Data Transmission Method and Device

Abstract

The present application provides a data transmission method and apparatus. The method includes: a terminal device generates a recording result, where the recording result includes at least one of a recorded minimized drive test report, an RLF report, and a RACH report. The recorded minimized drive test report includes an identifier of a candidate access cell, information for indicating whether the candidate access cell supports a network slice service initiated by the terminal device, location information of the terminal device when receiving the system message of the candidate access cell, and a network slice identifier corresponding to the network slice service initiated by the terminal device. The RLF report includes an identifier of a cell where a radio link failure occurs after the terminal device accesses and a network slice identifier corresponding to the network slice service when the terminal device has a radio link failure. The RACH report includes an identifier of the cell accessed by the terminal device and a network slice identifier corresponding to the network slice service initiated by the terminal device. The terminal device sends the recording result to a radio access network device to which the serving cell belongs.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and in particular, to a data transmission method and apparatus. Background Art

[0002] With the development of mobile communication technologies, various new services and application scenarios have emerged continuously. While the 5th generation (5G) communication has flexibility and scalability, it also needs to meet different service requirements. To this end, 5G provides services for users specifically through end-to-end network slices. A network slice is a customized network service provided by an operator for users. By flexibly allocating network resources and networking on demand, multiple logical resources with different characteristics and isolated from each other are virtualized on the same set of physical facilities, and each logical resource is a network slice. Each network slice can be composed of a radio access network slice, a transport network slice, and a core subnet slice.

[0003] The random access process is a process that a user equipment (UE) needs to execute when accessing the network. In the prior art, after the UE completes random access and enters the connected state, the UE sends a report result to the base station, and the report result includes a logged minimization of drive tests (Logged MDT) report, a random access channel (RACH) report, and a radio link failure (RLF) report. Among them, the Logged MDT report includes cell identification, timestamp, Bluetooth measurement information, wireless measurement information, etc. The random access report includes cell identification, channel state information-reference signal (CSI-RS), reference signal receiving power (RSRP) quality, and the event type of random access, etc. The RLF report mainly includes connection failure type, failed cell ID, and radio link failure reason. The base station can optimize the relevant configuration of the cell according to the received report result.

[0004] In the above process, the report result sent by the UE to the base station is the relevant measurement result of the UE under one or more cells. A cell can support multiple network slices, different network slices support different services, and different cells can deploy different network slices. At this time, how the UE can more effectively report the report result is an urgent problem to be solved. Summary of the Invention

[0005] The present application provides a data transmission method and apparatus to solve the problem of how a terminal device can more effectively report recorded results under different network slices supporting different service scenarios.

[0006] The terminal device generates a recorded result, which includes at least one of a recorded minimized drive test report, a radio link failure (RLF) report, and a random access channel (RACH) report. Among them, the recorded minimized drive test report includes the identifier of a candidate access cell, information indicating whether the candidate access cell supports the network slice service initiated by the terminal device, the location information of the terminal device when receiving the system message of the candidate access cell, and the network slice identifier corresponding to the network slice service initiated by the terminal device. The candidate access cell is the top N cells sorted in descending order of signal strength or signal quality among the cells measured by the terminal device, where N is a preset positive integer. The RLF report includes the identifier of the cell where the terminal device has access and a radio link failure occurs, and the network slice identifier corresponding to the network slice service of the terminal device when the radio link failure occurs. The RACH report includes the identifier of the cell accessed by the terminal device and the network slice identifier corresponding to the network slice service initiated by the terminal device.

[0007] Through the data transmission method provided in the first aspect, the terminal device generates a recorded result and sends the recorded result to the radio access network device to which the serving cell belongs. The recorded result includes at least one of a minimized drive test report, an RLF report, and a RACH report. The minimized drive test report, the RLF report, and the RACH report all carry information related to the network slice service. The radio access network device can learn from the recorded minimized drive test report whether each candidate access cell supports the network slice service initiated by the terminal device and the network slice identifier corresponding to the network slice service initiated by the terminal device in the corresponding candidate access cell. The radio access network device can learn from the RLF report the network slice identifier corresponding to the network slice service initiated by the terminal device in the cell where the terminal device has access and a radio link failure occurs. The radio access network device can learn from the RACH report the network slice identifier corresponding to the network slice service initiated by the terminal device in the accessed cell. Thus, when the radio access network device can determine that it needs to adjust the network slices it supports based on the network slice-related information learned from at least one of the above three reports, it adjusts the network slices it supports. Thus, the problem of how the terminal device reports the recorded results under different network slices supporting different service scenarios is solved. Furthermore, when the radio access network device can determine that it needs to adjust the network slices it supports based on the recorded results reported by the terminal device, it adjusts the network slices it can support, improving the success rate of the terminal device accessing the network slice.

[0008] In a possible design, the method of this embodiment may further include:

[0009] The terminal device receives the updated network slice configuration information sent by the radio access network device. The updated network slice configuration information is determined by the radio access network device, the network management device, or the access and mobility management function network element (AMF) based on the recording results of at least one terminal device within a preset time period. The updated network slice configuration information includes a network slice identifier list, and the network slice identifier list contains the network slice identifiers corresponding to at least one network slice supported by the radio access network device. The network slice identifier list includes the network slice identifier corresponding to the network slice service initiated by the terminal device in the cell controlled by the radio access network device.

[0010] Through the data transmission method provided in this embodiment, the network slice identifier list includes the network slice identifier corresponding to the network slice service initiated by the terminal device in the cell controlled by the radio access network device. Therefore, the network slice identifier list corresponding to the network slices supported after the adjustment of the radio access network device can include the network slice identifier corresponding to the network slice service initiated by the terminal device, which can improve the success rate of the terminal device accessing the network slice.

[0011] In a possible design, the terminal device generates a recording result, specifically:

[0012] The terminal device performs the following operations according to the reference signal information of the measured candidate access cells:

[0013] The terminal device obtains the network slice identifier list of the first candidate access cell;

[0014] The terminal device determines whether the first candidate access cell supports the network slice service initiated by the terminal device according to the network slice identifier list of the first candidate access cell;

[0015] If it is determined that it is,

[0016] The terminal device determines to store the RACH report corresponding to the first candidate access cell after successfully randomly accessing the first candidate access cell; or,

[0017] The terminal device determines to store the RLF report corresponding to the first candidate access cell after successfully randomly accessing the first candidate access cell and experiencing a radio link failure during the subsequent communication process; or,

[0018] The terminal device determines that it fails to successfully randomly access the first candidate access cell, obtains the network slice identifier list of the second candidate access cell, and stores the recorded minimum drive test report corresponding to the first candidate access cell;

[0019] If the determination is negative, the terminal device stores the minimized drive test report corresponding to the first candidate access cell, or the terminal device obtains the network slice identifier list of the second candidate access cell and stores the minimized drive test report corresponding to the first candidate access cell.

[0020] Through the data transmission method provided in this embodiment, during the process of the terminal device generating the recording result, the minimized drive test report, the RLF report, and the RACH report all carry information related to the network slice service. Therefore, the radio access network device can adjust the network slices it supports according to the information related to the network slice service carried in the recording results sent by multiple terminal devices within a preset time period, improving the success rate of the terminal device accessing the network slice.

[0021] In a possible design, the method of this embodiment may further include:

[0022] When the terminal device determines that the stored RACH report meets the preset condition, the terminal device deletes the stored RACH reports in ascending order of importance. The preset condition may be that the number of RACH reports carried is greater than or equal to a preset threshold, or the duration of the RACH reports carried is greater than or equal to a preset threshold. For example, the number of RACH reports carried is greater than eight times, or the duration of the RACH reports carried is greater than 48 hours, or both are satisfied, then it is determined that the preset condition is met. The determination condition for the importance of the RACH report may be: the importance of the RACH report of the cell that supports the network slice service initiated by the terminal device is higher than that of the RACH report of the cell that does not support the network slice service initiated by the terminal device; or, the importance of the RACH report of the cell with good signal quality (or high signal strength) is higher than that of the RACH report of the cell with bad signal quality (or low signal strength). By deleting the stored RACH reports in ascending order of importance, compared with randomly deleting in the prior art, the storage time of the RACH reports with high importance can be extended, and the utilization value of the RACH reports can be fully exerted.

[0023] In a possible design, when the terminal device determines that the random access fails in the first candidate access cell, there are the following two cases:

[0024] The terminal device determines that the number of random access attempts initiated in the first candidate access cell is greater than the first threshold; or,

[0025] The terminal device determines that it has successfully randomly accessed the first candidate access cell and the number of random access attempts initiated again after a radio link failure occurs during the subsequent communication process is greater than the first threshold.

[0026] In a possible design, the recorded minimized drive test report further includes at least one of network slice remapping information of a candidate access cell and network slice redirection of the candidate access cell.

[0027] Through the data transmission method provided by this embodiment, by carrying the network slice remapping information of the candidate access cell in the recorded minimized drive test report, the radio access network device that receives the recording result sent by the terminal device can adjust the new network slice remapping information according to the network slice remapping information originally stored by the terminal device (i.e., the network slice remapping information of the candidate access cell included in the recorded minimized drive test report), so that the terminal device can successfully initiate a network slice service. By carrying the network slice redirection information of the candidate access cell in the recorded minimized drive test report, the radio access network device that receives the recording result sent by the terminal device can redirect the terminal device to a cell that supports the network slice service to initiate the corresponding network slice service.

[0028] In a possible design, the method of this embodiment further includes:

[0029] The terminal device receives the adjustment information of the access category sent by the radio access network device, and the adjustment information of the access category is used to increase the access category related to the network slice service; or,

[0030] The terminal device prestores the adjustment information of the access category.

[0031] Through the data transmission method provided by this embodiment, by the terminal device receiving the adjustment information of the access category sent by the radio access network device, or the terminal device prestoring the adjustment information of the access category, and the adjustment information of the access category is used to increase the access category related to the network slice service, the probability of the terminal device accessing the network slice can be increased, and the probability of the terminal device accessing non-network slice services can be reduced.

[0032] In a possible design, when the recording result includes a RACH report, before the terminal device sends the recording result to the radio access network device to which the serving cell belongs, it further includes: the terminal device determines that the number of RACH reports stored by the terminal device is greater than or equal to a preset number and / or the time of the RACH reports stored by the terminal device is greater than or equal to a preset duration. Among them, the number of stored RACH reports can be obtained through a counter set by the terminal device, and the time of the stored RACH reports can be obtained through a timer set by the terminal device.

[0033] Through the data transmission method provided in this embodiment, after the terminal device generates a RACH report, when it is determined that the number of RACH reports stored by the terminal device is greater than or equal to a preset number and / or the time for which the terminal device has stored the RACH reports is greater than or equal to a preset duration, the RACH report is sent to the radio access network device to which the serving cell belongs. Thus, there is no need for the radio access network device to send a RACH report request, and the terminal device actively reports the RACH report.

[0034] In a possible design, after the terminal device sends a recording result to the radio access network device to which the serving cell belongs, the method further includes:

[0035] The terminal device deletes the stored RACH reports in ascending order of importance. The importance determination conditions can be: the importance of the RACH report of the cell that supports the network slice service initiated by the terminal device is higher than that of the RACH report of the cell that does not support the network slice service initiated by the terminal device; or, the importance of the RACH report of the cell with good signal quality (or high signal strength) is higher than that of the RACH report of the cell with bad signal quality (or low signal strength). The terminal device can delete one report, multiple reports, or clear the entire memory storing the RACH reports. By deleting the stored RACH reports in ascending order of importance, the storage time of the RACH reports with high importance can be extended, and the utilization value of the RACH reports can be fully utilized.

[0036] In a second aspect, the present application provides a data transmission method, including:

[0037] The radio access network device establishes a connection with the terminal device;

[0038] The radio access network device receives a recording result sent by the terminal device. The recording result includes at least one of a minimized drive test (MDT) report, a radio link failure (RLF) report, and a random access channel (RACH) report. The MDT report includes the identifier of a candidate access cell, information indicating whether the candidate access cell supports the network slice service initiated by the terminal device, the location information of the terminal device when receiving the system message, and the network slice identifier corresponding to the network slice service initiated by the terminal device. The candidate access cell is the top N cells sorted in descending order of signal strength or signal quality among the cells measured by the terminal device, where N is a preset positive integer. The RLF report includes the identifier of the cell in which the terminal device experiences a radio link failure after access and the network slice identifier corresponding to the network slice service when the terminal device experiences the radio link failure. The RACH report includes the identifier of the cell accessed by the terminal device and the network slice identifier corresponding to the network slice service initiated by the terminal device.

[0039] Through the data transmission method provided by the second aspect, after establishing a connection with the terminal device through the radio access network device, the radio access network device receives the recording result sent by the terminal device. The recording result includes at least one of a minimized drive test report, an RLF report, and a RACH report. The minimized drive test report, the RLF report, and the RACH report all carry information related to network slice services. According to the recorded minimized drive test report, the radio access network device can know whether each candidate access cell supports the network slice service initiated by the terminal device and the network slice identifier corresponding to the network slice service initiated by the terminal device in the corresponding candidate access cell. According to the RLF report, the radio access network device can know the network slice identifier corresponding to the network slice service initiated by the terminal device in the cell where the terminal device has accessed and a radio link failure has occurred. According to the RACH report, the radio access network device can know the network slice identifier corresponding to the network slice service initiated by the terminal device in the accessed cell. Thus, when the radio access network device can determine that it needs to adjust the network slices it supports based on the network slice-related information obtained from at least one of the above three reports, it adjusts the network slices it supports. Thus, the problem of how the terminal device reports the recording result in different network slices supporting different service scenarios is solved. Furthermore, when the radio access network device can determine that it needs to adjust the network slices it supports based on the recording result reported by the terminal device, it adjusts the network slices it can support, improving the success rate of the terminal device accessing the network slice.

[0040] In a possible design, the method of this embodiment may further include:

[0041] The radio access network device sends updated network slice configuration information to the terminal device. The updated network slice configuration information is determined by the radio access network device, the network management device, or the access and mobility management function network element AMF according to the recording results of at least one terminal device within a preset time period. The updated network slice configuration information includes a network slice identifier list, and the network slice identifier list contains the network slice identifiers corresponding to at least one network slice that the radio access network device can support. The network slice identifier list includes the network slice identifier corresponding to the network slice service initiated by the terminal device in the cell controlled by the radio access network device.

[0042] Through the data transmission method provided by this embodiment, the network slice identifier list includes the network slice identifier corresponding to the network slice service initiated by the terminal device in the cell controlled by the radio access network device. Thus, the network slice identifier list corresponding to the network slices supported after the adjustment of the radio access network device can include the network slice identifier corresponding to the network slice service initiated by the terminal device, which can improve the success rate of the terminal device accessing the network slice.

[0043] In a possible design, the method of this embodiment may further include:

[0044] The radio access network device stores the recording result and sends the recording result to other radio access network devices.

[0045] Through the data transmission method provided by this embodiment, the recording result is sent to other radio access network devices through the radio access network device, and the radio access network device can adjust the network slices it supports according to the information related to the network slice service carried in the recording results sent by multiple terminal devices received within a preset time period.

[0046] In a possible design, the method of this embodiment may further include:

[0047] The radio access network device determines a network slice identifier list according to the recorded minimized drive test reports, RLF reports, and RACH reports in the recording results of multiple terminal devices received within a preset time period.

[0048] In a possible design, the method of this embodiment may further include:

[0049] The radio access network device stores the recording result and sends the recording result to the network management device or the AMF, so that the network management device or the AMF determines the radio access network devices that need to adjust the network slice service and the corresponding network slice identifier list according to the recorded minimized drive test reports, RLF reports, and RACH reports in the recording results of multiple terminal devices received within a preset time period.

[0050] Through the data transmission method provided by this embodiment, the recording result is sent to the network management device or the AMF through the radio access network device, and the network management device or the AMF determines the radio access network devices that need to adjust the network slice service and the corresponding network slice identifier list according to the recorded minimized drive test reports, RLF reports, and RACH reports in the recording results of multiple terminal devices received within a preset time period. Compared with the radio access network device determining whether to adjust and how to adjust the network slices it supports, in this embodiment, the network management device or the AMF determines which radio access network devices need to adjust the network slice service and how to adjust, with higher accuracy. Since the network management device or the AMF can obtain the recording results of the terminal devices of multiple radio access network devices respectively, centralized decision-making can be carried out, which is beneficial to the improvement of the overall network experience in a region.

[0051] In a possible design, before the radio access network device sends updated network slice configuration information to the terminal device, it may further include:

[0052] The radio access network device receives an adjustment instruction sent by the network management device or the AMF. The adjustment instruction includes an updated network slice identifier list corresponding to the radio access network device.

[0053] Through the data transmission method provided in this embodiment, the network management device or the AMF determines the radio access network devices that need to adjust network slice services and the corresponding network slice identifier list, and then sends an adjustment instruction to the radio access network devices that need to adjust network slice services. Compared with the situation where the radio access network device determines whether to adjust and how to adjust the network slices it supports, in this embodiment, the network management device or the AMF determines which radio access network devices need to adjust network slice services and how to adjust them, with higher accuracy. Since the network management device or the AMF can obtain more record results of terminal devices, the decision-making is more perfect, which is beneficial to improving the overall network experience in a region.

[0054] In a possible design, the method of this embodiment may further include:

[0055] The radio access network device determines updated network slice remapping information according to the record result and the updated network slice configuration information, and the radio access network device sends the updated network slice remapping information to the terminal device.

[0056] Through the data transmission method provided in this embodiment, by adjusting the network slice remapping information according to the record result and the updated network slice configuration information by the radio access network device, the terminal device can successfully initiate network slice services, and the probability of the terminal device accessing the network slice is increased.

[0057] In a possible design, the updated network slice configuration information further includes adjustment information for the access control information of the network slice service. By carrying the adjustment information for the access control information of the network slice service, the probability of the terminal device accessing non-network slice services can be reduced, so that the terminal device preferentially accesses network slice services.

[0058] In a possible design, the adjustment information for the access control information of the network slice service is a system message. The radio access network device updates the access control parameter set list cell in SIB1. Specifically, there are the following four optional methods:

[0059] Exclude the access control identifier ID related to the network slice service from the unified access control blocking access identity information in the system message; or,

[0060] Add an access control ID unrelated to the network slice service to the unified access control blocking access identity information in the system message; or,

[0061] The value of the unified access control blocking factor cell corresponding to the network slice service in the system message decreases within a preset range; or,

[0062] The value of the unified access control time cell corresponding to the network slice service in the system message increases within a preset range.

[0063] In a possible design, the method of this embodiment may further include:

[0064] The radio access network device sends adjustment information for the access category to the terminal device, and the adjustment information for the access category is used to increase the access category related to the network slice service; or,

[0065] The radio access network device pre-stores the adjustment information for the access category.

[0066] Through the data transmission method provided by this embodiment, by the radio access network device sending the adjustment information for the access category to the terminal device, or the radio access network device pre-storing the adjustment information for the access category, and the adjustment information for the access category is used to increase the access category related to the network slice service, the probability of the terminal device accessing the network slice can be increased, and the probability of the terminal device accessing non-network slice services can be reduced.

[0067] In a possible design, the method of this embodiment may further further include:

[0068] The radio access network device modifies the current configuration, and the configuration includes at least one of the data radio bearer supported by the radio access network device, spectrum bandwidth configuration, carrier configuration, and modulation and demodulation mode configuration.

[0069] In a third aspect, the present application provides a terminal device, including:

[0070] A generation module, configured to generate a recording result, where the recording result includes at least one of a recorded minimized drive test report, a radio link failure (RLF) report, and a random access channel (RACH) report. The recorded minimized drive test report includes the identifier of a candidate access cell, information indicating whether the candidate access cell supports the network slice service initiated by the terminal device, the location information of the terminal device when receiving the system message, and the network slice identifier corresponding to the network slice service initiated by the terminal device. The candidate access cell is the top N cells among the cells measured by the terminal device sorted in descending order according to signal strength or signal quality, and N is a preset positive integer. The RLF report includes the identifier of the cell where the radio link failure occurs after the terminal device accesses and the network slice identifier corresponding to the network slice service when the terminal device has a radio link failure. The RACH report includes the identifier of the cell accessed by the terminal device and the network slice identifier corresponding to the network slice service initiated by the terminal device;

[0071] A sending module, configured to send the recording result to a radio access network device to which the serving cell belongs.

[0072] In a possible design, the terminal device may further include:

[0073] A receiving module, configured to receive updated network slice configuration information sent by a radio access network device, where the updated network slice configuration information is determined by the radio access network device, a network management device, or an access and mobility management function network element AMF according to recording results of at least one terminal device within a preset time period;

[0074] The updated network slice configuration information includes a network slice identifier list, where the network slice identifier list contains network slice identifiers corresponding to at least one network slice supported by the radio access network device, and the network slice identifier list includes network slice identifiers corresponding to network slice services initiated by the terminal device in a cell controlled by the radio access network device.

[0075] In a possible design, the generating module is configured to:

[0076] Perform the following operations according to the reference signal information of the measured candidate access cells:

[0077] Obtain the network slice identifier list of the first candidate access cell;

[0078] Determine whether the first candidate access cell supports the network slice service initiated by the terminal device according to the network slice identifier list of the first candidate access cell;

[0079] If it is determined to be yes,

[0080] Determine to store the RACH report corresponding to the first candidate access cell after successfully randomly accessing the first candidate access cell; or,

[0081] Determine to store the RLF report corresponding to the first candidate access cell after successfully randomly accessing the first candidate access cell and a radio link failure occurs during subsequent communication; or,

[0082] Determine that the first candidate access cell cannot be successfully randomly accessed, obtain the network slice identifier list of the second candidate access cell, and store the minimized drive test report corresponding to the first candidate access cell;

[0083] If it is determined to be no, then store the minimized drive test report corresponding to the first candidate access cell, or obtain the network slice identifier list of the second candidate access cell, and store the minimized drive test report corresponding to the first candidate access cell.

[0084] In a possible design, the terminal device may further include:

[0085] A first deletion module, configured to delete the stored RACH reports in ascending order of importance when it is determined that the stored RACH reports meet a preset condition.

[0086] In a possible design, the generation module determines that the first candidate access cell cannot be successfully randomly accessed, including:

[0087] Determining that the number of random access attempts in the first candidate access cell is greater than a first threshold; or,

[0088] Determining that the first candidate access cell is successfully randomly accessed and the number of random access attempts after a radio link failure occurs during subsequent communication is greater than the first threshold.

[0089] In a possible design, recording the minimized drive test report further includes at least one of the network slice remapping information of the candidate access cell and the network slice redirection of the candidate access cell.

[0090] In a possible design, the receiving module is further configured to:

[0091] Receive the access category adjustment information sent by the radio access network device, where the access category adjustment information is used to increase the access categories related to the network slice service; or,

[0092] The terminal device further includes a storage module, and the storage module is configured to pre-store the access category adjustment information.

[0093] In a possible design, when the recording result includes a RACH report, the terminal device may further include:

[0094] A determination module, configured to determine that the number of stored RACH reports of the terminal device is greater than or equal to a preset number and / or the time for which the terminal device has stored the RACH reports is greater than or equal to a preset duration before the sending module sends the recording result to the radio access network device to which the serving cell belongs.

[0095] In a possible design, the terminal device may further include:

[0096] A second deletion module, configured to delete the stored RACH reports in ascending order of importance after the sending module sends the recording result to the radio access network device to which the serving cell belongs.

[0097] For the terminal device provided in the above third aspect and each possible design of the above third aspect, the beneficial effects can refer to the beneficial effects brought by the above first aspect and each possible implementation manner of the first aspect, which will not be elaborated here.

[0098] In a fourth aspect, the present application provides a radio access network device, including:

[0099] a processing module for establishing a connection with a terminal device;

[0100] a receiving module for receiving a recording result sent by the terminal device, where the recording result includes at least one of a minimized drive test (MDT) recording, a minimized drive test report, a radio link failure (RLF) report, and a random access channel (RACH) report. The MDT report includes an identifier of a candidate access cell, information indicating whether the candidate access cell supports a network slice service initiated by the terminal device, location information of the terminal device when receiving system messages, and a network slice identifier corresponding to the network slice service initiated by the terminal device. The candidate access cell is the top N cells sorted in descending order of signal strength or signal quality among the cells measured by the terminal device, where N is a preset positive integer. The RLF report includes an identifier of the cell where a radio link failure occurs after the terminal device accesses and a network slice identifier corresponding to the network slice service when the terminal device has a radio link failure. The RACH report includes an identifier of the cell accessed by the terminal device and a network slice identifier corresponding to the network slice service initiated by the terminal device.

[0101] In a possible design, the radio access network device may further include:

[0102] a sending module for sending updated network slice configuration information to the terminal device, where the updated network slice configuration information is determined by the radio access network device, a network management device, or an access and mobility management function (AMF) based on the recording results of at least one terminal device within a preset time period;

[0103] The updated network slice configuration information includes a network slice identifier list, and the network slice identifier list contains network slice identifiers corresponding to at least one network slice supported by the radio access network device. The network slice identifier list includes the network slice identifier corresponding to the network slice service initiated by the terminal device in the cell controlled by the radio access network device.

[0104] In a possible design, the processing module is further used to store the recording results, and the sending module is further used to send the recording results to other radio access network devices.

[0105] In a possible design, the processing module is further used to determine a network slice identifier list based on the MDT report, RLF report, and RACH report in the recording results of multiple terminal devices received within a preset time period.

[0106] In a possible design, the processing module is further configured to store the recording result; the sending module is further configured to send the recording result to a network management device or an Access and Mobility Management Function (AMF) network element, so that the network management device or the AMF determines, according to the minimized drive test report, RLF report, and RACH report in the recording results of multiple terminal devices received within a preset time period, the radio access network devices that need to adjust the network slice service and the corresponding list of network slice identifiers.

[0107] In a possible design, the receiving module is further configured to: before the sending module sends updated network slice configuration information to a terminal device, receive an adjustment instruction sent by a network management device or the AMF, where the adjustment instruction includes an updated list of network slice identifiers corresponding to a radio access network device.

[0108] In a possible design, the processing module is further configured to: determine updated network slice remapping information according to the recording result and the updated network slice configuration information;

[0109] The sending module is further configured to send the updated network slice remapping information to the terminal device.

[0110] In a possible design, the updated network slice configuration information further includes adjustment information for the access control information of the network slice service.

[0111] In a possible design, the adjustment information for the access control information of the network slice service is a system message.

[0112] In the system message, the access control identifier ID related to the network slice service is removed from the unified access control blocking access identity information; or,

[0113] In the system message, an access control ID unrelated to the network slice service is added to the unified access control blocking access identity information; or,

[0114] In the system message, the cell value of the unified access control blocking factor corresponding to the network slice service is reduced within a preset range; or,

[0115] In the system message, the cell value of the unified access control time corresponding to the network slice service is increased within a preset range.

[0116] In a possible design, the sending module is further configured to:

[0117] send adjustment information for the access category to the terminal device, where the adjustment information for the access category is used to increase the access category related to the network slice service; or,

[0118] The processing module is further configured to pre-store the adjustment information for the access category.

[0119] In a possible design, the processing module is further configured to:

[0120] Modify the current configuration, where the configuration includes at least one of data radio bearers supported by the radio access network device, spectrum bandwidth configuration, carrier configuration, and modulation and demodulation mode configuration.

[0121] For the radio access network device provided in the fourth aspect above and each possible design of the fourth aspect, the beneficial effects can be referred to the beneficial effects brought by the second aspect and each possible implementation manner of the second aspect, which will not be elaborated here.

[0122] Fifth aspect, the present application provides a terminal device, including: a memory and a processor;

[0123] The memory is used to store program instructions;

[0124] The processor is used to call the program instructions in the memory to execute the data transmission method in the first aspect and any possible design of the first aspect.

[0125] Sixth aspect, the present application provides a radio access network device, including: a memory and a processor;

[0126] The memory is used to store program instructions;

[0127] The processor is used to call the program instructions in the memory to execute the data transmission method in the second aspect and any possible design of the second aspect.

[0128] Seventh aspect, the present application provides a computer-readable storage medium, where an execution instruction is stored in the readable storage medium. When at least one processor of the terminal device executes the execution instruction, the terminal device executes the data transmission method in the first aspect and any possible design of the first aspect.

[0129] Eighth aspect, the present application provides a computer-readable storage medium, where an execution instruction is stored in the readable storage medium. When at least one processor of the radio access network device executes the execution instruction, the radio access network device executes the data transmission method in the second aspect and any possible design of the second aspect. Description of the Drawings

[0130] Figure 1 It is a schematic diagram of a network slice service architecture provided by the present application;

[0131] Figure 2 It is an interaction flowchart of an embodiment of the data transmission method provided by the present application;

[0132] Figure 3 It is a schematic diagram of a scenario where a terminal device stores and records a minimized drive test report;

[0133] Figure 4 An interaction flowchart of an embodiment of a data transmission method provided by this application;

[0134] Figure 5 A schematic diagram of the process for a network management device or AMF to optimize network slicing services;

[0135] Figure 6 An interaction flowchart of an embodiment of a data transmission method provided by this application;

[0136] Figure 7 An interaction flowchart of an embodiment of a data transmission method provided by this application;

[0137] Figure 8 An interaction flowchart of an embodiment of a data transmission method provided by this application;

[0138] Figure 9 An interaction flowchart of an embodiment of a data transmission method provided by this application;

[0139] Figure 10 A schematic diagram of the structure of an embodiment of a terminal device provided by this application;

[0140] Figure 11 A schematic diagram of the structure of an embodiment of a terminal device provided by this application;

[0141] Figure 12 A schematic diagram of the structure of an embodiment of a terminal device provided by this application;

[0142] Figure 13 A schematic diagram of the structure of an embodiment of a terminal device provided by this application;

[0143] Figure 14 A schematic diagram of the structure of an embodiment of a terminal device provided by this application;

[0144] Figure 15 A schematic diagram of the structure of an embodiment of a terminal device provided by this application;

[0145] Figure 16 A schematic diagram of the structure of an embodiment of a radio access network device provided by this application;

[0146] Figure 17 A schematic diagram of the structure of an embodiment of a radio access network device provided by this application;

[0147] Figure 18 A schematic diagram of the structure of an embodiment of a terminal device provided by this application;

[0148] Figure 19 A schematic diagram of the structure of a terminal device provided by this application;

[0149] Figure 20 This is a schematic structural diagram of a wireless access network device provided for this application. Specific implementation manners

[0150] The embodiments of this application can be applied to a wireless communication system. It should be noted that the wireless communication systems mentioned in the embodiments of this application include but are not limited to: Narrow Band-Internet of Things (NB-IoT), Global System for Mobile Communications (GSM), Enhanced Data rate for GSM Evolution (EDGE), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access 2000 (CDMA2000), Time Division-Synchronization Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), and the three application scenarios of the next-generation 5G mobile communication system, namely enhanced mobile broadband (eMBB), URLLC, and massive machine-type communications (mMTC).

[0151] The communication devices involved in this application mainly include wireless access network devices or terminal devices. In this application, if the sending end is a wireless access network device, then the receiving end is a terminal device; if the sending end is a terminal device, then the receiving end is a wireless access network device.

[0152] Among them, the terminal device in the embodiment of the present application may be a wireless terminal. A wireless terminal may be a device that provides voice and / or other service data connectivity to users, a handheld device with wireless connection capabilities, or other processing devices connected to a wireless modem. The wireless terminal may communicate with one or more core networks via a radio access network (RAN). The wireless terminal may be a mobile terminal, such as a mobile phone (or a "cellular" phone) and a computer with a mobile terminal. For example, it may be a portable, pocket-sized, handheld, computer-integrated, or vehicle-mounted mobile device that exchanges voice and / or data with the wireless access network. For example, devices such as personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, and personal digital assistants (PDAs). The wireless terminal may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile, a remote station, a remote terminal, an access terminal, a user terminal, a user agent, a user device or user equipment, which is not limited herein.

[0153] The present application describes various embodiments in connection with a radio access network device. The radio access network device may be a device for communicating with a terminal device. For example, it may be a base transceiver station (BTS) in a GSM system or a CDMA system, a node B (NB) in a WCDMA system, an evolved NodeB (eNB or eNodeB) in an LTE system, a next-generation eNodeB (ng-eNB) in an LTE system, or the radio access network device may be a relay station, an access point (AP), a vehicle-mounted device, a wearable device, and a network-side device in a 5G network or a radio access network device in a future-evolved public land mobile network (PLMN). For example, it may be a new-generation node B (gNB or gNodeB).

[0154] The present application can be applied to the network slicing service scenario under a 5G communication system. The communication system of the present application may include a radio access network device and a terminal device. Figure 1 FIG. is a schematic diagram of a network slicing service architecture provided for the present application, as Figure 1 shown. The network slicing service architecture mainly involves a terminal device, a radio access network device, and a core network device (including an access and mobility management function (AMF)). Among them, Figure 1 3 network slices are shown. One network slice can be deployed in different cells, and different network slices support different services. The present application mainly involves network slice selection in the process of the terminal device accessing the core network via the RAN under the scenario where different network slices support different services. Specifically, the terminal device reports a recording result related to the network slice information to the radio access network device, and the radio access network device adjusts the network slice services it can support according to the recording results of the terminal device received within a preset time period to improve the success rate of the terminal device accessing the network slice.

[0155] It should be noted that the embodiments of the present application are not limited to the above network slicing service architecture, and can also be applied to future other communication systems, such as the 6th generation (6G) system architecture. Moreover, the names of the various network elements used in the embodiments of the present application above may maintain similar functions in future communication systems, but the names will change.

[0156] In the related art, the recording result sent by the UE to the base station is the related measurement result of the UE under one or more cells. A cell can support multiple network slices, different network slices support different services, and different cells can deploy different network slices. At this time, how the UE can more effectively report the recording result is an urgent problem to be solved. To solve this problem, the present application provides a data transmission method and device. The recording result is sent from the terminal device to the radio access network device to which the serving cell belongs. The recording result includes at least one of a recorded minimized drive test report, an RLF report, and a RACH report. The recorded minimized drive test report carries the identifier of the candidate access cell, the information indicating whether the candidate access cell supports the network slice service initiated by the terminal device, the location information of the terminal device when receiving the system message of the candidate access cell, and the network slice identifier corresponding to the network slice service initiated by the terminal device. The RLF report carries the identifier of the cell where the radio link failure occurs after the terminal device accesses and the network slice identifier corresponding to the network slice service when the terminal device has a radio link failure. The RACH report carries the identifier of the cell accessed by the terminal device and the network slice identifier corresponding to the network slice service initiated by the terminal device. Since the recording result carries information related to the network slice service, for the recorded minimized drive test report, the radio access network device can know whether each candidate access cell supports the network slice service initiated by the terminal device and the network slice identifier corresponding to the network slice service initiated by the terminal device in the corresponding candidate access cell; for the RLF report, the radio access network device can know the network slice identifier corresponding to the network slice service initiated by the terminal device in the cell where the terminal device has accessed and has a radio link failure; for the RACH report, the radio access network device can know the network slice identifier corresponding to the network slice service initiated by the terminal device in the accessed cell; so that when the radio access network device can determine that it needs to adjust the network slices it supports according to the information related to the network slice service carried in the recording results sent by multiple terminal devices within a preset time period, it adjusts the network slices it supports, thereby improving the success rate of the terminal device accessing the network slice. Thus, the problem of how the terminal device reports the recording result is solved, and further, the radio access network device can adjust the network slices it supports according to the recording result reported by the terminal device.

[0157] The data transmission method and device provided by the present application will be described in detail below with reference to the accompanying drawings.

[0158] Figure 2 It is an interaction flowchart of an embodiment of a data transmission method provided by the present application. As Figure 2 shown, the method of this embodiment may include:

[0159] S101. The terminal device generates a recording result.

[0160] Exemplarily, the terminal device generates a recording result, specifically: the terminal device executes the following S1011 - S1014 according to the reference signal information of the measured candidate access cells. The reference signal information of the candidate access cells can be the reference signal receiving power (RSRP) or (reference signal received quality, RSRQ). The candidate access cells are the top N cells sorted in descending order of signal strength or signal quality among the cells measured by the terminal device, where N is a preset positive integer.

[0161] S1011. The terminal device obtains the network slice identifier list of the first candidate access cell.

[0162] Specifically, it can be obtained by reading the network slice information in the system broadcast of the first candidate access cell. The network slice identifier list can contain one or more network slice identifiers.

[0163] S1012. The terminal device determines whether the first candidate access cell supports the network slice service initiated by the terminal device according to the network slice identifier list of the first candidate access cell.

[0164] S1013. If it is determined that the first candidate access cell supports the service, the terminal device determines to store the RACH report corresponding to the first candidate access cell after successfully randomly accessing the first candidate access cell; or,

[0165] The terminal device determines to store the RLF report corresponding to the first candidate access cell after successfully randomly accessing the first candidate access cell and experiencing a radio link failure during subsequent communication; or,

[0166] The terminal device determines that it fails to successfully randomly access the first candidate access cell, obtains the network slice identifier list of the second candidate access cell, and stores the minimized drive test report corresponding to the first candidate access cell.

[0167] As an implementable method, when the terminal device determines that it fails to successfully randomly access the first candidate access cell, there are two optional methods as follows:

[0168] Method 1. The terminal device determines that the number of random access attempts initiated in the first candidate access cell is greater than the first threshold, and at this time the terminal device is in the idle state.

[0169] Method 2. The terminal device determines that the number of random access attempts initiated again after successfully randomly accessing the first candidate access cell and experiencing a radio link failure during subsequent communication is greater than the first threshold.

[0170] S1014. If the determination result is negative, the terminal device stores the recorded minimized drive test report corresponding to the first candidate access cell; otherwise, the terminal device obtains the network slice identifier list of the second candidate access cell and stores the recorded minimized drive test report corresponding to the first candidate access cell.

[0171] Specifically, if the terminal device determines that it fails to randomly access the first candidate access cell or determines that the first candidate access cell does not support the network slice service initiated by the terminal device, it stores the recorded minimized drive test report corresponding to the first candidate access cell and attempts to obtain the network slice identifier list of the second candidate access cell. If the network slice identifier list of the second candidate access cell can be obtained, it determines whether the second candidate access cell supports the network slice service initiated by the terminal device according to the network slice identifier list of the second candidate access cell. If the determination result is positive, it initiates a random access in the second candidate access cell and stores the RACH report corresponding to the second candidate access cell after successfully randomly accessing the second candidate access cell; otherwise, if the terminal device determines that after successfully randomly accessing the second candidate access cell and a radio link failure occurs during the subsequent communication process, it stores the RLF report corresponding to the second candidate access cell; or, if the terminal device fails to randomly access the second candidate access cell, it continues to attempt to obtain the network slice identifier list of other candidate access cells until the terminal device successfully randomly accesses a cell. If the terminal device fails to obtain the network slice identifier list of the second candidate access cell, for example, the terminal device is in the central coverage area of the first candidate cell, it stores the recorded minimized drive test report corresponding to the first candidate access cell.

[0172] Figure 3 It is a schematic diagram of a scenario where a terminal device stores a recorded minimized drive test report, as Figure 3 shown Figure 3The first cell, the second cell, and the third cell among them are respectively the top three candidate access cells with the best signal strength (or signal quality) measured by the terminal device. None of these three cells support the network slice service initiated by the terminal device, such as network slice A. The fourth cell with the fourth-highest signal strength (or signal quality) supports the network slice service initiated by the terminal device. The terminal device first selects to camp on the first cell and achieve downlink synchronization, obtains the network slice identifier list of the first cell by listening to the system message broadcast of the first cell. Since there is no network slice A in the network slice identifier list of the first cell, it is known that the first cell does not support the network slice service initiated by the terminal device. Then the terminal device records the network slice-related information into the recorded minimized drive test report. Then the terminal device selects to camp on the second cell in the order of signal strength from large to small (or signal quality from good to bad) and achieve downlink synchronization, obtains the network slice identifier list of the second cell by listening to the system message broadcast of the second cell. Since there is no network slice A in the network slice identifier list of the second cell, it is known that the second cell also does not support the network slice service initiated by the terminal device. Then the terminal device records the network slice-related information of the second cell into the recorded minimized drive test report, that is, retains the network slice-related information of the first cell and records the network slice-related information of the second cell into the recorded minimized drive test report. Then the terminal device selects to camp on the third cell in the order of signal strength from large to small (or signal quality from good to bad) and achieve downlink synchronization, and obtains the network slice identifier list of the third cell by listening to the system message broadcast of the third cell. Since there is no network slice A in the network slice identifier list of the third cell, it is known that the third cell also does not support the network slice service initiated by the terminal device. Then the terminal device records the network slice-related information of the third cell into the recorded minimized drive test report, that is, retains the network slice-related information of the first cell and the second cell and records the network slice-related information of the third cell into the recorded minimized drive test report. Until the terminal device establishes a connection in the fourth cell and sends the recorded minimized drive test report to the fourth cell. For the first cell, the network slice-related information stored in the recorded minimized drive test report is the identifier of the first cell, the information indicating that the first cell does not support the network slice service initiated by the terminal device, the location information of the terminal device when receiving the system message of the candidate access cell, and the network slice identifier corresponding to the network slice service initiated by the terminal device.

[0173] Specifically, the recording result generated by the terminal device in S101 includes at least one of a recorded minimized drive test report, an RLF report, and a RACH report. Among them, the recorded minimized drive test report includes the identifier of the candidate access cell, information indicating whether the candidate access cell supports the network slice service initiated by the terminal device, the location information of the terminal device when receiving the system message of the candidate access cell, and the network slice identifier corresponding to the network slice service initiated by the terminal device. The location information of the terminal device when receiving the system message of the candidate access cell may be the global positioning system (GPS) location information of the terminal device when receiving the system message.

[0174] Among them, the information indicating whether the candidate access cell supports the network slice service initiated by the terminal device may be: the network slice identifier corresponding to the network slice service initiated by the terminal device and the network slice identifiers corresponding to the network slices supported by the radio access network device to which the candidate access cell belongs. For example, the network slice identifier corresponding to the network slice service initiated by the terminal device is 1, and the network slice identifiers corresponding to the network slices supported by the radio access network device to which the candidate access cell belongs include 1, 2, and 3, and 1 is among them. Therefore, it can be known that the candidate access cell supports the network slice service initiated by the terminal device. If 1 is not included, it can be known that the candidate access cell does not support the network slice service initiated by the terminal device.

[0175] Alternatively, the information indicating whether the candidate access cell supports the network slice service initiated by the terminal device may also be: the network slice identifier corresponding to the network slice service initiated by the terminal device and the indication information indicating whether the radio access network device to which the candidate access cell belongs supports the network slice service initiated by the terminal device. For example, the indication information indicating whether the radio access network device to which the candidate access cell belongs supports the network slice service initiated by the terminal device is a boolean option, that is, "yes" or "no", or the information indicating "yes" or "no", such as 1 represents "yes" and 0 represents "no".

[0176] Alternatively, the information indicating whether the candidate access cell supports the network slice service initiated by the terminal device may also be: the network slice identifiers corresponding to the network slices supported by the radio access network device to which the candidate access cell belongs and the indication information indicating whether the terminal device wants to initiate the network slice service supported by the radio access network device. For example, the indication information indicating whether the terminal device wants to initiate the network slice service supported by the radio access network device is a boolean option, that is, "yes" or "no", or the information indicating "yes" or "no", such as 1 represents "yes" and 0 represents "no".

[0177] Furthermore, in an implementable manner, the recorded minimized drive test report may further include at least one of the network slice remapping information of the candidate access cell and the network slice redirection information of the candidate access cell. Specifically, the terminal device learns the network slice remapping information of the candidate access cell and the network slice redirection information of the candidate access cell by listening to the system message broadcast. Among them, network slice remapping means giving one or more corresponding network slice information for a certain protocol data unit (PDU) session of the terminal device. Specifically, one PDU session identifier corresponds to one or more network slice identifiers, and this PDU session can be initiated in one of the network slices corresponding to these one or more network slice identifiers. By carrying the network slice remapping information of the candidate access cell in the recorded minimized drive test report, the radio access network device that receives the recorded result sent by the terminal device can adjust the new network slice remapping information according to the network slice remapping information originally stored by the terminal device (i.e., the network slice remapping information of the candidate access cell included in the recorded minimized drive test report), and can send the new network slice remapping information to the terminal device through a radio resource control (RRC) message, so that the terminal device can successfully initiate a network slice service. For example, as shown in Table 1 below, the network slice remapping information originally stored by the terminal device and the adjusted network slice remapping information are as follows: the network slice remapping information originally stored by the terminal device is that PDU session 1 corresponds to network slices 1, 2, and 3. The radio access network device learns from the recorded result of the terminal device received that there are fewer terminal devices actually needing to access network slice 1, while there are more terminal devices actually needing to access network slice 4. Therefore, it can adjust the network slice remapping information according to the learned information. The adjusted network slice remapping information is that PDU session 1 corresponds to network slices 4, 2, and 3. The radio access network device sends the adjusted network slice remapping information to the terminal device through an RRC message, which can enable the terminal device to successfully initiate a network slice service and increase the probability of the terminal device accessing the network slice.

[0178] Table 1 Network Slice Remapping Information

[0179]

[0180] Network slice redirection means that a radio access network device redirects a terminal device to a cell supporting network slice services to initiate the corresponding network slice service. By carrying the network slice redirection information of the candidate access cell in the recorded minimized drive test report, the radio access network device that receives the recorded result sent by the terminal device can redirect the terminal device to a cell supporting network slice services to initiate the corresponding network slice service. Table II below shows the original network slice redirection information (i.e., the network slice redirection information of the candidate access cell in the recorded minimized drive test report) and the adjusted network slice redirection information. In the original network slice redirection information, the cells supporting network slice 1 are cell 1, cell 2, and cell 3. The radio access network device learns from the recorded result of the terminal device it receives that: there are fewer terminal devices actually needing to access cell 1, while there are more terminal devices actually needing to access cell 4. Therefore, the network slice redirection information can be adjusted according to the information obtained. In the adjusted network slice redirection information, the cells supporting network slice 1 are cell 4, cell 2, and cell 3, so that the terminal device can successfully access cell 4 and the probability of the terminal device accessing the network slice can be increased.

[0181] Table II Network Slice Redirection Information

[0182]

[0183]

[0184] Optionally, Table III shows a possible message structure of the recorded minimized drive test report, as shown in Table III:

[0185] Table III Message Structure of the Recorded Minimized Drive Test Report

[0186] Record Minimized Drive Test Report > Network Slice Identifier corresponding to the network slice service initiated by the terminal device > Identifier of the candidate access cell > Whether the candidate access cell supports the network slice service initiated by the terminal device > Information indicating the signal strength and signal quality of the candidate access cell > Location information of the terminal device when receiving the system message of the candidate access cell > Network slice remapping information of the candidate access cell > Network slice redirection information of the candidate access cell > Timestamp > Tracking reference information > Tracking record session > Parameter tracking collection entity identity information > List of related information

[0187] The RLF report includes the identifier of the cell that has been accessed and experienced a radio link failure and the network slice identifier corresponding to the network slice service initiated by the terminal device. The RACH report includes the identifier of the accessed cell and the network slice identifier corresponding to the network slice service initiated by the terminal device. Among them, the network slice identifier corresponding to the network slice service initiated by the terminal device can be the single network slice selection assistance information (S-NSSAI) mentioned in the existing 3GPP protocol, or other flags that can identify the type of network slice service that the terminal device hopes to initiate.

[0188] Optionally, Table IV shows a possible message structure of the RLF report, as shown in Table IV:

[0189] Table IV Message Structure of the RLF Report

[0190] RLF Report > Network Slice Identifier corresponding to the network slice service initiated by the terminal device > Identifier of the cell that has been accessed and experienced a radio link failure Identifier of the re-established cell Time from handover start to connection failure Time since connection failure until now Connection failure type (RLF or handover failure) Location information Absolute radio frequency channel number Random access frequency and bandwidth Subcarrier spacing Starting frequency point of Message 1 Subcarrier spacing of Message 1 Frequency division multiplexing situation of Message 1 Random access order

[0191] Optionally, Table 5 shows a possible message structure of the RACH report, as shown in Table 5:

[0192] Table 5 Message structure of the RACH report

[0193]

[0194] According to the generation process of the above recording results, it can be understood that the number of minimized drive test reports included in the recording results can be one or more, the RLF reports can be one or more, and the number of RACH reports can be one or more.

[0195] Currently, the standard stipulates that the terminal device has constraints on the carrying quantity and carrying duration of the RACH report. For example, the terminal device can carry at most eight RACH reports, and the carrying duration of the RACH report is at most 48 hours. When the specified carrying quantity and carrying duration are exceeded, the terminal device will delete some RACH reports, making it difficult to fully utilize the value of the RACH report. To solve this problem, in this embodiment, as an implementable method, when the terminal device determines that the stored RACH reports meet the preset conditions, the terminal device deletes the stored RACH reports in ascending order of importance. The preset conditions can be that the carrying quantity of the RACH report is greater than or equal to the preset threshold, or the carrying duration of the RACH report is greater than or equal to the preset threshold. For example, the carrying quantity of the RACH report is greater than eight times, or the carrying duration of the RACH report is greater than 48 hours, or both are satisfied, then it is determined that the preset conditions are met. The determination conditions for the importance of the RACH report can be: the importance of the RACH report of the cell that supports the network slice service initiated by the terminal device is higher than that of the RACH report of the cell that does not support the network slice service initiated by the terminal device; or, the importance of the RACH report of the cell with good signal quality (or high signal strength) is higher than that of the RACH report of the cell with bad signal quality (or low signal strength). By deleting the stored RACH reports in ascending order of importance, the storage time of the RACH reports with high importance can be extended, and the utilization value of the RACH reports can be fully utilized.

[0196] S102. The terminal device sends the recording result to the radio access network device to which the serving cell belongs.

[0197] Wherein, the serving cell refers to the cell to which the terminal device successfully accesses by initiating random access.

[0198] Specifically, in the new radio (NR) protocol, a terminal device has three states: RRC idle state (RRC_IDLE), RRC connected state (RRC_connected), and RRC inactive state (RRC_inactive). The terminal device can send the recorded results to the radio access network device belonging to the serving cell when it is in the connected state or the inactive state. Specifically, in an implementable manner, the terminal device can send the recorded results to the radio access network device belonging to the serving cell when it is in the connected state. At this time, S102 can specifically be:

[0199] After the terminal device successfully performs random access in the serving cell, it sends the recorded minimized drive test report to the radio access network device belonging to the serving cell. After the terminal device successfully performs random access in the serving cell, the radio access network device may send a RACH report request to the terminal device, and the terminal device sends a RACH report to the radio access network device according to the RACH report request. After the terminal device successfully performs random access in the serving cell, the radio access network device sends a RLF report request to the terminal device, and the terminal device sends a RLF report to the radio access network device according to the RLF report request.

[0200] In another implementable manner, the terminal device can send the recorded results to the radio access network device belonging to the serving cell when it is in the inactive state. When in the inactive state, the terminal device may not establish an RRC connection with the radio access network device and directly send small data to the radio access network device. At this time, S102 can specifically be:

[0201] The terminal device sends small data to the radio access network device, and the recorded results are carried in the small data, that is, the terminal device sends the recorded results to the radio access network device in the small data.

[0202] After the radio access network device belonging to the serving cell receives the recorded results sent by the terminal device, there are two implementable manners. In one implementable manner, S103 is then executed. In another implementable manner, S103’ is then executed.

[0203] S103: The radio access network device belonging to the serving cell stores the recorded results sent by the terminal device and forwards the recorded results to other radio access network devices.

[0204] Specifically, it can be that the radio access network device belonging to the serving cell forwards through the network side interface (X-n) interface between radio access network devices to all or some of the radio access network devices that have established an X-n interface with the radio access network device belonging to the serving cell, and other radio access network devices forward through the X-n interface to the radio access network devices that have established an X-n interface with them.

[0205] S104. The radio access network device determines updated network slice configuration information according to the recording results of at least one terminal device received within a preset time period.

[0206] Specifically, the updated network slice configuration information may include a network slice identifier list. First, the radio access network device determines the network slice identifier list according to the recorded minimum drive test report, RLF report, and RACH report in the recording results of at least one terminal device received within a preset time period. Specifically, the network slice identifier list contains the network slice identifiers corresponding to at least one network slice supported by the radio access network device, and the network slice identifier list includes the network slice identifiers corresponding to the network slice services initiated by the terminal device in the cell controlled by the radio access network device.

[0207] It should be noted that the radio access network device executing S104 may be the radio access network device to which the serving cell belongs. The radio access network device to which the serving cell belongs may also receive the recording results of other terminal devices forwarded by other radio access network devices. The radio access network device executing S104 may also be other radio access network devices that receive the recording results of at least one terminal device.

[0208] Specifically, the radio access network device determines a network slice identifier list based on the recorded minimized drive test reports, RLF reports, and RACH reports in the recording results of at least one terminal device received within a preset time period. This network slice identifier list is an updated network slice identifier list. Since the recorded minimized drive test report carries the identifier of the candidate access cell, information indicating whether the candidate access cell supports the network slice service initiated by the terminal device, the location information of the terminal device when receiving the system message of the candidate access cell, and the network slice identifier corresponding to the network slice service initiated by the terminal device, the radio access network device can, based on the recorded minimized drive test report, know whether each candidate access cell supports the network slice service initiated by the terminal device, the network slice service initiated by the terminal device in the corresponding candidate access cell, and the location information of the terminal device when receiving the system message of the candidate access cell. Since the RLF report carries the identifier of the cell that has been accessed and has experienced a radio link failure and the network slice identifier corresponding to the network slice service initiated by the terminal device, the radio access network device can, based on the RLF report, know the network slice identifier corresponding to the network slice service initiated by the terminal device in the cell that has been accessed and has experienced a radio link failure. Since the RACH report carries the identifier of the accessed cell and the network slice identifier corresponding to the network slice service initiated by the terminal device, the radio access network device can, based on the RACH report, know the network slice identifier corresponding to the network slice service initiated by the terminal device in the accessed cell. Thus, the radio access network device can determine whether it needs to adjust the network slices it supports based on the network slice-related information obtained from at least one of the above three reports. If adjustment is needed, it adjusts the network slices it supports. For example, it can modify the network slice identifier corresponding to the network slices that the radio access network device can support, that is, the network slice identifier list. The modified network slice identifier list includes the network slice identifier corresponding to the network slice service initiated by the terminal device in the cell controlled by the radio access network device. Thus, the network slice identifier list corresponding to the network slices supported after the adjustment of the radio access network device can include the network slice identifier corresponding to the network slice service initiated by the terminal device.For example, for an RACH report, if the RACH report carries the identifier of the first cell that has been accessed and the network slice identifier 1 corresponding to the network slice service initiated by the terminal device, indicating that the terminal device has successfully initiated the network slice service corresponding to the network slice identifier 1 in the first cell, the radio access network device determines that there is no need to modify the network slice identifier 1. Specifically, the network slice identifier 1 is retained in the network slice list supported by itself; for recording the minimized drive test report and the RLF report, the network slice service corresponding to the minimized drive test report is a network slice service that has not been successfully initiated, and the network slice service corresponding to the RLF report is a network slice service that the terminal device has initiated but has experienced a radio link failure. The radio access network device determines that it needs to adjust the network slices supported by itself according to the minimized drive test report and the RLF report. For example, if the network slice identifier corresponding to the network slice service initiated by the terminal device carried in the minimized drive test report is 2, when the radio access network device adjusts the network slices supported by itself, specifically, it adjusts the priority order of the network slice identifier 2 in the network slice list supported by itself to reduce the priority of the network slice identifier 2, or if the network slice identifier corresponding to the network slice service initiated by the terminal device carried in the RLF report is 3, when the radio access network device adjusts the network slices supported by itself, specifically, it adjusts the priority order of the network slice identifier 3 in the network slice list supported by itself to reduce the priority of the network slice identifier 2. Thus, the success rate of the terminal device accessing the network slice can be improved.

[0209] It should be noted that when the radio access network device modifies the network slice identifier list corresponding to the network slices supported by itself, the radio access network device also needs to modify the current configuration. For example, the data radio bearers, spectrum bandwidth configuration, carrier configuration, and modulation and demodulation mode configuration supported by the radio access network device, etc.; in addition, the radio access network device also needs to send configuration update information (config update) to the core network device (such as the AMF). The configuration update information includes the modified network slice identifier list of the radio access network device, which is used to inform the core network device that the network slice identifier list supported by the radio access network device has changed.

[0210] S105. The radio access network device sends updated network slice configuration information to the terminal device.

[0211] Specifically, the updated network slice configuration information may include the network slice identifier list in S104. The radio access network device can broadcast the updated network slice configuration information to the terminal device through the system message. The radio access network device can directly add (or update) the network slice identifier list in the system message SIB1.

[0212] In an implementable manner, further, on the basis of the above method, it may further include:

[0213] S106. The radio access network device determines updated network slice remapping information according to the recording result and the updated network slice configuration information, and the radio access network device sends the updated network slice remapping information to the terminal device. Specifically, the radio access network device determines the updated network slice remapping information according to the network slices supported by itself in the recording result and the updated network slice configuration information. For example, the original remapping relationship stored in the terminal device is to map from network slice service 1 to network slice service 2 or network slice service 3, but the current radio access network device only supports network slice service 4 and does not support network slice service 1, network slice service 2, and network slice service 3. Therefore, the radio access network device determines the updated network slice remapping information as: the new mapping relationship "from network slice service 1 to the slice list including network slice 4". The radio access network device may send the updated network slice remapping information to the terminal device through an RRC message, enabling the terminal device to successfully initiate a network slice service.

[0214] In an implementable manner, further, the updated network slice configuration information may further include adjustment information for the access control information of the network slice service. By carrying the adjustment information for the access control information of the network slice service, the probability of the terminal device accessing non-network slice services can be reduced, enabling the terminal device to preferentially access network slice services.

[0215] Optionally, the adjustment information for the access control information of the network slice service may be a system message. The radio access network device updates the access control parameter set list (uac-barring infosetList) cell in SIB1. Specifically, there are the following four optional methods:

[0216] 1. Exclude the access control identifier (ID) related to the network slice service from the unified access control barring access identity information (uac-barring for accessidentity) in the system message.

[0217] 2. Add an access control ID unrelated to the network slice service to the unified access control barring access identity information (uac-barring for accessidentity) in the system message. Specifically, the access identity sequence (access identity number) 3-10 (the original reserved part) can be defined as the access control ID related to the network slice service to form a new access ID list, which is pre-stored in the terminal device and the radio access network device. Table VI shows a possible access ID list as follows.

[0218] Table VI Access ID List

[0219]

[0220] 3. When the value of the unified access control barring factor (uac-barringfactor) corresponding to the network slice service in the system message decreases within a preset range, the probability of allowing non-network-slice-related services to access the network can be appropriately reduced.

[0221] 4. When the value of the unified access control time (uac-barring time) corresponding to the network slice service in the system message increases within a preset range, the duration required for network-slice-related services to access the network can be appropriately increased.

[0222] Among them, the access control parameter set list represents the access control parameter set list; the unified access control barring access identity information represents a certain type of access identity (access id) corresponding to this access control list, where the access ID represents several types of access event types initiated by the terminal device (including the network slice service types initiated by the terminal device). Each terminal device is assigned an access ID during network registration; the unified access control barring factor represents the probability that a terminal device of this type of access ID is allowed to make an access attempt during access restriction check; the unified access control time represents the shortest time elapsed after a terminal device of this type of access ID is prohibited from accessing and before a new access attempt is made. In addition, an access ID that does not appear in the access control parameter set list indicates that it is not restricted by network access.

[0223] In an implementable manner, further, on the basis of the above method, it may further include:

[0224] S107. The radio access network device sends adjustment information for the access category to the terminal device, and the adjustment information for the access category is used to increase the access category related to the network slice service; or,

[0225] The radio access network device prestores the adjustment information for the access category.

[0226] Specifically, Table VII shows a possible list of access categories (access category) as follows.

[0227] Table VII Access Category List

[0228]

[0229] The radio access network device sends adjustment information for access categories to the terminal device, or the radio access network device and the terminal device pre-store adjustment information for access categories. The adjustment information for access categories is used to increase access categories related to network slice services, which can increase the probability of the terminal device accessing the network slice and reduce the probability of the terminal device accessing non-network slice services.

[0230] In the data transmission method provided in this embodiment, the terminal device generates a recording result and sends the recording result to the radio access network device to which the serving cell belongs. The recording result includes at least one of a minimized drive test report, an RLF report, and a RACH report. The minimized drive test report, the RLF report, and the RACH report all carry information related to network slice services. The radio access network device can learn whether each candidate access cell supports the network slice service initiated by the terminal device and the network slice identifier corresponding to the network slice service initiated by the terminal device in the corresponding candidate access cell according to the recorded minimized drive test report. The radio access network device can learn the network slice identifier corresponding to the network slice service initiated by the terminal device in the cell where the terminal device has accessed and a radio link failure has occurred according to the RLF report. The radio access network device can learn the network slice identifier corresponding to the network slice service initiated by the terminal device in the accessed cell according to the RACH report. Therefore, when the radio access network device can determine that it needs to adjust the network slices it supports based on the network slice-related information learned from at least one of the above three reports, it adjusts the network slices it supports, thus solving the problem of how the terminal device reports the recording result in different network slices supporting different service scenarios. Furthermore, when the radio access network device can determine that it needs to adjust the network slices it supports based on the recording result reported by the terminal device, it adjusts the network slices it can support, improving the success rate of the terminal device accessing the network slice.

[0231] Figure 4 It is an interaction flowchart of an embodiment of the data transmission method provided in this application. As Figure 4 shown, the difference from the embodiment shown in Figure 2 is that Figure 2 in the embodiment shown, the radio access network device determines which network slices it needs to adjust and how to adjust according to the recording results of at least one terminal device received within a preset time period. In this embodiment, the radio access network device sends the recording results to the network management device or the AMF, and the network management device or the AMF determines which radio access network devices need to adjust the network slice service and how to adjust according to the recording results of at least one terminal device received within a preset time period. The following is a detailed description. As Figure 4 shown, after S102 of the method in this embodiment, it may further include.

[0232] S103’. The radio access network device stores the recording result and sends the recording result to the network management device or the AMF.

[0233] S104’. The network management device or the AMF determines, according to the recording results of at least one terminal device received within a preset time period, the radio access network devices that need to adjust network slices and the corresponding network slice identifier lists.

[0234] Specifically, the network management device or the AMF may perform statistical analysis and judgment according to the recording minimized drive test reports, RLF reports, and RACH reports in the recording results of at least one terminal device received within a preset time period to determine the radio access network devices that need to adjust network slices. The determined radio access network devices that need to adjust network slices may be the radio access network devices to which the cells in the RAN-based notification area list belong, or the radio access network devices to which the cells in the tracking area (TA) list belong, or the radio access network devices to which the cells in other cell lists configured by the network management belong. This embodiment does not make specific limitations thereto.

[0235] Optionally, the network management device performs statistical analysis and judgment according to the recording minimized drive test reports, RLF reports, and RACH reports in the recording results of at least one terminal device received within a preset time period to determine the radio access network devices that need to adjust network slices, which may be beneficial for network planning and network optimization. This embodiment does not make specific limitations thereto.

[0236] Figure 5 FIG. is a schematic diagram of a process for a network management device or an AMF to optimize network slice services. As Figure 5 shown, the terminal device sends the recording result to the radio access network device to which the serving cell belongs. The radio access network device to which the serving cell belongs sends the recording result to the network management device or the AMF. The network management device or the AMF finds through statistics of the recording results of the terminal devices within a preset time period and within a preset range that the number of terminal devices initiating network slice service 1 within the preset range is the largest, but the number of radio access network devices supporting network slice service 1 is small, thus resulting in a poor access experience for the terminal devices. Therefore, the network management device or the AMF sends an adjustment instruction to the radio access network devices (such as radio access network device 1, radio access network device 2, and radio access network device 3 shown in the figure) near the geographical location of the terminal devices that hope to initiate network slice 1, notifying these radio access network devices to change other network slice services to network slice service 1.

[0237] S105’: The network management device or the AMF sends an adjustment instruction to the radio access network device. The adjustment instruction includes an updated network slice identifier list corresponding to the radio access network device.

[0238] Optionally, the adjustment instruction may further include an adjustment to the signal of the radio access network device. The radio access network device here may be the radio access network device to which the serving cell belongs, or it may be other radio access network devices.

[0239] S106’: The radio access network device sends the updated network slice configuration information to the terminal device.

[0240] Specifically, the updated network slice configuration information may include the network slice identifier list carried in the adjustment instruction. The network slice identifier list is the network slice identifier corresponding to the network slice services supported by the radio access network device, and the network slice identifier list includes the network slice identifier corresponding to the network slice service initiated by the terminal device in the cell controlled by the radio access network device.

[0241] In an implementable manner, further, on the basis of the above method, it may further include:

[0242] S107’: The radio access network device determines the updated network slice remapping information according to the recording result and the updated network slice configuration information, and the radio access network device sends the updated network slice remapping information to the terminal device.

[0243] The specific relevant description is the same as the relevant description of S106 in the Figure 2 illustrated embodiment, and will not be elaborated here.

[0244] In an implementable manner, further, the updated network slice configuration information may further include adjustment information for the access control information of the network slice service. The adjustment information for the access control information of the network slice service is a system message. In the system message, the access control identifier ID related to the network slice service is removed from the unified access control blocking access identity information. Or, an access control ID unrelated to the network slice service is added to the unified access control blocking access identity information in the system message. Or, the value of the unified access control blocking factor cell in the system message is reduced within a preset range. Or, the value of the unified access control time cell in the system message is increased within a preset range.

[0245] The specific relevant description is the same as the relevant description in the Figure 2 illustrated embodiment, and will not be elaborated here.

[0246] In an implementable manner, further, on the basis of the above method, it may further include:

[0247] S108’: The radio access network device sends adjustment information for access categories to the terminal device, and the adjustment information for access categories is used to increase access categories related to network slice services; or,

[0248] The radio access network device pre-stores adjustment information for access categories.

[0249] Specific relevant descriptions are the same as the relevant descriptions in S107 in the Figure 2 illustrated embodiment, and will not be elaborated here.

[0250] The above several implementable methods are all methods for the radio access network device to adjust its own network slice services. After receiving the recording result of the terminal device, in addition to adjusting its own network slice services, the radio access network device can also make the following adjustments. Further, the method of this embodiment may further include:

[0251] S109’: The radio access network device adjusts the transmission signal power of at least one network slice supported by itself according to the recording results of at least one terminal device received within a preset time period. The transmission signal power may be, for example, at least one of the power of SSB, the power of CSI-RS, and the RSRP power of SUL.

[0252] By the radio access network device adjusting the transmission signal power of at least one network slice supported by itself according to the recording results of at least one terminal device received within a preset time period. For example, if the radio access network device supports network slice 1, network slice 2, and network slice 3, and the radio access network device learns from the recording results of at least one terminal device received within a preset time period that the number of terminal devices accessing network slice 1 is large and the number of terminal devices accessing network slice 2 is small, it increases the transmission signal power of network slice 1 and reduces the transmission signal power of network slice 2, thereby increasing the probability of terminal devices accessing the network slice.

[0253] S110’: The radio access network device adjusts the RACH resources of at least one network slice supported by itself according to the recording results of at least one terminal device received within a preset time period.

[0254] By the radio access network device adjusting the RACH resources of at least one network slice supported by itself according to the recording results of at least one terminal device received within a preset time period, it can increase the access probability of terminal devices initiating network slice services, improve the access speed of terminal devices initiating network slice services, and reduce the probability and number of random access failures of terminal devices initiating network slice services.

[0255] It is also possible to execute both S109’ and S110’.

[0256] In the data transmission method provided in this embodiment, the terminal device generates a recording result and sends the recording result to the radio access network device to which the serving cell belongs. The recording result includes at least one of a minimized drive test report, an RLF report, and a RACH report. The minimized drive test report, the RLF report, and the RACH report all carry information related to the network slice service. The radio access network device sends the received recording result to the network management device or the AMF. The network management device or the AMF can learn whether each candidate access cell supports the network slice service initiated by the terminal device and the network slice identifier corresponding to the network slice service initiated by the terminal device in the corresponding candidate access cell according to the recorded minimized drive test report. The network management device or the AMF can learn the network slice identifier corresponding to the network slice service initiated by the terminal device in the cell where the terminal device has accessed and a radio link failure has occurred according to the RLF report. The network management device or the AMF can learn the network slice identifier corresponding to the network slice service initiated by the terminal device in the accessed cell according to the RACH report. Therefore, the network management device or the AMF can determine which radio access network devices need to adjust the network slice service and how to adjust it according to the recording results of at least one terminal device received within a preset time period, and send an adjustment instruction to the radio access network device that needs to adjust the network slice, so that the radio access network device adjusts the network slices supported by itself according to the adjustment instruction, thereby solving the problem of how the terminal device reports the recording result in different network slices supporting different service scenarios. Furthermore, the radio access network device can adjust the network slices supported by itself, improving the success rate of the terminal device accessing the network slice. Compared with Figure 2 In the embodiment shown, it is the radio access network device that determines whether to adjust and how to adjust the network slices supported by itself. In this embodiment, it is the network management device or the AMF that determines which radio access network devices need to adjust the network slice service and how to adjust it, with higher accuracy. Since the network management device or the AMF can obtain the recording results of the terminal devices of multiple radio access network devices respectively, centralized decision-making can be carried out, which is beneficial to the improvement of the overall network experience in a region.

[0257] For the data transmission method provided in this embodiment, under the separated architecture of the central unit (CU) and the distributed unit (DU) of the radio access network device, how the terminal device reports the recording result and how the radio access network device adjusts the network slices supported by itself will be described below in conjunction with Figure 6 and Figure 7 for illustration. Figure 6 The embodiment shown is the process of the radio access network device determining whether to adjust and how to adjust the network slices supported by itself under the CU-DU separated architecture. Figure 7The illustrated embodiment is a process in which a network management device or an AMF determines which radio access network devices need to adjust network slice services and how to adjust them in a CU-DU separation architecture, which will be described in detail below.

[0258] First, a brief description of the CU-DU separation architecture is given. CU and DU can be understood as a division of radio access network devices from a logical function perspective. CU and DU can be physically separated or deployed together. Multiple DUs can share a single CU. One DU can also be connected to multiple CUs. CU and DU can be connected through an interface, such as the F1 interface. CU and DU can be divided according to the protocol layers of the wireless network. For example, the functions of the RRC, service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) layers are set in the CU, while the functions of the radio link control (RLC), media access control (MAC) layer, physical (PHY) layer, etc. are set in the DU. It can be understood that this division of the processing functions of CU and DU according to the protocol layers is only an example, and it can also be divided in other ways. For example, CU or DU can be divided into functions with more protocol layers. For example, CU or DU can also be divided into partial processing functions of the protocol layers. In one design, some functions of the RLC layer and the protocol layers above the RLC layer are set in the CU, and the remaining functions of the RLC layer and the protocol layers below the RLC layer are set in the DU. In another design, the functions of CU or DU can also be divided according to service types or other system requirements. For example, in terms of latency division, the functions that need to meet the latency requirements are set in the DU, and the functions that do not need to meet the latency requirements are set in the CU. In another design, CU can also have one or more functions of the core network. One or more CUs can be centrally set or separated. For example, CU can be set on the network side for convenient centralized management. DU can have multiple radio frequency functions, or the radio frequency functions can be remotely set.

[0259] Figure 6 The interaction flowchart of an embodiment of the data transmission method provided by this application is as Figure 6 shown. The method of this embodiment may include:

[0260] S201. The terminal device generates a recording result.

[0261] Specifically, the detailed relevant description of the terminal device generating a recording result is related to Figure 2The description of S101 in the illustrated embodiment is the same as that of S101. For details, refer to the description of S101 and it will not be elaborated here.

[0262] S202. The terminal device transmits the recording result through the DU of the radio access network device to which the current serving cell belongs to the CU of the radio access network device to which the current serving cell belongs.

[0263] Optionally, if the terminal device learns through system message broadcast that the current serving cell does not support network slicing services, the terminal device can choose to only send the recording result of the part related to non-network slicing services.

[0264] S203. The CU of the radio access network device to which the current serving cell belongs stores the recording result sent by the terminal device and forwards the recording result to other radio access network devices.

[0265] S204. The radio access network device determines updated network slice configuration information according to the recording results of at least one terminal device received within a preset time period.

[0266] It should be noted that the radio access network device that executes S204 can be the radio access network device to which the serving cell belongs. The radio access network device to which the serving cell belongs can also receive the recording results of other terminal devices forwarded by other radio access network devices. The radio access network device that executes S204 can also be other radio access network devices that receive the recording results of at least one terminal device. Under the CU-DU separation structure of each radio access network device, there are the following two implementable methods in S204:

[0267] Method 1: Decision is made by the CU. Specifically, the CU of the radio access network device determines updated network slice configuration information according to the recording results of at least one terminal device received within a preset time period, and then sends the updated network slice configuration information or the updated network slice configuration information and the recording result to the DU through the F1 interface. The DU sends the updated network slice configuration information to the terminal device through SIB1.

[0268] In this Method 1, further, on the basis of the above method, it can also include:

[0269] S205. The CU determines updated network slice remapping information according to the recording result and the updated network slice configuration information, and the CU sends the updated network slice remapping information to the terminal device. It can be that the CU sends it to the terminal device through an RRC message.

[0270] In an implementable manner, further, the updated network slice configuration information may further include adjustment information for the access control information of the network slice service. Optionally, the adjustment information for the access control information of the network slice service may be a system message. The radio access network device updates the access control parameter set list (uac-barring infosetList) cell in SIB1. Specifically, there are four optional methods. For details, please refer to Figure 2 the description in the embodiments shown, which will not be elaborated here.

[0271] In an implementable manner, further, on the basis of the above method, it may further include:

[0272] S206. The CU sends adjustment information for the access category to the terminal device, and the adjustment information for the access category is used to increase the access category related to the network slice service; or,

[0273] The CU pre-stores the adjustment information for the access category.

[0274] In addition to the above adjustments that can be made to its own network slice service, the following adjustments can also be made. Further, the method of this embodiment may further include:

[0275] S207. The CU adjusts the transmission signal power of at least one network slice supported by itself according to the recording results of at least one terminal device received within a preset time period. The transmission signal power may be, for example, at least one of the power of the SSB, the power of the CSI-RS, and the RSRP of the SUL.

[0276] S208. The CU adjusts the RACH resources of at least one network slice supported by itself according to the recording results of at least one terminal device received within a preset time period. The adjustment information of the RACH resources may also be sent to the terminal device through an RRC message.

[0277] By the CU adjusting the RACH resources of at least one network slice supported by itself according to the recording results of at least one terminal device received within a preset time period, the access probability of the terminal device initiating the network slice service can be increased, the access speed of the terminal device initiating the network slice service can be improved, and the probability and number of random access failures of the terminal device initiating the network slice service can be reduced.

[0278] Method 2: Decision by the DU. Specifically, the CU sends the recording results to the DU through the F1 interface. The DU determines the updated network slice configuration information according to the recording results of at least one terminal device received within a preset time period, and the DU sends the updated network slice configuration information to the terminal device through SIB1.

[0279] S205’, the DU determines the updated network slice remapping information according to the recording result and the updated network slice configuration information. The DU sends the updated network slice remapping information to the CU through the F1 interface, and then the CU sends the updated network slice remapping information to the terminal device. The CU may send the updated network slice remapping information to the terminal device through an RRC message.

[0280] In an implementable manner, further, the updated network slice configuration information may further include adjustment information for the access control information of the network slice service. Optionally, the adjustment information for the access control information of the network slice service may be a system message. The radio access network device updates the access control parameter set list cell in SIB1. Specifically, there are four optional ways, which can be seen in detail Figure 2 the description in the embodiments shown, which will not be elaborated here.

[0281] In an implementable manner, further, on the basis of the above method, it may further include:

[0282] S206’, the DU sends the adjustment information for the access category to the CU through the F1 interface, and then the CU sends the adjustment information for the access category to the terminal device. The adjustment information for the access category is used to increase the access categories related to the network slice service; or,

[0283] The DU prestores the adjustment information for the access category.

[0284] In addition to the above adjustments that can be made to its own network slice service, the following adjustments can also be made. Further, the method of this embodiment may further include:

[0285] S207’, the DU adjusts the transmission signal power of at least one network slice supported by itself according to the recording results of at least one terminal device received within a preset time period. The transmission signal power may be, for example, at least one of the power of the SSB, the power of the CSI-RS, and the RSRP of the SUL.

[0286] S208, the DU adjusts the RACH resources of at least one network slice supported by itself according to the recording results of at least one terminal device received within a preset time period. The DU may send the adjustment information of the RACH resources to the CU through the F1 interface, and the CU sends the adjustment information of the RACH resources to the terminal device through an RRC message.

[0287] By adjusting the RACH resources of at least one network slice supported by itself according to the recording results of at least one terminal device received by the DU within a preset time period, the access probability of the terminal device initiating the network slice service can be increased, the access speed of the terminal device initiating the network slice service can be improved, and the probability and number of random access failures of the terminal device initiating the network slice service can be reduced.

[0288] Figure 7 The interaction flowchart of an embodiment of the data transmission method provided in this application is as Figure 7 shown. The method of this embodiment may include:

[0289] S301. The terminal device generates a recording result.

[0290] Specifically, the detailed relevant description of the terminal device generating the recording result is the same as the description of S101 in the Figure 2 shown embodiment. Refer to the description of S101, and details are not described herein again.

[0291] S302. The terminal device transparently transmits the recording result to the CU of the radio access network device to which the current serving cell belongs through the DU of the radio access network device to which the current serving cell belongs.

[0292] Optionally, if the terminal device learns through system message broadcast that the current serving cell does not support the network slice service, the terminal device may choose to only send the recording result of the non-network slice service related part.

[0293] S303. The CU of the radio access network device to which the current serving cell belongs stores the recording result sent by the terminal device and sends the recording result to the network management device or the AMF.

[0294] S304. The network management device or the AMF determines the radio access network device that needs to adjust the network slice and the corresponding network slice identifier list according to the recording results of at least one terminal device received within a preset time period.

[0295] S305. The network management device or the AMF sends an adjustment instruction to the CU of the radio access network device. The adjustment instruction includes the updated network slice identifier list corresponding to the radio access network device.

[0296] Optionally, the adjustment instruction may further include an adjustment to the signal of the radio access network device. The radio access network device here may be the radio access network device to which the serving cell belongs, or other radio access network devices.

[0297] S306. The CU of the radio access network device sends the updated network slice configuration information to the terminal device.

[0298] After the radio access network device receives the adjustment instruction, the CU of the radio access network device adjusts its own network slice service. In this embodiment, further, it may further include Figure 3 S107'-S110' in the embodiment shown in Figure 3 , except that they are all executed by the CU of the radio access network device. Others are similar. For details, refer to S107'-S110', which will not be elaborated here.

[0299] In the prior art, for the RACH report, the CU of the radio access network device needs to actively send a RACH report request to the terminal device after the terminal device's random access is successful. After receiving the request, the terminal device sends a RACH report to the radio access network device. However, in the CU-DU separation architecture, if there is no RRC message interaction between the radio access network device and the terminal device during the random access process, the CU of the radio access network device is unaware of the entire random access process. Therefore, it is unable to send a RACH report request to the terminal device in a timely manner after the random access is successful to obtain the RACH report. To solve this problem, the present application also provides a data transmission method. When the terminal device determines that the number of RACH reports stored by the terminal device is greater than or equal to a preset number and / or the time for which the terminal device has stored the RACH report is greater than or equal to a preset duration, the terminal device sends a RACH report to the radio access network device to which the serving cell belongs. Thus, there is no need for the radio access network device to send a RACH report request, and the terminal device actively reports the RACH report. The following is a detailed description in conjunction with Figure 8 Detailed description.

[0300] Figure 8 It is an interaction flowchart of an embodiment of the data transmission method provided by the present application. As shown in Figure 8 shown, the method of this embodiment may include:

[0301] S401. The terminal device generates a RACH report.

[0302] Specifically, for the process of the terminal device generating a RACH report, refer to the description of S1011-S1014 in the embodiment shown in Figure 2 shown. Details will not be elaborated here. The terminal device stores the RACH report after the candidate access cell supports the network slice service initiated by the terminal device and the terminal device determines that the random access in the candidate access cell is successful. The RACH report includes the identifier of the accessed cell and the network slice identifier corresponding to the network slice service initiated by the terminal device.

[0303] S402. The terminal device determines that the number of RACH reports stored by the terminal device is greater than or equal to a preset number and / or the time for which the terminal device has stored the RACH report is greater than or equal to a preset duration.

[0304] Among them, the preset quantity is, for example, 8, and the preset duration is, for example, 48 hours. The quantity of stored RACH reports can be obtained through a counter set by the terminal device, and the time of stored RACH reports can be obtained through a timer set by the terminal device.

[0305] As an implementable manner, the terminal device may trigger the timer when determining that the first trigger condition is satisfied, and record the time of the RACH reports stored by the terminal device through the timer. Optionally, the first trigger condition includes the first successful random access after the terminal device powers on and / or the terminal device deletes the RACH reports carried by the terminal device.

[0306] As an implementable manner, the terminal device may trigger the counter when determining that the second trigger condition is satisfied, and record the quantity of the random access reports stored by the terminal device through the counter. The second trigger condition may be: the terminal device stores the random access reports related to the preset network slice service.

[0307] Optionally, the timer and counter set by the terminal device may be set for the RACH reports related to a certain type or certain types of network slice services. For example, the terminal device stores the RACH reports related to network slice service 1 to trigger the counter, or the terminal device deletes or clears the RACH reports related to network slice service 1 to trigger the timer. The RACH reports related to network slice service 1 may be the RACH reports generated by the terminal device initiating random access to upload the data of network slice service 1, etc. The timer and counter set by the terminal device may also be set for all RACH reports, and this embodiment does not limit this.

[0308] S403. The terminal device sends the RACH report to the radio access network device to which the serving cell belongs.

[0309] Optionally, if the terminal device learns through system message broadcast that the serving cell does not support network slice services, the terminal device may choose to report only the RACH reports related to the non-network slice service part. If the terminal device learns through system message broadcast that the current cell supports network slice services, then the content of the reported record result may include network slice service information or may also exclude the part related to network slice service information.

[0310] Specifically, in an implementable manner, S403 may specifically be: after the terminal device successfully performs random access in the serving cell, the radio access network device may send a RACH report request to the terminal device, and the terminal device sends the RACH report to the radio access network device according to the RACH report request.

[0311] In another implementable manner, the terminal device may send a RACH report to the radio access network device to which the serving cell belongs when it is in the inactive state. Specifically, S403 may be: the terminal device sends small data to the radio access network device, and the RACH report is carried in the small data, that is, the terminal device sends the RACH report to the radio access network device in the small data.

[0312] Optionally, after S403 in the method of this embodiment, it may further include:

[0313] S404. The terminal device deletes the stored RACH reports in ascending order of importance.

[0314] The importance determination condition may be: the RACH report of the cell that supports the network slice service initiated by the terminal device has a higher importance than the RACH report of the cell that does not support the network slice service initiated by the terminal device; or, the RACH report of the cell with good signal quality (or high signal strength) has a higher importance than the RACH report of the cell with bad signal quality (or low signal strength). The terminal device may delete one report, or multiple reports, or clear the entire memory storing the RACH reports. By deleting the stored RACH reports in ascending order of importance, the storage time of the RACH reports with high importance can be extended, and the utilization value of the RACH reports can be fully utilized.

[0315] In the data transmission method provided in this embodiment, after the terminal device generates a RACH report, when it is determined that the number of stored RACH reports of the terminal device is greater than or equal to a preset number and / or the time for which the terminal device has stored the RACH reports is greater than or equal to a preset duration, the terminal device sends the RACH report to the radio access network device to which the serving cell belongs. Thus, there is no need for the radio access network device to send a RACH report request, and the terminal device actively reports the RACH report.

[0316] In the prior art, in the CU-DU separation architecture, if there is no RRC message interaction between the radio access network device and the terminal device during the random access process, the CU of the radio access network device is unaware of the entire random access process, and the CU of the radio access network device does not know whether the terminal device has successfully performed random access. To solve this problem, the present application also provides a data transmission method. After the terminal device successfully performs random access in the serving cell, the terminal device sends indication information for indicating that the terminal device has successfully performed random access in the serving cell to the radio access network device. Thus, the radio access network device can learn that the terminal device has successfully performed random access in the serving cell through the indication information. The following is a detailed description in conjunction with Figure 9 Detailed description.

[0317] Figure 9An interaction flowchart of an embodiment of a data transmission method provided by this application is as follows Figure 9 As shown, the method of this embodiment may include:

[0318] S501. The terminal device generates a RACH report.

[0319] S502. The terminal device sends indication information for indicating the successful random access of the terminal device in the serving cell to the radio access network device to which the serving cell belongs.

[0320] Specifically, there may be multiple pieces of such indication information. That is, every time the terminal device succeeds in random access, it sends the indication information to the radio access network device once, so that the radio access network device can know the number of times the terminal device has succeeded in random access and in which cells the access has succeeded.

[0321] Optionally, the indication information may be carried in an RRC message.

[0322] As an implementable manner, the terminal device may send the indication information after each successful random access.

[0323] As another implementable manner, the terminal device may send the indication information after some successful random access events. For example: The terminal device may select random access events related to a preset network slice service and send the indication information. Or, if in the 4-step or 2-step random access initiated by the terminal device, no RRC message is carried in message 3 or message B, the terminal device sends the indication information. Or, if in the 4-step or 2-step random access initiated by the terminal device, an RRC message is carried in message 3 or message B, the terminal device determines whether to send the indication information.

[0324] Optionally, the indication information may further include: a network slice identifier of a certain type of network slice service or information indicating the network slice service. That is, it indicates that the radio access network device has succeeded in random access for a certain type of network slice service or indicates that the radio access network device has succeeded in random access for the network slice service.

[0325] Further, the method of this embodiment may further include:

[0326] S503. The radio access network device sends a RACH report request to the terminal device.

[0327] Optionally, the RACH report request may include at least one network slice identifier, that is, the radio access network device requests the RACH report corresponding to at least one network slice identifier, and the radio access network device requests the RACH report related to a certain type of network slice service.

[0328] Optionally, the RACH report request may include an indication for requesting a RACH report related to a network slice service, that is, the radio access network device requests a RACH report related to the network slice service.

[0329] Optionally, the RACH report request may also carry no information, that is, the radio access network device requests all RACH reports without distinguishing whether they are related to the network slice service.

[0330] S504. The terminal device sends a RACH report to the radio access network device according to the RACH report request.

[0331] Specifically, the terminal device sends a RACH report to the radio access network device according to the content of the RACH report request. If the RACH report request includes at least one network slice identifier, the terminal device sends a RACH report corresponding to at least one network slice identifier to the radio access network device; if the RACH report request includes an indication for requesting a RACH report related to the network slice service, the terminal device sends a RACH report related to the network slice service to the radio access network device; if the RACH report request carries no information, the terminal device sends all stored RACH reports to the radio access network device.

[0332] In the data transmission method provided in this embodiment, after the terminal device generates a RACH report, it sends indication information for indicating successful random access of the terminal device in the serving cell to the radio access network device belonging to the serving cell. Thus, the radio access network device can learn about the successful random access of the terminal device in the serving cell through the indication information, and further send a RACH report request to the terminal device to obtain the RACH report.

[0333] Figure 10 As shown in the schematic structural diagram of an embodiment of a terminal device provided in this application, Figure 10 The terminal device in this embodiment may include: a generation module 11 and a sending module 12, where

[0334] The generating module 11 is used to generate record results, where the record results include at least one of a recorded minimized drive test report, a radio link failure (RLF) report, and a random access channel (RACH) report. Among them, the recorded minimized drive test report includes the identifier of a candidate access cell, information indicating whether the candidate access cell supports the network slice service initiated by the terminal device, the location information of the terminal device when receiving the system message of the candidate access cell, and the network slice identifier corresponding to the network slice service initiated by the terminal device. The candidate access cell is the top N cells among the cells measured by the terminal device sorted in descending order according to signal strength or signal quality, where N is a preset positive integer. The RLF report includes the identifier of the cell where the terminal device experiences a radio link failure after access and the network slice identifier corresponding to the network slice service when the terminal device experiences a radio link failure. The RACH report includes the identifier of the cell accessed by the terminal device and the network slice identifier corresponding to the network slice service initiated by the terminal device;

[0335] The sending module 12 is used to send the record results to the radio access network device to which the serving cell belongs.

[0336] The terminal device in this embodiment can be used to execute Figure 2 or Figure 4 or Figure 8 the technical solutions of the method embodiments shown. The implementation principles and technical effects are similar and will not be elaborated here.

[0337] Figure 11 The following is a schematic structural diagram of an embodiment of a terminal device provided by the present application. As Figure 11 shown, on the basis of what is shown in Figure 10 the terminal device in this embodiment may further include: a receiving module 13, which is used to receive updated network slice configuration information sent by the radio access network device. The updated network slice configuration information is determined by the radio access network device, the network management device, or the access and mobility management function network element (AMF) according to the record results of at least one terminal device within a preset time period;

[0338] The updated network slice configuration information includes a network slice identifier list, which contains the network slice identifiers corresponding to at least one network slice supported by the radio access network device. The network slice identifier list includes the network slice identifier corresponding to the network slice service initiated by the terminal device in the cell controlled by the radio access network device.

[0339] Further, the generating module 11 is used to:

[0340] Perform the following operations according to the reference signal information of the measured candidate access cell:

[0341] Obtain the network slice identifier list of the first candidate access cell;

[0342] Determine whether the first candidate access cell supports the network slice service initiated by the terminal device according to the network slice identifier list of the first candidate access cell;

[0343] If it is determined to be yes,

[0344] Determine to store the RACH report corresponding to the first candidate access cell after successfully randomly accessing the first candidate access cell; or,

[0345] Determine to store the RLF report corresponding to the first candidate access cell after successfully randomly accessing the first candidate access cell and a radio link failure occurs during subsequent communication; or,

[0346] Determine that the first candidate access cell cannot be successfully randomly accessed, obtain the network slice identifier list of the second candidate access cell, and store the recorded minimized drive test report corresponding to the first candidate access cell;

[0347] If it is determined to be no, store the recorded minimized drive test report corresponding to the first candidate access cell, or obtain the network slice identifier list of the second candidate access cell, and store the recorded minimized drive test report corresponding to the first candidate access cell.

[0348] The terminal device in this embodiment can be used to execute Figure 2 or Figure 4 or Figure 8 The technical solutions of the method embodiments shown, the implementation principles and technical effects are similar, and will not be elaborated here.

[0349] Figure 12 The following is a schematic structural diagram of an embodiment of a terminal device provided by the present application. As Figure 12 shown, on the basis shown in Figure 11 the terminal device in this embodiment may further include: a first deletion module 14, and the first deletion module 14 is used to delete the stored RACH reports in ascending order of importance when it is determined that the stored RACH reports meet the preset conditions.

[0350] Optionally, when the generation module 11 determines that the first candidate access cell cannot be successfully randomly accessed, it includes:

[0351] Determine that the number of random access attempts to the first candidate access cell is greater than a first threshold; or,

[0352] It is determined that the first candidate access cell is successfully randomly accessed, and the number of times of initiating a random access attempt again after a radio link failure occurs during subsequent communication processes is greater than a first threshold.

[0353] Optionally, recording the minimized drive test report further includes at least one of network slice remapping information of the candidate access cell and network slice redirection of the candidate access cell.

[0354] Optionally, recording the minimized drive test report further includes information for indicating the signal strength and signal quality of the candidate access cell.

[0355] Optionally, the receiving module 13 is further configured to:

[0356] Receive adjustment information of the access category sent by the radio access network device, where the adjustment information of the access category is used to increase the access category related to the network slice service.

[0357] The terminal device in this embodiment can be used to execute Figure 2 or Figure 4 or Figure 8 The technical solutions of the method embodiments shown, and their implementation principles and technical effects are similar, and will not be elaborated here.

[0358] Figure 13 The following is a schematic structural diagram of an embodiment of a terminal device provided by the present application. As Figure 13 shown, on the basis of what is shown in Figure 11 or Figure 12 shown, further, it may further include: a storage module 15, and the storage module 15 is used to pre-store the adjustment information of the access category.

[0359] The terminal device in this embodiment can be used to execute Figure 2 or Figure 4 or Figure 8 The technical solutions of the method embodiments shown, and their implementation principles and technical effects are similar, and will not be elaborated here.

[0360] Figure 14 The following is a schematic structural diagram of an embodiment of a terminal device provided by the present application. As Figure 14 shown, on the basis of what is shown in Figure 10 shown, further, it may further include: a determination module 16, and the determination module 16 is used to determine that the number of RACH reports stored by the terminal device is greater than or equal to a preset number and / or the time for which the terminal device has stored RACH reports is greater than or equal to a preset duration before the sending module 12 sends the recording result to the radio access network device to which the serving cell belongs.

[0361] Figure 15A schematic structural diagram of an embodiment of a terminal device provided by the present application is shown as follows Figure 15 As shown, on the basis of what is shown in Figure 14 the terminal device of this embodiment may further include: a second deletion module 17, which is configured to delete the stored RACH reports in ascending order of importance after the sending module 12 sends the recording result to the radio access network device to which the serving cell belongs.

[0362] Figure 14 and Figure 15 the terminal device of the embodiment shown in Figure 2 or Figure 4 or Figure 8 can be used to execute the technical solutions of the method embodiments shown in

[0363] Figure 16 A schematic structural diagram of an embodiment of a radio access network device provided by the present application is shown as follows Figure 16 As shown, the radio access network device of this embodiment may include: a processing module 21 and a receiving module 22, wherein

[0364] the processing module 21 is configured to establish a connection with the terminal device;

[0365] the receiving module 22 is configured to receive the recording result sent by the terminal device, and the recording result includes at least one of a minimized drive test (MDT) report, a radio link failure (RLF) report, and a random access channel (RACH) report. The MDT report includes the identifier of the candidate access cell, the information indicating whether the candidate access cell supports the network slice service initiated by the terminal device, the location information of the terminal device when receiving the system message of the candidate access cell, and the network slice identifier corresponding to the network slice service initiated by the terminal device. The candidate access cell is the top N cells sorted in descending order of signal strength or signal quality among the cells measured by the terminal device, where N is a preset positive integer. The RLF report includes the identifier of the cell where the terminal device has a radio link failure after access and the network slice identifier corresponding to the network slice service when the terminal device has a radio link failure. The RACH report includes the identifier of the cell accessed by the terminal device and the network slice identifier corresponding to the network slice service initiated by the terminal device.

[0366] The radio access network device of this embodiment can be used to execute Figure 2 or Figure 4 the technical solutions of the method embodiments shown, and their implementation principles and technical effects are similar, so they will not be elaborated here.

[0367] Figure 17 A structural schematic diagram of an embodiment of a wireless access network device provided by this application is as follows Figure 17 As shown, on the basis of what is shown in Figure 16 This embodiment of the wireless access network device may further include: a sending module 23, which is used to send updated network slice configuration information to the terminal device, and the updated network slice configuration information is determined by the wireless access network device, the network management device, or the access and mobility management function network element AMF according to the recording results of at least one terminal device within a preset time period;

[0368] The updated network slice configuration information includes a network slice identifier list, and the network slice identifier list contains network slice identifiers corresponding to at least one network slice supported by the wireless access network device, and the network slice identifiers corresponding to the network slice services initiated by the terminal device in the cell controlled by the wireless access network device are included in the network slice identifier list.

[0369] Furthermore, the processing module 21 is also used to store the recording results;

[0370] The sending module 23 is also used to send the recording results to other wireless access network devices.

[0371] Furthermore, the processing module 21 is also used to determine a network slice identifier list according to the recorded minimum drive test report, RLF report, and RACH report in the recording results of at least one terminal device received within a preset time period.

[0372] Furthermore, the processing module 21 is also used to store the recording results;

[0373] The sending module 23 is also used to send the recording results to the network management device or the access and mobility management function network element AMF, so that the network management device or AMF determines the wireless access network devices that need to adjust the network slice and the corresponding network slice identifier list according to the recorded minimum drive test report, RLF report, and RACH report in the recording results of at least one terminal device received within a preset time period.

[0374] Furthermore, the receiving module 22 is also used to:

[0375] Before the sending module 23 sends the updated network slice configuration information to the terminal device, receive an adjustment instruction sent by the network management device or AMF, and the adjustment instruction includes an updated network slice identifier list corresponding to the wireless access network device.

[0376] Furthermore, the processing module 21 is also used to:

[0377] Determine the updated network slice remapping information according to the recorded result and the updated network slice configuration information;

[0378] The sending module 23 is further configured to send the updated network slice remapping information to the terminal device.

[0379] Furthermore, the updated network slice configuration information further includes adjustment information for the access control information of the network slice service.

[0380] Optionally, the adjustment information for the access control information of the network slice service is a system message.

[0381] In the system message, the access control identification ID related to the network slice service is removed from the unified access control blocking access identity information; or,

[0382] In the system message, an access control ID unrelated to the network slice service is added to the unified access control blocking access identity information; or,

[0383] The cell value of the unified access control blocking factor corresponding to the network slice service in the system message is reduced within a preset range; or,

[0384] The cell value of the unified access control time corresponding to the network slice service in the system message is increased within a preset range.

[0385] Furthermore, the sending module 23 is further configured to:

[0386] Send adjustment information for the access category to the terminal device, and the adjustment information for the access category is used to increase the access category related to the network slice service; or,

[0387] The processing module is further configured to pre-store the adjustment information for the access category.

[0388] Furthermore, the processing module 21 is further configured to:

[0389] Adjust the transmission signal power of at least one network slice supported by itself according to the recorded results of multiple terminal devices received within a preset time period; and / or

[0390] Adjust the RACH resources of at least one network slice supported by itself according to the recorded results of multiple terminal devices received within a preset time period.

[0391] The radio access network device of this embodiment can be used to execute Figure 2 or Figure 4 The technical solutions of the method embodiments shown, the implementation principles and technical effects are similar, and will not be elaborated here.

[0392] Figure 18 This is a schematic structural diagram of an embodiment of a terminal device provided by the present application, asFigure 18 As shown in the figure, the terminal device of this embodiment may include: a generation module 31 and a transmission module 32, where,

[0393] The generation module 31 is used to generate a RACH report.

[0394] The transmission module 32 is used to send indication information indicating that the terminal device has successfully randomly accessed the serving cell to the radio access network device to which the serving cell belongs.

[0395] Optionally, the transmission module 32 is further used to send a RACH report to the radio access network device according to a RACH report request.

[0396] The terminal device of this embodiment can be used to execute Figure 9 The technical solutions of the method embodiment shown, and its implementation principle and technical effects are similar, which will not be elaborated here.

[0397] Figure 19 This is a schematic structural diagram of a terminal device provided by the present application. As Figure 19 shown, the terminal device 300 includes: a memory 301 and a processor 302;

[0398] The memory 301 is used to store a computer program;

[0399] The processor 302 is used to execute the computer program stored in the memory to implement the data transmission method in the above embodiment. For details, please refer to the relevant descriptions in the foregoing method embodiment.

[0400] Optionally, the memory 301 can be either independent or integrated with the processor 302.

[0401] When the memory 301 is a device independent of the processor 302, the terminal device 300 may further include:

[0402] A bus 303, used to connect the memory 301 and the processor 302.

[0403] Optionally, this embodiment further includes: a communication interface 304, and this communication interface 304 can be connected to the processor 302 through the bus 303. The processor 302 can control the communication interface 303 to implement the above receiving and sending functions of the terminal device 300.

[0404] This device can be used to execute each step and / or process corresponding to the terminal device in the above method embodiment.

[0405] Figure 20 This is a schematic structural diagram of a radio access network device provided by the present application. As Figure 20As shown, the wireless access network device 400 includes: a memory 401 and a processor 402;

[0406] The memory 401 is used to store computer programs;

[0407] The processor 402 is used to execute the computer programs stored in the memory to implement the data transmission method in the above embodiments. For specific details, reference can be made to the relevant descriptions in the foregoing method embodiments.

[0408] Optionally, the memory 401 can be either independent or integrated with the processor 402.

[0409] When the memory 401 is a device independent of the processor 402, the wireless access network device 400 may further include:

[0410] A bus 403 for connecting the memory 401 and the processor 402.

[0411] Optionally, this embodiment further includes: a communication interface 404, which can be connected to the processor 402 through the bus 403. The processor 402 can control the communication interface 403 to implement the above receiving and sending functions of the wireless access network device 400.

[0412] This device can be used to execute each step and / or process corresponding to the wireless access network device in the above method embodiments.

[0413] This application also provides a readable storage medium, in which execution instructions are stored. When at least one processor of the terminal device executes the execution instructions, the terminal device executes the data transmission method provided by the above various embodiments.

[0414] This application also provides a readable storage medium, in which execution instructions are stored. When at least one processor of the wireless access network device executes the execution instructions, the wireless access network device executes the data transmission method provided by the above various embodiments.

[0415] This application also provides a program product, which includes execution instructions stored in the readable storage medium. At least one processor of the terminal device can read the execution instructions from the readable storage medium, and the execution of the execution instructions by at least one processor enables the terminal device to implement the data transmission method provided by the above various embodiments.

[0416] The present application also provides a program product, which includes execution instructions stored in a readable storage medium. At least one processor of the radio access network device can read the execution instructions from the readable storage medium, and the execution of the execution instructions by the at least one processor enables the radio access network device to implement the data transmission methods provided by the above various embodiments.

[0417] Those of ordinary skill in the art can understand that: in the above embodiments, all or part of them can be implemented by software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions according to the embodiments of the present invention are generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wirelessly (such as infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer, or a data storage device such as a server or data center that includes one or more integrated available media. The available medium can be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)).

Claims

1. A data transmission method, characterized in that, applied to a terminal device, including: generating a recording result, the recording result including at least one of a recorded minimized drive test report or a radio link failure (RLF) report, wherein the recorded minimized drive test report includes an identifier of a candidate access cell, information for indicating whether the candidate access cell supports a network slice service initiated by the terminal device, location information of the terminal device when receiving a system message of the candidate access cell, and a network slice identifier corresponding to the network slice service initiated by the terminal device, the candidate access cell being the top N cells sorted in descending order of signal strength or signal quality among the cells measured by the terminal device, the N being a preset positive integer, and the RLF report includes an identifier of a cell where a radio link failure occurs after the terminal device accesses and a network slice identifier corresponding to the network slice service when the terminal device has a radio link failure; sending the recording result to a radio access network device to which the serving cell belongs.

2. The method according to claim 1, characterized in that, the method further includes: receiving updated network slice configuration information sent by the radio access network device, the updated network slice configuration information being determined by the radio access network device, a network management device, or an access and mobility management function network element (AMF) according to the recording results of at least one terminal device within a preset time period; the updated network slice configuration information includes a network slice identifier list, the network slice identifier list containing network slice identifiers corresponding to at least one network slice supported by the radio access network device, and the network slice identifier list includes a network slice identifier corresponding to the network slice service initiated by the terminal device in a cell controlled by the radio access network device.

3. The method according to claim 1, characterized in that, the generating of the recording result includes: performing the following operations according to the reference signal information of the measured candidate access cells: obtaining a network slice identifier list of the first candidate access cell; determining whether the first candidate access cell supports the network slice service initiated by the terminal device according to the network slice identifier list of the first candidate access cell; if it is determined to be yes, determining to store an RLF report corresponding to the first candidate access cell after successfully randomly accessing the first candidate access cell and having a radio link failure during subsequent communication; or, determining that the first candidate access cell cannot be successfully randomly accessed, obtaining a network slice identifier list of the second candidate access cell, and storing a recorded minimized drive test report corresponding to the first candidate access cell; if it is determined to be no, storing a recorded minimized drive test report corresponding to the first candidate access cell, or the terminal device obtaining a network slice identifier list of the second candidate access cell and storing a recorded minimized drive test report corresponding to the first candidate access cell.

4. The method according to claim 3, characterized in that, Said determination of failing to successfully perform random access to the first candidate access cell includes: Determining that the number of times of initiating a random access attempt in the first candidate access cell is greater than a first threshold; or, Determining that the number of times of initiating a random access attempt again after successfully performing random access to the first candidate access cell and experiencing a radio link failure during subsequent communication is greater than the first threshold.

5. The method according to claim 1, wherein, The recorded minimized drive test report further includes at least one of network slice remapping information of the candidate access cell and network slice redirection of the candidate access cell.

6. The method according to any one of claims 2-5, wherein, The method further includes: Receiving adjustment information of access categories sent by the radio access network device, the adjustment information of access categories being used to increase access categories related to network slice services; or, Pre-storing the adjustment information of access categories.

7. A data transmission method, wherein, Applied to a radio access network device, it includes: Establishing a connection with a terminal device; Receiving a recording result sent by the terminal device, the recording result including at least one of a recorded minimized drive test record and a radio link failure (RLF) report, wherein the recorded minimized drive test report includes an identifier of a candidate access cell, information for indicating whether the candidate access cell supports a network slice service initiated by the terminal device, location information of the terminal device when receiving a system message of the candidate access cell, and a network slice identifier corresponding to the network slice service initiated by the terminal device, the candidate access cell being the top N cells sorted in descending order of signal strength or signal quality among the cells measured by the terminal device, N being a preset positive integer, and the RLF report includes an identifier of the cell where a radio link failure occurs after the terminal device accesses and a network slice identifier corresponding to the network slice service when the terminal device experiences a radio link failure.

8. The method according to claim 7, wherein, The method further includes: Sending updated network slice configuration information to the terminal device, the updated network slice configuration information being determined by the radio access network device, a network management device, or an access and mobility management function network element (AMF) according to the recording results of at least one terminal device within a preset time period; The updated network slice configuration information includes a network slice identifier list, the network slice identifier list containing network slice identifiers corresponding to at least one network slice supported by the radio access network device, and the network slice identifier list includes a network slice identifier corresponding to the network slice service initiated by the terminal device in the cell controlled by the radio access network device.

9. The method according to claim 8, wherein, The method further includes: Storing the recording result and sending the recording result to other radio access network devices.

10. The method according to claim 8, wherein, The method further includes: Store the recorded result and send the recorded result to a network management device or an Access and Mobility Management Function (AMF) network element, so that the network management device or the AMF determines, based on the recorded results of multiple terminal devices received within the preset time period, a radio access network device that needs to adjust a network slice and a corresponding list of network slice identifiers.

11. The method according to claim 10, wherein, before sending updated network slice configuration information to the terminal device, further comprising: receiving an adjustment instruction sent by the network management device or the AMF, the adjustment instruction including the updated list of network slice identifiers corresponding to the radio access network device.

12. The method according to claim 8, wherein, the method further comprises: determining updated network slice remapping information according to the recorded result and the updated network slice configuration information; sending the updated network slice remapping information to the terminal device.

13. The method according to claim 8, wherein, the updated network slice configuration information further includes adjustment information for access control information of a network slice service.

14. The method according to claim 13, wherein, the adjustment information for access control information of the network slice service is a system message, removing an access control identifier ID related to the network slice service from the unified access control blocking access identity information in the system message; or, adding an access control ID unrelated to the network slice service to the unified access control blocking access identity information in the system message; or, decreasing a value of a unified access control blocking factor cell corresponding to the network slice service in the system message within a preset range; or, increasing a value of a unified access control time cell corresponding to the network slice service in the system message within a preset range.

15. The method according to claim 8, wherein, the method further comprises: sending adjustment information for an access category to the terminal device, the adjustment information for the access category being used to increase an access category related to the network slice service; or, pre-storing the adjustment information for the access category.

16. The method according to any one of claims 8 - 15, wherein, the method further comprises: modifying a current configuration, the configuration including any one of data radio bearers supported by the radio access network device, spectrum bandwidth configuration, carrier configuration, and modulation and demodulation mode configuration.

17. A terminal device, wherein, comprising: A generating module, configured to generate a recording result, where the recording result includes at least one of a recorded minimized drive test report or a radio link failure (RLF) report. The recorded minimized drive test report includes an identifier of a candidate access cell, information indicating whether the candidate access cell supports a network slice service initiated by the terminal device, location information of the terminal device when receiving a system message of the candidate access cell, and a network slice identifier corresponding to the network slice service initiated by the terminal device. The candidate access cell is the top N cells sorted in descending order of signal strength or signal quality among the cells measured by the terminal device, where N is a preset positive integer. The RLF report includes an identifier of the cell where the terminal device experiences a radio link failure after access and a network slice identifier corresponding to the network slice service when the terminal device experiences the radio link failure. A sending module, configured to send the recording result to a radio access network device to which a serving cell belongs.

18. The terminal device according to claim 17, wherein, the terminal device further includes: a receiving module, configured to receive updated network slice configuration information sent by the radio access network device, where the updated network slice configuration information is determined by the radio access network device, a network management device, or an access and mobility management function (AMF) based on the recording results of at least one terminal device within a preset time period; the updated network slice configuration information includes a network slice identifier list, where the network slice identifier list contains network slice identifiers corresponding to at least one network slice supported by the radio access network device, and the network slice identifier list includes the network slice identifier corresponding to the network slice service initiated by the terminal device in a cell controlled by the radio access network device.

19. The terminal device according to claim 18, wherein, the generating module is configured to: perform the following operations according to the reference signal information of the measured candidate access cells: obtain a network slice identifier list of the first candidate access cell; determine whether the first candidate access cell supports the network slice service initiated by the terminal device according to the network slice identifier list of the first candidate access cell; if it is determined that the first candidate access cell supports the network slice service, determine to store an RLF report corresponding to the first candidate access cell after successfully randomly accessing the first candidate access cell and experiencing a radio link failure during subsequent communication; or, determine that the first candidate access cell cannot be successfully randomly accessed, obtain a network slice identifier list of the second candidate access cell, and store a recorded minimized drive test report corresponding to the first candidate access cell; if it is determined that the first candidate access cell does not support the network slice service, store a recorded minimized drive test report corresponding to the first candidate access cell, or obtain a network slice identifier list of the second candidate access cell and store a recorded minimized drive test report corresponding to the first candidate access cell.

20. The terminal device according to claim 19, wherein, The generating module determines that the random access to the first candidate access cell fails, including: Determining that the number of random access attempts in the first candidate access cell is greater than a first threshold; or, Determining that the random access to the first candidate access cell is successful and the number of times of initiating a random access attempt again after a radio link failure occurs during subsequent communication is greater than the first threshold.

21. The terminal device according to claim 17, wherein, The recorded minimized drive test report further includes at least one of network slice remapping information of the candidate access cell and network slice redirection of the candidate access cell.

22. The terminal device according to any one of claims 18-21, wherein, The receiving module is further configured to: Receive adjustment information of the access category sent by the radio access network device, where the adjustment information of the access category is used to increase the access category related to the network slice service; or, The terminal device further includes a storage module, and the storage module is configured to pre-store the adjustment information of the access category.

23. A radio access network device, wherein, It includes: A processing module, configured to establish a connection with a terminal device; A receiving module, configured to receive a recording result sent by the terminal device, where the recording result includes at least one of a recorded minimized drive test record minimized drive test report or a radio link failure (RLF) report. The recorded minimized drive test report includes an identifier of a candidate access cell, information indicating whether the candidate access cell supports a network slice service initiated by the terminal device, location information of the terminal device when receiving a system message of the candidate access cell, and a network slice identifier corresponding to the network slice service initiated by the terminal device. The candidate access cell is the top N cells sorted in descending order of signal strength or signal quality among the cells measured by the terminal device, and N is a preset positive integer. The RLF report includes an identifier of the cell where the radio link failure occurs after the terminal device accesses and the network slice identifier corresponding to the network slice service when the terminal device has a radio link failure.

24. The radio access network device according to claim 23, wherein, The radio access network device further includes: A sending module, configured to send updated network slice configuration information to the terminal device, where the updated network slice configuration information is determined by the radio access network device, a network management device, or an access and mobility management function network element (AMF) according to the recording results of at least one terminal device within a preset time period; The updated network slice configuration information includes a network slice identifier list, and the network slice identifier list contains network slice identifiers corresponding to at least one network slice supported by the radio access network device. The network slice identifier list includes the network slice identifier corresponding to the network slice service initiated by the terminal device in the cell controlled by the radio access network device.

25. The radio access network device according to claim 24, wherein, The processing module is further configured to store the recording result; The sending module is further configured to send the recording result to other radio access network devices.

26. The radio access network device according to claim 25, wherein, the processing module is further configured to determine the network slice identifier list according to the recorded minimized drive test report, RLF report, and RACH report in the recording results of multiple terminal devices received within the preset time period.

27. The radio access network device according to claim 26, wherein, the processing module is further configured to store the recording result; the sending module is further configured to send the recording result to a network management device or an access and mobility management function network element AMF, so that the network management device or the AMF determines the radio access network devices that need to adjust network slices and the corresponding network slice identifier lists according to the recording results of multiple terminal devices received within the preset time period.

28. The radio access network device according to claim 27, wherein, the receiving module is further configured to: before the sending module sends updated network slice configuration information to the terminal device, receive an adjustment instruction sent by the network management device or AMF, where the adjustment instruction includes the updated network slice identifier list corresponding to the radio access network device.

29. The radio access network device according to claim 24, wherein, the processing module is further configured to: determine updated network slice remapping information according to the recording result and the updated network slice configuration information; the sending module is further configured to send the updated network slice remapping information to the terminal device.

30. The radio access network device according to claim 24, wherein, the updated network slice configuration information further includes adjustment information for the access control information of the network slice service.

31. The radio access network device according to claim 30, wherein, the adjustment information for the access control information of the network slice service is a system message, the access control identifier ID related to the network slice service is removed from the unified access control blocking access identity information in the system message; or, an access control ID unrelated to the network slice service is added to the unified access control blocking access identity information in the system message; or, the cell value of the unified access control blocking factor corresponding to the network slice service in the system message is reduced within a preset range; or, the cell value of the unified access control time corresponding to the network slice service in the system message is increased within a preset range.

32. The radio access network device according to claim 24, wherein, the sending module is further configured to: send adjustment information for the access category to the terminal device, where the adjustment information for the access category is used to increase the access category related to the network slice service; or, the processing module is further configured to pre-store the adjustment information for the access category.

33. The radio access network device according to any one of claims 24-32, wherein, the processing module is further configured to: Modify the current configuration, where the configuration includes any one of the data radio bearers supported by the radio access network device, the spectrum bandwidth configuration, the carrier configuration, and the modulation and demodulation mode configuration.

34. A terminal device, characterized in that it includes: a memory for storing program instructions; a processor for executing the data transmission method according to any one of claims 1-6 when calling and executing the program instructions in the memory.

35. A radio access network device, characterized in that it includes: a memory for storing program instructions; a processor for executing the data transmission method according to any one of claims 7-16 when calling and executing the program instructions in the memory.

36. A computer-readable storage medium, characterized in that execution instructions are stored in the readable storage medium, and when at least one processor of the terminal device executes the execution instructions, the terminal device executes the data transmission method according to any one of claims 1-6.

37. A computer-readable storage medium, characterized in that execution instructions are stored in the readable storage medium, and when at least one processor of the radio access network device executes the execution instructions, the radio access network device executes the data transmission method according to any one of claims 7-16.

38. A computer program product, the computer program product includes execution instructions, and when the execution instructions run on a computer, the computer executes the method according to any one of claims 1-6 or any one of claims 7-16.

Images