Patent Description:
To access a cell, a terminal device needs to receive system information broadcast by a base station of the cell. If the terminal device is located in coverage of the base station, the terminal device may directly receive the system information broadcast by the base station, or may receive the system information forwarded by a relay terminal device in coverage of the base station. If the terminal device is located out of coverage of the base station, the terminal device can receive the system information only via the relay terminal device in coverage of the base station.

When there is an available relay terminal device near the terminal device, to save power, the terminal device usually chooses to use the relay terminal device to indirectly "camp on" a cell or indirectly access a cell, and the terminal device can receive, via the relay terminal device, the system information broadcast by the base station. When the terminal device receives the system information via the relay terminal device, the relay terminal device does not know information such as system information type required by the terminal device, and consequently the system information forwarded to the terminal device by the relay terminal device includes system information not required by the terminal device. Consequently, there is relatively large signaling between the terminal device and the relay terminal device, signaling overheads are relatively large, and resource waste is caused.

<CIT> relates to methods and devices for providing system information of a cellular communication network. <CIT> relates to optimizations for relay communications.

<CIT> relates to providing and obtaining system information for remote wireless terminal and was filed before but published after the filing date of the present application.

Implementations of the present disclosure provide a method for transmitting system information and a terminal device, to reduce signaling interactions between terminal devices, reduce signaling overheads, and avoid resource waste.

The first terminal device can determine, based on the obtained first indication information of the second terminal device, the system information required by the second terminal device, so that the first terminal device does not send system information not required by the second terminal device to the second terminal device. This reduces signaling interactions between the first terminal device and the second terminal device, reduces signaling overheads, and avoids resource waste.

The first terminal device adds the second terminal device into the target terminal device group and sends the multicast message to all the terminal devices in the target terminal device group, thereby avoiding sending a same piece of system information to different terminal devices in a unicast manner. This reduces signaling interactions between the first terminal device and the second terminal device, reduces signaling overheads, and avoids resource waste.

Based on certain principles disclosed in the present application, the first terminal device sends a broadcast message including the public system information to the second terminal device, thereby avoiding repeatedly sending the public system information to different terminal devices. This reduces signaling interactions between the first terminal device and the second terminal device, reduces signaling overheads, and avoids resource waste.

The following clearly and completely describes the technical solutions in the implementations of the present disclosure with reference to the accompanying drawings in the implementations of the present disclosure.

<FIG> is a schematic architecture diagram of an application scenario according to an implementation of the present disclosure. As shown in <FIG>, a network <NUM> may include a base station <NUM>, first terminal devices <NUM> and <NUM>, and second terminal devices <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and <NUM>. The base station, the first terminal devices, and the second terminal devices may be wirelessly connected to each other.

When the base station <NUM> broadcasts system information, the first terminal devices <NUM> and <NUM> located in coverage (IC) of the base station <NUM> may directly receive the system information broadcast by the base station; the second terminal devices <NUM> and <NUM> located in coverage of the base station <NUM> and the second terminal devices <NUM> and <NUM> located in extended coverage (EC) of the base station <NUM> each may also directly receive the system information broadcast by the base station, or may receive the system information forwarded by the first terminal devices <NUM> and <NUM>; and the second terminal devices <NUM> and <NUM> located out of coverage (OOC) of the base station <NUM> need to receive, via the first terminal devices <NUM> and <NUM>, the system information broadcast by the base station. Based on the application scenario in <FIG>, an implementation of the present disclosure provides a method for transmitting system information. A first terminal device obtains first indication information of a second terminal device, so that the first terminal device can know a system information type required by the second terminal device, and the first terminal device does not send system information not required by the second terminal device to the second terminal device. This can reduce signaling interactions between the first terminal device and the second terminal device, reduce signaling overheads, and avoid resource waste. The following describes the method in detail with reference to <FIG>.

<FIG> is a schematic flowchart of a method <NUM> for transmitting system information according to an implementation of the present disclosure. The method <NUM> may be performed by a first terminal device, for example, the first terminal device <NUM> or the first terminal device <NUM> in the network <NUM>. The method <NUM> shown in <FIG> includes the following steps.

The first terminal device obtains first indication information.

The first terminal device determines, based on the first indication information, system information (SI) required by a second terminal device, where the second terminal device communicates with a base station via the first terminal device.

The first terminal device sends a message including target SI to the second terminal device, where the target SI is at least some of the SI required by the second terminal device.

In this implementation of the present disclosure, the first terminal device can determine, based on the obtained first indication information of the second terminal device, the system information SI required by the second terminal device, so that the first terminal device forwards the system information required by the second terminal device to the second terminal device. This reduces signaling interactions between the first terminal device and the second terminal device, reduces signaling overheads, and avoids resource waste.

It should be understood that the target SI or the SI required by the second terminal device may be a system information block (SIB) and/or some parameters in a SIB, or may be a set of all parameters that the second terminal device needs to receive.

Optionally, in some implementations, the first terminal device may be a relay terminal device, for example, a smartphone; and the second terminal device may be a wearable device (WD), for example, a smartwatch or a smart band. However, this implementation of the present disclosure is not limited thereto.

It should be understood that in this implementation of the present disclosure, a communication connection is established between the first terminal device and the second terminal device, and the communication connection may be, for example, a pairing relationship established based on a Bluetooth technology, or an association relationship established based on a wireless local area network (WLAN) technology, or a connection relationship established based on a device-to-device (D2D) technology in a Long Term Evolution (LTE) technology.

In this implementation of the present disclosure, the communication connection established between the first terminal device and the second terminal device is described only by using the pairing relationship, the association relationship, and the connection relationship. However, this implementation of the present disclosure is not limited thereto.

It should be understood that after the communication connection is established between the first terminal device and the second terminal device, to save power, the second terminal device usually chooses the first terminal device as a relay device to communicate with the base station, even if the second terminal device in coverage of the base station. For example, when a D2D connection is established between a wearable device WD and a relay terminal device, the wearable device receives system information via the relay terminal device in most cases.

Optionally, in some implementations, the first indication information may be a capability supported by the second terminal device.

For example, the first indication information may be an extended access barring (EAB) capability supported by the second terminal device, or may be an earthquake and tsunami warning system (ETWS) capability supported by the second terminal device, or may be a commercial mobile alert service (CMAS) capability supported by the second terminal device, or may be a service specific access control (SSAC) capability supported by the second terminal device, or an application specific congestion control for data communication (ACDC) capability supported by the second terminal device.

In this implementation of the present disclosure, the first indication information is described only by using the foregoing five types of capabilities supported by the second terminal device. However, this implementation of the present disclosure is not limited thereto.

Optionally, in some implementations, the first indication information may be alternatively of a system information type required by the second terminal device.

Optionally, in some implementations, that the first terminal device obtains first indication information may be: The first terminal device receives the first indication information sent by the second terminal device. To be specific, the second terminal device reports the capability supported by the second terminal device or the system information type required by the second terminal device to the first terminal device.

Optionally, in some implementations, that the first terminal device obtains first indication information may be alternatively: The first terminal device receives the first indication information sent by the base station or a mobility management entity (MME). When accessing a network for the first time, the second network device may register with an MME or a base station of a cell in which the second terminal device is located, the capability supported by the second terminal device or the system information type required by the second terminal device, namely, the first indication information. When the first terminal device needs to obtain the first indication information of the second terminal device, the base station or the MME may send, to the first terminal device, the first indication information that is prestored in the base station by the second terminal device.

In this implementation of the present disclosure, the first terminal device receives the first indication information sent by the base station or the MME, to prevent the second terminal device from sending the first indication information to the first terminal device. This reduces signaling interactions between the first terminal device and the second terminal device, reduces signaling overheads, and helps the second terminal device save power.

<FIG> is a schematic flowchart of a method <NUM> for transmitting system information according to an implementation of the present disclosure.

In <NUM>, a first terminal device and a second terminal device establish a communication connection.

Optionally, in some implementations, the communication connection may be a Bluetooth connection, or may be a WLAN connection, or may be a D2D connection.

In <NUM>, the first terminal device obtains first indication information.

For example, the first indication information may be an EAB capability supported by the second terminal device, or may be an ETWS capability supported by the second terminal device, or may be a CMAS capability supported by the second terminal device, or may be an SSAC capability supported by the second terminal device, or may be an ACDC capability supported by the second terminal device.

It should be understood that in this implementation of the present disclosure, the capability supported by the second terminal device is described only by using the foregoing five types of capabilities. However, this implementation of the present disclosure is not limited thereto.

Optionally, in some implementations, that the first terminal device obtains first indication information may be: The first terminal device receives the first indication information sent by the second terminal device.

Optionally, in some implementations, that the first terminal device obtains first indication information may be alternatively: The first terminal device receives the first indication information sent by a base station.

In <NUM>, the first terminal device obtains system information broadcast by a base station.

When broadcasting the system information, the base station broadcasts a master information block (MIB) and a SIB <NUM> in a SIB by using two separate Radio Resource Control (RRC) messages, and may broadcast SIBs other than the MIB and the SIB <NUM> by using a plurality of RRC messages, and a plurality of SIBs may be put into one RRC message and broadcast by the base station.

In <NUM>, the first terminal device sends a message including target SI to the second terminal device.

Optionally, in some implementations, the target SI is at least some of the SI required by the second terminal device.

Optionally, in some implementations, that the first terminal device sends a message including target SI to the second terminal device may be: When the first terminal device receives a paging message indicating a system information SI change, after the first terminal device receives updated system information broadcast by a cell, the first terminal device sends, to the second terminal device, updated system information other than the MIB, the SIB <NUM>, a SIB <NUM>, a SIB <NUM>, a SIB <NUM>, and a SIB <NUM> in the SI required by the second terminal device. That is, the first terminal device sends the target SI to the second terminal device, and the target SI is some of the SI required by the second terminal device.

It should be understood that the base station may indicate, by using the paging message, that system information other than the MIB, the SIB <NUM>, the SIB <NUM>, the SIB <NUM>, the SIB <NUM>, and the SIB <NUM> changes.

The base station may alternatively modify a value of SystemInfoValueTag in the SIB <NUM> to indicate that system information other than the MIB, the SIB <NUM>, the SIB <NUM>, the SIB <NUM>, the SIB <NUM>, and the SIB <NUM> changes. The value of SystemInfoValueTag is used to indicate whether the system information changes. A value range of SystemInfoValueTag is <NUM>-<NUM>. When the system information changes, a value of SystemInfoValueTag is incremented by <NUM>. Therefore, whether the system information changes can be determined based on whether the value of SystemInfoValueTag changes.

Optionally, in some implementations, when the second terminal device is a terminal device supporting the EAB capability, the target SI sent by the first terminal device to the second terminal device is a SIB <NUM>.

To be specific, that the first terminal device sends a message including target SI to the second terminal device may be: When the first terminal device receives a paging message indicating an EAB parameter change, the first terminal device sends an updated SIB <NUM> to the second terminal device.

It should be understood that when the first terminal device receives the paging message indicating the EAB parameter change, the first terminal device first needs to receive the SIB <NUM> broadcast by the base station and check a scheduling information list field (Scheduling InfoList) in the SIB <NUM> to determine whether the scheduling information list field includes a SIB <NUM> scheduling information; and when the scheduling information list field includes the SIB <NUM> scheduling information, the first terminal device receives the SIB <NUM> scheduling information based on scheduling information and sends the updated SIB <NUM> to the second terminal device.

Optionally, in some implementations, when the second terminal device is a terminal device supporting the ETWS capability, the target SI sent by the first terminal device to the second terminal device is a SIB <NUM> and/or a SIB <NUM>.

To be specific, that the first terminal device sends a message including target SI to the second terminal device may be: When the first terminal device receives a paging message indicating that there is an ETWS primary notification, the first terminal device sends the SIB <NUM> to the second terminal device; or
when the first terminal device receives a paging message indicating that there is an ETWS secondary notification, the first terminal device sends the SIB <NUM> to the second terminal device.

It should be understood that when the first terminal device receives the paging message indicating that there is the ETWS primary notification, the first terminal device first receives the SIB <NUM> and checks a scheduling information list field in the SIB <NUM> to determine whether the scheduling information list field indicates that there is the SIB <NUM> scheduling information; and if the scheduling information list field indicates that there is the SIB <NUM> scheduling information, the first terminal device receives the SIB <NUM> scheduling information based on scheduling information and sends the SIB <NUM> scheduling information to the second terminal device.

Likewise, when the first terminal device receives the paging message indicating that there is the ETWS secondary notification, the first terminal device first receives the SIB <NUM> and checks a scheduling information list field in the SIB <NUM> to determine whether the scheduling information list field indicates that there is the SIB <NUM> scheduling information; and if the scheduling information list field indicates that there is the SIB <NUM> scheduling information, the first terminal device receives the SIB <NUM> scheduling information based on scheduling information and sends the SIB <NUM> scheduling information to the second terminal device.

Optionally, in some implementations, when the second terminal device is a terminal device supporting the CMAS capability, the target SI sent by the first terminal device to the second terminal device is a SIB <NUM>.

To be specific, that the first terminal device sends a message including target SI to the second terminal device may be: When the first terminal device receives a paging message indicating that there is a CMAS notification, the first terminal device sends the SIB <NUM> to the second terminal device.

It should be understood that when the first terminal device receives the paging message indicating that there is the CMAS notification, the first terminal device first receives the SIB <NUM> and checks a scheduling information list field in the SIB <NUM> to determine whether the scheduling information list field indicates that there is the SIB <NUM> scheduling information; and if the scheduling information list field indicates that there is the SIB <NUM> scheduling information, the first terminal device receives the SIB <NUM> scheduling information based on scheduling information and sends the SIB <NUM> scheduling information to the second terminal device.

Optionally, in some implementations, after a communication connection relationship, a pairing relationship, or an association relationship is established between the first terminal device and the second terminal device, the first terminal device sends the target SI to the second terminal device, and the target SI is all of the SI required by the second terminal device.

Optionally, in some implementations, when the first terminal device performs cell reselection, intra-frequency handover, inter-frequency handover, and inter-RAT handover, after the first terminal device receives system information SI of a target cell on which cell reselection, intra-frequency handover, inter-frequency handover, and inter-RAT handover are performed, the first terminal device sends the target SI to the second terminal device, and the target SI is all of the system information SI required by the second terminal device.

For example, the first terminal device may determine, based on the first indication information, that system information currently required by the second terminal device is a SIB <NUM>, a SIB <NUM>, a SIB <NUM>, a SIB <NUM>, and a SIB <NUM>. When the first terminal device performs or completes cell reselection, intra-frequency handover, inter-frequency handover, or inter-RAT handover, the first terminal device sends, to the second terminal device, the following system information: a MIB, the SIB <NUM>, the SIB <NUM>, the SIB <NUM>, the SIB <NUM>, and the SIB <NUM>. In other words, the first terminal device sends all system information required by the second terminal device to the second terminal device.

Alternatively, when the first terminal device detects that the SIB <NUM> changes, after the first terminal device receives updated system information broadcast by a cell, the first terminal device sends, to the second terminal device, an updated SIB <NUM> or a parameter required by the second terminal device in an updated SIB <NUM>.

According to the invention, when the first terminal device detects that a parameter required by the second terminal device in the SIB <NUM> changes, after the first terminal device receives updated system information broadcast by a cell, the first terminal device sends, to the second terminal device, a parameter required by the second terminal device in an updated SIB <NUM>.

It should be understood that the first terminal device may determine, by checking a MIB or a SIB <NUM> broadcast by the base station, whether a MIB or a SIB <NUM> in the system information change.

Optionally, in some implementations, the first terminal device may be a relay terminal device, for example, a smartphone; and the second terminal device may be a wearable device, for example, a smartwatch or a smart band. However, this implementation of the present disclosure is not limited thereto.

In this implementation of the present disclosure, the first terminal device may send the system information required by the second terminal device to the second terminal device based on the capability supported by the second terminal device or directly based on the system information type required by the second terminal device, so that the first terminal device does not send system information not required by the second terminal device to the second terminal device. This reduces signaling interactions between the first terminal device and the second terminal device, reduces signaling overheads, and avoids resource waste.

Optionally, in some implementations, that the first terminal device obtains first indication information may be alternatively: The first terminal device receives the first indication information sent by a base station or an MME.

In <NUM>, the first terminal device adds the second terminal device into a target terminal device group.

Optionally, in some implementations, all terminal devices in the target terminal device group need target system information SI.

Optionally, in some implementations, that the first terminal device adds the second terminal device into a target terminal device group may be: The first terminal device obtains, based on the first indication information obtained by the first terminal device, a second terminal device that corresponds to each SIB and that requires the SIB, generates a list of second terminal devices corresponding to SIBs, and adds the second terminal device into the target terminal device group based on the list.

For example, it is assumed that at a current moment, communication connections are established between the first terminal device and six second terminal devices: second terminal devices #<NUM>-#<NUM>; after obtaining first indication information of the six second terminal devices, the first terminal device may obtain, based on the first indication information, a list of second terminal devices, as shown in Table <NUM>, that are corresponding to SIBs and that require the SIBs; and the first terminal device may add a current second terminal device into the target terminal device group based on the list, and the target terminal device group includes the current second terminal device.

Each row in Table <NUM> shows a terminal device requiring the SIB. For example, it can be determined based on the first indication information that system information required by a current second terminal device is a SIB <NUM>, and therefore the current second terminal device can be added into a target terminal device group shown in the second row in Table <NUM>, and all terminal devices in the target terminal device group need the SIB <NUM>.

For another example, it can be determined based on the first indication information that system information required by a current second terminal device is a SIB <NUM>, and therefore the current second terminal device can be added into a target terminal device group shown in the sixth row in Table <NUM>, and all terminal devices in the target terminal device group need the SIB <NUM>.

In <NUM>, the first terminal device sends a multicast message to the target terminal device group.

After the first terminal device adds the second terminal device into the target terminal device group, because all terminal devices in the target terminal device group require the target SI, the first terminal device may send a multicast message to the target terminal device group, and the multicast message includes the target SI. To be specific, the first terminal device sends, in a multicast manner, the target SI required by the second terminal device to all terminal devices requiring the target SI.

Optionally, in some implementations, that the first terminal device sends a multicast message to the target terminal device group may be: When the first terminal device receives a paging message indicating a system information change, the first terminal device sends updated system information other than a MIB, a SIB <NUM>, a SIB <NUM>, a SIB <NUM>, a SIB <NUM>, and a SIB <NUM> in the target SI to the target terminal device group in the multicast manner, and the target terminal device group includes the second terminal device.

To be specific, when the first terminal device receives the paging message indicating the system information change, the first terminal device sends the updated system information other than the MIB, the SIB <NUM>, the SIB <NUM>, the SIB <NUM>, the SIB <NUM>, and the SIB <NUM> to the second terminal device in the multicast manner.

Optionally, in some implementations, that the first terminal device sends a multicast message to the target terminal device group may be alternatively: When the second terminal device is a terminal device supporting the EAB capability, the first terminal device sends a SIB <NUM> to all terminal devices in the target terminal device group that require the SIB <NUM>, and the target terminal device group includes the second terminal device.

To be specific, when the first terminal device receives a paging message indicating an EAB parameter change, the first terminal device sends an updated SIB <NUM> to the second terminal device in the multicast manner.

Optionally, in some implementations, that the first terminal device sends a multicast message to the target terminal device group may be alternatively: When the second terminal device is a terminal device supporting the ETWS capability, the first terminal device sends a SIB <NUM> and/or a SIB <NUM> to all terminal devices in the target terminal device group that require the SIB <NUM> and/or the SIB <NUM>, and the target terminal device group includes the second terminal device.

Optionally, in some implementations, that the first terminal device sends a multicast message to the target terminal device group may be alternatively: When the second terminal device is a terminal device supporting the CMAS capability, the first terminal device sends a SIB <NUM> to all terminal devices in the target terminal device group that require the SIB <NUM>, and the target terminal device group includes the second terminal device.

To be specific, when the first terminal device receives a paging message indicating that there is a CMAS notification, the first terminal device sends a SIB <NUM> to the second terminal device in the multicast manner.

Optionally, in some implementations, after a communication connection relationship, a pairing relationship, or an association relationship is established between the first terminal device and the second terminal device, the first terminal device sends the target SI to the second terminal device in a unicast or multicast manner.

It should be understood that the target terminal device group may include only one second terminal device. For example, a target terminal device group corresponding to the SIB <NUM> and a target terminal device group corresponding to the SIB <NUM> shown in Table <NUM> each include only one second terminal device WD#<NUM>. In this case, the multicast message sent by the first terminal device to the target terminal device group may be a unicast message.

It should be understood that the target terminal device group may alternatively include all second terminal devices in the communication connection relationship, the pairing relationship, the association relationship, or a connection relationship with the first terminal device. For example, a target terminal device group corresponding to the SIB <NUM> and a target terminal device group corresponding to the SIB <NUM> shown in Table <NUM> each include all second terminal devices WD#<NUM>-WD#<NUM> communicatively connected to the first terminal device. In this case, the multicast message sent by the first terminal device to the target terminal device group may be a broadcast message.

Optionally, in some implementations, that the first terminal device sends a multicast message to the target terminal device group may be alternatively: When the first terminal device performs or completes cell reselection, intra-frequency handover, inter-frequency handover, and inter-RAT handover, the first terminal device sends the target SI to all terminal devices in the target terminal device group in the multicast manner, and the target terminal device group includes the second terminal device.

To be specific, when the first terminal device performs or completes cell reselection, intra-frequency handover, inter-frequency handover, and inter-RAT handover, the first terminal device sends corresponding target SI to each target terminal device group in the multicast manner, and the target SI is SI required by all second terminal devices in the target terminal device group.

It should be understood that system information types required by different second terminal devices may partially overlap with each other, and therefore a same second terminal device may belong to a plurality of target terminal device groups. Therefore, all system information required by the second terminal device is likely to include a plurality of pieces of target SI, and the plurality of pieces of target SI are included in multicast messages corresponding to different target terminal device groups and sent to the second terminal device.

Alternatively, when the first terminal device detects that a SIB <NUM> in the system information SI changes, the first terminal device sends, to all terminal devices in the multicast manner, an updated SIB <NUM> or a parameter required by the second terminal device in an updated SIB <NUM>.

According to the invention, when the first terminal device detects that a parameter required by the second terminal device in the SIB <NUM> changes, the first terminal device sends, to terminal devices in all terminal device groups in the multicast manner, a parameter required by the second terminal device in an updated SIB <NUM>.

In this implementation of the present disclosure, the first terminal device adds the second terminal device into the target terminal device group and sends the multicast message including the target SI to a terminal device in the target terminal device group, so that all terminal devices in the target terminal device group can receive the target SI required by the terminal device. In this case, the first terminal device does not need to send a same SIB to different terminal devices in a unicast manner, thereby reducing signaling interactions between the first terminal device and the second terminal device. This reduces signaling overheads, avoids resource waste, and helps the first terminal device and the second terminal device save power.

In this implementation of the present disclosure, the first terminal device may send system information required by the second terminal device to the second terminal device based on the capability supported by the second terminal device or directly based on the system information type required by the second terminal device, so that the first terminal device does not send system information unnecessary for the second terminal device to the second terminal device. This reduces signaling overheads between the first terminal device and the second terminal device, and avoids resource waste.

It should be understood that a second terminal device with only a basic capability only needs to receive public system information SI, namely, system information or a parameter required by all second terminal devices, and therefore when obtaining the first indication information, the first terminal device may not obtain first indication information of the second terminal device with only the basic capability.

In <NUM>, the first terminal device sends a broadcast message to the second terminal device.

Optionally, in some implementations, the broadcast message sent by the first terminal device to the second terminal device may be the public system information SI or some parameters in the public system information SI. The public SI or the some parameters in the public SI are system information or parameters in system information that all terminal devices need to receive.

For example, when a D2D connection is established between the first terminal device and the second terminal device, all the following parameters may be some content in the public system information SI broadcast by the first terminal device: parameters in a SIB <NUM> such as a cell identity (Cell ID), a cell barred state, a cell reserved for operator use state, a closed subscriber group identity (CSG Identity), a closed subscriber group indication (CSG Indication), a tracking area code, a system information value tag (SystemInfoValueTag), a category <NUM> allowed (Category <NUM> Allowed) indication, a public land mobile network identity list (PLMN-Identity List), and a system information validity time (SI-Validity Time), and parameters in a SIB <NUM> such as an access control barring factor (ac-Barring Factor), access control barring for emergency (ac-Barring For Emergency), access control barring for mobile originating-data (ac-Barring For Mobile Originating-Data, ac-Barring For MO-Data), access control barring for mobile originating-signaling (ac-Barring For MO-Signaling), access control barring for special access class (ac-Barring For Special AC), and an access control barring time (ac-Barring Time).

Optionally, in some implementations, the broadcast message may be carried in a discovery message or an LTE D2D sidelink master information block message (Master Information Block-SL message).

Optionally, in some implementations, the first terminal device may periodically broadcast the public SI or the some parameters in the public SI to the second terminal device.

In <NUM>, the first terminal device sends target system information SI other than the public SI to the second terminal device.

Optionally, in some implementations, the first terminal device may determine, based on the obtained first indication information, a system information type required by the second terminal device other than the public SI.

Optionally, in some implementations, when the first terminal device receives a paging message indicating a system information change, the first terminal device sends, to the second terminal device, system information other than a master information block MIB, a system information block SIB <NUM>, a SIB <NUM>, a SIB <NUM>, a SIB <NUM>, a SIB <NUM>, and the public SI in the target SI.

Optionally, in some implementations, when the first terminal device receives a paging message indicating an EAB parameter change, the first terminal device sends a SIB <NUM> to the second terminal device supporting the EAB capability.

Optionally, in some implementations, when the first terminal device receives a paging message indicating that there is an ETWS primary notification, the first terminal device sends a SIB <NUM> to the second terminal device supporting the ETWS capability.

Optionally, in some implementations, when the first terminal device receives a paging message indicating that there is an ETWS secondary notification, the first terminal device sends a SIB <NUM> to the second terminal device supporting the ETWS capability.

Optionally, in some implementations, when the first terminal device receives a paging message indicating that there is a CMAS notification, the first terminal device sends a SIB <NUM> to the second terminal device supporting the CMAS capability.

Optionally, in some implementations, after a communication connection relationship, a pairing relationship, an association relationship, or a connection relationship is established between the first terminal device and the second terminal device, the first terminal device sends, to the second terminal device, all SI required by the second terminal device other than the public system information. Optionally, in some implementations, when the first terminal device performs cell reselection, intra-frequency handover, inter-frequency handover, and inter-RAT handover, the first terminal device sends the target SI to the second terminal device, and the target SI is all SI required by the second terminal device other than the public SI.

The SIB <NUM> or some parameters in the SIB <NUM> are the public SI. Therefore, when the first terminal device detects that the SIB <NUM> changes, the first terminal device may send an updated SIB <NUM> or some parameters in an updated SIB <NUM> to all second terminal devices in a broadcast manner.

Optionally, in some implementations, the broadcast message sent by the first terminal device to the second terminal device may be alternatively a discovery message or a master information block-SL message, and the discovery message or the master information block-SL message carries the target SI. The target SI in this case is the SI required by the second terminal device or at least some of the SI required by the second terminal device.

The discovery message or the master information block-SL message is information periodically broadcast by the first terminal device. Therefore, when sending the target SI to the second terminal device, the first terminal device may add the target SI into the discovery message or the master information block-SL message, and broadcast the target SI when the first terminal device broadcasts the discovery message or the master information block-SL message to the second terminal device.

In this implementation of the present disclosure, the first terminal device sends the public SI to all second terminal devices in a broadcast manner, and therefore the public SI required by all the second terminal devices can be sent only once in a broadcast manner, thereby reducing signaling interactions between the first terminal device and the second terminal device. This reduces signaling overheads, avoids resource waste, and helps the first terminal device and the second terminal device save power.

In <NUM>, the first terminal device receives system information broadcast by a base station.

Optionally, in some implementations, when the base station broadcasts the system information to the first terminal device, the broadcast system information is sent to the first terminal device in a form of an RRC message. A MIB and a SIB <NUM> may be broadcast to the first terminal device in a form of two separate RRC messages. Other SIBs are broadcast to the first terminal device by using a plurality of RRC messages, and one RRC message may carry a plurality of other SIBs.

In <NUM>, the first terminal device extracts target SI from the system information broadcast by the base station.

Optionally, in some implementations, the first terminal device may extract, based on the obtained first indication information, the target SI from the system information broadcast by the base station.

In <NUM>, the first terminal device generates an RRC message.

Optionally, in some implementations, the first terminal device may reconstruct the target SI or some parameters in the target SI into the RRC message.

For example, when the second terminal device has only a basic capability, the system information or parameters in the system information that the second terminal device needs to receive may be a parameter in the SIB <NUM> such as a cell identity, a cell barred state, a cell reserved for operator use state, a closed subscriber group identity, a closed subscriber group indication, a tracking area code, a system information value tag, a category <NUM> allowed indication, a public land mobile network identity list, or a system information validity time, and a parameter in a SIB <NUM> related to access control such as an access control barring factor, access control barring for emergency, access control barring for mobile originating-data, access control barring for mobile originating-signaling, access control barring for special access class, or an access control barring time. The first terminal device may generate an RRC message including the foregoing parameter, so that the first terminal device does not need to send another parameter not required by the second terminal device in the SIB <NUM> and the SIB <NUM> to the second terminal device. This reduces signaling interactions between the first terminal device and the second terminal device, avoids resource waste, and helps the first terminal device and the second terminal device save power.

For another example, the second terminal device supporting the SSAC capability not only needs the foregoing parameters in the SIB <NUM> and the SIB <NUM>, but also needs an SSAC-related parameter in the SIB <NUM>, for example, service specific access control baring for multimedia telephony video (ssac-Barring For MMTEL-video) or service specific access control barring for multimedia telephony voice (ssac-Barring For MMTEL-voice). In this case, the first terminal device may reconstruct one or more SIBs and/or a parameter in one or more SIBs in SI required by the second terminal device supporting the SSAC capability, into one RRC message.

For still another example, the second terminal device supporting the ACDC capability further needs an ACDC-related parameter in the SIB <NUM>, for example, an ACDC application specific congestion control for data communication barring configuration (acdc-Barring Config), an ACDC application specific congestion control for data communication category (acdc-Category), an ACDC only for home public land mobile network (acdc-Only For HPLMN) indication, or a barring per ACDC-category list (barring Per ACDC-Category List). In this case, the first terminal device may reconstruct one or more SIBs and/or a parameter in one or more SIBs in SI required by the second terminal device supporting the ACDC capability, into one RRC message.

For yet another example, the second terminal device supporting a multimedia broadcast multicast service (MBMS) capability not only needs the foregoing parameters in the SIB <NUM> and the SIB <NUM>, but also needs a SIB <NUM> and a SIB <NUM>. In this case, the first terminal device may reconstruct one or more SIBs and/or a parameter in one or more SIBs in SI required by the second terminal device supporting the MBMS capability, into one RRC message.

In <NUM>, the first terminal device sends the RRC message to the second terminal device.

After the first terminal device extracts, based on the first indication information, the target SI from the system information required by the second terminal device and generates the RRC message, the first terminal device sends the RRC message to the second terminal device, and the RRC message carries all or some system information required by the second terminal device, namely, the target SI.

In this implementation of the present disclosure, when generating the RRC message, the first terminal device may extract only some parameters in a SIB and generate the RRC message, and the some parameters are parameters required by the second terminal device at a current moment, and therefore the first terminal device can neither send system information not required by the second terminal device to the second terminal device, nor send some parameters not required by the second terminal device in the system information to the second terminal device, and the first terminal device can further reconstruct a plurality of pieces of system information required by the second terminal device into one RRC message. This better helps reduce signaling interactions between the first terminal device and the second terminal device, reduce signaling overheads, and avoid resource waste, and helps the first terminal device and the second terminal device save power.

The foregoing describes the method implementations of the implementations of the present disclosure in detail with reference to <FIG>. The following describes terminal device implementations of the implementations of the present disclosure in detail with reference to <FIG>. It should be understood that the terminal device implementations and the method implementations correspond to each other, and for similar descriptions, reference may be made to the method implementations.

<FIG> is a schematic block diagram of a terminal device <NUM> according to an implementation of the present disclosure. As shown in <FIG>, the terminal device <NUM> includes:.

In this implementation of the present disclosure, the terminal device <NUM> can determine, based on the first indication information of the second terminal device obtained by the processing module <NUM>, the system information SI required by the second terminal device, so that the terminal device <NUM> sends the system information required by the second terminal device to the second terminal device by using the sending module <NUM>. This reduces signaling interactions between the first terminal device and the second terminal device, reduces signaling overheads, and avoids resource waste.

Optionally, in some implementations, the first indication information is used to indicate a capability supported by the second terminal device.

Optionally, in some implementations, the first indication information is used to indicate SI required by the second terminal device.

The processing module <NUM> is further configured to determine, based on the capability supported by the second terminal device, the SI required by the second terminal device.

The processing module <NUM> is further configured to add the second terminal device into a target terminal device group, where all terminal devices in the target terminal device group require the target SI.

The sending module <NUM> is specifically configured to send a multicast message to the terminal devices in the target terminal device group, where the multicast message includes the target SI.

Optionally, in some implementations, the sending module <NUM> is further configured to send a first broadcast message to the second terminal device, where the first broadcast message includes public SI.

Optionally, in some implementations, the sending module <NUM> is further configured to send a second broadcast message to the second terminal device, where the second broadcast message is a discovery message or a master information block-SL message, and the discovery message or the master information block-SL message carries the target SI. The target SI in this case is the SI required by the second terminal device or at least some of the SI required by the second terminal device.

It should be understood that the public SI is SI required by all second terminal devices or some parameters in SI required by all second terminal devices.

Optionally, the terminal device <NUM> further includes:
a receiving module <NUM>, configured to receive system information broadcast by the base station.

Optionally, in some implementations, the processing module <NUM> is further configured to extract the target SI from the system information broadcast by the base station and generate a Radio Resource Control RRC message, where the RRC message includes the target SI.

Optionally, in some implementations, the sending module <NUM> is further configured to send the RRC message to the second terminal device.

Optionally, in some implementations, the processing module <NUM> is specifically configured to receive the first indication information sent by the second terminal device.

Optionally, in some implementations, the processing module <NUM> is further configured to receive the first indication information sent by the base station or a mobility management entity MME.

Optionally, in some implementations, the sending module <NUM> is further configured to: when the terminal device receives a paging message indicating a system information change, send, to the second terminal device, system information other than a master information block MIB, a system information block SIB <NUM>, a SIB <NUM>, a SIB <NUM>, a SIB <NUM>, and a SIB <NUM> in the target SI.

Optionally, in some implementations, the sending module <NUM> is further configured to: when the terminal device <NUM> receives a paging message indicating an EAB parameter change, send an updated SIB <NUM> to the second terminal device.

Optionally, in some implementations, the sending module <NUM> is further configured to: when the terminal device <NUM> receives a paging message indicating that there is an ETWS primary notification, send a SIB <NUM> to the second terminal device.

Optionally, in some implementations, the sending module <NUM> is further configured to: when the terminal device <NUM> receives a paging message indicating that there is an ETWS secondary notification, send a SIB <NUM> to the second terminal device.

Optionally, in some implementations, the sending module <NUM> is further configured to: when the terminal device <NUM> receives a paging message indicating that there is a CMAS notification, send a SIB <NUM> to the second terminal device.

Optionally, in some implementations, the sending module <NUM> is further configured to: after a communication connection relationship, a pairing relationship, or an association relationship is established between the terminal device <NUM> and the second terminal device, send the target SI to the second terminal device.

Optionally, in some implementations, the sending module <NUM> is further configured to: when the terminal device <NUM> performs or completes cell reselection and handover, send the target SI to the second terminal device.

Alternatively, the sending module <NUM> is further configured to: when the terminal device <NUM> detects that a SIB <NUM> changes, send, to the second terminal device, an updated SIB <NUM> or a parameter required by the second terminal device in an updated SIB <NUM>.

According to the invention, the sending module <NUM> is further configured to: when the terminal device <NUM> detects that a parameter required by the second terminal device in a SIB <NUM> changes, send, to the second terminal device, a parameter required by the second terminal device in an updated SIB <NUM>.

It should be understood that the terminal device <NUM> according to this implementation of the present disclosure may be corresponding to the first terminal device in the implementations of the present disclosure. In addition, both the foregoing and other operations and/or functions of the modules in the terminal device <NUM> are to implement corresponding procedures of the methods in <FIG>. For brevity, details are not repeated herein.

<FIG> is a schematic structural diagram of a terminal device <NUM> according to an implementation of the present disclosure. As shown in <FIG>, the terminal device <NUM> includes:.

In this implementation of the present disclosure, the terminal device <NUM> sends the first indication information to the first terminal device by using the sending module <NUM>, so that the first terminal device determines the system information SI required by the terminal device <NUM>, and the target SI received by the terminal device <NUM> by using the receiving module <NUM> is the SI required by the terminal device <NUM> or at least some of the SI required by the terminal device <NUM>. This reduces signaling interactions between the first terminal device and the terminal device <NUM>, reduces signaling overheads, and avoids resource waste.

Optionally, in some implementations, the first indication information may be used to indicate a capability supported by the terminal device.

Optionally, in some implementations, the first indication information may be alternatively used to indicate the SI required by the terminal device.

Optionally, in some implementations, the receiving module <NUM> is specifically configured to receive a multicast message sent by the first terminal device to a target terminal device group, and all terminal devices in the target terminal device group require the target SI, and the multicast message includes the target SI.

Optionally, in some implementations, the receiving module <NUM> is further configured to receive a first broadcast message sent by the first terminal device, where the first broadcast message includes public SI.

Optionally, in some implementations, the receiving module <NUM> is further configured to receive a second broadcast message sent by the terminal device <NUM>, where the second broadcast message is a discovery message or a master information block-SL message, and the discovery message or the master information block-SL message carries the target SI. The target SI in this case is the SI required by the terminal device <NUM> or at least some of the SI required by the terminal device <NUM>.

It should be understood that the public SI is SI required by all terminal devices <NUM> or some parameters in SI required by all terminal devices <NUM>.

Optionally, in some implementations, the receiving module <NUM> is further configured to receive a Radio Resource Control RRC message generated by the first terminal device, where the RRC message includes the target SI.

It should be understood that the terminal device <NUM> according to this implementation of the present disclosure may be corresponding to the terminal device <NUM> in the implementations of the present disclosure. In addition, both the foregoing and other operations and/or functions of the modules in the terminal device <NUM> are to implement corresponding procedures of the methods in <FIG>. For brevity, details are not repeated herein.

<FIG> is a schematic structural diagram of a terminal device <NUM> according to an implementation of the present disclosure. As shown in <FIG>, the terminal device <NUM> includes a memory <NUM> and a processor <NUM>. The memory <NUM> and the processor <NUM> communicate with each other through an internal connection path to transfer control and/or data signals.

The memory <NUM> is configured to store program code.

The processor <NUM> is configured to invoke the program code to implement the methods in the foregoing implementations of the present disclosure.

In this implementation of the present disclosure, the processor <NUM> may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP. The processor may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. An implementation of the present disclosure provides a computer readable medium, configured to store computer program code. The computer program includes instructions used to perform the methods for transmitting system information according to the implementations of the present disclosure in <FIG>. The readable medium may be a read-only memory (ROM) or a random access memory (RAM). This is not limited in this implementation of the present disclosure.

A person of ordinary skill in the art may be aware that, units and algorithm steps in the examples described in the implementations disclosed in this specification can be implemented by electronic hardware or a combination of computer software and electronic hardware.

In the several implementations provided in this application, it should be understood that the disclosed system, apparatus, and method may be implemented in other manners. For example, the described apparatus implementation is merely an example. The indirect couplings or communication connections between the apparatuses or units may be implemented in electrical, mechanical, or other forms.

Some or all of the units may be selected based on actual requirements to achieve the objectives of the solutions of the implementations.

In addition, functional units in the implementations of this application may be integrated into one processing unit, or each of the units may exist alone physically, or two or more units are integrated into one unit.

Claim 1:
A method for transmitting system information, wherein the method comprises:
obtaining (<NUM>), by a first terminal device, first indication information;
determining (<NUM>), by the first terminal device based on the first indication information, system information SI required by a second terminal device, wherein the second terminal device communicates with a base station via the first terminal device; and
sending (<NUM>), by the first terminal device, a message comprising target SI to the second terminal device, wherein the target SI is some or all of the SI required by the second terminal device;
wherein the sending, by the first terminal device, a message comprising target SI to the second terminal device comprises:
adding, by the first terminal device, the second terminal device into a target terminal device group, wherein all terminal devices in the target terminal device group require the target SI; and
sending, by the first terminal device, a multicast message to the terminal devices in the target terminal device group, wherein the multicast message comprises the target SI;
wherein the sending, by the first terminal device, a message comprising target SI to the second terminal device comprises:
when the first terminal device detects that a parameter required by the second terminal device in a SIB <NUM> changes, sending, by the first terminal device to the second terminal device, a parameter required by the second terminal device in an updated SIB <NUM>;
wherein the first indication information comprises information indicating a capability supported by the second terminal device; and
the determining, by the first terminal device based on the first indication information, SI required by a second terminal device comprises:
determining, by the first terminal device based on the information about the capability supported by the second terminal device, the SI required by the second terminal device; or
wherein the first indication information comprises information indicating a type of the SI required by the second terminal device.