Wireless communication method, apparatus, computer program product
By receiving and managing the communication configuration information of the UE in the core network of the wireless communication system, optimizing the communication efficiency of the uplink and downlinks, the problem of difficulty in effectively managing the communication power in the wireless communication network in the prior art is solved, and more efficient power management and reduction of UE power consumption is achieved.
Patent Information
- Application Number
- CN202510010367.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2019-11-07
- Publication Date
- 2025-04-11
AI Technical Summary
In wireless communication networks, it is difficult for the prior art to effectively manage and optimize the communication power of the uplink and downlink, especially when the UE is in an idle state, it is difficult for the base station to identify and optimize the D-PUR resource configuration, resulting in transmission failure.
By receiving communication configuration information in the core network of the wireless communication system, the downlink transmission capability of the UE is determined and the downlink data packet size is suppressed or transmitted if necessary. At the same time, the communication efficiency of uplink and downlink is optimized using MT-EDT process and D-PUR resource configuration.
It realizes the management of uplink and downlink communication power more efficiently in the wireless communication network, reduces the power consumption of the UE, and improves the reliability and efficiency of D-PUR resource configuration.
Smart Images

Figure CN119815535A_ABST
Abstract
Description
[0001] This application is a divisional application of the Chinese patent application with application number "2019801020817", application date "November 7, 2019", and title "System and method for power-efficient establishment of uplink and downlink communications in wireless communication networks". Technical Field
[0002] The present disclosure relates generally to wireless communications and includes, but is not limited to, systems and methods for uplink and downlink communications with wireless communication devices. Background Art
[0003] The wireless communication network may include network communication devices, network communication nodes, and at least one core network associated with the wireless network. In some cases, a downlink message from a wireless communication node may be sent to the wireless communication device before a connection is established. Summary of the invention
[0004] The exemplary embodiments disclosed herein are intended to solve problems related to one or more problems existing in the prior art, as well as to provide additional features, which will become apparent by reference to the following detailed description in conjunction with the accompanying drawings. According to various embodiments, exemplary systems, methods, devices, and computer program products are disclosed herein. However, it should be understood that these embodiments are presented by way of example rather than limitation, and it is apparent to those of ordinary skill in the art who read this disclosure that various modifications may be made to the disclosed embodiments while remaining within the scope of this disclosure.
[0005] In one embodiment, a method performed by a core network of a wireless communication system includes: receiving, by the core network of the wireless communication system, communication configuration information associated with a wireless communication device. The method also includes: when the downlink data packet size is greater than the downlink transmission capability of the wireless communication device, suppressing, by the core network, transmitting the downlink data packet size associated with the wireless communication device to the wireless communication node. The method also includes: when the downlink data packet size is less than or equal to the downlink transmission capability of the wireless communication device, transmitting, by the core network, the downlink data packet size to the wireless communication node in a paging message.
[0006] In another embodiment, a method performed by a wireless communication node includes: receiving, by the wireless communication node, a first paging message from a core network of a wireless communication system. The method also includes: determining, by the wireless communication node, that the paging message includes at least one of a downlink data packet size, a downlink transmission capability, or a downlink transmission category associated with a wireless communication device. The method also includes: transmitting, by the wireless communication node, mobile station called early data transmission (MT-EDT) information to the wireless communication device based on at least one of the downlink data packet size, the downlink transmission capability, or the downlink transmission category.
[0007] In another embodiment, a method performed by a wireless communication device includes determining, by the wireless communication device, that data delivery via a D-PUR associated with D-PUR configuration information failed, and transmitting, by the wireless communication device to a wireless communication node, an indication of the failure to deliver data via the D-PUR.
[0008] In another embodiment, a method performed by a wireless communication device includes: receiving, by the wireless communication device, dedicated preconfigured uplink resource (D-PUR) configuration information of a control plane core Internet of Things (CIoT) evolved packet system (EPS) / 5GS optimized solution allocated to the wireless communication device from a wireless communication node. The method also includes: storing, by the wireless communication device, the D-PUR configuration information about a temporary user identifier associated with the wireless communication device. The method also includes: receiving, by the wireless communication device, a message indicating an update of the temporary user identifier. The method also includes: transmitting, by the wireless communication device, the updated temporary user identifier to the wireless communication node. The method also includes: updating, by the wireless communication device, the stored temporary user identifier.
[0009] In another embodiment, a method performed by a wireless communication node includes: transmitting, by the wireless communication node, dedicated preconfigured uplink resource (D-PUR) configuration information of a control plane CIoT EPS / 5GS optimization solution allocated to the wireless communication device to the wireless communication device. The method also includes: transmitting, by the wireless communication node, D-PUR configuration indication information to a core network of the wireless communication system. The method also includes: storing, by the wireless communication node, the D-PUR configuration information and a temporary user identifier associated with the wireless communication device. The method also includes: receiving, by the wireless communication node, a message indicating an update of the temporary user identifier. The method also includes: updating, by the wireless communication node, the stored temporary user identifier.
[0010] In another embodiment, a method performed by a wireless communication node includes transmitting, by the wireless communication node, dedicated preconfigured uplink resource (D-PUR) configuration information of a control plane CIoT EPS / 5GS optimization solution allocated to the wireless communication device to the wireless communication device and the core network. The method also includes: receiving, by the wireless communication node, a message from the wireless communication device, the message including at least one of (i) a request for D-PUR configuration information or (ii) release trigger resource acquisition. The method also includes: transmitting, by the wireless communication node to the core network, a request for D-PUR configuration information associated with the wireless communication device. The method also includes: receiving, by the wireless communication node, the requested D-PUR configuration information from the core network.
[0011] In another embodiment, a method performed by a wireless communication node includes: receiving, by the wireless communication node, a paging possibility and a group wake-up signal (WUS) support capability associated with a wireless communication device from a core network. The method also includes: transmitting, by the wireless communication node, the paging possibility and the group WUS support capability to another wireless communication node. The method also includes: determining, by the wireless communication node, a wake-up signal (WUS) group resource based on the paging possibility and the group WUS support capability. The method also includes: transmitting, by the wireless communication node, a wake-up signal to the wireless communication device via the WUS resource.
[0012] The above and other aspects and embodiments thereof are described in more detail in the drawings, the description and the claims. BRIEF DESCRIPTION OF THE DRAWINGS
[0013] Various example embodiments of the present solution are described in detail below with reference to the following figures or drawings. The drawings are provided for illustrative purposes only and only depict example embodiments of the present solution to facilitate the reader's understanding of the present solution. Therefore, the drawings should not be considered to limit the breadth, scope or applicability of the present solution. It should be noted that for clarity and ease of illustration, these drawings are not necessarily drawn to scale.
[0014] Figure 1 An example cellular communication network is shown in which the techniques and other aspects disclosed herein may be implemented according to an embodiment of the present disclosure.
[0015] Figure 2 A block diagram of an example base station and user equipment according to some embodiments of the present disclosure is shown.
[0016] Figure 3 A flow chart of a first exemplary process for determining to initiate MT-EDT in a wireless communication network according to some embodiments of the present disclosure is shown.
[0017] Figure 4A flow chart of a second exemplary process for determining to initiate MT-EDT in a wireless communication network according to some embodiments of the present disclosure is shown.
[0018] Figure 5 A flow chart of a third exemplary process for determining to initiate MT-EDT in a wireless communication network according to some embodiments of the present disclosure is shown.
[0019] Figure 6 A flow chart of a fourth exemplary process for determining to initiate MT-EDT in a wireless communication network according to some embodiments of the present disclosure is shown.
[0020] Figure 7 A flow chart of a fifth exemplary process for determining to initiate MT-EDT in a wireless communication network according to some embodiments of the present disclosure is shown.
[0021] Figure 8 A flow chart of a first exemplary process for D-PUR communication failure according to some embodiments of the present disclosure is shown.
[0022] Fig. 9 A flow chart of a second exemplary process for D-PUR communication failure is shown in accordance with some embodiments of the present disclosure.
[0023] Fig.10 A flow chart of a third exemplary process for D-PUR communication failure is shown in accordance with some embodiments of the present disclosure.
[0024] Fig.11 A flowchart of a first exemplary process for an identification strategy for D-PUR in a control plane CIoT EPS / 5GS optimization solution according to some embodiments of the present disclosure is shown.
[0025] Fig.12 A flowchart of a second exemplary process for an identification strategy for D-PUR in a control plane CIoT EPS / 5GS optimization solution according to some embodiments of the present disclosure is shown.
[0026] Fig.13A A flowchart of a third exemplary process for an identification strategy for D-PUR in a control plane CIoT EPS / 5GS optimization solution according to some embodiments of the present disclosure is shown.
[0027] Fig. 13B A flow chart of a fourth exemplary process for D-PUR configuration information exchange according to some embodiments of the present disclosure is shown.
[0028] Fig.14A flow chart illustrating an exemplary process for transferring or transmitting paging possibilities of a UE in an inactive state from one base station to another base station in accordance with some embodiments of the present disclosure.
[0029] Fig.15 A flow chart of an exemplary process for delivering or transmitting wake-up signal (WUS) assistance information according to some embodiments of the present disclosure is shown. DETAILED DESCRIPTION
[0030] Various example embodiments of the present solution are described below with reference to the accompanying drawings to enable a person of ordinary skill in the art to make and use the present solution. It will be apparent to a person of ordinary skill in the art that, after reading this disclosure, various changes or modifications may be made to the examples described herein without departing from the scope of the present solution. Therefore, the present solution is not limited to the example embodiments and applications described and illustrated herein. In addition, the specific order or hierarchy of steps in the methods disclosed herein are merely example methods. Based on design preferences, the specific order or hierarchy of steps of the disclosed methods or processes may be rearranged while remaining within the scope disclosed in the present solution. Therefore, a person of ordinary skill in the art will understand that the methods and techniques disclosed herein present various steps or actions in a sample order, and unless otherwise expressly stated, the present solution is not limited to the specific order or hierarchy presented.
[0031] Figure 1 An example wireless communication network and / or system 100 is shown in accordance with an embodiment of the present disclosure, in which the techniques disclosed herein may be implemented. In the following discussion, the wireless communication network 100 may be any wireless network, such as a cellular network or a narrowband Internet of Things (NB-IoT) network, and is referred to herein as “network 100”. Such an example network 100 includes a base station 102 (hereinafter “BS 102”) and a user equipment 104 (hereinafter “UE 104”), which may communicate with each other via a communication link 110 (e.g., a wireless communication channel), and includes cell clusters 126, 130, 132, 134, 136, 138, and 140 covering a geographic area 101. In Figure 1 1, BS 102 and UE 104 are contained within the respective geographic boundaries of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station operating over its allocated bandwidth to provide adequate wireless coverage to its intended users.
[0032] For example, BS 102 may operate under an allocated channel transmission bandwidth to provide sufficient coverage to UE 104. BS 102 and UE 104 may communicate via downlink radio frames 118 and uplink radio frames 124, respectively. Each radio frame 118 / 124 may be further divided into subframes 120 / 127, which may include data symbols 122 / 128. In the present disclosure, BS 102 and UE 104 are described herein as non-limiting examples of "communication nodes", which may generally implement the methods disclosed herein. According to various embodiments of the present solution, such communication nodes are capable of wireless and / or wired communication.
[0033] Figure 2 A block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., orthogonal frequency division multiplexing (OFDM) / orthogonal frequency division multiple access (OFDMA) signals) according to some embodiments of the present solution is shown. The system 200 may include components and elements configured to support known or conventional operating features that need not be described in detail herein. In an illustrative embodiment, as described above, the system 200 may be used in applications such as Figure 1 The wireless communication environment 100 may be used to transmit (eg, send and receive) data symbols.
[0034] System 200 generally includes a base station 202 (hereinafter referred to as "BS 202") and a user equipment 204 (hereinafter referred to as "UE 204"). BS 202 includes a BS (base station) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each of which is coupled to and interconnected with each other via a data communication bus 220 as needed. UE 204 includes a UE (user equipment) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each of which is coupled to and interconnected with each other via a data communication bus 240 as needed. BS 202 communicates with UE 204 via a communication channel 250, which can be any wireless channel or other medium suitable for data transmission as described herein.
[0035] As will be appreciated by those skilled in the art, the system 200 may also include Figure 2Any number of modules outside the modules shown. It will be appreciated by those skilled in the art that the various illustrative blocks, modules, circuits, and processing logic described in conjunction with the embodiments disclosed herein can be implemented in hardware, computer-readable software, firmware, or any actual combination thereof. In order to clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are generally described according to their functions. Whether such functions are implemented in hardware, firmware, or software depends on the specific application and the design constraints imposed on the entire system. People familiar with the concepts described herein can implement such functions in an appropriate manner for each specific application, but such implementation decision should not be interpreted as limiting the scope of the present disclosure.
[0036] According to some embodiments, the UE transceiver 230 may be referred to herein as an "uplink" transceiver 230, which includes a radio frequency (RF) transmitter and an RF receiver, each of which includes circuitry coupled to an antenna 232. A duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in a time duplex manner. Similarly, according to some embodiments, the BS transceiver 210 may be referred to herein as a "downlink" transceiver 210, which includes an RF transmitter and an RF receiver, each of which includes circuitry coupled to an antenna 212. The downlink duplex switch may alternatively couple the downlink transmitter or receiver to the downlink antenna 212 in a time duplex manner. The operation of the two transceiver modules 210 and 230 may be coordinated in time such that the uplink receiver circuit is coupled to the uplink antenna 232 to receive transmissions over the wireless transmission link 250 while the downlink transmitter is coupled to the downlink antenna 212. In some embodiments, there is tight time synchronization with minimum guard times between changes in duplex direction.
[0037] The UE transceiver 230 and the base station transceiver 210 are configured to communicate via a wireless data communication link 250 and cooperate with an appropriately configured RF antenna arrangement 212 / 232 that can support a specific wireless communication protocol and modulation scheme. In some illustrative embodiments, the UE transceiver 210 and the base station transceiver 210 are configured to support industry standards such as Long Term Evolution (LTE) and emerging 5G standards. However, it should be understood that the present disclosure is not necessarily limited to specific standards and related protocols in application. On the contrary, the UE transceiver 230 and the base station transceiver 210 can be configured to support alternative or additional wireless data communication protocols, including future standards or variations thereof.
[0038] According to various embodiments, BS 202 may be an evolved Node B (eNB), a serving eNB, a target eNB, a femtocell or a microcell. In some embodiments, UE 204 may be embodied in various types of user equipment, such as a mobile phone, a smart phone, a personal digital assistant (PDA), a tablet computer, a notebook computer, a wearable computing device, etc. Processor modules 214 and 236 may be implemented or implemented using a general-purpose processor, a content-addressable memory, a digital signal processor, an application-specific integrated circuit, a field programmable gate array, any suitable programmable logic device, a discrete gate or transistor logic, a discrete hardware component, or any combination thereof, in order to perform the functions described herein. In this manner, the processor may be implemented as a microprocessor, a controller, a microcontroller, a state machine, etc. The processor may also be implemented as a combination of computing devices, for example, a combination of a digital signal processor and a microprocessor, a combination of multiple microprocessors, one or more microprocessors and a digital signal processor core, or any other such configuration.
[0039] In addition, the steps of the methods or algorithms described in conjunction with the embodiments disclosed herein may be directly embodied in hardware, firmware, software modules executed by the processor modules 214 and 236, respectively, or in any practical combination thereof. The memory modules 216 and 234 may be implemented as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. In this regard, the memory modules 216 and 234 may be coupled to the processor modules 210 and 230, respectively, so that the processor modules 210 and 230 can read information from and write information to the memory modules 216 and 234, respectively. The memory modules 216 and 234 may also be integrated into the respective processor modules 210 and 230. In some embodiments, the memory modules 216 and 234 may each include a cache for storing temporary variables or other intermediate information during the execution of instructions to be executed by the processor modules 210 and 230, respectively. Memory modules 216 and 234 may also each include non-volatile memory for storing instructions to be executed by processor modules 210 and 230, respectively.
[0040] The network communication module 218 generally represents the hardware, software, firmware, processing logic and / or other components of the base station 202, which implement bidirectional communication between the base station transceiver 210 and other network components and communication nodes configured to communicate with the base station 202. For example, the network communication module 218 can be configured to support Internet or WiMAX traffic. In a typical deployment, without limitation, the network communication module 218 provides an 802.3 Ethernet interface so that the base station transceiver 210 can communicate with a conventional Ethernet-based computer network. In this way, the network communication module 218 can include a physical interface for connecting to a computer network (e.g., a mobile switching center (MSC)). The terms "configured for", "configured to" and their conjunctions, as used herein with respect to a specified operation or function, refer to a device, component, circuit, structure, machine, signal, etc. that is physically constructed, programmed, formatted and / or arranged to perform a specified operation or function.
[0041] Having discussed various aspects of a network environment and devices that may be used to implement the systems, methods, and apparatus described herein, additional details should follow.
[0042] A UE consumes a lot of power when communicating with a base station. In particular, power is consumed when the UE establishes a wireless connection with a 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), a base station can transmit a small amount of data to a UE during a downlink transmission without the UE establishing a connection with the base station. For example, before the UE establishes a radio resource control (RRC) connection or during the signal transmission phase in the RRC connection establishment process, the base station can use the machine-called early data transmission (MT-EDT) function to send data to the UE. However, before starting MT-EDT, the base station may need information about the UE's capabilities. In particular, the base station should have information about the maximum data size that the UE can receive based on the UE category.
[0043] Another way to save UE power consumption is to allow the UE to send uplink data on pre-configured uplink dedicated resources without the UE performing a physical random access channel (PRACH) process. In some technologies, such as, for example, NB-IoT and eMTC, a dedicated pre-configured uplink resource (D-PUR) function can be utilized, in which the base station can pre-configure uplink dedicated resources, and the UE can use this function to directly send uplink data to the base station without performing a PRACH process. However, when the UE fails to try to send data using D-PUR, the base station may not know the failure and therefore may not be able to reconfigure to optimize D-PUR. In addition, there is no effective strategy for identifying and reconfiguring pre-configured dedicated resources based on the control plane CIoT EPS / 5GS optimization solution. In addition, in some examples, the UE can communicate with the base station via uplink resources in an idle state. The uplink resource can be a dedicated pre-configured uplink resource (D-PUR) configured by the BS. In some cases, the UE may not be able to communicate via D-PUR. However, since the UE is in an idle state, the BS may not be aware 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 cases, the base station may not be aware of the paging possibility and / or group WUS capability associated with the UE. Due to the lack of the UE's paging possibility and / or group WUS capability, the BS may not be able to map to the WUS group resources monitored by the UE to receive paging messages.
[0044] In some aspects, the technical solution to the above technical problem may include: the core network of the wireless communication system determines whether the UE has the ability to receive data based on the MT-EDT process and whether the data packet size exceeds the UE capability, and determines whether the data is suitable for MT-EDT transmission. The core network can obtain the data packet size in a variety of ways. For example, for the user plane CIoT / 5GS optimization solution, the access and mobility management function (AMF) can obtain the data packet size from the user plane function (UPF) when the data arrives. For the control plane CIoT / 5GS optimization solution, the AMF can obtain the data packet size when the data arrives. For the user plane CIoT / 5GS optimization solution, the mobile management entity (MME) can obtain the data packet size from the serving gateway (S-GW). For the 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, and the base station can determine whether to perform MT-EDT. Regarding the failure of D-PUR to communicate, the UE can communicate the failure to the BS through a message during the RRC connection process or in the RACH measurement report sent to the BS after the connection is established. Regarding the paging possibility and / or group WUS capability of the UE, the target BS may be provided with the paging possibility and / or group WUS capability of the UE transmitted by another base station (which may obtain the paging possibility information and / or group WUS capability from the core network). These and other solutions to the problems discussed herein are discussed below.
[0045] Figure 3 A flow chart of a first exemplary process 300 for determining to initiate MT-EDT in a wireless communication network is shown. In particular, Figure 3Communication between UE 302, BS (base station) 306 and core network (CN) 308 is shown. UE and BS may also be referred to as wireless communication device and wireless communication node, respectively. In step 310, the UE may send communication configuration information of the UE to the CN. The communication configuration information may include, for example, UE category and / or UE capability information. In particular, the UE may send a non-access stratum (NAS) message to the CN, wherein the message includes the UE category and / or UE capability for receiving MT-EDT data. For example, the NAS message may be an initial attach request or a tracking area update request. The message may include UE category information, which may limit the downlink packet size that the BS may transmit to the UE within a transmission time interval (TTI). For example, the UE category may include category NB1 (wherein the associated maximum TTI data carrying capacity is 680 bits), category NB2 (wherein the associated maximum TTI data carrying capacity is 2536 bits), category M1 (wherein the associated maximum TTI data carrying capacity is 1000 bits), or category M2 (wherein the associated maximum TTI data carrying capacity is 4008 bits).
[0046] In some examples, UE category or downlink capability information may be carried by a UE capability container (such as, for example, UE network capabilities or MS network feature support). In some examples, UE category or MT-EDT capability information may be provided in a bitmap, wherein each bit position may correspond to a capability or category, and a value "0" or "1" corresponding to the bit position may indicate whether the UE has or does not have that particular capability. As described above, the UE category may include at least one of NB-IoT Category 1 (Category NB1), NB-IoT Category 2 (Category NB2), eMTC Category 1 (Category M1), or eMTC Category 2 (Category M2). The UE capability information may include whether the UE supports the MT-EDT process.
[0047] In step 312, the CN may determine whether the UE has the capability to receive MT-EDT data. In particular, the CN may determine whether the downlink packet size associated with the potential MT-EDT data is greater than the downlink transmission capability of the UE. The CN may 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 may compare whether the downlink data packet size is greater than any of the following maximum TTI data carrying capacities: 680 bits (for category NB1), 2536 bits (for category NB2), 1000 bits (for category M1), and 4008 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 may determine that the UE is not capable of performing the MT-EDT process. In another example, the CN may determine that the UE is not capable of performing the MT-EDT process based on the capability information received from the UE. For example, the capability information received from the UE (in step 310) may include whether the UE is capable of performing the MT-EDT process, and the CN may make a determination based on the received information.
[0048] In step 314, the CN may send a paging message not including downlink data packet size information to the BS when determining that the UE is not capable of performing the MT-EDT procedure. Not including the downlink data packet size in the paging message may indicate to the BS that the UE is not capable of performing the MT-EDT procedure or that the data packet size is too large to be sent through the MT-EDT procedure.
[0049] Alternatively, if the CN determines that the UE is capable of performing the MT-EDT process, the CN may send a paging message including downlink data packet size information to the BS in step 316. As described above, the CN may determine whether the data can be transmitted through the MT-EDT process by comparing the downlink data packet size with the maximum number of downlink data block bits (which 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 (which can be received within a TTI associated with the UE category), the CN may determine that the data can be transmitted through the MT-EDT process. In some examples, the message received from the UE may indicate that the UE is capable of performing the MT-EDT process, and the CN may determine the same based on the information. Once the CN determines that the UE is capable of performing the MT-EDT process, the CN may send a paging message including the downlink data packet size to the BS. Including the downlink data packet size in the paging message transmitted to the BS may indicate to the BS that the UE is capable of performing the MT-EDT process. In some examples, the communication to the BS may additionally include UE category and / or UE capability information for performing the MT-EDT process.
[0050] At the BS, if the BS receives a paging message that does not include a downlink data packet size, the BS may determine that the UE is not capable of performing the MT-EDT procedure or the data size is too large to be transmitted through the MT-EDT procedure in step 318. Therefore, the BS will not initiate the MT-EDT procedure with the UE.
[0051] On the other hand, if the BS receives a paging message including a downlink data packet size, the BS may determine that the UE is capable of performing the MT-EDT process. In step 320, the BS may determine whether the data packet size is less than or equal to the receiving capability of the lowest UE category of all UEs supporting MT-EDT transmission (e.g., the minimum 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 receiving capability of the lowest UE category, in step 322, the BS determines that the MT-EDT process should continue to use the lowest UE category. If the BS determines that the downlink data packet size is greater than the receiving capability of the lowest UE category, in step 324, the BS may select MT-EDT with a higher UE category. The BS may ensure that the selected UE category has a data receiving capability greater than the downlink data packet size. In step 326, the BS may send a paging message with MT-EDT information to the UE.
[0052] For example, if the BS determines that the downlink data packet size is less than or equal to 680 bits, the BS may initiate the MT-EDT process according to category NB1. For example, in step 326, the BS may send a U-port paging message including MT-EDT information to the UE. If the BS determines that the downlink data packet size is greater than 680 bits, it may implicitly indicate that the UE belongs to category NB2. The BS may then initiate the MT-EDT process according to the NB2 category and send a Uu paging message including MT-EDT information to the UE. If the BS determines that the downlink data packet size is less than or equal to 1000 bits, the BS may initiate the MT-EDT process according to the M1 category and send a U-port paging message including MT-EDT information to the UE. If the BS determines that the downlink data packet size is greater than 1000 bits, it may implicitly indicate that the UE belongs to the M2 category. The BS may then initiate the MT-EDT process using the M2 category and send a U-port paging message including MT-EDT information to the UE.
[0053] The UE may utilize the MT-EDT information received from the BS to receive data through downlink resources before establishing an RRC connection with the BS. Thus, data may be transmitted to the UE without the UE using precious energy to establish an RRC connection.
[0054] Figure 4 A flow chart of a second exemplary process 400 for determining that MT-EDT may be initiated in a wireless communication network is shown. The second exemplary process flow 400 is similar to the above with respect to Figure 3 The first exemplary process flow 300 is discussed. However, unlike the first exemplary process 300, in which the BS determines the UE category before paging the UE (steps 320, 322, and 324), in the second exemplary process 400, the BS does not determine the UE category. Instead, the BS sends a paging message (step 326) including MT-EDT information based on determining that the UE is capable of performing the MT-EDT process (in step 424). For example, the BS may receive a paging message (in step 316) from the CN including downlink data packet size information. Based on the presence of the downlink packet size information in the received paging message, the BS may determine that the UE can perform the MT-EDT process. Based on this determination, the BS may directly proceed to send a paging message (in step 326) including the MT-EDT information to the UE.
[0055] Figure 5A flow chart of a third exemplary process 500 for determining to initiate MT-EDT in a wireless communication network is shown. In the third exemplary process 500, in step 512, the CN determines whether the downlink data packet size is greater than the receiving capability of the highest UE category of all UEs supporting MT-EDT transmission (e.g., the maximum 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. For example, the CN can determine the broad category of the UE, such as whether the UE belongs to the NB-IoT category or the eMTC category. As described above, NB-IoT includes two independent categories: NB1 and NB2, and similarly, the eMTC category includes two independent categories M1 and M2. The CN can determine whether the downlink data packet size is greater than the receiving capability of the highest UE category of each of the NB-IoT and eMTC categories. The highest UE category of NB-IoT UEs is below the NB2 category (2536 bits), and the highest UE category of eMTC UEs is below the M2 category (4008 bits). Therefore, the CN determines whether the downlink data packet size is greater than 2536 bits or 4008 bits. If the UE belongs to the NB-IoT category (NB1 or NB2) and the CN determines that the downlink data packet size is greater than 2536 bits, the CN avoids including the downlink data packet size information in the paging message (step 314) transmitted to the BS. If the UE belongs to the eMTC category and the CN determines that the downlink data packet size is greater than 4008 bits, the CN avoids (e.g., bypasses or skips) including the downlink data packet size information in the paging message (step 314) transmitted to the BS. However, if the CN determines that the downlink data packet size is not greater than 2536 bits or 4008 bits, the CN may include at least one of the downlink data packet size information, the UE category, and the UE capability information in the paging message (step 516) to the BS.
[0056] If the paging message received from the CN does not include downlink data packet size information, the BS will not initiate the MT-EDT process with the UE (step 318). If the BS receives a paging message with downlink data packet size information, the presence of the size information can be used to indicate to the BS that the UE is capable of performing the MT-EDT process. For NB1 category UEs, NB2 category UEs, M1 category UEs, and M2 category UEs, if the BS determines that the downlink data packet size is less than or equal to the data carrying capacity of 680 bits, 2536 bits, 1000 bits, and 4008 bits, the BS can use the appropriate category to send a paging message including MT-EDT information to the UE (steps 520, 524). If the downlink data packet size is greater than the data carrying capacity of the corresponding UE category, the BS does not send a paging message including MT-EDT information to the UE (steps 522 and 526).
[0057] Figure 6 A flow chart of a fourth exemplary process 600 for determining to initiate MT-EDT in a wireless communication network is shown. In the fourth exemplary process 600, the UE may transmit UE category or UE capability information to the BS, which may then relay the information to the CN. For example, in step 632, the UE may transmit an access stratum (AS) message including the UE category or UE capability information. In some examples, the AS message may include an uplink RRC message. The message may include parameters such as, for example, a UE-RadioPagingInfo cell / element / field carried by the UE capability information. The UE category or UE downlink capability information may be carried by a separate cell / element / field or bitmap. The UE category may include at least one of: NB-IoT category 1 (category NB1), NB-IoT category 2 (category NB2), eMTC category 1 (category M1), and eMTC category 2 (category M2). The UE downlink capability information may include at least one of the following: the 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 634, the BS may transmit the information received from the UE to the CN in the AS message.
[0058] In step 512, as described above, the CN determines whether the downlink data packet size is greater than the maximum downlink capability of the UE and whether the UE supports the MT-EDT process. Based on the determination, the CN may send a paging message to the BS, the paging message including at least downlink data packet size information, which is used to indicate to the BS that the UE is capable of performing the MT-EDT process. In some examples, the paging message from the CN to the BS may include UE category or UE capability information. For example, the paging message may include a "UE radio capability for paging" cell / element. In some examples, the paging message may include a UERadioPagingInformation message, which may also include a UERadioPagingInformation message.
[0059] Figure 7A flowchart of a fifth exemplary process 700 for determining to initiate MT-EDT in a wireless communication network is shown. Process 700 includes step 310, in which the CN receives a NAS message including UE capability or UE category information from the UE. In step 712, the CN determines whether the downlink data packet size is greater than the receiving capability of the lowest UE category of all UEs supporting MT-EDT transmission (e.g., the minimum value of the maximum number of downlink data block bits that can be received within a TTI). In particular, the CN can determine whether the downlink data packet size is greater than the minimum capability of the NB1 category (680 bits) for NB-IoT UEs, and whether the downlink data packet size is greater than the capability of the M2 category (1000 bits) for eMTC UEs. If the conditions are met, the CN can determine that the UE is not capable of performing the MT-EDT process; otherwise, the CN can determine that the UE is not capable of performing the MT-EDT process. The remainder of the process is similar to the above regarding Figure 4 The process of discussion.
[0060] Dedicated pre-configured uplink resources
[0061] As described above, a UE in idle mode can send uplink data to the BS using pre-configured uplink resources without the need for a PRACH process. However, when the UE fails to transmit on the uplink resources, the BS is unaware of the failure and is therefore unable to reconfigure or optimize the D-PUR resource configuration. The discussion herein provides a base station strategy for D-PUR transmission failure and a base station strategy for identifying pre-configured dedicated resources in a control plane CIoT EPS / 5GS optimization solution. In addition, the discussion herein provides a method for communicating UE paging possibilities and / or group WUS capabilities to provide support for wake-up service group monitoring to save UE power consumption.
[0062] Figure 8A flow chart of a first exemplary process 800 for D-PUR failed communication is shown. In particular, the first exemplary process 800 includes communication between a UE 302 and a BS 306. In step 802, the UE receives a message including D-PUR dedicated resource configuration information from the BS. In some examples, the D-PUR dedicated resource configuration information may include at least one of the following: UL grant information, carrier frequency or frequency domain information of the D-PUR resource, a period (e.g., time interval) of the D-PUR resource, an effective time information of the D-PUR resource, a timer for waiting for a D-PUR transmission response, a D-PUR radio network temporary identifier (RNTI), a D-PUR user-specific PDCCH search space (USS) identified by the D-PURRNTI, a maximum D-PUR USS monitoring duration, a time alignment timer for an idle mode, or a serving cell reference signal received power (RSRP) change threshold used for a timing advance (TA) verification decision. The UE can communicate data with the base station through uplink resources using the D-PUR dedicated resource configuration information without establishing an RRC connection with the BS. However, in some cases, uplink communication may fail. For example, in step 804, the UE attempts to communicate data via D-PUR and fails. In some such cases, it may be beneficial for the BS to understand the failure so that the BS can implement reconfiguration or optimization of the D-PUR dedicated resource configuration, thereby reducing the risk of failure, for example. In step 806, the BS does not receive a D-PUR transmission response and the D-PUR transmission also fails. When transmission fails with D-PUR on the uplink, the UE can fall back to the RRC message to transmit a message indicating the D-PUR failure to the BS. For example, in step 808, the UE can transmit a physical random access channel (PRACH) preamble to the BS, and the BS initiates a random access procedure. In response, in step 810, the BS responds with a random access response (RAR) message that indicates the reception of the preamble and provides a time alignment command to adjust the transmission timing of the UE based on the timing of the received preamble. In step 812, the UE can communicate EDTMessage3 to the BS. The EDT Message3 from the UE may include a message indicating that the UE's attempt to communicate via D-PUR has failed. The BS may receive the EDT Message3 from the UE and may scan the payload of the message to receive a failure message from the UE. Step 812 may also include sending a MAC Control Element (CE) message. In some examples, the EDT Message3 may include a message such as RRC EarlyData Request or RRC Connection Request.
[0063] Fig. 9A flow chart of a second exemplary process 900 for D-PUR communication failure is shown. In particular, Fig. 9 The steps 802-810 are similar to the above steps. Figure 8 However, in Fig. 9 In the process 900 shown, the failure message is not sent in Message3 from the UE, but is sent in RRC Message5 or MAC CE message after receiving a message from the BS indicating that a connection is established with the BS. For example, in step 910, the UE sends Message3 in response to the RAR message received from the BS in step 810. In the next step 914, the UE receives a connection establishment message Message4 from the BS. Subsequently, the UE sends Message5, which may be an RRC Message5 or MAC CE message including a payload indicating that communication via D-PUR has failed. In some examples, Message5 may include a message such as RRCConnectionSetupComplete or RRCConnectionReestablishmentComplete.
[0064] Fig.10 A flow chart of a third exemplary process 1000 for D-PUR communication failure is shown. In particular, in process 1000, after a connection is established between a UE and a BS, a message indicating a failure to communicate via D-PUR is conveyed in a RACH measurement report sent by the UE to the BS. Process 1000 includes steps 802-810 and 912-914, which are similar to the above-described exemplary process 1000 for D-PUR communication failure. Fig. 9 Those discussed. Process 1000 also includes, in step 1016, RRC Message5 sent by the UE to the BS as part of a connection establishment process with the BS. In step 1018, the UE receives a message requesting a RACH report from the BS. For example, the UE may receive a UEInformationRequest message from the BS. In response, in step 1020, the UE may transmit a RACH report back to the BS. For example, the UE may transmit a UEInformationResponse message including the RACH report to the BS. The report to the BS may include a payload or message indicating to the BS that communication via D-PUR has failed. In some examples, the payload may include an indication that the UE falls back to the RRC connection, which in turn may be used to indicate to the BS that the UE's attempt to communicate via D-PUR has failed.
[0065] Identification strategy for D-PUR in control plane CIoT EPS / 5GS optimization solution
[0066] Fig.11A flowchart of a first exemplary process 1100 for an identification strategy of D-PUR in a control plane CIoT EPS / 5GS optimization solution is shown. In particular, in step 1102, the BS may transmit D-PUR dedicated resource configuration information to the UE via the control plane CIoT EPS / 5GS optimization solution. In steps 1102 and 1104, the UE and the BS store the D-PUR configuration information and temporary user identity of the UE in a memory, respectively. For example, the temporary user identity of the UE may include a service temporary mobile user identity (S-TMSI). Steps 808, 810, 912, 914, and 1016 may be similar to the above regarding Figure 8-10 Those discussed. In step 1122, the UE may receive a NAS message including an update to the temporary user identity (e.g., S-TMSI) of the UE from CN 308. In response, in step 1124, the UE configured with D-PUR resources may notify the BS of the updated temporary user identity. In some examples, the UE may send an AS signaling message to the BS and include the updated temporary user identity in the payload of the AS signaling message. In step 1126, the UE may update the storage at the UE with the updated temporary user identity. Similarly, in step 1128, the BS may also update the storage at the BS with the updated temporary user identity.
[0067] Fig.12 A flow chart of a second exemplary process 1200 for identifying a strategy for D-PUR in a control plane CIoT EPS / 5GS optimization solution is shown. In particular, in the second exemplary process 1200, in step 1230, the BS sends a message to the CN 308 to notify 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 may send the same D-PUR dedicated resource configuration information to the CN that was sent to the UE in step 1102. Fig.11 The process 1100 shown in FIG. Fig.11 In the process 1100 shown in FIG. 1 , an update of the temporary user identity of the UE is sent from the UE to the BS (step 1124). Fig.12 In the illustrated process 1200, an update to the temporary user identity of the UE is sent from the CN to the BS in step 1224. After updating the user identity of the UE, the CN may send the updated user identity of the UE to the BS (step 1224). The BS may then update its storage with the updated user identity of the UE.
[0068] Fig.13AFIG. 1 is a flow chart of a third exemplary process 1300 for identifying a strategy for D-PUR in a control plane CIoT EPS / 5GS optimization solution. In particular, in the third exemplary process 1300, the CN, rather than the BS (e.g., Fig.11 and 12 The CN may store the association between the user identity of the UE and the D-PUR configuration information (as shown). For example, in step 1306, the CN may store the D-PUR configuration information associated with the current temporary user identity (e.g., S-TMSI) of the UE received from the BS. For example, in step 1322, the UE may send a message to the BS requesting D-PUR configuration information or release trigger resource acquisition, and in response, the BS may send a request message for the D-PUR configuration associated with the UE to the CN (in step 1332). The request message may include the temporary user identity of the UE. In response, the CN may retrieve the D-PUR configuration information associated with the UE from the memory and transmit a message including the requested D-PUR configuration information to the BS (in step 1334).
[0069] Fig. 13B 1350 for reconfiguring or releasing D-PUR configuration information. In particular, in steps 1354 and 1356, the UE and the BS store the D-PUR configuration information in their respective memories. The UE may then continue to send RRC messages to the BS, such as those described above with respect to Fig.13A Messages 808, 810, 912, 914, and 1016 discussed. In step 1322, the UE may send a message to the BS requesting D-PUR reconfiguration or release. The message may be an RRC / MAC CE message and may include D-PUR RNT, time domain information of the D-PUR resource, and optional carrier frequency or frequency domain information of the D-PUR resource. In response, in step 1358, the BS may 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 1360, the BS may send an RRC / MAC CE message including the determined D-PUR carrier configuration information or D-PUR release information to the UE. The UE and the BS may then update (in steps 1362 and 1364) the D-PUR information or release the D-PUR information accordingly. The time domain information of the D-PUR resource includes at least one of the following: the effective time information of the D-PUR resource in the D-PUR configuration, the time occasion of the D-PUR resource derived from the effective time information of the D-PUR resource in the D-PUR configuration, or the period (for example, time interval) of the D-PUR resource in the D-PUR configuration.
[0070] Communication / transmission of paging possibility and / or group WUS capabilities of UE in RRC_INACTIVE state
[0071] In an exemplary wireless communication network supporting a WUS (wake-up signal) group, the BS must know the paging possibility and / or group WUS capability of the UE in order to map the WUS group resources that the UE needs to monitor. In the traditional paging possibility transmission process, the UE and the CN negotiate the paging possibility and / or group WUS capability of the UE through NAS. During the paging process, the CN can transmit the paging possibility and / or group WUS capability of the UE to the BS by using a paging message. The BS then maps the WUS group resources that the UE needs to monitor according to the paging possibility and / or group WUS capability of the UE, and then sends a WUS signal on the WUS resource, thereby waking up the UE to monitor paging.
[0072] However, for a UE in the RRC_INACTIVE state, the BS may not have received a paging message from the core network before the BS indicates that the UE has entered the RRC_INACTIVE state. Therefore, the BS will not be able to obtain the paging possibility and / or group WUS capability of the UE. Therefore, the BS will not be able to map to the WUS group resources to wake up the UE.
[0073] In one method of solving the above problem, the UE can communicate the paging possibility and / or group WUS capability of the UE with the CN in an inactive state. The CN can communicate the paging possibility and / or group WUS capability to the first BS, and the first BS in turn can communicate the paging possibility and / or group WUS capability to the second BS that wants to send a wake-up signal to the UE.
[0074] Fig.14 A flow chart of an exemplary process 1400 for transferring or transmitting the paging possibility and / or group WUS capability of a UE in an inactive state from one base station to another base station is shown. In step 1402, the UE and the CN may negotiate the paging possibility and group WUS capability of the UE, for example, through a NAS message. In step 1404, when a UE-specific connection is established between a first base station (BS1 306) and the UE, the CN may send the paging possibility and / or group WUS capability of the UE to the first base station. For example, the CN may send the paging possibility and / or group WUS capability to BS1 via downlink dedicated signaling of an S1 port (or interface) or an Ng port, which may be used by BS1 to determine the WUS resources of the UE in the RRC_inactive state. In step 1408, BS1 may instruct the UE to enter the RRC_inactive state. In addition, BS1 may communicate the paging possibility and group WUS capability of the UE to the second base station (BS2 1410). For example, in the RAN-based paging process, BS1 may convey the paging possibility and group WUS capability of the UE to BS2 through a paging message between BS1 and BS2.
[0075] In step 1412, BS1 may send a RAN-triggered paging message to the UE. BS1 may also map the WUS group resources that the UE must monitor based on the paging possibility of the UE. BS1 may then send a WUS signal on the WUS resources monitored by the UE, thereby waking up the UE to monitor for paging messages. In step 1414, BS2 performs tasks similar to those performed by BS1 in step 1412. In this way, BS2, which initially does not have the paging possibility and / or group WUS capability of the UE, may send a paging message to the UE based on the paging possibility received from BS1.
[0076] In some embodiments, when establishing or updating a UE-specific connection, the paging possibility and / or group WUS capability of the UE is transmitted to the base station via downlink dedicated signaling of the S1 port or the Ng port. 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 possibility and / or group WUS capability can be expressed as an integer, a percentage, or a probability level.
[0077] Fig.15 A flow chart of an exemplary process for delivering or transmitting wake-up signal (WUS) assistance information is shown. Fig.15 The process shown in Fig.14 The process shown in is similar to that shown in , and the same steps are represented by the same numerical symbols. In step 1502, the UE and the CN may negotiate WUS assistance information through a NAS message. In step 1504, BS1 may receive a WUS assistance information element (IE) from the CN. The presence of the IE may implicitly indicate the UE WUS capability. If a WUS assistance information IE is present, this indicates that the UE supports group WUS based on UE ID. If a paging possibility IE is present, this indicates that the UE supports group WUS based on paging possibility. In step 1510, the paging message from BS1 to BS2 may include WUS assistance information. In step 1512, based on the WUS assistance information, BS1 may select a corresponding WUS group to implement / execute RAN-based paging. Similarly, in step 1514, based on the WUS assistance information, BS2 may select a corresponding WUS group to implement / execute RAN-based paging.
[0078] The following table shows exemplary WUS assistance information elements:
[0079]
[0080] The above IE shows exemplary WUS assistance information for a base station to determine a WUS group when paging a UE in RRC_Inactive state. The presence of the above IE may indicate that the UE supports UE-ID-based group WUS.
[0081]
[0082] On the one hand, the present disclosure describes that the UE transmits the UE category (e.g., indicating the maximum downlink data packet size that can be carried in one TTI) or UE capabilities (e.g., whether the UE supports the MT-EDT process) to the core network through NAS signaling, and the core network determines whether downlink data can be transmitted through MT-EDT based on the UE capabilities. On the other hand, the UE transmits the UE category (e.g., indicating the maximum downlink data packet size that can be carried in one TTI) or UE capabilities (whether the UE supports the MT-EDT process) to the core network through NAS signaling; the core network transmits the UE capabilities and the downlink data packet size indication to the base station, and the base station determines whether downlink data can be transmitted through MT-EDT based on the UE capabilities. On the other hand, the UE transmits the UE category (e.g., indicating the maximum downlink data packet size that can be carried in one TTI) or UE capabilities (whether the UE supports the MT-EDT process) to the core network through AS signaling; the core network transmits the UE capabilities and the downlink data packet size indication to the base station, and the base station determines whether downlink data can be transmitted through MT-EDT based on the UE capabilities.
[0083] In one aspect, the present disclosure includes an information reporting strategy when D-PUR transmission fails. In another aspect, the present disclosure describes a D-PUR configuration and S-TMSI update strategy for a control plane CIoT EPS / 5GS optimization solution. In yet another aspect, the present disclosure describes a paging possibility transmission strategy for a UE in an RRC_inactive state.
[0084] Although various embodiments of the present solution have been described above, it should be understood that they are presented only in an exemplary and not limiting manner. Similarly, various figures may depict example architectures or configurations, which are provided so that those of ordinary skill in the art can understand the example features and functions of the present solution. However, such personnel will understand that the present solution is not limited to the example architectures or configurations shown, but may use a variety of alternative architectures and configurations to implement the present solution. In addition, as those of ordinary skill in the art will understand, one or more features of an embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of the present disclosure should not be limited to any of the above-mentioned illustrative embodiments.
[0085] It should also be understood that any reference to an element herein using names such as "first," "second," etc. does not generally limit the number or order of those elements. Rather, these names may be used herein as a convenient means of distinguishing between two or more elements or examples of elements. Thus, a reference to a first and a second element does not mean that only two elements may be used, or that the first element must be located before the second element in some manner.
[0086] In addition, those of ordinary skill in the art will appreciate that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, and symbols such as those referenced in the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
[0087] It will be further understood by those of ordinary skill in the art that any of the various schematic logic blocks, modules, processors, devices, circuits, methods, and functions described in conjunction with the aspects disclosed herein may be implemented by electronic hardware (e.g., digital implementations, analog implementations, or a combination of the two), firmware, various forms of design code or programs containing instructions (for convenience, may be referred to herein as "software" or "software modules"), or any combination of these technologies. In order to clearly illustrate this interchangeability of hardware, firmware, and software, various schematic components, blocks, modules, circuits, and steps have been described above generally according to their functions. Whether such functionality is implemented as hardware, firmware, or software, or a combination of these technologies, depends on the specific application and the design constraints imposed on the overall system. Technicians may implement the described functionality in various ways for each specific application, but such implementation decisions will not result in a departure from the scope of the present disclosure.
[0088] In addition, it will be understood by those of ordinary skill in the art that the various illustrative logic blocks, modules, devices, components, and circuits described herein may be implemented within or performed by an integrated circuit (IC), which may include: a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, or any combination thereof. The logic blocks, modules, and circuits may further include antennas and / or transceivers to communicate with various components within a network or within a device. A general purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors combined with a DSP core, or any other suitable configuration to perform the functions described herein.
[0089] If the function is implemented in software, the function can be stored as one or more instructions or codes on a computer-readable medium. Therefore, the steps of the method or algorithm disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media include both computer storage media and communication media, and communication media include any media that can enable a computer program or code to be transferred from one place to another. The storage medium can be any available medium that a computer can access. By way of example and in a non-limiting manner, such a computer-readable medium may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices, or any other medium that can be used to store desired program codes in the form of instructions or data structures and can be accessed by a computer.
[0090] In this document, the term "module" as used herein refers to software, firmware, hardware, and any combination of these elements for performing the associated functions described herein. In addition, for the purpose of discussion, various modules are described as discrete modules; however, it is obvious to a person of ordinary skill in the art that two or more modules can be combined to form a single module that performs the associated functions according to an embodiment of the present solution.
[0091] In addition, memory or other storage devices and communication components can be adopted in the embodiment of the present solution.It should be understood that, for the sake of clarity, the above description has described the embodiment of the present solution with reference to different functional units and processors.However, it will be apparent that, without departing from the present solution, any appropriate functional distribution between different functional units, processing logic elements or domains can be used.For example, the function that is illustrated as being performed by a separate processing logic element or controller can be performed by the same processing logic element or controller.Therefore, reference to a specific functional unit is only a reference to an appropriate device for providing the described function, rather than indicating a strict logical or physical structure or organization.
[0092] Various modifications to the embodiments described in this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but is to be given the widest scope consistent with the novel features and principles disclosed herein, as set forth in the claims below.
Claims
1. A wireless communication method, comprising: The wireless communication node receives, from a core network, paging possibilities and group wake-up signal (WUS) support capabilities associated with the wireless communication device; The wireless communication node transmits the paging possibility and the group WUS support capability to another wireless communication node; The wireless communication node determines a WUS group resource based on the paging possibility and the group WUS support capability; as well as The wireless communication node transmits a wake-up signal to the wireless communication device on a WUS resource.
2. The method according to claim 1, further comprising: The wireless communication node receives the paging possibility and the group WUS support capability from the core network via dedicated signaling of an S1 interface or an Ng interface when a UE-specific connection is established or updated.
3. The method according to claim 2, wherein: The dedicated signaling includes at least one of the following: an initial context establishment request, a UE context modification request, a UE context recovery response, a handover command, and a handover request.
4. The method according to claim 1, further comprising: The wireless communication node transmits the paging possibility and the group WUS support capability to the another wireless communication node through a paging message.
5. A wireless communication device, comprising at least one processor, wherein the at least one processor is configured to: receiving, via the transceiver, from a core network, paging possibilities and group wake-up signal (WUS) support capabilities associated with the wireless communication device; transmitting the paging possibility and the set WUS support capability to another wireless communication node via the transceiver; determining WUS group resources based on the paging possibility and the group WUS support capability; and A wake-up signal is transmitted via the transceiver to the wireless communication device on WUS resources.
6. The device according to claim 5, wherein: The at least one processor is further configured to: The paging possibility and the set WUS support capability are received from the core network via dedicated signaling of an S1 interface or an Ng interface when a UE-specific connection is established or updated.
7. The device according to claim 6, wherein: The dedicated signaling includes at least one of the following: an initial context establishment request, a UE context modification request, a UE context recovery response, a handover command, and a handover request.
8. The device according to claim 5, wherein: The at least one processor is further configured to: The paging possibility and the group WUS support capability are transmitted to the another wireless communication node through a paging message.
9. A computer program product having computer readable program medium code stored thereon, which, when executed by at least one processor, causes the at least one processor to: receiving, via the transceiver, from a core network, paging possibilities and group wake-up signal (WUS) support capabilities associated with the wireless communication device; transmitting the paging possibility and the set WUS support capability to another wireless communication node via the transceiver; determining WUS group resources based on the paging possibility and the group WUS support capability; and A wake-up signal is transmitted via the transceiver to the wireless communication device on WUS resources.
10. The computer program product according to claim 9, wherein: When the code is executed by at least one processor, the at least one processor further causes the at least one processor to: The paging possibility and the set WUS support capability are received from the core network via dedicated signaling of an S1 interface or an Ng interface when a UE-specific connection is established or updated.
11. The computer program product according to claim 10, wherein: The dedicated signaling includes at least one of the following: an initial context establishment request, a UE context modification request, a UE context recovery response, a handover command, and a handover request.
12. The computer program product of claim 9, wherein: When the code is executed by at least one processor, the at least one processor: The paging possibility and the group WUS support capability are transmitted to the another wireless communication node through a paging message.