Patent Description:
Wireless communication networks can include network communication devices, network communication nodes, and at least one core network associated with the wireless network. In some instances, a downlink message from the wireless communication node can be sent to the wireless communication device prior to establishing a connection.

3GPP R2-<NUM>, 3GPP R2-<NUM>, 3GPP R1-<NUM>, and 3GPP C1-<NUM> form part of the related prior art.

The example embodiments disclosed herein are directed to solving the issues relating to one or more of the problems presented in the prior art, as well as providing additional features that will become readily apparent by reference to the following detailed description when taken in conjunction with the accompany drawings. In accordance with various embodiments, example systems, methods, devices and computer program products are disclosed herein. It is understood, however, that these embodiments are presented by way of example and are not limiting, and it will be apparent to those of ordinary skill in the art who read the present disclosure that various modifications to the disclosed embodiments can be made while remaining within the scope of this disclosure.

The following examples/aspects/embodiments depicted in <FIG>, <FIG>, <FIG> and <FIG> and their corresponding description are not according to the claimed invention and are present for illustration purposes only.

Various example embodiments of the present solutions are described below with reference to the accompanying figures to enable a person of ordinary skill in the art to make and use the present solution.

" Such an example network <NUM> includes a base station <NUM> (hereinafter "BS <NUM>") and a user equipment device <NUM> (hereinafter "UE <NUM>") that can communicate with each other via a communication link <NUM> (e.g., a wireless communication channel), and a cluster of cells <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and <NUM> overlaying a geographical area <NUM>.

<FIG> illustrates a block diagram of an example wireless communication system <NUM> for transmitting and receiving wireless communication signals, e.g., orthogonal frequency-division multiplexing (OFDM)/orthogonal frequency-division multiple access (OFDMA) signals, in accordance with some embodiments of the present solution. The system <NUM> may include components and elements configured to support known or conventional operating features that need not be described in detail herein. In one illustrative embodiment, system <NUM> can be used to communicate (e.g., transmit and receive) data symbols in a wireless communication environment such as the wireless communication environment <NUM> of <FIG>, as described above.

The operations of the two transceiver modules <NUM> and <NUM> can be coordinated in time such that the uplink receiver circuitry is coupled to the uplink antenna <NUM> for reception of transmissions over the wireless transmission link <NUM> at the same time that the downlink transmitter is coupled to the downlink antenna <NUM>.

Having discussed aspects of a networking environment as well as devices that can be used to implement the systems, methods and apparatuses described herein, additional details shall follow.

UEs can consume considerable amount of power when communicating with base stations. In particular, the UEs can consume power when establishing a wireless connection with the base station from an idle state. In some technologies, such as, for example, NarrowBand-Internet of Things (NB-IoT) and enhanced machine-type communication (eMTC), the base station can transmit a small amount of data during a downlink transmission to the UE without having the UE to establish a connection with the base station. For example, the base station can utilize an machine termination-early data transmission (MT-EDT) function to send data to the UE either prior to the UE establishing a radio resource control (RRC) connection or during a signal transmission phase in the RRC connection establishment process. However, the base station may need information regarding the capabilities of the UE prior to initiating MT-EDT. In particular, the base station should have information regarding the maximum data size that the UE can receive based on a category of the UE.

Another approach to conserving the power consumption of UEs is to allow the UE to send uplink data on pre-configured uplink dedicated resource, without having the UE to carry out the physical random access channel (PRACH) process. In some technologies, such as, for example, NB-IoT and eMTC, a dedicated preconfigured uplink resource (D-PUR) function can be utilized in which the base station can pre-configure an uplink dedicated resource, which the UE can use to directly send the uplink data to the base station without having to carry out the PRACH process. However, when the UE's attempt to send data using the D-PUR fails, the base station may not have knowledge of the failure, and therefore may not be able to reconfigure to optimize the D-PUR. Further, there is no effective strategy for identifying and reconfiguring the pre-configured dedicated resource based on a Control Plane CIoT EPS/5GS Optimization solution. Further, in some examples, the UE can communicate with the base station over uplink resources while in an idle state. The uplink resources can be dedicated preconfigured uplink resources (D-PUR) configured by the BS. In some instances, the UE may fail to communicate over the D-PUR. However, as the UE is in the idle state, the BS may have no knowledge of the failure, and therefore may not be able to reconfigure or optimize the D-PUR configuration to reduce the risk of failure. Furthermore, in some instances, a base station may not know the paging probability and/or group WUS capability associated with the UE. Lacking the paging probability and/or group WUS capability of the UE, the BS may not be able to map to WUS group resources which the UE monitors to receive the paging messages.

In some aspects, technical solutions to the technical problems detailed above can include having the core network of the wireless communication system determine whether the UE has the capability to receive data based on MT-EDT process and whether the data is suitable for MT-EDT transmission based on whether a data packet size exceeds the UE capability. The core network can obtain the data packet size in several ways. For example, for User Plane CIoT/5GS Optimization solution, the Access and Mobility Management Function (AMF) can obtain the data packet size form the User Plane Function (UPF) when the data arrives. For Control Plane CIoT/5GS Optimization solution, the AMF can obtain the data packet size when the data arrives. For User Plane CIoT/5GS Optimization solution, the Mobile Management Entity (MME) can obtain the data packet size from the Serving Gateway (S-GW). For Control Plane CIoT/5GS Optimization solution, the MME can obtain the data packet size when the data arrives. The core network can then communicate this information to the base station, which can determine whether or not to carry out the MT-EDT. With regard to the D-PUR failure to communicate, the UE can communicate the failure to the BS over messages during the RRC connection process or in RACH measurement report sent to the BS after establishing a connection. With regard to paging probability and/or group WUS capability of the UE, a target BS can be served with the paging probability and/or group WUS capability of the UE transmitted by another base station that can acquire the paging probability information and/or group WUS capability from a core network. These and other solutions to the problems discussed herein are discussed below.

<FIG> shows a flow diagram for a first example process <NUM> for determining initiation of MT-EDT in a wireless communication network. In particular, <FIG> shows communications between a UE <NUM>, a BS (base station) <NUM>, and a core network (CN) <NUM>. The UE and the BS can also be referred to as a wireless communication device and a wireless communication node, respectively. In step <NUM>, the UE can send communication configuration information of the UE to the CN. The communication configuration information can include, for example, UE category and/or UE capability information. In particular, the UE can send a Non-Access Stratum (NAS) message to the CN, where the message includes a UE category and/or UE capability for receiving MT-EDT data. The NAS message, for example, can be an initial attach request or a tracking area update request. The message can include UE category information, which can limit the size of the downlink packet that can be transmitted to the UE by the BS in a transmission time interval (TTI). As an example, the UE categories can include a Category NB1, with an associated maximum TTI data carrying capacity of <NUM> bits, a Category NB2, with an associated maximum TTI data carrying capacity of <NUM> bits, a Category M1, with an associated maximum TTI data carrying capacity of <NUM> bits, or a Category M2, with an associated maximum TTI data carrying capacity of <NUM> bits.

In some examples, the UE category or downlink capability information can be carried by a UE Capability Container (such as, for example, the UE network capability or MS network feature support). In some examples, the UE category or MT-EDT capability information can be provided in bitmap, where each bit position can correspond to a capability or category, and a value of '<NUM>' or '<NUM>' corresponding to the bit position can indicate whether the UE has or does not have that particular capability. As mentioned above, the UE category can include at least one of NB-IoT Category <NUM> (Category NB1), NB-IoT Category <NUM> (Category NB2), eMTC Category <NUM> (Category M1), or eMTC Category <NUM> (Category M2). The UE capability information can include whether the UE supports the MT-EDT process.

In step <NUM>, the CN can determine whether the UE has the capability of receiving MT-EDT data. In particular, the CN can determine whether a downlink packet size associated with the potential MT-EDT data is greater than a downlink transmission capability of the UE. The CN can determine the category of the UE from the UE category information received from the UE and compare the maximum TTI data carrying capacity associated with the UE category with the downlink packet size. For example, the CN can compare whether the downlink data packet size is greater than any one of the following maximum TTI data carrying capacities: <NUM> bits (for category NB1), <NUM> bits (for Category NB2), <NUM> bits (for category M1), and <NUM> bits (for category M2). If the CN determines that the downlink data packet size is greater than the maximum TTI data carrying capacity of the category associated with the UE, the CN can determine that the UE is not able to carry out the MT-EDT process. In another example, the CN can determine that the UE cannot carry out the MT-EDT process based on a capability information received from the UE. For example, the capability information received from the UE (at step <NUM>) can include whether the UE is able to carry out the MT-EDT process, and the CN can make the determination based on the received information.

In step <NUM>, the CN, upon determining that the UE is not capable of carrying out the MT-EDT process, can send a paging message to the BS that does not include the downlink data packet size information. Not including the downlink data packet size in the paging message can indicate to the BS that the UE is not capable of carrying out the MT-EDT process or that the data size is too large to be transmitted by MT-EDT procedure.

Alternatively, if the CN determines that the UE is capable of carrying out the MT-EDT process, the CN, in step <NUM> can send a paging message to the BS that includes the downlink data packet size information. As mentioned above, the CN can determine whether the data can be transmitted by the MT-EDT process by comparing the downlink data packet size to the maximum number of downlink data block bits that can be received within a TTI associated with the UE category. If the downlink data packet size is less than or equal to the maximum number of downlink data block bits that can be received within a TTI associated with the category of the UE, then the CN can determine that the data can be transmitted by the MT-EDT process. In some examples, the message received from the UE can indicate that the UE is capable of carrying out the MT-EDT process, and the CN can determine likewise based on that information. Once the CN determines that the UE is capable of carrying out the MT-EDT process, the CN can send a paging message to the BS including the downlink data packet size. Including the downlink data packet size in the paging message to the BS can indicate to the BS that the UE is capable of carrying out the MT-EDT process. In some examples, the communication to the BS can additionally include the UE category and/or the UE capability information for carrying out the MT-EDT process.

At the BS, if the BS receives a paging message that does not include the downlink data packet size, the BS, in step <NUM>, can determine that the UE is not capable of carrying out the MT-EDT process or that the data size is too large to be transmitted by MT-EDT procedure. As a result, the BS will not initiate the MT-EDT process with the UE.

On the other hand, if the BS receives a paging message that includes the downlink data packet size, the BS, can determine that the UE is capable of carrying out the MT-EDT process. At step <NUM>, the BS can determine whether the data packet size is less than or equal to the reception capability of the lowest UE category of all UEs that supports MT-EDT transmission (e.g., with the lowest value of the maximum number of downlink data block bits that can be received within a TTI). If the BS determines that the downlink data packet size is less than or equal to the reception capability of the lowest UE category, then in step <NUM>, the BS determines that the MT-EDT process should continue using the lowest UE capacity. If the BS determines that the downlink data packet size is greater than the reception capability of the lowest UE category, then the BS, in step <NUM>, can select MT-EDT with the higher UE category. The BS can ensure that the selected UE category has a data reception capability that is greater than the downlink data packet size. In step <NUM>, the BS can send a paging message to the UE with MT-EDT information.

As an example, if the BS determines that the downlink data packet size is less than or equal to <NUM> bits, the BS can initiate the MT-EDT process according to Category NB1. The BS, in step <NUM>, for example, can send a U-port paging message to the UE including the MT-EDT information. If the BS determines that the downlink data packet size is greater than <NUM> bits, there can be an implicit indication that the UE is of the category NB2. The BS can then initiate the MT-EDT process according to the NB2 category, and send a Uu paging message to the UE including the MT-EDT information. If the BS determines that the downlink data packet size is less than or equal to <NUM> bits, the BS can initiate the MT-EDT process according the M1 category, and send the U-port paging message to the UE including the MT-EDT information. If the BS determines that the downlink data packet size is greater than <NUM> bits, there can be an implicit indication that the UE is of the M2 category. The BS can then initiate the MT-EDT process using the M2 category, and send the U-port paging message to the UE including the MT-EDT information.

The UE can utilize the MT-EDT information received from the BS to receive data over the downlink resource before establishing an RRC connection with the BS. As a result, data can be transmitted to the UE without the UE having to use valuable energy to establish an RRC connection.

<FIG> shows a flow diagram for a second example process <NUM> for determining possible initiation of MT-EDT in a wireless communication network. The second example process flow <NUM> is similar to the first example process flow <NUM> discussed above in relation to <FIG>. However, unlike the first example process <NUM>, in which the BS determines the UE category (steps <NUM>, <NUM>, and <NUM>) before paging the UE, in the second example process <NUM>, the BS does not determine the UE category. Instead, the BS sends the paging message (step <NUM>) including the MT-EDT information based on the determination (in step <NUM>) that the UE is capable of carrying out the MT-EDT process. For example, the BS can receive a paging message form the CN including downlink packet size information (in step <NUM>). Based on the presence of the downlink packet size information in the received paging message, the BS can make the determination that the UE can carry out the MT-EDT process. Based on this determination, the BS can directly proceed with sending the UE the paging message (in step <NUM>) including the MT-EDT information.

<FIG> shows a flow diagram for a third example process <NUM> for determining initiation of MT-EDT in a wireless communication network. In the third example process <NUM>, the CN, in step <NUM> determines whether the downlink data packet size is greater than the reception capability of the highest UE category of all UEs that supports MT-EDT transmission (e.g., with highest value of the maximum number of downlink data block bits that can be received within a TTI) and whether the UE supports the MT-EDT process. As an example, the CN can determine a broad category of the UE, such as, whether the UE is of the NB-IoT category or of the eMTC category. As discussed above, the NB-IoT includes two separate categories: NB1 and NB2, and similarly, the eMTC category includes two separate categories M1 and M2. The CN can determine whether the downlink data packet size is greater than the reception capability of the highest UE category of each of the NB-IoT and eMTC categories. The highest UE category of the NB-IoT UE is under the NB2 category (<NUM> bits) and the highest UE category of the eMTC UE is under the M2 category (<NUM> bits). Thus the CN determines whether the downlink data packet size is greater than either <NUM> bits or <NUM> bits. If the UE is of the NB-IoT category (NB1 or NB2) and the CN determines that the downlink data packet size is greater than <NUM> bits, then the CN refrains from including the downlink data packet size information in the paging message (step <NUM>) to the BS. If the UE is of the eMTC category, and the CN determines that the downlink data packet size is greater than <NUM> bits, the CN refrains from (e.g., bypasses or skips) including the downlink data packet size information in the paging message (step <NUM>) to the BS. If however, the CN determines that the downlink data packet size is not greater than either <NUM> bits or <NUM> bits, the CN can include in the paging message (step <NUM>) to the BS at least one of the downlink data packet size information, the UE category, and the UE capability information.

The BS, will not initiate the MT-EDT process with the UE if the paging message received from the CN does not include the downlink data packet size information (step <NUM>). If the BS receives the paging message with the downlink data packet size information, the presence of the size information can serve as an indication to the BS that the UE is capable of carrying out the MT-EDT process. For an NB1 category UE, NB2 category UE, M1 category UE, and the M2 category UE, if the BS determines that the downlink packet data size is less than or equal to data carrying capacity of <NUM> bits, <NUM> bits, <NUM> bits, and <NUM> bits, the BS can use the appropriate category for sending the paging message to the UE including the MT-EDT information (steps <NUM>, <NUM>). If the downlink data packet size is greater than the data carrying capacity of the respective UE category, then the BS does not send a paging message to the UE including the MT-EDT information (steps <NUM> and <NUM>).

<FIG> shows a flow diagram of a fourth example process <NUM> for determining initiation of MT-EDT in a wireless communication network. In the fourth example process <NUM>, the UE can transmit UE category or UE capability information to the BS, which can then relay that information to the CN. For example, in step <NUM>, the UE can transmit an Access Stratum (AS) message including the UE category or UE capability information. In some examples, the AS message can include an uplink RRC message. The message can include parameters such as, for example, UE-RadioPagingInfo cell/element/field carried by UECapabilityInformation. The UE category or UE downlink capability information can be carried by an independent cell/element/field or by a bitmap. The UE category can include at least one of the following: NB-IoT category <NUM> (category NB1), NB-IoT category <NUM> (category NB2), eMTC category <NUM> (category M1), and eMTC category <NUM> (category M2). The UE downlink capability information can include at least one of the following: a maximum number of downlink data bits that the UE can carry in one TTI, or whether the UE supports the MT-EDT process. In step <NUM>, the BS can transmit the information received from the UE to the CN in an AS message.

In step <NUM>, as discussed above, the CN determines whether the downlink data packet size is greater than a maximum downlink capability of the UE and whether the UE supports the MT-EDT process. Based on the determination, the CN can send a paging message to the BS that includes at least the downlink data packet size information, which serves as in indication to the BS that the UE is capable of carrying out the MT-EDT process. In some examples, the paging message from the CN to the BS can include the UE category or the UE capability information. For example, the paging message can include the "UE Radio Capability for Paging" cell/element. In some examples, the paging message can include a UERadioPagingInformation message, which can further include the UERadioPagingInformation message.

<FIG> shows a flow diagram of a fifth example process <NUM> for determining initiation of MT-EDT in a wireless communication network. The process <NUM> includes step <NUM> in which the CN receives an NAS message from the UE including the UE capability or UE category information. In step <NUM> the CN determines whether the downlink data packet size is greater than the reception capability of the lowest UE category of all UEs that supports MT-EDT transmission (e.g., with the lowest maximum number of downlink data block bits that can be received within a TTI). In particular, the CN can determine that for a NB-IoT UE, whether the downlink data packet size is greater than the minimum capability of NB1 category (<NUM> bits) and for a eMTC UE, whether the downlink data packet size is greater than the capability of the M2 category (<NUM> bits). If the conditions are satisfied, the CN can determine that the UE is not capable of carrying out the MT-EDT process; otherwise, the CN can determine that the UE is not capable of carrying out the MT-EDT process. The remainder of the process is similar to that discussed above in relation to <FIG>.

As mentioned above, the UE in idle mode can send uplink data to the BS using preconfigured uplink resource without requiring the PRACH process. However, when the UE's transmission on the uplink resource fails, the BS is unaware of the failure, and therefore, is unable to reconfigure or optimize the D-PUR resource configuration. The discussion herein provides base station strategies directed to D-PUR transmission failures and base station strategies for identifying preconfigured dedicated resources in the Control Plane CIoT EPS/5GS Optimization solution. In addition, the discussion herein provides a method for communicating the UE paging probability and/or group WUS capability to provide support for wakeup service group monitoring to save UE power consumption.

<FIG> shows a flow diagram of a first example process <NUM> for D-PUR failure communication. In particular, the first example process <NUM> includes communications between the UE <NUM> and the BS <NUM>. In step <NUM>, the UE receives a message from the BS including the D-PUR dedicated resource configuration information. In some examples, the D-PUR dedicated resource configuration information can include at least one of: UL grant information, Carrier frequency or frequency domain information of the D-PUR resources, Period(e.g. time interval) of the D-PUR resources, Taking effect time information of the D-PUR resources, Timer for waiting on D-PUR transmission response, D-PUR Radio-Network Temporary Identifier (RNTI), D-PUR user-specific PDCCH search space (USS) identified by the D-PUR RNTI, maximum D-PUR USS monitoring duration, Time Alignment Timer for idle mode or Serving cell Reference Signal Received Power (RSRP) change threshold used for timing advance (TA) validating decision. The UE can utilize the D-PUR dedicated resource configuration information to communicate data with the base station over an uplink resource without having to establish an RRC connection with the BS. However, in some instances, the uplink communication can fail. For example, in step <NUM>, the UE's attempt to communicate data over the D-PUR fails. In some such instances, it can be beneficial for the BS to have knowledge of the failure so that the BS can implement reconfiguration or optimization of the D-PUR dedicated resource configuration, to reduce the risk of failure for instance. In step <NUM>, the BS does not receive the D-PUR transmission response and D-PUR transmission also fails. The UE, upon failure to transmit on the uplink with D-PUR, can fall back on RRC messaging to transmit a message indicating D-PUR failure to the BS. For example, in step <NUM>, the UE can transmit a Physical Random Access Channel (PRACH) preamble to the BS, which initiates the random access procedure. In response, in step <NUM>, the BS responds with a Random Access Response (RAR) message indicating the reception of the preamble and providing a time-alignment command adjusting the transmission timing of the UE based on the timing of the received preamble. In step <NUM> the UE can communicate a EDT Message3 to the BS. The EDT Message3 from the UE can include a message indicating that the UE's attempt to communicate over the D-PUR has failed. The BS can receive the EDT Message3 from the UE and can scan the payload of the message to receive the failure message from the UE. Step <NUM> may also include sending a MAC control element (CE) message. In some examples, the EDT Message3 can include message such as RRCEarlyDataRequest or RRCConnectionRequest.

<FIG> shows a flow diagram of a second example process <NUM> for D-PUR failure communication. In particular, <FIG> includes steps <NUM>-<NUM> that are similar to the corresponding steps discussed above in relation to <FIG>. However in the process <NUM> shown in <FIG>, the failure message is not sent in the Message3 from the UE, but is instead sent in the RRC Message5 or MAC CE message after the receipt of a message from the BS indicating the establishment of the connection with the BS. For example, in step <NUM>, the UE sends a Message3 in response to the RAR message received from the BS in step <NUM>. In the following step <NUM>, the UE receives the connection establishment message, Message4, from the BS. Subsequently, the UE sends a Message5, which can be an RRC Message5 or a MAC CE message that includes a payload indicating a failure to communicate over the D-PUR. In some examples, the Message5 may include messages such as RRCConnectionSetupComplete or RRCConnectionReestablishmentComplete.

<FIG> shows a flow diagram of a third example process <NUM> for D-PUR failure communication. In particular, in process <NUM>, a message indicating a failure to communicate over D-PUR is communicated in a RACH measurement report sent by the UE to the BS after the establishment of a connection between the UE and the BS. The process <NUM> includes steps <NUM>-<NUM>, and <NUM>-<NUM> similar to those discussed above in relation to <FIG>. The process <NUM> further includes, in step <NUM>, an RRC Message5 sent by the UE to the BS as part of the connection establishment process with the BS. In step <NUM>, the UE receives a message from the BS requesting a RACH report. For example, the UE can receive a UEInformationRequest message from the BS. In response, in step <NUM>, the UE can transmit a RACH report back to the BS. For example, the UE can transmit a UEInformationResponse message including RACH report to the BS. The report to the BS can include a payload or message that indicates to the BS a failure to communicate over the D-PUR. In some examples, the payload can include an indication of the UE fallback to RRC connection, which in turn can serve as an indication to the BS of the UE's attempt to communicate over D-PUR failed.

<FIG> shows a flow diagram of a first example process <NUM> for identification strategies for D-PUR in Control Plane CIoT EPS/5GS Optimization solution. In particular, in step <NUM>, the BS can transmit the D-PUR dedicated resource configuration information to the UE over the Control Plane CIoT EPS/5GS Optimization solution. In steps <NUM> and <NUM>, the UE and the BS, respectively, store the D-PUR configuration information and a temporary subscriber identity of the UE in storage. For example, the temporary subscriber identity of the UE can include a Serving Temporary Mobile Subscriber Identity (S-TMSI). Steps <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> can be similar to those discussed above in relation to <FIG>. In step <NUM>, the UE can receive from the CN <NUM> a NAS message including an update to the temporary subscriber identity (e.g., S-TMSI) of the UE. In response, the UE configured with the D-PUR resource, in step <NUM>, can notify the BS of the updated temporary subscriber identity. In some examples, the UE can send an AS signaling message to the BS and include the updated temporary subscriber identity in the payload of the AS signaling message. In step <NUM>, the UE can update the storage at the UE with the updated temporary subscriber identity. Similarly, in step <NUM>, the BS can also update the storage at the BS with the updated temporary subscriber identity.

<FIG> shows a flow diagram of a second example process <NUM> for identification strategies for D-PUR in Control Plane CIoT EPS/5GS Optimization solution. In particular, in the second example process <NUM>, the BS, in step <NUM> sends a message to the CN <NUM> notifying the CN of the D-PUR dedicated resource configuration for the UE of the Control Plane CIoT EPS/5GS Optimization solution. In some examples, the BS can send to the CN the same D-PUR dedicated resource configuration information sent to the UE in step <NUM>. In contrast with the process <NUM> shown in <FIG>, in which the update to the temporary subscriber identity of the UE is sent from the UE to the BS (step <NUM>), in the process <NUM> shown in <FIG>, in step <NUM>, the update to the temporary subscriber identity of the UE is sent from CN to BS. Subsequent to updating the subscriber identity of the UE, the CN can send to the BS the updated subscriber identity of the UE (step <NUM>). The BS can then update its storage with the updated subscriber identity of the UE.

<FIG> shows a flow diagram of a third example process <NUM> for identification strategies for D-PUR in Control Plane CIoT EPS/5GS Optimization solution. In particular, in the third example process <NUM>, the CN, instead of the BS (as shown in <FIG> and <FIG>), stores the association between the subscriber identity of the UE and the D-PUR configuration information. For example, in step <NUM>, the CN can store the D-PUR configuration information received from the BS in association with the current temporary subscriber identity (e.g., S-TMSI) of the UE. For example, in step <NUM>, the UE can send a message to the BS requesting the D-PUR configuration information or a release trigger resource acquisition, the BS, in response, can send a request message (in step <NUM>) to the CN for the D-PUR configuration associated with the UE. The request message can include the temporary subscriber identity of the UE. The CN, in response, can retrieve the D-PUR configuration information associated with the UE from storage, and transmit a message to the BS (in step <NUM>) including the requested D-PUR configuration information.

<FIG> shows a flow diagram of a fourth example process <NUM> for D-PUR configuration information reconfiguration or release. In particular, in steps <NUM> and <NUM>, the UE and the BS store the D-PUR configuration information in their respective storage. The UE can then continue to send RRC messages to the BS, such as messages <NUM>, <NUM>, <NUM>, <NUM>, and <NUM> discussed above in relation to <FIG>. The UE, in step <NUM> can send a message to the BS requesting D-PUR reconfiguration or release. The message can be a RRC/MAC CE message, and can include a D-PUR RNT, time domain information of the D-PUR resources and optionally carrier frequency or frequency domain information of the D-PUR resource. In response, in step <NUM>, the BS can determine the stored D-PUR information based on the D-PUR RNT, the time domain information and/or the carrier frequency or frequency domain information of the D-PUR. In step <NUM>, the BS can send to the UE a RRC/MAC CE message including the determined D-PUR carrier configuration information or D-PUR release information. The UE and the BS can then update (in steps <NUM> and <NUM>) the D-PUR information or release D-PUR information accordingly. Wherein the time domain information of the D-PUR resources includes at least one of: a Taking effect time information of the D-PUR resources in the D-PUR configuration, the time occasion of D-PUR resources deduced from the Taking effect time information of the D-PUR resources in the D-PUR configuration, or Period (e.g., time interval) of the D-PUR resources in the D-PUR configuration.

In example wireless communication networks that support WUS (Wake Up Signal) groups, the BS has to know the paging probability and/or group WUS capability of the UE in order to map out the WUS group resources that the UE needs to monitor. In a conventional paging probability transmission process is the UE and the CN negotiate the paging probability and/or group WUS capability of the UE through NAS. In the paging process, the CN can transmit the paging probability and/or group WUS capability of the UE to a BS by using a paging message. The BS then follows the paging probability and/or group WUS capability of the UE to map the WUS group resources that the UE needs to monitor, and then sends a WUS signal on the WUS resource, thereby waking up the UE to monitor the paging.

However, for a UE in the RRC_Inactive state, as prior to the BS indicating that the UE has entered the RRC_Inactive state, the BS may not have received the paging message from the core network. As a result, the BS would not be able to obtain the paging probability and/or group WUS capability of the UE. Therefore, the BS would be unable to map to the WUS group resources to wake up the UE.

In one approach to addressing the above problem, the UE can communicate the paging probability and/or group WUS capability of the UE with the CN in the inactive state. The CN can communicate the paging probability and/or group WUS capability to a first BS, and the first BS, in turn, can communicate the paging probability and/or group WUS capability to the second BS that would like to send a wake up signal to the UE.

<FIG> shows a flow diagram of a process <NUM>, according to the claimed invention, for delivering or transmitting paging probability and/or group WUS capability of the UE in an inactive state from one base station to another. In step <NUM>, the UE and the CN can negotiate, e.g., over NAS messaging, the paging probability and group WUS capability of the UE. In step <NUM>, when a UE specific connection is established between the first base station (BS1 <NUM>) and the UE, the CN sends the paging probability and the group WUS capability of the UE to the first base station. For example, the CN can send the paging probability and the group WUS capability to the BS1 via the downlink dedicated signaling of the S <NUM> port (or interface) or the Ng port, which can be used by the BS1 to determine the WUS resources of the UE in RRC_Inactive state. In step <NUM>, the BS1 can instruct the UE to enter an RRC_Inactive state. Further, the BS1 communicates the paging probability and the group WUS capability of the UE to the second base station (BS2 <NUM>). For example, the BS1, in an RAN-based paging process, can communicate the paging probability and the group WUS capability of the UE to the BS2 through paging messages between the BS1 and BS2.

In step <NUM>, the BS1 can send RAN-triggered paging messages to the UE. The BS1 also can map the WUS group resource that the UE has to monitor based on the paging probability of the UE. The BS1 then sends out the WUS signal on the WUS resource monitored by the UE, thereby waking up the UE to monitor the paging message. In step <NUM>, the BS2 carries out the tasks similar to those carried out by the BS1 in step <NUM>. In this manner, the BS2, which did not initially have the paging probability and/or group WUS capability of the UE can send paging messages to the UE based on the paging probability received from the BS1.

In some embodiments, the paging probability and/or group WUS capability of the UE is carried to the base station through the downlink dedicated signaling of the S1 port of the Ng port when the UE-specific connection is established or updated. The downlink dedicated signaling of the S1 port or the Ng port includes at least one of the following: INITIAL CONTEXT SETUP REQUEST, UE CONTEXT MODIFICATION REQUEST, UE CONTEXT RESUME RESPONSE, HANDOVER COMMAND, HANDOVER REQUEST. In some examples, the paging probability and/or group WUS capability can be expressed in terms of an integer, a percentage, or a probability level.

<FIG> shows a flow diagram of an example process for delivering or transmitting wake up signal (WUS) Assistance information. The process shown in <FIG> is similar in some respects to the process shown in <FIG>, and like steps are shown with like numerals. In step <NUM>, the UE and the CN can negotiate, over NAS messages, WUS Assistance information. In step <NUM>, the BS1 can receive the WUS Assistance information element (IE) from the CN. Presence of the IE can implicitly indicate the UE WUS capability. If the WUS Assistance information IE is present, this indicates that the UE supports UE ID based group WUS. If the paging probability IE is present, this indicates that the UE supports Paging Probability based group WUS. In step <NUM>, the paging message from BS1 to BS2 can include WUS Assistance information. In step <NUM>, based on the WUS assistance information, the BS1 can select corresponding WUS group to implement/perform RAN based paging. Similarly, in step <NUM>, based on the WUS assistance information, the BS2 can select corresponding WUS group to implement/perform RAN based paging.

The table below shows an example WUS Assistance information element:.

The above IE shows an example WUS assistance information for a base station to determine the WUS group when paging the UE that is in an RRC_Inactive state. The presence of the above IE can indicate that the UE supports UE-ID based group WUS.

In one aspect, the present disclosure describes that a UE transmits the UE category (e.g., indicates the maximum downlink data packet size that can be carried in one TTI) or the UE capability (e.g., whether the UE supports the MT-EDT process) to the core network through NAS signaling, and the core network determines whether the downlink data can be transmitted through the MT-EDT based on the UE capability. In another aspect, a UE transmits the UE category(e.g., indicates the maximum downlink data packet size that can be carried in one TTI) or UE capability (whether the UE supports the MT-EDT process) to the core network through NAS signaling; the core network transmits the UE capability and the downlink data packet size indication to the base station, and the base station, based on the UE capability, determine whether downlink data can be transmitted through MT-EDT. In yet another aspect, a UE transmits the UE category(e.g., indicates the maximum downlink data packet size that can be carried in one TTI) or the UE capability (whether the UE supports the MT-EDT process) to the core network through AS signaling; the core network transmits the UE capability and the downlink data packet size indication to the base station, and the base station, based on the UE capability, determines whether downlink data can be transmitted through MT-EDT.

In one aspect, the present disclosure includes an information reporting strategy when the D-PUR transmission fails. In another aspect, the present disclosure describes D-PUR configuration of the Control Plane CIoT EPS/5GS Optimization solution and the S-TMSI update strategy. In yet another aspect, the present disclosure describes a paging probability transmission strategy of the UE in RRC_INACTIVE state.

Claim 1:
A method, comprising:
receiving (<NUM>), by a wireless communication node (<NUM>) from a core network (<NUM>), paging probability and a group wake up signal, WUS, support capability associated with a wireless communication device (<NUM>); characterised by:
transmitting (<NUM>), by the wireless communication node (<NUM>) to another wireless communication node (<NUM>), the paging probability and the group WUS support capability;
determining, by the wireless communication node based on the paging probability and the group WUS support capability, WUS group resources; and
transmitting (<NUM>), by the wireless communication node (<NUM>) to the wireless communication device (<NUM>), a wake-up signal over the WUS resources.