Used to send information for pre-configuring dedicated resources in idle mode

Abstract

Methods, systems and apparatus related to digital wireless communications, and more particularly, techniques related to sending preconfigured dedicated resources for data transmission. In one exemplary aspect, a wireless communication method includes sending preconfigured transmission resource information indicating a time domain location to a core network node. The method also includes receiving data from the core network node at the time domain location indicated in the preconfigured transmission resource information. In another exemplary aspect, a wireless communication method includes connecting a communication node to the core network node. The method also includes receiving data including the preconfigured transmission resource information from the core network node at the time domain location.

Description

Technical Field

[0001] The present invention relates generally to wireless communications. Background Art

[0002] Mobile communication technology is making the world move towards an increasingly connected society. The rapid growth and technological progress of mobile communications have led to greater demands for capacity and connectivity. Other aspects such as energy consumption, device cost, spectrum efficiency and latency are also important to meet the needs of various communication scenarios. Various technologies, including new ways to provide higher quality of service, are being discussed. Summary of the invention

[0003] The present invention discloses methods, systems and devices related to digital wireless communication, and more particularly, methods, systems and devices related to the technology involving pre-configuration of dedicated transmission resources.

[0004] In one exemplary aspect, a wireless communication method is disclosed. The method includes sending pre-configured transmission resource information indicating a time domain location to a core network node. The method also includes receiving data from the core network node near the time domain location indicated in the pre-configured transmission resource information.

[0005] In another exemplary aspect, a wireless communication method is disclosed. The method includes establishing a terminal-specific connection with a core network node before or at a time domain location of a preconfigured transmission resource. The method also includes receiving data from the core network node.

[0006] In another exemplary aspect, a wireless communication method is disclosed. The method includes receiving a paging message from a core network node within a predetermined duration before pre-configured transmission resource information. The method also includes forwarding the paging message to a terminal, wherein the paging message includes a time delay. The method also includes monitoring data sent from the terminal via the pre-configured transmission resources to establish a terminal-specific connection from the communication node to the core network node.

[0007] In another exemplary aspect, a wireless communication method is disclosed. The method includes sending a common search space (CSS) corresponding to a pre-configured transmission resource to a terminal, wherein the sent system information block (SIB) includes the pre-configured transmission resource common search space configuration information. The method also includes sending a message including a pre-configured transmission resource CSS index to the terminal.

[0008] In another exemplary aspect, a wireless communication method is disclosed. The method includes sending a preconfigured transmission resource allocation to a terminal, the preconfigured transmission resource allocation transmission including terminal-specific preconfigured transmission resource search space configuration information. The method also includes receiving data transmission from the terminal at a time domain location for the preconfigured transmission resource search space configuration information, through a preconfigured transmission resource location. The method also includes scheduling a terminal-specific search space and a terminal-specific identifier within a timer or a predetermined duration, wherein the terminal is configured to monitor the terminal-specific preconfigured transmission search space within the timer or the predetermined duration.

[0009] In another exemplary aspect, a wireless communication device is disclosed that includes a processor configured to perform the methods described herein.

[0010] In yet another exemplary aspect, the various techniques described herein may be implemented as processor-executable code and stored on a computer-readable program medium.

[0011] The details of one or more implementations are set forth in the appended drawings, and in the description that follows. Other features will be apparent from the description and drawings, and from the claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Figure 1 An exemplary schematic diagram showing a system architecture for dual connectivity (DC).

[0013] Figure 2A -E illustrates an exemplary signaling procedure for downlink data transmission based on pre-configured dedicated resources.

[0014] Figure 3A -D illustrates an example of data transmission based on pre-configured dedicated resources.

[0015] Figure 4A -C illustrates an example of coupling between processing paging information and pre-configured dedicated resources.

[0016] Figure 5 A pre-configured dedicated resource common search space configuration is illustrated.

[0017] Fig. 6A -H illustrates various terminal-specific pre-configured dedicated resource configuration methods.

[0018] Figure 7 An example PUR pattern is illustrated.

[0019] Figure 8 An example of a wireless communication system to which the technology according to one or more embodiments of the present technology can be applied is shown.

[0020] Fig. 9 A block diagram representation of a portion of a hardware platform.

[0021] Fig.10 A block diagram representation of a portion of a hardware platform. Specific implementation plan

[0022] The development of a new generation of wireless communications - 5G New Radio (NR) communications - is part of the continuous mobile broadband evolution process to meet the requirements of increasing network demands. NR will provide greater throughput to allow more users to be connected simultaneously. Other aspects such as energy consumption, device cost, spectrum efficiency and latency are also important to meet the needs of various communication scenarios.

[0023] As NR emerges in the wireless space, UEs will be able to support both protocols simultaneously. Figure 1 An exemplary schematic diagram of a system architecture for dual connectivity (DC) is shown. The current base station in the core network 103 (referred to as the first network element 81) can select a suitable base station for the UE 80 to act as the second network element 82. For example, a suitable base station can be selected by comparing the channel quality of the base station with a predetermined threshold. The two base stations can provide radio resources to the UE 80 for data transmission on the user plane. On the wired interface side, the first network element 81 and the core network 103 establish a control plane interface 104 for the UE 80. The second network element 82 and the core network 103 can establish a user plane interface 105 for the UE 80. An interface 106 (e.g., an Xn interface) interconnects the two network elements. On the wireless interface side, the first network element and the second network element (81 and 82) can use the same or different radio access technologies (RATs) to provide radio resources. Each of the network elements can independently schedule transmission with the UE 80. A network element having a control plane connection to the core network is referred to as a primary node (e.g., first network element 81), and a network element having only a user plane connection to the core network is referred to as a secondary node (e.g., second network element 82). In some cases, UE 80 may be connected to more than two nodes, one of which acts as a primary node and the remaining one of which acts as a secondary node.

[0024] In some embodiments, the UE may support LTE-NR dual connectivity (DC). For example, one of the typical LTE-NR dual connectivity architectures may be set up as follows: the primary node is an LTE RAN node (e.g., eNB), and the secondary node is an NR RAN node (e.g., gNB). The eNB and gNB are simultaneously connected to an evolved packet core (EPC) network (e.g., LTE core network). Figure 1The architecture shown in can also be modified to include various primary / secondary node configurations. For example, the NR RAN node can be the primary node and the LTE RAN node can be the secondary node. In such a case, the core network for the primary NR RAN node is the Next Generation Converged Network (NG-CN).

[0025] The UE capabilities for the LTE protocol and the NR protocol in LTE-NR DC include two parts: the UE's universal capabilities applicable to both the LTE protocol and the NR protocol for single connection scenarios, and the UE's band combination capabilities related to dual connection scenarios. When the UE has multiple simultaneous connections with a network node, the bands used for different network nodes must cooperate with each other, regardless of the RAT type (or types) used. Here, the term "cooperation" means that the UE can operate in the band without any conflict or substantial interference-that is, the bands can coexist. For example, the Third Generation Partnership Project (3GPP) standard specifies a set of band combinations that can cooperate with each other. If Band 1 and Band 2 are not designated as valid band combinations, the UE cannot use Band 1 when communicating with Node 1, and cannot use Band 2 when communicating with Node 2.

[0026] The present invention describes techniques that may be implemented to transmit downlink information based on pre-configured dedicated resources for data transmission.

[0027] In a machine-to-machine (M2M) communication system, the energy power of the terminal (or "user equipment (UE)") may be consumed during the establishment of the radio resource control (RRC) connection process, and during the transmission and reception of data in the RRC connection state. For narrowband Internet of Things (NB-IoT) small main bearings for data transmission, the terminal may be in the RRC connection state for a short period of time, and the main power consumption of the terminal may be during the connection establishment process (e.g., the physical random access channel (PRACH) process). Specifically, in early data transmission (EDT), small data packets may be sent through the PRACH process, and the terminal sending the small data packets may not have to enter the RRC connection state. Therefore, in some events, the power consumption of the terminal sending small data packets may be mainly consumed during the PRACH process.

[0028] In many cases, the PRACH process in the RRC connection establishment process can be based on PRACH resources, where the process can be divided into four steps. The first step can include a first message from a terminal ("UE") to a base station or a communication node (or "eNodeB"), which can be represented by Msg1:UE-eNodeB. The second step can include a random access response (RAR) message from the base station to the terminal, which can be represented by Msg2:eNodeB->UE. The third step can include a first RRC message from the terminal to the base station, which can be represented by Msg3:UE->eNodeB. The fourth step can include a second RRC message from the base station to the terminal, which can be represented by Msg4:eNodeB->UE.

[0029] The third step (Msg3) may include a UE identifier that identifies the terminal, and the fourth step (Msg4) may complete contention resolution based on the UE identifier, and the PRACH process may end. In a non-EDT scheme, after contention resolution is completed, the terminal may enter an RRC connected state and start terminal-specific data transmission. In an EDT scheme, the third step (msg3) may carry / include uplink data, and the fourth step (Msg4) may include downlink data. The description of contention completion may indicate that uplink and / or downlink data has been successfully sent to the destination. With this completion, the terminal may transition to an RRC idle state.

[0030] If the terminal is configured with dedicated uplink resources, such as pre-configured uplink resources (PUR) in RRC idle mode, data transmission / reception can be performed on the PUR, and contention resolution (UE identification) can be completed based on the pre-configured resources sent in the second step (Msg2). This can shorten the PRACH process and improve the efficiency (including energy efficiency) of small amounts of data transmission.

[0031] When pre-configuring RRC idle mode dedicated resources for the terminal, the following issues can be considered: policy considerations for downlink data transmission based on pre-configured dedicated resources; PUR PDCCH common search space (CSS) configuration method; PUR UE-specific PDCCH search space (PUR-USS) configuration method; coupling processing method for cyclic and pre-configured dedicated resources; and PUR dedicated resource configuration method with multi-service mode coverage.

[0032] Example Embodiment 1:

[0033] Figure 2A-E illustrates an exemplary signaling process for downlink data transmission based on pre-configured dedicated resources. The pre-configured dedicated resources (or "pre-configured uplink resources (PUR)") may include a dedicated resource location. The base station 230 (or "eNB") may notify the core network node (or "MME") 240 of the PUR dedicated resource time (or "time domain location") during the PUR resource configuration. In response, the MME 240 may send a paging message to the eNB 230 at the PUR dedicated resource time, which may include downlink data.

[0034] exist Figure 2A In the example, step 201A illustrates that the eNB 230 may send a dedicated pre-configuration message for idle mode data transmission state to the terminal 220. The message may include pre-configured idle mode data transmission dedicated resources and a terminal-specific PDCCH search space.

[0035] Step 202A: eNB 230 may send an RRC connection release message to UE 220. The RRC connection release message may include pre-configured PUR resources. Upon receiving the RRC connection release message, UE 220 may transition from the last RRC connected state T1A to the RRC idle state T2A.

[0036] Step 203A: The eNB 230 may send a message including the time domain location of the dedicated resources (or "PUR timing") using UE-specific signaling. The UE-specific signaling may be a UE CONTEXT RELEASE REQUEST or another dedicated message.

[0037] Step 204A: MME 240 may send a UECONTEXT RELEASE COMAND to eNB 230 based on receiving UECONTEXT RELEASE REQUEST 203A.

[0038] Step 205A: eNB 230 may send a UE CONTEXT RELEASE COMPLETE message to MME 240 indicating that the UE context message release request is complete.

[0039] Step 206A: The MME 240 may send paging and / or downlink data to the eNB. When the core network 240 has downlink data to be sent, one of the following information may be sent to the eNB 230 at the time domain location of the PUR: paging; paging and data; data and the UE's non-access stratum (NAS) identifier. The NAS identifier of the UE may be a System Architecture Evolution (SAE) Temporary Mobile Subscriber Identity (STMSI) or a similar identifiable UE identifier. Paging and / or downlink data may be sent at a pre-configured resource time domain location, where the UE 220 may not send any data. At the pre-configured resource time domain location, the UE 220 may transition from the RRC idle state T2A to the RRC idle mode USS monitoring state T3A.

[0040] Step 207A: Upon receiving the information sent from the MME 240, the downlink PDCCH search space corresponding to the pre-configured dedicated resources may use a dedicated radio network temporary identifier (RTNI) to perform downlink resource scheduling and / or downlink data transmission for the UE 220. The eNB 230 may use a physical downlink control channel (PDCCH) for downlink (DL) grants to transmit downlink data to the UE 220.

[0041] Step 208A: eNB 230 may send a physical downlink shared channel (PDSCH) message to UE 220. The PDSCH message may include a NAS PDU.

[0042] Step 209A: eNB may send an initial UE message to MME 240. After eNB 230 receives the information sent by core network 240, if UE 220 has corresponding pre-configured dedicated resources in eNB 230, eNB 230 triggers a UE-specific type of connection establishment between eNB 230 and MME 240.

[0043] Step 210A: MME 240 may send an initial context setup request to eNB 230 .

[0044] Step 211A: The eNB 230 may send an initial context setup response to the MME 240. This message may be sent based on receiving the initial context setup request 210A.

[0045] Step 212A: MME 240 may send a downlink NAS transfer message to eNB 230 .

[0046] Step 213A: eNB 230 may send an RRC connection release message to UE 220. RRC connection release message 213 may request UE 220 to switch from RRC idle mode USS monitoring state T3A to RRC idle mode T4A.

[0047] Step 214A: eNB 230 and MME 240 may communicate via a UE-specific S1 release procedure.

[0048] Figure 2B In step 201B, the eNB may send a PUR resource release message to the UE 220 to instruct the UE 220 to release the PUR resources. The UE 220 may switch from the last RRC connected state or the PUR data transmission state T1B to the RRC idle state T2B based on receiving the PUR resource release message 201B.

[0049] Step 202B: After the eNB 230 sends the PUR resource release message 201B to the UE 220, the eNB may send a PUR specific resource release message to the MME 240. The PUR specific resource release message 202B may include a PUR resource release instruction instructing the MME to release the PUR resources. The PUR specific resource release message 202B may be sent using UE specific signaling, such as a UE CONTEXT RELEASE REQUEST message or other dedicated messages sent to the MME 240.

[0050] Step 203B: MME 240 may send a UE context release command to eNB 230 .

[0051] Step 204B: eNB 230 may send a UE context release complete message to MME 240 indicating that the release process is complete.

[0052] Figure 2C The user plane (UP) PUR release indication procedure is illustrated. In step 201C, the eNB 230 may send an idle mode data transmission state dedicated pre-configuration message to the terminal 220. The message may include pre-configured idle mode data transmission dedicated resources and a terminal-specific PDCCH search space.

[0053] Step 202C: the eNB 230 may send an RRC connection release message to the UE 220. The UE 220 may switch from the last RRC connected state T1C to the RRC idle state T2C based on receiving the RRC connection release message 202C.

[0054] Step 203C: eNB 230 may send a message including the time domain location of the dedicated PUR resource to MME 240. After eNB 230 pre-configures the PUR dedicated resource for UE 220, the time domain location of the dedicated resource may be sent to MME 240 by using UE-specific signaling. The UE-specific signaling may be a UE CONTEXT SUSPEND REQUEST message or another dedicated message sent to MME 240.

[0055] Step 204C: In response to receiving the UE context suspend request 203C from the eNB 230 , the MME 240 may send a UE context suspend response to the eNB.

[0056] Step 205C: MME 240 may send paging and / or downlink data to eNB 230. When core network 240 has downlink data to be sent, one of the following information may be sent to eNB 230 in the time domain position of the PUR: paging information; paging information and data; data and NAS identifier of UE 220. The NAS identifier of UE 220 may be an STMSI or similar identifiable UE identifier. Paging and downlink data 205C may be sent at a pre-configured resource location, where UE 220 may not need to send uplink data. UE 220 may transition from RRC idle state T2C to RRC idle mode USS monitoring state T3C at a pre-configured resource location.

[0057] Step 206C: eNB 230 may send a PDCCH for DL ​​grant to UE 220. When eNB 230 receives paging and / or downlink data sent by the core network, the downlink PDCCH search space corresponding to the pre-configured dedicated resources may perform downlink resource scheduling and / or downlink data transmission for UE 220 using a dedicated RNTI.

[0058] Step 207C: The eNB 230 may send a PDSCH message to the UE 220 which may include downlink (DL) data.

[0059] Step 208C: After the eNB 230 receives the information sent by the core network 240, if the UE 220 has corresponding pre-configured dedicated resources in the eNB 230, the eNB 230 may trigger a UE-specific type of connection establishment between the eNB 230 and the MME 240. The eNB 230 may send a UE context restore message or another similar message to the MME 240.

[0060] Step 209C: eNB 230 may send a UE context restoration response to MME 240. This message may be sent based on receiving UE context restoration request 208C.

[0061] Step 210C: MME 240 may send a downlink NAS transfer message to eNB 230 .

[0062] Step 211C: the eNB 230 may send an RRC connection release message to the UE 220. The UE 220 may transition from the RRC idle mode USS monitoring state T3C to the RRC idle state T4C based on the UE 220 receiving the RRC connection release 211C.

[0063] Step 212C: After the eNB 230 sends the pre-configured PUR-specific resource release indication to the MME 240, the eNB 230 may send the pre-configured PUR-specific resource release indication to the MME 240 by using UE-specific signaling. The UE-specific signaling may be a UE CONTEXT SUSPEND REQUEST message or another dedicated message sent to the MME 240.

[0064] Step 213C: MME 240 may send a UE context suspend release message to eNB 230 based on receiving UE context suspend request 212C from eNB 230 .

[0065] Figure 2D The user plane PUR release indication is illustrated. In step 201D, the eNB 230 may send a pre-configured PUR resource release indication to the UE 220. The indication 201D may request the UE 220 to transition from the last RRC connected state or PUR resource transfer state T1D to the RRC idle state T2D.

[0066] Step 202D: After the eNB 230 sends the pre-configured PUR-specific resource release indication 201D to the UE 220, the eNB 230 may send the pre-configured PUR-specific resource release indication to the MME 240 by using UE-specific signaling. The UE-specific signaling may be a UE CONTEXT SUSPEND REQUEST message or another dedicated message sent to the MME 240. The UE context suspend request message may include a PUR resource release instruction.

[0067] Step 203D: MME 240 may send a UE context suspend response to eNB 230 based on receiving the UE context suspend request from eNB 230 .

[0068] Figure 2E The dedicated signaling release for PUR resources is illustrated. In step 201E, the eNB 230 may send a message indicating a request to configure or reconfigure PUR resources to the UE 220. The UE 220 may transition from the last RRC connected state or PUR transfer state T1E to the RRC idle state T2E based on receiving the message 201E.

[0069] Step 202E: The PUR resource reconfiguration or release request may cause the UE 220 to transition from the RRC idle state T2E to the RRC idle mode USS monitoring state T3E.

[0070] Step 203E: The eNB 230 may send a PUR resource reconfiguration or release indication to the UE, wherein the UE 220 may transition from the RRC idle mode USS monitoring state T3E to the RRC idle state T4E.

[0071] Step 204E: When the dedicated PUR resource is updated or released, notify the MME 240 of the PUR resource domain location update or PUR resource release indication. In an embodiment, there is no terminal-specific connection between the eNB 230 and the MME 240, and the UE identifier and the reconfiguration / release indication may be included in the message.

[0072] After the eNB 230 sends the pre-configured PUR dedicated resource time domain reconfiguration or the PUR resource release indication to the UE 220, the eNB 230 may send the time domain location reconfiguration information or the PUR resource release indication of the pre-configured PUR dedicated resource to the MME 240 by using UE-specific signaling. The UE-specific signaling may carry at least one of the following messages: a UE NAS identifier (such as an S-TMSI); and the time domain location information or the PUR resource release indication of the pre-configured PUR dedicated resource.

[0073] Step 205E: After receiving the PUR dedicated resource time domain reconfiguration or PUR resource release indication, the MME 240 may send a PUR resource time domain location update or PUR resource release, and may send a response or reply message to the eNB 230. Once the PUR resource update or release response 205E is sent, the reconfiguration or release process of the PUR resource may end. The RRC idle mode USS monitoring state may include monitoring of the PDCCH search space corresponding to the uplink dedicated resource of the idle mode, and the UE may monitor the PDCCH search space corresponding to the uplink dedicated resource at the resource location.

[0074] Example Embodiment 2:

[0075] Figure 3A-D illustrates an example of data transmission based on pre-configured dedicated resources. Figure 3A In the example, step 301A illustrates that the eNB 330 may send a dedicated pre-configuration message for idle mode data transmission state to the terminal 320. The message may include pre-configured dedicated resources for idle mode data transmission and a terminal-specific PDCCH search space.

[0076] Step 302A: eNB 330 may send an RRC connection release message to UE 320. The RRC connection release message may include pre-configured PUR resources. Upon receiving the RRC connection release message, UE 320 may transition from the last RRC connected state T1A to the RRC idle state T2A.

[0077] Step 303A: eNB 330 may use UE-specific signaling to send a message to MME 340. The UE-specific signaling may be UE CONTEXT RELEASE REQUEST or another dedicated message.

[0078] Step 304A: MME 340 may send a UECONTEXT RELEASE COMMAND to eNB 330 based on receiving UE CONTEXT RELEASE REQUEST 303A.

[0079] Step 305A: eNB 330 may send a UE CONTEXT RELEASECOMPLETE message to MME 340 indicating that the UE context release request is complete.

[0080] Step 306A: The eNB 330 may send an initial UE message to the MME 340 before or at the time domain location of the dedicated resources (or "PUR timing"). After the eNB 330 receives the information sent by the core network 340, if the UE 320 has corresponding pre-configured dedicated resources in the eNB 330, the eNB 330 may trigger a UE-specific type of connection establishment between the eNB 330 and the MME 340. The UE 220 may transition from the RRC idle state T2A to the RRC idle mode USS monitoring state T3A at the pre-configured resource location.

[0081] The eNB 330 may trigger the establishment of a connection with the MME 340 via an interface (e.g., an S1 interface). Establishing such a connection with the MME 340 may not depend on the reception of uplink data resources at the PUR timing (pre-configured time domain location). Once an interface, such as the S1 interface, is established, the MME 340 may send downlink data to the eNB 330. The eNB 330 may send downlink data to the UE 320 using downlink resource scheduling for the downlink PDCCH search space and resource RNTI PUR.

[0082] Step 307A: MME 340 may send an initial context setup request to eNB 330 .

[0083] Step 308A: eNB 330 may send an initial context setup response to MME 340. This message may be sent based on receiving initial context setup request 307A.

[0084] Step 309A: MME 340 may send a downlink NAS transfer message to eNB 330 .

[0085] Step 310A: The eNB 330 may send a PDCCH message regarding a downlink (DL) grant to the terminal.

[0086] Step 311A: eNB 330 may send a PDSCH message including a NAS PDU to UE 320 .

[0087] Step 312A: eNB 330 may send an RRC connection message to UE 320. UE 320 may transition from the RRC idle mode USS monitoring state T3A to the RRC idle state T4A based on receiving the RRC connection message 312A.

[0088] Step 313A: eNB 330 may use UE-specific signaling to send a message to MME 340. The UE-specific signaling may be UE CONTEXT RELEASE REQUEST or another dedicated message.

[0089] Step 314A: MME 340 may send a UECONTEXT RELEASE COMMAND to eNB 330 based on receiving UE CONTEXT RELEASE REQUEST 313A.

[0090] Step 315A: eNB 330 may send a UE CONTEXT RELEASECOMPLETE message to MME 340 indicating that the UE context release request is complete.

[0091] Figure 3B The example illustrates pre-configured data transmission for dedicated resources in idle mode. Figure 3B In the example, step 301B illustrates that the eNB 330 may send a dedicated pre-configuration message for idle mode data transmission state to the terminal 320. The message may include pre-configured dedicated resources for idle mode data transmission and a terminal-specific PDCCH search space.

[0092] Step 302B: eNB 330 may send an RRC connection release message to UE 320. The RRC connection release message may include pre-configured PUR resources. Upon receiving the RRC connection release message, UE 320 may transition from the last RRC connected state T1B to the RRC idle state T2B.

[0093] Step 303B: eNB 330 may use UE-specific signaling to send a message to MME 340. The UE-specific signaling may be UE CONTEXT SUSPEND REQUEST or another dedicated message.

[0094] Step 304B: MME 340 may send a UE CONTEXT SUSPEND RESPONSE to eNB 330 .

[0095] Step 305B: eNB 330 may send UE CONTEXT RESUME REQUST to MME 340 before or at the time domain location of dedicated resources (or "PUR timing"). The location of CP PUR resources may trigger the establishment of an S1 interface connection between eNB 330 and MME 340.

[0096] If UE 320 monitors the PDCCH search space corresponding to the PUR resources, eNB 330 may trigger the establishment of a UE-specific connection between eNB 330 and core network 340 as soon as the PUR resource location is reached. If UE 320 does not send uplink data to eNB 330 via the PUR resources, but UE 320 still monitors the PDCCH search space corresponding to the PUR resources, eNB 330 may establish a UE-specific connection between eNB 330 and core network 340 at the PUR resource location.

[0097] Step 306B: MME 340 may send a UE CONTEXT RESUME RESPONSE to eNB 330 based on receiving UE CONTEXT RESUME REQUEST 305B.

[0098] Step 307B: MME 340 may send a downlink NAS transfer message to eNB 330 .

[0099] Step 308B: the eNB 330 may send a PDCCH message regarding the downlink grant to the terminal 320 .

[0100] Step 309B: eNB 330 may send a PDSCH message including DL data to UE 320 .

[0101] Step 310B: the eNB 330 may send an RRC connection release message to the UE 320. The UE 320 may transition from the RRC idle mode USS monitoring state T3B to the RRC idle state T4B based on receiving the RRC connection release message 310B.

[0102] Step 311B: eNB 330 may use UE-specific signaling to send a message to MME 340. The UE-specific signaling may be UE CONTEXT SUSPEND REQUEST or another dedicated message.

[0103] Step 312B: MME 340 may send UECONTEXT SUSPEND RESPONSE 312B to eNB 330 based on receiving UE CONTEXT SUSPEND REQUEST 311B.

[0104] Figure 3C The illustration illustrates the determination of whether the paging may include user data based on the pre-configured dedicated resource configuration. In step 301C, the eNB 330 sends a Configure / Reconfigure PUR Resources message to the UE 320. The UE 320 may transition from the last RRC Connected state T1C to the RRC Idle state T2C.

[0105] Step 302C: the eNB 330 may send a PUR resource configuration / reconfiguration request to the MME 340. When the eNB configures or reconfigures the PUR resources, the eNB 330 may send the PUR resource configuration or reconfiguration information to the MME 340.

[0106] The sending of the PUR resource configuration or reconfiguration information to the MME may be performed by one of the following: UE-specific S1 interface signaling (e.g., UE CONTEXT RELEASE REQUEST, UE CONTEXT RELEASE COMPLETE, UE CONTEXT MODIFICATION RESPONSE, UE CONTEXT MODIFICATION FAILURE, UE RADIO CAPABILITY MATCH RESPONSE, UE CONTEXT MODIFICATION INDICATION, UE CONTEXT SUSPEND REQUEST, UE CONTEXT RESUME REQUEST, INITIAL UE MESSAGE, NAS NON DELIVERY INDICATION, NAS DELIVERY INDICATION, etc.) sent by the eNB 330 to the MME 340. The PUR resource configuration or reconfiguration information may be time domain location information of the PUR resource, PUR resource existence indication information, or other information related to the PUR resource configuration.

[0107] Step 303C: MME 340 may send paging information to eNB 330. When MME 340 has downlink data to send to UE 220, MME 340 may include the data in the paging message if UE 320 has PUR resource configuration. If UE 320 does not have PUR resource configuration, MME 340 may first send a paging message to eNB 330, and then send the downlink data to eNB 330 after receiving a message in response to the first paging message.

[0108] Step 304C: The eNB 330 may send a PDCCH associated with a common RNTI to the UE 320 through a PDCCH common search space (CSS). When the eNB 330 receives a paging message (with or without user data), if the UE 320 has pre-configured PUR resources, the UE 320 may perform DL Grant scheduling on the CSS-Paging and send the DL Grant to the UE 320. The common RNTI may include at least one of the following: a paging-RNTI; a common RNTI for paging with data; a common RNTI for data transmission. The PDCCH common search space may include at least one of the following: a PDCCH search space for paging; a PDCCH common search space for paging with data; a PDCCH common search space for data transmission. The PDCCH common search space may include at least one of the following: sent through SIB; sent through dedicated RRC signaling; a CSS set sent through SIB and a UE-specific index for the CSS sent through dedicated RRC signaling; a CSS sent through SIB and a UE-specific PDCCH repetition number sent through dedicated RRC signaling.

[0109] Step 305C: eNB 330 may send a PDSCH message to UE 320. The PDSCH channel may carry dedicated resource configuration information and / or downlink user data in a paging message. The dedicated resource configuration information may include at least one of: a UE-specific RNTI (such as C-RNTI); at least one uplink resource grant (UL Grant) for a scheduling request (SR), a buffer size report (BSR), or a response to DL user data; a PDCCH search space (such as USS) corresponding to dedicated resources; and a PDCCH search space monitoring time.

[0110] Step 306C: UE 320 may send a PUSCH message to eNB 330. When UE 320 receives a PDSCH channel, if data is carried on the PDSCH channel, UE 320 may confirm the data by using PUSCH through UL Grant. If there is no data on the PDSCH channel, UE 320 may send a message including at least one of RRCMsg3, SR, BSR, and paging response to eNB 320 through PUSCH through UL Grant. The message may trigger the establishment of an S1 interface UE-specific connection so that MME 340 may send downlink data to eNB 330.

[0111] Step 307C: eNB 330 may send a PDCCH message to UE 330 .

[0112] Step 308C: eNB 330 may send a paging response message to MME 340. When eNB 330 receives a response to the data from UE 320 through PUSCH via UL Grant, eNB 330 may send a paging response to MME 340, and downlink data transmission is completed.

[0113] Figure 3D The illustration shows that paging information and downlink data are sent to the terminal 320. In step 301D, the eNB 330 may send a message to configure or reconfigure PUR resources to the UE 320. The UE 320 may transition from the last RRC connected state T1D to the RRC idle state T2D based on receiving the message 301D.

[0114] Step 302D: MME 340 may send a paging message to eNB 330 (without carrying any downlink user data).

[0115] Step 303D: eNB 330 may directly trigger the establishment or resumption of UE-specific signaling of the S1 interface based on the PUR resource configuration information, so that MME 340 sends user data to eNB 330. The establishment of the S1 interface may be triggered by one of the following messages: UE CONTEXT RESUME REQUEST, INITIAL UE MESSAGE, or another newly added S1 port UE-specific signaling.

[0116] Step 304D: After the UE's S1 interface connection is established or restored, the MME 340 may send downlink data to the eNB 330 .

[0117] Step 305D: After receiving the user's downlink data, the eNB 330 may perform DL Grant scheduling on the UE 320 via a PDCCH associated with a common RNTI on a PDCCH common search space (CSS). The common RNTI may include at least one of the following: a paging-RNTI; a common RNTI for paging with data; a common RNTI for data transmission. The PDCCH common search space may include at least one of the following: a PDCCH search space for paging; a PDCCH common search space for paging with data; and a PDCCH common search space for data transmission. The PDCCH common search space includes at least one of the following: sent via SIB; sent via dedicated RRC signaling; a CSS set sent via SIB and a terminal-specific index for the CSS sent via dedicated RRC signaling; a CSS sent via SIB and a UE-specific PDCCH repetition number sent via dedicated RRC signaling.

[0118] Step 306D: The eNB 330 may send a PDSCH message on the DL Grant through the PDSCH channel. The PDSCH channel may carry dedicated resource configuration information and downlink user data. The dedicated resource configuration information may include at least one of: a UE-specific RNTI (such as C-RNTI); an uplink resource grant (UL Grant) for at least one of a scheduling request (SR), a buffer size report (BSR), and a response to DL user data; a PDCCH search space corresponding to the dedicated resource (such as USS); and a PDCCH search space monitoring time.

[0119] Step 307D: UE 320 may send a PUSCH message to eNB 330 through UL grant. Message 307D may include at least one of the following: RRC Msg3; SR; BSR; paging response; DL data response.

[0120] Step 308D: eNB 330 may send a PDCCH message to UE 320 .

[0121] Step 309D: After uplink and downlink data transmission is completed, eNB 330 may trigger an S1 interface UE-specific connection release or suspension procedure with MME 340. The S1 interface UE-specific may be released based on receiving one of the following messages: UE CONTEXT SUSPEND REQUEST; UE CONTEXT RELEASE REQUEST or another newly added S1 interface UE-specific signaling.

[0122] Example Embodiment 3:

[0123] Figure 4A -C illustrates an example of coupling between processing paging information and pre-configured dedicated resources. Figure 4A An example of paging and PUR coupling is illustrated. The eNB 430 may receive a paging message (paging 403A) from the MME 440 within a predefined time period before a valid preconfigured dedicated resource (e.g., PUR). In other words, the time interval between the paging message and the preconfigured dedicated resource is less than a predetermined length of time. The eNB 430 may determine to delay the paging message (paging 403A) based on the PUR.

[0124] If UE 420 monitors the terminal-specific PUR search space (PUR-USS) even if it does not send uplink data on the PUR, eNB 430 may initiate a UE-specific S1 connection establishment or resumption (e.g., S1 connection establishment or resumption 404A) upon receiving a paging message (Paging 403A) from MME 440 before the PUR resource location.

[0125] The eNB 430 may receive downlink data (e.g., downlink data 405A) from the MME 440 when the UE-specific S1 connection is established. The eNB 430 may transmit a PDCCH using a PDCCH search space corresponding to the associated PUR resources, wherein the downlink PDCCH may include using a dedicated RNTI to perform downlink resource scheduling for downlink data transmission to the UE 420.

[0126] Figure 4B An example of paging and PUR coupling is illustrated. If the UE 420 does not send data (uplink data) at a PUR resource location (e.g., a pre-configured resource location 406B), the pre-configured dedicated resource-specific PDCCH search space (PUR-USS) may not be monitored. If the eNB 430 receives uplink data on the PUR resource (e.g., at the pre-configured resource location 406B), the eNB 430 may trigger the establishment of an S1 interface with the MME 440 (S1 connection establishment or recovery 404B). In this case, the eNB 430 may not send a paging message to the UE 420.

[0127] Figure 4C An example of paging and PUR coupling is illustrated when the terminal 420 does not send data. The eNB 430 may not receive uplink data from the UE 420 on the PUR resources (e.g., pre-configured resource location (uplink data is not sent) 404). In this case, the eNB 430 may not monitor the PDCCH search space corresponding to the PUR. After the PUR resources (or pre-configured resource location) end, the eNB 430 may schedule a paging message (paging 406C) to be sent to the UE 420 through CSS signaling.

[0128] exist Figure 4A-C, if the paging message does not carry paging eDRX parameters, the predefined time period may include a duration not exceeding the MME 440 paging retransmission timer (e.g., 15 seconds). If the paging message carries eDRX parameters, the predefined time period may be a duration not exceeding a minimum value (e.g., MME 440 paging retransmission timer, paging time window (PTW) length). Valid PUR resources may identify that PUR resources may be configured to UE420 and that PUR resources are available (e.g., TA is valid and cell reselection does not occur, etc.). The paging retransmission timer may be defined by the communication node and / or sent from the core network, and the communication node may be configured to define and / or modify the predetermined duration.

[0129] Example Embodiment 4:

[0130] Figure 5 The pre-configured dedicated resource PDCCH common search space configuration is illustrated. In step 501: the eNB 530 configures a PDCCH common search space (CSS) corresponding to a PUR resource for the UE 520. The PUR-CSS configuration information may be sent to the UE 520 via a system information block (SIB). The PDCCH CSS may include at least one of the following: a PDCCH monitoring pattern set with different enhanced coverage level configurations, a PDCCH monitoring pattern without enhanced coverage level distinction.

[0131] Each PDCCH monitoring mode may include: a starting position of PDCCH monitoring or a parameter for determining the starting position of PDCCH monitoring; a time interval for PDCCH monitoring; a parameter for determining the PDCCH monitoring time interval; and a maximum number of repetitions of PDCCH.

[0132] Step 502A: The eNB 530 may configure a PUR dedicated resource and at least one of a PUR-CSS index and a PDCCH repetition number corresponding to the PUR dedicated resource. The eNB 530 may send the configuration to the UE 520 during the last RRC connected state when configuring the PUR dedicated resource for idle mode data transmission. The UE 520 may monitor the monitoring duration of the PUR-CSS from the PUR dedicated resource position. The eNB 530 may send an idle mode data transmission state dedicated resource pre-configuration, the idle mode data transmission state dedicated resource pre-configuration including the reconfigured idle mode data transmission dedicated resource and the PUR-CSS index.

[0133] Step 502B: The eNB 530 may configure PUR-specific resources, and at least one of a PUR-CSS index and a PDCCH repetition number corresponding to the PUR-specific resources, and a monitoring duration of the PUR-CSS by using an RRC connection release message in an RRC connected state or a PUR resource-based data transmission state. The PUR-CSS index corresponding to the PUR-specific resources may include a coverage level index where the UE 520 is located.

[0134] Example Embodiment 5:

[0135] Fig. 6A -H illustrates various terminal-specific pre-configured dedicated resource configuration methods. The eNB 630 can configure PUR resources for the terminal 620, wherein the terminal 620 can be configured to configure at least one of the following: UE-specific PURPDCCH search space; maximum monitoring during (PUR-USS-Duration); and monitoring timer (PUR-USS-Timer); UE-specific RNTI corresponding to the PUR PDCCH search space. The UE-specific RNTI corresponding to the PUR PDCCH is valid only when the terminal 620 monitors the PUR PDCCH search space or during the pur-USS-Duration starting from the PUR-USS monitoring.

[0136] The UE-specific PUR PDCCH search space (PUR USS) may include: a starting position for PDCCH monitoring or a parameter for determining a starting position for PDCCH monitoring; a time interval for PDCCH monitoring; a parameter for determining a PDCCH monitoring time interval; and a maximum number of PDCCH repetitions. The UE 620 may start or restart a PUR-USS-Timer at the start of PUR-USS monitoring or when there is no data transmission and reception. If the PUR-USS-Timer times out, the UE 620 may enter an RRC idle mode.

[0137] exist Fig. 6A In the present embodiment, if the UE does not send data on the PUR resource (e.g., the pre-configured resource location (UE does not send data) 602A), a timer (PUR-USS-Timer) may be started on the PUR resource location, and the UE 620 may enter the PUR-USS monitoring state T3A. If the timer expires and the PDCCH scheduling information is not monitored, the UE 620 enters the idle state T4A.

[0138] exist Figure 6BIn the present embodiment, if the UE 620 does not send any data on the PUR (or pre-configured resource location) and also monitors the terminal-specific pre-configured PDCCH search space (PUR-USS), the pre-configured resource timer (PUR-USS-Timer) may be started at the PUR resource location. If the PDCCH scheduling information is monitored before the timer expires, the UE 620 may perform data transmission and reception based on the scheduling information. When data is transmitted and received, the UE 620 may start or restart the timer (PUR-USS-Timer), and if the timer expires, the UE 620 may enter the idle state T4B.

[0139] exist Figure 6C In the case where the UE 620 does not send data on the PUR, the UE 620 may enter the idle mode if the UE 620 does not send data on the PUR resource. For example, monitoring the idle mode may include scheduling the paging space CSS-Paging.

[0140] exist Fig.6D In the embodiment of the present invention, if the UE 620 performs data transmission on the PUR resource, the timer (PUR-USS-Timer) may be started or restarted after the data transmission and reception are completed. If the timer expires, the UE may enter the idle state T4B. If the eNB 630 wants the UE 620 to stop PUR-USS monitoring before the timer expires, or if it wishes to reconfigure the PUR resources, the eNB 630 may send an instruction (PDCCH for acknowledgment or DL ​​grant 603D) to the UE 620 to notify the PUR-USS to stop monitoring before the timer expires. The instruction may be indicated by a PDCCH DCI, a downlink MAC CE scheduled by the PUR-USS, an RRC dedicated signaling scheduled by the PUR-USS, or an acknowledgment indication of uplink data. After receiving the relevant indication, the UE 620 may perform an indication response, and / or stop monitoring of the PDCCH search space.

[0141] exist Fig. 6EIn the RRC connected state T4E, if the UE 620 performs data transmission on the PUR resource, the timer (PUR-USS-Timer) may be started or restarted after the data transmission and reception are completed. If the eNB 630 wants the UE 620 to transition to the RRC connected state T4E, a state indication command (e.g., RRC reconfiguration or RRC setup / recovery 604E) may be sent to the UE 620 before the PUR-USS-Timer may time out, which indicates that the UE 620 transitions to the RRC connected state. The state indication command 604E may be an RRC connection establishment message, an RRC connection recovery message, an RRC connection reconfiguration message, a newly defined RRC dedicated downlink signaling message, a medium access control (MAC) control element (CE) including an indication command, or a PDCCH DCI including an indication command. The RRC reconfiguration or RRC setup / recovery message 604E may carry the C-RNTI.

[0142] If UE 620 receives the instruction command, UE 620 may transition to the RRC connection state based on instruction command 604E. If C-RNTI is carried in instruction 604E, UE 620 may use C-RNTI in RRC connection mode T4E. If C-RNTI is not carried in instruction 604E, UE 620 may use the RNTI used by UE before receiving instruction 604E (PDCCH scrambled with original RNTI).

[0143] exist Fig. 6F In the PUR-USS monitoring process, even if the eNB 630 sends the PDCCH Order 604F to the UE 620, the PUR-USS is still monitored.

[0144] exist Figure 6G and Figure 6H In the embodiment, during the PUR-USS monitoring procedure, the PUR-USS may be monitored even if the eNB 630 sends a PDCCH order message to the UE 620. During the PUR-USS monitoring procedure, if the eNB 630 sends a PDCCH Order (PDCCH order 604G) to the UE 620, the UE 620 may switch from PUR-USS monitoring to CSS-RA monitoring (if the PUR-USS-Timer is running, it may be stopped). When the UE receives a RAR or TA Update indication (607) (e.g., Timing Advance Command MAC CE), or the UE sends uplink data or a contention completion indication (such as C-RNTI MAC CE) to the UE after receiving the RAR, then the CSS-RA monitoring ends and the UE 620 may start monitoring the PUR-USS.

[0145] Example Embodiment 6:

[0146] Figure 7 When a PUR resource is configured to the UE 720, a PUR pattern corresponding to a service mode may be configured to the UE 720. The PUR pattern may include a PUR transmission start time, a periodic PUR transmission interval, a maximum valid duration of the periodic PUR resource, a valid timer, and superposition information of multiple service modes.

[0147] The PUR transmission start time may be expressed in absolute time (e.g., PUR transmission start time PUR-TransmissionStartTime, such as YY:MM:DD:HH:MM:SS; radio frame RF and radio subframe SF where PUR resource transmission starts). In an embodiment, the PUR transmission start time may be expressed in relative time (such as an offset value relative to the absolute time).

[0148] The superposition of multiple business modes may include a transmission time series expressed in a valid bit sequence (e.g., dayofWeek BIT STRING (SIZE(7)) or dayofMonth BIT STRING (SIZE(31)), hourofDay BIT STRING (SIZE(24))). The superposition of multiple business modes may include a set of configuration sets for multiple business modes, where each business mode set corresponds to a configuration index and is used for reconfiguration, release, scheduling, etc. of the business mode. The superposition of multiple business modes may include the superposition of the transmission time series and multiple sets of business mode configuration sets.

[0149] As an example, PUR-TransmissionStartTime is set to: 2019-01-01 00:00:00 RF=0, SF=0, and dayofWeek is set to: 118000. The periodic PUR-Duration is set to: 30 days. Then, starting from 2019-01-01 00:00:00, the first occurrence of RF0, SF0 is the starting position of the first PUR resource. Thereafter, the first occurrence of RF0, SF0 after 00:00:00 on Monday, Tuesday, and Wednesday has a PUR resource position. PUR resources appear in this pattern and do not appear until 2019-01-30 23:59:59.

[0150] The transmission sequence of a UE can also be divided into multiple groups of PUR resource configuration sets. For example, three resource sequences can be expressed as:

[0151] PUR configuration index 1:

[0152] The start time of PUR resource block 1; / / 2019-01-01 00:00:00;

[0153] Period and / or interval of PUR resource block 1; / / 1 week;

[0154] Scheduling information of PUR resource block 1;

[0155] PUR resource block 1 valid duration; / / 29~30days;

[0156] PUR configuration index 2:

[0157] The start time of PUR resource block 2; / / 2019-01-02 00:00:00;

[0158] Period and / or interval of PUR resource block 2; / / 1 week;

[0159] Scheduling information of PUR resource block 2;

[0160] PUR resource block 2 valid duration; / / 28~29 days

[0161] PUR configuration index 3:

[0162] The start time of PUR resource block 3; / / 2019-01-07 00:00:00;

[0163] Period and / or interval of PUR resource block 3; / / 1 week;

[0164] Scheduling information of PUR resource block 3;

[0165] PUR resource block 3 valid duration; / / 22~24 days

[0166] }

[0167] For example, a sequence of three resources can be expressed as:

[0168]

[0169]

[0170] Figure 8 802 is a flowchart illustrating a method for configuring pre-configured transmission resources. A communication node may send pre-configured transmission resource information indicating a time domain location to a core network node (block 802). The communication node may be an eNB as described in any one of example embodiments 1 to 6. The pre-configured transmission resource information may include a pre-configured uplink resource (PUR) as described in any one of examples 1 to 6. The core network node may include an MME as described in example embodiments 1 to 3.

[0171] The communication node may receive data from the core network node near the time domain location indicated in the preconfigured transmission resource information (block 804). The time domain location (or preconfigured resource location) may be associated with a preconfigured transmission resource (or PUR). The preconfigured transmission resource configuration associated with the PUR may be sent to the terminal (or UE as described in example embodiments 1 to 6).

[0172] In some embodiments, the pre-configured transmission resource information is included in a terminal-specific dedicated message sent by the communication device to the core network node.

[0173] In some embodiments, the data received at the communication device includes at least one of: paging information; paging information including user data; and user data with a non-access stratum (NAS) identifier of the terminal.

[0174] In some embodiments, the data comprises downlink data, and when it is determined that the communications node has sent a pre-configured transmission resource configuration to the terminal, the downlink data is included in a paging message.

[0175] In some embodiments, the method comprises the communication device sending the data to the terminal using a dedicated Radio Network Temporary Identifier (RNTI).

[0176] In some embodiments, the method includes a communication device sending a pre-configured transmission resource information reconfiguration message to the core network node, wherein the pre-configured transmission resource information release message includes a terminal-level dedicated message and at least one of: pre-configured transmission resource information indicating a time domain location; and a non-access stratum (NAS) identifier of the terminal.

[0177] In some embodiments, the method includes the communication device sending a pre-configured transmission resource information release message to the core network node, wherein the pre-configured transmission resource information release message includes a terminal-level dedicated message.

[0178] In some embodiments, the preconfigured transmission resource information release message includes a terminal identifier, and wherein the preconfigured transmission resource information identifies a preconfigured uplink resource (PUR).

[0179] In some embodiments, a wireless communication method includes a communication node establishing a terminal-specific connection with a core network node before or at a time domain location of a preconfigured transmission resource. The method also includes the communication node receiving data from the core network node.

[0180] In some embodiments, the method includes: the communication node performing downlink resource scheduling by using the downlink PDCCH search space and a dedicated radio network temporary identifier (RNTI) included in the pre-configured transmission resource information; and the communication node sending the data to the terminal.

[0181] In some embodiments, downlink data is sent from the core network node to the communications node via a terminal specific connection.

[0182] In some embodiments, the method includes: the communication node receives a paging message from the core network node based on determining that the communication node has not yet sent a pre-configured transmission resource configuration to the terminal; and the communication node sends a response to the paging message to the core network node via an S1 interface to establish a terminal-specific connection from the communication node to the core network node, wherein once the connection is established, the data is received by the communication node.

[0183] In some embodiments, the method includes: the communication node schedules resource grant (CSS-Paging) of a physical downlink shared channel (PDSCH) based on the PDCCH common search space using a PDCCH scrambled with a common RNTI; and the communication node uses the PDSCH to send a message, wherein the message includes dedicated resource configuration information, and the dedicated resource configuration information includes at least one of the following: a terminal-specific RNTI; an uplink (UL) resource grant (ULGrant); and a physical downlink control channel (PDCCH) search space.

[0184] In some embodiments, the method includes the communication node receiving a message using a physical uplink shared channel (PUSCH) on resources indicated by a UL Grant, wherein the message is sent after the terminal receives a downlink message carried by a PDSCH.

[0185] In some embodiments, the method includes the communication node sending a paging response to the core network node based on receiving a message from the terminal using a PUSCH through a UL Grant, wherein the paging response indicates that data transmission is completed.

[0186] In some embodiments, the method includes the communication node sending a preconfigured transmission resource configuration message to a terminal to configure or reconfigure the preconfigured transmission resource for the terminal.

[0187] In some embodiments, the method includes the communication node receiving a paging message from the core network node, and establishing a terminal-specific connection from the communication node to the core network node based on receiving the paging message.

[0188] In some embodiments, the method includes the communication node sending a release message to the core network node based on determining that uplink and downlink data transmission is complete.

[0189] In an embodiment, a wireless communication method includes a communication node receiving a paging message from a core network node within a predetermined duration before pre-configured transmission resource information. The method also includes the communication node forwarding the paging message to a terminal, wherein the second paging message includes a time delay. The method also includes the communication node monitoring data from the terminal through the pre-configured transmission resources to establish a terminal-specific connection from the communication node to the core network node.

[0190] In some embodiments, the method includes: the communication node determines that the time delay is greater than a predetermined duration or a pre-configured transmission resource PDCCH monitoring duration; the communication node sends a connection message to the core network node to establish an S1 interface connection; the communication node receives downlink data from the core network node through the S1 interface; the communication node performs downlink resource scheduling by using the downlink PDCCH search space and a dedicated radio network temporary identifier (RNTI) included in the pre-configured transmission resource information within the time delay; and the communication node sends the downlink data to the terminal.

[0191] In some embodiments, the method includes: the communication node receiving uplink data carried in the preconfigured transmission resource information from the terminal; and the communication node sending a terminal-specific S1 connection message to connect to the core network node through a terminal-level S1 interface.

[0192] In some embodiments, the method includes: the communication node determines that the pre-configured transmission resource information received by the terminal does not carry terminal uplink data, wherein the terminal is configured to not monitor the PDCCH search space associated with the pre-configured transmission resources based on determining that the pre-configured transmission resource information does not carry terminal uplink data; and the communication node uses a common search space (CSS) for paging to send a paging message to the terminal.

[0193] In some embodiments, the predetermined duration is less than a paging retransmission timer, wherein the paging message does not include a paging extended discontinuous reception (eDRX) parameter.

[0194] In some embodiments, the paging message comprises an eDRX parameter, wherein the predetermined duration is less than a paging retransmission timer, and wherein the communications node is configured to modify the predetermined duration.

[0195] In an embodiment, a wireless communication method includes: a communication device sends a PDCCH common search space (CSS) corresponding to a pre-configured transmission resource to a terminal, wherein the sent system information block (SIB) includes the pre-configured transmission resource PDCCH common search space configuration information; and the communication device sends a message including the pre-configured transmission resource CSS index to the terminal.

[0196] In some embodiments, the transmitting includes a physical downlink control channel (PDCCH) search space, and a first PDCCH common search space configuration associated with a first enhanced coverage level and a second PDCCH common search space configuration associated with a second enhanced coverage level.

[0197] In some embodiments, each of the first PDCCH common search space configuration and the second PDCCH common search space configuration includes at least one of: a starting position for PDCCH monitoring, a parameter for determining the starting position for PDCCH monitoring, a time interval for PDCCH monitoring, a parameter for determining the PDCCH monitoring time interval, and a maximum number of repetitions of the PDCCH.

[0198] In some embodiments, the method includes: configuring the preconfigured transmission resource, and a preconfigured transmission resource CSS index associated with the preconfigured transmission resource; and configuring the monitoring duration of the preconfigured transmission resource CSS during a radio resource control (RRC) connection state or a data transmission state based on the preconfigured transmission resource.

[0199] In some embodiments, the method includes the communication device sending an RRC connection release message in an RRC connected state or in a data transmission state based on pre-configured transmission resources.

[0200] In an embodiment, a wireless communication method includes: a communication node sends a preconfigured transmission resource allocation to a terminal, and the preconfigured transmission resource allocation transmission includes terminal-specific preconfigured transmission resource PDCCH search space configuration information; the communication node receives data transmission from the terminal through a preconfigured transmission resource position at a time domain position for the preconfigured transmission resource PDCCH search space configuration information; and the communication node schedules a terminal-specific PDCCH search space and a terminal-specific identifier within a timer or a predetermined duration, wherein the terminal is configured to monitor the terminal-specific preconfigured transmission PDCCH search space within the timer or the predetermined duration.

[0201] In some embodiments, the terminal-specific pre-configured transmission resource PDCCH search space configuration information includes at least one of the following: a maximum duration for a terminal to monitor the terminal-specific pre-configured transmission resource PDCCH search space; a timer for the terminal to stop monitoring the terminal-specific pre-configured transmission resource PDCCH search space based on determining that no data is sent or received; a terminal-specific radio network temporary identifier (RNTI) for the terminal-specific pre-configured transmission resource PDCCH search space; and a time domain location for the pre-configured transmission resource information.

[0202] In some embodiments, the terminal-specific pre-configured transmission resource PDCCH search space configuration information includes at least one of the following: a starting position for physical downlink control channel (PDCCH) monitoring; a parameter for determining the starting position for PDCCH monitoring; a time interval for PDCCH monitoring; a parameter for determining the PDCCH monitoring time interval; and a PDCCH, wherein the terminal-specific RNTI for the terminal-specific pre-configured transmission resource PDCCH search space is valid during the period during which the terminal monitors the terminal-specific pre-configured transmission resource PDCCH search space, or during the maximum duration during which the terminal monitors the terminal-specific pre-configured transmission resource PDCCH search space, and wherein the maximum duration for the UE to monitor the terminal-specific pre-configured transmission resource PDCCH search space starts at the time domain position used for the pre-configured transmission resource information, or starts at the time when the terminal starts monitoring the terminal-specific pre-configured transmission resource PDCCH search space.

[0203] In some embodiments, the method includes: the communication node determines that the terminal uplink data is not sent from the terminal through the pre-configured transmission resource location; and the communication node starts the terminal-specific pre-configured transmission resource PDCCH search space timer based on receiving a message sent from the terminal at the pre-configured transmission resource location.

[0204] In some embodiments, the method comprises: the communications node sending a message for triggering a switch to a Radio Resource Control (RRC) idle state to the terminal upon expiration of a pre-configured transmission resource PDCCH search space timer specific to the terminal.

[0205] In some embodiments, the method includes: the communication node sends PDCCH scheduling information before the terminal-specific pre-configured transmission resource PDCCH search space timer expires, wherein the terminal is configured to perform data sending and receiving based on the PDCCH scheduling information; and the communication node resets the terminal-specific pre-configured transmission resource PDCCH search space timer.

[0206] In some embodiments, the method includes: the communication node sends a PDCCH response message to the terminal based on determining that the pre-configured transmission resource location from the terminal has sent uplink terminal data; the communication node starts a terminal-specific pre-configured transmission resource PDCCH search space timer based on receiving the pre-configured transmission resource location from the terminal; and the communication node sends a message for triggering a switch to an RRC idle state to the terminal as soon as the terminal-specific pre-configured transmission resource PDCCH search space timer expires.

[0207] In some embodiments, the method includes: the communication node determines that the pre-configured transmission resource location from the terminal has sent uplink terminal data; and the communication node, based on determining that the pre-configured transmission resource location from the terminal has sent uplink data, sends an RRC reconfiguration message to the terminal before the terminal-specific pre-configured transmission resource PDCCH search space timer expires, wherein the terminal is configured to enter an RRC connected state upon receiving the RRC reconfiguration message.

[0208] In some embodiments, the method includes the communication node determining that a pre-configured transmission resource location from the terminal has sent uplink terminal data; the communication node sending a PDCCH instruction to the terminal; the communication node receiving a contention-free random access channel (CFRA) message from the terminal; the communication node sending a PDCCH message to the terminal via a terminal-specific pre-configured transmission resource PDCCH search space, wherein as soon as the PDCCH message is sent, a terminal-specific pre-configured transmission resource PDCCH search space timer is started.

[0209] In some embodiments, the method includes: the communication node determines a pre-configured transmission resource location from the terminal to send including uplink terminal data; the communication node sends a PDCCH instruction to the terminal; the communication node receives a CFRA message from the terminal; and the communication node sends a PDSCH message, the PDSCH message including a timing advance (TA) command medium access control (MAC) control element (CE) or a random access response (RAR) message, wherein as soon as the PDSCH message is sent, a terminal-specific pre-configured transmission resource PDCCH search space timer is started.

[0210] In some embodiments, the method includes: the communication node determines that the pre-configured transmission resource location from the terminal sends uplink terminal data; the communication node sends a PDCCH instruction to the terminal; the communication node receives a contention-free random access (CFRA) message from the terminal; the communication node sends a PDSCH message, the PDSCH message includes a TA command and a MAC CE, wherein as soon as the PDSCH message is sent, a terminal-specific pre-configured transmission resource PDCCH search space timer is started; and the communication node receives a PUSCH message including a C-RNTI MAC CE, wherein as soon as the PUSCH message is received, a terminal-specific pre-configured transmission resource PDCCH search space timer is started.

[0211] In some embodiments, the preconfigured transmission resource allocation transmission includes a traffic pattern corresponding to the preconfigured transmission resources.

[0212] In some embodiments, the business mode includes at least one of: a preconfigured transmission resource sending start time; a periodic preconfigured transmission resource sending interval; a periodic preconfigured maximum valid duration or a valid timer of the transmission resource; and superposition information of multiple business modes.

[0213] In some embodiments, the traffic pattern is expressed in terms of absolute pre-configured transmission resource sending start times.

[0214] In some embodiments, the traffic pattern is expressed using an offset value relative to an absolute time.

[0215] Fig. 9 An example of a wireless communication system in which the technology according to one or more embodiments of the present technology can be applied is shown. The wireless communication system 900 may include one or more base stations (BSs) 905a, 905b, one or more wireless devices 910a, 910b, 910c, 910d, and a core network 925. The base stations 905a, 905b may provide wireless services to the wireless devices 910a, 910b, 910c, and 910d in one or more wireless sectors. In some implementations, the base stations 905a, 905b include directional antennas that generate two or more directional beams to provide wireless coverage in different sectors.

[0216] The core network 925 can communicate with one or more base stations 905a, 905b. The core network 925 provides connections with other wireless communication systems and wired communication systems. The core network may include one or more service subscription databases storing information related to subscribed wireless devices 910a, 910b, 910c and 910d. The first base station 905a can provide wireless services based on a first radio access technology, and the second base station 905b can provide wireless services based on a second radio access technology. Base stations 905a and 905b can be located at the same place, or can be installed separately on site according to the deployment scenario. Wireless devices 910a, 910b, 910c and 910d can support multiple different radio access technologies.

[0217] In some implementations, a wireless communication system may include multiple networks using different wireless technologies. A dual-mode or multi-mode wireless device includes two or more wireless technologies that can be used to connect to different wireless networks.

[0218] Fig.10 1005 is a block diagram representation of a portion of a hardware platform. A hardware platform 1005 (such as a network device or base station or wireless device (or UE)) may include a processor electronic device 1010, such as a microprocessor, that implements one or more of the technologies presented in the present invention. The hardware platform 1005 may include a transceiver electronic device 1015 that sends and / or receives wired signals or wireless signals through one or more communication interfaces (such as an antenna 1020 or a wire line interface). The hardware platform 1005 may implement other communication interfaces with defined protocols for sending and receiving data. The hardware platform 1005 may include one or more memories (not explicitly shown) configured to store information such as data and / or instructions. In some implementations, the processor electronic device 1010 may include at least a portion of the transceiver electronic device 1015. In some embodiments, at least some of the disclosed technologies, modules, or functions are implemented using the hardware platform 1005.

[0219] From the foregoing, it will be appreciated that specific embodiments of the presently disclosed technology have been described herein for purposes of illustration, but that various modifications may be made without departing from the scope of the invention. Accordingly, the presently disclosed technology is not to be limited, except by the appended claims.

[0220] The disclosed and other embodiments, modules and functional operations described in the present invention can be implemented in digital electronic circuit systems, or in computer software, firmware or hardware (including the structures disclosed in the present invention and their structural equivalents), or in a combination of one or more of them. The disclosed and other embodiments can be implemented as one or more computer program products, that is, one or more modules of computer program instructions encoded on a computer-readable medium for data processing equipment to execute or control the operation of the data processing equipment. The computer-readable medium can be a machine-readable storage device, a machine-readable storage substrate, a memory device, a composition of matter that implements a machine-readable propagation signal, or a combination of one or more of them. The term "data processing equipment" includes all devices, devices and machines for processing data, including, for example, a programmable processor, a computer or multiple processors or computers. In addition to hardware, the device may also include code that creates an execution environment for the computer program in question, for example, code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them. A propagation signal is an artificially generated signal generated to encode information for transmission to a suitable receiver device, for example, a machine-generated electrical signal, an optical signal, or an electromagnetic signal.

[0221] A computer program (also referred to as a program, software, software application, script or code) can be written in any form of programming language (including compiled or interpreted languages), and it can be deployed in any form, including being deployed as a stand-alone program or being deployed as a module, component, subroutine or other unit suitable for use in a computing environment. A computer program does not necessarily correspond to a file in a file system. A program may be stored in a portion of a file that stores other programs or data (e.g., one or more scripts stored in a markup language invention), a single file dedicated to the program in question, or multiple coordinated files (e.g., files storing one or more modules, subroutines, or code portions). A computer program may be deployed on a computer, or on multiple computers that are placed at a site or distributed between multiple sites and interconnected by a communication network.

[0222] The processes and logic flows described in the present invention may be performed by one or more programmable processors that execute one or more computer programs that perform functions by operating on input data and generating outputs. The processes and logic flows may also be performed by a dedicated logic circuit system (e.g., an FPGA (thread programmable gate array) or an ASIC (application-specific integrated circuit)), and the device may also be implemented as a dedicated logic circuit system (e.g., an FPGA (thread programmable gate array) or an ASIC (application-specific integrated circuit)).

[0223] Processors suitable for executing computer programs include, for example, both general-purpose and special-purpose microprocessors, and any one or more processors of any kind of digital computer. Typically, the processor will receive instructions and data from a read-only memory or a random access memory or both. The basic elements of a computer are a processor for executing instructions, and one or more memory devices for storing instructions and data. Typically, a computer will also include one or more mass storage devices (e.g., magnetic disks, magneto-optical disks, or optical disks) for storing data, or be operatively coupled to receive data from one or more mass storage devices (e.g., magnetic disks, magneto-optical disks, or optical disks) for storing data, or to transfer data to these mass storage devices, or to both receive data from one or more mass storage devices (e.g., magnetic disks, magneto-optical disks, or optical disks) for storing data, and to transfer data to these mass storage devices. However, a computer need not have such a device. Computer-readable media suitable for storing computer program instructions and data include all forms of nonvolatile memory, media and memory devices, including, for example, semiconductor memory devices, such as EPROM, EEPROM and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CD ROM and DVD-ROM disks. The processor and memory may be supplemented by, or incorporated in, a dedicated logic circuit system.

[0224] Although this patent invention contains many details, these should not be interpreted as limitations on the scope of any invention or the scope of what can be claimed, but should be interpreted as descriptions of features that can be specific to a particular embodiment of a particular invention. Certain features described in the context of separate embodiments in this patent invention can also be implemented in combination in a single embodiment. Conversely, the various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or in any suitable sub-combination. Moreover, although features may be described above as acting in certain combinations, setting the action as initially claimed, one or more features from the claimed combination may be removed from the combination in some cases, and the claimed combination may be for a sub-combination or a variation of a sub-combination.

[0225] Similarly, although operations are depicted in a particular order in the drawings, this should not be understood as requiring that such operations be performed in the particular order shown or in a sequential order, or that all illustrated operations be performed to achieve the desired results. Moreover, the separation of various system components in the embodiments described in this patent invention should not be understood as requiring such separation in all embodiments.

[0226] Only a few implementations and examples are described, and other implementations, enhancements and variations may be made based on what is described and illustrated in this patent invention.

Claims

1. A wireless communication method, comprising: The communication node causes the terminal to transition from a radio resource control connected state to a radio resource control idle state; The communication node sends the terminal-specific dedicated message to a core network node, the terminal-specific dedicated message comprising pre-configured transmission resource information indicating a time domain location of dedicated resources for transmission in the radio resource control idle state; and The communication node receives data from the core network node before or at a time domain position indicated by preconfigured transmission resource information.

2. The method according to claim 1, wherein the data received at the communication node comprises at least one of: paging information; paging information including user data; and user data with a non-access stratum (NAS) identifier of the terminal.

3. The method according to claim 1, further comprising: The communication node sends the data to the terminal using a dedicated radio network temporary identifier RNTI.

4. The method according to claim 1, further comprising: The communication node sends pre-configured transmission resource information to the core network node, wherein the pre-configured transmission resource information includes a terminal identifier. The method according to claim 1 , wherein the preconfigured transmission resource information comprises a preconfigured uplink resource (PUR).

6. The method according to claim 1, further comprising: The communication node establishes a terminal-specific connection with the core network node before or at a time domain location based on preconfigured transmission resource information.

7. The method according to claim 6, further comprising: The communication node performs downlink resource scheduling by using a physical downlink control channel PDCCH search space and a dedicated radio network temporary identifier RNTI included in the pre-configured transmission resource information; and The communication node sends the data to the terminal.

8. A wireless communication method, comprising: The communication node causes the terminal to transition from a radio resource control connected state to a radio resource control idle state; the communications node receiving a paging message from a core network node within a predetermined duration prior to receiving pre-configured transmission resource information indicating dedicated resources for transmission in the radio resource control idle state; The communication node forwards the paging message to the terminal, wherein the paging message includes a time delay; and The communication node monitors data sent from the terminal via preconfigured transmission resources to establish a terminal-specific connection from the communication node to the core network node.

9. The method according to claim 8, further comprising: The communications node determines that the time delay is greater than a predetermined duration or a preconfigured transmission resource PDCCH monitoring duration; The communication node sends a connection message to the core network node to establish an S1 interface connection; The communication node receives downlink data from the core network node via the S1 interface; The communication node performs downlink resource scheduling by using a downlink PDCCH search space and a dedicated radio network temporary identifier RNTI included in the preconfigured transmission resource information within the time delay; and The communication node transmits the downlink data to the terminal.

10. The method according to claim 8, further comprising: The communication node receives uplink data carried in the pre-configured transmission resource information from the terminal; and The communication node sends a terminal-specific S1 connect message to connect to the core network node via a terminal-level S1 interface.

11. The method of claim 8, wherein the paging message comprises a paging eDRX parameter, wherein the predetermined duration is less than a paging retransmission timer and less than a paging time window PTW length, wherein the paging retransmission timer is defined by the communication node and / or sent by the core network node, wherein the communication node is configured to define and / or modify the predetermined duration.

12. A wireless communication method, comprising: The communication node causes the terminal to transition from a radio resource control connected state to a radio resource control idle state; The communication node sends a preconfigured transmission resource allocation to the terminal, wherein the preconfigured transmission resource allocation includes terminal-specific preconfigured transmission resource physical downlink control channel PDCCH search space configuration information and preconfigured dedicated resources for transmission in the radio resource control idle state; The communication node receives data transmission from the terminal via a preconfigured transmission resource location; and The communications node transmits a PDCCH associated with a terminal-specific identifier within a timer or a predetermined duration, wherein the terminal is configured to monitor the terminal-specific pre-configured transmission PDCCH search space within the timer or the predetermined duration.

13. The method according to claim 12, further comprising: The communication node determines that terminal uplink data is not sent from the terminal via the preconfigured transmission resource location; and The communication node starts a PDCCH search space timer for the pre-configured transmission resource specific to the terminal based on the information sent by the pre-configured transmission resource position received from the terminal.

14. The method according to claim 12, further comprising: The communication node sends a PDCCH response message to the terminal based on determining that the pre-configured transmission resource location from the terminal has sent uplink terminal data; The communication node starts a terminal-specific pre-configured transmission resource PDCCH search space timer based on receiving the pre-configured transmission resource position transmission from the terminal; and The communication node sends a message to the terminal to switch to the RRC idle state upon expiration of a PDCCH search space timer of a pre-configured transmission resource specific to the terminal.

15. The method according to claim 12, further comprising: The communication node determines that the preconfigured transmission resource location from the terminal transmits uplink terminal data; and The communication node sends uplink data based on determining a pre-configured transmission resource location from the terminal, and sends an RRC connection establishment, RRC connection recovery or RRC connection reconfiguration message to the terminal before the terminal-specific pre-configured transmission resource PDCCH search space timer expires, wherein the terminal is configured to enter an RRC connected state upon receiving the RRC message.

16. The method of claim 15, wherein: The RRC connection establishment, RRC connection recovery or RRC connection reconfiguration message carries the C-RNTI; If the UE receives the RRC connection establishment, RRC connection recovery or RRC connection reconfiguration message, the UE transitions to the RRC connected state based on the RRC message; If the C-RNTI is carried in the RRC connection reconfiguration message, the UE uses the C-RNTI in the RRC connected mode; If the C-RNTI is not carried in the RRC connection reconfiguration message, the UE uses the RNTI used before receiving the RRC reconfiguration message to scramble the original RNTI.

17. A wireless communication device, comprising a processor and a memory, wherein the processor is configured to read instructions from the memory to execute the method according to any one of claims 1 to 16.

Images