Data transmission method, data transmission device, storage medium and electronic device

Abstract

The present disclosure provides a data transmission method, a data transmission device, a storage medium and an electronic device, and relates to the field of wireless communication technology. The data processing method comprises: receiving a target service request sent by a user terminal; querying a target carrier channel corresponding to the target service request from a pre-configured carrier channel list; and sending service data corresponding to the target service request to the user terminal based on the target carrier channel. The present disclosure can reduce the complexity of the user terminal.

Description

Background Art

[0002] The new radio (NR) standard of the fifth generation mobile communication technology (5G) adopts a new end-to-end network architecture, which can provide extremely high data throughput and very reliable low-latency connections. The design of 5G NR enables effective reuse of different business models in three major scenarios.

[0003] Currently, a user terminal (UE) needs to be configured with different physical downlink control channel (PDCCH) monitoring capabilities for different service types. However, the above method increases the complexity of the UE.

[0004] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present disclosure, and therefore may include information that does not constitute the prior art known to ordinary technicians in the field. Summary of the invention

[0005] The purpose of the present disclosure is to provide a data transmission method, a data transmission device, a storage medium and an electronic device, thereby at least to a certain extent solving the problem of increasing UE complexity due to the limitations and defects of related technologies.

[0006] According to a first aspect of the present disclosure, a data transmission method is provided, comprising receiving a service request sent by a user terminal; querying a target carrier channel corresponding to the service request from a pre-configured carrier channel list; and sending service data corresponding to the service request to the user terminal based on the target carrier channel.

[0007] In an optional embodiment of the present disclosure, the data transmission method also includes determining the target service type corresponding to the target service request if there is no target carrier channel corresponding to the target service request in the carrier channel list; determining the target channel parameters of the target carrier channel based on the target number of time domain resources corresponding to the target service type; and constructing a target carrier channel for transmitting service data corresponding to the target service type based on the target channel parameters.

[0008] In an optional embodiment of the present disclosure, after receiving the target service request sent by the user terminal, the data transmission method also includes parsing the target service request to obtain multiple network slices corresponding to the target service request; and determining the service type corresponding to the target service request based on the slice identifiers of the multiple network slices.

[0009] In an optional embodiment of the present disclosure, after receiving the target service request sent by the user terminal, the data transmission method also includes parsing the target service request to obtain multiple service quality flows corresponding to the target service request; if the service identifier of the service quality flow is the target service identifier, then it is determined that the service type corresponding to the target service request is an ultra-high reliability and low-latency communication service.

[0010] In an optional embodiment of the present disclosure, the number of time domain resources of the target carrier channel corresponding to the ultra-high reliability and low latency communication service is greater than the number of time domain resources of the carrier channel corresponding to other service identifiers, and the other service identifiers are service identifiers other than the target service identifier.

[0011] In an optional embodiment of the present disclosure, before querying the target carrier channel corresponding to the target service request from a pre-configured carrier channel list, the data transmission method also includes determining each service type corresponding to each service request; determining the carrier channel corresponding to each service type according to the number of time domain resources corresponding to each service type; and constructing a carrier channel list based on the service type and the corresponding carrier channel.

[0012] In an optional embodiment of the present disclosure, before querying the target carrier channel corresponding to the service request from a pre-configured carrier channel list, the data transmission method also includes determining the service type corresponding to the service request; determining the carrier channel corresponding to the service type according to the downlink control information corresponding to each service type, and obtaining a carrier channel list of each service type and the corresponding carrier channel.

[0013] According to a second aspect of the present disclosure, a data transmission device is provided, including a service receiving module for receiving a target service request sent by a user terminal; a channel query module for querying a target carrier channel corresponding to the target service request from a pre-configured carrier channel list; and a data sending module for sending service data corresponding to the target service request to the user terminal based on the target carrier channel.

[0014] In an optional embodiment of the present disclosure, the information determination module is used to determine the target service type corresponding to the target service request if there is no target carrier channel corresponding to the target service request in the carrier channel list; the information determination module is used to determine the target channel parameters of the target carrier channel according to the target number of time domain resources corresponding to the target service type; and the data sending module is used to construct a target carrier channel for transmitting service data corresponding to the target service type according to the target channel parameters.

[0015] In an optional embodiment of the present disclosure, the information determination module can be used to parse the target business request to obtain multiple network slices corresponding to the target business request; and determine the business type corresponding to the target business request based on the slice identifiers of the multiple network slices.

[0016] In an optional embodiment of the present disclosure, the information determination module can be used to parse the target service request to obtain multiple service quality flows corresponding to the target service request; if the service identifier of the service quality flow is the target service identifier, the service type corresponding to the target service request is determined to be an ultra-high reliability and low-latency communication service.

[0017] In an optional embodiment of the present disclosure, the information determination module can be used to determine that the number of time domain resources of the target carrier channel corresponding to the ultra-high reliability and low latency communication service is greater than the number of time domain resources of the carrier channel corresponding to other service identifiers, and the other service identifiers are service identifiers other than the target service identifier.

[0018] In an optional embodiment of the present disclosure, the information determination module can be used to determine the service types corresponding to each service request; the information determination module can be used to determine the carrier channel corresponding to each service type based on the number of time domain resources corresponding to each service type; the channel construction module can be used to construct a carrier channel list based on each service type and the corresponding carrier channel.

[0019] In an optional embodiment of the present disclosure, the information determination module can be used to determine each service type corresponding to each service request; the information determination module can be used to determine the carrier channel corresponding to the service type according to the downlink control information corresponding to each service type, and obtain a carrier channel list of each service type and the corresponding carrier channel.

[0020] According to a third aspect of the present disclosure, a storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, any one of the above-mentioned data transmission methods is implemented.

[0021] According to a fourth aspect of the present disclosure, an electronic device is provided, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute any one of the above-mentioned data transmission methods by executing the executable instructions.

[0022] In the technical solutions provided in some embodiments of the present disclosure, a target service request sent by a user terminal is received; a target carrier channel corresponding to the target service request is queried from a pre-configured carrier channel list; and service data corresponding to the target service request is sent to the user terminal based on the target carrier channel. In this technical solution, the base station can query the target carrier channel corresponding to the target service request according to the target service request sent by the user terminal, thereby sending the received target service request to the terminal according to the target carrier channel. This technical solution avoids the problem in some technologies that the terminal is configured with service requests corresponding to different service requests, thereby increasing the complexity of the terminal.

[0023] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The drawings herein are incorporated into the specification and constitute a part of the specification, showing embodiments consistent with the present disclosure, and together with the specification, are used to explain the principles of the present disclosure. Obviously, the drawings described below are only some embodiments of the present disclosure, and for ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work. In the drawings:

[0025] Figure 1 A schematic diagram schematically illustrates a time slot-based PDCCH monitoring capability according to an exemplary embodiment of the present disclosure;

[0026] Figure 2 A schematic diagram schematically shows a PDCCH monitoring capability based on a monitoring range according to an exemplary embodiment of the present disclosure;

[0027] Figure 3 Schematically shows an architecture diagram of a data transmission system according to an exemplary embodiment of the present disclosure;

[0028] Figure 4 A flowchart of a data transmission method according to an exemplary embodiment of the present disclosure is schematically shown;

[0029] Figure 5 A flowchart of a method for determining a target service type corresponding to a target service request according to an exemplary embodiment of the present disclosure is schematically shown;

[0030] Figure 6 A flowchart of another data transmission method according to an exemplary embodiment of the present disclosure is schematically shown;

[0031] Figure 7 A block diagram schematically shows a data transmission device according to an exemplary embodiment of the present disclosure;

[0032] Figure 8 A block diagram schematically shows another data transmission device according to an exemplary embodiment of the present disclosure;

[0033] Fig. 9 A block diagram of an electronic device according to an exemplary embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0034] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as being limited to the examples set forth herein; on the contrary, these embodiments are provided so that the present disclosure will be more comprehensive and complete, and the concepts of the example embodiments are fully conveyed to those skilled in the art. The described features, structures, or characteristics may be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present disclosure. However, those skilled in the art will appreciate that the technical solutions of the present disclosure may be practiced while omitting one or more of the specific details, or other methods, components, devices, steps, etc. may be adopted. In other cases, known technical solutions are not shown or described in detail to avoid obscuring various aspects of the present disclosure.

[0035] In addition, the accompanying drawings are only schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the figures represent the same or similar parts, and their repeated description will be omitted. Some of the block diagrams shown in the accompanying drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities can be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and / or processor devices and / or microcontroller devices.

[0036] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the steps. For example, some steps may be decomposed, while some steps may be combined or partially combined, so the actual execution order may change according to the actual situation.

[0037] In order to facilitate understanding by those skilled in the art, some terms in the embodiments of the present disclosure are explained.

[0038] (1) Downlink Control Information (DCI), which is carried by PDCCH and is specifically sent by the base station to the UE. It can be used to carry the resource configuration information and other control information of the UE. The UE can correctly receive data in the physical downlink shared channel or send data in the physical uplink shared channel only after obtaining the DCI information.

[0039] (2) Slot and span. Slot refers to a basic time unit. Span is a time unit shorter than slot. A slot can include multiple spans.

[0040] (3) Control channel element (CCE): The basic unit of PDCCH. The actual time domain and frequency domain resources that need to be detected are determined in units of CCE.

[0041] (4) PDCCH monitoring capability or blind detection capability, including the maximum number of non-overlapping control channel elements (CCE) used for channel estimation and the maximum number of candidate PDCCHs. The maximum number of candidate PDCCHs refers to the maximum number of candidate PDCCHs that can be blindly detected in a span, and the maximum number of non-overlapping CCEs refers to the maximum number of CCEs for channel estimation when performing PDCCH blind detection in a span, so as to avoid unlimited PDCCH blind detection.

[0042] (5) Carrier Aggregation (CA): Carrier aggregation is a key technology in LTE-Advanced systems. It aggregates multiple contiguous or non-contiguous component carriers to obtain a larger transmission bandwidth, thereby achieving higher peak rate and throughput.

[0043] The design of 5G NR enables effective reuse of services of different models in three major scenarios, namely enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (URLLC) and massive machine type communication (mMTC). mMTC services can also be MIoT services. Among them, URLLC services have higher requirements on latency and reliability, and higher requirements on PDCCH monitoring capabilities than eMBB services and mMTC services.

[0044] In a communication system, a base station may send DCI information to a UE via a PDCCH, and the UE may decode received service data according to the DCI. One DCI may be transmitted in one PDCCH, and the UE may receive the DCI carried in the PDCCH through a blind detection capability.

[0045] The data transmission method provided by the embodiment of the present disclosure can be applied to an application scenario in which service data corresponding to a service request is transmitted to a UE, especially an application scenario in which service data corresponding to multiple service requests of different service types are transmitted to a UE. For example, a user uses the same UE to initiate multiple service requests at the same time, and the service request can be an eMBB service or a URLLC service. The base station can send the service data corresponding to the service request to the UE through a carrier channel.

[0046] At present, the R16 protocol introduces the PDCCH monitoring capability based on the monitoring range on the basis of the PDCCH monitoring capability based on the time slot in the R15 protocol. That is, the R16 protocol defines the PDCCH monitoring capability based on the time window, and a time slot contains multiple time windows, thereby increasing the PDCCH monitoring capability, effectively reducing the system latency and improving the system reliability.

[0047] Since users have different requirements for PDCCH monitoring capabilities for different service types, the UE needs to configure corresponding blind detection capabilities for different service types. However, this process inevitably increases the complexity of the UE, so that the problem of coexistence of PDCCH monitoring capabilities based on time slots and PDCCH monitoring capabilities based on monitoring ranges has not been solved in actual applications. For example, URLLC services are suitable for mobile devices, industrial control, unmanned driving, telemedicine and other fields. This type of service requires low network latency and high reliability. Therefore, URLLC services are suitable for PDCCH monitoring capabilities based on monitoring ranges. However, eMBB services and mMTC services have relatively low latency requirements. Therefore, eMBB services, mMTC services and other services are suitable for PDCCH monitoring capabilities based on time slots.

[0048] The following will be combined Figure 1 , Figure 2 The PDCCH monitoring capability for multiple types of services is described in detail.

[0049] Figure 1 A schematic diagram of a time slot-based PDCCH monitoring capability according to an exemplary embodiment of the present disclosure is schematically shown. Figure 1 , Figure 1 It is the time slot-based PDCCH monitoring capability defined in the R15 protocol, and M1 is the maximum number of candidate PDCCHs in a time slot, that is, the maximum number of candidate PDCCHs that the user terminal can blindly detect within a period of time is M1.

[0050] Figure 2 A schematic diagram of a PDCCH monitoring capability based on a monitoring range according to an exemplary embodiment of the present disclosure is schematically shown. Figure 2 , Figure 2It is the PDCCH monitoring capability based on monitoring range defined in R16 protocol. Each monitoring range corresponds to a monitoring time window, and a time slot contains multiple monitoring ranges, where M2 is the maximum number of candidate PDCCHs for each monitoring range. In order to consider the flexible scheduling requirements and terminal complexity of URLLC services, the total blind detection capability of the PDCCH monitoring capability based on monitoring range in a time slot is usually about twice that of the PDCCH monitoring capability based on time slot. The increase of blind detection capability can reduce latency and improve system reliability.

[0051] Considering the above problems, the exemplary embodiments of the present disclosure propose a data transmission method, which does not require the UE to configure different blind detection capabilities to report to the base station. Instead, when the base station receives a target service request, it queries the target carrier channel corresponding to the target service request from the pre-configured carrier channel list, thereby sending the service data corresponding to the target service request to the UE through the above target carrier channel, and the UE can directly process the received data. This realizes the differentiated requirements of different service types on PDCCH detection capabilities, greatly reducing the complexity of the user terminal.

[0052] Figure 3 The architecture diagram of the data transmission system provided by the embodiment of the present disclosure is as follows: Figure 3 As shown, the system includes a base station 30 and a UE 32. Among them, the UE 32 can send a target service request to the base station 30 through a carrier channel, and one service request corresponds to a service of a service type, such as: eMBB service, URLLC service or other service types. After receiving the target service request, the base station 30 queries the target carrier channel corresponding to the target service request from the pre-configured carrier channel list, and then sends the service data corresponding to the target service request to the UE 32 through the target carrier channel.

[0053] It should be understood that Figure 3 In the system architecture shown, the number of base stations 30 and UE 32 is only exemplary, and a greater or lesser number is within the scope of protection of the present application. In addition, in the above exemplary operation scenario, UE 32 can be, for example, a personal computer, a server, a PDA (Personal Digital Assistant), a notebook or any other computing device with networking capabilities.

[0054] After understanding the system architecture of the present disclosure, combined with Figure 4 The scheme of the data transmission method disclosed in the present invention is described in detail.

[0055] Figure 4The flowchart of a data transmission method provided by the embodiment of the present disclosure is as follows. The embodiment of the present disclosure provides a data transmission method, which can be executed by any device for executing the data transmission method, and the device can be implemented by software and / or hardware. In this embodiment, the device can be integrated in Figure 3 In the base station 30 shown. Figure 4 As shown, the data transmission method provided by the embodiment of the present disclosure may include the following steps:

[0056] S40. Receive a service request sent by a user terminal.

[0057] In an exemplary embodiment of the present disclosure, the UE sends a service request to the base station through an established protocol data unit (PDU) session. At the same time, when the UE establishes the PDU session, a carrier channel for transmitting the service request between the terminal and the base station is established.

[0058] S42. Query the target carrier channel corresponding to the target service request from the pre-configured carrier channel list.

[0059] Specifically, the pre-configured carrier channel list includes carrier channels corresponding to multiple carriers with different frequencies, and pre-configures the correspondence between different service types and carrier channels with different frequencies, that is, service type-carrier channel. Taking URLLC service and eMBB service as examples, developers can pre-configure the frequency f corresponding to the eMBB service. 1 The carrier frequency f corresponding to the URLLC service 2 If the base station determines that the received service request is an eMBB service, it will increase the frequency f 1 The carrier channel corresponding to the carrier of is determined as the target carrier channel. Similarly, the frequency f 2 The carrier channel corresponding to the carrier is determined as the target carrier channel of the URLLC service.

[0060] According to some embodiments of the present disclosure, before querying the target carrier channel corresponding to the target service request from a pre-configured carrier channel list, determine the service types corresponding to each service request; determine the carrier channel corresponding to each service type based on the number of time domain resources corresponding to each service type; and construct a carrier channel list based on the service type and the corresponding carrier channel.

[0061] The service type is the type of service corresponding to the service request, for example, URLLC services with high latency and reliability requirements, and eMBB services, mMTC services or other services with low latency and reliability requirements. The number of time domain resources is the PDCCH monitoring capability, that is, the maximum number of CCEs and the maximum number of candidate PDCCHs.

[0062] Specifically, the UE can concurrently send multiple service requests, each of which can carry different service types. The service types can be services of different models under the three major 5G scenarios and other service types, namely URLLC tasks, eMBB tasks, mMTC services and other service types. The carrier channel corresponding to the service type is determined according to the PDCCH monitoring capability required by the service type. The carrier channel is configured with the same PDCCH monitoring capability as that required by the service type, thereby establishing a corresponding relationship between the service type and the determined carrier channel and adding it to the carrier channel list.

[0063] The following will take the case where the service request includes both URLLC tasks and eMBB tasks and different carrier channels have different maximum numbers of PDCCH candidates as an example for explanation.

[0064] When the base station determines that the service type corresponding to the service request is a URLLC service, because the URLLC service is applicable to the PDCCH monitoring capability based on the monitoring range, according to the blind detection capability that the URLLC service expects to use in each monitoring time window, the carrier channel that matches the expected blind detection capability can be determined as the target carrier channel, and a carrier channel list between the URLLC service and the carrier channel can be obtained.

[0065] When the base station determines that the service type corresponding to the service request is an eMBB service, the eMBB service is applicable to the time slot-based PDCCH monitoring capability. Then, according to the blind detection capability expected to be used in each time slot, the carrier channel that matches the blind detection capability is determined as the target carrier channel, thereby obtaining a carrier channel list between the eMBB service and the carrier channel.

[0066] By determining the carrier channel corresponding to each service type through the number of time domain resources corresponding to the service type, not only can the differentiated requirements of different service types for PDCCH monitoring capabilities be met, but also without increasing the complexity of the UE, the same UE can realize the multiplexing of URLLC services and other service types.

[0067] For example, based on the R15 protocol, the R16 protocol not only enhances the PDCCH monitoring capability, but also includes enhancements of other capabilities, such as DCI, multiple-input multiple-output enhancement, etc. The following will take DCI as an example for description.

[0068] In another exemplary embodiment of the present disclosure, before querying the target carrier channel corresponding to the target service request from the pre-configured carrier channel list, the service types corresponding to the service requests are determined; the carrier channel corresponding to the service type is determined according to the DCI corresponding to the service type, and a carrier channel list of each service type and the corresponding carrier channel is obtained.

[0069] The compression of DCI information or the default indication field information in DCI can reduce the size of DCI.

[0070] Specifically, when the UE sends multiple service requests at the same time, the base station can determine the service type corresponding to each service request, such as URLLC service, eMBB service, and others. Since the URLLC service requires an ultra-low latency communication process, it is necessary to reduce the size of the DCI information, while the eMBB service and other service types do not need to reduce the size of the DCI information. Therefore, the carrier channel that matches the service type's requirements for the DCI information can be determined, thereby establishing a carrier channel list of service type-DCI information size.

[0071] Similarly, an example is taken in which a service request includes URLLC tasks, eMBB tasks, and different carrier channels with different sizes of DCI information.

[0072] When the base station determines that the service type corresponding to the service request is a URLLC service, because the URLLC service is suitable for a small amount of DCI information, the carrier channel configured with a small amount of DCI information is used as the first target carrier channel for the URLLC service. For example, the carrier channel that performs DCI compression or indicates the domain in the default DCI is used as the first target carrier channel, thereby constructing a carrier channel list of the URLLC service-first target carrier channel.

[0073] When the base station determines that the service type corresponding to the service request is an eMBB service, because the eMBB service is suitable for a large amount of DCI information, the carrier channel configured with a large amount of DCI information is used as the second target carrier channel for the eMBB service. For example, the carrier channel that has not performed DCI compression or the indication field in the DCI is not defaulted is used as the second target carrier channel, thereby constructing a carrier channel list of the eMBB service-second target carrier channel.

[0074] By building a carrier channel list based on the different DCI information requirements of different service types, the base station can allocate the corresponding service type to the target carrier channel that matches it for service data transmission. This solves the differentiated requirements of different service types for DCI information size, and avoids configuring different DCI information sizes in the UE to report to the base station for service data transmission, thereby reducing the complexity of the UR.

[0075] On the basis of the above embodiment, different carrier channels are in a CA scenario, which not only increases the transmission bandwidth between the base station and the user terminal, but also enables the PDCCH monitoring capabilities used for different service types to coexist for the same UE and be independent of each other, or enables the DCI information sizes used for different service types to coexist for the same UE and be independent of each other.

[0076] S44. Send the service data corresponding to the target service request to the user terminal through the target carrier channel.

[0077] Specifically, after determining the target carrier channel corresponding to the target service request in step S42, the base station may send the service data corresponding to the target service request to the UE.

[0078] In the technical solutions provided in some embodiments of the present disclosure, a target service request sent by a user terminal is received; a target carrier channel corresponding to the target service request is queried from a pre-configured carrier channel list; and service data corresponding to the target service request is sent to the user terminal based on the target carrier channel. In this technical solution, the base station can query the target carrier channel corresponding to the target service request according to the target service request sent by the user terminal, thereby sending the received target service request to the terminal according to the target carrier channel. This technical solution avoids the problem in some technologies that the terminal is configured with service requests corresponding to different service requests, thereby increasing the complexity of the terminal.

[0079] In the above exemplary embodiments, there is a target carrier channel corresponding to the target service request in the pre-configured carrier channel list. If the base station does not query the target carrier channel corresponding to the target service request from the pre-configured carrier channel list, it is necessary to construct a target carrier channel to transmit the service data corresponding to the target service request to the UE.

[0080] In an exemplary embodiment of the present disclosure, if the target carrier channel corresponding to the target service request does not exist in the carrier channel list, the target service type corresponding to the target service request is determined; based on the target number of time domain resources corresponding to the target service type, the target channel parameters of the target carrier channel are determined; and based on the target channel parameters, a target carrier channel for transmitting service data corresponding to the target service type is constructed.

[0081] The target channel parameters are parameter information for constructing a target carrier channel, which may include a carrier with a frequency corresponding to the target service type and the target number of time domain resources required by the target service type, ie, PDCCH monitoring capability.

[0082] Specifically, when the base station does not query the target carrier channel corresponding to the target service request from the pre-configured carrier channel list, the base station may construct a target carrier channel for transmitting service data corresponding to the target service type.

[0083] Taking the target service type as URLLC service as an example, first, when the base station determines that the service type corresponding to the target service request is URLLC service, the base station can allocate the URLLC service to the carrier channel corresponding to the URLLC service at the Medium Access Control (MAC) layer and send it to the UE.

[0084] Then, when the pre-configured carrier channel list does not contain the target carrier channel corresponding to the URLLC service, the base station will send a radio resource control (RRC) signaling to the UE to establish an RRC connection between the base station and the UE, and allocate corresponding carrier resources to determine the carrier with a frequency f pre-configured for the URLLC service.

[0085] Finally, according to the target number of time domain resources required by the URLLC service, that is, the maximum number of PDCCH candidates, it can be determined that when constructing the target carrier channel based on the carrier with frequency f, it is necessary to simultaneously configure the PDCCH monitoring capability corresponding to the URLLC service, thereby forming the target carrier channel corresponding to the URLLC service.

[0086] By constructing a target carrier channel corresponding to the target service type to transmit the service data corresponding to the target service type, a carrier channel can be constructed according to the different requirements of the service type for PDCCH monitoring capabilities, thereby solving the differentiated requirements of different service types for PDCCH monitoring capabilities, and thus avoiding the problem of increased UE complexity caused by configuring multiple PDCCH monitoring capabilities in the UE.

[0087] In an exemplary embodiment of the present disclosure, the number of time domain resources of the target carrier channel corresponding to the URLLC service is greater than the number of time domain resources of the target carrier channel corresponding to other service identifiers, and the other service identifiers are service identifiers other than the target service identifier.

[0088] Among them, other service identifiers may be a general term for all service identifiers except the target service identifier. Other service types may be determined by other service identifiers, and other service types may be eMBB services, MIoT services, etc.

[0089] The URLLC service has high requirements for PDCCH monitoring capabilities, and the number of time domain resources of the corresponding target carrier channel is greater than that of other service types, that is, in one time slot resource, the maximum number of candidate PDCCHs configured for the target carrier channel corresponding to the URLLC service is greater than the maximum number of candidate PDCCHs configured for the carrier channel corresponding to other service types. In an exemplary embodiment of the present disclosure, the subcarrier spacing of the target carrier channel corresponding to the URLLC service is large, and its corresponding bandwidth width in the frequency domain resources is large. Exemplarily, the type of service to be transmitted can be determined based on the subcarrier spacing configured for each carrier channel. For example, a carrier channel with a larger subcarrier spacing is determined as the target carrier channel for transmitting the URLLC service.

[0090] In the above embodiment, the target carrier channel corresponding to the URLLC service has a stronger PDCCH monitoring capability configured in its carrier channel compared with other service types such as the eMBB service, thereby improving the transmission performance of the carrier channel and thus being more adaptable to the high requirements of the URLLC service for latency and reliability.

[0091] In actual applications, the base station will receive a large number of target service requests sent by UEs at the same time. Therefore, the base station can determine whether the target service type corresponding to each target service request is a URLLC service, and then query the target carrier channel corresponding to the target service type to transmit the service data corresponding to the URLLC service through the target carrier channel.

[0092] Next, taking the target service types of URLLC service and eMBB service as an example, Figure 5 The process of the base station determining the target service type corresponding to the target service request is described in detail.

[0093] Figure 5 The following schematically shows a flow chart of a method for determining a target service type corresponding to a target service request according to an exemplary embodiment of the present disclosure. Figure 5 In step S500, it is determined whether network slicing is set in the network.

[0094] For 5G wireless networks, network slicing is mainly reflected in admission control, network selection and resource separation. If network slicing is configured in the network, the base station will preferentially carry the received target service request in the network slice configured in the network. A network slice may contain one or more PDU sessions, that is, a network slice may contain one or more service requests, and a PDU session cannot be configured across network slices, so one service request corresponds to one network slice.

[0095] In an exemplary implementation of the present disclosure, in step S502, the base station parses the target service request to obtain multiple network slices corresponding to the target service request.

[0096] Exemplarily, after receiving multiple target service requests, the base station can determine the network slice where each target service request is located according to the identifier of each target service request.

[0097] After determining the multiple network slices where each target service request is located, step S504 can be executed to determine the service type corresponding to the target service request based on the slice identifiers of the multiple network slices.

[0098] Specifically, a PDU session contains the network slice identifier S-NSSAI of the network slice, where the S-NSSAI format is shown in Table 1:

[0099] Table 1

[0100] SST SD

[0101] As can be seen from Table 1, the network slice identifier S-NSSAI includes a Slice / Service type (SST) for indicating the network slice or service type and a Slice Differentiator (SD) for indicating the network slice differentiation.

[0102] Among them, the SST values ​​are divided into standardized and non-standardized. The existing standardized SST values ​​are shown in Table 2, which are eMBB, URLLC, MIoT, and vehicle wireless communication technology (Vehicle to Everything, V2X). Non-standardized values ​​can be defined by operators based on their own deployed network slices.

[0103] Table 2

[0104] Network slice or service type SST value Chinese name eMBB 1 Enhanced Mobile Broadband URLLC 2 Ultra-reliable and low-latency communications MIoT 3 Massive IoT Communications V2X 4 Wireless communication technology for vehicles

[0105] The SST value is used to distinguish the scenario type of network slicing applications, and SD is used to distinguish different network slices more finely at the SST level. For example, when the SST value is 4, the scenario type of the network slicing application is V2X, and the SD value can be used to distinguish different car companies.

[0106] When determining the service type corresponding to the target service request according to the slice identifiers of multiple network slices in step S504, the SST value in the slice identifier S-NSSAI corresponding to the target service request can be obtained, thereby determining the service type of the target service request according to the SST value.

[0107] After determining the service type requested by the target service, step S506 may be executed to transmit the service data corresponding to the URLLC service and the eMBB service respectively through the queried or established target carrier channel.

[0108] In the above process, the service type corresponding to the target service request is determined by the slice identifier of the network slice, so that the base station can quickly determine the service type according to the slice identifier, so that different service types can transmit service data through the corresponding target carrier channel, solving the differentiated requirements of different service types for PDCCH monitoring capabilities.

[0109] In another exemplary embodiment of the present disclosure, if network slicing is not set in the network, step S508 is executed to parse the target service request to obtain multiple QoS flows corresponding to the target service request, namely, quality of service (QoS) flows, and the base station can determine the QoS flow in the PDU session according to the identifier of the target service request.

[0110] After obtaining multiple QoS flows, in step S510, it is determined whether the service identifier of the QoS flow is the target service identifier.

[0111] Specifically, in the 5G system, a QoS flow is identified by a QoS flow identifier (QFI), which can be dynamically allocated or equal to the 5G QoS flow identifier (5G QoS Identifier, 5QI). Data with the same QFI in a PDU session will receive the same forwarding processing, where the forwarding processing can be scheduling, admission threshold, priority, etc.

[0112] The base station can map the packets received by each QoS flow into the DRB, that is, the base station can map one or more QoS flows into one DRB, and the base station can identify the URLLC service from the QFI.

[0113] If it is a target service identifier, that is, an identifier corresponding to a URLLC service, step S512 is executed to determine that the service type corresponding to the target service request is a URLLC service. Otherwise, step S514 is executed to determine that the service type corresponding to the target service request is an eMBB service.

[0114] In the above process, whether the URLLC service is included is determined by the QoS flow corresponding to the target service request, so that the service type is transmitted using the corresponding carrier channel.

[0115] It should be noted that although the steps of the method in the present disclosure are described in a specific order in the drawings, this does not require or imply that the steps must be performed in this specific order, or that all the steps shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps, etc.

[0116] The following will be combined Figure 6 The process of using different carrier channels to transmit service data corresponding to different service requests is described in detail.

[0117] In step S601, a target service request sent by the UE is received based on the first carrier channel. The UE can initiate a PDU session request. At this time, relative to the base station, the UE sends a target service request through the established first carrier channel, wherein the PDCCH monitoring capability of the first carrier channel corresponds to the time slot-based PDCCH monitoring capability in the R15 protocol, which is applicable to eMBB services. The target service request sent by the UE may be one or more, and the corresponding service type may also be one or more. The following is an example in which the target service request sent by the UE includes both URLLC services and eMBB services.

[0118] According to some embodiments of the present disclosure, in step S603, whether network slicing is set in the network. If network slicing is set in the network, step S605 is executed to determine the slice identifier of each network slice. The base station can obtain the slice identifier of each network slice, so that the service type can be determined by the slice identifier S-NSSAI of the network slice, specifically, the network slice corresponding to the URLLC service can be determined according to the SST value in the slice identifier.

[0119] Execute step S607 to determine whether it is a URLLC service network slice. If so, execute step S613 for all URLLC service network slices to query or construct a second carrier channel to transmit URLLC services based on the second carrier channel if the second carrier channel exists. If it is not a URLLC service network slice, execute step S615 to transmit eMBB services based on the first carrier channel.

[0120] According to some embodiments of the present disclosure, if network slicing is not set in the network, step S609 is performed to determine the QFI corresponding to the QoS flow. The base station can determine the service type corresponding to each QoS flow through the QFI corresponding to each QoS flow.

[0121] Then, step S611 is executed to determine whether it is a QoS flow corresponding to the URLLC service. The base station determines the URLLC service according to the QFI. If the QoS flow is a URLLC service, step S613 is executed to query or construct a second carrier channel to transmit the URLLC service based on the second carrier channel if the second carrier channel exists. If it is not a QoS flow for the URLLC service, step S615 is executed to transmit the eMBB service based on the first carrier channel. Among them, the PDCCH monitoring capability configured by the second carrier channel is higher than the PDCCH monitoring capability configured by the first carrier channel, or the second carrier channel is configured with DCI compression or the default indication field in the DCI to reduce the DCI size, etc., while the first carrier channel does not perform DCI compression or the default indication field in the DCI to reduce the DCI size, etc.

[0122] Furthermore, in order to implement the above data transmission method, a data transmission device is provided in one embodiment of the present disclosure.

[0123] Figure 7 The block diagram of a data transmission device according to an exemplary embodiment of the present disclosure is schematically shown, wherein the data transmission device 7 comprises a service receiving module 70 , a channel query module 72 and a data sending module 74 .

[0124] The service receiving module 70 can be used to receive a target service request sent by a user terminal; the channel query module 72 can be used to query a target carrier channel corresponding to the target service request from a pre-configured carrier channel list; the data sending module 74 can be used to send service data corresponding to the target service request to the user terminal based on the target carrier channel.

[0125] The data transmission device 7 provided in the embodiment of the present disclosure can execute the technical solution of the data transmission method in any of the above-mentioned embodiments. Its implementation principle and beneficial effects are similar to the implementation principle and beneficial effects of the data transmission method. Please refer to the implementation principle and beneficial effects of the data transmission method, and no further details will be given here.

[0126] Furthermore, another data transmission device is provided in an embodiment of the present disclosure.

[0127] Figure 8 The block diagram of another data transmission device according to an exemplary embodiment of the present disclosure is schematically shown, wherein the data transmission device 8 comprises an information determination module 80 and a channel construction module 82 .

[0128] In an exemplary embodiment of the present disclosure, the data transmission device includes an information determination module 80 that can be used to determine the target service type corresponding to the target service request if there is no target carrier channel corresponding to the target service request in the carrier channel list; the information determination module 80 can be used to determine the target channel parameters of the target carrier channel according to the target number of time domain resources corresponding to the target service type; the channel construction module 82 can be used to construct a target carrier channel for transmitting service data corresponding to the target service type according to the target channel parameters.

[0129] In an exemplary embodiment of the present disclosure, the information determination module 80 can be used to parse the target business request to obtain multiple network slices corresponding to the target business request; and determine the business type corresponding to the target business request based on the slice identifiers of the multiple network slices.

[0130] In an exemplary embodiment of the present disclosure, the information determination module 80 can be used to parse the target service request to obtain multiple service quality flows corresponding to the target service request; if the service identifier of the service quality flow is the target service identifier, the service type corresponding to the target service request is determined to be an ultra-high reliability and low-latency communication service.

[0131] In an exemplary embodiment of the present disclosure, the number of time domain resources of the target carrier channel corresponding to the ultra-high reliability and low latency communication service is greater than the number of time domain resources of the carrier channel corresponding to other service identifiers, and the other service identifiers are service identifiers other than the target service identifier.

[0132] In an exemplary embodiment of the present disclosure, the information determination module 80 can be used to determine the service types corresponding to each service request; the information determination module 80 can be used to determine the carrier channel corresponding to each service type according to the number of time domain resources corresponding to each service type; the channel construction module 82 can be used to construct a carrier channel list based on the service type and the corresponding carrier channel.

[0133] In an exemplary embodiment of the present disclosure, the information determination module 80 can be used to determine each service type corresponding to each service request; the information determination module 80 can be used to determine the carrier channel corresponding to the service type according to the downlink control information corresponding to each service type, and obtain a carrier channel list of each service type and the corresponding carrier channel.

[0134] The data transmission device 8 provided in the embodiment of the present disclosure can execute the technical solution of the data transmission method in any of the above-mentioned embodiments. Its implementation principle and beneficial effects are similar to the implementation principle and beneficial effects of the data transmission method. Please refer to the implementation principle and beneficial effects of the data transmission method, and no further details will be given here.

[0135] In an exemplary embodiment of the present disclosure, a computer-readable storage medium is also provided, on which a program product capable of implementing the above method of the present specification is stored. In some possible implementations, various aspects of the present invention may also be implemented in the form of a program product, which includes a program code, and when the program product is run on a user terminal, the program code is used to enable the user terminal to execute the steps according to various exemplary embodiments of the present invention described in the above "Exemplary Method" section of the present specification.

[0136] The program product for implementing the above method according to an embodiment of the present invention may adopt a portable compact disk read-only memory (CD-ROM) and include program code, and may be run on a user terminal, such as a personal computer. However, the program product of the present invention is not limited thereto, and in this document, a readable storage medium may be any tangible medium containing or storing a program, which may be used by or in combination with an instruction execution system, apparatus, or device.

[0137] The program product may use any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0138] Computer readable signal media may include data signals propagated in baseband or as part of a carrier wave, in which readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Readable signal media may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0139] The program code embodied on the readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.

[0140] Program code for performing the operations of the present invention may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., through the Internet using an Internet service provider).

[0141] In an exemplary embodiment of the present disclosure, an electronic device capable of implementing the above method is also provided.

[0142] It will be appreciated by those skilled in the art that various aspects of the present invention may be implemented as a system, method or program product. Therefore, various aspects of the present invention may be specifically implemented in the following forms, namely: a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software, which may be collectively referred to herein as a "circuit", "module" or "system".

[0143] Refer to the following Fig. 9 An electronic device 900 according to this embodiment of the present invention will be described. Fig. 9 The electronic device 900 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0144] like Fig. 9 As shown, the electronic device 900 is in the form of a general computing device. The components of the electronic device 900 may include, but are not limited to: the at least one processing unit 910, the at least one storage unit 920, a bus 930 connecting different system components (including the storage unit 920 and the processing unit 910), and a display unit 940.

[0145] The storage unit stores program codes, which can be executed by the processing unit 910, so that the processing unit 910 performs the steps of various exemplary embodiments of the present invention described in the above “Exemplary Method” section of this specification. For example, the processing unit 910 can perform the following steps: Figure 4 Steps S40 to S44 shown in FIG.

[0146] The storage unit 920 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 9201 and / or a cache storage unit 9202 , and may further include a read-only storage unit (ROM) 9203 .

[0147] The storage unit 920 may also include a program / utility 9204 having a set (at least one) of program modules 9205, such program modules 9205 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0148] Bus 930 may represent one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

[0149] The electronic device 900 may also communicate with one or more external devices 1000 (e.g., keyboards, pointing devices, Bluetooth devices, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device 900, and / or communicate with any device that enables the electronic device 900 to communicate with one or more other computing devices (e.g., routers, modems, etc.). Such communication may be performed via an input / output (I / O) interface 950. Furthermore, the electronic device 900 may also communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) via a network adapter 960. As shown, the network adapter 960 communicates with other modules of the electronic device 900 via a bus 930. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 900, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, etc.

[0150] Through the description of the above implementation, it is easy for those skilled in the art to understand that the example implementation described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the implementation of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the implementation of the present disclosure.

[0151] In addition, the above-mentioned figures are only schematic illustrations of the processes included in the method according to an exemplary embodiment of the present invention, and are not intended to be limiting. It is easy to understand that the processes shown in the above-mentioned figures do not indicate or limit the time sequence of these processes. In addition, it is also easy to understand that these processes can be performed synchronously or asynchronously, for example, in multiple modules.

[0152] It should be noted that, although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into multiple modules or units to be embodied.

[0153] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary technical means in the art that are not disclosed in the present disclosure. The specification and examples are to be considered as exemplary only, and the true scope and spirit of the present disclosure are indicated by the claims.

[0154] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A data transmission method, characterized in that: include: Receiving a target service request sent by a user terminal; Querying a target carrier channel corresponding to the target service request from a pre-configured carrier channel list; wherein the carrier channel list is constructed based on each service type corresponding to each service request and the corresponding carrier channel, and the carrier channel corresponding to each service type is determined by the number of time domain resources corresponding to each service type, and the number of time domain resources is the PDCCH monitoring capability, and the carrier channel service corresponding to each service type is configured with a PDCCH monitoring capability that is the same as the PDCCH monitoring capability required by each service type; The service data corresponding to the target service request is sent to the user terminal through the target carrier channel.

2. The data transmission method according to claim 1, characterized in that: The data transmission method further comprises: If the target carrier channel corresponding to the target service request does not exist in the carrier channel list, determining the target service type corresponding to the target service request; Determining a target channel parameter of a target carrier channel according to the target number of time domain resources corresponding to the target service type; A target carrier channel for transmitting service data corresponding to the target service type is constructed according to the target channel parameters.

3. The data transmission method according to claim 1, characterized in that: After receiving the target service request sent by the user terminal, the data transmission method further includes: Parsing the target service request to obtain multiple network slices corresponding to the target service request; Determine the service type corresponding to the target service request according to the slice identifiers of the multiple network slices.

4. The data transmission method according to claim 1, characterized in that: After receiving the target service request sent by the user terminal, the data transmission method further includes: Parsing the target service request to obtain multiple service quality flows corresponding to the target service request; If the service identifier of the service quality flow is a target service identifier, it is determined that the service type corresponding to the target service request is an ultra-high reliability and low latency communication service.

5. The data transmission method according to claim 4, characterized in that: The number of time domain resources of the target carrier channel corresponding to the ultra-high reliability and low latency communication service is greater than the number of time domain resources of the carrier channel corresponding to other service identifiers, and the other service identifiers are service identifiers other than the target service identifier.

6. The data transmission method according to claim 1, characterized in that: Before querying the target carrier channel corresponding to the service request from the pre-configured carrier channel list, the data transmission method further includes: Determine each service type corresponding to each of the service requests; The carrier channel corresponding to each of the service types is determined according to the downlink control information corresponding to each of the service types, and the carrier channel list of each of the service types and the corresponding carrier channels is obtained.

7. A data transmission device, characterized in that: include: A service receiving module, used for receiving a target service request sent by a user terminal; A channel query module, used to query the target carrier channel corresponding to the target service request from a pre-configured carrier channel list; wherein the carrier channel list is constructed based on each service type corresponding to each service request and the corresponding carrier channel, the carrier channel corresponding to each service type is determined by the number of time domain resources corresponding to each service type, the number of time domain resources is the PDCCH monitoring capability, and the carrier channel service corresponding to each service type is configured with the same PDCCH monitoring capability as the PDCCH monitoring capability required by each service type; A data sending module is used to send the service data corresponding to the target service request to the user terminal based on the target carrier channel.

8. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the data transmission method according to any one of claims 1 to 6 is implemented.

9. An electronic device, characterized in that: include: processor; as well as A memory, configured to store executable instructions of the processor; The processor is configured to execute the data transmission method according to any one of claims 1 to 6 by executing the executable instructions.

Images