TW202002559A - Channel access type determination method, terminal device, and network device - Google Patents

Abstract

Disclosed is a channel access type determination method, capable of determining a channel access type of a physical uplink control channel sending a scheduling request. The method comprises: on the basis of a logical channel triggering a scheduling request, a terminal device determining a first channel access type of a physical uplink control channel sending the scheduling request. Further disclosed are another channel access type determination method, a terminal device, a network device, and a storage medium.

Description

Method for determining channel access type, terminal equipment and network equipment

The invention relates to the technical field of wireless communication, in particular to a method for determining a channel access type, terminal equipment and network equipment.

In related technologies, terminal equipment transmitting data on unlicensed spectrum needs to meet some unlicensed spectrum specifications, such as Listen Before Talk (LBT) mechanism; LBT mechanism refers to the terminal equipment or network equipment transmitting data Before the channel needs to be monitored, if the monitored energy is lower than the preset threshold, the terminal device is considered to be able to transmit data on the channel.

When the New Ratio (NR) system uses the stand-alone method to use unlicensed spectrum, the random access channel (Random Access Channel, RACH) process needs to be completed on the unlicensed spectrum. Therefore, RACH needs to target unlicensed spectrum The spectrum requirements are further optimized, and at the same time, access requirements for unlicensed spectrum, such as LBT, must also be met. In addition, when the NR system uses the unlicensed spectrum in a stand-alone manner, the terminal equipment also needs to perform physical upload control channel (Physical Uplink Control Channel, PUCCH) transmission on the unlicensed spectrum; the applicant found in the implementation process, how There is currently no solution to determine the channel access type of the PUCCH for transmission scheduling request (SR).

Embodiments of the present application provide a method for determining a channel access type, which can determine a channel access type of a PUCCH transmitting an SR.

In a first aspect, a method for determining a channel access type is provided, including: a terminal device determining a first channel access type for an entity upload control channel for sending a scheduling request based on a logical channel that triggers a scheduling request.

In a second aspect, a terminal device is provided for executing the method in the above-mentioned first aspect or various implementations thereof.

Specifically, the terminal device includes a functional module for performing the method in the above-mentioned first aspect or various implementations thereof.

In a third aspect, a terminal device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the method in the first aspect or its various implementations.

According to a fourth aspect, a method for determining a channel access type is provided, including: a network device configuring a terminal with a logical channel configuration parameter and/or a scheduling request configuration parameter; the logical channel configuration parameter and the scheduling request Configuration parameter used by the terminal device to determine the channel access type of the entity upload control channel used to send the scheduling request; wherein the configuration parameter of the logical channel and the configuration parameter of the scheduling request both include at least one channel storage Take type.

According to a fifth aspect, there is provided a network device, configured to execute the method in the above fourth aspect or various implementations thereof.

Specifically, the network device includes a functional module for performing the method in the fourth aspect or its implementations.

According to a sixth aspect, a network device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the method in the fourth aspect or the various implementations thereof.

According to a seventh aspect, there is provided a wafer for implementing any one of the above-mentioned first and fourth aspects or the method in each of the implementations thereof.

Specifically, the chip includes: a processor for calling and running a computer program from the memory, so that the device installed with the chip executes any one of the above first and fourth aspects or the respective implementations thereof Methods.

According to an eighth aspect, there is provided a computer-readable storage medium for storing a computer program, which causes the computer to execute the method in any one of the first and fourth aspects or the respective implementations thereof.

According to a ninth aspect, a computer program product is provided, which includes computer program instructions, which cause the computer to execute the method in any one of the first and fourth aspects or the respective implementations thereof.

According to a tenth aspect, there is provided a computer program which, when run on a computer, causes the computer to execute the method in any one of the above first and fourth aspects or the respective implementations thereof.

Through the above technical solution, the terminal device can determine the channel access type of the PUCCH that sends the SR based on the logical channel of the SR.

The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are a part of the embodiments of the present application, but not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art without creative work fall within the protection scope of the present application.

The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, and Broadband Code Division Multiple Access (Wideband Code Division Multiple Access, WCDMA) system, General Packet Radio Service (GPRS), LTE system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (Time Division) Duplex (TDD), Universal Mobile Telecommunication System (UMTS), Global Interoperability for Microwave Access (WiMAX) communication system or 5G system, etc.

Exemplarily, the communication system 100 applied in the embodiment of the present application is shown in FIG. 1. The communication system 100 may include a network device 110, and the network device 110 may be a device that communicates with a terminal device 120 (or referred to as a communication terminal or terminal). The network device 110 can provide communication coverage for a specific geographic area, and can communicate with terminal devices located in the coverage area. Optionally, the network device 110 may be a base transceiver station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, or a node (NodeB, NB) in a WCDMA system, or an LTE system. Evolutionary Node B (eNB or eNodeB), or a wireless controller in the Cloud Radio Access Network (CRAN), or the network equipment can be a mobile switching center, relay station, access Point, vehicle equipment, wearable devices, hubs, switches, bridges, routers, network side devices in 5G networks or network devices in future public land mobile networks (PLMN), etc. .

The communication system 100 also includes at least one terminal device 120 located within the coverage of the network device 110. As used herein, "terminal equipment" includes, but is not limited to, connection via wired lines, such as via Public Switched Telephone Networks (PSTN), Digital Subscriber Line (DSL), digital cables, and direct cable connections Cable; and/or another data connection/network; and/or via a wireless interface, eg, for cellular networks, wireless local area networks (WLAN), digital TV networks such as DVB-H networks Road, satellite network, AM-FM broadcast transmitter; and/or another terminal device configured to receive/transmit communication signals; and/or Internet of Things (IoT) equipment.

Terminal devices configured to communicate through a wireless interface may be referred to as "wireless communication terminals", "wireless terminals", or "mobile terminals". Examples of mobile terminals include but are not limited to satellite or cellular telephones; Personal Communications System (PCS) terminals that can combine cellular radiotelephones with data processing, fax, and data communication capabilities; can include radiotelephones, pagers, and Internet /Intranet access, Web browser, notepad, calendar, and/or PDA of Global Positioning System (GPS) receiver; and conventional laptop and/or palm-type receivers or including radio telephone transceiver Other electronic devices.

Terminal equipment can refer to access terminal, user equipment (User Equipment, UE), user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication Equipment, user agent or user device. The access terminal may be a mobile phone, a wireless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), or a wireless communication function Handheld devices, computing devices, or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks, or terminal devices in future PLMNs, etc.

Optionally, device to device (D2D) communication may be performed between the terminal devices 120.

Alternatively, the 5G system or 5G network may also be referred to as an NR system or NR network.

FIG. 1 exemplarily shows one network device and two terminal devices. Optionally, the communication system 100 may include multiple network devices and each network device may include other numbers of terminal devices within the coverage area. This is not limited in the embodiments of the present application.

Optionally, the communication system 100 may further include other network entities such as a network controller and a mobile management entity, which is not limited in the embodiments of the present application.

It should be understood that the devices with communication functions in the network/system in the embodiments of the present application may be called communication devices. Taking the communication system 100 shown in FIG. 1 as an example, the communication device may include a network device 110 and a terminal device 120 with a communication function, and the network device 110 and the terminal device 120 may be the specific devices described above, which is not described here. It will be described again; the communication device may also include other devices in the communication system 100, such as network controllers, mobile management entities and other network entities, which are not limited in the embodiments of the present application.

It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" in this article is just an association relationship describing related objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A exists alone, A and B exist simultaneously, and B exists alone. three situations. In addition, the character “/” in this article generally indicates that the related objects are a “or” relationship.

Before describing the embodiments of the present invention in detail, a brief introduction to the unlicensed spectrum and NR system is provided.

For unlicensed spectrum, the LTE system supports carrier aggregation (Carrier Aggregation, CA) to use unlicensed spectrum. In the specific implementation, the primary cell (Primary Cell, PCell) works on the licensed spectrum to provide basic access functions and data transmission functions; the secondary cell (Scell) works on the unlicensed spectrum as a data upgrade ( boosting). However, in the LTE system licensed spectrum assisted access (LAC) working mode, RACH is on the PCell, so the RACH function is not optimized for unlicensed spectrum. In the LAA agreement in the related art, PUCCH is also not supported on unlicensed spectrum, that is, SR is transmitted on the licensed spectrum.

The NR system supports the use of unlicensed spectrum in the manner of LAA and the use of unlicensed spectrum in a stand-alone manner.

In the NR system, SR is sent by the terminal device to the network device (such as gNB) to notify the terminal device that data needs to be sent to the network device. In the NR system, the terminal device can support up to 8 SR configurations, each logical channel corresponds to at most one SR configuration, and the logical channel may not correspond to the SR configuration. The network device can determine the current SR through different SR configurations The type of logical channel transmitted.

When the NR system uses the unlicensed spectrum by means of LAA, LAA defines two access types, namely type1 and type2. For type1, the terminal device can select different channel access priorities according to the service type, and the corresponding relationship between the channel access priorities and the QoS Class Identifier (QCI) is shown in Table 1. For type 2, the terminal device needs to listen for a fixed time of 25us before transmitting the Physical Uplink Shared Channel (PUSCH). Table 1

The optional processing flow 1 of the method for determining a channel access type applied to a terminal device provided by an embodiment of the present invention, as shown in FIG. 2, includes the following steps:

Step S101: Based on the logical channel that triggers the scheduling request, the terminal device determines the first channel access type of the entity upload control channel used to send the scheduling request.

In the embodiment of the present invention, the BSR is triggered when the data on the logical channel meets the trigger condition of the Buffer Status Report (Buffer Status Report, BSR); further, when the trigger condition of the SR is satisfied, the SR is triggered.

Here, the channel access type may have different priorities, and the different priorities are reflected in the duration of the final monitoring channel.

For example, the channel access type is divided based on the channel monitoring duration to obtain the first channel access type, the second channel access type, ... the Nth channel access type; where each channel access type corresponds to The monitoring duration of a channel; the higher the channel access priority, the higher the probability of selecting the monitoring channel duration. It can be understood that, from a statistical point of view, the probability that the channel access type with the highest channel access priority selects the duration of the monitoring channel is higher than the probability of the channel access type with the lower channel access priority selects the duration of the monitoring channel. .

In some embodiments, the logical channel has configuration parameters, and the configuration parameters of the logical channel include at least one channel access type; the terminal device determines the first channel access type of the PUCCH used to send the SR based on the configuration parameters of the logical channel.

In other embodiments, the terminal device determines the configuration parameter of the SR corresponding to the logical channel in the mapping relationship between the logical channel and the configuration parameter of the SR based on the ID of the logical channel; the configuration parameter of the SR includes at least one channel access type; the terminal In the at least one channel access type, the device determines the first channel access type of the PUCCH used to send the SR.

In a specific implementation, the terminal device may determine the first channel access type of the PUCCH used to send the SR based on the order of at least one channel access type included in the logical channel configuration parameter or the SR-based configuration parameter; The first channel access type is determined as the first channel access type, or the channel access type ranked last is determined as the first channel access type. The terminal device may also sort the channel monitoring duration corresponding to at least one channel access type included in the logical channel configuration parameter or the SR configuration parameter, and determine the channel access type corresponding to the shortest channel monitoring duration as the first channel Access type. The terminal device may also sort the window size corresponding to at least one channel access type included in the configuration parameter of the logical channel or the configuration parameter of the SR, and determine the channel access type corresponding to the largest window size as the first channel access type.

An optional processing flow 2 of a method for determining a channel access type provided by an embodiment of the present invention is similar to the foregoing optional processing flow 1, except that after step S101, the method further includes:

Step S102, when neither the configuration parameter of the logical channel nor the configuration parameter of the scheduling request includes the channel access type, the terminal device determines the pre-configured channel access type as the second channel of the entity upload control channel used to send the scheduling request Access type.

In the embodiment of the present invention, the pre-configured channel access type may be a channel access type broadcast by a network device through broadcasting, or may be a channel access sent by a network device to a terminal device through signaling Types of.

The optional processing flow 3 of a method for determining a channel access type provided by an embodiment of the present invention is similar to the foregoing optional processing flow 1, except that after step S101, the method further includes:

Step S103, when neither the configuration parameter of the logical channel nor the configuration parameter of the scheduling request includes the channel access type, the terminal device determines the entity used to send the scheduling request based on the parameter of the service carried by the logical channel to upload the second channel of the control channel Access type.

In the embodiment of the present invention, the service parameters include at least: delay, reliability, or required data rate.

In some embodiments, when the parameter of the service is delay and the delay is less than the preset first threshold, the first channel access type with a higher priority is used.

The optional processing flow 4 of a method for determining a channel access type provided by an embodiment of the present invention is similar to the foregoing optional processing flow 1, except that after step S101, the method further includes:

Step S104: When the terminal device fails to obtain the entity upload control channel based on the first channel access type, based on the order of at least one channel access type in the configuration parameters of the logical channel, the entity upload used to send the scheduling request is determined Control channel second channel access type.

In some embodiments, at least one channel access type in the configuration parameters of the logical channel is arranged in descending order according to the number of times the channel access type history is selected, and the channel access type ranked first is determined as the second channel storage Take type.

In other embodiments, sorting is performed according to the priority order of the channel access types, and the channel access type ranked first is determined as the second channel access type; here, the sorted channel access type may include the first The channel access type may not include the first channel access type.

The optional processing flow 5 of a method for determining a channel access type provided by an embodiment of the present invention is similar to the foregoing optional processing flow 1, except that after step S101, the method further includes:

Step S105: When the terminal device fails to acquire the entity upload control channel based on the first channel access type, it randomly selects a channel type from the channel type list configured in the logical channel as the entity upload control channel used to send the scheduling request The second channel access type.

It should be noted that, in the foregoing embodiment of the present invention, the second channel access type is the channel access type of the next available PUCCH resource for transmitting SR.

The channel access priority order of the first channel access type is higher than that of the second channel access type.

The optional processing flow 65 of the method for determining the channel access type provided by an embodiment of the present invention is similar to the foregoing optional processing flow 1, except that after step S101, the method further includes:

Step S106, the terminal device monitors the PUCCH based on the access type of the first channel.

Step S107, when the monitoring result indicates that the PUCCH is available, the SR is transmitted on the PUCCH.

In the above embodiments of the present invention, the terminal device determines the first channel access type based on the logical channel, and implements SR transmission based on PUCCH resources on the unlicensed spectrum based on the determined first access type.

The optional processing flow 1 of the method for determining a channel access type applied to a network device provided by an embodiment of the present invention, as shown in FIG. 3, includes the following steps:

In step S201, the network device configures the configuration parameters of the logical channel and/or the configuration parameters of the scheduling request for the terminal device.

In the embodiment of the present invention, the configuration parameters of the logical channel and the configuration parameters of the SR are used by the terminal device to determine the channel access type of the PUCCH used to send the SR; wherein, the configuration parameters of the logical channel and the configuration parameter of the SR include at least one Channel access type.

The optional processing flow of the method for determining a channel access type applied to a communication system provided by an embodiment of the present invention, as shown in FIG. 4, includes the following steps:

In step S301, the network device configures the configuration parameters of the logical channel and/or the configuration parameters of the scheduling request for the terminal device.

Here, the configuration parameters of the logical channel and the configuration parameters of the SR include at least one channel access type.

Step S302: The terminal device determines the first channel access type of the PUCCH used to send the SR based on the logical channel that triggers the SR.

In some embodiments, the terminal device determines the first channel access type based on at least one channel access type included in the configuration parameter of the SR logical channel.

In other embodiments, the terminal device determines the configuration parameter of the SR corresponding to the logical channel based on the ID of the logical channel, and determines the first channel access type based on at least one channel access type included in the SR configuration parameter.

In still other embodiments, when the network device is configured with the configuration parameters of the logical channel and the configuration parameters of the SR for the terminal device at the same time, and the configuration parameters of the logical channel and the configuration parameters of the SR include at least one channel access type, the terminal The device selects a configuration parameter based on a logical channel or a configuration parameter based on SR according to a preset policy to determine the access type of the first channel.

Step S303: When the terminal device fails to determine the access type of the first channel or fails to acquire the entity upload control channel based on the access type of the first channel, the access type of the second channel is determined.

In the above embodiments of the present invention, the channel access priority order of the first channel access type is higher than the channel access priority order of the second channel access type. In some embodiments, the channel access priority order includes at least the first channel access priority order and the second channel access priority order; wherein, the first channel access priority order is the highest level channel access priority order, such as channel The listening duration is fixed at 25us; the second channel access priority order is the configurable channel access priority order, such as configuring the channel listening duration and window size according to the configurable channel access priority order.

FIG. 5 is a schematic structural diagram of a terminal device 400 provided in an embodiment of the present application. The terminal device 400 includes: a determining unit 401 configured to determine an entity upload control for sending the scheduling request based on a logical channel that triggers the scheduling request The first channel access type of the channel.

In an embodiment, the configuration parameters of the logical channel include at least one channel access type.

In an embodiment, the determining unit 401 is configured to determine the first channel access type of the entity upload control channel used to send the scheduling request according to at least one channel access type included in the configuration parameter of the logical channel.

In an embodiment, the configuration parameters of the scheduling request include at least one channel access type.

In an embodiment, the determining unit 401 is configured to determine the configuration parameters of the scheduling request corresponding to the logical channel based on the logical channel that triggers the scheduling request;

Among the at least one channel access type included in the configuration parameter of the scheduling request, the first channel access type of the upload control channel used by the entity that sends the scheduling request is determined.

In an embodiment, when the configuration parameter of the logical channel does not include the channel access type, and the configuration parameter of the scheduling request does not include the channel access type,

The determining unit 401 is further configured to determine the pre-configured channel access type as the second channel access type for the entity that sends the scheduling request to upload the control channel.

In an embodiment, when the configuration parameter of the logical channel does not include the channel access type, and the configuration parameter of the scheduling request does not include the channel access type,

The determining unit 401 is further configured to determine the pre-configured channel access type as the second channel access type for the entity that sends the scheduling request to upload the control channel.

In an embodiment, the first channel access type is used to obtain an entity upload control channel failure,

The determining unit 401 is further configured to determine the second channel access type of the entity upload control channel used to send the scheduling request.

In an embodiment, the first channel access type is used to obtain an entity upload control channel failure,

The determining unit 401 is further configured to randomly select a channel type in the channel type list configured by the logical channel as the second channel access type of the entity upload control channel used to send the scheduling request.

In one embodiment, the channel access priority of the first channel access type is higher than the channel access priority of the second channel access type.

FIG. 6 is a schematic structural diagram of a network terminal device 500 provided in an embodiment of the present application. The network device 500 includes: a configuration unit 501 configured to configure logical channel configuration parameters and/or scheduling request configuration parameters for a terminal device ;

The configuration parameters of the logical channel and the configuration parameters of the scheduling request are used by the terminal device to determine the channel access type of the entity upload control channel used to send the scheduling request; wherein,

Both the configuration parameters of the logical channel and the configuration parameters of the scheduling request include at least one channel access type.

In one embodiment, different channel access types have different priorities.

7 is a schematic structural diagram of a communication device 600 provided by an embodiment of the present application. The communication device 600 shown in FIG. 7 includes a processor 610, and the processor 610 can call and run a computer program from the memory to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 7, the communication device 600 may further include a memory 620. The processor 610 can call and run a computer program from the memory 620 to implement the method in the embodiments of the present application.

The memory 620 may be a separate device independent of the processor 610, or may be integrated in the processor 610.

Optionally, as shown in FIG. 7, the communication device 600 may further include a transceiver 630, and the processor 610 may control the transceiver 630 to communicate with other devices, specifically, may send information or data to other devices, or receive other Information or data sent by the device.

Among them, the transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include antennas, and the number of antennas may be one or more.

Optionally, the communication device 600 may specifically be a network device according to an embodiment of the present application, and the communication device 600 may implement the corresponding process implemented by the network device in each method of the embodiment of the present application. Repeat again.

Optionally, the communication device 600 may specifically be a mobile terminal/terminal device according to an embodiment of the present application, and the communication device 600 may implement the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, for simplicity , Will not repeat them here.

8 is a schematic structural diagram of a wafer according to an embodiment of the present application. The chip 700 shown in FIG. 8 includes a processor 710, and the processor 710 can call and run a computer program from the memory to implement the method in the embodiment of the present application.

Optionally, as shown in FIG. 8, the chip 700 may further include a memory 720. The processor 710 can call and run a computer program from the memory 720 to implement the method in the embodiments of the present application.

The memory 720 may be a separate device independent of the processor 710, or may be integrated in the processor 710.

Optionally, the wafer 700 may further include an input interface 730. The processor 710 can control the input interface 730 to communicate with other devices or chips. Specifically, it can obtain information or data sent by other devices or chips.

Optionally, the wafer 700 may further include an output interface 740. The processor 710 can control the output interface 740 to communicate with other devices or chips. Specifically, it can output information or data to other devices or chips.

Optionally, the chip can be applied to the network device in the embodiment of the present application, and the chip can implement the corresponding process implemented by the network device in each method of the embodiment of the present application. For the sake of brevity, no further description is provided here.

Optionally, the wafer may be applied to the mobile terminal/terminal device in the embodiments of the present application, and the wafer may implement the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiments of the present application. For brevity, here No longer.

It should be understood that the wafers mentioned in the embodiments of the present application may also be referred to as system-level wafers, system wafers, wafer systems, or system-on-chip wafers.

9 is a schematic block diagram of a communication system 900 provided by an embodiment of the present application. As shown in FIG. 9, the communication system 900 includes a terminal device 910 and a network device 920.

Among them, the terminal device 910 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 920 can be used to implement the corresponding functions implemented by the network device in the above method. Repeat again.

It should be understood that the processor in the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. In the implementation process, the steps of the foregoing method embodiments may be completed by instructions in the form of hardware integrated logic circuits or software in the processor. The aforementioned processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or Other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps, and logical block diagrams disclosed in the embodiments of the present application may be implemented or executed. The general-purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in conjunction with the embodiments of the present application may be directly implemented and executed by a hardware decoding processor, or may be executed and completed by a combination of hardware and software modules in the decoding processor. The software module may be located in a random storage memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically readable and writable programmable memory, a register, and other mature storage media in the art. The storage medium is located in the memory. The processor reads the information in the memory and combines the hardware to complete the steps of the above method.

It can be understood that the memory in the embodiments of the present application may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. Among them, the non-volatile memory can be read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable ROM, PROM), erasable programmable read-only memory (Erasable PROM, EPROM), Electronically erasable programmable EPROM (EEPROM) or flash memory can be electronically cleared. The volatile memory may be a random access memory (Random Access Memory, RAM), which is used as an external cache memory. By way of example but not limitation, many forms of RAM are available, such as static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory ( Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous Dynamic Random Access Memory (Enhanced SDRAM, ESDRAM), synchronous connection dynamic random access memory (Synchlink DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

It should be understood that the foregoing memory is exemplary but not limiting, for example, the memory in the embodiments of the present application may also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM) , DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM), etc. That is to say, the memories in the embodiments of the present application are intended to include but are not limited to these and any other suitable types of memories.

The embodiments of the present application also provide a computer-readable storage medium for storing computer programs.

Optionally, the computer-readable storage medium can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program enables the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiments of the present application For the sake of brevity, I will not repeat them here.

An embodiment of the present application also provides a computer program product, including computer program instructions.

Optionally, the computer program product can be applied to the mobile terminal/terminal device in the embodiments of the present application, and the computer program instructions cause the computer to execute the corresponding process implemented by the mobile terminal/terminal device in each method of the embodiment of the present application, For brevity, I will not repeat them here.

The embodiment of the present application also provides a computer program. Optionally, the computer program can be applied to the mobile terminal/terminal device in the embodiments of the present application. When the computer program runs on the computer, the computer executes the methods of the embodiments of the present application by the mobile terminal/terminal device For the sake of brevity, I will not repeat them here.

Persons of ordinary skill in the art may realize that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application of the technical solution and design constraints. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

Those skilled in the art can clearly understand that for the convenience and conciseness of the description, the specific working process of the system, device and unit described above can refer to the corresponding process in the foregoing method embodiments, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed system, device, and method may be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the unit is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or elements may be combined or may Integration into another system, or some features can be ignored, or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical, mechanical or other forms.

The unit described as a separate component may or may not be physically separated, and the component displayed as a unit may or may not be a physical unit, that is, it may be located in one place, or may be distributed on multiple network units . Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit.

If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application essentially or part of the contribution to the existing technology or part of the technical solution can be embodied in the form of a software product, the computer software product is stored in a storage medium, including several The instruction is used to enable a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. The aforementioned storage media include: flash drives, removable hard drives, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), magnetic disks or optical discs, etc. can store program code Medium.

The above is only the specific implementation of this application, but the scope of protection of this application is not limited to this, any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in this application. It should be covered by the scope of protection of this application. Therefore, the scope of protection of this application shall be subject to the scope of patent application.

100‧‧‧Communication system 110‧‧‧Network equipment 120‧‧‧terminal equipment S101, S201, S301, S302, S303 400‧‧‧terminal equipment 401‧‧‧ Confirmation unit 500‧‧‧Network equipment 501‧‧‧Configuration unit 600‧‧‧Communication equipment 610‧‧‧ processor 620‧‧‧Memory 630‧‧‧Transceiver 700‧‧‧chip 710‧‧‧ processor 720‧‧‧Memory 730‧‧‧ input interface 740‧‧‧Output interface 900‧‧‧Communication system 910‧‧‧terminal equipment 920‧‧‧Network equipment

FIG. 1 is a schematic diagram of a communication system architecture provided by an embodiment of the present application.

2 is a schematic diagram of an optional processing flow of a method for determining a channel access type applied to a terminal device according to an embodiment of the present application.

3 is a schematic diagram of an optional processing flow of a method for determining a channel access type applied to a network device according to an embodiment of the present application.

4 is a schematic diagram of an optional processing flow of a method for determining a channel access type applied to a communication system provided by an embodiment of the present application.

FIG. 5 is a schematic diagram of the structure of a terminal device provided by an embodiment of the present application.

6 is a schematic structural diagram of a network device provided by an embodiment of the present application.

7 is a schematic structural diagram of a communication device provided by an embodiment of the present application.

8 is a schematic block diagram of a wafer provided by an embodiment of the present application.

9 is a schematic block diagram of a communication system provided by an embodiment of the present application.

S101‧‧‧Step

Claims (23)

A method for determining a channel access type, the method includes: The terminal device determines the first channel access type of the upload control channel used by the entity that sends the scheduling request based on the logical channel that triggers the scheduling request. The method according to item 1 of the patent application scope, wherein the configuration parameter of the logical channel includes at least one channel access type. The method according to item 1 or item 2 of the patent application scope, wherein the first channel access type of the upload control channel determined by the entity for sending the scheduling request includes: The terminal device determines the first channel access type of the entity upload control channel used to send the scheduling request according to at least one channel access type included in the configuration parameter of the logical channel. The method according to item 1 of the patent application scope, wherein the configuration parameter of the scheduling request includes at least one channel access type. The method according to item 1 or item 4 of the patent application scope, wherein the terminal device determines the first channel access type of the entity upload control channel based on the logical channel that triggers the scheduling request, including: Based on the logical channel that triggers the scheduling request, the terminal device determines the configuration parameters of the scheduling request corresponding to the logical channel; Among the at least one channel access type included in the configuration parameter of the scheduling request, the first channel access type of the upload control channel used by the entity that sends the scheduling request is determined. The method according to item 1 of the patent application scope, wherein, when the configuration parameter of the logical channel does not include the channel access type and the configuration parameter of the scheduling request does not include the channel access type, the method further includes: The terminal device determines the pre-configured channel access type as the second channel access type of the entity upload control channel used to send the scheduling request. The method according to item 1 of the patent application scope, wherein, when the configuration parameter of the logical channel does not include the channel access type and the configuration parameter of the scheduling request does not include the channel access type, the method further includes: The terminal device determines the second channel access type of the entity upload control channel used to send the scheduling request based on the parameter of the service carried by the logical channel. The method according to any one of items 1 to 5 of the patent application range, wherein, when the terminal device fails to acquire the entity upload control channel based on the first channel access type, the method further includes: The terminal device determines the second channel access type of the entity upload control channel used to send the scheduling request based on the order of at least one channel access type in the configuration parameters of the logical channel. The method according to any one of items 1 to 5 of the patent application scope, wherein when the terminal device fails to acquire the entity upload control channel based on the first channel access type, the terminal device is configured in the logical channel A channel type is randomly selected from the channel type list as the second channel access type of the entity upload control channel used to send the scheduling request. The method according to any one of claims 1 to 9, wherein the channel access priority order of the first channel access type is higher than the channel access priority order of the second channel access type. A terminal device, the terminal device includes: The determining unit is configured to determine the first channel access type of the upload control channel used by the entity that sends the scheduling request based on the logical channel that triggers the scheduling request, where the configuration parameter of the logical channel includes at least one channel access type ; The determining unit is configured to determine the first channel access type of the entity upload control channel used to send the scheduling request according to at least one channel access type included in the configuration parameter of the logical channel; The terminal device according to item 11 of the patent application scope, wherein the configuration parameter of the logical channel includes at least one channel access type. According to the terminal device described in item 11 or item 12 of the patent application scope, the determination unit is configured to determine the entity to send the scheduling request based on at least one channel access type included in the configuration parameters of the logical channel The first channel access type of the control channel. The terminal device according to item 11 of the patent application scope, wherein the configuration parameter of the scheduling request includes at least one channel access type. The terminal device according to item 11 or item 14 of the patent application scope, wherein the determination unit is configured to determine the configuration parameters of the scheduling request corresponding to the logical channel based on the logical channel that triggers the scheduling request; Among the at least one channel access type included in the configuration parameter of the scheduling request, the first channel access type of the upload control channel used by the entity that sends the scheduling request is determined. The terminal device according to item 11 of the patent application scope, in which the configuration parameter of the logical channel does not include the channel access type, and the configuration parameter of the scheduling request does not include the channel access type, The determining unit is further configured to determine the pre-configured channel access type as the second channel access type for the entity that sends the scheduling request to upload the control channel. The terminal device according to item 11 of the patent application scope, in which the configuration parameter of the logical channel does not include the channel access type, and the configuration parameter of the scheduling request does not include the channel access type, The determining unit is further configured to determine the pre-configured channel access type as the second channel access type for the entity that sends the scheduling request to upload the control channel. The terminal device according to any one of items 11 to 15 of the patent application range, wherein the first channel access type is used to obtain an entity upload control channel failure, The determining unit is further configured to determine the second channel access type of the entity upload control channel used to send the scheduling request. The terminal device according to any one of items 11 to 15 of the patent application range, wherein the first channel access type is used to obtain an entity upload control channel failure, The determining unit is further configured to randomly select a channel type in the channel type list configured by the logical channel as the second channel access type of the entity upload control channel used to send the scheduling request. The terminal device according to any one of claims 11 to 19, wherein the channel access priority of the first channel access type is higher than the channel access priority of the second channel access type. A method for determining a channel access type, the method includes: The network equipment configures the configuration parameters of the logical channel or the configuration parameters of the scheduling request for the terminal equipment; The configuration parameters of the logical channel and the configuration parameters of the scheduling request are used by the terminal device to determine the channel access type of the entity upload control channel used to send the scheduling request; wherein, Both the configuration parameters of the logical channel and the configuration parameters of the scheduling request include at least one channel access type. A network device, the network device includes: a configuration unit configured to configure a logical channel configuration parameter or a scheduling request configuration parameter for a terminal device; The configuration parameters of the logical channel and the configuration parameters of the scheduling request are used by the terminal device to determine the channel access type of the entity upload control channel used to send the scheduling request; wherein, Both the configuration parameters of the logical channel and the configuration parameters of the scheduling request include at least one channel access type. A terminal device, including: a processor and a memory, the memory is used to store a computer program, the processor is used to call and run the computer program stored in the memory, the implementation of the patent application in the scope of items 1 to 10 The dispatch request sending method according to any one of the items or 21.

Images