WO2022027525A1 - 系统信息的配置方法、获取方法及装置 - Google Patents

系统信息的配置方法、获取方法及装置 Download PDF

Info

Publication number
WO2022027525A1
WO2022027525A1 PCT/CN2020/107581 CN2020107581W WO2022027525A1 WO 2022027525 A1 WO2022027525 A1 WO 2022027525A1 CN 2020107581 W CN2020107581 W CN 2020107581W WO 2022027525 A1 WO2022027525 A1 WO 2022027525A1
Authority
WO
WIPO (PCT)
Prior art keywords
sib
information
scheduling information
system information
area
Prior art date
Application number
PCT/CN2020/107581
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 PCT/CN2020/107581 priority Critical patent/WO2022027525A1/zh
Priority to CN202080104343.6A priority patent/CN116097739A/zh
Publication of WO2022027525A1 publication Critical patent/WO2022027525A1/zh
Priority to US18/104,346 priority patent/US20230180227A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • 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
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks
    • H04W84/042—Public Land Mobile systems, e.g. cellular systems

Definitions

  • This application relates to the field of communications.
  • NR New Radio
  • AS access stratum
  • NAS non-access stratum
  • FIG. 1 is a schematic diagram of a system information acquisition process in NR.
  • the process includes: the terminal device obtains a master information block (MIB, MasterInformationBlock); the terminal device can also obtain a system information block 1 (SIB1, SystemInformationBlockType1); in addition, if necessary, the terminal device can also send the The network device sends a system information request (SystemInformationRequest) to request the network device to broadcast a system information message (SystemInformation messages), and obtain the system information message.
  • MIB MasterInformationBlock
  • SIB1, SystemInformationBlockType1 system information block 1
  • SystemInformationRequest system information request
  • SystemInformation messages SystemInformation messages
  • the stored system information block is introduced.
  • the terminal device can store the acquired SIB.
  • SIB1, SIB6 (SystemInformationBlockType6), SIB7 (SystemInformationBlockType7) or SIB8 (SystemInformationBlockType8) for other required SIBs, such as after cell reselection or when returning from out of coverage or after receiving a system information (SI) modification instruction , the end device can use a valid version of the stored system information.
  • SIB1 SystemInformationBlockType6
  • SIB7 SystemInformationBlockType7
  • SIB8 SystemInformationBlockType8
  • the terminal device When cell selection (e.g. power-on), cell reselection, returning from no coverage, after synchronization reconfiguration is complete, after entering the network from another RAT, receiving an indication of a system information change, receiving a PWS notification, or from
  • the terminal device will apply the system information acquisition process, first acquire MIB and SIB1 and store the acquired MIB and SIB1. For the required SIB, the terminal device can check whether a valid version of the SIB is stored, and if a valid version of the SIB is stored, the stored version can be used; once the terminal does not store a valid version of the SIB, the terminal device obtains the SIB.
  • the terminal device can store the acquired SIB and store the associated information of the SIB, including area scope (areaScope), public land mobile network identity (PLMN-Identity), system information area identity (systemInformationAreaID) and cell identity (cellIdentity).
  • areaScope area scope
  • PLMN-Identity public land mobile network identity
  • systemInformationAreaID system Information area identity
  • cellIdentity cell identity
  • the end device can check whether a valid version is stored.
  • NPN non-public networks, non-public networks
  • PLMN-Identity public land mobile network identifier
  • the terminal device When the system information area identifier in the system scheduling information, the value tag (valueTag) associated with the SIB, and the NPN identifier (NPN-Identity) in other information are associated with the system information stored in the version When the area identifier, value label and NPN identifier are the same, the terminal device considers the stored version to be valid, otherwise it is considered invalid;
  • the terminal device If the stored version of the SIB is not associated with an "areaScope", then, if the terminal device does not have NPN capability or the serving cell is not an NPN-only cell, when the value tag, other information associated with the SIB in the system scheduling information
  • the terminal device considers the stored version valid, otherwise it is considered invalid, if the terminal device has NPN capability
  • the serving cell is only an NPN cell, when the value tag associated with the SIB in the system scheduling information, the NPN identifier in other information, and the cell identifier are the same as the value tag, NPN identifier, and cell identifier associated with the stored version, the terminal equipment
  • the stored version is considered valid, otherwise invalid.
  • the system information area identifier is optional information, that is, in some scenarios, the network side may not provide this information.
  • the behavior of the end device is undefined for a SIB associated with "areaScope", for example, the end device may not be able to determine whether the stored version of the SIB is valid, or the end device may think that all the SIB's Stored versions are all invalid or multiple stored versions are considered valid. This will result in test errors of the terminal equipment and increase the test cost; it may also increase the power consumption of the terminal equipment.
  • embodiments of the present application provide a configuration method, an acquisition method, and an apparatus for system information.
  • the network device generates scheduling information based on the association between the system information area identifier and the area scope, which can avoid the situation where the area scope is configured but the system information area identifier is not configured.
  • the behavior of the terminal device with or without the configuration of the system information area identifier Therefore, the uncertainty of the behavior of the terminal equipment can be avoided, and the complexity of testing and the overhead of the terminal equipment can be reduced.
  • an apparatus for configuring system information the apparatus is applied to a network device, and the apparatus includes: a generating unit, which is based on a system information area identifier (systemInformationAreaID) and an area scope (areaScope). ) to generate scheduling information (SchedulingInfo); and a sending unit that sends the scheduling information.
  • systemInformationAreaID system information area identifier
  • areaScope area scope
  • scheduling information SchedulingInfo
  • an apparatus for acquiring system information is provided, the apparatus is applied to a terminal device, and the apparatus includes: a first acquiring unit, which acquires scheduling information, where the scheduling information is based on the system It is generated by the association between the information area ID (systemInformationAreaID) and the area scope (areaScope).
  • a first acquiring unit which acquires scheduling information, where the scheduling information is based on the system It is generated by the association between the information area ID (systemInformationAreaID) and the area scope (areaScope).
  • an apparatus for acquiring system information is provided, the apparatus is applied to a terminal device, and the apparatus includes: a fourth determining unit, which, for a stored version of a SIB, when the obtained The scheduling information includes an area scope (areaScope) corresponding to the SIB, and when the scheduling information includes a system information area identification (systemInformationAreaID) and the system information area identification and the first information are associated with the stored version of the system information When the area identifier and the corresponding information are the same, the stored version is considered valid.
  • areaScope area scope
  • systemInformationAreaID system information area identification
  • a network device includes the apparatus according to the first aspect of the embodiments of the present application.
  • a terminal device is provided, and the network device includes the apparatus according to the second aspect or the third aspect of the embodiments of the present application.
  • a communication system including the network device according to the fourth aspect of the embodiments of the present application and/or the fifth aspect of the embodiments of the present application Terminal Equipment.
  • a method for configuring system information is provided, the method is applied to a network device, and the method includes: an association based on a system information area identifier (systemInformationAreaID) and an area scope (areaScope) generating scheduling information (SchedulingInfo); and transmitting the scheduling information.
  • systemInformationAreaID system information area identifier
  • areaScope area scope
  • scheduling information SchedulingInfo
  • a method for acquiring system information the method is applied to a terminal device, and the method includes: acquiring scheduling information, the scheduling information is based on a system information area identifier (systemInformationAreaID) Generated by the association with the area scope (areaScope).
  • systemInformationAreaID system Information area identifier
  • a method for obtaining system information the method is applied to a terminal device, and the method includes: for a stored version of a SIB, when the obtained scheduling information includes information corresponding to the The area scope (areaScope) of the SIB, and when the scheduling information includes a system information area identifier (systemInformationAreaID) and the system information area identifier and the first information are related to the system information area identifier and corresponding information associated with the stored version At the same time, the terminal device considers the stored version to be valid.
  • SIB The area scope
  • systemInformationAreaID system information area identifier
  • a computer-readable program wherein when the program is executed in a system information configuration apparatus or a network device, the program makes the system information
  • the configuration apparatus or network device executes the system information configuration method described in the seventh aspect of the embodiments of the present application.
  • a storage medium storing a computer-readable program wherein the computer-readable program enables a system information configuration apparatus or a network device to execute the seventh aspect of the embodiments of the present application The configuration method of the system information.
  • a computer-readable program wherein when the program is executed in an apparatus for acquiring system information or a terminal device, the program causes the apparatus for acquiring system information or a terminal device to execute the program.
  • the terminal device executes the method for acquiring system information described in the eighth aspect or the ninth aspect of the embodiment of the present application.
  • a storage medium storing a computer-readable program, wherein the computer-readable program enables an apparatus for acquiring system information or a terminal device to execute the eighth aspect of the embodiments of the present application or The method for acquiring system information according to the ninth aspect.
  • the network device generates scheduling information based on the association between the system information area identifier and the area scope, which can avoid the situation where the area scope is configured but the system information area identifier is not configured, or the terminal device is checking
  • the validity of a stored version of an SIB specifies the behavior of the terminal device with or without the configuration of the system information area identifier. Therefore, the uncertainty of the behavior of the terminal equipment can be avoided, and the complexity of testing and the overhead of the terminal equipment can be reduced.
  • the terminal device can send a system information request message to the network device to request the network to broadcast the system information message.
  • the network device can provide the following configurations:
  • SIB1 includes si-RequestConfigSUL and si-RequestConfig;
  • si-RequestConfigSUL and si-RequestConfig are not included in SIB1.
  • the network device can provide the following configuration:
  • SIB1 includes posSI-RequestConfigSUL-r16 and posSI-RequestConfigSUL-r16;
  • posSI-RequestConfigSUL-r16 and posSI-RequestConfigSUL-r16 are not included in SIB1.
  • si-RequestConfig, posSI-RequestConfigSUL-r16 are the configurations used for requesting system information messages on the conventional uplink (Normal UL, NUL), and si-RequestConfigSUL, posSI-RequestConfigSUL-r16 are used on the supplementary uplink (Supplementary Uplink, SUL) Configuration for requesting system information messages.
  • the inventor also found that according to the current mechanism, if the serving cell is configured with supplementary uplink and if the system information broadcast status of any system information message (SI-message) in the scheduling information (SchedulingInfo) (for example, si-BroadcastStatus, posSI-BroadcastStatus)
  • SchedulingInfo for example, si-BroadcastStatus, posSI-BroadcastStatus
  • the configuration for example, si-RequestConfigSUL, posSI-RequestConfigSUL-r16
  • si-RequestConfigSUL is vacant. Therefore, in order to determine whether to provide si-RequestConfigSUL or posSI-RequestConfigSUL-r16, the network device needs to know whether the serving cell is configured with supplementary uplink.
  • the terminal device when the network device provides the SUL configuration; and considering the capabilities of the terminal device (for example, including supported frequency bands, supported uplink channel bandwidth, etc.), when the terminal device can support the SUL frequency band indicated in the SUL configuration, the terminal device considers that the service The cell is configured with supplementary uplink. While the network device is able to know whether it provides the SUL configuration, the network may not be able to determine the above terminal device capabilities because the terminal devices camped in the cell may not have indicated their terminal device capabilities to the network device; or, even if all terminal devices are Provides terminal equipment capabilities. For a SUL configuration, some terminal equipments in the serving cell may support the configuration, but some terminal equipments cannot. Therefore, the network device cannot determine whether the serving cell is configured with supplementary uplink, and therefore cannot determine whether the SIB1 includes si-RequestConfigSUL or posSI-RequestConfigSUL-r16.
  • the SIB1 includes si-RequestConfigSUL or posSI-RequestConfigSUL-r16.
  • embodiments of the present application further provide a method and apparatus for configuring system information.
  • the existence condition includes that the serving cell is configured with supplementary uplink
  • the capability of the terminal equipment is considered, or, for terminal equipment-specific parameters and cell-specific parameters, when the existence condition includes that the serving cell is configured with supplementary uplink , regardless of the capability of the terminal device or only considering that the network device provides the SUL configuration for the terminal device.
  • the network device can specify the content in the SIB1, avoid the uncertainty of the realization of the network device, reduce the test cost of the network device product, and thus save the network deployment cost.
  • an apparatus for configuring system information the apparatus is applied to network equipment, and the apparatus includes: a configuration unit, which, for terminal equipment-specific parameters, when the existence condition includes a service When the cell is configured with supplementary uplink, the capability of the terminal device is considered, or, for terminal device-specific parameters and cell-specific parameters, when the existence conditions include that the serving cell is configured with supplementary uplink, the capability of the terminal device or only the network device is not considered.
  • SUL configuration is provided for terminal equipment.
  • a network device includes the apparatus according to the fourteenth aspect of the embodiments of the present application.
  • a communication system includes the network device according to the fourteenth aspect of the embodiments of the present application.
  • a method for configuring system information is provided, the method is applied to a network device, and the method includes:
  • the network device For terminal device-specific parameters, when the existence condition includes that the serving cell is configured with supplementary uplink, the network device considers the capabilities of the terminal device, or, for terminal device-specific parameters and cell-specific parameters, when the existence condition includes the serving cell configuration When supplementing the uplink, the network device does not consider the capability of the terminal device or the network device only considers that the network device provides the SUL configuration for the terminal device.
  • a computer-readable program wherein when the program is executed in a system information configuration apparatus or a network device, the program makes the system information
  • the configuration apparatus or network device of the embodiment of the present application executes the system information configuration method described in the seventeenth aspect.
  • a storage medium storing a computer-readable program wherein the computer-readable program causes a system information configuration apparatus or a network device to execute the seventeenth embodiment of the present application The configuration method of the system information described in the aspect.
  • One of the beneficial effects of the embodiments of the present application is that: for terminal equipment-specific parameters, when the existence condition includes that the serving cell is configured with supplementary uplink, the capability of the terminal equipment is considered, or, for terminal equipment-specific parameters and cell-specific parameters , when the existence condition includes that the serving cell is configured with supplementary uplink, the capability of the terminal device is not considered or only the SUL configuration provided by the network device for the terminal device is considered.
  • the network device can specify the content in the SIB1, avoid the uncertainty of the realization of the network device, reduce the test cost of the network device product, and thus save the network deployment cost.
  • Fig. 1 is a schematic diagram of the system information acquisition process in NR;
  • FIG. 2 is a schematic diagram of a communication system according to an embodiment of the present application.
  • FIG. 3 is a schematic diagram of a method for configuring system information according to Embodiment 1 of the present application.
  • FIG. 4 is a schematic diagram of a method for generating scheduling information according to Embodiment 1 of the present application.
  • FIG. 5 is another schematic diagram of the method for generating scheduling information according to Embodiment 1 of the present application.
  • FIG. 6 is another schematic diagram of the method for generating scheduling information according to Embodiment 1 of the present application.
  • FIG. 7 is a schematic diagram of a method for acquiring system information according to Embodiment 2 of the present application.
  • FIG. 8 is a schematic diagram of a method for acquiring system information according to Embodiment 3 of the present application.
  • FIG. 9 is a schematic diagram of a method for acquiring system information according to Embodiment 4 of the present application.
  • FIG. 10 is another schematic diagram of a method for acquiring system information according to Embodiment 4 of the present application.
  • FIG. 11 is another schematic diagram of a method for acquiring system information according to Embodiment 4 of the present application.
  • FIG. 12 is a schematic diagram of a method for configuring system information according to Embodiment 5 of the present application.
  • FIG. 13 is a schematic diagram of an apparatus for configuring system information according to Embodiment 6 of the present application.
  • FIG. 14 is a schematic diagram of an apparatus for acquiring system information according to Embodiment 7 of the present application.
  • FIG. 16 is a schematic diagram of an apparatus for acquiring system information according to Embodiment 8 of the present application.
  • FIG. 17 is a schematic diagram of an apparatus for acquiring system information according to Embodiment 9 of the present application.
  • FIG. 18 is a schematic block diagram of a system configuration of a network device according to Embodiment 10 of the present application.
  • FIG. 19 is a schematic block diagram of a system configuration of a terminal device according to Embodiment 11 of the present application.
  • FIG. 20 is a schematic block diagram of a system configuration of a terminal device according to Embodiment 12 of the present application.
  • FIG. 21 is a schematic block diagram of a system configuration of a network device according to Embodiment 13 of the present application.
  • the terms “first”, “second”, etc. are used to distinguish different elements in terms of numelation, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be referred to by these terms restricted.
  • the term “and/or” includes any and all combinations of one or more of the associated listed items.
  • the terms “comprising”, “including”, “having”, etc. refer to the presence of stated features, elements, elements or components, but do not preclude the presence or addition of one or more other features, elements, elements or components.
  • the term "communication network” or “wireless communication network” may refer to a network that conforms to any of the following communication standards, such as Long Term Evolution (LTE, Long Term Evolution), Long Term Evolution Enhanced (LTE-A, LTE- Advanced), Wideband Code Division Multiple Access (WCDMA, Wideband Code Division Multiple Access), High-Speed Packet Access (HSPA, High-Speed Packet Access) and so on.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution Enhanced
  • 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 communication protocols at any stage, for example, including 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 communication protocols currently known or to be developed in the future.
  • Network device refers to, for example, a device in a communication system that connects a user equipment to a communication network and provides services for the user equipment.
  • Network devices may include but are not limited to the following devices: base station (BS, Base Station), access point (AP, Access Point), transmission and reception point (TRP, Transmission Reception Point), broadcast transmitter, mobility management entity (MME, Mobile Management Entity), gateway, server, radio network controller (RNC, Radio Network Controller), base station controller (BSC, Base Station Controller) and so on.
  • the base station may include but is not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB), and 5G base station (gNB), etc., and may also include a remote radio head (RRH, Remote Radio Head) , Remote Radio Unit (RRU, Remote Radio Unit), relay (relay) or low power node (eg femto, pico, etc.).
  • RRH Remote Radio Head
  • RRU Remote Radio Unit
  • relay relay
  • low power node eg femto, pico, etc.
  • base station may include some or all of their functions, each base station may provide communication coverage for a particular 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 a device that accesses a communication network through a network device and receives network services, and may also be called “Terminal Equipment” (TE, Terminal Equipment).
  • a terminal device may be fixed or mobile, and may also be referred to as a mobile station (MS, Mobile Station), a terminal, a subscriber station (SS, Subscriber Station), an access terminal (AT, Access Terminal), a station, and the like.
  • the terminal device may include but is not limited to the following devices: Cellular Phone (Cellular Phone), Personal Digital Assistant (PDA, Personal Digital Assistant), wireless modem, wireless communication device, handheld device, machine type communication device, laptop computer, Cordless phones, smartphones, smart watches, digital cameras, and more.
  • Cellular Phone Cellular Phone
  • PDA Personal Digital Assistant
  • wireless modem wireless communication device
  • handheld device machine type communication device
  • laptop computer Cordless phones, smartphones, smart watches, digital cameras, and more.
  • the terminal device may also be a machine or device that performs monitoring or measurement, such as but not limited to: Machine Type Communication (MTC, Machine Type Communication) terminals, In-vehicle 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 application, which schematically illustrates a situation in which a terminal device and a network device are used as examples. As shown in FIG. For simplicity, FIG. 1 only takes one terminal device as an example for description.
  • the network device 101 is, for example, an NR network device gNB.
  • an existing service or a service that can be implemented in the future may be performed between the network device 101 and the terminal device 102 .
  • these services include but are not limited to: Enhanced Mobile Broadband (eMBB, enhanced Mobile Broadband), Massive Machine Type Communication (mMTC, massive Machine Type Communication) and High Reliable Low Latency Communication (URLLC, Ultra-Reliable and Low-Latency Communication) Latency Communication), etc.
  • the terminal device 102 in order to verify whether there is a valid stored version of the system information block, the terminal device 102, for a stored version of a SIB, if the stored version of the SIB is associated with an "areaScope" and its value is associated with the service
  • the "areaScope" value of the SIB received in the system scheduling information (si-SchedulingInfo) of the cell is the same, then the terminal device 102 checks the system information area identifier in the system scheduling information and other information associated with the stored version of the SIB.
  • the terminal device 102 checks the cell identifier and other information with the SIB's "areaScope” value. Whether the corresponding information associated with the storage version is consistent.
  • the system information area identifier is optional information, that is, in some scenarios, the network device 101 may not provide this information. For example, after the terminal device 102 performs cell reselection, it finds that the system scheduling information does not include the system information area identifier; or, when the terminal device 102 returns from outside the coverage area, it finds that the system scheduling information does not include the system information area identifier; or, the network After sending the SI modification instruction, the device 101 updates the system scheduling information, where the system scheduling information does not include the system information area identifier.
  • the terminal device 102 cannot judge whether the stored version of the SIB is valid, which leads to the uncertainty of the behavior of the terminal device 102 and causes the test error of the terminal device 102; or,
  • the terminal device 102 may think that all stored versions of the SIB are invalid, so the terminal device 102 needs to re-acquire the SIB; and re-acquiring the SIB when the SIB remains unchanged will cause unnecessary consumption of the terminal device. electricity, which is not desirable for end devices that require energy savings; or,
  • the terminal device 102 may consider the associated stored version to be valid, which may result in multiple stored versions being valid, so that the terminal device 102 cannot determine which version to use or use one Invalid storage version.
  • the terminal device 102 has a storage version 1, which is associated with "areaScope”, and the corresponding storage information also includes the public land mobile network identity 1, system Information area identification 1 and cell identification 1; the terminal device 102 also has a storage version 2, which is associated with "areaScope", and the corresponding storage information also includes public land mobile network identification 1, system information area identification 2 and cell identification 2.
  • the terminal device 102 may think that there is an error because it cannot compare the system information area identifier; Or, the terminal device 102 thinks that both the storage version 1 and the storage version 2 are not valid, so it needs to re-acquire the SIBx; or, the terminal device 102 thinks that the storage version 1 and the storage version 2 are both valid, so it cannot determine which version to use, Or store version 1 (or store version 2) was selected, but that version is not actually valid.
  • the embodiment of the present application provides a method for configuring system information, and the method is applied to a network device.
  • the method is applied to the network device 101 in FIG. 2 .
  • FIG. 3 is a schematic diagram of a method for configuring system information according to Embodiment 1 of the present application. As shown in Figure 3, the method includes:
  • Step 301 Generate scheduling information (SchedulingInfo) based on the association between the system information area identifier (systemInformationAreaID) and the area scope (areaScope); and
  • Step 302 Send the scheduling information.
  • the network device generates the scheduling information based on the correlation between the system information area identifier and the area scope, which can avoid the situation where the area scope is configured but the system information area identifier is not configured. Therefore, the uncertainty of the behavior of the terminal device can be avoided, and the test can be reduced. complexity and end-device overhead.
  • the network device In step 301, the network device generates scheduling information based on the association between the system information area identifier and the area range.
  • the scheduling information may also be referred to as system scheduling information (si-SchedulingInfo).
  • the scheduling information is included in SIB1.
  • the system information area identifier is applicable to all cell-specific SIBs, that is, each SIB configured with an area range is associated with the same system information area identifier .
  • the scheduling information when the scheduling information includes an area range, the area range corresponds to one SIB, that is, the scheduling information may include one or more area ranges corresponding to one SIB.
  • the scheduling information When the scheduling information includes an area range corresponding to one SIB, it indicates that the SIB supports area specificity, that is, the SIB is valid in multiple cells in the area. When the scheduling information does not include the area corresponding to one SIB When the range is set, it means that the SIB does not support region specificity, that is, the SIB is only valid in the cell that provides the SIB.
  • the scheduling information is generated based on the association between the system information area identifier and the area scope.
  • the scheduling information may include both the system information area identifier and the area scope, or the scheduling information may not include the system information at the same time.
  • Information area identifier and area range, or, the scheduling information may include the system information area identifier, but does not include the area range.
  • FIG. 4 is a schematic diagram of a method for generating scheduling information according to Embodiment 1 of the present application. As shown in Figure 4, the method includes:
  • Step 401 When the scheduling information includes the system information area identifier, the network device configures the area range for one or more SIBs in the scheduling information or optionally configures the area for one or more SIBs in the scheduling information. area; and
  • Step 402 When the scheduling information does not include the system information area identifier, the network device does not configure the area range in the scheduling information.
  • the network device configures the area range for one or more SIBs in the scheduling information, or optionally, one or more SIBs in the scheduling information Configure the area scope, otherwise, do not configure the area scope.
  • the network device configuring the area scope for one or more SIBs in the scheduling information refers to forcibly configuring the area scope for one or more SIBs in the scheduling information.
  • the SIB may be at least one of SIB2, SIB3, SIB4, and SIB5, and in addition, the SIB may also be at least one of SIB9, SIB10, SIB11, SIB12, SIB13, and SIB14.
  • the necessary coding condition of the area scope field in the scheduling information is: when the scheduling information includes the system information area identifier, the area scope field is mandatory to exist; when the scheduling information When the system information area identifier is not included, the area scope field does not exist. That is, if the scheduling information includes the system information area identifier, then the area scope field is mandatory to exist; otherwise, the area scope field does not exist.
  • the necessary coding condition of the area scope field in the scheduling information is: when the scheduling information includes the system information area identifier, the area scope field optionally exists; when the scheduling information does not include the system information area identifier , the area scope domain does not exist. That is, if the scheduling information includes the system information area identifier, then the area scope field is optional; otherwise, the area scope field does not exist.
  • the area scope field is a conditional existence based on the system information area identification field (systemInformationAreaID field), that is, the conditional SI-Area-ID can be defined by the following Table 1 or Table 2 .
  • condition SI-Area-ID is only an exemplary name, and other names may also be used to represent, for example, the condition SIAreaID or the condition SI_AID.
  • the network will configure area scope for one or more SIBs to support area-specific SIBs.
  • the terminal device checks the validity of a stored version of an SIB, for a SIB configured with a region range, it must be able to check whether the system information region identifier in the scheduling information is consistent with the system information region identifier associated with the stored version.
  • the method allows the network device to optionally configure the area scope when the system information area identifier is configured, which ensures the flexibility of the network configuration.
  • the network will not configure the area scope and does not support area-specific SIBs. In this way, signaling overhead is saved and spectrum resources are saved.
  • FIG. 5 is another schematic diagram of the method for generating scheduling information according to Embodiment 1 of the present application. As shown in Figure 5, the method includes:
  • Step 501 When the scheduling information includes one or more area ranges configured for one SIB, the network device configures the system information area identifier in the scheduling information; and
  • Step 502 When the scheduling information does not include one or more area ranges configured for one SIB, the network device optionally configures the system information area identifier in the scheduling information.
  • the network device configures the system information area identifier in the scheduling information; otherwise, the network device configures the system information area identifier in the scheduling information
  • the optional configuration is in the scheduling information.
  • the SIB may be at least one of SIB2, SIB3, SIB4, and SIB5, and in addition, the SIB may also be at least one of SIB9, SIB10, SIB11, SIB12, SIB13, and SIB14.
  • the necessary coding condition of the system information area identifier field in the scheduling information is: when the scheduling information includes one or more area ranges configured for one SIB, the system information area identifier The domain is mandatory; and the system information domain identifies the optional existence of the domain when the scheduling information does not include one or more domain ranges configured for a SIB. That is, if the scheduling information includes one or more area ranges configured for one SIB, then the system information area identification field is mandatory to exist; otherwise, the system information area identification field is optional.
  • systemInformationAreaID field is conditional based on the area scope field (areaScope field), that is, the conditional AreaScope can be defined by the following Table 3.
  • conditional AreaScope is only an exemplary name, and other names may also be used, for example, the conditional Area-Scope or the conditional Area_Scope.
  • the network device when an area scope is configured for one or more SIBs, that is, an area-specific SIB is supported, the network device must configure a system information area identifier to determine the system information area where the serving cell is located. In this way, when the terminal device checks the validity of a stored version of an SIB, for an SIB configured with a region range, it must be able to check whether the system information region identifier in the scheduling information is consistent with the system information region identifier associated with the stored version.
  • the network in the case where the area scope is not configured, that is, the area-specific SIB is not supported, the network can optionally configure the system information area identifier, which ensures the flexibility of the network configuration.
  • FIG. 6 is another schematic diagram of the method for generating scheduling information according to Embodiment 1 of the present application. As shown in Figure 6, the method includes:
  • Step 601 When the scheduling information includes one or more area ranges configured for one SIB, the network device configures the system information area identifier in the scheduling information; and
  • Step 602 When the scheduling information does not include one or more area ranges configured for one SIB, the network device does not configure the system information area identifier in the scheduling information.
  • the network device configures the system information area identifier in the scheduling information; otherwise, the network device does not configure the system information area The identifier is configured in the scheduling information.
  • the SIB may be at least one of SIB2, SIB3, SIB4, and SIB5, and in addition, the SIB may also be at least one of SIB9, SIB10, SIB11, SIB12, SIB13, and SIB14.
  • the necessary coding condition of the system information area identifier field in the scheduling information is: when the scheduling information includes one or more area ranges configured for one SIB, the system information area identifier The domain is mandatory to exist; and when the scheduling information does not include one or more area ranges configured for a SIB, the system information area identification field does not exist. That is, if the scheduling information includes one or more area ranges configured for one SIB, then the system information area identification field is mandatory to exist; otherwise, the system information area identification field does not exist.
  • systemInformationAreaID field is based on the area scope field (areaScope field), and the conditional existence, that is, the conditional AreaScope can be defined by the following Table 4.
  • conditional AreaScope is only an exemplary name, and other names may also be used, for example, the conditional Area-Scope or the conditional Area_Scope.
  • the network device when an area scope is configured for one or more SIBs, that is, an area-specific SIB is supported, the network device must configure a system information area identifier to determine the system information area where the serving cell is located. In this way, when the terminal device checks the validity of a stored version of an SIB, for an SIB configured with a region range, it must be able to check whether the system information region identifier in the scheduling information is consistent with the system information region identifier associated with the stored version.
  • the network device in the case where the area scope is not configured, that is, the area-specific SIB is not supported, the network device will not configure the system information area identifier, which saves signaling overhead and spectrum resources.
  • the network device may send the generated scheduling information in the form of broadcasting.
  • the scheduling information is included in SIB1.
  • the network device transmits SIB1 in the form of broadcast.
  • the network device generates scheduling information based on the correlation between the system information area identifier and the area scope, which can avoid the situation where the area scope is configured but the system information area identifier is not configured, and therefore, the uncertainty of the behavior of the terminal device can be avoided. , and reduce the complexity of the test and the overhead of the terminal equipment.
  • An embodiment of the present application provides a method for acquiring system information, which is applied to a terminal device, and corresponds to the method for configuring system information applied to a network device described in Embodiment 1, and the same content will not be repeated.
  • the method is applied to the terminal device 102 in FIG. 2 .
  • FIG. 7 is a schematic diagram of a method for acquiring system information according to Embodiment 2 of the present application. As shown in Figure 7, the method includes:
  • Step 701 Obtain scheduling information, where the scheduling information is generated based on the association between the system information area identifier (systemInformationAreaID) and the area scope (areaScope).
  • systemInformationAreaID systemInformationAreaID
  • areaScope areaScope
  • the scheduling information may be included in SIB1, for example, the SIB1 is sent by a network device in the form of broadcast.
  • the method may further include:
  • Step 702 For a SIB, determine whether a valid version of the SIB is stored according to the scheduling information and other information in the system information broadcast by the serving cell.
  • the other information may be included in the SIB1.
  • the SIB may be at least one of SIB2, SIB3, SIB4, and SIB5, and in addition, the SIB may also be at least one of SIB9, SIB10, SIB11, SIB12, SIB13, and SIB14.
  • step 702 for a stored version of the SIB, when the system information area identifier in the scheduling information and the value tag (valueTag) associated with the SIB and the public land mobile network identifier (PLMN-Identity) in the other information are the same as the When the system information area identifier, value label and public land mobile network identifier associated with the stored version are the same, the terminal device considers the stored version to be valid.
  • the terminal device considers the stored version to be valid.
  • the terminal device determines whether the terminal device has NPN capability or the serving cell is not an NPN-only (NPN-only) cell. If the terminal device does not have NPN capability or the serving cell is not an NPN-only (NPN-only) cell, then when the system information area identifier in the scheduling information and the value tag (valueTag) associated with the SIB, the other information When the public land mobile network identity (PLMN-Identity) of the stored version is the same as the system information area identification, value label and public land mobile network identification associated with the stored version, the terminal device considers the stored version to be valid.
  • NPN-only NPN-only
  • the terminal device if the terminal device does not have NPN capability or the serving cell is not an NPN-only (NPN-only) cell, then when the value tag (valueTag) associated with the SIB in the scheduling information and the public land in the other information
  • the value tag valueTag
  • PLMN-Identity mobile network identity
  • the cell identity and the value tag associated with the stored version, the public land mobile network identity and the cell identity are the same, the terminal device considers the stored version valid.
  • step 702 for a stored version of the SIB, when the system information area identifier in the scheduling information, the value tag associated with the SIB, and the NPN identifier (NPN-Identity) in the other information are associated with the storage
  • NPN-Identity NPN-Identity
  • the terminal device considers the stored version to be valid.
  • the terminal device For example, if the terminal device has NPN capability and the serving cell is an NPN-only (NPN-only) cell, then when the system information area identifier in the scheduling information and the value tag associated with the SIB, the NPN identifier in the other information ( When the system information area identifier, value label and NPN identifier associated with the stored version are the same, the terminal device considers the stored version to be valid.
  • NPN-only NPN-only
  • the terminal device when the value tag associated with the SIB in the scheduling information and the NPN identifier (NPN-Identity in the other information) ), when the cell ID is the same as the value tag, NPN ID, and cell ID associated with the stored version, the terminal device considers the stored version to be valid.
  • the method may further include:
  • Step 703 When a valid version exists, the terminal device uses the valid version of the SIB.
  • Step 704 When there is no valid version, the terminal device sends a system information request to the network device or acquires the SIB according to the scheduling information.
  • the terminal device obtains the scheduling information generated by the network device based on the association between the system information area identifier and the area scope, which can avoid the situation where the area scope is configured but the system information area identifier is not configured. Therefore, the behavior of the terminal device can be avoided. uncertainty, and reduce the complexity of the test and the overhead of the end equipment.
  • An embodiment of the present application provides a method for acquiring system information, which is applied to a network device and a terminal device, and corresponds to the method for configuring system information applied to a network device described in Embodiment 1 and the method described in Embodiment 2.
  • the configuration method of the system information applied to the terminal device will not be repeated for the same content.
  • FIG. 8 is a schematic diagram of a method for acquiring system information according to Embodiment 3 of the present application. As shown in Figure 8, the method includes:
  • Step 801 The network device generates scheduling information based on the association between the system information area identifier and the area scope;
  • Step 802 the network device sends the scheduling information, and the terminal device obtains the scheduling information
  • Step 803 the terminal device determines whether a valid version of the SIB is stored according to the scheduling information and other information in the system information broadcast by the serving cell;
  • Step 804 When a valid version exists, the terminal device uses the valid version of the SIB.
  • Step 805 When there is no valid version, the terminal device sends a system information request to the network device or acquires the SIB according to the scheduling information.
  • step 805 it is optional for the terminal device to send a system information request to the network device. For example, if the network device has broadcast the scheduling information including the SIB, the terminal device does not need to After sending the system information request again, the SIB can be obtained directly according to the scheduling information.
  • each step in FIG. 8 may refer to the description of Embodiment 1 and Embodiment 2, and the description will not be repeated here.
  • the network device generates scheduling information based on the correlation between the system information area identifier and the area scope, which can avoid the situation where the area scope is configured but the system information area identifier is not configured, and therefore, the uncertainty of the behavior of the terminal device can be avoided. , and reduce the complexity of the test and the overhead of the terminal equipment.
  • An embodiment of the present application provides a method for acquiring system information, and the method is applied to a terminal device.
  • the method is applied to the terminal device 102 in FIG. 2 .
  • FIG. 9 is a schematic diagram of a method for acquiring system information according to Embodiment 4 of the present application. As shown in Figure 9, the method includes:
  • Step 901 For a stored version of a SIB, when the obtained scheduling information includes a region range corresponding to the SIB, and when the scheduling information includes a system information region identifier and the system information region identifier and the first information and the stored version When the associated system information area identifier and corresponding information are the same, the terminal device considers the stored version to be valid.
  • the SIB may be at least one of SIB2, SIB3, SIB4, and SIB5, and in addition, the SIB may also be at least one of SIB9, SIB10, SIB11, SIB12, SIB13, and SIB14.
  • the validity of each storage version is checked one by one.
  • the first information may include: the first PLMN identity (PLMN-Identity) received from the serving cell and included in the PLMN identity information list (PLMN-IdentityInfoList) and included in the scheduling information
  • PLMN identityInfoList PLMN identity information list
  • valueTag value tag
  • the corresponding information includes: the PLMN identity (PLMN-Identity) associated with the stored version of the SIB and the value tag.
  • the first information includes: the first information received from the serving cell and included in the PLMN identity information list (PLMN-IdentityInfoList) A PLMN identity (PLMN-Identity) and a value tag (valueTag) associated with the SIB included in the scheduling information; the corresponding information includes: a PLMN identity (PLMN-Identity) and a value associated with the stored version of the SIB Label.
  • PLMN-IdentityInfoList A PLMN identity (PLMN-Identity) and a value tag (valueTag) associated with the SIB included in the scheduling information
  • PLMN-Identity PLMN identity
  • valueTag value tag
  • the first information may include: the first NPN identifier received from the serving cell and included in the NPN identifier information list (NPN-IdentityInfoList) and the SIB association included in the scheduling information
  • the corresponding information includes: the NPN identifier and the value tag associated with the stored version of the SIB.
  • the first information includes: the first information received from the serving cell including the NPN identification information list (NPN-IdentityInfoList)
  • NPN-IdentityInfoList The NPN identifier and the value tag (valueTag) associated with the SIB included in the scheduling information
  • the corresponding information includes: the NPN identifier and the value tag associated with the stored version of the SIB.
  • the method may further include:
  • Step 902 For the stored version of a SIB, when the obtained scheduling information includes a region range corresponding to the SIB, and when the scheduling information does not include a system information region identifier, the terminal device considers the stored version to be invalid.
  • the terminal device considers the stored version to be valid, otherwise, the terminal device considers the stored version to be invalid.
  • the area scope is associated and the value of the area scope is the same as the value received in the system scheduling information for the SIB from the serving cell for this stored version of the SIB,
  • the system information area identity (if any) and the value of the SIB included in the system scheduling information received from the serving cell tag the PLMN associated with the stored version of the SIB.
  • the stored SIB is considered valid for the cell.
  • the value of the area scope is the same as the value received from the system scheduling information for the SIB for the serving cell, and if the system information is included in the system scheduling information area ID,
  • the system information area identity, and the value tag of the SIB included in the system scheduling information received from the serving cell are associated with the PLMN identity, system information of the stored version of the SIB The area ID and value label are the same,
  • the stored SIB is considered valid for the cell.
  • the terminal device in Rel-15 determines the validity of a stored version of an SIB by checking the system information area identifier, so as to avoid the uncertainty of the behavior of the terminal device and reduce the Test complexity and reduce equipment overhead.
  • the terminal device in the case where the system information area identifier is not configured, the terminal device considers the stored version to be invalid, which has little impact on the behavior and standards of the current terminal device, and can reduce the implementation cost.
  • the value of this area scope is the same as the value received from the serving cell's system scheduling information for this SIB,
  • the system information area identification (if present) and the system scheduling information received from the serving cell include The value label of the SIB is consistent with the NPN identifier, the system information area identifier and the value label associated with the stored version of the SIB,
  • the system information area identity (if any) and the value tag of the SIB included in the system scheduling information received from the serving cell are associated with the stored version of the SIB.
  • the PLMN identifier, system information area identifier and value label are consistent with each other,
  • the stored SIB is considered valid for the cell.
  • the value of the area scope is the same as the value received from the system scheduling information for the SIB for the serving cell, and if the system information is included in the system scheduling information area ID,
  • the terminal device has NPN capability and the cell is an NPN-only cell, and the first NPN identity included in the NPN identity list, the system information area identity, and the value of the SIB included in the system scheduling information received from the serving cell
  • the label is consistent with the NPN identifier, the system information area identifier and the value label associated with the stored version of the SIB
  • the system information area identity information list if the first PLMN identity included in the PLMN identity information list, the system information area identity, and the PLMN identity associated with the stored version of the SIB, the value label of the SIB included in the system scheduling information received from the serving cell, The system information area ID and value label are consistent,
  • the stored SIB is considered valid for the cell.
  • the terminal device in Rel-16 determines the validity of a stored version of an SIB by checking the system information area identifier, so as to avoid the uncertainty of the behavior of the terminal device and reduce the Test complexity and reduce equipment overhead.
  • This method takes into account that the terminal equipment in Rel-16 has the ability to support non-public network (NPN), so that the terminal equipment can check the NPN identity, not the PLMN identity, to determine the validity of a stored version of a SIB, thereby avoiding the need for Uncertainty of the behavior of the terminal device in the case that the network device does not broadcast the PLMN identity.
  • NPN non-public network
  • the terminal device in the case where the system information area identifier is not configured, the terminal device considers the stored version to be invalid, which has little impact on the behavior and standards of the current terminal device, and can reduce the implementation cost.
  • the method may further include:
  • Step 903 when the terminal device considers that the stored version is valid, use the SIB of the valid version.
  • Step 904 When there is no valid version, the terminal device sends a system information request to the network device or acquires the SIB according to the scheduling information.
  • FIG. 10 is another schematic diagram of a method for acquiring system information according to Embodiment 4 of the present application. As shown in Figure 10, the method includes:
  • Step 1001 For a stored version of a SIB, when the obtained scheduling information includes a region range corresponding to the SIB, and when the scheduling information includes a system information region identifier and the system information region identifier and the first information and the stored version When the associated system information area identifier and corresponding information are the same, the terminal device considers the stored version to be valid; and
  • Step 1002 For the stored version of a SIB, when the obtained scheduling information includes a region range corresponding to the SIB, and when the scheduling information does not include a system information region identifier and the first information is related to the corresponding information associated with the stored version. At the same time, the terminal device considers the stored version to be valid.
  • the terminal device considers that the stored version is valid; if the scheduling information does not include the system information area identifier and the first information is the same as the corresponding information associated with the stored version, the terminal device The stored version is also considered valid.
  • the area scope is associated and the value of the area scope is the same as the value received in the system scheduling information for the SIB from the serving cell for this stored version of the SIB,
  • the system information area identity (if any) and the value of the SIB included in the system scheduling information received from the serving cell tag the PLMN associated with the stored version of the SIB.
  • the value of the area scope is the same as the value received in the system scheduling information for the SIB from the serving cell, and, if not in the system scheduling information Including the system information area ID,
  • the area scope does not exist for the stored version of the SIB, and the value of the area scope is not included in the system scheduling information for the SIB from the serving cell,
  • the cell identity and the value tag included in the system scheduling information received from the serving cell for this SIB are associated with the PLMN identity, cell identity and value of the stored version of the SIB The labels are the same,
  • the stored SIB is considered valid for the cell.
  • the value of the area scope is the same as the value received in the system scheduling information for the SIB from the serving cell, and if the system scheduling information includes the system Information area identification,
  • the value of the area scope is the same as the value received in the system scheduling information for the SIB from the serving cell, and, if not in the system scheduling information Including the system information area ID,
  • the area scope does not exist for the stored version of the SIB, and the value of the area scope is not included in the system scheduling information for the SIB from the serving cell,
  • the cell identity and the value tag included in the system scheduling information received from the serving cell for this SIB are associated with the PLMN identity, cell identity and value of the stored version of the SIB The labels are the same,
  • the stored SIB is considered valid for the cell.
  • the value of this area scope is the same as the value received from the serving cell's system scheduling information for this SIB,
  • the system information area identification (if present) and the system scheduling information received from the serving cell include The value label of the SIB is consistent with the NPN identifier, the system information area identifier and the value label associated with the stored version of the SIB,
  • the system information area identity (if any) and the value tag of the SIB included in the system scheduling information received from the serving cell are associated with the stored version of the SIB.
  • the PLMN identifier, system information area identifier and value label are consistent with each other,
  • the value of the area scope is the same as the value received in the system scheduling information for the SIB from the serving cell, and if the system scheduling information does not include the system Information area identification,
  • the terminal device has NPN capability and the cell is an NPN-only cell, and the first NPN identifier included in the NPN identifier list and the value of the SIB included in the system scheduling information received from the serving cell are the same as the SIB's value tag
  • the NPN identifier and value label associated with the stored version are consistent
  • the terminal device has NPN capability and the cell is an NPN-only cell
  • the first NPN identity included in the NPN identity list, the cell identity, and the value of the SIB included in the system scheduling information received from the serving cell are the same as
  • the NPN identifier, cell identifier and value label associated with the stored version of the SIB are consistent
  • the stored SIB is considered valid for the cell.
  • the value of the area scope is the same as the value received from the system scheduling information for the SIB for the serving cell, and if the system information is included in the system scheduling information area ID,
  • the terminal device has NPN capability and the cell is an NPN-only cell, and the first NPN identity included in the NPN identity list, the system information area identity, and the value of the SIB included in the system scheduling information received from the serving cell
  • the label is consistent with the NPN identifier, the system information area identifier and the value label associated with the stored version of the SIB
  • the system information area identity information list if the first PLMN identity included in the PLMN identity information list, the system information area identity, and the PLMN identity associated with the stored version of the SIB, the value label of the SIB included in the system scheduling information received from the serving cell, The system information area ID and value label are consistent,
  • the value of the area scope is the same as the value received in the system scheduling information for the SIB from the serving cell, and if the system scheduling information does not include the system Information area identification,
  • the terminal device has NPN capability and the cell is an NPN-only cell, and the first NPN identifier included in the NPN identifier list and the value of the SIB included in the system scheduling information received from the serving cell are the same as the SIB's value tag
  • the NPN identifier and value label associated with the stored version are consistent
  • the terminal device has NPN capability and the cell is an NPN-only cell
  • the first NPN identity included in the NPN identity list, the cell identity, and the value of the SIB included in the system scheduling information received from the serving cell are the same as
  • the NPN identifier, cell identifier and value label associated with the stored version of the SIB are consistent
  • the stored SIB is considered valid for the cell.
  • the method may further include:
  • Step 1003 when the terminal device considers that the stored version is valid, use the SIB of the valid version.
  • Step 1004 When there is no valid version, the terminal device sends a system information request to the network device or acquires the SIB according to the scheduling information.
  • FIG. 11 is another schematic diagram of a method for acquiring system information according to Embodiment 4 of the present application. As shown in Figure 11, the method includes:
  • Step 1101 For a stored version of a SIB, when the obtained scheduling information includes a region range corresponding to the SIB, and when the scheduling information includes a system information region identifier and the system information region identifier and the first information and the stored version When the associated system information area identifier and corresponding information are the same, the terminal device considers the stored version to be valid; and
  • Step 1102 For the stored version of a SIB, when the obtained scheduling information includes the area range corresponding to the SIB, and when the scheduling information does not include the system information area identifier but the first information and the cell identifier are associated with the stored version. When the corresponding information and the cell identity are the same, the terminal device considers the stored version to be valid.
  • the terminal device For a stored version of a SIB, if the obtained scheduling information includes an area range corresponding to the SIB, and if the scheduling information includes a system information area identifier and the system information area identifier and the first information are associated with the storage If the system information area identifier associated with the version and the corresponding information are the same, then the terminal device considers the stored version to be valid; if the scheduling information does not include the system information area identifier and the first information and the cell identifier are associated with the stored version, the corresponding information and cell When the identifiers are the same, the terminal device also considers the stored version to be valid.
  • the area scope is associated and the value of the area scope is the same as the value received in the system scheduling information for the SIB from the serving cell for this stored version of the SIB,
  • the system information area identity (if any) and the value of the SIB included in the system scheduling information received from the serving cell tag the PLMN associated with the stored version of the SIB.
  • the value of the area scope is the same as the value received in the system scheduling information for the SIB from the serving cell, and, if not in the system scheduling information Include the system information area ID, or,
  • the first PLMN identity, cell identity included in the PLMN identity information list, and the value tag of the SIB included in the system scheduling information received from the serving cell are associated with the PLMN identity, cell identity, and value of the stored version of the SIB The labels are the same,
  • the stored SIB is considered valid for the cell.
  • the value of the area scope is the same as the value received in the system scheduling information for the SIB from the serving cell, and if the system scheduling information includes the system Information area identification,
  • the system information area identity, and the value tag of the SIB included in the system scheduling information received from the serving cell are associated with the PLMN identity, system information of the stored version of the SIB The area ID and value label are the same,
  • the value of the area scope is the same as the value received in the system scheduling information for the SIB from the serving cell, and, if not in the system scheduling information Include the system information area ID, or,
  • the first PLMN identity, cell identity included in the PLMN identity information list, and the value tag of the SIB included in the system scheduling information received from the serving cell are associated with the PLMN identity, cell identity, and value of the stored version of the SIB The labels are the same,
  • the stored SIB is considered valid for the cell.
  • the terminal device in Rel-15 determines the validity of a stored version of an SIB by checking the system information area identifier, so as to avoid the uncertainty of the behavior of the terminal device and reduce the Test complexity and reduce equipment overhead.
  • the terminal device when the system information area identifier is not configured, the terminal device needs to check the cell identifier to determine the validity of the stored version. In this way, when the cell identities are consistent, that is, when the SIB remains unchanged, the terminal device does not need to acquire the SIB again, which reduces the power consumption of the terminal.
  • the value of this area scope is the same as the value received from the serving cell's system scheduling information for this SIB,
  • the system information area identification (if present) and the system scheduling information received from the serving cell include The value label of the SIB is consistent with the NPN identifier, the system information area identifier and the value label associated with the stored version of the SIB,
  • the system information area identity (if any) and the value tag of the SIB included in the system scheduling information received from the serving cell are associated with the stored version of the SIB.
  • the PLMN identifier, system information area identifier and value label are consistent with each other,
  • the value of the area scope is the same as the value received in the system scheduling information for the SIB from the serving cell, and, if not in the system scheduling information Include the system information area ID, or,
  • the terminal device is NPN capable and the cell is an NPN only cell
  • the first NPN identity, cell identity and value tag included in the system scheduling information received from the serving cell for this SIB included in the NPN identity information list Consistent with the NPN identity, cell identity and value label associated with the stored version of the SIB
  • the stored SIB is considered valid for the cell.
  • the value of the area scope is the same as the value received from the system scheduling information for the SIB for the serving cell, and if the system information is included in the system scheduling information area ID,
  • the terminal device has NPN capability and the cell is an NPN-only cell, and the first NPN identity included in the NPN identity list, the system information area identity, and the value of the SIB included in the system scheduling information received from the serving cell
  • the label is consistent with the NPN identifier, the system information area identifier and the value label associated with the stored version of the SIB
  • the system information area identity information list if the first PLMN identity included in the PLMN identity information list, the system information area identity, and the PLMN identity associated with the stored version of the SIB, the value label of the SIB included in the system scheduling information received from the serving cell, The system information area ID and value label are consistent,
  • the value of the area scope is the same as the value received in the system scheduling information for the SIB from the serving cell, and, if not in the system scheduling information Include the system information area ID, or,
  • the terminal device has NPN capability and the cell is an NPN-only cell, and the first NPN identity included in the NPN identity information list, the cell identity included in the system scheduling information received from the serving cell for this SIB, and the value tag Consistent with the NPN identity, cell identity and value label associated with the stored version of the SIB,
  • the stored SIB is considered valid for the cell.
  • the terminal device in Rel-16 determines the validity of a stored version of an SIB by checking the system information area identifier, so as to avoid the uncertainty of the behavior of the terminal device and reduce the Test complexity and reduce equipment overhead.
  • the method takes into account that the terminal equipment in Rel-16 may have the ability to support non-public network (NPN), so that the terminal equipment can check the NPN identity, but not the PLMN identity, to determine the validity of a stored version of a SIB, thereby avoiding Uncertainty about the behavior of the terminal device when the network device does not broadcast the PLMN identity.
  • NPN non-public network
  • the terminal device when the system information area identifier is not configured, the terminal device needs to check the cell identifier to determine the validity of the stored version. In this way, when the cell identifiers are consistent, that is, when the SIB remains unchanged, the terminal does not need to acquire the SIB again, which reduces the power consumption of the terminal device.
  • the method may further include:
  • Step 1103 When the terminal device considers the stored version to be valid, use the SIB of the valid version;
  • Step 1104 When there is no valid version, the terminal device sends a system information request to the network device or obtains the SIB according to the scheduling information.
  • the terminal device when checking the validity of a stored version of an SIB, specifies the behavior of the terminal device when the system information area identifier is configured or not configured. Therefore, the uncertainty of the behavior of the terminal equipment can be avoided, and the complexity of testing and the overhead of the terminal equipment can be reduced.
  • the embodiment of the present application provides a method for configuring system information, and the method is applied to a network device.
  • the method is applied to the network device 101 in FIG. 2 .
  • FIG. 12 is a schematic diagram of a method for configuring system information according to Embodiment 5 of the present application. As shown in Figure 12, the method includes:
  • Step 1201 For terminal equipment-specific parameters, when the existence condition includes that the serving cell is configured with supplementary uplink, the network equipment considers the capabilities of the terminal equipment, or, for terminal equipment-specific parameters and cell-specific parameters, when the existence condition includes serving When the cell is configured with supplementary uplink, the network device does not consider the capability of the terminal device or the network device only considers that the network device provides the SUL configuration for the terminal device.
  • the network device considers the capabilities of the terminal device, including:
  • the network device determines that the terminal device can support the SUL frequency band provided in the SUL configuration; or,
  • the network device provides the terminal device with a SUL configuration, and based on the capabilities of the terminal device, the network device determines that the terminal device can support the SUL frequency band indicated in the SUL configuration.
  • the network device considers the capabilities of the terminal device, including:
  • supplementaryUplink supplementary Uplink
  • servingCellConfigCommon common cell configuration
  • the terminal device-specific parameter is tpc-Index and/or tpc-IndexSUL.
  • the parameter specific to the terminal device is OR information or IE or domain.
  • the terminal-device-specific parameter may also be a terminal-device-specific information or a terminal-device-specific IE or a terminal-device-specific field.
  • step 1201 when the existence condition includes that the serving cell is configured with supplementary uplink, the capability of the terminal device is not considered or only the SUL configuration provided by the network device for the terminal device is considered, including: first configuration information common to the cells
  • a configuration si-RequestConfigSUL for sending the system information message on the supplementary uplink is optionally provided in the scheduling information.
  • the configuration for sending the system information message on the supplementary uplink is optionally provided in the scheduling information.
  • the first configuration information may be a serving cell common configuration (servingCellConfigCommon).
  • step 1201 for example, when there is a supplementary uplink (supplementaryUplink) in the serving cell common configuration (servingCellConfigCommon) and when the system information broadcast status of any system information message (SI-message) in the scheduling information (SchedulingInfo) (for example, si-BroadcastStatus, When the posSI-BroadcastStatus) is set to not broadcast, the configuration (for example, si-RequestConfigSUL, posSI-RequestConfigSUL-r16) for sending the system information message on the supplementary uplink is optionally provided in the scheduling information.
  • supplementaryUplink supplementary Uplink
  • servingCellConfigCommon serving cell common configuration
  • SI-message system information message
  • SchedulingInfo scheduling information
  • the configuration for example, si-RequestConfigSUL, posSI-RequestConfigSUL-r16
  • supplementaryUplink supplementary Uplink
  • servingCellConfigCommon common cell configuration
  • system information broadcast status such as si-BroadcastStatus, posSI-BroadcastStatus
  • SI-message system information message
  • SchedulingInfo scheduling information
  • the configuration eg si-RequestConfigSUL, posSI-RequestConfigSUL-r16
  • si-RequestConfigSUL or posSI-RequestConfigSUL-r16 is vacant.
  • the existence condition of the configuration used for sending the system information message on the supplementary uplink is: when there is a supplementary uplink (supplementaryUplink) in the serving cell common configuration (servingCellConfigCommon) and when any system information in the scheduling information (SchedulingInfo) exists
  • supplementaryUplink supplementary uplink
  • servingCellConfigCommon serving cell common configuration
  • SchedulingInfo system information in the scheduling information
  • si-RequestConfigSUL existence condition SUL-MSG-1 may be defined in Table 5 below.
  • condition SUL-MSG-1 is only an exemplary name, and other names may also be used to represent, for example, the condition SUL-MSG1, the condition SUL-SI-Request, and the like.
  • the existence condition SUL-MSG-1 of posSI-RequestConfigSUL-r16 may be defined by the following Table 6.
  • tpc-Index existence condition SUL may be defined by the following Table 7.
  • tpc-Index existence condition SUL may be defined by the following Table 8.
  • the name used for each of the above conditions is only an exemplary name, and other names may also be used to represent, and the embodiment of the present application does not limit the form and format of these names.
  • the scheduling information is also called system scheduling information, and the scheduling information may be included in the SIB1.
  • the existence condition includes that the serving cell is configured with supplementary uplink
  • the capability of the terminal equipment is considered, or, for terminal equipment-specific parameters and cell-specific parameters, when the existence condition includes the service cell.
  • the supplementary uplink is configured in the cell
  • the capability of the terminal device is not considered or only the SUL configuration provided by the network device for the terminal device is considered.
  • the network device can specify the content in the SIB1, avoid the uncertainty of the realization of the network device, reduce the test cost of the network device product, and thus save the network deployment cost.
  • An embodiment of the present application provides an apparatus for configuring system information, and the apparatus is applied to a network device. Since the principle of the device for solving the problem is similar to that of the method in Embodiment 1, the specific implementation can refer to the implementation of the method described in Embodiment 1, and the same or related parts will not be repeated.
  • FIG. 13 is a schematic diagram of an apparatus for configuring system information according to Embodiment 6 of the present application. As shown in FIG. 13 , the apparatus 1300 includes:
  • a generating unit 1301 which generates scheduling information (SchedulingInfo) based on the association of the system information area identifier (systemInformationAreaID) and the area scope (areaScope); and
  • the generating unit 1301 compulsorily or optionally configures the area range for one or more SIBs in the scheduling information; when the scheduling information does not include When the system information area is identified, the area range is not configured in the scheduling information.
  • the necessary coding condition of the area scope in the scheduling information is: when the scheduling information includes the system information area identifier, the area scope is mandatory to exist; when the scheduling information does not include the system When the information area identifier, the area scope field does not exist, or, when the scheduling information includes the system information area identifier, the area scope field optionally exists; when the scheduling information does not include the system information area identifier, the area scope field The scope field does not exist.
  • the generating unit 1301 may configure the system information area identifier in the scheduling information when the scheduling information includes one or more area ranges configured for one SIB; when the scheduling information does not include When one or more areas are configured for one SIB, the system information area identifier is optionally configured in the scheduling information, or the system information area identifier is not configured in the scheduling information.
  • the necessary coding condition of the system information area identification field in the scheduling information is: when the scheduling information includes one or more area ranges configured for one SIB, the system information area identification field is forced to exist ; and the optional presence of the system information area identification field when the scheduling information does not include one or more area ranges configured for a SIB.
  • the necessary coding condition of the system information area identification field in the scheduling information is: when the scheduling information includes one or more area ranges configured for one SIB, the system information area identification field is mandatory to exist; and when the scheduling information includes one or more area ranges configured for one SIB When the information does not include one or more area ranges configured for a SIB, the system information area identification field does not exist.
  • the scheduling information may include the system information area identifier and the area range.
  • the scheduling information may be sent in the form of broadcasting.
  • the scheduling information may be included in SIB1.
  • the network device generates scheduling information based on the association between the system information area identifier and the area range, which can avoid the situation where the area range is configured but the system information area identifier is not configured, and therefore, the uncertainty of the behavior of the terminal device can be avoided. , and reduce the complexity of the test and the overhead of the terminal equipment.
  • An embodiment of the present application provides an apparatus for acquiring system information, and the apparatus is applied to a terminal device. Since the principle of the device for solving the problem is similar to that of the method in Embodiment 2, its specific implementation can refer to the implementation of the method described in Embodiment 2, and the same or related parts will not be repeated.
  • FIG. 14 is a schematic diagram of an apparatus for acquiring system information according to Embodiment 7 of the present application. As shown in FIG. 14 , the apparatus 1400 includes:
  • the first obtaining unit 1401 obtains scheduling information, where the scheduling information is generated based on the association between a system information area identifier (systemInformationAreaID) and an area scope (areaScope).
  • systemInformationAreaID system Information area identifier
  • areaScope area scope
  • the apparatus 1400 further includes:
  • the first determining unit 1402 determines whether a valid version of the SIB is stored according to the scheduling information and other information in the system information broadcast by the serving cell.
  • FIG. 15 is a schematic diagram of the first determination unit in Embodiment 7 of the present application. As shown in FIG. 15 , the first determination unit 1402 includes:
  • the second determination unit 1501 for a stored version of the SIB, when the system information area identifier in the scheduling information and the value tag (valueTag) associated with the SIB and the public land mobile network identifier (PLMN-Identity) in the other information )
  • the terminal device considers that the stored version is valid, or, for a stored version of the SIB, when the SIB in the scheduling information
  • the associated value tag (valueTag) and the public land mobile network identity (PLMN-Identity) in the other information, the cell identity and the value tag associated with the stored version, the public land mobile network identity and the cell identity (cellIdentity) and the cell identity are related.
  • the stored version is considered valid; or,
  • the third determining unit 1502 for a stored version of the SIB, when the system information area identifier in the scheduling information and the value tag associated with the SIB, the NPN identifier (NPN-Identity) and the cell identifier in the other information are associated with the SIB
  • the terminal device considers the storage version to be valid, or, for a stored version of the SIB, when the value associated with the SIB in the scheduling information is
  • the terminal device considers the stored version to be valid.
  • the apparatus 1400 further includes:
  • a first use unit 1403 which, when a valid version exists, uses the valid version of the SIB.
  • the second obtaining unit 1404 when there is no valid version, sends a system information request to the network device or obtains the SIB according to the scheduling information.
  • the scheduling information may include the system information area identifier and the area range.
  • the SIB may be at least one of SIB2, SIB3, SIB4, and SIB5, and in addition, the SIB may also be at least one of SIB9, SIB10, SIB11, SIB12, SIB13, and SIB14.
  • the scheduling information may be included in SIB1.
  • the terminal device obtains the scheduling information generated by the network device based on the association between the system information area identifier and the area scope, which can avoid the situation where the area scope is configured but the system information area identifier is not configured. Therefore, the behavior of the terminal device can be avoided. uncertainty, and reduce the complexity of the test and the overhead of the end equipment.
  • An embodiment of the present application provides an apparatus for acquiring system information, and the apparatus is applied to a terminal device. Since the principle of the device for solving the problem is similar to that of the method in Embodiment 4, the specific implementation can refer to the implementation of the method described in Embodiment 4, and the same or related parts will not be repeated.
  • FIG. 16 is a schematic diagram of an apparatus for acquiring system information according to Embodiment 8 of the present application. As shown in FIG. 16 , the apparatus 1600 includes:
  • the fourth determination unit 1601 for a stored version of a SIB, when the obtained scheduling information includes an area scope (areaScope) corresponding to the SIB, and when the scheduling information includes a system information area identifier (systemInformationAreaID) and the system information
  • areaScope area scope
  • systemInformationAreaID system information area identifier
  • the apparatus 1600 may further include:
  • the fifth determining unit 1602 for the stored version of an SIB, considers the stored version to be invalid when the obtained scheduling information includes a region range corresponding to the SIB, and when the scheduling information does not include a system information region identifier.
  • the apparatus 1600 may further include:
  • the apparatus 1600 may further include:
  • the seventh determination unit 1604 for the stored version of an SIB, when the obtained scheduling information includes an area scope (areaScope) corresponding to the SIB, and when the scheduling information does not include the system information area identifier and the first information and the cell are When the identity (cellIdentity) is the same as the corresponding information associated with the stored version and the cell identity, the stored version is considered valid.
  • areaScope area scope
  • cellIdentity identity
  • the first information may include: the first PLMN identity (PLMN-Identity) received from the serving cell and included in the PLMN identity information list (PLMN-IdentityInfoList) and included in the scheduling information
  • PLMN-IdentityInfoList the PLMN identity information list
  • valueTag value tag
  • the corresponding information may include: a PLMN identity (PLMN-Identity) associated with the stored version of the SIB and a value tag.
  • PLMN-Identity PLMN identity
  • the first information includes: the first information received from the serving cell and included in the PLMN identity information list (PLMN-IdentityInfoList) A PLMN identity (PLMN-Identity) and a value tag (valueTag) associated with the SIB included in the scheduling information; the corresponding information includes: a PLMN identity (PLMN-Identity) and a value associated with the stored version of the SIB Label.
  • PLMN-IdentityInfoList A PLMN identity (PLMN-Identity) and a value tag (valueTag) associated with the SIB included in the scheduling information
  • PLMN-Identity PLMN identity
  • valueTag value tag
  • the first information may include: the first NPN identifier received from the serving cell and included in the NPN identifier information list (NPN-IdentityInfoList) and the SIB association included in the scheduling information
  • the corresponding information includes: the NPN identifier and the value tag associated with the stored version of the SIB.
  • the first information includes: the first information received from the serving cell including the NPN identification information list (NPN-IdentityInfoList)
  • NPN-IdentityInfoList The NPN identifier and the value tag (valueTag) associated with the SIB included in the scheduling information
  • the corresponding information includes: the NPN identifier and the value tag associated with the stored version of the SIB.
  • the apparatus 1600 may further include:
  • a second using unit 1605 which uses the SIB of the valid version when the terminal device considers the stored version to be valid.
  • the terminal device obtains the scheduling information generated by the network device based on the association between the system information area identifier and the area scope, which can avoid the situation where the area scope is configured but the system information area identifier is not configured. Therefore, the behavior of the terminal device can be avoided. uncertainty, and reduce the complexity of the test and the overhead of the end equipment.
  • An embodiment of the present application provides an apparatus for configuring system information, and the apparatus is applied to a network device. Since the principle of the device for solving the problem is similar to that of the method in Embodiment 5, the specific implementation can refer to the implementation of the method described in Embodiment 5, and the same or related parts will not be repeated.
  • FIG. 17 is a schematic diagram of an apparatus for acquiring system information according to Embodiment 9 of the present application. As shown in FIG. 17 , the apparatus 1700 includes:
  • the configuration unit 1701 for terminal equipment-specific parameters, when the existence condition includes that the serving cell is configured with supplementary uplink, considers the capability of the terminal equipment, or, for terminal equipment-specific parameters and cell-specific parameters, when the existence condition includes the serving cell.
  • the supplementary uplink is configured, the capability of the terminal device is not considered or only the SUL configuration provided by the network device for the terminal device is considered.
  • the network device considers the capabilities of the terminal device, including:
  • the network device determines that the terminal device can support the SUL frequency band provided in the SUL configuration; or,
  • the network device provides the terminal device with a SUL configuration, and based on the capabilities of the terminal device, the network device determines that the terminal device can support the SUL frequency band indicated in the SUL configuration.
  • the network device considers the capabilities of the terminal device, including:
  • supplementaryUplink supplementary Uplink
  • servingCellConfigCommon common cell configuration
  • the terminal device-specific parameter is tpc-Index and/or tpc-IndexSUL.
  • the parameter specific to the terminal device is OR information or IE or domain.
  • the terminal-device-specific parameter may also be a terminal-device-specific information or a terminal-device-specific IE or a terminal-device-specific field.
  • the capability of the terminal device is not considered or only the network device provides the SUL configuration for the terminal device, including: when the cell common first
  • the supplementary uplink configuration for sending the system information message for example, si-RequestConfigSUL, posSI-RequestConfigSUL-r16
  • the system information message for example, si-RequestConfigSUL, posSI-RequestConfigSUL-r16
  • the first configuration information may be a serving cell common configuration (servingCellConfigCommon).
  • the configuration unit 1701 has a supplementary uplink (supplementaryUplink) in the serving cell common configuration (servingCellConfigCommon) and when the system information broadcast status (for example, si-message) of any system information message (SI-message) in the scheduling information (SchedulingInfo)
  • the configuration eg si-RequestConfigSUL, posSI-RequestConfigSUL-r16
  • si-RequestConfigSUL, posSI-RequestConfigSUL-r16 for sending the system information message on the supplementary uplink is optionally provided in the scheduling information.
  • the existence condition of the configuration used for sending the system information message on the supplementary uplink is:
  • supplementaryUplink supplementary Uplink
  • servingCellConfigCommon serving cell common configuration
  • SI-BroadcastStatus posSI-BroadcastStatus
  • SI-message system information message
  • SchedulingInfo scheduling information
  • the scheduling information may be included in SIB1.
  • the existence condition includes that the serving cell is configured with supplementary uplink
  • the capability of the terminal equipment is considered, or, for terminal equipment-specific parameters and cell-specific parameters, when the existence condition includes the service cell.
  • the supplementary uplink is configured in the cell
  • the capability of the terminal device is not considered or only the SUL configuration provided by the network device for the terminal device is considered.
  • the network device can specify the content in the SIB1, avoid the uncertainty of the realization of the network device, reduce the test cost of the network device product, and thus save the network deployment cost.
  • An embodiment of the present application provides a network device, where the network device includes the apparatus for configuring system information as described in Embodiment 6.
  • FIG. 18 is a schematic block diagram of a system configuration of a network device according to Embodiment 10 of the present application.
  • the network device 1800 may include: a processor 1810 and a memory 1820 ; the memory 1820 is coupled to the processor 1810 .
  • the memory 1820 can store various data; in addition, the program 1830 for information processing is also stored, and the program 1830 is executed under the control of the processor 1810 to receive various information sent by the terminal device and send various information to the terminal device. .
  • the functionality of the configuration device for system information may be integrated into the processor 1810 .
  • the processor 1810 may be configured to: generate scheduling information (SchedulingInfo) based on the association between the system information area identifier (systemInformationAreaID) and the area scope (areaScope); and send the scheduling information.
  • schedulingInfo scheduling information
  • systemInformationAreaID systemInformationAreaID
  • areaScope areaScope
  • the generating scheduling information based on the association between the system information area identifier and the area scope includes: when the scheduling information includes the system information area identifier, the network device configures the area scope for one or more SIBs in the scheduling information Or optionally configure the area range for one or more SIBs in the scheduling information.
  • the generating scheduling information based on the association between the system information area identifier and the area scope further includes: when the scheduling information does not include the system information area identifier, the network device does not configure the area scope in the scheduling information.
  • the necessary coding condition of the area scope field in the scheduling information is: when the scheduling information includes the system information area identifier, the area scope field is forced to exist; when the scheduling information does not include the system information area identifier , the area scope field does not exist, or, when the scheduling information includes the system information area identifier, the area scope field optionally exists; when the scheduling information does not include the system information area identifier, the area scope field does not exist .
  • the generating scheduling information based on the association between the system information area identifier and the area scope includes: when the scheduling information includes one or more area scopes configured for one SIB, the network device configures the system information area identifier in the in scheduling information.
  • the generating scheduling information based on the association between the system information area identifier and the area scope further includes: when the scheduling information does not include one or more area scopes configured for one SIB, the network device may use the system information area identifier to be available.
  • the selected configuration is in the scheduling information, or the network device does not configure the system information area identifier in the scheduling information.
  • the necessary coding conditions for the system information area identification field in the scheduling information are: when the scheduling information includes one or more area ranges configured for one SIB, the system information area identification field is mandatory to exist; and when the scheduling information When the information does not include one or more area ranges configured for a SIB, the system information area identification field is optionally present.
  • the necessary coding conditions for the system information area identification field in the scheduling information are: when the scheduling information includes one or more area ranges configured for one SIB, the system information area identification field is mandatory to exist; and when the scheduling information When the information does not include one or more area ranges configured for a SIB, the system information area identification field does not exist.
  • the scheduling information includes the system information area identifier and the area range.
  • the scheduling information is sent in the form of broadcasting.
  • the scheduling information is included in SIB1.
  • the device for configuring system information can be configured separately from the processor 1810 , for example, the device for configuring system information can be configured as a chip connected to the processor 1810 , and the configuration of the system information is implemented through the control of the processor 1810 . function of the device.
  • the network device 1800 may further include: a transceiver 1840, an antenna 1850, etc.; wherein, the functions of the above components are similar to those in the prior art, and details are not repeated here. It is worth noting that the network device 1800 does not necessarily include all the components shown in FIG. 18 ; in addition, the network device 1800 may also include components not shown in FIG. 18 , and reference may be made to the prior art.
  • the network device generates scheduling information based on the correlation between the system information area identifier and the area scope, which can avoid the situation where the area scope is configured but the system information area identifier is not configured, and therefore, the uncertainty of the behavior of the terminal device can be avoided. , and reduce the complexity of the test and the overhead of the terminal equipment.
  • An embodiment of the present application provides a terminal device, where the terminal device includes the apparatus for acquiring system information as described in Embodiment 7.
  • FIG. 19 is a schematic block diagram of a system configuration of a terminal device according to Embodiment 11 of the present application.
  • the terminal device 1900 may include a processor 1910 and a memory 1920 ; the memory 1920 is coupled to the processor 1910 .
  • this figure is exemplary; other types of structures may be used in addition to or in place of this structure to implement telecommunication functions or other functions.
  • the function of the apparatus for acquiring system information may be integrated into the processor 1910 .
  • the processor 1910 may be configured to obtain scheduling information, the scheduling information being generated based on the association of a system information area identifier (systemInformationAreaID) and an area scope (areaScope).
  • systemInformationAreaID system Information area identifier
  • areaScope area scope
  • the processor 1910 may also be configured to: for an SIB, determine whether a valid version of the SIB is stored according to the scheduling information and other information in the system information broadcast by the serving cell.
  • determining whether a valid version of the SIB is stored according to the scheduling information and other information in the system information broadcast by the serving cell includes: for a stored version of the SIB, when the system information area identifier in the scheduling information and the When the value tag (valueTag) associated with the SIB and the public land mobile network identity (PLMN-Identity) in the other information are the same as the system information area identification, value tag and public land mobile network identification associated with the stored version, the terminal device considers that The stored version is valid, or, for a stored version of the SIB, when the value tag (valueTag) associated with the SIB in the scheduling information and the public land mobile network identity (PLMN-Identity), cell identity in the other information and When the value tag, the public land mobile network identity and the cell identity (cellIdentity) associated with the stored version are the same, the terminal device considers the stored version to be valid; or, for a stored version of the SIB, when the system information area in the scheduling information When the identifier, the value label associated with the SIB,
  • the processor 1910 may also be configured to: when there is a valid version, the terminal device uses the valid version of the SIB; and when there is no valid version, the terminal device sends a system information request to the network device or according to the The scheduling information acquires the SIB.
  • the scheduling information includes the system information area identifier and the area range.
  • the SIB may be at least one of SIB2, SIB3, SIB4, and SIB5, and in addition, the SIB may be at least one of SIB9, SIB10, SIB11, SIB12, SIB13, and SIB14.
  • the scheduling information is included in SIB1.
  • the device for acquiring system information may be configured separately from the processor 1910 , for example, the device for acquiring system information may be configured as a chip connected to the processor 1910 , and the system information is acquired through the control of the processor 1910 . function of the device.
  • the terminal device 1900 may further include: a communication module 1930 , an input unit 1940 , a display 1950 , and a power supply 1960 . It is worth noting that the terminal device 1900 does not necessarily include all the components shown in FIG. 19 ; in addition, the terminal device 1900 may also include components not shown in FIG. 19 , and reference may be made to the related art.
  • the processor 1910 also sometimes referred to as a controller or operational control, may include a microprocessor or other processor device and/or logic device that receives input and controls the operation of the various components of the terminal device 1900. operate.
  • the memory 1920 may be one or more of a cache, flash memory, hard drive, removable medium, volatile memory, non-volatile memory or other suitable devices. Various kinds of data can be stored, and programs that execute the related information can also be stored. And the processor 1910 can execute the program stored in the memory 1920 to realize information storage or processing. The functions of other components are similar to the existing ones, and will not be repeated here.
  • Each component of the terminal device 1200 may be implemented by dedicated hardware, firmware, software, or a combination thereof, without departing from the scope of the present application.
  • the terminal device obtains the scheduling information generated by the network device based on the association between the system information area identifier and the area scope, which can avoid the situation where the area scope is configured but the system information area identifier is not configured. Therefore, the behavior of the terminal device can be avoided. uncertainty, and reduce the complexity of the test and the overhead of the end equipment.
  • An embodiment of the present application provides a terminal device, where the terminal device includes the apparatus for acquiring system information as described in Embodiment 8.
  • FIG. 20 is a schematic block diagram of a system configuration of a terminal device according to Embodiment 12 of the present application.
  • the terminal device 2000 may include a processor 2010 and a memory 2020 ; the memory 2020 is coupled to the processor 2010 .
  • this figure is exemplary; other types of structures may be used in addition to or in place of this structure to implement telecommunication functions or other functions.
  • the function of the apparatus for acquiring system information may be integrated into the processor 2010 .
  • the processor 2010 may be configured to: for a stored version of a SIB, when the obtained scheduling information includes an area scope (areaScope) corresponding to the SIB, and when the scheduling information includes a system information area identifier (systemInformationAreaID) and the system
  • areaScope area scope
  • systemInformationAreaID system information area identifier
  • the processor 2010 may be further configured to: for the stored version of an SIB, when the obtained scheduling information includes the area range corresponding to the SIB, and when the scheduling information does not include the system information area identifier, the terminal device The stored version is considered invalid.
  • the processor 2010 may be further configured to: for the stored version of an SIB, when the obtained scheduling information includes a region range corresponding to the SIB, and when the scheduling information does not include a system information region identifier and the first information is the same as the When the corresponding information associated with the stored version is the same, the terminal device considers the stored version to be valid.
  • the processor 2010 may also be configured to: for the stored version of an SIB, when the obtained scheduling information includes an area scope (areaScope) corresponding to the SIB, and when the scheduling information does not include the system information area identifier and the first When a piece of information and a cell identity (cellIdentity) are the same as the corresponding information and cell identity associated with the stored version, the terminal device considers the stored version to be valid.
  • areaScope area scope
  • cellIdentity cell identity
  • the first information includes: the first PLMN identity (PLMN-Identity) included in the PLMN identity information list (PLMN-IdentityInfoList) received from the serving cell and the value associated with the SIB included in the scheduling information Tag (valueTag); the corresponding information includes: a PLMN identity (PLMN-Identity) associated with the stored version of the SIB and a value tag.
  • PLMN-Identity the first PLMN identity included in the PLMN identity information list
  • valueTag the value associated with the SIB included in the scheduling information Tag
  • the corresponding information includes: a PLMN identity (PLMN-Identity) associated with the stored version of the SIB and a value tag.
  • the first information includes: the first information received from the serving cell and included in the PLMN identity information list (PLMN-IdentityInfoList) A PLMN identity (PLMN-Identity) and a value tag (valueTag) associated with the SIB included in the scheduling information; the corresponding information includes: a PLMN identity (PLMN-Identity) and a value associated with the stored version of the SIB Label.
  • PLMN-IdentityInfoList A PLMN identity (PLMN-Identity) and a value tag (valueTag) associated with the SIB included in the scheduling information
  • PLMN-Identity PLMN identity
  • valueTag value tag
  • the first information includes: the first NPN identifier in the NPN identification information list (NPN-IdentityInfoList) received from the serving cell and the value tag (valueTag) associated with the SIB included in the scheduling information;
  • the Corresponding information includes: an NPN identifier and a value tag associated with the stored version of the SIB.
  • the first information includes: the first information received from the serving cell including the NPN identification information list (NPN-IdentityInfoList)
  • NPN-IdentityInfoList The NPN identifier and the value tag (valueTag) associated with the SIB included in the scheduling information
  • the corresponding information includes: the NPN identifier and the value tag associated with the stored version of the SIB.
  • the processor 2010 may also be configured to: when the terminal device considers the stored version to be valid, use the SIB of the valid version; and when there is no valid version, the terminal device sends a system information request or The SIB is acquired according to the scheduling information. .
  • the apparatus for acquiring system information may be configured separately from the processor 2010 , for example, the apparatus for acquiring system information may be configured as a chip connected to the processor 2010 , and the acquisition of the system information is realized through the control of the processor 2010 . function of the device.
  • the terminal device 2000 may further include: a communication module 2030 , an input unit 2040 , a display 2050 , and a power supply 2060 . It is worth noting that the terminal device 2000 does not necessarily have to include all the components shown in FIG. 20; in addition, the terminal device 2000 may also include components not shown in FIG. 20, and reference may be made to the related art.
  • the processor 2010, also sometimes referred to as a controller or operational control, may include a microprocessor or other processor device and/or logic device that receives input and controls the various components of the terminal device 2000. operate.
  • the memory 2020 may be 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.
  • Various kinds of data can be stored, and programs that execute the related information can also be stored.
  • the processor 2010 can execute the program stored in the memory 2020 to realize information storage or processing.
  • the functions of other components are similar to the existing ones, and will not be repeated here.
  • Each component of the terminal device 2000 may be implemented by dedicated hardware, firmware, software, or a combination thereof, without departing from the scope of the present application.
  • the terminal device when checking the validity of a stored version of an SIB, specifies the behavior of the terminal device when the system information area identifier is configured or not configured. Therefore, the uncertainty of the behavior of the terminal equipment can be avoided, and the complexity of testing and the overhead of the terminal equipment can be reduced.
  • An embodiment of the present application provides a network device, where the network device includes the apparatus for configuring system information as described in Embodiment 9.
  • FIG. 21 is a schematic block diagram of a system configuration of a network device according to Embodiment 13 of the present application.
  • the network device 2100 may include: a processor 2110 and a memory 2120 ; the memory 2120 is coupled to the processor 2110 .
  • the memory 2120 can store various data; in addition, the program 2130 for information processing is also stored, and the program 2130 is executed under the control of the processor 2110 to receive various information sent by the terminal device and send various information to the terminal device. .
  • the functionality of the configuration device for system information may be integrated into the processor 2110 .
  • the processor 2110 may be configured to: for terminal device-specific parameters, when the existence condition includes that the serving cell is configured with supplementary uplink, the network device considers the capability of the terminal device, or, for terminal device-specific parameters and cell-specific parameters parameter, when the existence condition includes that the serving cell is configured with supplementary uplink, the network device does not consider the capability of the terminal device or the network device only considers that the network device provides the SUL configuration for the terminal device.
  • the network device considers the capability of the terminal device, including: based on the capability of the terminal device, the network device determines that the terminal device can support the SUL frequency band provided in the SUL configuration; or, the network device provides the SUL configuration for the terminal device , and based on the capability of the terminal device, the network device determines that the terminal device can support the SUL frequency band indicated in the SUL configuration.
  • the network device considers the capabilities of the terminal device, including: the presence of a supplementary uplink (supplementaryUplink) in the common cell configuration (servingCellConfigCommon) indicates that the network device provides the SUL configuration for the terminal device.
  • supplementaryUplink a supplementary uplink
  • servingCellConfigCommon a common cell configuration
  • the terminal device-specific parameters are tpc-Index and/or tpc-IndexSUL.
  • the terminal-specific parameters are OR information or IE or domain.
  • the terminal-device-specific parameter may also be a terminal-device-specific information or a terminal-device-specific IE or a terminal-device-specific field.
  • the capability of the terminal device is not considered or only the network device is considered to provide the SUL configuration for the terminal device, including: when the first configuration information common to the cell includes the supplementary uplink configuration
  • the configuration for example, si-RequestConfigSUL, posSI-RequestConfigSUL-r16
  • the configuration for example, si-RequestConfigSUL, posSI-RequestConfigSUL-r16
  • the scheduling information for example, si-RequestConfigSUL, posSI-RequestConfigSUL-r16
  • the first configuration information is a serving cell common configuration (servingCellConfigCommon).
  • supplementaryUplink supplementary Uplink
  • servingCellConfigCommon serving cell common configuration
  • system information broadcast status such as si-BroadcastStatus, posSI-BroadcastStatus
  • SI-message system information message
  • SchedulingInfo scheduling information
  • the existence condition of the configuration used for sending the system information message on the supplementary uplink is: when there is a supplementary uplink (supplementaryUplink) in the serving cell common configuration (servingCellConfigCommon) and when any system information message (SI-message) in the scheduling information (SchedulingInfo) ) when the system information broadcast status (such as si-BroadcastStatus, posSI-BroadcastStatus) is set to not broadcast, the configuration for sending system information messages on the supplementary uplink is optional, otherwise, the supplementary uplink is used for system information messages The configuration sent is vacant.
  • the scheduling information is included in SIB1.
  • the device for configuring system information can be configured separately from the processor 2110 .
  • the device for configuring system information can be configured as a chip connected to the processor 2110 , and the configuration of the system information can be realized through the control of the processor 2110 . function of the device.
  • the network device 2100 may further include: a transceiver 2140, an antenna 2150, etc.; wherein, the functions of the above components are similar to those in the prior art, and details are not repeated here. It is worth noting that the network device 2100 does not necessarily include all the components shown in FIG. 21 ; in addition, the network device 2100 may also include components not shown in FIG. 21 , and reference may be made to the prior art.
  • the existence condition includes that the serving cell is configured with supplementary uplink
  • the capability of the terminal equipment is considered, or, for terminal equipment-specific parameters and cell-specific parameters, when the existence condition includes the service cell.
  • the supplementary uplink is configured in the cell
  • the capability of the terminal device is not considered or only the SUL configuration provided by the network device for the terminal device is considered.
  • the network device can specify the content in the SIB1, avoid the uncertainty of the realization of the network device, reduce the test cost of the network device product, and thus save the network deployment cost.
  • An embodiment of the present application provides a communication system, including the network device according to Embodiment 10 and/or the terminal device according to Embodiment 11, or the communication system includes the terminal device according to Embodiment 12, Alternatively, the communication system includes the network device according to Embodiment 13.
  • the structure of the communication system may refer to FIG. 1.
  • the communication system 100 includes a network device 101 and a terminal device 102.
  • the network device 101 is the same as the network device described in Embodiment 10 or Embodiment 13, and/ Or, the terminal device 102 is the same as the terminal device described in Embodiment 11 or Embodiment 12, and repeated content will not be repeated.
  • the apparatuses and methods above in the present application may be implemented by hardware, or may be implemented by hardware combined with software.
  • the present application relates to a computer-readable program that, when executed by logic components, enables the logic components to implement the above-described apparatus or constituent components, or causes the logic components to implement the above-described various methods or steps.
  • Logic components such as field programmable logic components, microprocessors, processors used in computers, and the like.
  • the present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, and the like.
  • the method/apparatus described in conjunction with the embodiments of this application 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 shown in FIG. 13 and/or one or more combinations of the functional block diagrams may correspond to either each software module of the computer program flow or each hardware module.
  • These software modules may correspond to the respective steps shown in FIG. 3 .
  • These hardware modules can be implemented by, for example, solidifying these software modules using a Field Programmable Gate Array (FPGA).
  • FPGA Field Programmable Gate Array
  • a software module may reside 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 can be coupled to the processor, such that the processor can read information from, and write information to, the storage medium; or the storage medium can be an integral part of the processor.
  • the processor and storage medium may reside in an 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 FIG. 13 can be implemented as a general-purpose processor, a digital signal processor ( DSP), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any suitable combination thereof.
  • DSP digital signal processor
  • ASICs Application Specific Integrated Circuits
  • FPGAs Field Programmable Gate Arrays
  • One or more of the functional blocks and/or one or more combinations of the functional blocks described with respect to FIG. 13 can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microcomputers A processor, one or more microprocessors in communication with a DSP, or any other such configuration.
  • An apparatus for configuring system information the apparatus is applied to network equipment, and the apparatus comprises:
  • a generating unit that generates scheduling information (SchedulingInfo) based on the association of the system information area identifier (systemInformationAreaID) and the area scope (areaScope); and
  • a sending unit which sends the scheduling information.
  • the generating unit configures the area range for one or more SIBs in the scheduling information, or optionally one or more SIBs in the scheduling information.
  • the SIB configures the area scope.
  • the generating unit does not configure the area range in the scheduling information.
  • the area scope field is forced to exist; when the scheduling information does not include the system information area identifier, the area scope field does not exist, or,
  • the area scope field optionally exists; when the scheduling information does not include the system information area identifier, the area scope field does not exist.
  • the generating unit configures the system information area identifier in the scheduling information when the scheduling information includes one or more area ranges configured for one SIB.
  • the generating unit optionally configures the system information area identifier in the scheduling information, or does not configure the system information.
  • the area identifier is configured in the scheduling information.
  • the system information area identification field is mandatory to exist.
  • the system information area identification field may optionally exist.
  • the system information area identification field is mandatory to exist.
  • the system information area identification field does not exist.
  • the scheduling information includes the system information area identifier and the area range.
  • the scheduling information is sent in the form of broadcasting.
  • the scheduling information is included in SIB1.
  • An apparatus for acquiring system information the apparatus being applied to terminal equipment, the apparatus comprising:
  • a first obtaining unit which obtains scheduling information, where the scheduling information is generated based on the association between a system information area identifier (systemInformationAreaID) and an area scope (areaScope).
  • systemInformationAreaID system Information area identifier
  • areaScope areaScope
  • the first determining unit determines whether a valid version of the SIB is stored according to the scheduling information and other information in the system information broadcast by the serving cell.
  • the second determination unit is, for a stored version of the SIB, when the system information area identifier in the scheduling information and the value tag (valueTag) associated with the SIB and the public land mobile network identifier in the other information ( PLMN-Identity) when the system information area identifier, value label and public land mobile network identifier associated with the stored version are the same, the terminal device considers the stored version to be valid, or, for a stored version of the SIB, when The value tag (valueTag) associated with the SIB in the scheduling information and the public land mobile network identity (PLMN-Identity) in the other information, the value tag associated with the cell identity and the stored version, the public land mobile network When the identity and the cell identity (cellIdentity) are the same, the stored version is considered to be valid; or,
  • the third determination unit for a stored version of the SIB, when the system information area identifier in the scheduling information, the value tag associated with the SIB, and the NPN identifier (NPN-Identity) in the other information are related to the When the system information area identifier, value label and NPN identifier associated with the stored version are the same, the terminal device considers that the stored version is valid, or, for a stored version of the SIB, when the SIB in the scheduling information When the associated value tag and the NPN-Identity (NPN-Identity) and cell ID in the other information are the same as the value tag, NPN ID, and cell ID associated with the stored version, the stored version is considered valid.
  • a second acquiring unit which, when there is no valid version, sends a system information request to the network device or acquires the SIB according to the scheduling information.
  • the scheduling information includes the system information area identifier and the area range.
  • the SIB is at least one of SIB2, SIB3, SIB4 and SIB5.
  • the scheduling information is included in SIB1.
  • An apparatus for acquiring system information the apparatus being applied to terminal equipment, the apparatus comprising:
  • the fourth determination unit for a stored version of a SIB, when the obtained scheduling information includes an area scope (areaScope) corresponding to the SIB, and when the scheduling information includes a system information area identifier (systemInformationAreaID) and the When the system information area identifier and the first information are the same as the system information area identifier and corresponding information associated with the stored version, the stored version is considered valid.
  • areaScope area scope
  • systemInformationAreaID system information area identifier
  • the fifth determination unit for the storage version of an SIB, when the obtained scheduling information includes the area range corresponding to the SIB, and when the scheduling information does not include the system information area identifier, consider the storage version invalid.
  • the sixth determining unit for the stored version of one SIB, when the obtained scheduling information includes a region range corresponding to the SIB, and when the scheduling information does not include a system information region identifier and the first information is the same as the When the corresponding information associated with the stored version is the same, the stored version is considered valid.
  • a seventh determination unit for the stored version of an SIB, when the obtained scheduling information includes an area scope (areaScope) corresponding to the SIB, and when the scheduling information does not include a system information area identifier and the first information
  • the stored version is considered to be valid.
  • the first information includes: the first PLMN identification (PLMN-Identity) included in the PLMN identification information list (PLMN-IdentityInfoList) received from the serving cell and the SIB associated with the SIB included in the scheduling information. value tag (valueTag);
  • the corresponding information includes: a PLMN identity (PLMN-Identity) associated with the stored version of the SIB and a value tag.
  • PLMN-Identity PLMN identity
  • the terminal device does not have NPN capability or the serving cell is not an NPN-only (NPN-only) cell
  • the first information includes: the first PLMN identification (PLMN-Identity) included in the PLMN identification information list (PLMN-IdentityInfoList) received from the serving cell and the SIB associated information included in the scheduling information. value tag (valueTag);
  • the corresponding information includes: a PLMN identity (PLMN-Identity) associated with the stored version of the SIB and a value tag.
  • PLMN-Identity PLMN identity
  • the first information includes: received from the serving cell and includes the first NPN identification in the NPN identification information list (NPN-IdentityInfoList) and the SIB associated value tag (valueTag) included in the scheduling information;
  • the corresponding information includes an NPN identifier and a value tag associated with the stored version of the SIB.
  • the serving cell is an NPN-only (NPN-only) cell
  • the first information includes: received from the serving cell and includes the first NPN identification in the NPN identification information list (NPN-IdentityInfoList) and the SIB associated value tag (valueTag) included in the scheduling information;
  • the corresponding information includes an NPN identifier and a value tag associated with the stored version of the SIB.
  • a second using unit which uses the SIB of the valid version when the terminal device considers the stored version to be valid
  • a third obtaining unit where when there is no valid version, the terminal device sends a system information request to the network device or obtains the SIB according to the scheduling information.
  • a network device comprising the apparatus according to any one of appendices 1-11.
  • a terminal device comprising the apparatus according to any one of appendices 12-27.
  • a communication system comprising the network device according to appendix 33/or the terminal device according to appendix 34.
  • a method for configuring system information comprising:
  • schedulingInfo based on the association of the system information area identifier (systemInformationAreaID) and the area scope (areaScope);
  • the scheduling information is sent.
  • the network device configures the area range for one or more SIBs in the scheduling information, or optionally one or more SIBs in the scheduling information
  • the SIB configures the area scope.
  • the network device When the scheduling information does not include the system information area identifier, the network device does not configure the area range in the scheduling information.
  • the area scope field is forced to exist; when the scheduling information does not include the system information area identifier, the area scope field does not exist, or,
  • the area scope field optionally exists; when the scheduling information does not include the system information area identifier, the area scope field does not exist.
  • the network device configures the system information area identifier in the scheduling information.
  • the network device When the scheduling information does not include one or more area ranges configured for one SIB, the network device optionally configures the system information area identifier in the scheduling information, or the network device does not configure the system information area identifier in the scheduling information.
  • the system information area identifier is configured in the scheduling information.
  • the system information area identification field is mandatory to exist.
  • the system information area identification field may optionally exist.
  • the system information area identification field is mandatory to exist.
  • the system information area identification field does not exist.
  • the scheduling information includes the system information area identifier and the area range.
  • the scheduling information is sent in the form of broadcasting.
  • the scheduling information is included in SIB1.
  • a method for acquiring system information comprising:
  • the scheduling information is obtained, the scheduling information is generated based on the association of the system information area ID (systemInformationAreaID) and the area scope (areaScope).
  • systemInformationAreaID systemInformationAreaID
  • areaScope areaScope
  • SIB For one SIB, it is determined whether a valid version of the SIB is stored according to the scheduling information and other information in the system information broadcast by the serving cell.
  • the terminal device For a stored version of the SIB, when the system information area identifier in the scheduling information and the value tag (valueTag) associated with the SIB and the public land mobile network identifier (PLMN-Identity) in the other information are related to the When the system information area identifier, value label and public land mobile network identifier associated with the stored version are the same, the terminal device considers the stored version to be valid, or, for a stored version of the SIB, when the scheduling information The value tag (valueTag) associated with the SIB and the public land mobile network identity (PLMN-Identity) in the other information, the value tag associated with the cell identity and the stored version, the public land mobile network identity and the cell identity (cellIdentity) ) is the same, the terminal device considers the stored version to be valid; or,
  • the terminal device For a stored version of the SIB, when the system information area identifier in the scheduling information, the value tag associated with the SIB, and the NPN identifier (NPN-Identity) in the other information are associated with the stored version of the system When the information area identifier, value label and NPN identifier are the same, the terminal device considers the stored version to be valid, or, for a stored version of the SIB, when the value label associated with the SIB in the scheduling information and all When the NPN identity (NPN-Identity), cell identity and the value tag, NPN identity and cell identity associated with the stored version in the other information are the same, the terminal device considers the stored version to be valid.
  • NPN identity NPN-Identity
  • the terminal device uses the valid version of the SIB.
  • the terminal device When there is no valid version, the terminal device sends a system information request to the network device or acquires the SIB according to the scheduling information.
  • the scheduling information includes the system information area identifier and the area range.
  • the SIB is at least one of SIB2, SIB3, SIB4 and SIB5.
  • the scheduling information is included in SIB1.
  • a method for acquiring system information comprising:
  • the terminal device For a stored version of a SIB, when the obtained scheduling information includes an area scope (areaScope) corresponding to the SIB, and when the scheduling information includes a system information area identifier (systemInformationAreaID) and the system information area identifier and the first When a piece of information is the same as the system information area identifier and corresponding information associated with the stored version, the terminal device considers the stored version to be valid.
  • areaScope area scope
  • systemInformationAreaID system information area identifier
  • the terminal device For the stored version of one SIB, when the obtained scheduling information includes a region range corresponding to the SIB, and when the scheduling information does not include a system information region identifier, the terminal device considers the stored version to be invalid.
  • the terminal device For the stored version of an SIB, when the obtained scheduling information includes a region range corresponding to the SIB, and when the scheduling information does not include a system information region identifier and the first information is associated with the corresponding information of the stored version When the same, the terminal device considers the stored version to be valid.
  • the terminal device For the stored version of an SIB, when the obtained scheduling information includes an area scope (areaScope) corresponding to the SIB, and when the scheduling information does not include a system information area identifier and the first information and a cell identifier (cellIdentity) When the corresponding information associated with the stored version and the cell identity are the same, the terminal device considers the stored version to be valid.
  • areaScope area scope
  • cellIdentity cell identifier
  • the first information includes: the first PLMN identification (PLMN-Identity) included in the PLMN identification information list (PLMN-IdentityInfoList) received from the serving cell and the SIB associated information included in the scheduling information. value tag (valueTag);
  • the corresponding information includes: a PLMN identity (PLMN-Identity) associated with the stored version of the SIB and a value tag.
  • PLMN-Identity PLMN identity
  • the terminal device does not have NPN capability or the serving cell is not an NPN-only (NPN-only) cell
  • the first information includes: the first PLMN identification (PLMN-Identity) included in the PLMN identification information list (PLMN-IdentityInfoList) received from the serving cell and the SIB associated information included in the scheduling information. value tag (valueTag);
  • the corresponding information includes: a PLMN identity (PLMN-Identity) associated with the stored version of the SIB and a value tag.
  • PLMN-Identity PLMN identity
  • the first information includes: received from the serving cell and includes the first NPN identifier in the NPN identifier information list (NPN-IdentityInfoList) and the value tag (valueTag) associated with the SIB included in the scheduling information;
  • the corresponding information includes an NPN identifier and a value tag associated with the stored version of the SIB.
  • the serving cell is an NPN-only (NPN-only) cell
  • the first information includes: received from the serving cell and includes the first NPN identification in the NPN identification information list (NPN-IdentityInfoList) and the SIB associated value tag (valueTag) included in the scheduling information;
  • the corresponding information includes an NPN identifier and a value tag associated with the stored version of the SIB.
  • the terminal device When there is no valid version, the terminal device sends a system information request to the network device or acquires the SIB according to the scheduling information.
  • An apparatus for configuring system information the apparatus is applied to network equipment, and the apparatus comprises:
  • a configuration unit that, for terminal device-specific parameters, considers the capability of the terminal device when the existence condition includes that the serving cell is configured with supplementary uplink, or, for terminal device-specific parameters and cell-specific parameters, when the existence condition includes the serving cell configuration When supplementing the uplink, the capability of the terminal device is not considered or only the network device provides the SUL configuration for the terminal device.
  • the network device determines that the terminal device can support the SUL frequency band provided in the SUL configuration; or,
  • the network device provides the terminal device with a SUL configuration, and based on the capabilities of the terminal device, the network device determines that the terminal device can support the SUL frequency band indicated in the SUL configuration;
  • supplementaryUplink supplementary Uplink
  • servingCellConfigCommon common cell configuration
  • the terminal-specific parameters are tpc-Index and/or tpc-IndexSUL.
  • the terminal-specific parameters are OR information or IE or domain.
  • SUL configuration including:
  • the configuration of the supplementary uplink for sending the system information message is optionally provided in the scheduling information.
  • the first configuration information is a serving cell common configuration (servingCellConfigCommon).
  • the configuration unit when there is a supplementary uplink (supplementaryUplink) in the serving cell common configuration (servingCellConfigCommon) and when the system information broadcast state of any system information message (SI-message) in the scheduling information (SchedulingInfo) is set to not broadcast, in the
  • the scheduling information optionally provides the configuration for sending the system information message on the supplementary uplink.
  • supplementaryUplink When there is a supplementary uplink (supplementaryUplink) in the serving cell common configuration (servingCellConfigCommon) and when the system information broadcast status (si-BroadcastStatus) of any system information message (SI-message) in the scheduling information (SchedulingInfo) is set to not broadcast, the The configuration used for sending the system information message on the supplementary uplink is optional; otherwise, the configuration used for sending the system information message on the supplementary uplink is vacant.
  • the scheduling information is included in SIB1.
  • a network device comprising the apparatus according to any one of appendices 1-10.
  • a communication system comprising the network device according to appendix 11.
  • a method for configuring system information comprising:
  • the network device considers the capability of the terminal device, or,
  • the network equipment does not consider the capabilities of the terminal equipment or the network equipment only considers that the network equipment provides SUL configuration for the terminal equipment .
  • the network device determines that the terminal device can support the SUL frequency band provided in the SUL configuration; or,
  • the network device provides the terminal device with a SUL configuration, and based on the capabilities of the terminal device, the network device determines that the terminal device can support the SUL frequency band indicated in the SUL configuration.
  • supplementaryUplink supplementary Uplink
  • servingCellConfigCommon common cell configuration
  • the terminal-specific parameters are tpc-Index and/or tpc-IndexSUL.
  • the terminal-specific parameters are OR information or IE or domain.
  • the configuration (si-RequestConfigSUL) for sending the system information message on the supplementary uplink is optionally provided in the scheduling information.
  • the first configuration information is a serving cell common configuration (servingCellConfigCommon).
  • supplementaryUplink supplementaryUplink
  • servingCellConfigCommon serving cell common configuration
  • SI-message system information message
  • schedulingInfo scheduling information
  • supplementaryUplink When there is a supplementary uplink (supplementaryUplink) in the serving cell common configuration (servingCellConfigCommon) and when the system information broadcast status (si-BroadcastStatus) of any system information message (SI-message) in the scheduling information (SchedulingInfo) is set to not broadcast, the The configuration used for sending the system information message on the supplementary uplink is optional; otherwise, the configuration used for sending the system information message on the supplementary uplink is vacant.
  • the scheduling information is included in SIB1.

Landscapes

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

Abstract

一种系统信息的配置方法、获取方法及装置。该配置方法包括：基于系统信息区域标识和区域范围的关联性生成调度信息；以及发送该调度信息。

Description

系统信息的配置方法、获取方法及装置 技术领域
本申请涉及通信领域。
背景技术
在新无线(NR，New Radio)中，在建立通信之前，终端设备需要应用系统信息获取过程以获取接入层(AS)和非接入层(NAS)信息。该系统信息获取过程适用于空闲态、非连接态和连接态的终端设备。
图1是NR中的系统信息获取过程的一示意图。如图1所示，该过程包括：终端设备获取主信息块(MIB，MasterInformationBlock)；该终端设备还可以获取系统信息块1(SIB1，SystemInformationBlockType1)；另外，如果需要，该终端设备还可以向该网络设备发送系统信息请求(SystemInformationRequest)，以请求该网络设备广播系统信息消息(SystemInformation messages)，并获取该系统信息消息。
应该注意，上面对技术背景的介绍只是为了方便，对本申请的技术方案进行清楚、完整的说明，并方便本领域技术人员的理解而阐述的。不能仅仅因为这些方案在本申请的背景技术部分进行了阐述而认为上述技术方案为本领域技术人员所公知。
发明内容
在NR中，存储的系统信息块被引入。使用该方法，终端设备可以存储获取的SIB。除了MIB、SIB1、SIB6(SystemInformationBlockType6)、SIB7(SystemInformationBlockType7)或者SIB8(SystemInformationBlockType8)，对于其他需要的SIB，例如在小区重选后或者从覆盖范围外返回时或收到系统信息(SI)修改指示后，终端设备可以使用存储的系统信息的有效版本。
当小区选择时(例如开机时)、小区重选时、从无覆盖返回、同步重配完成后、从另一个RAT进入网络后、收到系统信息改变的指示时、收到PWS通知时或者从上层收到请求时(例如收到定位请求时)，终端设备将会应用系统信息获取过程，首先获取MIB和SIB1并存储获取的MIB和SIB1。对于需要的SIB，终端设备可以检查是否存储了有效版本的SIB，如果存储了有效版本的SIB，则可以使用存储的版本； 一旦终端没有存储有效版本的SIB，该终端设备获取该SIB。此外，终端设备可以存储获取的SIB，并存储该SIB的关联信息，包括区域范围(areaScope)、公共陆地移动网标识(PLMN-Identity)、系统信息区域标识(systemInformationAreaID)和小区标识(cellIdentity)。
对于需要的SIB，终端设备可以检查是否存储了有效版本。
例如，对于该SIB的一个存储版本，如果该SIB的该存储版本关联了“区域范围(areaScope)”，那么，如果该终端设备不具有NPN(非公众网络，non-publicnetworks)能力或服务小区不是仅NPN(NPN-only)小区，当系统调度信息(si-SchedulingInfo，又称为调度信息)中的系统信息区域标识以及该SIB关联的值标签(valueTag)、其他信息中的公共陆地移动网标识(PLMN-Identity)与该存储版本关联的系统信息区域标识、值标签以及公共陆地移动网标识相同时，该终端设备认为该存储版本有效，否则认为无效，如果该终端设备具有NPN能力且服务小区是仅NPN(NPN-only)小区，当系统调度信息中的系统信息区域标识以及该SIB关联的值标签(valueTag)、其他信息中的NPN标识(NPN-Identity)与该存储版本关联的系统信息区域标识、值标签以及NPN标识相同时，该终端设备认为该存储版本有效，否则认为无效；
如果该SIB的该存储版本没有关联“区域范围(areaScope)”，那么，如果该终端设备不具有NPN能力或服务小区不是仅NPN小区，当系统调度信息中的该SIB关联的值标签、其他信息中的公共陆地移动网标识以及小区标识与该存储版本关联的值标签、公共陆地移动网标识以及小区标识相同时，该终端设备认为该存储版本有效，否则认为无效，如果该终端设备具有NPN能力且服务小区是仅NPN小区，当系统调度信息中的该SIB关联的值标签、其他信息中的NPN标识以及小区标识与该存储版本关联的值标签、NPN标识以及小区标识相同时，该终端设备认为该存储版本有效，否则认为无效。
发明人发现，基于当前的机制，如果服务小区的系统调度信息(si-SchedulingInfo)里为一个SIB配置了“areaScope”，则终端设备检查该系统调度信息里的系统信息区域标识以及其他信息，确定存储版本的有效性。
但是，系统信息区域标识是可选信息，也就是说，在一些场景里，网络侧可能不会提供该信息。在这种情况下，对于一个关联了“areaScope”的SIB，终端设备的行为是不确定的，例如，终端设备可能无法判断该SIB的存储版本是否有效，或者，终 端设备可能认为该SIB的所有存储的版本都是无效的或者认为多个存储版本都是有效的。这将会造成终端设备的测试错误，增加测试成本；也可能造成终端设备的耗电增加。
为了解决上述问题中的一个或多个，本申请实施例提供了一种系统信息的配置方法、获取方法及装置。网络设备基于系统信息区域标识和区域范围的关联性生成调度信息，能够避免配置了区域范围但没有配置系统信息区域标识的情况，或者，终端设备在检查一个SIB的存储版本的有效性时，规定了配置或没有配置系统信息区域标识的情况下终端设备的行为。因此，能够避免终端设备行为的不确定性，并降低测试的复杂度以及终端设备的开销。
根据本申请实施例的第一方面，提供了一种系统信息的配置装置，所述装置应用于网络设备，所述装置包括：生成单元，其基于系统信息区域标识(systemInformationAreaID)和区域范围(areaScope)的关联性生成调度信息(SchedulingInfo)；以及发送单元，其发送所述调度信息。
根据本申请实施例的第二方面，提供了一种系统信息的获取装置，所述装置应用于终端设备，所述装置包括：第一获取单元，其获得调度信息，所述调度信息是基于系统信息区域标识(systemInformationAreaID)和区域范围(areaScope)的关联性生成的。
根据本申请实施例的第三方面，提供了一种系统信息的获取装置，所述装置应用于终端设备，所述装置包括：第四确定单元，其对于一个SIB的一个存储版本，当获得的调度信息包括对应于所述SIB的区域范围(areaScope)，并且，当所述调度信息包括系统信息区域标识(systemInformationAreaID)且所述系统信息区域标识以及第一信息与所述存储版本关联的系统信息区域标识以及相应信息相同时，认为所述存储版本有效。
根据本申请实施例的第四方面，提供了一种网络设备，该网络设备包括根据本申请实施例的第一方面所述的装置。
根据本申请实施例的第五方面，提供了一种终端设备，该网络设备包括根据本申请实施例的第二方面或第三方面所述的装置。
根据本申请实施例的第六方面，提供了一种通信系统，该通信系统包括根据本申请实施例的第四方面所述的网络设备和/或根据本申请实施例的第五方面所述的终端 设备。
根据本申请实施例的第七方面，提供了一种系统信息的配置方法，所述方法应用于网络设备，所述方法包括：基于系统信息区域标识(systemInformationAreaID)和区域范围(areaScope)的关联性生成调度信息(SchedulingInfo)；以及发送所述调度信息。
根据本申请实施例的第八方面，提供了一种系统信息的获取方法，所述方法应用于终端设备，所述方法包括：获得调度信息，所述调度信息是基于系统信息区域标识(systemInformationAreaID)和区域范围(areaScope)的关联性生成的。
根据本申请实施例的第九方面，提供了一种系统信息的获取方法，所述方法应用于终端设备，所述方法包括：对于一个SIB的一个存储版本，当获得的调度信息包括对应于所述SIB的区域范围(areaScope)，并且，当所述调度信息包括系统信息区域标识(systemInformationAreaID)且所述系统信息区域标识以及第一信息与所述存储版本关联的系统信息区域标识以及相应信息相同时，所述终端设备认为所述存储版本有效。
根据本申请实施例的第十方面，提供了一种提供了一种计算机可读程序，其中当在系统信息的配置装置或网络设备中执行所述程序时，所述程序使得所述系统信息的配置装置或网络设备执行本申请实施例的第七方面所述的系统信息的配置方法。
根据本申请实施例的第十一方面，提供了一种存储有计算机可读程序的存储介质，其中所述计算机可读程序使得系统信息的配置装置或网络设备执行本申请实施例的第七方面所述的系统信息的配置方法。
根据本申请实施例的第十二方面，提供了一种计算机可读程序，其中当在系统信息的获取装置或终端设备中执行所述程序时，所述程序使得所述系统信息的获取装置或终端设备执行本申请实施例的第八方面或第九方面所述的系统信息的获取方法。
根据本申请实施例的第十三方面，提供一种存储有计算机可读程序的存储介质，其中所述计算机可读程序使得系统信息的获取装置或终端设备执行本申请实施例的第八方面或第九方面所述的系统信息的获取方法。
本申请实施例的有益效果之一在于：网络设备基于系统信息区域标识和区域范围的关联性生成调度信息，能够避免配置了区域范围但没有配置系统信息区域标识的情况，或者，终端设备在检查一个SIB的存储版本的有效性时，规定了配置或没有配置 系统信息区域标识的情况下终端设备的行为。因此，能够避免终端设备行为的不确定性，并降低测试的复杂度以及终端设备的开销。
另外，当终端设备获取了MIB和SIB1之后，如果需要，终端设备可以向网络设备发送系统信息请求消息，请求网络广播系统信息消息。
为了保证系统信息请求消息的发送，网络设备可以提供以下配置：
SIB1中只包括si-RequestConfigSUL；
SIB1中只包括si-RequestConfig；
SIB1中包括si-RequestConfigSUL和si-RequestConfig；以及
SIB1中不包括si-RequestConfigSUL和si-RequestConfig。
类似地，对于定位系统信息，网络设备可以提供一下配置：
SIB1中只包括posSI-RequestConfigSUL-r16；
SIB1中只包括posSI-RequestConfig-r16；
SIB1中包括posSI-RequestConfigSUL-r16和posSI-RequestConfigSUL-r16；以及
SIB1中不包括posSI-RequestConfigSUL-r16和posSI-RequestConfigSUL-r16。
其中，si-RequestConfig，posSI-RequestConfigSUL-r16是常规上行(Normal UL，NUL)上用于请求系统信息消息的配置，si-RequestConfigSUL，posSI-RequestConfigSUL-r16是补充上行(Supplementary Uplink，SUL)上用于请求系统信息消息的配置。
发明人还发现，根据当前的机制，如果服务小区配置了补充上行且如果调度信息(SchedulingInfo)里任意系统信息消息(SI-message)的系统信息广播状态(例如，si-BroadcastStatus，posSI-BroadcastStatus)设置为“不广播(notBroadcasting)”，补充上行上用于系统信息消息发送的配置(例如，si-RequestConfigSUL，posSI-RequestConfigSUL-r16)可选存在；否则si-RequestConfigSUL空缺。因此，为了确定是否提供si-RequestConfigSUL或posSI-RequestConfigSUL-r16，网络设备需要知道服务小区是否配置了补充上行。
根据当前的机制，当网络设备提供了SUL配置；且考虑终端设备能力(例如包括支持的频带、支持的上行信道带宽等)，终端设备能够支持SUL配置里指示的SUL频带时，终端设备认为服务小区配置了补充上行。而网络设备能够知道自己是否提供了SUL配置，但网络可能无法确定上述终端设备能力，因为驻留在该小区下的终端 设备可能尚未向网络设备指示其终端设备能力；或者，即使所有终端设备都提供了终端设备能力，对于一个SUL配置，服务小区下可能有的终端设备能够支持该配置，有的终端设备无法支持。因此网络设备无法确定服务小区是否配置了补充上行，也就无法确定SIB1是否包括si-RequestConfigSUL或posSI-RequestConfigSUL-r16。
为了解决上述问题中的一个或多个，本申请实施例还提供了一种系统信息的配置方法及装置。对于终端设备特定的参数，当存在条件包括服务小区配置了补充上行时，考虑终端设备的能力，或者，对于终端设备特定的参数和小区特定的参数，当存在条件包括服务小区配置了补充上行时，不考虑终端设备的能力或者只考虑网络设备为终端设备提供了SUL配置。这样，网络设备能够明确SIB1里的内容，避免网络设备实现的不确定性，降低了网络设备产品的测试成本，从而节约了布网成本。
根据本申请实施例的第十四方面，提供了一种系统信息的配置装置，所述装置应用于网络设备，所述装置包括：配置单元，其对于终端设备特定的参数，当存在条件包括服务小区配置了补充上行时，考虑终端设备的能力，或者，对于终端设备特定的参数和小区特定的参数，当存在条件包括服务小区配置了补充上行时，不考虑终端设备的能力或者只考虑网络设备为终端设备提供了SUL配置。
根据本申请实施例的第十五方面，提供了一种网络设备，该网络设备包括根据本申请实施例的第十四方面所述的装置。
根据本申请实施例的第十六方面，提供了一种通信系统，该通信系统包括根据本申请实施例的第十四方面所述的网络设备。
根据本申请实施例的第十七方面，提供了一种系统信息的配置方法，所述方法应用于网络设备，所述方法包括：
对于终端设备特定的参数，当存在条件包括服务小区配置了补充上行时，所述网络设备考虑终端设备的能力，或者，对于终端设备特定的参数和小区特定的参数，当存在条件包括服务小区配置了补充上行时，所述网络设备不考虑终端设备的能力或者所述网络设备只考虑网络设备为终端设备提供了SUL配置。
根据本申请实施例的第十八方面，提供了一种提供了一种计算机可读程序，其中当在系统信息的配置装置或网络设备中执行所述程序时，所述程序使得所述系统信息的配置装置或网络设备执行本申请实施例的第十七方面所述的系统信息的配置方法。
根据本申请实施例的第十九方面，提供了一种存储有计算机可读程序的存储介 质，其中所述计算机可读程序使得系统信息的配置装置或网络设备执行本申请实施例的第十七方面所述的系统信息的配置方法。
本申请实施例的有益效果之一还在于：对于终端设备特定的参数，当存在条件包括服务小区配置了补充上行时，考虑终端设备的能力，或者，对于终端设备特定的参数和小区特定的参数，当存在条件包括服务小区配置了补充上行时，不考虑终端设备的能力或者只考虑网络设备为终端设备提供了SUL配置。这样，网络设备能够明确SIB1里的内容，避免网络设备实现的不确定性，降低了网络设备产品的测试成本，从而节约了布网成本。
参照后文的说明和附图，详细公开了本申请的特定实施方式，指明了本申请的原理可以被采用的方式。应该理解，本申请的实施方式在范围上并不因而受到限制。在所附权利要求的精神和条款的范围内，本申请的实施方式包括许多改变、修改和等同。
针对一种实施方式描述和/或示出的特征可以以相同或类似的方式在一个或更多个其它实施方式中使用，与其它实施方式中的特征相组合，或替代其它实施方式中的特征。
应该强调，术语“包括/包含/具有”在本文使用时指特征、整件、步骤或组件的存在，但并不排除一个或更多个其它特征、整件、步骤或组件的存在或附加。
附图说明
在本申请实施例的一个附图或一种实施方式中描述的元素和特征可以与一个或更多个其它附图或实施方式中示出的元素和特征相结合。此外，在附图中，类似的标号表示几个附图中对应的部件，并可用于指示多于一种实施方式中使用的对应部件。
所包括的附图用来提供对本申请实施例的进一步的理解，其构成了说明书的一部分，用于例示本申请的实施方式，并与文字描述一起来阐释本申请的原理。显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其它的附图。在附图中：
图1是NR中的系统信息获取过程的一示意图；
图2是本申请实施例的通信系统的一示意图；
图3是本申请实施例1的系统信息的配置方法的一示意图；
图4是本申请实施例1的生成调度信息的方法的一示意图；
图5是本申请实施例1的生成调度信息的方法的另一示意图；
图6是本申请实施例1的生成调度信息的方法的另一示意图；
图7是本申请实施例2的系统信息的获取方法的一示意图；
图8是本申请实施例3的系统信息的获取方法的一示意图；
图9是本申请实施例4的系统信息的获取方法的一示意图；
图10是本申请实施例4的系统信息的获取方法的另一示意图；
图11是本申请实施例4的系统信息的获取方法的又一示意图；
图12是本申请实施例5的系统信息的配置方法的一示意图；
图13是本申请实施例6的系统信息的配置装置的一示意图；
图14是本申请实施例7的系统信息的获取装置的一示意图；
图15是本申请实施例7的第一确定单元的一示意图；
图16是本申请实施例8的系统信息的获取装置的一示意图；
图17是本申请实施例9的系统信息的获取装置的一示意图；
图18是本申请实施例10的网络设备的系统构成的一示意框图；
图19是本申请实施例11的终端设备的系统构成的一示意框图；
图20是本申请实施例12的终端设备的系统构成的一示意框图；
图21是本申请实施例13的网络设备的系统构成的一示意框图。
具体实施方式
参照附图，通过下面的说明书，本申请的前述以及其它特征将变得明显。在说明书和附图中，具体公开了本申请的特定实施方式，其表明了其中可以采用本申请的原则的部分实施方式，应了解的是，本申请不限于所描述的实施方式，相反，本申请包括落入所附权利要求的范围内的全部修改、变型以及等同物。
在本申请实施例中，术语“第一”、“第二”等用于对不同元素从称谓上进行区分，但并不表示这些元素的空间排列或时间顺序等，这些元素不应被这些术语所限制。术语“和/或”包括相关联列出的术语的一种或多个中的任何一个和所有组合。术语“包含”、“包括”、“具有”等是指所陈述的特征、元素、元件或组件的存在，但并不排除存在或添加一个或多个其他特征、元素、元件或组件。
在本申请实施例中，单数形式“一”、“该”等包括复数形式，应广义地理解为 “一种”或“一类”而并不是限定为“一个”的含义；此外术语“所述”应理解为既包括单数形式也包括复数形式，除非上下文另外明确指出。此外术语“根据”应理解为“至少部分根据……”，术语“基于”应理解为“至少部分基于……”，除非上下文另外明确指出。
在本申请实施例中，术语“通信网络”或“无线通信网络”可以指符合如下任意通信标准的网络，例如长期演进(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所示，通信系统100可以包括：网络设备101和终端设备102。为简单起见，图1仅以一个终端设备为例进行说明。网络设备101例如为NR的网络设备gNB。
在本申请实施例中，网络设备101和终端设备102之间可以进行现有的业务或者未来可实施的业务。例如，这些业务包括但不限于：增强的移动宽带(eMBB，enhanced Mobile Broadband)、大规模机器类型通信(mMTC，massive Machine Type Communication)和高可靠低时延通信(URLLC，Ultra-Reliable and Low-Latency Communication)，等等。
基于当前的机制，终端设备102为了验证是否存在一个系统信息块的有效存储版本，对于一个SIB的一个存储版本，如果该SIB的该存储版本关联了“区域范围(areaScope)”且其值与服务小区的系统调度信息(si-SchedulingInfo)里收到的该SIB的“areaScope”值相同，则终端设备102检查该系统调度信息里的系统信息区域标识以及其他信息与该SIB的该存储版本关联的相应信息是否一致；如果该SIB的该存储版本不存在“areaScope”且服务小区的系统调度信息里不包括该SIB的“areaScope”值，则终端设备102检查小区标识以及其他信息与该SIB的该存储版本关联的相应信息是否一致。
但是，系统信息区域标识是可选信息，也就是说，在一些场景里，网络设备101 可能不会提供该信息。例如，终端设备102进行小区重选后，发现系统调度信息里不包括系统信息区域标识；或者，终端设备102从覆盖范围外返回时，发现系统调度信息里不包括系统信息区域标识；或者，网络设备101发送了SI修改指示后，更新了系统调度信息，该系统调度信息不包括系统信息区域标识。
在这些情况下，对于一个关联了“areaScope”的SIB，可能存在以下问题：
终端设备102无法判断该SIB的存储版本是否有效，从而导致终端设备102行为的不确定，造成终端设备102的测试错误；或者，
终端设备102可能认为该SIB的所有存储的版本都是无效的，从而需要终端设备102重新获取该SIB；而在该SIB不变的情况下重新获取该SIB，会造成不必要的终端设备的耗电，这对于需要节能的终端设备来说是不可取的；或者，
在除了系统信息区域标识之外的其他信息一致的情况下，终端设备102可能认为关联的存储版本是有效的，这可能造成多个存储版本有效，从而终端设备102无法确定使用哪个版本或使用一个无效的存储版本。
例如，对于除了SIB1、SIB6，SIB7或者SIB8之外的一个系统信息块SIBx，终端设备102有一个存储版本1，其关联了“areaScope”，相应的存储信息还有公共陆地移动网标识1、系统信息区域标识1和小区标识1；终端设备102还有一个存储版本2，其关联了“areaScope”，相应的存储信息还有公共陆地移动网标识1、系统信息区域标识2和小区标识2。如果在服务小区的调度信息里收到了该SIBx的“areaScope”，但该调度信息不包括系统信息区域标识，按照当前的机制，终端设备102可能因为无法比较系统信息区域标识，而认为存在错误；或者，终端设备102认为存储版本1和存储版本2都不是有效的，从而需要重新获取该SIBx；或者，终端设备102认为存储版本1和存储版本2都是有效的，那么无法确定使用哪个版本，或选择了存储版本1(或存储版本2)，但实际上该版本是无效的。
下面结合附图对本申请实施例的各种实施方式进行说明。这些实施方式只是示例性的，不是对本申请的限制。
实施例1
本申请实施例提供了一种系统信息的配置方法，该方法应用于网络设备。例如，该方法应用于图2中的网络设备101。
图3是本申请实施例1的系统信息的配置方法的一示意图。如图3所示，该方法 包括：
步骤301：基于系统信息区域标识(systemInformationAreaID)和区域范围(areaScope)的关联性生成调度信息(SchedulingInfo)；以及
步骤302：发送该调度信息。
这样，网络设备基于系统信息区域标识和区域范围的关联性生成调度信息，能够避免配置了区域范围但没有配置系统信息区域标识的情况，因此，能够避免终端设备行为的不确定性，并降低测试的复杂度以及终端设备的开销。
在步骤301中，网络设备基于系统信息区域标识和区域范围的关联性生成调度信息，在本申请实施例中，该调度信息又可以称为系统调度信息(si-SchedulingInfo)。
例如，该调度信息包括在SIB1中。
在本申请实施例中，当调度信息中包括系统信息区域标识时，该系统信息区域标识对于所有小区特定的SIB都适用，也就是说，各个配置了区域范围的SIB关联相同的系统信息区域标识。
在本申请实施例中，当调度信息中包括区域范围时，该区域范围对应于一个SIB，也就是说，该调度信息可以包括一个或多个对应于一个SIB的区域范围。
当调度信息中包括对应于一个SIB的区域范围时，表示该SIB支持区域特定，也就是说，该SIB在该区域的多个小区中均有效，当调度信息中不包括对应于一个SIB的区域范围时，表示该SIB不支持区域特定，也就是说，该SIB只在提供该SIB的小区内有效。
在本申请实施例中，基于系统信息区域标识和区域范围的关联性生成调度信息，例如，该调度信息中可以同时包括系统信息区域标识和区域范围，或者，该调度信息中可以同时不包括系统信息区域标识和区域范围，或者，该调度信息中可以包括系统信息区域标识，但不包括区域范围。
以下，对如何基于系统信息区域标识和区域范围的关联性生成调度信息进行示例性的说明。
图4是本申请实施例1的生成调度信息的方法的一示意图。如图4所示，该方法包括：
步骤401：当该调度信息包括该系统信息区域标识时，该网络设备在该调度信息内为一个或多个SIB配置该区域范围或者可选的在该调度信息内为一个或多个SIB 配置该区域范围；以及
步骤402：当该调度信息不包括该系统信息区域标识时，该网络设备不在该调度信息内配置该区域范围。
也就是说，如果该调度信息包括该系统信息区域标识，那么，该网络设备在该调度信息内为一个或多个SIB配置该区域范围或者可选的在该调度信息内为一个或多个SIB配置该区域范围，否则，不配置该区域范围。
在步骤401中，该网络设备在该调度信息内为一个或多个SIB配置该区域范围是指在该调度信息内强制的为一个或多个SIB配置该区域范围。
在本申请实施例中，该SIB可以是SIB2、SIB3、SIB4以及SIB5中的至少一个，另外，该SIB还可以是SIB9、SIB10、SIB11、SIB12、SIB13以及SIB14中的至少一个。
在本申请实施例中，相应的，该调度信息中的该区域范围域的必要性编码条件为：当该调度信息包括该系统信息区域标识时，该区域范围域强制的存在；当该调度信息不包括该系统信息区域标识时，该区域范围域不存在。也就是说，如果该调度信息包括该系统信息区域标识，那么，该区域范围域强制的存在；否则该区域范围域不存在。
或者，该调度信息中的该区域范围域的必要性编码条件为：当该调度信息包括该系统信息区域标识时，该区域范围域可选的存在；当该调度信息不包括该系统信息区域标识时，该区域范围域不存在。也就是说，如果该调度信息包括该系统信息区域标识，那么，该区域范围域可选的存在；否则该区域范围域不存在。
也就是说，该区域范围域(areaScope域)是基于该系统信息区域标识域(systemInformationAreaID域)的、有条件的存在，即，条件SI-Area-ID可以用如下的表1或表2进行定义。
表1
Figure PCTCN2020107581-appb-000001
表2
Figure PCTCN2020107581-appb-000002
在本申请实施例中，条件SI-Area-ID只是一个示例性的名称，也可以使用其他名称表示，例如，条件SIAreaID或条件SI_AID等。
这样，只有在配置了系统信息区域标识的情况下，网络才会为一个或多个SIB配置区域范围，支持区域特定的SIB。这样，终端设备检查一个SIB的存储版本的有效性时，对于配置了区域范围的SIB，必然能够检查调度信息中的系统信息区域标识是否与该存储版本关联的系统信息区域标识一致。此外，该方法允许在配置了系统信息区域标识的情况下，网络设备可选地配置区域范围，保证了网络配置的灵活性。
另外，在该方法中，在没有配置系统信息区域标识的情况下，网络不会配置区域范围，不支持区域特定的SIB。这样节约了信令开销，节省频谱资源。
图5是本申请实施例1的生成调度信息的方法的另一示意图。如图5所示，该方法包括：
步骤501：当该调度信息包括一个或多个为一个SIB配置的区域范围时，该网络设备将该系统信息区域标识配置在该调度信息内；以及
步骤502：当该调度信息不包括一个或多个为一个SIB配置的区域范围时，该网络设备将该系统信息区域标识可选的配置在该调度信息内。
也就是说，如果该调度信息包括一个或多个为一个SIB配置的区域范围，那么，该网络设备将该系统信息区域标识配置在该调度信息内，否则，该网络设备将该系统信息区域标识可选的配置在该调度信息内。
在本申请实施例中，该SIB可以是SIB2、SIB3、SIB4以及SIB5中的至少一个，另外，该SIB还可以是SIB9、SIB10、SIB11、SIB12、SIB13以及SIB14中的至少一个。
在本申请实施例中，相应的，该调度信息中的系统信息区域标识域的必要性编码条件为：当该调度信息包括一个或多个为一个SIB配置的区域范围时，该系统信息区域标识域强制存在；以及当该调度信息不包括一个或多个为一个SIB配置的区域范围 时，该系统信息区域标识域可选的存在。也就是说，如果该调度信息包括一个或多个为一个SIB配置的区域范围，那么，该系统信息区域标识域强制存在；否则，该系统信息区域标识域可选的存在。
也就是说，该系统信息区域标识域(systemInformationAreaID域)是基于该区域范围域(areaScope域)的、有条件的存在，即，条件AreaScope可以用如下的表3进行定义。
表3
Figure PCTCN2020107581-appb-000003
在本申请实施例中，条件AreaScope只是一个示例性的名称，也可以使用其他名称表示，例如，条件Area-Scope或条件Area_Scope等。
这样，在为一个或多个SIB配置了区域范围、即支持区域特定的SIB的情况下，网络设备一定配置系统信息区域标识，以确定该服务小区所在的系统信息的区域。这样，终端设备检查一个SIB的存储版本的有效性时，对于配置了区域范围的SIB，必然能检查调度信息中的系统信息区域标识是否与存储版本关联的系统信息区域标识一致。
另外，在该方法中，在没有配置区域范围、即不支持区域特定的SIB的情况下，网络可选地配置系统信息区域标识，这样保证了网络配置的灵活性。
图6是本申请实施例1的生成调度信息的方法的另一示意图。如图6所示，该方法包括：
步骤601：当该调度信息包括一个或多个为一个SIB配置的区域范围时，该网络设备将该系统信息区域标识配置在该调度信息内；以及
步骤602：当该调度信息不包括一个或多个为一个SIB配置的区域范围时，该网络设备不将该系统信息区域标识配置在该调度信息内。
也就是说，如果该调度信息包括一个或多个为一个SIB配置的区域范围，那么，该网络设备将该系统信息区域标识配置在该调度信息内，否则，该网络设备不将该系 统信息区域标识配置在该调度信息内。
在本申请实施例中，该SIB可以是SIB2、SIB3、SIB4以及SIB5中的至少一个，另外，该SIB还可以是SIB9、SIB10、SIB11、SIB12、SIB13以及SIB14中的至少一个。
在本申请实施例中，相应的，该调度信息中的系统信息区域标识域的必要性编码条件为：当该调度信息包括一个或多个为一个SIB配置的区域范围时，该系统信息区域标识域强制存在；以及当该调度信息不包括一个或多个为一个SIB配置的区域范围时，该系统信息区域标识域不存在。也就是说，如果该调度信息包括一个或多个为一个SIB配置的区域范围，那么，该系统信息区域标识域强制存在；否则，该系统信息区域标识域不存在。
也就是说，该系统信息区域标识域(systemInformationAreaID域)是基于该区域范围域(areaScope域)的、有条件的存在，即，条件AreaScope可以用如下的表4进行定义。
表4
Figure PCTCN2020107581-appb-000004
在本申请实施例中，条件AreaScope只是一个示例性的名称，也可以使用其他名称表示，例如，条件Area-Scope或条件Area_Scope等。
这样，在为一个或多个SIB配置了区域范围、即支持区域特定的SIB的情况下，网络设备一定配置系统信息区域标识，以确定该服务小区所在的系统信息的区域。这样，终端设备检查一个SIB的存储版本的有效性时，对于配置了区域范围的SIB，必然能检查调度信息中的系统信息区域标识是否与存储版本关联的系统信息区域标识一致。
另外，在这个实施例里，在没有配置区域范围、即不支持区域特定的SIB的情况下，网络设备不会配置系统信息区域标识，这样节约了信令开销，节省频谱资源。
在通过步骤301生成该调度信息后，在步骤302中，网络设备可以通过广播的形式发送生成的该调度信息。
例如，该调度信息包括在SIB1里，参见图1，网络设备以广播的形式发送SIB1。
由上述实施例可知，网络设备基于系统信息区域标识和区域范围的关联性生成调度信息，能够避免配置了区域范围但没有配置系统信息区域标识的情况，因此，能够避免终端设备行为的不确定性，并降低测试的复杂度以及终端设备的开销。
实施例2
本申请实施例提供了一种系统信息的获取方法，该方法应用于终端设备，其对应于实施例1所述的应用于网络设备的系统信息的配置方法，相同的内容不再重复说明。例如，该方法应用于图2中的终端设备102。
图7是本申请实施例2的系统信息的获取方法的一示意图。如图7所示，该方法包括：
步骤701：获得调度信息，该调度信息是基于系统信息区域标识(systemInformationAreaID)和区域范围(areaScope)的关联性生成的。
在本申请实施例中，该调度信息的生成方法可以参见实施例1中的记载，此处不再赘述。
在本申请实施例中，该调度信息可以包括在SIB1里，例如，该SIB1是网络设备以广播的形式发送的。
在本申请实施例中，如图7所示，该方法还可以包括：
步骤702：对于一个SIB，根据该调度信息和服务小区广播的系统信息中的其他信息确定是否存储了该SIB的有效版本。
在本申请实施例中，该其他信息可以包括在SIB1里。
在本申请实施例中，该SIB可以是SIB2、SIB3、SIB4以及SIB5中的至少一个，另外，该SIB还可以是SIB9、SIB10、SIB11、SIB12、SIB13以及SIB14中的至少一个。
在步骤702中，对于该SIB的一个存储版本，当该调度信息中的系统信息区域标识以及该SIB关联的值标签(valueTag)以及该其他信息中的公共陆地移动网标识(PLMN-Identity)与该存储版本关联的系统信息区域标识、值标签以及公共陆地移动网标识相同时，该终端设备认为该存储版本有效。
或者，对于该SIB的一个存储版本，当该调度信息中的该SIB关联的值标签(valueTag)以及该其他信息中的公共陆地移动网标识(PLMN-Identity)、小区标识与该存储版本关联的值标签、公共陆地移动网标识以及小区标识(cellIdentity)相同 时，该终端设备认为该存储版本有效。
例如，如果该终端设备不具有NPN能力或服务小区不是仅NPN(NPN-only)小区，那么，当该调度信息中的系统信息区域标识以及该SIB关联的值标签(valueTag)、该其他信息中的公共陆地移动网标识(PLMN-Identity)与该存储版本关联的系统信息区域标识、值标签以及公共陆地移动网标识相同时，该终端设备认为该存储版本有效。
或者，例如，如果该终端设备不具有NPN能力或服务小区不是仅NPN(NPN-only)小区，那么，当该调度信息中的该SIB关联的值标签(valueTag)以及该其他信息中的公共陆地移动网标识(PLMN-Identity)、小区标识与该存储版本关联的值标签、公共陆地移动网标识以及小区标识相同时，该终端设备认为该存储版本有效。
在步骤702中，也可以是，对于该SIB的一个存储版本，当该调度信息中的系统信息区域标识以及该SIB关联的值标签以及该其他信息中的NPN标识(NPN-Identity)与该存储版本关联的系统信息区域标识、值标签以及NPN标识相同时，该终端设备认为该存储版本有效。
或者，对于该SIB的一个存储版本，当该调度信息中的该SIB关联的值标签以及该其他信息中的NPN标识(NPN-Identity)、小区标识与该存储版本关联的值标签、NPN标识以及小区标识相同时，该终端设备认为该存储版本有效。
例如，如果该终端设备具有NPN能力且服务小区是仅NPN(NPN-only)小区，那么，当该调度信息中的系统信息区域标识以及该SIB关联的值标签、该其他信息中的NPN标识(NPN-Identity)与该存储版本关联的系统信息区域标识、值标签以及NPN标识相同时，该终端设备认为该存储版本有效。
或者，例如，如果该终端设备具有NPN能力且服务小区是仅NPN(NPN-only)小区，那么，当该调度信息中的该SIB关联的值标签以及该其他信息中的NPN标识(NPN-Identity)、小区标识与该存储版本关联的值标签、NPN标识以及小区标识相同时，该终端设备认为该存储版本有效。
在本申请实施例中，如图7所示，该方法还可以包括：
步骤703：当存在有效版本时，该终端设备使用该SIB的该有效版本；以及
步骤704：当不存在有效版本时，该终端设备向该网络设备发送系统信息请求或根据该调度信息获取该SIB。
由上述实施例可知，终端设备获取网络设备基于系统信息区域标识和区域范围的关联性生成的调度信息，能够避免配置了区域范围但没有配置系统信息区域标识的情况，因此，能够避免终端设备行为的不确定性，并降低测试的复杂度以及终端设备的开销。
实施例3
本申请实施例提供了一种系统信息的获取方法，该方法应用于网络设备和终端设备，其对应于实施例1所述的应用于网络设备的系统信息的配置方法和实施例2所述的应用于终端设备的系统信息的配置方法，相同的内容不再重复说明。
图8是本申请实施例3的系统信息的获取方法的一示意图。如图8所示，该方法包括：
步骤801：网络设备基于系统信息区域标识和区域范围的关联性生成调度信息；
步骤802：该网络设备发送该调度信息，终端设备获得该调度信息；
步骤803：该终端设备根据该调度信息和服务小区广播的系统信息中的其他信息确定是否存储了该SIB的有效版本；
步骤804：当存在有效版本时，该终端设备使用该SIB的该有效版本；以及
步骤805：当不存在有效版本时，该终端设备向该网络设备发送系统信息请求或根据该调度信息获取该SIB。
在本申请实施例中，在步骤805中，该终端设备向该网络设备发送系统信息请求是可选的，例如，如果该网络设备已经广播了包括该SIB的调度信息，则该终端设备不需要再发送系统信息请求，可以直接根据该调度信息获取该SIB。
在本申请实施例中，图8中各个步骤的具体实施可以参照实施例1和实施例2的记载，此处不再重复说明。
由上述实施例可知，网络设备基于系统信息区域标识和区域范围的关联性生成调度信息，能够避免配置了区域范围但没有配置系统信息区域标识的情况，因此，能够避免终端设备行为的不确定性，并降低测试的复杂度以及终端设备的开销。
实施例4
本申请实施例提供了一种系统信息的获取方法，该方法应用于终端设备。例如，该方法应用于图2中的终端设备102。
图9是本申请实施例4的系统信息的获取方法的一示意图。如图9所示，该方法 包括：
步骤901：对于一个SIB的一个存储版本，当获得的调度信息包括对应于该SIB的区域范围，并且，当该调度信息包括系统信息区域标识且该系统信息区域标识以及第一信息与该存储版本关联的系统信息区域标识以及相应信息相同时，该终端设备认为该存储版本有效。
在本申请实施例中，该SIB可以是SIB2、SIB3、SIB4以及SIB5中的至少一个，另外，该SIB还可以是SIB9、SIB10、SIB11、SIB12、SIB13以及SIB14中的至少一个。
在本申请实施例中，如果该SIB有多个存储版本，那么，对于各个存储版本逐个进行检查其有效性。
在本申请实施例中，该第一信息可以包括：从服务小区收到的包括在PLMN标识信息列表(PLMN-IdentityInfoList)中的第一个PLMN标识(PLMN-Identity)以及包括在该调度信息中的该SIB关联的值标签(valueTag)；该相应信息包括：与该SIB的该存储版本关联的PLMN标识(PLMN-Identity)以及值标签。
例如，当该终端设备不具有NPN能力或服务小区不是仅NPN(NPN-only)小区时，该第一信息包括：从服务小区收到的包括在PLMN标识信息列表(PLMN-IdentityInfoList)中的第一个PLMN标识(PLMN-Identity)以及包括在该调度信息中的该SIB关联的值标签(valueTag)；该相应信息包括：与该SIB的该存储版本关联的PLMN标识(PLMN-Identity)以及值标签。
在本申请实施例中，或者，该第一信息可以包括：从服务小区收到的包括NPN标识信息列表(NPN-IdentityInfoList)中的第一个NPN标识以及包括在该调度信息中的该SIB关联的值标签(valueTag)；该相应信息包括：与该SIB的该存储版本关联的NPN标识以及值标签。
例如，当该终端设备具有NPN能力且服务小区是仅NPN(NPN-only)小区时，该第一信息包括：从服务小区收到的包括NPN标识信息列表(NPN-IdentityInfoList)中的第一个NPN标识以及包括在该调度信息中的该SIB关联的值标签(valueTag)；该相应信息包括：与该SIB的该存储版本关联的NPN标识以及值标签。
在本申请实施例中，如图9所示，该方法还可以包括：
步骤902：对于一个SIB的该存储版本，当获得的调度信息包括对应于该SIB的 区域范围，并且，当该调度信息不包括系统信息区域标识时，该终端设备认为该存储版本无效。
也就是说，对于一个SIB的一个存储版本，如果获得的调度信息包括对应于该SIB的区域范围，并且，该调度信息包括系统信息区域标识且该系统信息区域标识以及第一信息与该存储版本关联的系统信息区域标识以及相应信息相同，那么，该终端设备认为该存储版本有效，否则，该终端设备认为该存储版本无效。
例如，对于Rel-15，对于一个SIB的各个存储版本，
如果该区域范围是关联的，并且对于该SIB的该存储版本，该区域范围的值与来自服务小区的关于该SIB的系统调度信息中接收的值相同，
如果包括在PLMN标识信息列表中的第一个PLMN标识、系统信息区域标识(如果存在)以及从服务小区接收的系统调度信息中包括的该SIB的值标签与该SIB的该存储版本关联的PLMN标识、系统信息区域标识以及值标签一致，
那么，认为该存储的SIB对于该小区是有效的。
又例如，对于Rel-15，对于一个SIB的各个存储版本，
如果该区域范围是关联的，并且对于该SIB的该存储版本，该区域范围的值与从服务小区为该SIB的系统调度信息中接收的值相同，并且如果该系统调度信息中包括了系统信息区域标识，
如果包括在PLMN标识信息列表中的第一个PLMN标识、系统信息区域标识以及从服务小区接收的系统调度信息中包括的该SIB的值标签与该SIB的该存储版本关联的PLMN标识、系统信息区域标识以及值标签一致，
那么，认为该存储的SIB对于该小区是有效的。
在该方法中，在配置了系统信息区域标识的情况下，Rel-15中的终端设备通过检查系统信息区域标识确定一个SIB的存储版本的有效性，避免终端设备的行为的不确定性，降低测试的复杂度、并降低设备的开销。
另外，在该方法中，在没有配置系统信息区域标识的情况下，终端设备认为该存储版本无效，对当前终端设备的行为和标准影响小，可以降低实现成本。
例如，对于Rel-16，对于一个SIB的各个存储版本，
如果该区域范围是关联的，并且对于该SIB的该存储版本，该区域范围的值与从服务小区为该SIB的系统调度信息中接收的值相同，
如果该终端设备具有NPN能力且该小区是仅NPN小区，并且，包括在NPN标识列表里的第一个NPN标识、系统信息区域标识(如果存在)以及从服务小区接收的系统调度信息中包括的该SIB的值标签与该SIB的该存储版本关联的NPN标识、系统信息区域标识以及值标签一致，
那么，认为该存储的SIB对于该小区是有效的；
否则，如果包括在PLMN标识信息列表中的第一个PLMN标识、系统信息区域标识(如果存在)以及从服务小区接收的系统调度信息中包括的该SIB的值标签与该SIB的该存储版本关联的PLMN标识、系统信息区域标识以及值标签一致，
那么，认为该存储的SIB对于该小区是有效的。
又例如，对于Rel-16，对于一个SIB的各个存储版本，
如果该区域范围是关联的，并且对于该SIB的该存储版本，该区域范围的值与从服务小区为该SIB的系统调度信息中接收的值相同，并且如果该系统调度信息中包括了系统信息区域标识，
如果该终端设备具有NPN能力且该小区是仅NPN小区，并且，包括在NPN标识列表里的第一个NPN标识、系统信息区域标识以及从服务小区接收的系统调度信息中包括的该SIB的值标签与该SIB的该存储版本关联的NPN标识、系统信息区域标识以及值标签一致，
那么，认为该存储的SIB对于该小区是有效的；
否则，如果包括在PLMN标识信息列表中的第一个PLMN标识、系统信息区域标识以及从服务小区接收的系统调度信息中包括的该SIB的值标签与该SIB的该存储版本关联的PLMN标识、系统信息区域标识以及值标签一致，
那么，认为该存储的SIB对于该小区是有效的。
在该方法中，在配置了系统信息区域标识的情况下，Rel-16中的终端设备通过检查系统信息区域标识确定一个SIB的存储版本的有效性，避免终端设备的行为的不确定性，降低测试的复杂度、并降低设备的开销。该方法考虑了Rel-16中的终端设备具备支持非公共网络(NPN)的能力，这样终端设备可以检查NPN标识，而不是PLMN标识，以确定一个SIB的一个存储版本的有效性，从而避免了在网络设备不广播PLMN标识的情况下，终端设备的行为的不确定性。
另外，在该方法中，在没有配置系统信息区域标识的情况下，终端设备认为该存 储版本无效，对当前终端设备的行为和标准影响小，可以降低实现成本。
在本申请实施例中，如图9所示，该方法还可以包括：
步骤903：当该终端设备认为该存储版本有效时，使用该有效版本的该SIB；以及
步骤904：当不存在有效版本时，该终端设备向该网络设备发送系统信息请求或根据该调度信息获取该SIB。
图10是本申请实施例4的系统信息的获取方法的另一示意图。如图10所示，该方法包括：
步骤1001：对于一个SIB的一个存储版本，当获得的调度信息包括对应于该SIB的区域范围，并且，当该调度信息包括系统信息区域标识且该系统信息区域标识以及第一信息与该存储版本关联的系统信息区域标识以及相应信息相同时，该终端设备认为该存储版本有效；以及
步骤1002：对于一个SIB的该存储版本，当获得的调度信息包括对应于该SIB的区域范围，并且，当该调度信息不包括系统信息区域标识而第一信息与该存储版本关联的相应信息相同时，该终端设备认为该存储版本有效。
也就是说，对于一个SIB的一个存储版本，如果获得的调度信息包括对应于该SIB的区域范围，并且，如果该调度信息包括系统信息区域标识且该系统信息区域标识以及第一信息与该存储版本关联的系统信息区域标识以及相应信息相同，那么，该终端设备认为该存储版本有效；如果该调度信息不包括系统信息区域标识而第一信息与该存储版本关联的相应信息相同，该终端设备也认为该存储版本有效。
例如，对于Rel-15，对于一个SIB的各个存储版本，
如果该区域范围是关联的，并且对于该SIB的该存储版本，该区域范围的值与来自服务小区的关于该SIB的系统调度信息中接收的值相同，
如果包括在PLMN标识信息列表中的第一个PLMN标识、系统信息区域标识(如果存在)以及从服务小区接收的系统调度信息中包括的该SIB的值标签与该SIB的该存储版本关联的PLMN标识、系统信息区域标识以及值标签一致，
那么，认为该存储的SIB对于该小区是有效的；
如果该区域范围是关联的，并且对于该SIB的该存储版本，该区域范围的值与来自服务小区的关于该SIB的系统调度信息中接收的值相同，并且，并且如果该系统调 度信息中不包括系统信息区域标识，
如果包括在PLMN标识信息列表中的第一个PLMN标识以及从服务小区接收的系统调度信息中包括的该SIB的值标签与该SIB的该存储版本关联的PLMN标识以及值标签一致，
那么，认为该存储的SIB对于该小区是有效的；
如果对于该SIB的该存储版本，该区域范围不存在，并且，该区域范围的值不包括在来自服务小区的关于该SIB的该系统调度信息中，
如果包括在PLMN标识信息列表中的第一个PLMN标识、小区标识以及从服务小区为该SIB接收的系统调度信息中包括的值标签与该SIB的该存储版本关联的PLMN标识、小区标识以及值标签一致，
那么，认为该存储的SIB对于该小区是有效的。
又例如，对于Rel-15，对于一个SIB的各个存储版本，
如果该区域范围是关联的，并且对于该SIB的该存储版本，该区域范围的值与来自服务小区的关于该SIB的系统调度信息中接收的值相同，并且如果该系统调度信息中包括了系统信息区域标识，
如果包括在PLMN标识信息列表中的第一个PLMN标识、系统信息区域标识以及从服务小区接收的系统调度信息中包括的该SIB的值标签与该SIB的该存储版本关联的PLMN标识、系统信息区域标识以及值标签一致，
那么，认为该存储的SIB对于该小区是有效的；
如果该区域范围是关联的，并且对于该SIB的该存储版本，该区域范围的值与来自服务小区的关于该SIB的系统调度信息中接收的值相同，并且，并且如果该系统调度信息中不包括系统信息区域标识，
如果包括在PLMN标识信息列表中的第一个PLMN标识以及从服务小区接收的系统调度信息中包括的该SIB的值标签与该SIB的该存储版本关联的PLMN标识以及值标签一致，
那么，认为该存储的SIB对于该小区是有效的；
如果对于该SIB的该存储版本，该区域范围不存在，并且，该区域范围的值不包括在来自服务小区的关于该SIB的该系统调度信息中，
如果包括在PLMN标识信息列表中的第一个PLMN标识、小区标识以及从服 务小区为该SIB接收的系统调度信息中包括的值标签与该SIB的该存储版本关联的PLMN标识、小区标识以及值标签一致，
那么，认为该存储的SIB对于该小区是有效的。
例如，对于Rel-16，对于一个SIB的各个存储版本，
如果该区域范围是关联的，并且对于该SIB的该存储版本，该区域范围的值与从服务小区为该SIB的系统调度信息中接收的值相同，
如果该终端设备具有NPN能力且该小区是仅NPN小区，并且，包括在NPN标识列表里的第一个NPN标识、系统信息区域标识(如果存在)以及从服务小区接收的系统调度信息中包括的该SIB的值标签与该SIB的该存储版本关联的NPN标识、系统信息区域标识以及值标签一致，
那么，认为该存储的SIB对于该小区是有效的；
否则，如果包括在PLMN标识信息列表中的第一个PLMN标识、系统信息区域标识(如果存在)以及从服务小区接收的系统调度信息中包括的该SIB的值标签与该SIB的该存储版本关联的PLMN标识、系统信息区域标识以及值标签一致，
那么，认为该存储的SIB对于该小区是有效的；
如果该区域范围是关联的，并且对于该SIB的该存储版本，该区域范围的值与来自服务小区的关于该SIB的系统调度信息中接收的值相同，并且如果该系统调度信息中不包括系统信息区域标识，
如果该终端设备具有NPN能力且该小区是仅NPN小区，并且，包括在NPN标识列表里的第一个NPN标识以及从服务小区接收的系统调度信息中包括的该SIB的值标签与该SIB的该存储版本关联的NPN标识以及值标签一致，
那么，认为该存储的SIB对于该小区是有效的；
如果对于该SIB的该存储版本，该区域范围不存在，并且，该区域范围的值不包括在来自服务小区的关于该SIB的该系统调度信息中，
如果该终端设备具有NPN能力且该小区是仅NPN小区，并且，包括在NPN标识列表里的第一个NPN标识、小区标识以及从服务小区接收的系统调度信息中包括的该SIB的值标签与该SIB的该存储版本关联的NPN标识、小区标识以及值标签一致，
那么，认为该存储的SIB对于该小区是有效的。
又例如，对于Rel-16，对于一个SIB的各个存储版本，
如果该区域范围是关联的，并且对于该SIB的该存储版本，该区域范围的值与从服务小区为该SIB的系统调度信息中接收的值相同，并且如果该系统调度信息中包括了系统信息区域标识，
如果该终端设备具有NPN能力且该小区是仅NPN小区，并且，包括在NPN标识列表里的第一个NPN标识、系统信息区域标识以及从服务小区接收的系统调度信息中包括的该SIB的值标签与该SIB的该存储版本关联的NPN标识、系统信息区域标识以及值标签一致，
那么，认为该存储的SIB对于该小区是有效的；
否则，如果包括在PLMN标识信息列表中的第一个PLMN标识、系统信息区域标识以及从服务小区接收的系统调度信息中包括的该SIB的值标签与该SIB的该存储版本关联的PLMN标识、系统信息区域标识以及值标签一致，
那么，认为该存储的SIB对于该小区是有效的；
如果该区域范围是关联的，并且对于该SIB的该存储版本，该区域范围的值与来自服务小区的关于该SIB的系统调度信息中接收的值相同，并且如果该系统调度信息中不包括系统信息区域标识，
如果该终端设备具有NPN能力且该小区是仅NPN小区，并且，包括在NPN标识列表里的第一个NPN标识以及从服务小区接收的系统调度信息中包括的该SIB的值标签与该SIB的该存储版本关联的NPN标识以及值标签一致，
那么，认为该存储的SIB对于该小区是有效的；
如果对于该SIB的该存储版本，该区域范围不存在，并且，该区域范围的值不包括在来自服务小区的关于该SIB的该系统调度信息中，
如果该终端设备具有NPN能力且该小区是仅NPN小区，并且，包括在NPN标识列表里的第一个NPN标识、小区标识以及从服务小区接收的系统调度信息中包括的该SIB的值标签与该SIB的该存储版本关联的NPN标识、小区标识以及值标签一致，
那么，认为该存储的SIB对于该小区是有效的。
在本申请实施例中，如图10所示，该方法还可以包括：
步骤1003：当该终端设备认为该存储版本有效时，使用该有效版本的该SIB；以 及
步骤1004：当不存在有效版本时，该终端设备向该网络设备发送系统信息请求或根据该调度信息获取该SIB。
图11是本申请实施例4的系统信息的获取方法的又一示意图。如图11所示，该方法包括：
步骤1101：对于一个SIB的一个存储版本，当获得的调度信息包括对应于该SIB的区域范围，并且，当该调度信息包括系统信息区域标识且该系统信息区域标识以及第一信息与该存储版本关联的系统信息区域标识以及相应信息相同时，该终端设备认为该存储版本有效；以及
步骤1102：对于一个SIB的该存储版本，当获得的调度信息包括对应于该SIB的区域范围，并且，当该调度信息不包括系统信息区域标识而第一信息以及小区标识与该存储版本关联的相应信息以及小区标识相同时，该终端设备认为该存储版本有效。
也就是说，对于一个SIB的一个存储版本，如果获得的调度信息包括对应于该SIB的区域范围，并且，如果该调度信息包括系统信息区域标识且该系统信息区域标识以及第一信息与该存储版本关联的系统信息区域标识以及相应信息相同，那么，该终端设备认为该存储版本有效；如果该调度信息不包括系统信息区域标识而第一信息以及小区标识与该存储版本关联的相应信息以及小区标识相同时，该终端设备也认为该存储版本有效。
例如，对于Rel-15，对于一个SIB的各个存储版本，
如果该区域范围是关联的，并且对于该SIB的该存储版本，该区域范围的值与来自服务小区的关于该SIB的系统调度信息中接收的值相同，
如果包括在PLMN标识信息列表中的第一个PLMN标识、系统信息区域标识(如果存在)以及从服务小区接收的系统调度信息中包括的该SIB的值标签与该SIB的该存储版本关联的PLMN标识、系统信息区域标识以及值标签一致，
那么，认为该存储的SIB对于该小区是有效的；
如果该区域范围是关联的，并且对于该SIB的该存储版本，该区域范围的值与来自服务小区的关于该SIB的系统调度信息中接收的值相同，并且，并且如果该系统调度信息中不包括系统信息区域标识，或者，
如果对于该SIB的该存储版本，该区域范围不存在，并且，该区域范围的值不包括在来自服务小区的关于该SIB的该系统调度信息中，
如果包括在PLMN标识信息列表中的第一个PLMN标识、小区标识以及从服务小区接收的系统调度信息中包括的该SIB的值标签与该SIB的该存储版本关联的PLMN标识、小区标识以及值标签一致，
那么，认为该存储的SIB对于该小区是有效的。
又例如，对于Rel-15，对于一个SIB的各个存储版本，
如果该区域范围是关联的，并且对于该SIB的该存储版本，该区域范围的值与来自服务小区的关于该SIB的系统调度信息中接收的值相同，并且如果该系统调度信息中包括了系统信息区域标识，
如果包括在PLMN标识信息列表中的第一个PLMN标识、系统信息区域标识以及从服务小区接收的系统调度信息中包括的该SIB的值标签与该SIB的该存储版本关联的PLMN标识、系统信息区域标识以及值标签一致，
那么，认为该存储的SIB对于该小区是有效的；
如果该区域范围是关联的，并且对于该SIB的该存储版本，该区域范围的值与来自服务小区的关于该SIB的系统调度信息中接收的值相同，并且，并且如果该系统调度信息中不包括系统信息区域标识，或者，
如果对于该SIB的该存储版本，该区域范围不存在，并且，该区域范围的值不包括在来自服务小区的关于该SIB的该系统调度信息中，
如果包括在PLMN标识信息列表中的第一个PLMN标识、小区标识以及从服务小区接收的系统调度信息中包括的该SIB的值标签与该SIB的该存储版本关联的PLMN标识、小区标识以及值标签一致，
那么，认为该存储的SIB对于该小区是有效的。
在该方法中，在配置了系统信息区域标识的情况下，Rel-15中的终端设备通过检查系统信息区域标识确定一个SIB的存储版本的有效性，避免终端设备的行为的不确定性，降低测试的复杂度、并降低设备的开销。
另外，在该方法中，在没有配置系统信息区域标识的情况下，终端设备需要检查小区标识确定存储版本的有效性。这样，在小区标识一致，即在SIB不变的情况下，终端设备不必重新获取SIB，降低了终端耗电。
例如，对于Rel-16，对于一个SIB的各个存储版本，
如果该区域范围是关联的，并且对于该SIB的该存储版本，该区域范围的值与从服务小区为该SIB的系统调度信息中接收的值相同，
如果该终端设备具有NPN能力且该小区是仅NPN小区，并且，包括在NPN标识列表里的第一个NPN标识、系统信息区域标识(如果存在)以及从服务小区接收的系统调度信息中包括的该SIB的值标签与该SIB的该存储版本关联的NPN标识、系统信息区域标识以及值标签一致，
那么，认为该存储的SIB对于该小区是有效的；
否则，如果包括在PLMN标识信息列表中的第一个PLMN标识、系统信息区域标识(如果存在)以及从服务小区接收的系统调度信息中包括的该SIB的值标签与该SIB的该存储版本关联的PLMN标识、系统信息区域标识以及值标签一致，
那么，认为该存储的SIB对于该小区是有效的；
如果该区域范围是关联的，并且对于该SIB的该存储版本，该区域范围的值与来自服务小区的关于该SIB的系统调度信息中接收的值相同，并且，并且如果该系统调度信息中不包括系统信息区域标识，或者，
如果对于该SIB的该存储版本，该区域范围不存在，并且，该区域范围的值不包括在来自服务小区的关于该SIB的该系统调度信息中，
如果该终端设备具有NPN能力且该小区是仅NPN小区，并且，包括在NPN标识信息列表中的第一个NPN标识、小区标识以及从服务小区为该SIB接收的系统调度信息中包括的值标签与该SIB的该存储版本关联的NPN标识、小区标识以及值标签一致，
那么，认为该存储的SIB对于该小区是有效的。
又例如，对于Rel-16，对于一个SIB的各个存储版本，
如果该区域范围是关联的，并且对于该SIB的该存储版本，该区域范围的值与从服务小区为该SIB的系统调度信息中接收的值相同，并且如果该系统调度信息中包括了系统信息区域标识，
如果该终端设备具有NPN能力且该小区是仅NPN小区，并且，包括在NPN标识列表里的第一个NPN标识、系统信息区域标识以及从服务小区接收的系统调度信息中包括的该SIB的值标签与该SIB的该存储版本关联的NPN标识、系统信息区 域标识以及值标签一致，
那么，认为该存储的SIB对于该小区是有效的；
否则，如果包括在PLMN标识信息列表中的第一个PLMN标识、系统信息区域标识以及从服务小区接收的系统调度信息中包括的该SIB的值标签与该SIB的该存储版本关联的PLMN标识、系统信息区域标识以及值标签一致，
那么，认为该存储的SIB对于该小区是有效的；
如果该区域范围是关联的，并且对于该SIB的该存储版本，该区域范围的值与来自服务小区的关于该SIB的系统调度信息中接收的值相同，并且，并且如果该系统调度信息中不包括系统信息区域标识，或者，
如果对于该SIB的该存储版本，该区域范围不存在，并且，该区域范围的值不包括在来自服务小区的关于该SIB的该系统调度信息中，
如果该终端设备具有NPN能力且该小区是仅NPN小区，并且，包括在NPN标识信息列表中的第一个NPN标识、从服务小区为该SIB接收的系统调度信息中包括的小区标识以及值标签与该SIB的该存储版本关联的NPN标识、小区标识以及值标签一致，
那么，认为该存储的SIB对于该小区是有效的。
在该方法中，在配置了系统信息区域标识的情况下，Rel-16中的终端设备通过检查系统信息区域标识确定一个SIB的存储版本的有效性，避免终端设备的行为的不确定性，降低测试的复杂度、并降低设备的开销。该方法考虑了Rel-16中的终端设备可能具备支持非公共网络(NPN)的能力，这样终端设备可以检查NPN标识，而不是PLMN标识，以确定一个SIB的一个存储版本的有效性，从而避免了网络设备不广播PLMN标识情况下的终端设备的行为的不确定性。
另外，在该方法中，在没有配置系统信息区域标识的情况下，终端设备需要检查小区标识确定存储版本的有效性。这样，在小区标识一致，即在SIB不变的情况下，终端不必重新获取SIB，降低了终端设备的耗电。
在本申请实施例中，如图11所示，该方法还可以包括：
步骤1103：当该终端设备认为该存储版本有效时，使用该有效版本的该SIB；以及
步骤1104：当不存在有效版本时，该终端设备向该网络设备发送系统信息请求 或根据该调度信息获取该SIB。
由上述实施例可知，终端设备在检查一个SIB的存储版本的有效性时，规定了配置或没有配置系统信息区域标识的情况下终端设备的行为。因此，能够避免终端设备行为的不确定性，并降低测试的复杂度以及终端设备的开销。
实施例5
本申请实施例提供了一种系统信息的配置方法，该方法应用于网络设备。例如，该方法应用于图2中的网络设备101。
图12是本申请实施例5的系统信息的配置方法的一示意图。如图12所示，该方法包括：
步骤1201：对于终端设备特定的参数，当存在条件包括服务小区配置了补充上行时，该网络设备考虑终端设备的能力，或者，对于终端设备特定的参数和小区特定的参数，当存在条件包括服务小区配置了补充上行时，该网络设备不考虑终端设备的能力或者该网络设备只考虑网络设备为终端设备提供了SUL配置。
在本申请实施例中，例如，该网络设备考虑终端设备的能力，包括：
基于该终端设备的能力，该网络设备确定该终端设备能够支持SUL配置里提供的SUL频带；或者，
该网络设备为该终端设备提供了SUL配置，且基于该终端设备的能力，该网络设备确定该终端设备能够支持SUL配置里指示的SUL频带。
在本申请实施例中，例如，该网络设备考虑终端设备的能力，包括：
公共小区配置(servingCellConfigCommon)里存在补充上行(supplementaryUplink)表示该网络设备为该终端设备提供了SUL配置。
在本申请实施例中，例如，该终端设备特定的参数是tpc-Index和/或tpc-IndexSUL。
在本申请实施例中，例如，该对于终端设备特定的参数是或信息或IE或域。
例如，该对于终端设备特定的参数还可以是一个终端设备特定的信息或终端设备特定的IE或终端设备特定的域。
在步骤1201中，例如，所述当存在条件包括服务小区配置了补充上行时，不考虑终端设备的能力或者只考虑网络设备为终端设备提供了SUL配置，包括：当小区公共的第一配置信息里包括补充上行配置时，在调度信息中可选的提供补充上行上用 于系统信息消息发送的配置(si-RequestConfigSUL)。
也就是说，如果小区公共的第一配置信息里包括补充上行配置，那么，在调度信息中可选的提供补充上行上用于系统信息消息发送的配置。
在本申请实施例中，该第一配置信息可以是服务小区公共配置(servingCellConfigCommon))。
在步骤1201中，例如，当服务小区公共配置(servingCellConfigCommon)里存在补充上行(supplementaryUplink)且当调度信息(SchedulingInfo)里任意系统信息消息(SI-message)的系统信息广播状态(例如si-BroadcastStatus，posSI-BroadcastStatus)设置为不广播时，在该调度信息中可选的提供该补充上行上用于系统信息消息发送的配置(例如si-RequestConfigSUL，posSI-RequestConfigSUL-r16)。
也就是说，如果公共小区配置(servingCellConfigCommon)里存在补充上行(supplementaryUplink)且如果调度信息(SchedulingInfo)里任意系统信息消息(SI-message)的系统信息广播状态(例如si-BroadcastStatus，posSI-BroadcastStatus)设置为“不广播(notBroadcasting)”，补充上行上用于系统信息消息发送的配置(例如si-RequestConfigSUL，posSI-RequestConfigSUL-r16)可选存在；否则si-RequestConfigSUL或posSI-RequestConfigSUL-r16空缺。
在本申请实施例中，该补充上行上用于系统信息消息发送的配置的存在条件为：当服务小区公共配置(servingCellConfigCommon)里存在补充上行(supplementaryUplink)且当调度信息(SchedulingInfo)里任意系统信息消息(SI-message)的系统信息广播状态(例如si-BroadcastStatus，posSI-BroadcastStatus)设置为不广播时，该补充上行上用于系统信息消息发送的配置可选的存在，否则，该补充上行上用于系统信息消息发送的配置空缺。
例如，si-RequestConfigSUL存在条件SUL-MSG-1可以用如下的表5进行定义。
表5
Figure PCTCN2020107581-appb-000005
在本申请实施例中，条件SUL-MSG-1只是一个示例性的名称，也可以使用其他名称来表示，例如条件SUL-MSG1，条件SUL-SI-Request等。
又例如，posSI-RequestConfigSUL-r16存在条件SUL-MSG-1可以用如下的表6进行定义。
表6
Figure PCTCN2020107581-appb-000006
又例如，tpc-Index存在条件SUL可以用如下的表7进行定义。
表7
Figure PCTCN2020107581-appb-000007
又例如，tpc-Index存在条件SUL可以用如下的表8进行定义。
表8
Figure PCTCN2020107581-appb-000008
在本申请实施例中，上述各个条件使用的名称只是一个示例性的名称，也可以使用其他名称来表示，本申请实施例不对这些名称的形式和格式进行限制。在本申请实施例中，该调度信息又称为系统调度信息，该调度信息可以包括在SIB1里。
由上述实施例可知，对于终端设备特定的参数，当存在条件包括服务小区配置了补充上行时，考虑终端设备的能力，或者，对于终端设备特定的参数和小区特定的参数，当存在条件包括服务小区配置了补充上行时，不考虑终端设备的能力或者只考虑网络设备为终端设备提供了SUL配置。这样，网络设备能够明确SIB1里的内容，避免网络设备实现的不确定性，降低了网络设备产品的测试成本，从而节约了布网成本。
实施例6
本申请实施例提供了一种系统信息的配置装置，该装置应用于网络设备。由于该装置解决问题的原理与实施例1的方法类似，因此其具体的实施可以参照实施例1所述的方法的实施，内容相同或相关之处不再重复说明。
图13是本申请实施例6的系统信息的配置装置的一示意图，如图13所示，装置1300包括：
生成单元1301，其基于系统信息区域标识(systemInformationAreaID)和区域范围(areaScope)的关联性生成调度信息(SchedulingInfo)；以及
发送单元1302，其发送该调度信息。
在本申请实施例中，生成单元1301当该调度信息包括该系统信息区域标识时，强制的或可选的在该调度信息内为一个或多个SIB配置该区域范围；当该调度信息不包括该系统信息区域标识时，不在该调度信息内配置该区域范围。
在本申请实施例中，该调度信息中的该区域范围域的必要性编码条件为：当该调度信息包括该系统信息区域标识时，该区域范围域强制存在；当该调度信息不包括该系统信息区域标识时，该区域范围域不存在，或者，当该调度信息包括该系统信息区域标识时，该区域范围域可选的存在；当该调度信息不包括该系统信息区域标识时， 该区域范围域不存在。
在本申请实施例中，也可以是，生成单元1301当该调度信息包括一个或多个为一个SIB配置的区域范围时将该系统信息区域标识配置在该调度信息内；当该调度信息不包括一个或多个为一个SIB配置的区域范围时，将该系统信息区域标识可选的配置在该调度信息内，或者，不将该系统信息区域标识配置在该调度信息内。
在本申请实施例中，该调度信息中的系统信息区域标识域的必要性编码条件为：当该调度信息包括一个或多个为一个SIB配置的区域范围时，该系统信息区域标识域强制存在；以及当该调度信息不包括一个或多个为一个SIB配置的区域范围时，该系统信息区域标识域可选的存在。
或者，该调度信息中的系统信息区域标识域的必要性编码条件为：当该调度信息包括一个或多个为一个SIB配置的区域范围时，该系统信息区域标识域强制存在；以及当该调度信息不包括一个或多个为一个SIB配置的区域范围时，该系统信息区域标识域不存在。
在本申请实施例中，该调度信息可以包括该系统信息区域标识和该区域范围。
在本申请实施例中，该调度信息可以通过广播的形式发送。
在本申请实施例中，该调度信息可以包括在SIB1里。
在本实施例中，上述各个单元的功能的实现可以参照实施例1中相关步骤的内容，此处不再重复说明。
由上述实施例可知，网络设备基于系统信息区域标识和区域范围的关联性生成调度信息，能够避免配置了区域范围但没有配置系统信息区域标识的情况，因此，能够避免终端设备行为的不确定性，并降低测试的复杂度以及终端设备的开销。
实施例7
本申请实施例提供了一种系统信息的获取装置，该装置应用于终端设备。由于该装置解决问题的原理与实施例2的方法类似，因此其具体的实施可以参照实施例2所述的方法的实施，内容相同或相关之处不再重复说明。
图14是本申请实施例7的系统信息的获取装置的一示意图，如图14所示，装置1400包括：
第一获取单元1401，其获得调度信息，该调度信息是基于系统信息区域标识(systemInformationAreaID)和区域范围(areaScope)的关联性生成的。
在本申请实施例中，如图14所示，装置1400还包括：
第一确定单元1402，其对于一个SIB，根据该调度信息和服务小区广播的系统信息中的其他信息确定是否存储了该SIB的有效版本。
图15是本申请实施例7的第一确定单元的一示意图，如图15所示，第一确定单元1402包括：
第二确定单元1501，其对于该SIB的一个存储版本，当该调度信息中的系统信息区域标识以及该SIB关联的值标签(valueTag)以及该其他信息中的公共陆地移动网标识(PLMN-Identity)与该存储版本关联的系统信息区域标识、值标签以及公共陆地移动网标识相同时，该终端设备认为该存储版本有效，或者，对于该SIB的一个存储版本，当该调度信息中的该SIB关联的值标签(valueTag)以及该其他信息中的公共陆地移动网标识(PLMN-Identity)、小区标识与该存储版本关联的值标签、公共陆地移动网标识以及小区标识(cellIdentity)以及小区标识相同时，认为该存储版本有效；或者，
第三确定单元1502，其对于该SIB的一个存储版本，当该调度信息中的系统信息区域标识以及该SIB关联的值标签、该其他信息中的NPN标识(NPN-Identity)以及小区标识与该存储版本关联的系统信息区域标识、值标签、NPN标识以及小区标识相同时，该终端设备认为该存储版本有效，或者，对于该SIB的一个存储版本，当该调度信息中的该SIB关联的值标签以及该其他信息中的NPN标识(NPN-Identity)、小区标识与该存储版本关联的值标签、NPN标识以及小区标识相同时，该终端设备认为该存储版本有效。
在本申请实施例中，如图14所示，装置1400还包括：
第一使用单元1403，其当存在有效版本时，使用该SIB的该有效版本；以及
第二获取单元1404，其当不存在有效版本时，向该网络设备发送系统信息请求或根据该调度信息获取该SIB。
在本申请实施例中，该调度信息可以包括该系统信息区域标识和该区域范围。
在本申请实施例中，该SIB可以是SIB2、SIB3、SIB4以及SIB5中的至少一个，另外，该SIB还可以是SIB9、SIB10、SIB11、SIB12、SIB13以及SIB14中的至少一个。
在本申请实施例中，该调度信息可以包括在SIB1里。
在本实施例中，上述各个单元的功能的实现可以参照实施例2中相关步骤的内容，此处不再重复说明。
由上述实施例可知，终端设备获取网络设备基于系统信息区域标识和区域范围的关联性生成的调度信息，能够避免配置了区域范围但没有配置系统信息区域标识的情况，因此，能够避免终端设备行为的不确定性，并降低测试的复杂度以及终端设备的开销。
实施例8
本申请实施例提供了一种系统信息的获取装置，该装置应用于终端设备。由于该装置解决问题的原理与实施例4的方法类似，因此其具体的实施可以参照实施例4所述的方法的实施，内容相同或相关之处不再重复说明。
图16是本申请实施例8的系统信息的获取装置的一示意图，如图16所示，装置1600包括：
第四确定单元1601，其对于一个SIB的一个存储版本，当获得的调度信息包括对应于该SIB的区域范围(areaScope)，并且，当该调度信息包括系统信息区域标识(systemInformationAreaID)且该系统信息区域标识以及第一信息与该存储版本关联的系统信息区域标识以及相应信息相同时，认为该存储版本有效。
在本申请实施例中，如图16所示，装置1600还可以包括：
第五确定单元1602，其对于一个SIB的该存储版本，当获得的调度信息包括对应于该SIB的区域范围，并且，当该调度信息不包括系统信息区域标识时，认为该存储版本无效。
在本申请实施例中，如图16所示，装置1600还可以包括：
第六确定单元1603，其对于一个SIB的该存储版本，当获得的调度信息包括对应于该SIB的区域范围，并且，当该调度信息不包括系统信息区域标识而第一信息与该存储版本关联的相应信息相同时，认为该存储版本有效。
在本申请实施例中，如图16所示，装置1600还可以包括：
第七确定单元1604，其对于一个SIB的该存储版本，当获得的调度信息包括对应于该SIB的区域范围(areaScope)，并且，当该调度信息不包括系统信息区域标识而第一信息以及小区标识(cellIdentity)与该存储版本关联的相应信息以及小区标识相同时，认为该存储版本有效。
在本申请实施例中，该第一信息可以包括：从服务小区收到的包括在PLMN标识信息列表(PLMN-IdentityInfoList)中的第一个PLMN标识(PLMN-Identity)以及包括在该调度信息中的该SIB关联的值标签(valueTag)；
该相应信息可以包括：与该SIB的该存储版本关联的PLMN标识(PLMN-Identity)以及值标签。
例如，当该终端设备不具有NPN能力或服务小区不是仅NPN(NPN-only)小区时，该第一信息包括：从服务小区收到的包括在PLMN标识信息列表(PLMN-IdentityInfoList)中的第一个PLMN标识(PLMN-Identity)以及包括在该调度信息中的该SIB关联的值标签(valueTag)；该相应信息包括：与该SIB的该存储版本关联的PLMN标识(PLMN-Identity)以及值标签。
在本申请实施例中，或者，该第一信息可以包括：从服务小区收到的包括NPN标识信息列表(NPN-IdentityInfoList)中的第一个NPN标识以及包括在该调度信息中的该SIB关联的值标签(valueTag)；该相应信息包括：与该SIB的该存储版本关联的NPN标识以及值标签。
例如，当该终端设备具有NPN能力且服务小区是仅NPN(NPN-only)小区时，该第一信息包括：从服务小区收到的包括NPN标识信息列表(NPN-IdentityInfoList)中的第一个NPN标识以及包括在该调度信息中的该SIB关联的值标签(valueTag)；该相应信息包括：与该SIB的该存储版本关联的NPN标识以及值标签。
在本申请实施例中，如图16所示，装置1600还可以包括：
第二使用单元1605，其当该终端设备认为该存储版本有效时，使用该有效版本的该SIB；以及
第三获取单元1606，其当不存在有效版本时，该终端设备向该网络设备发送系统信息请求或根据该调度信息获取该SIB。
在本实施例中，上述各个单元的功能的实现可以参照实施例4中相关步骤的内容，此处不再重复说明。
由上述实施例可知，终端设备获取网络设备基于系统信息区域标识和区域范围的关联性生成的调度信息，能够避免配置了区域范围但没有配置系统信息区域标识的情况，因此，能够避免终端设备行为的不确定性，并降低测试的复杂度以及终端设备的开销。
实施例9
本申请实施例提供了一种系统信息的配置装置，该装置应用于网络设备。由于该装置解决问题的原理与实施例5的方法类似，因此其具体的实施可以参照实施例5所述的方法的实施，内容相同或相关之处不再重复说明。
图17是本申请实施例9的系统信息的获取装置的一示意图，如图17所示，装置1700包括：
配置单元1701，其对于终端设备特定的参数，当存在条件包括服务小区配置了补充上行时，考虑终端设备的能力，或者，对于终端设备特定的参数和小区特定的参数，当存在条件包括服务小区配置了补充上行时，不考虑终端设备的能力或者只考虑网络设备为终端设备提供了SUL配置。
在本申请实施例中，该网络设备考虑终端设备的能力，包括：
基于该终端设备的能力，该网络设备确定该终端设备能够支持SUL配置里提供的SUL频带；或者，
该网络设备为该终端设备提供了SUL配置，且基于该终端设备的能力，该网络设备确定该终端设备能够支持SUL配置里指示的SUL频带。
在本申请实施例中，该网络设备考虑终端设备的能力，包括：
公共小区配置(servingCellConfigCommon)里存在补充上行(supplementaryUplink)表示该网络设备为该终端设备提供了SUL配置。
在本申请实施例中，例如，该终端设备特定的参数是tpc-Index和/或tpc-IndexSUL。
在本申请实施例中，该对于终端设备特定的参数是或信息或IE或域。
例如，该对于终端设备特定的参数还可以是一个终端设备特定的信息或终端设备特定的IE或终端设备特定的域。
在本申请实施例中，例如，所述当存在条件包括服务小区配置了补充上行时，不考虑终端设备的能力或者只考虑网络设备为终端设备提供了SUL配置，包括：当小区公共的第一配置信息里包括补充上行配置时，在调度信息中可选的提供补充上行上用于系统信息消息发送的配置(例如si-RequestConfigSUL，posSI-RequestConfigSUL-r16)。
在本申请实施例中，该第一配置信息可以为服务小区公共配置 (servingCellConfigCommon))。
在本申请实施例中，配置单元1701当服务小区公共配置(servingCellConfigCommon)里存在补充上行(supplementaryUplink)且当调度信息(SchedulingInfo)里任意系统信息消息(SI-message)的系统信息广播状态(例如si-BroadcastStatus，posSI-BroadcastStatus)设置为不广播时，在该调度信息中可选的提供该补充上行上用于系统信息消息发送的配置(例如si-RequestConfigSUL，posSI-RequestConfigSUL-r16)。
在本申请实施例中，该补充上行上用于系统信息消息发送的配置的存在条件为：
当服务小区公共配置(servingCellConfigCommon)里存在补充上行(supplementaryUplink)且当调度信息(SchedulingInfo)里任意系统信息消息(SI-message)的系统信息广播状态(例如si-BroadcastStatus，posSI-BroadcastStatus)设置为不广播时，该补充上行上用于系统信息消息发送的配置可选的存在，否则，该补充上行上用于系统信息消息发送的配置空缺。
在本申请实施例中，该调度信息可以包括在SIB1里。
在本实施例中，上述各个单元的功能的实现可以参照实施例5中相关步骤的内容，此处不再重复说明。
由上述实施例可知，对于终端设备特定的参数，当存在条件包括服务小区配置了补充上行时，考虑终端设备的能力，或者，对于终端设备特定的参数和小区特定的参数，当存在条件包括服务小区配置了补充上行时，不考虑终端设备的能力或者只考虑网络设备为终端设备提供了SUL配置。这样，网络设备能够明确SIB1里的内容，避免网络设备实现的不确定性，降低了网络设备产品的测试成本，从而节约了布网成本。
实施例10
本申请实施例提供了一种网络设备，该网络设备包括如实施例6所述的系统信息的配置装置。
图18是本申请实施例10的网络设备的系统构成的一示意框图。如图18所示，网络设备1800可以包括：处理器(processor)1810和存储器1820；存储器1820耦合到处理器1810。其中该存储器1820可存储各种数据；此外还存储信息处理的程序1830，并且在处理器1810的控制下执行该程序1830，以接收终端设备发送的各种信息、并且向终端设备发送各种信息。
在一个实施方式中，系统信息的配置装置的功能可以被集成到处理器1810中。其中，处理器1810可以被配置为：基于系统信息区域标识(systemInformationAreaID)和区域范围(areaScope)的关联性生成调度信息(SchedulingInfo)；以及发送该调度信息。
例如，该基于系统信息区域标识和区域范围的关联性生成调度信息，包括：当该调度信息包括该系统信息区域标识时，该网络设备在该调度信息内为一个或多个SIB配置该区域范围或者可选的在该调度信息内为一个或多个SIB配置该区域范围。
例如，该基于系统信息区域标识和区域范围的关联性生成调度信息，还包括：当该调度信息不包括该系统信息区域标识时，该网络设备不在该调度信息内配置该区域范围。
例如，该调度信息中的该区域范围域的必要性编码条件为：当该调度信息包括该系统信息区域标识时，该区域范围域强制存在存在；当该调度信息不包括该系统信息区域标识时，该区域范围域不存在，或者，当该调度信息包括该系统信息区域标识时，该区域范围域可选的存在；当该调度信息不包括该系统信息区域标识时，该区域范围域不存在。
例如，该基于系统信息区域标识和区域范围的关联性生成调度信息，包括：当该调度信息包括一个或多个为一个SIB配置的区域范围时，该网络设备将该系统信息区域标识配置在该调度信息内。
例如，该基于系统信息区域标识和区域范围的关联性生成调度信息，还包括：当该调度信息不包括一个或多个为一个SIB配置的区域范围时，该网络设备将该系统信息区域标识可选的配置在该调度信息内，或者，该网络设备不将该系统信息区域标识配置在该调度信息内。
例如，该调度信息中的系统信息区域标识域的必要性编码条件为：当该调度信息包括一个或多个为一个SIB配置的区域范围时，该系统信息区域标识域强制存在；以及当该调度信息不包括一个或多个为一个SIB配置的区域范围时，该系统信息区域标识域可选的存在。
例如，该调度信息中的系统信息区域标识域的必要性编码条件为：当该调度信息包括一个或多个为一个SIB配置的区域范围时，该系统信息区域标识域强制存在；以及当该调度信息不包括一个或多个为一个SIB配置的区域范围时，该系统信息区域标 识域不存在。
例如，该调度信息包括该系统信息区域标识和该区域范围。
例如，该调度信息通过广播的形式发送。
例如，该调度信息包括在SIB1里。
在另一个实施方式中，系统信息的配置装置可以与处理器1810分开配置，例如可以将系统信息的配置装置配置为与处理器1810连接的芯片，通过处理器1810的控制来实现系统信息的配置装置的功能。
此外，如图18所示，网络设备1800还可以包括：收发机1840和天线1850等；其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，网络设备1800也并不是必须要包括图18中所示的所有部件；此外，网络设备1800还可以包括图18中没有示出的部件，可以参考现有技术。
由上述实施例可知，网络设备基于系统信息区域标识和区域范围的关联性生成调度信息，能够避免配置了区域范围但没有配置系统信息区域标识的情况，因此，能够避免终端设备行为的不确定性，并降低测试的复杂度以及终端设备的开销。
实施例11
本申请实施例提供了一种终端设备，该终端设备包括如实施例7所述的系统信息的获取装置。
图19是本申请实施例11的终端设备的系统构成的一示意框图。如图19所示，终端设备1900可以包括处理器1910和存储器1920；存储器1920耦合到处理器1910。值得注意的是，该图是示例性的；还可以使用其他类型的结构，来补充或代替该结构，以实现电信功能或其他功能。
在本申请实施例的一个实施方式中，系统信息的获取装置的功能可以被集成到处理器1910中。处理器1910可以被配置为：获得调度信息，该调度信息是基于系统信息区域标识(systemInformationAreaID)和区域范围(areaScope)的关联性生成的。
例如，处理器1910还可以被配置为：对于一个SIB，根据该调度信息和服务小区广播的系统信息中的其他信息确定是否存储了该SIB的有效版本。
例如，该根据该调度信息和服务小区广播的系统信息中的其他信息确定是否存储了该SIB的有效版本，包括：对于该SIB的一个存储版本，当该调度信息中的系统信息区域标识以及该SIB关联的值标签(valueTag)、该其他信息中的公共陆地移动网 标识(PLMN-Identity)与该存储版本关联的系统信息区域标识、值标签以及公共陆地移动网标识相同时，该终端设备认为该存储版本有效，或者，对于该SIB的一个存储版本，当该调度信息中的该SIB关联的值标签(valueTag)以及该其他信息中的公共陆地移动网标识(PLMN-Identity)、小区标识与该存储版本关联的值标签、公共陆地移动网标识以及小区标识(cellIdentity)相同时，该终端设备认为该存储版本有效；或者，对于该SIB的一个存储版本，当该调度信息中的系统信息区域标识以及该SIB关联的值标签、该其他信息中的NPN标识(NPN-Identity)与该存储版本关联的系统信息区域标识、值标签以及NPN标识相同时，该终端设备认为该存储版本有效，或者，对于该SIB的一个存储版本，当该调度信息中的该SIB关联的值标签以及该其他信息中的NPN标识(NPN-Identity)、小区标识与该存储版本关联的值标签、NPN标识以及小区标识相同时，该终端设备认为该存储版本有效。
例如，处理器1910还可以被配置为：当存在有效版本时，该终端设备使用该SIB的该有效版本；以及当不存在有效版本时，该终端设备向该网络设备发送系统信息请求或根据该调度信息获取该SIB。
例如，该调度信息包括该系统信息区域标识和该区域范围。
例如，该SIB可以是SIB2、SIB3、SIB4以及SIB5中的至少一个，另外，该SIB还可以是SIB9、SIB10、SIB11、SIB12、SIB13以及SIB14中的至少一个。
例如，该调度信息包括在SIB1里。
在另一个实施方式中，系统信息的获取装置可以与处理器1910分开配置，例如可以将系统信息的获取装置配置为与处理器1910连接的芯片，通过处理器1910的控制来实现系统信息的获取装置的功能。
如图19所示，终端设备1900还可以包括：通信模块1930、输入单元1940、显示器1950、电源1960。值得注意的是，终端设备1900也并不是必须要包括图19中所示的所有部件；此外，终端设备1900还可以包括图19中没有示出的部件，可以参考相关技术。
如图19所示，处理器1910有时也称为控制器或操作控件，可以包括微处理器或其他处理器装置和/或逻辑装置，该处理器1910接收输入并控制终端设备1900的各个部件的操作。
其中，存储器1920，例如可以是缓存器、闪存、硬驱、可移动介质、易失性存 储器、非易失性存储器或其它合适装置中的一种或更多种。可储存各种数据，此外还可存储执行有关信息的程序。并且处理器1910可执行该存储器1920存储的该程序，以实现信息存储或处理等。其他部件的功能与现有类似，此处不再赘述。终端设备1200的各部件可以通过专用硬件、固件、软件或其结合来实现，而不偏离本申请的范围。
由上述实施例可知，终端设备获取网络设备基于系统信息区域标识和区域范围的关联性生成的调度信息，能够避免配置了区域范围但没有配置系统信息区域标识的情况，因此，能够避免终端设备行为的不确定性，并降低测试的复杂度以及终端设备的开销。
实施例12
本申请实施例提供了一种终端设备，该终端设备包括如实施例8所述的系统信息的获取装置。
图20是本申请实施例12的终端设备的系统构成的一示意框图。如图20所示，终端设备2000可以包括处理器2010和存储器2020；存储器2020耦合到处理器2010。值得注意的是，该图是示例性的；还可以使用其他类型的结构，来补充或代替该结构，以实现电信功能或其他功能。
在本申请实施例的一个实施方式中，系统信息的获取装置的功能可以被集成到处理器2010中。处理器2010可以被配置为：对于一个SIB的一个存储版本，当获得的调度信息包括对应于该SIB的区域范围(areaScope)，并且，当该调度信息包括系统信息区域标识(systemInformationAreaID)且该系统信息区域标识以及第一信息与该存储版本关联的系统信息区域标识以及相应信息相同时，该终端设备认为该存储版本有效。
例如，处理器2010还可以被配置为：对于一个SIB的该存储版本，当获得的调度信息包括对应于该SIB的区域范围，并且，当该调度信息不包括系统信息区域标识时，该终端设备认为该存储版本无效。
例如，处理器2010还可以被配置为：对于一个SIB的该存储版本，当获得的调度信息包括对应于该SIB的区域范围，并且，当该调度信息不包括系统信息区域标识而第一信息与该存储版本关联的相应信息相同时，该终端设备认为该存储版本有效。
例如，处理器2010还可以被配置为：对于一个SIB的该存储版本，当获得的调 度信息包括对应于该SIB的区域范围(areaScope)，并且，当该调度信息不包括系统信息区域标识而第一信息以及小区标识(cellIdentity)与该存储版本关联的相应信息以及小区标识相同时，该终端设备认为该存储版本有效。
例如，该第一信息包括：从服务小区收到的包括在PLMN标识信息列表(PLMN-IdentityInfoList)中的第一个PLMN标识(PLMN-Identity)以及包括在该调度信息中的该SIB关联的值标签(valueTag)；该相应信息包括：与该SIB的该存储版本关联的PLMN标识(PLMN-Identity)以及值标签。
例如，当该终端设备不具有NPN能力或服务小区不是仅NPN(NPN-only)小区时，该第一信息包括：从服务小区收到的包括在PLMN标识信息列表(PLMN-IdentityInfoList)中的第一个PLMN标识(PLMN-Identity)以及包括在该调度信息中的该SIB关联的值标签(valueTag)；该相应信息包括：与该SIB的该存储版本关联的PLMN标识(PLMN-Identity)以及值标签。
例如，该第一信息包括：从服务小区收到的包括NPN标识信息列表(NPN-IdentityInfoList)中的第一个NPN标识以及包括在该调度信息中的该SIB关联的值标签(valueTag)；该相应信息包括：与该SIB的该存储版本关联的NPN标识以及值标签。
例如，当该终端设备具有NPN能力且服务小区是仅NPN(NPN-only)小区时，该第一信息包括：从服务小区收到的包括NPN标识信息列表(NPN-IdentityInfoList)中的第一个NPN标识以及包括在该调度信息中的该SIB关联的值标签(valueTag)；该相应信息包括：与该SIB的该存储版本关联的NPN标识以及值标签。
例如，处理器2010还可以被配置为：当该终端设备认为该存储版本有效时，使用该有效版本的该SIB；以及当不存在有效版本时，该终端设备向该网络设备发送系统信息请求或根据该调度信息获取该SIB。。
在另一个实施方式中，系统信息的获取装置可以与处理器2010分开配置，例如可以将系统信息的获取装置配置为与处理器2010连接的芯片，通过处理器2010的控制来实现系统信息的获取装置的功能。
如图20所示，终端设备2000还可以包括：通信模块2030、输入单元2040、显示器2050、电源2060。值得注意的是，终端设备2000也并不是必须要包括图20中所示的所有部件；此外，终端设备2000还可以包括图20中没有示出的部件，可以参 考相关技术。
如图20所示，处理器2010有时也称为控制器或操作控件，可以包括微处理器或其他处理器装置和/或逻辑装置，该处理器2010接收输入并控制终端设备2000的各个部件的操作。
其中，存储器2020，例如可以是缓存器、闪存、硬驱、可移动介质、易失性存储器、非易失性存储器或其它合适装置中的一种或更多种。可储存各种数据，此外还可存储执行有关信息的程序。并且处理器2010可执行该存储器2020存储的该程序，以实现信息存储或处理等。其他部件的功能与现有类似，此处不再赘述。终端设备2000的各部件可以通过专用硬件、固件、软件或其结合来实现，而不偏离本申请的范围。
由上述实施例可知，终端设备在检查一个SIB的存储版本的有效性时，规定了配置或没有配置系统信息区域标识的情况下终端设备的行为。因此，能够避免终端设备行为的不确定性，并降低测试的复杂度以及终端设备的开销。
实施例13
本申请实施例提供了一种网络设备，该网络设备包括如实施例9所述的系统信息的配置装置。
图21是本申请实施例13的网络设备的系统构成的一示意框图。如图21所示，网络设备2100可以包括：处理器(processor)2110和存储器2120；存储器2120耦合到处理器2110。其中该存储器2120可存储各种数据；此外还存储信息处理的程序2130，并且在处理器2110的控制下执行该程序2130，以接收终端设备发送的各种信息、并且向终端设备发送各种信息。
在一个实施方式中，系统信息的配置装置的功能可以被集成到处理器2110中。其中，处理器2110可以被配置为：对于终端设备特定的参数，当存在条件包括服务小区配置了补充上行时，该网络设备考虑终端设备的能力，或者，对于终端设备特定的参数和小区特定的参数，当存在条件包括服务小区配置了补充上行时，该网络设备不考虑终端设备的能力或者该网络设备只考虑网络设备为终端设备提供了SUL配置。
例如，该网络设备考虑终端设备的能力，包括：基于该终端设备的能力，该网络设备确定该终端设备能够支持SUL配置里提供的SUL频带；或者，该网络设备为该 终端设备提供了SUL配置，且基于该终端设备的能力，该网络设备确定该终端设备能够支持SUL配置里指示的SUL频带。
例如，网络设备考虑终端设备的能力，包括：公共小区配置(servingCellConfigCommon)里存在补充上行(supplementaryUplink)表示该网络设备为该终端设备提供了SUL配置。
例如，该终端设备特定的参数是tpc-Index和/或tpc-IndexSUL。
例如，该对于终端设备特定的参数是或信息或IE或域。
例如，该对于终端设备特定的参数还可以是一个终端设备特定的信息或终端设备特定的IE或终端设备特定的域。
例如，所述当存在条件包括服务小区配置了补充上行时，不考虑终端设备的能力或者只考虑网络设备为终端设备提供了SUL配置，包括：当小区公共的第一配置信息里包括补充上行配置时，在调度信息中可选的提供补充上行上用于系统信息消息发送的配置(例如si-RequestConfigSUL，posSI-RequestConfigSUL-r16)。
例如，该第一配置信息为服务小区公共配置(servingCellConfigCommon))。
例如，当服务小区公共配置(servingCellConfigCommon)里存在补充上行(supplementaryUplink)且当调度信息(SchedulingInfo)里任意系统信息消息(SI-message)的系统信息广播状态(例如si-BroadcastStatus，posSI-BroadcastStatus)设置为不广播时，在该调度信息中可选的提供该补充上行上用于系统信息消息发送的配置(例如si-RequestConfigSUL，posSI-RequestConfigSUL-r16)。
例如，该补充上行上用于系统信息消息发送的配置的存在条件为：当服务小区公共配置(servingCellConfigCommon)里存在补充上行(supplementaryUplink)且当调度信息(SchedulingInfo)里任意系统信息消息(SI-message)的系统信息广播状态(例如si-BroadcastStatus，posSI-BroadcastStatus)设置为不广播时，该补充上行上用于系统信息消息发送的配置可选的存在，否则，该补充上行上用于系统信息消息发送的配置空缺。
例如，该调度信息包括在SIB1里。
在另一个实施方式中，系统信息的配置装置可以与处理器2110分开配置，例如可以将系统信息的配置装置配置为与处理器2110连接的芯片，通过处理器2110的控制来实现系统信息的配置装置的功能。
此外，如图21所示，网络设备2100还可以包括：收发机2140和天线2150等；其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，网络设备2100也并不是必须要包括图21中所示的所有部件；此外，网络设备2100还可以包括图21中没有示出的部件，可以参考现有技术。
由上述实施例可知，对于终端设备特定的参数，当存在条件包括服务小区配置了补充上行时，考虑终端设备的能力，或者，对于终端设备特定的参数和小区特定的参数，当存在条件包括服务小区配置了补充上行时，不考虑终端设备的能力或者只考虑网络设备为终端设备提供了SUL配置。这样，网络设备能够明确SIB1里的内容，避免网络设备实现的不确定性，降低了网络设备产品的测试成本，从而节约了布网成本。
实施例14
本申请实施例提供了一种通信系统，包括根据实施例10所述的网络设备和/或根据实施例11所述的终端设备，或者，该通信系统包括根据实施例12所述的终端设备，或者，该通信系统包括根据实施例13所述的网络设备。
例如，该通信系统的结构可以参照图1，如图1所示，通信系统100包括网络设备101和终端设备102，网络设备101与实施例10或实施例13所述的网络设备相同，和/或，终端设备102与实施例11或实施例12所述的终端设备相同，重复的内容不再赘述。
本申请以上的装置和方法可以由硬件实现，也可以由硬件结合软件实现。本申请涉及这样的计算机可读程序，当该程序被逻辑部件所执行时，能够使该逻辑部件实现上文所述的装置或构成部件，或使该逻辑部件实现上文所述的各种方法或步骤。逻辑部件例如现场可编程逻辑部件、微处理器、计算机中使用的处理器等。本申请还涉及用于存储以上程序的存储介质，如硬盘、磁盘、光盘、DVD、flash存储器等。
结合本申请实施例描述的方法/装置可直接体现为硬件、由处理器执行的软件模块或二者组合。例如，图13中所示的功能框图中的一个或多个和/或功能框图的一个或多个组合，既可以对应于计算机程序流程的各个软件模块，亦可以对应于各个硬件模块。这些软件模块，可以分别对应于图3中所示的各个步骤。这些硬件模块例如可利用现场可编程门阵列(FPGA)将这些软件模块固化而实现。
软件模块可以位于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动磁盘、CD-ROM或者本领域已知的任何其它形式的存 储介质。可以将一种存储介质耦接至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息；或者该存储介质可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。该软件模块可以存储在移动终端的存储器中，也可以存储在可插入移动终端的存储卡中。例如，若设备(如移动终端)采用的是较大容量的MEGA-SIM卡或者大容量的闪存装置，则该软件模块可存储在该MEGA-SIM卡或者大容量的闪存装置中。
针对附图13中描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，可以实现为用于执行本申请所描述功能的通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件或者其任意适当组合。针对附图13描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，还可以实现为计算设备的组合，例如，DSP和微处理器的组合、多个微处理器、与DSP通信结合的一个或多个微处理器或者任何其它这种配置。
以上结合具体的实施方式对本申请进行了描述，但本领域技术人员应该清楚，这些描述都是示例性的，并不是对本申请保护范围的限制。本领域技术人员可以根据本申请的精神和原理对本申请做出各种变型和修改，这些变型和修改也在本申请的范围内。
根据本申请实施例公开的各种实施方式，还公开了如下附记：
附记一、
1、一种系统信息的配置装置，所述装置应用于网络设备，所述装置包括：
生成单元，其基于系统信息区域标识(systemInformationAreaID)和区域范围(areaScope)的关联性生成调度信息(SchedulingInfo)；以及
发送单元，其发送所述调度信息。
2、根据附记1所述的装置，其中，
所述生成单元当所述调度信息包括所述系统信息区域标识时，在所述调度信息内为一个或多个SIB配置所述区域范围或者可选的在所述调度信息内为一个或多个SIB配置所述区域范围。
3、根据附记2所述的装置，其中，
所述生成单元当所述调度信息不包括所述系统信息区域标识时，不在所述调度信 息内配置所述区域范围。
4、根据附记1-3中的任一项所述的装置，其中，
所述调度信息中的所述区域范围域的必要性编码条件为：
当所述调度信息包括所述系统信息区域标识时，所述区域范围域强制存在；当所述调度信息不包括所述系统信息区域标识时，所述区域范围域不存在，或者，
当所述调度信息包括所述系统信息区域标识时，所述区域范围域可选的存在；当所述调度信息不包括所述系统信息区域标识时，所述区域范围域不存在。
5、根据附记1所述的装置，其中，
所述生成单元当所述调度信息包括一个或多个为一个SIB配置的区域范围时将所述系统信息区域标识配置在所述调度信息内。
6、根据附记5所述的装置，其中，
所述生成单元当所述调度信息不包括一个或多个为一个SIB配置的区域范围时，将所述系统信息区域标识可选的配置在所述调度信息内，或者，不将所述系统信息区域标识配置在所述调度信息内。
7、根据附记1、5、6中的任一项所述的装置，其中，
所述调度信息中的系统信息区域标识域的必要性编码条件为：
当所述调度信息包括一个或多个为一个SIB配置的区域范围时，所述系统信息区域标识域强制存在；以及
当所述调度信息不包括一个或多个为一个SIB配置的区域范围时，所述系统信息区域标识域可选的存在。
8、根据附记1、5、6中的任一项所述的装置，其中，
所述调度信息中的系统信息区域标识域的必要性编码条件为：
当所述调度信息包括一个或多个为一个SIB配置的区域范围时，所述系统信息区域标识域强制存在；以及
当所述调度信息不包括一个或多个为一个SIB配置的区域范围时，所述系统信息区域标识域不存在。
9、根据附记1-2、4-8中的任一项所述的装置，其中，
所述调度信息包括所述系统信息区域标识和所述区域范围。
10、根据附记1-9中的任一项所述的装置，其中，
所述调度信息通过广播的形式发送。
11、根据附记1-10中的任一项所述的装置，其中，
所述调度信息包括在SIB1里。
12、一种系统信息的获取装置，所述装置应用于终端设备，所述装置包括：
第一获取单元，其获得调度信息，所述调度信息是基于系统信息区域标识(systemInformationAreaID)和区域范围(areaScope)的关联性生成的。
13、根据附记12所述的装置，其中，所述装置还包括：
第一确定单元，其对于一个SIB，根据所述调度信息和服务小区广播的系统信息中的其他信息确定是否存储了所述SIB的有效版本。
14、根据附记13所述的装置，其中，所述第一确定单元包括：
第二确定单元，其对于所述SIB的一个存储版本，当所述调度信息中的系统信息区域标识以及所述SIB关联的值标签(valueTag)以及所述其他信息中的公共陆地移动网标识(PLMN-Identity)与所述存储版本关联的系统信息区域标识、值标签以及公共陆地移动网标识相同时，所述终端设备认为所述存储版本有效，或者，对于所述SIB的一个存储版本，当所述调度信息中的所述SIB关联的值标签(valueTag)以及所述其他信息中的公共陆地移动网标识(PLMN-Identity)、小区标识与所述存储版本关联的值标签、公共陆地移动网标识以及小区标识(cellIdentity)相同时，认为所述存储版本有效；或者，
第三确定单元，其对于所述SIB的一个存储版本，当所述调度信息中的系统信息区域标识以及所述SIB关联的值标签、所述其他信息中的NPN标识(NPN-Identity)与所述存储版本关联的系统信息区域标识、值标签以及NPN标识相同时，所述终端设备认为所述存储版本有效，或者，对于所述SIB的一个存储版本，当所述调度信息中的所述SIB关联的值标签以及所述其他信息中的NPN标识(NPN-Identity)、小区标识与所述存储版本关联的值标签、NPN标识以及小区标识相同时，认为所述存储版本有效。
15、根据附记13或14所述的装置，其中，所述装置还包括：
第一使用单元，其当存在有效版本时，使用所述SIB的所述有效版本；以及
第二获取单元，其当不存在有效版本时，向所述网络设备发送系统信息请求或根据所述调度信息获取所述SIB。
16、根据附记12-15中的任一项所述的装置，其中，
所述调度信息包括所述系统信息区域标识和所述区域范围。
17、根据附记13-16中的任一项所述的装置，其中，
所述SIB为SIB2、SIB3、SIB4以及SIB5中的至少一个。
18、根据附记12-17中的任一项所述的装置，其中，
所述调度信息包括在SIB1里。
19、一种系统信息的获取装置，所述装置应用于终端设备，所述装置包括：
第四确定单元，其对于一个SIB的一个存储版本，当获得的调度信息包括对应于所述SIB的区域范围(areaScope)，并且，当所述调度信息包括系统信息区域标识(systemInformationAreaID)且所述系统信息区域标识以及第一信息与所述存储版本关联的系统信息区域标识以及相应信息相同时，认为所述存储版本有效。
20、根据附记19所述的装置，其中，所述装置还包括：
第五确定单元，其对于一个SIB的所述存储版本，当获得的调度信息包括对应于所述SIB的区域范围，并且，当所述调度信息不包括系统信息区域标识时，认为所述存储版本无效。
21、根据附记19所述的装置，其中，所述装置还包括：
第六确定单元，其对于一个SIB的所述存储版本，当获得的调度信息包括对应于所述SIB的区域范围，并且，当所述调度信息不包括系统信息区域标识而第一信息与所述存储版本关联的相应信息相同时，认为所述存储版本有效。
22、根据附记19所述的装置，其中，所述装置还包括：
第七确定单元，其对于一个SIB的所述存储版本，当获得的调度信息包括对应于所述SIB的区域范围(areaScope)，并且，当所述调度信息不包括系统信息区域标识而第一信息以及小区标识(cellIdentity)与所述存储版本关联的相应信息以及小区标识相同时，认为所述存储版本有效。
23、根据附记19-22中的任一项所述的装置，其中，
所述第一信息包括：从服务小区收到的包括在PLMN标识信息列表(PLMN-IdentityInfoList)中的第一个PLMN标识(PLMN-Identity)以及包括在所述调度信息中的所述SIB关联的值标签(valueTag)；
所述相应信息包括：与所述SIB的所述存储版本关联的PLMN标识 (PLMN-Identity)以及值标签。
24、根据附记19-23中的任一项所述的装置，其中，
当所述终端设备不具有NPN能力或服务小区不是仅NPN(NPN-only)小区时，
所述第一信息包括：从服务小区收到的包括在PLMN标识信息列表(PLMN-IdentityInfoList)中的第一个PLMN标识(PLMN-Identity)以及包括在所述调度信息中的所述SIB关联的值标签(valueTag)；
所述相应信息包括：与所述SIB的所述存储版本关联的PLMN标识(PLMN-Identity)以及值标签。
25、根据附记19-22中的任一项所述的装置，其中，
所述第一信息包括：从服务小区收到的包括NPN标识信息列表(NPN-IdentityInfoList)中的第一个NPN标识以及包括在所述调度信息中的所述SIB关联的值标签(valueTag)；
所述相应信息包括：与所述SIB的所述存储版本关联的NPN标识以及值标签。
26、根据附记19-22、25中的任一项所述的装置，其中，
当所述终端设备具有NPN能力且服务小区是仅NPN(NPN-only)小区时，
所述第一信息包括：从服务小区收到的包括NPN标识信息列表(NPN-IdentityInfoList)中的第一个NPN标识以及包括在所述调度信息中的所述SIB关联的值标签(valueTag)；
所述相应信息包括：与所述SIB的所述存储版本关联的NPN标识以及值标签。
27、根据附记19-26中的任一项所述的装置，其中，所述装置还包括：
第二使用单元，其当所述终端设备认为所述存储版本有效时，使用所述有效版本的所述SIB；以及
第三获取单元，其当不存在有效版本时，所述终端设备向所述网络设备发送系统信息请求或根据所述调度信息获取所述SIB。
33、一种网络设备，所述网络设备包括根据附记1-11中的任一项所述的装置。
34、一种终端设备，所述终端设备包括根据附记12-27中的任一项所述的装置。
35、一种通信系统，所述通信系统包括根据附记33所述的网络设备/或根据附记34所述的终端设备。
36、一种系统信息的配置方法，所述方法应用于网络设备，所述方法包括：
基于系统信息区域标识(systemInformationAreaID)和区域范围(areaScope)的关联性生成调度信息(SchedulingInfo)；以及
发送所述调度信息。
37、根据附记36所述的方法，其中，所述基于系统信息区域标识和区域范围的关联性生成调度信息，包括：
当所述调度信息包括所述系统信息区域标识时，所述网络设备在所述调度信息内为一个或多个SIB配置所述区域范围或者可选的在所述调度信息内为一个或多个SIB配置所述区域范围。
38、根据附记37所述的方法，其中，所述基于系统信息区域标识和区域范围的关联性生成调度信息，还包括：
当所述调度信息不包括所述系统信息区域标识时，所述网络设备不在所述调度信息内配置所述区域范围。
39、根据附记36-38中的任一项所述的方法，其中，
所述调度信息中的所述区域范围域的必要性编码条件为：
当所述调度信息包括所述系统信息区域标识时，所述区域范围域强制存在；当所述调度信息不包括所述系统信息区域标识时，所述区域范围域不存在，或者，
当所述调度信息包括所述系统信息区域标识时，所述区域范围域可选的存在；当所述调度信息不包括所述系统信息区域标识时，所述区域范围域不存在。
40、根据附记36所述的方法，其中，所述基于系统信息区域标识和区域范围的关联性生成调度信息，包括：
当所述调度信息包括一个或多个为一个SIB配置的区域范围时，所述网络设备将所述系统信息区域标识配置在所述调度信息内。
41、根据附记40所述的方法，其中，所述基于系统信息区域标识和区域范围的关联性生成调度信息，还包括：
当所述调度信息不包括一个或多个为一个SIB配置的区域范围时，所述网络设备将所述系统信息区域标识可选的配置在所述调度信息内，或者，所述网络设备不将所述系统信息区域标识配置在所述调度信息内。
42、根据附记36、40、41中的任一项所述的方法，其中，
所述调度信息中的系统信息区域标识域的必要性编码条件为：
当所述调度信息包括一个或多个为一个SIB配置的区域范围时，所述系统信息区域标识域强制存在；以及
当所述调度信息不包括一个或多个为一个SIB配置的区域范围时，所述系统信息区域标识域可选的存在。
43、根据附记36、40、41中的任一项所述的方法，其中，
所述调度信息中的系统信息区域标识域的必要性编码条件为：
当所述调度信息包括一个或多个为一个SIB配置的区域范围时，所述系统信息区域标识域强制存在；以及
当所述调度信息不包括一个或多个为一个SIB配置的区域范围时，所述系统信息区域标识域不存在。
44、根据附记36-37、39-43中的任一项所述的方法，其中，
所述调度信息包括所述系统信息区域标识和所述区域范围。
45、根据附记36-44中的任一项所述的方法，其中，
所述调度信息通过广播的形式发送。
46、根据附记36-45中的任一项所述的方法，其中，
所述调度信息包括在SIB1里。
47、一种系统信息的获取方法，所述方法应用于终端设备，所述方法包括：
获得调度信息，所述调度信息是基于系统信息区域标识(systemInformationAreaID)和区域范围(areaScope)的关联性生成的。
48、根据附记47所述的方法，其中，所述方法还包括：
对于一个SIB，根据所述调度信息和服务小区广播的系统信息中的其他信息确定是否存储了所述SIB的有效版本。
49、根据附记48所述的方法，其中，所述根据所述调度信息和服务小区广播的系统信息中的其他信息确定是否存储了所述SIB的有效版本，包括：
对于所述SIB的一个存储版本，当所述调度信息中的系统信息区域标识以及所述SIB关联的值标签(valueTag)以及所述其他信息中的公共陆地移动网标识(PLMN-Identity)与所述存储版本关联的系统信息区域标识、值标签以及公共陆地移动网标识相同时，所述终端设备认为所述存储版本有效，或者，对于所述SIB的一个存储版本，当所述调度信息中的所述SIB关联的值标签(valueTag)以及所述其他 信息中的公共陆地移动网标识(PLMN-Identity)、小区标识与所述存储版本关联的值标签、公共陆地移动网标识以及小区标识(cellIdentity)相同时，所述终端设备认为所述存储版本有效；或者，
对于所述SIB的一个存储版本，当所述调度信息中的系统信息区域标识以及所述SIB关联的值标签以及所述其他信息中的NPN标识(NPN-Identity)与所述存储版本关联的系统信息区域标识、值标签以及NPN标识相同时，所述终端设备认为所述存储版本有效，或者，对于所述SIB的一个存储版本，当所述调度信息中的所述SIB关联的值标签以及所述其他信息中的NPN标识(NPN-Identity)、小区标识与所述存储版本关联的值标签、NPN标识以及小区标识相同时，所述终端设备认为所述存储版本有效。
50、根据附记48或49所述的方法，其中，所述方法还包括：
当存在有效版本时，所述终端设备使用所述SIB的所述有效版本；以及
当不存在有效版本时，所述终端设备向所述网络设备发送系统信息请求或根据所述调度信息获取所述SIB。
51、根据附记47-50中的任一项所述的方法，其中，
所述调度信息包括所述系统信息区域标识和所述区域范围。
52、根据附记48-51中的任一项所述的方法，其中，
所述SIB为SIB2、SIB3、SIB4以及SIB5中的至少一个。
53、根据附记47-52中的任一项所述的方法，其中，
所述调度信息包括在SIB1里。
54、一种系统信息的获取方法，所述方法应用于终端设备，所述方法包括：
对于一个SIB的一个存储版本，当获得的调度信息包括对应于所述SIB的区域范围(areaScope)，并且，当所述调度信息包括系统信息区域标识(systemInformationAreaID)且所述系统信息区域标识以及第一信息与所述存储版本关联的系统信息区域标识以及相应信息相同时，所述终端设备认为所述存储版本有效。
55、根据附记54所述的方法，其中，所述方法还包括：
对于一个SIB的所述存储版本，当获得的调度信息包括对应于所述SIB的区域范围，并且，当所述调度信息不包括系统信息区域标识时，所述终端设备认为所述存储 版本无效。
56、根据附记54所述的方法，其中，所述方法还包括：
对于一个SIB的所述存储版本，当获得的调度信息包括对应于所述SIB的区域范围，并且，当所述调度信息不包括系统信息区域标识而第一信息与所述存储版本关联的相应信息相同时，所述终端设备认为所述存储版本有效。
57、根据附记54所述的方法，其中，所述方法还包括：
对于一个SIB的所述存储版本，当获得的调度信息包括对应于所述SIB的区域范围(areaScope)，并且，当所述调度信息不包括系统信息区域标识而第一信息以及小区标识(cellIdentity)与所述存储版本关联的相应信息以及小区标识相同时，所述终端设备认为所述存储版本有效。
58、根据附记54-57中的任一项所述的方法，其中，
所述第一信息包括：从服务小区收到的包括在PLMN标识信息列表(PLMN-IdentityInfoList)中的第一个PLMN标识(PLMN-Identity)以及包括在所述调度信息中的所述SIB关联的值标签(valueTag)；
所述相应信息包括：与所述SIB的所述存储版本关联的PLMN标识(PLMN-Identity)以及值标签。
59、根据附记54-58中的任一项所述的方法，其中，
当所述终端设备不具有NPN能力或服务小区不是仅NPN(NPN-only)小区时，
所述第一信息包括：从服务小区收到的包括在PLMN标识信息列表(PLMN-IdentityInfoList)中的第一个PLMN标识(PLMN-Identity)以及包括在所述调度信息中的所述SIB关联的值标签(valueTag)；
所述相应信息包括：与所述SIB的所述存储版本关联的PLMN标识(PLMN-Identity)以及值标签。
60、根据附记54-57中的任一项所述的方法，其中，
所述第一信息包括：从服务小区收到的包括NPN标识信息列表(NPN-IdentityInfoList)中的第一个NPN标识以及包括在所述调度信息中的所述SIB关联的值标签(valueTag)；
所述相应信息包括：与所述SIB的所述存储版本关联的NPN标识以及值标签。
61、根据附记54-57、60中的任一项所述的方法，其中，
当所述终端设备具有NPN能力且服务小区是仅NPN(NPN-only)小区时，
所述第一信息包括：从服务小区收到的包括NPN标识信息列表(NPN-IdentityInfoList)中的第一个NPN标识以及包括在所述调度信息中的所述SIB关联的值标签(valueTag)；
所述相应信息包括：与所述SIB的所述存储版本关联的NPN标识以及值标签。
62、根据附记54-61中的任一项所述的方法，其中，所述方法还包括：
当所述终端设备认为所述存储版本有效时，使用所述有效版本的所述SIB；以及
当不存在有效版本时，所述终端设备向所述网络设备发送系统信息请求或根据所述调度信息获取所述SIB。
附记二、
1、一种系统信息的配置装置，所述装置应用于网络设备，所述装置包括：
配置单元，其对于终端设备特定的参数，当存在条件包括服务小区配置了补充上行时，考虑终端设备的能力，或者，对于终端设备特定的参数和小区特定的参数，当存在条件包括服务小区配置了补充上行时，不考虑终端设备的能力或者只考虑网络设备为终端设备提供了SUL配置。
2、根据附记1所述的装置，其中，所述网络设备考虑终端设备的能力，包括：
基于所述终端设备的能力，所述网络设备确定所述终端设备能够支持SUL配置里提供的SUL频带；或者，
所述网络设备为所述终端设备提供了SUL配置，且基于所述终端设备的能力，所述网络设备确定所述终端设备能够支持SUL配置里指示的SUL频带；。
3、根据附记1或2所述的装置，其中，所述网络设备考虑终端设备的能力，包括：
公共小区配置(servingCellConfigCommon)里存在补充上行(supplementaryUplink)表示所述网络设备为所述终端设备提供了SUL配置。
4、根据附记1所述的装置，其中，
所述终端设备特定的参数是tpc-Index和/或tpc-IndexSUL。
5、根据附记1-3中的任一项所述的装置，其中，
所述对于终端设备特定的参数是或信息或IE或域。
6、根据附记1-5中的任一项所述的装置，其中，所述当存在条件包括服务小区 配置了补充上行时，不考虑终端设备的能力或者只考虑网络设备为终端设备提供了SUL配置，包括：
当小区公共的第一配置信息里包括补充上行配置时，在调度信息中可选的提供补充上行上用于系统信息消息发送的配置。
7、根据附记1-6中的任一项所述的装置，其中，
所述第一配置信息为服务小区公共配置(servingCellConfigCommon)。
8、根据附记1-7中的任一项所述的装置，其中，
所述配置单元当服务小区公共配置(servingCellConfigCommon)里存在补充上行(supplementaryUplink)且当调度信息(SchedulingInfo)里任意系统信息消息(SI-message)的系统信息广播状态设置为不广播时，在所述调度信息中可选的提供所述补充上行上用于系统信息消息发送的配置。
9、根据附记1-8中的任一项所述的装置，其中，所述补充上行上用于系统信息消息发送的配置的存在条件为：
当服务小区公共配置(servingCellConfigCommon)里存在补充上行(supplementaryUplink)且当调度信息(SchedulingInfo)里任意系统信息消息(SI-message)的系统信息广播状态(si-BroadcastStatus)设置为不广播时，所述补充上行上用于系统信息消息发送的配置可选的存在，否则，所述补充上行上用于系统信息消息发送的配置空缺。
10、根据附记1-9中的任一项所述的装置，其中，
所述调度信息包括在SIB1里。
11、一种网络设备，所述网络设备包括根据附记1-10中的任一项所述的装置。
12、一种通信系统，所述通信系统包括根据附记11所述的网络设备。
13、一种系统信息的配置方法，所述方法应用于网络设备，所述方法包括：
对于终端设备特定的参数，当存在条件包括服务小区配置了补充上行时，所述网络设备考虑终端设备的能力，或者，
对于终端设备特定的参数和小区特定的参数，当存在条件包括服务小区配置了补充上行时，所述网络设备不考虑终端设备的能力或者所述网络设备只考虑网络设备为终端设备提供了SUL配置。
14、根据附记13所述的方法，其中，所述网络设备考虑终端设备的能力，包括：
基于所述终端设备的能力，所述网络设备确定所述终端设备能够支持SUL配置里提供的SUL频带；或者，
所述网络设备为所述终端设备提供了SUL配置，且基于所述终端设备的能力，所述网络设备确定所述终端设备能够支持SUL配置里指示的SUL频带。
15、根据附记13或14所述的方法，其中，所述网络设备考虑终端设备的能力，包括：
公共小区配置(servingCellConfigCommon)里存在补充上行(supplementaryUplink)表示所述网络设备为所述终端设备提供了SUL配置。
16、根据附记13所述的方法，其中，
所述终端设备特定的参数是tpc-Index和/或tpc-IndexSUL。
17、根据附记13-15中的任一项所述的方法，其中，
所述对于终端设备特定的参数是或信息或IE或域。
18、根据附记13-17中的任一项所述的方法，其中，所述当存在条件包括服务小区配置了补充上行时，不考虑终端设备的能力或者只考虑网络设备为终端设备提供了SUL配置，包括：
当小区公共的第一配置信息里包括补充上行配置时，在调度信息中可选的提供补充上行上用于系统信息消息发送的配置(si-RequestConfigSUL)。
19、根据附记18所述的方法，其中，
所述第一配置信息为服务小区公共配置(servingCellConfigCommon))。
20、根据附记13-19中的任一项所述的方法，其中，
当服务小区公共配置(servingCellConfigCommon)里存在补充上行(supplementaryUplink)且当调度信息(SchedulingInfo)里任意系统信息消息(SI-message)的系统信息广播状态设置为不广播时，在所述调度信息中可选的提供所述补充上行上用于系统信息消息发送的配置。
21、根据附记13-20中的任一项所述的方法，其中，所述补充上行上用于系统信息消息发送的配置的存在条件为：
当服务小区公共配置(servingCellConfigCommon)里存在补充上行(supplementaryUplink)且当调度信息(SchedulingInfo)里任意系统信息消息(SI-message)的系统信息广播状态(si-BroadcastStatus)设置为不广播时，所述补充 上行上用于系统信息消息发送的配置可选的存在，否则，所述补充上行上用于系统信息消息发送的配置空缺。
22、根据附记13-21中的任一项所述的方法，其中，
所述调度信息包括在SIB1里。

Claims (20)

  1. 一种系统信息的配置装置，所述装置应用于网络设备，所述装置包括：
    生成单元，其基于系统信息区域标识(systemInformationAreaID)和区域范围(areaScope)的关联性生成调度信息(SchedulingInfo)；以及
    发送单元，其发送所述调度信息。
  2. 根据权利要求1所述的装置，其中，
    所述生成单元当所述调度信息包括所述系统信息区域标识时，在所述调度信息内为一个或多个SIB配置所述区域范围或者可选的在所述调度信息内为一个或多个SIB配置所述区域范围。
  3. 根据权利要求2所述的装置，其中，
    所述生成单元当所述调度信息不包括所述系统信息区域标识时，不在所述调度信息内配置所述区域范围。
  4. 根据权利要求1所述的装置，其中，
    所述生成单元当所述调度信息包括一个或多个为一个SIB配置的区域范围时将所述系统信息区域标识配置在所述调度信息内。
  5. 根据权利要求4所述的装置，其中，
    所述生成单元当所述调度信息不包括一个或多个为一个SIB配置的区域范围时，将所述系统信息区域标识可选的配置在所述调度信息内，或者，不将所述系统信息区域标识配置在所述调度信息内。
  6. 根据权利要求1所述的装置，其中，
    所述调度信息中的系统信息区域标识域的必要性编码条件为：
    当所述调度信息包括一个或多个为一个SIB配置的区域范围时，所述系统信息区域标识域强制存在；以及
    当所述调度信息不包括一个或多个为一个SIB配置的区域范围时，所述系统信息区域标识域可选的存在。
  7. 根据权利要求1所述的装置，其中，
    所述调度信息中的系统信息区域标识域的必要性编码条件为：
    当所述调度信息包括一个或多个为一个SIB配置的区域范围时，所述系统信息区 域标识域强制存在；以及
    当所述调度信息不包括一个或多个为一个SIB配置的区域范围时，所述系统信息区域标识域不存在。
  8. 一种系统信息的获取装置，所述装置应用于终端设备，所述装置包括：
    第一获取单元，其获得调度信息，所述调度信息是基于系统信息区域标识(systemInformationAreaID)和区域范围(areaScope)的关联性生成的。
  9. 根据权利要求8所述的装置，其中，所述装置还包括：
    第一确定单元，其对于一个SIB，根据所述调度信息和服务小区广播的系统信息中的其他信息确定是否存储了所述SIB的有效版本。
  10. 根据权利要求9所述的装置，其中，所述第一确定单元包括：
    第二确定单元，其对于所述SIB的一个存储版本，当所述调度信息中的系统信息区域标识以及所述SIB关联的值标签(valueTag)以及所述其他信息中的公共陆地移动网标识(PLMN-Identity)与所述存储版本关联的系统信息区域标识、值标签以及公共陆地移动网标识相同时，所述终端设备认为所述存储版本有效，或者，对于所述SIB的一个存储版本，当所述调度信息中的所述SIB关联的值标签(valueTag)以及所述其他信息中的公共陆地移动网标识(PLMN-Identity)、小区标识与所述存储版本关联的值标签、公共陆地移动网标识以及小区标识(cellIdentity)相同时认为所述存储版本有效；或者，
    第三确定单元，其对于所述SIB的一个存储版本，当所述调度信息中的系统信息区域标识以及所述SIB关联的值标签、所述其他信息中的NPN标识(NPN-Identity)与所述存储版本关联的系统信息区域标识、值标签以及NPN标识相同时，所述终端设备认为所述存储版本有效，或者，对于所述SIB的一个存储版本，当所述调度信息中的所述SIB关联的值标签以及所述其他信息中的NPN标识(NPN-Identity)、小区标识与所述存储版本关联的值标签、NPN标识以及小区标识相同时，认为所述存储版本有效。
  11. 根据权利要求9所述的装置，其中，所述装置还包括：
    第一使用单元，其当存在有效版本时，使用所述SIB的所述有效版本；以及
    第二获取单元，其当不存在有效版本时，向网络设备发送系统信息请求或根据所述调度信息获取所述SIB。
  12. 一种系统信息的获取装置，所述装置应用于终端设备，所述装置包括：
    第四确定单元，其对于一个SIB的一个存储版本，当获得的调度信息包括对应于所述SIB的区域范围(areaScope)，并且，当所述调度信息包括系统信息区域标识(systemInformationAreaID)且所述系统信息区域标识以及第一信息与所述存储版本关联的系统信息区域标识以及相应信息相同时，认为所述存储版本有效。
  13. 根据权利要求12所述的装置，其中，所述装置还包括：
    第五确定单元，其对于一个SIB的所述存储版本，当获得的调度信息包括对应于所述SIB的区域范围，并且，当所述调度信息不包括系统信息区域标识时，认为所述存储版本无效。
  14. 根据权利要求12所述的装置，其中，所述装置还包括：
    第六确定单元，其对于一个SIB的所述存储版本，当获得的调度信息包括对应于所述SIB的区域范围，并且，当所述调度信息不包括系统信息区域标识而第一信息与所述存储版本关联的相应信息相同时，认为所述存储版本有效。
  15. 根据权利要求12所述的装置，其中，所述装置还包括：
    第七确定单元，其对于一个SIB的所述存储版本，当获得的调度信息包括对应于所述SIB的区域范围(areaScope)，并且，当所述调度信息不包括系统信息区域标识而第一信息以及小区标识(cellIdentity)与所述存储版本关联的相应信息以及小区标识相同时，认为所述存储版本有效。
  16. 根据权利要求12所述的装置，其中，
    所述第一信息包括：从服务小区收到的包括在PLMN标识信息列表(PLMN-IdentityInfoList)中的第一个PLMN标识(PLMN-Identity)以及包括在所述调度信息中的所述SIB关联的值标签(valueTag)；
    所述相应信息包括：与所述SIB的所述存储版本关联的PLMN标识(PLMN-Identity)以及值标签。
  17. 根据权利要求12所述的装置，其中，
    当所述终端设备不具有NPN能力或服务小区不是仅NPN(NPN-only)小区时，
    所述第一信息包括：从服务小区收到的包括在PLMN标识信息列表(PLMN-IdentityInfoList)中的第一个PLMN标识(PLMN-Identity)以及包括在所述调度信息中的所述SIB关联的值标签(valueTag)；
    所述相应信息包括：与所述SIB的所述存储版本关联的PLMN标识(PLMN-Identity)以及值标签。
  18. 根据权利要求12所述的装置，其中，
    所述第一信息包括：从服务小区收到的包括NPN标识信息列表(NPN-IdentityInfoList)中的第一个NPN标识以及包括在所述调度信息中的所述SIB关联的值标签(valueTag)；
    所述相应信息包括：与所述SIB的所述存储版本关联的NPN标识以及值标签。
  19. 根据权利要求12所述的装置，其中，
    当所述终端设备具有NPN能力且服务小区是仅NPN(NPN-only)小区时，
    所述第一信息包括：从服务小区收到的包括NPN标识信息列表(NPN-IdentityInfoList)中的第一个NPN标识以及包括在所述调度信息中的所述SIB关联的值标签(valueTag)；
    所述相应信息包括：与所述SIB的所述存储版本关联的NPN标识以及值标签。
  20. 根据权利要求12所述的装置，其中，所述装置还包括：
    第二使用单元，其当所述终端设备认为所述存储版本有效时，使用所述有效版本的所述SIB；以及
    第三获取单元，其当不存在有效版本时，所述终端设备向网络设备发送系统信息请求或根据所述调度信息获取所述SIB。
PCT/CN2020/107581 2020-08-06 2020-08-06 系统信息的配置方法、获取方法及装置 WO2022027525A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
PCT/CN2020/107581 WO2022027525A1 (zh) 2020-08-06 2020-08-06 系统信息的配置方法、获取方法及装置
CN202080104343.6A CN116097739A (zh) 2020-08-06 2020-08-06 系统信息的配置方法、获取方法及装置
US18/104,346 US20230180227A1 (en) 2020-08-06 2023-02-01 Methods for configuring and acquiring system information and apparatuses thereof

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2020/107581 WO2022027525A1 (zh) 2020-08-06 2020-08-06 系统信息的配置方法、获取方法及装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/104,346 Continuation US20230180227A1 (en) 2020-08-06 2023-02-01 Methods for configuring and acquiring system information and apparatuses thereof

Publications (1)

Publication Number Publication Date
WO2022027525A1 true WO2022027525A1 (zh) 2022-02-10

Family

ID=80119854

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/107581 WO2022027525A1 (zh) 2020-08-06 2020-08-06 系统信息的配置方法、获取方法及装置

Country Status (3)

Country Link
US (1) US20230180227A1 (zh)
CN (1) CN116097739A (zh)
WO (1) WO2022027525A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107113657A (zh) * 2015-04-17 2017-08-29 松下电器（美国）知识产权公司 Mtc系统信息的覆盖增强等级信令和高效封装
CN107645730A (zh) * 2016-07-20 2018-01-30 电信科学技术研究院 一种系统信息的获取、发送方法、移动终端及接入点
US20200052768A1 (en) * 2018-08-07 2020-02-13 Samsung Electronics Co., Ltd. Method and apparatus for validating stored system information
US20200187100A1 (en) * 2017-08-08 2020-06-11 Lg Electronics Inc. Method and apparatus for reducing system information acquisition time in wireless communication system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107113657A (zh) * 2015-04-17 2017-08-29 松下电器（美国）知识产权公司 Mtc系统信息的覆盖增强等级信令和高效封装
CN107645730A (zh) * 2016-07-20 2018-01-30 电信科学技术研究院 一种系统信息的获取、发送方法、移动终端及接入点
US20200187100A1 (en) * 2017-08-08 2020-06-11 Lg Electronics Inc. Method and apparatus for reducing system information acquisition time in wireless communication system
US20200052768A1 (en) * 2018-08-07 2020-02-13 Samsung Electronics Co., Ltd. Method and apparatus for validating stored system information

Also Published As

Publication number Publication date
CN116097739A (zh) 2023-05-09
US20230180227A1 (en) 2023-06-08

Similar Documents

Publication Publication Date Title
EP3934299A1 (en) Communication method and apparatus
US12010576B2 (en) Communication method, apparatus, and system
US20180139690A1 (en) System and Method for Efficient Communications System Scanning
US20210250824A1 (en) Controlling the Operation of Mobile Terminals with Respect to Multiple Radio Access Technologies
WO2019024816A1 (zh) 传输信息的方法和装置
RU2678661C1 (ru) Способ связи устройство-устройство, устройство и система
US20220408518A1 (en) Multi-sim dynamic capabilities
US9769802B2 (en) Method and apparatus for registering access point through WiFi network by using information obtained from common device in cellular-WiFi convergence system
CN106160963B (zh) 一种网络功能配置方法及终端、基站
US11812367B2 (en) Method and apparatus for transmitting and receiving information in a wireless communication system
WO2019095894A1 (zh) 测量信号的方法和设备
WO2015119553A1 (en) Controlling wlan access in case of wlan/3gpp radio interworking
IL258384B (en) An access point that supports at least two virtual networks and a method performed by it to communicate with a wireless device
US20220159565A1 (en) Method and apparatus for node selection in integrated access and backhaul network
WO2021065748A1 (en) Method and apparatus for performing handover of a multi-usim radio-capable ue over same or different systems
WO2022027525A1 (zh) 系统信息的配置方法、获取方法及装置
WO2016058499A1 (en) System and method for reducing communications overhead
WO2021087916A1 (zh) 必要系统信息获取失败时的处理方法及装置
KR102207117B1 (ko) 시스템 정보 획득 방법, 사용자 단말기와 네트워크측 기기
WO2024007795A1 (zh) 通信方法与通信装置
WO2022082758A1 (zh) 切片信息的使用方法、装置、设备及存储介质
WO2021226953A1 (zh) 小区搜索方法及装置
CN108811040B (zh) 系统信息变更指示方法、网络侧设备及终端
WO2020147038A1 (en) Method and apparatus for dedicated core network selection
WO2021062675A1 (zh) 无线通信方法及设备

Legal Events

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

Ref document number: 20947946

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20947946

Country of ref document: EP

Kind code of ref document: A1