WO2024093498A1 - 一种数据处理方法和通信装置 - Google Patents

一种数据处理方法和通信装置 Download PDF

Info

Publication number
WO2024093498A1
WO2024093498A1 PCT/CN2023/116651 CN2023116651W WO2024093498A1 WO 2024093498 A1 WO2024093498 A1 WO 2024093498A1 CN 2023116651 W CN2023116651 W CN 2023116651W WO 2024093498 A1 WO2024093498 A1 WO 2024093498A1
Authority
WO
WIPO (PCT)
Prior art keywords
mdt
network device
data
access network
core network
Prior art date
Application number
PCT/CN2023/116651
Other languages
English (en)
French (fr)
Inventor
程雯洁
曾宇
耿婷婷
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2024093498A1 publication Critical patent/WO2024093498A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic

Definitions

  • the present application relates to the field of communication technology, and in particular to a data processing method and a communication device.
  • MDT drive-tests
  • UE user equipment
  • MDT data can be used to detect and optimize problems and faults in wireless networks.
  • the MDT data reported by the UE is transparently transmitted to the trace collection entity (TCE), and the application scenarios of the MDT data are limited.
  • TCE trace collection entity
  • the embodiments of the present application provide a data processing method and a communication device, which are used for an access network device to obtain MDT data rights.
  • an embodiment of the present application provides a data processing method, which is applied to a core network device, and the method includes: determining the minimized drive test (MDT) data authority assigned to an access network device; and sending a first message to the access network device, wherein the first message is used to indicate the MDT data authority.
  • MDT minimized drive test
  • the core network device determines the MDT data authority assigned to the access network device, and then the core network device sends the first message to the access network device, wherein the first message is used to indicate the MDT data authority. Since the access network device can obtain the MDT data authority assigned to the access network device by the core network device, the access network device has the MDT data authority, which expands the application scenario of the MDT data.
  • the first information includes: indication information of the terminal device executing MDT.
  • the core network device sends indication information of the terminal device executing MDT to the access network device, so that the access network device can obtain MDT data for the terminal device indicated in the indication information.
  • the first information includes: indication information of an MDT type; the MDT type includes at least one of the following: immediate MDT and non-immediate MDT.
  • the first information includes: MDT usage information; the MDT usage information is used to indicate that the MDT data is applied inside the access network device, or to indicate that the MDT data is applied inside the access network device and to indicate that the access network device transmits the MDT data to other access network devices.
  • the access network device can use the MDT data according to the MDT usage information to achieve the correct use of the MDT data and avoid the risk of MDT data leakage.
  • the first information includes: an identifier of a terminal device executing MDT, an MDT measurement item, and an MDT data authority corresponding to the MDT measurement item.
  • the access network device can obtain MDT data corresponding to the MDT measurement item for the UE indicated in the first information.
  • the method further includes: receiving an MDT data request sent by the access network device according to the MDT data authority; and sending a response corresponding to the MDT data request to the access network device, the response including: MDT data.
  • the core network device can send MDT data to the access network device, so that the access network device has the ability to use MDT data.
  • the MDT data includes: non-immediate MDT data of a terminal device in a non-connected state cached by the core network device, and/or immediate MDT data sent multiple times by a terminal device in a connected state to the core network device.
  • the method further includes: receiving a first request from the access network device, the first request being used to request the MDT data permission from the core network device.
  • the access network device can request the core network device to allocate the MDT data permission, so that the access network device can flexibly request the required MDT data permission.
  • the method further includes: receiving a second request from the access network device, the second request Used to request the core network device to modify the MDT data authority; modify the MDT data authority assigned to the access network device according to the second request; send a second message to the access network device, the second message being used to indicate the modified MDT data authority.
  • the access network device parses the second message and can obtain the modified MDT data authority assigned to the access network device by the core network device, so that the access network device has the modified MDT data authority, solving the problem that the access network device cannot update the MDT data authority, so that the MDT data corresponding to the modified MDT data authority can be obtained by using the modified MDT data authority.
  • the second information includes: indication information of a terminal device that performs MDT.
  • the indication information of the terminal device includes at least one of the following: a terminal device selection ratio, a terminal device identification list, and a terminal device screening condition; or, when the MDT is a signaling-based MDT, the indication information of the terminal device includes: the identification of the terminal device.
  • the method further includes: receiving a third request from the access network device, the third request being used to request the core network device to modify the MDT configuration; and sending third information to the access network device, the third information including the modified MDT configuration.
  • the access network device parses the third information and can obtain the modified MDT configuration assigned to the access network device by the core network device, thereby solving the problem that the access network device cannot update the MDT data, and using the modified MDT configuration can obtain the MDT data corresponding to the modified MDT configuration.
  • the modified MDT configuration includes: a modified triggering condition corresponding to the MDT measurement item and/or a modified configuration parameter corresponding to the MDT measurement item.
  • the configuration parameters include: the measurement period of the MDT measurement item, and/or, the MDT event triggering configuration parameters of the MDT measurement item; or, when the MDT is non-immediate MDT, the configuration parameters include at least one of the following: the measurement interval of the MDT measurement item, the measurement duration of the MDT measurement item, or, the MDT event triggering configuration parameters of the MDT measurement item.
  • the core network device can modify the triggering condition of the MDT measurement item, thereby changing the triggering condition for the UE to execute MDT by modifying the triggering condition.
  • the core network device can modify one or more configuration parameters of the MDT measurement items, so that the access network device can obtain the modified triggering condition and the modified configuration parameters of the MDT measurement item.
  • the modified trigger condition includes an added or deleted trigger condition.
  • the embodiment of the present application also provides a data processing method, which is applied to an access network device, and the method includes: receiving a first message from a core network device; and obtaining a minimized drive test (MDT) data permission assigned to the access network device according to the first message.
  • MDT minimized drive test
  • the core network device determines the MDT data permission assigned to the access network device, and then the core network device sends a first message to the access network device, and the first message is used to indicate the MDT data permission. Since the access network device can obtain the MDT data permission assigned to the access network device by the core network device, the access network device has the MDT data permission, which expands the application scenario of the MDT data.
  • the method further includes: acquiring MDT data according to the MDT data authority.
  • the access network device can use the MDT data authority, that is, the access network device has the ability to acquire MDT data, and the access network device can acquire the MDT data corresponding to the MDT data authority.
  • the acquiring of MDT data according to the MDT data authority includes: sending an MDT data request to the core network device according to the MDT data authority; and receiving a response corresponding to the MDT data request from the core network device, the response including: MDT data.
  • the core network device can send MDT data to the access network device, so that the access network device has the ability to use the MDT data.
  • the MDT data includes: non-immediate MDT data of a terminal device in a non-connected state cached by the core network device, and/or immediate MDT data sent multiple times by a terminal device in a connected state to the core network device.
  • the acquiring of MDT data according to the MDT data authority includes: receiving an MDT measurement report sent by a terminal device according to the MDT data authority, wherein the MDT measurement report includes: MDT data.
  • the terminal device can send MDT data to the access network device, so that the access network device has the ability to use the MDT data.
  • the MDT data permission includes: MDT usage information
  • the MDT usage information is used to instruct the access network device to transmit the MDT data to other access network devices
  • the method further includes: transmitting the MDT data to other access network devices.
  • the access network device can use the MDT data according to the MDT usage information to achieve the correct use of the MDT data and avoid the risk of MDT data leakage.
  • the first information includes: indication information of the MDT type; the MDT type includes at least the following: One: immediate MDT and non-immediate MDT.
  • the first information includes: an identifier of a terminal device executing MDT, an MDT measurement item, and an MDT data authority corresponding to the MDT measurement item.
  • the method further includes: sending a first request to the core network device, the first request being used to request the MDT data permission from the core network device.
  • the access network device can request the core network device to allocate the MDT data permission, so that the access network device can flexibly request the required MDT data permission.
  • the method further includes: sending a second request to the core network device, the second request being used to request the core network device to modify the MDT data authority; receiving second information from the core network device; and obtaining the modified MDT data authority assigned to the access network device according to the second information.
  • the access network device parses the second information and can obtain the modified MDT data authority assigned to the access network device by the core network device, so that the access network device has the modified MDT data authority, which solves the problem that the access network device cannot update the MDT data authority, so that the MDT data corresponding to the modified MDT data authority can be obtained using the modified MDT data authority.
  • the method further includes: sending a third request to the core network device, the third request being used to request the core network device to modify the MDT configuration; receiving third information from the core network device; and obtaining the modified MDT configuration according to the third information.
  • the access network device parses the third information and can obtain the modified MDT configuration assigned to the access network device by the core network device, thereby solving the problem that the access network device cannot update the MDT data.
  • the MDT data corresponding to the modified MDT configuration can be obtained by using the modified MDT configuration.
  • the modified MDT configuration includes: a modified triggering condition corresponding to the MDT measurement item and/or a modified configuration parameter corresponding to the MDT measurement item.
  • the configuration parameter when the MDT is immediate MDT, includes: a measurement period of the MDT measurement item, and/or an MDT event triggering configuration parameter of the MDT measurement item; or, when the MDT is non-immediate MDT, the configuration parameter includes at least one of the following: a measurement interval of the MDT measurement item, a measurement duration of the MDT measurement item, or an MDT event triggering configuration parameter of the MDT measurement item.
  • an embodiment of the present application further provides a communication device, wherein the communication device is a core network device, including:
  • a processing module used for determining the Minimized Drive Test (MDT) data authority allocated to the access network device
  • the sending module is used to send first information to the access network device, where the first information is used to indicate the MDT data authority.
  • the constituent modules of the communication device may also execute the steps described in the aforementioned first aspect and various possible implementations, see the aforementioned description of the first aspect and various possible implementations for details.
  • an embodiment of the present application further provides a communication device, wherein the communication device is a core network device, including:
  • a receiving module used for receiving first information from a core network device
  • the processing module is configured to obtain, according to the first information, the Minimization of Drive Tests (MDT) data authority allocated to the access network device.
  • MDT Minimization of Drive Tests
  • the constituent modules of the communication device may also execute the steps described in the aforementioned second aspect and various possible implementations, see the aforementioned description of the second aspect and various possible implementations for details.
  • an embodiment of the present application provides a computer-readable storage medium, wherein instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium is run on a computer, the computer executes the method described in the first aspect or the second aspect above.
  • an embodiment of the present application provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the method described in the first aspect or the second aspect above.
  • an embodiment of the present application provides a communication device, which may include entities such as a core network device or an access network device or a chip, and the communication device includes: a processor, a memory; the memory is used to store instructions; the processor is used to execute the instructions in the memory, so that the communication device executes a method as described in any one of the first or second aspects above.
  • the present application provides a chip system, which includes a processor for supporting a core network device or an access network device to implement the functions involved in the above aspects, for example, sending or processing the data and/or information involved in the above methods.
  • the chip system also includes a memory, which is used to store program instructions and data necessary for the core network device or the access network device.
  • the chip system can be composed of chips, or it can include chips and other discrete devices.
  • the present application provides a data processing system, the system comprising: a core network device as described in any one of the third aspects and an access network device as described in any one of the fourth aspects.
  • the core network device determines the MDT data authority assigned to the access network device, and then the core network device sends first information to the access network device, and the first information is used to indicate the MDT data authority. Since the access network device can obtain the MDT data authority assigned to the access network device by the core network device, the access network device has the MDT data authority, which expands the application scenario of the MDT data.
  • FIG1 is a schematic diagram of a system scenario in which a data processing method provided in an embodiment of the present application is applied;
  • FIG2 is a schematic diagram of a structure of an access network device provided in an embodiment of the present application.
  • FIG3 is a schematic diagram of an embodiment of a data processing method provided in an embodiment of the present application.
  • FIG4 is a schematic diagram of another embodiment of a data processing method provided in an embodiment of the present application.
  • FIG5 is a schematic diagram of another embodiment of a data processing method provided in an embodiment of the present application.
  • FIG6 is a schematic diagram of another embodiment of a data processing method provided in an embodiment of the present application.
  • FIG7 is a schematic diagram of another embodiment of a data processing method provided in an embodiment of the present application.
  • FIG8a is a schematic diagram of another embodiment of a data processing method provided in an embodiment of the present application.
  • FIG8b is a schematic diagram of another embodiment of the data processing method provided in an embodiment of the present application.
  • FIG9 is a schematic diagram of another embodiment of a data processing method provided in an embodiment of the present application.
  • FIG10 is a schematic diagram of a structure of a communication device provided in an embodiment of the present application.
  • FIG11 is another schematic diagram of the structure of a communication device provided in an embodiment of the present application.
  • FIG. 12 is a schematic diagram of the structure of a data processing system provided in an embodiment of the present application.
  • the embodiments of the present application provide a data processing method and a communication device, which are used for an access network device to obtain MDT data rights.
  • NR new radio
  • LTE long term evolution
  • FDD frequency division duplex
  • TDD LTE time division duplex
  • UMTS universal mobile telecommunication system
  • 6G mobile communication system for example, 6G mobile communication system
  • V2X vehicle to everything
  • the communication system to which the present application is applicable includes a core network device, an access network device, and a terminal device.
  • the access network device may include a network device, and the core network device and the access network device communicate and transmit via a wired or wireless manner, and the access network device and the terminal device may communicate and transmit using a beam.
  • the core network equipment, network equipment and terminal equipment of this application are introduced below.
  • the system architecture of the data processing method of the embodiment of the present application may include: a core network (CN) device 10, an access network device 20 and a terminal device 30.
  • CN core network
  • the core network device 10 can be connected to the access network device 20.
  • the core network device 10 can specifically be an LTE core network device, or a 5G core network device, etc.
  • the core network device 10 can specifically include: an access and mobility management function (AMF) entity, or the core network device 10 can specifically include: a mobility management entity (MME).
  • the core network device 10 has the ability to allocate and manage minimization of drive test (MDT) data permissions.
  • MDT data refers to the data in the MDT measurement report generated after the terminal device 30 executes MDT.
  • the core network device 10 is specifically an AMF entity (hereinafter referred to as AMF) for example.
  • AMF AMF entity
  • the access network device 20 may be a device in a wireless network, and the access network device 20 may obtain the MDT data authority from the core network device 10, thereby using the MDT data authority to obtain the MDT data.
  • the access network device 20 may be a device deployed in a wireless access network to provide wireless communication functions for terminal devices.
  • the access network device 20 may be a radio access network (RAN) node that connects the terminal device to the wireless network, and the access network device 20 may also be referred to as a network device.
  • RAN radio access network
  • the access network device involved in the embodiments of the present application may be an access network device in a RAN (such as a gNB, eNB), etc., or may be a device having some or all of the functions of an access network device, for example, the access network device 20 includes a centralized unit (CU) and/or a distributed unit (DU).
  • a centralized unit CU
  • DU distributed unit
  • FIG. 2 a schematic diagram of the structure of an access network device provided in an embodiment of the present application.
  • the access network device adopts a separate architecture of CU and DU.
  • CU and DU can be understood as a division of the access network device from a logical function perspective.
  • CU and DU can be physically separated or deployed together.
  • Multiple DUs can share one CU.
  • One DU can also be connected to multiple CUs (not shown in the figure).
  • the CU and DU can be connected through an interface, such as an F1 interface.
  • CU and DU can be divided according to the protocol layer of the wireless network.
  • CU is used to perform the functions of the radio resource control (RRC) layer, the service data adaptation protocol (SDAP) layer, and the packet data convergence protocol (PDCP) layer
  • DU is used to perform the functions of the radio link control (RLC) layer, the media access control (MAC) layer, the physical layer, etc.
  • RRC radio resource control
  • SDAP service data adaptation protocol
  • PDCP packet data convergence protocol
  • DU is used to perform the functions of the radio link control
  • RLC radio link control
  • MAC media access control
  • the physical layer etc.
  • the division of the CU and DU processing functions according to this protocol layer is only an example, and can also be divided in other ways.
  • the CU or DU can be divided into functions with more protocol layers.
  • the CU or DU can also be divided into partial processing functions with protocol layers.
  • the functions of the CU or DU can also be divided according to the service type or other system requirements. For example, by latency, the functions whose processing time meets the latency requirements are set in the DU, and the functions that do not meet the latency requirements are set in the CU.
  • the CU may also have one or more functions of the core network.
  • One or more CUs can be set centrally or separately.
  • the CU can be set on the network side for centralized management.
  • the DU can have multiple radio frequency functions, or the radio frequency functions can be set remotely.
  • the functions of CU can be implemented by one entity or by different entities.
  • the functions of CU can be further divided, for example, the control plane (CP) and the user plane (UP) are separated, that is, the control plane (CU-CP) of CU and the user plane (CU-UP) of CU.
  • CU-CP and CU-UP can be implemented by different functional entities and connected through the E1 interface.
  • the CU-CP and CU-UP can be coupled with DU to jointly complete the functions of the access network device.
  • the control plane CU-CP of CU also includes a further divided architecture, that is, the existing CU-CP is further divided into CU-CP1 and CU-CP2.
  • CU-CP1 includes various wireless resource management functions
  • CU-CP2 only includes RRC functions and PDCP-C functions (that is, the basic functions of control plane signaling at the PDCP layer).
  • the terminal device 30 may be various devices that provide voice and/or data connectivity to the user, and may also be referred to as a terminal, user equipment (UE), mobile station, mobile terminal, etc.
  • the terminal device 30 may be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IOT), virtual reality, augmented reality, industrial control, automatic driving, telemedicine, smart grid, smart furniture, smart office, smart wear, smart transportation, smart city, etc.
  • the terminal device 30 may be a mobile phone, a tablet computer, a computer with wireless transceiver function, a wearable device, aerospace equipment, etc.
  • the chip used in the above-mentioned device may also be referred to as a terminal.
  • UE is used as a terminal device for explanation.
  • the MDT measurement type in the MDT scenario is first described as follows:
  • Signal level measurement The UE measures the signal level of the wireless signal and reports the measurement result to the access network equipment.
  • QoS measurement The access network device performs QoS measurement.
  • the access network device can measure the service flow, service throughput, service delay, etc.
  • the measurement can be performed by the UE.
  • the UE can measure the uplink processing delay.
  • the access network device and the UE can also perform joint processing, such as air interface delay measurement, in which the time from when the data packet passes through the SDAP/PDCP layer of the access network device to when the data packet reaches the SDAP/PDCP layer of the UE is measured.
  • the UE records the information of RRC connection establishment failure and reports it to the access network equipment.
  • MDT includes non-immediate (logged) MDT and immediate (immediate) MDT.
  • MDT includes non-immediate (logged) MDT and immediate (immediate) MDT.
  • loggedMDT is the MDT performed by the UE in idle state or inactive state.
  • loggedMDT is used to measure the strength of the received signal.
  • the access network device configures the UE to perform MDT when it is in idle state or inactive state, when the UE enters the connected state, the UE will no longer continue to perform MDT according to the MDT measurement configuration in the idle state or inactive state.
  • the access network device can configure the MDT measurement to be performed when the UE is in the connected state.
  • immediateMDT is the MDT performed by the UE in the connected state. immediateMDT is used to measure at least one of the UE's data volume, throughput, packet transmission delay, packet loss rate or processing delay.
  • the access network device configures the logged MDT measurement configuration for the UE, such as notifying the logged MDT measurement configuration in an RRC message.
  • the UE enters an idle state or an inactive state, the UE records the corresponding measurement results according to the corresponding logged MDT measurement configuration.
  • the RRC message carries indication information, which indicates the measurement results of the logged MDT currently recorded by the UE.
  • the access network device can send a logged MDT request to the UE, and the UE then reports the measurement results of the logged MDT to the access network device.
  • the access network device can initiate MDT measurement tasks respectively.
  • MDT measurement tasks can be divided into signaling based MDT and management based MDT.
  • the signaling-based MDT refers to the MDT for a specific UE.
  • the access network device receives the instruction information of performing MDT for the specific UE from the core network device.
  • the core network device will not initiate the signaling-based MDT for the UE.
  • the core network device notifies the access network device of the MDT configuration information and the Internet protocol (IP) address of the trace collection entity (TCE).
  • the MDT configuration information includes at least one of the following: MDT type, MDT measurement range, MDT configuration parameters, and a public land mobile network (PLMN) list for the signaling-based MDT.
  • the MDT type may include immediate MDT and logged MDT
  • the MDT configuration parameters may include: measurement events of immediate MDT and measurement intervals and measurement durations of logged MDT.
  • the management-based MDT is not an MDT for a specific UE.
  • the access network device receives an indication message for performing MDT from the core network device.
  • the access network device can select one or more UEs from the UEs managed by the access network device, and perform management-based MDT on the selected one or more UEs.
  • the access network device can consider whether the UE agrees to perform MDT, such as only selecting those UEs that have agreed to perform MDT for MDT, such as the core network device sending an indication message to the access network device, and the indication message indicates whether one or more UEs agree to perform MDT.
  • the core network device sends a management-based MDT allowed indication message to the access network device, and the access network device determines the UEs that agree to perform MDT according to the management-based MDT allowed indication message.
  • the core network device can send a PLMN list of management-based MDT to the access network device, and the access network device determines the UEs that agree to perform MDT according to the PLMN list of management-based MDT.
  • the UE can generate MDT data, and the UE sends the MDT data to the TCE.
  • the MDT data can be transparently transmitted from the UE to the TCE.
  • the access network device does not have the MDT data authority, so the access network device cannot use the MDT data.
  • the access network device cannot obtain continuous UE data from the MDT data.
  • the continuous UE data refers to the data generated by the UE executing MDT in a continuous period of time.
  • the continuous UE data includes at least one of the following: UE location information in continuous time, reference signal receiving power (RSRP), reference signal quality (RSRQ), signal to interference plus noise ratio (SINR), packet loss rate, and delay information.
  • the access network device cannot use continuous UE data as input and reasoning information for the artificial intelligence (AI) model, and there is a problem that the access network device cannot train and reason about the AI model.
  • the MDT data in the embodiment of the present application is not limited to the application scenarios of the AI model, and can be extended to any application scenarios using MDT data, such as estimating the channel quality of the cell where the UE is currently located.
  • the embodiment of the present application proposes a data processing method, which solves the problem that the access network device cannot obtain MDT data authority.
  • Figure 3 is a schematic diagram of an interaction process between the core network device and the access network device provided in the embodiment of the present application, including the following steps:
  • the core network device determines the MDT data authority allocated to the access network device.
  • the core network device has the authority to allocate MDT data.
  • the core network device first determines to allocate MDT data authority to the access network device.
  • MDT data authority refers to the authority for obtaining and using MDT data.
  • MDT data authority is allocated to the access network device by the core network device.
  • MDT data authority may include at least one of the following: the type of MDT data that the access network device can obtain, the identifier (ID) of the UE that provides MDT data to the access network device, the purpose of the access network device using MDT data, and the access network device.
  • the MDT measurement items corresponding to the MDT data that can be obtained by the device, etc.
  • the MDT data authority that the core network device may allocate to the access network device is immediate MDT data, so the access network device has the authority to obtain the immediate MDT data but does not have the authority to obtain the non-immediate MDT data.
  • the MDT data authority that the core network device can allocate to the access network device is the MDT data generated after UE1 executes MDT. Then the access network device has the authority to obtain the MDT data of UE1, but does not have the authority to obtain the MDT data of other UEs except UE1. Specifically, the UE can authorize whether to execute MDT. For different UEs, the user can authorize whether to execute MDT respectively.
  • the core network device can only allocate the identifier of the UE that executes MDT to the access network device for the UE that is authorized to execute MDT. For the UE that is not authorized to execute MDT, the core network device cannot allocate the authority of the UE to execute MDT to the access network device.
  • the core network device assigns the permission for the use of MDT to the access network device, so that the access network device can use the MDT data for the purpose of the MDT. For example, the core network device assigns the permission for the access network device to use the MDT data only within the access network device. After the access network device obtains the MDT data, it can only use the MDT data within the access network device, and cannot transmit the MDT data to other access network devices. For another example, the core network device assigns the permission for the access network device to transmit MDT data externally. After the access network device obtains the MDT data, it can use the MDT data within the access network device and can also transmit the MDT data to other access network devices.
  • the MDT data authority that the core network device may allocate to the access network device is the MDT data generated after the UE executes the first MDT measurement item.
  • the access network device has the authority to obtain the MDT data generated after the UE executes the first MDT measurement, but does not have the authority to obtain the MDT data corresponding to other MDT measurement items other than the first MDT measurement item.
  • the core network device sends first information to the access network device, where the first information is used to indicate MDT data authority.
  • the first information may be generated, and the first information is used to indicate the MDT data permission, and then the core network device sends the first information to the access network device.
  • the first information may be an MDT data permission configuration message, or the first information may also be control signaling, which is not limited here.
  • the first information includes: indication information of a UE performing MDT.
  • the indication information of the UE performing MDT may indicate the identifier of the UE to perform MDT.
  • the core network device can enable the access network device to obtain MDT data for the UE indicated in the indication information.
  • the indication information of the UE performing the MDT includes at least one of the following: a selection ratio of the UE performing the MDT, an identification list of the UE performing the MDT, and a screening condition of the UE performing the MDT; or,
  • the indication information of the UE performing the MDT includes: an identifier of the UE performing the MDT.
  • MDT is divided into signaling-based MDT and management-based MDT.
  • signaling-based MDT and management-based MDT see the description of signaling-based MDT and management-based MDT in the above content.
  • the signaling-based MDT is for a specific UE, and the indication information of the UE performing the MDT includes the identifier of the UE performing the MDT, so that the access network device can determine the identifier of the UE performing the MDT according to the indication information of the UE performing the MDT, and the access network device can obtain MDT data for the UE performing the MDT.
  • the core network device defaults to the same MDT data permission configuration for all UEs.
  • Management-based MDT is for multiple UEs in a specified area range, and the manner of specifying the area range may include at least one of the following: a selection ratio of UEs performing MDT, an identification list of UEs performing MDT, and a screening condition for UEs performing MDT.
  • the selection ratio of UEs performing MDT there are multiple values for the selection ratio of UEs performing MDT. For example, if the selection ratio of UEs performing MDT is 5%, the access network device can select 5% of UEs from all currently served UEs to perform MDT according to the selection ratio of UEs performing MDT.
  • the identification list of UEs performing MDT includes the identification of UEs performing MDT, and the access network device can select UEs in the list to perform MDT according to the identification list of UEs performing MDT.
  • the screening condition of UEs performing MDT can be used by the access network device to select UEs that meet the screening condition from all currently served UEs to perform MDT.
  • the access network device can instruct the access network device to select one or more UEs to perform MDT through the first information, and the access network device can determine the authority of the UE performing MDT, which solves the problem that the access network device cannot obtain the MDT data authority.
  • the first information includes: indication information of the MDT type; the MDT type includes at least one of the following: immediate MDT and non-immediate MDT.
  • immediate MDT and non-immediate MDT For detailed introduction of immediate MDT and non-immediate MDT, please refer to the above related content.
  • the core network device sends the indication information of the MDT type to the access network device, so that the access network device can obtain the MDT data for the MDT type indicated in the indication information. For example, if the core network device allocates the immediate MDT data right to the access network device, the access network device can only obtain the immediate MDT data, but cannot obtain the non-immediate MDT data. For another example, if the core network device allocates the non-immediate MDT data right to the access network device, the access network device can only obtain the immediate MDT data, but cannot obtain the non-immediate MDT data. If the access network device does not have the immediate MDT data permission, it can only obtain the non-immediate MDT data but cannot obtain the immediate MDT data.
  • the first information includes: usage information of MDT.
  • the MDT usage information is used to indicate the usage of MDT data, including: indicating that the MDT data is applied inside the access network device, or indicating that the MDT data is applied inside the access network device and indicating that the access network device transmits the MDT data to other access network devices.
  • indicating that the MDT data is applied inside the access network device or indicating that the MDT data is applied inside the access network device and indicating that the access network device transmits the MDT data to other access network devices.
  • the core network device indicates that the MDT data is applied to the inside of the access network device and instructs the access network device to transmit the MDT data to other access network devices.
  • the access network device can input the MDT data into the AI model of the access device for model training or reasoning.
  • the access network device can send the MDT data to other access network devices so that other access network devices use the MDT data for the AI model of the other access network device for model training or reasoning.
  • a core network device is a source access network device, and other core network devices are target access network devices.
  • the source access network device sends MDT data to the target access network device through a communication interface.
  • the usage information of MDT can be represented by a 1-bit value.
  • the core network device defaults to an access network device that can use the MDT data inside the access network device, and can also send the MDT data to other access network devices.
  • the first information includes: an identifier of a UE performing MDT, an MDT measurement item, and an MDT data authority corresponding to the MDT measurement item.
  • the MDT may be a signaling-based MDT
  • the first information includes: an identifier of a UE that performs the MDT, for example, the identifier of the UE that performs the MDT may be determined by the aforementioned indication information of the UE that performs the MDT.
  • the core network device sends the identifier of the UE that performs the MDT to the access network device, so that the access network device can obtain MDT data for the UE indicated in the first information.
  • the MDT measurement item may be one or more items, and the specific implementation of the MDT measurement item is not limited.
  • the MDT measurement item may include at least one of the following: M1, M2, M3, M4, M5, M6, M7, M8, M9, and the specific implementation of the above MDT measurement items will not be described in detail.
  • the MDT measurement item may include at least one of the following: location information (locationInfo), serving cell identity (servCellIdentity), serving cell measurement result (measResultServingCell), neighboring cell measurement result (measResultNeighCells), used to indicate the detection of any cell selection state (anyCellSelectionDetected) and the suspension of measurement log (inDeviceCoexDetected) due to the detection of coexistence problems within the device, and the specific implementation of the above MDT measurement items will not be described in detail.
  • locationInfo location information
  • serving cell identity serving cell identity
  • measResultServingCell serving cell measurement result
  • measResultNeighCells neighboring cell measurement result
  • the MDT data authority corresponding to the MDT measurement item refers to the MDT data authority set by the core network device for each MDT measurement item. For example, if the MDT data authority corresponding to an MDT measurement item is 1, it means that the core network device allocates the MDT data authority corresponding to the MDT measurement item to the access network device. For another example, if the MDT data authority corresponding to an MDT measurement item is 0, it means that the core network device does not allocate the MDT data authority corresponding to the MDT measurement item to the access network device. There is no limitation on the value of the MDT data authority.
  • MDT can be divided into immediate MDT and non-immediate MDT.
  • the core network device can configure MDT data permissions. For example, if the MDT measurement item of immediate MDT is M1 and the MDT data permission corresponding to M1 is 1, it means that the core network device has allocated MDT data permissions to the access network device.
  • the core network device can configure MDT data permissions. For example, if the MDT measurement item of non-immediate MDT is location information and the MDT data permission corresponding to the location information is 0, it means that the core network device has not allocated MDT data permissions to the access network device.
  • the access network device receives first information from the core network device.
  • the access network device obtains the MDT data authority allocated to the access network device according to the first information.
  • the access network device After receiving the first information from the core network device, the access network device parses the first information and can obtain the MDT data authority assigned by the core network device to the access network device, thereby enabling the access network device to obtain MDT data.
  • the data processing method executed by the access network device further includes the following step A1:
  • the access network device obtains MDT data according to the MDT data authority.
  • the access network device receives the MDT data authority from the core network device, and the access network device can use the MDT data authority, that is, the access network device has the ability to obtain MDT data, and the access network device can obtain the MDT data corresponding to the MDT data authority.
  • the specific method of the access network device to obtain MDT data please refer to the example description in the subsequent embodiments.
  • the access network device when the access network device performs model training or inference on the AI model of the access network device, it obtains continuous UE data.
  • the access network device can obtain the corresponding MDT data according to the MDT data authority, and the access network device obtains continuous UE data according to the MDT data.
  • the MDT data and continuous UE data please refer to the above content.
  • step A1 the access network device obtains MDT data according to the MDT data authority, including:
  • the access network device receives the MDT measurement report sent by the UE according to the MDT data authority.
  • the MDT measurement report includes: MDT data.
  • the access network device after receiving the MDT data authority, the access network device sends MDT configuration information to the UE according to the MDT data authority, the UE performs MDT according to the MDT configuration information, and then the UE generates an MDT measurement report, and the UE sends the MDT measurement report to the access network device.
  • the MDT data authority includes: MDT usage information, and the MDT usage information is used to instruct the access network device to transmit MDT data to other access network devices.
  • the data processing method executed by the access network device also includes the following step B1:
  • Access network equipment transmits MDT data to other access network equipment.
  • the MDT data authority allocated by the core network device to the access network device indicates that the access network device transmits MDT data to other access network devices.
  • the access network device obtains the authority to transmit MDT data externally based on the MDT data authority.
  • the access network device can transmit the MDT data to other access network devices, solving the problem that other access network devices cannot obtain MDT data.
  • other access network devices receive MDT data from access network devices with MDT data outbound authority, and the other access network devices obtain continuous UE data from the MDT data.
  • the other access network devices input the continuous UE data into the AI model of other access network devices for model training or reasoning.
  • the first information may also include PLMN information of the cell that uses the MDT data externally, cell global identifier (CGI) information, etc.
  • CGI cell global identifier
  • the core network device and the access network device interact with each other through the method shown in FIG3.
  • the core network device can also execute steps 402 and 403 shown in FIG4.
  • the access network device can also execute steps 401 and 404 shown in FIG4.
  • the MDT data authority and MDT data involved in the aforementioned embodiments are not described in detail. For details, see the embodiment shown in FIG3. Please refer to FIG4, which is another schematic diagram of the interaction process between the core network device and the access network device provided in the embodiment of the present application, including the following steps:
  • the access network device sends an MDT data request to the core network device according to the MDT data authority.
  • the access network device After the access network device obtains the MDT data authority through the embodiment shown in Figure 3, the access network device sends an MDT data request to the core network device according to the MDT data authority.
  • the MDT data authority For details on the MDT data authority, see the above embodiment.
  • the core network device receives the MDT data request sent by the access network device according to the MDT data authority.
  • the core network device receives the MDT data request from the access network device, and performs verification according to the MDT data authority carried in the MDT data request.
  • the access network device passes the MDT data authority verification, the subsequent step 403 is executed.
  • the core network device sends a response corresponding to the MDT data request to the access network device, where the response includes: MDT data.
  • the core network device allocates immediate MDT data authority to the access network device, and allocates the identifier of UE1 and MDT measurement item 1. Then, the MDT data sent by the core network device to the access network device is the immediate MDT data obtained by UE1 executing MDT measurement item 1.
  • the core network device allocates non-immediate MDT data authority to the access network device, and allocates the identifier of UE2 and MDT measurement item 2. Then the MDT data sent by the core network device to the access network device is the non-immediate MDT data obtained by UE2 executing MDT measurement item 2.
  • the access network device receives a response corresponding to the MDT data request from the core network device, where the response includes: MDT data.
  • the access network device can parse the response to obtain the MDT data allocated by the core network device to the access network device.
  • the MDT data includes: non-immediate MDT data of the UE in a non-connected state buffered by the core network device, and/or immediate MDT data sent multiple times by the UE in a connected state to the core network device.
  • the UE when the UE in the connected state performs immediate MDT, the UE can send the MDT data of the immediate MDT to the access network device multiple times.
  • the UE When the UE in the non-connected state performs non-immediate MDT, the UE will cache the MDT data. Later, when the UE initiates an RRC connection to the access network device, it will indicate that the MDT data of the non-immediate MDT is currently recorded, and then the access network device can request the UE, and the UE reports the MDT data of the non-immediate MDT to the access network device.
  • the access network device can request the MDT data from the core network device or TCE.
  • the core network device and the access network device interact with each other through the method shown in Figures 3 and 4.
  • the core network device can also execute step 502 shown in Figure 5, and the access network device
  • the access network device may also execute step 501 shown in FIG5.
  • the MDT data authority and MDT data involved in the aforementioned embodiments are not described in detail. For details, see the embodiments shown in FIG3 to FIG4. Please refer to FIG5, which is another schematic diagram of the interaction process between the core network device and the access network device provided in the embodiment of the present application.
  • the method provided in the embodiment of the present application further includes the following steps:
  • An access network device sends a first request to a core network device, where the first request is used to request MDT data authority from the core network device.
  • the access network device When the access network device acquires the MDT data, the access network device generates the first request.
  • the first request may specifically include at least one of the following: the MDT type requested by the access network device, the identifier of the UE performing the MDT, the MDT measurement item, the MDT data authority corresponding to the MDT measurement item, etc.
  • the MDT type the identifier of the UE performing the MDT, the MDT measurement item, and the MDT data authority corresponding to the MDT measurement item, see the above content for details.
  • the core network device receives the first request.
  • the core network device may parse the first request and determine the MDT data authority requested by the access network device to the core network device.
  • the core network device may also execute steps 301 and 302 shown in FIG. 3, which will not be described in detail here.
  • the access network device can request the core network device to modify the MDT data authority or request to modify the MDT configuration to solve the problem that the current MDT data cannot meet the needs of the access network device.
  • the following is an illustration of the access network device requesting the core network device to modify the MDT data authority with FIG6, and the following is an illustration of the access network device requesting the core network device to modify the MDT configuration with FIG7.
  • the core network device and the access network device interact through the method shown in Figures 3, 4 and 5.
  • the core network device can also execute steps 602 to 604 shown in Figure 6.
  • the access network device can also execute steps 601, 605, and 606 shown in Figure 6.
  • the MDT data authority and MDT data involved in the aforementioned embodiments are no longer described in detail. See the embodiments shown in Figures 3 to 5 for details.
  • FIG. 6 is another schematic diagram of an interaction process between a core network device and an access network device provided in an embodiment of the present application, including the following steps:
  • the access network device sends a second request to the core network device, where the second request is used to request the core network device to modify MDT data permissions.
  • step 601 can be executed after executing step 304 shown in the aforementioned FIG. 3 .
  • the second request may include at least one of the following: the MDT type requested to be modified by the access network device, the identifier of the UE executing MDT requested to be modified, the MDT data permission requested to be modified, etc.
  • the second request may be a MDT incremental configuration data permission request message, or the second request may be other request messages, which are not limited here.
  • the access network device may request to modify any one or more of the above three, which are not limited here.
  • the MDT type, the identifier of the UE executing MDT, and the MDT data permission please refer to the above content in detail.
  • modifying the MDT data permission may include adding the MDT data permission, or deleting the MDT data permission.
  • the core network device receives a second request from the access network device, where the second request is used to request the core network device to modify MDT data permissions.
  • the core network device modifies the MDT data authority allocated to the access network device according to the second request.
  • the core network device may modify the current MDT data authority allocated to the access network device according to the second request to meet the requirement of the access network device for modifying the MDT data authority.
  • the core network device sends second information to the access network device, where the second information is used to indicate the modified MDT data authority.
  • the core network device After the core network device completes the modification of the current MDT data rights assigned to the access network device, it can indicate the modified MDT data rights to the access network device through the second information.
  • the second information can specifically be the MDT configuration and data rights request response.
  • the access network device receives second information from the core network device.
  • the access network device obtains the modified MDT data authority allocated to the access network device according to the second information.
  • the access network device After receiving the second information, the access network device parses the second information and can obtain the modified MDT data authority assigned by the core network device to the access network device, so that the access network device has the modified MDT data authority, which solves the problem that the access network device cannot update the MDT data authority, so that the modified MDT data authority can be used to obtain the data corresponding to the modified MDT data authority. Limited to the corresponding MDT data.
  • FIG. 6 illustrates the way in which the core network device modifies the MDT data permissions.
  • the access network device can request the core network device to modify the MDT configuration to solve the problem that the current MDT data cannot meet the needs of the access network device.
  • the core network device and the access network device interact through the method shown in Figures 3, 4, 5 and 6.
  • the core network device can also execute steps 702 to 703 shown in Figure 7.
  • the access network device can also execute steps 701, step 704, and step 705 shown in Figure 7.
  • the MDT data authority and MDT data involved in the aforementioned embodiments are not described in detail. See the embodiments shown in Figures 3 to 6 for details.
  • FIG. 7 is another schematic diagram of an interaction process between a core network device and an access network device provided in an embodiment of the present application, including the following steps:
  • the access network device sends a third request to the core network device, where the third request is used to request the core network device to modify the MDT configuration.
  • the third request may include at least one of the following: the MDT type requested to be modified by the access network device, the identifier of the UE executing MDT requested to be modified, the MDT measurement item requested to be modified, etc.
  • the third request may be an MDT incremental configuration request message, or the third request may be other request messages, which are not limited here.
  • the access network device may request to modify any one or more of the above three, which are not limited here.
  • the MDT type, the identifier of the UE executing MDT, and the MDT measurement item please refer to the above content in detail.
  • modifying the MDT configuration may include adding an MDT configuration, or deleting an MDT configuration.
  • the core network device receives a third request from the access network device, where the third request is used to request the core network device to modify the MDT configuration.
  • the third request and the second request of the embodiment shown in FIG. 6 may be sent through the same message, or the third request and the second request may be sent through different messages, which is not limited here.
  • the core network device sends third information to the access network device, where the third information includes the modified MDT configuration.
  • the core network device may modify the current MDT configuration allocated to the access network device according to the third request to meet the requirement of the access network device for modifying the MDT configuration.
  • the third information and the second information of the embodiment described in FIG. 6 may be sent through the same message, or the third information and the second information may be sent through different messages, which is not limited here.
  • the modified MDT configuration can be determined, and the core network device can indicate the modified MDT configuration to the access network device through third information.
  • the third information can specifically be an MDT configuration request response.
  • the modified MDT configuration includes: a modified trigger condition corresponding to the MDT measurement item, and/or a modified configuration parameter corresponding to the MDT measurement item.
  • the core network device may modify the triggering condition of the MDT measurement item, thereby changing the triggering condition for the UE to perform MDT by modifying the triggering condition.
  • the core network device may modify the configuration parameters of one or more MDT measurement items.
  • the modified trigger condition includes an added or deleted trigger condition.
  • the core network device can add trigger conditions, such as adding trigger conditions for AI model training or reasoning.
  • the core network device can also delete the corresponding trigger condition.
  • the configuration parameters may include: a measurement period of an MDT measurement item, and/or an MDT event triggering configuration parameter of an MDT measurement item.
  • the core network device may modify the measurement period of the MDT measurement item, for example, increase or shorten the measurement period of the MDT measurement item.
  • the core network device may modify the MDT event triggering configuration parameter. For example, a new MDT event triggering configuration parameter is added, or an original MDT event triggering configuration parameter is deleted, or the value of the MDT event triggering configuration parameter is modified.
  • the configuration parameters include at least one of the following: a measurement interval of an MDT measurement item, a measurement duration of an MDT measurement item, or an MDT event triggering configuration parameter of an MDT measurement item.
  • the core network device may modify the measurement interval of the MDT measurement item, such as increasing or shortening the measurement interval of the MDT measurement item.
  • the core network device may modify the measurement duration of the MDT measurement item.
  • the core network device may modify the MDT event triggering configuration parameter. For example, a new MDT event triggering configuration parameter may be added or an original MDT event triggering configuration parameter may be deleted or the value of the MDT event triggering configuration parameter may be modified.
  • modifying the MDT event triggering configuration parameters may include: modifying an RSRP threshold, or modifying an RSRQ threshold, and the like.
  • the access network device receives third information from the core network device.
  • the access network device obtains the modified MDT configuration according to the third information.
  • the access network device After the access network device receives the third information, it parses the third information and can obtain the modified MDT configuration assigned to the access network device by the core network device, thereby solving the problem that the access network device cannot update the MDT data.
  • the modified MDT configuration can be used to obtain the MDT data corresponding to the modified MDT configuration.
  • the core network device is specifically AMF
  • the access network device is specifically gNB.
  • MDT data There are many ways for gNB to use MDT data.
  • gNB take gNB obtaining MDT data for AI model training and reasoning as an example. The above scenario is only one possible implementation method and is not intended to limit the embodiments of this application.
  • AMF sends an MDT data authority configuration message to gNB.
  • gNB obtains MDT data according to the MDT data authority.
  • gNB uses the obtained MDT data for input and reasoning of AI models.
  • the way for gNB to obtain MDT data can be that gNB directly obtains MDT data from UE. If gNB cannot obtain MDT data from UE, gNB can obtain MDT data from AMF or TCE.
  • FIGS. 8a and 8b are schematic diagrams of another embodiment of the data processing method provided by the embodiment of the present application, including the following process:
  • Step 801 AMF sends an MDT data authority configuration message to gNB.
  • the AMF sends an MDT data authority configuration message to the gNB so that the gNB obtains the MDT data authority allocated by the AMF.
  • MDT can be divided into signaling-based MDT and management-based MDT.
  • signaling-based MDT and management-based MDT please refer to the above-mentioned related content.
  • AMF may not authorize all MDT data.
  • the embodiment of the present application is divided into two authorization situations. One is that AMF uniformly configures MDT data permissions for all MDT data of different UEs, and the other is that AMF separately configures MDT data permissions for different MDT data of different UEs.
  • the AMF uniformly configures permissions for all MDT data of different UEs.
  • the MDT data permission configuration message does not indicate which part of the MDT data in the MDT measurement report is authorized.
  • the MDT data permission configuration message includes at least one of the following: an identifier of the UE performing MDT, data permissions for immediate MDT, and data permissions for non-immediate MDT.
  • the content of the MDT data permission configuration message may be as shown in the following Table 1:
  • the AMF configures permissions for different MDT data of different UEs respectively, and the MDT data permission configuration message can indicate which specific data in the MDT measurement report is authorized.
  • the MDT data permission configuration message may include at least one of the following: an identifier of the UE performing MDT, measurement items of immediate MDT and corresponding MDT data permissions, and measurement items of non-immediate MDT and corresponding MDT data permissions.
  • the content included in the MDT data permission configuration message may be as shown in the following Table 2:
  • Step 802 The gNB obtains MDT data from the UE.
  • the UE when a UE in a connected state performs immediate MDT, the UE can send MDT data of immediate MDT to the gNB multiple times.
  • the UE When a UE in a non-connected state performs non-immediate MDT, the UE will cache the MDT data. Later, when the UE initiates an RRC connection to the gNB, it will indicate that the MDT data of non-immediate MDT is currently recorded, and then the gNB can request the UE to report the MDT data of non-immediate MDT to the gNB.
  • Step 803 gNB sends an MDT data request to AMF or TCE.
  • the gNB can request MDT data from the AMF or TCE.
  • the difference between Figure 8a and Figure 8b is that the methods for obtaining MDT data are different.
  • the gNB can request the corresponding MDT data from the AMF based on the MDT data authority issued by the AMF and the data requirements of the AI model.
  • the MDT data request specifies the purpose information of the MDT, the identifier of the UE executing the MDT, and the corresponding MDT data type.
  • Step 804 AMF or TCE sends a response to the MDT data request to the gNB.
  • the AMF issues the MDT data authority to the gNB, so that the gNB can legally obtain the MDT data and extract continuous UE data from it as the input and reasoning data of the AI model to improve the reasoning or training accuracy of the AI model deployed on the gNB.
  • the solution provided by this application is introduced in combination with the application scenario. If the MDT data obtained by the gNB is not sufficient to support the needs of the AI model, the gNB can send an MDT incremental configuration data permission request to the AMF, and the AMF returns the modified MDT data configuration and data permission request response, and then the gNB sends the new MDT configuration to the UE to obtain a new MDT measurement report and extract continuous UE data from the new MDT measurement report.
  • FIG. 9 is a schematic diagram of another embodiment of the data processing method provided in the embodiment of the present application, comprising the following steps:
  • Step 901 gNB sends an MDT incremental configuration data permission request message to AMF.
  • the MDT incremental configuration data authority request message may include: the triggering conditions that the gNB requests to modify, and the configuration parameters of the MDT measurement items that the gNB requests to modify.
  • the MDT incremental configuration data permission request message may include: gNB requesting to modify MDT data permissions, or gNB requesting to modify MDT configuration.
  • the MDT incremental configuration data permission request message may include at least one of the following: an identifier of the UE performing MDT, the original MDT configuration, a modified trigger condition for the UE to perform MDT, data permission for immediate MDT, and data permission for non-immediate MDT.
  • the original MDT configuration includes: the triggering conditions for executing MDT, the measurement period and reporting times of immediate MDT, or the measurement interval and measurement duration of non-immediate MDT, and the modified triggering conditions for UE to execute MDT include: AI model training or reasoning identifier.
  • the MDT incremental configuration data permission request message can be defined as follows in Table 3:
  • M1 configuration update For modifying the immediate MDT configuration parameters, take M1 configuration update as an example, as shown in Table 4 below:
  • a configuration update based on a non-immediate MDT triggering event as shown in Table 3 may be defined, as shown in Table 6 below:
  • the MDT incremental configuration data permission request message may include at least one of the following: screening conditions for UEs performing MDT, original MDT configuration, modified triggering conditions for UEs performing MDT, data permissions for immediate MDT, and data permissions for non-immediate MDT.
  • the original MDT configuration, modified triggering conditions for UEs performing MDT, data permissions for immediate MDT, and data permissions for non-immediate MDT are the same as those for the aforementioned signaling-based MDT, as shown in Table 3.
  • the modified triggering condition for the UE to perform MDT may be defined as shown in the following Table 7:
  • Step 902 AMF sends an MDT incremental configuration data permission request response to the gNB.
  • the AMF sends a gNB MDT incremental configuration data permission request response to the gNB according to the gNB MDT incremental configuration data permission request, and the gNB MDT incremental configuration data permission request response includes: modified MDT data permission and modified MDT configuration.
  • modified MDT data permission and modified MDT configuration see the above content for details.
  • Step 903 gNB sends MDT configuration to UE.
  • the gNB After receiving the new MDT configuration through step 902, the gNB sends the MDT configuration to the UE.
  • Step 904 The UE sends an MDT measurement report to the gNB.
  • the UE After the UE receives the MDT configuration based on step 903, the UE performs MDT, generates an MDT measurement report, and sends the MDT measurement report to the gNB.
  • Step 905 gNB obtains UE data.
  • the gNB obtains continuous UE data from the MDT data.
  • the continuous UE data includes the non-immediate MDT data of the non-connected UE and the immediate MDT data reported multiple times by the connected UE.
  • the gNB can request the MDT incremental configuration data authority from the AMF according to the requirements of the AI model, so that the gNB can legally obtain the MDT data, and extract continuous UE data from the MDT data as the input and reasoning data of the AI model to improve the reasoning or training accuracy of the AI model deployed on the gNB.
  • the communication device provided in the embodiment of the present application is described below.
  • FIG10 is a schematic diagram of a structure of a communication device provided in an embodiment of the present application.
  • the communication device can be used to execute the process executed by the core network device in the embodiments shown in FIG3 to FIG7, or the communication device can be used to execute the process executed by the access network device in the embodiments shown in FIG3 to FIG7.
  • the relevant introduction in the above method embodiment please refer to the relevant introduction in the above method embodiment.
  • the communication device 1000 includes a processing module 1001 and a transceiver module 1002.
  • the transceiver module 1002 can implement corresponding communication functions, and the processing module 1001 is used for data processing.
  • the transceiver module 1002 can also be called a communication interface or a communication module.
  • the communication device 1000 may further include a storage module, which may be used to store instructions and/or data, and the processing module 1001 may read the instructions and/or data in the storage module so that the communication device implements the aforementioned method embodiment.
  • a storage module which may be used to store instructions and/or data
  • the processing module 1001 may read the instructions and/or data in the storage module so that the communication device implements the aforementioned method embodiment.
  • the communication device 1000 can be used to perform the actions performed by the communication device in the above method embodiment.
  • the communication device 1000 can be a communication device or a component that can be configured in a communication device.
  • the processing module 1001 is used to perform the processing-related operations on the communication device side in the above method embodiment.
  • the transceiver module 1002 is used to perform the reception-related operations on the communication device side in the above method embodiment.
  • the transceiver module 1002 may include a sending module and a receiving module.
  • the sending module is used to execute the sending
  • the receiving module is used to perform the receiving operation in the above method embodiment.
  • the communication device 1000 may include a sending module but not a receiving module.
  • the communication device 1000 may include a receiving module but not a sending module. Specifically, it may depend on whether the above solution executed by the communication device 1000 includes a sending action and a receiving action.
  • the processing module 1001 in the above embodiment can be implemented by at least one processor or processor-related circuit.
  • the transceiver module 1001 can be implemented by a transceiver or a transceiver-related circuit.
  • the transceiver module 1002 can also be called a communication module or a communication interface.
  • the storage module can be implemented by at least one memory.
  • the communication device is used to execute the aforementioned steps 301 and 302, steps 402 and 403, step 502, steps 602 to 604, and steps 702 to 703 executed by the core network device in the above method embodiment.
  • the communication device is used to execute steps 303 and 304, steps 401 and 404, steps 501, 601, 605, 606, 701, 704 and 705 performed by the access network device in the above method embodiment.
  • FIG11 shows a simplified schematic diagram of the structure of a communication device.
  • the communication device includes a processor, a memory, and a transceiver.
  • the memory can store computer program codes
  • the transceiver includes a transmitter 1131, a receiver 1132, an antenna 1133, and an input/output device (not shown in the figure).
  • the processor is mainly used to process communication protocols and communication data, control communication devices, execute software programs, process data of software programs, etc.
  • the memory is mainly used to store software programs and data.
  • the processor When sending data, the processor performs baseband processing on the data to be sent, and then outputs the baseband signal to the RF circuit.
  • the RF circuit performs RF processing on the baseband signal and then sends the RF signal outward in the form of electromagnetic waves through the antenna.
  • the RF circuit receives the RF signal through the antenna, converts the RF signal into a baseband signal, and outputs the baseband signal to the processor.
  • the processor converts the baseband signal into data and processes the data.
  • only one memory, processor and transceiver are shown in Figure 11. In an actual communication device product, there may be one or more processors and one or more memories.
  • the memory may also be referred to as a storage medium or a storage device, etc.
  • the memory may be set independently of the processor or integrated with the processor, and the embodiments of the present application do not limit this.
  • the antenna and the radio frequency circuit with transceiver functions may be regarded as the transceiver module of the communication device, and the processor with processing function may be regarded as the processing module of the communication device.
  • the communication device includes a processor 1110, a memory 1120 and a transceiver 1130.
  • the processor 1110 may also be referred to as a processing unit, a processing board, a processing module, a processing device, etc.
  • the transceiver 1130 may also be referred to as a transceiver unit, a transceiver, a transceiver device, etc.
  • the device for implementing the receiving function in the transceiver 1130 is regarded as a receiving module
  • the device for implementing the sending function in the transceiver 1130 is regarded as a sending module
  • the transceiver 1130 includes a receiver and a transmitter.
  • the transceiver may sometimes be referred to as a transceiver, a transceiver module, or a transceiver circuit.
  • the receiver may sometimes be referred to as a receiver, a receiving module, or a receiving circuit.
  • the transmitter may sometimes be referred to as a transmitter, a transmitting module, or a transmitting circuit.
  • FIG. 11 is merely an example and not a limitation, and the above-mentioned communication device including the transceiver module and the processing module may not rely on the structure shown in FIG. 11 .
  • the chip When the communication device 1100 is a chip, the chip includes a processor, a memory and a transceiver.
  • the transceiver may be an input/output circuit or a communication interface;
  • the processor may be a processing module or a microprocessor or an integrated circuit integrated on the chip.
  • the sending operation of the communication device in the above method embodiment may be understood as the output of the chip, and the receiving operation of the communication device in the above method embodiment may be understood as the input of the chip.
  • the communication device is used to execute the aforementioned steps 301 and 302, steps 402 and 403, step 502, steps 602 to 604, and steps 702 to 703 executed by the core network device in the above method embodiment.
  • the communication device is used to execute steps 303 and 304, steps 401 and 404, steps 501, 601, 605, 606, 701, 704 and 705 performed by the access network device in the above method embodiment.
  • An embodiment of the present application also provides a computer-readable storage medium on which computer instructions for implementing the method executed by a terminal device or a network device in the above method embodiment are stored.
  • the computer when the computer program is executed by a computer, the computer can implement the method described above by the terminal device or the network. The method performed by the device.
  • An embodiment of the present application also provides a computer program product comprising instructions, which, when executed by a computer, enables the computer to implement the method executed by a terminal device or a network device in the above method embodiment.
  • an embodiment of the present application further provides a data processing system, which communication system includes the core network device and access network device in the above embodiment.
  • An embodiment of the present application also provides a chip device, including a processor, for calling a computer program or computer instruction stored in the memory so that the processor executes the method of the embodiment shown in Figures 3 to 7 above.
  • the input of the chip device corresponds to the receiving operation in the embodiments shown in FIG. 3 to FIG. 7
  • the output of the chip device corresponds to the sending operation in the embodiments shown in FIG. 3 to FIG. 7 .
  • the processor is coupled to the memory via an interface.
  • the chip device further comprises a memory, in which computer programs or computer instructions are stored.
  • the processor mentioned in any of the above may be a general-purpose central processing unit, a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the method of the embodiments shown in Figures 3 to 7.
  • the memory mentioned in any of the above may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM), etc.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed.
  • Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to the actual application scenario to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.
  • the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium.
  • the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application.
  • the aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard drives, ROM, RAM, magnetic disks, or optical disks.
  • the network device and/or the terminal device can perform some or all of the steps in the embodiment of the present application, and these steps or operations are only examples. In the embodiment of the present application, other operations or variations of various operations can also be performed. In addition, each step can be performed in a different order presented in the embodiment of the present application, and it is possible not to perform all the operations in the embodiment of the present application.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例公开了一种数据处理方法和通信装置，用于接入网设备能够获取到MDT数据权限。本申请实施例提供的方法包括：确定分配给接入网设备的最小化路测MDT数据权限；向所述接入网设备发送第一信息，所述第一信息用于指示所述MDT数据权限。

Description

一种数据处理方法和通信装置
本申请要求于2022年11月03日提交中国专利局、申请号为202211373651.6、发明名称为“一种数据处理方法和通信装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种数据处理方法和通信装置。
背景技术
最小化路测(minimization of drive-tests，MDT)是通信系统实现自动化采集和分析含位置信息的用户设备(user equipment，UE)测量报告的技术，运营商通过签约的UE进行测量上报来部分替代传统的路测工作，自动收集UE的MDT数据，该MDT数据可用于检测和优化无线网络中的问题和故障。
在目前的通信系统中，UE上报的MDT数据透传至跟踪收集实体(trace collection entity，TCE)，MDT数据的应用场景受限。
发明内容
本申请实施例提供了一种数据处理方法和通信装置，用于接入网设备能够获取到MDT数据权限。
为解决上述技术问题，本申请实施例提供以下技术方案：
第一方面，本申请实施例提供一种数据处理方法，所述方法应用于核心网设备，所述方法包括：确定分配给接入网设备的最小化路测MDT数据权限；向所述接入网设备发送第一信息，所述第一信息用于指示所述MDT数据权限。在上述方案中，核心网设备确定分配给接入网设备的MDT数据权限，然后核心网设备向接入网设备发送第一信息，第一信息用于指示所述MDT数据权限。由于接入网设备可以获取到核心网设备分配给该接入网设备的MDT数据权限，从而接入网设备具有MDT数据权限，扩展了MDT数据的应用场景。
在一种可能的实现方式中，所述第一信息包括：执行MDT的终端设备的指示信息。在上述方案中，核心网设备通过向接入网设备发送执行MDT的终端设备的指示信息，能够使得接入网设备针对该指示信息中指示的终端设备获取MDT数据。
在一种可能的实现方式中，所述第一信息包括：MDT类型的指示信息；所述MDT类型包括如下至少一种：立即MDT、非立即MDT。
在一种可能的实现方式中，所述第一信息包括：MDT的用途信息；所述MDT的用途信息，用于指示MDT数据应用于所述接入网设备内部，或者，指示MDT数据应用于所述接入网设备内部以及指示所述接入网设备向其它接入网设备传输所述MDT数据。在上述方案中，接入网设备可以根据该MDT的用途信息使用MDT数据，实现对MDT数据的正确使用，避免MDT数据泄露的风险。
在一种可能的实现方式中，所述第一信息包括：执行MDT的终端设备的标识、MDT测量项、所述MDT测量项对应的MDT数据权限。在上述方案中，能够使得接入网设备针对该第一信息中指示的UE获取MDT测量项对应的MDT数据。
在一种可能的实现方式中，所述方法还包括：接收所述接入网设备根据所述MDT数据权限发送的MDT数据请求；向所述接入网设备发送对应于所述MDT数据请求的响应，所述响应包括：MDT数据。在上述方案中，核心网设备能够向接入网设备发送MDT数据，从而使得接入网设备具有使用MDT数据的能力。
在一种可能的实现方式中，所述MDT数据包括：所述核心网设备缓存的处于非连接态的终端设备的非立即MDT数据，和/或处于连接态的终端设备多次向所述核心网设备发送的立即MDT数据。
在一种可能的实现方式中，所述方法还包括：接收来自所述接入网设备的第一请求，所述第一请求用于向所述核心网设备请求所述MDT数据权限。在上述方案中，接入网设备可以请求核心网设备分配MDT数据权限，使得接入网设备能够灵活的请求所需的MDT数据权限。
在一种可能的实现方式中，所述方法还包括：接收来自所述接入网设备的第二请求，所述第二请求 用于请求所述核心网设备修改MDT数据权限；根据所述第二请求修改分配给所述接入网设备的MDT数据权限；向所述接入网设备发送第二信息，所述第二信息用于指示所述修改后的MDT数据权限。在上述方案中，接入网设备接收到第二信息之后，解析该第二信息，可以获取到核心网设备分配给该接入网设备的修改后的MDT数据权限，从而使得接入网设备具有修改后的MDT数据权限，解决了接入网设备无法对MDT数据权限进行更新的问题，从而使用修改后的MDT数据权限能够获取到与修改后的MDT数据权限相对应的MDT数据。
在一种可能的实现方式中，所述第二信息包括：执行MDT的终端设备的指示信息。
在一种可能的实现方式中，当所述MDT是基于管理的MDT时，所述终端设备的指示信息包括如下至少一种：终端设备选取比例、终端设备标识列表、终端设备筛选条件；或者，当所述MDT是基于信令的MDT时，所述终端设备的指示信息包括：所述终端设备的标识。
在一种可能的实现方式中，所述方法还包括：接收来自所述接入网设备的第三请求，所述第三请求用于请求所述核心网设备修改MDT配置；向所述接入网设备发送第三信息，所述第三信息包括修改后的MDT配置。在上述方案中，接入网设备接收到第三信息之后，解析该第三信息，可以获取到核心网设备分配给该接入网设备的修改后的MDT配置，解决了接入网设备无法对MDT数据进行更新的问题，使用修改后的MDT配置能够获取到与修改后的MDT配置相对应的MDT数据。
在一种可能的实现方式中，所述修改后的MDT配置包括：对应于MDT测量项的修改后的触发条件、和/或，对应于MDT测量项的修改后的配置参数。
在一种可能的实现方式中，当MDT为立即MDT时，所述配置参数包含：所述MDT测量项的测量周期，和/或，所述MDT测量项的MDT事件触发配置参数；或者，当MDT为非立即MDT时，所述配置参数包含如下至少一项：所述MDT测量项的测量间隔，所述MDT测量项的测量持续时间，或者，所述MDT测量项的MDT事件触发配置参数。在上述方案中，核心网设备可以修改MDT测量项的触发条件，从而通过修改触发条件，更改UE执行MDT的触发条件。或者，核心网设备可以修改一项或多项MDT测量项的配置参数，从而能够使得接入网设备获取到修改后的触发条件和修改后的MDT测量项的配置参数。
在一种可能的实现方式中，所述修改后的触发条件包括增加或者删除的触发条件。
第二方面，本申请实施例还提供一种数据处理方法，所述方法应用于接入网设备，所述方法包括：接收来自核心网设备的第一信息；根据所述第一信息获取分配给所述接入网设备的最小化路测MDT数据权限。在上述方案中，核心网设备确定分配给接入网设备的MDT数据权限，然后核心网设备向接入网设备发送第一信息，第一信息用于指示所述MDT数据权限。由于接入网设备可以获取到核心网设备分配给该接入网设备的MDT数据权限，从而接入网设备具有MDT数据权限，扩展了MDT数据的应用场景。
在一种可能的实现方式中，所述方法还包括：根据所述MDT数据权限获取MDT数据。在上述方案中，接入网设备可以使用该MDT数据权限，即接入网设备具有能够获取MDT数据的能力，接入网设备可以获取到与MDT数据权限相对应的MDT数据。
在一种可能的实现方式中，所述根据所述MDT数据权限获取MDT数据，包括：根据所述MDT数据权限向所述核心网设备发送MDT数据请求；接收来自所述核心网设备的对应于所述MDT数据请求的响应，所述响应包括：MDT数据。在上述方案中，核心网设备能够向接入网设备发送MDT数据，从而使得接入网设备具有使用MDT数据的能力。
在一种可能的实现方式中，所述MDT数据包括：所述核心网设备缓存的处于非连接态的终端设备的非立即MDT数据，和/或处于连接态的终端设备多次向所述核心网设备发送的立即MDT数据。
在一种可能的实现方式中，所述根据所述MDT数据权限获取MDT数据，包括：根据所述MDT数据权限接收终端设备发送的MDT测量报告，所述MDT测量报告包括：MDT数据。在上述方案中，终端设备能够向接入网设备发送MDT数据，从而使得接入网设备具有使用MDT数据的能力。
在一种可能的实现方式中，所述MDT数据权限包括：MDT的用途信息，所述MDT的用途信息用于指示所述接入网设备向其它接入网设备传输所述MDT数据，所述方法还包括：向其它接入网设备传输所述MDT数据。在上述方案中，接入网设备可以根据该MDT的用途信息使用MDT数据，实现对MDT数据的正确使用，避免MDT数据泄露的风险。
在一种可能的实现方式中，所述第一信息包括：MDT类型的指示信息；所述MDT类型包括如下至少 一种：立即MDT、非立即MDT。
在一种可能的实现方式中，所述第一信息包括：执行MDT的终端设备的标识、MDT测量项、所述MDT测量项对应的MDT数据权限。
在一种可能的实现方式中，所述方法还包括：向所述核心网设备发送第一请求，所述第一请求用于向所述核心网设备请求MDT数据权限。在上述方案中，接入网设备可以请求核心网设备分配MDT数据权限，使得接入网设备能够灵活的请求所需的MDT数据权限。
在一种可能的实现方式中，所述方法还包括：向所述核心网设备发送第二请求，所述第二请求用于请求所述核心网设备修改MDT数据权限；接收来自所述核心网设备的第二信息；根据所述第二信息获取分配给所述接入网设备的修改后的MDT数据权限。在上述方案中，接入网设备接收到第二信息之后，解析该第二信息，可以获取到核心网设备分配给该接入网设备的修改后的MDT数据权限，从而使得接入网设备具有修改后的MDT数据权限，解决了接入网设备无法对MDT数据权限进行更新的问题，从而使用修改后的MDT数据权限能够获取到与修改后的MDT数据权限相对应的MDT数据。
在一种可能的实现方式中，所述方法还包括：向所述核心网设备发送第三请求，所述第三请求用于请求所述核心网设备修改MDT配置；接收来自所述核心网设备的第三信息；根据所述第三信息获取修改后的MDT配置。在上述方案中，接入网设备接收到第三信息之后，解析该第三信息，可以获取到核心网设备分配给该接入网设备的修改后的MDT配置，解决了接入网设备无法对MDT数据进行更新的问题，使用修改后的MDT配置能够获取到与修改后的MDT配置相对应的MDT数据。
在一种可能的实现方式中，所述修改后的MDT配置包括：对应于MDT测量项的修改后的触发条件、和/或，对应于MDT测量项的修改后的配置参数。
在一种可能的实现方式中，当MDT为立即MDT时，所述配置参数包含：所述MDT测量项的测量周期，和/或，所述MDT测量项的MDT事件触发配置参数；或者，当MDT为非立即MDT时，所述配置参数包含如下至少一项：所述MDT测量项的测量间隔，所述MDT测量项的测量持续时间，或者，所述MDT测量项的MDT事件触发配置参数。
第三方面，本申请实施例还提供一种通信装置，所述通信装置为核心网设备，包括：
处理模块，用于确定分配给接入网设备的最小化路测MDT数据权限；
发送模块，用于向所述接入网设备发送第一信息，所述第一信息用于指示所述MDT数据权限。
在本申请的第三方面中，通信装置的组成模块还可以执行前述第一方面以及各种可能的实现方式中所描述的步骤，详见前述对第一方面以及各种可能的实现方式中的说明。
第四方面，本申请实施例还提供一种通信装置，所述通信装置为核心网设备，包括：
接收模块，用于接收来自核心网设备的第一信息；
处理模块，用于根据所述第一信息获取分配给所述接入网设备的最小化路测MDT数据权限。
在本申请的第四方面中，通信装置的组成模块还可以执行前述第二方面以及各种可能的实现方式中所描述的步骤，详见前述对第二方面以及各种可能的实现方式中的说明。
第五方面，本申请实施例提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有指令，当其在计算机上运行时，使得计算机执行上述第一方面或第二方面所述的方法。
第六方面，本申请实施例提供了一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述第一方面或第二方面所述的方法。
第七方面，本申请实施例提供一种通信装置，该通信装置可以包括核心网设备或者接入网设备或者芯片等实体，所述通信装置包括：处理器、存储器；所述存储器用于存储指令；所述处理器用于执行所述存储器中的所述指令，使得所述通信装置执行如前述第一方面或第二方面中任一项所述的方法。
第八方面，本申请提供了一种芯片系统，该芯片系统包括处理器，用于支持核心网设备或者接入网设备实现上述方面中所涉及的功能，例如，发送或处理上述方法中所涉及的数据和/或信息。在一种可能的设计中，所述芯片系统还包括存储器，所述存储器，用于保存核心网设备或者接入网设备必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
第九方面，本申请提供了一种数据处理系统，该系统包括：如第三方面中任一项所述的核心网设备和第四方面中任一项所述的接入网设备。
从以上技术方案可以看出，本申请实施例具有以下优点：
在本申请实施例中，核心网设备确定分配给接入网设备的MDT数据权限，然后核心网设备向接入网设备发送第一信息，第一信息用于指示所述MDT数据权限。由于接入网设备可以获取到核心网设备分配给该接入网设备的MDT数据权限，从而接入网设备具有MDT数据权限，扩展了MDT数据的应用场景。
附图说明
图1为本申请实施例提供的数据处理方法应用的系统场景的一个示意图；
图2为本申请实施例提供的接入网设备的一个结构示意图；
图3为本申请实施例提供的数据处理方法的一个实施例示意图；
图4为本申请实施例提供的数据处理方法的另一个实施例示意图；
图5为本申请实施例提供的数据处理方法的另一个实施例示意图；
图6为本申请实施例提供的数据处理方法的另一个实施例示意图；
图7为本申请实施例提供的数据处理方法的另一个实施例示意图；
图8a为本申请实施例提供的数据处理方法的另一个实施例示意图；
图8b为本申请实施例提供的数据处理方法的另一个实施例示意图；
图9为本申请实施例提供的数据处理方法的另一个实施例示意图；
图10为本申请实施例提供的通信装置的一个结构示意图；
图11为本申请实施例提供的通信装置的另一个结构示意图；
图12为本申请实施例提供的数据处理系统的一个结构示意图。
具体实施方式
本申请实施例提供了一种数据处理方法和通信装置，用于接入网设备能够获取到MDT数据权限。
下面结合附图，对本申请的实施例进行描述。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的术语在适当情况下可以互换，这仅仅是描述本申请的实施例中对相同属性的对象在描述时所采用的区分方式。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，以便包含一系列单元的过程、方法、系统、产品或设备不必限于那些单元，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它单元。
本申请的技术方案可以应用于各种通信系统。例如，新无线(new radio，NR)系统、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)、通用移动通信系统(universal mobile telecommunication system，UMTS)、NR系统之后的移动通信系统(例如，6G移动通信系统)、车联网(vehicle to everything，V2X)通信系统等。
为便于理解本申请实施例的技术方案，下面结合图1示出了本申请实施例提供的方法适用的一种系统应用场景，本申请适用的通信系统包括核心网设备、接入网设备和终端设备。其中，接入网设备可以包括网络设备，核心网设备和接入网设备之间通过有线或者无线的方式进行通信传输，接入网设备与终端设备可以采用波束进行通信传输。
下面对本申请的核心网设备和网络设备、终端设备进行介绍。
如图1所示，本申请实施例的数据处理方法应用的系统架构中，可以包括：核心网(core network，CN)设备10、接入网设备20和终端设备30。
其中，核心网设备10可以和接入网设备20相连，例如核心网设备10具体可以是LTE的核心网设备，也可以是5G的核心网设备等。例如核心网设备10具体可以包括：接入和移动管理功能(access and mobility management function，AMF)实体，或者核心网设备10具体可以包括：移动管理实体(mobility management entity，MME)。核心网设备10具有分配和管理最小化路测(minimization of drive test，MDT)数据权限的能力。其中，MDT数据是指终端设备30执行MDT后生成的MDT测量报告中的数据。后 续实施例中以核心网设备10具体为AMF实体(后续简称为AMF)进行示例说明。
接入网设备20可以是无线网络中的设备，接入网设备20可以从核心网设备10获取到MDT数据权限，从而使用该MDT数据权限获取MDT数据。例如，接入网设备20可以是部署在无线接入网中为终端设备提供无线通信功能的设备。例如，接入网设备20可以为将终端设备接入到无线网络的无线接入网(radio access network，RAN)节点，接入网设备20又可以称为网络设备。本申请实施例中所涉及到的接入网设备可以是RAN中的接入网设备(如gNB、eNB)等，也可以是具有部分或全部接入网设备功能的设备，例如接入网设备20包含集中式单元(centralized unit，CU)和/或分布式单元(distributed unit,DU)。
如图2所示，本申请实施例提供的接入网设备的一个结构示意图。该接入网设备采用CU和DU的分离架构。CU和DU可以理解为是对接入网设备从逻辑功能角度的划分。CU和DU在物理上可以是分离的也可以部署在一起。多个DU可以共用一个CU。一个DU也可以连接多个CU(图中未示出)。CU和DU之间可以通过接口相连，例如可以是F1接口。CU和DU可以根据无线网络的协议层划分。例如其中一种可能的划分方式是：CU用于执行无线资源控制(radio resource control，RRC)层、业务数据适配协议(service data adaptation protocol，SDAP)层以及分组数据汇聚层协议(packet data convergence protocol，PDCP)层的功能，而DU用于执行无线链路控制(radio link control，RLC)层，媒体接入控制(media access control，MAC)层，物理(physical)层等的功能。可以理解的是，对CU和DU处理功能按照这种协议层的划分仅仅是一种举例，也可以按照其他的方式进行划分。例如可以将CU或者DU划分为具有更多协议层的功能。例如，CU或DU还可以划分为具有协议层的部分处理功能。在一种设计中，将RLC层的部分功能和RLC层以上的协议层的功能设置在CU，将RLC层的剩余功能和RLC层以下的协议层的功能设置在DU。在另一种设计中，还可以按照业务类型或者其他系统需求对CU或者DU的功能进行划分。例如按时延划分，将处理时间满足时延要求的功能设置在DU，不满足该时延要求的功能设置在CU。在另一种设计中，CU也可以具有核心网的一个或多个功能。一个或者多个CU可以集中设置，也分离设置。例如CU可以设置在网络侧方便集中管理。DU可以具有多个射频功能，也可以将射频功能拉远设置。
CU的功能可以由一个实体来实现也可以由不同的实体实现。例如，可以对CU的功能进行进一步切分，例如，将控制面(control plane，CP)和用户面(user plane，UP)分离，即CU的控制面(CU-CP)和CU用户面(CU-UP)。例如，CU-CP和CU-UP可以由不同的功能实体来实现，并通过E1接口相连，所述CU-CP和CU-UP可以与DU相耦合，共同完成接入网设备的功能。CU的控制面CU-CP还包括一种进一步切分的架构，即把现有的CU-CP进一步切分为CU-CP1和CU-CP2。其中CU-CP1包括各种无线资源管理功能，CU-CP2仅包括RRC功能和PDCP-C功能(即控制面信令在PDCP层的基本功能)。
在本申请实施例中，终端设备30可以是向用户提供语音和/或数据连通性的各类设备，也可以称为终端、用户设备(user equipment，UE)、移动台、移动终端等。终端设备30可以广泛应用于各种场景，例如，设备到设备(device-to-device，D2D)、车物(vehicle to everything，V2X)通信、机器类通信(machine-type communication，MTC)、物联网(internet of things，IOT)、虚拟现实、增强现实、工业控制、自动驾驶、远程医疗、智能电网、智能家具、智能办公、智能穿戴、智能交通、智慧城市等。终端设备30可以是手机、平板电脑、带无线收发功能的电脑、可穿戴设备、航空航天设备等。在本申请实施例中，应用于上述设备中的芯片也可以称为终端。本申请中以UE作为终端设备进行说明。
接下来对本申请实施例适用的MDT场景进行说明。
示例性的，首先对MDT场景中的MDT测量类型进行如下举例说明：
1.信号水平测量：由UE测量无线信号的信号水平，将测量结果上报给接入网设备。
2.服务质量(quality of service，Qos)测量：接入网设备执行Qos测量，比如，接入网设备可以测量业务的流量、业务的吞吐量，业务时延等，或者，也可以由UE测量，比如UE可以测量上行处理时延，也可以是接入网设备和UE联合处理，比如空口时延测量，其中，测量数据包经过接入网设备的SDAP/PDCP层到该数据包达到UE的SDAP/PDCP层的时间。
3.可接入性测量：由UE记录RRC连接建立失败的信息，并上报给接入网设备。
示例性的，接下来对MDT场景中的MDT进行说明，MDT包括非立即(logged)MDT和立即(immediate) MDT。
其中，loggedMDT是处于空闲态(idle)或非激活态(inactive)的UE进行的MDT。loggedMDT用于测量接收信号的强度。一般地，如果接入网设备配置UE处于空闲态或非激活态时执行MDT，当UE进入连接态时，UE不会再继续按照空闲态或非激活态时的MDT测量配置执行MDT。接入网设备为了获得测量结果，则可以配置UE处于连接态时执行的MDT测量。immediateMDT是处于连接态的UE进行的MDT。immediateMDT用于测量UE的数据量、吞吐率、包传输时延、丢包率或处理时延中的至少一项。
当UE处于连接态时，接入网设备给UE配置logged MDT测量配置，比如通过RRC消息中通知logged MDT测量配置。当UE进入到空闲态或非激活态时，UE按照对应的logged MDT测量配置记录对应的测量结果。当UE向接入网设备发起RRC连接时，在RRC消息中携带指示信息，该指示信息指示当前UE记录的logged MDT的测量结果。接入网设备可以向UE发送logged MDT的请求，UE再向接入网设备上报logged MDT的测量结果。
在上述loggedMDT场景和immediateMDT场景下，接入网设备可以分别发起MDT测量任务。MDT测量任务可以分为基于信令的MDT(signalling based MDT)，以及基于管理的MDT(management based MDT)。
首先对基于信令的MDT进行说明，基于信令的MDT是指针对特定UE的MDT，接入网设备从核心网设备收到对特定UE进行MDT的指示信息。对于基于信令的MDT而言，除非UE已经同意进行MDT，否则核心网设备并不会发起针对该UE的基于信令的MDT。对于基于信令的MDT，核心网设备将MDT配置信息、跟踪收集实体(trace collection entity，TCE)的互联网协议(internet protocol，IP)地址通知给接入网设备。其中，MDT配置信息包括如下至少一种：MDT类型，MDT测量范围，MDT配置参数，基于信令的MDT的公共陆地移动网(public land mobile network，PLMN)列表。例如，MDT类型可以包括immediate MDT和logged MDT，MDT配置参数包括：immediate MDT的测量事件和logged MDT的测量间隔和测量持续时间等。
接下来对基于管理的MDT进行说明，基于管理的MDT并不是针对特定UE的MDT，接入网设备从核心网设备收到进行MDT的指示信息。接入网设备可以从该接入网设备管理下的UE中选择一个或多个UE，针对选择出的一个或多个UE进行基于管理的MDT。对于基于管理的MDT，接入网设备在选择UE时，可以考虑UE是否同意进行MDT，比如只选择那些已经同意进行MDT的UE进行MDT，比如核心网设备向接入网设备发送指示信息，该指示信息指示一个或多个UE是否同意进行MDT。比如核心网设备向接入网设备发送基于管理的MDT允许指示(management based MDT allowed indication)信息，接入网设备根据基于管理的MDT允许指示信息确定同意进行MDT的UE。又如，核心网设备可以向接入网设备发送基于管理的MDT的PLMN列表，接入网设备根据基于管理的MDT的PLMN列表确定同意进行MDT的UE。
在MDT场景中，UE执行MDT之后，UE可以生成MDT数据，UE将该MDT数据发送给TCE，MDT数据可以从UE透传至TCE，接入网设备没有MDT数据权限，因此接入网设备无法使用MDT数据。例如，在RAN场景中，接入网设备无法从MDT数据中获取到连续的UE数据，该连续的UE数据是指UE在一段连续时间内执行MDT生成的数据，连续的UE数据包括如下至少一种：连续时间下UE的位置信息、参考信号接收功率(reference signal receiving power，RSRP)、参考信号质量(reference signal received quality，RSRQ)、信号与干扰加噪声比(signal to interference plus noise ratio，SINR)、丢包率、时延信息。接入网设备无法使用连续的UE数据作为人工智能(artificial intelligence，AI)模型的输入和推理信息，存在接入网设备无法进行AI模型的训练和推理的问题。本申请实施例MDT数据不限于AI模型的应用场景，可拓展于任何使用MDT数据的应用场景，例如对UE当前所在小区的信道质量的估计等。
为解决接入网设备没有MDT数据权限的问题，本申请实施例提出一种数据处理方法，解决了接入网设备无法获取MDT数据权限的问题。请参阅图3所示，为本申请实施例提供的核心网设备和接入网设备之间的一种交互流程示意图，包括如下步骤：
301、核心网设备确定分配给接入网设备的MDT数据权限。
其中，核心网设备具有分配MDT数据权限，核心网设备首先确定为接入网设备分配MDT数据权限。MDT数据权限指的是用于获取MDT数据以及使用MDT数据的权限。MDT数据权限由核心网设备分配给接入网设备。具体的，MDT数据权限可以包括如下至少一种：接入网设备能够获取到的MDT数据的类型，向接入网设备提供MDT数据的UE的标识(identifier，ID)，接入网设备使用MDT数据的用途，接入网 设备能够获取到的MDT数据对应的MDT测量项等。本申请实施例中对于核心网设备向接入网设备具体分配的MDT数据权限的方式不做限定。
例如，核心网设备可以向接入网设备分配的MDT数据权限为立即MDT数据，则接入网设备具有获取立即MDT数据的权限，而没有获取非立即MDT数据的权限。
又如，核心网设备可以向接入网设备分配的MDT数据权限为UE1执行MDT后生成的MDT数据，则接入网设备具有获取UE1的MDT数据的权限，而没有获取除UE1以外的其它UE的MDT数据的权限。具体的，UE可以授权是否执行MDT，对于针对不同UE可以分别由用户授权是否执行MDT，核心网设备只能针对授权执行MDT的UE，向接入网设备分配执行MDT的UE的标识，对于没有授权执行MDT的UE，核心网设备无法向接入网设备分配该UE执行MDT的权限。
又如，核心网设备向接入网设备分配MDT的用途的权限，能够使得接入网设备针对该MDT的用途使用MDT数据。例如核心网设备向接入网设备分配只能在接入网设备内部使用MDT数据权限，则接入网设备获取到MDT数据之后，只能在接入网设备的内部使用该MDT数据，而无法向其它接入网设备传输MDT数据。又如，核心网设备向接入网设备分配能够向外传输MDT数据权限，则接入网设备获取到MDT数据之后，可以在接入网设备的内部使用该MDT数据，也可以向其它接入网设备传输MDT数据。
又如核心网设备可以向接入网设备分配的MDT数据权限为UE执行第一MDT测量项后生成的MDT数据，则接入网设备具有获取UE执行第一MDT测量后生成的MDT数据的权限，而没有获取第一MDT测量项以外的其它MDT测量项对应的MDT数据的权限。
302、核心网设备向接入网设备发送第一信息，第一信息用于指示MDT数据权限。
示例性的，核心网设备为接入网设备分配MDT数据权限之后，可以生成第一信息，该第一信息用于指示MDT数据权限，然后核心网设备向接入网设备发送第一信息。例如该第一信息可以为MDT数据权限配置消息，或者第一信息还可以是控制信令，此处不做限定。
在本申请的一些实施方式中，第一信息包括：执行MDT的UE的指示信息。
示例性的，该执行MDT的UE的指示信息可以指示将执行MDT的UE的标识。核心网设备通过向接入网设备发送执行MDT的UE的指示信息，能够使得接入网设备针对该指示信息中指示的UE获取MDT数据。
在本申请的一些实施方式中，当MDT是基于管理的MDT时，执行MDT的UE的指示信息包括如下至少一种：执行MDT的UE的选取比例、执行MDT的UE的标识列表、执行MDT的UE的筛选条件；或者，
当MDT是基于信令的MDT时，执行MDT的UE的指示信息包括：执行MDT的UE的标识。
举例说明如下，从数据收集对象的角度将MDT分为基于信令的MDT和基于管理的MDT。详见前述内容对基于信令的MDT和基于管理的MDT的说明。
基于信令的MDT是针对特定UE的，执行MDT的UE的指示信息包括执行MDT的UE的标识，使得接入网设备可以根据执行MDT的UE的指示信息确定执行MDT的UE的标识，接入网设备可以针对执行MDT的UE获取MDT数据。在另一个实施方式中，若在第一信息中不包括执行MDT的UE的标识，则核心网设备默认对所有UE的MDT数据权限配置是一致的。
基于管理的MDT是针对指定区域范围的多个UE，指定区域范围的方式可以包括如下至少一种：执行MDT的UE的选取比例、执行MDT的UE的标识列表、执行MDT的UE的筛选条件。
其中，执行MDT的UE的选取比例的取值有多种，例如，执行MDT的UE的选取比例为5％，则接入网设备可以根据执行MDT的UE的选取比例从当前服务的所有UE中选择5％的UE执行MDT。执行MDT的UE的标识列表中包括执行MDT的UE的标识，接入网设备可以根据执行MDT的UE的标识列表选择该列表中的UE执行MDT。执行MDT的UE的筛选条件可用于接入网设备从当前服务的所有UE选择符合该筛选条件的UE执行MDT。本申请实施例中接入网设备可以通过第一信息指示接入网设备选择一个或多个UE执行MDT，接入网设备能够确定执行MDT的UE的权限，解决了接入网设备无法获取到MDT数据权限的问题。
在本申请的一些实施方式中，第一信息包括：MDT类型的指示信息；MDT类型包括如下至少一种：立即MDT、非立即MDT。关于立即MDT以及非立即MDT的详细介绍可以参照前述相关内容。
具体的，核心网设备通过向接入网设备发送MDT类型的指示信息，能够使得接入网设备针对该指示信息中指示的MDT类型获取MDT数据。例如核心网设备向接入网设备分配立即MDT数据权限，则接入网设备只能获取到立即MDT数据，而无法获取到非立即MDT数据。又如，核心网设备向接入网设备分配非 立即MDT数据权限，则接入网设备只能获取到非立即MDT数据，而无法获取到立即MDT数据。
在本申请的一些实施方式中，第一信息包括：MDT的用途信息。
MDT的用途信息用于指示MDT数据用途，包括：指示MDT数据应用于接入网设备内部，或者，指示MDT数据应用于接入网设备内部以及指示接入网设备向其它接入网设备传输MDT数据。关于MDT的用途的详细介绍可以参照前述相关内容。
举例说明如下，核心网设备指示MDT数据应用于接入网设备内部以及指示接入网设备向其它接入网设备传输MDT数据，接入网设备获取MDT数据后，接入网设备可以将该MDT数据输入本接入设备的AI模型进行模型训练或推理，接入网设备可以将该MDT数据发送给其它接入网设备，以使得其它接入网设备将该MDT数据用于该其它接入网设备的AI模型进行模型训练或推理。例如一个核心网设备为源接入网设备，其它核心网设备为目标接入网设备，源接入网设备通过通信接口向目标接入网设备发送MDT数据。例如，MDT的用途信息可以用1位比特值表示。在另一种实现方式中，若第一信息中不配置MDT的用途信息，则核心网设备默认对一个接入网设备可以在该接入网设备内部使用MDT数据，也可以将该MDT数据发送给其它接入网设备。
在本申请的一些实施方式中，第一信息包括：执行MDT的UE的标识、MDT测量项、以及MDT测量项对应的MDT数据权限。
其中，MDT可以是基于信令的MDT，第一信息包括：执行MDT的UE的标识，例如执行MDT的UE的标识可以通过前述的执行MDT的UE的指示信息确定。核心网设备通过向接入网设备发送执行MDT的UE的标识，能够使得接入网设备针对该第一信息中指示的UE获取MDT数据。
另外，MDT测量项具体可以为一项或者多项，对于MDT测量项的具体实现方式不做限定。例如，MDT为立即MDT，MDT测量项可以包括如下至少一种：M1，M2，M3，M4，M5，M6，M7，M8，M9,对上述MDT测量项的具体执行方式不再详细举例说明。例如，MDT为非立即MDT，MDT测量项可以包括如下至少一种：位置信息(locationInfo)，服务小区标识(servCellIdentity)，服务小区测量结果(measResultServingCell)，邻区测量结果(measResultNeighCells)，用于指示检测任何小区选择状态(anyCellSelectionDetected)由于设备内共存问题检测而暂停测量日志(inDeviceCoexDetected)，对于上述MDT测量项的具体执行方式不再详细举例说明。
MDT测量项对应的MDT数据权限是指核心网设备针对每个MDT测量项设置的MDT数据权限。例如一个MDT测量项对应的MDT数据权限为1，则表示核心网设备为接入网设备分配该MDT测量项对应的MDT数据权限。又如，一个MDT测量项对应的MDT数据权限为0，则表示核心网设备没有为接入网设备分配该MDT测量项对应的MDT数据权限。对于MDT数据权限的取值，不做限定。
进一步的，MDT可以分为立即MDT和非立即MDT，对于立即MDT的每个测量项，核心网设备可以配置MDT数据权限，例如立即MDT的MDT测量项为M1，M1对应的MDT数据权限为1，则表示核心网设备为接入网设备分配了MDT数据权限。对于非立即MDT的每个测量项，核心网设备可以配置MDT数据权限，例如非立即MDT的MDT测量项为位置信息，位置信息对应的MDT数据权限为0，则表示核心网设备没有为接入网设备分配MDT数据权限。
303、接入网设备接收来自核心网设备的第一信息。
304、接入网设备根据第一信息获取分配给接入网设备的MDT数据权限。
其中，接入网设备从核心网设备接收到第一信息之后，解析该第一信息，可以获取到核心网设备分配给该接入网设备的MDT数据权限，从而使得接入网设备具有了能够获取MDT数据的能力。
对于第一信息和MDT数据权限的说明，详见前述内容。
在本申请的一些实施方式中，接入网设备除了执行前述303和304以外，接入网设备执行的数据处理方法还包括如下步骤A1：
A1、接入网设备根据MDT数据权限获取MDT数据。
其中，接入网设备从核心网设备接收到MDT数据权限，则接入网设备可以使用该MDT数据权限，即接入网设备具有能够获取MDT数据的能力，接入网设备可以获取到与MDT数据权限相对应的MDT数据，对于接入网设备获取MDT数据的具体方式，详见后续实施例的举例说明。
举例说明如下，接入网设备对本接入网设备的AI模型进行模型训练或推理时，获取连续的UE数据 作为AI模型的输入和推理信息。接入网设备可以根据MDT数据权限获取到相应的MDT数据，接入网设备根据MDT数据获取连续的UE数据，对于MDT数据和连续UE数据的说明详见前述内容。
在本申请的一些实施方式中，步骤A1接入网设备根据MDT数据权限获取MDT数据，包括：
A11、接入网设备根据MDT数据权限接收UE发送的MDT测量报告，MDT测量报告包括：MDT数据。
具体的，接入网设备接收到MDT数据权限后，根据该MDT数据权限向UE下发MDT配置信息，UE根据该MDT配置信息执行MDT，然后UE生成MDT测量报告，UE向接入网设备发送MDT测量报告。
在本申请的一些实施方式中，MDT数据权限包括：MDT的用途信息，且MDT的用途信息用于指示接入网设备向其它接入网设备传输MDT数据。接入网设备除了执行前述303和304以外，接入网设备执行的数据处理方法还包括如下步骤B1：
B1、接入网设备向其它接入网设备传输MDT数据。
在该实施方式中，核心网设备向接入网设备分配的MDT数据权限指示接入网设备向其它接入网设备传输MDT数据，则接入网设备根据该MDT数据权限获取到了向外传输MDT数据的权限，则接入网设备获取到MDT数据之后，接入网设备可以向其它接入网设备传输MDT数据，解决了其它接入网设备无法获取到MDT数据的问题，例如其它接入网设备从具有MDT数据外发权限的接入网设备接收到MDT数据，该其它接入网设备从MDT数据获取到连续的UE数据，其它接入网设备将连续的UE数据输入到其它接入网设备的AI模型中进行模型训练或推理。
示例性的，当MDT的用途信息用于指示接入网设备向其它接入网设备传输MDT数据，第一信息中还可以包括外部使用MDT数据的小区PLMN信息、小区全局标识(cell global identifier，CGI)信息等。
本申请实施例中，核心网设备和接入网设备之间通过图3所示的方法进行交互，核心设备除了执行前述步骤301和步骤302，核心网设备还可以执行图4所示的步骤402和步骤403，接入网设备除了执行前述步骤303和步骤304，接入网设备还可以执行图4所示的步骤401和步骤404，对于前述实施例中涉及到的MDT数据权限，以及MDT数据等，不再详细说明，详见图3所示的实施例。请参阅图4所示，为本申请实施例提供的核心网设备和接入网设备之间的另一种交互流程示意图，包括如下步骤：
401、接入网设备根据MDT数据权限向核心网设备发送MDT数据请求。
其中，接入网设备通过前述图3所示的实施例获取到MDT数据权限之后，接入网设备根据MDT数据权限向核心网设备发送MDT数据请求。对于MDT数据权限的说明详见前述实施例。
402、核心网设备接收接入网设备根据MDT数据权限发送的MDT数据请求。
核心网设备接收来自接入网设备的MDT数据请求，根据MDT数据请求携带的MDT数据权限进行校验，当接入网设备通过MDT数据权限校验之后，执行后续步骤403。
403、核心网设备向接入网设备发送对应于MDT数据请求的响应，响应包括：MDT数据。
举例说明如下，核心网设备向接入网设备分配的是立即MDT数据权限，且分配的是UE1的标识，以及MDT测量项1，则核心网设备向接入网设备发送的MDT数据是UE1执行MDT测量项1得到的立即MDT数据。
又如，核心网设备向接入网设备分配的是非立即MDT数据权限，且分配的是UE2的标识，以及MDT测量项2，则核心网设备向接入网设备发送的MDT数据是UE2执行MDT测量项2得到的非立即MDT数据。
404、接入网设备接收来自核心网设备的对应于MDT数据请求的响应，响应包括：MDT数据。
接入网设备解析该响应可以获取到核心网设备分配给接入网设备的MDT数据。
在本申请的一些实施方式中，MDT数据包括：核心网设备缓存的处于非连接态的UE的非立即MDT数据，和/或处于连接态的UE多次向核心网设备发送的立即MDT数据。
其中，当处于连接态的UE执行立即MDT时，UE可以多次向接入网设备发送立即MDT的MDT数据。当处于非连接态的UE执行非立即MDT时，UE会缓存MDT数据。之后当UE向接入网设备发起RRC连接时会指示当前记录了非立即MDT的MDT数据，然后接入网设备可以向UE请求，由UE向接入网设备上报非立即MDT的MDT数据。另外，若接入网设备无法从UE获取到MDT数据，接入网设备可以向核心网设备或者TCE请求MDT数据。
本申请实施例中，核心网设备和接入网设备之间通过图3和图4所示的方法进行交互，核心设备除了执行前述步骤301和步骤302、步骤402和403，核心网设备还可以执行图5中所示的步骤502，接入 网设备除了执行前述步骤303和步骤304、步骤401和步骤404，接入网设备还可以执行图5所示的步骤501，对于前述实施例中涉及到的MDT数据权限，以及MDT数据等，不再详细说明，详见图3至图4所示的实施例。请参阅图5所示，为本申请实施例提供的核心网设备和接入网设备之间的另一种交互流程示意图，在前述步骤301执行之前，本申请实施例提供的方法还包括如下步骤：
501、接入网设备向核心网设备发送第一请求，第一请求用于向核心网设备请求MDT数据权限。
其中，接入网设备获取MDT数据时，接入网设备生成该第一请求。例如第一请求中可以具体包括如下至少一种：接入网设备请求获取的MDT类型、执行MDT的UE的标识、MDT测量项、MDT测量项对应的MDT数据权限等。对于MDT类型、执行MDT的UE的标识、MDT测量项、MDT测量项对应的MDT数据权限的说明，详见前述内容。
502、核心网设备接收该第一请求。
其中，核心网设备可以解析该第一请求，确定接入网设备向核心网设备请求的MDT数据权限。
对于MDT数据权限的说明，详见前述实施例。
在本申请的一些实施方式中，在核心网设备执行步骤502之后，核心网设备还可以执行图3中所示的步骤301和步骤302，此处不再详细说明。
在本申请的一些实施方式中，接入网设备在获取到MDT数据之后，若该MDT数据无法满足接入网设备的需求，则接入网设备可以向核心网设备请求修改MDT数据权限或者请求修改MDT配置，以解决当前MDT数据无法满足接入网设备需求的问题。如下以图6对接入网设备请求核心网设备修改MDT数据权限进行说明，如下以图7对接入网设备请求核心网设备修改MDT配置进行说明。
本申请实施例中，核心网设备和接入网设备之间通过图3、图4和图5所示的方法进行交互，核心设备除了执行前述步骤301和步骤302、步骤402和403、步骤502，核心网设备还可以执行图6中所示的步骤602至604，接入网设备除了执行前述步骤303和步骤304、步骤401和步骤404、步骤501，接入网设备还可以执行图6所示的步骤601、步骤605和步骤606，对于前述实施例中涉及到的MDT数据权限，以及MDT数据等，不再详细说明，详见图3至图5所示的实施例。
请参阅图6所示，为本申请实施例提供的核心网设备和接入网设备之间的另一种交互流程示意图，包括如下步骤：
601、接入网设备向核心网设备发送第二请求，第二请求用于请求核心网设备修改MDT数据权限。
其中，步骤601可以执行前述图3所示的步骤304之后执行。
第二请求中可以包括如下至少一种：接入网设备请求修改的MDT类型、请求修改的执行MDT的UE的标识、请求修改的MDT数据权限等。例如第二请求具体可以是MDT增量配置数据权限请求消息，或者第二请求具体可以是其它的请求消息，此处不做限定。接入网设备可以请求修改上述三种的任意一种或者多种，此处不做限定。对于MDT类型、执行MDT的UE的标识、MDT数据权限的说明，详细前述内容。
在本申请的一些实施方式中，修改MDT数据权限可以包括增加MDT数据权限，或者删除MDT数据权限。
602、核心网设备接收来自接入网设备的第二请求，第二请求用于请求核心网设备修改MDT数据权限。
603、核心网设备根据第二请求修改分配给接入网设备的MDT数据权限。
其中，核心网设备接收到第二请求之后，可以根据第二请求对分配给接入网设备的当前MDT数据权限进行修改，以满足接入网设备对修改MDT数据权限的要求。
604、核心网设备向接入网设备发送第二信息，第二信息用于指示修改后的MDT数据权限。
其中，核心网设备对分配给接入网设备的当前MDT数据权限进行修改完成之后，可以通过第二信息向接入网设备指示修改后的MDT数据权限。例如，第二信息具体可以是MDT配置和数据权限请求响应。
605、接入网设备接收来自核心网设备的第二信息。
606、接入网设备根据第二信息获取分配给接入网设备的修改后的MDT数据权限。
其中，接入网设备接收到第二信息之后，解析该第二信息，可以获取到核心网设备分配给该接入网设备的修改后的MDT数据权限，从而使得接入网设备具有修改后的MDT数据权限，解决了接入网设备无法对MDT数据权限进行更新的问题，从而使用修改后的MDT数据权限能够获取到与修改后的MDT数据权 限相对应的MDT数据。
前述图6对核心网设备修改MDT数据权限的方式进行了说明，在本申请的一些实施方式中，接入网设备在获取到MDT数据之后，若该MDT数据无法满足接入网设备的需求，则接入网设备可以向核心网设备请求修改MDT配置，以解决当前MDT数据无法满足接入网设备需求的问题。
本申请实施例中，核心网设备和接入网设备之间通过图3、图4、图5和图6所示的方法进行交互，核心设备除了执行前述步骤301和步骤302、步骤402和步骤403、步骤502、步骤602至604，核心网设备还可以执行图7中所示的步骤702至703，接入网设备除了执行前述步骤303和步骤304、步骤401和步骤404、步骤501、步骤601、步骤605、步骤606，接入网设备还可以执行图7所示的步骤701、步骤704和步骤705，对于前述实施例中涉及到的MDT数据权限，以及MDT数据等，不再详细说明，详见图3至图6所示的实施例。
请参阅图7所示，为本申请实施例提供的核心网设备和接入网设备之间的另一种交互流程示意图，包括如下步骤：
701、接入网设备向核心网设备发送第三请求，第三请求用于请求核心网设备修改MDT配置。
第三请求中可以包括如下至少一种：接入网设备请求修改的MDT类型、请求修改的执行MDT的UE的标识、请求修改的MDT测量项等。例如第三请求具体可以是MDT增量配置请求消息，或者第三请求具体可以是其它的请求消息，此处不做限定。接入网设备可以请求修改上述三种的任意一种或者多种，此处不做限定。对于MDT类型、执行MDT的UE的标识、MDT测量项的说明，详细前述内容。
在本申请的一些实施方式中，修改MDT配置可以包括增加MDT配置，或者删除MDT配置。
702、核心网设备接收来自接入网设备的第三请求，第三请求用于请求核心网设备修改MDT配置。
在本申请的一些实施方式中，第三请求和前述图6所示实施例的第二请求可以通过同一个消息发送，或者第三请求和前述的第二请求可以通过不同的消息发送，此处不做限定。
703、核心网设备向接入网设备发送第三信息，第三信息包括修改后的MDT配置。
其中，核心网设备接收到第三请求之后，可以根据第三请求对分配给接入网设备的当前MDT配置进行修改，以满足接入网设备对修改MDT配置的要求。
在本申请的一些实施方式中，第三信息和前述图6所述实施例的第二信息可以通过同一个消息发送，或者第三信息和前述的第二信息可以通过不同的消息发送，此处不做限定。
核心网设备对分配给接入网设备的当前MDT配置进行修改完成之后，可以确定修改后的MDT配置，核心网设备可以通过第三信息向接入网设备指示修改后的MDT配置。例如，第三信息具体可以是MDT配置请求响应。
在本申请的一些实施方式中，修改后的MDT配置包括：对应于MDT测量项的修改后的触发条件、和/或，对应于MDT测量项的修改后的配置参数。
其中，核心网设备可以修改MDT测量项的触发条件，从而通过修改触发条件，更改UE执行MDT的触发条件。或者，核心网设备可以修改一项或多项MDT测量项的配置参数。
在本申请的一些实施方式中，修改后的触发条件包括增加或者删除的触发条件。
其中，核心网设备可以增加触发条件，例如增加触发条件为AI模型训练或推理。另外，当接入网设备不使用原有的触发条件对应的MDT数据时，核心网设备还可以删除相应的触发条件。
在本申请的一些实施方式中，当MDT为立即MDT时，配置参数可以包括：MDT测量项的测量周期，和/或，MDT测量项的MDT事件触发配置参数。具体的，核心网设备可以修改MDT测量项的测量周期，例如增大或者缩短MDT测量项的测量周期。或者，核心网设备可以修改MDT事件触发配置参数。例如增加新的MDT事件触发配置参数或者删除原有的MDT事件触发配置参数或修改MDT事件触发配置参数的值。
当MDT为非立即MDT时，配置参数包括如下至少一项：MDT测量项的测量间隔，MDT测量项的测量持续时间，或者，MDT测量项的MDT事件触发配置参数。具体的，核心网设备可以修改MDT测量项的测量间隔，例如增大或者缩短MDT测量项的测量间隔。或者，核心网设备可以修改MDT测量项的测量持续时间。或者，核心网设备可以修改MDT事件触发配置参数。例如增加新的MDT事件触发配置参数或者删除原有的MDT事件触发配置参数或修改MDT事件触发配置参数的值。
例如，修改MDT事件触发配置参数可以包括：修改RSRP门限、或者修改RSRQ门限等。
704、接入网设备接收来自核心网设备的第三信息。
705、接入网设备根据第三信息获取修改后的MDT配置。
其中，接入网设备接收到第三信息之后，解析该第三信息，可以获取到核心网设备分配给该接入网设备的修改后的MDT配置，解决了接入网设备无法对MDT数据进行更新的问题，使用修改后的MDT配置能够获取到与修改后的MDT配置相对应的MDT数据。
为便于更好的理解和实施本申请实施例的上述方案，下面举例相应的应用场景来进行具体说明。
接下来以核心网设备具体为AMF、接入网设备具体为gNB进行示例说明，gNB使用MDT数据的方式有多种，接下来以gNB获取MDT数据用于AI模型的训练和推理为例。上述场景只是一种可实现方式，不作为对本申请实施例的限定。
实施例一
AMF向gNB发送MDT数据权限配置消息，gNB根据MDT数据权限获取MDT数据，gNB将获取到的MDT数据用于AI模型的输入和推理。gNB获取MDT数据的方式可以是gNB从UE直接获取MDT数据，若gNB无法从UE获取到MDT数据，gNB可以从AMF或者TCE获取MDT数据。
基于前述图3至图5所示的实施例，结合应用场景，对本申请提供的方案进行介绍，请参阅如图8a和图8b所示，为本申请实施例提供的数据处理方法的另一个实施例示意图，包括如下流程：
步骤801：AMF向gNB发送MDT数据权限配置消息。
AMF向gNB发送MDT数据权限配置消息，以便gNB获取AMF分配的MDT数据权限。
根据MDT数据的收集对象不同，MDT可以分为基于信令的MDT和基于管理的MDT。对于基于信令的MDT和基于管理的MDT的说明，详见前述相关内容。
由于MDT数据内容很多，AMF可能不会授权所有MDT数据，本申请实施例分两种授权情况，一种是AMF对不同UE的全部MDT数据统一配置MDT数据权限，另一种是AMF对不同UE的不同MDT数据分别配置MDT数据权限。
作为一种可能的实现方式，AMF对不同UE的全部MDT数据统一配置权限，此时MDT数据权限配置消息中不指示MDT测量报告中哪部分MDT数据被授权。MDT数据权限配置消息包括如下至少一种：执行MDT的UE的标识、立即MDT的数据权限、非立即MDT的数据权限。
例如，MDT数据权限配置消息包括的内容可以如下表1所示：

作为另一种可能的实现方式，AMF对不同UE的不同MDT数据分别配置权限，此时MDT数据权限配置消息可以指示MDT测量报告中具体哪部分数据被授权。MDT数据权限配置消息可以包括如下至少一种：执行MDT的UE的标识、立即MDT的测量项和相应的MDT数据权限、非立即的MDT的测量项和相应的MDT数据权限。
例如，MDT数据权限配置消息包括的内容可以如下表2所示：

步骤802：gNB从UE获取MDT数据。
如图8a所示，当处于连接态的UE执行立即MDT时，UE可以多次向gNB发送立即MDT的MDT数据。当处于非连接态的UE执行非立即MDT时，UE会缓存MDT数据。之后当UE向gNB发起RRC连接时会指示当前记录了非立即MDT的MDT数据，然后gNB可以向UE请求，由UE向gNB上报非立即MDT的MDT数据。
步骤803：gNB向AMF或者TCE发送MDT数据请求。
如图8b所示，gNB可以向AMF或者TCE请求MDT数据。图8a和图8b的区别在于获取MDT数据方式不同。
示例性的，当gNB释放了MDT数据或者非连接态UE恢复RRC连接态时发生了切换，gNB的本地是没有MDT数据的。此时，gNB根据AMF下发的MDT数据权限和AI模型的数据需求，gNB可以向AMF请求相应的MDT数据。MDT数据请求中指明MDT的用途用途信息、执行MDT的UE的标识和对应的MDT数据类型。
步骤804：AMF或者TCE向gNB发送MDT数据请求的响应。
通过实施例一，AMF给gNB下发了MDT数据权限，可以使得gNB能够合法获取MDT数据，并从中提取连续的UE数据作为AI模型的输入和推理数据，以提高gNB上部署的AI模型的推理或训练精度。
实施例二
基于前述图6至图7所示的实施例，结合应用场景，对本申请提供的方案进行介绍。如果gNB获取到的MDT数据不足以支撑AI模型的需求，则gNB可以向AMF发送MDT增量配置数据权限请求，AMF返回修改后的MDT数据配置和数据权限请求响应，然后gNB再将新的MDT配置下发给UE，以获取新的MDT测量报告，并从新的MDT测量报告中提取连续的UE数据。
请参阅如图9所示，为本申请实施例提供的数据处理方法的另一个实施例示意图，包括如下步骤：
步骤901：gNB向AMF发送MDT增量配置数据权限请求消息。
其中，MDT增量配置数据权限请求消息可以包括：gNB请求修改的触发条件、gNB请求修改的MDT测量项的配置参数。
对于触发条件和MDT测量项的配置参数的说明，详见前述内容。
MDT增量配置数据权限请求消息中可以包括：gNB请求修改MDT数据权限，或者gNB请求修改MDT配置。
对于基于信令的MDT，MDT增量配置数据权限请求消息可以包括如下至少一种：执行MDT的UE的标识、原有的MDT配置、修改的UE执行MDT的触发条件、立即MDT的数据权限、非立即MDT的数据权限。
其中，原有的MDT配置包括：执行MDT的触发条件、立即MDT的测量周期和上报次数、或非立即MDT的测量间隔和测量持续时间，修改的UE执行MDT的触发条件包括：AI模型训练或推理标识。
MDT增量配置数据权限请求消息可以定义如下表3：

对于修改立即MDT配置参数，以M1配置更新为例，如下表4所示：
对于M1配置条件的举例，如下表5所示：

对于修改非立即MDT配置参数，可定义基于如表3中所示的非立即MDT触发事件的配置更新，如下表6所示：
对于基于管理的MDT，MDT增量配置数据权限请求消息可以包括如下至少一种：执行MDT的UE的筛选条件、原有的MDT配置、修改的UE执行MDT的触发条件、立即MDT的数据权限、非立即MDT的数据权限。原有的MDT配置、修改的UE执行MDT的触发条件、立即MDT的数据权限、非立即MDT的数据权限，与前述基于信令的MDT相同，如表3所示。
修改的UE执行MDT的触发条件可以定义如下表7所示：
步骤902：AMF向gNB发送MDT增量配置数据权限请求响应。
AMF根据gNB发送MDT增量配置数据权限请求向gNB发送gNB发送MDT增量配置数据权限请求响应，gNB发送MDT增量配置数据权限请求响应包括：修改后的MDT数据权限和修改后的MDT配置。对于修改后的MDT数据权限和修改后的MDT配置的说明，详见前述内容。
步骤903：gNB向UE下发MDT配置。
gNB通过步骤902接收到新的MDT配置后，向UE下发MDT配置。
步骤904：UE向gNB发送MDT测量报告。
UE基于步骤903接收到MDT配置之后，UE执行MDT，生成MDT测量报告，并将MDT测量报告发送给gNB。
步骤905：gNB获取UE数据。
gNB从MDT数据中获取连续的UE数据，连续的UE数据包括非连接态UE的非立即MDT数据和连接态UE多次上报的立即MDT数据。
通过实施例二，gNB可以根据AI模型的需求向AMF请求MDT增量配置数据权限，以使得gNB能够合法获取的MDT数据，并从MDT数据中提取连续的UE数据作为AI模型的输入和推理数据，以提高gNB上部署的AI模型的推理或训练精度。
可以理解的是，对于前述的各方法实施例，为了简单描述，故将其都表述为一系列的动作组合，但是本领域技术人员应该知悉，本申请并不受所描述的动作顺序的限制，因为依据本申请，某些步骤可以采用其他顺序或者同时进行。其次，本领域技术人员也应该知悉，说明书中所描述的实施例所涉及的动作和模块并不一定是本申请所必须的。
为便于更好的实施本申请实施例的上述方案，下面还提供用于实施上述方案的相关装置。
上述各个方法实施例可以单独实施，也可以结合实施。各实施例中涉及的术语和相关技术可以互相参考。也就是说不同实施例之间不矛盾或逻辑上没有冲突的技术方案之间是可以相互结合的，具体本申请不做限定。
下面对本申请实施例提供的通信装置进行描述。
图10为本申请实施例提供的通信装置的一个结构示意图。请参阅图10，通信装置可以用于执行图3至图7所示的实施例中核心网设备执行的过程，或者通信装置可以用于执行图3至图7所示的实施例中接入网设备执行的过程，具体请参考上述方法实施例中的相关介绍。
通信装置1000包括处理模块1001和收发模块1002。收发模块1002可以实现相应的通信功能，处理模块1001用于进行数据处理。收发模块1002还可以称为通信接口或通信模块。
可选的，该通信装置1000还可以包括存储模块，该存储模块可以用于存储指令和/或数据，处理模块1001可以读取存储模块中的指令和/或数据，以使得通信装置实现前述方法实施例。
该通信装置1000可以用于执行上文方法实施例中通信装置所执行的动作。该通信装置1000可以为通信装置或者可配置于通信装置的部件。处理模块1001用于执行上文方法实施例中通信装置侧的处理相关的操作。可选的，收发模块1002用于执行上文方法实施例中通信装置侧的接收相关的操作。
可选的，收发模块1002可以包括发送模块和接收模块。发送模块用于执行上述方法实施例中的发 送操作。接收模块用于执行上述方法实施例中的接收操作。
可以理解的是，通信装置1000可以包括发送模块，而不包括接收模块。或者，通信装置1000可以包括接收模块，而不包括发送模块。具体可以视通信装置1000执行的上述方案中是否包括发送动作和接收动作。
应理解，各模块执行上述相应过程的具体过程在上述方法实施例中已经详细说明，为了简洁，在此不再赘述。
上文实施例中的处理模块1001可以由至少一个处理器或处理器相关电路实现。收发模块1001可以由收发器或收发器相关电路实现。收发模块1002还可称为通信模块或通信接口。存储模块可以通过至少一个存储器实现。
在一个实施方式中，该通信装置用于执行上文方法实施例中核心网设备所执行的前述步骤301和步骤302、步骤402和403、步骤502、步骤602至604、步骤702至703。
在一个实施方式中，该通信装置用于执行上述方法实施例中接入网设备所执行的步骤303和步骤304、步骤401和步骤404、步骤501、步骤601、步骤605、步骤606、步骤701、步骤704和步骤705。
图11示出了一种简化的通信装置的结构示意图。如图11所示，通信装置包括处理器、存储器、以及收发器。存储器可以存储计算机程序代码，收发器包括发射机1131、接收机1132、天线1133以及输入输出装置(图中未示出)。
处理器主要用于对通信协议以及通信数据进行处理，以及对通信装置进行控制，执行软件程序，处理软件程序的数据等。存储器主要用于存储软件程序和数据。
当发送数据时，处理器对待发送的数据进行基带处理后，输出基带信号至射频电路，射频电路将基带信号进行射频处理后将射频信号通过天线以电磁波的形式向外发送。当有数据发送到通信装置时，射频电路通过天线接收到射频信号，将射频信号转换为基带信号，并将基带信号输出至处理器，处理器将基带信号转换为数据并对该数据进行处理。为便于说明，图11中仅示出了一个存储器、处理器和收发器，在实际的通信装置产品中，可以存在一个或多个处理器和一个或多个存储器。存储器也可以称为存储介质或者存储设备等。存储器可以是独立于处理器设置，也可以是与处理器集成在一起，本申请实施例对此不做限制。
在本申请实施例中，可以将具有收发功能的天线和射频电路视为通信装置的收发模块，将具有处理功能的处理器视为通信装置的处理模块。
如图11所示，通信装置包括处理器1110、存储器1120和收发器1130。处理器1110也可以称为处理单元，处理单板，处理模块、处理装置等，收发器1130也可以称为收发单元、收发机、收发装置等。
可选的，将收发器1130中用于实现接收功能的器件视为接收模块，将收发器1130中用于实现发送功能的器件视为发送模块，即收发器1130包括接收器和发送器。收发器有时也可以称为收发机、收发模块、或收发电路等。接收器有时也可以称为接收机、接收模块、或接收电路等。发送器有时也可以称为发射机、发射模块或者发射电路等。
应理解，图11仅为示例而非限定，上述包括收发模块和处理模块的通信装置可以不依赖于图11所示的结构。
当该通信装置1100为芯片时，该芯片包括处理器、存储器和收发器。其中，收发器可以是输入输出电路或通信接口；处理器可以为该芯片上集成的处理模块或者微处理器或者集成电路。上述方法实施例中通信装置的发送操作可以理解为芯片的输出，上述方法实施例中通信装置的接收操作可以理解为芯片的输入。
在一个实施方式中，该通信装置用于执行上文方法实施例中核心网设备所执行的前述步骤301和步骤302、步骤402和403、步骤502、步骤602至604、步骤702至步骤703。
在一个实施方式中，该通信装置用于执行上述方法实施例中接入网设备所执行的步骤303和步骤304、步骤401和步骤404、步骤501、步骤601、步骤605、步骤606、步骤701、步骤704和步骤705。
本申请实施例还提供一种计算机可读存储介质，其上存储有用于实现上述方法实施例中由终端设备或网络设备执行的方法的计算机指令。
例如，该计算机程序被计算机执行时，使得该计算机可以实现上述方法实施例中由终端设备或网络 设备执行的方法。
本申请实施例还提供一种包含指令的计算机程序产品，该指令被计算机执行时使得该计算机实现上述方法实施例中由终端设备或网络设备执行的方法。
如图12所示，本申请实施例还提供一种数据处理系统，该通信系统包括上文实施例中的核心网设备和接入网设备。
本申请实施例还提供一种芯片装置，包括处理器，用于调用该存储器中存储的计算机程度或计算机指令，以使得该处理器执行上述图3至图7所示的实施例的方法。
一种可能的实现方式中，该芯片装置的输入对应上述图3至图7所示的实施例中的接收操作，该芯片装置的输出对应上述图3至图7所示的实施例中的发送操作。
可选的，该处理器通过接口与存储器耦合。
可选的，该芯片装置还包括存储器，该存储器中存储有计算机程度或计算机指令。
其中，上述任一处提到的处理器，可以是一个通用中央处理器，微处理器，特定应用集成电路(application-specific integrated circuit，ASIC)，或一个或多个用于控制上述图3至图7所示的实施例的方法的程序执行的集成电路。上述任一处提到的存储器可以为只读存储器(read-only memory，ROM)或可存储静态信息和指令的其他类型的静态存储设备，随机存取存储器(random access memory，RAM)等。
所属领域的技术人员可以清楚地了解到，为描述方便和简洁，上述提供的任一种通信装置中相关内容的解释及有益效果均可参考上文提供的对应的方法实施例，此处不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的应用场景选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
所述集成的单元如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、ROM、RAM、磁碟或者光盘等各种可以存储程序代码的介质。
本申请的各个实施例中的内容可以相互参考，如果没有特殊说明以及逻辑冲突，不同的实施例之间的术语和/或描述具有一致性、且可以相互引用，不同的实施例中的技术特征根据其内在的逻辑关系可以组合形成新的实施例。
可以理解的，本申请实施例中，网络设备和/或终端设备可以执行本申请实施例中的部分或全部步骤，这些步骤或操作仅是示例，本申请实施例中，还可以执行其它操作或者各种操作的变形。此外，各个步骤可以按照本申请实施例呈现的不同的顺序来执行，并且有可能并非要执行本申请实施例中的全部操作。

Claims (33)

  1. 一种数据处理方法，其特征在于，所述方法应用于核心网设备，所述方法包括：
    确定分配给接入网设备的最小化路测MDT数据权限；
    向所述接入网设备发送第一信息，所述第一信息用于指示所述MDT数据权限。
  2. 根据权利要求1所述的方法，其特征在于，所述第一信息包括：执行MDT的终端设备的指示信息。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一信息包括：MDT类型的指示信息；所述MDT类型包括如下至少一种：立即MDT、非立即MDT。
  4. 根据权利要求1至3中任一项所述的方法，其特征在于，所述第一信息包括：MDT的用途信息；
    所述MDT的用途信息，用于指示MDT数据应用于所述接入网设备内部，或者，指示MDT数据应用于所述接入网设备内部以及指示所述接入网设备向其它接入网设备传输所述MDT数据。
  5. 根据权利要求1至4中任一项所述的方法，其特征在于，所述第一信息包括：执行MDT的终端设备的标识、MDT测量项、所述MDT测量项对应的MDT数据权限。
  6. 根据权利要求1至5中任一项所述的方法，其特征在于，所述方法还包括：
    接收所述接入网设备根据所述MDT数据权限发送的MDT数据请求；
    向所述接入网设备发送对应于所述MDT数据请求的响应，所述响应包括：MDT数据。
  7. 根据权利要求6所述的方法，其特征在于，所述MDT数据包括：所述核心网设备缓存的处于非连接态的终端设备的非立即MDT数据，和/或处于连接态的终端设备多次向所述核心网设备发送的立即MDT数据。
  8. 根据权利要求1至7中任一项所述的方法，其特征在于，所述方法还包括：
    接收来自所述接入网设备的第一请求，所述第一请求用于向所述核心网设备请求所述MDT数据权限。
  9. 根据权利要求1至8中任一项所述的方法，其特征在于，所述方法还包括：
    接收来自所述接入网设备的第二请求，所述第二请求用于请求所述核心网设备修改MDT数据权限；
    根据所述第二请求修改分配给所述接入网设备的MDT数据权限；
    向所述接入网设备发送第二信息，所述第二信息用于指示所述修改后的MDT数据权限。
  10. 根据权利要求9所述的方法，其特征在于，所述第二信息包括：执行MDT的终端设备的指示信息。
  11. 根据权利要求2或10所述的方法,其特征在于，当所述MDT是基于管理的MDT时，所述终端设备的指示信息包括如下至少一种：终端设备选取比例、终端设备标识列表、终端设备筛选条件；或者，
    当所述MDT是基于信令的MDT时，所述终端设备的指示信息包括：所述终端设备的标识。
  12. 根据权利要求1至11中任一项所述的方法，其特征在于，所述方法还包括：
    接收来自所述接入网设备的第三请求，所述第三请求用于请求所述核心网设备修改MDT配置；
    向所述接入网设备发送第三信息，所述第三信息包括修改后的MDT配置。
  13. 根据权利要求12所述的方法，其特征在于，所述修改后的MDT配置包括：对应于MDT测量项的修改后的触发条件、和/或，对应于MDT测量项的修改后的配置参数。
  14. 根据权利要求13所述的方法，其特征在于，当MDT为立即MDT时，所述配置参数包含：所述MDT测量项的测量周期，和/或，所述MDT测量项的MDT事件触发配置参数；或者，
    当MDT为非立即MDT时，所述配置参数包含如下至少一项：所述MDT测量项的测量间隔，所述MDT测量项的测量持续时间，或者，所述MDT测量项的MDT事件触发配置参数。
  15. 根据权利要求13或14所述的方法，其特征在于，所述修改后的触发条件包括增加或者删除的触发条件。
  16. 一种数据处理方法，其特征在于，所述方法应用于接入网设备，所述方法包括：
    接收来自核心网设备的第一信息；
    根据所述第一信息获取分配给所述接入网设备的最小化路测MDT数据权限。
  17. 根据权利要求16所述的方法，其特征在于，所述方法还包括：
    根据所述MDT数据权限获取MDT数据。
  18. 根据权利要求17所述的方法，其特征在于，所述根据所述MDT数据权限获取MDT数据，包括：
    根据所述MDT数据权限向所述核心网设备发送MDT数据请求；
    接收来自所述核心网设备的对应于所述MDT数据请求的响应，所述响应包括：MDT数据。
  19. 根据权利要求18所述的方法，其特征在于，所述MDT数据包括：所述核心网设备缓存的处于非连接态的终端设备的非立即MDT数据，和/或处于连接态的终端设备多次向所述核心网设备发送的立即MDT数据。
  20. 根据权利要求17所述的方法，其特征在于，所述根据所述MDT数据权限获取MDT数据，包括：
    根据所述MDT数据权限接收终端设备发送的MDT测量报告，所述MDT测量报告包括：MDT数据。
  21. 根据权利要求16至20中任一项所述的方法，其特征在于，所述MDT数据权限包括：MDT的用途信息，所述MDT的用途信息用于指示所述接入网设备向其它接入网设备传输所述MDT数据，所述方法还包括：
    向其它接入网设备传输所述MDT数据。
  22. 根据权利要求16至21中任一项所述的方法，其特征在于，所述第一信息包括：MDT类型的指示信息；所述MDT类型包括如下至少一种：立即MDT、非立即MDT。
  23. 根据权利要求16至22中任一项所述的方法，其特征在于，所述第一信息包括：执行MDT的终端设备的标识、MDT测量项、所述MDT测量项对应的MDT数据权限。
  24. 根据权利要求16至23中任一项所述的方法，其特征在于，所述方法还包括：
    向所述核心网设备发送第一请求，所述第一请求用于向所述核心网设备请求MDT数据权限。
  25. 根据权利要求16至24中任一项所述的方法，其特征在于，所述方法还包括：
    向所述核心网设备发送第二请求，所述第二请求用于请求所述核心网设备修改MDT数据权限；
    接收来自所述核心网设备的第二信息；
    根据所述第二信息获取分配给所述接入网设备的修改后的MDT数据权限。
  26. 根据权利要求16至25中任一项所述的方法，其特征在于，所述方法还包括：
    向所述核心网设备发送第三请求，所述第三请求用于请求所述核心网设备修改MDT配置；
    接收来自所述核心网设备的第三信息；
    根据所述第三信息获取修改后的MDT配置。
  27. 根据权利要求26所述的方法，其特征在于，所述修改后的MDT配置包括：对应于MDT测量项的修改后的触发条件、和/或，对应于MDT测量项的修改后的配置参数。
  28. 根据权利要求27所述的方法，其特征在于，当MDT为立即MDT时，所述配置参数包含：所述MDT测量项的测量周期，和/或，所述MDT测量项的MDT事件触发配置参数；或者，
    当MDT为非立即MDT时，所述配置参数包含如下至少一项：所述MDT测量项的测量间隔，所述MDT测量项的测量持续时间，或者，所述MDT测量项的MDT事件触发配置参数。
  29. 一种通信装置，其特征在于，包括：处理器，存储器；所述处理器、所述存储器之间进行相互的通信；
    所述存储器用于存储指令；
    所述处理器用于执行所述存储器中的所述指令，执行如权利要求1至15中任一项所述的方法。
  30. 一种通信装置，其特征在于，包括：处理器，存储器；所述处理器、所述存储器之间进行相互的通信；
    所述存储器用于存储指令；
    所述处理器用于执行所述存储器中的所述指令，执行如权利要求16至28中任一项所述的方法。
  31. 一种数据处理系统，其特征在于，所述系统包括：核心网设备和接入网设备，其中，
    所述核心网设备，用于执行如权利要求1至15中任一项所述的方法；
    所述接入网设备，用于执行如权利要求16至28中任一项所述的方法。
  32. 一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机执行如权利要求1-15，或者16-28任意一项所述的方法。
  33. 一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行如权利要求1-15，或者16-28任意一项所述的方法。
PCT/CN2023/116651 2022-11-03 2023-09-04 一种数据处理方法和通信装置 WO2024093498A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211373651.6 2022-11-03
CN202211373651.6A CN117998393A (zh) 2022-11-03 2022-11-03 一种数据处理方法和通信装置

Publications (1)

Publication Number Publication Date
WO2024093498A1 true WO2024093498A1 (zh) 2024-05-10

Family

ID=90892302

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/116651 WO2024093498A1 (zh) 2022-11-03 2023-09-04 一种数据处理方法和通信装置

Country Status (2)

Country Link
CN (1) CN117998393A (zh)
WO (1) WO2024093498A1 (zh)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103037353A (zh) * 2011-09-29 2013-04-10 中兴通讯股份有限公司 信息传输、实现最小化路测的方法、核心网及接入网设备
CN103037412A (zh) * 2011-09-29 2013-04-10 中兴通讯股份有限公司 一种最小化路测相关信息发送方法及无线接入网
US20140052871A1 (en) * 2011-08-15 2014-02-20 Nokia Siemems Networks Oy Methods And Apparatus For Management Of Data Privacy
CN111586740A (zh) * 2019-02-15 2020-08-25 华为技术有限公司 最小化路测技术配置方法和基站
CN112788656A (zh) * 2019-11-07 2021-05-11 北京三星通信技术研究有限公司 Mdt测量的汇报方法、配置方法、装置、电子设备及介质
CN113259191A (zh) * 2020-02-13 2021-08-13 华为技术有限公司 用于配置最小化路测mdt的方法和装置
CN114788384A (zh) * 2019-12-25 2022-07-22 华为技术有限公司 通信方法及装置

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140052871A1 (en) * 2011-08-15 2014-02-20 Nokia Siemems Networks Oy Methods And Apparatus For Management Of Data Privacy
CN103037353A (zh) * 2011-09-29 2013-04-10 中兴通讯股份有限公司 信息传输、实现最小化路测的方法、核心网及接入网设备
CN103037412A (zh) * 2011-09-29 2013-04-10 中兴通讯股份有限公司 一种最小化路测相关信息发送方法及无线接入网
CN111586740A (zh) * 2019-02-15 2020-08-25 华为技术有限公司 最小化路测技术配置方法和基站
CN112788656A (zh) * 2019-11-07 2021-05-11 北京三星通信技术研究有限公司 Mdt测量的汇报方法、配置方法、装置、电子设备及介质
CN114788384A (zh) * 2019-12-25 2022-07-22 华为技术有限公司 通信方法及装置
CN113259191A (zh) * 2020-02-13 2021-08-13 华为技术有限公司 用于配置最小化路测mdt的方法和装置

Also Published As

Publication number Publication date
CN117998393A (zh) 2024-05-07

Similar Documents

Publication Publication Date Title
US20220408282A1 (en) Communication method and apparatus
US11678153B2 (en) Information transmission and reception method and apparatus
EP4072226A1 (en) Communication method and apparatus
WO2021213481A1 (zh) 用于体验质量测量结果发送的通信方法及装置
US20220210031A1 (en) Method for Quality of Experience Measurement and Communication Apparatus
WO2014094309A1 (zh) 最小化路测测量方法、用户设备和网络设备
WO2022082727A1 (zh) 通信方法，装置，可读存储介质和系统
CN113747478A (zh) 通信方法及装置
WO2016045418A1 (zh) 一种参考信号接收质量上报方法及装置
US20220386160A1 (en) Method for reporting and configuring mdt measurement, apparatus and electronic device using the same and medium
CN116250272A (zh) 一种信息处理方法及装置
JP2023525836A (ja) 通信方法および通信装置
CN114501511A (zh) 测量方法和测量装置
WO2016019743A1 (zh) 一种上报信息的方法、设备及存储介质
US20220330371A1 (en) Wireless communication method, apparatus, and system
WO2021027907A1 (zh) 通信方法和通信装置
WO2021204274A1 (zh) 一种测量对象指示方法与装置
WO2016161771A1 (zh) 一种最小化路测方法及装置
WO2021027660A1 (zh) 无线通信的方法和通信装置
WO2024093498A1 (zh) 一种数据处理方法和通信装置
US20230030697A1 (en) Information Transmission Method and Related Device
WO2022032690A1 (zh) 通信方法、装置及系统
CN114731544B (zh) 一种基于网络切片的数据传输方法、装置和系统
WO2024007345A1 (zh) 测量获取方法和装置
WO2022032687A1 (zh) 通信的方法和通信装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23884435

Country of ref document: EP

Kind code of ref document: A1