Patent Application
20220103440
This application claims priority to Chinese patent application No. 201910010612.1 filed on Jan. 7, 2019, the content of which is hereby incorporated by reference in its entirety.
Embodiments of the disclosure relate to the technical field of communications, and particularly to a data processing method and a device.
With the coming of the Fifth-Generation (5G) era, various communication and processing technologies such as the mobile Internet, the Internet of things, and cloud computing have been developed rapidly, requirements on intelligentization and self-optimization capabilities of radio access networks have increased, and big-data-based wireless network optimization has become a new trend. Data acquisition is the base of big-data-based wireless network optimization. Acquired wireless data may be used to support real-time and non-real-time network optimization and analysis.
At present, data acquisition of a 5G radio access network is mainly implemented by acquiring wireless data from a Distributed Unit (DU) and a Centralized Unit (CU), signaling data and non-signaling data being included. At present, mainstream data acquisition solutions mainly include a software-based acquisition solution and an F1-interface-based data acquisition solution. According to the software-based acquisition solution, signaling on the DU and the CU is acquired to a specified data platform. According to the F1-interface-based data acquisition solution, data of the DU is reported to the CU mainly through an interface between the DU and the CU in the related art.
The present software-based acquisition solution mainly has the following defects.
(1) Acquisition of signaling data is mainly supported, and acquisition of non-signaling data cannot be supported well.
This is mainly because a software-based acquisition protocol is based on a bit sequence design, signaling has a fixed bit length, and thus may be adapted to the software-based acquisition protocol well, while there is too much non-signaling data that is thus difficult to completely encapsulate with data of a bit sequence type.
(2) The flexibility in data clipping is poor.
Since the software-based acquisition protocol is based on the bit sequence design, data acquisition cannot be implemented effectively, and data that is not transmitted still occupies some bits. However, a non-signaling data transmission scenario usually has a great need for clipping.
(3) The reporting flexibility is low.
The software-based acquisition protocol cannot configure reporting of an acquisition device flexibly to be adapted to different real-time and non-real-time data reporting needs and further support periodic, event-triggered, and busy/idle-time reporting mechanisms, etc.
(4) Data distribution under different reporting configurations of multiple target nodes is not supported.
The present software-based acquisition protocol has a fixed reporting target, and cannot implement data distribution under different reporting configurations of multiple targets.
The present F1-interface-based data acquisition solution is mainly applied to data acquisition from the DU to the CU as a part of the radio access network, and mainly has the following defects.
(1) Data acquisition from the DU to the CU is mainly supported, and acquisition of data of the CU is not supported.
(2) An F1 interface resource is occupied, and excessive data acquisition may affect the network.
(3) A real-time data reporting scenario is mainly supported, and non-real-time data reporting is not supported.
(4) The flexibility in data reporting is low. Present F1-interface-based data acquisition is mainly used to acquire data required by a CU function, and thus only supports acquisition of part of data of the DU and is lack of a complete data reporting configuration support.
Based on the above reasons, there is an urgent need at present for a data processing method which may simultaneously support acquisition of various types of signaling and non-signaling data and through which data to be acquired is configured flexibly and a data content to be acquired, an acquisition manner, and a reporting manner are specified.
The embodiments of the disclosure provide a data processing method and device, to solve the problem of low flexibility of a data processing method in the related art.
According to a first aspect of the embodiments of the disclosure, a data processing method is provided, which may be applied to a source node and include that: a first request message is received from a target node, the first request message including at least one of information about creation of a data acquisition task, information about updating of the data acquisition task, or information about cancellation of the data acquisition task; and a first response message configured to respond to the first request message is sent to the target node.
Optionally, the first request message may include the information about creation of the data acquisition task; the method may further include that: data acquisition is performed according to the information about creation of the data acquisition task, and an acquisition result is sent to the target node.
Optionally, the operation that data acquisition is performed according to the information about creation of the data acquisition task and the acquisition result is sent to the target node may include that: a reporting triggering event Identity (ID) is added to an event monitor; when the event monitor monitors a triggering event corresponding to the reporting triggering event ID, a task ID of the data acquisition task corresponding to the reporting triggering event ID is queried; data acquisition is performed on a data object corresponding to descriptive information of the acquired target data object according to descriptive information of an acquisition configuration to obtain the acquisition result; a first timer is set according to a reporting period, and a second timer is set according to reporting valid time; when the first timer is triggered, the acquisition result is sent to the target node according to a reporting purpose ID; and when the second timer is triggered, the first timer and the second timer are cleared, and then the step that the task ID of the data acquisition task corresponding to the reporting triggering event ID is queried when the event monitor monitors the triggering event corresponding to the reporting triggering event ID is re-executed.
Optionally, the acquisition result may include one or more of the task ID of the data acquisition task, an ID of the source node, and an acquired data object array.
Optionally, the acquired data object array may include one or more of a data object source tag corresponding to a source tag of the acquired target data object, data object context data corresponding to a context acquisition condition of the acquired target data object, and a data object array corresponding to a tag of the acquired target data object, the data object array including one or more of an ID of the data object, a data value of the data object, and data generation time of the data object.
Optionally, the information about creation of the data acquisition task may include one or more of the descriptive information of the acquired target data object, descriptive information of a reporting configuration, and the descriptive information of the acquisition configuration; the first response message may include one or more of the task ID of the created data acquisition task, information representing that the data acquisition task is created successfully, information representing that the data acquisition task fails to be created, and a reason why the data acquisition task fails to be created.
Optionally, the descriptive information of the acquired target data object may include one or more of the source tag of the acquired target data object, the context acquisition condition of the acquired target data object, and the tag of the acquired target data object.
Optionally, the source tag of the acquired target data object may be an acquired target signaling flow tag or an acquired target layer tag; or, the context acquisition condition of the acquired target data object may include one or more of an acquisition condition and a context object tag, the acquisition condition including a reporting containing instruction and/or a reporting filtering instruction; or, the tag of the acquired target data object may be a message tag in a signaling flow or a data tag in a target layer.
Optionally, the descriptive information of the reporting configuration may include one or more of the reporting triggering event ID, the reporting period, the reporting valid time, and the reporting purpose ID.
Optionally, the descriptive information of the acquisition configuration may include one or more of a User Equipment (UE) sampling rate and a time sampling rate.
Optionally, the operation that the acquisition result is sent to the target node may include that: the acquisition result is sent to the target node through a data distribution protocol.
Optionally, the data distribution protocol may be a Message Queuing
Telemetry Transport (MQTT) protocol or a Kalfa protocol; the method may further include that: the task ID is determined as the reporting purpose ID.
Optionally, the data distribution protocol may be a HyperText Transfer Protocol (HTTP); the method may further include that: an ID of the target node is determined as the reporting purpose ID.
Optionally, the first request message may include the information about creation of the data acquisition task; the method may further include that: a second request message is received from the target node, the second request message including the information about updating of the data acquisition task, and a second response message configured to respond to the second request message is sent to the target node.
Optionally, the first request message may include the information about creation of the data acquisition task or the information about updating of the data acquisition task; the method may further include that: a third request message is received from the target node, the third request message including the information about cancellation of the data acquisition task, and a third response message configured to respond to the third request message is sent to the target node.
Optionally, the information about updating of the data acquisition task may include one or more of the task ID of the data acquisition task, descriptive information of a new acquired target data object, descriptive information of a new reporting configuration, and descriptive information of a new acquisition configuration; the first response message or the second response message may include one or more of information representing that the data acquisition task is updated successfully, information representing that the data acquisition task fails to be updated, and a reason why the data acquisition task fails to be updated.
Optionally, the information about cancellation of the data acquisition task may include the task ID of the data acquisition task; the first response message or the third response message may include one or more of information representing that the data acquisition task is canceled successfully, information representing that the data acquisition task tails to be canceled, and a reason why the data acquisition task fails to be canceled.
According to a second aspect of the embodiments of the disclosure, a data processing method is provided, which may be applied to a target node and include that: a first request message is sent to a source node, the first request message including at least one of information about creation of a data acquisition task, information about updating of the data acquisition task, or information about cancellation of the data acquisition task; and a first response message configured to respond to the first request message is received from the source node.
Optionally, the first request message may include the information about creation of the data acquisition task; the method may further include that: an acquisition result is received from the source node, the acquisition result being obtained by the source node by performing data acquisition according to the information about creation of the data acquisition task.
Optionally, the acquisition result may include one or more of a task ID of the data acquisition task, an ID of the source node, and an acquired data object array.
Optionally, the acquired data object array may include one or more of a data object source tag corresponding to a source tag of an acquired target data object, data object context data corresponding to a context acquisition condition of the acquired target data object, and a data object array corresponding to a tag of the acquired target data object, the data object array including one or more of an ID of the data object, a data value of the data object, and data generation time of the data object.
Optionally, the information about creation of the data acquisition task may include one or more of descriptive information of the acquired target data object, descriptive information of a reporting configuration, and descriptive information of an acquisition configuration; the first response message may include one or more of the task ID of the created data acquisition task, information representing that the data acquisition task is created successfully, information representing that the data acquisition task fails to be created, and a reason why the data acquisition task fails to be created.
Optionally, the descriptive information of the acquired target data object may include one or more of the source tag of the acquired target data object, the context acquisition condition of the acquired target data object, and the tag of the acquired target data object.
Optionally, the source tag of the acquired target data object may be an acquired target signaling flow tag or an acquired target layer tag; or, the context acquisition condition of the acquired target data object may include one or more of an acquisition condition and a context object tag, the acquisition condition including a reporting containing instruction and/or a reporting filtering instruction; or, the tag of the acquired target data object may be a message tag in a signaling flow or a data tag in a target layer.
Optionally, the descriptive information of the reporting configuration may include one or more of a reporting triggering event ID, a reporting period, reporting valid time, and a reporting purpose ID.
Optionally, the descriptive information of the acquisition configuration may include one or more of a UE sampling rate and a time sampling rate.
Optionally, the operation that the acquisition result is received from the source node may include that: the acquisition result is received from the source node through a data distribution protocol.
Optionally, the data distribution protocol may be an MQTT protocol or a Kalfa protocol; and the reporting purpose ID may be the task ID.
Optionally, the data distribution protocol may be an HTTP; and the reporting purpose ID may be an ID of the target node.
Optionally, the first request message may include the information about creation of the data acquisition task; the method may further include that: a second request message is sent to the source node, the second request message including the information about updating of the data acquisition task, and a second response message configured to respond to the second request message is received from the source node.
Optionally, the first request message may include the information about creation of the data acquisition task or the information about updating of the data acquisition task; the method may further include that: a third request message is sent to the source node, the third request message including the information about cancellation of the data acquisition task, and a third response message configured to respond to the third request message is received from the source node.
Optionally, the information about updating of the data acquisition task may include one or more of the task ID of the data acquisition task, descriptive information of a new acquired target data object, descriptive information of a new reporting configuration, and descriptive information of a new acquisition configuration; and the first response message or the second response message may include one or more of information representing that the data acquisition task is updated successfully, information representing that the data acquisition task fails to be updated, and a reason why the data acquisition task fails to be updated.
Optionally, the information about cancellation of the data acquisition task may include the task ID of the data acquisition task; and the first response message or the third response message may include one or more of information representing that the data acquisition task is canceled successfully, information representing that the data acquisition task tails to be canceled, and a reason why the data acquisition task fails to be canceled.
According to a third aspect of the embodiments of the disclosure, a source node is provided, which may include a first transceiver and a first processor. The first transceiver may be configured to receive a first request message from a target node, the first request message including at least one of information about creation of a data acquisition task, information about updating of the data acquisition task, or information about cancellation of the data acquisition task. The first transceiver may further be configured to send a first response message configured to respond to the first request message to the target node.
Optionally, the first request message includes the information about creation of the data acquisition task; the first processor is configured to perform data acquisition according to the information about creation of the data acquisition task, and send an acquisition result to the target node.
Optionally, the first processor is further configured to: add a reporting triggering event ID to an event monitor; when the event monitor monitors a triggering event corresponding to the reporting triggering event ID, query a task ID of the data acquisition task corresponding to the reporting triggering event ID; perform data acquisition on a data object corresponding to descriptive information of the acquired target data object according to descriptive information of an acquisition configuration to obtain the acquisition result; set a first timer according to a reporting period, and set a second timer according to reporting valid time; when the first timer is triggered, send the acquisition result to the target node according to a reporting purpose ID; and when the second timer is triggered, clear the first timer and the second timer, and then re-execute the step of querying the task ID of the data acquisition task corresponding to the reporting triggering event ID when the event monitor monitors the triggering event corresponding to the reporting triggering event ID.
Optionally, the acquisition result includes one or more of the task ID of the data acquisition task, an ID of the source node, and an acquired data object array.
Optionally, the acquired data object array includes one or more of a data object source tag corresponding to a source tag of the acquired target data object, data object context data corresponding to a context acquisition condition of the acquired target data object, and a data object array corresponding to a tag of the acquired target data object, the data object array including one or more of an ID of the data object, a data value of the data object, and data generation time of the data object.
Optionally, the information about creation of the data acquisition task includes one or more of the descriptive information of the acquired target data object, descriptive information of a reporting configuration, and the descriptive information of the acquisition configuration; the first response message includes one or more of the task ID of the created data acquisition task, information representing that the data acquisition task is created successfully, information representing that the data acquisition task fails to be created, and a reason why the data acquisition task fails to be created.
Optionally, the descriptive information of the acquired target data object includes one or more of the source tag of the acquired target data object, the context acquisition condition of the acquired target data object, and the tag of the acquired target data object.
Optionally, the source tag of the acquired target data object is an acquired target signaling flow tag or an acquired target layer tag; or, the context acquisition condition of the acquired target data object includes one or more of an acquisition condition and a context object tag, the acquisition condition including a reporting containing instruction and/or a reporting filtering instruction; or, the tag of the acquired target data object is a message tag in a signaling flow or a data tag in a target layer.
Optionally, the descriptive information of the reporting configuration includes one or more of the reporting triggering event ID, the reporting period, the reporting valid time, and the reporting purpose ID.
Optionally, the descriptive information of the acquisition configuration includes one or more of a UE sampling rate and a time sampling rate.
Optionally, the first transceiver is further configured to send the acquisition result to the target node through a data distribution protocol.
Optionally, the data distribution protocol is an MQTT protocol or a Kalfa protocol.
The first processor is further configured to determine the task ID as the reporting purpose ID.
Optionally, the data distribution protocol is an HTTP.
The first processor is further configured to determine an ID of the target node as the reporting purpose ID.
Optionally, the first request message includes the information about creation of the data acquisition task.
The first transceiver is further configured to receive a second request message from the target node, the second request message including the information about updating of the data acquisition task.
The first transceiver is further configured to send a second response message configured to respond to the second request message to the target node.
Optionally, the first request message includes the information about creation of the data acquisition task or the information about updating of the data acquisition task.
The first transceiver is further configured to receive a third request message from the target node, the third request message including the information about cancellation of the data acquisition task.
The first transceiver is further configured to send a third response message configured to respond to the third request message to the target node.
Optionally, the information about updating of the data acquisition task includes one or more of the task ID of the data acquisition task, descriptive information of a new acquired target data object, descriptive information of a new reporting configuration, and descriptive information of a new acquisition configuration; the first response message or the second response message includes one or more of information representing that the data acquisition task is updated successfully, information representing that the data acquisition task fails to be updated, and a reason why the data acquisition task fails to be updated.
Optionally, the information about cancellation of the data acquisition task includes the task ID of the data acquisition task; the first response message or the third response message includes one or more of information representing that the data acquisition task is canceled successfully, information representing that the data acquisition task tails to be canceled, and a reason why the data acquisition task fails to be canceled.
According to a fourth aspect of the embodiments of the disclosure, a target node is provided, which may include a second transceiver and a second processor. The second transceiver may be configured to send a first request message to a source node, the first request message including at least one of information about creation of a data acquisition task, information about updating of the data acquisition task, or information about cancellation of the data acquisition task. The second transceiver may further be configured to receive a first response message configured to respond to the first request message from the source node.
Optionally, the first request message includes the information about creation of the data acquisition task; the second transceiver is further configured to receive an acquisition result from the source node, the acquisition result being obtained by the source node by performing data acquisition according to the information about creation of the data acquisition task.
Optionally, the acquisition result includes one or more of a task ID of the data acquisition task, an ID of the source node, and an acquired data object array.
Optionally, the acquired data object array includes one or more of a data object source tag corresponding to a source tag of an acquired target data object, data object context data corresponding to a context acquisition condition of the acquired target data object, and a data object array corresponding to a tag of the acquired target data object, the data object array including one or more of an ID of the data object, a data value of the data object, and data generation time of the data object.
Optionally, the information about creation of the data acquisition task includes one or more of descriptive information of the acquired target data object, descriptive information of a reporting configuration, and descriptive information of an acquisition configuration; the first response message includes one or more of the task ID of the created data acquisition task, information representing that the data acquisition task is created successfully, information representing that the data acquisition task fails to be created, and a reason why the data acquisition task fails to be created.
Optionally, the descriptive information of the acquired target data object includes one or more of the source tag of the acquired target data object, the context acquisition condition of the acquired target data object, and the tag of the acquired target data object.
Optionally, the source tag of the acquired target data object is an acquired target signaling flow tag or an acquired target layer tag; or, the context acquisition condition of the acquired target data object may include one or more of an acquisition condition and a context object tag, the acquisition condition including a reporting containing instruction and/or a reporting filtering instruction; or, the tag of the acquired target data object may be a message tag in a signaling flow or a data tag in a target layer.
Optionally, the descriptive information of the reporting configuration includes one or more of a reporting triggering event ID, a reporting period, reporting valid time, and a reporting purpose ID.
Optionally, the descriptive information of the acquisition configuration includes one or more of a UE sampling rate and a time sampling rate.
Optionally, the second transceiver is further configured to receive the acquisition result from the source node through a data distribution protocol.
Optionally, the data distribution protocol is an MQTT protocol or a Kalfa protocol; and the reporting purpose ID is the task ID.
Optionally, the data distribution protocol is an HTTP; and the reporting purpose ID is an ID of the target node.
Optionally, the first request message includes the information about creation of the data acquisition task.
The second transceiver is further configured to send a second request message to the source node, the second request message including the information about updating of the data acquisition task.
The second transceiver is further configured to receive a second response message configured to respond to the second request message from the source node.
Optionally, the first request message includes the information about creation of the data acquisition task or the information about updating of the data acquisition task.
The second transceiver is further configured to send a third request message to the source node, the third request message including the information about cancellation of the data acquisition task.
The second transceiver is further configured to receive a third response message configured to respond to the third request message from the source node.
Optionally, the information about updating of the data acquisition task includes one or more of the task ID of the data acquisition task, descriptive information of a new acquired target data object, descriptive information of new reporting configuration, and descriptive information of a new acquisition configuration; and the first response message or the second response message includes one or more of information representing that the data acquisition task is updated successfully, information representing that the data acquisition task fails to be updated, and a reason why the data acquisition task fails to be updated.
Optionally, the information about cancellation of the data acquisition task includes the task ID of the data acquisition task; and the first response message or the third response message may include one or more of information representing that the data acquisition task is canceled successfully, information representing that the data acquisition task tails to be canceled, and a reason why the data acquisition task fails to be canceled.
According to a fifth aspect of the embodiments of the disclosure, a communication device is provided, which may include a processor, a memory, and a program stored in the memory and capable of running in the processor, the program being executed by the processor to implement the steps of the data processing method as described in the first aspect or the steps of the data processing method as described in the second aspect.
According to a sixth aspect of the embodiments of the disclosure, a computer-readable storage medium is provided, in which a computer program may be stored, the computer program being executed by a processor to implement the steps of the data processing method as described in the first aspect or the steps of the data processing method as described in the second aspect.
In the embodiments of the disclosure, the source node performs data processing of creating the data acquisition task, updating information about the data acquisition task, or canceling the data acquisition task according to the first request message from the target node, so that higher flexibility in data processing is achieved.
In order to describe the technical solutions of the embodiments of the disclosure more clearly, the drawings required to be used in the descriptions about the embodiments of the disclosure will be simply introduced below. It is apparent that the drawings described below are merely some embodiments of the disclosure. Other drawings may further be obtained by those of ordinary skill in the art according to these drawings without creative work.
The technical solutions in the embodiments of the disclosure will be clearly and completely described below in combination with the drawings in the embodiments of the disclosure. It is apparent that the described embodiments are not all embodiments but part of embodiments of the disclosure. All other embodiments obtained by those of ordinary skill in the art on the basis of the embodiments in the disclosure without creative work shall fall within the scope of protection of the disclosure.
Referring to
In 101, a first request message is received from a target node.
In the embodiment of the disclosure, the first request message includes at least one of information about creation of a data acquisition task, information about updating of the data acquisition task, or information about cancellation of the data acquisition task.
In 102, a first response message configured to respond to the first request message is sent to the target node.
Referring to
In 201, a first request message is sent to a source node.
In the embodiment of the disclosure, the first request message includes at least one of information about creation of a data acquisition task, information about updating of the data acquisition task, or information about cancellation of the data acquisition task.
In 202, a first response message configured to respond to the first request message is received from the source node.
In the embodiment of the disclosure, the source node performs data processing of creating the data acquisition task, updating information about the data acquisition task, or canceling the data acquisition task according to the first request message from the target node, so that higher flexibility in data processing is achieved.
For the condition that the first request message includes the information about creation of the data acquisition task, referring to
In 301, a target node sends a first request message to a source node.
In the embodiment of the disclosure, the first request message includes information about creation of a data acquisition task.
Optionally, the information about creation of the data acquisition task includes descriptive information of an acquired target data object, descriptive information of a reporting configuration, and descriptive information of an acquisition configuration.
Furthermore, the descriptive information of the acquired target data object includes:
a source tag of the acquired target data object,
the source tag of the acquired target data object being mainly configured to identify a source of the acquired target data object, and being an acquired target signaling flow tag or an acquired target layer tag, for example, a port Physical layer (PHY) tag, a Multiple Access Channel (MAC) tag, a system tag, and a Radio Resource Control (RRC) tag;
a context acquisition condition of the acquired target data object,
the context acquisition condition of the acquired target data object including an acquisition condition and a context object tag, for example, a UEID, a cell ID, a Radio Bear Identity (RBID), and a signaling flow state, and
the acquisition condition including a reporting containing instruction and/or a reporting filtering instruction, for example, a UE ID filtering instruction and a flow state filtering instruction; and
a tag of the acquired target data object,
the tag of the acquired target data object being mainly configured to identify a data object tag in the source of the acquired target data object, and being a data tag in a signaling flow or a data tag in a target layer, for example, a Channel Quality Indicator (CQI) in a signaling flow such as PHY.
Furthermore, the descriptive information of the reporting configuration includes a reporting triggering event ID, a reporting period, reporting valid time, and a reporting purpose ID.
Furthermore, the descriptive information of the acquisition configuration includes a UE sampling rate and a time sampling rate, and is configured to represent information only valid to non-signaling data acquisition.
In 302, a first response message sent by the source node to the target node and configured to respond to the first request message is received.
In the embodiment of the disclosure, when the data acquisition task is created successfully, the first response message includes a task ID of the created data acquisition task and information representing that the data acquisition task is created successfully.
When the data acquisition task fails to be created, the first response message includes information representing that the data acquisition task fails to be created and a reason why the data acquisition task fails to be created.
In 303, data acquisition is performed according to information about creation of a data acquisition task, and an acquisition result is sent to the target node.
In the embodiment of the disclosure, the source node performs data acquisition according to a content in the information about creation of the data acquisition task.
Specifically, data acquisition includes the following specific operations.
In (1), the reporting triggering event ID is added to an event monitor.
In (2), when the event monitor monitors a triggering event corresponding to the reporting triggering event ID, the task ID of the data acquisition task corresponding to the reporting triggering event ID is queried.
In (2), data acquisition is performed on the data object corresponding to the descriptive information of the acquired target data object according to the descriptive information of the acquisition configuration to obtain the acquisition result.
In (3), a first timer is set according to the reporting period, and a second timer is set according to the reporting valid time.
In (4), when the first timer is triggered, the acquisition result is sent to the target node according to the reporting purpose ID.
In (5), when the second timer is triggered, the first timer and the second timer are cleared, and then (2) is re-executed.
Furthermore, the acquisition result includes the task ID of the data acquisition task, an ID of the source node, and an acquired data object array.
Optionally, the acquisition result further includes reporting time.
The acquired data object array includes:
a data object source tag corresponding to the source tag of the acquired target data object;
data object context data corresponding to the context acquisition condition of the acquired target data object, for example, the UEID, the cell ID, the RBID, and the signaling flow state;
a data object array corresponding to the tag of the acquired target data object.
Optionally, the acquired data object array further includes acquired data packing time, a data object type (for example, signaling or non-signaling), and acquisition time of the data object.
Furthermore, the data object array includes one or more of an ID of the data object, a data value of the data object, and data generation time of the data object.
It is to be noted that a relationship between a data object source and a data object is that a data object source may include multiple data objects. For example, when the data object source is a signaling flow, the object data may be a message in the flow. For another example, when the data object source is PHY, the data object may be a parameter such as the CQI in PHY.
Optionally, the source node sends the acquisition result to the target node through a data distribution protocol.
In the embodiment of the disclosure, the data distribution protocol is an MQTT protocol, a Kafka protocol, and an HTTP.
Furthermore, when the data distribution protocol is the MQTT protocol or the Kafka protocol, the task ID is determined as the reporting purpose ID. When the data distribution protocol is the HTTP, an ID of the target node is determined as the reporting purpose ID.
The data distribution protocol may be used to form a data acquisition sharing mechanism. For example, when a data subject is set as a task ID, different task IDs are created according to different data uses and data ranges (for example, acquisition of different types of signaling or data of different layers determined as different tasks), and multiple target nodes may subscribe to data of corresponding task ID subjects according to data using needs, to implement data acquisition and distribution sharing, thereby reducing reporting of the source node.
In the embodiment of the disclosure, the source node performs data acquisition according to the information about creation of the data acquisition task in the first request message from the target node, acquisition of various types of signaling and non-signaling data may be simultaneously supported, data to be acquired is clipped and configured flexibly, a data content to be acquired, an acquisition manner, and a reporting manner are specified, data acquisition under different acquisition configurations of multiple target nodes may be simultaneously supported, and a data sharing mechanism for data acquisition of multiple target nodes is supported.
For the condition that the first request message includes the information about creation of the data acquisition task, referring to
In 401, a target node sends a first request message to a source node.
In 402, the target node receives a first response message configured to respond to the first request message from the source node.
In 403, the source node performs data acquisition according to information about creation of a data acquisition task, and sends an acquisition result to the target node.
The descriptions of 401 to 403 may refer to the descriptions of 301 to 303 in
In 404, the source node receives a second request message from the target node.
In the embodiment of the disclosure, the second request message includes information about updating of the data acquisition task.
Furthermore, the information about updating of the data collection task includes a task ID of the data collection task, descriptive information of a new acquired data target object, descriptive information of a new reporting configuration, and descriptive information of a new acquisition configuration.
In 405, the source node sends a second response message configured to respond to the second request message to the target node.
In the embodiment of the disclosure, when the data acquisition task is updated successfully, the second response message includes information representing that the data acquisition task is updated successfully.
When the data acquisition task fails to be updated, the second response message includes information representing that the data acquisition task fails to be updated and a reason why the data acquisition task fails to be updated.
In the embodiment of the disclosure, after the data acquisition task is completed, the source node updates the data acquisition task according to the second request message sent by the target node to obtain the descriptive information of the new acquired data target object, the descriptive information of the new reporting configuration, and the descriptive information of the new acquisition configuration for data acquisition according to a new requirement.
For the condition that the first request message includes the information about creation of the data acquisition task, referring to
In 501, a target node sends a first request message to a source node.
In 502, the target node receives a first response message configured to respond to the first request message from the source node.
In 503, the source node performs data acquisition according to information about creation of a data acquisition task, and sends an acquisition result to the target node.
The descriptions of 501 to 503 may refer to the descriptions of 301 to 303 in
In 504, the source node receives a third request message from the target node.
In the embodiment of the disclosure, the third request message includes information about cancellation of the data acquisition task.
Furthermore, the information about cancellation of the data acquisition task includes a task ID of the data acquisition task.
In 505, the source node sends a third response message configured to respond to the third request message to the target node.
In the embodiment of the disclosure, when the data acquisition task is canceled successfully, the third response message includes information representing that the data acquisition task is canceled successfully.
When the data acquisition task fails to be canceled, the third response message includes information representing that the data acquisition task fails to be canceled and a reason why the data acquisition task fails to be canceled.
In the embodiment of the disclosure, after the data acquisition task is completed, the source node may cancel the data acquisition task according to the third request message sent by the target node, and feed back a task cancellation result through the third response message.
Referring to
In 601, a target node sends a first request message to a source node.
In 602, the target node receives a first response message configured to respond to the first request message from the source node.
In 603, the source node performs data acquisition according to information about creation of a data acquisition task, and sends an acquisition result to the target node.
The descriptions of 601 to 603 may refer to the descriptions of 301 to 303 in
In 604, the source node receives a second request message from the target node.
In 605, the source node sends a second response message configured to respond to the second request message to the target node.
The descriptions of 604 and 605 may refer to the descriptions of 404 and 405 in
In 606, the source node receives a third request message from the target node.
In 607, the source node sends a third response message configured to respond to the third request message to the target node.
The descriptions of 606 and 607 may refer to the descriptions of 504 and 505 in
In the embodiment of the disclosure, the source node completes a process including creation of a data acquisition task, data acquisition, updating of the data acquisition task, and cancellation of the data acquisition task according to the request messages sent by the target node.
Referring to
The first transceiver 701 is configured to receive a first request message from a target node, the first request message including at least one of information about creation of a data acquisition task, information about updating of the data acquisition task, or information about cancellation of the data acquisition task.
The first transceiver 701 is further configured to send a first response message configured to respond to the first request message to the target node.
Optionally, the first request message includes the information about creation of the data acquisition task.
The first processor 702 is configured to perform data acquisition according to the information about creation of the data acquisition task, and send an acquisition result to the target node.
Optionally, the first processor 702 is further configured to: add a reporting triggering event ID to an event monitor; when the event monitor monitors a triggering event corresponding to the reporting triggering event ID, query a task ID of the data acquisition task corresponding to the reporting triggering event ID; perform data acquisition on a data object corresponding to descriptive information of the acquired target data object according to descriptive information of an acquisition configuration to obtain the acquisition result; set a first timer according to a reporting period, and set a second timer according to reporting valid time; when the first timer is triggered, send the acquisition result to the target node according to a reporting purpose ID; and when the second timer is triggered, clear the first timer and the second timer, and then re-execute the step of querying the task ID of the data acquisition task corresponding to the reporting triggering event ID when the event monitor monitors the triggering event corresponding to the reporting triggering event ID.
Optionally, the acquisition result includes one or more of the task ID of the data acquisition task, an ID of the source node, and an acquired data object array.
Optionally, the acquired data object array includes one or more of a data object source tag corresponding to a source tag of the acquired target data object, data object context data corresponding to a context acquisition condition of the acquired target data object, and a data object array corresponding to a tag of the acquired target data object, the data object array including one or more of an ID of the data object, a data value of the data object, and data generation time of the data object.
Optionally, the information about creation of the data acquisition task includes one or more of the descriptive information of the acquired target data object, descriptive information of a reporting configuration, and the descriptive information of the acquisition configuration. The first response message includes one or more of the task ID of the created data acquisition task, information representing that the data acquisition task is created successfully, information representing that the data acquisition task fails to be created, and a reason why the data acquisition task fails to be created.
Optionally, the descriptive information of the acquired target data object includes one or more of the source tag of the acquired target data object, the context acquisition condition of the acquired target data object, and the tag of the acquired target data object.
Optionally, the source tag of the acquired target data object is an acquired target signaling flow tag or an acquired target layer tag. Or, the context acquisition condition of the acquired target data object includes one or more of an acquisition condition and a context object tag, the acquisition condition including a reporting containing instruction and/or a reporting filtering instruction. Or, the tag of the acquired target data object is a message tag in a signaling flow or a data tag in a target layer.
Optionally, the descriptive information of the reporting configuration includes one or more of the reporting triggering event ID, the reporting period, the reporting valid time, and the reporting purpose ID.
Optionally, the descriptive information of the acquisition configuration includes one or more of a UE sampling rate and a time sampling rate.
Optionally, the first transceiver 701 is further configured to send the acquisition result to the target node through a data distribution protocol.
Optionally, the data distribution protocol is an MQTT protocol or a Kalfa protocol.
The first processor 702 is further configured to determine the task ID as the reporting purpose ID.
Optionally, the data distribution protocol is an HTTP.
The first processor 702 is further configured to determine an ID of the target node as the reporting purpose ID.
Optionally, the first request message includes the information about creation of the data acquisition task.
The first transceiver 701 is further configured to receive a second request message from the target node, the second request message including the information about updating of the data acquisition task.
The first transceiver 701 is further configured to send a second response message configured to respond to the second request message to the target node.
Optionally, the first request message includes the information about creation of the data acquisition task or the information about updating of the data acquisition task.
The first transceiver 701 is further configured to receive a third request message from the target node, the third request message including the information about cancellation of the data acquisition task.
The first transceiver 701 is further configured to send a third response message configured to respond to the third request message to the target node.
Optionally, the information about updating of the data acquisition task includes one or more of the task ID of the data acquisition task, descriptive information of a new acquired target data object, descriptive information of a new reporting configuration, and descriptive information of a new acquisition configuration. The first response message or the second response message includes one or more of information representing that the data acquisition task is updated successfully, information representing that the data acquisition task fails to be updated, and a reason why the data acquisition task fails to be updated.
Optionally, the information about cancellation of the data acquisition task includes the task ID of the data acquisition task. The first response message or the third response message includes one or more of information representing that the data acquisition task is canceled successfully, information representing that the data acquisition task tails to be canceled, and a reason why the data acquisition task fails to be canceled.
In the embodiment of the disclosure, the source node performs data processing of creating the data acquisition task, updating information about the data acquisition task, or canceling the data acquisition task according to the first request message from the target node, so that higher flexibility in data processing is achieved.
Referring to
The second transceiver 801 is configured to send a first request message to a source node, the first request message including at least one of information about creation of a data acquisition task, information about updating of the data acquisition task, or information about cancellation of the data acquisition task.
The second transceiver 801 is further configured to receive a first response message configured to respond to the first request message from the source node.
Optionally, the first request message includes the information about creation of the data acquisition task.
The second transceiver 801 is further configured to receive an acquisition result from the source node, the acquisition result being obtained by the source node by performing data acquisition according to the information about creation of the data acquisition task.
Optionally, the acquisition result includes one or more of a task ID of the data acquisition task, an ID of the source node, and an acquired data object array.
Optionally, the acquired data object array includes one or more of a data object source tag corresponding to a source tag of an acquired target data object, data object context data corresponding to a context acquisition condition of the acquired target data object, and a data object array corresponding to a tag of the acquired target data object, the data object array including one or more of an ID of the data object, a data value of the data object, and data generation time of the data object.
Optionally, the information about creation of the data acquisition task includes one or more of descriptive information of the acquired target data object, descriptive information of a reporting configuration, and descriptive information of an acquisition configuration. The first response message includes one or more of the task ID of the created data acquisition task, information representing that the data acquisition task is created successfully, information representing that the data acquisition task fails to be created, and a reason why the data acquisition task fails to be created.
Optionally, the descriptive information of the acquired target data object includes one or more of the source tag of the acquired target data object, the context acquisition condition of the acquired target data object, and the tag of the acquired target data object.
Optionally, the source tag of the acquired target data object is an acquired target signaling flow tag or an acquired target layer tag. Or, the context acquisition condition of the acquired target data object includes one or more of an acquisition condition and a context object tag, the acquisition condition including a reporting containing instruction and/or a reporting filtering instruction. Or, the tag of the acquired target data object is a message tag in a signaling flow or a data tag in a target layer.
Optionally, the descriptive information of the reporting configuration includes one or more of a reporting triggering event ID, a reporting period, reporting valid time, and a reporting purpose ID.
Optionally, the descriptive information of the acquisition configuration includes one or more of a UE sampling rate and a time sampling rate.
Optionally, the second transceiver 801 is further configured to receive the acquisition result from the source node through a data distribution protocol.
Optionally, the data distribution protocol is an MQTT protocol or a Kalfa protocol. The reporting purpose ID is the task ID.
Optionally, the data distribution protocol is an HTTP. The reporting purpose ID is an ID of the target node.
Optionally, the first request message includes the information about creation of the data acquisition task.
The second transceiver 801 is further configured to send a second request message to the source node, the second request message including the information about updating of the data acquisition task.
The second transceiver 801 is further configured to receive a second response message configured to respond to the second request message from the source node.
Optionally, the first request message includes the information about creation of the data acquisition task or the information about updating of the data acquisition task.
The second transceiver 801 is further configured to send a third request message to the source node, the third request message including the information about cancellation of the data acquisition task.
The second transceiver 801 is further configured to receive a third response message configured to respond to the third request message from the source node.
Optionally, the information about updating of the data acquisition task includes one or more of the task ID of the data acquisition task, descriptive information of a new acquired target data object, descriptive information of a new reporting configuration, and descriptive information of a new acquisition configuration. The first response message or the second response message includes one or more of information representing that the data acquisition task is updated successfully, information representing that the data acquisition task fails to be updated, and a reason why the data acquisition task fails to be updated.
Optionally, the information about cancellation of the data acquisition task includes the task ID of the data acquisition task. The first response message or the third response message includes one or more of information representing that the data acquisition task is canceled successfully, information representing that the data acquisition task tails to be canceled, and a reason why the data acquisition task fails to be canceled.
In the embodiment of the disclosure, the source node performs data processing of creating the data acquisition task, updating information about the data acquisition task, or canceling the data acquisition task according to the first request message from the target node, so that higher flexibility in data processing is achieved.
Referring to
The processor 901 may be responsible for management over a bus architecture and general processing. The memory 903 may store data used by the processor 901 when executing operations.
In the embodiment of the disclosure, the communication device 900 may further include a program stored in the memory 903 and capable of running in the processor 901. The processor is executed by the processor 901 to implement the steps of the method provided in the embodiments of the disclosure.
In
An embodiment of the disclosure also provides a computer-readable storage medium, in which a computer program is stored. The computer program is executed by a processor to implement each process in the method embodiment. The same technical effects may be achieved. To avoid repetitions, elaborations are omitted here. The computer-readable storage medium is, for example, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
It is to be noted that terms “include” and “contain” or any other variant thereof is intended to cover nonexclusive inclusions herein, so that a process, method, object, or apparatus including a series of elements not only includes those elements but also includes other elements which are not clearly listed or further includes elements intrinsic to the process, the method, the object, or the apparatus. Under the condition of no more limitations, an element defined by the statement “including a/an . . . ” does not exclude existence of the same other elements in a process, method, object, or apparatus including the element.
The embodiments of the disclosure are described above in combination with the drawings, but the disclosure is not limited to the abovementioned specific implementation modes. The abovementioned specific implementation modes are not restrictive but only schematic, those of ordinary skill in the art may be inspired by the disclosure to implement many forms without departing from the purpose of the disclosure and the scope of protection of the claims, and all shall fall within the scope of protection of the disclosure.
| Number | Date | Country | Kind |
|---|---|---|---|
| 201910010612.1 | Jan 2019 | CN | national |
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/CN2020/070656 | 1/7/2020 | WO | 00 |
