WO2022104662A1 - 请求系统消息块的方法及装置、通信设备及存储介质 - Google Patents

请求系统消息块的方法及装置、通信设备及存储介质 Download PDF

Info

Publication number
WO2022104662A1
WO2022104662A1 PCT/CN2020/130213 CN2020130213W WO2022104662A1 WO 2022104662 A1 WO2022104662 A1 WO 2022104662A1 CN 2020130213 W CN2020130213 W CN 2020130213W WO 2022104662 A1 WO2022104662 A1 WO 2022104662A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
msg2
feedback information
mac
sib
Prior art date
Application number
PCT/CN2020/130213
Other languages
English (en)
French (fr)
Inventor
李艳华
江小威
Original Assignee
北京小米移动软件有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 北京小米移动软件有限公司 filed Critical 北京小米移动软件有限公司
Priority to CN202080003415.8A priority Critical patent/CN112567791B/zh
Priority to PCT/CN2020/130213 priority patent/WO2022104662A1/zh
Priority to US18/037,614 priority patent/US20240129095A1/en
Publication of WO2022104662A1 publication Critical patent/WO2022104662A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/08—Non-scheduled access, e.g. ALOHA
    • H04W74/0833—Random access procedures, e.g. with 4-step access
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/14—Access restriction or access information delivery, e.g. discovery data delivery using user query or user detection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present disclosure relates to the technical field of wireless communication, but is not limited to the technical field of wireless communication, and in particular, relates to a method and apparatus for requesting a system message block, a communication device, and a storage medium.
  • System messages include: master message block (Master Information Block, MIB) and system message block (System Information Block, SIB). SIBs are further divided into SIB1 and other SIBs. Other SIBs may include: SIB2, SIB3, and SIB4....
  • MIB Master Information Block
  • SIB4 System Information Block
  • the MIB includes information such as system frame number and/or subcarrier spacing.
  • SIB1 carries scheduling information, access control information, and cell selection information of other SIBs.
  • SIBs carry parameters required for other functions, such as cell reselection, positioning, emergency notification, and a direct link (Sidelink, SL).
  • the UE needs to obtain MIB and SIB1 all the time.
  • SIBs the UE selects the information to read according to its own needs.
  • the base station When the system message is changed, the base station will send a short message.
  • the short message will carry a system message modification notification to notify the UE that the system information is changed. After the UE receives the short message, it will read and obtain the updated system information.
  • the short message also carries an emergency message notification. If the UE supports obtaining the emergency message, after receiving the notification, it will read SIB6, SIB7 and SIB8 to obtain the content of the emergency message.
  • Embodiments of the present disclosure provide a method and apparatus for requesting a system message block, a communication device, and a storage medium.
  • a first aspect of an embodiment of the present disclosure provides a method for requesting a system message block, including:
  • a second aspect of an embodiment of the present disclosure provides a method for requesting a system message block, including:
  • a third aspect of an embodiment of the present disclosure provides an apparatus for requesting a system message block, including:
  • a first receiving module configured to receive an acquisition request requesting a system message block SIB
  • the first sending module is configured to send feedback information for the obtaining request.
  • a fourth aspect of an embodiment of the present disclosure provides an apparatus for requesting a system message block, including:
  • the second sending module is configured to send an acquisition request requesting the system message block SIB;
  • the second receiving module is configured to receive feedback information for the obtaining request.
  • a fifth aspect of the embodiments of the present disclosure provides a communication device, including a processor, a transceiver, a memory, and an executable program stored on the memory and capable of being run by the processor, wherein the processor runs the executable program When the program executes the method for requesting a system message block as provided in the first aspect or the second aspect.
  • Method for requesting a system message block
  • the network side after receiving the acquisition request for requesting the SIB, the network side will deliver feedback information in response to the acquisition request.
  • the UE after the UE receives the feedback information, it will determine whether it needs to resend the acquisition request according to the information content of the feedback information, or wait for the network side to deliver the requested SIB; thus reducing the fact that the UE will not deliver the requested SIB on the network side.
  • the power consumption caused by repeated requests or continuous monitoring when requesting the SIB saves the power consumption of the UE and reduces the impact on the wireless environment caused by the repeated sending of the acquisition request by the UE.
  • FIG. 1 is a schematic structural diagram of a wireless communication system according to an exemplary embodiment
  • FIG. 2 is a schematic flowchart of a method for requesting a system message block according to an exemplary embodiment
  • FIG. 3 is a schematic flowchart of a random access procedure according to an exemplary embodiment
  • FIG. 4 is a schematic diagram of a format of a MAC PDU according to an exemplary embodiment
  • FIG. 5 is a schematic diagram of the format of a MAC RAR shown according to an exemplary embodiment
  • FIG. 6 is a schematic diagram of the format of a BI subheader shown according to an exemplary embodiment
  • FIG. 7 is a schematic diagram of the format of a MAC CE shown according to an exemplary embodiment
  • 8A is a schematic diagram of a format of a MAC CE shown according to an exemplary embodiment
  • 8B is a schematic diagram of a format of a MAC CE shown according to an exemplary embodiment
  • FIG. 9 is a schematic flowchart of a method for requesting a system message block according to an exemplary embodiment
  • FIG. 10 is a schematic flowchart of a method for requesting a system message block according to an exemplary embodiment
  • FIG. 11 is a schematic structural diagram of an apparatus for requesting a system message block according to an exemplary embodiment
  • FIG. 12 is a schematic structural diagram of an apparatus for requesting a system message block according to an exemplary embodiment
  • FIG. 13 is a schematic structural diagram of a UE according to an exemplary embodiment
  • Fig. 14 is a schematic structural diagram of a base station according to an exemplary embodiment.
  • first, second, third, etc. may be used in embodiments of the present disclosure to describe various pieces of information, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.
  • the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information.
  • the word "if” as used herein can be interpreted as "at the time of” or "when” or "in response to determining.”
  • FIG. 1 shows a schematic structural diagram of a wireless communication system provided by an embodiment of the present disclosure.
  • the wireless communication system is a communication system based on cellular mobile communication technology, and the wireless communication system may include: several UEs 11 and several base stations 12 .
  • the UE11 may be a device that provides voice and/or data connectivity to the user.
  • the UE11 may communicate with one or more core networks via a Radio Access Network (RAN), and the UE11 may be an IoT UE, such as a sensor device, a mobile phone (or "cellular" phone) and an IoT-enabled UE.
  • RAN Radio Access Network
  • the UE's computer for example, may be a stationary, portable, pocket-sized, hand-held, computer-built-in, or vehicle-mounted device.
  • a station For example, a station (Station, STA), a subscriber unit (subscriber unit), a subscriber station (subscriber station), a mobile station (mobile station), a mobile station (mobile), a remote station (remote station), an access point, a remote UE ( remote terminal), access UE (access terminal), user device (user terminal), user agent (user agent), user equipment (user device), or user UE (user equipment, UE).
  • the UE11 may also be a device of an unmanned aerial vehicle.
  • the UE 11 may also be an in-vehicle device, for example, a trip computer with a wireless communication function, or a wireless communication device connected to an external trip computer.
  • the UE11 may also be a roadside device, for example, may be a streetlight, a signal light, or other roadside device having a wireless communication function.
  • the base station 12 may be a network-side device in a wireless communication system.
  • the wireless communication system may be a fourth generation mobile communication (the 4th generation mobile communication, 4G) system, also known as a long term evolution (Long Term Evolution, LTE) system; or, the wireless communication system may also be a 5G system, Also known as new radio (NR) system or 5G NR system.
  • the wireless communication system may also be a next-generation system of the 5G system.
  • the access network in the 5G system can be called NG-RAN (New Generation-Radio Access Network, a new generation of radio access network).
  • the MTC system may be a network-side device in a wireless communication system.
  • the base station 12 may be an evolved base station (eNB) used in the 4G system.
  • the base station 12 may also be a base station (gNB) that adopts a centralized distributed architecture in a 5G system.
  • eNB evolved base station
  • gNB base station
  • the base station 12 adopts a centralized distributed architecture it usually includes a centralized unit (central unit, CU) and at least two distributed units (distributed unit, DU).
  • the centralized unit is provided with a protocol stack of a Packet Data Convergence Protocol (PDCP) layer, a Radio Link Control Protocol (Radio Link Control, RLC) layer, and a Media Access Control (Media Access Control, MAC) layer; distribution A physical (Physical, PHY) layer protocol stack is set in the unit, and the specific implementation manner of the base station 12 is not limited in this embodiment of the present disclosure.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control Protocol
  • MAC Media Access Control
  • distribution A physical (Physical, PHY) layer protocol stack is set in the unit, and the specific implementation manner of the base station 12 is not limited in this embodiment of the present disclosure.
  • a wireless connection can be established between the base station 12 and the UE 11 through a wireless air interface.
  • the wireless air interface is a wireless air interface based on the fourth generation mobile communication network technology (4G) standard; or, the wireless air interface is a wireless air interface based on the fifth generation mobile communication network technology (5G) standard, such as
  • the wireless air interface is a new air interface; alternatively, the wireless air interface may also be a wireless air interface based on a 5G next-generation mobile communication network technology standard.
  • an E2E (End to End, end-to-end) connection may also be established between UE11.
  • V2V vehicle to vehicle, vehicle-to-vehicle
  • V2I vehicle to Infrastructure, vehicle-to-roadside equipment
  • V2P vehicle to pedestrian, vehicle-to-person communication in vehicle-to-everything (V2X) communication etc. scene.
  • the above wireless communication system may further include a network management device 13 .
  • the network management device 13 may be a core network device in a wireless communication system, for example, the network management device 13 may be a mobility management entity (Mobility Management Entity) in an evolved packet core network (Evolved Packet Core, EPC). MME).
  • the network management device may also be other core network devices, such as a serving gateway (Serving GateWay, SGW), a public data network gateway (Public Data Network GateWay, PGW), a policy and charging rules functional unit (Policy and Charging Rules) Function, PCRF) or home subscriber server (Home Subscriber Server, HSS), etc.
  • the implementation form of the network management device 13 is not limited in this embodiment of the present disclosure.
  • an embodiment of the present disclosure provides a method for requesting a system message block, including:
  • S120 Deliver feedback information for the acquisition request.
  • the method can be applied to a base station on the network side, and the base station can be various base stations such as an evolved base station (envolved Node B, enB) or a next generation base station (Next Generation B, gNB).
  • enB evolved Node B
  • gNB next generation base station
  • a request for obtaining an SIB sent by the UE is received.
  • the acquisition request includes but is not limited to: ondemand request.
  • the feedback information is sent to the UE.
  • the feedback information may include: confirmation feedback indicating confirmation to issue the requested SIB and/or denial feedback refusing to send the requested SIB.
  • the UE By sending the feedback information, in this way, the UE knows whether the network side will send the SIBs requested by itself, instead of sending all the SIBs requested by the network side by default, or always sending requests when the requested SIBs are not received. Corresponding to the acquisition request of the SIB; reducing the power consumption caused by the UE's non-stop waiting and/or non-stop sending of requests caused by the UE's failure to obtain the network side's feedback for the acquisition request.
  • SIB1 is a separately sent system message block that is sent uncoupled from other SIBs.
  • the SIB is an SIBx obtained in the form of ondemand on demand, and x is a positive integer equal to or greater than 2.
  • the SIBx here includes but is not limited to: SIB2, SIB3, SIB4, SIB5, SIB6, SIB7 or SIB8 or SIB9, etc.
  • SIB2 SIB2, SIB3, SIB4, SIB5, SIB6, SIB7 or SIB8 or SIB9, etc.
  • the SIB for which the feedback information is directed may carry the SIB provided to the UE in the disconnected state.
  • the UEs in the disconnected state include but are not limited to: UEs in an idle state and/or UEs in an inactive state.
  • the SIBx is: a SIB carrying the configuration information of a tracking reference signal (Tracking Rfeference Signal, TRS) TRS; and/or, carrying a channel state information reference signal (Channel State Indicator, CSI)-(Reference Signal, RS ) of the SIB for configuration information.
  • TRS Track Rfeference Signal
  • CSI Channel State Indicator
  • the configuration information includes but is not limited to: resource information of the sending resource.
  • the transmission resources include but are not limited to: frequency domain resources, time domain resources and/or beam resources.
  • the configuration information may include: indication information of a pattern for sending TRS; and/or indication information of a pattern for sending CSI-RS.
  • the pattern may be a pattern of frequency domain resources, and/or a pattern of time domain resources.
  • the TRS can be used by the UE for phase noise estimation.
  • the CSI-RS can be used by the UE to estimate the channel quality of the current wireless channel.
  • the S120 may include: sending a negative acknowledgement (Negative Acknowledge, NACK), wherein the NACK indicates that the network side does not send the requested SIB; or, sending a confirmation reply (Acknowledge, ACK), Wherein, the ACK indicates the SIB of the request issued by the network side.
  • NACK negative acknowledgement
  • Acknowledge ACK
  • the ACK indicates the SIB of the request issued by the network side.
  • the feedback information in the embodiment of the present disclosure may be NACK.
  • the UE may be regarded as an ACK given by the network side.
  • the probability of the network side delivering NACK is lower than the probability of ACK.
  • the feedback information provided in the embodiments of the present disclosure may be NACK. If NACK is sent, it means that the network side will not send the SIB requested by the UE.
  • the network side sends an ACK, it means that the network side will send the SIB corresponding to the acquisition request, and the UE can receive the requested SIB at the sending resource position of the corresponding SIB, instead of continuing to send the acquisition request to repeatedly request the delivery of the SIB.
  • the S120 may include at least one of the following:
  • the NACK is delivered in response to the scheduling information of the requested SIB being in the minimum remaining system information RMSI.
  • RMSI minimum remaining system information
  • the base station finds that there are few UEs in the disconnected state or even no UEs in the disconnected state, so that communication resources can be saved so that more communication resources are used for other information transmission.
  • the base station has uncorresponding reference signals and/or control information to configure transmission resources
  • the configured transmission resources have been occupied or other control information and/or other control information with higher priority are transmitted due to emergency service data and other situations.
  • the network side does not have the resources to send the corresponding reference signals and/or control information, so the SIB carrying the configuration information of these reference signals and/or control information does not exist, and the base station side can also send NACK. Inform the UE not to continue waiting for the requested SIB or to repeatedly request the corresponding SIB.
  • the resource indicated by the configuration information carried by the SIB does not send the reference signal and the reference signal corresponding to the configuration information. / or control information.
  • the base station side may consider that it is unnecessary to repeatedly send, and may also send a NACK.
  • the base station may issue a NACK.
  • the UE may request the UE at the neighboring location to obtain the RMSI.
  • the feedback information further includes:
  • auxiliary information is at least for the user equipment UE to determine relevant information required for acquiring the SIB.
  • the feedback information includes not only the feedback indication, but also the auxiliary information.
  • the feedback indication here is the aforementioned NACK or ACK.
  • the auxiliary information can be used by the UE to obtain relevant information of the requested SIB, for example, to indicate when the UE can initiate a request for obtaining the SIB again, and/or to indicate whether the configuration resource corresponding to the configuration information carried in the requested SIB is available .
  • the UE By issuing the auxiliary information, the UE knows whether to initiate an acquisition request again, when to initiate an acquisition request, and the like.
  • the auxiliary information may further carry: the feedback information carries cause information of NACK.
  • the feedback information carries cause information of NACK. For example, when the UE requests a SIB that carries the configuration information of TRS/CSI-RS, and the base station finds that no TRS/CSI-RS transmission resources are currently configured, or the configured transmission resources are in an unavailable state such as being crowded, the following It is useless to send the requested SIB, then the base station will feed back NACK and inform the reason for sending NACK. Based on this reason, the UE can know the reason why the base station sends NACK, so as not to repeatedly initiate the acquisition request or continue to wait.
  • the auxiliary information includes at least one of the following:
  • duration information indicating the interval duration at which the UE initiates the acquisition request again
  • the available status information indicates whether there is configuration information carried by the SIB requested by the obtaining request, or whether the resource indicated by the configuration information carried by the SIB requested by the obtaining request is available.
  • the interval time By setting the interval time, the frequent initiation of acquisition requests by the UE is reduced, and the phenomenon of radio environment deterioration caused by frequent initiation of acquisition requests is reduced.
  • the network side does not configure the configuration information contained in the corresponding requested SIB, that is, the reference signal transmission resources are not configured for the corresponding reference signal and/or control information; Or, the network side has configuration information contained in the SIB requested for configuration, but the configuration information is now in an invalid state, that is, the sending resource indicated by the configuration information is in an unavailable state that is occupied by other control information and/or service data.
  • the acquisition request is sent by a UE in a disconnected state, and at this time, the base station receives the acquisition request in the random access process.
  • S110 includes but is not limited to: in the random access process
  • the acquisition request is received in the first message Msg1 or the third message Msg3 in the .
  • the UEs in the non-connected state here include: UEs in the idle state and/or UEs in the inactive state.
  • FIG. 3 shows a schematic flowchart of a 4-step random access process.
  • 4-step random access process
  • the UE sends Msg1 to the base station;
  • Msg1 carries the random access preamble (Random Access Preamble, RAP) identifier (Identity, ID) that the UE requests for random access;
  • RAP Random Access Preamble
  • ID Identity, ID
  • the base station If the base station selects the UE for random access, it will issue Msg2, if the Msg2 carries the RAP ID reported by the UE;
  • the UE After receiving the Msg2 carrying its own PRA ID, the UE will send the Msg3 to the base station;
  • the base station After receiving the Msg3, the base station will deliver the Msg4, and the Msg4 is composed of a MAC protocol data unit (Protocol Data Unit, PDU).
  • PDU Protocol Data Unit
  • Msg1 can be understood as a random access request carrying a random access preamble during the random access process.
  • Msg3 can be understood as: after the UE receives the message based on Msg1 and delivers the message sent after Msg2.
  • Msg2 may include a Random Access Response (RAR).
  • RAR Random Access Response
  • the method further includes: receiving the acquisition request carried in a paging response sent by a paging message.
  • the feedback information may be carried in Msg2 and/or Msg4. In order to make the UE obtain feedback information as quickly as possible, the feedback information is carried in Msg2.
  • the Msg2 may carry one or more feedback bits indicating the feedback information.
  • one or more bits in the Msg2 indicate the feedback information.
  • a bit has two bit values, "0" and "1", respectively.
  • the bit value of the feedback bit is “0”, indicating that the network side instructs the feedback to be acknowledged, and the value of the bit is "1", indicating that the feedback is denied.
  • the bit value of the feedback bit is "1”, indicating that the network side indicates confirmation of feedback, and when the bit value is "0", it indicates that the network side indicates negative feedback.
  • the feedback bits may be composed of reserved bits in the message format of Msg2, or may be composed of extended bits in the message format of Msg2.
  • the extension bits here can be new bits.
  • the MAC PDU corresponding to Msg2 carries at least MAC sub-PDUs.
  • the MAC PDU may include pading in addition to MAC sub-PDUs.
  • Padding is optional content of the MAC PDU in Msg2.
  • one MAC sub-PDU may include at least one sub-header.
  • a MAC sub-PDU may also include a corresponding MAC RAR.
  • the MAC sub-PDU carries the RAP ID. If the RAP ID is sent by a certain UE, it means that the MAC RAR associated with the MAC sub-PDU is sent to the UE, and the UE can send the third message based on the MAC RAR.
  • the feedback information may be carried in the MAC RAR.
  • the feedback bits may be carried in the MAC RAR.
  • the third MAC sub-PDU in the MAC PDU shown in FIG. 4 is a MAC sub-PDU carrying feedback information.
  • the feedback information is NACK as an example, and there is a RAP ID subheader and a second type of MAC RAR in the third MAC sub-PDU.
  • the MAC RAR can be divided into the first type MAC RAR and the second type MAC RAR; the first type MAC RAR does not carry the feedback information, and the second type MAC RAR carries the feedback information.
  • the information carried by the first type MAC RAR may include: authorization information for various transmissions, for example, authorization information for the physical uplink shared channel.
  • the feedback information is carried in the second type MAC RAR, then the corresponding UE receives Msg2, and will be based on the RAP ID matching technology in the random access process according to the related technology.
  • the UE matching the RAP ID is sent to
  • the UE will continue to decode the second type MAC RAR to obtain the feedback information, and obtain the ACK or NACK indication of the base station from the feedback information.
  • the UE decides the subsequent random access procedure or whether to continue requesting the SIB or waiting to receive the SIB. For example, if NACK is received, the current random access procedure is terminated, for example, Msg3 is not sent any further.
  • the RAP ID carried by Msg2 is different from the RAP ID sent by the UE in Msg1, the UE suspends this random access procedure.
  • the Msg2 since feedback information is introduced into the Msg2, the Msg2 can be divided into two types according to whether it can carry the feedback information.
  • Msg2 One type of Msg2 continues to use the information format that does not carry feedback information, and the Msg2 of this information format constitutes the first type of Msg2; another type of Msg2 will carry the information format of feedback information, and the Msg2 of this information format is the second type. Msg2.
  • the Msg2 provided in the embodiment of the present disclosure can be divided into: the Msg2 that cannot carry the feedback information is the first type Msg2; and the Msg2 that can carry the feedback information is the second type Msg2.
  • the communication resources of the Msg1 corresponding to the first type Msg2 are different from the communication resources of the Msg1 corresponding to the second type Msg2.
  • the base station side can determine which type of Msg2 to reply to the UE according to the communication resources used by the UE to send the Msg1.
  • the communication resources of Msg1 corresponding to the second type Msg2 may not be visible to UEs that do not support the second type Msg2.
  • the communication resources of Msg1 corresponding to the second type Msg2 may be a configuration of non-critical extensions.
  • Configuration of this non-critical extension is optional.
  • the network side may select the configuration of the non-critical extension, or may not select the configuration of the non-critical extension. If the network side does not select the configuration of the non-critical extension, the network side is not configured to use the second type Msg2 to deliver feedback information.
  • the base station can simply determine whether the Msg1 carries the acquired communication resources according to the communication resources of the received Msg1 request, which information format needs to be used to decode the received Msg1, so as to simplify the decoding of the Msg1 by the base station side.
  • the Msg1 that carries the acquisition request and the Msg1 that does not carry the acquisition request may reuse the same communication resources.
  • the information format of the message format is used to decode the Msg1.
  • the type of the Msg1 at this time can be distinguished by the ID of the random access preamble carried by it.
  • the method further includes: delivering a SIB1, wherein the SIB1 carries resource information of the communication resources of the Msg1 corresponding to the second type Msg2.
  • the communication resource of Msg1 is carried in the SIB1 sent by broadcast, so that even a UE in a non-connected state can receive the resource information of the communication resource of the above-mentioned Msg1.
  • the manner in which the Msg2 carries the feedback information includes:
  • Implicit carrying that is, indicating the feedback information by sharing the indication bits with other information.
  • the feedback information has a corresponding relationship with specific information, and when at least the corresponding bits carry specific information, it is equivalent to indicating the corresponding specific information and the specific information at the same time. Feedback.
  • the specific information includes but is not limited to: a random access preamble (Random Access Preamble, RAP) ID.
  • RAP Random Access Preamble
  • the RAP ID can be divided into at least two categories, one is the RAP ID that has a corresponding relationship with the feedback information, and the other is the RAP ID that does not have a corresponding relationship with the feedback information.
  • a RAP ID that has a corresponding relationship with the feedback information is established.
  • the UE After receiving the RAP ID, the UE will know the feedback information of the SIB requested by the UE from the network side, and then determine the next operation according to the feedback information, such as , whether to continue to send the acquisition request, or to receive SIBs on the corresponding resource, etc.
  • the RAP ID that has a corresponding relationship with the feedback information may be: the RAP ID reserved in the related art.
  • the reserved RAP ID here may be notified to the UE in advance by the network side, or may be specified by a communication protocol.
  • the RAP ID corresponding to the feedback information at least includes: the RAP ID corresponding to the NACK. That is, Msg2 can carry at least the RAP ID that has a corresponding relationship with NACK.
  • the second type Msg2 in order to facilitate decoding by the UE, the second type Msg2 further has a type field, and the type field indicates the type of the Msg2.
  • the first type Msg2 and the second type Msg2 are not distinguished by a special type field. It can be understood that the first type Msg2 and the second type Msg2 are distinguished by the type of the field carried by the Msg2; and/or the first type Msg2 and the second type Msg2 are distinguished by the information content carried by the Msg2.
  • the first type Msg2 carries the first type MAC RAR; the second type Msg2 carries the second type MAC RAR.
  • the second type Msg2 carries a RAP ID that has a corresponding relationship with the feedback information; the first type Msg2 carries a RAP ID that does not have a corresponding relationship with the feedback information.
  • the type field includes one or more bits, which can also be called a type flag (Flag), which can be used to indicate whether the current Msg2 is the second type Msg2, or directly indicate whether the current Msg2 is the first type Msg1 or the first type.
  • the current Msg2 may be a Msg2 that includes the type field.
  • the RAP ID that the Msg2 carries has a corresponding relationship with the feedback information, and has at least one of the following characteristics:
  • One of the RAP IDs has a corresponding relationship with the feedback information of multiple SIBs.
  • the Msg2 In response to a corresponding relationship between one of the RAP IDs and the feedback information of a plurality of the SIBs, the Msg2 also carries the information identifiers of the SIBs corresponding to the feedback information.
  • the RAP IDs corresponding to the feedback information of different SIBs are different; or, the feedback information of different SIBs corresponds to the same RAP ID, and the Msg2 carries the RAP ID of the SIB indicated by the feedback information. identification information.
  • the RAP IDs corresponding to the feedback information of the different SIBs are different, at least including: the RAP IDs corresponding to the NACKs of the different SIBs are different.
  • the feedback information of the different SIBs corresponds to the same RAP ID, at least including: NACKs of different SIBs correspond to the same RAP ID.
  • the second type Msg2 carries the RAP ID that has a corresponding relationship with the feedback information, and does not carry the auxiliary information and/or the information identifier of the SIB corresponding to the feedback information;
  • the second type Msg2 carries a RAP ID that has a corresponding relationship with one SIB feedback information; further, in this case, the second type Msg2 can also carry one or more of the aforementioned auxiliary information;
  • the second type Msg2 carries a RAP ID that has a corresponding relationship with multiple SIB feedback information and the information identifier of the SIB corresponding to the RAP ID. Further, in this case, the second type Msg2 may also carry one or more of the aforementioned auxiliary information.
  • the RAP ID carried in the second type Msg2 can correspond to the feedback information of one SIB. In this way, the UE will know the feedback information of the corresponding SIB after receiving the corresponding RAP ID.
  • the UE after receiving the RAP ID corresponding to the feedback information of multiple SIBs at the same time, the UE will also determine the SIB corresponding to which RAP ID acts on which RAP ID according to the information identifier.
  • the number of RAP IDs that have a corresponding relationship with the feedback information of the SIB can be relatively small, for example, it can be only a small number such as one or two. If there are multiple RAP IDs corresponding to the feedback information of multiple SIBs, different RAP IDs may correspond to the feedback information of different SIBs; thus, the information bits carrying identification information in the second type Msg2 may correspond to reduce.
  • Case 1 The different RAP IDs carried by the Msg2 correspond to the feedback information of different SIBs, and the Msg2 does not have a MAC RAR that carries auxiliary information;
  • Case 1 The same RAP ID carried by the Msg2 corresponds to the feedback information of different SIBs, and the Msg2 does not have a MAC RAR carrying auxiliary information;
  • Case 4 The same RAP ID carried by the Msg2 corresponds to feedback information of different SIBs, and the Msg2 has a MAC RAR carrying auxiliary information.
  • the Msg2 further carries the information identifier of the SIB having the feedback information.
  • the information identifier can be carried when one RAP ID corresponds to the feedback information of one SIB, or can be carried when one RAP ID corresponds to the feedback information of multiple SIBs. In consideration of reducing bit overhead, the information identifier can only be carried in one RAP ID.
  • the RAP ID is carried when it corresponds to the feedback information of multiple SIBs.
  • the information identifier may be explicitly indicated by a dedicated bit, or implicitly indicated by establishing a corresponding relationship with other information.
  • the information identification is carried in the identification information field of the Msg2; the identification information field carries the information identification of one or more SIBs corresponding to the NACK; or, The identifier information field carries one or more information identifiers of the SIB corresponding to the ACK.
  • an identification information field is introduced, and the identification information field can be specially used to place the information identification of the SIB whose feedback information has a corresponding relationship with the RAP ID.
  • the information identification field can also be used to carry the aforementioned auxiliary information.
  • the identification information field is included in the MAC RAR of the Msg2, and the length of one of the MAC RARs is greater than or equal to the length of the identification information field.
  • a Msg2 protocol data unit may include multiple MAC sub-PDUs; one MAC sub-PDU includes a RAP ID subheader (subheader) and a MAC random access response (Random Access Response, RAR).
  • the RAP ID subheader is used to carry the RAP ID; the MAC RAR is used to carry the random access response.
  • the identification information field may be included in the MAC RAR, and the length of the identification information field is less than or equal to the length of the identification information field, so that it can be compatible with the MAC sub-PDU format in the related art. If the length of the identification information field is exactly equal to the length of the MAC RAR, then the MAC RAR has no remaining bits, and the format at the MAC RAR level is not changed at this time. If the length of the identification information field is less than the length of the MAC RAR, the MAC RAR has remaining bits, and the remaining bits can be used as reserved bits or carry other information, so the information format at the MAC RAR level is changed.
  • the length of the identification information field is less than or equal to the length of the MAC RAR, which can be selected according to current wireless transmission requirements.
  • the length of the identification information field may exceed the length of the MAC RAP.
  • the identification information field contains both the information bits and extension bits of the MAC RAP.
  • the extension bits here are newly added bits in a MAC sub-PDU.
  • Msg2 carries auxiliary information
  • an information identification field is set in Msg2
  • the identification information field is also used to carry the auxiliary information; wherein, the auxiliary information is at least used by the user equipment UE for determination. to obtain the relevant information required for the SIB.
  • the auxiliary information For the relevant description of the auxiliary information, reference may be made to the foregoing corresponding embodiments, which will not be repeated here.
  • auxiliary information carried by Msg2 can be carried in the information identification field or outside the information identification field.
  • FIG. 5 shows a format example of the second type of MAC RAR provided by the embodiment of the present disclosure.
  • the MAC RAR of the second type may include a plurality of bytes.
  • a MAC RAR of the second type includes 8 octets (octets), oct0 to oct7, respectively.
  • the second type MAC RAR shown in FIG. 5 has a SI RAP ID-i field, and the SI RAP ID-i field can be used to carry at least the identification information of the SIB corresponding to the foregoing feedback information. In some embodiments, the SI RAP ID-i field may also be used to carry assistance information.
  • the Msg2 has a BI subheader of a backoff indicator BI; wherein the BI subheader carries the feedback information.
  • the MAC sub-PDU of the Msg2 also carries BI.
  • the UE that receives the Msg2 will perform random access backoff according to the BI in the BI subheader, and after the backoff value reaches the value indicated by the BI, it can initiate random access again, that is, send the Msg1 again.
  • the BI subheader of the BI is carried in one MAC sub-PDU of Msg2.
  • the first MAC sub-PDU is a MAC sub-PDU carrying BI.
  • the subheader of the first MAC sub-PDU may be referred to as a BI subheader.
  • the E field in the subheader of each MAC sub-PDU can be used to indicate whether the subheader where it is located has other fields; the T field can be used to indicate whether the subheader where it is located contains a RAP ID; for example, the first MAC subheader In the subheader of the PDU, the T field indicates that the subheader where it is located contains not the RAP ID but the BI subheader.
  • the BI subhead carries BI.
  • the subheader carrying the RAP ID in FIG. 4 may be referred to as the RAP ID subheader.
  • the feedback information may be carried by using the remaining bits in the BI subheader.
  • one or more of the reserved bits in the BI subheader may be used to indicate feedback information, for example, to indicate ACK or NACK in the feedback information.
  • the BI subheader further carries the aforementioned auxiliary information, and here, the auxiliary information is at least for the user equipment UE to determine relevant information required for acquiring the SIB.
  • the reserved bits of the BI subheader may also carry the aforementioned duration information and/or availability status information, etc.
  • Figure 6 shows an example of a message format for a subheader containing BI.
  • the BI subheader shown in FIG. 6 may include 1 octet (oct1). 1 octet can include 8 bits.
  • the BI subheader also carries feedback information.
  • the R field is a reserved field
  • E is an extension field, indicating whether the subheader has other contents
  • the T field is a type field, indicating whether the subheader carries a RAP ID. Both the E field and the T field may occupy 1 bit.
  • the feedback information may also occupy a field in this subheader.
  • the UE when the UE receives the Msg2, it can not only know whether the network layer will send the SIB requested by itself, but also know when the request for obtaining the SIB can be re-initiated according to the auxiliary information carried in the BI subheader, or the network side refuses to send it.
  • Reason for SIB The reasons include but are not limited to: the configuration information carried by the SIB requested by the acquisition request is not configured on the network side and/or the configuration information carried by the SIB is configured but the sending resource indicated by the configuration information is unavailable.
  • the feedback information is carried by reserved bits of the BI subheader.
  • the feedback information may have a corresponding relationship with the BI carried by the BI subheader.
  • the BI carried in the BI subheader not only indicates the backoff value, but also indicates the NACK or ACK for the acquisition request.
  • the S110 may include: receiving a third message Msg3 that carries an acquisition request for the SIB.
  • the SIB acquisition request may be carried in Msg3.
  • S120 may include: carrying the feedback information in the Msg4 and delivering it to the UE.
  • the Msg4 includes: a medium access control MAC control element CE.
  • One Msg4 can carry one or more MAC CEs.
  • MAC CE includes: MAC CE subheader (subheader).
  • a MAC CE subheader may carry an LCID value.
  • the MAC CE subheader includes one octet (oct), and one oct has 8 bits, the 8 bits include: reserved field and LCID field; reserved field includes reserved bits; LCID field , which is used to carry the LCID value.
  • the reserved field may include 2 reserved bits; the LCID field may include 6 bits.
  • the LCID field has 64 LCID values.
  • the 64 LCID values can be as shown in Table 1:
  • the codepoint/index (codepoint/index) is 35, that is, the codepoint or index is 35, which is an example of the LCID value having a corresponding relationship with the feedback information.
  • the code point or the LCID value whose index is 35 in Table 1 has a corresponding relationship with the NACK in the feedback information.
  • the network side preconfigures many LCID values that can be carried by the MAC CE subheader. And one or more of the multiple LCID values configured on the network side have a corresponding relationship with the feedback information. For example, one or more of the multiple LCID values have a corresponding relationship with NACK or ACK in the feedback information.
  • At least some of the multiple LCID values carried by the MAC CE subheader have a corresponding relationship with the feedback information.
  • one MAC CE subheader carries one LCID value at a time. There are multiple candidate values for the LCID value that can be carried into the MAC CE subheader, and one or more of the multiple candidate values have a corresponding relationship with the feedback information.
  • the LCID value carried by Msg4 may or may not have a corresponding relationship with the feedback information. If the LCID value carried by the Msg4 has a corresponding relationship with the feedback information, after the UE receives the Msg4, the LCID value extracted from the Msg4 has a corresponding relationship with the feedback information, and the network side will be determined according to the LCID value.
  • the feedback information may be NACK or ACK.
  • one of the MAC CEs includes: a payload.
  • the first part of the continuous distribution in the payload does not have a corresponding relationship with the feedback information
  • the second part other than the first part in the payload has a corresponding relationship with the feedback information.
  • the 48 bits can be divided into a first part and a second part, the first part is used to resolve contention conflicts between UEs, and the second part is used to carry feedback information.
  • the first part may include 32 bits; the second part may include 16 bits for carrying feedback information.
  • the first portion may be the first 32 of the 48 bits, and the second portion may be the last 16 of the 48 bits.
  • the payload is 48 bits.
  • the first part of the 48 bits may include: 40 bits; the second part may be the remaining 8 bits.
  • the bits corresponding to the first part are continuously distributed, so that the subsequent UE can quickly determine whether the random access is successful after receiving the Msg4.
  • the payload of the MAC CE of the Msg4 has extension bits; the extension bits are used to carry the feedback information.
  • the payload of the MAC CE with the extension bits added will exceed 48 bits.
  • the payload of the MAC CE of the Msg4 has one or more extension bits, and the extension bits carry the foregoing feedback information and/or auxiliary information.
  • the original bits in the payload of the MAC CE can be used to resolve contention conflicts between UEs, and the extended bits indicate the feedback information, so that the number of bits in the payload of the MAC CE increases.
  • the feedback information indicated by the extension bit includes: in addition to the ACK/NACK, the auxiliary information of any one of the preceding items may also be included.
  • the MAC CEs may include: two types of MAC CEs, namely a first type of MAC CE and a second type of MAC CE. The purpose of the first type of MAC CE and the second type of MAC CE is different.
  • the first type of MAC CE is used for contention and conflict resolution between UEs; the second type of MAC CE is used to carry the feedback information.
  • MAC CE subheader In some cases, whether it is the first type of MAC CE or the second type of MAC CE, in addition to the MAC CE subheader, it can also include: a padding part.
  • the MAC CE subheader can be divided into reserved fields and LCID fields.
  • the second type of MAC CE subheader carries an LCID value that has a corresponding relationship with the feedback information.
  • the LCID value It can be a newly added LCID value or an enhanced LCID value.
  • the newly added LCID value (or becomes the enhanced LCID value) may be the code point in Table 1 or the LCID value whose index is 35.
  • the feedback information carried by the second type of MAC CE occupies bits in the reserved field or is carried in the padding part of the second type of MAC CE, it can be considered that the bit value corresponding to the feedback information does not belong to the LCID value.
  • the bit value of the reserved field is divided into the LCID field after the LCID field is enhanced, it can also be considered that the second type of MAC CE carries the enhanced LCID value corresponding to the feedback information.
  • the length of the MAC CE subheader can be fixed or not.
  • the fixed length of a MAC CE subheader may be 8 bits; the number of bits included in the MAC CE subheader may be an integer multiple of 8 bits.
  • the first type of MAC CE and the second type of MAC CE are adjacently distributed in the Msg4.
  • FIG. 7 is a schematic diagram of a MAC CE subheader.
  • a MAC CE subheader may include one octet (oct1).
  • a MAC CE subheader includes: the R field and the LCID field; the R field is a reserved field with one or more reserved bits.
  • the reserved field of the MAC CE subheader in Figure 7 has 2 reserved bits.
  • the LCID field of the MAC CE subheader has 6 bits and has 64 bit values, that is, 64 LCID values can be indicated.
  • FIG. 7 can be understood as an example of the first type of MAC CE subheader.
  • 8A and 8B can be understood as an example of the second type of MAC CE.
  • the second type of MAC CE subheader shown in Figure 8A has an Enhanced Logical Channel Identification (enLCID) field.
  • the enLCID field can be used to carry feedback information, or carry an LCID value that has a corresponding relationship with the feedback information.
  • the length of the second type MAC CE subheader shown in FIG. 8A is fixed, that is, 1 octet, that is, 8 bits.
  • the length of the second type of MAC CE shown in FIG. 8B is not fixed, that is, the length of the second type of MAC CE is variable.
  • the number of bits of a non-fixed MAC CE is usually a positive integer multiple of 8.
  • the F field is used to indicate that the length of the current MAC CE is not fixed.
  • the length of the second type of MAC CE shown in FIG. 8B is increased from 1 octet of fixed length to 2 octets, and the two octets are oct1 and oct2 respectively.
  • the enLCID field and the L field can jointly indicate feedback information.
  • the L field is used to identify that the enLCID field in the MAC CE subheader carries feedback information or an LCID value that has a corresponding relationship with the feedback information.
  • MAC CEs including different types of MAC CE subheaders are different types of MAC CEs.
  • the different types of MAC CEs include at least a first type of MAC CE and a second type of MAC CE.
  • the second type of MAC CE follows its corresponding type of MAC CE. Through the positional relationship between the first type of MAC CE and the second type of MAC CE, it is indicated that the feedback information carried by the current second type of MAC CE is for the UE corresponding to the first type of MAC CE located in front of it.
  • the S120 may include:
  • a radio connection control (Radio Resource Control, RRC) message carrying the feedback information is delivered.
  • RRC Radio Resource Control
  • the UE in the disconnected state sends the acquisition request through Msg1 or Msg3 or sends the acquisition request in other ways, and the UE can receive the RRC message after switching from the disconnected state to the connected state in the random access process.
  • the base station on the network side can send the feedback information to the UE through an RRC message. If the network side does not prepare to deliver the SIB requested by the acquisition request, the UE can determine whether to continue to send the acquisition information according to the feedback information carried in the RRC message. ask.
  • an embodiment of the present disclosure provides a method for requesting a system message block, including:
  • S210 Send an acquisition request requesting the SIB
  • S220 Receive feedback information for the acquisition request.
  • the method for requesting a system message block provided by the embodiments of the present disclosure can be applied to various UEs requesting SIBs.
  • the UE may be a UE in a disconnected state.
  • the UE may send the acquisition request through Msg1 and/or Msg3 in the random access procedure.
  • the UE after sending the acquisition request, the UE will receive feedback information returned based on the acquisition request.
  • the feedback information may be carried explicitly through one or more bits, or may be carried implicitly through the corresponding relationship with other information.
  • the feedback information may include: NACK or ACK.
  • the UE can determine whether to continue to send the acquisition request according to the feedback information, or to receive the requested SIB in the configuration resource of the requested SIB.
  • the feedback information it is possible to reduce unnecessary waiting for sending unnecessary acquisition requests and receiving SIBs.
  • the SIB is an SIBx obtained in an ondemand form, where x is a positive integer equal to or greater than 2.
  • the SIB requested to the network side through the acquisition request is SIBx.
  • the SIBx is: a SIB carrying configuration information of the TRS; and/or a SIB carrying the configuration information of the CSI-RS.
  • the S210 may include: receiving a negative reply NACK, wherein the NACK indicates that the network side does not issue the requested SIB; or, receiving a confirmation reply ACK, wherein the ACK indicates that the network side sends the requested SIB The requested SIB.
  • the feedback information can be NACK or ACK. If the UE receives NACK, it means that the network side will not send the requested SIB. On the one hand, the UE knows that the network side will not send the requested SIB, so there is no need to repeat the request. There is no need to wait for the UE to issue the SIB, which reduces the power consumption caused by the UE repeatedly requesting the SIB or waiting to monitor the SIB.
  • the UE If the UE receives an ACK, it means that the network side will deliver the SIB requested by the UE, and the UE can directly receive the requested SIB on the configuration resources of the requested SIB without repeating the request, thereby reducing the number of problems caused by repeated requests. power consumption.
  • the feedback information further includes:
  • auxiliary information is at least for the user equipment UE to determine relevant information required for acquiring the SIB.
  • the auxiliary information may be issued when the feedback information is NACK.
  • the auxiliary information can be used to instruct the UE to re-send the acquisition request interval time information, or, the information indicating the reason for the network side to send the NACK, the information indicating the reason for the network side to send the NACK includes but not limited to: available status information.
  • the auxiliary information includes:
  • duration information indicating the interval duration for the UE to initiate the acquisition request again; and/or available status information, indicating whether there is configuration information carried by the SIB requested by the acquisition request, or, indicating the SIB requested by the acquisition request Whether the resource indicated by the carrying configuration information is available.
  • the auxiliary information when the feedback information is ACK, the auxiliary information may be: configuration information of the requested SIB, where the configuration information may at least indicate the transmission resources of the requested SIB. In this way, the UE can receive the SIB on the corresponding transmission resource according to the auxiliary information of the SIB carried by the auxiliary information.
  • the S210 may include: sending a first message Msg1 carrying the acquisition request.
  • the first message Msg1 is one of the random access messages, is the first random access message in the four-step random access process, and generally carries an identification (Identification, ID) of an access preamble.
  • Msg1 not only carries the ID of the preamble, but also carries the acquisition request.
  • the S220 may include: sending a second message Msg 2 that carries the feedback information.
  • Msg2 carries the feedback information of the acquisition request.
  • the feedback information may be NACK or ACK.
  • the Msg2 carries feedback bits.
  • Msg2 carries feedback bits that explicitly indicate the feedback information, and the feedback bits may be original reserved bits in Msg2 or reserved bits in Msg2.
  • the feedback information is carried in the MAC random access response RAR of the Msg2.
  • the feedback bits may be carried in the MAC RAR.
  • the MAC RAR that carries the feedback information is the second type of MAC RAR; the MAC RAR that does not carry the feedback information is the first type of MAC RAR.
  • the MAC RAR carried by Msg2 carrying the feedback information is the second type of MAC RAR.
  • the Msg2 can be classified into a first type Msg2 and a second type Msg2.
  • the Msg2 that cannot carry the feedback information is the first type Msg2; the Msg2 that can carry the feedback information is the second type Msg2. It can be understood that: the first type Msg2 does not carry the feedback bits, while the second type Msg2 carries the feedback bits; or, the first type Msg2 carries the first type MAC RAR; the second type Msg2 carries the second type MAC RAR.
  • the first type Msg2 can be used as reply information for the Msg1 that does not carry the acquisition request.
  • the second type Msg2 can be used as reply information carrying the Msg1 of the acquisition request.
  • the communication resources of the Msg1 corresponding to the first type of Msg2 are different from the communication resources of the Msg1 corresponding to the second type of Msg2.
  • the UE may send the Msg1 on the corresponding communication resource according to whether the currently to-be-sent Msg1 carries an acquisition request to trigger the network downlink Send the corresponding type of Msg2.
  • the configuration mode of the communication resources corresponding to the Msg1 of the second type Msg2 may be different from the configuration mode of the communication resources of the Msg1 corresponding to the first type Msg2.
  • the communication resources of Msg1 corresponding to the second type Msg2 are configured through non-critical extensions in the SIB. The configuration of this non-critical extension is optional.
  • the method further includes: receiving SIB1, wherein the SIB1 carries resource information of communication resources of Msg1 of the second type Msg2.
  • the resource information here may be: information such as time-frequency resources and/or beam resources indicating transmission of the Msg1 corresponding to the second type Msg2.
  • the S220 may include: receiving the Msg2 carrying the random access preamble RAP ID corresponding to the feedback information.
  • Msg2 does not directly carry the feedback bits of the feedback information, but implicitly indicates the feedback information by carrying the RAPID that has a corresponding relationship with the feedback information.
  • the RAP ID includes: a RAP ID that has a corresponding relationship with NACK in the feedback information, a RAP ID that has a corresponding relationship with ACK in the feedback information, and/or a RAP ID that does not have a corresponding relationship with the feedback information RAP ID.
  • the second type Msg2 further has a type field indicating the type of Msg2.
  • the type field may include one or more bits indicating that the current Msg2 may be a second type Msg2, so as to facilitate the UE to quickly decode the Msg2.
  • the RAP IDs corresponding to the feedback information of different SIBs are different; or, the feedback information of different SIBs corresponds to the same RAP ID.
  • Case 1 The different RAP IDs carried by the Msg2 correspond to the feedback information of different SIBs, and the Msg2 does not have a MAC RAR that carries auxiliary information;
  • Case 1 The same RAP ID carried by the Msg2 corresponds to the feedback information of different SIBs, and the Msg2 does not have a MAC RAR carrying auxiliary information;
  • Case 4 The same RAP ID carried by the Msg2 corresponds to feedback information of different SIBs, and the Msg2 has a MAC RAR carrying auxiliary information.
  • the Msg2 further carries the information identifier of the SIB having the feedback information.
  • the information identifier can be carried when one RAP ID corresponds to the feedback information of one SIB, or can be carried when one RAP ID corresponds to the feedback information of multiple SIBs. In consideration of reducing bit overhead, the information identifier can only be carried in one RAP ID.
  • the RAP ID is carried when it corresponds to the feedback information of multiple SIBs.
  • the information identifier may be explicitly indicated by a dedicated bit, or implicitly indicated by establishing a corresponding relationship with other information.
  • the information identifier when the information identifier is explicitly indicated by a dedicated bit, the information identifier is carried in the identification information field of the Msg2; the identification information field carries one or more SIBs corresponding to NACKs or, the identification information field carries one or more information identifiers of SIBs corresponding to the ACK.
  • the identification information field is included in the MAC RAR of the Msg2, and a length of the MAC RAR is greater than or equal to the length of the identification information field.
  • Msg2 carries auxiliary information
  • an information identification field is set in Msg2
  • the identification information field is also used to carry the auxiliary information; wherein, the auxiliary information is at least used by the user equipment UE for determination. to obtain the relevant information required for the SIB.
  • auxiliary information carried by Msg2 can be carried in the information identification field or outside the information identification field.
  • Msg2 has MAC sub-PDUs; one Msg2 has at least one MAC sub-PDU carrying a BI subheader, and the BI subheader carries a BI. Reserved bits in the BI subheader can be used to carry the feedback information.
  • the Msg2 has a BI subheader of a backoff indicator BI; wherein the BI subheader carries the feedback information.
  • the feedback information is carried by reserved bits of the BI subheader.
  • the BI subheader also carries auxiliary information
  • the auxiliary information is at least for the user equipment UE to determine relevant information required for acquiring the SIB.
  • the S210 may include: sending a third message Msg3 that carries the acquisition request of the SIB.
  • the S220 may include: receiving a fourth message Msg4 that carries the feedback information.
  • the Msg4 may include: one or more medium access control MAC control elements CE.
  • the MAC CE that carries the feedback information can be called a feedback CE, which can be distinguished from the MAC CE that resolves contention between UEs.
  • a MAC CE includes at least the MAC CE subheader.
  • the MAC CE includes a payload (payload) in addition to the MAC CE subheader, and the feedback information carried by the feedback CE can be carried in the MAC CE subheader or in the payload. .
  • the MAC CE includes: a MAC CE subheader; wherein, at least part of the values of the multiple LCID values carried by the MAC CE subheader have a corresponding relationship with the feedback information.
  • the Msg4 includes: a medium access control MAC control unit CE; the MAC CE includes: a payload; wherein, the first part of the continuous distribution in the payload does not have a corresponding relationship with the feedback information ; The second part other than the first part in the payload has a corresponding relationship with the feedback information.
  • the payload of the MAC CE of the Msg4 has extension bits; the extension bits are used to carry the feedback information.
  • the payload of the MAC CE of the Msg4 has extension bits; the extension bits are used to carry the feedback information.
  • the payload of the MAC CE has extension bits that carry the feedback information.
  • the extension bits of the payload of the MAC CE may explicitly indicate the feedback information, or may be implicitly indicated by an LCID value having a corresponding relationship with the feedback information.
  • the payload of one MAC CE has 48 bits, which can be used for contention collision resolution between UEs.
  • the 48 bits are used to carry the first 48 bits of the uplink (Uplink, UL) common control channel service data unit (Common Control Channel Service Data Unit, CCCH SDU) carried by the responded UE in Msg3.
  • the first 48 bits of the UL CCCH SDU carried by the Msg3 sent by different UEs are different. Therefore, the first 48 bits of the UL CCCH SDU of the UE with successful random access are copied through the first 48 bits of the MAC CE.
  • each UE After each UE receives the first 48 bits of the MAC CE and the first 48 bits of the UL CCCH SDU carried in the Msg3 sent by itself, if the comparison is consistent, it considers that its random access is successful; otherwise, it can be considered that its random access is successful. Entry failed.
  • the MAC CE in addition to the first type of bits used for the net weight collision between UEs, the MAC CE also includes the second type of bits other than the first type of bits.
  • the second type of bits here may be used to carry the feedback information, or carry an LCID value that has a corresponding relationship with the feedback information. If the number of bits of the first type is 48, the MAC CE containing the bits of the second type must exceed 48 bits.
  • the Msg4 comprises:
  • the first type of MAC CE is used for contention and conflict resolution between UEs
  • the second type of MAC CE carries the feedback information.
  • MAC CE subheader In some cases, whether it is the first type of MAC CE or the second type of MAC CE, in addition to the MAC CE subheader, it can also include: a padding part.
  • the MAC CE subheader can be divided into reserved fields and LCID fields. In one embodiment, if the feedback information in the second type of MAC CE only occupies the bits of the LCID field, it can be considered that the second type of MAC CE
  • the subheader carries an LCID value corresponding to the feedback information, and the LCID value may be a newly added LCID value or an enhanced LCID value.
  • the newly added LCID value (or becomes the enhanced LCID value) may be the code point in Table 1 or the LCID value whose index is 35.
  • the feedback information carried by the second type of MAC CE occupies bits in the reserved field or is carried in the padding part of the second type of MAC CE, it can be considered that the bit value corresponding to the feedback information does not belong to the LCID value.
  • the bit value part of the reserved field is divided into the LCID field to obtain the enhanced LCID field, then it can also be considered that the second type of MAC CE carries the enhanced LCID value that has a corresponding relationship with the feedback information at this time.
  • the first type of MAC CE and the second type of MAC CE are adjacently distributed in the Msg4.
  • the first type of MAC CE and the second type of MAC CE are distributed at different locations in Msg4.
  • the S220 may include: receiving a radio connection control RRC message carrying the feedback information.
  • the UE may also receive the feedback information in an RRC message.
  • the RRC message carrying the feedback information may be a dedicated RRC message specially designed to carry the feedback information.
  • the dedicated RRC message may be an RRC system message response (RRCSystemInfoResponse).
  • the RRC message carrying the feedback information may be an RRC message carrying other contents in the related art multiplexed.
  • the base station may carry the feedback information through the RRC connection establishment message in the RRC message.
  • the UE detects an RRC connection establishment message carrying feedback information, it may establish an RRC connection with the base station, and may not establish an RRC connection but only to obtain feedback information corresponding to the acquisition request sent by itself.
  • the method further includes:
  • S230 In response to receiving the NACK without the duration information, obtain duration information for re-initiating the acquisition request; wherein the duration information indicates an interval duration for the UE to re-initiate the acquisition request. If the feedback information received by the UE is NACK, it means that the network side will not send the request SIB currently. With the change of network load and/or wireless environment, after a period of time, the base station may deliver the SIB or configure the configuration information carried by the SIB requested by the UE. In view of this, the UE may repeatedly send the acquisition request, but how long does it take to send the acquisition request again.
  • the acquisition request is sent too frequently, it will lead to further deterioration of the wireless environment on the one hand, and power consumption of the UE on the other hand. If the sending of the acquisition request is too sparse, the delay from the UE request to the corresponding SIB will increase.
  • the method further includes:
  • the method further includes:
  • the obtaining request is initiated again after an interval according to the duration indicated by the duration information.
  • the obtaining time information when the obtaining request is initiated again includes at least one of the following:
  • the duration information is determined according to the UE's coping strategy for the NACK.
  • the UE may send request information for obtaining the duration information to the network side, and after receiving the request information, the network side may send the duration information to the UE by a broadcast message, a multicast message or a unicast message.
  • the network side may preconfigure the duration information.
  • the duration information may be pre-agreed, and once the duration information is pre-determined, the subsequent UE may use the pre-agreed duration information one or more times to determine The UE initiates an acquisition request for acquiring the same SIB again.
  • the UE internally stores a response strategy for receiving NACK, and determines the duration information according to the response strategy.
  • the interval duration indicated by the duration information determined according to the response strategy can be larger than that of non-power-consuming UEs such as mobile phones or vehicle-mounted terminals according to the response strategy.
  • the interval duration indicated by the duration information can be larger than that of non-power-consuming UEs such as mobile phones or vehicle-mounted terminals according to the response strategy.
  • the interval durations indicated by the duration information mapped to the NACK coping strategies of different SIBs are different.
  • the interval duration indicated by the duration information determined according to the coping strategy is the first duration;
  • the duration indicated by the duration information determined according to the coping strategy may be a second duration.
  • the first duration is different from the second duration.
  • both y1 and y2 are positive integers greater than 2, and are different positive integers greater than 2.
  • the specific size of the first duration and the second duration may be determined according to the urgency or priority of SIBy1 and SIBy2.
  • the urgency of the SIB carrying the earthquake or tsunami notification may be higher than the urgency of the SIB carrying the configuration information of the CSI-RS, so the interval corresponding to the SIB carrying the earthquake or tsunami notification may be smaller than that of the SIB carrying the CSI-RS.
  • the interval length of the SIB of the configuration information may be determined according to the urgency or priority of SIBy1 and SIBy2.
  • an embodiment of the present disclosure provides an apparatus for requesting a system message block, including:
  • the first receiving module 110 is configured to receive an acquisition request requesting a system message block SIB;
  • the first sending module 120 is configured to deliver feedback information for the obtaining request.
  • the first receiving module 110 and the first sending module 120 may both be program modules, and after the program modules are executed by the processor, they can realize the reception of the SIB acquisition request and the transmission of the feedback information. Issued.
  • the first receiving module 110 and the first sending module 120 may be software-hardware combination modules; the software-hardware combination modules include but are not limited to: a programmable array; the programmable array Including but not limited to: field programmable array or complex programmable array.
  • the first receiving module 110 and the first sending module 120 may be pure hardware modules; the pure hardware modules include but are not limited to: application specific integrated circuits.
  • the SIB is an SIBx obtained in an ondemand form, and x is a positive integer equal to or greater than 2.
  • the SIBx is:
  • the SIB that carries the configuration information of the channel state indication CSI-reference signal RS.
  • the first sending module 120 is configured to send a negative reply NACK, wherein the NACK indicates that the network side does not send the requested SIB; or, send a confirmation reply ACK, wherein the ACK, indicating the SIB that the network side sends the request.
  • the first sending module 120 is configured to perform at least one of the following:
  • the NACK is delivered in response to the scheduling information of the requested SIB being in the minimum remaining system information RMSI.
  • the feedback information further includes:
  • auxiliary information is at least for the user equipment UE to determine relevant information required for acquiring the SIB.
  • the feedback information includes not only the feedback indication, but also the auxiliary information.
  • the feedback indication here is the aforementioned NACK or ACK.
  • the assistance information is mainly used to assist the UE to acquire the requested SIB or to stop sending the acquisition request.
  • the auxiliary information includes at least one of the following:
  • duration information indicating the interval duration at which the UE initiates the acquisition request again
  • the available status information indicates whether there is configuration information carried by the SIB requested by the obtaining request, or whether the resource indicated by the configuration information carried by the SIB requested by the obtaining request is available.
  • the first receiving module 110 is configured to receive a first message Msg1 that carries the obtaining request.
  • the first sending module 120 is configured to deliver a second message Msg 2 that carries the feedback information.
  • the feedback information is carried in the MAC random access response RAR of the Msg2.
  • the MAC RAR that carries the feedback information is the second type of MAC RAR; the MAC RAR that does not carry the feedback information is the first type of MAC RAR.
  • the Msg2 that cannot carry the feedback information is the first type Msg2;
  • the Msg2 capable of carrying the feedback information is the second type Msg2.
  • the communication resources of Msg1 corresponding to the first type of Msg2 are different from the communication resources of Msg1 corresponding to the second type of Msg2.
  • the first sending module 120 is further configured to deliver SIB1, wherein the SIB1 carries resource information of the communication resources of Msg1 corresponding to the second type Msg2.
  • the first sending module 120 is configured to deliver the Msg2 carrying the random access preamble RAP ID corresponding to the feedback information.
  • the Msg2 that carries the RAP ID corresponding to the feedback information is the second type Msg2, and the Msg that does not carry the RAP ID corresponding to the feedback information is the first type Msg2.
  • different RAP IDs carried by the Msg2 correspond to feedback information of different SIBs, and the Msg2 does not have a MAC RAR that carries auxiliary information;
  • Different RAP IDs carried by the Msg2 correspond to feedback information of different SIBs, and the Msg2 has a MAC RAR that carries auxiliary information;
  • the RAP IDs corresponding to the feedback information of different SIBs are different,
  • the feedback information of the different SIBs corresponds to the same RAP ID, and the Msg2 carries the identification information of the SIB indicated by the feedback information.
  • the information identification is carried in the identification information field of the Msg2;
  • the identification information field carries one or more information identifications of SIBs corresponding to NACKs;
  • the identifier information field carries one or more information identifiers of the SIB corresponding to the ACK.
  • the identification information field is included in the MAC RAR of the Msg2,
  • a length of the MAC RAR greater than or equal to the length of the identification information field.
  • the identification information field is further used to carry the auxiliary information; wherein, the auxiliary information is at least for the user equipment UE to determine the relevant information required for acquiring the SIB.
  • the Msg2 has a BI subheader of a backoff indicator BI; wherein the BI subheader carries the feedback information.
  • the feedback information is carried by reserved bits of the BI subheader. In this embodiment, it is equivalent to some bits in the BI subheader to indicate BI, and some bits to indicate feedback information.
  • the BI subheader also carries auxiliary information
  • the auxiliary information is at least for the user equipment UE to determine relevant information required for acquiring the SIB.
  • the first receiving module 110 is further configured to receive a third message Msg3 that carries the SIB acquisition request.
  • the first sending module 120 is further configured to deliver a fourth message Msg4 that carries the feedback information.
  • the Msg4 includes: a medium access control MAC control unit CE; the MAC CE includes: a MAC CE subheader;
  • At least some of the multiple LCID values carried by the MAC CE subheader have a corresponding relationship with the feedback information.
  • the Msg4 includes: a medium access control MAC control unit CE; the MAC CE includes: a payload;
  • the first part of the continuous distribution in the payload does not have a corresponding relationship with the feedback information
  • the second part other than the first part in the payload has a corresponding relationship with the feedback information.
  • the payload of the MAC CE of the Msg4 has extension bits; the extension bits are used to carry the feedback information.
  • the Msg4 comprises:
  • the first type of MAC CE is used for contention and conflict resolution between UEs
  • the second type of MAC CE carries the feedback information.
  • the first type of MAC CE and the second type of MAC CE are adjacently distributed in the Msg4.
  • the first sending module 120 is configured to deliver a radio connection control RRC message carrying the feedback information.
  • an embodiment of the present disclosure provides an apparatus for requesting a system message block, including:
  • the second sending module 210 is configured to send an acquisition request requesting the system message block SIB;
  • the second receiving module 220 is configured to receive feedback information for the obtaining request.
  • the second sending module 210 and the second receiving module 220 may both be program modules, and after the program modules are executed by the processor, they can implement the sending of the SIB acquisition request and the feedback information reception.
  • the second sending module 210 and the second receiving module 220 may be software-hardware combination modules; the software-hardware combination modules include but are not limited to: programmable arrays; the programmable arrays include but are not limited to: Not limited to: field programmable array or complex programmable array.
  • the second sending module 210 and the second receiving module 220 may be pure hardware modules; the pure hardware modules include but are not limited to: application specific integrated circuits.
  • the SIB is an SIBx obtained in an ondemand form, and x is a positive integer equal to or greater than 2.
  • the SIBx is:
  • the SIB that carries the configuration information of the channel state indication CSI-reference signal RS.
  • the second receiving module 220 is configured to receive a negative reply NACK, wherein the NACK indicates that the network side does not issue the requested SIB; or, receive a confirmation reply ACK, wherein the ACK, Indicates the SIB of the request issued by the network side.
  • the feedback information further includes:
  • auxiliary information is at least for the user equipment UE to determine relevant information required for acquiring the SIB.
  • the auxiliary information includes at least one of the following:
  • duration information indicating the interval duration at which the UE initiates the acquisition request again
  • the available status information indicates whether there is configuration information carried by the SIB requested by the obtaining request, or indicates whether the resource indicated by the configuration information carried by the SIB requested by the obtaining request is available.
  • the second sending module 210 is configured to send the first message Msg1 that carries the obtaining request.
  • the second receiving module 220 is configured to receive the second message Msg 2 that carries the feedback information.
  • the feedback information is carried in the MAC random access response RAR of the Msg2.
  • the MAC RAR that carries the feedback information is the second type of MAC RAR; the MAC RAR that does not carry the feedback information is the first type of MAC RAR.
  • the Msg2 that cannot carry the feedback information is the first type Msg2; the Msg2 that can carry the feedback information is the second type Msg2.
  • the communication resources of the Msg1 corresponding to the first type Msg2 are different from the communication resources of the Msg1 corresponding to the second type Msg2.
  • the second receiving module 220 is further configured to receive SIB1, wherein the SIB1 carries resource information of the communication resources of the Msg1 of the second type Msg2.
  • the second receiving module 220 is further configured to receive the Msg2 that carries the RAP identifier ID of the random access preamble corresponding to the feedback information.
  • the RAP IDs corresponding to the feedback information of different SIBs are different; or, the feedback information of different SIBs corresponds to the same RAP ID, and the Msg2 carries the identifier of the SIB indicated by the feedback information information.
  • the information identification is carried in the identification information field of the Msg2;
  • the identification information field carries one or more information identifications of SIBs corresponding to NACKs;
  • the identifier information field carries one or more information identifiers of the SIB corresponding to the ACK.
  • the identification information field is included in the MAC RAR of the Msg2,
  • a length of the MAC RAR greater than or equal to the length of the identification information field.
  • the identification information field is further used to carry the auxiliary information; wherein, the auxiliary information is at least for the user equipment UE to determine the relevant information required for acquiring the SIB.
  • the Msg2 has a BI subheader of a backoff indicator BI; wherein the BI subheader carries the feedback information.
  • the feedback information is carried by reserved bits of the BI subheader.
  • the BI subheader also carries auxiliary information
  • the auxiliary information is at least for the user equipment UE to determine relevant information required for acquiring the SIB.
  • the second sending module 210 is configured to send a third message Msg3 that carries the SIB acquisition request.
  • the second receiving module 220 is configured to receive a fourth message Msg4 that carries the feedback information.
  • the Msg4 includes: a medium access control MAC control unit CE; the MAC CE includes: a MAC CE subheader;
  • At least some of the multiple LCID values carried by the MAC CE subheader have a corresponding relationship with the feedback information.
  • the Msg4 includes: a medium access control MAC control unit CE; the MAC CE includes: a payload; wherein, the first part of the payload that is continuously distributed does not have a corresponding relationship with the feedback information ;
  • the second part other than the first part in the payload has a corresponding relationship with the feedback information.
  • the payload of the MAC CE of the Msg4 has extension bits; the extension bits are used to carry the feedback information.
  • the Msg4 comprises:
  • the first type of MAC CE is used for contention and conflict resolution between UEs
  • the second type of MAC CE carries the feedback information.
  • the first type of MAC CE and the second type of MAC CE are adjacently distributed in the Msg4.
  • the receiving feedback information for the obtaining request includes:
  • a radio connection control RRC message carrying the feedback information is received.
  • the apparatus further includes:
  • an acquisition module configured to acquire, in response to receiving the NACK without the duration information, the duration information for re-initiating the acquisition request; wherein the duration information indicates the interval duration of the UE re-initiating the acquisition request .
  • the obtaining module executes at least one of the following:
  • the duration information is determined according to the UE's coping strategy for the NACK.
  • the acquisition methods of system messages are broadcast acquisition and ondemand acquisition.
  • the UE can directly read the system message in the system message window, while for the system message in the form of ondemand, the minimum remaining system message (Remained Minimum System Information, RMSI) has an indication bit (bit) indicating whether it is broadcast or not.
  • RMSI Remained Minimum System Information
  • the system message is whether broadcasting (Broadcasting/notBroadcasting).
  • the user equipment User Equipment, UE
  • the UE For system messages that are not being broadcast, the UE needs to pass Msg1 or Msg3.
  • ACK acknowledgment character
  • the configuration information of Tracking Reference Signal (TRS)/Channel Reference Singal (CRS) does not need to be broadcast all the time in the cell, for example, if there is no idle UE in the network or the idle UE does not support Using the characteristics of the TRS/CRS in the idle state, broadcasting this information can be considered as a waste of resources. Therefore, the best way is to use the UE to obtain the ondemand request.
  • the ondemand request here is one of the aforementioned fetch requests.
  • the ondemand request indicates that the system message scheduling information to be acquired is broadcast in the RMSI in advance, and when the UE acquires the SI after an ondemand request is initiated, it is generally considered that the SI is always successfully requested. Therefore, the ondemand request mechanism defaults to a positive response from the network. However, if the base station may not currently have the TRS/CRS configuration for the UE in the idle state, at this time, the UE may fail to request the TRS/CRS configuration, and there will be a negative reply from the network side.
  • the solutions provided in the embodiments of the present disclosure may be as follows: for a request for a specific SI, the base station provides the requested feedback information, and the feedback information may at least include: a negative acknowledgement (NACK) indicating that the requested system message cannot be provided.
  • NACK negative acknowledgement
  • the specific system message (System Imformaiton, SI) is an SI-x configured to be acquired in the form of ondemand.
  • x may be a positive integer equal to or greater than 2.
  • the SI is the aforementioned SIB.
  • the specific SI-x is configuration information that carries a specific reference signal, such as TRS/CRS used by a UE in a non-connected state.
  • the UEs in the disconnected state here include: UEs in the idle state and/or UEs in the inactive state.
  • the base station provides a negative reply (NACK) to the acquisition request for a specific SI; at this time, the UE understands that the network side does not wish to provide a valid configuration.
  • NACK negative reply
  • the UE goes to request, but the network has no available TRS/CRS transmission resources, so it replies with NACK.
  • the TRS/CRS sending resource may be the time-frequency resource for sending the TRS/CRS.
  • the UE requests one or more SIBs through an acquisition request, but the network has TRS/CRS resource configuration, but it is not available, so the network side replies with NACK.
  • the UE initiates a request for the specific SI; the base station provides a negative reply (NACK) for the request for the specific SI.
  • NACK negative reply
  • Auxiliary information such as duration information can also be carried in the NACK reply of the Ondemand request.
  • the NACK response of the Ondemand request may carry the duration information as T; at this time, the UE understands that the network does not want to provide the duration of effective TRS/CRS transmission, and at this time the UE can be within the duration range indicated by the duration information. No need to request SI again.
  • the existing protocol needs to be modified in Msg2, and the indication of NACK is added.
  • Mode 1 Enhance the media access control payload (MAC payload for Random Access Response) of the random access response, which is used to carry information such as NACK and/or duration information returned by the base station.
  • MAC payload for Random Access Response Enhance the media access control payload (MAC payload for Random Access Response) of the random access response, which is used to carry information such as NACK and/or duration information returned by the base station.
  • the payload here can also be called the net load.
  • the MAC payload for Random Access Response type2 is introduced in the media access control payload of the enhanced random access response.
  • the original MAC payload for Random Access Response is of type 1; MAC RAR type 2 is used to carry ACK or NACK and/or duration information returned by the base station/and further available information of TRS/CRS.
  • the UE of version 1 When the UE of version 1 requests system messages, it will only receive the MAC CE of RAP ID only; while the UE of the new version (ie version 2) will receive the MAC CE of RAP ID and MAC RAR type2. After the UE receives and matches the RAP ID sent by itself, it will further determine Msg2, and determine the feedback information of the network side for the acquisition request of its own SI, for example, the feedback information may be a positive or negative reply.
  • the non-critical extension configuration may be: a configuration for a system message request (SI-RequestConfig), an exemplary example may be as follows:
  • the above is only an example of separately configuring the resources of the type 2 Msg1 and the type 2 Msg2, and there are many specific implementation manners, which are not limited to any one of the above.
  • the Msg1 of type 2 is the aforementioned Msg1 corresponding to the second type of Msg2.
  • the Msg2 of type 2 here is the aforementioned second type Msg2.
  • Method 2 Reserve the RAP ID for the negative reply of a specific SI request.
  • the reserved RAP ID may be the RAP ID that has a corresponding relationship established with the feedback information of the SI request.
  • Case 1 The network reserves the RAP ID for a negative response to a specific SI request.
  • the UE receives the network reserved RAP ID, it implicitly expresses the network's NACK response; at this time, after the UE receives it, it will not continue to try until The maximum number of retransmissions for Msg1 is reached. In this way, the UE can save more power.
  • Case 2 The network reserves the RAP ID for positive and/or negative replies to specific SI requests.
  • the following is an example of NACK.
  • the UE receives the RAP ID reserved by the network, it implicitly expresses the NACK reply of the network; the UE can further check the MAC RAR type2, where the MAC RAR type2 is used to carry the NACK and/or duration information returned by the base station/and TRS/CRS further available information; at this time, the RAR corresponding to the RAP ID reserved by the network is MAC RAR type2.
  • Case 3 The network reserves the NACK RAP ID for a specific SI-i requesting a negative reply to the SI RAP ID-i.
  • the UE receives the NACK RAP ID and SI RAP ID-i reserved by the network, the UE considers that it has received a NACK reply for the specific SI-i request SI RAP ID-i.
  • the RAP IDs reserved by the network in cases 1 to 3 are the RAP IDs corresponding to the feedback information described above.
  • the length of the information field (eg, MAC RAR Type-2) carrying the SI RAP ID-i is the same as the length of the MAC RAR. In this way, it is better to directly include the SI RAP ID-i in a MAC RAR.
  • the information field carrying the SI RAP ID-i can carry multiple SI RAP ID-i, which are used to reply to multiple specific SI-i requests for negative responses of the SI RAP ID-i.
  • the negative reply here is the NACK of the aforementioned acquisition request.
  • the information field carrying the SI RAP ID-2 may also carry duration information/and availability status information indicating whether the TRS/CRS is available.
  • Method 3 Enhance the content of the existing BI subheader as a NACK reply to the ondemand request, that is, use a reserved bit reserved by it to carry more information other than BI. For example, you can use reservation reservation bit to indicate whether the network has no TRS/CRS resources available or if the network has TRS/CRS resources available but currently unavailable.
  • the TRS/CRS resource here is the communication resource for sending the TRS/CRS.
  • the UE of version 1 if it receives a NACK reply from the network, it needs to continue to use BI to initiate the next request until the maximum number of transmissions of Msg1 is reached, and new users can get more information of TRS/CRS.
  • Method 1 Enhance the content of the existing conflict resolution MAC CE as a NACK reply to the ondemand request.
  • An implementation manner is: adding a new LCID value, where the new LCID value may be an enhanced UE contention resolution identity (Contention Resolution Identity).
  • the newly added LCID value may be carried in a new MAC CE.
  • the payload for this new MAC CE may be different from the MAC CE used for conflict resolution between UEs.
  • the payload of the MAC CE used for conflict resolution between UEs is to use the first 48 bits of the UL CCCH SDU carried in Msg3 as the identification of the contention conflict.
  • the MAC CE in the letter can use fewer bits, for example, the first 32 bits are used as the identifier of the contention conflict, and the remaining bits are used to carry NACK, and/or , the synchronization indicates the duration information and/or whether the network has no TRS/CRS resources available or the network has TRS/CRS resources available or is currently unavailable.
  • the newly added LCID value will not be recognized.
  • the UE will obtain a new LCID value.
  • the number of bits of the MAC CE used to resolve the UE Contention Resolution Identity (UE Contention Resolution Identity) is used to carry NACK.
  • a new LCID value is added, and the newly added LCID value is carried in the MAC CE, and the MAC CE carrying the LCID value can be called a feedback CE.
  • the feedback CEs may include NACK CEs carrying NACK and/or ACK CEs carrying ACK.
  • the UE still receives a NACK CE after the conflict between the UEs is resolved, it means that the acquisition request sent by the UE gets a NACK response. If the UE still receives an ACK CE after resolving the conflict based on the MAC CE for conflict resolution between UEs, it means that the acquisition request has received an ACK response from the network side.
  • the position of the feedback CE is immediately after the UE Contention Resolution Identity MAC CE, which is used to implicitly identify the UE Contention Resolution Identity MAC CE associated with the feedback CE.
  • the location of the NACK CE is immediately after the UE Contention Resolution Identity MAC CE, which is used to implicitly identify the UE Contention Resolution Identity MAC CE associated with the NACK CE.
  • the length of the NACK CE can be of two types, namely fixed length and variable length; the subheader of the fixed length NACK CE can be shown in Figure 8A, and the subheader of the variable length NACK CE can be shown in 8B.
  • Enhanced RRC message that is, a new RRC message (RRCSystemInfoResponse) is added to carry feedback information.
  • the feedback information includes: NACK and/or ACK.
  • the RRC message may further include: auxiliary information.
  • the assistance information includes further available information for carrying ACK, NACK and/or duration information/ and TRS/CRS returned by the base station.
  • the NACK reply of the Ondemand request does not carry the duration information; when the UE requests again depends on the time interval configured by the network.
  • the duration interval may be based on network configuration or pre-agreed; in an embodiment, if the NACK reply of the Ondemand request does not carry duration information; when the UE requests again depends on the UE implementation.
  • Embodiments of the present disclosure provide a communication device, including:
  • memory for storing processor-executable instructions
  • the processor is connected to the memory;
  • the processor is configured to execute the method for requesting a system message block provided by any of the foregoing technical solutions.
  • the processor may include various types of storage media, which are non-transitory computer storage media capable of continuing to memorize information stored thereon after the communication device is powered down.
  • the communication device includes a base station or a UE.
  • the processor may be connected to the memory through a bus or the like, for reading executable programs stored on the memory, for example, at least one of the methods shown in FIG. 2 , FIG. 3 , FIG. 9 and/or FIG. 10 .
  • FIG. 13 is a block diagram of a UE (UE) 800 according to an exemplary embodiment.
  • UE 800 may be a mobile phone, computer, digital broadcast user equipment, messaging device, game console, tablet device, medical device, fitness device, personal digital assistant, and the like.
  • UE 800 may include one or more of the following components: processing component 802, memory 804, power supply component 806, multimedia component 808, audio component 810, input/output (I/O) interface 812, sensor component 814, and Communication component 816.
  • the processing component 802 generally controls the overall operations of the UE 800, such as operations associated with display, phone calls, data communications, camera operations, and recording operations.
  • the processing component 802 can include one or more processors 820 to execute instructions to perform all or some of the steps of the methods described above.
  • processing component 802 may include one or more modules that facilitate interaction between processing component 802 and other components.
  • processing component 802 may include a multimedia module to facilitate interaction between multimedia component 808 and processing component 802.
  • Memory 804 is configured to store various types of data to support operation at UE 800 . Examples of such data include instructions for any application or method operating on the UE 800, contact data, phonebook data, messages, pictures, videos, etc.
  • Memory 804 may be implemented by any type of volatile or nonvolatile storage device or combination thereof, such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Magnetic or Optical Disk.
  • SRAM static random access memory
  • EEPROM electrically erasable programmable read only memory
  • EPROM erasable Programmable Read Only Memory
  • PROM Programmable Read Only Memory
  • ROM Read Only Memory
  • Magnetic Memory Flash Memory
  • Magnetic or Optical Disk Magnetic Disk
  • Power supply component 806 provides power to various components of UE 800 .
  • Power components 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to UE 800.
  • Multimedia component 808 includes screens that provide an output interface between the UE 800 and the user.
  • the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from a user.
  • the touch panel includes one or more touch sensors to sense touch, swipe, and gestures on the touch panel. The touch sensor may not only sense the boundaries of a touch or swipe action, but also detect the duration and pressure associated with the touch or swipe action.
  • the multimedia component 808 includes a front-facing camera and/or a rear-facing camera. When the UE 800 is in an operation mode, such as a shooting mode or a video mode, the front camera and/or the rear camera may receive external multimedia data. Each of the front and rear cameras can be a fixed optical lens system or have focal length and optical zoom capability.
  • Audio component 810 is configured to output and/or input audio signals.
  • the audio component 810 includes a microphone (MIC) that is configured to receive external audio signals when the UE 800 is in operating modes, such as call mode, recording mode, and voice recognition mode.
  • the received audio signal may be further stored in memory 804 or transmitted via communication component 816 .
  • audio component 810 also includes a speaker for outputting audio signals.
  • the I/O interface 812 provides an interface between the processing component 802 and a peripheral interface module, which may be a keyboard, a click wheel, a button, or the like. These buttons may include, but are not limited to: home button, volume buttons, start button, and lock button.
  • Sensor component 814 includes one or more sensors for providing various aspects of status assessment for UE 800 .
  • the sensor component 814 can detect the open/closed state of the device 800, the relative positioning of components, such as the display and keypad of the UE 800, the sensor component 814 can also detect the position change of the UE 800 or a component of the UE 800, the user and the UE 800. Presence or absence of UE800 contact, UE800 orientation or acceleration/deceleration and UE800 temperature changes.
  • Sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects in the absence of any physical contact.
  • Sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications.
  • the sensor assembly 814 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
  • Communication component 816 is configured to facilitate wired or wireless communications between UE 800 and other devices.
  • the UE 800 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof.
  • the communication component 816 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel.
  • the communication component 816 also includes a near field communication (NFC) module to facilitate short-range communication.
  • NFC near field communication
  • the NFC module may be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.
  • RFID radio frequency identification
  • IrDA infrared data association
  • UWB ultra-wideband
  • Bluetooth Bluetooth
  • UE 800 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gates An array (FPGA), controller, microcontroller, microprocessor, or other electronic component implementation for performing the above method.
  • ASICs application specific integrated circuits
  • DSPs digital signal processors
  • DSPDs digital signal processing devices
  • PLDs programmable logic devices
  • FPGA field programmable gates
  • controller microcontroller, microprocessor, or other electronic component implementation for performing the above method.
  • non-transitory computer-readable storage medium including instructions, such as a memory 804 including instructions, which are executable by the processor 820 of the UE 800 to perform the above method.
  • the non-transitory computer-readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.
  • an embodiment of the present disclosure shows a structure of a base station.
  • the base station 900 may be provided as a network-side device.
  • base station 900 includes a processing component 922, which further includes one or more processors, and a memory resource, represented by memory 932, for storing instructions executable by processing component 922, such as application programs.
  • An application program stored in memory 932 may include one or more modules, each corresponding to a set of instructions.
  • the processing component 922 is configured to execute instructions to execute any of the aforementioned methods applied to the base station, eg, as shown in FIG. 2 , FIG. 3 , FIG. 9 and/or FIG. 10 .
  • the base station 900 may also include a power supply assembly 926 configured to perform power management of the base station 900, a wired or wireless network interface 950 configured to connect the base station 900 to a network, and an input output (I/O) interface 958.
  • Base station 900 may operate based on an operating system stored in memory 932, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM or the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开实施例提供一种请求系统消息块的方法及装置、通信设备及存储介质。所述请求系统消息块的方法可包括：接收请求系统消息块SIB的获取请求；下发针对所述获取请求的反馈信息。

Description

请求系统消息块的方法及装置、通信设备及存储介质 技术领域
本公开涉及无线通信技术领域但不限于无线通信技术领域，尤其涉及一种请求系统消息块的方法及装置、通信设备及存储介质。
背景技术
基站会通过广播方式发送系统消息。系统消息包括：主消息块(Master Information Block，MIB)和系统消息块(System Information Block，SIB)。SIB又分为SIB1和其他的SIB。其他SIB可包括：SIB2、SIB 3及SIB 4…。MIB携带了UE接入小区所需的最必要的信息。
举例来说，MIB包括系统帧号和/或子载波间隔等信息。
SIB1携带了其他SIB的调度信息、接入控制信息和小区选择信息等。
其他SIB携带了其他功能所需的参数，比如小区重选、定位、紧急通知及直连链路(Sidelink，SL)等。UE需要一直获取MIB和SIB1。对于其他SIB，UE根据自己的需要选择其中的信息进行读取。
当系统消息发生变更时，基站会发送短消息。短消息会携带系统消息修改通知，来通知UE系统信息发生更改。UE收到短消息之后，会读取并获得更新的系统信息。
短消息中还会携带紧急消息通知，如果UE支持获取紧急消息，则在收到通知后，会读取SIB6、SIB7和SIB8，来获取紧急消息的内容。
发明内容
本公开实施例提供一种请求系统消息块的方法及装置、通信设备及存储介质。
本公开实施例第一方面提供一种请求系统消息块的方法，包括：
接收请求系统消息块SIB的获取请求；
下发针对所述获取请求的反馈信息。
本公开实施例第二方面提供一种请求系统消息块的方法，包括：
发送请求系统消息块SIB的获取请求；
接收针对所述获取请求的反馈信息。
本公开实施例第三方面提供一种请求系统消息块的装置，包括：
第一接收模块，被配置为接收请求系统消息块SIB的获取请求；
第一发送模块，被配置为下发针对所述获取请求的反馈信息。
本公开实施例第四方面提供一种请求系统消息块的装置，包括：
第二发送模块，被配置为发送请求系统消息块SIB的获取请求；
第二接收模块，被配置为接收针对所述获取请求的反馈信息。
本公开实施例第五方面提供一种通信设备，包括处理器、收发器、存储器及存储在存储器上并能够有所述处理器运行的可执行程序，其中，所述处理器运行所述可执行程序时执行如前述第一方面或第二方面提供的请求系统消息块的方法。
本公开实施例第六方面提供一种计算机存储介质，所述计算机存储介质存储有可执行程序；所述可执行程序被处理器执行后，能够实现前述的＝第一方面或第二方面提供的请求系统消息块的方法。
本公开实施例提供的请求系统消息块的方法装置、通信设备及存储介质，网络侧在接收到请求SIB的获取请求之后，会下发答复所述获取请求的反馈信息。如此，UE在接收到该反馈信息之后，会根据反馈信息的信息内容，确定是否需要重新发送获取请求，或者等待网络侧下发所请求的SIB；从而减少了UE在网络侧不会下发所请求SIB时重复请求或持续监听等到导致的功耗，节省了UE的功耗，且减少了因为UE重复发送获取请求对无线 环境的影响。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本公开实施例。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本发明实施例，并与说明书一起用于解释本发明实施例的原理。
图1是根据一示例性实施例示出的一种无线通信系统的结构示意图；
图2是根据一示例性实施例示出的一种请求系统消息块的方法的流程示意图；
图3是根据一示例性实施例示出的随机接入过程的流程示意图；
图4是根据一示例性实施例示出的一种MAC PDU的格式示意图；
图5是根据一示例性实施例示出的一种MAC RAR的格式示意图；
图6是根据一示例性实施例示出的一种BI子头的格式示意图；
图7是根据一示例性实施例示出的一种MAC CE的格式示意图；
图8A是根据一示例性实施例示出的一种MAC CE的格式示意图；
图8B是根据一示例性实施例示出的一种MAC CE的格式示意图；
图9是根据一示例性实施例示出的一种请求系统消息块的方法的流程示意图；
图10是根据一示例性实施例示出的一种请求系统消息块的方法的流程示意图；
图11是根据一示例性实施例示出的一种请求系统消息块的装置的结构示意图；
图12是根据一示例性实施例示出的一种请求系统消息块的装置的结构示意图；
图13是根据一示例性实施例示出的一种UE的结构示意图；
图14是根据一示例性实施例示出的一种基站的结构示意图。
具体实施方式
这里将详细地对示例性实施例进行说明，其示例表示在附图中。下面的描述涉及附图时，除非另有表示，不同附图中的相同数字表示相同或相似的要素。以下示例性实施例中所描述的实施方式并不代表与本发明实施例相一致的所有实施方式。相反，它们仅是与如所附权利要求书中所详述的、本发明实施例的一些方面相一致的装置和方法的例子。
在本公开实施例使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本公开实施例。在本公开实施例和所附权利要求书中所使用的单数形式的“一种”、“一个”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。
应当理解，尽管在本公开实施例可能采用术语第一、第二、第三等来描述各种信息，但这些信息不应限于这些术语。这些术语仅用来将同一类型的信息彼此区分开。例如，在不脱离本公开实施例范围的情况下，第一信息也可以被称为第二信息，类似地，第二信息也可以被称为第一信息。取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”。
请参考图1，其示出了本公开实施例提供的一种无线通信系统的结构示意图。如图1所示，无线通信系统是基于蜂窝移动通信技术的通信系统，该无线通信系统可以包括：若干个UE11以及若干个基站12。
其中，UE11可以是指向用户提供语音和/或数据连通性的设备。UE11可以经无线接入网(Radio Access Network，RAN)与一个或多个核心网进行通信，UE11可以是物联网UE，如传感器设备、移动电话(或称为“蜂窝”电话)和具有物联网UE的计算机，例如，可以是固定式、便携式、袖珍式、 手持式、计算机内置的或者车载的装置。例如，站(Station，STA)、订户单元(subscriber unit)、订户站(subscriber station)、移动站(mobile station)、移动台(mobile)、远程站(remote station)、接入点、远程UE(remote terminal)、接入UE(access terminal)、用户装置(user terminal)、用户代理(user agent)、用户设备(user device)、或用户UE(user equipment，UE)。或者，UE11也可以是无人飞行器的设备。或者，UE11也可以是车载设备，比如，可以是具有无线通信功能的行车电脑，或者是外接行车电脑的无线通信设备。或者，UE11也可以是路边设备，比如，可以是具有无线通信功能的路灯、信号灯或者其它路边设备等。
基站12可以是无线通信系统中的网络侧设备。其中，该无线通信系统可以是第四代移动通信技术(the 4th generation mobile communication，4G)系统，又称长期演进(Long Term Evolution，LTE)系统；或者，该无线通信系统也可以是5G系统，又称新空口(new radio，NR)系统或5G NR系统。或者，该无线通信系统也可以是5G系统的再下一代系统。其中，5G系统中的接入网可以称为NG-RAN(New Generation-Radio Access Network，新一代无线接入网)。或者，MTC系统。
其中，基站12可以是4G系统中采用的演进型基站(eNB)。或者，基站12也可以是5G系统中采用集中分布式架构的基站(gNB)。当基站12采用集中分布式架构时，通常包括集中单元(central unit，CU)和至少两个分布单元(distributed unit，DU)。集中单元中设置有分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层、无线链路层控制协议(Radio Link Control，RLC)层、媒体访问控制(Media Access Control，MAC)层的协议栈；分布单元中设置有物理(Physical，PHY)层协议栈，本公开实施例对基站12的具体实现方式不加以限定。
基站12和UE11之间可以通过无线空口建立无线连接。在不同的实施 方式中，该无线空口是基于第四代移动通信网络技术(4G)标准的无线空口；或者，该无线空口是基于第五代移动通信网络技术(5G)标准的无线空口，比如该无线空口是新空口；或者，该无线空口也可以是基于5G的更下一代移动通信网络技术标准的无线空口。
在一些实施例中，UE11之间还可以建立E2E(End to End，端到端)连接。比如车联网通信(vehicle to everything，V2X)中的V2V(vehicle to vehicle，车对车)通信、V2I(vehicle to Infrastructure，车对路边设备)通信和V2P(vehicle to pedestrian，车对人)通信等场景。
在一些实施例中，上述无线通信系统还可以包含网络管理设备13。
若干个基站12分别与网络管理设备13相连。其中，网络管理设备13可以是无线通信系统中的核心网设备，比如，该网络管理设备13可以是演进的数据分组核心网(Evolved Packet Core，EPC)中的移动性管理实体(Mobility Management Entity，MME)。或者，该网络管理设备也可以是其它的核心网设备，比如服务网关(Serving GateWay，SGW)、公用数据网网关(Public Data Network GateWay，PGW)、策略与计费规则功能单元(Policy and Charging Rules Function，PCRF)或者归属签约用户服务器(Home Subscriber Server，HSS)等。对于网络管理设备13的实现形态，本公开实施例不做限定。
如图2所示，本公开实施例提供一种请求系统消息块的方法，其中，包括：
S110：接收请求系统消息块SIB的获取请求；
S120：下发针对所述获取请求的反馈信息。
该方法可应用网络侧的基站中，该基站可为演进型基站(envolved Node B，enB)或者下一代基站(Next Generation B，gNB)等各种基站。
接收到UE发送的请求SIB的获取请求。该获取请求包括但不限于： ondemand请求。
在本公开实施例中，接收到该获取请求之后，会向UE发送反馈信息。该反馈信息可包括：指示确认下发所请求的SIB的确认反馈和/或拒绝发送所请求SIB的否认反馈。
通过反馈信息的下发，如此，UE就知道网络侧是否会下发自身请求的SIB，而不是一律默认网络侧下发自身请求的所有SIB，或者，在未接收到请求的SIB时一直发送请求对应SIB的获取请求；减少了UE一直得到不到网络侧对获取请求的回馈导致的UE的不停等待和/或不停发送请求所产生的功耗。
在一些实施例中，SIB1是与其他SIB不耦合发送的单独发送的系统消息块。所述SIB为按需ondemand形式获取的SIBx，x为等于2或大于2的正整数。
此处的SIBx包括但不限于：SIB2、SIB3、SIB4、SIB5、SIB6、SIB7或SIB8或者SIB9等。当然此处仅是对获取请求所请求的SIB的举例，具体实现时不局限上述举例。
在一些实施例中，所述反馈信息所针对的SIB可为携带向非连接态的UE提供SIB。所述非连接态的UE包括但不限于：空闲态的UE和/或非激活态的UE。
可以理解地，所述SIBx为：携带跟踪参考信号(Tracking Rfeference Signal，TRS)TRS的配置信息的SIB；和/或，携带信道状态信息参考信号(Channel State Indicator，CSI)-(Reference Signal，RS)的配置信息的SIB。
所述配置信息包括但不限于：发送资源的资源信息。该发送资源包括但不限于：频域资源、时域资源和/或波束资源。
可以理解地，所述配置信息可包括：发送TRS的图样的指示信息；和/ 或发送CSI-RS的图样的指示信息。所述图样可为频域资源的图样，和/或时域资源的图样。
所述TRS可用于UE进行相位噪声估计。
所述CSI-RS可用于UE对当前无线信道进行信道质量估计。
在一些实施例中，所述S120可包括：下发否定答复(Negative Acknowledge，NACK)，其中，所述NACK，指示网络侧不下发请求的SIB；或者，下发确定答复(Acknowledge，ACK)，其中，所述ACK指示网络侧下发请求的SIB。
本公开实施例中的反馈信息可为NACK，例如，若UE未接收到携带反馈信息，则可认为网络侧给出的ACK。根据统计数据，网络侧下发NACK的概率比ACK的概率低，为了减少信令开销，更多的沿用相关技术中，本公开实施例中提供的反馈信息可为NACK。若下发的NACK，则说明网络侧不会发送UE所请求的SIB。
若网络侧下发ACK，说明网络侧会下发获取请求对应的SIB，UE到对应SIB的发送资源位置上接收所请求的SIB即可，而不用继续发送获取请求以重复请求SIB的下发。
在一个实施例中，所述S120可包括以下至少之一：
响应于未配置请求的SIB携带的配置信息所指示的资源，下发所述NACK；
响应于配置有请求的SIB携带的配置信息所指示资源且所述配置信息所指示资源的不可用，下发所述NACK；
响应于请求的SIB的调度信息在最小剩余系统信息RMSI中，下发所述NACK。例如，在确定是否需要配置SIB的发送资源时，基站发现小区处于非连接态的UE很少甚至无处于非连接态的UE，则可以从节省通信资源使得有更多通信资源用于其他信息发送其他信息，则可能没有未TRS和/ 或CSI-RS等配置发送资源，则相当于部分基于ondemand获取的SIB不存在。在这种情况下，基站自然下发NACK。
再例如，基站虽然有未对应的参考信号和/或控制信息配置发送资源，但是由于紧急业务数据等情况，该配置的发送资源已经被占用或者被传输优先级更高的其他控制信息和/或业务数据所挤占，因此网络侧没有发送资源来下发对应的参考信号和/或控制信息，因此携带这些参考信号和/或控制信息的配置信息的SIB也就不存在，基站侧同样可发送NACK告知UE不用再继续等待请求的SIB或者重复请求对应的SIB。
此处的响应于配置有请求的SIB携带的配置信息所指示资源且所述配置信息所指示资源不可用，可认为：SIB携带的配置信息所指示资源没有发送对应该配置信息对应的参考信号和/或控制信息。
在另一个实施例中，若基站侧已经下发了对应SIB所携带配置信息，基站侧可认为没有必要重复发送，同样可发送NACK。
例如，所请求SIB携带的配置信息已经在最小剩余系统消息(RMSI)携带，则基站可下发NACK。如此，UE接收到NACK，则可以到RMSI提取所请求SIB所需携带的信息内容。在一些情况下，若该UE没有收到对应的RMSI，该UE可以请求相邻位置处的UE获取RMSI。
在一些实施例中，所述反馈信息还包括：
辅助信息，其中，所述辅助信息，至少供用户设备UE确定用于获取所述SIB所需的相关信息。
即在这种情况下，反馈信息不仅包括反馈指示，还包括辅助信息。此处的反馈指示即为前述NACK或ACK。
该辅助信息，可用于UE获取所请求SIB的相关信息，例如，指示UE何时能够发起再次请求该SIB的获取请求，和/或，指示所请求SIB内所携带配置信息对应的配置资源是否可用。
通过该辅助信息的下发，则UE知晓是否需要再次发起获取请求、何时发起获取请求等。
在另一些实施例中，所述辅助信息还可携带有：反馈信息携带的是NACK的原因信息。举例来说，UE请求携带有TRS/CSI-RS的配置信息的SIB，基站发现当前没有配置TRS/CSI-RS的发送资源，或者配置的发送资源出现被挤占等不可用的状态时，则下发所请求SIB也没有用，则基站会反馈NACK，同时告知发送NACK的原因，基于该原因UE就能够知晓基站发送NACK的原因，从而不重复发起获取请求或者持续等待。
在一个实施例中，所述辅助信息包括以下至少之一：
时长信息，指示所述UE再次发起所述获取请求的间隔时长；
可用状态信息，指示是否有所述获取请求所请求SIB携带的配置信息，或指示所述获取请求所请求SIB的携带配置信息所指示资源是否可用。
通过间隔时长的设置，减少UE频繁发起获取请求，减少因为频繁发起获取请求导致的无线环境恶化的现象。
导致请求的SIB无需下发的原因至少有两种，一种是：网络侧没有配置对应所请求SIB包含的配置信息，即没有为相应的参考信号和/或控制信息配置参考信号的发送资源；或者，网络侧有配置所请求SIB包含的配置信息，但是该配置信息现在处于无效状态，即该配置信息所指示的发送资源处于被其他控制信息和/或业务数据所挤占的不可用状态。
在一些实施例中，该获取请求是由处于非连接态的UE发送的，则此时基站是在随机接入过程中接收所述获取请求，例如，S110包括但不限于：在随机接入过程中的第一消息Msg1或第三消息Msg3中接收所述获取请求。此处非连接态的UE包括：空闲态UE和/或非激活态的UE。
图3所示为一种4步随机接入过程的流程示意图，在4步随机接入过程中：
UE向基站发送Msg1；Msg1携带有UE请求随机接入的随机接入前导码(Random Access Preamble，RAP)标识(Identity，ID)；
基站若挑选该UE进行随机接入，则会下发Msg2，该Msg2若携带了该UE上报的RAP ID；
UE在接收到携带自身的PRA ID的Msg2之后，会向基站发送Msg3；
基站接收到Msg3之后会下发Msg4，Msg4由MAC协议数据单元(Protocol Data Unit，PDU)构成。
Msg1可理解为随机接入过程中携带有随机接入前导码的随机接入请求。
Msg3可理解为：UE在接收到基于Msg1后下发了Msg2之后发送的消息。Msg2可包含随机接入响应(Random Access Response，RAR)。
在另一些实施例中，所述方法还包括：接收寻呼消息发送的寻呼响应携带的所述获取请求。
若获取请求携带在Msg1中，则反馈信息可以携带在Msg2和/或Msg4中。为了使得UE尽可能快地获得反馈信息，将所述反馈信息携带在Msg2中。
所述Msg2中可携带一个或多个指示所述反馈信息的反馈比特。
例如，所述Msg2中一个或多个比特指示所述反馈信息。一个比特具有两个比特值，分别是“0”及“1”。
在一种情况下，该反馈比特的比特值为“0”表示网络侧指示确认反馈，则该比特值为“1”表示否认反馈。在另一种情况下，该反馈比特的比特值为“1”表示网络侧指示确认反馈，则该比特值为“0”时表示网络侧指示否认反馈。
在一个实施例中，所述反馈比特可为Msg2的消息格式中预留比特构成，也可以是在Msg2的消息格式中的扩展比特构成。此处的扩展比特可为 新增比特。
Msg2对应的MAC PDU至少携带有MAC子PDU。在一些场景下，该MAC PDU除了包括MAC子PDU之外，还会包括填充(pading)。填充是Msg2中的MAC PDU的可选内容。
参考图4所示，一个MAC子PDU可至少包括一个子头。一个MAC子PDU除了包括一个子头以外，还可以包括对应的MAC RAR。MAC子PDU携带有RAP ID，若该RAP ID为某一个UE发送，则表示该MAC子PDU关联的MAC RAR为发送给该UE，该UE可以基于MAC RAR发送第三消息。
本公开实施例中反馈信息可以携带在MAC RAR中。例如，所述反馈比特可以携带在MAC RAR中。
图4所示的MAC PDU中第3个MAC子PDU为携带有反馈信息的MAC子PDU。图4中以反馈信息为NACK进行举例，在第3个MAC子PDU中存在一个RAP ID子头和一个第二类型的MAC RAR。
根据MAC RAR是否携带有反馈信息，可以将MAC RAR分为第一类型MAC RAR和第二类型MAC RAR；第一类型MAC RAR不携带反馈信息，第二类型MAC RAR携带反馈信息。第一类型MAC RAR携带的信息可包括：各种传输的授权信息，例如，物理上行共享信道的授权信息。
在本公开实施例中，所述反馈信息携带在第二类型MAC RAR中，则对应UE接收到Msg2，将根据相关技术随机接入过程中基于RAP ID匹配的技术，UE匹配RAP ID是发送给自身之后，则UE将继续解码所述第二类型MAC RAR获取所述反馈信息，从反馈信息获取到基站的ACK或者NACK指示。此后UE决定后续随机接入流程或者是否继续请求SIB或者等待接收SIB。比如，若收到NACK，则终止本次随机接入过程，例如，不再继续发送Msg3。比如，收到Msg2携带的RAP ID与UE在Msg1中发送 的RAP ID的不同，则UE中止本次随机接入过程。
在一些实施例中，由于在Msg2中引入反馈信息，则可以根据是否能够携带反馈信息，将Msg2分为两个类型。
一个类型的Msg2继续沿用不携带反馈信息的信息格式，这种信息格式的Msg2构成了第一类型Msg2；另一个类型的Msg2将携带反馈信息的信息格式，这种信息格式的Msg2为第二类型Msg2。
故在本公开实施例中提供的Msg2可以分为：不能够携带所述反馈信息的Msg2为第一类型Msg2；和能够携带所述反馈信息的Msg2为第二类型Msg2。
在一个实施例中，对应于所述第一类型Msg2的Msg1的通信资源，不同于对应于所述第二类型Msg2的Msg1的通信资源。
第一类型Msg2和第二类型Msg2所对应的Msg1的通信资源不同，则基站侧根据UE发送Msg1所使用的通信资源，就可以确定出以哪种类型的Msg2回复UE。
在一些实施例中，对应于第二类型Msg2的Msg1的通信资源，可对于不支持第二类型Msg2的UE而言是不可见的。例如，对应于第二类型Msg2的Msg1的通信资源可以是非关键性扩展的配置。
这种非关键性扩展的配置是一种可选配置。在进行配置时，网络侧可以选择该非关键性扩展的配置，也可以不选择该非关键性扩展的配置。若网络侧未选择该非关键性扩展的配置，则网络侧未配置采用第二类型Msg2进行反馈信息下发。
在一个实施例中，由于基站下发第一类型Msg2和第二类型Msg2的Msg1所使用的通信资源不同，则此时，基站根据接收Msg1的通信资源，可以简便的确定出Msg1是否携带有获取请求，需要以哪种信息格式来解码接收到Msg1，从而简化基站侧对Msg1的解码。
当然在一些实施例中，携带有获取请求的Msg1和不携带获取请求的Msg1可以复用相同的通信资源，基站侧在接收到Msg1之后，分别以携带有获取请求和不携带有获取请求的Msg1的信息格式进行Msg1的解码，比如，此时Msg1的类型，可以通过其携带随机接入前导码的ID进行区分。
在一个实施例中，所述方法还包括：下发SIB1，其中，所述SIB1中携带有所述第二类型Msg2所对应Msg1的通信资源的资源信息。
在本公开实施例中，Msg1的通信资源携带在广播发送的SIB1中，如此即便非连接态的UE也能够接收到上述Msg1的通信资源的资源信息。
所述Msg2携带所述反馈信息的方式包括：
显性携带，即通过专门的反馈比特指示所述反馈信息；
隐性携带，即通过与其他信息共用指示比特指示所述反馈信息，例如，反馈信息与特定信息具有对应关系，对应的至少比特携带特定信息时，就相当于同时指示对应的特定信息和所述反馈信息。
所述特定信息包括但不限于：随机接入前导码(Random Access Preamble，RAP)ID。
该RAP ID可为分为至少两类，一类是与反馈信息建立有对应关系的RAP ID，另一个类是未与反馈信息建立有对应关系的RAP ID。
例如，建立与反馈信息建立有对应关系的RAP ID，则UE接收到这种RAP ID之后，就知晓网络侧对UE请求的SIB的反馈信息，进而根据反馈信息确定出执行下一步的操作，例如，是否继续发送获取请求，或者需要到对应的资源上接收SIB等。
与反馈信息建立有对应关系的RAP ID可为：相关技术中预留的RAP ID。此处的预留的RAP ID可由网络侧预先通知UE，或者，由通信协议规定。
在本公开实施例中，与反馈信息对应的RAP ID至少包括：与NACK 对应的RAP ID。即Msg2至少可携带与NACK具有对应关系的RAP ID。
在一些实施例中，为了方便UE解码，所述第二类型Msg2还具有类型字段，所述类型字段指示Msg2的类型。
在一些实施例中，第一类型Msg2和第二类型Msg2，不用通过专门的类型字段进行去区分。可以理解的，通过Msg2所携带字段的类型区分第一类Msg2和第二类型Msg2；和/或，通过Msg2所携带的信息内容来区分第一类Msg2和第二类型Msg2。例如，第一类型Msg2携带第一类型MAC RAR；第二类型Msg2携带第二类型MAC RAR。再例如，第二类型Msg2携带与反馈信息具有对应关系的RAP ID；第一类型Msg2携带与反馈信息不具有对应关系的RAP ID。
该类型字段包括一个或多个比特，该类型字段也可以称之为类型标志(Flag)，可以用于指示当前Msg2是不是第二类型Msg2，或者，直接指示当前Msg2是第一类型的Msg1还是第二类型Msg2。当前Msg2可为包含所述类型字段的Msg2。
所述Msg2携带的与所述反馈信息具有对应关系的RAP ID，具有如下特点的至少之一：
不同RAP ID与不同所述SIB的反馈信息具有对应关系；
一个所述RAP ID与多个所述SIB的反馈信息具有对应关系。
响应于一个所述RAP ID与多个所述SIB的反馈信息具有对应关系，则所述Msg2还携带有所述反馈信息对应的SIB的信息标识。
即，在所述对应关系中；不同SIB的反馈信息对应的RAP ID不同；或者，不同所述SIB的反馈信息对应相同的RAP ID，且所述Msg2携带有所述反馈信息所指示的SIB的标识信息。
所述不同SIB的反馈信息对应的RAP ID不同，至少包括：不同SIB的NACK对应的RAP ID不同。
所述不同所述SIB的反馈信息对应相同的RAP ID，至少包括：不同SIB的NACK对应相同的RAP ID。
根据第二类型Msg2的携带内容不同可以分为以下几种情况：
情况1：第二类型Msg2携带与反馈信息具有对应关系的RAP ID，不在携带辅助信息和/或反馈信息所对应SIB的信息标识；
情况2：第二类型Msg2携带与一个SIB反馈信息具有对应关系的RAP ID；进一步地，在这种情况下，第二类型Msg2还可以携带前述辅助信息中的一个或多个；
情况3：第二类型Msg2携带与多个SIB反馈信息具有对应关系的RAP ID及该RAP ID所对应的SIB的信息标识。进一步地，在这种情况下，该第二类型Msg2还可以携带前述辅助信息中的一个或多个。
在情况1和情况2下，第二类型Msg2中携带RAP ID都可以对应于一个SIB的反馈信息，如此，UE接收到对应的RAP ID之后就知道对应SIB的反馈信息。
在情况3下，UE接收到同时对应于多个SIB的反馈信息的RAP ID之后，还会根据信息标识确定该RAP ID作用于哪个RAP ID对应的SIB。
采用情况3的方式，则与SIB的反馈信息具有对应关系的RAP ID的数量可以比较少，例如，可以仅为一个或者两个等少量个数。若这种与多个SIB的反馈信息具有对应关系的RAP ID有多个时，不同的RAP ID可对应于不同SIB的反馈信息；如此，第二类型Msg2中携带标识信息的信息比特可以相应的减少。
在一个实施例中，根据RAP ID与SIB的反馈信息的对应关系，及携带有反馈信息的Msg2是否携带有辅助信息，可以分为以下四种情况：
情况1：所述Msg2携带的不同RAP ID对应于不同SIB的反馈信息，且所述Msg2不具有携带有辅助信息的MAC RAR；
或者，
情况1：所述Msg2携带的相同RAP ID对应于不同SIB的反馈信息，且所述Msg2不具有携带有辅助信息的MAC RAR；
或者，
情况1：所述Msg2携带的不同RAP ID对应于不同SIB的反馈信息，且所述Msg2具有携带有辅助信息的MAC RAR；
或者，
情况4：所述Msg2携带的相同RAP ID对应于不同SIB的反馈信息，且所述Msg2具有携带有辅助信息的MAC RAR。
在一个实施例中，所述Msg2还携带有具有所述反馈信息的SIB的信息标识。
该信息标识可以是在一个RAP ID对应于一个SIB的反馈信息时携带，也可以是在一个RAP ID对应于多个SIB的反馈信息时携带，处于减少比特开销的考虑，信息标识可以仅仅在一个RAP ID对应于多个SIB的反馈信息时携带。
在一个实施例中，该信息标识可以由专用的比特显性指示，也可以和其他信息建立对应关系的方式进行隐性指示。
在该信息标识是由专用的比特显性指示时，所述信息标识携带在所述Msg2的标识信息域内；所述标识信息域携带有一个或多个与NACK对应的SIB的信息标识；或者，所述标识信息域携带一个或多个与ACK对应的SIB的信息标识。
在第二类型Msg2中引入了标识信息域，该标识信息域可专门用于放置反馈信息与RAP ID具有对应关系的SIB的信息标识。当然该信息标识域还可以用于携带前述的辅助信息。
所述标识信息域包含在所述Msg2的MAC RAR中，且一个所述MAC RAR的长度，大于或等于所述标识信息域的长度。
例如，一个Msg2的协议数据单元(Protocol Data Unit，PDU)可包括多个MAC子PDU；一个MAC子PDU包括一个RAP ID子头(subheader)和MAC随机接入响应(Random Access Response，RAR)。RAP ID子头用于携带RAP ID；MAC RAR用于携带随机接入响应。
在本公开实施例中，所述标识信息域可包含在MAC RAR中，且标识信息域的长度小于或等于标识信息域的长度，如此，可以在与相关技术中MAC子PDU格式的兼容。若标识信息域的长度刚好等于MAC RAR的长度，则MAC RAR没有剩余比特，此时在MAC RAR层面的格式没有变更。若标识信息域的长度小于MAC RAR的长度，则MAC RAR有剩余比特，该剩余比特可以作为预留比特或者携带其他信息，如此在MAC RAR层面的信息格式有变更。
具体所述标识信息域的长度是小于或等于所述MAC RAR的长度，可以根据当前的无线传输需求来选择。
在另一个实施例中，所述标识信息域的长度可以超过MAC RAP的长度。例如，若标识信息域的长度超过一个MAC RAP的长度时，一个MAC子PDU具有扩展比特，则标识信息域同时包含MAC RAP的信息比特和扩展比特。此处的扩展比特是一个MAC子PDU内的新增比特。
在一些实施例中，若Msg2携带辅助信息，且Msg2中设置有信息标识域，则所述标识信息域还用于携带所述辅助信息；其中，所述辅助信息，至少供用户设备UE确定用于获取所述SIB所需的相关信息。辅助信息的相关描述可以参见前述对应实施例，此处就不重复了。
值得注意的是：Msg2携带的辅助信息，可以携带在信息标识域内，也可以携带在信息标识域外。
图5所示为本公开实施例提供的第二类型MAC RAR的一种格式示例。
第二类型的MAC RAR可包括多个字节，在图5中一个第二类型MAC RAR包含8个八位组(octet)，分别是oct0至oct7。图5中所示的第二类型MAC RAR具有一个SI RAP ID-i域，该SI RAP ID-i域可至少用于携带前述的反馈信息所对应SIB的标识信息。在一些实施例中，SI RAP ID-i域还可以用于携带辅助信息。
所述Msg2具有退避指示符BI的BI子头；其中，所述BI子头携带所述反馈信息。
所述Msg2的MAC子PDU中还携带有BI。该BI指示的随机接入的退避值。接收到该Msg2的UE会根据BI子头内的BI进行随机接入退避，在退避值达到所述BI指示的值之后，可再次发起随机接入，即再次发送Msg1。
在一个实施例中，在Msg2的有一个MAC子PDU中携带有所述BI的BI子头。参考图4所示，在构成Msg2的MAC PDU中，第1个MAC子PDU是携带BI的MAC子PDU。在图4中第1个MAC子PDU的子头可以称为BI子头。
在图4中各个MAC子PDU的子头内的E字段，可用于指示其所在子头是否有其他字段；T字段，可用于指示其所在子头是否包含RAP ID；例如，第1个MAC子PDU的子头内，T字段指示其所在子头包含的不是RAP ID而是BI子头。而BI子头携带有BI。在图4中携带有RAP ID的子头可以称之为RAP ID子头。
在本公开实施例中，所述反馈信息可以使用BI子头中的剩余比特来携带。例如，BI子头中的预留比特中的一个或多个，可以用于指示反馈信息，例如，指示反馈信息中的ACK或NACK。
在一些实施例中，所述BI子头还携带有前述的辅助信息，此处地，所述辅助信息，至少供用户设备UE确定用于获取所述SIB所需的相关信息。
例如，BI子头的预留比特还可以携带前述时长信息和/或可用状态信息 等。
图6所示为包含BI的子头的一个信息格式示例。在图6中所示的BI子头可包括1个八位组(oct1)。1个八位组可包括8个比特。参考图6可知，在该BI子头内除了携带BI以外，还携带有反馈信息。图6中R字段为预留字段；E为扩展字段，指示该子头是否还有其他内容；T字段为类型字段，指示该子头内是否携带有RAP ID。E字段和T字段都可占用1个比特。反馈信息也可以占用该子头内一个字段。
如此，UE接收到该Msg2不仅能够知晓网络层对自身请求的SIB是否会发送，还会根据BI子头携带的辅助信息，知道何时可以再次发起获取SIB的获取请求，或者，网络侧拒绝发送SIB的原因。该原因包括但不限于：网络侧未配置获取请求所请求SIB携带的配置信息和/或配置有SIB携带的配置信息但是该配置信息指示的发送资源不可用。
在一个实施例中，所述反馈信息由所述BI子头的预留比特携带。
在另一个实施例中，所述反馈信息可与BI子头携带的BI具有对应关系。在这种情况下，BI子头携带的BI不仅指示了退避值，同时还指示了对获取请求的NACK或者ACK。
在一个实施例中，所述S110可包括：接收携带有所述SIB的获取请求的第三消息Msg3。
在一个实施例中，所述SIB的获取请求可以携带在Msg3中。
对应地，S120可包括：将所述反馈信息携带在所述Msg4中下发给UE。
在一个实施例中，所述Msg4包括：媒体访问控制MAC控制单元CE。
一个Msg4可携带有一个或多个MAC CE。MAC CE包括：MAC CE子头(subheader)。一个MAC CE子头可以携带一个LCID值。
在一个实施例中，MAC CE子头包括一个八位组(oct)，而一个oct具有8个比特，这8个比特包括：预留域和LCID域；预留域包括预留比特； LCID域，用于携带LCID值。如图7所示，预留域可包括2个预留比特；LCID域可包括6个比特。如此，LCID域具有64个LCID值。这64个LCID值可如表1：
Figure PCTCN2020130213-appb-000001
Figure PCTCN2020130213-appb-000002
表1
在表1中码点/索引(codepoint/index)为35，即码点或索引为35，是与反馈信息具有对应关系的LCID值的示例。
例如，表1中码点或索引为35的LCID值是与反馈信息中的NACK具有对应关系。
但是网络侧预先配置了很多可以供MAC CE子头携带的LCID值。且网络侧配置的多个LCID值中的一个或多个与反馈信息具有对应关系。例如，多个LCID值中的一个或多个与反馈信息中的NACK或ACK具有对应关系。
总之，MAC CE子头所携带的多个LCID值中至少部分值，与所述反馈信息具有对应关系。
在一个实施例中，一个MAC CE子头一次性携带一个LCID值。能够被携带到MAC CE子头中LCID值的备选值有多个，这多个备选值中有一个或多个与反馈信息具有对应关系。
在这种情况下，Msg4携带的LCID值可能与反馈信息具有对应关系，也可能与反馈信息不具有对应关系。若Msg4携带的LCID值与反馈信息具有对应关系，则UE接收到该Msg4之后，从Msg4中提取的LCID值为与反馈信息具有对应关系的LCID值，则会根据这种LCID值确定出网络侧对自身所发送获取请求的反馈，该反馈信息可为NACK或者ACK。
在一个实施例中，一个所述MAC CE包括：有效负荷(payload)。
其中，所述有效负荷中连续分布的第一部分，与所述反馈信息不具有对应关系；
所述有效负荷中所述第一部分以外的第二部分，与所述反馈信息具有对应关系。
例如，假设有效负荷为48比特，这48个比特可以分为第一部分和第二部分，第一部分用于解决UE之间的竞争冲突，第二部分用于携带反馈信息。可以理解地，第一部分可包括32个比特；第二部分可包括16个比特用于携带反馈信息。在一个实施例中，第一部分可为48个比特中的前32个比特，而第二部分是48个比特中的后16个比特。
再例如，假设有效负荷为48个比特。这48个比特中的第一部分可包括：40个比特；第二部分可为剩余的8个比特。
第一部分对应的比特连续分布，方便后续UE接收到Msg4之后，快速确定自身是否随机接入成功。
在一个些实施例中，所述Msg4的MAC CE的有效负荷具有扩展比特；所述扩展比特，用于携带所述反馈信息。
例如，假设原本MAC CE的有效负荷为48个比特，则添加了扩展比特的MAC CE的有效负荷会超过48个比特。
在本公开实施例中，该Msg4的MAC CE的有效负荷具有一个或多个扩展比特，该扩展比特携带前述反馈信息和/或辅助信息。
在本公开实施例中，MAC CE的有效负荷中原有的比特，可用于解决UE之间竞争冲突，扩展比特指示所述反馈信息，如此MAC CE的有效负荷的比特数就增加了。扩展比特指示的反馈信息包括：ACK/NACK外，还可以包括前述任意一项的辅助信息。
在一些实施例中，所述MAC CE可包括：两类MAC CE，分别是第一类MAC CE和第二类MAC CE。第一类MAC CE和第二类MAC CE的用 途不同。
例如，第一类MAC CE，用于UE之间竞争冲突解决；第二类MAC CE，携带所述反馈信息。
不管是第一类MAC CE还是第二类MAC CE都包括：MAC CE子头。在一些情况下，不管是第一类MAC CE还是第二类MAC CE均除了包括MAC CE子头以外，还可包括：填充部分。
MAC CE子头可以分为保留域和LCID域。在一个实施例中，若第二类MAC CE中，反馈信息仅占用了LCID域的比特，则可认为第二类MAC CE子头携带的是与反馈信息具有对应关系的LCID值，该LCID值可为新增的LCID值或者增强LCID值。新增LCID值(或成为增强LCID值)可如表1中码点或索引为35的LCID值。
若第二类MAC CE携带的反馈信息占用了保留域的比特或者是携带在第二类MAC CE的填充部分中，此时可认为反馈信息对应的比特值，不属于LCID值。当然在一些情况下，若保留域的比特值部分划分到LCID域得到增强后的LCID域，则此时也可以认为第二类MAC CE携带的是与反馈信息具有对应关系的增强LCID值。
MAC CE子头的长度可以是固定的，也可以是不固定的。例如，一个MAC CE子头的固定长度可为8个比特；MAC CE子头包含的比特数可为8个比特数的整数倍。
为了方便同时需要获取第一类MAC CE和第二类MAC CE对Msg4的简便解码，则所述第一类MAC CE和所述第二类MAC CE相邻分布在所述Msg4中。
图7为一个MAC CE子头的示意图。在图7中一个MAC CE子头可包括一个八位组(oct1)。一个MAC CE子头包括：R域和LCID域；R域为保留域，具有一个或多个预留比特。在图7中MAC CE子头的保留域具有 2个保留比特。在图7中MAC CE子头的LCID域具有6个比特，具有64个比特值，即可指示64个LCID值。
图7可以理解为第一类MAC CE子头的一种示例。
图8A和图8B可以理解为第二类MAC CE的示例。
在图8A中展示的第二类MAC CE子头具有的是一个增强逻辑信道标识(enLCID)域。该enLCID域可用于携带反馈信息，或者携带与反馈信息具有对应关系的LCID值。
图8A所示的第二类MAC CE子头的长度是固定的，即为1个八位组，也即8个比特。
图8B中展示的第二类MAC CE的长度是不固定的，即第二类MAC CE的长度是可变的。不固定的MAC CE的比特数通常为8的正整数倍。
在图8B所示的第二类MAC CE中，利用F字段指示当前MAC CE的长度是不固定的。图8B所示的第二类MAC CE的长度由固定长度的1个八位组，增长到2个八位组，且这两个八位组分别是oct1和oct2。
在图8B中enLCID域和L域，可由共同指示反馈信息。或者，L字段用于标识该MAC CE子头内的enLCID域携带的是反馈信息或者与反馈信息具有对应关系的LCID值。
在一个实施例中，包含不同类型的MAC CE子头的MAC CE即为不同类型的MAC CE。此处，不同类型的MAC CE至少包括第一类型MAC CE和第二类型MAC CE。
在一个实施例中，第二类MAC CE紧随其对应的所述一类MAC CE。通过这种第一类MAC CE和第二类MAC CE之间的位置关系，表明当前第二类MAC CE携带的反馈信息是：针对位于其前方的第一类MAC CE所对应UE的。
在一个实施例中，所述S120可包括：
下发携带有所述反馈信息的无线连接控制(Radio Resource Control，RRC)消息。
例如，非连接态的UE通过Msg1或者Msg3发送所述获取请求或者其他方式方式发送获取请求，UE通过随机接入过程中从非连接态切换到连接态之后，就能够接收所述RRC消息。此时，网络侧的基站可以通过RRC消息向UE发送所述反馈信息，若网络侧不预备下发获取请求所请求的SIB，则UE可以根据该RRC消息携带的反馈信息，确定是否继续发送获取请求。
如图9所示，本公开实施例提供一种请求系统消息块的方法，包括：
S210：发送请求SIB的获取请求；
S220：接收针对所述获取请求的反馈信息。
本公开实施例提供的请求系统消息块的方法，可应用于各种请求SIB的UE内。该UE可以为处于非连接态的UE。
在一个实施例中，UE可以通过随机接入过程中的Msg1和/或Msg3发送所述获取请求。
在本公共实施例中，UE发送所述获取请求之后会收到基于该获取请求返回的反馈信息。该反馈信息可以是通过一个或多个比特显性携带的，也可以是通过与其他信息之间的对应关系被隐性携带的。
在本公开实施例中，所述反馈信息可包括：NACK或者ACK。
如此，UE可以根据反馈信息，确定是否继续发送获取请求，或者在所请求SIB的配置资源接收所请求的SIB。通过反馈信息的接收，可以减少不必要的获取请求的发送和接收SIB的不必要等待。
在一些实施例中，所述SIB为按需ondemand形式获取的SIBx，x为等于2或大于2的正整数。
在本公开实施例中，通过获取请求去向网络侧请求的SIB为SIBx。
在一个实施例中，所述SIBx为：携带TRS的配置信息的SIB；和/或， 携带CSI-RS的配置信息的SIB。
在一些实施例中，所述S210可包括：接收否定答复NACK，其中，所述NACK，指示网络侧不下发请求的SIB；或者，接收确定答复ACK，其中，所述ACK，指示网络侧下发请求的SIB。
反馈信息可为NACK或者ACK，若UE接收到的是NACK，说明网络侧不会发送请求的SIB，一方面UE知晓了网络侧不会下发请求SIB，则不必要重复请求，另一方面也不用等待UE下发SIB，减少了UE重复请求SIB或者等待监听SIB所产生的功耗。
若UE接收到ACK，则说明网络侧会下发UE请求的SIB，UE可以直接在请求的SIB的配置资源上接收所请求的SIB即可，不用重复请求，从而也减少了重复请求所产生的功耗。
在一个实施例中，所述反馈信息还包括：
辅助信息，其中，所述辅助信息，至少供用户设备UE确定用于获取所述SIB所需的相关信息。
在一个实施例中，所述辅助信息可为反馈信息为NACK时下发的。例如，辅助信息可用于指示UE再次发送所述获取请求需要间隔时长的时长信息，或者，指示网络侧下发NACK的原因的信息，指示网络侧下发NACK的原因的信息包括但不限于：可用状态信息。
在一个实施例中，所述辅助信息包括：
时长信息，指示所述UE再次发起所述获取请求的间隔时长；和/或，可用状态信息，指示是否有所述获取请求所请求SIB携带的配置信息，或，指示所述获取请求所请求SIB的携带配置信息所指示资源是否可用。
在另一些实施例中，在所述反馈信息为ACK时，所述辅助信息可为：所请求SIB的配置信息，该配置信息可至少指示了所请求SIB的发送资源。如此，UE可以根据该辅助信息携带的SIB的辅助信息，在对应的发送资源 上接收该SIB。
在一个实施例中，所述S210可包括：发送携带有所述获取请求的第一消息Msg1。
第一消息Msg1为随机接入消息中的一条，为4步随机接入过程中的第一条随机接入消息，一般携带有接入前导码的标识(Identification，ID)。
在本公开实施例中，Msg1不仅携带前导码的ID还可以携带所述获取请求。
在一些实施例中，所述S220可包括：发送携带有所述反馈信息的第二消息Msg 2。
在本公开实施例中，Msg2携带有所述获取请求的反馈信息。该反馈信息可为NACK或者ACK。
在一个实施例中，所述Msg2为携带有反馈比特。
Msg2携带有显性指示所述反馈信息的反馈比特，该反馈比特可为Msg2中原本的预留比特，也可以是Msg2中的预留比特。
所述反馈信息，携带在所述Msg2的MAC随机接入响应RAR中。例如，针对由反馈比特显性指示反馈比特，则反馈比特可以携带在MAC RAR中。
携带所述反馈信息的MAC RAR为第二类型MAC RAR；不携带所述反馈信息的MAC RAR为第一类型MAC RAR。
示例性地，携带反馈信息的Msg2携带的MAC RAR为第二类型MAC RAR。
在一个实施例中，按照Msg2是否可以携带反馈信息进行区分，可以分为第一类型Msg2和第二类型Msg2。
例如，不能够携带所述反馈信息的Msg2为第一类型Msg2；能够携带所述反馈信息的Msg2为第二类型Msg2。可以理解地是：所述第一类型 Msg2不携带所述反馈比特，而第二类型Msg2携带所述反馈比特；或者，第一类型Msg2携带第一类型MAC RAR；第二类型Msg2携带第二类型MAC RAR。
第一类型Msg2可作为未携带有获取请求的Msg1的回复信息。第二类型Msg2可作为携带有获取请求的Msg1的回复信息。
在一些实施例中，对应于所述第一类型Msg2的Msg1的通信资源，不同于对应于所述第二类型Msg2的Msg1的通信资源。
由于不同类型Msg2所对应的Msg1的通信资源不同，此时，在S210中，UE可以根据当前待发送的Msg1是否携带有获取请求，在对应的通信资源上发送所述Msg1，以触发网络侧下发对应类型的Msg2。
该对应于第二类型Msg2的Msg1的通信资源的配置方式，可与对应于第一类型Msg2的Msg1的通信资源的配置方式不同。例如，对应于第二类型Msg2的Msg1的通信资源是通过SIB中的非关键扩展进行配置的。该非关键扩展的配置是一种可选配置。
在一个实施例中，所述方法还包括：接收SIB1，其中，所述SIB1中携带有所述第二类型Msg2的Msg1的通信资源的资源信息。
这里的资源信息可为：指示传输对应于第二类型Msg2的Msg1的时频资源和/或波束资源等信息。
在一个实施例中，所述S220可包括：接收携带有与所述反馈信息对应的随机接入前导码RAP标识ID的Msg2。
在一个实施方式中，Msg2不直接携带反馈信息的反馈比特，而是通过通过携带与反馈信息具有对应关系的RAP ID来隐性指示所述反馈信息。
例如，在本公开实施例中，所述RAP ID包括：与反馈信息中NACK具有对应关系的RAP ID、与反馈信息中ACK具有对应关系的RAP ID、和/或与反馈信息不具有对应关系的RAP ID。
在一些实施例中，所述第二类型Msg2还具有类型字段，所述类型字段指示Msg2的类型。
例如，该类型字段可包括一个或多个比特，指示当前Msg2可为第二类型Msg2，以方便UE快速解码所述Msg2。
在一个实施例中，不同所述SIB的反馈信息对应的RAP ID不同；或者，不同所述SIB的反馈信息对应相同的RAP ID。
在一个实施例中，根据RAP ID与SIB的反馈信息的对应关系，及携带有反馈信息的Msg2是否携带有辅助信息，可以分为以下四种情况：
情况1：所述Msg2携带的不同RAP ID对应于不同SIB的反馈信息，且所述Msg2不具有携带有辅助信息的MAC RAR；
或者，
情况1：所述Msg2携带的相同RAP ID对应于不同SIB的反馈信息，且所述Msg2不具有携带有辅助信息的MAC RAR；
或者，
情况1：所述Msg2携带的不同RAP ID对应于不同SIB的反馈信息，且所述Msg2具有携带有辅助信息的MAC RAR；
或者，
情况4：所述Msg2携带的相同RAP ID对应于不同SIB的反馈信息，且所述Msg2具有携带有辅助信息的MAC RAR。
在一个实施例中，所述Msg2还携带有具有所述反馈信息的SIB的信息标识。
该信息标识可以是在一个RAP ID对应于一个SIB的反馈信息时携带，也可以是在一个RAP ID对应于多个SIB的反馈信息时携带，处于减少比特开销的考虑，信息标识可以仅仅在一个RAP ID对应于多个SIB的反馈信息时携带。
在一个实施例中，该信息标识可以由专用的比特显性指示，也可以和其他信息建立对应关系的方式进行隐形指示。
在一个实施例中，在该信息标识是由专用的比特显性指示时，所述信息标识携带在所述Msg2的标识信息域内；所述标识信息域携带有一个或多个与NACK对应的SIB的信息标识；或者，所述标识信息域携带一个或多个与ACK对应的SIB的信息标识。
在另一个实施例中，所述标识信息域包含在所述Msg2的MAC RAR中，一个所述MAC RAR的长度，大于或等于所述标识信息域的长度。
在一个实施例中，若Msg2携带辅助信息，且Msg2中设置有信息标识域，则所述标识信息域还用于携带所述辅助信息；其中，所述辅助信息，至少供用户设备UE确定用于获取所述SIB所需的相关信息。
值得注意的是：Msg2携带的辅助信息，可以携带在信息标识域内，也可以携带在信息标识域外。
在一个实施例中，Msg2具有MAC子PDU；一个Msg2至少有一个MAC子PDU携带有BI子头，该BI子头携带有BI。BI子头中的预留比特可用于携带所述反馈信息。
在一个实施例中，所述Msg2具有退避指示符BI的BI子头；其中，所述BI子头携带所述反馈信息。
在一个实施例中，所述反馈信息由所述BI子头的预留比特携带。
在一些实施例中，所述BI子头还携带有辅助信息；
所述辅助信息，至少供用户设备UE确定用于获取所述SIB所需的相关信息。
在一些实施例中，所述S210可包括：发送携带有所述SIB的获取请求的第三消息Msg3。
在一些实施例中，所述S220可包括：接收携带所述反馈信息的第四消 息Msg4。
在一个实施例中，所述Msg4可包括：一个或多个媒体访问控制MAC控制单元CE。
携带有所述反馈信息的MAC CE可以称之为反馈CE，可区别于解决UE之间竞争的MAC CE。
一个MAC CE至少包括MAC CE子头。在一些情况下，所述MAC CE除了包含MAC CE子头还会包括有效负荷(payload)，所述反馈CE携带的反馈信息，可以携带在MAC CE子头内，也可以是携带在有效负荷内。
在一个实施例中，所述MAC CE包括：MAC CE子头；其中，MAC CE子头所携带的多个LCID值中至少部分值，与所述反馈信息具有对应关系。
在一个实施例中，所述Msg4包括：媒体访问控制MAC控制单元CE；所述MAC CE包括：有效负荷；其中，所述有效负荷中连续分布的第一部分，与所述反馈信息不具有对应关系；所述有效负荷中所述第一部分以外的第二部分，与所述反馈信息具有对应关系。
在一个实施例中，所述Msg4的MAC CE的有效负荷具有扩展比特；所述扩展比特，用于携带所述反馈信息。
在一个实施例中，所述Msg4的MAC CE的有效负荷具有扩展比特；所述扩展比特，用于携带所述反馈信息。
在一些实施例中，MAC CE的有效负荷具有扩展比特，该扩展比特携带有所述反馈信息。例如，所述MAC CE的有效负荷的扩展比特的可以显性指示所述反馈信息，也可以是通过与所述反馈信息具有对应关系的LCID值来隐形指示。
例如，一个MAC CE的有效负荷具有48个比特，该48比特可用于UE之间竞争冲突的解决。例如，该48个比特用于携带被响应的UE在Msg3中携带的上行链路(Uplink，UL)公共控制信道服务数据单元(Common  Control Channel Service Data Unit，CCCH SDU)前48比特。不同UE发送的Msg3携带的UL CCCH SDU的前48比特不同，因此通过MAC CE的前48个比特复制随机接入成功的UE的UL CCCH SDU的前48个比特的比特值。各UE接收到之后通过MAC CE的前48个比特与自身发送的Msg3中携带的UL CCCH SDU的前48比特的比特，若比对一致，则认为自身随机接入成功；否则可认为自身随机接入失败。
在本公开实施例中，MAC CE中包含用于UE之间净重冲突的第一类比特之外，还有第一类比特之外的第二类比特。此处的第二类比特可以用于携带所述反馈信息，或者携带与所述反馈信息具有对应关系的LCID值。若第一类比特的个数为48，则包含第二类比特的MAC CE则必然超过48个比特。
在一个实施例中，所述Msg4包含：
第一类MAC CE，用于UE之间竞争冲突解决；
第二类MAC CE，携带所述反馈信息。
不管是第一类MAC CE还是第二类MAC CE都包括：MAC CE子头。在一些情况下，不管是第一类MAC CE还是第二类MAC CE均除了包括MAC CE子头以外，还可包括：填充部分。
MAC CE子头可以分为保留域和LCID域。在一个实施例中，若第二类MAC CE中，反馈信息仅占用了LCID域的比特，则可认为第二类MAC CE
子头携带的是与反馈信息具有对应关系的LCID值，该LCID值可为新增的LCID值或者增强LCID值。新增LCID值(或成为增强LCID值)可如表1中码点或索引为35的LCID值。
若第二类MAC CE携带的反馈信息占用了保留域的比特或者是携带在第二类MAC CE的填充部分中，此时可认为反馈信息对应的比特值，不属于LCID值。当然在一些情况下，若保留域的比特值部分划分到LCID域得 到增强后的LCID域，则此时也可以认为第二类MAC CE携带的是与反馈信息具有对应关系的增强LCID值。
在一个实施例中，所述第一类MAC CE和所述第二类MAC CE相邻分布在所述Msg4中。
在另一个实施例中，所述第一类MAC CE和所述第二类MAC CE在Msg4中分布在不同的位置处。在一个实施例中，所述S220可包括：接收携带有所述反馈信息的无线连接控制RRC消息。
在一个实施例中，所述UE还可以在RRC消息中接收到所述反馈信息。
携带所述反馈信息的RRC消息，可为一种专门设计用于携带反馈信息的专用RRC消息。例如，该专有RRC消息可为RRC系统消息响应(RRCSystemInfoResponse)。
在还有一些实施例中，携带所述反馈信息的RRC消息可为复用了相关技术中携带其他内容的RRC消息。举例来说，若当前UE处于非连接态，则基站可以通过RRC消息中的RRC连接建立消息来携带所述反馈信息。UE检测到时携带有反馈信息的RRC连接建立消息，可能会与基站建立RRC连接，可以不建立RRC连接而是仅为了获取到与自身发送的获取请求对应的反馈信息。
在一些实施例中，如图10所示，所述方法还包括：
S230：响应于接收到未携带时长信息的所述NACK，获取再次发起所述获取请求的时长信息；其中，所述时长信息，指示所述UE再次发起所述获取请求的间隔时长。若UE接收到反馈信息是NACK，此时表示网络侧当前不会下发请求SIB。随着网络负载和/或无线环境的变化，过一段时间后基站可能可以下发SIB或者为配置了UE所请求SIB所携带的配置信息。有鉴于此，UE可能会重复发送获取请求，但是间隔多长时间再次发送获取请求，若获取请求的发送过于频繁，一方面会导致无线环境的进一步恶化， 另一方面会导致UE的功耗。若获取请求的发送过于稀疏，会使得UE请求到对应的SIB的延时增加。
在一个实施例中，如图10所示，所述方法还包括：
S240：在确定所述时长信息之后，会在间隔所述时长信息至少的时长之后，再次发起所述获取请求。
在一些实施例中，所述方法还包括：
响应接收到携带有时长信息的NACK，在间隔根据所述时长信息指示的时长之后，再次发起所述获取请求。
在一个实施例中，所述获取再次发起所述获取请求的时间信息，包括以下至少之一：
发送获取所述时长信息的请求信息；
根据所述网络配置确定所述时长信息；
根据预先约定确定所述时长信息；
根据所述UE对所述NACK的应对策略，确定所述时长信息。
在一个实施例中，UE可以向网络侧发送获取所述时长信息的请求信息，网络侧接收到请求信息之后，可以广播消息、组播消息或者单播消息向UE发送所述时长信息。
在另一个实施例中，网络侧可以预先配置出所述时长信息。
在另一个实施例中，在UE多次接入网络的过程中，可以预先约定所述时长信息，一旦所述时长信息预定之后，后续UE可以一次或多次使用该预先约定的时长信息，确定UE再次发起对获取同一个SIB的获取请求。
在另一些实施例中，UE内部存储有对接收到NACK的应对策略，根据该应对策略确定所述时长信息。
例如，不同类型的UE对接收到NACK的应对策略不同，低功耗的互联网设备，根据应对策略确定的时长信息指示的间隔时长，可大于手机或 者车载终端等非功耗的UE根据应对策略确定的时长信息所指示的间隔时长。
再例如，不同SIB的NACK的应对策略所映射的时长信息所指示的间隔时长不同。UE接收到请求SIBy1的获取请求的NACK时，根据应对策略确定的时长信息指示的间隔时长为第一时长；UE接收到请求SIBy2的获取请求的NACK时，根据应对策略确定的时长信息指示的时长间隔可为第二时长。第一时长不同于第二时长。其中，y1和y2均为大于2的正整数，且是大于2的不同正整数。
具体的第一时长和第二时长的大小，可以根据SIBy1和SIBy2的紧急程度或者优先级来决定。例如，携带地震或者海啸通知的SIB的紧急程度可能就比携带CSI-RS的配置信息的SIB的紧急程度高，故携带地震或者海啸通知的SIB对应的间隔时长，可能就小于携带CSI-RS的配置信息的SIB的间隔时长。
当然以上仅是举例，具体的实现方式有很多种，不局限于上述任意一种。
如图11所示，本公开实施例提供一种请求系统消息块的装置，其中，包括：
第一接收模块110，被配置为接收请求系统消息块SIB的获取请求；
第一发送模块120，被配置为下发针对所述获取请求的反馈信息。
在一个实施例中，所述第一接收模块110和第一发送模块120可均为程序模块，所述程序模块被处理器执行之后，能够实现所述SIB的获取请求接收及所述反馈信息的下发。
在另一个实施例中，所述第一接收模块110和所述第一发送模块120可为软硬结合模块；所述软硬结合模块包括但不限于：可编程阵列；所述可编程这列包括但不限于：现场可编程阵列或者复杂可编程阵列。
在还有一个实施例中，所述第一接收模块110和所述第一发送模块120可为纯硬件模块；所述纯硬件模块包括但不限于：专用集成电路。
在一个实施例中，所述SIB为按需ondemand形式获取的SIBx，x为等于2或大于2的正整数。
在一个实施例中，所述SIBx为：
携带跟踪参考信号TRS的配置信息的SIB；
和/或，
携带信道状态指示CSI-参考信号RS的配置信息的SIB。
在一个实施例中，所述第一发送模块120，被配置为下发否定答复NACK，其中，所述NACK，指示网络侧不下发请求的SIB；或者，下发确定答复ACK，其中，所述ACK，指示网络侧下发请求的SIB。
在一个实施例中，所述第一发送模块120，被配置为执行以下至少之一：
响应于未配置请求的SIB携带的配置信息所指示的资源，下发所述NACK；
响应于配置有请求的SIB携带的配置信息所指示资源且所述配置信息所指示资源的不可用，下发所述NACK；
响应于请求的SIB的调度信息在最小剩余系统信息RMSI中，下发所述NACK。
在一个实施例中，所述反馈信息还包括：
辅助信息，其中，所述辅助信息，至少供用户设备UE确定用于获取所述SIB所需的相关信息。
即在这种情况下，反馈信息不仅包括反馈指示，还包括辅助信息。此处的反馈指示即为前述NACK或ACK。辅助信息主要是用于辅助UE获取所请求的SIB或者停止发送获取请求。
在一个实施例中，所述辅助信息包括以下至少之一：
时长信息，指示所述UE再次发起所述获取请求的间隔时长；
可用状态信息，指示是否有所述获取请求所请求SIB携带的配置信息，或指示所述获取请求所请求SIB的携带配置信息所指示资源是否可用。
在一个实施例中，所述第一接收模块110，被配置为接收携带有所述获取请求的第一消息Msg1。
在一个实施例中，所述第一发送模块120，被配置为下发携带有所述反馈信息的第二消息Msg 2。
在一个实施例中，所述反馈信息，携带在所述Msg2的MAC随机接入响应RAR中。
在一个实施例中，携带所述反馈信息的MAC RAR为第二类型MAC RAR；不携带所述反馈信息的MAC RAR为第一类型MAC RAR。
在一个实施例中，不能够携带所述反馈信息的Msg2为第一类型Msg2；
能够携带所述反馈信息的Msg2为第二类型Msg2。
在一个实施例中，对应于所述第一类型Msg2的Msg1的通信资源，不同于对应于所述第二类型Msg2的Msg1通信资源。
在一个实施例中，所述第一发送模块120，还被配置为下发SIB1，其中，所述SIB1中携带有对应所述第二类型Msg2的Msg1的通信资源的资源信息。
在一个实施例中，所述第一发送模块120，被配置为下发携带有与所述反馈信息对应的随机接入前导码RAP标识ID的Msg2。
在一个实施例中，携带与所述反馈信息对应的RAP ID的Msg2为第二类型Msg2，不携带与所述反馈信息对应的RAP ID的Msg为第一类型Msg2。
在一个实施例中，所述Msg2携带的不同RAP ID对应于不同SIB的反馈信息，且所述Msg2不具有携带有辅助信息的MAC RAR；
或者，
所述Msg2携带的不同RAP ID对应于不同SIB的反馈信息，且所述Msg2具有携带有辅助信息的MAC RAR；
不同所述SIB的反馈信息对应的RAP ID不同，
或者，
不同所述SIB的反馈信息对应相同的RAP ID，且所述Msg2携带有所述反馈信息所指示的SIB的标识信息。
在一个实施例中，所述信息标识，携带在所述Msg2的标识信息域内；
所述标识信息域携带有一个或多个与NACK对应的SIB的信息标识；
或者，
所述标识信息域携带一个或多个与ACK对应的SIB的信息标识。
在一个实施例中，所述标识信息域包含在所述Msg2的MAC RAR中，
一个所述MAC RAR的长度，大于或等于所述标识信息域的长度。
在一个实施例中，所述标识信息域还用于携带所述辅助信息；其中，所述辅助信息，至少供用户设备UE确定用于获取所述SIB所需的相关信息。
在一个实施例中，所述Msg2具有退避指示符BI的BI子头；其中，所述BI子头携带所述反馈信息。
在一个实施例中，所述反馈信息由所述BI子头的预留比特携带。在这种实施例中，相当于BI子头中的部分比特指示BI，部分比特指示反馈信息。
在一个实施例中，所述BI子头还携带有辅助信息；
所述辅助信息，至少供用户设备UE确定用于获取所述SIB所需的相关信息。
在一个实施例中，所述第一接收模块110，还被配置为接收携带有所述SIB的获取请求的第三消息Msg3。
在一个实施例中，所述第一发送模块120，还被配置为下发携带所述反 馈信息的第四消息Msg4。
在一个实施例中，所述Msg4包括：媒体访问控制MAC控制单元CE；所述MAC CE包括：MAC CE子头；
其中，MAC CE子头所携带的多个LCID值中至少部分值，与所述反馈信息具有对应关系。
在一个实施例中，所述Msg4包括：媒体访问控制MAC控制单元CE；所述MAC CE包括：有效负荷；
还包括
其中，所述有效负荷中连续分布的第一部分，与所述反馈信息不具有对应关系；
所述有效负荷中所述第一部分以外的第二部分，与所述反馈信息具有对应关系。
在一个实施例中，所述Msg4的MAC CE的有效负荷具有扩展比特；所述扩展比特，用于携带所述反馈信息。
在一个实施例中，所述Msg4包含：
第一类MAC CE，用于UE之间竞争冲突解决；
第二类MAC CE，携带所述反馈信息。
在一个实施例中，所述第一类MAC CE和所述第二类MAC CE相邻分布在所述Msg4中。
在另一个实施例中，所述第一发送模块120，被配置为下发携带有所述反馈信息的无线连接控制RRC消息。
如图12所示，本公开实施例提供一种请求系统消息块的装置，其中，包括：
第二发送模块210，被配置为发送请求系统消息块SIB的获取请求；
第二接收模块220，被配置为接收针对所述获取请求的反馈信息。
在一个实施例中，所述第二发送模块210和第二接收模块220可均为程序模块，所述程序模块被处理器执行之后，能够实所述SIB的获取请求的发送和所述反馈信息的接收。
在另一个实施例中，所述第二发送模块210和第二接收模块220可为软硬结合模块；所述软硬结合模块包括但不限于：可编程阵列；所述可编程这列包括但不限于：现场可编程阵列或者复杂可编程阵列。
在还有一个实施例中，所述第二发送模块210和第二接收模块220可为纯硬件模块；所述纯硬件模块包括但不限于：专用集成电路。
在一个实施例中，所述SIB为按需ondemand形式获取的SIBx，x为等于2或大于2的正整数。
在一个实施例中，所述SIBx为：
携带跟踪参考信号TRS的配置信息的SIB；
和/或，
携带信道状态指示CSI-参考信号RS的配置信息的SIB。
在一个实施例中，所述第二接收模块220，被配置为接收否定答复NACK，其中，所述NACK，指示网络侧不下发请求的SIB；或者，接收确定答复ACK，其中，所述ACK，指示网络侧下发请求的SIB。
在一个实施例中，所述反馈信息还包括：
辅助信息，其中，所述辅助信息，至少供用户设备UE确定用于获取所述SIB所需的相关信息。
在一个实施例中，所述辅助信息包括以下至少之一：
时长信息，指示所述UE再次发起所述获取请求的间隔时长；
可用状态信息，指示是否有所述获取请求所请求SIB携带的配置信息，或，指示所述获取请求所请求SIB的携带配置信息所指示资源是否可用。
在一个实施例中，所述第二发送模块210，被配置为发送携带有所述获 取请求的第一消息Msg1。
在一个实施例中，所述第二接收模块220，被配置为接收携带有所述反馈信息的第二消息Msg 2。
在一个实施例中，所述反馈信息，携带在所述Msg2的MAC随机接入响应RAR中。
在一个实施例中，携带所述反馈信息的MAC RAR为第二类型MAC RAR；不携带所述反馈信息的MAC RAR为第一类型MAC RAR。
在一个实施例中，不能够携带所述反馈信息的Msg2为第一类型Msg2；能够携带所述反馈信息的Msg2为第二类型Msg2。
在一个实施例中，对应于所述第一类型Msg2的Msg1的通信资源，不同于对应于所述第二类型Msg2的Msg1的通信资源。
在一个实施例中，所述第二接收模块220还被配置为接收SIB1，其中，所述SIB1中携带有所述第二类型Msg2的Msg1的通信资源的资源信息。
在一个实施例中，所述第二接收模块220，还被配置为接收携带有与所述反馈信息对应的随机接入前导码RAP标识ID的Msg2。
在一个实施例中，不同所述SIB的反馈信息对应的RAP ID不同；或者，不同所述SIB的反馈信息对应相同的RAP ID，且所述Msg2携带有所述反馈信息所指示的SIB的标识信息。
在一个实施例中，所述信息标识，携带在所述Msg2的标识信息域内；
所述标识信息域携带有一个或多个与NACK对应的SIB的信息标识；
或者，
所述标识信息域携带一个或多个与ACK对应的SIB的信息标识。
在一个实施例中，所述标识信息域包含在所述Msg2的MAC RAR中，
一个所述MAC RAR的长度，大于或等于所述标识信息域的长度。
在一个实施例中，所述标识信息域还用于携带所述辅助信息；其中， 所述辅助信息，至少供用户设备UE确定用于获取所述SIB所需的相关信息。
在一个实施例中，所述Msg2具有退避指示符BI的BI子头；其中，所述BI子头携带所述反馈信息。
在一个实施例中，，所述反馈信息由所述BI子头的预留比特携带。
在一个实施例中，所述BI子头还携带有辅助信息；
所述辅助信息，至少供用户设备UE确定用于获取所述SIB所需的相关信息。
在一个实施例中，所述第二发送模块210，被配置为发送携带有所述SIB的获取请求的第三消息Msg3。
在一个实施例中，所述第二接收模块220，被配置为接收携带所述反馈信息的第四消息Msg4。
在一个实施例中，所述Msg4包括：媒体访问控制MAC控制单元CE；所述MAC CE包括：MAC CE子头；
其中，MAC CE子头所携带的多个LCID值中至少部分值，与所述反馈信息具有对应关系。
在一个实施例中，所述Msg4包括：媒体访问控制MAC控制单元CE；所述MAC CE包括：有效负荷；其中，所述有效负荷中连续分布的第一部分，与所述反馈信息不具有对应关系；
所述有效负荷中所述第一部分以外的第二部分，与所述反馈信息具有对应关系。
在一个实施例中，所述Msg4的MAC CE的有效负荷具有扩展比特；所述扩展比特，用于携带所述反馈信息。
在一个实施例中，所述Msg4包含：
第一类MAC CE，用于UE之间竞争冲突解决；
第二类MAC CE，携带所述反馈信息。
在一个实施例中，所述第一类MAC CE和所述第二类MAC CE相邻分布在所述Msg4中。
在一个实施例中，所述接收针对所述获取请求的反馈信息包括：
接收携带有所述反馈信息的无线连接控制RRC消息。
在一个实施例中，所述装置还包括：
获取模块，被配置为响应于接收到未携带时长信息的所述NACK，获取再次发起所述获取请求的时长信息；其中，所述时长信息，指示所述UE再次发起所述获取请求的间隔时长。
在一个实施例中，所述获取模块，执行以下至少之一：
发送获取所述时长信息的请求信息；
根据所述网络配置确定所述时长信息；
根据预先约定确定所述时长信息；
根据所述UE对所述NACK的应对策略，确定所述时长信息。
系统消息的获取方式为广播获取和按需(ondemand)形式获取。对于前者，UE直接在系统消息窗口中读取系统消息即可，而对于ondemand形式的系统消息，则最小剩余系统消息(Remained Minimum System Information，RMSI)中有个是否广播的指示比特(bit)表示该系统消息为是否在广播(Broadcasting/notBroadcasting)。对于已经在广播的系统消息，则用户设备(User Equipment，UE)直接在系统消息接收窗口中直接读取对应的系统消息即可，而对于没有在广播的系统消息，则UE需要通过Msg1或者Msg3进行请求，在UE得到网络的确认(Acknowledgement character，ACK)ack之后，此时会认为基站会广播该系统消息，则会在系统消息接收窗口中直接读取对应的系统消息即可。
跟踪参考信号(Tracking Reference Signal，TRS)/信道参考信号(Channel Reference Singal，CRS)的配置信息，并非需要在小区中一直进行广播，比 如若网络中没有空闲态的UE或者空闲态的UE不支持使用空闲态的TRS/CRS的特性，则广播该信息可以认为是资源的浪费。因此最好的方式是用UE进行ondemand请求的获取。此处的ondemand请求为前述获取请求的一种。
ondemand请求指示待获取的系统消息调度信息是事先在RMSI中广播的，都在UE发起按需(ondemand)请求之后获取该SI时，通常会认为该SI是一直都是会请求成功的。因此ondemand请求机制都默认是得到网络的肯定答复。但是，若基站当前可能没有给空闲态的UE使用的TRS/CRS的配置，此时，UE去请求TRS/CRS的配置是极有可能失败的，是会存在网络侧的否定答复的。
有鉴于此，在本公开实施例提供的方案可如下：基站对于特定SI的请求，提供请求的反馈信息，该反馈信息可至少包括：指示不能够提供所请求系统消息的否定答复(NACK)。
作为一种实施例，特定的系统消息(System Imformaiton，SI)为配置为ondemand形式获取的SI-x。此处的x可为等于或大于2的正整数。该SI即为前述的SIB。
作为一种实施例，特定SI-x为承载特定参考信号的配置信息，比如非连接态UE的使用的TRS/CRS。此处的非连接态的UE包括：空闲态的UE和/或非激活态的UE。
基站对于特定SI的获取请求，提供否定答复(NACK)；此时UE理解为网络侧不希望提供有效配置。
作为一种实施例，UE去请求，但是网络没有可用的TRS/CRS的发送资源，因此回复NACK。此处的TRS/CRS的发送资源可为发送TRS/CRS的时频资源。
作为一种实施例，UE通过获取请求去请求一个或多个SIB，但是网络 有TRS/CRS资源配置，但是不可用，因此网络侧回复NACK。
若特定SI的调度信息已在RMSI中发送时，UE发起对特定SI的请求；基站对于特定SI的请求，提供否定答复(NACK)。Ondemand请求的NACK回复中还可以携带时长信息等辅助信息。作为一种实施例，Ondemand请求的NACK回复中可以携带时长信息为T；此时UE理解为网络不希望提供有效的TRS/CRS传输的时长，此时UE可以在该时长信息指示的时长范围内不用再次请求SI。
对于Msg1请求方式：Msg2中需要修改现有协议，增加对NACK的指示。
方式一：增强随机接入响应的媒体访问控制净负荷(MAC payload for Random Access Response)，用于携带基站返回的NACK和/或时长信息等信息。
以下提供几种能够实现的方式：
1)增强随机接入响应的媒体访问控制的控制单元的有效负荷(MAC payload for Random Access Response)。此处的有效负荷，也可以称之为净负荷。例如，在增强随机接入响应的媒体访问控制净负荷引入MAC payload for Random Access Response type2类型。而原有的MAC payload for Random Access Response为type1类型；其中MAC RAR type2用于携带基站返回ACK或NACK和/或时长信息/以及TRS/CRS的更进一步可用信息。
2)版本1的UE在请求系统消息时，仅会收到RAP ID only的MAC CE；而新版本(即版本2)的UE会收到RAP ID and MAC RAR type2的MAC CE。UE在收到和自己发送的RAP ID匹配之后，将会进一步确定Msg2，确定网络侧对自身SI的获取请求的反馈信息，例如，该反馈信息可为肯定或者否定答复。
3)为做到后向兼容性，保证版本1的UE对MAC payload for Random  Access Response type2类型的错误解码，为版本2的UE在Msg1请求的资源对于版本1的UE是不可见的。例如，一种实施例为在SIB1中进行非关键扩展配置。该非关键扩展配置可为：针对系统消息的请求的配置(SI-RequestConfig)，示例性举例可如下：
si-RequestConfigSUL-v17xy SI-RequestConfig OPTIONAL,--Cond SUL-MSG-1
si-RequestConfigSUL-v17xy SI-RequestConfig OPTIONAL,--Cond SUL-MSG-1
当然上述仅是对单独配置类型2的Msg1和类型2的Msg2的资源的一种示例，具体实现方式有很多种，不局限于上述任意一种。此处类型2的Msg1即为前述对应于第二类型Msg2的Msg1。此处的类型2的Msg2就是前述的第二类型Msg2。
方式二：预留RAP ID用于特定SI请求的否定答复。例如，预留的RAP ID可为与SI请求的反馈信息建立有对应关系的RAP ID。
情况1：网络预留RAP ID用于特定SI请求的否定答复，当UE收到网络预留RAP ID，则隐含表达了网络的NACK答复；此时UE收到后，将不继续进行尝试直到达到Msg1的最大重传次数。用该方式UE可以更加省电。
情况2：网络预留RAP ID用于特定SI请求的肯定和/或否定答复。以下以NACK举例。当UE收到网络预留RAP ID，则隐含表达了网络的NACK答复；UE还可以进一步check MAC RAR type2，其中MAC RAR type2用于携带基站返回的NACK和/或时长信息/以及TRS/CRS的更进一步可用信息；此时，网络预留RAP ID对应的RAR则为MAC RAR type2。
情况3：网络预留NACK RAP ID用于特定SI-i请求SI RAP ID-i的否定答复。当UE收到网络预留的NACK RAP ID和SI RAP ID-i的时候，UE认为接收到了对于特定SI-i请求SI RAP ID-i的NACK答复。
此处情况1至情况3中网络预留RAP ID均为前述与反馈信息对应的RAP ID。
在一个实施例中，该携带该SI RAP ID-i的信息域(如，MAC RAR Type-2)的长度与MAC RAR的长度相同。如此，可以更好的直接将SI RAP ID-i直接包含在一个MAC RAR中。
可以理解地，该携带该SI RAP ID-i的信息域可以携带多个SI RAP ID-i，用于答复多个特定SI-i请求SI RAP ID-i的否定答复。此处的否定答复即为前述的获取请求的NACK。
可以理解地，该携带该SI RAP ID-2的信息域还可以携带时长信息/以及指示TRS/CRS的是否可用的可用状态信息。
方式三：增强现有的BI子头的内容，作为对于ondemand请求的NACK回复，即利用其预留的一个预留比特用于携带BI之外的更多信息，比如；可以用预留预留比特来指明网络是是网络没有可用的TRS/CRS资源还是网络有可用的TRS/CRS资源，但是当前不可用。此处的TRS/CRS资源为发送TRS/CRS的通信资源。
对于版本1的UE，若收到网络的NACK回复，则需要继续用BI发起下次请求直到达到Msg1的最大传输次数，而新的用户则可以得到TRS/CRS的更多信息。
对于Msg3方式：Msg4中需要修改现有协议，增加对ACK和/或NACK的指示。以下以NACK举例：
方式一：增强现有的冲突解决MAC CE的内容，作为对于ondemand请求的NACK回复。
一种实现方式是：增加一个新的LCID值，该新增的LCID值可为增强的UE竞争解决标识(Contention Resolution Identity)。该新增的LCID值可以携带在一种新的MAC CE中。
对于该种新的MAC CE的有效负荷可以不同于用于UE之间冲突解决的MAC CE。
用于UE之间冲突解决的MAC CE的有效负荷是用Msg3中携带的UL CCCH SDU的前48比特作为竞争冲突的标识。
在用于UE之间冲突解决的MAC CE的基础上进行改进，则在信的MAC CE可以使用更少比特，比如利用前32比特作为竞争冲突的标识，其余比特用于携带NACK，和/或，同步指示时长信息和/或网络没有可用的TRS/CRS资源还是网络有可用的TRS/CRS资源或但是当前不可用。
对于版本1的用户使用原来的LCID值，对于新增加的LCID值将无法识别。而对于新版本的UE将获取新的LCID值。
新增LCID值之后的LCID值和码点/索引之间的对应关系，可以参见前述表1，此处就不再重复了。
方式二：
扩展相关技术中，用于解决UE竞争冲突ID(UE Contention Resolution Identity)的MAC CE的比特位数，用于携带NACK。
对于版本1的UE将仅获取前48比特进行冲突解决；对于版本2的UE需要先检查前48比特得到冲突解决之后，再获取后续的反馈信息，该反馈信息包括但不限于：NACK和/或ACK。
方式三：
增加新的LCID值，新增的LCID值携带在MAC CE中，携带该LCID值的MAC CE可以称之为反馈CE。该反馈CE可包括：携带NACK的NACK CE和/或携带ACK的ACK CE。
UE若UE之间冲突解决之后还收到了NACK CE，则意味着UE发送的获取请求得到NACK的回应。若UE基于UE之间冲突解决的MAC CE解决冲突之后，还收到ACK CE，则意味着获取请求得到了网络侧ACK回应。 该反馈CE的位置为紧随UE Contention Resolution Identity MAC CE之后，用于隐含的标识该反馈CE关联的UE Contention Resolution Identity MAC CE。例如，该NACK CE的位置为紧随UE Contention Resolution Identity MAC CE之后，用于隐含的标识该NACK CE关联的UE Contention Resolution Identity MAC CE。
NACK CE的长度可以为两种类型，分别是固定长度和可变长度；固定长度的NACK CE的子头可以参见图8A所示，可变长度的NACK CE的子头可以参见8B所示。
方式四：
增强RRC消息；即增加新的RRC消息(RRCSystemInfoResponse)，用于携带反馈信息。该反馈信息包括：NACK和/或ACK。其中，反馈信息为NACK时，则该RRC消息还可包括：辅助信息。该辅助信息包含用于携带基站返回的ACK，NACK和/或时长信息/以及TRS/CRS的更进一步可用信息。
在一个实施例中，若Ondemand请求的NACK回复中没有携带时长信息；则UE何时再次请求取决于网络配置的时间间隔。
作为一种实施例，该时长间隔可以基于网络配置或者预先约定；在一个实施例中，若Ondemand请求的NACK回复中没有携带时长信息；则UE何时再次请求取决于UE实现。
本公开实施例提供一种通信设备，包括：
用于存储处理器可执行指令的存储器；
处理器，分别存储器连接；
其中，处理器被配置为执行前述任意技术方案提供的请求系统消息块方法。
处理器可包括各种类型的存储介质，该存储介质为非临时性计算机存 储介质，在通信设备掉电之后能够继续记忆存储其上的信息。
这里，所述通信设备包括基站或UE。
所述处理器可以通过总线等与存储器连接，用于读取存储器上存储的可执行程序，例如，如图2、图3、图9和/或图10所示的方法的至少其中之一。
图13是根据一示例性实施例示出的一种UE(UE)800的框图。例如，UE800可以是移动电话，计算机，数字广播用户设备，消息收发设备，游戏控制台，平板设备，医疗设备，健身设备，个人数字助理等。
参照图13，UE800可以包括以下一个或多个组件：处理组件802，存储器804，电源组件806，多媒体组件808，音频组件810，输入/输出(I/O)的接口812，传感器组件814，以及通信组件816。
处理组件802通常控制UE800的整体操作，诸如与显示，电话呼叫，数据通信，相机操作和记录操作相关联的操作。处理组件802可以包括一个或多个处理器820来执行指令，以完成上述的方法的全部或部分步骤。此外，处理组件802可以包括一个或多个模块，便于处理组件802和其他组件之间的交互。例如，处理组件802可以包括多媒体模块，以方便多媒体组件808和处理组件802之间的交互。
存储器804被配置为存储各种类型的数据以支持在UE800的操作。这些数据的示例包括用于在UE800上操作的任何应用程序或方法的指令，联系人数据，电话簿数据，消息，图片，视频等。存储器804可以由任何类型的易失性或非易失性存储设备或者它们的组合实现，如静态随机存取存储器(SRAM)，电可擦除可编程只读存储器(EEPROM)，可擦除可编程只读存储器(EPROM)，可编程只读存储器(PROM)，只读存储器(ROM)，磁存储器，快闪存储器，磁盘或光盘。
电源组件806为UE800的各种组件提供电力。电源组件806可以包括 电源管理系统，一个或多个电源，及其他与为UE800生成、管理和分配电力相关联的组件。
多媒体组件808包括在所述UE800和用户之间的提供一个输出接口的屏幕。在一些实施例中，屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。所述触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与所述触摸或滑动操作相关的持续时间和压力。在一些实施例中，多媒体组件808包括一个前置摄像头和/或后置摄像头。当UE800处于操作模式，如拍摄模式或视频模式时，前置摄像头和/或后置摄像头可以接收外部的多媒体数据。每个前置摄像头和后置摄像头可以是一个固定的光学透镜系统或具有焦距和光学变焦能力。
音频组件810被配置为输出和/或输入音频信号。例如，音频组件810包括一个麦克风(MIC)，当UE800处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器804或经由通信组件816发送。在一些实施例中，音频组件810还包括一个扬声器，用于输出音频信号。
I/O接口812为处理组件802和外围接口模块之间提供接口，上述外围接口模块可以是键盘，点击轮，按钮等。这些按钮可包括但不限于：主页按钮、音量按钮、启动按钮和锁定按钮。
传感器组件814包括一个或多个传感器，用于为UE800提供各个方面的状态评估。例如，传感器组件814可以检测到设备800的打开/关闭状态，组件的相对定位，例如所述组件为UE800的显示器和小键盘，传感器组件814还可以检测UE800或UE800一个组件的位置改变，用户与UE800接触的存在或不存在，UE800方位或加速/减速和UE800的温度变化。传感器组 件814可以包括接近传感器，被配置用来在没有任何的物理接触时检测附近物体的存在。传感器组件814还可以包括光传感器，如CMOS或CCD图像传感器，用于在成像应用中使用。在一些实施例中，该传感器组件814还可以包括加速度传感器，陀螺仪传感器，磁传感器，压力传感器或温度传感器。
通信组件816被配置为便于UE800和其他设备之间有线或无线方式的通信。UE800可以接入基于通信标准的无线网络，如WiFi，2G或3G，或它们的组合。在一个示例性实施例中，通信组件816经由广播信道接收来自外部广播管理系统的广播信号或广播相关信息。在一个示例性实施例中，所述通信组件816还包括近场通信(NFC)模块，以促进短程通信。例如，在NFC模块可基于射频识别(RFID)技术，红外数据协会(IrDA)技术，超宽带(UWB)技术，蓝牙(BT)技术和其他技术来实现。
在示例性实施例中，UE800可以被一个或多个应用专用集成电路(ASIC)、数字信号处理器(DSP)、数字信号处理设备(DSPD)、可编程逻辑器件(PLD)、现场可编程门阵列(FPGA)、控制器、微控制器、微处理器或其他电子元件实现，用于执行上述方法。
在示例性实施例中，还提供了一种包括指令的非临时性计算机可读存储介质，例如包括指令的存储器804，上述指令可由UE800的处理器820执行以完成上述方法。例如，所述非临时性计算机可读存储介质可以是ROM、随机存取存储器(RAM)、CD-ROM、磁带、软盘和光数据存储设备等。
如图14所示，本公开一实施例示出一种基站的结构。例如，基站900可以被提供为一网络侧设备。参照图14，基站900包括处理组件922，其进一步包括一个或多个处理器，以及由存储器932所代表的存储器资源，用于存储可由处理组件922的执行的指令，例如应用程序。存储器932中 存储的应用程序可以包括一个或一个以上的每一个对应于一组指令的模块。此外，处理组件922被配置为执行指令，以执行上述方法前述应用在所述基站的任意方法，例如，如图2、图3、图9和/或图10所示方法。
基站900还可以包括一个电源组件926被配置为执行基站900的电源管理，一个有线或无线网络接口950被配置为将基站900连接到网络，和一个输入输出(I/O)接口958。基站900可以操作基于存储在存储器932的操作系统，例如Windows Server TM，Mac OS XTM，UnixTM，LinuxTM，FreeBSDTM或类似。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本发明的其它实施方案。本公开旨在涵盖本发明的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本发明的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本发明的真正范围和精神由下面的权利要求指出。
应当理解的是，本发明并不局限于上面已经描述并在附图中示出的精确结构，并且可以在不脱离其范围进行各种修改和改变。本发明的范围仅由所附的权利要求来限制。

Claims (66)

  1. 一种请求系统消息块的方法，应用于网络设备，包括：
    接收请求系统消息块SIB的获取请求；
    下发针对所述获取请求的反馈信息。
  2. 根据权利要求1所述的方法，其中，所述SIB为按需ondemand形式获取的SIBx，x为等于2或大于2的正整数。
  3. 根据权利要求2所述的方法，其中，所述SIBx为：
    携带跟踪参考信号TRS的配置信息的SIB；
    和/或，
    携带信道状态信息参考信号CSI-RS的配置信息的SIB。
  4. 根据权利要求1所述的方法，其中，所述下发针对所述获取请求的反馈信息，包括：
    下发否定答复NACK，其中，所述NACK，指示网络侧不下发请求的SIB；
    或者，
    下发肯定答复ACK，其中，所述ACK，指示网络侧下发请求的SIB。
  5. 根据权利要求4所述的方法，其中，所述下发否定答复NACK，包括以下中的至少一项：
    响应于未配置请求的SIB携带的配置信息所指示的资源，下发所述NACK；
    响应于配置有请求的SIB携带的配置信息所指示资源且所述配置信息所指示资源的不可用，下发所述NACK；
    响应于请求的SIB的调度信息在最小剩余系统信息RMSI中，下发所述NACK。
  6. 根据权利要求1至5任一项所述的方法，其中，所述反馈信息还包 括：
    辅助信息，其中，所述辅助信息，至少供用户设备UE确定用于获取所述SIB所需的相关信息。
  7. 根据权利要求6所述的方法，其中，所述辅助信息包括以下至少之一：
    时长信息，指示所述UE再次发起所述获取请求的间隔时长；
    可用状态信息，指示是否有所述获取请求所请求SIB携带的配置信息，或指示所述获取请求所请求SIB的携带配置信息所指示资源是否可用。
  8. 根据权利要求1至7任一项所述的方法，其中，所述接收请求系统消息块SIB的获取请求，包括：
    接收携带有所述获取请求的第一消息Msg1。
  9. 根据权利要求8所述的方法，其中，所述下发针对所述获取请求的反馈信息，包括：
    下发携带有所述反馈信息的第二消息Msg2。
  10. 根据权利要求9所述的方法，其中，
    所述反馈信息，携带在所述Msg2的MAC随机接入响应RAR中。
  11. 根据权利要求10所述的方法，其中，携带所述反馈信息的MAC RAR为第二类型MAC RAR；不携带所述反馈信息的MAC RAR为第一类型MAC RAR。
  12. 根据权利要求10或11所述的方法，其中，不能够携带所述反馈信息的Msg2为第一类型Msg2；
    能够携带所述反馈信息的Msg2为第二类型Msg2。
  13. 根据权利要求9至12任一项所述的方法，其中，对应于所述第一类型Msg2的Msg1的通信资源，不同于对应于所述第二类型Msg2的Msg1通信资源。
  14. 根据权利要求13所述的方法，其中，所述方法还包括：
    下发SIB1，其中，所述SIB1中携带有对应所述第二类型Msg2的Msg1的通信资源的资源信息。
  15. 根据权利要求8所述的方法，其中，所述下发针对所述获取请求的反馈信息，包括：
    下发携带有与所述反馈信息对应的随机接入前导码RAP标识ID的Msg2。
  16. 根据权利要求15所述的方法，其中，携带与所述反馈信息对应的RAP ID的Msg2为第二类型Msg2，不携带与所述反馈信息对应的RAP ID的Msg为第一类型Msg2。
  17. 根据权利要求15所述的方法，其中，
    所述Msg2携带的不同RAP ID对应于不同SIB的反馈信息，且所述Msg2不具有携带有辅助信息的MAC RAR；
    或者，
    所述Msg2携带的相同RAP ID对应于不同SIB的反馈信息，且所述Msg2不具有携带有辅助信息的MAC RAR；
    或者，
    所述Msg2携带的不同RAP ID对应于不同SIB的反馈信息，且所述Msg2具有携带有辅助信息的MAC RAR；
    或者，
    所述Msg2携带的相同RAP ID对应于不同SIB的反馈信息，且所述Msg2具有携带有辅助信息的MAC RAR；
    其中，所述辅助信息，至少供用户设备UE确定用于获取所述SIB所需的相关信息。
  18. 根据权利要求17所述的方法，其中，所述Msg2还携带有具有所 述反馈信息的SIB的信息标识；
    所述信息标识携带在所述Msg2的标识信息域内，其中，所述标识信息域携带有一个或多个与NACK对应的SIB的信息标识；或者，所述标识信息域携带一个或多个与ACK对应的SIB的信息标识。
  19. 根据权利要求18所述的方法，其中，所述标识信息域包含在所述Msg2的MAC RAR中，
    一个所述MAC RAR的长度，大于或等于所述标识信息域的长度。
  20. 根据权利要求18所述的方法，其中，所述标识信息域还用于携带所述辅助信息；其中，所述辅助信息，至少供用户设备UE确定用于获取所述SIB所需的相关信息。
  21. 根据权利要求9所述的方法，其中，所述Msg2具有退避指示符BI的BI子头；其中，所述BI子头携带所述反馈信息。
  22. 根据权利要求21所述的方法，其中，所述反馈信息由所述BI子头的预留比特携带。
  23. 根据权利要求22所述的方法，其中，所述BI子头还携带有辅助信息；
    所述辅助信息，至少供用户设备UE确定用于获取所述SIB所需的相关信息。
  24. 根据权利要求1至7任一项所述的方法，其中，所述接收请求系统消息块SIB的获取请求，包括：
    接收携带有所述SIB的获取请求的第三消息Msg3。
  25. 根据权利要求24所述的方法，其中，所述下发针对所述获取请求的反馈信息，包括：
    下发携带所述反馈信息的第四消息Msg4。
  26. 根据权利要求25所述的方法，其中，所述Msg4包括：媒体访问 控制MAC控制单元CE，所述MAC CE包括：MAC CE子头；
    其中，MAC CE子头所携带的多个LCID值中至少部分值，与所述反馈信息具有对应关系。
  27. 根据权利要求24所述的方法，其中，所述Msg4包括：媒体访问控制MAC控制单元CE，所述MAC CE包括：有效负荷；
    其中，所述有效负荷中连续分布的第一部分，与所述反馈信息不具有对应关系；
    所述有效负荷中所述第一部分以外的第二部分，与所述反馈信息具有对应关系。
  28. 根据权利要求25所述的方法，其中，所述Msg4的MAC CE的有效负荷具有扩展比特；所述扩展比特，用于携带所述反馈信息。
  29. 根据权利要求25所述的方法，其中，所述Msg4包含：
    第一类MAC CE，用于UE之间竞争冲突解决；
    第二类MAC CE，携带所述反馈信息。
  30. 根据权利要求29所述的方法，其中，所述第一类MAC CE和所述第二类MAC CE相邻分布在所述Msg4中。
  31. 根据权利要求1至7任一项所述的方法，其中，所述下发针对所述获取请求的反馈信息包括：
    下发携带有所述反馈信息的无线连接控制RRC消息。
  32. 一种请求系统消息块的方法，应用于用户设备，包括：
    发送请求系统消息块SIB的获取请求；
    接收针对所述获取请求的反馈信息。
  33. 根据权利要求32所述的方法，其中，所述SIB为按需ondemand形式获取的SIBx，x为等于2或大于2的正整数。
  34. 根据权利要求33所述的方法，其中，所述SIBx为：
    携带跟踪参考信号TRS的配置信息的SIB；
    和/或，
    携带信道状态信息参考信号CSI-RS的配置信息的SIB。
  35. 根据权利要求32所述的方法，其中，所述接收针对所述获取请求的反馈信息，包括：
    接收否定答复NACK，其中，所述NACK，指示网络侧不下发请求的SIB；
    或者，
    接收确定答复ACK，其中，所述ACK，指示网络侧下发请求的SIB。
  36. 根据权利要求32至35任一项所述的方法，其中，所述反馈信息还包括：
    辅助信息，其中，所述辅助信息，至少供用户设备UE确定用于获取所述SIB所需的相关信息。
  37. 根据权利要求36所述的方法，其中，所述辅助信息包括以下至少之一：
    时长信息，指示所述UE再次发起所述获取请求的间隔时长；
    可用状态信息，指示是否有所述获取请求所请求SIB携带的配置信息，或，指示所述获取请求所请求SIB的携带配置信息所指示资源是否可用。
  38. 根据权利要求32至37任一项所述的方法，其中，所述发送请求系统消息块SIB的获取请求，包括：
    发送携带有所述获取请求的第一消息Msg1。
  39. 根据权利要求38所述的方法，其中，所述接收针对所述获取请求的反馈信息，包括：
    接收携带有所述反馈信息的第二消息Msg 2。
  40. 根据权利要求39所述的方法，其中，所述反馈信息，携带在所述 Msg2的MAC随机接入响应RAR中。
  41. 根据权利要求40所述的方法，其中，携带所述反馈信息的MAC RAR为第二类型MAC RAR；不携带所述反馈信息的MAC RAR为第一类型MAC RAR。
  42. 根据权利要求40或41所述的方法，其中，不能够携带所述反馈信息的Msg2为第一类型Msg2；能够携带所述反馈信息的Msg2为第二类型Msg2。
  43. 根据权利要求41或42所述的方法，其中，对应于所述第一类型Msg2的Msg1的通信资源，不同于对应于所述第二类型Msg2的Msg1的通信资源。
  44. 根据权利要求42所述的方法，其中，所述方法还包括：
    接收SIB1，其中，所述SIB1中携带有所述第二类型Msg2的Msg1的通信资源的资源信息。
  45. 根据权利要求39所述的方法，其中，所述接收针对所述获取请求的反馈信息，包括：
    接收携带有与所述反馈信息对应的随机接入前导码RAP标识ID的Msg2。
  46. 根据权利要求44所述的方法，其中，
    所述Msg2携带的不同RAP ID对应于不同SIB的反馈信息，且所述Msg2不具有携带有辅助信息的MAC RAR；
    或者，
    所述Msg2携带的相同RAP ID对应于不同SIB的反馈信息，且所述Msg2不具有携带有辅助信息的MAC RAR；
    或者，
    所述Msg2携带的不同RAP ID对应于不同SIB的反馈信息，且所述 Msg2具有携带有辅助信息的MAC RAR；
    或者，
    所述Msg2携带的相同RAP ID对应于不同SIB的反馈信息，且所述Msg2具有携带有辅助信息的MAC RAR。
  47. 根据权利要求45所述的方法，其中，所述Msg2还携带有具有所述反馈信息的SIB的信息标识；所述信息标识携带在所述Msg2的标识信息域内；
    所述标识信息域携带有一个或多个与NACK对应的SIB的信息标识；
    或者，
    所述标识信息域携带一个或多个与ACK对应的SIB的信息标识。
  48. 根据权利要求46所述的方法，其中，所述标识信息域包含在所述Msg2的MAC RAR中，
    一个所述MAC RAR的长度，大于或等于所述标识信息域的长度。
  49. 根据权利要求46所述的方法，其中，所述标识信息域还用于携带所述辅助信息；其中，所述辅助信息，至少供用户设备UE确定用于获取所述SIB所需的相关信息。
  50. 根据权利要求39所述的方法，其中，所述Msg2具有退避指示符BI的BI子头；其中，所述BI子头携带所述反馈信息。
  51. 根据权利要求49所述的方法，其中，所述反馈信息由所述BI子头的预留比特携带。
  52. 根据权利要求49所述的方法，其中，所述BI子头还携带有辅助信息；
    所述辅助信息，至少供用户设备UE确定用于获取所述SIB所需的相关信息。
  53. 根据权利要求32至37任一项所述的方法，其中，所述发送请求 系统消息块SIB的获取请求，包括：
    发送携带有所述SIB的获取请求的第三消息Msg3。
  54. 根据权利要求52所述的方法，其中，所述接收针对所述获取请求的反馈信息，包括：
    接收携带所述反馈信息的第四消息Msg4。
  55. 根据权利要求53所述的方法，其中，所述Msg4包括：媒体访问控制MAC控制单元CE；所述MAC CE包括：MAC CE子头；
    其中，MAC CE子头所携带的多个LCID值中至少部分值，与所述反馈信息具有对应关系。
  56. 根据权利要求54所述的方法，其中，所述Msg4包括：媒体访问控制MAC控制单元CE；所述MAC CE包括：有效负荷；其中，所述有效负荷中连续分布的第一部分，与所述反馈信息不具有对应关系；
    所述有效负荷中所述第一部分以外的第二部分，与所述反馈信息具有对应关系。
  57. 根据权利要求54所述的方法，其中，所述Msg4的MAC CE的有效负荷具有扩展比特；所述扩展比特，用于携带所述反馈信息。
  58. 根据权利要求53所述的方法，其中，所述Msg4包含：
    第一类MAC CE，用于UE之间竞争冲突解决；
    第二类MAC CE，携带所述反馈信息。
  59. 根据权利要求57所述的方法，其中，所述第一类MAC CE和所述第二类MAC CE相邻分布在所述Msg4中。
  60. 根据权利要求32至38任一项所述的方法，其中，所述接收针对所述获取请求的反馈信息包括：
    接收携带有所述反馈信息的无线连接控制RRC消息。
  61. 根据权利要求35所述的方法，其中，所述方法还包括：
    响应于接收到未携带时长信息的所述NACK，获取再次发起所述获取请求的时长信息；其中，所述时长信息，指示所述UE再次发起所述获取请求的间隔时长。
  62. 根据权利要求60所述的方法，其中，所述获取再次发起所述获取请求的时间信息，包括以下至少之一：
    发送获取所述时长信息的请求信息；
    根据所述网络配置确定所述时长信息；
    根据预先约定确定所述时长信息；
    根据所述UE对所述NACK的应对策略，确定所述时长信息。
  63. 一种请求系统消息块的装置，其中，包括：
    第一接收模块，被配置为接收请求系统消息块SIB的获取请求；
    第一发送模块，被配置为下发针对所述获取请求的反馈信息。
  64. 一种请求系统消息块的装置，其中，包括：
    第二发送模块，被配置为发送请求系统消息块SIB的获取请求；
    第二接收模块，被配置为接收针对所述获取请求的反馈信息。
  65. 一种通信设备，包括处理器、收发器、存储器及存储在存储器上并能够有所述处理器运行的可执行程序，其中，所述处理器运行所述可执行程序时执行如权利要求1至31或32至61任一项提供的方法。
  66. 一种计算机存储介质，所述计算机存储介质存储有可执行程序；所述可执行程序被处理器执行后，能够实现如权利要求1至31或32至61任一项提供的方法。
PCT/CN2020/130213 2020-11-19 2020-11-19 请求系统消息块的方法及装置、通信设备及存储介质 WO2022104662A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
CN202080003415.8A CN112567791B (zh) 2020-11-19 2020-11-19 请求系统消息块的方法及装置、通信设备及存储介质
PCT/CN2020/130213 WO2022104662A1 (zh) 2020-11-19 2020-11-19 请求系统消息块的方法及装置、通信设备及存储介质
US18/037,614 US20240129095A1 (en) 2020-11-19 2020-11-19 Method for requesting system information block, and communication device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/130213 WO2022104662A1 (zh) 2020-11-19 2020-11-19 请求系统消息块的方法及装置、通信设备及存储介质

Publications (1)

Publication Number Publication Date
WO2022104662A1 true WO2022104662A1 (zh) 2022-05-27

Family

ID=75034963

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/130213 WO2022104662A1 (zh) 2020-11-19 2020-11-19 请求系统消息块的方法及装置、通信设备及存储介质

Country Status (3)

Country Link
US (1) US20240129095A1 (zh)
CN (1) CN112567791B (zh)
WO (1) WO2022104662A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022257012A1 (zh) * 2021-06-08 2022-12-15 北京小米移动软件有限公司 省电方法、装置、设备及可读存储介质
WO2023151085A1 (zh) * 2022-02-14 2023-08-17 北京小米移动软件有限公司 一种系统信息的传输方法、通信装置及通信设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017196146A1 (ko) * 2016-05-12 2017-11-16 삼성전자 주식회사 단말의 전력을 절약하기 위한 방법 및 장치
CN108024380A (zh) * 2016-11-04 2018-05-11 电信科学技术研究院 一种系统信息获取方法、用户终端和网络侧设备
CN110291740A (zh) * 2017-05-03 2019-09-27 摩托罗拉移动有限责任公司 对系统信息请求的反馈

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101640901B (zh) * 2009-04-29 2013-05-08 北京邮电大学 基于上行协作多点的数据合并接收方法
CN110622448B (zh) * 2017-05-24 2022-09-09 摩托罗拉移动有限责任公司 基于传输的数量达到阈值执行动作的方法和装置
CN109089225A (zh) * 2017-06-14 2018-12-25 维沃移动通信有限公司 一种系统信息传输方法、终端及网络设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017196146A1 (ko) * 2016-05-12 2017-11-16 삼성전자 주식회사 단말의 전력을 절약하기 위한 방법 및 장치
CN108024380A (zh) * 2016-11-04 2018-05-11 电信科学技术研究院 一种系统信息获取方法、用户终端和网络侧设备
CN110291740A (zh) * 2017-05-03 2019-09-27 摩托罗拉移动有限责任公司 对系统信息请求的反馈

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Correction on SI message acquisition timing", 3GPP DRAFT; R2-1817659 CORRECTION ON SI MESSAGE ACQUISITION, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Spokane, USA; 20181112 - 20181116, 12 November 2018 (2018-11-12), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051557183 *

Also Published As

Publication number Publication date
CN112567791A (zh) 2021-03-26
CN112567791B (zh) 2023-12-15
US20240129095A1 (en) 2024-04-18

Similar Documents

Publication Publication Date Title
JP2023520478A (ja) 構成情報伝送方法および装置、通信機器および記憶媒体
CN110622617B (zh) 信息处理方法、装置及计算机存储介质
CN111226487B (zh) 随机接入方法及装置、通信设备及存储介质
US20230094982A1 (en) Method and device for communication processing
WO2022016474A1 (zh) 接入控制方法及装置、存储介质
WO2022104662A1 (zh) 请求系统消息块的方法及装置、通信设备及存储介质
WO2020237679A1 (zh) 随机接入方法及装置、通信设备及存储介质
WO2021062712A1 (zh) 信息处理方法及装置、通信设备及存储介质
CN111670604B (zh) 信息传输方法及装置、通信设备及存储介质
WO2022236498A1 (zh) 连接失败检测方法及装置、通信设备及存储介质
WO2022047799A1 (zh) 接入控制方法及装置、及通信设备及存储介质
US20240064606A1 (en) Relay ue selection method and apparatus, information pro- cessing method and apparatus, and device and medium
JP7335452B2 (ja) 通信処理方法、装置及びコンピュータ記憶媒体
WO2023184121A1 (zh) 信息传输方法、装置、通信设备和存储介质
WO2023050362A1 (zh) 下行传输配置、接收方法及装置、通信设备及存储介质
CN114246007B (zh) 信息传输方法、装置、通信设备和存储介质
WO2022205362A1 (zh) 寻呼处理方法及装置、通信设备及存储介质
WO2022032482A1 (zh) 资源处理方法及装置、通信设备及存储介质
JP2023522780A (ja) 情報伝送方法、装置、通信機器及び記憶媒体
WO2024026758A1 (zh) 信息处理方法、装置、通信设备及存储介质
WO2023206504A1 (zh) 系统消息处理方法及装置、通信设备及存储介质
WO2024055313A1 (zh) 一种目标终端确定方法、装置、通信设备及存储介质
WO2024016233A1 (zh) 初始bwp处理方法、装置、通信设备及存储介质
RU2814210C1 (ru) Способ и устройство управления прямым соединением, устройство связи и носитель данных
RU2787888C1 (ru) Способ определения окна конкуренции, устройство связи и носитель данных

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20961953

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20961953

Country of ref document: EP

Kind code of ref document: A1