Timing configuration for event based data collection and datareporting for ai / ml

Abstract

A method (600) implemented by a requesting node (430). The method comprises transmitting (610) a data collection request to a reporting node (440). The data collection request comprises one or more information elements indicating an instruction for transmitting reports after an event. The method further comprises receiving (620) a report from the reporting node (440) after one or more occurrences of the event.figure for publication:

Description

[0001] TIMING CONFIGURATION FOR EVENT BASED DATA COLLECTION AND DATA REPORTING FOR AI / ML

[0002] RELATED APPLICATIONS

[0003] This application claims the benefit of U.S. Provisional Application No. 63 / 571063 filed 28 March 2024, the entire disclosure of which is hereby incorporated by reference herein.

[0004] TECHNICAL FIELD

[0005] The present disclosure generally relates to the field of communication networks and is more particularly directed to data collection within a communications network.

[0006] BACKGROUND

[0007] Data collection is a procedure a radio access network (RAN) node uses to request information reports needed to support, e.g., artificial intelligence / machine learning (AI / ML) in next generation radio access network (NG-RAN). The procedure uses non-user equipment (non-UE) associated signaling. According to existing data collection procedures, after a triggering event, either singular or periodic reporting is allowed. In singular reporting, a report is transmitted after the first triggering event. In periodic reporting, a report corresponding to each occurrence of a triggering event is sent in the following scheduled reporting message, which is part of a periodic series of reporting messages.

[0008] SUMMARY

[0009] Existing data collection procedures are generally limited to only singular or periodic reporting. These limited reporting options are inflexible and prevent efficient and / or timely reporting in the wireless network. For example, in existing data collection procedures, it is impossible to send the reporting message immediately after an event triggering the reporting and to continue doing so for each subsequent occurrence of the triggering event.

[0010] Accordingly, embodiments of the present disclosure provide procedures for data collection. A requesting node transmits a data collection request to a reporting node. The request comprises one or more information elements indicating one or more instructions for transmitting reports after an event. After the request, and after one or more occurrences of the event, the requesting node receives a report from the reporting node.

[0011] Some embodiments include a method implemented by a requesting node. The method comprises transmitting a data collection request to a reporting node. The data collection request comprises one or more information elements indicating an instruction for transmitting reports after an event. The method further comprises receiving a report from the reporting node after one or more occurrences of the event.

[0012] In some embodiments, the event is any one of a handover, mobility, conditional handover, PSCell addition, PSCell change, or a user equipment trajectory.

[0013] In some embodiments, the mobility is due to energy saving or load balancing. In some embodiments, the instruction specifies a time frame for the requesting node to receive the report.

[0014] In some embodiments, the time frame is without delay.

[0015] In some embodiments, the time frame is within a predetermined time.

[0016] In some embodiments, the time frame is after a predetermined time.

[0017] In some embodiments, receiving comprises receiving the report after the event has occurred a predetermined number of times, wherein the predetermined number of times and the event are indicated by the instruction.

[0018] In some embodiments, the data collection request comprises a request that a user equipment, UE, transmit data associated with the one or more occurrences of the event as a group report.

[0019] In some embodiments, the data collection request requests that the UE transmit the group report upon determining that signal quality is better than a threshold.

[0020] In some embodiments, the method further comprises receiving a plurality of reports in a same message and in accordance with the instruction.

[0021] In some embodiments, the method further comprises requesting a user equipment (UE) to perform group reporting for a set of data associated with an event type, wherein the group reporting is performed when a coverage measured by the UE is higher than a threshold, or when an interference measured by the UE is lower than a threshold.

[0022] Other embodiments include a requesting node configured to transmit a data collection request to a reporting node. The data collection request comprises one or more information elements indicating an instruction for transmitting reports after an event. The requesting node is further configured to receive a report from the reporting node after one or more occurrences of the event.

[0023] In some embodiments, the requesting node is further configured to perform any one of the requesting node methods described above.

[0024] Other embodiments include a requesting node comprising processing circuitry and a memory. The memory containing instructions executable by the processing circuitry whereby the requesting node is configured to transmit a data collection request to a reporting node. The data collection request comprises one or more information elements indicating an instruction for transmitting reports after an event. The requesting node is further configured to receive a report from the reporting node after one or more occurrences of the event.

[0025] In some embodiments, the requesting node is further configured to perform any one of the requesting node methods described above.

[0026] Other embodiments include a computer program comprising instructions which, when executed on processing circuitry of a requesting node, cause the processing circuity to carry out any one of the requesting node methods described above. Other embodiments include a carrier containing the computer program. The carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

[0027] Other embodiments include a method implemented by a reporting node. The method comprises receiving a data collection request from a requesting node. The data collection request comprises one or more information elements indicating an instruction for transmitting reports after an event. The method further comprises transmitting a report to the requesting node after one or more occurrences of the event.

[0028] In some embodiments, the event is any one of a handover, mobility, conditional handover, PSCell addition, PSCell change, or a user equipment trajectory.

[0029] In some embodiments, the mobility is due to energy saving or load balancing.

[0030] In some embodiments, the instruction specifies a time frame for the requesting node to receive the report.

[0031] In some embodiments, the time frame is without delay.

[0032] In some embodiments, the time frame is within a predetermined time.

[0033] In some embodiments, the time frame is after a predetermined time.

[0034] In some embodiments, the transmitting comprises transmitting the report after the event has occurred a predetermined number of times, wherein the predetermined number of times and the event are indicated by the instruction.

[0035] In some embodiments, data collection request comprises a request that a user equipment, UE, transmit data associated with the one or more occurrences of the event as a group report.

[0036] In some embodiments, the data collection request requests that the UE (110) transmit the group report upon determining that signal quality is better than a threshold.

[0037] In some embodiments, the method further comprises transmitting a plurality of reports in the same message and in accordance with the instruction.

[0038] Other embodiments include a reporting node configured to receive a data collection request from a requesting node. The data collection request comprises one or more information elements indicating an instruction for transmitting reports after an event. The reporting node is further configured to transmit a report to the requesting node after one or more occurrences of the event.

[0039] In some embodiments, the reporting node is further configured to perform any one of the reporting node methods described above.

[0040] Other embodiments include a reporting node comprising processing circuitry and a memory. The memory containing instructions executable by the processing circuitry whereby the reporting node is configured to receive a data collection request from a requesting node. The data collection request comprises one or more information elements indicating an instruction for transmitting reports after an event. The reporting node is further configured to transmit a report to the requesting node after one or more occurrences of the event. In some embodiments, the reporting node is further configured to perform any of the reporting node methods described above.

[0041] Other embodiments include a computer program comprising instructions which, when executed on processing circuitry of a reporting node, causes the processing circuitry to carry out any of the reporting node methods described above.

[0042] Yet other embodiments include a carrier containing the computer program. The carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

[0043] BRIEF DESCRIPTION OF THE DRAWINGS

[0044] Aspects of the present disclosure are illustrated by way of example and are not limited by the accompanying figures with like references indicating like elements. In general, the use of a reference numeral should be regarded as referring to the depicted subject matter according to one or more embodiments, whereas discussion of a specific instance of an illustrated element will append a letter designation thereto (e.g., discussion of a RAN node 120, generally, as opposed to discussion of particular instances of RAN nodes 120a, 120b).

[0045] FIG. 1 is a schematic block diagram illustrating an example of a wireless communication network according to one or more embodiments of the present disclosure.

[0046] FIG. 2 is a schematic block diagram illustrating an example RAN according to one or more embodiments of the present disclosure.

[0047] FIG. 3 illustrates the overall architecture of an exemplary gNB according to some aspects of the present disclosure.

[0048] FIG. 4 illustrates a signaling diagram illustrating an exemplary data collection procedure.

[0049] FIG. 5 illustrates a signaling diagram illustrating an example data collection reporting procedure.

[0050] FIG. 6 is a flow diagram illustrating an example method performed by a requesting node according to some embodiments of the present disclosure.

[0051] FIG. 7 is a flow diagram illustrating an example method performed by a reporting node according to some embodiments of the present disclosure.

[0052] FIG. 8 is a schematic block diagram illustrating an example RAN node according to one or more embodiments of the present disclosure.

[0053] FIGS. 9A-9D are tables comprising example request message parameters for initiating a data collection request according to one or more embodiments of the present disclosure.

[0054] FIGS. 10A-10D are tables comprising example data collection update message parameters for data collection reporting according to one or more embodiments of the present disclosure.

[0055] FIGS. 11A-11C are tables comprising example message parameters for data collection messages implemented in XnAP (3GPP TS 38.423 version 18.0.0) according to one or more embodiments of the present disclosure. DETAILED DESCRIPTION

[0056] The present invention may, of course, be carried out in other ways than those specifically set forth herein without departing from essential characteristics of the invention. The present embodiments are to be considered in all respects as illustrative and not restrictive, and all changes coming within the meaning and equivalency range of the appended claims are intended to be embraced therein.

[0057] The examples provided herein may be given that are commonly associated with a particular generation of Third Generation Partnership Project (3GPP) networks. For example, the term gNB (a term that was first used in connection with 5G networks) may be used to refer to a RAN node of a 5G RAN. These specific examples are given solely for the purpose of illustration and should not be interpreted to exclude other network elements, whether presently known or to be developed in the future. Indeed, the embodiments described herein may be applied to any generation of the 3GPP network unless otherwise specified.

[0058] FIG. 1 is a schematic block diagram illustrating an example of a UE 110 connected to a wireless communication network 100. The wireless communications network 100 comprises a core network 160 and a RAN represented in this example by a first RAN node 120a and a second RAN node 120b. Each RAN node 120a and 120b serves a respective coverage area 130a and 130b, in which the UE 110 may access the core network 160. The core network 160 comprises one or more core network nodes 140 that support the UE 110 in accessing core network services and / or resources provided by an external data network 170.

[0059] FIG. 2 is a schematic block diagram illustrating the RAN 150 described above. As previously noted, the RAN 150 comprises RAN nodes 120a and 120b. The RAN nodes 120a and 120b are interconnected. Each RAN node 120a, 120b may support communication with one or more UEs 110 using one or more Radio Access Technologies (RATs) (e.g., Long Term Evolution (LTE), New Radio (NR)). In this regard, each RAN node 120a, 120b may support Frequency Division Duplexing (FDD), Time Division Duplexing (TDD), Orthogonal Frequency Division Multiplexing (OFDM), or any combination thereof (e.g., dual mode FDD / TDD).

[0060] In this example, RAN node 120a comprises a Centralized Unit (CU) 250 and one or more Distributed Units (DUs) 220a, 220b. The CU 250 is connected to each of the DUs 220a and 220b. The CU 250 and the DUs 220a and 220b may be configured to handle different parts of the radio protocol stack. For example, a CU 250 may support higher protocol layers (e.g., Radio Resource Control (RRC)). A DU 220a, 220b may provide support for lower protocol layers (e.g., Radio Link Control (RLC), Medium Access Control (MAC)).

[0061] Either or both RAN nodes 120a and 120b may be a gNodeB (gNB). In such an example, the CU 250 may be a gNB-CU, and each DU 220 may be a gNB-DU. The gNB-CU may be connected to each of the gNB-DUs via an F1 interface. The core network 160 may be a Fifth Generation Core (5GC), and each RAN node 120a, 120b may be connected to the core network 160 over a Next Generation (NG) interface (e.g., in accordance with a traditional NG- RAN architecture). Further, the RAN nodes 120a and 120b may be interconnected by one or more Xn interfaces, e.g., an Xn User Plane (Xn-U) interface and an Xn Control Plane (Xn-C) interface.

[0062] According to other embodiments, either or both RAN nodes 120a and 120b may be a Next Generation eNodeB (ng-eNB). In such an ng-eNB, the CU 250 may be an ng-eNB-CU and each DU 220 may be an ng-eNB-DU(s). In such an embodiment, the ng-eNB-CU and an ng-eNB-DU may be connected via a W1 interface. The core network 160 may be an Evolved Packet Core (EPC), and each RAN node 120a, 120b may be connected to the EPC via one or more S1 interfaces (e.g., an S1 User Plane (S1-U) interface and an S1-Control Plane (S1-C) interface.

[0063] The RAN 150 may, in some embodiments, support Evolved Non-standalone Dual Connectivity (EN-DC) in which one of the RAN node 120a is a gNB and the other RAN node 120b is an eNB. The NG and Xn-C interfaces for a gNB comprising a gNB-CU and one or more gNB-DUs terminate in the gNB-CU. S1-U and X2-C interfaces for a gNB comprising a gNB-CU and gNB-DUs terminate in the gNB-CU. The gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB.

[0064] FIG. 3 illustrates the overall architecture of a gNB 260. As shown, a feature of the gNB architecture includes control plane / user plane separation. A gNB 260 may comprise a CU 250 for the control plane (i.e., a gNB-CU-CP 265), one or more CUs 250 for the user plane (i.e., one or more gNB-CU-UPs 270), and one or more gNB-DUs 280. The gNB-CU-CP 265 is connected to each gNB-DU 280 through an F1-C interface. One or more of the gNB-CU-UPs 270 may be connected to one or more gNB-DUs 280 through an F1-U interface. The gNB-CU-UP 265 is connected to each gNB-CU-CP 270 through an E1 interface. A gNB-DU 280 is connected to only one gNB-CU-CP 265. A gNB-CU-UP 270 is connected to only one gNB-CU-CP 265.

[0065] In some embodiments, a gNB-DU 280 may comprise a lower DU 290 and an upper DU 285 connected by a fronthaul interface. The lower DU 290 handles the Physical Layer (PHY) protocol and Radio Frequency (RF) aspects, while the upper DU 285 handles RLC and MAC. In some embodiments, the upper DU 285 may be called an O-DU, whereas the lower DU may be called an O-DU.

[0066] Data Collection Reporting Initiation

[0067] FIG. 4 illustrates a signaling diagram illustrating an exemplary successful operation of a data collection procedure according to some embodiments.

[0068] FIGS. 4-5 include a requesting node 430, which may be a RAN node 120a, and a reporting node 440, which may be a RAN node 120b.

[0069] Requesting node 430 initiates the procedure by sending the DATA COLLECTION REQUEST MESSAGE 410 to reporting node 440 to start or stop information reporting. Upon receipt, reporting node 440 initiates the requested information reporting according to the parameters given in the request if a Registration Request Information Element (IE) is set to "start.” The reporting node 440 stops all measurements and predictions and terminates the reporting if the Registration Request IE is set to “stop.”

[0070] In some examples, the Registration Request IE is set to “start” in the DATA COLLECTION REQUEST MESSAGE 410. The Report Characteristics IE indicates cell-specific information reporting. In this case, the Cell to Report List for Data Collection IE is included in the DATA COLLECTION RESPONSE MESSAGE 420.

[0071] In some examples, the reporting node 440 provides all of the requested information, and it initiates information reporting as requested by requesting node 430 and responds with a DATA COLLECTION RESPONSE MESSAGE 420.

[0072] In some examples, reporting node 440 provides some but not all of the requested information. In this case, the reporting node 440 initiates information reporting for the admitted requested information. The report can include a Node Measurement Initiation Result List IE, a Per Cell Measurement Initiation Result List IE or both in the DATA COLLECTION RESPONSE MESSAGE 420.

[0073] In some examples, a Reporting Periodicity IE is present in the DATA COLLECTION REQUEST MESSAGE 410. The Reporting Periodicity IE indicates a periodicity for reporting configured measurement objects. The reporting node 440 reports only once unless otherwise requested within the Reporting Periodicity IE.

[0074] In some examples, a Requested Prediction Time IE is present in the DATA COLLECTION REQUEST MESSAGE. The Requested Prediction Time IE indicates the specific point in time to which the prediction of the requested information applies. The reporting node 440 considers the Requested Prediction Time IE when generating the requested predicted information.

[0075] In some examples, a UE Trajectory Collection Configuration IE is present in the DATA COLLECTION REQUEST MESSAGE 410. In that case, the reporting node 440 configures UE trajectory collection and reporting. The reporting node 440 reports the UE trajectory only once. Reporting node 440 terminates the collection when the time since UE 110 was successfully handed over to reporting node 440 is equal to the value of the Collection Time Duration IE, or when the number of visited cells within reporting node 440 is equal to the value of the Number of Visited Cells IE if included, or if the UE moves to RRCJNACTIVE or RRCJDLE state, or if the UE 110 is handed over to a cell belonging to a RAN node different from the reporting node 440. The result of the UE trajectory collection is reported in the following available DATA COLLECTION UPDATE MESSAGE.

[0076] In some examples, the UE 110 Performance Collection Configuration IE is present in the DATA COLLECTION REQUEST MESSAGE 410. In that case, the reporting node 440 takes into account the configuration of UE 110 performance collection and reporting. Reporting node 440 terminates the collection when at least one of the times since UE 110 was successfully handed over to reporting node 440 is equal to the value of the Collection Time Duration IE, when the UE 110 moves to RRCJNACTIVE or RRCJDLE state or the UE 110 is handed over to another cell, is fulfilled. The UE 110 performance collection result is reported in the next available DATA COLLECTION UPDATE MESSAGE.

[0077] Interaction with the Data Collection Reporting Procedure

[0078] When starting a measurement, the Report Characteristics IE in the DATA COLLECTION REQUEST MESSAGE 410 indicates the type of objects on which the RAN node 120b performs measurements or predictions.

[0079] In some examples, the reporting node 440 includes in the DATA COLLECTION UPDATE MESSAGE the Synchronization Signal Block (SSB) Area Radio Resource Status List IE, excluding the downlink (DL) scheduling Physical downlink Control Channel (PDCCH) control channel element (CCE) usage IE and uplink (UL) scheduling PDCCH CCE usage IE, included in the Predicted Radio Resource Status IE if the first bit, "Predicted Radio Resource Status" of the Report Characteristics IE included in the DATA COLLECTION REQUEST message is set to "1".

[0080] In some examples, the reporting node 440 includes in the DATA COLLECTION UPDATE MESSAGE 510 the Predicted Number of Active UEs IE if the second bit, "Predicted Number of Active UEs" of the Report Characteristics IE included in the DATA COLLECTION REQUEST MESSAGE 410 is set to "1".

[0081] In some examples, the reporting node 440 includes the Predicted RRC Connections IE in the DATA COLLECTION UPDATE MESSAGE 510 if the third bit, "Predicted RRC Connections" of the Report Characteristics IE, included in the DATA COLLECTION REQUEST MESSAGE 410, is set to "1".

[0082] In some examples, the reporting node 440 includes in the DATA COLLECTION UPDATE MESSAGE 510 the Average UE Throughput DL IE if the fourth bit, "Average UE Throughput DL" of the Report Characteristics IE, included in the DATA COLLECTION REQUEST MESSAGE 410, is set to "1".

[0083] In some examples, the reporting node 440 includes the Average UE Throughput UL IE in the DATA COLLECTION UPDATE MESSAGE 510 if the fifth bit, "Average UE Throughput UL" of the Report Characteristics IE included in the DATA COLLECTION REQUEST MESSAGE 410, is set to "1".

[0084] In some examples, the reporting node 440 includes in the DATA COLLECTION UPDATE MESSAGE 510 the Average Packet Delay IE if the sixth bit, "Average Packet Delay" of the Report Characteristics IE, included in the DATA COLLECTION REQUEST MESSAGE 410, is set to "1".

[0085] In some examples, the reporting node 440 includes in the DATA COLLECTION UPDATE MESSAGE 510 the Average Packet Loss DL IE if the seventh bit, "Average Packet Loss DL" of the Report Characteristics IE, included in the DATA COLLECTION REQUEST MESSAGE 410, is set to "1". In some examples, the reporting node 440 includes the Energy Cost IE in the DATA COLLECTION UPDATE MESSAGE 510 if the eighth bit, "Energy Cost" of the Report Characteristics IE included in the DATA COLLECTION REQUEST MESSAGE 410, is set to "1".

[0086] In some examples, the reporting node 440 includes the Measured UE Trajectory in the DATA COLLECTION UPDATE MESSAGE 510 if the ninth bit, "Measured UE Trajectory" of the Report Characteristics IE included in the DATA COLLECTION REQUEST MESSAGE 410, is set to "1".

[0087] Data Collection Request

[0088] The DATA COLLECTION REQUEST MESSAGE 410 is sent by requesting node 430 to the reporting node 440 to initiate the requested information reporting according to the parameters given in the message.

[0089] Data Collection Reporting

[0090] Data collection reporting is initiated by reporting node 440 to report information accepted by requesting node 430 following a successful Data Collection Reporting Initiation procedure for the purpose of, e.g., AI / ML in RAN. The procedure uses non-UE-associated signaling.

[0091] FIG. 5 illustrates a flowchart illustrating an example of the successful operation of a data collection reporting procedure according to some embodiments. Reporting node 440 reports the accepted information in DATA COLLECTION UPDATE MESSAGE 510. The accepted information is the information that was successfully initiated during the preceding Data Collection Reporting Initiation procedure. A DATA COLLECTION UPDATE MESSAGE 510 is sent by reporting node 440 to requesting node 430 to report the requested information.

[0092] Embodiments of the current disclosure enable a requesting node 430 to request measurement reports from a reporting node 440. Measurement reports may have characteristics such as reporting triggered by the occurrence of an event. Other characteristics include reporting after the occurrence of the event. Additionally, or alternatively, characteristics may include reporting repeated for each subsequent event occurrence for a certain time or until a certain number of event occurrences is reached.

[0093] Because certain types of events, such as handovers, can occur in bursts, the embodiments of the present disclosure give the requesting network node a means to protect itself and the reporting node from transmitting reports in bursts.

[0094] Embodiments of the present disclosure enable the reporting of data associated with the occurrence of a specified type of event in batches. For example, the requested data is reported after a certain number of event occurrences or after a certain amount of time has passed after the event.

[0095] One or more embodiments of the present disclosure, an I E(s) is included in the DATA COLLECTION REQUEST MESSAGE 410 to instruct the reporting node 440 to report data immediately after the occurrence of an event. The reporting may be triggered for each subsequent occurrence of the event until a certain number of event occurrences is reached or until a certain amount of time has elapsed. In some examples, when events occur in bursts, the requesting node 430 may include an IE(s) in the DATA COLLECTION REQUEST MESSAGE 410 to instruct the reporting node 440 on how to batch the reporting of data corresponding / triggered by the occurrences of the events.

[0096] Embodiments of the present disclosure provide flexibility in controlling the timing of reporting data related to a triggering event.

[0097] For reporting data associated with or triggered by the occurrence of an event, this enables the requesting node 430 to request the reporting node 440 to either send the report immediately after the occurrence of the event or differ for a certain time the transmission of the report and to proceed likewise for each report related to a subsequent occurrence of the event.

[0098] By receiving the requested data immediately after the occurrence of an event, the requesting node 430 can better understand the impact of its actions in relation to that event.

[0099] By allowing the reporting node 440 to wait for a certain period of time before sending the report to the requesting node 430. Embodiments of the present disclosure allow the reporting node 440 to bundle several small yet frequent reports in a single larger report, which will result in a lower signaling overhead and a reduced signaling messages peak rate.

[0100] In some examples, the requesting node 430 (e.g., RAN node 120a) sends a request to the reporting node 440 (e.g., a RAN node 120b), and the request comprises a configuration indicating an event type (e.g., mobility triggered due energy saving reasons) and a set of data to be reported (e.g., UE 110 performance) upon the occurrence of the event. The configuration provides the reporting node 440 with an indication, instructing (or at least guiding) the reporting node 440 on, for example, when to report the data in relation to the occurrence of the event, i.e., immediate reporting I differed reporting. In the examples, the configuration provides an indication of how many occurrences of the event or for how long the reporting should be repeated in case of subsequent occurrences of the event. In other examples, the configuration instructs the reporting node 440 on how to group the requested data associated with the event type in a single reporting towards the requesting node 430.

[0101] In one embodiment, the requesting node 430 includes an IE in the request, which indicates the number of occurrences of the event for which data reporting should be performed by the reporting node 440.

[0102] In another embodiment, the requesting node 430 may include in the request an IE that indicates to the reporting node 440 the time frame or the time duration during which the second network node should report data for each occurrence of the event.

[0103] To efficiently collect data associated with a common use case or event type (e.g., data associated with mobility procedures initiated by a requesting node 430 towards a reporting node 440 due to energy savings), the reporting of such data is organized in a way that allows to reduce the amount of signaling messages exchanged between the involved nodes. The assumption here is that the amount of data being requested and associated with a single occurrence of the given event type allows performing group reporting, i.e., reporting the data associated with multiple occurrences of the same event type.

[0104] According to some embodiments, a requesting node 430 initiates a request for group reporting for a certain event type towards a reporting node 440. The elements of the request pertaining to the solution, i.e., the “group reporting” and the “event type,” can be indicated explicitly or implicitly, as detailed in the alternatives described below.

[0105] In other embodiments of the present disclosure, the “group reporting” and the “event type” are implicit, and the reporting node 440, upon receiving a request comprising a certain combination of parameters (e.g., the request for measurements X, Y, Z, or predictions X’, Y,’ Z,’ or a request for certain measurements / predictions together with parameters concerning the collection of the above measurements / predictions), then the second network node initiates group reporting. Regardless of the option (or combination of options) selected, the technical effect of the group reporting performed from the reporting node 440 to the requesting node 430 can greatly reduce the amount of signaling between the RAN nodes.

[0106] The methods can be extended to group reporting of data associated with more than just one event type. This allows, e.g., group reporting of UE 110 performance after a handover due to load balancing and handover due to energy saving. So long as the message size of the protocol interface is used to convey group reporting, this approach does not require message fragmentation. Further extension of the methods (applicable to any interface) is also applicable to the case where the size of the message caused by the group reporting surpasses the limit of the protocol interface, and more than just one message is needed to convey the data. In this case, the advantage of the solution is reduced compared to sending a single message for group reporting.

[0107] The methods can be extended to group reporting over the air interface, i.e., between a UE 110 and a requesting node 430. In this case, the reporting of data in a group enables an even greater benefit. Indeed, if the requesting node 430 requests the UE 110 to perform group reporting for a set of data associated with a given event type, only when the coverage experienced by the UE 110 is good (or good enough), e.g., when the coverage measured by the UE 110 (e.g., in terms of RSRP) is higher than a threshold, or when the interference measured by the UE 110 (e.g., in terms of RSSI) is lower than a threshold, then group reporting avoid repetitive signaling over the air, meaning that precious air interface resources can be used more efficiently.

[0108] In some embodiments, the requesting node 430 issues a request containing an explicit indication of at least one event type for which the group reporting is requested and a set of data requested for an individual instance of the event type. In this case, the fact that group reporting is requested can be provided implicitly (e.g., a certain combination of data being requested constitutes an implicit indication that group reporting is requested). In another embodiment, instead of explicitly indicating the event type for which group reporting is requested, the requesting node 430 simply indicates that group reporting is requested. In this case, one or more parameters included in the same request can be used to implicitly indicate to the request receiver the event type to which the group reporting refers.

[0109] In another embodiment, the first network node explicitly indicates to the reporting node 440 that group reporting is requested and at least one event type for which group reporting is requested.

[0110] In another embodiment, the requesting node 430 indicates to the reporting node 440 that group reporting is requested by comprising in the request one or more dedicated parameters (for instance, a “reporting period deferral” or an “Allowed report deferral duration,” or “Deferred reporting”), indicating that reporting (of the data being requested) can be performed after a certain time, and / or that deferred reporting is allowed / requested / preferred. Any combination of the above options is possible.

[0111] In one embodiment, the request sent by the requesting node 430 includes a minimum and / or a maximum amount of time for starting and / or for ending the collection of data to be reported in the form of group reporting.

[0112] In one embodiment, the requesting node 430 includes in the request an indication of a minimum and / or a maximum number of instances of individual (e.g., per UE) reporting to be included in a single group reporting.

[0113] In one embodiment, the request sent by the requesting node 430 includes a minimum and / or maximum amount of time for collecting data worth a single group reporting (e.g., a reference time interval for group reporting), based on which the reporting node 440 is requested to collect data associated with one (or a certain number of) group reporting.

[0114] The event type for which group reporting can be any but not limited to (or a combination of) mobility, a conditional handover, a PSCell addition, a PSCell change, a mobility due to energy saving, a mobility due to load balancing, and / or a UE 110 trajectory.

[0115] FIG. 6 is a flow diagram illustrating a method 600 for receiving a report message performed by a requesting node 430 according to some embodiments of the present disclosure. Method 600, implemented by a requesting node 430, comprises transmitting 610 a data collection request to a reporting node 440. The data collection request comprises one or more information elements indicating an instruction for transmitting reports after an event. The method 600 further comprises receiving 620 a report from the reporting node 440 after one or more occurrences of the event.

[0116] According to some embodiments, the event is any one of a handover, mobility, conditional handover, PSCell addition, PSCell change, or a user equipment trajectory.

[0117] According to some embodiments, mobility is any one of a mobility due to energy saving, or mobility due to load balancing. According to some embodiments, the instruction specifies a time frame for the requesting node 430 to receive the report.

[0118] According to some embodiments, the time frame is without delay.

[0119] According to some embodiments, the time frame is within a predetermined time.

[0120] According to some embodiments, the time frame is after a predetermined time.

[0121] According to some embodiments, the receiving comprises receiving the report after the event has occurred a predetermined number of times, wherein the predetermined number of times and the event are indicated by the instruction.

[0122] According to some embodiments, the method further comprises receiving a plurality of reports in a same message and in accordance with the instruction.

[0123] FIG. 7 is a flow diagram illustrating a method for transmitting a report message performed by a reporting node 440 according to some embodiments of the present disclosure. Method 700, implemented by a reporting node 440, comprises receiving 710 a data collection request from a requesting node 430, wherein the data collection request comprises one or more information elements indicating an instruction for transmitting reports after an event. The method 700 further comprises transmitting 720 a report to the requesting node 430 after one or more occurrences of the event.

[0124] According to some embodiments, the event is any one of a handover, mobility, conditional handover, PSCell addition, PSCell change, or a user equipment trajectory.

[0125] According to some embodiments, mobility is any one of a mobility due to energy saving or load balancing.

[0126] According to some embodiments, the instruction specifies a time frame for the requesting node (430) to receive the report.

[0127] According to some embodiments, the time frame is without delay.

[0128] According to some embodiments, the time frame is within a predetermined time.

[0129] According to some embodiments, the time frame is after a predetermined time.

[0130] According to some embodiments, the transmitting comprises transmitting the report after the event has occurred a predetermined number of times, wherein the predetermined number of times and the event are indicated by the instruction.

[0131] According to some embodiments, the method further comprises transmitting a plurality of reports in a same message and in accordance with the instruction.

[0132] The requesting node 430 may be configured (e.g., by the processing circuitry 810) to perform the method 600 described above.

[0133] The reporting node 440 may be configured (e.g., by the processing circuitry 810) to perform the method 700 described above.

[0134] Still, other embodiments include a control program 840 comprising instructions that, when executed on processing circuitry 810 of a reporting node 430, cause the reporting node 430 to carry out the method 600 described above. Still, other embodiments include a control program 840 comprising instructions that, when executed on processing circuitry 810 of a requesting node 440, cause the requesting node 440 to carry out the method 700 described above.

[0135] Yet other embodiments include a carrier containing the control program 740. The carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

[0136] FIG. 8 shows a RAN node 120 (e.g., a requesting node 430, a reporting node 440, a DU 220, a CU 250) in accordance with some embodiments. As used herein, a RAN Node refers to a device capable, configured, arranged, and / or operable to communicate wirelessly with network nodes and / or other RAN nodes.

[0137] The RAN node 120 includes processing circuitry 810 that is operatively coupled via a bus 804 to an interface circuitry 830, memory circuity 820, an interface circuitry 830, and / or any other component or any combination thereof. Certain RAN nodes 120 may utilize all or a subset of the components shown in FIG. 8. The level of integration between the components may vary from one RAN node to another RAN node. Further, certain RAN nodes 120 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0138] The processing circuitry 810 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory circuitry 820. The processing circuitry 810 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 810 may include multiple central processing units (CPUs).

[0139] The memory 820 may be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 820 includes one or more computer programs, 840, configured to control the operation of the RAN node 120 in at least some respects. The memory 820 may additionally or alternatively include other software components, such as an operating system, application, widget, gadget engine, and / or corresponding data. Indeed, the memory 820 may be stored for use by the RAN node 120 in any of a variety of operating systems or combinations of operating systems.

[0140] The memory 820 may be configured to include a number of physical drive units, such as a redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper-resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may, for example, be an embedded UICC (eUlCC), integrated UICC (iUICC), or a removable UICC commonly known as a ‘SIM card.’ The memory 820 may allow the RAN node 120 to access instructions, application programs, and the like stored on transitory or non-transitory memory media, off-load data, or upload data. An article of manufacture, such as one utilizing a communication system, may be tangibly embodied as or in the memory 820, which may be or comprise a device-readable storage medium.

[0141] The processing circuitry 810 may be configured to communicate with an access network or other network using the interface circuitry 830. The interface circuitry 830 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna. The interface circuitry 830 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE 110 or a network node in an access network). Each transceiver may include a transmitter 832 and / or a receiver 834 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 832 and receiver 834 may be coupled to one or more antennas (e.g., antenna) and may share circuit components, software, or firmware or alternatively be implemented separately.

[0142] In the illustrated embodiment, communication functions of the interface circuitry 830 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11 , Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0143] FIGS. 9A-D are tables comprising example request message parameters according to one or more embodiments of the present disclosure. The parameters are lEs sent by a requesting node 430 to a reporting node 440 to initiate the requested information reporting. The parameters include, but are not limited to, identification, measurement, and prediction data. FIGS. 10A-D are tables comprising example data collection update message parameters for according to one or more embodiments of the present disclosure. The parameters are encapsulated within the data collection update message sent from a reporting node 440 to a requesting node 430. The parameters include but are not limited to, identification, measurement, and prediction data.

[0144] FIGS. 11 A-C are tables comprising example message parameters implemented in XnAP (3GPP TS 38.423 version 18.0.0) according to one or more embodiments of the present disclosure.

[0145] Although the computing devices described herein (e.g., UEs, network nodes) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions, and methods disclosed herein. Determining, calculating, obtaining, or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information, or converting information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any such components may be implemented in software or firmware, and computationally intensive functions may be implemented in hardware.

[0146] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, the processing circuitry may provide some or all of the functionality without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the functionality described. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device but are enjoyed by the computing device as a whole and / or by end users and a wireless network generally.

Claims

CLAIMSWhat is claimed is:1 . 1 . A method (600) implemented by a requesting node (430), the method comprising: transmitting (610) a data collection request to a reporting node (440), wherein the data collection request comprises one or more information elements indicating an instruction for transmitting reports after an event; and receiving (620) a report from the reporting node (440) after one or more occurrences of the event.

2. The method of claim 1 , wherein the event is any one of a handover, mobility, a conditional handover, a PSCell addition, a PSCell change, or a user equipment trajectory.

3. The method of claim 2, wherein the mobility is due to energy saving or load balancing.

4. The method of any one of the preceding claims, wherein the instruction specifies a time frame for the requesting node (430) to receive the report.

5. The method of claim 4, wherein the time frame is without delay.

6. The method of claim 4, wherein the time frame is within a predetermined time.

7. The method of claim 4, wherein the time frame is after a predetermined time.

8. The method of any one of the preceding claims, wherein the receiving comprises receiving the report after the event has occurred a predetermined number of times, wherein the predetermined number of times and the event are indicated by the instruction.

9. The method of any one of claims 1-8, wherein the data collection request comprises a request that a user equipment, UE (110), transmit data associated with the one or more occurrences of the event as a group report.

10. The method of the preceding claim, wherein the data collection request requests that the UE (110) transmit the group report upon determining that signal quality is better than a threshold.11 . The method of any one of the preceding claims, further comprising receiving a plurality of reports in a same message and in accordance with the instruction.

12. A requesting node (430) configured to: transmit a data collection request to a reporting node (440), wherein the data collection request comprises one or more information elements indicating an instruction for transmitting reports after an event; and receive a report from the reporting node (440) after one or more occurrences of the event.

13. The requesting node of the preceding claim, further configured to perform the method of any one of claims 2-11.

14. A requesting node (430) comprising: processing circuitry (810) and a memory (820), the memory (820) containing instructions executable by the processing circuitry (810) whereby the requesting node (430) is configured to: transmit a data collection request to a reporting node (440), wherein the data collection request comprises one or more information elements indicating an instruction for transmitting reports after an event; and receive a report from the reporting node (440) after one or more occurrences of the event.

15. The requesting node of the preceding claim is further configured to perform the method of any one of claims 2-11 .

16. A computer program (840) comprising instructions which, when executed on processing circuitry (810) of a requesting node (430), cause the processing circuity (810) to carry out the method according to any one of claims 1-11.

17. A carrier containing the computer program (840) of the preceding claim, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

18. A method (700) implemented by a reporting node (440), the method comprising: receiving (710) a data collection request from a requesting node (430), wherein the data collection request comprises one or more information elements indicating an instruction for transmitting reports after an event; andtransmitting (720) a report to the requesting node (430) after one or more occurrences of the event.

19. The method of claim 18, wherein the event is any one of a handover, mobility, a conditional handover, a PSCell addition, a PSCell change, or a user equipment trajectory.

20. The method of claim 19, wherein the mobility is due to energy saving or load balancing.21 . The method of any one of claims 18-20, wherein the instruction specifies a time frame for the requesting node (430) to receive the report.

22. The method of claim 21 , wherein the time frame is without delay.

23. The method of claim 21 , wherein the time frame is within a predetermined time.

24. The method of claim 21 , wherein the time frame is after a predetermined time.

25. The method of any one of the preceding claims, wherein the transmitting comprises transmitting the report after the event has occurred a predetermined number of times, wherein the predetermined number of times and the event are indicated by the instruction.

26. The method of any one of claims 18-25, wherein the data collection request comprises a request that a user equipment, UE (110), transmit data associated with the one or more occurrences of the event as a group report.

27. The method of the preceding claim, wherein the data collection request requests that the UE (110) transmit the group report upon determining that signal quality is better than a threshold.

28. The method of any one of the preceding claims, further comprising transmitting a plurality of reports in the same message and in accordance with the instruction.

29. A reporting node (440) configured to: receive a data collection request from a requesting node (430), wherein the data collection request comprises one or more information elements indicating an instruction for transmitting reports after an event; andtransmit a report to the requesting node (430) after one or more occurrences of the event.

30. The reporting node (440) of the preceding claim, further configured to perform the method of any one of claims 19-28.31 . A reporting node (440) comprising: processing circuitry (810) and a memory (820), the memory (820) containing instructions executable by the processing circuitry (810) whereby the reporting node (440) is configured to: receive a data collection request from a requesting node (430), wherein the data collection request comprises one or more information elements indicating an instruction for transmitting reports after an event; and transmit a report to the requesting node (430) after one or more occurrences of the event.

32. The reporting node (440) of the preceding claim, further configured to perform the method of any one of claims 19-28.

33. A computer program (840) comprising instructions which, when executed on processing circuitry (810) of a reporting node (440), causes the processing circuitry (810) to carry out the method according to any one of claims 18-28.

34. A carrier containing the computer program (840) of the preceding claim, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer readable storage medium.

Images