Patent Application
20240098697
This disclosure is directed generally to wireless communications, and particularly to a method, device, and system for transmitting and receiving paging indication.
Controlling power consumption and reducing energy cost are critical for developing and deploying a wireless communication network. In a wireless communication employing various paging mechanisms, increasing paging success rate while reducing power consumption has always been an important goal. Efficient signaling between the wireless communication network and the mobile devices in a paging process is critical for reducing false paging detection rate and improving power efficiency.
This disclosure is directed to a method, device, and system for transmitting and receiving paging indication in wireless communications.
In some embodiments, a method performed by a wireless communication node in a wireless network is disclosed. The method may include determining whether a predetermined condition is met; and in response to the predetermined condition being met, transmitting a Downlink Control Information (DCI) to a UE in the wireless network, wherein the DCI is scramble by a Radio Network Temporary Identification (RNTI) and comprises a paging indication, and wherein the paging indication indicates whether the UE is to receive a next coming paging occasion.
In some embodiments, a method performed by a UE in a wireless network is disclosed. The method may include receiving a Downlink Control Information (DCI) from a wireless communication node in the wireless network, wherein the DCI is scramble by a Radio Network Temporary Identification (RNTI) and comprises a paging indication, and wherein the paging indication indicates whether the UE is to receive a next coming paging occasion; resolving the paging indication from the DCI in response to determining that a predetermined condition is met; and determining whether the UE is to receive the next coming paging occasion based on the paging indication.
In some embodiments, there is a UE and/or a wireless communication node comprising a processor and a memory, wherein the processor is configured to read code from the memory and implement any methods recited in any of the embodiments.
In some embodiments, a computer program product comprising a computer-readable program medium code stored thereupon, the code, when executed by a processor, causing the processor to implement any method recited in any of the embodiments.
The above embodiments and other aspects and alternatives of their implementations are described in greater detail in the drawings, the descriptions, and the claims below.
The gNB 124 may include a central unit (CU) and at least one distributed unit (DU). The CU and the at least one DU may be co-located, or they may be split in different locations. The CU and the DU may be connected via an F1 interface. Alternatively, for an eNB which is capable of connecting to the 5G network, it may also be similarly divided into a CU and at least one DU, referred to as ng-eNB-CU and ng-eNB-DU, respectively. The ng-eNB-CU and the at least one ng-eNB-DU may be connected via a W1 interface.
The wireless communication network 100 may include one or more tracking areas. A tracking area may include a set of cells managed by at least one base station. For example, tracking area 1 labeled as 140 includes cell 1, cell 2, and cell 3, and may further include more cells that may be managed by other base stations and not shown in
The wireless communication network 100 may be implemented as, for example, a 2G, 3G, 4G/LTE, or 5G cellular communication network. Correspondingly, the base stations 122 and 124 may be implemented as a 2G base station, a 3G NodeB, an LTE eNB, or a 5G NR gNB. The UE 160 may be implemented as mobile or fixed communication devices which are capable of accessing the wireless communication network 100. The UE 160 may include but is not limited to mobile phones, laptop computers, tablets, personal digital assistants, wearable devices, Internet of Things (IoT) devices, MTC/eMTC devices, distributed remote sensor devices, roadside assistant equipment, XR devices, and desktop computers. The UE 160 may support sidelink communication to another UE via a PC5 interface.
While the description below focuses on cellular wireless communication systems as shown in
The electronic device 200 may also include system circuitry 204. System circuitry 204 may include processor(s) 221 and/or memory 222. Memory 222 may include an operating system 224, instructions 226, and parameters 228. Instructions 226 may be configured for execution by the one or more of the processors 221 to perform the functions of a network node. The parameters 228 may include parameters to support execution of the instructions 226. For example, the parameters may include network protocol settings, bandwidth parameters, radio frequency mapping assignments, and/or other parameters.
Referring to
Referring to
In the wireless communication system, a UE may connect with the base station via an Over The Air (OTA) interface. If there is an active communication session associated with the UE and the base station, then the status of the connection between the UE and the base station is active and the UE is in an active mode. On the other hand, if there is no active communication session between the UE and the base station, then the UE moves to an idle state or inactive state, for example, a Radio Resource Control (RRC) idle state or an RRC inactive state. The UE limits its usage of the radio resources during the idle state or inactive state and may reduce power consumption by using various techniques including but not limited to Discontinuous Reception (DRX).
In DRX, resource monitoring and communication activities are managed in cycles, referred to as DRX cycles, or paging cycles.
After receiving the paging DCI 412, the UE may further receive a paging message 414 which is scheduled by the paging DCI 412 and is carried on a physical downlink shared channel (PDSCH). However, the paging message 414 may target another UE and may not be for this UE. For example, in a case that the paging message 414 does not contain the 5th Generation System Temporary Mobile Subscription Identifier (5G-S-TMSI) of this UE, a false detection may occur if the UE receives and decodes paging messages not targeting itself. Such false detection leads to energy waste for this UE. Therefore, if the UE can avoid detecting paging message not intended for itself, power consumption may be reduced.
In some implementations, an indication mechanism may be employed in a paging process. As shown in
In some implementations, in the wireless communication network, UEs may be assigned or configured into different paging groups (or UE groups). For example, there may be 10 paging groups, each paging group containing 10 UEs. The paging indication 416 (or may be referred to as paging indication signal, paging indication information) may indicate targeted paging group(s). If the UE does not belong to any targeted paging group, then the UE may skip the reception of paging message and/or paging DCI.
A base station may send a paging indication to the UE via a control message, for example, a DCI.
The DCI includes multiple non-reserved fields. Each non-reserved field may carry different type of information. For example, a Modulation and Coding Scheme (MCS) field in the DCI may convey MCS related information; a Frequency domain resource assignment field may convey frequency domain resource allocation information, etc. The DCI may also include a reserved bits field (or reserved field) which contains multiple reserved bits.
In this disclosure, to at least re-use the existing DCI and improve signaling and decoding efficiency, various embodiments are disclosed to re-interpret or re-purpose one or more DCI fields. The re-interpretation may be based on a pre-condition which will be described in great detail below. Under such implementations, a DCI field may possess a polymorphism property. That is, in a default condition, the DCI field is interpreted as carrying default (or original) information, whereas when the pre-condition is satisfied, the same DCI field is interpreted as carrying different type of information other than the default information. For example, under default condition, the MCS field carries MCS related information. When a pre-condition is met, the MCS field may carry the paging indication. For another example, under default condition, the reserved field is reserved. When a pre-condition is met, the reserved field may be used to carry the paging information.
In some implementations, both reserved field and non-reserved field may be used for joint paging indication.
In some implementations, only reserved field(s) is used.
In some implementations, only non-reserved field(s) is/are used.
In some implementations, all bits in a field are used.
In some implementations, only a portion of the bits of a field is used. The selection of the portion of the bits may be pre-determined or configured by higher layer signaling.
In some implementations, a bitmap formed by the DCI field(s) may be used for paging indication. For example, each bit in the bitmap corresponds to or indicate a paging group. For example, when a bit is set to “1”, the corresponding paging group is selected or targeted; when bit is set to “0”, the corresponding paging group is not selected.
In some implementations, the codepoint in the DCI field(s) may be used for paging indication. For example, each codepoint corresponds to a paging group. When the field is set to a particular codepoint, the corresponding paging group is selected or targeted. The codepoint is the binary value of the bits in the DCI field. For example, if the DCI field contains 3 bits set to binary “101”, then the codepoint is decimal 5.
The pre-condition for DCI field re-interpretation may include a particular DCI field being set to a specific value, or multiple DCI fields each being set to a specific value. Table 1 below shows exemplary DCI values for indicating a pre-condition.
For example, as shown in Table 1, the pre-condition may be that the MCS field is set to zero, or the TB scaling field is set to one. For another example, the pre-condition may be that the MCS field is set to zero whereas the TB scaling field is set to one.
In some embodiments, when the UE decodes the DCI, if the UE determines that the aforementioned pre-condition is met, the UE may interpret the reserved field as carrying paging information. For example, the UE may interpret that the whole reserved field is used for carrying paging information, or the UE may interpret that partial bits of the reserved field are used for carrying paging information.
Various embodiments for implementing paging indication are described in further detail below.
In this embodiment, the paging indication may be transmitted from a base station to a UE via a DCI. The DCI may be a format 1_0 DCI with cyclic redundancy check (CRC) scrambled by a Paging Radio Network Temporary Identification (P-RNTI). This particular DCI format has an identical bit size as a DCI that schedules system information (SI). The DCI includes non-reserved fields as listed in Table 1 above.
As described in Table 1, these non-reserved DCI fields may be used for indicating DCI re-interpretation when setting to a specific value. The specific value of each field listed in Table 1 is for exemplary purpose and may be set to other pre-determined values. For example, the bits in each field may be set to all 1, all 0, or other pre-determined patterns.
Some other exemplary pre-conditions are listed below.
In one implementation, the pre-condition may be that, in the DCI, all the bits before the TB scaling bits are set to zero and the TB scaling bits are all one (i.e., ‘11’).
In another implementation, the pre-condition may be that the value corresponding to the MCS fields is a reserved value (e.g., 29, 30, 31).
In another implementation, the pre-condition may be that the value corresponding to the MCS field indicates a modulation order that is higher than 2 (e.g., 10, 11, . . . , 28). Alternatively, the pre-condition may be that the value corresponding to the MCS field is higher than or equal to a specific value (e.g., 8, 9, 10, . . . , 31).
In another implementation, the pre-condition may be that the value corresponding to the MCS field is a specific value (e.g., 31, all one in binary), and the number of RBs allocated as indicated by the “Frequency domain resource assignment” field is a specific value (e.g., all 1, or all 0 in binary). Alternatively, the pre-condition may be that the value corresponding to the MCS field is a specific value (e.g., 31, all one in binary) and the number of RBs allocated as indicated by the “Frequency domain resource assignment” field is less than or equal to a specific value (e.g., 4).
The reserved bits in the reserved bits field may have 8 bits, for example, when a cell is operated in a shared spectrum channel access mode. Otherwise the reserved bits field may have 6 bits.
In one implementation, when there are 8 reserved bits which may be interpreted for paging indication, if the number of paging groups (N) is less than or equal to 8, then the first N bits may be used for paging indication (e.g., one bit for one paging group) while the rest 8-N bit(s) of the 8 bits remains reserved.
Likewise, when there are 6 reserved bits which may be interpreted for paging indication, if the number of groups (N) is less than or equal to 6, then the first N bits may be used for paging indication (e.g., one bit for one paging group) while the rest 6-N bit(s) of the 6 bits remains reserved.
In one implementation, when there are 6 reserved bits which may be interpreted for paging indication, if the number of groups N is greater than 6, then the first M=5 bits may be used for paging indication (e.g., one bit for one paging group) for the first M paging groups while the last bit may be used to indicate the last N-M paging group(s). See Table 2 below for an example. For simplicity, the group in the table refers to the paging group.
In one implementation, when the bit used for paging indication is set to “1”, the corresponding paging group is targeted. The UE in the targeted paging group will wake up and receive a coming paging DCI in a next PO, and the UE may further need to receive the paging message from the PDSCH according to the received paging DCI. Otherwise when the bit used for paging indication is set to “0”, the addressed paging group is not targeted. The UE in the un-targeted paging group will remain in sleep mode, or skip the reception of the next PO and/or the paging message. For example, in Table 2, if the second bit is set to 1, the addressed paging group (i.e., the second paging group) is targeted. If the UE is in the second paging group, then the UE would wake up in the next PO to detect the paging DCI and may further receive the paging message according to the received paging DCI. For another example, in Table 2, if the third bit is set to 0, the corresponding paging group (i.e., the third paging group) is not targeted. If the UE is in the third paging group, then the UE will remain in sleep mode during the next PO.
In one implementation, the indication values may be swapped from the above implementation: “1” means not targeted, and “0” means targeted.
In one implementation, if the indication bit is set to “0”, the UE in the corresponding paging group will perform one of: take no action; keep current state; go to sleep; or skip receiving the coming paging DCI, and/or the paging message on the PDSCH.
In one implementation, how UE reacts to the paging indication bit may be determined or configured by higher layer.
In one implementation, when there are 6 reserved bits that may be interpreted for paging indication, if the number of paging groups (N) is greater than 6, then the first M=4 bits are used for paging indication (e.g., one bit for one paging group) for the first M paging groups while the (M+1)th bit is used to indicate the (M+1)th and the (M+2)th group, and the last bit is used to indicate the last N−M−2 paging group(s). See Table 3 below for an example.
Alternatively, 4 bits out of the 6 reserved bits may be used to address paging groups with each bit addressing 2 paging groups. The rest 2 bits may be used for other purpose. See Table 4 and Table 5 below for examples.
In one implementation, when the DCI is a paging DCI (whose CRC is scrambled by P-RNTI) and the DCI is used to indicate paging information including the paging group, the “Reserved bits” and a sub-set of “MCS bits” may be used to indicate paging group. See Table 6 and Table 7 below for examples.
In one implementation, when the DCI is a paging DCI and the DCI is used to indicate paging information including the paging group, only the “Reserved bits” are used to indicate paging group, and no bit from other non-reserved field is used. Refer to Table 8 below for an example.
In this embodiment, a UE, upon receiving a DCI configured for paging indication, may know whether the paging group to which the UE belongs is targeted (or paged, indicated). This embodiment is also backward compatible and is transparent to UEs which are not configured to support features in this embodiment, as these UEs may just ignore the paging indication information without causing faulty behavior.
Using this embodiment, the decoding performance of paging indication may be improved. For example, as shown in
In
In this embodiment, a codepoint of a DCI field may be used as paging indication. A codepoint may be the formed by all the bits in the DCI field, or a partial of all the bits in the DCI field.
In addition to the exemplary pre-conditions for DCI field re-interpretation listed above, some more exemplary pre-conditions are listed below.
In one implementation, the pre-condition may be that the MCS field is set to a specific value, such as MCS=31 (i.e. 5 MCS bits are set to all one).
In one implementation, the pre-condition may be that MCS=31 and the value (i.e., the codepoint) of the TB scaling fields is set to 3 in decimal (“11” in binary format).
In this embodiment, in addition to indicate paging information, the reserved bit field may also indicate other type of information simultaneously. For example, there may be K reserved bits (with K equal to 6, 8, or more) in the reserved bits field. P out of the K bits may be selected to indicate paging group, while the remaining K−P bit(s) may be used for other purpose (e.g., for tracking reference signal (TRS) indication information, channel state information reference signal (CSI-RS) indication, or TRS/CSI-RS availability indication). Both K an P are integers, and P is less than K.
In one implementation, a paging DCI (whose CRC is scrambled by P-RNTI) may be used to indicate paging information. In particular, the codepoint formed by the reserved bits (in the reserved bit field) may be used to indicate paging information.
In one implementation, when a pre-condition (e.g., a pre-condition as described above) is true, information other than paging information may be indicated by re-interpreting existing DCI field. For example, the “Frequency domain resource assignment field”, and/or the “Time domain resource assignment field” may be used to indicate TRS/CSI-RS availability information.
In one implementation, when a pre-condition is met, one or more bit in an DCI field (e.g., the reserved bit field, the “Frequency domain resource assignment field”, or the “Time domain resource assignment field”) may be used to indicate the availability of one TRS/CSI-RS resource set, or the availability of one group of TRS/CSI-RS resource sets.
In one implementation, when a pre-condition is met, a codepoint of an DCI field (e.g., the reserved bit field, the “Frequency domain resource assignment field”, or the “Time domain resource assignment field”) may be used to indicate the availability of one TRS/CSI-RS resource set, or the availability of one group of TRS/CSI-RS resource sets.
In one implementation, when a pre-condition is met, a sub-set (i.e., partial bits) of the re-interpreted field is used to indicate channel state information reference signal (CSI-RS) availability.
In one implementation, when a pre-condition is met, if the reserved bit field has K bits, then P=4 bits out of the K bits may be selected to indicate paging information while the remaining (K−P) bits may be used to indicate TRS/CSI-RS availability information. For example, the decimal value 0, 1, 2, and 3 of the remaining (K−P) bits indicate the availability of the first, the second, the third, and the fourth group of TRS/CSI-RS resource sets, respectively.
In one implementation, when a pre-condition is met, a bitmap formed by a DCI field may be used for TRS/CSI-RS availability indication. For example, the first bit indicates the availability of the first group TRS/CSI-RS resource set, and the second bit indicates the availability of the second group TRS/CSI-RS resource set, etc.
Table 9 below shows an example in which a bitmap formed by 4 bits of the reserved bits field are used to indicate paging information.
In one implementation, one bit of the reserved bits field is used to indicate a UE behavior. For example, the UE behavior may include UE behavior A (e.g., waking up) and UE behavior B (e.g., going to sleep, staying in sleep state). In this implementation, the UE behavior A or B may be indicated at the same time and in the same DCI when indicating paging group.
Table 10 below shows an exemplary DCI reserved bit field re-interpretation in which the second bit is used to indicate UE behavior, and a codepoint is used for paging indication.
Using this embodiment, the decoding performance of paging indication is improved. For example, as shown in
In this embodiment, a UE, upon receiving a DCI configured for paging indication, may know whether the paging group to which the UE belongs is targeted (or paged, indicated). This embodiment is also backward compatible and is transparent to UEs which are not configured to support features in this embodiment, as these UEs may just ignore the paging indication information without causing faulty behavior.
In this embodiment, the paging indication may be transmitted from a base station to a UE via a DCI. The pre-condition for DCI field re-interpretation may be similar to or following the same principles as described in embodiment 1 and is not duplicated.
In one implementation, a 2-bits Short Messages Indicator field in the DCI may be included. An exemplary interpretation of this field is shown in Table 11 below.
The Short Messages field of the DCI has a bit-width of 8. If the “Short Messages Indicator” described above is “00” or “01”, then this bit field is reserved. Otherwise, these bits will carry short messages from higher layer.
The reserved bits in the reserved bits fields may be interpreted as paging indication under certain pre-conditions. For example, when the TB scaling field in the same DCI is set to a pre-determined value, the reserved bits may be interpreted as paging indication. If there are 8 reserved bits in the reserved bits field, each bit may be associated with one paging group (up to 8 paging groups). For 6 reserved bits, an exemplary interpretation is listed in Table 12 below.
For 8 reserved bits in the reserved bits field, Table 13 below shows exemplary interpretation of the reserved bits.
In one implementation, when a pre-condition as described above is met, there are 8 reserved bits in the reserved bits fields which need to be re-interpreted.
In one implementation, when a pre-condition as described above is met, there are up to 8 reserved bits in the reserved bits fields (e.g., 4, 5, 6, 7, or 8 bits) which need to be re-interpreted. The selection of these reserved bits may be pre-determined, or configured by higher layer signalling.
In this embodiment, one or more non-reserved field of the DCI may be combined with the reserved bits field to indicate paging information.
For example, when a pre-condition is met, the VRB-to-PRB mapping field may be re-interpreted to indicate paging information.
For another example, the MCS field may be re-interpreted to indicate paging information. In one implementation, the MCS field has 5 bits. When the first four bits are all set to zero, the last bit may be re-interpreted to indicate paging information.
In this embodiment, more exemplary pre-conditions for DCI field re-interpretation are described below.
For example, the Time domain resource assignment field has 4 bits. The pre-condition may be that all these 4 bits are set to zero.
For another example, the pre-condition may include: the time domain resource assignment field is set to a specific value (e.g., 15 in decimal), and the CRC of the DCI that carries the paging indication is scrambled by P-RNTI. Alternatively, the pre-condition may further include that the DCI is in a common search space. Alternatively, the pre-condition may further include that the DCI is in a PDCCH Type0 common search space.
For another example, the pre-condition may include: the “Frequency domain resource assignment bits” field and the “TB scaling bits” field have a specific value (e.g., all one).
Table 14 below shows exemplary paging information interpretation in which both non-reserved fields and reserve bits field are used.
Table 14 above shows only an exemplary manner to use the bits in various fields to indicate paging groups. Other bit combinations following different order to indicate paging groups may also be implemented under the principles described above. For example, the first bit of the reserved bits may be used to indicate the eighth paging group.
Table 15 below shows another exemplary paging information interpretation in which both non-reserved fields and reserve bits field are used.
Table 16 below shows another exemplary paging information interpretation in which both non-reserved fields and reserve bits field are used.
Table 17 below shows another exemplary paging information interpretation in which both non-reserved fields and reserve bits field are used.
In one implementation, the meaning or interpretation of a bit field may depend on a second level condition (where first level condition may be one of the pre-conditions described above). In this case, the first level condition determines whether a DCI field should be interpreted as its default usage, or should be re-interpreted (e.g., re-interpreted for paging indication purpose). Once the first level condition is met, the second level condition further determines how to interpret the field. For example, the meaning of “VRB-to-PRB mapping” filed or the last bit of the Reserved bits field depends on some second level condition. The second level condition may be based on the number of PO in a paging frame (i.e., Ns). Refer to Table 18 below for an example.
In this embodiment, the paging indication may be transmitted from a base station to a UE via a DCI.
In one implementation, the CRC of this DCI may be scrambled by a RNTI different from the P-RNTI. For example, the RNTI may include a system information RNTI (SI-RNTI, 0xFFFF in hex). For another example, the RNTI may be configured by higher layer (e.g., configured as 0xFFFF in hex).
In one implementation, when the CRC of the DCI is scrambled by an RNTI which is different from the P-RNTI, the UE only needs to re-interpret the DCI fields (e.g., non-reserved field or reserved bits field) which carry paging indication information. In one implementation, the UE may further assume that the DCI only contains field(s) for paging indication purpose. In one implementation, the UE may assume that the DCI only contains field(s) for paging indication. In one implementation, the UE may assume that the DCI only contains field(s) for paging indication and/or TRS/CSI-RS availability indication. In one implementation, the UE may assume that the DCI only contains field(s) for paging indication and/or TRS/CSI-RS availability indication and/or Short Messages.
In one implementation, when the CRC of the DCI is scrambled by a RNTI which is different from the P-RNTI (e.g., an SI-RNTI), only w bits out of all the reserved bits in the reserved bits field are used for indicating paging information, where w is the number of paging groups that is configured by higher layer.
In one implementation, only w+1 bits out of all the reserved bits in the reserved bits field are used for indicating paging information, in which w bits indicate paging groups and the additional one bit is used for future extension.
In one implementation, only w+1 bits out of all the reserved bits in the reserved bits field are used for indicating paging information, in which w bits indicate paging groups and the additional one bit is used to indicate UE behavior. The UE behavior may include a UE behavior A (e.g., waking up to receive a coming paging DCI and/or paging message) and a UE behavior B (e.g., going to sleep, keeping at sleep). When the UE behavior is indicated, a UE in a corresponding paging group will follow the indicated behavior. It is to be understood that in some implementations, there is no need to indicate the UE behavior. In this case, the default behavior may be pre-determined.
In this embodiment, a specific value of a DCI field may be used to determine whether other fields need to be re-interpreted. For example, when all bits in the Frequency domain resource assignment field is set to one, or when the Frequency domain resource assignment field is set to a pre-determined value, the VRB-to-PRB mapping field, the MCS field, or the TB scaling field may be re-interpreted as carrying paging indication information.
In this embodiment, a specific value of a DCI field may also carry other paging indication related information. For example, when the Frequency domain resource assignment field is set to decimal 511, it indicates that the paging indication carried in the DCI applies to just one PO (e.g., the next coming PO). When the Frequency domain resource assignment field is set to decimal 510, it indicates that the paging indication carried in the DCI applies to multiple POs (e.g., Ns POs, where Ns is the number of POs in a paging frame). The specific value of the DCI field may be pre-determined or be configure by higher layer.
Similarly, the example above may apply to other DCI fields. For example, a specific value may be set for the time domain resource assignment field, to determine whether other fields need to be re-interpreted.
Table 19 below shows an example in which various non-reserved DCI fields are used to indicate paging information.
Table 20 below shows another example in which various non-reserved DCI fields are used to indicate paging information.
Table 21 below shows another example in which various non-reserved DCI fields are used to indicate paging information.
In this embodiment, the paging indication may be transmitted from a base station to a UE via a DCI. The CRC of the DCI may be scrambled by a power saving RNTI.
The DCI may include a paging indication field which has Y bits (Y is an integer). Each bit corresponds to a paging group. For example, the i-th bit (counting from most significant bit (MSB), or from the least significant bit (LSB)) corresponds to the i-th paging group.
In one implementation, the paging indication field may include an additional bit (i.e., Y+1 bits total). This additional bit may be used to indicate a UE behavior, such as the UE behavior A or UE behavior B as described above.
In one implementation, the paging indication field may include ceil(log 2(Y)) bits where Y is the number of paging groups configured by higher layer, ceil( ) represents a ceiling operation that fetches a minimum integer which is not lower than the operand, and log 2( ) is logarithm of base 2. A codepoint of these bits may be used to indicate paging information.
In this embodiment, the DCI carrying the paging indication information has a small footprint (i.e., the size of the DCI is small). Thus, the signaling overhead is reduced and the coverage performance is improved. Meanwhile, from a UE power consumption perspective, as unnecessary paging reception is avoided from the UE side, the power consumption is reduced.
In this embodiment, in addition to normal paging message scheduling, a paging DCI may be assigned a new function related to paging indication. For example, a paging DCI in a previous paging cycle may carry paging indication for a current paging cycle, or a paging DCI in a current paging cycle may carry paging indication for a next paging cycle.
Similarly, a paging DCI in a previous paging cycle may carry TRS/CSI-RS availability information for a current paging cycle, or a paging DCI in a current paging cycle may carry TRS/CSI-RS availability information for a next paging cycle.
In one implementation, the paging DCI in previous paging frame(s) for one UE may indicate paging indication information (e.g., paging group, UE group, TRS/CSI-RS availability) for a current paging cycle for another UE. Optionally, the time interval between two adjacent paging DCIs is configured to be larger than or equal to a multiple of the duration of a reference duration. The reference duration may include a duration of a paging frame, or a periodicity of a Synchronization Signal Block (SSB). For example, the time interval between two adjacent paging DCIs may be 3 to 6 times of the duration of a paging frame. For another example, the time interval between two adjacent paging DCIs may be 3 periodicities of SSB.
The paging indication may be transmitted from a base station to a UE via a DCI. The CRC of the DCI may be scrambled by a power saving RNTI.
In this embodiment, the value of the short message indicator field may be used by the UE to interpret other fields for paging indication.
For example, when the short message indicator field is “00” or “01” in binary, or the first bit of the short message indicator field is “0” in binary, the short messages field of the DCI may be used for paging indication and/or TRS/CSI-RS availability indication. When the short message indicator field is “10” or “11” in binary, or the first bit of the short message indicator field is “1” in binary, the fourth to eighth bit of the short messages field may be used for paging indication and/or TRS/CSI-RS availability indication.
For another example, when the short message indicator field is “10” in binary, the bits in the following fields may be used for paging indication and/or TRS/CSI-RS availability indication:
In one implementation, the bits in the reserved bits field may be divided into two sets. One set may be used for paging indication, and the other set may be used for TRS/CSI-RS availability indication. The indication may be based on bitmap formed by the bits in each set, or the indication may be based on the codepoint of each set.
In one implementation, when the short message indicator field is “00” or “01” in binary, the short messages field may be used for paging group/UE group indication, and the reserved bits field may be used for TRS/CSI-RS availability indication. Alternatively, the short messages field may be used for TRS/CSI-RS availability indication, and the reserved bits field may be used for paging group/UE group indication.
In one implementation, when the short message indicator field is “10” in binary, the “Frequency domain resource assignment” field may be used for paging group/UE group indication, and the reserved bits field may be used for TRS/CSI-RS availability indication. Alternatively, the “Frequency domain resource assignment” field may be used for TRS/CSI-RS availability indication, and the reserved bits field may be used for paging group/UE group indication.
In one implementation, when the short message indicator field is “10” in binary, the “Time domain resource assignment” field may be used for paging group/UE group indication, and the reserved bits field may be used for TRS/CSI-RS availability indication. Alternatively, the “Time domain resource assignment” field may be used for TRS/CSI-RS availability indication, and the reserved bits field may be used for paging group/UE group indication.
In some embodiments, rather than re-using an existing DCI to transmit paging indication information, a new DCI may be created for paging indication and/or TRS/CSI-RS availability indication. The CRC of this new DCI may be scrambled by a P-RNTI, or an RNTI configured by higher layer (e.g., RRC).
In one implementation, when the CRC of the DCI is scrambled by P-RNTI or an RNTI configured by higher layer (e.g., RRC), this DCI may include the following bit field:
When the CRC of DCI is scrambled by P-RNTI or an RNTI configured by higher layer (e.g., RRC), this DCI may include the following bit fields with N+M bits in total as the list below. Alternatively, the DCI size (i.e., N+M bits) may be fixed or configured by higher layer. Alternatively, the DCI size (i.e., N+M bits) is 12 (e.g., N=8 for 8 paging groups, M=4 for reserved bits).
In one implementation, when the CRC of a PDCCH-PEI is scrambled by P-RNTI or an RNTI configured by higher layer (e.g., RRC), this PDCCH-PEI may include the following bit fields:
In one implementation, if the DCI size of the DCI is less than that of the DCI format 1_0 whose CRC is scrambled by SI-RNTI (e.g., 41 bits for a CORESET with 24 RB), then zeros are appended (padded) until it has the identical size with that of the DCI format 1_0 whose CRC is scrambled by SI-RNTI. Alternatively, if the DCI size of the DCI is less than that of the DCI format 1_0 whose CRC is scrambled by P-RNTI, then zeros are appended until it has the identical size with that of the DCI format 1_0 whose CRC is scrambled by P-RNTI.
In one implementation, when the CRC of the DCI is scrambled by P-RNTI or an RNTI configured by higher layer (e.g., RRC), this DCI may include the following bit fields:
Table 22, 23, and 24 below show some example paging and/or other information interpretations.
In one implementation, when the CRC of the DCI is scrambled by P-RNTI or an RNTI configured by higher layer (e.g., RRC), this DCI may include the following bit fields:
In one implementation, when the CRC of the DCI is scrambled by P-RNTI or an RNTI configured by higher layer (e.g., RRC), this DCI may include the following bit fields:
In one implementation, when the CRC of the DCI is scrambled by P-RNTI or an RNTI configured by higher layer (e.g., RRC), this DCI may include the following bit fields
In one implementation, when the CRC of the DCI is scrambled by P-RNTI or an RNTI configured by higher layer (e.g., RRC), this DCI may have N bits in total and it may include the following bit fields, where N is configured by higher layer (e.g., N=12).
In one implementation, when the CRC of the DCI is scrambled by P-RNTI or an RNTI configured by higher layer (e.g., RRC), this DCI may have the following bit field:
Table 25 and 26 below show some example paging and/or other information interpretations.
In one implementation, when the CRC of the DCI is scrambled by P-RNTI or an RNTI configured by higher layer (e.g., Medium Access Control, MAC), if the DCI has identical DCI size to that of DCI format 1_0, then the bit(s) in the DCI corresponding to the MCS bit of another DCI (e.g., the 25th-29th bit, i.e., the bits corresponding to the MCS bits of DCI format 1_0 that is scrambled by P-RNTI, in a CORESET with 24 RB) is/are set a predefined value (e.g., all one in binary, “11111”). The bit correspondence may be established by a bit index in each DCI (i.e., the first bit in the DCI corresponds to the first bit in another DCI).
In one implementation, when the CRC of the DCI is scrambled by P-RNTI or an RNTI configured by higher layer (e.g., RRC), this DCI maybe transmitted in search space zero (SS0). Alternatively, when the CRC of the DCI is scrambled by a P-RNTI or an RNTI configured by higher layer, this DCI maybe transmitted in PagingSearchSpace that carries paging DCI (or paging-PDCCH). Alternatively, when the CRC of the DCI is scrambled by P-RNTI or an RNTI configured by higher layer, this DCI maybe transmitted in a common search space that is configured by higher layer. Alternatively, when the CRC of the DCI is scrambled by a P-RNTI or an RNTI configured by higher layer, this DCI maybe transmitted in PEISearchSpace which may be configured as SS0 or PagingSearchSpace. Alternatively, when the CRC of the DCI is scrambled by a P-RNTI or an RNTI configured by higher layer, this DCI maybe transmitted in a common search space or PEISearchSpace.
With embodiments of this disclosure, the paging group, and/or TRS/CSI-RS availability, and/or Short Messages will be addressed. With the implementation of the paging indication as disclosed in this disclosure, a UE under idle of inactive state may save power consumption.
The description and accompanying drawings above provide specific example embodiments and implementations. The described subject matter may, however, be embodied in a variety of different forms and, therefore, covered or claimed subject matter is intended to be construed as not being limited to any example embodiments set forth herein. A reasonably broad scope for claimed or covered subject matter is intended. Among other things, for example, subject matter may be embodied as methods, devices, components, systems, or non-transitory computer-readable media for storing computer codes. Accordingly, embodiments may, for example, take the form of hardware, software, firmware, storage media or any combination thereof. For example, the method embodiments described above may be implemented by components, devices, or systems including memory and processors by executing computer codes stored in the memory.
Throughout the specification and claims, terms may have nuanced meanings suggested or implied in context beyond an explicitly stated meaning. Likewise, the phrase “in one embodiment/implementation” as used herein does not necessarily refer to the same embodiment and the phrase “in another embodiment/implementation” as used herein does not necessarily refer to a different embodiment. It is intended, for example, that claimed subject matter includes combinations of example embodiments in whole or in part.
In general, terminology may be understood at least in part from usage in context. For example, terms, such as “and”, “or”, or “and/or,” as used herein may include a variety of meanings that may depend at least in part on the context in which such terms are used. Typically, “or” if used to associate a list, such as A, B or C, is intended to mean A, B, and C, here used in the inclusive sense, as well as A, B or C, here used in the exclusive sense. In addition, the term “one or more” as used herein, depending at least in part upon context, may be used to describe any feature, structure, or characteristic in a singular sense or may be used to describe combinations of features, structures or characteristics in a plural sense. Similarly, terms, such as “a,” “an,” or “the,” may be understood to convey a singular usage or to convey a plural usage, depending at least in part upon context. In addition, the term “based on” may be understood as not necessarily intended to convey an exclusive set of factors and may, instead, allow for the existence of additional factors not necessarily expressly described, again, depending at least in part on context.
Reference throughout this specification to features, advantages, or similar language does not imply that all of the features and advantages that may be realized with the present solution should be or are included in any single implementation thereof. Rather, language referring to the features and advantages is understood to mean that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present solution. Thus, discussions of the features and advantages, and similar language, throughout the specification may, but do not necessarily, refer to the same embodiment.
Furthermore, the described features, advantages and characteristics of the present solution may be combined in any suitable manner in one or more embodiments. One of ordinary skill in the relevant art will recognize, in light of the description herein, that the present solution may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the present solution.
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/CN2021/121553 | Sep 2021 | US |
| Child | 18521078 | US |
