WO2020191726A1 - 系统信息请求的发送方法、装置和系统 - Google Patents

系统信息请求的发送方法、装置和系统 Download PDF

Info

Publication number
WO2020191726A1
WO2020191726A1 PCT/CN2019/080156 CN2019080156W WO2020191726A1 WO 2020191726 A1 WO2020191726 A1 WO 2020191726A1 CN 2019080156 W CN2019080156 W CN 2019080156W WO 2020191726 A1 WO2020191726 A1 WO 2020191726A1
Authority
WO
WIPO (PCT)
Prior art keywords
sul
terminal device
nul
message
request
Prior art date
Application number
PCT/CN2019/080156
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 EP19922168.0A priority Critical patent/EP3952508A4/en
Priority to PCT/CN2019/080156 priority patent/WO2020191726A1/zh
Priority to JP2021556930A priority patent/JP7449959B2/ja
Priority to CN201980093727.XA priority patent/CN113557775A/zh
Publication of WO2020191726A1 publication Critical patent/WO2020191726A1/zh
Priority to US17/476,567 priority patent/US20220007425A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access, e.g. scheduled or random access
    • H04W74/08—Non-scheduled or contention based access, e.g. random access, ALOHA, CSMA [Carrier Sense Multiple Access]
    • H04W74/0833—Non-scheduled or contention based access, e.g. random access, ALOHA, CSMA [Carrier Sense Multiple Access] using a random access procedure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H04L5/001—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT the frequencies being arranged in component carriers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/14—Access restriction or access information delivery, e.g. discovery data delivery using user query or user detection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network

Definitions

  • the present invention relates to the field of communications, and in particular to a method, device and system for sending system information requests.
  • supplementary uplink can be configured as a normal uplink (Normal UL) or non-supplementary uplink (Non-supplementary Uplink). NUL) assistance.
  • Fig. 1 is a schematic diagram of an example of using supplementary uplink. As shown in Fig. 1, in this example, the network device uses SUL to configure one downlink and two uplinks of the same cell for the terminal device.
  • network equipment can provide any of the following configurations:
  • SIB1 only includes si-RequestConfigSUL;
  • SIB1 only includes si-RequestConfig
  • SIB1 includes si-RequestConfigSUL and si-RequestConfig;
  • SIB1 does not include si-RequestConfigSUL and si-RequestConfig.
  • SIB is an abbreviation of System Information Block
  • SIB1 is a type of existing system information block.
  • SI System Information
  • the selected uplink carrier is not considered, that is, regardless of whether the selected uplink carrier is SUL (supplementary uplink) or NUL (regular uplink, non-supplementary uplink), the message 1 based SI request process;
  • the selected uplink carrier is SUL and only si-RequestConfigSUL is included in SIB1, use the SI request procedure based on message 1; otherwise, use the SI request procedure based on message 3;
  • the selected uplink carrier is NUL and only si-RequestConfig is included in SIB1, use the SI request procedure based on message 1; otherwise, use the SI request procedure based on message 3;
  • si-RequestConfigSUL and si-RequestConfig are not included in SIB1
  • the selected uplink carrier is not considered, that is, regardless of whether the selected uplink carrier is SUL (Supplementary Uplink) or NUL (Regular Uplink, Non-Supplementary Uplink), use message 3
  • SUL Serial Uplink
  • NUL Regular Uplink, Non-Supplementary Uplink
  • the configuration may not be available to the terminal device.
  • the terminal device will not be able to initiate the SI request process.
  • SIB1 contains the configuration of SUL, but the capabilities of the terminal device cannot support the use of this SUL.
  • the terminal device may determine to use SUL (that is, on the SUL) to initiate the SI request process based on message 1, but the actual The upper terminal device cannot implement this method, so that the terminal device cannot obtain the on demand system information.
  • embodiments of the present invention provide a method, device, and system for sending a system information request.
  • a method for sending a system information request which is applied to a terminal device, wherein the method includes:
  • the terminal device determines to use the system information (SI) request process based on message 1 or the SI request process based on message 3 to request the network device for on-demand system information through SUL or NUL according to whether the serving cell is configured with SUL.
  • SI system information
  • a method for configuring a system information request which is applied to a network device, wherein the method includes:
  • Network equipment configures SUL and/or NUL for terminal equipment
  • the network device receives the SI request based on message 1 or the SI request based on message 3 sent by the terminal device;
  • the network device sends on-demand system information according to the SI request.
  • an apparatus for sending a system information request which is configured in a terminal device, wherein the apparatus includes:
  • the determining unit determines whether to use the system information (SI) request process based on message 1 or the SI request process based on message 3 to request on-demand system information from the network device through SUL or NUL according to whether the serving cell is configured with SUL.
  • SI system information
  • a device for configuring a system information request which is configured in a network device, wherein the device includes:
  • a configuration unit which configures SUL and/or NUL for the terminal device
  • a receiving unit which receives the SI request based on message 1 or the SI request based on message 3 sent by the terminal device;
  • a sending unit that sends on-demand system information according to the SI request.
  • a carrier selection method applied to a terminal device wherein the method includes:
  • the terminal equipment selects the SUL carrier to perform the random access procedure, where the criteria for satisfying the selection of SUL are:
  • the carrier used by the random access process is not explicitly notified, and if the serving cell of the random access process is configured with SUL or SUL configured through dedicated signaling, and if the RSRP of the downlink path loss reference is lower than the threshold, the selection is considered to be satisfied SUL standards; or
  • the carrier used in the random access process is not explicitly notified, and if the serving cell of the random access process is configured with SUL or dedicated signaling includes the configuration information of the random access parameters on the SUL, and if the RSRP of the downlink path loss reference is lower than Threshold, it is considered to meet the criteria for selecting SUL; or
  • the carrier used by the random access process is not explicitly notified, and if the serving cell of the random access process is configured with SUL, and if the RSRP referenced by the downlink path loss is lower than the threshold.
  • a carrier selection device configured in a terminal device, wherein the device includes:
  • the selection unit when the serving cell is configured with SUL and meets the criteria for selecting the SUL, selects the SUL carrier to perform the random access procedure, where the criteria for satisfying the selection of the SUL are:
  • the carrier used by the random access process is not explicitly notified, and if the serving cell of the random access process is configured with SUL or SUL configured through dedicated signaling, and if the RSRP of the downlink path loss reference is lower than the threshold, the selection is considered to be satisfied SUL standards; or
  • the carrier used in the random access process is not explicitly notified, and if the serving cell of the random access process is configured with SUL or dedicated signaling includes the configuration information of the random access parameters on the SUL, and if the RSRP of the downlink path loss reference is lower than Threshold, it is considered to meet the criteria for selecting SUL; or
  • the carrier used by the random access process is not explicitly notified, and if the serving cell of the random access process is configured with SUL, and if the RSRP referenced by the downlink path loss is lower than the threshold.
  • a terminal device wherein the terminal device includes the device described in the foregoing third and sixth aspects.
  • a network device wherein the network device includes the apparatus described in the foregoing fourth aspect.
  • a communication system including the terminal device according to the seventh aspect and the network device according to the eighth aspect.
  • a computer-readable program is provided, wherein when the program is executed in a terminal device, the program causes the computer to execute the aforementioned first and fifth aspects in the terminal device.
  • a storage medium storing a computer-readable program, wherein the computer-readable program enables a computer to execute the method described in the first and fifth aspects in a terminal device.
  • a computer-readable program wherein when the program is executed in a network device, the program causes the computer to execute the method described in the foregoing second aspect in the network device .
  • a storage medium storing a computer-readable program, wherein the computer-readable program enables a computer to execute the method described in the foregoing second aspect in a network device.
  • the terminal device can determine whether the terminal device is configured with SUL and/or whether the terminal device supports the configuration of SUL.
  • the SI request process of message 1 or the SI request process based on message 3 can avoid selecting the wrong SI request process when the terminal device's capabilities are not supported.
  • the condition of "whether the terminal device is configured with SUL and/or whether the terminal device supports the configuration of SUL" can be integrated into a module, so that only the module needs to be called when making judgments, which optimizes the terminal implementation process and saves Cost.
  • Figure 1 is a schematic diagram of an example of using supplementary uplink
  • Figure 2 is a schematic diagram of a communication system according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of a method for sending a system information request of Embodiment 1;
  • FIG. 4 is a schematic diagram of an example of applying the method of the embodiment shown in FIG. 3;
  • FIG. 5 is a schematic diagram of another example of applying the method of the embodiment shown in FIG. 3;
  • FIG. 6 is a schematic diagram of another example of applying the method of the embodiment shown in FIG. 3;
  • FIG. 7 is another schematic diagram of the method for sending a system information request of Embodiment 1;
  • FIG. 8 is a schematic diagram of an example of applying the method of the embodiment shown in FIG. 7;
  • FIG. 9 is another schematic diagram of the method for sending a system information request of Embodiment 1;
  • FIG. 10 is a schematic diagram of an example of applying the method of the embodiment shown in FIG. 9;
  • FIG. 11 is a schematic diagram of a method for configuring a system information request of Embodiment 2;
  • FIG. 12 is a schematic diagram of the carrier selection method of Embodiment 3.
  • FIG. 13 is a schematic diagram of a system information request sending device of Embodiment 4.
  • FIG. 14 is another schematic diagram of the system information request sending device of Embodiment 4.
  • FIG. 15 is another schematic diagram of the system information request sending device of Embodiment 4.
  • FIG. 16 is a schematic diagram of a configuration device for system information request of Embodiment 5.
  • FIG. 17 is a schematic diagram of a carrier selection device of Embodiment 6;
  • FIG. 19 is a schematic diagram of a network device of Embodiment 8.
  • the terms “first”, “second”, etc. are used to distinguish different elements in terms of numelations, but they do not indicate the spatial arrangement or temporal order of these elements. These elements should not be used by these terms. Limited.
  • the term “and/or” includes any and all combinations of one or more of the associated listed terms.
  • the terms “comprising”, “including”, “having” and the like refer to the existence of the stated features, elements, elements or components, but do not exclude the presence or addition of one or more other features, elements, elements or components.
  • the term "communication network” or “wireless communication network” can refer to a network that complies with any of the following communication standards, such as Long Term Evolution (LTE), and Enhanced Long Term Evolution (LTE-A, LTE-A). Advanced), Wideband Code Division Multiple Access (WCDMA, Wideband Code Division Multiple Access), High-Speed Packet Access (HSPA, High-Speed Packet Access), etc.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution-A
  • LTE-A LTE-A
  • Advanced Wideband Code Division Multiple Access
  • WCDMA Wideband Code Division Multiple Access
  • High-Speed Packet Access High-Speed Packet Access
  • HSPA High-Speed Packet Access
  • the communication between devices in the communication system can be carried out according to any stage of communication protocol, for example, it can include but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and future 5G, New Radio (NR, New Radio), etc., and/or other currently known or future communication protocols.
  • Network device refers to, for example, a device in a communication system that connects a terminal device to a communication network and provides services for the terminal device.
  • Network equipment may include but is not limited to the following equipment: base station (BS, Base Station), access point (AP, Access Point), transmission and reception point (TRP, Transmission Reception Point), broadcast transmitter, mobile management entity (MME, Mobile Management Entity), gateway, server, radio network controller (RNC, Radio Network Controller), base station controller (BSC, Base Station Controller), etc.
  • the base station may include but is not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB), 5G base station (gNB), etc., and may also include remote radio head (RRH, Remote Radio Head), remote End radio unit (RRU, Remote Radio Unit), relay (relay), or low-power node (such as femto, pico, etc.).
  • NodeB Node B
  • eNodeB or eNB evolved Node B
  • gNB 5G base station
  • RRH Remote Radio Head
  • RRU Remote Radio Unit
  • relay relay
  • low-power node such as femto, pico, etc.
  • base station can include some or all of their functions, and each base station can provide communication coverage for a specific geographic area.
  • the term "cell” may refer to a base station and/or its coverage area, depending on the context in which the term is used.
  • the term "User Equipment” refers to, for example, a device that accesses a communication network through a network device and receives network services, and may also be referred to as "Terminal Equipment” (TE, Terminal Equipment).
  • the terminal equipment can be fixed or mobile, and can also be called a mobile station (MS, Mobile Station), terminal, user, subscriber station (SS, Subscriber Station), access terminal (AT, Access Terminal), station, etc. Wait.
  • Terminal devices may include but are not limited to the following devices: Cellular Phone, Personal Digital Assistant (PDA, Personal Digital Assistant), wireless modem, wireless communication device, handheld device, machine-type communication device, laptop computer, cordless phone , Smart phones, smart watches, digital cameras, etc.
  • PDA Personal Digital Assistant
  • wireless modem wireless communication device
  • handheld device machine-type communication device
  • laptop computer machine-type communication device
  • cordless phone Smart phones
  • smart watches digital cameras, etc.
  • a terminal device may also be a machine or device that performs monitoring or measurement.
  • it may include, but is not limited to: Machine Type Communication (MTC) terminals, Vehicle-mounted communication terminals, device to device (D2D, Device to Device) terminals, machine to machine (M2M, Machine to Machine) terminals, etc.
  • MTC Machine Type Communication
  • D2D Device to Device
  • M2M Machine to Machine
  • FIG. 2 is a schematic diagram of a communication system according to an embodiment of the present invention, schematically illustrating a case where a terminal device and a network device are taken as an example.
  • the communication system 200 may include: a network device 201 and a terminal device 202.
  • Figure 2 only uses one terminal device as an example for illustration.
  • the network device 201 is, for example, the network device gNB in the NR system.
  • eMBB enhanced mobile broadband
  • mMTC large-scale machine type communication
  • URLLC Ultra-Reliable and Low- Latency Communication
  • the terminal device 202 can send data to the network device 201, for example, using an unauthorized transmission method.
  • the network device 201 can receive data sent by one or more terminal devices 202 and feedback information to the terminal device 202, such as acknowledgement (ACK) information or non-acknowledgement (NACK) information.
  • ACK acknowledgement
  • NACK non-acknowledgement
  • the terminal device 202 can confirm the end of the transmission process according to the feedback information, Alternatively, new data transmission can be performed, or data retransmission can be performed.
  • This embodiment provides a method for sending a system information request, and the method is applied to a terminal device, such as the terminal device 202 shown in FIG. 2.
  • Fig. 3 is a schematic diagram of a method for sending a system information request in this embodiment. Please refer to Fig. 3, the method includes:
  • Step 301 The terminal device determines to use the SI request procedure based on message 1 or the SI request procedure based on message 3 according to whether the serving cell is configured with SUL to request the network device on demand through SUL or NUL (that is, on SUL or NUL) system message.
  • the terminal device can determine to use the SI request process based on Message 1 or the SI request process based on Message 3 according to "whether the serving cell is configured with SUL", which can avoid selecting the wrong one if the terminal device's capabilities are not supported. SI request process.
  • the terminal device uses the SI request process based on Message 1 on the SUL to request the network device for the above on demand system information; otherwise, if the serving cell is configured If NUL meets the criteria for selecting NUL, the terminal device uses the SI request process based on message 1 on the NUL to request the on demand system information from the network device; otherwise, the terminal device uses the SI request process based on message 3 to request the on demand from the network device. Demand system information.
  • the serving cell when one or more of the following conditions are met, it is considered that the serving cell is configured with SUL.
  • These conditions include but are not limited to:
  • SIB1 includes si-SchedulingInfo including si-RequestConfigSUL;
  • the terminal device supports one or more frequency bands (frequency bands) indicated in the frequencyBandList field of SUL;
  • the terminal device supports the initial uplink BWP bandwidth indicated in the locationAndBandwidth field of the SUL;
  • the terminal device supports one or more additionalSpectrumEmission in the NR-NS-PmaxList of the supported SUL band; or, the additionalSpectrumEmission in the SUL band supported by the terminal device is 0.
  • the serving cell when one or more of the following conditions are met, it is considered that the serving cell is configured with NUL, and these conditions include but are not limited to:
  • SIB1 includes si-SchedulingInfo including si-RequestConfig;
  • the terminal device supports one or more frequency bands (frequency bands) indicated in the frequencyBandList field of NUL;
  • the terminal device supports the initial uplink BWP bandwidth indicated in the locationAndBandwidth field of NUL;
  • the terminal device supports one or more additionalSpectrumEmission in the NR-NS-PmaxList of the supported NUL band; or, the additionalSpectrumEmission of the NUL band supported by the terminal device is 0.
  • the carrier used in the random access process is not explicitly notified, and if the serving cell of the random access process is configured with SUL or SUL is configured through dedicated signaling, and if the RSRP of the downlink path loss reference is lower than The threshold is considered to meet the criteria for selecting SUL.
  • the carrier used by the random access process is not explicitly notified, and if the serving cell of the random access process is configured with SUL or dedicated signaling includes the configuration information of the random access parameters on the SUL, and if the following If the RSRP referenced by the path loss is lower than the threshold, it is considered to meet the criteria for selecting the SUL.
  • the carrier used by the random access process is not explicitly notified, and if the serving cell of the random access process is configured with SUL, and if the RSRP of the downlink path loss reference is lower than the threshold, it is considered that the selection of SUL is satisfied.
  • the serving cell of the random access procedure is configured with SUL
  • these conditions include but not limited to:
  • the ReconfigurationWithSync field includes the rach-ConfigDedicated field containing supplementaryUplink;
  • the SCellConfig field includes the ServingCellConfig field containing supplementaryUplink;
  • the BWP-UplinkDedicated field includes the beamFailureRecoveryConfig field containing supplementaryUplink;
  • the serving cell is configured with SUL during the SI request.
  • the random access process if the SUL configuration is received from the dedicated configuration, it is considered that the serving cell is configured with SUL.
  • the serving cell is configured with SUL can also be expressed as any of the following: consider that the serving cell is configured with SUL, configured with SUL, considered configured with SUL, terminal equipment configured with SUL, considered terminal equipment configured with SUL , The terminal equipment thinks that SUL is configured, and the terminal equipment thinks that the serving cell is configured with SUL, etc. Regardless of the way of expression, the meaning is the same. And in different scenarios, there may be different expressions, which is not limited in this embodiment.
  • Fig. 4 is a schematic diagram of an example of applying the method of this embodiment.
  • the description of the request for on demand system information can be modified, for example, “if SIB1 includes si-SchedulingInfo containing si- RequestConfigSUL" is replaced with "if the serving cell is configured with supplementary uplink”, and "else if SIB1 includes si-SchedulingInfo containing si-RequestConfig" is replaced with "if the serving cell is configured with normal uplink”.
  • Figure 5 is a schematic diagram of another example of applying the method of this embodiment.
  • the description of triggering SI message acquisition can be modified, for example, an option "5>if the UE supports one" can be modified. or more of frequency bands indicated in the frequencyBandList of supplementary uplink band, and add an option "6>consider supplementary uplink as configured in the serving cell", and change the original option "6trigger to a require
  • the SI message(s) as defined in sub-clause 5.2.2.3.3” is amended to "6 Trigger a request to acquire the SI message(s) over supplementary uplink as defined in sub-clause 5.2.2.3.3".
  • the terminal device supports one or more frequency bands indicated in the frequencyBandList field of SUL" as an example of the condition that the serving cell is configured with SUL
  • the above option 5> can also be replaced with the aforementioned serving cell
  • Other conditions of SUL are configured, so the description is omitted here.
  • Fig. 6 is a schematic diagram of another example of applying the method of this embodiment.
  • restrictions on NUL can also be added, such as Add an option "5>else” and add two options under this option "6>consider normal uplink as configured in the serving cell” and "6>trigger a request to acquire the SI message(s) over normal uplink as defined in sub-clause 5.2.2.3.3".
  • the method of this embodiment determines whether to use the SI request process based on Message 1 or the SI request process based on Message 3 according to whether the serving cell is configured with SUL, which can avoid selecting the wrong SI request process when the terminal device capability is not supported.
  • condition of "the serving cell is configured with SUL" can be integrated into one module, so that only the module needs to be called when making a judgment, which optimizes the process of terminal equipment implementation and saves costs.
  • FIG. 7 is another schematic diagram of the method for sending a system information request of this embodiment. As shown in FIG. 7, the method includes:
  • Step 701 The terminal device determines whether to use the SI request procedure based on message 1 or the SI request procedure based on message 3 to pass SUL or NUL (that is, on the SUL or on the SUL) according to whether the SIB1 includes the SUL configuration and whether the terminal device can support the SUL configuration. On NUL) request on demand system information from the network device.
  • whether the serving cell is configured with SUL refers to "whether SIB1 includes the configuration of SUL and whether the terminal equipment can support the configuration of the SUL", and the terminal equipment depends on whether SIB1 includes the configuration of SUL and whether the terminal equipment can support it.
  • the SUL configuration determines to use the SI request process based on message 1 or the SI request process based on message 3, which can avoid selecting the wrong SI request process when the terminal device's capabilities are not supported.
  • SIB1 includes si-SchedulingInfo including si-RequestConfigSUL
  • the terminal device can support the configuration of SUL, and the standard for selecting SUL is satisfied
  • the terminal device can use the SI request procedure based on message 1 on the SUL to
  • the network device requests the aforementioned on demand system information; otherwise, if SIB1 includes si-SchedulingInfo including si-RequestConfig, and the terminal device can support NUL configuration, and meets the criteria for selecting NUL, the terminal device can use NUL-based message
  • the SI request process of 1 requests the network device for the above on demand system information; otherwise, the terminal device uses the SI request process based on message 3 to request the above on demand system information from the network device.
  • the terminal device can support the configuration of SUL.
  • These conditions include but are not limited to:
  • the terminal device supports one or more frequency bands (frequency bands) indicated in the frequencyBandList field of SUL;
  • the terminal device supports the initial uplink BWP bandwidth indicated in the locationAndBandwidth field of the SUL;
  • the terminal device supports one or more additionalSpectrumEmission in the NR-NS-PmaxList of the supported SUL band; or, the additionalSpectrumEmission in the SUL band supported by the terminal device is 0.
  • the terminal device can support the configuration of NUL.
  • These conditions include but are not limited to:
  • the terminal device supports one or more frequency bands (frequency bands) indicated in the frequencyBandList field of NUL;
  • the terminal device supports the initial uplink BWP bandwidth indicated in the locationAndBandwidth field of NUL;
  • the terminal device supports one or more additionalSpectrumEmission in the NR-NS-PmaxList of the supported NUL band; or, the additionalSpectrumEmission of the NUL band supported by the terminal device is 0.
  • Fig. 8 is a schematic diagram of an example of applying the method of this embodiment.
  • the description of the request for on demand system information can be modified. For example, “if SIB1 includes si-SchedulingInfo containing si -RequestConfigSUL and criteria to select supplementary uplink as defined in TS 38.321[13],clause 5.1.1is met” replaced with "if SIB1 includes si-SchedulingInfo containing si-RequestConfigSUL and if the UE supports one or more of the frequency bands indicated in the frequencyBandList of supplementary uplink and criteria to select supplementary uplink as defined in TS 38.321[13], clause 5.1.1is met”.
  • the terminal device supports one or more frequency bands indicated in the frequencyBandList field of SUL" as an example for the condition of "the terminal device supports the configuration of SUL", the above expression can also be replaced with the aforementioned " The other conditions of the “terminal device supporting SUL configuration” are omitted here.
  • the method of this embodiment determines whether to use the SI request process based on message 1 or the SI request process based on message 3 according to whether SIB1 includes the configuration of SUL and the terminal device can support the configuration of SUL, which can avoid the selection when the terminal device's capabilities are not supported. Wrong SI request process.
  • the method of this embodiment directly modifies the on demand system information request, which is flexible and can reduce debugging overhead, thereby reducing costs.
  • FIG. 9 is another schematic diagram of the method for sending a system information request of this embodiment. As shown in FIG. 9, the method includes:
  • Step 901 The terminal device determines whether to use the SI request process based on message 1 or the SI request process based on message 3 to pass SUL or NUL (that is, on SUL or on NUL) according to whether the terminal device can support the configuration of SUL and NUL. Request on demand system information from the network device.
  • whether the serving cell is configured with SUL refers to "whether the terminal device can support the configuration of SUL and NUL".
  • the terminal device determines whether the terminal device can support the configuration of SUL and the configuration of NUL according to the message-based
  • the SI request process of 1 or the SI request process based on message 3 can avoid selecting the wrong SI request process when the terminal device's capabilities are not supported.
  • the SI request for obtaining the SI message on the SUL or the SI request for obtaining the SI message on the NUL can be triggered according to the si-SchedulingInfo. If the SI request for obtaining the SI message on the SUL is triggered, and the selection of SUL is satisfied The terminal device uses the SI request process based on message 1 on the SUL to request the above on demand system information from the network device; otherwise, if the SI request to obtain the SI message on the NUL is triggered, and the NUL selection criterion is met, the terminal The device uses the SI request procedure based on message 1 on the NUL to request the above on demand system information from the network device; otherwise, the terminal device uses the SI request procedure based on message 3 to request the above on demand system information from the network device.
  • si-SchedulingInfo for the SI message "including at least one required SIB and whose si-BroadcastStatus is set to notBroadcasting", if it includes the si-SchedulingInfo of the si-RequestConfigSUL containing the SI message, and the terminal If the device can support the configuration of SUL, it triggers the SI request to obtain the SI message on the SUL; otherwise, if the si-SchedulingInfo of the si-RequestConfig that contains the SI message is included, and the terminal device can support the configuration of NUL, then the trigger is The SI request for obtaining the SI message on the NUL.
  • the above-mentioned trigger mode is only an example, and this embodiment does not limit it.
  • the conditions of "terminal equipment can support the configuration of SUL” and the conditions of "terminal equipment can support the configuration of NUL” are the same as the embodiment in FIG. 7, and the content is incorporated here, and will not be repeated here. .
  • Figure 10 is a schematic diagram of an example of applying the method of this embodiment.
  • the description of triggering SI message acquisition can be modified, for example, an option "5>if the UE supports one" more of frequency bands indicated in the frequencyBandList of supplementary uplink band, and the original option "6trigger a request to acquire the SI message(s) as defined in sub-clause 5.2.2.3.3” is changed to "6" trigger a request to acquire the SI message(s) over supplementary uplink as defined in sub-clause 5.2.2.3.3".
  • the terminal device supports one or more frequency bands indicated in the frequencyBandList field of SUL" as an example for the condition of "the configuration of the terminal device supports SUL", the above option 5> can also be replaced with The description of other conditions of the aforementioned "terminal equipment supporting SUL configuration" is omitted here.
  • an option "6>consider supplementary as configured in the serving cell" can also be added after the added option 5>.
  • the method of this embodiment first determines whether the terminal device can support the configuration of SUL and NUL, and then determines whether to use the SI request process based on message 1 or the SI request process based on message 3, which can avoid the situation that the terminal device does not support the capability Select the wrong SI request process.
  • the method of this embodiment divides the selection conditions into two levels, taking into account integration and distribution.
  • FIG. 11 is a schematic diagram of a method for configuring a system information request in this embodiment. Please refer to FIG. 11, the method includes:
  • Step 1101 The network device configures SUL and/or NUL for the terminal device;
  • Step 1102 The network device receives the SI request based on message 1 or the SI request based on message 3 sent by the terminal device;
  • Step 1103 The network device sends on-demand system information according to the SI request.
  • the network device may send SIB1 to the terminal device.
  • the SIB1 includes si-SchedulingInfo including si-RequestConfigSUL, or the SIB1 includes si-SchedulingInfo including si-RequestConfig.
  • the terminal device can confirm whether the serving cell is configured with SUL and/or whether the terminal device supports the configuration of SUL and/or whether the terminal device supports the configuration of SUL and NUL, and then determines whether to use the system information (SI) based on message 1
  • the request process still uses the SI request process based on message 3 to request on-demand system information from the network device.
  • the aforementioned on-demand system information may be an SI message "including at least one required SIB and whose si-BroadcastStatus is set to notBroadcasting", and this embodiment is not limited to this.
  • FIG. 12 is a schematic diagram of the carrier selection method of this embodiment. As shown in FIG. 12, the method includes:
  • Step 1201 The terminal device selects the SUL carrier to perform the random access procedure when the SUL is configured in the serving cell and the SUL selection criterion is met, where the SUL selection criterion is satisfied:
  • the carrier used by the random access process is not explicitly notified, and if the serving cell of the random access process is configured with SUL or SUL configured through dedicated signaling, and if the RSRP of the downlink path loss reference is lower than the threshold, the selection is considered to be satisfied SUL standards; or
  • the carrier used in the random access process is not explicitly notified, and if the serving cell of the random access process is configured with SUL or dedicated signaling includes the configuration information of the random access parameters on the SUL, and if the RSRP of the downlink path loss reference is lower than Threshold, it is considered to meet the criteria for selecting SUL; or
  • the carrier used by the random access process is not explicitly notified, and if the serving cell of the random access process is configured with SUL, and if the RSRP referenced by the downlink path loss is lower than the threshold.
  • the conditions that the serving cell is configured with SUL include one or more of the following conditions, that is, the terminal device can consider that the serving cell is configured when one or more of the following conditions are met.
  • the ReconfigurationWithSync field includes the rach-ConfigDedicated field containing supplementaryUplink;
  • the SCellConfig field includes the ServingCellConfig field containing supplementaryUplink;
  • the BWP-UplinkDedicated field includes the beamFailureRecoveryConfig field containing supplementaryUplink;
  • the terminal device can obtain the SUL configuration from the dedicated signaling, and perform random access according to the SUL configuration provided in the dedicated signaling.
  • This embodiment provides an apparatus for sending system information requests.
  • the apparatus is configured in a terminal device. Since the principle of the apparatus to solve the problem is similar to the method in Embodiment 1, the specific implementation can refer to Embodiment 1. The content is the same The description will not be repeated.
  • FIG. 13 is a schematic diagram of the apparatus for sending a system information request in this embodiment. As shown in FIG. 13, the apparatus 1300 includes:
  • the determining unit 1301 determines to use the system information (SI) request process based on message 1 or the SI request process based on message 3 to request on-demand system information from the network device through the SUL or NUL according to whether the serving cell is configured with SUL.
  • SI system information
  • the determining unit 1301 includes a first selection unit 13011, if the serving cell is configured with the SUL and meets the criteria for selecting the SUL, the first selection unit 13011 uses the SI request process based on Message 1 on the SUL; otherwise If the serving cell is configured with NUL and meets the criteria for selecting NUL, the first selection unit 13011 uses the SI request process based on message 1 on the NUL; otherwise, the first selection unit 13011 uses the SI request process based on message 3.
  • the serving cell is configured with SUL:
  • SIB1 includes si-SchedulingInfo including si-RequestConfigSUL;
  • the terminal device supports one or more frequency bands indicated in the frequencyBandList field of SUL;
  • the terminal device supports the initial uplink BWP bandwidth indicated in the locationAndBandwidth field of the SUL;
  • the terminal device supports one or more additionalSpectrumEmission in the NR-NS-PmaxList of the supported SUL band; or, the additionalSpectrumEmission in the SUL band supported by the terminal device is 0.
  • the serving cell is configured with NUL:
  • SIB1 includes si-SchedulingInfo including si-RequestConfig;
  • the terminal device supports one or more frequency bands indicated in the frequencyBandList field of NUL;
  • the terminal device supports the initial uplink BWP bandwidth indicated in the locationAndBandwidth field of NUL;
  • the terminal device supports one or more additionalSpectrumEmission in the NR-NS-PmaxList of the supported NUL band; or, the additionalSpectrumEmission of the NUL band supported by the terminal device is 0.
  • meeting the criteria for selecting SUL refers to:
  • the carrier used by the random access process is not explicitly notified, and if the serving cell of the random access process is configured with SUL or SUL is configured through dedicated signaling, and if the RSRP of the downlink path loss reference is lower than the threshold; or
  • the carrier used in the random access process is not explicitly notified, and if the serving cell of the random access process is configured with SUL or dedicated signaling includes the configuration information of the random access parameters on the SUL, and if the RSRP of the downlink path loss reference is lower than Threshold; or
  • the carrier used by the random access process is not explicitly notified, and if the serving cell of the random access process is configured with SUL, and if the RSRP referenced by the downlink path loss is lower than the threshold.
  • the serving cell of the random access procedure is configured with SUL
  • the serving cell is considered to be configured with SUL:
  • the ReconfigurationWithSync field includes the rach-ConfigDedicated field containing supplementaryUplink;
  • the SCellConfig field includes the ServingCellConfig field containing supplementaryUplink;
  • the BWP-UplinkDedicated field includes the beamFailureRecoveryConfig field containing supplementaryUplink;
  • FIG. 14 is another schematic diagram of the apparatus for sending a system information request in this embodiment. As shown in FIG. 14, the apparatus 1400 includes:
  • the determining unit 1401 which determines whether to use the system information (SI) request process based on message 1 or the SI request process based on message 3 to the network through SUL or NUL according to whether SIB1 includes the configuration of SUL and whether the terminal device can support the configuration of SUL
  • SIB1 includes the configuration of SUL and whether the terminal device can support the configuration of SUL
  • the device requests on-demand system information.
  • the determining unit 1401 includes a second selection unit 14011. If SIB1 includes si-SchedulingInfo including si-RequestConfigSUL, and the terminal device can support the configuration of SUL, and meets the criteria for selecting SUL, the second selection unit 14011 uses the SI request process based on message 1 on SUL; otherwise, if SIB1 includes si-SchedulingInfo containing si-RequestConfig, and the terminal device can support NUL configuration, and meets the criteria for selecting NUL, the second selection unit 14011 uses The SI request process based on message 1 on the NUL; otherwise, the second selection unit 14011 uses the SI request process based on message 3.
  • the terminal device can support the configuration of SUL:
  • the terminal device supports one or more frequency bands indicated in the frequencyBandList field of SUL;
  • the terminal device supports the initial uplink BWP bandwidth indicated in the locationAndBandwidth field of the SUL;
  • the terminal device supports one or more additionalSpectrumEmission in the NR-NS-PmaxList of the supported SUL band; or, the additionalSpectrumEmission in the SUL band supported by the terminal device is 0.
  • the terminal device can support the NUL configuration:
  • the terminal device supports one or more frequency bands indicated in the frequencyBandList field of NUL;
  • the terminal device supports the initial uplink BWP bandwidth indicated in the locationAndBandwidth field of NUL;
  • the terminal device supports one or more additionalSpectrumEmission in the NR-NS-PmaxList of the supported NUL band; or, the additionalSpectrumEmission of the NUL band supported by the terminal device is 0.
  • FIG. 15 is another schematic diagram of the apparatus for sending a system information request in this embodiment. As shown in FIG. 15, the apparatus 1500 includes:
  • a determining unit 1501 which determines to use the system information (SI) request process based on message 1 or the SI request process based on message 3 to request an on-demand system from the network device through SUL or NUL according to whether the terminal device can support the configuration of SUL and NUL information.
  • SI system information
  • the determination unit 1501 includes a trigger unit 15011 and a third selection unit 15012.
  • the trigger unit 15011 is used to trigger the SI request to obtain the SI message on the SUL or the SI request to obtain the SI message on the NUL according to the si-SchedulingInfo; if the SI request to obtain the SI message on the SUL is triggered, and the criteria for selecting SUL are met, Then the third selection unit 15012 uses the SI request process based on Message 1 on the SUL; otherwise, if the SI request to obtain the SI message on the NUL is triggered and the criteria for selecting NUL are met, the third selection unit 15012 uses the message 1 based on the NUL SI request process; otherwise, the third selection unit 15012 uses the SI request process based on message 3.
  • si-SchedulingInfo for an SI message that includes at least one required SIB and whose si-BroadcastStatus is set to notBroadcasting, if it includes the si-SchedulingInfo of si-RequestConfigSUL that contains the SI message, and the terminal device can If the configuration of the SUL is supported, the trigger unit 15011 triggers the SI request to obtain the above SI message on the SUL; otherwise, if the si-SchedulingInfo of the si-RequestConfig containing the SI message is included, and the terminal device can support the NUL The trigger unit 15011 triggers the SI request to obtain the above-mentioned SI message on the NUL.
  • the terminal device can support the configuration of SUL:
  • the terminal device supports one or more frequency bands indicated in the frequencyBandList field of SUL;
  • the terminal device supports the initial uplink BWP bandwidth indicated in the locationAndBandwidth field of the SUL;
  • the terminal device supports one or more additionalSpectrumEmission in the NR-NS-PmaxList of the supported SUL band; or, the additionalSpectrumEmission in the SUL band supported by the terminal device is 0.
  • the terminal device can support the NUL configuration:
  • the terminal device supports one or more frequency bands indicated in the frequencyBandList field of NUL;
  • the terminal device supports the initial uplink BWP bandwidth indicated in the locationAndBandwidth field of NUL;
  • the terminal device supports one or more additionalSpectrumEmission in the NR-NS-PmaxList of the supported NUL band; or, the additionalSpectrumEmission of the NUL band supported by the terminal device is 0.
  • This embodiment also provides a device for configuring system information requests.
  • the device is configured on a network device. Since the principle of the device to solve the problem is similar to the method in embodiment 2, the specific implementation can refer to embodiment 2, and the content is the same. The description will not be repeated here.
  • FIG. 16 is a schematic diagram of an apparatus 1600 for configuring a system information request in this embodiment.
  • the apparatus 1600 includes: a configuration unit 1601, a receiving unit 1602, and a sending unit 1603.
  • the configuration unit 1601 is used to configure SUL and/or NUL for the terminal device;
  • the receiving unit 1602 is used to receive the SI request based on Message 1 or the SI request based on Message 3 sent by the terminal device;
  • the sending unit 1603 is used to configure SUL and/or NUL according to the SI Request to send on-demand system information.
  • the configuration unit 1601 may send SIB1 to the terminal device.
  • the SIB1 includes si-SchedulingInfo including si-RequestConfigSUL, or the SIB1 includes si-SchedulingInfo including si-RequestConfig.
  • the terminal device can determine to use the system information (SI) request process based on message 1 or the SI request process based on message 3 to request on-demand system information from the network device through SUL or NUL (that is, on SUL or NUL), Regarding the processing of the terminal device, the description has been made in Embodiment 1, and will not be repeated here.
  • SI system information
  • the aforementioned on-demand system information may be an SI message "including at least one required SIB and whose si-BroadcastStatus is set to notBroadcasting", and this embodiment is not limited to this.
  • This embodiment provides a carrier selection device, which is configured in terminal equipment. Since the principle of the device to solve the problem is similar to the method in embodiment 3, the specific implementation can refer to embodiment 3, and the same content will not be repeated. Description.
  • FIG. 17 is a schematic diagram of a carrier selection device 1700 of this embodiment. As shown in FIG. 17, the device 1700 includes:
  • the selection unit 1701 when the serving cell is configured with SUL and meets the criteria for selecting SUL, selects the SUL carrier to perform the random access procedure, where the criteria for satisfying the selection of SUL are:
  • the carrier used by the random access process is not explicitly notified, and if the serving cell of the random access process is configured with SUL or SUL configured through dedicated signaling, and if the RSRP of the downlink path loss reference is lower than the threshold, the selection is considered to be satisfied SUL standards; or
  • the carrier used in the random access process is not explicitly notified, and if the serving cell of the random access process is configured with SUL or dedicated signaling includes the configuration information of the random access parameters on the SUL, and if the RSRP of the downlink path loss reference is lower than Threshold, it is considered to meet the criteria for selecting SUL; or
  • the carrier used by the random access process is not explicitly notified, and if the serving cell of the random access process is configured with SUL, and if the RSRP referenced by the downlink path loss is lower than the threshold.
  • the serving cell is configured with SUL:
  • the ReconfigurationWithSync field includes the rach-ConfigDedicated field containing supplementaryUplink;
  • the SCellConfig field includes the ServingCellConfig field containing supplementaryUplink;
  • the BWP-UplinkDedicated field includes the beamFailureRecoveryConfig field containing supplementaryUplink;
  • the terminal equipment can obtain the SUL configuration from the dedicated signaling, and perform random access according to the SUL configuration provided in the dedicated signaling.
  • An embodiment of the present invention also provides a terminal device, where the terminal device includes the device described in Embodiment 4 or 6.
  • Fig. 18 is a schematic diagram of a terminal device according to an embodiment of the present invention.
  • the terminal device 1800 may include a central processing unit 1801 and a memory 1802; the memory 1802 is coupled to the central processing unit 1801. It is worth noting that this figure is exemplary; other types of structures can also be used to supplement or replace this structure to achieve telecommunication functions or other functions.
  • the function of the device described in embodiment 4 or 6 can be integrated into the central processing unit 1801, and the central processing unit 1801 realizes the function of the device described in embodiment 4 or 6, which is related to embodiment 4 Or the functions of the device described in 6 are incorporated here, and will not be repeated here.
  • the device described in embodiment 4 or 6 can be configured separately from the central processing unit 1801.
  • the device described in embodiment 4 or 6 can be configured as a chip connected to the central processing unit 1801, through The control of the central processing unit 1801 realizes the functions of the device described in Embodiment 4 or 6.
  • the terminal device 1800 may further include: a communication module 1803, an input unit 1804, an audio processing unit 1805, a display 1806, and a power supply 1807. It is worth noting that the terminal device 1800 does not necessarily include all the components shown in FIG. 18; in addition, the terminal device 1800 may also include components not shown in FIG. 18, and the prior art can be referred to.
  • the central processing unit 1801 is sometimes called a controller or an operating control, and may include a microprocessor or other processor devices and/or logic devices.
  • the central processing unit 1801 receives input and controls each of the terminal equipment 1800 Operation of components.
  • the memory 1802 may be, for example, one or more of a cache, a flash memory, a hard drive, a removable medium, a volatile memory, a non-volatile memory, or other suitable devices.
  • the above information related to the configuration can be stored, in addition to the program that executes the related information.
  • the central processing unit 1801 can execute the program stored in the memory 1802 to implement information storage or processing.
  • the functions of other components are similar to the existing ones, so I won't repeat them here.
  • Each component of the terminal device 1800 can be implemented by dedicated hardware, firmware, software, or a combination thereof, without departing from the scope of the present invention.
  • the terminal device of this embodiment it is possible to avoid selecting the wrong SI request process when the terminal device's capabilities are not supported, or to obtain the SUL configuration from the dedicated signaling, and according to the SUL configuration provided in the dedicated signaling Perform random access.
  • the embodiment of the present invention also provides a network device, wherein the network device includes the device described in Embodiment 5.
  • FIG. 19 is a schematic diagram of an implementation manner of a network device according to an embodiment of the present invention.
  • the network device 1900 may include: a central processing unit (CPU) 1901 and a memory 1902; the memory 1902 is coupled to the central processing unit 1901.
  • the memory 1902 can store various data; in addition, it also stores information processing programs, and executes the programs under the control of the central processing unit 1901 to receive various information sent by the terminal device and send various information to the terminal device.
  • the functions of the device described in embodiment 5 can be integrated into the central processing unit 1901, and the central processing unit 1901 realizes the functions of the device described in embodiment 5, which is related to the device described in embodiment 5
  • the functions of is incorporated here, so I won’t repeat them here.
  • the device described in embodiment 5 can be configured separately from the central processing unit 1901.
  • the device described in embodiment 5 can be a chip connected to the central processing unit 1901, and the device can be configured by the central processing unit 1901. Control to realize the function of the device described in the fifth embodiment.
  • the network device 1900 may further include: a transceiver 1903, an antenna 1904, etc.; wherein the functions of the above-mentioned components are similar to those of the prior art, and will not be repeated here. It is worth noting that the network device 1900 does not necessarily include all the components shown in FIG. 19; in addition, the network device 1900 may also include components not shown in FIG. 19, and the prior art can be referred to.
  • An embodiment of the present invention also provides a communication system, which includes a network device and a terminal device.
  • the network device is, for example, the network device 1900 described in Embodiment 8
  • the terminal device is, for example, the terminal device 1800 described in Embodiment 7.
  • the terminal device is, for example, a UE served by gNB.
  • the terminal device also includes the conventional composition and functions of the terminal device. As described in Embodiment 7, This will not be repeated here.
  • the network device may be, for example, the gNB in NR.
  • the network device In addition to the functions of the device described in Embodiment 5, it also includes the regular composition and functions of the network device. As described in Embodiment 8, here No longer.
  • the embodiment of the present invention also provides a computer-readable program, wherein when the program is executed in the terminal device, the program causes the computer to execute the method described in Embodiment 1 or 3 in the terminal device.
  • An embodiment of the present invention also provides a storage medium storing a computer-readable program, wherein the computer-readable program enables a computer to execute the method described in Embodiment 1 or 3 in a terminal device.
  • the embodiment of the present invention also provides a computer-readable program, wherein when the program is executed in the network device, the program causes the computer to execute the method described in Embodiment 2 in the network device.
  • An embodiment of the present invention also provides a storage medium storing a computer-readable program, wherein the computer-readable program enables a computer to execute the method described in Embodiment 2 in a network device.
  • the above devices and methods of the present invention can be implemented by hardware, or by hardware combined with software.
  • the present invention relates to such a computer-readable program, when the program is executed by a logic component, the logic component can realize the above-mentioned device or constituent component, or the logic component can realize the above-mentioned various methods Or steps.
  • Logic components such as field programmable logic components, microprocessors, processors used in computers, etc.
  • the present invention also relates to storage media for storing the above programs, such as hard disks, magnetic disks, optical disks, DVDs, flash memory, and the like.
  • the method/device described in conjunction with the embodiments of the present invention may be directly embodied as hardware, a software module executed by a processor, or a combination of the two.
  • one or more of the functional block diagrams and/or one or more combinations of the functional block diagrams shown in the figure may correspond to each software module of the computer program flow or each hardware module.
  • These software modules can respectively correspond to the steps shown in the figure.
  • These hardware modules can be implemented by curing these software modules by using a field programmable gate array (FPGA), for example.
  • FPGA field programmable gate array
  • the software module can be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM or any other form of storage medium known in the art.
  • a storage medium may be coupled to the processor, so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be a component of the processor.
  • the processor and the storage medium may be located in the ASIC.
  • the software module can be stored in the memory of the mobile terminal, or can be stored in a memory card that can be inserted into the mobile terminal.
  • the software module can be stored in the MEGA-SIM card or a large-capacity flash memory device.
  • One or more of the functional blocks and/or one or more combinations of the functional blocks described in the drawings can be implemented as general-purpose processors, digital signal processors (DSPs) for performing the functions described in the present invention. ), Application Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component or any appropriate combination thereof.
  • DSPs digital signal processors
  • ASIC Application Specific Integrated Circuit
  • FPGA Field Programmable Gate Array
  • One or more of the functional blocks described in the drawings and/or one or more combinations of the functional blocks can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, or multiple micro-processing DSP, one or more microprocessors or any other device combined with DSP communication.

Abstract

本发明提供了一种系统信息请求的发送方法、装置和系统，该方法包括：终端设备根据服务小区是否配置了SUL确定使用基于消息1的系统信息(SI)请求过程或者基于消息3的SI请求过程通过SUL或NUL向网络设备请求按需系统信息。根据本发明实施例，能够避免在终端设备能力不支持的情况下选择错误的SI请求过程。

Description

系统信息请求的发送方法、装置和系统 技术领域
本发明涉及通信领域，特别涉及一种系统信息请求的发送方法、装置和系统。
背景技术
在新无线(NR，New Radio)里，为了改善高频场景的上行覆盖，可以配置补充上行(Supplementary Uplink，SUL)，作为常规上行(Normal UL，NUL)或非补充上行(Non-supplementary Uplink，NUL)的辅助。图1是使用补充上行的一个示例的示意图，如图1所示，在这个示例中，网络设备使用SUL为终端设备配置了相同小区的一个下行和两个上行。通常情况下，网络设备可以提供以下配置的任意一种：
SIB1中只包括si-RequestConfigSUL；
SIB1中只包括si-RequestConfig；
SIB1中包括si-RequestConfigSUL和si-RequestConfig；
SIB1中不包括si-RequestConfigSUL和si-RequestConfig。
其中，SIB是系统信息块(System Information Block)的简写，SIB1是现有的系统信息块的一种类型。
另一方面，对于空闲态或非激活态的终端设备，可以通过执行系统信息(SI，System Information)请求以获取按需(on demand)系统信息。目前，有两种执行SI请求的方法，即基于消息1的SI请求过程和基于消息3的SI请求过程。通常情况下，可以根据以下原则决定是执行基于消息1的SI请求过程，还是执行基于消息3的SI请求过程。
在SIB1中包括si-RequestConfigSUL和si-RequestConfig的情况下，不考虑选择的上行载波，即不管选择的上行载波是SUL(补充上行)还是NUL(常规上行，非补充上行)，使用基于消息1的SI请求过程；
如果选择的上行载波是SUL，并且，SIB1中只包括si-RequestConfigSUL，则使用基于消息1的SI请求过程，否则使用基于消息3的SI请求过程；
如果选择的上行载波是NUL，并且，SIB1中只包括si-RequestConfig，则使用基于消息1的SI请求过程，否则使用基于消息3的SI请求过程；
在SIB1中不包括si-RequestConfigSUL和si-RequestConfig的情况下，不考虑选择的上行载波，即不管选择的上行载波是SUL(补充上行)还是NUL(常规上行，非补充上行)，使用基于消息3的SI请求过程。
应该注意，上面对技术背景的介绍只是为了方便对本发明的技术方案进行清楚、完整的说明，并方便本领域技术人员的理解而阐述的。不能仅仅因为这些方案在本发明的背景技术部分进行了阐述而认为上述技术方案为本领域技术人员所公知。
发明内容
发明人发现，基于当前机制，只要SIB1中包含了相关配置，如si-RequestConfigSUL或si-RequestConfig，该配置对终端设备就是可用的。但是，当考虑到终端设备的能力时，即便SIB1中包含了相关配置，该配置对终端设备可能是不可用的。这种情况下，如果仍采用当前的SI请求过程的原则，终端设备将无法发起SI请求过程。例如，SIB1中包含SUL的配置，但终端设备的能力无法支持这个SUL的使用，根据当前原则，终端设备有可能确定使用SUL(也即在SUL上)发起基于消息1的SI请求过程，而实际上终端设备无法实现该方法，从而导致终端设备无法获得on demand系统信息。
为了解决上述问题中的至少一个或者解决其他类似问题，本发明实施例提供了一种系统信息请求的发送方法、装置和系统。
根据本发明实施例的第一方面，提供了一种系统信息请求的发送方法，应用于终端设备，其中，所述方法包括：
终端设备根据服务小区是否配置了SUL确定使用基于消息1的系统信息(SI)请求过程或者基于消息3的SI请求过程通过SUL或NUL向网络设备请求按需系统信息。
根据本发明实施例的第二方面，提供了一种系统信息请求的配置方法，应用于网络设备，其中，所述方法包括：
网络设备为终端设备配置SUL和/或NUL；
所述网络设备接收所述终端设备发送的基于消息1的SI请求或者基于消息3的SI请求；
所述网络设备根据所述SI请求发送按需系统信息。
根据本发明实施例的第三方面，提供了一种系统信息请求的发送装置，配置于终端设备，其中，所述装置包括：
确定单元，其根据服务小区是否配置了SUL确定使用基于消息1的系统信息(SI)请求过程或者基于消息3的SI请求过程通过SUL或NUL向网络设备请求按需系统信息。
根据本发明实施例的第四方面，提供了一种系统信息请求的配置装置，配置于网络设备，其中，所述装置包括：
配置单元，其为终端设备配置SUL和/或NUL；
接收单元，其接收所述终端设备发送的基于消息1的SI请求或者基于消息3的SI请求；
发送单元，其根据所述SI请求发送按需系统信息。
根据本发明实施例的第五方面，提供了一种载波选择方法，应用于终端设备，其中，所述方法包括：
终端设备在服务小区配置了SUL并且满足选择SUL的标准的情况下，选择SUL载波执行随机接入过程，其中，满足选择SUL的标准为：
如果没有显式通知随机接入过程使用的载波，且如果随机接入过程的服务小区配置了SUL或通过专用信令配置了SUL，且如果下行路损参考的RSRP低于阈值，则认为满足选择SUL的标准；或者
如果没有显式通知随机接入过程使用的载波，且如果随机接入过程的服务小区配置了SUL或专用信令包括SUL上随机接入参数的配置信息，且如果下行路损参考的RSRP低于阈值，则认为满足选择SUL的标准；或者
如果没有显式通知随机接入过程使用的载波，且如果随机接入过程的服务小区配置了SUL，且如果下行路损参考的RSRP低于阈值。
根据本发明实施例的第六方面，提供了一种载波选择装置，配置于终端设备，其中，所述装置包括：
选择单元，其在服务小区配置了SUL并且满足选择SUL的标准的情况下，选择SUL载波执行随机接入过程，其中，满足选择SUL的标准为：
如果没有显式通知随机接入过程使用的载波，且如果随机接入过程的服务小区配置了SUL或通过专用信令配置了SUL，且如果下行路损参考的RSRP低于阈值，则 认为满足选择SUL的标准；或者
如果没有显式通知随机接入过程使用的载波，且如果随机接入过程的服务小区配置了SUL或专用信令包括SUL上随机接入参数的配置信息，且如果下行路损参考的RSRP低于阈值，则认为满足选择SUL的标准；或者
如果没有显式通知随机接入过程使用的载波，且如果随机接入过程的服务小区配置了SUL，且如果下行路损参考的RSRP低于阈值。
根据本发明实施例的第七方面，提供了一种终端设备，其中，所述终端设备包括前述第三、六方面所述的装置。
根据本发明实施例的第八方面，提供了一种网络设备，其中，所述网络设备包括前述第四方面所述的装置。
根据本发明实施例的第九方面，提供了一种通信系统，所述通信系统包括前述第七方面所述的终端设备和前述第八方面所述的网络设备。
根据本发明实施例的其它方面，提供了一种计算机可读程序，其中当在终端设备中执行所述程序时，所述程序使得计算机在所述终端设备中执行前述第一、五方面所述的方法。
根据本发明实施例的其它方面，提供了一种存储有计算机可读程序的存储介质，其中所述计算机可读程序使得计算机在终端设备中执行前述第一、五方面所述的方法。
根据本发明实施例的其它方面，提供了一种计算机可读程序，其中当在网络设备中执行所述程序时，所述程序使得计算机在所述网络设备中执行前述第二方面所述的方法。
根据本发明实施例的其它方面，提供了一种存储有计算机可读程序的存储介质，其中所述计算机可读程序使得计算机在网络设备中执行前述第二方面所述的方法。
本发明实施例的有益效果在于：根据本发明实施例的至少一个方面，终端设备能够根据“终端设备是否配置了SUL和/或终端设备能否支持SUL的配置”确定在SUL或NUL上使用基于消息1的SI请求过程或基于消息3的SI请求过程，能够避免在终端设备能力不支持的情况下选择错误的SI请求过程。此外，“终端设备是否配置了SUL和/或终端设备能否支持SUL的配置”的条件可以集成为一个模块，使得在进行判断时仅需要调用该模块即可，优化了终端实现的过程，节约了成本。
参照后文的说明和附图，详细公开了本发明的特定实施方式，指明了本发明的原理可以被采用的方式。应该理解，本发明的实施方式在范围上并不因而受到限制。在所附权利要求的精神和条款的范围内，本发明的实施方式包括许多改变、修改和等同。
针对一种实施方式描述和/或示出的特征可以以相同或类似的方式在一个或更多个其它实施方式中使用，与其它实施方式中的特征相组合，或替代其它实施方式中的特征。
应该强调，术语“包括/包含”在本文使用时指特征、整件、步骤或组件的存在，但并不排除一个或更多个其它特征、整件、步骤或组件的存在或附加。
附图说明
在本发明实施例的一个附图或一种实施方式中描述的元素和特征可以与一个或更多个其它附图或实施方式中示出的元素和特征相结合。此外，在附图中，类似的标号表示几个附图中对应的部件，并可用于指示多于一种实施方式中使用的对应部件。
所包括的附图用来提供对本发明实施例的进一步的理解，其构成了说明书的一部分，用于例示本发明的实施方式，并与文字描述一起来阐释本发明的原理。显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其它的附图。在附图中：
图1是使用补充上行的一个示例的示意图；
图2是本发明实施例的通信系统的示意图；
图3是实施例1的系统信息请求的发送方法的一个示意图；
图4是应用图3所示的实施例的方法的一个示例的示意图；
图5是应用图3所示的实施例的方法的另一个示例的示意图；
图6是应用图3所示的实施例的方法的再一个示例的示意图；
图7是实施例1的系统信息请求的发送方法的另一个示意图；
图8是应用图7所示的实施例的方法的一个示例的示意图；
图9是实施例1的系统信息请求的发送方法的再一个示意图；
图10是应用图9所示的实施例的方法的一个示例的示意图；
图11是实施例2的系统信息请求的配置方法的示意图；
图12是实施例3的载波选择方法的示意图；
图13是实施例4的系统信息请求的发送装置的一个示意图；
图14是实施例4的系统信息请求的发送装置的另一个示意图；
图15是实施例4的系统信息请求的发送装置的再一个示意图；
图16是实施例5的系统信息请求的配置装置的示意图；
图17是实施例6的载波选择装置的示意图；
图18是实施例7的终端设备的示意图；
图19是实施例8的网络设备的示意图。
具体实施方式
参照附图，通过下面的说明书，本发明的前述以及其它特征将变得明显。在说明书和附图中，具体公开了本发明的特定实施方式，其表明了其中可以采用本发明的原则的部分实施方式，应了解的是，本发明不限于所描述的实施方式，相反，本发明包括落入所附权利要求的范围内的全部修改、变型以及等同物。
在本发明实施例中，术语“第一”、“第二”等用于对不同元素从称谓上进行区分，但并不表示这些元素的空间排列或时间顺序等，这些元素不应被这些术语所限制。术语“和/或”包括相关联列出的术语的一种或多个中的任何一个和所有组合。术语“包含”、“包括”、“具有”等是指所陈述的特征、元素、元件或组件的存在，但并不排除存在或添加一个或多个其他特征、元素、元件或组件。
在本发明实施例中，单数形式“一”、“该”等包括复数形式，应广义地理解为“一种”或“一类”而并不是限定为“一个”的含义；此外术语“所述”应理解为既包括单数形式也包括复数形式，除非上下文另外明确指出。此外术语“根据”应理解为“至少部分根据……”，术语“基于”应理解为“至少部分基于……”，除非上下文另外明确指出。
在本发明实施例中，术语“通信网络”或“无线通信网络”可以指符合如下任意通信标准的网络，例如长期演进(LTE，Long Term Evolution)、增强的长期演进(LTE-A，LTE-Advanced)、宽带码分多址接入(WCDMA，Wideband Code Division Multiple Access)、高速报文接入(HSPA，High-Speed Packet Access)等等。
并且，通信系统中设备之间的通信可以根据任意阶段的通信协议进行，例如可以包括但不限于如下通信协议：1G(generation)、2G、2.5G、2.75G、3G、4G、4.5G 以及未来的5G、新无线(NR，New Radio)等等，和/或其他目前已知或未来将被开发的通信协议。
在本发明实施例中，术语“网络设备”例如是指通信系统中将终端设备接入通信网络并为该终端设备提供服务的设备。网络设备可以包括但不限于如下设备：基站(BS，Base Station)、接入点(AP、Access Point)、发送接收点(TRP，Transmission Reception Point)、广播发射机、移动管理实体(MME、Mobile Management Entity)、网关、服务器、无线网络控制器(RNC，Radio Network Controller)、基站控制器(BSC，Base Station Controller)等等。
基站可以包括但不限于：节点B(NodeB或NB)、演进节点B(eNodeB或eNB)以及5G基站(gNB)，等等，此外还可包括远端无线头(RRH，Remote Radio Head)、远端无线单元(RRU，Remote Radio Unit)、中继(relay)或者低功率节点(例如femto、pico等等)。并且术语“基站”可以包括它们的一些或所有功能，每个基站可以对特定的地理区域提供通信覆盖。术语“小区”可以指的是基站和/或其覆盖区域，这取决于使用该术语的上下文。
在本发明实施例中，术语“用户设备”(UE，User Equipment)例如是指通过网络设备接入通信网络并接收网络服务的设备，也可以称为“终端设备”(TE，Terminal Equipment)。终端设备可以是固定的或移动的，并且也可以称为移动台(MS，Mobile Station)、终端、用户、用户台(SS，Subscriber Station)、接入终端(AT，Access Terminal)、站，等等。
终端设备可以包括但不限于如下设备：蜂窝电话(Cellular Phone)、个人数字助理(PDA，Personal Digital Assistant)、无线调制解调器、无线通信设备、手持设备、机器型通信设备、膝上型计算机、无绳电话、智能手机、智能手表、数字相机，等等。
再例如，在物联网(IoT，Internet of Things)等场景下，终端设备还可以是进行监控或测量的机器或装置，例如可以包括但不限于：机器类通信(MTC，Machine Type Communication)终端、车载通信终端、设备到设备(D2D，Device to Device)终端、机器到机器(M2M，Machine to Machine)终端，等等。
以下通过示例对本发明实施例的场景进行说明，但本发明实施例不限于此。
图2是本发明实施例的通信系统的示意图，示意性说明了以终端设备和网络设备为例的情况，如图2所示，通信系统200可以包括：网络设备201和终端设备202。 为简单起见，图2仅以一个终端设备为例进行说明。网络设备201例如为NR系统中的网络设备gNB。
在本发明实施例中，网络设备201和终端设备202之间可以进行现有的业务或者未来可实施的业务。例如，这些业务包括但不限于：增强的移动宽带(eMBB，enhanced Mobile Broadband)、大规模机器类型通信(mMTC，massive Machine Type Communication)和高可靠低时延通信(URLLC，Ultra-Reliable and Low-Latency Communication)，等等。
终端设备202可以向网络设备201发送数据，例如使用免授权传输方式。网络设备201可以接收一个或多个终端设备202发送的数据，并向终端设备202反馈信息，例如确认(ACK)信息或非确认(NACK)信息，终端设备202根据反馈信息可以确认结束传输过程、或者还可以再进行新的数据传输，或者可以进行数据重传。
下面结合附图对本发明的各种实施方式进行说明。这些实施方式只是示例性的，不是对本发明的限制。
实施例1
本实施例提供了一种系统信息请求的发送方法，该方法应用于终端设备，例如图2所示的终端设备202。
图3是本实施例的系统信息请求的发送方法的一个示意图，请参照图3，该方法包括：
步骤301：终端设备根据服务小区是否配置了SUL确定使用基于消息1的SI请求过程或者基于消息3的SI请求过程通过SUL或NUL(也即在SUL上或在NUL上)向网络设备请求on demand系统信息。
在本实施例中，终端设备能够根据“服务小区是否配置了SUL”确定使用基于消息1的SI请求过程或基于消息3的SI请求过程，能够避免在终端设备能力不支持的情况下选择错误的SI请求过程。
在本实施例中，如果服务小区配置了SUL并且满足选择SUL的标准，则终端设备使用该SUL上基于消息1的SI请求过程向网络设备请求上述on demand系统信息；否则，如果服务小区配置了NUL并且满足选择NUL的标准，则终端设备使用该NUL上基于消息1的SI请求过程向网络设备请求上述on demand系统信息；否则，终端设备使用基于消息3的SI请求过程向网络设备请求上述on demand系统信息。
在本实施例中，在满足下面一个条件或多个条件的情况下，认为服务小区配置了SUL，这些条件包括但不限于：
SIB1包括包含si-RequestConfigSUL的si-SchedulingInfo；
终端设备支持SUL的frequencyBandList域里指示的一个或多个频带(frequency bands)；
终端设备支持SUL的locationAndBandwidth域里指示的初始上行BWP的带宽；
终端设备支持支持的SUL频带的NR-NS-PmaxList里的一个或多个additionalSpectrumEmission；或者，终端设备支持支持的SUL频带里的additionalSpectrumEmission为0。
在本实施例中，在满足下面一个条件或多个条件的情况下，认为服务小区配置了NUL，这些条件包括但不限于：
SIB1包括包含si-RequestConfig的si-SchedulingInfo；
终端设备支持NUL的frequencyBandList域里指示的一个或多个频带(frequency bands)；
终端设备支持NUL的locationAndBandwidth域里指示的初始上行BWP的带宽；
终端设备支持支持的NUL频带的NR-NS-PmaxList里的一个或多个additionalSpectrumEmission；或者，终端设备支持支持的NUL频带的additionalSpectrumEmission为0。
在本实施例中，关于满足选择SUL的标准：
在一个实施方式中，如果没有显式通知随机接入过程使用的载波，且如果随机接入过程的服务小区配置了SUL或通过专用信令配置了SUL，且如果下行路损参考的RSRP低于阈值，则认为满足选择SUL的标准。
在另一个实施方式中，如果没有显式通知随机接入过程使用的载波，且如果随机接入过程的服务小区配置了SUL或专用信令包括SUL上随机接入参数的配置信息，且如果下行路损参考的RSRP低于阈值，则认为满足选择SUL的标准。
在再一个实施方式中，如果没有显式通知随机接入过程使用的载波，且如果随机接入过程的服务小区配置了SUL，且如果下行路损参考的RSRP低于阈值，则认为满足选择SUL的标准。
在本实施例中，在满足选择SUL的标准包括“随机接入过程的服务小区配置了 SUL”的情况下，如果满足下面一个条件或多个条件，认为服务小区配置了SUL，这些条件包括但不限于：
ReconfigurationWithSync域里包括包含supplementaryUplink的rach-ConfigDedicated域；
SCellConfig域里包括包含supplementaryUplink的ServingCellConfig域；
BWP-UplinkDedicated域里包括包含supplementaryUplink的beamFailureRecoveryConfig域；以及
存在supplementaryUplink域。
在本实施方式中，与前述在进行SI请求时判断服务小区是否配置了SUL不同，在随机接入过程中，如果从专用配置里接收到SUL配置，则认为服务小区配置了SUL。
在本实施例中，“服务小区配置了SUL”也可以表述为下面任意一种：认为服务小区配置了SUL，配置了SUL，认为配置了SUL，终端设备配置了SUL，认为终端设备配置了SUL，终端设备认为配置了SUL，终端设备认为服务小区配置了SUL等，无论表述方式如何，其代表的含义都相同。并且在不同的场景里，可以有不同表述，本实施例对此不作限制。
在本实施例中，对“满足NUL的标准”的条件不作限制，现有的“满足NUL的标准”的条件适用于本申请。
图4是应用本实施例的方法的一个示例的示意图，如图4所示，在当前标准中，可以修改对于on demand系统信息的请求的描述，例如，将“if SIB1includes si-SchedulingInfo containing si-RequestConfigSUL”替换为“if the serving cell is configured with supplementary uplink”，并将“else if SIB1includes si-SchedulingInfo containing si-RequestConfig”替换为“if the serving cell is configured with normal uplink”。
图5是应用本实施例的方法的另一个示例的示意图，如图5所示，在当前标准中，可以修改对于触发SI消息获取的描述，例如，增加一个选项“5﹥if the UE supports one or more of frequency bands indicated in the frequencyBandList of supplementary uplink band”，并在该选项下增加一个选项“6﹥consider supplementary uplink as configured in the serving cell”，并将原来的选项“6﹥trigger a request to acquire the SI message(s)as  defined in sub-clause 5.2.2.3.3”修改为“6﹥trigger a request to acquire the SI message(s)over supplementary uplink as defined in sub-clause 5.2.2.3.3”。
在图5的示例中，以“终端设备支持SUL的frequencyBandList域里指示的一个或多个频带”作为服务小区配置了SUL的条件为例进行了说明，上述选项5﹥也可以替换为前述服务小区配置了SUL的其他条件，此处省略说明。
图6是应用本实施例的方法的另一个示例的示意图，如图6所示，在当前标准中，基于图5所示对当前标准中相关描述的修改，还可以增加针对NUL的限制，例如增加一个选项“5﹥else”，并在该选项下增加两个选项“6﹥consider normal uplink as configured in the serving cell”和“6﹥trigger a request to acquire the SI message(s)over normal uplink as defined in sub-clause 5.2.2.3.3”。
在图6的示例中，选项“6﹥consider normal uplink as configured in the serving cell”也可以替换为“6﹥consider supplementary uplink as not configured in the serving cell”。
本实施例的方法根据服务小区是否配置了SUL确定使用基于消息1的SI请求过程或基于消息3的SI请求过程，能够避免在终端设备能力不支持的情况下选择错误的SI请求过程。
在本实施例中，“服务小区配置了SUL”的条件可以集成为一个模块，使得在进行判断时仅需要调用该模块即可，优化了终端设备实现的过程，节约了成本。
图7是本实施例的系统信息请求的发送方法的另一个示意图，如图7所示，该方法包括：
步骤701：终端设备根据SIB1是否包括SUL的配置以及终端设备能否支持该SUL的配置确定使用基于消息1的SI请求过程或者基于消息3的SI请求过程通过SUL或NUL(也即在SUL上或者在NUL上)向网络设备请求on demand系统信息。
在本实施例中，“服务小区是否配置了SUL”是指“SIB1是否包括SUL的配置以及终端设备能否支持该SUL的配置”，终端设备根据SIB1是否包括SUL的配置以及终端设备能否支持该SUL的配置确定使用基于消息1的SI请求过程或基于消息3的SI请求过程，能够避免在终端设备能力不支持的情况下选择错误的SI请求过程。
在本实施例中，如果SIB1包括包含si-RequestConfigSUL的si-SchedulingInfo，并且终端设备能够支持SUL的配置，并且，满足选择SUL的标准，则终端设备可以使用SUL上基于消息1的SI请求过程向网络设备请求上述on demand系统信息；否则， 如果SIB1包括包含si-RequestConfig的si-SchedulingInfo，并且，终端设备能够支持NUL的配置，并且，满足选择NUL的标准，则终端设备可以使用NUL上基于消息1的SI请求过程向网络设备请求上述on demand系统信息；否则，终端设备使用基于消息3的SI请求过程向网络设备请求上述on demand系统信息。
在本实施例中，在满足下面一个条件或多个条件的情况下，认为终端设备能够支持SUL的配置，这些条件包括但不限于：
终端设备支持SUL的frequencyBandList域里指示的一个或多个频带(frequency bands)；
终端设备支持SUL的locationAndBandwidth域里指示的初始上行BWP的带宽；
终端设备支持支持的SUL频带的NR-NS-PmaxList里的一个或多个additionalSpectrumEmission；或者，终端设备支持支持的SUL频带里的additionalSpectrumEmission为0。
在本实施例中，在满足下面一个条件或多个条件的情况下，认为终端设备能够支持NUL的配置，这些条件包括但不限于：
终端设备支持NUL的frequencyBandList域里指示的一个或多个频带(frequency bands)；
终端设备支持NUL的locationAndBandwidth域里指示的初始上行BWP的带宽；
终端设备支持支持的NUL频带的NR-NS-PmaxList里的一个或多个additionalSpectrumEmission；或者，终端设备支持支持的NUL频带的additionalSpectrumEmission为0。
图8是应用本实施例的方法的一个示例的示意图，如图8所示，在当前标准中，可以修改对于on demand系统信息的请求的描述，例如，将“if SIB1 includes si-SchedulingInfo containing si-RequestConfigSUL and criteria to select supplementary uplink as defined in TS 38.321[13],clause 5.1.1is met”替换为“if SIB1 includes si-SchedulingInfo containing si-RequestConfigSUL  and if the UE supports one or more  of the frequency bands indicated in the frequencyBandList of supplementary uplink and criteria to select supplementary uplink as defined in TS 38.321[13],clause 5.1.1is met”。
在图8的示例中，以“终端设备支持SUL的frequencyBandList域里指示的一个 或多个频带”作为“终端设备支持SUL的配置”的条件为例进行了说明，上述表述也可以替换为前述“终端设备支持SUL的配置”的其他条件，此处省略说明。
关于“终端设备支持NUL的配置”的条件也可以相应补充或替换当前标准，此处省略说明。
本实施例的方法根据SIB1是否包括SUL的配置以及终端设备能够支持SUL的配置确定使用基于消息1的SI请求过程或基于消息3的SI请求过程，能够避免在终端设备能力不支持的情况下选择错误的SI请求过程。
此外，本实施例的方法直接对on demand系统信息的请求进行了修改，实现灵活，能减小调试开销，从而降低成本。
图9是本实施例的系统信息请求的发送方法的再一个示意图，如图9所示，该方法包括：
步骤901：终端设备根据终端设备能否支持SUL的配置和NUL的配置确定使用基于消息1的SI请求过程或者基于消息3的SI请求过程通过SUL或NUL(也即在SUL上或者在NUL上)向网络设备请求on demand系统信息。
在本实施例中，“服务小区是否配置了SUL”是指“终端设备能否支持SUL的配置和NUL的配置”，终端设备根据终端设备能否支持SUL的配置和NUL的配置确定使用基于消息1的SI请求过程或基于消息3的SI请求过程，能够避免在终端设备能力不支持的情况下选择错误的SI请求过程。
在本实施例中，可以根据si-SchedulingInfo触发在SUL上获取SI消息的SI请求或者触发在NUL上获取SI消息的SI请求，如果触发了在SUL上获取SI消息的SI请求，并且满足选择SUL的标准，则终端设备使用SUL上基于消息1的SI请求过程向网络设备请求上述on demand系统信息；否则，如果触发了在NUL上获取SI消息的SI请求，并且满足选择NUL的标准，则终端设备使用NUL上基于消息1的SI请求过程向网络设备请求上述on demand系统信息；否则，终端设备使用基于消息3的SI请求过程向网络设备请求上述on demand系统信息。
在一个实施方式中，根据si-SchedulingInfo，对于“包括至少一个要求的SIB且其si-BroadcastStatus置为notBroadcasting的”SI消息，如果包括包含所述SI消息的si-RequestConfigSUL的si-SchedulingInfo，并且终端设备能够支持SUL的配置，则触发在SUL上获取该SI消息的SI请求；否则，如果包括包含所述SI消息的 si-RequestConfig的si-SchedulingInfo，并且终端设备能够支持NUL的配置，则触发在所述NUL上获取该SI消息的SI请求。
上述触发方式只是举例说明，本实施例对此不作限制。
在本实施例中，关于“终端设备能够支持SUL的配置”的条件和“终端设备能够支持NUL的配置”的条件与图7的实施方式相同，其内容被合并于此，此处不再赘述。
图10是应用本实施例的方法的一个示例的示意图，如图10所示，在当前标准中，可以修改对于触发SI消息获取的描述，例如，增加一个选项“5﹥if the UE supports one or more of frequency bands indicated in the frequencyBandList of supplementary uplink band”，并将原来的选项“6﹥trigger a request to acquire the SI message(s)as defined in sub-clause 5.2.2.3.3”修改为“6﹥trigger a request to acquire the SI message(s)over supplementary uplink as defined in sub-clause 5.2.2.3.3”。
在图10的示例中，以“终端设备支持SUL的frequencyBandList域里指示的一个或多个频带”作为“终端设备支持SUL的配置”的条件为例进行了说明，上述选项5﹥也可以替换为前述“终端设备支持SUL的配置”的其他条件，此处省略说明。
在图10的示例中，与图5的示例类似，也可以在增加的选项5﹥后面增加一个选项“6﹥consider supplementary uplink as configured in the serving cell”。
关于“终端设备支持NUL的配置”的条件也可以相应补充或替换当前标准，此处省略说明。
本实施例的方法先确定终端设备能否支持SUL的配置和NUL的配置，再确定使用基于消息1的SI请求过程或基于消息3的SI请求过程，能够避免在终端设备能力不支持的情况下选择错误的SI请求过程。
此外，本实施例的方法将选择的条件分成两个级别，兼顾了集成性和分布性。
实施例2
本实施例提供了一种系统信息请求的配置方法，该方法应用于网络设备，其是对应实施例1的方法的网络侧的处理，其中与实施例1相同的内容不再重复说明。图11是本实施例的系统信息请求的配置方法的示意图，请参照图11，该方法包括：
步骤1101：网络设备为终端设备配置SUL和/或NUL；
步骤1102：所述网络设备接收所述终端设备发送的基于消息1的SI请求或者基于消息3的SI请求；
步骤1103：所述网络设备根据所述SI请求发送按需系统信息。
在本实施例中，网络设备可以向终端设备发送SIB1，该SIB1包括包含si-RequestConfigSUL的si-SchedulingInfo，或者该SIB1包括包含si-RequestConfig的si-SchedulingInfo。终端设备据此可以确认服务小区是否配置了SUL和/或终端设备是否支持SUL的配置和/或终端设备是否支持SUL的配置和NUL的配置，进而决定是使用基于消息1的系统信息(SI)请求过程还是使用基于消息3的SI请求过程向网络设备请求按需系统信息。
在本实施例中，上述按需系统信息可以是“包括至少一个要求的SIB且其si-BroadcastStatus置为notBroadcasting的”SI消息，本实施例不限于此。
通过本实施例的方法，能够避免在终端设备能力不支持的情况下选择错误的SI请求过程。
实施例3
本实施例提供了一种载波选择方法，该方法应用于终端设备。图12是本实施例的载波选择方法的示意图，如图12所示，该方法包括：
步骤1201：终端设备在服务小区配置了SUL并且满足选择SUL的标准的情况下，选择SUL载波执行随机接入过程，其中，满足选择SUL的标准为：
如果没有显式通知随机接入过程使用的载波，且如果随机接入过程的服务小区配置了SUL或通过专用信令配置了SUL，且如果下行路损参考的RSRP低于阈值，则认为满足选择SUL的标准；或者
如果没有显式通知随机接入过程使用的载波，且如果随机接入过程的服务小区配置了SUL或专用信令包括SUL上随机接入参数的配置信息，且如果下行路损参考的RSRP低于阈值，则认为满足选择SUL的标准；或者
如果没有显式通知随机接入过程使用的载波，且如果随机接入过程的服务小区配置了SUL，且如果下行路损参考的RSRP低于阈值。
在本实施例中，关于上述满足选择SUL的标准，已经在实施例1中做了说明，其内容被合并于此，此处不再赘述。
在本实施例中，对于上述专用信令中提供的SUL配置，只要该专用信令中提供了SUL配置，则认为配置了SUL。
例如，可以在域描述或过程描述里指明认为服务小区配置了SUL的条件包括以下一个或多个情况，也即终端设备可以在满足下面一个条件或多个条件的情况下，认为服务小区配置了SUL：
ReconfigurationWithSync域里包括包含supplementaryUplink的rach-ConfigDedicated域；
SCellConfig域里包括包含supplementaryUplink的ServingCellConfig域；
BWP-UplinkDedicated域里包括包含supplementaryUplink的beamFailureRecoveryConfig域；以及
存在supplementaryUplink域。
通过本实施例的方法，终端设备可以从专用信令中获得SUL的配置，并根据专用信令里提供的该SUL配置进行随机接入。
实施例4
本实施例提供了一种系统信息请求的发送装置，该装置配置于终端设备，由于该装置解决问题的原理与实施例1的方法类似，其具体的实施可以参考实施例1，内容相同之处不再重复说明。
图13是本实施例的系统信息请求的发送装置的一个示意图，如图13所示，该装置1300包括：
确定单元1301，其根据服务小区是否配置了SUL确定使用基于消息1的系统信息(SI)请求过程或者基于消息3的SI请求过程通过SUL或NUL向网络设备请求按需系统信息。
在一个实施方式中，该确定单元1301包括第一选择单元13011，如果服务小区配置了所述SUL并且满足选择SUL的标准，第一选择单元13011使用该SUL上基于消息1的SI请求过程；否则，如果服务小区配置了NUL并且满足选择NUL的标准，第一选择单元13011使用该NUL上基于消息1的SI请求过程；否则，第一选择单元13011使用基于消息3的SI请求过程。
在本实施方式中，在满足下面一个条件或多个条件的情况下，认为服务小区配置 了SUL：
SIB1包括包含si-RequestConfigSUL的si-SchedulingInfo；
终端设备支持SUL的frequencyBandList域里指示的一个或多个频带；
终端设备支持SUL的locationAndBandwidth域里指示的初始上行BWP的带宽；
终端设备支持支持的SUL频带的NR-NS-PmaxList里的一个或多个additionalSpectrumEmission；或者，终端设备支持支持的SUL频带里的additionalSpectrumEmission为0。
在本实施方式中，在满足下面一个条件或多个条件的情况下，认为服务小区配置了NUL：
SIB1包括包含si-RequestConfig的si-SchedulingInfo；
终端设备支持NUL的frequencyBandList域里指示的一个或多个频带；
终端设备支持NUL的locationAndBandwidth域里指示的初始上行BWP的带宽；
终端设备支持支持的NUL频带的NR-NS-PmaxList里的一个或多个additionalSpectrumEmission；或者，终端设备支持支持的NUL频带的additionalSpectrumEmission为0。
在本实施方式中，满足选择SUL的标准是指：
如果没有显式通知随机接入过程使用的载波，且如果随机接入过程的服务小区配置了SUL或通过专用信令配置了SUL，且如果下行路损参考的RSRP低于阈值；或者
如果没有显式通知随机接入过程使用的载波，且如果随机接入过程的服务小区配置了SUL或专用信令包括SUL上随机接入参数的配置信息，且如果下行路损参考的RSRP低于阈值；或者
如果没有显式通知随机接入过程使用的载波，且如果随机接入过程的服务小区配置了SUL，且如果下行路损参考的RSRP低于阈值。
在本实施方式中，在满足选择SUL的标准包括“随机接入过程的服务小区配置了SUL”情况下，如果满足下面一个条件或多个条件，认为服务小区配置了SUL：
ReconfigurationWithSync域里包括包含supplementaryUplink的rach-ConfigDedicated域；
SCellConfig域里包括包含supplementaryUplink的ServingCellConfig域；
BWP-UplinkDedicated域里包括包含supplementaryUplink的beamFailureRecoveryConfig域；以及
存在supplementaryUplink域。
图14是本实施例的系统信息请求的发送装置的另一个示意图，如图14所示，该装置1400包括：
确定单元1401，其根据SIB1是否包括SUL的配置以及终端设备能否支持所述SUL的配置确定使用基于消息1的系统信息(SI)请求过程或者基于消息3的SI请求过程通过SUL或NUL向网络设备请求按需系统信息。
在一个实施方式中，该确定单元1401包括第二选择单元14011，如果SIB1包括包含si-RequestConfigSUL的si-SchedulingInfo，并且终端设备能够支持SUL的配置，并且，满足选择SUL的标准，第二选择单元14011使用SUL上基于消息1的SI请求过程；否则，如果SIB1包括包含si-RequestConfig的si-SchedulingInfo，并且，终端设备能够支持NUL的配置，并且，满足选择NUL的标准，第二选择单元14011使用NUL上基于消息1的SI请求过程；否则，第二选择单元14011使用基于消息3的SI请求过程。
在本实施方式中，在满足下面一个条件或多个条件的情况下，认为终端设备能够支持SUL的配置：
终端设备支持SUL的frequencyBandList域里指示的一个或多个频带；
终端设备支持SUL的locationAndBandwidth域里指示的初始上行BWP的带宽；
终端设备支持支持的SUL频带的NR-NS-PmaxList里的一个或多个additionalSpectrumEmission；或者，终端设备支持支持的SUL频带里的additionalSpectrumEmission为0。
在本实施方式中，在满足下面一个条件或多个条件的情况下，认为终端设备能够支持NUL的配置：
终端设备支持NUL的frequencyBandList域里指示的一个或多个频带；
终端设备支持NUL的locationAndBandwidth域里指示的初始上行BWP的带宽；
终端设备支持支持的NUL频带的NR-NS-PmaxList里的一个或多个additionalSpectrumEmission；或者，终端设备支持支持的NUL频带的additionalSpectrumEmission为0。
图15是本实施例的系统信息请求的发送装置的再一个示意图，如图15所示，该装置1500包括：
确定单元1501，其根据终端设备能否支持SUL的配置和NUL的配置确定使用基于消息1的系统信息(SI)请求过程或者基于消息3的SI请求过程通过SUL或NUL向网络设备请求按需系统信息。
在一个实施方式中，该确定单元1501包括触发单元15011和第三选择单元15012。触发单元15011用于根据si-SchedulingInfo触发在SUL上获取SI消息的SI请求或者触发在NUL上获取SI消息的SI请求；如果触发在SUL上获取SI消息的SI请求，并且满足选择SUL的标准，则第三选择单元15012使用SUL上基于消息1的SI请求过程；否则，如果触发在NUL上获取SI消息的SI请求，并且满足选择NUL的标准，第三选择单元15012使用NUL上基于消息1的SI请求过程；否则，第三选择单元15012使用基于消息3的SI请求过程。
在本实施方式中，根据si-SchedulingInfo，对于包括至少一个要求的SIB且其si-BroadcastStatus置为notBroadcasting的SI消息，如果包括包含所述SI消息的si-RequestConfigSUL的si-SchedulingInfo，并且终端设备能够支持所述SUL的配置，则触发单元15011触发在该SUL上获取上述SI消息的SI请求；否则，如果包括包含所述SI消息的si-RequestConfig的si-SchedulingInfo，并且终端设备能够支持所述NUL的配置，则触发单元15011触发在该NUL上获取上述SI消息的SI请求。
在本实施方式中，在满足下面一个条件或多个条件的情况下，认为终端设备能够支持SUL的配置：
终端设备支持SUL的frequencyBandList域里指示的一个或多个频带；
终端设备支持SUL的locationAndBandwidth域里指示的初始上行BWP的带宽；
终端设备支持支持的SUL频带的NR-NS-PmaxList里的一个或多个additionalSpectrumEmission；或者，终端设备支持支持的SUL频带里的additionalSpectrumEmission为0。
在本实施方式中，在满足下面一个条件或多个条件的情况下，认为终端设备能够支持NUL的配置：
终端设备支持NUL的frequencyBandList域里指示的一个或多个频带；
终端设备支持NUL的locationAndBandwidth域里指示的初始上行BWP的带宽；
终端设备支持支持的NUL频带的NR-NS-PmaxList里的一个或多个additionalSpectrumEmission；或者，终端设备支持支持的NUL频带的additionalSpectrumEmission为0。
通过本实施例的装置，能够避免在终端设备能力不支持的情况下选择错误的SI请求过程。
实施例5
本实施例还提供了一种系统信息请求的配置装置，该装置配置于网络设备，由于该装置解决问题的原理与实施例2的方法类似，其具体的实施可以参考实施例2，内容相同之处不再重复说明。
图16是本实施例的系统信息请求的配置装置1600的示意图，如图16所示，该装置1600包括：配置单元1601、接收单元1602和发送单元1603。配置单元1601用于为终端设备配置SUL和/或NUL；接收单元1602用于接收所述终端设备发送的基于消息1的SI请求或者基于消息3的SI请求；发送单元1603用于根据所述SI请求发送按需系统信息。
在本实施例中，配置单元1601可以向终端设备发送SIB1，该SIB1包括包含si-RequestConfigSUL的si-SchedulingInfo，或者该SIB1包括包含si-RequestConfig的si-SchedulingInfo。终端设备据此可以确定使用基于消息1的系统信息(SI)请求过程或者基于消息3的SI请求过程通过SUL或NUL(也即在SUL上或者在NUL上)向网络设备请求按需系统信息，关于终端设备的处理，已经在实施例1中做了说明，此处不再赘述。
在本实施例中，上述按需系统信息可以为“包括至少一个要求的SIB且其si-BroadcastStatus置为notBroadcasting的”SI消息，本实施例不限于此。
通过本实施例的装置，能够避免在终端设备能力不支持的情况下选择错误的SI请求过程。
实施例6
本实施例提供了一种载波选择装置，该装置配置于终端设备，由于该装置解决问题的原理与实施例3的方法类似，其具体的实施可以参考实施例3，内容相同之处不 再重复说明。
图17是本实施例的载波选择装置1700的示意图，如图17所示，该装置1700包括：
选择单元1701，其在服务小区配置了SUL并且满足选择SUL的标准的情况下，选择SUL载波执行随机接入过程，其中，满足选择SUL的标准为：
如果没有显式通知随机接入过程使用的载波，且如果随机接入过程的服务小区配置了SUL或通过专用信令配置了SUL，且如果下行路损参考的RSRP低于阈值，则认为满足选择SUL的标准；或者
如果没有显式通知随机接入过程使用的载波，且如果随机接入过程的服务小区配置了SUL或专用信令包括SUL上随机接入参数的配置信息，且如果下行路损参考的RSRP低于阈值，则认为满足选择SUL的标准；或者
如果没有显式通知随机接入过程使用的载波，且如果随机接入过程的服务小区配置了SUL，且如果下行路损参考的RSRP低于阈值。
在本实施例中，在满足下面一个条件或多个条件的情况下，认为服务小区配置了SUL：
ReconfigurationWithSync域里包括包含supplementaryUplink的rach-ConfigDedicated域；
SCellConfig域里包括包含supplementaryUplink的ServingCellConfig域；
BWP-UplinkDedicated域里包括包含supplementaryUplink的beamFailureRecoveryConfig域；以及
存在supplementaryUplink域。
通过本实施例的装置，终端设备可以从专用信令中获得SUL的配置，并根据专用信令里提供的该SUL配置进行随机接入。
实施例7
本发明实施例还提供了一种终端设备，其中，该终端设备包括实施例4或6所述的装置。
图18是本发明实施例的终端设备的示意图。如图18所示，该终端设备1800可以包括中央处理器1801和存储器1802；存储器1802耦合到中央处理器1801。值得 注意的是，该图是示例性的；还可以使用其它类型的结构，来补充或代替该结构，以实现电信功能或其它功能。
在一个实施方式中，实施例4或6所述的装置的功能可以被集成到中央处理器1801中，由中央处理器1801实现实施例4或6所述的装置的功能，其中关于实施例4或6所述的装置的功能被合并于此，在此不再赘述。
在另一个实施方式中，实施例4或6所述的装置可以与中央处理器1801分开配置，例如可以将该实施例4或6所述的装置配置为与中央处理器1801连接的芯片，通过中央处理器1801的控制来实现该实施例4或6所述的装置的功能。
如图18所示，该终端设备1800还可以包括：通信模块1803、输入单元1804、音频处理单元1805、显示器1806、电源1807。值得注意的是，终端设备1800也并不是必须要包括图18中所示的所有部件；此外，终端设备1800还可以包括图18中没有示出的部件，可以参考现有技术。
如图18所示，中央处理器1801有时也称为控制器或操作控件，可以包括微处理器或其它处理器装置和/或逻辑装置，该中央处理器1801接收输入并控制终端设备1800的各个部件的操作。
其中，存储器1802，例如可以是缓存器、闪存、硬驱、可移动介质、易失性存储器、非易失性存储器或其它合适装置中的一种或更多种。可储存上述与配置有关的信息，此外还可存储执行有关信息的程序。并且中央处理器1801可执行该存储器1802存储的该程序，以实现信息存储或处理等。其它部件的功能与现有类似，此处不再赘述。终端设备1800的各部件可以通过专用硬件、固件、软件或其结合来实现，而不偏离本发明的范围。
通过本实施例的终端设备，能够避免在终端设备能力不支持的情况下选择错误的SI请求过程，或者，可以从专用信令中获得SUL的配置，并根据专用信令里提供的该SUL配置进行随机接入。
实施例8
本发明实施例还提供了一种网络设备，其中，该网络设备包括实施例5所述的装置。
图19是本发明实施例的网络设备的一个实施方式的构成示意图。如图19所示， 网络设备1900可以包括：中央处理器(CPU)1901和存储器1902；存储器1902耦合到中央处理器1901。其中该存储器1902可存储各种数据；此外还存储信息处理的程序，并且在中央处理器1901的控制下执行该程序，以接收终端设备发送的各种信息、并且向终端设备发送各种信息。
在一个实施方式中，实施例5所述的装置的功能可以被集成到中央处理器1901中，由中央处理器1901实现实施例5所述的装置的功能，其中关于实施例5所述的装置的功能被合并于此，在此不再赘述。
在另一个实施方式中，实施例5所述的装置可以与中央处理器1901分开配置，例如可以将该实施例5所述的装置为与中央处理器1901连接的芯片，通过中央处理器1901的控制来实现该实施例5所述的装置的功能。
此外，如图19所示，网络设备1900还可以包括：收发机1903和天线1904等；其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，网络设备1900也并不是必须要包括图19中所示的所有部件；此外，网络设备1900还可以包括图19中没有示出的部件，可以参考现有技术。
通过本实施例的网络设备，能够避免在终端设备能力不支持的情况下选择错误的SI请求过程。
实施例9
本发明实施例还提供一种通信系统，该通信系统包括网络设备和终端设备，网络设备例如为实施例8所述的网络设备1900，终端设备例如为实施例7所述的终端设备1800。
在本实施例中，该终端设备例如是gNB服务的UE，其除了包含实施例4或6所述的装置的功能以外，还包括终端设备的常规组成和功能，如实施例7所述，在此不再赘述。
在本实施例中，该网络设备例如可以是NR中的gNB，其除了包含实施例5所述的装置的功能以外，还包括网络设备的常规组成和功能，如实施例8所述，在此不再赘述。
通过本实施例的通信系统，能够避免在终端设备能力不支持的情况下选择错误的SI请求过程。
本发明实施例还提供一种计算机可读程序，其中当在终端设备中执行所述程序时，所述程序使得计算机在所述终端设备中执行实施例1或3所述的方法。
本发明实施例还提供一种存储有计算机可读程序的存储介质，其中所述计算机可读程序使得计算机在终端设备中执行实施例1或3所述的方法。
本发明实施例还提供一种计算机可读程序，其中当在网络设备中执行所述程序时，所述程序使得计算机在所述网络设备中执行实施例2所述的方法。
本发明实施例还提供一种存储有计算机可读程序的存储介质，其中所述计算机可读程序使得计算机在网络设备中执行实施例2所述的方法。
本发明以上的装置和方法可以由硬件实现，也可以由硬件结合软件实现。本发明涉及这样的计算机可读程序，当该程序被逻辑部件所执行时，能够使该逻辑部件实现上文所述的装置或构成部件，或使该逻辑部件实现上文所述的各种方法或步骤。逻辑部件例如现场可编程逻辑部件、微处理器、计算机中使用的处理器等。本发明还涉及用于存储以上程序的存储介质，如硬盘、磁盘、光盘、DVD、flash存储器等。
结合本发明实施例描述的方法/装置可直接体现为硬件、由处理器执行的软件模块或二者组合。例如，图中所示的功能框图中的一个或多个和/或功能框图的一个或多个组合，既可以对应于计算机程序流程的各个软件模块，亦可以对应于各个硬件模块。这些软件模块，可以分别对应于图中所示的各个步骤。这些硬件模块例如可利用现场可编程门阵列(FPGA)将这些软件模块固化而实现。
软件模块可以位于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动磁盘、CD-ROM或者本领域已知的任何其它形式的存储介质。可以将一种存储介质耦接至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息；或者该存储介质可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。该软件模块可以存储在移动终端的存储器中，也可以存储在可插入移动终端的存储卡中。例如，若设备(如移动终端)采用的是较大容量的MEGA-SIM卡或者大容量的闪存装置，则该软件模块可存储在该MEGA-SIM卡或者大容量的闪存装置中。
针对附图中描述的功能方框中的一个或多个和/或功能方框的一个或多个组合， 可以实现为用于执行本发明所描述功能的通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件或者其任意适当组合。针对附图描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，还可以实现为计算设备的组合，例如，DSP和微处理器的组合、多个微处理器、与DSP通信结合的一个或多个微处理器或者任何其它装置。
以上结合具体的实施方式对本发明进行了描述，但本领域技术人员应该清楚，这些描述都是示例性的，并不是对本发明保护范围的限制。本领域技术人员可以根据本发明的精神和原理对本发明做出各种变型和修改，这些变型和修改也在本发明的范围内。

Claims (20)

  1. 一种系统信息请求的发送装置，配置于终端设备，其中，所述装置包括：
    确定单元，其根据服务小区是否配置了SUL确定使用基于消息1的系统信息(SI)请求过程或者基于消息3的SI请求过程通过SUL或NUL向网络设备请求按需系统信息。
  2. 根据权利要求1所述的装置，其中，所述确定单元包括：
    第一选择单元，如果所述服务小区配置了所述SUL并且满足选择SUL的标准，所述第一选择单元使用所述SUL上基于消息1的SI请求过程；
    否则，如果所述服务小区配置了NUL并且满足选择NUL的标准，所述第一选择单元使用所述NUL上基于消息1的SI请求过程；
    否则，所述第一选择单元使用基于消息3的SI请求过程。
  3. 根据权利要求2所述的装置，其中，在满足下面一个条件或多个条件的情况下，认为所述服务小区配置了所述SUL：
    SIB1包括包含si-RequestConfigSUL的si-SchedulingInfo；
    所述终端设备支持SUL的frequencyBandList域里指示的一个或多个频带；
    所述终端设备支持SUL的locationAndBandwidth域里指示的初始上行BWP的带宽；
    所述终端设备支持支持的SUL频带的NR-NS-PmaxList里的一个或多个additionalSpectrumEmission；或者，所述终端设备支持支持的SUL频带里的additionalSpectrumEmission为0。
  4. 根据权利要求2所述的装置，其中，在满足下面一个条件或多个条件的情况下，认为所述服务小区配置了所述NUL：
    SIB1包括包含si-RequestConfig的si-SchedulingInfo；
    所述终端设备支持NUL的frequencyBandList域里指示的一个或多个频带；
    所述终端设备支持NUL的locationAndBandwidth域里指示的初始上行BWP的带宽；
    所述终端设备支持支持的NUL频带的NR-NS-PmaxList里的一个或多个additionalSpectrumEmission；或者，所述终端设备支持支持的NUL频带的 additionalSpectrumEmission为0。
  5. 根据权利要求2所述的装置，其中，满足选择SUL的标准是指：
    如果没有显式通知随机接入过程使用的载波，且如果随机接入过程的服务小区配置了SUL或通过专用信令配置了SUL，且如果下行路损参考的RSRP低于阈值；或者
    如果没有显式通知随机接入过程使用的载波，且如果随机接入过程的服务小区配置了SUL或专用信令包括SUL上随机接入参数的配置信息，且如果下行路损参考的RSRP低于阈值；或者
    如果没有显式通知随机接入过程使用的载波，且如果随机接入过程的服务小区配置了SUL，且如果下行路损参考的RSRP低于阈值。
  6. 根据权利要求5所述的装置，其中，如果满足选择SUL的标准包括随机接入过程的服务小区配置了SUL，在满足下面一个条件或多个条件的情况下，认为所述服务小区配置了所述SUL：
    ReconfigurationWithSync域里包括包含supplementaryUplink的rach-ConfigDedicated域；
    SCellConfig域里包括包含supplementaryUplink的ServingCellConfig域；
    BWP-UplinkDedicated域里包括包含supplementaryUplink的beamFailureRecoveryConfig域；以及
    存在supplementaryUplink域。
  7. 根据权利要求1所述的装置，其中，所述服务小区是否配置了SUL是指：SIB1是否包括SUL的配置以及终端设备能否支持所述SUL的配置。
  8. 根据权利要求7所述的装置，其中，所述确定单元包括：
    第二选择单元，如果所述SIB1包括包含si-RequestConfigSUL的si-SchedulingInfo，并且所述终端设备能够支持所述SUL的配置，并且，满足选择SUL的标准，所述第二选择单元使用SUL上基于消息1的SI请求过程；
    否则，如果所述SIB1包括包含si-RequestConfig的si-SchedulingInfo，并且，所述终端设备能够支持NUL的配置，并且，满足选择NUL的标准，所述第二选择单元使用NUL上基于消息1的SI请求过程；
    否则，所述第二选择单元使用基于消息3的SI请求过程。
  9. 根据权利要求8所述的装置，其中，在满足下面一个条件或多个条件的情况下，认为所述终端设备能够支持所述SUL的配置：
    所述终端设备支持SUL的frequencyBandList域里指示的一个或多个频带；
    所述终端设备支持SUL的locationAndBandwidth域里指示的初始上行BWP的带宽；
    所述终端设备支持支持的SUL频带的NR-NS-PmaxList里的一个或多个additionalSpectrumEmission；或者，所述终端设备支持支持的SUL频带里的additionalSpectrumEmission为0。
  10. 根据权利要求8所述的装置，其中，在满足下面一个条件或多个条件的情况下，认为所述终端设备能够支持所述NUL的配置：
    所述终端设备支持NUL的frequencyBandList域里指示的一个或多个频带；
    所述终端设备支持NUL的locationAndBandwidth域里指示的初始上行BWP的带宽；
    所述终端设备支持支持的NUL频带的NR-NS-PmaxList里的一个或多个additionalSpectrumEmission；或者，所述终端设备支持支持的NUL频带的additionalSpectrumEmission为0。
  11. 根据权利要求1所述的装置，其中，所述服务小区是否配置了SUL是指：所述终端设备能否支持SUL的配置和NUL的配置。
  12. 根据权利要求11所述的装置，其中，所述确定单元包括：
    触发单元，其根据si-SchedulingInfo触发在SUL上获取SI消息的SI请求或者触发在NUL上获取SI消息的SI请求；
    第三选择单元，如果触发在SUL上获取SI消息的SI请求，并且满足选择SUL的标准，所述第三选择单元使用SUL上基于消息1的SI请求过程；
    否则，如果触发在NUL上获取SI消息的SI请求，并且满足选择NUL的标准，所述第三选择单元使用NUL上基于消息1的SI请求过程；
    否则，所述第三选择单元使用基于消息3的SI请求过程。
  13. 根据权利要求12所述的装置，其中，
    根据si-SchedulingInfo，对于包括至少一个要求的SIB且其si-BroadcastStatus置为notBroadcasting的SI消息，如果包括包含所述SI消息的si-RequestConfigSUL的 si-SchedulingInfo，并且所述终端设备能够支持所述SUL的配置，所述触发单元触发在所述SUL上获取所述SI消息的SI请求；
    否则，如果包括包含所述SI消息的si-RequestConfig的si-SchedulingInfo，并且所述终端设备能够支持所述NUL的配置，所述触发单元触发在所述NUL上获取所述SI消息的SI请求。
  14. 根据权利要求13所述的装置，其中，在满足下面一个条件或多个条件的情况下，认为所述终端设备能够支持所述SUL的配置：
    所述终端设备支持SUL的frequencyBandList域里指示的一个或多个频带；
    所述终端设备支持SUL的locationAndBandwidth域里指示的初始上行BWP的带宽；
    所述终端设备支持支持的SUL频带的NR-NS-PmaxList里的一个或多个additionalSpectrumEmission；或者，所述终端设备支持支持的SUL频带里的additionalSpectrumEmission为0。
  15. 根据权利要求13所述的装置，其中，在满足下面一个条件或多个条件的情况下，认为所述终端设备能够支持所述NUL的配置：
    所述终端设备支持NUL的frequencyBandList域里指示的一个或多个频带；
    所述终端设备支持NUL的locationAndBandwidth域里指示的初始上行BWP的带宽；
    所述终端设备支持支持的NUL频带的NR-NS-PmaxList里的一个或多个additionalSpectrumEmission；或者，所述终端设备支持支持的NUL频带的additionalSpectrumEmission为0。
  16. 一种系统信息请求的配置装置，配置于网络设备，其中，所述装置包括：
    配置单元，其为终端设备配置SUL和/或NUL；
    接收单元，其接收所述终端设备发送的基于消息1的SI请求或者基于消息3的SI请求；
    发送单元，其根据所述SI请求发送按需系统信息。
  17. 根据权利要求16所述的装置，其中，所述配置单元向所述终端设备发送SIB1，所述SIB1包括包含si-RequestConfigSUL的si-SchedulingInfo，或者所述SIB1包括包含si-RequestConfig的si-SchedulingInfo。
  18. 根据权利要求16所述的装置，其中，所述按需系统信息为包括至少一个要求的SIB且其si-BroadcastStatus置为notBroadcasting的SI消息。
  19. 一种载波选择装置，配置于终端设备，其中，所述装置包括：
    选择单元，其在服务小区配置了SUL并且满足选择SUL的标准的情况下，选择SUL载波执行随机接入过程，其中，满足选择SUL的标准为：
    如果没有显式通知随机接入过程使用的载波，且如果随机接入过程的服务小区配置了SUL或通过专用信令配置了SUL，且如果下行路损参考的RSRP低于阈值，则认为满足选择SUL的标准；或者
    如果没有显式通知随机接入过程使用的载波，且如果随机接入过程的服务小区配置了SUL或专用信令包括SUL上随机接入参数的配置信息，且如果下行路损参考的RSRP低于阈值，则认为满足选择SUL的标准；或者
    如果没有显式通知随机接入过程使用的载波，且如果随机接入过程的服务小区配置了SUL，且如果下行路损参考的RSRP低于阈值。
  20. 根据权利要求19所述的装置，其中，在满足下面一个条件或多个条件的情况下，认为服务小区配置了SUL：
    ReconfigurationWithSync域里包括包含supplementaryUplink的rach-ConfigDedicated域；
    SCellConfig域里包括包含supplementaryUplink的ServingCellConfig域；
    BWP-UplinkDedicated域里包括包含supplementaryUplink的beamFailureRecoveryConfig域；以及
    存在supplementaryUplink域。
PCT/CN2019/080156 2019-03-28 2019-03-28 系统信息请求的发送方法、装置和系统 WO2020191726A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP19922168.0A EP3952508A4 (en) 2019-03-28 2019-03-28 METHOD, DEVICE AND SYSTEM FOR SENDING SYSTEM INFORMATION REQUEST
PCT/CN2019/080156 WO2020191726A1 (zh) 2019-03-28 2019-03-28 系统信息请求的发送方法、装置和系统
JP2021556930A JP7449959B2 (ja) 2019-03-28 2019-03-28 システム情報要求の送信方法、装置及びシステム
CN201980093727.XA CN113557775A (zh) 2019-03-28 2019-03-28 系统信息请求的发送方法、装置和系统
US17/476,567 US20220007425A1 (en) 2019-03-28 2021-09-16 Method and apparatus for transmitting a system information request and system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/080156 WO2020191726A1 (zh) 2019-03-28 2019-03-28 系统信息请求的发送方法、装置和系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US17/476,567 Continuation US20220007425A1 (en) 2019-03-28 2021-09-16 Method and apparatus for transmitting a system information request and system

Publications (1)

Publication Number Publication Date
WO2020191726A1 true WO2020191726A1 (zh) 2020-10-01

Family

ID=72610887

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/080156 WO2020191726A1 (zh) 2019-03-28 2019-03-28 系统信息请求的发送方法、装置和系统

Country Status (5)

Country Link
US (1) US20220007425A1 (zh)
EP (1) EP3952508A4 (zh)
JP (1) JP7449959B2 (zh)
CN (1) CN113557775A (zh)
WO (1) WO2020191726A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117643154A (zh) * 2021-11-03 2024-03-01 Oppo广东移动通信有限公司 基于增强上行覆盖的传输方法、门限的配置方法以及装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170223732A1 (en) * 2008-09-19 2017-08-03 Texas Instruments Incorporated Preamble group selection in random access of wireless networks
CN107708205A (zh) * 2017-10-31 2018-02-16 武汉虹信通信技术有限责任公司 一种ran寻呼消息处理方法及基站
CN108521890A (zh) * 2018-04-17 2018-09-11 北京小米移动软件有限公司 随机接入方法及装置
CN109152036A (zh) * 2017-06-16 2019-01-04 华为技术有限公司 上行资源的授权方法、装置及系统

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108029136B (zh) * 2015-12-29 2021-01-15 华为技术有限公司 用于随机接入的方法和装置
CN108810827B (zh) * 2017-05-05 2021-02-26 华为技术有限公司 获取系统信息的方法和装置
CN107980234B (zh) * 2017-07-14 2021-04-02 达闼机器人有限公司 用于终端能力上报的方法和装置
KR102305906B1 (ko) * 2017-08-10 2021-09-28 삼성전자 주식회사 무선 통신 시스템에서 상향링크 전송 방법 및 장치
WO2019031906A1 (en) * 2017-08-11 2019-02-14 Samsung Electronics Co., Ltd. METHOD AND APPARATUS FOR SUPPORTING ADDITIONAL UPLINK FREQUENCIES IN NEXT GENERATION MOBILE COMMUNICATION SYSTEM
WO2019080008A1 (zh) * 2017-10-25 2019-05-02 北京小米移动软件有限公司 增补上行载波配置方法及装置和调度资源分配方法及装置
SG11202004480PA (en) * 2017-11-14 2020-06-29 Idac Holdings Inc Supplementary uplink in wireless systems
CN113170380A (zh) * 2018-11-27 2021-07-23 三星电子株式会社 在支持多个上行链路载波的小区中的系统信息请求的系统和方法
KR20210119568A (ko) * 2019-02-22 2021-10-05 삼성전자주식회사 무선 통신 시스템에서 랜덤 액세스를 처리하기 위한 방법 및 사용자 단말

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170223732A1 (en) * 2008-09-19 2017-08-03 Texas Instruments Incorporated Preamble group selection in random access of wireless networks
CN109152036A (zh) * 2017-06-16 2019-01-04 华为技术有限公司 上行资源的授权方法、装置及系统
CN107708205A (zh) * 2017-10-31 2018-02-16 武汉虹信通信技术有限责任公司 一种ran寻呼消息处理方法及基站
CN108521890A (zh) * 2018-04-17 2018-09-11 北京小米移动软件有限公司 随机接入方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3952508A4 *

Also Published As

Publication number Publication date
CN113557775A (zh) 2021-10-26
US20220007425A1 (en) 2022-01-06
EP3952508A1 (en) 2022-02-09
JP2022528515A (ja) 2022-06-14
JP7449959B2 (ja) 2024-03-14
EP3952508A4 (en) 2022-04-06

Similar Documents

Publication Publication Date Title
US8958404B2 (en) Apparatus and method for providing access to a local area network
WO2019213921A1 (zh) 波束指示方法、装置和系统
US20210297913A1 (en) Method and apparatus for parameter configuration, network device, and terminal
US20160234713A1 (en) Information Transmission Method, Apparatus, and System
WO2019153302A1 (zh) 小区配置装置及方法
WO2020051890A1 (zh) 评估无线链路质量的方法、参数配置方法、装置和系统
WO2021097698A1 (zh) 一种上行接入方法、电子设备及存储介质
WO2019232798A1 (zh) 功率的确定方法及装置
WO2020191740A1 (zh) 信号接收或发送方法、装置和系统
WO2019157665A1 (zh) 业务接收或发送方法以及装置、通信系统
EP3886528A1 (en) Cell state management method and apparatus, terminal device, and network device
WO2019136629A1 (zh) 系统信息发送、获取方法以及装置、通信系统
US20230093234A1 (en) Uplink measurement management method, apparatus, and system
JP2022502929A (ja) データ伝送制御方法、ネットワーク機器および記憶媒体
WO2018126448A1 (zh) 基于动态时分双工的传输装置、方法以及通信系统
WO2020029281A1 (zh) 竞争窗口调整方法、装置以及通信系统
JP7338725B2 (ja) システム情報の指示方法、装置及び通信システム
WO2018201473A1 (zh) 激活命令的确认装置、数据传输模式的上报装置及方法
WO2020220342A1 (zh) 参考信号的发送方法、装置和通信系统
WO2020191751A1 (zh) 波束失败恢复方法、装置和通信系统
WO2020143006A1 (zh) 配置和确定寻呼机会的方法、装置和系统
WO2020191726A1 (zh) 系统信息请求的发送方法、装置和系统
WO2021092940A1 (zh) 一种小区切换方法、电子设备及存储介质
WO2020248143A1 (zh) 监听控制信道的方法、终端设备和网络设备
US10681702B2 (en) Communication method and device

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: 19922168

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021556930

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019922168

Country of ref document: EP

Effective date: 20211028