A method and device for minimizing drive test configuration

Abstract

The present invention provides a method and device for minimizing drive test configuration, wherein a first node sends MDT state information to a second node; the second node determines whether to configure management-based logging-type MDT measurement for a UE, thereby avoiding the situation where the network reconfigures MDT for the UE and incorrectly overwrites the currently valid MDT configuration information.

Description

Technical Field

[0001] The present invention relates to wireless communication technology, and in particular to a configuration method and device for minimizing drive test measurements. Background Art

[0002] Modern mobile communications are increasingly tending to provide users with high-speed transmission of multimedia services, such as Figure 1 The following is a diagram of the system architecture of the System Architecture Evolution (SAE).

[0003] User equipment (UE) 101 is a terminal device used to receive data. Evolved Universal Terrestrial Radio Access Network (E-UTRAN) 102 is a wireless access network, which includes a macro base station (eNodeB / NodeB) that provides a wireless network interface for the UE to access. The mobile management entity (MME) 103 is responsible for managing the mobile context, session context and security information of the UE. The serving gateway (SGW) 104 mainly provides user plane functions, and the MME 103 and SGW 104 may be in the same physical entity. The packet data network gateway (PGW) 105 is responsible for functions such as billing and lawful interception, and may also be in the same physical entity as the SGW 104. The policy and charging rules function entity (PCRF) 106 provides quality of service (QoS) policies and charging criteria. The general packet radio service support node (SGSN) 108 is a network node device that provides routing for data transmission in the universal mobile telecommunications system (UMTS). The Home Subscriber Server (HSS) 109 is the home subsystem of the UE and is responsible for protecting user information including the current location of the user equipment, the address of the service node, user security information, and the packet data context of the user equipment.

[0004] like Figure 2 The following is a system architecture diagram of the next generation network or the fifth generation 5G network.

[0005] User equipment (UE) 201 is a terminal device used to receive data. The next generation radio access network (NG-RAN) 202 is a radio access network, which includes a base station (gNB or eNB connected to the 5G core network 5GC, the eNB connected to the 5GC is also called ng-gNB) that provides the UE with an access wireless network interface. The access control and mobility management function entity (AMF) 203 is responsible for managing the mobility context and security information of the UE. The user plane function entity (UPF) 204 mainly provides user plane functions. The session management function entity SMF 205 is responsible for session management. The data network (DN) 206 includes services such as operators, Internet access, and third-party services. Summary of the invention

[0006] According to one aspect of the present application, a method for minimizing drive tests (MDT) configuration is provided, wherein the method is performed by a first node and includes:

[0007] The second node receives the MDT state information sent by the first node;

[0008] The second node decides whether to configure management-based logging-type MDT measurement for the user equipment UE, or continues to calculate the remaining time length included in the MDT state information, or sends the MDT state information to the third node.

[0009] The first node is a base station, or a core network node.

[0010] The second base station is a base station, or a core network.

[0011] The MDT status information includes indication information. The indication information may indicate at least one of the following:

[0012] MDT measurement is configured for the UE, logging-type MDT measurement is configured for the UE, signaling-based MDT measurement is configured for the UE, signaling-based logging-type MDT measurement is configured for the UE, and management-based logging-type MDT measurement is configured for the UE.

[0013] The MDT status information further includes at least one of the following: a unique identifier of the MDT, a type of the configured MDT, a configuration time of the log-type MDT, a measurement time length of the log-type MDT, and a remaining time length of the log-type MDT.

[0014] According to another aspect of the present application, a method for minimizing drive tests (MDT) configuration is characterized by comprising: a first node determining MDT status information; the first node sending the MDT status information to a second node so that the second node decides whether to configure management-based logging-type MDT measurement for a user equipment UE, or to continue to calculate the remaining time length included in the MDT status information, or to send the MDT status information to a third node.

[0015] According to another aspect of the present application, a node is provided, including:

[0016] The transceiver is used for transmitting and receiving signals, and the processor is used for controlling the node to execute the method of the second node according to various aspects of the present application.

[0017] According to another aspect of the present application, a node is provided, including: a transceiver for transmitting and receiving signals, and a processor for controlling the node to execute the first node method according to various aspects of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1This is the existing LTE system architecture diagram;

[0019] Figure 2 This is the existing 5G system architecture diagram;

[0020] Figure 3 It is a schematic diagram of the MDT measurement structure;

[0021] Figure 4 This is a schematic diagram of a process of Embodiment 1 of the present invention;

[0022] Figure 5 This is a schematic diagram of the process of Embodiment 2 of the present invention;

[0023] Figure 6 This is a schematic diagram of the process of Embodiment 3 of the present invention;

[0024] Figure 7 This is a schematic diagram of a flow chart of Embodiment 4 of the present invention;

[0025] Figure 8 This is a schematic diagram of the process of Embodiment 5 of the present invention;

[0026] Fig. 9 It is a schematic diagram of the device of the present invention;

[0027] Fig.10 It is a schematic diagram of the method of the present invention;

[0028] Fig.11 This is a flow chart of Embodiment 6 of the present invention;

[0029] Fig.12 This is a flow chart of Embodiment 7 of the present invention;

[0030] Fig.13 This is a flow chart of Embodiment 8 of the present invention;

[0031] Fig.14 is a flowchart of Embodiment 9 of the present invention; and

[0032] Fig.15 This is a flowchart of the tenth embodiment of the present invention. DETAILED DESCRIPTION

[0033] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application is further described in detail below in conjunction with the accompanying drawings. It should be noted that the following description is only for illustration and is not intended to limit the present disclosure. In the following description, in order to provide a thorough understanding of the present disclosure, a large number of specific details are set forth. However, it is obvious to a person of ordinary skill in the art that these specific details do not have to be adopted to implement the present disclosure. In other examples, in order to avoid confusing the present disclosure, known circuits, materials or methods are not specifically described.

[0034] Throughout the specification, references to "one embodiment," "an embodiment," "an example," or "an example" mean that a particular feature, structure, or characteristic described in conjunction with the embodiment or example is included in at least one embodiment of the present disclosure. Therefore, the phrases "in one embodiment," "in an embodiment," "an example," or "an example" appearing in various places throughout the specification do not necessarily all refer to the same embodiment or example. In addition, particular features, structures, or characteristics may be combined in one or more embodiments or examples in any suitable combination and / or sub-combination. In addition, it will be appreciated by those of ordinary skill in the art that the figures provided herein are for illustrative purposes and that the figures are not necessarily drawn to scale. The term "and / or" as used herein includes any and all combinations of one or more of the associated listed items.

[0035] Minimization of drive tests (MDT) is to let the base station or user perform some measurements and transmit the measurement results to the measurement center node, such as the TCE (Trace Collection Entity) node, to reduce the burden of manual testing. MDT measurement must support real-time and non-real-time measurements. The core network or operation and maintenance node sends an MDT activation message to the access network node. The message carries specific MDT measurement configurations, such as measurement type, measurement cycle, threshold, reporting cycle or threshold, etc. Some MDT measurement types require the UE to perform measurements. For these measurement types, the access network node sends an RRC message to the UE to configure the UE to perform MDT measurements, and the UE reports the measurement results to the access network node. Some MD measurement types require the base station to perform measurements. For these measurement types, the base station performs MDT measurements based on specific configuration information. The access network sends the measurement results, including the measurement results performed by the UE and the measurement results performed by the base station, to the measurement center node.

[0036] According to the MDT initiation method, MDT can be divided into management-based MDT and signaling-based MDT. Management-based MDT means that the access network entity receives an MDT activation message from the operation and maintenance node, and signaling-based MDT means that the access network entity receives an MDT activation message from a core network entity, such as a mobility management entity.

[0037] According to the state of the UE, the MDT measurement performed by the UE in the RRC connected state is called timely MDT, and the MDT measurement performed by the UE in the RRC idle state or RRC inactive state (RRC-inactive) is called logged MDT.

[0038] Figure 3The structural diagram of the management-based MDT is described. 301 represents the operation and maintenance node (ElementManagement, referred to as EM), and the operation and maintenance node 301 sends an MDT activation request message to the access network node 302. The access network node 302 can be a 4G system eNB or a gNB or eNB in ​​a 5G system, or a base station in other systems. The MDT activation request message contains the configuration information of the MDT. The configuration information of the MDT mainly includes: MDT location selection conditions, reporting mechanism configuration, trace reference (Trace Reference, referred to as TR), IP address of the MDT measurement center node (such as TCE), work type, MDT data anonymity and other information. The above work types can be configured into different types. For example, there are currently four types defined: Immediate MDT only, Logged MDT only, Trace only, Immediate MDT and Trace. It is not excluded to define more types or simplified types. The MDT location selection condition configures which UEs in which locations can be selected as users for MDT measurement. The location selection condition can be configured as the range of the cell, or the range of the TAC, or the entire PLMN. UEs within the range can be selected as UEs for MDT. TR uniquely identifies an MDT process. In an MDT process, the base station can select multiple users for MDT measurement.

[0039] The access network node 302 selects the UE for MDT measurement. When the access network node selects the UE, it must follow certain conditions, such as whether the user agrees to perform the measurement and / or whether the UE is located in the MDT position in the MDT configuration information. If the UE does not agree to MDT, or the UE does not meet the position selection conditions, the UE cannot be selected as the UE for MDT. After selecting the UE, if the UE needs to perform measurement, the access network node 302 sends the MDT configuration information to the UE 303. The UE 303 performs MDT measurement according to the configuration, and when the reporting conditions are met, the measurement results are sent to the network node access network node 302. The access network node 302 sends an MDT tracking message to the core network entity 305. The core network entity can be the 4G mobile management entity MME (Mobility Management Entity), the 5G AMF (Access and Mobility Management Function), or a core network entity connected to the access network in other systems. The message contains at least the MDT identifier and the IP address of the TCE. The core network entity 305 finds the unique identifier of the UE, such as IMSI or IMEI (SV), and sends the unique identifier to the TCE. The access network node 302 saves the MDT measurement results, also called MDT records, and according to a predefined policy, the access network node 302 sends the MDT records to the MDT central node 304 (for example, the tracking collection entity TCE). The MDT central node 304 combines the information sent by the core network entity to know which UEs the MDT records are for.

[0040] The difference between signaling-based MDT is that the MDT startup message is sent from the core network entity to the access network entity, and the MDT configuration information is allocated by the core network entity.

[0041] Fig.10 This is a schematic diagram of the method of the present invention. By using this method, it is avoided that when the network reconfigures MDT for the UE, the currently valid MDT configuration information is mistakenly overwritten.

[0042] In step 1001, the first node sends MDT status information to the second node.

[0043] The first node may be a 3G base station, a 4G base station, a 5G base station, or a base station of other systems, or a 3G core network, a 4G core network, or a 5G core network. The second node may be a 3G base station, a 4G base station, a 5G base station, or a base station of other systems, or a 3G core network, a 4G core network, or a 5G core network.

[0044] The MDT status information may include a status indication, such as one or more of the following statuses:

[0045] -Indicates whether MDT measurements are configured for the UE;

[0046] - Indicates whether logged MDT measurements are configured for the UE;

[0047] - Indicates whether signaling-based MDT measurements are configured for the UE;

[0048] - Indicates whether signaling-based logging-type MDT measurements are configured for the UE;

[0049] - Indicates whether management-based logged MDT measurements are configured for the UE.

[0050] The MDT state information may include a unique identifier of a configured MDT, such as TR (Trace Reference) and TRSR (Trace Recording Session Reference).

[0051] The MDT status information may include the type of MDT that has been configured, such as management-based logging-type MDT and signaling-based logging-type MDT.

[0052] The MDT state information may include a first timestamp, where the timestamp is the time when the log-type MDT is configured, for example, the time when the signaling-based log-type MDT is configured, and the configuration time is the absolute time of the base station when the base station sends the RRC message of log-type MDT configuration to the UE, for example, in the form of year-month-day hour-minute-second. The time is the same as the absolute time included in the RRC message of log-type MDT configuration sent by the base station to the UE.

[0053] The MDT status information may include the measurement time length (Logging duration) of the logging MDT, such as the measurement time length of the logging MDT based on signaling. This logging MDT has been configured in the UE. The measurement time length parameter is sent by the core network to the base station, and then sent by the base station to the UE. The value of this parameter is the same as the measurement time length (Logging duration) included in the RRC message sent to the UE.

[0054] The MDT status information may further include a second timestamp, which is the remaining time length of the logged MDT. The remaining time length may be the remaining time length of the logged MDT measurement based on signaling and / or the remaining time length of the logged MDT measurement based on management.

[0055] In step 1002, the second node determines one or more of the following actions according to the MDT status information:

[0056] 1) Determine whether management-based logging-based MDT can be configured for the UE;

[0057] 2) Calculate MDT status information;

[0058] 3) Send MDT status information to the next node.

[0059] The second node determines whether to configure the signaling-based logging-type MDT measurement for the UE according to the MDT state information. For example, if the MDT state information indicates that the signaling-based logging-type MDT measurement has been configured for the UE, and / or through the timestamp included in the MDT state information, the base station knows that the signaling-based logging-type MDT measurement has been configured for the UE, and the measurement has not timed out, then the second node cannot configure the management-based logging-type MDT measurement for the UE, and if it has timed out, the management-based logging-type MDT measurement can be configured for the UE.

[0060] The second node determines whether to configure management-based logged MDT measurement for the UE according to the configuration time of the logged MDT and with reference to the MDT configuration parameters.

[0061] The second node continues to calculate the remaining time length included in the MDT state information. If the remaining time length is 0, the node 2 may delete the corresponding MDT state information.

[0062] The second node may send the MDT state information, or the updated MDT state information, to the next node. The next node may be a 3G base station, a 4G base station, a 5G base station, or a base station of another system, or a 3G core network, a 4G core network, or a 5G core network.

[0063] The method of the present invention avoids the situation where the network reconfigures MDT for UE and incorrectly overwrites the currently valid MDT configuration information.

[0064] Embodiment 1:

[0065] Figure 4 Embodiment 1 of the present invention is described. A UE in RRC connected mode is configured with signaling-based logging-type MDT measurement or management-based logging-type MDT measurement, and then the UE enters RRC idle mode, and the base station reports the MDT state to the core network, and the core network saves the MDT state information for subsequent processes.

[0066] Specifically, Figure 4 The following steps may be included:

[0067] Step 401: An RRC connection is established between the UE and the base station.

[0068] The base station can be a 3G base station, a 4G base station, or a 5G base station, or a base station of another access system. The process of establishing an RRC connection adopts the current process, which includes the following three steps. After the UE establishes the RRC connection, it enters the RRC connection mode. The base station saves the context information of the UE.

[0069] 1.UE initiates the establishment of RRC connection and sends an RRC establishment request message to DU. The message carries the temporary identifier of UE and the reason for RRC establishment.

[0070] 2. The RRC establishment message is sent to the UE.

[0071] 3. The RRC connection establishment complete message carries the operator identifier (eg PLMN ID) selected by the UE.

[0072] The message also includes a non-access layer message. After receiving the message, the base station sends the non-access layer message to the core network mobile function node AMF.

[0073] Step 402: The base station sends an initial UE message to the core network.

[0074] After receiving the message that the RRC connection establishment is complete, the base station sends an "initial UE message" to the core network through the interface between the base station and the core network. The core network can be a 3G core network, a 4G core network, a 5G core network, or a core network of other systems. The message carries the non-access layer message carried by the UE in the RRC connection establishment completion message. The message also carries the location information of the UE, such as the network-wide unique identifier of the cell where the UE is located. The message contains the temporary identifier of the UE, which is assigned to the UE by the core network, such as the 5G-S-TMSI assigned to the UE by the 5G core network.

[0075] Step 403: The core network sends an initial context establishment request message to the base station.

[0076] The core network receives the message of step 402 and can find the context information of the UE according to the temporary identifier of the UE. Thus, the capability information of the UE is obtained. The UE sends an initial context establishment request message to the base station. The message contains the information of the data bearer established for the UE, the encryption capability information of the UE, and the wireless access capability information. In this message, trace or MDT measurement can also be configured for the UE. After establishing the UE context of the base station, the core network can also configure trace or MDT measurement for the UE through a separate trace activation process.

[0077] The MDT measurement parameters include the measurement identifier, such as TRSR, TCE identifier (TCE ID), measurement area configuration, whether the measurement is record-based or timely, if it is record-based, it also includes the measurement time length, whether the reporting type is periodic or event-triggered, the measurement type, etc. The measurement time length indicates the time length that the UE needs to perform the measurement, for example, it can be set to 10 minutes, 2 hours, etc.

[0078] After step 403 is completed, the base station may send a successful response message to the core network.

[0079] Step 404: The base station sends the MDT configuration to the UE.

[0080] After receiving the MDT measurement from the core network, if the UE needs to perform measurement, such as record-type MDT, it needs to be configured to the UE in advance, and the MDT measurement is started when the UE enters the idle mode or RRC-inactive mode. The base station sends an RRC message to the UE, such as a record-type measurement configuration message, which carries the configuration parameters of the MDT measurement. The measurement configuration parameters include the measurement identifier, such as TRSR, TCE identifier (TCE ID), measurement area configuration, network absolute timestamp, which is used to provide the UE with a reference to the absolute time of the current cell, the length of the MDT measurement, whether the reporting type is periodic or event-triggered, and the type of measurement. The measurement length indicates the length of time the UE needs to perform the measurement, which can be set to 10 minutes, 2 hours, etc. After receiving the MDT configuration, the UE starts to start the clock corresponding to the measurement time. When the UE state changes or moves out of the measurement range, the clock continues to calculate until the length of the MDT measurement time expires, the clock stops, the MDT record also stops, and the corresponding configuration can also be cleared.

[0081] Step 405: The base station sends a UE context release request message to the core network.

[0082] The base station decides to release the RRC connection of the UE and put the UE into RRC idle mode. The base station sends a UE context release request message to the core network. The message carries the interface identifier assigned by the base station to the UE, the interface identifier assigned by the core network to the UE, and the reason for the release. If the UE has been configured with logged MDT measurement, the message may also include MDT status information, which may include status indications, such as one or more of the following statuses:

[0083] -Indicates whether MDT measurements are configured for the UE;

[0084] - Indicates whether logged MDT measurements are configured for the UE;

[0085] - Indicates whether signaling-based MDT measurements are configured for the UE;

[0086] - Indicates whether signaling-based logging-type MDT measurements are configured for the UE;

[0087] - Indicates whether management-based logged MDT measurements are configured for the UE.

[0088] The MDT state information may include a unique identifier of a configured MDT, such as TR (Trace Reference) and TRSR (Trace Recording Session Reference).

[0089] The MDT status information may include the type of MDT that has been configured, such as management-based logging-type MDT and signaling-based logging-type MDT.

[0090] The MDT state information may further include a first timestamp, where the timestamp is the configuration time of the log-type MDT, such as the configuration time of the log-type MDT based on signaling, where the configuration time is the absolute time of the cell when the base station sends the RRC message of the log-type MDT configuration to the UE, such as the format of year-month-day hour-minute-second. The configuration time of the log-type MDT included in the MDT state information is the same as the time included in the RRC message of the log-type MDT configuration sent by the base station to the UE.

[0091] The MDT status information may also include the measurement duration of the logging MDT, such as the measurement duration of the logging MDT based on signaling. This logging MDT has been configured in the UE. The parameter is sent by the core network to the base station, and the base station sends it to the UE. The value of this parameter is the same as the measurement duration (Logging duration) included in the RRC message sent to the UE.

[0092] The MDT status information may further include a second timestamp, which is a time stamp of the remaining time length of the logged MDT, and the remaining time length may be the remaining time length of the logged MDT measurement based on signaling and / or the remaining time length of the logged MDT measurement based on management.

[0093] The remaining time length of the logging-type MDT is related to the logging-type MDT time length (loggingduration) in the MDT configuration parameters. It is calculated from the time when the UE is configured to perform logging-type measurements. The initial remaining time length is the logging-type MDT time length until the logging-type MDT time length times out and the remaining time length is 0. For example, at 10 a.m. on a certain day, the base station configures the UE to perform MDT logging-type measurements, where the MDT logging-type measurement time length is set to 2 hours. From then on, the base station starts to calculate the remaining time length. If at 11 a.m. on the same day, the base station decides to release the RRC connection, the base station notifies the core network that the signaling-based logging-type MDT has been configured for the UE, and notifies the core network that the remaining time of the signaling-based logging-type MDT is one hour. The remaining time length of the logging-type MDT can be expressed as an absolute time of 12 o'clock, or as a relative time of 60 minutes.

[0094] After receiving the MDT status information, the core network saves the MDT status information in the context of the UE, including the configuration time of the logging-type MDT, and sends the MDT status information to the base station if necessary when the UE enters the connected mode next time. The core network has saved the MDT configuration information. If the UE returns to the RRC connected state later, the core network receives the initial UE message from the UE's serving base station. The core network determines whether to send the MDT status information to the UE's serving base station based on the configuration time of the signaling-based logging-type MDT and the logging-type MDT duration (logging duration) in the MDT configuration information. For example, the configuration time of the signaling-based logging-type MDT is 10 a.m. on a certain day, and the logging-type MDT duration is two hours. When the core network receives the initial UE message, the time of the core network is 12 a.m. Based on the above time information, the core network knows that the logging time period of the signaling-based logging-type MDT has been exceeded, and the core network may not send the MDT status information to the base station. If there is no new MDT configuration, the core network does not send the MDT configuration parameters to the base station. If the core network receives the initial UE message at 11:00 a.m., the core network needs to send the MDT status information to the UE's serving base station, and the core network can also send MDT configuration parameters to the base station. The base station can decide whether to configure management-based logging MDT measurements for the UE based on the status information.

[0095] After receiving the MDT status information, the core network saves the MDT status information in the context of the UE. The core network can continue to calculate the remaining time length and send the MDT status information to the base station if necessary when the UE enters the connected mode next time. If the UE returns to the RRC connected state within the remaining time length indicated by the base station, the core network needs to send the MDT status information to the UE's serving base station. The MDT status information contains the remaining time length calculated by the core network. After receiving the information, the base station decides whether to configure management-based logging-type MDT measurements for the UE based on the remaining time length. If the UE returns to the RRC connected state after the remaining time indicated by the base station, the core network does not need to send the MDT status information to the UE's serving base station.

[0096] It should be noted that the base station may also report the MDT state information to the core network in the UE context release complete message.

[0097] It should be noted that this method is also applicable to the process of UE context release initiated by the core network. The core network sends a UE context release command to the base station, and the base station can indicate the MDT state information to the core network after the UE context release is completed.

[0098] Step 406: The core network sends a UE context release command message to the base station.

[0099] The core network sends a dedicated message to confirm the release of the UE context.

[0100] Step 407: The base station sends an RRC release message to the UE.

[0101] The base station initiates a dedicated RRC process to release the configuration information of the RRC connection on the UE side.

[0102] Step 408: The base station sends a UE context release completion message to the core network.

[0103] The base station sends a dedicated UE message to the core network to confirm the release of the UE connection.

[0104] Embodiment 2:

[0105] Figure 5 Embodiment 2 of the present invention is described. When the UE enters the RRC connected mode from the idle mode, the core network sends the MDT status to the serving base station of the UE. The serving base station determines whether to configure the management-based logging MDT for the UE according to the MDT status information. Specifically, Figure 5 The specific steps are as follows.

[0106] Step 501: UE sends a base station RRC establishment request message to a base station.

[0107] The base station can be a 3G base station, a 4G base station, or a 5G base station, or a base station of another access system. The UE initiates the establishment of an RRC connection and sends an RRC establishment request message to the DU. The message carries the temporary identifier of the UE and the reason for the RRC establishment.

[0108] Step 502: The base station sends an RRC establishment message to the UE.

[0109] Step 503: The UE sends an RRC setup completion message to the base station.

[0110] The RRC establishment complete message carries the operator identifier (e.g. PLMN ID) selected by the UE. The message also contains a non-access layer message. After receiving the message, the base station sends the non-access layer message to the core network mobile function node AMF. After establishing the RRC connection, the UE enters the RRC connection mode. The base station saves the UE's context information.

[0111] The UE can also notify the base station through the RRC establishment completion message that the UE is configured with the record-type MDT measurement and how much measurement time is left. After receiving the information, the network can save it in the context of the UE and not configure the record-type MDT measurement during the remaining measurement time unless necessary, so as to avoid wrongly covering the original measurement.

[0112] Step 504: The base station sends an initial UE message to the core network.

[0113] After receiving the message that the RRC connection establishment is complete, the base station sends an "initial UE message" to the core network through the interface between the base station and the core network. The core network can be a 3G core network, a 4G core network, a 5G core network, or a core network of other systems. The message carries the non-access layer message carried by the UE in the RRC connection establishment completion message. The message also carries the location information of the UE, such as the network-wide unique identifier of the cell where the UE is located. The message contains the temporary identifier of the UE, which is assigned to the UE by the core network, such as the 5G-S-TMSI assigned to the UE by the 5G core network.

[0114] Step 505: The core network sends an initial context establishment request message to the base station.

[0115] The core network receives the message of step 504 and can find the context information of the UE according to the temporary identifier of the UE. Thus, the capability information of the UE is obtained. The core network sends an initial context establishment request message to the base station. The message includes the information of the data bearer established for the UE, the encryption capability information of the UE, and the wireless access capability information. The context of the UE also includes the configuration parameters of the MDT and the status information of the MDT. Therefore, in this message, the message can also include the configuration parameters of the MDT and the MDT status information. The MDT status information can include a status indication, such as one or more of the following states:

[0116] -Indicates whether MDT measurements are configured for the UE;

[0117] - Indicates whether logged MDT measurements are configured for the UE;

[0118] - Indicates whether signaling-based MDT measurements are configured for the UE;

[0119] - Indicates whether signaling-based logging-type MDT measurements are configured for the UE;

[0120] - Indicates whether management-based logged MDT measurements are configured for the UE.

[0121] The MDT state information may include a unique identifier of a configured MDT, such as TR (Trace Reference) and TRSR (Trace Recording Session Reference).

[0122] The MDT status information may include the type of MDT that has been configured, such as management-based logging-type MDT and signaling-based logging-type MDT.

[0123] The MDT state information may further include a first timestamp, where the first timestamp is the configuration time of the log-type MDT, such as the configuration time of the log-type MDT based on signaling, and the configuration time is the absolute time of the cell when the base station sends the RRC message of the log-type MDT configuration to the UE, such as the format of year-month-day hour-minute-second. The configuration time of the log-type MDT included in the MDT state information is the same as the time included in the RRC message of the log-type MDT configuration sent by the base station to the UE.

[0124] The MDT status information may also include the measurement duration of the logging MDT, such as the measurement duration of the logging MDT based on signaling. This logging MDT has been configured in the UE. The parameter is sent by the core network to the base station, and the base station sends it to the UE. The value of this parameter is the same as the measurement duration (Logging duration) included in the RRC message sent to the UE.

[0125] The MDT status information may further include a second timestamp, which is the remaining time length of the logged MDT. The remaining time length may be the remaining time length of the logged MDT measurement based on signaling and / or the remaining time length of the logged MDT measurement based on management.

[0126] The core network can calculate the remaining time using one of the following methods:

[0127] -Calculated by the core network based on the MDT status information reported by the base station. For example, at 10:00 a.m. on a certain day, the base station configures the UE to perform MDT logging measurement, where the MDT logging measurement time length is set to 2 hours. From then on, the base station starts to calculate the remaining time length. If at 10:30 a.m. on the same day, the base station decides to release the RRC connection, the base station notifies the core network that the signaling-based logging MDT has been configured for the UE, and notifies the core network of the remaining time length of the signaling-based logging MDT. For example, using the above example, at 10:00 a.m. the base station sends the MDT configuration information to the UE, and the logging MDT time length is set to 2 hours. At 11:00 a.m. on the same day, the base station allows the UE to enter the RRC idle mode. The remaining time length of the logging MDT contained in the UE context release request message sent by the base station to the core network can be expressed as an absolute time of 12 o'clock, or as a relative time of 60 minutes. Afterwards, the core network saves the information in the context of the UE and continues to calculate the remaining time length if necessary.

[0128] -The core network calculates it by itself, which is calculated from the length of the record-type MDT time. If the core network is configured with the signaling-based record-type MDT, the core network starts calculating the remaining MDT time length from the time the core network sends the MDT configuration information to the base station. For example, at 10 o'clock on a certain day, the core network sends the MDT configuration information to the base station, and the length of the record-type MDT time is 2 hours. Then the calculation starts from 10 o'clock, and the remaining MDT time is one minute less than 2 hours for every minute that passes.

[0129] The remaining time length in the MDT status information can be expressed as an absolute time or a relative time. For example, in the above example, the core network sends the MDT configuration information to the base station at 10 o'clock, and then the UE enters the RRC idle mode and returns to the RRC connected state before 11 o'clock. The remaining time length contained in the initial context establishment request message sent by the core network can be expressed as an absolute time of 12 o'clock or a relative time of 60 minutes.

[0130] Step 506: The base station may send a successful response message to the core network.

[0131] After receiving the message, the base station saves the information in the context of the UE.

[0132] The base station receives the MDT status information. If the MDT status information indicates that the signaling-based logging-type MDT measurement has been configured for the UE, and / or the MDT status information includes the configuration time and the measurement time length of the logging-type MDT, the base station can know that the signaling-based logging-type MDT measurement has been configured for the UE, whether the measurement time of the signaling-based logging-type MDT has timed out, and thus can decide whether the management-based logging-type MDT measurement can be configured for the UE. For example, the configuration time of the signaling-based logging-type MDT is 10:00 a.m. on a certain day, and the signaling-based logging-type MDT time length is two hours. If the base station time is after 12:00 a.m. when the initial context establishment request is received, based on the above time information, the base station knows that the logging time period of the signaling-based logging-type MDT has been exceeded, and the base station can send the management-based logging-type MDT configuration to the UE. If the base station time is 11:00 a.m. when the initial context establishment request is received, the base station cannot configure the management-based logging-type MDT measurement for the UE. Or if the MDT status information is not received, it means that the base station can send the management-based logging-type MDT configuration to the UE.

[0133] The base station receives the MDT status information. If the MDT status information indicates that the management-based logging-type MDT measurement has been configured for the UE, and / or the base station knows the remaining length of the MDT time from the status information, the base station can decide whether to configure the management-based MDT measurement for the UE according to the MDT status information. For example, if the remaining length of the signaling-based logging-type MDT time included in the MDT status information is 60 minutes, it means that the management-based logging-type MDT measurement cannot be configured for the UE within 60 minutes. After that, the base station can configure the management-based logging-type MDT measurement for the UE as needed.

[0134] After saving the UE information, the base station sends a successful response message to the core network.

[0135] Embodiment three:

[0136] Figure 6 Embodiment 3 of the present invention is described. The UE cell reselects to a new cell, the new cell is on a new base station, the UE requests to restore the RRC connection, or requests RRC reconstruction, the new base station obtains the UE context information from the old base station, the old base station has configured the UE to perform log-based MDT measurement, the old base station sends the MDT status to the new base station, the new base station saves it to the UE context, and decides whether to configure management-based log-based MDT for the UE. Specifically, Figure 6 The specific steps are as follows.

[0137] Step 601: UE sends an RRC recovery request message to a new base station.

[0138] The message may include the UE's identifier in the old cell, which includes the information of the old base station, the C-RNTI allocated by the new cell, the physical layer identifier PCI of the new cell, and the network-wide unique identifier of the new cell.

[0139] Step 602: The new base station sends a UE context acquisition request message to the old base station.

[0140] The new base station receives the recovery request message, and knows that the UE context is on the old base station through the information of the old base station contained in the message. The new base station sends a UE context acquisition request message to the old base station.

[0141] The Get UE Context Request message contains the UE Context Identifier. For the RRC recovery process, the UE Context Identifier contains the UE's identifier in the old cell, the temporary C-RNTI of the UE assigned by the new cell, i.e. the cell that received the RRC recovery request, and the PCI of the new cell. The message also contains the cell unique identifier of the new cell, such as CGI, and the reason for the RRC recovery.

[0142] Step 603: The old base station sends a UE context acquisition response message to the new base station.

[0143] The old base station determines whether to send a response message to the new base station based on the information of the old base station. If the UE context can be sent to the new base station, the old base station sends a Get UE Context Response message to the new base station. The message may include the UE context information, the MDT configuration parameters, and the MDT status information. The MDT status information may include a status indication, such as one or more of the following statuses:

[0144] -Indicates whether MDT measurements are configured for the UE;

[0145] - Indicates whether logged MDT measurements are configured for the UE;

[0146] - Indicates whether signaling-based MDT measurements are configured for the UE;

[0147] - Indicates whether signaling-based logging-type MDT measurements are configured for the UE;

[0148] - Indicates whether management-based logged MDT measurements are configured for the UE.

[0149] The MDT state information may include a unique identifier of a configured MDT, such as TR (Trace Reference) and TRSR (Trace Recording Session Reference).

[0150] The MDT status information may include the type of MDT that has been configured, such as management-based logging-type MDT and signaling-based logging-type MDT.

[0151] The MDT state information may further include a first timestamp, where the first timestamp is the configuration time of the log-type MDT, such as the configuration time of the log-type MDT based on signaling, and the configuration time is the absolute time of the cell when the base station sends the RRC message of the log-type MDT configuration to the UE, such as the format of year-month-day hour-minute-second. The configuration time of the log-type MDT included in the MDT state information is the same as the time included in the RRC message of the log-type MDT configuration sent by the base station to the UE.

[0152] The MDT status information may also include the measurement duration of the logging MDT, such as the measurement duration of the logging MDT based on signaling. This logging MDT has been configured in the UE. The parameter is sent by the core network to the base station, and the base station sends it to the UE. The value of this parameter is the same as the measurement duration (Logging duration) included in the RRC message sent to the UE.

[0153] The MDT status information may further include a second timestamp, where the second timestamp is the remaining time length of the logged MDT, and the remaining time length may be the remaining time length of the logged MDT measurement based on signaling and / or the remaining time length of the logged MDT measurement based on management.

[0154] The remaining time length of the logging-type MDT is related to the logging-type MDT time length (loggingduration) in the MDT configuration parameters. It is calculated from the time when the UE is configured to perform logging-type measurement. The initial remaining time length is the logging-type MDT time length until the logging-type MDT time length times out and the remaining time length is 0. For example, at 10 o'clock on a certain day, the old base station configures the UE to perform MDT logging-type measurement, where the MDT logging-type measurement time length is set to 2 hours. From then on, the old base station starts to calculate the remaining time length. If at 11 o'clock in the morning of the same day, the old base station receives the Get UE Context Request message, the old base station notifies the new base station that the logging-type MDT has been configured for the UE, and notifies the new base station of the remaining time length of the logging-type MDT. For example, using the above example, at 10 o'clock in the morning, the old base station sends the MDT configuration information to the UE, and the logging-type MDT time length is set to 2 hours. At 11 o'clock in the morning of the same day, the old base station receives the Get UE Context Request message, then the MDT remaining time length contained in the Get UE Context Response message sent by the old base station can be expressed as an absolute time of 12 o'clock, or as a relative time of 60 minutes.

[0155] The new base station receives the MDT status information and saves the information in the context of the UE. If the MDT status information indicates that the signaling-based logging-type MDT measurement has been configured for the UE, and / or the MDT status information includes the configuration time and measurement time length of the logging-type MDT, the new base station can know that the signaling-based logging-type MDT measurement has been configured for the UE, whether the measurement time of the signaling-based logging-type MDT has timed out, and thus can decide whether to configure the management-based logging-type MDT measurement for the UE. For example, the configuration time of the signaling-based logging-type MDT is 10:00 a.m. on a certain day, and the signaling-based logging-type MDT time length is two hours. If the time of the new base station is after 12:00 a.m. when the new base station receives the initial context establishment request, based on the above time information, the new base station knows that the logging time period of the signaling-based logging-type MDT has been exceeded, and the new base station can send the management-based logging-type MDT configuration to the UE. If the time of the new base station is 11:00 a.m. when the initial context establishment request is received, the new base station cannot configure the management-based logging-type MDT measurement for the UE. Or if no MDT status information is received, it means that the base station can send a management-based logging-type MDT configuration to the UE.

[0156] After receiving the MDT status information, the new base station saves the MDT status information in the context of the UE and can continue to calculate the remaining time length. If the MDT status information indicates that the management-based logging-type MDT measurement has been configured for the UE, and / or the remaining time length of the MDT is known from the status information base station, the new base station can decide whether to configure the management-based MDT measurement for the UE based on the MDT status information. For example, if the remaining time length of the signaling-based logging-type MDT contained in the MDT status information is 60 minutes, it means that the management-based logging-type MDT measurement cannot be configured for the UE within 60 minutes. After that, the new base station can configure the management-based logging-type MDT measurement for the UE as needed.

[0157] Step 604: The new base station sends an RRC recovery response message to the UE.

[0158] Step 605: The UE sends an RRC recovery complete message to the new base station.

[0159] It should be noted that this method is also applicable to the RRC re-establishment process, and it is only necessary to replace the corresponding message with the message in the RRC re-establishment process.

[0160] Embodiment 4:

[0161] Figure 7 Embodiment 4 of the present invention is described. A UE switches from a source base station to a target base station. The source base station sends MDT status information to the target base station, and the target base station saves the MDT status information to the context of the UE and decides whether to configure management-based logging MDT for the UE. Specifically, Figure 7 The specific steps are as follows.

[0162] Step 701: The source base station sends a UE handover request to the target base station.

[0163] The message may include the identifier of the target cell, the capability information of the UE, the bearer information to be established, and if the signaling-based MDT measurement is configured in the source base station, the message may also include the configuration parameters of the MDT. The message may also include MDT status information. The MDT status information may include a status indication, such as one or more of the following statuses:

[0164] -Indicates whether MDT measurements are configured for the UE;

[0165] - Indicates whether logged MDT measurements are configured for the UE;

[0166] - Indicates whether signaling-based MDT measurements are configured for the UE;

[0167] - Indicates whether signaling-based logging-type MDT measurements are configured for the UE;

[0168] - Indicates whether management-based logged MDT measurements are configured for the UE.

[0169] The MDT state information may include a unique identifier of a configured MDT, such as TR (Trace Reference) and TRSR (Trace Recording Session Reference).

[0170] The MDT status information may include the type of MDT that has been configured, such as management-based logging-type MDT and signaling-based logging-type MDT.

[0171] The MDT state information may further include a first timestamp, where the first timestamp is the configuration time of the log-type MDT, such as the configuration time of the log-type MDT based on signaling, and the configuration time is the absolute time of the cell when the base station sends the RRC message of the log-type MDT configuration to the UE, such as the format of year-month-day hour-minute-second. The configuration time of the log-type MDT included in the MDT state information is the same as the time included in the RRC message of the log-type MDT configuration sent by the base station to the UE.

[0172] The MDT status information may also include the measurement duration of the logging MDT, such as the measurement duration of the logging MDT based on signaling. This logging MDT has been configured in the UE. The parameter is sent by the core network to the base station, and the base station sends it to the UE. The value of this parameter is the same as the measurement duration (Logging duration) included in the RRC message sent to the UE.

[0173] The MDT status information may further include a second timestamp, where the second timestamp is the remaining time length of the logged MDT, and the remaining time length may be the remaining time length of the logged MDT measurement based on signaling and / or the remaining time length of the logged MDT measurement based on management.

[0174] The remaining time length of the logging-type MDT is related to the logging-type MDT time length (loggingduration) in the MDT configuration parameters. It is calculated from the time when the UE is configured to perform logging-type measurements. The initial remaining time length is the logging-type MDT time length until the logging-type MDT time length times out and the remaining time length is 0. For example, at 10 o'clock on a certain day, the source base station configures the UE to perform MDT logging-type measurements, where the MDT logging-type measurement time length is set to 2 hours. From then on, the source base station starts calculating the remaining time length. If at 11 o'clock in the morning of the same day, the source base station decides to switch the UE to the destination base station, the source base station notifies the destination base station of the remaining time length of the logging-type MDT. The remaining time length of MDT can be expressed as an absolute time of 12 o'clock, or as a relative time of 60 minutes.

[0175] The destination base station receives the MDT status information and saves the information in the context of the UE. If the MDT status information indicates that the source base station has configured the signaling-based log-type MDT measurement for the UE, and / or the MDT status information includes the configuration time and measurement time length of the log-type MDT, the destination base station can know that the signaling-based log-type MDT measurement has been configured for the UE and whether the measurement time of the signaling-based log-type MDT has timed out, so as to decide whether to configure the management-based log-type MDT measurement for the UE. For example, if the configuration time of the signaling-based log-type MDT is 10 o'clock in the morning of a certain day, and the signaling-based log-type MDT time length is two hours, then after 12 o'clock on the same day, the destination base station can send the management-based log-type MDT configuration to the UE. Previously, the destination base station could not configure the management-based log-type MDT measurement for the UE. Or if the MDT status information is not received, it means that the destination base station can send the management-based log-type MDT configuration to the UE.

[0176] After receiving the MDT status information, the destination base station saves the MDT status information in the context of the UE and, if necessary, continues to calculate the remaining time length. If the MDT status information indicates that management-based logging-type MDT measurement has been configured for the UE, and / or the remaining time length of the MDT is known from the status information base station, the destination base station can decide whether to configure management-based MDT measurement for the UE based on the MDT status information. For example, if the remaining time length of the signaling-based logging-type MDT contained in the MDT status information is 60 minutes, it means that management-based logging-type MDT measurement cannot be configured for the UE within 60 minutes. After that, the destination base station can configure management-based logging-type MDT measurement for the UE as needed.

[0177] Step 702: The target base station sends a handover request response message to the source base station.

[0178] Step 703: The source base station sends an RRC reconfiguration request message to the UE.

[0179] The message may contain the configuration of the switch.

[0180] Step 704: The UE sends an RRC reconfiguration completion message to the target base station.

[0181] This message may contain information that the handover is complete.

[0182] Embodiment five:

[0183] Figure 8 Embodiment 5 of the present invention is described. Through the interface between the base station and the core network, the UE switches from the source base station to the target base station. The source base station sends MDT status information to the core network, the core network sends MDT status information to the target base station, the target base station saves the MDT status information to the context of the UE, and decides whether to configure management-based logging MDT for the UE. Specifically, Figure 8 The specific steps are as follows.

[0184] Step 801: The source base station sends a handover required message to the core network.

[0185] The source base station decides to switch the UE to the destination base station based on the UE measurement results. The message carries the identifier of the destination base station or the identifier of the destination cell. If there is no horizontal interface between the source base station and the destination base station, the source base station sends a switching request message to the core network.

[0186] The message may also include MDT status information. The MDT status information may include a status indication, such as one or more of the following statuses:

[0187] -Indicates whether MDT measurements are configured for the UE;

[0188] - Indicates whether logged MDT measurements are configured for the UE;

[0189] - Indicates whether signaling-based MDT measurements are configured for the UE;

[0190] - Indicates whether signaling-based logging-type MDT measurements are configured for the UE;

[0191] - Indicates whether management-based logged MDT measurements are configured for the UE.

[0192] The MDT state information may include a unique identifier of a configured MDT, such as TR (Trace Reference) and TRSR (Trace Recording Session Reference).

[0193] The MDT status information may include the type of MDT that has been configured, such as management-based logging-type MDT and signaling-based logging-type MDT.

[0194] The MDT state information may further include a first timestamp, where the timestamp is a configuration time of the log-type MDT, such as a configuration time of the log-type MDT based on management, where the configuration time is an absolute time of the cell when the base station sends an RRC message of log-type MDT configuration to the UE, such as an identifier in the form of year-month-day hour-minute-second. The configuration time of the log-type MDT included in the MDT state information is the same as the time included in the RRC message of log-type MDT configuration sent by the base station to the UE.

[0195] The MDT status information may also include the measurement time length of the logging MDT, such as the measurement time length of the logging MDT based on signaling. This logging MDT has been configured in the UE. The parameter is sent by the core network to the base station, and the base station sends it to the UE. The value of this parameter is the same as the measurement time length (Logging duration) included in the RRC message sent to the UE.

[0196] The MDT status information may further include a second timestamp, which is the remaining time length of the logged MDT. The remaining time length may be the remaining time length of the logged MDT measurement based on signaling and / or the remaining time length of the logged MDT measurement based on management.

[0197] The remaining time length of the logging-type MDT is related to the logging-type MDT time length (loggingduration) in the MDT configuration parameters. It is calculated from the time when the UE is configured to perform logging-type measurements. The initial remaining time length is the logging-type MDT time length until the logging-type MDT time length times out and the remaining time length is 0. For example, at 10 o'clock on a certain day, the source base station configures the UE to perform MDT logging-type measurements, where the MDT logging-type measurement time length is set to 2 hours. From then on, the source base station starts calculating the remaining time length. If at 11 o'clock in the morning of the same day, the source base station decides to switch the UE to the destination base station, the source notifies the destination base station of the remaining time length of the logging-type MDT. The remaining time length of MDT can be expressed as an absolute time of 12 o'clock, or as a relative time of 60 minutes.

[0198] Step 802: The core network sends a handover request to the target base station.

[0199] The core network receives the message in step 801 and sends a handover request to the target base station. The handover request message includes the UE identifier on the interface and the information of the bearer to be established. The message also includes the configuration parameters of the MDT. The message may also include the MDT status information. The MDT status information is as described in step 801.

[0200] The destination base station receives the MDT status information and saves the information in the context of the UE. If the MDT status information indicates that the source base station has configured signaling-based log-type MDT measurements for the UE, and / or the MDT status information includes the configuration time and measurement time length of the log-type MDT, the destination base station can know that signaling-based log-type MDT measurements have been configured for the UE and whether the measurement time of the signaling-based log-type MDT has timed out, so as to decide whether management-based log-type MDT measurements can be configured for the UE. For example, if the configuration time of the signaling-based log-type MDT is 10:00 a.m. on a certain day, and the signaling-based log-type MDT time length is two hours, then after 12:00 a.m. on the same day, the destination base station can send management-based log-type MDT configuration to the UE. Previously, the destination base station could not configure management-based log-type MDT measurements for the UE.

[0201] After receiving the MDT status information, the destination base station saves the MDT status information in the context of the UE and continues to calculate the remaining time length if necessary. If the MDT status information indicates that the management-based logging-type MDT measurement has been configured for the UE, and / or the MDT remaining time length is known from the status information base station, the destination base station can decide whether to configure the management-based MDT measurement for the UE based on the MDT status information. For example, if the signaling-based logging-type MDT remaining time length contained in the MDT status information is 60 minutes, it means that the management-based logging-type MDT measurement cannot be configured for the UE within 60 minutes. After that, the destination base station can configure the management-based logging-type MDT measurement for the UE as needed.

[0202] Step 803: The target base station sends a handover response to the core network.

[0203] The message may carry the UE's interface identifier and the information of the bearer received. The RRC container in the handover response message may contain the handover command to be sent to the UE.

[0204] Step 804: The core network sends a handover command message to the source base station.

[0205] The message can confirm that the target base station has made handover preparations, and can also carry the identifier of the UE on the interface and the information of the bearer accepted by the target base station.

[0206] Step 805: The source base station sends a handover command to the UE.

[0207] The source base station sends the handover command generated by the target base station to the UE.

[0208] Step 806: The UE synchronizes with the target cell and sends a handover completion message to the target base station.

[0209] Step 807: The target base station sends a switching notification message to the core network.

[0210] Embodiment six:

[0211] Fig.11 Embodiment 6 of the present invention is described. The method of the present invention can also be used in the case of dual connection. When the master base station MN establishes dual connection for the UE, the master base station and the auxiliary base station SN can send RRC messages to the UE respectively, which means that the master base station and the auxiliary base station do not know whether the other party has configured MDT. Therefore, the MN needs to tell the SN whether the MN has configured MDT measurement for the UE, and then the SN can refer to the information to decide whether to configure MDT for the UE. Specifically, Fig.11 The specific steps are as follows.

[0212] Step 1101: a master base station MN sends a secondary base station adding request or a secondary base station modifying request message to a secondary base station SN.

[0213] The primary base station / secondary base station can be an LTE base station or a 5G base station gNB. Assume that both the primary base station and the secondary base station are connected to the 5G core network. Both the LTE base station and the 5G base station belong to the 5G access network.

[0214] The primary base station decides to establish certain bearers, such as service data flows (QoS flows), on the secondary base station. The secondary base station establishment request message or the secondary base station modification request message carries one or more of the following information:

[0215] The location indication of the upper layer resources. For example, it indicates whether the PDCP is on the secondary base station or not on the secondary base station. If it is not on the secondary base station, it indicates that the PDCP is established on the primary base station.

[0216] The location indication of the lower layer resources. For example, it indicates whether the MCG RLC resources exist, whether the SCG RLC resources exist, or both exist. If both exist, it corresponds to the split RLC resources.

[0217] A list of QoS flow identifiers. It corresponds to the identifiers of the QoS flows to be established on the secondary base station, that is, the list of identifiers of the QoS flows to be diverted. If the primary base station indicates that the PDCP is established on the secondary base station, the secondary base station can determine the mapping of the above QoS flows to the data radio bearer. The QoS flow identifier is sent by the core network to the primary base station through the initial context establishment process or the initial context modification process.

[0218] Quality requirement parameters of QoS Flow. This information is the quality requirement corresponding to the QoS flow, which may include the standard 5G quality requirement indication 5QI, priority ARP, uplink / downlink maximum rate of GBR service, and uplink / downlink guaranteed rate of GBR service. Or it may include specific parameters of quality requirements, such as resource type, priority level, data delay target, error rate and other information. The QoS Flow identifier and the corresponding quality requirement parameters are transmitted from the core network to the primary base station. The primary base station can directly send the value transmitted from the core network to the secondary base station, or determine a new value based on the value transmitted from the core network and send it to the secondary base station.

[0219] If the primary base station configures MDT measurement for the UE, for example, log-type MDT, after sending the MDT measurement configuration to the UE, the primary base station can delete the MDT information stored on the base station, but the primary base station needs to tell the secondary base station the MDT status information, so the message can also include the MDT status information.

[0220] MDT status information: The MDT status information may include a status indication, such as one or more of the following statuses:

[0221] -Indicates whether MDT measurements are configured for the UE;

[0222] - Indicates whether logged MDT measurements are configured for the UE;

[0223] - Indicates whether signaling-based MDT measurements are configured for the UE;

[0224] - Indicates whether signaling-based logging-type MDT measurements are configured for the UE;

[0225] - Indicates whether management-based logging-type MDT measurements are configured for the UE;

[0226] - Indicates whether signaling-based timely MDT measurements are configured for the UE;

[0227] - Indicates whether management-based timely MDT measurements are configured for the UE;

[0228] - Indicates whether the MDT configuration has been released;

[0229] - Indicates whether the secondary base station is allowed to configure MDT for the UE.

[0230] The MDT state information may include a unique identifier of a configured MDT, such as TR, TRSR.

[0231] The MDT status information may include the type of MDT that has been configured, such as management-based logging-type MDT, signaling-based logging-type MDT, signaling-based timely MDT, and management-based timely MDT.

[0232] The MDT state information may further include a first timestamp, where the timestamp is a configuration time of the log-type MDT, such as a configuration time of the log-type MDT based on management, where the configuration time is an absolute time of the cell when the base station sends an RRC message of log-type MDT configuration to the UE, such as an identifier in the form of year-month-day hour-minute-second. The configuration time of the log-type MDT included in the MDT state information is the same as the time included in the RRC message of log-type MDT configuration sent by the base station to the UE.

[0233] The MDT status information may also include the measurement duration of the logging MDT, such as the measurement duration of the logging MDT based on signaling. This logging MDT has been configured in the UE. The parameter is sent by the core network to the base station, and the base station sends it to the UE. The value of this parameter is the same as the measurement duration (Logging duration) included in the RRC message sent to the UE.

[0234] The MDT status information may further include a second timestamp, which is the remaining time length of the logged MDT. The remaining time length may be the remaining time length of the logged MDT measurement based on signaling and / or the remaining time length of the logged MDT measurement based on management.

[0235] The remaining time length of the logging-type MDT is related to the logging-type MDT time length (loggingduration) in the MDT configuration parameters. It is calculated from the time when the UE is configured to perform logging-type measurements. The initial remaining time length is the logging-type MDT time length until the logging-type MDT time length times out and the remaining time length is 0. For example, at 10 o'clock on a certain day, the primary base station configures the UE to perform MDT logging-type measurements, where the MDT logging-type measurement time length is set to 2 hours. From then on, the primary base station starts calculating the remaining time length. If at 11 o'clock in the morning of the same day, the primary base station decides to configure dual connectivity for the UE, the primary base station notifies the secondary base station of the remaining time length of the logging-type MDT. The remaining time length of MDT can be expressed as an absolute time of 12 o'clock, or as a relative time of 60 minutes.

[0236] Step 1102: The secondary base station sends a secondary base station establishment response or a secondary base station modification response message to the primary base station.

[0237] The secondary base station receives the MDT status information and saves the information in the context of the UE. If the MDT status information indicates that the primary base station has configured the signaling-based timely MDT measurement for the UE, the secondary base station no longer configures the management-based timely MDT measurement for the UE.

[0238] Alternatively, the auxiliary base station can know that the signaling-based recorded MDT measurement has been configured for the UE through the configuration time of the recorded MDT and the measurement time length of the recorded MDT included in the MDT status information. It can also determine whether the management-based recorded MDT measurement can be configured for the UE based on the exception-based MDT measurement time. For example, if the configuration time of the signaling-based recorded MDT is 10:00 a.m. on a certain day, and the signaling-based recorded MDT time length is two hours, then after 12:00 a.m. on the same day, the auxiliary base station can send the management-based recorded MDT configuration to the UE. Previously, the auxiliary base station could not configure the management-based recorded MDT measurement for the UE.

[0239] Alternatively, the MDT state information includes the remaining time length of the log-type MDT, and the auxiliary base station can decide whether to configure the management-based log-type MDT measurement for the UE according to the MDT state information. For example, if the remaining time length of the signaling-based log-type MDT included in the MDT state information is 60 minutes, it means that the management-based log-type MDT measurement cannot be configured for the UE within 60 minutes, and then the auxiliary base station can configure the management-based log-type MDT measurement for the UE as needed.

[0240] If the MDT status information indicates that the MDT configuration has been released, the secondary base station can configure MDT measurements for the UE according to its own needs. If the MDT status information indicates that the secondary base station is allowed to perform MDT measurements on the UE, the secondary base station can configure MDT measurements for the UE according to its own needs. If the MDT status information indicates that the secondary base station is not allowed to perform MDT measurements on the UE, the secondary base station cannot configure MDT measurements for the UE.

[0241] The secondary base station establishment response message or the secondary base station modification response message includes one or more of the following information:

[0242] A list of QoS flows that the secondary base station accepts. For the QoS flows that the primary base station decides to divert to the secondary base station, the secondary base station can decide to accept some QoS flows and reject some QoS flows. In the secondary base station establishment response message, the secondary base station notifies the primary base station which QoS flows are accepted and which QoS flows are rejected.

[0243] The DRB identifier of the radio bearer established by the secondary base station. In the secondary base station establishment request message, the primary base station decides to establish PDCP on the secondary base station. The primary base station also indicates which QoS flows need to be diverted to the secondary base station. The secondary base station can decide the mapping of QoS flows to DRBs. If the secondary base station decides to use a new mapping, the new mapping uses a new DRB identifier. The secondary base station selects a new DRB identifier from the range of available DRB identifiers based on the identifier information of the DRB available to the secondary base station obtained in step 1101. The identifier of the new DRB corresponding to the QoS flow can be carried in the message of step 1102.

[0244] RRC transparent container: The RRC transparent container may include the configuration information of the secondary base station for the UE. The primary base station forwards the RRC transparent container to the UE in step 1103.

[0245] MDT status information, the status information indicates whether the SN has configured MDT for the UE, for example, indicating that the SN has configured a management-based record-based MDT for the UE, and / or indicating that the SN has configured a management-based timely MDT for the UE. It may also further include more information, for example, the MDT status information may include a unique identifier of the configured MDT, such as TR, TRSR.

[0246] The MDT status information may include the type of MDT that has been configured, such as management-based logging-type MDT and signaling-based logging-type MDT.

[0247] The MDT state information may also include a first timestamp, where the timestamp is the configuration time of the log-type MDT, such as the configuration time of the log-type MDT based on management, where the configuration time is the absolute time of the cell when the auxiliary base station sends the RRC message of the log-type MDT configuration to the UE, such as the format of year-month-day hour-minute-second. The configuration time of the log-type MDT included in the MDT state information is the same as the time included in the RRC message of the log-type MDT configuration sent by the auxiliary base station to the UE.

[0248] The MDT status information may also include the measurement duration of the logging MDT, such as the measurement duration of the management-based logging MDT, which has been configured in the UE and is sent by the secondary base station to the UE. The value of this parameter is the same as the measurement duration (Logging duration) included in the RRC message sent to the UE.

[0249] The MDT status information may further include a second timestamp, which is the remaining time length of the logged MDT. The remaining time length may be the remaining time length of the logged MDT measurement based on signaling and / or the remaining time length of the logged MDT measurement based on management.

[0250] After receiving the message, the MN can save the information in the context of the UE and refer to the information in the subsequent MDT configuration process.

[0251] Step 1103: The primary base station sends an RRC reconfiguration request message to the UE.

[0252] The primary base station does not parse the RRC container sent by the secondary base station, and forwards the RRC container to the UE. The primary base station can add its own configuration information for the UE and send it together with the configuration information of the secondary base station to the UE.

[0253] Step 1104: The UE sends an RRC reconfiguration completion message to the primary base station.

[0254] After the UE is configured successfully, it sends a response message to the primary base station. The response message may include both the response to the primary base station configuration information and the response to the secondary base station configuration information. If necessary, the UE also needs to perform a random access process with the new secondary base station and synchronize with the new secondary base station. After synchronization, the secondary base station can start sending data to the UE.

[0255] Step 1105: The primary base station sends a secondary base station reconfiguration completion message to the secondary base station.

[0256] The primary base station notifies the secondary base station of the information that the configuration of the UE has been successful. Because the UE sends a confirmation message to the primary base station, the primary base station needs to forward the confirmation message to the secondary base station. If the primary base station cannot parse the UE's response to the configuration information of the secondary base station, the primary base station can also forward the UE's response to the configuration information of the secondary base station to the secondary base station in the form of an RRC container.

[0257] Step 1106: The primary base station sends a modification indication message to the core network.

[0258] If the secondary base station establishes a new connection with the core network, the primary base station needs to send a new downlink data receiving address to the core network. The message carries a bearer identifier and a corresponding downlink data receiving address.

[0259] The description of this embodiment ends here. It should be noted that this embodiment omits some known information and known steps.

[0260] Embodiment seven:

[0261] Figure 6 The method shown can also have another implementation mode, namely Fig.12 Embodiment 7 shown. The UE cell reselects to a new cell, the new cell is on a new base station, and the UE requests to restore the RRC connection, or requests RRC reestablishment. When describing sending or receiving messages, the present invention does not specifically distinguish between base stations and cells. When a base station sends or receives a message, it means that the cell on the base station sends or receives a message. Specifically, Fig.12 The specific steps are as follows.

[0262] Step 1201: UE sends an RRC recovery request message to a new base station.

[0263] The message includes the UE's identifier in the old cell, which includes the information of the old base station, the C-RNTI allocated by the new cell, the physical layer identifier PCI of the new cell, and the network-wide unique identifier of the new cell.

[0264] Step 1202: The new base station sends a UE context acquisition request message to the old base station.

[0265] The new base station receives the recovery request message, and knows that the UE context is on the old base station through the information of the old base station contained in the message. The new base station sends a UE context acquisition request message to the old base station.

[0266] The Get UE Context Request message contains the UE Context Identifier. For the RRC recovery process, the UE Context Identifier contains the UE's identifier in the old cell, the temporary C-RNTI of the UE allocated by the new cell (i.e., the cell that received the RRC recovery request), and the PCI of the new cell. The message also contains the cell unique identifier of the new cell, such as CGI, and the reason for RRC recovery.

[0267] Step 1203: The old base station sends a UE context acquisition response message to the new base station.

[0268] The old base station determines whether to send a response message to the new base station. If the UE context can be sent to the new base station, the old base station sends a UE context acquisition response message to the new base station. The message includes the UE context information. If the old base station has configured the UE to perform a record-type MDT, the message may include MDT status information. The MDT status information may include a status indication, such as an indication of whether a signaling-based record-type MDT measurement is configured for the UE. It may also include more information, see the timestamp information described in Embodiment 3.

[0269] If the old base station has not configured the UE for logging-type MDT, one situation is that the UE enters the RRC-inactive mode in the old base station, and then receives the logging-type MDT configuration sent by the core network. At this time, the old base station saves the configuration information of the logging-type MDT in the UE context. When the UE later requests to restore the RRC connection in the new base station, and the old base station receives the Get UE Context Request message sent by the new base station, the old base station calculates the MDT logging duration (MDT logging Duration) contained in the MDT configuration information. The old base station obtains a new logging duration based on the time when the logging-type MDT configuration is received from the core network and the time when the new base station requests the UE context. In other words, the old base station subtracts the time when the old base station saves the MDT measurement in the UE context from the logging-type MDT logging duration configured by the core network. For example, at 10 a.m., the base station receives a record-type MDT configuration from the core network, and the record duration included in the MDT configuration information is 2 hours. At 11 a.m., the old base station receives a UE context request sent by the new base station, and then the old base station modifies the record duration to 1 hour, and includes the new record duration in the MDT configuration information, and sends the MDT configuration information including the new record duration to the new base station through step 1203. The calculation of the new record duration can be several predefined fixed values, for example, the record duration can be one of 10 minutes, 20 minutes, 40 minutes, 60 minutes, 90 minutes, and 120 minutes. After calculation, the old base station finds the closest value as the new record duration.

[0270] The old base station determines whether to continue to save the MDT configuration based on the recording duration and the time saved in the UE context. If the old base station finds that the record-type MDT has timed out, the old base station deletes the MDT configuration information. When the new base station requests to obtain the UE context, the MDT configuration information is not sent to the new base station.

[0271] In the above example, the UE requests to restore the RRC connection at the new base station. The UE can also request to restore the RRC connection at the old base station. If the UE requests to restore the RRC connection at the old base station, when the old base station sends a record-type MDT configuration message to the UE, it is also necessary to recalculate the record duration of the record-type MDT saved in the UE context and send a new record duration to the UE. The calculation method is shown above.

[0272] When the new base station receives the MDT configuration information, it sends the MDT configuration information to the UE through the subsequent RRC record-type MDT configuration message. After the UE receives the record-type MDT configuration information, the UE starts the MDT clock. When the UE enters the RRC idle mode, the UE determines when the clock times out based on the record duration. The clock started on the UE side and the MDT clock recorded by the core network are not started at the same time, and the record duration on the core network side and the record duration obtained by the UE are also different. However, the time when the clock on the core network side and the clock on the UE side time out is the same, that is, the time when the clock stops is the same.

[0273] Step 1204: The new base station sends an RRC recovery response message to the UE.

[0274] Step 1205: The UE sends an RRC recovery complete message to the new base station.

[0275] It should be noted that this method is also used in the RRC re-establishment process, and only the corresponding message needs to be replaced with the message in the RRC re-establishment process.

[0276] Embodiment eight:

[0277] Fig.13 The method shown is another embodiment, namely Fig.13 In the eighth embodiment shown, the UE accesses a separate RAN architecture, which is divided into a central node (CU for short) and a distributed node (DU for short), or divided into a central control node (CU-CP for short), a central user node (CU-UP for short) and a distributed node (DU for short). Fig.13 The separated RAN architecture includes CU-CP, CU-UP and DU. If the separated RAN architecture only includes CU and DU, the functions of CU-CP and CU-UP are implemented on CU. Fig.13The interaction process between CU-CP and CU-UP can be omitted, which belongs to internal information interaction. The control node of RAN knows that the UE has been configured with record-based MDT measurement. The control node notifies other nodes of RAN that the UE has been configured with signaling-based MDT measurement and no longer needs to perform management-based MDT measurement. Or the control node of RAN has configured the UE or base station to perform MDT measurement. The control node tells CU-UP or DU the corresponding MDT configuration information, and CU-UP or DU no longer initiates conflicting MDT measurements. This method avoids the overlap or conflict between MDT measurements directly configured by different nodes. Specifically, Fig.13 The specific steps are as follows.

[0278] Step 1301: CN sends a trace activation request message to CU-CP.

[0279] Step 1302: CU-CP sends an RRC message to the UE. The message carries configuration information of MDT measurement for the UE.

[0280] Step 1303: CU-CP sends a UE context modification request message to DU.

[0281] The message name is only exemplary and may be other names. The message carries MDT status information, which indicates the MDT status of the UE. Specifically, the MDT status information may include one or more of the following statuses:

[0282] -Indicates whether MDT measurements are configured for the UE;

[0283] - Indicates whether logged MDT measurements are configured for the UE;

[0284] - Indicates whether signaling-based MDT measurements are configured for the UE;

[0285] - Indicates whether signaling-based logging-type MDT measurements are configured for the UE;

[0286] - Indicates whether management-based logging-type MDT measurements are configured for the UE;

[0287] - Indicates whether signaling-based timely MDT measurements are configured for the UE;

[0288] - Indicates whether management-based timely MDT measurements are configured for the UE;

[0289] - Indicates whether the MDT configuration has been released;

[0290] -Indication of the RAT type of the configured MDT measurement, for example, eUTRA or new access technology NR.

[0291] DU receives the status information, saves the status information to the context of UE, and decides whether to select the user for management-based MDT measurement based on the status information. For example, if the status information indicates that signaling-based logging-type MDT measurement is configured for the UE, the DU will not select the user for management-based logging-type MDT measurement, so as to avoid the management-based logging-type MDT measurement covering the configuration of the signaling-based logging-type MDT measurement. Or if only one MDT measurement can be configured under the same RAT, and the status information indicates that CU-CP has configured a certain type of MDT measurement for the UE under a certain RAT, when the DU receives a management-based MDT measurement request message sent by the OAM of the same RAT, especially for the same measurement type, the DU will not select the user for management-based MDT measurement, so as to avoid conflicts between management-based MDT measurement and signaling-based MDT measurement, or conflicts between MDT measurement initiated by the DU and MDT measurement initiated by the CU-CP. Or when the UE has been configured with signaling-based MDT measurement, if management-based MDT measurement cannot be performed at the same time, the DU does not select the UE to perform management-based measurement.

[0292] After that, DU sends a response message to CU-CP. Fig.13 Omitted in .

[0293] Step 1304: CU-CP sends a bearer modification request message to CU-UP.

[0294] The message name is only exemplary and may be other names. The message carries MDT status information, which indicates the MDT status of the UE. Specifically, the MDT status information may include one or more of the following statuses:

[0295] -Indicates whether MDT measurements are configured for the UE;

[0296] - Indicates whether logged MDT measurements are configured for the UE;

[0297] - Indicates whether signaling-based MDT measurements are configured for the UE;

[0298] - Indicates whether signaling-based logging-type MDT measurements are configured for the UE;

[0299] - Indicates whether management-based logging-type MDT measurements are configured for the UE;

[0300] - Indicates whether signaling-based timely MDT measurements are configured for the UE;

[0301] - Indicates whether management-based timely MDT measurements are configured for the UE;

[0302] - Indicates whether the MDT configuration has been released;

[0303] -Indication of the RAT type of the configured MDT measurement, for example, eUTRA or new access technology NR.

[0304] CU-UP receives the status information, saves the status information to the context of the UE, and decides whether to select the user for management-based MDT measurement based on the status information. For example, if the status information indicates that a signaling-based logging-type MDT measurement is configured for the UE, CU-UP will not select the user for management-based logging-type MDT measurement, so as to avoid the management-based logging-type MDT measurement covering the configuration of the signaling-based logging-type MDT measurement. Or if only one MDT measurement can be configured under the same RAT, and the status information indicates that under a certain RAT, CU-CP has configured a certain MDT measurement for the UE, when CU-UP receives a management-based MDT measurement request message sent by the OAM of the same RAT, especially for the same measurement type, CU-UP will not select the user for management-based MDT measurement, so as to avoid conflicts between management-based MDT measurements and signaling-based MDT measurements, or conflicts between MDT measurements initiated by CU-UP and MDT measurements initiated by CU-CP. Or when the UE has been configured with signaling-based MDT measurement, if management-based MDT measurement cannot be performed at the same time, the CU-UP does not select the UE to perform management-based measurement.

[0305] After that, CU-UP sends a response message to CU-CP. Fig.13 Omitted in .

[0306] Step 1305, the UE is in idle mode. The process of entering idle mode is the same as the current one and is omitted here. Before the UE enters idle mode, the network configures the UE to perform MDT measurement. When configuring the MDT measurement, the UE may be notified of information that the MDT measurement is a signaling-based MDT measurement or a management-based MDT measurement, or, as in the current mechanism, the UE does not know this information and does not affect the following steps.

[0307] Step 1306: The UE enters the connection mode. During the RRC connection establishment process, the UE sends an indication message indicating the existence of the MDT record to the CU-CP, or the UE indicates to the CU-CP that the MDT has been configured, or the UE indicates to the CU-CP that there is an ongoing MDT measurement.

[0308] Step 1307: CU-CP sends a UE context establishment request message to DU.

[0309] The message name is only exemplary and may be other names. The message carries MDT status information, which indicates the MDT status of the UE. Specifically, the MDT status information may include one or more of the following statuses:

[0310] -Indicates whether MDT measurements are configured for the UE;

[0311] - Indicates whether logged MDT measurements are configured for the UE;

[0312] - Indicates whether signaling-based MDT measurements are configured for the UE;

[0313] - Indicates whether signaling-based logging-type MDT measurements are configured for the UE;

[0314] - Indicates whether management-based logging-type MDT measurements are configured for the UE;

[0315] - Indicates whether signaling-based timely MDT measurements are configured for the UE;

[0316] - Indicates whether management-based timely MDT measurements are configured for the UE;

[0317] - Indicates whether the MDT configuration has been released;

[0318] -Indication of the RAT type of the configured MDT measurement, for example, eUTRA or new access technology NR.

[0319] DU receives the status information, saves the status information to the context of UE, and decides whether to select the user for management-based MDT measurement based on the status information. For example, if the status information indicates that signaling-based logging-type MDT measurement is configured for the UE, the DU will not select the user for management-based logging-type MDT measurement, so as to avoid the management-based logging-type MDT measurement covering the configuration of the signaling-based logging-type MDT measurement. Or if only one MDT measurement can be configured under the same RAT, and the status information indicates that CU-CP has configured a certain type of MDT measurement for the UE under a certain RAT, when the DU receives a management-based MDT measurement request message sent by the OAM of the same RAT, especially for the same measurement type, the DU will not select the user for management-based MDT measurement, so as to avoid conflicts between management-based MDT measurement and signaling-based MDT measurement, or conflicts between MDT measurement initiated by the DU and MDT measurement initiated by the CU-CP. Or when the UE has been configured with signaling-based MDT measurement, if management-based MDT measurement cannot be performed at the same time, the DU does not select the UE to perform management-based measurement.

[0320] After that, DU sends a response message to CU-CP. Fig.13 Omitted in .

[0321] Step 1308: CU-CP sends a bearer establishment request message to CU-UP.

[0322] The CU-CP sends a bearer modification request message to the CU-UP.

[0323] The message name is only exemplary and may be other names. The message carries MDT status information, which indicates the MDT status of the UE. Specifically, the MDT status information may include one or more of the following statuses:

[0324] -Indicates whether MDT measurements are configured for the UE;

[0325] - Indicates whether logged MDT measurements are configured for the UE;

[0326] - Indicates whether signaling-based MDT measurements are configured for the UE;

[0327] - Indicates whether signaling-based logging-type MDT measurements are configured for the UE;

[0328] - Indicates whether management-based logging-type MDT measurements are configured for the UE;

[0329] - Indicates whether signaling-based timely MDT measurements are configured for the UE;

[0330] - Indicates whether management-based timely MDT measurements are configured for the UE;

[0331] - Indicates whether the MDT configuration has been released;

[0332] -Indication of the RAT type of the configured MDT measurement, for example, eUTRA or new access technology NR.

[0333] CU-UP receives the status information, saves the status information to the context of the UE, and decides whether to select the user for management-based MDT measurement based on the status information. For example, if the status information indicates that a signaling-based logging-type MDT measurement is configured for the UE, CU-UP will not select the user for management-based logging-type MDT measurement, so as to avoid the management-based logging-type MDT measurement covering the configuration of the signaling-based logging-type MDT measurement. Or if only one MDT measurement can be configured under the same RAT, and the status information indicates that under a certain RAT, CU-CP has configured a certain MDT measurement for the UE, when CU-UP receives a management-based MDT measurement request message sent by the OAM of the same RAT, especially for the same measurement type, CU-UP will not select the user for management-based MDT measurement, so as to avoid conflicts between management-based MDT measurements and signaling-based MDT measurements, or conflicts between MDT measurements initiated by CU-UP and MDT measurements initiated by CU-CP. Or when the UE has been configured with signaling-based MDT measurement, if management-based MDT measurement cannot be performed at the same time, the CU-UP does not select the UE to perform management-based measurement.

[0334] After that, CU-UP sends a response message to CU-CP. Fig.13 Omitted in .

[0335] It should be noted that the MDT state can indicate the RAT type indication of the configured MDT measurement, which is also applicable to the previous embodiments, such as Embodiments 1 to 7. If only one MDT measurement can be configured under the same RAT, it is determined whether the UE can be selected for MDT measurement based on the RAT information contained in the MDT state.

[0336] Embodiment nine:

[0337] Fig.14 The method shown is another embodiment, namely Fig.14 In the ninth embodiment shown, the UE accesses a separate RAN architecture, which is divided into a central node (CU for short) and a distributed node (DU for short), or divided into a central control node (CU-CP for short), a central user node (CU-UP for short) and a distributed node (DU for short). Fig.14 The separated RAN architecture includes CU-CP, CU-UP and DU. If the separated RAN architecture only includes CU and DU, the functions of CU-CP and CU-UP are implemented on CU. Fig.14The interaction process between CU-CP and CU-UP can be omitted, which belongs to the internal information interaction. The core network configures the UE to perform signaling-based MDT measurement. If the RAN node is configured with management-based MDT measurement, the CU-CP can reject the management-based MDT measurement. Through the method of the present invention, it can be avoided that the MDT configuration of the DU covers the MDT configuration of the core network or covers the MDT configuration of the CU-CP, it can be avoided that the MDT configuration of the DU conflicts with the MDT configuration of the CU-CP, and it can be avoided that the MDT configuration of the DU exceeds the capability of the UE. Specifically, Fig.14 The specific steps are as follows.

[0338] Step 1401: DU sends a message related to MDT configuration to CU-CP.

[0339] OAM on DU initiates management-based MDT measurement. Based on the configuration information of MDT measurement, DU selects a certain user for MDT measurement. For example, DU will select UE that is authorized to perform MDT measurement and is within a certain range to perform MDT measurement. For some timely measurements, such as M5, or record-type measurements, the measurement must also be performed on CU-UP, or the record-type measurement must be performed on UE. DU needs to send the MDT configuration information to CU-UP or UE through CU-CP. DU sends a message to CU-CP. For example, DU sends a message that UE context modification is required, or sends an RRC message transmission, or DU sends a trace activation message to CU-CP.

[0340] The message carries one of the following information:

[0341] -RRC message to be sent to the UE, or a container containing an RRC message. The RRC message contains the measurement configuration for the UE.

[0342] -MDT information, such as the MDT trace ID, or the MDT mode, such as timely MDT measurement or recorded MDT measurement, and may also include the MDT measurement type, such as M1, M4, etc.

[0343] -Indication information of MDT configuration, for example, indicating that the DU has initiated management-based MDT configuration.

[0344] After receiving the message, CU-CP determines whether there is a conflict with the MDT measurement configured by CU-CP through the MDT information contained in the message, such as the indication information of the MDT configuration or the measurement type of the MDT, or determines whether the management-based MDT covers the signaling-based MDT configuration, or determines whether the UE is capable of performing the configured measurement. For example, based on the report of the UE, CU-CP can know whether the UE has been configured with the record-type MDT measurement. Then, when CU-CP receives the message of step 1401, it can determine whether the management-based record-type measurement configured by DU will cover the record-type MDT that has been configured to the UE. If there is such a risk, CU-CP can reject the MDT measurement initiated by DU and send the message of step 1404 to DU. If CU-CP determines that there is no conflict and the UE is capable of performing the MDT measurement, CU-CP sends the MDT measurement configuration message to UE, and if necessary, the UE sends a successful response message to DU. If there is a conflict, or the UE is not capable enough, CU-CP does not configure the UE or does not configure CU-UP to perform MDT measurement, and CU-CP performs the message of step 1404.

[0345] Step 1402: The CU-CP sends a message related to MDT configuration to the CU-UP or to the UE.

[0346] If the CU-UP needs to perform MDT measurement, the CU-CP sends a trace activation request to the CU-UP. The trace activation request message includes the MDT identifier Trace ID, the MDT mode, such as timely MDT measurement, and the MDT measurement type, such as M5, M4, etc. If the UE needs to perform MDT measurement, the CU-CP sends an RRC message carrying the configuration information of the MDT measurement to the UE.

[0347] Step 1403: DU sends a Cell Traffic Trace message to CU-CP.

[0348] After DU selects a user for management-based MDT measurement, DU needs to send a Cell Traffic Trace message to CU-CP. The purpose of the message is to let CU-CP send a Cell Traffic Trace message to the core network. The message carries the MDT identifier Trace ID, MDT mode, MDT measurement type, etc.

[0349] It should be noted that the messages of step 1401 and step 1402 may not occur, and the message of step 1403 may be sent without the messages of step 1401 and 1402.

[0350] Step 1404, CU-CP sends a trace failure message to DU.

[0351] In order to avoid management-based MDT measurement, which covers signaling-based MDT measurement, or to avoid conflict between CU-CP and DU configuration, or DU's MDT measurement configuration exceeds UE's capability, CU-CP can reject management-based MDT measurement initiated by DU. CU-CP sends a message to DU, for example, the message can be a UE context modification failure message, or a trace failure message, which indicates that the reason for the failure is that signaling-based MDT measurement has been configured, or that the UE capability is insufficient or the MDT capability is insufficient, or that the configuration initiated by DU conflicts with the configuration of CU-CP. After receiving the message, DU no longer performs the corresponding MDT measurement.

[0352] The above process is also applicable to the MDT measurement initiated by the CU-UP. It only needs to replace the interaction process between the DU and the CU-CP with the interaction process between the CU-UP and the CU-CP, which is omitted here.

[0353] Embodiment ten:

[0354] Fig.15 The method shown is another embodiment, namely Fig.15 Embodiment 10 is shown. Fig.15 The figure shows that under dual connection, both the master base station MN and the auxiliary base station SN can configure the UE to perform MDT measurement. The master base station can perform signaling-based and management-based MDT configuration, and the auxiliary base station can perform management-based MDT configuration. How to ensure that the configurations of MN and SN do not conflict with each other is described in this embodiment. Through the method of the present invention, the MDT configuration of SN can be avoided, covering the MDT configuration of MN, avoiding conflicts with the MDT configuration of MN, and avoiding the MDT configuration exceeding the capability of UE. Specifically, Fig.15 The specific steps are as follows.

[0355] Step 1501: SN sends a message related to MDT configuration to MN.

[0356] The OAM on the SN initiates a management-based MDT measurement. According to the configuration information of the MDT measurement, the SN selects a certain user to perform the MDT measurement. For example, the SN will select a UE that is authorized to perform MDT measurement and is within a certain range to perform MDT measurement. For some timely measurements, such as M1, or record-type measurements, the measurement is performed on the UE side, and the SN needs to configure the UE to perform the corresponding measurement. First, the SN needs to send an RRC message containing the MDT configuration to the user. If the SN has established an RRC signaling connection between the SN and the UE, such as SRB3, the MDT configuration can be sent to the UE through SRB3. If SRB3 is not established, or in order to let the MN know that the SN has configured management-based MDT measurement, the SN sends a message to the MN. For example, the SN sends an SN modification required message, or sends an RRC message transmission, or the SN sends a trace (Trace) activation message to the MN.

[0357] The message carries one of the following information:

[0358] -RRC message to be sent to the UE, or a container containing an RRC message. The RRC message contains the measurement configuration for the UE;

[0359] - MDT trace ID, MDT mode, such as timely MDT measurement or recorded MDT measurement, and MDT measurement type, such as M1, M4, etc.

[0360] -Indication information of MDT configuration, for example, indicating that the SN has initiated management-based MDT configuration.

[0361] After receiving the message, the MN determines whether there is a conflict with the MDT measurement configured by the MN through the MDT information contained in the message, such as the indication information of the MDT configuration or the measurement type of the MDT, or determines whether the management-based MDT covers the signaling-based MDT configuration, or

[0362] The MN determines whether the UE is capable of performing the configured measurement. If there is no conflict, the UE is capable of performing the MDT measurement. The MN sends a measurement configuration message to the UE and, if necessary, sends a corresponding success message to the SN. If there is a conflict or the UE is not capable enough, the MN sends the message of step 1503.

[0363] Step 1502: SN sends a Cell Traffic Trace message to MN.

[0364] After SN selects a user for management-based MDT measurement, SN needs to send a Cell Traffic Trace message to MN. The purpose of the message is to let MN send a Cell Traffic Trace message to the core network. The message carries the MDT trace ID, MDT mode, MDT measurement type, etc.

[0365] It should be noted that the message of step 1501 may not be sent, and the message of step 1502 may be sent without the message of step 1501.

[0366] The MN receives the message of step 1502, and determines whether there is a conflict with the MDT measurement configured by the MN through the MDT information contained in the message, such as the measurement type of the MDT, or determines whether the management-based MDT covers the signaling-based MDT configuration, or determines whether the UE is capable of performing the configured measurement. If there is no conflict, the UE is capable of performing the MDT measurement, and the MN sends a measurement configuration message to the UE, and if necessary, sends a successful response message to the SN. If there is a conflict, or the UE is not capable enough, the MN performs the operation of step 1503.

[0367] Step 1503: MN sends a message to SN.

[0368] In order to avoid management-based MDT measurement, which covers signaling-based MDT measurement, or to avoid configuration conflicts between SN and MN, or MDT measurement exceeds the capability of UE, MN can reject management-based MDT measurement initiated by SN, and MN sends a message to SN, for example, the message can be RRC transmission failure message, or SN configuration failure message, or trace failure message, the message indicates that the reason for the failure is that signaling-based MDT measurement has been configured, or indicates that UE capability is insufficient or MDT capability is insufficient. After receiving the message, SN no longer performs the corresponding MDT measurement, and / or sends a message to UE via SRB3 to delete the MDT measurement configured on the UE side.

[0369] Fig. 9 The structure block diagram of an access network node performing MDT measurement according to an exemplary embodiment of the present invention is schematically shown. Fig. 9 As shown, the access network node receives MDT configuration parameters and / or MDT status information, and decides whether to configure management-based logging-type MDT measurement for the UE based on the MDT status information. The access network node can also send the MDT status information to the core network or another access network node.

[0370] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A method performed by a second node in a communication system, characterized in that: include: The second node receives the minimization of drive tests (MDT) state information sent by the first node; Based on the MDT state information, the second node determines whether to configure management-based logging-type MDT measurement, signaling-based logging-type MDT measurement, or management-based MDT measurement for the user equipment UE, The MDT status information includes at least one of the following: Information indicating that MDT measurement is configured for the UE, information indicating that logged-type MDT measurement is configured for the UE, information indicating that signaling-based MDT measurement is configured for the UE, information indicating that signaling-based logged-type MDT measurement is configured for the UE, information indicating that management-based logged-type MDT measurement is configured for the UE, information indicating whether the MDT configuration has been released, and information indicating the RAT type of the configured MDT measurement.

2. The method according to claim 1, characterized in that The first node includes: at least one of a base station control node, a base station distribution node, a main base station, an auxiliary base station, and a core network node.

3. The method according to claim 1, characterized in that The second node includes: at least one of a base station control node, a base station distribution node, a main base station, and an auxiliary base station.

4. The method according to claim 1, characterized in that The MDT status information also includes at least one of the following: The unique identifier of the MDT, the type of the configured MDT, the configuration time of the logging-type MDT, the measurement time length of the logging-type MDT, and the remaining time length of the logging-type MDT.

5. The method according to claim 1, characterized in that Also includes: The second node sends a failure message to the first node.

6. The method according to any one of claims 1 to 5, characterized in that: Also includes: In case that management-based logged-type MDT measurement is to be configured for the UE, an MDT activation request message is received from the third node.

7. The method according to claim 6, characterized in that The third node includes an operation and maintenance node.

8. The method according to any one of claims 1 to 5, characterized in that: Also includes: In case that signaling-based logged-type MDT measurement is to be configured for the UE, an MDT activation request message is received from the first node.

9. A method performed by a first node in a communication system, characterized in that: include: The first node determines MDT state information; The first node sends MDT status information to the second node, where the MDT status information is used by the second node to determine whether to configure management-based logging-type MDT measurement, signaling-based logging-type MDT measurement, or management-based MDT measurement for the user equipment UE. The MDT status information includes at least one of the following: Information indicating that MDT measurement is configured for the UE, information indicating that logged-type MDT measurement is configured for the UE, information indicating that signaling-based MDT measurement is configured for the UE, information indicating that signaling-based logged-type MDT measurement is configured for the UE, information indicating that management-based logged-type MDT measurement is configured for the UE, information indicating whether the MDT configuration has been released, and information indicating the RAT type of the configured MDT measurement.

10. The method according to claim 9, characterized in that The first node includes: at least one of a base station control node, a base station distribution node, a main base station, an auxiliary base station, and a core network node.

11. The method according to claim 9, characterized in that The second node includes: at least one of a base station control node, a base station distribution node, a main base station, and an auxiliary base station.

12. The method according to claim 9, characterized in that The MDT status information also includes at least one of the following: The unique identifier of the MDT, the type of the configured MDT, the configuration time of the logging-type MDT, the measurement time length of the logging-type MDT, and the remaining time length of the logging-type MDT.

13. The method according to claim 9, characterized in that Also includes: The first node receives a failure message from the second node.

14. The method according to any one of claims 9 to 13, characterized in that: In case that management-based logged-type MDT measurements are to be configured for the UE, the MDT activation request message is sent by the third node to the second node.

15. The method according to claim 14, characterized in that The third node includes an operation and maintenance node.

16. The method according to any one of claims 9 to 13, characterized in that: Also includes: In case that the signaling-based logged MDT measurement is to be configured for the UE, an MDT activation request message is sent to the second node.

17. A method performed by a base station in a communication system, characterized in that: include: receiving a context establishment request message from a core network node, wherein the context establishment request message includes information related to MDT measurement; Sending MDT configuration information to the UE; Sending a UE context release request to a core network node, wherein the UE context release request includes MDT state information; Receive a UE context release command message from the core network node, The MDT status information includes at least one of the following: Information indicating that MDT measurement is configured for the UE, information indicating that logged-type MDT measurement is configured for the UE, information indicating that signaling-based MDT measurement is configured for the UE, information indicating that signaling-based logged-type MDT measurement is configured for the UE, information indicating that management-based logged-type MDT measurement is configured for the UE, information indicating whether the MDT configuration has been released, and information indicating the RAT type of the configured MDT measurement.

18. The method according to claim 17, characterized in that The MDT configuration information includes at least one of the following: MDT measurement identifier, TCE identifier, TRSR, MDT measurement area configuration, network timestamp, MDT measurement time length, and information indicating whether the reporting type is periodic or event-triggered.

19. The method according to claim 17, characterized in that The MDT status information also includes at least one of the following: The unique identifier of the MDT, the type of the configured MDT, the configuration time of the logging-type MDT, the measurement time length of the logging-type MDT, and the remaining time length of the logging-type MDT.

20. A method executed by a core network node in a communication system, characterized in that: include: Sending a context establishment request message to a base station, where the context establishment request message includes information related to MDT measurement; receiving a UE context release request from a base station, wherein the UE context release request includes MDT state information; Send a UE context release command message to the base station, The MDT status information includes at least one of the following: Information indicating that MDT measurement is configured for the UE, information indicating that logged-type MDT measurement is configured for the UE, information indicating that signaling-based MDT measurement is configured for the UE, information indicating that signaling-based logged-type MDT measurement is configured for the UE, information indicating that management-based logged-type MDT measurement is configured for the UE, information indicating whether the MDT configuration has been released, and information indicating the RAT type of the configured MDT measurement.

21. The method according to claim 20, characterized in that The MDT configuration information includes at least one of the following: MDT measurement identifier, TCE identifier, TRSR, MDT measurement area configuration, network timestamp, MDT measurement time length, and information indicating whether the reporting type is periodic or event-triggered.

22. The method according to claim 20, characterized in that The MDT status information also includes at least one of the following: The unique identifier of the MDT, the type of the configured MDT, the configuration time of the logging-type MDT, the measurement time length of the logging-type MDT, and the remaining time length of the logging-type MDT.

23. A second node, characterized in that: include: Transceiver, used to send and receive signals, A processor is coupled to the transceiver and configured to execute the method according to any one of claims 1 to 8.

24. A first node, characterized in that: include: Transceiver, used to send and receive signals, A processor is coupled to the transceiver and configured to execute the method according to any one of claims 9 to 16.

25. A base station, characterized in that: include: Transceiver, used to send and receive signals, A processor is coupled to the transceiver and configured to execute the method according to any one of claims 17 to 19.

26. A core network node, characterized in that: include: Transceiver, used to send and receive signals, A processor coupled to the transceiver and configured to execute the method according to any one of claims 20-22.

Images