Channel access process based on channel access priority class

Abstract

Embodiments of the present disclosure relate to devices, methods, apparatuses, and computer-readable storage media for a channel access process based on a channel access priority category (CAPC). The method includes: receiving scheduling information from a second device, the scheduling information indicating at least: resources allocated for transmission from a first device to a second device, a channel access type for transmission, and an expected access priority for transmission. The method also includes: comparing the expected access priority with the access priority of data in a buffer of the first device; and determining the use of resources based on the comparison. In this way, channel occupancy time (COT) sharing can be used only for data with higher or equal priority to avoid unintended use of authorization on an unlicensed band, and coexistence fairness between nodes with different types of services to be transmitted can be achieved.

Description

Technical Field

[0001] Embodiments of the present disclosure relate generally to the field of telecommunications, and in particular to devices, methods, apparatuses, and computer-readable storage media for a channel access procedure based on a channel access priority class (CAPC). Background Art

[0002] Two types of uplink channel access procedures for listen-before-talk (LBT) have been defined in 3GPP for LTE unlicensed band operation. In LBT Type 1, the channel access procedure uses an exponential backoff with parameters that depend on the CAPC of the LCH within the TB. In LBT Type 2, the channel access procedure has a fixed duration for channel sensing. Type 2 channel access procedures can only be applied within the shared channel occupation time (COT).

[0003] In order to facilitate the correct selection of uplink data, the network device can indicate the value of the CAPC in the UL grant to the terminal device when performing the LBT process and initiating COT. The channel access (CA) type (i.e., LBT type) and the value of the CAPC for the terminal device are explicitly signaled using the downlink control information (DCI) in the uplink grant and carried on the physical downlink control channel (PDCCH). Summary of the invention

[0004] Generally speaking, example embodiments of the present disclosure provide a solution for a CAPC-based channel access procedure.

[0005] In a first aspect, a first device is provided. The first device includes: at least one processor; and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to, together with the at least one processor, cause the first device to at least: receive scheduling information from a second device, the scheduling information at least indicating: resources allocated for transmission from the first device to the second device, a channel access type for transmission, and an expected access priority for transmission. The first device is also caused to perform the following operations: compare the expected access priority with the access priority of data in a buffer of the first device; and determine the use of resources based on the comparison.

[0006] In a second aspect, a method is provided. The method includes: receiving scheduling information from a second device, the scheduling information indicating at least: resources allocated for transmission from a first device to a second device, a channel access type for the transmission, and an expected access priority for the transmission. The method also includes: comparing the expected access priority with the access priority of data in a buffer of the first device; and determining the use of resources based on the comparison.

[0007] In a third aspect, an apparatus is provided, comprising: a component for receiving scheduling information from a second device, the scheduling information indicating at least: resources allocated for transmission from a first device to a second device, a channel access type for transmission, and an expected access priority for transmission; a component for comparing the expected access priority with the access priority of data in a buffer of the first device; and a component for determining the use of resources based on the comparison.

[0008] In a fourth aspect, there is provided a computer readable medium having stored thereon a computer program which, when executed by at least one processor of a device, causes the device to perform the method according to the second aspect.

[0009] Other features and advantages of the embodiments of the present disclosure will also be apparent from the following description of the specific embodiments when read in conjunction with the accompanying drawings, which illustrate, by way of example, the principles of the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Embodiments of the present disclosure are presented in an exemplary sense and their advantages are explained in more detail below with reference to the accompanying drawings, in which

[0011] Figure 1 shows an example communication network in which example embodiments of the present disclosure may be implemented;

[0012] Figure 2 A flow chart illustrating an example method 200 of a CAPC-based channel access procedure according to some example embodiments of the present disclosure;

[0013] Figure 3 A flow chart illustrating an example method 300 of a CAPC-based channel access procedure according to some example embodiments of the present disclosure;

[0014] Figures 4 to 6 A diagram illustrating an example LBT process according to some example embodiments of the present disclosure;

[0015] Figure 7 shows a simplified block diagram of a device suitable for implementing an example embodiment of the present disclosure; and

[0016] Figure 8 A block diagram of an example computer-readable medium is shown in accordance with some embodiments of the present disclosure.

[0017] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION

[0018] The subject matter described herein will now be discussed with reference to several example embodiments. It should be understood that these embodiments are discussed only to enable those skilled in the art to better understand and thus implement the subject matter described herein, and do not imply any limitation on the scope of the subject matter.

[0019] The terms used herein are used only to describe specific embodiments and are not intended to limit the exemplary embodiments. As used herein, the singular forms "a", "an", and "the" are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the terms "comprises / comprising" and / or "includes / including" when used herein refer to the presence of specified features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or their groups.

[0020] It should also be noted that in some alternative implementations, the functions / actions mentioned may not be performed in the order mentioned in the figures. For example, in fact, two functions or actions shown in succession may be performed simultaneously, or these functions or actions may sometimes be performed in reverse order, depending on the functionality / actions involved.

[0021] As used herein, the term "communication network" refers to a network that complies with any suitable communication standard, such as Long Term Evolution (LTE), LTE Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed ​​Packet Access (HSPA), New Radio (NR), etc. In addition, communication between a terminal device and a network device in the communication network may be performed according to any suitable generation of communication protocols, including but not limited to first generation (1G) communication protocols, second generation (2G) communication protocols, 2.5G communication protocols, 2.75G communication protocols, third generation (3G) communication protocols, fourth generation (4G) communication protocols, 4.5G communication protocols, future fifth generation (5G) communication protocols and / or any other protocols currently known or to be developed in the future.

[0022] The embodiments of the present disclosure can be applied in various communication systems. In view of the rapid development of communications, of course, there will be future types of communication technologies and systems that can implement the present disclosure. It should not be considered that the scope of the present disclosure is limited to the aforementioned systems. For the purpose of illustration, the embodiments of the present disclosure will be described with reference to the 5G communication system.

[0023] The term "network device" as used herein includes, but is not limited to, a base station (BS), a gateway, a registration management entity, and other suitable equipment in a communication system. The term "base station" or "BS" means a Node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), a new radio (NR) NB (also referred to as a gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, a low power node such as a femto, a pico, etc.

[0024] The term "terminal device" used herein includes but is not limited to "user equipment (UE)" and other suitable terminal devices capable of communicating with network devices. As an example, "terminal device" may refer to a terminal, a mobile terminal (MT), a subscriber station (SS), a portable subscriber station, a mobile station (MS) or an access terminal (AT).

[0025] As used herein, the term "circuitry" may refer to one or more or all of the following:

[0026] (a) pure hardware circuit implementation (such as implementation in pure analog and / or digital circuitry) and

[0027] (b) a combination of hardware circuitry and software such as (where applicable):

[0028] (i) Combination of analog and / or digital hardware circuit(s) with:

[0029] Software / Firmware and

[0030] (ii) any portion of hardware processor(s) and software (including digital signal processor(s), software and memory(s) that work together to enable a device (such as a mobile phone or server) to perform various functions, and

[0031] (c) Hardware circuits and / or processors, such as microprocessor(s) or portions of microprocessor(s), that require software (e.g., firmware) to operate, but the software may not be present when the software is not required to operate.

[0032] This definition of circuitry applies to all uses of the term in this application, including in any claims. As another example, as used in this application, the term "circuitry" also covers an implementation of only a hardware circuit or processor (or multiple processors), or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term "circuitry" also covers, for example (and if applicable to a particular claim element), a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in a server, a cellular network device, or another computing or network device.

[0033] Figure 1 An example communication network 100 that can be used to implement an embodiment of the present disclosure is shown. The network 100 includes a second device 110 (hereinafter may be referred to as the network device 110) and first devices 120-1 and 120-2 (hereinafter collectively referred to as the first device 120 or individually referred to as the terminal device 120) served by the network device 110. The service area of ​​the network device 110 is referred to as a cell 102. It should be understood that the number of network devices and terminal devices is only for illustrative purposes and does not imply any limitation. The network 100 may include any suitable number of network devices and terminal devices suitable for implementing an embodiment of the present disclosure. Although not shown, it should be understood that one or more terminal devices may be located in the cell 102 and served by the network device 110.

[0034] Communications in network 100 may conform to any suitable standard, including but not limited to New Radio (NR), Long Term Evolution (LTE), LTE Evolution, LTE Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), and Global System for Mobile Communications (GSM), etc. In addition, communications may be performed according to any generation of communication protocols currently known or to be developed in the future. Examples of communication protocols include but are not limited to first generation (1G) communication protocols, second generation (2G) communication protocols, 2.5G communication protocols, 2.75G communication protocols, third generation (3G) communication protocols, fourth generation (4G) communication protocols, 4.5G communication protocols, and fifth generation (5G) communication protocols.

[0035] As mentioned above, two types of uplink channel access procedures for LBT have been defined in 3GPP for LTE unlicensed band operation. In LBT Type 1, the channel access procedure uses an exponential backoff with parameters that depend on the CAPC of the LCH within the TB. The CAPC for uplink (UL) is represented in the table below.

[0036] Table 1: Channel access priority categories for UL

[0037]

[0038] CW min，p It can be called the minimum contention window size, CW max，p It can be called the maximum contention window size, T mcot，p can be called the maximum channel occupancy time, and CW p It can be called the set of allowed contention window sizes.

[0039] In LBT Type 2, the channel access procedure has a fixed duration for channel sensing. The Type 2 channel access procedure can only be applied within the COT.

[0040] The CA type (ie, LBT type) and the value of CAPC for the terminal device are explicitly signaled using downlink DCI in an uplink grant and carried on the PDDCH.

[0041] For example, DCI format 0A is used to schedule the physical uplink shared channel (PUSCH) in a licensed assisted access (LAA) secondary cell (SCell), or to activate / release autonomous UL transmission (AUL), or to indicate AUL downlink feedback information (AUL-DFI) to the terminal device, which AUL downlink feedback information is activated with AUL transmission.

[0042] A similar approach to instructing a terminal device on a channel access procedure may also apply to New Radio Unlicensed (NR-U), with potentially more LBT types defined. More specifically, four channel access (LBT) categories are being discussed in NR-U (category 1 LBT without channel sensing; category 2 LBT with a sensing duration of 16us; category 2 LBT with a sensing duration of 25us; and category 4 LBT with exponential backoff). Category 2 LBT corresponds to LBT type 2, and category 4 LBT corresponds to LBT type 1.

[0043] For UL channel access type 2 with COT sharing, the assumption is that the network device has initiated channel occupation using category 4 LBT, and the UL transmission occurs within the channel occupation time. Under these conditions, the terminal device only needs to perform a shorter LBT (i.e., LBT type 2 as mentioned above), or no LBT or sensing at all (i.e., category 1 LBT). The exact parameterization of the network device category 4 LBT depends on the channel access priority category p, which is shown in the table below.

[0044] Table 2: Channel access priority categories

[0045]

[0046] CW min，p It can be called the minimum contention window size, CWmax，p It can be called the maximum contention window size, T mcot，p can be called the maximum channel occupancy time, and CW p It can be called the set of allowed contention window sizes.

[0047] When using channel occupancy for UL transmission initiated by the network device (i.e., COT sharing), the assumption is that the CAPC value of the uplink channel or data must be the same as or lower than the CAPC value assumed by the network device (lower CAPC values ​​have higher priority). That is, the priority of the uplink data must be the same as or higher than the priority of the downlink data. In order to facilitate the correct selection of uplink data, the network device can indicate to the UE the value of the CAPC in the uplink grant when performing Class 4LBT and initiating COT.

[0048] For example, it has been agreed that if a network device indicates a Type 2 channel access procedure for a terminal device in a DCI, then the network device indicates in the DCI the channel access priority class used to obtain access to the channel.

[0049] However, there is no such restriction on the data of logical channels that can include CAPC in uplink transmission in the LCP (Logical Channel Priority) process in the terminal device. Even if it is stated in the specification that CAPC is indicated for type 2, the indicated CAPC in the DCI will not be considered at all. This is left to the network equipment to ensure that it gives the correct authorization based on the downlink business, the latest buffer status report (BSR) received from the terminal device and the received UL business. But the BSR has a coarse granularity and is reported by logical channel group (LCG), and does not always contain the latest information for all LCHs with data available for transmission. For example, the network can group LCHs with similar LCP priorities, and such LCHs can still have different CAPCs. It may happen that the terminal device does not have data with a higher or equal priority than the CAPC indicated in the DCI. In this case, the data multiplexed into the allocated UL resources may not meet the CAPC restrictions indicated for the authorization / COT, which will have a negative impact on fairness.

[0050] Therefore, according to an embodiment of the present disclosure, a method for accessing a channel based on CAPC is proposed. A terminal device may obtain data priority expected for uplink transmission from a DCI transmitted from a network device, and schedule uplink transmission based on the value of CAPC.

[0051] References below Figure 2 The principles and implementations of the present disclosure are described in detail. Figure 21 is a flow chart showing an example method 200 of a CAPC-based channel access process according to some example embodiments of the present disclosure. The method 200 may be performed in a Figure 1 For discussion purposes, reference will be made to the terminal device 120 shown in FIG. Figure 1 Method 200 is described.

[0052] like Figure 2 As shown in , at 210 , the terminal device 120 receives scheduling information from the network device 110 . The scheduling information used herein may be referred to as DCI, which may be used to schedule uplink transmission, ie, transmission from the terminal device 120 to the network device 110 .

[0053] The scheduling information may include various indications. For example, the scheduling information may include resources in both the time domain and the frequency domain allocated for uplink transmission, information associated with channel access, such as the expected access priority of the channel for uplink transmission, and the channel access type, such as the LBT type.

[0054] The access priority category of the channel used in this document may be referred to as CAPC as mentioned above. Four channel access priority categories are defined in TS36.213, which can be used when uplink and downlink transmissions are performed in an LAA carrier. The table (shown below) shows which channel access priority category should be used by services belonging to different standardizations (QoS class identifiers). Non-standardized QCI (i.e., operator-specific QCI) should use the appropriate channel access priority category based on the following table, i.e., the channel access priority category for non-standardized QCI should be the channel access priority category of the standardized QCI, which best matches the service category of the non-standardized QCI. In the table, lower CAPC values ​​have higher priority.

[0055] Table 3: Mapping between channel access priority classes and QCI

[0056] Channel access priority class (p) QCI 1 1,3,5,65,66,69,70 2 2,7 3 4,6,8,9 4 -

[0057] The scheduling information may also include a time interval for checking channel availability. The process for checking channel availability may refer to an LBT process. As mentioned above, there are 2 types of LBT. The duration of the type 1 LBT process may be based on exponential backoff, which means that the type 1 LBT process may require a longer sensing time. The LBT process in this solution may refer to type 2 LBT, and the duration for checking channel availability / sensing channel occupancy is very short because the type 1 LBT process has been completed at the network device 110.

[0058] Reference Figure 2 At 220, the terminal device 120 compares the expected access priority (the expected access priority is determined according to the scheduling information) with the access priority of the data in the buffer of the terminal device 120. The access priority here may refer to a channel access priority category.

[0059] Each data in the buffer may have an access priority, which may depend on the type of service associated with the data. Only data with an access priority equal to or higher than the expected access priority may be transmitted on a channel with COT sharing. Therefore, the terminal device 120 may determine whether the buffer contains data with an access priority exceeding the expected access priority. That is, if there is no data of equal or higher priority included in a transport block (TB), the access priority of the data to be transmitted on the channel with COT sharing cannot be lower than the expected access priority.

[0060] For the case where the buffer contains data with an access priority exceeding the expected access priority, the terminal device 120 may construct a transport block from the data and transmit a TB with respect to the resources allocated for uplink transmission. However, it may be possible that the access priority of each data in the buffer is lower than the expected access priority. Therefore, at 230, the terminal device 120 determines the use of resources based on the comparison.

[0061] If the access priority of each data in the buffer is lower than the expected access priority, the terminal device 120 can fall back to the type 1 LBT process, which is used to check the channel availability for data with lower access priority, which may require more sensing time. That is, the terminal device 120 can change the channel access type from type 2 LBT to type 1 LBT.

[0062] The duration of the LBT process with exponential backoff may depend on the data with the lowest access priority multiplexed into the TB. This may apply to the case where the terminal device 120 changes the channel access type from type 2 LBT to type 1 LBT as described above and the case where the terminal device 120 is instructed to use type 1 LBT from the scheduling information. Therefore, the time interval scheduled by the network device 110 (which time interval can be regarded as a gap between DL transmission and UL transmission) may be insufficient for the LBT process with exponential backoff.

[0063] If the LBT process with exponential backoff is not completed within the time interval, the time interval for checking channel availability may be extended. However, the extended time interval may overlap with the time domain resources allocated for UL transmission, and the time domain resources allocated for UL transmission may be adjusted. Figure 3, the LBT process performed at the terminal device 120 can be described in detail as follows.

[0064] Figure 3 1 is a flow chart showing an example method 300 of a CAPC-based channel access process according to some example embodiments of the present disclosure. The method 300 may be performed in a Figure 1 For the purpose of discussion, reference will be made to the terminal device 120 shown in FIG. Figure 1 Method 300 is described.

[0065] like Figure 3 As shown in , in 310, the terminal device 120 compares the expected access priority with the access priority of the data in the buffer of the terminal device 120, which is equivalent to action 220 in method 200. The access priority of the data may be the highest priority of the data to be multiplexed in the TB.

[0066] In 320, if the terminal device 120 determines that the access priority of the data in the buffer is lower than the expected access priority, in other words, the data contained in the buffer does not have an access priority that exceeds the expected access priority, then in the case where the indicated channel access type is type 2 LBT, the terminal device 120 may change the channel access type to type 1 LBT in 330. The terminal device 120 may determine a time interval for checking channel availability to transmit the data in the buffer.

[0067] As mentioned above, Type 1 LBT uses exponential backoff and requires more time to sense UL transmissions for data with lower access priority multiplexed into a TB. If the terminal device 120 determines that the LBT process with exponential backoff is not completed within the time interval, the terminal device 120 may extend the time interval for checking channel availability.

[0068] As mentioned above, the time interval of the LBT process scheduled by the network device 110 is not enough for the LBT process to be performed in the terminal device 120, and the time interval of the LBT process can be extended. That is, the time interval of the LBT process can overlap with the time domain resources allocated for uplink transmission. If the terminal device 120 determines that the extended time interval overlaps with the time domain resources used for transmission, the terminal device 120 can adjust the range of the time domain resources used for transmission based on the extended time interval of the LBT process.

[0069] Figures 4 to 6 FIG. 1 is a diagram showing an example LBT process according to some example embodiments of the present disclosure. Figures 4 to 6 , the adjustment of the range of time domain resources used for uplink transmission can be better understood.

[0070] like Figure 4 As shown in FIG, the terminal device 120 receives scheduling information about resources 411 for downlink transmission in time interval 401. The terminal device 120 can determine that resources 412 and 413 for uplink transmission can start at the starting point of time interval 403, and the terminal device 120 can perform uplink transmission in time intervals 403 and 404. Time interval 402 can be used to check channel availability, that is, to perform the LBT process that has been scheduled and indicated in the DCI. It can be seen that the interval is very short and is typically 25 μs.

[0071] In some example embodiments, in order to sense a channel with a longer time, terminal device 120 may postpone the time domain resources allocated for uplink transmission (time intervals 403 and 404). Terminal device 120 may determine the starting point of the time domain resources allocated for uplink transmission based on the scheduling information, and postpone the starting point based on the extended time interval.

[0072] The postponed time period may be preconfigured and may be, for example, a predetermined number of symbols. Figure 5 As shown in FIG. 5 , the terminal device 120 receives scheduling information about resources 511 for downlink transmission in time interval 501. Figure 4 In comparison, resources 512 and 513 for uplink transmission are postponed and the time interval 502 of the LBT process performed at the terminal device 120 is increased.

[0073] In some example embodiments, terminal device 120 may reserve time domain resources allocated for uplink transmission. For this case, terminal device 120 may postpone the starting point of the time domain resources allocated for uplink transmission based on the scheduling information, and reserve a time period for the extended time interval from the starting point of the resources. During the reserved time period, UL transmission is suspended.

[0074] The predetermined time period may be preconfigured and may be, for example, a predetermined number of symbols. Figure 6 As shown in FIG. 5 , the terminal device 120 receives scheduling information about resources 611 for downlink transmission in the time interval 501. Figure 4 In comparison, a portion of the resources 612 used for uplink transmission is reserved for the LBT process, and the time interval 602 of the LBT process performed at the terminal device 120 is increased.

[0075] In some example embodiments, terminal device 120 may reserve a first set of resources among a plurality of contiguous sets of resources allocated for uplink transmission.For example, the entire resources 512 may be used for the LBT process.

[0076] As another option, if the terminal device 120 determines that the access priority of the data in the buffer is lower than the expected access priority, the terminal device 120 may skip uplink transmission on the resource. In other words, the terminal device 120 may not construct a transport block to be transmitted based on the data in the buffer.

[0077] As another option, if terminal device 120 determines that the data priority of the data in the buffer is lower than the access priority, terminal device 120 may generate an indication of the access priority of the data in the buffer and transmit the indication to network device 110 on the resource.

[0078] As another option, if the terminal device 120 determines that the data priority of the data in the buffer is lower than the access priority, the terminal device 120 may transmit a BSR regarding the resources to the network device 110 .

[0079] In some example embodiments, in the event that terminal device 120 does not have data of sufficiently high priority to be transmitted in a COT initiated by shared network device 110, network device 110 may also indicate to terminal device 120 via, for example, RRC signaling, which of the above behaviors terminal device 120 should apply.

[0080] In this way, COT sharing can be used only for data with higher or equal priority to avoid unintended usage of licenses on unlicensed bands, and coexistence fairness between nodes with different types of traffic to transmit can be achieved.

[0081] In some example embodiments, an apparatus that can perform method 200 (eg, implemented at terminal device 120) may include components for performing the corresponding steps of method 200. The components may be implemented in any suitable form. For example, the components may be implemented in a circuit system or a software module.

[0082] In some example embodiments, the apparatus includes: a component for receiving scheduling information from a second device, the scheduling information indicating at least: resources allocated for transmission from a first device to a second device, a channel access type for transmission, and an expected access priority for transmission; a component for comparing the expected access priority with the access priority of data in a buffer of the first device; and a component for determining the use of resources based on the comparison.

[0083] In some example embodiments, the apparatus further comprises means for changing the channel access type to LBT with exponential backoff in response to determining that the channel access type is LBT without exponential backoff and the access priority of the data is lower than the expected access priority.

[0084] In some example embodiments, the component for changing the channel access type includes: a component for determining a time interval for checking channel availability to transmit data in a buffer and a component for extending the time interval for checking channel availability to transmit data in a buffer in response to determining that a process of LBT with exponential backoff is not completed within the time interval.

[0085] In some example embodiments, the apparatus further comprises means for, in response to determining that the extended time interval overlaps the time domain resources for transmission, adjusting the range of the time domain resources for transmission based on the extended time interval.

[0086] In some example embodiments, means for adjusting the time domain resources allocated for transmission includes means for determining a starting point of the time domain resources allocated for transmission based on scheduling information and means for deferring the starting point based on the extended time interval.

[0087] In some example embodiments, the means for adjusting the time domain resources allocated for transmission includes: means for determining a starting point of the time domain resources allocated for transmission based on scheduling information and means for reserving a time period for an extended time interval from the starting point of the resources, wherein transmission is suspended during the reserved time period.

[0088] In some example embodiments, means for determining usage of the resource comprises means for skipping transmission of the resource in response to determining that an access priority of data for transmission is lower than an expected access priority.

[0089] In some example embodiments, the means for determining use of resources includes means for generating an indication of data priority in response to determining that the access priority of data for transmission is lower than the expected access priority; and means for transmitting the indication to the second device on the resources.

[0090] In some example embodiments, means for determining usage of the resource comprises means for transmitting a buffer status report (BSR) on the resource to the second device in response to determining that the access priority of the data for transmission is lower than the expected access priority.

[0091] In some example embodiments, the access priority comprises a channel access priority class.

[0092] Figure 7 700 is a simplified block diagram of a device 700 suitable for implementing an embodiment of the present disclosure. The device 700 may be provided to implement a communication device, such as Figure 1As shown, the device 700 includes one or more processors 710, one or more memories 740 coupled to the processor 710, and one or more transmitters and / or receivers (TX / RX) 740 coupled to the processor 710.

[0093] TX / RX 740 is used for bidirectional communication. TX / RX 740 has at least one antenna to facilitate communication. The communication interface may represent any interface necessary to communicate with other network elements.

[0094] Processor 710 may be of any type suitable for the local technology network and may include one or more of the following: a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture, as non-limiting examples. Device 700 may have multiple processors, such as application specific integrated circuit chips that are time slaved to a clock synchronized with a main processor.

[0095] The memory 720 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 724, electrically programmable read-only memory (EPROM), flash memory, hard disk, compact disk (CD), digital video disk (DVD), and other magnetic storage devices and / or optical storage devices. Examples of volatile memories include, but are not limited to, random access memory (RAM) 722 and other volatile memories that will not persist for the duration of a power outage.

[0096] Computer program 730 includes computer executable instructions executed by associated processor 710. Program 730 may be stored in ROM 1020. Processor 710 may perform any suitable actions and processes by loading program 730 into RAM 720.

[0097] The embodiments of the present disclosure may be implemented with the aid of program 730, so that device 700 may execute the following steps: Figures 2 to 6 Any process of the present disclosure discussed. The embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

[0098] In some embodiments, the program 730 may be tangibly embodied in a computer-readable medium, which may be included in the device 700 (such as included in the memory 720) or in other storage devices accessible to the device 700. The device 700 may load the program 730 from the computer-readable medium to the RAM 722 for execution. The computer-readable medium may include any type of tangible, non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Figure 8 An example of a computer readable medium 800 is shown in the form of a CD or DVD. The computer readable medium has a program 730 stored thereon.

[0099] In general, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are illustrated and described as block diagrams, flow charts, or using some other graphical representations, it should be understood that the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combination thereof as non-limiting examples.

[0100] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer executable instructions, such as computer executable instructions included in program modules, which are executed in a device on a target real or virtual processor to perform the above-referenced Figures 2 to 6 Methods 500 and 600 described. Typically, program modules include routines, programs, libraries, objects, categories, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of program modules can be combined or divided between program modules as needed. The machine executable instructions of program modules can be executed in local or distributed devices. In distributed devices, program modules can be located in both local storage media and remote storage media.

[0101] The program code for carrying out the method of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device so that the program code, when executed by the processor or controller, enables the functions / operations specified in the flow chart and / or block diagram to be implemented. The program code can be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine or entirely on a remote machine or server.

[0102] In the context of the present disclosure, computer program codes or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform various processes and operations as described above. Examples of carriers include signals, computer readable media, etc.

[0103] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or apparatuses or any suitable combination of the foregoing. More specific examples of computer readable storage media would include an electrical connection with one or more wires, a portable computer 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 foregoing.

[0104] Further, although operations are depicted in a particular order, it should not be understood that such operations need to be performed in the particular order shown or in a sequential order, or that all illustrated operations need to be performed to achieve the desired result. In some cases, multitasking and parallel processing can be advantageous. Similarly, although several specific implementation details are included in the above discussion, these implementation details should not be interpreted as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to a particular embodiment. Certain features described in the context of a separate embodiment may also be implemented in a single embodiment in combination. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments individually or in any suitable sub-combination.

[0105] Although the disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A device for communication, comprising: at least one processor; as well as at least one memory including computer program code; The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to at least: receiving scheduling information from a device, the scheduling information indicating at least: time domain resources allocated for transmission from the apparatus to the device, a channel access type for the transmission, and an expected access priority for the transmission, wherein the apparatus is a terminal device and the device is a network device; as well as comparing the expected access priority with access priorities of data in a buffer of the device, wherein the access priority comprises a channel access priority category, wherein each data in the buffer has an access priority, the access priority depending on a service type associated with the data, wherein only data having an access priority equal to or higher than the expected access priority may be transmitted on a channel having channel occupancy time (COT) sharing, and wherein the access priority of data transmitted on a channel having COT sharing cannot be lower than the expected access priority if there is no data of equal or higher priority included in a transmission block; determining usage of the time domain resources based on the comparison; responsive to determining that the channel access type is listen before talk without exponential backoff and the access priority of the data is lower than the expected access priority, changing the channel access type to listen before talk with exponential backoff; The device is configured to change the channel access type by: determining a time interval for checking channel availability to transmit the data in the buffer; as well as In response to determining that the listen-before-talk process with exponential backoff is not completed within the time interval, extending the time interval for checking the channel availability to transmit the data in the buffer; The apparatus is configured to adjust the time domain resources allocated for the transmission by: determining a starting point of the time domain resources allocated for the transmission based on the scheduling information; delaying the starting point based on the extended time interval; as well as A time period for the extended time interval is reserved from the starting point of the time domain resource, wherein the transmission is suspended during the reserved time period.

Images