Communication methods and devices

Abstract

A communication method and apparatus are provided that relate to the field of communication technology. The method includes receiving first information from a first network device; transmitting the first information to a second network device; receiving a second MDT setting from the second network device; and performing an MDT measurement based on the second MDT setting. The first information indicates a first MDT setting, the first MDT setting includes an MDT setting corresponding to a terminal device, and the second MDT setting is obtained based on the first MDT setting. In the method provided in the embodiments of the present application, after the terminal device has moved from an idle state to a connected state, the terminal device can transmit first information indicating an MDT setting corresponding to the terminal device to a newly connected second network device, thereby the second network device, by using the first information, obtains an MDT setting via the first network device that was previously connected to the terminal device, delivers the MDT setting to the terminal device, and thereby maintains MDT continuity.

Description

Technical Field

[0001] Embodiments of the present application relate to the field of communication technology, and in particular, relate to a communication method and apparatus.

Background Art

[0002] In the field of mobile communication, a mobile communication network can be monitored through minimization of drive-test (MDT). MDT is for optimizing mobile communication networks by finding problems such as weak coverage, coverage holes, and overshoot in mobile communication networks by using measurement reports reported by terminal devices that carry location information.

[0003] In some scenarios, for example, in an artificial intelligence (AI) model training process, a terminal device is expected to perform continuous MDT, so that a network device can obtain continuous MDT data to improve network optimization effects.

[0004] However, when the radio resource control (RRC) state of the terminal device changes, the terminal device may not be able to continuously perform MDT measurement.

Summary of the Invention

[0005] Embodiments of the present application provide a communication method and apparatus, so that a terminal device can maintain MDT continuity. To achieve the foregoing objective, the following technical solutions are used in the embodiments of the present application.

[0006] According to a first aspect, an embodiment of the present application provides a communication method. The method may be performed by a terminal device, or by a module used in the terminal device (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of performing all or part of the functions of the terminal device. The method includes: receiving first information from a first network device; transmitting the first information to a second network device; receiving a second MDT setting from the second network device; and performing an MDT measurement based on the second MDT setting. The first information indicates a first MDT setting, the first MDT setting includes an MDT setting corresponding to a terminal device. The second MDT setting is obtained based on the first MDT setting.

[0007] In the method provided in this embodiment of the present application, after a terminal device transitions from an idle state to a connected state, the terminal device can transmit first information indicating the MDT settings corresponding to the terminal device to a newly connected second network device. As a result, the second network device uses the first information to obtain the MDT settings via the first network device previously connected to the terminal device and delivers the MDT settings to the terminal device. This avoids the case where the terminal device stops MDT measurement due to the newly connected network device failing to transmit the second MDT settings to the terminal device, thereby maintaining MDT continuity and obtaining continuous MDT data to satisfy the requirement for obtaining continuous MDT data in some scenarios. For example, the network device can obtain continuous MDT data for AI model training to improve the accuracy of AI model training and improve the effectiveness of applying the AI ​​model.

[0008] In possible implementations, the first information may be stored before the terminal device leaves the first network device. In this way, interruptions to the MDT caused by the terminal device failing to transmit the first information to the second network device due to the release of the first information after the terminal device has disconnected from the first network device are avoided.

[0009] In possible implementations, the first information may be transmitted to the second network device after a connection to the second network device has been established, thereby enabling the terminal device to obtain the second MDT settings from the second network device and maintain the continuity of MDT measurement.

[0010] In possible implementations, the second MDT setting may include an Immediate Drive Test Minimization (Immediate MDT) setting.

[0011] For example, by using the immediate MDT setting in the second MDT setting, the terminal device can measure information or parameters such as the amount of data the terminal device has collected, Internet Protocol (IP) throughput, packet transmission delay, packet loss rate, and processing delay.

[0012] In possible implementations, the first piece of information may include an index of the first MDT setting.

[0013] It will be understood that the first network device is capable of storing MDT settings for multiple terminal devices. The index of the first MDT settings helps the first network device determine which MDT setting corresponds to a terminal device from among the MDT settings for multiple terminal devices.

[0014] In possible implementations, indices of multiple MDT settings may be stored in an index list within a second network device. The second network device can look up the index list for the index corresponding to a terminal device and then send first information to the first network device indicating that the MDT setting for the terminal device, i.e., the first MDT setting, needs to be retrieved.

[0015] In possible implementations, second information may be received from the first network device and transmitted to the second network device. The second information represents the first MDT data, which is obtained through measurements based on the first MDT settings.

[0016] It should be noted that in some scenarios, network devices need to acquire continuous MDT data, for example, to train an AI model using continuous MDT data. In this case, a terminal device can send second information indicating the first MDT data acquired through measurements using the first MDT setting to a newly connected second network device. As a result, the second network device uses the second information to acquire the first MDT data via the first network device that was previously connected to the first network device, and trains the AI ​​model using the first MDT data. This can improve the predictive accuracy of the model for data (e.g., future throughput and trajectory information of the terminal) and improve the network optimization effect.

[0017] In possible implementations, the second piece of information may include an index of the first MDT data.

[0018] It will be understood that the first network device is capable of storing multiple MDT data. An index of the first MDT data helps the first network device determine the first MDT data from among multiple MDT data.

[0019] In possible implementations, the indices of multiple MDT data may be stored in an index list within a second network device. The second network device can search the index list for the index corresponding to a terminal device and then send the second information to the first network device to indicate that the MDT data corresponding to the terminal device, i.e., the first MDT data, needs to be retrieved.

[0020] According to a second aspect, embodiments of the present application provide a communication method. The method may be performed by a network device, or by a module used in a network device (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of performing all or part of the functions of a network device. The method includes: receiving first information from a second network device, wherein the first information indicates a first MDT setting, and the first MDT setting includes an MDT setting corresponding to a terminal device; and transmitting the first MDT setting to a second network device.

[0021] For beneficial effects that can be achieved by the method provided in the second embodiment, please refer to the beneficial effects of the method provided in the first embodiment. Further details will not be provided here.

[0022] In possible implementations, the first piece of information can be sent to the terminal device.

[0023] In a possible implementation, the third information may be received from a core network device or Operation, Administration, and Maintenance (OAM), and the third information indicates to store the first MDT configuration.

[0024] In a possible implementation, the third information may include an identifier of a terminal device and an index of the first MDT configuration.

[0025] In a possible implementation, the third information may further include a retention period of the first MDT configuration and / or an index range of the first MDT configuration.

[0026] In a possible implementation, the second information may be received from a second network device, the second information indicates first MDT data, the first MDT data is obtained through measurement based on the first MDT configuration; and the first MDT data is transmitted to the second network device.

[0027] In a possible implementation, the second information may be transmitted to a terminal device, the second information indicates first MDT data, and the first MDT data is obtained through measurement based on the first MDT configuration.

[0028] In a possible implementation, the fourth information may be received from a core network device or OAM, the fourth information indicates to store first MDT data, and the first MDT data is obtained through measurement based on the first MDT configuration.

[0029] In a possible implementation, the fourth information may include an identifier of a terminal device and an index of the first MDT data.

[0030] In a possible implementation, the fourth information may further include a retention period of the first MDT data and / or an index range of the first MDT data.

[0031] According to a third aspect, embodiments of the present application provide a communication method. The method may be performed by a network device, or by a module used in a network device (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of performing all or part of the functions of a network device. The method includes: transmitting first information to a first network device, wherein the first information indicates a first MDT setting, the first MDT setting includes an MDT setting corresponding to a terminal device; receiving the first MDT setting from the first network device; determining a second MDT setting based on the first MDT setting; and transmitting the second MDT setting to a terminal device.

[0032] For beneficial effects that can be achieved by the method provided in the third aspect, please refer to the beneficial effects of the method provided in the first aspect. Further details will not be provided here.

[0033] In possible implementations, the first piece of information may be received from the terminal device.

[0034] In possible implementations, the second information may be transmitted to the first network device, the second information may indicate the first MDT data, the first MDT data is obtained through measurements based on the first MDT settings; and the first MDT data is received from the first network device.

[0035] In a possible implementation, the second piece of information may be received from a terminal device, and this second piece of information represents the first MDT data, which is obtained through measurements based on the first MDT settings.

[0036] According to a fourth aspect, embodiments of the present application provide a communication method. The method may be performed by a terminal device, or by a module used in a terminal device (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of performing all or part of the functions of a terminal device. The method includes: receiving a first MDT setting from a first network device, the first MDT setting including an MDT setting corresponding to a terminal device; transmitting the first MDT setting to a second network device; receiving a second MDT setting from a second network device, the second MDT setting being obtained based on the first MDT setting; and performing an MDT measurement based on the second MDT setting.

[0037] In the method provided in this embodiment of the present application, after a terminal device transitions from an idle state to a connected state, the terminal device can transmit a first MDT configuration, including the MDT configuration corresponding to the terminal device, to a newly connected second network device, thereby enabling the second network device to deliver the MDT configuration to the terminal device using the first MDT configuration. This avoids the case where the terminal device stops MDT measurement due to the newly connected network device failing to transmit the second MDT configuration to the terminal device, thereby maintaining MDT continuity and acquiring continuous MDT data to satisfy the requirement for acquiring continuous MDT data in some scenarios. For example, the network device can acquire continuous MDT data for AI model training to improve the accuracy of AI model training and enhance the effectiveness of applying the AI ​​model.

[0038] In possible implementations, the first MDT setting may be stored before the terminal device leaves the first network device.

[0039] It will be understood that a terminal device will release some information that is not supposed to be saved after being disconnected from the first network device. To avoid the case where the first MDT settings are released, the terminal device can store the first MDT settings before being disconnected from the first network device (i.e., before entering an idle state) and acquire continuous MDT data to satisfy the requirement of acquiring continuous MDT data in some scenarios.

[0040] In possible implementations, the first MDT configuration may be sent to the second network device after the connection to the second network device has been established.

[0041] It will be understood that when a terminal establishes a connection to a second network device, this indicates that the terminal device enters a connected state. In this case, the terminal device needs to obtain the MDT settings from the second network device in order to maintain MDT continuity. Therefore, after establishing a connection to the second network device, the terminal needs to send the first MDT settings to the second network device, and as a result, the second network device delivers the MDT settings to the terminal device.

[0042] In a possible implementation, a fifth piece of information may be received from the first network device, and this fifth piece of information instructs the first MDT to remember its settings.

[0043] It can be seen that a terminal device can receive fifth information from a first network device and store the first MDT settings based on the instructions in the fifth information. This avoids an MDT interruption caused by the terminal device failing to send the first MDT settings to the second network device because it does not remember the first MDT settings.

[0044] In possible implementations, the first MDT data may be received from a first network device, acquired through measurements based on a first MDT configuration, and transmitted to a second network device.

[0045] It should be noted that in some scenarios, network devices need to acquire continuous MDT data, for example, to train an AI model using continuous MDT data. In this case, a terminal device can send second information indicating the first MDT data acquired through measurements using the first MDT setting to a newly connected second network device. As a result, the second network device uses the second information to acquire the first MDT data via the first network device that was previously connected to the first network device, and trains the AI ​​model using the first MDT data. This can improve the predictive accuracy of the model for data (e.g., future throughput and trajectory information of the terminal) and improve the network optimization effect.

[0046] In a possible implementation, the sixth piece of information may be received from the first network device, which instructs the first MDT data to be stored, and the first MDT data is obtained through measurements based on the first MDT settings.

[0047] It can be seen that the terminal device can receive sixth information from the first network device and store the first MDT data based on the instructions of the sixth information. This avoids the second network device failing to train the AI ​​model by using the first MDT data because the terminal device fails to transmit the first MDT data to the second network device due to the terminal device not having stored the first MDT data.

[0048] According to a fifth aspect, embodiments of the present application provide a communication method. The method may be performed by a network device, or by a module used in a network device (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of performing all or part of the functions of a network device. The method includes: receiving a first MDT setting from a core network device or OAM, the first MDT setting including an MDT setting corresponding to a terminal device; and transmitting the first MDT setting to the terminal device.

[0049] For beneficial effects that can be achieved by the method provided in the fifth aspect, please refer to the beneficial effects of the method provided in the fourth aspect. Further details will not be explained here again.

[0050] In possible implementations, the fifth piece of information may be sent to the terminal device, which instructs the terminal device to remember the first MDT setting.

[0051] In possible implementations, the first MDT data can be transmitted to a terminal device, and the first MDT data is acquired through measurements based on the first MDT settings.

[0052] In possible implementations, a sixth piece of information can be transmitted to a terminal device, which instructs the terminal device to store the first MDT data, and the first MDT data is obtained through measurements based on the first MDT settings.

[0053] According to a sixth aspect, embodiments of the present application provide a communication method. The method may be performed by a network device, or by a module used in a network device (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of performing all or part of the functions of a network device. The method includes: receiving a first MDT setting from a terminal device, the first MDT setting including an MDT setting corresponding to the terminal device; determining a second MDT setting based on the first MDT setting; and transmitting the second MDT setting to the terminal device.

[0054] For beneficial effects that can be achieved by the method provided in the sixth aspect, please refer to the beneficial effects of the method provided in the fourth aspect. Further details will not be explained here again.

[0055] In possible implementations, the first MDT data can be received from a terminal device, and the first MDT data is acquired through measurements based on the first MDT settings.

[0056] According to the seventh aspect, embodiments of the present application provide a communication method. The method may be performed by a terminal device, or by a module used in the terminal device (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of performing all or part of the functions of the terminal device. The method includes: receiving a fourth MDT setting from a first network device; transmitting first instruction information to a second network device; receiving a fifth MDT setting from the second network device; and performing an MDT measurement based on the fifth MDT setting. The fourth MDT setting is obtained based on a third MDT setting. The third MDT setting is a management-based MDT setting. The third MDT setting includes an MDT activation type, an immediate MDT setting, a logged MDT setting, and trace reference (TR) information. The TR information indicates the first TR and the second TR. The first TR is the TR for immediate MDT settings, and the second TR is the TR for logging MDT settings. The first TR is the same as the second TR.

[0057] In the method provided in this embodiment of the present application, after the terminal device transitions from an idle state to a connected state, the terminal device can transmit first instruction information to a newly connected second network device, and as a result, the second network device uses the first instruction information to obtain MDT settings from the core network device and deliver the MDT settings to the terminal device. This avoids the case where the terminal device stops MDT measurement due to the newly connected network device not transmitting a fifth MDT setting to the terminal device, thereby maintaining MDT continuity and obtaining continuous MDT data to satisfy the requirement for obtaining continuous MDT data in some scenarios. For example, the network device can obtain continuous MDT data for AI model training to improve the accuracy of AI model training and improve the effectiveness of applying the AI ​​model.

[0058] In possible implementations, the MDT activation type included in the third MDT setting instructs the terminal device to perform immediate MDT measurements and logged MDT measurements.

[0059] In possible implementations, a Trace Recording Session Reference (TRSR) identifier may be further received from the first network device, and the first instruction information may include a target TRSR identifier and / or an identifier for a terminal device. The target TRSR identifier is the TRSR identifier assigned to the terminal device by the first network device. The terminal device corresponding to the MDT data can be identified by using the TRSR identifier.

[0060] The method provided in this embodiment of the present application introduces a new MDT activation type, "Immediate MDT and Logged MDT," which means that the OAM can associate immediate MDT and logged MDT data for the same terminal device by sending immediate MDT and logged MDT settings with the same TR and using the TR and target TRSR identifier. This avoids the problem of not being able to obtain continuous MDT data for the same terminal device because it is not possible to associate immediate MDT data and logged MDT data for the same terminal device due to differences between the TRs of the immediate MDT settings and the logged MDT settings for the same terminal device. Thus, in some scenarios, the requirement for obtaining continuous MDT data is met.

[0061] In possible implementations, the second instruction information may be further transmitted to a second network device. The second instruction information indicates that a logged MDT measurement report is stored on the terminal device. The second instruction information may also be used to notify that a logged MDT measurement report is stored on the terminal device, and as a result, the second network device retrieves the logged MDT measurement report from the terminal device when it is needed.

[0062] In possible implementations, the first and second instruction information may be the same. Using the same information to transmit the first and second instruction information helps reduce signaling overhead.

[0063] According to the eighth aspect, embodiments of the present application provide a communication method. The method may be performed by a network device, or by a module used in a network device (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of performing all or part of the functions of a network device. The method includes: receiving a third MDT setting transmitted by OAM, determining a fourth MDT setting based on the third MDT setting, transmitting the fourth MDT setting to a terminal device, and transmitting the fourth MDT setting to a core network device. The third MDT setting is a management-based MDT setting. The third MDT setting includes an MDT activation type, an immediate MDT setting, a logging MDT setting, and TR information. The TR information indicates a first TR and a second TR, where the first TR is the TR for the immediate MDT setting and the second TR is the TR for the logging MDT setting. The first TR is the same as the second TR. The fourth MDT setting is the MDT setting corresponding to the terminal device.

[0064] For beneficial effects that can be achieved by the method provided in the eighth aspect, please refer to the beneficial effects of the method provided in the seventh aspect. Further details are not provided here.

[0065] In possible implementations, the MDT activation type included in the third MDT setting instructs the terminal device to perform immediate MDT measurements and logging MDT measurements.

[0066] In possible implementations, the fourth MDT setting and target TRSR identifier can be transmitted to the core network device. The target TRSR identifier is the TRSR identifier assigned to the terminal device by the first network device.

[0067] In possible implementations, the first TR and the second TR may be indicated by using the same TR.

[0068] In another possible implementation, the first TR and the second TR may be indicated by using two identical TRs.

[0069] In possible implementations, the third MDT setting may further include the MDT area range.

[0070] In possible implementations, the fourth MDT setting may further include an identifier for the terminal device.

[0071] In possible implementations, the target TRSR identifier may be further transmitted to the terminal device.

[0072] According to the ninth aspect, embodiments of the present application provide a communication method. The method may be performed by a network device, or by a module used in a network device (e.g., a processor, chip, or chip system), or by a logical node, logical module, or software capable of performing all or part of the functions of a network device. The method includes: receiving first instruction information from a terminal device; transmitting the first instruction information to a core network device; receiving a third MDT setting transmitted from the core network device; determining a fifth MDT setting based on the third MDT setting; and transmitting the fifth MDT setting to the terminal device. The first instruction information indicates a third MDT setting stored in the core network device. The first instruction information includes an identifier for the terminal device. The third MDT setting includes an MDT setting corresponding to the terminal device.

[0073] For beneficial effects that can be achieved by the method provided in the ninth aspect, please refer to the beneficial effects of the method provided in the seventh aspect. Further details are not provided here.

[0074] In possible implementations, a third MDT configuration and target TRSR identifier transmitted by the core network device may be received.

[0075] In a possible implementation, the first instruction information indicates a third MDT configuration and target TRSR identifier stored in the core network device, and the first instruction information includes the target TRSR identifier and / or the identifier of the terminal device.

[0076] In possible implementations, a second instruction information transmitted by the terminal device may be received. This second instruction information indicates that a logged MDT measurement report is stored on the terminal device.

[0077] In possible implementations, the first response information may be further sent to a terminal device to receive a logged MDT measurement report sent by the terminal device. The first response information is used to request the logged MDT measurement report.

[0078] In possible implementations, the logged MDT measurement report may be further sent to a trace collection entity (TCE).

[0079] In possible implementations, TR information and / or MDT activation type may be further transmitted to the core network device.

[0080] In possible implementations, the immediate MDT measurement report and the logged MDT measurement report of the terminal device may be associated by using the target TRSR identifier and TR information.

[0081] In possible implementations, the fifth MDT setting may be the same as the fourth MDT setting.

[0082] According to the tenth aspect, an embodiment of the present application provides a communication device. The device may be a terminal device, or a module used in a terminal device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of performing all or part of the functions of a terminal device. The device may be configured to perform a method according to any one of the possible implementations of the first, fourth, or seventh aspects.

[0083] For example, the apparatus includes a module or unit configured to perform a method according to any one of the possible implementations of the first or fourth embodiment.

[0084] According to the tenth aspect, an embodiment of the present application provides a communication device. The device may be a network device, or a module used in a network device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of performing all or part of the functions of a network device. The device may be configured to perform a method according to any one of the possible implementations of the second, third, fifth, eighth, or ninth aspects.

[0085] For example, the apparatus includes a module or unit configured to perform a method according to any one of the possible implementations of the second, third, fifth, or sixth embodiment.

[0086] According to the twelfth aspect, an embodiment of the present application provides a communication device. The device may be a terminal device, or a module used in a terminal device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of performing all or part of the functions of a terminal device. The communication device includes at least one processor. When at least one processor executes program code or instructions, a method according to any one of the possible implementations of the first, fourth, or seventh aspect is performed.

[0087] Optionally, the communication device may further include at least one memory, at least one of which is configured to store program code or instructions.

[0088] According to the 13th aspect, an embodiment of the present application provides a communication device. The device may be a network device, or a module used in a network device (e.g., a processor, chip, or chip system), or network· A logical node, logical module, or software capable of performing all or part of the device's functions may be included. The communication device includes at least one processor. When at least one processor executes program code or instructions, a method according to any one of the possible implementations of the second, third, fifth, eighth, or ninth embodiment is performed.

[0089] Optionally, the communication device may further include at least one memory, at least one of which is configured to store program code or instructions.

[0090] According to 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 includes memory. At least one processor is configured to execute code in memory. When at least one processor is executing code, the chip implements a method according to any one of the preceding aspects.

[0091] Optionally, the chip may be an integrated circuit.

[0092] According to the 15th aspect, an embodiment of the present application further provides a computer-readable storage medium configured to store a computer program. The computer program is used to carry out a method according to any one of the preceding aspects.

[0093] According to the sixteenth aspect, the embodiments of the present application further provide a computer program product including instructions. When the computer program product is executed on a computer, the computer becomes capable of performing any one of the methods described above.

[0094] The communication devices, computer storage media, computer program products, and chips provided in the embodiments are all configured to perform the methods provided above. Therefore, for the beneficial effects that can be achieved by the communication devices, computer storage media, computer program products, and chips, please refer to the beneficial effects of the methods provided above. Further details are not described here. [Brief explanation of the drawing]

[0095] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings illustrating the embodiments are briefly described below. It will be apparent that the accompanying drawings in the following description represent only a portion of the embodiments of this application, and that those skilled in the art can derive other accompanying drawings from these without any creative effort.

[0096] [Figure 1] Figure 1 is a structural diagram of a communication system according to an embodiment of the present application.

[0097] [Figure 2] Figure 2 is a schematic flowchart of the communication method according to the embodiment of the present application.

[0098] [Figure 3] Figure 3 is a schematic flowchart of another communication method according to the embodiment of the present application.

[0099] [Figure 4] Figure 4 is a schematic flowchart of yet another communication method according to an embodiment of the present application.

[0100] [Figure 5] Figure 5 is a schematic flowchart of yet another communication method according to an embodiment of the present application.

[0101] [Figure 6] Figure 6 is a schematic flowchart of yet another communication method according to an embodiment of the present application.

[0102] [Figure 7] Figure 7 is a structural diagram of a communication device according to an embodiment of the present application.

[0103] [Figure 8] Figure 8 is a structural diagram of another communication device according to an embodiment of the present application.

[0104] [Figure 9] Figure 9 is a structural diagram of yet another communication device according to an embodiment of the present application.

[0105] [Figure 10] Figure 10 is a structural diagram of yet another communication device according to one embodiment of the present application.

[0106] [Figure 11] Figure 11 is a structural diagram of yet another communication device according to an embodiment of the present application.

[0107] [Figure 12] Figure 12 is a structural diagram of yet another communication device according to an embodiment of the present application.

[0108] [Figure 13] Figure 13 is a structural diagram of yet another communication device according to an embodiment of the present application.

[0109] [Figure 14] Figure 14 is a structural diagram of yet another communication device according to an embodiment of the present application.

[0110] [Figure 15] Figure 15 is a structural diagram of yet another communication device according to an embodiment of the present application.

[0111] [Figure 16] Figure 16 is a structural diagram of a chip according to an embodiment of the present application.

[0112] [Figure 17] Figure 17 is a structural diagram of another communication device according to an embodiment of the present application. [Modes for carrying out the invention]

[0113] The technical solutions of the embodiments of this application will be clearly and fully described below with reference to the accompanying drawings of the embodiments of this application. It will be clear that the embodiments described are only a part, and not the entirety, of the embodiments of this application. All other embodiments that can be grasped by those skilled in the art based on the embodiments of this application without creative effort will fall within the scope of protection of the embodiments of this application.

[0114] The term "and / or" in this specification merely describes a relationship of relevance to describe the relevant subjects, indicating that there may be three possible relationships. For example, A and / or B could represent the following three cases: when only A exists, when both A and B exist, and when only B exists.

[0115] In this specification and accompanying drawings of embodiments of the present application, terms such as "first," "second," etc., are intended to distinguish between different subjects or different processes of the same subject, but do not indicate a specific order of subjects.

[0116] Furthermore, the terms “including,” “having,” and other variations thereof as used in the description of embodiments of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device comprising a series of steps or units is not limited to the listed steps or units, but optionally further includes other unlisted steps or units, or optionally further includes other specific steps or units of the process, method, product, or device.

[0117] It should be noted that in the description of embodiments of this application, terms such as “example” or “for example” indicate that an example, illustration, or explanation is being given. Any embodiment or design solution described as “example” or “for example” in the embodiments of this application is not described as being preferable to or having more advantages than another embodiment or design solution. More precisely, the use of terms such as “example” or “for example” is intended to present the relevant concepts in a particular way.

[0118] MDT is a technique used to monitor mobile communication networks for network optimization. In some scenarios, such as in an AI model training process, terminal devices are expected to perform continuous MDT, which in turn allows network devices to acquire continuous MDT data to improve network optimization effects. However, if the terminal device's RRC state changes, the terminal device may not be able to continuously perform MDT measurements. Specifically, a connected terminal device can perform measurements based on MDT settings transmitted by the network device. When a terminal device switches from a connected state to an idle state, the terminal device is disconnected from the network device and releases its MDT settings. If a terminal device switches from an idle state back to a connected state and then establishes a connection to a new network device, the terminal device may stop performing MDT measurements because the newly connected network device does not transmit MDT settings to the terminal device. In this application, the change in the terminal device's RRC state may also be referred to as the terminal device's cross-connect state, including, for example, a scenario in which a terminal device enters an idle state from a connected state and then enters a connected state again.

[0119] Therefore, the embodiments of this application provide a communication method that enables a terminal device to maintain MDT continuity.

[0120] The technical solutions provided in embodiments of this application may be applicable to a variety of communication systems. These solutions may be applied to 5th Generation Mobile Communication Technology (5G) communication systems, future evolutionary systems, multiple centralized communication systems, or similar systems, or to existing communication systems, or similar systems. Application scenarios for the technical solutions provided in embodiments of this application may include multiple scenarios, such as machine-to-machine (M2M), macro-micro communications, enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (uRLLC), and massive machine-type communications (mMTC). These scenarios may include, but are not limited to, scenarios of communication between terminal devices, scenarios of communication between network devices, scenarios of communication between network devices and terminal devices, and similar systems. The following examples illustrate how technical solutions are applied to communication scenarios between network devices and terminal devices.

[0121] Figure 1 is a possible non-limiting diagram of the aforementioned communication system. As shown in Figure 1, 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., 110a and 110b in Figure 1, collectively referred to as 110) and at least one terminal device (e.g., 120a to 120j in Figure 1, collectively referred to as 120). The RAN 100 may further include other RAN nodes, e.g., radio relay devices and / or radio backhaul devices (not shown in Figure 1). The terminal device 120 is connected to the RAN node 110 wirelessly. The RAN node 110 is connected to the core network 200 wirelessly or wired. The core network devices within the core network 200 and the RAN nodes 110 within the RAN 100 may be different physical devices, or they may be the same physical device that integrates the logical functions of the core network and the logical functions of the wireless access network.

[0122] RAN 100 may be a cellular system associated with the 3rd generation partnership project (3GPP), such as a 4G mobile communication system, a 5G mobile communication system, or a future evolved system (such as a 6G mobile communication system). Alternatively, RAN 100 may be an open access network (open RAN, O-RAN, or ORAN), a cloud radio access network (CRAN), or a wireless fidelity (Wi-Fi) system. Alternatively, RAN 100 may be a communication system that integrates two or more of the aforementioned systems.

[0123] RAN nodes 110, sometimes called access network devices, RAN entities, or access nodes, form part of a communication system and assist terminal devices in performing wireless access. Multiple RAN nodes 110 in the communication system 10 may be of the same type or of different types. In some scenarios, the roles of RAN nodes 110 and terminal devices 120 are relative. For example, network element 120i in Figure 1 may be a helicopter or unmanned aerial vehicle and may be configured as a mobile base station. With respect to terminal device 120j accessing RAN 100 via network element 120i, network element 120i is a base station. However, with respect to base station 110a, network element 120i is a terminal device. Both RAN nodes 110 and terminal devices 120 may be called communication devices. For example, network elements 110a and 110b in Figure 1 may be understood as communication devices with base station functionality, and network elements 120a through 120j may be understood as communication devices with terminal device functionality.

[0124] In possible scenarios, a RAN node may be a base station, evolved NodeB (eNodeB), access point (AP), transmission reception point (TRP), next generation NodeB (gNB), next generation base station in a 6th generation (6G) mobile communication system, base station in a future mobile communication system, or access node in a Wi-Fi system. A RAN node may be a macro base station (e.g., 110a in Figure 1), a micro base station or indoor base station (e.g., 110b in Figure 1), a relay node or donor node, or a radio controller in a CRAN scenario. Optionally, a RAN node may be a server, wearable device, vehicle, in-vehicle device, or similar. For example, an access network device in vehicle-to-everything (V2X) technology may be a roadside unit (RSU). All or part of the functionality of the RAN node in the embodiments of this application may be alternatively implemented by using software functionality running on hardware, or by using virtualization functionality instantiated on a platform (e.g., a cloud platform). The RAN node in the embodiments of this application may alternatively be a logical node, logical module, or software capable of performing all or part of the functionality of the RAN node.

[0125] A RAN node may have different representations, such as network devices. In the embodiments of this application, unless otherwise specified, “network devices” will be used to refer to those representations.

[0126] In another possible scenario, multiple RAN nodes cooperate to help terminal devices access wirelessly, with different RAN nodes independently performing some of the base station's functions. For example, a RAN node may be a central unit (CU), a distributed unit (DU), a CU control plane (CP), a CU user plane (UP), or a radio unit (RU). CUs and DUs may be located separately or may be included in the same network element, such as a baseband unit (BBU). An RU may be included in a radio frequency device or 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 have different names, but those skilled in the art will be able to understand their meaning. For example, in an ORAN system, CU may be called O-CU (open CU), DU may be called O-DU, CU-CP may be called O-CU-CP, CU-UP may be called O-CU-UP, and RU may be called O-RU. For ease of explanation, CU, CU-CP, CU-UP, DU, and RU are used as illustrative examples in the embodiments of this application. Any one of CU (or CU-CP or CU-UP), DU, and RU in the embodiments of this application may be implemented using a software module, a hardware module, or a combination of a software module and a hardware module.

[0128] Terminal devices are sometimes also called terminals, user equipment (UE), mobile stations, or mobile terminal devices. Terminal devices can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), the Internet of Things (IoT), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, and smart cities. Terminal devices may be mobile phones, tablet computers, computers with wireless transceiver capabilities, wearable devices, vehicles, unmanned aerial vehicles, helicopters, airplanes, ships, robots, robotic arms, smart home devices, or similar. The device form of a terminal device is not limited to the embodiments of this application.

[0129] The core network 200 may include one or more core network elements. Using a 5G core network as an example, the 5G core network may include an access and mobility management function (AMF) network element responsible for services such as mobility management and access management, a session management function (SMF) network element responsible for session management, a user plane function (UPF) network element responsible for data packet routing and forwarding on the user plane and quality of service (QoS) control, a policy control function (PCF) network element, and similar elements. The core network elements may operate independently or be combined to perform some control functions. For example, the AMF, SMF, and PCF may be combined to function as a core network device.

[0130] In possible implementations, a communication system may further include operation, administration, and maintenance (OAM). OAM may include fault detection, routing, fault positioning, performance monitoring, and similar functions. Nodes within an OAM domain in a communication network may perform OAM. An OAM domain is the set of all nodes in a communication network that support OAM functionality.

[0131] It will be understood that in this application, examples in which network devices and terminal devices are used as performers in interaction diagrams are used for illustrative purposes. However, the performers in the interaction diagrams are not limited in this application. For example, the network device in the method of this application may alternatively be a chip, chip system, or processor used in the network device, or a logical node, logical module, or software capable of implementing all or part of the functions of the network device. The terminal device in the method of this application may alternatively be a chip, chip system, or processor used in the terminal device, or a logical node, logical module, or software capable of implementing all or part of the functions of the terminal device.

[0132] Figure 2 shows a communication method according to an embodiment of the present application. As shown in Figure 2, the method includes the following steps.

[0133] S201: The first network device transmits the first piece of information to the terminal device.

[0134] In response, the terminal device receives first information from the first network device.

[0135] The first piece of information indicates the first MDT setting, which includes the MDT setting corresponding to the terminal device.

[0136] Terminal devices can perform MDT measurements by using the corresponding MDT settings. For example, a terminal can measure information or parameters such as serving cell and intra-frequency / inter-frequency / inter-RAT neighboring cell downlink semaphores, packet data convergence protocol (PDCP) service data unit (SDU) data volume, average UE throughput, and data packet delay by using the corresponding MDT settings.

[0137] For example, in a scenario where a network device needs to perform continuous MDT measurements, for example, in a scenario where a network device needs continuous MDT data for AI model training, the first network device can send the first information to a terminal device by using RRC reconfiguration messages, UE information request messages, or other signaling.

[0138] In this embodiment of the present application, "Transmitting information to... (for example, to a terminal device)" or related descriptions in the attached drawings may be understood to mean that the destination of the information is a terminal device, and may include transmitting information directly or indirectly to a terminal device; also, The phrases "receiving information from... (e.g., a terminal device)," "receiving information from... (a terminal device)," or related descriptions in the attached drawings may be understood to mean that the source of the information is a terminal device, and that this may include receiving information directly or indirectly from a terminal device. The information may undergo necessary processing between the sending and receiving terminals for transmission, such as format changes, but the receiving terminal is able to understand valid information from the sending terminal. Similar expressions in the embodiments of this application can be understood in the same way and are not described in detail here.

[0139] In possible implementations, the first MDT setting may include the MDT activation type, the Immediate Drive Test Minimization (Immediate MDT) setting, and the Logged MDT (logged MDT) setting.

[0140] For example, an immediate MDT configuration may include one or more of the following: serving cell and intra-frequency / inter-frequency / intra-RAT neighbor cell downlink semaphore measurement configuration, PDCP SDU data volume measurement configuration, average UE throughput measurement configuration, data packet delay measurement configuration, and packet loss rate measurement configuration.

[0141] The logging MDT settings may include settings for measuring the received signal strength of the terminal device.

[0142] The MDT type is a method of measuring MDT that can be used by terminal devices. For example, this method may include: using only immediate MDT, using only logged MDT, or using both immediate MDT and trace.

[0143] In possible implementations, the first MDT configuration may further include one or more of the following: MDT area range, Signaling-based MDT public land mobile network List (Signaling-based MDT PLMN List), identifier of the first network device, and identifier of the terminal device.

[0144] The MDT area range indicates the 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] The signaling-based MDT PLMN list shows a list of permitted PLMNs supported by the signaling-based MDT mechanism.

[0146] In possible implementations, the first piece of information may include an index of the first MDT setting.

[0147] For example, the index of the first MDT setting may be a next-generation radio access network trace identifier (NG-RAN Trace ID), and the first network device instructs the network device to retrieve the necessary MDT setting for a terminal device (i.e., the first MDT setting) from among the MDT settings of multiple terminal devices stored in the network device.

[0148] For example, the index of the first MDT setting may alternatively be the identifier of the terminal device. For example, if a network device stores only one MDT setting for each terminal device, the identifier of the terminal device is the first MDT setting It may be reused for indexing.

[0149] For example, the identifier for a terminal device is the cell-radio network temporary identifier (CRNTI). , and This may also be time information, or a System Architecture Evolution Temporary Mobile Station Identifier (STMSI).

[0150] In possible implementations, the first network device may further transmit second information to the terminal device.

[0151] For example, a terminal device receives second information from a first network device.

[0152] The second piece of information shows the first MDT data, which is obtained through measurements based on the first MDT setting.

[0153] For example, in a scenario where historical MDT data needs to be acquired, such as a scenario where a network device needs historical MDT data for AI model training, the first network device can send second information to the terminal device by using an RRCReconfiguration message, a UE information request message, or other signaling.

[0154] It will be understood that training AI models using historical MDT data (data such as historical throughput and trajectory data) can help improve the inference accuracy of AI models regarding future throughput and trajectory information of terminal devices.

[0155] In possible implementations, the first MDT data includes MDT data acquired by the terminal device through measurements based on the first MDT configuration. For example, the terminal device acquires one or more of the following MDT data through measurements based on the first MDT configuration: downlink semaphore measurement results for serving cells and intra-frequency / inter-frequency / inter-RAT neighbor cells, PDCP SDU data volume, average UE throughput, and data packet delay. The MDT data may be considered as the MDT measurement results.

[0156] In another possible implementation, the first MDT data includes MDT data acquired by the network device through measurements based on the first MDT configuration.

[0157] In yet another possible implementation, the first MDT data includes MDT data acquired by terminal devices and network devices through measurements based on the first MDT configuration.

[0158] In possible implementations, the second piece of information includes an index of the first MDT data.

[0159] The index of the first MDT data is intended to instruct the first network device to retrieve the required MDT data (i.e., the first MDT data) from among the MDT data of multiple terminal devices that are stored in the first network device.

[0160] For example, the index of the first MDT data may be the NG-RAN trace ID.

[0161] For example, the index of the first MDT data may alternatively be the identifier of the terminal device. For example, if a network device stores only one MDT data for each terminal device, the identifier of the terminal device is the first MDT data index It may be reused for this purpose.

[0162] In possible implementations, the first network device may, alternatively, store the first MDT setting when disconnected from the terminal device until the storage of the first MDT setting times out. The storage of the first MDT setting times out means that the storage time for the first MDT setting is longer than the retention duration for the first MDT setting. The retention duration for the first MDT setting may be pre-configured or specified by third information, which indicates that the first MDT setting is to be stored.

[0163] For example, the first network device can store the first MDT settings when disconnected from the terminal device until the storage of the first MDT settings times out. Therefore, in a scenario where, for example, the network device requires the terminal device to continuously perform MDT measurements, the stored first MDT settings can be used by the terminal device to perform MDT measurements and acquire continuous MDT data.

[0164] In another example, the first network device may remember the first MDT setting when it is disconnected from the terminal device based on the instructions of the third piece of information, until the memory of the first MDT setting times out.

[0165] In possible implementations, the first network device may also receive third information.

[0166] For example, the first network device may receive third information from the OAM.

[0167] In another example, the first network device can receive an MDT configuration from the core network device, which carries the third information, and obtain the third information.

[0168] In another example, the first network device can receive the MDT settings transmitted by the OAM via the core network device, which carry the third information, and obtain the third information.

[0169] In possible implementations, the third piece of information may include the identifier of the terminal device and the index of the first MDT setting.

[0170] For example, the identifier of a terminal device may be included in the identifier list. The identifier list may indicate one or more terminal devices that hold MDT settings (i.e., it indicates which terminal devices hold corresponding MDT settings).

[0171] In possible implementations, the third piece of information may further include the retention period for the first MDT setting and / or the index range for the first MDT setting.

[0172] The index range of the first MDT setting indicates the transmission range of the first MDT setting (i.e., the MDT setting that may be sent to the terminal device by the network device).

[0173] For example, the index range of the first MDT setting may be a Next-Generation Wireless Access Network Trace Identifier List (NG-RAN Trace ID List). Each NG-RAN Trace ID in the NG-RAN Trace ID List may correspond to a single MDT setting.

[0174] It will be understood that after disconnection from a terminal device, the first network device releases some settings associated with the terminal device (e.g., the first MDT settings). To avoid cases where the first MDT settings are released because they are not remembered, the OAM can instruct the first network device to remember the first MDT settings by using third information. In this way, an MDT interruption caused by the first network device failing to send the first MDT settings to the second network device due to the release of the first MDT settings is avoided.

[0175] In possible implementations, the first network device may, alternatively, store the first MDT data when it is separated from the terminal device until the storage of the first MDT data times out.

[0176] For example, the first network device may store the first MDT data when it separates from the terminal device until the storage of the first MDT data times out. The storage of the first MDT data times out means that the time the first MDT data is stored is longer than the period for which the first MDT data should be retained. The retention period for the first MDT data may be predetermined or specified by a fourth piece of information, which indicates that the first MDT data is to be stored.

[0177] In another example, the first network device may store the first MDT data when it separates from the terminal device based on the instructions of the fourth piece of information, until the storage of the first MDT data times out. Thus, the stored first MDT data may be transmitted to another network device and used, for example, in a scenario where the network device trains an AI model based on historical MDT data (in chronological order).

[0178] In possible implementations, the first network device is capable of receiving the fourth piece of information.

[0179] For example, the first network device can receive the MDT settings from the OAM, which are carrying the fourth information, and obtain the fourth information.

[0180] For example, the first network device can receive the MDT settings from the core network device, which are carrying the fourth information, and obtain the fourth information.

[0181] For example, the first network device can receive the fourth piece of information transmitted by OAM via the core network device.

[0182] In possible implementations, the fourth piece of information may include the identifier of the terminal device and an index of the first MDT data.

[0183] In possible implementations, the fourth piece of information may further include the retention period for the first MDT data and / or the index range for the first MDT data.

[0184] The index range of the first MDT data indicates the transmission range of the first MDT data (i.e., the MDT data that may be sent from the network device to the terminal device).

[0185] For example, the index range of the first MDT setting may be a Next-Generation Wireless Access Network Trace Identifier List (NG-RAN Trace ID List). Each NG-RAN Trace ID in the NG-RAN Trace ID List may correspond to a single MDT setting.

[0186] To avoid the case where the first MDT data is released because it is not stored, OAM can use fourth information to instruct the first network device to store the first MDT data. In this way, the first network device is prevented from failing to send the first MDT data to the second network device due to the release of the first MDT data, and as a result, the second network device can train the AI ​​model using the first MDT data.

[0187] In possible implementations, the terminal device may, alternatively, store the first information before separating from the first network device.

[0188] For example, in a connected state, the terminal device will maintain a connection to the first network device. Before the terminal device is disconnected from the first network device, that is, before the terminal device switches from a connected state to an idle state, the terminal device can store the first information until the first information is transmitted to the second network device.

[0189] S202: The terminal device transmits the first piece of information to the second network device.

[0190] In response, the second network device receives the first information from the terminal device.

[0191] For example, a terminal device can transmit first information to a second network device by using a measurement report (MR), a UE information response message, or other signaling.

[0192] In possible implementations, a terminal device can transmit first information to a second network device after establishing a connection to the second network device.

[0193] For example, if the terminal device switches from a connected state to an idle state and moves away from the first network device, it can switch back from the idle state to a connected state, establish an RRC connection to the second network device, and then send the first information to the second network device using a measurement report, UE information response message, or other signaling.

[0194] In possible implementations, the terminal device can further transmit second information to a second network device.

[0195] For example, a terminal device can use measurement reports, UE information response messages, or other signaling to determine the 2 It is possible to transmit this information to a second network device.

[0196] In possible implementations, a terminal device can transmit second information to a second network device after establishing a connection to that second network device.

[0197] For example, if the terminal device switches from a connected state to an idle state and moves away from the first network device, it can switch back from the idle state to a connected state, establish an RRC connection to the second network device, and then send the second information to the second network device using a measurement report, UE information response message, or other signaling.

[0198] In possible implementations, 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 do not need to be performed.

[0200] S203: The second network device transmits the first information to the first network device.

[0201] In response, the first network device receives the first information from the second network device.

[0202] For example, in a scenario where a terminal device is required to continuously perform MDT measurements, a second network device can send the first information to the first network device by using a retrieve UE context request message, a handover request acknowledgement message, a UE context release message, or other signaling.

[0203] In possible implementations, the indices of multiple MDT settings can be stored in an index list within a second network device. The second network device can search the index list to find the index corresponding to the terminal device, determine the first information, and then send the first information to the first network device to indicate that the MDT setting of the terminal device, i.e., the first MDT setting, needs to be retrieved.

[0204] In possible implementations, the first network device can further transmit the second information to the second network device.

[0205] In response, the first network device receives the second information from the second network device.

[0206] For example, in a scenario where it is necessary to acquire historical MDT data, a second network device can send the second information to the first network device by using a UE context acquisition request message, a handover request acknowledgment message, a UE context release message, or other signaling.

[0207] In possible implementations, the indices of multiple MDT data can be stored in an index list within a second network device. The second network device can search the index list to determine the index corresponding to the terminal device, determine the second information, and then send the second information to the first network device to indicate that the MDT data corresponding to the terminal device, i.e., the first MDT data, needs to be retrieved.

[0208] S204: The first network device sends the first MDT configuration to the second network device.

[0209] In response, the second network device receives the first MDT configuration from the first network device.

[0210] For example, the first network device can send the first MDT configuration to the second network device by using a UE context acquisition response message or other signaling.

[0211] In possible implementations, the first network device can further determine the first MDT setting from one or more stored MDT settings based on the first information.

[0212] In possible implementations, the first network device may further send a first response message to the second network device. The first response message indicates the reason why it could not send the first MDT configuration.

[0213] For example, if the first MDT setting cannot be sent, the first network device may send a first response message to the second network device indicating that the first MDT setting cannot be sent for any of the following reasons: the first MDT setting has been released, the memory of the first MDT setting has timed out, the first MDT setting cannot be found, or something similar.

[0214] In possible implementations, the first network device can further transmit the first MDT data to a second network device.

[0215] In response, the second network device receives the first MDT data from the first network device.

[0216] For example, the first network device can send the first MDT data to the second network device by using a UE context acquisition response message or other signaling.

[0217] In possible implementations, the first network device can further determine the first MDT data from one or more stored MDT data based on the second information.

[0218] In possible implementations, the first network device may further send a second response message to the second network device. The second response message indicates the reason why the first MDT data could not be sent. For example, if the first MDT data cannot be sent, the first network device may send a second response message to the second network device indicating the following reasons why the first MDT data could not be sent: namely, the first MDT data has been released, the storage of the first MDT data has timed out, the first MDT data cannot be found, or similar.

[0219] S205: The second network device determines the second MDT setting based on the first MDT setting.

[0220] For example, a second network device may obtain a second MDT configuration by modifying the format of the first MDT configuration or by adding or deleting content from the first MDT configuration (for example, by deleting information such as the MDT activation type and signaling-based MDT PLMN list).

[0221] In possible implementations, the second MDT setting may include an immediate MDT setting.

[0222] It should be noted that the immediate MDT setting in the second MDT setting may be obtained based on the immediate MDT setting in the first MDT setting. For example, it is possible to obtain the immediate MDT setting in the second MDT setting by removing some of the measurement settings (such as the average UE throughput measurement setting or the packet loss rate measurement setting) from the immediate MDT setting in the first MDT setting.

[0223] S206: The second network device sends the second MDT configuration to the terminal device.

[0224] In response, the terminal device receives the second MDT settings from the second network device.

[0225] S207: The terminal device performs an MDT measurement based on the second MDT setting.

[0226] For example, a terminal device can perform MDT measurements based on the immediate MDT setting in the second MDT setting and periodically report the MDT results to the second network device.

[0227] The measurement results may include one or more of the following: downlink semaphore measurements for serving cells and intra-frequency / inter-frequency / inter-RAT neighbor cells, packet data convergence protocol (PDCP) service data unit (SDU) data volume, average UE throughput, or data packet delay.

[0228] In the method provided in this embodiment of the present application, after a terminal device transitions from an idle state to a connected state, the terminal device can transmit first information indicating the MDT settings corresponding to the terminal device to a newly connected second network device, and as a result, the second network device uses the first information to obtain the MDT settings via the first network device previously connected to the terminal device and delivers the MDT settings to the terminal device. This avoids the case where the terminal device stops MDT measurement due to the newly connected network device not transmitting the second MDT settings to the terminal device, thereby maintaining MDT continuity and obtaining continuous MDT data to satisfy the requirement for obtaining continuous MDT data in some scenarios. For example, the network device can obtain continuous MDT data for AI model training to improve the accuracy of AI model training and improve the effectiveness of applying the AI ​​model.

[0229]

[0230] Based on the embodiment shown in Figure 2, and with reference to the signaling procedure shown in Figure 3, the communication method provided in this application will be described below. The embodiments provided in this application may be referenced, cited, or combined with each other, and Figure 2 It will be understood that the details described in the embodiments will not be explained again. As shown in Figure 3, the method includes the following steps.

[0230] S301:OAM transmits third information to the core network device.

[0231] For example, in a scenario where a terminal device requires continuous MDT measurements, or in a scenario where a network device requires continuous MDT data for AI model training, the OAM can transmit third information to the core network device, indicating that the third information stores the aforementioned first MDT settings. For a detailed explanation of the third information, please refer to the content of the third information in the embodiment shown in Figure 2.

[0232] In possible implementations, S301 can also be replaced with:OAM sending third information to the first network device.

[0233] In possible implementations, the OAM can further transmit a fourth piece of information to the core network device, indicating that the fourth piece of information stores the aforementioned first MDT data. For a detailed description of the fourth piece of information, please refer to the content of the fourth piece of information in the embodiment shown in Figure 2.

[0234] For example, in a scenario where it is necessary to acquire historical MDT data, for example, in a scenario where a network device requires historical MDT data for AI model training, the OAM can transmit the fourth piece of information to the core network device or the first network device.

[0235] In possible implementations, the OAM may alternatively transmit the fourth piece of information to the first network device.

[0236] S302: The core network device transmits third information to the first network device.

[0237] S303: The first network device remembers the first MDT settings based on the third information.

[0238] For a detailed explanation of the first MDT setting, please refer to the content of the first MDT setting in the embodiment shown in Figure 2.

[0239] In possible implementations, the first network device can further store the first MDT data based on the fourth information.

[0240] For a detailed explanation of the first MDT data, please refer to the content of the first MDT data in the embodiment shown in Figure 2.

[0241] S304: The first network device transmits the first information to the terminal device.

[0242] For a detailed explanation of the first piece of information, please refer to the content of the first piece of information in the embodiment shown in Figure 2.

[0243] S305: The terminal device transmits the first piece of information to the second network device.

[0244] S306: The second network device transmits the first information to the first network device.

[0245] S307: The first network device sends the first MDT configuration to the second network device.

[0246] S309: The second network device sends the second MDT configuration to the terminal device.

[0247] S310: The terminal device performs an MDT measurement based on the second MDT setting.

[0248] For example, a terminal device can perform MDT measurements based on the immediate MDT setting in the second MDT setting and periodically report the MDT results to the second network device.

[0249] It should be noted that for the specific implementation of steps S304 through S310, please refer to the explanations in steps S201 through S207. Further details will not be explained here.

[0250] Figure 4 shows yet another communication method according to an embodiment of the present application. Unlike the embodiment shown in Figure 2, in this solution, the first network device does not transmit the aforementioned first information to the terminal, but directly transmits the aforementioned first MDT settings. As shown in Figure 4, the method includes the following steps:

[0251] S401: The first network device sends the first MDT configuration to the terminal device.

[0252] In response, 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 the contents of the first MDT configuration in the embodiment shown in Figure 2.

[0253] For example, in a scenario where a terminal device requires continuous MDT measurements, or in a scenario where a network device requires continuous MDT data for AI model training, the first network device can send the first MDT settings to the terminal device.

[0254] In possible implementations, the first network device may further transmit the first MDT data to the terminal device. For a detailed description of the first MDT data, please refer to the content of the first MDT data in the embodiment shown in Figure 2.

[0255] In response, the terminal device receives the first MDT data from the first network device.

[0256] For example, in a scenario where it is necessary to acquire historical MDT data, for example, in a scenario where a network device requires historical MDT data for AI model training, the first network device can transmit the first MDT data to the terminal device.

[0257] It should be noted that the first MDT setting may be obtained by the first network device from the core network device or OAM.

[0258] For example, a first network device can receive a first MDT configuration sent by OAM via a core network device.

[0259] In possible implementations, the first network device can further transmit a fifth piece of information to a terminal device.

[0260] The fifth piece of information indicates that the first MDT setting is stored.

[0261] For example, in a scenario where a terminal device is required to perform MDT measurements continuously, the first network device may transmit fifth information to the terminal device.

[0262] For example, the fifth piece of information may include the identifier of the terminal device and the retrieval range of the first MDT setting.

[0263] The search scope for the first MDT setting indicates the transmission scope for the first MDT setting (i.e., the network devices to which the first MDT setting may be transmitted).

[0264] For example, the fifth piece of information may further include the retention duration and / or the index range of the first MDT setting.

[0265] For example, the fifth piece of information may further include an MDT setting retention indicator.

[0266] For example, the MDT setting retention indicator may be indicated using bits. For instance, if the value of the bit corresponding to the MDT setting retention indicator is 1, it indicates that the first MDT setting is stored, and if the value of the bit is 0, it indicates that the first MDT setting is not stored.

[0267] In another example, the MDT setting retention indicator may be implicitly indicated by using a first MDT setting. For instance, if a terminal device receives a first MDT setting, the first MDT setting is stored by default.

[0268] In possible implementations, the fifth piece of information may be generated by the first network device.

[0269] For example, the first network device may generate fifth information when a terminal device needs to perform MDT measurements continuously.

[0270] In another possible implementation, the fifth piece of information may, alternatively, be obtained by the first network device from another device.

[0271] For example, the first network device may receive the fifth piece of information from the core network device or OAM.

[0272] For example, the first network device may receive a first MDT configuration from a core network device or OAM that carries the fifth information, and obtain the fifth information.

[0273] In another example, the first network device may receive the first MDT configuration transmitted by the OAM via the core network device, which carries the fifth information, and obtain the fifth information.

[0274] It will be understood that a terminal device may release some information after it has separated from the first network device. To avoid the case where the first MDT setting is released because it is not supposed to be remembered, the fifth piece of information can instruct the terminal device to remember the first MDT setting. In this way, an interruption in MDT caused by the terminal device failing to send the first MDT setting to the second network device due to the release of the first MDT setting after the terminal device has separated from the first network device is avoided.

[0275] In possible implementations, the first network device can further transmit sixth information to the terminal device.

[0276] The sixth piece of information indicates that it stores the first MDT data.

[0277] For example, the sixth piece of information may include the identifier of the terminal device and the search range of the first MDT data.

[0278] The search range for the first MDT data indicates the transmission range for the first MDT data (i.e., the network devices to which the first MDT data may be transmitted).

[0279] For example, the sixth information may further include a retention period of the first MDT data and / or an index range of the first MDT data.

[0280] For example, the sixth information may further include an MDT data retention indicator.

[0281] For example, the MDT data retention indicator may be indicated by using a bit. For example, when the value of the bit corresponding to the MDT data retention indicator is 1, it indicates that the first MDT data is to be stored; when the value of the bit is 0, it indicates that the first MDT data is not to be stored.

[0282] In another example, the MDT data retention indicator may alternatively be implicitly indicated by using the first MDT data. For example, when a terminal device receives the first MDT data, the first MDT data is stored by default.

[0283] In a possible implementation, the sixth information may be generated by the first network device.

[0284] For example, the first network device may generate the sixth information when historical MDT data needs to be acquired.

[0285] In another possible implementation, the sixth information may alternatively be acquired by the first network device from another device.

[0286] For example, the first network device may alternatively receive the sixth information from a core network device or OAM.

[0287] For example, the first network device may receive a first MDT configuration carrying the sixth information from a core network device or OAM, and acquire the sixth information.

[0288] In another example, a first MDT configuration transmitted by OAM, which carries the sixth information, is received via a core network device, and the sixth information is retrieved.

[0289] In possible implementations, the terminal device may, alternatively, store the first MDT configuration before separating from the first network device.

[0290] For example, when a terminal device receives the fifth piece of information and is connected, before the terminal device disconnects from the first network device (i.e., before the terminal device switches from a connected state to an idle state), the terminal device may store the first MDT setting until the first MDT setting is sent to the second network device or until the storage of the first MDT setting times out. The storage of the first MDT setting times out means that the time the first MDT setting is stored is longer than the retention period of the first MDT setting. The retention period of the first MDT setting may be predetermined or may be indicated by the fifth piece of information.

[0291] In possible implementations, the terminal device may, alternatively, store the first MDT data before separating from the first network device.

[0292] For example, when a terminal device receives the sixth piece of information and is connected, before the terminal device disconnects from the first network device (i.e., before the terminal device switches from a connected state to an idle state), the terminal device may store the first MDT data until the first MDT data is sent to the second network device or until the storage of the first MDT data times out. The storage of the first MDT data times out means that the time the first MDT data is stored is longer than the retention period of the first MDT data. The retention period of the first MDT data may be predetermined or may be indicated by the sixth piece of information.

[0293] It will be understood that, in order to avoid the case in which the first MDT data is released due to the first MDT data not being stored, the sixth piece of information allows the terminal device to be instructed to store the first MDT data. In this way, after separation from the first network device, the failure to transmit the first MDT data to the second network device due to the release of the first MDT data is avoided, and as a result, the second network· The device can train an AI model by using the first MDT data.

[0294] S402: The terminal device sends the first MDT settings to the second network device.

[0295] In response, the second network device receives the first MDT settings from the terminal device.

[0296] In possible implementations, a terminal device can send the first MDT configuration to the second network device after establishing a connection to the second network device.

[0297] For example, when switching from a connected state to an idle state and separating from the first network device, the terminal device switches back from the idle state to a connected state, establishes an RRC connection to the second network device, and then sends the first MDT settings to the second network device by using a measurement report, UE information response message, or other signaling.

[0298] In another example, if the first MDT setting is still held within the terminal device and the second network device is within the search range of the first MDT setting, the terminal device can send the first MDT setting to the second network device.

[0299] In another example, if the first MDT setting is still held within the terminal device, but the second network device is not within the search range of the first MDT setting, the terminal device may not send the first MDT setting to the second network device.

[0300] In possible implementations, the terminal device may also transmit the first MDT data to a second network device.

[0301] In response, the second network device receives the first MDT data from the terminal device.

[0302] For example, if the terminal device switches from a connected state to an idle state and disconnects from the first network device, it may switch back from the idle state to a connected state, establish an RRC connection to the second network device, and then send the first MDT data to the second network device using a measurement report, UE information response message, or other signaling.

[0303] In another example, if the first MDT data is still stored in the terminal device and the second network device is within the search range of the first MDT data, the terminal device can send the first MDT data to the second network device.

[0304] In another example, if the first MDT data is still stored in the terminal device but the second network device is not within the search 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, the terminal device may alternatively send a fourth response message to the second network device.

[0306] The fourth response message indicates the reason why the first MDT data cannot be sent.

[0307] For example, when the first MDT data cannot be sent to the second network device, the fourth response message may be sent to the second network device to indicate any of the following reasons for being unable to send the first MDT data: the first MDT data has been released, storage of the first MDT data has timed out, the second network device is not within the search range of the first MDT data, or the like.

[0308] In a possible implementation, the second network device can send a fifth response message to the terminal device.

[0309] The fifth response message indicates the reason for rejecting reception of the first MDT configuration.

[0310] For example, the second network device may send a fifth response message to the terminal device if it lacks measurement resources, computing resources, or does not need to maintain continuous MDT.

[0311] In possible implementations, S402 may also be replaced by: the terminal device sending a third response message to the second network device; the third response message indicating why it could not send the first MDT configuration.

[0312] For example, if the first MDT setting cannot be sent to the second network device, the terminal may send a third response message to the second network device to indicate that the first MDT setting cannot be sent for one of the following reasons: the first MDT setting is released, the memory of the first MDT setting has timed out, the second network device is not within the search range for the first MDT setting, or something similar.

[0313] In possible implementations, the second network device and the first network device may be the same network device.

[0314] S403: The second network device determines the second MDT setting based on the first MDT setting.

[0315] For example, the format of the first MDT setting may be modified, or the contents of the first MDT setting may be added or deleted to obtain the second MDT setting.

[0316] S404: The second network device sends the second MDT configuration to the terminal device.

[0317] In response, the terminal device receives the second MDT settings from the second network device.

[0318] S405: The terminal device performs an MDT measurement based on the second MDT setting.

[0319] For example, a terminal device may perform an MDT measurement based on the immediate MDT setting in the second MDT setting and periodically report the MDT results to the second network device.

[0320] It should be noted that the immediate MDT setting in the second MDT setting may be obtained based on the immediate MDT setting in the first MDT setting. For example, the immediate MDT setting in the second MDT setting may be obtained by removing some of the measurement settings (such as the average UE throughput measurement setting or the packet loss rate measurement setting) from the immediate MDT setting in the first MDT setting.

[0321] For a detailed explanation of steps S403 to S405, please refer to the explanation of steps S205 to S207 in the embodiment shown in Figure 2.

[0322] In the method provided in this embodiment of the present application, after a terminal device transitions from an idle state to a connected state, the terminal device can transmit a first MDT configuration, including the MDT configuration corresponding to the terminal device, to a newly connected second network device, thereby enabling the second network device to deliver the MDT configuration to the terminal device using the first MDT configuration. This avoids the case where the terminal device stops MDT measurement due to the newly connected network device failing to transmit the second MDT configuration to the terminal device, thereby maintaining MDT continuity and acquiring continuous MDT data to satisfy the requirement for acquiring continuous MDT data in some scenarios. For example, the network device acquires continuous MDT data for AI model training to improve the accuracy of AI model training and enhance the effectiveness of applying the AI ​​model.

[0323] Based on the embodiment shown in Figure 4, and with reference to the signaling procedure shown in Figure 5, the communication method provided in this application will be described below. The contents described in the embodiment of Figure 4 will not be described again. As shown in Figure 5, the method includes the following steps.

[0324] S501:OAM sends the first MDT configuration to the core network device.

[0325] For a detailed explanation of the first MDT setting, please refer to the content of the first MDT setting in the embodiment shown in Figure 2.

[0326] In possible implementations, S501 is also replaced by: OAM sending the first MDT configuration to the first network device.

[0327] In possible implementations, the OAM can further transmit a fifth piece of information to the core network device, indicating that it stores the first MDT settings. For a detailed description of the fifth piece of information, please refer to the content of the fifth piece of information in the embodiment shown in Figure 4.

[0328] In possible implementations, the OAM may alternatively transmit the fifth piece of information to the first network device.

[0329] In possible implementations, the OAM can further transmit a sixth piece of information to the core network device, indicating that the sixth piece of information stores the first MDT data. For a detailed description of the sixth piece of information, please refer to the content of the sixth piece of information in the embodiment shown in Figure 4.

[0330] In possible implementations, the OAM may alternatively transmit the sixth piece of information to the first network device.

[0331] S502: The core network device sends the first MDT configuration to the first network device.

[0332] In possible implementations, the core network device can also transmit a fifth piece of information to the first network device.

[0333] The fifth piece of information may be generated by the core network device or may be received from the OAM.

[0334] For example, a core network device may generate a fifth piece of information if MDT continuity needs to be maintained.

[0335] In possible implementations, the core network device can also transmit a sixth piece of information to the first network device.

[0336] The sixth piece of information may be generated by the core network device or may be received from the OAM.

[0337] For example, the first network device can generate the sixth piece of information if it requires the acquisition of historical MDT data.

[0338] S503: The first network device sends the first MDT configuration to the terminal device.

[0339] It should be noted that for the specific implementation of S503, please refer to the explanation in S401. Further details will not be explained here.

[0340] S504: The terminal device remembers the first MDT setting.

[0341] In possible implementations, the terminal device may store the first MDT settings before separating from the first network device.

[0342] For example, if a core network device transmits fifth information to a first network device, and the first network device then transmits fifth information to a terminal device, the terminal device may maintain its connection to the first network device while it has received fifth information and is connected. Before the terminal device disconnects from the first network device (i.e., before the terminal device switches from a connected state to an idle state), the terminal device may store the first MDT setting until the first MDT setting is transmitted to the second network device or until the storage of the first MDT setting times out.

[0343] In possible implementations, the terminal device may store the first MDT data before separating from the first network device.

[0344] For example, if a core network device transmits sixth information to a first network device, and the first network device then transmits sixth information to a terminal device, the terminal device may maintain its connection to the first network device while it has received sixth information and is connected. Before the terminal device disconnects from the first network device (i.e., before the terminal device switches from a connected state to an idle state), the terminal device may store the first MDT data until the first MDT data is transmitted to the second network device or until the storage of the first MDT data times out.

[0345] For a detailed explanation of the first MDT data, please refer to the content of the first MDT data in the embodiment shown in Figure 2.

[0346] S505: The terminal device sends the first MDT settings to the second network device.

[0347] S506: The second network device determines the second MDT setting based on the first MDT setting.

[0348] S507: The second network device sends the second MDT configuration to the terminal device.

[0349] S508: The terminal device performs an MDT measurement based on the second MDT setting.

[0350] Please note that for the specific implementation of steps S505 through S508, please refer to the explanation of steps S402 through S405. Further details will not be explained here.

[0351] Figure 6 shows yet another communication method according to an embodiment of the present application. This embodiment may be mutually referenced with the embodiments provided in Figures 2 and 4, and the concepts described in the embodiments provided in Figures 2 and 4 are not described in this embodiment. Unlike the embodiment shown in Figure 2, in this solution, the MDT settings transmitted to the terminal by the first network device include a Trace Reference (TR) for an immediate MDT setting and a TR for a logged MDT setting, the values ​​of the two TRs being the same. The method includes the following steps:

[0352] S601:OAM sends the third MDT configuration to the first network device.

[0353] In response, the first network device receives the third MDT configuration from the OAM.

[0354] The third MDT setting is a management-based MDT setting, and the MDT activation type is "immediate MDT and logged MDT".

[0355] It should be noted that the MDT activation type "Immediate MDT and Logged MDT" is a newly added MDT activation type in this embodiment of the present application. The MDT activation type "Immediate MDT and Logged MDT" indicates that the terminal device performs immediate MDT measurement and logged MDT measurement. For example, based on an MDT setting in which the MDT activation type is "Immediate MDT and Logged MDT", the terminal device can perform immediate MDT measurement in a connected state and logged MDT measurement in an idle state.

[0356] The third MDT setting includes the MDT activation type, immediate MDT setting, logging MDT setting, and TR information. The TR information indicates the first TR and the second TR, where the first TR is the TR for the immediate MDT setting and the second TR is the TR for the logging MDT setting. The first TR is the same as the second TR.

[0357] In possible implementations, the first TR and the second TR may be indicated by using the same TR.

[0358] In another possible implementation, the first TR and the second TR may be indicated by using two identical TRs.

[0359] Immediate MDT data and logged MDT data may be associated using TR. For example, if the TR for the immediate MDT setting and the logged MDT setting are the same, it can be determined that the immediate MDT data obtained through measurements using the immediate MDT setting and the logged MDT data obtained through measurements using the logged MDT setting were obtained through measurements using the same MDT session.

[0360] In possible implementations, the third MDT setting may further include the MDT area range.

[0361] S602: The first network device determines the fourth MDT setting based on the third MDT setting.

[0362] The fourth MDT setting includes the MDT activation type, immediate MDT setting, logging MDT setting, and TR information.

[0363] For example, the first network device can obtain the fourth MDT configuration by modifying the format of the third MDT configuration or by adding or deleting content from the third MDT configuration (for example, by deleting the identifier of the first network device).

[0364] In possible implementations, the fourth MDT setting may further include an identifier for the terminal device.

[0365] S603: The first network device sends the fourth MDT configuration to the terminal device.

[0366] In response, the terminal device receives the fourth MDT setting from the first network device.

[0367] In possible implementations, the first network device can further transmit a Trace Recording Session Reference (TRSR) identifier to the terminal device.

[0368] The target TRSR identifier is the TRSR identifier assigned to the terminal device by the first network device. The terminal device corresponding to the MDT data can be identified by using the TRSR identifier.

[0369] S604: The first network device sends the third MDT configuration and target TRSR identifier to the core network device.

[0370] In response, the core network device receives the third MDT configuration and target TRSR identifier from the first network device.

[0371] In possible implementations, the core network device can store a third MDT configuration and target TRSR identifier within the UE context.

[0372] In possible implementations, the core network device can transmit a third MDT configuration and target TRSR to a second network device. For example, if the core network device receives a third MDT configuration and detects that a terminal device has established a connection to the second network device, the core network device can proactively transmit the third MDT configuration and target TRSR identifier to the second network device.

[0373] S605: The terminal device transmits the first instruction information to the second network device.

[0374] In response, the second network device receives the first instruction information from the terminal device.

[0375] The first instruction information indicates the third MDT setting and target TRSR identifier stored in the core network device. The first instruction information includes the target TRSR identifier and / or the identifier of the terminal device.

[0376] For example, if the terminal device switches from a connected state to an idle state and is disconnected from the first network device, it can switch back from the idle state to a connected state, establish an RRC connection to the second network device, and then send first instruction information carrying the target TRSR identifier and the terminal device identifier to the second network device.

[0377] In possible implementations, the first instruction information may further include TR information and / or MDT activation type.

[0378] In possible implementations, the identifier of the terminal device may be obtained by the terminal device based on the fourth MDT setting, or by using other signaling.

[0379] In possible implementations, the terminal device may also transmit a second instruction to a second network device. This second instruction indicates that a logged MDT measurement report is stored in the terminal device.

[0380] In possible implementations, the first instruction information and the second instruction information may be the same information.

[0381] In possible implementations, the terminal device can also send logged MDT measurement reports to a second network device.

[0382] For example, upon receiving the first response information, the terminal device may send a logging MDT measurement report to the second network device. The first response information is used to request the logging MDT measurement report.

[0383] In possible implementations, after receiving a logged MDT measurement report, a second network device can further send the logged MDT measurement report to a trace collection entity (TCE).

[0384] S606: The second network device transmits the first instruction information to the core network device.

[0385] In response, the core network device receives the first instruction information from the second network device.

[0386] In possible implementations, the second network device can further transmit TR information and / or MDT activation type to the core network device.

[0387] S607: The core network device transmits the third MDT configuration and target TRSR identifier to the second network device.

[0388] In response, the second network device receives the third MDT configuration and target TRSR identifier from the core network device.

[0389] For example, a core network device can use TR information and a target TRSR identifier to retrieve the UE context, determine a third MDT configuration, and then send the third MDT configuration to a second network device.

[0390] S608: The second network device determines the fifth MDT setting based on the third MDT setting.

[0391] For example, a second network device can obtain a fifth MDT configuration by modifying the format of the third MDT configuration or by adding or deleting content from the third MDT configuration.

[0392] It should be noted that in the process in which the second network device determines the fifth MDT setting based on the third MDT setting, a new TRSR identifier does not need to be assigned to the terminal device, and the target TRSR identifier may be reused.

[0393] In possible implementations, a second network device can correlate the terminal device's immediate MDT measurement report with the logged MDT measurement report by using the target TRSR identifier and TR information.

[0394] In possible implementations, the fifth MDT setting may be the same as the fourth MDT setting.

[0395] S609: The second network device sends the fifth MDT configuration to the terminal device.

[0396] In response, the terminal device receives the 5th MDT setting from the second network device.

[0397] S610: The terminal device performs an MDT measurement based on the fifth MDT setting.

[0398] The method provided in this embodiment of the present application introduces a new MDT activation type, "Immediate MDT and Logged MDT," which means that the OAM can associate immediate MDT data and logged MDT data for the same terminal device by transmitting immediate MDT settings and logged MDT settings having the same TR, and by using the TR and target TRSR identifier. This avoids the failure to acquire continuous MDT data for the same terminal device due to the inability to associate immediate MDT data and logged MDT data for the same terminal device because of differences between the TRs of the immediate MDT settings and the logged MDT settings for the same terminal device. Thus, the requirement for acquiring continuous MDT data is met in some scenarios. For example, a network device acquires continuous MDT data for AI model training to improve the accuracy of AI model training and improve the effectiveness of applying the AI ​​model.

[0399] Furthermore, after the terminal device transitions from an idle state to a connected state, it can transmit first instruction information to a newly connected second network device, carrying the target TRSR identifier and / or the terminal identifier. As a result, the second network device uses the first instruction information to obtain the MDT settings from the core network device and distribute the MDT settings to the terminal device. This avoids the scenario where the terminal device stops MDT measurement because the newly connected network device does not transmit the fifth MDT settings to the terminal device, thereby maintaining MDT continuity and obtaining continuous MDT data to meet the requirement for obtaining continuous MDT data in some scenarios.

[0400] The following describes a communication device configured to perform the aforementioned communication method, with reference to Figures 7 through 15.

[0401] It will be understood that, in order to implement the functions of the communication method described above, the communication device includes corresponding hardware and / or software modules for performing the functions. With respect to the algorithmic steps in the examples described in the embodiments disclosed in this specification, the embodiments of this application may be implemented in hardware or in combination of hardware and computer software. Whether the functions are performed by hardware or by hardware driven by computer software depends on the specific application and design constraints of the technical solution. A person skilled in the art will see that, in relation to the embodiments, different methods may be used to implement the described functions for each specific application, but it should not be assumed that such implementations go beyond the scope of the embodiments of this application.

[0402] In the embodiments of this application, the communication device may be divided into multiple functional modules based on the method examples described above. For example, each functional module may be obtained through division based on its corresponding function, or two or more functions may be integrated into a single processing module. The integrated module may be implemented in hardware form. It should be noted that the module division in the embodiments is merely an example and a logical functional division. In actual implementations, other division methods may exist.

[0403] Figure 7 shows a possible configuration of the communication device in the above-described embodiment, where each functional module is obtained through division based on its corresponding function. The device may be a terminal device, or a module used in a terminal device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of performing all or part of the functions of a terminal device. As shown in Figure 7, the communication device 700 may include a receiving unit 701, a transmitting unit 702, and a processing unit 703.

[0404] The receiving unit 701 is configured to receive first information from a first network device, the first information indicating a first MDT setting, the first MDT setting including an MDT setting corresponding to a terminal device.

[0405] The transmitting unit 702 is configured to transmit the first information to a second network device.

[0406] The receiving unit 701 is further configured to receive a second MDT setting from a second network device, the second MDT setting being obtained based on the first MDT setting.

[0407] The processing unit 703 is configured to perform MDT measurements based on a second MDT setting.

[0408] In possible implementations, the processing unit 703 is further configured to store the first information before being disconnected from the first network device.

[0409] In possible implementations, the transmitting unit 702 is specifically configured to transmit the first information to the second network device after establishing a connection to the second network device.

[0410] In possible implementations, the second MDT setting may include an immediate MDT setting.

[0411] In possible implementations, the first piece of information may include an index of the first MDT setting.

[0412] In a possible implementation, the receiving unit 701 is further configured to receive second information from a first network device, the second information representing first MDT data, the first MDT data being obtained through measurements based on a first MDT setting.

[0413] In possible implementations, the transmitting unit 702 is further configured to transmit second information to a second network device.

[0414] In possible implementations, the second piece of information may include an index of the first MDT data.

[0415] Figure 8 is a possible configuration diagram of the communication device in the above-described embodiment, where each functional module is obtained through division based on its corresponding function. The device may be a network device, or a module used in a network device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of performing all or part of the functions of a network device. As shown in Figure 8, the communication device 800 may include a receiving unit 801 and a transmitting unit 802.

[0416] The receiving unit 801 is configured to receive first information from a second network device, the first information indicating a first MDT setting, the first MDT setting including an MDT setting corresponding to a terminal device.

[0417] The transmitting unit 802 is configured to transmit the first MDT settings to the second network device.

[0418] In possible implementations, the transmitting unit 802 is further configured to transmit the first information to a terminal device.

[0419] In a possible implementation, the receiving unit 801 is further configured to receive third information from a core network device or OAM, the third information indicating that it stores the first MDT settings.

[0420] In possible implementations, the third piece of information may include the identifier of the terminal device and the index of the first MDT setting.

[0421] In possible implementations, the third piece of information may further include the retention period and / or the index range of the first MDT setting.

[0422] In a possible implementation, the receiving unit 801 is further configured to receive second information from a second network device, the second information representing first MDT data, the first MDT data being obtained through measurements based on first MDT settings.

[0423] In possible implementations, the transmitting unit 802 is further configured to transmit the first MDT data to a second network device.

[0424] In possible implementations, the transmitting unit 802 is further configured to transmit second information to a terminal device, the second information representing first MDT data, the first MDT data being obtained through measurements based on first MDT settings.

[0425] In a possible implementation, the receiving unit 801 is further configured to receive a fourth piece of information from a core network device or OAM, the fourth piece of information indicating that it stores the first MDT data, which is obtained through measurements based on the first MDT settings.

[0426] In possible implementations, the fourth piece of information may include the identifier of the terminal device and an index of the first MDT data.

[0427] In possible implementations, the fourth piece of information may further include the retention period and / or index range of the first MDT data.

[0428] Figure 9 is another possible configuration diagram of the communication device in the above-described embodiment, where each functional module is obtained through division based on its respective corresponding function. The device may be a network device, or a module used in a network device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of performing all or part of the functions of a network device. As shown in Figure 9, the communication device 900 may include a transmitting unit 901, a receiving unit 902, and a processing unit 903.

[0429] The transmitting unit 901 is configured to transmit first information to a first network device, the first information indicating a first MDT setting, and the first MDT setting includes an MDT setting corresponding to a terminal device.

[0430] The receiving unit 902 is configured to receive the first MDT settings from the first network device.

[0431] The processing unit 903 is configured to determine a second MDT setting based on a first MDT setting.

[0432] The transmitting unit 901 is further configured to transmit a second MDT setting to the terminal device.

[0433] In possible implementations, the receiving unit 902 is further configured to receive first information from a terminal device.

[0434] In possible implementations, the transmitting unit 901 is further configured to transmit second information to a first network device, the second information representing first MDT data, the first MDT data being obtained through measurements based on first MDT settings.

[0435] In possible implementations, the receiving unit 902 is further configured to receive first MDT data from a first network device.

[0436] In possible implementations, the receiving unit 902 is further configured to receive second information from a terminal device, the second information representing first MDT data, the first MDT data being obtained through measurements based on first MDT settings.

[0437] Figure 10 is a possible configuration diagram of the communication device in the above-described embodiment, where each functional module is obtained through division based on its corresponding function. The device may be a terminal device, or a module used in a terminal device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of performing all or part of the functions of a terminal device. As shown in Figure 10, the communication device 1000 may include a receiving unit 1001, a transmitting unit 1002, and a processing unit 1003.

[0438] The receiving unit 1001 is configured to receive a first MDT setting from a first network device, the first MDT setting including an MDT setting corresponding to a terminal device.

[0439] The transmitting unit 1002 is configured to transmit the first MDT settings to the second network device.

[0440] The receiving unit 1001 is further configured to receive a second MDT setting from a second network device, the second MDT setting being obtained based on the first MDT setting.

[0441] The processing unit 1003 is configured to perform MDT measurements based on a second MDT setting.

[0442] In possible implementations, the processing unit 1003 is further configured to store the first MDT settings before being disconnected from the first network device.

[0443] In possible implementations, the transmitting unit 1002 is specifically configured to transmit the first MDT configuration to the second network device after establishing a connection to the second network device.

[0444] In a possible implementation, the receiving unit 1001 is further configured to receive fifth information from a first network device, the fifth information indicating that it stores the first MDT setting.

[0445] In possible implementations, the receiving unit 1001 is further configured to receive first MDT data from a first network device, the first MDT data being acquired through measurements based on a first MDT setting.

[0446] In possible implementations, the transmitting unit 1002 is further configured to transmit the first MDT data to a second network device.

[0447] In a possible implementation, the receiving unit 1001 is further configured to receive sixth information from a first network device, the sixth information indicating that it stores first MDT data, the first MDT data is obtained through measurements based on first MDT settings.

[0448] Figure 11 is another possible configuration diagram of the communication device in the above-described embodiment, where each functional module is obtained through division based on its respective corresponding function. The device may be a network device, or a module used in a network device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of performing all or part of the functions of a network device. As shown in Figure 11, the communication device 1100 may include a receiving unit 1101 and a transmitting unit 1102.

[0449] The receiving unit 1101 is configured to receive a first MDT setting from a core network device or OAM, the first MDT setting including an MDT setting corresponding to a terminal device.

[0450] The transmission unit 1102 is configured to send the first MDT setting to the terminal device.

[0451] In possible implementations, the transmission unit 1102 is further configured to transmit a fifth piece of information to a terminal device, the fifth piece of information indicating that it stores the first MDT setting.

[0452] In possible implementations, the transmission unit 1102 is further configured to transmit first MDT data to a terminal device, the first MDT data being acquired through measurements based on first MDT settings.

[0453] In possible implementations, the transmission unit 1102 is further configured to transmit a sixth piece of information to a terminal device, the sixth piece of information indicating that it stores first MDT data, the first MDT data is obtained through measurements based on first MDT settings.

[0454] Figure 12 is another possible configuration diagram of the communication device in the above-described embodiment, where each functional module is obtained through division based on its respective corresponding function. The device may be a network device, or a module used in a network device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of performing all or part of the functions of a network device. As shown in Figure 12, the communication device 1200 may include a receiving unit 1201, a processing unit 1202, and a transmitting unit 1203.

[0455] The receiving unit 1201 is configured to receive a first MDT setting from a terminal device, the first MDT setting including an MDT setting corresponding to the terminal device.

[0456] The processing unit 1202 is configured to determine a second MDT setting based on a first MDT setting.

[0457] The transmission unit 1203 is configured to send the second MDT setting to the terminal device.

[0458] In possible implementations, the receiving unit 1201 is further configured to receive first MDT data from a terminal device, the first MDT data being acquired through measurements based on a first MDT setting.

[0459] Figure 13 is a possible configuration diagram of the communication device in the above-described embodiment, where each functional module is obtained through division based on its respective corresponding function. The device may be a terminal device, or a module used in a terminal device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of performing all or part of the functions of a terminal device. As shown in Figure 13, the communication device 1300 may include a receiving unit 1301, a transmitting unit 1302, and a processing unit 1303.

[0460] The receiving unit 1301 is configured to receive the fourth MDT setting from the first network device.

[0461] The transmitting unit 1302 is configured to transmit first instruction information to a second network device. The first instruction information includes an identifier for the terminal device. The aforementioned fifth MDT setting is obtained based on the aforementioned third MDT setting.

[0462] The receiving unit 1301 is further configured to receive a fifth MDT setting from a second network device.

[0463] The processing unit 1303 is configured to perform MDT measurements based on a fifth MDT setting.

[0464] The fourth MDT setting is obtained based on the third MDT setting. The third MDT setting is a management-based MDT setting, and the MDT activation type is "Immediate MDT and Logging MDT". The third MDT setting includes the MDT activation type, immediate MDT setting, logging MDT setting, and TR information. The TR information indicates the first TR and the second TR, where the first TR is the TR for the immediate MDT setting and the second TR is the TR for the logging MDT setting. The first TR is the same as the second TR. The fourth MDT setting includes the MDT activation type, immediate MDT setting, logging MDT setting, and TR information. The first instruction information indicates the third MDT setting stored in the core network device.

[0465] In possible implementations, the receiving unit 1301 is further configured to receive a target TRSR identifier from a first network device, and the first instruction information may include the target TRSR identifier and / or the identifier of a terminal device. The target TRSR identifier is the TRSR identifier assigned to the terminal device by the first network device. The terminal device corresponding to the MDT data may be identified by using the TRSR identifier.

[0466] In possible implementations, the transmitting unit 1302 is further configured to transmit a second instruction information to a second network device. The second instruction information indicates that a logged MDT measurement report is stored in the terminal device.

[0467] In possible implementations, the first instruction information and the second instruction information may be the same information.

[0468] In possible implementations, the transmission unit 1302 is further configured to send a logged MDT measurement report to a second network device.

[0469] Figure 14 is another possible configuration diagram of the communication device in the above-described embodiment, where each functional module is obtained through division based on its respective corresponding function. The device may be a network device, or a module used in a network device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of performing all or part of the functions of a network device. As shown in Figure 14, the communication device 1400 may include a receiving unit 1401, a processing unit 1402, and a transmitting unit 1403.

[0470] The receiving unit 1401 is configured to receive a third MDT configuration transmitted by the core network device.

[0471] The processing unit 1402 is configured to determine a fourth MDT setting based on a third MDT setting.

[0472] The transmission unit 1403 is configured to send the fourth MDT setting to the terminal device.

[0473] The third MDT setting is a management-based MDT setting, and the MDT activation type is "Immediate MDT and Logging MDT". The third MDT setting includes the MDT activation type, immediate MDT setting, logging MDT setting, and TR information. The TR information indicates the first TR and the second TR, where the first TR is the TR for the immediate MDT setting and the second TR is the TR for the logging MDT setting. The first TR is the same as the second TR. The fourth MDT setting is an MDT setting corresponding to the terminal device.

[0474] In possible implementations, the transmitting unit 1403 is further configured to transmit a fourth MDT setting and a target TRSR identifier to the core network device. The target TRSR identifier is the TRSR identifier assigned to the terminal device by the first network device.

[0475] In possible implementations, the first TR and the second TR may be indicated by using the same TR.

[0476] In another possible implementation, the first TR and the second TR may be indicated by using two identical TRs.

[0477] In possible implementations, a third MDT setting may further include the MDT area range.

[0478] In possible implementations, the fourth MDT setting may further include an identifier for the terminal device.

[0479] In possible implementations, the transmission unit 1403 is further configured to transmit a target TRSR identifier to a terminal device.

[0480] Figure 15 is another possible configuration diagram of the communication device in the above-described embodiment, where each functional module is obtained through division based on its corresponding function. The device may be a network device, or a module used in a network device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of performing all or part of the functions of a network device. 15 As shown, the communication device 1500 may include a receiving unit 1501, a transmitting unit 1502, and a processing unit 1503.

[0481] The receiving unit 1501 is configured to receive first instruction information from the terminal device.

[0482] The transmitting unit 1502 is configured to transmit the first instruction information to the core network device.

[0483] The receiving unit 1501 is configured to receive a third MDT configuration transmitted by the core network device.

[0484] The processing unit 1503 is configured to determine a fifth MDT setting based on a third MDT setting.

[0485] The transmission unit 1502 is configured to send the fifth MDT setting to the terminal device.

[0486] The first instruction information indicates the third MDT setting stored in the core network device. The first instruction information includes the identifier of the terminal device. The third MDT setting includes the MDT setting corresponding to the terminal device.

[0487] In possible implementations, the receiving unit 1501 is further configured to receive a third MDT setting and a target TRSR identifier transmitted by the core network device.

[0488] In a possible implementation, the first instruction information indicates a third MDT setting and a target TRSR identifier stored in the core network device, and the first instruction information includes the target TRSR identifier and / or the identifier of the terminal device.

[0489] In possible implementations, the receiving unit 1501 is further configured to receive second instruction information transmitted by the terminal device. The second instruction information indicates that a logged MDT measurement report is stored in the terminal device.

[0490] In possible implementations, the transmission unit 150 2 It is further configured to send a first response to a terminal device, which is used to request a logged MDT measurement report.

[0491] In possible implementations, the receiving unit 1501 is further configured to receive logged MDT measurement reports transmitted by the terminal device.

[0492] In possible implementations, the transmission unit 150 2 It is further configured to send logged MDT measurement reports to TCE.

[0493] In possible implementations, the transmission unit 150 2 It is further configured to transmit TR information and / or MDT activation type to the core network device.

[0494] In possible implementations, processing unit 150 3 It is further configured to correlate the immediate MDT measurement report and the logged MDT measurement report of the terminal device by using the target TRSR identifier and TR information.

[0495] In possible implementations, the fifth MDT setting may be the same as the fourth MDT setting.

[0496] For a more detailed explanation of the functions performed by the communication device units described in Figures 7 to 15, please refer to the description of the steps performed by the terminal device or network device in the embodiments of the method described above.

[0497] Embodiments of the present application further provide a chip. Figure 16 is a diagram of the configuration of chip 1600. Chip 1600 includes one or more processors 1601 and an interface circuit 1602. Optionally, chip 1600 may further include a bus 1603.

[0498] The processor 1601 may be an integrated circuit chip and has signal processing capabilities. In the implementation process, the steps in the aforementioned communication method can be completed through the integrated logic circuits of the hardware within the processor 1601 or by using software-based instructions.

[0499] For example, the processor 1601 may be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA), or another programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The processor is capable of implementing or performing the methods and steps disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor, or the processor may be any conventional processor or of the same kind.

[0500] The interface circuit 1602 can be configured to transmit or receive data, instructions, or information. The processor 1601 may process the data, instructions, or other information received through the interface circuit 1602, and may transmit the processed information through the interface circuit 1602.

[0501] Optionally, the chip may include additional memory. This memory includes read-only memory and random-access memory, capable of providing operational instructions and data to the processor. Some of the memory may further include non-volatile random-access memory (NVRAM).

[0502] Optionally, memory can store executable software modules or data structures, and the processor can perform corresponding operations by calling operation instructions stored in memory (the operation instructions may be stored in the operating system).

[0503] Optionally, the chip may be used in a communication device according to embodiments of the present application. Optionally, the interface circuit 1602 may be configured to output the execution results of the processor 1601. For communication methods provided in one or more embodiments of the present application, please refer to the embodiments described above. Further details are not described here again.

[0504] It should be noted that the functions corresponding to the processor 1601 and the interface circuit 1602 may be implemented by using hardware design, by using software design, or by using a combination of software and hardware. This is not limited to the present invention.

[0505] Figure 17 is a structural diagram of a communication device according to an embodiment of the present application. The communication device is applicable to the scenario shown in the embodiment of the method described above. For ease of explanation, Figure 17 shows only the main components of the communication device, including a processor 1701, memory 1702, control circuit 1703, and input / output device 1704. The processor 1701 is mainly configured to process communication protocols and communication data, execute software programs, and process data of software programs. The memory 1702 is mainly configured to store software programs and data. The control circuit 1703 is mainly configured to supply power and transmit various electrical signals. The input / output device 1704 is mainly configured to receive data input by the user and output data to the user.

[0506] If the communication device is the processor 1701, the control circuit 1703 may be the main board. The memory 1702 includes a storage medium such as a hard disk, RAM, or ROM. The processor 1701 is a baseband processor. Sakyu The system may also include a central processing unit. The baseband processor is configured primarily to process communication protocols and communication data. The central processing unit is configured primarily to control the entire communication device, execute software programs, and process data for the software programs. Input / output devices 1704 include displays, keyboards, mice, and the like. The control circuit 1703 may further include or be connected to a transceiver circuit or transceiver, such as a network cable interface, and is configured to transmit or receive data or signals, for example, to perform data transmission and communication with another device. Furthermore, the control circuit may include an antenna configured to receive and transmit radio signals, and an antenna configured to perform data / signal transmission with another device.

[0507] Embodiments of the present application further provide a communication device. The device includes at least one processor. When the at least one processor executes program code or instructions, the aforementioned related method steps are implemented to realize the communication method in the aforementioned embodiment.

[0508] Optionally, the device may further include at least one memory, at least one of which is configured to store program code or instructions.

[0509] Embodiments of the present application further provide a computer storage medium. The computer storage medium stores computer instructions. When a computer instruction is executed by a communication device, the communication device can perform the aforementioned related method steps to implement the communication method in the aforementioned embodiment.

[0510] Embodiments of this application further provide a computer program product. When the computer program product is executed on a computer, the computer is able to perform the aforementioned related steps and implement the communication method in the embodiments described above.

[0511] Embodiments of the present application further provide a communication device. The device may specifically be a chip, an integrated circuit, a component, or a module. Specifically, the device may include a connected processor and a memory configured to store instructions, or the device may include at least one processor configured to retrieve instructions from an external memory. When the device is in operation, the processor executes instructions to enable the chip to perform the communication method in the embodiments of the present invention.

[0512] Embodiments of the present application further provide a communication system. The communication system includes a plurality of communication devices. The communication devices are configured to perform the communication method in the embodiments of the method described above.

[0513] It should be understood that the sequence numbers of the aforementioned processes do not represent the execution order in the various embodiments of this application. The execution order of the processes should be determined based on the function and internal logic of the processes and should not be interpreted as any limitation to the implementation processes of the embodiments of this application.

[0514] A person skilled in the art will recognize that, in combination with the examples described in the embodiments disclosed in this specification, the units and algorithmic steps may be implemented by electronic hardware or by a combination of computer software and electronic hardware. Whether the functions are performed by hardware or by software depends on the specific application and design constraints of the technical solution. A person skilled in the art will recognize that different methods may be used to implement the described functions for each specific application, but such implementations should not be considered to extend beyond the scope of the embodiments of this application.

[0515] For the sake of convenient and concise explanation, it will be readily apparent to those skilled in the art that the detailed operating processes of the aforementioned systems, apparatus, and units are described by referring to the corresponding processes in the embodiments of the methods described above. Further details are not described here.

[0516] It should be understood that, in some embodiments provided in the embodiments of this application, the systems, apparatus, and methods disclosed may be implemented in other ways. For example, the embodiments of the apparatus described are merely examples. For example, the division into units is merely a logical functional division, and other divisions may be used in actual implementations. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not performed. Furthermore, the mutual coupling, direct coupling, or communication connection shown or described may be implemented through some interfaces. Indirect coupling or communication connection between apparatus or units may be implemented electronically, mechanically, or in other forms.

[0517] Units described as separate components may or may not be physically separate, and components illustrated as units may or may not be physical units, may be located in one place, or may be distributed across multiple network units. Some or all of the units can be selected based on actual requirements to achieve the objectives of the solution of the embodiment.

[0518] Furthermore, the functional units in the embodiments of this application may be integrated into a single processing unit, or each unit may exist physically independently, or two or more units may be integrated into a single unit.

[0519] When a function is implemented in the form of a software function unit and sold or used as an independent product, the function may be stored on a computer-readable storage medium. Based on such understanding, the technical solutions of the embodiments of this application, or the parts that contribute to the prior art, or parts of the technical solutions, may be implemented in the form of a software product. A computer software product is stored on a storage medium and includes several instructions for instructing a computer device (which may be a personal computer, server, network device, etc.) to perform all or part of the steps of the method described in the embodiments of this application. The aforementioned storage medium includes any medium capable of storing program code, such as a USB flash drive, removable hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

Claims

1. It is a method of communication: A step of receiving first information from a first network device, wherein the first information indicates a first drive test minimized MDT setting, and the first MDT setting includes an MDT setting corresponding to a terminal device; A step of transmitting the first information to a second network device; A step of receiving a second MDT setting from the second network device, wherein the second MDT setting is obtained based on the first MDT setting; and Steps to perform an MDT measurement based on the second MDT setting described above; A method that includes this.

2. The method according to claim 1, further: Steps of storing the first information before being disconnected from the first network device; A method that includes this.

3. In the method according to claim 1 or 2, the step of transmitting the first information to a second network device is: The step of transmitting the first information to the second network device after establishing a connection to the second network device; Methods that include...

4. A method according to any one of claims 1 to 3, wherein the second MDT setting includes an immediate drive test minimized MDT setting.

5. A method according to any one of claims 1 to 4, wherein the first information includes an index of the first MDT setting.

6. The method according to any one of claims 1 to 5, further: A step of receiving second information from the first network device, wherein the second information indicates a first MDT setting, and the first MDT setting is obtained through a measurement based on the first MDT setting; A step of transmitting the second information to a second network device; A method that includes this.

7. The method according to claim 6, wherein the second information includes an index of the first MDT data.

8. It is a method of communication: The steps include: receiving first information from a second network device, wherein the first information indicates a first MDT setting, and the first MDT setting includes an MDT setting corresponding to a terminal device; and A step of sending the first MDT settings to the second network device; A method that includes this.

9. The method according to claim 8, further: Step of transmitting the first information to the terminal device; A method that includes this.

10. The method according to claim 8 or 9, further: A step of receiving third information from a core network device or an Operations Maintenance Management (OAM), wherein the third information indicates that the first MDT setting is stored; A method that includes this.

11. The method according to claim 11, wherein the third information includes an identifier for the terminal device and an index for the first MDT setting.

12. The method according to claim 11, wherein the third information further includes the retention period of the first MDT setting and / or the index range of the first MDT setting.

13. The method according to any one of claims 8 to 12, further: A step of receiving second information from the second network device, wherein the second information represents first MDT data, and the first MDT data is obtained through a measurement based on the first MDT setting; and The step of transmitting the first MDT data to a second network device; A method that includes this.

14. The method according to any one of claims 8 to 13, further: A step of transmitting the second information to the terminal device, wherein the second information represents the first MDT data, and the first MDT data is obtained through measurement based on the first MDT setting; A method that includes this.

15. The method according to any one of claims 8 to 14, further: A step of receiving a fourth piece of information from a core network device or the OAM, wherein the fourth piece of information indicates that it stores first MDT data, and the first MDT data is obtained through measurements based on the first MDT settings; A method that includes this.

16. The method according to claim 15, wherein the fourth information includes an identifier for the terminal device and an index of the first MDT data.

17. The method according to claim 16, wherein the fourth information further includes the retention period of the first MDT data and / or the index range of the first MDT data.

18. It is a method of communication: A step of sending first information to a first network device, wherein the first information indicates a first MDT setting, and the first MDT setting includes an MDT setting corresponding to a terminal device; Steps include receiving the first MDT settings from the first network device; A step of determining a second MDT setting based on the first MDT setting; Steps include sending the second MDT setting to the terminal device; A method that includes this.

19. The method according to claim 18, further: A step of receiving the first information from the terminal device; A method that includes this.

20. The method according to claim 18 or 19, further: A step of transmitting second information to the first network device, wherein the second information represents first MDT data, and the first MDT data is obtained through a measurement based on the first MDT setting; and Steps include receiving the first MDT data from the first network device; A method that includes this.

21. The method according to any one of claims 18 to 20, further: A step of receiving second information from the terminal device, wherein the second information represents first MDT data, and the first MDT data is obtained through measurement based on the first MDT setting; A method that includes this.

22. A communication device comprising a module configured to perform the method according to any one of claims 1 to 7, the method according to any one of claims 8 to 17, or the method according to any one of claims 18 to 21.

23. A communication device including a processor, wherein the processor is coupled to a memory, the memory is configured to store instructions, and when an instruction is executed by the processor, the communication device becomes capable of performing the method according to any one of claims 1 to 7, the method according to any one of claims 8 to 17, or the method according to any one of claims 18 to 21.

24. A computer-readable storage medium configured to store a computer program, wherein when the computer program is in operation, the method according to any one of claims 1 to 7, the method according to any one of claims 8 to 17, or the method according to any one of claims 18 to 21 is executed.

25. A computer program product comprising an instruction, wherein when the instruction is executed, the method according to any one of claims 1 to 7, the method according to any one of claims 8 to 17, or the method according to any one of claims 18 to 21 is executed.

26. A chip comprising at least one processor and memory, wherein when the at least one processor executes a program or instruction stored in the memory, the information processing device becomes capable of performing the method according to any one of claims 1 to 7, any one of claims 8 to 17, or any one of claims 18 to 21.

Images