WO2024109726A1

WO2024109726A1 - Random access method and apparatus, storage medium, terminal device, and network device

Info

Publication number: WO2024109726A1
Application number: PCT/CN2023/132855
Authority: WO
Inventors: 徐敏; 赵思聪
Original assignee: 展讯通信（上海）有限公司
Priority date: 2022-11-25
Filing date: 2023-11-21
Publication date: 2024-05-30
Also published as: CN118102485A

Abstract

The present application provides a random access method and apparatus, a storage medium, a terminal device, and a network device. The random access method comprises: initiating random access by using a physical random access channel (PRACH) resource or initiating random access at a first partial bandwidth for a reduced-capability terminal; sending a first message, the first message carrying a first logical channel identifier, and the first logical channel identifier being a logical channel identifier dedicated to a reduced-capability terminal having a first type or a logical channel identifier used by a non-reduced capability terminal. According to the present application, the capabilities of a reduced-capability terminal can be reported in advance without adding new random access resources.

Description

Random access method and device, storage medium, terminal equipment, network equipment

This application claims priority to the Chinese patent application filed with the China Patent Office on November 25, 2022, with application number 202211497287.4 and invention name “Random access method and device, storage medium, terminal equipment, network equipment”, all contents of which are incorporated by reference in this application.

Technical Field

The present application relates to the field of communication technology, and in particular to a random access method and apparatus, a storage medium, a terminal device, and a network device.

Background technique

With the continuous deployment and widespread application of the fifth generation mobile communication (5th generation mobile networks or 5th generation wireless systems, 5G) systems, in order to better meet the specific requirements of mid-range IoT applications such as industrial wireless sensors, video surveillance and wearable devices for reduced device complexity and cost, reduced size, lower energy consumption, etc., in Release 17 (R17), the 3rd Generation Partnership Project (3GPP) defined New Radio (NR) low-complexity and low-cost devices, namely reduced capability terminals (RedCap), or NR-lite devices. NR R15/16 version terminal devices can support a maximum channel bandwidth of 100 megahertz (MHz); in order to reduce the complexity/cost of terminal devices, R17 reduced capability terminals reduce the maximum supported channel bandwidth: for frequency range 1 (FR1) and FR2 systems, it is reduced to 20MHz and 100MHz respectively. The partial bandwidth (Band Width Part, BWP) of a reduced-capability terminal cannot be greater than the maximum channel bandwidth it supports.

In the prior art, an early indication mechanism is introduced in R17. A reduced capability terminal can use a dedicated physical random access channel (PRACH) resource allocated by the network to send a message 1 (Msg1) or a message A (MsgA). At this time, the base station can determine that the R17 reduced capability terminal is connected based on the received resources. This process is called early reporting of Msg1. If the network configures dedicated PRACH resources, the R17 reduced capability terminal must use the relevant resources for random access.

However, R18 will introduce reduced capability terminals with further reduced capabilities. If the R18 reduced capability terminals continue to adopt the advance reporting mechanism of the previous version (such as R17), such as the advance reporting of Msg1, the cell will be required to allocate random access resources for the new version of the reduced capability terminals, resulting in fragmentation and difficulty in PRACH resource allocation; if the R18 reduced capability terminals do not adopt the advance reporting mechanism, the base station will not be able to identify them as reduced capability terminals in advance, resulting in the reduced capability terminals failing to receive message 2 (Msg2)/message B (MsgB) due to base station scheduling problems, resulting in random access failure, making these reduced capability terminals unable to access the cell normally, or the base station unable to perform access control on these reduced capability terminals.

Summary of the invention

The present application provides a random access method and apparatus, a storage medium, a terminal device, and a network device, and provides a scheme for random access of a new version of a reduced-capability terminal, so as to complete the early reporting of the reduced-capability terminal capability without adding new random access resources.

In order to achieve the above objectives, this application provides the following technical solutions:

In a first aspect, a random access method is provided, the random access method comprising: initiating random access using a physical random access channel PRACH resource or initiating random access in a first part of a bandwidth used for a reduced capability terminal; sending a first message, the first message carrying a first logical channel identifier, the first logical channel identifier being a logical channel identifier dedicated to a reduced capability terminal of a first type or a logical channel identifier used by a non-reduced capability terminal.

Optionally, the PRACH resources are allocated for use by a second type of reduced capability terminal.

Optionally, when the first logical channel identifier is a logical channel identifier of a first type dedicated to a reduced-capability terminal, the PRACH resource is allocated for use by a non-reduced-capability terminal.

Optionally, when the physical random access channel PRACH resources for the reduced capability terminal overlap with the PRACH resources for the non-reduced capability terminal, or the first part of the bandwidth overlaps with the second part of the bandwidth for the non-reduced capability terminal, the first logical channel identifier is the same as the second logical channel identifier corresponding to the reduced capability terminal of the second type.

Optionally, the second type of reduced capability terminal corresponds to a second logical channel identifier, and the first logical channel identifier is different from the second logical channel identifier.

Optionally, the sending of the first message includes: determining the first logical channel identifier according to the length of the message in the common control channel CCCH; and carrying the first logical channel identifier in the first message and sending it.

Optionally, if the length of the message in the CCCH is 64 bits, the first logical channel identifier is 0; if the length of the message in the CCCH is 48 bits, the first logical channel identifier is 52.

In a second aspect, the present application also discloses a random access method, which includes: sending a random access response according to the maximum channel bandwidth of a reduced capability terminal of the first type, wherein the random access is initiated using a physical random access channel PRACH resource or in a first part of the bandwidth used for the reduced capability terminal; receiving a first message, the first message carrying a first logical channel identifier, the first logical channel identifier being a logical channel identifier dedicated to a reduced capability terminal of the first type, or a logical channel identifier used by a non-reduced capability terminal; determining that the current reduced capability terminal is of the first type according to the first logical channel identifier.

Optionally, the sending of the random access response according to the maximum channel bandwidth of the first type of reduced capability terminal comprises: sending the random access response to the reduced capability terminal according to the maximum channel bandwidth of the first type of reduced capability terminal; The random access response is sent to the non-reduced capability terminal based on the maximum channel bandwidth of the terminal.

In a third aspect, the present application also discloses a communication device, comprising: a communication module, used to initiate random access using a physical random access channel PRACH resource or to initiate random access in a first part of the bandwidth used for a reduced capability terminal; the communication module is also used to send a first message, the first message carries a first logical channel identifier, and the first logical channel identifier is a logical channel identifier dedicated to a reduced capability terminal of a first type or a logical channel identifier used by a non-reduced capability terminal.

In a fourth aspect, the present application also discloses a communication device, comprising: a communication module, used to send a random access response according to the maximum channel bandwidth of a reduced capability terminal of the first type, wherein the random access is initiated using a physical random access channel PRACH resource or initiated in a first part of the bandwidth used for the reduced capability terminal; the communication module is also used for a first message, the first message carries a first logical channel identifier, and the first logical channel identifier is a logical channel identifier dedicated to a reduced capability terminal of the first type or a logical channel identifier used for a non-reduced capability terminal; a processing module, used to determine that the current reduced capability terminal has a first type based on the first logical channel identifier.

In a fifth aspect, a computer-readable storage medium is provided, on which a computer program is stored, and the computer program is executed by a processor to execute any one of the methods provided in the first aspect or the second aspect.

In a sixth aspect, a communication device is provided, comprising a memory and a processor, wherein the memory stores a computer program executable on the processor, and the processor executes the computer program to execute any one of the methods provided in the first aspect.

In a seventh aspect, a communication device is provided, comprising a memory and a processor, wherein the memory stores a computer program executable on the processor, and wherein the processor executes the computer program to execute any one of the methods provided in the second aspect.

In an eighth aspect, a computer program product is provided, on which a computer program is stored, and the computer program is executed by a processor to execute any one of the methods provided in the first aspect or the second aspect.

In a ninth aspect, a communication system is provided, comprising the above-mentioned terminal device and the above-mentioned network device.

In the tenth aspect, an embodiment of the present application further provides a chip (or a data transmission device) on which a computer program is stored, and when the computer program is executed by the chip, the steps of the above method are implemented.

In the eleventh aspect, a system chip is used in a terminal, wherein the chip system includes at least one processor and an interface circuit, wherein the interface circuit and the at least one processor are interconnected through lines, and the at least one processor is used to execute instructions to execute any one of the methods provided in the first aspect or the second aspect.

Compared with the prior art, the technical solution of the embodiment of the present application has the following beneficial effects:

In the technical solution of the present application, the reduced capability terminal uses the existing PRACH resources or initiates random access in the first part of the bandwidth used for the reduced capability terminal, and carries a first logical channel identifier dedicated to the first type of reduced capability terminal in the first message. Alternatively, the reduced capability terminal initiates random access in the first part of the bandwidth used for the reduced capability terminal, and carries a logical channel identifier used by non-reduced capability terminals in the first message. The technical solution of the present application enables the network device to know that the type of the reduced capability terminal is the first type without dividing new PRACH resources; since the capabilities of different types of reduced capability terminals are different, the network device can also know the capabilities of the reduced capability terminal, thereby performing access control according to the capabilities of the reduced capability terminal and achieving normal access of the reduced capability terminal.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG1 is a flow chart of a communication method provided in an embodiment of the present application;

FIG2 is an interactive flow chart of a communication method provided in an embodiment of the present application;

FIG3 is an interactive flow chart of another communication method provided in an embodiment of the present application;

FIG4 is an interaction flow chart of another communication method provided in an embodiment of the present application;

FIG5 is an interaction flow chart of another communication method provided in an embodiment of the present application;

FIG6 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application;

FIG. 7 is a schematic diagram of the hardware structure of a communication device provided in an embodiment of the present application.

Detailed ways

The communication systems to which the embodiments of the present application are applicable include, but are not limited to, Long Term Evolution (LTE) systems, fifth-generation (5G) systems, new radio (NR) systems, and future evolution systems or multiple communication convergence systems. Among them, the 5G system can be a non-standalone (NSA) 5G system or a standalone (SA) 5G system. The technical solution of the present application is also applicable to different network architectures, including but not limited to relay network architecture, dual-link architecture, vehicle-to-everything communication architecture and other architectures.

This application mainly relates to the communication between terminal equipment and network equipment. Among them:

The network device in the embodiment of the present application may also be referred to as an access network device, for example, a base station (BS) (also referred to as a base station device), which is a device deployed in a radio access network (RAN) to provide wireless communication functions. For example, the equipment providing base station functions in the second generation (2nd-Generation, 2G) network includes a base transceiver station (Base Transceiver Station, BTS), the equipment providing base station functions in the third generation (3rd-Generation, 3G) network includes a node B (NodeB), and the equipment providing base station functions in the fourth generation (4th-Generation, 4G) network includes an evolved node B (evolved NodeB, eNB), and in wireless local area networks (Wireless Local Area Networks, WLAN), the equipment providing base station functions is an access point (Access Point, AP), and the equipment providing base station functions in NR is the next generation Node Base station (next generation Node Base station, gNB), and the evolving node B (ng-eNB), wherein the gNB and the terminal device communicate using NR technology, and the ng-eNB and the terminal device communicate using Evolved Universal Terrestrial Radio Access (Evolved Universal Terrestrial Radio Access, E-UTRA) technology, and both gNB and ng-eNB can be connected to the 5G core network. The network equipment in the embodiment of the present application also includes equipment that provides base station functions in future new communication systems, etc.

The terminal equipment in the embodiments of the present application may refer to various forms of access terminals, user units, user stations, mobile stations, mobile stations (MS), remote stations, remote terminals, mobile devices, user terminals, wireless communication devices, user agents or user devices. The terminal equipment may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a future 5G network or a terminal device in a future evolving Public Land Mobile Network (PLMN), etc., and the embodiments of the present application do not limit this. The terminal equipment may also be referred to as User Equipment (UE), a terminal, etc.

As described in the background technology, R18 will introduce reduced capability terminals with further reduced capabilities. If the R18 reduced capability terminals continue to adopt the advance reporting mechanism of the previous version (such as R17), such as the advance reporting of Msg1, the cell will be required to allocate random access resources for the new version of the reduced capability terminals, resulting in fragmentation and difficulty in PRACH resource allocation; if the R18 reduced capability terminals do not adopt the advance reporting mechanism, the base station will not be able to identify them as reduced capability terminals in advance, resulting in the reduced capability terminals failing to receive message 2 (Msg2)/message B (MsgB) due to base station scheduling problems, resulting in random access failure, making these reduced capability terminals unable to access the cell normally, or the base station unable to perform access control on these reduced capability terminals.

The technical solution of the present application can enable the network device to know that the type of the reduced capability terminal is the first type without allocating new PRACH resources; since the capabilities of different types of reduced capability terminals are different, the network device can also know the capabilities of the reduced capability terminal, thereby performing access control according to the capabilities of the reduced capability terminal and achieving normal access of the reduced capability terminal. In addition, the present application can also reduce the difficulty of cell allocation of PRACH resources and save the overhead of PRACH resources.

In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, the specific embodiments of the present application are described in detail below with reference to the accompanying drawings.

Referring to FIG1 , the method provided in this application includes:

Step 101: Initiate random access using a physical random access channel PRACH resource or initiate random access in a first portion of bandwidth for reduced capability terminals.

Step 102: Send a first message, where the first message carries a first logical channel identifier, where the first logical channel identifier is a logical channel identifier dedicated to a reduced-capability terminal of a first type or a logical channel identifier used by a non-reduced-capability terminal.

In this embodiment, the random access method can be used in a reduced capability terminal (Redcap). Further, the random access method is used in a reduced capability terminal of the first type. The reduced capability terminal of the first type can be a reduced capability terminal other than an R17 (or earlier version) reduced capability terminal, for example, an R18 reduced capability terminal or a reduced capability terminal of a future evolution version (which may also be referred to as an enhanced reduced capability terminal, which is not limited in the present application). Reduced capability terminals of different versions may be referred to as reduced capability terminals of different types.

Specifically, the different capabilities of terminals with different types of reduced capabilities may refer to different maximum channel bandwidths supported by terminals with different types of reduced capabilities. For example, the maximum channel bandwidth supported by R17 reduced capability terminals is 20 MHz, while the maximum channel bandwidth supported by R18 reduced capability terminals is 5 MHz. Specifically, the R18 reduced capability terminal may be a terminal with reduced baseband (BB) bandwidth, that is, the terminal's transmission and reception of the physical downlink shared channel (PDSCH) and the physical uplink shared channel (PUSCH) will be reduced to 5 MHz, and the radio frequency (RF) bandwidth is still 20 MHz; or the peak rate of the terminal is reduced, etc.

It is understandable that, in a specific implementation, the random access method can be implemented in the form of a software program, and the software program runs in a processor integrated inside a chip or a chip module. The method can also be implemented in the form of software combined with hardware, which is not limited in this application.

In this embodiment, the first message may be an uplink message in the random access process, specifically, message 3 (Msg3), message A (MsgA) or a common control channel (Common Control Channel). Channel, CCCH) Service Data Unit (SDU). CCCH SDU can specifically include RRC resume request (RRCResumeRequest) message and RRC setup request (RRCSetupRequest) message.

In this embodiment, the initiation of random access referred to in step 101 may be sending a preamble or message A, where message A is the first message sent in the two-step random access process, and may include a preamble and message 3 in the four-step random access process, where message 3 is sent via a dedicated PUSCH resource configured in a system message.

In a specific implementation manner, the first logical channel identifier is a logical channel identifier used by a non-R17 reduced-capability terminal.

The following describes the process using different embodiments according to the different resources for initiating random access by the reduced capability terminal and the different first logical channel identifiers.

Embodiment 1, please refer to FIG. 2 , in step 201 , a first type of reduced capability terminal initiates random access using a PRACH resource allocated to a second type of reduced capability terminal.

Specifically, if the cell has allocated PRACH resources for the second type of reduced capability terminal, where the PRACH resources may include Preamble and/or Random Access Channel Occasion (RACH Occasion, RO) resources or PUSCH resources for sending MsgA. It should be noted that the PRACH resources here may be PRACH resources for Msg1 or MsgA. The first type of reduced capability terminal can directly use the PRACH resources to initiate random access. In other words, there is no need to allocate a new type of PRACH resource for the first type of reduced capability terminal, and the first type of reduced capability terminal shares the PRACH resources with the second type of reduced capability terminal. The first type of reduced capability terminal adopts the Msg1 or MsgA reporting mechanism of the second type of reduced capability terminal.

In this case, the network device can determine that the terminal device initiating random access is a reduced capability terminal based on the PRACH resource. However, the network device cannot determine the type of reduced capability terminal at this time. Therefore, in order to ensure the correct reception of the random access message, the network device can schedule data according to the maximum channel bandwidth supported by the first type of reduced capability terminal, for example For example, the network device always schedules data according to 5 MHz. Alternatively, the network device performs scheduling according to the maximum channel bandwidth supported by the first type of reduced capability terminals and the maximum channel bandwidth supported by the non-reduced capability terminals.

In step 202, a first type of reduced capability terminal sends a first message. Accordingly, the network device receives the first message. The first message carries a first logical channel identifier (Logical Channel Identification, LCID), and the first logical channel identifier is a logical channel identifier dedicated to the first type of reduced capability terminal.

In this embodiment, through step 201, the network device can determine that the terminal device initiating random access is a reduced capability terminal, but cannot determine the type of the reduced capability terminal. Through the logical channel identifier dedicated to the reduced capability terminal carried in the first message in step 202, the network device can determine that the terminal device initiating random access is a first type of reduced capability terminal.

In a specific implementation, the first message may be message 3 (Msg3), and the random access process described above in the embodiment of the present invention may also be referred to as early indication based on message 3.

In the embodiment of the present invention, by letting the network device know in advance that the terminal device is a first type of reduced capability terminal, the network device can use appropriate channel bandwidth for scheduling, so that the first type of reduced capability terminal successfully receives Msg2/MsgB, and can send uplink data according to appropriate uplink scheduling, thereby achieving successful random access and allowing the first type of reduced capability terminal to access the cell normally. In addition, by letting the network device know in advance that the terminal device is a first type of reduced capability terminal, the network device can also perform access control on these reduced capability terminals in a timely manner. For example, the current cell load is relatively high, and a large number of reduced capability terminals may access the network at the same time, resulting in resource shortages. At this time, the network device can perform access control based on the type of terminal device, and deny access to some or all of the reduced capability terminals, because the latency requirements of these reduced capability terminals are relatively low, and access can be allowed when they are idle later; or the network device has other access policies and can perform advance access control on the terminal device based on these policies. It should be noted that if the terminal uses the logical channel identifier dedicated to the first type of reduced capability terminal in step 202, step 201 may not be used either. The base station may also determine, according to the dedicated logical channel identifier received in step 202, that the random access procedure is initiated by the first type of reduced capability terminal using the PRACH resources allocated to the second type of reduced capability terminal for use.

In a specific embodiment, the first logical channel identifier may be represented by an index, and the value is selected from [37-42].

Please refer to Table 1. In the current index design of the logical channel identifier, indexes 37-42 are reserved bits, so the first logical channel identifier can be selected from them without adding new bits, thereby reducing signaling overhead.

It should be noted that it is also possible to add new bits to the index of the logical channel identifier and use a new index value to represent the first logical channel identifier, such as an index greater than 63, and this application does not impose any restrictions on this.

Table 1

Specifically, the second type of reduced capability terminal corresponds to the second logical channel identifier, As shown in 35 or 36 in Table 1, the first logical channel identifier is different from the second logical channel identifier.

Embodiment 2, referring to FIG. 3 , in step 301 , a first type of reduced capability terminal initiates random access using a PRACH resource allocated to a second type of reduced capability terminal.

In step 302, a first type of reduced capability terminal sends a first message. Correspondingly, the network device receives the first message. The first message carries a first logical channel identifier, which is a logical channel identifier used by a non-reduced capability terminal, such as 0 and 52 in Table 1.

Specifically, the first logical channel identifier can be determined according to the length of the message in the CCCH. Specifically, if the length of the message in the CCCH is 64 bits, the first logical channel identifier is 0; if the length of the message in the CCCH is 48 bits, the first logical channel identifier is 52.

In this embodiment, through step 301, the network device can determine that the terminal device initiating random access is a reduced capability terminal, but cannot determine the type of the reduced capability terminal. Through the logical channel identifier used by non-reduced capability terminals carried in the first message in step 202, the network device can determine that the terminal device initiating random access is a first type of reduced capability terminal.

Example 3, please refer to Figure 4, in step 401, a first type of reduced capability terminal initiates random access in a first part of the bandwidth (Band Width Part, BWP) used for reduced capability terminals.

In this embodiment, when the cell does not allocate PRACH resources for the second type of reduced capability terminal, the first type of reduced capability terminal initiates random access in the first portion of bandwidth used for the reduced capability terminal, where the first portion of bandwidth may be a portion of bandwidth dedicated to the reduced capability terminal, or may be a portion of bandwidth dedicated to the first type of reduced capability terminal. At this time, the PRACH resources used for the reduced capability terminal do not overlap with the PRACH resources used for the non-reduced capability terminal, or the first portion of bandwidth does not overlap with the second portion of bandwidth used for the non-reduced capability terminal, where the second portion of bandwidth may be the initial portion of bandwidth. In this case, the network device can determine that the terminal device is a reduced capability terminal by initiating a portion of the bandwidth used for random access, but cannot determine the type of the reduced capability terminal. It should be noted that in this embodiment, the cell can allocate PRACH resources for the second type of reduced capability terminal, and the resources can be configured in the first portion of the bandwidth of the reduced capability terminal.

In step 402, a first type of reduced capability terminal sends a first message. Correspondingly, the network device receives the first message. The first message carries a first logical channel identifier, which is a logical channel identifier dedicated to the first type of reduced capability terminal.

In this embodiment, through step 401, the network device can determine that the terminal device initiating random access is a reduced capability terminal, but cannot determine the type of the reduced capability terminal. Through the logical channel identifier dedicated to the reduced capability terminal carried in the first message in step 402, the network device can determine that the terminal device initiating random access is a first type of reduced capability terminal.

Embodiment 4, referring to FIG. 5 , in step 501 , a first type of reduced capability terminal initiates random access in a first portion of bandwidth used for reduced capability terminals.

In step 502, a first type of reduced capability terminal sends a first message. Accordingly, the network device receives the first message. The first message carries a first logical channel identifier, which is a logical channel identifier used by a non-reduced capability terminal, such as 0 and 52 in Table 1.

In this embodiment, through step 501, the network device can determine that the terminal device initiating random access is a reduced capability terminal, but cannot determine the type of the reduced capability terminal. Through the logical channel identifier of the non-reduced capability terminal carried in the first message in step 502, the network device can determine that the terminal device initiating random access is a first type of reduced capability terminal.

Further, in step 503, the network device sends a random access response.

In a specific implementation, if the network device determines that the terminal device is a first type of reduced capability terminal, the network device sends a random access response to the reduced capability terminal according to the maximum channel bandwidth (e.g., 5 MHz) of the first type of reduced capability terminal. If the end device is a reduced capability terminal of the second type, the network device sends a random access response to the reduced capability terminal according to the maximum channel bandwidth (such as 20 MHz) of the reduced capability terminal of the second type.

If the network device determines that the terminal device is neither a first type of reduced capability terminal nor a second type of reduced capability terminal, or determines that the terminal device is a non-reduced capability terminal, a random access response is sent to the non-reduced capability terminal according to the maximum channel bandwidth of the non-reduced capability terminal (e.g., 100 MHz).

In a non-limiting embodiment, if the PRACH resources for the reduced capability terminal overlap with the PRACH resources for the non-reduced capability terminal, or the first portion of bandwidth overlaps with the second portion of bandwidth for the non-reduced capability terminal, the first logical channel identifier is the same as the second logical channel identifier corresponding to the reduced capability terminal of the second type. In other words, the first type of reduced capability terminal and the second type of reduced capability terminal use the same logical channel identifier.

For more specific implementation methods of the embodiments of the present application, please refer to the aforementioned embodiments, which will not be repeated here.

Please refer to FIG. 6 , which shows a communication device 60. The communication device 60 may include:

The communication module 601 is configured to initiate random access using a physical random access channel PRACH resource or initiate random access in a first part of bandwidth used for reduced capability terminals.

The communication module 601 is further configured to send a first message, the first message carrying a first logical channel identifier, where the first logical channel identifier is a logical channel identifier dedicated to a reduced capability terminal of a first type or a logical channel identifier used by a non-reduced capability terminal.

In a specific implementation, the above-mentioned communication device 60 may correspond to a chip with communication function in a terminal device, such as a system-on-a-chip (SOC), a baseband chip, etc.; or correspond to a chip module with communication function in a terminal device; or correspond to a chip module with a data processing function chip, or correspond to a terminal device.

In another specific embodiment, the communication device 60 may include a communication module 601 and Processing module 602.

The communication module 601 is used to send a random access response according to the maximum channel bandwidth of the first type of reduced capability terminal, wherein the random access is initiated using a physical random access channel PRACH resource or in a first part of the bandwidth for the reduced capability terminal.

The communication module 601 is also used for a first message, the first message carries a first logical channel identifier, and the first logical channel identifier is a logical channel identifier dedicated to a reduced capability terminal of a first type or a logical channel identifier used by a non-reduced capability terminal.

The processing module 602 is configured to determine, according to the first logical channel identifier, that the current reduced capability terminal is of the first type.

Further, the communication module 601 sends the random access response to the reduced capability terminal according to the maximum channel bandwidth of the reduced capability terminal of the first type.

In a specific implementation, the above-mentioned communication device 60 may correspond to a chip with communication function in a network device, such as a SOC, a baseband chip, etc.; or correspond to a chip module with communication function in a network device; or correspond to a chip module with a data processing function chip, or correspond to a network device.

For other related descriptions about the communication device 60 , reference may be made to the related descriptions in the aforementioned embodiments, which will not be repeated here.

Regarding the various modules/units included in the various devices and products described in the above embodiments, they can be software modules/units, or hardware modules/units, or they can be partially software modules/units and partially hardware modules/units. For example, for various devices and products applied to or integrated in a chip, the various modules/units included therein can all be implemented in the form of hardware such as circuits, or at least some of the modules/units can be implemented in the form of software programs, which run on a processor integrated inside the chip, and the remaining (if any) modules/units can be implemented in the form of hardware such as circuits; for various devices and products applied to or integrated in a chip module, the various modules/units included therein can all be implemented in the form of hardware such as circuits, and different modules/units can be located in the same chip module. A component (e.g., a chip, a circuit module, etc.) or different components, or at least some modules/units can be implemented in the form of a software program, which runs on a processor integrated inside the chip module, and the remaining (if any) modules/units can be implemented in hardware such as circuits; for various devices and products applied to or integrated in a terminal device, the various modules/units contained therein can all be implemented in hardware such as circuits, and different modules/units can be located in the same component (e.g., a chip, a circuit module, etc.) or different components in the terminal device, or at least some modules/units can be implemented in the form of a software program, which runs on a processor integrated inside the terminal device, and the remaining (if any) modules/units can be implemented in hardware such as circuits.

The embodiment of the present application also discloses a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and when the computer program is run, the steps of the method shown in Figures 1 to 5 can be executed. The storage medium may include a read-only memory (ROM), a random access memory (RAM), a disk or an optical disk, etc. The storage medium may also include a non-volatile memory (non-volatile) or a non-transitory memory, etc.

7 , the present application also provides a hardware structure diagram of a communication device. The device includes a processor 701 , a memory 702 , and a transceiver 703 .

Processor 701 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application. Processor 701 may also include multiple CPUs, and processor 701 may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. The processor here may refer to one or more devices, circuits, or processing cores for processing data (such as computer program instructions).

The memory 702 may be a ROM or other type of static storage device that can store static information and instructions, a RAM or other type of dynamic storage device that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disk, or a read-only optical disk. The memory 702 may be a computer program memory (computer program memory, computer read-only memory, CD-ROM) or other optical disk storage, optical disk storage (including compressed optical disk, laser disk, optical disk, digital versatile disk, Blu-ray disk, etc.), magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, and the embodiments of the present application do not impose any restrictions on this. The memory 702 can be independent (in this case, the memory 702 can be located outside the device or inside the device), or it can be integrated with the processor 701. Among them, the memory 702 can contain computer program code. The processor 701 is used to execute the computer program code stored in the memory 702, so as to implement the method provided in the embodiments of the present application.

The processor 701, the memory 702 and the transceiver 703 are connected via a bus. The transceiver 703 is used to communicate with other devices or a communication network. Optionally, the transceiver 703 may include a transmitter and a receiver. The device used to implement the receiving function in the transceiver 703 can be regarded as a receiver, and the receiver is used to perform the receiving step in the embodiment of the present application. The device used to implement the sending function in the transceiver 703 can be regarded as a transmitter, and the transmitter is used to perform the sending step in the embodiment of the present application.

When the structural diagram shown in FIG7 is used to illustrate the structure of the terminal device involved in the above embodiment, the processor 701 is used to control and manage the actions of the terminal device, for example, the processor 701 is used to support the terminal device to execute steps 101 and 102 in FIG1, or steps 302, 303 and 304 in FIG2, and/or actions performed by the terminal device in other processes described in the embodiments of the present application. The processor 701 can communicate with other network entities through the transceiver 703, for example, communicate with the above network devices. The memory 702 is used to store program codes and data of the terminal device.

When the structural diagram shown in FIG7 is used to illustrate the structure of the network device involved in the above embodiment, the processor 701 is used to control and manage the actions of the network device. For example, the processor 701 is used to support the network device to execute steps 201 and 202 in FIG2, or steps 301 and 302 in FIG2, and/or actions performed by the network device in other processes described in the embodiments of the present application. The processor 701 can communicate with other network entities through the transceiver 703, for example, communicate with the above terminal device. The memory 702 is used to store Stores program code and data for network devices.

The embodiment of the present application defines a unidirectional communication link from an access network to a terminal device as a downlink, data transmitted on the downlink is downlink data, and the transmission direction of downlink data is called the downlink direction; and a unidirectional communication link from a terminal device to an access network is an uplink, data transmitted on the uplink is uplink data, and the transmission direction of uplink data is called the uplink direction.

It should be understood that the term "and/or" in this article is only a description of the association relationship of the associated objects, indicating that there can be three relationships. For example, A and/or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character "/" in this article indicates that the associated objects before and after are in an "or" relationship.

The "plurality" appearing in the embodiments of the present application refers to two or more.

The first, second, etc. descriptions appearing in the embodiments of the present application are only used for illustration and distinction of the description objects. There is no order, nor do they indicate any special limitation on the number of devices in the embodiments of the present application, and cannot constitute any limitation on the embodiments of the present application.

The "connection" that appears in the embodiments of the present application refers to various connection methods such as direct connection or indirect connection to achieve communication between devices, and the embodiments of the present application do not impose any limitations on this.

The above embodiments may be implemented in whole or in part by software, hardware, firmware or any other combination thereof. When implemented using software, the above embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website site, computer, server or data center to another website site, computer, server or data center by wired or wireless means.

It should be understood that in various embodiments of the present application, the size of the sequence number of the above-mentioned processes is not It does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

In the several embodiments provided in the present application, it should be understood that the disclosed methods, devices and systems can be implemented in other ways. For example, the device embodiments described above are merely schematic; for example, the division of the units is only a logical function division, and there may be other division methods in actual implementation; for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or 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 be physically included separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of hardware plus software functional units.

The above-mentioned integrated unit implemented in the form of a software functional unit can be stored in a computer-readable storage medium. The above-mentioned software functional unit is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to perform some steps of the method described in each embodiment of the present application.

Although the present application is disclosed as above, the present application is not limited thereto. Any person skilled in the art can make various changes and modifications without departing from the spirit and scope of the present application, so the protection scope of the present application shall be subject to the scope defined by the claims.

Claims

A random access method, comprising:

Initiating random access using a physical random access channel PRACH resource or initiating random access in the first part of the bandwidth for reduced capability terminals;

A first message is sent, where the first message carries a first logical channel identifier, where the first logical channel identifier is a logical channel identifier dedicated to a reduced capability terminal of a first type or a logical channel identifier used by a non-reduced capability terminal.
The random access method according to claim 1, characterized in that the PRACH resources are allocated for use by the second type of reduced capability terminals.
The random access method according to claim 1 is characterized in that when the first logical channel identifier is a logical channel identifier dedicated to a reduced capability terminal of the first type, the PRACH resource is allocated for use by a non-reduced capability terminal.
The random access method according to claim 1 is characterized in that, when the physical random access channel PRACH resources for the reduced capability terminal overlap with the PRACH resources for the non-reduced capability terminal, or the first part of the bandwidth overlaps with the second part of the bandwidth for the non-reduced capability terminal, the first logical channel identifier is the same as the second logical channel identifier corresponding to the reduced capability terminal of the second type.
The random access method according to claim 1 is characterized in that the second type of reduced capability terminal corresponds to a second logical channel identifier, and the first logical channel identifier is different from the second logical channel identifier.
The random access method according to claim 1, wherein sending the first message comprises:

Determine the first logical channel identifier according to the length of the message in the common control channel CCCH;

The first logical channel identifier is carried in the first message and sent out.
The random access method according to claim 6 is characterized in that if the length of the message in the CCCH is 64 bits, the first logical channel identifier is 0; if the length of the message in the CCCH is 48 bits, the first logical channel identifier is 52.
A random access method, comprising:

Sending a random access response according to a maximum channel bandwidth of a reduced capability terminal of the first type, wherein the random access is initiated using a physical random access channel PRACH resource or in a first portion of the bandwidth for the reduced capability terminal;

receiving a first message, where the first message carries a first logical channel identifier, where the first logical channel identifier is a logical channel identifier dedicated to a reduced capability terminal of a first type, or a logical channel identifier used by a non-reduced capability terminal;

It is determined that the current reduced capability terminal is of the first type according to the first logical channel identifier.
The random access method according to claim 8, wherein the sending of the random access response according to the maximum channel bandwidth of the first type of reduced capability terminal comprises:

sending the random access response to the reduced capability terminal according to the maximum channel bandwidth of the reduced capability terminal of the first type;

The random access response is sent to the non-reduced capability terminal according to the maximum channel bandwidth of the non-reduced capability terminal.
A communication device, comprising:

A communication module, configured to initiate random access using a physical random access channel PRACH resource or initiate random access in a first portion of bandwidth for a reduced capability terminal;

The communication module is further used to send a first message, where the first message carries a first logical channel identifier, where the first logical channel identifier is a logical channel identifier dedicated to a reduced capability terminal of a first type or a logical channel identifier used by a non-reduced capability terminal.
A communication device, comprising:

A communication module, configured to send a random access response according to a maximum channel bandwidth of a reduced capability terminal of the first type, wherein the random access is initiated using a physical random access channel PRACH resource or in a first portion of the bandwidth for the reduced capability terminal;

The communication module is further used for a first message, the first message carrying a first logical channel identifier, the first logical channel identifier being a logical channel identifier dedicated to a reduced capability terminal of a first type or a logical channel identifier used by a non-reduced capability terminal;

The processing module is used to determine, according to the first logical channel identifier, that the current reduced capability terminal is of the first type.
A computer-readable storage medium having a computer program stored thereon, characterized in that when the computer program is executed by a computer, the steps of any one of the random access methods of claims 1 to 9 are executed.
A terminal device comprises a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and is characterized in that when the processor runs the computer program, the steps of the random access method described in any one of claims 1 to 7 are executed.
A network device comprises a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and wherein the processor executes the steps of the random access method described in any one of claims 8 or 9 when running the computer program.