Communication method, terminal, network device, and storage medium

Abstract

The present disclosure relates to a communication method, a terminal, a network device, and a storage medium. The method comprises: receiving configuration information sent by a network device, wherein the configuration information is used for configuring a random access priority parameter of a first random access channel (RACH) procedure, and the RACH procedure is used by a terminal to request a system information block (SIB) 1 or a synchronization signal block (SSB). In the method of the present disclosure, by receiving configuration information, a terminal can acquire a random access priority parameter which is configured by a network device and used for requesting an SIB1 or an SSB, such that the terminal can request the SIB 1 or the SSB on the basis of the random access priority parameter, thereby reducing the request time delay, and improving the communication efficiency.

Description

Communication method, terminal, network device and storage medium TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of communication, and particularly relates to a communication method, a terminal, a network device and a storage medium. BACKGROUND

[0002] The terminal can request system information (SI) based on a first message (MSG1) of a random access channel (RACH) procedure or based on MSG3, in which the terminal performs the RACH procedure according to configuration parameters of a conventional RACH.

[0003] SUMMARY

[0004] In the above manner in which the terminal requests SI, the terminal request information needs a long time delay.

[0005] Embodiments of the present disclosure provide a communication method, a terminal, a network device and a storage medium.

[0006] In a first aspect, embodiments of the present disclosure provide a communication method, performed by a terminal, the method comprising:

[0007] receiving configuration information, the configuration information being used to configure a random access priority parameter of a first random access channel (RACH) procedure, the first RACH procedure being used for the terminal to request a system information block (SIB1) or a synchronization signal block (SSB).

[0008] In a second aspect, embodiments of the present disclosure provide a communication method, performed by a network device, the method comprising:

[0009] sending configuration information, the configuration information being used to configure a random access priority parameter of a first random access channel (RACH) procedure, the first RACH procedure being used for the terminal to request a system information block (SIB1) or a synchronization signal block (SSB).

[0010] In a third aspect, embodiments of the present disclosure provide a terminal, comprising:

[0011] a transceiver, configured to receive configuration information, the configuration information being used to configure a parameter of a first random access channel (RACH) procedure, the first RACH procedure being used for the terminal to request a system information block (SIB1) or a synchronization signal block (SSB).

[0012] Fourthly, embodiments of this disclosure provide a network device, including:

[0013] The transceiver module is used to send configuration information, which is used to configure the parameters of the first random access channel (RACH) procedure. The first RACH procedure is used by the terminal to request system information block SIB1 or synchronization signal block SSB.

[0014] Fifthly, embodiments of this disclosure provide a terminal, including:

[0015] One or more processors;

[0016] The terminal is configured to implement the method described in the first aspect.

[0017] Sixthly, embodiments of this disclosure provide a network device, including:

[0018] One or more processors;

[0019] The network device is configured to implement the method described in the second aspect.

[0020] In a seventh aspect, embodiments of this disclosure provide a communication system, including a terminal and a network device, wherein,

[0021] The terminal is configured to implement the method described in the first aspect;

[0022] The network device is configured to implement the method described in the second aspect.

[0023] Eighthly, embodiments of this disclosure provide a storage medium storing instructions, wherein...

[0024] When the instructions are executed on the communication device, the communication device causes the communication device to perform the method described in the first aspect or the second aspect.

[0025] Ninthly, embodiments of this disclosure provide a program product, wherein,

[0026] When the program product is executed by a communication device, the communication device performs the method described in the first aspect or the second aspect.

[0027] In this embodiment of the present disclosure, the terminal can obtain the random access priority parameters configured by the network device for requesting the first RACH procedure of SIB1 or SSB by receiving configuration information. Thus, the terminal can request SIB1 or SSB based on the random access priority parameters, thereby reducing request latency and improving communication efficiency. Attached Figure Description

[0028] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following describes the drawings required for the embodiments, and the following drawings are only some embodiments of the present disclosure, and do not specifically limit the protection scope of the present disclosure.

[0029] FIG. 1a is one exemplary schematic diagram of an architecture of a communication system according to an embodiment of the present disclosure;

[0030] FIG. 1b is a schematic diagram of system information according to an embodiment of the present disclosure;

[0031] FIG. 1c to FIG. 1e are multiplexing patterns of SSB and RMSI control resource set according to an embodiment of the present disclosure;

[0032] FIG. 1f is a schematic diagram of SI request according to an embodiment of the present disclosure;

[0033] FIG. 1g is a schematic diagram of network side response in random access procedure;

[0034] FIG. 2a to FIG. 2b are one exemplary interactive schematic diagram of a method according to an embodiment of the present disclosure;

[0035] FIG. 3a to FIG. 3e are one exemplary flowchart of a method according to an embodiment of the present disclosure;

[0036] FIG. 4a to FIG. 4c are another exemplary flowchart of a method according to an embodiment of the present disclosure;

[0037] FIG. 5a is one schematic diagram of a structure of a device according to an embodiment of the present disclosure;

[0038] FIG. 5b is another schematic diagram of a structure of a device according to an embodiment of the present disclosure;

[0039] FIG. 6a is one schematic diagram of a communication device according to an embodiment of the present disclosure;

[0040] FIG. 6b is another schematic diagram of a communication device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0041] The embodiments of the present disclosure provide a communication method, a terminal, a network device and a storage medium.

[0042] In a first aspect, the embodiments of the present disclosure provide a communication method, executed by a terminal, comprising:

[0043] receiving configuration information, the configuration information being used for configuring a random access priority parameter of a first random access channel (RACH) procedure, the first RACH procedure being used for the terminal to request a SIB1 or a SSB.

[0044] In the above embodiments, the terminal can learn the random access priority parameter configured by the network device for requesting the SIB1 or the SSB through receiving the configuration information, so that the terminal can request the SIB1 or the SSB based on the random access priority parameter, reduce the request delay, and improve the communication efficiency.

[0045] In combination with the embodiments of the first aspect, in some embodiments, the random access priority parameter comprises at least one of:

[0046] a power ramping step for uplink transmission in the first RACH procedure;

[0047] a scaling factor of a back-off indicator (BI) for uplink transmission in the first RACH procedure;

[0048] an initial reception power indicated by the network device;

[0049] a maximum number of transmissions of a preamble in the first RACH procedure.

[0050] In the above embodiments, different parameters applicable to the first RACH procedure can be configured in the configuration information to improve the efficiency of the terminal requesting the SIB1 or the SSB.

[0051] In combination with the embodiments of the first aspect, in some embodiments, the random access priority parameter satisfies at least one of:

[0052] the power ramping step is greater than a first value;

[0053] the maximum number of transmissions is less than a second value; the first value is a power ramping step for other RACH procedures than the first RACH procedure, and the second value is a maximum number of transmissions for other RACH procedures than the first RACH procedure.

[0054] In the above embodiments, the configuration information can configure a larger power ramping step to improve the transmission power of the terminal requesting the SIB1 or the SSB, so as to improve the efficiency of requesting the SIB1 or the SSB. Alternatively, the configuration information can configure a smaller maximum number of transmissions to reduce the number of times of requesting the SIB1 or the SSB by the terminal, so that the terminal can replace the candidate cell corresponding to the requested information in time.

[0055] In combination with the embodiments of the first aspect, in some embodiments, the method further comprises:

[0056] requesting the SIB1 or the SSB in the first RACH procedure according to the configuration information.

[0057] In the above embodiments, the terminal can request the SIB1 or the SSB in the RACH procedure of high priority according to the configuration information of the network device, so that the terminal accesses the cell as soon as possible, and the efficiency of the request information is improved.

[0058] In combination with the embodiments of the first aspect, in some embodiments, the first RACH procedure includes:

[0059] sending the first message MSG1;

[0060] receiving the second message MSG2 within a running duration of the first timer.

[0061] In the above embodiments, the terminal can request the SIB1 or the SSB in the 2-step RACH procedure.

[0062] In combination with the embodiments of the first aspect, in some embodiments, the MSG1 is used to request the SIB1 or the SSB, and the MSG2 includes feedback information, which is feedback of the request for the SIB1 or the SSB.

[0063] In the above embodiments, the terminal can request the SIB1 or the SSB based on the MSG1, and request the SIB1 or the SSB faster based on the parameters configured by the configuration information.

[0064] In combination with the embodiments of the first aspect, in some embodiments, the first timer is started after the terminal sends the MSG1, and the running duration of the first timer is less than a third value, and the third value is a running duration of a response timer for other RACH procedures other than the first RACH procedure.

[0065] In the above embodiments, the terminal can receive the feedback of the network device for the request of the SIB1 or the SSB as soon as possible within the running duration of the first timer, so that the efficiency of the request of the SIB1 or the SSB is improved, and the request delay is reduced.

[0066] In combination with the embodiments of the first aspect, in some embodiments, the running duration of the first timer is configured by the network device.

[0067] In the above embodiments, the network device can configure the terminal with the first timer running for a shorter time, so that the network device can feed back to the terminal as soon as possible within a shorter time, and the delay of the request of the SIB1 or the SSB is reduced.

[0068] In combination with the embodiments of the first aspect, in some embodiments, the method further includes:

[0069] The physical downlink control channel (PDCCH) is received according to a radio network temporary identity (RNTI), the PDCCH being used for scheduling the MSG2, wherein the PDCCH is scrambled by the RNTI.

[0070] In the above embodiment, the terminal can obtain the feedback of the network device for the request of the SIB1 or the SSB according to the PDCCH scheduling the MSG2.

[0071] In combination with the embodiments of the first aspect, in some embodiments, the RNTI satisfies one of the following:

[0072] configured by the network device;

[0073] defined by a protocol;

[0074] determined according to a random access (RA) RNTI of the first RACH procedure and a bias configured by the network device.

[0075] In the above embodiment, the network device can scramble the PDCCH scheduling the MSG2 based on the new RNTI, for the high-priority RACH procedure.

[0076] In combination with the embodiments of the first aspect, in some embodiments, the PDCCH is sent in a first search space, wherein the first search space is a search space of remaining minimum system information (RMSI), or a search space configured by the network device for the PDCCH.

[0077] In the above embodiment, the PDCCH can be sent in a separately configured search space or a search space multiplexed with the RMSI.

[0078] In combination with the embodiments of the first aspect, in some embodiments, the first RACH procedure further includes:

[0079] sending a third message (MSG3), the MSG3 being used for requesting the SIB1 or the SSB. In the above embodiment, the terminal can request the SIB1 or the SSB in the 4-step RACH procedure. The terminal can request the SIB1 or the SSB based on the MSG3, and request the SIB1 or the SSB faster based on the parameters configured according to the configuration information.

[0080] In some embodiments of the first aspect, the first RACH procedure further comprises: receiving, within a running time of a second timer, a fourth message MSG4 sent by the network device, the MSG4 comprising feedback information, the feedback information being feedback to the request for the SIB1 or the SSB.

[0081] In some embodiments of the first aspect, the MSG3 comprises at least one of:

[0082] indication information for indicating the request for the SIB1;

[0083] a set of SSB indexes expected by the terminal for sending the SIB1.

[0084] In the above embodiments, when the terminal requests the SIB1 based on the MSG3, the terminal can carry the indication information and / or the set of SSB indexes in the MSG3, so as to obtain feedback from the network device.

[0085] In some embodiments of the first aspect, the second timer is started after the terminal sends the MSG3, and a running time of the second timer is less than a fourth value, the fourth value being a running time of a conflict timer for other RACH procedures than the first RACH procedure.

[0086] In the above embodiments, the terminal can receive feedback from the network device for the request for the SIB1 or the SSB as soon as possible within the running time of the second timer, so as to improve the efficiency of the request for the SIB1 or the SSB and reduce the request delay.

[0087] In some embodiments of the first aspect, the running time of the second timer is configured by the network device.

[0088] In the above embodiments, the network device can configure the terminal with a second timer with a shorter running time, so that the network device can give feedback to the terminal as soon as possible within a shorter time, thereby reducing the delay of the request for the SIB1 or the SSB.

[0089] In some embodiments of the first aspect, the method further comprises:

[0090] receiving the SIB1 or the SSB.

[0091] In the above embodiments, the terminal can receive the SIB1 or the SSB on a suitable time-frequency resource based on the feedback from the network device, so as to complete cell access as soon as possible.

[0092] In some embodiments of the first aspect, the SIB1 or the SSB satisfies at least one of:

[0093] transmitted in a beam sweeping manner in a first SSB index order, wherein the first SSB index is an index of an SSB transmitted by a cell corresponding to the configuration information;

[0094] transmitted based on a second SSB index indicated by the terminal;

[0095] transmitted in an SSB set including the second SSB index.

[0096] In the above embodiments, the terminal can accurately receive the SIB1 or the SSB based on the corresponding index.

[0097] In combination with the embodiments of the first aspect, in some embodiments, the second SSB index includes at least one of:

[0098] an SSB index indicated in the MSG3;

[0099] an SSB index mapped with a RACH resource, wherein the RACH resource includes a preamble and / or a random access occasion RO corresponding to the first RACH procedure.

[0100] In combination with the embodiments of the first aspect, in some embodiments, in the case that the first RACH procedure fails, the terminal performs at least one of:

[0101] judging that a state of the cell corresponding to the configuration information is a prohibited access state, and a time of the prohibited access state is less than a fifth value;

[0102] reinitiating the RACH procedure to request the SIB1 or the SSB;

[0103] performing cell reselection;

[0104] initiating the RACH procedure to the reselected cell.

[0105] In the above embodiments, when the first RACH procedure fails, the terminal can timely adjust its own behavior to reaccess or request the SIB1 or the SSB from other cells as soon as possible, improve the efficiency of accessing the cell, and improve the communication effect.

[0106] In a second aspect, the embodiments of the present disclosure provide a communication method, performed by a network device, and the method includes:

[0107] transmitting, to a terminal, configuration information used for configuring a random access priority parameter of a first random access channel (RACH) procedure, wherein the first RACH procedure is used for the terminal to request a system information block (SIB1) or a synchronization signal block (SSB).

[0108] In combination with the embodiments of the second aspect, in some embodiments, the random access priority parameter includes at least one of:

[0109] a power ramping step for uplink transmission in the first RACH procedure;

[0110] a scaling factor of a backoff indication BI for uplink transmission in the first RACH procedure;

[0111] an initial reception power indicated by the network device;

[0112] a maximum number of transmissions of a preamble in the first RACH procedure.

[0113] In some embodiments in combination with the embodiments of the second aspect, the random access priority parameter satisfies at least one of the following:

[0114] the power ramping step is greater than a first value;

[0115] the maximum number of transmissions is less than a second value; the first value is a power ramping step for other RACH procedures than the first RACH procedure, and the second value is a maximum number of transmissions for other RACH procedures than the first RACH procedure.

[0116] In some embodiments in combination with the embodiments of the second aspect, the method further comprises:

[0117] receiving information requesting SIB1 or SSB in the first RACH procedure.

[0118] In some embodiments in combination with the embodiments of the second aspect, the first RACH procedure comprises:

[0119] receiving a first message MSG1;

[0120] transmitting a second message MSG2 within a running duration of a first timer.

[0121] In some embodiments in combination with the embodiments of the second aspect, the MSG1 is information requesting SIB1 or SSB, and the MSG2 is feedback information, the feedback information being feedback to the request for the SIB1 or the SSB.

[0122] In some embodiments in combination with the embodiments of the second aspect, the first timer is started after the terminal transmits the MSG1, and a running duration of the first timer is less than a third value, the third value being a running duration of a response timer for other RACH procedures than the first RACH procedure.

[0123] In some embodiments in combination with the embodiments of the second aspect, the running duration of the first timer is configured by the network device.

[0124] In some embodiments in combination with the embodiments of the second aspect, the method further comprises:

[0125] Transmit the physical downlink control channel (PDCCH) scrambled with RNTI. The PDCCH is used to schedule MSG2.

[0126] In conjunction with the embodiments of the second aspect, in some embodiments, RNTI satisfies one of the following:

[0127] Network device configuration;

[0128] Defined by the protocol;

[0129] It is determined based on the bias of the random access RA-RNTI in the first RACH procedure and the network device configuration.

[0130] In conjunction with the embodiments of the second aspect, in some embodiments, the PDCCH is sent in a first search space, wherein the first search space is the search space of the Remaining Minimum System Information (RMSI) or the search space configured by the network device for the PDCCH.

[0131] In conjunction with embodiments of the second aspect, in some embodiments, the first RACH process further includes:

[0132] Receive a third message MSG3, which is used to request either SIB1 or SSB.

[0133] In conjunction with embodiments of the second aspect, in some embodiments, the first RACH process further includes:

[0134] During the duration of the second timer, a fourth message MSG4 is sent, which includes feedback information, namely, feedback on the request of SIB1 or SSB.

[0135] In conjunction with embodiments of the second aspect, in some embodiments, MSG3 includes at least one of the following:

[0136] Instruction information used to indicate a request for SIB1;

[0137] The set of SSB indices that the terminal expects to be used to send SIB1.

[0138] In conjunction with the embodiments of the second aspect, in some embodiments, the second timer is started after the terminal sends MSG3, and the runtime of the second timer is less than the fourth value, which is the runtime of the conflict timer used for other RACH processes besides the first RACH process.

[0139] In conjunction with the embodiments of the second aspect, in some embodiments, the runtime of the second timer is configured by the network device.

[0140] In conjunction with the embodiments of the second aspect, in some embodiments, the method further includes:

[0141] transmitting the SIB1 or the SSB.

[0142] With reference to the embodiments of the second aspect, in some embodiments, the SIB1 or the SSB satisfies at least one of the following:

[0143] transmitted in a beam sweeping manner in a first SSB index order, wherein the first SSB index is an index of an SSB transmitted by a cell corresponding to the configuration information;

[0144] transmitted based on a second SSB index indicated by the terminal;

[0145] transmitted in an SSB set including the second SSB index.

[0146] With reference to the embodiments of the second aspect, in some embodiments, the second SSB index includes at least one of the following:

[0147] an SSB index set indicated in the MSG3;

[0148] an SSB index mapped by a RACH resource, wherein the RACH resource includes a preamble and / or a random access occasion RO corresponding to the first RACH procedure.

[0149] In a third aspect, the embodiments of the present disclosure provide a terminal, comprising:

[0150] a transceiver, configured to receive configuration information, wherein the configuration information is used to configure a random access priority parameter of a first random access channel (RACH) procedure, and the first RACH procedure is used for the terminal to request a system information block (SIB1) or a synchronization signal block (SSB).

[0151] In a fourth aspect, the embodiments of the present disclosure provide a network device, comprising:

[0152] a transceiver, configured to transmit configuration information, wherein the configuration information is used to configure a random access priority parameter of a first random access channel (RACH) procedure, and the first RACH procedure is used for the terminal to request a system information block (SIB1) or a synchronization signal block (SSB).

[0153] In a fifth aspect, the embodiments of the present disclosure provide a terminal, comprising:

[0154] one or more processors;

[0155] The terminal is configured to implement the method of the first aspect.

[0156] In a sixth aspect, the embodiments of the present disclosure provide a network device, comprising:

[0157] one or more processors;

[0158] The network device is configured to implement the method of the second aspect.

[0159] In a seventh aspect, the embodiments of the present disclosure provide a communication system, comprising a terminal and a network device, wherein,

[0160] The terminal is configured to implement the method of the first aspect.

[0161] The network device is configured to implement the method of the second aspect.

[0162] In an eighth aspect, the embodiments of the present disclosure provide a storage medium, wherein the storage medium stores instructions.

[0163] When the instructions run on a communication device, the communication device executes the method of the first aspect or the second aspect.

[0164] In a ninth aspect, the embodiments of the present disclosure provide a program product, wherein

[0165] When the program product is executed by a communication device, the communication device executes the method of the first aspect or the second aspect.

[0166] In a tenth aspect, the embodiments of the present disclosure provide a computer program, which, when running on a computer, causes the computer to execute the method as described in the optional implementation manners of the first aspect and the second aspect.

[0167] In an eleventh aspect, the embodiments of the present disclosure provide a chip or a chip system. The chip or the chip system comprises processing circuitry configured to execute the method described in the above-mentioned first aspect and the second aspect and the optional implementation manners thereof.

[0168] It can be understood that the above-mentioned terminal, network device, communication system, storage medium, program product, computer program, chip or chip system are all used to execute the method proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved thereby can refer to the beneficial effects in the corresponding method, which will not be described here again.

[0169] The embodiments of the present disclosure are not exhaustive, but only illustrate some embodiments, and are not specific limitations on the protection scope of the present disclosure. In the case of no contradiction, each step in an embodiment can be implemented as an independent embodiment, and the steps can be combined arbitrarily, for example, the scheme after removing some steps in an embodiment can also be implemented as an independent embodiment, and the order of the steps in an embodiment can be exchanged arbitrarily, in addition, the optional implementation manners in an embodiment can be combined arbitrarily; in addition, the embodiments can be combined arbitrarily, for example, the steps of different embodiments or the optional implementation manners of other embodiments can be combined arbitrarily.

[0170] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0171] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0172] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0173] In the embodiments disclosed herein, "multiple" refers to two or more.

[0174] In some embodiments, the terms “at least one of”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.

[0175] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of B); in some embodiments, B (execute B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, A and B (both A and B are executed). The same applies when there are more branches such as A, B, C, etc.

[0176] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execution of A regardless of B); in some embodiments, B (execution of B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, C, etc.

[0177] The prefix words of "first", "second" and the like in the embodiments of the present disclosure are merely used to distinguish different description objects, and do not constitute limitation on the position, order, priority, quantity or content of the description objects. The description objects are described in the claims or embodiments, and should not be construed as redundant limitation because of the use of the prefix words. For example, the description object is "field", and the ordinal words before "field" in "first field" and "second field" do not limit the position or order between "fields", and "first" and "second" do not limit whether the "fields" modified thereby are in the same message or not, nor limit the order of "first field" and "second field". For another example, the description object is "level", and the ordinal words before "level" in "first level" and "second level" do not limit the priority between "levels". For another example, the quantity of the description object is not limited by the ordinal words, and can be one or more. For example, "first device", wherein the quantity of "device" can be one or more. In addition, the objects modified by different prefix words can be the same or different, for example, the description object is "device", and "first device" and "second device" can be the same device or different devices, and the types thereof can be the same or different. For another example, the description object is "information", and "first information" and "second information" can be the same information or different information, and the contents thereof can be the same or different.

[0178] In some embodiments, "including A", "containing A", "for indicating A", "carrying A" can be interpreted as directly carrying A, or indirectly indicating A.

[0179] In some embodiments, the terms of "in response to", "in response to determining", "in the case of", "when", "when", "if", "if" and the like can be replaced with each other.

[0180] In some embodiments, the terms of "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not lower than", "above" and the like can be replaced with each other, and the terms of "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", "below" and the like can be replaced with each other.

[0181] In some embodiments, the apparatuses and devices can be interpreted as entities, and can also be interpreted as virtual, whose names are not limited to the names described in the embodiments, and in some cases can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc.

[0182] In some embodiments, "network" can be interpreted as an apparatus contained in the network, for example, access network device, core network device, etc.

[0183] In some embodiments, "access network device (AN device)" can also be referred to as "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", and in some embodiments can also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)", "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)", etc.

[0184] In some embodiments, "terminal" or "terminal device" may be referred to as "user equipment (UE)," "user terminal," "mobile station (MS)," "mobile terminal (MT)," "subscriber station," "mobile unit," "subscriber unit," "wireless unit," "remote unit," "mobile device," "wireless device," "wireless communication device," "remote device," "mobile subscriber station," "access terminal," "mobile terminal," "wireless terminal," "remote terminal," "handset," "user agent," "mobile client," "client," etc.

[0185] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

[0186] In some embodiments, data, information, etc., may be obtained with the user's consent.

[0187] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0188] Figure 1a is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0189] As shown in Figure 1a, the communication system 100 includes a terminal 101 and a network device 102.

[0190] In some embodiments, the terminal 101 includes at least one of a mobile phone, a wearable device, an Internet of Things device, a communication-capable automobile, a smart automobile, a tablet (Pad), a wireless transceiver-equipped computer, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, a wireless terminal device in a smart home, and the like, but is not limited thereto.

[0191] In some embodiments, the network device 102 can include at least one of an access network device and a core network device.

[0192] In some embodiments, the access network device is at least one of a node or a device that accesses a terminal to a wireless network, for example, and can include at least one of an evolved NodeB (eNB) in a 5G communication system, a next generation eNB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved node B (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an Open RAN, a Cloud RAN, a base station in other communication systems, an access node in a wireless fidelity (WiFi) system, and the like, but is not limited thereto.

[0193] In some embodiments, the technical solutions of the present disclosure can be applied to an Open RAN architecture, at this time, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can become internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0194] In some embodiments, the access network device can be composed of a central unit (CU) and a distributed unit (DU), where the CU can also be referred to as a control unit. The CU-DU structure can split the protocol layers of the access network device, with some protocol layer functions being controlled by the CU, and the remaining or all protocol layer functions being distributed in the DU and controlled by the CU. However, the present disclosure is not limited thereto.

[0195] In some embodiments, the core network device can be one device including one or more network elements, or can be multiple devices or device groups including all or part of one or more network elements. The network element can be virtual or physical. The core network includes at least one of an evolved packet core (EPC), a 5G core network (5GCN), and a next-generation core (NGC), for example. Alternatively, the core network device refers to a network element with specific functions, such as an access management function (AMF) and a service management function (SMF).

[0196] It can be understood that the communication system described in the embodiments of the present disclosure is for more clearly illustrating the technical solutions of the embodiments of the present disclosure, and does not constitute a limitation on the technical solutions provided by the embodiments of the present disclosure. Those skilled in the art can know that, as the system architecture evolves and new business scenarios appear, the technical solutions provided by the embodiments of the present disclosure are also applicable to similar technical problems.

[0197] The following embodiments of the present disclosure can be applied to the communication system 100 shown in FIG. 1a or part of the subject, but are not limited thereto.

[0198] The subjects shown in FIG. 1a are examples. The communication system can include all or part of the subjects in FIG. 1a, or other subjects other than those in FIG. 1a. The number and form of each subject is arbitrary. The connection relationship between the subjects is an example. The subjects can be connected or not connected. The connection can be in any manner, can be direct connection or indirect connection, and can be wired connection or wireless connection.

[0199] Embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (Bluetooth (registered trademark)), Public Land Mobile Network (PLMN) network, Device-to-Device (D2D) system, Machine to Machine (M2M) system, Internet of Things (IoT) system, Vehicle-to-Everything (V2X), system using other communication processing methods, next-generation system expanded based on them, and the like. In addition, a plurality of systems can be applied in combination (for example, combination of LTE or LTE-A and 5G, and the like).

[0200] 5G can meet the communication requirements of users for rate, delay, high mobility, energy efficiency, and the diversity and complexity of services in future life. The main application scenarios of 5G include enhanced mobile broadband (eMBB), ultra-reliable and low-latency communications (URLLC), and massive machine type communications (mMTC). Among them, eMBB aims to provide users with multimedia content, services and data, and its demand is growing rapidly; eMBB can be deployed in different scenarios, such as indoor, urban, rural, etc., and the difference in capacity and demand is relatively large, which needs to be analyzed in detail combined with the specific deployment scenario. The typical applications of URLLC include industrial automation, power automation, remote medical operations (surgery), traffic safety assurance, etc. The typical characteristics of mMTC include high connection density, small data volume, delay-insensitive services, low-cost modules, and long service life, etc.

[0201] The energy consumption of a 5G base station is four times that of an LTE base station, so network energy saving is an important means to reduce the cost of operating a 5G system.

[0202] In Release 16 (R16), a wake-up signal (WUS) is introduced to achieve energy saving for RRC_CONNECTED terminals. The duration of sending WUS is defined before the offset of the Connected DRX (C-DRX) on duration of the terminal in the connected state, and WUS, i.e., Downlink Control Information (DCI) 2-6, is sent during the duration of sending WUS, which is scrambled by Power Saving RNTI (PS-RNTI) and used to indicate whether the terminal wakes up to monitor PDCCH during the next C-DRX on duration.

[0203] In R17, paging WUS is introduced to realize the energy saving of RRC idle or inactive state (RRC_IDLE / INACTIVE) terminal. The paging WUS is sent at a certain time before the paging occasion (PO), and the paging early indication (PEI) is used to indicate whether the terminal listens to the paging scheduling information in the PO. The PEI is DCI 2-7 scrambled by PEI-RNTI.

[0204] In R18, in order to reduce the energy consumption of the network, the network can enter the network energy saving mode (NES mode), and the cell discontinuously transmits (cell DTX) and / or discontinuously receives (cell DRX) periodically according to a certain interval. However, in the cell DTX or cell DRX, the master information block (MIB), the system information block (SIB), the paging, and the RACH can be transmitted and received. The NES functions include: SSB-less SCell, cell DTX / DRX, antenna port adaptation, and PDSCH transmission power adaptation.

[0205] For the cell DTX / DRX, the network side configures the pattern of the cell DTX / DRX work through RRC dedicated signaling, that is, configures a period, a bias, and an on duration length. In the on duration, the cell is in an active state, and the reception or transmission of data can be performed; in other time, the non-active time, the network side does not perform the reception or transmission of data in principle, and the special cases such as the paging, SSB, MIB, SIB, or RACH process are not affected, and the reception or transmission is normally performed.

[0206] Among them, DCI 2-9 is a group common DCI, which is used to inform the terminal about the activation and deactivation of cell DTX or DRX of the cell. In addition, cell switch off is also included in NES. Because of the cell DTX / DRX activation or cell switch off, the terminal supporting NES cannot work or cannot meet the high performance requirements of the terminal, so the terminal needs to switch to other cells at this time. For this purpose, the NES introduces conditional handover (CHO) for NES, that is, NES CHO, and at the same time, the handover can also be triggered based on the 1-bit instruction of the DCI, that is, when the NES CHO handover condition is met, the DCI handover instruction is received from the network side, the handover can be performed. The DCI can be DCI format 2-9, that is, reuse the DCI of cell DTX / DRX activation and deactivation.

[0207] The contents broadcasted by the NR system include MIB, RMSI (i.e. SIB1), other SIB (OSI). In combination with Fig. 1b, the SIB1 is configured with configuration parameters related to cell selection, cell access, OSI scheduling, cell common configuration, access control, and configuration information related to cell capability. The control resource set (CORESET) of SIB1 is configured in MIB. The multiplexing relationship between RMSI CORESET and SS / PBCH block (i.e. SSB) resources includes three patterns shown in Figs. 1c-1e, wherein pattern 1 is time division multiplexing (TDM), pattern 2 is TDM + frequency division multiplexing (FDM), and pattern 3 is FDM. The terminal obtains the resource location of PDCCH according to the RMSI CORESET information in the physical broadcast channel (PBCH), and further receives RMSI.

[0208] SI can be sent based on the request of the terminal to reduce the number of system information broadcasted by the base station by default and save wireless resources. For example, in addition to MIB and SIB1, other SIBs can be on-demand, that is, the base station will broadcast only after receiving the SI request of the terminal. Among them, SIB1 has an indication of whether each SI is being broadcasted, and the terminal 101 can know the SIB that needs to make an SI request by reading SIB1.

[0209] SI request can be MSG1-based or MSG3-based. MSG1-based request is based on reserved preamble and / or RACH resource. MSG3-based request does not require reserved RACH preamble, and can be defined as RRC SystemlnfoRequest message (MSG3). The terminal can know whether to use MSG1-based or MSG3-based request by reading system information. For example, if the base station provides configuration information of SI request (si-RequestConfig) in system information (SIB1), the terminal uses MSG1-based SI request, otherwise, the terminal uses MSG3-based SI request. The terminal can send request information (SystemlnformationRequest) to request SI and obtain Systemlnformation messages as shown in FIG. 1f. In MSG1-based, the terminal considers that the random access is successfully completed when it receives the header of the random access preamble identifier (RAPID) of the preamble transmitted by itself, and notifies the upper layer that the SI request is received. In MSG3-based, the terminal considers that the random access is completed based on the contention-based random access procedure, receives the collision resolution message, and matches the common control channel (CCCH), and notifies the upper layer that the SI request is received. The information structure of the base station confirmation or response can be referred to FIG. 1g, and the terminal can read each media access control (MAC) layer sub-protocol data unit (sub PDU).

[0210] In new radio (NR), multiple events can trigger random access (RACH), and a high priority RACH procedure can be defined. The high priority RACH procedure can be configured with some special parameters or processed specially, such as BI backoff scaling, and separate configured random power ramping compensation. The defined RACH procedures with high priority include: handover; beam failure recovery (BFR).

[0211] In combination with the description of the above request SI, the MSG1-based scheme or the MSG3-based scheme both use the RACH procedure, but the RACH procedure of the two schemes is not a high-priority RACH procedure, and is a RACH procedure performed according to the configuration parameters of the conventional RACH or the existing RACH. For the SI requested by the terminal before, the terminal has camped on the current cell, and other SI to be acquired is used for subsequent cell reselection, and thus can not be urgent. However, for the request of some information, for example, the request of SIB1, SIB1 is related to whether the terminal 101 can camp on the current target cell, and is urgent.

[0212] The embodiment of the present disclosure provides a communication method that can process the requested information as soon as possible, so as to reduce the request delay as much as possible.

[0213] FIG. 2a is an interaction schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG. 2a, the embodiment of the present disclosure relates to a communication method, and the above method comprises:

[0214] In step S2101, the network device 102 sends configuration information to the terminal 101.

[0215] In some embodiments, the configuration information is used to configure a random access prioritization (RA-Prioritization) parameter of a first random access channel (RACH) procedure, and the first RACH procedure is used for the terminal 101 to request SIB1 or SSB.

[0216] Optionally, the network device 102 configures the random access prioritization parameter for the first RACH procedure, that is, the first RACH procedure is a high-priority RACH procedure.

[0217] Optionally, the configuration information is used to configure resources for requesting SIB1 or SSB, that is, the random access prioritization parameter for the terminal 101 to request SIB1 or SSB is configured separately, so that the terminal 101 can request SIB1 or SSB through the random access prioritization parameter of the high-priority RACH.

[0218] Optionally, the SIB1 or SSB can be on-demand SIB1 or on-demand SSB, which is issued by the network device 102 based on the request of the terminal 101.

[0219] In some embodiments, the terminal 101 can be a terminal 101 in a radio resource control (RRC) idle state (RRC-IDLE) or an inactive state (RRC-INACTIVE).

[0220] In some embodiments, the network device 102 can send the configuration information through system broadcast information or RRC dedicated signaling, or configure the high priority RACH procedure parameters for requesting SIB1 or SSB in the system broadcast information or RRC dedicated signaling.

[0221] Optionally, the configuration information can configure the parameters of the high priority RACH procedure of the current cell or neighboring cell in which the terminal 101 resides, wherein the current cell or neighboring cell can be an NES cell, i.e., a cell in the network energy saving mode as described in the foregoing embodiments, such as a cell configured with cell DTX / DRX or transmitting SI on demand.

[0222] In some embodiments, the network device 102 can send the configuration information according to the request of the terminal 101.

[0223] In an example, after the terminal 101 resides in a cell, if there is a new SIB or a configuration for requesting SIB1 of another NES cell in the cell, the terminal 101 can initiate a procedure for requesting the SI. In this example, the terminal 101 can first send a request to obtain the configuration information for requesting SIB1.

[0224] In some embodiments, the random access priority parameters configured by the configuration information include at least one of the following:

[0225] a power ramping step (powerRampingStepHighPriority) for uplink transmission in the first RACH procedure;

[0226] a scaling factor (scalingFactorBI) of BI for uplink transmission in the first RACH procedure;

[0227] an initial reception power (preambleReceivedTargetPower) indicated by the network device;

[0228] a maximum number of transmissions (preambleTransMax) of a preamble in the RACH procedure.

[0229] Optionally, the configuration information can configure any one of the above parameters, or any two of the above parameters, or any three of the above parameters, or all of the above parameters.

[0230] In an example, the related parameters can be configured through random access prioritization (RA-Prioritization) information:

[0231] Optionally, the power ramping step is used to indicate the power increase value of the terminal 101 in each time of initiating RACH in the random access procedure, such as the step of MSG1 transmission power ramping, wherein the terminal 101 can send a preamble through MSG1. In an example, after a RACH failure, the terminal 101 can send a preamble again by sending MSG1, and the difference between the power of the MSG1 sent again and the last MSG1 (such as the MSG1 corresponding to the RACH failure) can conform to the configured power ramping step.

[0232] In an example, the power ramping step is greater than a first value, and the first value is a power ramping step for a first RACH procedure, i.e., a high-priority RACH procedure, or the first value is a power ramping step for a regular RACH procedure. Alternatively, the first value is determined according to a power ramping step of other RACH. Wherein the other RACH procedure or the regular RACH procedure refers to a common RACH that is not high-priority. In this example, the high-priority RACH configuration for requesting SIB1 or SSB has a larger power ramping step than the common RACH, so that the terminal 101 can quickly access successfully.

[0233] Optionally, the BI can be used to indicate the time length of the terminal 101 to back off or wait after a RACH failure. The network device 102 can configure the BI value for the terminal 101, and in this embodiment, the configuration information can configure a scaling factor based on the BI, which is used to determine the backoff value in the random access procedure in this embodiment, i.e., in the high-priority RACH for requesting SIB1 or SSB, a backoff or waiting time length based on the BI can be used.

[0234] In an example, in the high-priority RACH for requesting SIB1 or SSB, the backoff can be: BI multiplied by a scaling factor; or SCALING_FACTOR_BI multiplied by PREAMBLE_BACKOFF, wherein SCALING_FACTOR_BI represents the scaling factor, and PREAMBLE_BACKOFF represents the BI, and PREAMBLE_BACKOFF is a backoff value configured by the network device 102.

[0235] Optionally, the initial received power is used to determine the transmission power of the terminal 101 sending MSG1, and the greater the initial received power, the greater the transmission power of the terminal 101 sending MSG1 when requesting SIB1 or SSB, so as to reduce the number of power ramping and speed up the process of requesting SIB1 or SSB.

[0236] Optionally, the maximum transmission number is used to indicate a maximum transmission number of the preamble in the random access procedure, and if the number of times of transmitting the preamble by the terminal 101 reaches the maximum transmission number, the random access procedure is considered to fail.

[0237] In an example, the maximum transmission number is less than a second value; wherein the second value is a maximum transmission number for a RACH procedure other than the first RACH procedure, i.e., the high priority RACH procedure, and the second value can be defined by a protocol or configured by the network device. In this example, the maximum transmission number is set to be relatively small, so that the terminal 101 can select another candidate cell for random access as soon as possible after the random access fails, thereby improving the efficiency of successful random access.

[0238] In some embodiments, the terminal 101 receives the configuration information sent by the network device 102 to learn the relevant configuration parameters when requesting SIB1 or SSB.

[0239] In step S2102, the terminal 101 sends a first message MSG1 to the network device 102 according to the configuration information.

[0240] In some embodiments, the MSG1 can be the first message sent by the terminal 101 in the first RACH procedure.

[0241] In an example, the MSG1 can carry the preamble.

[0242] In some embodiments, the MSG1 is used to request SIB1 or SSB. That is, in this embodiment, SIB1 or SSB can be requested based on MSG1.

[0243] Optionally, when the terminal 101 requests SIB1 or SSB using MSG1, the terminal 101 can send MSG1 based on the random access priority parameter of the configuration information. For example, for the first RACH procedure for requesting SIB1, the terminal 101 uses the above-mentioned configuration for power ramping and backoff avoidance in the random access procedure, such as sending MSG1 based on one or more of the power ramping step, the scaling factor of the BI, the initial received power, or the maximum transmission number in the configuration information.

[0244] In some embodiments, the network device 102 can receive the MSG1 sent by the terminal 101.

[0245] In step S2103, the terminal 101 starts a first timer.

[0246] In some embodiments, the terminal 101 can start a first timer after sending the MSG1. The first timer is used to indicate the time length for waiting for the network side response, such as the time length for waiting for the random access response (RAR), which can be recorded as ra-ResponseWindow.

[0247] In some embodiments, the running time of the first timer is less than a third value. The third value is the running time of the response timer for other RACH processes or the conventional RACH except the first RACH process, i.e., the high priority RACH process, and the first timer is a timer independently configured for the MSG1 for requesting the SIB1 or the SSB, which is shorter than the running time of the conventional RACH, i.e., the terminal 101 has a shorter waiting time.

[0248] Optionally, the third value can be defined by the protocol or configured by the network device.

[0249] In some embodiments, the terminal 101 waits for the feedback or confirmation of the network side, such as the MSG2, within the running time of the first timer. The running time of the first timer is shorter, so that the time for the terminal 101 to request the SIB1 can be as short as possible, forcing the network side to reply as soon as possible.

[0250] In some embodiments, the running time of the first timer is configured by the network device. For example, the network device 102 configures the running time of the first timer by the following parameters:

[0251] ra-ResponseWindow-v1610 ENUMERATED{sl60,sl160}

[0252] Step S2104, the network device 102 sends the second message MSG2 to the terminal 101.

[0253] In some embodiments, when the MSG1 is used to request the SIB1 or the SSB, the MSG2 is used to respond, feed back or confirm the request of the terminal 101, i.e., the MSG2 includes the feedback information, and the feedback information is the feedback to the request of the SIB1 or the SSB.

[0254] In some embodiments, the MSG2 can include the RAR, which can indicate the information of the network device 102 issuing the SIB1 or the SSB. For example, the MSG2 is the RAR MAC PDU.

[0255] In some embodiments, the network device 102 can schedule the MSG2 through the PDCCH. The network device 102 sends the PDCCH scrambled by the RNTI, and the terminal 101 receives the PDCCH according to the corresponding RNTI, and then obtains the MSG2 scheduled by the PDCCH.

[0256] Optionally, the RNTI corresponding to the scheduling of MSG2 in this embodiment can be a separate RNTI configured or designated for terminal 101, which is specifically used to receive the feedback confirmation (such as MSG2) requested by the network side for SIB1 or SSB. In the related art, terminal 101 receives MSG2 according to the random access RNTI (RA-RNTI) corresponding to the random access resource (RACH Occasion, RO) where the preamble is sent.

[0257] In some embodiments, the RNTI corresponding to the scheduling of MSG2 satisfies one of the following:

[0258] Configured by the network device;

[0259] Defined by the protocol;

[0260] Determined according to the random access RA-RNTI of the first RACH process and the offset configured by the network device.

[0261] For example, the network device 102 configures an offset, and after terminal 101 calculates the RA-RNTI, the offset is superimposed on the temporary identifier for receiving the PDCCH, that is, offset+RA-RNTI; offset+RA-RNTI is used to receive the scheduling information of the RAR. Wherein, RA-RNTI is determined based on the RO resource used to send MSG1.

[0262] In some embodiments, the PDCCH is sent in the first search space, wherein the first search space is the search space (search space) of the remaining minimum system information RMSI, or the search space configured by the network device for the PDCCH.

[0263] Optionally, the PDCCH scrambled by the RNTI is sent in the search space of RMSI, or the PDCCH scrambled by the RNTI is sent in a separately configured search space.

[0264] Optionally, the network device 102 can send the PDCCH scrambled by the RNTI according to the sending of SIB1. For example, when SIB1 is sent, the network device 102 starts to periodically send the PDCCH scrambled by the RNTI; if SIB1 is not sent, the network device 102 stops sending the PDCCH scrambled by the RNTI.

[0265] In some embodiments, terminal 101 listens to and receives MSG2 sent by network device 102 within the running time of the first timer, and can receive SIB1 or SSB according to MSG2.

[0266] Step S2105, the network device 102 sends SIB1 or SSB to the terminal 101.

[0267] Optionally, in this step, the network device 102 sends the terminal 101 the information requested by the terminal 101, such as SIB1 or SSB.

[0268] In some embodiments, when the network device 102 sends SIB1 or SSB, at least one of the following can be met:

[0269] In a beam sweeping manner according to the first SSB index order, wherein the first SSB index is the index of the SSB sent by the cell corresponding to the configuration information;

[0270] Based on the second SSB index indicated by the terminal;

[0271] In the SSB set including the second SSB index.

[0272] Optionally, the network device 102 can send SIB1 in a beam sweeping manner in all actually sent SSB index directions of the cell.

[0273] Optionally, the network device 102 can select to send SIB1 on the SSB index indicated by the terminal 101 or the SSB set containing the SSB index indicated by the terminal 101. For example, the SSB index indicated by the terminal 101 is 4, and the network device 102 can send SIB1 on the SSB index 4, or send SIB1 on the set containing the SSB index 4, such as {SSB index 4, SSB index 5, SSB index 6}.

[0274] In some embodiments, the SSB index indicated by the terminal 101, i.e. the second SSB index, can include:

[0275] The SSB index mapped by the RACH resource, wherein the RACH resource includes the preamble and / or random access occasion RO corresponding to the first RACH procedure.

[0276] Optionally, the RACH resource is the RACH resource corresponding to or used by MSG1 when the terminal 101 requests SIB1 or SSB based on MSG1 in the first RACH procedure. For example, the second SSB index includes the SSB index mapped by the preamble or RO resource of MSG1, i.e. the MSG1 is used to request SIB1 or SSB under the coverage of the SSB index.

[0277] In some embodiments, the terminal 101 receives the requested SIB1 or SSB based on the corresponding SSB index.

[0278] In some embodiments, if the random access procedure of the terminal 101 requesting SIB1 or SSB fails, for example, the preamble reaches the maximum number of transmissions, the terminal 101 can perform corresponding processing based on its own implementation.

[0279] In some embodiments, in the case of failure of the first RACH procedure, the terminal performs at least one of the following:

[0280] judging that the state of the cell corresponding to the configuration information is a barred state, and the time of the barred state is less than a fifth value;

[0281] reinitiating a RACH procedure to request SIB1 or SSB;

[0282] performing cell reselection;

[0283] initiating a RACH procedure to the reselected cell.

[0284] Optionally, the fifth value can be configured by the network or defined by the protocol. The value can be equal to or less than the time of barred in the relevant protocol. Alternatively, the network device configures or the protocol defines the time of barred state of the cell corresponding to the configuration information.

[0285] For example, the time of barred in the relevant protocol is 300s, and the fifth value of the embodiment can be equal to or less than 300s, so that the terminal 101 in the embodiment considers that the time of barred of the cell corresponding to the configuration information is less than 300s, for example, the terminal 101 considers that the time of barred of the cell corresponding to the configuration information is 100s.

[0286] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and the terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", etc. can be replaced with each other.

[0287] In some embodiments, “get,” “obtain,” “receive,” “transmit,” “bidirectional transmission,” and “send and / or receive” can be used interchangeably and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining through self-processing, or autonomous implementation, among other meanings.

[0288] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.

[0289] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.

[0290] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “duration,” “segment,” “time window,” “window,” and “time.”

[0291] In some embodiments, the terms "component carrier (CC)," "cell," "frequency carrier," and "carrier frequency" can be used interchangeably.

[0292] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.

[0293] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0294] In some embodiments, "not expecting to receive" can be interpreted as not receiving on the time domain resource and / or the frequency domain resource, or can be interpreted as, after receiving the data, etc., not performing subsequent processing on the data, etc.; "not expecting to send" can be interpreted as not sending, or can be interpreted as sending but not expecting the receiving party to respond to the content of the sending.

[0295] The method related to the embodiments of the present disclosure can include at least one of steps S2101-S2105.

[0296] In some embodiments, the method includes step S2101.

[0297] In some embodiments, the method includes steps S2101-S2103.

[0298] In some embodiments, reference can be made to the other optional implementations described before or after the description corresponding to FIG. 2a.

[0299] In the embodiments of the present disclosure, when the terminal 101 in RRC-IDLE / INACTIVE requests SIB1, a RACH with high priority is used, such as using parameters configured separately for the SIB1 RACH process to request through MSG1. Thus, the time for requesting SIB1 is shorter, and the terminal 101 can camp on the target cell as soon as possible, thereby shortening the camping cell change time.

[0300] FIG. 2b is an interaction schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG. 2b, the embodiments of the present disclosure relate to a communication method, and the above method includes:

[0301] Step S2201, the network device 102 sends configuration information to the terminal 101.

[0302] In some embodiments, the implementation of step S2201 can refer to the implementation of step S2101 in FIG. 2a, which will not be described here.

[0303] Step S2202, the terminal 101 sends MSG1 to the network device 102.

[0304] In some embodiments, in this embodiment, MSG1 is not used to request SIB1 or SSB, and the implementation of the remaining steps S2202 can refer to the implementation of step S2102 in FIG. 2a, which will not be described here.

[0305] Step S2203, the terminal 101 starts a first timer.

[0306] In some embodiments, the implementation of step S2203 can refer to the implementation of step S2103 in FIG. 2a, which will not be described here.

[0307] Step S2204, the network device 102 sends MSG2 to the terminal 101.

[0308] In some embodiments, the implementation of step S2204 can refer to the implementation of step S2104 in FIG. 2a, which will not be repeated here.

[0309] Step S2205, the terminal 101 sends MSG3 to the network device 102.

[0310] In some embodiments, MSG3 is used to request SIB1 or SSB.

[0311] In some embodiments, MSG3 includes at least one of the following:

[0312] indication information for indicating the request of SIB1;

[0313] a set of SSB indexes expected by the terminal for sending SIB1.

[0314] Optionally, the indication information can occupy 1 or more bits, for indicating whether the terminal 101 requests SIB1 or SSB.

[0315] Optionally, the set of SSB indexes indicated by the terminal 101 in MSG3 can include at least one SSB index.

[0316] Step S2206, the terminal 101 starts a second timer.

[0317] In some embodiments, the terminal 101 can start a second timer after sending MSG3, the second timer being used to indicate the time length for waiting for the network side response, such as the time length for waiting for the network conflict resolution information, which can be denoted as ra-ContentionResolutionTimer.

[0318] In some embodiments, the running time length of the second timer is less than a fourth value. Wherein, the fourth value is the running time length of the conflict timer for other RACH processes or conventional RACH processes other than the first RACH process, i.e., the high-priority RACH process, and the second timer is a timer independently configured for MSG3 for requesting SIB1 or SSB, which is shorter than the conventional RACH running time length, i.e., the terminal 101 has a shorter waiting time.

[0319] Optionally, the fourth value can be defined by a protocol or configured by the network device.

[0320] In some embodiments, the terminal 101 waits for the network side conflict resolution information within the running time of the second timer, such as waiting for MSG4, wherein the running time of the second timer is short, so that the time for the terminal 101 to request SIB1 is as short as possible, forcing the network side to reply as soon as possible to the conflict resolution information of the SIB1 request.

[0321] In some embodiments, the running time of the second timer is configured by the network device. For example, the network device 102 configures the running time of the second timer by the following parameters:

[0322] ra-ContentionResolutionTimer ENUMERATED{sf8,sf16,sf24,sf32,sf40,sf48,sf56,sf64}

[0323] Step S2207, the network device 102 sends MSG4 to the terminal 101.

[0324] In some embodiments, when MSG3 is used to request SIB1 or SSB, MSG4 includes feedback information, which is the feedback of the request for the SIB1 or the SSB.

[0325] In some embodiments, MSG4 is a MAC CE for conflict resolution, which can indicate the information of the SIB1 or SSB issued by the network device 102.

[0326] In some embodiments, the terminal 101 listens and receives MSG4 sent by the network device 102 within the running time of the second timer.

[0327] Step S2208, the network device 102 sends SIB1 or SSB to the terminal 101.

[0328] In some embodiments, the implementation of step S2208 can refer to the implementation of step S2105 in FIG. 2a, which will not be repeated here.

[0329] For example, in some embodiments, the network device 102 can send in a beam sweeping manner when sending SIB1 or SSB according to the first SSB index order, wherein the first SSB index is the SSB index of all actually sent SSBs of the cell corresponding to the configuration information.

[0330] In some embodiments, the network device 102 can send based on the second SSB index indicated by the terminal or send in the SSB set including the second SSB index when sending SIB1 or SSB.

[0331] The second SSB index can include an SSB index of a RACH resource mapping, where the RACH resource includes a preamble and / or a random access occasion (RO) corresponding to the first RACH procedure.

[0332] In some embodiments, if the first RACH procedure random access procedure of the terminal 101 requesting the SIB1 or the SSB fails, see the description of step S2105.

[0333] The method related to the embodiments of the present disclosure can include at least one of steps S2201-S2208.

[0334] In some embodiments, see the other optional implementations described before or after the corresponding description of FIG. 2b.

[0335] In the embodiments of the present disclosure, when the terminal 101 in RRC-IDLE / INACTIVE requests the SIB1, a RACH with high priority is used, such as using parameters configured separately for the SIB1 RACH procedure to request through MSG3. Thus, the time for requesting the SIB1 is shorter, and the terminal 101 can camp on the target cell as soon as possible, thereby shortening the camping cell change time.

[0336] FIG. 3a is a flow diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in FIG. 3a, the embodiments of the present disclosure relate to a communication method, which is performed by a terminal 101, and the above method includes:

[0337] Step S3101, receiving configuration information.

[0338] In some embodiments, the implementation of step S3101 can refer to the implementation of step S2101 in FIG. 2a or step S2201 in FIG. 2b, which will not be repeated here.

[0339] Step S3102, sending MSG1.

[0340] In some embodiments, when MSG1 is used to request SIB1 or SSB, the implementation of step S3102 can refer to the implementation of step S2102 in FIG. 2a, which will not be repeated here.

[0341] In some embodiments, MSG1 is not used to request SIB1 or SSB, and the implementation of step S3102 can refer to the implementation of step S2202 in FIG. 2b, which will not be repeated here.

[0342] Step S3103, starting a first timer.

[0343] In some embodiments, implementation of step S3103 can refer to implementation of step S2103 in FIG. 2a or step S2203 in FIG. 2b, which will not be repeated here.

[0344] Step S3104, receiving MSG2.

[0345] In some embodiments, implementation of step S3104 can refer to implementation of step S2104 in FIG. 2a or step S2204 in FIG. 2b, which will not be repeated here.

[0346] Step S3105, sending MSG3.

[0347] In some embodiments, implementation of step S3105 can refer to implementation of step S2205 in FIG. 2b, which will not be repeated here.

[0348] Step S3106, starting a second timer.

[0349] In some embodiments, implementation of step S3106 can refer to implementation of step S2206 in FIG. 2b, which will not be repeated here.

[0350] Step S3107, receiving MSG4.

[0351] In some embodiments, implementation of step S3104 can refer to implementation of step S2207 in FIG. 2b, which will not be repeated here.

[0352] Step S3108, receiving SIB1 or SSB.

[0353] In some embodiments, implementation of step S3108 can refer to implementation of step S2105 in FIG. 2a or step S2208 in FIG. 2b, which will not be repeated here.

[0354] The method related to the embodiments of the present disclosure can include at least one of steps S3101-S3108. For example, steps S3101-S3104 are included, or steps S3101-S3107 are included.

[0355] In some embodiments, other optional implementations can be described before or after the corresponding description of FIG. 3a.

[0356] FIG. 3b is a flow diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in FIG. 3b, the embodiments of the present disclosure relate to a communication method, which is performed by a terminal 101, and the above method includes:

[0357] Step S3201, receiving configuration information.

[0358] In some embodiments, the implementation of step S3201 can refer to the implementation of step S2101 in FIG. 2a, which will not be repeated here.

[0359] Step S3202, sending MSG1.

[0360] In some embodiments, the implementation of step S3202 can refer to the implementation of step S2102 in FIG. 2a, which will not be repeated here.

[0361] Step S3203, receiving MSG2 within the running duration of the first timer.

[0362] In some embodiments, the implementation of step S3203 can refer to the implementation of steps S2103-S2104 in FIG. 2a, which will not be repeated here.

[0363] The method related to the embodiments of the present disclosure can include at least one of steps S3201-S3203.

[0364] In some embodiments, other optional implementations can be described before or after the corresponding description of FIG. 3b.

[0365] FIG. 3c is a flow diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in FIG. 3c, the embodiments of the present disclosure relate to a communication method, which is performed by a terminal 101, and the above method includes:

[0366] Step S3301, receiving configuration information.

[0367] In some embodiments, the implementation of step S3301 can refer to the implementation of step S2101 in FIG. 2a, which will not be repeated here.

[0368] Step S3302, sending MSG1.

[0369] In some embodiments, the implementation of step S3302 can refer to the implementation of step S2202 in FIG. 2b, which will not be repeated here.

[0370] Step S3303, receiving MSG2 within the running duration of the first timer.

[0371] In some embodiments, the implementation of step S3203 can refer to the implementation of steps S2203-S2204 in FIG. 2b, which will not be repeated here.

[0372] Step S3304, sending MSG3.

[0373] In some embodiments, the implementation of step S3304 can refer to the implementation of step S2205 in FIG. 2b, which will not be repeated here.

[0374] Step S3305, receiving MSG4 within a duration of running of the second timer.

[0375] In some embodiments, the implementation of step S3305 can refer to the implementation of steps S2206-S2207 in FIG. 2b, which will not be repeated here.

[0376] The method related to the embodiments of the present disclosure can include at least one of steps S3301-S3305.

[0377] In some embodiments, other optional implementations can be recorded before or after the corresponding description of FIG. 3c.

[0378] FIG. 3d is a flow diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in FIG. 3d, the embodiments of the present disclosure relate to a communication method, which is performed by a terminal 101, and the above method includes:

[0379] Step S3401, receiving configuration information.

[0380] In some embodiments, the implementation of step S3401 can refer to the implementation of step S2101 in FIG. 2a, which will not be repeated here.

[0381] Step S3402, requesting SIB1 or SSB in a RACH procedure according to the configuration information.

[0382] In some embodiments, when SIB1 or SSB is requested based on MSG1, the implementation of step S3402 can refer to the implementation of steps S2102-S2105 in FIG. 2a, which will not be repeated here.

[0383] In some embodiments, when SIB1 or SSB is requested based on MSG3, the implementation of step S3402 can refer to the implementation of steps S2202-S2208 in FIG. 2b, which will not be repeated here.

[0384] In some embodiments, other optional implementations can be recorded before or after the corresponding description of FIG. 3d.

[0385] FIG. 3e is a flow diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in FIG. 3e, the embodiments of the present disclosure relate to a communication method, which is performed by a terminal 101, and the above method includes:

[0386] Step S3501, receiving configuration information.

[0387] In some embodiments, the implementation of step S3501 can refer to the implementation of step S2101 in FIG. 2a, which will not be repeated here.

[0388] In some embodiments, other optional implementations described before or after the description corresponding to FIG. 3e can be referred to.

[0389] FIG. 4a is a flow diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in FIG. 4a, an embodiment of the present disclosure relates to a communication method, which is performed by the network device 102, and the above method comprises the following steps:

[0390] In step S4101, configuration information is sent.

[0391] In some embodiments, the implementation of step S4101 can refer to the implementation of step S2101 in FIG. 2a or step S2201 in FIG. 2b, which will not be repeated here.

[0392] In step S4102, MSG1 is received.

[0393] In some embodiments, when MSG1 is used to request SIB1 or SSB, the implementation of step S3102 can refer to the implementation of step S2102 in FIG. 2a, which will not be repeated here.

[0394] In some embodiments, when MSG1 is not used to request SIB1 or SSB, the implementation of step S3102 can refer to the implementation of step S2202 in FIG. 2b, which will not be repeated here.

[0395] In step S4103, MSG2 is sent.

[0396] In some embodiments, the implementation of step S4103 can refer to the implementation of step S2104 in FIG. 2a or step S2204 in FIG. 2b, which will not be repeated here.

[0397] In step S4104, MSG3 is received.

[0398] In some embodiments, the implementation of step S4104 can refer to the implementation of step S2205 in FIG. 2b, which will not be repeated here.

[0399] In step S4105, MSG4 is sent.

[0400] In some embodiments, the implementation of step S4105 can refer to the implementation of step S2207 in FIG. 2b, which will not be repeated here.

[0401] In step S4106, SIB1 or SSB is sent.

[0402] In some embodiments, the implementation of step S4105 can refer to the implementation of step S2105 in FIG. 2a or step S2208 in FIG. 2b, which will not be repeated here.

[0403] The method related to the embodiments of the present disclosure can include at least one of steps S4101-S4106.

[0404] In some embodiments, other optional implementations can be described before or after the description corresponding to FIG. 4a.

[0405] FIG. 4b is a flow diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in FIG. 4b, the embodiments of the present disclosure relate to a communication method, which is performed by the network device 102, and the above method includes the following steps.

[0406] In step S4201, configuration information is sent.

[0407] In some embodiments, the implementation of step S4201 can refer to the implementation of step S2101 in FIG. 2a, which will not be described here again.

[0408] In step S4202, information of SIB1 or SSB requested in a RACH procedure is received.

[0409] In some embodiments, when SIB1 or SSB is requested based on MSG1, the implementation of step S4202 can refer to the implementation of steps S2102-S2105 in FIG. 2a, which will not be described here again.

[0410] In some embodiments, when SIB1 or SSB is requested based on MSG3, the implementation of step S4202 can refer to the implementation of steps S2202-S2208 in FIG. 2b, which will not be described here again.

[0411] In some embodiments, other optional implementations can be described before or after the description corresponding to FIG. 4b.

[0412] FIG. 4c is a flow diagram illustrating a communication method according to an embodiment of the present disclosure. As shown in FIG. 4c, the embodiments of the present disclosure relate to a communication method, which is performed by the network device 102, and the above method includes the following steps.

[0413] In step S4301, configuration information is sent.

[0414] In some embodiments, the implementation of step S4301 can refer to the implementation of step S2101 in FIG. 2a, which will not be described here again.

[0415] In some embodiments, other optional implementations can be described before or after the description corresponding to FIG. 4c.

[0416] In this embodiment of the disclosure, when an RRC-IDLE / INACTIVE UE requests SIB1, a high-priority RACH is used, i.e., parameters configured separately for the SIB1 request RACH process are used. This shortens the SIB1 request time, allowing the UE to camp on the target cell as early as possible and reducing the time for cell change. To facilitate understanding of this embodiment of the disclosure, some examples are provided below:

[0417] Example 1:

[0418] Once a UE camps on a cell, if that cell has a new SIB or a configuration for requesting SIB1 from other NES cells, the UE will immediately initiate a process to request that SIB1 to obtain the configuration information.

[0419] The system broadcast message or RRC dedicated signaling configures (which can be configured for the current cell or neighboring NES cells) to request resource configuration for SIB1. The configuration includes parameters for RACH priority, including power ramp step size and / or backoff factor, and / or initial target received power (preambleReceivedTargetPower), and / or maximum preamble transmission count (preambleTransMax).

[0420] The power ramp step size is used to determine the power ramp step size of the MSG1 transmission during the random access process of the UE. The power ramp step size is larger than that of the normal RACH for the on-demand SIB1 triggered RACH, so that the random access can be completed quickly.

[0421] The backoff factor is used by the UE to determine the backoff value during random access, which is the backoff factor SCALING_FACTOR_BI multiplied by PREAMBLE_BACKOFF, where PREAMBLE_BACKOFF is the backoff value given by the network.

[0422] The initial receive power is a parameter used to set the transmit power when sending MSG1. If this parameter is set to a larger value, the UE requesting SIB1 can send MSG1 at a higher power, reducing the number of power ramp-ups and speeding up the SIB1 request process.

[0423] Wherein, preamble maximum transmission times preambleTransMax is the maximum transmission times of preamble in random access process, if the maximum transmission times is reached, the random process is considered to fail, in order to quickly reduce the time interval of cell reselection, the preamble maximum transmission times preambleTransMax needs to be set relatively small, so that the UE selects other candidate cells as soon as possible.

[0424] For the RACH process of requesting SIB1, the UE uses the above configuration for power ramping and backoff avoidance in the random access process.

[0425] Example two:

[0426] On the basis of example one, in the RACH process, after sending MSG1, the terminal starts the timer ra-ResponseWindow to wait for the feedback or confirmation of the network side, at this time, for the RACH process of requesting SIB1, an independent ra-ResponseWindow is configured, at this time, the value is set to have a shorter waiting time than other RACH. The purpose is to make the time of requesting SIB1 as short as possible, and also to force the network side to reply the RAR of requesting SIB1 as soon as possible.

[0427] Wherein, ra-ResponseWindow-v1610 ENUMERATED{sl60,sl160}.

[0428] Example three:

[0429] On the basis of example one or example two, if it is a SIB1 request mode based on MSG3, the terminal 101 also needs to send MSG3, MSG3 contains SIB1 request indication information, and also contains the suggested SSB index set (at least one SSB index) of sending SIB1.

[0430] Optionally, after sending MSG3, the terminal starts the conflict resolution timer ra-ContentionResolutionTimer, at this time, for the RACH process of requesting SIB1, an independent ra-ContentionResolutionTimer is configured, at this time, the value is set to have a shorter waiting time than other RACH. The purpose is to make the time of requesting SIB1 as short as possible, and also to force the network side to reply the conflict resolution MAC CE of requesting SIB1 as soon as possible.

[0431] ra-ContentionResolutionTimer ENUMERATED { sf8, sf16, sf24, sf32, sf40, sf48, sf56, sf64}.

[0432] Example Four:

[0433] On the basis of any one of the examples one to three, after the network side receives the SIB1 sending request from the terminal, the reply confirmation is sent:

[0434] In this example, an RNTI is configured for the UE or the system, which is specially used for receiving the feedback confirmation from the network side for the request of SIB1. In the related art, the terminal receives the RAR MAC PDU (MSG2) using the RA-RNTI corresponding to the RO resource of the preamble.

[0435] Further, the network side can send the PDCCH scrambled by the RNTI according to the sending of SIB1. The PDCCH scrambled by the RNTI is sent in the search space of RMSI. Or the PDCCH scrambled by the RNTI is sent in the separately configured search space. For example, if SIB1 is sent, the network side starts to periodically send the PDCCH scrambled by the RNTI. If SIB1 is not sent, the sending of the PDCCH scrambled by the RNTI is stopped.

[0436] Alternatively, the network side configures an offset. After the terminal calculates the RA-RNTI, the offset is superimposed to obtain the temporary identifier for receiving the RA-RNTI. That is, offset + RA-RNTI is used to receive the scheduling information of the RAR, that is, the DCI is scrambled based on the new RNTI. The RA-RNTI is determined based on the RO resource used for sending MSG1.

[0437] Example Five:

[0438] On the basis of example four, after the network side receives the SIB1 sending request from the terminal, SIB1 is sent:

[0439] Among them, for the MSG1 based scheme, the network side can send SIB1 in the beam sweeping mode in all actually sent SSB index directions of the cell. The network side can also choose to send SIB1 on the SSB index indicated by the terminal (the indication of the terminal means that the MSG1 preamble or the RO resource implies the SSB index to which the UE belongs, that is, under the coverage of the SSB index) or the SSB set containing the SSB index indicated by the terminal.

[0440] For the MSG3 based solution, the network side can transmit SIB1 in a beam sweeping manner in all actually transmitted SSB index directions of the cell. The network side can also choose to transmit SIB1 on the SSB index indicated by the terminal (the terminal indication refers to the SSB index implied by the MSG1 preamble or RO resource, that is, under the coverage of the SSB index, or the SSB index set indicated by MSG3) or the SSB set containing the SSB index indicated by the terminal.

[0441] Example six:

[0442] On the basis of any one of examples one to five, if the random access procedure for requesting SIB1 fails, for example, the maximum number of transmissions is reached, the following processing is performed depending on the terminal implementation:

[0443] The cell is considered barred, but the barred time is not 300s, but a value smaller than 300s, which can be configured by the network side or agreed by the protocol, for example, 100s.

[0444] The RACH procedure is reinitiated to continue to request SIB1.

[0445] Another candidate cell is selected as a target cell for cell reselection, and if the new target cell is still an on-demand SIB1 cell, the random access procedure to the cell is started.

[0446] Example seven:

[0447] In any of the above examples, the above SIB1 request can be applied to the on-demand SSB request scenario if the on-demand SSB is requested using the RACH procedure.

[0448] In the embodiments of the present disclosure, the UE can initiate a RACH procedure based on the high-priority RACH resource configured by the network side; wherein the RACH procedure can also be controlled based on the short timer configured by the network side. In addition, the network determines the beam set for transmitting SIB1 according to the beam index implicitly or explicitly indicated by the terminal.

[0449] The embodiments of the present disclosure also propose a device for implementing any of the above methods, for example, a device comprising units or modules for implementing each step performed by the terminal in any of the above methods. For another example, another device is also proposed, comprising units or modules for implementing each step performed by the network device (such as an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0450] It should be understood that the division of each unit or module in the above apparatus is only a logical function division, and all or part of them can be integrated into a physical entity or physically separated in actual implementation. In addition, the units or modules in the apparatus can be implemented in the form of processor calling software: for example, the apparatus includes a processor, the processor is connected with a memory, the memory stores instructions, and the processor calls the instructions stored in the memory to realize any of the above methods or realize the functions of each unit or module of the above apparatus, wherein the processor is a general processor such as a central processing unit (CPU) or a microprocessor, and the memory is a memory in the apparatus or a memory outside the apparatus. Alternatively, the units or modules in the apparatus can be implemented in the form of hardware circuit, and the functions of part or all of the units or modules can be realized by the design of hardware circuit. The above hardware circuit can be understood as one or more processors; for example, in one implementation, the above hardware circuit is an application-specific integrated circuit (ASIC), and the functions of part or all of the units or modules are realized by the design of the logical relationship of elements in the circuit; for another example, in another implementation, the above hardware circuit is a programmable logic device (PLD), and a field programmable gate array (FPGA) is taken as an example, which can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by a configuration file, so as to realize the functions of part or all of the above units or modules. All units or modules of the above apparatus can be all implemented in the form of processor calling software, or all implemented in the form of hardware circuit, or part implemented in the form of processor calling software and the remaining part implemented in the form of hardware circuit.

[0451] In the embodiments of the present disclosure, the processor is a circuit with signal processing capability. In one implementation, the processor can be a circuit with instruction reading and running capability, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), a digital signal processor (DSP), or the like. In another implementation, the processor can implement certain functions through a logical relationship of a hardware circuit, and the logical relationship of the hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In the reconfigurable hardware circuit, the processor loads a configuration document to implement the configuration of the hardware circuit. It can be understood that the processor loads instructions to implement the functions of the above part or all units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), and the like.

[0452] FIG. 5a is a structural schematic diagram of a terminal according to an embodiment of the present disclosure. As shown in FIG. 5a, the terminal 5100 can include at least one of a transceiver module 5101, a processing module 5102, and the like. In some embodiments, the transceiver module 5101 is configured to receive configuration information, where the configuration information is used to configure a random access priority parameter of a first random access channel (RACH) procedure, and the first RACH procedure is used for the terminal to request a system information block (SIB1) or a synchronization signal block (SSB).

[0453] Optionally, the transceiver module 5101 is configured to perform at least one of the communication steps, such as receiving and / or transmitting, performed by the terminal 101 in any of the above methods, which will not be described herein. Optionally, the processing module 5102 is configured to perform at least one of the other steps performed by the terminal 101 in any of the above methods, which will not be described herein.

[0454] FIG. 5b is a structural schematic diagram of a terminal according to an embodiment of the present disclosure. As shown in FIG. 5b, the network device 5200 can include at least one of a transceiver module 5201, a processing module 5202, and the like. In some embodiments, the transceiver module 5201 is configured to send configuration information, where the configuration information is used to configure a random access priority parameter of a first random access channel (RACH) procedure, and the first RACH procedure is used for the terminal to request a system information block (SIB1) or a synchronization signal block (SSB).

[0455] In some embodiments, the transceiver module can include a sending module and / or a receiving module, and the sending module and the receiving module can be separate or integrated together. Alternatively, the transceiver module can be mutually replaced with a transceiver.

[0456] In some embodiments, the processing module can be one module or can include multiple sub-modules. Alternatively, the multiple sub-modules are respectively configured to perform all or part of the steps required by the processing module. Alternatively, the processing module can be mutually replaced with a processor.

[0457] FIG. 6a is a structural schematic diagram of a communication device 6100 according to an embodiment of the present disclosure. The communication device 6100 can be a network device (for example, an access network device, a core network device, and the like), a terminal (for example, a user equipment, and the like), a chip, a chip system, or a processor supporting the network device to implement any of the above methods, or a chip, a chip system, or a processor supporting the terminal to implement any of the above methods. The communication device 6100 can be used to implement the methods described in the above method embodiments, and details can be referred to the descriptions in the above method embodiments.

[0458] As shown in FIG. 6a, the communication device 6100 includes one or more processors 6101. The processor 6101 can be a general-purpose processor or a special-purpose processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process a communication protocol and communication data, and the central processing unit can be used to control a communication device (for example, a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, and the like), execute a program, and process data of the program. Alternatively, the communication device 6100 is configured to implement any of the above methods. Alternatively, the one or more processors 6101 are configured to invoke instructions to cause the communication device 6100 to implement any of the above methods.

[0459] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceiver 6102 performs at least one of the communication steps of sending and / or receiving in the above-described methods, and the processor 6101 performs at least one of the other steps. In alternative embodiments, the transceiver can include a receiver and / or a transmitter, which can be separate or integrated together. Alternatively, the terms transceiver, transceiving unit, transceiver, transceiving circuit, interface circuit, interface, etc. can be replaced by each other, the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc. can be replaced by each other, and the terms receiver, receiving unit, receiver, receiving circuit, etc. can be replaced by each other.

[0460] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data. Alternatively, all or part of the memory 6103 can also be outside the communication device 6100. In alternative embodiments, the communication device 6100 can include one or more interface circuits 6104. Alternatively, the interface circuit 6104 is connected with the memory 6103, and the interface circuit 6104 can be used to receive data from the memory 6103 or other devices, and can be used to send data to the memory 6103 or other devices. For example, the interface circuit 6104 can read the data stored in the memory 6103 and send the data to the processor 6101.

[0461] The communication device 6100 described in the above embodiments can be a network device or a terminal, but the scope of the communication device 6100 described in the present disclosure is not limited thereto, and the structure of the communication device 6100 can not be limited by Figure 6a. The communication device can be a standalone device or can be part of a larger device. For example, the communication device can be: 1) a standalone integrated circuit (IC), or a chip, or a chip system or subsystem; (2) a set of one or more ICs, which can optionally include storage components for storing data, programs; (3) an ASIC, such as a Modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, a smart terminal device, a cellular phone, a wireless device, a handset, a mobile unit, a vehicle-mounted device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0462] Figure 6b is a structural schematic diagram of a chip 6200 according to an embodiment of the present disclosure. For the case where the communication device 6100 is a chip or a chip system, the structural schematic diagram of the chip 6200 shown in Figure 6b can be referred to, but is not limited thereto.

[0463] The chip 6200 includes one or more processors 6201. The chip 6200 is configured to perform any of the above methods.

[0464] In some embodiments, chip 6200 further includes one or more interface circuits 6202. Optionally, the terms interface circuit, interface, transceiver pin, and the like can be substituted for one another. In some embodiments, chip 6200 further includes one or more memories 6203 for storing data. Optionally, all or part of memory 6203 can be external to chip 6200. Optionally, interface circuit 6202 is connected to memory 6203, and interface circuit 6202 can be used to receive data from memory 6203 or other devices, and interface circuit 6202 can be used to send data to memory 6203 or other devices. For example, interface circuit 6202 can read data stored in memory 6203 and send the data to processor 6201.

[0465] In some embodiments, interface circuit 6202 performs at least one of the communication steps of sending and / or receiving in the above-described methods. The performance of interface circuit 6202 in the communication steps of sending and / or receiving in the above-described methods refers to, for example, the performance of data interaction between processor 6201, chip 6200, memory 6203, or transceiver devices by interface circuit 6202. In some embodiments, processor 6201 performs at least one of the other steps.

[0466] The modules and / or devices described in each of the embodiments of virtual devices, physical devices, chips, and the like can be combined or separated as appropriate. Optionally, some or all of the steps can also be performed by a plurality of modules and / or devices in cooperation, which is not limited herein.

[0467] The disclosure further proposes a storage medium having instructions stored thereon, which, when executed on communication device 6100, cause communication device 6100 to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited to this, and can also be a storage medium readable by other devices. Optionally, the storage medium can be a non-transitory storage medium, but is not limited to this, and can also be a transitory storage medium.

[0468] The disclosure further proposes a program product, which, when executed by communication device 6100, causes communication device 6100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0469] The disclosure further proposes a computer program, which, when executed on a computer, causes the computer to perform any of the above methods. Industrial applicability

[0470] The terminal can know the random access priority parameter configured by the network device for requesting SIB1 or SSB by receiving the configuration information, so that the terminal can request SIB1 or SSB based on the random access priority parameter, reduce the request delay, and improve the communication efficiency.

Claims

1. A communication method, executed by a terminal, the method comprising: The system receives configuration information, which is used to configure the random access priority parameters of the first random access channel (RACH) procedure. The first RACH procedure is used by the terminal to request system information block SIB1 or synchronization signal block SSB.

2. The method as described in claim 1, wherein, The random access priority parameter includes at least one of the following: The uplink power ramp-up step size during the first RACH process; The scaling factor of the backoff indication BI sent uplink during the first RACH process; The initial receive power indicated by the network device; The maximum number of preamble transmissions during the first RACH process.

3. The method as described in claim 2, wherein, The random access priority parameter satisfies at least one of the following: The power ramp-up step size is greater than the first value; The maximum number of transmissions is less than the second value; the first value is the power ramp step size for other RACH processes besides the first RACH process, and the second value is the maximum number of transmissions for other RACH processes besides the first RACH process.

4. The method as described in any one of claims 1 to 3, wherein, The method further includes: Based on the configuration information, the SIB1 or the SSB is requested during the first RACH procedure.

5. The method of claim 4, wherein, The first RACH process includes: Send the first message MSG1; During the runtime of the first timer, receive the second message MSG2.

6. The method of claim 5, wherein, The MSG1 is used to request the SIB1 or the SSB, and the MSG2 includes feedback information, which is a response to the request for the SIB1 or the SSB.

7. The method of claim 5 or 6, wherein, The first timer starts after the terminal sends the MSG1. The runtime of the first timer is less than a third value, which is the runtime of the response timer for other RACH procedures besides the first RACH procedure.

8. The method as described in any one of claims 5 to 7, wherein, The runtime of the first timer is configured by the network device.

9. The method according to any one of claims 5 to 8, wherein, The method further includes: The Physical Downlink Control Channel (PDCCH) is received based on the Radio Network Temporary Identifier (RNTI). The PDCCH is used to schedule the MSG2, and the PDCCH is scrambled by the RNTI.

10. The method of claim 9, wherein, The RNTI satisfies one of the following: The network device is configured; Defined by the protocol; The bias is determined based on the random access RA-RNTI of the first RACH procedure and the network device configuration.

11. The method of claim 9, wherein, The PDCCH is sent in a first search space, wherein the first search space is the search space of the Remaining Minimum System Information (RMSI), or the search space configured by the network device for the PDCCH.

12. The method as described in any one of claims 5, 7 to 11, wherein, The first RACH process also includes: Send a third message MSG3, which is used to request either SIB1 or SSB.

13. The method of claim 12, wherein, The first RACH process also includes: During the duration of the second timer, a fourth message MSG4 is received, which includes feedback information, namely, feedback on the request of SIB1 or SSB.

14. The method of claim 13, wherein, The MSG3 includes at least one of the following: Instruction information used to indicate a request for SIB1; The terminal expects the SSB index set for sending SIB1.

15. The method of claim 12, wherein, The second timer starts after the terminal sends the MSG3. The runtime of the second timer is less than the fourth value, which is the runtime of the conflict timer used for other RACH procedures besides the first RACH procedure.

16. The method as claimed in any one of claims 12 to 15, wherein, The runtime of the second timer is configured by the network device.

17. The method as claimed in any one of claims 4 to 16, wherein, The method further includes: Receive the SIB1 or the SSB.

18. The method of claim 17, wherein, The SIB1 or the SSB satisfies at least one of the following: Transmitted in beam scanning mode according to the first SSB index order, wherein the first SSB index is the index of the SSB transmitted by the cell corresponding to the configuration information; Send based on the second SSB index indicated by the terminal; Send in the SSB set that includes the second SSB index.

19. The method of claim 18, wherein, The second SSB index includes at least one of the following: The set of SSB indexes indicated in MSG3; The SSB index of the RACH resource mapping, wherein the RACH resource includes the preamble and / or random access timing (RO) corresponding to the first RACH procedure.

20. The method according to any one of claims 4 to 19, wherein, If the first RACH procedure fails, the terminal performs at least one of the following: The status of the cell corresponding to the configuration information is determined to be an access-prohibited state, and the time of the access-prohibited state is less than the fifth value; Re-initiate the RACH procedure to request either SIB1 or SSB; Perform cell reselection; Initiate the RACH process for the cell to be reselected.

21. A communication method performed by a network device, the method comprising: Send configuration information, which is used to configure the random access priority parameters of the first random access channel RACH procedure. The first RACH procedure is used by the terminal to request system information block SIB1 or synchronization signal block SSB.

22. The method of claim 21, wherein, The random access priority parameter includes at least one of the following: The uplink power ramp-up step size during the first RACH process; The scaling factor of the backoff indication BI sent uplink during the first RACH process; The initial received power indicated by the network device; The maximum number of preamble transmissions during the first RACH process.

23. The method of claim 22, wherein, The random access priority parameter satisfies at least one of the following: The power ramp-up step size is greater than the first value; The maximum number of transmissions is less than the second value; wherein the first value is the power ramp step size for other RACH processes besides the first RACH process, and the second value is the maximum number of transmissions for other RACH processes besides the first RACH process.

24. The method according to any one of claims 21 to 23, wherein, The method further includes: Receive information requesting the SIB1 or the SSB during the first RACH process.

25. The method of claim 24, wherein, The first RACH process includes: Receive first message MSG1; Within the duration of the first timer, send the second message MSG2.

26. The method of claim 25, wherein, MSG1 is information requesting SIB1 or SSB, and MSG2 includes feedback information, which is feedback on the request to SIB1 or SSB.

27. The method of claim 25 or 26, wherein, The first timer starts after the terminal sends the MSG1. The runtime of the first timer is less than a third value, which is the runtime of the response timer for other RACH procedures besides the first RACH procedure.

28. The method according to any one of claims 25 to 27, wherein, The runtime of the first timer is configured by the network device.

29. The method as claimed in any one of claims 25 to 28, wherein, The method further includes: Transmit the RNTI-scrambled Physical Downlink Control Channel (PDCCH), which is used to schedule the MSG2.

30. The method of claim 29, wherein, The RNTI satisfies one of the following: The network device is configured; Defined by the protocol; The bias is determined based on the random access RA-RNTI of the first RACH procedure and the network device configuration.

31. The method of claim 29, wherein, The PDCCH is sent in a first search space, wherein the first search space is the search space of the Remaining Minimum System Information (RMSI), or the search space configured by the network device for the PDCCH.

32. The method according to any one of claims 25, 27 to 31, wherein, The first RACH process also includes: Receive a third message MSG3, which is used to request either SIB1 or SSB.

33. The method of claim 32, wherein, The first RACH process also includes: During the duration of the second timer, a fourth message MSG4 is sent, which includes feedback information, namely, feedback on the request of SIB1 or SSB.

34. The method of claim 33, wherein, The MSG3 includes at least one of the following: Instruction information used to indicate a request for SIB1; The terminal expects the SSB index set for sending SIB1.

35. The method of claim 32, wherein, The second timer starts after the terminal sends the MSG3. The runtime of the second timer is less than the fourth value, which is the runtime of the conflict timer used for other RACH procedures besides the first RACH procedure.

36. The method according to any one of claims 32 to 35, wherein, The runtime of the second timer is configured by the network device.

37. The method of any one of claims 24 to 36, wherein, The method further includes: Send the SIB1 or the SSB.

38. The method of claim 37, wherein, The SIB1 or the SSB satisfies at least one of the following: Transmitted in beam scanning mode according to the first SSB index order, wherein the first SSB index is the index of the SSB transmitted by the cell corresponding to the configuration information; Send based on the second SSB index indicated by the terminal; Send in the SSB set that includes the second SSB index.

39. The method of claim 38, wherein, The second SSB index includes at least one of the following: The set of SSB indexes indicated in MSG3; The SSB index of the RACH resource mapping, wherein the RACH resource includes the preamble and / or random access timing (RO) corresponding to the first RACH procedure.

40. A terminal, comprising: The transceiver module is used to receive configuration information, which is used to configure the random access priority parameters of the first random access channel (RACH) procedure. The first RACH procedure is used by the terminal to request system information block SIB1 or synchronization signal block SSB.

41. A network device, comprising: The transceiver module is used to send configuration information, which is used to configure the random access priority parameters of the first random access channel (RACH) procedure. The first RACH procedure is used by the terminal to request system information block SIB1 or synchronization signal block SSB.

42. A terminal, comprising: One or more processors; The terminal is configured to implement the method according to any one of claims 1 to 20.

43. A network device, comprising: One or more processors; The network device is configured to implement the method as described in any one of claims 21 to 39.

44. A communication system comprising a terminal and network equipment, wherein, The terminal is configured to implement the method as described in any one of claims 1 to 20; The network device is configured to implement the method as described in any one of claims 21 to 39.

45. A storage medium storing instructions, wherein, When the instructions are executed on the communication device, the communication device performs the method as described in any one of claims 1 to 20, or any one of claims 21 to 39.

46. ​​A program product, wherein, When the program product is executed by a communication device, the communication device performs the method as described in any one of claims 1 to 20, or any one of claims 21 to 39.

Images