Method and system for data transmission in a wireless network

Abstract

Methods, apparatuses, and systems are described for improving data transmission efficiency in a wireless network. In one example aspect, a wireless communication method includes receiving, by a signaling node in a first node having a suspended connection with a terminal, resume information, receiving, by the signaling node from a second node, a message associated with the resume request information, and instructing, by the signaling node, the first node to provide context information of the terminal directly to the second node.

Description

Technical Field

[0001] This application generally pertains to wireless communication. Background Technology

[0002] Efforts are underway to define the next generation of wireless communication networks, which will offer greater deployment flexibility, support for a wider range of devices and services, and diverse technologies for efficient bandwidth utilization. The next generation of wireless communication networks also anticipates the deployment of a new core network that provides additional services and flexibility beyond those currently available. Summary of the Invention

[0003] This application provides techniques for improving data transmission efficiency in wireless networks.

[0004] In one example embodiment of the disclosed technology, a wireless communication method is disclosed. This wireless communication method includes: a signaling node receiving recovery information in a first node having a suspend connection with a terminal; the signaling node receiving a message associated with recovery request information from a second node; and the signaling node instructing the first node to directly provide the second node with context information of the terminal.

[0005] In another example embodiment of the disclosed technology, a wireless communication method is disclosed. This wireless communication method includes: a signaling node sending a paging message to a second node, instructing the second node to receive an access request from a terminal; the signaling node receiving a message requesting context information of the terminal from the second node via an application protocol provided between the radio access network and the core network; and instructing the second node to obtain a context response associated with the terminal from a first node or the signaling node.

[0006] In another example embodiment of the disclosed technology, a wireless communication method is disclosed. This wireless communication method includes: performing a connection suspension process to suspend the connection between a terminal and a first base station; providing a paging message from a mobility management entity to a second base station; and enabling the second base station to obtain context information of the terminal from at least one of the first base station or the mobility management entity.

[0007] In another example embodiment of the disclosed technology, the above method is embodied in the form of process executable code and stored in a computer-readable process medium.

[0008] In another example embodiment of the disclosed technology, a device configured or operable to perform the above-described methods is disclosed.

[0009] The above and other aspects and their embodiments will be described in more detail in the drawings, specification and claims. Attached Figure Description

[0010] Figure 1 An example of a wireless communication system is shown.

[0011] Figure 2 This is a flowchart illustrating an example process performed by a component of a communication system.

[0012] Figure 3 This is a flowchart illustrating another example process performed by a component of a communication system.

[0013] Figure 4 This is a flowchart illustrating yet another example process performed by a component of a communication system.

[0014] Figure 5 This is a flowchart illustrating yet another example process performed by a component of a communication system.

[0015] Figure 6 This is an example flowchart of obtaining terminal context between different base stations based on new base station requests, core network notifications, and old base station responses, based on some embodiments of the disclosed technology.

[0016] Figure 7 This is a flowchart illustrating how to obtain terminal context between different base stations based on new base station requests and core network responses, according to some embodiments of the disclosed technology.

[0017] Figure 8 This is a flowchart illustrating an example process performed by components of a communication system implemented based on some embodiments of the disclosed technology.

[0018] Figure 9 This is a flowchart illustrating another example process performed by components of a communication system implemented based on some embodiments of the disclosed technology.

[0019] Figure 10 This is a flowchart illustrating an example of a wireless communication method based on some embodiments of the disclosed technology.

[0020] Figure 11 This is a flowchart illustrating another example of a wireless communication method based on some embodiments of the disclosed technology.

[0021] Figure 12 This is a flowchart illustrating another example of a wireless communication method based on some embodiments of the disclosed technology.

[0022] Figure 13 This is a block diagram representation of a portion of a wireless site according to one or more embodiments to which the present technology may be applied. Detailed Implementation

[0023] Figure 1An example of a wireless communication system (e.g., an LTE, 5G New Radio (NR) cellular network) including a radio access node 120 and one or more user equipments (UEs) 111, 112, and 113 is illustrated. In some embodiments, downlink transmissions (141, 142, 143) include control plane messages that include a procedure sequence for procuring multiple user plane functions. This can be followed by uplink transmissions (131, 132, 133) based on the procedure sequence received by the UE. Similarly, user plane functions can be processed by the UE based on the received procedure sequence of downlink transmissions. The UE can be, for example, a smartphone, tablet, mobile computer, machine-to-machine (M2M) device, terminal, mobile device, Internet of Things (IoT) device, etc.

[0024] The examples used in this application from the 3GPP New Radio (NR) network architecture and 5G protocols are for ease of understanding only, and the disclosed technologies and embodiments can be practiced in other wireless systems using communication protocols different from the 3GPP protocols.

[0025] The R15 IoT standard (e.g., Narrowband IoT / Enhanced Machine Type Communication [eMTC]) supports efficient uplink packet transmission, such as Mobile Terminal Initiated Early Data Transmission (MO-EDT). For example, a terminal can directly encapsulate small uplink data within uplink signaling during random access, allowing the terminal and network to resolve conflicts, and the data transmission is considered successful. No wireless connection is required between the terminal and the network, and the terminal remains idle at all times.

[0026] The R16 IoT standard discussion introduced a new Mobile Terminal Termination Early Data Transmission (MT-EDT) feature, primarily targeting IoT applications or services where downlink data transmission may dominate. To further improve transmission efficiency, the standard is discussing the following basic MT-EDT process.

[0027] Figure 2 This is a flowchart illustrating an example process performed by a component of a communication system.

[0028] Upon receiving a paging message from the core network, the base station determines that an MT-EDT procedure needs to be triggered, and the base station sends a first air interface transmission to the terminal. In some implementations, the first air interface transmission may include a paging message, and the paging message carries terminal-specific (e.g., contention-free) random access resources and information related to a terminal-specific Radio Network Temporary Identifier (RNTI) used to identify uplink and downlink transmissions. In some implementations, the RNTI is used to distinguish / identify connected UEs in the cell, a specific radio channel, a group of UEs in paging condition, a group of UEs for which power control is issued by the eNB, and system information sent for all UEs.

[0029] The terminal learns of its own specific random access resource and sends a second air interface transmission based on the information about the resource. In some implementations, the terminal-specific random access resource may include a contention-free random access resource. In this case, the terminal uses the contention-free random access resource to send the random access preamble, which minimizes conflicts between terminals.

[0030] Upon receiving a random access preamble sent by the terminal on a contention-free random access resource, the base station triggers a related process to request downlink data from the core network, and then the base station sends a third air interface transmission to the terminal. In some implementations, the third air interface transmission includes downlink data. This downlink transmission is scrambled with a terminal-specific RNTI. The downlink transmission may also include the terminal's latest timing advance information.

[0031] After receiving downlink data, the terminal sends a fourth air interface transmission to the base station. In some implementations, the uplink transmission is scrambled by a terminal-specific RNTI. The uplink transmission may include uplink physical layer acknowledgments, or media access control (MAC) layer acknowledgments, or radio resource control (RRC) layer acknowledgments, or application layer acknowledgments for the received downlink data.

[0032] In the above basic process, for uplink transmission, before the third air interface transmission, the base station needs to obtain the context information associated with the terminal in order to encrypt the downlink data, and then send the encrypted downlink data through the air interface. However, there may be a situation where the connection is suspended at the first base station, the terminal's context is stored at the first base station, and the first base station assigns a ResumeID to the terminal to identify the stored terminal context. Then, if the second base station is within the same core network coverage area as the first base station, the terminal moves to the second base station. Upon receiving downlink data for the terminal, the core network determines that the terminal is in an idle state and initiates a paging message to the terminal. The core network can then send paging messages to multiple base stations with available coverage (e.g., the first base station and the second base station). The first base station and the second base station respectively trigger the MT-EDT procedure for the terminal.

[0033] However, only the second base station detects the terminal-specific random access preamble on the dedicated random access resources allocated to the terminal. The second base station can obtain the terminal's System Architecture Evolution (SAE) - Temporary Mobile Subscriber Identity (S-TMSI) identification information and the address information of the core network registered by the terminal (e.g., the core network that sends paging messages to the terminal / base station). The second base station can also initiate interface establishment or recovery to the core network and obtain downlink data for the terminal. However, because the second base station lacks the terminal's context information and the ResumeID used to identify the context, as well as the address information where the first base station stores the terminal's context information, the second base station cannot obtain the terminal context or encrypt the downlink data.

[0034] Figure 3 This is a flowchart illustrating another example process performed by a component of a communication system.

[0035] In one embodiment of the disclosed technology, when the previous connection is suspended, the first base station assigns a ResumeID to the terminal, and the ResumeID and necessary security information are transmitted to the core network via uplink signaling between the base station and the core network, and stored by the core network. Here, the first base station may also transmit security information to later determine whether the second base station is a trusted base station. During the next paging process, the core network carries the ResumeID and security information from the paging message to one or more second base stations. After one of the second base stations detects the terminal-specific random access preamble, the second base station learns the address information of the first base station based on the ResumeID and security information. Then, using an existing inter-base station context retrieval procedure, the ResumeID and security information are provided to the first base station, and then the terminal's context information is obtained from the first base station.

[0036] In some cases, Access Layer (AS) terminal context-related information needs to be sent to and stored in the core network. Furthermore, since the core network can send paging messages to multiple base stations when sending a paging message, in the next paging process, the core network needs to send the terminal-associated context information to multiple base stations within the paging area, which can result in significant signaling overhead.

[0037] Figure 4 This is a flowchart illustrating yet another example process performed by a component of a communication system.

[0038] In another embodiment of the disclosed technology, to avoid sending AS layer information to the Mobility Management Entity (MME) and storing it in the MME, the terminal context can also be indirectly identified by using the base station-core network interface identifier (eNB UE S1 Application Protocol (S1AP) ID) assigned to the terminal by the first base station during the previous connection. When downlink data for the terminal is received, the MME can obtain information about the first base station in the terminal's previous connection, including the first base station's eNB ID and eNB UE S1AP ID. The MME can carry the information in the paging message to the second base station. After the second base station detects the terminal-specific random access preamble, the second base station can trigger an inter-base station terminal context retrieval process to the first base station based on the first base station's eNB ID and provide the eNB UE S1AP ID information to the first base station, so that the first base station can search for the terminal's context information based on this information and respond to the second base station.

[0039] In some implementations, S1AP provides signaling services between the Evolved Terrestrial Radio Access Network (E-UTRAN) and the Evolved Packet Core Network (EPC) required to implement S1AP functionality. S1AP services are divided into two groups: non-UE-associated services, which relate to the entire S1 interface instance between the eNB and MME utilizing non-UE-associated signaling connections; and UE-associated services, which relate to a single UE. The S1AP functionality providing these services is associated with the UE-associated signaling connections maintained for the UE.

[0040] Figure 5 This is a flowchart illustrating yet another example process performed by a component of a communication system.

[0041] refer to Figure 3 and 4The example procedure discussed requires triggering a terminal context retrieval process between base stations, where the first base station needs to send the complete terminal context to the second base station. To avoid the aforementioned overhead, and considering that only partial context information is needed to complete the data encryption operation, a new partial context can be defined, which only includes information related to the security key. When the previous connection was suspended, the first base station constructs the partial context and carries it to the core network during the uplink signaling and core network interface suspension process, storing it in the core network. During the next paging process, the core network carries the partial context from the paging message to the second base station. After the second base station detects the terminal-specific random access preamble, it retrieves the terminal's downlink data from the core network, directly encrypts the downlink data using the partial context, and sends the data to the terminal over the air interface.

[0042] This example process also requires sending AS layer terminal context-related information to the core network and storing it in the core network. Considering that the core network can send paging messages to multiple base stations, storing and sending this part of the context will cause a huge overhead on the interface between the base station and the core network.

[0043] In the example discussed with reference to Figures 3-5, the paging message on the interface between the base station and the core network needs to carry terminal context information, and this information can be sent to multiple target base stations. In some implementations, only one target base station receives the terminal-specific random access preamble, and only this target base station needs to initiate the terminal context retrieval process. Therefore, sending terminal context information to multiple base stations may result in unnecessary signaling overhead.

[0044] In one embodiment of the disclosed technology, the process for obtaining terminal context between different base stations is based on a new base station request, core network notification, and old base station response (see [link to documentation]). Figure 6 The paging messages between the base station and the core network do not need to be enhanced, and the new base station will only request the terminal context and / or security-related information from the core network after receiving a dedicated random access preamble sent by the terminal, and the core network will request the old base station to send the terminal context to the new base station.

[0045] In another embodiment of the disclosed technology, the process for obtaining terminal context between different base stations is based on a new base station request and a core network response (see [link]). Figure 7 The paging messages between the base station and the core network do not need to be enhanced. The new base station only requests the terminal context and / or security-related information from the core network after receiving a dedicated random access preamble sent by the terminal. The terminal context is obtained from the old base station and sent to the new base station by the core network.

[0046] In some embodiments of the disclosed technology, the core network is configured to carry terminal context-related information in paging instead of storing the AS context in the core network. This example procedure also avoids sending the same paging message to multiple base stations.

[0047] Figure 6 This is an example flowchart of obtaining terminal context between different base stations based on new base station requests, core network notifications, and old base station responses, based on some embodiments of the disclosed technology.

[0048] The terminal suspends the connection from the first base station (old base station) before moving to the second base station (new base station). After the new base station receives a paging message from the core network, it determines that an MT-EDT procedure needs to be triggered, and the new base station sends a first air interface transmission (e.g., a paging message) to the terminal via the air interface. This paging message carries terminal-specific (e.g., contention-free) random access resources and related information, as well as a terminal-specific RNTI for identifying uplink and downlink transmissions for the terminal.

[0049] The terminal learns about the contention-free random access resource based on information about it. In some embodiments of the disclosed technology, the terminal uses the contention-free random access resource to send a random access preamble.

[0050] After receiving the random access preamble sent by the terminal on a contention-free random access resource, the new base station discovers that the context associated with the terminal is not stored based on the terminal identifier (e.g., NAS identifier), and the new base station triggers the following process to obtain downlink data from the core network;

[0051] 1. The new base station can determine the MME information registered by the terminal based on the received paging message, and then sends an S1 interface uplink message to the MME to request the terminal context. This S1 interface uplink message can be a new S1-AP message, or it can utilize an existing S1-AP message. The message contains a terminal identifier, which can be an eNB UE S1AP ID / MME UE S1AP ID interface information pair, or a terminal identifier S-TMSI. In some implementations, when using existing S1 interface uplink messages, Type 2 (Category 2) messages, such as eNB DIRECT INFORMATION TRANSFER or eNB TRANSFER MESSAGE, sent in unacknowledged mode, can be reused or optimized.

[0052] 2. The MME receives the S1 interface terminal context request message and locates the old base station information for the terminal context based on the terminal identifier. The MME then sends an S1 interface downlink message to the old base station to trigger terminal context transfer. The S1 interface downlink message can be a new S1-AP message or an existing S1-AP message. This message carries the terminal identifier and the eNB ID of the new base station. When using existing S1 interface uplink messages, Type 2 (Category 2) messages can be reused or optimized. These messages are those sent in unacknowledged mode, such as the MME DIRECT INFORMATION TRANSFER or MME CONFIGURATION TRANSFER messages.

[0053] 3. Upon receiving a downlink message from the MME requesting the transfer of terminal context via the S1 interface, the old base station obtains the terminal's context information based on terminal identifier matching. Then, using address information provided by the MME (e.g., the new base station's eNB ID), the old base station provides the terminal's context information to the new base station via the X2 interface. The old base station can use new X2-AP interface messages, or it can reuse or optimize existing UE CONTEXT RESPONSE messages to do this.

[0054] Figure 7 This is a flowchart illustrating how to obtain terminal context between different base stations based on new base station requests and core network responses, according to some embodiments of the disclosed technology.

[0055] Before moving to the second base station (new base station), the terminal suspends the connection from the first base station (old base station). After the new base station receives a paging message sent by the core network, it determines that the MT-EDT procedure needs to be triggered, and the new base station sends a first air interface transmission (e.g., a paging message) to the terminal via the air interface. This paging message carries terminal-specific (e.g., contention-free) random access resources and related information, as well as a terminal-specific RNTI for identifying uplink and downlink transmissions for the terminal.

[0056] The terminal learns about the contention-free random access resources based on the information about them, and then uses the contention-free random access resources to send the random access preamble.

[0057] After receiving the random access preamble sent by the terminal on a contention-free random access resource, the new base station discovers that the context associated with the terminal is not stored according to the terminal's NAS identifier, and the new base station triggers the following process to obtain downlink data from the core network.

[0058] 1. The new base station can determine the MME information registered by the terminal based on the received paging message, and then send an S1 interface uplink message to the MME to request the terminal context. This S1 interface uplink message can be a new S1-AP message, or it can utilize an existing S1-AP message. The message contains a terminal identifier, which can be an eNB UE S1AP ID / MME UE S1AP ID pair, or a terminal identifier S-TMSI. When using existing S1 interface uplink messages, Category 2 messages can be reused or optimized; these are messages sent in unacknowledged mode, such as eNB DIRECTINFORMATION TRANSFER or eNB TRANSFER MESSAGE.

[0059] 2. The MME receives the S1 interface terminal context request message and searches for old base station information storing the terminal context based on the terminal identifier. The MME then sends an S1 interface downlink message to the old base station to request the transfer of the terminal context. This S1 interface downlink message can be a new S1-AP message or an existing S1-AP message. The message carries the terminal identifier, and the terminal initiates a new cell ID for dedicated random access.

[0060] 3. The old base station receives the UE context request message sent by the MME, finds the terminal's context information, and sends an S1 interface uplink message to the core network, carrying the terminal context information. In some implementations, steps 2 and 3 can use a pair of Category 1 messages containing a request and a response.

[0061] 4. Upon receiving the terminal context message, the core network sends an S1 interface downlink message to the new base station and also sends the terminal context message to the new base station. In some implementations, the new base station may subsequently send an S1 interface uplink message to the core network to confirm that the terminal context information has been received. The S1 interface downlink message may be a new S1-AP message or an existing S1-AP message may be used. When using an existing S1 interface downlink message, a Category 2 message may be used. In some implementations, the message sent in acknowledgment mode may include a reused or optimized MME DIRECTINFORMATION TRANSFER or MME CONFIGURATION TRANSFER message.

[0062] In some implementations, steps 1 and 4 may also use a pair of Category 1 messages containing a request and a response. For example, steps 1 and 4 may also reuse or optimize the ENB CONFIGURATION UPDATE and ENB CONFIGURATION UPDATEACKNOWLEDGE messages, or the UE RADIO CAPABILITY MATCH REQUEST and UE RADIO CAPABILITY MATCH RESPONSE messages.

[0063] Figure 8 This is a flowchart illustrating an example process performed by components of a communication system implemented based on some embodiments of the disclosed technology.

[0064] In another embodiment of the disclosed technology, the old base station can send the terminal context to the core network and store it in the core network when the last connection was suspended. In this way, when the MME receives an S1 interface terminal context request message from the new base station, the MME can directly locate the stored terminal context information based on the terminal identifier, and then send the S1 interface downlink message to the new base station, thus passing the terminal context message to the new base station. The message flow is as follows: Figure 8 As shown.

[0065] This message flow also needs to send AS layer terminal context information to the core network and store it there. However, this message flow avoids the situation where paging messages on the interface between the base station and the core network need to carry terminal context information, and this information may be sent to multiple target base stations.

[0066] Figure 9 This is a flowchart illustrating another example process performed by components of a communication system implemented based on some embodiments of the disclosed technology.

[0067] like Figure 7 As shown, based on the embodiments of the disclosed technology, the terminal context between different base stations can be obtained based on a new base station request and a core network response. In another embodiment of the disclosed technology, the process by which the core network requests the terminal context from the old base station and passes it to the new base station can be implemented with reference to the inter-base station handover process. The message flow is as follows: Figure 9 As shown.

[0068] In some implementations, terminal context information can be placed in the UE history information element within the source eNB-to-target eNB transparent container information element and carried during optimized handover. The required message is transmitted from the old base station to the core network and then carried from the core network to the new base station in an optimized handover request message. The new base station can send an optimized handover request confirmation message to the MME for confirmation.

[0069] Figure 10 This is a flowchart illustrating an example of a wireless communication method based on some embodiments of the disclosed technology. The wireless communication method 1000 includes: at step 1010, a signaling node receiving recovery information in a first node having a pending connection with a terminal; at step 1020, a signaling node receiving a message associated with recovery request information from a second node; and at step 1030, a signaling node instructing the first node to directly provide the second node with context information of the terminal.

[0070] The wireless communication method 1000 may further include: receiving a context suspension request for a terminal by a signaling node, the context suspension request including an identifier identifying context information associated with the terminal. The wireless communication method 1000 may further include: receiving a context suspension request for a terminal by a signaling node, the context suspension request including an identifier of a first node. The wireless communication method 1000 may further include: receiving a context suspension request for a terminal by a signaling node, the context suspension request including an identifier of the terminal. The wireless communication method 1000 may further include: receiving a context suspension request for a terminal by a signaling node, the context suspension request including security information used by the first node to determine whether a second node is reliable. The wireless communication method 1000 may further include: receiving a context suspension request for a terminal by a signaling node, the context suspension request including an early data transmission security context terminated by the mobile terminal.

[0071] In some implementations, the message associated with the recovery request information includes the identifier of the terminal. In some implementations, the message used by the signaling node to instruct the first node to provide context information to the second node includes the identifier of the second node and / or the identifier of the terminal. In some implementations, the signaling node includes a Mobility Management Entity (MME). In some implementations, each of the first and second nodes includes an Evolved Node B (eNB).

[0072] Figure 11 This is a flowchart illustrating another example of a wireless communication method based on some embodiments of the disclosed technology. Wireless communication method 1100 includes, at step 1110, a signaling node sending a paging message to a second node; at step 1120, the second node receiving an access request from a terminal; at step 1130, the signaling node receiving a message requesting context information of the terminal from the second node via an application protocol provided between the radio access network and the core network; and at step 1140, instructing the second node to obtain a context response associated with the terminal from a first node or the signaling node.

[0073] The wireless communication method 1100 may further include sending a message from a signaling node to a first node to trigger the transmission of context information of a terminal. In some embodiments, the message triggering the transmission of context information of the terminal includes an identifier of the terminal. In some embodiments, the message triggering the transmission of context information of the terminal is provided via an application protocol provided between the radio access network and the core network. The wireless communication method 1100 may further include: causing the first node to directly send a message for a context response associated with the terminal to a second node. In some embodiments, the message is sent via an application protocol provided between the first and second nodes. The wireless communication method 1100 may further include: causing the first node to send a message for a context response associated with the terminal to a signaling node so that the second node can directly receive the context response associated with the terminal from the signaling node. In some embodiments, the message is sent via an application protocol provided between the radio access network and the core network. The wireless communication method 1100 may further include: the signaling node sending a message for responding to context information of the terminal to the second node via an application protocol provided between the radio access network and the core network. The wireless communication method 1100 may further include: receiving a context suspension request for the terminal from the first node by a signaling node before sending a paging message to the second node. In some embodiments, the signaling node includes a mobility management entity (MME). In some embodiments, each of the first and second nodes includes an evolved Node B (eNB).

[0074] Figure 12 This is a flowchart illustrating another example of a wireless communication method based on some embodiments of the disclosed technology. Wireless communication method 1200 includes, at step 1210, performing a connection suspension procedure to suspend the connection between a terminal and a first base station; at step 1220, providing a paging message to a second base station by a mobility management entity; and at step 1230, enabling the second base station to obtain UE context information from at least one of the first base station or the mobility management entity.

[0075] In some implementations, enabling the second base station to obtain the terminal's context information includes indirectly identifying the terminal's context information using a base station core network interface identifier assigned to the terminal by the first base station during the connection between the terminal and the first base station. In some implementations, indirectly identifying the terminal's context information includes triggering an inter-base station terminal context retrieval process, where the base station core network interface identifier is assigned to the terminal by the first base station.

[0076] The wireless communication method 1200 may further include: providing a message for a terminal context request to a second base station, providing a message for triggering a terminal context handover to a mobility management entity, and providing a message for a terminal context response to the second base station. The wireless communication method 1200 may also include: providing a message for a terminal context request to a mobility management entity, providing a message for triggering a terminal context handover to a first base station, providing a message for a terminal context handover response to a mobility management entity, and providing a message for a terminal context response to the second base station. In some embodiments, performing a connection suspension procedure to suspend the connection between the terminal and the first base station includes providing a message for a terminal context suspension request to a mobility management entity. The wireless communication method 1200 may also include: providing a message for a terminal context request to a mobility management entity, and providing a message for a UE context response to the second base station.

[0077] In some implementations, enabling the second base station to obtain the terminal's context information includes transmitting the terminal's context information to the second base station using an inter-base station handover procedure. The wireless communication method 1200 may further include: providing a message for a terminal context request to a mobility management entity, providing a message for triggering a terminal context transfer to a first base station, providing a handover request to the second base station, and providing a message for acknowledging the handover request to the mobility management entity.

[0078] Figure 13 This is a block diagram representation of a portion of a wireless station according to one or more embodiments to which the present technology may be applied. The wireless station 1305, such as a base station or wireless device (or UE), may include processor electronics 1310, such as a microprocessor implementing one or more wireless technologies proposed in this application. The wireless station 1305 may include transceiver electronics 1315 for transmitting and / or receiving wireless signals via one or more communication interfaces, such as antenna 1320. The wireless station 1305 may include other communication interfaces for transmitting and receiving data. The wireless station 1305 may include one or more memories (not explicitly shown) configured to store information such as data and / or instructions. In some embodiments, processor electronics 1310 may include at least a portion of transceiver electronics 1315. In some embodiments, at least some of the disclosed technologies, modules, or functions are implemented using the wireless station 1305.

[0079] Some embodiments described herein are described in the general context of methods or processes that may be implemented in one embodiment by a computer program product embodied in a computer-readable medium, including computer-executable instructions such as program code that are executed by a computer in a networked environment. The computer-readable medium may include removable and non-removable storage devices, including but not limited to read-only memory (ROM), random access memory (RAM), optical disc (CD), digital versatile optical disc (DVD), etc. Therefore, the computer-readable medium may include non-transitory storage media. Typically, program modules may include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. Computer or processor-executable instructions, associated data structures, and program modules represent examples of program code for performing steps of the methods disclosed herein. A particular sequence of such executable instructions or associated data structures represents examples of corresponding behaviors for implementing the functionality described in these steps or processes.

[0080] Some of the disclosed embodiments can be implemented using devices or modules that utilize hardware circuitry, software, or a combination thereof. For example, hardware circuitry implementations may include discrete analog and / or digital components, which may be integrated, for example, as part of a printed circuit board. Alternatively or additionally, the disclosed components or modules may be implemented as application-specific integrated circuits (ASICs) and / or field-programmable gate arrays (FPGAs). Some implementations additionally or alternatively include a digital signal processor (DSP), which is a dedicated microprocessor with an architecture optimized for the operational requirements of digital signal processing related to the functions disclosed herein. Similarly, the various components or sub-components within each module may be implemented in software, hardware, or firmware. Connections between modules and / or components within modules may be provided using any of the connection methods and media known in the art, including but not limited to communication via the Internet, wired, or wireless networks using appropriate protocols.

[0081] Although this application contains numerous details, these details should not be construed as limiting the scope of the claimed invention or the content that may be claimed, but rather as descriptions of specific features of particular embodiments. Certain features described herein in the context of individual embodiments may also be implemented in combination in a single embodiment. Conversely, various features described in the context of a single embodiment may also be implemented individually or in any suitable sub-combination in multiple embodiments. Furthermore, although the foregoing features may be described as operating in a particular combination, and even initially claimed as such, in certain circumstances one or more features of the claimed combination may be removed from the claimed combination, and the claimed combination may be for sub-combinations or variations thereof. Similarly, although operations are described in a specific order in the drawings, this should not be construed as requiring these operations to be performed in the specific order or sequence shown, or requiring all described operations to achieve the desired result.

[0082] This document describes only some implementation methods and examples. Other implementation methods, improvements and variations can be made based on the content described and illustrated in this disclosure.

Claims

1. A method for wireless communication, comprising: receiving, by a signaling node, resumption information from a first node having a suspended connection with a terminal; receiving, by the signaling node, a message for requesting context information of the terminal from a second node over a S 1 interface, the message including an identity of the terminal; determining, by the signaling node, the first node based on the identity of the terminal, and instructing the first node to provide the context information of the terminal directly to the second node over an X2 interface, wherein the providing of the context information of the terminal to the second node occurs before the second node obtains downlink data from a core network.

2. The method of claim 1, further comprising: receiving, by the signaling node, a context suspension request for the terminal, the context suspension request including at least one of: an identity identifying context information associated with the terminal; an identity of the first node; an identity of the terminal; security information for the first node to determine whether the second node is reliable; an early data transmission security context terminated by the mobile terminal. the message used by the signaling node to instruct the first node to provide the context information to the second node includes an identity of the second node.

3. The method of claim 1, wherein, the message used by the signaling node to instruct the first node to provide the context information to the second node includes an identity of the terminal.

4. The method of claim 1, wherein, the signaling node comprises a mobility management entity (MME), and each of the first node and the second node comprises an evolved Node B (eNB).

5. The method of claim 1, wherein, 6. An apparatus for wireless communication, comprising a memory and a processor, wherein the processor reads code from the memory and implements the method of any of claims 1-5.

7. A computer-readable process storage medium having code stored thereon, the code, when executed by a processor, causing the processor to implement the method of any of claims 1-5. ​

Images