QoS measurement for multiple UEs

Abstract

Embodiments of this specification relate to QoS measurements for multiple UEs. In some embodiments, a method (500) is proposed that is performed by a first network function (111, 700) implementing a Vertical Application Layer (VAL) server. In one embodiment, the method may include the step (S501) of sending a subscription message to a second network function (212, 800) implementing a Service Enabler Architecture Layer (SEAL) Data Distribution (DD) server to request a report of transmit quality measurements for one or more VAL user devices (UEs) (201). The subscription message includes a first parameter that indicates a group of VAL UEs (201) or all VAL UEs (201) as the measurement target VAL UE. In one embodiment, the method may further include the step (S502) of receiving an notification message from the second network function (212, 800) to provide a report of transmit quality measurements. According to embodiments of this specification, QoS measurements at the SEALDD layer can be improved to support multiple VAL UEs in a single subscription.

Description

Technical Field

[0001] Cross - reference to Related Applications This application claims priority to PCT Application No. PCT / CN2023 / 076771, filed on February 17, 2023, entitled "QOS MEASUREMENT FOR MULTIPLE UES", the entire content of which is incorporated herein by reference.

[0002] Embodiments of this specification generally relate to the field of communications. More specifically, embodiments of this specification relate to quality of service (QoS) measurements for multiple user equipment (UE).

Background Art

[0003] SEAL (Service Enablement Architecture Layer for Verticals) has been introduced since 3GPP Release 16 to support vertical applications (e.g., V2X (Vehicle to Everything) applications). 3GPP TS23.434 specifies application plane entities and signaling plane entities for application enabling services (e.g., group management, configuration management, location management, identification information / key management, network resource management) that can be reused across vertical applications. Also, SEAL specifies north - bound application programming interfaces (APIs) for individual services of SEAL to enable flexible integration with vertical applications.

[0004] Figure 1 is a schematic block diagram showing a typical on-network functionality model 100 of SEAL. As shown in Figure 1, in the Vertical Application Layer (VAL), a VAL client 121 can communicate with a VAL server 111 via a VAL-UU reference point. The VAL-UU can support both unicast and multicast distribution modes.

[0005] The SEAL functional entities on UE101 and on the server are grouped into (one or more) SEAL clients 122 and (one or more) SEAL servers 112, respectively. SEAL may have a common set of services (e.g., group management, location management) and reference points. SEAL provides SEAL services to VAL.

[0006] One or more SEAL clients 122 can communicate with one or more SEAL servers 112 via a SEAL-UU reference point. SEAL-UU can support both unicast and multicast distribution modes. One or more SEAL clients 122 can provide service enabler layer support functionality to one or more VAL clients 121 via a SEAL-C reference point. One or more VAL servers 111 can communicate with one or more SEAL servers 112 via a SEAL-S reference point. One or more SEAL servers 112 can communicate with the underlying 3GPP network system 102 using their respective 3GPP interfaces specified by the 3GPP network system 102.

[0007] Data distribution (DD) One of the capabilities that SEAL offers is data delivery (DD).

[0008] Figure 2 is a schematic block diagram showing the on-network functional model of SEAL for DD, which is Architecture 200 for SEAL data distribution service.

[0009] For uplink (UL) traffic, VAL client 121 can send application data traffic to SEALDD client 222 for SEALDD services via SEALDD-C. After data plane packet processing by SEALDD client 222, the application data traffic can be converted to SEALDD data traffic and forwarded to SEALDD server 212 via SEALDD-UU. SEALDD server 212 can reconstruct the application data traffic and send it to VAL server 111 via SEALDD-S.

[0010] For downlink (DL) traffic, VAL server 111 can send application data traffic to SEALDD server 212 for SEALDD services via SEALDD-S. After data plane packet processing by SEALDD server 212, the application data traffic can be converted to SEALDD data traffic and forwarded to SEALDD client 222 via SEALDD-UU. SEALDD client 222 can reconstruct the application data traffic and send it to VAL client 121 via SEALDD-C.

[0011] Optionally, a VAL deployment may choose to route application signaling traffic and application data traffic for some or all of the functions it provides using the SEALDD service, and Figure 3 shows an architecture to achieve this. In this case, the VAL client 121 and VAL server 111 may choose not to maintain application connectivity on their own and may forward all application traffic via the SEALDD connection for their functions.

[0012] It should be noted that SEALDD capabilities can be provided to the VAL layer as an API, and it is up to the VAL layer to determine which traffic should be forwarded (e.g., application signaling, application data).

[0013] Figure 3 is a schematic block diagram showing an exemplary architecture for SEAL application traffic forwarding. SEALDD client 222 can interact with SEALDD server 212 to establish an application layer data transport path. Through this path, SEALDD server 212 and SEALDD client 222 can provide data transport service capabilities, such as data plane packet processing (e.g., packet duplication, deletion, or transport coordination), data forwarding, data caching, and background data transfer, to support VAL server 111 and VAL client 121.

[0014] The data transport service capabilities provided by SEALDD client 222 and SEALDD server 212 can be improved by performing data transmission quality measurement. Currently, SEALDD data transmission quality measurement supports only a single UE. [Overview of the project]

[0015] Embodiments of this specification propose methods, network functions, computer-readable media, and computer program products for enabling QoS measurement for multiple values.

[0016] In some embodiments, a method is proposed that is performed by a first network function implementing a VAL server. This method may include the step of sending a subscription message to a second network function implementing a SEALDD server to request a report of transmit quality measurements for one or more VAL UEs. The subscription message may include a first parameter that designates a group of VAL UEs, or all VAL UEs, as the measurement target VAL UE, and optionally all VAL UEs may have established a SEALDD connection with the second network function. This method may further include the step of receiving an notification message from the second network function to provide a report of transmit quality measurements.

[0017] In one embodiment, the first parameter may include a group identifier (ID) for a group of VALUEs, or an instruction to refer to all of the VALUEs.

[0018] In one embodiment, a group of VALUEs may include multiple VALUEs that share the same VAL service and / or are located in the same geographical area.

[0019] In one embodiment, the subscription message may further include a second parameter indicating the reporting periodicity if the reporting is set to periodic reporting.

[0020] In one embodiment, the subscription message may further include a third parameter indicating the reporting granularity.

[0021] In one embodiment, the reporting granularity may indicate whether the requested report is about a specific VALUE, about an individual VALUE among several VALUEs, about a group of VALUEs, or about all VALUEs.

[0022] In one embodiment, the subscription message may further include a fourth parameter that indicates one or more measurement conditions for transmission quality measurement.

[0023] In one embodiment, the one or more measurement conditions may include one or more spatial conditions and / or one or more temporal conditions.

[0024] In one embodiment, if one or more conditions are not met, the SEALDD server may stop or interrupt the transmission quality measurement.

[0025] In one embodiment, the notification message may further include a fifth parameter that indicates one or more VALUES for which the transmission quality is measured and / or a report of the transmission quality measurement is provided based on the third parameter.

[0026] In one embodiment, when the third parameter is set to a specific VALUE or an individual VALUE among a plurality of VALUES, the transmission quality measurement for one or more VALUES may be the transmission quality measurement value for the specific VALUE or the individual VALUE.

[0027] In one embodiment, when the third parameter is set to a plurality of VALUES, the transmission quality measurement for one or more VALUES may be an aggregation of the transmission quality measurement values for a group of VALUES or all VALUES.

[0028] In one embodiment, the notification message may further include a sixth parameter that indicates an average measurement value of a plurality of transmission quality measurement values for a group of VALUES or all VALUES.

[0029] In one embodiment, the subscription message may be a SEALDD enabled data transmission quality measurement subscription request.

[0030] In one embodiment, the notification message may be a SEALDD-enabled data transmission quality measurement notification.

[0031] In one embodiment, the transmission quality measurement may be a measurement relating to latency, bitrate, or packet loss rate.

[0032] In some embodiments, a method is proposed that is performed by a second network function implementing a SEALDD server. This method may include the step of receiving a subscription message from a first network function implementing a VAL server to request a report of transmit quality measurements for one or more VAL UEs. The subscription message may include a first parameter that designates a group of VAL UEs, or all VAL UEs, as the measurement target VAL UE, and optionally all VAL UEs may have established a SEALDD connection with the second network function. This method may further include the step of sending an alert message to the first network function to provide a report of the transmit quality measurements.

[0033] In one embodiment, the method may further include the step of identifying a SEALDD connection corresponding to a measurement target VALUE in order to trigger a measurement after receiving a subscription message and before sending a notification message.

[0034] In one embodiment, the first parameter may include a group ID for a group of VALUEs, or an instruction to indicate all VALUEs.

[0035] In one embodiment, a group of VALUEs may include multiple VALUEs that share the same VAL service and / or are located in the same geographical area.

[0036] In one embodiment, the subscription message may further include a second parameter indicating the reporting periodicity if the reporting is set to periodic reporting.

[0037] In one embodiment, the subscription message may further include a third parameter indicating the reporting granularity.

[0038] In one embodiment, the reporting granularity may indicate whether the requested report is about a specific VALUE, about an individual VALUE among several VALUEs, about a group of VALUEs, or about all VALUEs.

[0039] In one embodiment, the subscription message may further include a fourth parameter that specifies one or more measurement conditions for transmission quality measurement.

[0040] In one embodiment, one or more measurement conditions may include one or more spatial conditions and / or one or more temporal conditions.

[0041] In one embodiment, if one or more conditions are not met, the SEALDD server may stop or interrupt the transmission quality measurement.

[0042] In one embodiment, the method may further include the steps of performing a transmit quality measurement to obtain one or more measurements for each of a group of VALUEs or all of VALUEs, which are performed repeatedly, and generating one or more transmit quality measurement reports based on the one or more measurements.

[0043] In one embodiment, the method may further include the step of aggregating one or more transmit quality measurement reports to form an aggregated transmit quality measurement report.

[0044] In one embodiment, the notification message may further include a fifth parameter indicating one or more VALUEs, on which the transmission quality is measured and / or a report of the transmission quality measurement is provided.

[0045] In one embodiment, if the third parameter is set to a specific VALUE or to an individual VALUE among several VALUEs, the transmission quality measurement for one or more VALUEs may be a transmission quality measurement for a specific VALUE or an individual VALUE.

[0046] In one embodiment, if the third parameter is set for multiple VALUEs, the transmission quality measurement for one or more VALUEs may be an aggregation of transmission quality measurements for a group of VALUEs or for all VALUEs.

[0047] In one embodiment, the notification message may further include a sixth parameter indicating the average measurement of multiple transmission quality measurements for a group of VALUEs or all of VALUEs.

[0048] In one embodiment, the subscription message may be a SEALDD-enabled data transmission quality measurement subscription request.

[0049] In one embodiment, the notification message may be a SEALDD-enabled data transmission quality measurement notification.

[0050] In one embodiment, the transmission quality measurement may be a measurement relating to latency, bitrate, or packet loss rate.

[0051] In some embodiments, a network function is proposed comprising at least one processor and a non-temporary computer-readable medium coupled to the at least one processor. In one embodiment, the non-temporary computer-readable medium may store instructions executable by the at least one processor, thereby allowing the at least one processor to be configured to perform the above-described method relating to the network function. In one embodiment, the network function may be configured as the first network function or the second network function.

[0052] In some embodiments, we propose a computer-readable medium that stores computer-readable code that, when operated on the device, can cause the device to perform any of the methods described above.

[0053] In some embodiments, we propose a computer program product that stores computer-readable code that, when run on the device, can cause the device to perform any of the methods described above.

[0054] According to embodiments of this specification, QoS measurement in the SEALDD layer may be improved to support multiple VAL UEs in a single subscription, otherwise the VAL server would need to send many subscription requests (one per UE data flow).

[0055] The accompanying drawings incorporated herein and forming part of the specification illustrate, along with descriptions, various embodiments of the disclosure, and further explain the principles of the disclosure, and serve to enable those skilled in the art to manufacture and use the embodiments disclosed herein. In the drawings, similar reference numerals indicate equivalent or functionally similar elements. [Brief explanation of the drawing]

[0056] [Figure 1] This is a schematic block diagram illustrating a typical on-network functionality model for SEAL. [Figure 2] This is a schematic block diagram showing the on-network functionality model of SEAL for DD. [Figure 3] A schematic block diagram illustrating an exemplary architecture for SEAL application traffic forwarding. [Figure 4] This is a schematic signaling chart showing messages in the SEALDD enabled data transmission quality measurement procedure according to embodiments of this specification. [Figure 5]This is a schematic flowchart illustrating an exemplary method in the first network function according to embodiments of this specification. [Figure 6] This is a schematic flowchart illustrating an exemplary method in a second network function according to embodiments of this specification. [Figure 7] This is a schematic block diagram illustrating an exemplary first network function according to embodiments of this specification. [Figure 8] This is a schematic block diagram illustrating an exemplary second network function according to embodiments of this specification. [Figure 9] This is a schematic block diagram showing an exemplary computer implementation according to the embodiments of this specification. [Modes for carrying out the invention]

[0057] Embodiments of this specification are described below in detail with reference to the accompanying drawings illustrating these embodiments. However, these embodiments of this specification may be embodied in many different forms and should not be construed as being limited to the embodiments described herein. The elements of the drawings are not necessarily to a constant scale relative to one another.

[0058] A reference to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in relation to that embodiment is included in at least one embodiment. Therefore, the phrase "in one embodiment" appearing in various places throughout this specification does not necessarily refer to the same embodiment.

[0059] As used herein, the terms “A, B, or C” mean “A” or “B” or “C,” the terms “A, B, and C” as used herein mean “A” and “B” and “C,” and the terms “A, B, and / or C” as used herein mean “A,” “B,” “C,” “A and B,” “A and C,” “B and C,” or “A, B, and C.”

[0060] Currently, SEALDD data transmission quality measurement supports only a single UE per subscription, where, for example, the UE ID or address is provided in the SEALDD transmission quality measurement subscription request. When a single UE is not provided, for example, the UE ID or address is not provided in the SEALDD transmission quality measurement subscription request, it is unclear how the measurement will be performed by the SEALDD server (whether all UEs will be measured, or whether random UEs will be measured).

[0061] To avoid non-deterministic measurements, the embodiment proposes a solution for supporting all UEs as measurement targets and for supporting transmission quality measurement reporting for groups or multiple VALUEs.

[0062] The embodiment can be implemented in the architecture for the SEAL data distribution service shown in Figures 2 and 3.

[0063] In one embodiment, architecture 200 may be configured in an OTT scenario. The OTT connection may be transparent in the sense that the participating communication devices through which the OTT connection passes are unaware of the routing of uplink and downlink communications. For example, a base station may not be aware of, or does not need to be aware of, the past routing of incoming downlink communications with data originating from one or more VAL servers 111 or one or more SEALDD servers 212 that are to be forwarded (e.g., handed over) to the connected UE 201. Similarly, the base station does not need to be aware of the future routing of outgoing uplink communications originating from the UE 201 and destined for one or more VAL servers 111 or one or more SEALDD servers 212.

[0064] It should also be understood that network functionality can be implemented as network elements on dedicated hardware, as software instances running on dedicated hardware, or as virtualized functionality instantiated on an appropriate platform, such as a cloud infrastructure.

[0065] As used herein, UE101 or 201 refers to a device that is capable of, configured, and / or operational for wireless communication with network nodes and / or other UEs. Examples of UE101 or 201 include, but are not limited to, smartphones, mobile phones, cell phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptop computers, laptop embedded equipment (LEE), laptop mounted equipment (LME), smart devices, wireless customer premises equipment (CPE), vehicle-mounted or vehicle-embedded / integrated wireless devices, etc. Other examples include any UE identified by the Third Generation Partnership Project (3GPP), including narrowband Internet of Things (NB-IoT) UEs, machine-type communications (MTC) UEs, and / or enhanced MTC (eMTC) UEs.

[0066] UE101 or 201 may support D2D (device-to-device) communication by implementing 3GPP standards for sidelink communication, dedicated short-range communication (DSRC), V2V (Vehicle-to-Vehicle), V2I (Vehicle-to-Infrastructure), or V2X (Vehicle-to-Everything), for example. In other examples, UE101 or 201 does not necessarily have a user in the sense of a human user who owns and / or operates the associated device. Instead, UE101 or 201 may represent a device (e.g., a smart sprinkler controller) that is intended to be sold to or operated by a human user, but may not be associated with a particular human user, or may not be associated with a particular human user in the first place. Alternatively, UE101 or 201 may represent a device (e.g., a smart power meter) that is not intended to be sold to or operated by an end user, but may be associated with or operate for the benefit of a user.

[0067] While a 3GPP network system 102 is used as an example herein, it should be noted that embodiments herein may also be applicable to (one or more) non-3GPP networks. In that sense, the network system 102 may be configured to operate according to predefined rules or procedures, including, but not limited to, any other suitable wireless communication standards, such as GSM (Global System for Mobile Communications), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future-generation standard (e.g., 6G), wireless local area network (WLAN) standards such as the IEEE 802.11 standard (WiFi), and / or any other suitable wireless communication standards such as global interoperability for microwave access (WiMAX), Bluetooth, Z-Wave, near-field communications (NFC) ZigBee, LiFi, and / or LoRa and Sigfox, or any low-power wide area network (LPWAN) standards.

[0068] Figure 4 is a schematic signaling chart showing messages in a SEALDD-enabled data transmission quality measurement procedure according to an embodiment of this specification. The SEALDD client 222 and SEALDD server 212 can be improved by performing data transmission quality measurement.

[0069] Before executing the data transmission quality measurement procedure, the SEALDD server 212 and SEALDD client 222 may be synchronized to a time source provided by 5GS as specified in 3GPP TS23.501, and the VAL server 111 may discover and select the SEALDD server 212 by the Common API Framework (CAPIF) function.

[0070] In one embodiment, the signaling chart in Figure 4 may include the following messages or steps:

[0071] Step 1. An ongoing normal data transmission connection may be established in accordance with Section 9.2.2.2 of 3GPP TS23.433.

[0072] Step 2. The VAL server 111 may send a SEALDD transmit quality measurement subscription request to the SEALDD server 212. The request may include an application traffic identifier (e.g., VAL service ID, VAL server ID), the requirements for the transmit quality measurement (e.g., latency, bitrate, packet loss rate), the target UE for measurement (a single UE, a group of UEs, or all UEs), and may also include reporting frequency, spatial conditions, and temporal conditions.

[0073] For example, a group of VALUEs or VALUE groups may include multiple VALUEs that share the same VAL service and / or are located in the same geographical area.

[0074] Table 1 below describes the information flow from VAL server 111 to SEALDD server 212 for subscribing to the data transmission measurement service. TIFF2026509152000002.tif159170

[0075] As shown in Table 1, the information element "VALUE Group ID," which is a group identifier (ID) for a group of VALUEs, or the information element "VALUE All Instruction," which is an instruction for all VALUEs, may be provided in a subscription request for a report of transmission quality measurements for one or more VALUEs.

[0076] Furthermore, the information element "Reporting Frequency" may be provided in the subscription request to indicate whether the report should be periodic. If the report is set to periodic, the information element "Reporting Periodicity" may be provided in the subscription request to indicate the reporting periodicity.

[0077] Furthermore, the information element "Reporting Granularity" may be provided in the subscription request to indicate whether the report should be provided per UE or per aggregation of multiple UEs. Reporting Granularity may indicate whether the requested report is for a specific VALUE, for individual VALUEs among multiple VALUEs, for a group of VALUEs, or for all VALUEs.

[0078] Furthermore, the information element "measurement conditions" may be provided in the subscription request to specify one or more spatial conditions and / or one or more temporal conditions for measurement. If one or more conditions are not met, the SEALDD server 212 may stop or interrupt the transmission quality measurement.

[0079] In one example, the VAL server 111 may send a measurement request to the SEALDD server 212 that includes a geographical area or a scheduled route (spatial condition), and / or a start-stop time with arbitrary time periodicity (temporal condition).

[0080] For example, measurements are expected to be taken daily from 9:00 a.m. to 6:00 p.m. for (one or more) VAL UE201 located in a park or on campus.

[0081] In another example, measurements are expected to be taken for (one or more) VAL UE201 (e.g., a group of V2X UEs) along a scheduled route (from city A to city B via highways A2 and A3) until September 2025, on Tuesdays from 9:00 a.m. to 11:00 a.m. and Thursdays from 1:00 p.m. to 5:00 p.m.

[0082] Step 3. Upon receiving the request, the SEALDD server 212 may perform an authorization check. If the authorization check is successful, the SEALDD server 212 may send a response to the VAL server 111 containing the subscription ID and expiration time.

[0083] Table 2 below describes the information flow from SEALDD server 212 to VAL server 111 in response to a transmission quality measurement subscription request. TIFF2026509152000003.tif37170

[0084] Step 4. Based on the request from the VAL server 111 in Step 2, the SEALDD server 212 may initiate a downlink (DL) packet delay measurement. The SEALDD server 212 may encapsulate DL monitoring packets (i.e., DL SEALDD packets with a SEALDD DL monitoring header and VAL traffic as payload, or dummy DL SEALDD packets generated for data transmission quality monitoring) along with the local time T1 at which the SEALDD server 212 sends the DL monitoring packets. The SEALDD server 212 may consider spatial and / or temporal conditions when initiating / restarting the transmission quality measurement. If those conditions are not met, the SEALDD server 212 may stop / suspend the transmission quality measurement.

[0085] Step 5. SEALDD client 222 may receive DL monitoring packets and record local time T2. Note that dummy packets are not sent to VAL client 222.

[0086] Step 6. Similarly, SEALDD client 222 may encapsulate uplink (UL) monitoring packets (i.e., UL SEALDD packets with a SEALDD UL monitoring header and VAL traffic as payload, or dummy UL SEALDD packets generated for data transmission quality monitoring) along with the local time T2 when SEALDD client 222 receives the DL monitoring packets and the local time T3 when SEALDD client 222 sends out the UL monitoring packets.

[0087] Step 7. The SEALDD server 212 may record local time T4, during which the SEALDD server 212 receives UL monitoring packets and calculates packet delays along with T1, T2, T3, and T4. The SEALDD server 212 may also calculate bitrate and packet loss rate over a period of time via a particular SEALDD connection by recording the status of SEALDD packets carrying VAL traffic or dummy SEALDD packets generated for transmission quality measurement reports.

[0088] Step 8. The SEALDD server 212 may report the data transmission quality measurement results (e.g., packet delay, bitrate, packet error rate) to the VAL server 111 via a notification message.

[0089] When a group or all VALUE instruction is received in step 2, steps 4 to 7 may be repeated for the VALUEs in the group or for all VALUEs. The SEALDD server 212 may identify the SEALDD connection corresponding to the desired VALUE 201 (one or more) to trigger a measurement. Also, depending on the reporting requirements for multiple VALUE 201, the SEALDD server 212 may calculate the necessary reports for the VAL server 111. For example, the SEALDD server 212 may aggregate one or more transmit quality measurement results to form an aggregated transmit quality measurement result (such as average measurement, minimum measurement, and maximum measurement).

[0090] Table 3 below describes the information flow from SEALDD server 212 to VAL server 111 for notifying transmission quality measurement reports. TIFF2026509152000004.tif118170

[0091] When the measurement target is for a group of UEs or all UEs, the report may be per UE or an aggregation (e.g., average measurement, maximum measurement) for the group or all UEs, depending on the reporting requirements. As shown in Table 3, the information element "(one or more) VAL UE ID" may be provided in the notification to indicate whether the transmission quality measurement and / or report is per UE or an aggregation for multiple UEs.

[0092] If the information element "Reporting Granularity" in a subscription request is set for a specific VALUE, or for individual VALUEs among multiple VALUEs, then the transmission quality measurement for one or more VALUEs may be a transmission quality measurement for a specific VALUE or for individual VALUEs.

[0093] If the "Reporting Granularity" information element in a subscription request is set for multiple UEs, the transmission quality metric for one or more VALUEs may be an aggregation of transmission quality metrics for a group of VALUEs or for all VALUEs.

[0094] For example, in the case of a group of vehicles, the average transmission quality measurement for those vehicles may be used for re-selection by the SEALDD server 212. As shown in Table 3, the information element “Average Measurement” may be provided in a notification to indicate the average measurement of multiple transmission quality measurements for a group of VALUEs or for all VALUEs.

[0095] In the data transmission quality measurement procedure shown in Figure 4, embodiments herein may support multiple VALUEs in a SEALDD data transmission quality measurement subscription and support different reporting formats (e.g., average values) for multiple VALUEs. As a result, QoS measurement at the SEALDD layer may be improved to support multiple VALUEs in a single subscription, otherwise the VAL server would need to send many subscription requests (one for each UE data flow).

[0096] Figure 5 is a schematic flowchart illustrating an exemplary method 500 in the first network function according to embodiments of this specification. In one embodiment, the flowchart in Figure 5 may be implemented in the VAL server 111 in Figures 1 to 4.

[0097] Method 500 may begin with step S501, in which a first network function (such as VAL server 111) may send a subscription message to a second network function implementing a SEALDD server (such as SEALDD server 212) to request a report of transmission quality measurements for one or more VALUEs. The subscription message may include a first parameter indicating a group of VALUEs, or all VALUEs, as the measurement target VALUE. Optionally, all VALUEs may have established a SEALDD connection with the second network function.

[0098] In one embodiment, the first parameter may include a group identifier (ID) for a group of VALUEs, or an instruction to refer to all of the VALUEs.

[0099] In one embodiment, a group of VALUEs may include multiple VALUEs that share the same VAL service and / or are located in the same geographical area.

[0100] In one embodiment, the subscription message may further include a second parameter indicating the reporting periodicity if the reporting is set to periodic reporting.

[0101] In one embodiment, the subscription message may further include a third parameter indicating the reporting granularity.

[0102] In one embodiment, the reporting granularity may indicate whether the requested report is about a specific VALUE, about an individual VALUE among several VALUEs, about a group of VALUEs, or about all VALUEs.

[0103] In one embodiment, the subscription message may further include a fourth parameter that specifies one or more measurement conditions for transmission quality measurement.

[0104] In one embodiment, one or more measurement conditions may include one or more spatial conditions and / or one or more temporal conditions.

[0105] In one embodiment, if one or more conditions are not met, the SEALDD server may stop or interrupt the transmission quality measurement.

[0106] In one embodiment, the subscription message may be a SEALDD-enabled data transmission quality measurement subscription request.

[0107] In one embodiment, the transmission quality measurement may be a measurement relating to latency, bitrate, or packet loss rate.

[0108] Method 500 may then proceed to step S502, in which a first network function (such as VAL server 111) may receive a notification message from a second network function to provide a report on the transmission quality measurement.

[0109] In one embodiment, the notification message may further include a fifth parameter indicating one or more VALUEs, on which the transmission quality is measured and / or a report of the transmission quality measurement is provided.

[0110] In one embodiment, if the third parameter is set to a specific VALUE or to an individual VALUE among several VALUEs, the transmission quality measurement for one or more VALUEs may be a transmission quality measurement for a specific VALUE or an individual VALUE.

[0111] In one embodiment, if the third parameter is set for multiple VALUEs, the transmission quality measurement for one or more VALUEs may be an aggregation of transmission quality measurements for a group of VALUEs or for all VALUEs.

[0112] In one embodiment, the notification message may further include a sixth parameter indicating the average measurement of multiple transmission quality measurements for a group of VALUEs or all of VALUEs.

[0113] In one embodiment, the notification message may be a SEALDD-enabled data transmission quality measurement notification.

[0114] The steps described above are merely examples, and the first network function may perform any related actions as described with respect to Figures 1 to 4.

[0115] Figure 6 is a schematic flowchart illustrating an exemplary method 600 in a second network function according to embodiments of this specification. In one embodiment, the flowchart in Figure 6 may be implemented in the SEALDD server 212 in Figures 2 to 4.

[0116] Method 600 may begin with step S601, in which a second network function (such as SEALDD server 212) may receive a subscription message from a first network function implementing a VAL server (such as VAL server 111) to request a report of transmission quality measurements for one or more VAL UEs. The subscription message may include a first parameter indicating a group of VAL UEs, or all VAL UEs, as the measurement target VAL UE. Optionally, all VAL UEs may have established a SEALDD connection with the second network function.

[0117] In one embodiment, the first parameter may include a group ID for a group of VALUEs, or an instruction to indicate all VALUEs.

[0118] In one embodiment, a group of VALUEs may include multiple VALUEs that share the same VAL service and / or are located in the same geographical area.

[0119] In one embodiment, the subscription message may further include a second parameter indicating the reporting periodicity if the reporting is set to periodic reporting.

[0120] In one embodiment, the subscription message may further include a third parameter indicating the reporting granularity.

[0121] In one embodiment, the reporting granularity may indicate whether the requested report is about a specific VALUE, about an individual VALUE among several VALUEs, about a group of VALUEs, or about all VALUEs.

[0122] In one embodiment, the subscription message may further include a fourth parameter that specifies one or more measurement conditions for transmission quality measurement.

[0123] In one embodiment, one or more measurement conditions may include one or more spatial conditions and / or one or more temporal conditions.

[0124] In one embodiment, if one or more conditions are not met, the SEALDD server may stop or interrupt the transmission quality measurement.

[0125] In one embodiment, the subscription message may be a SEALDD-enabled data transmission quality measurement subscription request.

[0126] In one embodiment, the transmission quality measurement may be a measurement relating to latency, bitrate, or packet loss rate.

[0127] In one embodiment, after receiving a subscription message, a second network function (such as SEALDD server 212) may identify the SEALDD connection corresponding to the measurement target VALUE in order to trigger a measurement.

[0128] Method 600 may then proceed to step S602, in which a second network function (such as the SEALDD server 212) may perform a transmission quality measurement.

[0129] In one embodiment, the second network function may repeatedly perform the steps of: performing a transmit quality measurement to obtain one or more measurements for each of a group of VALUEs or all of VALUEs; and generating one or more transmit quality measurement reports based on the one or more measurements.

[0130] In one embodiment, the method may further include the step of aggregating one or more transmit quality measurement reports to form an aggregated transmit quality measurement report.

[0131] Method 600 may then proceed to step S603, in which a second network function (such as SEALDD server 212) may send a notification message to the first network function to provide a report on the transmission quality measurement.

[0132] In one embodiment, the notification message may further include a fifth parameter indicating one or more VALUEs, on which the transmission quality is measured and / or a report of the transmission quality measurement is provided.

[0133] In one embodiment, if the third parameter is set to a specific VALUE or to an individual VALUE among several VALUEs, the transmission quality measurement for one or more VALUEs may be a transmission quality measurement for a specific VALUE or an individual VALUE.

[0134] In one embodiment, if the third parameter is set for multiple VALUEs, the transmission quality measurement for one or more VALUEs may be an aggregation of transmission quality measurements for a group of VALUEs or for all VALUEs.

[0135] In one embodiment, the notification message may further include a sixth parameter indicating the average measurement of multiple transmission quality measurements for a group of VALUEs or all of VALUEs.

[0136] In one embodiment, the notification message may be a SEALDD-enabled data transmission quality measurement notification.

[0137] The steps described above are merely examples, and the second network function may perform any related actions as described with respect to Figures 2 to 4.

[0138] Figure 7 is a schematic block diagram showing an exemplary first network function 700 according to an embodiment of this specification. In one embodiment, the exemplary first network function 700 in Figure 7 may be implemented as the VAL server 111 in Figures 1 to 4.

[0139] In one embodiment, the first network function 700 may include at least one processor 701 and a non-temporary computer-readable medium 702 coupled to the at least one processor 701. The non-temporary computer-readable medium 702 may store instructions executable by the at least one processor 701, thereby configuring the at least one processor 701 to perform steps in the exemplary method 500 shown in the schematic flowchart of Figure 5, details of which are omitted here.

[0140] It should be noted that the first network function 700 can be implemented as hardware, software, firmware, or any combination thereof. For example, the first network function 700 may include a plurality of units, circuits, modules, etc., each of which may be used to perform one or more steps of the exemplary method 500, or one or more steps shown in Figures 1 to 4 relating to the first network function (such as the VAL server 111).

[0141] Figure 8 is a schematic block diagram showing an exemplary second network function 800 according to embodiments of this specification. In one embodiment, the exemplary second network function 800 in Figure 8 may be implemented as the SEALDD server 212 in Figures 2 to 4.

[0142] In one embodiment, the second network function 800 may include at least one processor 801 and a non-temporary computer-readable medium 802 coupled to the at least one processor 801. The non-temporary computer-readable medium 802 may store instructions executable by the at least one processor 801, thereby configuring the at least one processor 801 to perform steps in the exemplary method 600 shown in the schematic flowchart of Figure 6, details of which are omitted here.

[0143] It should be noted that the second network function 800 may be implemented as hardware, software, firmware, or any combination thereof. For example, the second network function 800 may include multiple units, circuits, modules, etc., each of which may be used to perform one or more steps of the exemplary method 600, or one or more steps shown in Figures 2 to 4 relating to the second network function (such as the SEALDD server 212).

[0144] Figure 9 is a schematic block diagram showing an exemplary computer implementation device 900 according to embodiments of this specification. In one embodiment, the device 900 may be configured as the above-described devices, such as UE101 or a functional component of UE101 (such as one or more VAL clients 121 and / or one or more SEAL clients 122), UE201 or a functional component of UE201 (such as one or more VAL clients 121 and / or one or more SEALDD clients 222), a first network function (such as one or more VAL servers 111), or a second network function (such as a SEALDD server 212).

[0145] In one embodiment, the device 900 may include, but is not limited to, at least one processor, such as a central processing unit (CPU) 901, a computer-readable medium 902, and a memory 903. The memory 903 may comprise volatile memory (e.g., random access memory, RAM) and / or non-volatile memory (e.g., a hard disk or flash memory). In one embodiment, the computer-readable medium 902 may be configured to store computer programs and / or instructions that, when executed by the processor 901, cause the processor 901 to perform any of the methods described above.

[0146] In one embodiment, a computer-readable medium 902 (such as a non-temporary computer-readable medium) may be stored in memory 903. In another embodiment, a computer program may be stored in a remote location, for example, a computer program product 904 (which may also be embodied as a computer-readable medium), and accessible by the processor 901 via, for example, a carrier 905.

[0147] Computer-readable media 902 and / or computer program products 904 may be distributed and / or stored on removable computer-readable media, such as diskettes, CDs (Compact Discs), DVDs (Digital Video Discs), flash or similar removable memory media (e.g., CompactFlash, SD (Secure Digital), Memory Stick, MiniSD Card, MMC Multimedia Card, SmartMedia), HD-DVDs (High Definition DVDs), or Blu-ray DVDs, USB (Universal Serial Bus) based removable memory media, magnetic tape media, optical storage media, magneto-optical media, bubble memory, or distributed as propagating signals over a network (e.g., Ethernet, ATM, ISDN, PSTN, X.25, the Internet, a local area network (LAN), or similar networks capable of transporting data packets to infrastructure nodes).

[0148] Furthermore, the following amendments are proposed to correct the current 3GPP technical report 3GPP TS23.433 v1.1.0(2023-01).

[0149] Title: SEALDD QoS Measurement for Multiple UEs Introduction: This pCR adds support for multiple UEs in SEALDD QoS measurements.

[0150] Reason for the change: The current SEALDD data transmission quality measurement supports a single UE. It is unclear how the measurement will be performed by the SEALDD server when a single UE is not provided (whether all UEs will be measured, or whether random UEs will be measured).

[0151] To avoid non-deterministic measurements, it is proposed to support all UEs as measurement targets. Furthermore, it should be possible to obtain transmission quality measurement reports for groups of UEs.

[0152] When the measurement target is for a group of UEs or all UEs, the report may be per UE or an aggregation (e.g., average measurement, maximum measurement) for the group or all UEs, depending on the reporting requirements.

[0153] Proposed changes: ***First Change*** (The proposed changes include content to be added to 3GPP TS23.433 v1.1.0(2023-01) (indicated by underlining) and content to be removed from 3GPP TS23.433 v1.1.0(2023-01) (indicated by strikethrough)) 9.7.2.1 Data Transmission Quality Measurement The diagram (see Figure 4) illustrates the procedure for measuring data transmission quality with SEALDD enabled. The SEALDD client and SEALDD server are configured to perform data transmission quality measurement.

[0154] Prerequisites: 1. The SEALDD server and SEALDD client are synchronized to a time source provided by 5GS as specified in 3GPP TS23.501[5]. 2. The VAL server discovers and selects the SEALDD server using the CAPIF function.

[0155] Figure (see Figure 4): SEALDD Enabled Data Transmission Quality Measurement Procedure 1. An ongoing normal data transmission connection is established in accordance with Section 9.2.2.2. 2. The VAL server sends a SEALDD transmit quality measurement subscription request to the SEALDD server. This request includes an application traffic identifier (e.g., VAL service ID, VAL server ID) and the requirements for transmit quality measurement (e.g., latency, bitrate, packet loss rate). Measurement target UE (single UE, group of UEs, or all UEs) and TIFF2026509152000005.tif7170 may also include reporting frequency, spatial conditions, and temporal conditions. 3. Upon receiving a request, the SEALDD server performs an authorization check. If authorization is successful, the SEALDD server sends a response to the VAL server containing the subscription ID and expiration time. 4. Based on the request from the VAL server in step 2, the SEALDD server initiates DL packet delay measurement. The SEALDD server encapsulates the DL monitoring packet (i.e., a DL SEALDD packet with a SEALDD DL monitoring header and VAL traffic as the payload, or a dummy DL SEALDD packet generated for data transmission quality monitoring) along with the local time T1 when the SEALDD server sends out the DL monitoring packet. The SEALDD server considers spatial and / or temporal conditions when starting / restarting transmit quality measurements. If those conditions are not met, the SEALDD server stops / suspends the transmit quality measurement. 5. The SEALDD client receives the DL monitoring packet and records local time T2.

[0156] Note: Dummy packets are not sent to the VAL client.

[0157] 6. Similarly, the SEALDD client encapsulates the UL monitoring packet (i.e., a UL SEALDD packet with a SEALDD UL monitoring header and VAL traffic as the payload, or a dummy UL SEALDD packet generated for data transmission quality monitoring) along with the local time T2 at which the SEALDD client receives the DL monitoring packet and the local time T3 at which the SEALDD client sends out the UL monitoring packet. 7. The SEALDD server records local time T4, during which the SEALDD server receives UL monitoring packets and calculates packet delays along with T1, T2, T3, and T4. The SEALDD server can also calculate the bitrate and packet loss rate over a period of time through a particular SEALDD connection by recording the status of SEALDD packets carrying VAL traffic or dummy SEALDD packets generated for transmission quality measurement reports. 8. The SEALDD server reports the data transmission quality measurement results (e.g., packet delay, bitrate, packet error rate) to the VAL server via a notification message.

[0158] When a group or all VALUE instruction is received in step 2, steps 4 through 7 are repeated for the VALUEs in the group or for all VALUEs. The SEALDD server identifies the SEALDD connection corresponding to the desired VALUEs (one or more) to trigger the measurement. Also, depending on the reporting requirements for multiple UEs, the SEALDD server calculates the necessary reports for the VALUE server.

[0159] Editor's Note: Whether and how the SEALDD server can provide the relevant APIs to allow other consumers (e.g., VAL server, SEALDD server, NSCE server, etc.) to query measurement results is FFS.

[0160] ***Second Change*** (The proposed changes include content (indicated by underlining) that should be added to 3GPP TS23.433 v1.1.0 (2023-01)) 9.7.3.1 SEALDD Enabled Data Transmission Quality Measurement Subscription Request

[0161] Table 9.7.3.1-1 describes the information flow from the VAL server to the SEALDD server for subscribing to the data transmission measurement service. TIFF2026509152000006.tif159170

[0162] ***Third Change*** (The proposed changes include content to be added to 3GPP TS23.433 v1.1.0(2023-01) (indicated by underlining) and content to be removed from 3GPP TS23.433 v1.1.0(2023-01) (indicated by strikethrough)) 9.7.3.2 SEALDD Enabled Data Transmission Quality Measurement Subscription Response Table 9.7.3.2-1 describes the information flow from the SEALDD server to the VAL server in response to a transmission quality measurement subscription request. TIFF2026509152000007.tif37170

[0163] ***Fourth Change*** (The proposed changes include content to be added to 3GPP TS23.433 v1.1.0(2023-01) (indicated by underlining) and content to be removed from 3GPP TS23.433 v1.1.0(2023-01) (indicated by strikethrough)) 9.7.3.3 SEALDD Enabled Data Transmission Quality Measurement Notification Table 9.7.3.3-1 describes the information flow from the SEALDD server to the VAL server for notifying the transmission quality measurement report. TIFF2026509152000008.tif184170***End of Change***

[0164] Exemplary embodiments have been described herein with reference to block diagrams and / or flowchart examples of computer implementation methods, apparatus (systems and / or devices) and / or non-temporary computer program products. It should be understood that blocks in block diagrams and / or flowchart examples, and combinations of blocks in block diagrams and / or flowchart examples, can be implemented by computer program instructions executed by one or more computer circuits. These computer program instructions may be provided to processor circuits of general-purpose computer circuits, dedicated computer circuits and / or other programmable data processing circuits for creating machines, and so the instructions executed via the processor of a computer and / or other programmable data processing device convert and control transistors, values ​​stored in memory locations, and other hardware components in such circuits in order to implement functions / actions specified in one or more blocks of block diagrams and / or flowcharts, and thereby to create means (functions) and / or structures for implementing functions / actions specified in (one or more) blocks of block diagrams and / or flowcharts.

[0165] These computer program instructions may also be stored in a tangible computer-readable medium that can guide a computer or other programmable data processing device to function in a particular manner, and so the instructions stored in the computer-readable medium may produce a product containing instructions that implement functions / actions specified in one or more blocks of a block diagram and / or flowchart. Thus, embodiments of the concept of the present invention may be embodied in hardware and / or in software (including firmware, resident software, microcode, etc.) running on a processor such as a digital signal processor, which may be collectively referred to as “circuits,” “modules” or variations thereof.

[0166] Furthermore, it should be noted that in some alternative implementations, the functions / actions mentioned in a block may be performed in a different order than those mentioned in the flowchart. For example, depending on the functions / actions involved, two consecutively shown blocks may be executed effectively and substantially concurrently, or blocks may sometimes be executed in reverse order. Moreover, the functions of a given block in a flowchart and / or block diagram may be separated into multiple blocks, and / or the functions of two or more blocks in a flowchart and / or block diagram may be integrated, at least partially. Finally, other blocks may be added / inserted between the shown blocks, and / or blocks / actions may be omitted without deviating from the scope of the inventive concept. Furthermore, while some of the diagrams include arrows on the communication path to indicate the main direction of communication, it should be understood that communication may occur in the opposite direction to the illustrated arrows.

[0167] Many variations and modifications can be made to the embodiments without substantially departing from the principles of the conceptual idea of ​​the present invention. All such variations and modifications are included herein within the scope of the conceptual idea of ​​the present invention. Accordingly, the subject matter disclosed above should be considered illustrative and not limiting, and the accompanying examples of embodiments should cover all such modifications, extensions, and other embodiments that fall within the spirit and scope of the conceptual idea of ​​the present invention. Accordingly, to the maximum extent permitted by law, the scope of the conceptual idea of ​​the present invention should be determined by the broadest permissible interpretation of this disclosure, including subsequent examples of embodiments and their equivalents, and should not be limited or restricted by the detailed description above.

[0168] Abbreviation 3GPP Third Generation Partnership Project API Application Programming Interface DD Data Distribution DL Downlink OTT Over the Top QoS (Quality of Service) Service Enablement Architecture Layer for SEAL Vertical SEALDD SEAL Data Distribution UE User Equipment UP Uplink V2X vehicle to Everything VAL Vertical Application Layer

Claims

1. A method (500) performed by a first network function (111, 700) that implements a Vertical Application Layer (VAL) server, - Sending a subscription message to a second network function (212, 800) implementing a Service Enabler Architecture Layer (SEAL) Data Distribution (DD) server to request a report of transmission quality measurements for one or more VAL user devices (UEs) (201) (S501), wherein the subscription message includes a first parameter that indicates a group of VAL UEs (201) or all of the VAL UEs (201) as the measurement target VAL UE (S501), - Receiving a notification message from the second network function (212, 800) to provide the report of the transmission quality measurement (S502) Method (500), including the method (500).

2. The method according to claim 1 (500), wherein the first parameter includes a group identifier (ID) of the group of VALUE(201), or an instruction for indicating all of the VALUE(201).

3. The method (500) according to claim 1 or 2, wherein the group of VALUE(201) includes a plurality of VALUE(201) that share the same VAL service and / or are located in the same geographic area.

4. The method according to any one of claims 1 to 3 (500), wherein the subscription message further includes a second parameter indicating reporting periodicity if the report is set to periodic reporting.

5. The subscription message further includes a third parameter indicating the reporting granularity, The aforementioned reporting granularity indicates whether the requested report pertains to a specific VALUE(201), to individual VALUE(201) from a group of VALUE(201), to a group of VALUE(201), or to all of the VALUE(201). The method according to any one of claims 1 to 4 (500).

6. The method according to any one of claims 1 to 5 (500), wherein the subscription message further includes a fourth parameter indicating one or more measurement conditions for the transmission quality measurement.

7. The one or more measurement conditions include one or more spatial conditions and / or one or more temporal conditions, and / or If one or more of the above conditions are not met, the SEALDD server stops or interrupts the transmission quality measurement. The method according to claim 6 (500).

8. The method according to any one of claims 1 to 7 (500), wherein the notification message further includes a fifth parameter indicating one or more VALUE(201) on which the transmission quality is measured and / or a report of the transmission quality measurement is provided.

9. The method according to claim 8 (500), wherein when the third parameter is set to a specific VALUE(201) or to individual VALUE(201) among a plurality of VALUE(201), the transmission quality measurement for one or more VALUE(201) is a transmission quality measurement for the specific VALUE(201) or the individual VALUE(201), and when the third parameter is set to a plurality of VALUE(201), the transmission quality measurement for one or more VALUE(201) is an aggregation of transmission quality measurements for the group of VALUE(201) or all of the VALUE(201).

10. The method according to any one of claims 1 to 9 (500), wherein the notification message further includes a sixth parameter indicating an average measurement of a plurality of transmission quality measurements for the group of VALUE(201) or all of the VALUE(201).

11. The aforementioned subscription message is a SEALDD-enabled data transmission quality measurement subscription request, The notification message is a SEALDD-enabled data transmission quality measurement notification, and / or The aforementioned transmission quality measurement is a measurement relating to one of the following: latency, bitrate, or packet loss rate. The method according to any one of claims 1 to 10 (500).

12. A method (600) performed by a second network function (212, 800) that implements a Service Enabler Architecture Layer (SEAL) Data Distribution (DD) server, - Receiving a subscription message from a first network function (111, 700) implementing a Vertical Application Layer (VAL) server to request a report of transmission quality measurement for one or more VAL user devices (UEs) (201) (S601), wherein the subscription message includes a first parameter indicating a group of VAL UEs (201) or all of the VAL UEs (201) as the measurement target VAL UE (S601), - Send a notification message to the first network function (111, 700) to provide the report of the transmission quality measurement (S603) Method (600), including.

13. After receiving the aforementioned subscription message, and before sending the aforementioned notification message, To trigger the measurement, identify the SEALDD connection corresponding to the measurement target VALUE. The method according to claim 12, further comprising (600).

14. The method according to claim 12 or 13 (600), wherein the first parameter includes a group identifier (ID) of the group of VALUE(201), or an instruction for indicating all of the VALUE(201).

15. The method (600) according to any one of claims 12 to 14, wherein the group of VALUE(201) includes a plurality of VALUE(201) that share the same VAL service and / or are located in the same geographic area.

16. The method according to any one of claims 12 to 15 (600), wherein the subscription message further includes a second parameter indicating reporting periodicity if the report is set to periodic reporting.

17. The subscription message further includes a third parameter indicating the reporting granularity, The aforementioned reporting granularity indicates whether the requested report pertains to a specific VALUE(201), to individual VALUE(201) from a group of VALUE(201), to a group of VALUE(201), or to all of the VALUE(201). The method according to any one of claims 12 to 16 (600).

18. The method according to any one of claims 12 to 17 (600), wherein the subscription message further includes a fourth parameter indicating one or more measurement conditions for the transmission quality measurement.

19. The one or more measurement conditions include one or more spatial conditions and / or one or more temporal conditions, and / or If one or more of the above conditions are not met, the SEALDD server stops or interrupts the transmission quality measurement. The method according to claim 18 (600).

20. For each of the aforementioned group of VALUE(201) or all of the VALUE(201), - Performing the transmission quality measurement to obtain one or more measurement values ​​(S602), - To generate one or more transmission quality measurement reports based on the one or more measurements mentioned above. The method according to any one of claims 12 to 19, further comprising (600).

21. - Aggregating one or more transmission quality measurement reports to form an aggregated transmission quality measurement report. The method according to claim 20 (600), further comprising:

22. The method according to any one of claims 12 to 21 (600), wherein the notification message further includes a fifth parameter indicating one or more VALUE(201) on which the transmission quality is measured and / or a report of the transmission quality measurement is provided.

23. The method (600) of claim 22, wherein when the third parameter is set to a specific VALUE(201) or to individual VALUE(201) among a plurality of VALUE(201), the transmission quality measurement for one or more VALUE(201) is a transmission quality measurement for the specific VALUE(201) or the individual VALUE(201), and when the third parameter is set to a plurality of VALUE(201), the transmission quality measurement for one or more VALUE(201) is an aggregation of transmission quality measurements for the group of VALUE(201) or all of the VALUE(201).

24. The method (600) according to any one of claims 12 to 23, wherein the notification message further includes a sixth parameter indicating an average measurement of a plurality of transmission quality measurements for the group of VALUE(201) or all of the VALUE(201).

25. The aforementioned subscription message is a SEALDD-enabled data transmission quality measurement subscription request, The notification message is a SEALDD-enabled data transmission quality measurement notification, and / or The aforementioned transmission quality measurement is a measurement relating to one of the following: latency, bitrate, or packet loss rate. The method according to any one of claims 12 to 24 (600).

26. A first network function (700) that implements a Vertical Application Layer (VAL) server, At least one processor (701), A non-temporary computer-readable medium (702) coupled to at least one processor (701) and A first network function (700) comprising, wherein the non-temporary computer-readable medium (702) includes instructions executable by the at least one processor (701), thereby configuring the at least one processor (701) to perform the method (500) according to any one of claims 1 to 11.

27. A second network function (800) that implements a Service Enabler Architecture Layer (SEAL) Data Distribution (DD) server, At least one processor (801), A non-temporary computer-readable medium (802) coupled to at least one processor (801) and A second network function (800) comprising the non-temporary computer-readable medium (802) including instructions executable by the at least one processor (801), thereby configuring the at least one processor (801) to perform the method (600) according to any one of claims 12 to 25.

28. A computer-readable medium (902) comprising a computer-readable code that, when operated on the device (900), causes the device (900) to execute the method (500, 600) according to any one of claims 1 to 25.

29. A computer program product (904) comprising computer-readable code that, when operated on the device (900), causes the device (900) to execute the method (500, 600) according to any one of claims 1 to 25.

Images