Access method, device, equipment, readable storage medium and program product
By introducing the RRC_STANDBY state, the terminal maintains a lightweight connection with the control node and quickly switches to the RRC_CONNECTED state, which solves the problem of rapid cell handover, reduces signaling overhead and power consumption, and improves the continuity and stability of data transmission.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- CHINA MOBILE COMM LTD RES INST
- Filing Date
- 2024-10-29
- Publication Date
- 2026-05-01
AI Technical Summary
Existing technologies cannot meet the needs of rapid cell handover, resulting in increased signaling overhead and power consumption.
The RRC_STANDBY state is introduced, which allows the terminal to maintain a lightweight connection with the control node, save context information, and quickly switch to the RRC_CONNECTED state when the channel quality deteriorates, thereby reducing signaling interaction and energy consumption.
It enables fast handover, reduces handover latency, lowers terminal power consumption and signaling overhead, and improves the continuity and stability of data transmission.
Smart Images
Figure CN121968374A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of communication technology, and in particular to an access method, apparatus, device, readable storage medium, and program product. Background Technology
[0002] Existing technologies define three Radio Resource Control (RRC) states: RRC-IDLE, RRC-Inactive, and RRC-Connected. The RRC-Inactive state allows the terminal to enter a low-power mode without completely disconnecting, thereby reducing frequent RRC connection establishment and disconnection processes, and consequently lowering signaling overhead and power consumption. Therefore, when a terminal accesses a new network, the RRC-Inactive state allows for faster recovery compared to the RRC-IDLE state.
[0003] However, existing technologies still cannot meet the needs of rapid cell handover. Summary of the Invention
[0004] This application provides an access method, apparatus, device, readable storage medium, and program product to reduce handover latency.
[0005] In a first aspect, embodiments of this application provide an access method applied to a terminal, including:
[0006] Receive configuration information from the first node;
[0007] According to the configuration information, the state between the terminal and the first node is set to a first RRC state, and the state between the terminal and the second node is set to a second RRC state;
[0008] In the first RRC state, no air interface connection is established between the terminal and the first node, and in the second RRC state, the terminal is in the RRC connected state (RRC_CONNECTED).
[0009] Optionally, the first RRC state is the RRC preparation state (RRC_STANDBY).
[0010] Optionally, the method further includes:
[0011] The terminal receives first information from the first node, which is used for the terminal to access the first node.
[0012] Optionally, the method further includes:
[0013] If the first condition is met, the state between the terminal and the first node is switched to RRC_CONNECTED.
[0014] Optionally, switching the state between the terminal and the first node to RRC_CONNECTED includes:
[0015] If the first condition is met, a first request is sent to the first node, the first request being used to request access to the first node.
[0016] Optionally, the method further includes:
[0017] Upon receiving a first response from the first node, the state between the terminal and the first node is switched to RRC_CONNECTED, whereby the first response indicates that the connection between the first node and the terminal has been successfully established.
[0018] Optionally, the first condition includes:
[0019] The channel quality between the terminal and the second node does not meet the preset requirements.
[0020] Secondly, embodiments of this application provide an access method applied to a first node, comprising:
[0021] Send configuration information to the terminal to set the state between the terminal and the first node to a first RRC state, and to set the state between the terminal and the second node to a second RRC state;
[0022] In the first RRC state, no air interface connection is established between the terminal and the first node, and the second RRC state is RRC_CONNECTED.
[0023] Optionally, the method further includes:
[0024] Receive the context of the terminal sent by the second node.
[0025] Optionally, the method further includes:
[0026] Send first information to the terminal, the first information being used for the terminal to access the first node.
[0027] Optionally, the method further includes:
[0028] Switch the state between the first node and the terminal to RRC_CONNECTED.
[0029] Optionally, switching the state between the first node and the terminal to RRC_CONNECTED includes:
[0030] The terminal receives a first request sent to the first node under a first condition, the first request being used to request access to the first node;
[0031] A second request is sent to the second node, the second request being used to request the release of the connection between the terminal and the second node.
[0032] Optionally, the method further includes:
[0033] A first response is sent to the terminal, the first response indicating that the connection between the first node and the terminal has been successfully established.
[0034] Optionally, the first condition includes:
[0035] The channel quality between the terminal and the second node does not meet the preset requirements.
[0036] Optionally, while maintaining the first RRC state with the terminal, the first node maintains a connection with the core network.
[0037] Thirdly, embodiments of this application provide an access method applied to a second node, including:
[0038] The state between the terminal and the first node is set to the second RRC state, wherein the state between the terminal and the first node is the first RRC state; in the first RRC state, no air interface connection is established between the terminal and the first node, and the second RRC state is RRC_CONNECTED.
[0039] Optionally, the method further includes:
[0040] Send the context of the terminal to the first node.
[0041] Optionally, the method further includes:
[0042] The terminal receives a second request sent by the first node, the second request being used to request the release of the connection between the terminal and the second node.
[0043] Fourthly, embodiments of this application provide an access device applied to a terminal, comprising:
[0044] The first receiving module is used to receive the configuration information of the first node;
[0045] The first setting module is configured to set the state between the terminal and the first node to a first RRC state, and to set the state between the terminal and the second node to a second RRC state, according to the configuration information.
[0046] In the first RRC state, no air interface connection is established between the terminal and the first node, and in the second RRC state, the RRC connection state is RRC_CONNECTED.
[0047] Optionally, the first RRC state is the RRC preparation state RRC_STANDBY.
[0048] Optionally, the device further includes:
[0049] The second receiving module is used to receive first information from the first node, the first information being used by the terminal to access the first node.
[0050] Optionally, the device further includes:
[0051] The first processing module is configured to switch the state between the terminal and the first node to RRC_CONNECTED when a first condition is met.
[0052] Optionally, the first processing module is used for:
[0053] If the first condition is met, a first request is sent to the first node to switch the state between the terminal and the first node to RRC_CONNECTED. The first request is used to request access to the first node.
[0054] Optionally, the device may further include:
[0055] The second receiving module is used to receive the first response from the first node, the first response indicating that the connection between the first node and the terminal has been successfully established.
[0056] Optionally, the first condition includes:
[0057] The channel quality between the terminal and the second node does not meet the preset requirements.
[0058] Fifthly, embodiments of this application provide an access device applied to a first node, comprising:
[0059] The first sending module is used to send configuration information to the terminal, and to set the state between the terminal and the first node to a first RRC state, and to set the state between the terminal and the second node to a second RRC state.
[0060] In the first RRC state, no air interface connection is established between the terminal and the first node, and the second RRC state is RRC_CONNECTED.
[0061] Optionally, the device further includes:
[0062] The first receiving module is used to receive the context of the terminal sent by the second node.
[0063] Optionally, the device further includes:
[0064] The second sending module is used to send first information to the terminal, the first information being used for the terminal to access the first node.
[0065] Optionally, the device further includes:
[0066] The first processing module is used to switch the state between the first node and the terminal to RRC_CONNECTED.
[0067] Optionally, the first processing module is further configured to:
[0068] The terminal receives a first request sent to the first node under a first condition, the first request being used to request access to the first node;
[0069] A second request is sent to the second node, the second request being used to request the release of the connection between the terminal and the second node.
[0070] Optionally, the device further includes:
[0071] The third sending module is used to send a first response to the terminal, the first response being used to indicate that the connection between the first node and the terminal has been successfully established.
[0072] Optionally, the first condition includes:
[0073] The channel quality between the terminal and the second node does not meet the preset requirements.
[0074] Optionally, while maintaining the first RRC state with the terminal, the first node maintains a connection with the core network.
[0075] Sixthly, embodiments of this application provide an access device applied to a second node, comprising:
[0076] The first setting module is used to set the state between the terminal and the first node to a second RRC state, wherein the state between the terminal and the first node is a first RRC state; in the first RRC state, no air interface connection is established between the terminal and the first node, and the second RRC state is RRC_CONNECTED.
[0077] Optionally, the device may further include:
[0078] The first sending module is used to send the context of the terminal to the first node.
[0079] Optionally, the device may further include:
[0080] The first receiving module is used to receive a second request sent by the first node, the second request being used to request the release of the connection between the terminal and the second node.
[0081] In a seventh aspect, embodiments of this application provide an access device applied to a terminal, comprising: a processor and a transceiver;
[0082] The transceiver is used to receive configuration information from the first node;
[0083] The processor is configured to set the state between the terminal and the first node to a first RRC state, and to set the state between the terminal and the second node to a second RRC state, according to the configuration information.
[0084] In the first RRC state, no air interface connection is established between the terminal and the first node, and in the second RRC state, the RRC connection state is RRC_CONNECTED.
[0085] Optionally, the first RRC state is the RRC preparation state RRC_STANDBY.
[0086] Optionally, the transceiver is further configured to receive first information from the first node, the first information being used by the terminal to access the first node.
[0087] Optionally, the processor is further configured to switch the state between the terminal and the first node to RRC_CONNECTED if a first condition is met.
[0088] Optionally, the processor is further configured to, when the first condition is met, send a first request to the first node to switch the state between the terminal and the first node to RRC_CONNECTED, wherein the first request is used to request access to the first node.
[0089] Optionally, the transceiver is further configured to receive a first response from the first node, the first response indicating that a connection between the first node and the terminal has been successfully established.
[0090] Optionally, the first condition includes:
[0091] The channel quality between the terminal and the second node does not meet the preset requirements.
[0092] Eighthly, embodiments of this application provide an access device applied to a first node, comprising: a processor and a transceiver;
[0093] The transceiver is used to send configuration information to the terminal, to set the state between the terminal and the first node to a first RRC state, and to set the state between the terminal and the second node to a second RRC state.
[0094] In the first RRC state, no air interface connection is established between the terminal and the first node, and the second RRC state is RRC_CONNECTED.
[0095] Optionally, the transceiver is further configured to receive the context of the terminal sent by the second node.
[0096] Optionally, the transceiver is further configured to send first information to the terminal, the first information being used for the terminal to access the first node.
[0097] Optionally, the processor is further configured to switch the state between the first node and the terminal to RRC_CONNECTED.
[0098] Optionally, the processor is further configured to:
[0099] The terminal receives a first request sent to the first node under a first condition, the first request being used to request access to the first node;
[0100] A second request is sent to the second node, the second request being used to request the release of the connection between the terminal and the second node.
[0101] Optionally, the transceiver is further configured to send a first response to the terminal, the first response indicating that the connection between the first node and the terminal has been successfully established.
[0102] Optionally, the first condition includes:
[0103] The channel quality between the terminal and the second node does not meet the preset requirements.
[0104] Optionally, while maintaining the first RRC state with the terminal, the first node maintains a connection with the core network.
[0105] Ninthly, embodiments of this application provide an access device applied to a second node, comprising: a processor and a transceiver;
[0106] The processor is configured to set the state between the terminal and the first node to a second RRC state, wherein the state between the terminal and the first node is a first RRC state; in the first RRC state, no air interface connection is established between the terminal and the first node, and the second RRC state is RRC_CONNECTED.
[0107] Optionally, the transceiver is also configured to send the context of the terminal to the first node.
[0108] Optionally, the transceiver is further configured to receive a second request sent by the first node, the second request being used to request the release of the connection between the terminal and the second node.
[0109] In a tenth aspect, embodiments of this application also provide a communication device, including: a memory, a processor, and a program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps in the access method described above.
[0110] Eleventhly, embodiments of this application also provide a readable storage medium storing a program, which, when executed by a processor, implements the steps in the access method described above.
[0111] In a twelfth aspect, embodiments of this application also provide a computer program product, including computer instructions that, when executed by a processor, implement the steps in the access method described above.
[0112] In this embodiment, the terminal sets the state between itself and the first node to a first RRC state based on the configuration information of the first node, and sets the state between itself and the second node to a second RRC state. In the first RRC state, no air interface connection is established between the terminal and the first node, and in the second RRC state, it is in an RRC connected state (RRC_CONNECTED). Because no air interface connection is established between the terminal and the first node, but an RRC connected state is established with the second node, a quick handover to the first node is possible without signaling interaction, thereby reducing handover latency. Attached Figure Description
[0113] Figure 1 This is one of the flowcharts of the access method provided in the embodiments of this application;
[0114] Figure 2 This is a schematic diagram of the state between the terminal and the first and second nodes in an embodiment of this application;
[0115] Figure 3 This is the second flowchart of the access method provided in the embodiments of this application;
[0116] Figure 4 This is the third flowchart of the access method provided in the embodiments of this application;
[0117] Figure 5 This is the fourth flowchart of the access method provided in the embodiments of this application;
[0118] Figure 6 This is one of the structural diagrams of the access device provided in the embodiments of this application;
[0119] Figure 7 This is the second structural diagram of the access device provided in the embodiments of this application;
[0120] Figure 8 This is the third structural diagram of the access device provided in the embodiments of this application;
[0121] Figure 9 This is the fourth structural diagram of the access device provided in the embodiments of this application;
[0122] Figure 10 This is the fifth structural diagram of the access device provided in the embodiments of this application;
[0123] Figure 11 This is the sixth structural diagram of the access device provided in the embodiments of this application. Detailed Implementation
[0124] In the embodiments of this application, the term "and / or" describes the relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following associated objects have an "or" relationship.
[0125] In the embodiments of this application, the term "multiple" refers to two or more, and other quantifiers are similar.
[0126] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.
[0127] See Figure 1 , Figure 1 This is a flowchart of the access method provided in the embodiments of this application, applied to a terminal, such as... Figure 1 As shown, it includes the following steps:
[0128] Step 101: Receive the configuration information of the first node.
[0129] The configuration information may include status settings between the terminal and the first node, and status settings between the terminal and the second node. The first node may also be called a control node, and the second node may also be called a service node. In this embodiment, a scheme of separating the control node and the service node is adopted. The control node provides low-frequency signals to provide signaling connections for the terminal, ensuring wide coverage of the signaling plane; the service node provides data transmission for the terminal, and its frequency is generally high-frequency, which can provide high-speed data transmission for the terminal.
[0130] Step 102: Based on the configuration information, set the state between the terminal and the first node to a first RRC state, and set the state between the terminal and the second node to a second RRC state.
[0131] In the first RRC state, no air interface connection is established between the terminal and the first node, and in the second RRC state, the RRC connection state is RRC_CONNECTED.
[0132] When the terminal maintains a connection with the second node, high-speed data transmission is required, necessitating rapid handover. To mitigate the impact of handover on the terminal experience, this application proposes a new RRC state, namely the RRC_STANDBY state. The first RRC state is RRC_STANDBY. For example... Figure 2 The diagram shown is a state diagram between the terminal and the first and second nodes in an embodiment of this application.
[0133] The RRC_STANDBY has the following characteristics:
[0134] 1. Lightweight Connection: The RRC_STANDBY state provides a lightweight connection between the terminal and the first node. This connection allows for a rapid transition from the RRC_STANDBY state to the RRC_CONNECTED state when the channel quality between the terminal and the second node deteriorates, enabling the first node to provide services to the terminal and reducing terminal handover latency.
[0135] 2. First Node Connection: In the RRC_STANDBY state, the first node maintains a connection with the core network to receive and forward messages from the core network in a timely manner; it maintains a disconnected air interface link with the terminal, reducing terminal measurement overhead and power consumption. Simultaneously, the first node also saves the terminal's context information to quickly restore the terminal's connection state when needed, reducing the signaling overhead and latency required to restore the connection.
[0136] 3. Connection between the terminal and the second node: The terminal and the second node maintain the RRC_CONNECTED state, which enables the terminal to continue receiving data services from the second node and maintain the continuity and stability of communication.
[0137] 4. Reduced monitoring requirements: Unlike the RRC_INACTIVE (RRC inactive state) state, the terminal in the RRC_STANDBY state does not need to monitor the call channel and broadcast channel. This is because the terminal and the second node are in a connected state, so the terminal will directly receive the paging and broadcast messages sent by the second node.
[0138] 5. First Node and Second Node: The first node and the second node will transmit the updated UE context. The first node stores the most recent UE context, which facilitates the terminal to quickly access the first node.
[0139] Accordingly, if the first condition is met, the state between the terminal and the first node is switched to RRC_CONNECTED. The first condition includes: the channel quality between the terminal and the second node does not meet a preset requirement, which may vary depending on the specific representation of channel quality. For example, if the Reference Signal Receiving Power (RSRP) between the terminal and the second node is less than a certain preset value, then the channel quality between the terminal and the second node can be considered to not meet the preset requirement.
[0140] In practical applications, high-speed data services can be transmitted while the terminal remains active with the second node. However, due to factors such as terminal movement and changes in the network environment, the communication quality between the terminal and the second node may deteriorate. In such cases, a rapid switch to the first node is necessary to ensure the continuity and stability of data transmission. Based on the above settings, when a switch is required, the terminal can quickly switch to the first node, thereby reducing switchover latency. Simultaneously, since the terminal only maintains a connection with the second node and no air interface connection is established with the first node, terminal power consumption is saved, the connection management process in the network is simplified, terminal measurement overhead is reduced, and inter-frequency measurement is unnecessary, avoiding resource consumption caused by inter-frequency measurement, thus reducing power consumption, extending battery life, and improving overall performance. Because the terminal can directly and efficiently switch to the control node without inter-frequency measurement, resource consumption caused by inter-frequency measurement is avoided, and the high-frequency coverage is discontinuous, avoiding idle measurement by the terminal and saving terminal power consumption.
[0141] During the aforementioned state transition process, if the first condition is met, the terminal sends a first request to the first node to switch the state between the terminal and the first node to RRC_CONNECTED. This first request is used to request access to the first node. Subsequently, the first node may send a second request to the second node to request the release of the connection between the terminal and the second node, thereby switching the state between the terminal and the first node to RRC_CONNECTED. Optionally, the terminal may also receive a first response from the first node, indicating that the connection between the first node and the terminal has been successfully established.
[0142] The first request may be, for example, an RRC connection recovery request, and the first response may be, for example, an RRC connection recovery request complete message.
[0143] In this embodiment, the terminal sets the state between itself and the first node to a first RRC state based on the configuration information of the first node, and sets the state between itself and the second node to a second RRC state. In the first RRC state, no air interface connection is established between the terminal and the first node, and in the second RRC state, it is in an RRC connected state (RRC_CONNECTED). Because no air interface connection is established between the terminal and the first node, but an RRC connected state is established with the second node, a quick handover to the first node is possible without signaling interaction, thereby reducing handover latency.
[0144] Based on the above embodiments, the terminal may also receive first information from the first node, which is used for the terminal to access the first node. This first information may include a preamble, security algorithms, etc. By pre-configuring this information, the terminal can quickly switch to the first node without a signaling interaction process.
[0145] Among them, the first node and the second node mentioned above can be base stations, etc.
[0146] See Figure 3 , Figure 3 This is a flowchart of the access method provided in the embodiments of this application, applied to the first node, such as... Figure 3 As shown, it includes the following steps:
[0147] Step 301: Send configuration information to the terminal to set the state between the terminal and the first node to a first RRC state, and to set the state between the terminal and the second node to a second RRC state; wherein, in the first RRC state, no air interface connection is established between the terminal and the first node, and the second RRC state is RRC_CONNECTED.
[0148] The explanation of the first RRC state can be found in the description of the foregoing method embodiments. While maintaining the first RRC state with the terminal, the first node maintains a connection with the core network to receive and forward messages from the core network in a timely manner.
[0149] In this embodiment, the terminal sets the state between itself and the first node to a first RRC state based on the configuration information of the first node, and sets the state between itself and the second node to a second RRC state. In the first RRC state, no air interface connection is established between the terminal and the first node, and in the second RRC state, it is in an RRC connected state (RRC_CONNECTED). Because no air interface connection is established between the terminal and the first node, but an RRC connected state is established with the second node, a quick handover to the first node is possible without signaling interaction, thereby reducing handover latency.
[0150] Optionally, based on the above embodiments, the first node may receive the context of the terminal sent by the second node, so that the terminal can quickly access the first node.
[0151] Optionally, based on the above embodiments, the first node may send first information to the terminal, the first information being used for the terminal to access the first node. This first information may include a preamble, security algorithms, etc. By pre-configuring this information, the terminal can quickly switch to the first node without a signaling interaction process.
[0152] Optionally, based on the above embodiments, the first node can switch the state between the first node and the terminal to RRC_CONNECTED. Specifically, the first node receives a first request sent by the terminal to the first node when a first condition is met, the first request being used to request access to the first node. Then, the first node sends a second request to the second node, the second request being used to request the release of the connection between the terminal and the second node. Further, the first node can also send a first response to the terminal, the first response being used to indicate that the connection between the first node and the terminal has been successfully established. For an explanation of the first condition, please refer to the description of the foregoing method embodiments.
[0153] See Figure 4 , Figure 4 This is a flowchart of the access method provided in the embodiments of this application, applied to the second node, such as... Figure 4 As shown, it includes the following steps:
[0154] Step 401: Set the state between the terminal and the first node to the second RRC state, wherein the state between the terminal and the first node is the first RRC state; in the first RRC state, no air interface connection is established between the terminal and the first node, and the second RRC state is RRC_CONNECTED.
[0155] The explanation of the first RRC state can be found in the description of the foregoing method embodiments. Since the terminal and the second node maintain the RRC_CONNECTED state, this allows the terminal to continue receiving data services from the second node and maintains the continuity and stability of communication.
[0156] Optionally, the second node may also send the terminal's context to the first node so that the terminal can quickly switch to the first node.
[0157] Optionally, the second node may also receive a second request sent by the first node, the second request being used to request the release of the connection between the terminal and the second node. This second request may, for example, be an RRC connection release.
[0158] In this embodiment, the terminal sets the state between itself and the first node to a first RRC state based on the configuration information of the first node, and sets the state between itself and the second node to a second RRC state. In the first RRC state, no air interface connection is established between the terminal and the first node, and in the second RRC state, it is in an RRC connected state (RRC_CONNECTED). Because no air interface connection is established between the terminal and the first node, but an RRC connected state is established with the second node, a quick handover to the first node is possible without signaling interaction, thereby reducing handover latency.
[0159] See Figure 5 , Figure 5 This is a flowchart of the access method provided in an embodiment of this application. The first node is a control node, and the second node is a service node. Figure 5 As shown, this embodiment may include:
[0160] The terminal maintains the RRC_standby state with the control node and the RRC_CONNECTED state with the service node. Data is transmitted between the terminal and the service node, and the control node saves the terminal's context.
[0161] Step 501: When the terminal's context changes, the service node will synchronize the terminal's context content through UE context synchronization. For example, when the terminal initiates or receives data services, the network's Bearer resources may be dynamically adjusted according to Quality of Service (QoS) requirements. This involves the creation, modification, or release of Bearers, thereby affecting the Bearer list in the terminal's context.
[0162] Step 502: The control node completes the reception by replying with the UE context synchronization response.
[0163] Step 503: The control node pre-configures the preamble code, security algorithm, etc. for the terminal via the RRCReconfiguration message. The control node can reserve n (n≥1) preamble codes for the service node, and the terminal selects one preamble for random access.
[0164] Step 504: When the terminal measures poor channel quality at a service node, the terminal sends an RRC connection recovery request to the control node, carrying the terminal identifier. Upon receiving the recovery request, the control node verifies the terminal's identifier and confirms the access request. The control node stores the terminal's context information, enabling rapid access.
[0165] Step 505: The control node requests to release the connection between the terminal and the service node through RRC connection release, and the service node stops providing services to the terminal.
[0166] Step 506: The control node completes the terminal's access via the RRC connection recovery request complete message. The terminal and control node change from the RRC_standby state to the RRC_CONNECTED state, establishing a Signalalling Radio Bearer (SRB) and a Data Radio Bearer (DRB). The control node will then provide services to the terminal, enabling it to receive and send data packets.
[0167] In the above embodiments, the terminal can directly and efficiently switch to the control node without performing inter-frequency measurement, avoiding the resource consumption caused by inter-frequency measurement. Furthermore, the high-frequency coverage is discontinuous, preventing empty measurements by the terminal and reducing its power consumption. The service node and control node transmit updated terminal context information, and the control node stores the latest terminal context content. When the channel quality of the service node deteriorates, the terminal can quickly access the control node, reducing the terminal access time. Simultaneously, the pre-synchronization of the UE context content and the pre-configuration of control node signaling also ensure rapid terminal handover.
[0168] See Figure 6 , Figure 6 This is a structural diagram of the access device provided in the embodiments of this application, applied to a terminal. For example... Figure 6 As shown, the access device includes:
[0169] The first receiving module 601 is used to receive configuration information of the first node; the first setting module 602 is used to set the state between the terminal and the first node to a first RRC state and, according to the configuration information, set the state between the terminal and the second node to a second RRC state.
[0170] In the first RRC state, no air interface connection is established between the terminal and the first node, and in the second RRC state, the RRC connection state is RRC_CONNECTED.
[0171] Optionally, the first RRC state is the RRC preparation state RRC_STANDBY.
[0172] Optionally, the device further includes:
[0173] The second receiving module is used to receive first information from the first node, the first information being used by the terminal to access the first node.
[0174] Optionally, the device further includes:
[0175] The first processing module is configured to switch the state between the terminal and the first node to RRC_CONNECTED when a first condition is met.
[0176] Optionally, the first processing module is used for:
[0177] If the first condition is met, a first request is sent to the first node to switch the state between the terminal and the first node to RRC_CONNECTED. The first request is used to request access to the first node.
[0178] Optionally, the device may further include:
[0179] The second receiving module is used to receive the first response from the first node, the first response indicating that the connection between the first node and the terminal has been successfully established.
[0180] Optionally, the first condition includes:
[0181] The channel quality between the terminal and the second node does not meet the preset requirements.
[0182] The apparatus provided in this application embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.
[0183] See Figure 7 , Figure 7 This is a structural diagram of the access device provided in an embodiment of this application, applied to the first node. For example... Figure 7 As shown, the access device includes:
[0184] The first sending module 701 is used to send configuration information to the terminal, and to set the state between the terminal and the first node to a first RRC state, and to set the state between the terminal and the second node to a second RRC state.
[0185] In the first RRC state, no air interface connection is established between the terminal and the first node, and the second RRC state is RRC_CONNECTED.
[0186] Optionally, the device further includes:
[0187] The first receiving module is used to receive the context of the terminal sent by the second node.
[0188] Optionally, the device further includes:
[0189] The second sending module is used to send first information to the terminal, the first information being used for the terminal to access the first node.
[0190] Optionally, the device further includes:
[0191] The first processing module is used to switch the state between the first node and the terminal to RRC_CONNECTED.
[0192] Optionally, the first processing module is further configured to:
[0193] The terminal receives a first request sent to the first node under a first condition, the first request being used to request access to the first node;
[0194] A second request is sent to the second node, the second request being used to request the release of the connection between the terminal and the second node.
[0195] Optionally, the device further includes:
[0196] The third sending module is used to send a first response to the terminal, the first response being used to indicate that the connection between the first node and the terminal has been successfully established.
[0197] Optionally, the first condition includes:
[0198] The channel quality between the terminal and the second node does not meet the preset requirements.
[0199] Optionally, while maintaining the first RRC state with the terminal, the first node maintains a connection with the core network.
[0200] The apparatus provided in this application embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.
[0201] See Figure 8 , Figure 8This is a structural diagram of the access device provided in an embodiment of this application, applied to the second node. For example... Figure 8 As shown, the access device includes:
[0202] The first setting module 801 is used to set the state between the terminal and the first node to a second RRC state, wherein the state between the terminal and the first node is a first RRC state; in the first RRC state, no air interface connection is established between the terminal and the first node, and the second RRC state is RRC_CONNECTED.
[0203] Optionally, the device may further include:
[0204] The first sending module is used to send the context of the terminal to the first node.
[0205] Optionally, the device may further include:
[0206] The first receiving module is used to receive a second request sent by the first node, the second request being used to request the release of the connection between the terminal and the second node.
[0207] The apparatus provided in this application embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.
[0208] See Figure 9 , Figure 9 This is a structural diagram of the access device provided in the embodiments of this application, applied to a terminal. For example... Figure 9 As shown, the access device includes: a processor 901 and a transceiver 902;
[0209] The transceiver 902 is used to receive configuration information from the first node;
[0210] The processor 901 is configured to set the state between the terminal and the first node to a first RRC state, and to set the state between the terminal and the second node to a second RRC state, according to the configuration information.
[0211] In the first RRC state, no air interface connection is established between the terminal and the first node, and in the second RRC state, the RRC connection state is RRC_CONNECTED.
[0212] Optionally, the first RRC state is the RRC preparation state RRC_STANDBY.
[0213] Optionally, the transceiver 902 is further configured to receive first information from the first node, the first information being used by the terminal to access the first node.
[0214] Optionally, the processor 901 is further configured to, when a first condition is met, switch the state between the terminal and the first node to RRC_CONNECTED.
[0215] Optionally, the processor 901 is further configured to, when the first condition is met, send a first request to the first node to switch the state between the terminal and the first node to RRC_CONNECTED, wherein the first request is used to request access to the first node.
[0216] Optionally, the transceiver 902 is further configured to receive a first response from the first node, the first response indicating that a connection between the first node and the terminal has been successfully established.
[0217] Optionally, the first condition includes:
[0218] The channel quality between the terminal and the second node does not meet the preset requirements.
[0219] The apparatus provided in this application embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.
[0220] See Figure 10 , Figure 10 This is a structural diagram of the access device provided in an embodiment of this application, applied to the first node. For example... Figure 10 As shown, the access device includes: a processor 1001 and a transceiver 1002;
[0221] The transceiver 1002 is used to send configuration information to the terminal, and to set the state between the terminal and the first node to a first RRC state, and to set the state between the terminal and the second node to a second RRC state.
[0222] In the first RRC state, no air interface connection is established between the terminal and the first node, and the second RRC state is RRC_CONNECTED.
[0223] Optionally, the transceiver is further configured to receive the context of the terminal sent by the second node.
[0224] Optionally, the transceiver is further configured to send first information to the terminal, the first information being used for the terminal to access the first node.
[0225] Optionally, the processor 1001 is further configured to switch the state between the first node and the terminal to RRC_CONNECTED.
[0226] Optionally, the processor 1001 is further configured to:
[0227] The terminal receives a first request sent to the first node under a first condition, the first request being used to request access to the first node;
[0228] A second request is sent to the second node, the second request being used to request the release of the connection between the terminal and the second node.
[0229] Optionally, the transceiver 1002 is further configured to send a first response to the terminal, the first response indicating that the connection between the first node and the terminal has been successfully established.
[0230] Optionally, the first condition includes:
[0231] The channel quality between the terminal and the second node does not meet the preset requirements.
[0232] Optionally, while maintaining the first RRC state with the terminal, the first node maintains a connection with the core network.
[0233] The apparatus provided in this application embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.
[0234] See Figure 11 , Figure 11 This is a structural diagram of the access device provided in an embodiment of this application, applied to the second node. For example... Figure 11 As shown, the access device includes: a processor 1101 and a transceiver 1102;
[0235] The processor 1101 is configured to set the state between the terminal and the first node to a second RRC state, wherein the state between the terminal and the first node is a first RRC state; in the first RRC state, no air interface connection is established between the terminal and the first node, and the second RRC state is RRC_CONNECTED.
[0236] Optionally, the transceiver 1102 is further configured to send the context of the terminal to the first node.
[0237] Optionally, the transceiver 1102 is further configured to receive a second request sent by the first node, the second request being used to request the release of the connection between the terminal and the second node.
[0238] The apparatus provided in this application embodiment can execute the above method embodiment, and its implementation principle and technical effect are similar, so it will not be described again here.
[0239] It should be noted that the division of units in the embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated units described above can be implemented in hardware or as software functional units.
[0240] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0241] This application provides a communication device, including: a memory, a processor, and a program stored in the memory and executable on the processor; the processor is used to read the program in the memory to implement the steps in the access method as described above.
[0242] This application also provides a readable storage medium storing a program. When executed by a processor, this program implements the various processes of the above-described access method embodiments and achieves the same technical effects. To avoid repetition, it will not be described again here. The readable storage medium can be any available medium or data storage device that the processor can access, including but not limited to magnetic storage (e.g., floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (e.g., CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (e.g., ROMs, EPROMs, EEPROMs, non-volatile memory (NAND flash), solid-state drives (SSDs)).
[0243] This application also provides a computer program product, including computer instructions. When these computer instructions are executed by a processor, they implement the various processes of the above-described access method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.
[0244] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.
[0245] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.
[0246] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.
Claims
1. An access method, characterized in that, Applied to terminals, including: Receive configuration information from the first node; According to the configuration information, the state between the terminal and the first node is set to a first Radio Resource Control (RRC) state, and the state between the terminal and the second node is set to a second RRC state. In the first RRC state, no air interface connection is established between the terminal and the first node, and in the second RRC state, the RRC connection state is RRC_CONNECTED.
2. The method according to claim 1, characterized in that, The first RRC state is the RRC preparation state RRC_STANDBY.
3. The method according to claim 1, characterized in that, The method further includes: The terminal receives first information from the first node, which is used for the terminal to access the first node.
4. The method according to any one of claims 1-3, characterized in that, The method further includes: If the first condition is met, the state between the terminal and the first node is switched to RRC_CONNECTED.
5. The method according to claim 4, characterized in that, Switching the state between the terminal and the first node to RRC_CONNECTED includes: If the first condition is met, a first request is sent to the first node to switch the state between the terminal and the first node to RRC_CONNECTED. The first request is used to request access to the first node.
6. The method according to claim 5, characterized in that, The method further includes: The system receives a first response from the first node, which indicates that a connection between the first node and the terminal has been successfully established.
7. The method according to claim 4, characterized in that, The first condition includes: The channel quality between the terminal and the second node does not meet the preset requirements.
8. An access method, characterized in that, Applied to the first node, including: Send configuration information to the terminal to set the state between the terminal and the first node to a first RRC state, and to set the state between the terminal and the second node to a second RRC state; In the first RRC state, no air interface connection is established between the terminal and the first node, and the second RRC state is RRC_CONNECTED.
9. The method according to claim 8, characterized in that, The method further includes: Receive the context of the terminal sent by the second node.
10. The method according to claim 8, characterized in that, The method further includes: Send first information to the terminal, the first information being used for the terminal to access the first node.
11. The method according to any one of claims 8-10, characterized in that, The method further includes: Switch the state between the first node and the terminal to RRC_CONNECTED.
12. The method according to claim 11, characterized in that, The step of switching the state between the first node and the terminal to RRC_CONNECTED includes: The terminal receives a first request sent to the first node under a first condition, the first request being used to request access to the first node; A second request is sent to the second node, the second request being used to request the release of the connection between the terminal and the second node.
13. The method according to claim 12, characterized in that, The method further includes: A first response is sent to the terminal, the first response indicating that the connection between the first node and the terminal has been successfully established.
14. The method according to claim 12, characterized in that, The first condition includes: The channel quality between the terminal and the second node does not meet the preset requirements.
15. The method according to any one of claims 8-10, characterized in that, While maintaining the first RRC state with the terminal, the first node maintains a connection with the core network.
16. An access method, characterized in that, Applied to the second node, including: The state between the terminal and the first node is set to the second RRC state, wherein the state between the terminal and the first node is the first RRC state; in the first RRC state, no air interface connection is established between the terminal and the first node, and the second RRC state is RRC_CONNECTED.
17. The method according to claim 16, characterized in that, The method further includes: Send the context of the terminal to the first node.
18. The method according to claim 16, characterized in that, The method further includes: The terminal receives a second request sent by the first node, the second request being used to request the release of the connection between the terminal and the second node.
19. An access device, characterized in that, Applied to terminals, including: The first receiving module is used to receive the configuration information of the first node; The first setting module is configured to set the state between the terminal and the first node to a first RRC state, and to set the state between the terminal and the second node to a second RRC state, according to the configuration information. In the first RRC state, no air interface connection is established between the terminal and the first node, and in the second RRC state, the RRC connection state is RRC_CONNECTED.
20. An access device, characterized in that, Applied to the first node, including: The first sending module is used to send configuration information to the terminal, and to set the state between the terminal and the first node to a first RRC state, and to set the state between the terminal and the second node to a second RRC state. In the first RRC state, no air interface connection is established between the terminal and the first node, and the second RRC state is RRC_CONNECTED.
21. An access device, characterized in that, Applied to the second node, including: The first setting module is used to set the state between the terminal and the first node to a second RRC state, wherein the state between the terminal and the first node is a first RRC state; in the first RRC state, no air interface connection is established between the terminal and the first node, and the second RRC state is RRC_CONNECTED.
22. An access device, characterized in that, Applied to terminals, including: processors and transceivers; The transceiver is used to receive configuration information from the first node; The processor is configured to set the state between the terminal and the first node to a first RRC state, and to set the state between the terminal and the second node to a second RRC state, according to the configuration information. In the first RRC state, no air interface connection is established between the terminal and the first node, and in the second RRC state, the RRC connection state is RRC_CONNECTED.
23. An access device, characterized in that, Applied to the first node, including: processor and transceiver; The transceiver is used to send configuration information to the terminal, to set the state between the terminal and the first node to a first RRC state, and to set the state between the terminal and the second node to a second RRC state. In the first RRC state, no air interface connection is established between the terminal and the first node, and the second RRC state is RRC_CONNECTED.
24. An access device, characterized in that, Applied to the second node, it includes: a processor and a transceiver; The processor is configured to set the state between the terminal and the first node to a second RRC state, wherein the state between the terminal and the first node is a first RRC state; in the first RRC state, no air interface connection is established between the terminal and the first node, and the second RRC state is RRC_CONNECTED.
25. A communication device, comprising: A memory, a processor, and a program stored in the memory and executable on the processor; characterized in that the processor is configured to read the program from the memory to implement the steps of the access method as described in any one of claims 1 to 17.
26. A computer-readable storage medium for storing a program, characterized in that, When the program is executed by the processor, it implements the steps of the access method as described in any one of claims 1 to 17.
27. A computer program product, characterized in that, It includes computer instructions that, when executed by a processor, implement the steps in the access method as described in any one of claims 1 to 17.