CN116471621A

CN116471621A - Method for supporting wireless communication network data collection

Info

Publication number: CN116471621A
Application number: CN202310067610.2A
Authority: CN
Inventors: 王妍茹; 麻晓宁; 许丽香; 汪巍崴; 王弘
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2022-01-19
Filing date: 2023-01-13
Publication date: 2023-07-21

Abstract

A method performed by a first entity in a wireless communication network is disclosed, the method comprising receiving a message comprising information related to network data collection from a second entity.

Description

Method for supporting wireless communication network data collection

Technical Field

The present disclosure relates to a method of supporting wireless communication network data collection and an apparatus thereof.

Background

In order to meet the increasing demand for wireless data communication services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or quasi 5G communication systems. Therefore, a 5G or quasi 5G communication system is also referred to as a "super 4G network" or a "LTE-after-system".

Wireless communication is one of the most successful innovations in modern history. Recently, the number of subscribers to wireless communication services exceeds 50 billion and continues to grow rapidly. As smartphones and other mobile data devices (e.g., tablet computers, notebook computers, netbooks, e-book readers, and machine type devices) become increasingly popular among consumers and businesses, the demand for wireless data services is rapidly growing. To meet the high-speed growth of mobile data services and support new applications and deployments, it is important to improve the efficiency and coverage of the wireless interface.

Different entities in a wireless communication network may be classified into different kinds of User Equipment (UE), access node, mobility management function entity, session management function entity, data plane function entity, etc. according to the task to be undertaken.

Disclosure of Invention

Technical problem

The current stage can not support the user model management and the user reasoning content reporting management in the moving process, which can cause repeated downloading and installation of the model, excessive storage of a User Equipment (UE) useless model, invalid model reasoning and/or training of the UE and the like, so that the performance of the network and the UE can not be ensured. The network entity cannot be supported to interact with the calculation power information at the present stage, so that the calculation power cannot be reasonably distributed and/or corresponding strategies cannot be set to ensure the performance of the network and the user equipment.

Technical proposal for solving the problems

According to one aspect of the present disclosure, there is provided a method performed by a first entity in a wireless communication network, the method comprising receiving a message comprising information related to network data collection from a second entity.

In an embodiment, receiving a message from the second entity comprising information related to network data collection comprises receiving a second message from the second entity comprising UE model information, and further comprising sending a first message comprising a user equipment UE model information request to the second entity before receiving the second message from the second entity comprising UE model information. The first message includes one or more of the following: the method comprises the steps of UE identification, application range of content of the first message, switching time, UE model information reporting request identification, reporting registration request, reporting time interval, reporting time, information reporting type, information reporting period, reporting trigger condition configuration and content to be reported; and wherein reporting the content includes one or more of: the number and/or list of numbers of the model, the name of the model, the purpose of the model, the state of the model integrity, the state of the model which is not downloaded, the model download address, the model download proportion, the suggested measure, the measure suggested for the model which is not downloaded, the model accuracy, the model activation condition, the model deactivation condition, the model activation time, the model deactivation time, the reasoning content reporting condition; and wherein the inferential content reporting conditions include one or more of: the method comprises the steps of reasoning content reporting type, reasoning content reporting period, reasoning content reporting triggering condition, reported reasoning content, and applicable time and accuracy of the reasoning content which is requested to report and/or reported. The second message includes one or more of the following: the UE identification, the application range of the content of the second message, the reporting confirmation of the requested content, the triggering condition and the model information content; and wherein the model information content includes one or more of: the number and/or list of numbers of the model, the name of the model, the purpose of the model, the state of model integrity, the state of the model which is not downloaded, suggested actions, actions suggested for the model which is not downloaded, model accuracy, model download address, model download proportion, model activation condition, model deactivation condition, model activation time, model deactivation time, reasoning content reporting condition; and wherein the inferential content reporting conditions include one or more of: the method comprises the steps of reasoning content reporting type, reasoning content reporting period, reasoning content reporting triggering condition, reported reasoning content, and applicable time and accuracy of the reported reasoning content.

In an embodiment, receiving a message from the second entity comprising information related to network data collection comprises receiving a fourth message from the second entity comprising UE model management decisions. The fourth message includes one or more of the following: UE identity, application range of the content of the fourth message, model management decision; and wherein the model management decision comprises one or more of: the number and/or list of numbers of the model, the name of the model, the purpose of the model, the state of the model which is not downloaded, the decision for the model which is not downloaded, the list of models which is activated, the model activation indication, the model deactivation indication, the model activation time, the model deactivation time, the model activation condition, the model deactivation condition, the forwarding strategy which is applicable to the model which is already downloaded, the model forwarding strategy which is applicable to the model which is not downloaded, the model forwarding proportion, the reasoning content reporting decision; and wherein the inferential content reporting decision comprises one or more of: the method comprises the steps of reporting the type of the reasoning content, reporting the period of the reasoning content, reporting the triggering condition of the reasoning content, reporting the reasoning content, applying time of the reported reasoning content, requesting to report the reasoning content, applying time and accuracy of the requesting to report the reasoning content.

In an embodiment, receiving a message from the second entity comprising information related to network data collection comprises receiving a sixth message from the second entity comprising a UE model, and further comprising sending a fifth message to the second entity comprising a UE model forwarding request before receiving the sixth message from the second entity comprising the UE model. The fifth message includes one or more of the following: the UE identification, the application range of the content of the fifth message, the switching time, the model forwarding request identification, the model forwarding registration request, the model forwarding time interval, the model forwarding time, the model forwarding proportion, the model forwarding type, the model forwarding trigger condition configuration, the model downloading address, the model downloading proportion and the content needing to be forwarded; and wherein forwarding the content includes one or more of: the model number and/or number list, the model name, the model purpose, the model state, the model accuracy, the model type, the model characteristic parameters, the model input parameter type, the model input parameter limiting conditions, the model output parameter type, the model input parameter preprocessing method, the model output parameter post-processing method and the model reasoning content application time. The sixth message includes one or more of the following: the UE identification, the application range of the content of the sixth message, the confirmation that the requested content can be forwarded, the model download proportion, the model forwarding trigger condition, the forwarding content and the issuing content; and wherein forwarding the content includes one or more of: the method comprises the steps of numbering and/or numbering a list of models, names of the models, purposes of the models, states of the models, accuracy of the models, types of the models, input parameter types of characteristic parameter models of the models, input parameter limiting conditions of the models, output parameter types of the models, an input parameter preprocessing method of the models, an output parameter post-processing method of the models and application time of model reasoning content; and wherein the delivered content includes one or more of: the model number and/or number list, the model name, the model purpose, the model state, the model accuracy, the model type, the model characteristic parameters, the model input parameter type, the model input parameter limiting conditions, the model output parameter type, the model input parameter preprocessing method and the model output parameter post-processing method.

In an embodiment, receiving a message from the second entity comprising information related to the network data collection comprises receiving a tenth message from the second entity comprising computational power information.

In an embodiment, receiving a message from the second entity comprising information related to the network data collection comprises sending an eighth message to the second entity comprising information for requesting the computing power information, receiving a ninth message from the second entity comprising information in response to the eighth message or a tenth message comprising the computing power information. The eighth message includes one or more of the following: the application range of the content of the eighth message, the prediction identifier, the prediction registration request, the reporting time interval, the reporting time, the prediction information reporting time interval, the prediction information reporting time, the prediction result application time of the prediction information, the calculation information reporting type, the calculation information reporting period, the calculation information reporting trigger condition configuration, the prediction calculation information reporting type, the prediction calculation information reporting period, the prediction calculation information reporting trigger condition configuration, the calculation information content to be reported and the calculation information content to be reported. The ninth message includes one or more of the following: the application range of the content of the ninth message, the reporting confirmation of the requested content, the reporting confirmation of the requested predicted content, the reporting triggering condition of the calculation force information, the reporting triggering condition of the predicted calculation force information, the reporting content of the predicted calculation force information, the accuracy of the predicted calculation force information and the application time of the predicted calculation force information. The tenth message includes one or more of the following: the application range of the content of the tenth message, the reporting triggering condition of the calculation force information, the reporting triggering condition of the predicted calculation force information, the reporting content of the predicted calculation force information, the accuracy of the predicted calculation force information and the application time of the predicted calculation force information.

According to another aspect of the disclosure, there is provided a method performed by a second entity in a wireless communication network, the method comprising sending a message comprising information related to network data collection to a first entity. Wherein the message including information related to network data collection includes one of: a message comprising user equipment, UE, model information, a message comprising a UE model management decision, a message comprising a UE model, a message comprising a response to a calculation information reporting request, and a message comprising calculation information.

According to yet another aspect of the present disclosure, there is provided an entity in a wireless communication network, the entity comprising a processor and a transceiver, the processor being coupled to the transceiver and configured to perform the above-described methods, steps and operations.

Advantageous effects of the invention

The present disclosure provides a method for supporting wireless communication network data collection, so that model issuing and/or training and/or reasoning effectiveness of a UE can be guaranteed, and unnecessary model issuing and/or training and/or reasoning is reduced.

Drawings

The above and other aspects, features and advantages of the present invention will become more apparent from the following detailed description when taken in conjunction with the accompanying drawings.

FIG. 1 illustrates an exemplary system architecture for System Architecture Evolution (SAE);

FIG. 2 illustrates an exemplary system architecture according to various embodiments of the present disclosure;

fig. 3 is a schematic diagram illustrating one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure;

fig. 4 is a schematic diagram illustrating one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure;

fig. 5 is a schematic diagram illustrating one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure;

fig. 6 is a schematic diagram illustrating one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure;

fig. 7 is a schematic diagram illustrating one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure;

fig. 8 is a schematic diagram illustrating one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure;

fig. 9 is a schematic diagram illustrating one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure;

fig. 10 is a schematic diagram illustrating one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure;

Fig. 11 is a schematic diagram illustrating one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure;

fig. 12 is a schematic diagram illustrating one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure;

fig. 13 is a schematic diagram illustrating one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure;

fig. 14 is a schematic diagram illustrating one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure;

fig. 15 is a schematic diagram illustrating one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure;

fig. 16 is a schematic diagram illustrating one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure;

fig. 17 is a schematic diagram illustrating one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure;

fig. 18 is a schematic diagram illustrating one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure;

fig. 19 is a schematic diagram illustrating one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure;

Fig. 20 is a schematic diagram illustrating one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure; and

fig. 21 is a flowchart illustrating a method of supporting wireless communication network data collection according to an embodiment of the present disclosure;

fig. 22 illustrates a schematic diagram of one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure;

fig. 23 illustrates a schematic diagram of one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure;

fig. 24 illustrates a schematic diagram of one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure.

Detailed Description

The following description with reference to the accompanying drawings is provided to facilitate a thorough understanding of the various embodiments of the present disclosure as defined by the claims and their equivalents. The description includes various specific details to facilitate understanding, but is to be considered exemplary only. Accordingly, one of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.

The terms and phrases used in the specification and claims are not limited to their dictionary meanings, but are used only by the inventors to enable a clear and consistent understanding of the disclosure. It will thus be apparent to those skilled in the art that the following descriptions of the various embodiments of the present disclosure are provided for illustration only and not for the purpose of limitation.

It should be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more such surfaces.

The terms "comprises" or "comprising" may refer to the presence of a corresponding disclosed function, operation or component that may be used in various embodiments of the present disclosure, rather than to the presence of one or more additional functions, operations or features. Furthermore, the terms "comprises" or "comprising" may be interpreted as referring to certain features, numbers, steps, operations, constituent elements, components, or combinations thereof, but should not be interpreted as excluding the existence of one or more other features, numbers, steps, operations, constituent elements, components, or combinations thereof.

The term "or" as used in the various embodiments of the present disclosure includes any listed term and all combinations thereof. For example, "a or B" may include a, may include B, or may include both a and B.

The term "forwarding" as used in various embodiments of the present disclosure includes "forwarding" and "transmitting/Send".

Unless defined differently, all terms (including technical or scientific terms) used in this disclosure have the same meaning as understood by one of ordinary skill in the art to which this disclosure belongs. General terms as defined in the dictionary are to be construed to have meanings consistent with the context in the relevant technical field, and these terms should not be interpreted ideally or excessively formally unless explicitly so defined in the present disclosure.

Figures 1 through 20, discussed below, and the various embodiments used to describe the principles of the present disclosure are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will appreciate that the principles of the present disclosure may be implemented in any suitably arranged system or device.

Fig. 1 illustrates an exemplary system architecture 100 for System Architecture Evolution (SAE). A User Equipment (UE) 101 is a terminal device for receiving data. An evolved universal terrestrial radio access network (E-UTRAN) 102 is a radio access network including macro base stations (enodebs/nodebs) providing an access radio network interface for UEs. The Mobility Management Entity (MME) 103 is responsible for managing the UE's mobility context, session context and security information. Serving Gateway (SGW) 104 mainly provides the functions of the user plane, and MME 103 and SGW 104 may be in the same physical entity. The packet data network gateway (PGW) 105 is responsible for charging, lawful interception, etc. functions, and may also be in the same physical entity as the SGW 104. A Policy and Charging Rules Function (PCRF) 106 provides quality of service (QoS) policies and charging criteria. The general packet radio service support node (SGSN) 108 is a network node device in the Universal Mobile Telecommunications System (UMTS) that provides a route for the transmission of data. A Home Subscriber Server (HSS) 109 is a home subsystem of the UE and is responsible for protecting user information including the current location of the user equipment, the address of the service node, user security information, packet data context of the user equipment, etc.

Fig. 2 illustrates an exemplary system architecture 200 according to various embodiments of the present disclosure. Other embodiments of the system architecture 200 can be used without departing from the scope of this disclosure.

A User Equipment (UE) 201 is a terminal device for receiving data. The next generation radio access network (NG-RAN) 202 is a radio access network including base stations (gnbs or enbs connected to a 5G core network 5GC, also referred to as NG-gnbs) that provide access radio network interfaces for UEs. An access control and mobility management function (AMF) 203 is responsible for managing the mobility context of the UE, and security information. The User Plane Function (UPF) 204 mainly provides the functions of the user plane. The session management function entity SMF205 is responsible for session management. The Data Network (DN) 206 includes services such as operators, access to the internet, and third party traffic, among others.

The entities described in this disclosure may include: a gNB, gNB centralized Unit (gNB-CU), gNB distribution Unit (gNB Distributed Unit, gNB-DU), gNB centralized Unit Control Plane (gNB CU-CP), gNB centralized Unit User Plane (gNB CU-UP), en-gNB, eNB, ng-eNB, UE, access and mobility management function (Access and Mobility Management Function, AMF), session management function (Session Management Function, SMF), mobility management entity (Mobility Management Entity, MME) and other network entities or network logic units.

According to one aspect of an embodiment of the present disclosure, there is provided a method of supporting wireless communication network data collection, the method comprising: the first entity sends a first message including a UE model information request to the second entity to inform the second entity of the UE model information feedback requirement. After the second entity receives the first message, the UE model information needs to be reported to the first entity according to the request, so that the first entity can acquire the UE model information of the UE, and provide information for the first entity to make UE model management decisions on the UE model, thereby ensuring the effectiveness of UE model issuing and/or training and/or reasoning and reducing unnecessary model issuing and/or training and/or reasoning.

The first message may be a HANDOVER request aware (HANDOVER REQUEST ACKNOWLEDGE) message of X2 or Xn or an acquire UE context request (RETRIEVE UE CONTEXT REQUEST) message or a UE context release (UE CONTEXT RELEASE) message or a HANDOVER SUCCESS (HANDOVER SUCCESS) message; the second eNB modification request (SENB MODIFICATION REQUEST) message or second eNB modification request awareness (SENB MODIFICATION REQUEST ACKNOWLEDGE) message or second eNB modification request rejection (SENB MODIFICATION REQUEST REJECT) message or second gNB modification request (SGNB MODIFICATION REQUEST) message or second gNB modification request awareness (SGNB MODIFICATION REQUEST ACKNOWLEDGE) message or second gNB modification request rejection (SGNB MODIFICATION REQUEST REJECT) message or second eNB modification need (SENB MODIFICATION REQUIRED) message or second eNB modification acknowledgement (SENB MODIFICATION CONFIRM) message or second eNB modification rejection (SENB MODIFICATION REFUSE) message or second gNB modification need (SGNB MODIFICATION REQUIRED) message or second gNB modification acknowledgement (SGNB MODIFICATION CONFIRM) message or second gNB modification rejection (SGNB MODIFICATION REFUSE) message of X2; or an Xn secondary node modification request (S-NODE MODIFICATION REQUEST) message or a secondary node modification request awareness (S-NODE MODIFICATION REQUEST ACKNOWLEDGE) message or a secondary node modification request rejection (S-NODE MODIFICATION REQUEST REJECT) message or a secondary node modification need (S-NODE MODIFICATION REQUIRED) message or a secondary node modification acknowledgement (S-NODE MODIFICATION CONFIRM) message or a secondary node modification rejection (S-NODE MODIFICATION REFUSE) message; a second gNB change confirm (SGNB CHANGE CONFIRM) message that may also be X2; or a secondary node change acknowledgement (S-NODE CHANGE CONFIRM) message of Xn; a second eNB release request (SENB RELEASE REQUEST) message or a second eNB release acknowledgement (SENB RELEASE CONFIRM) message or a second gNB release request (SGNB RELEASE REQUEST) message or a second gNB release acknowledgement (SGNB RELEASE CONFIRM) message of X2; or an Xn secondary node release request (S-NODE RELEASE REQUEST) message or a secondary node release confirmation (S-NODE RELEASE CONFIRM) message; a second eNB reconfiguration complete (SENB RECONFIGURATION COMPLETE) message or a second gNB reconfiguration complete (SGNB RECONFIGURATION COMPLETE) message of X2; or an auxiliary node reconfiguration complete (S-NODE RECONFIGURATION COMPLETE) message of Xn; or X2 SETUP REQUEST (X2 SETUP REQUEST) message of X2 or EN-DC X2 SETUP REQUEST (EN-DC X2 SETUP REQUEST) message; an Xn SETUP REQUEST (Xn SETUP REQUEST) message of Xn is also possible; an eNB configuration update (ENB CONFIGURATION UPDATE) message or eNB configuration update aware (ENB CONFIGURATION UPDATE ACKNOWLEDGE) message or EN-DC configuration update (EN-DC CONFIGURATION UPDATE) message or EN-DC configuration update aware (EN-DC CONFIGURATION UPDATE ACKNOWLEDGE) message for X2; an NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or an NG-RAN node configuration update awareness (NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE) message of Xn is also possible; a RESET REQUEST message, which may also be X2 or Xn; a move change request (MOBILITY CHANGE REQUEST) message for X2; or a HANDOVER COMMAND (HANDOVER COMMAND) message or a HANDOVER preparation failure (HANDOVER PREPARATION FAILURE) message or a HANDOVER REQUEST awareness (HANDOVER REQUEST ACKNOWLEDGE) message or a HANDOVER notification (HANDOVER NOTIFY) message or a HANDOVER SUCCESS (HANDOVER SUCCESS) message or a path switch REQUEST (PATH SWITCH REQUEST) message or a UE context release COMMAND (UE CONTEXT RELEASE COMMAND) message; it may also be a radio resource control (Radio Resource Control, RRC) setup (RRCSetup) message or an RRC connection setup (RRCConnectionSetup) message or an RRC reconfiguration (rrcconnectionconfiguration) message or an RRC reestablishment (rrcreesctabilizent) message or an RRC connection reestablishment (RRCConnectionReestablishment) message or an RRC connection restoration (rrcresum) message or an RRC connection restoration (rrcconnectionreset) message or an RRC release with deferred configuration (RRCRelease with suspend configuration) message or a move from NR command (mobilityf rom command) message; may also be a system message such as a system message block (System Information Block), a master message block (Master Information Block), a Positioning system message block (posSIB), etc.; or a newly defined X2 message or Xn message or NG message or RRC container.

The first message includes one or more of the following:

● UE identity: and the method is used for identifying the UE where the model information to be reported is located. The identification may be one or more of the following: NG-RAN node UE XnAP ID, source NG-RAN node UE XnAP ID, M-NG-RAN node UE XnAP ID, S-NG-RAN node UE XnAP ID, meNB UE X2AP ID, seNB UE X2AP ID, meNB UE X2AP ID, sgNB UE X2AP ID, AMF UE NGAP ID, RAN UE NGAP ID, source AMF UE NGAP ID, UE-Identity, newUE-Identity.

● First entity identification: for identifying the requesting entity. The identification may be one or more of the following: cell Global ID, target Cell Global ID, requested Target Cell ID.

● Second entity identification: for identifying the entity that received the request. The identification may be one or more of the following: cell Global ID, target Cell Global ID, requested Target Cell ID, UE identity.

● And (3) interaction identification: for identifying the interaction. The identity may be an RRC interaction identity (RRC-TransactionIdentifier).

● The application range is as follows: the application scope identification and/or the identification list of the message content. Including one or more of the following: UE, qoS flow (QoS flow), qoS class (QoS level), data radio bearer (Data Radio Bearer), slice, cell, node, traffic, area, operator, etc. The identification of the slice may be single network slice selection assistance information (Single Network Slice Selection Assistance Information, S-NSSAI). The identity of the cell may be a Physical layer cell identity (Physical-layer Cell identity). The identity of the operator may be a public land mobile network (Public Land Mobile Network ID, PLMN ID). The identification of QoS class may be a mapped 5G quality of service identification (5G QoS Identifier,5QI) or quality of service class identification (QoS Class Identifier, QCI).

● Switching time: for indicating the point in time at which the UE is handed over. The time may be a relative time or an absolute time.

● UE model information reporting request identification: for representing and including a UE model information reporting request. This field may be represented in a single bit, e.g., 1 indicates that the request includes a UE model information reporting request, and 0 indicates that the request does not include a UE model information reporting request; or 1 indicates that the request does not include a UE model information reporting request, and 0 indicates that the request includes a UE model information reporting request.

● Reporting a registration request: the method is used for representing the start, the end, the new addition and the like of the UE model information report.

● Reporting time interval: for representing the time interval of reporting. May be represented by 2*n bits, for example, the first n bits representing the reporting start time and the last n bits representing the reporting end time. The time may be a relative time or an absolute time. It may also be represented by separate fields, including one or more of the following:

reporting start time: for indicating the start time of the reporting. The start time may be a relative time or an absolute time.

Reporting end time: for indicating the end time of the reporting. The end time may be a relative time or an absolute time.

● Reporting time: for indicating the point in time of the reporting. The time may be a relative time or an absolute time.

● Type of information reporting: the method is used for indicating that the model information is reported in a single time or periodically or in a condition triggering manner. Reporting types include, but are not limited to: on demand, periodic, condition triggered reporting, etc.

● Information reporting period: and the interval time is used for representing the periodic reporting of the model information. If the field content is not available, a single report is indicated.

● Reporting trigger condition configuration: and the trigger condition is used for indicating the trigger condition needing to be reported. Only when the actual situation satisfies the triggering situation, reporting is needed, such as that the number of models in an Active state and/or an Inactive state is greater than and/or less than a threshold value, a measurement report related value (reference signal received power (Reference Signal Received Power, RSRP), reference signal received quality (Reference Signal Receiving Quality, RSRQ), signal to interference plus noise ratio (Signal to Interference plus Noise Ratio, SINR), etc.) is greater than and/or less than a threshold value, accessing a slice (e.g., entering a slice identified by single network slice selection assistance information (Single Network Slice Selection Assistance Information, S-nsai), accessing a private network, accessing a network of an operator (e.g., entering an operator identified by public land mobile network (Public Land Mobile Network, PLMN), etc.), transitioning a user from an Inactive state (Active state) and/or an Idle state (Idle state) to an Active state (Active state), transitioning a user from an Active state (Active state) to an Inactive state (Idle state), transitioning a model accuracy is greater than and/or less than a non-Active state (Idle state), or not completing a model of downloading, etc.

● The content needs to be reported: for indicating what needs to be reported. The reporting content includes one or more of the following:

numbering and/or numbering list of O-models

Name of O model

Use of O model

State of the o model: for representing a current state of a model, including one or more of: an activated state, a deactivated state, etc. The model may be a model that has completed a download and/or a model that has not completed a download.

Model integrity status: for indicating whether the model has completed downloading, including one or more of the following: completed downloads, incomplete downloads, etc.

Status of model not downloaded: representing a state of the model in incomplete download, including one or more of: an activated state, a deactivated state, etc. When in an active state, indicating that a model is currently being downloaded; when in the inactive state, a suspension of downloading is indicated.

Model download address: for representing model download addresses including, but not limited to, at least one of the following information: the address and/or port and/or protocol of the server, URL address are downloaded.

Model download ratio: for representing the download progress of a model, including one or more of the following: the downloaded portion accounts for the proportion of the whole content to be downloaded, the un-downloaded portion accounts for the proportion of the whole content to be downloaded, and the like.

Suggested measure: representing suggested actions for the model, including one or more of: retention, deletion, deactivation, activation, etc., which may be a model of completed downloads and/or a model of incomplete downloads, etc. Deactivating the representation-preserving model, but without training and/or reasoning, for the downloaded model; the representation retention model is activated and training and/or reasoning continues. Deactivating the model for incomplete downloads, which means that the downloaded portion remains but does not continue to be downloaded; the activation indicates that the downloading of the non-downloaded portion is continued.

Suggested actions for model not downloaded: representing suggested actions for the model that did not download, including one or more of: hold, delete, deactivate, activate, etc. Deactivation means that the downloaded portion is retained but the download is not continued; the activation indicates that the downloading of the non-downloaded portion is continued.

Model accuracy: performance assessment results for the identification model, including one or more of: accuracy, reliability, etc.

Model activation conditions: an activation condition indicating that a certain model is activated, i.e. when the activation condition is satisfied, the model is activated. The activation condition may be entering a cell (e.g. accessing a cell identity), accessing an operator (e.g. entering an operator identified by PLMN, etc.), accessing a slice (e.g. entering a slice identified by S-NSSAI, etc.), signal strength and/or signal quality (which may be RSRP/RSRQ/SINR/RSSI, etc.) being at and/or above a certain threshold and/or being at and/or below a certain threshold, entering a geographical area, entity movement speed being above and/or below a certain threshold and/or being at and/or above a certain threshold and/or being at and/or below a certain threshold and/or being at and/or above a certain interval. The model may be a completed download model or an incomplete download model.

Model deactivation conditions: a deactivation condition indicating that a certain model is deactivated, i.e. when the deactivation condition is fulfilled, the model is deactivated. The activation condition may be entering a cell (e.g. accessing a cell identity), accessing an operator (e.g. entering an operator identified by PLMN, etc.), accessing a slice (e.g. entering a slice identified by S-NSSAI, etc.), signal strength and/or signal quality (which may be RSRP/RSRQ/SINR/RSSI, etc.) being at and/or above a certain threshold and/or being at and/or below a certain threshold, entering a geographical area, entity movement speed being above and/or below a certain threshold and/or being at and/or above a certain threshold and/or being at and/or below a certain threshold and/or being at and/or above a certain interval. The model may be a completed download model or an incomplete download model.

Model activation time: the point in time and/or period of time at which the model is activated is indicated.

Model deactivation time: indicating the point in time and/or period of time at which the model was deactivated.

O reasoning content reporting case: representing the situation that the UE reports the model reasoning content, including one or more of the following:

■ Type of reasoning content reporting: the method is used for indicating that the reasoning content is reported once or periodically or in a condition triggering manner. Reporting types include, but are not limited to: on demand, periodic, condition triggered reporting, etc.

■ Reasoning content reporting period: for representing the time interval during which the inferred content is periodically reported. If the field content is not available, a single report is indicated.

■ Reporting triggering conditions of reasoning contents: and the trigger condition is used for indicating the need of reporting the reasoning content. Only when the actual situation satisfies the trigger situation, reporting is needed, such as accessing a certain slice (e.g., accessing a certain slice identified by S-nsai, etc.), accessing a private network, accessing a certain operator (e.g., accessing a certain operator identified by PLMN, etc.), transitioning a user from an Inactive state (Active state) and/or an Idle state (Idle state) to an Active state (Active state), transitioning a user from an Active state (Active state) to an Inactive state (Active state) and/or an Idle state (Idle state), and/or a model accuracy being higher and/or lower than a threshold value, etc.

■ The reported reasoning content: and the reasoning content is used for representing the reasoning content reported by the UE. May include one or more of the following: predicted data volume, predicted location information, predicted trajectory information, predicted computational power information (e.g., hash values, units may be TOPS, TFLOPS, FLOP, GOPS, etc.), predicted energy efficiency (Energy efficiency), predicted energy, predicted quality of service information, predicted user experience information, predicted traffic type, predicted traffic information, predicted load information, predicted resource status information, predicted measurement report information, predicted operating condition information, predicted handover destination node information, etc.

■ The applicable time of the reasoning content: for representing the applicable time and/or point in time of the inferred content. The inference content can be the submitted inference content or the requested submitted inference content. The time may be a relative time or an absolute time. In the case of a time interval, this may be represented by 2*n bits, for example, the first n bits representing the start time and the last n bits representing the end time. It may also be represented by separate fields, including one or more of the following:

● Start time: for indicating the start time of the applicable time interval. The start time may be a relative time or an absolute time.

● End time: for indicating the end time of the applicable time interval. The end time may be a relative time or an absolute time.

■ Accuracy: the evaluation results for identifying the model and/or the inference content include one or more of the following: accuracy, reliability, etc.

The second entity sends a second message including the UE model information to the first entity according to the self situation and/or according to the UE model information request sent by the first entity, so that the first entity can acquire the UE model information of the UE. After the first entity receives the second message, a decision needs to be made on the model of the UE, for example, activation, deactivation, deletion, reservation, reasoning content reporting decision, etc., and the decision can be directly or indirectly notified to the UE to perform model management later, so as to ensure the effectiveness of model issuing and/or training and/or reasoning content reporting of the UE, and reduce unnecessary model issuing and/or training and/or reasoning content reporting.

The second message may be a HANDOVER REQUEST (HANDOVER REQUEST) message of X2 or Xn or a get UE context response (RETRIEVE UE CONTEXT RESPONSE) message or a get UE context failure (RETRIEVE UE CONTEXT FAILURE) message; the second eNB modification request (SENB MODIFICATION REQUEST) message or second eNB modification request awareness (SENB MODIFICATION REQUEST ACKNOWLEDGE) message or second eNB modification request rejection (SENB MODIFICATION REQUEST REJECT) message or second gNB modification request (SGNB MODIFICATION REQUEST) message or second gNB modification request awareness (SGNB MODIFICATION REQUEST ACKNOWLEDGE) message or second gNB modification request rejection (SGNB MODIFICATION REQUEST REJECT) message or second eNB modification need (SENB MODIFICATION REQUIRED) message or second eNB modification acknowledgement (SENB MODIFICATION CONFIRM) message or second eNB modification rejection (SENB MODIFICATION REFUSE) message or second gNB modification need (SGNB MODIFICATION REQUIRED) message or second gNB modification acknowledgement (SGNB MODIFICATION CONFIRM) message or second gNB modification rejection (SGNB MODIFICATION REFUSE) message of X2; or an Xn secondary node modification request (S-NODE MODIFICATION REQUEST) message or a secondary node modification request awareness (S-NODE MODIFICATION REQUEST ACKNOWLEDGE) message or a secondary node modification request rejection (S-NODE MODIFICATION REQUEST REJECT) message or a secondary node modification need (S-NODE MODIFICATION REQUIRED) message or a secondary node modification acknowledgement (S-NODE MODIFICATION CONFIRM) message or a secondary node modification rejection (S-NODE MODIFICATION REFUSE) message; a second gNB change required (SGNB CHANGE REQUIRED) message, which may also be X2; an auxiliary node change need (S-NODE CHANGE REQUIRED) message of Xn is also possible; a second gNB release request aware (SGNB RELEASE REQUEST ACKNOWLEDGE) message or a second eNB release need (SENB RELEASE REQUIRED) message or a second gNB release need (SGNB RELEASE REQUIRED) message of X2; or an Xn secondary node release request awareness (S-NODE RELEASE REQUEST ACKNOWLEDGE) message or a secondary node release need (S-NODE RELEASE REQUIRED) message; a second eNB reconfiguration complete (SENB RECONFIGURATION COMPLETE) message or a second gNB reconfiguration complete (SGNB RECONFIGURATION COMPLETE) message of X2; or an auxiliary node reconfiguration complete (S-NODE RECONFIGURATION COMPLETE) message of Xn; a HANDOVER required (HANDOVER REQUIRED) message or a HANDOVER REQUEST (HANDOVER REQUEST) message or a path switch REQUEST aware (PATH SWITCH REQUEST ACKNOWLEDGE) message or a path switch REQUEST failed (PATH SWITCH REQUEST failed) message or a UE context release REQUEST (UE CONTEXT RELEASE REQUEST) message or a UE context release complete (UE CONTEXT RELEASE COMPLETE) message or a UE information forwarding (UE INFORMATION TRANSFER) message or an initial UE context setup REQUEST (INITIAL CONTEXT SETUP REQUEST) message; or may be an RRC establishment request (RRCSetup request) message or an RRC connection request (RRCConnection request) message or an RRC establishment complete (RRCSetup complete) message or an RRC connection establishment complete (RRCConnection setup complete) message or an RRC reconfiguration complete (RRCRECONfigurationcomplete) message or an RRC connection reconfiguration complete (RRCConnection reconfigurationcomplete) message or an RRC reestablishment request (RRCReestablismentrequest) message or an RRC connection reestablishment a request (rrcconnectionresestischentrequest) message or RRC reestablishment complete (rrcrestischentcomplete) message or RRC connection reestablishment complete (rrcconnectionresestischentcomplete) message or RRC restoration request (rrcrescendrequest or rrcrescendrequest 1) message or RRC connection restoration request (rrcconnectionresequence request) message or RRC restoration complete (rrcrescenecomplete) message or RRC connection restoration complete (rrcconnectionresescents) message; or a newly defined X2 or Xn or NG message or RRC container.

The second message includes one or more of the following:

● UE identity: and the UE is used for identifying the reported model information. The identification may be one or more of the following: NG-RAN node UE XnAP ID, source NG-RAN node UE XnAP ID, M-NG-RAN node UE XnAP ID, S-NG-RAN node UE XnAP ID, meNB UE X2AP ID, seNB UE X2AP ID, meNB UE X2AP ID, sgNB UE X2AP ID, AMF UE NGAP ID, RAN UE NGAP ID, source AMF UE NGAP ID, UE-Identity, newUE-Identity.

● First entity identification: for identifying the first entity. The identification may be one or more of the following: cell Global ID, target Cell Global ID, requested Target Cell ID.

● Second entity identification: for identifying the second entity. The identification may be one or more of the following: cell Global ID, target Cell Global ID, requested Target Cell ID, UE identity.

● The requested content may report an acknowledgement: a single bit may be used to indicate whether reporting is possible, e.g., a 1 bit indicates that all requested content can be reported, and a 0 bit indicates that requested content cannot be reported; or request content confirmation one by one, for example, in the form of a bitmap (bitmap), where each bit corresponds to one request content, for example, when the bit is 1, it indicates that the corresponding request content can be sent, and 0 indicates that the corresponding request content cannot be sent; separate fields may also be used to represent different confirmation of the content of the request for reporting.

● The content of the model information: for indicating the reported content of the model information. The model information content includes one or more of the following:

numbering and/or numbering list of O-models

Name of O model

Use of O model

Model integrity status: for indicating whether the model has completed downloading, including one or more of the following: completed, incomplete downloads, etc.

Model download ratio: for indicating download progress, including one or more of: the downloaded portion accounts for the proportion of the whole content to be downloaded, the un-downloaded portion accounts for the proportion of the whole content to be downloaded, and the like.

Model activation conditions: representing configured activation conditions for activating a model, i.e. activating the model when the activation conditions are met. The activation condition may be entering a cell (e.g. accessing a cell identity), accessing an operator (e.g. entering an operator identified by PLMN, etc.), accessing a slice (e.g. entering a slice identified by S-NSSAI, etc.), signal strength and/or signal quality (which may be RSRP/RSRQ/SINR/RSSI, etc.) being at and/or above a certain threshold and/or being at and/or below a certain threshold, entering a geographical area, entity movement speed being above and/or below a certain threshold and/or being at and/or above a certain threshold and/or being at and/or below a certain threshold and/or being at and/or above a certain interval. The model may be a completed download model or an incomplete download model.

Model deactivation conditions: the deactivation condition indicating that a model is configured to be deactivated, i.e., when the deactivation condition is satisfied, the model is deactivated. The activation condition may be entering a cell (e.g. accessing a cell identity), accessing an operator (e.g. entering an operator identified by PLMN, etc.), accessing a slice (e.g. entering a slice identified by S-NSSAI, etc.), signal strength and/or signal quality (which may be RSRP/RSRQ/SINR/RSSI, etc.) being at and/or above a certain threshold and/or being at and/or below a certain threshold, entering a geographical area, entity movement speed being above and/or below a certain threshold and/or being at and/or above a certain threshold and/or being at and/or below a certain threshold and/or being at and/or above a certain interval. The model may be a completed download model or an incomplete download model.

■ Reporting triggering conditions of reasoning contents: and the trigger condition is used for indicating the need of reporting the reasoning content. Only when the actual situation satisfies the trigger situation, reporting is needed, such as accessing a certain slice (e.g., accessing a certain slice identified by S-nsai, etc.), accessing a private network, accessing a certain operator (e.g., accessing a certain operator identified by PLMN, etc.), transitioning a user from an Inactive state (Active state) and/or an Idle state (Idle state) to an Active state (Active state), transitioning a user from an Active state (Active state) to an Inactive state (Active state) and/or an Idle state (Idle state), and when the model accuracy is higher and/or lower than a threshold value.

■ The reported reasoning content: and the reasoning content is used for representing the reasoning content reported by the UE. May include one or more of the following: predicted data volume, predicted location information, predicted trajectory information, predicted computational power information (e.g., hash values, units may be TOPS, TFLOPS, FLOP, GOPS, etc.), predicted energy efficiency, predicted energy, predicted quality of service information, predicted user experience information, predicted traffic type, predicted traffic information, predicted load information, predicted resource status information, predicted measurement report information, predicted operating condition information, predicted handover destination node information, etc.

■ The applicable time of the reported reasoning content: for indicating the applicable time and/or point in time of the content of the inference being reported. The time may be a relative time or an absolute time. In the case of a time interval, this may be represented by 2*n bits, for example, the first n bits representing the start time and the last n bits representing the end time. It may also be represented by separate fields, including one or more of the following:

● Triggering conditions: for indicating the triggering situation of this report, such as that the number of Active state models and/or Inactive state models is greater than and/or less than a threshold, that the measurement report related value (RSRP, RSRQ, SINR, etc.) is greater than and/or less than a threshold, that a slice is accessed (e.g., a slice identified by S-nsai is accessed), that a private network is accessed, that an operator is accessed (e.g., an operator identified by PLMN is accessed, etc.) is accessed, that the user is transitioned from Inactive state (Active state) and/or Idle state (Idle state) to Active state (Active state), that the user is transitioned from Active state (Active state) to Inactive state (Inactive state) and/or Idle state (Idle state), that the model accuracy is higher and/or lower than the threshold, that there is an unfinished downloaded model, etc.

If the second entity cannot feed back the UE model information result to the first entity according to the UE model information request sent by the first entity, the second entity sends a third message including failure in reporting or failure in reporting to the first entity, so that the first entity knows that the second entity cannot report according to the request.

The third message may be a HANDOVER REQUEST (HANDOVER REQUEST) message of X2 or Xn or a get UE context response (RETRIEVE UE CONTEXT RESPONSE) message or a get UE context failure (RETRIEVE UE CONTEXT FAILURE) message; the second eNB modification request (SENB MODIFICATION REQUEST) message or second eNB modification request awareness (SENB MODIFICATION REQUEST ACKNOWLEDGE) message or second eNB modification request rejection (SENB MODIFICATION REQUEST REJECT) message or second gNB modification request (SGNB MODIFICATION REQUEST) message or second gNB modification request awareness (SGNB MODIFICATION REQUEST ACKNOWLEDGE) message or second gNB modification request rejection (SGNB MODIFICATION REQUEST REJECT) message or second eNB modification need (SENB MODIFICATION REQUIRED) message or second eNB modification acknowledgement (SENB MODIFICATION CONFIRM) message or second eNB modification rejection (SENB MODIFICATION REFUSE) message or second gNB modification need (SGNB MODIFICATION REQUIRED) message or second gNB modification acknowledgement (SGNB MODIFICATION CONFIRM) message or second gNB modification rejection (SGNB MODIFICATION REFUSE) message of X2; or an Xn secondary node modification request (S-NODE MODIFICATION REQUEST) message or a secondary node modification request awareness (S-NODE MODIFICATION REQUEST ACKNOWLEDGE) message or a secondary node modification request rejection (S-NODE MODIFICATION REQUEST REJECT) message or a secondary node modification need (S-NODE MODIFICATION REQUIRED) message or a secondary node modification acknowledgement (S-NODE MODIFICATION CONFIRM) message or a secondary node modification rejection (S-NODE MODIFICATION REFUSE) message; a second gNB change required (SGNB CHANGE REQUIRED) message, which may also be X2; an auxiliary node change need (S-NODE CHANGE REQUIRED) message of Xn is also possible; a second gNB release request aware (SGNB RELEASE REQUEST ACKNOWLEDGE) message or a second eNB release need (SENB RELEASE REQUIRED) message or a second gNB release need (SGNB RELEASE REQUIRED) message of X2; or an Xn secondary node release request awareness (S-NODE RELEASE REQUEST ACKNOWLEDGE) message or a secondary node release need (S-NODE RELEASE REQUIRED) message; a second eNB reconfiguration complete (SENB RECONFIGURATION COMPLETE) message or a second gNB reconfiguration complete (SGNB RECONFIGURATION COMPLETE) message of X2; or an auxiliary node reconfiguration complete (S-NODE RECONFIGURATION COMPLETE) message of Xn; a HANDOVER required (HANDOVER REQUIRED) message or a HANDOVER REQUEST (HANDOVER REQUEST) message or a path switch REQUEST aware (PATH SWITCH REQUEST ACKNOWLEDGE) message or a path switch REQUEST failed (PATH SWITCH REQUEST failed) message or a UE context release REQUEST (UE CONTEXT RELEASE REQUEST) message or a UE context release complete (UE CONTEXT RELEASE COMPLETE) message or a UE information forwarding (UE INFORMATION TRANSFER) message or an initial UE context setup REQUEST (INITIAL CONTEXT SETUP REQUEST) message; or may be an RRC establishment request (RRCSetup request) message or an RRC connection request (RRCConnection request) message or an RRC establishment complete (RRCSetup complete) message or an RRC connection establishment complete (RRCConnection setup complete) message or an RRC reconfiguration complete (RRCRECONfigurationcomplete) message or an RRC connection reconfiguration complete (RRCConnection reconfigurationcomplete) message or an RRC reestablishment request (RRCReestablismentrequest) message or an RRC connection reestablishment a request (rrcconnectionresestischentrequest) message or RRC reestablishment complete (rrcrestischentcomplete) message or RRC connection reestablishment complete (rrcconnectionresestischentcomplete) message or RRC restoration request (rrcrescendrequest or rrcrescendrequest 1) message or RRC connection restoration request (rrcconnectionresequence request) message or RRC restoration complete (rrcrescenecomplete) message or RRC connection restoration complete (rrcconnectionresescents) message; or a newly defined X2 message or Xn message or NG message or RRC container.

The third message includes one or more of the following:

● The application range is as follows: the application scope identification and/or the identification list of the message content. Including one or more of the following: UE, qoS flow (QoS flow), qoS class (QoS level), data radio bearer (Data Radio Bearer), slice, cell, node, traffic, area, operator, etc. The identification of the slice may be single network slice selection assistance information (Single Network Slice Selection Assistance Information, S-NSSAI). The identity of the cell may be a Physical layer cell identity (Physical-layer Cell identity). The identity of the operator may be a public land mobile network (Public Land Mobile Network ID, PLMN ID). The identification of QoS class may be a mapped 5G quality of service identification (5G QoSIdentifier,5QI) or quality of service class identification (QoS Class Identifier, QCI).

● The reason is that: for indicating the reason for the failure of the request, e.g. no report content requested, no model, etc.

According to another aspect of an embodiment of the present disclosure, there is provided a method of supporting wireless communication network data collection, the method comprising: the second entity sends a fourth message comprising the UE model management decision to the first entity, and the UE model management decision of the second entity is directly or indirectly notified to the UE, so that the effectiveness of model issuing and/or training and/or reasoning content reporting of the UE is ensured, and unnecessary model training and/or reasoning is reduced. The UE model management decision comprises a model management decision and/or an reasoning content reporting decision and the like.

The fourth message may be a HANDOVER request aware (HANDOVER REQUEST ACKNOWLEDGE) message of X2 or Xn or a get UE context request (RETRIEVE UE CONTEXT REQUEST) message or a UE context release (UE CONTEXT RELEASE) message or a HANDOVER SUCCESS (HANDOVER SUCCESS) message; a second eNB modification request (SENB MODIFICATION REQUEST) message or a second gNB modification request (SGNB MODIFICATION REQUEST) message or a second eNB modification need (SENB MODIFICATION REQUIRED) message or a second gNB modification need (SGNB MODIFICATION REQUIRED) message of X2; or an Xn secondary node modification request (S-NODE MODIFICATION REQUEST) message or a secondary node modification need (S-NODE MODIFICATION REQUIRED) message; a second gNB change confirm (SGNB CHANGE CONFIRM) message that may also be X2; or a secondary node change acknowledgement (S-NODE CHANGE CONFIRM) message of Xn; a second eNB release request (SENB RELEASE REQUEST) message or a second eNB release acknowledgement (SENB RELEASE CONFIRM) message or a second gNB release request (SGNB RELEASE REQUEST) message or a second gNB release acknowledgement (SGNB RELEASE CONFIRM) message of X2; or an Xn secondary node release request (S-NODE RELEASE REQUEST) message or a secondary node release confirmation (S-NODE RELEASE CONFIRM) message; a second eNB reconfiguration complete (SENB RECONFIGURATION COMPLETE) message or a second gNB reconfiguration complete (SGNB RECONFIGURATION COMPLETE) message of X2; or an auxiliary node reconfiguration complete (S-NODE RECONFIGURATION COMPLETE) message of Xn; or X2 SETUP REQUEST (X2 SETUP REQUEST) message of X2 or EN-DC X2 SETUP REQUEST (EN-DC X2 SETUP REQUEST) message; an Xn SETUP REQUEST (Xn SETUP REQUEST) message of Xn is also possible; an eNB configuration update (ENB CONFIGURATION UPDATE) message or eNB configuration update aware (ENB CONFIGURATION UPDATE ACKNOWLEDGE) message or EN-DC configuration update (EN-DC CONFIGURATION UPDATE) message or EN-DC configuration update aware (EN-DC CONFIGURATION UPDATE ACKNOWLEDGE) message for X2; an NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or an NG-RAN node configuration update awareness (NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE) message of Xn is also possible; a RESET REQUEST message, which may also be X2 or Xn; a move change request (MOBILITY CHANGE REQUEST) message for X2; or a HANDOVER COMMAND (HANDOVER COMMAND) message or a HANDOVER preparation failure (HANDOVER PREPARATION FAILURE) message or a HANDOVER REQUEST awareness (HANDOVER REQUEST ACKNOWLEDGE) message or a HANDOVER notification (HANDOVER NOTIFY) message or a HANDOVER SUCCESS (HANDOVER SUCCESS) message or a path switch REQUEST (PATH SWITCH REQUEST) message of NG; it may also be an RRC setup (RRCSetup) message or an RRC connection setup (RRCConnectionSetup) message or an RRC connection reconfiguration (rrcconnectionconfiguration) message or an RRC reestablishment (rrcreescitabliment) message or an RRC connection reestablishment (RRCConnectionReestablishment) message or an RRC restoration (rrcresseme) message or an RRC connection restoration (RRCConnectionResume) message or an RRC release with deferred configuration (RRCRelease with suspend configuration) message or a move from NR command (mobilityf rom command) message; may also be a system message such as a system message block (System Information Block), a master message block (Master Information Block), a Positioning system message block (posSIB), etc.; or a newly defined X2 message or Xn message or NG message or RRC container.

The fourth message includes one or more of the following:

● First entity identification: for identifying the first entity. The identification may be one or more of the following: cell Global ID, target Cell Global ID, requested Target Cell ID, UE identity.

● Second entity identification: for identifying the second entity. The identification may be one or more of the following: cell Global ID, target Cell Global ID, requested Target Cell ID.

● Model management decision: for indicating model management decisions. The model management decisions include one or more of the following:

numbering and/or numbering list of O-models

Name of O model

Use of O model

Decision for model: for representing decisions for the model, including one or more of: hold, delete, deactivate, activate, etc. The model may be a model that has completed a download and/or a model that has not completed a download, etc. Deactivating the representation-preserving model, but without training and/or reasoning, for the downloaded model; the representation retention model is activated and training and/or reasoning continues. Deactivating the model for incomplete downloads, which means that the downloaded portion remains but does not continue to be downloaded; the activation indicates that the downloading of the non-downloaded portion is continued.

Decision for model not downloaded yet: a decision for representing a model for incomplete downloads, comprising one or more of: hold, delete, deactivate, activate, etc. Deactivation means that the downloaded portion is retained but the download is not continued; the activation indicates that the downloading of the non-downloaded portion is continued.

List of models activated: the list of models that can be activated can be represented by the number of the model, the name of the model, the purpose of the model, and the like.

Activation model indication: the model is instructed to be activated, i.e. it can be trained and/or inferred.

The deactivation model indicates: indicating that the model is deactivated, i.e., the model remains, but training and/or reasoning is not performed, or that the model is deleted.

Model activation conditions: indicating that the model is activated when the activation condition is satisfied. The activation condition may be entering a cell (e.g. accessing a cell identity), accessing an operator (e.g. entering an operator identified by PLMN, etc.), accessing a slice (e.g. entering a slice identified by S-NSSAI, etc.), signal strength and/or signal quality (which may be RSRP/RSRQ/SINR/RSSI, etc.) being at and/or above a certain threshold and/or being at and/or below a certain threshold, entering a geographical area, entity movement speed being above and/or below a certain threshold and/or being at and/or above a certain threshold and/or being at and/or below a certain threshold and/or being at and/or above a certain interval. The model may be a completed download model or an incomplete download model.

Model deactivation conditions: indicating that the model is activated when the deactivation condition is satisfied. The activation condition may be entering a cell (e.g. accessing a cell identity), accessing an operator (e.g. entering an operator identified by PLMN, etc.), accessing a slice (e.g. entering a slice identified by S-NSSAI, etc.), signal strength and/or signal quality (which may be RSRP/RSRQ/SINR/RSSI, etc.) being at and/or above a certain threshold and/or being at and/or below a certain threshold, entering a geographical area, entity movement speed being above and/or below a certain threshold and/or being at and/or above a certain threshold and/or being at and/or below a certain threshold and/or being at and/or above a certain interval. The model may be a completed download model or an incomplete download model.

Forwarding policy applicable to the model that has completed downloading: including one or more of the following: model forwarding is required, model forwarding is not required, etc. Wherein model forwarding includes one or more of: partial model forwarding, full model forwarding, etc.

Model forwarding policy applicable to model that did not complete the download: including one or more of the following: model forwarding is required, model forwarding is not required, etc. Wherein model forwarding includes one or more of: partial model forwarding, full model forwarding, etc.

Model forward ratio: a scale for representing model forwarding, comprising one or more of: partial model forwarding (< 100%), full model forwarding (100%), remaining model forwarding, etc. Wherein the remaining model forwarding represents forwarding the un-downloaded portion; where partial model forwarding may represent a percentage of statistics back from a beginning portion or a percentage of statistics back from an ending portion. The model may include one or more of the following: a model that has completed downloading and/or a model that has not completed downloading, etc.

O reasoning content reporting decisions: decisions representing the reporting of the UE model reasoning content include one or more of:

■ Requesting the reported reasoning content: for representing the content of the inference requesting the reporting. May include one or more of the following: predicted data volume, predicted location information, predicted trajectory information, predicted computational power information (e.g., hash values, units may be TOPS, TFLOPS, FLOP, GOPS, etc.), predicted energy efficiency, predicted energy, predicted quality of service information, predicted user experience information, predicted traffic type, predicted traffic information, predicted load information, predicted resource status information, predicted measurement report information, predicted operating condition information, predicted handover destination node information, etc.

■ The applicable time of the reasoning content requested to be reported: for indicating the applicable time and/or point in time of the requested reporting of the inferred content. The time may be a relative time or an absolute time. In the case of a time interval, this may be represented by 2*n bits, for example, the first n bits representing the start time and the last n bits representing the end time. It may also be represented by separate fields, including one or more of the following:

● Start time: for indicating the start time of the applicable time interval.

The start time may be a relative time or an absolute time.

After the first entity receives the fourth message, it forwards or applies the model management decision. If the first entity is a UE, the UE applies the UE model management decision, and if the first entity is not a UE, the first entity forwards the UE model management decision to other entities, indirectly informing the UE of the UE model management decision.

According to another aspect of an embodiment of the present disclosure, there is provided a method of supporting wireless communication network data collection, the method comprising: the first entity sends a fifth message to the second entity including a model forwarding request to inform the second entity of the model forwarding requirement. After receiving the fifth message, the second entity needs to report the model to the first entity according to the model forwarding request, so that the first entity can acquire the model to ensure the performance of the subsequent network and/or the UE.

The fifth message may be a HANDOVER request aware (HANDOVER REQUEST ACKNOWLEDGE) message of X2 or Xn or a get UE context request (RETRIEVE UE CONTEXT REQUEST) message or a UE context release (UE CONTEXT RELEASE) message or a HANDOVER SUCCESS (HANDOVER SUCCESS) message; a second eNB modification request (SENB MODIFICATION REQUEST) message or a second gNB modification request (SGNB MODIFICATION REQUEST) message or a second eNB modification need (SENB MODIFICATION REQUIRED) message or a second gNB modification need (SGNB MODIFICATION REQUIRED) message of X2; or an Xn secondary node modification request (S-NODE MODIFICATION REQUEST) message or a secondary node modification need (S-NODE MODIFICATION REQUIRED) message; a second gNB change confirm (SGNB CHANGE CONFIRM) message that may also be X2; or a secondary node change acknowledgement (S-NODE CHANGE CONFIRM) message of Xn; a second eNB release request (SENB RELEASE REQUEST) message or a second eNB release acknowledgement (SENB RELEASE CONFIRM) message or a second gNB release request (SGNB RELEASE REQUEST) message or a second gNB release acknowledgement (SGNB RELEASE CONFIRM) message of X2; or an Xn secondary node release request (S-NODE RELEASE REQUEST) message or a secondary node release confirmation (S-NODE RELEASE CONFIRM) message; a second eNB reconfiguration complete (SENB RECONFIGURATION COMPLETE) message or a second gNB reconfiguration complete (SGNB RECONFIGURATION COMPLETE) message of X2; or an auxiliary node reconfiguration complete (S-NODE RECONFIGURATION COMPLETE) message of Xn; or X2 SETUP REQUEST (X2 SETUP REQUEST) message of X2 or EN-DC X2 SETUP REQUEST (EN-DC X2 SETUP REQUEST) message; an Xn SETUP REQUEST (Xn SETUP REQUEST) message of Xn is also possible; an eNB configuration update (ENB CONFIGURATION UPDATE) message or eNB configuration update aware (ENB CONFIGURATION UPDATE ACKNOWLEDGE) message or EN-DC configuration update (EN-DC CONFIGURATION UPDATE) message or EN-DC configuration update aware (EN-DC CONFIGURATION UPDATE ACKNOWLEDGE) message for X2; an NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or an NG-RAN node configuration update awareness (NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE) message of Xn is also possible; a RESET REQUEST message, which may also be X2 or Xn; a move change request (MOBILITY CHANGE REQUEST) message for X2; or a HANDOVER COMMAND (HANDOVER COMMAND) message or a HANDOVER preparation failure (HANDOVER PREPARATION FAILURE) message or a HANDOVER REQUEST awareness (HANDOVER REQUEST ACKNOWLEDGE) message or a HANDOVER notification (HANDOVER NOTIFY) message or a HANDOVER SUCCESS (HANDOVER SUCCESS) message or a path switch REQUEST (PATH SWITCH REQUEST) message or a UE context release COMMAND (UE CONTEXT RELEASE COMMAND) message; but also a RESET message of F1 or a F1 SETUP REQUEST (F1 SETUP REQUEST) message or a GNB-DU configuration update (GNB-DU CONFIGURATION UPDATE) message or a GNB-CU configuration update (GNB-CU CONFIGURATION UPDATE) message or a UE context release command (UE CONTEXT RELEASE COMMAND) message or a UE context modification REQUEST (UE CONTEXT MODIFICATION REQUEST) message or a UE context modification need (UE CONTEXT MODIFICATION REQUIRED) message; it may also be a RESET message of E1 or a GNB-CU-UP E1 SETUP REQUEST (GNB-CU-UP E1 SETUP REQUEST) message or a GNB-CU-CP E1 SETUP REQUEST (GNB-CU-CP E1 SETUP REQUEST) message or a GNB-CU-UP configuration update (GNB-CU-UP CONFIGURATION UPDATE) message or a GNB-CU-CP configuration update (GNB-CU-CP CONFIGURATION UPDATE) message; or an E1 RELEASE REQUEST (E1 RELEASE REQUEST) message or a bearer context setup REQUEST (BEARER CONTEXT SETUP REQUEST) message or a bearer context modification REQUEST (BEARER CONTEXT MODIFICATION REQUEST) message or a bearer context modification required (BEARER CONTEXT MODIFICATION REQUIRED) message or a bearer context RELEASE command (BEARER CONTEXT RELEASE COMMAND) message; or a newly defined X2 message or Xn message or NG message or F1 message or E1 message.

The fifth message includes one or more of the following:

● Second entity identification: for identifying the entity that received the request. The identification may be one or more of the following: cell Global ID, target Cell Global ID, requested Target Cell ID.

● Model forwarding request identification: for representing including model forwarding requests. This field may be represented in a single bit, e.g., 1 indicates that the request includes a model forwarding request, and 0 indicates that the request does not include a model forwarding request; or 1 indicates that the request does not include a model forwarding request, and 0 indicates that the request includes a model forwarding request.

● The model forwards the registration request: for indicating the start, end, new addition, etc. of model forwarding.

● Model forwarding time interval: for representing the time interval of model forwarding. The model forwarding start time may be represented by 2*n bits, for example, the first n bits represent model forwarding end time, and the last n bits represent model forwarding end time, which may be a relative time or an absolute time. It may also be represented by a separate field, the model forwarding time interval comprising one or more of the following:

model forward start time: for representing the start time of the model forwarding. The start time may be a relative time or an absolute time.

Model forwarding end time: for representing the end time of the model forwarding. The end time may be a relative time or an absolute time.

● Model forwarding time: for representing the point in time of model forwarding. The time may be a relative time or an absolute time.

● Model forwarding ratio: a scale for representing model forwarding, comprising one or more of: partial model forwarding (< 100%), full model forwarding (100%), remaining model forwarding, etc. Wherein the remaining model forwarding represents forwarding the un-downloaded portion; where partial model forwarding may represent a percentage of statistics back from a beginning portion or a percentage of statistics back from an ending portion.

● Model forwarding type: for indicating that the model forwarding is single forwarding or triggered forwarding. Reporting types include, but are not limited to: on demand, condition triggered reporting, etc.

● Model forwarding trigger configuration: for indicating a trigger condition requiring model forwarding. Only when the actual situation satisfies the trigger situation, reporting is needed, such as accessing a certain slice (e.g., accessing a certain slice identified by S-nsai, etc.), accessing a private network, accessing a certain operator (e.g., accessing a certain operator identified by PLMN, etc.), transitioning a user from an Inactive state (Active state) and/or an Idle state (Idle state) to an Active state (Active state), transitioning a user from an Active state (Active state) to an Inactive state (Active state) and/or an Idle state (Idle state), having a model accuracy above and/or below a threshold, having a model being distributed and/or being downloaded, etc.

● Model download address: for representing model download addresses including, but not limited to, at least one of the following information: the address and/or port and/or protocol of the server, URL address are downloaded.

● Model download ratio: for indicating download progress, including one or more of: the downloaded portion accounts for the proportion of the whole content to be downloaded, the un-downloaded portion accounts for the proportion of the whole content to be downloaded, and the like.

● The content needs to be forwarded: for indicating the content that needs to be forwarded. Forwarding the content includes one or more of:

numbering and/or numbering list of O-models

Name of O model

Use of O model

State of the o model: for representing a current state of a model, including one or more of: an activated state, a deactivated state, etc. When in an active state, indicating that a model is currently being downloaded; when in the inactive state, a suspension of downloading is indicated.

Type of o model: model types for representing machine learning, which may include, but are not limited to: perceptron, feedforward neural network, radial basis function network, depth feedforward network, cyclic neural network, long/short term memory network, gated cyclic unit, automatic encoder, variation automatic encoder, denoising automatic encoder, sparse automatic encoder, markov chain, hopt network, boltzmann machine, constrained boltzmann machine, depth belief network, depth convolution network, deconvolution neural network, depth convolution inverse graph network, generation countermeasure network, liquid machine, extreme learning machine, echo state network, depth residual network, kohonen network, support vector machine, neural graph machine, convolution neural network, artificial neural network, cyclic neural network, depth neural network, etc.;

Characteristic parameters of the o model: including but not limited to at least one of the following:

■ The number of layers is used for representing the number of layers of the neural network;

■ The number of the neurons of each layer is used for representing the number of the neurons of each layer of the neural network;

■ Weights for representing weights of neurons and/or neuron connections of the neural network;

■ A bias for representing a bias of the neural network neurons and/or the neuron connections;

■ The direction is used for representing the direction of the neural network connection;

■ Activating a function;

■ The layer type is used for representing the type of the neural network layer, and comprises an input layer, a hidden layer, an output layer and the like.

Input parameter type of O model

Input parameter defining condition of o model: including but not limited to time, precision, etc.

Output parameter type of O model

Input parameter pretreatment method of O model: may include, but is not limited to, a preprocessing matrix, and the like.

Output parameter post-processing method of O model: may include, but is not limited to, post-processing matrices, and the like.

Time of application of the o model reasoning content: for representing the applicable time and/or point in time of the model inference content. The time may be a relative time or an absolute time. In the case of a time interval, this may be represented by 2*n bits, for example, the first n bits representing the start time and the last n bits representing the end time. It may also be represented by separate fields, including one or more of the following:

■ Start time: for indicating the start time of the applicable time interval. The start time may be a relative time or an absolute time.

■ End time: for indicating the end time of the applicable time interval. The end time may be a relative time or an absolute time.

The second entity transmits a sixth message comprising the model to the first entity according to the self situation and/or according to the model forwarding request transmitted by the first entity, so that the first entity can acquire the UE model to ensure the performance of the subsequent network and/or the UE.

The sixth message may be a HANDOVER REQUEST (HANDOVER REQUEST) message of X2 or Xn or a get UE context response (RETRIEVE UE CONTEXT RESPONSE) message or a get UE context failure (RETRIEVE UE CONTEXT FAILURE) message; the second eNB modification request (SENB MODIFICATION REQUEST) message or second eNB modification request awareness (SENB MODIFICATION REQUEST ACKNOWLEDGE) message or second eNB modification request rejection (SENB MODIFICATION REQUEST REJECT) message or second gNB modification request (SGNB MODIFICATION REQUEST) message or second gNB modification request awareness (SGNB MODIFICATION REQUEST ACKNOWLEDGE) message or second gNB modification request rejection (SGNB MODIFICATION REQUEST REJECT) message or second eNB modification need (SENB MODIFICATION REQUIRED) message or second eNB modification acknowledgement (SENB MODIFICATION CONFIRM) message or second eNB modification rejection (SENB MODIFICATION REFUSE) message or second gNB modification need (SGNB MODIFICATION REQUIRED) message or second gNB modification acknowledgement (SGNB MODIFICATION CONFIRM) message or second gNB modification rejection (SGNB MODIFICATION REFUSE) message of X2; or an Xn secondary node modification request (S-NODE MODIFICATION REQUEST) message or a secondary node modification request awareness (S-NODE MODIFICATION REQUEST ACKNOWLEDGE) message or a secondary node modification request rejection (S-NODE MODIFICATION REQUEST REJECT) message or a secondary node modification need (S-NODE MODIFICATION REQUIRED) message or a secondary node modification acknowledgement (S-NODE MODIFICATION CONFIRM) message or a secondary node modification rejection (S-NODE MODIFICATION REFUSE) message; a second gNB change required (SGNB CHANGE REQUIRED) message, which may also be X2; an auxiliary node change need (S-NODE CHANGE REQUIRED) message of Xn is also possible; a second gNB release request aware (SGNB RELEASE REQUEST ACKNOWLEDGE) message or a second eNB release need (SENB RELEASE REQUIRED) message or a second gNB release need (SGNB RELEASE REQUIRED) message of X2; or an Xn secondary node release request awareness (S-NODE RELEASE REQUEST ACKNOWLEDGE) message or a secondary node release need (S-NODE RELEASE REQUIRED) message; a second eNB reconfiguration complete (SENB RECONFIGURATION COMPLETE) message or a second gNB reconfiguration complete (SGNB RECONFIGURATION COMPLETE) message of X2; or an auxiliary node reconfiguration complete (S-NODE RECONFIGURATION COMPLETE) message of Xn; a HANDOVER required (HANDOVER REQUIRED) message or a HANDOVER REQUEST (HANDOVER REQUEST) message or a path switch REQUEST aware (PATH SWITCH REQUEST ACKNOWLEDGE) message or a path switch REQUEST failed (PATH SWITCH REQUEST failed) message or a UE context release REQUEST (UE CONTEXT RELEASE REQUEST) message or a UE context release complete (UE CONTEXT RELEASE COMPLETE) message or a UE information forwarding (UE INFORMATION TRANSFER) message or an initial UE context setup REQUEST (INITIAL CONTEXT SETUP REQUEST) message; it may also be a reset aware (RESET ACKNOWLEDGE) message of F1 or a F1 SETUP RESPONSE (F1 SETUP RESPONSE) message or a GNB-DU configuration update aware (GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-CU configuration update aware (GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE) message or a UE context SETUP request (UE CONTEXT SETUP REQUEST) message or a UE context release request (UE CONTEXT RELEASE REQUEST) message or a UE context release complete (UE CONTEXT RELEASE COMPLETE) message or a UE context modification RESPONSE (UE CONTEXT MODIFICATION RESPONSE) message or a UE context modification acknowledgement (UE CONTEXT MODIFICATION CONFIRM) message or a UE inactivity notification (UE INACTIVITY NOTIFICATION) message; but also a reset aware (RESET ACKNOWLEDGE) message of E1 or a GNB-CU-UP E1 SETUP RESPONSE (GNB-CU-UP E1 SETUP RESPONSE) message or a GNB-CU-CP E1 SETUP RESPONSE (GNB-CU-CP E1 SETUP RESPONSE) message or a GNB-CU-UP configuration update aware (GNB-CU-UP CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-CU-CP configuration update aware (GNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE) message or an E1 RELEASE RESPONSE (E1 RELEASE RESPONSE) message or a bearer context SETUP RESPONSE (BEARER CONTEXT SETUP RESPONSE) message or a bearer context modification acknowledgement (BEARER CONTEXT MODIFICATION RESPONSE) message or a bearer context modification acknowledgement (BEARER CONTEXT MODIFICATION CONFIRM) message or a bearer context RELEASE complete (BEARER CONTEXT RELEASE COMPLETE) message or a bearer context RELEASE request (BEARER CONTEXT RELEASE REQUEST) message or a bearer context inactivity notification (BEARER CONTEXT INACTIVITY NOTIFICATION) message; or a newly defined X2 message or Xn message or NG message or F1 message or E1 message.

The sixth message includes one or more of the following:

● UE identity: and the method is used for identifying the UE where the model information to be reported is located and/or applicable. The identification may be one or more of the following: NG-RAN node UE XnAP ID, source NG-RAN node UE XnAP ID, M-NG-RAN node UE XnAP ID, S-NG-RAN node UE XnAP ID, meNB UE X2AP ID, seNB UE X2AP ID, meNB UE X2AP ID, sgNB UE X2AP ID, AMF UE NGAP ID, RAN UE NGAP ID, source AMF UE NGAP ID, UE-Identity, newUE-Identity.

● The requested content may forward an acknowledgement: a single bit may be used to indicate whether forwarding is possible, e.g., a bit of 1 indicates that all requested content may be forwarded, and a bit of 0 indicates that requested content may not be forwarded; or request content confirmation one by one, for example, in the form of a bitmap (bitmap), each bit corresponds to one request content, for example, when the bit is 1, it indicates that the corresponding forwarding request content can be sent, and 0 indicates that the corresponding forwarding request content cannot be sent; separate fields may also be used to represent different forwarding request content acknowledgements.

● Forwarding content: for indicating the content that needs to be forwarded. Forwarding the content includes one or more of:

numbering and/or numbering list of O-models

Name of O model

Use of O model

■ Activating a function;

Input parameter type of O model

Output parameter type of O model

● Model forwarding trigger condition: for indicating the triggering situation of the forwarding of the secondary model, such as accessing a certain slice (e.g. entering a certain slice identified by S-nsai, etc.), accessing a private network, accessing a certain operator (e.g. entering a certain operator identified by PLMN, etc.) network, transitioning a user from Inactive state (Active state) and/or Idle state (Idle state) to Active state (Active state), transitioning a user from Active state (Active state) to Inactive state (Active state) and/or Idle state (Idle state), having a model accuracy above and/or below a threshold value, having a model being distributed and/or a model being downloaded, etc.

● Issuing: for indicating what needs to be delivered. The delivery includes one or more of the following:

numbering and/or numbering list of O-models

Name of O model

Use of O model

■ Activating a function;

Input parameter type of O model

Output parameter type of O model

The forwarding content and/or the delivering content may include all sub-content, or may include only a part of sub-content. Wherein the portion of sub-content may be content that is changed as compared to the last forwarded and/or delivered content. The sub-content of the forwarding content and/or the delivering content may be a specific value or a change value compared to the last-forwarded and/or delivered content.

If the second entity cannot feed back the model forwarding result to the first entity according to the model forwarding request sent by the first entity, the second entity sends a seventh message including that forwarding cannot be performed or forwarding fails to the first entity, so that the first entity knows that the second entity cannot perform forwarding according to the request.

The seventh message may be a HANDOVER REQUEST (HANDOVER REQUEST) message of X2 or Xn or a get UE context response (RETRIEVE UE CONTEXT RESPONSE) message or a get UE context failure (RETRIEVE UE CONTEXT FAILURE) message; the second eNB modification request (SENB MODIFICATION REQUEST) message or second eNB modification request awareness (SENB MODIFICATION REQUEST ACKNOWLEDGE) message or second eNB modification request rejection (SENB MODIFICATION REQUEST REJECT) message or second gNB modification request (SGNB MODIFICATION REQUEST) message or second gNB modification request awareness (SGNB MODIFICATION REQUEST ACKNOWLEDGE) message or second gNB modification request rejection (SGNB MODIFICATION REQUEST REJECT) message or second eNB modification need (SENB MODIFICATION REQUIRED) message or second eNB modification acknowledgement (SENB MODIFICATION CONFIRM) message or second eNB modification rejection (SENB MODIFICATION REFUSE) message or second gNB modification need (SGNB MODIFICATION REQUIRED) message or second gNB modification acknowledgement (SGNB MODIFICATION CONFIRM) message or second gNB modification rejection (SGNB MODIFICATION REFUSE) message of X2; or an Xn secondary node modification request (S-NODE MODIFICATION REQUEST) message or a secondary node modification request awareness (S-NODE MODIFICATION REQUEST ACKNOWLEDGE) message or a secondary node modification request rejection (S-NODE MODIFICATION REQUEST REJECT) message or a secondary node modification need (S-NODE MODIFICATION REQUIRED) message or a secondary node modification acknowledgement (S-NODE MODIFICATION CONFIRM) message or a secondary node modification rejection (S-NODE MODIFICATION REFUSE) message; a second gNB change required (SGNB CHANGE REQUIRED) message, which may also be X2; an auxiliary node change need (S-NODE CHANGE REQUIRED) message of Xn is also possible; a second gNB release request aware (SGNB RELEASE REQUEST ACKNOWLEDGE) message or a second eNB release need (SENB RELEASE REQUIRED) message or a second gNB release need (SGNB RELEASE REQUIRED) message of X2; or an Xn secondary node release request awareness (S-NODE RELEASE REQUEST ACKNOWLEDGE) message or a secondary node release need (S-NODE RELEASE REQUIRED) message; a second eNB reconfiguration complete (SENB RECONFIGURATION COMPLETE) message or a second gNB reconfiguration complete (SGNB RECONFIGURATION COMPLETE) message of X2; or an auxiliary node reconfiguration complete (S-NODE RECONFIGURATION COMPLETE) message of Xn; a HANDOVER required (HANDOVER REQUIRED) message or a HANDOVER REQUEST (HANDOVER REQUEST) message or a path switch REQUEST aware (PATH SWITCH REQUEST ACKNOWLEDGE) message or a path switch REQUEST failed (PATH SWITCH REQUEST failed) message or a UE context release REQUEST (UE CONTEXT RELEASE REQUEST) message or a UE context release complete (UE CONTEXT RELEASE COMPLETE) message or a UE information forwarding (UE INFORMATION TRANSFER) message or an initial UE context setup REQUEST (INITIAL CONTEXT SETUP REQUEST) message; it may also be a reset aware (RESET ACKNOWLEDGE) message of F1 or a F1 SETUP RESPONSE (F1 SETUP RESPONSE) message or a F1 SETUP FAILURE (F1 SETUP FAILURE) message or a GNB-DU configuration update aware (GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-DU configuration update FAILURE (GNB-DU CONFIGURATION UPDATE FAILURE) message or a GNB-CU configuration update aware (GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-CU configuration update FAILURE (GNB-CU CONFIGURATION UPDATE FAILURE) message or a UE context release complete (UE CONTEXT RELEASE COMPLETE) message or a UE context modification RESPONSE (UE CONTEXT MODIFICATION RESPONSE) message or a UE context modification FAILURE (UE CONTEXT MODIFICATION FAILURE) message or a UE context modification acknowledgement (UE CONTEXT MODIFICATION CONFIRM) message or a UE context modification rejection (UE CONTEXT MODIFICATION REFUSE) message; it may also be a reset aware (RESET ACKNOWLEDGE) message of E1 or a GNB-CU-UP E1 SETUP RESPONSE (GNB-CU-UP E1 SETUP RESPONSE) message or a GNB-CU-UP E1 SETUP FAILURE (GNB-CU-UP E1 SETUP FAILURE) message or a GNB-CU-CP E1 SETUP RESPONSE (GNB-CU-CP E1 SETUP RESPONSE) message or a GNB-CU-CP E1 SETUP FAILURE (GNB-CU-CP E1 SETUP FAILURE) message or a GNB-CU-UP configuration update aware (GNB-CU-UP CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-CU-UP configuration update FAILURE (GNB-CU-UP CONFIGURATION UPDATE FAILURE) message or a GNB-CU-CP configuration update aware (GNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE) message or a GNB-CU-CP configuration update FAILURE (GNB-CU-CP CONFIGURATION UPDATE FAILURE) message; or an E1 RELEASE RESPONSE (E1 RELEASE RESPONSE) message or bearer context setup RESPONSE (BEARER CONTEXT SETUP RESPONSE) message or bearer context setup failure (BEARER CONTEXT SETUP FAILURE) message or bearer context modification RESPONSE (BEARER CONTEXT MODIFICATION RESPONSE) message or bearer context modification failure (BEARER CONTEXT MODIFICATION FAILURE) message or bearer context modification acknowledgement (BEARER CONTEXT MODIFICATION CONFIRM) message or bearer context RELEASE complete (BEARER CONTEXT RELEASE COMPLETE) message; or a newly defined X2 message or Xn message or NG message or F1 message or E1 message.

The seventh message includes one or more of the following:

● UE identity: and the method is used for identifying the UE where the model information to be reported is located and/or applicable. The identification may be one or more of the following: NG-RAN node UE XnAP ID, source NG-RAN node UE XnAP ID, M-NG-RAN node UE XnAP ID, S-NG-RAN node UE XnAP ID, meNB UE X2AP ID, seNB UE X2AP ID, meNB UE X2AP ID, sgNB UE X2AP ID, AMF UE NGAP ID, RAN UE NGAP ID, source AMF UE NGAP ID.

● The reason is that: for indicating the reason for the failure of the request, e.g., no forwarding content requested, no model, model unavailable, etc.

According to yet another aspect of an embodiment of the present disclosure, there is provided a method of supporting wireless communication network data collection, the method comprising: the first entity sends an eighth message including a calculation force information reporting request to the second entity to notify the second entity of the calculation force information reporting requirement. After receiving the eighth message, the second entity needs to report the calculation information to the first entity according to the calculation information reporting request, so that the first entity can acquire the calculation information of the second entity, and the performance of the subsequent network and/or UE is ensured.

The eighth message may be a resource status request (RESOURCE STATUS REQUEST) message of X2 or Xn or F1 or E1; or an EN-DC resource status REQUEST (EN-DC RESOURCE STATUS REQUEST) message of X2 or an EN-DC X2 SETUP REQUEST (EN-DC X2 SETUP REQUEST) message or an EN-DC configuration update (EN-DC CONFIGURATION UPDATE) message or a second gNB addition REQUEST (SGNB ADDITION REQUEST) message; an Xn SETUP REQUEST (Xn SETUP REQUEST) message of Xn or an NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or a secondary node addition REQUEST (S-NODE ADDITION REQUEST) message or a secondary node modification REQUEST (S-NODE MODIFICATION REQUEST) message or a secondary node modification need (S-NODE MODIFICATION REQUIRED) message; a gNB Central Unit (gNB-CU)) configuration update (gNB-CU CONFIGURATION UPDATE) message of F1; also can be a gNB central unit control plane (gNB Central Unit Control Plane, gNB-CU-CP) E1 SETUP REQUEST (GNB-CU-CP E1 SETUP REQUEST) message or a gNB-CU-CP configuration update (GNB-CU-CP CONFIGURATION UPDATE) message or a bearer context SETUP REQUEST (BEARER CONTEXT SETUP REQUEST) message or a bearer context modification REQUEST (BEARER CONTEXT MODIFICATION REQUEST) message of E1; measurement configuration of RRC, MDT configuration, etc. are also possible; or a newly defined X2 message or Xn message or F1 message or E1 message or RRC Container.

The eighth message includes one or more of the following:

● First entity identification: for identifying the requesting entity. The identification may be one or more of the following: cell Global ID, target Cell Global ID, requested Target Cell ID, eNB Measurement ID, en-gNB Measurement ID, NG-RAN node Measurement ID, gNB-DU Measurement ID, gNB-CU Measurement ID, gNB-CU-CP Measurement ID, gNB-CU-UP Measurement ID, RAN Measurement ID.

● Second entity identification: for identifying the entity that received the request. The identification may be one or more of the following: cell Global ID, target Cell Global ID, requested Target Cell ID, ue-Identity, newUE-Identity, eNB Measurement ID, en-gNB Measurement ID, NG-RAN node Measurement ID, gNB-DU Measurement ID, gNB-CU Measurement ID, gNB-CU-CP Measurement ID, gNB-CU-UP Measurement ID, RAN Measurement ID.

● And (3) predicting and identifying: and the predicted computing power related information reporting request is used for identifying whether the request comprises the second entity. This field may be represented by a single bit, e.g., 1 indicates that the request includes a predicted-force-related information reporting request, and 0 indicates that the request does not include a predicted-force-related information reporting request; or 1 indicates that the request does not include the predicted-force-related information reporting request, and 0 indicates that the request includes the predicted-force-related information reporting request. Alternatively, 1 may indicate that the request includes a request for reporting information related to the predicted calculation power, and 0 may indicate that the request includes a request for reporting information related to the calculation power; or 1 indicates that the request comprises a calculation power related information reporting request, and 0 indicates that the request comprises a predicted calculation power related information reporting request.

● Predicting a registration request: and the related information is used for indicating at least one of the start, the end or the new addition of the predicted power information.

● Registration request: and the related information is used for indicating at least one of the start, the end or the new addition of the calculation force information reporting.

● Reporting time interval: and the time interval is used for representing the reporting of the calculation force information. The time may be represented by 2*n bits, for example, the first n bits represent the start time of the report, and the last n bits represent the end time of the report, which may be a relative time or an absolute time. It may also be represented by separate fields, including one or more of the following:

● Reporting time: and the time point is used for representing the reporting time point of the calculation force information. The time may be a relative time or an absolute time.

● Predicted information reporting time interval: the time interval is used for indicating the report of the predicted power information. The time may be represented by 2*n bits, for example, the first n bits represent the start time of the report, and the last n bits represent the end time of the report, which may be a relative time or an absolute time. It may also be represented by separate fields, including one or more of the following:

● Predicted information reporting time: the time point is used for indicating the report of the predicted calculation force information. The time may be a relative time or an absolute time.

● Prediction result application time of prediction information: for representing the time of applicability and/or the point in time of the requested predictive power information. The time may be a relative time or an absolute time. In the case of a time interval, this may be represented by 2*n bits, for example, the first n bits representing the start time and the last n bits representing the end time. It may also be represented by separate fields, including one or more of the following:

start time: for indicating the start time of the applicable time interval. The start time may be a relative time or an absolute time.

End time: for indicating the end time of the applicable time interval. The end time may be a relative time or an absolute time.

● The calculation force information reporting type: the method is used for indicating that the calculation force information is reported in a single time or periodically or in a condition triggering manner. Reporting types include, but are not limited to: on demand, periodic, condition triggered reporting, etc.

● Calculation force information reporting period: and the interval time is used for representing the periodic reporting of the calculation force information. If the field content is not available, a single report is indicated.

● And (3) calculating force information reporting triggering condition configuration: the method is used for indicating the triggering condition of the information reporting of the calculation force. Only when the actual condition meets the triggering condition, the calculation force information needs to be reported, such as that the calculation force is larger than and/or larger than or equal to a certain threshold value, that the calculation force is smaller than and/or smaller than or equal to a certain threshold value, that the calculation force is in a descending trend, that the calculation force is in an ascending trend, and the like.

● The type of information reporting of the predicted calculation power: the method is used for indicating that the predicted power information is reported in a single time or periodically or in a condition triggering manner. Reporting types include, but are not limited to: on demand, periodic, condition triggered reporting, etc.

● The predicted power information reporting period: the device is used for representing the interval time for periodically reporting the predicted power information. If the field content is not available, a single report is indicated.

● Configuration of the triggering condition of the report of the predicted calculation power information: the method is used for indicating the triggering condition of the information reporting of the predicted power. The predicted calculation force information needs to be reported only when the actual situation meets the triggering situation, such as the predicted calculation force is greater than and/or greater than or equal to a certain threshold value, the predicted calculation force is less than and/or less than or equal to a certain threshold value, the predicted calculation force is in a descending trend, the predicted calculation force is in an ascending trend, the calculation force is greater than and/or greater than or equal to a certain threshold value, the calculation force is less than and/or less than or equal to a certain threshold value, the calculation force is in a descending trend, the calculation force is in an ascending trend, and the like.

● The information content of calculation force needs to be reported: and the calculation information is used for indicating calculation information which needs to be reported. The reporting content includes one or more of the following: the calculation force, hash value, and the like may be TOPS, TFLOPS, FLOP, GOPS or the like.

● The content of the predictive calculation power information needs to be reported: and the predicted calculation force information is used for indicating the information to be reported. The reporting content includes one or more of the following: the calculation force, hash value, and the like may be TOPS, TFLOPS, FLOP, GOPS or the like.

The second entity sends a ninth message comprising a calculation force information reporting request response to the first entity according to the calculation force information reporting request sent by the first entity so as to inform the first entity whether the calculation force information can be reported.

The ninth message may be a resource status response (RESOURCE STATUS RESPONSE) message or a resource status failure (RESOURCE STATUS FAILURE) message or a resource status update (RESOURCE STATUS UPDATE) message of X2 or Xn or F1 or E1; it may also be an EN-DC resource status RESPONSE (EN-DC RESOURCE STATUS RESPONSE) message of X2 or an EN-DC resource status FAILURE (EN-DC RESOURCE STATUS FAILURE) message or an EN-DC resource status update (EN-DC RESOURCE STATUS UPDATE) message of X2 or an EN-DC X2 SETUP RESPONSE (EN-DC X2 SETUP RESPONSE) message or an EN-DC X2 SETUP FAILURE (EN-DC X2 SETUP FAILURE) message or an EN-DC configuration update (EN-DC CONFIGURATION UPDATE) message or an EN-DC configuration awareness (EN-DC CONFIGURATION UPDATE ACKNOWLEDGE) message or a second gNB addition request awareness (SGNB ADDITION REQUEST ACKNOWLEDGE) message; an Xn setup response (XN SETUP RESPONSE) message or NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or NG-RAN node configuration update aware (NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE) message or secondary node addition request (S-NODE ADDITION REQUEST) message or secondary node addition request aware (S-NODE ADDITION REQUEST ACKNOWLEDGE) message or secondary node modification request aware (S-NODE MODIFICATION REQUEST ACKNOWLEDGE) message or secondary node modification request reject (S-NODE MODIFICATION REQUEST REJECT) message or secondary node modification confirm (S-NODE MODIFICATION CONFIRM) message of Xn; also possible is a gNB-CU configuration update awareness (GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE) message or a gNB distribution unit (gNB Distributed Unit, gNB-DU) configuration update awareness (GNB-DU CONFIGURATION UPDATE) message or a GNB-DU status indication (GNB-DU STATUS INDICATION) message of F1; also can be a gNB-CU User Plane (gNB-CU-User Plane, gNB-CU-UP) configuration update (GNB-CU-UP CONFIGURATION UPDATE) message or a bearer context modification response (BEARER CONTEXT MODIFICATION RESPONSE) message or a GNB-CU-UP status indication (GNB-CU-UP STATUS INDICATION) message of E1; measurement reports of RRC, MDT reports, etc.; or a newly defined X2 message or Xn message or F1 message or E1 message or RRC Container.

The ninth message includes one or more of the following:

● First entity identification: for identifying the first entity. The identification may be one or more of the following: cell Global ID, target Cell Global ID, requested Target Cell ID, eNB Measurement ID, en-gNB Measurement ID, NG-RAN node Measurement ID, gNB-DU Measurement ID, gNB-CU Measurement ID, gNB-CU-CP Measurement ID, gNB-CU-UP Measurement ID, RANMeasurement ID.

● Second entity identification: for identifying the second entity. The identification may be one or more of the following: cell Global ID, target Cell Global ID, requested Target Cell ID, ue-Identity, newUE-Identity, eNB Measurement ID, en-gNB Measurement ID, NG-RAN node Measurement ID, gNB-DU Measurement ID, gNB-CU Measurement ID, gNB-CU-CP Measurement ID, gNB-CU-UP Measurement ID, RAN Measurement ID.

● The application range is as follows: the application scope identification and/or the identification list of the message content. Including one or more of the following: UE, qoS flow (QoS flow), qoS class (QoS level), data radio bearer (Data Radio Bearer), slice, cell, node, traffic, area, operator, etc. The identification of the slice may be single network slice selection assistance information (Single Network Slice Selection Assistance Information, S-NSSAI). The identity of the cell may be a Physical layer cell identity (Physical-layer Cell identity). The identity of the operator may be a public land mobile network (Public Land Mobile Network ID, PLMNID). The identification of QoS class may be a mapped 5G quality of service identification (5G QoS Identifier,5QI) or quality of service class identification (QoS Class Identifier, QCI).

● The requested predicted content may report an acknowledgement: a single bit can be used for indicating whether the predicted calculation force information can be reported, if the bit is 1, all the requested predicted calculation force contents can be reported, and if the bit is 0, the requested predicted calculation force contents cannot be reported; or request content confirmation one by one, for example, in the form of a bitmap (bitmap), where each bit corresponds to one request content, for example, when the bit is 1, it indicates that the corresponding request content can be sent, and 0 indicates that the corresponding request content cannot be sent; separate fields may also be used to represent different confirmation of the content of the request for reporting.

● And reporting the calculation force information to trigger conditions: and the trigger condition is used for indicating the reporting of the calculation force information. Only when the actual condition meets the triggering condition, the calculation force information needs to be reported, such as that the calculation force is larger than and/or larger than or equal to a certain threshold value, that the calculation force is smaller than and/or smaller than or equal to a certain threshold value, that the calculation force is in a descending trend, that the calculation force is in an ascending trend, and the like.

● The triggering condition is reported by the predicted calculation force information: the trigger condition is used for indicating the report of the predicted power information. The predicted calculation force information needs to be reported only when the actual situation meets the triggering situation, such as the predicted calculation force is greater than and/or greater than or equal to a certain threshold value, the predicted calculation force is less than and/or less than or equal to a certain threshold value, the predicted calculation force is in a descending trend, the predicted calculation force is in an ascending trend, the calculation force is greater than and/or greater than or equal to a certain threshold value, the calculation force is less than and/or less than or equal to a certain threshold value, the calculation force is in a descending trend, the calculation force is in an ascending trend, and the like.

● The calculation force information report content: for indicating the reported calculation force information. The reporting content includes one or more of the following: the calculation force, hash value, and the like may be TOPS, TFLOPS, FLOP, GOPS or the like.

● The report content of the predicted calculation force information comprises the following steps: and the prediction calculation force information is used for indicating the reported prediction calculation force information. The reporting content includes one or more of the following: the calculation force, hash value, and the like may be TOPS, TFLOPS, FLOP, GOPS or the like.

● Accuracy of predicted power information: the method is used for indicating the accuracy of the reported predicted calculation force information and/or model. The accuracy may include one or more of the following: accuracy, reliability, etc.

● The application time of the predicted power information: for indicating the applicable time and/or point in time of the reported predictive power information. The time may be a relative time or an absolute time. In the case of a time interval, this may be represented by 2*n bits, for example, the first n bits representing the start time and the last n bits representing the end time. It may also be represented by separate fields, including one or more of the following:

The second entity sends a tenth message comprising the calculation force information to the first entity according to the self situation and/or according to the calculation force information reporting request sent by the first entity, so that the first entity can acquire the calculation force information.

The tenth message may be a resource status response (RESOURCE STATUS RESPONSE) message or a resource status failure (RESOURCE STATUS FAILURE) message or a resource status update (RESOURCE STATUS UPDATE) message of X2 or Xn or F1 or E1; it may also be an EN-DC resource status RESPONSE (EN-DC RESOURCE STATUS RESPONSE) message of X2 or an EN-DC resource status FAILURE (EN-DC RESOURCE STATUS FAILURE) message or an EN-DC resource status update (EN-DC RESOURCE STATUS UPDATE) message of X2 or an EN-DC X2 SETUP RESPONSE (EN-DC X2 SETUP RESPONSE) message or an EN-DC X2 SETUP FAILURE (EN-DC X2 SETUP FAILURE) message or an EN-DC configuration update (EN-DC CONFIGURATION UPDATE) message or an EN-DC configuration awareness (EN-DC CONFIGURATION UPDATE ACKNOWLEDGE) message or a second gNB addition request awareness (SGNB ADDITION REQUEST ACKNOWLEDGE) message; an Xn setup response (XN SETUP RESPONSE) message or NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or NG-RAN node configuration update aware (NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE) message or secondary node addition request (S-NODE ADDITION REQUEST) message or secondary node addition request aware (S-NODE ADDITION REQUEST ACKNOWLEDGE) message or secondary node modification request aware (S-NODE MODIFICATION REQUEST ACKNOWLEDGE) message or secondary node modification request reject (S-NODE MODIFICATION REQUEST REJECT) message or secondary node modification confirm (S-NODE MODIFICATION CONFIRM) message of Xn; also possible is a gNB-CU configuration update awareness (GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE) message or a gNB distribution unit (gNB Distributed Unit, gNB-DU) configuration update awareness (GNB-DU CONFIGURATION UPDATE) message or a GNB-DU status indication (GNB-DU STATUS INDICATION) message of F1; also can be a gNB-CU User Plane (gNB-CU-User Plane, gNB-CU-UP) configuration update (GNB-CU-UP CONFIGURATION UPDATE) message or a bearer context modification response (BEARER CONTEXT MODIFICATION RESPONSE) message or a GNB-CU-UP status indication (GNB-CU-UP STATUS INDICATION) message of E1; measurement reports of RRC, MDT reports, etc.; or a newly defined X2 message or Xn message or F1 message or E1 message or RRC Container.

The tenth message includes one or more of the following:

● First entity identification: for identifying the first entity. The identification may be one or more of the following: cell Global ID, target Cell Global ID, requested Target Cell ID, eNB Measurement ID, en-gNB Measurement ID, NG-RAN node Measurement ID, gNB-DU Measurement ID, gNB-CU Measurement ID, gNB-CU-CP Measurement ID, gNB-CU-UP Measurement ID, RAN Measurement ID.

● The calculation force information report content: and the power calculation information is used for indicating the reported power calculation information. The reporting content includes one or more of the following: the calculation force, hash value, and the like may be TOPS, TFLOPS, FLOP, GOPS or the like.

● The report content of the predicted calculation force information comprises the following steps: and the predicted calculation force information is used for indicating the report. The reporting content includes one or more of the following: the calculation force, hash value, and the like may be TOPS, TFLOPS, FLOP, GOPS or the like.

If the second entity cannot feed back the calculation information result to the first entity according to the calculation information reporting request sent by the first entity, the second entity sends an eleventh message including failure to report or failure to report to the first entity, so that the first entity knows that the second entity cannot report according to the request.

The eleventh message may be a resource status response (RESOURCE STATUS RESPONSE) message or a resource status failure (RESOURCE STATUS FAILURE) message or a resource status update (RESOURCE STATUS UPDATE) message of X2 or Xn or F1 or E1; it may also be an EN-DC resource status RESPONSE (EN-DC RESOURCE STATUS RESPONSE) message of X2 or an EN-DC resource status FAILURE (EN-DC RESOURCE STATUS FAILURE) message or an EN-DC resource status update (EN-DC RESOURCE STATUS UPDATE) message of X2 or an EN-DC X2 SETUP RESPONSE (EN-DC X2 SETUP RESPONSE) message or an EN-DC X2 SETUP FAILURE (EN-DC X2 SETUP FAILURE) message or an EN-DC configuration update (EN-DC CONFIGURATION UPDATE) message or an EN-DC configuration awareness (EN-DC CONFIGURATION UPDATE ACKNOWLEDGE) message or a second gNB addition request awareness (SGNB ADDITION REQUEST ACKNOWLEDGE) message; an Xn setup response (XN SETUP RESPONSE) message or NG-RAN node configuration update (NG-RAN NODE CONFIGURATION UPDATE) message or NG-RAN node configuration update aware (NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE) message or secondary node addition request (S-NODE ADDITION REQUEST) message or secondary node addition request aware (S-NODE ADDITION REQUEST ACKNOWLEDGE) message or secondary node modification request aware (S-NODE MODIFICATION REQUEST ACKNOWLEDGE) message or secondary node modification request reject (S-NODE MODIFICATION REQUEST REJECT) message or secondary node modification confirm (S-NODE MODIFICATION CONFIRM) message of Xn; also possible is a gNB-CU configuration update awareness (GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE) message or a gNB distribution unit (gNB Distributed Unit, gNB-DU) configuration update awareness (GNB-DU CONFIGURATION UPDATE) message of F1; also can be a gNB-CU User Plane (gNB-CU-User Plane, gNB-CU-UP) configuration update (GNB-CU-UP CONFIGURATION UPDATE) message or a bearer context modification response (BEARER CONTEXT MODIFICATION RESPONSE) message of E1; measurement reports of RRC, MDT reports, etc.; or a newly defined X2 message or Xn message or F1 message or E1 message or RRC Container. The eleventh message includes one or more of the following:

● The reason is that: for example, the report content without request, the calculation information without calculation information, the prediction capability without calculation information, the corresponding prediction result of the application time of the requested prediction result, etc. can not be provided.

The models referred to in this disclosure may be artificial intelligence models, machine learning models, mathematical models, and the like.

The distribution of the model referred to in this disclosure is that the owner entity of the model downloads to the requester entity of the model, and the downloading of the model is that the requester entity of the model downloads from the owner entity of the model, and in this disclosure, the distribution and downloading of the model may be replaced with each other according to the entity roles.

The reasoning content in the present disclosure is an output result obtained by inputting corresponding input parameters by using a trained model.

The activation state of the user referred to in the present disclosure may be a state such as an RRC Connected state (rrc_connected) and/or a CM Connected state (cm_connected), the deactivation state of the user may be a state such as an RRC Inactive state (rrc_active), and the Idle state of the user may be a state such as an RRC Idle state (rrc_idle) and/or a CM Idle state (cm_idle).

The model state referred to in this disclosure may be that for a model that has been downloaded, the deactivated state represents a retention model, but without training and/or reasoning; the activation state indicates that the model is being used, and training and/or reasoning, etc. For a model that has not been downloaded, the deactivated state indicates that the downloaded portion is reserved, but the remaining portion is not to be downloaded continuously; the active state indicates that the un-downloaded portion is continuing to be downloaded.

The model management decisions referred to in this disclosure may be that for the model that has been downloaded, the representation retention model is deactivated, but no training and/or reasoning is performed; the representation retention model is activated and training and/or reasoning continues. Deactivating the model for incomplete downloads, which means that the downloaded portion remains but does not continue to be downloaded; the activation indicates that the downloading of the non-downloaded portion is continued.

The on-demand reporting referred to in this disclosure may refer to a single reporting.

The user experience information referred to in this disclosure may include one or more of the following: round-trip time (Round-trip time), jitter duration (Jitter duration), corruption duration (Corruption duration), average throughput (Average throughput), initial Play-out delay (Initial playout delay), device Information (Device Information), rendering viewport (Rendered viewports), codec Information (Codec Information), buffer level (Buffer level), switch time representation (Representation switch events), playlist (playlist), media presentation description Information (MPD (Media presentation description) Information), interactivity summary (Interactivity Summary), interactivity event List (Interactivity Event List), qoE MOS value, evaluation value of the above parameters, and the like.

The quality of service information referred to in this disclosure may include one or more of the following: packet loss rate, delay, throughput, data rate, qoS class, evaluation of the above parameters, etc. The identification of QoS class may be a mapped 5G quality of service identification (5G QoS Identifier,5QI) or quality of service class identification (QoS Class Identifier, QCI).

The load information in this disclosure may also be resource status information.

The measurement report information and/or measurement report related values in the present disclosure may include one or more of the following: RSRP, RSRQ, SINR, strength indication of received signal (Received Signal Strength Indicator, RSSI), etc.

The characteristic parameters of the model referred to in this disclosure may be absolute values or relative values, for example, relative values with respect to previous parameters and/or existing parameters. The relative values may help reduce the signaling size of the transmission.

The positional information referred to in this disclosure may be absolute position, relative position, or the like. The location information may be represented in terms of longitude and latitude, absolute coordinates, relative coordinates, serving cell, camping cell, connection entity, beam, etc. The location information may be represented in terms of latitude and longitude, absolute coordinates, relative coordinates, serving cell, camping cell, etc. The location information may include one or more of the following: time points and/or time intervals, location coordinates and/or ranges, expected speed (including size and/or direction), direction of movement, cell identity (e.g., cell Global ID, etc.), entity identity, beam identity, accuracy, etc. The serving cell and/or the camping cell may be represented by a cell identity. The accuracy of the location information may include, for example, meters, centimeters, decimeters, kilometers, and the like.

The trajectory information referred to in this disclosure may be represented in terms of longitude and latitude, absolute coordinates, relative coordinates, serving cell, camping cell, connection entity, beam, etc. The trajectory information may be represented in terms of longitude and latitude, absolute coordinates, relative coordinates, serving cell, camping cell, etc. The trajectory information may include one or more of the following: time points and/or time intervals, location coordinates and/or ranges, predicted speed (including magnitude and/or direction), direction of movement, cell identity (e.g., cell Global ID, etc.), entity identity, beam identity, accuracy, track special case type, track special case coordinate points and/or ranges, etc. The serving cell and/or the camping cell may be represented by a cell identity. The accuracy of the trajectory information may include, for example, meters, centimeters, decimeters, kilometers, and the like. The track special case type may include, but is not limited to, long dwell, short dwell, ping-pong movement, etc. The coordinate points and/or the range of the special track condition represent the position information of the special track condition.

The energy efficiency referred to in this disclosure may include one or more of the following: maximum power (in watts), minimum power, average power, energy consumption (Energy consumption in kilowatt hours), amount of uplink and/or downlink Data (Data volume), ratio of amount of uplink and/or downlink Data to energy consumption. The types of traffic referred to in this disclosure may include one or more of the following: ultra-reliable low latency transmissions (Ultra Reliable Low Latency Communication, URLLC), enhanced mobile broadband (Enhanced Mobile Broadband, emmbb), mass machine type communications (massive Machine Type of Communication, mctc), and the like. Traffic types may also refer to services having one and/or more QoS requirements. The traffic type may also be represented by QoS class, qoS type, etc.

The QoS class and/or QoS type referred to in this disclosure may be identified by one or more of the following: 5G QoS identification (5G QoS Identifier,5QI), qoS flow identification (Qos Flow Identifier, QFI), etc.

Traffic information referred to in this disclosure may include one or more of the following: data volume, qoS class and/or QoS type, qoS parameters, qoS requirements, qoS parameters corresponding to QoS requirements and/or QoS class and/or QoS type, etc.

The handover target node information referred to in the present disclosure may include one or more of: target node, target cell, target beam, target slice, etc.

The entities and/or nodes referred to in this disclosure may also refer to one and/or more cells of an entity and/or node.

The operating condition information referred to in this disclosure may include one or more of the following: neighbor cell measurements, connection cell measurements, measurement compensation, hysteresis, threshold for event, etc.

Measurement results and measurement reports referred to in this disclosure may refer to each other.

Load information and/or resource status information referred to in this disclosure may include one or more of the following: a transport network layer (Transport Network Layer, TNL) capacity indication, radio resource status, integrated available capacity set, integrated available resource set, number of active user terminals, radio resource control (Radio Resource Control, RRC) connection number, slice available capacity, hardware capacity indication, S1 TNL load indication, hardware load indication, almost blank subframe (Almost Blank Subframe, ABS) status, reference signal received power (Reference Signal Received Power, RSRP) measurement report or report list, reference signal received quality (Reference Signal Receiving Quality, RSRQ) measurement report or report list, signal to interference plus noise ratio (Signal to Interference plus Noise Ratio, SINR) measurement report or report list, RSSI report or report list, channel state information (Channel State Information, CSI) report, cell report indication, channel occupancy (Channel Occupancy) time scale, energy Detection (Energy Detection) threshold, signal strength and/or signal quality, channel busy scale, data volume, and Jitter (Jitter) condition of respective predicted content parameters, etc. Where the jitter condition may be the variance or standard deviation of the parameters. The parameter may be a connection cell condition, a neighbor cell condition, or a condition of other coexistence technologies (for example, wireless local area network (Wireless Local Area Network, WLAN), bluetooth, etc.), or a sum of a self condition and a neighbor cell condition, or an average value of a self condition and a neighbor cell condition. The parameters may be uplink, downlink, uplink and downlink. The parameter may be a current value, a historical value, a maximum value, a minimum value, or an average value.

The radio resource status referred to in the present disclosure is used to indicate the usage of physical resource blocks (Physical Resource Block, PRBs) for downlink and/or uplink traffic and/or the usage of physical downlink control channel elements (Physical downlink control channel Control channel element, PDCCH CCEs) for downlink and/or uplink scheduling. For example, a radio resource status is used to indicate a physical resource block (Physical Resource Block, PRB) usage of downlink and uplink traffic and a physical downlink control channel element (Physical downlink control channel Control channel element, PDCCH CCE) usage of downlink and uplink scheduling within a region, e.g., a cell and/or synchronization signal/physical broadcast channel block (Synchronisation signal/Physical broadcast channel block, SSB) region, and/or for a period of time and/or at one or more points in time and/or one or more slices, which may be a radio resource status (Radio Resource Status) and/or a new radio resource status (NR Radio Resource Status); the radio resource status may also be used to indicate the PRB usage of downlink and uplink traffic in a certain region, e.g., a cell and SSB region, and/or over a period of time and/or at one or more time points and/or one or more slices; the radio resource status may also be used to indicate the PRB usage of downlink and uplink traffic and the PDCCH CCE usage of downlink and uplink scheduling. The radio resource status may include one or more of: uplink and/or downlink guaranteed bit rate (Guaranteed Bit Rate, GBR) PRB usage, uplink and/or downlink non-GBR PRB usage, uplink and/or downlink scheduling PDCCH CCE usage, SSB region uplink and/or downlink GBR PRB usage, SSB region uplink and/or downlink non-GBR PRB usage, SSB region uplink and/or downlink PRB usage, uplink and/or downlink scheduling PDCCH CCE usage, and the like.

Reference signal received power (Reference Signal Received Power, RSRP) measurement reports or report lists referred to in this disclosure are used to provide RSRP measurement reports for user terminals. For example, an RSRP measurement report or report list may be used to provide an RSRP measurement report for the user terminal, and the reference signal received power measurement report list may be an RSRP measurement report list (RSRP Measurement Report List). The reference signal received power measurement report list may include a measured RSRP or the like.

The channel state information (Channel State Information, CSI) reports referred to in this disclosure are used to provide CSI reports for the UE. The channel state information report may include one or more of the following: rank Indicator (RI), wideband channel quality Indicator (Channel quality Indicator, CQI), subband (subband) size, subband CQI, subband index, 4-bit CQI, 3-bit spatial differential CQI, 2-bit subband differential CQI, 2-bit subband differential CQI, precoding matrix Indicator (Precoding Matrix Indicator, PMI), channel state information reference signal resource Indicator (CSI-RS Resource Indicator, CRI), layer Indicator (LI), layer 1 reference signal received power (L1-RSRP).

The model information referred to in this disclosure includes all information related to the model, and may include one or more of the following: model information, inferred content report information, inferred content information, and the like.

Exemplary embodiments of the present disclosure are further described below with reference to the accompanying drawings.

Fig. 3 illustrates a schematic diagram of one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure. Specifically, fig. 3 illustrates a process of interacting UE model information between entities, which provides information for the entities to make UE model management decisions on a UE model, so as to ensure validity of UE model issuing and/or training and/or reasoning, and reduce unnecessary model issuing and/or training and/or reasoning. In one implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB, and the second entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB. In another implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB, and the second entity may be a UE. In yet another implementation, for example, the first entity may be an AMF or SMF or MME and the second entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB. In yet another implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB, and the second entity may be an AMF or SMF or MME.

Step 301: the first entity sends a UE model information request message to the second entity to inform the second entity of UE model information that needs to be fed back to the first entity. In one implementation, for example, the message may be the aforementioned first message including the UE model information request.

Step 302: the second entity collects model information.

Step 303: the second entity sends a message including UE model information to the first entity. In one implementation, for example, the message may be the aforementioned second message including UE model information. If the second entity cannot report the UE model information according to the request, the second entity sends a UE model information request failure message to the first entity and step 304 is not performed. In one implementation, for example, the message may be the aforementioned third message including the UE model information reporting failure information.

Step 304: the first entity may make UE model management decisions, e.g., activation, deactivation, deletion, retention, inferential content reporting decisions, etc., for the model of the UE based on the UE model information.

Fig. 4 illustrates a schematic diagram of one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure. Specifically, fig. 4 shows a process of interacting UE model information between entities according to self conditions, and provides information for the entity to make UE model management decisions on the UE model, so as to ensure effectiveness of model issuing and/or training and/or reasoning of the UE, and reduce unnecessary model issuing and/or training and/or reasoning. In one implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB, and the second entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB. In another implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB, and the second entity may be a UE. In yet another implementation, for example, the first entity may be an AMF or SMF or MME and the second entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB. In yet another implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB, and the second entity may be an AMF or SMF or MME.

Step 401: the second entity collects UE model information.

Step 402: the second entity sends a message including UE model information to the first entity according to the self situation. In one implementation, for example, the message may be the aforementioned second message including UE model information.

Step 403: the first entity may make UE model management decisions, e.g., activation, deactivation, deletion, retention, inferential content reporting decisions, etc., for the model of the UE based on the UE model information.

Fig. 5 illustrates a schematic diagram of one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure. Specifically, fig. 5 shows a process of interacting a UE model management decision between entities according to self conditions, and directly or indirectly notifying the UE of the entity to the UE model management decision, so as to ensure effectiveness of model issuing and/or training and/or reasoning of the UE and reduce unnecessary model issuing and/or training and/or reasoning. In one implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB, and the second entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB. In another implementation, for example, the first entity may be a UE and the second entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB. In yet another implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB, and the second entity may be an AMF or SMF or MME. In yet another implementation, for example, the first entity may be an AMF or SMF or MME and the second entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB.

Step 501: the second entity makes a UE model management decision based on the UE model information.

Step 502: the second entity sends a message including the UE model management decision to the first entity according to the self situation. In one implementation, for example, the message may be the fourth message described above including the UE model management decision.

Step 503: the first entity may forward or apply the UE model management decisions. If the first entity is a UE, the UE applies the UE model management decision, and if the first entity is not a UE, the first entity forwards the UE model management decision to other entities, indirectly informing the UE of the UE model management decision.

Fig. 6 illustrates a schematic diagram of one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure. Specifically, fig. 6 illustrates a process of interacting UE model information and UE model management decisions between entities, and notifying the UE of the entity to the UE's model management decisions directly or indirectly, so as to ensure validity of model issuing and/or training and/or reasoning of the UE, and reduce unnecessary model issuing and/or training and/or reasoning. In one implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB, and the second entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB. In another implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB, and the second entity may be a UE. In yet another implementation, for example, the first entity may be an AMF or SMF or MME and the second entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB. In yet another implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB, and the second entity may be an AMF or SMF or MME.

Step 601: the second entity collects UE model information.

Step 602: the second entity sends a message including UE model information to the first entity according to the self situation. In one implementation, for example, the message may be the aforementioned second message including UE model information.

Step 603: the first entity may make UE model management decisions, e.g., activation, deactivation, deletion, retention, inferential content reporting decisions, etc., for the model of the UE based on the UE model information.

Step 604: the first entity sends a message to the second entity including the UE model management decision. In one implementation, for example, the message may be the fourth message described above including the UE model management decision.

Step 605: the second entity may forward or apply the UE model management decisions. If the second entity is a UE, the UE applies the UE model management decision, and if the second entity is not a UE, the second entity forwards the UE model management decision to other entities, indirectly informing the UE of the UE model management decision.

Fig. 7 illustrates a schematic diagram of one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure. Specifically, fig. 7 illustrates a process of interaction model forwarding requests and models between entities, so that the entities may acquire the models to ensure performance of subsequent networks and/or UEs. In one implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB, and the second entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB. In another implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB, and the second entity may be a UE. In yet another implementation, for example, the first entity may be an AMF or SMF or MME and the second entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB. In yet another implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB, and the second entity may be an AMF or SMF or MME. In yet another implementation, for example, the first entity may be a gNB CU and the second entity may be a gNB DU. In yet another implementation, for example, the first entity may be a gNB DU and the second entity may be a gNB CU. In yet another implementation, for example, the first entity may be a gNB CU-CP and the second entity may be a gNB CU-UP. In yet another implementation, for example, the first entity may be a gNB CU-UP and the second entity may be a gNB CU-CP.

Step 701: the first entity sends a model forwarding request message to the second entity. In one implementation, for example, the message may be the fifth message described above that includes the model forwarding request. In another implementation, for example, the message may be the fourth message described above including the UE model management decision.

Step 702: the second entity forwards the message comprising the model to the first entity according to the model forwarding request. In one implementation, for example, the message may be the sixth message described above that includes the model. If the second entity cannot forward the model to the first entity according to the model forwarding request, a message including failure of the model forwarding request is sent to the first entity and step 703 is not performed. In one implementation, for example, the message may be the seventh message described above that includes a model forwarding failure.

Step 703: the first entity may forward or apply the model. If the first entity is a target application entity of the model, the first entity applies the model; if the first entity is not the target application entity of the model, the first entity forwards the model to other entities, indirectly sending the model to the target application entity.

Fig. 8 illustrates a schematic diagram of one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure. Specifically, fig. 8 illustrates that an entity forwards a model according to its own situation, so that the entity can acquire the model to ensure the performance of a subsequent network and/or UE. In one implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB, and the second entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB. In another implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB, and the second entity may be a UE. In yet another implementation, for example, the first entity may be an AMF or SMF or MME and the second entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB. In yet another implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB, and the second entity may be an AMF or SMF or MME. In yet another implementation, for example, the first entity may be a gNB CU and the second entity may be a gNB DU. In yet another implementation, for example, the first entity may be a gNB DU and the second entity may be a gNB CU. In yet another implementation, for example, the first entity may be a gNB CU-CP and the second entity may be a gNB CU-UP. In yet another implementation, for example, the first entity may be a gNB CU-UP and the second entity may be a gNB CU-CP.

Step 801: the second entity forwards the message comprising the model to the first entity according to the self situation. In one implementation, for example, the message may be the sixth message described above that includes the model.

Step 802: the first entity may forward or apply the model. If the first entity is a target application entity of the model, the first entity applies the model; if the first entity is not the target application entity of the model, the first entity forwards the model to other entities, indirectly sending the model to the target application entity.

Fig. 9 illustrates a schematic diagram of one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure. Specifically, fig. 9 illustrates that an entity forwards a model according to its own situation, so that the entity can acquire the model and forward the model to a UE, so as to ensure performance of a subsequent network and/or the UE. In one implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB, and the second entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB. In another implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB, and the second entity may be an AMF or SMF or MME. In yet another implementation, for example, the first entity may be a gNB CU and the second entity may be a gNB DU. In yet another implementation, for example, the first entity may be a gNB DU and the second entity may be a gNB CU. In yet another implementation, for example, the first entity may be a gNB CU-CP and the second entity may be a gNB CU-UP. In yet another implementation, for example, the first entity may be a gNB CU-UP and the second entity may be a gNB CU-CP.

Step 901: the second entity forwards the message comprising the model to the first entity according to its own situation and/or based on the model forwarding request of the first entity. In one implementation, for example, the message may be the sixth message described above that includes the model.

Step 902: the first entity forwards a message including the model to the UE. In one implementation, for example, the message may be the sixth message described above that includes the model.

Step 903: the UE applies the received model.

Fig. 10 illustrates a schematic diagram of one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure. Specifically, fig. 10 shows a process of interacting UE model information and UE model management decisions between entities in a mobile scenario, and notifying the UE of the UE model management decisions of the entities directly or indirectly, so as to ensure validity of model issuing and/or training and/or reasoning of the UE and reduce unnecessary model issuing and/or training and/or reasoning. In one implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB, and the second entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB.

Step 1001: the second entity sends UE model information to the first entity in a handover request message for the UE to inform the first entity of the UE model information of the UE. In one implementation, for example, the message may be the aforementioned second message including UE model information.

Step 1002: the first entity makes a UE model management decision for a model of the UE. The first entity sends the UE model management decision to the second entity in a handover request awareness message for the UE to inform the second entity of the UE model management decision. In one implementation, for example, the message may be the fourth message described above including the UE model management decision.

Step 1003: the second entity sends an RRC reconfiguration message carrying the UE model management decisions to the UE to inform the UE of the UE model management decisions for it. In one implementation, for example, the message may be the fourth message described above including the UE model management decision.

Step 1004: the UE sends an RRC reconfiguration complete message to the first entity.

If the UE model information in step 1001 includes information indicating that there is a model that has not been downloaded, and the UE model management decision in step 1002 requires the second entity to forward the model, step 1005 is performed.

Step 1005: the second entity forwards the message comprising the model to the first entity. In one implementation, for example, the message may be the sixth message described above that includes the model.

If the UE model information in step 1001 includes information indicating that there is a model that has not been downloaded, and/or the first entity decides to distribute the model to the UE, step 1006 is performed.

Step 1006: the first entity sends a message to the UE including the model. In one implementation, for example, the message may be the sixth message described above that includes the model.

Step 1005 may precede step 1003, step 1004 and/or be performed simultaneously with step 1003, step 1004.

Fig. 11 illustrates a schematic diagram of one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure. Specifically, fig. 11 illustrates a process of interacting UE model information between entities in a mobile scenario, so that the entities may make UE model management decisions for the UE, and notify the UE of the UE model management decisions by the entities to ensure effectiveness of model issuing and/or training and/or reasoning for the UE, and reduce unnecessary model issuing and/or training and/or reasoning. In one implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB, and the second entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB.

Step 1101: the second entity sends UE model information to the first entity in a handover request message for the UE to inform the first entity of the UE model information of the UE. In one implementation, for example, the message may be the aforementioned second message including UE model information.

Step 1102: the first entity sends a handover request awareness message to the second entity.

Step 1103: the second entity sends an RRC reconfiguration message to the UE.

Step 1104: the UE sends an RRC reconfiguration complete message to the first entity.

Step 1105: the first entity makes a UE model management decision on a model of the UE. The first entity sends a message to the UE including the UE model management decision to inform the UE of the UE model management decision for it. In one implementation, for example, the message may be the fourth message described above including the UE model management decision.

If the UE model information in step 1101 includes information indicating that there is a model that has not been downloaded, and/or the first entity decides to distribute the model to the UE, step 1106 is performed.

Step 1106: the first entity sends a message to the UE including the model. In one implementation, for example, the message may be the sixth message described above that includes the model.

Fig. 12 illustrates a schematic diagram of one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure. Specifically, fig. 12 shows a process of interacting UE model information and UE model management decisions between a UE and an entity in a mobile scenario, and notifying the UE of the entity to the UE of the model management decisions of the UE, so as to ensure effectiveness of model issuing and/or training and/or reasoning of the UE and reduce unnecessary model issuing and/or training and/or reasoning. In one implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB, and the second entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB.

Step 1201: the second entity sends a handover request to the first entity for the UE.

Step 1202: the first entity sends a handover request awareness message to the second entity.

Step 1203: the second entity sends an RRC reconfiguration message to the UE.

Step 1204: the UE sends an RRC reconfiguration complete message to the first entity, and UE model information is carried in the message so as to inform the first entity of the UE model information of the UE. In one implementation, for example, the message may be the aforementioned second message including UE model information.

Step 1205: the first entity makes a UE model management decision for a model of the UE. The first entity sends a message to the UE including the UE model management decision to inform the UE of the UE model management decision for it. In one implementation, for example, the message may be the fourth message described above including the UE model management decision.

If the UE model information in step 1204 includes information indicating that there is an incomplete download model, and/or the first entity decides to distribute the model to the UE, then step 1206 is performed.

Step 1206: the first entity sends a message to the UE including the model. In one implementation, for example, the message may be the sixth message described above that includes the model.

Fig. 13 illustrates a schematic diagram of one aspect of supporting wireless communication network data collection, according to an embodiment of the present disclosure. Specifically, fig. 13 shows that in a dual-connectivity mobile scenario, the entities interact with UE model information to provide reference information for UE model management decisions, so that the UE may acquire and apply UE model management decisions made by the entities to ensure validity of model delivery and/or training and/or reasoning of the UE, and reduce unnecessary model delivery and/or training and/or reasoning.

Step 1300: and the main node, the source auxiliary node and the target auxiliary node perform a target auxiliary node adding process.

Step 1301: and the master node sends an auxiliary node release request to the source auxiliary node.

Step 1302: the source auxiliary node sends an auxiliary node request knowledge message carrying UE model information to the main node. In one implementation, for example, the message may be the aforementioned second message including UE model information.

Step 1303: the master node sends an RRC reconfiguration message to the UE.

Step 1304: the UE sends an RRC reconfiguration complete message to the master node.

Step 1305: and the master node sends an auxiliary node reconfiguration completion message carrying the UE model information to the target auxiliary node. In one implementation, for example, the message may be the aforementioned second message including UE model information.

Step 1306: and the UE and the target auxiliary node perform a random access process.

Step 1307: and the target auxiliary node makes UE model management decisions according to the received UE model information.

Step 1308: the target secondary node sends a message to the UE including the UE model management decision to inform the UE of the UE model management decision for it. In one implementation, for example, the message may be the fourth message described above including the UE model management decision.

If the UE model management decision in step 1307 requires model forwarding, then steps 1309a and 1310a, or steps 1309b and 1310b are performed.

Step 1309a: the target auxiliary node sends a model forwarding request message to the source auxiliary node. In one implementation, for example, the message may be the fifth message described above that includes the model forwarding request.

Step 1310a: the source secondary node forwards a message including the model to the target secondary node based on the received model forwarding request. In one implementation, for example, the message may be the sixth message described above that includes the model.

Step 1309b, the target auxiliary node sends the model forwarding request message to the source auxiliary node through the main node. In one implementation, for example, the message may be the fifth message described above that includes the model forwarding request.

Step 1310b: the source auxiliary node forwards the message comprising the model to the target auxiliary node through the main node based on the received model forwarding request. In one implementation, for example, the message may be the sixth message described above that includes the model.

If the UE model information in step 1305 includes information indicating that there is a model that has not been downloaded, and/or the target secondary node decides to distribute the model to the UE, step 1311 is performed.

Step 1311: the target secondary node sends a message to the UE including the model. In one implementation, for example, the message may be the sixth message described above that includes the model.

Step 1307 may precede step 1306 or be performed concurrently with step 1306. Step 1309a and step 1310b and/or step 1309b and step 1310b can be performed prior to step 1308 or simultaneously with step 1308.

Fig. 14 illustrates a schematic diagram of one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure. Specifically, fig. 14 shows that in a dual connectivity mobile scenario, the entities interact with UE model information to provide reference information for UE model management decisions, so that the UE may acquire and apply UE model management decisions made by the entities to ensure validity of model delivery and/or training and/or reasoning of the UE, and reduce unnecessary model delivery and/or training and/or reasoning.

Step 1400: and the main node, the source auxiliary node and the target auxiliary node perform a target auxiliary node adding process.

Step 1401: and the master node sends an auxiliary node release request to the source auxiliary node.

Step 1402: the source auxiliary node sends an auxiliary node request knowledge message carrying UE model information to the main node. In one implementation, for example, the message may be the aforementioned second message including UE model information.

Step 1403: and the master node makes UE model management decisions according to the received UE model information.

Step 1404: the master node sends an RRC reconfiguration message to the UE carrying the UE model management decisions. In one implementation, for example, the message may be the fourth message described above including the UE model management decision.

Step 1405: the UE sends an RRC reconfiguration complete message to the master node.

Step 1406: and the master node sends an auxiliary node reconfiguration completion message to the target auxiliary node.

Step 1407: and the UE and the target auxiliary node perform a random access process.

If the UE model management decision in step 1403 requires model forwarding, steps 1408 and 1409 are performed.

Step 1408: the master node sends a model forwarding request message to the source and the auxiliary nodes. In one implementation, for example, the message may be the fifth message described above that includes the model forwarding request.

Step 1409: the source and the auxiliary nodes forward the message comprising the model to the main node based on the received model forwarding request. In one implementation, for example, the message may be the sixth message described above that includes the model.

If the UE model information in step 1402 includes information indicating that there is a model that has not been downloaded, and/or the master node decides to distribute the model to the UE, step 1410 is performed.

Step 1410: the master node sends a message to the UE including the model. In one implementation, for example, the message may be the sixth message described above that includes the model.

Step 1408 and step 1409 may precede step 1404, step 1405, step 1406, step 1407 or be performed simultaneously with step 1404, step 1405, step 1406, step 1407.

Fig. 15 illustrates a schematic diagram of one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure. Specifically, fig. 15 shows that in the dual-connectivity mobile scenario, the UE reports UE model information to provide reference information for the entity to make UE model management decisions, so that the UE may acquire and apply UE model management decisions made by the entity to the UE, so as to ensure validity of model issuing and/or training and/or reasoning of the UE, and reduce unnecessary model issuing and/or training and/or reasoning.

Step 1500: and the main node, the source auxiliary node and the target auxiliary node perform a target auxiliary node adding process.

Step 1501: and the master node sends an auxiliary node release request to the source auxiliary node.

Step 1502: the source and secondary nodes send secondary node request awareness messages to the primary node.

Step 1503: the master node sends an RRC reconfiguration message to the UE.

Step 1504: and the UE sends an RRC reconfiguration completion message carrying UE model information to the master node. In one implementation, for example, the message may be the aforementioned second message including UE model information.

Step 1505: and the master node sends an auxiliary node reconfiguration completion message carrying the UE model information to the target auxiliary node. In one implementation, for example, the message may be the aforementioned second message including UE model information.

Step 1506: and the UE and the target auxiliary node perform a random access process.

Step 1507: and the target auxiliary node makes UE model management decisions according to the received UE model information.

Step 1508: the target secondary node sends a message to the UE including the UE model management decision to inform the UE of the UE model management decision for it. In one implementation, for example, the message may be the fourth message described above including the UE model management decision.

Step 1507 may precede step 1506 or be performed concurrently with step 1506.

Fig. 16 illustrates a schematic diagram of one aspect of supporting wireless communication network data collection in accordance with an embodiment of the disclosure. Specifically, fig. 16 shows that in a dual-connectivity mobile scenario, the UE reports UE model information to provide reference information for the entity to make UE model management decisions, so that the UE may acquire and apply UE model management decisions made by the entity to the UE, so as to ensure validity of model issuing and/or training and/or reasoning of the UE, and reduce unnecessary model issuing and/or training and/or reasoning.

Step 1600: and the main node, the source auxiliary node and the target auxiliary node perform a target auxiliary node adding process.

Step 1601: and the master node sends an auxiliary node release request to the source auxiliary node.

Step 1602: the source and secondary nodes send secondary node request awareness messages to the primary node.

Step 1603: the master node sends an RRC reconfiguration message to the UE.

Step 1604: and the UE sends an RRC reconfiguration completion message carrying UE model information to the master node. In one implementation, for example, the message may be the aforementioned second message including UE model information.

Step 1605: and the master node sends an auxiliary node reconfiguration completion message to the target auxiliary node.

Step 1606: and the UE and the target auxiliary node perform a random access process.

Step 1607: and the master node makes UE model management decisions according to the received UE model information.

Step 1608: the master node sends a message to the UE including the UE model management decision to inform the UE of the UE model management decision for it. In one implementation, for example, the message may be the fourth message described above including the UE model management decision.

Steps 1607 and 1608 may precede steps 1605 and 1606 or be performed concurrently with steps 1605 and 1606.

Fig. 17 illustrates a schematic diagram of one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure. Specifically, fig. 17 illustrates a process in which an entity notifies a UE of a UE model management decision in a mobile scenario, and notifies the UE of the model management decision of the entity to the UE, so as to ensure validity of model issuing and/or training and/or reasoning of the UE, and reduce unnecessary model issuing and/or training and/or reasoning. In one implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB, and the second entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB.

Step 1701: the second entity sends a handover request for the UE to the first entity.

Step 1702: the first entity replies to the second entity with knowledge of the handoff request.

Step 1703: the second entity makes a UE model management decision for the UE. The second entity sends an RRC reconfiguration message carrying the UE model management decisions to the UE to inform the UE of the UE model management decisions for it. In one implementation, for example, the message may be the fourth message described above including the UE model management decision.

Step 1704: the UE sends an RRC reconfiguration complete message to the first entity.

Fig. 18 illustrates a schematic diagram of one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure. Specifically, fig. 18 shows that in a mobile scenario, in a handover process based on NG, the entities interact with UE model information to provide reference information for UE model management decisions, so that the UE can acquire and apply UE model management decisions made by the entities to the UE, so as to ensure validity of model issuing and/or training and/or reasoning of the UE, and reduce unnecessary model issuing and/or training and/or reasoning.

Step 1801: the source node sends a handover required message carrying UE model information to the AMF. In one implementation, for example, the message may be the aforementioned second message including UE model information.

Step 1802: the AMF sends a switching request message carrying UE model information to a target node. In one implementation, for example, the message may be the aforementioned second message including UE model information.

Step 1803: the target node sends a handover request awareness message to the AMF carrying the UE model management decisions. In one implementation, for example, the message may be the fourth message described above including the UE model management decision.

Step 1804: the AMF sends a handover command message carrying the UE model management decisions to the source node. In one implementation, for example, the message may be the fourth message described above including the UE model management decision.

Step 1805: the source node sends a handover command message carrying the UE model management decisions to the UE to inform the UE of the UE model management decisions for it. In one implementation, for example, the message may be the fourth message described above including the UE model management decision.

Step 1806: and the UE performs a random access process with the target node.

If the UE model management decisions in step 1803 and step 1804 require model forwarding, then step 1807a or step 1807b is performed.

Step 1807a: the source secondary node forwards a message including the model to the target secondary node based on the received UE model management decision. In one implementation, for example, the message may be the sixth message described above that includes the model.

Step 1807b: the source auxiliary node forwards the message comprising the model to the target auxiliary node through the AMF based on the received UE model management decision. In one implementation, for example, the message may be the sixth message described above that includes the model.

Step 1807a and/or step 1807b may precede step 1805 and/or step 1806 or be concurrent with step 1805 and/or step 1806.

Fig. 19 illustrates a schematic diagram of one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure. Specifically, fig. 19 shows a process of interacting the computing force information between entities to send a computing force information report request message to a second entity. After receiving the message, the second entity needs to report the calculation information to the first entity according to the calculation information reporting request, so that the first entity can acquire the calculation information of the second entity to ensure the performance of the subsequent network and/or UE. In one implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB, and the second entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB. In another implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB, and the second entity may be a UE. In yet another implementation, for example, the first entity may be an AMF or SMF or MME and the second entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB. In yet another implementation, for example, the first entity may be a gNB CU and the second entity may be a gNB DU. In yet another implementation, for example, the first entity may be a gNB CU-CP and the second entity may be a gNB CU-UP.

Step 1901: the first entity sends the calculation force information reporting request message to the second entity, so that the second entity can report the calculation force information according to the request. In one implementation, for example, the request message may be the eighth message described above including the calculation information reporting request.

Step 1902: the second entity sends a message including the computing power information in response to the computing power information reporting request. In one implementation, for example, the message may be the ninth message including the calculation information reporting response, or may be the tenth message including the calculation information. If the second entity cannot report the calculation force information according to the request, a message including failure of reporting the calculation force information is sent to the first entity and step 1903 is not performed. In one implementation, for example, the message may be the eleventh message described above including the loss of computing power information reporting information.

If periodic reporting is required in the request message in step 1901, reporting in step 1903 and later is performed. If the request message in step 1901 requires on-demand reporting, reporting in step 1903 and later is not performed. If the request message in step 1901 requires on-demand reporting, step 1902 may be a ninth message including a calculation information reporting response, step 1903 may be a tenth message including calculation information, and reporting after step 1903 is not continued.

Step 1903: the second entity sends a message including the computing power information to the first entity. In one implementation, for example, the message may be the tenth message described above including the computing force information.

Fig. 20 illustrates a schematic diagram of one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure. Specifically, fig. 20 shows a process of interaction of the computing power information between the entities according to the self situation, specifically, the second entity sends a message including the reporting of the computing power information to the first entity according to the self situation, so that the first entity can acquire the computing power information of the second entity, so as to ensure the performance of the subsequent network and/or UE. In one implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB, and the second entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB. In another implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB, and the second entity may be a UE. In yet another implementation, for example, the first entity may be an AMF or SMF or MME and the second entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB. In yet another implementation, for example, the first entity may be a gNB CU and the second entity may be a gNB DU. In yet another implementation, for example, the first entity may be a gNB CU-CP and the second entity may be a gNB CU-UP.

Step 2001: the second entity sends a message comprising the calculation information. In one implementation, for example, the message may be the tenth message described above including the computing force information.

Fig. 21 is a flowchart 2100 illustrating a method of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure.

Step 2101: a message including information related to network data collection is received from a second entity.

It should be appreciated that there is also provided herein a first entity and a second entity comprising a processor and a transceiver, wherein the processors of the first entity and the second entity are coupled to the transceiver and configured to perform the methods, steps and operations described above with reference to fig. 3-21.

Fig. 22 illustrates a schematic diagram of one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure. Specifically, fig. 22 shows that in a mobile scenario, an entity issues a UE model in advance, and when the UE is connected to an applicable entity, the entity to which the model is applicable sends a model management decision, so that the UE can use a related model in time, and the model use delay caused by the model issue is reduced, thereby guaranteeing the performance of the network and the UE. In one implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or gNB-CU or en-gNB or eNB or ng-eNB, and the second entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or gNB-CU or en-gNB or eNB or ng-eNB.

Step 2201: the second entity sends a message to the UE including the model. In one implementation, for example, the message may be the sixth message described above that includes the model. If the model is issued in step 2201, that is, the UE downloads the model, the model is already downloaded, and thus the model may be in an inactive state or an active state after being issued. If the second entity is not the applicable entity of the model, the secondary model issuing is an advanced model issuing, and the model is in an inactive state after issuing.

Step 2202: the second entity sends UE model information to the first entity in a handover request message for the UE to inform the first entity of the UE model information of the UE. In one implementation, for example, the message may be the aforementioned second message including UE model information.

Step 2203: the first entity sends a handover request awareness message to the second entity.

Step 2204: the second entity sends an RRC reconfiguration message to the UE.

Step 2205: the UE sends an RRC reconfiguration complete message to the first entity.

Step 2206: the first entity makes a UE model management decision on a model of the UE. The first entity sends a message to the UE including the UE model management decision to inform the UE of the UE model management decision for it. In one implementation, for example, the message may be the fourth message described above including the UE model management decision. If the first entity is the applicable entity that issued the model in step 2201, then the UE model management decision in step 2206 may be to activate the model.

Fig. 23 illustrates a schematic diagram of one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure. Specifically, fig. 23 shows that in a mobile scenario, an entity issues and sends a UE model management decision in advance to notify a UE, and when the UE is connected to an applicable entity, the entity to which the model is applicable sends the model management decision, so that the UE can use a related model in time, and the model use time delay caused by the model issue is reduced, thereby guaranteeing the performance of the network and the UE. In one implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB, and the second entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB.

Step 2301: the second entity sends a message to the UE including the model. In one implementation, for example, the message may be the sixth message described above that includes the model. If the model is issued in step 2201, that is, the UE finishes downloading the model, the model is already downloaded, so the model may be in an inactive state or an active state after being issued. If the second entity is not the applicable entity of the model, the secondary model issuing is an advanced model issuing, and the model is in an inactive state after issuing.

Step 2302: the second entity makes a UE model management decision on the model of the UE. The second entity sends a message to the UE including the UE model management decision to inform the UE of the UE model management decision for it. In one implementation, for example, the message may be the fourth message described above including the UE model management decision. If the second entity is not the applicable entity that issued the model in step 2301, then the UE model management decision in step 2302 may configure the UE with the conditions for model activation.

Step 2303: the second entity sends UE model information to the first entity in a handover request message for the UE to inform the first entity of the UE model information of the UE. In one implementation, for example, the message may be the aforementioned second message including UE model information.

Step 2304: the first entity sends a handover request awareness message to the second entity.

Step 2305: the second entity sends an RRC reconfiguration message to the UE.

Step 2306: the UE sends an RRC reconfiguration complete message to the first entity.

Step 2307: if the model activation condition configured by the entity for the UE in step 2302 is satisfied, the UE activates the model, and further performs training and/or reasoning of the model.

Step 2307 may be performed prior to and/or concurrently with step 2303, step 2304, step 2305, step 2306.

Fig. 24 illustrates a schematic diagram of one aspect of supporting wireless communication network data collection in accordance with an embodiment of the present disclosure. Specifically, fig. 7 illustrates a process of interaction model forwarding requests and models between entities, so that the entities may acquire the models to ensure performance of subsequent networks and/or UEs. In one implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB, and the second entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB. In another implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB, and the second entity may be a UE. In yet another implementation, for example, the first entity may be an AMF or SMF or MME and the second entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB. In yet another implementation, for example, the first entity may be a gNB or gNB CU-CP or gNB CU or gNB DU or en-gNB or eNB or ng-eNB, and the second entity may be an AMF or SMF or MME. In yet another implementation, for example, the first entity may be a gNB CU and the second entity may be a gNB DU. In yet another implementation, for example, the first entity may be a gNB DU and the second entity may be a gNB CU. In yet another implementation, for example, the first entity may be a gNB CU-CP and the second entity may be a gNB CU-UP. In yet another implementation, for example, the first entity may be a gNB CU-UP and the second entity may be a gNB CU-CP.

Step 2401: the first entity sends a message to the second entity that includes the model. In one implementation, for example, the message may be the sixth message described above that includes the model. If the current situation does not lend itself to the use of the model, the model may be in an inactive state.

Step 2402: the first entity makes a UE model management decision and the first entity sends the UE model management decision to the second entity. In one implementation, for example, the message may be the fourth message described above including the UE model management decision. If the model issued in step 2401 is in an inactive state, the model may be activated using the message in step 2402 when the current conditions are appropriate for training and/or reasoning with the model issued in step 2401.

Step 2403: the second entity applies and/or forwards the UE model management decisions.

The various illustrative logical blocks, modules, and circuits described herein may be implemented or performed with a general purpose processor, a digital signal processor (Digital Signal Processor, DSP), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

The steps of a method or algorithm described in connection with the disclosure herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.

In one or more exemplary designs, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

The description set forth herein describes example configurations, methods, and apparatus in connection with the accompanying drawings and is not intended to represent all examples that may be implemented or are within the scope of the claims. The term "exemplary" as used herein means "serving as an example, instance, or illustration," rather than "preferred" or "advantageous over other examples. The detailed description includes specific details for the purpose of providing an understanding of the described technology. However, the techniques may be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form in order to avoid obscuring the concepts of the described examples.

Although this description contains many specific implementation details, these should not be construed as limitations on the scope of any invention or of what may be claimed, but rather as descriptions of features specific to particular embodiments of particular inventions. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Furthermore, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

It should be understood that the specific order or hierarchy of steps in the methods of the present invention is an illustration of exemplary processes. Based on design preferences, it is understood that the specific order or hierarchy of steps in the methods may be rearranged to achieve the functions and effects disclosed in the present invention. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented, unless otherwise specifically recited. Furthermore, although elements may be described or claimed in the singular, the plural is contemplated unless limitation to the singular is explicitly stated. Accordingly, the present disclosure is not limited to the examples shown, and any means for performing the functions described herein are included in aspects of the present disclosure.

The description and drawings are provided by way of example only to assist the reader in understanding the present disclosure. They are not intended, nor should they be construed, to limit the scope of the present disclosure in any way. While certain embodiments and examples have been provided, it will be apparent to those of ordinary skill in the art from this disclosure that variations may be made to the embodiments and examples shown without departing from the scope of the disclosure.

Claims

1. A method performed by a first entity in a wireless communication network, the method comprising:

a message including information related to network data collection is received from a second entity.

2. The method according to claim 1,

wherein receiving a message from the second entity comprising information related to the collection of network data comprises:

a second message including UE model information is received from a second entity.

3. The method according to claim 2,

wherein receiving a message from the second entity comprising information related to the collection of network data further comprises:

before receiving a second message comprising UE model information from the second entity, sending a first message comprising a user equipment UE model information request to the second entity,

wherein the first message includes one or more of:

a UE identity;

the application range of the content of the first message;

switching time;

reporting the request identifier by the UE model information;

reporting a registration request;

reporting the time interval;

reporting time;

information reporting type;

information reporting period;

reporting trigger condition configuration; and

content needs to be reported; and is also provided with

Wherein the reporting content includes one or more of the following:

Numbering and/or numbering list of models;

the name of the model;

use of the model;

the state of the model;

model integrity status;

the status of the model that did not complete the download;

downloading an address of the model;

model download ratio;

suggested actions;

suggested actions for the model that did not download;

model accuracy;

model activation conditions;

model deactivation conditions;

model activation time;

model deactivation time;

reasoning about content reporting conditions;

and wherein the inferential content reporting conditions include one or more of:

reasoning the report type of the content;

reasoning a content reporting period;

reporting triggering conditions by reasoning content;

the reported reasoning content;

requesting the reporting and/or the applicable time of the reported reasoning content;

accuracy.

4. A method according to any of claims 2 or 3, wherein the second message comprises one or more of:

a UE identity;

the application range of the content of the second message;

the requested content may be reported for confirmation;

triggering conditions;

model information content;

and wherein the model information content includes one or more of:

numbering and/or numbering list of models;

The name of the model;

use of the model;

the state of the model;

model integrity status;

the status of the model that did not complete the download;

suggested actions;

suggested actions for the model that did not download;

model accuracy;

downloading an address of the model;

model download ratio;

model activation conditions;

model deactivation conditions;

model activation time;

model deactivation time;

reasoning about content reporting conditions;

reasoning the report type of the content;

reasoning a content reporting period;

reporting triggering conditions by reasoning content;

the reported reasoning content;

the applicable time of the reported reasoning content;

accuracy.

5. The method according to claim 1,

a fourth message including a UE model management decision is received from the second entity,

wherein the fourth message includes one or more of:

a UE identity;

the application range of the content of the fourth message;

model management decision-making;

and wherein the model management decision comprises one or more of:

Numbering and/or numbering list of models;

the name of the model;

use of the model;

the state of the model;

the status of the model that did not complete the download;

decision making for the model;

decision making for model not yet downloaded;

a list of activated models;

a model activation indication;

a model deactivation indication;

model activation time;

model deactivation time;

model activation conditions;

model deactivation conditions;

forwarding strategies applicable to the downloaded model are completed;

a model forwarding strategy applicable to the model which is not downloaded;

model forwarding ratio;

reporting the reasoning content to make a decision;

and wherein the inferential content reporting decision comprises one or more of:

reasoning the report type of the content;

reasoning a content reporting period;

reporting triggering conditions by reasoning content;

the reported reasoning content;

the applicable time of the reported reasoning content;

requesting the reported reasoning content;

the applicable time of the reasoning content requested to be reported;

accuracy.

6. The method according to claim 1,

a sixth message including the UE model is received from the second entity.

7. The method according to claim 6, wherein the method comprises,

wherein receiving a message from the second entity comprising information related to the collection of network data further comprises: before receiving a sixth message including the UE model from the second entity, sending a fifth message including a UE model forwarding request to the second entity,

wherein the fifth message includes one or more of the following:

a UE identity;

the application range of the content of the fifth message;

switching time;

the model forwards the request identification;

the model forwards the registration request;

model forwarding time intervals;

model forwarding time;

model forwarding ratio;

model forwarding type;

configuring the model forwarding trigger condition;

downloading an address of the model;

model download ratio;

content needs to be forwarded;

and wherein the forwarding content includes one or more of:

numbering and/or numbering list of models;

the name of the model;

use of the model;

the state of the model;

model accuracy;

the type of model;

characteristic parameters of the model;

the input parameter type of the model;

input parameters of the model define conditions;

the output parameter type of the model;

the input parameter preprocessing method of the model;

the post-processing method of the output parameters of the model;

The model infers the applicable time of the content.

8. The method of any of claims 6 or 7, wherein the sixth message comprises one or more of:

a UE identity;

application scope of the content of the sixth message

A confirmation that the requested content is forwardable;

model download ratio;

model forwarding ratio;

the model forwards the triggering condition;

forwarding the content;

issuing content;

and wherein the forwarding content includes one or more of:

numbering and/or numbering list of models;

the name of the model;

use of the model;

the state of the model;

model accuracy;

the type of model;

characteristic parameters of the model;

the input parameter type of the model;

input parameters of the model define conditions;

the output parameter type of the model;

the input parameter preprocessing method of the model;

the post-processing method of the output parameters of the model;

the model infers the applicable time of the content,

the delivery includes one or more of the following:

numbering and/or numbering list of models;

the name of the model;

use of the model;

the state of the model;

model accuracy;

the type of model;

characteristic parameters of the model;

the input parameter type of the model;

Input parameters of the model define conditions;

the output parameter type of the model;

the input parameter preprocessing method of the model;

the output parameter post-processing method of the model.

9. The method according to claim 1,

a tenth message including the computing force information is received from the second entity.

10. The method according to claim 1,

transmitting an eighth message including information for requesting calculation of power to the second entity;

a ninth message including a response to the eighth message or a tenth message including calculation information is received from the second entity,

wherein the eighth message includes one or more of the following:

the application range of the content of the eighth message;

a prediction mark;

predicting a registration request;

a registration request;

reporting the time interval;

reporting time;

predicting an information reporting time interval;

predicting information reporting time;

the prediction result application time of the prediction information;

the calculation force information reporting type;

calculating a force information reporting period;

reporting the calculation force information and configuring the triggering condition;

Predicting the type of reporting the power information;

predicting a force information reporting period;

the configuration of triggering conditions is reported by the predicted calculation force information;

the calculation force information content needs to be reported;

the content of the predictive calculation power information needs to be reported,

wherein the ninth message includes one or more of the following:

the application range of the content of the ninth message;

the requested content may be reported for confirmation;

the requested predicted content may be reported for confirmation;

reporting the calculation force information to trigger conditions;

the triggering condition is reported by the predicted calculation force information;

reporting the calculation force information;

the report content of the power information is predicted;

the accuracy of the force information is predicted;

the application time of the force information is predicted.

11. The method of any of claims 9 or 10, wherein the tenth message comprises one or more of:

the application range of the content of the tenth message;

reporting the calculation force information to trigger conditions;

reporting the calculation force information;

the report content of the power information is predicted;

the accuracy of the force information is predicted;

the application time of the force information is predicted.

12. A method performed by a second entity in a wireless communication network, the method comprising:

A message including information related to the collection of network data is sent to the first entity.

13. The method of claim 12, wherein the message comprising information related to network data collection comprises one of:

a message comprising user equipment, UE, model information;

a message comprising a UE model management decision;

a message including a UE model;

the method comprises the steps of responding to a message of a calculation force information reporting request; and

a message including calculation force information.

14. A first entity in a wireless communication network, the first entity comprising:

a transceiver; and

a processor coupled to the transceiver and configured to perform the method of any of claims 1-11.

15. A second entity in a wireless communication network, the second entity comprising:

a transceiver; and

a processor coupled with the transceiver and configured to perform the method of any of claims 12-13.