Information processing method, communication node, storage medium and program product

Abstract

The invention provides an information processing method, a communication node, a storage medium and a program product, the information processing method is applied to a first communication node, the method comprises the following steps: transmitting a verification request, the verification request indicating verification of a to-be-verified event; and obtaining a verification report, wherein the verification report indicates a verification result of the to-be-verified event.

Description

Information processing methods, communication nodes, storage media and program products Technical Field

[0001] This application relates to the field of communication technology, such as information processing methods, communication nodes, storage media, and program products. Background Technology

[0002] With the rapid development of information technology, various terminal devices are constantly generating large amounts of sensing data and signal measurement data. The data generated by these terminal devices will be applied to various fields.

[0003] However, the data generated by terminal devices is not necessarily accurate, so how to solve the problem of the accuracy of data generated by terminal devices is an urgent issue to be addressed. Summary of the Invention

[0004] This application provides an information processing method, a communication node, a storage medium, and a program product, ensuring the accuracy of the data generated by the terminal device.

[0005] In a first aspect, embodiments of this application provide an information processing method applied to a first communication node, the method comprising:

[0006] Transmit a confirmation request, which instructs that the event to be confirmed be verified;

[0007] Obtain a confirmation report, which indicates the confirmation result of the event to be confirmed.

[0008] Secondly, embodiments of this application provide yet another information processing method applied to a second communication node, the method comprising:

[0009] Obtain a verification request, which instructs verification of the event to be verified;

[0010] In response to the verification request, obtain a verification report;

[0011] Transmit the confirmation report.

[0012] Thirdly, embodiments of this application provide an information processing method applied to a third communication node, the method comprising:

[0013] Obtain a verification task, wherein the verification task includes a task to verify the event to be verified;

[0014] In response to the verification task, the event to be verified is verified, and a verification report is obtained;

[0015] Transmit confirmation report.

[0016] Fourthly, embodiments of this application provide an information processing method applied to a fourth communication node, the method comprising:

[0017] Obtain a viewing request, the viewing request instructing the viewing of verification evidence, the verification evidence including evidence confirming the event to be verified;

[0018] Obtain the aforementioned verification proof;

[0019] The verification certificate is transmitted.

[0020] Fifthly, embodiments of this application provide a communication node, including:

[0021] One or more processors;

[0022] Storage device for storing one or more programs;

[0023] When the one or more programs are executed by the one or more processors, the one or more processors implement the information processing method provided in the embodiments of this application.

[0024] Sixthly, embodiments of this application provide a storage medium, characterized in that the storage medium stores a computer program, which, when executed by a processor, implements the information processing method provided in embodiments of this application.

[0025] In a seventh aspect, embodiments of this application provide a computer program product, including a computer program that, when executed by a processor, implements the information processing method provided in embodiments of this application.

[0026] Further details regarding the above embodiments and other aspects of this application, as well as their implementations, are provided in the accompanying drawings, detailed description, and claims. Attached Figure Description

[0027] Figure 1 is a schematic diagram of an access network architecture provided in an embodiment of this application;

[0028] Figure 2 is a flowchart illustrating an information processing method provided in an embodiment of this application;

[0029] Figure 3 is a flowchart illustrating another information processing method provided in an embodiment of this application;

[0030] Figure 4 is a flowchart illustrating another information processing method provided in an embodiment of this application;

[0031] Figure 5 is a flowchart illustrating another information processing method provided in an embodiment of this application;

[0032] Figure 6 is a schematic flowchart of a transmission confirmation request provided in an embodiment of this application;

[0033] Figure 7 is a schematic diagram of an allocation verification task provided in an embodiment of this application;

[0034] Figure 8 is a schematic diagram of another allocation verification task provided in an embodiment of this application;

[0035] Figure 9 is a schematic diagram of another allocation verification task provided in an embodiment of this application;

[0036] Figure 10 is an interactive schematic diagram of a verification report provided in an embodiment of this application;

[0037] Figure 11 is an interactive schematic diagram of another verification report provided in an embodiment of this application;

[0038] Figure 12 is an interactive schematic diagram of another verification report provided in an embodiment of this application;

[0039] Figure 13 is an interactive schematic diagram of a summarized verification report provided in an embodiment of this application;

[0040] Figure 14 is an interactive schematic diagram of another type of summarized verification report provided in an embodiment of this application;

[0041] Figure 15 is a schematic diagram of a transmission query request provided in an embodiment of this application;

[0042] Figure 16 is a schematic diagram of another transmission query request provided in an embodiment of this application;

[0043] Figure 17 is a schematic diagram illustrating a method for verifying evidence storage provided in an embodiment of this application;

[0044] Figure 18 is a schematic diagram of a verification query provided in an embodiment of this application;

[0045] Figure 19 is a schematic diagram of a verification transmission provided in an embodiment of this application;

[0046] Figure 20 is a schematic diagram of the structure of an information processing device provided in an embodiment of this application;

[0047] Figure 21 is a schematic diagram of the structure of another information processing device provided in an embodiment of this application;

[0048] Figure 22 is a schematic diagram of another information processing device provided in an embodiment of this application;

[0049] Figure 23 is a schematic diagram of another information processing device provided in an embodiment of this application;

[0050] Figure 24 is a schematic diagram of the structure of a communication node provided in an embodiment of this application. Detailed Implementation

[0051] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in detail below with reference to the accompanying drawings. It should be noted that, unless otherwise specified, the embodiments and features described in these embodiments can be arbitrarily combined with each other.

[0052] The steps illustrated in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases the steps shown or described may be performed in a different order than that presented here.

[0053] In this application, the terms "first," "second," etc., are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0054] With the widespread application of 5G mobile communication technology and the rapid development of the Internet of Things (IoT), various smart terminals are constantly generating massive amounts of sensing data, location information, and signal measurement data. This data has significant application value in many fields such as smart cities, autonomous driving, precise positioning services, and network optimization. However, under the current technological framework, information generated by terminal devices (User Equipment, UE) often lacks a reliable verification mechanism. For example, in Integrated Sensing and Communication (ISAC) applications, sensing results may originate from devices with different hardware capabilities. In vehicle-to-everything (V2X) scenarios, sensing results from other vehicles, pedestrians, etc., may not be accurate.

[0055] With the rapid development of information technology, future 6th Generation Mobile Communication Technology (6G) networks will face more diversified and complex application scenarios. These scenarios not only cover traditional mobile communication services but also extend to multiple vertical industries such as intelligent transportation, industrial internet, smart cities, and telemedicine. In 5G networks, the core network adopts cloud technology and service-based architecture (SBA) to achieve the virtualization and modularization of network functions. By decoupling network functions into independent service components, SBA allows each component to be developed, deployed, and maintained independently, thereby improving the network's flexibility and scalability.

[0056] Figure 1 is a schematic diagram of an access network architecture provided in an embodiment of this application. Referring to Figure 1, the Next Generation Radio Access Network (NG-RAN) is the main network component in 5G responsible for handling radio signal transmission and resource management between the UE and the 5G Core Network (5G Core, 5GC). The Next Generation Interface (NG) connects the NG-RAN and the 5GC. The Xn interface is used to connect gNBs, ng-eNBs, and gNBs and ng-eNBs.

[0057] In 5GC, the Access and Mobility Management Function (AMF) is responsible for UE access management, while the User Plane Function (UPF) is responsible for user data forwarding.

[0058] The UE connects to the NG-RAN (gNB or ng-eNB) via a wireless interface.

[0059] This application can be applied to the architecture shown in Figure 1, or to architectures derived from the architecture shown in Figure 1, without limitation.

[0060] This application proposes a witnessing mechanism for network information based on the inherent security and trustworthiness characteristics of the network. This mechanism can witness the results of sensing, positioning, and signal measurement, and generate credentials for applications such as billing and monitoring. This application can be applied to at least 6G. The following describes the information processing method provided in this application:

[0061] In one exemplary embodiment, FIG2 is a flowchart illustrating an information processing method provided in an embodiment of this application. The method can be applied to verifying data generated by a first communication node. The method can be executed by an information processing device provided in this application. The information processing device can be executed by software and / or hardware. The device can be integrated on the first communication node, which can be the communication node to be verified for the generated data, such as a UE.

[0062] As shown in Figure 1, the information processing method provided in this embodiment includes the following operations:

[0063] S110, Transmit a confirmation request, the confirmation request indicating that the event to be confirmed be confirmed.

[0064] An event to be verified can be the event corresponding to the data generated by the first communication node. An event to be verified can represent the data generated by the first communication node. An event to be verified can be an event that needs to be verified. If the event to be verified needs to be verified by a more trusted communication node (also known as witnessing, authentication, proof, verification, etc.), then it may be an event to be verified.

[0065] Verifying an event can be considered as making a decision about the accuracy of the facts to be verified. The result of verification can be considered credible, meaning that the judgment of the accuracy of the facts to be verified has guiding or reference value.

[0066] A confirmation request can be considered a request to confirm an event to be confirmed. This operation transmits a confirmation request to trigger the communication node performing the confirmation to confirm the event to be confirmed.

[0067] This operation does not limit the content of the confirmation request, as long as it can trigger the communication node to confirm the event to be confirmed. The confirmation request should include at least the initial event result of the event to be confirmed.

[0068] The initial event result can be considered as the result determined by the first communication node for the event to be verified. This result needs further verification.

[0069] The initial event result differs depending on the scenario. In a perception scenario, the initial event result can be the perception result. In a localization scenario, the initial event result can be the localization result. In a measurement scenario, the initial event result can be the signal strength measurement result.

[0070] In this operation, the first communication node can transmit a confirmation request to the second communication node to trigger the second communication node to respond to the confirmation request.

[0071] S120. Obtain a confirmation report, the confirmation report indicating the confirmation result of the event to be confirmed.

[0072] A confirmed result can be considered as the outcome determined after verifying the event to be verified. A confirmed result can characterize whether the initial event result is accurate.

[0073] After transmitting the confirmation request, this operation can obtain a confirmation report to determine the confirmation result of the event to be confirmed.

[0074] This embodiment does not limit the content included in the verification report. It may include information indicating whether the initial event result is accurate, or it may include the event result determined after the event to be verified. The event result may be determined by the communication node performing the verification, or it may be determined by other nodes after analyzing the result verified by the communication node performing the verification.

[0075] In this operation, the first communication node can obtain the confirmation report transmitted by the second communication node.

[0076] The information processing method provided in this embodiment can transmit a verification request to obtain a verification report when there is an event to be verified at the first communication node, thereby verifying the accuracy of the event to be verified and ensuring the accuracy of the result corresponding to the event to be verified, such as ensuring the accuracy of the initial event result.

[0077] Based on the above embodiments, modified embodiments of the above embodiments are proposed. It should be noted that, in order to keep the description brief, only the differences from the above embodiments are described in the modified embodiments.

[0078] In one embodiment, the confirmation request includes one or more of the following information:

[0079] First identification information, the first identification information including information identifying the confirmation request;

[0080] The second identification information includes information that identifies the first communication node;

[0081] Event type, which indicates the type of the event to be verified;

[0082] The first timestamp includes the time when the initial event result of the event to be verified was obtained;

[0083] The result of the initial event;

[0084] The first spatial range includes the spatial range of the event to be verified.

[0085] The priority information of the event to be verified;

[0086] The expected method of confirmation.

[0087] The first identification information, also known as the unique identifier of the request (i.e., Witness request ID), is used for subsequent tracking and response matching.

[0088] The second identification information can be considered as information identifying the first communication node requesting verification. This second identification information is also known as the Witness request node ID, such as the UE ID.

[0089] The type of the event to be verified (i.e., the Witness event type) can be associated with the scenario. In a perception scenario, the type can be verifying the perception result. In a localization scenario, the type can be verifying location information. In a measurement scenario, the type can be verifying the measurement result of the signal.

[0090] The acquisition time can be the timestamp of the initial event result (i.e., the Initial event Time stamp). For example, the timestamp of the initial event result acquired by the UE.

[0091] The initial event result can be a request source for confirming the event to be confirmed, such as the result determined by the UE for the event to be confirmed, such as the sensing result, the positioning result, and / or the signal enhancement result.

[0092] The first spatial range can be the location or area to be verified, such as the spatial range of the event to be verified. The spatial range can include location information or information representing a region. The spatial range can be the UE's location information or relative area and location information determined based on the UE's capabilities.

[0093] Priority information can be considered as information that characterizes the priority of an event to be verified, such as information that characterizes the urgency (i.e., the witness level) of the event to be verified. The form of priority information is not limited here; different values ​​can represent the urgency level, such as 0 indicating a non-urgent event and 1 indicating an urgent event.

[0094] The verification method can be considered as the way the event to be verified is verified. There are no limitations on the method here, such as the communication node performing the verification, or the means used for verification. The desired verification method can be the verification method that the communication node is expected to use to perform the verification.

[0095] The desired verification method (i.e., Witness progress type) is not limited here. It could include witnessing by the Radio Access Network (RAN) node, witnessing by other UEs, or witnessing by UEs within a group. The other UEs can be considered as UEs other than the first communication node, assuming the first communication node is the UE.

[0096] In one embodiment, the confirmation report includes one or more of the following information:

[0097] The third identification information includes information identifying the verification report;

[0098] First identification information, the first identification information including information identifying the confirmation request;

[0099] The fourth identification information includes an identifier for the communication node that performs the verification of the event to be verified;

[0100] Event type, which indicates the type of the event to be verified;

[0101] A second timestamp, the second timestamp including the time when the event to be verified was performed;

[0102] Event confirmation results, which include the event results determined after confirming the event to be confirmed;

[0103] The second spatial range includes the spatial range for verifying the event to be verified.

[0104] Confidence information, which indicates the degree of confidence in the confirmation of the event.

[0105] The third identification information, also known as the unique identifier of the response (such as the confirmation report of the response) (also known as the WitnessResponse ID), is used for subsequent tracking and confirmation proof generation.

[0106] The fourth identification information may include the identifier of the communication node performing the verification (i.e., the Witness node ID). For example, the identifier of the communication node performing the verification task. If there are multiple communication nodes performing the task, the number of identifiers can be multiple (a Witness node ID list), with each identifier uniquely corresponding to its corresponding communication node. The verification task can be considered as a task that triggers the verification of the event to be verified. A verification task can be a task initiated based on a verification request to trigger the verification of the event to be verified.

[0107] The second timestamp can be considered as the time when the fact to be verified is confirmed (i.e., Witness Time stamp).

[0108] Witness result can include the results determined for the event to be verified after the event to be verified is verified, such as the verification result of the event to be verified, including the perception result after verification, the location information after verification, or the measurement result after verification.

[0109] The second spatial range (i.e., Witness location) can be the spatial range verified by the communication node performing the verification, such as a location or area.

[0110] Witness confidence level indicates the degree of credibility of an event's verifiable results, such as the confidence level in verifying its own results.

[0111] In one embodiment, the information processing method further includes:

[0112] A viewing request is transmitted, the viewing request instructing the viewing of verification evidence, the verification evidence including evidence confirming the event to be verified;

[0113] Obtain the aforementioned verification proof.

[0114] Verification proof can be considered as proof of a fact to be verified. The content included in verification proof is not limited here; it can summarize the information included in the verification request and the verification report for use in this verification process. In this embodiment, verification proof includes some information from the verification request and some information from the verification process itself. It is not limited which parts of the information are included, as long as they can prove the verification process, such as the verification request, the verification report, and the event results determined after verification.

[0115] A view request can be considered a request to view verification evidence. In this embodiment, after transmitting a verification request or obtaining a verification report, the first communication node can transmit a view request to obtain verification evidence for the event to be verified. The content of the view request is not limited here, as long as verification evidence can be retrieved; it may include identification information of the verification evidence.

[0116] In this embodiment, the first communication node can transmit a viewing request to the second communication node and obtain a confirmation report transmitted by the second communication node. The first communication node can also transmit a viewing request to the fourth communication node and obtain a confirmation report transmitted by the fourth communication node.

[0117] In one embodiment, the witness proof includes one or more of the following:

[0118] The fifth identification information includes information identifying the verification certificate;

[0119] The third identification information includes information identifying the verification report (i.e., Witnessresponse ID);

[0120] First identification information, the first identification information includes information identifying the verification request (such as WitnessRequest ID);

[0121] Event type, which indicates the type of the event to be verified;

[0122] A second timestamp, the second timestamp including the time when the event to be verified was performed;

[0123] Event confirmation results, which include the event results determined after confirming the event to be confirmed;

[0124] The second spatial range includes the spatial range for verifying the event to be verified.

[0125] The second identification information includes information that identifies the first communication node;

[0126] The fourth identification information includes identifying the communication node that performs the verification of the event to be verified.

[0127] The fifth identification information may include information used to uniquely identify the proof of proof, i.e., the unique identifier of the proof of proof (i.e., Proof ID).

[0128] In one embodiment, the viewing request includes one or more of the following:

[0129] The fifth identification information includes information identifying the verification certificate;

[0130] The third identification information includes information identifying the verification report;

[0131] First identification information, the first identification information including information identifying the confirmation request;

[0132] The second identification information includes information that identifies the first communication node;

[0133] The fourth identification information includes identifying the communication node that performs the verification of the event to be verified.

[0134] A view request can be identified by the fifth identifier, which specifies the required verification document. A view request can be identified by the first identifier, facilitating the retrieval of the corresponding verification document. A view request can be identified by the second identifier, which specifies the first communication node initiating the verification request, facilitating the retrieval of one or more verification documents corresponding to the first communication node. A view request can be identified by the third identifier, which specifies the verification report, facilitating the retrieval of the corresponding verification document, such as the verification document for the event to be verified as confirmed in the verification report. A view request can be identified by the fourth identifier, which specifies the communication node verifying the event to be verified, facilitating the retrieval of the corresponding verification document.

[0135] In one embodiment, the confirmation report may be determined and transmitted by a second communication node that received the confirmation request. Alternatively, the confirmation report may be transmitted by the second communication node and determined by a third communication node. If there is only one third communication node, the second communication node can directly transmit the confirmation report. If there are multiple third communication nodes, the second communication node can aggregate the various confirmation reports and transmit the aggregated confirmation report to the first communication node.

[0136] In one exemplary embodiment, Figure 3 is a schematic flowchart of another information processing method provided in this application embodiment. This method can be applied to situations where it can be executed by an information processing device, which can be implemented by software and / or hardware. This device can be integrated on a second communication node, which can be a communication node responding to a confirmation request, such as a RAN node. Details not covered in this embodiment can be found in the above embodiments and will not be elaborated upon here.

[0137] As shown in Figure 3, the information processing method provided in this application includes the following operations:

[0138] S310. Obtain a verification request, wherein the verification request instructs verification of the event to be verified.

[0139] This operation can obtain the confirmation request transmitted by the first communication node and respond to the confirmation request.

[0140] S320. Respond to the verification request and obtain a verification report.

[0141] After receiving a confirmation request, this operation can respond to the confirmation request to obtain a confirmation report for the event to be confirmed.

[0142] The method by which this operation responds to the confirmation request is not limited. It can be that the second communication node itself confirms the event to be confirmed; or it can be that a confirmation task is assigned, triggering the other communication nodes to confirm the event to be confirmed.

[0143] This embodiment does not limit the determination of the communication node for verifying the event to be verified. For example, the communication node for verification can be determined by parsing the verification request. Alternatively, it can be determined based on the desired verification method included in the verification request, or based on the desired verification method included in the verification request, a first spatial range, and the ability to select a communication node to perform verification.

[0144] The operation of responding to a confirmation request may include confirming the event to be confirmed, and obtaining a confirmation report after confirmation. This operation can obtain the confirmation report obtained after confirmation.

[0145] In one example, if the event to be verified is verified locally, the verification can be obtained locally. If the event to be verified is verified by other communication nodes, the verification can be obtained from those other communication nodes. These other communication nodes can also be called third communication nodes, such as the communication node that performs the verification of the event to be verified. There can be one or more third communication nodes.

[0146] In this embodiment, when selecting a third communication node, information in the verification request can be referenced, such as the desired verification method. Alternatively, the desired verification method can be ignored, and a third communication node can be selected directly. When referencing the desired verification method, a third communication node that can satisfy the desired verification method can be selected first. If no such node can be selected, a third communication node capable of performing the verification can be selected.

[0147] This operation can be performed by the second communication node itself, which can then obtain a confirmation report, or it can be obtained from the third communication node.

[0148] S330, Transmit the confirmation report.

[0149] After obtaining the confirmation report, this operation can transmit the confirmation report to the first communication node. It can also transmit the confirmation report to any communication node that needs to store the confirmation report.

[0150] The information processing method provided in this embodiment acquires and responds to verification requests to obtain verification reports, thereby verifying the events to be verified and ensuring the accuracy of the events to be verified.

[0151] Based on the above embodiments, modified embodiments of the above embodiments are proposed. It should be noted that, in order to keep the description brief, only the differences from the above embodiments are described in the modified embodiments.

[0152] In one embodiment, responding to the verification request and obtaining a verification report includes:

[0153] In response to the verification request, the verification task is transmitted to the third communication node;

[0154] Obtain the confirmation report.

[0155] In this embodiment, the event to be verified can be verified through a third communication node. The third communication node can be selected by the second communication node, such as based on the verification request and the capabilities of the third communication node.

[0156] In one example, a third communication node can be selected based on the desired verification method in the verification request and the capabilities of the third communication node. Alternatively, a third communication node can be selected based on the desired verification method in the verification request, the first spatial range, and the capabilities of the third communication node. If the selected third communication node meets the desired verification method, it can also verify the event to be verified within the first spatial range.

[0157] In this embodiment, the second communication node responds to the verification request, selects a third communication node capable of verifying the event to be verified, and then transmits the verification task to the third communication node to trigger the third communication node to obtain a verification report. Finally, the verification report determined by the third communication node is obtained.

[0158] Obtaining a confirmation report can be achieved either by the second communication node requesting a confirmation report from the third communication node, or by the third communication node confirming the confirmation report and then transmitting it to the second communication node.

[0159] In this embodiment, the content of the verification task is not limited, as long as it can trigger the third communication node to verify the event to be verified.

[0160] The verification task may include all or part of the information in the verification request. Additionally, the verification task may include information identifying the second communication node.

[0161] In this embodiment, the second communication node transmits a verification task to the third communication node and obtains a verification report transmitted by the third communication node.

[0162] In one embodiment, in response to the verification request, transmitting a verification task to a third communication node includes:

[0163] Based on the expected verification method in the verification request, the first spatial range in the verification request, and the node capability information, a third communication node is determined, and the number of the third communication nodes is at least one.

[0164] The confirmation task is transmitted to the third communication node.

[0165] Node capability information can be considered as information characterizing the capabilities of communication nodes that can perform verification. In this embodiment, a third communication node capable of verifying the event to be verified within the first spatial range can be selected from the nodes corresponding to the node capability information based on the desired verification method. The method of selection based on the desired verification method is not limited here; if the selected third communication node satisfies the desired verification method, the selection can be based solely on the desired verification method, and the final third communication node is determined based on the node capability information.

[0166] The number of selected third communication nodes can be multiple, and each third communication node can independently verify the event to be verified, or they can jointly verify the event to be verified. There is no limitation on the method of joint verification here. For example, each third communication node may verify a portion of the event to be verified.

[0167] Once at least one third communication node is identified, this operation can transmit the verification task to each of the third communication nodes.

[0168] In one embodiment, the verification task includes the information contained in the verification request.

[0169] In this embodiment, the verification task may include information from the verification request to trigger the third communication node to verify the event to be verified. The verification task may include all or part of the information from the verification request.

[0170] In one embodiment, the information processing method further includes:

[0171] Obtain the response information transmitted by the third communication node, the response information indicating whether to execute the verification task.

[0172] After transmitting the verification task to the third communication node, this embodiment can obtain the response information returned by the third communication node. This response information can be considered a response to the verification task. The response information can indicate whether to execute the verification task.

[0173] If the response message indicates that the verification task should not be performed, the second communication node can re-determine the third communication node and transmit the verification task to the re-determined third communication node.

[0174] In one embodiment, obtaining the confirmation report includes:

[0175] Obtain confirmation reports from multiple third-party communication nodes;

[0176] By summarizing the various confirmation reports, a final confirmation report is obtained.

[0177] In this embodiment, there can be multiple third communication nodes. This embodiment can obtain confirmation reports from multiple third communication nodes. The number of confirmation reports obtained here can be the same as the number of third communication nodes determined by the second communication node.

[0178] In different situations, you can continue to acquire confirmation reports from third communication nodes that have not sent confirmation reports. If no confirmation report is acquired after the set time, you can perform a summary confirmation report operation, or select a new communication node to replace the communication node that has not sent a confirmation report, or select a new group for confirmation.

[0179] After obtaining the confirmation reports, this embodiment can summarize the confirmation reports. The summarization method is not limited here. For example, it can combine the confidence information of each confirmation report to form a seed confirmation report. Combining confidence information can be done by first selecting the confirmation report with the highest confidence level from among the various confirmation reports as the summarized confirmation report. Alternatively, it can be done by selecting the top N confidence levels from the confidence information corresponding to each confirmation report, and summarizing the event confirmation results of the confirmation reports corresponding to the top N confidence levels to obtain the summarized confirmation report. Another approach is to calculate the weights of the confidence levels corresponding to the confidence information in each confirmation report to obtain the summarized confirmation report.

[0180] After obtaining the aggregated confirmation report, the aggregated confirmation report can be transmitted to the first communication node.

[0181] In one embodiment, responding to the verification request and obtaining a verification report includes:

[0182] In response to the verification request, the event to be verified is verified according to the verification request, and a verification report is obtained.

[0183] In this embodiment, the second communication node verifies the event to be verified based on the verification request and generates a verification report. After generating the verification report, the verification report is transmitted to the first communication node.

[0184] The specific methods of verification are not specified here.

[0185] In one embodiment, the information processing method further includes:

[0186] Generate a verification certificate, which includes a certificate confirming the event to be verified;

[0187] The verification certificate is transmitted to a fourth communication node, which includes a communication node that stores the verification certificate.

[0188] In this embodiment, after obtaining the verification report, a verification certificate can be generated, and then the verification certificate can be transmitted to the fourth communication node for storage.

[0189] The means of generating the verification certificate are not limited here; they can be related to the information required in the verification certificate. For example, the verification certificate can be generated by combining the information included in the verification request and the information included in the verification report.

[0190] In one example, information from the verification request and information from the verification report are combined to form a verification certificate.

[0191] In one embodiment, the method further includes generating a verification certificate.

[0192] In this embodiment, a verification certificate can be generated. After the verification certificate is generated, it is not necessary to transmit the verification certificate to the fourth communication node.

[0193] In one embodiment, the information processing method further includes:

[0194] Obtain a viewing request, the viewing request indicating that you wish to view the verification certificate;

[0195] The verification certificate is transmitted.

[0196] A request to view can be considered a request to view the verification evidence.

[0197] In this embodiment, a viewing request can be obtained. After obtaining the viewing request, a verification certificate can be sent back. Alternatively, it can be verified whether the communication node sending the viewing request has the necessary permissions; if it does, the verification certificate can be transmitted.

[0198] The communication node transmitting the verification request can be a UE or a RAN node. The UE includes a first communication node that initiates the verification. The RAN node includes a third communication node that responds to the verification request.

[0199] This embodiment can obtain a viewing request from a first communication node and correspondingly transmit confirmation evidence to the first communication node. This embodiment can also obtain a viewing request from a third communication node and correspondingly transmit confirmation evidence to the third communication node.

[0200] In one embodiment, the information processing method further includes:

[0201] Receive a request, the request indicating that the verification certificate be obtained;

[0202] The verification certificate is transmitted.

[0203] A request to retrieve can be considered a request to obtain verification evidence. In this application, a request to view can be a query for verification evidence. A request to retrieve verification evidence can be a request to obtain and store it, thus achieving evidence preservation.

[0204] If the fourth communication node does not store the verification certificate, it can transmit a request to the second communication node to request the verification certificate to be stored.

[0205] After receiving the retrieval request, it is possible to verify whether the communication node that sent the retrieval request has the authority to retrieve it, and if so, to verify the transmission.

[0206] In this embodiment, an acquisition request transmitted by a fourth communication node can be received.

[0207] In one example, after receiving a request from the fourth communication node, a confirmation certificate can be transmitted to the fourth communication node.

[0208] In one embodiment, obtaining the confirmation report includes:

[0209] Obtain confirmation reports from multiple third-party communication nodes;

[0210] The confirmation report is transmitted to the fourth communication node;

[0211] Obtain the summary confirmation report transmitted by the fourth communication node.

[0212] In this embodiment, there can be multiple third communication nodes. The second communication node can use the assistance of a fourth communication node to verify the report results, thereby generating a summarized verification report.

[0213] In this embodiment, the method for obtaining confirmation reports transmitted by multiple third communication nodes is the same as in the above embodiment. After obtaining the formal inclusion, it can be transmitted to the fourth node. The transmission method is not limited here; for example, it can be transmitted to the fourth communication node immediately upon obtaining the confirmed inclusion, or it can be that after obtaining the confirmation reports transmitted by all third communication nodes, each confirmation report is transmitted to the fourth communication node. The fourth communication node then summarizes the reports to obtain the summarized confirmation report. The method of summarizing by the fourth communication node is not limited here and can be the same as the method of summarizing by the second communication node.

[0214] In one embodiment, the confirmation request includes one or more of the following:

[0215] First identification information, the first identification information including information identifying the confirmation request;

[0216] The second identification information includes information that identifies the first communication node;

[0217] Event type, which indicates the type of the event to be verified;

[0218] The first timestamp includes the time when the initial event result of the event to be verified was obtained;

[0219] The result of the initial event;

[0220] The first spatial range includes the spatial range of the event to be verified.

[0221] The priority information of the event to be verified;

[0222] The expected method of confirmation.

[0223] In one embodiment, the confirmation report includes one or more of the following:

[0224] The third identification information includes information identifying the verification report;

[0225] First identification information, the first identification information including information identifying the confirmation request;

[0226] The fourth identification information includes an identifier for the communication node that performs the verification of the event to be verified;

[0227] Event type, which indicates the type of the event to be verified;

[0228] A second timestamp, the second timestamp including the time when the event to be verified was performed;

[0229] Event confirmation results, which include the event results determined after confirming the event to be confirmed;

[0230] The second spatial range includes the spatial range for verifying the event to be verified.

[0231] Confidence information, which indicates the degree of confidence in the confirmation of the event.

[0232] In one embodiment, the proof includes one or more of the following:

[0233] The fifth identification information includes information identifying the verification certificate;

[0234] The third identification information includes information that identifies the verification report;

[0235] First identification information, the first identification information including information identifying the confirmation request;

[0236] Event type, which indicates the type of the event to be verified;

[0237] A second timestamp, the second timestamp including the time when the event to be verified was performed;

[0238] Event confirmation results, which include the event results determined after confirming the event to be confirmed;

[0239] The second spatial range includes the spatial range for verifying the event to be verified.

[0240] The second identification information includes information that identifies the first communication node;

[0241] The fourth identification information includes identifying the communication node that performs the verification of the event to be verified.

[0242] In one embodiment, a view request includes one or more of the following:

[0243] The fifth identification information includes information identifying the verification certificate;

[0244] The third identification information includes information identifying the verification report;

[0245] First identification information, the first identification information including information identifying the confirmation request;

[0246] The second identification information includes information that identifies the first communication node;

[0247] The fourth identification information includes identifying the communication node that performs the verification of the event to be verified.

[0248] In one exemplary embodiment, this application also provides an information processing method. Figure 4 is a flowchart illustrating another information processing method provided in an embodiment of this application. This method is applicable to situations where an event to be verified needs to be verified. This method can be executed by an information processing device, which can be implemented in software and / or hardware, and can be integrated on a third communication node. The third communication node can be a communication node that performs the verification. Examples include a UE other than the first communication node, or a RAN node other than the second communication node. Another example is multiple UEs or a group of UEs, excluding the first communication node. Details not covered in this embodiment can be found in the above embodiments and will not be elaborated upon here.

[0249] As shown in Figure 4, the information processing method provided in this application includes the following operations:

[0250] S410. Obtain a verification task, wherein the verification task includes a task to verify the event to be verified.

[0251] This operation can obtain the confirmation task transmitted by the second communication node to determine whether to confirm the event to be confirmed. If it is determined whether to confirm the event, a response message can be transmitted to the second communication node to indicate whether to execute the confirmation task.

[0252] In one embodiment, a verification task is obtained, and a response message is transmitted, the response message indicating that the verification task is not performed.

[0253] In one embodiment, a verification task is obtained, and response information is transmitted, instructing the execution of the verification task. Then, step S420 is executed.

[0254] S420. In response to the verification task, verify the event to be verified and obtain a verification report.

[0255] When a verification task is determined to be performed, this operation verifies the event to be verified and obtains a verification report. The verification task may include information contained in the verification request. This operation can verify the event to be verified based on the information contained in the verification request and obtain a verification report. No specific verification method is limited here. For example, the event to be verified can be verified based on a first spatial scope to obtain a verification report.

[0256] S430, Transmit confirmation report.

[0257] After receiving a confirmation report, this operation can transmit the confirmation report to the second communication node.

[0258] The information processing method provided in this embodiment involves a third communication node acquiring a verification task, verifying the event to be verified, and obtaining a verification report, thereby achieving the verification of the event to be verified and ensuring the accuracy of the event to be verified.

[0259] Based on the above embodiments, modified embodiments of the above embodiments are proposed. It should be noted that, in order to keep the description brief, only the differences from the above embodiments are described in the modified embodiments.

[0260] In one embodiment, the verification task includes the information contained in the verification request.

[0261] In one embodiment, responding to the verification task by verifying the event to be verified and obtaining a verification report includes:

[0262] In response to the verification task, the event to be verified is verified based on the information contained in the verification request, and a verification report is obtained.

[0263] In this embodiment, the event to be verified can be verified based on the first spatial range, event type, initial event result, and priority information included in the verification request.

[0264] The initial event results of the events to be verified within the first spatial scope are verified. During verification, the order of verification can be determined based on the priority information of the events to be verified.

[0265] Priority information can also be determined by the second communication node to determine the order of responses to confirmation requests.

[0266] In another embodiment, the information processing method further includes:

[0267] A viewing request is transmitted, the viewing request instructing the viewing of verification evidence, the verification evidence including evidence confirming the event to be verified;

[0268] Obtain the aforementioned verification proof.

[0269] In this embodiment, the third communication node can also transmit a viewing request to obtain a confirmation report, which will not be elaborated here.

[0270] In one instance, a third communication node sends a view request to a second communication node to obtain confirmation evidence transmitted by the second communication node.

[0271] In one example, a third communication node can send a view request to a fourth communication node to obtain confirmation evidence transmitted by the fourth communication node.

[0272] In one embodiment, the confirmation request includes one or more of the following information:

[0273] First identification information, the first identification information including information identifying the confirmation request;

[0274] The second identification information includes information that identifies the first communication node;

[0275] Event type, which indicates the type of the event to be verified;

[0276] The first timestamp includes the time when the initial event result of the event to be verified was obtained;

[0277] The result of the initial event;

[0278] The first spatial range includes the spatial range of the event to be verified.

[0279] The priority information of the event to be verified;

[0280] The expected method of confirmation.

[0281] In one embodiment, the confirmation report includes one or more of the following information:

[0282] The third identification information includes information identifying the verification report;

[0283] First identification information, the first identification information including information identifying the confirmation request;

[0284] The fourth identification information includes an identifier for the communication node that performs the verification of the event to be verified;

[0285] Event type, which indicates the type of the event to be verified;

[0286] A second timestamp, the second timestamp including the time when the event to be verified was performed;

[0287] Event confirmation results, which include the event results determined after confirming the event to be confirmed;

[0288] The second spatial range includes the spatial range for verifying the event to be verified.

[0289] Confidence information, which indicates the degree of confidence in the confirmation of the event.

[0290] In one embodiment, the verification proof includes one or more of the following:

[0291] The fifth identification information includes information identifying the verification certificate;

[0292] The third identification information includes information that identifies the verification report;

[0293] First identification information, the first identification information including information identifying the confirmation request;

[0294] Event type, which indicates the type of the event to be verified;

[0295] A second timestamp, the second timestamp including the time when the event to be verified was performed;

[0296] Event confirmation results, which include the event results determined after confirming the event to be confirmed;

[0297] The second spatial range includes the spatial range for verifying the event to be verified.

[0298] The second identification information includes information that identifies the first communication node;

[0299] The fourth identification information includes identifying the communication node that performs the verification of the event to be verified.

[0300] In one embodiment, the viewing request includes one or more of the following:

[0301] The fifth identification information includes information identifying the verification certificate;

[0302] The third identification information includes information identifying the verification report;

[0303] First identification information, the first identification information including information identifying the confirmation request;

[0304] The second identification information includes information that identifies the first communication node;

[0305] The fourth identification information includes identifying the communication node that performs the verification of the event to be verified.

[0306] In one exemplary embodiment, this application also provides an information processing method. Figure 5 is a flowchart illustrating another information processing method provided in an embodiment of this application. This method can be applied to situations where verification evidence corresponding to an event to be verified needs to be viewed. This method can be executed by an information processing device, which can be implemented by software and / or hardware, and can be integrated on a fourth communication node. The fourth communication node can be a core network (CN). Details not covered in this embodiment can be found in the above embodiments and will not be elaborated upon here.

[0307] Referring to Figure 5, the information processing method provided in this application embodiment includes the following operations:

[0308] S510. Obtain a viewing request, the viewing request instructing the viewing of verification evidence, the verification evidence including evidence confirming the event to be verified.

[0309] In this operation, the fourth communication node can receive viewing requests. After receiving a viewing request, it can verify the permissions of the communication node that sent the request to determine if there is a valid viewing request. If so, it obtains and transmits confirmation. If not, it can either not respond or transmit a response indicating that it is not authorized to view.

[0310] In this embodiment, it is possible to obtain viewing requests transmitted by a third communication node, or to obtain viewing requests transmitted by nodes other than the UE and RAN nodes.

[0311] S520, Obtain the verification certificate.

[0312] After receiving a view request, if the communication node that sent the view request has the right to view, this operation can obtain a verification certificate in order to transmit the verification certificate.

[0313] This operation can obtain a verification certificate locally. If no verification certificate is stored at this time, a request can be sent to the second communication node to obtain the verification certificate.

[0314] S530, Transmit the verification certificate.

[0315] After obtaining the verification certificate, this operation can transmit the verification certificate to the communication node that transmitted the view request.

[0316] The information processing method provided in this embodiment enables the viewing of verification evidence for an event to be verified. After the event to be verified and verification evidence is generated, the verification evidence can be viewed through a viewing request. This facilitates viewing the verification evidence while ensuring the accuracy of the event to be verified.

[0317] Based on the above embodiments, modified embodiments of the above embodiments are proposed. It should be noted that, in order to keep the description brief, only the differences from the above embodiments are described in the modified embodiments.

[0318] In one embodiment, obtaining the verification proof includes:

[0319] A request to be acquired is transmitted to the second communication node, the request indicating that the verification certificate be acquired;

[0320] Obtain the aforementioned verification proof.

[0321] In this embodiment, a request to obtain can be transmitted to the second communication node to obtain verification evidence from the second communication node for evidence storage, and a viewing request can be responded to.

[0322] In this application, the communication node that transmits the viewing request to the second communication node and the communication node that transmits the viewing request to the fourth communication node can be the same or different communication nodes.

[0323] For example, the first communication node and / or the third communication node can transmit a viewing request to the second communication node, and can also transmit a viewing request to the fourth communication node.

[0324] A third party can transmit a viewing request to a fourth communication node. This third party can be a communication node outside of the UE and RAN nodes, such as a communication operator and / or equipment provider.

[0325] In one embodiment, the verification proof includes one or more of the following:

[0326] The fifth identification information includes information identifying the verification certificate;

[0327] The third identification information includes information that identifies the verification report;

[0328] First identification information, the first identification information including information identifying the confirmation request;

[0329] Event type, which indicates the type of the event to be verified;

[0330] A second timestamp, the second timestamp including the time when the event to be verified was performed;

[0331] Event confirmation results, which include the event results determined after confirming the event to be confirmed;

[0332] The second spatial range includes the spatial range for verifying the event to be verified.

[0333] The second identification information includes information that identifies the first communication node;

[0334] The fourth identification information includes identifying the communication node that performs the verification of the event to be verified.

[0335] In one embodiment, the viewing request includes one or more of the following:

[0336] The fifth identification information includes information identifying the verification certificate;

[0337] The third identification information includes information identifying the verification report;

[0338] First identification information, the first identification information including information identifying the confirmation request;

[0339] The second identification information includes information that identifies the first communication node;

[0340] The fourth identification information includes identifying the communication node that performs the verification of the event to be verified.

[0341] In one embodiment, the verification certificate transmitted by the second communication node is obtained.

[0342] In one embodiment, confirmation reports from multiple third communication nodes transmitted by the second communication node are obtained, and the individual confirmation reports are summarized to obtain a summarized confirmation report.

[0343] In one embodiment, the verification proof includes one or more of the following:

[0344] The fifth identification information includes information identifying the verification certificate;

[0345] The third identification information includes information that identifies the verification report;

[0346] First identification information, the first identification information including information identifying the confirmation request;

[0347] Event type, which indicates the type of the event to be verified;

[0348] A second timestamp, the second timestamp including the time when the event to be verified was performed;

[0349] Event confirmation results, which include the event results determined after confirming the event to be confirmed;

[0350] The second spatial range includes the spatial range for verifying the event to be verified.

[0351] The second identification information includes information that identifies the first communication node;

[0352] The fourth identification information includes identifying the communication node that performs the verification of the event to be verified.

[0353] The following is an exemplary description of this application. The information processing method provided in this application can be considered as a witnessing mechanism in a mobile network. The witnessing (also known as verification) process can be initiated by the first communication node, such as the UE. When the UE discovers an event that needs to be witnessed, i.e. an event to be verified, it can send a witnessing request to the RAN node, i.e. a verification request. The RAN node performs the witnessing task according to the request, i.e., verification task allocation (assigned to other UEs, RAN nodes, or UE groups, i.e., the third communication node). After the witnessing task is completed, the RAN node returns the witness report, i.e. a verification report, to the requesting UE and generates a witness certificate, i.e. a verification certificate, which is saved to the RAN node or CN, i.e. the fourth communication node. The relevant UE and RAN node (such as any UE and RAN node) can apply for witness certificate storage.

[0354] Figure 6 is a schematic diagram of a transmission confirmation request provided in an embodiment of this application. Referring to Figure 6, the UE sends a confirmation request, i.e., a witness request, to the RAN node through RRC (such as RRC message A), which contains the following information:

[0355] WitnessrequestID corresponds to the first identification information: a unique identifier for the request, used for subsequent tracking and response matching;

[0356] WitnessrequestnodeID corresponds to the second identification information: the ID of the node requesting witnessing, such as UEID;

[0357] Witnesseventtype corresponds to the event type: the type of event requesting witnessing, such as perception result verification, location information verification, signal measurement, etc.

[0358] InitialeventTimestamp corresponds to the first timestamp: the timestamp at which the UE obtains the initial event result.

[0359] Initialeventresult corresponds to the initial event result: the request source, such as the UE's initial event result, such as the perception result, positioning result, signal strength result, etc.

[0360] Witnesstargetlocation corresponds to the first spatial range: the location or area information of the requested witness, which can be based on the UE's precise positioning information or relative area and location information determined based on the UE's capabilities;

[0361] Witnesslevel corresponds to the priority information of the event to be verified: it indicates the urgency of the event that needs to be verified, and can be divided into 0 to represent non-urgent events and 1 to represent urgent events;

[0362] Witnessprogresstype corresponds to the expected verification method: indicating the expected verification method, such as RAN node verification, other UE verification, group UE verification, etc.

[0363] After sending the confirmation request, the RAN node responds with a witness request via RRC. The RAN node can also transmit confirmation information via RRC message B, indicating that the confirmation request has been received.

[0364] After receiving a confirmation request, the RAN node can respond to the confirmation request and assign confirmation tasks. Task assignment may be performed as needed, including:

[0365] 1) The RAN node selects a base station (including the second and third communication nodes) to verify the response;

[0366] 2) The RAN node selects the UE to verify the response;

[0367] 3) The RAN node selects multiple UE / UE groups (UEs within the group can be managed uniformly) to perform combined verification responses.

[0368] When the verification method is UE combined verification, the RAN node can select groups or multiple UEs based on the information in the witness request, the desired verification method, the first spatial range, and UE capability information in multiple UEs / UE groups, and then distribute the witness task to the relevant UEs via unicast / multicast. In other words, the verification task is transmitted to multiple third-party communication nodes.

[0369] Figure 7 is a schematic diagram of an allocation of a verification task provided in an embodiment of this application. Referring to Figure 7, if the witness request receiving node, i.e. the second communication node, needs to send a witness task to other RAN nodes (such as communication nodes other than the second communication node), it can send the information included in the verification request, i.e., witness request info, to the target other RAN nodes through XnAP (which can be a communication protocol used between NG-RAN nodes) (e.g., sent through XnAP message A, where the information included in the verification request is included in the verification task). Other RAN nodes will provide response information, i.e., witness response, depending on whether they accept the task.

[0370] Figure 8 is a schematic diagram of another method of allocating a witness task provided in an embodiment of this application. As shown in Figure 8, if the witness request receiving node needs to send a witness task to other UEs (such as communication nodes other than the first communication node), it can send the witness request info to other UEs through RRC. Other UEs will respond with a witness response depending on whether they accept the task.

[0371] Figure 9 is a schematic diagram of another method for allocating a witness confirmation task according to an embodiment of this application. Referring to Figure 9, if the witness request receiving node needs to issue a witness task to multiple UEs or UE groups, it can send the witness request info to multiple UEs or UE groups according to the UE list (showing multiple UEs or UE groups) via RRC. The UEs will provide a witness response based on whether they accept the task. The sending method can be unicast or multicast depending on the specific number of UEs. The UE group can be a centrally managed group of UEs. The multiple UEs can be randomly combined.

[0372] When a verification task is assigned to a single UE, the UE performs the witnessing (sensing, positioning, signal measurement, etc.) based on the witness request info. After completing the verification task, the UE returns a verification report to the RAN node. The witness report includes one or more of the following:

[0373] The witness report contains the following information:

[0374] The Witness response ID corresponds to the third identification information: a unique identifier for the response, used for subsequent tracking and proof generation;

[0375] The Witness request ID corresponds to the first identification information: a unique identifier for the request, used for subsequent tracking and response matching;

[0376] The Witness node ID corresponds to the fourth identification information: the UE ID that performed the witness task;

[0377] Witness event type corresponds to the event type that requests witnessing, such as perception result verification, location information verification, signal measurement, etc.

[0378] The Witness Time stamp corresponds to the second timestamp: the timestamp of the witnessing process.

[0379] Witness result corresponds to the event confirmation result: the witness result of the initial event of the request source, such as the perception result, the positioning result, the signal strength result, etc.

[0380] Witness location corresponds to the second spatial scope: the location or area information of the witness;

[0381] Witness Confidence level corresponds to confidence information: the witness's confidence assessment of their own witnessing results.

[0382] Figure 10 is an interactive schematic diagram of a confirmation report provided in an embodiment of this application. Referring to Figure 10, after other UEs determine the confirmation report, they transmit the confirmation report through RRC message A. The RAN node transmits the confirmation report to the UE, and the UE transmits information indicating confirmation to the RAN node.

[0383] When a witness task is assigned to a RAN node, the RAN node performs the witness (sensing, positioning, signal measurement, etc.) based on the witnessrequestinfo. After completing the witness task, if the witness task execution node is the request receiving node, the result is returned to the requesting UE; if the execution node is another RAN node, the witness report is returned to the RAN node.

[0384] Figure 11 is a schematic diagram of another type of confirmation report interaction provided in the embodiments of this application. Referring to Figure 11, the RAN node can transmit the confirmation report to the UE through RRC message A, and the UE can transmit an indication of receipt of the confirmation report, i.e., ack, to the RAN node through RRC message B.

[0385] Figure 12 is a schematic diagram of another type of verification report interaction provided in the embodiment of this application. Referring to Figure 12, other RANs transmit the verification report to the RAN node through XnAP message A, the RAN node transmits the verification report to the UE through RRC message B, and the UE transmits an acknowledgment through RRC message C, indicating that the verification report has been obtained.

[0386] When a witness task is assigned to a group of UEs or multiple UEs, the receiving UE performs witnessing (sensing, positioning, signal measurement, etc.) according to the witness request info. After completing the verification task, the UE returns a witness report to the RAN node. The information included in the verification report can be found in the above embodiments.

[0387] After receiving confirmation reports from all assigned UEs, the RAN node summarizes the confirmation results, such as by combining the WitnessConfidencelevel of each UE for weighted calculation, to form the final confirmation. This includes:

[0388] WitnessresponseID: A unique identifier for the response, used for subsequent tracking and witness proof generation;

[0389] WitnessrequestID: A unique identifier for the request, used for subsequent tracking and response matching;

[0390] WitnessnodeIDlist: A list of UEIDs that will perform the witness task;

[0391] Witnesseventtype: The type of event for which witnessing is requested, such as verification of perception results, verification of location information, signal measurement, etc.

[0392] WitnessTimestamp: The timestamp of the witnessing process;

[0393] Witnessresult: Witness results of the initial events of the request source, such as perception results, positioning results, signal strength results, etc.

[0394] Witnesslocation: Location or area information for witnessing;

[0395] WitnessConfidencelevel: A witness's confidence level in their own witnessing results.

[0396] The content of the aforementioned report may be derived from a summary of the contents included in the verification report.

[0397] Figure 13 is an interactive schematic diagram of a summarized confirmation report provided in an embodiment of this application. Referring to Figure 13, multiple UEs or UE groups transmit the confirmation report to the RAN node via RRC. The RAN node transmits the summarized confirmation report to the UE via RRC. The UE receives the confirmation through the RRC transmission indication.

[0398] If the RAN node cannot determine the witnessing result, the RAN node will package the confirmation reports returned by multiple UEs or UE groups, i.e., UEs in the witnessUElist, and send them to the CN. After the CN verifies the witnessing result, it will return the witnessing result report, i.e., the summarized confirmation report.

[0399] Figure 14 is an interactive schematic diagram of another summary confirmation report provided in the embodiments of this application. Referring to Figure 14, the RAN node transmits the packaged confirmation report to the CN (that is, transmits the confirmation report to the fourth communication node) through NGAP message A, and the CN transmits the summary confirmation report to the RAN node through NGAP message B.

[0400] After the RAN node completes the witnessing process, it generates a witnessproof and stores it in both the RAN node and the CN node. The witnessproof includes one or more of the following:

[0401] ProofID corresponds to the fifth identification information: the unique identifier of this proof;

[0402] WitnessresponseID corresponds to the third identification information: a unique identifier for the response, used for subsequent tracking and proof generation;

[0403] WitnessrequestID corresponds to the first identification information: a unique identifier for the request, used for subsequent tracking and response matching;

[0404] Witnesseventtype corresponds to the event type: the type of event requesting witnessing, such as perception result verification, location information verification, signal measurement, etc.

[0405] WitnessTimestamp corresponds to the second timestamp: the timestamp of the witnessing process.

[0406] Witnessresult corresponds to the event confirmation result: the witnessing result of the initial event of the request source, such as the perception result, the positioning result, the signal strength result, etc.

[0407] Witnesslocation corresponds to the second spatial scope: the location or area information of the witness;

[0408] The fourth identifier corresponding to WitnessnodeID(list) is the unique identifier of the witness task execution node;

[0409] WitnessrequestnodeID corresponds to the second identification information: a unique identifier for the witness task request node.

[0410] If the relevant UE or RAN node needs to request to view the verification certificate, it can initiate a viewing request process, which must include at least one of the following information:

[0411] ProofID corresponds to the fifth identification information: the unique identifier of this proof;

[0412] WitnessresponseID corresponds to the third identification information: a unique identifier for the response, used for subsequent tracking and proof generation;

[0413] WitnessrequestID corresponds to the first identification information: a unique identifier for the request, used for subsequent tracking and response matching;

[0414] The fourth identifier corresponding to WitnessnodeID(list) is the unique identifier of the witness task execution node;

[0415] WitnessrequestnodeID corresponds to the second identification information: a unique identifier for the witness task request node.

[0416] Figure 15 is a schematic diagram of a transmission query request provided in an embodiment of this application. Referring to Figure 15, the UE can initiate a query request to the RAN node through RRC to query the verification certificate. The RAN node verifies the certificate according to the request and returns the verification certificate.

[0417] Figure 16 is a schematic diagram of another transmission query request provided in an embodiment of this application. Referring to Figure 16, other RAN nodes can initiate a query request to the RAN node through XnAP to query the verification certificate. The RAN node verifies the certificate according to the request and returns the verification certificate.

[0418] Figure 17 is a schematic diagram of a verification certificate storage method provided in an embodiment of this application. Referring to Figure 17, if it is necessary to send the verification certificate to the CN for storage, the verification certificate can be sent to the CN through NGAP.

[0419] Figure 18 is a schematic diagram of a verification certificate query provided in an embodiment of this application. Referring to Figure 18, other RAN nodes can initiate a query request to the CN node through NGAP to query the verification certificate. The CN verifies the certificate according to the request and returns the verification certificate.

[0420] If a third party needs to apply for verification, they can do so via the Network Exposure Function (NEF) using an Application Programming Interface (API). Information related to this can be found in the information described above. If the requested verification is stored in the CN, it can be retrieved directly. If it is not stored in the CN, a request to retrieve it is transmitted to the second communication node. Figure 19 is a schematic diagram of verification transmission provided in this embodiment. Referring to Figure 19, the verification is sent to the AMF via the RAN node and then to the third party via the Network Exposure Function (NEF).

[0421] In one exemplary embodiment, this application provides an information processing device. FIG20 is a schematic diagram of the structure of an information processing device provided in this application embodiment. The device can be integrated on a first communication node. As shown in FIG20, the device includes:

[0422] The first transmission module 2010 is configured to transmit a confirmation request, wherein the confirmation request indicates that the event to be confirmed should be confirmed.

[0423] The acquisition module 2020 is configured to acquire a confirmation report, which indicates the confirmation result of the event to be confirmed.

[0424] The information processing device provided in this embodiment is used to implement the information processing method shown in Figure 2. The implementation principle and technical effect of the information processing device provided in this embodiment are similar to those of the information processing method shown in Figure 2, and will not be repeated here.

[0425] Based on the above embodiments, modified embodiments of the above embodiments are proposed. It should be noted that, in order to keep the description brief, only the differences from the above embodiments are described in the modified embodiments.

[0426] In one embodiment, the confirmation request includes one or more of the following information:

[0427] First identification information, the first identification information including information identifying the confirmation request;

[0428] The second identification information includes information that identifies the first communication node;

[0429] Event type, which indicates the type of the event to be verified;

[0430] The first timestamp includes the time when the initial event result of the event to be verified was obtained;

[0431] The result of the initial event;

[0432] The first spatial range includes the spatial range of the event to be verified.

[0433] The priority information of the event to be verified;

[0434] The expected method of confirmation.

[0435] In one embodiment, the confirmation report includes one or more of the following information:

[0436] The third identification information includes information identifying the verification report;

[0437] First identification information, the first identification information including information identifying the confirmation request;

[0438] The fourth identification information includes an identifier for the communication node that performs the verification of the event to be verified;

[0439] Event type, which indicates the type of the event to be verified;

[0440] A second timestamp, the second timestamp including the time when the event to be verified was performed;

[0441] Event confirmation results, which include the event results determined after confirming the event to be confirmed;

[0442] The second spatial range includes the spatial range for verifying the event to be verified.

[0443] Confidence information, which indicates the degree of confidence in the confirmation of the event.

[0444] In one embodiment, the information processing apparatus further includes a second transmission module, configured as follows:

[0445] A viewing request is transmitted, the viewing request instructing the viewing of verification evidence, the verification evidence including evidence confirming the event to be verified;

[0446] Obtain the aforementioned verification proof.

[0447] In one embodiment, the verification proof includes one or more of the following:

[0448] The fifth identification information includes information identifying the verification certificate;

[0449] The third identification information includes information that identifies the verification report;

[0450] First identification information, the first identification information including information identifying the confirmation request;

[0451] Event type, which indicates the type of the event to be verified;

[0452] A second timestamp, the second timestamp including the time when the event to be verified was performed;

[0453] Event confirmation results, which include the event results determined after confirming the event to be confirmed;

[0454] The second spatial range includes the spatial range for verifying the event to be verified.

[0455] The second identification information includes information that identifies the first communication node;

[0456] The fourth identification information includes identifying the communication node that performs the verification of the event to be verified.

[0457] In one embodiment, the viewing request includes one or more of the following:

[0458] The fifth identification information includes information identifying the verification certificate;

[0459] The third identification information includes information identifying the verification report;

[0460] First identification information, the first identification information including information identifying the confirmation request;

[0461] The second identification information includes information that identifies the first communication node;

[0462] The fourth identification information includes identifying the communication node that performs the verification of the event to be verified.

[0463] In one exemplary embodiment, this application also provides an information processing device. FIG21 is a schematic diagram of the structure of another information processing device provided in an embodiment of this application. The information processing device can be integrated on a second communication node. As shown in FIG21, the device includes:

[0464] The first acquisition module 2110 is configured to acquire a verification request, wherein the verification request indicates that the event to be verified is to be verified.

[0465] The second acquisition module 2120 is configured to acquire a verification report in response to the verification request;

[0466] The transmission module 2130 is configured to transmit the confirmation report.

[0467] The information processing device provided in this embodiment is used to implement the information processing method shown in Figure 3. The implementation principle and technical effect of the information processing device provided in this embodiment are similar to those of the information processing method shown in Figure 3, and will not be repeated here.

[0468] Based on the above embodiments, modified embodiments of the above embodiments are proposed. It should be noted that, in order to keep the description brief, only the differences from the above embodiments are described in the modified embodiments.

[0469] In one embodiment, the second acquisition module 2120 includes:

[0470] The transmission unit is configured to transmit a verification task to a third communication node in response to the verification request;

[0471] The acquisition unit is configured to acquire the confirmation report.

[0472] In one embodiment, the transmission unit is configured as follows:

[0473] Based on the expected verification method in the verification request, the first spatial range in the verification request, and the node capability information, a third communication node is determined, and the number of the third communication nodes is at least one.

[0474] The confirmation task is transmitted to the third communication node.

[0475] In one embodiment, the verification task includes the information contained in the verification request.

[0476] In one embodiment, the information processing apparatus further includes a third acquisition module, configured as follows:

[0477] Obtain the response information transmitted by the third communication node, the response information indicating whether to execute the verification task.

[0478] In one embodiment, the acquisition unit is specifically configured as follows:

[0479] Obtain confirmation reports from multiple third-party communication nodes;

[0480] By summarizing the various confirmation reports, a final confirmation report is obtained.

[0481] In one embodiment, the second acquisition module 2120 is specifically configured as follows:

[0482] In response to the verification request, the event to be verified is verified according to the verification request, and a verification report is obtained.

[0483] In one embodiment, the information processing apparatus further includes a generation module configured to:

[0484] Generate a verification proof;

[0485] The verification certificate is transmitted to a fourth communication node, which includes a communication node that stores the verification certificate.

[0486] In one embodiment, the information processing apparatus further includes a fourth acquisition module, configured as follows:

[0487] Obtain a viewing request, the viewing request indicating that you wish to view the verification certificate;

[0488] The verification certificate is transmitted.

[0489] In one embodiment, the information processing apparatus further includes a receiving module configured to:

[0490] Receive a request, the request indicating that the verification certificate be obtained;

[0491] The verification certificate is transmitted.

[0492] In one embodiment, the acquisition unit is specifically configured as follows:

[0493] Obtain confirmation reports from multiple third-party communication nodes;

[0494] The confirmation report is transmitted to the fourth communication node;

[0495] Obtain the summary confirmation report transmitted by the fourth communication node.

[0496] In one embodiment, the confirmation request includes one or more of the following:

[0497] First identification information, the first identification information including information identifying the confirmation request;

[0498] The second identification information includes information that identifies the first communication node;

[0499] Event type, which indicates the type of the event to be verified;

[0500] The first timestamp includes the time when the initial event result of the event to be verified was obtained;

[0501] The result of the initial event;

[0502] The first spatial range includes the spatial range of the event to be verified.

[0503] The priority information of the event to be verified;

[0504] The expected method of confirmation.

[0505] In one embodiment, the confirmation report includes one or more of the following:

[0506] The third identification information includes information identifying the verification report;

[0507] First identification information, the first identification information including information identifying the confirmation request;

[0508] The fourth identification information includes an identifier for the communication node that performs the verification of the event to be verified;

[0509] Event type, which indicates the type of the event to be verified;

[0510] A second timestamp, the second timestamp including the time when the event to be verified was performed;

[0511] Event confirmation results, which include the event results determined after confirming the event to be confirmed;

[0512] The second spatial range includes the spatial range for verifying the event to be verified.

[0513] Confidence information, which indicates the degree of confidence in the confirmation of the event.

[0514] In one embodiment, the proof includes one or more of the following:

[0515] The fifth identification information includes information identifying the verification certificate;

[0516] The third identification information includes information that identifies the verification report;

[0517] First identification information, the first identification information including information identifying the confirmation request;

[0518] Event type, which indicates the type of the event to be verified;

[0519] A second timestamp, the second timestamp including the time when the event to be verified was performed;

[0520] Event confirmation results, which include the event results determined after confirming the event to be confirmed;

[0521] The second spatial range includes the spatial range for verifying the event to be verified.

[0522] The second identification information includes information that identifies the first communication node;

[0523] The fourth identification information includes identifying the communication node that performs the verification of the event to be verified.

[0524] In one embodiment, a view request includes one or more of the following:

[0525] The fifth identification information includes information identifying the verification certificate;

[0526] The third identification information includes information identifying the verification report;

[0527] First identification information, the first identification information including information identifying the confirmation request;

[0528] The second identification information includes information that identifies the first communication node;

[0529] The fourth identification information includes identifying the communication node that performs the verification of the event to be verified.

[0530] In one exemplary embodiment, this application also provides an information processing apparatus, and FIG22 is a schematic diagram of another information processing apparatus provided in an embodiment of this application; the apparatus can be integrated on a third communication node, and the apparatus includes:

[0531] The acquisition module 2210 is configured to acquire verification tasks, wherein the verification tasks include tasks for verifying events to be verified.

[0532] The verification module 2220 is configured to respond to the verification task, verify the event to be verified, and obtain a verification report;

[0533] The first transmission module 2230 is configured to transmit a confirmation report.

[0534] The information processing device provided in this embodiment is used to implement the information processing method shown in Figure 4. The implementation principle and technical effect of the information processing device provided in this embodiment are similar to those of the information processing method shown in Figure 4, and will not be repeated here.

[0535] Based on the above embodiments, modified embodiments of the above embodiments are proposed. It should be noted that, in order to keep the description brief, only the differences from the above embodiments are described in the modified embodiments.

[0536] In one embodiment, the verification task includes the information contained in the verification request.

[0537] In one embodiment, the verification module 2220 is specifically configured as follows:

[0538] In response to the verification task, the event to be verified is verified based on the information contained in the verification request, and a verification report is obtained.

[0539] In one embodiment, the information processing apparatus further includes a second transmission module, configured as follows:

[0540] A viewing request is transmitted, the viewing request instructing the viewing of verification evidence, the verification evidence including evidence confirming the event to be verified;

[0541] Obtain the aforementioned verification proof.

[0542] In one embodiment, the confirmation request includes one or more of the following information:

[0543] First identification information, the first identification information including information identifying the confirmation request;

[0544] The second identification information includes information that identifies the first communication node;

[0545] Event type, which indicates the type of the event to be verified;

[0546] The first timestamp includes the time when the initial event result of the event to be verified was obtained;

[0547] The result of the initial event;

[0548] The first spatial range includes the spatial range of the event to be verified.

[0549] The priority information of the event to be verified;

[0550] The expected method of confirmation.

[0551] In one embodiment, the confirmation report includes one or more of the following information:

[0552] The third identification information includes information identifying the verification report;

[0553] First identification information, the first identification information including information identifying the confirmation request;

[0554] The fourth identification information includes an identifier for the communication node that performs the verification of the event to be verified;

[0555] Event type, which indicates the type of the event to be verified;

[0556] A second timestamp, the second timestamp including the time when the event to be verified was performed;

[0557] Event confirmation results, which include the event results determined after confirming the event to be confirmed;

[0558] The second spatial range includes the spatial range for verifying the event to be verified.

[0559] Confidence information, which indicates the degree of confidence in the confirmation of the event.

[0560] In one embodiment, the verification proof includes one or more of the following:

[0561] The fifth identification information includes information identifying the verification certificate;

[0562] The third identification information includes information that identifies the verification report;

[0563] First identification information, the first identification information including information identifying the confirmation request;

[0564] Event type, which indicates the type of the event to be verified;

[0565] A second timestamp, the second timestamp including the time when the event to be verified was performed;

[0566] Event confirmation results, which include the event results determined after confirming the event to be confirmed;

[0567] The second spatial range includes the spatial range for verifying the event to be verified.

[0568] The second identification information includes information that identifies the first communication node;

[0569] The fourth identification information includes identifying the communication node that performs the verification of the event to be verified.

[0570] In one embodiment, the viewing request includes one or more of the following:

[0571] The fifth identification information includes information identifying the verification certificate;

[0572] The third identification information includes information identifying the verification report;

[0573] First identification information, the first identification information including information identifying the confirmation request;

[0574] The second identification information includes information that identifies the first communication node;

[0575] The fourth identification information includes identifying the communication node that performs the verification of the event to be verified.

[0576] In one exemplary embodiment, this application also provides an information processing apparatus. FIG23 is a schematic diagram of the structure of another information processing apparatus provided in an embodiment of this application. The information processing apparatus can be integrated on a fourth communication node. As shown in FIG23, the apparatus includes:

[0577] The first acquisition module 2310 is configured to acquire a viewing request, wherein the viewing request indicates viewing a verification certificate, and the verification certificate includes a certificate confirming the event to be verified;

[0578] The second acquisition module 2320 is configured to acquire the verification proof;

[0579] The transmission module 2330 is configured to transmit the verification certificate.

[0580] The information processing device provided in this embodiment is used to implement the information processing method shown in Figure 5. The implementation principle and technical effect of the information processing device provided in this embodiment are similar to those of the information processing method shown in Figure 5, and will not be repeated here.

[0581] Based on the above embodiments, modified embodiments of the above embodiments are proposed. It should be noted that, in order to keep the description brief, only the differences from the above embodiments are described in the modified embodiments.

[0582] In one embodiment, the second acquisition module 2320 is specifically configured as follows:

[0583] A request to be acquired is transmitted to the second communication node, the request indicating that the verification certificate be acquired;

[0584] Obtain the aforementioned verification proof.

[0585] In one embodiment, the verification proof includes one or more of the following:

[0586] The fifth identification information includes information identifying the verification certificate;

[0587] The third identification information includes information that identifies the verification report;

[0588] First identification information, the first identification information including information identifying the confirmation request;

[0589] Event type, which indicates the type of the event to be verified;

[0590] A second timestamp, the second timestamp including the time when the event to be verified was performed;

[0591] Event confirmation results, which include the event results determined after confirming the event to be confirmed;

[0592] The second spatial range includes the spatial range for verifying the event to be verified.

[0593] The second identification information includes information that identifies the first communication node;

[0594] The fourth identification information includes identifying the communication node that performs the verification of the event to be verified.

[0595] In one embodiment, the viewing request includes one or more of the following:

[0596] The fifth identification information includes information identifying the verification certificate;

[0597] The third identification information includes information identifying the verification report;

[0598] First identification information, the first identification information including information identifying the confirmation request;

[0599] The second identification information includes information that identifies the first communication node;

[0600] The fourth identification information includes identifying the communication node that performs the verification of the event to be verified.

[0601] In one embodiment, the verification certificate transmitted by the second communication node is obtained.

[0602] In one embodiment, confirmation reports from multiple third communication nodes transmitted by the second communication node are obtained, and the individual confirmation reports are summarized to obtain a summarized confirmation report.

[0603] In one embodiment, the verification proof includes one or more of the following:

[0604] The fifth identification information includes information identifying the verification certificate;

[0605] The third identification information includes information that identifies the verification report;

[0606] First identification information, the first identification information including information identifying the confirmation request;

[0607] Event type, which indicates the type of the event to be verified;

[0608] A second timestamp, the second timestamp including the time when the event to be verified was performed;

[0609] Event confirmation results, which include the event results determined after confirming the event to be confirmed;

[0610] The second spatial range includes the spatial range for verifying the event to be verified.

[0611] The second identification information includes information that identifies the first communication node;

[0612] The fourth identification information includes identifying the communication node that performs the verification of the event to be verified.

[0613] In one exemplary embodiment, this application also provides a communication node. FIG24 is a schematic diagram of the structure of a communication node provided in this application embodiment. The communication node can be one or more of the first communication node, second communication node, third communication node and fourth communication node in this application. As shown in FIG24, the first communication node provided in this application includes one or more processors 241 and a storage device 242. The processors 241 in the first communication node can be one or more, and FIG24 takes one processor 241 as an example. The storage device 242 is used to store one or more programs. The one or more programs are executed by the one or more processors 241, so that the one or more processors 241 implement the information processing method as described in the embodiment of this application.

[0614] The first communication node also includes: a communication device 243, an input device 244, and an output device 245.

[0615] The processor 241, storage device 242, communication device 243, input device 244, and output device 245 in the first communication node can be connected by a bus or other means. Figure 24 shows an example of connection via a bus.

[0616] Input device 244 can be used to receive input digital or character information, and to generate key signal inputs related to user settings and function control of the first communication node. Output device 245 may include display devices such as a display screen.

[0617] The communication device 243 may include a receiver and a transmitter. The communication device 243 is configured to perform information transmission and reception communication under the control of the processor 241.

[0618] Storage device 242, as a computer-readable storage medium, can be configured to store software programs, computer-executable programs, and modules, such as program instructions / modules corresponding to the information processing method described in the embodiments of this application (e.g., the first transmission module 2010 and acquisition module 2020 in the information processing device; or the first acquisition module 2110, second acquisition module 2120, and transmission module 2130 in the information processing device; or the acquisition module 2210, verification module 2220, and first transmission module 2230 in the information processing device; or the first acquisition module 2310, second acquisition module 2320, and transmission module 2330 in the information processing device). Storage device 242 may include a program storage area and a data storage area, wherein the program storage area may store the operating system and at least one application program required for a function; the data storage area may store data created based on the use of the first communication node, etc. In addition, storage device 242 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some instances, storage device 242 may further include memory remotely disposed relative to processor 241, which can be connected to the first communication node via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0619] In one exemplary embodiment, this application also provides a storage medium storing a computer program that, when executed by a processor, implements any of the methods described in this application. The storage medium stores a computer program that, when executed by a processor, implements any of the information processing methods described in the embodiments of this application. Examples include information processing methods applied to a first communication node, a second communication node, a third communication node, and a fourth communication node.

[0620] Among them, the information processing method applied to the first communication node is: transmitting a confirmation request, wherein the confirmation request indicates that the event to be confirmed be verified;

[0621] Obtain a confirmation report, which indicates the confirmation result of the event to be confirmed.

[0622] The information processing method applied to the second communication node includes: obtaining a confirmation request, wherein the confirmation request indicates that the event to be confirmed be verified;

[0623] In response to the verification request, obtain a verification report;

[0624] Transmit the confirmation report.

[0625] Information processing methods applied to third communication nodes include:

[0626] Obtain a verification task, wherein the verification task includes a task to verify the event to be verified;

[0627] In response to the verification task, the event to be verified is verified, and a verification report is obtained;

[0628] Transmit confirmation report.

[0629] Information processing methods applied to the fourth communication node include:

[0630] Obtain a viewing request, the viewing request instructing the viewing of verification evidence, the verification evidence including evidence confirming the event to be verified;

[0631] Obtain the aforementioned verification proof;

[0632] The verification certificate is transmitted.

[0633] The computer storage medium in this application embodiment can be any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. For example, a computer-readable storage medium can be, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable CD-ROM, optical storage device, magnetic storage device, or any suitable combination thereof. The computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0634] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media may also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit programs for use by or in connection with an instruction execution system, apparatus, or device.

[0635] Program code contained on a computer-readable medium may be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, radio frequency (RF), etc., or any suitable combination thereof.

[0636] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, and C++, as well as conventional procedural programming languages ​​such as "C" or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0637] The above description is merely an exemplary embodiment of this application and is not intended to limit the scope of protection of this application.

[0638] Those skilled in the art will understand that the term terminal equipment covers any suitable type of wireless user equipment, such as mobile phones, portable data processing devices, portable web browsers, or vehicle-mounted mobile stations.

[0639] Generally, the various embodiments of this application can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. For example, some aspects can be implemented in hardware, while others can be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although this application is not limited thereto.

[0640] Embodiments of this application can be implemented by executing computer program instructions through the data processor of a mobile device, for example, in a processor entity, or through hardware, or through a combination of software and hardware. The computer program instructions can be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, status setting data, or source code or object code written in any combination of one or more programming languages.

[0641] Any block diagram of logical flow in the accompanying drawings of this application may represent program steps, or may represent interconnected logic circuits, modules, and functions, or may represent a combination of program steps and logic circuits, modules, and functions. The computer program may be stored on memory. Memory may be of any type suitable to the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, read-only memory (ROM), random access memory (RAM), optical storage devices and systems (Digital Video Disc (DVD) or Compact Disk (CD)), etc. Computer-readable media may include non-transitory storage media. The data processor may be of any type suitable to the local technical environment, such as, but not limited to, general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), and processors based on multi-core processor architectures.

[0642] A detailed description of exemplary embodiments of this application has been provided above through exemplary and non-limiting examples. However, various modifications and adjustments to the above embodiments will be apparent to those skilled in the art when considered in conjunction with the accompanying drawings and claims, without departing from the scope of this disclosure.

Claims

1. An information processing method, characterized in that, Applied to a first communication node, the method includes: transmitting a confirmation request, the confirmation request indicating confirmation of an event to be confirmed; and obtaining a confirmation report, the confirmation report indicating the confirmation result of the event to be confirmed.

2. The method according to claim 1, characterized in that, The confirmation request includes one or more of the following information: first identification information, which includes information identifying the confirmation request; and second identification information, which includes information identifying the first communication node. Event type, which indicates the type of the event to be verified; The first timestamp includes the time when the initial event result of the event to be verified was obtained; The result of the initial event; The first spatial range includes the spatial range of the event to be verified. The priority information of the event to be verified; The expected method of confirmation.

3. The method according to claim 1, characterized in that, The confirmation report includes one or more of the following information: third identification information, which includes information identifying the confirmation report; first identification information, which includes information identifying the confirmation request; and fourth identification information, which includes information identifying the communication node that performed the confirmation of the event to be confirmed. Event type, which indicates the type of the event to be verified; A second timestamp, the second timestamp including the time when the event to be verified was performed; Event confirmation results, which include the event results determined after confirming the event to be confirmed; The second spatial range includes the spatial range for verifying the event to be verified; confidence information indicates the confidence level of the verification result of the event.

4. The method according to claim 1, characterized in that, Also includes: A viewing request is transmitted, the viewing request instructing the viewing of verification evidence, the verification evidence including evidence confirming the event to be verified; Obtain the aforementioned verification proof.

5. The method according to claim 4, characterized in that, The verification certificate includes one or more of the following: fifth identification information, which includes information identifying the verification certificate; third identification information, which includes information identifying the verification report; first identification information, which includes information identifying the verification request; and event type, which indicates the type of the event to be verified. A second timestamp, the second timestamp including the time when the event to be verified was performed; The event verification result includes the event result determined after verifying the event to be verified; the second spatial range includes the spatial range for verifying the event to be verified; the second identification information includes information identifying the first communication node; and the fourth identification information includes information identifying the communication node that performed the verification of the event to be verified.

6. The method according to claim 4, characterized in that, The viewing request includes one or more of the following: fifth identification information, which includes information identifying the verification certificate; third identification information, which includes information identifying the verification report; first identification information, which includes information identifying the verification request; second identification information, which includes information identifying the first communication node; and fourth identification information, which includes information identifying the communication node performing the verification of the event to be verified.

7. An information processing method, characterized in that, Applied to a second communication node, the method includes: obtaining a verification request, the verification request indicating verification of an event to be verified; responding to the verification request and obtaining a verification report; and transmitting the verification report.

8. The method according to claim 7, characterized in that, The step of responding to the verification request and obtaining the verification report includes: responding to the verification request by transmitting the verification task to the third communication node; and obtaining the verification report.

9. The method according to claim 8, characterized in that, In response to the verification request, transmitting a verification task to a third communication node includes: determining a third communication node based on the expected verification method in the verification request, the first spatial range in the verification request, and node capability information, wherein the number of third communication nodes is at least one; and transmitting the verification task to the third communication node.

10. The method according to claim 9, characterized in that, The verification task includes the information contained in the verification request.

11. The method according to claim 9, characterized in that, Also includes: Obtain the response information transmitted by the third communication node, the response information indicating whether to execute the verification task.

12. The method according to claim 8, characterized in that, The process of obtaining the confirmation report includes: obtaining confirmation reports transmitted by multiple third communication nodes; and summarizing the confirmation reports to obtain a summarized confirmation report.

13. The method according to claim 7, characterized in that, The step of responding to the verification request and obtaining a verification report includes: responding to the verification request, verifying the event to be verified according to the verification request, and obtaining a verification report.

14. The method according to claim 7, characterized in that, Also includes: Generate a verification certificate; transmit the verification certificate to a fourth communication node, the fourth communication node including a communication node storing the verification certificate.

15. The method according to claim 7, characterized in that, Also includes: Obtain a viewing request, the viewing request indicating that the verification certificate is to be viewed; transmit the verification certificate.

16. The method according to claim 7, characterized in that, Also includes: Receive a request, the request indicating that the verification certificate be obtained; The verification certificate is transmitted.

17. The method according to claim 7, characterized in that, The process of obtaining the confirmation report includes: obtaining confirmation reports transmitted by multiple third communication nodes; transmitting the confirmation reports to a fourth communication node; and obtaining a summarized confirmation report transmitted by the fourth communication node.

18. An information processing method, characterized in that, Applied to a third communication node, the method includes: obtaining a verification task, the verification task including a task to verify an event to be verified; responding to the verification task, verifying the event to be verified, and obtaining a verification report; and transmitting the verification report.

19. The method according to claim 18, characterized in that, The verification task includes the information contained in the verification request.

20. The method according to claim 19, characterized in that, The step of responding to the verification task and verifying the event to be verified to obtain a verification report includes: responding to the verification task and verifying the event to be verified based on the information contained in the verification request to obtain a verification report.

21. The method according to claim 18, characterized in that, Also includes: A viewing request is transmitted, the viewing request instructing the viewing of verification evidence, the verification evidence including evidence confirming the event to be verified; Obtain the aforementioned verification proof.

22. An information processing method, characterized in that, Applied to a fourth communication node, the method includes: obtaining a viewing request, the viewing request instructing the viewing of a verification certificate, the verification certificate including a certificate verifying the event to be verified; obtaining the verification certificate; and transmitting the verification certificate.

23. The method according to claim 22, characterized in that, The step of obtaining the verification certificate includes: transmitting an acquisition request to a second communication node, the acquisition request indicating the acquisition of the verification certificate; and acquiring the verification certificate.

24. A communication node, characterized in that, include: One or more processors; Storage device for storing one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the method as described in any one of claims 1-6, or the method as described in any one of claims 7-17, or the method as described in any one of claims 18-21, or the method as described in any one of claims 22-23.

25. A storage medium, characterized in that, The storage medium stores a computer program that, when executed by a processor, implements the method described in any one of claims 1-23.

26. A computer program product comprising a computer program that, when executed by a processor, implements the method according to any one of claims 1-23.

Images