A first network entity, a second network entity, and a third network entity for obtaining an average activity time period of a QoS level

Abstract

The present invention relates to obtaining an average active time period for a Quality of Service (QoS) level, wherein the average active time period represents the length of time a QoS flow can be expected to remain active at the QoS level. A first network entity (100) requests and receives from a second network entity (300) at least one of the following: an active time period set for a QoS level and an average active time period for the QoS level, wherein the active time period is the time period during 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 the average active time period for the QoS level.

Description

Technical Field

[0001] The present invention relates to a first network entity, a second network entity and a third network entity for obtaining an average activity time period of a quality of service (QoS) level. In addition, the present invention also relates to a corresponding method and a computer program. Background Art

[0002] The QoS model of the 5G system has appropriate mechanisms to ensure that the QoS of a QoS flow is guaranteed. However, due to, for example, unexpected demand and radio impairments, the pre-agreed QoS of a QoS flow cannot always be maintained throughout the life cycle of the QoS flow. In the case of non-guaranteed bit rate (GBR) services, the pre-agreed QoS can fluctuate dynamically through a mechanism called reflective QoS. On the other hand, in the case of GBR services, the radio access network can generate a notification control to the next-generation core (NGC) when it is difficult to meet the QoS requirements of a QoS flow, and the NGC decides how to handle the current QoS flow. Summary of the Invention

[0003] The purpose of embodiments of the present invention is to provide a solution to reduce or solve the disadvantages and problems of traditional solutions.

[0004] These 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.

[0005] According to a first aspect of the present invention, the above and other objects are achieved using a first network entity, wherein the first network entity is configured to:

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

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

[0008] An average activity time period of the QoS level is obtained according to the second message.

[0009] The first network entity may send a first message 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 an average activity time period based on input from more than one second network entity.

[0010] An advantage of the first network entity according to the first aspect is that the first network entity can obtain a metric indicating the length of time a QoS flow can be expected to remain active at the QoS level, sometimes referred to as the QoS level's maintainability. The average activity period of the QoS level is provided in an easily interpretable format.

[0011] According to the first aspect, in an implementation of the first network entity, 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 the following: the number of QoS flows, the number of radio link failures, the number of switching failures, and the number of beam failures.

[0012] An advantage of this implementation is that the number of radio link failures, handover failures, and / or beam failures can be reflected in the average active time period of a QoS level. For example, the greater the number of radio link failures, handover failures, and / or beam failures, the lower the average active time period of a QoS level. Therefore, the average active time period of a QoS level can accurately reflect the QoS level's maintainability.

[0013] According to the first aspect, in an implementation of the first network entity, the second message further indicates at least one of the following: the number of QoS flows, the number of radio link failures, the number of handover failures, and the number of beam failures.

[0014] An advantage of this implementation manner is that the first network entity can obtain the number of radio link failures, handover failures and / or beam failures that have occurred from the second network entity.

[0015] According to the first aspect, in the implementation method of the first network entity, at least one of the active time period set of the QoS level and the average active time period of the QoS level is associated with at least one of the cell and network slice selection assistance information (NSSAI).

[0016] An advantage of this implementation is that an average active period of a QoS level can be derived for a specific cell and / or NSSAI. Thus, the first network entity can determine the maintainability of the QoS level for each cell and / or NSSAI.

[0017] According to the first aspect, in an implementation manner of the first network entity, the derived activity time period of the QoS level is associated with at least one of the cell and the NSSAI.

[0018] The advantage of this implementation is that the preservation of QoS levels can be derived and provided for specific cells and / or NSSAIs.

[0019] According to the first aspect, in an implementation of the first network entity, the first network entity is a network data analytics function (NWDAF).

[0020] This implementation has the advantage of enhancing the existing functionality in the NWDAF to obtain the average activity period indicating the length of time a QoS flow can be expected to remain active at the QoS level.

[0021] According to a second aspect of the present invention, the above and other objects are achieved using a second network entity, wherein the second network entity is configured to:

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

[0023] Obtain at least one of an active time period set of the QoS level and an average active time period of the QoS level;

[0024] A second message is sent to the first network entity, wherein the second message indicates at least one of the set of activity time periods for the QoS level and the average activity time period for the QoS level.

[0025] According to the second aspect, the second network entity has the advantage that it can obtain and exchange information related to the activity time periods of the QoS levels, thereby supporting the determination of the retentivity of the QoS levels.

[0026] According to the second aspect, in an implementation manner of the second network entity, obtaining the active time period set of the QoS level includes:

[0027] An activity time period of at least one QoS flow active at the QoS level is measured.

[0028] The advantage of this implementation is that the activity time period of each QoS flow at the QoS level can be determined in the second network entity.

[0029] According to the second aspect, in an implementation manner of the second network entity, obtaining the active time period set of the QoS level includes:

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

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

[0032] According to the second aspect, in an implementation manner of the second network entity, obtaining the active time period set of the QoS level includes:

[0033] Sending a third message to a third network entity, wherein the third message indicates a set of active time periods requesting the QoS level;

[0034] A fourth message is received from the third network entity, wherein the fourth message indicates a set of active time periods for the QoS level.

[0035] The advantage of this implementation is that different entities can participate in determining the activity time period of the QoS level, thereby providing a flexible and robust solution.

[0036] According to the second aspect, in an implementation manner of the second network entity, obtaining the average activity time period of the QoS level includes:

[0037] The average active time period of the QoS level is calculated based on the set of active time periods of the QoS level 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.

[0038] An advantage of this implementation is that the number of radio link failures, handover failures, and / or beam failures can be reflected in the average active time period of a QoS level. For example, the greater the number of radio link failures, handover failures, and / or beam failures, the lower the average active time period of a QoS level. Therefore, the average active time period of a QoS level can accurately reflect the QoS level's maintainability.

[0039] According to the second aspect, in an implementation of the 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.

[0040] The advantage of this implementation is that the first network entity can determine the maintainability of the QoS level for each cell and / or NSSAI.

[0041] According to the second aspect, in the 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.

[0042] The advantage of this implementation is that it enhances the existing functions in SMF, AMF or OAM, thereby enabling SMF, AMF or OAM to obtain and exchange information related to the activity time period of the QoS level.

[0043] According to a third aspect of the present invention, the above and other objects are achieved using a third network entity, wherein the third network entity is configured to:

[0044] receiving a third message from the second network entity, wherein the third message indicates a set of active time periods for the requested QoS level, wherein the active time period is a time period during which the QoS flow is active at the QoS level;

[0045] Obtaining a set of active time periods for the QoS level;

[0046] A fourth message is sent to the second network entity, wherein the fourth message indicates the acquired active time period set of the QoS level.

[0047] According to the third aspect, the advantage of the third network entity is that the third network entity also participates in determining the activity time period of the QoS level, thereby making the solution more flexible and robust.

[0048] According to the third aspect, in an implementation manner of the third network entity, obtaining the active time period set of the QoS level includes:

[0049] An activity time period of at least one QoS flow active at the QoS level is measured.

[0050] The advantage of this implementation is that the activity time period of the QoS level can be determined in the third network entity by considering each QoS flow.

[0051] According to the third aspect, in an implementation manner of the third network entity, obtaining the active time period set of the QoS level includes:

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

[0053] The advantage of this implementation is that the activity time period of the QoS level can be determined in the third network entity using known methods.

[0054] According to the third aspect, in an implementation manner of the 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.

[0055] An advantage of this implementation is that the third network entity can provide information related to the activity time period, which makes it possible to determine the preservation of the QoS level for each cell or NSSAI.

[0056] According to the third aspect, in an implementation manner of the third network entity, the third network entity is a client device or a network access node.

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

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

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

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

[0061] An average activity time period of the QoS level is obtained according to the second message.

[0062] The method according to the fourth aspect can be extended to an implementation corresponding to the implementation of the first network entity according to the first aspect. Therefore, the implementation of the method includes one or more features of the corresponding implementation of the first network entity.

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

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

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

[0066] Obtain at least one of an active time period set of the QoS level and an average active time period of the QoS level;

[0067] A second message is sent to the first network entity, wherein the second message indicates at least one of the set of activity time periods for the QoS level and the average activity time period for the QoS level.

[0068] The method according to the fifth aspect can be extended to an implementation corresponding to the implementation of the second network entity according to the second aspect. Therefore, the implementation of the method includes one or more features of the corresponding implementation of the second network entity.

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

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

[0071] receiving a third message from the second network entity, wherein the third message indicates a set of active time periods for the requested QoS level, wherein the active time period is a time period during which the QoS flow is active at the QoS level;

[0072] Obtaining a set of active time periods for the QoS level;

[0073] A fourth message is sent to the second network entity, wherein the fourth message indicates the acquired active time period set of the QoS level.

[0074] The method according to the sixth aspect can be extended to an implementation corresponding to the implementation of the third network entity according to the third aspect. Therefore, the implementation of the method includes one or more features of the corresponding implementation of the third network entity.

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

[0076] The present invention also relates to a computer program, wherein the program code, when executed by at least one processor, causes the at least one processor to perform any method according to an embodiment of the present invention. In addition, the present invention also relates to a computer program product comprising a computer-readable medium and the computer program, wherein the computer program is included in the computer-readable medium and comprises one or more of the following: a read-only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), a flash memory, an electrically EPROM (EEPROM), and a hard disk drive.

[0077] Other applications and advantages of embodiments of the present invention will become apparent from the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0078] The accompanying drawings are intended to illustrate and explain different embodiments of the present invention. In the drawings:

[0079] Figure 1 shows a first network entity according to an embodiment of the present invention;

[0080] Figure 2 A method for a first network entity according to an embodiment of the present invention is shown;

[0081] Figure 3 shows a second network entity according to an embodiment of the present invention;

[0082] Figure 4 A method for a second network entity according to an embodiment of the present invention is shown;

[0083] Figure 5 shows a third network entity according to an embodiment of the present invention;

[0084] Figure 6 A method for a third network entity according to an embodiment of the present invention is shown;

[0085] Figure 7 shows signaling between a first network entity and a second network entity according to an embodiment of the present invention;

[0086] Figure 8 The signaling between the second network entity and the third network entity according to an embodiment of the present invention is shown. DETAILED DESCRIPTION

[0087] Although the basic mechanism for alerting the user equipment (UE) whenever the QoS of a PDU session falls below a pre-agreed performance level is standardized in the Rel-16 timeframe in 3GPP, the 5G system does not know how long the PDU session can be expected to maintain the pre-agreed QoS when accepting a new PDU session. The length of time the network is expected to achieve the pre-agreed QoS for a QoS flow is sometimes referred to as the QoS flow's retainability.

[0088] Given the inherent characteristics of packet-switched based 5G systems, it is necessary to measure how long a communication session can be maintained at a pre-agreed QoS level at a specific location or time so that the measurement results can clearly and easily indicate / reflect / represent the maintainability.

[0089] 3GPP has introduced a key performance indicator (KPI) for retention that shows how often an end user experiences abnormal loss of a QoS flow during its use. The retention KPI is measured based on the number of QoS flows for which data in the buffer is abnormally released and is normalized using the number of data session time units. One issue with this measurement is that it mixes the number of releases that occurred with the session time, making the interpretation of the resulting value non-intuitive. Furthermore, the retention of any cellular network due to congestion depends on the radio access network (RAN) resources, as the RAN is the bottleneck in the network. Therefore, it would be more appropriate if retention-related measurements were taken from the UE, RAN, and session management function (SMF).

[0090] According to one proposal, a measurement KPI is defined as the in-session active time for a QoS flow. This measurement provides the cumulative active session time for QoS flows in a cell. Alternatively, a UE in-session active time is defined, which provides the cumulative active session time for UEs in a cell. The measurement KPI is 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 UE's QoS requirements. Retention measurements must truly reflect network issues, and the way the in-session active time is calculated for QoS flows and UEs does not allow for this distinction.

[0091] According to an embodiment of the present invention, an average activity time period of a QoS level is introduced, which reflects the network's ability to meet the UE's QoS requirements by indicating the time period a QoS flow can be expected to remain active at the QoS level.

[0092] Figure 1FIG. 1 shows a first network entity 100 according to an embodiment of the present invention. Figure 1 In the illustrated embodiment, a first network entity 100 includes a processor 102, a transceiver 104, and a memory 106. The processor 102 is coupled to the transceiver 104 and the memory 106 via a communication device 108 known in the art. The first network entity 100 may be configured to perform wireless communication and wired communication in a wireless communication system and a wired communication system, respectively. Wireless communication capabilities may be provided by an antenna or antenna array 110 coupled to the transceiver 104, while wired communication capabilities may be provided by a wired communication interface 112 coupled to the transceiver 104.

[0093] 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 includes appropriate devices for performing the actions, such as a processor 102 and a transceiver 104 .

[0094] According to an embodiment of the present invention, a first network entity 100 is configured to send a first message 510 to a second network entity 300, wherein the first message 510 indicates a request for at least one of the following: 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 during 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 following: the set of active time periods for the QoS level and the average active time period for the QoS level, and to derive the average active time period for the QoS level based on the second message 520.

[0095] Figure 2 It is shown that it is possible to Figure 1 Flowchart of a corresponding method 200 performed in a first network entity 100 as shown in FIG. The method 200 includes 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 activity time periods for a QoS level and an average activity time period for the QoS level, wherein an activity time period is a time period during which a QoS flow is active at the QoS level. The method 200 also includes receiving 204 a second message 520 from the second network entity 300, wherein the second message 520 indicates at least one of: the set of activity time periods for the QoS level and an average activity time period for the QoS level; and deriving 206 the average activity time period for the QoS level based on the second message 520.

[0096] Figure 3 FIG. 3 shows a second network entity 300 according to an embodiment of the present invention. Figure 3 In the illustrated embodiment, the second network entity 300 includes a processor 302, a transceiver 304, and a memory 306. The processor 302 is coupled to the transceiver 304 and the memory 306 via a communication device 308 known in the art. The second network entity 300 can be configured to perform wireless communication and wired communication in a wireless communication system and a wired communication system, respectively. Wireless communication capabilities can be provided by an antenna or antenna array 310 coupled to the transceiver 304, while wired communication capabilities can be provided by a wired communication interface 312 coupled to the transceiver 304.

[0097] In the present invention, the second network entity 300 being configured to perform certain actions may be understood to mean that the second network entity 300 includes appropriate devices for performing the actions, such as a processor 302 and a transceiver 304 .

[0098] According to an embodiment of the present invention, the second network entity 300 is used to receive a first message 510 from the first network entity 100, wherein the first message 510 indicates at least one of an active time period set of the requested QoS level and an average active time period of the QoS level, wherein the active time period is a time period during which the QoS flow is active at the QoS level; the second network entity 300 is also used to obtain at least one of an active time period set of the QoS level and an 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 an active time period set of the QoS level and an average active time period of the QoS level.

[0099] Figure 4 It is shown that it is possible to Figure 3 4 shows a flow chart of a corresponding method 400 performed in the second network entity 300 shown in FIG. The method 400 includes receiving 402 a first message 510 from the first network entity 100, wherein the first message 510 indicates at least one of a set of activity time periods for the requested QoS level and an average activity time period for the QoS level, wherein an activity time period is a time period during which a QoS flow is active at the QoS level. The method 400 also includes obtaining 404 at least one of the set of activity time periods for the QoS level and the average activity time period for 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 activity time periods for the QoS level and the average activity time period for the QoS level.

[0100] Figure 5 FIG. 5 shows a third network entity 500 according to an embodiment of the present invention. Figure 5In the illustrated embodiment, the third network entity 500 includes a processor 502, a transceiver 504, and a memory 506. The processor 502 is coupled to the transceiver 504 and the memory 506 via a communication device 508 known in the art. The third network entity 500 can be configured to perform wireless communication and wired communication in a wireless communication system and a wired communication system, respectively. Wireless communication capabilities can be provided by an antenna or antenna array 510 coupled to the transceiver 504, while wired communication capabilities can be provided by a wired communication interface 512 coupled to the transceiver 504.

[0101] In the present invention, the third network entity 500 being configured to perform certain actions may be understood to mean that the third network entity 500 includes appropriate devices for performing the actions, such as a processor 502 and a transceiver 504 .

[0102] 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 for the requested QoS level, wherein the active time period is a time period during which a QoS flow is active at the requested QoS level. The third network entity 500 is further configured to obtain the set of active time periods for the requested QoS level 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 requested QoS level.

[0103] Figure 6 It is shown that it is possible to Figure 5 6 shows a flow chart of a corresponding method 600 executed in the third network entity 500. The method 600 includes 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 the requested QoS level, wherein the active time period is a time period during which a QoS flow is active at the requested QoS level. The method 600 also includes obtaining 604 the set of active time periods for the requested 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 requested QoS level.

[0104] Figure 71 shows signaling between a first network entity 100 and a second network entity 300 for exchanging information associated with an activity 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 analytics 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.

[0105] exist Figure 7 In step I, 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 the following: a set of active time periods for a QoS level and an average active time period for the QoS level. Each active time period in the set of active time periods is a time period during which a QoS flow is active at the QoS level. The QoS level may correspond to a set of QoS requirements including QoS parameters and / or QoS characteristics. In an embodiment, the QoS level may be defined by a 5G QoS identifier (5QI).

[0106] The first network entity 100 may send a first message 510 to the second network entity 300 to obtain or subscribe to information associated with the active time period of the QoS level. Thus, the first message 510 may be a request to obtain information associated with the active time period of the QoS level. However, the first message 510 may also be a request to subscribe to information associated with the active time period of the QoS level. In the latter case, the first message 510 may trigger the second network entity 300 to monitor the information associated with the active time period of the QoS level and report the information to the first network entity 100 at predetermined intervals.

[0107] In an embodiment where the first network entity 100 is an NWDAF and the second network entity 300 is an SMF, an AMF or an OAM, the first message 510 may correspond to an Nsmf_EventExposure_Subscribe message or a Namf_EventExposure_Subscribe message according to the 3GPP standard, and one or more additional information elements.

[0108] The second network entity 300 receives the first message 510 from the first network entity 100, thereby receiving a request for at least one of a set of activity time periods for a QoS class and an average activity time period for a QoS class. Figure 7 In step II, the second network entity 300 obtains at least one of the set of active time periods for the QoS level and the average active time period for the QoS level based on the received first message 510. The second network entity 300 may obtain at least one of the set of active time periods for the QoS level and the average active time period for the QoS level based on measurement results in the second network entity 300 and / or based on measurement results obtained from another network entity (e.g., the third network entity 500).

[0109] When the first message 510 indicates that an active time period set of a QoS level is requested, the second network entity 300 may obtain an active time period set of the QoS level based on a measurement result in the second network entity 300. The second network entity 300 may obtain an active time period set of the QoS level by measuring an active time period of at least one QoS flow active at the QoS level. The second network entity 300 may measure an active time period for each QoS flow active at the QoS level in the second network entity 300 or active in another entity reporting to the second network entity 300. Therefore, the active time period set of the QoS level may include an active time period of each active QoS flow at the QoS level. The second network entity 300 may also measure an active time period of each QoS flow active at the QoS level in the cell and / or in network slice selection assistance information (NSSAI), so that the active time period set of the QoS level is associated with at least one of the cell and the NSSAI, as further described below.

[0110] In an embodiment, the second network entity 300 may measure the active time period of at least one QoS flow active at a QoS level based on at least one of a timer and a time window. The timer may be a timer that measures the time that a QoS flow with a specific QoS level (e.g., a specific 5QI) has been active, and may start when the QoS flow is started or moved to a specific QoS level. The timer may stop when the QoS flow is interrupted, for example, due to a radio link failure, a switching failure, or a beam failure. The timer may also stop if the QoS is modified so 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 that defines a time period for measuring the active time period of at least one QoS flow active at a QoS level. The timer may be triggered for each QoS flow per QoS level, so that multiple timers are active for a specific QoS level. Therefore, the set of active time periods for a QoS level may be measured based on the number of timers for the QoS level.

[0111] The second network entity 300 may also obtain the set of active time periods of the QoS level from the third network entity 500 by making a request for the set of active time periods of the QoS level to the third network entity 500. Figure 8 Further details related to the signaling between the second network entity 300 and the third network entity 500 for exchanging active time period sets of QoS levels are described.

[0112] When the first message 510 indicates the average activity time period of the requested QoS level, the second network entity 300 may obtain the average activity time period of the QoS level based on the activity time period set of the QoS level. The activity time period set of the QoS level may be obtained as described above, i.e., based on the measurement result in the second network entity 300 and / or based on the activity time period set of the QoS level received from the third network entity 500.

[0113] The second network entity 300 may obtain the average active time period of the QoS level by calculating the average active time period of the QoS level based on the active time period set of the QoS level and 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 measurement results in the second network entity 300 or from another network entity (e.g., the third network entity 500). The average active time period of the QoS level may be a ratio between the active time period set of the QoS level and 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.

[0114] exist Figure 7 In step III, the second network entity 300 sends a second message 520 to the first network entity 100. The second message 520 indicates that Figure 7 At least one of the set of active time periods of the QoS level and the average active time period of the QoS level obtained by the second network entity 300 in step II.

[0115] In an embodiment where the first network entity 100 is an NWDAF and the second network entity 300 is an SMF, an AMF or an OAM, the second message 520 may correspond to an Nsmf_EventExposure_Notify message or an Nsmf_EventExposure_Notify message according to the 3GPP standard and one or more additional information elements.

[0116] 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 class indicated in the second message 520 and the average active time period of the QoS class.

[0117] exist Figure 7 In step IV, based on the received second message 520, the first network entity 100 derives the average active time period for the QoS level. Thus, the first network entity 100 can 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 indicated in the second message 520 and the average active time period for the QoS level. The second message 520 may include other information that can also be used to derive the average active time period. The derived average active time period for the QoS level is a measure of the length of time a QoS flow is expected to remain active at that QoS level, and can therefore be used to indicate the likelihood that a QoS flow initiated at a QoS level can remain active at that QoS level.

[0118] In an embodiment, when establishing a packet data unit (PDU) session, the first network entity 100 may provide the derived average activity time period of the QoS level to other network entities (e.g., an application function (AF) or a client application running in a client device). The AF or the client application may use the derived average activity time period of the QoS level as input to a determination function / algorithm. In the case of a vehicle-to-anything (V2X) application, for example, the derived average activity time period of the QoS level may help the AF switch to a physical path with higher survivability at the required QoS level.

[0119] In an embodiment, the average active time period for a QoS level is based on a ratio between the set of active time periods for the QoS level and at least one of the following: the number of QoS flows, the number of radio link failures, the number of handover failures, and the number of beam failures. The 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 can be obtained, for example, from the second network entity 300 in a second message 520 or from another network entity. Therefore, in an embodiment, the second message 520 can also indicate at least one of the following: the number of QoS flows, the number of radio link failures, the number of handover failures, and the number of beam failures. However, this information can be received in a separate message or obtained from another network entity or database.

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

[0121]

[0122] Among them, 5QIx is the QoS level to be calculated for the average active time period, ∑ i The active time period 5QIx is the sum of the i active time periods in the active time period set for 5QIx, and TotNbrQoSFlows5QI x is the total number of QoS flows of 5QIx, and TotalNbrRLFs.HOFs.BFs is the total number of radio link failures, handover failures, and beam failures.

[0123] The average activity period can be derived based on a sliding time window that defines the time period over which the average period is to be calculated. This is similar to a moving average (rolling average or sliding average), which is a calculation that analyzes data points by creating a series of averages of different subsets of the complete dataset. By having a sliding time window, the goal is to take a temporal average of a random or arbitrary time variable over different moving time windows.

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

[0125] According to an embodiment of the present invention, at least one of the set of active time periods for a QoS level and the average active time period for a 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 for a QoS level and / or an average active time period for a QoS level for a specific cell and / or NSSAI. A cell may be identified, for example, by a physical cell identifier (PCI), an NR cell global identifier (NCGI), or an E-UTRAN cell global identifier (ECGI). The first network entity 100 may also derive an average active time period for a specific cell and / or NSSAI. Therefore, in an embodiment, the derived average active time period for a QoS level may be associated with at least one of a cell and an NSSAI. Therefore, the derived active time period may indicate the expected time that a QoS flow may remain active at a QoS level in a cell and / or NSSAI.

[0126] In reference Figure 7 In the described embodiment, the first network entity 100 requests information associated with the activity time period from one second network entity 300 and receives one second message 520. However, in an embodiment, the first network entity 100 may request and receive information associated with the activity 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.

[0127] The first network entity 100 may derive an average activity time period for a QoS level based on some or all of the information received from more than one second network entity 300. For example, the first network entity 100 may receive multiple average activity time periods for a QoS level from different second network entities 300 and derive the average activity time period for the QoS level based on the multiple received average activity time periods. The derived average activity time period for the QoS level may be, for example, the average or mean of the multiple received average activity time periods. Furthermore, the first network entity 100 may receive an activity time period set from each second network entity 300 serving the cell and derive the average activity time period for the QoS level based on the received activity time period set, thereby further deriving the average activity time period for the QoS level of the cell.

[0128] Figure 8The figure shows signaling for exchanging active time period sets of 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).

[0129] exist Figure 8 In step I, the second network entity 300 sends a third message 530 to the third network entity 500. The third message 530 indicates a set of activity time periods for the requested QoS level.

[0130] 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. When the second network entity 300 receives an indication that the third network entity 500 is initiating a PDU session, the second network entity 300 may further send the third message 530. 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 exchanged between the AMF and the UE.

[0131] The third network entity 500 receives the third message 530 from the second network entity 300, thereby receiving a request for a set of active time periods for a QoS level. Figure 8 In step II, based on the third message 530, the third network entity 500 obtains the set of active time periods for the QoS level. The third network entity 500 may obtain the set of active time periods for the QoS level by measuring the active time periods of at least one QoS flow active at the QoS level. For example, this may be achieved by measuring the active time periods of each QoS flow active at the QoS level in the third network entity 500. Therefore, the set of active time periods for the QoS level may include the active time periods of each QoS flow active at the QoS level in the third network entity 500.

[0132] In an embodiment, the third network entity 500 may measure the active 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. Figure 7 Step II in takes place in the same way as described for the second network entity 300 .

[0133] According to an embodiment of the present invention, the third network entity 500 may further calculate the average activity time period of the QoS level based on the acquired activity time period set of the QoS level. Figure 7 The average activity time period of the QoS level is calculated in the same manner as described in step II for the second network entity 300. In the embodiment where the third network entity 500 calculates the average activity time period of the QoS level, the third message 530 may also indicate the average activity time period of the requested QoS level.

[0134] As previously described, the set of active time periods and / or the averaging time period for a 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 obtain the set of active time periods for the QoS level based on the cell and / or NSSAI. Therefore, in an embodiment, the active time period is obtained for a QoS flow in a specific cell and / or NSSAI.

[0135] exist Figure 8 In step III, the third network entity 500 sends a fourth message 540 to the second network entity 300. The fourth message 540 indicates the obtained set of active time periods for the QoS level and / or the obtained average time period for the QoS level. The second network entity 300 receives the fourth message 540 from the third network entity 500 and thereby obtains the indicated set of active time periods for the QoS level and / or the indicated average time period for the QoS level. Upon receiving the obtained set of active time periods for the QoS level and / or the obtained average time period for the QoS level, the second network entity 300 may forward the obtained set of active time periods for the QoS level and / or the obtained average time period for the QoS level to the first network entity 100 without modification, or use the obtained set of active time periods for the QoS level and / or the obtained average time period to derive / calculate, for example, the average active time period, as described above with reference to FIG. Figure 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 second network entities 300 and / or third network entities 500.

[0136] 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 3GPP-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 3GPP TS 23.288.

[0137] The second network entity 300 herein may be represented as a session management function (SMF), an access and management function (AMF), or an OAM. The SMF, AMF, or OAM may be functions configured for communication in 3GPP-related LTE and LTE-Advanced, in WiMAX and its evolution, and in fifth-generation wireless technologies such as new radio (NR).

[0138] The third network entity 500 herein may represent a client device or a network access node. The client device may also be represented as a user apparatus, user equipment (UE), a mobile station, an Internet of Things (IoT) device, a sensor device, a wireless terminal and / or a mobile terminal, capable of wireless communication in a wireless communication system (sometimes also 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 computer with wireless functionality. In this context, the UE may be, for example, a portable, pocket-storage, handheld, computer-contained or vehicle-mounted mobile device capable of transmitting 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 including a media access control (MAC) and physical layer (PHY) interface to a wireless medium (WM) that complies with IEEE 802.11. The UE may also be configured to communicate in 3GPP-related LTE and LTE-Advanced, in WiMAX and its evolutions, and in fifth generation wireless technologies such as New Radio.

[0139] A network access node may also be denoted as a radio network access node, access network access node, access point, or base station, such as a radio base station (RBS), which in some networks may be referred to as a transmitter, "gNB", "gNodeB", "eNB", "eNodeB", "NodeB" or "B node", depending on the technology and terminology used. Radio network access nodes may be of different categories, such as macro eNodeB, home eNodeB or pico base station, depending on the transmission power and, therefore, the cell size. A radio network access node may be a station (STA), which is any device that includes a media access control (MAC) and physical layer (PHY) interface to a wireless medium (WM) that complies with IEEE 802.11. A radio network access node may also be a base station corresponding to a fifth generation (5G) wireless system. A radio network access node in this document may also be denoted as a roadside unit, such as a roadside unit in a V2X application. A roadside unit may be any device / node deployed along a road to improve vehicle network performance and extend coverage. A roadside unit may be a standalone device / node, or may be integrated with, for example, a network access node.

[0140] In addition, any method according to an embodiment of the present invention can be implemented in a computer program having a codec unit, which, when executed by a processing device, causes the processing device to perform the method steps. The computer program is included in a computer-readable medium of a computer program product. The computer-readable medium can 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 disk drive.

[0141] Furthermore, those skilled in the art will recognize that embodiments of the first network entity 100, the second network entity 300, and the third network entity 500 include necessary communication capabilities in the form of, for example, functions, devices, units, elements, and the like for performing the scheme. Examples of other such devices, units, elements, and functions include: a processor, a memory, a buffer, control logic, an encoder, a decoder, a rate matcher, a derate matcher, a mapping unit, a multiplier, a decision unit, a selection unit, a switch, an interleaver, a deinterleaver, a modulator, a demodulator, an input, an output, an antenna, an amplifier, a receiver unit, a transmitter unit, a DSP, an MSD, a TCM encoder, a TCM decoder, a power supply unit, a power supply line, a communication interface, a communication protocol, and the like, which are appropriately arranged together to perform the scheme.

[0142] In particular, the one or more processors of the first network entity 100, the second network entity 300, and the 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 capable of interpreting and executing instructions. The term "processor" may therefore refer to a processing circuit system comprising multiple processing circuits, such as any, some, or all of the items listed above. The processing circuit system may also perform data processing functions for inputting, outputting, and processing data, including data buffering and device control functions, such as call processing control and user interface control.

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

Claims

1. A first network entity (100), characterized in that: Includes a transceiver and a processor, including: The transceiver is configured to send a first message (510) to a second network entity (300), wherein the first message (510) indicates a request for at least one of the following: an activity time period set of a QoS level, wherein the activity time periods in the activity time period set of the QoS level are used to calculate the average activity time period of the QoS level, and the activity time period is the time period during which the QoS flow is active at the QoS level, or The average activity period for the QoS level, The transceiver 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: a set of activity time periods for the QoS level and an average activity time period for the QoS level; and The processor is configured to derive an average activity time period of the QoS level according to the second message (520).

2. The first network entity (100) according to claim 1, characterized in that The average active time period for the QoS level is based on a ratio between the set of active time periods 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.

3. The first network entity (100) according to claim 2, characterized in that The second message (520) further indicates at least one of the following: 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) according to any one of claims 1 to 3, characterized in that At least one of the set of active time periods for the QoS level and the average active time period for the QoS level is associated with at least one of cell and network slice selection assistance information NSSAI.

5. The first network entity (100) according to claim 4, characterized in that 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), characterized in that: Includes a transceiver and a processor, including: The transceiver is configured to receive a first message (510) from a first network entity (100), wherein the first message (510) indicates a request for at least one of the following: an activity time period set of a QoS level, wherein the activity time periods in the activity time period set of the QoS level are used to calculate the average activity time period of the QoS level, and the activity time period is the time period during which the QoS flow is active at the QoS level, or The average activity period for the QoS level, The processor is configured to obtain at least one of an activity time period set of the QoS level and an average activity time period of the QoS level; The transceiver is further configured to send a second message (520) to the first network entity (100), wherein the second message (520) indicates at least one of the set of activity time periods for the QoS level and the average activity time period for the QoS level.

7. The second network entity (300) according to claim 6, characterized in that Obtaining the active time period set of the QoS level includes: An activity time period of at least one QoS flow active at the QoS level is measured.

8. The second network entity (300) according to claim 7, characterized in that Obtaining the active time period set of the QoS level 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.

9. The second network entity (300) according to any one of claims 6 to 8, characterized in that Obtaining the active time period set of the QoS level includes: sending a third message (530) to a third network entity (500), wherein the third message (530) indicates a set of activity time periods requesting the QoS level; A fourth message (540) is received from the third network entity (500), wherein the fourth message (540) indicates a set of activity time periods for the QoS level.

10. The second network entity (300) according to any one of claims 6 to 8, characterized in that Obtaining the average activity time period of the QoS level includes: The average active time period of the QoS level is calculated based on the set of active time periods of the QoS level 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.

11. The second network entity (300) according to any one of claims 6 to 8, characterized in that At least one of the set of active time periods for the QoS class and the average active time period for the QoS class is associated with at least one of a cell and an NSSAI.

12. A third network entity (500), characterized in that: Includes a transceiver and a processor, including: The transceiver is configured to receive a third message (530) from a second network entity (300), wherein the third message (530) indicates a set of activity time periods for a requested QoS level, wherein the activity time periods in the set of activity time periods for the QoS level are used to calculate an average activity time period for the QoS level, the activity time period being a time period during which a QoS flow is active at the QoS level; The processor is configured to obtain an active time period set of the QoS level; The transceiver is further configured to send a fourth message (540) to the second network entity (300), wherein the fourth message (540) indicates the acquired set of activity time periods of the QoS level.

13. The third network entity (500) according to claim 12, characterized in that Acquiring the active time period set of the QoS level includes: An activity time period of at least one QoS flow active at the QoS level is measured.

14. The third network entity (500) according to claim 13, characterized in that Acquiring the active time period set of the QoS level 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.

15. The third network entity (500) according to any one of claims 12 or 14, characterized in that The set of active time periods for the QoS class is associated with at least one of a cell and an NSSAI.

Images