Communication method and device
By sending MDT configuration information to newly connected network devices when the terminal device state changes, the problem that the terminal device cannot continuously perform MDT measurements is solved, and the acquisition of continuous MDT data is achieved, and the effect of network optimization and AI model training is improved.
Patent Information
- Application Number
- CN202311008107.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-08-10
- Publication Date
- 2025-02-18
AI Technical Summary
When the RRC state changes, terminal devices may not be able to continuously perform minimizing road test (MDT), resulting in reduced network optimization effect, especially in scenarios such as AI model training.
After the terminal device enters the connected state from the idle state, MDT configuration information is sent to the newly connected second network device, the second network device can obtain the MDT configuration through the previously connected first network device and send it to the terminal device, thereby Maintain the continuity of MDT.
It realizes that the terminal device maintains the continuity of MDT when the RRC state changes, ensures that the network device can obtain continuous MDT data, and improves the accuracy and application effect of AI model training.
Smart Images

Figure CN119485355A_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present application relate to the field of communication technologies, and in particular, to communication methods and devices. Background Art
[0002] In the field of mobile communications, the mobile communication network can be monitored through minimization of drive-test (MDT). MDT refers to the use of measurement reports with location information reported by terminal devices to discover problems such as weak coverage, coverage holes, and over-coverage in the mobile communication network, thereby optimizing the mobile communication network.
[0003] In some scenarios, such as artificial intelligence (AI) model training, terminal devices are expected to perform continuous MDT, so that network devices can obtain continuous MDT data to improve the effect of network optimization.
[0004] However, if the radio resource control (RRC) state of the terminal device changes, the terminal device may not be able to continuously perform MDT measurements. Summary of the invention
[0005] The embodiment of the present application provides a communication method and apparatus, which can enable a terminal device to maintain the continuity of MDT. To achieve the above purpose, the embodiment of the present application adopts the following technical solutions:
[0006] In a first aspect, an embodiment of the present application provides a communication method, which can be executed by a terminal device, or by a module (such as a processor, a chip or a chip system, etc.) applied to the terminal device, or by a logical node, a logical module or software that can implement all or part of the functions of the terminal device. The method includes: receiving first information from a first network device. Sending the above-mentioned first information to a second network device. Receive a second MDT configuration from the above-mentioned second network device. Perform MDT measurement according to the above-mentioned second MDT configuration. The above-mentioned first information is used to indicate a first MDT configuration, and the above-mentioned first MDT configuration includes an MDT configuration corresponding to the terminal device. The above-mentioned second MDT configuration is obtained based on the above-mentioned first MDT configuration.
[0007] It can be seen that in the method provided in the embodiment of the present application, after the terminal device enters the connected state from the idle state, the terminal device can send the first information indicating the MDT configuration corresponding to the terminal device to the newly connected second network device, so that the second network device uses the first information to obtain the MDT configuration through the first network device previously connected to the terminal device and sends the MDT configuration to the terminal device, thereby avoiding the terminal device stopping the MDT measurement because the newly connected network device did not send the second MDT configuration to the terminal device. In this way, the continuity of the MDT can be maintained, thereby obtaining continuous MDT data, so as to meet the need to obtain continuous MDT data in some scenarios. For example, the network device obtains continuous MDT data for the training of the AI model, thereby improving the accuracy of the AI model training and improving the effect of applying the AI model.
[0008] In a possible implementation, the first information may be saved before disconnecting from the first network device, thereby preventing the terminal device from being unable to send the first information to the second network device due to releasing the first information after disconnecting from the first network device, thereby causing MDT interruption.
[0009] In a possible implementation manner, the first information may be sent to the second network device after establishing a connection with the second network device, so that the terminal device may obtain the second MDT configuration from the second network device to maintain the continuity of the MDT measurement.
[0010] In a possible implementation manner, the second MDT configuration may include an immediate minimization of drive tests (ImmediateMDT) configuration.
[0011] Exemplarily, the terminal device can measure information or parameters such as the terminal device data volume, Internet protocol (IP) throughput, packet transmission delay, packet loss rate, and processing delay through the Immediate MDT configuration in the second MDT configuration.
[0012] In a possible implementation manner, the first information may include an index of the first MDT configuration.
[0013] It is understandable that the first network device may store the MDT configurations corresponding to multiple terminal devices. The index of the first MDT configuration helps the first network device to determine the MDT configuration corresponding to the terminal device from the MDT configurations corresponding to the multiple terminal devices.
[0014] In one possible implementation, the indexes of multiple MDT configurations may be stored in the second network device in the form of an index list. The second network device may search for the index corresponding to the aforementioned terminal device in the index list, and then send the first information to the first network device to indicate the need to obtain the MDT configuration of the terminal device, i.e., the aforementioned first MDT configuration.
[0015] In a possible implementation, second information may be received from the first network device, and the second information may be sent to the second network device, wherein the second information is used to indicate first MDT data, and the first MDT data is measured according to the first MDT configuration.
[0016] It should be noted that in some scenarios, network devices need to obtain continuous MDT data, such as training AI models through continuous MDT data. To this end, the terminal device can send second information indicating the first MDT data measured through the first MDT configuration to the newly connected second network device, so that the second network device uses the second information to obtain the first MDT data through the first network device previously connected to the terminal device. By training the AI model with the first MDT data, the model's prediction accuracy for data (such as the terminal's future throughput and trajectory information) can be improved, thereby improving the effect of network optimization.
[0017] In a possible implementation manner, the second information may include an index of the first MDT data.
[0018] It is understandable that the first network device may store a plurality of MDT data. The index of the first MDT data helps the first network device to determine the first MDT data from the plurality of MDT data.
[0019] In one possible implementation, the indexes of multiple MDT data can be stored in the second network device in the form of an index list. The second network device can search for the index corresponding to the aforementioned terminal device in the index list, and then send second information to the first network device to indicate the need to obtain the MDT data corresponding to the terminal device, namely the aforementioned first MDT data.
[0020] In a second aspect, an embodiment of the present application provides a communication method, which can be executed by a network device, or by a module (such as a processor, a chip or a chip system, etc.) applied to the network device, or by a logical node, a logical module or software that can implement all or part of the network device functions. The method includes: receiving first information from a second network device, the first information is used to indicate a first MDT configuration, the first MDT configuration includes an MDT configuration corresponding to a terminal device; and sending the first MDT configuration to the second network device.
[0021] The beneficial effects that can be achieved by the method provided in the second aspect can be referred to the beneficial effects of the method provided in the first aspect above, and will not be repeated here.
[0022] In a possible implementation manner, the first information may be sent to a terminal device.
[0023] In a possible implementation manner, third information may be received from a core network device or an operation administration and maintenance (OAM), where the third information is used to instruct to save the first MDT configuration.
[0024] In a possible implementation, the third information may include an identifier of the terminal device and an index of the first MDT configuration.
[0025] In a possible implementation manner, the third information may further include the retention duration of the first MDT configuration and / or the index range of the first MDT configuration.
[0026] In a possible implementation, second information may be received from a second network device, where the second information is used to indicate first MDT data, and the first MDT data is measured according to the first MDT configuration; and the first MDT data is sent to the second network device.
[0027] In a possible implementation manner, second information may be sent to the terminal device, where the second information is used to indicate first MDT data, and the first MDT data is obtained by measuring according to the first MDT configuration.
[0028] In a possible implementation manner, fourth information may be received from a core network device or an OAM, where the fourth information is used to instruct to save the first MDT data, where the first MDT data is obtained by measuring according to the first MDT configuration.
[0029] In a possible implementation manner, the fourth information may include an identifier of the terminal device and an index of the first MDT data.
[0030] In a possible implementation manner, the fourth information may further include a retention duration of the first MDT data and / or an index range of the first MDT data.
[0031] In a third aspect, an embodiment of the present application provides a communication method, which can be executed by a network device, or by a module (such as a processor, a chip or a chip system, etc.) applied to the network device, or by a logical node, a logical module or software that can implement all or part of the network device functions. The method includes: sending first information to a first network device, the first information is used to indicate a first MDT configuration, the first MDT configuration includes an MDT configuration corresponding to a terminal device; receiving the first MDT configuration from the first network device; determining a second MDT configuration according to the first MDT configuration; and sending the second MDT configuration to the terminal device.
[0032] The beneficial effects that can be achieved by the method provided in the third aspect can be referred to the beneficial effects of the method provided in the first aspect above, and will not be repeated here.
[0033] In a possible implementation manner, the first information may be received from the terminal device.
[0034] In a possible implementation, second information may be sent to the first network device, where the second information is used to indicate first MDT data, where the first MDT data is measured according to the first MDT configuration; and the first MDT data is received from the first network device.
[0035] In a possible implementation manner, second information may be received from the terminal device, where the second information is used to indicate first MDT data, and the first MDT data is obtained by measuring according to the first MDT configuration.
[0036] In a fourth aspect, an embodiment of the present application provides a communication method, which can be executed by a terminal device, or by a module (such as a processor, a chip or a chip system, etc.) applied to the terminal device, or by a logical node, a logical module or software that can implement all or part of the functions of the terminal device. The method includes: receiving a first MDT configuration from a first network device, the first MDT configuration including an MDT configuration corresponding to the terminal device. Sending the first MDT configuration to a second network device. Receive a second MDT configuration from the second network device, the second MDT configuration being obtained based on the first MDT configuration. Perform MDT measurements according to the second MDT configuration.
[0037] It can be seen that in the method provided in the embodiment of the present application, after the terminal device enters the connected state from the idle state, the terminal device can send a first MDT configuration including the MDT configuration corresponding to the terminal device to the newly connected second network device, so that the second network device sends the MDT configuration to the terminal device through the first MDT configuration, thereby avoiding the terminal device from stopping MDT measurement due to the newly connected network device not sending the second MDT configuration to the terminal device. In this way, the continuity of MDT can be maintained, thereby obtaining continuous MDT data, so as to meet the need to obtain continuous MDT data in some scenarios. For example, the network device obtains continuous MDT data for the training of the AI model, thereby improving the accuracy of the AI model training and improving the effect of applying the AI model.
[0038] In a possible implementation manner, the first MDT configuration may be saved before disconnecting from the first network device.
[0039] It is understandable that the terminal device may release some unsaved information after disconnecting from the first network device. To avoid the first MDT configuration being released, the terminal device may save the first MDT configuration before disconnecting from the first network device (i.e., before entering the idle state), thereby obtaining continuous MDT data to meet the need to obtain continuous MDT data in some scenarios.
[0040] In a possible implementation manner, the first MDT configuration may be sent to the second network device after establishing a connection with the second network device.
[0041] It can be understood that the establishment of a connection between the terminal and the second network device indicates that the terminal device has entered the connected state, and at this time the terminal device needs to obtain the MDT configuration from the second network device in order to maintain the continuity of the MDT. Therefore, the terminal needs to send the first MDT configuration to the second network device after establishing a connection with the second network device so that the second network device sends the MDT configuration to the terminal device.
[0042] In a possible implementation manner, fifth information may be received from the first network device, where the fifth information is used to instruct to save the first MDT configuration.
[0043] It can be seen that the terminal device can receive the fifth information from the first network device and save the first MDT configuration according to the instruction of the fifth information, thereby avoiding MDT interruption caused by the terminal device being unable to send the first MDT configuration to the second network device due to failure to save the first MDT configuration.
[0044] In a possible implementation manner, first MDT data may be received from the first network device, where the first MDT data is obtained by measurement according to the first MDT configuration; and the first MDT data may be sent to the second network device.
[0045] It should be noted that in some scenarios, network devices need to obtain continuous MDT data, such as training AI models through continuous MDT data. To this end, the terminal device can send second information indicating the first MDT data measured through the first MDT configuration to the newly connected second network device, so that the second network device uses the second information to obtain the first MDT data through the first network device previously connected to the terminal device. By training the AI model with the first MDT data, the model's prediction accuracy for data (such as the terminal's future throughput and trajectory information) can be improved, thereby improving the effect of network optimization.
[0046] In a possible implementation manner, sixth information may be received from the first network device, where the sixth information is used to instruct to save first MDT data, where the first MDT data is obtained by measuring according to the first MDT configuration.
[0047] It can be seen that the terminal device can receive the sixth information from the above-mentioned first network device to save the first MDT data according to the instruction of the sixth information, thereby avoiding the terminal device failing to save the first MDT data and being unable to send the first MDT data to the second network device, causing the second network device to be unable to train the AI model through the first MDT data.
[0048] In a fifth aspect, an embodiment of the present application provides a communication method, which can be executed by a network device, or by a module (such as a processor, a chip or a chip system, etc.) applied to the network device, or by a logical node, a logical module or software that can implement all or part of the network device functions. The method includes: receiving a first MDT configuration from a core network device or an OAM, the first MDT configuration including an MDT configuration corresponding to a terminal device; and sending the first MDT configuration to the terminal device.
[0049] The beneficial effects that can be achieved by the method provided in the fifth aspect can be referred to the beneficial effects of the method provided in the fourth aspect above, and will not be repeated here.
[0050] In a possible implementation manner, fifth information may be sent to the terminal device, where the fifth information is used to instruct to save the first MDT configuration.
[0051] In a possible implementation manner, first MDT data may be sent to the terminal device, where the first MDT data is obtained by measurement according to the first MDT configuration.
[0052] In a possible implementation manner, sixth information may be sent to the terminal device, where the sixth information is used to instruct to save the first MDT data, where the first MDT data is obtained by measuring according to the first MDT configuration.
[0053] In a sixth aspect, an embodiment of the present application provides a communication method, which can be executed by a network device, or by a module (such as a processor, a chip or a chip system, etc.) applied to the network device, or by a logical node, a logical module or software that can implement all or part of the network device functions. The method includes: receiving a first MDT configuration from a terminal device, the first MDT configuration including an MDT configuration corresponding to the terminal device; determining a second MDT configuration according to the first MDT configuration; and sending the second MDT configuration to the terminal device.
[0054] The beneficial effects that can be achieved by the method provided in the sixth aspect can be referred to the beneficial effects of the method provided in the fourth aspect above, and will not be repeated here.
[0055] In a possible implementation manner, first MDT data from the terminal device may be received, where the first MDT data is obtained by measuring according to the first MDT configuration.
[0056] In the seventh aspect, an embodiment of the present application provides a communication method, which can be executed by a terminal device, or by a module (such as a processor, a chip or a chip system, etc.) applied to the terminal device, and can also be implemented by a logical node, a logical module or software that can realize all or part of the functions of the terminal device. The method includes: receiving a fourth MDT configuration from a first network device, sending a first indication message to a second network device, receiving a fifth MDT configuration from the second network device, and performing MDT measurement according to the fifth MDT configuration. The fourth MDT configuration is obtained based on the third MDT configuration, the third MDT configuration is a management-based MDT configuration, the third MDT configuration includes an MDT activation type, an Immediate MDT configuration, a logged MDT configuration and a trace reference (TR) session information, the TR information is used to indicate a first TR and a second TR, the first TR is a TR configured by the Immediate MDT, and the second TR is a TR configured by the logged MDT. The first TR is the same as the second TR.
[0057] It can be seen that in the method provided in the embodiment of the present application, after the terminal device enters the connected state from the idle state, the terminal device can send a first indication message to the newly connected second network device, so that the second network device uses the first indication message to obtain the MDT configuration from the core network device and send the MDT configuration to the terminal device, thereby avoiding the terminal device from stopping the MDT measurement because the newly connected network device does not send the fifth MDT configuration to the terminal device. In this way, the continuity of MDT can be maintained, thereby obtaining continuous MDT data, so as to meet the need to obtain continuous MDT data in some scenarios. For example, the network device obtains continuous MDT data for the training of the AI model, thereby improving the accuracy of the AI model training and improving the effect of applying the AI model.
[0058] In a possible implementation manner, the MDT activation type included in the third MDT configuration is used to instruct the terminal device to perform Immediate MDT measurement and Logged MDT measurement.
[0059] In a possible implementation, a target tracking recording session reference (Trace Recording Session Reference, TRSR) identifier may also be received from the first network device, and the first indication information may include a target TRSR identifier and / or an identifier of the terminal device. The target TRSR identifier is a TRSR identifier assigned by the first network device to the terminal device. The terminal device corresponding to the MDT data can be identified by the TRSR identifier.
[0060] It can be seen that in the method provided in the embodiment of the present application, a new MDT activation type "Immediate MDT and Logged MDT" is introduced, so that OAM can send the same Immediate MDT configuration and Logged MDT configuration in TR, and associate the immediate MDT data and logged MDT data of the same terminal device through TR and target TRSR identifiers, thereby avoiding the problem of not being able to obtain continuous MDT data of the same terminal device due to the inability to associate the immediate MDT data and logged MDT data of the same terminal device due to the different TR of the immediate MDT configuration and the TR of the logged MDT configuration of the same terminal device. This meets the need to obtain continuous MDT data in some scenarios.
[0061] In a possible implementation, a second indication message may also be sent to the second network device. The second indication message is used to indicate that a logged MDT measurement report is stored in the terminal device. The second indication message may inform the terminal device that a logged MDT measurement report is stored in the terminal device, so that the second network device obtains the logged MDT measurement report from the terminal device when the logged MDT measurement report is needed.
[0062] In a possible implementation manner, the first indication information and the second indication information may be the same information. Transmitting the first indication information and the second indication information through the same information helps to reduce signaling overhead.
[0063] In an eighth aspect, an embodiment of the present application provides a communication method, which can be executed by a network device, or by a module (such as a processor, a chip or a chip system, etc.) applied to the network device, or by a logical node, a logical module or software that can implement all or part of the network device functions. The method includes: receiving a third MDT configuration sent from OAM, determining a fourth MDT configuration according to the third MDT configuration, sending a fourth MDT configuration to a terminal device, and sending a fourth MDT configuration to a core network device, wherein the third MDT configuration is a management based MDT configuration, and the third MDT configuration includes an MDT activation type, an Immediate MDT configuration, a logged MDT configuration and TR information, and the TR information is used to indicate a first TR and a second TR, the first TR is a TR configured with Immediate MDT, and the second TR is a TR configured with Logged MDT. The first TR and the second TR are the same. The fourth MDT configuration is the MDT configuration corresponding to the terminal device.
[0064] The beneficial effects that can be achieved by the method provided in the eighth aspect can be referred to the beneficial effects of the method provided in the seventh aspect above, and will not be repeated here.
[0065] In a possible implementation, the MDT activation type included in the third MDT configuration is used to instruct the terminal device to perform Immediate MDT measurement and Logged MDT measurement.
[0066] In a possible implementation, the fourth MDT configuration and the target TRSR identifier may be sent to the core network device. The target TRSR identifier is the TRSR identifier allocated by the first network device to the terminal device.
[0067] In a possible implementation, the first TR and the second TR may be indicated by the same TR.
[0068] In another possible implementation, the first TR and the second TR may be indicated by two identical TRs.
[0069] In a possible implementation manner, the third MDT configuration may further include an MDT area range.
[0070] In a possible implementation manner, the fourth MDT configuration may further include an identifier of the terminal device.
[0071] In a possible implementation manner, the target TRSR identifier may also be sent to the terminal device.
[0072] In the ninth aspect, an embodiment of the present application provides a communication method, which can be executed by a network device, or by a module (such as a processor, a chip or a chip system, etc.) applied to the network device, and can also be implemented by a logical node, a logical module or software that can implement all or part of the network device functions. The method includes: receiving a first indication message from a terminal device. Sending a first indication message to a core network device. Receiving a third MDT configuration sent from the core network device. Determining a fifth MDT configuration based on the third MDT configuration. Sending a fifth MDT configuration to the terminal device. Among them, the first indication information is used to indicate the third MDT configuration stored by the core network device. The first indication information includes an identifier of the terminal device. The third MDT configuration includes an MDT configuration corresponding to the terminal device.
[0073] The beneficial effects that can be achieved by the method provided in the ninth aspect can be referred to the beneficial effects of the method provided in the seventh aspect above, and will not be repeated here.
[0074] In a possible implementation manner, a third MDT configuration and a target TRSR identifier sent by a core network device may be received.
[0075] In a possible implementation manner, the first indication information is used to indicate the third MDT configuration and the target TRSR identifier stored in the core network device, and the first indication information includes the target TRSR identifier and / or the identifier of the terminal device.
[0076] In a possible implementation manner, second indication information sent by the terminal device may also be received, wherein the second indication information is used to indicate that a logged MDT measurement report is stored in the terminal device.
[0077] In a possible implementation, first response information may also be sent to the terminal device to receive a logged MDT measurement report sent from the terminal device, wherein the first response information is used to request a logged MDT measurement report.
[0078] In a possible implementation manner, a logged MDT measurement report may also be sent to a trace collection entity (TCE).
[0079] In a possible implementation manner, the TR information and / or the MDT activation type may also be sent to the core network device.
[0080] In a possible implementation manner, the target TRSR identifier and TR information may be used to associate the immediate MDT measurement report and the logged MDT measurement report of the terminal device.
[0081] In a possible implementation manner, the fifth MDT configuration may be the same as the fourth MDT configuration.
[0082] In a tenth aspect, an embodiment of the present application provides a communication device, which may be a terminal device, or a module (such as a processor, a chip, or a chip system, etc.) applied to a terminal device, or a logical node, a logical module, or software that can implement all or part of the functions of the terminal device. The device may be used to execute the method described in any possible implementation of the first aspect, the fourth aspect, or the seventh aspect.
[0083] Exemplarily, the above-mentioned device includes a module or unit for executing the method described in any possible implementation manner of the first aspect or the fourth aspect.
[0084] In an eleventh aspect, an embodiment of the present application provides a communication device, which may be a network device, or a module (such as a processor, a chip, or a chip system, etc.) applied to a network device, or a logical node, a logical module, or software that can implement all or part of the functions of the network device. The device may be used to execute the method described in any possible implementation of the second aspect, the third aspect, the fifth aspect, the sixth aspect, the eighth aspect, or the ninth aspect.
[0085] Exemplarily, the apparatus includes a module or unit for executing the method described in any possible implementation of the second aspect, the third aspect, the fifth aspect, or the sixth aspect.
[0086] In a twelfth aspect, an embodiment of the present application further provides a communication device, which may be a terminal device, or a module (such as a processor, a chip, or a chip system, etc.) applied to a terminal device, or a logical node, a logical module, or software that can implement all or part of the functions of the terminal device. The communication device includes: at least one processor, when the at least one processor executes a program code or instruction, implements the method described in any possible implementation method of the first aspect, the fourth aspect, or the seventh aspect.
[0087] Optionally, the communication device may further include at least one memory, and the at least one memory is used to store the program code or instruction.
[0088] In the thirteenth aspect, the embodiment of the present application also provides another communication device, which can be a network device, or a module (such as a processor, a chip or a chip system, etc.) applied to a network device, or a logical node, a logical module or software that can implement all or part of the functions of a terminal device. The communication device includes: at least one processor, when the at least one processor executes a program code or instruction, implements the method described in any possible implementation method of the second aspect, the third aspect, the fifth aspect, the sixth aspect, the eighth aspect or the ninth aspect.
[0089] Optionally, the communication device may further include at least one memory, and the at least one memory is used to store the program code or instruction.
[0090] In a fourteenth aspect, an embodiment of the present application further provides a chip, comprising: an input interface, an output interface, and at least one processor. Optionally, the chip further comprises a memory. The at least one processor is used to execute the code in the memory, and when the at least one processor executes the code, the chip implements the method described in any one of the above aspects.
[0091] Optionally, the above chip may also be an integrated circuit.
[0092] In a fifteenth aspect, an embodiment of the present application further provides a computer-readable storage medium for storing a computer program, wherein the computer program includes methods for implementing any of the above aspects.
[0093] In the sixteenth aspect, the embodiments of the present application also provide a computer program product comprising instructions, which, when executed on a computer, enables the computer to implement the method described in any of the above aspects.
[0094] The communication device, computer storage medium, computer program product and chip provided in this embodiment are all used to execute the method provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the method provided above and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS
[0095] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.
[0096] Figure 1A schematic diagram of the structure of a communication system provided in an embodiment of the present application;
[0097] Figure 2 A flow chart of a communication method provided in an embodiment of the present application;
[0098] Figure 3 A flowchart of another communication method provided in an embodiment of the present application;
[0099] Figure 4 A flowchart of another communication method provided in an embodiment of the present application;
[0100] Figure 5 A flowchart of another communication method provided in an embodiment of the present application;
[0101] Figure 6 A flowchart of another communication method provided in an embodiment of the present application;
[0102] Figure 7 A schematic diagram of the structure of a communication device provided in an embodiment of the present application;
[0103] Figure 8 A schematic diagram of the structure of another communication device provided in an embodiment of the present application;
[0104] Fig. 9 A schematic diagram of the structure of another communication device provided in an embodiment of the present application;
[0105] Fig.10 A schematic diagram of the structure of another communication device provided in an embodiment of the present application;
[0106] Fig.11 A schematic diagram of the structure of another communication device provided in an embodiment of the present application;
[0107] Fig.12 A schematic diagram of the structure of another communication device provided in an embodiment of the present application;
[0108] Fig.13 A schematic diagram of the structure of another communication device provided in an embodiment of the present application;
[0109] Fig.14 A schematic diagram of the structure of another communication device provided in an embodiment of the present application;
[0110] Fig.15 A schematic diagram of the structure of another communication device provided in an embodiment of the present application;
[0111] Fig.16 A schematic diagram of the structure of a chip provided in an embodiment of the present application;
[0112] Fig.17A schematic diagram of the structure of another communication device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0113] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the embodiments of the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the embodiments of the present application.
[0114] The term "and / or" in this article is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone.
[0115] The terms "first" and "second" and the like in the description and drawings of the embodiments of the present application are used to distinguish different objects, or to distinguish different processing of the same object, rather than to describe a specific order of objects.
[0116] In addition, the terms "including" and "having" and any variations thereof mentioned in the description of the embodiments of the present application are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device including a series of steps or units is not limited to the listed steps or units, but may optionally include other steps or units that are not listed, or may optionally include other steps or units inherent to these processes, methods, products or devices.
[0117] It should be noted that in the description of the embodiments of the present application, words such as "exemplarily" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplarily" or "for example" in the embodiments of the present application should not be interpreted as having priority or advantage over other embodiments or designs. Specifically, the use of words such as "exemplarily" or "for example" is intended to present related concepts in a specific way.
[0118] MDT is a technology that monitors mobile communication networks to achieve network optimization. In some scenarios, such as during AI model training, terminal devices are expected to perform continuous MDT, so that network devices can obtain continuous MDT data to improve the effect of network optimization. However, if the RRC state change of the terminal device changes, the terminal device may not be able to perform MDT measurements continuously. Specifically, a terminal device in a connected state can perform measurements according to the MDT configuration sent by the network device. When the terminal device switches from a connected state to an idle state, it disconnects from the network device and releases the MDT configuration. If the terminal device switches from an idle state to a connected state again and establishes a connection with a new network device, the terminal device may stop performing MDT measurements because the network device to which the terminal device is newly connected does not send an MDT configuration to the terminal device. In the present application, the RRC state change of a terminal device may also be referred to as a cross-connected state of the terminal device, for example, including a scenario in which the terminal device enters an idle state from a connected state and then enters a connected state again.
[0119] To this end, an embodiment of the present application provides a communication method that enables a terminal device to maintain the continuity of MDT.
[0120] The technical solution provided in the embodiment of the present application can be applied to various communication systems. The technical solution provided in the embodiment of the present application can be applied to the fifth generation mobile communication technology (5th Generation Mobile Communication Technology, 5G) communication system, future evolution system or multiple communication convergence system, etc., and can also be applied to existing communication systems, etc. The application scenarios of the technical solution provided in the embodiment of the present application may include a variety of scenarios, for example, machine to machine (machine to machine, M2M), macro and micro communication, enhanced mobile broadband (enhanced mobile broadband, eMBB), ultra-high reliability and ultra-low latency communication (ultra reliable & low latency communication, uRLLC) and massive Internet of Things communication (massive machine type communication, mMTC) and other scenarios. These scenarios may include, but are not limited to: communication scenarios between terminal devices and terminal devices, communication scenarios between network devices and network devices, communication scenarios between network devices and terminal devices, etc. The following is an example of the scenario applied to the communication between network devices and terminal devices.
[0121] Figure 1A possible, non-limiting schematic diagram of the above communication system is shown. Figure 1 As shown, the communication system 10 includes a radio access network (RAN) 100 and a core network (CN) 200. The RAN 100 includes at least one RAN node (e.g. Figure 1 110a and 110b in, collectively referred to as 110) and at least one terminal device (such as Figure 1 RAN 100 may also include other RAN nodes, such as wireless relay equipment and / or wireless backhaul equipment ( Figure 1 The terminal device 120 is connected to the RAN node 110 in a wireless manner. The RAN node 110 is connected to the core network 200 in a wireless or wired manner. The core network device in the core network 200 and the RAN node 110 in the RAN 100 can be different physical devices, or the same physical device that integrates the core network logical function and the radio access network logical function.
[0122] RAN 100 may be a cellular system related to the third generation partnership project (3GPP), for example, a 4G, 5G mobile communication system, or a future evolution system (for example, a 6G mobile communication system). RAN 100 may also be an open access network (open RAN, O-RAN or ORAN), a cloud radio access network (cloudradio access network, CRAN), or a wireless fidelity (wireless fidelity, WiFi) system. RAN 100 may also be a communication system that integrates two or more of the above systems.
[0123] The RAN node 110, which may also be sometimes referred to as an access network device, a RAN entity or an access node, constitutes a part of the communication system to help terminal devices achieve wireless access. The multiple RAN nodes 110 in the communication system 10 may be nodes of the same type or nodes of different types. In some scenarios, the roles of the RAN node 110 and the terminal device 120 are relative, for example, Figure 1 The network element 120i may be a helicopter or a drone, which may be configured as a mobile base station. For the terminal devices 120j that access the RAN 100 through the network element 120i, the network element 120i is a base station; but for the base station 110a, the network element 120i is a terminal device. The RAN node 110 and the terminal device 120 are sometimes referred to as communication devices, for example Figure 1The network elements 110a and 110b can be understood as communication devices with base station functions, and the network elements 120a_120j can be understood as communication devices with terminal equipment functions.
[0124] In one possible scenario, a RAN node may be a base station, an evolved NodeB (eNodeB), an access point (AP), a transmission reception point (TRP), a next generation NodeB (gNB), a next generation base station in a sixth generation (6G) mobile communication system, a base station in a future mobile communication system, or an access node in a WiFi system. A RAN node may be a macro base station (e.g. Figure 1 110a in), micro base stations or indoor stations (such as Figure 1 110b in the example), a relay node or a donor node, or a wireless controller in a CRAN scenario. Optionally, the RAN node may also be a server, a wearable device, a vehicle or an on-board device, etc. For example, the access network device in the vehicle to everything (V2X) technology may be a road side unit (RSU). All or part of the functions of the RAN node in the embodiment of the present application may also be implemented by software functions running on hardware, or by virtualization functions instantiated on a platform (such as a cloud platform). The RAN node in the embodiment of the present application may also be a logical node, a logical module or software that can implement all or part of the functions of the RAN node.
[0125] The RAN node may also be expressed in different ways, such as a network device. In the embodiments of the present application, unless otherwise specified, network devices are used for expression.
[0126] In another possible scenario, multiple RAN nodes collaborate to assist terminal devices in achieving wireless access, and different RAN nodes implement part of the functions of the base station respectively. For example, the RAN node can be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU can be set separately, or can also be included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or a radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU) or a remote radio head (RRH).
[0127] In different systems, CU (or CU-CP and CU-UP), DU or RU may also have different names, but those skilled in the art can understand their meanings. For example, in the ORAN system, CU may also be called O-CU (open CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU. For the convenience of description, the embodiments of the present application are described by taking CU, CU-CP, CU-UP, DU and RU as examples. Any unit of CU (or CU-CP, CU-UP), DU and RU in the embodiments of the present application may be implemented by a software module, a hardware module, or a combination of a software module and a hardware module.
[0128] Terminal devices may also be referred to as terminals, user equipment (UE), mobile stations, mobile terminal devices, etc. Terminal devices can be widely used in various scenarios, for example, device-to-device (D2D), vehicle to everything (V2X) communication, machine-type communication (MTC), Internet of Things (IOT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grid, smart home, smart office, smart wear, smart transportation, smart city, etc. Terminal devices may be mobile phones, tablet computers, computers with wireless transceiver functions, wearable devices, vehicles, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, etc. The embodiments of the present application do not limit the device form of terminal devices.
[0129] The core network 200 may include one or more core network elements. Taking the 5G core network as an example, the 5G core network includes an access and mobility management function (AMF) element responsible for services such as mobility management and access management, a session management function (SMF) element responsible for session management, a user plane function (UPF) element responsible for data packet routing and forwarding and quality of service (QoS) control on the user plane, and a policy control function (PCF) element. The above core network elements can work independently or be combined to implement certain control functions, such as AMF, SMF and PCF can be combined together as a core network device.
[0130] In a possible implementation, the communication system may further include operation administration and maintenance (OAM). OAM may include fault detection, path discovery, fault location, and performance monitoring. Nodes in an OAM domain in a communication network may perform OAM. An OAM domain refers to a collection of all nodes in a communication network that support OAM functions.
[0131] It is understandable that the present application uses network devices and terminal devices as examples of the execution subjects of the interactive diagram, but the present application does not limit the execution subjects of the interactive diagram. For example, the network device in the method of the present application may also be a chip, chip system or processor applied to the network device, or a logical node, logic module or software that can implement all or part of the network device; the terminal device in the method of the present application may also be a chip, chip system or processor applied to the terminal device, or a logical node, logic module or software that can implement all or part of the terminal device functions.
[0132] Figure 2 A communication method provided in an embodiment of the present application, such as Figure 2 As shown, the method includes:
[0133] S201. A first network device sends first information to a terminal device.
[0134] Correspondingly, the terminal device receives the first information from the first network device.
[0135] The first information is used to indicate a first MDT configuration, and the first MDT configuration includes an MDT configuration corresponding to the terminal device.
[0136] The terminal device can use the corresponding MDT configuration to perform MDT measurements. For example, the terminal can use the corresponding MDT configuration to measure the downlink signal volume of the serving cell and the same-frequency / different-frequency / different-system neighboring cells, the packet data convergence protocol (PDCP) service data unit (SDU) data volume, the average UE throughput, and the data packet delay and other information or parameters.
[0137] Exemplarily, the first network device can send the first information to the terminal device through an RRC reconfiguration message, a UE information request message or other signaling in a scenario where the terminal device is required to perform MDT measurements continuously, such as a scenario where the network device needs continuous MDT data to train an AI model.
[0138] It can be understood that in the embodiments of the present application, "sending information to... (for example, a terminal device)" or the related illustrations in the accompanying drawings can be understood as the destination end of the information being the terminal device. It can include sending information directly or indirectly to a terminal device. "Receiving information from... (for example, a terminal device)" or "receiving information from... (for example, a terminal device)", or the related illustrations in the accompanying drawings can be understood as the source end of the information being a terminal device, which can include receiving information directly or indirectly from a terminal device. The information may be subjected to necessary processing between the source end and the destination end of the information transmission, such as format changes, etc., but the destination end can understand the valid information from the source end. Similar expressions in the embodiments of the present application can be understood similarly and will not be repeated here.
[0139] In a possible implementation manner, the first MDT configuration may include an MDT activation type, an immediate minimization of drive test (Immediate MDT) configuration, and a logged MDT (logged MDT) configuration.
[0140] Exemplarily, the immediate MDT configuration may include one or more of the downlink signal quantity measurement configuration of the serving cell and the same-frequency / different-frequency / different-system neighboring cells, the PDCP SDU data quantity measurement configuration, the average UE throughput measurement configuration, the data packet delay measurement configuration, and the packet loss rate measurement configuration.
[0141] The logged MDT configuration may include the measurement configuration of the received signal strength by the terminal device.
[0142] The MDT activation type refers to the MDT measurement mode that the terminal device can use, such as: using only Immediate MDT (Immediate MDT only), using only Logged MDT (Logged MDT only), or using Immediate MDT and Trace (Immediate MDT and Trace).
[0143] In a possible implementation manner, the first MDT configuration may also include one or more of an MDT area range, a signaling based MDT public land mobile network list (Signalling based MDT public land mobile network List, Signalling based MDT PLM N List), an identifier of the first network device, and an identifier of the terminal device.
[0144] The MDT area range indicates an area where MDT data collection should be performed, and may be a cell list, a tracking area list, or a tracking area identifier list.
[0145] Signalling based MDT PLMN List indicates the PLMN list supported by the signaling based MDT mechanism.
[0146] In a possible implementation manner, the first information may include an index of the first MDT configuration.
[0147] Exemplarily, the index of the above-mentioned first MDT configuration can be a next generation radio access network Trace identifier (NG-RAN Trace ID), which is used to instruct the first network device to retrieve the required MDT configuration of the terminal device (i.e., the first MDT configuration) from the MDT configurations of multiple terminal devices saved by the first network device.
[0148] Exemplarily, the index of the first MDT configuration may also be an identifier of the terminal device. For example, if the network device only stores one MDT configuration for each terminal device, the index of the first MDT may reuse the identifier of the terminal device.
[0149] Exemplarily, the identifier of the above-mentioned terminal device can be a cell-radionetwork temporary identifier (CRNTI), CRNTI and time information or a system architecture evolution temporary mobile station identifier (STMSI).
[0150] In a possible implementation manner, the first network device may also send second information to the terminal device.
[0151] Exemplarily, the terminal device receives the second information from the first network device.
[0152] The second information is used to indicate first MDT data, and the first MDT data is obtained by measuring according to the first MDT configuration.
[0153] Exemplarily, the first network device can send the second information to the terminal device through an RRCReconfiguration message, a UE informationrequest message or other signaling in a scenario where historical MDT data needs to be obtained, such as a scenario where the network device needs historical MDT data to train an AI model.
[0154] It is understandable that training the AI model with historical MDT data (such as historical throughput, trajectory data, etc.) can help improve the AI model's reasoning accuracy on the future throughput and trajectory information of the terminal device.
[0155] In a possible implementation, the first MDT data includes MDT data measured by the terminal device according to the first MDT configuration. For example, the terminal device measures any one or more of the following MDT data: downlink signal quantity measurement results of the serving cell and the same-frequency / different-frequency / different-system neighboring cells, PDCP SDU data volume, average UE throughput, and data packet delay according to the first MDT configuration. MDT data can also be considered as MDT measurement results.
[0156] In another possible implementation manner, the first MDT data includes MDT data measured by the network device according to the first MDT configuration.
[0157] In yet another possible implementation, the first MDT data includes MDT data measured by the network device and the terminal device according to the first MDT configuration.
[0158] In a possible implementation manner, the second information includes an index of the first MDT data.
[0159] The index of the first MDT data is used to instruct the first network device to retrieve the required MDT data (ie, the first MDT data) from the MDT data of multiple terminal devices stored in the first network device.
[0160] Exemplarily, the index of the first MDT data may be a NG-RAN Trace ID.
[0161] Exemplarily, the index of the first MDT data may also be an identifier of the terminal device. For example, if the network device only stores one MDT data for each terminal device, the first MDT data may reuse the identifier of the terminal device.
[0162] In a possible implementation, the first network device may also save the first MDT configuration when disconnected from the terminal device until the storage of the first MDT configuration times out. The storage timeout of the first MDT configuration means that the storage time of the first MDT configuration is greater than the retention time of the first MDT configuration, and the retention time of the first MDT configuration may be preset or indicated by third information, and the third information is used to indicate the saving of the above-mentioned first MDT configuration.
[0163] Exemplarily, the first network device can save the first MDT configuration when disconnected from the terminal device until the storage of the first MDT configuration times out, so that the saved first MDT configuration can be used for the terminal device to perform MDT measurements, thereby obtaining continuous MDT data, such as a scenario where the network device requires the terminal device to continuously perform MDT measurements.
[0164] As another example, the first network device may save the first MDT configuration according to the instruction of the third information when the connection with the terminal device is disconnected, until the storage of the first MDT configuration times out.
[0165] In a possible implementation manner, the first network device may also receive third information.
[0166] Exemplarily, the first network device may receive the third information from the OAM.
[0167] As another example, the first network device may receive an MDT configuration carrying the third information from the core network device to obtain the third information.
[0168] As another example, the first network device may receive, through the core network device, an MDT configuration carrying the third information sent by the OAM to obtain the third information.
[0169] In a possible implementation manner, the third information may include an identifier of the terminal device and an index of the first MDT configuration.
[0170] Exemplarily, the identifier of the terminal device may be included in an identifier list. The identifier list may be used to indicate one or more terminal devices for which the MDT configuration is to be retained (ie, used to indicate which terminal devices correspond to which MDT configurations are to be retained).
[0171] In a possible implementation manner, the third information may further include a retention duration of the first MDT configuration and / or an index range of the first MDT configuration.
[0172] The index range of the first MDT configuration is used to indicate the sending range of the first MDT configuration (ie, to indicate which MDT configurations the network device can send to the terminal device).
[0173] Exemplarily, the index range of the first MDT configuration may be a next generation radio access network trace identification list (NG-RAN Trace ID List), wherein each NG-RAN Trace ID in the NG-RAN Trace ID List may correspond to an MDT configuration.
[0174] It is understandable that after the first network device is disconnected from the terminal device, some configurations related to the terminal device (such as the first MDT configuration) will be released. In order to avoid the first MDT configuration being released due to not being saved, the OAM can instruct the first network device to save the first MDT configuration through the third information. In this way, the MDT interruption caused by the first network device being unable to send the first MDT configuration to the second network device due to the release of the first MDT configuration is avoided.
[0175] In a possible implementation manner, the first network device may also save the first MDT data when disconnected from the terminal device until the storage of the first MDT data times out.
[0176] Exemplarily, the first network device may save the first MDT data when disconnected from the terminal device until the first MDT data storage times out. The first MDT data storage timeout means that the storage time of the first MDT data is greater than the retention time of the first MDT data, and the retention time of the first MDT data may be preset or indicated by the fourth information, and the fourth information is used to indicate the saving of the above-mentioned first MDT data.
[0177] In another exemplary embodiment, the first network device may save the first MDT data according to the instruction of the fourth information when disconnected from the terminal device until the storage of the first MDT data times out. Thus, the saved first MDT data may be sent to other network devices, for example, in a scenario where the network device trains an AI model based on historical MDT data.
[0178] In a possible implementation manner, the first network device may receive fourth information.
[0179] Exemplarily, the first network device may receive an MDT configuration carrying the fourth information from the OAM to obtain the fourth information.
[0180] Exemplarily, the first network device may receive an MDT configuration carrying the fourth information from the core network device to obtain the fourth information.
[0181] Exemplarily, the first network device may receive the fourth information sent from the OAM through the core network device.
[0182] In a possible implementation manner, the fourth information may include an identifier of the terminal device and an index of the first MDT data.
[0183] In a possible implementation manner, the fourth information may further include a retention duration of the first MDT data and / or an index range of the first MDT data.
[0184] The index range of the first MDT data is used to indicate a sending range of the first MDT data (ie, to indicate which MDT data the network device can send to the terminal device).
[0185] Exemplarily, the index range of the first MDT data may be a NG-RAN Trace ID List, wherein each NG-RAN Trace ID in the NG-RAN Trace ID List may correspond to one MDT data.
[0186] It is understandable that, in order to prevent the first MDT data from being released due to not being saved, the OAM can instruct the first network device to save the first MDT data through the fourth information. This prevents the first network device from being unable to send the first MDT data to the second network device due to releasing the first MDT data, so that the second network device can train the AI model through the first MDT data.
[0187] In a possible implementation, the terminal device may further save the first information before disconnecting from the first network device.
[0188] Exemplarily, when the terminal device is in the connected state, it can maintain a connection with the first network device. Before the terminal device is disconnected from the first network device, that is, before the terminal device switches from the connected state to the idle state, the terminal device can save the first information until the first information is sent to the second network device.
[0189] S202. The terminal device sends first information to the second network device.
[0190] Correspondingly, the second network device receives the first information from the terminal device.
[0191] Exemplarily, the terminal device may send the first information to the second network device via a measurement report (measurement report, MR), a UE information response (UE information response) message or other signaling.
[0192] In a possible implementation manner, the terminal device may send the first information to the second network device after establishing a connection with the second network device.
[0193] Exemplarily, the terminal device can switch from the connected state to the idle state, disconnect from the first network device, and then switch from the idle state to the connected state again, establish an RRC connection with the second network device, and then send the above-mentioned first information to the second network device through a measurement report, a UE information response message or other signaling.
[0194] In a possible implementation manner, the terminal device may also send second information to the second network device.
[0195] Exemplarily, the terminal device may send the first information to the second network device via a measurement report, a UE information response message or other signaling.
[0196] In a possible implementation manner, the terminal device may send the second information to the second network device after establishing a connection with the second network device.
[0197] Exemplarily, the terminal device can switch from the connected state to the idle state and disconnect from the first network device, and then switch from the idle state to the connected state again to establish an RRC connection with the second network device, and then send the above-mentioned second information to the second network device through a measurement report, a UE information response message or other signaling.
[0198] In a possible implementation manner, the second network device and the first network device may be the same network device.
[0199] It should be noted that if the first network device and the second network device are the same network device, steps S203 and S204 may not be performed.
[0200] S203: The second network device sends first information to the first network device.
[0201] Correspondingly, the first network device receives the first information from the second network device.
[0202] Exemplarily, in a scenario where the terminal device needs to perform MDT measurements continuously, the second network device can send the above-mentioned first information to the first network device by retrieving a UE context request message, a handover request acknowledgement message, a UE context release message or other signaling.
[0203] In one possible implementation, the indexes of multiple MDT configurations may be stored in the second network device in the form of an index list. The second network device may search the index corresponding to the aforementioned terminal device in the index list to determine the first information, and then send the first information to the first network device to indicate the need to obtain the MDT configuration of the terminal device, i.e., the aforementioned first MDT configuration.
[0204] In a possible implementation manner, the first network device may also send second information to the second network device.
[0205] Correspondingly, the first network device receives the second information from the second network device.
[0206] Exemplarily, in a scenario where historical MDT data needs to be obtained, the second network device may send the second information to the first network device through a retrieveUE context request message, a handover request acknowledgement message, a UE context release message or other signaling.
[0207] In one possible implementation, the indexes of multiple MDT data can be stored in the second network device in the form of an index list. The second network device can search for the index corresponding to the aforementioned terminal device in the index list to determine the second information, and then send the second information to the first network device to indicate the need to obtain the MDT data corresponding to the terminal device, namely the aforementioned first MDT data.
[0208] S204: The first network device sends a first MDT configuration to the second network device.
[0209] Accordingly, the second network device receives the first MDT configuration from the first network device.
[0210] Exemplarily, the first network device may send the first MDT configuration to the second network device through a retrieve UE context response message or other signaling.
[0211] In a possible implementation manner, the first network device may also determine the first MDT configuration from one or more stored MDT configurations according to the first information.
[0212] In a possible implementation manner, the first network device may also send a first response message to the second network device, wherein the first response message is used to indicate a reason why the first MDT configuration cannot be transmitted.
[0213] Exemplarily, when the first network device cannot send the first MDT configuration, it may send the first response message to the second network device to indicate that the failure to transmit the first MDT configuration is due to the first MDT configuration being released, the first MDT configuration storage timeout, or the failure to find the first MDT configuration.
[0214] In a possible implementation manner, the first network device may also send the first MDT data to the second network device.
[0215] Correspondingly, the second network device receives the first MDT data from the first network device.
[0216] Exemplarily, the first network device may send the first MDT data to the second network device through a retrieve UE context response message or other signaling.
[0217] In a possible implementation manner, the first network device may also determine the first MDT data from one or more stored MDT data according to the second information.
[0218] In a possible implementation, the first network device may further send a second response message to the second network device. The second response message is used to indicate the reason why the first MDT data cannot be transmitted. Exemplarily, when the first MDT data cannot be transmitted, the first network device may send a second response message to the second network device to indicate that the reason why the first MDT data cannot be transmitted is because the first MDT data has been released, the first MDT data storage has timed out, or the first MDT data cannot be found.
[0219] S205: The second network device determines a second MDT configuration according to the first MDT configuration.
[0220] Exemplarily, the second network device may modify the format of the first MDT configuration or add or delete content of the first MDT configuration (such as deleting information such as the MDT activation type and the Signalling based MDT PLMN List) to obtain the second MDT configuration.
[0221] In a possible implementation manner, the second MDT configuration may include an Immediate MDT configuration.
[0222] It should be noted that the Immediate MDT configuration in the second MDT configuration may be obtained based on the Immediate MDT configuration in the first MDT configuration. For example, some measurement configurations (such as average UE throughput measurement configuration or packet loss rate measurement configuration) in the Immediate MDT configuration in the first MDT configuration may be deleted to obtain the Immediate MDT configuration in the second MDT configuration.
[0223] S206: The second network device sends a second MDT configuration to the terminal device.
[0224] Correspondingly, the terminal device receives the second MDT configuration from the second network device.
[0225] S207: The terminal device performs MDT measurement according to the second MDT configuration.
[0226] Exemplarily, the terminal device may perform MDT measurement according to the Immediate MDT configuration in the second MDT configuration and periodically report the MDT result to the second network device.
[0227] Among them, the above measurement results may include one or more of the downlink signal volume measurement results of the service cell and the same-frequency / different-frequency / different-system neighboring cells, the packet data convergence protocol (PDCP) service data unit (SDU) data volume, the average UE throughput or the data packet delay.
[0228] It can be seen that in the method provided in the embodiment of the present application, after the terminal device enters the connected state from the idle state, the terminal device can send the first information indicating the MDT configuration corresponding to the terminal device to the newly connected second network device, so that the second network device uses the first information to obtain the MDT configuration through the first network device previously connected to the terminal device and sends the MDT configuration to the terminal device, thereby avoiding the terminal device stopping the MDT measurement because the newly connected network device does not send the second MDT configuration to the terminal device. In this way, the continuity of MDT can be maintained, thereby obtaining continuous MDT data, so as to meet the need to obtain continuous MDT data in some scenarios. For example, the network device obtains continuous MDT data for the training of the AI model, thereby improving the accuracy of the AI model training and improving the effect of applying the AI model.
[0229] The following will be Figure 2 Based on the embodiment shown, combined Figure 3The signaling process shown illustrates the communication method provided by the present application. It can be understood that the various embodiments provided by the present application can be referenced, cited or combined with each other, and Figure 3 The contents introduced in the embodiments will not be repeated here. Figure 3 As shown, the method includes:
[0230] S301. OAM sends third information to a core network device.
[0231] Exemplarily, OAM can send third information to the core network device in a scenario where the terminal device needs to continuously perform MDT measurements, such as a scenario where the network device needs continuous MDT data to train an AI model, and the third information is used to instruct to save the above-mentioned first MDT configuration. For a detailed description of the third information, please refer to Figure 2 Regarding the content of the third information in the illustrated embodiment.
[0232] In a possible implementation manner, the above S301 is also replaced by: the OAM sends third information to the first network device.
[0233] In a possible implementation, the OAM may also send fourth information to the core network device, where the fourth information is used to instruct to save the first MDT data. Figure 2 Regarding the content of the fourth information in the illustrated embodiment.
[0234] Exemplarily, OAM may send the fourth information to the core network device or the first network device in a scenario where historical MDT data needs to be obtained, such as a scenario where the network device needs historical MDT data to train an AI model.
[0235] In a possible implementation manner, the OAM may also send fourth information to the first network device.
[0236] S302. The core network device sends third information to the first network device.
[0237] S303: The first network device saves the first MDT configuration according to the third information.
[0238] For detailed description of the first MDT configuration, please refer to Figure 2 The content about the first MDT configuration in the illustrated embodiment.
[0239] In a possible implementation manner, the first network device may further save the first MDT data according to the fourth information.
[0240] For detailed description of the first MDT data, please refer to Figure 2 The content of the first MDT data in the illustrated embodiment.
[0241] S304: The first network device sends first information to the terminal device.
[0242] For a detailed description of the first information, please refer to Figure 2 Regarding the content of the first information in the illustrated embodiment.
[0243] S305. The terminal device sends first information to the second network device.
[0244] S306: The second network device sends first information to the first network device.
[0245] S307: The first network device sends a first MDT configuration to the second network device.
[0246] S309: The second network device sends a second MDT configuration to the terminal device.
[0247] S310: The terminal device performs MDT measurement according to the second MDT configuration.
[0248] Exemplarily, the terminal device may perform MDT measurement according to the Immediate MDT configuration in the second MDT configuration and periodically report the MDT result to the second network device.
[0249] It should be noted that the specific implementation of the above steps S304-S310 can refer to the description of the above steps S201-S207, which will not be repeated here.
[0250] Figure 4 Another communication method provided in an embodiment of the present application is Figure 2 The difference of the embodiment shown is that in this solution, the first network device no longer sends the first information to the terminal but directly sends the first MDT configuration, such as Figure 4 As shown, the method includes:
[0251] S401. A first network device sends a first MDT configuration to a terminal device.
[0252] Accordingly, the terminal device receives the first MDT configuration from the first network device. For a detailed description of the first MDT configuration, please refer to Figure 2 The content about the first MDT configuration in the illustrated embodiment.
[0253] Exemplarily, the first network device may send a first MDT configuration to the terminal device in a scenario where the terminal device is required to perform MDT measurements continuously, such as a scenario where the network device requires continuous MDT data to train an AI model.
[0254] In a possible implementation, the first network device may also send first MDT data to the terminal device. For a detailed description of the first MDT data, please refer to Figure 2 The content of the first MDT data in the illustrated embodiment.
[0255] Correspondingly, the terminal device receives the first MDT data from the first network device.
[0256] Exemplarily, the first network device may send the first MDT data to the terminal device in a scenario where historical MDT data needs to be obtained, such as a scenario where the network device needs historical MDT data to train an AI model.
[0257] It should be noted that the first MDT configuration may be obtained by the first network device from a core network device or an OAM.
[0258] Exemplarily, the first network device may receive the first MDT configuration sent by the OAM through the core network device.
[0259] In a possible implementation manner, the first network device may also send fifth information to the terminal device.
[0260] The fifth information is used to instruct to save the first MDT configuration.
[0261] Exemplarily, the first network device may send the fifth information to the terminal device in a scenario where the terminal device is required to continuously perform MDT measurement.
[0262] Exemplarily, the fifth information may include the identifier of the terminal device and the retrieval scope of the first MDT configuration.
[0263] The retrieval scope of the first MDT configuration is used to indicate the sending scope of the first MDT configuration (ie, used to indicate to which network devices the first MDT configuration can be sent).
[0264] Exemplarily, the fifth information may further include the retention duration of the first MDT configuration and / or the index range of the first MDT configuration.
[0265] Exemplarily, the fifth information may further include an MDT configuration retention indicator.
[0266] Exemplarily, the MDT configuration retention indicator may be indicated by a bit. For example, if the bit value corresponding to the MDT configuration retention indicator is 1, it indicates that the first MDT configuration is saved, and if the bit value is 0, it indicates that the first MDT configuration is not saved.
[0267] As another example, the MDT configuration retention indicator may also be implicitly indicated by the first MDT configuration. For example, if the terminal device receives the first MDT configuration, the first MDT configuration is saved by default.
[0268] In a possible implementation manner, the fifth information may be generated by the first network device.
[0269] Exemplarily, the first network device may generate the fifth information when the terminal device is required to continuously perform MDT measurement.
[0270] In another possible implementation manner, the fifth information may also be obtained by the first network device from other devices.
[0271] Exemplarily, the first network device may receive the fifth information from the core network device or the OAM.
[0272] For example, the first network device may receive the first MDT configuration carrying the fifth information from the core network device or the OAM to obtain the fifth information.
[0273] For another example, the first network device may receive the first MDT configuration carrying the fifth information sent by the OAM through the core network device to obtain the fifth information.
[0274] It is understandable that the terminal device may release some information after disconnecting from the first network device. In order to avoid the first MDT configuration being released due to not being saved, the fifth information can be used to instruct the terminal to save the first MDT configuration, thereby avoiding the terminal device being unable to send the first MDT configuration to the second network device due to the release of the first MDT configuration after disconnecting from the first network device, thereby causing MDT interruption.
[0275] In a possible implementation manner, the first network device may also send sixth information to the terminal device.
[0276] The sixth information is used to instruct to save the first MDT data.
[0277] Exemplarily, the sixth information may include the identifier of the terminal device and the search scope of the first MDT data.
[0278] The retrieval scope of the first MDT data is used to indicate the sending scope of the first MDT data (ie, used to indicate to which network devices the first MDT data can be sent).
[0279] Exemplarily, the sixth information may further include a retention duration of the first MDT data and / or an index range of the first MDT data.
[0280] Exemplarily, the sixth information may further include an MDT data retention indicator.
[0281] Exemplarily, the MDT data retention indicator may be indicated by a bit. For example, if the bit value corresponding to the MDT data retention indicator is 1, it indicates that the first MDT data is saved, and if the bit value is 0, it indicates that the first MDT data is not saved.
[0282] As another example, the MDT data retention indicator may also be implicitly indicated by the first MDT data. For example, if the terminal device receives the first MDT data, the first MDT data is saved by default.
[0283] In a possible implementation manner, the sixth information may be generated by the first network device.
[0284] Exemplarily, the first network device may generate the sixth information when it is necessary to obtain historical MDT data.
[0285] In another possible implementation manner, the sixth information may also be obtained by the first network device from other devices.
[0286] Exemplarily, the first network device may also receive sixth information from the core network device or OAM.
[0287] For example, the first network device may receive the first MDT configuration carrying the sixth information from the core network device or the OAM to obtain the sixth information.
[0288] For another example, the first MDT configuration carrying the sixth information and sent by the OAM may be received through the core network device to obtain the sixth information.
[0289] In a possible implementation manner, the terminal device may further save the first MDT configuration before disconnecting from the first network device.
[0290] Exemplarily, after receiving the fifth information and the terminal device is in a connected state and before disconnecting from the first network device (i.e., before the terminal device switches from a connected state to an idle state), the terminal device can save the first MDT configuration until the first MDT configuration is sent to the second network device or the storage of the first MDT configuration times out. The storage timeout of the first MDT configuration means that the storage time of the first MDT configuration is greater than the retention time of the first MDT configuration, and the retention time of the first MDT configuration can be preset or indicated by the fifth information.
[0291] In a possible implementation manner, the terminal device may further save the first MDT data before disconnecting from the first network device.
[0292] Exemplarily, after receiving the sixth information and the terminal device is in a connected state and before disconnecting from the first network device (i.e., before the terminal device switches from a connected state to an idle state), the terminal device can save the first MDT data until the first MDT data is sent to the second network device or the first MDT data storage times out. The first MDT data storage timeout means that the storage time of the first MDT data is greater than the retention time of the first MDT data, and the retention time of the first MDT data can be preset or indicated by the sixth information.
[0293] It can be understood that in order to avoid the first MDT data being released due to not being saved, the sixth information can be used to instruct the terminal to save the first MDT data, thereby avoiding the terminal device being unable to send the first MDT data to the second network device due to the release of the first MDT data after disconnecting from the first network device, so that the second device can train the AI model through the first MDT data.
[0294] S402: The terminal device sends a first MDT configuration to the second network device.
[0295] Correspondingly, the second network device receives the first MDT configuration from the terminal device.
[0296] In a possible implementation manner, the terminal device may send the first MDT configuration to the second network device after establishing a connection with the second network device.
[0297] Exemplarily, when the terminal device switches from the connected state to the idle state and is disconnected from the first network device, it switches from the idle state to the connected state again, establishes an RRC connection with the second network device, and then sends the above-mentioned first MDT configuration to the second network device through a measurement report, a UE information response message or other signaling.
[0298] As another example, if the first MDT configuration is still retained inside the terminal device, and the second network device is within the search range of the first MDT configuration, the terminal device may send the first MDT configuration to the second network device.
[0299] As another example, if the first MDT configuration is still retained inside the terminal device, but the second network device is not within the retrieval range of the first MDT configuration, the terminal device may not send the first MDT configuration to the second network device.
[0300] In a possible implementation manner, the terminal device may also send the first MDT data to the second network device.
[0301] Correspondingly, the second network device receives the first MDT data from the terminal device.
[0302] Exemplarily, the terminal device can switch from the connected state to the idle state and disconnect from the first network device, and then switch from the idle state to the connected state again to establish an RRC connection with the second network device, and then send the above-mentioned first MDT data to the second network device through a measurement report, a UE information response message or other signaling.
[0303] As another example, if the first MDT data is still retained inside the terminal device, and the second network device is within the search range of the first MDT data, the terminal device may send the first MDT data to the second network device.
[0304] As another example, if the first MDT data is still retained inside the terminal device, but the second network device is not within the retrieval range of the first MDT data, the terminal device may not send the first MDT data to the second network device.
[0305] In a possible implementation manner, the terminal device may also send a fourth response message to the second network device.
[0306] The fourth response message is used to indicate the reason why the first MDT data cannot be sent.
[0307] Exemplarily, when the first MDT data cannot be sent to the second network device, a fourth response message can be sent to the second network device to indicate that the failure to transmit the first MDT data is due to reasons such as the first MDT data has been released, the first MDT data has timed out, the second network device is not within the retrieval range of the first MDT data, etc.
[0308] In a possible implementation manner, the second network device may send a fifth response message to the terminal device.
[0309] The fifth response message is used to indicate the reason for rejecting to receive the first MDT configuration.
[0310] Exemplarily, the second network device may send the fifth response message to the terminal device when there are no measurement resources, no computing resources, or no need to maintain continuous MDT.
[0311] In a possible implementation, the above S402 is also replaced by: the terminal device sends a third response message to the second network device, wherein the third response message is used to indicate the reason why the first MDT configuration cannot be sent.
[0312] Exemplarily, when the terminal is unable to send the first MDT configuration to the second network device, the terminal may send a third response message to the second network device to indicate that the first MDT configuration cannot be transmitted because the first MDT configuration has been released, or the storage of the first MDT configuration has timed out, or the second network device is not within the retrieval range of the first MDT configuration.
[0313] In a possible implementation manner, the second network device and the first network device may be the same network device.
[0314] S403: The second network device determines a second MDT configuration according to the first MDT configuration.
[0315] Exemplarily, the format of the first MDT configuration may be modified or the content of the first MDT configuration may be increased or decreased to obtain the second MDT configuration.
[0316] S404: The second network device sends a second MDT configuration to the terminal device.
[0317] Correspondingly, the terminal device receives the second MDT configuration from the second network device.
[0318] S405: The terminal device performs MDT measurement according to the second MDT configuration.
[0319] Exemplarily, the terminal device may perform MDT measurement according to the immediate MDT configuration in the second MDT configuration and periodically report the MDT result to the second network device.
[0320] It should be noted that the Immediate MDT configuration in the second MDT configuration may be obtained based on the Immediate MDT configuration in the first MDT configuration. For example, some measurement configurations (such as average UE throughput measurement configuration or packet loss rate measurement configuration) in the Immediate MDT configuration in the first MDT configuration may be deleted to obtain the Immediate MDT configuration in the second MDT configuration.
[0321] For detailed description of steps S403 to 405, please refer to the aforementioned Figure 2 Description of steps S205 to S207 in the illustrated embodiment.
[0322] It can be seen that in the method provided in the embodiment of the present application, after the terminal device enters the connected state from the idle state, the terminal device can send a first MDT configuration including the MDT configuration corresponding to the terminal device to the newly connected second network device, so that the second network device sends the MDT configuration to the terminal device through the first MDT configuration, thereby avoiding the terminal device from stopping MDT measurement due to the newly connected network device not sending the second MDT configuration to the terminal device. In this way, the continuity of MDT can be maintained, thereby obtaining continuous MDT data, so as to meet the need to obtain continuous MDT data in some scenarios. For example, the network device obtains continuous MDT data for the training of the AI model, thereby improving the accuracy of the AI model training and improving the effect of applying the AI model.
[0323] The following will be Figure 4 Based on the embodiment shown, combined Figure 5 The signaling process shown illustrates the communication method provided by the present application. Figure 4 The contents introduced in the embodiments will not be repeated here. Figure 5 As shown, the method includes:
[0324] S501. OAM sends a first MDT configuration to a core network device.
[0325] For a detailed description of the first MDT configuration, please refer to Figure 2 The content about the first MDT configuration in the illustrated embodiment.
[0326] In a possible implementation manner, the above S501 is also replaced by: the OAM sends the first MDT configuration to the first network device.
[0327] In a possible implementation, the OAM may also send fifth information to the core network device, where the fifth information is used to instruct to save the first MDT configuration. Figure 4 Regarding the content of the fifth information in the illustrated embodiment.
[0328] In a possible implementation manner, the OAM may also send fifth information to the first network device.
[0329] In a possible implementation, the OAM may also send sixth information to the core network device, where the sixth information is used to instruct to save the first MDT data. For a detailed description of the sixth information, please refer to Figure 4 Regarding the content of the sixth information in the illustrated embodiment.
[0330] In a possible implementation manner, the OAM may also send sixth information to the first network device.
[0331] S502: The core network device sends a first MDT configuration to the first network device.
[0332] In a possible implementation manner, the core network device may also send fifth information to the first network device.
[0333] The fifth information may be generated by the core network device itself, or may be received from OAM.
[0334] Exemplarily, the core network device may generate the fifth information when it is necessary to maintain the continuity of the MDT.
[0335] In a possible implementation manner, the core network device may also send sixth information to the first network device.
[0336] The sixth information may be generated by the core network device itself, or may be received from OAM.
[0337] Exemplarily, the first network device may generate the sixth information when it is necessary to obtain historical MDT data.
[0338] S503: The first network device sends a first MDT configuration to the terminal device.
[0339] It should be noted that the specific implementation of S503 can refer to the description of S401 above, which will not be repeated here.
[0340] S504: The terminal device saves the first MDT configuration.
[0341] In a possible implementation manner, the terminal device may save the first MDT configuration before disconnecting from the first network device.
[0342] Exemplarily, if the core network device sends the aforementioned fifth information to the first network device, and then the first network device sends the fifth information to the terminal device, the terminal device can maintain a connection with the first network device when it receives the fifth information and the terminal device is in a connected state. Before the terminal device is disconnected from the above-mentioned first network device (that is, before the terminal device switches from the connected state to the idle state), the terminal device can save the above-mentioned first MDT configuration until the first MDT configuration is sent to the second network device or the storage of the first MDT configuration times out.
[0343] In a possible implementation manner, the terminal device may save the first MDT data before disconnecting from the first network device.
[0344] Exemplarily, if the core network device sends the aforementioned sixth information to the first network device, and then the first network device sends the sixth information to the terminal device, the terminal device can maintain a connection with the first network device when it receives the sixth information and the terminal device is in a connected state. Before the terminal device is disconnected from the above-mentioned first network device (that is, before the terminal device switches from the connected state to the idle state), the terminal device can save the above-mentioned first MDT data until the first MDT data is sent to the second network device or the storage of the first MDT data times out.
[0345] For a detailed description of the first MDT data, please refer to Figure 2 The content of the first MDT data in the illustrated embodiment.
[0346] S505: The terminal device sends the first MDT configuration to the second network device.
[0347] S506: The second network device determines a second MDT configuration according to the first MDT configuration.
[0348] S507: The second network device sends a second MDT configuration to the terminal device.
[0349] S508: The terminal device performs MDT measurement according to the second MDT configuration.
[0350] It should be noted that the specific implementation of the above steps S505-S508 can refer to the description of the above steps S402-S405, which will not be repeated here.
[0351] Figure 6 Another communication method provided in an embodiment of the present application is Figure 2 and Figure 4 The provided embodiments can be referenced to each other. Figure 2 and Figure 4 The contents introduced in the embodiments provided are not repeated in this embodiment. Figure 2 The difference between the illustrated embodiment is that the MDT configuration sent by the first network device to the terminal in the solution includes a trace session (Trace Referen ce, TR) configured by Immediate MDT and a TR configured by logged MDT, and the values of these two TRs are the same. The method includes:
[0352] S601. OAM sends a third MDT configuration to a first network device.
[0353] Accordingly, the first network device receives the third MDT configuration from the OAM.
[0354] The third MDT configuration is a management based MDT configuration, and the MDT activation type is "Immediate MDT and Logged MDT".
[0355] It should be noted that the MDT activation types Immediate MDT and Logged MDT are newly added MDT activation types in the embodiments of the present application. The MDT activation types "Immediate MDT and Logged MDT" are used to instruct the terminal device to perform Immediate MDT measurements and Logged MDT measurements. For example, the terminal device can perform measurements of type Immediate MDT in the connected state and measurements of type Logged MDT in the idle state according to the MDT configuration with the MDT activation type of "Immediate MDT and Logged MDT".
[0356] The third MDT configuration includes MDT activation type, Immediate MDT configuration, logged MDT configuration and TR information, the TR information is used to indicate the first TR and the second TR, the first TR is a TR configured with Immediate MDT, and the second TR is a TR configured with Logged MDT. The first TR and the second TR are the same.
[0357] In a possible implementation, the first TR and the second TR may be indicated by the same TR.
[0358] In another possible implementation, the first TR and the second TR may be indicated by two identical TRs.
[0359] The Immediate MDT data and the logged MDT data can be associated through the TR. For example, if the TRs of the Immediate MDT configuration and the logged MDT configuration are the same, it can be determined that the Immediate MDT data measured through the Immediate MDT configuration and the logged MDT data measured through the logged MDT configuration are measured through the same MDT session.
[0360] In a possible implementation manner, the third MDT configuration may further include an MDT area range.
[0361] S602: The first network device determines a fourth MDT configuration according to the third MDT configuration.
[0362] The fourth MDT configuration includes the above-mentioned MDT activation type, Immediate MDT configuration, logged MDT configuration and the above-mentioned TR information.
[0363] Exemplarily, the first network device may modify the format of the third MDT configuration or add or delete the content of the third MDT configuration (such as deleting the identifier of the first network device) to obtain the fourth MDT configuration.
[0364] In a possible implementation manner, the fourth MDT configuration may further include an identifier of the terminal device.
[0365] S603: The first network device sends a fourth MDT configuration to the terminal device.
[0366] Correspondingly, the terminal device receives the fourth MDT configuration from the first network device.
[0367] In a possible implementation manner, the first network device may also send a target tracing and recording session reference (Trace Recording Session Reference, TRSR) identifier to the terminal device.
[0368] The target TRSR identifier is a TRSR identifier allocated by the first network device to the terminal device. The terminal device corresponding to the MDT data can be identified by the TRSR identifier.
[0369] S604: The first network device sends a third MDT configuration and a target TRSR identifier to the core network device.
[0370] Correspondingly, the core network device receives the third MDT configuration and the target TRSR identifier from the first network device.
[0371] In a possible implementation manner, the core network device may store the third MDT configuration and the target TRSR identifier in the UE context.
[0372] In a possible implementation, the core network device may send the third MDT configuration and the target TRSR to the second network device. For example, when the core network device receives the third MDT configuration and senses that the terminal device has established a connection with the second network device, the core network device may actively send the third MDT configuration and the target TRSR identifier to the second network device.
[0373] S605. The terminal device sends first indication information to the second network device.
[0374] Correspondingly, the second network device receives the first indication information from the terminal device.
[0375] The first indication information is used to indicate the third MDT configuration and the target TRSR identifier stored in the core network device. The first indication information includes the target TRSR identifier and / or the identifier of the terminal device.
[0376] Exemplarily, the terminal device can switch from the connected state to the idle state, disconnect from the first network device, and then switch from the idle state to the connected state again. After establishing an RRC connection with the second network device, the terminal device sends a first indication message carrying the target TRSR identifier and the terminal device identifier to the second network device.
[0377] In a possible implementation manner, the first indication information may further include the TR information and / or the MDT activation type.
[0378] In a possible implementation manner, the identifier of the terminal device may be obtained by the terminal device according to the fourth MDT configuration, or may be obtained by the terminal device through other signaling.
[0379] In a possible implementation, the terminal device may also send second indication information to the second network device, wherein the second indication information is used to indicate that a logged MDT measurement report is stored in the terminal device.
[0380] In a possible implementation manner, the first indication information and the second indication information may be the same information.
[0381] In a possible implementation manner, the terminal device may also send a logged MDT measurement report to the second network device.
[0382] Exemplarily, the terminal device may send a logged MDT measurement report to the second network device when receiving the first response information, wherein the first response information is used to request the logged MDT measurement report.
[0383] In a possible implementation manner, after receiving the logged MDT measurement report, the second network device may further send the logged MDT measurement report to a trace collection entity (TCE).
[0384] S606. The second network device sends first indication information to the core network device.
[0385] Correspondingly, the core network device receives the first indication information from the second network device.
[0386] In a possible implementation manner, the second network device may also send the TR information and / or the MDT activation type to the core network device.
[0387] S607: The core network device sends the third MDT configuration and the target TRSR identifier to the second network device.
[0388] Correspondingly, the second network device receives the third MDT configuration and the target TRSR identifier from the core network device.
[0389] Exemplarily, the core network device may retrieve the UE context through the TR information and the target TRSR identifier to determine the third MDT configuration, and then send the third MDT configuration to the second network device.
[0390] S608: The second network device determines a fifth MDT configuration according to the third MDT configuration.
[0391] Exemplarily, the second network device may modify the format of the third MDT configuration or add or delete content of the third MDT configuration to obtain the fifth MDT configuration.
[0392] It should be noted that, in the process of the second network device determining the fifth MDT configuration according to the third MDT configuration, there is no need to allocate a new TRSR identifier to the terminal device, but the above target TRSR identifier can be reused.
[0393] In a possible implementation manner, the second network device may use the target TRSR identifier and TR information to associate the immediate MDT measurement report and the logged MDT measurement report of the terminal device.
[0394] In a possible implementation manner, the fifth MDT configuration may be the same as the fourth MDT configuration.
[0395] S609: The second network device sends a fifth MDT configuration to the terminal device.
[0396] Correspondingly, the terminal device receives the fifth MDT configuration from the second network device.
[0397] S610: The terminal device performs MDT measurement according to the fifth MDT configuration.
[0398] It can be seen that in the method provided in the embodiment of the present application, a new MDT activation type "Immediate MDT and Logged MDT" is introduced, so that OAM can send the same Immediate MDT configuration and Logged MDT configuration as TR, and associate the immediate MDT data and logged MDT data of the same terminal device through TR and target TRSR identifier, thereby avoiding the inability to associate the immediate MDT data and logged MDT data of the same terminal device due to the different TR of the immediate MDT configuration and the TR of the logged MDT configuration of the same terminal device, resulting in the inability to obtain continuous MDT data of the same terminal device. This meets the need to obtain continuous MDT data in some scenarios. For example, the network device obtains continuous MDT data for the training of the AI model, thereby improving the accuracy of the AI model training and improving the effect of applying the AI model.
[0399] In addition, after the terminal device enters the connected state from the idle state, the terminal device can send the first indication information carrying the target TRSR identifier and / or the terminal identifier to the newly connected second network device, so that the second network device uses the first indication information to obtain the MDT configuration from the core network device and send the MDT configuration to the terminal device, thereby avoiding the terminal device from stopping the MDT measurement because the newly connected network device does not send the fifth MDT configuration to the terminal device. In this way, the continuity of MDT can be maintained, thereby obtaining continuous MDT data, which meets the need to obtain continuous MDT data in some scenarios.
[0400] The following will be combined Figures 7 to 15 A communication device for executing the above communication method is introduced.
[0401] It is understandable that, in order to implement the functions of the above-mentioned communication method, the communication device includes hardware and / or software modules corresponding to the execution of each function. In combination with the algorithm steps of each example described in the embodiments disclosed herein, the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in combination with the embodiments, but such implementation should not be considered to exceed the scope of the embodiments of the present application.
[0402] The embodiment of the present application can divide the functional modules of the communication device according to the above method example. For example, each functional module can be divided according to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware. It should be noted that the division of modules in this embodiment is schematic and is only a logical function division. There may be other division methods in actual implementation.
[0403] In the case of dividing each functional module into corresponding functional modules, Figure 7 A possible composition diagram of the communication device involved in the above embodiment is shown, and the device may be a terminal device, or a module (such as a processor, a chip or a chip system, etc.) applied to the terminal device, or a logical node, a logical module or software that can realize all or part of the functions of the terminal device. Figure 7 As shown, the communication device 700 may include: a receiving unit 701, a sending unit 702 and a processing unit 703.
[0404] The receiving unit 701 is used to receive first information from a first network device, where the first information is used to indicate a first MDT configuration, and the first MDT configuration includes an MDT configuration corresponding to a terminal device.
[0405] The sending unit 702 is used to send the first information to the second network device.
[0406] The receiving unit 701 is further configured to receive a second MDT configuration from the second network device, where the second MDT configuration is obtained based on the first MDT configuration.
[0407] The processing unit 703 is configured to perform MDT measurement according to the second MDT configuration.
[0408] In a possible implementation, the processing unit 703 is further configured to: save the first information before disconnecting from the first network device.
[0409] In a possible implementation manner, the sending unit 702 is specifically configured to: send the first information to the second network device after establishing a connection with the second network device.
[0410] In a possible implementation manner, the second MDT configuration may include an Immediate MDT configuration.
[0411] In a possible implementation manner, the first information may include an index of the first MDT configuration.
[0412] In a possible implementation manner, the receiving unit 701 is further configured to: receive second information from the first network device, where the second information is used to indicate first MDT data, and the first MDT data is measured according to the first MDT configuration.
[0413] In a possible implementation manner, the sending unit 702 is further configured to: send the second information to the second network device.
[0414] In a possible implementation manner, the second information may include an index of the first MDT data.
[0415] In the case of dividing each functional module into corresponding functional modules, Figure 8 Another possible composition diagram of the communication device involved in the above embodiment is shown, and the device may be a network device, or a module (such as a processor, a chip or a chip system, etc.) applied to the network device, or a logical node, a logical module or software that can realize all or part of the functions of the network device. Figure 8 As shown, the communication device 800 may include: a receiving unit 801 and a sending unit 802.
[0416] The receiving unit 801 is used to receive first information from a second network device, where the first information is used to indicate a first MDT configuration, and the first MDT configuration includes an MDT configuration corresponding to a terminal device.
[0417] The sending unit 802 is configured to send the first MDT configuration to the second network device.
[0418] In a possible implementation, the sending unit 802 is further configured to: send the first information to a terminal device.
[0419] In a possible implementation manner, the receiving unit 801 is further configured to: receive third information from a core network device or an OAM, where the third information is used to instruct to save the first MDT configuration.
[0420] In a possible implementation manner, the third information may include an identifier of the terminal device and an index of the first MDT configuration.
[0421] In a possible implementation manner, the third information may further include the retention duration of the first MDT configuration and / or the index range of the first MDT configuration.
[0422] In a possible implementation manner, the receiving unit 801 is further configured to: receive second information from a second network device, where the second information is used to indicate first MDT data, and the first MDT data is obtained by measuring according to the first MDT configuration.
[0423] In a possible implementation manner, the sending unit 802 is further configured to: send the first MDT data to the second network device.
[0424] In a possible implementation manner, the sending unit 802 is further used to: send second information to the terminal device, where the second information is used to indicate first MDT data, and the first MDT data is obtained by measuring according to the first MDT configuration.
[0425] In a possible implementation, the receiving unit 801 is further used to: receive fourth information from a core network device or OAM, where the fourth information is used to instruct to save the first MDT data, where the first MDT data is measured according to the first MDT configuration.
[0426] In a possible implementation manner, the fourth information may include an identifier of the terminal device and an index of the first MDT data.
[0427] In a possible implementation manner, the fourth information may further include a retention duration of the first MDT data and / or an index range of the first MDT data.
[0428] In the case of dividing each functional module into corresponding functional modules, Fig. 9 Another possible composition diagram of the communication device involved in the above embodiment is shown, and the device may be a network device, or a module (such as a processor, a chip or a chip system, etc.) applied to the network device, or a logical node, a logical module or software that can realize all or part of the functions of the network device. Fig. 9 As shown, the communication device 900 may include: a sending unit 901 , a receiving unit 902 and a processing unit 903 .
[0429] The sending unit 901 is used to send first information to a first network device, where the first information is used to indicate a first MDT configuration, and the first MDT configuration includes an MDT configuration corresponding to a terminal device.
[0430] The receiving unit 902 is configured to receive the first MDT configuration from the first network device.
[0431] The processing unit 903 is configured to determine a second MDT configuration according to the first MDT configuration.
[0432] The sending unit 901 is further configured to send the second MDT configuration to the terminal device.
[0433] In a possible implementation, the receiving unit 902 is further configured to: receive the first information from the terminal device.
[0434] In a possible implementation manner, the sending unit 901 is further used to: send second information to the first network device, where the second information is used to indicate first MDT data, and the first MDT data is obtained by measurement according to the first MDT configuration.
[0435] In a possible implementation manner, the receiving unit 902 is further configured to: receive the first MDT data from the first network device.
[0436] In a possible implementation manner, the receiving unit 902 is further configured to: receive second information from the terminal device, where the second information is used to indicate first MDT data, and the first MDT data is obtained by measuring according to the first MDT configuration.
[0437] In the case of dividing each functional module into corresponding functional modules, Fig.10 A possible composition diagram of the communication device involved in the above embodiment is shown, and the device may be a terminal device, or a module (such as a processor, a chip or a chip system, etc.) applied to the terminal device, or a logical node, a logical module or software that can realize all or part of the functions of the terminal device. Fig.10 As shown, the communication device 1000 may include: a receiving unit 1001 , a sending unit 1002 and a processing unit 1003 .
[0438] The receiving unit 1001 is configured to receive a first MDT configuration from a first network device, where the first MDT configuration includes an MDT configuration corresponding to a terminal device.
[0439] The sending unit 1002 is configured to send the first MDT configuration to the second network device.
[0440] The receiving unit 1001 is further configured to receive a second MDT configuration from the second network device, where the second MDT configuration is obtained based on the first MDT configuration.
[0441] The processing unit 1003 is configured to perform MDT measurement according to the second MDT configuration.
[0442] In a possible implementation manner, the processing unit 1003 is further configured to: save the first MDT configuration before disconnecting from the first network device.
[0443] In a possible implementation manner, the sending unit 1002 is specifically configured to: send the first MDT configuration to the second network device after establishing a connection with the second network device.
[0444] In a possible implementation manner, the receiving unit 1001 is further configured to: receive fifth information from the first network device, where the fifth information is used to instruct to save the first MDT configuration.
[0445] In a possible implementation manner, the receiving unit 1001 is further configured to: receive first MDT data from the first network device, where the first MDT data is obtained by measurement according to the first MDT configuration.
[0446] In a possible implementation manner, the sending unit 1002 is further configured to: send the first MDT data to the second network device.
[0447] In a possible implementation manner, the receiving unit 1001 is further used to: receive sixth information from the first network device, where the sixth information is used to instruct to save first MDT data, where the first MDT data is obtained by measuring according to the first MDT configuration.
[0448] In the case of dividing each functional module into corresponding functional modules, Fig.11 Another possible composition diagram of the communication device involved in the above embodiment is shown, and the device may be a network device, or a module (such as a processor, a chip or a chip system, etc.) applied to the network device, or a logical node, a logical module or software that can realize all or part of the functions of the network device. Fig.11 As shown, the communication device 1100 may include: a receiving unit 1101 and a sending unit 1102 .
[0449] The receiving unit 1101 is used to receive a first MDT configuration from a core network device or an OAM, where the first MDT configuration includes an MDT configuration corresponding to a terminal device.
[0450] The sending unit 1102 is used to send the first MDT configuration to the terminal device.
[0451] In a possible implementation manner, the sending unit 1102 is further used to: send fifth information to the terminal device, where the fifth information is used to instruct to save the first MDT configuration.
[0452] In a possible implementation manner, the sending unit 1102 is further configured to: send first MDT data to the terminal device, where the first MDT data is obtained by measurement according to the first MDT configuration.
[0453] In a possible implementation manner, the sending unit 1102 is further used to: send sixth information to the terminal device, where the sixth information is used to instruct to save the first MDT data, where the first MDT data is obtained by measuring according to the first MDT configuration.
[0454] In the case of dividing each functional module into corresponding functional modules, Fig.12 Another possible composition diagram of the communication device involved in the above embodiment is shown, and the device may be a network device, or a module (such as a processor, a chip or a chip system, etc.) applied to the network device, or a logical node, a logical module or software that can realize all or part of the functions of the network device. Fig.12 As shown, the communication device 1200 may include: a receiving unit 1201 , a processing unit 1202 and a sending unit 1203 .
[0455] The receiving unit 1201 is configured to receive a first MDT configuration from a terminal device, where the first MDT configuration includes an MDT configuration corresponding to the terminal device.
[0456] The processing unit 1202 is configured to determine a second MDT configuration according to the first MDT configuration.
[0457] The sending unit 1203 is configured to send the second MDT configuration to the terminal device.
[0458] In a possible implementation manner, the receiving unit 1201 is further configured to: receive first MDT data from the terminal device, where the first MDT data is obtained by measuring according to the first MDT configuration.
[0459] In the case of dividing each functional module into corresponding functional modules, Fig.13 Another possible composition diagram of the communication device involved in the above embodiment is shown, and the device may be a terminal device, or a module (such as a processor, a chip or a chip system, etc.) applied to the terminal device, or a logical node, a logical module or software that can realize all or part of the functions of the terminal device. Fig.13 As shown, the communication device 1300 may include: a receiving unit 1301 , a sending unit 1302 and a processing unit 1303 .
[0460] The receiving unit 1301 is configured to receive a fourth MDT configuration from a first network device.
[0461] The sending unit 1302 is configured to send first indication information to the second network device. The first indication information includes an identifier of the terminal device. The fifth MDT configuration is obtained based on the third MDT configuration.
[0462] The receiving unit 1301 is further configured to receive a fifth MDT configuration from the second network device.
[0463] The processing unit 1303 is configured to perform MDT measurement according to the fifth MDT configuration.
[0464] Among them, the fourth MDT configuration is obtained based on the third MDT configuration, the third MDT configuration is a management based MDT configuration, and the MDT activation type is "Immediate MDT and Logged MDT", the third MDT configuration includes the MDT activation type, the Immediate MDT configuration, the logged MDT configuration and the TR information, the TR information is used to indicate the first TR and the second TR, the first TR is the TR of the Immediate MDT configuration, and the second TR is the TR of the logged MDT configuration. The first TR is the same as the second TR. The fourth MDT configuration includes the MDT activation type, the Immediate MDT configuration, the logged MDT configuration and the TR information. The first indication information is used to indicate the third MDT configuration stored in the core network device.
[0465] In a possible implementation, the receiving unit 1301 is further used to: receive a target TRSR identifier from the first network device, and the first indication information may include a target TRSR identifier and / or an identifier of the terminal device. The target TRSR identifier is a TRSR identifier assigned by the first network device to the terminal device. The terminal device corresponding to the MDT data can be identified by the TRSR identifier.
[0466] In a possible implementation, the sending unit 1302 is further configured to: send second indication information to the second network device, wherein the second indication information is used to indicate that a logged MDT measurement report is stored in the terminal device.
[0467] In a possible implementation manner, the first indication information and the second indication information may be the same information.
[0468] In a possible implementation manner, the sending unit 1302 is further configured to: send a logged MDT measurement report to the second network device.
[0469] In the case of dividing each functional module into corresponding functional modules, Fig.14 Another possible composition diagram of the communication device involved in the above embodiment is shown, and the device may be a network device, or a module (such as a processor, a chip or a chip system, etc.) applied to the network device, or a logical node, a logical module or software that can realize all or part of the functions of the network device. Fig.14 As shown, the communication device 1400 may include: a receiving unit 1401 , a processing unit 1402 and a sending unit 1403 .
[0470] The receiving unit 1401 is configured to receive a third MDT configuration sent from a core network device.
[0471] The processing unit 1402 is configured to determine a fourth MDT configuration according to the third MDT configuration.
[0472] The sending unit 1403 is configured to send a fourth MDT configuration to the terminal device.
[0473] Among them, the third MDT configuration is a management based MDT configuration, and the MDT activation type is "Immediate MDT and Logged MDT". The third MDT configuration includes the MDT activation type, Immediate MDT configuration, logged MDT configuration and TR information. The TR information is used to indicate the first TR and the second TR. The first TR is a TR configured with Immediate MDT, and the second TR is a TR configured with Logged MDT. The first TR and the second TR are the same. The fourth MDT configuration is the MDT configuration corresponding to the terminal device.
[0474] In a possible implementation, the sending unit 1403 is further configured to: send the fourth MDT configuration and the target TRSR identifier to the core network device. The target TRSR identifier is the TRSR identifier allocated by the first network device to the terminal device.
[0475] In a possible implementation, the first TR and the second TR may be indicated by the same TR.
[0476] In another possible implementation, the first TR and the second TR may be indicated by two identical TRs.
[0477] In a possible implementation manner, the third MDT configuration may further include an MDT area range.
[0478] In a possible implementation manner, the fourth MDT configuration may further include an identifier of the terminal device.
[0479] In a possible implementation manner, the sending unit 1403 is further configured to: send a target TRSR identifier to the terminal device.
[0480] In the case of dividing each functional module into corresponding functional modules, Fig.15Another possible composition diagram of the communication device involved in the above embodiment is shown, and the device may be a network device, or a module (such as a processor, a chip or a chip system, etc.) applied to the network device, or a logical node, a logical module or software that can realize all or part of the functions of the network device. Fig.12 As shown, the communication device 1500 may include: a receiving unit 1501, a sending unit 1502 and a processing unit 1503.
[0481] The receiving unit 1501 is used to receive first indication information from a terminal device.
[0482] The sending unit 1502 is used to send first indication information to the core network device.
[0483] The receiving unit 1501 is configured to receive a third MDT configuration sent from a core network device.
[0484] The processing unit 1503 is configured to determine a fifth MDT configuration according to the third MDT configuration.
[0485] The sending unit 1502 is configured to send a fifth MDT configuration to the terminal device.
[0486] The first indication information is used to indicate the third MDT configuration stored in the core network device. The first indication information includes an identifier of the terminal device. The third MDT configuration includes an MDT configuration corresponding to the terminal device.
[0487] In a possible implementation manner, the receiving unit 1501 is further configured to: receive a third MDT configuration and a target TRSR identifier sent from a core network device.
[0488] In a possible implementation manner, the first indication information is used to indicate the third MDT configuration and the target TRSR identifier stored in the core network device, and the first indication information includes the target TRSR identifier and / or the identifier of the terminal device.
[0489] In a possible implementation manner, the receiving unit 1501 is further configured to: receive second indication information sent from the terminal device, wherein the second indication information is used to indicate that a logged MDT measurement report is stored in the terminal device.
[0490] In a possible implementation, the sending unit 1503 is further used to: send first response information to the terminal device, where the first response information is used to request a logged MDT measurement report.
[0491] In a possible implementation manner, the receiving unit 1501 is further configured to: receive a logged MDT measurement report sent from a terminal device.
[0492] In a possible implementation manner, the sending unit 1503 is further configured to: send a logged MDT measurement report to the TCE.
[0493] In a possible implementation manner, the sending unit 1503 is further configured to: send the TR information and / or the MDT activation type to the core network device.
[0494] In a possible implementation manner, the processing unit 1502 is further configured to: use the target TRSR identifier and the TR information to associate the immediate MDT measurement report and the logged MDT measurement report of the terminal device.
[0495] In a possible implementation manner, the fifth MDT configuration may be the same as the fourth MDT configuration.
[0496] It is understandable that the above Figures 7 to 15 For a more detailed description of the functions performed by each unit in the described communication devices, reference may be made to the introduction of the steps performed by the terminal device or the network device in the aforementioned method embodiment.
[0497] The embodiment of the present application also provides a chip. Fig.16 1 shows a schematic diagram of the structure of a chip 1600. The chip 1600 includes one or more processors 1601 and an interface circuit 1602. Optionally, the chip 1600 may also include a bus 1603.
[0498] The processor 1601 may be an integrated circuit chip with signal processing capability. In the implementation process, each step of the above communication method may be completed by an integrated logic circuit of hardware in the processor 1601 or by instructions in the form of software.
[0499] Exemplarily, the processor 1601 may be a general purpose processor, a digital signal processing (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods and steps disclosed in the embodiments of the present application may be implemented or executed. The general purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
[0500] The interface circuit 1602 can be used to send or receive data, instructions or information. The processor 1601 can use the data, instructions or other information received by the interface circuit 1602 to process, and can send the processing completion information through the interface circuit 1602.
[0501] Optionally, the chip also includes a memory, which may include a read-only memory and a random access memory, and provides operation instructions and data to the processor. A portion of the memory may also include a non-volatile random access memory (NVRAM).
[0502] Optionally, the memory stores executable software modules or data structures, and the processor can perform corresponding operations by calling operation instructions stored in the memory (the operation instructions can be stored in the operating system).
[0503] Optionally, the chip can be used in the communication device involved in the embodiment of the present application. Optionally, the interface circuit 1602 can be used to output the execution result of the processor 1601. The communication method provided in one or more embodiments of the embodiment of the present application can refer to the above embodiments, which will not be repeated here.
[0504] It should be noted that the corresponding functions of the processor 1601 and the interface circuit 1602 can be implemented through hardware design, software design, or a combination of hardware and software, and there is no limitation here.
[0505] Fig.17 The following is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. The communication device can be applied to the scenario shown in the above method embodiment. For the convenience of explanation, Fig.17 Only the main components of the communication device are shown, including a processor 1701, a memory 1702, a control circuit 1703, and an input-output device 1704. The processor 1701 is mainly used to process the communication protocol and communication data, execute the software program, and process the data of the software program. The memory 1702 is mainly used to store the software program and data. The control circuit 1703 is mainly used for power supply and transmission of various electrical signals. The input-output device 1704 is mainly used to receive data input by the user and output data to the user.
[0506] When the communication device is a processor 1701, the control circuit 1703 can be a mainboard, the memory 1702 includes a hard disk, RAM, ROM and other media with storage functions, the processor 1701 can include a baseband processor 1701 and a central processing unit, the baseband processor is mainly used to process the communication protocol and communication data, the central processing unit is mainly used to control the entire communication device, execute software programs, and process the data of the software programs, and the input and output device 1704 includes a display screen, a keyboard and a mouse, etc.; the control circuit 1703 can further include or connect a transceiver circuit or a transceiver, such as: a network cable interface, etc., for sending or receiving data or signals, such as data transmission and communication with other devices. Further, it can also include an antenna for sending and receiving wireless signals, and for data / signal transmission with other devices.
[0507] An embodiment of the present application also provides a communication device, which includes: at least one processor, when the at least one processor executes program code or instructions, the above-mentioned related method steps are implemented to implement the communication method in the above-mentioned embodiment.
[0508] Optionally, the device may further include at least one memory, and the at least one memory is used to store the program code or instruction.
[0509] An embodiment of the present application also provides a computer storage medium, in which computer instructions are stored. When the computer instructions are executed on a communication device, the communication device executes the above-mentioned related method steps to implement the communication method in the above-mentioned embodiment.
[0510] The embodiment of the present application also provides a computer program product. When the computer program product is run on a computer, the computer is caused to execute the above-mentioned related steps to implement the communication method in the above-mentioned embodiment.
[0511] The embodiment of the present application also provides a communication device, which may be a chip, an integrated circuit, a component or a module. Specifically, the device may include a connected processor and a memory for storing instructions, or the device may include at least one processor for obtaining instructions from an external memory. When the device is running, the processor may execute instructions so that the chip executes the communication method in each of the above method embodiments.
[0512] The embodiment of the present application further provides a communication system, which includes: a plurality of the above-mentioned communication devices. The above-mentioned communication devices are used to execute the communication methods in the above-mentioned method embodiments.
[0513] It should be understood that in various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
[0514] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the embodiments of the present application.
[0515] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.
[0516] In the several embodiments provided in the embodiments of the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the above 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 through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0517] The units described above as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, and may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0518] In addition, 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.
[0519] If the above functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or the 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, a server, or a network device, etc.) to perform all or part of the steps of the above methods of each embodiment of the embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.
Claims
1. A communication method, characterized in that: The method comprises: Receiving first information from a first network device, where the first information is used to indicate a first minimization of drive tests (MDT) configuration, where the first MDT configuration includes an MDT configuration corresponding to a terminal device; Sending the first information to a second network device; receiving a second MDT configuration from the second network device, where the second MDT configuration is obtained based on the first MDT configuration; Perform MDT measurement according to the second MDT configuration.
2. The method according to claim 1, characterized in that The method further comprises: The first information is saved before disconnecting from the first network device.
3. The method according to claim 1 or 2, characterized in that: The sending the first information to the second network device includes: The first information is sent to the second network device after establishing a connection with the second network device.
4. The method according to any one of claims 1 to 3, characterized in that The second MDT configuration includes an Immediate MDT configuration.
5. The method according to any one of claims 1 to 4, characterized in that The first information includes an index of the first MDT configuration.
6. The method according to any one of claims 1 to 5, characterized in that The method further comprises: receiving second information from the first network device, where the second information is used to indicate first MDT data, where the first MDT data is measured according to the first MDT configuration; The second information is sent to the second network device.
7. The method according to claim 6, characterized in that The second information includes an index of the first MDT data.
8. A communication method, characterized in that: The method comprises: receiving first information from a second network device, where the first information is used to indicate a first MDT configuration, where the first MDT configuration includes an MDT configuration corresponding to the terminal device; The first MDT configuration is sent to the second network device.
9. The method according to claim 8, characterized in that The method further comprises: Send the first information to the terminal device.
10. The method according to claim 8 or 9, characterized in that: The method further comprises: Receive third information from a core network device or an operation maintenance management (OAM), where the third information is used to instruct to save the first MDT configuration.
11. The method according to claim 11, characterized in that: The third information includes an identifier of the terminal device and an index of the first MDT configuration.
12. The method according to claim 11, characterized in that The third information further includes a retention duration of the first MDT configuration and / or an index range of the first MDT configuration.
13. The method according to any one of claims 8 to 12, characterized in that The method further comprises: receiving second information from a second network device, where the second information is used to indicate first MDT data, where the first MDT data is measured according to the first MDT configuration; The first MDT data is sent to the second network device.
14. The method according to any one of claims 8 to 13, characterized in that The method further comprises: Sending second information to the terminal device, where the second information is used to indicate first MDT data, where the first MDT data is obtained by measuring according to the first MDT configuration.
15. The method according to any one of claims 8 to 14, characterized in that The method further comprises: Fourth information is received from a core network device or an OAM, where the fourth information is used to instruct to save first MDT data, where the first MDT data is obtained by measuring according to the first MDT configuration.
16. The method according to claim 15, characterized in that The fourth information includes an identifier of the terminal device and an index of the first MDT data.
17. The method according to claim 16, characterized in that The fourth information further includes a retention duration of the first MDT data and / or an index range of the first MDT data.
18. A communication method, characterized in that: The method comprises: Sending first information to a first network device, where the first information is used to indicate a first MDT configuration, where the first MDT configuration includes an MDT configuration corresponding to the terminal device; receiving the first MDT configuration from the first network device; determining a second MDT configuration according to the first MDT configuration; Send the second MDT configuration to the terminal device.
19. The method according to claim 18, characterized in that The method further comprises: Receive the first information from the terminal device.
20. The method according to claim 18 or 19, characterized in that The method further comprises: Sending second information to the first network device, where the second information is used to indicate first MDT data, where the first MDT data is measured according to the first MDT configuration; The first MDT data is received from the first network device.
21. The method according to any one of claims 18 to 20, characterized in that The method further comprises: Second information is received from the terminal device, where the second information is used to indicate first MDT data, where the first MDT data is obtained by measuring according to the first MDT configuration.
22. A communication device, characterized in that: Comprising means for performing the method of any one of claims 1 to 7, any one of 8 to 17 or any one of 18 to 21.
23. A communication device, characterized in that: The device comprises a processor coupled to a memory, wherein the memory is used to store instructions. When the instructions are executed by the processor, the device performs the method as claimed in any one of claims 1 to 7, any one of 8 to 17, or any one of 18 to 21.
24. A computer-readable storage medium for storing a computer program, characterized in that: When the computer program is executed, the method of any one of claims 1 to 7, any one of 8 to 17, or any one of 18 to 21 is executed.
25. A computer program product, comprising instructions, characterized in that: When the instructions are executed, the method of any one of claims 1 to 7, any one of 8 to 17, or any one of 18 to 21 is executed.
26. A chip comprising at least one processor and a memory, characterized in that: The at least one processor executes a program or instruction stored in the memory so that the information processing device implements the method of any one of claims 1 to 7, any one of 8 to 17, or any one of 18 to 21.
Citation Information
Cited By
Communication method and apparatus
EP4742734A1
Communication method and apparatus
WO2025031044A1