WO2018113664A1 - 用户设备和相关方法 - Google Patents

用户设备和相关方法 Download PDF

Info

Publication number
WO2018113664A1
WO2018113664A1 PCT/CN2017/117183 CN2017117183W WO2018113664A1 WO 2018113664 A1 WO2018113664 A1 WO 2018113664A1 CN 2017117183 W CN2017117183 W CN 2017117183W WO 2018113664 A1 WO2018113664 A1 WO 2018113664A1
Authority
WO
WIPO (PCT)
Prior art keywords
system information
message
rrc
random access
triggered
Prior art date
Application number
PCT/CN2017/117183
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 EP17884014.6A priority Critical patent/EP3562251A1/en
Priority to US16/471,183 priority patent/US20190394807A1/en
Publication of WO2018113664A1 publication Critical patent/WO2018113664A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/004—Transmission of channel access control information in the uplink, i.e. towards network
    • 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
    • H04W74/0841—Random access procedures, e.g. with 4-step access with collision treatment
    • H04W74/085—Random access procedures, e.g. with 4-step access with collision treatment collision avoidance
    • 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
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/50—Queue scheduling
    • H04L47/62—Queue scheduling characterised by scheduling criteria
    • H04L47/625—Queue scheduling characterised by scheduling criteria for service slots or service orders
    • H04L47/6275—Queue scheduling characterised by scheduling criteria for service slots or service orders based on priority
    • 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
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0091—Signaling for the administration of the divided path
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • 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
    • 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

Definitions

  • the present disclosure relates to the field of wireless communication technologies, and more particularly, the present disclosure relates to user equipment and related methods.
  • 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 New Radio
  • the invention solves the problem that the system information is requested to conflict with the general random access by using the random access procedure.
  • a method in a user equipment UE includes: creating a first common control channel CCCH and a second common control channel CCCH having different priorities for transmitting a dedicated radio resource control RRC message and a system information request message, respectively, the system information request message is used to request a minimum system System information other than the information; determining, according to the priorities of the first CCCH and the second CCCH, which CCCH service data unit SDU corresponding to which one of the first CCCH and the second CCCH is included in the random access message 3'Msg3' Or the CCCH SDUs of the first CCCH and the second CCCH are both included in the random access message 3'Msg3'; and the random access message 3'Msg3' is transmitted to the base station.
  • the dedicated RRC message includes one or more of the following: an RRC Connection Request message, an RRC Connection Reestablishment Request message, or an RRC Connection Recovery Request message.
  • a user equipment UE includes: a channel creation unit configured to create a first common control channel CCCH and a second common control channel CCCH having different priorities for transmitting a dedicated radio resource control RRC message and a system information request message, respectively, the system information
  • the request message is used to request system information other than the minimum system information
  • the determining unit is configured to determine to include the first CCCH and the second CCCH in the random access message 3'Msg3' according to the priorities of the first CCCH and the second CCCH Which CCCH service data unit SDU corresponding to the CCCH or both CCCH SDUs of the first CCCH and the second CCCH are included in the random access message 3'Msg3'
  • the transmitting unit is configured to connect the random access message 3'Msg3' is sent to the base station.
  • the dedicated RRC message includes one or more of the following: an RRC Connection Request message, an RRC Connection Reestablishment Request message, or an RRC Connection Recovery Request message.
  • a method in a user equipment UE includes: creating a first CCCH and a second CCCH for separately transmitting a dedicated RRC message and a request system information message with different priorities; and selecting a preamble corresponding to a CCCH with a higher priority in the first CCCH and the second CCCH a sequence; and transmitting the selected preamble sequence to the base station.
  • the dedicated RRC message includes one or more of the following: an RRC Connection Request message, an RRC Connection Reestablishment Request message, or an RRC Connection Recovery Request message.
  • a user equipment UE includes: a channel creation unit configured to create a first CCCH and a second CCCH for separately transmitting a dedicated RRC message and a request system information message with different priorities; a selecting unit configured to select with the first CCCH and the first a preamble sequence corresponding to the higher priority CCCH in the two CCCHs; and a transmitting unit configured to transmit the selected preamble sequence to the base station.
  • the dedicated RRC message includes one or more of the following: an RRC Connection Request message, an RRC Connection Reestablishment Request message, or an RRC Connection Recovery Request message.
  • a method in a user equipment UE includes determining a priority of a transmission system information request message and a dedicated RRC message, the system information request message being used to request system information other than minimum system information; according to the priority, in a random trigger triggered by the request system information message And when the access conflicts with the random access triggered by the dedicated RRC message, selecting a preamble sequence corresponding to the high priority message in the system information request message and the dedicated RRC message; and transmitting the selected preamble sequence to the base station.
  • the method further comprises: determining whether there is an RRC procedure requesting system information Other RRC procedures other than being triggered or being executed; and if other RRC procedures other than the RRC procedure requesting system information are triggered or are being executed, waiting for other RRC procedures that are triggered or being executed to end, and then starting the requesting system information RRC procedure; or terminate the RRC procedure for requesting system information.
  • the method further comprises: determining whether there is a requesting system The RRC procedure of the information is being performed; and if there is an RRC procedure requesting system information being executed, terminating the RRC procedure of the requesting system information being executed, and performing other RRC procedures other than the RRC procedure requesting the system information, and requesting system information After the end of the other RRC procedures other than the RRC procedure, the RRC procedure of requesting system information is restarted.
  • the method further comprises: determining whether there is an RRC procedure requesting system information Other RRC procedures other than being triggered or being executed; and if other RRC procedures other than the RRC procedure requesting system information are triggered or being executed, terminate other RRC procedures other than the RRC procedure of the requesting system information being executed, and execute The RRC procedure for requesting system information.
  • the method further includes: determining whether there is a request The RRC procedure of the system information is triggered or is being executed; and if an RRC procedure requesting system information is triggered or is being executed, waiting for the RRC procedure of the triggered system system to be triggered or being executed to end, and then starting the request system information Other RRC procedures other than the RRC procedure; or other RRC procedures other than the RRC procedure for requesting system information.
  • a user equipment UE includes: a determining unit configured to determine a priority of a transmission system information request message and a dedicated RRC message, the system information request message being used to request system information other than minimum system information; and a selecting unit configured to Priority, when the random access triggered by the request system information message collides with the random access triggered by the dedicated RRC message, selecting a preamble sequence corresponding to the high priority message in the system information request message and the dedicated RRC message; And a sending unit configured to send the selected preamble sequence to the base station.
  • the UE further includes: a first determining unit configured to determine Whether there is another RRC procedure other than the RRC procedure requesting system information is triggered or is being executed; and the first RRC procedure control unit is configured to: if there is another RRC procedure other than the RRC procedure requesting system information is triggered or is being executed, Then wait for the other RRC process triggered or being executed to end, and then start the RRC procedure of requesting system information; or terminate the RRC procedure of requesting system information.
  • the UE further includes: a second determining unit, An RRC procedure configured to determine whether there is request for system information is being executed; and a second RRC process control unit configured to terminate the RRC procedure of the requesting system information being executed if an RRC procedure requesting system information is being performed, And performing other RRC procedures other than the RRC procedure for requesting system information, and restarting the RRC procedure of requesting system information after the end of other RRC procedures other than the RRC procedure for requesting system information.
  • the UE further includes: a third determining unit configured to determine Whether there is another RRC procedure other than the RRC procedure requesting system information is triggered or is being executed; and the third RRC procedure control unit is configured to: if there is another RRC procedure other than the RRC procedure requesting system information is triggered or is being executed, Then, other RRC procedures other than the RRC procedure of the system information that is being executed are terminated, and an RRC procedure of requesting system information is performed.
  • the UE further includes: a fourth determining unit Configuring, to determine whether an RRC procedure requesting system information is triggered or being executed; the fourth RRC process control unit is configured to wait for the triggered if an RRC procedure requesting system information is triggered or is being executed Or the RRC process of requesting system information that is being executed ends, and then initiates other RRC procedures other than the RRC procedure for requesting system information; or terminates other RRC procedures other than the RRC procedure for requesting system information.
  • a fourth determining unit Configuring to determine whether an RRC procedure requesting system information is triggered or being executed
  • the fourth RRC process control unit is configured to wait for the triggered if an RRC procedure requesting system information is triggered or is being executed Or the RRC process of requesting system information that is being executed ends, and then initiates other RRC procedures other than the RRC procedure for requesting system information; or terminates other RRC procedures other than the RRC procedure for requesting system information.
  • a method in a user equipment UE includes determining a priority of a random access triggered by a request system information message and a random access triggered by other events, the system information request message being used to request system information other than minimum system information; When the message-triggered random access conflicts with the random access triggered by other events, the preamble sequence corresponding to the higher priority random access is selected; and the selected preamble sequence is sent to the base station.
  • the method further comprises: determining whether there is a random connection triggered by the requesting system information message And entering a corresponding preamble sequence to be sent; and if there is a preamble sequence corresponding to the random access triggered by the request system information message to be sent, selecting a preamble sequence corresponding to the random access triggered by the request system information message.
  • the method further comprises: determining whether there is random access triggered by other events being executed; if there is random access triggered by other events being executed, interrupting other random connections currently being executed The random access triggered by the trigger message; and the preamble sequence corresponding to the random access triggered by the requesting system information message.
  • the method further includes: determining whether there is random access triggered by other events; And if there is random access triggered by other events, the preamble sequence corresponding to the random access triggered by other events is selected.
  • the method further comprises: determining whether there is a random access triggered by the requesting system information message being executed; if there is a random access being triggered by the requesting system information message being executed, interrupting the currently executing Random access triggered by requesting system information messages; and selecting a preamble sequence corresponding to random access triggered by other events.
  • a user equipment UE includes: a determining unit configured to determine a priority of a random access triggered by a request system information message and a random access triggered by another event, the system information request message being used to request system information other than minimum system information a selection unit configured to: when a random access triggered by the request system information message collides with a random access triggered by another event, select a preamble sequence corresponding to the higher priority random access; and a sending unit, It is configured to transmit the selected preamble sequence to the base station.
  • the UE further includes: a first determining unit configured to determine whether there is a And requesting, by the system information message, a preamble sequence corresponding to the random access to be sent, where the selecting unit is further configured to: if there is a preamble sequence corresponding to the random access triggered by the request system information message to be sent, select the request The preamble sequence corresponding to the random access triggered by the system information message.
  • the first determining unit is further configured to determine whether there is a random access triggered by other events
  • the UE further includes: a first random access interrupting unit configured to: if There is a random access triggered by other events being executed, interrupting the random access currently being executed triggered by other random access trigger messages, wherein the selection unit is further configured to select the trigger triggered by the request system information message.
  • the preamble sequence corresponding to the random access is further configured to determine whether there is a random access triggered by other events
  • the UE further includes: a first random access interrupting unit configured to: if There is a random access triggered by other events being executed, interrupting the random access currently being executed triggered by other random access trigger messages
  • the selection unit is further configured to select the trigger triggered by the request system information message. The preamble sequence corresponding to the random access.
  • the UE further includes: a second determining unit configured to determine whether there is a Other event-triggered random access, wherein the selection unit is further configured to: if there is random access triggered by other events, select a preamble sequence corresponding to random access triggered by other events.
  • the second determining unit is further configured to determine whether there is a random access triggered by the requesting system information message
  • the UE further comprising: a second random access interrupting unit configured to : if there is a random access triggered by the requesting system information message being executed, interrupting the random access currently triggered by the requesting system information message, and wherein the selection unit is further configured to select triggering by other events The preamble sequence corresponding to the random access.
  • a method in a user equipment UE includes determining a priority of a random access triggered by a request system information message and a random access triggered by other events, the system information request message being used to request system information other than minimum system information; When the message-triggered random access conflicts with the random access triggered by other events, the message corresponding to the higher priority random access is selected; and the selected message is included in the random access message 3'Msg3' Send the selected message to the base station.
  • a user equipment UE includes: a determining unit configured to determine a priority of a random access triggered by a request system information message and a random access triggered by another event, the system information request message being used to request system information other than minimum system information
  • the selecting unit is configured to: when the random access triggered by the requesting system information message collides with the random access triggered by other events, select a message corresponding to the random access with higher priority; and the sending unit, It is configured to transmit the selected message to the base station by including the selected message in the random access message 3'Msg3'.
  • Figure 1 schematically shows an existing random access procedure
  • FIG. 2 shows a flow diagram of a method 200 in a user equipment UE, in accordance with an embodiment of the disclosure
  • FIG. 3 shows a flow diagram of a method 300 in a user equipment UE in accordance with an embodiment of the present disclosure
  • FIG. 4-8 illustrate a flow diagram of a method 400 in a user equipment UE, in accordance with an embodiment of the disclosure
  • 9-13 illustrate a flow diagram of a method 900 in a user equipment UE, in accordance with an embodiment of the disclosure.
  • FIG. 14 shows a flowchart of a method 1400 in a user equipment UE in accordance with an embodiment of the present disclosure
  • FIG. 15 shows a block diagram of a UE 1500 in accordance with an embodiment of the present disclosure
  • FIG. 16 shows a block diagram of a UE 1600 in accordance with an embodiment of the present disclosure
  • FIG. 17 shows a block diagram of a UE 1700 in accordance with an embodiment of the present disclosure
  • FIG. 18 shows a block diagram of a UE 1800 in accordance with an embodiment of the present disclosure
  • FIG. 19 shows a block diagram of a UE 1900 in accordance with an embodiment of the disclosure.
  • system information In an existing LTE system, in order to ensure normal access of an LTE user equipment (UE), a base station (eNB) periodically broadcasts information of an access layer and a non-access stratum, 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), which are used to carry different contents.
  • MIB MasterInformationBlock
  • SIBs SystemInformationBlocks
  • the MIB carries the necessary and most frequently transmitted parameters for acquiring basic information of the cell
  • 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 (Enhanced Access Control), the eNB broadcasts the SIB14, which carries the relevant information of the EAB, and vice versa.
  • Enhanced Access Control Enhanced Access Control
  • the eNB broadcasts the SIB13 and the like. These broadcasted SIBs are reflected in the scheduling information carried by the SIB1, and the unscheduled SIBs are not broadcasted.
  • the UE 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 the multi-standard system, the SIB8 needs to be read to obtain the hetero-system-related cell reselection information. Otherwise, it is not required. If the UE supports the inter-operation of the WLAN, the SIB17 and the like need to be acquired, and vice versa.
  • MBMS Multimedia Broadcast Multicast Service
  • the NR system information was divided into two categories, one is periodic broadcast system information (called Minimum System Information, Minimum SI), and such system information can contain the most important or other System information required by system information or required by most UEs, such as parameters that must be acquired before the UE randomly accesses.
  • Minimum SI periodic broadcast system information
  • the other type is system information (called other system information, other SI) that is not included in the minimum system information.
  • the other system information may not be broadcast periodically, but may be sent when the UE requests or when the network decides to transmit.
  • the existing random access procedure includes the following four steps: (1) transmitting a selected preamble; (2) receiving a random access response (RAR); (3) transmitting a message 3 (ie, Message 3); (4) Receive the contention resolution message.
  • the content of the message 3 is different, and the message 3 may include a Cell Radio Network Temporary Identifier (C-RNTI) Medium Access Control (MAC) Control Unit (CE) or a Common Control Channel (CCCH) Service Data Unit (SDU).
  • C-RNTI Cell Radio Network Temporary Identifier
  • MAC Medium Access Control
  • CE Common Control Channel
  • SDU Service Data Unit
  • the UE may request other system information through a random access procedure.
  • some companies claim to request system information through the random access procedure step (1), that is, define different preamble sequences for different other system information (or system information blocks), and the UE requests related other systems by sending corresponding preamble sequences. information.
  • the existing LTE system stipulates that in a MAC entity, only one random access procedure can be performed at a time. If the UE uses the random access procedure to request system information, it may conflict with the random access procedure triggered by other events. The collision may occur in step (1) or step (3) of the random access procedure. How to solve the conflict between the random access procedure triggered by requesting other system information and the random access procedure triggered by other events is a problem to be solved.
  • RRC Radio Resource Control, radio resource control
  • MAC Medium Access Control, media access control
  • CCCH Common Control Channel, the common control channel, the channel may be used to send an uplink or downlink channel of control information when the association between the UE and the base station has not been determined (eg, during establishment of an RRC connection procedure);
  • UL-SCH Uplink Shared Channel, uplink shared channel; the channel has one or more of the following characteristics: beamforming (ie beamforming), dynamic transmission of transform power, modulation and coding to support dynamic link adaptation, support HARQ, support dynamic and semi-static resource allocation;
  • beamforming ie beamforming
  • dynamic transmission of transform power ie beamforming
  • modulation and coding to support dynamic link adaptation
  • support HARQ support dynamic and semi-static resource allocation
  • SDU Service Data Unit, service data unit
  • RRC connection request message RRCConnectionRequest, used to request to establish an RRC connection message
  • RRC connection reestablishment request message rrcConnectionReestablishmentRequest, used to request to re-establish the RRC connection message;
  • RRC Connection Recovery Request message RRCConnectionResumeRequest, for requesting to resume the suspended RRC connection message;
  • RRC connection state RRC_CONNECTED, when the RRC connection is established, the UE is in the RRC_CONNECTED state;
  • RRC inactive state in this state, at least one base station (referred to as eNB) stores the access layer context (AS Context) information of the UE, and can maintain 5G-RAN and 5G-CN (ie, 5G-RAN is connected) Connection between the core networks);
  • eNB stores the access layer context (AS Context) information of the UE, and can maintain 5G-RAN and 5G-CN (ie, 5G-RAN is connected) Connection between the core networks);
  • RRC idle state when no RRC connection is established (and/or the UE is not in the RRC_INACTIVE state or the base station or 5G-RAN or EUTRAN does not save the user context information), the UE is in the RRC_IDLE state;
  • PDCCH order a DCI corresponding to a specific format (for example, DCI format 1A) and used to trigger a random access procedure, where the DCI carries relevant parameters for random access;
  • Random access message 3 part of the random access procedure of the message, is a message sent by the UE to the base station.
  • the content of message 3 may be different depending on the current state of the UE.
  • the message 3 is from the upper layer or the RRC layer and may include a C-RNTI MAC CE or CCCH SDU and/or a UE collision resolution identifier and is transmitted on the uplink shared channel UL-SCH.
  • the message 3 is the message sent in the third step of the random access; when the random access is performed in the 2-step mode, the message 3 is sent in the first step of the random access.
  • the 4-step mode performs random access, which refers to random access including 4 steps: the UE sends a preamble sequence to the base station in the first step; the second step UE receives the random access response RAR from the base station; the third step UE The message 3 is sent to the base station; in the fourth step, the UE receives the message 4 for contention resolution from the base station, and the message 4 is different according to the content carried by the message 3.
  • Performing the random access in the 2-step manner refers to performing random access in two steps: in the first step, the UE sends the preamble sequence to the base station and all or part of the information carried in the random access message 3 in the 4-step mode, Other information not carried in message 3 can also be sent; in the second step, the UE receives a response from the base station.
  • the message 3 in the present invention may refer to the message sent in step 3 of the 4-step random access, and may also refer to the message sent in step 2 in the 2-step random access.
  • the present disclosure describes the system information in a 4-step random access manner as an example, and the present disclosure is also applicable to the 2-step random access method request system information.
  • the present disclosure classifies random access into two categories: one is random access triggered by requesting system information, and such random access is triggered by an upper layer (eg, RRC layer) requesting other system information, which is referred to in the present disclosure.
  • the system information is requested to be randomly accessed; the other type is random access triggered by other events, which is referred to as general random access in the present disclosure.
  • Embodiments of the present disclosure are also applicable to other naming schemes.
  • the present disclosure refers to a message requesting other system information as a system information request message.
  • the present disclosure also refers to a message including a CCCH SDU corresponding to a system information request message, but the present disclosure is also applicable to other naming schemes.
  • Manner 1 Mapping different system information to different preamble sequences, and the UE requests related other system information by sending a corresponding preamble sequence.
  • the system information required by UEs in different states may be different.
  • other system information is classified, and a corresponding preamble sequence (or a preamble sequence group) is defined (or associated).
  • the UE status in the NR system may be an RRC connected state, an RRC idle state, and an RRC inactive state.
  • other system information may be classified according to system information required by the UE in the corresponding state (other states may correspond to other system information of the same part).
  • the UE selects a corresponding preamble sequence to send according to its associated state, and the base station sends corresponding system information according to the received preamble sequence. It is also possible to group system information into system information blocks in a similar manner to LTE, and reserve a preamble sequence or a set of preamble sequences for each system information block (or system information block group). In this manner, a random access collision may occur in the random access step (1) (shown in Figure 1) to select the preamble sequence to be transmitted.
  • Manner 2 Reserve one or a set of preamble sequences for requesting other system information, but other system information types requested by the UE are indicated in the random access message 3. If the RAR message in response to the request for the other system information preamble sequence and the RAR message in response to the general random access procedure preamble sequence are the same, the random access collision may occur in the random access step (1) to select the preamble sequence to be transmitted or It is determined in the random access message 3 that CCCH SDUs from different CCCHs or CCCH SDUs for different purposes or CCCH SDUs containing different RRC messages are carried.
  • a random access collision may occur in the random access step (1) to select to send The leader sequence process.
  • Manner 3 The preamble sequence is shared with an existing LTE (or general or other) random access procedure, and other system information types requested by the UE are indicated in the random access message 3. If the RAR message in response to the request for other system information and the RAR message in response to the general random access procedure are different, then in this manner, a random access collision may occur in the random access step (1) to select the preamble to be transmitted. Sequence process. In this manner, a random access collision may occur in message 3 to determine which of the CCCH SDUs from different CCCHs or CCCH SDUs for different purposes.
  • a collision occurs in the random access step (1) to select a preamble sequence procedure to be transmitted (ie, determining which preamble sequence to transmit), it may be predefined or configured by RRC signaling.
  • the other RRC message (referred to as a dedicated RRC message) includes an RRC connection request message, an RRC connection reestablishment request message, an RRC connection recovery request message, and the like.
  • the MAC entity preferentially includes an RRC message with a high priority or a CCCH SDU or data corresponding to the message in the random access message 3.
  • FIG. 2 shows a flow diagram of a method 200 in a user equipment UE in accordance with an embodiment of the disclosure.
  • step S210 the user equipment UE creates a first common control channel CCCH and a second common control channel CCCH having different priorities for transmitting a dedicated radio resource control RRC message and a system information request message, respectively, the system
  • the information request message is used to request system information other than the minimum system information.
  • step S230 the user equipment UE determines, according to the priorities of the first CCCH and the second CCCH, which CCCH service data unit corresponding to which one of the first CCCH and the second CCCH is included in the random access message 3'Msg3'
  • the SDU either includes the CCCH SDU of the first CCCH and the second CCCH in the random access message 3'Msg3'.
  • step S250 the user equipment UE transmits a random access message 3 'Msg3' to the base station (or delivers the message 3 to the lower layer or physical layer or transport channel UL-SCH for transmission to the base station).
  • the dedicated RRC message includes one or more of the following: an RRC Connection Request message, an RRC Connection Reestablishment Request message, or an RRC Connection Recovery Request message.
  • FIG. 3 shows a flow diagram of a method 300 in a user equipment UE in accordance with an embodiment of the disclosure.
  • step S310 the user equipment UE creates a first CCCH and a second CCCH for respectively transmitting a dedicated RRC message and a request system information message with different priorities.
  • step S330 the user equipment UE selects a preamble sequence corresponding to the higher priority CCCH in the first CCCH and the second CCCH.
  • the user equipment UE transmits the selected preamble sequence to the base station (or delivers message 3 to the lower layer or physical layer or transport channel UL-SCH for transmission to the base station).
  • the dedicated RRC message includes one or more of the following: an RRC Connection Request message, an RRC Connection Reestablishment Request message, or an RRC Connection Recovery Request message.
  • step S330 may include: selecting a preamble sequence from the preamble sequence corresponding to the first CCCH when both the first CCCH and the second CCCH have CCCH SDUs to be transmitted.
  • step S330 may include: selecting a preamble sequence from the preamble sequence corresponding to the second CCCH when both the first CCCH and the second CCCH have CCCH SDUs to be transmitted.
  • the UE selects a preamble sequence according to a predefined rule, for example, according to the message 3. Size selects the leader sequence.
  • the UE includes the CCCH SDU corresponding to the CCCH with the highest priority in the message 3. That is, when constructing the message 3, the UE first determines whether the CCCH with a high priority has a CCCH SDU to be sent, and if so, the CCCH SDU with the high priority is included in the message 3.
  • FIG. 4 shows a flow diagram of a method 400 in a user equipment UE in accordance with an embodiment of the disclosure.
  • step S410 the user equipment UE determines the priority of the transmission system information request message and the dedicated RRC message for requesting system information other than the minimum system information.
  • step S430 according to the priority, when the random access triggered by the request system information message collides with the random access triggered by the dedicated RRC message, the system information request message and the message with high priority in the dedicated RRC message are selected.
  • the corresponding preamble sequence when the random access triggered by the request system information message collides with the random access triggered by the dedicated RRC message, the system information request message and the message with high priority in the dedicated RRC message are selected. The corresponding preamble sequence.
  • the user equipment UE transmits the selected preamble sequence to the base station.
  • the method 400 may also Steps S420, S421, and S422 shown in FIG. 5 are included.
  • step S420 the user equipment UE determines whether there is another RRC procedure other than the RRC procedure requesting system information is triggered or is being executed (ie, there is a dedicated RRC message to be sent or sent but no response message is received).
  • Other RRC procedures other than the RRC procedure for requesting system information described in the present disclosure include one or more of the following procedures: an RRC connection setup procedure, an RRC connection recovery procedure, and an RRC connection reestablishment procedure.
  • step S421 the user equipment UE waits for other RRC procedures that are triggered or are being executed to end, and then initiates an RRC procedure requesting system information. Alternatively, the user equipment UE may terminate the RRC procedure requesting system information.
  • step S422 the user equipment UE performs an RRC procedure requesting system information.
  • the method 400 may further include the method of FIG. Steps S423, S424, and S425 are shown.
  • step S423 the user equipment UE determines whether there is an RRC procedure for requesting system information being executed.
  • step S424 the user equipment UE terminates the RRC procedure of the requesting system information being executed, and performs other RRC procedures other than the RRC procedure for requesting system information, and ends with other RRC procedures other than the RRC procedure for requesting system information. After that, the RRC process of requesting system information is restarted.
  • step S425 the user equipment UE performs other RRC procedures other than the RRC procedure of the triggered request system information.
  • the method 400 may include steps S440, S441 as shown in FIG. And S442.
  • step S440 the user equipment UE determines whether there is another RRC procedure other than the RRC procedure requesting system information is triggered or is being executed.
  • step S441 the user equipment UE terminates other RRC procedures other than the RRC procedure for requesting system information being executed, and performs an RRC procedure requesting system information.
  • step S442 the user equipment UE performs an RRC procedure requesting system information.
  • the method 400 may include as shown in FIG. Steps S443 and S444 and S445.
  • step S443 the user equipment UE determines whether an RRC procedure requesting system information is triggered or is being executed.
  • step S444 the user equipment UE waits for the RRC procedure of the system information to be triggered or being executed to end, and then initiates an RRC procedure other than the RRC procedure for requesting system information.
  • the user equipment UE may also terminate other RRC procedures other than the RRC procedure for requesting system information.
  • step S445 the user equipment UE performs other RRC procedures than the RRC procedure of the triggered request system information.
  • FIG. 9 shows a flow diagram of a method 900 in a user equipment UE in accordance with an embodiment of the disclosure.
  • the user equipment UE determines the priority of the random access triggered by the request system information message and the random access triggered by other events (eg, upper layer or dedicated RRC message, MAC layer itself, PDCCH order, etc.) Level or determine the priority of the random access corresponding preamble sequence triggered by different events (eg, request system information, dedicated RRC message, MAC layer itself, PDCCH order, etc.), the system information request message is used to request other than minimum system information system message.
  • events eg, upper layer or dedicated RRC message, MAC layer itself, PDCCH order, etc.
  • step S930 when the random access triggered by the request system information message collides with the random access triggered by other events, the preamble sequence corresponding to the random access with higher priority is selected or the preamble with higher priority is selected. sequence.
  • the user equipment UE transmits the selected preamble sequence to the base station.
  • the method 900 may further include FIG. 10 Steps S920 and S921 are shown.
  • step S920 the user equipment UE determines whether there is a preamble sequence corresponding to the random access triggered by the request system information message to be transmitted.
  • step S921 the preamble sequence corresponding to the random access triggered by the request system information message is selected. If no, the method 900 returns to step S920.
  • method 900 optionally further includes steps S922, S923, S924, and S925.
  • step S922 the user equipment UE determines whether there is a random access triggered by other events being executed.
  • step S923 the user equipment UE interrupts the random access triggered by other random access trigger messages currently being executed, and selects the preamble sequence corresponding to the random access triggered by the request system information message in step S924.
  • step S925 the preamble sequence corresponding to the random access triggered by the request system information message is selected.
  • the method 900 may further include steps S940 and S941 as shown in FIG.
  • step S940 the user equipment UE determines whether there is random access triggered by other events.
  • step S941 the preamble sequence corresponding to the random access triggered by the other event is selected. If no, method 900 can return to step S940.
  • method 900 also optionally further includes steps S942, S943, and S944.
  • step S942 the user equipment UE determines whether there is a random access triggered by the request system information message being executed.
  • step S943 the random access triggered by the requesting system information message currently being executed is interrupted in step S943, and the preamble sequence corresponding to the random access triggered by the other event is selected in step S944.
  • step S944 the preamble sequence corresponding to the random access triggered by the other event is selected.
  • FIG. 14 shows a flow diagram of a method 1400 in a user equipment UE, in accordance with an embodiment of the disclosure.
  • step S1410 the user equipment UE determines the priority of the random access triggered by the request system information message and the random access triggered by other events, the system information request message is used to request other than the minimum system information. system message.
  • step S1430 when the random access triggered by the request system information message collides with the random access triggered by other events, the message corresponding to the random access with higher priority is selected.
  • step S1450 the user equipment UE transmits the selected message to the base station by including the selected message in the random access message 3 'Msg3'.
  • Scenario 1 The collision occurs at the RRC layer.
  • the RRC layer (or upper layer) will select a corresponding preamble sequence according to the system information requested, and submit or indicate the preamble sequence to the lower layer (or The MAC layer) is sent.
  • the specific process is as follows:
  • the NAS layer (or higher layer) or the RRC layer triggers the UE to request the system information process due to service requirements or due to system information expiration. If there are no other RRC procedures being performed (including but not limited to RRC connection establishment, RRC connection reestablishment, RRC connection recovery) or CCCH SDUs that are not to be sent in the CCCH logical channel, the UE may perform different manners according to the UE requesting other system information. Perform one of the following two embodiments:
  • the UE selects a corresponding preamble sequence according to the system information that needs to be requested, and delivers the preamble sequence to the lower layer (or MAC layer).
  • the UE constructs a system information request message according to the system information that needs to be requested, and delivers the system information request message to the lower layer for transmission.
  • the RRC procedure (or system information request message) for requesting other system information may be pre-defined or configured by RRC signaling with other RRC procedures or RRC connection setup procedures (or RRC connection request message or RRC connection reestablishment request message or RRC connection recovery) The priority of the request message).
  • the RRC procedure (or system information request message) requesting other system information has a lower priority than the other RRC procedure or RRC connection setup procedure (or RRC connection request message or RRC connection reestablishment request message or RRC Connection Recovery Request message). If the NAS layer or the upper layer or the RRC layer triggers the system information request process, the UE determines whether another RRC procedure or an RRC connection setup procedure is triggered or is being executed (ie, an RRC connection request message or an RRC connection reestablishment request message or an RRC connection reestablishment request message is to be executed.
  • the UE may wait for the other RRC procedure or the RRC connection setup procedure that is triggered or is being executed to end, and then initiate an RRC procedure for requesting other system information (ie, construct and send The system information request message or the system information request message is delivered to the lower layer); or the UE may also terminate the RRC procedure for requesting other system information (ie, discard the system information request message); if not, the UE may construct the system information request message and submit it to the lower layer. Send it.
  • the UE determines whether there is an RRC procedure for requesting other system information (eg, the system information request message is to be sent or sent but does not receive the response message); if yes, the UE may Terminating the RRC procedure of the system information request being executed (eg, discarding or deleting the system information request message that has not been sent or if the message has been sent but has not received the response message, then no longer receiving the response message) and performing the priority Higher RRC process.
  • the RRC procedure for requesting other system information (eg, the system information request message is to be sent or sent but does not receive the response message); if yes, the UE may Terminating the RRC procedure of the system information request being executed (eg, discarding or deleting the system information request message that has not been sent or if the message has been sent but has not received the response message, then no longer receiving the response message) and performing the priority Higher RRC process.
  • the RRC process for requesting other system information may be restarted (that is, the system information request message is sent or the system information request message is delivered to the lower layer); if not, the UE may construct a corresponding message and submit the message.
  • the lower layer is transmitted (for example, an RRC Connection Request message or an RRC Connection Reestablishment Request message or an RRC Connection Recovery Request message is constructed and transmitted and delivered to the lower layer for transmission).
  • the RRC procedure (or system information request message) requesting other system information has a higher priority than the other RRC procedure or RRC connection setup procedure (or RRC connection request message or RRC connection reestablishment request message or RRC connection resumption request message) being executed. . If the NAS layer or the upper layer or the RRC layer triggers the system information request procedure, the UE determines whether another RRC procedure or RRC connection setup procedure is triggered or is being executed; if yes, the UE may terminate other RRC procedures or RRC connection setup procedures being performed.
  • the terminated RRC procedure may wait for the system information process to end and then restart; if not, the UE may construct a system information request message and submit it to the lower layer for transmission.
  • the UE determines whether there is a request for the system information procedure to be triggered or is performing an RRC procedure requesting other system information (eg, the system information request message is to be sent or sent but no response message is received) If yes, the UE may wait for the process of requesting the system information to be triggered or being executed to end, and then initiate another RRC procedure or RRC connection setup procedure (ie, construct and send an RRC Connection Request message or an RRC Connection Reestablishment Request message or an RRC connection) Recovering the request message and delivering the message to the lower layer for transmission); or the UE may also terminate the RRC connection setup procedure or other RRC procedure (eg, discard or delete the RRC Connection Request message or the RRC Connection Reestablishment Request message or the RRC connection that has not been sent yet) Recovery request message); if not, the UE may initiate another RRC procedure or RRC connection setup procedure (ie, construct and send an RRC Connection Request message or an RRC Connection
  • terminating the RRC process being performed may also include reconfiguring physical channels and/or reconfiguration.
  • the reconfiguration may be to reapply the default configuration.
  • the RRC connection establishment procedure in the present disclosure may be an RRC connection setup message, an RRC connection reestablishment request message, and an RRC connection setup procedure corresponding to the RRC connection recovery request message.
  • a second CCCH logical channel that is different from the first CCCH logical channel is defined.
  • the first CCCH logical channel (including uplink and downlink CCCH logical channels) is used for transmitting an RRC connection request message, an RRC connection reestablishment request message, an RRC connection recovery request message (the message is transmitted on an uplink CCCH logical channel), and a corresponding response A message (the message is transmitted on the downlink CCCH logical channel) or the like.
  • the second CCCH logical channel (including uplink and/or downlink CCCH logical channels) is used to transmit a system information request message (the message is transmitted in an uplink CCCH logical channel) and/or a corresponding response message (the message is on the downlink) Transmission in the CCCH logical channel). It is also possible not to define a separate downlink CCCH logical channel, but to use an existing downlink logical channel, for example, a first downlink CCCH logical channel. The partial parameters of the second CCCH logical channel are different from the first CCCH logical channel.
  • the priority of the second CCCH logical channel is defined as a value different from the first CCCH logic (for example, 2 or other values), and/or a logical channel group identifier of the second CCCH logical channel.
  • a value eg, 1 or other value
  • a corresponding system information request message or an RRC connection request message or an RRC connection reestablishment request message or an RRC connection recovery request message may be constructed and submitted to the lower layer. transmission.
  • the MAC entity may be based on the priority of the logical channel and/or The logical channel group identity determines which CCCH SDUs corresponding to the CCCH logical channel are included in message 3 or the CCCH SDUs of all CCCH logical channels are included in message 3.
  • the MAC entity may The corresponding preamble sequence is selected based on the logical channel's priority and/or logical channel group identity and submitted to the lower layer transmission.
  • the first CCCH logical channel (or RRC Connection Request message or RRC Connection Reestablishment Request message or RRC Connection Resilience Request message or CCCH SDU corresponding to the first CCCH logical channel) has a higher priority than the second CCCH logical channel (or system)
  • the priority of the information request message or the CCCH SDU corresponding to the second CCCH logical channel when the first CCCH logical channel and the second CCCH logical channel both have CCCH SDUs to be transmitted, and the MAC entity receives the preamble sequence corresponding to the first CCCH logical channel. Select a preamble sequence and submit it to the lower layer for transmission. vice versa.
  • one or more of the following steps are performed in the RRC process of requesting other system information (before the other system information request message is delivered to the lower layer for transmission):
  • the physical channel configuration and/or the semi-persistent scheduling configuration and/or the MAC master configuration corresponding to the first CCCH logical channel may be the same as the configuration corresponding to the second CCCH logical channel.
  • the UE may perform only different steps in the foregoing steps and the second CCCH logical channel configuration, for example, only performing Step (d); conversely, when the CCCH SDU corresponding to the second CCCH logical channel has not been sent yet, the establishment of the RRC connection procedure is triggered (such as an RRC connection request message or an RRC connection reestablishment request message or an RRC connection recovery request message, etc.),
  • the UE may also apply only a configuration different from the first CCCH logical channel configuration without reconfiguring the physical channel and/or semi-persistent scheduling and/or MAC.
  • the priority between the requesting system information message and other RRC messages is defined in accordance with different conditions that trigger the UE to request system information.
  • the other RRC message may include: an RRC connection request message, an RRC connection reestablishment request message, an RRC connection recovery request message, and an RRC connection reconfiguration complete message. For example, if the UE triggered by the locally stored system information expires to send the system information request message (ie, initiates the system information request process), the system information request message has the highest priority, that is, when the system information expires.
  • the priority between the requesting system information message and other RRC messages may also be defined according to a condition for triggering the UE to request system information and a type of the requested system information.
  • the priority between the request system information message and other RRC messages may also be defined according to only the type of system information that needs to be obtained. Some types of system information have higher priority than other RRC messages, and other parts of system information have lower priority than other RRC messages.
  • the priority between different types of system information or the preamble priority corresponding to different types of system information may be defined.
  • priority is given to system information with high priority.
  • the MAC layer conflicts are classified into the following types:
  • Type 1 Requesting system information random access conflicts with contention-based random access
  • the contention-based random access preamble sequence is a preamble sequence selected by the MAC layer, and the contention-based random access may include random access triggered by the following events:
  • the following is an example of random access triggered by the MAC sublayer itself.
  • the embodiment is also applicable to contention-based random access triggered by other events.
  • the preamble sequence for requesting random access of system information is different from the preamble of general random access.
  • the MAC layer selects a corresponding preamble sequence for transmission based on a pre-defined or priority configured by RRC signaling. For example, if the pre-defined request system information random access has a higher priority than the MAC sub-layer triggered random access or general random access, when the collision occurs, the MAC selects the reservation to request the system information for random access.
  • the preamble sequence indicates the physical layer transmission, that is, when the MAC entity selects the preamble sequence for random access, it first determines whether there is a request for system information random access or a preamble sequence corresponding to the request system information to be sent, and if so, selects The preamble sequence requesting random access of the system information and instructing the physical layer to transmit; or when requesting system information random access is triggered or requesting the preamble sequence corresponding to the system information to be sent, if there is a random connection triggered by the MAC sublayer being executed
  • the UE may interrupt the random access or the general random access triggered by the MAC sublayer currently being executed, and start to perform the requesting system information random access or the preamble sequence corresponding to the sending request system information; Defining the priority of requesting system information random access is lower than the random access or general random access triggered by the MAC sublayer.
  • the MAC selects a preamble sequence for general random access and indicates physical layer transmission, that is, when the MAC entity selects a preamble sequence for random access, it first determines whether there is a random connection triggered by the MAC sublayer. Incoming or general random access, if yes, selecting a preamble sequence for general random access and instructing the physical layer to transmit; or if there is a request to perform system information random access, when the MAC sublayer triggers random access or Generally, the random access is triggered, and the UE interrupts the random access of the currently requested system information, and starts to perform random access or general random access triggered by the MAC sublayer or selects a general random access preamble sequence and instructs the physical layer to transmit.
  • requesting system information random access uses the same preamble sequence as general random access.
  • the preamble sequence requesting random access of system information is a general random access contention based preamble sequence set.
  • the MAC entity selects a preamble sequence from the set of preamble sequences that are generally randomly accessed and instructs the physical layer to transmit, in which case the MAC entity resolves the collision in message 3.
  • Pre-defining or configuring other system information request messages ie, CCCH SDU or second CCCH SDU corresponding to the system information message
  • other RRC messages such as an RRC connection request message or an RRC connection reestablishment request message or an RRC connection resuming request
  • the priority of the CCCH SDU or the first CCCH SDU or the data corresponding to the message, the MAC entity includes the message or data with high priority based on the predefined priority in the message 3; or if the message 3 can accommodate multiple pieces
  • the message or data may be included in the message 3 in order of priority from high to low. For example, if other system information request messages are higher than other messages or data, the MAC first determines whether there is a CCCH SDU corresponding to other system information request messages to be sent when constructing message 3. If yes, it is included in message 3. . How to construct message 3 according to the priority of different messages is described in the type three corresponding embodiment.
  • Type 2 requesting system information random access conflicts with non-contention based random access
  • the non-contention based random access may include random access triggered by PDCCH order and/or random access triggered by handover, etc., and the preamble sequence corresponding to the random access is explicitly specified and is not 0000000 or other uses The value indicating that the MAC needs to select the preamble sequence (ie, the preamble sequence is not selected by the MAC entity).
  • the following embodiment is exemplified by non-contention based random access triggered by PDCCH order, which is also applicable to non-contention based random access triggered by other events.
  • the preamble sequence for requesting random access of system information is different from the preamble sequence of general random access.
  • the MAC layer selects a corresponding preamble sequence based on a pre-defined or priority configured by RRC signaling and instructs the physical layer to transmit.
  • the MAC selects to reserve a preamble sequence requesting random access of the system information and instructs the physical layer to perform Sending, that is, when the MAC entity selects the preamble sequence for random access, it first determines whether there is a request for system information random access or a preamble sequence for requesting system information to be sent, and if so, selecting to request system information to be randomized Accessing the preamble sequence and instructing the physical layer to transmit; or if the PDCCH order triggered random access is being performed, requesting system information random access is triggered or requesting the system information preamble sequence to be sent, the UE interrupts the currently executing PDCCH order trigger Random access, and start to perform request system information random access or instruct the physical layer to send a request system information preamble sequence; if the predefined request system information random access priority is lower than the PDCCH order triggered random access
  • the MAC entity when the MAC entity selects the preamble sequence for random access, it first determines whether there is random access triggered by the PDCCH order, and if so, selects the preamble sequence explicitly specified in the PDCCH order and instructs the physical layer to transmit; or if Performing request system information random access, PDCCH order triggers random access, the UE interrupts the currently requested request system information random access, and starts to perform random access triggered by PDCCH order or selects the preamble sequence explicitly specified in the PDCCH order and Instructs the physical layer to send.
  • the foregoing embodiment is also applicable to a scenario in which requesting system information random access uses the same preamble sequence as general random access.
  • the MAC entity selects a preamble sequence to transmit from the preamble sequence set of the general random access.
  • the preamble sequence requesting random access of system information is a general random access contention based preamble sequence set.
  • the MAC entity selects a preamble sequence from the general random access contention-based preamble sequence and instructs the physical layer to send
  • Type 3 Random access triggered by the MAC sublayer, message 3 conflicts
  • the random access is triggered by the MAC sublayer, and when the UE constructs the message 3, there are multiple messages or data to be sent, and the message or data may be from different CCCH logical channels or the same CCCH logical channel (
  • the identifier may be carried to indicate a message type or a message priority, so that the MAC distinguishes different messages or prioritizes different messages.
  • the message 3 can only carry one type of message or data. For example, if the message 3 carries the CCCH SDU corresponding to the other system information request message, the message cannot be carried.
  • the priority of different messages or data or CCCH SDU or CCCH logical channels can be pre-defined or configured by RRC signaling, and the UE contains the highest priority message or data or CCCH SDU in message 3. If the priority of the CCCH SDU or the message corresponding to the other system information request message is higher than other CCCH SDUs or messages or data, the MAC entity first determines whether there is a CCCH SDU corresponding to the system information request message to be sent when constructing the message 3.
  • message if any, includes the content in message 3; if not, the CCCH SDU or message or data corresponding to the other CCCH is included in message 3. If the CCCH SDU or message priority corresponding to the other system information request message is lower than other CCCH SDUs or messages or data, the MAC entity first determines whether there are CCCH SDUs or messages corresponding to other CCCHs to be sent when constructing message 3. Or data, if any, contains the CCCH SDU or message or data corresponding to the other CCCH in message 3; if not, the content is included in message 3.
  • the message 3 may carry multiple types of messages or data. For example, if the uplink grant (UL Grant) carried in the RAR is large enough, the message 3 may carry multiple messages or CCCH SDUs or data and These messages or CCCH SDUs or data are included in message 3 in a predefined order. For example, it is assumed that the CCCH SDU corresponding to the other system information request message is requested to be placed before the corresponding CCCH SDU such as the RRC connection request message or the RRC connection reestablishment request message or the RRC connection reestablishment request message, and vice versa.
  • UL Grant uplink grant
  • predefined parameters or rules or priorities described in this disclosure may also be configured through RRC signaling.
  • FIG. 15 shows a block diagram of a UE 1500 in accordance with an embodiment of the disclosure.
  • the UE 1500 includes a channel creation unit 1510, a determination unit 1530, and a transmission unit 1550.
  • the channel creating unit 1510 is configured to create a first common control channel CCCH and a second common control channel CCCH having different priorities for transmitting a dedicated radio resource control RRC message and a system information request message, respectively, the system information request message is used for Request system information other than minimum system information.
  • the determining unit 1530 is configured to determine, according to the priorities of the first CCCH and the second CCCH, which CCCH service data unit SDU corresponding to which one of the first CCCH and the second CCCH is included in the random access message 3'Msg3' Or the CCCH SDUs of the first CCCH and the second CCCH are both included in the random access message 3'Msg3'.
  • Transmitting unit 1550 is configured to transmit random access message 3 'Msg3' to the base station.
  • the dedicated RRC message includes one or more of the following: an RRC Connection Request message, an RRC Connection Reestablishment Request message, or an RRC Connection Recovery Request message.
  • FIG. 16 shows a block diagram of a UE 1600 in accordance with an embodiment of the disclosure.
  • the UE 1600 includes a channel creation unit 1610, a selection unit 1630, and a transmission unit 1650.
  • the channel creation unit 1610 is configured to create a first CCCH and a second CCCH for separately transmitting the dedicated RRC message and the request system information message with different priorities.
  • the selecting unit 1630 is configured to select a preamble sequence corresponding to the CCCH of the higher priority in the first CCCH and the second CCCH.
  • Transmitting unit 1650 is configured to transmit the selected preamble sequence to the base station.
  • the dedicated RRC message includes one or more of the following: an RRC Connection Request message, an RRC Connection Reestablishment Request message, or an RRC Connection Recovery Request message.
  • the first CCCH has a higher priority than the second CCCH.
  • the selecting unit 1630 is further configured to select a preamble sequence from the preamble sequence corresponding to the first CCCH when both the first CCCH and the second CCCH have CCCH SDUs to be transmitted.
  • FIG. 17 shows a block diagram of a UE 1700 in accordance with an embodiment of the present disclosure.
  • the UE 1700 includes a determining unit 1710, a selecting unit 1730, and a transmitting unit 1750.
  • the determining unit 1710 is configured to determine a priority of the transmission system information request message and the dedicated RRC message for requesting system information other than the minimum system information.
  • the selecting unit 1730 is configured to select a high priority in the system information request message and the dedicated RRC message when the random access triggered by the request system information message collides with the random access triggered by the dedicated RRC message according to the priority.
  • Transmitting unit 1750 is configured to transmit the selected preamble sequence to the base station.
  • the priority of the requesting system information message is lower than the priority of the dedicated RRC message, and the RRC procedure requesting system information is triggered.
  • the UE 1700 further includes: a first determining unit 1720 configured to determine whether another RRC procedure other than the RRC procedure requesting system information is triggered or is being executed; and the first RRC process control unit 1721, Is configured to: if another RRC procedure other than the RRC procedure requesting system information is triggered or is being executed, wait for the other RRC procedure triggered or being executed to end, and then start the RRC procedure of requesting system information; or terminate the request system The RRC process of information.
  • the first RRC process control unit 1721 is further configured to perform an RRC procedure requesting system information if another RRC procedure other than the RRC procedure requesting system information is triggered or is being executed.
  • the priority of the requesting system information message is lower than the priority of the dedicated message, and other RRC procedures other than the RRC procedure requesting system information are triggered.
  • the UE 1700 further includes: a second determining unit 1722 configured to determine whether an RRC procedure for requesting system information is being executed; and a second RRC process control unit 1723 configured to: if there is a request The RRC procedure of the system information is being executed, the RRC procedure of the requesting system information being executed is terminated, and other RRC procedures other than the RRC procedure requesting the system information are performed, and after the RRC procedure other than the RRC procedure of requesting the system information ends, Restart the RRC process requesting system information.
  • the priority of the requesting system information message is higher than the priority of the dedicated RRC message, and the RRC procedure requesting system information is triggered.
  • the UE 1700 further includes: a third determining unit 1724 configured to determine whether another RRC procedure other than the RRC procedure requesting system information is triggered or is being executed; and the third RRC process control unit 1725 And configured to: if other RRC procedures other than the RRC procedure requesting system information are triggered or are being executed, terminate other RRC procedures other than the RRC procedure of the requesting system information being executed, and perform an RRC procedure of requesting system information.
  • the third RRC process control unit 1725 is further configured to perform an RRC procedure requesting system information if another RRC procedure other than the RRC procedure requesting system information is triggered or is being executed.
  • the priority of the requesting system information message is higher than the priority of the dedicated RRC message, and other RRC procedures other than the RRC procedure requesting system information are triggered.
  • the UE 1700 further includes: a fourth determining unit 1726 configured to determine whether an RRC procedure for requesting system information is triggered or is being executed; and the fourth RRC process control unit 1727 is configured to: If the RRC procedure for requesting system information is triggered or is being executed, the RRC procedure of the requested system information that is triggered or being executed is terminated, and then another RRC procedure other than the RRC procedure for requesting system information is started; or the request system information is terminated. Other RRC procedures outside the RRC process.
  • first judging unit 1720, the second judging unit 1722, the third judging unit 1724, and the fourth judging unit 1726 may be combined into a single unit.
  • first RRC process control unit 1721, the second RRC process control unit 1723, the third RRC process control unit 1725, and the fourth RRC process control unit 1727 may also be incorporated into a single unit.
  • FIG. 18 shows a block diagram of a UE 1800 in accordance with an embodiment of the present disclosure.
  • the UE 1800 includes a determining unit 1810, a selecting unit 1830, and a transmitting unit 1850.
  • the determining unit 1810 is configured to determine a priority of random access triggered by the request system information message and random access triggered by other events, the system information request message being used to request system information other than the minimum system information.
  • the selecting unit 1830 is configured to select a preamble sequence corresponding to the higher priority random access when the random access triggered by the request system information message collides with the random access triggered by other events.
  • Transmitting unit 1850 is configured to transmit the selected preamble sequence to the base station.
  • the random access triggered by the requesting system information message is higher than the priority of the random access triggered by other events.
  • the UE 1800 further includes: a first determining unit 1820, configured to determine whether there is a preamble sequence corresponding to the random access triggered by the request system information message to be sent.
  • the selecting unit 1830 is further configured to: if there is a preamble sequence corresponding to the random access triggered by the request system information message to be sent, select a preamble sequence corresponding to the random access triggered by the request system information message.
  • the first determining unit 1820 is further configured to determine whether there is a random access triggered by other events
  • the UE 1800 further includes: a first random access interrupting unit 1821 configured to: There is a random access triggered by other events that is being executed, and the random access currently triggered by other random access trigger messages is interrupted.
  • the selection unit 1820 is further configured to select a preamble sequence corresponding to the random access triggered by the request system information message.
  • the random access triggered by the requesting system information message is lower than the priority of the random access triggered by other events.
  • the UE 1800 further includes: a second determining unit 1822 configured to determine whether there is random access triggered by other events.
  • the selection unit 1820 is further configured to select a preamble sequence corresponding to the random access triggered by the other event if there is random access triggered by other events.
  • the second determining unit 1822 is further configured to determine whether there is a random access triggered by the requesting system information message
  • the UE 1800 further includes: a second random access interrupting unit 1823 configured to: If there is a random access being triggered by the requesting system information message being executed, the random access triggered by the requesting system information message currently being executed is interrupted.
  • selection unit 1820 is also configured to select a preamble sequence corresponding to random access triggered by other events.
  • first judging unit 1820 and the second judging unit 1822 may be combined into a single unit.
  • first random access interrupt unit 1821 and the second random access interrupt unit 1823 may also be combined into a single unit.
  • FIG. 19 shows a block diagram of a UE 1900 in accordance with an embodiment of the disclosure.
  • the UE 1900 includes a determining unit 1910, a selecting unit 1930, and a transmitting unit 1950.
  • the determining unit 1910 is configured to determine a priority of random access triggered by the request system information message and random access triggered by other events, the system information request message being used to request system information other than the minimum system information.
  • the selecting unit 1930 is configured to select a message corresponding to the higher priority random access when the random access triggered by the request system information message collides with the random access triggered by the other event.
  • Transmitting unit 1950 is configured to transmit the selected message to the base station by including the selected message in random access message 3 'Msg3'.
  • 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 program for realizing the functions of the embodiments of the present invention can be recorded on a computer readable recording medium.
  • the corresponding functions can be realized by causing a computer system to read programs recorded on the recording medium and execute the programs.
  • the so-called "computer system” herein may be a computer system embedded in the device, and may include an operating system or hardware (such as a peripheral device).
  • the "computer readable recording medium” may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium of a short-term dynamic storage program, or any other recording medium readable by a computer.
  • circuitry e.g., monolithic or multi-chip integrated circuits.
  • Circuitry designed to perform the functions described in this specification can include general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete Gate or transistor logic, discrete hardware components, or any combination of the above.
  • DSPs digital signal processors
  • ASICs application specific integrated circuits
  • FPGAs field programmable gate arrays
  • a general purpose processor may be a microprocessor or any existing processor, controller, microcontroller, or state machine.
  • the above circuit may be a digital circuit or an analog circuit.
  • One or more embodiments of the present invention may also be implemented using these new integrated circuit technologies in the context of new integrated circuit technologies that have replaced existing integrated circuits due to advances in semiconductor technology.
  • the present invention is not limited to the above embodiment. Although various examples of the embodiments have been described, the invention is not limited thereto.
  • Fixed or non-mobile electronic devices installed indoors or outdoors can be used as terminal devices or communication devices such as AV devices, kitchen devices, cleaning devices, air conditioners, office equipment, vending machines, and other home appliances.

Landscapes

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

Abstract

本公开提供了一种用户设备UE中的方法，包括：创建具有不同优先级的第一公共控制信道CCCH和第二公共控制信道CCCH分别用于传输专用无线资源控制RRC消息和系统信息请求消息，所述系统信息请求消息用于请求最小系统信息以外的系统信息；根据第一CCCH和第二CCCH的优先级，确定在随机接入消息3'Msg3'中包含第一CCCH和第二CCCH中的哪一个CCCH所对应的CCCH服务数据单元SDU或者将第一CCCH和第二CCCH的CCCH SDU都包含在随机接入消息3'Msg3'中；以及将随机接入消息3'Msg3'发送到基站。

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的所有应用场景、需求和部署环境。为了更好地节能减排，在该项目的初期要求中提出了要避免网络侧重复发送不必要的信息，其中包括避免周期性地发送所有系统信息(System Information，记为SI)。
本发明解决采用随机接入过程请求系统信息与一般随机接入发生冲突的问题。
发明内容
根据本公开的第一方面，提供了一种用户设备UE中的方法。该方法包括：创建具有不同优先级的第一公共控制信道CCCH和第二公共控制信道CCCH分别用于传输专用无线资源控制RRC消息和系统信息请求消息，所述系统信息请求消息用于请求最小系统信息以外的系统信息；根据第一CCCH和第二CCCH的优先级，确定在随机接入消息3‘Msg3’中包含第一CCCH和第二CCCH中的哪一个CCCH所对应的CCCH服务数据单元SDU或者将第一CCCH和第二CCCH的CCCH SDU都包含在随机接入消息3‘Msg3’中；以及将随机接入消息3‘Msg3’发送到基站。
在一个实施例中，所述专用RRC消息包括以下一个或多个：RRC连接请求消息、RRC连接重建请求消息或RRC连接恢复请求消息。
根据本公开的第二方面，提供了一种用户设备UE。该UE包括：信道 创建单元，被配置为创建具有不同优先级的第一公共控制信道CCCH和第二公共控制信道CCCH分别用于传输专用无线资源控制RRC消息和系统信息请求消息，所述系统信息请求消息用于请求最小系统信息以外的系统信息；确定单元，被配置为根据第一CCCH和第二CCCH的优先级，确定在随机接入消息3‘Msg3’中包含第一CCCH和第二CCCH中的哪一个CCCH所对应的CCCH服务数据单元SDU或者将第一CCCH和第二CCCH的CCCH SDU都包含在随机接入消息3‘Msg3’中；以及发送单元，被配置为将随机接入消息3‘Msg3’发送到基站。
在一个实施例中，所述专用RRC消息包括以下一个或多个：RRC连接请求消息、RRC连接重建请求消息或RRC连接恢复请求消息。
根据本公开的第三方面，提供了一种用户设备UE中的方法。该方法包括：创建第一CCCH和第二CCCH用于以不同的优先级分别传输专用RRC消息和请求系统信息消息；选择与第一CCCH和第二CCCH中优先级较高的CCCH所对应的前导序列；以及将所选择的前导序列发送到基站。
在一个实施例中，所述专用RRC消息包括以下一个或多个：RRC连接请求消息、RRC连接重建请求消息或RRC连接恢复请求消息。
根据本公开的第四方面，提供了一种用户设备UE。该UE包括：信道创建单元，被配置为创建第一CCCH和第二CCCH用于以不同的优先级分别传输专用RRC消息和请求系统信息消息；选择单元，被配置为选择与第一CCCH和第二CCCH中优先级较高的CCCH所对应的前导序列；以及发送单元，被配置为将所选择的前导序列发送到基站。
在一个实施例中，所述专用RRC消息包括以下一个或多个：RRC连接请求消息、RRC连接重建请求消息或RRC连接恢复请求消息。
根据本公开的第五方面，提供了一种用户设备UE中的方法。该方法包括：确定传输系统信息请求消息和专用RRC消息的优先级，所述系统信息请求消息用于请求最小系统信息以外的系统信息；根据所述优先级，在由请求系统信息消息触发的随机接入与由专用RRC消息触发的随机接入发生冲突时，选择系统信息请求消息和专用RRC消息中优先级高的消息所对应的前导序列；以及将所选择的前导序列发送到基站。
在一个实施例中，如果请求系统信息消息的优先级低于专用RRC消息的优先级，并且如果请求系统信息的RRC过程被触发，则所述方法还包 括：判断是否有请求系统信息的RRC过程以外的其他RRC过程被触发或正在执行；以及如果有请求系统信息的RRC过程以外的其他RRC过程被触发或正在执行，则等待被触发或正在执行的其他RRC过程结束，然后再启动请求系统信息的RRC过程；或者终止请求系统信息的RRC过程。
在一个实施例中，如果请求系统信息消息的优先级低于专用消息的优先级，并且如果请求系统信息的RRC过程以外的其他RRC过程被触发，则所述方法还包括：判断是否有请求系统信息的RRC过程正在执行；以及如果有请求系统信息的RRC过程正在执行，则终止正在执行的请求系统信息的RRC过程，并执行请求系统信息的RRC过程以外的其他RRC过程，以及在请求系统信息的RRC过程以外的其他RRC过程结束之后，重新启动请求系统信息的RRC过程。
在一个实施例中，如果请求系统信息消息的优先级高于专用RRC消息的优先级，并且如果请求系统信息的RRC过程被触发，则所述方法还包括：判断是否有请求系统信息的RRC过程以外的其他RRC过程被触发或正在执行；以及如果有请求系统信息的RRC过程以外的其他RRC过程被触发或正在执行，则终止正在执行的请求系统信息的RRC过程以外的其他RRC过程，并执行请求系统信息的RRC过程。
在一个实施例中，如果请求系统信息消息的优先级高于专用RRC消息的优先级，并且如果请求系统信息的RRC过程以外的其他RRC过程被触发，则所述方法还包括：判断是否有请求系统信息的RRC过程被触发或正在执行；以及如果有请求系统信息的RRC过程被触发或正在执行，则等待所述被触发或正在执行的请求系统信息的RRC过程结束，然后启动请求系统信息的RRC过程以外的其他RRC过程；或者终止请求系统信息的RRC过程以外的其他RRC过程。
根据本公开的第六方面，提供了一种用户设备UE。该UE包括：确定单元，被配置为确定传输系统信息请求消息和专用RRC消息的优先级，所述系统信息请求消息用于请求最小系统信息以外的系统信息；选择单元，被配置为根据所述优先级，在由请求系统信息消息触发的随机接入与由专用RRC消息触发的随机接入发生冲突时，选择系统信息请求消息和专用RRC消息中优先级高的消息所对应的前导序列；以及发送单元，被配置为将所选择的前导序列发送到基站。
在一个实施例中，如果请求系统信息消息的优先级低于专用RRC消息的优先级，并且如果请求系统信息的RRC过程被触发，则所述UE还包括：第一判断单元，被配置为判断是否有请求系统信息的RRC过程以外的其他RRC过程被触发或正在执行；以及第一RRC过程控制单元，被配置为：如果有请求系统信息的RRC过程以外的其他RRC过程被触发或正在执行，则等待被触发或正在执行的其他RRC过程结束，然后再启动请求系统信息的RRC过程；或者终止请求系统信息的RRC过程。
在一个实施例中，如果请求系统信息消息的优先级低于专用消息的优先级，并且如果请求系统信息的RRC过程以外的其他RRC过程被触发，则所述UE还包括：第二判断单元，被配置为判断是否有请求系统信息的RRC过程正在执行；以及第二RRC过程控制单元，被配置为：如果有请求系统信息的RRC过程正在执行，则终止正在执行的请求系统信息的RRC过程，并执行请求系统信息的RRC过程以外的其他RRC过程，以及在请求系统信息的RRC过程以外的其他RRC过程结束之后，重新启动请求系统信息的RRC过程。
在一个实施例中，如果请求系统信息消息的优先级高于专用RRC消息的优先级，并且如果请求系统信息的RRC过程被触发，则所述UE还包括：第三判断单元，被配置为判断是否有请求系统信息的RRC过程以外的其他RRC过程被触发或正在执行；以及第三RRC过程控制单元，被配置为：如果有请求系统信息的RRC过程以外的其他RRC过程被触发或正在执行，则终止正在执行的请求系统信息的RRC过程以外的其他RRC过程，并执行请求系统信息的RRC过程。
在一个实施例中，如果请求系统信息消息的优先级高于专用RRC消息的优先级，并且如果请求系统信息的RRC过程以外的其他RRC过程被触发，则所述UE还包括：第四判断单元，被配置为判断是否有请求系统信息的RRC过程被触发或正在执行；第四RRC过程控制单元，被配置为：如果有请求系统信息的RRC过程被触发或正在执行，则等待所述被触发或正在执行的请求系统信息的RRC过程结束，然后启动请求系统信息的RRC过程以外的其他RRC过程；或者终止请求系统信息的RRC过程以外的其他RRC过程。
根据本公开的第七方面，提供了一种用户设备UE中的方法。该方法包 括：确定由请求系统信息消息触发的随机接入与由其他事件触发的随机接入的优先级，所述系统信息请求消息用于请求最小系统信息以外的系统信息；在由请求系统信息消息触发的随机接入与由其他事件触发的随机接入发生冲突时，选择优先级较高的随机接入所对应的前导序列；以及将所选择的前导序列发送到基站。
在一个实施例中，如果由请求系统信息消息触发的随机接入高于由其他事件触发的随机接入的优先级，则所述方法还包括：判断是否存在由请求系统信息消息触发的随机接入对应的前导序列待发送；以及如果存在由请求系统信息消息触发的随机接入对应的前导序列待发送，则选择由请求系统信息消息触发的随机接入所对应的前导序列。
在一个实施例中，该方法还包括：判断是否有正在执行的由其他事件触发的随机接入；如果有正在执行的由其他事件触发的随机接入，则中断当前正在执行的由其他随机接入触发消息触发的随机接入；以及选择由请求系统信息消息触发的随机接入所对应的前导序列。
在一个实施例中，如果由请求系统信息消息触发的随机接入低于由其他事件触发的随机接入的优先级，则所述方法还包括：判断是否存在由其他事件触发的随机接入；以及如果存在由其他事件触发的随机接入，则选择由其他事件触发的随机接入所对应的前导序列。
在一个实施例中，该方法还包括：判断是否有正在执行的由请求系统信息消息触发的随机接入；如果有正在执行的由请求系统信息消息触发的随机接入，则中断当前正在执行的由请求系统信息消息触发的随机接入；以及选择由其他事件触发的随机接入所对应的前导序列。
根据本公开的第八方面，提供了一种用户设备UE。该UE包括：确定单元，被配置为确定由请求系统信息消息触发的随机接入与由其他事件触发的随机接入的优先级，所述系统信息请求消息用于请求最小系统信息以外的系统信息；选择单元，被配置为在由请求系统信息消息触发的随机接入与由其他事件触发的随机接入发生冲突时，选择优先级较高的随机接入所对应的前导序列；以及发送单元，被配置为将所选择的前导序列发送到基站。
在一个实施例中，如果由请求系统信息消息触发的随机接入高于由其他事件触发的随机接入的优先级，则所述UE还包括：第一判断单元，被 配置为判断是否存在由请求系统信息消息触发的随机接入对应的前导序列待发送，其中，所述选择单元还被配置为：如果存在由请求系统信息消息触发的随机接入对应的前导序列待发送，则选择由请求系统信息消息触发的随机接入所对应的前导序列。
在一个实施例中，所述第一判断单元还被配置为判断是否有正在执行的由其他事件触发的随机接入，所述UE还包括：第一随机接入中断单元，被配置为：如果有正在执行的由其他事件触发的随机接入，则中断当前正在执行的由其他随机接入触发消息触发的随机接入，其中，所述选择单元还被配置为选择由请求系统信息消息触发的随机接入所对应的前导序列。
在一个实施例中，如果由请求系统信息消息触发的随机接入低于由其他事件触发的随机接入的优先级，则所述UE还包括：第二判断单元，被配置为判断是否存在由其他事件触发的随机接入，其中，所述选择单元还被配置为：如果存在由其他事件触发的随机接入，则选择由其他事件触发的随机接入所对应的前导序列。
在一个实施例中，所述第二判断单元还被配置为判断是否有正在执行的由请求系统信息消息触发的随机接入，所述UE还包括：第二随机接入中断单元，被配置为：如果有正在执行的由请求系统信息消息触发的随机接入，则中断当前正在执行的由请求系统信息消息触发的随机接入，以及其中，所述选择单元还被配置为选择由其他事件触发的随机接入所对应的前导序列。
根据本公开的第九方面，提供了一种用户设备UE中的方法。该方法包括：确定由请求系统信息消息触发的随机接入与由其他事件触发的随机接入的优先级，所述系统信息请求消息用于请求最小系统信息以外的系统信息；在由请求系统信息消息触发的随机接入与由其他事件触发的随机接入发生冲突时，选择优先级较高的随机接入所对应的消息；以及通过在随机接入消息3‘Msg3’中包含所选择的消息，将所选择的消息发送到基站。
根据本公开的第十方面，提供了一种用户设备UE。该UE包括：确定单元，被配置为确定由请求系统信息消息触发的随机接入与由其他事件触发的随机接入的优先级，所述系统信息请求消息用于请求最小系统信息以外的系统信息；选择单元，被配置为：在由请求系统信息消息触发的随机接入与由其他事件触发的随机接入发生冲突时，选择优先级较高的随机接 入所对应的消息；以及发送单元，被配置为：通过在随机接入消息3‘Msg3’中包含所选择的消息，将所选择的消息发送到基站。
附图说明
通过下文结合附图的详细描述，本公开的上述和其它特征将会变得更加明显，其中：
图1示意性地示出了现有的随机接入过程；
图2示出了根据本公开实施例的用户设备UE中的方法200的流程图；
图3示出了根据本公开实施例的用户设备UE中的方法300的流程图；
图4-8示出了根据本公开实施例的用户设备UE中的方法400的流程图；
图9-13示出了根据本公开实施例的用户设备UE中的方法900的流程图；
图14示出了根据本公开实施例的用户设备UE中的方法1400的流程图；
图15示出了根据本公开实施例的UE 1500的框图；
图16示出了根据本公开实施例的UE 1600的框图；
图17示出了根据本公开实施例的UE 1700的框图；
图18示出了根据本公开实施例的UE 1800的框图；以及
图19示出了根据本公开实施例的UE 1900的框图。
具体实施方式
下面结合附图和具体实施方式对本公开进行详细阐述。应当注意，本公开不应局限于下文所述的具体实施方式。另外，为了简便起见，省略了对与本公开没有直接关联的公知技术的详细描述，以防止对本公开的理解造成混淆。
在现有的LTE系统中，为了保证LTE用户设备(UE)的正常接入，基站(eNB)会周期性地广播接入层以及非接入层的信息，统称为系统信息。目前LTE系统下，系统信息分为一个主系统信息块MasterInformationBlock(MIB)和若干个系统信息块SystemInformationBlocks(SIBs)，用来承载不同的 内容。截止目前为止LTE定义的SIB多达20种。MIB上携带了用于获取小区的基本信息的必需的以及最频繁发送的参数，SIB1中包含用来判断某小区是否适合用于小区选择的参数以及其他SIB的时域调度信息。MIB和SIB1在预定义的时间周期内发送。其他具有相同调度周期的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等，反之，则不需要。
在3GPP RAN2 95次会议上，达成将NR系统信息分成两类，一类是周期性广播的系统信息(称为最小系统信息，Minimum SI)，这类系统信息中可以包含最重要的或获取其他系统信息所必需的或为绝大多数UE所需的系统信息，例如UE随机接入前所必需获取的参数。另一类是不包含在最小系统信息中的系统信息(称为其他系统信息，other SI)。所述其他系统信息可以不周期性广播，而是在UE请求时或网络决定发送时才发送。
如图1所示，现有的随机接入过程包含以下四个步骤：(1)发送选定的前导序列(preamble)；(2)接收随机接入应答RAR；(3)发送消息3(即Message 3)；(4)接收竞争解决消息。根据UE当前状态，消息3的内容不同，消息3可以包含小区无线网络临时标识符(C-RNTI)媒体访问入控制(MAC)控制单元(CE)或公共控制信道(CCCH)服务数据单元(SDU)。 如果是基于非竞争的随机接入过程，则仅包含前个步骤。如果是基于竞争的随机接入过程，则包含所述全部四个步骤。
UE可以通过随机接入过程请求其他系统信息。目前部分公司主张通过随机接入过程步骤(1)请求系统信息，即为不同的其他系统信息(或系统信息块)定义不同的前导序列，UE通过发送对应的前导序列来请求相关的其他系统信息。还有些公司主张通过随机接入过程步骤(3)请求系统信息，即在消息3中携带UE所要请求的系统信息类型(或系统信息块类型)。
现有的LTE系统规定，在一个MAC实体中，每个时刻只能执行一个随机接入过程。如果UE采用随机接入过程来请求系统信息，那么有可能与其他事件触发的随机接入过程发生冲突。所述冲突可以发生在随机接入过程步骤(1)或步骤(3)。如何解决由请求其他系统信息触发的随机接入过程与其他事件触发的随机接入过程之间的冲突是需要解决的问题。
下面描述本公开中用到的术语，除特别说明外，本公开涉及的术语都采用此处定义。
RRC：Radio Resource Control，无线资源控制；
MAC：Medium Access Control，媒体访问控制；
CCCH：Common Control Channel，公共控制信道，所述信道可以用于在UE和基站间还未确定关联时(例如在建立RRC连接过程中)发送控制信息的上行或下行信道；
UL-SCH：Uplink Shared Channel，上行共享信道；所述信道具有以下一项或多项特征：可能使用波束赋形(即beamforming)、通过变换发送功率、调制和编码支持动态链路自适应、支持HARQ、支持动态和半静态资源分配；
SDU：Service Data Unit，服务数据单元；
RRC连接请求消息：RRCConnectionRequest，用于请求建立RRC连接的消息；
RRC连接重建请求消息：rrcConnectionReestablishmentRequest，用于请求重建RRC连接的消息；
RRC连接恢复请求消息：RRCConnectionResumeRequest，用于请求恢 复被挂起的RRC连接的消息；
RRC连接态：RRC_CONNECTED，当RRC连接建立后，UE处于RRC_CONNECTED状态；
RRC非激活态：RRC_INACTIVE，在此状态下，至少一个基站(记为eNB)保存UE的接入层上下文(AS Context)信息，且可以保持5G-RAN和5G-CN(即5G-RAN所连接的核心网)间的连接；
RRC空闲态：RRC_IDLE，没有建立RRC连接(和/或UE不处于RRC_INACTIVE态或基站或5G-RAN或EUTRAN中未保存用户上下文信息)时，UE处于RRC_IDLE态；
PDCCH order：对应某种特定格式的DCI(例如DCI format 1A)且用于触发随机接入过程，所述DCI中携带用于随机接入的相关参数；
Msg3：随机接入消息3，所述消息随机接入过程的一部分，是UE发送给基站的消息。根据UE当前状态，消息3的内容可能不同。消息3来自上层或RRC层，可以包含C-RNTI MAC CE或CCCH SDU和/或UE冲突解决标识且在上行共享信道UL-SCH上传输。
当采用4步方式执行随机接入时，消息3为随机接入的第三步所发送的消息；当采用2步方式执行随机接入时，消息3在随机接入第一步发送。所述4步方式执行随机接入是指在包含4个步骤的随机接入：第一步中UE向基站发送前导序列；第二步UE接收来自基站的随机接入应答RAR；第三步UE向基站发送消息3；第四步UE接收来自基站的用于竞争解决的消息4，根据消息3所携带的内容不同，消息4也不同。需要说明的是，如果是基于非竞争的随机接入，则不需要用于竞争解决的消息3和消息4。所述2步方式执行随机接入是指在包含2个步骤的随机接入：在第一步中UE向基站发送前导序列和4步方式执行随机接入消息3中携带的全部或部分信息，还可以发送其他未携带在消息3中的信息；在第二步中，UE接收来自基站的应答。
本发明中所述消息3可以指4步随机接入中步骤3所发送的消息，也可以指2步随机接入中步骤2所发送的消息。本公开以4步随机接入方式请求系统信息为例进行描述，本公开也适用于2步随机接入方式请求系统信息。
本公开将随机接入分为两类：一类是请求系统信息触发的随机接入，此类随机接入是由于上层(例如RRC层)请求其他系统信息触发的，在本公开中称之为请求系统信息随机接入；另一类是除此之外的其他事件触发的随机接入，在本公开中称之为一般随机接入。本公开的实施例也适用于其他命名方式。本公开将请求其他系统信息的消息称为系统信息请求消息。本公开将包含系统信息请求消息对应的CCCH SDU的消息也称为消息3，但是本公开也适用于采用其他命名方式。
下面先介绍UE请求其他系统信息可以采用的三种方式：
方式一：将不同的其他系统信息映射到不同的前导序列，UE通过发送对应的前导序列来请求相关的其他系统信息。例如，处于不同状态的UE所需要的系统信息可能不同。根据UE在不同状态所需要的系统信息，将其他系统信息进行分类，并定义(或关联)对应的前导序列(或前导序列组)。目前，NR系统中UE状态可以是RRC连接态，RRC空闲态，RRC非激活态。相应地，可以将其他系统信息按照UE在相应状态所需要的系统信息分类(不同状态可能对应部分相同的其他系统信息)。UE根据其所属状态选择对应的前导序列发送，基站根据接收到的前导序列发送对应的其他系统信息。也可以按照LTE类似的方式，将系统信息分组得到系统信息块，为每个系统信息块(或系统信息块组)预留一个前导序列或一组前导序列。在这种方式中，随机接入冲突可能发生在随机接入步骤(1)(如图1所示)中选择要发送的前导序列过程。
方式二：预留一个或一组前导序列用于请求其他系统信息，但UE请求的其他系统信息类型在随机接入消息3中指示。如果响应于请求其他系统信息前导序列的RAR消息和响应于一般随机接入过程前导序列的RAR消息相同，则随机接入冲突可能发生在随机接入步骤(1)选择要发送的前导序列过程或者在随机接入消息3中确定携带来自不同CCCH的CCCH SDU或用于不同目的的CCCH SDU或包含不同RRC消息的CCCH SDU。
如果响应于请求其他系统信息的RAR消息和响应于现有LTE(或一般或其他)随机接入过程的RAR消息不相同，则随机接入冲突可能发生在随机接入步骤(1)选择要发送的前导序列过程。
方式三：与现有LTE(或一般或其他)随机接入过程共享前导序列，UE请求的其他系统信息类型在随机接入消息3中指示。如果响应于请求其 他系统信息的RAR消息和响应于一般随机接入过程的RAR消息不相同，则在这种方式中，随机接入冲突可能发生在随机接入步骤(1)选择要发送的前导序列过程。在这种方式中，随机接入冲突可能发生在消息3中确定携带来自不同CCCH的CCCH SDU或用于不同目的的CCCH SDU中的哪一个。
根据本公开，基于请求系统信息的不同方式，如果冲突发生在随机接入步骤(1)选择要发送的前导序列过程(即确定选择哪个前导序列发送)，可以预定义或通过RRC信令配置由请求系统信息(或请求系统信息消息)触发的随机接入和由其他事件触发的随机接入间的优先级。MAC实体基于所述优先级，在发生冲突时，可以选择优先级高的事件对应的前导序列进行发送。如果冲突发生在随机接入消息3(即确定在消息3中包含哪种消息或CCCH SDU或数据)，可以预定义或通过RRC信令配置请求系统信息消息(或所述消息对应的CCCH SDU)和其他RRC消息(或所述消息对应的CCCH SDU)或数据或所述消息对应的逻辑信道间的优先级。所述其他RRC消息(称为专用RRC消息)包括RRC连接请求消息、RRC连接重建请求消息、RRC连接恢复请求消息等。MAC实体基于所述优先级，在发生冲突时，在随机接入消息3中优先包含优先级高的RRC消息或所述消息对应的CCCH SDU或数据。
下面将介绍根据本公开实施例的用户设备UE中的各种方法，用于解决由请求其他系统信息触发的随机接入过程与其他事件触发的随机接入过程导致的冲突。
图2示出了根据本公开实施例的用户设备UE中的方法200的流程图。
如图所示，在步骤S210，用户设备UE创建具有不同优先级的第一公共控制信道CCCH和第二公共控制信道CCCH分别用于传输专用无线资源控制RRC消息和系统信息请求消息，所述系统信息请求消息用于请求最小系统信息以外的系统信息。
在步骤S230，用户设备UE根据第一CCCH和第二CCCH的优先级，确定在随机接入消息3‘Msg3’中包含第一CCCH和第二CCCH中的哪一 个CCCH所对应的CCCH服务数据单元SDU或者将第一CCCH和第二CCCH的CCCH SDU都包含在随机接入消息3‘Msg3’中。
在步骤S250，用户设备UE将随机接入消息3‘Msg3’发送到基站(或将消息3递交给下层或物理层或传输信道UL-SCH以发送给基站)。
例如，专用RRC消息包括以下一个或多个：RRC连接请求消息、RRC连接重建请求消息或RRC连接恢复请求消息。
图3示出了根据本公开实施例的用户设备UE中的方法300的流程图。
如图所示，在步骤S310，用户设备UE创建第一CCCH和第二CCCH用于以不同的优先级分别传输专用RRC消息和请求系统信息消息。
在步骤S330，用户设备UE选择与第一CCCH和第二CCCH中优先级较高的CCCH所对应的前导序列。
在步骤S350，用户设备UE将所选择的前导序列发送到基站(或将消息3递交给下层或物理层或传输信道UL-SCH以发送给基站)。
例如，专用RRC消息包括以下一个或多个：RRC连接请求消息、RRC连接重建请求消息或RRC连接恢复请求消息。
在一个实现方式中，第一CCCH的优先级高于第二CCCH的优选级。在这种情况下，步骤S330可以包括：当第一CCCH和第二CCCH均有待发送的CCCH SDU时，从第一CCCH对应的前导序列中选择一个前导序列。
在另一个实现方式中，第二CCCH的优先级高于第一CCCH的优选级。在这种情况下，步骤S330可以包括：当第一CCCH和第二CCCH均有待发送的CCCH SDU时，从第二CCCH对应的前导序列中选择一个前导序列。
需要说明的是，如果两者共享相同的前导序列或前导序列组，当第一CCCH和第二CCCH均有CCCH SDU待发送，则UE根据预定义的规则选择一个前导序列，例如根据消息3的大小选择前导序列。此时，UE在消息3中包含优先级高的那个CCCH对应的CCCH SDU。即UE在构建消息3时，先判断优先级高的CCCH是否有CCCH SDU待发送，如果是，则在消息3中包含所述优先级高的CCCH SDU。
图4示出了根据本公开实施例的用户设备UE中的方法400的流程图。
如图所示，在步骤S410，用户设备UE确定传输系统信息请求消息和专用RRC消息的优先级，所述系统信息请求消息用于请求最小系统信息以 外的系统信息。
在步骤S430，根据所述优先级，在由请求系统信息消息触发的随机接入与由专用RRC消息触发的随机接入发生冲突时，选择系统信息请求消息和专用RRC消息中优先级高的消息所对应的前导序列。
在步骤S450，用户设备UE将所选择的前导序列发送到基站。
在一个实现方式中，如果请求系统信息消息的优先级低于专用RRC消息的优先级，并且如果请求系统信息的RRC过程被触发(即要构建及发送系统信息请求消息)，则方法400还可以包括如图5所示的步骤S420、S421和S422。
在步骤S420，用户设备UE判断是否有请求系统信息的RRC过程以外的其他RRC过程被触发或正在执行(即有专用RRC消息待发送或已发送但未收到应答消息)。本公开中所述的请求系统信息的RRC过程以外的其他RRC过程包括以下过程的一个或多个：RRC连接建立过程、RRC连接恢复过程和RRC连接重建过程等。
如果是，则在步骤S421，用户设备UE等待被触发或正在执行的其他RRC过程结束，然后再启动请求系统信息的RRC过程。或者，用户设备UE可以终止请求系统信息的RRC过程。
如果否，则在步骤S422，用户设备UE执行请求系统信息的RRC过程。
在另一个实现方式中，如果请求系统信息消息的优先级低于专用RRC消息的优先级，并且如果请求系统信息的RRC过程以外的其他RRC过程被触发，则方法400还可以包括如图6所示的步骤S423、S424和S425。
在步骤S423，用户设备UE判断是否有请求系统信息的RRC过程正在执行。
如果是，则在步骤S424，用户设备UE终止正在执行的请求系统信息的RRC过程，并执行请求系统信息的RRC过程以外的其他RRC过程，以及在请求系统信息的RRC过程以外的其他RRC过程结束之后，重新启动请求系统信息的RRC过程。
如果否，则在步骤S425，用户设备UE执行所述被触发的请求系统信息的RRC过程以外的其他RRC过程。
在又一个实现方式中，如果请求系统信息消息的优先级高于专用RRC消息的优先级，并且如果请求系统信息的RRC过程被触发，则方法400可 以包括如图7所示的步骤S440、S441和S442。
在步骤S440，用户设备UE判断是否有请求系统信息的RRC过程以外的其他RRC过程被触发或正在执行。
如果是，则在步骤S441，用户设备UE终止正在执行的请求系统信息的RRC过程以外的其他RRC过程，并执行请求系统信息的RRC过程。
如果否，则在步骤S442，用户设备UE执行请求系统信息的RRC过程。
在再一个实现方式中，如果请求系统信息消息的优先级高于专用RRC消息的优先级，并且如果请求系统信息的RRC过程以外的其他RRC过程被触发，则方法400可以包括如图8所示的步骤S443和S444和S445。
在步骤S443，用户设备UE判断是否有请求系统信息的RRC过程被触发或正在执行。
如果是，则在步骤S444，用户设备UE等待所述被触发或正在执行的请求系统信息的RRC过程结束，然后启动请求系统信息的RRC过程以外的其他RRC过程。或者，用户设备UE也可以终止请求系统信息的RRC过程以外的其他RRC过程。
否则，在步骤S445，用户设备UE执行所述被触发的请求系统信息的RRC过程以外的其他RRC过程。
图9示出了根据本公开实施例的用户设备UE中的方法900的流程图。
如图所示，在步骤S910，用户设备UE确定由请求系统信息消息触发的随机接入与由其他事件(例如上层或专用RRC消息、MAC层本身、PDCCH order等)触发的随机接入的优先级或确定不同事件(例如，请求系统信息、专用RRC消息、MAC层本身、PDCCH order等)触发的随机接入对应前导序列的优先级，所述系统信息请求消息用于请求最小系统信息以外的系统信息。
在步骤S930，在由请求系统信息消息触发的随机接入与由其他事件触发的随机接入发生冲突时，选择优先级较高的随机接入所对应的前导序列或选择优先级较高的前导序列。
在步骤S950，用户设备UE将所选择的前导序列发送到基站。
在一个实现方式中，如果由请求系统信息消息触发的随机接入或对应的前导序列高于由其他事件触发的随机接入或对应的前导序列的优先级， 则方法900还可以包括如图10所示的步骤S920和S921。
在步骤S920，用户设备UE判断是否存在由请求系统信息消息触发的随机接入对应的前导序列待发送。
如果是，则在步骤S921，选择由请求系统信息消息触发的随机接入所对应的前导序列。如果否，则方法900返回到步骤S920。
如图11所示，如果请求系统信息的随机接入被触发，方法900还可选地进一步包括步骤S922、S923、S924和S925。
在步骤S922，用户设备UE判断是否有正在执行的由其他事件触发的随机接入。
如果是，则在步骤S923，用户设备UE中断当前正在执行的由其他随机接入触发消息触发的随机接入，并在步骤S924选择由请求系统信息消息触发的随机接入所对应的前导序列。
如果否，则在步骤S925，选择由请求系统信息消息触发的随机接入所对应的前导序列。
在另一实现方式中，如果由请求系统信息消息触发的随机接入低于由其他事件触发的随机接入的优先级，则方法900还可以包括如图12所示的步骤S940和S941。
在步骤S940，用户设备UE判断是否存在由其他事件触发的随机接入。
如果是，则在步骤S941，选择由其他事件触发的随机接入所对应的前导序列。如果否，则方法900可以返回步骤S940。
如图13所示，方法900还可选地进一步包括步骤S942、S943和S944。
在步骤S942，用户设备UE判断是否有正在执行的由请求系统信息消息触发的随机接入。
如果是，则在步骤S943中断当前正在执行的由请求系统信息消息触发的随机接入，并在步骤S944选择由其他事件触发的随机接入所对应的前导序列。
否则，在步骤S944，选择由其他事件触发的随机接入所对应的前导序列。
图14示出了根据本公开实施例的用户设备UE中的方法1400的流程图。
如图所示，在步骤S1410，用户设备UE确定由请求系统信息消息触发的随机接入与由其他事件触发的随机接入的优先级，所述系统信息请求消息用于请求最小系统信息以外的系统信息。
在步骤S1430，在由请求系统信息消息触发的随机接入与由其他事件触发的随机接入发生冲突时，选择优先级较高的随机接入所对应的消息。
在步骤S1450，用户设备UE通过在随机接入消息3‘Msg3’中包含所选择的消息，将所选择的消息发送到基站。
下面将基于冲突发生的场景，具体介绍UE解决冲突的不同方式。
场景一：冲突发生在RRC层
如果UE通过发送不同的前导序列来请求不同的其他系统信息，则RRC层(或称高层)将根据需要请求的系统信息选择对应的前导序列，并将所述前导序列递交或指示给下层(或MAC层)进行发送。具体过程如下：
由于业务需要或因系统信息到期，NAS层(或称高层)或RRC层触发UE请求系统信息过程。如果目前没有其他正在执行的RRC过程(包括但不限于RRC连接建立，RRC连接重建，RRC连接恢复)或CCCH逻辑信道中没有待发送的CCCH SDU，根据UE请求其他系统信息的不同方式，UE可以执行以下两个实施例之一：
在一个实施例中，UE根据需要请求的系统信息选择对应的前导序列，将所述前导序列递交给下层(或MAC层)。
在另一个实施例中，UE根据需要请求的系统信息构建系统信息请求消息，将所述系统信息请求消息递交给下层进行传输。
可以预定义或通过RRC信令配置用于请求其他系统信息的RRC过程(或系统信息请求消息)与其他RRC过程或RRC连接建立过程(或RRC连接请求消息或RRC连接重建请求消息或RRC连接恢复请求消息)的优先级。
在一个实施例中，假设请求其他系统信息的RRC过程(或系统信息请求消息)的优先级低于正在执行的其他RRC过程或RRC连接建立过程(或RRC连接请求消息或RRC连接重建请求消息或RRC连接恢复请求消息)。如果NAS层或高层或RRC层触发系统信息请求过程，UE判断是否有其他 RRC过程或RRC连接建立过程被触发或正在执行(即RRC连接请求消息或RRC连接重建请求消息或RRC连接恢复请求消息待发送或已发送但未接收到应答消息)；如果是，UE可以等待所述被触发或正在执行的其他RRC过程或RRC连接建立过程结束，再启动请求其他系统信息的RRC过程(即构建并发送系统信息请求消息或将系统信息请求消息递交给下层)；或者UE也可以终止请求其他系统信息的RRC过程(即丢弃系统信息请求消息)；如果否，UE可以构建系统信息请求消息并递交给下层进行发送。如果RRC连接建立过程或其他RRC过程被触发，UE判断是否有正在执行请求其他系统信息的RRC过程(例如，系统信息请求消息待发送或已发送但未接收到应答消息)；如果是，UE可以终止正在执行的系统信息请求的RRC过程(例如，丢弃或删除尚未发送的系统信息请求消息或如果所述消息已发送但尚未接收到应答消息，则不再接收应答消息)并执行所述优先级更高的RRC过程。待优先级更高的RRC过程结束后，可以重新启动请求其他系统信息的RRC过程(即发送系统信息请求消息或将系统信息请求消息递交给下层)；如果否，UE可以构建相应的消息并递交给下层进行发送(例如，构建并发送RRC连接请求消息或RRC连接重建请求消息或RRC连接恢复请求消息并将所述消息递交给下层进行发送)。
假设请求其他系统信息的RRC过程(或系统信息请求消息)的优先级高于正在执行的其他RRC过程或RRC连接建立过程(或RRC连接请求消息或RRC连接重建请求消息或RRC连接恢复请求消息)。如果NAS层或高层或RRC层触发系统信息请求过程，UE判断是否有其他RRC过程或RRC连接建立过程被触发或正在执行；如果是，则UE可以终止正在执行的其他RRC过程或RRC连接建立过程(例如，丢弃或删除尚未发送的RRC连接请求消息或RRC连接重建请求消息或RRC连接恢复请求消息)并执行请求其他系统信息的RRC过程(即发送系统信息请求消息或将系统信息请求消息递交给下层)(所述终止的RRC过程可以等请求系统信息过程结束后再重新启动)；如果否，UE可以构建系统信息请求消息并递交给下层进行发送。如果RRC连接建立过程或其他RRC过程被触发，UE判断是否有请求系统信息过程被触发或正在执行请求其他系统信息的RRC过程(例如，系统信息请求消息待发送或已发送但未接收到应答消息)；如果是，UE可以等待所述被触发或正在执行的请求系统信息过程结束，再启动其他 RRC过程或RRC连接建立过程(即构建并发送RRC连接请求消息或RRC连接重建请求消息或RRC连接恢复请求消息并将所述消息递交给下层进行发送)；或者UE也可以终止RRC连接建立过程或其他RRC过程(例如，丢弃或删除尚未发送的RRC连接请求消息或RRC连接重建请求消息或RRC连接恢复请求消息)；如果否，UE可以启动其他RRC过程或RRC连接建立过程(即构建并发送RRC连接请求消息或RRC连接重建请求消息或RRC连接恢复请求消息并将所述消息递交给下层进行发送)。
需要说明的是，本公开中所述终止正在执行的RRC过程(其中包括请求系统信息过程，RRC连接建立过程等)或启动或重新启动一个RRC过程还可以包括重配置物理信道和/或重配置半静态调度配置和/或重配置MAC主配置和/或重配置CCCH逻辑信道实现。所述重配置可以是重新应用缺省配置。本公开中的RRC连接建立过程可以是RRC连接请求消息，RRC连接重建请求消息，RRC连接恢复请求消息对应的RRC连接建立过程。
在另一个实施例中，定义不同于第一CCCH逻辑信道的第二CCCH逻辑信道。所述第一CCCH逻辑信道(含上行和下行CCCH逻辑信道)用于传输RRC连接请求消息、RRC连接重建请求消息、RRC连接恢复请求消息(所述消息在上行CCCH逻辑信道传输)及相应的应答消息(所述消息在下行CCCH逻辑信道传输)等。所述第二CCCH逻辑信道(含上行和/或下行CCCH逻辑信道)用于传输系统信息请求消息(所述消息在上行CCCH逻辑信道中传输)和/或相应的应答消息(所述消息在下行CCCH逻辑信道中传输)。也可以不单独定义用于第二下行CCCH逻辑信道，而是采用已有的下行逻辑信道，例如，第一下行CCCH逻辑信道。所述第二CCCH逻辑信道的部分参数不同于第一CCCH逻辑信道。例如，所述第二CCCH逻辑信道的优先级定义为不同于第一CCCH逻辑的值(例如，为2或其他值)，和/或所述第二CCCH逻辑信道的逻辑信道群标识(logicalChannelGroup)定义为不同于第一CCCH逻辑的逻辑信道群标识的值(例如，为1或其他值)。
在本实施例中，当UE需要请求其他系统信息或建立RRC连接过程时，可以构建相应的系统信息请求消息或RRC连接请求消息或RRC连接重建请求消息或RRC连接恢复请求消息并递交给下层进行传输。如果由系统信 息请求消息(即第二CCCH逻辑信道)或其他RRC消息(即第一CCCH逻辑信道)触发的随机接入过程共享前导序列集，则MAC实体可以基于逻辑信道的优先级和/或逻辑信道群标识决定在消息3中包含哪个CCCH逻辑信道对应的CCCH SDU或将所有CCCH逻辑信道的CCCH SDU都包含在消息3中。如果由系统信息请求消息(即第二CCCH逻辑信道对应的CCCH SDU)或其他RRC消息(即第一CCCH逻辑信道对应的CCCH SDU)触发的随机接入过程采用不同的前导序列，则MAC实体可以基于逻辑信道的优先级和/或逻辑信道群标识选择相应的前导序列并递交给下层发送。例如，如果第一CCCH逻辑信道(或RRC连接请求消息或RRC连接重建请求消息或RRC连接恢复请求消息或第一CCCH逻辑信道对应的CCCH SDU)的优先级高于第二CCCH逻辑信道(或系统信息请求消息或第二CCCH逻辑信道对应的CCCH SDU)的优先级，则当第一CCCH逻辑信道和第二CCCH逻辑信道均有待发送的CCCH SDU，MAC实体从第一CCCH逻辑信道对应的前导序列中选择一个前导序列并递交给下层发送。反之亦然。
可选的，对于处于RRC空闲态的UE，在执行请求其他系统信息的RRC过程(将其他系统信息请求消息递交到下层进行传输前)还需要执行以下步骤中的一步或多步：
(a)应用缺省的物理信道配置(预定义参数值)；
(b)应用缺省的半静态调度配置(预定义参数值)；
(c)应用确省的MAC主配置(预定义参数值)；
(d)应用第二CCCH逻辑信道配置(预定义参数值)；
第一CCCH逻辑信道对应的的物理信道配置和/或半静态调度配置和/或MAC主配置可以与第二CCCH逻辑信道对应的配置相同。当第一CCCH逻辑信道对应的CCCH SDU尚未发送，请求其他系统信息过程被触发(即系统信息请求消息待发送)，UE可以只执行上述步骤中与第二CCCH逻辑信道配置不同步骤，例如只执行步骤(d)；反之，当第二CCCH逻辑信道对应的CCCH SDU尚未发送，而建立RRC连接过程被触发(如RRC连接请求消息或RRC连接重建请求消息或RRC连接恢复请求消息等等待发送)，UE也可以仅应用与第一CCCH逻辑信道配置不同的配置，而不需要重新配置物理信道和/或半静态调度和/或MAC。
在又一个实施例中，根据触发UE请求系统信息的不同条件，定义请求 系统信息消息与其他RRC消息间的优先级。所述其他RRC消息可以包括：RRC连接请求消息、RRC连接重建请求消息、RRC连接恢复请求消息、RRC连接重配置完成消息。例如如果是由于本地存储的系统信息到期而触发的UE发送系统信息请求消息(即启动系统信息请求过程)，则所述系统信息请求消息的优先级最高，即当因系统信息到期而触发发送系统信息请求消息时，如果有其他等待发送或已经发送但未接收到应答消息的RRC消息，取消(或暂停发送)其他RRC消息或终止(或挂起)其他RRC消息对应的RRC过程；如果其他RRC消息已经发送但未接收到应答消息，则不接收应答消息。将系统信息请求消息递交给下层。
可选的，还可以根据触发UE请求系统信息的条件及请求系统信息的类型，定义请求系统信息消息与其他RRC消息间的优先级。
可选的，也可以仅根据需要获取的系统信息的类型，定义请求系统信息消息与其他RRC消息间的优先级。部分类型的系统信息优先级高于其他RRC消息，另一部分的系统信息优先级低于低于其他RRC消息。
可选的，还可以定义不同类型的系统信息间的优先级或不同类型系统信息对应的前导序列优先级，当要求请求多种类型的系统信息时，优先请求优先级高的系统信息。
场景二：冲突发生在MAC层
根据请求系统信息的不同方式，MAC层的冲突分为以下几种类型：
类型一：请求系统信息随机接入与基于竞争的随机接入发生冲突
所述基于竞争的随机接入前导序列是由MAC层选择的前导序列，基于竞争的随机接入可以包含由以下事件触发的随机接入：
A.由MAC子层本身触发的随机接入；
B.由PDCCH order触发或由切换触发或携带切换指示信元(记为mobilityControlInfo)的RRC连接重配置消息触发等，且前导序列值为000000或为其他用于指示MAC需要选择前导序列的值。
以下以由MAC子层本身触发的随机接入为例进行说明，所述实施例也适用于其他事件触发的基于竞争的随机接入。
在一个实施例中，如果为请求系统信息预留了一个或多个前导序列，即用于请求系统信息随机接入的前导序列不同于一般随机接入的前导序 列。MAC层基于预定义或通过RRC信令配置的优先级选择相应的前导序列进行发送。例如，如果预定义请求系统信息随机接入的优先级高于MAC子层触发的随机接入或一般随机接入，则在发生所述冲突时，MAC选择预留给请求系统信息随机接入的前导序列并指示物理层发送，即MAC实体在选择用于随机接入的前导序列时，先判断是否存在请求系统信息随机接入或请求系统信息对应的前导序列待发送，如果是，则选择用于请求系统信息随机接入的前导序列并指示物理层发送；或者当请求系统信息随机接入被触发或请求系统信息对应的前导序列待发送时，如果有正在执行的MAC子层触发的随机接入或一般随机接入，UE可以中断当前正在执行的MAC子层触发的随机接入或一般随机接入，并开始执行请求系统信息随机接入或发送请求系统信息对应的前导序列待；如果预定义请求系统信息随机接入的优先级低于MAC子层触发的随机接入或一般随机接入，则在发生所述冲突时，MAC选择用于一般随机接入的前导序列并指示物理层发送，即MAC实体在选择用于随机接入的前导序列时，先判断是否存在MAC子层触发的随机接入或一般随机接入，如果是，则选择用于一般随机接入的前导序列并指示物理层发送；或者如果有正在执行的请求系统信息随机接入，当MAC子层触发的随机接入或一般随机接入被触发，UE中断当前正在执行的请求系统信息随机接入，并开始执行MAC子层触发的随机接入或一般随机接入或选择一般随机接入前导序列并指示物理层发送。
在另一个实施例中，请求系统信息随机接入与一般随机接入使用相同的前导序列。例如，请求系统信息随机接入的前导序列是一般随机接入基于竞争的前导序列集。MAC实体从一般随机接入的前导序列集中选择一个前导序列并指示物理层发送，此时MAC实体在消息3中解决冲突。预定义或通过RRC信令配置其他系统信息请求消息(即请求系统信息消息对应的CCCH SDU或第二CCCH SDU)与其他RRC消息(例如RRC连接请求消息或RRC连接重建请求消息或RRC连接恢复请求消息对应的CCCH SDU或第一CCCH SDU)或数据的优先级，MAC实体基于所述预定义的优先级将优先级高的消息或数据包含在消息3中；或者如果消息3中可以容纳多条消息或数据，可以将按照优先级由高到低依次将所述消息或数据包含在消息3中。例如，假设其他系统信息请求消息高于其他消息或数据，MAC在构建消息3时，先判断是否有请求其他系统信息请求消息对应的CCCH  SDU待发送，如果是，则将其包含在消息3中。在类型三对应的实施例中描述了如何根据不同消息的优先级构建消息3。
类型二：请求系统信息随机接入与基于非竞争的随机接入发生冲突
所述基于非竞争的随机接入可以包括由PDCCH order触发的随机接入和/或由切换触发的随机接入等，所述随机接入对应的前导序列显式指定且不为0000000或其他用于指示MAC需要选择前导序列的值(即前导序列不是由MAC实体选择)。以下实施例以由PDCCH order触发的基于非竞争的随机接入为例，所述实施例也适用于由其他事件触发的基于非竞争的随机接入。
在一个实施例中，如果为请求系统信息预留了一个或多个前导序列，即用于请求系统信息随机接入的前导序列不同于一般随机接入的前导序列。在发生冲突时，MAC层基于预定义或通过RRC信令配置的优先级选择相应的前导序列并指示物理层进行发送。例如，如果规定请求系统信息随机接入的优先级高于PDCCH order触发的随机接入，则在发生所述冲突时，MAC选择预留给请求系统信息随机接入的前导序列并指示物理层进行发送，即MAC实体在选择用于随机接入的前导序列时，先判断是否存在请求系统信息随机接入或用于请求系统信息的前导序列待发送，如果是，则选择用于请求系统信息随机接入的前导序列并指示物理层发送；或者如果正在执行PDCCH order触发的随机接入时，请求系统信息随机接入被触发或请求系统信息前导序列待发送，UE中断当前正在执行的PDCCH order触发的随机接入，并开始执行请求系统信息随机接入或指示物理层发送请求系统信息前导序列；如果预定义请求系统信息随机接入的优先级低于PDCCH order触发的随机接入，则在发生所述冲突时，MAC选择用于PDCCH order中显式指定的前导序列并指示物理层进行发送。即MAC实体在选择用于随机接入的前导序列时，先判断是否存在PDCCH order触发的随机接入，如果是，则选择PDCCH order中显式指定的前导序列并指示物理层发送；或者如果正在执行请求系统信息随机接入，PDCCH order触发随机接入，UE中断当前正在执行的请求系统信息随机接入，并开始执行PDCCH order触发的随机接入或选择PDCCH order中显式指定的前导序列并指示物理层发送。
需要说明的是，上述实施例也适用于请求系统信息随机接入与一般随机接入使用相同的前导序列的场景。此时，如果需要执行系统信息请求随机接入，MAC实体从一般随机接入的前导序列集中选择一个前导序列发送。上述实施例的其他过程保持不变。例如，请求系统信息随机接入的前导序列是一般随机接入基于竞争的前导序列集。当执行由系统信息请求消息触发的随机接入过程时，MAC实体从一般随机接入基于竞争的前导序列集中选择一个前导序列并指示物理层发送
类型三：由MAC子层触发的随机接入，消息3发生冲突
在所述类型中，随机接入由MAC子层触发，UE在构建消息3时，有多条消息或数据待发送，所述消息或数据可以来自不同的CCCH逻辑信道或相同的CCCH逻辑信道(其中可以携带一个标识，用于指示消息类型或消息优先级，以便MAC区分不同的消息或区分不同消息的优先级)。
在一个实施例中，消息3只可携带一种类型的消息或数据，例如如果消息3中携带了请求其他系统信息请求消息对应的CCCH SDU，则不能再携带其他消息或数据。可以预定义或通过RRC信令配置不同消息或数据或CCCH SDU或CCCH逻辑信道的优先级，UE在消息3中包含优先级最高的消息或数据或CCCH SDU。如果预定义请求其他系统信息请求消息对应的CCCH SDU或消息优先级高于其他CCCH SDU或消息或数据，则MAC实体在构建消息3时，先判断是否有待发送的系统信息请求消息对应的CCCH SDU或消息，如果有，则在消息3中包含所述内容；如果没有，则在消息3中包含所述其他CCCH对应的CCCH SDU或消息或数据。如果预定义请求其他系统信息请求消息对应的CCCH SDU或消息优先级低于其他CCCH SDU或消息或数据，则MAC实体在构建消息3时，先判断是否有待发送的其他CCCH对应的CCCH SDU或消息或数据，如果有，则在消息3中包含所述其他CCCH对应的CCCH SDU或消息或数据；如果没有，则在消息3中包含所述内容。
在另一个实施例中，消息3中可以携带多种类型的消息或数据，例如如果携带在RAR中的上行调度(UL Grant)足够大，消息3中可以携带多种消息或CCCH SDU或数据且这些消息或CCCH SDU或数据按照预定义的顺序包含在消息3中。例如假设请求其他系统信息请求消息对应的CCCH  SDU放在RRC连接请求消息或RRC连接重建请求消息或RRC连接恢复请求消息等对应的CCCH SDU前面，反之亦然。
需要说明的是，本公开所述预定义的参数或规则或优先级也可以通过RRC信令配置。
与上述方法200相对应，本公开提供了一种用户设备UE。图15示出了根据本公开实施例的UE 1500的框图。如图所示，UE 1500包括：信道创建单元1510、确定单元1530和发送单元1550。信道创建单元1510被配置为创建具有不同优先级的第一公共控制信道CCCH和第二公共控制信道CCCH分别用于传输专用无线资源控制RRC消息和系统信息请求消息，所述系统信息请求消息用于请求最小系统信息以外的系统信息。确定单元1530被配置为根据第一CCCH和第二CCCH的优先级，确定在随机接入消息3‘Msg3’中包含第一CCCH和第二CCCH中的哪一个CCCH所对应的CCCH服务数据单元SDU或者将第一CCCH和第二CCCH的CCCH SDU都包含在随机接入消息3‘Msg3’中。发送单元1550被配置为将随机接入消息3‘Msg3’发送到基站。
在一个实施例中，所述专用RRC消息包括以下一个或多个：RRC连接请求消息、RRC连接重建请求消息或RRC连接恢复请求消息。
与上述方法300相对应，本公开提供了一种用户设备UE。图16示出了根据本公开实施例的UE 1600的框图。如图所示，UE 1600包括：信道创建单元1610、选择单元1630和发送单元1650。信道创建单元1610被配置为创建第一CCCH和第二CCCH用于以不同的优先级分别传输专用RRC消息和请求系统信息消息。选择单元1630被配置为选择与第一CCCH和第二CCCH中优先级较高的CCCH所对应的前导序列。发送单元1650被配置为将所选择的前导序列发送到基站。
在一个实施例中，所述专用RRC消息包括以下一个或多个：RRC连接请求消息、RRC连接重建请求消息或RRC连接恢复请求消息。
在一个实施例中，第一CCCH的优先级高于第二CCCH的优选级。在这种情况下，选择单元1630还被配置为：当第一CCCH和第二CCCH均有待发送的CCCH SDU时，从第一CCCH对应的前导序列中选择一个前导 序列。
与上述方法400相对应，本公开提供了一种用户设备UE。图17示出了根据本公开实施例的UE 1700的框图。如图所示，UE 1700包括：确定单元1710、选择单元1730和发送单元1750。确定单元1710被配置为确定传输系统信息请求消息和专用RRC消息的优先级，所述系统信息请求消息用于请求最小系统信息以外的系统信息。选择单元1730被配置为根据所述优先级，在由请求系统信息消息触发的随机接入与由专用RRC消息触发的随机接入发生冲突时，选择系统信息请求消息和专用RRC消息中优先级高的消息所对应的前导序列。发送单元1750被配置为将所选择的前导序列发送到基站。
在一个实施例中，请求系统信息消息的优先级低于专用RRC消息的优先级，并且请求系统信息的RRC过程被触发。在这个实施例中，所述UE1700还包括：第一判断单元1720，被配置为判断是否有请求系统信息的RRC过程以外的其他RRC过程被触发或正在执行；以及第一RRC过程控制单元1721，被配置为：如果有请求系统信息的RRC过程以外的其他RRC过程被触发或正在执行，则等待被触发或正在执行的其他RRC过程结束，然后再启动请求系统信息的RRC过程；或者终止请求系统信息的RRC过程。根据这个实施例，可选地，第一RRC过程控制单元1721还被配置为：如果没有请求系统信息的RRC过程以外的其他RRC过程被触发或正在执行，则执行请求系统信息的RRC过程。
在一个实施例中，请求系统信息消息的优先级低于专用消息的优先级，并且请求系统信息的RRC过程以外的其他RRC过程被触发。在这个实施例中，所述UE 1700还包括：第二判断单元1722，被配置为判断是否有请求系统信息的RRC过程正在执行；以及第二RRC过程控制单元1723，被配置为：如果有请求系统信息的RRC过程正在执行，则终止正在执行的请求系统信息的RRC过程，并执行请求系统信息的RRC过程以外的其他RRC过程，以及在请求系统信息的RRC过程以外的其他RRC过程结束之后，重新启动请求系统信息的RRC过程。
在一个实施例中，请求系统信息消息的优先级高于专用RRC消息的优先级，并且请求系统信息的RRC过程被触发。在这个实施例中，所述UE 1700还包括：第三判断单元1724，被配置为判断是否有请求系统信息的RRC过程以外的其他RRC过程被触发或正在执行；以及第三RRC过程控制单元1725，被配置为：如果有请求系统信息的RRC过程以外的其他RRC过程被触发或正在执行，则终止正在执行的请求系统信息的RRC过程以外的其他RRC过程，并执行请求系统信息的RRC过程。根据这个实施例，可选地，第三RRC过程控制单元1725还被配置为：如果没有请求系统信息的RRC过程以外的其他RRC过程被触发或正在执行，则执行请求系统信息的RRC过程。
在一个实施例中，请求系统信息消息的优先级高于专用RRC消息的优先级，并且请求系统信息的RRC过程以外的其他RRC过程被触发。在这个实施例中，所述UE 1700还包括：第四判断单元1726，被配置为判断是否有请求系统信息的RRC过程被触发或正在执行；第四RRC过程控制单元1727，被配置为：如果有请求系统信息的RRC过程被触发或正在执行，则等待所述被触发或正在执行的请求系统信息的RRC过程结束，然后启动请求系统信息的RRC过程以外的其他RRC过程；或者终止请求系统信息的RRC过程以外的其他RRC过程。
应理解，本公开中所涉及的两个或多个不同单元可以在逻辑上或物理上结合在一起。例如，第一判断单元1720、第二判断单元1722、第三判断单元1724和第四判断单元1726可以合并到单个单元内。此外，第一RRC过程控制单元1721、第二RRC过程控制单元1723、第三RRC过程控制单元1725和第四RRC过程控制单元1727也可以合并到单个单元内。
与上述方法900相对应，本公开提供了一种用户设备UE。图18示出了根据本公开实施例的UE 1800的框图。如图所示，UE 1800包括：确定单元1810、选择单元1830和发送单元1850。确定单元1810被配置为确定由请求系统信息消息触发的随机接入与由其他事件触发的随机接入的优先级，所述系统信息请求消息用于请求最小系统信息以外的系统信息。选择单元1830被配置为在由请求系统信息消息触发的随机接入与由其他事件触发的随机接入发生冲突时，选择优先级较高的随机接入所对应的前导序列。发送单元1850被配置为将所选择的前导序列发送到基站。
在一个实施例中，由请求系统信息消息触发的随机接入高于由其他事 件触发的随机接入的优先级。在这个实施例中，所述UE 1800还包括：第一判断单元1820，被配置为判断是否存在由请求系统信息消息触发的随机接入对应的前导序列待发送。所述选择单元1830还被配置为：如果存在由请求系统信息消息触发的随机接入对应的前导序列待发送，则选择由请求系统信息消息触发的随机接入所对应的前导序列。可选地，所述第一判断单元1820还被配置为判断是否有正在执行的由其他事件触发的随机接入，并且UE 1800还包括：第一随机接入中断单元1821，被配置为：如果有正在执行的由其他事件触发的随机接入，则中断当前正在执行的由其他随机接入触发消息触发的随机接入。在这种情况下，选择单元1820还被配置为选择由请求系统信息消息触发的随机接入所对应的前导序列。
在一个实施例中，由请求系统信息消息触发的随机接入低于由其他事件触发的随机接入的优先级。在这个实施例中，所述UE 1800还包括：第二判断单元1822，被配置为判断是否存在由其他事件触发的随机接入。选择单元1820还被配置为：如果存在由其他事件触发的随机接入，则选择由其他事件触发的随机接入所对应的前导序列。可选地，第二判断单元1822还可以被配置为判断是否有正在执行的由请求系统信息消息触发的随机接入，并且UE 1800还包括：第二随机接入中断单元1823，被配置为：如果有正在执行的由请求系统信息消息触发的随机接入，则中断当前正在执行的由请求系统信息消息触发的随机接入。在这种情况下，选择单元1820还被配置为选择由其他事件触发的随机接入所对应的前导序列。
应理解，本公开中所涉及的两个或多个不同单元可以在逻辑上或物理上结合在一起。例如，第一判断单元1820和第二判断单元1822可以合并到单个单元内。此外，第一随机接入中断单元1821和第二随机接入中断单元1823也可以合并到单个单元内。
与上述方法1400相对应，本公开提供了一种用户设备UE。图19示出了根据本公开实施例的UE 1900的框图。如图所示，UE 1900包括：确定单元1910、选择单元1930和发送单元1950。确定单元1910被配置为确定由请求系统信息消息触发的随机接入与由其他事件触发的随机接入的优先级，所述系统信息请求消息用于请求最小系统信息以外的系统信息。选择单元1930被配置为：在由请求系统信息消息触发的随机接入与由其他事件 触发的随机接入发生冲突时，选择优先级较高的随机接入所对应的消息。发送单元1950被配置为：通过在随机接入消息3‘Msg3’中包含所选择的消息，将所选择的消息发送到基站。
运行在根据本发明的设备上的程序可以是通过控制中央处理单元(CPU)来使计算机实现本发明的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统中。
用于实现本发明各实施例功能的程序可以记录在计算机可读记录介质上。可以通过使计算机系统读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机系统”可以是嵌入在该设备中的计算机系统，可以包括操作系统或硬件(如外围设备)。“计算机可读记录介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如，单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器，也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路，也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下，本发明的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外，本发明并不局限于上述实施例。尽管已经描述了所述实施例的各种示例，但本发明并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备，如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上，已经参考附图对本发明的实施例进行了详细描述。但是，具体的结构并不局限于上述实施例，本发明也包括不偏离本发明主旨的任何设计改动。另外，可以在权利要求的范围内对本发明进行多种改动，通过适 当地组合不同实施例所公开的技术手段所得到的实施例也包含在本发明的技术范围内。此外，上述实施例中所描述的具有相同效果的组件可以相互替代。

Claims (30)

  1. 一种用户设备UE中的方法，包括：
    创建具有不同优先级的第一公共控制信道CCCH和第二公共控制信道CCCH分别用于传输专用无线资源控制RRC消息和系统信息请求消息，所述系统信息请求消息用于请求最小系统信息以外的系统信息；
    根据第一CCCH和第二CCCH的优先级，确定在随机接入消息3‘Msg3’中包含第一CCCH和第二CCCH中的哪一个CCCH所对应的CCCH服务数据单元SDU或者将第一CCCH和第二CCCH的CCCH SDU都包含在随机接入消息3‘Msg3’中；以及
    将随机接入消息3‘Msg3’发送到基站。
  2. 根据权利要求1所述的方法，其中，所述专用RRC消息包括以下一个或多个：RRC连接请求消息、RRC连接重建请求消息或RRC连接恢复请求消息。
  3. 一种用户设备UE，包括：
    信道创建单元，被配置为创建具有不同优先级的第一公共控制信道CCCH和第二公共控制信道CCCH分别用于传输专用无线资源控制RRC消息和系统信息请求消息，所述系统信息请求消息用于请求最小系统信息以外的系统信息；
    确定单元，被配置为根据第一CCCH和第二CCCH的优先级，确定在随机接入消息3‘Msg3’中包含第一CCCH和第二CCCH中的哪一个CCCH所对应的CCCH服务数据单元SDU或者将第一CCCH和第二CCCH的CCCH SDU都包含在随机接入消息3‘Msg3’中；以及
    发送单元，被配置为将随机接入消息3‘Msg3’发送到基站。
  4. 根据权利要求3所述的UE，其中，所述专用RRC消息包括以下一个或多个：RRC连接请求消息、RRC连接重建请求消息或RRC连接恢复请求消息。
  5. 一种用户设备UE中的方法，包括：
    创建第一CCCH和第二CCCH用于以不同的优先级分别传输专用RRC消息和请求系统信息消息；
    选择与第一CCCH和第二CCCH中优先级较高的CCCH所对应的前导 序列；以及
    将所选择的前导序列发送到基站。
  6. 根据权利要求3所述的方法，其中，所述专用RRC消息包括以下一个或多个：RRC连接请求消息、RRC连接重建请求消息或RRC连接恢复请求消息。
  7. 一种用户设备UE，包括：
    信道创建单元，被配置为创建第一CCCH和第二CCCH用于以不同的优先级分别传输专用RRC消息和请求系统信息消息；
    选择单元，被配置为选择与第一CCCH和第二CCCH中优先级较高的CCCH所对应的前导序列；以及
    发送单元，被配置为将所选择的前导序列发送到基站。
  8. 根据权利要求7所述的UE，其中，所述专用RRC消息包括以下一个或多个：RRC连接请求消息、RRC连接重建请求消息或RRC连接恢复请求消息。
  9. 一种用户设备UE中的方法，包括：
    确定传输系统信息请求消息和专用RRC消息的优先级，所述系统信息请求消息用于请求最小系统信息以外的系统信息；
    根据所述优先级，在由请求系统信息消息触发的随机接入与由专用RRC消息触发的随机接入发生冲突时，选择系统信息请求消息和专用RRC消息中优先级高的消息所对应的前导序列；以及
    将所选择的前导序列发送到基站。
  10. 根据权利要求9所述的方法，其中，如果请求系统信息消息的优先级低于专用RRC消息的优先级，并且如果请求系统信息的RRC过程被触发，则所述方法还包括：
    判断是否有请求系统信息的RRC过程以外的其他RRC过程被触发或正在执行；以及
    如果有请求系统信息的RRC过程以外的其他RRC过程被触发或正在执行，则等待被触发或正在执行的其他RRC过程结束，然后再启动请求系统信息的RRC过程；或者终止请求系统信息的RRC过程。
  11. 根据权利要求9所述的方法，其中，如果请求系统信息消息的优先级低于专用消息的优先级，并且如果请求系统信息的RRC过程以外的其他 RRC过程被触发，则所述方法还包括：
    判断是否有请求系统信息的RRC过程正在执行；以及
    如果有请求系统信息的RRC过程正在执行，则终止正在执行的请求系统信息的RRC过程，并执行请求系统信息的RRC过程以外的其他RRC过程，以及在请求系统信息的RRC过程以外的其他RRC过程结束之后，重新启动请求系统信息的RRC过程。
  12. 根据权利要求9所述的方法，其中，如果请求系统信息消息的优先级高于专用RRC消息的优先级，并且如果请求系统信息的RRC过程被触发，则所述方法还包括：
    判断是否有请求系统信息的RRC过程以外的其他RRC过程被触发或正在执行；以及
    如果有请求系统信息的RRC过程以外的其他RRC过程被触发或正在执行，则终止正在执行的请求系统信息的RRC过程以外的其他RRC过程，并执行请求系统信息的RRC过程。
  13. 根据权利要求9所述的方法，其中，如果请求系统信息消息的优先级高于专用RRC消息的优先级，并且如果请求系统信息的RRC过程以外的其他RRC过程被触发，则所述方法还包括：
    判断是否有请求系统信息的RRC过程被触发或正在执行；以及
    如果有请求系统信息的RRC过程被触发或正在执行，则等待所述被触发或正在执行的请求系统信息的RRC过程结束，然后启动请求系统信息的RRC过程以外的其他RRC过程；或者终止请求系统信息的RRC过程以外的其他RRC过程。
  14. 一种用户设备UE，包括：
    确定单元，被配置为确定传输系统信息请求消息和专用RRC消息的优先级，所述系统信息请求消息用于请求最小系统信息以外的系统信息；
    选择单元，被配置为根据所述优先级，在由请求系统信息消息触发的随机接入与由专用RRC消息触发的随机接入发生冲突时，选择系统信息请求消息和专用RRC消息中优先级高的消息所对应的前导序列；以及
    发送单元，被配置为将所选择的前导序列发送到基站。
  15. 根据权利要求14所述的UE，其中，如果请求系统信息消息的优先级低于专用RRC消息的优先级，并且如果请求系统信息的RRC过程被触 发，则所述UE还包括：
    第一判断单元，被配置为判断是否有请求系统信息的RRC过程以外的其他RRC过程被触发或正在执行；以及
    第一RRC过程控制单元，被配置为：如果有请求系统信息的RRC过程以外的其他RRC过程被触发或正在执行，则等待被触发或正在执行的其他RRC过程结束，然后再启动请求系统信息的RRC过程；或者终止请求系统信息的RRC过程。
  16. 根据权利要求14所述的UE，其中，如果请求系统信息消息的优先级低于专用消息的优先级，并且如果请求系统信息的RRC过程以外的其他RRC过程被触发，则所述UE还包括：
    第二判断单元，被配置为判断是否有请求系统信息的RRC过程正在执行；以及
    第二RRC过程控制单元，被配置为：如果有请求系统信息的RRC过程正在执行，则终止正在执行的请求系统信息的RRC过程，并执行请求系统信息的RRC过程以外的其他RRC过程，以及在请求系统信息的RRC过程以外的其他RRC过程结束之后，重新启动请求系统信息的RRC过程。
  17. 根据权利要求14所述的UE，其中，如果请求系统信息消息的优先级高于专用RRC消息的优先级，并且如果请求系统信息的RRC过程被触发，则所述UE还包括：
    第三判断单元，被配置为判断是否有请求系统信息的RRC过程以外的其他RRC过程被触发或正在执行；以及
    第三RRC过程控制单元，被配置为：如果有请求系统信息的RRC过程以外的其他RRC过程被触发或正在执行，则终止正在执行的请求系统信息的RRC过程以外的其他RRC过程，并执行请求系统信息的RRC过程。
  18. 根据权利要求14所述的UE，其中，如果请求系统信息消息的优先级高于专用RRC消息的优先级，并且如果请求系统信息的RRC过程以外的其他RRC过程被触发，则所述UE还包括：
    第四判断单元，被配置为判断是否有请求系统信息的RRC过程被触发或正在执行；
    第四RRC过程控制单元，被配置为：如果有请求系统信息的RRC过程被触发或正在执行，则等待所述被触发或正在执行的请求系统信息的 RRC过程结束，然后启动请求系统信息的RRC过程以外的其他RRC过程；或者终止请求系统信息的RRC过程以外的其他RRC过程。
  19. 一种用户设备UE中的方法，包括：
    确定由请求系统信息消息触发的随机接入与由其他事件触发的随机接入的优先级，所述系统信息请求消息用于请求最小系统信息以外的系统信息；
    在由请求系统信息消息触发的随机接入与由其他事件触发的随机接入发生冲突时，选择优先级较高的随机接入所对应的前导序列；以及
    将所选择的前导序列发送到基站。
  20. 根据权利要求19所述的方法，其中，如果由请求系统信息消息触发的随机接入高于由其他事件触发的随机接入的优先级，则所述方法还包括：
    判断是否存在由请求系统信息消息触发的随机接入对应的前导序列待发送；以及
    如果存在由请求系统信息消息触发的随机接入对应的前导序列待发送，则选择由请求系统信息消息触发的随机接入所对应的前导序列。
  21. 根据权利要求20所述的方法，还包括：
    判断是否有正在执行的由其他事件触发的随机接入；
    如果有正在执行的由其他事件触发的随机接入，则中断当前正在执行的由其他随机接入触发消息触发的随机接入；以及
    选择由请求系统信息消息触发的随机接入所对应的前导序列。
  22. 根据权利要求19所述的方法，其中，如果由请求系统信息消息触发的随机接入低于由其他事件触发的随机接入的优先级，则所述方法还包括：
    判断是否存在由其他事件触发的随机接入；以及
    如果存在由其他事件触发的随机接入，则选择由其他事件触发的随机接入所对应的前导序列。
  23. 根据权利要求22所述的方法，还包括：
    判断是否有正在执行的由请求系统信息消息触发的随机接入；
    如果有正在执行的由请求系统信息消息触发的随机接入，则中断当前正在执行的由请求系统信息消息触发的随机接入；以及
    选择由其他事件触发的随机接入所对应的前导序列。
  24. 一种用户设备UE，包括：
    确定单元，被配置为确定由请求系统信息消息触发的随机接入与由其他事件触发的随机接入的优先级，所述系统信息请求消息用于请求最小系统信息以外的系统信息；
    选择单元，被配置为在由请求系统信息消息触发的随机接入与由其他事件触发的随机接入发生冲突时，选择优先级较高的随机接入所对应的前导序列；以及
    发送单元，被配置为将所选择的前导序列发送到基站。
  25. 根据权利要求24所述的UE，其中，如果由请求系统信息消息触发的随机接入高于由其他事件触发的随机接入的优先级，则所述UE还包括：
    第一判断单元，被配置为判断是否存在由请求系统信息消息触发的随机接入对应的前导序列待发送，
    其中，所述选择单元还被配置为：如果存在由请求系统信息消息触发的随机接入对应的前导序列待发送，则选择由请求系统信息消息触发的随机接入所对应的前导序列。
  26. 根据权利要求25所述的UE，其中，所述第一判断单元还被配置为判断是否有正在执行的由其他事件触发的随机接入，所述UE还包括：
    第一随机接入中断单元，被配置为：如果有正在执行的由其他事件触发的随机接入，则中断当前正在执行的由其他随机接入触发消息触发的随机接入，
    其中，所述选择单元还被配置为选择由请求系统信息消息触发的随机接入所对应的前导序列。
  27. 根据权利要求24所述的UE，其中，如果由请求系统信息消息触发的随机接入低于由其他事件触发的随机接入的优先级，则所述UE还包括：
    第二判断单元，被配置为判断是否存在由其他事件触发的随机接入，
    其中，所述选择单元还被配置为：如果存在由其他事件触发的随机接入，则选择由其他事件触发的随机接入所对应的前导序列。
  28. 根据权利要求27所述的UE，其中，所述第二判断单元还被配置为判断是否有正在执行的由请求系统信息消息触发的随机接入，所述UE还包括：
    第二随机接入中断单元，被配置为：如果有正在执行的由请求系统信息消息触发的随机接入，则中断当前正在执行的由请求系统信息消息触发的随机接入，以及
    其中，所述选择单元还被配置为选择由其他事件触发的随机接入所对应的前导序列。
  29. 一种用户设备UE中的方法，包括：
    确定由请求系统信息消息触发的随机接入与由其他事件触发的随机接入的优先级，所述系统信息请求消息用于请求最小系统信息以外的系统信息；
    在由请求系统信息消息触发的随机接入与由其他事件触发的随机接入发生冲突时，选择优先级较高的随机接入所对应的消息；以及
    通过在随机接入消息3‘Msg3’中包含所选择的消息，将所选择的消息发送到基站。
  30. 一种用户设备UE，包括：
    确定单元，被配置为确定由请求系统信息消息触发的随机接入与由其他事件触发的随机接入的优先级，所述系统信息请求消息用于请求最小系统信息以外的系统信息；
    选择单元，被配置为：在由请求系统信息消息触发的随机接入与由其他事件触发的随机接入发生冲突时，选择优先级较高的随机接入所对应的消息；以及
    发送单元，被配置为：通过在随机接入消息3‘Msg3’中包含所选择的消息，将所选择的消息发送到基站。
PCT/CN2017/117183 2016-12-22 2017-12-19 用户设备和相关方法 WO2018113664A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP17884014.6A EP3562251A1 (en) 2016-12-22 2017-12-19 User equipment and related method
US16/471,183 US20190394807A1 (en) 2016-12-22 2017-12-19 User equipment and related method

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201611204493.6 2016-12-22
CN201611204493.6A CN108235446A (zh) 2016-12-22 2016-12-22 用户设备和相关方法

Publications (1)

Publication Number Publication Date
WO2018113664A1 true WO2018113664A1 (zh) 2018-06-28

Family

ID=62624471

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/117183 WO2018113664A1 (zh) 2016-12-22 2017-12-19 用户设备和相关方法

Country Status (4)

Country Link
US (1) US20190394807A1 (zh)
EP (1) EP3562251A1 (zh)
CN (1) CN108235446A (zh)
WO (1) WO2018113664A1 (zh)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
MX2018013639A (es) * 2016-05-11 2019-05-15 Sony Corp Control distribuido en sistemas inalambricos.
CN110622570B (zh) * 2017-06-14 2022-04-12 摩托罗拉移动有限责任公司 执行用于系统信息请求的竞争解决
US11178677B2 (en) * 2017-06-27 2021-11-16 Lg Electronics Inc. Method and apparatus for configuring multiple common control channels in wireless communication system
EP3462797A1 (en) * 2017-09-28 2019-04-03 Panasonic Intellectual Property Corporation of America User equipment and base station participating in prioritized random access
US11284437B2 (en) * 2018-02-23 2022-03-22 Apple Inc. On-demand system information request procedures for new radio (NR)
CN110831260B (zh) * 2018-08-10 2022-04-22 大唐移动通信设备有限公司 Rrc连接恢复的处理方法、装置及终端
RU2769952C1 (ru) * 2018-08-14 2022-04-11 Самсунг Электроникс Ко., Лтд. Способ и оборудование для определения типа доступа к каналу в системе беспроводной связи
WO2021011281A1 (en) * 2019-07-17 2021-01-21 Google Llc Communication of segmented radio resource control messages
US11234259B2 (en) * 2020-07-15 2022-01-25 Qualcomm Incorporated Managing wireless device communication with a base station
WO2021248306A1 (en) * 2020-06-09 2021-12-16 Qualcomm Incorporated Techniques for improving random access performance

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101277517A (zh) * 2007-03-28 2008-10-01 中兴通讯股份有限公司 随机接入方法和装置
CN101541072A (zh) * 2009-04-16 2009-09-23 北京天碁科技有限公司 一种移动通信终端及其调度方法
WO2016073243A1 (en) * 2014-11-03 2016-05-12 Qualcomm Incorporated Wireless communication systems and methods having a user equipment-centric medium access control layer
WO2016198909A1 (en) * 2015-06-11 2016-12-15 Intel IP Corporation Low overhead system information acquisition for wireless communication

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101277517A (zh) * 2007-03-28 2008-10-01 中兴通讯股份有限公司 随机接入方法和装置
CN101541072A (zh) * 2009-04-16 2009-09-23 北京天碁科技有限公司 一种移动通信终端及其调度方法
WO2016073243A1 (en) * 2014-11-03 2016-05-12 Qualcomm Incorporated Wireless communication systems and methods having a user equipment-centric medium access control layer
WO2016198909A1 (en) * 2015-06-11 2016-12-15 Intel IP Corporation Low overhead system information acquisition for wireless communication

Also Published As

Publication number Publication date
US20190394807A1 (en) 2019-12-26
CN108235446A (zh) 2018-06-29
EP3562251A1 (en) 2019-10-30

Similar Documents

Publication Publication Date Title
WO2018113664A1 (zh) 用户设备和相关方法
US11751255B2 (en) Data transmission method in a wireless communication network
US11558870B2 (en) Method and device for processing carrier activation
WO2018028683A1 (zh) 执行随机接入的方法、用户设备和基站
EP3657831B1 (en) User power headroom report related method, user device and base station
KR101924704B1 (ko) 비허가 스펙트럼을 사용함으로써 통신을 수행하는 방법, 디바이스 및 시스템
TWI430693B (zh) 隨機存取通道最佳化的方法及其相關通訊裝置
WO2019192477A1 (zh) 用户设备执行的方法、基站执行的方法、用户设备和基站
JP2023545238A (ja) 無線通信システムにおけるアクセスコントロールのための方法およびユーザ機器
WO2018028681A1 (zh) 执行随机接入的方法、用户设备和基站
US11445528B2 (en) Method implemented by user equipment and user equipment
WO2018082605A1 (zh) 基站、用户设备和相关方法
WO2018082607A1 (zh) 基站、用户设备和相关方法
US20240080933A1 (en) Data transmission method and user equipment
RU2770891C2 (ru) Способ и устройство для возврата уровня управления доступом к среде в исходное состояние
WO2022199479A1 (zh) 用户设备及其执行方法
WO2020192729A1 (zh) 随机接入方法以及用户设备
WO2011124173A2 (zh) 网络拥塞处理方法和系统
WO2019154028A1 (zh) 一种控制终端接入的方法、网元、终端及系统
WO2024017184A1 (zh) 由用户设备执行的方法以及用户设备
WO2022194194A1 (zh) 在多个网络连接之间切换网络连接的方法及用户设备
RU2786625C2 (ru) Способ управления доступом и оборудование пользователя
WO2022199605A1 (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: 17884014

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2017884014

Country of ref document: EP

Effective date: 20190722