CN109587811B

CN109587811B - Information acquisition method and terminal

Info

Publication number: CN109587811B
Application number: CN201710899198.5A
Authority: CN
Inventors: 范强; 娄崇; 黄曲芳
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2017-09-28
Filing date: 2017-09-28
Publication date: 2021-01-15
Anticipated expiration: 2037-09-28
Also published as: CN109587811A; WO2019062582A1

Abstract

The application discloses an information acquisition method and a terminal, wherein the method comprises the following steps: if the terminal monitors a first RAR (random access request) which is transmitted by an access network element and comprises the identifier of the first lead code between the first time and the second time, determining to end the request of the first information through the random access process; the first time is the time when the terminal triggers the request of N information through a random access process, or the time when the terminal determines to request the first information again through the random access process, wherein the first information is one of the N information; n is an integer greater than 0; the first lead code is used for requesting the first information, and the second time is the starting time of the terminal for sending the first lead code; and the terminal receives the first information transmitted by the access network element.

Description

Information acquisition method and terminal

Technical Field

The present application relates to the field of communications technologies, and in particular, to an information obtaining method and a terminal.

Background

In a New Radio (NR) System in the future, System Information (SI) is divided into Minimum System Information (MSI) and Other System Information (OSI) that are the most basic System Information required for a terminal to access a network. The MSI is transmitted periodically by the network, and the OSI is transmitted by network trigger or by request of the terminal. For a terminal in idle (idle) state or deactivated (inactive) state, an On-Demand system information (On-Demand SI) may be requested by starting a random access procedure. The request process may be based on message 1(Msg1) or may be based on message 3(Msg 3).

In the Msg 1-based request process, the terminal firstly sends a preamble (Msg1) corresponding to the requested SI on a Physical Random Access Channel (PRACH); after receiving the preamble, the access network element sends a Random Access Response (RAR) including information to the terminal. The terminal monitors a Physical Downlink Control Channel (PDCCH) within a Random Access Response (RAR) time window for a fixed time period after sending the preamble, so as to receive the RAR. If the RAR replied by the access network element is not received in the RAR time window or the received RAR does not have the identifier of the lead code sent by the terminal, the system information requested according to the requirement is considered to be failed; after waiting for a period of time, the terminal re-initiates the random access process. And if the terminal receives the RAR comprising the identifier of the lead code, determining that an access network element sends the SI corresponding to the lead code.

In the above process, each time the terminal requests the system information, it needs to wait for a long time to determine whether the system information required for the request is successful, which results in low efficiency of requesting the system information.

Disclosure of Invention

The application provides an information acquisition method and a terminal, which are used for improving the efficiency of requesting information by the terminal.

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

if the terminal monitors a first RAR (random access request) which is transmitted by the access network element and comprises the identifier of the first lead code between the first time and the second time, determining to end the request of the first information through the random access process;

the first time is the time when the terminal triggers the request of N information through a random access process, or the time when the terminal determines to request the first information again through the random access process, wherein the first information is one of the N information; n is an integer greater than 0; the first lead code is used for requesting the first information, and the second time is the starting time of the terminal for sending the first lead code;

and the terminal receives the first information transmitted by the access network element.

By the method, the terminal starts to monitor whether the access network element transmits the first RAR at the first time before the terminal sends the first lead code, so that when the first RAR is monitored, the access network element is determined to transmit the first information corresponding to the first lead code, the process of requesting the first information through the random access process can be skipped, and the access network element is directly waited to transmit the first information. Through the process, the terminal reduces the time overhead required by the first information request and improves the efficiency of the first information request.

In an optional embodiment, after determining that the first information is requested through the random access procedure, the method further includes:

the terminal determines that the first preamble is no longer sent to the access network element.

In an alternative embodiment, the method comprises:

if the terminal does not monitor the first RAR between the first time and the second time, the terminal sends the first lead code to the access network element;

if the terminal monitors the first RAR from the third time to the fourth time, determining that the first information is successfully requested through a random access process;

the third time is the starting time of the terminal for sending the first lead code; the fourth time is the start time of the RAR window corresponding to the first preamble.

By the method, the terminal starts to monitor the first RAR at the third time while sending the first lead code, so that when the first RAR is monitored, the access network element is determined to transmit the first information corresponding to the first lead code, the random access process of requesting the first information can be ended in advance, and the access network element is waited to transmit the first information. Through the process, the terminal reduces the time overhead required by the first information request and improves the efficiency of the first information request.

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

the terminal sends a first lead code to an access network element;

if the terminal monitors a first Random Access Response (RAR) comprising the identifier of the first lead code at a third time to a fourth time, determining that the first information is successfully requested through a random access process;

wherein the first information is one of the N pieces of information; n is an integer greater than 0; the first preamble is a preamble used for requesting the first information, and the third time is a starting time for the terminal to transmit the first preamble; the fourth time is the start time of the RAR window corresponding to the first lead code;

By the method, the terminal starts to monitor the first RAR at the third time while sending the first lead code, so that when the first RAR is monitored, the access network element is determined to transmit the first information corresponding to the first lead code, the random access process for requesting the first information can be ended in advance, and the access network element is waited to transmit the first information. Through the process, the terminal reduces the time overhead required by the first information request and improves the efficiency of the first information request.

In an optional embodiment, the method further comprises:

and if the terminal does not monitor the first RAR transmitted by the access network element between the third time and the fourth time, monitoring a second RAR in an RAR window corresponding to the first lead code, wherein the second RAR is the RAR sent by the access network element after receiving the first lead code sent by the terminal.

In an optional embodiment, N is an integer greater than 1, and the method further comprises:

if the terminal monitors a third RAR (random access request) transmitted by the access network element and comprising the identifier of the second lead code between the first time and the fifth time, determining that the second lead code is not sent to the access network element any more; the fifth time is any time after the first time and before the end time of the RAR window corresponding to the first preamble.

The second preamble is a preamble for requesting the second information, and the second information is any one of the N pieces of information except the first information.

By the method, the terminal starts to monitor whether the access network element transmits the third RAR at the first time before the terminal sends the second lead code, so that when the third RAR is monitored, the access network element is determined to transmit the second information corresponding to the second lead code, the process of requesting the second information through the random access process can be skipped, and the access network element is waited to transmit the second information. Through the process, the terminal reduces the time overhead required by requesting the second information and improves the efficiency of requesting the second information.

In an alternative embodiment, N is an integer greater than 1;

the first information is information with the highest priority in K information, and the K information is information which needs to be acquired by the terminal in the N information; the priority is configured for the network element of the access network, or the priority is preset; n is greater than or equal to K;

or, the first information is determined and indicated to a Media Access Control (MAC) entity of the terminal by the terminal through a Radio Resource Control (RRC) entity of the terminal;

or the first information is determined by the terminal through an MAC entity of the terminal;

or the first information is determined by the terminal through an application layer entity of the terminal and is indicated to an MAC entity of the terminal.

In an optional implementation manner, after the terminal determines to end the request of the first information through the random access procedure or determines to successfully request the first information through the random access procedure, the method further includes:

and the terminal informs the RRC entity of the terminal through the MAC entity of the terminal, and the access network element transmits the first information.

In an optional implementation manner, after the terminal receives the first information transmitted by the access network element, the method further includes:

the terminal informs a MAC entity of the terminal to terminate a random access procedure for requesting the first information through the first preamble through an RRC entity of the terminal.

In a third aspect, an embodiment of the present application provides a terminal, including:

a processing unit, configured to determine to end requesting the first information through a random access procedure if a first random access response RAR including an identifier of a first preamble transmitted by the access network element is monitored between a first time and a second time through the transceiver unit;

the transceiver unit is configured to receive the first information transmitted by the access network element.

In an optional embodiment, after determining that the first information is requested through the random access procedure, the processing unit is further configured to:

determining to no longer send the first preamble to the access network element.

In an optional implementation manner, if the transceiver unit does not monitor the first RAR between the first time and the second time, the transceiver unit sends the first preamble to the access network element;

the processing unit determines to successfully request the first information through a random access process if the first RAR is monitored from the third time to the fourth time through the transceiver unit;

In a fourth aspect, an embodiment of the present application provides a terminal, including:

a receiving and sending unit, configured to send a first preamble to an access network element;

a processing unit, configured to determine that a first information request is successfully made through a random access procedure if a first random access response RAR including an identifier of the first preamble is monitored at a third time to a fourth time;

In an optional implementation manner, the transceiver unit is further configured to:

and if the first RAR transmitted by the access network element is not monitored between the third time and the fourth time, monitoring a second RAR in an RAR window corresponding to the first preamble, where the second RAR is an RAR sent by the access network element after receiving the first preamble sent by the terminal.

In an optional embodiment, N is an integer greater than 1, and the processing unit is further configured to:

if a third RAR (random access request message) transmitted by the access network element and including an identifier of a second lead code is monitored between the first time and the fifth time through the transceiver unit, determining that the second lead code is not sent to the access network element any more; the fifth time is any time after the first time and before the end time of the RAR window corresponding to the first preamble.

In an alternative embodiment, N is an integer greater than 1;

In an optional embodiment, after determining that the first information is requested by the random access procedure at the end or determining that the first information is successfully requested by the random access procedure, the processing unit is further configured to:

and informing the RRC entity of the terminal through the MAC entity of the terminal, wherein the access network element transmits the first information.

In an optional implementation manner, after receiving the first information transmitted by the access network element, the processing unit is further configured to:

notifying, by an RRC entity of the terminal, an MAC entity of the terminal to terminate a random access procedure for requesting the first information through the first preamble.

In a fifth aspect, an embodiment of the present application provides a communication method, where the method includes:

a terminal receives a random access response RAR from an access network element; the RAR comprises duration indication information, and the duration indication information is used for indicating the transmission duration of the message 3;

and the terminal sends the message 3 according to the duration indication information.

In an optional implementation manner, the duration indication information is located in an uplink grant field of the RAR.

In an optional embodiment, the transmission duration is the number of symbols occupied by the message 3, or the time length of the message 3 when transmitting.

In a sixth aspect, an embodiment of the present application provides a communication method, where the method includes:

the terminal receives a first message from an access network element; the first message comprises duration indication information, and the duration indication information is used for indicating the transmission duration of the second message; the first message is system information; the second message is any one of the following messages: message 3 in the random access process; a paging message sent by the access network element; single cell point-to-multipoint SC-PTM messages; the system information; a semi-persistent scheduling (SPS) message;

and the terminal receives or sends the second message according to the duration indication information.

In an optional implementation manner, the duration indication information is located in downlink control information DCI of the first message.

In an optional implementation manner, the transmission duration is the number of symbols occupied by the second message, or a time length for which the second message lasts when being transmitted.

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

a receiving and sending unit, configured to receive a random access response RAR from an access network element; the RAR comprises duration indication information, and the duration indication information is used for indicating the transmission duration of the message 3;

and the processing unit is used for sending the message 3 through the receiving and sending unit according to the duration indication information.

In an eighth aspect, an embodiment of the present application provides a terminal, including:

a receiving and sending unit, configured to receive a first message from an access network element; the first message comprises duration indication information, and the duration indication information is used for indicating the transmission duration of the second message; the first message is system information; the second message is any one of the following messages: message 3 in the random access process; a paging message sent by the access network element; single cell point-to-multipoint SC-PTM messages; the system information; a semi-persistent scheduling (SPS) message;

and the processing unit is used for receiving or sending the second message through the transceiving unit according to the duration indication information.

In a ninth aspect, embodiments of the present application provide a computer-readable storage medium having computer-readable instructions stored thereon, which, when read and executed by a computer, cause the computer to perform the method of any one of the above aspects or any one of the possible designs of any one of the above aspects.

In a tenth aspect, embodiments of the present application provide a computer program product, which when read and executed by a computer, causes the computer to perform the method of any one of the above aspects or any one of the possible designs of any one of the aspects.

In an eleventh aspect, embodiments of the present application provide a chip, where the chip is connected to a memory, and is configured to read and execute a software program stored in the memory, so as to implement the method in any one of the above aspects or any one of the possible designs of any one of the above aspects.

Drawings

Fig. 1 is a diagram illustrating a contention random access procedure in the prior art;

fig. 2 is a schematic flow chart of an information acquisition method according to an embodiment of the present disclosure;

fig. 3(a) to fig. 3(b) are schematic diagrams of a listening time provided in an embodiment of the present application;

fig. 4(a) to fig. 4(b) are schematic diagrams of a listening time provided in the embodiment of the present application;

fig. 5 is a schematic view of a listening time provided in an embodiment of the present application;

fig. 6 is a schematic view of a listening time provided in an embodiment of the present application;

fig. 7 is a flowchart illustrating a communication method according to an embodiment of the present application;

fig. 8 is a schematic diagram of a random access response structure according to an embodiment of the present application;

fig. 9 is a schematic diagram of a random access response structure according to an embodiment of the present application;

fig. 10 is a flowchart illustrating a communication method according to an embodiment of the present application;

fig. 11 is a flowchart illustrating a communication method according to an embodiment of the present application;

fig. 12(a) to 12(d) are schematic diagrams of message structures provided in the embodiment of the present application;

fig. 13 is a schematic structural diagram of a terminal according to an embodiment of the present application;

fig. 14 is a schematic structural diagram of a terminal according to an embodiment of the present application;

fig. 15 is a schematic structural diagram of a terminal according to an embodiment of the present application;

fig. 16 is a schematic structural diagram of a terminal according to an embodiment of the present application.

Detailed Description

The present application will be described in further detail below with reference to the accompanying drawings.

The embodiment of the application can be applied to various mobile communication systems, such as: new Radio (NR) systems (also referred to as 5G systems), Long Term Evolution (LTE) systems, Advanced Long Term Evolution (LTE-a) systems, evolved Long Term Evolution (LTE) systems, and other mobile communication systems.

Hereinafter, some terms in the present application are explained to facilitate understanding by those skilled in the art.

1) A terminal, also called a User Equipment (UE), is a device providing voice and/or data connectivity to a User, for example, a handheld device with a wireless connection function, a vehicle-mounted device, and so on. Common terminals include, for example: the mobile phone includes a mobile phone, a tablet computer, a notebook computer, a palm computer, a Mobile Internet Device (MID), and a wearable device such as a smart watch, a smart bracelet, a pedometer, and the like.

2) The access network element may be a common base station (e.g., a Node B or an eNB), may be a New Radio controller (New Radio controller, NR controller), may be a gnon B (gNB) in a 5G system, may be a Centralized network element (Centralized Unit), may be a New Radio base station, may be a Radio remote module, may be a micro base station, may be a relay (relay), may be a Distributed network element (Distributed Unit), may be a Reception Point (Transmission Reception Point, TRP), a Transmission Point (Transmission Point, TP), or any other Radio access device, but the embodiment of the present invention is not limited thereto.

3) Message 3(Msg3), message sent by the terminal to the base station in step three of the random access procedure. The Msg3 can be a L2 message or a L3 message, the L2 message can be a Media Access Control (MAC) Control cell, and the L3 message can be an RRC message (RRC connection establishment request, RRC connection re-establishment, etc.).

Fig. 1 is a schematic diagram illustrating a contention random access procedure in the prior art.

S101: a terminal transmits a Random Access preamble (preamble) to a base station, where the preamble is transmitted on a Physical Random Access Channel (PRACH). This message may also be referred to as message 1(Msg 1).

S102: the base station replies a Random Access Response (RAR) message to the terminal.

This message may also be referred to as message 2(Msg 2).

S103: the terminal sends Msg3 to the base station, Msg3 may be a L2 message or a L3 message.

The L2 message may be a MAC control information element, and the L3 message may be an RRC connection setup request message or an RRC connection re-setup message, etc.

S104: the base station feeds back a contention resolution message, which may be an RRC message (e.g., RRC connection setup, etc.), to the terminal, which may also be referred to as message 4(Msg 4).

In the NR system in question, a terminal may request On-Demand (On-Demand) system information from an access network element through a random access procedure. In the invention, the information that the terminal can request the access network element through the random access process is not limited to the information such as system information and the like.

With reference to the foregoing description, as shown in fig. 2, a schematic flow chart of an information obtaining method provided in the embodiment of the present application is shown. The method comprises the following steps:

step 201: and if the terminal monitors a first Random Access Response (RAR) which is transmitted by the access network element and comprises the identifier of the first lead code between the first time and the second time, the terminal determines to end the request of the first information through the random access process.

The first time is the time when the terminal triggers the request of N information through a random access process, or the time when the terminal determines to request the first information again through the random access process, wherein the first information is one of the N information; n is an integer greater than 0; the first preamble is a preamble for requesting the first information, and the second time is a start time of the terminal transmitting the first preamble.

It should be noted that the terminal is in an idle (idle) state or an inactive (inactive) state.

As described above, in the embodiment of the present application, any one of the N pieces of Information may be Information such as System Information, and further, any one of the N pieces of Information may be Other System Information (OSI).

Step 202: and the terminal receives the first information transmitted by the access network element.

In step 201, when the terminal determines that the information is required to be requested, a Radio Resource Control (RRC) entity of the terminal may trigger a Medium Access Control (MAC) entity of the terminal to initiate a random Access process, and at this time, the terminal may determine N preambles for requesting the N information, a time-frequency Resource for transmitting a first preamble for requesting the first information, and the like.

Optionally, when N is greater than 1, the terminal may determine the first information from the N pieces of information first. In a first possible implementation manner, the terminal may determine information with the highest priority among K pieces of information as the first information, where the K pieces of information are information that the terminal needs to acquire, and N is greater than or equal to K. The priority may be configured for the access network element, for example, the access network element may broadcast the most basic System Information (MSI) including the priority of the N pieces of Information, so as to configure the priority of the N pieces of Information; the priority may also be preset, i.e. pre-agreed between the terminal and the network element of the access network.

In a second possible implementation manner, the first information is determined and indicated to a media access control MAC entity of the terminal by the RRC entity of the terminal.

In a third possible implementation manner, the first information is determined by the terminal through an MAC entity of the terminal.

In a fourth possible implementation manner, the first information is determined by the terminal through an application layer entity of the terminal and is indicated to an MAC entity of the terminal.

In this embodiment, in order to improve the efficiency of the terminal acquiring the information, the terminal may start to monitor whether the access network element transmits one or more of the N pieces of information after triggering the time of requesting the N pieces of information through the random access process. The process of terminal monitoring can be divided into different time periods, and the following description takes the terminal requesting the first information as an example:

first, the terminal may listen between the first time and the second time whether the access network element transmits a first RAR comprising an identification of the first preamble. The length of time between the first time and the second time may also be referred to as a first time window.

For example, as shown in fig. 3(a), a schematic view of listening time provided in the embodiment of the present application is shown. In fig. 3(a), the first time is a time when the terminal triggers to request N information through the random access procedure, and the second time is a start time when the terminal transmits the first preamble, i.e., a start time located in the duration of the first preamble transmission.

Of course, fig. 3(a) is only an example, and the first time may also be located at any time after the time when the terminal triggers the request of N information through the random access procedure and before the time when the terminal sends the first preamble; the second time may be any time after the first time and before the time when the terminal transmits the first preamble. For example, as shown in fig. 3(b), the first time is after the time when the terminal triggers the request of N information through the random access procedure, and the second time is before the time when the terminal transmits the first preamble, and the first time window may be as shown in fig. 3 (b).

Optionally, if the terminal has sent the first preamble to the access network element before, but the access network element does not send the second RAR corresponding to the first preamble to the terminal, that is, the terminal fails to request the first information based on the first preamble, the terminal may re-initiate a random access procedure to request the first information, where the first time may be a time when the terminal determines to request the first information again through the random access procedure. The first time may also be any time after the terminal determines the time to re-request the first information through the random access procedure and before the time when the terminal transmits the first preamble.

In this process, if the terminal monitors the first RAR including the identifier of the first preamble transmitted by the access network element between the first time and the second time, it may be determined that the first preamble for requesting the first information does not need to be sent to the access network element, so that the request for the first information through the random access procedure may be ended. At this time, the terminal notifies the RRC entity of the terminal through the MAC entity of the terminal, and the access network element transmits the first information.

Of course, the terminal may also continue to send the first preamble to the access network element, which is not limited in this embodiment.

It should be noted that the first RAR monitored by the terminal is not a response message of the access network element to the reception of the first preamble sent by the terminal, but a response message of the preamble sent by another terminal. In this embodiment of the present application, one piece of information may correspond to at least one preamble, so when the terminal determines that the monitored first RAR includes the identifier of the preamble corresponding to the first information, it may be determined that there are other terminals that are also requesting the first information, and the access network element is ready to transmit the first information, so that the terminal may not send the first preamble to the access network element any more. Optionally, after monitoring the first RAR between the first time and the second time, the terminal may determine to request the access network element for the second information, and send a second preamble for requesting the second message. The second information is any one of the N pieces of information except the first information.

In the process, if the terminal does not monitor the first RAR including the identifier of the first preamble transmitted by the access network element between the first time and the second time, the terminal sends the first preamble to the access network element.

The terminal may monitor whether the access network element transmits the first RAR including the identifier of the first preamble between the third time and the fourth time while transmitting the first preamble. The length of time between the third time and the fourth time may also be referred to as a second time window. The third time is the starting time of the terminal for sending the first lead code; the fourth time is the start time of the RAR window corresponding to the first preamble. The RAR window is a time period for monitoring whether an access network element sends a second RAR corresponding to a first preamble to the terminal after the terminal sends the first preamble, and specific contents of the RAR window may refer to descriptions in the prior art and are not described herein again.

For example, as shown in fig. 4(a), a schematic view of listening time provided in the embodiment of the present application is shown. In fig. 4(a), the first time is a time when the terminal triggers a request for N information through a random access procedure, the third time is a start time when the terminal sends the first preamble, that is, a start time of a duration of a first preamble transmission, and the fourth time is a start time of a RAR window corresponding to the first preamble.

Of course, fig. 4(a) is only an example, and the third time may be located at any time after the time when the terminal transmits the first preamble and before the start time of the RAR window; the fourth time may be any time after the third time and before the start time of the RAR window. For example, as shown in fig. 4(b), the third time may be located after the time when the terminal transmits the first preamble, and the fourth time may also be located before the start time of the RAR window, in which case the second time window may be as shown in fig. 4 (b).

It should be noted that, in the LTE system, in the random access process, after the terminal sends the preamble, a time after the terminal starts after a fixed time interval is taken as a start time of the RAR window. The start time of the fixed time interval is the end time of a subframe (subframe) in which the preamble is transmitted, and the length of the fixed time interval is an integer multiple of the subframe length, so the RAR window always starts at a subframe boundary. In NR, a start time of the fixed time interval is an end time of a symbol (symbol) of a preamble that is transmitted, and a length of the fixed time interval is an integer multiple of a symbol length or a subframe length of a carrier of the RAR received by the terminal. Since the NR supports different symbol lengths of uplink and downlink carriers in a cell, the end position of the fixed time interval may fall within the symbol/subframe of the carrier on which the terminal receives the RAR.

Referring to fig. 5, in this embodiment, after the terminal finishes transmitting the current symbol of the preamble on the first carrier, after waiting for a fixed Time Interval of the duration of S symbols or subframes or Transmission Time Intervals (TTIs) in the second carrier, if it is determined that the end Time of the fixed Time Interval is aligned with the symbol or subframe or TTI boundary of the second carrier, determining the end Time of the fixed Time Interval as the start Time of the RAR window, otherwise, determining the end Time of the symbol or subframe or TTI including the end Time of the fixed Time Interval as the start Time of the RAR window. And the second carrier is a carrier for receiving the RAR by the terminal, S is a positive integer greater than 0, and S is a preset value and is determined according to actual conditions.

The first carrier and the second carrier may be uplink carriers and downlink carriers configured to one cell, or may be uplink carriers and downlink carriers configured to different cells. Optionally, the first carrier and the second carrier may be uplink partial BandWidth (BWP) and downlink partial BandWidth configured to a cell, or uplink partial BandWidth and downlink partial BandWidth configured to different cells.

And if the terminal monitors the first RAR from the third time to the fourth time, determining that the first information is successfully requested through the random access process, so that the request of the first information through the random access process can be finished. At this time, the terminal notifies the RRC entity of the terminal through the MAC entity of the terminal, and the access network element transmits the first information and determines that the random access process is finished.

Correspondingly, if the terminal does not monitor the first RAR transmitted by the access network element between the third time and the fourth time, a second RAR is monitored in an RAR window corresponding to the first preamble, where the second RAR is an RAR sent by the access network element after receiving the first preamble sent by the terminal.

If the terminal does not monitor the second RAR in the RAR window, it may determine that the request for the first information through the random access procedure fails, and may request the first information by initiating the random access procedure again, and of course, the terminal may also initiate the random access procedure to request the second information at this time. The second information is any one of the N pieces of information except the first information.

It should be noted that, when the terminal requests the first information by initiating the random access procedure again, the used preamble may be the same as or different from the preamble used for requesting the first information last time, which is not limited in this embodiment of the application. For example, the last time the terminal uses the preamble identified by 34 of the preamble to request the access network element to send the first information, and when the terminal requests the first information by initiating the random access procedure again, the terminal may use the preamble identified by 38 of the preamble to request the access network element to send the first information.

In summary, the terminal may start to listen to the RAR including the identity of the first preamble before transmitting the first preamble. The first preamble may not be transmitted if the MAC entity of the terminal listens to the RAR including the identity of the first preamble before transmitting the first preamble. If the terminal transmits the first preamble but listens to the RAR including the identifier of the first preamble before the RAR window corresponding to the first preamble (i.e., the window in which the terminal receives the second RAR) starts, the terminal may not listen to the second RAR in the RAR window corresponding to the first preamble. If the terminal receives the RAR before the end of the RAR window corresponding to the first preamble, it may be determined that the request for the first information through the random access procedure is successful. In the embodiment of the present application, once the MAC entity of the terminal receives the RAR of the identifier of the first preamble in the following 3 cases, it indicates that the first information is successfully requested through the random access procedure:

case 1: the terminal listens (i.e., receives) to a RAR including an identification of the first preamble within a first time window, at which time the first preamble may not be transmitted.

Case 2: the terminal listens (i.e., receives) to the RAR including the identity of the first preamble within a second time window, which is located before the beginning of the RAR window corresponding to the first preamble.

Case 3: the terminal sends the first preamble and receives the RAR including the identifier of the first preamble in the RAR window corresponding to the first preamble.

Further, when N is greater than 1, if the terminal monitors a third RAR including an identifier of a second preamble transmitted by the access network element between the first time and the fifth time, it is determined that the second preamble is no longer transmitted to the access network element, at this time, the terminal notifies an RRC entity of the terminal through an MAC entity of the terminal, and the access network element is to transmit second information corresponding to the second preamble, thereby determining that the second information does not need to be requested through a random access procedure; the second preamble is a preamble for requesting the second information, and the second information is any one of the N pieces of information except the first information. And the fifth time is any time after the first time and before the end time of the RAR window corresponding to the first preamble.

It should be noted that the third RAR monitored by the terminal is a response message of the access network element to the second preamble sent by the other terminal.

For example, as shown in fig. 6, a schematic view of listening time provided in the embodiment of the present application is provided. In fig. 6, the first time is a time when the terminal triggers to request N pieces of information through a random access procedure, and the fifth time is an end time of an RAR window corresponding to the first preamble. Of course, fig. 6 is only an example, and the fifth time may also be located at the time when the terminal transmits the first preamble, or the fifth time may be located at the start time of the RAR window, and the like.

In step 202, after the terminal receives the first information transmitted by the access network element, the terminal may notify the MAC entity of the terminal to terminate the random access procedure for requesting the first information through the first preamble through the RRC entity of the terminal. The reason why the RRC entity of the terminal indicates that the MAC entity of the terminal receives the first information may be: the terminal monitors the first Information in a transmission period of the first Information, or the UE monitors Remaining Minimum System Information (RMSI), and the RMSI includes a transmission instruction of the first Information.

It should be noted that the access network element transmits the first information in a broadcast manner.

The embodiment of the present application further provides a method for indicating a message transmission duration, which will be described in detail below.

Fig. 7 is a schematic flow chart of a communication method according to an embodiment of the present application.

Referring to fig. 7, the method includes:

step 701: an access network element receives a lead code sent by a terminal;

step 702: the access network element sends RAR to the terminal according to the lead code; the RAR comprises duration indication information, and the duration indication information is used for indicating the transmission duration of the message 3.

The transmission duration may also be referred to as a transport block duration (transport block duration).

In the embodiment of the present application, the duration indication information may be a separate field in the RAR, for example, as shown in fig. 8. In fig. 8, the RAR includes a MAC subheader, duration indication information, Tracking Area Code (TAC), Uplink (UP) grant (grant) field, etc., which are not illustrated one by one.

The duration indication information may also be located in an uplink grant field of the RAR. For example, as shown in fig. 9, the RAR includes a MAC subheader, a Tracking Area Code (TAC), an Uplink (UP) grant (grant) field, etc., which are not illustrated in sequence. Wherein, the uplink authorization field includes duration indication information.

In this embodiment, the duration indication information may be a specific value of the transmission duration, for example, the transmission duration is 10 μ s, and at this time, the duration indication information may be 10. After the terminal receives the duration indication information, the transmission duration of the message 3 can be determined to be 10 μ s according to the value of the duration indication information. It should be noted that the time unit indicated by the duration indication information as the transmission duration may be predetermined, and is not described herein again.

The duration indication information may also be an index value corresponding to the transmission duration, for example, the transmission duration is 10 μ s, the corresponding index value is 1, and at this time, the duration indication information may be 1. After the terminal receives the duration indication information, the transmission duration of the message 3 can be determined to be 10 μ s according to the value of the duration indication information. It should be noted that the correspondence between the transmission duration and the index value may be predetermined, that is, preset, between the terminal and the access network element, or may be configured by the access network element through the system information.

The transmission duration may also be the number of symbols occupied by message 3, e.g., message 3 occupies 2 symbols, in which case the duration indication information may be 2. After the terminal receives the duration indication information, the transmission duration of the message 3 can be determined to be 2 symbols according to the value of the duration indication information. Of course, the length of the symbol may be the length of the symbol in the carrier or the bandwidth part that transmits the message 3, or may also be the length of the symbol in the reference carrier or the reference bandwidth part.

Step 703: the terminal receives RAR from an access network element; the RAR comprises duration indication information, and the duration indication information is used for indicating the transmission duration of the message 3.

Step 704: and the terminal sends the message 3 according to the duration indication information.

Optionally, in this embodiment of the application, the transmission duration of the message 3 may also be predetermined, and the RAR may not include the duration indication information. How to agree specifically, the embodiments of the present application are not limited.

It should be noted that the terminal may retransmit the message 3, and when the terminal retransmits the message 3, the transmission duration of the message 3 may be determined by the indication information in the system information, the transmission duration of the message 3 may also be determined according to the duration indication information in the RAR, a predetermined duration may also be used as the transmission duration of the message 3, and the like, which is not limited in the embodiment of the present application. The implementation manner of the indication information in the system information may be the same as the implementation manner of the duration indication information in the RAR, and specifically, reference may be made to the foregoing description, which is not repeated herein.

Fig. 10 is a schematic flow chart of a communication method according to an embodiment of the present application.

Referring to fig. 10, the method includes:

step 1001: the terminal receives a first message from an access network element; the first message comprises duration indication information, and the duration indication information is used for indicating the transmission duration of the second message.

Wherein the first message is system information; the system information may be OSI, MSI, etc.

The second message is any one of the following messages: message 3 in the random access process; a paging message sent by the access network element; a Single Cell-Point To Multipoint (SC-PTM) message; system information; Semi-Persistent Scheduling (SPS) messages.

Step 1002: and the terminal receives or sends the second message according to the duration indication information.

Specifically, when the terminal sends the second message, the terminal sends the second message of the transmission duration indicated by the duration indication information according to the duration indication information; and when receiving the second message, the terminal receives the second message of the transmission time length indicated by the time length indication information according to the time length indication information.

Optionally, the duration indication Information is located in Downlink Control Information (DCI) of the first message.

In this embodiment, the duration indication information may be a specific value of the transmission duration, for example, the transmission duration is 10 μ s, and at this time, the duration indication information may be 10. After the terminal receives the duration indication information, the transmission duration of the second message can be determined to be 10 μ s according to the value of the duration indication information. It should be noted that the time unit indicated by the duration indication information as the transmission duration may be predetermined, and is not described herein again.

The duration indication information may also be an index value corresponding to the transmission duration, for example, the transmission duration is 10 μ s, the corresponding index value is 1, and at this time, the duration indication information may be 1. After the terminal receives the duration indication information, the transmission duration of the second message can be determined to be 10 μ s according to the value of the duration indication information. It should be noted that the correspondence between the transmission duration and the index value may be predetermined, that is, preset, between the terminal and the access network element, or may be configured by the access network element through the system information.

The transmission duration may also be the number of symbols occupied by the second message, e.g., the second message occupies 2 symbols, in which case the duration indication information may be 2. After the terminal receives the duration indication information, the transmission duration of the second message can be determined to be 2 symbols according to the value of the duration indication information. Of course, the length of the symbol may be the length of the symbol in the carrier or the bandwidth portion that transmits the second message, may also be the length of the symbol in the reference carrier or the reference bandwidth portion, may also be the length of the symbol in the carrier or the bandwidth portion that transmits the first message, and the like.

Optionally, in this embodiment of the application, the transmission duration of the second message may also be predetermined, and at this time, the first message may not include the duration indication information. How to agree specifically, the embodiments of the present application are not limited.

Optionally, in this embodiment of the application, the first message may also be the same message as the second message, that is, any one of the messages described above.

When the terminal requests the information on demand based on the request process of the Msg3, the response returned by the access network element is carried in the Msg 4. If the method for solving the conflict by using the Msg4 in the LTE is adopted, only one terminal can successfully solve the conflict at one time. And the information requested by the terminal with successful conflict resolution may be the same as the information requested by other terminals, and the other terminals with failed conflict resolution initiate unnecessary Msg 3-based request processes to continue requesting the information. Therefore, the embodiment of the present application provides a communication method to solve the above problem.

Fig. 11 is a schematic flowchart of a communication method according to an embodiment of the present application.

Referring to fig. 11, the method includes:

step 1101: an access network element generates conflict resolution indicating information, wherein the conflict resolution indicating information is used for indicating whether the request of the access network element for the P information is received successfully or not; p is an integer greater than 0.

The information may be SI, and further, the information may be OSI or the like.

The collision resolution indication information may be a bitmap, each of the P pieces of information corresponds to at least one bit in the collision resolution indication information, and a value of the bit corresponding to each piece of information indicates whether a request for the information is successfully received.

The conflict resolution indication information is a bitmap which comprises M bits, each bit corresponds to one information request, and when the value of the bit is 1, the information request corresponding to the bit is successfully received; when the bit value is 0, it indicates that the information request corresponding to the bit has failed to be received. The value of M is not particularly limited in this embodiment. Of course, the above is only an illustration, and the corresponding relationship between the bit value and whether the information request corresponding to the bit is received successfully may be determined according to the time situation, and is not described herein again.

In this scenario, when two terminals send messages 3 (different beams are used) in the same resource and the information requested by the two terminals is different, as long as the access network element can correctly solve the messages 3 sent by the two terminals on the two beams, the bit corresponding to the requested information carried in the messages 3 can be set to 1. Optionally, the conflict resolution indication information may indicate whether the information request carried in the message 3 including the terminal that successfully resolves the conflict is successfully received, and also include whether the request corresponding to the other one or more information is successfully received by the access network element.

It should be noted that the corresponding relationship between each information and the bit in the bit map may be predetermined by the terminal and the access network element, or may be determined in other manners, for example, the terminal is notified by the system information of the access network element, which is not described herein again.

Step 1102: and the access network element sends a message 4, wherein the message 4 comprises DCI, and the DCI comprises the conflict resolution indication information.

Optionally, the message 4 includes only DCI, and does not include a data portion.

Optionally, the DCI is scrambled by using a preset Radio Network Temporary Identifier (RNTI). The preset RNTI may be an RNTI different from an RNTI (e.g., TC-RNTI) conventionally used by an access network element.

Such a message 4 comprising the collision resolution indication information may be sent simultaneously with a conventional message 4 addressed with a Temporary Cell Radio Network Temporary Identifier (RNTI, TC-RNTI). And the terminal monitors a Physical Downlink Control Channel (PDCCH) by using the TC-RNTI and the preset RNTI in a message 4 window, and the terminal considers that the conflict resolution is successful as long as a response message of any format is received.

After receiving the conflict resolution indication information, the terminal may determine whether the message 3 sent by the terminal is successfully received according to the conflict resolution indication information.

In another possible implementation manner, the message 4 sent by the access network Element may include a MAC Control Element (CE), and the conflict resolution indication information is located in the MAC CE.

In another possible implementation manner, the message 4 sent by the access network element follows a terminal collision solution MAC CE in the LTE system, that is, a Logical Channel InDex (LCID) in a MAC subheader corresponding to the MAC CE in the message 4 is the same as an LCID corresponding to the terminal collision solution MAC CE in the LTE, and meanwhile, DCI of the message 4 is scrambled by using TC-RNTI.

The payload (payload) of the MAC CE in this message 4 contains the contents in the message 3 sent by the terminal, and requires a MAC header to indicate the MAC CE length through the 'L' field.

Optionally, the payload of the MAC CE in the message 4 contains the content in the message 3, but is not multiplexed with other MAC Service Data Units (SDUs), and the MAC header is not required to indicate the MAC CE length through the 'L' field.

Optionally, the payload of the MAC CE in the message 4 contains the content in the message 3 and is padded (padded) to 48 bits.

In another possible implementation manner, the message 4 sent by the access network element continues to use the terminal collision resolution MAC CE in the LTE system, that is, the LCID in the MAC sub-header corresponding to the MAC CE in the message 4 is the same as the LCID corresponding to the terminal collision resolution MAC CE in the LTE, and the scrambling method of the DCI of the message 4 may be:

scrambling method 1: and scrambling by adopting a special RNTI, and monitoring whether corresponding DCI exists by adopting the special RNTI by all terminals initiating the request process based on the message 3. The special RNTI shown may be any RNTI other than TC-RNTI.

Scrambling mode 2: and scrambling by adopting TC-RNTI.

Meanwhile, conflict resolution indication information may be included in the message 4. Wherein the collision resolution indication information may be located in the MAC CE.

In the embodiment of the present application, a MAC subheader structure of a message 4 for random access collision resolution is also provided.

The MAC header structure of the message 4 for random access collision resolution sent by the access network element may be as shown in fig. 12(a) to 12 (d). The LCID (00001) represents a logical channel ID corresponding to the SRB1, but is not limited to only indicating that the MAC SDU (DCCH) comes from a logical channel with LCID (00001) and the signaling radio bearer1 (SRB 1).

As shown in fig. 12(a) to 12(d), R denotes a reserved bit.

E denotes a field for indicating whether more fields are included in the MAC header, and when E is set to '1', denotes that the fields are followed by 'R/F2/E/LCID'; when E is set to '0', it indicates that the next byte starts with a MAC SDU, or a MAC control cell, or padding (padding).

F represents the size of the L field, when the length of the L field indication is less than 128 bytes, the F field is set to 0, otherwise, the F field is set to 1.

L denotes the length of the corresponding MAC SDU or the length of the variable-length MAC control cell, and the length indicated by the L field is in bytes.

LCID (11111) indicates that the payload field corresponding to the MAC subheader is padding.

LCID (11100) indicates that the load domain corresponding to the MAC subheader is a terminal conflict Resolution identifier MAC control cell (UE context Resolution Identity).

The first byte of the MAC subheader shown in fig. 12(a) is used for padding, and the last two bytes respectively indicate that the subsequent MAC payload includes a terminal collision resolution identifier MAC control cell and a MAC SDU from a DCCH logical channel.

The first and second bytes of the MAC subheader shown in fig. 12(b) are used for padding, and the third and fourth bytes indicate that the subsequent MAC payload includes a terminal collision resolution identification MAC control cell and a MAC SDU from a DCCH logical channel.

The first byte of the MAC subheader shown in fig. 12(c) corresponds to a terminal collision resolution identification MAC control cell in the MAC payload, and the second and third bytes of the MAC subheader correspond to a MAC SDU from a DCCH logical channel in the MAC payload, wherein the length of the MAC SDU from the DCCH logical channel does not exceed 128 bytes. The fourth byte of the MAC subheader corresponds to padding in the MAC payload.

The first byte of the MAC subheader shown in fig. 12(d) corresponds to the terminal collision resolution identification MAC control cell in the MAC payload, and the second and third and fourth bytes of the MAC subheader correspond to the MAC SDU from DCCH logical channel in the MAC payload, wherein the length of the MAC SDU from DCCH logical channel exceeds 128 bytes. The fifth byte of the MAC subheader corresponds to padding in the MAC payload.

In the embodiment of the present application, a conflict resolution scheme is further provided, which is described in detail below.

After successfully receiving the messages 3 scrambled by the same TC-RNTI of a plurality of terminals, the access network element respectively issues the messages 4 scrambled by the TC-RNTI aiming at each terminal.

The terminal continuously listens to the message 4 without TC-RNTI scrambling until a contention resolution timer (mac-ContentionResolutionTimer) receiving the message 4 times out or stops. When the terminal monitors the message 4 scrambled by the TC-RNTI and successfully decodes the message 4 (not indicating successful contention resolution), the contention resolution timer for receiving the message 4 is not stopped, and the terminal continues to monitor the message 4 until the contention resolution timer times out.

Optionally, if the terminal determines that the conflict resolution is successful according to the content in the message 4, the contention resolution timer for receiving the message 4 is stopped; if the terminal judges that the conflict resolution is failed according to the contents in the message 4, the contention resolution timer for receiving the message 4 is not stopped.

The format of the message 4 may refer to any one of the formats described above, and is not described herein again.

In the embodiment of the present application, the MAC entity of the terminal does not perform collision resolution, and whether to continue to initiate the next random access procedure depends on the indication of the RRC entity of the terminal.

For example, the RRC entity of terminal a and the RRC entity of terminal B both instruct the respective terminals to perform the following actions: a competitive preamble is sent and the SI is requested based on the way of message 3. The SI types requested by the two terminals may or may not be the same.

The MAC entity of the terminal A and the MAC entity of the terminal B select the same PRACH occasion and the same preamble, so the preambles sent by the two terminals conflict with each other, and only one access network element can detect the collision. Therefore, the access network element sends a message 2, both terminals receive the message 2, and both terminals are considered to be sent to the access network element and receive the same TC-RNTI. Therefore, both terminals use the uplink resource allocated in message 2 and both send message 3 to the access network element. Because the RRC message requesting the SI has no terminal id, the contents of the message 3 sent by the two terminals may be the same or different, specifically, if the requested SI by the two terminals is the same, the contents of the message 3 sent by the two terminals are the same; if the requested SI is the same for both terminals, the content of message 3 sent by them is the same. If the uplink resources used by the two terminals are the same but transmitted using different uplink beams (beams), the access network element can successfully decode the message 3 sent by the two terminals. The access network element may be addressed with the TC-RNTI and send a message 4, which message 4 is an RRC message containing a bitmap, said bitmap being used to indicate which SI sending requests the access network element has received. After receiving the message, the MAC layer of the terminal does not perform conflict resolution, but directly sends the RRC message to the RRC entity, and after receiving the RRC message, the RRC entity has three processing methods:

the processing method 1: the RRC, discovering that the SI requested in message 3 generated by itself is all contained in the bitmap of message 4, instructs the MAC of the terminal to: conflict resolution is successful. After the MAC receives the data, the MAC considers that the conflict is resolved successfully, stops the contention resolution timer and does not use TC-RNTI monitoring any more.

The treatment method 2 comprises the following steps: the RRC entity determines that, in the SI requested in the message 3 sent, a part of the SI is contained in the bitmap of the message 4, and a part of the SI is not contained in the bitmap of the message 4, and may instruct the MAC entity of the terminal to: conflict resolution fails. After receiving the conflict resolution failure, the MAC entity considers the conflict resolution failure, does not stop the contention resolution timer, and continues to monitor by using the T-RNTI. In this case, the MAC entity of the terminal continues to initiate the second random access, and the number counter of the random access is incremented by 1. However, the message 3 sent in the second random access is different from the original message, and the message 3 sent in the second random access only contains the request corresponding to the SI that has not been requested in the message 4 of the previous random access.

The processing method 3: the RRC entity, discovering that none of the SI requested in message 3 generated by itself is contained in the bitmap of message 4, instructs the MAC entity of the terminal to: conflict resolution fails. After receiving the conflict resolution failure, the MAC entity considers that the conflict resolution fails, does not stop the contention resolution timer, and continues to monitor by using the TC-RNTI.

In the embodiment of the present application, how to select RACH parameters in the SI request process based on message 3 may refer to the following description:

one possible implementation manner is that a plurality of RACH parameter configurations are preset, that is, the terminal and the access network element agree with the plurality of RACH parameter configurations in advance, and the access network element may include one or more of the following RACH parameter configurations through each RACH parameter configuration: configuration identification, an available preamble set (the set may only contain one preamble), a power ramp parameter, a preamble maximum retransmission number, a RAR window (window) size, and a timer length for receiving the message 4.

Another possible implementation manner is that when the terminal has multiple parameter configurations and needs to request SI through the SI request procedure based on message 3, the RACH parameter configuration may be determined by the following method:

the method comprises the following steps: after the RRC entity of the terminal selects RACH parameter configuration, the MAC entity of the terminal is informed; the RRC entity informs the MAC entity that the configuration identifier may be an RACH parameter configuration identifier, or may be a specific parameter configuration, such as preamble information; the terminal performs the SI request procedure based on message 3 using the RACH parameter configuration indicated by the RRC entity.

The method 2 comprises the following steps: selecting, by the MAC entity, a RACH parameter configuration; the terminal performs the SI request procedure based on message 3 using the RACH parameter configuration selected by the MAC entity.

When the terminal triggers random access due to the arrival of uplink data, the parameter in the RACH parameter configuration may be selected for random access according to the correspondence between the access category (access category) of the uplink data and the RACH parameter configuration. The corresponding relationship between the access category of the uplink data and the RACH parameter configuration may be predefined by a protocol, or notified to the terminal by system information, or notified to the terminal by RRC dedicated signaling, which is not described herein again.

As shown in fig. 13, a schematic diagram of a terminal structure is provided for the embodiment of the present application.

Referring to fig. 13, the terminal 1300 includes: a processing unit 1301 and a transceiving unit 1302.

A processing unit 1301, configured to determine to end requesting the first information through a random access procedure if a first random access response RAR including an identifier of a first preamble transmitted by the access network element is monitored between the first time and the second time through the transceiving unit 1302;

the transceiver 1302 is configured to receive the first information transmitted by the access network element.

In an optional implementation manner, after determining that the first information is requested through a random access procedure, the processing unit 1301 is further configured to:

determining to no longer send the first preamble to the access network element.

In an optional implementation manner, if the first RAR is not monitored between the first time and the second time, the transceiving unit 1302 sends the first preamble to the access network element;

the processing unit 1301, through the transceiving unit 1302, determines to successfully request the first information through the random access procedure if the first RAR is monitored from the third time to the fourth time;

In an optional implementation manner, the transceiving unit 1302 is further configured to:

In an optional implementation manner, N is an integer greater than 1, and the processing unit 1301 is further configured to:

if a third RAR (random access request message) transmitted by the access network element and including an identifier of a second lead code is monitored between the first time and the fifth time through the transceiver unit, determining that the second lead code is not sent to the access network element any more; the fifth time is any time after the first time and before the end time of the RAR window corresponding to the first preamble;

In an alternative embodiment, N is an integer greater than 1;

In an optional embodiment, after determining to end the request of the first information through the random access procedure or determining to successfully request the first information through the random access procedure, the processing unit 1301 is further configured to:

In an optional implementation manner, after receiving the first information transmitted by the access network element, the processing unit 1301 is further configured to:

As shown in fig. 14, a schematic structural diagram of a terminal is provided for the embodiment of the present application.

Referring to fig. 14, the terminal 1400 includes: a processing unit 1401 and a transceiving unit 1402.

A transceiver unit 1402, configured to send a first preamble to an access network element;

a processing unit 1401, configured to determine that the first information is successfully requested through a random access procedure if a first random access response RAR including an identifier of the first preamble is monitored at a third time to a fourth time;

the transceiver 1402 is configured to receive the first information transmitted by the access network element.

In an optional implementation manner, the transceiver unit 1402 is further configured to:

In an alternative embodiment, N is an integer greater than 1, and the processing unit 1401 is further configured to:

if a third RAR including an identifier of a second preamble transmitted by the access network element is monitored between the first time and the fifth time through the transceiver unit 1402, determining to no longer send the second preamble to the access network element; the fifth time is any time after the first time and before the end time of the RAR window corresponding to the first preamble.

In an alternative embodiment, N is an integer greater than 1;

In an optional embodiment, after determining to end the request of the first information through the random access procedure or determining to successfully request the first information through the random access procedure, the processing unit 1401 is further configured to:

In an optional implementation manner, after receiving the first information transmitted by the access network element, the processing unit 1401 is further configured to:

As shown in fig. 15, a schematic diagram of a terminal structure is provided for the embodiment of the present application.

Referring to fig. 15, the terminal 1500 includes: a processor 1501, a transceiver 1502, a memory 1503, and a communication interface 1504; the processor 1501, the transceiver 1502, the memory 1503, and the communication interface 1504 are connected to one another via a bus 1505.

Processor 1501 may be a Central Processing Unit (CPU), a Network Processor (NP), or a combination of a CPU and an NP. The processor 1501 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a Programmable Logic Device (PLD), or a combination thereof. The PLD may be a Complex Programmable Logic Device (CPLD), a field-programmable gate array (FPGA), a General Array Logic (GAL), or any combination thereof.

Memory 1503 may include volatile memory (RAM), such as random-access memory (RAM); the memory may also include a non-volatile memory (non-volatile memory), such as a flash memory (flash memory), a Hard Disk Drive (HDD) or a solid-state drive (SSD); memory 1503 may also include combinations of the above types of memory.

The communication interface 1504 may be a wired communication access, a wireless communication interface, or a combination thereof, wherein the wired communication interface may be, for example, an ethernet interface. The ethernet interface may be an optical interface, an electrical interface, or a combination thereof. The wireless communication interface may be a WLAN interface.

The bus 1505 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, among others. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one double-headed arrow is shown in FIG. 8, but that does not indicate only one bus or one type of bus.

Memory 1503 may be used to store program instructions that processor 1501 calls stored in memory 1503 to perform one or more of the steps in the embodiments shown in the schemes described above.

A processor 1501, configured to determine to end the request for the first information through the random access procedure if a first random access response RAR including an identifier of the first preamble transmitted by the access network element is monitored between the first time and the second time through the transceiver 1502;

the transceiver 1502 is configured to receive the first information transmitted by the access network element.

In an optional embodiment, after determining to end the request for the first information through the random access procedure, the processor 1501 is further configured to:

determining to no longer send the first preamble to the access network element.

In an optional embodiment, the transceiver 1502 sends the first preamble to the access network element if the first RAR is not monitored between the first time and the second time;

the processor 1501, through the transceiver 1502, determines that the first information is successfully requested through a random access procedure if the first RAR is monitored from the third time to the fourth time;

In an optional embodiment, the transceiver 1502 is further configured to:

In an alternative embodiment, N is an integer greater than 1, and the processor 1501 is further configured to:

if a third RAR (random access request) transmitted by the access network element and including an identifier of a second lead code is monitored between the first time and the fifth time through the transceiver, determining that the second lead code is not sent to the access network element any more; the fifth time is any time after the first time and before the end time of the RAR window corresponding to the first preamble;

In an alternative embodiment, N is an integer greater than 1;

In an optional embodiment, after determining to end the request of the first information through the random access procedure or determining to successfully request the first information through the random access procedure, the processor 1501 is further configured to:

In an optional implementation manner, after receiving the first information transmitted by the access network element, the processor 1501 is further configured to:

As shown in fig. 16, a schematic structural diagram of a terminal is provided for the embodiment of the present application.

Referring to fig. 16, the terminal 1600 includes: a processor 1601, a transceiver 1602, a memory 1603, and a communication interface 1604; the processor 1601, the transceiver 1602, the memory 1603 and the communication interface 1604 are connected to each other via the bus 1605, and the specific contents of the above modules may refer to the description of the relevant modules in fig. 16, which is not described herein again.

A transceiver 1602, configured to send a first preamble to an access network element;

a processor 1601, configured to determine that a first information request through a random access procedure is successful if a first random access response RAR including an identifier of the first preamble is monitored at a third time to a fourth time;

the transceiver 1602 is configured to receive the first information transmitted by the access network element.

In an optional implementation, the transceiver 1602 is further configured to:

In an alternative embodiment, N is an integer greater than 1, and the processor 1601 is further configured to:

if a third RAR including an identifier of a second preamble transmitted by the access network element is monitored between the first time and the fifth time through the transceiver 1602, determining to no longer send the second preamble to the access network element; the fifth time is any time after the first time and before the end time of the RAR window corresponding to the first preamble.

In an alternative embodiment, N is an integer greater than 1;

In an optional embodiment, after determining that the first information is requested by the random access procedure at the end or determining that the first information is successfully requested by the random access procedure, the processor 1601 is further configured to:

In an optional implementation manner, after receiving the first information transmitted by the access network element, the processor 1601 is further configured to:

The embodiment of the present application further provides a computer-readable storage medium, which is used for storing computer software instructions required to be executed for executing the processor, and which contains a program required to be executed for executing the processor.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.

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

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1. An information acquisition method, characterized in that the method comprises:

if a terminal monitors a first Random Access Response (RAR) which is transmitted by an access network element and comprises an identifier of a first lead code between a first time and a second time, determining to end the request of the first information through a random access process;

2. The method of claim 1, wherein after determining to end the request for the first information through the random access procedure, the method further comprises:

3. The method according to claim 1, characterized in that it comprises:

4. The method of claim 3, further comprising:

5. The method of claim 4, wherein N is an integer greater than 1, the method further comprising:

if the terminal monitors a third RAR (random access request) transmitted by the access network element and comprising the identifier of the second lead code between the first time and the fifth time, determining that the second lead code is not sent to the access network element any more; the fifth time is any time after the first time and before the end time of the RAR window corresponding to the first preamble;

the second preamble is a preamble for requesting second information, and the second information is any one of the N pieces of information except the first information.

6. The method of any one of claims 1 to 5, wherein N is an integer greater than 1;

7. The method according to any of claims 1 to 5, wherein after the terminal determines to end the request of the first information through the random access procedure or determines to successfully request the first information through the random access procedure, the method further comprises:

8. The method according to any of claims 1 to 5, wherein after the terminal receives the first information transmitted by the network element of the access network, the method further comprises:

9. A terminal, comprising:

a processing unit, configured to determine to end requesting the first information through a random access procedure if a first random access response RAR including an identifier of a first preamble transmitted by an access network element is monitored between a first time and a second time;

and the receiving and sending unit is used for receiving the first information transmitted by the access network element.

10. The terminal of claim 9, wherein after determining to end the request for the first information through the random access procedure, the processing unit is further configured to:

determining to no longer send the first preamble to the access network element.

11. The terminal of claim 9, wherein the transceiver unit sends the first preamble to the access network element if the first RAR is not monitored between the first time and the second time;

12. The terminal of claim 11, wherein the transceiver unit is further configured to:

13. The terminal of claim 12, wherein N is an integer greater than 1, and wherein the processing unit is further configured to:

14. A terminal as claimed in any one of claims 9 to 13, characterised in that N is an integer greater than 1;

15. The terminal according to any of claims 9 to 13, wherein after determining to end or determine to succeed in requesting the first information through a random access procedure, the processing unit is further configured to:

16. The terminal according to any of claims 9 to 13, wherein after receiving the first information transmitted by the access network element, the processing unit is further configured to: