The present application claims priority from a chinese patent application entitled "a method for generating random access ID" filed by the national intellectual property office at 22/6/2021 under the application number 202110688647.8, the entire contents of which are incorporated herein by reference.
Detailed Description
In a communication system, after a terminal is powered on or in a cell switching scenario, the terminal may detect a Synchronization Signal Block (SSB) sent by a peripheral access network device, select an access network device capable of providing a network service for the terminal according to the SSB and a system message sent by the access network device, initiate a Random Access (RA) to the selected access network device on an RO corresponding to the SSB, access to a cell covered by the access network device (or the cell corresponding to the SSB), and perform data transmission with the access network device through a Radio Resource Control (RRC) connection between the terminal and the access network device.
In the embodiment of the present application, the SSB may include a Synchronization Signal (SS) and a Physical Broadcast Channel (PBCH). The system information (system information) may include a Master Information Block (MIB) and a System Information Block (SIB). The SS may be used to synchronize the transmission of the terminal with the access network equipment. The system message may include some communication parameters of the cell, such as the system message may include one or more of configuration information (which may be referred to as BWP configuration information for short) of an initial bandwidth part (initial BWP), size of the system bandwidth, subcarrier spacing, and frame structure configuration. With cells (or referred to as sectors) as granularity, in order to enable signals sent by the access network device to cover the whole cell, one cell may correspond to one or more SSBs, one SSB corresponds to one beam, and different beams correspond to SSBs with different numbers. The terminal in the cell may receive and detect the signal quality of one or more SSBs, and determine which beam corresponding to the SSB may meet the signal quality standard according to the detection result, for example, may compare the signal reception energy with a preset threshold, and a beam corresponding to an SSB exceeding the preset threshold meets the signal quality standard. For example, taking the access network device as the base station, as shown in fig. 1, the base station uses 4 SSBs: the SSBs 0-SSBs 3 cover a certain sector/cell, and after the terminal detects the SSBs 0-SSBs 3 sent by the base station, the terminal may measure the signal quality of the 4 SSBs, and if it is determined that the beam corresponding to the SSB2 can provide better signal quality and the provided signal quality exceeds a preset threshold, it is determined that the base station corresponding to the cell may provide network service for the terminal. If the terminal determines to access the cell, the terminal initiates random access to the base station on the RO corresponding to the SSB 2.
In the embodiment of the present application, the random access described above may refer to contention-type random access (or referred to as contention-based random access or competitive random access), and the random access may include 4-step random access (may be referred to as 4-step RA) or 2-step random access (may be referred to as 2-step RA). There is also a non-contention type random access (alternatively referred to as a non-contention based random access or a non-contention random access) as opposed to a contention type random access. The non-contention type random access may be applied to cell handover or in an out-of-synchronization scenario where there is a downlink data transmission requirement, where the non-contention type random access may refer to random access initiated by a terminal using a preamble designated for the non-contention type random access on an RO designated by an access network device. It should be understood that the random access described in the present application refers to a contention type random access, and the present application does not discuss a non-contention type random access unless otherwise specified. The following introduces 4-step random access and 2-step random access:
referring to fig. 2a, for 4-step random access, as shown in fig. 2a, the 4-step random access may include: step (1), the terminal selects a random access occasion (RO), and sends a message (message 1, msg1) to the access network device on the selected RO to notify the access network device that there is a random access request. The message one may include a preamble sequence (or referred to as a preamble or random access sequence (random access preamble)). And (2) after receiving the Msg1, the access network equipment sends a message two (message 2, msg2) to the terminal. Wherein, the message two may include scheduling information of the message three (message 3, msg 3), and the message two may be used to instruct the terminal how to send the message three. And the terminal correspondingly receives the second message. And (3) the terminal sends a third message to the access network equipment according to the message. Step (4), the access network device sends a message four (message 4, msg 4) to the terminal, and the message four may include a response message for Msg3 determined by the access network device, and the response message may include information for contention resolution between the terminals.
Referring to fig. 2b, for 2-step random access, as shown in fig. 2b, the 2-step random access may include: step (1), the terminal selects an RO, and sends a Physical Random Access Channel (PRACH) carrying a message a (MsgA) and a Physical Uplink Shared Channel (PUSCH) to the access network device on the selected RO, where the MsgA may include a preamble. And (2) the access network equipment receives the MsgA and replies a message B (MsgB) to the terminal, wherein the MsgB can comprise information for solving the competition between the terminals.
In the random access process shown in fig. 2a and fig. 2b, except that the first step is that the terminal selects an RO and a preamble sends a message, messages transmitted in other steps all need to be scheduled by the access network device, and the access network device needs to indicate a time-frequency resource location corresponding to the message. For example, after the access network device receives the preamble sent by the terminal on the RO, the access network device may issue Downlink Control Information (DCI) and a Random Access Response (RAR) scheduled by the DCI (e.g., msg2 or MsgB), where the RAR is carried in a Physical Downlink Shared Channel (PDSCH). After the terminal sends the preamble on the RO, the terminal starts to monitor the DCI sent to the terminal on the downlink, and then the RAR sent to the terminal is acquired in the PDSCH scheduled by the DCI.
In this embodiment, the response message may be referred to as a Random Access Response (RAR) or a media access control random access response (MAC RAR). In 4-step RA, RAR may refer to Msg2, and in 2-step RA, RAR may refer to MsgB. The DCI for scheduling the RAR may carry scheduling information for RAR transmission, such as a time-frequency resource occupied by the RAR, an adopted modulation and coding scheme, and the like. The DCI is carried in a Physical Downlink Control Channel (PDCCH). DCI transmitted to different terminals is transmitted in one PDCCH.
In order to enable the terminal to distinguish which DCI transmitted in the PDCCH is transmitted to itself, the DCI may be scrambled with/using a Radio Network Temporary Identity (RNTI). The RNTI may be a sequence of length 16 bits (bit). The terminal monitors DCI sent in the PDCCH on a downlink, can descramble the DCI by using the RNTI, and if the descrambling is successful, the terminal determines that the DCI is the DCI sent to the terminal, and then obtains the RAR according to the indication of the DCI.
As shown in fig. 3a, assuming that the RNTI is a sequence with a length of 16 bits, when the access network device sends the DCI, the access network device generates a check bit (such as a Cyclic Redundancy Check (CRC)) according to information of the coded DCI, where the length of the check bit is also 16 bits. Then, the access network device performs modulo-two addition (XOR) processing on the 16-bit check bit by using the RNTI of the terminal, and encapsulates the processed check bit and the DCI together to be transmitted on the PDCCH. After receiving DCI on the PDCCH, the terminal generates a corresponding check bit according to the received DCI, performs modulo two addition processing on the generated check bit and the RNTI of the terminal, compares the result of the modulo two addition processing with the check bit actually received by the terminal, and if the two are the same, indicates that the DCI is sent to the terminal.
In the embodiment of the present application, for convenience of description, the RNTI used for scrambling DCI in the 4-step random access process may be referred to as RA-RNTI, and the RNTI used for scrambling DCI in the 2-step random access process may be referred to as MsgB-RNTI. An association relationship exists between a value of the RNTI and the RO used by the terminal to send the preamble, and the RNTI can be determined according to a time-frequency resource position of the RO used by the terminal to send the preamble, for example, the RNTI can be determined according to an index value s _ id of a symbol occupied by the RO, an index value t _ id of a time slot occupied by the RO, an index value f _ id of a frequency domain unit occupied by the RO, and an index value ul _ carrier _ id of an uplink carrier occupied by the RO.
For example, for RA-RNTI, the following formula (1) can be satisfied between RA-RNTI and RO:
RA-RNTI=1+s_id+Nsymbol*t_id+Nsymbol*Nslot*f_id+Nsymbol*Nslot*Nf*ul_carrier_id。
for the MsgB-RNTI, the following formula (2) can be satisfied between the MsgB-RNTI and the RO:
MsgB-RNTI =1 s _id + Nsymbol + t _id + Nsymbol + Nslot + f _id + Nsymbol + Nslot + Nf ul _carrier _id + offset amount _1 (offset _ 1) formula (2)
The offset _1 (offset _ 1) may be a preset integer greater than 0, for example, the offset _1 (offset _ 1) may take a value of 17921. Namely, the offset is introduced to distinguish whether DCI scrambled by RNTI corresponds to 2-step RA or 4-step RA, so as to avoid random access conflict between terminals initiating different RA.
For example, assuming that Nsymbol =14, nslot =80, nf =8, nc =2, and offset _1is equal to Nsymbol × Nslot × Nf × Nc, as shown in fig. 3b, the range of values of RA-RNTI for 4-step RA is [1, 17920], the range of values of MsgB-RNTI for 4-step RA is [17921, 35840], and these two types do not overlap each other.
In the embodiment of the present application, the symbol "+" in each formula represents addition calculation, and the symbol "+" represents multiplication calculation. Wherein the coincidence can also be replaced by the symbol "x".
In this embodiment, the value of s _ id is an index (index) (or referred to as a number) of a symbol occupied by the RO in one slot. The index value of the symbol occupied by the RO in one slot may be referred to as an absolute index value of the symbol occupied by the RO in one slot. One slot may include Nsymbol symbols (symbols). Nsymbol may be preconfigured or protocol predefined, nsymbol being an integer greater than 0. For example, in a New Radio (NR) system, nsymbol =14 in the case of a Normal Cyclic Prefix (NCP), that is, 14 symbols may be included in one slot. For example, nsymbol symbols in a slot may be numbered sequentially starting from 0, resulting in a slot including symbols 0 to Nsymbol-1. It should be noted that the present application is not limited to sequentially numbering symbols in one slot from 0, but may also sequentially number symbols in one slot from 1 or other numbers, without limitation. The examples of the present application are described only with reference to the numbers from 0. In the case where symbols in one slot are numbered sequentially from 0, s _ id has a value ranging from [0, nsymbol-1].
In this embodiment, the value of t _ id is an index value (or number) of a timeslot occupied by the RO in a system frame. The index value of the time slot occupied by the RO in one system frame may be referred to as an absolute index value of the time slot occupied by the RO in one system frame. One system frame includes a maximum of Nslot slots. Nslot may be pre-configured or protocol pre-specified, such as that Nslot =80 is specified in an NR system, i.e. a system frame may include up to 80 slots. If the Nslot slots are numbered sequentially starting from 0, a system frame including slots 0 through Nslot-1 can be obtained. It should be noted that the present application is not limited to sequentially numbering the slots in one system frame from 0, but may also sequentially number the slots in one system frame from 1 or other numbers, without limitation. The present application is described only with reference to the numbers starting from 0. In the case of sequentially numbering slots starting from 0, t _ id takes a value in the range of [0, nslot-1].
In the embodiment of the present application, the value of f _ id is an index value (or a number) of a frequency domain unit occupied by RO in Nf frequency domain units; the index value of the frequency-domain unit occupied by RO in Nf frequency-domain units may be referred to as the absolute index value of the frequency-domain unit occupied by RO in Nf frequency-domain units. Nf may be a preset maximum value of the frequency division multiplexing coefficient for random access, nf may be configured in advance or may be predefined by a protocol, for example, nf =8 is specified in the NR system, that is, a frequency domain unit for random access includes at most 8 frequency domain units, and if the 8 frequency domain units are sequentially numbered from 0, the frequency domain unit for random access may be obtained by: frequency domain unit 0 through frequency domain unit 7. It should be noted that the present application is not limited to sequentially numbering frequency domain elements for random access from 0, and may also sequentially number frequency domain elements for random access from 1 or other numbers, without limitation. The examples of the present application are described only with reference to the numbers from 0. In the case of sequentially numbering the frequency domain units starting from 0, f _ id has a value in the range of [0, nf-1]. It should be understood that the frequency domain unit described in the embodiment of the present application may be a bandwidth part (BWP) or a Physical Resource Block (PRB) or other granularity frequency domain resources, and is not limited.
In the embodiment of the application, the value of ul _ carrier _ id is an index value of an uplink carrier occupied by RO in Nc uplink carriers; the index value of the uplink carrier occupied by the RO in the Nc uplink carriers may be referred to as an absolute index value of the uplink carrier occupied by the RO in the Nc uplink carriers. Nc may be a preset number of uplink carriers for random access, and Nc may be pre-configured or protocol-predefined. For example, in the NR system, nc =2 is defined, that is, 2 uplink carriers are used for random access. If the Nc uplink carriers are sequentially numbered from 0, obtaining the uplink carriers for random access may include: uplink carrier 0 to uplink carrier Nc-1. It should be noted that the present application is not limited to sequentially numbering uplink carriers for random access from 0, and may also sequentially number uplink carriers for random access from 1 or other numbers, without limitation. The examples of the present application are described only with reference to the numbers from 0. In the case where the uplink carriers are sequentially numbered starting from 0, the value range of ul _ carrier _ id may be [0, nc-1].
As can be seen from the above formula, the parameters for calculating the RNTI are all determined by the time-frequency location of the RO that sends the preamble. In a scenario where multiple terminals (e.g., reduced capability (redcap) terminals and non-redcap terminals) share the same random access resource (e.g., RO) to transmit preamble or parameters (time domain position, frequency domain index) of the random access resource used when multiple terminals transmit preamble are the same, if the same calculation formula (1) or formula (2)) is used, the calculated RNTIs are the same, and the DCI obtained by scrambling is the same, and it is not possible to distinguish which terminal's DCI through the RNTI. In this case, to solve this problem, different RNTI calculation formulas may be designed for different terminals, so as to ensure that RNTIs of different terminals are different, and DCI of the terminal is scrambled by the RNTI of the terminal. Since the RNTIs of different terminals are different, which terminal is DCI can be distinguished by the RNTI.
For example, the 4-step RA of the non-redcap terminal may be calculated by using the above formula (1) to obtain RA-RNTI, the 2-step RA of the non-redcap terminal may be calculated by using the above formula (2), the following formula (3) is designed for the 4-step RA of the redcap terminal, and the following formula (4) is designed for the 2-step RA of the redcap terminal:
RA-RNTI =1+ s + u id + Nsymbol + t _id + Nsymbol + Nslot + Nf + u symbol + u carrier id + offset amount _2 (offset _ 2) formula (3)
Formula (4) of MsgB-RNTI =1+ s _id + Nsymbol + t _id + Nsymbol + Nslot + f _id + Nsymbol + Nslot + Nf ul _ carrier + offset _3
Wherein, the offset _2 (offset _ 2) and the offset _3 (offset _ 3) can be set to be integers greater than 0, and the offsets in formula (2) to formula (4) can be pre-configured, and these offsets can be used to isolate RA-RNTI and MsgB-RNTI assigned to different types of terminals. For example, as shown in fig. 3c, different RNTIs are allocated to RAs initiated by different types of terminals, an RNTI with a value range of [0, 17920] is allocated to a 4-step RA of a non-redcap terminal, an RNTI with a value range of [17921, 35840] is allocated to a 2-step RA of the non-redcap terminal, an RNTI with a value range of [35841, 53760] is allocated to a 4-step RA of the redcap terminal, and an RNTI with a value range of [53761, 71680] is allocated to a 2-step RA of the redcap terminal.
It should be understood that the formula (3) and the formula (4) relate to the parameters: for the description of s _ id, t _ id, f _ id, ul _ carrier _ id, nsymbol, nslot, and Nf, reference may be made to the above description, which is not repeated herein. In addition, for convenience of description, the formula (1) and the formula (2) may be collectively referred to as a calculation formula corresponding to the second type of terminal, and the second type of terminal may include a non-redcap terminal. The formula (3) and the formula (4) may be collectively referred to as a calculation formula corresponding to a first class terminal, and the first class terminal includes a redcap terminal.
For example, as shown in fig. 4a, the system bandwidth includes an initial bandwidth part (BWP) of the redcap terminal and an initial BWP of the non-redcap terminal. The initial BWP of the non-redcap terminal is allocated with RO resources used by the non-redcap terminal: RO e to RO l, the initial BWP of the redcap terminal is configured with RO resources of the redcap terminal: RO a to RO d. Assume that a non-redcap terminal sends Msg1 on RO e, and a redcap terminal sends Msg1 on RO a, s _ id =10, t_id =40, ul_carrier_id =0. Although the redcap terminal is also a non-redcap terminal, which transmits Msg1 on a different RO, for the non-redcap terminal, since the index value f _ id of the frequency domain unit starts from 0, f _ id =0 for RO e, RO a. I.e. the parameters s _ id, t _ id, f _ id, ul _ carrier _ id used for calculating the RA-RNTI are the same for both redcap and non-redcap terminals. At this time, formula (1) is adopted to obtain RA-RNTI =1+ s _id +14 × t _ id +14 × 80 × f _ id +14 × 80 × 8 × ul _ carrier _ id =1+10+14 × 40+14 × 80 × 0+14 × 80 × 8 × 0=571 for the non-redcap terminal. Assuming offset amount _2=35840, formula (3) is adopted to obtain RA-RNTI =1+ s + u id +14 × t _ id +14 × 80 × f _ id +14 × 80 × 8 × ul _ carrier _ id + offset amount _2=1+10+14 × 40+14 × 80 × 0+14 × 80 × 8 × 0+35840=36411. Thus, although the parameters s _ id, t _ id, f _ id and ul _ carrier _ id are the same, because different calculation formulas are adopted, the RA-RNTIs of the redcap terminal and the non-redcap terminal are different, and two DCIs are obtained by scrambling with different RA-RNTIs and schedule RARs of the redcap terminal and the non-redcap terminal respectively.
For another example, as shown in fig. 4b, in order to improve the utilization rate of the RO resources, the access network device configures a redcap terminal and a non-redcap terminal to share RACH resources (which may be referred to as shared ROs in this application), that is, configures the same RO/shared RO (RO resources: RO a to RO d shown in fig. 4 b) for the redcap terminal and the non-redcap terminal. The non-redcap terminal and the redcap terminal can send Msg1 on the same RO, for example, msg1 on RO a, at this time, although the values of s _ id, t _ id, f _ id, ul _ carrier _ id of the non-redcap terminal and the redcap terminal are the same, the RA-RNTI of the non-redcap terminal can be obtained by formula (1), and the RA-RNTI of the redcap terminal can be obtained by formula (3), so that the RA-RNTIs of the redcap terminal and the non-redcap terminal are different, and two DCIs obtained by scrambling with different RA-RNTIs, and the two DCIs schedule RARs of the redcap terminal and the non-redcap terminal respectively.
According to the method, different RNTI calculation formulas can be designed for different types of terminals by introducing offset, RNTIs used for initiating RA by different types of terminals can be distinguished, the different values of the RNTIs calculated by different types of terminals are ensured, the network side sends down DCI of the terminal according to the RNTIs of different terminals, and the terminal side can distinguish which type of RA initiated by which type of terminal corresponds to the DCI sent down by the network side through the RNTI, so that the terminal can obtain the RAR according to the DCI, and random access conflicts among different terminals initiating different RA are avoided.
Although it can be ensured that the RNTIs of different types of terminals are different by designing different RNTI calculation formulas, the DCI delivered by the network side is the DCI of which terminal is distinguished by the RNTI. However, from the perspective of signaling overhead, in a scenario where multiple terminals share random access resources, if different RNTIs are used for scrambling to obtain different DCIs, scheduling different RARs with different DCIs will increase the signaling overhead. For example, taking fig. 4b as an example, a redcap terminal and a non-redcap terminal share an RO, after an access network device receives Msg1 sent by the redcap terminal and the non-redcap terminal on the shared RO, the access network device obtains two different RA-RNTIs by using formula (1) and formula (3) through calculation, and obtains two DCIs by scrambling using the two different RA-RNTIs, where the two DCIs can schedule two PDSCHs, one PDSCH carries an RAR of the redcap terminal and the other PDSCH carries an RAR of the non-redcap terminal, that is, the two DCIs are used to schedule RARs of the redcap terminal and the non-redcap terminal, respectively, so as to increase signaling overhead.
In order to solve the above problem, an embodiment of the present application provides a random access method, where the method may include: a first terminal sends a first message to access network equipment on a first random access resource, the access network equipment receives the first message and sends a first DCI for scheduling a response message corresponding to the first message to the first terminal; the RNTI used for scrambling the first DCI is obtained by calculation according to the parameter of the first random access resource and the offset, and the offset is indicated to the first terminal through the first information. Namely, the indication terminal calculates the RNTI according to the parameter of the random access resource and the offset, descrambles the received DCI by using the calculated RNTI, and then receives the response message according to the indication of the DCI which descrambles successfully. The RNTI is not calculated according to the parameters of the random access resources, but is calculated by combining an offset amount on the basis, the design mode is different from the existing mode, so that the terminal can calculate the RNTI according to the existing mode or calculate the RNTI by combining the offset amount under the condition that the first information indicates the offset amount, and the calculation mode is flexible and various. In addition, the RNTIs calculated by different types of terminals can be the same in certain scenes, and the RARs of the different types of terminals are scheduled through the same DCI, so that the signaling overhead is saved.
The random access method provided by the embodiment of the present application is described below with reference to the drawings of the specification.
The random access method provided in the embodiment of the present application may be used in any one of a fourth generation (4 th generation,4 g) system, a Long Term Evolution (LTE) system, a fifth generation (5 th generation,5 g) system, a New Radio (NR) system, a NR-vehicle-to-any-object communication (V2X) system, and an internet of things system, and may also be applied to other next-generation communication systems, and the like, without limitation. The following describes a random access method provided in the embodiment of the present application, by taking the communication system shown in fig. 5 as an example.
Fig. 5 is a schematic diagram of a communication system according to an embodiment of the present application, and as shown in fig. 5, the communication system may include an access network device and a plurality of terminals, such as: terminal 1, terminal 2. In the system shown in fig. 5, the terminal may be in an idle state or an inactive state. It should be noted that fig. 5 is an exemplary framework diagram, the number of nodes included in fig. 5 is not limited, and other nodes may be included in addition to the functional nodes shown in fig. 5, such as: core network devices, gateway devices, application servers, etc., without limitation.
The access network device is mainly used for realizing the functions of resource scheduling, wireless resource management, wireless access control and the like of the terminal. Specifically, the access network device may be any one of a small base station, a wireless access point, a Transmission Receive Point (TRP), a Transmission Point (TP), and some other access node.
The terminal may be a terminal equipment (terminal equipment) or a User Equipment (UE), or a Mobile Station (MS), or a Mobile Terminal (MT), etc. Specifically, the terminal may be a mobile phone (mobile phone), a tablet computer or a computer with a wireless transceiving function, and may also be a Virtual Reality (VR) terminal, an Augmented Reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in unmanned driving, a wireless terminal in telemedicine, a wireless terminal in a smart grid, a wireless terminal in a smart city (smart city), a smart home, a vehicle-mounted terminal, and the like. In this embodiment, the apparatus for implementing the function of the terminal may be the terminal, and may also be an apparatus capable of supporting the terminal to implement the function, such as a chip system (for example, a chip, or a processing system formed by multiple chips). The following describes a random access method provided in an embodiment of the present application, by taking a device for implementing a function of a terminal as an example.
In a specific implementation, each network element shown in fig. 5 is as follows: the terminal and the access network device may adopt the composition structure shown in fig. 6 or include the components shown in fig. 6. Fig. 6 is a schematic composition diagram of a communication device 600 according to an embodiment of the present application, where when the communication device 600 has a function of a terminal according to the embodiment of the present application, the communication device 600 may be a terminal or a chip or a system on a chip in the terminal. When the communication apparatus 600 has the functions of the access network device according to the embodiment of the present application, the communication apparatus 600 may be an access network device or a chip or a system on chip in the access network device.
As shown in fig. 6, the communication device 600 may include a processor 601, a communication link 602, and a communication interface 603. Further, the communication device 600 may also include a memory 604. The processor 601, the memory 604 and the communication interface 603 may be connected via a communication line 602.
The processor 601 may be a Central Processing Unit (CPU), a Network Processor (NP), a Digital Signal Processor (DSP), a microprocessor, a microcontroller, a Programmable Logic Device (PLD), or any combination thereof. The processor 601 may also be other devices with processing functions, such as a circuit, a device, or a software module.
A communication line 602 for transmitting information between the respective components included in the communication apparatus 600.
A communication interface 603 for communicating with other devices or other communication networks. The other communication network may be an ethernet, a Radio Access Network (RAN), a Wireless Local Area Network (WLAN), or the like. Communication interface 603 may be a radio frequency module, a transceiver, or any device capable of enabling communication. In the embodiment of the present application, the communication interface 603 is taken as an example of a radio frequency module, where the radio frequency module may include an antenna, a radio frequency circuit, and the like, and the radio frequency circuit may include a radio frequency integrated chip, a power amplifier, and the like.
A memory 604 for storing instructions. Wherein the instructions may be a computer program.
The memory 604 may be a read-only memory (ROM) or other types of static storage devices that can store static information and/or instructions, a Random Access Memory (RAM) or other types of dynamic storage devices that can store information and/or instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, magnetic disc storage media or other magnetic storage devices, and the optical disc storage includes a compact disc, a laser disc, an optical disc, a digital versatile disc, a blu-ray disc, and the like.
It should be noted that the memory 604 may exist independently of the processor 601 or may be integrated with the processor 601. The memory 604 may be used for storing instructions or program code or some data or the like. The memory 604 may be located inside the communication device 600 or outside the communication device 600, which is not limited. The processor 601 is configured to execute the instructions stored in the memory 604 to implement the random access method provided in the following embodiments of the present application.
In one example, processor 601 may include one or more CPUs, such as CPU0 and CPU1 in FIG. 6.
As an alternative implementation, the communication device 600 includes multiple processors, for example, the processor 607 may be included in addition to the processor 601 in fig. 6.
As an alternative implementation, the communication apparatus 600 may further include an output device 605 and an input device 606. The input device 606 may be a keyboard, mouse, microphone, joystick, or the like, and the output device 605 may be a display screen, speaker (spaker), or the like.
It should be noted that the communication apparatus 600 may be a desktop computer, a portable computer, a network server, a mobile phone, a tablet computer, a wireless terminal, an embedded device, a chip system, or a device with a similar structure as in fig. 6. Further, the constituent structure shown in fig. 6 does not constitute a limitation of the communication apparatus, and the communication apparatus may include more or less components than those shown in fig. 6, or combine some components, or a different arrangement of components, in addition to the components shown in fig. 6.
In the embodiment of the present application, the chip system may be composed of a chip, and may also include a chip and other discrete devices.
The following describes a random access method provided in the embodiment of the present application with reference to the communication system shown in fig. 5 and taking a random access resource as an RO as an example. In the following embodiments, each device may have a component shown in fig. 6, and actions, terms, and the like related to each embodiment may be mutually referred to, a name of a message exchanged between devices or a name of a parameter in the message and the like in each embodiment are only an example, and other names may also be used in specific implementations, without limitation. In addition, the terms "first" and "second" and the like in the embodiments of the present application are used for distinguishing different objects, and are not used for describing a specific order of the objects, and the embodiments of the present application do not limit the attributes of the different objects represented by the "first" and the "second".
Fig. 7 is a flowchart of a random access method provided in an embodiment of the present application, and as shown in fig. 7, the method may include:
step 701: the first terminal sends a first message to the access network device on the first RO. Accordingly, the access network device receives a first message from the first terminal.
The first terminal may be any terminal in fig. 5, for example, the first terminal may be terminal 1 or terminal 2 in fig. 5. The first terminal may be in a non-connected state (e.g., an idle state or an inactive state). The access network device may be the access network device of fig. 5, which may provide network services for the first terminal.
Wherein the first RO may be an RO randomly selected by the first terminal for transmitting Msg1 or MsgB. The first message may carry a preamble. The first message may be Msg1. Or the first message may be MsgA, and in addition to carrying the preamble, the MsgA may further include a Physical Uplink Shared Channel (PUSCH) associated with the preamble, and the PUSCH may include uplink data and/or other information.
In this embodiment, the first terminal belongs to a first class of terminal, and the first RO may be included in a random access resource shared by the first class of terminal and the second class of terminal. Illustratively, the first type of terminal includes a redcap terminal, and the second type of terminal includes a non-redcap terminal; or, the first type of terminal includes a terminal supporting coverage enhancement, and the second type of terminal includes a terminal not supporting coverage enhancement; or, the first type of terminal includes a terminal supporting the access network slice, and the second type of terminal includes a terminal not supporting the access network slice. The second class of terminals may be referred to as normal (normal) terminals or as legacy (legacy) terminals.
In the embodiment of the present application, the random access resource shared by the first class of terminals and the second class of terminals may be understood as a shared random access resource. The shared random access resource may be used jointly by terminals of the first type and terminals of the second type. For example, the ROs a to RO d shown in fig. 4b are shared random access resources, and may be shared by a redcap terminal and a non-redcap terminal.
In the embodiment of the present application, the redcap terminal may support a 20 megahertz (MHz) bandwidth, 1 receive antenna (RX), or 2 receive antennas (RX). A non-redcap terminal may support a 100MHz bandwidth, 4 receive antennas (4 RX), etc. When performing the random access procedure, the access network device may configure a dedicated RACH resource (such as a dedicated RO, etc.) for the non-redcap terminal. The non-redcap terminal can send Msg1 or MsgA on the RACH resource configured by the access network device and corresponding to the redcap terminal, the access network device can receive Msg1 or MsgA on the RACH resource, and can know that the terminal is the non-redcap terminal according to the RACH resource.
In the embodiment of the present application, coverage enhancement may refer to increasing a coverage range by repeating transmission or the like. Taking a Physical Uplink Shared Channel (PUSCH) as an example, a terminal supporting coverage enhancement capability may repeatedly send a PUSCH multiple times at one time, and when an access network device receives a signal, the access network device may combine and receive the repeated PUSCHs to increase an equivalent signal-to-noise ratio of the signal, so that the access network device receives a signal of a terminal farther away. If a terminal needs to use a coverage enhancement technology such as repeated transmission when sending Msg3 or MsgA in a random access process, the access network device may configure a dedicated RACH resource (such as a dedicated RO) for the "coverage enhancement" of the terminal. After the terminal selects the RACH resource associated with coverage enhancement, msg1 or MsgA may be sent on the selected RACH resource, and correspondingly, the access network device may receive Msg1 or MsgA on the RACH resource. For 4-step RA, the access network device may know that the terminal wishes to use coverage enhancement technology to send Msg3 according to the RACH resource selected by the terminal, and then may schedule transmission of Msg3 in a coverage enhancement manner. For 2-step RA, the RACH resource corresponding to the "coverage enhancement" includes a dedicated RO/preamble and a PUSCH configured in a coverage enhancement mode (such as repeated transmission, etc.), and when the terminal sends MsgA, the terminal sends the RO/preamble corresponding to the "coverage enhancement" and the PUSCH transmitted repeatedly.
In this embodiment of the present application, a terminal that supports an access network slice may obtain/be allocated with a better quality and a more sufficient air interface resource, and a terminal that does not support an access network slice may obtain/be allocated with a worse air interface resource. In performing the random access procedure, the access network device may configure a dedicated RACH resource (such as a dedicated RO, etc.) for the terminal supporting the access network slice. The terminal supporting the access network slice can send Msg1 or MsgA on the RACH resource configured by the access network device, and correspondingly, the access network device can receive Msg1 or MsgA on the RACH resource, and can know that the terminal is the terminal supporting the access network slice according to the RACH resource.
It should be understood that the first type of terminal and the second type of terminal are introduced in the embodiment of the present application to more clearly illustrate the technical solutions in the embodiment of the present application, and do not limit the technical solutions provided in the embodiment of the present application, and may include other types of terminals besides the above types of terminals. For example, as can be known by those of ordinary skill in the art, with the evolution of a network architecture and the occurrence of a new service scenario, for Msg1 initiated by other new types of terminals, the technical solution provided in the embodiment of the present application may still use the RA-RNTI obtained according to the above formula (1) to scramble the DCI of the response message corresponding to the scheduling Msg1, or may also obtain the RA-RNTI according to a new calculation formula obtained by adding an offset, and scramble the DCI of the response message corresponding to the scheduling Msg1 using the obtained RA-RNTI. It is to be understood that with the evolution of network architecture and the emergence of new service scenarios, terminals that appear to support one or more new capabilities (functions or features) may be understood as a first class of terminals in the embodiments of the present application, while existing terminals that do not support new capabilities may be understood as a second class of terminals in the embodiments of the present application.
Step 702: and the access network equipment sends the first DCI to the first terminal according to the first message. Correspondingly, the first terminal receives the first DCI from the access network equipment.
Further optionally, the access network device sends a response message corresponding to the first message on the time-frequency resource location indicated by the first DCI. Correspondingly, the first terminal determines the RNTI according to the first RO, descrambles the first DCI according to the RNTI, and receives a response message corresponding to the first message according to the time-frequency resource position indicated by the first DCI after the first DCI is descrambled successfully. When the first message is Msg1, the response message corresponding to the first message may be Msg2. When the first message is MsgA, the response message corresponding to the first message may be MsgB.
Further optionally, if the response message corresponding to the first message is Msg2, the method further includes: the first terminal sends Msg3 carrying uplink data to the access network equipment, and the access network equipment receives the Msg3 and sends Msg4 to the first terminal.
The first DCI may be used to schedule a response message corresponding to the first message. The first DCI may indicate a time-frequency resource location of a response message corresponding to the first message. The first DCI is scrambled by using RNTI, and an association relationship exists between the RNTI and the first RO. It should be understood that when the first message is Msg1, the RNTI scrambling the first DCI may be an RA-RNTI. When the first message is MsgA, the RNTI that scrambles the first DCI may be MsgB-RNTI.
In this embodiment of the present application, the RNTI of the first DCI scrambled by the first terminal may be calculated according to formula (1)/formula (2), or may be calculated according to formula (3)/formula (4). For example, in a scenario where the first type of terminal and the second type of terminal share an RO, if the access network device desires that the first type of terminal and the second type of terminal share DCI scrambled by the same RNTI and share an RAR scheduled by the same DCI, no instruction is sent to the first terminal, and the first terminal is calculated by using formula (1)/formula (2) by default to obtain the RNTI, or the access network device may instruct the first terminal to calculate the RNTI by using a calculation formula (such as formula (1)/formula (2)) corresponding to the second type of terminal. If the access network equipment wants the first type terminal and the second type terminal to respectively use different DCI scheduling RARs, and does not want the first type terminal and the second type terminal to share the DCI scrambled by the same RNTI, the first terminal is indicated to calculate by adopting a calculation formula (3)/formula (4)) corresponding to the first type terminal to obtain the RNTI.
It should be understood that the calculation formula corresponding to the second type of terminal described in the present application may refer to an RNTI calculation formula that is default or pre-configured to the second type of terminal. Instructing the first terminal to calculate the RNTI by using a calculation formula (such as formula (1)/formula (2)) corresponding to the second type of terminal may include: and when the first message is the Msg1, indicating the first terminal to calculate the RA-RNTI by adopting the formula (1) described above. And when the first message is MsgB, indicating the first terminal to calculate the MsgB-RNTI by adopting the formula (2) above. Therefore, the first class terminal and the second class terminal can use the same RNTI calculation formula, for example, both use formula (1) or formula (2) to calculate the RNTI corresponding to the RA mode, and it is ensured that the RNTIs calculated by the first class terminal and the second class terminal are the same, and the DCI obtained by scrambling using the RNTI is also the same and is the same DCI when the parameters of the random access resources of the first class terminal and the second class terminal for sending preamble are the same, and the DCI can be used for scheduling the RAR of the first class terminal and the RAR of the second class terminal, that is, the RAR of the multiple classes terminal is carried in the same PDSCH scheduled by the same DCI, thereby realizing the sharing of the DCI and the RAR of the multiple classes terminal, and reducing signaling overhead.
Taking fig. 4b as an example, assume that both the non-redcap terminal and the redcap terminal send preamble in RO a, assuming s _ id =10, t \ u id =40, ul \ u carrier \ u id =0. For non-redcap terminals and redcap terminals, f _ id =0. After the access network equipment receives Msg1 sent by a redcap terminal and a non-redcap terminal on a shared RO, if the access network equipment wants to use RAR scheduled by the same DCI to feed back two types of terminals, the access network equipment calculates, using formula (1), RA-RNTI =1+ s \ id +14 × t _ id +14 × 80 × f _ id +14 × 80 × 8 × ul _ carrier _ id =1+10+14 × 40+14 × 80 × 0+ 571 of the two types of terminals, obtaining the same RA-RNTI, scrambling by using the RA-RNTI to obtain a DCI, wherein the DCI can schedule a PDSCH, and the PDSCH can carry RARs of a redcap terminal and RARs of non-redcap terminals, namely, one DCI can schedule RARs of the redcap terminal and the non-redcap terminal, so that signaling overhead is reduced. And meanwhile, the access network equipment indicates the redcap terminal to calculate the RA-RNTI by using the formula (1), or the redcap terminal calculates the RA-RNTI by default using the formula (1), and DCI is received according to the calculated RA-RNTI. If the access network device wishes to use the RAR scheduled by different DCI for feedback on two types of terminals, it indicates that redcap terminal calculates using formula (3) to obtain RA-RNTI =1+ s \ u id +14 × t _ id +14 × 80 × f _ id +14 × 80 × ul _ carrier _ id + M =1+10+14 × 40+14 × 80 × 0+14 × 80 × 8 × 0+35840=36411, and thus RA-RNTI calculated by redcap terminal is different from RA-RNTI calculated by non-redcap terminal. Therefore, the two types of terminals receive different DCIs, and Msg2 feedback is carried out by using RARs scheduled by the two different DCIs.
Further, in order to distinguish which RAR is the RAR of the first-class terminal and which is the RAR of the non-redcap terminal among the RARs scheduled by the same DCI. In one possible design, which RAR is sent to which terminal may be distinguished by assigning preambles to different types of terminals. For example, different preambles are allocated to the first class of terminals (e.g., redcap) and the second class of terminals (e.g., non-redcap) in advance. One preamble corresponds to one number, which may be understood as a Random Access Preamble Identifier (RAPID) (which may be abbreviated as RPID), and the identifier of the preamble may be used to identify/identify the preamble, and the terminal may distinguish whether the terminal is an RAR of itself through a field corresponding to the preamble carried in the RAR.
For example, taking the response message as a MAC RAR as an example, a format of the MAC RAR corresponding to Msg1 initiated by multiple terminals is shown in fig. 8, and it can be seen that the MAC RAR may include RARs for multiple terminals, for example, in the MAC load (payload) in fig. 8, n MAC RARs are included, where n is an integer greater than or equal to 1. In order to distinguish which terminal each RAR belongs to, a field of "RPID" is included in a MAC subheader (subheader) of each RAR, and this field corresponds to the number of the preamble. For example, a terminal uses a preamble with the number 5 when sending Msg1, and after the terminal receives a PDSCH carrying MAC RARs with the format shown in fig. 8 according to DCI, the terminal may check the RPID field in each RAR in the MAC RAR, and if the RPID field of one RAR is the same as the number 5 of the preamble sent by itself, it means that this RAR may be sent to itself.
The following describes a process in which the access network device indicates the first terminal to calculate the RNTI by using a calculation formula (such as formula (1)/formula (2)) corresponding to the second type of terminal:
and (1.1) directly indicating the first terminal to calculate by adopting a calculation formula corresponding to the second type of terminal to obtain the RNTI. For example, when the access network device desires that the first class terminal and the second class terminal share DCI scrambled by the same RNTI and share RAR scheduled by the same DCI, the access network device may send information a to the first terminal, where the information a indicates that the first terminal obtains the RNTI through calculation using a calculation formula (1) or formula (2)) corresponding to the second class terminal.
The information a may be carried in a higher layer signaling, such as a Radio Resource Control (RRC) message, or may also be carried in a media access control unit (MAC CE), where the information a indicates that the first terminal calculates the RNTI by using a calculation formula corresponding to the second type of terminal may include the following several ways:
in a possible design, the information a includes an index of a calculation formula corresponding to the second type of terminal, that is, the calculation formula corresponding to the second type of terminal is directly used.
For example, the index corresponding to formula (1) is 1, the index corresponding to formula (2) is 2, the index corresponding to formula (3) is 3, and the index corresponding to formula (4) is 4. When the first message is Msg1, if the information a carries an index 1 corresponding to the formula (1), indicating the first terminal to calculate by using the formula (1) to obtain an RA-RNTI; and if the information a carries the index 3, the RA-RNTI is obtained by calculation by using the formula (3). When the first message is Msg2, if the information a carries an index 2 corresponding to the formula (2), indicating the first terminal to calculate by using the formula (2) to obtain MsgB-RNTI; and if the information a carries the index 4, indicating that the MsgB-RNTI is calculated by using the formula (4).
In another possible design method, the information a includes RO configuration information of the first type of terminal, and the first terminal is instructed to calculate the RNTI by using a calculation formula corresponding to the second type of terminal according to a value of an RO parameter included in the RO configuration information.
The RO configuration information may include RO parameters such as a starting frequency domain position of the RO resource, a frequency division multiplexing coefficient of the RO, and a time domain position of the RO, and may further include a correspondence between the RO and the SSB (for example, the number of SSBs (SSBs per RO) corresponding to one RO), a bandwidth of one RO, and the like. The starting frequency-domain position of the RO resource may refer to an offset amount between a RO ranked at the lowest frequency in the RO resource (which may be referred to as a starting RO) and a starting frequency of an initial BWP for the class of terminal. The frequency division multiplexing coefficient of the RO may refer to the number of ROs configured on different frequency domain units corresponding to the same time unit, such as a slot (slot). The time domain location of the RO may refer to a time resource location occupied by the RO during one transmission period.
For example, when the frequency division multiplexing coefficient of the RO is a preset value, for example, 4, the first terminal is instructed to calculate to obtain the RNTI by using a calculation formula corresponding to the second type of terminal. And when the frequency division multiplexing coefficient of the RO is other values, indicating the first terminal not to adopt a calculation formula corresponding to the second type terminal to calculate to obtain the RNTI, and calculating to obtain the RNTI by using a formula (3)/a formula (4).
In another possible design, the information a includes BWP configuration information of the first class of terminal, and the first terminal is instructed to calculate the RNTI by using a calculation formula corresponding to the second class of terminal according to a value of the BWP parameter included in the BWP configuration information.
The BWP configuration information may include bandwidth size, starting frequency domain position, and other BWP parameters of the initial BWP, and may further include subcarrier spacing (SCS) of the initial BWP (which may be referred to as BWP SCS for short). The start frequency domain position may refer to an offset of a start frequency domain (or a frequency domain unit with the lowest frequency) of the initial BWP from a start frequency domain of the system bandwidth, and the offset may be an integer greater than or equal to 0. The starting frequency domain of the system bandwidth may refer to a frequency domain unit with the lowest frequency in the system bandwidth, optionally, the starting frequency domain of the system bandwidth is the frequency domain unit numbered 0, and the starting frequency domain position of the system bandwidth is 0PRB.
For example, when the initial frequency domain position in the BWP configuration information is 0PRB, that is, the initial frequency domain of the initial BWP is the same as the initial frequency domain position of the system bandwidth, the first terminal is instructed to calculate to obtain the RNTI by using the calculation formula corresponding to the second class of terminal. And when the initial frequency domain position in the BWP configuration information is other values, indicating the first terminal not to adopt a calculation formula corresponding to the second type terminal to calculate to obtain the RNTI, and calculating by using a formula (3)/a formula (4) in a default manner to obtain the RNTI.
It should be understood that, in the embodiment of the present application, the initial BWP and RO resources are configured with the terminal type as granularity. For a first terminal belonging to a first class terminal, the BWP configuration information and the RO configuration information of the first terminal correspond to the first class terminal, and the BWP configuration information and the RO configuration information may be sent to the first terminal in a system message corresponding to the first class terminal. For example, before performing S701, the access network device may send a system message to the first terminal, where the system message may carry BWP configuration information of the first class terminal and RO configuration information of an RO resource allocated to the first class terminal. Alternatively, the RO configuration information may be carried in the BWP configuration information.
In still another possible design, the first random access resource is included in a shared RO corresponding to a calculation formula (1)/formula (2)) corresponding to the second type of terminal, and in this case, the information a may include indication information indicating the shared RO.
In one example, a binary bit may be used to indicate that all RO resources of the first terminal are shared ROs or that all RO resources are non-shared ROs. For example, a binary bit "1" may indicate that all RO resources of the first terminal are shared ROs, and a binary bit "0" may indicate that all RO resources of the first terminal are non-shared ROs. When the information a carries a binary bit "1", it indicates that all RO resources of the first terminal are shared ROs, and when the first terminal initiates an RA in all RO resources, the first terminal calculates by using a calculation formula (1)/formula (2)) corresponding to the second class of terminals to obtain the RNTI.
In yet another example, the RO resource of the first terminal corresponds to a mask (mask), which may be referred to as an RO mask. The mask comprises S bits, S is equal to the frequency division multiplexing coefficient of the first terminal, i.e. the mask may be a bitmap, the mask comprises a bit corresponding to an RO of the first terminal, the bit is used to indicate whether the RO corresponding to the bit is a shared RO, and the value of the bit may be "1" or "0".
Taking "1" to indicate that the RO is a shared RO and "0" to indicate that the RO is a non-shared RO as an example, for example, the frequency reuse factor of the first terminal is 4, that is, 4 ROs are included, and then the information a may include a mask: 0011, where the first bit corresponds to the lowest frequency RO, the second bit corresponds to the second lowest frequency RO, and so on. Thus, the mask 0011 represents that two ROs with lower frequency domain numbers are not shared, and the RNTI is calculated by using formula (3)/formula (4), while two ROs with higher frequency domain numbers are shared, and the RNTI is calculated by using formula (1)/formula (2).
It should be understood that the message names or the parameter names in the messages in the embodiments of the present application are only examples, and other names may also be used in specific implementations, and are not limited. Such as information a, may also be described as first information, second information, and so on.
And (1.2) indicating the offset (such as offset _2 in formula 3 or offset _3 in formula 4) in the calculation formula corresponding to the first class terminal to the first terminal through the information b, wherein the offset is zero. That is, the first class terminal is default or preconfigured to calculate the RNTI using the formula (3) or the formula (4), except that for the offset in the formula (3) or the formula (4), the default or preconfigured integer larger than 1 is no longer used, but the offset is indicated to be zero, which is equivalent to calculating the RNTI using the formula (1) or the formula (2).
It should be understood that the calculation formula corresponding to the first class terminal described in the present application may refer to an RNTI calculation formula (3) or formula (4)) which is default or pre-configured to the first class terminal. For example, the formula of the calculation default or pre-configured to the first type of terminal is formula (3) corresponding to the 4-step RA of the first type of terminal. For a 2-step RA for a second class of terminals, the calculation formula default or pre-configured to the first class of terminals is formula (4).
The information b may be carried in higher layer signaling, such as RRC message, and may also be carried in MAC CE. The information b indicating that the offset is zero may include the following ways:
in one possible embodiment, the information b includes an offset, i.e. a numerical value directly indicating the offset.
In another possible design method, the information b includes RO configuration information of the first type terminal, and the offset is indicated to be zero by a value of an RO parameter included in the RO configuration information. For example, when the RO parameter included in the RO configuration information takes a first value, the offset is zero.
Wherein the first value may be preconfigured, without limitation. As described above, the RO configuration information may include RO parameters such as a start frequency domain location of the RO resource, a frequency division multiplexing coefficient of the RO, a time domain location of the RO, and the like. Illustratively, when the frequency division multiplexing coefficient of the RO is a preset value, for example, 4, the offset is indicated to be zero. When the frequency division multiplexing coefficient of the RO is other value, it indicates that the offset is other value, such as an integer greater than 1 which is default/preconfigured.
In another possible design, the information b includes BWP configuration information of the first type terminal, and the bias is indicated to be zero by a value of a BWP parameter included in the BWP configuration information. For example, when the BWP configuration information includes the BWP parameter that takes the value of the second value, the offset is zero.
Wherein the second value may be preconfigured, without limitation. As described above, the BWP configuration information may include BWP parameters such as bandwidth size, starting frequency domain position, etc. of the initial BWP. Illustratively, when the starting frequency-domain position in the BWP configuration information is 0PRB, i.e. the starting frequency-domain of the initial BWP is the same as the starting frequency-domain position of the system bandwidth, the offset is indicated to be zero. For example, when the starting frequency-domain position in the BWP configuration information is 0PRB, which is another value, the offset is indicated to be another value, such as an integer greater than 1 for default/pre-configuration.
In yet another possible design, the first RO is included in a shared RO, the shared RO corresponds to an offset of zero, and the information b includes indication information indicating the shared RO.
In one example, a binary bit may be used to indicate that all RO resources of the first terminal are shared ROs or that all RO resources are non-shared ROs. For example, a binary bit "1" may indicate that all RO resources of the first terminal are shared ROs, and a binary bit "0" may indicate that all RO resources of the first terminal are non-shared ROs. When the information b carries a binary bit "1", it indicates that all RO resources of the first terminal are shared ROs, and when the first terminal initiates an RA in all RO resources, the offset used in calculating the RNTI is zero.
In yet another example, the RO resource of the first terminal corresponds to a mask, which may be referred to as an RO mask. The mask comprises S bits, S is equal to the frequency division multiplexing coefficient of the first terminal, i.e. the mask may be a bitmap, the mask comprises a bit corresponding to an RO of the first terminal, the bit is used to indicate whether the RO corresponding to the bit is a shared RO, and the value of the bit may be "1" or "0".
Taking "1" to indicate that RO is shared RO and "0" to indicate that RO is non-shared RO as an example, for example, the frequency reuse factor of the first terminal is 4, that is, 4 ROs are included, in this case, the information b may include a mask 0011, where the first bit corresponds to the RO with the lowest frequency, the second bit corresponds to the RO with the second lowest frequency, and so on. In this way, mask 0011 represents that two ROs with lower frequency domain numbers do not share, and RNTI is calculated by using a default/preconfigured offset larger than 1, while two ROs with higher frequency domain numbers share, and the offset used in calculating RNTI is zero.
It should be understood that the message names or the parameter names in the messages in the embodiments of the present application are only examples, and other names may also be used in specific implementations, which are not limited. Such as information b, may also be described as first information, second information, and so on.
In a possible application scenario, although a first type of terminal and a second type of terminal share the same RO, a parameter of the shared RO corresponding to the first type of terminal is different from a parameter of the shared RO corresponding to the second type of terminal, so that after the two types of terminals initiate random access on the shared RO, RNTI obtained through calculation according to the parameter of the shared RO and a same calculation formula are different, and it is impossible to implement RAR scheduling for the two types of terminals based on DCI scrambled by the same RNTI.
Taking the first type of terminal as a redcap terminal and the second type of terminal as a non-redcap terminal as an example, as shown in fig. 9, for example, the access network device configures BWP of the non-redcap terminal and BWP of the redcap terminal respectively. The starting frequency domain position of configuring the RO in the BWP system message of the non-redcap terminal is 12PRB, and the frequency division multiplexing coefficient is 8. The starting frequency domain position where RO is configured in the BWP system message of the redcap terminal is 5PRB (the redcap terminal uses only RO e to RO h), and the frequency division multiplexing coefficient is 4. The non-redcap terminal occupies RO a to RO h, the redcap terminal occupies RO e to RO h, and the redcap terminal shares the 4 ROs with higher frequency in the non-redcap terminal: RO e to RO h. When the index values f _ id of the ROs are numbered sequentially from 0, the index values f _ id of the 4 ROs shared by the redcap terminals, i.e., the RO e to the RO h, are [0,3], the index values of the RO e to the RO h occupied by the non-redcap terminals are [4,7], and the values of f _ id corresponding to the same RO are different for the two types of terminals. For example, the RO e occupied by the redcap terminal corresponds to f _ id =0, and the RO e occupied by the non-redcap terminal corresponds to f _ id =4. If the redcap terminal and the non-redcap terminal send Msg1 on the RO e, even if the non-redcap terminal and the redcap terminal realize the calculation of RA-RNTI based on the formula (1) by the above mode, the calculated RA-RNTI is different because the f _ id of the RO e is different, and the feedback of RAR scheduled by the same DCI by the redcap terminal and the non-redcap terminal can not be realized.
In order to solve the problem that RNTIs calculated by a first class of terminal and a second class of terminal based on a parameter of shared RO are different, an embodiment of the present application provides a method: and the access network equipment indicates the offset of the parameter of the first RO to the first terminal through the information c, and the first terminal calculates the RNTI according to the parameter of the first RO and the offset of the parameter of the first RO after receiving the information c.
In this embodiment, the parameter of the first RO may include at least f _ id, and may further include at least one of s _ id, t _ id, and ul _ carrier _ id. The relevant descriptions of s _ id, t _ id, f _ id, ul _ carrier _ id are as described above, and are not repeated herein. The offset of the parameter of the first RO may be used to adjust a value (or referred to as an initial value) of a first random access parameter, so that the adjusted value of the parameter of the first RO of the first terminal is the same as/aligned with the value (or referred to as an initial value) of the parameter of the first RO corresponding to the second type of terminal, and after the random access is initiated on the first RO, RNTIs calculated based on the same calculation formula are the same, thereby implementing RAR scheduling for different types of terminals based on the same DCI.
In this embodiment, the value of the parameter of the first RO may be understood as an initial value of the parameter of the first RO. The adjusted value of the parameter of the first RO may refer to a value obtained by adjusting the initial value of the parameter of the RO by using the offset of the parameter. Illustratively, the adjusted value of the parameter of the first RO = the value of the parameter of the first RO + the offset of the parameter. It should be understood that the manner of determining the adjustment value of the parameter described in this application is only an exemplary illustration, and optionally, when the offset of the parameter is a negative number smaller than 0, the adjustment value of the parameter of the first RO = the value of the parameter of the first RO — the offset of the parameter, that is, any technical means that the adjustment value of the parameter of the first RO of the first terminal is the same as the value of the parameter of the first RO corresponding to the second type of terminal is within the protection scope of this application.
For example, the value of s _ id of the first RO is an index value of a symbol occupied by the first RO in a time slot, and the adjusted value of s _ id of the first RO = the value of s _ id of the first RO + the offset of s _ id. The value of t _ id of the first RO is an index value of a time slot occupied by the first RO in a system frame, and the adjusted value of t _ id of the first RO = the value of t _ id of the first RO + the offset of t _ id. The value of f _ id of the first RO is an index value of the frequency domain unit occupied by the first RO in Nf frequency domain units, and the adjustment value of f _ id of the first RO = the value of f _ id of the first RO + the offset of f _ id. The ul _ carrier _ id of the first RO is taken as an index value of the uplink carrier occupied by the first RO in Nc uplink carriers, and the adjustment value of the ul _ carrier _ id of the first RO = the value of the ul _ carrier _ id of the first RO + the offset of the ul _ carrier _ id.
In this embodiment, the obtaining, by the first terminal, the RNTI calculated according to the parameter of the first RO and the offset of the parameter of the first RO may include: and adding the offset to the value of the parameter of the first RO to obtain an adjusted value of the parameter of the first RO, and calculating to obtain the RNTI according to the adjusted value of the parameter of the first RO. For example, when the first message is Msg1, that is, when a 4-step RA is initiated, the RA-RNTI is obtained based on the formula (1) and the adjustment value of the parameter of the first RO. And when the first message is MsgA, namely 2-step RA is initiated, obtaining MsgB-RNTI based on the formula (2) and the adjustment value of the parameter of the first RO.
Taking the same time domain position of the RO shared by the first class terminal and the second class terminal, different values of the frequency domain index f _ id, and adjusting the value of f _ id as an example, assuming that the offset of the parameters is Δ and Δ is an integer greater than or equal to 0, when the first message is Msg1, i.e. a 4-step RA is initiated, referring to the above formula (1), the RA-RNTI calculated by the first terminal according to the parameter of the first RO and the offset of the parameter of the first RO satisfies the following formula:
RA-RNTI =1+ s _id + Nsymbol + t _id + Nsymbol + Nslot (f _ id +. Delta) + Nsymbol + Nslot _ Nf _ ul _ carrier _ id; the value ranges of s _ id, t _ id, f _ id and ul _ carrier _ id are the same as those in the formula (1); or,
RA-RNTI =1+ s _id + Nsymbol + t _id + Nsymbol + Nslot + f _id + Nsymbol + Nslot _ Nf ul _ carrier _ id, f _ id' = f _ id +. Delta; the value ranges of s _ id, t _ id, f _ id and ul _ carrier _ id are the same as those in the formula (1); or,
RA-RNTI =1+ s _id + Nsymbol + t _id + Nsymbol + Nslot f _id + Nsymbol + Nslot _ Nf ul _ carrier _ id, s _ id, t _ id and ul _ carrier _ id have the same value range as in formula (1), the value range of f _ id' is [ f _ id + delta, nf-1], and the value range of f _ id is [0, nf-1].
Similarly, taking the same time domain position of the RO shared by the first type terminal and the second type terminal, different values of the frequency domain index f _ id, and adjusting the value of f _ id as an example, assuming that the offset of the parameter is Δ, and Δ is an integer greater than or equal to 0, when the first message is MsgA, that is, when a 2-step RA is initiated, referring to the above formula (2), the MsgB-RNTI calculated by the first terminal according to the parameter of the first RO and the offset of the parameter of the first RO satisfies the following formula:
MsgB-RNTI =1+ s + u id + Nsymbol + t + u id + Nsymbol + Nslot (f _ id + delta) + Nsymbol + Nslot + Nf ul _ carrier _ id + offset _1; the value ranges of s _ id, t _ id, f _ id, ul _ carrier _ id and offset _1 are the same as those in the formula (2); or,
MsgB-RNTI =1+ s _id + Nsymbol + t _id + Nsymbol + Nslot + f _id + Nsymbol + Nslot + Nf ul _ carrier _ id + offset amount _1, f _id' = f _ id +; the value ranges of s _ id, t _ id, f _ id, ul _ carrier _ id and offset _1 are the same as those in the formula (2); or,
MsgB-RNTI =1 s _id + Nsymbol + t _id + Nsymbol + Nslot + f _id + Nsymbol + Nslot + offset amount _1, the value ranges of s _id, t _ id, ul _ carrier _ id and offset amount _1 are the same as those in formula (2), the value range of f _ id' is [ f _ id +. Delta, nf-1], and the value range of f _ id is [0, nf-1].
Taking fig. 9 as an example, the redcap terminal shares the higher frequency 4 ROs in the non-redcap terminal: RO e to RO h. In the case of sequentially numbering the index values f _ id of the ROs from 0, the access network device may indicate the redcap terminal that the offset Δ =4 of the f _ id, and at this time, the index values f _ id of the 4 ROs shared by the redcap terminal are adjusted to [4,7], which is the same as the index values [4,7] of the ROs e to RO h occupied by the non-redcap terminal. If the redcap terminal and the non-redcap terminal send Msg1 on RO e, the redcap terminal calculates RA-RNTI based on RA-RNTI =1+ s + u id + Nsymbol t + u id + Nsymbol Nslot (f _ id + delta) + Nsymbol Nslot Nf ul _ carrier _ id to obtain the same RA-RNTI calculated by the non-redcap terminal based on the formula (1), and the redcap terminal and the non-redcap terminal can feed back by using the RAR with the same DCI scheduling, so that the signaling overhead is saved.
It should be noted that the offset of f _ id may be set to be greater than or equal to 0 and smaller than the maximum frequency division multiplexing coefficient Nf. For example, if the offset of f _ id is Δ, if Nf =8, 8 >. DELTA.0. If Nf =4, 4 >. DELTA.gtoreq.0.
The information c may be carried in a higher layer signaling, such as an RRC message, may also be carried in a MAC CE, and may also be carried in RO configuration information of the first terminal. The manner in which the information c indicates the offset of the parameter of the first RO may include any of the following possible design manners:
in one possible design, the information c includes an offset of the parameter of the first RO, i.e., a numerical value directly indicating the offset of the parameter of the first RO.
In yet another possible design method, the information c includes RO configuration information of the second type terminal. The RO configuration information of the second type terminal is used to indicate the RO time domain position, the frequency division multiplexing coefficient, and the starting frequency domain position of the second type terminal. And the first terminal acquires the RO configuration information of the second type terminal from the information c, and the first terminal calculates the offset of the parameter according to the RO configuration information of the second type terminal.
In an example, taking the parameter f _ id as an example, the calculating, by the first terminal, the offset of the parameter f _ id according to the RO configuration information of the second type terminal may include: and calculating the offset of f _ id according to the RO configuration information of the first type of terminal and the RO configuration information of the second type of terminal. For example, the frequency domain position of the RO allocated to the first class terminal is determined according to the RO configuration information of the first class terminal, the frequency domain position of the RO allocated to the second class terminal is determined according to the RO configuration information of the second class terminal, the overlapping frequency domain position of the RO allocated to the first class terminal and the frequency domain position of the RO allocated to the second class terminal is determined as the RO shared by the first class terminal and the second class terminal (may be simply referred to as a shared RO), and an offset of f _ id is obtained according to the frequency domain interval between the start RO in the shared RO and the start RO in the RO resource of the second class terminal, where the offset of f _ id = the frequency domain position of the start RO of the second class terminal minus the position of the start frequency domain RO in the shared RO. In this manner, the offset amount of f _ id can be determined according to the frequency domain location allocated to the RO used by the second type terminal and the frequency domain location allocated to the RO used by the first type terminal.
Wherein, the RO configuration information of the first terminal can be carried in the system message and configured to the first terminal. Specifically, the description of the RO configuration information of the first terminal is as described above, and is not repeated.
For example, taking fig. 9 as an example, the RO configuration information of the non-redcap terminal and the redcap terminal is as shown in the following table a, the access network device configures an initial BWP with a bandwidth of 40 megahertz (MHz) (corresponding to 106 PRBs) for the non-redcap terminal, on which the RO with a frequency division multiplexing coefficient of 8 is configured, and the starting RO of the non-redcap terminal is located at 12 PRBs (frequency domain position of the starting RO of the non-redcap terminal relative to the starting RO of the initial BWP of the non-redcap terminal). For the redcap terminal, the access network device configures the initial BWP with 20MHz (equivalent to 51 PRB) bandwidth, and the RO configuration information of the redcap terminal includes the frequency division multiplexing coefficient =8, and the starting RO is located in-43 PRB (frequency domain position of the starting RO of the 8 ROs relative to the starting RO of the initial BWP of the redcap terminal), which means that the 8 ROs are outside the initial BWP of the redcap terminal. If it is specified that the redcap terminal can use only the ROs that are within the initial BWP of the redcap terminal, the redcap terminal can calculate from table one that only the 4 ROs (RO e to RO h) with higher frequency are within the initial BWP of the redcap terminal and can be used by the redcap terminal, i.e. the starting RO that the redcap terminal can use corresponds to the 5th RO that the non-redcap terminal can use, and the offset of f _ id is set to 4.
Watch 1
In another example, taking the parameter f _ id as an example, the calculating, by the first terminal, the offset of the parameter f _ id according to the RO configuration information of the second class of terminals may include: and calculating the offset of f _ id according to the BWP configuration information of the first type terminal and the RO configuration information of the second type terminal. For example, the frequency domain position of the RO allocated to the second type terminal is determined according to the RO configuration information of the second type terminal, the frequency domain position (or frequency domain range) of the initial BWP of the first type terminal is determined according to the BWP configuration information of the first type terminal, if the frequency domain position of the part of RO allocated to the second type terminal is located in the initial BWP of the first type terminal, the part of RO is determined as the RO shared by the first type terminal and the second type terminal (may be simply referred to as shared RO), and an offset of f _ id is obtained according to the frequency domain interval between the start RO in the shared RO and the start RO in the RO resource of the second type terminal, for example, the offset of f _ id = the frequency domain position of the start RO of the second type terminal minus the frequency domain position of the start RO in the shared RO. That is, the offset of f _ id is determined according to the frequency domain position of the RO allocated to the second type terminal and the frequency domain position of the initial BWP allocated to the first type terminal.
Wherein the BWP configuration information of the first class of terminals may be used to indicate the bandwidth size, the starting frequency domain position, etc. of the initial BWP of the first class of terminals. The BWP configuration information of the first type of terminal may be carried in a system message configured to the first terminal. Specifically, the description of the BWP configuration information of the first type terminal is as described above and is not repeated herein.
For example, as shown in fig. 9, the message c may include RO configuration information of the non-redcap terminal: the frequency multiplexing coefficient 8, the starting frequency-domain position 12PRB, the time-domain position, and the like of the RO, and 8 ROs (RO a to RO h) are included in the same time-domain position, and in fig. 9, the starting frequency-domain position of the initial BWP of the redcap terminal is 55PRB, and the width of the initial BWP is 51 PRB. At this time, the redcap terminal may calculate that the ROs a-d are not within the initial BWP range of the redcap terminal and cannot be used by the redcap terminal, and the ROs e-RO h are within the initial BWP range of the redcap terminal and can be used or shared. Since the lower 4 ROs cannot be used, only the higher 4 ROs (RO e to RO h) can be used by the redcap terminal, i.e. the starting RO that can be used by the redcap terminal corresponds to the 5th RO that can be used by the non-redcap terminal, and the offset of f _ id is set to 4.
In yet another possible design, the first RO is included in a shared RO, and the information c includes first indication information. The first indication information is used for indicating the RO set and the shared RO in the RO set. The first terminal may derive an offset of f _ id from a frequency domain interval between a starting RO of the shared ROs and a starting RO of the set of ROs.
Wherein the RO set may be a set of ROs assigned to the second type of terminal for use, and the RO set may include one or more ROs. The shared RO in the RO set may refer to an RO assigned to a terminal of the first type and a terminal of the second type for common use.
In one example, the RO set corresponds to a mask, which may be referred to as a RO mask. The mask comprises S bits, S is equal to the frequency division multiplexing coefficient, i.e. the mask may be a bit map, the mask comprises a bit corresponding to one RO in the set of ROs, the bit is used to indicate whether the RO corresponding to the bit is shared, and the value of the bit may be "1" or "0".
Taking "1" indicating that RO is shared RO and "0" indicating that RO is unshared RO as an example, as an example in fig. 9, the frequency multiplexing coefficient is 8, and 8 ROs (RO a to RO h) are included in the same time domain position, where information c may include a mask: 00001111 where the first bit corresponds to the lowest frequency RO, the second bit corresponds to the second lowest frequency RO, and so on. Thus, the mask 00001111 represents that the 4 ROs with lower frequency domain numbers are not shared, the 4 ROs with higher frequency numbers are shared, and the offset of f _ id is set to 4.
It should be understood that the message names or the parameter names in the messages in the embodiments of the present application are only examples, and other names may also be used in specific implementations, which are not limited. Such as information c, may also be described as first information, second information, and so on.
The above-mentioned scheme provided by the embodiments of the present application is mainly introduced from the perspective of interaction between the nodes. It is understood that each node, for example, a terminal, a network device, in order to implement the above functions, includes a corresponding hardware structure and/or software module for performing each function. Those of skill in the art will readily appreciate that the present application is capable of hardware or a combination of hardware and computer software implementing the various illustrative algorithm steps described in connection with the embodiments disclosed herein. Whether a function is performed as hardware or computer software drives hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiment of the present application, the first device and the second device may be divided into the functional modules according to the above method examples, for example, each functional module may be divided corresponding to each function, or two or more functions may be integrated into one processing module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. It should be noted that, in the embodiment of the present application, the division of the module is schematic, and is only one logic function division, and there may be another division manner in actual implementation.
Fig. 10 shows a block diagram of a communication device 100, the communication device 100 may be a first terminal, or a chip in the first terminal, or a system on chip, and the communication device 100 may be used to perform the functions of the first terminal involved in the above embodiments. As one implementation, the communication apparatus 100 shown in fig. 10 includes: transmitting section 1001, receiving section 1002;
a sending unit 1001 configured to send a first message to an access network device on a first RO. For example, the transmitting unit 1001 may be configured to support the communication apparatus 100 to perform step 701.
A receiving unit 1002, configured to receive a first DCI from an access network device, where the first DCI is used to schedule a response message corresponding to a first message, the first DCI is scrambled using an RNTI, and the RNTI is determined according to a parameter of a first RO and an offset. For example, the receiving unit 1002 may be used to support the communication device 100 to perform step 702.
Specifically, all relevant contents of each step related to the method embodiment shown in fig. 7 may be referred to the functional description of the corresponding functional module, and are not described herein again. The communication apparatus 100 is configured to perform the function of the first terminal in the random access method shown in fig. 7, and thus can achieve the same effect as the random access method described above.
As still another implementation, the communication apparatus 100 shown in fig. 10 includes: a processing module and a communication module. The processing module is used for controlling and managing the actions of the communication device 100, and for example, the processing module may support the communication device 100 to execute a control function. The communication module may integrate the functions of the transmitting unit 1001 and the receiving unit 1002, and may be used to support the communication apparatus 100 to perform the steps 701 and 702 and to communicate with other network entities, for example, the functional module or the network entity shown in fig. 6. The communication device 100 may also include a memory module for storing program codes and data for the communication device 100.
The processing module may be a processor or a controller. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. A processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, a DSP and a microprocessor, or the like. The communication module may be a transceiver circuit or a communication interface, etc. The storage module may be a memory. When the processing module is a processor, the communication module is a communication interface, and the storage module is a memory, the communication device 100 according to the embodiment of the present application may be the communication device 600 shown in fig. 6.
Fig. 11 shows a block diagram of a communication device 110, where the communication device 110 may be an access network device, or a chip in the access network device, or a system on chip, and the communication device 110 may be configured to perform the functions of the access network device in the above embodiments. As one implementation, the communication device 110 shown in fig. 11 includes: a reception unit 1101, a transmission unit 1102;
a receiving unit 1101 for receiving a first message from a first terminal on a first RO. For example, the receiving unit 1101 may support the communication device 110 to perform step 701.
A sending unit 1102, configured to send a first DCI of an access network device to a first terminal, where the first DCI is used to schedule a response message corresponding to a first message, the first DCI is scrambled using an RNTI, and the RNTI is determined according to a parameter of a first RO and an offset. For example, the sending unit 1102 may enable the communication device 110 to perform step 702.
Specifically, all relevant contents of each step related to the method embodiment shown in fig. 7 may be referred to the functional description of the corresponding functional module, and are not described herein again. The communication device 110 is configured to perform the function of the access network equipment in the random access method shown in fig. 7, so that the same effect as the random access method described above can be achieved.
As yet another implementation, the communication device 110 shown in fig. 11 includes: a processing module and a communication module. The processing module is used for controlling and managing the actions of the communication device 110, for example, the processing module may support the communication device 110 to perform management functions. The communication module may integrate the functions of the receiving unit 1101 and the sending unit 1102 and may be used to support the communication device 110 to perform steps 701 and 702 and to communicate with other network entities, such as the functional module or the network entity shown in fig. 6. The communication device 110 may also include a memory module for storing program codes and data for the communication device 110.
The processing module may be a processor or a controller, among others. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. A processor may also be a combination of computing functions, e.g., comprising one or more microprocessors, a DSP and a microprocessor, or the like. The communication module may be a transceiver circuit or a communication interface, etc. The storage module may be a memory. When the processing module is a processor, the communication module is a communication interface, and the storage module is a memory, the communication device 110 according to the embodiment of the present application may be the communication device 600 shown in fig. 6.
Fig. 12 is a block diagram of a communication system according to an embodiment of the present application, and as shown in fig. 12, the communication system may include: terminal 120, access network device 121. The function of the terminal 120 is the same as that of the communication apparatus 100 described above. The access network device 121 has the same function as the communication apparatus 110, and is not described in detail.
The embodiment of the application also provides a computer readable storage medium. All or part of the processes in the above method embodiments may be performed by relevant hardware instructed by a computer program, which may be stored in the above computer-readable storage medium, and when executed, may include the processes in the above method embodiments. The computer readable storage medium may be a terminal of any of the foregoing embodiments, such as: including internal storage units of the data sending end and/or the data receiving end, such as a hard disk or a memory of the terminal. The computer readable storage medium may also be an external storage device of the terminal, such as a plug-in hard disk, a Smart Memory Card (SMC), a Secure Digital (SD) card, a flash memory card (flash card), and the like, which are provided on the terminal. Further, the computer-readable storage medium may include both an internal storage unit and an external storage device of the terminal. The computer-readable storage medium stores the computer program and other programs and data required by the terminal. The above-described computer-readable storage medium may also be used to temporarily store data that has been output or is to be output.
It should be noted that the terms "first" and "second" and the like in the description, claims and drawings of the present application are used for distinguishing different objects and not for describing a particular order. Furthermore, the terms "include" and "have," as well as any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those steps or elements but may alternatively include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.
It should be understood that in the present application, "at least one" means one or more, "a plurality" means two or more, "at least two" means two or three and more, "and/or" is used to describe the association relationship of the associated objects, meaning that there may be three relationships, for example, "a and/or B" may mean: only A, only B and both A and B are present, wherein A and B may be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of single item(s) or plural items. For example, at least one (one) of a, b, or c, may represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", wherein a, b, c may be single or plural.
It should be understood that in the embodiment of the present application, "B corresponding to a" means that B is associated with a. For example, B may be determined from A. It should also be understood that determining B from a does not mean determining B from a alone, but may also be determined from a and/or other information. In addition, the term "connect" in the embodiment of the present application refers to various connection manners such as direct connection or indirect connection, so as to implement communication between devices, which is not limited in this embodiment of the present application.
The "transmission" appearing in the embodiments of the present application refers to a bidirectional transmission, including actions of transmission and/or reception, unless otherwise specified. Specifically, "transmission" in the embodiment of the present application includes transmission of data, reception of data, or both transmission of data and reception of data. Alternatively, the data transmission herein includes uplink and/or downlink data transmission. The data may include channels and/or signals, uplink data transmission, i.e., uplink channel and/or uplink signal transmission, and downlink data transmission, i.e., downlink channel and/or downlink signal transmission. In the embodiments of the present application, "network" and "system" represent the same concept, and a communication system is a communication network.
Through the above description of the embodiments, it is clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions.
In the several embodiments provided in the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described device embodiments are merely illustrative, and for example, the division of the modules or units is only one logical functional division, and there may be other divisions when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another device, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may be one physical unit or multiple physical units, that is, may be located in one place, or may be distributed in multiple different places. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially or partially contributed to by the prior art, or all or part of the technical solutions may be embodied in the form of a software product, where the software product is stored in a storage medium and includes several instructions to enable a device (which may be a single chip, a chip, or the like) or a processor (processor) to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk.
The above description is only an embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.