WO2018082605A1 - 基站、用户设备和相关方法 - Google Patents
基站、用户设备和相关方法 Download PDFInfo
- Publication number
- WO2018082605A1 WO2018082605A1 PCT/CN2017/109089 CN2017109089W WO2018082605A1 WO 2018082605 A1 WO2018082605 A1 WO 2018082605A1 CN 2017109089 W CN2017109089 W CN 2017109089W WO 2018082605 A1 WO2018082605 A1 WO 2018082605A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- system information
- request message
- time window
- information request
- base station
- Prior art date
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/0001—Arrangements for dividing the transmission path
- H04L5/0003—Two-dimensional division
- H04L5/0005—Time-frequency
- H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L27/00—Modulated-carrier systems
- H04L27/26—Systems using multi-frequency codes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L27/00—Modulated-carrier systems
- H04L27/26—Systems using multi-frequency codes
- H04L27/2601—Multicarrier modulation systems
- H04L27/2647—Arrangements specific to the receiver only
- H04L27/2655—Synchronisation arrangements
- H04L27/2689—Link with other circuits, i.e. special connections between synchronisation arrangements and other circuits for achieving synchronisation
- H04L27/2692—Link with other circuits, i.e. special connections between synchronisation arrangements and other circuits for achieving synchronisation with preamble design, i.e. with negotiation of the synchronisation sequence with transmitter or sequence linked to the algorithm used at the receiver
-
- 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
-
- 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/0048—Allocation of pilot signals, i.e. of signals known to the receiver
-
- 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
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- 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/10—Access restriction or access information delivery, e.g. discovery data delivery using broadcasted information
-
- 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
- H04W56/00—Synchronisation arrangements
- H04W56/004—Synchronisation arrangements compensating for timing error of reception due to propagation delay
- H04W56/0045—Synchronisation arrangements compensating for timing error of reception due to propagation delay compensating for timing error by altering transmission time
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W72/00—Local resource management
- H04W72/12—Wireless traffic scheduling
- H04W72/1221—Wireless traffic scheduling based on age of data to be sent
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/20—Manipulation of established connections
- H04W76/27—Transitions between radio resource control [RRC] states
Definitions
- the present disclosure relates to the field of wireless communication technologies, and more particularly, to a method of acquiring system information and corresponding base stations and user equipment.
- NTT DOCOMO proposed a new research project on 5G technology standards (see Non-patent literature: RP-160671) :New SID Proposal: Study on New Radio Access Technology), and approved.
- the goal of the research project is to develop a new wireless (New Radio: NR) access technology to meet all 5G application scenarios, requirements and deployment environments.
- NR mainly has three application scenarios: Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC) and Ultra Reliable and Low Latency Communications (URLLC).
- eMBB Enhanced Mobile Broadband
- mMTC Massive Machine Type Communication
- URLLC Ultra Reliable and Low Latency Communications
- the standardization of NR is carried out in two phases: the first phase of standardization will be completed in mid-2018; the second phase of standardization will be completed by the end of 2019.
- the first-stage standard specification is forward-compatible with the second-stage standard specification, while the second-stage standard specification is based on the first-stage standard specification and meets all the requirements of the 5G NR technical standard.
- a base station which may be labeled as an eNB or a gNB periodically broadcasts access layer and non-access layer information, collectively referred to as system information.
- system information is divided into a main system information block MasterInformationBlock (MIB) and several system information blocks SystemInformationBlocks (SIBs) for carrying different content, as of now There are up to 20 types of SIBs defined by LTE.
- MIB MasterInformationBlock
- SIBs SystemInformationBlocks
- the MIB carries the necessary and most frequently transmitted parameters for acquiring basic information of the cell
- the SIB1 includes parameters for determining whether a cell is suitable for cell selection and time domain scheduling information of other SIBs.
- the MIB and SIB1 are sent within a predefined time period.
- the other SIBs with the same scheduling period are scheduled to be sent in the same system information message (SI message) and periodically sent in the corresponding system information window SI-window according to the time domain scheduling information carried in the SIB1. .
- SI message system information message
- MIB and SIB1 not all SIBs need to be broadcast.
- the eNB selects the system information block related to the feature to broadcast according to the characteristics supported by the current access network device and the characteristics of the non-access stratum. For example, if the current access network supports enhanced access control, the eNB broadcasts the SIB14, which carries the information about the EAB.
- the eNB will broadcast SIB13 and so on. These broadcasted SIBs are reflected in the scheduling information carried by the SIB1, and the unscheduled SIBs are not broadcasted.
- SIB8 Before the UE initiates the access, in addition to the MIB and the SIB1, it is necessary to obtain other SIBs according to its own characteristics, and then initiate the access. For example, if the UE supports multiple modes, the SIB8 needs to be read to obtain the heterogeneous cell reselection information. Otherwise, it is not required. If the UE supports WLAN interoperation, the SIB17 and the like need to be acquired. Otherwise, it is not required.
- the method of periodically broadcasting all the system information supported by the eNB is beneficial to the UE to obtain corresponding information at any time. However, this does not consider the UE's acquisition requirements (for example, only a small number of UEs need to be acquired), and all system information supported by the eNB is broadcasted repeatedly on a specific downlink resource, resulting in low system resource utilization. And the energy consumption is large.
- some vendors proposed to transmit system information in a combination of network autonomous broadcasting and UE request transmission.
- system information is transmitted by the eNB autonomously through periodic broadcasts (such system information is referred to as minimum system information or first system information in the present disclosure), such system information It may include parameters required for accessing the cell and/or parameters related to cell selection and/or parameters necessary for obtaining other system information or system information required for most UEs;
- One type of system information is system information that is not included in the first system information, which is sent under certain circumstances (eg, upon receipt of a UE request or when an update is required) (this type is disclosed in the present disclosure)
- the system information is referred to as other system information or second system information or supplementary system information.
- the supplementary system information may be transmitted by broadcast or multicast or unicast. When the UE needs to supplement part or all of the system information, how to obtain the supplementary system information is a problem to be solved.
- a method and corresponding user equipment and base station capable of acquiring supplemental system information are provided.
- a method in a user equipment UE comprising: transmitting a system information request message to a base station to request required supplementary system information, simultaneously starting a timer; and defining at the timer Within the time window, the requested supplemental system information is received.
- the value of the time window is set to a multiple of the system information change period.
- the start position of the time window is set to the start subframe of the next system information change period after transmitting the system information request message.
- the start position of the time window is set to the last subframe of the system information request message plus an offset, the value of the offset being predefined or configured by RRC signaling.
- the value of the time window is set to a multiple of the transmission period of the minimum system information that schedules the requested supplemental system information.
- the start position of the time window is set to the start subframe of the next transmission cycle after transmitting the system information request message.
- the start position of the time window is set to the last subframe of the system information request message plus an offset, the value of the offset being predefined or configured by RRC signaling.
- a user equipment comprising: a transmitting unit configured to send a system information request message to a base station to request required supplementary system information; a timer unit configured to be in the The sending unit starts a timer while transmitting the system information request message to the base station; and the receiving unit is configured to receive the requested supplementary system information within a time window defined by the timer.
- the value of the time window is set to a multiple of the system information change period.
- the start position of the time window is set to the start subframe of the next system information change period after transmitting the system information request message.
- the start position of the time window is set to the last subframe of the system information request message plus an offset, the value of the offset being predefined or configured by RRC signaling.
- the value of the time window is set to a multiple of the transmission period of the minimum system information that schedules the requested supplemental system information.
- the start position of the time window is set to the start subframe of the next transmission cycle after transmitting the system information request message.
- the start position of the time window is set to the last subframe of the system information request message plus an offset, the value of the offset being predefined or configured by RRC signaling.
- a method in a base station comprising: receiving a system information request message from a UE, the system information request message requesting supplementary system information required by the UE; and responding to the system information Receiving the request message, transmitting the requested supplemental system information to the UE.
- a base station comprising: a receiving unit configured to receive a system information request message from a user equipment, the system information request message requesting supplementary system information required by the UE; and a transmitting unit And configured to transmit the requested supplemental system information to the user equipment in response to receipt of the system information request message.
- FIG. 1 shows a flowchart of a supplemental system information acquisition method according to an embodiment 1 of the present disclosure.
- FIG. 2 shows an example of an information system request message transmitting step according to the present disclosure.
- FIG. 3 shows a schematic diagram of a MAC CE as a system information request message in accordance with the present disclosure.
- FIG. 4 shows a flowchart of a supplementary information acquisition method according to Embodiment 2 of the present disclosure.
- FIG. 5 shows a block diagram of a user equipment according to Embodiment 1 of the present disclosure.
- FIG. 6 shows a block diagram of a base station according to Embodiment 1 of the present disclosure.
- FIG. 7 shows a block diagram of a user equipment according to Embodiment 2 of the present disclosure.
- FIG. 8 shows a block diagram of a base station according to Embodiment 2 of the present disclosure.
- PDCCH Physical Downlink Control Channel, physical downlink control channel
- CCCH Common Control Channel, common control channel
- DCCH Dedicated Control Channel, dedicated control channel
- BCCH Broadcast Control Channel, broadcast control channel
- RRC Radio Resource Control
- RRC inactive state the state is a state different from the RRC idle state and the RRC connected state,
- the UE in this state is based on a notification procedure initiated by the radio access network RAN.
- System information block The parameters applicable to all UEs or for some UEs are grouped according to a predefined manner (for example, according to function or according to whether it is applicable to all UEs), each set of parameters is called a system information block, which is denoted as SIB. .
- SIB system information block
- a neighbor cell related parameter for cell reselection is used as a system information block.
- System information block group A collection of system information blocks called a system information block group, denoted as SI.
- System information change cycle can be used to limit the change of system information. It can only occur in a specific system frame. That is, according to the scheduling of system information, system information may be sent multiple times in the system information change cycle and the content is the same.
- the system information in the present disclosure may be a system information block or a system information block group, unless otherwise specified.
- Fig. 1 is a flow chart showing a method of acquiring supplementary system information according to Embodiment 1 of the present invention.
- step S10 the UE transmits a preamble sequence to the base station to request supplemental system information.
- step S20 the base station receives the preamble sequence sent by the UE.
- step S30 the base station sends a response message to the UE.
- step S40 the UE receives the response message sent by the base station.
- the preamble sequence may be a preamble sequence that is predefined or configured by RRC signaling for requesting supplemental system information.
- one or a set of preamble sequences are predefined or configured by RRC signaling for requesting supplemental system information. Transmitting the preamble sequence or selecting a preamble sequence from the set of preamble sequences for transmission when the UE needs to request supplemental system information (eg, Equal probability method is chosen randomly).
- the leader sequence or leader sequence set is referred to as a first leader sequence in the present disclosure.
- two preamble sequences or two sets of preamble sequences are predefined or configured by RRC signaling for requesting supplemental system information.
- One of the preamble sequences or a set of preamble sequences is used to request all supplementary system information, that is, when the UE needs to request all supplementary system information, send the preamble sequence or select a preamble sequence from the corresponding preamble sequence group (for example, etc.)
- the probability mode is randomly selected.
- the preamble sequence or the preamble sequence group is referred to as a second preamble sequence; another preamble sequence or preamble sequence group is used to request partial supplemental system information, that is, when the UE needs to request partial supplemental system information.
- the preamble sequence is transmitted or selected from a corresponding set of preamble sequences (eg, randomly selected in an equal probability manner), and the preamble sequence or preamble sequence group is referred to as a third preamble sequence in the present disclosure.
- the preamble sequence includes a plurality of preamble sequences respectively corresponding to different system information block/system information block groups
- transmitting the preamble sequence to the base station includes: from the plurality of preambles
- a preamble sequence corresponding to the system information block/system information block group required by the UE is selected in the sequence for transmission.
- the correspondence between the plurality of preamble sequences and the system information block/system information block group is predefined or configured by RRC signaling. The correspondence may be that one preamble sequence corresponds to one system information block; for example, the system information block SIB X corresponds to the preamble sequence Y.
- the corresponding relationship may also be that one preamble sequence corresponds to one system information block group; for example, the system information block group N corresponds to the preamble sequence S, and the system information block group N includes system information blocks SIB X1, SIB X2, and SIB X3. It is also possible to pre-define or configure one preamble sequence corresponding to all supplementary system information by RRC signaling, that is, one of the plurality of preamble sequences corresponds to all system information. In this embodiment, when the UE requests a certain system information block or system information block group or all supplementary system information, the corresponding preamble sequence is selected and transmitted. All supplementary system information described in the present disclosure may be all supplementary system information supported by the cell.
- one or more (or one or more groups) of preamble sequences are predefined or configured by RRC signaling, and the system information block or system information block group requested by the UE according to requirements
- the number of selections corresponds to a corresponding number of preamble sequences and the selected preamble sequence is transmitted (or a preamble sequence is selected from the corresponding set of preamble sequences).
- the resource used by the UE to send the preamble sequence may be a resource used by the UE to perform random access or a resource configured by a pre-defined or configured by RRC signaling to send a preamble sequence requesting supplementary system information. If the resource for transmitting the preamble sequence requesting the supplemental system information is different from the resource of the random access, the base station can determine whether the UE performs random access or requests supplementary system information from the resource location of the preamble sequence. Pre-defined or configured dedicated preamble sequences are used to request supplemental system information. Different resource configurations can be used to request different supplementary system information (ie, system information block/system information block group). For example, different supplemental system information is mapped to different time-frequency resources.
- the request (or preamble sequence) is sent on the corresponding time-frequency resource.
- the base station determines the supplementary system information required by the UE according to the mapping relationship.
- the response message sent by the base station to the UE may also be different according to the difference of the preamble sequence sent by the UE.
- the base station sends a response message corresponding to the first preamble sequence (or the third preamble sequence) to the UE, where the response message includes an allocated uplink resource (UL Grant), and the uplink resource may be used for sending by the UE.
- UL Grant allocated uplink resource
- a system information request message to request the required supplemental system information.
- the base station receives the non-first preamble sequence and the third preamble sequence (eg, the second preamble sequence) from the UE, and sends the corresponding non-first preamble sequence and the third preamble sequence to the UE (eg, the second preamble) Sequence response message.
- the base station includes, in the response message, a system information block/system information block group corresponding to the received preamble sequence.
- the response message received by the UE from the base station includes the requested supplementary system information.
- the response message indicates that the supplemental system information requested by the UE is to be broadcast.
- the base station will subsequently broadcast the requested supplemental system information, and the UE will perform the process of receiving the supplemental system information of the broadcast.
- the response message indicates scheduling information of supplemental system information requested by the UE.
- the base station will follow the scheduling information.
- the requested supplementary system information is transmitted, and the UE performs a process of receiving the supplementary system information. For example, the UE receives the requested supplemental system information according to the scheduling information.
- the response message indicates scheduling information of supplemental system information requested by the UE, the scheduling information being pre-configured by RRC signaling.
- the UE receives the requested system information block/system information block group according to the pre-configured scheduling information.
- Figure 1 also shows that in step S50, the UE transmits a system information request message to the base station on the allocated uplink resource, requesting the required supplemental system information.
- the base station receives the system information request message sent by the UE on the uplink resource allocated to the UE.
- the base station in response to receipt of the system information request message, transmits a system information request response message to the UE.
- the UE receives the system information request response message.
- the system information request message indicates supplemental system information to be requested.
- said request message indicates an identification of one or more system information blocks to be requested.
- the request message indicates an identification of one or more system information block groups to be requested.
- the request message indicates that all system information is requested to be supplemented.
- the request message indicates an identification of one or more system information blocks to be requested and/or an identification of one or more system information block groups.
- the identifier of the system information block or system information block group may be predefined or configured by RRC signaling.
- each system information block has a number, which is assumed to be SIB X, and the number can be used as an identifier of the system information block.
- a system number block can be explicitly assigned a number, assuming SI Y, which can be used as an identifier for the system information block.
- the system information block group can also be indicated in an implicit manner. For example, assuming that the split information of the system information block group (ie, the SIB included in each SI) is included in the first system information, the UE may use the order in which the SI appears as its identifier. The order of appearance may be an order of appearance only in the set of supplementary system information blocks, or an order of appearance in all sets of system information blocks.
- the UE determines the cell before sending the system information request message (may be a small service) Whether the zone or the camping cell has the requested supplementary system information and whether the requested supplementary system information is broadcast, for example, the UE determines by acquiring the first system information.
- the system information request message may be a small service
- the radio resource that the UE sends the system information request message is not limited to the uplink resource obtained through the preamble sequence request/response process (that is, the uplink resource obtained through steps S10-S40), and may also be the uplink resource obtained by other methods. Including but not limited to, pre-defined, configured by RRC signaling, and allocated by PDCCH, in the manner, steps S10-S40 may not be performed.
- the system information request message is an RRC message transmitted on an uplink CCCH logical channel.
- the system information request message may include a cell (for example, allOtherSIRequest) for requesting all supplementary system information; the message may also include a supplementary system information block list (for example, otherSIBRequestList), and the list may be included.
- One of the elements indicates a system information block identifier or an identifier corresponding to the system information block identifier, for example, a binary string corresponding to the system information block (for example, SIB X1 corresponds to 000); the message may also include a supplement A list of system information block groups (e.g., otherSIRequestList), an element in the list indicating a system information block group identifier.
- the cells used to request all or part of the supplementary system information may be the same cell, and the system information may be requested to be fully or partially supplemented by different values of the cells.
- the UE in the RRC connected state may be an RRC message transmitted on the uplink DCCH logical channel.
- the system information request message may include a cell (for example, allOtherSIRequest) for requesting all supplementary system information; the message may also include a supplementary system information block list (for example, otherSIBRequestList), and the list may be included.
- One of the elements indicates a system information block identifier or an identifier corresponding to the system information block identifier, for example, a binary string corresponding to the system information block (for example, SIB X1 corresponds to 000); the message may also include a supplement A list of system information block groups (e.g., otherSIRequestList), an element in the list indicating a system information block group identifier.
- system information block groups e.g., otherSIRequestList
- the cells used to request all or part of the supplementary system information may be the same cell, and the cells are not passed. The same value implementation request replenishes system information in whole or in part.
- FIG. 2 shows an example of step S50 in accordance with the present disclosure. As shown in the figure, step S50 may further include:
- Step S510 the UE determines whether it is required to request all the supplementary system information, and if so, step S520 is performed; if not, the UE only needs to request partial supplementary system information, then step S530 is performed;
- step S510 and step S520 are not performed.
- Step S520 including, in the system information request message, an indication for requesting all supplementary system information (that is, the message indicates requesting all supplementary system information); for example, a value of a cell (allOtherSIRequest) corresponding to all supplementary system information is requested.
- an indication for requesting all supplementary system information that is, the message indicates requesting all supplementary system information
- a value of a cell allOtherSIRequest
- Step S530 including, in the system information request message, an indication for requesting a required system information block and/or a system information block group (ie, the message indicates supplementary system information that needs to be requested); for example, supplementing the part of the request
- the value of the cell corresponding to the system information is set to the identifier of the corresponding system information block or the identifier of the system information block group.
- the system information request message further includes a UE identifier.
- the UE identifier for example, S-TMSI
- the UE is identified as the identifier received from the upper layer; If the UE identifier is not provided, a random number may be generated, and the UE identifier is set as the generated random number.
- a timestamp may also be carried in the system information request message, for example, the timestamp is the current system time.
- Step S540 Send the system information request message to the next layer for transmission.
- the first timer is started.
- the value of the first timer is predefined or configured by RRC signaling.
- the UE identifier to be sent may be encrypted, for example, using asymmetric key encryption. That is, the UE uses the public key encryption of the base station.
- the base station when receiving the request message, the base station first obtains the UE identifier by using the decryption, so as to determine whether the UE is legal.
- the base station (for example, the eNB) can communicate with the core network, send the UE identifier to the core network, determine whether the UE is legal by the core network, and return the determination result to the base station.
- the core network may also notify the base station in a certain area (for example, notify the UE of all base stations in the tracking area) of the UE identity, so that the base station can use the UE identifier to determine whether the UE that sends the system information request message is a legitimate UE.
- the core network will also notify the corresponding UE identifier corresponding to the base station. If the UE is in the RRC inactive state or the RRC connected state, and the corresponding security configuration is already used in the base station and the UE, the system information request message may be encrypted by using the security configuration information, but the UE identifier may not be encryption. If the request message carries a timestamp, the timestamp can be encrypted.
- the system information request message is one or more MAC CEs
- FIG. 3 shows an example of a MAC CE.
- E is an extension bit for indicating whether other MAC headers are also included
- R is a reserved bit and can be set to 0
- a system information index (SI index) is used to indicate the requested supplemental system information.
- SI index system information index
- E and R may or may not exist, and may also have multiple R bits, and the number of bits occupied by the SI index is determined according to the number of system information blocks or system information block groups.
- a system information block or a system information block group may be associated with one SI index, or an SI index may be defined for requesting all supplementary system information.
- the mapping relationship between the SI index and the system information may be predefined or configured by RRC signaling or implicit indication, such as the order in which the system information appears in the first system information and the SI index (small to large or large to small) One-to-one correspondence.
- the system information request response message is an RRC message transmitted on a downlink CCCH logical channel.
- the system information request response message is an RRC message transmitted on a downlink DCCH logical channel.
- the system information request response message is an RRC message transmitted on a downlink BCCH logical channel.
- step S80 the UE receives the system information request response cancellation.
- the system information request response message indicates that the base station will broadcast the requested supplemental system information.
- the base station then broadcasts the requested supplemental system information and the UE receives the supplemental system information for the broadcast.
- step S80 the UE receives a system information request response message indicating scheduling information of the requested supplemental system information.
- the base station transmits the requested supplementary system information according to the scheduling information.
- the UE receives the requested system information according to the scheduling information.
- the system information request response message is a reject message.
- the system information request response message includes supplementary system information requested by the UE (for example, the supplementary system information requested by the UE is included in the cell rrc-SImessage, and the UE determines the received system information request response. Whether the field is included in the message). In this case, the UE performs the configuration corresponding to the requested supplementary system information (that is, the operation that needs to be performed when the system information is received); if the request message does not include the requested system information (ie, the indication office) The requested system information will be broadcast), for example, the response message does not contain the cell rrc-SImessage), then the UE receives the broadcast supplemental system information
- the base station determines whether it is supplemental system information of the broadcast/scheduling request according to the situation or the requested supplementary system information, or includes the requested supplementary system information in the system information request response message.
- the UE may determine, according to its type (or capability) or the requested system information type or the current RRC state, whether to send a CCCH or DCCH request message and receive a CCCH, DCCH or BCCH response message, for example, to classify system information into two categories. If the UE requests the first type of system information, it receives the response message transmitted on the CCCH; if the UE requests the second type of system information, it receives the response message transmitted on the BCCH.
- the second timer is started.
- the value of the second timer is predefined or configured by RRC signaling.
- the system information request response message received by the UE includes system information requested by the UE, stopping the first timer.
- the UE receives the system information request response message, stopping the first timer.
- the third timer is started, and when the third timer is running, the UE cannot send the system information request message again; when the third timer expires, the UE A system information request message can be sent.
- the value of the third timer may be predefined or configured by RRC signaling or included in the system information request rejection message.
- the following operations may be performed: resetting the MAC layer and releasing the MAC configuration; and/or notifying the upper layer to obtain system information.
- system information request response message it may be determined whether the system information request response message is a system information request rejection message. For example, if the system information request response message includes the requested system information or includes an indication that the requested system information is to be broadcast/scheduled, the system information request response is not a system information request rejection message, otherwise the system Information request rejection message.
- the UE may receive the requested supplementary system information in a corresponding scheduling period according to the scheduling information of the requested supplementary system information carried in the response message of the system information request.
- One SI-RNTI may be pre-defined or configured by RRC to monitor the PDCCH corresponding to the requested supplementary system information.
- the scheduling information may also not be included in the system information request response message, but may be over-RRC signaling configuration (eg, included in the first system information).
- the operation that needs to be performed when receiving the supplementary system information is performed according to the received supplemental system information.
- the first timer or the second timer is stopped when the supplementary system information is received.
- the upper layer indicates that the system information acquisition fails.
- the maximum number of transmittables is predefined or configured by RRC signaling (eg, included in the first system information). If the maximum number of times of transmission is not reached, the UE may repeat step S50, following Additional system information required for the renewal request.
- the UE may also employ a random access procedure to receive supplemental system information.
- FIG. 4 shows a flowchart of a supplementary information acquisition method according to Embodiment 2 of the present disclosure. The operation of the media access control layer when the UE receives the supplemental system information by using the random access procedure will be described below with reference to FIG.
- step S210 the UE sends a system information acquisition request, and starts a fourth timer; the value of the fourth timer is predefined or configured through RRC signaling.
- the fourth timer is a time window, and the UE receives the requested system information within the time window; the value of the time window may be set to a multiple of the system information change period.
- the starting position of the time window is a starting subframe of a next change period after the request message is sent.
- the start position of the time window is the last subframe of the transmission system information request message plus an offset. The value of the offset is predefined or configured by RRC signaling.
- the value of the fourth timer is a time window during which the UE receives the requested system information.
- the value of the time window is a multiple of the transmission period of the first system information that schedules the requested system information.
- the starting position of the time window is a starting subframe of a next transmission period after the request message is sent.
- the start position of the time window is the last subframe of the transmission system information request message plus an offset.
- the value of the offset is predefined or configured by RRC signaling.
- the first timer may also be a time window, and the value of the time window and the starting position may be the same as the fourth timer.
- the start position of the time window may be when the UE sends the system information request message to the lower layer (that is, when the system information request message is sent to the lower layer, the first timer is started).
- step S220 the base station receives a system information request message sent by the UE. Then, at Step S230, the base station sends the requested supplementary system information.
- the UE receives the requested supplemental system information within the defined time window (or when the fourth timer is running).
- the fourth timer is stopped.
- the fourth timer is stopped if the UE receives a PDCCH scrambled by an RNTI (denoted as SIR-RNTI) for the System Information Request message.
- RNTI denoted as SIR-RNTI
- the fourth timer is stopped if the UE receives the Temporary C-RNTI (Temporary C-RNTI) scrambled PDCCH.
- the fourth timer is stopped if the UE receives the Temporary C-RNTI (Temporary C-RNTI) scrambled PDCCH.
- the fourth timer expires, if the number of preamble transmissions has reached the maximum number of transmissions +1, the upper layer indicates that the acquisition of system information fails.
- FIG. 5 shows a block diagram of a UE 500 in accordance with Embodiment 1 of the present disclosure.
- the UE 500 includes a transmitting unit 510 configured to transmit a preamble sequence to the base station to request supplemental system information, and a receiving unit 520 configured to receive a response message from the base station.
- the preamble sequence includes a plurality of preamble sequences, respectively, corresponding to different system information block/system information block groups, and the transmitting unit 510 is further configured to: A preamble sequence corresponding to a system information block/system information block group required by the UE is selected from among a plurality of preamble sequences for transmission.
- the preamble sequence includes a plurality of preamble sequences, respectively, corresponding to different system information block/system information block groups, and one of the plurality of preamble sequences corresponds to All supplement system information when the UE needs full
- the transmitting unit 510 is further configured to: select a preamble sequence corresponding to all supplementary system information from the plurality of preamble sequences for transmission.
- the correspondence between the plurality of preamble sequences and the system information block/system information block group is predefined or configured by RRC signaling.
- the correspondence is: one preamble sequence corresponds to one system information block; or one preamble sequence corresponds to one system information block group.
- the preamble sequence includes a plurality of preamble sequences
- the transmitting unit 510 is further configured to: select a corresponding number of preamble sequences for transmission according to a required number of system information blocks/system information block groups .
- the transmitting unit 510 is further configured to transmit a preamble sequence on a resource configured by the RRC signaling for transmitting the request supplemental system information.
- different resources are configured to request different sets of system information blocks/system information blocks
- the transmitting unit 510 is further configured to: according to a system information block/system information block group required by the UE, The preamble sequence is sent on the corresponding resource.
- the response message indicates that the base station will broadcast the requested system information block/system information block group
- the receiving unit 520 is further configured to receive the broadcasted system information block/system information block group.
- the response message indicates scheduling information of the requested system information block/system information block group
- the receiving unit 520 is further configured to: receive the requested system information block according to the scheduling information/ System information block group.
- the scheduling information is pre-configured by RRC signaling
- the response message indicates that the requested system information block/system information block group will be scheduled according to pre-configured scheduling information
- the receiving unit 520 is further configured to: receive the requested system information block/system information block group according to the pre-configured scheduling information.
- the response message indicates an allocated uplink resource, and the UE is authorized to transmit a system information request message on the uplink resource to request the required supplemental system information from the base station.
- the transmitting unit 510 is further configured to: on the assigned A system information request message is transmitted on the line link resource, and the system information request message indicates a required system information block/system information block group.
- the system information request message includes an identification indicating that all of the supplemental system information is required.
- the system information request message is an RRC message transmitted on an uplink CCCH logical channel or an uplink DCCH logical channel.
- the system information request message includes a UE identity.
- the UE identity is an identity received from an upper layer or a random number generated by the UE.
- the system information request message includes a timestamp that records the current system time.
- the system information request message is one or more MAC CEs.
- the receiving unit 520 is further configured to receive a system information request response message in response to transmission of the system information request message.
- the system information request response message is an RRC message transmitted on a downlink CCCH logical channel or a downlink DCCH logical channel or a downlink BCCH logical channel.
- the system information request response message includes the requested system information block/system information block group.
- the system information request response message indicates that the base station will broadcast the requested system information block/system information block group
- the receiving unit 520 is further configured to: receive the broadcasted system information block/system information block group.
- system information request response message indicates scheduling information of the requested system information block/system information block group
- the receiving unit 520 is further configured to: receive the requested system according to the scheduling information.
- Information block / system information block group is further configured to: receive the requested system according to the scheduling information.
- FIG. 6 shows a block diagram of a base station 600 in accordance with Embodiment 1 of the present disclosure.
- the base station 600 includes a receiving unit 610 configured to receive a preamble sequence requesting supplemental system information from the UE, and a transmitting unit 620 configured to send a response message to the UE.
- the preamble sequence includes a plurality of preamble sequences respectively corresponding to different system information block/system information block groups
- the transmitting unit 620 is further configured to: respond to a message The system information block/system information block group corresponding to the received preamble sequence is included.
- the preamble sequence includes a plurality of preamble sequences respectively corresponding to different system information block/system information block groups
- the transmitting unit 620 is further configured to: send to the UE a response message indicating that the requested system information block/system information block group will be broadcast;
- the transmitting unit 620 is further configured to broadcast the requested system information block/system information block group.
- the preamble sequence includes a plurality of preamble sequences respectively corresponding to different system information block/system information block groups
- the transmitting unit 620 is further configured to: send to the UE And a response message indicating the scheduling information of the requested system information block/system information block group; and transmitting the requested system information block/system information block group according to the scheduling information.
- different resources are configured for requesting different system information block/system information block groups by the UE, and the transmitting unit 620 is further configured to: determine the UE according to the resource receiving the preamble sequence Additional system information is required for delivery.
- the response message includes an uplink resource allocated to the UE, and the UE is authorized to transmit a system information request message on the uplink resource to request the required supplemental system information.
- the receiving unit 610 is further configured to: receive a system information request message sent by the UE on the allocated uplink resource, requesting supplementary system information required.
- the transmitting unit 620 is further configured to transmit a system information request response message in response to receipt of the system information request message.
- the system information request response message is an RRC message transmitted on a downlink CCCH logical channel or a downlink DCCH logical channel or a downlink BCCH logical channel.
- the system information request response message includes the requested system information block/system information block group.
- system information request response message indicates that the requested system information block/system information block group will be broadcast
- the transmitting unit 620 is further configured to: broadcast a system information block/system information block group.
- the system information request response message indicates scheduling information of the requested system information block/system information block group
- the transmitting unit 620 is further configured to: send the requested system according to the scheduling information.
- Embodiment 1 The other various embodiments described above in connection with Embodiment 1 are also applicable to the UE 500 and the base station 600.
- FIG. 7 shows a block diagram of a UE 700 in accordance with Embodiment 2 of the present disclosure.
- the UE 700 includes a transmitting unit 710 configured to send a system information request message to the base station to request required supplementary system information, and a timer unit 720 configured to send system information to the base station at the transmitting unit 710.
- the timer is started at the same time as the request message; and the receiving unit 730 is configured to receive the requested supplemental system information within a time window defined by the timer.
- the value of the time window is set to a multiple of the system information change period.
- the start position of the time window is set to the start subframe of the next system information change period after transmitting the system information request message.
- the start position of the time window is set to the last subframe of the system information request message plus an offset, the value of the offset being predefined or configured by RRC signaling.
- the value of the time window is set to a multiple of the transmission period of the minimum system information that schedules the requested supplemental system information.
- the start position of the time window is set to the start subframe of the next transmission cycle after transmitting the system information request message.
- the start position of the time window is set to a system information request
- the last subframe of the message is appended with an offset whose value is predefined or configured by RRC signaling.
- FIG. 8 shows a block diagram of a base station 800 in accordance with Embodiment 2 of the present disclosure.
- the base station 800 includes a receiving unit 810 configured to receive a system information request message from the UE, the system information request message requesting supplementary system information required by the UE, and a transmitting unit 820 configured to respond to Receiving the system information request message, and transmitting the requested supplemental system information to the UE.
- Embodiment 2 The other various embodiments described above in connection with Embodiment 2 are also applicable to the UE 700 and the base station 800.
- the above-described embodiments of the present invention can be implemented by software, hardware, or a combination of both software and hardware.
- the base station and various components within the user equipment in the above embodiments may be implemented by various devices or circuits including, but not limited to, analog circuit devices, digital circuit devices, digital signal processing (DSP) circuits, and the like.
- DSP digital signal processing
- Programming processors application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), programmable logic devices (CPLDs), and the like.
- embodiments of the invention disclosed herein may be implemented on a computer program product.
- the computer program product is a product having a computer readable medium encoded with computer program logic that, when executed on a computing device, provides related operations to implement The above technical solution of the present invention.
- the computer program logic When executed on at least one processor of a computing system, the computer program logic causes the processor to perform the operations (methods) described in the embodiments of the present invention.
- the setting code of the present invention Software, code, and/or other data structures, or such as one or more ROM or RAM or PROM, that are provided or encoded on a computer readable medium such as an optical medium (eg, a CD-ROM), a floppy disk, or a hard disk.
- Software or firmware or such a configuration may be installed on the computing device such that one or more processors in the computing device perform the technical solutions described in the embodiments of the present invention.
- Embodiments of the invention disclosed herein may be implemented as a program running on a device in accordance with the present invention.
- the program running on the device according to the present invention may be a program that causes a computer to implement the functions of the embodiments of the present invention by controlling a central processing unit (CPU).
- the program or information processed by the program may be temporarily stored in a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memory system.
- a volatile memory such as a random access memory RAM
- HDD hard disk drive
- non-volatile memory such as a flash memory
Landscapes
- Engineering & Computer Science (AREA)
- Signal Processing (AREA)
- Computer Networks & Wireless Communication (AREA)
- Computer Security & Cryptography (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
本公开提供了一种获取补充***信息的方法和对应的用户设备和基站。根据本公开的用户设备中的方法包括:向基站发送***信息请求消息,以请求所需的补充***信息,同时启动定时器;以及在定时器所定义的时间窗内,接收所请求的补充***信息。
Description
本公开涉及无线通信技术领域,更具体地,本公开涉及一种获取***信息的方法和相应的基站和用户设备。
2016年3月,在第三代合作伙伴计划(3rd Generation Partnership Project:3GPP)RAN#71次全会上,NTT DOCOMO提出了一个关于5G技术标准的新的研究项目(参见非专利文献:RP-160671:New SID Proposal:Study on New Radio Access Technology),并获批准。该研究项目的目的是开发一个新的无线(New Radio:NR)接入技术以满足5G的所有应用场景、需求和部署环境。NR主要有三个应用场景:增强的移动宽带通信(Enhanced Mobile Broadband:eMBB)、大规模机器类通信(massive Machine Type Communication:mMTC)和超可靠低延迟通信(Ultra Reliable and Low Latency Communications:URLLC)。按照该研究项目的规划,NR的标准化分二个阶段进行:第一阶段的标准化工作将于2018年中期完成;第二阶段的标准化工作将于2019年底完成。第一阶段的标准规范要前向兼容于第二阶段的标准规范,而第二阶段的标准规范要建立在第一阶段的标准规范之上,并满足5G NR技术标准的所有要求。
为了更好地节能减排,在该项目的初期要求中提出了要避免网络侧重复发送不必要的信息。该要求是基于以下考虑:
在现有的LTE***中,为了保证LTE用户设备(UE)的正常接入,基站(可标记为eNB或gNB)会周期性的广播接入层以及非接入层的信息,统称为***信息。目前LTE***中,***信息分为一个主***信息块MasterInformationBlock(MIB)和若干个***信息块SystemInformationBlocks(SIBs)用来承载不同的内容,截止目前为
止LTE定义的SIB多达20种。MIB上携带了用于获取小区的基本信息的必需的以及最频繁发送的参数,SIB1中包含用来判断某小区是否适合用于小区选择的参数以及其他SIB的时域调度信息。MIB和SIBl在预定义的时间周期内发送。其他具有相同调度周期的SIB会被安排在同一个***信息消息(System Information Message,称为SI消息)中并按照SIB1中携带的时域调度信息在对应的***信息窗SI-window内周期性发送。除了MIB和SIB1外,并不是所有SIB都需要被广播。eNB根据当前接入网设备支持的特性,以及非接入层的特性,选择与特性相关的***信息块进行广播。例如,当前接入网支持增强的接入准入控制(Enhanced Access Control),则eNB会广播SIB14,里面携带EAB的相关信息,反之,则不广播;如果当前接入网支持MBMS(Multimedia Broadcast Multicast Service,多媒体广播多播业务),则eNB会广播SIB13等。这些被广播的SIB都会在SIB1携带的调度信息中反映,没有调度的SIB即不被广播。UE在发起接入前,除了MIB和SIB1是必须获取的,还需要根据自身特性获得其他的SIB,然后再发起接入。例如,如果UE支持多制式,还需要读取SIB8获取异制式相关的小区重选信息,反之,则不需要;如果UE支持WLAN的互操作,还需要获取SIB17等,反之,则不需要。
采用周期性广播eNB所支持的所有的***信息的方式,有利于UE随时获取相应的信息。但是,这种不考虑UE的获取需求(例如,部分***信息只有少量的UE需要获取),而将eNB所支持的所有***信息在特定的下行资源上周而复始的广播,导致***资源利用率不高且能耗较大。在3GPP RAN2#94次会议上,部分厂商提出采用网络自主广播与UE请求发送相结合的方式传输***信息。这些厂商提出将***信息分成两类:一类***信息由eNB自主通过周期性广播的方式发送(本公开中将这类***信息称为最小***信息或第一***信息),这类***信息中可以包含访问小区所需要的参数和/或小区选择相关参数和/或获取其他***信息所必需的参数或为绝大多数UE所需的***信息;另
一类***信息是那些不包含在第一***信息中的***信息,所述***信息在特定的情况下(例如:在收到UE请求时或需要更新时)才发送(本公开中将这类***信息称为其他***信息或第二***信息或补充***信息),补充***信息可以采用广播或组播或单播方式发送。当UE需要部分或全部补充***信息时,如何获取所述补充***信息是需要解决的问题。
发明内容
根据本公开,提供了能够获取补充***信息的方法和对应的用户设备和基站。
根据本公开的第一方面,提供了一种用户设备UE中的方法,包括:向基站发送***信息请求消息,以请求所需的补充***信息,同时启动定时器;以及在定时器所定义的时间窗内,接收所请求的补充***信息。
在一个实施例中,所述时间窗的值被设置为***信息变更周期的倍数。
在一个实施例中,所述时间窗的起始位置被设置为发送***信息请求消息后的下一***信息变更周期的起始子帧。
在一个实施例中,所述时间窗的起始位置被设置为***信息请求消息的最后一个子帧加上一个偏移,所述偏移的值是预定义的或通过RRC信令配置的。
在一个实施例中,所述时间窗的值被设置为调度所请求的补充***信息的最小***信息的发送周期的倍数。
在一个实施例中,所述时间窗的起始位置被设置为发送***信息请求消息后的下一发送周期的起始子帧。
在一个实施例中,所述时间窗的起始位置被设置为***信息请求消息的最后一个子帧加上一个偏移,所述偏移的值是预定义的或通过RRC信令配置的。
根据本公开的第二方面,提供了一种用户设备,包括:发送单元,被配置为向基站发送***信息请求消息,以请求所需的补充***信息;定时器单元,被配置为在所述发送单元向基站发送***信息请求消息的同时启动定时器;以及接收单元,被配置为在定时器所定义的时间窗内,接收所请求的补充***信息。
在一个实施例中,所述时间窗的值被设置为***信息变更周期的倍数。
在一个实施例中,所述时间窗的起始位置被设置为发送***信息请求消息后的下一***信息变更周期的起始子帧。
在一个实施例中,所述时间窗的起始位置被设置为***信息请求消息的最后一个子帧加上一个偏移,所述偏移的值是预定义的或通过RRC信令配置的。
在一个实施例中,所述时间窗的值被设置为调度所请求的补充***信息的最小***信息的发送周期的倍数。
在一个实施例中,所述时间窗的起始位置被设置为发送***信息请求消息后的下一发送周期的起始子帧。
在一个实施例中,所述时间窗的起始位置被设置为***信息请求消息的最后一个子帧加上一个偏移,所述偏移的值是预定义的或通过RRC信令配置的。
根据本公开的第三方面,提供了一种基站中的方法,包括:从UE接收到***信息请求消息,所述***信息请求消息请求UE所需的补充***信息;以及响应于所述***信息请求消息的接收,向所述UE发送所请求的补充***信息。
根据本公开的第四方面,提供了一种基站,包括:接收单元,被配置为从用户设备接收到***信息请求消息,所述***信息请求消息请求UE所需的补充***信息;以及发送单元,被配置为响应于***信息请求消息的接收,向所述用户设备发送所请求的补充***信息。
通过下文结合附图的详细描述,本公开的上述和其它特征将会变得更加明显,其中:
图1示出了根据本公开的实施方案l的补充***信息获取方法的流程图。
图2示出了根据本公开的信息***请求消息发送步骤的一个示例。
图3示出了根据本公开的作为***信息请求消息的MAC CE的示意图。
图4示出了根据本公开的实施方案2的补充信息获取方法的流程图。
图5示出了根据本公开实施方案1的用户设备的框图。
图6示出了根据本公开实施方案1的基站的框图。
图7示出了根据本公开实施方案2的用户设备的框图。
图8示出了根据本公开实施方案2的基站的框图。
下面结合附图和具体实施方式对本公开进行详细阐述。应当注意,本公开不应局限于下文所述的具体实施方式。另外,为了简便起见,省略了对与本公开没有直接关联的公知技术的详细描述,以防止对本公开的理解造成混淆。
下面描述本公开涉及的术语:
PDCCH:Physical Downlink Control Channel,物理下行控制信道;
CCCH:Common Control Channel,公共控制信道;
DCCH:Dedicated Control Channel,专用控制信道;
BCCH:Broadcast Control Channel,广播控制信道;
RRC:Radio Resource Control,无线资源控制
RRC非激活态:所述状态是不同于RRC空闲态和RRC连接态的状态,
处于此状态的UE基于无线访问网络RAN发起的通知过程。
MAC CE:媒体访问控制元素
***信息块:将适用于全部UE或适用于部分UE的参数根据预定义的方式分组(例如按照功能划分或按照是否适用于所有UE划分),每组参数称为一个***信息块,记为SIB。例如,将用于小区重选的邻小区相关参数作为一个***信息块。
***信息块组:若干***信息块组成的集合称为***信息块组,记为SI。
***信息变更周期:可以使用***信息变更周期来限定***信息的改变只能发生在特定的***帧,即根据***信息的调度,***信息可能在***信息变更周期内发送多次且内容相同。
如未特别说明,本公开中的***信息可以是***信息块或***信息块组。
以下结合附图描述根据本公开的补充***信息获取方法。
实施方案1
前导序列/应答消息
图1示出了根据本发明的实施方案1的补充***信息获取方法的流程图。
在步骤S10,UE向基站发送前导序列,以请求补充***信息。
在步骤S20,基站接收到UE发送的前导序列。
在步骤S30,基站向UE发送应答消息。
在步骤S40,UE接收到基站发送的应答消息。
所述前导序列可以是预定义的或通过RRC信令配置的用于请求补充***信息的前导序列。
在一个实施例中,预定义或通过RRC信令配置一个或一组前导序列用于请求补充***信息。当UE需要请求补充***信息时,发送所述前导序列或从所述前导序列组中选择一个前导序列以供发送(例如以
等概率方式随机选择)。在本公开中称所述前导序列或前导序列组为第一前导序列。
在一个实施例中,预定义或通过RRC信令配置两个前导序列或两组前导序列用于请求补充***信息。其中一个前导序列或一组前导序列用于请求全部补充***信息,即当UE需要请求全部补充***信息时,发送所述前导序列或从对应的前导序列组中选择一个前导序列发送(例如以等概率方式随机选择),在本公开中称所述前导序列或前导序列组为第二前导序列;另一个前导序列或前导序列组用于请求部分补充***信息,即当UE需要请求部分补充***信息时,发送所述前导序列或从对应的前导序列组中选择一个前导序列发送(例如以等概率方式随机选择),在本公开中称所述前导序列或前导序列组为第三前导序列。
在一个实施例中,所述前导序列包括多个前导序列,所述多个前导序列分别对应于不同的***信息块/***信息块组,并且向基站发送前导序列包括:从所述多个前导序列中选择与UE所需***信息块/***信息块组相对应的前导序列以供发送。所述多个前导序列与***信息块/***信息块组之间的对应关系是预定义或通过RRC信令配置的。所述对应关系可以是一个前导序列对应于一个***信息块;例如,***信息块SIB X对应前导序列Y。所述对应关系还可以是一个前导序列对应于一个***信息块组;例如***信息块组N对应前导序列S,所述***信息块组N包含***信息块SIB X1,SIB X2,SIB X3。还可以预定义或通过RRC信令配置一个前导序列与全部补充***信息相对应,即所述多个前导序列中的一个前导序列对应于全部***信息。在本实施例中,当UE要请求某***信息块或***信息块组或全部补充***信息时,选择并发送对应的前导序列。本公开所述的全部补充***信息可以是小区所支持的所有补充***信息。
在一个实施例中,预定义或通过RRC信令配置一个或多个(或一组或多组)前导序列,UE根据需要请求的***信息块或***信息块组
的数目选择对应数目的前导序列并发送选择的前导序列(或从对应的前导序列组中选择一个前导序列发送)。
需要说明的,UE用于发送前导序列的资源可以是UE用于执行随机接入的资源或者是预定义或通过RRC信令配置的用于发送请求补充***信息的前导序列的资源。如果用于发送请求补充***信息的前导序列的资源不同于随机接入的资源,那么基站从接收到前导序列的资源位置就可以确定UE是执行随机接入还是请求补充***信息,此时不需要预定义或配置专用的前导序列用来请求补充***信息。可以将不同的资源配置用于请求不同的补充***信息(即***信息块/***信息块组)。例如,将不同的补充***信息映射到不同的时频资源。当UE需要特定的补充***信息时,在对应的时频资源上发送请求(或前导序列)。相应地,基站在接收到请求(或前导序列)时,根据映射关系确定UE所需的补充***信息。
根据UE发送的前导序列的不同,基站向UE发送的应答消息也可能不同。
在一个实施例中,基站向UE发送对应第一前导序列(或第三前导序列)的应答消息,所述应答消息中包含分配的上行资源(UL Grant),所述上行资源可以用于UE发送***信息请求消息,以请求所需的补充***信息。
在另一个实施例中,基站从UE接收到非第一前导序列和第三前导序列(例如第二前导序列),并向UE发送对应非第一前导序列和第三前导序列(例如第二前导序列)的应答消息。优选的,基站在所述应答消息中包括接收到的前导序列所对应的***信息块/***信息块组。相应地,UE从基站接收到的所述应答消息中包含请求的补充***信息。备选的,所述应答消息指示UE所请求的补充***信息将被广播。在这种情况下,基站后续将广播所请求的补充***信息,UE则执行接收广播的补充***信息的过程。备选地,所述应答消息指示UE所请求的补充***信息的调度信息。在这种情况下,基站后续将按照所述调度信息
发送所请求的补充***信息,UE则执行接收补充***信息过程。例如,UE根据调度信息,接收所请求的补充***信息。
在另一个实施例中,所述应答消息指示UE所请求的补充***信息的调度信息,所述调度信息是由RRC信令预先配置的。在这种情况下,UE根据所述预先配置的调度信息,接收所请求的***信息块/***信息块组。
***信息请求消息/***信息请求响应消息
图1还示出了在步骤S50,UE在所分配的上行链路资源上向基站发送***信息请求消息,请求所需的补充***信息。在步骤S60,基站在分配给UE的上行链路资源上接收到UE发送的***信息请求消息。在步骤S70,响应于***信息请求消息的接收,基站向UE发送***信息请求响应消息。在步骤S80,UE接收到***信息请求响应消息。
所述***信息请求消息指示所要请求的补充***信息。优选的,所述请求消息指示所要请求的一个或多个***信息块的标识。备选的,所述请求消息指示所要请求的一个或多个***信息块组的标识。备选的,所述请求消息指示请求全部补充***信息。备选的,所述请求消息指示所要请求的一个或多个***信息块的标识和/或一个或多个***信息块组的标识。所述***信息块或***信息块组的标识可以预定义或通过RRC信令配置。
例如:每个***信息块有一个编号,假设为SIB X,所述编号可以作为***信息块的标识。同样的,可以为***信息块组显式的分配一个编号,假设为SI Y,所述编号可以作为***信息块的标识。也可以用隐式的的方式指示***信息块组。例如,假设在第一***信息中包含***信息块组的划分信息(即每个SI中包含的SIB),UE可以将SI出现的顺序作为其标识。所述出现顺序可以是仅在补充***信息块组中的出现顺序,也可以是在全部***信息块组中的出现顺序。
可选的,UE发送***信息请求消息前先确定小区(可以是服务小
区或驻留小区)是否有所请求的补充***信息且所请求的补充***信息是否被广播,例如,UE通过获取第一***信息来确定。
需要说明的是,UE发送***信息请求消息的无线资源不限于通过前导序列请求/应答过程获得的上行资源(即通过步骤S10-S40获得的上行资源),也可以是其他方式获得的上行资源,包括但不限于预定义、通过RRC信令配置、通过PDCCH分配,在所述方式下,可以不执行步骤S10-S40。
在一个实施例中,所述***信息请求消息是在上行CCCH逻辑信道上传输的RRC消息。所述***信息请求消息中可以包含一个信元(例如记为allOtherSIRequest),用于请求全部补充***信息;所述消息中也可以包含一个补充***信息块列表(例如记为otherSIBRequestList),所述列表中的一个元素指示一个***信息块标识或与***信息块标识一一对应的标识,例如,***信息块对应的二进制字符串(例如,SIB X1对应000);所述消息中也可以包含一个补充***信息块组列表(例如记为otherSIRequestList),所述列表中的一个元素指示一个***信息块组标识。需要说明的是,用于请求全部或部分补充***信息的信元可以是同一个信元,通过信元不同的取值实现请求全部或部分补充***信息。
在另一个实施例中,处于RRC连接态的UE,所述***信息请求消息可以是在上行DCCH逻辑信道上传输的RRC消息。所述***信息请求消息中可以包含一个信元(例如记为allOtherSIRequest),用于请求全部补充***信息;所述消息中也可以包含一个补充***信息块列表(例如记为otherSIBRequestList),所述列表中的一个元素指示一个***信息块标识或与***信息块标识一一对应的标识,例如,***信息块对应的二进制字符串(例如,SIB X1对应000);所述消息中也可以包含一个补充***信息块组列表(例如记为otherSIRequestList),所述列表中的一个元素指示一个***信息块组标识。需要说明的是,用于请求全部或部分补充***信息的信元可以是同一个信元,通过信元不
同的取值实现请求全部或部分补充***信息。
图2示出了根据本公开的步骤S50的一个示例。如图所示,步骤S50还可以包括:
步骤S510、UE确定是否需要请求全部补充***信息,如果是,则执行步骤S520;如果否,UE仅需要请求部分补充***信息,则执行步骤S530;
需要说的是,如果不支持UE发送请求全部补充***信息的操作,则不执行步骤S510和步骤S520。
步骤S520、在所述***信息请求消息中包含用于请求全部补充***信息的指示(即所述消息指示请求全部补充***信息);例如将请求全部补充***信息对应的信元(allOtherSIRequest)的值置为“1”或“setup”或“true”或其他预定义的值。
步骤S530、在所述***信息请求消息中包含用于请求所需的***信息块和/或***信息块组的指示(即所述消息指示需要请求的补充***信息);例如将请求的部分补充***信息对应的信元的值置为对应的***信息块的标识或***信息块组的标识。
可选的,所述***信息请求消息中还包含UE标识。具体地,如果上层提供了UE标识(例如,S-TMSI)或用于在基站中获取UE上下文的标识或其他用于区分UE的标识,则置UE标识为从上层接收到的标识;如果上层没有提供UE标识,则可以生成一个随机数,并置UE标识为所述生成的随机数。
可选的,还可以在***信息请求消息中携带一个时间戳,例如所述时间戳为将当前***时间。
步骤S540、将所述***信息请求消息发送到下一层进行传输。
可选的,启动第一定时器。所述第一定时器的值预定义或通过RRC信令配置。
需要说明的是,如果UE处于空闲状态,如果请求消息中包含UE标识,可以对要发送的UE标识进行加密,例如采用非对称密钥加密,
即UE采用基站的公钥加密。此时,基站在收到所述请求消息时,先用解密获得UE标识,从而判断UE是否是合法的。基站(例如eNB)可以与核心网进行通信,将所述UE标识发送给核心网,由核心网判断UE是否合法,并将判断结果返回给基站。核心网也可以通知某个区域内的基站(例如通知UE跟踪区域内的所有基站)的UE标识,这样基站可以利用所述UE标识判断发送***信息请求消息的UE是否是合法的UE。在这种情况下,当UE的跟踪区域发生更新时,核心网也将通知相应的基站对应的UE标识。如果UE处于RRC非激活态或RRC连接态,用于此时基站和UE中已经有对应的安全配置,则可以利用所述安全配置信息对所述***信息请求消息进行加密,但UE标识可以不加密。如果所述请求消息中携带了时间戳,可以对所述时间戳进行加密。
在另一个实施例中,所述***信息请求消息是一个或多个MAC CE,图3给出了MAC CE的示例。其中E是扩展位,用于指示是否还包含其他MAC头;R是保留比特,可以置为0;***信息索引(SI index)用于指示所请求的补充***信息。需要说明的是,E和R可能存在也可能不存在,也可以有多个R比特,SI index所占的比特数根据***信息块或***信息块组的数量确定。可以将一个***信息块或一个***信息块组对应一个SI index,也可以定义一个SI index用于请求全部补充***信息。所述SI index与***信息间的映射关系可以预定义或通过RRC信令配置或隐含指示,例如***信息在第一***信息中出现的顺序与SI index(从小到大或从大到小)一一对应。
在一个实施例中,所述***信息请求响应消息是在下行CCCH逻辑信道上传输的RRC消息。
在另一个实施例中,所述***信息请求响应消息是在下行DCCH逻辑信道上传输的RRC消息。
在另一个实施例中,所述***信息请求响应消息是在下行BCCH逻辑信道上传输的RRC消息。
在一个实施例中,在步骤S80中,UE接收到***信息请求响应消
息,所述***信息请求响应消息指示基站将广播所请求的补充***信息。然后,基站广播所请求的补充***信息,UE则接收广播的补充***信息。
在一个实施例中,在步骤S80中,UE接收到***信息请求响应消息,所述***信息请求响应消息指示所请求的补充***信息的调度信息。基站根据所述调度信息来发送所请求的补充***信息。相应地,UE根据所述调度信息,接收所请求的***信息。
在一个实施例中,所述***信息请求响应消息是拒绝消息。
在一个实施例中,所述***信息请求响应消息中包含UE所请求的补充***信息(例如,UE所请求的补充***信息包含在信元rrc-SImessage中,UE判断接收到的***信息请求响应消息中是否包含所述字段)。在这种情况下,UE执行所请求的补充***信息对应的配置(即执行接收到所述***信息时需要执行的操作);如果所述请求消息中不包含所请求的***信息(即指示所请求的***信息将被广播),例如响应消息不包含信元rrc-SImessage),则UE接收广播的补充***信息
可选的,基站根据情况或所请求的补充***信息确定是广播/调度请求的补充***信息,还是在***信息请求响应消息中包含所请求的补充***信息。相应的,UE可以根据其类型(或能力)或所请求的***信息类型或当前RRC状态确定是发送CCCH或DCCH请求消息以及接收CCCH、DCCH或BCCH的应答消息,例如,将***信息分成两类,如果UE请求第一类的***信息,则接收CCCH上传输的应答消息;如果UE请求第二类的***信息,则接收BCCH上传输的应答消息。
可选的,如果UE接收到的所述***信息请求响应消息中不包含UE所请求的***信息,则启动第二定时器。所述定二定时器的值预定义或通过RRC信令配置。
可选的,如果UE接收到的所述***信息请求响应消息中包含UE所请求的***信息,则停止第一定时器。
可选的,如果UE接收到***信息请求响应消息,停止第一定时器。
可选的,如果UE接收到***信息请求拒绝消息,启动第三定时器,在所述第三定时器运行时,UE不能再次发送***信息请求消息;在第三定时器到期时,UE才可以发送***信息请求消息。所述第三定时器的值可以预定义或通过RRC信令配置或包含在所述***信息请求拒绝消息中。
可选的,如果UE接收到***信息请求拒绝消息,可以执行以下操作:重置MAC层并释放MAC配置;和/或通知上层获取***信息失败。
需要说明的是,可以根据***信息请求响应消息中不同字段判断是***信息请求响应消息是否是***信息请求拒绝消息。例如,如果所述***信息请求响应消息中包含所请求的***信息或包含指示所请求的***信息将被广播/调度的指示,则所述***信息请求应答不是***信息请求拒绝消息,否则为***信息请求拒绝消息。
补充***信息接收/发送
具体地,UE可以根据***信息请求响应消息携带的所请求的补充***信息的调度信息,在对应的调度周期内接收所请求的补充***信息。可以预定义或通过RRC配置一个SI-RNTI用来监测所请求的补充***信息对应的PDCCH。所述调度信息也可以不包含在***信息请求响应消息,而过RRC信令配置(例如包含在第一***信息中)。根据接收到的补充***信息执行在接收到该补充***信息时需要执行的操做。可选地,在接收到所述补充***信息时,停止第一定时器或第二定时器。
可选的,当第一定时器或第二定时器到期时,向上层指示***信息获取失败。可选的,在向上层指示***信息获取失败前先判断发送***信息请求消息的次数是否达到所设定的最大可发送次数。所述最大可发送次数预定义或通过RRC信令配置(例如,包含在第一***信息中)。如果未达到所述最大可发送次数,则UE可以重复步骤S50,继
续请求所需的补充***信息。
实施方案2
根据本公开,UE也可以采用随机接入过程来接收补充***信息。图4示出了根据本公开的实施方案2的补充信息获取方法的流程图。以下结合图4来描述UE采用随机接入过程接收补充***信息时媒体访问控制层的操作。
在步骤S210,UE发送***信息获取请求,并启动第四定时器;所述第四定时器的值是预定义或通过RRC信令配置的。
在一个实施例中,如果补充***信息只能在***信息变更周期的起始子帧发送(例如,假设基站在第n个***信息变更周期接收到***信息请求消息,基站将在下一个***信息变更周期发送所请求的***信息),所述第四定时器是一个时间窗,UE在所述时间窗内接收所请求的***信息;所述时间窗的值可以设置为***信息变更周期的倍数。优选的,所述时间窗的起始位置为发送请求消息后的下一变更周期的起始子帧。备选的,时间窗的起始位置是发送***信息请求消息的最后一个子帧加上一个偏移。所述偏移的值预定义或通过RRC信令配置。
在另一个实施例中,第四定时器的值是一个时间窗,UE在所述时间窗内接收所请求的***信息。所述时间窗的值是调度所请求的***信息的第一***信息的发送周期的倍数。优选的,所述时间窗的起始位置为发送请求消息后的下一发送周期的起始子帧。备选的,时间窗的起始位置是发送***信息请求消息的最后一个子帧加上一个偏移。所述偏移的值预定义或通过RRC信令配置。
需要说明的是,第一定时器也可以是一个时间窗,所述时间窗的值及起始位置可以与第四定时器相同。可选的,时间窗的起始位置可以是UE将***信息请求消息发送给下层时(即将***信息请求消息发送给下层时,启动第一定时器)。
在步骤S220,基站接收到UE发送的***信息请求消息。然后,在
步骤S230,基站发送所请求的补充***信息。
在步骤S240,UE在所定义的时间窗内(或第四计时器运行时)接收所请求的补充***信息。
在一个实施例中,如果接收到来自下一层的接收PDCCH传输的通知,且在***信息请求消息中携带了C-RNTI MAC CE,则停止第四定时器。
在一个实施例中,如果UE接收到由用于***信息请求消息的RNTI(记为SIR-RNTI)加扰的PDCCH,则停止第四定时器。可选的,还需要判断所接收到的应答消息中是否有UE所请求的***信息或指示UE所请求的***信息将发送(例如,广播)的指示,如果有,则停止第四定时器。
在一个实施例中,如果UE接收到临时C-RNTI(Temporary C-RNTI)加扰的PDCCH,则停止第四定时器。可选的,还需要判断所接收到的应答消息中是否有UE所请求的***信息或指示UE所请求的***信息将广播的指示,如果有,则停止第四定时器。
当第四定时器到期时,如果前导序列传输次数已达到最大可传输次数+1,则向上层指示获取***信息失败。
与上述实施方案1相对应,本公开提供了一种用户设备UE。图5示出了根据本公开实施方案1的UE 500的框图。如图所示,UE 500包括:发送单元510,被配置为向基站发送前导序列,以请求补充***信息;以及接收单元520,被配置为从基站接收应答消息。
在一个实施例中,所述前导序列包括多个前导序列,所述多个前导序列分别对应于不同的***信息块/***信息块组,并且所述发送单元510还被配置为:从所述多个前导序列中选择与UE所需***信息块/***信息块组相对应的前导序列以供发送。
在一个实施例中,所述前导序列包括多个前导序列,所述多个前导序列分别对应于不同的***信息块/***信息块组,并且所述多个前导序列中的一个前导序列对应于全部补充***信息,当所述UE需要全
部补充***信息时,所述发送单元510还被配置为:从所述多个前导序列中选择与全部补充***信息相对应的前导序列以供发送。
在一个实施例中,所述多个前导序列与***信息块/***信息块组之间的对应关系是预定义的或通过RRC信令配置的。
在一个实施例中,所述对应关系是:一个前导序列对应于一个***信息块;或者一个前导序列对应于一个***信息块组。
在一个实施例中,所述前导序列包括多个前导序列,并且所述发送单元510还被配置为:根据所需***信息块/***信息块组的数目,选择对应数目的前导序列以供发送。
在一个实施例中,所述发送单元510还被配置为:在通过RRC信令配置的用于发送请求补充***信息的资源上发送前导序列。
在一个实施例中,不同的资源被配置用于请求不同的***信息块/***信息块组,其中,所述发送单元510还被配置为:根据UE所需***信息块/***信息块组,在对应的资源上发送前导序列。
在一个实施例中,所述应答消息指示基站将广播所请求的***信息块/***信息块组,并且所述接收单元520还被配置为:接收广播的***信息块/***信息块组。
在一个实施例中,所述应答消息指示所请求***信息块/***信息块组的调度信息,并且所述接收单元520还被配置为:根据所述调度信息,接收所请求的***信息块/***信息块组。
在一个实施例中,所述调度信息是由RRC信令预先配置的,并且所述应答消息指示所请求***信息块/***信息块组将按照预先配置的调度信息进行调度,并且所述接收单元520还被配置为:根据所述预先配置的调度信息,接收所请求的***信息块/***信息块组。
在一个实施例中,所述应答消息指示被分配的上行链路资源,UE被授权在所述上行链路资源上发送***信息请求消息,以向基站请求所需的补充***信息。
在一个实施例中,所述发送单元510还被配置为:在所分配的上
行链路资源上发送***信息请求消息,所述***信息请求消息指示所需的***信息块/***信息块组。
在一个实施例中,所述***信息请求消息包括指示需要全部补充***信息的标识。
在一个实施例中,所述***信息请求消息是在上行CCCH逻辑信道或上行DCCH逻辑信道上传输的RRC消息。
在一个实施例中,所述***信息请求消息包括UE标识。
在一个实施例中,所述UE标识是从上层接收到的标识或UE生成的随机数。
在一个实施例中,所述***信息请求消息包括记录当前***时间的时间戳。
在一个实施例中,所述***信息请求消息是一个或多个MAC CE。
在一个实施例中,所述接收单元520还被配置为:响应于***信息请求消息的发送,接收***信息请求响应消息。
在一个实施例中,所述***信息请求响应消息是在下行CCCH逻辑信道或下行DCCH逻辑信道或下行BCCH逻辑信道上传输的RRC消息。
在一个实施例中,所述***信息请求响应消息包括所请求的***信息块/***信息块组。
在一个实施例中,所述***信息请求响应消息指示基站将广播所请求的***信息块/***信息块组,并且所述接收单元520还被配置为:接收广播的***信息块/***信息块组。
在一个实施例中,所述***信息请求响应消息指示所请求***信息块/***信息块组的调度信息,并且所述接收单元520还被配置为:根据所述调度信息,接收所请求的***信息块/***信息块组。
与上述实施方案1相对应,本公开提供了一种基站。图6示出了根据本公开实施方案1的基站600的框图。如图所示,基站600包括:接收单元610,被配置为从UE接收到请求补充***信息的前导序列;以及发送单元620,被配置为向UE发送应答消息。
在一个实施例中,所述前导序列包括多个前导序列,所述多个前导序列分别对应于不同的***信息块/***信息块组,并且所述发送单元620还被配置为:在应答消息中包括接收到的前导序列所对应的***信息块/***信息块组。
在一个实施例中,所述前导序列包括多个前导序列,所述多个前导序列分别对应于不同的***信息块/***信息块组,并且所述发送单元620还被配置为:向UE发送应答消息,所述应答消息指示将广播所请求的***信息块/***信息块组;
在一个实施例中,所述发送单元620还被配置为:广播所请求的***信息块/***信息块组。
在一个实施例中,所述前导序列包括多个前导序列,所述多个前导序列分别对应于不同的***信息块/***信息块组,并且所述发送单元620还被配置为:向UE发送应答消息,所述应答消息指示所请求的***信息块/***信息块组的调度信息;以及按照所述调度信息发送所请求的***信息块/***信息块组。
在一个实施例中,不同的资源被配置用于由UE请求不同的***信息块/***信息块组,并且所述发送单元620还被配置为:根据接收到所述前导序列的资源来确定UE所需的补充***信息以供发送。
在一个实施例中,所述应答消息包括向UE分配的上行链路资源,UE被授权在所述上行链路资源上发送***信息请求消息,以请求所需的补充***信息。
在一个实施例中,所述接收单元610还被配置为:在所分配的上行链路资源上接收UE发送的***信息请求消息,请求所需的补充***信息。
在一个实施例中,所述发送单元620还被配置为:响应于***信息请求消息的接收,发送***信息请求响应消息。
在一个实施例中,所述***信息请求响应消息是在下行CCCH逻辑信道或下行DCCH逻辑信道或下行BCCH逻辑信道上传输的RRC消息。
在一个实施例中,所述***信息请求响应消息包括所请求的***信息块/***信息块组。
在一个实施例中,所述***信息请求响应消息指示将广播所请求的***信息块/***信息块组,并且所述发送单元620还被配置为:广播***信息块/***信息块组。
在一个实施例中,所述***信息请求响应消息指示所请求***信息块/***信息块组的调度信息,并且所述发送单元620还被配置为:根据所述调度信息,发送所请求的***信息块/***信息块组。
以上结合实施方案1描述的其他各个实施例也适用于UE500和基站600。
与上述实施方案2相对应,本公开提供了一种用户设备UE。图7示出了根据本公开实施方案2的UE 700的框图。如图所示,UE 700包括:发送单元710,被配置为向基站发送***信息请求消息,以请求所需的补充***信息;定时器单元720,被配置为在发送单元710向基站发送***信息请求消息的同时启动定时器;以及接收单元730,被配置为在定时器所定义的时间窗内,接收所请求的补充***信息。
在一个实施例中,所述时间窗的值被设置为***信息变更周期的倍数。
在一个实施例中,所述时间窗的起始位置被设置为发送***信息请求消息后的下一***信息变更周期的起始子帧。
在一个实施例中,所述时间窗的起始位置被设置为***信息请求消息的最后一个子帧加上一个偏移,所述偏移的值是预定义的或通过RRC信令配置的。
在一个实施例中,所述时间窗的值被设置为调度所请求的补充***信息的最小***信息的发送周期的倍数。
在一个实施例中,所述时间窗的起始位置被设置为发送***信息请求消息后的下一发送周期的起始子帧。
在一个实施例中,所述时间窗的起始位置被设置为***信息请求
消息的最后一个子帧加上一个偏移,所述偏移的值是预定义的或通过RRC信令配置的。
与上述实施方案2相对应,本公开提供了一种基站。图8示出了根据本公开实施方案2的基站800的框图。如图所示,基站800包括:接收单元810,被配置为从UE接收到***信息请求消息,所述***信息请求消息请求UE所需的补充***信息;以及发送单元820,被配置为响应于***信息请求消息的接收,向所述UE发送所请求的补充***信息。
以上结合实施方案2描述的其他各个实施例也适用于UE 700和基站800。
还需要注意的是,在图5-8中描述的用户设备和基站仅是为了使本领域技术人员更清楚地理解本发明而作的图,其中省略了一些对理解本发明不必要的单元/组件,本发明的保护范围不应受这些附图的具体细节所限制。例如,实际生产的设备中可以包括更多的单元/组件,如显示器、操作维护接口、天线等等。同样地,图5-8中的各个单元也可通过更多或更少的单元/组件来实现。
应该理解,本发明的上述实施例可以通过软件、硬件或者软件和硬件两者的结合来实现。例如,上述实施例中的基站和用户设备内部的各种组件可以通过多种器件或电路来实现,这些器件包括但不限于:模拟电路器件、数字电路器件、数字信号处理(DSP)电路、可编程处理器、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、可编程逻辑器件(CPLD),等等。
此外,这里所公开的本发明的实施例可以在计算机程序产品上实现。更具体地,该计算机程序产品是如下的一种产品:具有计算机可读介质,计算机可读介质上编码有计算机程序逻辑,当在计算设备上执行时,该计算机程序逻辑提供相关的操作以实现本发明的上述技术方案。当在计算***的至少一个处理器上执行时,计算机程序逻辑使得处理器执行本发明实施例所述的操作(方法)。本发明的这种设置典
型地提供为设置或编码在例如光介质(例如CD-ROM)、软盘或硬盘等的计算机可读介质上的软件、代码和/或其他数据结构、或者诸如一个或多个ROM或RAM或PROM芯片上的固件或微代码的其他介质、或一个或多个模块中的可下载的软件图像、共享数据库等。软件或固件或这种配置可安装在计算设备上,以使得计算设备中的一个或多个处理器执行本发明实施例所描述的技术方案。
这里所公开的本发明的实施例可以实现为运行在根据本发明的设备上的程序。运行在根据本发明的设备上的程序可以是通过控制中央处理单元(CPU)来使计算机实现本发明的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器***中。
尽管以上已经结合本发明的优选实施例示出了本发明,但是本领域的技术人员将会理解,在不脱离本发明的精神和范围的情况下,可以对本发明进行各种修改、替换和改变。因此,本发明不应由上述实施例来限定,而应由所附权利要求及其等价物来限定。
Claims (16)
- 一种用户设备UE中的方法,包括:向基站发送***信息请求消息,以请求所需的补充***信息,同时启动定时器;以及在定时器所定义的时间窗内,接收所请求的补充***信息。
- 根据权利要求1所述的方法,其中,所述时间窗的值被设置为***信息变更周期的倍数。
- 根据权利要求2所述的方法,其中,所述时间窗的起始位置被设置为发送***信息请求消息后的下一***信息变更周期的起始子帧。
- 根据权利要求2所述的方法,其中,所述时间窗的起始位置被设置为***信息请求消息的最后一个子帧加上一个偏移,所述偏移的值是预定义的或通过无线资源控制(RRC)信令配置的。
- 根据权利要求1所述的方法,其中,所述时间窗的值被设置为调度所请求的补充***信息的最小***信息的发送周期的倍数。
- 根据权利要求5所述的方法,其中,所述时间窗的起始位置被设置为发送***信息请求消息后的下一发送周期的起始子帧。
- 根据权利要求5所述的方法,其中,所述时间窗的起始位置被设置为***信息请求消息的最后一个子帧加上一个偏移,所述偏移的值是预定义的或通过无线资源控制(RRC)信令配置的。
- 一种用户设备,包括:发送单元,被配置为向基站发送***信息请求消息,以请求所需的补充***信息;定时器单元,被配置为在所述发送单元向基站发送***信息请求消息的同时启动定时器;以及接收单元,被配置为在定时器所定义的时间窗内,接收所请求的补充***信息。
- 根据权利要求8所述的用户设备,其中,所述时间窗的值被设置为***信息变更周期的倍数。
- 根据权利要求9所述的用户设备,其中,所述时间窗的起始位置被设置为发送***信息请求消息后的下一***信息变更周期的起始子帧。
- 根据权利要求9所述的用户设备,其中,所述时间窗的起始位置被设置为***信息请求消息的最后一个子帧加上一个偏移,所述偏移的值是预定义的或通过无线资源控制(RRC)信令配置的。
- 根据权利要求8所述的用户设备,其中,所述时间窗的值被设置为调度所请求的补充***信息的最小***信息的发送周期的倍数。
- 根据权利要求12所述的用户设备,其中,所述时间窗的起始位置被设置为发送***信息请求消息后的下一发送周期的起始子帧。
- 根据权利要求12所述的用户设备,其中,所述时间窗的起始位置被设置为***信息请求消息的最后一个子帧加上一个偏移,所述偏移的值是预定义的或通过无线资源控制(RRC)信令配置的。
- 一种基站中的方法,包括:从UE接收到***信息请求消息,所述***信息请求消息请求UE所需的补充***信息;以及响应于所述***信息请求消息的接收,向所述UE发送所请求的补 充***信息。
- 一种基站,包括:接收单元,被配置为从用户设备接收到***信息请求消息,所述***信息请求消息请求UE所需的补充***信息;以及发送单元,被配置为响应于***信息请求消息的接收,向所述用户设备发送所请求的补充***信息。
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/343,721 US11290946B2 (en) | 2016-11-04 | 2017-11-02 | Base station, user equipment and related method |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201610974620.4A CN108023712B (zh) | 2016-11-04 | 2016-11-04 | 基站、用户设备和相关方法 |
CN201610974620.4 | 2016-11-04 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2018082605A1 true WO2018082605A1 (zh) | 2018-05-11 |
Family
ID=62075732
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2017/109089 WO2018082605A1 (zh) | 2016-11-04 | 2017-11-02 | 基站、用户设备和相关方法 |
Country Status (3)
Country | Link |
---|---|
US (1) | US11290946B2 (zh) |
CN (1) | CN108023712B (zh) |
WO (1) | WO2018082605A1 (zh) |
Families Citing this family (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR102531880B1 (ko) * | 2016-12-22 | 2023-05-12 | 한국전자통신연구원 | 통신 네트워크에서 시스템 정보를 전송하는 통신 노드의 동작 방법 |
US10973008B2 (en) * | 2018-03-12 | 2021-04-06 | Apple Inc. | Wireless device preferred bandwidth part configuration and duty cycle indication |
CN110636578B (zh) | 2018-06-21 | 2023-10-31 | 中兴通讯股份有限公司 | 一种请求***消息的方法、装置、存储介质及终端 |
EP3811673B1 (en) * | 2018-06-21 | 2023-03-15 | FG Innovation Company Limited | Method and apparatus for performing cell (re) selection in a wireless communication system |
CN111698767B (zh) * | 2019-03-13 | 2021-08-31 | 华为技术有限公司 | 一种请求***信息的方法及设备 |
EP4032343B1 (en) * | 2019-09-16 | 2023-07-12 | Telefonaktiebolaget Lm Ericsson (Publ) | Enhanced on-demand request procedures for obtaining various system information |
WO2022021184A1 (en) * | 2020-07-30 | 2022-02-03 | Nokia Shanghai Bell Co., Ltd. | Methods, apparatuses, and computer readable media for controlling pre-configured uplink resources in inactive state |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101442742A (zh) * | 2008-12-12 | 2009-05-27 | 华为技术有限公司 | 一种实现移动集群组呼端到端加密的方法、***及设备 |
CN101547075A (zh) * | 2008-03-25 | 2009-09-30 | 中兴通讯股份有限公司 | ***消息发送及接收方法 |
Family Cites Families (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0967740A1 (en) * | 1998-06-24 | 1999-12-29 | ICO Services Ltd. | Updating system information in LEO satellites terminal using BCCH channel |
JP4869778B2 (ja) * | 2006-01-18 | 2012-02-08 | 株式会社エヌ・ティ・ティ・ドコモ | 送信装置、受信装置および通信方法 |
CN100479548C (zh) * | 2006-06-21 | 2009-04-15 | 华为技术有限公司 | 一种传送***消息的方法及装置 |
EP1887822B1 (en) * | 2006-08-09 | 2013-07-24 | Alcatel Lucent | A method for acquiring system information by a mobile station |
JP4882775B2 (ja) * | 2007-02-09 | 2012-02-22 | 富士通株式会社 | 無線端末の通信制御方法及び無線端末 |
DE602007003076D1 (de) * | 2007-04-27 | 2009-12-17 | Research In Motion Ltd | Vorrichtung und Verfahren zur Handhabung von Rundfunksysteminformationen auf Benutzergeräten eines Telekommunikationssystems |
CN101729139B (zh) * | 2008-11-03 | 2012-11-14 | 电信科学技术研究院 | ***信息消息的传输方法和基站 |
CN101742572B (zh) * | 2008-11-07 | 2016-03-30 | 中兴通讯股份有限公司 | 调度信息的传输方法和装置 |
CN101442724B (zh) * | 2008-12-12 | 2010-12-01 | 中兴通讯股份有限公司 | 一种下一代网络短消息中心及其实现方法 |
US8873439B2 (en) * | 2010-03-25 | 2014-10-28 | Qualcomm Incorporated | Subframe dependent physical uplink control channel (PUCCH) region design |
EP2777328A1 (en) * | 2011-11-08 | 2014-09-17 | Koninklijke KPN N.V. | Distribution of system information in a wireless access telecommunications system |
CN103517211B (zh) * | 2012-06-21 | 2016-08-31 | 电信科学技术研究院 | ***广播信息的传输方法和设备 |
CN103534970B (zh) * | 2013-05-17 | 2017-09-08 | 华为技术有限公司 | ***信息块传输方法和装置 |
WO2015020583A1 (en) * | 2013-08-09 | 2015-02-12 | Telefonaktiebolaget L M Ericsson (Publ) | System information broadcast for machine-type communication |
US10034308B2 (en) * | 2014-03-11 | 2018-07-24 | Lg Electronics Inc. | Method for allocating temporary identifier to terminal in random access procedure in wireless communication system and apparatus therefor |
CN104219767A (zh) * | 2014-03-20 | 2014-12-17 | 中兴通讯股份有限公司 | 一种***信息传输方法、基站及终端 |
JP6810737B2 (ja) * | 2015-08-14 | 2021-01-06 | テレフオンアクチーボラゲット エルエム エリクソン(パブル) | ワイヤレス通信システムにおけるシステムアクセス情報の配信 |
EP3409048B1 (en) * | 2016-02-29 | 2020-12-02 | Samsung Electronics Co., Ltd. | Apparatus and method for signaling system information |
CN116782393A (zh) * | 2016-08-12 | 2023-09-19 | 华为技术有限公司 | 一种***信息发送方法及装置 |
-
2016
- 2016-11-04 CN CN201610974620.4A patent/CN108023712B/zh active Active
-
2017
- 2017-11-02 WO PCT/CN2017/109089 patent/WO2018082605A1/zh active Application Filing
- 2017-11-02 US US16/343,721 patent/US11290946B2/en active Active
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101547075A (zh) * | 2008-03-25 | 2009-09-30 | 中兴通讯股份有限公司 | ***消息发送及接收方法 |
CN101442742A (zh) * | 2008-12-12 | 2009-05-27 | 华为技术有限公司 | 一种实现移动集群组呼端到端加密的方法、***及设备 |
Non-Patent Citations (1)
Title |
---|
"Report of Email Discussion on 94#40 NR System Information", TSG-RAN WG2 95, R2-165201, 26 August 2016 (2016-08-26), pages 8 and 17, XP051140934 * |
Also Published As
Publication number | Publication date |
---|---|
CN108023712B (zh) | 2022-08-12 |
US20190274093A1 (en) | 2019-09-05 |
CN108023712A (zh) | 2018-05-11 |
US11290946B2 (en) | 2022-03-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2018082605A1 (zh) | 基站、用户设备和相关方法 | |
AU2017311151B8 (en) | Method for execution of random access, user equipment, and base station | |
TW201826815A (zh) | 需求式系統資訊傳遞進程 | |
US20190174378A1 (en) | Method for execution of random access, user equipment, and base station | |
WO2018082607A1 (zh) | 基站、用户设备和相关方法 | |
US20190394807A1 (en) | User equipment and related method | |
WO2018010694A1 (zh) | 发送和接收***消息的方法、基站和用户设备 | |
US10869337B2 (en) | Random access coverage enhancement level ramp up procedure | |
EP2632213A2 (en) | Method and apparatus for performing network entry/reentry in wireless communication system | |
US11019557B2 (en) | Apparatus and method for acquisition of periodically broadcasted system information in wireless communication | |
US20230328769A1 (en) | On-demand system information broadcasting system | |
CN110771209A (zh) | 参与***信息获取过程的用户设备和基站 | |
US11218950B2 (en) | Apparatus and method for acquisition of system information in wireless communications | |
CN107623936B (zh) | ***信息的获取方法、基站和用户设备 | |
CA3099967A1 (en) | Apparatus and method for acquisition of on-demand system information in wireless communications | |
US20240049117A1 (en) | Apparatus and method for acquisition of on-demand system information in connected state | |
US10660023B2 (en) | Apparatus and method for acquisition of on-demand system information in wireless communications | |
CN106341896B (zh) | 一种数据传输方法和设备、*** | |
US10869259B2 (en) | Apparatus and method for acquisition of system information in wireless communications | |
WO2021083262A1 (zh) | 基站、用户设备和相关方法 | |
WO2021156984A1 (ja) | 端末装置及び無線通信方法 | |
TWI840760B (zh) | 隨選系統資訊 | |
WO2017161973A1 (zh) | 数据传输方法、用户设备和基站 |
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: 17867225 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: 17867225 Country of ref document: EP Kind code of ref document: A1 |