CN115175197B

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

Info

Publication number: CN115175197B
Application number: CN202210793707.7A
Authority: CN
Inventors: 赵晓垠; 黄韬; 胡春雷; 王庆扬
Original assignee: China Telecom Corp Ltd
Current assignee: China Telecom Corp Ltd
Priority date: 2022-07-05
Filing date: 2022-07-05
Publication date: 2025-05-02
Anticipated expiration: 2042-07-05
Also published as: CN115175197A

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

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

Technical Field

The present disclosure relates to the field of wireless communication technologies, and in particular, to a data transmission method, a data transmission device, a storage medium, and an electronic apparatus.

Background

The New air interface (NR) standard of the fifth generation mobile communication technology (5th Generation Mobile Communication Technology,5G) employs a New end-to-end network architecture, which can provide extremely high data throughput and very reliable low-latency connection. And the design of 5G NR makes the service types of different models realize effective multiplexing in three scenes.

Currently, a User Equipment (UE) needs to configure monitoring capabilities of different physical downlink control channels (Physical Downlink Control Channel, PDCCH) for different service types. However, the above method increases the complexity of the UE.

It should be noted that the information disclosed in the above background section is only for enhancing understanding of the background of the present disclosure and thus may include information that does not constitute prior art known to those of ordinary skill in the art.

Disclosure of Invention

An object of the present disclosure is to provide a data transmission method, a data transmission apparatus, a storage medium, and an electronic device, which further solve, at least to some extent, the problem of increasing UE complexity due to limitations and drawbacks of the related art.

According to a first aspect of the present disclosure, a data transmission method is provided, which includes 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.

In an optional embodiment of the disclosure, the data transmission method further includes determining a 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 a target channel parameter of the target carrier channel according to a target time domain resource number corresponding to the target service type, and constructing a target carrier channel for transmitting service data corresponding to the target service type according to the target channel parameter.

In an optional embodiment of the disclosure, after receiving a target service request sent by a user terminal, the data transmission method further includes analyzing the target service request to obtain a plurality of network slices corresponding to the target service request, and determining a service type corresponding to the target service request according to slice identifiers of the plurality of network slices.

In an optional embodiment of the disclosure, after receiving a target service request sent by a user terminal, the data transmission method further includes analyzing the target service request to obtain a plurality of service quality flows corresponding to the target service request, and if a service identifier of the service quality flow is a target service identifier, determining that a service type corresponding to the target service request is an ultra-high reliable and low-delay communication service.

In an alternative 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 channels corresponding to other service identifiers, which are service identifiers other than the target service identifier.

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

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

According to a second aspect of the present disclosure, there is provided a data transmission apparatus, including a service receiving module configured to receive a target service request sent by a user terminal, a channel querying module configured to query a target carrier channel corresponding to the target service request from a pre-configured carrier channel list, and a data sending module configured to send service data corresponding to the target service request to the user terminal based on the target carrier channel.

In an optional embodiment of the disclosure, the information determining module is configured to determine a 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 determining module is configured to determine a target channel parameter of the target carrier channel according to a target time domain resource number corresponding to the target service type, and the data sending module is configured to construct a target carrier channel for transmitting service data corresponding to the target service type according to the target channel parameter.

In an optional embodiment of the disclosure, the information determining module may be configured to parse the target service request to obtain a plurality of network slices corresponding to the target service request, and determine a service type corresponding to the target service request according to slice identifiers of the plurality of network slices.

In an optional embodiment of the disclosure, the information determining module may be configured to parse the target service request to obtain a plurality of service quality flows corresponding to the target service request, and determine that the service type corresponding to the target service request is an ultra-high reliable and low-latency communication service if the service identifier of the service quality flow is the target service identifier.

In an optional embodiment of the disclosure, the information determining module may be configured 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 channels corresponding to other service identifiers, where the other service identifiers are service identifiers other than the target service identifier.

In an optional embodiment of the disclosure, the information determining module may be configured to determine each service type corresponding to each service request, the information determining module may be configured to determine a carrier channel corresponding to each service type according to a time domain resource number corresponding to each service type, and the channel construction module may be configured to construct a carrier channel list based on each service type and the corresponding carrier channel.

In an optional embodiment of the disclosure, the information determining module may be configured to determine each service type corresponding to each service request, and the information determining module may be configured to determine a carrier channel corresponding to the service type according to downlink control information corresponding to each service type, so as to obtain a carrier channel list of each service type and the corresponding carrier channel.

According to a third aspect of the present disclosure, there is provided a storage medium having stored thereon a computer program which, when executed by a processor, implements any of the above-described data transmission methods.

According to a fourth aspect of the present disclosure, there is provided an electronic device comprising a processor and a memory for storing executable instructions of the processor, wherein the processor is configured to perform any one of the above-described data transmission methods via execution of the executable instructions.

In some embodiments of the present disclosure, a target service request sent by a user terminal is received; and sending the service data corresponding to the target service request to the user terminal based on the target carrier channel. In the technical scheme, the base station can query a target carrier channel corresponding to the target service request according to the target service request sent by the user terminal, so that the received target service request is sent to the terminal according to the target carrier channel. The technical scheme avoids the problem that in some technologies, the terminal is configured corresponding to the service requests aiming at different service requests, so that the complexity of the terminal is increased.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure. It will be apparent to those of ordinary skill in the art that the drawings in the following description are merely examples of the disclosure and that other drawings may be derived from them without undue effort. In the drawings:

fig. 1 schematically illustrates a schematic diagram of a slot-based PDCCH monitoring capability according to an exemplary embodiment of the present disclosure;

Fig. 2 schematically illustrates a schematic diagram of a monitoring range-based PDCCH monitoring capability according to an exemplary embodiment of the present disclosure;

Fig. 3 schematically illustrates an architecture diagram of a data transmission system according to an exemplary embodiment of the present disclosure;

Fig. 4 schematically illustrates a flow chart of a data transmission method according to an exemplary embodiment of the present disclosure;

FIG. 5 schematically illustrates a flow chart of a method of determining a target service type corresponding to a target service request according to an exemplary embodiment of the present disclosure;

fig. 6 schematically illustrates another data transmission method flow diagram according to an exemplary embodiment of the present disclosure;

fig. 7 schematically illustrates a block diagram of a data transmission device according to an exemplary embodiment of the present disclosure;

Fig. 8 schematically illustrates a block diagram of another data transmission apparatus according to an exemplary embodiment of the present disclosure;

fig. 9 schematically illustrates a block diagram of an electronic device according to an exemplary embodiment of the present disclosure.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments may be embodied in many forms and should not be construed as limited to the examples set forth herein, but rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the present disclosure. One skilled in the relevant art will recognize, however, that the aspects of the disclosure may be practiced without one or more of the specific details, or with other methods, components, devices, steps, etc. In other instances, well-known technical solutions have not been shown or described in detail to avoid obscuring aspects of the present disclosure.

Furthermore, the drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus a repetitive description thereof will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in software or in one or more hardware modules or integrated circuits or in different networks and/or processor devices and/or microcontroller devices.

The flow diagrams depicted in the figures are exemplary only and not necessarily all steps are included. For example, some steps may be decomposed, and some steps may be combined or partially combined, so that the order of actual execution may be changed according to actual situations.

To facilitate understanding by those skilled in the art, some of the terms in the embodiments of the present disclosure will be explained.

(1) Downlink control information (Downlink Control Information, DCI), which is carried by the PDCCH, specifically, downlink control information sent to the UE by the base station, may be used to carry resource configuration information and other control information of the UE, where the UE obtains the DCI information, and can correctly receive data in the physical downlink shared channel or send data in the physical uplink shared channel.

(2) Slots (slots), which refer to one basic time unit, and time windows (spans). span is a unit of time shorter than slot. A slot may include multiple spans.

(3) A Control Channel Element (CCE) CHANNEL ELEMENT constitutes a basic unit of the PDCCH, and determines actual time-domain and frequency-domain resources to be detected in CCE units.

(4) PDCCH monitoring capability or blind detection capability, including a maximum number of non-overlapping Control Channel Elements (CCEs) CHANNEL ELEMENT for channel estimation and a maximum number of PDCCH candidates. The maximum number of candidate PDCCHs refers to the number of blind detection of at most a plurality of candidate PDCCHs in one span, and the maximum number of non-overlapping CCEs refers to the number of CCEs which are subjected to channel estimation at most when the PDCCH blind detection is performed in one span, so that the PDCCH blind detection is prevented from being performed without limitation.

(5) Carrier aggregation (Carrier Aggregation, CA), which is a key technology in LTE-Advanced systems, acquires a larger transmission bandwidth through multiple continuous or discontinuous component carrier aggregation, thereby acquiring a higher peak rate and throughput.

The 5G NR design can enable the service of different models to realize effective multiplexing under three scenes, wherein the three scenes are enhanced mobile broadband (Enhanced Mobile Broadband, eMBB), ultra-high reliability and low-delay Communication (Ultra-Reliable & LowLatency Communication, URLLC) and massive Internet of things Communication (MASSIVE MACHINE TYPE Communication, mMTC), and mMTC service can also be MIoT service, and URLLC service has higher requirements on time ductility and reliability and PDCCH monitoring capability than eMBB service, mMTC service and the like.

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

The data transmission method provided by the embodiment of the disclosure can be applied to the application scene of transmitting the service data corresponding to the service request to the UE, in particular to the application scene of transmitting the service data corresponding to a plurality of service requests of different service types to the UE. For example, a user initiates multiple service requests simultaneously using the same UE, which may be eMBB or URLLC services. The base station can send the service data corresponding to the service request to the UE through the carrier channel.

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, namely, the R16 protocol defines the PDCCH monitoring capability based on the time window, and a plurality of time windows are included in one time slot, so that the PDCCH monitoring capability is increased, the timeliness of the system is reduced well, and the reliability of the system is improved.

Because the requirements of users on the PDCCH monitoring capability of different service types of one user are different, the UE needs to configure corresponding blind detection capability aiming at different service types, but the complexity of the UE is necessarily increased in the process, so that the problem that the PDCCH monitoring capability based on time slots and the PDCCH monitoring capability based on the monitoring range coexist is not solved in practical application. For example URLLC services are suitable for mobile devices, industrial control, unmanned, telemedicine etc. fields, which require lower network timeliness and high reliability. Therefore, URLLC traffic is applicable to PDCCH monitoring capability based on the monitoring range. However, eMBB service and mMTC service have relatively low requirements on time ductility, so that the services such as eMBB service and mMTC service are suitable for the PDCCH monitoring capability based on time slots.

The PDCCH monitoring capability of the multi-type service will be described in detail with reference to fig. 1 and 2.

Fig. 1 schematically illustrates a schematic diagram of a slot-based PDCCH monitoring capability according to an exemplary embodiment of the present disclosure. Referring to fig. 1, fig. 1 is a timeslot-based PDCCH monitoring capability defined in the R15 protocol, M1 is the maximum number of PDCCH candidates within one timeslot, i.e., the maximum number of PDCCH candidates that a user terminal can blindly detect within a period of time is M1.

Fig. 2 schematically illustrates a schematic diagram of a PDCCH monitoring capability based on a monitoring range according to an exemplary embodiment of the present disclosure. Referring to fig. 2, fig. 2 is a PDCCH monitoring capability defined in the R16 protocol based on monitoring ranges, each monitoring range corresponds to a monitoring time window, and a time slot includes a plurality of monitoring ranges, where M2 is the maximum number of PDCCH candidates for each monitoring range. In order to consider flexible scheduling requirements and terminal complexity of URLLC services, the total blind detection capability of the PDCCH monitoring capability based on the monitoring range in one time slot is about twice as high as that of the PDCCH monitoring capability based on the time slot, and the increase of the blind detection capability can reduce the timeliness and improve the reliability of the system.

In view of the foregoing, exemplary embodiments of the present disclosure provide a data transmission method, where, when a base station receives a target service request, a target carrier channel corresponding to the target service request is queried from a pre-configured carrier channel list without configuring different blind detection capabilities by a UE to report to the base station, so that service data corresponding to the target service request is sent to the UE through the target carrier channel, and the UE can directly process the received data. Therefore, the differential requirements of different service types on the PDCCH detection capability are realized, and the complexity of the user terminal is greatly reduced.

Fig. 3 is a block diagram of a data transmission system according to an embodiment of the present disclosure, and as shown in fig. 3, the system includes a base station 30 and a UE 32. The UE 32 may send a target service request to the base station 30 through a carrier channel, where a service corresponding to one service type in one service request, for example, eMBB services, URLLC services, or other service types. After receiving the target service request, the base station 30 queries a target carrier channel corresponding to the target service request from a pre-configured carrier channel list, so as to transmit service data corresponding to the target service request to the UE 32 through the target carrier channel.

It should be understood that the number of base stations 30 and UEs 32 in the system architecture shown in fig. 3 is merely exemplary, and that a greater or lesser number is within the scope of the present application. Also, in the example operational scenario described above, the UE 32 may be, for example, a Personal computer, a server, a Personal computer (Personal DIGITAL ASSISTANT, PDA), a notebook, or any other computing device having networking functionality.

Having knowledge of the system architecture of the present disclosure, a scheme of the data transmission method of the present disclosure will be described in detail with reference to fig. 4.

Fig. 4 is a flowchart of a data transmission method according to an embodiment of the present disclosure, where the method may be performed by any device that performs the data transmission method, and the device may be implemented by software and/or hardware. In this embodiment, the apparatus may be integrated in the base station 30 as shown in fig. 3. As shown in fig. 4, the data transmission method provided by the embodiment of the present disclosure may include the following steps:

s40, receiving a service request sent by the user terminal.

In an exemplary embodiment of the present disclosure, the UE transmits a service request to the base station through an established protocol data unit (Protocol Data Unit, PDU) session. Meanwhile, when the UE establishes the PDU session, a carrier channel for transmitting service requests between the terminal and the base station is established.

S42, inquiring a target carrier channel corresponding to the target service request from a preset carrier channel list.

Specifically, the preconfigured carrier channel list includes carrier channels corresponding to multiple carriers with different frequencies, and the corresponding relation between different service types and carrier channels with different frequencies, namely, the service type-carrier channel is preconfigured. Taking URLLC service and eMBB service as an example, a developer may pre-configure a carrier with frequency f ₁ corresponding to eMBB service, and a carrier with frequency f ₂ corresponding to URLLC service, when the base station determines that the received service request is eMBB service, the base station determines a carrier channel corresponding to the carrier with frequency f ₁ as a target carrier channel, and similarly, determines a carrier channel corresponding to the carrier with frequency f ₂ as a target carrier channel of URLLC service.

According to some embodiments of the present disclosure, before a target carrier channel corresponding to a target service request is queried from a pre-configured carrier channel list, each service type corresponding to each service request is determined, a carrier channel corresponding to each service type is determined according to the number of time domain resources corresponding to each service type, and a carrier channel list is constructed based on the service type and the corresponding carrier channel.

The service type is the type of the service corresponding to the service request, for example, URLLC service with high requirements on time ductility and reliability, eMBB service, mMTC service or other services with low requirements on time ductility and reliability, and the like. The number of time domain resources is the PDCCH monitoring capability, i.e. the maximum number of CCEs and the maximum number of PDCCH candidates involved.

Specifically, the UE may concurrently send multiple service requests, where each service request may carry a different service type, and the service types may be services of different models in the three 5G scenarios, and other service types, that is, URLLC tasks, eMBB tasks, mMTC services, and other service types. And determining a carrier channel corresponding to the service type according to the PDCCH monitoring capability required by the service type, wherein the carrier channel is configured with the PDCCH monitoring capability identical to the PDCCH monitoring capability required by the service type, so that the service type and the determined carrier channel are constructed into a corresponding relation, and the corresponding relation is added in a carrier channel list.

The following will take the service request containing URLLC tasks, eMBB tasks and different carrier channels as examples, and take different maximum candidate numbers of PDCCHs as examples.

When the base station determines that the service type corresponding to the service request is URLLC services, because URLLC services are applicable to PDCCH monitoring capability based on the monitoring range, according to the blind detection capability expected to be used by URLLC services in each monitoring time window, a carrier channel matched with the blind detection capability expected to be used can be determined as a target carrier channel, and a carrier channel list between URLLC services and the carrier channel can be obtained.

When the base station determines that the service type corresponding to the service request is eMBB services, eMBB services are applicable to PDCCH monitoring capability based on time slots, and a carrier channel matched with the blind detection capability is determined as a target carrier channel according to the blind detection capability expected to be used in each time slot, so that a carrier channel list between eMBB services and the carrier channel is obtained.

The carrier channels corresponding to the service types are determined according to the number of time domain resources corresponding to the service types, so that the differentiated requirements of different service types on PDCCH monitoring capability can be realized, and the situation that URLLC service and other service types are multiplexed by the same UE is realized under the condition that the complexity of the UE is not increased.

The R16 protocol, based on the R15 protocol, not only enhances the PDCCH monitoring capability, but also includes other capability enhancements, such as DCI, multiple input multiple output enhancement, etc. Hereinafter, DCI will be described as an example.

In another exemplary embodiment of the present disclosure, before a target carrier channel corresponding to a target service request is queried from a pre-configured carrier channel list, each service type corresponding to each service request is determined, a carrier channel corresponding to a service type is determined according to DCI corresponding to each service type, and a carrier channel list of each service type and the corresponding carrier channel is obtained.

Wherein, the size of the DCI can be reduced by compressing DCI information or by indicating domain information in default DCI.

Specifically, when the UE simultaneously transmits multiple service requests, the base station may determine a service type corresponding to each service request, for example, URLLC service, eMBB service, and others. Since URLLC service requires communication process with ultra-low time delay, the size of DCI information needs to be reduced, while eMBB service and other service types do not need to reduce the size of DCI information, so that the carrier channel matched with the DCI information can be determined according to the requirement of the service type on the DCI information, and a carrier channel list of the service type-DCI information size is established.

The service request includes URLLC tasks, eMBB tasks and different carrier channels, and DCI information amounts with different sizes are taken as examples.

When the base station determines that the service type corresponding to the service request is URLLC services, since the URLLC services are applicable to the services with smaller DCI information, the carrier channel with smaller DCI information is used as the first target carrier channel of the URLLC services, for example, the carrier channel with the indication field in the DCI compression or the default DCI is used as the first target carrier channel, so as to construct a carrier channel list of URLLC services-the first target carrier channel.

When the base station determines that the service type corresponding to the service request is eMBB services, since the eMBB services are suitable for the services with large DCI information, the carrier channel with large DCI information is configured as the second target carrier channel of the eMBB services, for example, the carrier channel without DCI compression or the indication field in the default DCI is used as the second target carrier channel, so as to construct a carrier channel list of eMBB services-the second target carrier channel.

And constructing carrier channel lists according to different requirements of different service types on DCI information, so that the base station distributes the corresponding service types to a target carrier channel matched with the corresponding service types for transmitting service data. Therefore, the differential requirements of different service types on the DCI information size are solved, and further, the situation that the UE is configured with different DCI information sizes to report to the base station for service data transmission is avoided, so that the complexity of UR is reduced.

On the basis of the embodiment, the transmission bandwidth between the base station and the user terminal is increased under the condition that the carrier channels are in CA, and the PDCCH monitoring capability used for different service types can coexist and mutually independent for the same UE or the DCI information used for different service types can coexist and mutually independent for the same UE.

S44, service data corresponding to the target service request is sent to the user terminal through the target carrier channel.

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.

The above exemplary embodiments are all that there is a target carrier channel corresponding to a target service request in a pre-configured carrier channel list, and if 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 needs to construct the target carrier channel to transmit service data corresponding to the target service request to the UE.

In an exemplary embodiment of the disclosure, if a target carrier channel corresponding to a target service request does not exist in a carrier channel list, determining a target service type corresponding to the target service request, determining target channel parameters of the target carrier channel according to the number of target 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 according to the target channel parameters.

The target channel parameter is parameter information of a target carrier channel, and may include a carrier of a frequency corresponding to a target service type, and a target time domain resource number required by the target service type, that is, PDCCH monitoring capability.

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 the target carrier channel for transmitting service data corresponding to the target service type.

Taking the service with the target service type URLLC 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 may allocate URLLC service to a carrier channel corresponding to URLLC service at a medium access control (Medium Access Control, MAC) layer and send the service to the UE.

Then, when the pre-configured carrier channel list does not have the target carrier channel corresponding to URLLC services, the base station issues radio resource control (Radio Resource Control, RRC) signaling to the UE, so as to establish RRC connection between the base station and the UE, and allocate corresponding carrier resources to determine a carrier with frequency f pre-configured by URLLC services.

Finally, according to the number of target time domain resources required by URLLC services, namely the maximum number of PDCCH candidates, it can be determined that when a target carrier channel is constructed according to carriers with frequency f, PDCCH monitoring capability corresponding to URLLC services needs to be configured at the same time, so that a target carrier channel corresponding to URLLC services is formed.

By constructing a target carrier channel corresponding to a target service type to transmit service data corresponding to the target service type, the carrier channel can be constructed according to different requirements of the service type on the PDCCH monitoring capability, so that the differential requirements of different service types on the PDCCH monitoring capability are solved, and the problem of complexity increase of the UE caused by configuring a plurality of PDCCH monitoring capabilities on the UE is further avoided.

In an exemplary embodiment of the present disclosure, the number of time domain resources of a target carrier channel corresponding to URLLC traffic is greater than the number of time domain resources of the target carrier channel corresponding to other traffic identities, which are traffic identities other than the target traffic identity.

Wherein, the other service identifier may be a generic term of all service identifiers except the target service identifier. Other service types may be determined by other service identities, which may be eMBB services, MIoT services, etc.

The URLLC service has higher requirement on the monitoring capability of the PDCCH, and the number of time domain resources of the corresponding target carrier channel is larger than that of other service types, namely, in one time slot resource, the number of the maximum candidate PDCCHs configured by the URLLC service corresponding to the target carrier channel is larger than that of the maximum candidate PDCCHs configured by the carrier channels corresponding to the other service types. In an exemplary embodiment of the present disclosure, the subcarrier spacing of the target carrier channel corresponding to URLLC traffic is larger, and the bandwidth width corresponding to the frequency domain resource is larger. For example, the type of traffic being transmitted may be determined according to the subcarrier spacing of each carrier channel configuration, e.g., a carrier channel with a larger subcarrier spacing may be determined as the target carrier channel for transmitting URLLC traffic.

In the above embodiment, compared with other service types such as eMBB service, the target carrier channel corresponding to URLLC service has stronger PDCCH monitoring capability configured by the carrier channel, and improves the transmission performance of the carrier channel, so as to more adapt to the high requirements of the URLLC service on time ductility and reliability.

In practical application, the base station receives a plurality of target service requests sent by the UE simultaneously, so the base station can determine whether the target service type corresponding to each target service request is URLLC services, thereby querying a target carrier channel corresponding to the target service type, and transmitting service data corresponding to URLLC services through the target carrier channel.

Next, taking the service types URLLC and eMBB as examples, a process of determining the target service type corresponding to the target service request by the base station will be described in detail with reference to fig. 5.

Fig. 5 schematically illustrates 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. Referring to fig. 5, in step S500, it is determined whether a network slice is set in the network.

For a 5G wireless network, network slicing is mainly embodied in admission control, network selection, and resource separation. If the network slice is configured in the network, the base station preferentially loads the received target service request in the network slice configured in the network. One network slice may contain 1 or more PDU sessions, i.e. one network slice may contain 1 or more service requests, and one PDU session is not configurable across network slices, so one service request corresponds to one network slice.

In an exemplary embodiment of the present disclosure, in step S502, a base station parses a target service request to obtain a plurality of network slices corresponding to the target service request.

For example, the base station may determine, after receiving the plurality of target service requests, a network slice in which each target service request is located according to an identifier of each target service request.

After determining the plurality of network slices in which each target service request is located, step S504 may be executed to determine the service type corresponding to the target service request according to the slice identifiers of the plurality of network slices.

Specifically, a PDU session includes a network slice identifier S-NSSAI of the network slice, where the format of S-NSSAI is shown in table 1:

TABLE 1

SST

SD

As can be seen from table 1, the network Slice identifier S-NSSAI includes a (Slice/SERVICE TYPE, SST) for indicating a network Slice or service type and a (Slice Differentiator, SD) for indicating a network Slice differentiation.

The values of SST are classified into standardized and non-standardized, and the values of SST standardized in the prior art are eMBB, URLLC, MIoT and wireless communication technology for vehicles (Vehicle to Everything, V2X) respectively as shown in table 2. Non-standardized values may be defined by the operator from self-deployed network slices.

TABLE 2

Network slice or service type	SST value	Chinese name
			eMBB	1	Enhancing mobile broadband
URLLC	2	Ultra-high reliability and low latency communication
			MIoT	3	Mass internet of things communication
V2X	4	Wireless communication technology for vehicle

Wherein the value of SST is used to distinguish the scene type of the network slice application, SD is to distinguish different network slices more carefully at the SST level. For example, when the SST is 4, the scene type of the network slice application is identified as V2X, and the SD value can be used to distinguish different vehicle enterprises.

When determining the service type corresponding to the target service request according to the slice identifiers of the plurality of network slices in step S504, the SST value in the slice identifier S-NSSAI corresponding to the target service request may be obtained, so that the service type of the target service request is determined according to the SST value.

After determining the service type of the target service request, step S506 may be executed to transmit service data corresponding to URLLC services and eMBB services through the query or the established target carrier channel, respectively.

In the process, the service type corresponding to the target service request is determined through the slice identifier of the network slice, so that the base station can quickly determine the service type according to the slice identifier, and therefore, different service types transmit service data through the corresponding target carrier channel, and the differential requirement of different service types on the PDCCH monitoring capability is solved.

In another exemplary embodiment of the present disclosure, if no network slice is set in the network, step S508 is performed to parse the target service request to obtain a plurality of QoS flows corresponding to the target service request. I.e., quality of service (Quality of Service, qoS) flows, the base station may determine the QoS flows in the PDU session based on the identity of the target service request.

After obtaining a plurality of QoS flows, in step S510, it is determined whether the service identifier of the QoS flow is the target service identifier.

Specifically, in a 5G system, a QoS flow is identified by a QoS flow identifier (QoS Flow Identifier, QFI), and the QFI may be dynamically allocated, or may be equal to the QoS flow identifier ((5G QoS Identifier,5QI) of 5G.

The base station may map the packets received for each QoS flow into DRBs, i.e., the base station may map one or more QoS flows into one DRB, and the base station may discriminate URLLC traffic from QFI.

If the service identifier is the identifier corresponding to the service URLLC, step S512 is executed to determine that the service type corresponding to the service request is URLLC service. Otherwise, step S514 is executed to determine that the service type corresponding to the target service request is eMBB services.

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

It should be noted that although the steps of the methods in the present disclosure are depicted in the accompanying drawings in a particular order, this does not require or imply that the steps must be performed in that particular order, or that all illustrated steps be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step to perform, and/or one step decomposed into multiple steps to perform, etc.

The following describes in detail the procedure of using different carrier channels to perform the service data transmission corresponding to different service requests respectively, with reference to fig. 6.

In step S601, a target service request sent by a UE is received based on a first carrier channel. The UE may initiate a PDU session request, where, with respect to the base station, the UE sends a target service request through the established first carrier channel, where the PDCCH monitoring capability of the first carrier channel corresponds to the timeslot-based PDCCH monitoring capability in the R15 protocol, and is applicable to eMBB services. The number of the target service requests sent by the UE may be one or more, and the number of the corresponding service types may be one or more, and in the following, the description will be given by taking the case that the target service requests sent by the UE include URLLC services and eMBB services at the same time.

In step S603, according to some embodiments of the present disclosure, whether a network slice is set in the network. If a network slice is set in the network, step S605 is performed to determine the slice identity of each network slice. The base station may obtain the slice identifier of each network slice, so that the service type may be determined by using the slice identifier S-NSSAI of the network slice, and specifically, the network slice corresponding to the URLLC service may be determined according to the SST value in the slice identifier.

Step S607 is performed to determine whether it is URLLC service network slices. If so, step S613 is performed for all URLLC traffic network slices, querying or constructing a second carrier channel to transmit URLLC traffic based on the second carrier channel in the presence of the second carrier channel. If it is not URLLC traffic network slice, step S615 is performed to transmit eMBB traffic based on the first carrier channel.

According to some embodiments of the present disclosure, if no network slice is set in the network, step S609 is performed to determine the QFI corresponding to the QoS flow. The base station may determine the traffic type corresponding to each QoS flow through the QFI corresponding to each QoS flow.

Then, step S611 is executed to determine whether the QoS flow corresponds to URLLC traffic. The base station determines URLLC traffic according to QFI, and if the QoS flow is URLLC traffic, then step S613 is executed to query or construct a second carrier channel, so as to transmit URLLC traffic based on the second carrier channel in the presence of the second carrier channel. If it is not the QoS flow of URLLC traffic, step S615 is performed to transmit eMBB traffic based on the first carrier channel. The PDCCH monitoring capability of the second carrier path configuration is higher than the PDCCH monitoring capability of the first carrier path configuration, or the second carrier path is configured with an indication field in DCI compression or default DCI to reduce the DCI size, etc., while the first carrier path does not perform DCI compression or indication field in the default DCI to reduce the DCI size, etc.

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

Fig. 7 schematically illustrates a block diagram of a data transmission device according to an exemplary embodiment of the present disclosure. The data transmission device 7 includes a service receiving module 70, a channel inquiring module 72, and a data transmitting module 74.

The service receiving module 70 may be configured to receive a target service request sent by a user terminal, the channel querying module 72 may be configured to query a pre-configured carrier channel list for a target carrier channel corresponding to the target service request, and the data sending module 74 may be configured to send service data corresponding to the target service request to the user terminal based on the target carrier channel.

The data transmission device 7 provided in the embodiments of the present disclosure may execute the technical scheme of the data transmission method in any of the embodiments, and the implementation principle and beneficial effects of the data transmission method are similar to those of the data transmission method, and reference may be made to the implementation principle and beneficial effects of the data transmission method, which are not described herein.

Further, another data transmission device is provided in one embodiment of the present disclosure.

Fig. 8 schematically illustrates a block diagram of another data transmission apparatus of an exemplary embodiment of the present disclosure. The data transmission device 8 includes an information determining module 80 and a channel constructing module 82.

In an exemplary embodiment of the present disclosure, the data transmission apparatus includes an information determining module 80 that may be configured to determine a 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 determining module 80 that may be configured to determine a target channel parameter of the target carrier channel according to a target time domain resource number corresponding to the target service type, and a channel constructing module 82 that may be configured to construct the target carrier channel for transmitting service data corresponding to the target service type according to the target channel parameter.

In an exemplary embodiment of the present disclosure, the information determining module 80 may be configured to parse the target service request to obtain a plurality of network slices corresponding to the target service request, and determine a service type corresponding to the target service request according to slice identifiers of the plurality of network slices.

In an exemplary embodiment of the present disclosure, the information determining module 80 may be configured to parse the target service request to obtain a plurality of service quality flows corresponding to the target service request, and determine that the service type corresponding to the target service request is an ultra-high reliable and low-latency communication service if the service identifier of the service quality flow is the target service identifier.

In an exemplary embodiment of the present disclosure, the number of time domain resources of a target carrier channel corresponding to an ultra-high reliability communication service with low latency is greater than the number of time domain resources of carrier channels corresponding to other service identifications, which are service identifications other than the target service identification.

In an exemplary embodiment of the present disclosure, the information determining module 80 may be configured to determine each service type corresponding to each service request, the information determining module 80 may be configured to determine a carrier channel corresponding to each service type according to the number of time domain resources corresponding to each service type, and the channel construction module 82 may be configured to construct a carrier channel list based on the service type and the corresponding carrier channel.

In an exemplary embodiment of the present disclosure, the information determining module 80 may be configured to determine each service type corresponding to each service request, and the information determining module 80 may be configured to determine a carrier channel corresponding to each service type according to downlink control information corresponding to each service type, so as to obtain a carrier channel list of each service type and a corresponding carrier channel.

The data transmission device 8 provided in the embodiments of the present disclosure may execute the technical scheme of the data transmission method in any of the embodiments, and the implementation principle and beneficial effects of the data transmission method are similar to those of the data transmission method, and reference may be made to the implementation principle and beneficial effects of the data transmission method, which are not described herein.

In an exemplary embodiment of the present disclosure, a computer-readable storage medium having stored thereon a program product capable of implementing the method described above in the present specification is also provided. In some possible embodiments, the various aspects of the invention may also be implemented in the form of a program product comprising program code for causing a user terminal to carry out the steps according to the various exemplary embodiments of the invention as described in the "exemplary methods" section of this specification, when the program product is run on the user terminal.

A program product for implementing the above-described method according to an embodiment of the present invention may employ a portable compact disc 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 that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

The program product may employ 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 can be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of a readable storage medium include an electrical connection having 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

The computer readable signal medium may include a data signal propagated in baseband or as part of a carrier wave with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Program code for carrying out operations of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind 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., connected via the Internet using an Internet service provider).

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

Those skilled in the art will appreciate that the various aspects of the invention may be implemented as a system, method, or program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, micro-code, etc.) or an embodiment combining hardware and software aspects that may be referred to herein collectively as a "circuit," module "or" system.

An electronic device 900 according to such an embodiment of the invention is described below with reference to fig. 9. The electronic device 900 shown in fig. 9 is merely an example, and should not be construed as limiting the functionality and scope of use of embodiments of the present invention.

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

Wherein the storage unit stores program code that is executable by the processing unit 910 such that the processing unit 910 performs steps according to various exemplary embodiments of the present invention described in the above-described "exemplary methods" section of the present specification. For example, the processing unit 910 may perform steps S40 to S44 as shown in fig. 4.

The storage unit 920 may include readable media in the form of volatile storage units, such as Random Access Memory (RAM) 9201 and/or cache memory 9202, and may further include Read Only Memory (ROM) 9203.

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 or some combination of which may include an implementation of a network environment.

The bus 930 may be 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.

The electronic device 900 may also communicate with one or more external devices 1000 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device 900, and/or with any device (e.g., router, modem, etc.) that enables the electronic device 900 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 950. Also, electronic device 900 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet, through network adapter 960. As shown, the network adapter 960 communicates with other modules of the electronic device 900 over the bus 930. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 900, including, but not limited to, microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.

From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware. Thus, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.) or on a network, including several instructions to cause a computing device (may be a personal computer, a server, a terminal device, or a network device, etc.) to perform the method according to the embodiments of the present disclosure.

Furthermore, the above-described drawings are only schematic illustrations of processes included in the method according to the exemplary embodiment of the present invention, and are not intended to be limiting. It will be readily appreciated that the processes shown in the above figures do not indicate or limit the temporal order of these processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, for example, among a plurality of modules.

It should be noted that although in the above detailed description several modules or units of a device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit in accordance with embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any adaptations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected 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, comprising:

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 comprises:

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 comprises:

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 is 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 comprises:

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, comprising:

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, wherein 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, comprising:

Processor; and

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.