CN114826513B

CN114826513B - Terminal identification method and equipment

Info

Publication number: CN114826513B
Application number: CN202110068639.3A
Authority: CN
Inventors: 王磊; 邢艳萍
Original assignee: Datang Mobile Communications Equipment Co Ltd
Current assignee: Datang Mobile Communications Equipment Co Ltd
Priority date: 2021-01-19
Filing date: 2021-01-19
Publication date: 2024-03-12
Anticipated expiration: 2041-01-19
Also published as: CN114826513A; WO2022156436A1

Abstract

The embodiment of the application relates to a terminal identification method and equipment, wherein the method comprises the following steps: the method comprises the steps that a first class terminal determines a target RO, wherein the target RO is an RO which cannot be used by a second class terminal; and the first type terminal sends a preamble to network side equipment on the target RO so that the network side equipment determines the type of the first type terminal based on the target RO. In the method, only the first class terminal can send the preamble on the target RO, and the second class terminal cannot send the preamble on the target RO; thus, the network side device can determine the type of the first type terminal based on the target RO receiving the preamble.

Description

Terminal identification method and equipment

Technical Field

The present disclosure relates to the field of wireless communications technologies, and in particular, to a terminal identification method and device.

Background

In the new wireless access (5th Generation New RAT,5G NR) system of the fifth generation mobile communication, terminals of different versions can appear, the functions supported by the terminals of different versions are different, and the network side equipment needs to adopt different strategies to schedule the terminals and detect and receive signals sent by the terminals.

In the related art, the network side device cannot identify the supported functions of the terminal, and cannot determine the manner of scheduling the terminal and the manner of detecting and receiving the signal sent by the terminal.

For example: in 5G NR systems, to enhance signaling 3 (Message 3Physical Uplink Shared Channel,msg3 PUSCH) coverage in the physical uplink shared channel, the third generation partnership project (3rd Generation Partnership Project,3GPP) decides to introduce a retransmission mechanism (e.g., repetition type A) for msg3 PUSCH. This means that there will be both terminals supporting retransmission of the Msg3 PUSCH and terminals not supporting retransmission of the Msg3 PUSCH in the network. The network side equipment carries out Msg3 retransmission through a terminal capable of supporting Msg3 PUSCH repetition, and the terminal can carry out repeated transmission on the Msg3 PUSCH on a plurality of slots (time slots) continuously, so that the uplink coverage of the Msg3 PUSCH is enhanced. At this time, the network side device needs to detect the received Msg3 PUSCH on a plurality of consecutive slots, and decide whether to combine the received Msg3 PUSCH based on implementation. For a terminal which does not support the Msg3 PUSCH repetition, repeated transmission of the Msg3 PUSCH cannot be realized. Because the network side equipment in the current system cannot know whether the terminal supports the Msg3 PUSCH repetition or not, the network side equipment cannot determine whether to instruct the terminal to carry out repeated transmission of the Msg3 PUSCH, and the network side equipment needs to detect and receive the Msg3 PUSCH according to two different assumptions, so that the detection and reception process is complex.

Disclosure of Invention

The application provides a terminal identification method and equipment, which are used for solving the problem that the terminal type cannot be identified in the prior art.

In a first aspect, an embodiment of the present application provides a terminal identification method, where the method includes:

the method comprises the steps that a first class terminal determines a target RO (random access channel opportunity, random Access Channel Occasion, RO), wherein the target RO is an RO which cannot be used by a second class terminal;

the first class terminal transmits a preamble (preamble) to a network side device on the target RO so that the network side device determines the type of the first class terminal based on the target RO.

As an alternative embodiment, the method further comprises:

and the first class terminal sends a preamble to the network side device on other RO except the target RO so that the network side device recognizes the first class terminal as a second class terminal.

As an alternative embodiment, the first class of terminal determines a target RO, including:

the first class terminal determines the RO which is not mapped with the SSB as the target RO according to a first parameter in the explicit signaling sent by the network side equipment;

wherein the first parameter indicates a mapping relationship of SSB (synchronization signal block ), preamble, and RO.

As an optional implementation manner, if the first type of terminal is a terminal supporting the coverage enhancement technology, the second type of terminal is a terminal not supporting the coverage enhancement technology;

if the first type of terminal is a redcap terminal, the second type of terminal is a non-redcap terminal;

if the first type of terminal is a small data terminal, the second type of terminal is a non-small data terminal.

As an optional implementation manner, if the first type of terminal is a terminal supporting coverage enhancement technology, the first type of terminal supports retransmission of msg3 PUSCH.

As an optional implementation manner, the first class terminal sends a preamble to a network side device on the target RO, including:

if a plurality of target RO are determined, the first class terminal sends a preamble to the network side device on one or a plurality of target RO;

wherein the plurality of target ROs are located in one or more consecutive SSB-to-RO association periods.

As an optional implementation manner, before the first class terminal sends the preamble to the network side device on the target RO, the method further includes:

and the first class terminal determines the mapping relation of the SSB, the preamble and the target RO.

As an optional implementation manner, the determining, by the first class terminal, a mapping relationship between the SSB, the preamble and the target RO includes:

and the first type terminal determines the mapping relation of the SSB, the preamble and the target RO based on the received explicit signaling sent by the network side equipment.

As an optional implementation manner, the determining, by the first type of terminal, a mapping relationship between SSB, preamble and target RO based on the received explicit signaling sent by the network side device includes:

the first class terminal determines the number of continuous SSB-to-RO association periods contained in one mapping time window of the SSB and the target RO based on a second parameter in the explicit signaling;

and determining the mapping relation of the SSB, the preamble and the target RO according to the first parameter in the explicit signaling in a mapping time window of the SSB and the target RO.

As an alternative embodiment, the mapping relationship includes:

each SSB has at least one corresponding target RO within a mapping time window of the SSB and the target RO.

The first class terminal determines the mapping relation of the SSB, the preamble and the target RO based on a third parameter in the explicit signaling;

the third parameter is used for indicating a mapping relation of the SSB, the preamble and the target RO aiming at the first-class terminal.

As an alternative embodiment, the mapping relationship includes:

each SSB has at least one corresponding target RO during one or a plurality of SSB-to-RO association cycles.

As an alternative embodiment, the number of SSB-to-RO association periods in the mapping relationship is indicated by a second parameter in the explicit signaling.

As an alternative embodiment, the explicit signaling is received by the first class of terminals via the network side configured system information block (System Information Block, SIB) 1.

and the first type terminal determines the mapping relation of the SSB, the preamble and the target RO based on a preset mapping rule.

As an optional implementation manner, the determining, by the first class terminal, a mapping relationship between the SSB, the preamble and the target RO based on a preset mapping rule includes:

And the first type of terminal determines the mapping relation of the SSB, the preamble and the target RO in the preset mapping rule according to the function relation based on the number of the target RO and the number of the SSB candidates.

As an alternative embodiment, the target RO is located in one or a plurality of SSB-to-RO association cycles in succession.

As an alternative embodiment, the mapping relationship includes:

each SSB has at least one corresponding target RO during the one or more SSB-to-RO association periods.

In a second aspect, an embodiment of the present application provides a terminal identification method, where the method includes:

the network equipment receives a preamble sent by a first type terminal on a target RO; the target RO is an RO which cannot be used by the second class terminal;

the network side device determines the type of the first class terminal based on the target RO.

As an alternative embodiment, the method further comprises:

the network side equipment receives a preamble sent by the second class terminal on the RO which can be used by the second class terminal;

the network side device determines the type of the second class terminal based on the RO usable by the second class terminal.

As an alternative embodiment, the method further comprises:

The network side equipment receives the preamble sent by the first class terminal on other RO except the target RO;

the network side device identifies the first class of terminals as second class of terminals based on other ROs than the target RO.

As an optional implementation manner, before the network side device receives the preamble sent by the first class terminal on the target RO, the network side device further includes:

and determining the RO which is not mapped with the SSB as the target RO.

As an optional implementation manner, the network side device receives, on the target RO, a preamble sent by the first class terminal, including:

if the network side equipment determines a plurality of target RO, the network side equipment receives a preamble sent by the first type terminal on one or a plurality of target RO;

and the network side equipment sends an explicit signaling to the first type of terminal.

As an alternative implementation manner, the explicit signaling carries a first parameter and a second parameter, so that the first class of terminals determine the number of continuous SSB-to-RO association periods contained in one mapping time window of SSB and target RO based on the second parameter; and determining the mapping relation of the SSB, the preamble and the target RO according to the first parameter in a mapping time window of the SSB and the target RO.

As an alternative embodiment, the mapping relationship includes:

As an optional implementation manner, the explicit signaling carries a third parameter, so that the first class terminal determines the mapping relationship of the SSB, the preamble and the target RO based on the third parameter;

As an alternative embodiment, the mapping relationship includes:

As an alternative embodiment, the explicit signaling is configured by the network side device through SIB 1.

the network side equipment determines the mapping relation of the SSB, the preamble and the target RO based on a preset mapping rule.

As an alternative embodiment, the mapping relationship includes:

In a third aspect, an embodiment of the present application provides a first type of terminal, where the first type of terminal includes:

the RO determining module is used for determining a target RO, wherein the target RO is an RO which cannot be used by the second class terminal;

And the sending module is used for sending a preamble to the network side equipment on the target RO so that the network side equipment determines the type of the first-type terminal based on the target RO.

In a fourth aspect, an embodiment of the present application provides a network side device, where the network side device includes:

a receiving module, configured to receive a preamble sent by a first class terminal on a target RO; the target RO is an RO which cannot be used by the second class terminal;

and the type determining module is used for determining the type of the first type terminal based on the target RO.

In a fifth aspect, an embodiment of the present application provides a first type of terminal, where the first type of terminal includes: a processor and a memory;

the memory is used for storing computer instructions;

the processor is configured to read the computer instructions and perform the following operations:

determining a target RO, wherein the target RO is an RO which cannot be used by a second class terminal;

and sending a preamble to network side equipment on the target RO so that the network side equipment determines the type of the first-class terminal based on the target RO.

As an alternative embodiment, the operations further comprise:

and sending a preamble to the network side equipment on other RO except the target RO so that the network side equipment can identify the first type terminal as a second type terminal.

As an alternative embodiment, determining the target RO includes:

according to a first parameter in the explicit signaling sent by the network side equipment, determining the RO which is not mapped with the SSB as the target RO;

wherein, the first parameter indicates a mapping relationship of SSB, preamble and RO.

As an optional implementation manner, sending the preamble to the network side device on the target RO includes:

if a plurality of target RO are determined, sending a preamble to the network side equipment on one or a plurality of target RO;

As an alternative embodiment, the operations further comprise:

before sending the preamble to the network device on the target RO, determining the mapping relation among the SSB, the preamble and the target RO.

As an optional implementation manner, the determining the mapping relationship between the SSB, the preamble and the target RO includes:

and determining the mapping relation of the SSB, the preamble and the target RO based on the received explicit signaling sent by the network side equipment.

As an optional implementation manner, based on the received explicit signaling sent by the network side device, determining the mapping relationship between the SSB, the preamble and the target RO includes:

determining the number of consecutive SSB-to-RO association periods contained in a mapping time window of SSBs and target ROs based on a second parameter in the explicit signaling;

As an alternative embodiment, the mapping relationship includes:

Determining the mapping relation of the SSB, the preamble and the target RO based on a third parameter in the explicit signaling;

As an alternative embodiment, the mapping relationship includes:

As an alternative embodiment, the explicit signaling is received through SIB1 configured at the network side.

As an optional implementation manner, determining the mapping relationship between the SSB, the preamble and the target RO includes:

and determining the mapping relation of the SSB, the preamble and the target RO based on a preset mapping rule.

As an optional implementation manner, determining the mapping relationship of the SSB, the preamble and the target RO based on the preset mapping rule includes:

and determining the mapping relation of the SSB, the preamble and the target RO in the preset mapping rule according to the function relation based on the number of the target RO and the number of the SSB candidates.

As an alternative embodiment, the mapping relationship includes:

In a sixth aspect, an embodiment of the present application provides a network side device, where the network side device includes: a processor and a memory;

the memory stores computer instructions;

receiving a preamble sent by a first type terminal on a target RO; the target RO is an RO which cannot be used by the second class terminal;

and determining the type of the first-type terminal based on the target RO.

As an alternative embodiment, the operations further comprise:

receiving a preamble sent by the second class terminal on the RO which can be used by the second class terminal;

the type of the second class of terminal is determined based on ROs that are available to the second class of terminal.

As an alternative embodiment, the operations further comprise:

receiving a preamble sent by a first class terminal on other RO except the target RO;

And identifying the first-type terminal as a second-type terminal based on other RO besides the target RO.

As an alternative embodiment, the operations further comprise:

and before receiving the preamble sent by the first class terminal on the target RO, determining the RO which is not mapped with the SSB as the target RO.

As an optional implementation manner, receiving, on the target RO, a preamble sent by the first class terminal includes:

if a plurality of target RO are determined, receiving a preamble sent by the first type terminal on one or a plurality of target RO;

As an alternative embodiment, the operations further comprise:

and before receiving the preamble sent by the first class terminal on the target RO, sending an explicit signaling to the first class terminal.

As an alternative embodiment, the mapping relationship includes:

As an alternative embodiment, the operations further comprise:

before receiving the preamble sent by the first class terminal on the target RO, determining the mapping relation of the SSB, the preamble and the target RO based on a preset mapping rule.

As an alternative embodiment, the mapping relationship includes:

In a seventh aspect, embodiments of the present application provide a storage medium storing computer-executable instructions for causing a computer to perform the method according to any one of the first or second aspects.

In the scheme provided by the embodiment of the application, the first class terminal determines the target RO which cannot be used by the second class terminal, and sends the preamble to the network side device on the target RO, namely, only the first class terminal can send the preamble on the target RO, and the second class terminal cannot send the preamble on the target RO; thus, the network side device can determine the type of the first type terminal based on the target RO receiving the preamble.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a schematic diagram of mapping relationships between SSB, preamble and RO provided in an embodiment of the present application;

fig. 2 is an interaction flow chart of a first terminal identification method provided in an embodiment of the present application;

fig. 3 is an interaction flow chart of a second terminal identification method provided in an embodiment of the present application;

fig. 4 is an interaction flow chart of a third terminal identification method provided in an embodiment of the present application;

Fig. 5 is an interaction flow chart of a fourth terminal identification method provided in an embodiment of the present application;

FIG. 6A is a schematic structural diagram of a first parameter according to an embodiment of the present disclosure;

FIG. 6B is a schematic diagram of a target RO according to an embodiment of the present application;

fig. 6C is a schematic diagram of mapping relationships between a first SSB, a preamble, and a target RO according to an embodiment of the present application;

fig. 7 is an interaction flow chart of a fifth terminal identification method provided in an embodiment of the present application;

FIG. 8A is a schematic structural diagram of a third parameter according to an embodiment of the present disclosure;

fig. 8B is a schematic diagram of mapping relationships between a second SSB, a preamble, and a target RO according to an embodiment of the present application;

FIG. 9A is a schematic structural diagram of another third parameter according to an embodiment of the present disclosure;

fig. 9B is a schematic diagram of mapping relationships between a third SSB, a preamble, and a target RO according to an embodiment of the present application;

fig. 10 is an interaction flow chart of a sixth terminal identification method provided in an embodiment of the present application;

fig. 11 is a schematic diagram of mapping relationships between a fourth SSB, a preamble, and a target RO according to an embodiment of the present application;

fig. 12 is a flowchart of a first terminal identification method provided in an embodiment of the present application;

fig. 13 is a flowchart of a second terminal identification method according to an embodiment of the present application;

Fig. 14 is a block diagram of a first type of terminal according to an embodiment of the present application;

fig. 15 is a block diagram of a network side device according to an embodiment of the present application;

fig. 16 is a block diagram of another first type of terminal according to an embodiment of the present application;

fig. 17 is a block diagram of another network side device according to an embodiment of the present application.

Detailed Description

For the purposes of making the objects, technical solutions and advantages of the present application more apparent, the present application will be described in further detail below with reference to the accompanying drawings, wherein it is apparent that the described embodiments are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.

Some of the terms in the embodiments of the present application are explained below to facilitate understanding by those skilled in the art.

(1) In the present embodiment, the terms "network" and "system" are often used interchangeably, but those skilled in the art will understand their meaning.

(2) The term "plurality" in the embodiments of the present application means two or more, and other adjectives are similar thereto.

(3) "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a exists alone, A and B exist together, and B exists alone. The character "/" generally indicates that the context-dependent object is an "or" relationship.

(4) The terminal according to the embodiments of the present application may be a device that provides voice and/or data connectivity to a user, a handheld device with a wireless connection function, or other processing device connected to a wireless modem, etc. The names of the terminal devices may also be different in different systems, for example in a 5G system, the terminal devices may be referred to as User Equipment (UE). The wireless terminal device may communicate with one or more Core Networks (CNs) via a radio access Network (Radio Access Network, RAN), which may be mobile terminal devices such as mobile phones (or "cellular" phones) and computers with mobile terminal devices, e.g., portable, pocket, hand-held, computer-built-in or vehicle-mounted mobile devices that exchange voice and/or data with the radio access Network. Such as personal communication services (Personal Communication Service, PCS) phones, cordless phones, session initiation protocol (Session Initiated Protocol, SIP) phones, wireless local loop (Wireless Local Loop, WLL) stations, personal digital assistants (Personal Digital Assistant, PDAs), and the like. The wireless terminal device may also be referred to as a system, subscriber unit (subscriber unit), subscriber station (subscriber station), mobile station (mobile), remote station (remote station), access point (access point), remote terminal device (remote terminal), access terminal device (access terminal), user terminal device (user terminal), user agent (user agent), user equipment (user device), and the embodiments of the present application are not limited.

(5) The network side device according to the embodiment of the present application may be a base station, where the base station may include a plurality of cells for providing services for a terminal. A base station may also be called an access point or may be a device in an access network that communicates over the air-interface, through one or more sectors, with wireless terminal devices, or other names, depending on the particular application. The network side device may be configured to exchange received air frames with internet protocol (Internet Protocol, IP) packets as a router between the wireless terminal device and the rest of the access network, which may include an Internet Protocol (IP) communication network. The network side device may also coordinate attribute management for the air interface. For example, the network side device according to the embodiments of the present application may be a network side device (Base Transceiver Station, BTS) in a global system for mobile communications (Global System for Mobile communications, GSM) or code division multiple access (Code Division Multiple Access, CDMA), a network side device (NodeB) in a wideband code division multiple access (Wide-band Code Division Multiple Access, WCDMA), an evolved network side device (evolutional Node B, eNB or e-NodeB) in a long term evolution (long term evolution, LTE) system, a 5G base station (gNB) in a 5G network architecture (next generation system), a home evolved base station (Home evolved Node B, heNB), a relay node (relay node), a home base station (femto), a pico base station (pico), and the like. In some network structures, the network-side device may include a Centralized Unit (CU) node and a Distributed Unit (DU) node, which may also be geographically separated.

Multiple-input Multiple-output (Multi Input Multi Output, MIMO) transmission can be performed between the network side device and the terminal by using one or more antennas, and the MIMO transmission can be Single User MIMO (SU-MIMO) or Multiple User MIMO (MU-MIMO). The MIMO transmission may be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO, or may be diversity transmission, precoding transmission, beamforming transmission, or the like, depending on the form and number of the root antenna combinations.

The technical scheme provided by the embodiment of the application can be suitable for various systems, in particular to a 5G system. For example, suitable systems may be global system for mobile communications (global system of mobile communication, GSM), code division multiple access (code division multiple access, CDMA), wideband code division multiple access (Wideband Code Division Multiple Access, WCDMA) universal packet Radio service (general packet Radio service, GPRS), long term evolution (long term evolution, LTE), LTE frequency division duplex (frequency division duplex, FDD), LTE time division duplex (time division duplex, TDD), long term evolution-advanced (long term evolution advanced, LTE-a), universal mobile system (universal mobile telecommunication system, UMTS), worldwide interoperability for microwave access (worldwide interoperability for microwave access, wiMAX), 5G New air interface (New Radio, NR), and the like. The various systems comprise a terminal device and a network side device. Core network parts such as evolved packet system (Evloved Packet System, EPS), 5G system (5 GS) etc. may also be included in the system.

In the 5G NR system, terminals of different versions may occur, where functions supported by the terminals of different versions are different, and the network side device needs to schedule the terminals by using different policies, and detect and receive signals sent by the terminals. In the related art, the network side device cannot identify the supported functions of the terminal, and cannot determine the manner of scheduling the terminal and the manner of detecting and receiving the signal sent by the terminal.

For example: in 5G NR systems, to enhance msg3PUSCH coverage, 3GPP decides to introduce repetition type A retransmission mechanisms for msg3 PUSCH. This means that there will be both terminals supporting the Msg3PUSCH repetition and terminals not supporting the Msg3PUSCH repetition in the network. The network side equipment carries out Msg3 retransmission through a terminal capable of supporting Msg3PUSCH repetition, and the terminal can carry out repeated transmission on the Msg3PUSCH on a plurality of slots continuously, so that uplink coverage of the Msg3PUSCH is enhanced. At this time, the network side device needs to detect the received Msg3PUSCH on a plurality of consecutive slots, and decide whether to combine the received Msg3PUSCH based on implementation. For a terminal which does not support the Msg3PUSCH repetition, repeated transmission of the Msg3PUSCH cannot be realized. Because the network side equipment in the current system cannot know whether the terminal supports the Msg3PUSCH repetition or not, the network side equipment cannot determine whether to instruct the terminal to carry out repeated transmission of the Msg3PUSCH, and the network side equipment needs to detect and receive the Msg3PUSCH according to two different assumptions, so that the detection and reception process is complex.

In the current 5G system, the Msg3PUSCH is scheduled by an UL grant (a kind of physical control information from a network side device) carried in a random access response (Random Access Response, RAR), and does not support retransmission. In the random access process, the terminal selects an available preamble for transmission on the RACH resource configured by the base station through the SIB 1. And the terminal detects that the RAR of the terminal is received in a subsequent RAR window (time window), and sends the msg3PUSCH in a corresponding slot according to the indication of the UL grant carried in the RAR. The network detects and receives the Msg3PUSCH on the corresponding slot.

The mapping relationship between SSB and RO is configured by explicit signaling in SIB 1. There is a one-to-one or one-to-many or many-to-one mapping between SSBs and ROs. SSB and RO need to complete at least one round of mapping in one SSB-to-RO association cycle (i.e., all configured SSBs can find the RO corresponding to them). After completing the integer multiple of SSB-to-RO mapping, if there is still a part of RO that cannot complete the mapping with all configured SSBs, this part of RO will not map any SSBs and cannot be used as a preamble transmission. Terminals in the current system need to ignore these ROs. Referring to fig. 1, 8 ROs map with SSB, and 2 ROs do not map with SSB, and cannot transmit preamble on the RO mapped with SSB.

In order to solve the problem that the terminal type cannot be identified in the prior art, the embodiment of the application provides a terminal identification method and device. The embodiment of the application can be applied to a 5G system and other systems.

Embodiments of the present application will be described in detail below with reference to the accompanying drawings.

In the description, the implementation of the terminal and the network side device, and the implementation of the terminal and the network side device in cooperation with each other will be described. Such an explanation does not mean that the two must be implemented cooperatively or separately, and in fact, when the terminal and the network side device are implemented separately, they solve the problems of the terminal and the network side device, respectively, and when the two are used in combination, a better technical effect is obtained.

Fig. 2 is an interaction flow chart of a first terminal identification method provided in an embodiment of the present application, and as shown in the drawing, may include:

step S201: the first class terminal determines a target RO, wherein the target RO is an RO which cannot be used by the second class terminal.

Step S202: and the first class terminal sends a preamble to the network equipment on the target RO.

Step S203: the network side equipment determines the type of the first type terminal based on the target RO.

In this embodiment, the first class terminal determines a target RO that cannot be used by the second class terminal, and sends a preamble to the network side device on the target RO, that is, only the first class terminal can send the preamble on the target RO, and the second class terminal cannot send the preamble on the target RO; in this way, the network side equipment can determine the type of the first type terminal based on the target RO of the preamble; furthermore, the network side equipment only needs to schedule the first type of terminal by adopting a strategy aiming at the first type of terminal, namely, a scheduling mode aiming at the first type of terminal is defined; and the strategy aiming at the first type of terminal is adopted to detect and receive the signals sent by the first type of terminal, so that the complexity of detecting and receiving the signals is reduced.

Optionally, before step S201, the method further includes: and the network side equipment sends the explicit signaling to the first type of terminal. The explicit signaling carries a first parameter indicating a mapping relationship of the SSB, the preamble and the RO.

Correspondingly, step S201 may be implemented by, but not limited to, the following ways:

and the first class terminal determines the RO which is not mapped with the SSB as the target RO according to a first parameter in the explicit signaling.

For the second class of terminals, after mapping is completed at least N times (N is a positive integer) in one association period based on the first parameter in the explicit signaling (that is, all configured SSBs can find the ROs corresponding to the first parameter), some ROs cannot complete mapping with all configured SSBs, and some ROs cannot map any SSBs and cannot be used as the second class of terminals to send preambles, and the second class of terminals needs to ignore the ROs. For the first class of terminals, based on the first parameter in the explicit signaling, after mapping is completed at least N times (N is a positive integer) in one association period, some ROs cannot complete mapping with all configured SSBs, and the first class of terminals determine the part as target ROs that cannot be used by the second class of terminals.

Also taking the above fig. 1 as an example, there are 2 ROs to which SSBs are not mapped, which are ROs that cannot be used by the second class of terminal, that is, the second class of terminal cannot send a preamble on the 2 ROs; correspondingly, the 2 ROs are target ROs determined by the first class of terminal.

In some specific embodiments, the above explicit signaling is configured by the network side device through SIB1, and the corresponding first class terminal receives the explicit signaling through SIB 1.

Alternatively, the step S102 may be implemented by, but not limited to, the following ways:

If a plurality of target RO are determined, the first class terminal sends a preamble to the network side device on one or a plurality of target RO; and the corresponding network side equipment receives the preamble sent by the first type terminal on one or more target RO. Wherein the plurality of target ROs are located in one or more consecutive SSB-to-RO association periods.

In this embodiment, the number of the target ROs may be one or more, and if there is only one target RO, the first class terminal sends a preamble to the network side device on one target RO; if a plurality of target ROs exist, one or more target ROs in the target ROs can be selected according to the actual application scenario, and a preamble can be sent to the network side device on the selected target ROs.

Correspondingly, the network side device needs to determine the type of the first class terminal based on the target RO, and based on the type of the first class terminal, before the network side device receives the preamble sent by the first class terminal on the target RO, the network side device also needs to determine the RO without the SSB mapping as the target RO.

Optionally, the first class of terminals, and the second class of terminals have the following possible implementations:

1) And if the first type of terminal is a terminal supporting the coverage enhancement technology, the second type of terminal is a terminal not supporting the coverage enhancement technology.

The first type of terminal is a terminal supporting Msg3 PUSCH repetition, and the first type of terminal is a terminal not supporting Msg3 PUSCH repetition.

2) If the first type of terminal is a redcap terminal, the second type of terminal is a non-redcap terminal.

3) If the first type of terminal is a small data terminal, the second type of terminal is a non-small data terminal.

In this embodiment, the network side device needs to schedule the first class terminal and the second class terminal in different scheduling manners, and/or receive signals sent by the first class terminal and the second class terminal in different receiving manners. That is, as for the network side device, as long as the terminals with different scheduling modes and receiving signal modes can be respectively used as the first-class terminal and the second-class terminal, the first-class terminal and the second-class terminal are not limited to the three possible implementation modes.

Fig. 3 is an interaction flow chart of a second terminal identification method according to an embodiment of the present application, as shown in the drawing, may include:

step S301: the first class terminal determines a target RO, wherein the target RO is an RO which cannot be used by the second class terminal.

Step S302: and the first class terminal sends a preamble to the network equipment on the target RO.

Step S303: the network side equipment determines the type of the first type terminal based on the target RO.

The implementation manner of steps S301 to S303 is the same as that of steps S201 to S203 described above, and will not be repeated here.

Step S304: the second class of terminals send a preamble to the network device on the available RO.

Step S305: the network side device determines the type of the second class terminal based on the RO available to the second class terminal.

Wherein, there is no necessary logic sequence between the steps S301-S303 and the steps S304-S305.

In this embodiment, a first class terminal determines a target RO that cannot be used by a second class terminal, and sends a preamble to a network side device on the target RO, that is, only the first class terminal can send the preamble on the target RO; the second class terminal transmits a preamble to the network side device on an RO (non-target RO) that it can use, i.e., only the second class terminal will transmit a preamble on an RO that it can use. In this way, the network side equipment can determine the type of the first type terminal based on the target RO of the preamble; the type of the second class terminal can be determined based on the RO available to the second class terminal that receives the preamble. Furthermore, the network side equipment only needs to schedule the first class of terminals by adopting a strategy aiming at the first class of terminals, and schedule the second class of terminals by adopting a strategy aiming at the second class of terminals, so that a scheduling mode is defined; and the strategy aiming at the first class terminal is adopted to detect and receive the signals sent by the first class terminal, and the strategy aiming at the second class terminal is adopted to detect and receive the signals sent by the second class terminal, so that the complexity of detecting and receiving the signals is reduced.

As described above, for the second class terminal, after mapping is completed at least N times in one association period based on the first parameter in the explicit signaling, there is a part of ROs that cannot complete mapping with all configured SSBs, and that cannot map any SSBs and cannot be used as a second class terminal to send a preamble, and the RO mapped to the SSB can be used as a second class terminal to send a preamble, i.e., the RO mapped to the SSB is an RO usable by the second class terminal. For the first class of terminals, based on the first parameter in the explicit signaling, after mapping is completed at least N times in one association period, some ROs cannot complete mapping with all configured SSBs, and the part is determined as a target RO that cannot be used by the second class of terminals.

In other optional embodiments, the first type terminal may also send a preamble to the network side device on an RO other than the target RO (e.g., an RO mapped to SSB as shown in fig. 1), and the network side device does not identify the first type terminal as the first type terminal, but identifies the first type terminal as the second type terminal, because the network side device does not receive the preamble on the target RO. In this way, in some special application scenarios, the network side device can schedule the first class of terminals in a scheduling mode aiming at the second class of terminals, and detect and receive signals sent by the first class of terminals by adopting a receiving strategy aiming at the second class of terminals, so as to meet the requirements of different application scenarios.

Fig. 4 is an interaction flow chart of a third terminal identification method according to an embodiment of the present application, as shown in the drawing, may include:

step S401: the first class terminal determines a target RO, wherein the target RO is an RO which cannot be used by the second class terminal.

The implementation manner of this step S401 is the same as that of the above step S201, and will not be repeated here.

Step S402: the first class terminal determines the mapping relation of SSB, preamble and target RO.

The first type terminal sends a preamble to the network side device on the target RO, and only when the SSB, the preamble and the target RO are mapped, the first type terminal can send the preamble on the target RO. Based on the above, before the first class terminal sends the preamble to the network side device on the target RO, it needs to determine the mapping relationship between the SSB, the preamble and the target RO.

The specific implementation manner of determining the mapping relationship between the SSB, the preamble and the target RO by the first class of terminal is not limited in this embodiment, and for example, the mapping relationship between the SSB, the preamble and the target RO may be determined based on an explicit signaling sent by the received network side device or based on a preset mapping rule.

Step S403: and the first class terminal sends a preamble to the network equipment on the target RO.

Step S404: the network side equipment determines the type of the first type terminal based on the target RO.

The implementation manner of the steps S403 to S404 is the same as that of the steps S202 to S203, and will not be repeated here.

As described above, the first type of terminal may determine the mapping relationship between the SSB, the preamble and the target RO based on the explicit signaling sent by the received network side device, and fig. 5 is a corresponding interaction flowchart of the fourth terminal identification method provided in the embodiment of the present application, and as shown in the drawing, may include:

step S501: the first class terminal determines a target RO, wherein the target RO is an RO which cannot be used by the second class terminal.

The implementation manner of this step S501 is the same as that of the above step S201, and will not be described here again.

Step S502: the first class of terminals determines the number of consecutive SSB-to-RO association periods contained in one mapping time window of SSBs and target ROs based on the second parameter in the explicit signaling.

Step S503: and the first type of terminal determines the mapping relation of the SSB, the preamble and the target RO according to the first parameter in the explicit signaling in a mapping time window of the SSB and the target RO.

For example, the first class terminal may multiplex the first parameter in the target RO, that is, determine the mapping relationship of the SSB, the preamble, and the target RO by referring to the mapping relationship of the SSB, the preamble, and the RO indicated by the first parameter. In this scenario, the explicit signaling also carries a second parameter, and the first class terminal determines, based on the second parameter, the number of consecutive SSB-to-RO association periods included in a mapping time window of the SSB and the target RO, and further determines that mapping of the SSB, the preamble, and the target RO is completed in several consecutive SSB-to-RO association periods.

Specifically, all SSBs complete mapping at least once within a mapping time window between the SSBs and the target ROs, i.e., each SSB has at least one corresponding target RO.

Step S504: and the first class terminal sends a preamble to the network equipment on the target RO.

Step S505: the network side equipment determines the type of the first type terminal based on the target RO.

The implementation manner of steps S504-S505 is the same as that of steps S202-S203, and will not be repeated here.

The above embodiments are described below with reference to specific examples.

Example 1

To enhance the coverage performance of the Msg3PUSCH, the Rel-17 coverage enhancement item determines repetition type A repeated transmissions supporting the Msg3 PUSCH. Typically, there are both Rel-17 terminals in the network that support coverage enhancement, and other terminals that do not support coverage enhancement. Correspondingly, when the Rel-17 terminal supporting coverage enhancement transmits the Msg3PUSCH, repeated transmission is carried out on a plurality of time slots; and when the terminal which does not support coverage enhancement transmits the Msg3PUSCH, the terminal does not support repeated transmission, and the transmission is carried out on the time slot indicated by the UL grant carried by the MAC RAR. The network side dispatches the coverage enhancement terminals and the non-coverage enhancement terminals according to different receiving strategies, and detects and receives the Msg3PUSCH of the terminals supporting the coverage enhancement technology and the terminals not supporting the coverage enhancement technology according to different strategies.

In the embodiment, the first type of terminal is used as a terminal supporting the coverage enhancement technology, and the second type of terminal is used as a terminal not supporting the coverage enhancement technology; the manner in which the network side device configures the target RO for the terminal of the coverage enhancement technique by explicit signaling is exemplified.

In this embodiment, the current system is frequency division duplex (Frequency Division Duplexing, FDD), the frequency band is FR1, and the RACH resource number configured by the base station is RACH configuration #27 (specific parameter configuration and meaning visible reference TS38.211, table 6.3.3.2-2). The number of SSB candidates in the system is 8, and the mapping relation between SSB, preamble and RO can be known from the first parameter (SSB-perRACH-occidionandbb-preablessperssb) carried in the explicit signaling received through SIB 1. Referring to fig. 6A, in this embodiment, parameters outlined by dotted lines are used as a possible implementation of the first parameter, that is, the first parameter indicates that each RO is mapped with one SSB, and each SSB is mapped with 8 preambles. Based on this configuration, SSB-to-RO association period is 10 slots in size at this time. In this embodiment, scs=15 kHz, so SSB-to-RO association period (SSB-to-RO association period) is 10ms.

Based on this, in one association period, the RO mapped with the SSB and the RO not mapped with the SSB can be referred to as shown in fig. 6B. By the RO shown in fig. 6B, which is not mapped with SSB, and is denoted as a target RO (ro#8 and ro#9 in fig. 6B), it is determined whether a certain terminal is a terminal supporting the coverage enhancement technique.

In this embodiment, the terminal supporting the coverage enhancement technique shares the first parameter described above with the terminal not supporting the coverage enhancement technique. That is, it is determined that one SSB is mapped per target RO and 8 preambles are mapped per SSB based on the first parameter for a terminal supporting the coverage enhancement technique. The explicit signaling also carries a second parameter (CEUE-SSB-RACH-occupancy-CB-preamples-window) indicating the number of consecutive SSB-to-RO association periods contained in one mapping time window of the terminal SSB supporting the coverage enhancement technique and the target RO. In a mapping time window of the SSB and the target RO, the configured 8 SSBs complete mapping at least once, namely, the 8 SSBs all have at least one corresponding target RO. The second parameter in this embodiment takes a value of 4, i.e. the target RO needs and SSBs of the terminal for supporting coverage enhancement techniques are mapped in 4 consecutive SSB-to-RO association periods. Specifically, the mapping relationship between SSB, preamble, and target RO of the terminal for supporting the coverage enhancement technique may be shown in fig. 6C.

For a terminal supporting the coverage enhancement technique, in the target RO shown in fig. 6C, it is determined that a corresponding preamble is transmitted on one or more target ROs according to the SSB, the preamble, and the mapping relationship of the target ROs. And if the network side equipment detects that the preamble is received on the target RO, determining that the terminal which transmits the preamble is a terminal supporting the coverage enhancement technology.

For terminals that do not support coverage enhancement techniques, the second parameter is ignored and the preamble is sent only on the ROs other than the target RO in 6B (ro#0-ro#7). If the network side equipment detects that the preamble is received on the other RO except the target RO, the network side equipment determines that the terminal which does not support the coverage enhancement technology transmits the preamble.

As described above, the first type of terminal may determine the mapping relationship between the SSB, the preamble and the target RO based on the received explicit signaling sent by the network side device, and fig. 7 is an interaction flow chart of the fifth terminal identification method provided in the embodiment of the present application, as shown in the figure, may include:

step S701: the first class terminal determines a target RO, wherein the target RO is an RO which cannot be used by the second class terminal.

The implementation of this step S701 is the same as that of the step S201 described above, and will not be described here again.

Step S702: and the first type terminal determines the mapping relation of the SSB, the preamble and the target RO based on a third parameter in the explicit signaling.

For example, the network side device may configure a new set of mapping relationships for the target RO, that is, the first class terminal does not multiplex the first parameter in the target RO, but refers to the third parameter in the explicit signaling to determine the mapping relationships of the SSB, the preamble and the target RO.

Optionally, the mapping relationship includes: each SSB has at least one corresponding target RO during one or a plurality of SSB-to-RO association cycles.

In this scenario, the mapping relationship for the target RO and the mapping relationship for other ROs are different, and at least one mapping of all SSBs may be completed in one SSB-to-RO association period, i.e. each SSB has at least one corresponding target RO; it is also possible that at least one mapping of all SSBs can be done within a succession of SSB-to-RO association periods.

Optionally, the number of SSB-to-RO association periods in the mapping relationship is indicated by a second parameter in the explicit signaling. In this embodiment, the first class terminal determines, based on the second parameter, the number of consecutive SSB-to-RO association periods included in a mapping time window of the SSB and the target RO, that is, the number of SSB-to-RO association periods in the mapping relationship, and further determines that the mapping of the SSB, the preamble and the target RO is completed in several SSB-to-RO association periods.

Step S703: and the first class terminal sends a preamble to the network equipment on the target RO.

Step S704: the network side equipment determines the type of the first type terminal based on the target RO.

The implementation manner of steps S703 to S704 is the same as that of steps S202 to S203, and will not be repeated here.

The above embodiments are described below with reference to specific examples.

Example 2

To enhance the coverage performance of the Msg3PUSCH, the Rel-17 coverage enhancement item determines repetition type A repeated transmissions supporting the Msg3 PUSCH. Typically, there are both Rel-17 terminals in the network that support coverage enhancement, and other terminals that do not support coverage enhancement. Correspondingly, when the Rel-17 terminal supporting coverage enhancement transmits the Msg3PUSCH, repeated transmission is carried out on a plurality of time slots; and when the terminal which does not support coverage enhancement transmits the Msg3PUSCH, the terminal does not support repeated transmission, and the transmission is carried out on the time slot indicated by the UL grant carried by the MAC RAR. The network side dispatches the coverage enhancement terminal and the non-coverage enhancement terminal according to different receiving strategies, and detects and receives the Msg3PUSCH of the coverage enhancement terminal and the non-coverage enhancement terminal according to different strategies.

In this embodiment, the current system is FDD, the frequency band is FR1, and the RACH resource number configured by the base station is RACH configuration #27 (specific parameter configuration and meaning can be seen from reference files TS38.211, table 6.3.3.2-2). The number of SSB candidates in the system is 8, and the mapping relation between SSB, preamble and RO can be known from the first parameter (SSB-perRACH-occidionandbb-preablessperssb) carried in the explicit signaling received through SIB 1. In this embodiment, the implementation of the first parameter may refer to fig. 6A, that is, the first parameter indicates that each RO is mapped with one SSB, and each SSB is mapped with 8 preambles. Based on this configuration, SSB-to-RO association period is 10 slots in size at this time. In this embodiment, scs=15 kHz, so SSB-to-RO association period (SSB-to-RO association period) is 10ms.

In this embodiment, the explicit signaling further carries a third parameter (SSB-perRACH-occidionandbb-preablessessb-ForCEUE) indicating a mapping relationship between SSB, preamble and target RO dedicated to the terminal supporting the coverage enhancement technique. Referring to fig. 8A, in this embodiment, parameters outlined by dotted lines are used as a possible implementation of the third parameter, that is, the third parameter indicates that each RO is mapped with 4 SSBs, and each SSB is mapped with 8 preambles. Specifically, the mapping relationship of SSB, preamble, and target RO of the terminal for supporting the coverage enhancement technique may participate in the illustration of fig. 8B.

For a terminal supporting the coverage enhancement technique, in the target RO shown in fig. 8B, it is determined that a corresponding preamble is transmitted on one or more target ROs according to the SSB, the preamble, and the mapping relationship of the target ROs. And if the network side equipment detects that the preamble is received on the target RO, determining that the terminal which transmits the preamble is a terminal supporting the coverage enhancement technology.

For the terminal that does not support the coverage enhancement technique, the third parameter is ignored and the preamble is transmitted only to the ROs (ro#0 to ro#7) other than the target RO in fig. 6A. If the network side equipment detects that the preamble is received on the other RO except the target RO, the network side equipment determines that the terminal which does not support the coverage enhancement technology transmits the preamble.

Example 3

In this embodiment, the current system is FDD, the frequency band is FR1, and the RACH resource number configured by the base station is RACH configuration #27 (specific parameter configuration and meaning can be seen from reference files TS38.211, table 6.3.3.2-2). The number of SSB candidates in the system is 8, and the mapping relation between SSB, preamble and RO can be known from the first parameter (SSB-perRACH-occidionandbb-preablessperssb) carried in the explicit signaling received through SIB 1. Referring to fig. 6A, in this embodiment, parameters outlined by dotted lines are used as a possible implementation of the first parameter, that is, the first parameter indicates that each RO is mapped with one SSB, and each SSB is mapped with 8 preambles. Based on this configuration, SSB-to-RO association period is 10 slots in size at this time. In this embodiment, scs=15 kHz, so SSB-to-RO association period (SSB-to-RO association period) is 10ms.

In this embodiment, the explicit signaling also carries a second parameter (CEUE-ssb-RACH-Ocction-CB-preamps-window) and a third parameter (ssb-perRACH-OccasionandCB-preambiserSSB-ForCEUE). The second parameter indicates the number of consecutive SSB-to-RO association periods contained in one mapping time window of the terminal SSB supporting the coverage enhancement technique and the target RO; the third parameter indicates a mapping relationship of a terminal-specific SSB, preamble, and target RO supporting the coverage enhancement technique. Referring to fig. 9A, in this embodiment, parameters outlined by dotted lines are used as a possible implementation of the third parameter, that is, the third parameter indicates that each RO is mapped with 2 SSBs, and each SSB is mapped with 8 preambles. In this embodiment, the second parameter takes a value of 2, that is, the target RO needs and SSBs of the terminal for supporting the coverage enhancement technique complete mapping in 2 consecutive SSB-to-RO association periods. Specifically, the mapping relationship of SSB, preamble, and target RO of the terminal for supporting the coverage enhancement technique may participate in the illustration of fig. 9B.

For a terminal supporting the coverage enhancement technique, in the target RO shown in fig. 9B, it is determined that a corresponding preamble is transmitted on one or more target ROs according to the SSB, the preamble, and the mapping relationship of the target ROs. And if the network side equipment detects that the preamble is received on the target RO, determining that the terminal which transmits the preamble is a terminal supporting the coverage enhancement technology.

For the terminal that does not support the coverage enhancement technique, the second parameter and the third parameter are ignored, and the preamble is transmitted only to the ROs (ro#0 to ro#7) other than the target RO in fig. 6A. If the network side equipment detects that the preamble is received on the other RO except the target RO, the network side equipment determines that the terminal which does not support the coverage enhancement technology transmits the preamble.

Fig. 10 is an interaction flow chart of a sixth terminal identification method according to an embodiment of the present application, as shown in the drawing, may include:

step S1001: the first class terminal determines a target RO, wherein the target RO is an RO which cannot be used by the second class terminal.

The implementation of this step S1001 is the same as that of the step S201, and will not be described here again.

Step S1002: and the first type terminal determines the mapping relation of the SSB, the preamble and the target RO based on a preset mapping rule.

In this embodiment, the first type of terminal and the network side device determine the preset mapping rule in advance, and the first type of terminal and the network side device determine the mapping relationship of the SSB, the preamble and the target RO based on the preset mapping rule.

In this embodiment, the specific implementation manner of the preset mapping rule and determining the mapping relationship is not limited, and in one possible implementation manner, the first type of terminal determines, based on the number of target ROs and the number of SSB candidates, the mapping relationship between SSB, preamble and target ROs in the preset mapping rule according to a functional relationship.

The preset mapping rule includes the number of ROs and the correspondence of the functional relationship, that is, the functional relationship to be adopted can be determined according to the number of the target ROs; substituting the number of configured SSB candidates into the functional relationship can obtain the number of SSBs corresponding to a target RO. In addition, the number of preambles corresponding to one SSB can be determined according to the number of preambles available in the network and the number of SSB candidates. Furthermore, according to the number of SSBs corresponding to one target RO and the number of preambles corresponding to one SSB, determining the mapping relationship among the SSBs, the preambles and the target RO in the preset mapping rule.

The network side device may also determine the mapping relationship between the SSB, the preamble and the target RO in the same manner, which is not described herein.

Optionally, the target RO is located in one or more SSB-to-RO association cycles in succession.

Optionally, the mapping relationship includes: each SSB has at least one corresponding target RO during the one or more SSB-to-RO association periods.

Step S1003: and the first class terminal sends a preamble to the network equipment on the target RO.

Step S1004: the network side equipment determines the type of the first type terminal based on the target RO.

The implementation manner of the steps S1003-S1004 is the same as that of the steps S202-S203, and will not be repeated here.

The above embodiments are described below with reference to specific examples.

Example 4

In this embodiment, the terminal and the network side device supporting the coverage enhancement technology determine the mapping relationship of the SSB, the preamble and the target RO according to a preset mapping rule. Specifically, the number of target ROs in the SSB-to-RO association period (denoted as R, in this embodiment, r=2 is taken as an example), the number of SSB candidates in the network (denoted as S, in this embodiment, s=8 is taken as an example), and the number of available preambles in the network (denoted as P, in this embodiment, p=64 is taken as an example); determining the number of SSBs corresponding to one target RO according to the following formula:

In this embodiment r=2, the selected functional relationship isSubstituting s=8 gives x=4, i.e. one target RO corresponds to 4 SSBs. />

Determining the number of preamble corresponding to one SSB according to the following formula: y=p/S. Substituting p=64 and s=8 to obtain x=8, i.e. 8 preambles corresponding to one SSB. Specifically, the mapping relationship between SSB, preamble, and target RO of the terminal for supporting the coverage enhancement technique may be shown in fig. 11.

For a terminal supporting the coverage enhancement technique, in the target RO shown in fig. 11, it is determined that a corresponding preamble is transmitted on one or more target ROs according to the SSB, the preamble, and the mapping relationship of the target ROs. And if the network side equipment detects that the preamble is received on the target RO, determining that the terminal which transmits the preamble is a terminal supporting the coverage enhancement technology.

For terminals that do not support coverage enhancement techniques, the preset mapping rule cannot be known, and the preamble is sent only on the ROs other than the target RO in 6A (ro#0-ro#7). If the network side equipment detects that the preamble is received on the other RO except the target RO, the network side equipment determines that the terminal which does not support the coverage enhancement technology transmits the preamble.

The foregoing embodiments 1 to 4 are all described by taking an FDD system as an example, and the foregoing embodiments 1 to 4 are also applicable to a time division duplex (Time Division Duplex, TDD) system, and specific implementation manners may refer to the foregoing embodiments and are not repeated herein.

As described above, the method can also be used in other scenarios, for example, assuming that the first type of terminal is a RedCap terminal or a small data terminal. For example, for distinguishing between a RedCap UE and a non-RedCap UE, or a small data UE and a non-small data UE, etc. The specific method may refer to the above embodiments, and will not be described herein.

Based on the same inventive concept, the embodiment of the present application further provides a terminal identification method, and since the method corresponds to the method corresponding to the first type of terminal, a specific implementation manner of the method may refer to the foregoing embodiment, and details of repetition are not repeated.

As shown in fig. 12, a flowchart of a first terminal identification method provided in an embodiment of the present application includes the following steps:

step S1201: the first class terminal determines a target RO, wherein the target RO is an RO which cannot be used by the second class terminal.

Step S1202: and the first type terminal sends a preamble to network side equipment on the target RO so that the network side equipment determines the type of the first type terminal based on the target RO.

As an alternative embodiment, the method further comprises:

As an alternative embodiment, the mapping relationship includes:

As an alternative implementation manner, the explicit signaling is received by the first type of terminal through SIB1 configured at the network side.

As an alternative embodiment, the mapping relationship includes:

Based on the same inventive concept, the embodiment of the present application further provides a terminal identification method, and since the method corresponds to the method corresponding to the network side device, a specific implementation manner of the method may refer to the foregoing embodiment, and details of repetition are not repeated.

As shown in fig. 13, a flowchart of a second terminal identification method provided in an embodiment of the present application includes the following steps:

Step S1301: the network equipment receives a preamble sent by a first type terminal on a target RO; the target RO is an RO which cannot be used by the second class terminal;

step S1302: the network side device determines the type of the first class terminal based on the target RO.

As an alternative embodiment, the method further comprises:

and determining the RO which is not mapped with the SSB as the target RO.

As an alternative embodiment, the mapping relationship includes:

As an optional implementation manner, the explicit signaling further carries a third parameter, so that the first class terminal determines a mapping relationship between SSB, preamble and target RO based on the third parameter;

As an alternative embodiment, the mapping relationship includes:

As shown in fig. 14, a first type of terminal 1400 provided in an embodiment of the present application includes: the RO determination module 1401 and the transmission module 1402, in some alternative embodiments, the first class of terminals 1400 further comprises a mapping relation determination module 1403;

an RO determining module 1401 configured to determine a target RO, where the target RO is an RO that cannot be used by the second class of terminals;

a sending module 1402, configured to send a preamble to a network side device on the target RO, so that the network side device determines a type of the first class terminal based on the target RO.

As an alternative embodiment, the RO determining module 1401 determines a target RO, including:

As an alternative embodiment, the sending module 1402 is further configured to: and sending a preamble to the network side equipment on other RO except the target RO so that the network side equipment can identify the first type terminal as a second type terminal.

As an optional implementation manner, the sending module 1402 sends a preamble to a network side device on the target RO, including:

As an alternative embodiment, the mapping relation determining module 1403 is configured to: the sending module 1402 determines a mapping relationship between the SSB, the preamble, and the target RO before sending the preamble to the network side device on the target RO.

As an alternative embodiment, the mapping relationship determining module 1403 determines the mapping relationship of the SSB, the preamble, and the target RO, including:

the mapping relation determining module 1403 determines the mapping relation of the SSB, the preamble and the target RO based on the received explicit signaling sent by the network side device.

As an optional implementation manner, the mapping relationship determining module 1403 determines, based on the received explicit signaling sent by the network side device, a mapping relationship between the SSB, the preamble, and the target RO, where the mapping relationship includes:

the mapping relation determining module 1403 determines, based on the second parameter in the explicit signaling, a number of consecutive SSB-to-RO association periods included in one mapping time window of SSB and target RO;

As an alternative embodiment, the mapping relationship includes:

The mapping relation determining module 1403 determines the mapping relation of the SSB, the preamble, and the target RO based on a preset mapping rule.

As an alternative embodiment, the mapping relationship determining module 1403 determines, based on a preset mapping rule, a mapping relationship of the SSB, the preamble, and the target RO, including:

the mapping relation determining module 1403 determines, according to the function relation, the mapping relation of the SSB, the preamble and the target RO in the preset mapping rule based on the number of target ROs and the number of SSB candidates.

As an alternative embodiment, the mapping relationship includes:

As shown in fig. 15, a network side device 1500 provided in an embodiment of the present application includes: a receiving module 1501 and a type determining module 1502, in some optional embodiments, the network side device 1500 further comprises at least one of a sending module 1503 and a mapping relationship determining module 1504;

a receiving module 1501, configured to receive a preamble sent by a first class terminal on a target RO; the target RO is an RO which cannot be used by the second class terminal;

A type determining module 1502 is configured to determine a type of the first type terminal based on the target RO.

As an optional implementation manner, the receiving module 1501 is further configured to receive, on an RO available to the second class terminal, a preamble sent by the second class terminal;

the type determining module 1502 is further configured to determine a type of the second type of terminal based on ROs that the second type of terminal can use.

As an optional implementation manner, the receiving module 1501 is further configured to receive a preamble sent by the first class terminal on an RO other than the target RO;

the type determining module 1502 is further configured to identify the first type terminal as a second type terminal based on other ROs than the target RO.

As an optional implementation manner, before the receiving module 1501 receives the preamble sent by the first class terminal on the target RO, the receiving module is further configured to:

and determining the RO which is not mapped with the SSB as the target RO.

As an optional implementation manner, the receiving module 1501 receives, on the target RO, a preamble sent by the first class terminal, including:

if multiple target ROs are determined, the receiving module 1501 receives the preamble sent by the first class terminal on one or multiple target ROs;

As an optional implementation manner, the sending module 1503 is configured to send, by the receiving module 1501, explicit signaling to the first type terminal before receiving, at the target RO, the preamble sent by the first type terminal.

As an alternative embodiment, the mapping relationship includes:

As an optional implementation manner, the mapping relationship determining module 1504 is configured to determine, by the receiving module 1501, a mapping relationship between the SSB, the preamble and the target RO based on a preset mapping rule before receiving the preamble sent by the first class terminal on the target RO.

As an alternative embodiment, the mapping relationship includes:

As shown in fig. 16, a first type of terminal provided in an embodiment of the present application includes: processor 1601, memory 1602, transceiver 1603, and bus interface 1604.

The processor 1601 is responsible for managing the bus architecture and general processing, and the memory 1602 may store data used by the processor 1601 in performing operations. The transceiver 1603 is for receiving and transmitting data under the control of the processor 1601.

The bus architecture may comprise any number of interconnected buses and bridges, and in particular one or more processors represented by the processor 1601 and various circuits of the memory represented by the memory 1602. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The processor 1601 is responsible for managing the bus architecture and general processing, and the memory 1602 may store data used by the processor 1601 in performing operations.

The flow disclosed in the embodiments of the present application may be applied to the processor 1601 or implemented by the processor 1601. In implementation, the steps of the signal processing flow may be performed by integrated logic circuitry of hardware in the processor 1601 or instructions in the form of software. The processor 1601 may be a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, where the methods, steps and logic blocks disclosed in the embodiments of the present application may be implemented or performed. The general purpose processor may be a microprocessor or any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in the processor for execution. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in the memory 1602, and the processor 1601 reads information in the memory 1602 and performs steps of a signal processing flow in combination with its hardware.

Specifically, the processor 1601 is configured to read the computer instructions in the memory 1602 and perform the following operations:

As an alternative embodiment, the operations further comprise:

As an alternative embodiment, determining the target RO includes:

As an alternative embodiment, the operations further comprise:

As an alternative embodiment, the mapping relationship includes:

As shown in fig. 17, a network side device provided in an embodiment of the present application includes: a processor 1701, a memory 1702, a transceiver 1703, and a bus interface 1704.

The processor 1701 is responsible for managing the bus architecture and general processing, and the memory 1702 may store data used by the processor 1701 in performing operations. The transceiver 1703 is used for receiving and transmitting data under the control of the processor 1701.

The bus architecture may include any number of interconnecting buses and bridges, and in particular one or more of the processors represented by the processor 1701 and the various circuits of the memory represented by the memory 1702. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, power management circuits, etc., which are well known in the art and, therefore, will not be described further herein. The bus interface provides an interface. The processor 1701 is responsible for managing the bus architecture and general processing, and the memory 1702 may store data used by the processor 1701 in performing operations.

The flow disclosed in the embodiments of the present application may be applied to the processor 1701 or implemented by the processor 1701. In implementation, the steps of the signal processing flow may be performed by integrated logic circuits of hardware in the processor 1701 or instructions in the form of software. The processor 1701 may be a general purpose processor, a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, and may implement or perform the methods, steps, and logic blocks disclosed in the embodiments of the present application. The general purpose processor may be a microprocessor or any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present application may be embodied directly in a hardware processor for execution, or in a combination of hardware and software modules in the processor for execution. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in the memory 1702, and the processor 1701 reads the information in the memory 1702 and performs the steps of the signal processing flow in combination with its hardware.

Specifically, the processor 1701 is configured to read the computer instructions in the memory 1702 and perform the following operations:

and determining the type of the first-type terminal based on the target RO.

As an alternative embodiment, the operations further comprise:

As an alternative embodiment, the mapping relationship includes:

As an alternative embodiment, the operations further comprise:

As an alternative embodiment, the mapping relationship includes:

The embodiment of the application provides a storage medium, which stores computer executable instructions for causing a computer to execute a terminal identification method executed by a terminal of the first type.

The embodiment of the application provides a storage medium, which stores computer executable instructions for causing a computer to execute a terminal identification method executed by the network side device.

The storage media described above can be any available media or data storage device that can be accessed by a computer, including, but not limited to, magnetic storage (e.g., floppy disks, hard disks, magnetic tape, magneto-optical disks (MOs), etc.), optical storage (e.g., CD, DVD, BD, HVD, etc.), and semiconductor storage (e.g., ROM, EPROM, EEPROM, nonvolatile storage (NAND FLASH), solid State Disk (SSD)), etc.

The present application is described above with reference to block diagrams and/or flowchart illustrations of methods, apparatus (systems) and/or computer program products according to embodiments of the application. It will be understood that one block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, and/or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer and/or other programmable data processing apparatus, create means for implementing the functions/acts specified in the block diagrams and/or flowchart block or blocks.

Accordingly, the present application may also be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.). Still further, the present application may take the form of a computer program product on a computer-usable or computer-readable storage medium having computer-usable or computer-readable program code embodied in the medium for use by or in connection with an instruction execution system. In the context of this application, a computer-usable or computer-readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.

It will be apparent to those skilled in the art that various modifications and variations can be made in the present application without departing from the spirit or scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims and the equivalents thereof, the present application is intended to cover such modifications and variations.

Claims

1. A terminal identification method, the method comprising:

the method comprises the steps that a first class terminal determines a target random access channel (RO), wherein the target RO is an RO which cannot be used by a second class terminal;

The first class terminal sends a preamble to network side equipment on the target RO so that the network side equipment determines the type of the first class terminal based on the target RO;

wherein the first class of terminals determines a target RO, comprising:

the first class terminal determines the RO without mapping the synchronous signal block SSB as the target RO according to a first parameter in the explicit signaling sent by the network side equipment;

2. The method of claim 1, wherein if the first type of terminal is a terminal supporting coverage enhancement technology, the second type of terminal is a terminal not supporting coverage enhancement technology;

3. The method of claim 1, wherein the first class of terminals sends a preamble to a network side device on the target RO, comprising:

4. The method of claim 1, wherein the first class of terminals further comprises, before sending a preamble to a network side device on the target RO:

5. The method of claim 4, wherein the first class of terminals determining the mapping relationship of SSB, preamble, and target RO comprises:

6. The method of claim 5, wherein the first class of terminals determines a mapping relationship of SSB, preamble, and target RO based on the received explicit signaling sent by the network side device, comprising:

7. The method of claim 6, wherein the mapping relationship comprises:

8. The method of claim 5, wherein the first class of terminals determines a mapping relationship of SSB, preamble, and target RO based on the received explicit signaling sent by the network side device, comprising:

9. The method of claim 8, wherein the mapping relationship comprises:

10. The method of claim 9, wherein a number of SSB-to-RO association periods in the mapping relationship is indicated by a second parameter in the explicit signaling.

11. The method according to any of the claims 5-10, characterized in that said explicit signaling is received by said first type of terminal through said network side configured system information block SIB 1.

12. The method of claim 4, wherein the first class of terminals determining the mapping relationship of SSB, preamble, and target RO comprises:

13. The method of claim 12, wherein the first class of terminals determines the mapping relationship of SSB, preamble, and target RO based on a preset mapping rule, comprising:

14. The method of claim 12, wherein the target RO is located in one or a plurality of SSB-to-RO association cycles in succession.

15. The method of claim 14, wherein the mapping relationship comprises:

16. A terminal identification method, the method comprising:

The network side equipment determines the type of the first type terminal based on the target RO;

before the network side device receives the preamble sent by the first type terminal on the target RO, the network side device further includes:

and determining the RO which is not mapped with the SSB as the target RO.

17. The method of claim 16, wherein the method further comprises:

18. The method of claim 16, wherein if the first type of terminal is a terminal supporting coverage enhancement technology, the second type of terminal is a terminal not supporting coverage enhancement technology;

19. The method of claim 16, wherein the network side device receives the preamble sent by the first class terminal on the target RO, comprising:

20. The method of claim 16, wherein before the network side device receives the preamble sent by the first class terminal on the target RO, the method further comprises:

21. The method of claim 20, wherein the explicit signaling carries a first parameter and a second parameter, such that the first class of terminals determine a number of consecutive SSB-to-RO association periods contained in one mapping time window of SSBs and target ROs based on the second parameter; and determining the mapping relation of the SSB, the preamble and the target RO according to the first parameter in a mapping time window of the SSB and the target RO.

22. The method of claim 21, wherein the mapping relationship comprises:

23. The method of claim 20, wherein the explicit signaling carries a third parameter, such that the first class of terminals determine a mapping relationship of SSBs, preambles and target ROs based on the third parameter;

24. The method of claim 23, wherein the mapping relationship comprises:

25. The method of claim 24, wherein a number of SSB-to-RO association periods in the mapping relationship is indicated by a second parameter in the explicit signaling.

26. The method according to any of claims 20-25, wherein the explicit signaling is configured by the network side device via SIB 1.

27. The method of claim 16, wherein before the network side device receives the preamble sent by the first class terminal on the target RO, the method further comprises:

28. The method of claim 27, wherein the target RO is located in one or a consecutive plurality of SSB-to-RO association cycles.

29. The method of claim 28, wherein the mapping relationship comprises:

30. A first class of terminals, comprising:

a sending module, configured to send a preamble to a network side device on the target RO, so that the network side device determines a type of the first class terminal based on the target RO;

wherein the RO determination module determines a target RO comprising:

31. A network side device, characterized in that the network side device comprises:

a type determining module for determining a type of the first type terminal based on the target RO;

the receiving module is further configured to, before receiving the preamble sent by the first class terminal on the target RO:

And determining the RO which is not mapped with the SSB as the target RO.

32. A terminal of a first type, comprising: a processor and a memory;

the memory is used for storing computer instructions;

sending a preamble to a network side device on the target RO so that the network side device determines the type of the first-class terminal based on the target RO;

wherein determining the target RO comprises:

33. The first type of terminal of claim 32, wherein if the first type of terminal is a terminal supporting coverage enhancement technology, the second type of terminal is a terminal not supporting coverage enhancement technology;

34. The first class terminal of claim 32, wherein sending a preamble to a network side device on the target RO comprises:

35. The first type of terminal of claim 32, wherein the operations further comprise:

36. The first class of terminals of claim 35, wherein determining the mapping relationship of SSB, preamble, and target RO comprises:

37. The first class of terminals of claim 36, wherein determining the mapping relationship of SSB, preamble and target RO based on the received explicit signaling sent by the network side device comprises:

38. The first class of terminals of claim 37, wherein said mapping relationship comprises:

39. The first class of terminals of claim 37, wherein determining the mapping relationship of SSB, preamble and target RO based on the received explicit signaling sent by the network side device comprises:

40. The first class of terminals of claim 39, wherein the mapping relationship comprises:

41. The first class of terminals of claim 40, wherein the number of SSB-to-RO association periods in the mapping relationship is indicated by a second parameter in the explicit signaling.

42. The first class of terminals of any of claims 36 to 41, wherein said explicit signaling is received via SIB1 configured at said network side.

43. The first class of terminals of claim 35, wherein determining the mapping relationship of SSBs, preambles and target ROs comprises:

44. The first class of terminals of claim 43, wherein determining the mapping relationship of the SSB, the preamble, and the target RO based on the preset mapping rule comprises:

45. A terminal of the first type as recited in claim 43, wherein said target RO is located in one or more SSB-to-RO association cycles.

46. The first class of terminals of claim 45, wherein the mapping relationship comprises:

47. A network side device, comprising: a processor and a memory;

The memory stores computer instructions;

determining a type of the first class of terminals based on the target RO;

wherein the operations further comprise:

48. The network-side device of claim 47, wherein the operations further comprise:

49. The network-side device of claim 47, wherein if the first type of terminal is a terminal supporting coverage enhancement technology, the second type of terminal is a terminal not supporting coverage enhancement technology;

50. The network-side device of claim 47, wherein receiving the preamble sent by the first class of terminal on the target RO comprises:

51. The network-side device of claim 47, wherein the operations further comprise:

52. The network-side device of claim 51, wherein the explicit signaling carries a first parameter and a second parameter, so that the first class of terminals determine, based on the second parameter, a number of consecutive SSB-to-RO association periods included in one mapping time window of SSBs and target ROs; and determining the mapping relation of the SSB, the preamble and the target RO according to the first parameter in a mapping time window of the SSB and the target RO.

53. The network-side device of claim 52, wherein the mapping relationship comprises:

54. The network side device of claim 51, wherein the explicit signaling carries a third parameter, so that the first class of terminals determine a mapping relationship of SSB, preamble and target RO based on the third parameter;

55. The network-side device of claim 54, wherein the mapping relationship comprises:

56. The network-side device of claim 55, wherein the number of SSB-to-RO association periods in the mapping relationship is indicated by a second parameter in the explicit signaling.

57. The network side device of any of claims 51-56, wherein the explicit signaling is configured by the network side device through SIB 1.

58. The network-side device of claim 47, wherein the operations further comprise:

59. A network-side device as recited in claim 58, wherein the target RO is located in one or more SSB-to-RO association cycles.

60. The network-side device of claim 59, wherein the mapping relationship comprises:

61. A storage medium storing computer executable instructions for causing a computer to perform the method of any one of claims 1-29.