PDU set monitoring

Abstract

Various examples provide an apparatus (120) comprising: means (11, 15) for receiving, from a first core network entity (131), one or more protocol data unit (PDU) sets for transmission by the apparatus to a user equipment (UE 110); means for determining, for the one or more PDU sets (202), that a PDU set is considered to be successfully or unsuccessfully transmitted from the apparatus to the UE, wherein the determining is based at least in part on a number of PDUs in the PDU set that have been successfully or unsuccessfully transmitted from the apparatus to the UE; means (11) for determining a number of the one or more PDU sets that are considered to be successfully or unsuccessfully transmitted; and means (11, 15) for sending, to a second core network entity (132) or the first core network entity, information indicating the number of the one or more PDU sets that are considered to be successfully or unsuccessfully transmitted.

Description

Technical Field

[0001] Examples of this disclosure relate to monitoring sets of Protocol Data Units (PDUs). Some examples relate to apparatus, methods, and computer programs for performing PDU set measurements (e.g., measuring one or more Quality of Service (QoS) parameters associated with the PDU set, such as PDU set loss rate (PSLR)) and reporting such measurements. Background Technology

[0002] Monitoring a set of PDUs (i.e., by measuring and reporting one or more Quality of Service (QoS) parameters associated with the set of PDUs transmitted via the Radio Access Network (RAN)) enables the determination of whether the QoS associated with the set of PDUs is met, and if not, enables remedial actions to be taken to meet the QoS associated with the set of PDUs.

[0003] The standard procedures for monitoring PDU sets are not always optimal. Similarly, the standard procedures for measuring and reporting QoS parameters associated with PDU sets are not always optimal.

[0004] In some cases, it may be desirable to provide an improved process for monitoring PDU sets. In other cases, it may be desirable to provide an improved process for measuring and reporting QoS parameters associated with PDU sets. Summary of the Invention

[0005] Based on various, but not necessarily all, examples provided in this disclosure are those claimed in the appended claims. Any examples and features described in this specification that do not fall within the scope of the independent claims should be interpreted as examples useful for understanding the various embodiments of the invention.

[0006] According to at least some examples of this disclosure, an apparatus is provided, comprising: A component for receiving one or more sets of Protocol Data Units (PDUs) from a first core network entity for transmission by the device to a User Equipment (UE); A component for determining, for one or more PDU sets, whether a PDU set is considered to have been successfully transmitted or unsuccessfully transmitted from the device to the UE, wherein the determination is based at least in part on the number of PDUs in the PDU set that have been successfully transmitted or unsuccessfully transmitted from the device to the UE; A component for determining the number of the one or more PDU sets considered to have been successfully transmitted or not successfully transmitted; and A component for sending information to a second core network entity or a first core network entity indicating the number of said one or more PDU sets that are considered to have been successfully transmitted or not successfully transmitted.

[0007] Based on various, but not necessarily all, examples of this disclosure, a method is provided, including: The device receives one or more sets of Protocol Data Units (PDUs) from a first core network entity for transmission to a User Equipment (UE). At the device, for one or more PDU sets, it is determined whether the PDU set is considered to have been successfully transmitted from the device or unsuccessfully transmitted to the UE, wherein the determination is based at least in part on the number of PDUs in the PDU set that have been successfully transmitted from the device or unsuccessfully transmitted to the UE; At the device, determine the number of one or more sets of PDUs that are considered to have been successfully or unsuccessfully transmitted; and The device sends information to the second core network entity or the first core network entity indicating the number of one or more PDU sets that are considered to have been successfully transmitted or not successfully transmitted.

[0008] Based on various, but not necessarily all, examples of this disclosure, a method is provided, including: The device receives one or more sets of Protocol Data Units (PDUs) from the User Equipment (UE) for transmission to the first core network entity. At the device, for one or more sets of PDUs, it is determined whether the set of PDUs is considered to have been successfully or unsuccessfully received from the UE at the device, wherein the determination is based at least in part on the number of PDUs in the set that have been successfully or unsuccessfully received from the UE at the device; The number of one or more PDU sets considered successfully received or unsuccessfully received is determined at the device; and The device sends information to the first core network entity or the second core network entity indicating the number of one or more PDU sets that are considered to have been successfully or unsuccessfully received from the UE at the device.

[0009] According to various, but not necessarily all, examples of this disclosure, a chipset is provided that includes processing circuitry configured to perform the methods described above.

[0010] According to various, but not all, examples of this disclosure, means, modules, circuits, devices, and / or systems are provided that include components for performing the methods described above.

[0011] According to various, but not necessarily all, examples of this disclosure, a computer program including instructions is provided that, when executed by a device, causes the device to perform the methods described above.

[0012] According to various, but not necessarily all, examples of this disclosure, an apparatus is provided, comprising: At least one processor; and At least one memory storing instructions that, when executed by at least one processor, cause the device to at least: Receive one or more sets of Protocol Data Units (PDUs) from the first core network entity for the device to transmit to the User Equipment (UE). For one or more PDU sets, determine whether the PDU set is considered to have been successfully transmitted or unsuccessfully transmitted from the device to the UE, wherein the determination is based at least in part on the number of PDUs in the PDU set that have been successfully transmitted or unsuccessfully transmitted from the device to the UE; Determine the number of one or more PDU sets that are considered to have been successfully or unsuccessfully transmitted; and Send information to the second core network entity or the first core network entity indicating the number of one or more PDU sets that are considered to have been successfully transmitted or not successfully transmitted.

[0013] According to various, but not necessarily all, examples of this disclosure, a non-transitory computer-readable medium encoded with instructions that, when executed by at least one processor, cause at least the following operations to be performed: At a device, one or more sets of Protocol Data Units (PDUs) are received from a first core network entity for the device to transmit to a User Equipment (UE). At the device, for one or more PDU sets, it is determined whether the PDU set is considered to have been successfully transmitted or unsuccessfully transmitted from the device to the UE, wherein the determination is based at least in part on the number of PDUs in the PDU set that have been successfully transmitted or unsuccessfully transmitted from the device to the UE; The number of one or more PDU sets considered to have been successfully or unsuccessfully transmitted is determined at the device; and The device sends information to the second core network entity or the first core network entity indicating the number of one or more PDU sets that are considered to have been successfully transmitted or not.

[0014] According to at least some examples of this disclosure, an apparatus is provided, comprising: A component for receiving configuration information from a first core network entity for reporting first information to a second core network entity, the first information indicating the number of one or more PDU sets that are considered to have been successfully or unsuccessfully transmitted to a user equipment (UE) by a radio access network (RAN) node; Components for receiving first information from the RAN node; and Components used to report first information to the second core network entity.

[0015] Based on various, but not necessarily all, examples of this disclosure, a method is provided, including: At a device, configuration information is received from a first core network entity for reporting first information to a second core network entity, the first information indicating the number of one or more PDU sets that are considered to have been successfully or unsuccessfully transmitted to the user equipment (UE) by the radio access network (RAN) node; The device receives the first information from the RAN node; and The device reports the first information to the second core network entity.

[0016] Based on various, but not necessarily all, examples of this disclosure, a method is provided, including: At a device, configuration information is received from a first core network entity for reporting first information to a second core network entity, the first information indicating the number of one or more PDU sets that are considered to have been successfully or unsuccessfully received by the radio access network (RAN) node from the user equipment (UE); The device receives the first information from the RAN node; and The device reports the first information to the second core network entity.

[0017] According to various, but not necessarily all, examples of this disclosure, a chipset is provided that includes processing circuitry configured to perform the methods described above.

[0018] According to various, but not all, examples of this disclosure, means, modules, circuits, devices, and / or systems are provided that include components for performing the methods described above.

[0019] According to various, but not necessarily all, examples of this disclosure, a computer program including instructions is provided that, when executed by a device, causes the device to perform the methods described above.

[0020] According to various, but not necessarily all, examples of this disclosure, an apparatus is provided, comprising: At least one processor; and At least one memory storing instructions that, when executed by at least one processor, cause the device to at least: Receive configuration information from the first core network entity for reporting first information to the second core network entity, the first information indicating the number of one or more PDU sets that are considered to have been successfully or unsuccessfully transmitted to the user equipment (UE) by the radio access network (RAN) node; Receive the first information from the RAN node; and Report the first information to the second core network entity.

[0021] According to various, but not necessarily all, examples of this disclosure, a non-transitory computer-readable medium encoded with instructions that, when executed by at least one processor, cause at least the following operations to be performed: At a device, configuration information is received from a first core network entity for reporting first information to a second core network entity, the first information indicating the number of one or more PDU sets that are considered to have been successfully or unsuccessfully transmitted to the user equipment (UE) by the radio access network (RAN) node; The device receives the first information from the RAN node; and The device reports the first information to the second core network entity.

[0022] The following sections of this “Summary of the Invention” describe various features, which, with necessary modifications, may be features of any of the examples described in the foregoing sections of this “Summary of the Invention”. The description of the function should also be considered as disclosing any components suitable for performing the function, or any instructions stored in at least one memory that, when executed by at least one processor, cause the device to perform the function.

[0023] In some, but not all, examples, the information indicating the number of one or more PDU sets considered successfully or unsuccessfully transmitted is based at least in part on the total number of one or more PDU sets to be transmitted to the UE, and the information indicates a ratio of the following: The number of one or more PDU sets that were considered to have been successfully or unsuccessfully transmitted, and The total number of one or more PDU sets to be transmitted by the device to the UE.

[0024] In some, but not all, examples, the information indicates a PDU set loss rate (PSLR) measurement, where the PSLR measurement indicates the ratio of PDU sets that were successfully transmitted or not successfully transmitted.

[0025] In some, but not all, examples, the determination of whether a set of PDUs is considered to have been successfully or unsuccessfully transmitted is based on whether the proportion of successfully transmitted PDUs in the set exceeds a threshold.

[0026] In some, but not all, examples, the device also includes a component for receiving configuration information from a second core network entity, which is used to configure the device to perform PSLR measurements.

[0027] In some, but not all, examples, the configuration information includes information for configuring the device to perform at least one or more of the following: Determine whether the PDU set is considered successfully transmitted or not. Determine the number of one or more PDU sets that are considered to have been successfully transmitted or not successfully transmitted; Send this information to the first or second core network entity.

[0028] In some, but not all, examples, the configuration information includes information indicating the entity to which the information should be sent; and the information is sent to that entity.

[0029] In some, but not all, examples, the configuration information includes an indication that the transmission of the information will be based on information determined by the device that a threshold has been exceeded; and the threshold is based at least in part on the number of one or more PDU sets that are considered to have been successfully or unsuccessfully transmitted.

[0030] In some, but not all, examples, the configuration information includes information indicating the threshold.

[0031] In some, but not necessarily all, examples, the configuration information includes information indicating a time interval; and the execution of at least one or more of the following is at least partially based on that time interval: Determine whether the PDU set is considered successfully transmitted or unsuccessfully transmitted, or Determine the number of one or more PDU sets that are considered to have been successfully transmitted or not.

[0032] In some, but not necessarily all, examples, the configuration information includes information indicating a first number of PDU sets; and wherein the execution of at least one or more of the following is at least partially based on the first number of PDU sets: Determine whether the PDU set is considered successfully transmitted or unsuccessfully transmitted, or Determine the number of one or more PDU sets that are considered to have been successfully transmitted or not.

[0033] In some, but not all, examples, the configuration information includes information indicating one or more metrics to be reported to the first or second core network entity.

[0034] In some, but not all, examples, the device also includes components for receiving configuration information from a second core network entity, the configuration information being used to configure the device to perform at least one or more of the following: For each of the multiple PDU sets to be transmitted from the device to the UE, determine: The total number of PDUs in each PDU set, and The number of PDUs in each PDU set that have been successfully or unsuccessfully transmitted to the UE by the device; Determine one or more metrics that indicate the transmission quality of the PDU set from the device to the UE, wherein the metrics are determined based at least in part on the following: The total number of PDUs in each PDU set, and The number of PDUs in each PDU set that have been successfully or unsuccessfully transmitted to the UE by the device.

[0035] According to various, but not necessarily all, embodiments, an apparatus is provided including components for performing at least a portion of one or more methods described herein. The description of functions and / or actions should also be considered as disclosing any components suitable for performing those functions and / or actions. The functions and / or actions described herein can be performed using any suitable method and in any suitable manner.

[0036] Examples as claimed in the appended claims are provided according to various, but not necessarily all, embodiments.

[0037] While the examples and optional features of this disclosure have been described separately, it should be understood that they are included within this disclosure in all possible combinations and permutations. It should be understood that the various examples of this disclosure may include any or all of the features described with respect to other examples of this disclosure, and vice versa. Furthermore, it should be understood that any one or more features in any combination may be implemented / included / performed by means of, as needed and appropriately, by means of, apparatus, method, and / or computer program instructions. The description of the function should also be considered as disclosing any apparatus suitable for performing that function. Attached Figure Description

[0038] Some examples will now be described with reference to the accompanying drawings, in which: Figure 1 Examples of the topics described in this article are shown; Figure 2 Another example of the topic described in this article is shown; Figure 3 Another example of the topic described in this article is shown; Figure 4 Another example of the subject described in this article is shown; and Figure 5 Another example of the topic described in this article is shown.

[0039] The accompanying drawings are not necessarily drawn to scale. For clarity and brevity, some features and views in the drawings may be shown schematically or enlarged to scale. For example, the dimensions of some elements in the drawings may be enlarged relative to other elements to aid illustration. Similar reference numerals are used in the accompanying drawings to indicate similar features. For clarity, not all reference numerals are necessarily shown in all drawings.

[0040] Abbreviations / Definitions 3GPP Third Generation Partnership Project 5G fifth generation 5GS 5G System 5QI 5G Quality of Service Identifier ACK confirmation AF application functions ATSSS access service guidance, switching, and traffic offloading ATW Analysis Time Window BS base station DSCP Differentiated Service Code Point FEC Forward Error Correction gNB next-generation NodeB, 5G / NR base station GTP-UGPRS Tunneling Protocol User Plane HARQ Hybrid Automatic Repeat Request N2SMF / PCF interface with RAN N3UPF interface with RAN Interface between N4UPF and SMF / PCF N6UPF interface with data network The interface between the two UPFs of N9 NE network entities NEF Network Open Functions Number of NPSPDU sets NR New Radio NW Network PCC Strategy and Charging Control PCF strategy control function PDU Protocol Data Unit PER grouping error rate PLR packet loss rate PSDPDU collection delay PSDBPDU collection delay budget PSERPDU set error rate PSLRPDU set loss rate PSQMPDU aggregates QoS measurements QoS (Quality of Service) QMPQoS measurement packets RAN Radio Access Network SMF Session Management Function TRP transceiver point UE User Equipment UPF User Face Functions XRM Extended Reality (XR) and Media Services Detailed Implementation Figure 1 An example of a network 100 suitable for use with the examples of this disclosure is schematically shown. The network (which may be referred to as NW) includes multiple network entities (which may be referred to as NE), including: • Terminal device 110 (which may be referred to as a terminal node or user equipment (UE)). • Access device 120 (which may be referred to as access node, gNodeB, gNB or base station BS). • One or more core network devices 130 (which may be referred to as core nodes, core functions, core entities or core network entities).

[0041] Terminal node 110 and access node 120 communicate with each other. In some, but not all, examples, one or more core network nodes 130 may communicate with each other. In some, but not all, examples, one or more access nodes 120 may communicate with each other. In some, but not all, examples, one or more access nodes 120 may communicate with one or more core network nodes 130. Access node 120 may communicate with location servers via one or more core nodes 130. Access node 120 and one or more location servers may communicate directly with each other.

[0042] In this example, network 100 is a 3GPP telecommunications network in which at least some of the terminal nodes 110 and access nodes 120 communicate with each other using radio wave transmission / reception.

[0043] Network 100 may include a radio access network (RAN), such as a cellular network comprising multiple cells 122, each cell 122 being served by access node 120. Access node 120 includes a cellular radio transceiver. Terminal node 110 includes a cellular radio transceiver.

[0044] In the specific examples shown and discussed below, network 100 includes a 3GPP New Radio (NR) network and its fifth-generation 5G NR technology. In other examples, network 100 may be a network beyond 5G, such as the next-generation (i.e., sixth-generation 6G) radio network currently under development (i.e., an NR network and its evolution into 5G technology).

[0045] The interface between terminal node 110 and access node 120 is radio interface 124 (e.g., Uu interface). The interface between access node 120 and one or more core nodes 130 is backhaul interface 128 (e.g., S1 and / or next-generation NG interface).

[0046] Depending on the specific deployment scenario, access node 120 can be a RAN node, such as an NG-RAN node. An NG-RAN node can be a gNodeB or gNB, which provides NG user plane and control plane protocol termination to the UE. The gNB connects to the 5G core network (5GC) via an NG interface, for example, connecting to the Access and Mobility Management Function (AMF) via the NG control plane NG-C interface, and connecting to the User Plane Function (UPF) via the NG user plane NG-U interface. Access nodes 120 can interconnect with each other via Xn interface 126.

[0047] Cellular network 100 can be configured to operate in licensed or unlicensed frequency bands (e.g., unlicensed frequency bands that rely on the transmission equipment to sense radio resources / mediums before transmission begins, such as via the Listen-Before-Speak, LBT process; and unlicensed frequency bands that may require beamforming to achieve the desired coverage).

[0048] Access node 120 can be deployed in NG standalone operation / scenarios. Access node 120 can be deployed in NG non-standalone operation / scenarios. Access node 120 can be deployed in carrier aggregation (CA) operation / scenarios. Access node 120 can be deployed in dual connectivity (DC) operation / scenarios, i.e., multiple radio access technologies - dual connectivity, MR-DC or NR-DC. Access node 120 can be deployed in multi-connectivity MC operation / scenarios.

[0049] In this non-standalone / dual-connectivity deployment, access nodes 120 can interconnect with each other via X2 or Xn interfaces and connect to the evolved packet core (EPC) via the S1 interface or to the 5GC via the NG interface.

[0050] In addition to communicating with other terminal nodes via access node 120 of network 100, terminal node 110 can also be configured to communicate directly with one or more other terminal nodes. In this regard, the terminal node can be configured to perform device-to-device (D2D) communication, which may be referred to as side-link (SL) communication. This D2D / SL communication can use the PC5 interface. PC5 is a reference point for direct communication between a terminal node and another terminal node via a direct channel (i.e., without communication via an access node). D2D communication can be short-range, network-free direct communication. SL in New Radio (NR) is defined in 3GPP Release 16 for 5G NR.

[0051] exist Figure 1In the example, core node 130 is shown as a single entity. In some examples, core node 130 may be distributed across multiple entities. For example, core node 130 may be cloud-based or distributed in any other suitable manner. A core node / core entity may provide one or more functionalities, such as User Plane Function (UPF), Session Management Function (SMF), Policy Control Function (PCF), and Application Function (AF).

[0052] Access node 120 is a network element responsible for radio transmission and reception to or from terminal node 110 in one or more cells 122. Access node 120 is a network terminal of a radio link. Each access node can be a transceiver point (TRP) or can host one or more TRPs.

[0053] Access node 120 can be implemented as a single network device, or as a split architecture with different functional split architectures and different interfaces, which are decomposed / distributed across two or more access nodes (such as centralized unit (CU), distributed unit (DU), remote radio head (RRH)).

[0054] Terminal node 110 is a user-side network element in the network that terminates a radio link. They are devices that allow access to network services. The functions of terminal node 110 can also be performed by a mobile terminal, MT (part of an Integrated Access and Backhaul (IAB) node). Terminal node 110 can be referred to as user equipment (UE), mobile device, mobile terminal, or mobile station.

[0055] The term "user equipment" can be used to refer to a mobile device that includes components for authentication / encryption, such as a smart card, for example, a subscriber identity module (SIM). The SIM / SIM card can be a memory chip, module, or universal subscriber identity module (USIM). In some examples, the term "user equipment" can be used to refer to a location / location tag, an ultra / smart device, an ultra / smart sensor, or a mobile device that includes circuitry for authentication / encryption (such as a software SIM) embedded as part of the user equipment.

[0056] In the following description: The terminal device / terminal node can be abbreviated as UE 110; and The access device / access node can be abbreviated as BS 120; Core devices / core nodes (such as AMF, UPF, SMF, PCF, and AF) can be simply referred to as core network entities.

[0057] We will now briefly discuss PDU sets and PDU set QoS parameters.

[0058] A PDU set can be defined as one or more PDUs that carry a payload of an information unit generated at the application level (e.g., a video frame or video slice for extended reality (XR) services).

[0059] In 3GPP Release 18, specifications (such as 3GPP TS 23.501 V18.5.0 and TS 23.502 V18.5.0) define PDU-based processing to support QoS for XR and enable application-aware 5GS.

[0060] All PDUs in a PDU set can be transmitted within the same QoS stream. PDU set QoS parameters can be applied to the PDU aggregations that constitute the PDU set. The UPF can identify individual PDUs as belonging to the PDU set, and the UPF can add PDU set information to the GPRS Tunneling Protocol User Plane (GTP-U) header of packets sent from the UPF to NG-RAN. NG-RAN uses PDU set information and PDU set QoS parameters to provide QoS based on the PDU set.

[0061] PDU set QoS parameters can be used to support PDU set-based QoS processing in NG-RAN. The following PDU set QoS parameters can be sent to NG-RAN to implement PDU set-based QoS processing: • PDU Set Error Rate (PSER): This defines an upper limit on the rate of PDU set loss for non-congestion-related issues.

[0062] • PDU Set Delay Budget (PSDB): This defines the upper limit of the delay that the PDU set may experience for transmission between the UE and the N6 termination point at the UPF (i.e., the duration between the reception time of the first PDU [i.e., at the N6 termination point of the DL, or at the UE of the UL] and the time when all PDUs in the PDU set have been successfully received [i.e., at the UE of the DL or the N6 termination point of the UL)).

[0063] For a given QoS flow, the value of PSDB can be different for UL and DL.

[0064] The QoS profile sent to NG-RAN to configure QoS may include PDU set QoS parameters for UL and / or DL ​​(multiple) directions. The PCF determines the PDU set QoS parameters based on information provided by AF and / or local configuration. The PDU set QoS parameters are sent to the SMF as part of the Policy and Charging Control (PCC) rules. The SMF then sends the PDU set QoS parameters to NG-RAN as part of the QoS profile.

[0065] If the NG-RAN receives PDU set QoS parameters, it enables PDU set-based QoS processing and applies the PDU set QoS parameters (e.g., as described in 3GPP Rel. 18 TS 38.300, TS 38.413 and TS 38.331).

[0066] Now let's briefly discuss QoS monitoring.

[0067] QoS monitoring is an effective and efficient method defined in 3GPP (since Rel-16) for monitoring network or QoS flow performance. Since Rel-18, QoS monitoring has expanded from Ultra-Reliable Low Latency Communications and URLLC-specific services to general services. For Rel-18 XR and Media Services (XRM), it has been agreed to measure new QoS parameters as requested by the AF.

[0068] AF can request the measurement of one or more of the following QoS parameters, which can trigger QoS monitoring of (multiple) service data streams: • UL packet delay, DL packet delay, round-trip packet delay (see, for example, TS 23.501, Clause 5.45.2).

[0069] • Congestion (see, for example, TS 23.501, Clause 5.45.3).

[0070] • Data rate (see, for example, TS 23.501, Clause 5.45.4).

[0071] • Packet delay variations (see, for example, TS 23.501, Clause 5.37.7).

[0072] • Consider the round-trip packet delay of the UL on one service data stream and the DL on another service data stream (see, for example, TS23.501, Clause 5.37.4).

[0073] QoS monitoring reports can be: - UPF to local network opening functionality, NEF / AF -UPF to SMF to PCF to NEF to AF - Use GTP-U to transfer data from RAN to UPF.

[0074] Now let's briefly discuss the packet loss rate (PLR).

[0075] PLR measurement (see, for example, TS23.501, Clause 5.32.5.2a) has been standardized by 3GPP to support access service bootstrapping, switching, splitting, and ATSSS. The transmitting side (UPF for DL ​​and UE for UL) and the receiving side (UE for DL ​​and UPF for UL) count the transmitted and received PDUs and determine the PLR ​​based on the count ratio. Performance Management Function (PMF) messages are exchanged between the UE and UPF to enable counting and reporting of PLR-related information.

[0076] In addition, for QoS, the Packet Error Rate (PER) target to be implemented is provided to the RAN. This involves the RAN determining whether the PDU was successfully transmitted.

[0077] We will now discuss some examples of the present invention that seek to improve or solve certain problems.

[0078] Traditionally / currently, in XR, the AF or PCF (if locally configured) can provide PDU set QoS parameters (e.g., PSER) to the NG-RAN for efficient service processing. However, there is currently no suitable mechanism for the AF / 5GC to know whether PDU set-related QoS (e.g., PSER) is satisfied. Therefore, if PDU set-related QoS is not satisfied, the 5GC is unaware of this and cannot trigger / take any remedial measures to seek to satisfy the PDU set-related QoS (e.g., take action to reduce the loss rate and achieve the requested PSER).

[0079] Conventional / current error / loss rate monitoring mechanisms for measuring and reporting error / loss rates are not optimal. Traditional PLR measurements and packet error rate (PER) targets involve the loss rate and errors of individual packets (i.e., practically PDU-level / granular PDU QoS parameters). They do not consider the loss rate of the PDU set (i.e., practically PDU set QoS parameters at the PDU set level / granularity). This disclosure defines a new PDU set QoS monitoring method, PSQM, or PDU set loss rate (PSLR), which can be used, for example, with XR services. PSLR can provide an indication of the loss rate of the PDU set between the UE and the RAN. Examples provide methods and procedures for measuring and reporting PSLR.

[0080] In the conventional process for measuring the PLR ​​of an ATSSS (Advanced Transaction Support System), PDUs are counted at both the sender (i.e., the UE or UPF) and the receiver (i.e., the UPF or UE). The counts are then compared to determine the PLR. However, this process is not suitable for measuring the PSLR. To measure the PSLR using such a process, the receiver would need to know the PDU set information, specifically which PDUs are part of the PDU set instance, so that these PDUs can be counted and the presence of errors affecting the PDU set can be determined. However, this known PDU set information is traditionally unknown at the receiver (i.e., the UE for DL ​​services or the UPF for UL services). Providing the PDU set information to the receiver would require transmitting the PDU set information over the air interface and coordinating the counting of PDUs including each PDU set between the UE and the UPF. This would be complex to implement and increase the overhead of each PDU. The various examples in this disclosure seek to provide alternative methods for determining the PSLR.

[0081] Various examples of this disclosure seek to address / mitigate the aforementioned problems. Various examples of this disclosure seek to provide measurements of improved loss metrics associated with PDU sets. Various examples of this disclosure seek to provide methods for monitoring losses, for example, during the transmission of PDU sets between the RAN and UE (a QoS parameter of such PDU set associated with the loss of PDUs in the PDU set is referred to herein as the PDU Loss Ratio (PSLR) [and described in further detail below]). Various examples of this disclosure seek to provide methods for monitoring PDU losses incurred during the transmission of PDU sets within a QoS stream.

[0082] Figure 2 Method 200, an example of the subject matter described herein, is illustrated schematically.

[0083] Figure 2 It can be considered to demonstrate multiple methods, in a sense, Figure 2 This can be considered as illustrating one or more actions performed by multiple participants / entities (i.e., RAN (represented by RAN NE such as BS 120) or first (and second) core NE 130 (such as UPF (and SMF or AF)) / at multiple participants / entities). Therefore, Figure 2 This can be considered as illustrating multiple individual methods performed by each of the corresponding individual participants / entities among multiple participants / entities.

[0084] Figure 2 The component blocks are functional, and the described functionality can be derived from a single physical entity (such as a reference). Figure 4 The functions described can also be performed by computer programs (such as references). Figure 5 To achieve this, as described above.

[0085] Method 200 can be executed by device 10, which can be embodied in BS 120. In the following example, the method is described from the perspective of execution by BS 120 and for a downlink scenario.

[0086] In box 201, BS 120 receives one or more PDU sets 202 from first core network entity 130 (e.g., UPF 131) for transmission to UE (not shown). In this respect, the BS may receive multiple PDUs and information indicating which set each PDU belongs to. This information may be PDU set information included in the GTP-U header received from the UPF.

[0087] Each PDU set can include multiple PDUs (e.g., N PDUs). Additionally, the BS can be provided with PDU set information to indicate which PDUs belong to which PDU set.

[0088] In box 203, BS 120 determines for each received PDU set whether the PDU set is considered to have been successfully or unsuccessfully transmitted from BS to UE.

[0089] In box 203, the determination of whether a set of PDUs is considered to have been successfully or unsuccessfully transmitted is based at least in part on the number of PDUs in the set that have been successfully or unsuccessfully transmitted from the BS to the UE. In this regard, the determination of whether a set of PDUs is considered to have been successfully or unsuccessfully transmitted can be based on whether the proportion of successfully transmitted PDUs (of that set) exceeds a threshold. This threshold can be pre-configured, sent via signaling, or otherwise indicated to the BS, or it can be defined in a standard.

[0090] In box 204, BS 120 determines the number 205 of PDU sets that are considered to have been successfully or unsuccessfully transmitted. In this respect, the BS counts the number of PDU sets considered to have been successfully or unsuccessfully transmitted in box 203. The number 205 can indicate the number of PDU sets lost, thus providing an indication of PDU set loss measurement.

[0091] In box 206, BS 120 sends information 207 to the second core network entity (e.g., SMF) indicating the number of one or more PDU sets that were considered to have been successfully or unsuccessfully transmitted. The SMF can then send information to the NEF or AF (not shown).

[0092] Alternatively, in box 206', BS 120 sends information 207 to UPF. UPF can then send information to AF or NEF (not shown). In this respect, UPF itself may have already received configuration information from SMF (not shown) for configuring UPF to report information 207 to AF or NEF (not shown).

[0093] The information 207 reported in box 206 or 206' may be based at least in part on the number 205 determined in box 204, that is, the information 207 may be based at least in part on a PDU set loss measurement. In this respect, the information 207 may indicate a PDU set loss rate (PSLR) measurement, wherein the PSLR measurement indicates the ratio of PDU sets that were successfully transmitted or unsuccessfully transmitted, that is, how many PDU sets out of the total number of PDU sets transmitted by the BS to the UE were determined to be successfully transmitted or unsuccessfully transmitted.

[0094] In other words, the information 207 sent in box 206 or 206' can indicate PSLR, where PSLR indicates the ratio of the following: The number of one or more PDU sets that were considered to have been successfully or unsuccessfully transmitted, and The total number of one or more PDU sets that the BS needs to transmit to the UE.

[0095] The BS can be configured to execute by receiving configuration information. Figure 2 One or more of the boxes above, namely: For each PDU set, determine whether the PDU set is considered to have been successfully or unsuccessfully transmitted to the UE by the BS; Determine the number of PDU sets that are considered to have been successfully or unsuccessfully transmitted; Send information indicating the number (i.e., PSLR measurement) to the SMF or UPF.

[0096] In this regard, the BS can be configured to perform PSLR measurements via configuration information. That is, the BS can be configured to perform at least one or more of the following: For each of the multiple PDU sets to be transmitted from the BS to the UE: The total number of PDUs in each PDU set, and The number of PDUs in each PDU set that have been successfully or unsuccessfully transmitted to the UE by the BS; Determine one or more metrics (e.g., one or more PSLR measurements) that indicate the transmission quality of the PDU set from the BS to the UE, wherein the metric is determined based at least in part on the following: The total number of PDUs in each PDU set, and The number of PDUs in each PDU set that have been successfully or unsuccessfully transmitted to the UE by the BS.

[0097] The BS can receive configuration information (before box 201) from a second core network entity (e.g., SMF) to configure the BS to perform PSLR measurements.

[0098] The configuration information itself may initially come from the AF. For example, the configuration information may be provided to the BS as follows: AF>NEF>PCF>SMF>BS. Alternatively, if QoS monitoring based on PDU sets is configured in the PCF, the configuration information may be provided to the BS as follows: PCF>SMF>BS.

[0099] The configuration information may include information indicating the entity to which the message / PSLR should be sent (e.g., SMF or UPF), and in response, the BS sends the message / PSLR appropriately to the appropriate entity based on the configuration information.

[0100] Configuration information may also include instructions on when to send the message / PSLR, for example, if you want to send the message / PSLR: Periodically; Non-periodic; In response to the fulfillment of the triggering condition; In response to meeting a threshold criterion (in this case, the configuration information may include information indicating the threshold, such as an indication of its value).

[0101] In some examples, the configuration information includes indications that the transmission of information will be based on the BS determining that a threshold has been exceeded; wherein the threshold is based at least in part on the number of one or more PDU sets that are considered to have been successfully or unsuccessfully transmitted. In this respect, the threshold may depend on PDU set QoS parameters, such as PSER.

[0102] In some examples, the configuration information may include information indicating time intervals; and the execution of at least one or more of the following is at least partially based on time intervals: To determine whether a set of PDUs is considered successfully or unsuccessfully transmitted, Determine the number of PDU sets that are considered to have been successfully or unsuccessfully transmitted, or Determine PSLR.

[0103] In this regard, the time window can be the analytical time window (ATW), which defines the time period for which PSLR is to be measured.

[0104] In some examples, the configuration information may include information indicating the number of PDU sets; and the execution of at least one or more of the following is at least partially based on the first number of PDU sets: Determine whether the PDU set is considered successfully transmitted or unsuccessfully transmitted, or Determine the number of PDU sets that are considered to have been successfully or unsuccessfully transmitted.

[0105] In this respect, the number of PDU sets NPS can correspond to the number of PDU sets "n" for which PSLR is to be measured (e.g., a sequence of n PDU sets). In other words, the BS can be configured to measure PSLR only for a specific number of PDU sets (i.e., the indicated NPS), rather than for all PDU sets received at the BS for further transmission to the UE.

[0106] In some examples, the configuration information includes information indicating one or more metrics to be reported to the second or first core network entity (e.g., SMF or UPF), such as average PSLR, median PSLR, PSLR variance, or one or more metrics / statistics. Such one or more metrics may be included in information 207 sent by the BS in box 206 or 206'.

[0107] Method 200 has already been described for downlink, DL scenario (i.e., DL transmission of a PDU set, e.g., from UPF to BS to UE). It should be understood that the above method can be applied equally well to uplink, UL scenario (i.e., UL transmission of a PDU set, e.g., from UE to BS to UPF), with necessary modifications. In this regard, the necessary changes in the UL scenario are as follows: • Regarding box 201, the PDU set is not received by the BS from the UPF, but by the BS from the UE; • Regarding box 203, this will instead involve determining whether the PDU set was successfully received by the BS from the UE or not; • Regarding box 204, this will instead involve determining the number of PDU sets that the BS successfully or unsuccessfully received from the UE (e.g., in a predetermined or total number of PDU sets).

[0108] Examples in this disclosure provide methods and procedures for defining new PDU set QoS monitoring (PSQM), i.e., PSLR (e.g., for XR services), and its measurement and reporting (e.g., as described above regarding...). Figure 2 The topics discussed and the following will be about Figure 3 (To be discussed in further detail). Similar to the PSER QoS parameter (see Section 5.7.7.3 of TS23.501), the PSLR measurement focuses on the PDU set loss between the RAN and the UE (i.e., it does not consider the PDU set loss on the N3 or N6 interface).

[0109] Create a PSQM-specific strategy in the PCF (e.g., based on a request from the AF or due to local configuration) to collect data and / or statistics (e.g., mean, median, etc.) related to PSLR measurements. Statistics can be determined on a time window (e.g., ATW as described below) or on several sample / PDU sets (e.g., NPS as described below). Measurements can be opened to the 5GC (e.g., towards the AF) periodically or non-periodically using existing reporting measurements (e.g., based on a threshold or when a certain number of measurements have been obtained).

[0110] Examples of this disclosure relate to the following novel behaviors of AF, PCF, SMF, and RAN.

[0111] AF behavior: The AF can request PSLR statistics, which can trigger PSQM for (multiple) service data streams. Optionally, the AF can provide the "Analysis Time Window" (ATW), which indicates the time interval used to determine PSLR, the "PDU Set Number" (NPS) required to perform PSLR measurement in 5GS, and / or one or more thresholds for reporting PSLR. The AF can also request separate reporting-related parameters for PDU set performance measurement (e.g., reporting frequency, such as threshold-based reporting triggering).

[0112] ATW is intended to represent the duration for determining PSLR. It can be determined to be long enough for PSLR to be statistically "correct". For example, if only 12 PDU sets are monitored (requiring ATW=200 ms) and 1 is lost, it should not be claimed that the PSLR is 1 / 12; it may just be a coincidence, and no more PDU sets will be lost in the next 200 seconds. On the other hand, if 12,000 PDU sets are monitored (requiring ATW=200 ms) and 1,000 are lost, it is more reasonable to report PSLR=1000 / 12,000=1 / 12.

[0113] NPS is an alternative to ATW. It specifies the count of the PDU set required for PSLR measurement instead of the time interval. ATW or NPS can be provided by AF, configured in PCF, SMF, or RAN, or calculated in PCF / SMF or RAN based on the requested PSER.

[0114] PCF behavior: The PCF generates an authorized PSQM policy based on an AF request or local policy, requesting PSLR measurement of the service data stream. The PCF includes this policy in a PCC rule and provides it to the SMF. The PSQM policy indicates new QoS monitoring(s) parameters and reporting-related parameters related to PSLR measurement. These parameters may include ATW, NPS, and / or reporting thresholds based on the AF request or local configuration. The PCC rule may also provide the Application Layer Forward Error Correction (FEC) ratio (which indicates the proportion of PDUs in the PDU set required for application recovery). Alternatively, the UPF may provide the FEC ratio as PDU set information to the RAN. When the proportion of lost PDUs in the PDU set exceeds the proportion indicated by the FEC ratio, the PDU set is considered lost (i.e., not successfully transmitted), thus affecting PSLR measurement.

[0115] The PSQM policy can instruct PSLR reporting (e.g., toward AF) to be completed only when the measured PSLR exceeds a threshold, which can be relative to the QoS parameter PSER.

[0116] SMF behavior: If a PSLR measurement is triggered based on a received PCC rule or local configuration for a QoS flow targeting the UE, the SMF configures the NG-RAN service to perform the PSLR measurement. The SMF can provide ATW and NPS. The SMF configures the RAN to report measurements directly to the SMF (option 1) or to the UPF (option 2). PSLR measurements can also be combined with other measurements in the same report.

[0117] If reporting via UPF is configured in the RAN (Option 2), the SMF configures the UPF to report PSLR monitoring results to the SMF or NEF / AF. The reporting can be similar to the reporting described in Clause 5.8.2.18 of 3GPP TS 23.501.

[0118] Alternatively, the SMF can configure the UPF or RAN to send a measurement report only when the measured PSLR exceeds a threshold, which can be relative to the PSER QoS parameter.

[0119] RAN behavior: The RAN (e.g., NG-RAN, i.e., a BS such as a gNB) can receive from the SMF: FEC-Ratio, ATW and / or NPS parameters, and reporting thresholds to be used to determine and report PSLR. Alternatively, these parameters can be configured locally within the RAN.

[0120] For each set of PDUs sent to the UE by the NG-RAN, the NG-RAN begins recording how many PDUs in the set were successfully sent to the UE and / or how many PDUs were lost (not successfully sent to the UE). Layer 2 (e.g., HARQ ACK / NACK) can be used to determine whether the UE has successfully received the PDUs. The NG-RAN then determines whether the FEC-Ratio standard or the default standard is not met.

[0121] When ATW, NPS, or the default criteria are met, NG-RAN determines the PSLR measurement:

[0122] NG-RAN can also record how many PDUs in the PDU set are lost on the N3 interface and use this information to determine whether the PDU set has been lost.

[0123] The RAN can collect individual PDU sets of PSLR measurements and report them to the UPF periodically, or it can report them after a certain number of measurements have been obtained. The RAN can alternatively or additionally determine one or more statistics (e.g., mean PSLR, median PSLR, PSLR variance) and report them to the UPF.

[0124] NG-RAN can also report PDU loss in N3 and over the air to determine the cause of the PDU set loss.

[0125] Figure 3 An example signaling diagram is shown for a method to measure PSLR in 5GS and report it to AF (but it should be understood that this method can be applied to the next generation 6GS).

[0126] Figure 3 It can be considered to demonstrate multiple methods, in this sense, Figure 3 This can be interpreted as demonstrating one or more actions performed by or at multiple participants / entities, including not only the RAN and UPF, but also the SMF / PCF, AF, and UE. Therefore, Figure 3 This can be considered as illustrating multiple individual methods performed by each individual participant / entity among multiple participants / entities.

[0127] In summary (as will be elaborated in more detail below), in Figure 3 In this method / process, it is assumed that the 5GS can receive QoS monitoring requests for (multiple) PDU sets from the AF, i.e., monitoring PSLR. Then, the 5GC (e.g., SMF) configures the UPF and RAN (similar to traditional QoS monitoring) to perform PSLR measurements. The 5GC can also configure the NG-RAN to provide PDU set latency measurements.

[0128] The signaling diagram highlights how the RAN measures PSLR requested or configured by the 5GC (e.g., SMF). The signaling diagram illustrates a downlink (DL) example. However, with necessary modifications, the basic concepts can also be applied to the uplink.

[0129] about Figure 3 One or more features under discussion can be Figure 2 Found it. Figure 3 During the discussion, for illustrative purposes, references will be made to... Figure 2 Features and their accompanying reference numerals.

[0130] In the following description of the process and algorithm of the proposed method, the following PDU set transmission and reception model is assumed, i.e., where the PDU set includes multiple "N" PDUs. PDU_i represents the first PDU in the PDU set received at the UPF. PDU_N represents the last PDU in the PDU set received at the UPF.

[0131] In step 1a, the AF sends a request for QoS monitoring of the PDU set, optionally with one or more monitoring and reporting parameters (e.g., ATW, NPS, PSLR reporting threshold, desired reporting [periodic, threshold-based, etc.]).

[0132] In step 1b: The PCF creates PCC rules using the PSLR's PDU set QoS monitoring parameters. If the PSLR report will be via the UPF ("Option 2"), the SMF appropriately configures the UPF via N4 signaling to report PSLR monitoring results, for example, in a manner similar to that described in Section 5.8.2.18 TS 23.501.

[0133] In step 2: The SMF configures the NG-RAN via N2 signaling to perform PSLR measurements and also instructs on the parameters for monitoring and reporting.

[0134] In step 3: DL services, such as DL services from an external data network, are received at the UPF.

[0135] In step 4: UPF determines the PDU set of the received DL service and determines the PDU set information of the GTP-U header.

[0136] In step 5: The UPF sends the PDU containing PDU set information in the GTP-U header to the RAN. This step can effectively correspond to... Figure 1 Box 201 in the GTP-U header, wherein the PDUs containing PDU set information can be effectively corresponding to Figure 1 The PDU set in the data is 202.

[0137] In steps 6-10: The RAN performs the service transmission process between the RAN and at least one UE, including scheduling and Layer 2 (L2) feedback (e.g., HARQ ACK / NACK, RLC ACK).

[0138] In step 11: The RAN counts the number of PDUs that were not successfully (or successfully) transmitted in each PDU set and the total number of PDU sets that attempted to be transmitted. The RAN detects the last PDU in a PDU set based on an indication in the GTP-U header (e.g., [End of PDU set]). The RAN determines whether (multiple) PDUs in a PDU set are lost by dividing the number of PDUs in the PDU set that have not yet been successfully transmitted to the UE by the number of PDUs in that PDU set and comparing the result with the FEC ratio parameter or a locally configured standard (parameter). In other examples, the number of PDUs in a PDU set that have been successfully transmitted to the UE can alternatively be used to determine whether (multiple) PDUs in a PDU set are lost. This step can effectively correspond to Figure 2 Box 203 in the middle.

[0139] If a PDU set is lost based on the number of lost PDUs in the PDU set, then the RAN increments the counter for the "lost PDU set". This can be effectively corresponded to Figure 1 Box 204 in the diagram, where the number of missing PDU sets can be effectively corresponded to Figure 1 The number of PDU sets considered to have been successfully or unsuccessfully transmitted is 205.

[0140] The RAN also increments a counter for the "total number of PDU sets" for each PDU set received from the UPF.

[0141] Repeat steps 3-11 for subsequent PDU sets until the criteria used to determine the PSLR (e.g., ATW or NPS) are met.

[0142] In step 12: The RAN determines a new PSLR estimate or updates the current PSLR estimate based on the ratio of the "lost PDU set" to the "total number of attempts to send the PDU set". The PSLR estimate can effectively correspond to the indication in Figure 1 Information 207: The number of PDU sets that were considered to have been successfully or unsuccessfully transmitted.

[0143] In step 13: RAN determines whether the PSLR reporting criteria are met (e.g., periodicity, number of PSLR estimates and / or PSLR threshold relative to PSER, etc.).

[0144] If the PSLR reporting criteria are not met, repeat steps 3-13.

[0145] In step 14: RAN may optionally determine the PSLR statistics of the PSLR measurement results (e.g., mean, median, mode, maximum, etc.).

[0146] In step 15: For option-1, the RAN reports the PSLR measurement results and / or PSLR statistics to the SMF. The SMF can then send the PSLR measurement results and / or PSLR statistics to the AF (e.g., via the PCF or NEF). This step can effectively correspond to... Figure 1 Box 206 in the middle.

[0147] In step 16: For option 2, the RAN reports PSLR measurements and / or PSLR statistics to the UPF, for example, via virtual uplink packets and / or GTP-U header extensions. This step can effectively correspond to Figure 1 Box 206' in the middle.

[0148] In step 16b, for option 2, the UPF / PCF / NEF sends PSLR measurement results and / or PSLR statistics to the AF.

[0149] The above about Figure 3 The described example methods and signaling can thus provide a process for monitoring, measuring, and reporting, for example, the PDU set loss rate, PSLR, measurement, and / or PSLR statistics for XR services. Various examples in this disclosure can define new QoS monitoring mechanisms for XR services based on PDU sets.

[0150] Advantageously, the various methods and processes described above provide a mechanism for measuring and reporting PDU set-related QoS metrics (e.g., PSLR), which can be reported to the AF / 5GC, enabling the AF / 5GC to know whether PDU set-related QoS / PSLR has been / is being met. If not, the 5GC can seek remedial measures.

[0151] Figure 4 This schematically illustrates the means for performing the functions described in this disclosure and Figure 2 and Figure 3 A block diagram of apparatus 10 showing methods, processes, procedures, and signaling is provided. In this respect, the apparatus can perform the role of an entity (such as BS, RAN, UPF, SMF, PCF, or AF) in the methods shown and described.

[0152] Figure 4 The component boxes are functional, and the described functions can be performed by a single physical entity (such as a BS or UPF).

[0153] The device includes a controller 11, which can be located within a device / entity (e.g., BS or UPF).

[0154] The controller 11 may be implemented by a computing device (such as the computing device mentioned above). In some, but not all, examples, the device may be embodied as a chip, chipset, circuit, or module, i.e., for any of the foregoing. As used herein, "module" means a unit or device that does not include certain parts / components to be added by the end manufacturer or user.

[0155] The controller 11 can be implemented as a controller circuit. The controller 11 can be implemented only in hardware, can have certain aspects only in software including firmware, or can be a combination of hardware and software (including firmware).

[0156] The controller 11 can be implemented using instructions that implement hardware functions, for example, by using executable instructions of a computer program 14 in a general-purpose or special-purpose processor 12, which can be stored on a computer-readable storage medium 13, such as a memory or a disk, for execution by such a processor 12.

[0157] Processor 12 is configured to read from and write to memory 13. Processor 12 may also include an output interface and an input interface, via which processor 12 outputs data and / or commands and via the input interface to receive data and / or commands. The device may be coupled to or include one or more other components 15 (e.g., radio transceivers, sensors, input / output user interface elements, and / or other modules / devices / components for inputting and outputting data / commands).

[0158] Memory 13 stores instructions such as computer program 14, which includes instructions (e.g., computer program instructions / code) that control the operation of device 10 when loaded into processor 12. The instructions of computer program 14 enable the device to perform operations described herein and... Figure 2 and Figure 3 The methods, processes, and program logic and routines are shown in the diagram. Processor 12 can load and execute computer program 14 by reading memory 13.

[0159] Instructions may be included in computer programs, non-transitory computer-readable media, computer program products, and machine-readable media. As used herein, the term "non-transitory" refers to a limitation on the medium itself (i.e., tangible, not tactile) rather than a limitation on the persistence of data storage (e.g., RAM and ROM). In some, but not necessarily all, examples, computer program instructions may be distributed across more than one computer program.

[0160] Although memory 13 is shown as a single component / circuit, it can be implemented as one or more separate components / circuits, some or all of which may be integrated / removable and / or provide permanent / semi-permanent / dynamic / cached storage.

[0161] Although processor 12 is shown as a single component / circuit, it can be implemented as one or more separate components / circuits, some or all of which may be integrated / removable. Processor 12 may be a single-core or multi-core processor.

[0162] The apparatus may include tools for implementing the features described herein. Figure 2 and Figure 3 The methods, processes, and procedures shown herein may include one or more components. It is conceivable that the functionality of these components may be combined within one or more components, or performed by other components with equivalent functionality. The description of the functionality should also be considered as disclosing any means suitable for performing that functionality.

[0163] Where a structural feature has been described, it may be replaced by means of one or more of the functions that perform the structural feature, whether the function or those functions are explicitly or implicitly described.

[0164] Although examples of devices have been described above in terms of including various components, it should be understood that components may be embodied as corresponding controllers or circuits (such as one or more processing elements or processors of the device) or otherwise controlled by them. In this regard, each of the components described above may be one or more of any device, apparatus, or circuit embodied in hardware, software, or a combination of hardware and software, configured to perform the corresponding function of the corresponding component as described above.

[0165] The device can be, for example, a base station, server equipment, core network entity / node, UPF, SMF, PCF, or AF in a mobile cellular telecommunications system. The device can be embodied by a computing device (such as the computing device mentioned above). However, in some examples, the device can be embodied as a chip, chipset, circuit, or module, i.e., used for any of the foregoing.

[0166] In one example, the device is embodied in a client device, UE, mobile cellular phone, handheld portable electronic device, mobile communication device, wearable computing device, or personal digital assistant, and may also provide one or more audio / text / video communication functions (e.g., telecommunications, video communication, and / or text transmission [Short Message Service / Multimedia Messaging Service / Email] functions), interactive / non-interactive viewing functions (e.g., web browsing, navigation, TV / program viewing functions), music recording / playback functions (e.g., Motion Picture Experts Group-1 Audio Layer 3 (MP3) or other formats and / or FM / AM radio broadcast recording / playback), data download / transmission functions, image capture functions (e.g., using a built-in digital camera), and gaming functions, or any combination thereof.

[0167] In some examples (such as where the device is provided within BS 120), device 10 includes: At least one processor 12; and At least one memory 13 stores instructions that, when executed by at least one processor 12, cause the device to at least: Receive one or more sets of Protocol Data Units (PDUs) from the first core network entity for transmission from the device to the User Equipment (UE); For one or more PDU sets, determine whether the PDU set is considered to have been successfully or unsuccessfully transmitted from the device to the UE, wherein the determination is based at least in part on the number of PDUs in the PDU set that have been successfully or unsuccessfully transmitted from the device to the UE; Determine the number of one or more PDU sets that are considered to have been successfully or unsuccessfully transmitted; and Send information to the second core network entity or the first core network entity indicating the number of one or more PDU sets that are considered to have been successfully transmitted or not successfully transmitted.

[0168] In some examples (such as where the device is provided within UPF 131), device 10 includes: At least one processor 12; and At least one memory 13 stores instructions that, when executed by at least one processor 12, cause the device to at least: Receive configuration information from the first core network entity for reporting first information to the second core network entity, the first information indicating the number of one or more PDU sets that are considered to have been successfully or unsuccessfully transmitted to the user equipment (UE) by the radio access network (RAN) node; Receive first information from the RAN node; and Report the first information to the second core network entity.

[0169] The examples above can be applied to implement the following components: telecommunications systems; tracking systems; automotive systems; electronic systems including consumer electronics; distributed computing systems; media systems for generating or rendering media content including audio, visual, and audiovisual content, as well as mixed, mediated, virtual, and / or augmented reality media content; personal systems including personal health systems or personal fitness systems; navigation systems; user interfaces also known as human-machine interfaces; networks including cellular, non-cellular, and optical networks; self-organizing networks; the Internet of Things (IoT); vehicle-to-everything (V2X) networks; virtualized networks; and related software and services.

[0170] According to the examples of this disclosure, the device can be provided in an electronic device (e.g., a mobile terminal). However, it should be understood that the mobile terminal is merely an illustration of an electronic device that will benefit from the implementation of this disclosure and should therefore not be construed as limiting the scope of this disclosure. While the device may be provided in a mobile terminal in some implementation examples, other types of electronic devices, such as, but not limited to, mobile communication devices, handheld portable electronic devices, wearable computing devices, portable digital assistants (PDAs), pagers, mobile computers, desktop computers, televisions, gaming devices, laptop computers, cameras, video recorders, GPS devices, and other types of electronic systems, can readily adopt the examples of this disclosure. Furthermore, devices can readily adopt the examples of this disclosure regardless of their intention to provide mobility.

[0171] Figure 5 A computer program 14 that can be transmitted via delivery mechanism 20 is shown. Delivery mechanism 20 can be any suitable delivery mechanism, such as a machine-readable medium, a computer-readable medium, a non-transitory computer-readable storage medium, a computer program product, a memory device, a solid-state memory, a recording medium (such as an optical disc read-only memory (CD-ROM) or a digital versatile optical disc (DVD)), or an article of manufacture that includes or tangibly embodies the computer program 14. The delivery mechanism can be a signal configured to reliably transmit the computer program. The apparatus can receive, propagate, or transmit the computer program as a computer data signal.

[0172] In some examples of this disclosure, a computer program including instructions is provided that, when executed by a device (e.g., BS 120), causes the device to perform at least the following operations or is used to cause the following operations to be performed: At a device, one or more sets of Protocol Data Units (PDUs) are received from a first core network entity for the device to transmit to a User Equipment (UE). At the device, for one or more PDU sets, it is determined whether the PDU set is considered to have been successfully transmitted from the device or unsuccessfully transmitted to the UE, wherein the determination is based at least in part on the number of PDUs in the PDU set that have been successfully transmitted from the device or unsuccessfully transmitted to the UE; The number of one or more PDU sets considered to have been successfully or unsuccessfully transmitted is determined at the device; and The device sends information to the second core network entity or the first core network entity indicating the number of one or more PDU sets that are considered to have been successfully or unsuccessfully transmitted.

[0173] In some examples of this disclosure, a computer program is provided that includes instructions that, when executed by a device (e.g., UPF 131), cause the device to perform at least the following operations or is used to cause the device to perform at least the following operations: At a device, configuration information is received from a first core network entity for reporting first information to a second core network entity, the first information indicating the number of one or more PDU sets that are considered to have been successfully or unsuccessfully transmitted to the user equipment (UE) by the radio access network (RAN) node; The device receives the first information from the RAN node; and The device reports the first information to the second core network entity.

[0174] References to computer programs, computer-readable storage media, computer program products, tangibly embodied computer programs, etc., or controllers, computers, processors, etc., should be understood to encompass not only computers with different architectures (such as single / multiprocessor architectures and sequential (von Neumann) / parallel architectures) but also special-purpose circuits (such as field-programmable gate arrays (FPGAs), special-purpose circuits (ASICs), signal processing devices, and other devices). References to computer programs, instructions, code, etc., should be understood to encompass software or firmware for programmable processors, such as, for example, programmable content of hardware devices, whether instructions for processors or configuration settings for fixed-function devices, gate arrays, or programmable logic devices, etc.

[0175] As used in this application, the term "circuit" may refer to one or more or all of the following: (a) Hardware circuit implementation only (such as implementation in analog and / or digital circuits only), and (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits and software / firmware, and (ii) Any part of a hardware processor(s) having software (including (multiple) digital signal processors, software, and (multiple) memories, which together enable a device such as a mobile phone or server to perform various functions; and (c) A hardware circuit and / or a processor, such as a microprocessor or part of a microprocessor, that requires software (e.g. firmware) for operation, but may be absent if operation does not require the software.

[0176] This definition of "circuit" applies to all uses of the term in this application (including in any claim). As another example, as used in this application, the term "circuit" also covers only the implementation of hardware circuits or processors and their accompanying software and / or firmware. For example, where applicable to a particular claim element, the term "circuit" also covers baseband integrated circuits for mobile devices or similar integrated circuits in servers, cellular network devices, or other computing or networking devices.

[0177] Although various examples of this disclosure have been described in the preceding paragraphs, it should be understood that modifications may be made to the given examples without departing from the scope of the invention as set forth in the claims.

[0178] Figure 2 and Figure 3 The boxes shown can represent actions in a method, functions performed by a device, and / or instructions / code segments in a computer program.

[0179] It should be understood that Figure 2 and Figure 3 Each box and combination of boxes shown, as well as the further functions described above, can be implemented by various means, such as hardware, firmware, and / or software including one or more computer program instructions. For example, one or more of the functions described above can be implemented by a suitably configured means (such as a means including components for performing the functions described above [e.g., Figure 4 [As shown]) can be executed. One or more of the above functions / functionalities can be performed by a properly configured computer program (such as a computer program that includes computer program instructions embodying the above functions / functionalities and can be stored in a memory storage device and executed by a processor [e.g. Figure 5 As shown in the figure]) to illustrate.

[0180] As will be understood, any such computer program instructions can be loaded onto a computer or other programmable device (i.e., hardware) to produce a machine, such that when executed on the programmable device, the instructions create means for implementing the function / functionality specified in the box. These computer program instructions can also be stored in a computer-readable medium that can instruct the programmable device to operate in a particular manner, such that the instructions stored in the computer-readable medium produce an article of writing including means for implementing the function specified in the box. The computer program instructions can also be loaded onto the programmable device to cause a series of operational actions to be performed on the programmable device to produce a computer-implemented process, such that the instructions, which execute on the programmable device, provide actions for implementing the function / functionality specified in the box.

[0181] The various, but not all, examples disclosed herein may take the form of methods, apparatus, or computer programs. Therefore, the various, but not all, examples may be implemented in hardware, software, or a combination of hardware and software.

[0182] Various, but not all, examples of this disclosure are described using flowcharts and schematic block diagrams. It should be understood that each block (of the flowcharts and block diagrams), and combinations thereof, can be implemented by computer program instructions of a computer program. These program instructions can be provided to one or more processors, processing circuits, or controllers(s) such that instructions executed thereon form components for causing the implementation of the functions specified in one or more blocks, i.e., enabling the method to be implemented by a computer. The computer program instructions can be executed by the processor(s) to cause the processor(s) to perform a series of operation blocks / steps / actions, thereby producing a computer-implemented process, such that instructions executed on the processor(s) provide blocks / steps for implementing the functions specified in one or more blocks.

[0183] Therefore, these boxes support: combinations of components for performing a specified function; combinations of actions for performing a specified function; and computer program instructions / algorithms for performing a specified function. It should also be understood that each box and combination of boxes can be implemented by a dedicated hardware-based system, or a combination of dedicated hardware and computer program instructions, that performs the specified function or action.

[0184] Various, but not all, examples of this disclosure provide both a method and corresponding apparatus, which includes various modules, components, or circuits providing functionality for performing / applying the actions of the method. The modules, components, or circuits may be implemented as hardware or as software or firmware executed by a computer processor. In the case of firmware or software, examples of this disclosure may be provided as a computer program product including a computer-readable storage structure embodying computer program instructions (i.e., software or firmware) executable by a computer processor.

[0185] Although certain terms are used in this article, they are used only in a general and descriptive sense and not for restrictive purposes.

[0186] The features described above can be used in combinations other than those explicitly stated.

[0187] Although some features have been described with reference to certain characteristics, these functions can be performed by other features, whether or not they are described.

[0188] Although features have been described with reference to certain examples, these features may also exist in other examples, whether or not they are described. Therefore, a feature described with respect to one example / aspect of this disclosure may include any or all features described with respect to another example / aspect of this disclosure, and vice versa, provided that they do not contradict each other.

[0189] The term “comprising” as used in this document has an inclusive rather than exclusive meaning. That is, any reference to X that includes Y indicates that X may include only one Y or may include more than one Y. If the intention is to use “comprising” with an exclusive meaning, it will be made clear in the context by referring to “comprising only one…” or by using “consisting of…”.

[0190] In this specification, the terms “connection,” “coupling,” and “communication,” and their derivatives, mean operatively connecting / coupling / communicating. It should be understood that any number or combination of intermediate components (including no intermediate components) may be present to provide direct or indirect connection / coupling / communication. Any such intermediate component may include hardware and / or software components.

[0191] As used herein, the term "determine" or "determining" (and its grammatical variations) can include, but is not limited to: evaluation, calculation, operation, processing, derivation, measurement, investigation, identification, lookup (e.g., searching in a table, database, or other data structure), ascertainment, etc. Furthermore, "determining" can include receiving (e.g., receiving information), retrieving / accessing (e.g., retrieving / accessing data in memory), obtaining, etc. Additionally, "determining" can include parsing, selecting, picking, building, inferring, etc.

[0192] As used herein, a description of an action should also be considered as disclosing enabling and / or causing and / or controlling the action. For example, a description of transmitting information should also be considered as disclosing enabling and / or causing and / or controlling the transmission of information. Similarly, for example, a description of a means of transmitting information should also be considered as disclosing at least one component or controller of the means that enables and / or causes and / or controls the means of transmitting information.

[0193] The term "component" as used in the specification and claims may refer to one or more individual elements configured to perform a corresponding described function or multiple functions, or may refer to several elements performing such functions. Furthermore, the functions described in the claims may be performed by the same individual component or a combination of the same components. For example, one or more such functions may be performed by an instruction stored in the memory of the device executed by a processor in the device.

[0194] Unless explicitly stated otherwise (unless the context requires otherwise), references to parameters or parameter values ​​should be understood as referring to "data indicating the relevant parameter / value," "data defining the relevant parameter / value," or "data representing the relevant parameter / value." Data can indicate the relevant parameter / value in any way and can indicate the relevant parameter / value directly or indirectly.

[0195] Various examples have been referenced in this specification. Descriptions of the features or functions of an example indicate which features or functions are present in that example. The use of the terms "example," "for example," "can," or "may" in the text indicates that, whether explicitly stated or not, these features or functions are present at least in the described example, and may, but not necessarily, be present in some or all other examples. Therefore, "example," "for example," "can," or "may" refers to a specific instance of a class of examples. An instance's property can be a property of only that instance, or a property of the class, or a property of a subclass of the class, which includes some but not all instances of the class.

[0196] In this specification, unless otherwise expressly stated, references to “a (a) / a (an) / the” [feature, element, component, part...] are used in an inclusive rather than exclusive sense and should be interpreted as “at least one” [feature, element, component, part...]. That is, any reference to X that includes a / the Y indicates that X may include only one Y, or may include more than one Y, unless the context clearly indicates the opposite. If “a” or “the” is intended to be used in an exclusive sense, it will be clearly stated in the context. In some cases, “at least one” or “one or more” may be used to emphasize the inclusive meaning, but the omission of these terms should not be construed as implying any exclusive meaning. As used herein, “at least one of the following: ” and “at least one of ” and similar expressions (where the list of two or more elements is connected by “and” or “or”) mean at least any one element, at least any two or more elements, or at least all elements.

[0197] The presence of a feature (or combination of features) in a claim is a reference to that feature (or combination of features) itself, as well as to features that achieve substantially the same technical effect (equivalent features). Equivalent features include, for example, features that are variations and achieve substantially the same result in substantially the same manner. Equivalent features include, for example, features that perform substantially the same function in substantially the same manner to achieve substantially the same result.

[0198] In this specification, various examples have been referenced to describe the characteristics of the examples using adjectives or adjective phrases. Such descriptions of the characteristics associated with the examples indicate that the characteristics exist exactly as described in some examples, and substantially as described in others.

[0199] In the above description, the described apparatus may alternatively or additionally include apparatus for a distributed system (e.g., a client / server apparatus system) that includes apparatus in some other examples. In examples where the provided apparatus forms (or the method is implemented as) a distributed system, each apparatus forming a component and / or part of the system provides (or implements) one or more features that collectively implement the examples of this disclosure. In some examples, the apparatus is reconfigured by an entity other than its original manufacturer to implement the examples of this disclosure by being provided with additional software (e.g., by a user downloading such software), which, when executed, causes the apparatus to implement the examples of this disclosure (such implementation is either entirely implemented by the apparatus or as part of a system of apparatus as described above).

[0200] The foregoing description illustrates some examples of this disclosure; however, those skilled in the art will recognize possible alternative structures and methodological features that provide equivalent functionality to the specific examples of such structures and features described above, and for the sake of brevity and clarity, have been omitted from the foregoing description. Nevertheless, the foregoing description should be understood to implicitly include references to such alternative structures and methodological features that provide equivalent functionality, unless such alternative structures or methodological features are explicitly excluded in the foregoing description of the examples of this disclosure.

[0201] While efforts have been made in the foregoing specification to draw attention to those features of the examples of this disclosure that are considered particularly important, it should be understood that the applicant claims protection for any patentable features or combinations thereof referenced above and / or shown in the accompanying drawings, whether or not they have been specifically highlighted.

[0202] Examples in this disclosure and the appended claims may be appropriately combined in any manner obvious to a person skilled in the art. Individual references to “example,” “in some examples,” etc., in the specification do not necessarily refer to the same example and are not mutually exclusive unless stated and / or obvious to a person skilled in the art from the specification. For example, a feature, structure, process, block, step, action, etc., described in one example may also be included in other examples, but not necessarily.

[0203] Each claim is incorporated herein as further disclosure, and these claims are embodiments of this disclosure. Furthermore, while the claims herein are provided to include specific dependencies, it is contemplated that any claim may be dependent on any other claim; and any such alternative embodiments and their equivalents are also within the scope of this disclosure, to the extent that any alternative embodiments arise by combining, integrating, and / or omitting features of various claims and / or changing the dependencies of the claims.

Claims

1. An apparatus comprising: A component for receiving one or more sets of Protocol Data Units (PDUs) from a first core network entity for transmission by the device to a User Equipment (UE); Components for determining, for the one or more PDU sets, whether a PDU set is considered to have been successfully transmitted from the device or unsuccessfully transmitted to the UE, wherein the determination is based at least in part on the number of PDUs in the PDU set that have been successfully transmitted from the device or unsuccessfully transmitted to the UE; A component for determining the number of the one or more PDU sets that are considered to have been successfully transmitted or not successfully transmitted; as well as A component for sending information to a second core network entity or the first core network entity indicating the number of the one or more PDU sets that are considered to have been successfully transmitted or not successfully transmitted.

2. The apparatus of claim 1, wherein the information indicating the number of the one or more PDU sets considered to have been successfully transmitted or not successfully transmitted is at least partially based on the total number of the one or more PDU sets to be transmitted to the UE, and wherein the information indicates a ratio of: The number of the one or more PDU sets that were considered to have been successfully transmitted or not successfully transmitted, and The total number of the one or more PDU sets to be transmitted by the device to the UE.

3. The apparatus according to any of the preceding claims, wherein the information indicates a PDU set loss rate (PSLR) measurement, wherein the PSLR measurement indicates the ratio of PDU sets that were successfully transmitted or not successfully transmitted.

4. The apparatus according to any of the preceding claims, wherein the determination of whether the PDU set is considered to have been successfully transmitted or not successfully transmitted is based on whether the proportion of PDUs in the PDU set that were successfully transmitted exceeds a threshold.

5. The apparatus according to any of the preceding claims further includes a component for receiving configuration information from the second core network entity, the configuration information being used to configure the apparatus to perform the PSLR measurement.

6. The apparatus of claim 5, wherein the configuration information includes information for configuring the apparatus to perform at least one or more of the following: Determine whether the PDU set is considered successfully transmitted or not. Determine the number of the one or more PDU sets that are considered to have been successfully transmitted or not successfully transmitted; Send the information to the first or second core network entity.

7. The apparatus according to any one of claims 5 to 6, wherein the configuration information includes information indicating the entity to which the information is to be sent; and wherein the information is sent to the entity.

8. The apparatus according to any one of claims 5 to 7, wherein the configuration information includes information indicating that the transmission of the information will be based on a threshold determined by the apparatus to have been exceeded; and wherein the threshold is based at least in part on the number of the one or more PDU sets that are considered to have been successfully transmitted or not successfully transmitted.

9. The apparatus of claim 8, wherein the configuration information includes information indicating the threshold.

10. The apparatus according to any one of claims 5 to 9, wherein the configuration information includes information indicating a time interval; and wherein the execution of at least one or more of the following is at least partially based on the time interval: Determine whether the PDU set is considered successfully transmitted or unsuccessfully transmitted, or Determine the number of the one or more PDU sets that are considered to have been successfully transmitted or not successfully transmitted.

11. The apparatus according to any one of claims 5 to 10, wherein the configuration information includes information indicating a first number of PDU sets; and wherein the execution of at least one or more of the following is at least partially based on the first number of PDU sets: Determine whether the PDU set is considered successfully transmitted or unsuccessfully transmitted, or Determine the number of the one or more PDU sets that are considered to have been successfully transmitted or not successfully transmitted.

12. The apparatus according to any one of claims 5 to 11, wherein the configuration information includes information indicating one or more metrics to be reported to the first or second core network entity.

13. The apparatus according to any preceding claim further includes a component for receiving configuration information from the second core network entity, the configuration information being configured to perform at least one or more of the following: For each of the multiple PDU sets to be transmitted from the device to the UE, determine: The total number of PDUs in each set of PDUs, and The number of PDUs in each PDU set that have been successfully or unsuccessfully transmitted by the device to the UE; Determine one or more metrics that indicate the transmission quality of the PDU set from the device to the UE, wherein the metrics are determined at least in part based on: The total number of PDUs in each set of PDUs, and The number of PDUs in each PDU set that have been successfully or unsuccessfully transmitted to the UE by the device.

14. A method comprising: Receive one or more sets of Protocol Data Units (PDUs) from the first core network entity for the device to transmit to the User Equipment (UE). For the one or more PDU sets, a PDU set is determined to be considered successfully transmitted from the device or unsuccessfully transmitted to the UE, wherein the determination is based at least in part on the number of PDUs in the PDU set that have been successfully transmitted from the device or unsuccessfully transmitted to the UE; Determine the number of the one or more PDU sets that are considered to have been successfully transmitted or not successfully transmitted; as well as Send information to the second core network entity or the first core network entity indicating the number of the one or more PDU sets that are considered to have been successfully transmitted or not successfully transmitted.

15. An apparatus comprising: A component for receiving configuration information from a first core network entity for reporting first information to a second core network entity, the first information indicating the number of one or more PDU sets that are considered to have been successfully or unsuccessfully transmitted to a user equipment (UE) by a radio access network (RAN) node; A component for receiving the first information from the RAN node; as well as Components used to report the first information to the second core network entity.

Images