A connection establishment method, network element, storage medium and system

By grouping IoT devices and pre-establishing or pre-recovering of RRC connections within the terminal group, the high control plane signaling overhead caused by massive connections of IoT devices is solved, and the system transmission efficiency is improved.

CN109548170BActive Publication Date: 2024-11-05ZTE CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN201710607456.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2017-07-24
Publication Date
2024-11-05
Estimated Expiration
2037-07-24

AI Technical Summary

Technical Problem

In the prior art, the massive connection of IoT devices leads to high overhead cost for control plane signaling and affects system transmission efficiency.

Method used

By grouping user terminals, when any user terminal in the terminal group initiates a connection request, the RRC connection is pre-established or pre-recovered to other terminals in the group, reducing the control plane signaling overhead during subsequent connection establishment.

Benefits of technology

It realizes rapid establishment or recovery of RRC connections, effectively reducing the overhead cost of control plane signaling and improving system transmission efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN109548170B_ABST
    Figure CN109548170B_ABST
Patent Text Reader

Abstract

The present invention discloses a connection establishment method, network element, storage medium and system, the method comprising: upon receiving a connection request initiated by a user terminal B, the access network element determines the terminal group to which the user terminal B belongs; the access network element determines a user terminal that can be pre-processed for connection in the terminal group; the access network element performs connection pre-processing on the determined user terminal. The technical solution of the present invention can quickly establish or restore an RRC connection and effectively reduce the overhead cost of control plane signaling.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to a connection establishment method, a storage medium, a network element and a system. Background Art

[0002] With the development of the Internet of Things, the number of user terminals continues to increase, which has become the background of the industry. The load problem of massive connections on network access and system efficiency have become one of the current research focuses.

[0003] Low cost, small bandwidth, and small data are typical characteristics of IoT devices. The duration of network access of such devices is short, and the amount of data transmitted is small, but the number of devices is very large. Each time a device establishes a connection with a wireless communication network, a large amount of control plane signaling of the air interface and the control plane signaling overhead on the ground side will be generated. The control plane signaling consumed in the context establishment process on the RAN side is the main one. However, compared with the amount of data transmitted by the device, there is a situation where the control plane signaling overhead is greater than the user plane data volume, which leads to low system transmission efficiency. At present, 3GPP is studying the enhancement of MTC (Machine-type communication), Narrow Band Internet of Things (NBIOT), and 5G new network (5G new Radio Access Technology). How to reduce the control plane signaling overhead cost caused by massive access is one of the important research directions.

[0004] In the LTE standard and 5G new RAT standard currently discussed by 3GPP, the light connected state is introduced in LTE, and the inactive state is introduced in 5G new RAT. The nature of these two states is similar. For LTE RAN and 5G RAN, the light connected state and the inactive state are both sub-states of the RRC connected state. When the terminal is in the light connected state or the inactive state, its RRC connection with the RAN is still maintained, and the signaling bearer and the data bearer are still maintained. However, the difference from the RRC connected state is that the terminal and RAN need to save the terminal context, the terminal mobility adopts the cell reselection method, and the terminal monitors the paging of the RAN and CN.

[0005] The introduction of the above two new states can partially reduce the power consumption of the terminal and the number of times the terminal switches from the IDLE state to the connected state, thereby reducing some signaling overhead; but it does not essentially reduce the signaling caused by massive connections. Summary of the invention

[0006] The technical problem to be solved by the present invention is to provide a connection establishment method, a storage medium, a network element and a system to solve the problem of high control plane signaling overhead cost in the prior art.

[0007] In order to solve the above technical problems, on the one hand, the present invention provides a connection establishment method.

[0008] Upon receiving a connection request initiated by user terminal B, the access network element determines the terminal group to which the user terminal B belongs;

[0009] The access network element determines, in the terminal group, a user terminal that can be subjected to connection preprocessing;

[0010] The access network element performs connection preprocessing on the determined user terminal.

[0011] Further, the user terminal capable of connection preprocessing is:

[0012] A user terminal that can create a new AS access layer context; or,

[0013] User terminals that can perform AS connection pre-recovery.

[0014] Further, connection preprocessing is performed on the determined user terminal, including:

[0015] Pre-restoring the AS connection of the user terminal determined to be capable of AS connection pre-restoration according to the pre-stored AS context of the user terminal in the terminal group; or,

[0016] An AS context is established for the user terminal capable of creating a new AS context according to the group information of the terminal group and / or the information of the user terminals in the terminal group.

[0017] Furthermore, the user terminal capable of pre-recovery of AS connection refers to: a user terminal having AS context pre-stored on both the network side and the terminal side;

[0018] The user terminal that can create a new AS access layer context refers to a user terminal that does not store an AS context on the network side and the terminal side.

[0019] Furthermore, the connection request initiated by the user terminal B is: a connection establishment request, a connection recovery request or a data transmission request.

[0020] Further, after receiving the connection request initiated by the user terminal B, the access network element determines that the user terminal B belongs to the terminal group, including:

[0021] When the user terminal B uses a physical random access channel PRACH resource pre-allocated specifically for the terminal group, it is determined that the user terminal B is a user terminal in the terminal group; or,

[0022] According to the ID uploaded by the user terminal B or the group ID of the group to which the user terminal B belongs, it is determined that the user terminal B is a user terminal in the terminal group.

[0023] Further, determining the user terminal that can perform connection preprocessing in the terminal group includes:

[0024] Sending a request to a core network element to request the core network element to determine a user terminal in the terminal group that can perform connection preprocessing; the request includes the IDs of all user terminals in the terminal group except user terminal B, the ID of the terminal group, or only the ID of user terminal B;

[0025] According to the confirmation indication fed back by the core network element, the user terminals in the terminal group that are determined to be capable of connection preprocessing are obtained.

[0026] Furthermore, establishing the AS context includes:

[0027] Using the public part of the AS context of the user terminal B as the public part of the AS context of the target user terminal to establish the AS context; or,

[0028] Preset an AS context, and use the common part in the preset AS context as the common part of the AS context of the target user terminal for which the AS context is to be established;

[0029] The dedicated part of the AS context of the target user terminal is established by negotiation between the target user terminal and the network side.

[0030] Further, the pre-restoration of the AS connection includes:

[0031] Saving the AS context of the last AS connection of all user terminals in the terminal group;

[0032] Allocating a terminal group recovery ID to the terminal group, or allocating a corresponding recovery ID to each user terminal in the terminal group;

[0033] When establishing the pre-recovery AS connection, the AS context corresponding to the received recovery ID of the terminal group or the recovery ID of the user terminal is searched; and the AS connection is pre-recovered according to the AS context.

[0034] Further, the pre-restoration of the AS connection includes:

[0035] Saving the AS context of the last AS connection of the user terminal B, and storing the common part of the AS context as the common part of the AS context of all user terminals in the terminal group;

[0036] Allocating a terminal group recovery ID to the terminal group, or allocating a corresponding recovery ID to each user terminal in the terminal group;

[0037] When establishing the pre-recovery AS connection, the AS context corresponding to the received recovery ID of the terminal group or the recovery ID of the user terminal is searched; and the AS connection is pre-recovered according to the AS context.

[0038] Further, determining the user terminal that can create a new AS context or the user terminal that can pre-recover an AS connection includes:

[0039] For user terminals in the terminal group, user terminals that concentratedly initiated connection requests or connection recovery requests in the previous terminal group, or user terminals that continuously initiated connection requests or connection recovery requests more than a set threshold, are determined as user terminals that can create new AS contexts or user terminals that can pre-recover AS connections.

[0040] Further, determining the user terminal that can create a new AS context or the user terminal that can pre-recover an AS connection includes:

[0041] When the group data period of the user terminals in the terminal group is unique, the user terminals that match the group data period and data transmission time offset of the user terminal B are determined as the user terminals that can create new AS contexts or the user terminals that can pre-recover AS connections;

[0042] When the user terminals in the terminal group have multiple data cycles, the user terminals whose data cycles and data transmission time offsets match those of the user terminal B are determined as the user terminals that can create new AS contexts or the user terminals that can pre-recover AS connections.

[0043] Further, determining the user terminal that can create a new AS context or the user terminal that can pre-recover an AS connection includes:

[0044] The user terminals that can create a new AS context or pre-recovery of AS connection are determined based on the list of user terminals that can create a new AS context or the list of user terminals that can pre-recovery of AS connection specified by the core network network element, or the list of user terminals that refuse to create a new AS context or pre-recovery of AS connection specified by the core network network element.

[0045] Furthermore, the pre-recovery of the AS connection at least includes: establishing a signaling bearer, a data bearer and AS security.

[0046] In another aspect, the present invention provides a connection establishment method, comprising:

[0047] The core network element receives a decision request sent by the access network element, requesting the core network element to determine whether a user terminal in the terminal group can perform new AS context creation or AS connection pre-recovery;

[0048] The core network element makes a decision on the request, and feeds back to the access network element a list of user terminals that are allowed and / or denied to create new AS contexts or pre-recover AS connections.

[0049] Furthermore, after the core network element makes a determination on the request, the following steps are also included:

[0050] Create a new non-access layer NAS context or pre-recover a core network connection for the user terminal;

[0051] The core network connection pre-restoration includes that the core network element restores the NAS connection and S1 connection of the terminal according to the core network context of the user terminal saved in advance, wherein the S1 connection refers to the connection between the core network and the RAN.

[0052] Furthermore, the decision request includes an ID list of user terminals to be decided, or a group ID of a preset terminal group to which the user terminal to be decided belongs.

[0053] Further, the core network connection pre-recovery also includes:

[0054] Saving the core network context of the previous core network connection of all user terminals in a preset terminal group in groups, or selecting the core network context of the previous core network connection of a user terminal B in the terminal group to save, and using the common part of the core network context storage of the user terminal B as the common part of the core network context storage of all user terminals in the terminal group;

[0055] Allocating a corresponding terminal group recovery ID for the core network context storage, or allocating a corresponding user terminal recovery ID for each user terminal in the terminal group;

[0056] When the user terminal B establishes a core network connection again, receiving a recovery ID of the terminal group or a recovery ID of the user terminal B sent by the user terminal B or the access network element;

[0057] According to the recovery ID of the terminal group or the recovery ID of the user terminal B, the core network context storage corresponding to the user terminal B is queried, and the core network connection of the user terminal B is established according to the stored core network context.

[0058] In another aspect, the present invention provides a storage medium, wherein program instructions are stored in the storage medium, and the program instructions are configured to:

[0059] After receiving a connection request initiated by user terminal B, determining the terminal group to which the user terminal B belongs;

[0060] Determining a user terminal in the terminal group that can perform connection preprocessing;

[0061] Perform connection preprocessing on the determined user terminal.

[0062] Further, the user terminal capable of connection preprocessing is:

[0063] A user terminal that can create a new AS access layer context; or,

[0064] User terminals that can perform AS connection pre-recovery.

[0065] Further, connection preprocessing is performed on the determined user terminal, including:

[0066] Pre-restoring the AS connection of the user terminal determined to be capable of AS connection pre-restoration according to the pre-stored AS context of the user terminal in the terminal group; or,

[0067] An AS context is established for the user terminal capable of creating a new AS context according to the group information of the terminal group and / or the information of the user terminals in the terminal group.

[0068] Furthermore, the user terminal capable of pre-recovery of AS connection refers to: a user terminal having AS context pre-stored on both the network side and the terminal side;

[0069] The user terminal that can create a new AS access layer context refers to a user terminal that does not store an AS context on the network side and the terminal side.

[0070] Furthermore, the connection request initiated by the user terminal B is: a connection establishment request, a connection recovery request or a data transmission request.

[0071] Further, determining that the user terminal B belongs to the terminal group includes:

[0072] After pre-allocating a dedicated physical random access channel PRACH resource for the terminal group, when the user terminal B uses the dedicated PRACH resource, determining that the user terminal B is a user terminal in the terminal group; or,

[0073] According to the ID uploaded by the user terminal B or the group ID of the group to which the user terminal B belongs, it is determined that the user terminal B is a user terminal in the terminal group.

[0074] Further, determining the user terminal that can perform connection preprocessing in the terminal group includes:

[0075] Sending a request to a core network element to request the core network element to determine a user terminal in the terminal group that can perform connection preprocessing; the request includes the IDs of all user terminals in the terminal group except user terminal B, the ID of the terminal group, or only the ID of user terminal B;

[0076] According to the confirmation indication fed back by the core network element, the user terminals in the terminal group that are determined to be capable of connection preprocessing are obtained.

[0077] Furthermore, establishing the AS context includes:

[0078] Using the public part of the AS context of the user terminal B as the public part of the AS context of the target user terminal to establish the AS context; or,

[0079] Preset an AS context, and use the common part in the preset AS context as the common part of the AS context of the target user terminal for which the AS context is to be established;

[0080] The dedicated part of the AS context of the target user terminal is established by negotiation between the target user terminal and the network side.

[0081] Further, the pre-restoration of the AS connection includes:

[0082] Saving the AS context of the last AS connection of all user terminals in the terminal group;

[0083] Allocating a terminal group recovery ID to the terminal group, or allocating a corresponding recovery ID to each user terminal in the terminal group;

[0084] When establishing the pre-recovery AS connection, the AS context corresponding to the received recovery ID of the terminal group or the recovery ID of the user terminal is searched; and the AS connection is pre-recovered according to the AS context.

[0085] Further, the pre-restoration of the AS connection includes:

[0086] Saving the AS context of the last AS connection of the user terminal B, and storing the common part of the AS context as the common part of the AS context of all user terminals in the terminal group;

[0087] Allocating a terminal group recovery ID to the terminal group, or allocating a corresponding recovery ID to each user terminal in the terminal group;

[0088] When establishing the pre-recovery AS connection, the AS context corresponding to the received recovery ID of the terminal group or the recovery ID of the user terminal is searched; and the AS connection is pre-recovered according to the AS context.

[0089] Further, determining the user terminal that can create a new AS context or the user terminal that can pre-recover an AS connection includes:

[0090] For user terminals in the terminal group, user terminals that concentratedly initiated connection requests or connection recovery requests in the previous terminal group, or user terminals that continuously initiated connection requests or connection recovery requests more than a set threshold, are determined as user terminals that can create new AS contexts or user terminals that can pre-recover AS connections.

[0091] Further, determining the user terminal that can create a new AS context or the user terminal that can pre-recover an AS connection includes:

[0092] When the group data period of the user terminals in the terminal group is unique, the user terminals that match the group data period and data transmission time offset of the user terminal B are determined as the user terminals that can create new AS contexts or the user terminals that can pre-recover AS connections;

[0093] When the user terminals in the terminal group have multiple data cycles, the user terminals whose data cycles and data transmission time offsets match those of the user terminal B are determined as the user terminals that can create new AS contexts or the user terminals that can pre-recover AS connections.

[0094] Further, determining the user terminal that can create a new AS context or the user terminal that can pre-recover an AS connection includes:

[0095] The user terminals that can create a new AS context or pre-recovery of AS connection are determined based on the list of user terminals that can create a new AS context or the list of user terminals that can pre-recovery of AS connection specified by the core network network element, or the list of user terminals that refuse to create a new AS context or pre-recovery of AS connection specified by the core network network element.

[0096] Furthermore, the pre-recovery of the AS connection at least includes: establishing a signaling bearer, a data bearer and AS security.

[0097] In another aspect, the present invention provides a storage medium, wherein program instructions are stored in the storage medium, and the program instructions are configured to:

[0098] Receiving a decision request sent by a wireless access network access network element side, requesting a core network element to determine whether a user terminal in a terminal group can perform new AS context creation or AS connection pre-recovery;

[0099] A decision is made with respect to the request, and a list of user terminals that are allowed and / or denied to perform new AS context creation or AS connection pre-recovery is fed back to the access network element.

[0100] Furthermore, after making a decision on the request, the following is also included:

[0101] Create a new non-access layer NAS context or pre-recover a core network connection for the user terminal;

[0102] The core network connection pre-recovery includes that the core network network element recovers the NAS connection and S1 connection of the terminal according to the core network context of the user terminal saved in advance, wherein the S1 connection refers to the connection between the core network and the access network element.

[0103] Furthermore, the decision request includes an ID list of user terminals to be decided, or a group ID of a preset terminal group to which the user terminal to be decided belongs.

[0104] Further, the core network connection pre-recovery also includes:

[0105] Saving the core network context of the previous core network connection of all user terminals in a preset terminal group in groups, or selecting the core network context of the previous core network connection of a user terminal B in the terminal group to save, and using the common part of the core network context storage of the user terminal B as the common part of the core network context storage of all user terminals in the terminal group;

[0106] Allocating a corresponding terminal group recovery ID for the core network context storage, or allocating a corresponding user terminal recovery ID for each user terminal in the terminal group;

[0107] When the user terminal B establishes a core network connection again, receiving a recovery ID of the terminal group or a recovery ID of the user terminal B sent by the user terminal B or the RAN;

[0108] According to the recovery ID of the terminal group or the recovery ID of the user terminal B, the core network context storage corresponding to the user terminal B is queried, and the core network connection of the user terminal B is established according to the stored core network context.

[0109] In another aspect, the present invention provides an access network element, including a processor and a memory, wherein the memory stores program instructions, and the processor performs the following operations by calling the program instructions in the memory:

[0110] After receiving a connection request initiated by user terminal B, determining the terminal group to which the user terminal B belongs;

[0111] Determining a user terminal in the terminal group that can perform connection preprocessing;

[0112] Perform connection preprocessing on the determined user terminal.

[0113] Further, connection preprocessing is performed on the determined user terminal, including:

[0114] Pre-restoring the AS connection of the user terminal determined to be capable of AS connection pre-restoration according to the pre-stored AS context of the user terminal in the terminal group; or,

[0115] An AS context is established for the user terminal capable of creating a new AS context according to the group information of the terminal group and / or the information of the user terminals in the terminal group.

[0116] Furthermore, establishing the AS context includes:

[0117] Using the public part of the AS context of the user terminal B as the public part of the AS context of the target user terminal to establish the AS context; or,

[0118] Preset an AS context, and use the common part in the preset AS context as the common part of the AS context of the target user terminal for which the AS context is to be established;

[0119] The dedicated part of the AS context of the target user terminal is established by negotiation between the target user terminal and the network side.

[0120] Further, the pre-restoration of the AS connection includes:

[0121] Saving the AS context of the last AS connection of all user terminals in the terminal group;

[0122] Allocating a terminal group recovery ID to the terminal group, or allocating a corresponding recovery ID to each user terminal in the terminal group;

[0123] When establishing the pre-recovery AS connection, the AS context corresponding to the received recovery ID of the terminal group or the recovery ID of the user terminal is searched; and the AS connection is pre-recovered according to the AS context.

[0124] Further, the pre-restoration of the AS connection includes:

[0125] Saving the AS context of the last AS connection of the user terminal B, and storing the common part of the AS context as the common part of the AS context of all user terminals in the terminal group;

[0126] Allocating a terminal group recovery ID to the terminal group, or allocating a corresponding recovery ID to each user terminal in the terminal group;

[0127] When establishing the pre-recovery AS connection, the AS context corresponding to the received recovery ID of the terminal group or the recovery ID of the user terminal is searched; and the AS connection is pre-recovered according to the AS context.

[0128] Furthermore, the pre-recovery of the AS connection at least includes: establishing a signaling bearer, a data bearer and AS security.

[0129] In another aspect, the present invention provides a core network element, including a processor and a memory, wherein the memory stores program instructions, and the processor performs the following operations by calling the program instructions in the memory:

[0130] Receiving a decision request sent by a wireless access network access network element side, requesting a core network element to determine whether a user terminal in a terminal group can perform new AS context creation or AS connection pre-recovery;

[0131] The core network element makes a decision on the request, and feeds back to the access network element a list of user terminals that are allowed and / or denied to create new AS contexts or pre-recover AS connections.

[0132] Furthermore, after making a determination on the decision request, the following steps are also included:

[0133] Create a new non-access layer NAS context or pre-recover a core network connection for the user terminal;

[0134] The core network connection pre-recovery includes that the core network network element recovers the NAS connection and S1 connection of the terminal according to the core network context of the user terminal saved in advance, wherein the S1 connection refers to the connection between the core network and the access network element.

[0135] Further, the core network connection pre-recovery also includes:

[0136] Saving the core network context of the previous core network connection of all user terminals in a preset terminal group in groups, or selecting the core network context of the previous core network connection of a user terminal B in the terminal group to save, and using the common part of the core network context storage of the user terminal B as the common part of the core network context storage of all user terminals in the terminal group;

[0137] Allocating a corresponding terminal group recovery ID for the core network context storage, or allocating a corresponding user terminal recovery ID for each user terminal in the terminal group;

[0138] When the user terminal B establishes a core network connection again, receiving a recovery ID of the terminal group or a recovery ID of the user terminal B sent by the user terminal B or the access network element;

[0139] According to the recovery ID of the terminal group or the recovery ID of the user terminal B, the core network context storage corresponding to the user terminal B is queried, and the core network connection of the user terminal B is established according to the stored core network context.

[0140] On the other hand, the present invention provides a system, comprising the above-mentioned access network element, core network element and user terminal.

[0141] The beneficial effects of the present invention are as follows:

[0142] The present invention is based on a group approach. When a terminal in the group initiates a connection, the RRC connection is pre-established or pre-recovered for other terminals in the group to which it belongs. In this way, when these terminals that have completed the pre-establishment or pre-recovery of the RRC connection initiate the establishment or recovery of the RRC connection again, the RRC connection can be quickly established or recovered, and the overhead cost of the control plane signaling is effectively reduced. BRIEF DESCRIPTION OF THE DRAWINGS

[0143] Figure 1 It is a flow chart of a method for establishing a multi-terminal connection based on a group form in an embodiment of the present invention. DETAILED DESCRIPTION

[0144] The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0145] Although the concept of group was proposed in 3GPP, it is currently only used in group-based addressing, AMBR (Aggregate Maximum Bit Rate) control, group message sending in broadcast form, and group-based billing. For the largest process (connection establishment process) generated by control plane signaling, since this is an individual discrete behavior initiated by the terminal, it is difficult to achieve it in a group manner at one time in terms of time and connection nature, so it has never been paid attention to or solved by the industry.

[0146] The core scheme of the present invention is: user terminals are grouped, and when any user terminal in the terminal group initiates a connection request (connection establishment request, connection recovery request or data transmission request), the remaining user terminals in the terminal group are screened and identified, and user terminals that can be pre-processed for connection are selected, and pre-connection processing is performed on the access network side and the core network side for the selected user terminals. In this way, when a user terminal that has established pre-connection processing initiates a connection request again, the pre-connection information is directly used to establish a connection, so that the RRC connection can be quickly established or restored, and the overhead cost of control plane signaling is effectively reduced.

[0147] The remaining user terminals in the terminal group are screened and identified, and when the user terminals that can be pre-connected are selected, if the core network side needs to make a decision, the core network network element receives the decision request sent by the access network network element RAN side, requesting the core network network element to determine whether the user terminals in the terminal group can perform new AS context creation or AS connection pre-recovery; the core network network element makes a determination based on the request, and feeds back to the RAN a list of user terminals that are allowed and / or denied to perform new AS context creation or AS connection pre-recovery.

[0148] The pre-connection processing on the base station side includes: pre-restoring the AS connection of the user terminal determined to be capable of AS connection pre-recovery based on the AS context of the user terminal in the pre-stored terminal group; or, establishing an AS context for the user terminal capable of creating a new AS context based on the group information of the terminal group and / or the information of the user terminals in the terminal group.

[0149] The pre-connection processing on the core network side includes: creating a non-access layer NAS context for the user terminal or pre-recovering the core network connection; wherein the core network connection pre-recovery includes the core network element recovering the NAS connection and S1 connection of the terminal according to the core network context of the user terminal saved in advance, wherein the S1 connection refers to the connection between the core network and the RAN.

[0150] The following describes it in detail through specific embodiments.

[0151] Example 1

[0152] This embodiment relates to a connection establishment method, which is applied to an access network element side and includes:

[0153] After receiving a connection request initiated by user terminal B, the access network element first determines the terminal group to which user terminal B belongs; then determines the user terminal that can be pre-processed for connection in the terminal group; and finally performs connection pre-processing on the determined user terminal. Through the above technical solution, when the terminal that has completed the connection pre-processing initiates a connection request again, the RRC connection can be quickly established or restored, effectively reducing the overhead cost of control plane signaling.

[0154] In this embodiment, the terminal group to which the user terminal B belongs may be determined by any of the following solutions:

[0155] When user terminal B uses a physical random access channel PRACH resource pre-allocated specifically for the terminal group, user terminal B is determined to be a user terminal in the terminal group; or,

[0156] According to the ID uploaded by the user terminal B or the group ID of the group to which the user terminal B belongs, it is determined that the user terminal B is a user terminal in the terminal group.

[0157] In the above scheme, the connection request initiated by user terminal B can be a connection establishment request, a connection recovery request or a data transmission request. The user terminal that can perform connection preprocessing is: a user terminal that can create a new access layer AS context; or a user terminal that can perform AS connection pre-recovery. The AS connection pre-recovery at least includes: establishing a signaling bearer, a data bearer and AS security.

[0158] Wherein, determining a user terminal that can create a new AS context or a user terminal that can pre-recover an AS connection includes:

[0159] For user terminals in the terminal group, user terminals that have initiated connection requests or connection recovery requests in the terminal group in the previous time, or user terminals that have continuously initiated connection requests or connection recovery requests for more than a set threshold, are determined as user terminals that can create new AS contexts or user terminals that can pre-recover AS connections; or,

[0160] Determine the user terminal in the terminal group that matches the data cycle and data transmission time offset of the user terminal B as a user terminal that can create a new AS context or a user terminal that can pre-recover an AS connection; or

[0161] Determine the user terminals that can create a new AS context or pre-recovery of AS connection based on the list of user terminals that can create a new AS context or pre-recovery of AS connection specified by the core network network element, or the list of user terminals that refuse to create a new AS context or pre-recovery of AS connection specified by the core network network element.

[0162] In the above scheme, determining the user terminals that can perform connection preprocessing in the terminal group includes:

[0163] Sending a request to a core network element to request the core network element to determine a user terminal in the terminal group that can be connected preprocessed; the request includes the IDs of all user terminals in the terminal group except user terminal B, the ID of the terminal group, or only the ID of user terminal B;

[0164] According to the confirmation indication fed back by the core network element, the user terminal determined in the terminal group for which connection preprocessing can be performed is obtained.

[0165] In the above solution, establishing the AS context includes:

[0166] The public part of the AS context of user terminal B is used as the public part of the AS context of the target user terminal for which the AS context is to be established; or, an AS context is preset, and the public part of the preset AS context is used as the public part of the AS context of the target user terminal for which the AS context is to be established; the private part of the AS context of the target user terminal is established by negotiation between the target user terminal and the network side.

[0167] In the above solution, the pre-restoration of AS connection includes:

[0168] The AS context of the last AS connection of all user terminals in the terminal group is saved; a terminal group recovery ID is assigned to the terminal group, or a corresponding recovery ID is assigned to each user terminal in the terminal group; when establishing a pre-recovery AS connection, the corresponding AS context is found according to the received recovery ID of the terminal group or the recovery ID of the user terminal; the AS connection is pre-recovered according to the AS context; or,

[0169] Save the AS context of the last AS connection of user terminal B, and store the common part of the AS context as the common part of the AS context of all user terminals in the terminal group; assign a terminal group recovery ID to the terminal group, or assign a corresponding recovery ID to each user terminal in the terminal group; when establishing a pre-recovery AS connection, find the corresponding AS context based on the received recovery ID of the terminal group or the recovery ID of the user terminal; pre-recover the AS connection based on the AS context.

[0170] In the above scheme, connection preprocessing is performed on the determined user terminal, specifically:

[0171] According to the AS context of the user terminal in the pre-stored terminal group, the AS connection is pre-restored for the user terminal determined to be capable of AS connection pre-recovery; or, according to the group information of the terminal group and / or the information of the user terminal in the terminal group, an AS context is established for the user terminal capable of creating a new AS context.

[0172] Example 2

[0173] This embodiment relates to a storage medium, in which program instructions are stored for implementing the technical solution of Embodiment 1, wherein the program instructions are used to implement the following functions:

[0174] After receiving a connection request initiated by user terminal B, the access network element first determines the terminal group to which user terminal B belongs; then determines the user terminal that can be pre-processed for connection in the terminal group; and finally performs connection pre-processing on the determined user terminal. Through the above technical solution, when the terminal that has completed the connection pre-processing initiates a connection request again, the RRC connection can be quickly established or restored, effectively reducing the overhead cost of control plane signaling.

[0175] In this embodiment, the terminal group to which the user terminal B belongs may be determined by any of the following solutions:

[0176] When user terminal B uses a physical random access channel PRACH resource pre-allocated specifically for the terminal group, user terminal B is determined to be a user terminal in the terminal group; or,

[0177] According to the ID uploaded by the user terminal B or the group ID of the group to which the user terminal B belongs, it is determined that the user terminal B is a user terminal in the terminal group.

[0178] In the above scheme, the connection request initiated by user terminal B can be a connection establishment request, a connection recovery request or a data transmission request. The user terminal that can perform connection preprocessing is: a user terminal that can create a new access layer AS context; or a user terminal that can perform AS connection pre-recovery. The AS connection pre-recovery at least includes: establishing a signaling bearer, a data bearer and AS security.

[0179] Wherein, determining a user terminal that can create a new AS context or a user terminal that can pre-recover an AS connection includes:

[0180] For user terminals in the terminal group, user terminals that have initiated connection requests or connection recovery requests in the terminal group in the previous time, or user terminals that have continuously initiated connection requests or connection recovery requests for more than a set threshold, are determined as user terminals that can create new AS contexts or user terminals that can pre-recover AS connections; or,

[0181] Determine the user terminal in the terminal group that matches the data cycle and data transmission time offset of the user terminal B as a user terminal that can create a new AS context or a user terminal that can pre-recover an AS connection; or

[0182] Determine the user terminals that can create a new AS context or pre-recovery of AS connection based on the list of user terminals that can create a new AS context or pre-recovery of AS connection specified by the core network network element, or the list of user terminals that refuse to create a new AS context or pre-recovery of AS connection specified by the core network network element.

[0183] In the above scheme, determining the user terminals that can perform connection preprocessing in the terminal group includes:

[0184] Sending a request to a core network element to request the core network element to determine a user terminal in the terminal group that can be connected preprocessed; the request includes the IDs of all user terminals in the terminal group except user terminal B, the ID of the terminal group, or only the ID of user terminal B;

[0185] According to the confirmation indication fed back by the core network element, the user terminal determined in the terminal group for which connection preprocessing can be performed is obtained.

[0186] In the above solution, establishing the AS context includes:

[0187] The public part of the AS context of user terminal B is used as the public part of the AS context of the target user terminal for which the AS context is to be established; or, an AS context is preset, and the public part of the preset AS context is used as the public part of the AS context of the target user terminal for which the AS context is to be established; the private part of the AS context of the target user terminal is established by negotiation between the target user terminal and the network side.

[0188] In the above solution, the pre-restoration of AS connection includes:

[0189] The AS context of the last AS connection of all user terminals in the terminal group is saved; a terminal group recovery ID is assigned to the terminal group, or a corresponding recovery ID is assigned to each user terminal in the terminal group; when establishing a pre-recovery AS connection, the corresponding AS context is found according to the received recovery ID of the terminal group or the recovery ID of the user terminal; the AS connection is pre-recovered according to the AS context; or,

[0190] Save the AS context of the last AS connection of user terminal B, and store the common part of the AS context as the common part of the AS context of all user terminals in the terminal group; assign a terminal group recovery ID to the terminal group, or assign a corresponding recovery ID to each user terminal in the terminal group; when establishing a pre-recovery AS connection, find the corresponding AS context based on the received recovery ID of the terminal group or the recovery ID of the user terminal; pre-recover the AS connection based on the AS context.

[0191] In the above scheme, connection preprocessing is performed on the determined user terminal, specifically:

[0192] According to the AS context of the user terminal in the pre-stored terminal group, the AS connection is pre-restored for the user terminal determined to be capable of AS connection pre-recovery; or, according to the group information of the terminal group and / or the information of the user terminal in the terminal group, an AS context is established for the user terminal capable of creating a new AS context.

[0193] Example 3

[0194] This embodiment relates to an access network element, including a processor and a memory, wherein program instructions are stored in the processor, and the processor implements the technical solution of Embodiment 1 by calling the program instructions stored in the memory, wherein the program instructions are used to implement the following functions:

[0195] After receiving a connection request initiated by user terminal B, the access network element first determines the terminal group to which user terminal B belongs; then determines the user terminal that can be pre-processed for connection in the terminal group; and finally performs connection pre-processing on the determined user terminal. Through the above technical solution, when the terminal that has completed the connection pre-processing initiates a connection request again, the RRC connection can be quickly established or restored, effectively reducing the overhead cost of control plane signaling.

[0196] In this embodiment, the terminal group to which the user terminal B belongs may be determined by any of the following solutions:

[0197] When user terminal B uses a physical random access channel PRACH resource pre-allocated specifically for the terminal group, user terminal B is determined to be a user terminal in the terminal group; or,

[0198] According to the ID uploaded by the user terminal B or the group ID of the group to which the user terminal B belongs, it is determined that the user terminal B is a user terminal in the terminal group.

[0199] In the above scheme, the connection request initiated by user terminal B can be a connection establishment request, a connection recovery request or a data transmission request. The user terminal that can perform connection preprocessing is: a user terminal that can create a new access layer AS context; or a user terminal that can perform AS connection pre-recovery. The AS connection pre-recovery at least includes: establishing a signaling bearer, a data bearer and AS security.

[0200] Wherein, determining a user terminal that can create a new AS context or a user terminal that can pre-recover an AS connection includes:

[0201] For user terminals in the terminal group, user terminals that have initiated connection requests or connection recovery requests in the terminal group in the previous time, or user terminals that have continuously initiated connection requests or connection recovery requests for more than a set threshold, are determined as user terminals that can create new AS contexts or user terminals that can pre-recover AS connections; or,

[0202] Determine the user terminal in the terminal group that matches the data cycle and data transmission time offset of the user terminal B as a user terminal that can create a new AS context or a user terminal that can pre-recover an AS connection; or

[0203] Determine the user terminals that can create a new AS context or pre-recovery of AS connection based on the list of user terminals that can create a new AS context or pre-recovery of AS connection specified by the core network network element, or the list of user terminals that refuse to create a new AS context or pre-recovery of AS connection specified by the core network network element.

[0204] In the above scheme, determining the user terminals that can perform connection preprocessing in the terminal group includes:

[0205] Sending a request to a core network element to request the core network element to determine a user terminal in the terminal group that can be connected preprocessed; the request includes the IDs of all user terminals in the terminal group except user terminal B, the ID of the terminal group, or only the ID of user terminal B;

[0206] According to the confirmation indication fed back by the core network element, the user terminal determined in the terminal group for which connection preprocessing can be performed is obtained.

[0207] In the above solution, establishing the AS context includes:

[0208] The public part of the AS context of user terminal B is used as the public part of the AS context of the target user terminal for which the AS context is to be established; or, an AS context is preset, and the public part of the preset AS context is used as the public part of the AS context of the target user terminal for which the AS context is to be established; the private part of the AS context of the target user terminal is established by negotiation between the target user terminal and the network side.

[0209] In the above solution, the pre-restoration of AS connection includes:

[0210] The AS context of the last AS connection of all user terminals in the terminal group is saved; a terminal group recovery ID is assigned to the terminal group, or a corresponding recovery ID is assigned to each user terminal in the terminal group; when establishing a pre-recovery AS connection, the corresponding AS context is found according to the received recovery ID of the terminal group or the recovery ID of the user terminal; the AS connection is pre-recovered according to the AS context; or,

[0211] Save the AS context of the last AS connection of user terminal B, and store the common part of the AS context as the common part of the AS context of all user terminals in the terminal group; assign a terminal group recovery ID to the terminal group, or assign a corresponding recovery ID to each user terminal in the terminal group; when establishing a pre-recovery AS connection, find the corresponding AS context based on the received recovery ID of the terminal group or the recovery ID of the user terminal; pre-recover the AS connection based on the AS context.

[0212] In the above scheme, connection preprocessing is performed on the determined user terminal, specifically:

[0213] According to the AS context of the user terminal in the pre-stored terminal group, the AS connection is pre-restored for the user terminal determined to be capable of AS connection pre-recovery; or, according to the group information of the terminal group and / or the information of the user terminal in the terminal group, an AS context is established for the user terminal capable of creating a new AS context.

[0214] Example 4

[0215] This embodiment relates to a connection establishment method, which is applied to a core network element side and includes:

[0216] The core network network element receives a decision request sent by the access network network element, requesting the core network network element to determine whether a user terminal in a terminal group can create a new AS context or pre-recover an AS connection; wherein the decision request includes an ID list of user terminals to be decided, or a group ID of a preset terminal group to which the user terminal to be decided belongs.

[0217] The core network element makes a decision on the request, and feeds back to the access network element a list of user terminals that are allowed and / or denied to create new AS contexts or pre-recover AS connections.

[0218] Furthermore, after the core network element makes a determination on the request, the following steps are also included:

[0219] Create a new non-access layer NAS context or pre-recover a core network connection for the user terminal;

[0220] The core network connection pre-recovery includes that the core network network element recovers the NAS connection and S1 connection of the terminal according to the core network context of the user terminal saved in advance, wherein the S1 connection refers to the connection between the core network and the access network element.

[0221] Wherein, the core network connection pre-recovery also includes:

[0222] Saving the core network context of the previous core network connection of all user terminals in a preset terminal group in groups, or selecting the core network context of the previous core network connection of a user terminal B in the terminal group to save, and using the common part of the core network context storage of the user terminal B as the common part of the core network context storage of all user terminals in the terminal group;

[0223] Allocating a corresponding terminal group recovery ID for the core network context storage, or allocating a corresponding user terminal recovery ID for each user terminal in the terminal group;

[0224] When the user terminal B establishes a core network connection again, receiving a recovery ID of the terminal group or a recovery ID of the user terminal B sent by the user terminal B or the access network element;

[0225] According to the recovery ID of the terminal group or the recovery ID of the user terminal B, the core network context storage corresponding to the user terminal B is queried, and the core network connection of the user terminal B is established according to the stored core network context.

[0226] The technical solution of this embodiment performs non-access layer NAS context creation or core network connection pre-recovery on the user terminal that is determined to perform AS context creation or AS connection pre-recovery. In this way, when these terminals initiate a request and then initiate a connection establishment request, the RRC connection can be quickly established or restored, and the overhead cost of control plane signaling can be effectively reduced.

[0227] Example 5

[0228] This embodiment relates to a storage medium, in which program instructions are stored for implementing the technical solution of Embodiment 4, wherein the program instructions are used to implement the following functions:

[0229] The core network network element receives a decision request sent by the access network network element, requesting the core network network element to determine whether a user terminal in a terminal group can create a new AS context or pre-recover an AS connection; wherein the decision request includes an ID list of user terminals to be decided, or a group ID of a preset terminal group to which the user terminal to be decided belongs.

[0230] The core network element makes a decision on the request, and feeds back to the access network element a list of user terminals that are allowed and / or denied to create new AS contexts or pre-recover AS connections.

[0231] Furthermore, after the core network element makes a determination on the request, the following steps are also included:

[0232] Create a new non-access layer NAS context or pre-recover a core network connection for the user terminal;

[0233] The core network connection pre-recovery includes that the core network network element recovers the NAS connection and S1 connection of the terminal according to the core network context of the user terminal saved in advance, wherein the S1 connection refers to the connection between the core network and the access network element.

[0234] Wherein, the core network connection pre-recovery also includes:

[0235] Saving the core network context of the previous core network connection of all user terminals in a preset terminal group in groups, or selecting the core network context of the previous core network connection of a user terminal B in the terminal group to save, and using the common part of the core network context storage of the user terminal B as the common part of the core network context storage of all user terminals in the terminal group;

[0236] Allocating a corresponding terminal group recovery ID for the core network context storage, or allocating a corresponding user terminal recovery ID for each user terminal in the terminal group;

[0237] When the user terminal B establishes a core network connection again, receiving a recovery ID of the terminal group or a recovery ID of the user terminal B sent by the user terminal B or the access network element;

[0238] According to the recovery ID of the terminal group or the recovery ID of the user terminal B, the core network context storage corresponding to the user terminal B is queried, and the core network connection of the user terminal B is established according to the stored core network context.

[0239] The technical solution of this embodiment performs non-access layer NAS context creation or core network connection pre-recovery on the user terminal that is determined to perform AS context creation or AS connection pre-recovery. In this way, when these terminals initiate a request and then initiate a connection establishment request, the RRC connection can be quickly established or restored, and the overhead cost of control plane signaling can be effectively reduced.

[0240] Example 6

[0241] This embodiment relates to a core network element, including a processor and a memory, wherein program instructions are stored in the processor, and the processor implements the technical solution of Embodiment 4 by calling the program instructions stored in the memory, wherein the program instructions are used to implement the following functions:

[0242] Receive a decision request sent by an access network element, and request the core network element to determine whether a user terminal in a terminal group can create a new AS context or pre-recover an AS connection; wherein the decision request includes an ID list of user terminals to be decided, or a group ID of a preset terminal group to which the user terminal to be decided belongs.

[0243] A decision is made with respect to the request, and a list of user terminals that are allowed and / or denied to perform new AS context creation or AS connection pre-recovery is fed back to the access network element.

[0244] Furthermore, after making a decision on the request, the following is also included:

[0245] Create a new non-access layer NAS context or pre-recover a core network connection for the user terminal;

[0246] The core network connection pre-restoration includes restoring the NAS connection and S1 connection of the terminal according to the core network context of the user terminal saved in advance, wherein the S1 connection refers to the connection between the core network and the access network elements.

[0247] Wherein, the core network connection pre-recovery also includes:

[0248] Saving the core network context of the previous core network connection of all user terminals in a preset terminal group in groups, or selecting the core network context of the previous core network connection of a user terminal B in the terminal group to save, and using the common part of the core network context storage of the user terminal B as the common part of the core network context storage of all user terminals in the terminal group;

[0249] Allocating a corresponding terminal group recovery ID for the core network context storage, or allocating a corresponding user terminal recovery ID for each user terminal in the terminal group;

[0250] When the user terminal B establishes a core network connection again, receiving a recovery ID of the terminal group or a recovery ID of the user terminal B sent by the user terminal B or the access network element;

[0251] According to the recovery ID of the terminal group or the recovery ID of the user terminal B, the core network context storage corresponding to the user terminal B is queried, and the core network connection of the user terminal B is established according to the stored core network context.

[0252] The technical solution of this embodiment performs non-access layer NAS context creation or core network connection pre-recovery on the user terminal that is determined to perform AS context creation or AS connection pre-recovery. In this way, when these terminals initiate a request and then initiate a connection establishment request, the RRC connection can be quickly established or restored, and the overhead cost of control plane signaling can be effectively reduced.

[0253] The following is a specific embodiment to illustrate the method for establishing a multi-terminal connection in a group form and related network element devices of the present invention.

[0254] Example 7

[0255] Taking the LTE system as an example, assuming that a terminal group A has been predefined on the core network element MME-A (mobility management entity-A) side, which contains the IDs of 10 terminals (such as S-TMSI or IMSI), and the eNB under MME-A has obtained the information of group A from MME-A in advance, terminal B (assuming it is a member of terminal group A) initiates a calling process and initiates an RRC connection establishment process to an eNB (LTE RAN base station) under MME-A; 5 minutes later, another member terminal D of group A initiates an RRC connection recovery process to the eNB.

[0256] This example is used to illustrate how the RAN (Radio Access Network) and MME prepare the AS connections and core network connections of multiple group members in advance in the form of a group during the process of establishing a new network connection, and use them in the subsequent RRC connection establishment process of the group member terminals to reduce the air interface signaling overhead.

[0257] Figure 1 Only the process of establishing RRC connection pre-recovery for other terminals in the group is shown in the figure (Note: AS connection is a general term for the connection between the wireless access network and the terminal, and RRC connection belongs to AS connection), as well as the subsequent process of establishing RRC connection initiated by the terminal in the group. Therefore, Figure 1 The process of establishing an RRC connection by terminal B is not included, which does not mean that terminal B does not establish an RRC connection. Figure 1 The connection request initiated by user terminal B may be: a connection establishment request, a connection recovery request or a data transmission.

[0258] like Figure 1 As shown, the method for establishing a multi-terminal connection based on a group form includes:

[0259] Step 101: Terminal B initiates an RRC connection establishment process to the eNB, and reports its own UE ID (S-TMSI) in the RRC connection establishment request message. The reason for this RRC connection establishment is MO-data (calling data service);

[0260] Step 102: eNB queries whether terminal B is a member of a certain group, and determines that it belongs to group A based on its ID; the member terminals belonging to the same group are defined by the RAN or core network element, and a group ID is assigned. The member terminals in the group should have the following common characteristics: the same service, the same service model, the same service type, the same terminal type, or the same APN (Access Point Name).

[0261] Step 103: the eNB determines whether to perform RRC connection pre-recovery for the remaining 9 group member terminals of group A; the necessary condition for performing RRC connection pre-recovery is that the eNB has stored the AS context of the terminal in advance, and the terminal without the stored context cannot perform RRC connection pre-recovery. On the basis of satisfying the necessary condition, the method for determining which group member terminals to perform RRC connection pre-recovery includes:

[0262] Judging by the activity of group members: If a group member X did not initiate a connection in the previous RRC connection of group members, or group member X did not initiate an RRC connection for several consecutive times, the group member X is considered to be an inactive member, and RAN does not pre-recover the RRC connection for the member;

[0263] Judging by the data cycle of the group members: If the group members have reported their own data transmission cycle information (data cycle) to the RAN, or the RAN has obtained the data transmission cycle information of the group A from the MME, the RAN can determine whether it is necessary to pre-recover the RRC connection for the member based on the information; specifically:

[0264] If the UE currently initiating the connection does not meet the data cycle and data transmission time offset, it is determined that this connection is a personal burst behavior of the UE, and there is no need to pre-recover the RRC connection of other group members;

[0265] If the group members have multiple data cycles, it is determined which group members' data cycles and data transmission time offsets match the UE currently initiating the connection, and the RRC connections of the matching group members can be pre-recovered;

[0266] According to the feedback from the MME: if the MME-A specifies a list of UEs that can pre-recover the RRC connection, the eNB determines the group member UEs that can pre-recover the RRC connection according to these instructions; if the MME specifies a list of UEs that refuse to pre-recover the connection, the eNB does not perform RRC pre-establishment or pre-recovery for the UEs in the list;

[0267] If the connection establishment reason of terminal B that currently initiates the connection process is MT call (Mobile Terminal Call, called party), and RAN has not received paging from MME to other group A member UEs, or has not received group paging of group A from MME, it is considered that this MT call is only a separate service of the UE, and other group A members do not need to pre-recover RRC connections together;

[0268] Among the above methods, one method can be selected to assist in the judgment, or two or three methods can be used in combination, among which the method indicated by the MME has the highest priority. That is, if the eNB determines that there are 8 terminals that can perform RRC connection pre-recovery, but the MME indicates that only 5 of them are allowed to perform RRC connection pre-recovery, then the eNB needs to comply with the MME's instructions.

[0269] In this example, it is assumed that the eNB determines that 7 terminals out of the remaining 9 terminals perform RRC pre-recovery.

[0270] Step 104: The eNB sends the list of seven terminals selected for RRC pre-recovery to the MME for review. The list can be carried by existing signaling of the S1 interface, such as by sending an initial UE message; or a new S1 interface signaling can be defined. The S1 interface refers to the interface between the eNB and the MME. Note: If the eNB decides to perform RRC connection pre-recovery on all the remaining terminals in group A, only the ID of group A can be sent to the MME.

[0271] Step 105: MME examines whether these 7 terminals can pre-recover the core network connection. Similarly, the necessary condition for pre-recovery of the core network connection is that MME has stored the core network context of the corresponding terminal in advance. Otherwise, the terminal cannot pre-recover the core network connection. On the basis of meeting this necessary condition, the method of examination can also refer to the method of step 103. Due to the differences in algorithms and parameters between eNB and MME, and the need for MME to consider additional factors such as its own load, the MME's examination result may reject the pre-establishment of some terminals. In this example, assuming that MME only allows 6 terminals to pre-recover the core network connection, MME will feed back the list of terminals allowed to pre-recover the core network connection to eNB. The list can be carried through the existing signaling of the S1 interface, such as sent through the initial Context Setup Request; or a new S1 interface signaling can be defined.

[0272] At the same time, the MME starts to pre-recover the core network connections of the six terminals, that is, according to the corresponding terminal contexts pre-stored by the MME, the S1 control plane bearer, S1 user plane bearer, NAS security context, etc. are restored for each terminal.

[0273] Step 106: The eNB finally determines the terminals that can perform RRC pre-recovery according to the list of the MME, and performs RRC connection pre-recovery of the terminals according to the AS contexts of the terminals stored in the eNB, including establishing signaling bearers, data bearers, AS security contexts, etc. for each terminal;

[0274] Note: In the above steps, the process of establishing the RRC connection and NAS connection of terminal B is not affected, and the pre-recovery of the RRC connection and core network connection of other terminals can be carried out in parallel.

[0275] A terminal that has completed RRC connection pre-recovery and core network connection pre-recovery is in a light connected state from the perspective of the LTE network; it is in an inactive state from the perspective of the 5G new RAT network, that is, both the terminal and the network side save the terminal context, the terminal mobility adopts the cell reselection method, and the terminal monitors the paging of the RAN and the core network.

[0276] Step 107: 5 minutes later, assuming that member terminal D of group A wants to initiate a service, it initiates an RRC connection establishment process or an RRC connection recovery process to the eNB, and reports its own UE ID in the RRC connection establishment request message or the RRC connection recovery request message. The reason for this RRC connection establishment is MO-data (calling data service);

[0277] Step 108: the eNB inquires whether the terminal D has pre-recovered the RRC connection. If so, the pre-recovered RRC connection context (or AS context) is directly used to configure the RRC connection parameters for the terminal D and send them down, and at the same time inform the MME that the terminal D can recover the connection. The notification information should include the ID of the terminal D. The notification information can be carried in the existing S1 interface signaling, or a new S1 interface signaling is created; if not, the RRC connection is still established for the terminal according to the normal new RRC connection process;

[0278] Step 109: After receiving the notification information sent by the eNB, the MME uses the pre-recovered core network connection to transmit control plane signaling to the terminal D.

[0279] Embodiment 8:

[0280] The application scenario of this embodiment is the same as that of Embodiment 7, except that when determining the list of terminals that can perform RRC connection pre-recovery, in addition to the final decision made by the MME as described in Embodiment 7, the following method may also be used:

[0281] The RAN does not perform step 103, but directly sends the user terminal list of group A to the MME, and the MME makes the final decision to determine which user terminals can perform RRC connection pre-recovery;

[0282] Embodiment 9:

[0283] The application scenario of this embodiment is assumed to be the same as that of Embodiment 7, except that when determining the list of terminals that can perform RRC connection pre-recovery, in addition to the final decision made by the MME as described in Embodiment 7, the following method may also be used:

[0284] The RAN does not perform steps 104 and 105, but directly performs RRC connection pre-recovery on the user terminals in group A that it has determined can perform RRC connection pre-recovery;

[0285] This is further divided into two implementation modes:

[0286] 1. The RAN does not inform the MME of the list of user terminals in group A that are determined to perform RRC connection pre-recovery, so that when a terminal that has pre-recovered the RRC connection subsequently accesses the network, a new core network connection can be created for it;

[0287] 2. The RAN notifies the MME of the list of user terminals in group A for which RRC connection pre-recovery is determined, and the MME performs core network connection pre-recovery for the UEs included in the list;

[0288] Embodiment 10:

[0289] Taking the LTE system as an example, assuming that a terminal group A has been predefined on the RAN side, which contains the IDs of 10 terminals (such as S-TMSI or IMSI), terminal B (assuming it is a member of terminal group A) initiates the calling process and initiates the RRC connection establishment process to the eNB (the base station of the LTE RAN); 5 minutes later, another member terminal D of group A also initiates the RRC connection recovery process to the eNB.

[0290] This example is used to illustrate how RAN prepares partial contexts of AS connections of multiple group members in advance in the form of a group during a new network connection, and uses them in the subsequent RRC connection establishment or recovery process of the group member terminals to reduce air interface signaling overhead and reduce the processing power consumption of the base station.

[0291] Step 401: Terminal B initiates an RRC connection establishment process to the eNB, and reports its own UE ID (S-TMSI) in the RRC connection establishment request message. The reason for this RRC connection establishment is MO-data (calling data service);

[0292] Step 402: the eNB queries whether terminal B is a member of a certain group, and determines that it belongs to group A according to its ID;

[0293] Step 403: The eNB determines whether the remaining 9 group member terminals of group A have stored AS contexts. If not, then only new AS contexts can be created. In this example, it is assumed that the eNB does not have AS contexts stored by these 9 group member terminals. Then the eNB further determines which terminals to create new AS contexts for. The selection method includes:

[0294] Judging by the activity of group members: If a group member X did not initiate a connection in the previous RRC connection of group members, or group member X did not initiate an RRC connection for several consecutive times, the group member X is considered to be an inactive member, and RAN does not create a new AS context for the member;

[0295] Determine based on the data cycle of the group members: If the group members have reported their own data transmission cycle information to the RAN, or the RAN has obtained the data transmission cycle information of the group A from the MME, the RAN can determine whether a new AS context needs to be created for the member based on the information; specifically:

[0296] If the UE currently initiating the connection does not meet the group data cycle and data transmission time offset, it is determined that this connection is a personal burst behavior of the UE and no new AS context is required;

[0297] If the group members have multiple data cycles, it is determined which group members' data cycles and data transmission time offsets match the UE currently initiating the connection, and a new AS context can be created for the matching group members;

[0298] If the connection establishment reason of the terminal B that currently initiates the connection process is MT call (Mobile Terminal Call, called party), and the RAN has not received paging from the MME to other UEs of group A, or has not received group paging of group A from the MME, it is considered that this MT call is only a separate service of the UE, and other members of group A do not need to create a new AS context together;

[0299] Among the above methods, one method can be selected to assist in the judgment, or two or three methods can be used in combination.

[0300] In this example, it is assumed that the eNB determines to create new AS contexts for 7 terminals out of the remaining 9 terminals.

[0301] Step 404: the eNB creates a new AS context for the selected terminal, including the following two methods:

[0302] 1. Create a new AS context based on the AS context of terminal B that is currently establishing a connection;

[0303] 2. Create a new AS context based on the preset default AS context.

[0304] The AS context is divided into a public part and a private part;

[0305] The common part refers to the AS context part that can be used with other UEs. In the LTE standard, it includes one or more of the following: UE security capability, QoS information, RAB (radio access bearer) information, RRC context, and switching restriction list; among which, although the UE security capability and QoS information may vary from terminal to terminal, the common part of the AS context can be used for the same group of terminals with the same characteristics;

[0306] The proprietary part refers to the AS context part that is unique to the UE and different from other UEs, and at least includes: AS security information. Because the AS security information needs to be dynamically updated, it cannot be used as a reference by other UEs or a fixed blueprint for reference;

[0307] The newly created AS context by the eNB for the selected terminal actually refers to the public part of the newly created AS context, and the exclusive part of the AS context of the terminal needs to be newly created when the terminal initiates an RRC connection by itself.

[0308] Step 405: 5 minutes later, assuming that member terminal D of group A wants to initiate a service, it initiates an RRC connection establishment process or an RRC connection recovery process to the eNB, reports its own UE ID in the RRC connection establishment request message or the RRC connection recovery request message, and the reason for this RRC connection establishment is MO-data (calling data service);

[0309] Step 406: eNB inquires whether terminal D has created a new AS context. If so, the public part of the context of terminal D is established based on the newly created context. In addition, eNB regenerates the private part of the AS context for terminal D, for example: sending the newly generated AS security information to terminal D, and completing the AS security handshake with terminal D to establish AS security.

[0310] Embodiment 11:

[0311] In combination with Example 7 and Example 10, in step 103 and step 403, when the eNB selects which terminals among the remaining terminals of group A can perform RRC connection pre-recovery or AS context creation, if some of the remaining terminals do not have pre-saved contexts in the eNB, and some have pre-saved contexts in the eNB, then the eNB can choose to use both methods at the same time, i.e., perform AS context creation for terminals that do not have pre-saved AS contexts, and perform RRC connection pre-recovery for terminals that have pre-saved AS contexts.

[0312] Embodiment 12:

[0313] This embodiment describes how to perform AS context preservation and RRC connection recovery in groups in an eNB, including:

[0314] Saving the terminal AS context of the previous AS connection of all user terminals of the terminal group A in groups, and assigning a corresponding group A recovery ID to the AS context storage; or assigning a corresponding recovery ID to each user terminal in the terminal group A;

[0315] Alternatively, the AS context of the previous AS connection of the user terminal B is selected for saving, and the common part of the AS context of the user terminal B is stored as the common part of the AS context of all user terminals in the terminal group A; a corresponding group A recovery ID is assigned to the AS context storage; or a corresponding recovery ID is assigned to each user terminal in the terminal group A;

[0316] When user terminal B in group A requests to establish an AS connection again, RAN receives the recovery ID of the terminal group A or the recovery ID of the user terminal B sent by it, queries the AS context storage corresponding to the terminal B according to the recovery ID of the terminal group A or the recovery ID of the user terminal B, and establishes the AS connection of the user terminal B according to the stored context.

[0317] Embodiment 13:

[0318] The present embodiment relates to a system for implementing the above-mentioned embodiment, which system includes an access network element, a core network element and a user terminal. Among them, the access network element includes a memory (storage medium) and a processor, and the processor of the access network element implements the functions of the access network element in the above-mentioned embodiment by calling the program instructions (software program) in the memory on the access network element. The core network element includes a memory (storage medium) and a processor, and the processor of the core network element implements the functions of the core network element in the above-mentioned embodiment by calling the program instructions (software program) in the memory on the core network element. The storage medium refers to a physical carrier for storing program instruction data (software program); it can be a floppy disk, an optical disk, a DVD, a hard disk, a flash memory, a U disk, a CF card, an SD card, an MMC card, a SM card, a memory stick (Memory Stick), an xD card, etc.; it can also be a device including the above-mentioned storage products. Among them:

[0319] 1. The program instructions stored in the memory installed on the access network element implement the following functions:

[0320] After receiving a connection request initiated by user terminal B, determining the terminal group to which the user terminal B belongs;

[0321] Determining a user terminal in the terminal group that can perform connection preprocessing;

[0322] Perform connection preprocessing on the determined user terminal.

[0323] Further, the user terminal capable of connection preprocessing is:

[0324] A user terminal that can create a new AS access layer context; or,

[0325] User terminals that can perform AS connection pre-recovery.

[0326] Further, connection preprocessing is performed on the determined user terminal, including:

[0327] Pre-restoring the AS connection of the user terminal determined to be capable of AS connection pre-restoration according to the pre-stored AS context of the user terminal in the terminal group; or,

[0328] An AS context is established for the user terminal capable of creating a new AS context according to the group information of the terminal group and / or the information of the user terminals in the terminal group.

[0329] Furthermore, the user terminal capable of pre-recovery of AS connection refers to: a user terminal having AS context pre-stored on both the network side and the terminal side;

[0330] The user terminal that can create a new AS access layer context refers to a user terminal that does not store an AS context on the network side and the terminal side.

[0331] Furthermore, the connection request initiated by the user terminal B is: a connection establishment request, a connection recovery request or a data transmission request.

[0332] Further, determining that the user terminal B belongs to the terminal group includes:

[0333] After pre-allocating a dedicated physical random access channel PRACH resource for the terminal group, when the user terminal B uses the dedicated PRACH resource, determining that the user terminal B is a user terminal in the terminal group; or,

[0334] According to the ID uploaded by the user terminal B or the group ID of the group to which the user terminal B belongs, it is determined that the user terminal B is a user terminal in the terminal group.

[0335] Further, determining the user terminal that can perform connection preprocessing in the terminal group includes:

[0336] Sending a request to a core network element to request the core network element to determine a user terminal in the terminal group that can perform connection preprocessing; the request includes the IDs of all user terminals in the terminal group except user terminal B, the ID of the terminal group, or only the ID of user terminal B;

[0337] According to the confirmation indication fed back by the core network element, the user terminals in the terminal group that are determined to be capable of connection preprocessing are obtained.

[0338] Furthermore, establishing the AS context includes:

[0339] Using the public part of the AS context of the user terminal B as the public part of the AS context of the target user terminal to establish the AS context; or,

[0340] Preset an AS context, and use the common part in the preset AS context as the common part of the AS context of the target user terminal for which the AS context is to be established;

[0341] The dedicated part of the AS context of the target user terminal is established by negotiation between the target user terminal and the network side.

[0342] Further, the pre-restoration of the AS connection includes:

[0343] Saving the AS context of the last AS connection of all user terminals in the terminal group;

[0344] Allocating a terminal group recovery ID to the terminal group, or allocating a corresponding recovery ID to each user terminal in the terminal group;

[0345] When establishing the pre-recovery AS connection, the AS context corresponding to the received recovery ID of the terminal group or the recovery ID of the user terminal is searched; and the AS connection is pre-recovered according to the AS context.

[0346] Further, the pre-restoration of the AS connection includes:

[0347] Saving the AS context of the last AS connection of the user terminal B, and storing the common part of the AS context as the common part of the AS context of all user terminals in the terminal group;

[0348] Allocating a terminal group recovery ID to the terminal group, or allocating a corresponding recovery ID to each user terminal in the terminal group;

[0349] When establishing the pre-recovery AS connection, the AS context corresponding to the received recovery ID of the terminal group or the recovery ID of the user terminal is searched; and the AS connection is pre-recovered according to the AS context.

[0350] Further, determining the user terminal that can create a new AS context or the user terminal that can pre-recover an AS connection includes:

[0351] For user terminals in the terminal group, user terminals that concentratedly initiated connection requests or connection recovery requests in the previous terminal group, or user terminals that continuously initiated connection requests or connection recovery requests more than a set threshold, are determined as user terminals that can create new AS contexts or user terminals that can pre-recover AS connections.

[0352] Further, determining the user terminal that can create a new AS context or the user terminal that can pre-recover an AS connection includes:

[0353] When the group data period of the user terminals in the terminal group is unique, the user terminals that match the group data period and data transmission time offset of the user terminal B are determined as the user terminals that can create new AS contexts or the user terminals that can pre-recover AS connections;

[0354] When the user terminals in the terminal group have multiple data cycles, the user terminals whose data cycles and data transmission time offsets match those of the user terminal B are determined as the user terminals that can create new AS contexts or the user terminals that can pre-recover AS connections.

[0355] Further, determining the user terminal that can create a new AS context or the user terminal that can pre-recover an AS connection includes:

[0356] The user terminals that can create a new AS context or pre-recovery of AS connection are determined based on the list of user terminals that can create a new AS context or the list of user terminals that can pre-recovery of AS connection specified by the core network network element, or the list of user terminals that refuse to create a new AS context or pre-recovery of AS connection specified by the core network network element.

[0357] Furthermore, the pre-recovery of the AS connection at least includes: establishing a signaling bearer, a data bearer and AS security.

[0358] 2. The program instructions stored in the memory installed on the core network element are used to implement the following functions:

[0359] Receiving a decision request sent by the radio access network RAN ​​side, requesting the core network element to determine whether a user terminal in the terminal group can perform new AS context creation or AS connection pre-recovery;

[0360] The core network element makes a decision on the request and feeds back to the RAN a list of user terminals that are allowed and / or denied to create new AS contexts or pre-recovery of AS connections.

[0361] Furthermore, after the core network element makes a determination on the request, the following steps are also included:

[0362] Create a new non-access layer NAS context or pre-recover a core network connection for the user terminal;

[0363] The core network connection pre-restoration includes that the core network element restores the NAS connection and S1 connection of the terminal according to the core network context of the user terminal saved in advance, wherein the S1 connection refers to the connection between the core network and the RAN.

[0364] Furthermore, the decision request includes an ID list of user terminals to be decided, or a group ID of a preset terminal group to which the user terminal to be decided belongs.

[0365] Further, the core network connection pre-recovery also includes:

[0366] Saving the core network context of the previous core network connection of all user terminals in a preset terminal group in groups, or selecting the core network context of the previous core network connection of a user terminal B in the terminal group to save, and using the common part of the core network context storage of the user terminal B as the common part of the core network context storage of all user terminals in the terminal group;

[0367] Allocating a corresponding terminal group recovery ID for the core network context storage, or allocating a corresponding user terminal recovery ID for each user terminal in the terminal group;

[0368] When the user terminal B establishes a core network connection again, receiving a recovery ID of the terminal group or a recovery ID of the user terminal B sent by the user terminal B or the RAN;

[0369] According to the recovery ID of the terminal group or the recovery ID of the user terminal B, the core network context storage corresponding to the user terminal B is queried, and the core network connection of the user terminal B is established according to the stored core network context.

[0370] In the above embodiment, the types of access network elements include, in addition to eNB, small cells, home base stations, 5G new RAT and other access network element types compatible with the EPC architecture.

[0371] In addition to MME, core network elements also include C-SGN, NBIoT MME and other core network elements that support machine type communication and mobility management.

[0372] It should be understood by those skilled in the art that the modules or steps of the present invention described above can be implemented by a general-purpose computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, and optionally, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present invention is not limited to any specific combination of hardware and software.

[0373] The above description is only a preferred embodiment of the present invention and is not intended to limit the scope of protection of the present invention. According to the content of the invention of the present invention, there may be other various embodiments. Without departing from the spirit and essence of the present invention, those skilled in the art can make various corresponding changes and deformations according to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention. Although the preferred embodiments of the present invention have been disclosed for illustrative purposes, those skilled in the art will realize that various improvements, additions and substitutions are also possible. Therefore, the scope of the present invention should not be limited to the above embodiments.

Claims

1. A connection establishment method, characterized in that: Upon receiving a connection request initiated by user terminal B, the access network element determines the terminal group to which the user terminal B belongs; The access network element determines, in the terminal group, a user terminal that can be subjected to connection preprocessing; The access network element performs connection preprocessing on the determined user terminal; The user terminal capable of connection preprocessing is: A user terminal capable of creating a new access layer AS context; or User terminals capable of AS connection pre-recovery; Determining the user terminal that can create a new AS context or the user terminal that can pre-recover an AS connection includes: The user terminals that can create a new AS context or pre-recovery of AS connection are determined based on the list of user terminals that can create a new AS context or the list of user terminals that can pre-recovery of AS connection specified by the core network network element, or the list of user terminals that refuse to create a new AS context or pre-recovery of AS connection specified by the core network network element.

2. The connection establishment method according to claim 1, characterized in that: Perform connection preprocessing on the determined user terminal, including: Pre-restoring the AS connection of the user terminal determined to be capable of AS connection pre-restoration according to the pre-stored AS context of the user terminal in the terminal group; or, An AS context is established for the user terminal capable of creating a new AS context according to the group information of the terminal group and / or the information of the user terminals in the terminal group.

3. The connection establishment method according to claim 1, characterized in that: The connection request initiated by the user terminal B is: a connection establishment request, a connection recovery request or a data transmission request.

4. The connection establishment method according to claim 1, characterized in that: After receiving the connection request initiated by the user terminal B, the access network element determines that the user terminal B belongs to the terminal group, including: When the user terminal B uses a physical random access channel PRACH resource pre-allocated specifically for the terminal group, it is determined that the user terminal B is a user terminal in the terminal group; or, According to the ID uploaded by the user terminal B or the group ID of the group to which the user terminal B belongs, it is determined that the user terminal B is a user terminal in the terminal group.

5. The connection establishment method according to claim 1, characterized in that: Determining a user terminal that can perform connection preprocessing in the terminal group includes: Sending a request to a core network element to request the core network element to determine a user terminal in the terminal group that can perform connection preprocessing; the request includes the IDs of all user terminals in the terminal group except user terminal B, the ID of the terminal group, or only the ID of user terminal B; According to the confirmation indication fed back by the core network element, the user terminals in the terminal group that are determined to be capable of connection preprocessing are obtained.

6. The connection establishment method according to claim 2, characterized in that: Establishing an AS context includes: Using the public part of the AS context of the user terminal B as the public part of the AS context of the target user terminal to establish the AS context; or, Preset an AS context, and use the common part in the preset AS context as the common part of the AS context of the target user terminal for which the AS context is to be established; The dedicated part of the AS context of the target user terminal is established by negotiation between the target user terminal and the network side.

7. The connection establishment method according to claim 2, characterized in that: The pre-restoration AS connection includes: Saving the AS context of the last AS connection of all user terminals in the terminal group; Allocating a terminal group recovery ID to the terminal group, or allocating a corresponding recovery ID to each user terminal in the terminal group; When establishing the pre-recovery AS connection, the AS context corresponding to the received recovery ID of the terminal group or the recovery ID of the user terminal is searched; and the AS connection is pre-recovered according to the AS context.

8. The connection establishment method according to claim 2, characterized in that: The pre-restoration AS connection includes: Saving the AS context of the last AS connection of the user terminal B, and storing the common part of the AS context as the common part of the AS context of all user terminals in the terminal group; Allocating a terminal group recovery ID to the terminal group, or allocating a corresponding recovery ID to each user terminal in the terminal group; When establishing the pre-recovery AS connection, the AS context corresponding to the received recovery ID of the terminal group or the recovery ID of the user terminal is searched; and the AS connection is pre-recovered according to the AS context.

9. The connection establishment method according to claim 1, characterized in that: Determining the user terminal that can create a new AS context or the user terminal that can pre-recover an AS connection includes: For user terminals in the terminal group, user terminals that concentratedly initiated connection requests or connection recovery requests in the previous terminal group, or user terminals that continuously initiated connection requests or connection recovery requests more than a set threshold, are determined as user terminals that can create new AS contexts or user terminals that can pre-recover AS connections.

10. The connection establishment method according to claim 1, characterized in that: Determining the user terminal that can create a new AS context or the user terminal that can pre-recover an AS connection includes: The user terminals in the terminal group that match the data cycle and data transmission time offset of the user terminal B are determined as the user terminals that can create new AS contexts or the user terminals that can pre-recover AS connections.

11. The connection establishment method according to claim 1, characterized in that: The pre-recovery of the AS connection at least includes: establishing a signaling bearer, a data bearer and AS security.

12. A connection establishment method, characterized in that: include: The core network element receives a decision request sent by the access network element, requesting the core network element to determine whether a user terminal in the terminal group can perform new AS context creation or AS connection pre-recovery; The core network element makes a decision on the request and feeds back to the access network element a list of user terminals that are allowed and / or denied to create new AS contexts or pre-recover AS connections; The access network element is used to determine a user terminal in the terminal group that can perform connection preprocessing; The user terminal capable of connection preprocessing is: A user terminal capable of creating a new access layer AS context; or User terminals capable of AS connection pre-recovery; The access network element determines the user terminal that can create a new AS context or the user terminal that can pre-recover an AS connection, including: The user terminals that can create a new AS context or pre-recovery of AS connection are determined based on the list of user terminals that can create a new AS context or the list of user terminals that can pre-recovery of AS connection specified by the core network network element, or the list of user terminals that refuse to create a new AS context or pre-recovery of AS connection specified by the core network network element.

13. The connection establishment method according to claim 12, characterized in that: After the core network element makes a decision on the request, it also includes: Create a new non-access layer NAS context or pre-recover a core network connection for the user terminal; The core network connection pre-recovery includes that the core network network element recovers the NAS connection and S1 connection of the terminal according to the core network context of the user terminal saved in advance, wherein the S1 connection refers to the connection between the core network and the access network element.

14. The connection establishment method according to claim 12, characterized in that: The decision request includes an ID list of user terminals to be decided, or a group ID of a preset terminal group to which the user terminal to be decided belongs.

15. The connection establishment method according to claim 13, characterized in that: The core network connection pre-recovery also includes: Saving the core network context of the previous core network connection of all user terminals in a preset terminal group in groups, or selecting the core network context of the previous core network connection of a user terminal B in the terminal group to save, and using the common part of the core network context storage of the user terminal B as the common part of the core network context storage of all user terminals in the terminal group; Allocating a corresponding terminal group recovery ID for the core network context storage, or allocating a corresponding user terminal recovery ID for each user terminal in the terminal group; When the user terminal B establishes a core network connection again, receiving a recovery ID of the terminal group or a recovery ID of the user terminal B sent by the user terminal B or the access network element; According to the recovery ID of the terminal group or the recovery ID of the user terminal B, the core network context storage corresponding to the user terminal B is queried, and the core network connection of the user terminal B is established according to the stored core network context.

16. A storage medium, characterized in that: The storage medium stores program instructions, and the program instructions are configured to: After receiving a connection request initiated by user terminal B, determining the terminal group to which the user terminal B belongs; Determining a user terminal in the terminal group that can perform connection preprocessing; Performing connection preprocessing on the determined user terminal; The user terminal capable of connection preprocessing is: A user terminal that can create a new AS access layer context; or, User terminals capable of AS connection pre-recovery; Wherein, determining the user terminal that can create a new AS context or the user terminal that can pre-recover an AS connection includes: The user terminals that can create a new AS context or pre-recovery of AS connection are determined based on the list of user terminals that can create a new AS context or the list of user terminals that can pre-recovery of AS connection specified by the core network network element, or the list of user terminals that refuse to create a new AS context or pre-recovery of AS connection specified by the core network network element.

17. The storage medium according to claim 16, wherein: Perform connection preprocessing on the determined user terminal, including: Pre-restoring the AS connection of the user terminal determined to be capable of AS connection pre-restoration according to the pre-stored AS context of the user terminal in the terminal group; or, An AS context is established for the user terminal capable of creating a new AS context according to the group information of the terminal group and / or the information of the user terminals in the terminal group.

18. The storage medium according to claim 17, wherein: Establishing an AS context includes: Using the public part of the AS context of the user terminal B as the public part of the AS context of the target user terminal to establish the AS context; or, Preset an AS context, and use the common part in the preset AS context as the common part of the AS context of the target user terminal for which the AS context is to be established; The dedicated part of the AS context of the target user terminal is established by negotiation between the target user terminal and the network side.

19. The storage medium according to claim 17, wherein: The pre-restoration AS connection includes: Saving the AS context of the last AS connection of all user terminals in the terminal group; Allocating a terminal group recovery ID to the terminal group, or allocating a corresponding recovery ID to each user terminal in the terminal group; When establishing the pre-recovery AS connection, the AS context corresponding to the received recovery ID of the terminal group or the recovery ID of the user terminal is searched; and the AS connection is pre-recovered according to the AS context.

20. The storage medium according to claim 17, wherein: The pre-restoration AS connection includes: Saving the AS context of the last AS connection of the user terminal B, and storing the common part of the AS context as the common part of the AS context of all user terminals in the terminal group; Allocating a terminal group recovery ID to the terminal group, or allocating a corresponding recovery ID to each user terminal in the terminal group; When establishing the pre-recovery AS connection, the AS context corresponding to the received recovery ID of the terminal group or the recovery ID of the user terminal is searched; and the AS connection is pre-recovered according to the AS context.

21. A storage medium, characterized in that: The storage medium stores program instructions, and the program instructions are configured to: Receiving a decision request sent by the access network element side, requesting the core network element to determine whether a user terminal in the terminal group can perform new AS context creation or AS connection pre-recovery; Make a decision on the request and feedback to the access network element a list of user terminals that are allowed and / or denied to create new AS contexts or pre-recovery of AS connections; The access network element is used to determine a user terminal in the terminal group that can perform connection preprocessing; The user terminal capable of connection preprocessing is: A user terminal capable of creating a new access layer AS context; or User terminals capable of AS connection pre-recovery; The access network element determines the user terminal that can create a new AS context or the user terminal that can pre-recover an AS connection, including: The user terminals that can create a new AS context or pre-recovery of AS connection are determined based on the list of user terminals that can create a new AS context or the list of user terminals that can pre-recovery of AS connection specified by the core network network element, or the list of user terminals that refuse to create a new AS context or pre-recovery of AS connection specified by the core network network element.

22. The storage medium according to claim 21, wherein After making a decision on the decision request, it also includes: Create a new non-access layer NAS context or pre-recover a core network connection for the user terminal; The core network connection pre-restoration includes restoring the NAS connection and S1 connection of the terminal according to the core network context of the user terminal saved in advance, wherein the S1 connection refers to the connection between the core network and the access network elements.

23. The storage medium according to claim 21, wherein The decision request includes an ID list of user terminals to be decided, or a group ID of a preset terminal group to which the user terminal to be decided belongs.

24. The storage medium according to claim 22, wherein: The core network connection pre-recovery also includes: Saving the core network context of the previous core network connection of all user terminals in a preset terminal group in groups, or selecting the core network context of the previous core network connection of a user terminal B in the terminal group to save, and using the common part of the core network context storage of the user terminal B as the common part of the core network context storage of all user terminals in the terminal group; Allocating a corresponding terminal group recovery ID for the core network context storage, or allocating a corresponding user terminal recovery ID for each user terminal in the terminal group; When the user terminal B establishes a core network connection again, receiving a recovery ID of the terminal group or a recovery ID of the user terminal B sent by the user terminal B or the access network element; According to the recovery ID of the terminal group or the recovery ID of the user terminal B, the core network context storage corresponding to the user terminal B is queried, and the core network connection of the user terminal B is established according to the stored core network context.

25. An access network element, comprising a processor and a memory, characterized in that: The memory stores program instructions, and the processor performs the following operations by calling the program instructions in the memory: After receiving a connection request initiated by user terminal B, determining the terminal group to which the user terminal B belongs; Determining a user terminal in the terminal group that can perform connection preprocessing; Performing connection preprocessing on the determined user terminal; The user terminal capable of connection preprocessing is: A user terminal capable of creating a new access layer AS context; or User terminals capable of AS connection pre-recovery; Determining the user terminal that can create a new AS context or the user terminal that can pre-recover an AS connection includes: The user terminals that can create a new AS context or pre-recovery of AS connection are determined based on the list of user terminals that can create a new AS context or the list of user terminals that can pre-recovery of AS connection specified by the core network network element, or the list of user terminals that refuse to create a new AS context or pre-recovery of AS connection specified by the core network network element.

26. The access network element according to claim 25, characterized in that: Perform connection preprocessing on the determined user terminal, including: Pre-restoring the AS connection of the user terminal determined to be capable of AS connection pre-restoration according to the pre-stored AS context of the user terminal in the terminal group; or, An AS context is established for the user terminal capable of creating a new AS context according to the group information of the terminal group and / or the information of the user terminals in the terminal group.

27. The access network element according to claim 26, characterized in that: Establishing an AS context includes: Using the public part of the AS context of the user terminal B as the public part of the AS context of the target user terminal to establish the AS context; or, Preset an AS context, and use the common part in the preset AS context as the common part of the AS context of the target user terminal for which the AS context is to be established; The dedicated part of the AS context of the target user terminal is established by negotiation between the target user terminal and the network side.

28. The access network element according to claim 26, characterized in that: The pre-restoration AS connection includes: Saving the AS context of the last AS connection of all user terminals in the terminal group; Allocating a terminal group recovery ID to the terminal group, or allocating a corresponding recovery ID to each user terminal in the terminal group; When establishing the pre-recovery AS connection, the AS context corresponding to the received recovery ID of the terminal group or the recovery ID of the user terminal is searched; and the AS connection is pre-recovered according to the AS context.

29. The access network element according to claim 26, characterized in that: The pre-restoration AS connection includes: Saving the AS context of the last AS connection of the user terminal B, and storing the common part of the AS context as the common part of the AS context of all user terminals in the terminal group; Allocating a terminal group recovery ID to the terminal group, or allocating a corresponding recovery ID to each user terminal in the terminal group; When establishing the pre-recovery AS connection, the AS context corresponding to the received recovery ID of the terminal group or the recovery ID of the user terminal is searched; and the AS connection is pre-recovered according to the AS context.

30. The access network element according to claim 25, characterized in that: The pre-recovery of the AS connection at least includes: establishing a signaling bearer, a data bearer and AS security.

31. A core network element, comprising a processor and a memory, characterized in that: The memory stores program instructions, and the processor performs the following operations by calling the program instructions in the memory: Receiving a decision request sent by a wireless access network, requesting a core network element to determine whether a user terminal in a terminal group can perform a new AS context or a pre-recovery of an AS connection; Make a decision on the request and feedback to the access network element a list of user terminals that are allowed and / or denied to create new AS contexts or pre-recovery of AS connections; The access network element is used to determine a user terminal in the terminal group that can perform connection preprocessing; The user terminal capable of connection preprocessing is: A user terminal capable of creating a new access layer AS context; or User terminals capable of AS connection pre-recovery; The access network element determines the user terminal that can create a new AS context or the user terminal that can pre-recover an AS connection, including: The user terminals that can create a new AS context or pre-recovery of AS connection are determined based on the list of user terminals that can create a new AS context or the list of user terminals that can pre-recovery of AS connection specified by the core network network element, or the list of user terminals that refuse to create a new AS context or pre-recovery of AS connection specified by the core network network element.

32. The core network element according to claim 31, characterized in that: After making a decision on the decision request, it also includes: Create a new non-access layer NAS context or pre-recover a core network connection for the user terminal; The core network connection pre-restoration includes restoring the NAS connection and S1 connection of the terminal according to the core network context of the user terminal saved in advance, wherein the S1 connection refers to the connection between the core network and the access network elements.

33. The core network element according to claim 31, characterized in that: The core network connection pre-recovery also includes: Saving the core network context of the previous core network connection of all user terminals in a preset terminal group in groups, or selecting the core network context of the previous core network connection of a user terminal B in the terminal group to save, and using the common part of the core network context storage of the user terminal B as the common part of the core network context storage of all user terminals in the terminal group; Allocating a corresponding terminal group recovery ID for the core network context storage, or allocating a corresponding user terminal recovery ID for each user terminal in the terminal group; When the user terminal B establishes a core network connection again, receiving a recovery ID of the terminal group or a recovery ID of the user terminal B sent by the user terminal B or the access network element; According to the recovery ID of the terminal group or the recovery ID of the user terminal B, the core network context storage corresponding to the user terminal B is queried, and the core network connection of the user terminal B is established according to the stored core network context.

34. A system, characterized in that: It comprises the access network element as described in any one of claims 25 to 30, the core network element as described in any one of claims 31 to 33, and a user terminal.