System information configuration method, acquisition method and apparatus

Abstract

A method and apparatus for configuring and acquiring system information. The method for configuring includes generating scheduling information based on the association between a system information area identifier and an area range, and transmitting the scheduling information.

Description

Technical Field

[0001] This application relates to the field of communications. Background Technology

[0002] In New Radio (NR), before establishing communication, terminal devices need to apply a system information acquisition process to obtain access stratum (AS) and non-access stratum (NAS) information. This system information acquisition process is applicable to terminal devices in idle, disconnected, and connected states.

[0003] Figure 1 This is a schematic diagram of the system information acquisition process in NR. For example... Figure 1 As shown, the process includes: the terminal device acquiring the Master Information Block (MIB); the terminal device can also acquire System Information Block 1 (SIB1); in addition, if necessary, the terminal device can also send a System Information Request to the network device to request the network device to broadcast System Information messages and acquire the system information messages.

[0004] It should be noted that the above introduction to the technical background is for convenience, to provide a clear and complete explanation of the technical solutions of this application, and to facilitate understanding by those skilled in the art. It should not be assumed that these technical solutions are known to those skilled in the art simply because they have been described in the background section of this application. Summary of the Invention

[0005] In NR, stored system information blocks are introduced. Using this method, the terminal device can store the acquired SIBs. In addition to MIBs, SIB1, SIB6 (SystemInformationBlockType6), SIB7 (SystemInformationBlockType7), or SIB8 (SystemInformationBlockType8), for other required SIBs, such as after cell reselection, when returning from outside coverage, or after receiving a system information (SI) modification instruction, the terminal device can use the valid version of the stored system information.

[0006] When selecting a cell (e.g., upon power-on), during cell reselection, returning from no coverage, after synchronization reconfiguration, entering the network from another RAT, receiving a system information change indication, receiving a PWS notification, or receiving a request from an upper layer (e.g., a location request), the terminal device will apply the system information acquisition process. First, it will acquire and store the MIB and SIB1. For a required SIB, the terminal device can check if a valid version of the SIB is stored. If a valid version is stored, it can use that version; otherwise, it will acquire the SIB. Furthermore, the terminal device can store the acquired SIB and its associated information, including area scope, Public Land Mobile Network (PLMN) identity, system information area ID (System Information Area ID), and cell identity.

[0007] For the required SIB, the terminal device can check whether a valid version is stored.

[0008] For example, for a storage version of this SIB, if this storage version of the SIB is associated with an "areaScope", then if the terminal device does not have NPN (non-public networks) capability or the serving cell is not an NPN-only cell, the terminal device considers the storage version valid when the system information area identifier in the system scheduling information (si-SchedulingInfo, also known as scheduling information), the value tag associated with the SIB, and the public land mobile network identifier (PLMN-Identity) in other information are the same as the system information area identifier, value tag, and public land mobile network identifier associated with the storage version; otherwise, it is considered invalid. If the terminal device has NPN capability and the serving cell is an NPN-only cell, the terminal device considers the storage version valid when the system information area identifier in the system scheduling information, the value tag associated with the SIB, and the NPN identifier (NPN-Identity) in other information are the same as the system information area identifier, value tag, and NPN identifier associated with the storage version; otherwise, it is considered invalid.

[0009] 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, the terminal device considers the stored version valid if the value label associated with the SIB in the system scheduling information, the public land mobile network identifier in other information, and the cell identifier are the same as the value label associated with the stored version, the public land mobile network identifier, and the cell identifier; otherwise, it considers it invalid. If the terminal device has NPN capability and the serving cell is an NPN-only cell, the terminal device considers the stored version valid if the value label 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 label associated with the stored version, the NPN identifier, and the cell identifier; otherwise, it considers it invalid.

[0010] The inventors discovered that, based on the current mechanism, if the system scheduling information (si-SchedulingInfo) of the serving cell configures "areaScope" for a SIB, the terminal device checks the system information area identifier and other information in the system scheduling information to determine the validity of the stored version.

[0011] However, the system information area identifier is optional, meaning that in some scenarios, the network side may not provide this information. In such cases, the behavior of the terminal device is uncertain for an SIB associated with "areaScope." For example, the terminal device may not be able to determine whether the storage version of the SIB is valid, or it may assume that all storage versions of the SIB are invalid or that multiple storage versions are valid. This will cause testing errors on the terminal device, increase testing costs, and may also increase the terminal device's power consumption.

[0012] To address one or more of the aforementioned problems, embodiments of this application provide a method for configuring system information, a method for obtaining system information, and an apparatus. Network devices generate scheduling information based on the correlation between system information region identifiers and region ranges. This avoids situations where region ranges are configured but system information region identifiers are not, or where terminal devices, when checking the validity of a SIB's storage version, specify the terminal device's behavior with or without configured system information region identifiers. Therefore, it avoids uncertainty in terminal device behavior and reduces testing complexity and terminal device overhead.

[0013] According to a first aspect of the embodiments of this application, a system information configuration apparatus is provided, the apparatus being applied to a network device, the apparatus comprising: a generation unit that generates scheduling information based on the correlation between a system information area ID (systemInformationAreaID) and an area scope (areaScope); and a sending unit that sends the scheduling information.

[0014] According to a second aspect of the embodiments of this application, a system information acquisition device is provided. The device is applied to a terminal device and includes: a first acquisition unit that acquires scheduling information, the scheduling information being generated based on the association between a system information area ID (systemInformationAreaID) and an area scope (areaScope).

[0015] According to a third aspect of the embodiments of this application, a system information acquisition apparatus is provided. The apparatus is applied to a terminal device and includes: a fourth determining unit, which, for a storage version of a SIB, considers the storage version to be valid when the obtained scheduling information includes an area scope corresponding to the SIB, and when the scheduling information includes a system information area ID and the system information area ID and the first information associated with the storage version are the same as the system information area ID and the corresponding information.

[0016] According to a fourth aspect of the present application, a network device is provided, the network device including the apparatus described in the first aspect of the present application.

[0017] According to a fifth aspect of the embodiments of this application, a terminal device is provided, the network device including the apparatus described in the second or third aspect of the embodiments of this application.

[0018] According to a sixth aspect of the present application, a communication system is provided, the communication system including the network device described in the fourth aspect of the present application and / or the terminal device described in the fifth aspect of the present application.

[0019] According to a seventh aspect of the embodiments of this application, a method for configuring system information is provided, the method being applied to a network device, the method comprising: generating scheduling information based on the correlation between a system information area identifier (systemInformationAreaID) and an area scope (areaScope); and sending the scheduling information.

[0020] According to an eighth aspect of the embodiments of this application, a method for obtaining system information is provided, the method being applied to a terminal device, the method comprising: obtaining scheduling information, the scheduling information being generated based on the association between a system information area ID (systemInformationAreaID) and an area scope (areaScope).

[0021] According to a ninth aspect of the present application, a method for obtaining system information is provided. The method is applied to a terminal device. The method includes: for a storage version of an SIB, when the obtained scheduling information includes an area scope corresponding to the SIB, and when the scheduling information includes a system information area ID and the system information area ID and first information associated with the storage version are the same, the terminal device considers the storage version to be valid.

[0022] According to a tenth aspect of the present application, a computer-readable program is provided, wherein when the program is executed in a system information configuration device or network device, the program causes the system information configuration device or network device to perform the system information configuration method described in the seventh aspect of the present application.

[0023] According to an eleventh aspect of the present application, a storage medium storing a computer-readable program is provided, wherein the computer-readable program causes a system information configuration device or a network device to perform the system information configuration method described in the seventh aspect of the present application.

[0024] According to a twelfth aspect of the present application, a computer-readable program is provided, wherein when the program is executed in a system information acquisition device or terminal device, the program causes the system information acquisition device or terminal device to perform the system information acquisition method described in the eighth or ninth aspect of the present application.

[0025] According to a thirteenth aspect of the present application, a storage medium storing a computer-readable program is provided, wherein the computer-readable program causes a system information acquisition device or terminal device to perform the system information acquisition method described in the eighth or ninth aspect of the present application.

[0026] One of the beneficial effects of this application's embodiments is that: the network device generates scheduling information based on the correlation between the system information region identifier and the region range, which can avoid the situation where the region range is configured but the system information region identifier is not configured, or, when checking the validity of a SIB's storage version, the terminal device's behavior is specified with or without the system information region identifier configured. Therefore, the uncertainty of the terminal device's behavior can be avoided, and the complexity of testing and the overhead of the terminal device can be reduced.

[0027] In addition, once the terminal device has acquired the MIB and SIB1, it can send a system information request message to the network device if needed, requesting the network to broadcast the system information message.

[0028] To ensure the transmission of system information request messages, network devices can provide the following configurations:

[0029] SIB1 only includes si-RequestConfigSUL;

[0030] SIB1 only includes si-RequestConfig;

[0031] SIB1 includes si-RequestConfigSUL and si-RequestConfig; and

[0032] SIB1 does not include si-RequestConfigSUL and si-RequestConfig.

[0033] Similarly, for location system information, network devices can provide the following configurations:

[0034] SIB1 only includes posSI-RequestConfigSUL-r16;

[0035] SIB1 only includes posSI-RequestConfig-r16;

[0036] SIB1 includes posSI-RequestConfigSUL-r16 and posSI-RequestConfigSUL-r16; while SIB1 does not include posSI-RequestConfigSUL-r16 and posSI-RequestConfigSUL-r16.

[0037] Among them, si-RequestConfig and posSI-RequestConfigSUL-r16 are configurations used to request system information messages on the Normal Uplink (Normal UL, NUL), while si-RequestConfigSUL and posSI-RequestConfigSUL-r16 are configurations used to request system information messages on the Supplementary Uplink (SUL).

[0038] The inventors also discovered that, under the current mechanism, if the serving cell is configured with supplementary uplink and if the system information broadcast status (e.g., si-BroadcastStatus, posSI-BroadcastStatus) of any system information message (SI-message) in the scheduling information (SchedulingInfo) is set to "not broadcasting", the configuration for sending system information messages on the supplementary uplink (e.g., si-RequestConfigSUL, posSI-RequestConfigSUL-r16) is optionally present; otherwise, si-RequestConfigSUL is empty. Therefore, in order to determine whether si-RequestConfigSUL or posSI-RequestConfigSUL-r16 is provided, the network device needs to know whether the serving cell is configured with supplementary uplink.

[0039] Under the current mechanism, when a network device provides a Supplemental Uplink (SUL) configuration, and considering the capabilities of the terminal device (e.g., supported frequency bands, supported uplink channel bandwidth, etc.), the terminal device considers the serving cell to have a Supplemental Uplink configured. While the network device knows whether it has provided an SUL configuration, it may not be able to determine the aforementioned terminal device capabilities. This is because the terminal devices residing in that cell may not have yet indicated their capabilities to the network device; or, even if all terminal devices have provided their capabilities, for a given SUL configuration, some terminal devices in the serving cell may support that configuration, while others may not. Therefore, the network device cannot determine whether the serving cell has a Supplemental Uplink configured, and thus cannot determine whether SIB1 includes si-RequestConfigSUL or posSI-RequestConfigSUL-r16.

[0040] To address one or more of the aforementioned problems, embodiments of this application also provide a method and apparatus for configuring system information. For terminal device-specific parameters, when the condition includes the serving cell configuring supplementary uplink, the capabilities of the terminal device are considered; alternatively, for both terminal device-specific and cell-specific parameters, when the condition includes the serving cell configuring supplementary uplink, the capabilities of the terminal device are not considered, or only the network device providing SUL configuration for the terminal device is considered. This allows the network device to clearly define the contents of SIB1, avoiding uncertainties in network device implementation, reducing testing costs for network device products, and thus saving network deployment costs.

[0041] According to a fourteenth aspect of the present application, a system information configuration apparatus is provided, the apparatus being applied to a network device, the apparatus comprising: a configuration unit that, for terminal device-specific parameters, considers the capabilities of the terminal device when conditions include supplemental uplink configuration of the serving cell, or, for terminal device-specific parameters and cell-specific parameters, does not consider the capabilities of the terminal device or only considers that the network device provides SUL configuration for the terminal device when conditions include supplemental uplink configuration of the serving cell.

[0042] According to a fifteenth aspect of the present application, a network device is provided, the network device including the apparatus described in a fourteenth aspect of the present application.

[0043] According to a sixteenth aspect of the present application, a communication system is provided, the communication system including the network device described in a fourteenth aspect of the present application.

[0044] According to a seventeenth aspect of the embodiments of this application, a method for configuring system information is provided, the method being applied to a network device, the method comprising:

[0045] For terminal device-specific parameters, when the conditions include the serving cell configuring supplemental uplink, the network device considers the terminal device's capabilities; or, for both terminal device-specific and cell-specific parameters, when the conditions include the serving cell configuring supplemental uplink, the network device does not consider the terminal device's capabilities or only considers that the network device provides SUL configuration for the terminal device.

[0046] According to the eighteenth aspect of the present application, a computer-readable program is provided, wherein when the program is executed in a system information configuration device or network device, the program causes the system information configuration device or network device to perform the system information configuration method described in the seventeenth aspect of the present application.

[0047] According to a nineteenth aspect of the present application, a storage medium storing a computer-readable program is provided, wherein the computer-readable program causes a system information configuration device or a network device to perform the system information configuration method described in the seventeenth aspect of the present application.

[0048] One of the beneficial effects of this application's embodiments is that, for terminal device-specific parameters, when the condition includes the serving cell configuring supplementary uplink, the capabilities of the terminal device are considered; or, for both terminal device-specific and cell-specific parameters, when the condition includes the serving cell configuring supplementary uplink, the capabilities of the terminal device are not considered, or only the network device providing SUL configuration for the terminal device is considered. In this way, the network device can clearly understand the content in SIB1, avoiding uncertainties in network device implementation, reducing the testing costs of network device products, and thus saving network deployment costs.

[0049] Specific embodiments of this application are disclosed in detail with reference to the following description and accompanying drawings, indicating how the principles of this application can be adopted. It should be understood that the embodiments of this application are not limited in scope. Within the spirit and scope of the appended claims, embodiments of this application include many changes, modifications, and equivalents.

[0050] Features described and / or illustrated for one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0051] It should be emphasized that the term "including / comprises / have" as used herein refers to the presence of a feature, whole, step, or component, but does not exclude the presence or addition of one or more other features, wholes, steps, or components. Attached Figure Description

[0052] The elements and features described in one drawing or embodiment of this application may be combined with elements and features shown in one or more other drawings or embodiments. Furthermore, in the drawings, similar reference numerals denote corresponding parts in several drawings and can be used to indicate corresponding parts used in more than one embodiment.

[0053] The accompanying drawings, which form part of the specification, are used to provide a further understanding of the embodiments of this application and illustrate the implementation methods of this application, together with the textual description, to explain the principles of this application. Obviously, the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any creative effort. In the drawings:

[0054] Figure 1 This is a schematic diagram of the system information acquisition process in NR;

[0055] Figure 2 This is a schematic diagram of a communication system according to an embodiment of this application;

[0056] Figure 3 This is a schematic diagram of a system information configuration method according to Embodiment 1 of this application;

[0057] Figure 4 This is a schematic diagram of the method for generating scheduling information according to Embodiment 1 of this application;

[0058] Figure 5 This is another schematic diagram of the method for generating scheduling information according to Embodiment 1 of this application;

[0059] Figure 6 This is another schematic diagram of the method for generating scheduling information according to Embodiment 1 of this application;

[0060] Figure 7 This is a schematic diagram of a system information acquisition method according to Embodiment 2 of this application;

[0061] Figure 8 This is a schematic diagram of a system information acquisition method according to Embodiment 3 of this application;

[0062] Figure 9 This is a schematic diagram of a system information acquisition method according to Embodiment 4 of this application;

[0063] Figure 10 This is another schematic diagram of the system information acquisition method of Embodiment 4 of this application;

[0064] Figure 11 This is yet another schematic diagram of the system information acquisition method in Embodiment 4 of this application;

[0065] Figure 12 This is a schematic diagram of a system information configuration method according to Embodiment 5 of this application;

[0066] Figure 13 This is a schematic diagram of a system information configuration device according to Embodiment 6 of this application;

[0067] Figure 14 This is a schematic diagram of a system information acquisition device according to Embodiment 7 of this application;

[0068] Figure 15 This is a schematic diagram of the first determining unit in Embodiment 7 of this application;

[0069] Figure 16 This is a schematic diagram of a system information acquisition device according to Embodiment 8 of this application;

[0070] Figure 17 This is a schematic diagram of a system information acquisition device according to Embodiment 9 of this application;

[0071] Figure 18 This is a schematic block diagram of the system configuration of the network device in Embodiment 10 of this application;

[0072] Figure 19 This is a schematic block diagram of the system configuration of the terminal device according to Embodiment 11 of this application;

[0073] Figure 20 This is a schematic block diagram of the system configuration of the terminal device of Embodiment 12 of this application;

[0074] Figure 21 This is a schematic block diagram of the system configuration of the network device in Embodiment 13 of this application. Detailed Implementation

[0075] Referring to the accompanying drawings, the foregoing and other features of this application will become apparent from the following description. Specific embodiments of this application are specifically disclosed in the description and drawings, illustrating partial implementations in which the principles of this application may be employed. It should be understood that this application is not limited to the described embodiments; rather, it includes all modifications, variations, and equivalents falling within the scope of the appended claims.

[0076] In the embodiments of this application, the terms "first," "second," etc., are used to distinguish different elements by name, but do not indicate the spatial arrangement or chronological order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one or more of the terms listed in association and all combinations thereof. The terms "comprising," "including," "having," etc., refer to the presence of the stated features, elements, components, or assemblies, but do not exclude the presence or addition of one or more other features, elements, components, or assemblies.

[0077] In the embodiments of this application, the singular forms "a," "the," etc., including the plural forms, should be broadly understood as "a kind" or "a class" rather than limited to the meaning of "an." Furthermore, the term "the" should be understood to include both the singular and plural forms, unless the context explicitly indicates otherwise. Additionally, the term "according to" should be understood as "at least partially based on…," and the term "based on" should be understood as "at least partially based on…," unless the context explicitly indicates otherwise.

[0078] In the embodiments of this application, 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), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0079] Furthermore, communication between devices in a communication system can be carried out according to communication protocols at any stage, 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), and / or other currently known or future communication protocols.

[0080] In the embodiments of this application, the term "network device" refers, for example, to a device in a communication system that connects a user equipment to a communication network and provides services to that user equipment. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0081] The term "base station" can include, but is not limited to, NodeBs (or NBs), evolved NodeBs (or eNodeBs or eNBs), and 5G base stations (gNBs), etc. It can also include Remote Radio Heads (RRHs), Remote Radio Units (RRUs), relays, or low-power nodes (e.g., femto, pico, etc.). The term "base station" can encompass some or all of its functions, and each base station can provide communication coverage to a specific geographic area. The term "cell" can refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0082] In the embodiments of this application, the term "user equipment" (UE) refers to a device that accesses a communication network and receives network services through a network device, and can also be called "terminal equipment" (TE). Terminal equipment can be fixed or mobile, and can also be called a mobile station (MS), terminal, subscriber station (SS), access terminal (AT), station, etc.

[0083] The terminal device may include, but is not limited to, the following devices: cellular phone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, machine-type communication device, laptop computer, cordless phone, smartphone, smartwatch, digital camera, etc.

[0084] For example, in scenarios such as the Internet of Things (IoT), terminal devices can also be machines or devices for monitoring or measurement, such as including but not limited to: machine-type communication (MTC) terminals, vehicle communication terminals, device-to-device (D2D) terminals, machine-to-machine (M2M) terminals, and so on.

[0085] In the embodiments of this application, "when," "under the circumstances," "for the situation of," and "if" all indicate based on one or more conditions or states, and these expressions can be used interchangeably.

[0086] The following examples illustrate the scenarios of embodiments of this application, but this application is not limited thereto.

[0087] Figure 2 This is a schematic diagram of a communication system according to an embodiment of this application, illustrating the case with terminal equipment and network equipment as examples, such as... Figure 2 As shown, the communication system 100 may include: a network device 101 and a terminal device 102. For simplicity, Figure 1 This explanation will use only one terminal device as an example. Network device 101 is, for example, an NR network device gNB.

[0088] In this embodiment of the application, network device 101 and terminal device 102 can perform existing services or services that can be implemented in the future. For example, these services include, but are not limited to: enhanced mobile broadband (eMBB), massive machine-type communication (mMTC), and ultra-reliable and low-latency communication (URLLC), etc.

[0089] Based on the current mechanism, in order to verify the existence of a valid storage version of a system information block, for a storage version of a SIB, if the storage version of the SIB is associated with an "areaScope" and its value is the same as the "areaScope" value of the SIB received in the system scheduling information (si-SchedulingInfo) of the serving cell, then the terminal device 102 checks whether the system information area identifier and other information in the system scheduling information are consistent with the corresponding information associated with the storage version of the SIB; if the storage version of the SIB does not have an "areaScope" and the system scheduling information of the serving cell does not include the "areaScope" value of the SIB, then the terminal device 102 checks whether the cell identifier and other information are consistent with the corresponding information associated with the storage version of the SIB.

[0090] However, the system information area identifier is optional information, meaning that in some scenarios, network device 101 may not provide this information. For example, after performing cell reselection, terminal device 102 may find that the system scheduling information does not include the system information area identifier; or, when terminal device 102 returns from outside the coverage area, it may find that the system scheduling information does not include the system information area identifier; or, after network device 101 sends an SI modification instruction and updates the system scheduling information, this system scheduling information does not include the system information area identifier.

[0091] In these cases, the following issues may arise for an SIB associated with "areaScope":

[0092] Terminal device 102 cannot determine whether the storage version of the SIB is valid, resulting in uncertainty in the behavior of terminal device 102 and causing testing errors in terminal device 102; or,

[0093] Terminal device 102 might consider all stored versions of the SIB to be invalid, thus requiring terminal device 102 to reacquire the SIB; however, reacquiring the SIB without changing its contents would cause unnecessary power consumption for the terminal device, which is undesirable for energy-efficient terminal devices; or,

[0094] If all other information except the system information area identifier is consistent, the terminal device 102 may consider the associated storage version to be valid. This may result in multiple valid storage versions, making it impossible for the terminal device 102 to determine which version to use or to use an invalid storage version.

[0095] For example, for a System Information Block (SIBx) other than SIB1, SIB6, SIB7, or SIB8, terminal device 102 has a storage version 1 associated with "areaScope," and the corresponding stored information includes Public Land Mobile Network Identifier 1, System Information Area Identifier 1, and Cell Identifier 1; terminal device 102 also has a storage version 2 associated with "areaScope," and the corresponding stored information includes Public Land Mobile Network Identifier 1, System Information Area Identifier 2, and Cell Identifier 2. If the "areaScope" of this SIBx is received in the scheduling information of the serving cell, but the scheduling information does not include the System Information Area Identifier, according to the current mechanism, terminal device 102 may consider an error because it cannot compare the System Information Area Identifier; or, terminal device 102 may consider that neither storage version 1 nor storage version 2 is valid, thus requiring it to reacquire the SIBx; or, terminal device 102 may consider that both storage version 1 and storage version 2 are valid, then it cannot determine which version to use, or it may select storage version 1 (or storage version 2), but in reality, that version is invalid.

[0096] Various embodiments of the present application will now be described with reference to the accompanying drawings. These embodiments are merely exemplary and are not intended to limit the scope of the present application.

[0097] Example 1

[0098] This application provides a method for configuring system information, which is applied to network devices. For example, the method is applied to... Figure 2 Network device 101.

[0099] Figure 3 This is a schematic diagram of a system information configuration method according to Embodiment 1 of this application. Figure 3 As shown, the method includes:

[0100] Step 301: Generate scheduling information (SchedulingInfo) based on the correlation between the system information area identifier (systemInformationAreaID) and the area scope (areaScope); and

[0101] Step 302: Send the scheduling information.

[0102] In this way, network devices generate scheduling information based on the correlation between system information area identifiers and area ranges, which can avoid the situation where area ranges are configured but system information area identifiers are not configured. Therefore, it can avoid the uncertainty of terminal device behavior and reduce the complexity of testing and the overhead of terminal devices.

[0103] In step 301, the network device generates scheduling information based on the correlation between the system information area identifier and the area range. In this embodiment, the scheduling information can also be referred to as system scheduling information (si-SchedulingInfo).

[0104] For example, this scheduling information is included in SIB1.

[0105] In this embodiment of the application, when the scheduling information includes a system information area identifier, 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.

[0106] In the embodiments of this application, when the scheduling information includes a region range, the region range corresponds to a SIB. That is, the scheduling information may include one or more region ranges corresponding to a SIB.

[0107] When the scheduling information includes a region range corresponding to a SIB, it indicates that the SIB supports region specificity, meaning that the SIB is valid in multiple cells within that region. When the scheduling information does not include a region range corresponding to a SIB, it indicates that the SIB does not support region specificity, meaning that the SIB is only valid within the cell that provides the SIB.

[0108] In this embodiment of the application, scheduling information is generated based on the correlation between system information region identifier and region range. For example, the scheduling information may include both system information region identifier and region range, or it may not include both system information region identifier and region range, or it may include system information region identifier but not region range.

[0109] The following is an exemplary description of how to generate scheduling information based on the correlation between system information area identifiers and area ranges.

[0110] Figure 4 This is a schematic diagram of a method for generating scheduling information according to Embodiment 1 of this application. Figure 4 As shown, the method includes:

[0111] Step 401: When the scheduling information includes a system information area identifier, the network device configures the area range for one or more SIBs within the scheduling information, or optionally configures the area range for one or more SIBs within the scheduling information; and

[0112] 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.

[0113] In other words, if the scheduling information includes the system information area identifier, then the network device configures the area range for one or more SIBs within the scheduling information, or optionally configures the area range for one or more SIBs within the scheduling information; otherwise, the area range is not configured.

[0114] In step 401, the network device configuring the area range for one or more SIBs within the scheduling information means that the area range is forcibly configured for one or more SIBs within the scheduling information.

[0115] In the embodiments of this application, the SIB can be at least one of SIB2, SIB3, SIB4 and SIB5. In addition, the SIB can also be at least one of SIB9, SIB10, SIB11, SIB12, SIB13 and SIB14.

[0116] In this embodiment, the necessity encoding condition for the region range field in the scheduling information is as follows: when the scheduling information includes the system information region identifier, the region range field is mandatory to exist; when the scheduling information does not include the system information region identifier, the region range field does not exist. That is, if the scheduling information includes the system information region identifier, then the region range field is mandatory to exist; otherwise, the region range field does not exist.

[0117] Alternatively, the necessity encoding condition for the region range field in the scheduling information is: when the scheduling information includes the system information region identifier, the region range field may optionally exist; when the scheduling information does not include the system information region identifier, the region range field does not exist. In other words, if the scheduling information includes the system information region identifier, then the region range field may optionally exist; otherwise, the region range field does not exist.

[0118] In other words, the area scope domain is conditionally based on the system information area identifier domain (systemInformationAreaID domain). That is, the condition SI-Area-ID can be defined using Table 1 or Table 2 as follows.

[0119] Table 1

[0120]

[0121] Table 2

[0122]

[0123] In this application embodiment, condition SI-Area-ID is just an exemplary name, and other names can also be used, such as condition SIAreaID or condition SI_AID, etc.

[0124] In this way, the network will only configure a region range for one or more SIBs when a system information region identifier is configured, supporting region-specific SIBs. Thus, when a terminal device checks the validity of a SIB's storage version, for an SIB with a configured region range, it will necessarily be able to check whether the system information region identifier in the scheduling information matches the system information region identifier associated with that storage version. Furthermore, this method allows network devices to optionally configure the region range when a system information region identifier is configured, ensuring network configuration flexibility.

[0125] Furthermore, in this method, the network will not configure the area range and does not support area-specific SIBs without configuring a system information area identifier. This saves signaling overhead and conserves spectrum resources.

[0126] Figure 5 This is another schematic diagram of the method for generating scheduling information according to Embodiment 1 of this application. For example... Figure 5 As shown, the method includes:

[0127] Step 501: When the scheduling information includes one or more area ranges configured for a single SIB, the network device configures the system information area identifier within the scheduling information; and

[0128] Step 502: When the scheduling information does not include one or more area ranges configured for a SIB, the network device will optionally configure the system information area identifier within the scheduling information.

[0129] In other words, if the scheduling information includes one or more area ranges configured for a SIB, then the network device will configure the system information area identifier in the scheduling information; otherwise, the network device will optionally configure the system information area identifier in the scheduling information.

[0130] In the embodiments of this application, the SIB can be at least one of SIB2, SIB3, SIB4 and SIB5. In addition, the SIB can also be at least one of SIB9, SIB10, SIB11, SIB12, SIB13 and SIB14.

[0131] In this embodiment, the necessity encoding condition for the system information region identifier field in the scheduling information is as follows: when the scheduling information includes one or more region ranges configured for a SIB, the system information region identifier field is mandatory; and when the scheduling information does not include one or more region ranges configured for a SIB, the system information region identifier field is optional. In other words, if the scheduling information includes one or more region ranges configured for a SIB, then the system information region identifier field is mandatory; otherwise, the system information region identifier field is optional.

[0132] In other words, the system information area identifier field (systemInformationAreaID field) exists conditionally based on the area scope field (areaScope field), that is, the conditional AreaScope can be defined using Table 3 below.

[0133] Table 3

[0134]

[0135] In this application embodiment, conditionAreaScope is just an exemplary name, and other names may also be used, such as conditionArea-Scope or conditionArea_Scope.

[0136] Thus, when a region range is configured for one or more SIBs, meaning region-specific SIBs are supported, the network device must configure a system information region identifier to determine the region of the system information where the serving cell is located. Therefore, when a terminal device checks the validity of a SIB's storage version, for SIBs configured with a region range, it can necessarily check whether the system information region identifier in the scheduling information matches the system information region identifier associated with the storage version.

[0137] In addition, in this method, when no area range is configured, i.e., area-specific SIBs are not supported, the network can optionally configure a system information area identifier, thus ensuring the flexibility of network configuration.

[0138] Figure 6 This is another schematic diagram of the method for generating scheduling information according to Embodiment 1 of this application. For example... Figure 6 As shown, the method includes:

[0139] Step 601: When the scheduling information includes one or more area ranges configured for a single SIB, the network device configures the system information area identifier within the scheduling information; and

[0140] Step 602: When the scheduling information does not include one or more area ranges configured for a SIB, the network device does not configure the system information area identifier in the scheduling information.

[0141] In other words, if the scheduling information includes one or more area ranges configured for a single SIB, then the network device will configure the system information area identifier within the scheduling information; otherwise, the network device will not configure the system information area identifier within the scheduling information.

[0142] In the embodiments of this application, the SIB can be at least one of SIB2, SIB3, SIB4 and SIB5. In addition, the SIB can also be at least one of SIB9, SIB10, SIB11, SIB12, SIB13 and SIB14.

[0143] In this embodiment, the necessity encoding condition for the system information region identifier field in the scheduling information is as follows: when the scheduling information includes one or more region ranges configured for a SIB, the system information region identifier field is mandatory; and when the scheduling information does not include one or more region ranges configured for a SIB, the system information region identifier field does not exist. In other words, if the scheduling information includes one or more region ranges configured for a SIB, then the system information region identifier field is mandatory; otherwise, the system information region identifier field does not exist.

[0144] In other words, the system information area identifier field (systemInformationAreaID field) exists conditionally based on the area scope field (areaScope field), that is, the conditional AreaScope can be defined using Table 4 below.

[0145] Table 4

[0146]

[0147] In this embodiment of the application, ConditionAreaScope is just an exemplary name, and other names may also be used, such as ConditionArea-Scope or ConditionArea_Scope.

[0148] Thus, when a region range is configured for one or more SIBs, meaning region-specific SIBs are supported, the network device must configure a system information region identifier to determine the region of the system information where the serving cell is located. Therefore, when a terminal device checks the validity of a SIB's storage version, for SIBs configured with a region range, it can necessarily check whether the system information region identifier in the scheduling information matches the system information region identifier associated with the storage version.

[0149] In addition, in this embodiment, if no area range is configured, i.e., if area-specific SIBs are not supported, the network device will not configure the system information area identifier, thus saving signaling overhead and spectrum resources.

[0150] After generating the scheduling information in step 301, in step 302, the network device can send the generated scheduling information via broadcast.

[0151] For example, this scheduling information is included in SIB1, see [link / reference]. Figure 1 The network device sends SIB1 in broadcast form.

[0152] As can be seen from the above embodiments, the network device generates scheduling information based on the correlation 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. Therefore, it can avoid the uncertainty of the terminal device behavior and reduce the complexity of testing and the overhead of the terminal device.

[0153] Example 2

[0154] This application provides a method for obtaining system information. This method is applied to a terminal device and corresponds to the system information configuration method for network devices described in Embodiment 1. The same content will not be repeated. For example, this method is applied to... Figure 2 Terminal device 102 in the middle.

[0155] Figure 7 This is a schematic diagram of a system information acquisition method according to Embodiment 2 of this application. Figure 7 As shown, the method includes:

[0156] Step 701: Obtain scheduling information, which is generated based on the association between system information area ID (systemInformationAreaID) and area scope (areaScope).

[0157] In this embodiment, the method for generating the scheduling information can be found in Embodiment 1, and will not be repeated here.

[0158] In this embodiment of the application, the scheduling information may be included in SIB1. For example, SIB1 is sent by the network device in the form of broadcast.

[0159] In the embodiments of this application, such as Figure 7 As shown, the method may further include:

[0160] Step 702: For a SIB, determine whether a valid version of the SIB is stored based on the scheduling information and other information in the system information broadcast by the serving cell.

[0161] In this embodiment of the application, the other information may be included in SIB1.

[0162] In the embodiments of this application, the SIB can be at least one of SIB2, SIB3, SIB4 and SIB5. In addition, the SIB can also be at least one of SIB9, SIB10, SIB11, SIB12, SIB13 and SIB14.

[0163] In step 702, for a stored version of the SIB, if the system information area identifier in the scheduling information, the value tag associated with the SIB, and the public land mobile network identifier (PLMN-Identity) in the other information are the same as the system information area identifier, value tag, and public land mobile network identifier associated with the stored version, the terminal device considers the stored version to be valid.

[0164] Alternatively, for a stored version of the SIB, if the value tag associated with the SIB in the scheduling information and the Public Land Mobile Network Identifier (PLMN-Identity) and cell identifier in the other information are the same as the value tag associated with the stored version, the PLMN-Identity and cell identifier, the terminal device considers the stored version to be valid.

[0165] For example, if the terminal device does not have NPN capability or the serving cell is not an NPN-only cell, then when the system information area identifier in the scheduling information and the value tag associated with the SIB, and the public land mobile network identifier (PLMN-Identity) in the other information are the same as the system information area identifier, value tag, and public land mobile network identifier associated with the storage version, the terminal device considers the storage version to be valid.

[0166] Alternatively, for example, if the terminal device does not have NPN capability or the serving cell is not an NPN-only cell, then the terminal device considers the stored version to be valid when the value tag associated with the SIB in the scheduling information and the Public Land Mobile Network Identifier (PLMN-Identity), cell identifier in the other information are the same as the value tag associated with the stored version, the Public Land Mobile Network Identifier, and the cell identifier.

[0167] In step 702, it is also possible that, for a storage version of the SIB, when the system information region identifier in the scheduling information, the value tag associated with the SIB, and the NPN identifier (NPN-Identity) in the other information are the same as the system information region identifier, value tag, and NPN identifier associated with the storage version, the terminal device considers the storage version to be valid.

[0168] Alternatively, for a storage version of the SIB, if the value tag associated with the SIB in the scheduling information and the NPN identifier and cell identifier in the other information are the same as the value tag, NPN identifier and cell identifier associated with the storage version, the terminal device considers the storage version to be valid.

[0169] For example, if the terminal device has NPN capability and the serving cell is an 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 are the same as the system information area identifier, value tag and NPN identifier associated with the storage version, the terminal device considers the storage version to be valid.

[0170] Alternatively, for example, if the terminal device has NPN capability and the serving cell is an NPN-only cell, then when the value tag associated with the SIB in the scheduling information and the NPN identifier, cell identifier in the other information are the same as the value tag associated with the storage version, the NPN identifier, and the cell identifier, the terminal device considers the storage version to be valid.

[0171] In the embodiments of this application, such as Figure 7 As shown, the method may further include:

[0172] Step 703: When a valid version exists, the terminal device uses that valid version of the SIB; and

[0173] Step 704: When no valid version exists, the terminal device sends a system information request to the network device or obtains the SIB according to the scheduling information.

[0174] As can be seen from the above embodiments, the terminal device can obtain the scheduling information generated by the network device based on the correlation 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. Therefore, it can avoid the uncertainty of the terminal device's behavior and reduce the complexity of testing and the overhead of the terminal device.

[0175] Example 3

[0176] This application provides a method for obtaining system information, which is applied to network devices and terminal devices. It corresponds to the system information configuration method for network devices described in Embodiment 1 and the system information configuration method for terminal devices described in Embodiment 2. The same content will not be described again.

[0177] Figure 8 This is a schematic diagram of a system information acquisition method according to Embodiment 3 of this application. Figure 8 As shown, the method includes:

[0178] Step 801: The network device generates scheduling information based on the correlation between the system information area identifier and the area range;

[0179] Step 802: The network device sends the scheduling information, and the terminal device receives the scheduling information;

[0180] Step 803: The terminal device determines whether it has stored a valid version of the SIB based on the scheduling information and other information in the system information broadcast by the serving cell;

[0181] Step 804: When a valid version exists, the terminal device uses that valid version of the SIB; and

[0182] Step 805: When no valid version exists, the terminal device sends a system information request to the network device or obtains the SIB based on the scheduling information.

[0183] In this embodiment of the application, in 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 already broadcast scheduling information including the SIB, the terminal device does not need to send a system information request again and can directly obtain the SIB based on the scheduling information.

[0184] In the embodiments of this application, Figure 8 The specific implementation of each step can be referred to the descriptions in Embodiments 1 and 2, and will not be repeated here.

[0185] As can be seen from the above embodiments, the network device generates scheduling information based on the correlation 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. Therefore, it can avoid the uncertainty of the terminal device behavior and reduce the complexity of testing and the overhead of the terminal device.

[0186] Example 4

[0187] This application provides a method for obtaining system information, which is applied to a terminal device. For example, the method is applied to... Figure 2 Terminal device 102 in the middle.

[0188] Figure 9 This is a schematic diagram of a system information acquisition method according to Embodiment 4 of this application. Figure 9 As shown, the method includes:

[0189] Step 901: For a storage version of an SIB, when the obtained scheduling information includes the 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 are the same as the system information region identifier and the corresponding information associated with the storage version, the terminal device considers the storage version to be valid.

[0190] In the embodiments of this application, the SIB can be at least one of SIB2, SIB3, SIB4 and SIB5. In addition, the SIB can also be at least one of SIB9, SIB10, SIB11, SIB12, SIB13 and SIB14.

[0191] In this embodiment of the application, if the SIB has multiple storage versions, the validity of each storage version is checked one by one.

[0192] In this embodiment of the application, the first information may include: the first PLMN identifier (PLMN-Identity) received from the serving cell and included in the PLMN identifier information list (PLMN-IdentityInfoList), and the value tag associated with the SIB included in the scheduling information; the corresponding information includes: the PLMN identifier (PLMN-Identity) and the value tag associated with the storage version of the SIB.

[0193] For example, when the terminal device does not have NPN capability or the serving cell is not an NPN-only cell, the first information includes: the first PLMN identifier (PLMN-Identity) received from the serving cell and included in the PLMN-IdentityInfoList, and the value tag associated with the SIB included in the scheduling information; the corresponding information includes: the PLMN identifier (PLMN-Identity) and value tag associated with the storage version of the SIB.

[0194] In this application embodiment, the first information may include: the first NPN identifier received from the serving cell, which includes the first NPN identifier in the NPN-IdentityInfoList and the value tag associated with the SIB included in the scheduling information; the corresponding information includes: the NPN identifier and the value tag associated with the storage version of the SIB.

[0195] For example, when the terminal device has NPN capability and the serving cell is an NPN-only cell, the first information includes: the first NPN identifier received from the serving cell, which includes the first NPN identifier in the NPN-IdentityInfoList and the value tag associated with the SIB included in the scheduling information; the corresponding information includes: the NPN identifier and value tag associated with the storage version of the SIB.

[0196] In the embodiments of this application, such as Figure 9 As shown, the method may further include:

[0197] Step 902: For a storage version of an SIB, if the obtained scheduling information includes the region range corresponding to the SIB, and if the scheduling information does not include the system information region identifier, the terminal device considers the storage version invalid.

[0198] In other words, for a storage version of an SIB, if the obtained scheduling information includes the region range corresponding to the SIB, and the scheduling information includes a system information region identifier and the system information region identifier and the first information are the same as the system information region identifier and the corresponding information associated with the storage version, then the terminal device considers the storage version to be valid; otherwise, the terminal device considers the storage version to be invalid.

[0199] For example, for Rel-15, for the various storage versions of a SIB,

[0200] If the region range is associated, and for that storage version of the SIB, the value of the region range is the same as the value received from the system scheduling information about the SIB from the serving cell.

[0201] If the first PLMN identifier included in the PLMN identifier information list, the system information region identifier (if it exists), and the value label of the SIB included in the system scheduling information received from the serving cell are consistent with the PLMN identifier, system information region identifier, and value label associated with the storage version of the SIB,

[0202] Therefore, the SIB stored in this cell is considered valid.

[0203] For example, for Rel-15, for the various storage versions of an SIB,

[0204] If the region range is associated, and for that storage version of the SIB, the value of the region range is the same as the value received from the system scheduling information for the SIB from the serving cell, and if the system scheduling information includes a system information region identifier,

[0205] If the first PLMN identifier included in the PLMN identifier information list, the system information region identifier, and the value label of the SIB included in the system scheduling information received from the serving cell are consistent with the PLMN identifier, system information region identifier, and value label associated with the storage version of the SIB,

[0206] Therefore, the SIB stored in this cell is considered valid.

[0207] In this method, when a system information area identifier is configured, the terminal device in Rel-15 determines the validity of a storage version of an SIB by checking the system information area identifier, thereby avoiding uncertainty in the behavior of the terminal device, reducing the complexity of testing, and reducing the overhead of the device.

[0208] In addition, in this method, if no system information area identifier is configured, the terminal device considers the storage version invalid, which has little impact on the behavior and standards of the current terminal device and can reduce implementation costs.

[0209] For example, for Rel-16, for the various storage versions of a SIB,

[0210] If the region range is associated, and for that storage version of the SIB, the value of the region range is the same as the value received from the system scheduling information for that SIB from the serving cell.

[0211] If the terminal device has NPN capability and the cell is an NPN-only cell, and the first NPN identifier in the NPN identifier list, the system information region identifier (if present), and the value label of the SIB included in the system scheduling information received from the serving cell are consistent with the NPN identifier, system information region identifier, and value label associated with the storage version of the SIB,

[0212] Therefore, the SIB stored in this cell is considered valid.

[0213] Otherwise, if the first PLMN identifier included in the PLMN identifier information list, the system information region identifier (if it exists), and the value label of the SIB included in the system scheduling information received from the serving cell are consistent with the PLMN identifier, system information region identifier, and value label associated with the storage version of the SIB,

[0214] Therefore, the SIB stored in this cell is considered valid.

[0215] For example, for Rel-16, for the various storage versions of an SIB,

[0216] If the region range is associated, and for that storage version of the SIB, the value of the region range is the same as the value received from the system scheduling information for the SIB from the serving cell, and if the system scheduling information includes a system information region identifier,

[0217] If the terminal device has NPN capability and the cell is an NPN-only cell, and the first NPN identifier in the NPN identifier list, the system information region identifier, and the value label of the SIB included in the system scheduling information received from the serving cell are consistent with the NPN identifier, system information region identifier, and value label associated with the storage version of the SIB,

[0218] Therefore, the SIB stored in this cell is considered valid.

[0219] Otherwise, if the first PLMN identifier included in the PLMN identifier information list, the system information area identifier, and the value tag of the SIB included in the system scheduling information received from the serving cell are consistent with the PLMN identifier, system information area identifier, and value tag associated with the storage version of the SIB,

[0220] Therefore, the SIB stored in this cell is considered valid.

[0221] In this method, when a System Information Region (SIR) identifier is configured, the terminal device in Rel-16 determines the validity of a storage version of an SIB by checking the SIR identifier. This avoids uncertainty in the behavior of the terminal device, reduces testing complexity, and lowers device overhead. The method also considers that the terminal device in Rel-16 has the capability to support Non-Public Networks (NPNs). This allows the terminal device to check the NPN identifier, rather than the PLMN identifier, to determine the validity of a storage version of an SIB, thus avoiding the uncertainty in the terminal device's behavior when network devices do not broadcast the PLMN identifier.

[0222] In addition, in this method, if no system information area identifier is configured, the terminal device considers the storage version invalid, which has little impact on the behavior and standards of the current terminal device and can reduce implementation costs.

[0223] In the embodiments of this application, such as Figure 9 As shown, the method may further include:

[0224] Step 903: When the terminal device deems the storage version valid, it uses the valid version of the SIB; and

[0225] Step 904: When no valid version exists, the terminal device sends a system information request to the network device or obtains the SIB according to the scheduling information.

[0226] Figure 10 This is another schematic diagram of the system information acquisition method in Embodiment 4 of this application. For example... Figure 10 As shown, the method includes:

[0227] Step 1001: For a storage version of an 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 associated with the storage version are the same, the terminal device considers the storage version valid; and

[0228] Step 1002: For a storage version of an SIB, when the obtained scheduling information includes the region range corresponding to the SIB, and when the scheduling information does not include the system information region identifier and the first information is the same as the corresponding information associated with the storage version, the terminal device considers the storage version to be valid.

[0229] In other words, for a storage version of an SIB, if the obtained scheduling information includes the region range corresponding to the SIB, and if the scheduling information includes a system information region identifier and the system information region identifier and the first information are the same as the system information region identifier and the corresponding information associated with the storage version, then the terminal device considers the storage version to be valid; if the scheduling information does not include a system information region identifier but the first information is the same as the corresponding information associated with the storage version, the terminal device also considers the storage version to be valid.

[0230] For example, for Rel-15, for the various storage versions of a SIB,

[0231] If the region range is associated, and for that storage version of the SIB, the value of the region range is the same as the value received from the system scheduling information about the SIB from the serving cell.

[0232] If the first PLMN identifier included in the PLMN identifier information list, the system information region identifier (if it exists), and the value label of the SIB included in the system scheduling information received from the serving cell are consistent with the PLMN identifier, system information region identifier, and value label associated with the storage version of the SIB,

[0233] Therefore, the SIB stored in this cell is considered valid.

[0234] If the region range is associated, and for that storage version of the SIB, the value of the region range is the same as the value received in the system scheduling information about the SIB from the serving cell, and if the system scheduling information does not include a system information region identifier,

[0235] If the first PLMN identifier included in the PLMN identifier information list and the value tag of the SIB included in the system scheduling information received from the serving cell are consistent with the PLMN identifier and value tag associated with the storage version of the SIB,

[0236] Therefore, the SIB stored in this cell is considered valid.

[0237] If the region range does not exist for that storage version of the SIB, and the value of the region range is not included in the system scheduling information about the SIB from the serving cell,

[0238] If the first PLMN identifier, cell identifier, and value tag included in the system scheduling information received from the serving cell for the SIB in the PLMN identifier information list are consistent with the PLMN identifier, cell identifier, and value tag associated with the storage version of the SIB,

[0239] Therefore, the SIB stored in this cell is considered valid.

[0240] For example, for Rel-15, for the various storage versions of an SIB,

[0241] If the region is associated, and for that storage version of the SIB, the value of the region is the same as the value received in the system scheduling information about the SIB from the serving cell, and if the system scheduling information includes a system information region identifier,

[0242] If the first PLMN identifier included in the PLMN identifier information list, the system information region identifier, and the value label of the SIB included in the system scheduling information received from the serving cell are consistent with the PLMN identifier, system information region identifier, and value label associated with the storage version of the SIB,

[0243] Therefore, the SIB stored in this cell is considered valid.

[0244] If the region range is associated, and for that storage version of the SIB, the value of the region range is the same as the value received in the system scheduling information about the SIB from the serving cell, and if the system scheduling information does not include a system information region identifier,

[0245] If the first PLMN identifier included in the PLMN identifier information list and the value tag of the SIB included in the system scheduling information received from the serving cell are consistent with the PLMN identifier and value tag associated with the storage version of the SIB,

[0246] Therefore, the SIB stored in this cell is considered valid.

[0247] If the region range does not exist for that storage version of the SIB, and the value of the region range is not included in the system scheduling information about the SIB from the serving cell,

[0248] If the first PLMN identifier, cell identifier, and value tag included in the system scheduling information received from the serving cell for the SIB in the PLMN identifier information list are consistent with the PLMN identifier, cell identifier, and value tag associated with the storage version of the SIB,

[0249] Therefore, the SIB stored in this cell is considered valid.

[0250] For example, for Rel-16, for the various storage versions of a SIB,

[0251] If the region range is associated, and for that storage version of the SIB, the value of the region range is the same as the value received from the system scheduling information for that SIB from the serving cell.

[0252] If the terminal device has NPN capability and the cell is an NPN-only cell, and the first NPN identifier in the NPN identifier list, the system information region identifier (if present), and the value label of the SIB included in the system scheduling information received from the serving cell are consistent with the NPN identifier, system information region identifier, and value label associated with the storage version of the SIB,

[0253] Therefore, the SIB stored in this cell is considered valid.

[0254] Otherwise, if the first PLMN identifier included in the PLMN identifier information list, the system information region identifier (if it exists), and the value label of the SIB included in the system scheduling information received from the serving cell are consistent with the PLMN identifier, system information region identifier, and value label associated with the storage version of the SIB,

[0255] Therefore, the SIB stored in this cell is considered valid.

[0256] If the region range is associated, and for that storage version of the SIB, the value of the region range is the same as the value received from the system scheduling information about the SIB from the serving cell, and if the system scheduling information does not include a system information region identifier,

[0257] If 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 label of the SIB included in the system scheduling information received from the serving cell are consistent with the NPN identifier and value label associated with the storage version of the SIB,

[0258] Therefore, the SIB stored in this cell is considered valid.

[0259] If the region range does not exist for that storage version of the SIB, and the value of the region range is not included in the system scheduling information about the SIB from the serving cell,

[0260] If the terminal device has NPN capability and the cell is an NPN-only cell, and the first NPN identifier in the NPN identifier list, the cell identifier, and the value label of the SIB included in the system scheduling information received from the serving cell are consistent with the NPN identifier, cell identifier, and value label associated with the storage version of the SIB,

[0261] Therefore, the SIB stored in this cell is considered valid.

[0262] For example, for Rel-16, for the various storage versions of an SIB,

[0263] If the region range is associated, and for that storage version of the SIB, the value of the region range is the same as the value received from the system scheduling information for the SIB from the serving cell, and if the system scheduling information includes a system information region identifier,

[0264] If the terminal device has NPN capability and the cell is an NPN-only cell, and the first NPN identifier in the NPN identifier list, the system information region identifier, and the value label of the SIB included in the system scheduling information received from the serving cell are consistent with the NPN identifier, system information region identifier, and value label associated with the storage version of the SIB,

[0265] Therefore, the SIB stored in this cell is considered valid.

[0266] Otherwise, if the first PLMN identifier included in the PLMN identifier information list, the system information area identifier, and the value tag of the SIB included in the system scheduling information received from the serving cell are consistent with the PLMN identifier, system information area identifier, and value tag associated with the storage version of the SIB,

[0267] Therefore, the SIB stored in this cell is considered valid.

[0268] If the region range is associated, and for that storage version of the SIB, the value of the region range is the same as the value received from the system scheduling information about the SIB from the serving cell, and if the system scheduling information does not include a system information region identifier,

[0269] If 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 label of the SIB included in the system scheduling information received from the serving cell are consistent with the NPN identifier and value label associated with the storage version of the SIB,

[0270] Therefore, the SIB stored in this cell is considered valid.

[0271] If the region range does not exist for that storage version of the SIB, and the value of the region range is not included in the system scheduling information about the SIB from the serving cell,

[0272] If the terminal device has NPN capability and the cell is an NPN-only cell, and the first NPN identifier in the NPN identifier list, the cell identifier, and the value label of the SIB included in the system scheduling information received from the serving cell are consistent with the NPN identifier, cell identifier, and value label associated with the storage version of the SIB,

[0273] Therefore, the SIB stored in this cell is considered valid.

[0274] In the embodiments of this application, such as Figure 10 As shown, the method may further include:

[0275] Step 1003: When the terminal device deems the storage version valid, it uses the valid version of the SIB; and

[0276] Step 1004: When no valid version exists, the terminal device sends a system information request to the network device or obtains the SIB according to the scheduling information.

[0277] Figure 11 This is another schematic diagram of the system information acquisition method in Embodiment 4 of this application. For example... Figure 11 As shown, the method includes:

[0278] Step 1101: For a storage version of an 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 associated with the storage version are the same, the terminal device considers the storage version valid; and

[0279] Step 1102: For a 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 and the first information and cell identifier are the same as the corresponding information and cell identifier associated with the storage version, the terminal device considers the storage version to be valid.

[0280] In other words, for a storage version of an SIB, if the obtained scheduling information includes the 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 the same as the system information area identifier and the corresponding information associated with the storage version, then the terminal device considers the storage version to be valid; if the scheduling information does not include a system information area identifier but the first information and the cell identifier are the same as the corresponding information and the cell identifier associated with the storage version, the terminal device also considers the storage version to be valid.

[0281] For example, for Rel-15, for the various storage versions of a SIB,

[0282] If the region range is associated, and for that storage version of the SIB, the value of the region range is the same as the value received from the system scheduling information about the SIB from the serving cell.

[0283] If the first PLMN identifier included in the PLMN identifier information list, the system information region identifier (if it exists), and the value label of the SIB included in the system scheduling information received from the serving cell are consistent with the PLMN identifier, system information region identifier, and value label associated with the storage version of the SIB,

[0284] Therefore, the SIB stored in this cell is considered valid.

[0285] If the region range is associated, and for that storage version of the SIB, the value of the region range is the same as the value received in the system scheduling information about the SIB from the serving cell, and if the system scheduling information does not include a system information region identifier, or...

[0286] If the region range does not exist for that storage version of the SIB, and the value of the region range is not included in the system scheduling information about the SIB from the serving cell,

[0287] If the first PLMN identifier, cell identifier, and value tag of the SIB included in the PLMN identifier information list, as well as the system scheduling information received from the serving cell, are consistent with the PLMN identifier, cell identifier, and value tag associated with the storage version of the SIB,

[0288] Therefore, the SIB stored in this cell is considered valid.

[0289] For example, for Rel-15, for the various storage versions of an SIB,

[0290] If the region is associated, and for that storage version of the SIB, the value of the region is the same as the value received in the system scheduling information about the SIB from the serving cell, and if the system scheduling information includes a system information region identifier,

[0291] If the first PLMN identifier included in the PLMN identifier information list, the system information region identifier, and the value label of the SIB included in the system scheduling information received from the serving cell are consistent with the PLMN identifier, system information region identifier, and value label associated with the storage version of the SIB,

[0292] Therefore, the SIB stored in this cell is considered valid.

[0293] If the region range is associated, and for that storage version of the SIB, the value of the region range is the same as the value received in the system scheduling information about the SIB from the serving cell, and if the system scheduling information does not include a system information region identifier, or...

[0294] If the region range does not exist for that storage version of the SIB, and the value of the region range is not included in the system scheduling information about the SIB from the serving cell,

[0295] If the first PLMN identifier, cell identifier, and value tag of the SIB included in the PLMN identifier information list, as well as the system scheduling information received from the serving cell, are consistent with the PLMN identifier, cell identifier, and value tag associated with the storage version of the SIB,

[0296] Therefore, the SIB stored in this cell is considered valid.

[0297] In this method, when a system information area identifier is configured, the terminal device in Rel-15 determines the validity of a storage version of an SIB by checking the system information area identifier, thereby avoiding uncertainty in the behavior of the terminal device, reducing the complexity of testing, and reducing the overhead of the device.

[0298] Furthermore, in this method, without a configured system information area identifier, the terminal device needs to check the cell identifier to determine the validity of the stored version. Thus, if the cell identifier remains the same, i.e., the SIB remains unchanged, the terminal device does not need to reacquire the SIB, reducing terminal power consumption.

[0299] For example, for Rel-16, for the various storage versions of a SIB,

[0300] If the region range is associated, and for that storage version of the SIB, the value of the region range is the same as the value received from the system scheduling information for that SIB from the serving cell.

[0301] If the terminal device has NPN capability and the cell is an NPN-only cell, and the first NPN identifier in the NPN identifier list, the system information region identifier (if present), and the value label of the SIB included in the system scheduling information received from the serving cell are consistent with the NPN identifier, system information region identifier, and value label associated with the storage version of the SIB,

[0302] Therefore, the SIB stored in this cell is considered valid.

[0303] Otherwise, if the first PLMN identifier included in the PLMN identifier information list, the system information region identifier (if it exists), and the value label of the SIB included in the system scheduling information received from the serving cell are consistent with the PLMN identifier, system information region identifier, and value label associated with the storage version of the SIB,

[0304] Therefore, the SIB stored in this cell is considered valid.

[0305] If the region range is associated, and for that storage version of the SIB, the value of the region range is the same as the value received in the system scheduling information about the SIB from the serving cell, and if the system scheduling information does not include a system information region identifier, or...

[0306] If the region range does not exist for that storage version of the SIB, and the value of the region range is not included in the system scheduling information about the SIB from the serving cell,

[0307] If the terminal device has NPN capability and the cell is an NPN-only cell, and the first NPN identifier, cell identifier, and value tag included in the NPN identifier information list, as well as the system scheduling information received from the serving cell for the SIB, are consistent with the NPN identifier, cell identifier, and value tag associated with the storage version of the SIB, then...

[0308] Therefore, the SIB stored in this cell is considered valid.

[0309] For example, for Rel-16, for the various storage versions of an SIB,

[0310] If the region range is associated, and for that storage version of the SIB, the value of the region range is the same as the value received from the system scheduling information for the SIB from the serving cell, and if the system scheduling information includes a system information region identifier,

[0311] If the terminal device has NPN capability and the cell is an NPN-only cell, and the first NPN identifier in the NPN identifier list, the system information region identifier, and the value label of the SIB included in the system scheduling information received from the serving cell are consistent with the NPN identifier, system information region identifier, and value label associated with the storage version of the SIB,

[0312] Therefore, the SIB stored in this cell is considered valid.

[0313] Otherwise, if the first PLMN identifier included in the PLMN identifier information list, the system information area identifier, and the value tag of the SIB included in the system scheduling information received from the serving cell are consistent with the PLMN identifier, system information area identifier, and value tag associated with the storage version of the SIB,

[0314] Therefore, the SIB stored in this cell is considered valid.

[0315] If the region range is associated, and for that storage version of the SIB, the value of the region range is the same as the value received in the system scheduling information about the SIB from the serving cell, and if the system scheduling information does not include a system information region identifier, or...

[0316] If the region range does not exist for that storage version of the SIB, and the value of the region range is not included in the system scheduling information about the SIB from the serving cell,

[0317] If the terminal device has NPN capability and the cell is an NPN-only cell, and the first NPN identifier included in the NPN identifier information list, the cell identifier included in the system scheduling information received from the serving cell for the SIB, and the value label are consistent with the NPN identifier, cell identifier, and value label associated with the storage version of the SIB,

[0318] Therefore, the SIB stored in this cell is considered valid.

[0319] In this method, when a System Information Region (SIR) identifier is configured, the terminal device in Rel-16 determines the validity of a storage version of an SIB by checking the SIR identifier. This avoids uncertainty in the behavior of the terminal device, reduces testing complexity, and lowers device overhead. The method also considers that the terminal device in Rel-16 may have the capability to support Non-Public Networks (NPNs). In this case, the terminal device can check the NPN identifier, rather than the PLMN identifier, to determine the validity of a storage version of an SIB, thereby avoiding the uncertainty in the behavior of the terminal device when the network device does not broadcast the PLMN identifier.

[0320] Furthermore, in this method, without a configured system information area identifier, the terminal device needs to check the cell identifier to determine the validity of the stored version. Thus, if the cell identifier remains the same, i.e., the SIB remains unchanged, the terminal does not need to reacquire the SIB, reducing the terminal device's power consumption.

[0321] In the embodiments of this application, such as Figure 11 As shown, the method may further include:

[0322] Step 1103: When the terminal device deems the storage version valid, it uses the valid version of the SIB; and

[0323] Step 1104: When no valid version exists, the terminal device sends a system information request to the network device or obtains the SIB according to the scheduling information.

[0324] As can be seen from the above embodiments, when checking the validity of a SIB's storage version, the terminal device's behavior is specified for both configured and unconfigured system information area identifiers. Therefore, uncertainty in the terminal device's behavior can be avoided, and the complexity of testing and the overhead of the terminal device can be reduced.

[0325] Example 5

[0326] This application provides a method for configuring system information, which is applied to network devices. For example, the method is applied to... Figure 2 Network device 101.

[0327] Figure 12 This is a schematic diagram of a system information configuration method according to Embodiment 5 of this application. Figure 12 As shown, the method includes:

[0328] Step 1201: For terminal device-specific parameters, when the conditions include the serving cell configuring supplementary uplink, the network device considers the terminal device's capabilities; or, for both terminal device-specific and cell-specific parameters, when the conditions include the serving cell configuring supplementary uplink, the network device does not consider the terminal device's capabilities or only considers that the network device provides SUL configuration for the terminal device.

[0329] In this application embodiment, for example, the network device considers the capabilities of the terminal device, including:

[0330] Based on the capabilities of the terminal device, the network device determines that the terminal device can support the SUL frequency band provided in the SUL configuration; or,

[0331] The network device provides SUL configuration for the terminal device, 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.

[0332] In this application embodiment, for example, the network device considers the capabilities of the terminal device, including:

[0333] The presence of a supplementary uplink in the public cell configuration (servingCellConfigCommon) indicates that the network device provides SUL configuration for the terminal device.

[0334] In the embodiments of this application, for example, the terminal device-specific parameters are tpc-Index and / or tpc-IndexSUL.

[0335] In the embodiments of this application, for example, the parameter specific to the terminal device is information, IE, or domain.

[0336] For example, the terminal device-specific parameter can also be terminal device-specific information, terminal device-specific IE, or terminal device-specific domain.

[0337] In step 1201, for example, when the condition includes that the serving cell is configured with supplementary uplink, the capabilities of the terminal device are not considered, or only the network device is considered to provide SUL configuration for the terminal device, including: when the first configuration information common to the cell includes supplementary uplink configuration, the configuration for sending system information messages on supplementary uplink (si-RequestConfigSUL) can be optionally provided in the scheduling information.

[0338] In other words, if the primary configuration information of the community includes supplementary uplink configuration, then the scheduling information may optionally provide supplementary uplink configuration for sending system information messages.

[0339] In this embodiment of the application, the first configuration information may be the serving cell common configuration (servingCellConfigCommon).

[0340] In step 1201, for example, when there is a supplementary uplink in the serving cell common configuration (servingCellConfigCommon) and when the system information broadcast status (e.g., si-BroadcastStatus, posSI-BroadcastStatus) of any system information message (SI-message) in the scheduling information (SchedulingInfo) is set to non-broadcast, the scheduling information may optionally provide the configuration for sending system information messages on the supplementary uplink (e.g., si-RequestConfigSUL, posSI-RequestConfigSUL-r16).

[0341] In other words, if a supplementary uplink exists in the public cell configuration (servingCellConfigCommon) and the system information broadcast status (e.g., si-BroadcastStatus, posSI-BroadcastStatus) of any system information message (SI-message) in the scheduling information (SchedulingInfo) is set to "not broadcasting", the configuration for sending system information messages on the supplementary uplink (e.g., si-RequestConfigSUL, posSI-RequestConfigSUL-r16) may be present; otherwise, si-RequestConfigSUL or posSI-RequestConfigSUL-r16 is missing.

[0342] In this embodiment, the configuration for sending system information messages on the supplementary uplink exists under the following conditions: when a supplementary uplink exists in the serving cell common configuration (servingCellConfigCommon) and the system information broadcast status (e.g., si-BroadcastStatus, posSI-BroadcastStatus) of any system information message (SI-message) in the scheduling information (SchedulingInfo) is set to non-broadcast, the configuration for sending system information messages on the supplementary uplink is optional; otherwise, the configuration for sending system information messages on the supplementary uplink is missing.

[0343] For example, the existence condition SUL-MSG-1 of si-RequestConfigSUL can be defined using Table 5 below.

[0344] Table 5

[0345]

[0346] In this application embodiment, condition SUL-MSG-1 is just an exemplary name, and other names can also be used, such as condition SUL-MSG1, condition SUL-SI-Request, etc.

[0347] For example, the existence condition SUL-MSG-1 of posSI-RequestConfigSUL-r16 can be defined using Table 6 below.

[0348] Table 6

[0349]

[0350] For example, the existence condition SUL of tpc-Index can be defined using Table 7 below.

[0351] Table 7

[0352]

[0353] For example, the existence condition SUL of tpc-Index can be defined using Table 8 below.

[0354] Table 8

[0355]

[0356] In this embodiment, the names used for the above conditions are merely exemplary names, and other names may also be used. This embodiment does not limit the form and format of these names. In this embodiment, the scheduling information is also referred to as system scheduling information, which may be included in SIB1.

[0357] As can be seen from the above embodiments, for terminal device-specific parameters, when the condition includes the serving cell configuring supplementary uplink, the terminal device's capabilities are considered; or, for both terminal device-specific and cell-specific parameters, when the condition includes the serving cell configuring supplementary uplink, the terminal device's capabilities are not considered, or only the network device providing SUL configuration for the terminal device is considered. In this way, the network device can clearly understand the contents of SI81, avoiding uncertainties in network device implementation, reducing the testing costs of network device products, and thus saving network deployment costs.

[0358] Example 6

[0359] This application provides a system information configuration device, which is applied to a network device. Since the principle by which this device solves the problem is similar to the method in Embodiment 1, its specific implementation can refer to the implementation of the method described in Embodiment 1. The same or related aspects will not be repeated.

[0360] Figure 13 This is a schematic diagram of a system information configuration device according to Embodiment 6 of this application, as shown below. Figure 13 As shown, the device 1300 includes:

[0361] Generation unit 1301 generates scheduling information (SchedulingInfo) based on the correlation between system information area identifier (systemInformationAreaID) and area scope (areaScope); and

[0362] The sending unit 1302 sends the scheduling information.

[0363] In this embodiment of the application, when the scheduling information includes the system information region identifier, the generation unit 1301 forcibly or optionally configures the region range for one or more SIBs within the scheduling information; when the scheduling information does not include the system information region identifier, it does not configure the region range within the scheduling information.

[0364] In this embodiment of the application, the necessity encoding condition for the region range field in the scheduling information is as follows: when the scheduling information includes the system information region identifier, the region range field is mandatory; when the scheduling information does not include the system information region identifier, the region range field does not exist; or, when the scheduling information includes the system information region identifier, the region range field may exist optionally; when the scheduling information does not include the system information region identifier, the region range field does not exist.

[0365] In this embodiment of the application, the generation unit 1301 may configure the system information region identifier in the scheduling information when the scheduling information includes one or more regions configured for a SIB; or, when the scheduling information does not include one or more regions configured for a SIB, optionally configure the system information region identifier in the scheduling information, or not configure the system information region identifier in the scheduling information.

[0366] In this embodiment of the application, the necessity encoding condition for the system information region identifier field in the scheduling information is as follows: when the scheduling information includes one or more region ranges configured for a SIB, the system information region identifier field is mandatory to exist; and when the scheduling information does not include one or more region ranges configured for a SIB, the system information region identifier field is optional to exist.

[0367] Alternatively, the necessity encoding condition for the system information region identifier field in the scheduling information is as follows: when the scheduling information includes one or more region ranges configured for a SIB, the system information region identifier field is mandatory to exist; and when the scheduling information does not include one or more region ranges configured for a SIB, the system information region identifier field does not exist.

[0368] In this embodiment of the application, the scheduling information may include the system information area identifier and the area range.

[0369] In this embodiment of the application, the scheduling information can be sent via broadcast.

[0370] In this embodiment of the application, the scheduling information may be included in SIB1.

[0371] In this embodiment, the functions of each of the above units can be implemented with reference to the relevant steps in Embodiment 1, and will not be repeated here.

[0372] As can be seen from the above embodiments, the network device generates scheduling information based on the correlation 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. Therefore, it can avoid the uncertainty of the terminal device behavior and reduce the complexity of testing and the overhead of the terminal device.

[0373] Example 7

[0374] This application provides a system information acquisition device, which is applied to a terminal device. Since the principle by which this device solves the problem is similar to the method in Embodiment 2, its specific implementation can refer to the implementation of the method described in Embodiment 2. The same or related parts will not be repeated.

[0375] Figure 14 This is a schematic diagram of a system information acquisition device according to Embodiment 7 of this application, as shown below. Figure 14 As shown, the device 1400 includes:

[0376] The first acquisition unit 1401 acquires scheduling information, which is generated based on the association between the system information area identifier (systemInformationAreaID) and the area scope (areaScope).

[0377] In the embodiments of this application, such as Figure 14 As shown, the device 1400 also includes:

[0378] The first determining unit 1402 determines, for a given SIB, whether a valid version of the SIB is stored based on the scheduling information and other information in the system information broadcast by the serving cell.

[0379] Figure 15 This is a schematic diagram of the first determining unit in Embodiment 7 of this application, as shown below. Figure 15 As shown, the first determining unit 1402 includes:

[0380] The second determining unit 1501, for a stored version of the SIB, considers the stored version valid when the system information area identifier and the value tag associated with the SIB in the scheduling information, and the public land mobile network identifier (PLMN-Identity) in the other information, are the same as the system information area identifier, value tag, and public land mobile network identifier associated with the stored version; or, for a stored version of the SIB, considers the stored version valid when the value tag associated with the SIB in the scheduling information, and the public land mobile network identifier (PLMN-Identity) and cell identifier in the other information, are the same as the value tag, public land mobile network identifier, cell identifier (cellIdentity), and cell identifier associated with the stored version; or,

[0381] The third determining unit 1502, for a storage version of the SIB, considers the storage version valid when the system information region identifier in the scheduling information and the value tag associated with the SIB, the NPN identifier (NPN-Identity) in the other information and the cell identifier are the same as the system information region identifier, value tag, NPN identifier and cell identifier associated with the storage version; or, for a storage version of the SIB, the terminal device considers the storage version valid when the value tag associated with the SIB in the scheduling information and the NPN identifier (NPN-Identity) in the other information and the cell identifier are the same as the value tag, NPN identifier and cell identifier associated with the storage version.

[0382] In the embodiments of this application, such as Figure 14 As shown, the device 1400 also includes:

[0383] The first user unit 1403, when a valid version exists, uses the valid version of the SIB; and

[0384] The second acquisition unit 1404, when no valid version exists, sends a system information request to the network device or acquires the SIB according to the scheduling information.

[0385] In this embodiment of the application, the scheduling information may include the system information area identifier and the area range.

[0386] In the embodiments of this application, the SIB can be at least one of SIB2, SIB3, SIB4 and SIB5. In addition, the SIB can also be at least one of SIB9, SIB10, SIB11, SIB12, SIB13 and SIB14.

[0387] In this embodiment of the application, the scheduling information may be included in SIB1.

[0388] In this embodiment, the functions of each of the above units can be implemented with reference to the relevant steps in Embodiment 2, and will not be repeated here.

[0389] As can be seen from the above embodiments, the terminal device can obtain the scheduling information generated by the network device based on the correlation 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. Therefore, it can avoid the uncertainty of the terminal device's behavior and reduce the complexity of testing and the overhead of the terminal device.

[0390] Example 8

[0391] This application provides a system information acquisition device, which is applied to a terminal device. Since the principle by which this device solves the problem is similar to the method in Embodiment 4, its specific implementation can refer to the implementation of the method described in Embodiment 4. The same or related parts will not be repeated.

[0392] Figure 16 This is a schematic diagram of a system information acquisition device according to Embodiment 8 of this application, as shown below. Figure 16 As shown, the device 1600 includes:

[0393] The fourth determining unit 1601, for a storage version of an SIB, considers the storage version to be valid when the obtained scheduling information includes the area scope corresponding to the SIB, and when the scheduling information includes the system information area ID and the system information area ID and the corresponding information associated with the first information are the same.

[0394] In the embodiments of this application, such as Figure 16 As shown, the device 1600 may further include:

[0395] The fifth determining unit 1602, for a storage version of an SIB, considers the storage version invalid when the obtained scheduling information includes the region range corresponding to the SIB, and when the scheduling information does not include the system information region identifier.

[0396] In the embodiments of this application, such as Figure 16 As shown, the device 1600 may further include:

[0397] The sixth determining unit 1603, for a storage version of an SIB, considers the storage version to be valid when the obtained scheduling information includes the region range corresponding to the SIB, and when the scheduling information does not include the system information region identifier and the first information is the same as the corresponding information associated with the storage version.

[0398] In the embodiments of this application, such as Figure 16 As shown, the device 1600 may further include:

[0399] The seventh determining unit 1604, for a storage version of an SIB, considers the storage version to be valid when the obtained scheduling information includes the area scope corresponding to the SIB, and when the scheduling information does not include the system information area identifier but the first information and cell identifier are the same as the corresponding information and cell identifier associated with the storage version.

[0400] In this embodiment of the application, the first information may include: the first PLMN identifier (PLMN-Identity) received from the serving cell and included in the PLMN identifier information list (PLMN-IdentityInfoList), and the value tag associated with the SIB included in the scheduling information;

[0401] The relevant information may include: the PLMN identity associated with the storage version of the SIB and the value label.

[0402] For example, when the terminal device does not have NPN capability or the serving cell is not an NPN-only cell, the first information includes: the first PLMN identifier (PLMN-Identity) received from the serving cell and included in the PLMN-IdentityInfoList, and the value tag associated with the SIB included in the scheduling information; the corresponding information includes: the PLMN identifier (PLMN-Identity) and value tag associated with the storage version of the SIB.

[0403] In this application embodiment, the first information may include: the first NPN identifier received from the serving cell, which includes the first NPN identifier in the NPN-IdentityInfoList and the value tag associated with the SIB included in the scheduling information; the corresponding information includes: the NPN identifier and the value tag associated with the storage version of the SIB.

[0404] For example, when the terminal device has NPN capability and the serving cell is an NPN-only cell, the first information includes: the first NPN identifier received from the serving cell, which includes the first NPN identifier in the NPN-IdentityInfoList and the value tag associated with the SIB included in the scheduling information; the corresponding information includes: the NPN identifier and value tag associated with the storage version of the SIB.

[0405] In the embodiments of this application, such as Figure 16 As shown, the device 1600 may further include:

[0406] The second usage unit 1605, when the terminal device deems the storage version valid, uses the valid version of the SIB; and

[0407] The third acquisition unit 1606, when no valid version exists, the terminal device sends a system information request to the network device or acquires the SIB according to the scheduling information.

[0408] In this embodiment, the functions of each of the above units can be implemented with reference to the relevant steps in Embodiment 4, and will not be repeated here.

[0409] As can be seen from the above embodiments, the terminal device can obtain the scheduling information generated by the network device based on the correlation 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. Therefore, it can avoid the uncertainty of the terminal device's behavior and reduce the complexity of testing and the overhead of the terminal device.

[0410] Example 9

[0411] This application provides a system information configuration device applied to a network device. Since the principle by which this device solves the problem is similar to the method in Embodiment 5, its specific implementation can refer to the implementation of the method described in Embodiment 5; the same or related parts will not be repeated.

[0412] Figure 17 This is a schematic diagram of a system information acquisition device according to Embodiment 9 of this application, as shown below. Figure 17 As shown, the device 1700 includes:

[0413] Configuration unit 1701, for terminal device-specific parameters, when the conditions include the serving cell configuring supplementary uplink, considers the capabilities of the terminal device; or, for terminal device-specific parameters and cell-specific parameters, when the conditions include the serving cell configuring supplementary uplink, it does not consider the capabilities of the terminal device or only considers that the network device provides SUL configuration for the terminal device.

[0414] In this embodiment of the application, the network device takes into account the capabilities of the terminal device, including:

[0415] Based on the capabilities of the terminal device, the network device determines that the terminal device can support the SUL frequency band provided in the SUL configuration; or,

[0416] The network device provides SUL configuration for the terminal device, 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.

[0417] In this embodiment of the application, the network device takes into account the capabilities of the terminal device, including:

[0418] The presence of a supplementary uplink in the public cell configuration (servingCellConfigCommon) indicates that the network device provides SUL configuration for the terminal device.

[0419] In the embodiments of this application, for example, the terminal device-specific parameters are tpc-Index and / or tpc-IndexSUL.

[0420] In this embodiment of the application, the parameter specific to the terminal device is either information, IE, or domain.

[0421] For example, the terminal device-specific parameter can also be terminal device-specific information, terminal device-specific IE, or terminal device-specific domain.

[0422] In this application embodiment, for example, when the condition includes that the serving cell is configured with supplementary uplink, the capability of the terminal device is not considered or only the network device provides SUL configuration for the terminal device is considered, including: when the first configuration information common to the cell includes supplementary uplink configuration, the configuration for sending system information messages on supplementary uplink (e.g., si-RequestConfigSUL, posSI-RequestConfigSUL-r16) can be optionally provided in the scheduling information.

[0423] In this embodiment of the application, the first configuration information may be the serving cell common configuration (servingCellConfigCommon).

[0424] In this embodiment of the application, when there is a supplementary uplink in the serving cell common configuration (servingCellConfigCommon) and the system information broadcast status (e.g., si-BroadcastStatus, posSI-BroadcastStatus) of any system information message (SI-message) in the scheduling information (SchedulingInfo) is set to not broadcast, the configuration unit 1701 may optionally provide the configuration for sending system information messages on the supplementary uplink (e.g., si-RequestConfigSUL, posSI-RequestConfigSUL-r16) in the scheduling information.

[0425] In this embodiment of the application, the existence condition for the supplementary uplink configuration for sending system information messages is as follows:

[0426] When a supplementary uplink exists in the serving cell configuration (servingCellConfigCommon) and the system information broadcast status (e.g., si-BroadcastStatus, posSI-BroadcastStatus) of any system information message (SI-message) in the scheduling information (SchedulingInfo) is set to non-broadcast, the configuration for sending system information messages on the supplementary uplink is optional; otherwise, the configuration for sending system information messages on the supplementary uplink is empty.

[0427] In this embodiment of the application, the scheduling information may be included in SIB1.

[0428] In this embodiment, the functions of each of the above units can be implemented with reference to the relevant steps in Embodiment 5, and will not be repeated here.

[0429] As can be seen from the above embodiments, for terminal device-specific parameters, when the condition includes the serving cell configuring supplementary uplink, the terminal device's capabilities are considered. Alternatively, for both terminal device-specific and cell-specific parameters, when the condition includes the serving cell configuring supplementary uplink, the terminal device's capabilities are not considered, or only the network device providing SUL configuration for the terminal device is considered. In this way, the network device can clearly understand the contents of SIB1, avoiding uncertainties in network device implementation, reducing the testing costs of network device products, and thus saving network deployment costs.

[0430] Example 10

[0431] This application provides a network device that includes a system information configuration device as described in Embodiment 6.

[0432] Figure 18 This is a schematic block diagram of the system configuration of the network device in Embodiment 10 of this application. Figure 18 As shown, 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 types of data; it also stores an information processing program 1830, which is executed under the control of the processor 1810 to receive and send various types of information to terminal devices.

[0433] In one embodiment, the functionality of the system information configuration device can be integrated into the processor 1810. The processor 1810 can be configured to: generate scheduling information (SchedulingInfo) based on the correlation between the system information area identifier (systemInformationAreaID) and the area scope (areaScope); and send the scheduling information.

[0434] For example, the generation of scheduling information based on the correlation between system information area identifier and area range includes: when the scheduling information includes the system information area identifier, the network device configures the area range for one or more SIBs within the scheduling information, or optionally configures the area range for one or more SIBs within the scheduling information.

[0435] For example, the generation of scheduling information based on the correlation between system information area identifier and area range also includes: 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.

[0436] For example, the necessity encoding condition for the region range field in the scheduling information is as follows: when the scheduling information includes the system information region identifier, the region range field is mandatory to exist; when the scheduling information does not include the system information region identifier, the region range field does not exist; or, when the scheduling information includes the system information region identifier, the region range field is optional to exist; when the scheduling information does not include the system information region identifier, the region range field does not exist.

[0437] For example, the generation of scheduling information based on the correlation between system information area identifier and area range includes: when the scheduling information includes one or more area ranges configured for a SIB, the network device configures the system information area identifier within the scheduling information.

[0438] For example, the generation of scheduling information based on the correlation between system information area identifier and area range also includes: when the scheduling information does not include one or more area ranges configured for a SIB, the network device may optionally configure the system information area identifier in the scheduling information, or the network device may not configure the system information area identifier in the scheduling information.

[0439] For example, the necessity coding condition for the system information area identifier field in the scheduling information is: when the scheduling information includes one or more area ranges configured for a SIB, the system information area identifier field is mandatory; and when the scheduling information does not include one or more area ranges configured for a S1B, the system information area identifier field is optional.

[0440] For example, the necessity encoding condition for the system information area identifier field in the scheduling information is: when the scheduling information includes one or more area ranges configured for a SIB, the system information area identifier field 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 identifier field does not exist.

[0441] For example, the scheduling information includes the system information area identifier and the area range.

[0442] For example, the scheduling information is sent via broadcast.

[0443] For example, this scheduling information is included in SIB1.

[0444] In another embodiment, the system information configuration device can be configured separately from the processor 1810. For example, the system information configuration device can be configured as a chip connected to the processor 1810, and the function of the system information configuration device can be realized through the control of the processor 1810.

[0445] In addition, such as Figure 18 As shown, network device 1800 may also include: transceiver 1840 and antenna 1850, etc.; the functions of the above components are similar to those in the prior art, and will not be described in detail here. It is worth noting that network device 1800 is not necessarily required to include... Figure 18 All components shown; in addition, network device 1800 may also include Figure 18 For components not shown, please refer to existing technology.

[0446] As can be seen from the above embodiments, the network device generates scheduling information based on the correlation 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. Therefore, it can avoid the uncertainty of the terminal device behavior and reduce the complexity of testing and the overhead of the terminal device.

[0447] Example 11

[0448] This application provides a terminal device that includes a system information acquisition device as described in Embodiment 7.

[0449] Figure 19 This is a schematic block diagram of the system configuration of the terminal device according to Embodiment 11 of this application. Figure 19 As shown, terminal device 1900 may include processor 1910 and memory 1920; memory 1920 is coupled to processor 1910. It is worth noting that this figure is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunications functions or other functions.

[0450] In one embodiment of this application, the function of the system information acquisition device can be integrated into the processor 1910. The processor 1910 can be configured to: acquire scheduling information, which is generated based on the association between the system information area ID (systemInformationAreaID) and the area scope (areaScope).

[0451] For example, the processor 1910 can also be configured to determine, for a given SIB, whether a valid version of the SIB is stored based on the scheduling information and other information in the system information broadcast by the serving cell.

[0452] For example, determining whether a valid version of the SIB is stored based on the scheduling information and other information in the system information broadcast by the serving cell includes: for a stored version of the SIB, if the system information area identifier and the value tag associated with the SIB in the scheduling information, and the Public Land Mobile Network (PLMN) identifier in the other information are the same as the system information area identifier, value tag, and PLMN identifier associated with the stored version, the terminal device considers the stored version valid; or, for a stored version of the SIB, if the value tag associated with the SIB in the scheduling information, and the PLMN identifier and cell identifier in the other information are the same as the value tag associated with the stored version... The terminal device considers the stored version valid if the Public Land Mobile Network (PTN) identifier and cell identifier are the same; or, for a stored version of the SIB, the terminal device considers the stored version valid if the system information area identifier in the scheduling information, the value tag associated with the SIB, and the NPN identifier in the other information are the same as the system information area identifier, value tag, and NPN identifier associated with the stored version; or, for a stored version of the SIB, the terminal device considers the stored version valid if the value tag associated with the SIB in the scheduling information, the NPN identifier in the other information, and the cell identifier are the same as the value tag, NPN identifier, and cell identifier associated with the stored version.

[0453] For example, the processor 1910 can also be configured to: when a valid version exists, the terminal device uses the valid version of the SIB; and when a valid version does not exist, the terminal device sends a system information request to the network device or obtains the SIB according to the scheduling information.

[0454] For example, the scheduling information includes the system information area identifier and the area range.

[0455] For example, the SIB can be at least one of SIB2, SIB3, SIB4 and SIB5, and the SIB can also be at least one of SIB9, SIB10, SIB11, SIB12, SIB13 and SIB14.

[0456] For example, this scheduling information is included in SIB1.

[0457] In another embodiment, the system information acquisition device can be configured separately from the processor 1910. For example, the system information acquisition device can be configured as a chip connected to the processor 1910, and the function of the system information acquisition device can be realized through the control of the processor 1910.

[0458] like Figure 19 As shown, the terminal device 1900 may also 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 is not necessarily required to include these components. Figure 19 All components shown; in addition, terminal device 1900 may also include Figure 19 For components not shown, please refer to relevant technologies.

[0459] like Figure 19 As shown, processor 1910, sometimes also referred to as controller or operation control, may include a microprocessor or other processor device and / or logic device, which receives input and controls the operation of various components of terminal device 1900.

[0460] The memory 1920 may be, for example, one or more of a cache, flash memory, hard drive, removable media, volatile memory, non-volatile memory, or other suitable devices. It can store various types of data, and also stores programs for executing related information. The processor 1910 can execute the program stored in the memory 1920 to perform information storage or processing, etc. The functions of other components are similar to those in existing systems and will not be described further here. The various components of the terminal device 1200 can be implemented using dedicated hardware, firmware, software, or a combination thereof, without departing from the scope of this application.

[0461] As can be seen from the above embodiments, the terminal device can obtain the scheduling information generated by the network device based on the correlation 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. Therefore, it can avoid the uncertainty of the terminal device's behavior and reduce the complexity of testing and the overhead of the terminal device.

[0462] Example 12

[0463] This application provides a terminal device that includes a system information acquisition device as described in Embodiment 8.

[0464] Figure 20 This is a schematic block diagram of the system configuration of the terminal device according to Embodiment 12 of this application. Figure 20As shown, terminal device 2000 may include processor 2010 and memory 2020; memory 2020 is coupled to processor 2010. It is worth noting that this figure is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunications functions or other functions.

[0465] In one embodiment of this application, the function of the system information acquisition device can be integrated into the processor 2010. The processor 2010 can be configured such that, for a storage version of an SIB, when the obtained scheduling information includes an area scope corresponding to the SIB, and when the scheduling information includes a system information area ID and the system information area ID and the first information associated with the storage version are the same, the terminal device considers the storage version to be valid.

[0466] For example, the processor 2010 can also be configured such that, for a storage 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, the terminal device considers the storage version invalid.

[0467] For example, the processor 2010 can also be configured such that, for a storage 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 corresponding information associated with the storage version, the terminal device considers the storage version to be valid.

[0468] For example, the processor 2010 can also be configured such that, for a storage version of an SIB, when the obtained scheduling information includes the area scope corresponding to the SIB, and when the scheduling information does not include the system information area identifier but the first information and cell identifier are the same as the corresponding information and cell identifier associated with the storage version, the terminal device considers the storage version to be valid.

[0469] For example, the first information includes: the first PLMN identifier (PLMN-Identity) received from the serving cell and included in the PLMN-IdentityInfoList, and the value tag associated with the SIB included in the scheduling information; the corresponding information includes: the PLMN identifier (PLMN-Identity) and value tag associated with the storage version of the SIB.

[0470] For example, when the terminal device does not have NPN capability or the serving cell is not an NPN-only cell, the first information includes: the first PLMN identifier (PLMN-Identity) received from the serving cell and included in the PLMN-IdentityInfoList, and the value tag associated with the SIB included in the scheduling information; the corresponding information includes: the PLMN identifier (PLMN-Identity) and value tag associated with the storage version of the SIB.

[0471] For example, the first information includes: the first NPN identifier received from the serving cell, which is in the NPN-IdentityInfoList, and the value tag associated with the SIB included in the scheduling information; the corresponding information includes: the NPN identifier and value tag associated with the storage version of the SIB.

[0472] For example, when the terminal device has NPN capability and the serving cell is an NPN-only cell, the first information includes: the first NPN identifier received from the serving cell, which includes the first NPN identifier in the NPN-IdentityInfoList and the value tag associated with the SIB included in the scheduling information; the corresponding information includes: the NPN identifier and value tag associated with the storage version of the SIB.

[0473] For example, the processor 2010 can also be configured to: use the valid version of the SIB when the terminal device deems the storage version valid; and when no valid version exists, the terminal device sends a system information request to the network device or obtains the SIB according to the scheduling information.

[0474] In another embodiment, the system information acquisition device can be configured separately from the processor 2010. For example, the system information acquisition device can be configured as a chip connected to the processor 2010, and the function of the system information acquisition device can be realized through the control of the processor 2010.

[0475] like Figure 20 As shown, the terminal device 2000 may also 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 is not necessarily required to include these components. Figure 20 All components shown; in addition, the terminal device 2000 may also include Figure 20 For components not shown, please refer to relevant technologies.

[0476] like Figure 20 As shown, the processor 2010, sometimes also referred to as a controller or operation control, may include a microprocessor or other processor device and / or logic device, which receives input and controls the operation of various components of the terminal device 2000.

[0477] The memory 2020 may be, for example, one or more of a cache, flash memory, hard drive, removable media, volatile memory, non-volatile memory, or other suitable devices. It can store various types of data and, in addition, programs for executing related information. The processor 2010 can execute the program stored in the memory 2020 to perform information storage or processing, etc. The functions of other components are similar to those in existing systems and will not be described further here. The various components of the terminal device 2000 can be implemented using dedicated hardware, firmware, software, or a combination thereof without departing from the scope of this application.

[0478] As can be seen from the above embodiments, when checking the validity of a SIB's storage version, the terminal device's behavior is specified for both configured and unconfigured system information area identifiers. Therefore, uncertainty in the terminal device's behavior can be avoided, and the complexity of testing and the overhead of the terminal device can be reduced.

[0479] Example 13

[0480] This application provides a network device that includes a system information configuration device as described in Embodiment 9.

[0481] Figure 21 This is a schematic block diagram of the system configuration of the network device in Embodiment 13 of this application. Figure 21 As shown, 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 types of data; it also stores an information processing program 2130, which is executed under the control of the processor 2110 to receive and send various types of information to the terminal devices.

[0482] In one embodiment, the function of the system information configuration device can be integrated into the processor 2110. The processor 2110 can be configured to: for terminal device-specific parameters, when the condition includes the serving cell configuring supplementary uplink, the network device considers the capabilities of the terminal device; or, for both terminal device-specific and cell-specific parameters, when the condition includes the serving cell configuring supplementary uplink, the network device does not consider the capabilities of the terminal device, or the network device only considers that the network device provides SUL configuration for the terminal device.

[0483] For example, the network device considers the capabilities of the terminal device, including: based on the capabilities of the terminal device, the network device determines that the terminal device can support the SUL band provided in the SUL configuration; or, the network device provides the terminal device with an SUL configuration, and based on the capabilities of the terminal device, the network device determines that the terminal device can support the SUL band indicated in the SUL configuration.

[0484] For example, network devices consider the capabilities of terminal devices, including: the presence of a supplementary uplink in the servingCellConfigCommon indicates that the network device provides SUL configuration for the terminal device.

[0485] For example, the terminal device-specific parameters are tpc-Index and / or tpc-IndexSUL.

[0486] For example, the parameter specific to the terminal device is either information, IE, or domain.

[0487] For example, the terminal device-specific parameter can also be terminal device-specific information, terminal device-specific IE, or terminal device-specific domain.

[0488] For example, when the conditions include the serving cell being configured with supplementary uplink, the capabilities of the terminal device are not considered, or only the network device is considered to provide SUL configuration for the terminal device, including: when the first configuration information common to the cell includes supplementary uplink configuration, the configuration for sending system information messages on supplementary uplink (e.g., si-RequestConfigSUL, posSI-RequestConfigSUL-r16) can be optionally provided in the scheduling information.

[0489] For example, the first configuration information is the serving cell common configuration (servingCellConfigCommon).

[0490] For example, when there is a supplementary uplink in the serving cell common configuration (servingCellConfigCommon) and the system information broadcast status (e.g., si-BroadcastStatus, posSI-BroadcastStatus) of any system information message (SI-message) in the scheduling information (SchedulingInfo) is set to non-broadcast, the scheduling information may optionally provide the configuration for sending system information messages on the supplementary uplink (e.g., si-RequestConfigSUL, posSI-RequestConfigSUL-r16).

[0491] For example, the configuration for sending system information messages on the supplementary uplink exists under the following conditions: when a supplementary uplink exists in the serving cell common configuration (servingCellConfigCommon) and the system information broadcast status (e.g., si-BroadcastStatus, posSI-BroadcastStatus) of any system information message (SI-message) in the scheduling information (SchedulingInfo) is set to non-broadcast, the configuration for sending system information messages on the supplementary uplink is optional; otherwise, the configuration for sending system information messages on the supplementary uplink is missing.

[0492] For example, this scheduling information is included in SIB1.

[0493] In another embodiment, the system information configuration device can be configured separately from the processor 2110. For example, the system information configuration device can be configured as a chip connected to the processor 2110, and the function of the system information configuration device can be realized through the control of the processor 2110.

[0494] In addition, such as Figure 21 As shown, network device 2100 may also include: transceiver 2140 and antenna 2150, etc.; the functions of the above components are similar to those in the prior art, and will not be described in detail here. It is worth noting that network device 2100 is not necessarily required to include... Figure 21 All components shown; in addition, network device 2100 may also include Figure 21 For components not shown, please refer to existing technology.

[0495] As can be seen from the above embodiments, for terminal device-specific parameters, when the condition includes the serving cell configuring supplementary uplink, the terminal device's capabilities are considered. Alternatively, for both terminal device-specific and cell-specific parameters, when the condition includes the serving cell configuring supplementary uplink, the terminal device's capabilities are not considered, or only the network device providing SUL configuration for the terminal device is considered. In this way, the network device can clearly understand the contents of SIB1, avoiding uncertainties in network device implementation, reducing the testing costs of network device products, and thus saving network deployment costs.

[0496] Example 14

[0497] This 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, or the communication system includes the network device according to embodiment 13.

[0498] For example, the structure of this communication system can be referred to Figure 1 ,like Figure 1 As shown, 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. Repeated content will not be described again.

[0499] The apparatus and methods described above in this application can be implemented in hardware or in combination with software. This application relates to a computer-readable program that, when executed by a logic component, enables the logic component to implement the apparatus or components described above, or to implement the various methods or steps described above. Logic components include, for example, field-programmable logic devices (FPGAs), microprocessors, and processors used in computers. This application also relates to storage media for storing the above programs, such as hard disks, magnetic disks, optical disks, DVDs, and flash memory.

[0500] The methods / apparatus described in conjunction with the embodiments of this application can be directly embodied in hardware, software modules executed by a processor, or a combination of both. For example, Figure 13 One or more, and / or combinations of one or more, functional block diagrams shown can correspond to either software modules or hardware modules in a computer program flow. These software modules can respectively correspond to... Figure 3 The steps are shown in the diagram. These hardware modules can be implemented by embedding these software modules, for example, using a field-programmable gate array (FPGA).

[0501] The software module can 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, enabling the processor to 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 can reside in an ASIC. The software module can be stored in the memory of a mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a high-capacity MEGA-SIM card or a high-capacity flash memory device, the software module can be stored in the MEGA-SIM card or the high-capacity flash memory device.

[0502] Regarding the appendix Figure 13One or more and / or one or more combinations of functional blocks described herein can be implemented as a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, or any suitable combination thereof for performing the functions described herein. (Regarding the appendix...) Figure 13 One or more of the functional blocks described and / or one or more combinations of functional blocks can also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0503] The present application has been described above with reference to specific embodiments. However, those skilled in the art should understand that these descriptions are exemplary and not intended to limit the scope of protection of the present application. Those skilled in the art can make various modifications and variations to the present application based on its spirit and principles, and these modifications and variations are also within the scope of the present application.

[0504] According to the various embodiments disclosed in this application, the following notes are also disclosed:

[0505] Postscript 1

[0506] 1. A system information configuration device, the device being applied to a network device, the device comprising:

[0507] The generation unit generates scheduling information (SchedulingInfo) based on the correlation between the system information area identifier (systemInformationAreaID) and the area scope (areaScope); and

[0508] The sending unit sends the scheduling information.

[0509] 2. The apparatus according to Appendix 1, wherein,

[0510] When the scheduling information includes the system information region identifier, the generation unit configures the region range for one or more SIBs within the scheduling information, or optionally configures the region range for one or more SIBs within the scheduling information.

[0511] 3. The apparatus according to Appendix 2, wherein,

[0512] When the scheduling information does not include the system information region identifier, the generation unit does not configure the region range in the scheduling information.

[0513] 4. The apparatus according to any one of Appendices 1-3, wherein,

[0514] The necessity coding condition for the regional range field in the scheduling information is as follows:

[0515] When the scheduling information includes the system information region identifier, the region range field is mandatory; when the scheduling information does not include the system information region identifier, the region range field does not exist, or...

[0516] When the scheduling information includes the system information region identifier, the region range field may optionally exist; when the scheduling information does not include the system information region identifier, the region range field does not exist.

[0517] 5. The apparatus according to Appendix 1, wherein,

[0518] When the scheduling information includes one or more regions configured as an SIB, the generation unit configures the system information region identifier within the scheduling information.

[0519] 6. The apparatus according to Appendix 5, wherein,

[0520] When the scheduling information does not include one or more regions configured as an SIB, the generation unit may optionally configure the system information region identifier within the scheduling information, or may not configure the system information region identifier within the scheduling information.

[0521] 7. The apparatus according to any one of Appendix 1, 5, or 6, wherein,

[0522] The necessary encoding conditions for the system information area identifier field in the scheduling information are as follows:

[0523] When the scheduling information includes one or more region ranges configured for a single SIB, the system information region identifier field is mandatory; and

[0524] When the scheduling information does not include one or more area ranges configured for a single SIB, the system information area identifier field may be present.

[0525] 8. The apparatus according to any one of Appendix 1, 5, or 6, wherein,

[0526] The necessary encoding conditions for the system information area identifier field in the scheduling information are as follows:

[0527] When the scheduling information includes one or more region ranges configured for a single SIB, the system information region identifier field is mandatory; and

[0528] When the scheduling information does not include one or more area ranges configured for a single SIB, the system information area identifier field does not exist.

[0529] 9. The apparatus according to any one of Appendix 1-2 or 4-8, wherein,

[0530] The scheduling information includes the system information region identifier and the region range.

[0531] 10. The apparatus according to any one of Appendices 1-9, wherein,

[0532] The scheduling information is sent via broadcast.

[0533] 11. The apparatus according to any one of Appendices 1-10, wherein,

[0534] The scheduling information is included in SIB1.

[0535] 12. A system information acquisition device, the device being applied to a terminal device, the device comprising:

[0536] The first acquisition unit obtains scheduling information, which is generated based on the correlation between the system information area identifier (systemInformationAreaID) and the area scope (areaScope).

[0537] 13. The apparatus according to Appendix 12, wherein the apparatus further comprises:

[0538] The first determining unit determines, for a given SIB, whether a valid version of the SIB is stored based on the scheduling information and other information in the system information broadcast by the serving cell.

[0539] 14. The apparatus according to Appendix 13, wherein the first determining unit comprises:

[0540] The second determining unit, for a stored version of the SIB, considers the stored version valid when the system information area identifier in the scheduling information, the value tag associated with the SIB, and the public land mobile network identifier (PLMN-Identity) in the other information are the same as the system information area identifier, value tag, and public land mobile network identifier associated with the stored version; or, for a stored version of the SIB, considers the stored version valid when the value tag associated with the SIB in the scheduling information, the public land mobile network identifier (PLMN-Identity), and the cell identifier in the other information are the same as the value tag, public land mobile network identifier, and cell identifier associated with the stored version; or...

[0541] The third determining unit, for a storage version of the SIB, considers the storage version valid when the system information region identifier in the scheduling information, the value tag associated with the SIB, and the NPN identifier in the other information are the same as the system information region identifier, value tag, and NPN identifier associated with the storage version; or, for a storage version of the SIB, considers the storage version valid when the value tag associated with the SIB in the scheduling information, the NPN identifier, and cell identifier in the other information are the same as the value tag, NPN identifier, and cell identifier associated with the storage version.

[0542] 15. The apparatus according to Appendix 13 or 14, wherein the apparatus further comprises:

[0543] The first user unit, when a valid version exists, uses the valid version of the SIB; and

[0544] The second acquisition unit, when no valid version exists, sends a system information request to the network device or acquires the SIB according to the scheduling information.

[0545] 16. The apparatus according to any one of Appendices 12-15, wherein,

[0546] The scheduling information includes the system information region identifier and the region range.

[0547] 17. The apparatus according to any one of Appendix 13-16, wherein,

[0548] The SIB is at least one of SIB2, SIB3, SIB4 and SIB5.

[0549] 18. The apparatus according to any one of Appendix 12-17, wherein,

[0550] The scheduling information is included in SIB1.

[0551] 19. A system information acquisition device, the device being applied to a terminal device, the device comprising:

[0552] The fourth determining unit, for a storage version of an SIB, considers the storage version to be valid when the obtained scheduling information includes an area scope corresponding to the SIB, and when the scheduling information includes a system information area ID and the system information area ID and corresponding information associated with the storage version are the same.

[0553] 20. The apparatus according to Appendix 19, wherein the apparatus further comprises:

[0554] The fifth determining unit considers the storage version invalid if, for a storage version of an SIB, the obtained scheduling information includes a region range corresponding to the SIB, and if the scheduling information does not include a system information region identifier.

[0555] 21. The apparatus according to Appendix 19, wherein the apparatus further comprises:

[0556] The sixth determining unit considers the storage version to be valid when, for a storage version of an SIB, 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 but the first information is the same as the corresponding information associated with the storage version.

[0557] 22. The apparatus according to Appendix 19, wherein the apparatus further comprises:

[0558] The seventh determining unit, for a storage version of an SIB, considers the storage version to be valid when the obtained scheduling information includes the area scope corresponding to the SIB, and when the scheduling information does not include the system information area identifier but the first information and cell identifier are the same as the corresponding information and cell identifier associated with the storage version.

[0559] 23. The apparatus according to any one of Appendix 19-22, wherein,

[0560] The first information includes: the first PLMN identifier (PLMN-Identity) received from the serving cell and included in the PLMN identifier information list (PLMN-IdentityInfoList), and the value tag associated with the SIB included in the scheduling information;

[0561] The relevant information includes: the PLMN identifier (PLMN-Identity) and value label associated with the storage version of the SIB.

[0562] 24. The apparatus according to any one of Annexes 19-23, wherein,

[0563] When the terminal device does not have NPN capability or the serving cell is not an NPN-only cell,

[0564] The first information includes: the first PLMN identifier (PLMN-Identity) received from the serving cell and included in the PLMN identifier information list (PLMN-IdentityInfoList), and the value tag associated with the SIB included in the scheduling information;

[0565] The relevant information includes: the PLMN identifier (PLMN-Identity) and value label associated with the storage version of the SIB.

[0566] 25. The apparatus according to any one of Annexes 19-22, wherein,

[0567] The first information includes: the first NPN identifier received from the serving cell, which is part of an NPN identifier information list (NPN-IdentityInfoList) and the value tag associated with the SIB included in the scheduling information;

[0568] The relevant information includes: an NPN identifier and a value tag associated with the storage version of the SIB.

[0569] 26. The apparatus according to any one of Appendices 19-22, 25, wherein,

[0570] When the terminal device has NPN capability and the serving cell is an NPN-only cell,

[0571] The first information includes: the first NPN identifier received from the serving cell, which is part of an NPN identifier information list (NPN-IdentityInfoList) and the value tag associated with the SIB included in the scheduling information;

[0572] The relevant information includes: an NPN identifier and a value tag associated with the storage version of the SIB.

[0573] 27. The apparatus according to any one of Appendices 19-26, wherein the apparatus further comprises:

[0574] The second usage unit uses the valid version of the SIB when the terminal device deems the storage version valid; and

[0575] The third acquisition unit, when no valid version exists, sends a system information request to the network device or acquires the SIB according to the scheduling information.

[0576] 33. A network device comprising the means according to any one of Appendices 1-11.

[0577] 34. A terminal device comprising the means according to any one of Appendices 12-27.

[0578] 35. A communication system comprising the network device according to Appendix 33 and / or the terminal device according to Appendix 34.

[0579] 36. A method for configuring system information, the method being applied to a network device, the method comprising:

[0580] Scheduling information (SchedulingInfo) is generated based on the correlation between the system information area identifier (systemInformationAreaID) and the area scope (areaScope); and

[0581] Send the scheduling information.

[0582] 37. The method according to Appendix 36, wherein generating scheduling information based on the correlation between system information region identifier and region range includes:

[0583] When the scheduling information includes the system information region identifier, the network device configures the region range for one or more SIBs within the scheduling information, or optionally configures the region range for one or more SIBs within the scheduling information.

[0584] 38. The method according to Appendix 37, wherein generating scheduling information based on the correlation between system information area identifier and area range further includes:

[0585] When the scheduling information does not include the system information region identifier, the network device does not configure the region range in the scheduling information.

[0586] 39. The method according to any one of notes 36-38, wherein,

[0587] The necessity coding condition for the regional range field in the scheduling information is as follows:

[0588] When the scheduling information includes the system information region identifier, the region range field is mandatory; when the scheduling information does not include the system information region identifier, the region range field does not exist, or...

[0589] When the scheduling information includes the system information region identifier, the region range field may optionally exist; when the scheduling information does not include the system information region identifier, the region range field does not exist.

[0590] 40. The method according to Appendix 36, wherein generating scheduling information based on the correlation between system information region identifier and region range includes:

[0591] When the scheduling information includes one or more area ranges configured for a single SIB, the network device configures the system information area identifier within the scheduling information.

[0592] 41. The method according to Appendix 40, wherein generating scheduling information based on the correlation between system information region identifier and region range further includes:

[0593] When the scheduling information does not include one or more area ranges configured for a single SIB, the network device may optionally configure the system information area identifier within the scheduling information, or the network device may not configure the system information area identifier within the scheduling information.

[0594] 42. The method described according to any one of notes 36, 40, and 41, wherein,

[0595] The necessary encoding conditions for the system information area identifier field in the scheduling information are as follows:

[0596] When the scheduling information includes one or more region ranges configured for a single SIB, the system information region identifier field is mandatory; and

[0597] When the scheduling information does not include one or more area ranges configured for a single SIB, the system information area identifier field may be present.

[0598] 43. The method described according to any one of notes 36, 40, and 41, wherein,

[0599] The necessary encoding conditions for the system information area identifier field in the scheduling information are as follows:

[0600] When the scheduling information includes one or more region ranges configured for a single SIB, the system information region identifier field is mandatory; and

[0601] When the scheduling information does not include one or more area ranges configured for a single SIB, the system information area identifier field does not exist.

[0602] 44. The method described according to any one of notes 36-37, 39-43, wherein,

[0603] The scheduling information includes the system information region identifier and the region range.

[0604] 45. The method according to any one of notes 36-44, wherein,

[0605] The scheduling information is sent via broadcast.

[0606] 46. ​​The method according to any one of notes 36-45, wherein,

[0607] The scheduling information is included in SIB1.

[0608] 47. A method for acquiring system information, the method being applied to a terminal device, the method comprising:

[0609] Obtain scheduling information, which is generated based on the association between system information area ID (systemInformationAreaID) and area scope (areaScope).

[0610] 48. The method according to Appendix 47, wherein the method further comprises:

[0611] For a given SIB, it is determined whether a valid version of the SIB is stored based on the scheduling information and other information in the system information broadcast by the serving cell.

[0612] 49. The method according to Appendix 48, wherein determining whether a valid version of the SIB is stored based on the scheduling information and other information in the system information broadcast by the serving cell includes:

[0613] For a stored version of the SIB, when the System Information Area Identifier (SIA) in the scheduling information, the value tag associated with the SIB, and the Public Land Mobile Network (PLMN) Identifier in the other information are the same as the SIA, value tag, and PLMN Identifier associated with the stored version, the terminal device considers the stored version valid. Alternatively, for a stored version of the SIB, when the value tag associated with the SIB in the scheduling information, and the PLMN Identifier and cell identifier in the other information are the same as the value tag, PLMN Identifier, and cell identifier associated with the stored version, the terminal device considers the stored version valid.

[0614] For a storage version of the SIB, the terminal device considers the storage version valid when the system information region identifier in the scheduling information, the value tag associated with the SIB, and the NPN identifier in the other information are the same as the system information region identifier, value tag, and NPN identifier associated with the storage version. Alternatively, for a storage version of the SIB, the terminal device considers the storage version valid when the value tag associated with the SIB in the scheduling information, the NPN identifier, and cell identifier in the other information are the same as the value tag, NPN identifier, and cell identifier associated with the storage version.

[0615] 50. The method according to Appendix 48 or 49, wherein the method further comprises:

[0616] When a valid version exists, the terminal device uses the valid version of the SIB; and

[0617] When no valid version exists, the terminal device sends a system information request to the network device or obtains the SIB according to the scheduling information.

[0618] 51. The method according to any one of notes 47-50, wherein,

[0619] The scheduling information includes the system information region identifier and the region range.

[0620] 52. The method described according to any one of notes 48-51, wherein,

[0621] The SIB is at least one of SIB2, SIB3, SIB4 and SIB5.

[0622] 53. The method described according to any one of notes 47-52, wherein,

[0623] The scheduling information is included in SIB1.

[0624] 54. A method for acquiring system information, the method being applied to a terminal device, the method comprising:

[0625] For a storage version of an SIB, when the obtained scheduling information includes an area scope corresponding to the SIB, and when the scheduling information includes a system information area ID (systemInformationAreaID) and the system information area ID and the first information are the same as the system information area ID and corresponding information associated with the storage version, the terminal device considers the storage version to be valid.

[0626] 55. The method according to Appendix 54, wherein the method further comprises:

[0627] For a storage version of an SIB, the terminal device considers the storage version 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.

[0628] 56. The method according to Appendix 54, wherein the method further comprises:

[0629] For a storage version of an SIB, the terminal device considers the storage version valid 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 but the first information is the same as the corresponding information associated with the storage version.

[0630] 57. The method according to Appendix 54, wherein the method further comprises:

[0631] For a storage version of an SIB, the terminal device considers the storage version valid when the obtained scheduling information includes the area scope corresponding to the SIB, and when the scheduling information does not include the system information area identifier but the first information and cell identifier are the same as the corresponding information and cell identifier associated with the storage version.

[0632] 58. The method described according to any one of notes 54-57, wherein,

[0633] The first information includes: the first PLMN identifier (PLMN-Identity) received from the serving cell and included in the PLMN identifier information list (PLMN-IdentityInfoList), and the value tag associated with the SIB included in the scheduling information;

[0634] The relevant information includes: the PLMN identifier (PLMN-Identity) and value tag associated with the storage version of the SIB.

[0635] 59. The method described according to any one of notes 54-58, wherein,

[0636] When the terminal device does not have NPN capability or the serving cell is not an NPN-only cell,

[0637] The first information includes: the first PLMN identifier (PLMN-Identity) received from the serving cell and included in the PLMN identifier information list (PLMN-IdentityInfoList), and the value tag associated with the SIB included in the scheduling information;

[0638] The relevant information includes: the PLMN identifier (PLMN-Identity) and value tag associated with the storage version of the SIB.

[0639] 60. The method described according to any one of notes 54-57, wherein,

[0640] The first information includes: the first NPN identifier received from the serving cell, which is part of an NPN identifier information list (NPN-IdentityInfoList) and the value tag associated with the SIB included in the scheduling information;

[0641] The relevant information includes: an NPN identifier and a value tag associated with the storage version of the SIB.

[0642] 61. The method described according to any one of notes 54-57, 60, wherein,

[0643] When the terminal device has NPN capability and the serving cell is an NPN-only cell,

[0644] The first information includes: the first NPN identifier received from the serving cell, which is part of an NPN identifier information list (NPN-IdentityInfoList) and the value tag associated with the SIB included in the scheduling information;

[0645] The relevant information includes: an NPN identifier and a value tag associated with the storage version of the SIB.

[0646] 62. The method according to any one of Appendices 54-61, wherein the method further comprises:

[0647] When the terminal device deems the storage version valid, it uses the valid version of the SIB; and

[0648] When no valid version exists, the terminal device sends a system information request to the network device or obtains the SIB according to the scheduling information.

[0649] Appendix II

[0650] 1. A system information configuration device, the device being applied to a network device, the device comprising:

[0651] The configuration unit, for terminal device-specific parameters, considers the terminal device's capabilities when the conditions include the serving cell configuring supplementary uplink; or, for both terminal device-specific and cell-specific parameters, when the conditions include the serving cell configuring supplementary uplink, it either does not consider the terminal device's capabilities or only considers that the network device provides SUL configuration for the terminal device.

[0652] 2. The apparatus according to Appendix 1, wherein the network device takes into account the capabilities of the terminal device, including:

[0653] Based on the capabilities of the terminal device, the network device determines that the terminal device can support the SUL frequency band provided in the SUL configuration; or...

[0654] The network device provides SUL configuration for the terminal device, 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.

[0655] 3. The apparatus according to Appendix 1 or 2, wherein the network device takes into account the capabilities of the terminal device, including:

[0656] The presence of a supplementary uplink in the public cell configuration (servingCellConfigCommon) indicates that the network device provides SUL configuration for the terminal device.

[0657] 4. The apparatus according to Appendix 1, wherein,

[0658] The specific parameters of the terminal device are tpc-Index and / or tpc-IndexSUL.

[0659] 5. The apparatus according to any one of Appendices 1-3, wherein,

[0660] The parameters specific to the terminal device are either information, IE, or domain.

[0661] 6. The apparatus according to any one of Appendices 1-5, wherein the step of considering either the capabilities of the terminal device or only the network device providing SUL configuration for the terminal device when the conditions include the serving cell being configured with supplementary uplink includes:

[0662] When the primary configuration information of the community includes supplementary uplink configuration, the scheduling information may optionally provide supplementary uplink configuration for sending system information messages.

[0663] 7. The apparatus according to any one of Appendices 1-6, wherein,

[0664] The first configuration information is the serving cell common configuration (servingCellConfigCommon).

[0665] 8. The apparatus according to any one of Appendices 1-7, wherein,

[0666] When the serving cell configuration common configuration (servingCellConfigCommon) contains a supplementary uplink and the system information broadcast status of any system information message (SI-message) in the scheduling information is set to non-broadcast, the configuration unit may optionally provide the configuration for sending system information messages on the supplementary uplink in the scheduling information.

[0667] 9. The apparatus according to any one of Appendices 1-8, wherein the condition for the existence of the supplementary uplink configuration for sending system information messages is:

[0668] When a supplementary uplink exists in the serving cell configuration (servingCellConfigCommon) and the system information broadcast status (si-BroadcastStatus) of any system information message (SI-message) in the scheduling information (SchedulingInfo) is set to non-broadcast, the configuration for sending system information messages on the supplementary uplink is optional; otherwise, the configuration for sending system information messages on the supplementary uplink is empty.

[0669] 10. The apparatus according to any one of Appendices 1-9, wherein,

[0670] The scheduling information is included in SIB1.

[0671] 11. A network device comprising the means according to any one of Appendices 1-10.

[0672] 12. A communication system comprising the network device described in Appendix 11.

[0673] 13. A method for configuring system information, the method being applied to a network device, the method comprising:

[0674] For terminal device-specific parameters, when conditions include the serving cell configuring supplemental uplink, the network device considers the terminal device's capabilities, or...

[0675] For terminal device-specific parameters and cell-specific parameters, when conditions include the serving cell configuring supplementary uplink, the network device does not consider the terminal device's capabilities or the network device only considers that the network device provides SUL configuration for the terminal device.

[0676] 14. The method according to Appendix 13, wherein the network device takes into account the capabilities of the terminal device, including:

[0677] Based on the capabilities of the terminal device, the network device determines that the terminal device can support the SUL frequency band provided in the SUL configuration; or...

[0678] The network device provides SUL configuration for the terminal device, 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.

[0679] 15. The method according to Appendix 13 or 14, wherein the network device takes into account the capabilities of the terminal device, including:

[0680] The presence of a supplementary uplink in the public cell configuration (servingCellConfigCommon) indicates that the network device provides SUL configuration for the terminal device.

[0681] 16. According to the method described in Appendix 13, wherein,

[0682] The specific parameters of the terminal device are tpc-Index and / or tpc-IndexSUL.

[0683] 17. The method according to any one of notes 13-15, wherein,

[0684] The parameters specific to the terminal device are either information, IE, or domain.

[0685] 18. The method according to any one of Appendices 13-17, wherein the step of considering only the network device providing SUL configuration for the terminal device without considering the terminal device's capabilities or only considering that the serving cell has configured supplementary uplink when the conditions include:

[0686] When the primary configuration information of the community includes supplementary uplink configuration, the supplementary uplink configuration (si-RequestConfigSUL) for sending system information messages can be optionally provided in the scheduling information.

[0687] 19. According to the method described in Appendix 18, wherein,

[0688] The first configuration information is the serving cell common configuration (servingCellConfigCommon).

[0689] 20. The method according to any one of notes 13-19, wherein,

[0690] When a supplementary uplink exists in the serving cell configuration (servingCellConfigCommon) and the system information broadcast status of any system information message (SI-message) in the scheduling information (SchedulingInfo) is set to non-broadcast, the scheduling information may optionally provide the configuration for sending system information messages on the supplementary uplink.

[0691] 21. The method according to any one of Appendices 13-20, wherein the existence condition of the supplementary uplink configuration for sending system information messages is:

[0692] When a supplementary uplink exists in the serving cell configuration (servingCellConfigCommon) and the system information broadcast status (si-BroadcastStatus) of any system information message (SI-message) in the scheduling information (SchedulingInfo) is set to non-broadcast, the configuration for sending system information messages on the supplementary uplink is optional; otherwise, the configuration for sending system information messages on the supplementary uplink is empty.

[0693] 22. The method according to any one of notes 13-21, wherein,

[0694] The scheduling information is included in SIB1.

Claims

1. A system information configuration device, the device being applied to a network device, the device comprising: Memory; as well as A processor, which is connected to the memory, and the processor is configured to: For cell-specific parameters, when the serving cell common configuration (servingCellConfigCommon) includes supplementary uplink configuration and when the system information broadcast status of any system information message (SI-message) in the scheduling information (SchedulingInfo) included in SIB1 is set to "not broadcast", the scheduling information included in SIB1 provides the configuration for sending system information messages on the supplementary uplink of the serving cell.

2. A communication system, the communication system comprising network equipment and terminal equipment: The network device is configured to provide, for cell-specific parameters, the supplementary uplink configuration for sending system information messages in the supplementary uplink of the serving cell when the serving cell common configuration (servingCellConfigCommon) includes supplementary uplink configuration and when the system information broadcast status of any system information message (SI-message) in the scheduling information (SchedulingInfo) included in SIB1 is set to "not broadcast". The terminal device is configured to receive the SIB1, which includes the supplementary uplink configuration for sending system information messages for the serving cell in the scheduling information, wherein... For cell-specific parameters, the configuration is provided when the serving cell configuration includes the supplementary uplink configuration and when the system information broadcast status of any system information message (SI-message) in the scheduling information (SchedulingInfo) included in the SIB1 is set to "not broadcast".

Images