MDT reporting method, communication equipment, device and storage medium

Abstract

The invention provides an MDT reporting method, communication equipment, a device and a storage medium. The method comprises the steps that first communication equipment receives MDT configuration or indication information sent by second communication equipment; the MDT configuration comprises area range information, the area range information comprises slice information, and the indication information is used for indicating the first communication equipment to carry the slice information when executing MDT reporting; and reporting MDT measurement information based on the MDT configuration or the indication information, wherein the MDT measurement information carries slice information. According to the MDT reporting method, the communication equipment, the device and the storage medium provided by the invention, a network can identify a real slice deployment condition, so that optimization of slice deployment is realized.

Description

Technical Field

[0001] This application relates to the field of wireless communication technology, and in particular to an MDT reporting method, communication equipment, apparatus, and storage medium. Background Technology

[0002] In New Radio (NR) systems, networks can implement network slicing by scheduling and providing different configurations, with different slices corresponding to different needs. A key technical problem to be solved is how to enable the network to identify the actual slice deployment status and thus optimize slice deployment through Minimization of Drive Tests (MDT) reporting. Summary of the Invention

[0003] This application provides an MDT reporting method, communication device, apparatus, and storage medium to enable the network to identify the actual slice deployment situation and thereby optimize slice deployment.

[0004] In a first aspect, this application provides an MDT reporting method, applied to a first communication device, comprising:

[0005] Receive MDT configuration or indication information sent by the second communication device; the MDT configuration includes area range information, the area range information includes slice information, and the indication information is used to instruct the first communication device to carry slice information when performing MDT reporting;

[0006] MDT measurement information is reported based on MDT configuration or indication information, and the MDT measurement information carries slice information.

[0007] In some embodiments, the region extent information is newly defined region extent information for the slice; or...

[0008] The area scope information is existing area scope information.

[0009] In some embodiments, the MDT measurement information also carries one or more of the following:

[0010] Supports measurement results for cells or beams in a specified slice;

[0011] Measurement information of the slices.

[0012] In some embodiments, the measurement information of the slice includes one or more of the following:

[0013] Average throughput per slice;

[0014] Data volume per slice;

[0015] Packet loss rate per slice;

[0016] Packet latency per slice;

[0017] Zero-resource cells per slice.

[0018] In some embodiments, the MDT configuration includes one or more of the following measurement trigger conditions:

[0019] Layer 1 event triggered;

[0020] Periodic triggering;

[0021] Triggered upon leaving the coverage area;

[0022] Slice trigger detected.

[0023] In some embodiments, the MDT configuration includes one or more of the following measurement parameters:

[0024] Supports measurement results for cells or beams in a specified slice;

[0025] Measurement information of the slices.

[0026] In some embodiments, the slice information includes one or more of the following:

[0027] Single-network slice selection auxiliary information S-NSSAI;

[0028] Network slice access layer group NSAG identifier;

[0029] List of NSAG slicing supports.

[0030] Secondly, this application also provides an MDT reporting method, applied to a second communication device, comprising:

[0031] Send MDT configuration or indication information to the first communication device; the MDT configuration includes area range information, the area range information includes slice information, and the indication information is used to instruct the first communication device to carry slice information when performing MDT reporting;

[0032] Receive MDT measurement information reported by the first communication device. The MDT measurement information carries slice information.

[0033] In some embodiments, the region extent information is newly defined region extent information for the slice; or...

[0034] The area scope information is existing area scope information.

[0035] In some embodiments, the MDT measurement information also carries one or more of the following:

[0036] Supports measurement results for cells or beams in a specified slice;

[0037] Measurement information of the slices.

[0038] In some embodiments, the measurement information of the slice includes one or more of the following:

[0039] Average throughput per slice;

[0040] Data volume per slice;

[0041] Packet loss rate per slice;

[0042] Packet latency per slice;

[0043] Zero-resource cells per slice.

[0044] In some embodiments, the MDT configuration includes one or more of the following measurement trigger conditions:

[0045] Layer 1 event triggered;

[0046] Periodic triggering;

[0047] Triggered upon leaving the coverage area;

[0048] Slice trigger detected.

[0049] In some embodiments, the MDT configuration includes one or more of the following measurement parameters:

[0050] Supports measurement results for cells or beams in a specified slice;

[0051] Measurement information of the slices.

[0052] In some embodiments, the slice information includes one or more of the following:

[0053] Single-network slice selection auxiliary information S-NSSAI;

[0054] Network slice access layer group NSAG identifier;

[0055] List of NSAG slicing supports.

[0056] Thirdly, this application also provides a first communication device, including a memory, a transceiver, and a processor;

[0057] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0058] Receive MDT configuration or indication information sent by the second communication device; the MDT configuration includes area range information, the area range information includes slice information, and the indication information is used to instruct the first communication device to carry slice information when performing MDT reporting;

[0059] MDT measurement information is reported based on MDT configuration or indication information, and the MDT measurement information carries slice information.

[0060] In some embodiments, the region extent information is newly defined region extent information for the slice; or...

[0061] The area scope information is existing area scope information.

[0062] In some embodiments, the MDT measurement information also carries one or more of the following:

[0063] Supports measurement results for cells or beams in a specified slice;

[0064] Measurement information of the slices.

[0065] In some embodiments, the measurement information of the slice includes one or more of the following:

[0066] Average throughput per slice;

[0067] Data volume per slice;

[0068] Packet loss rate per slice;

[0069] Packet latency per slice;

[0070] Zero-resource cells per slice.

[0071] In some embodiments, the MDT configuration includes one or more of the following measurement trigger conditions:

[0072] Layer 1 event triggered;

[0073] Periodic triggering;

[0074] Triggered upon leaving the coverage area;

[0075] Slice trigger detected.

[0076] In some embodiments, the MDT configuration includes one or more of the following measurement parameters:

[0077] Supports measurement results for cells or beams in a specified slice;

[0078] Measurement information of the slices.

[0079] In some embodiments, the slice information includes one or more of the following:

[0080] Single-network slice selection auxiliary information S-NSSAI;

[0081] Network slice access layer group NSAG identifier;

[0082] List of NSAG slicing supports.

[0083] Fourthly, this application also provides a second communication device, including a memory, a transceiver, and a processor;

[0084] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations:

[0085] Send MDT configuration or indication information to the first communication device; the MDT configuration includes area range information, the area range information includes slice information, and the indication information is used to instruct the first communication device to carry slice information when performing MDT reporting;

[0086] Receive MDT measurement information reported by the first communication device. The MDT measurement information carries slice information.

[0087] In some embodiments, the region extent information is newly defined region extent information for the slice; or...

[0088] The area scope information is existing area scope information.

[0089] In some embodiments, the MDT measurement information also carries one or more of the following:

[0090] Supports measurement results for cells or beams in a specified slice;

[0091] Measurement information of the slices.

[0092] In some embodiments, the measurement information of the slice includes one or more of the following:

[0093] Average throughput per slice;

[0094] Data volume per slice;

[0095] Packet loss rate per slice;

[0096] Packet latency per slice;

[0097] Zero-resource cells per slice.

[0098] In some embodiments, the MDT configuration includes one or more of the following measurement trigger conditions:

[0099] Layer 1 event triggered;

[0100] Periodic triggering;

[0101] Triggered upon leaving the coverage area;

[0102] Slice trigger detected.

[0103] In some embodiments, the MDT configuration includes one or more of the following measurement parameters:

[0104] Supports measurement results for cells or beams in a specified slice;

[0105] Measurement information of the slices.

[0106] In some embodiments, the slice information includes one or more of the following:

[0107] Single-network slice selection auxiliary information S-NSSAI;

[0108] Network slice access layer group NSAG identifier;

[0109] List of NSAG slicing supports.

[0110] Fifthly, this application also provides an MDT reporting device, comprising:

[0111] The first receiving unit is used to receive MDT configuration or indication information sent by the second communication device; the MDT configuration includes area range information, the area range information includes slice information, and the indication information is used to instruct the first communication device to carry slice information when performing MDT reporting;

[0112] The reporting unit is used to report MDT measurement information based on MDT configuration or indication information. The MDT measurement information carries slice information.

[0113] In some embodiments, the region extent information is newly defined region extent information for the slice; or...

[0114] The area scope information is existing area scope information.

[0115] In some embodiments, the MDT measurement information also carries one or more of the following:

[0116] Supports measurement results for cells or beams in a specified slice;

[0117] Measurement information of the slices.

[0118] In some embodiments, the measurement information of the slice includes one or more of the following:

[0119] Average throughput per slice;

[0120] Data volume per slice;

[0121] Packet loss rate per slice;

[0122] Packet latency per slice;

[0123] Zero-resource cells per slice.

[0124] In some embodiments, the MDT configuration includes one or more of the following measurement trigger conditions:

[0125] Layer 1 event triggered;

[0126] Periodic triggering;

[0127] Triggered upon leaving the coverage area;

[0128] Slice trigger detected.

[0129] In some embodiments, the MDT configuration includes one or more of the following measurement parameters:

[0130] Supports measurement results for cells or beams in a specified slice;

[0131] Measurement information of the slices.

[0132] In some embodiments, the slice information includes one or more of the following:

[0133] Single-network slice selection auxiliary information S-NSSAI;

[0134] Network slice access layer group NSAG identifier;

[0135] List of NSAG slicing supports.

[0136] Sixthly, this application also provides an MDT reporting device, comprising:

[0137] The sending unit is used to send MDT configuration or indication information to the first communication device; the MDT configuration includes area range information, the area range information includes slice information, and the indication information is used to instruct the first communication device to carry slice information when performing MDT reporting.

[0138] The second receiving unit is used to receive the MDT measurement information reported by the first communication device, which carries slice information.

[0139] In some embodiments, the region extent information is newly defined region extent information for the slice; or...

[0140] The area scope information is existing area scope information.

[0141] In some embodiments, the MDT measurement information also carries one or more of the following:

[0142] Supports measurement results for cells or beams in a specified slice;

[0143] Measurement information of the slices.

[0144] In some embodiments, the measurement information of the slice includes one or more of the following:

[0145] Average throughput per slice;

[0146] Data volume per slice;

[0147] Packet loss rate per slice;

[0148] Packet latency per slice;

[0149] Zero-resource cells per slice.

[0150] In some embodiments, the MDT configuration includes one or more of the following measurement trigger conditions:

[0151] Layer 1 event triggered;

[0152] Periodic triggering;

[0153] Triggered upon leaving the coverage area;

[0154] Slice trigger detected.

[0155] In some embodiments, the MDT configuration includes one or more of the following measurement parameters:

[0156] Supports measurement results for cells or beams in a specified slice;

[0157] Measurement information of the slices.

[0158] In some embodiments, the slice information includes one or more of the following:

[0159] Single-network slice selection auxiliary information S-NSSAI;

[0160] Network slice access layer group NSAG identifier;

[0161] List of NSAG slicing supports.

[0162] In a seventh aspect, this application also provides a non-transient readable storage medium storing a computer program for causing a processor to execute the MDT reporting method described in the first aspect above, or to execute the MDT reporting method described in the second aspect above.

[0163] Eighthly, this application also provides a communication device, wherein the communication device stores a computer program, the computer program being used to cause the communication device to execute the MDT reporting method described in the first aspect above, or to execute the MDT reporting method described in the second aspect above.

[0164] Ninthly, this application also provides a processor-readable storage medium storing a computer program for causing a processor to execute the MDT reporting method described in the first aspect above, or to execute the MDT reporting method described in the second aspect above.

[0165] In a tenth aspect, this application also provides a chip product, wherein the chip product stores a computer program, the computer program being used to cause the chip product to execute the MDT reporting method described in the first aspect above, or to execute the MDT reporting method described in the second aspect above.

[0166] The MDT reporting method, communication device, apparatus, and storage medium provided in this application send enhanced MDT configuration or indication information to a first communication device through a second communication device. After receiving the enhanced MDT configuration or indication information, the first communication device can carry slice information when reporting MDT measurement information based on the enhanced MDT configuration or indication information, so that the network can identify the actual slice deployment situation and thus optimize the slice deployment. Attached Figure Description

[0167] To more clearly illustrate the technical solutions in the embodiments or related technologies of this application, the accompanying drawings used in the description of the embodiments or related technologies will be briefly introduced below. Obviously, the accompanying drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0168] Figure 1 This is one of the flowcharts illustrating the MDT reporting method provided in the embodiments of this application;

[0169] Figure 2 The second flowchart illustrates the MDT reporting method provided in this application embodiment.

[0170] Figure 3 This is a schematic diagram of the structure of the first communication device provided in an embodiment of this application;

[0171] Figure 4 This is a schematic diagram of the structure of the second communication device provided in an embodiment of this application;

[0172] Figure 5 This is one of the structural schematic diagrams of the MDT reporting device provided in the embodiments of this application;

[0173] Figure 6 This is a second schematic diagram of the structure of the MDT reporting device provided in the embodiments of this application. Detailed Implementation

[0174] In the embodiments of this application, the term "and / or" describes the relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following associated objects have an "or" relationship.

[0175] In the embodiments of this application, the term "multiple" refers to two or more, and other quantifiers are similar.

[0176] In the embodiments of this application, the terms "first," "second," etc., are used to distinguish similar objects, and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, and the number of objects is not limited; for example, the first object can be one or more.

[0177] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0178] To facilitate a clearer understanding of the technical solutions of the various embodiments of this application, some technical content related to the various embodiments of this application will be introduced first.

[0179] 1. Network slicing

[0180] In NR, the network can implement network slicing by scheduling and providing different configurations, with different slices corresponding to different needs. Services in different slices are processed through different Protocol Data Unit (PDU) sessions; that is, each slice corresponds to one PDU session. Each slice is identified by Single Network Slice Selection Assistance Information (S-NSSAI), where each S-NSSAI can consist of two parts:

[0181] Mandatory (required) SST (Slice / Service Type): Identifies the type of slice;

[0182] Optional SD (Slice Differentiator): Further differentiates slices with the same SST.

[0183] The network can support hundreds of slices, but a single terminal (or User Equipment, UE) can only support a maximum of 8 slices at the same time.

[0184] When a UE requests network access, it can include the requested slice information in the Radio Resource Control (RRC) Setup Complete message. The network will then send feedback to the UE in subsequent downlink messages regarding the slices that are allowed or denied.

[0185] It is generally believed that slice deployment is per Tracking Area (TA), meaning that cells within a TA support the same slice(s). Enhancements in related technologies allow for a specific slice's service area to differ from the TA defined on the Radio Access Network (RAN) side. Specifically, if a cell is within a TA but not within the slice's service area, the cell can indicate its support for the slice by defining that it provides zero resources for that slice; the cell will not use any of the slice's resources. Neighboring nodes also interactively configure cells with zero resources for slices for UE mobility decision reference.

[0186] 2. MDT

[0187] 2.1 Immediate MDT

[0188] The measurements supported by Immediate MDT mainly include the following parts, some of which are measured by the UE and some by the base station:

[0189] (1) M1: Downlink signal measurement results of the serving cell and its intra-frequency / inter-frequency / inter-RAT neighboring cells. For NR cells, this includes cell-level or beam-level measurement results.

[0190] The M1 measurement reporting content is related to the UE. The content reported by the UE includes:

[0191] Radio Resource Management (RRM) measurement results (including measurement results related to the serving cell and neighboring cells);

[0192] Geographic location information;

[0193] Bluetooth (BT) or Wireless Local Area Network (WLAN) measurement information;

[0194] Sensor-related information includes the following: air pressure information obtained by the internal sensors of the terminal, terminal motion direction information, and terminal speed direction information.

[0195] (2) M2: UE performs power margin measurement;

[0196] (3) M3: void (Long Term Evolution (LTE) defines it as the received interference power measured by the base station, but there is no such definition in NR RAN1);

[0197] (4) M4: Data volume measurement, divided into downlink (DL) and uplink (UL), is per DRB (Data Radio Bearer) per UE;

[0198] (5) M5: UE average throughput measurement, divided into DL and UL. For DL ​​it is per UE, and for UL it is per DRB per UE and per UE, which are measured by the base station;

[0199] (6)M6: Packet delay measurement, divided into DL and UL, is per DRB per UE;

[0200] (7)M7: Packet loss rate measurement, divided into DL and UL, is per DRB per UE;

[0201] (8) M8: The UE performs Received Signal Strength Indication (RSSI) measurement (for BT / WLAN measurement);

[0202] (9)M9: UE performs round-trip time (RTT) measurement (for WLAN measurement).

[0203] Immediate MDT measurement reporting trigger conditions:

[0204] For M1:

[0205] a. Event-triggered measurement reporting, triggered according to events A1, A2, A3, A4, A5, A6, B1, and B2 currently configured in the RRM.

[0206] b. Periodic triggering, A2 event triggering, or A2 event triggering periodic measurement reporting, triggered according to the measurement configuration specified by MDT.

[0207] For M2: Receive Power Headroom Report (PHR) based on the current RRM configuration.

[0208] For M4 to M9: The measurement and collection period has ended.

[0209] 2.2 Logged MDT

[0210] Logged MDT supports the following measurements:

[0211] (1) Trace and absolute timestamp configuration parameters.

[0212] (2) Relative timestamp information.

[0213] (3) UE location information.

[0214] (4) Record the identity (ID) information of the serving cell associated with the data;

[0215] (5) Record the service cell measurement results associated with the data, specifically including:

[0216] Service community-level measurement results;

[0217] The identification information of the beam with the best signal quality in the serving cell;

[0218] Beam-level measurement results of the beam with the best signal quality in the serving cell;

[0219] The number of beams with good signal quality serving the cell.

[0220] (6) Neighbor cell measurement results, including: NR neighbor cell measurement results and Evolved Universal Terrestrial Radio Access Network (E-UTRAN) neighbor cell measurement results.

[0221] The neighbor cell measurement results have been adapted to enhance interoperability between NR and LTE. For NR neighbor cell measurement results, the data also includes the number of beams with good neighbor cell signal quality.

[0222] (7) Any Cell Selection Instruction.

[0223] Logged MDT measurement event type configuration information:

[0224] (1) Periodic Logged MDT measurement event type.

[0225] (2) Event-triggered Logged MDT measurement event types, currently including two event-triggered types:

[0226] The Out of Coverage (OOC) event is triggered;

[0227] The Layer 1 (L1) event is triggered when the signal quality of the serving cell is below a certain threshold.

[0228] 2.3 Configuration Scope of Immediate MDT and Logged MDT

[0229] The configuration scope of Immediate MDT and Logged MDT includes:

[0230] (1) Cell based: This means that the UE only performs measurements in some cells.

[0231] (2) TAI (Tracking Area Identity) based: This means that the UE only performs measurements within some TAIs.

[0232] (3) PLMN (Public Land Mobile Network) based: refers to the UE only performing measurements within some PLMNs.

[0233] (4) NPN (Non-Public Network) related based, including PNI-NPN (Public Network Integrated Non-Public Network) based MDT, SNPN (Stand-alone Non-Public Network) Cell based MDT, SNPN TAI based MDT, and SNPN based MDT.

[0234] In related technologies, MDT (Multi-Level Reporting) does not support any slice-related content, causing the network to be unable to identify the actual slice deployment status. This leads to service interruptions and performance impact when the UE encounters slice vulnerabilities or lacks sufficient slice resources. Therefore, this application provides an MDT reporting method that enables the network to identify the actual slice deployment status, thereby optimizing slice deployment.

[0235] Figure 1This is one of the flowcharts illustrating the MDT reporting method provided in the embodiments of this application. The method is applied to a first communication device, such as... Figure 1 As shown, the method includes the following steps:

[0236] Step 100: Receive MDT configuration or indication information sent by the second communication device; the MDT configuration includes area range information, the area range information includes slice information, and the indication information is used to instruct the first communication device to carry slice information when performing MDT reporting.

[0237] Specifically, the first communication device is a terminal or access network device (e.g., a base station).

[0238] When the first communication device is a terminal and the second communication device is an access network device, the terminal receives MDT configuration or indication information sent by the access network device. The MDT configuration includes area scope information (i.e., the concept remains consistent throughout the text and will not be repeated hereafter). The area scope information includes slice information (which enhances the MDT configuration). The indication information is used to instruct the terminal to carry slice information when performing MDT reporting.

[0239] When the first communication device is an access network device, and the second communication device is a core network element and / or Operation Administration and Maintenance (OAM), the access network device receives MDT configuration or instruction information sent by the core network element and / or OAM. The MDT configuration includes area range information, which in turn includes slice information. The instruction information is used to instruct the access network device to include slice information when performing MDT reporting. The access network device may further send MDT configuration or instruction information to the terminal. This MDT configuration, which includes area range information, also includes slice information, and the instruction information is used to instruct the terminal to include slice information when performing MDT reporting.

[0240] Step 101: Report MDT measurement information based on MDT configuration or indication information. The MDT measurement information carries slice information.

[0241] Specifically, after receiving the enhanced MDT configuration or indication information, the first communication device can report the slice information together with the MDT measurement information based on the enhanced MDT configuration or indication information.

[0242] For example, the terminal carries slice information in the MDT measurement information reported to the access network equipment.

[0243] For example, access network devices may carry slice information in the MDT measurement information reported to the core network and / or OAM.

[0244] The MDT reporting method provided in this application embodiment sends enhanced MDT configuration or indication information to a first communication device through a second communication device. After receiving the enhanced MDT configuration or indication information, the first communication device can carry slice information when reporting MDT measurement information based on the enhanced MDT configuration or indication information, so that the network can identify the actual slice deployment situation and thus optimize the slice deployment.

[0245] In some embodiments, the region extent information is newly defined for the slice; or, the region extent information is existing region extent information.

[0246] Specifically, there are different ways to enhance the MDT configuration. One approach is to define a new MDT area scope for a slice, including slice information in the newly defined area scope information for the slice. For example, the MDT configuration adds a new area scope that is slice-based and contains slice information. The first communication device only performs measurements within the range of the slice corresponding to this slice information.

[0247] Another approach is to include slice information in the existing area scope information, or it can be understood as combining slices with the existing area scope, adding slice information to the existing area scope, and the first communication device only performs measurements within the configured existing area scope and within the configured slice (the slice corresponding to the slice information).

[0248] For example, an MDT combining slices with an existing area scope can include one or more of the following: Cell-based slice MDT, TAI-based slice MDT, PLMN-based slice MDT, SNPN-based slice MDT, PNI-NPN-based slice MDT, SNPN-cell-based slice MDT, and SNPN-TAI-based slice MDT.

[0249] Cell-based slice MDT: The first communication device only performs measurements within the configured cell range and supports the configured slice cells.

[0250] TAI-based slice MDT: The first communication device performs measurements only within the configured TAI range and supports the configured slice range.

[0251] PLMN-based slice MDT: The first communication device performs measurements only within the configured PLMN and supports the configured slice range.

[0252] SNPN based slice MDT: The first communication device performs measurements only within the configured SNPN range and supports the configured slice range.

[0253] PNI-NPN based slice MDT: The first communication device performs measurements only within the configured PNI-NPN range and supports the configured slice range.

[0254] SNPN Cell-based Slice MDT: The first communication device performs measurements only within a specific cell range of the configured SNPN and supports the configured slice range.

[0255] SNPN TAI based slice MDT: The first communication device performs measurements only within a specific TAI range of the configured SNPN and supports the configured slice range.

[0256] By using different MDT configuration enhancement methods, the flexibility of MDT configuration is improved.

[0257] In some embodiments, the MDT measurement information also carries one or more of the following:

[0258] (1) Supports measurement results of cells or beams in a specified slice.

[0259] Specifically, a designated slice refers to the slice corresponding to the slice information contained in the MDT configuration, that is, the slice in the network configuration.

[0260] It supports cells or beams for a specified slice, and may also include meanings such as allowing cells or beams for a specified slice, cells or beams that are available for a specified slice, and cells or beams that can be detected for a specified slice.

[0261] The community can be a service community, a neighboring community, or a residential community.

[0262] For example, the MDT configuration adds a new area scope, which is slice-based and contains slice information 1. The MDT measurement information reported by the first communication device can carry the measurement results of the cell or beam that supports slice 1.

[0263] For example, MDT configuration adds slice information to an existing area scope, assuming it is Cell-based slice MDT. Slice information slice1 is added to the Cell-based area scope. The MDT measurement information reported by the first communication device can carry the measurement results of the cell or beam that supports slice1 within the Cell-based area scope.

[0264] (2) Measurement information of the slice.

[0265] In some embodiments, the measurement information for a slice can be per-slice measurement information. For example, it can be the measurement information for each slice corresponding to the slice information included in the MDT configuration, or it can be the measurement information for each slice supported by a cell or beam in the MDT measurement information.

[0266] By including more detailed slice-related information in the MDT measurement information, the network can better optimize slice deployment.

[0267] In some embodiments, the measurement information of the slice includes one or more of the following:

[0268] Average throughput per slice;

[0269] Data volume per slice;

[0270] Packet loss rate per slice;

[0271] Packet latency per slice;

[0272] Zero-resource cells per slice. A zero-resource cell means that the cell's resources cannot be used for a given slice.

[0273] For example, if the MDT configuration includes slice information, assuming that the slice information corresponds to slice 1 and slice 2, the first communication device can report one or more of the following information: average throughput, data volume, packet loss rate, packet delay, zero-resource cell, etc. of slice 1, and one or more of the following information: average throughput, data volume, packet loss rate, packet delay, zero-resource cell, etc. of slice 2.

[0274] For example, if the first communication device reports MDT according to the instruction information sent by the second communication device, assuming that the reported MDT measurement information carries the measurement results of cell 1, and cell 1 supports slice 1 and slice 2, the first communication device can report one or more of the following information: average throughput, data volume, packet loss rate, packet delay, zero resource cell, etc. of slice 1, and report one or more of the following information: average throughput, data volume, packet loss rate, packet delay, zero resource cell, etc. of slice 2.

[0275] The measurement information for each slice includes one or more of the following: average throughput, data volume, packet loss rate, packet latency, zero-resource cells, etc. This not only improves the flexibility of MDT reporting, but also allows the network to have a more detailed understanding of the actual situation of slice deployment, thereby helping the network to better optimize slice deployment.

[0276] In some embodiments, the MDT configuration includes one or more of the following measurement trigger conditions:

[0277] Layer 1 event triggered;

[0278] Periodic triggering;

[0279] Triggered upon leaving the coverage area;

[0280] Slice trigger detected.

[0281] Specifically, for the enhanced scheme that includes slice information in the MDT configuration, in addition to the existing measurement triggering conditions (L1 event triggering, periodic triggering, and out-of-coverage triggering), this application also introduces a new measurement triggering condition, namely, slice detection triggering. For example, if the first communication device detects that a specific cell (such as the serving cell, the cell where the current UE is camped, etc.) supports a specified slice, then it triggers measurement reporting (or logging).

[0282] The MDT in this application can be an Immediate MDT and / or a Logged MDT, and is not limited thereto.

[0283] By introducing slice-related measurement triggering conditions, we can more effectively support MDT reporting of slice-related content, which will help the network to better optimize slice deployment.

[0284] In some embodiments, the MDT configuration includes one or more of the following measurement parameters:

[0285] Supports measurement results for cells or beams in a specified slice;

[0286] Measurement information of the slices.

[0287] Specifically, the second communication device can configure slice-related measurement content to the first communication device, and the first communication device performs measurements and reports them according to the configured measurement content. For example, the first communication device measures and reports the measurement results of cells or beams supporting a specified slice according to the configured measurement content, or measures and reports the slice measurement information according to the configured measurement content. The slice measurement information includes at least one of the following: average throughput per slice, data volume per slice, packet loss rate per slice, data packet delay per slice, and zero-resource cells per slice.

[0288] By configuring slice-related measurement content, the first communication device can report slice-related measurements more effectively, which helps the network to better optimize slice deployment.

[0289] In some embodiments, the slice information mentioned above includes one or more of the following: S-NSSAI; Network Slice AS Group (NSAG) identifier; NSAG slice support list (i.e., the list of slices supported by NSAG, including the list of slices belonging to NSAG).

[0290] For example, the first communication device receives the MDT configuration sent by the second communication device. The area range information of the MDT configuration includes slice information. The slice information can be one or more of S-NSSAI, NSAG identifier, and NSAG slice support list. The one or more slice information can be used to identify or indicate a specific slice. The first communication device can determine the slice of the network configuration through the one or more slice information.

[0291] For example, the MDT measurement information reported by the first communication device carries slice information, which may be one or more of S-NSSAI, NSAG identifier, or NSAG slice support list. The network can determine which slice information is included in the MDT measurement information reported by the first communication device based on the one or more slice information.

[0292] In some embodiments, the above-mentioned slice information may be a list containing multiple S-NSSAI, NSAG ID, or NSAG slice support lists.

[0293] For the slice information in the MDT configuration and the slice information carried in the MDT measurement information, slices can be identified or indicated by one or more of S-NSSAI, NSAG identifier, and NSAG slice support list, which can make MDT configuration and MDT reporting more flexible.

[0294] Figure 2 This is a second flowchart illustrating the MDT reporting method provided in this application embodiment. The method is applied to a second communication device, such as... Figure 2 As shown, the method includes the following steps:

[0295] Step 200: Send MDT configuration or indication information to the first communication device; the MDT configuration includes area range information, the area range information includes slice information, and the indication information is used to instruct the first communication device to carry slice information when performing MDT reporting.

[0296] Step 201: Receive the MDT measurement information reported by the first communication device. The MDT measurement information carries slice information.

[0297] Specifically, the first communication device is a terminal or access network device (e.g., a base station).

[0298] When the first communication device is a terminal and the second communication device is an access network device, the terminal receives MDT configuration or indication information sent by the access network device. The MDT configuration includes area range information, which includes slice information (which enhances the MDT configuration). The indication information is used to instruct the terminal to carry slice information when performing MDT reporting.

[0299] When the first communication device is an access network device, and the second communication device is a core network element and / or OAM, the access network device receives MDT configuration or indication information sent by the core network element and / or OAM. The MDT configuration includes area range information, which in turn includes slice information. The indication information is used to instruct the access network device to include slice information when performing MDT reporting. The access network device may further send MDT configuration or indication information to the terminal. This MDT configuration includes area range information, which in turn includes slice information. The indication information is used to instruct the terminal to include slice information when performing MDT reporting.

[0300] After receiving the enhanced MDT configuration or indication information, the first communication device can report the slice information along with the MDT measurement information based on the enhanced MDT configuration or indication information.

[0301] For example, the terminal carries slice information in the MDT measurement information reported to the access network equipment.

[0302] For example, access network devices may carry slice information in the MDT measurement information reported to the core network and / or OAM.

[0303] The MDT reporting method provided in this application embodiment sends enhanced MDT configuration or indication information to a first communication device through a second communication device. After receiving the enhanced MDT configuration or indication information, the first communication device can carry slice information when reporting MDT measurement information based on the enhanced MDT configuration or indication information, so that the network can identify the actual slice deployment situation and thus optimize the slice deployment.

[0304] In some embodiments, the region extent information is newly defined for the slice; or, the region extent information is existing region extent information.

[0305] Specifically, there are different ways to enhance the MDT configuration. One approach is to define a new MDT area scope for a slice, including slice information in the newly defined area scope information for the slice. For example, the MDT configuration adds a new area scope that is slice-based and contains slice information. The first communication device only performs measurements within the range of the slice corresponding to this slice information.

[0306] Another approach is to include slice information in the existing area scope information, or it can be understood as combining slices with the existing area scope, adding slice information to the existing area scope, and the first communication device only performs measurements within the configured existing area scope and within the configured slice (the slice corresponding to the slice information).

[0307] For example, an MDT combining slices with an existing area scope can include one or more of the following: Cell-based slice MDT, TAI-based slice MDT, PLMN-based slice MDT, SNPN-based slice MDT, PNI-NPN-based slice MDT, SNPN-cell-based slice MDT, and SNPN-TAI-based slice MDT.

[0308] Cell-based slice MDT: The first communication device only performs measurements within the configured cell range and supports the configured slice cells.

[0309] TAI-based slice MDT: The first communication device performs measurements only within the configured TAI range and supports the configured slice range.

[0310] PLMN-based slice MDT: The first communication device performs measurements only within the configured PLMN and supports the configured slice range.

[0311] SNPN based slice MDT: The first communication device performs measurements only within the configured SNPN range and supports the configured slice range.

[0312] PNI-NPN based slice MDT: The first communication device performs measurements only within the configured PNI-NPN range and supports the configured slice range.

[0313] SNPN Cell-based Slice MDT: The first communication device performs measurements only within a specific cell range of the configured SNPN and supports the configured slice range.

[0314] SNPN TAI based slice MDT: The first communication device performs measurements only within a specific TAI range of the configured SNPN and supports the configured slice range.

[0315] By using different MDT configuration enhancement methods, the flexibility of MDT configuration is improved.

[0316] In some embodiments, the MDT measurement information also carries one or more of the following:

[0317] (1) Supports measurement results of cells or beams in a specified slice.

[0318] Specifically, a designated slice refers to the slice corresponding to the slice information contained in the MDT configuration, that is, the slice in the network configuration.

[0319] It supports cells or beams for a specified slice, and may also include meanings such as allowing cells or beams for a specified slice, cells or beams that are available for a specified slice, and cells or beams that can be detected for a specified slice.

[0320] The community can be a service community, a neighboring community, or a residential community.

[0321] For example, the MDT configuration adds a new area scope, which is slice-based and contains slice information 1. The MDT measurement information reported by the first communication device can carry the measurement results of the cell or beam that supports slice 1.

[0322] For example, MDT configuration adds slice information to an existing area scope, assuming it is Cell-based slice MDT. Slice information slice1 is added to the Cell-based area scope. The MDT measurement information reported by the first communication device can carry the measurement results of the cell or beam that supports slice1 within the Cell-based area scope.

[0323] (2) Measurement information of the slice.

[0324] In some embodiments, the measurement information for a slice can be per-slice measurement information. For example, it can be the measurement information for each slice corresponding to the slice information included in the MDT configuration, or it can be the measurement information for each slice supported by a cell or beam in the MDT measurement information.

[0325] By including more detailed slice-related information in the MDT measurement information, the network can better optimize slice deployment.

[0326] In some embodiments, the measurement information of the slice includes one or more of the following:

[0327] Average throughput per slice;

[0328] Data volume per slice;

[0329] Packet loss rate per slice;

[0330] Packet latency per slice;

[0331] Zero-resource cells per slice. A zero-resource cell means that the cell's resources cannot be used for a given slice.

[0332] For example, if the MDT configuration includes slice information, assuming that the slice information corresponds to slice 1 and slice 2, the first communication device can report one or more of the following information: average throughput, data volume, packet loss rate, packet delay, zero-resource cell, etc. of slice 1, and one or more of the following information: average throughput, data volume, packet loss rate, packet delay, zero-resource cell, etc. of slice 2.

[0333] For example, if the first communication device reports MDT according to the instruction information sent by the second communication device, assuming that the reported MDT measurement information carries the measurement results of cell 1, and cell 1 supports slice 1 and slice 2, the first communication device can report one or more of the following information: average throughput, data volume, packet loss rate, packet delay, zero resource cell, etc. of slice 1, and report one or more of the following information: average throughput, data volume, packet loss rate, packet delay, zero resource cell, etc. of slice 2.

[0334] The measurement information for each slice includes one or more of the following: average throughput, data volume, packet loss rate, packet latency, zero-resource cells, etc. This not only improves the flexibility of MDT reporting, but also allows the network to have a more detailed understanding of the actual situation of slice deployment, thereby helping the network to better optimize slice deployment.

[0335] In some embodiments, the MDT configuration includes one or more of the following measurement trigger conditions:

[0336] Layer 1 event triggered;

[0337] Periodic triggering;

[0338] Triggered upon leaving the coverage area;

[0339] Slice trigger detected.

[0340] Specifically, for the enhanced scheme that includes slice information in the MDT configuration, in addition to the existing measurement triggering conditions (L1 event triggering, periodic triggering, and out-of-coverage triggering), this application also introduces a new measurement triggering condition, namely, slice detection triggering. For example, if the first communication device detects that a specific cell (such as the serving cell, the cell where the current UE is camped, etc.) supports a specified slice, then it triggers measurement reporting (or logging).

[0341] By introducing slice-related measurement triggering conditions, we can more effectively support MDT reporting of slice-related content, which will help the network to better optimize slice deployment.

[0342] In some embodiments, the MDT configuration includes one or more of the following measurement parameters:

[0343] Supports measurement results for cells or beams in a specified slice;

[0344] Measurement information of the slices.

[0345] Specifically, the second communication device can configure slice-related measurement content to the first communication device, and the first communication device performs measurements and reports them according to the configured measurement content. For example, the first communication device measures and reports the measurement results of cells or beams supporting a specified slice according to the configured measurement content, or measures and reports the slice measurement information according to the configured measurement content. The slice measurement information includes at least one of the following: average throughput per slice, data volume per slice, packet loss rate per slice, data packet delay per slice, and zero-resource cells per slice.

[0346] By configuring slice-related measurement content, the first communication device can report slice-related measurements more effectively, which helps the network to better optimize slice deployment.

[0347] In some embodiments, the above-mentioned slice information includes one or more of the following: S-NSSAI; NSAG identifier; NSAG slice support list (i.e., the list of slices supported by NSAG, including the list of slices belonging to NSAG).

[0348] For example, the first communication device receives the MDT configuration sent by the second communication device. The area range information of the MDT configuration includes slice information. The slice information can be one or more of S-NSSAI, NSAG identifier, and NSAG slice support list. The one or more slice information can be used to identify or indicate a specific slice. The first communication device can determine the slice of the network configuration through the one or more slice information.

[0349] For example, the MDT measurement information reported by the first communication device carries slice information, which may be one or more of S-NSSAI, NSAG identifier, or NSAG slice support list. The network can determine which slice information is included in the MDT measurement information reported by the first communication device based on the one or more slice information.

[0350] In some embodiments, the above-mentioned slice information may be a list containing multiple S-NSSAI, NSAG ID, or NSAG slice support lists.

[0351] For the slice information in the MDT configuration and the slice information carried in the MDT measurement information, slices can be identified or indicated by one or more of S-NSSAI, NSAG identifier, and NSAG slice support list, which can make MDT configuration and MDT reporting more flexible.

[0352] The methods provided in the various embodiments of this application are based on the same concept, so the implementation of each method can be referred to each other, and repeated parts will not be described again.

[0353] The methods provided in the above embodiments of this application are illustrated below through examples of specific application scenarios.

[0354] Example 1: Define a new area scope for a slice MDT.

[0355] The core network and / or OAM send MDT configuration to the base station, which can further send the MDT configuration to the UE (via RRC message, dedicated signaling, System Information Block (SIB) etc.). The MDT configuration includes at least one of the following: MDT area range information, measurement trigger conditions of UE and / or base station, and content that needs to be measured by UE and / or base station.

[0356] When the core network and / or OAM send area scope information to the base station in a "slice-based" manner, it includes slice information. Specifically, a new area scope is added, which is slice-based and contains slice information.

[0357] The slice information includes one or more of the following: S-NSSAI, NSAG ID, and a list of supported NSAG slices (including a list of slices belonging to NSAG). This slice information can be a list containing multiple S-NSSAI, NSAG IDs, and NSAG supported slice lists.

[0358] The UE and / or base station only perform measurements within the scope of the configured slice (the slice corresponding to the slice information).

[0359] For example, if the core network and / or OAM configures the area scope to slice 1 for the base station, and the base station further sends this configuration to the UE, then the UE and / or the base station will only consider performing MDT if slice 1 can be measured.

[0360] The measurement triggering conditions for UE and / or base station to perform MDT can be: the core network and / or OAM configures the measurement triggering conditions to the base station, and the base station further sends the configuration information to the UE. The measurement triggering conditions include: L1 event triggering, periodic triggering, out-of-coverage triggering, and slice detection triggering.

[0361] For example, if the UE and / or base station detects that a specific cell supports the slice that needs to be measured (the specific cell can be interpreted as the serving cell and / or the cell where the current UE is camped), then the UE and / or base station perform measurement reporting (or logging); or, if the UE and / or base station detects that a specific cell supports the slice that needs to be measured (the specific cell can be interpreted as the serving cell and / or the cell where the current UE is camped), and the triggering conditions of L1 event / period / out-of-coverage are met, then the UE and / or base station perform measurement reporting (logging).

[0362] The core network and / or OAM will also send measurement content to the base station, which is the measurement content that the base station / UE needs to collect, and the base station can further send it to the UE.

[0363] The measurement content includes one or more of the following: Immediate MDT measurement, Logged MDT measurement, measurement results of cells / beams supporting the slice (the slice corresponding to the slice information), average throughput per slice, data volume per slice, packet loss rate per slice, packet latency per slice, and zero-resource cells per slice.

[0364] When the UE and / or base station report to the MDT, they carry measurement-related information as well as slice information that the core network and / or OAM require them to measure.

[0365] The measurement-related information includes at least one of the following: the measured Immediate MDT measurement, the measured Logged MDT measurement, the measurement results of the cells / beams supporting the slice, the average throughput per slice, the data volume per slice, the packet loss rate per slice, the packet latency per slice, and the zero-resource cells per slice.

[0366] The slicing information is the slicing information set by the area scope.

[0367] For example, if the core network and / or OAM configures the area scope to slice 1 for the base station, and the base station further sends this configuration to the UE, then the UE and / or the base station should report slice 1 measurement-related information and slice 1 slice information.

[0368] Example 2: Add slice information based on an existing area scope.

[0369] The core network and / or OAM send MDT configuration to the base station, which can further send the MDT configuration to the UE (via RRC message, dedicated signaling, SIB, etc.). The MDT configuration includes at least one of the following: MDT area range information, measurement trigger conditions of UE and / or base station, and content that needs to be measured by UE and / or base station.

[0370] When the area scope information is cell-based slice MDT, the core network and / or OAM need to send slice information in addition to sending the cell ID contained in the cell-based area scope to the base station.

[0371] The slice information includes one or more of the following: S-NSSAI, NSAG ID, and a list of supported NSAG slices (including a list of slices belonging to NSAG). This slice information can be a list containing multiple S-NSSAI, NSAG IDs, and NSAG supported slice lists.

[0372] The UE and / or base station will only perform measurements within the configured cell range and in cells that support the configured slice.

[0373] For example, the core network and / or OAM configures the area scope to the base station as cell-based slice MDT, specifically cells 1-10 and slice 1. The base station further sends this configuration to the UE, so the UE and / or the base station only consider performing MDT on slice 1 within cells 1-10.

[0374] The measurement triggering conditions for UE and / or base station to perform MDT can be: the core network and / or OAM configures the measurement triggering conditions to the base station, and the base station further sends the configuration information to the UE. The measurement triggering conditions include: L1 event triggering, periodic triggering, and out-of-coverage triggering.

[0375] For example, if the UE and / or base station detects that a specific cell supports the slice that needs to be measured (the specific cell can be interpreted as the serving cell and / or the cell where the current UE is camped), and the triggering conditions of L1 event / period / out-of-coverage are met, then the UE and / or base station perform measurement reporting (logging).

[0376] The core network / OAM also sends measurement content to the base station, which is the measurement content that the base station / UE needs to collect. The base station can then send this content to the UE.

[0377] The measurement content includes one or more of the following: Immediate MDT measurement, Logged MDT measurement, measurement results of cells / beams supporting the slice (the slice corresponding to the slice information), average throughput per slice, data volume per slice, packet loss rate per slice, packet latency per slice, and zero-resource cells per slice.

[0378] When the UE and / or base station report to the MDT, they carry measurement-related information as well as slice information that the core network and / or OAM require them to measure.

[0379] The measurement-related information includes at least one of the following: the Immediate MDT measurement, the Logged MDT measurement, the measurement results of the cells / beams supporting the slice, the average throughput per slice, the data volume per slice, the packet loss rate per slice, the packet delay per slice, and the zero-resource cells per slice within the cell area scope (configured cell range).

[0380] Note: The same applies to other granularity area scopes, and will not be elaborated further. For example, for a TAI-based area scope, the following are reported within the TAI area scope (configured TAI range): Immediate MDT measurements, Logged MDT measurements, measurement results of cells / beams supporting the slice, average throughput per slice, data volume per slice, packet loss rate per slice, packet latency per slice, and zero-resource cells per slice.

[0381] The slice information is the slice information contained in the cell-based area scope.

[0382] For example, if the core network and / or OAM configures the area scope to cell 1-10 and slice 1 to the base station, and the base station further sends this configuration to the UE, then the UE and / or the base station should report the measurement-related information of slice 1 that can be measured in cell 1-10 and the slice information of slice 1.

[0383] For other granularities, refer to cell-based slice MDT, the difference being:

[0384] TAI-based slice MDT: Depending on the core network and / or OAM configuration, the UE / base station only performs measurements within the configured TAI range and supports the configured slice range.

[0385] PLMN-based slice MDT: Depending on the core network and / or OAM configuration, the UE / base station can only perform measurements within the configured PLMN and support the configured slice range.

[0386] SNPN based slice MDT: Depending on the core network and / or OAM configuration, the UE / base station only performs measurements within the configured SNPN range and supports the configured slice range.

[0387] PNI-NPN based slice MDT: Depending on the core network and / or OAM configuration, the UE / base station will only perform measurements within the configured PNI-NPN range and support the configured slice range.

[0388] SNPN Cell-based Slice MDT: Depending on the core network and / or OAM configuration, the UE / base station performs measurements only within a specific cell range of the configured SNPN and supports the configured slice range.

[0389] SNPN TAI based slice MDT: Depending on the core network and / or OAM configuration, the UE / base station only performs measurements within a specific TAI range of the configured SNPN and supports the configured slice range.

[0390] Example 3: Sending instruction information.

[0391] The core network and / or OAM sends the MDT configuration to the base station. The base station can further send the MDT configuration to the UE (via RRC messages, dedicated signaling, SIB, etc.). The MDT configuration includes at least one of the following: MDT area scope information, measurement triggering conditions for the UE and / or base station, and the content that the UE and / or base station need to measure. (For Example 3, the MDT area scope information is not enhanced and is the existing mechanism; the UE performs measurements within the configured area scope. The measurement triggering conditions for the UE and / or base station to execute the MDT are also not enhanced and are the existing mechanism.)

[0392] The core network and / or OAM sends indication information to the base station, which instructs the UE and / or base station to include slice information when performing MDT reporting. The base station sends indication information to the UE, which instructs the UE to include slice information when performing MDT reporting.

[0393] The slice information includes one or more of the following: S-NSSAI, NSAG ID, and a list of supported NSAG slices (including a list of slices belonging to NSAG). This slice information can be a list containing multiple S-NSSAI, NSAG IDs, and NSAG supported slice lists.

[0394] The core network and / or OAM will also send measurement content to the base station, which is the measurement content that the base station / UE needs to collect, and the base station can further send it to the UE.

[0395] The measurement content includes one or more of the following: Immediate MDT measurement, Logged MDT measurement, average throughput per slice, data volume per slice, packet loss rate per slice, packet latency per slice, and zero-resource cell per slice.

[0396] When the UE and / or base station report in MDT, they carry measurement-related information and slice information.

[0397] The measurement-related information includes at least one of the following: the measured Immediate MDT measurement, the measured Logged MDT measurement, the average throughput per slice, the data volume per slice, the packet loss rate per slice, the packet latency per slice, and the zero-resource cell per slice.

[0398] The slice information is the slice information corresponding to the measurement-related information.

[0399] For example, the core network and / or OAM instructs the base station to include slice information in the MDT reporting, and the base station further sends this instruction to the UE. When the UE and / or base station report cell / beam measurement results, they need to include the slice information supported by that cell / beam, such as cell 1 + slices 1, 2, and 3 supported by that cell + measurement results. When the UE and / or base station report throughput per DRB, for DL ​​it is per UE per slice, and the UE reports throughput per slice, such as the throughput of UE's slice 1, the throughput of UE's slice 2, and for UL it is per DRB per UE per slice, and the UE reports throughput per DRB per slice, such as the throughput of DRB1 and the slice information used by DRB1 (slice 1), the throughput of DRB2 and the slice information used by DRB2, and so on. The reporting of other measurements is similar and will not be elaborated here.

[0400] The methods and apparatuses provided in the various embodiments of this application are based on the same concept. Since the methods and apparatuses solve problems in similar ways, the implementations of the apparatuses and methods can refer to each other, and repeated details will not be repeated.

[0401] Figure 3 A schematic diagram of the structure of the first communication device provided in the embodiments of this application is shown below. Figure 3 As shown, the first communication device includes a memory 320, a transceiver 310, and a processor 300; wherein the processor 300 and the memory 320 may also be physically arranged separately.

[0402] The memory 320 is used to store computer programs; the transceiver 310 is used to send and receive data under the control of the processor 300.

[0403] Specifically, the transceiver 310 is used to receive and send data under the control of the processor 300.

[0404] Among them, Figure 3 In this application, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 300 and memory represented by memory 320 together. The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be further described herein. The bus interface provides an interface. The transceiver 310 can be multiple elements, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, and other transmission media.

[0405] The processor 300 is responsible for managing the bus architecture and general processing, while the memory 320 can store the data used by the processor 300 when performing operations.

[0406] The processor 300 can be a central processing unit (CPU), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor can also adopt a multi-core architecture.

[0407] The processor 300 executes any of the methods described in the embodiments of this application according to the obtained executable instructions by calling the computer program stored in the memory 320. For example:

[0408] Receive MDT configuration or indication information sent by the second communication device; the MDT configuration includes area range information, the area range information includes slice information, and the indication information is used to instruct the first communication device to carry slice information when performing MDT reporting;

[0409] MDT measurement information is reported based on MDT configuration or indication information, and the MDT measurement information carries slice information.

[0410] In some embodiments, the region extent information is newly defined region extent information for the slice; or...

[0411] The area scope information is existing area scope information.

[0412] In some embodiments, the MDT measurement information also carries one or more of the following:

[0413] Supports measurement results for cells or beams in a specified slice;

[0414] Measurement information of the slices.

[0415] In some embodiments, the measurement information of the slice includes one or more of the following:

[0416] Average throughput per slice;

[0417] Data volume per slice;

[0418] Packet loss rate per slice;

[0419] Packet latency per slice;

[0420] Zero-resource cells per slice.

[0421] In some embodiments, the MDT configuration includes one or more of the following measurement trigger conditions:

[0422] Layer 1 event triggered;

[0423] Periodic triggering;

[0424] Triggered upon leaving the coverage area;

[0425] Slice trigger detected.

[0426] In some embodiments, the MDT configuration includes one or more of the following measurement parameters:

[0427] Supports measurement results for cells or beams in a specified slice;

[0428] Measurement information of the slices.

[0429] In some embodiments, the slice information includes one or more of the following:

[0430] Single-network slice selection auxiliary information S-NSSAI;

[0431] Network slice access layer group NSAG identifier;

[0432] List of NSAG slicing supports.

[0433] Figure 4 This is a schematic diagram of the structure of the second communication device provided in the embodiments of this application, such as... Figure 4 As shown, the second communication device includes a memory 420, a transceiver 410, and a processor 400; wherein the processor 400 and the memory 420 may also be physically arranged separately.

[0434] The memory 420 is used to store computer programs; the transceiver 410 is used to send and receive data under the control of the processor 400.

[0435] Specifically, transceiver 410 is used to receive and send data under the control of processor 400.

[0436] Among them, Figure 4In this application, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 400 and memory represented by memory 420 together. The bus architecture may also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be further described herein. The bus interface provides an interface. The transceiver 410 may be multiple elements, including a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, including wireless channels, wired channels, optical fibers, and other transmission media.

[0437] The processor 400 is responsible for managing the bus architecture and general processing, while the memory 420 can store the data used by the processor 400 when performing operations.

[0438] The processor 400 can be a CPU, ASIC, FPGA or CPLD, and the processor can also adopt a multi-core architecture.

[0439] The processor 400 executes any of the methods described in the embodiments of this application according to the obtained executable instructions by calling the computer program stored in the memory 420. For example:

[0440] Send MDT configuration or indication information to the first communication device; the MDT configuration includes area range information, the area range information includes slice information, and the indication information is used to instruct the first communication device to carry slice information when performing MDT reporting;

[0441] Receive MDT measurement information reported by the first communication device. The MDT measurement information carries slice information.

[0442] In some embodiments, the region extent information is newly defined region extent information for the slice; or...

[0443] The area scope information is existing area scope information.

[0444] In some embodiments, the MDT measurement information also carries one or more of the following:

[0445] Supports measurement results for cells or beams in a specified slice;

[0446] Measurement information of the slices.

[0447] In some embodiments, the measurement information of the slice includes one or more of the following:

[0448] Average throughput per slice;

[0449] Data volume per slice;

[0450] Packet loss rate per slice;

[0451] Packet latency per slice;

[0452] Zero-resource cells per slice.

[0453] In some embodiments, the MDT configuration includes one or more of the following measurement trigger conditions:

[0454] Layer 1 event triggered;

[0455] Periodic triggering;

[0456] Triggered upon leaving the coverage area;

[0457] Slice trigger detected.

[0458] In some embodiments, the MDT configuration includes one or more of the following measurement parameters:

[0459] Supports measurement results for cells or beams in a specified slice;

[0460] Measurement information of the slices.

[0461] In some embodiments, the slice information includes one or more of the following:

[0462] Single-network slice selection auxiliary information S-NSSAI;

[0463] Network slice access layer group NSAG identifier;

[0464] List of NSAG slicing supports.

[0465] It should be noted that the first communication device and the second communication device provided in this application embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0466] Figure 5 This is one of the structural schematic diagrams of the MDT reporting device provided in the embodiments of this application, such as... Figure 5 As shown, the device includes:

[0467] The first receiving unit 500 is used to receive MDT configuration or indication information sent by the second communication device; the MDT configuration includes area range information, the area range information includes slice information, and the indication information is used to instruct the first communication device to carry slice information when performing MDT reporting.

[0468] The reporting unit 510 is used to report MDT measurement information based on MDT configuration or indication information. The MDT measurement information carries slice information.

[0469] In some embodiments, the region extent information is newly defined region extent information for the slice; or...

[0470] The area scope information is existing area scope information.

[0471] In some embodiments, the MDT measurement information also carries one or more of the following:

[0472] Supports measurement results for cells or beams in a specified slice;

[0473] Measurement information of the slices.

[0474] In some embodiments, the measurement information of the slice includes one or more of the following:

[0475] Average throughput per slice;

[0476] Data volume per slice;

[0477] Packet loss rate per slice;

[0478] Packet latency per slice;

[0479] Zero-resource cells per slice.

[0480] In some embodiments, the MDT configuration includes one or more of the following measurement trigger conditions:

[0481] Layer 1 event triggered;

[0482] Periodic triggering;

[0483] Triggered upon leaving the coverage area;

[0484] Slice trigger detected.

[0485] In some embodiments, the MDT configuration includes one or more of the following measurement parameters:

[0486] Supports measurement results for cells or beams in a specified slice;

[0487] Measurement information of the slices.

[0488] In some embodiments, the slice information includes one or more of the following:

[0489] Single-network slice selection auxiliary information S-NSSAI;

[0490] Network slice access layer group NSAG identifier;

[0491] List of NSAG slicing supports.

[0492] Figure 6 This is a second schematic diagram of the structure of the MDT reporting device provided in the embodiments of this application, as shown below. Figure 6As shown, the device includes:

[0493] The sending unit 600 is used to send MDT configuration or indication information to the first communication device; the MDT configuration includes area range information, the area range information includes slice information, and the indication information is used to instruct the first communication device to carry slice information when performing MDT reporting.

[0494] The second receiving unit 610 is used to receive MDT measurement information reported by the first communication device, wherein the MDT measurement information carries slice information.

[0495] In some embodiments, the region extent information is newly defined region extent information for the slice; or...

[0496] The area scope information is existing area scope information.

[0497] In some embodiments, the MDT measurement information also carries one or more of the following:

[0498] Supports measurement results for cells or beams in a specified slice;

[0499] Measurement information of the slices.

[0500] In some embodiments, the measurement information of the slice includes one or more of the following:

[0501] Average throughput per slice;

[0502] Data volume per slice;

[0503] Packet loss rate per slice;

[0504] Packet latency per slice;

[0505] Zero-resource cells per slice.

[0506] In some embodiments, the MDT configuration includes one or more of the following measurement trigger conditions:

[0507] Layer 1 event triggered;

[0508] Periodic triggering;

[0509] Triggered upon leaving the coverage area;

[0510] Slice trigger detected.

[0511] In some embodiments, the MDT configuration includes one or more of the following measurement parameters:

[0512] Supports measurement results for cells or beams in a specified slice;

[0513] Measurement information of the slices.

[0514] In some embodiments, the slice information includes one or more of the following:

[0515] Single-network slice selection auxiliary information S-NSSAI;

[0516] Network slice access layer group NSAG identifier;

[0517] List of NSAG slicing supports.

[0518] It should be noted that the division of units in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.

[0519] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0520] It should be noted that the apparatus provided in this application embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0521] On the other hand, embodiments of this application also provide a non-transient readable storage medium storing a computer program for causing a processor to execute the MDT reporting method provided in the above embodiments.

[0522] It should be noted that the non-transiently readable storage medium provided in this application embodiment can implement all the method steps implemented in the above method embodiment and can achieve the same technical effect. Here, the parts that are the same as those in the method embodiment and the beneficial effects will not be described in detail.

[0523] The non-transiently readable storage medium can be any available medium or data storage device that a computer can access, including but not limited to magnetic storage (e.g., floppy disks, hard disks, magnetic tapes, magneto-optical disks (MOs), etc.), optical storage (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (e.g., ROMs, EPROMs, EEPROMs, non-volatile memory (NAND flash), solid-state drives (SSDs)).

[0524] The technical solutions provided in this application can be applied to various systems, especially 5G systems. For example, applicable systems include Global System for Mobile Communication (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA) General Packet Radio Service (GPRS), Long Term Evolution (LTE), LTE Frequency Division Duplex (FDD), LTE Time Division Duplex (TDD), Long Term Evolution Advanced (LTE-A), Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX), and 5G New Radio (NR). All of these systems include terminal equipment and network equipment. The systems may also include a core network component, such as Evolved Packet System (EPS) and 5G systems (5GS).

[0525] The terminal involved in the embodiments of this application can be a device that provides voice and / or data connectivity to a user, a handheld device with wireless connectivity, or other processing devices connected to a wireless modem. The name of the terminal may differ in different systems; for example, in a 5G system, the terminal can be called a User Equipment (UE). The wireless terminal device can communicate with one or more core networks (CNs) via a Radio Access Network (RAN). The wireless terminal device can be a mobile terminal device, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal device, for example, a portable, pocket-sized, handheld, computer-embedded, or vehicle-mounted mobile device. They exchange voice and / or data with the radio access network. Examples include Personal Communication Service (PCS) phones, cordless phones, Session Initiated Protocol (SIP) phones, Wireless Local Loop (WLL) stations, and Personal Digital Assistants (PDAs). Wireless terminal equipment can also be referred to as a system, subscriber unit, subscriber station, mobile station, mobile station, remote station, access point, remote terminal, access terminal, user terminal, user agent, or user device, but is not limited to these terms in the embodiments of this application.

[0526] The access network equipment involved in this application embodiment can be a base station, which may include multiple cells providing services to terminals. Depending on the specific application, the base station may also be called an access point, or a device in the access network that communicates with wireless terminal devices through one or more sectors on the air interface, or other names. The network device can be used to exchange received air frames with Internet Protocol (IP) packets, acting as a router between the wireless terminal device and the rest of the access network, where the rest of the access network may include an Internet Protocol (IP) communication network. The access network equipment can also coordinate the attribute management of the air interface. For example, the access network equipment involved in the embodiments of this application can be the Base Transceiver Station (BTS) in Global System for Mobile communications (GSM) or Code Division Multiple Access (CDMA), or the NodeB in Wide-band Code Division Multiple Access (WCDMA), or the evolved Node B (eNB or e-NodeB) in a long term evolution (LTE) system, or the 5G base station (gNB) in a next-generation system, or the Home evolved Node B (HeNB), relay node, femto, pico, etc., and is not limited in the embodiments of this application. In some network structures, the access network equipment may include centralized unit (CU) nodes and distributed unit (DU) nodes, and the centralized unit and distributed unit may also be geographically separated.

[0527] Access network devices and terminals can each use one or more antennas for multiple-input multiple-output (MIMO) transmission. MIMO transmission can be single-user MIMO (SU-MIMO) or multiple-user MIMO (MU-MIMO). Depending on the configuration and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO, and can also be diversity transmission, precoding transmission, or beamforming transmission, etc.

[0528] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, disk storage and optical storage) containing computer-usable program code.

[0529] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart... Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0530] These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the processor-readable memory produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0531] These processors can execute instructions that can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable device for implementing the process. Figure 1One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0532] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A minimum road test (MDT) reporting method, characterized in that, Applied to a first communication device, including: Receive MDT configuration or indication information sent by the second communication device; the MDT configuration includes area range information, the area range information includes slice information, and the indication information is used to instruct the first communication device to carry slice information when performing MDT reporting; MDT measurement information is reported based on the MDT configuration or the indication information, and the MDT measurement information carries slice information.

2. The MDT reporting method according to claim 1, characterized in that, The region range information is newly defined region range information for the slice; or... The area range information is existing area range information.

3. The MDT reporting method according to claim 1 or 2, characterized in that, The MDT measurement information also carries one or more of the following: Supports measurement results for cells or beams in a specified slice; Measurement information of the slices.

4. The MDT reporting method according to claim 3, characterized in that, The measurement information of the slice includes one or more of the following: Average throughput per slice; Data volume per slice; Packet loss rate per slice; Packet latency per slice; Zero-resource cells per slice.

5. The MDT reporting method according to claim 1 or 2, characterized in that, The MDT configuration includes one or more of the following measurement trigger conditions: Layer 1 event triggered; Periodic triggering; Triggered upon leaving the coverage area; Slice trigger detected.

6. The MDT reporting method according to claim 1 or 2, characterized in that, The MDT configuration includes one or more of the following measurement items: Supports measurement results for cells or beams in a specified slice; Measurement information of the slices.

7. The MDT reporting method according to claim 1, characterized in that, The slice information includes one or more of the following: Single-network slice selection auxiliary information S-NSSAI; Network slice access layer group NSAG identifier; List of NSAG slicing supports.

8. A minimum road test (MDT) reporting method, characterized in that, Applied to a second communication device, including: Send MDT configuration or indication information to the first communication device; the MDT configuration includes area range information, the area range information includes slice information, and the indication information is used to instruct the first communication device to carry slice information when performing MDT reporting; The device receives MDT measurement information reported by the first communication device, wherein the MDT measurement information carries slice information.

9. The MDT reporting method according to claim 8, characterized in that, The region range information is newly defined region range information for the slice; or... The area range information is existing area range information.

10. The MDT reporting method according to claim 8 or 9, characterized in that, The MDT measurement information also carries one or more of the following: Supports measurement results for cells or beams in a specified slice; Measurement information of the slices.

11. The MDT reporting method according to claim 10, characterized in that, The measurement information of the slice includes one or more of the following: Average throughput per slice; Data volume per slice; Packet loss rate per slice; Packet latency per slice; Zero-resource cells per slice.

12. The MDT reporting method according to claim 8 or 9, characterized in that, The MDT configuration includes one or more of the following measurement trigger conditions: Layer 1 event triggered; Periodic triggering; Triggered upon leaving the coverage area; Slice trigger detected.

13. The MDT reporting method according to claim 8 or 9, characterized in that, The MDT configuration includes one or more of the following measurement items: Supports measurement results for cells or beams in a specified slice; Measurement information of the slices.

14. The MDT reporting method according to claim 8, characterized in that, The slice information includes one or more of the following: Single-network slice selection auxiliary information S-NSSAI; Network slice access layer group NSAG identifier; List of NSAG slicing supports.

15. A first communication device, characterized in that, Includes memory, transceiver, and processor; A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations: Receive minimum road test MDT configuration or indication information sent by the second communication device; the MDT configuration includes area range information, the area range information includes slice information, and the indication information is used to instruct the first communication device to carry slice information when performing MDT reporting; MDT measurement information is reported based on the MDT configuration or the indication information, and the MDT measurement information carries slice information.

16. The first communication device according to claim 15, characterized in that, The region range information is newly defined region range information for the slice; or... The area range information is existing area range information.

17. The first communication device according to claim 15 or 16, characterized in that, The MDT measurement information also carries one or more of the following: Supports measurement results for cells or beams in a specified slice; Measurement information of the slices.

18. The first communication device according to claim 17, characterized in that, The measurement information of the slice includes one or more of the following: Average throughput per slice; Data volume per slice; Packet loss rate per slice; Packet latency per slice; Zero-resource cells per slice.

19. The first communication device according to claim 15 or 16, characterized in that, The MDT configuration includes one or more of the following measurement trigger conditions: Layer 1 event triggered; Periodic triggering; Triggered upon leaving the coverage area; Slice trigger detected.

20. The first communication device according to claim 15 or 16, characterized in that, The MDT configuration includes one or more of the following measurement items: Supports measurement results for cells or beams in a specified slice; Measurement information of the slices.

21. The first communication device according to claim 15, characterized in that, The slice information includes one or more of the following: Single-network slice selection auxiliary information S-NSSAI; Network slice access layer group NSAG identifier; List of NSAG slicing supports.

22. A second communication device, characterized in that, Includes memory, transceiver, and processor; A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer programs from the memory and performing the following operations: Send minimum drive test (MDT) configuration or indication information to the first communication device; the MDT configuration includes area range information, the area range information includes slice information, and the indication information is used to instruct the first communication device to carry slice information when performing MDT reporting; The device receives MDT measurement information reported by the first communication device, wherein the MDT measurement information carries slice information.

23. The second communication device according to claim 22, characterized in that, The region range information is newly defined region range information for the slice; or... The area range information is existing area range information.

24. The second communication device according to claim 22 or 23, characterized in that, The MDT measurement information also carries one or more of the following: Supports measurement results for cells or beams in a specified slice; Measurement information of the slices.

25. The second communication device according to claim 24, characterized in that, The measurement information of the slice includes one or more of the following: Average throughput per slice; Data volume per slice; Packet loss rate per slice; Packet latency per slice; Zero-resource cells per slice.

26. The second communication device according to claim 22 or 23, characterized in that, The MDT configuration includes one or more of the following measurement trigger conditions: Layer 1 event triggered; Periodic triggering; Triggered upon leaving the coverage area; Slice trigger detected.

27. The second communication device according to claim 22 or 23, characterized in that, The MDT configuration includes one or more of the following measurement items: Supports measurement results for cells or beams in a specified slice; Measurement information of the slices.

28. The second communication device according to claim 22, characterized in that, The slice information includes one or more of the following: Single-network slice selection auxiliary information S-NSSAI; Network slice access layer group NSAG identifier; List of NSAG slicing supports.

29. A minimum road test MDT reporting device, characterized in that, include: The first receiving unit is configured to receive MDT configuration or indication information sent by the second communication device; the MDT configuration includes area range information, the area range information includes slice information, and the indication information is used to instruct the first communication device to carry slice information when performing MDT reporting; The reporting unit is used to report MDT measurement information based on the MDT configuration or the indication information, wherein the MDT measurement information carries slice information.

30. A minimum road test MDT reporting device, characterized in that, include: The sending unit is used to send MDT configuration or indication information to the first communication device; the MDT configuration includes area range information, the area range information includes slice information, and the indication information is used to instruct the first communication device to carry slice information when performing MDT reporting; The second receiving unit is used to receive MDT measurement information reported by the first communication device, wherein the MDT measurement information carries slice information.

31. A non-transiently readable storage medium, characterized in that, The non-transiently readable storage medium stores a computer program that causes a processor to perform the method according to any one of claims 1 to 7.

32. A non-transiently readable storage medium, characterized in that, The non-transiently readable storage medium stores a computer program that causes a processor to perform the method according to any one of claims 8 to 14.

Images