WO2019019990A1 - 连接建立方法、网元、存储介质及系统 - Google Patents

连接建立方法、网元、存储介质及系统 Download PDF

Info

Publication number
WO2019019990A1
WO2019019990A1 PCT/CN2018/096751 CN2018096751W WO2019019990A1 WO 2019019990 A1 WO2019019990 A1 WO 2019019990A1 CN 2018096751 W CN2018096751 W CN 2018096751W WO 2019019990 A1 WO2019019990 A1 WO 2019019990A1
Authority
WO
WIPO (PCT)
Prior art keywords
user terminal
connection
context
terminal
core network
Prior art date
Application number
PCT/CN2018/096751
Other languages
English (en)
French (fr)
Inventor
戴谦
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2019019990A1 publication Critical patent/WO2019019990A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management

Definitions

  • the present disclosure relates to the field of communication technologies, for example, to a connection establishment method, a storage medium, a network element, and a system.
  • IoT devices Low cost, small bandwidth, and small data are typical features of IoT devices. Such devices have a short duration of access to the network and a small amount of data to be transmitted, but the amount of equipment is very large. Each time the device establishes a connection with the wireless communication network, it will result in control plane signaling of a large number of air interfaces and control plane signaling overhead on the ground side, which is consumed by the establishment process of the context on the radio access network (RAN) side. Control plane signaling is dominant. However, compared with the amount of data transmitted by the device, there is a case where the control plane signaling overhead is greater than the user plane data amount, which results in low system transmission efficiency.
  • RAN radio access network
  • the 3rd Generation Partnership Project (3GPP) is currently enhancing machine-type communication (MTC), Narrow Band Intemet of Things (NBIOT), and fifth-generation mobile communications.
  • MTC machine-type communication
  • NBIOT Narrow Band Intemet of Things
  • 5G new RAT access technology
  • how to reduce the control plane signaling overhead cost brought by massive access is one of the research directions.
  • LTE Long Term Evolution
  • 5G new RAT 5G new RAT
  • RRC Radio Resource Control
  • the difference from the RRC connection state is that the terminal and the RAN need to save the terminal context, the mobility of the terminal adopts the cell reselection mode, and the terminal monitors the paging of the RAN and the core network (Core Network, CN).
  • the core network Core Network, CN
  • the present disclosure provides a connection establishment method, a storage medium, a network element, and a system to solve the problem that the signaling overhead cost of the related art control plane is high.
  • connection establishment method including:
  • the access network element determines a terminal group to which the user terminal that initiates the connection request belongs;
  • the access network element determines a target user terminal that performs connection pre-processing in the terminal group
  • the access network element performs the connection pre-processing on the determined target user terminal.
  • the disclosure further provides a connection establishment method, including:
  • the core network element receives the decision request sent by the access network element, where the decision request is used to request the core network element to determine whether the user terminal to be determined in the terminal group can perform connection preprocessing;
  • the core network element determines the decision request, and feeds back the determination result to the access network element, where the determination result includes at least one of the following: a list of user terminals that are allowed to perform connection pre-processing and refuse to connect. A list of pre-processed user terminals.
  • the present disclosure further provides a computer readable storage medium having program instructions stored therein, the program instructions being configured to implement a connection establishment method on an access network element side.
  • the present disclosure further provides a computer readable storage medium having program instructions stored therein, the program instructions being configured to implement a connection establishment method on a core network side of a core network.
  • the present disclosure further provides an access network element, including a processor and a memory, where the program stores program instructions, and the processor calls the program instruction in the memory, the program The connection establishment method of the access network element side is performed when the instruction is running.
  • the present disclosure further provides a core network element, including a processor and a memory, where the program stores program instructions, and the processor calls the program instruction in the memory by using the program instruction.
  • the connection establishment method of the core network side of the core network is executed during operation.
  • the present disclosure further provides a system, including the foregoing access network element, core network element, and user terminal.
  • FIG. 1 is a flowchart of a connection establishment method according to an embodiment of the present disclosure
  • FIG. 2 is a flowchart of another method for establishing a connection according to an embodiment of the present disclosure
  • FIG. 3 is a flowchart of a method for establishing a multi-terminal connection based on a group form in an open embodiment
  • FIG. 4 is a flowchart of a connection establishment method in an LTE system according to an embodiment of the present disclosure.
  • the present disclosure groups user terminals.
  • 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 filtered and identified, and the selection may be performed.
  • the user terminal performing the connection pre-processing performs pre-connection processing on the access network side and the core network side for the selected user terminal. In this way, when the user terminal that has established the pre-connection process initiates the connection request again, the connection is directly established by using the pre-connected information, so that the RRC connection is quickly established or restored, and the overhead cost of the control plane signaling is effectively reduced.
  • the core network element receives the decision request sent by the access network element RAN side.
  • the core network element is requested to determine whether the user terminal in the terminal group can perform AS context creation or AS connection pre-recovery; the core network element determines the request, and feeds back to the RAN to allow and/or refuse to perform AS context new establishment. Or the AS connects to the list of pre-recovered user terminals.
  • the pre-connection process on the base station side includes: pre-restoring the AS connection to the user terminal that determines that the AS connection pre-recovery is performed according to the AS context of the user terminal in the pre-stored terminal group; or, according to the group information of the terminal group and/or the The information of the user terminal in the terminal group establishes an AS context for the user terminal that can perform the AS context creation.
  • the pre-connection processing on the core network side includes: performing a non-access stratum (NAS) context creation or a core network connection pre-recovery for the user terminal; wherein the core network connection pre-recovery includes, the core network element is based on The core network context of the user terminal saved in advance restores the NAS connection and the S1 connection of the terminal, wherein the S1 connection refers to the connection between the core network and the RAN.
  • NAS non-access stratum
  • the access network element determines the terminal group to which the user terminal (e.g., mobile terminal B) that initiated the connection request belongs.
  • the access network element determines a target user terminal that performs connection pre-processing in the terminal group.
  • the access network element performs the connection pre-processing on the determined target user terminal.
  • the target user terminal that performs connection preprocessing is:
  • determining a target user terminal for performing connection pre-processing includes one of the following:
  • the user terminal that continuously initiates the connection request for more than the set threshold determines the target user terminal that is newly created by the AS context or the target user terminal that performs the AS connection pre-recovery.
  • the determining a target user terminal for performing connection pre-processing includes:
  • the user terminal in the terminal group that matches the data period of the user terminal and the data transmission time offset is determined as the target user terminal that performs the AS context creation or the target user terminal that performs the AS connection pre-recovery.
  • determining a target user terminal for performing connection pre-processing includes one of the following:
  • the access network element determines a target user terminal that performs connection pre-processing in the terminal group, including:
  • establishing an AS context for the target user terminal includes:
  • the access network element negotiates with the target user terminal to establish a proprietary portion of the AS context of the target user terminal.
  • pre-restoring the AS connection to the target user terminal includes:
  • pre-restoring the AS connection to the target user terminal includes:
  • the terminal group recovery identifier ID corresponds to all user terminals in the terminal group; when the AS connection is pre-recovered, the terminal group recovery identifier ID is used to search for Recovering, by the terminal group, a public part of an AS context of all user terminals corresponding to the identifier ID;
  • performing the connection pre-processing on the determined target user terminal includes:
  • the target user terminal that performs the connection pre-processing is the target user terminal that performs the pre-recovery of the AS connection
  • the AS is pre-restored to the target user terminal according to the AS context of the target user terminal in the terminal group stored in advance. connection;
  • the AS context is established for the target user terminal according to at least one piece of information: the group information of the terminal group and the terminal. Information about user terminals within the group.
  • the core network element receives the decision request sent by the access network element, where the decision request is used to request the core network element to determine whether the user terminal to be determined in the terminal group can connect. Pretreatment.
  • the core network element determines the decision request, and feeds back the determination result to the access network element, where the determination result includes at least one of the following: a list of user terminals that are allowed to perform connection pre-processing and refuse to connect. A list of pre-processed user terminals.
  • the core network element determines whether the user terminal to be determined in the terminal group can perform connection preprocessing, including:
  • the core network element determines whether the user terminal in the terminal group can perform the access layer AS context creation or the access layer AS connection pre-recovery;
  • a list of user terminals that are allowed to perform connection pre-processing including one of: a list of user terminals that allow AS context creation, and a list of user terminals that allow AS connection pre-recovery;
  • a list of user terminals that refuse to perform connection pre-processing including one of the following: a list of user terminals that refuse to perform AS context creation and a list of user terminals that refuse to perform AS connection pre-recovery.
  • the method further includes:
  • the non-access stratum NAS context is newly created for the user terminal in the list;
  • the core network connection pre-recovery includes: the core network element is based on The core network context of the pre-saved user terminal restores the NAS connection and the S1 connection of the user terminal, wherein the S1 connection is a connection between the core network element and the access network element.
  • the decision request includes a list of identifier IDs of the user terminal to be determined, or a group identifier ID of the terminal group to which the user terminal to be determined belongs.
  • the core network connection pre-recovery further includes:
  • the core network context of the last core network connection of all user terminals of the terminal group is saved in units of groups, or the core network context of the last core network connection of the user terminal initiating the connection request in the terminal group is saved. And treating the public part of the core network context storage of the user terminal that initiates the connection request as a common part of the core network context storage of all user terminals of the terminal group;
  • terminal group recovery identifier ID corresponds to all user terminals in the terminal group
  • the core network context of the last core network connection of all user terminals of the terminal group is saved in units of groups, or the core network context of the last core network connection of the user terminal that initiated the connection request in the terminal group is selected. Saving, and treating the public part of the core network context storage of the user terminal that initiates the connection request as a common part of the core network context storage of all user terminals in the terminal group;
  • the embodiment is related to a method for establishing a connection, and the method is applied to the network element side of the access network.
  • the method includes:
  • the access network element determines a terminal group to which the user terminal that initiates the connection request belongs.
  • the access network element determines a target user terminal that performs connection pre-processing in the terminal group.
  • the access network element performs the connection pre-processing on the determined target user terminal.
  • the access network element After receiving the connection request initiated by the user terminal B, the access network element first determines the terminal group to which the user terminal B belongs; then determines the user terminal that can perform connection pre-processing in the terminal group; and finally performs the determined user terminal. Connection preprocessing.
  • determining the terminal group to which the user terminal B belongs may adopt any of the following solutions:
  • the user terminal B When the user terminal B pre-allocates a dedicated physical random access channel (PRACH) resource for the terminal group, it is determined that the user terminal B is the user terminal in the terminal group; or
  • PRACH dedicated physical random access channel
  • the user terminal B is determined to be the user terminal in the terminal group according to the ID of the user terminal B uploaded by the user terminal B or the group ID of the terminal group to which the user terminal B belongs.
  • connection request initiated by the user terminal B may be a connection establishment request, a connection recovery request, or a data transmission request.
  • the user terminal that can perform connection pre-processing is: a user terminal that can be newly created in the access layer AS context; or a user terminal that can perform AS connection pre-recovery.
  • the pre-recovery of the AS connection includes at least: establishing signaling bearer, data bearer, and AS security.
  • the user terminal that can perform pre-recovery of the AS connection refers to: a user terminal that stores an AS context in advance on both the network side and the terminal side;
  • a user terminal that can be newly created in the AS access layer context refers to a user terminal that does not store an AS context on the network side and the terminal side.
  • the user terminal that can be newly created in the AS context or the pre-recovered user terminal that can perform the AS connection includes:
  • the user terminal that initially initiates the connection request or the connection recovery request in the previous terminal group, or the user terminal that continuously initiates the connection request or the connection recovery request exceeds the set threshold is determined to be operable.
  • the list of user terminals of the restored user terminal determines a user terminal that can be newly created by the AS context or a pre-recovered user terminal that can perform AS connection.
  • the user terminal that can perform connection pre-processing in the terminal group includes:
  • the user terminal in the terminal group that can determine the connection pre-processing is obtained.
  • the public part in the AS context of the user terminal B is used as the common part of the AS context of the target user terminal to be established in the AS context; or, an AS context is preset, and the public part in the preset AS context is used as the AS context to be established.
  • the public part of the AS context of the target user terminal; the proprietary part of the AS context of the target user terminal is established by the target user terminal in consultation with the network side.
  • the pre-recovery AS connection includes:
  • the AS context of the last AS connection of all the user terminals in the terminal group is saved; the terminal group recovery ID is assigned to the terminal group, or the corresponding recovery ID is assigned to each user terminal in the terminal group; when the pre-recovery AS connection is established, Finding an AS context corresponding thereto according to the recovery ID of the received terminal group or the recovery ID of the user terminal; pre-restoring the AS connection according to the AS context; or
  • the AS context of the last AS connection of the user terminal B is saved, and the common part of the AS context is stored as a common part of the AS context of all user terminals in the terminal group; the terminal group recovery ID is assigned to the terminal group, or is in the terminal group Each user terminal is assigned a corresponding recovery ID; when a pre-recovery AS connection is established, the AS context corresponding thereto is found according to the recovery ID of the received terminal group or the recovery ID of the user terminal; and the AS connection is pre-restored according to the AS context.
  • connection pre-processing is performed on the determined user terminal, which is:
  • Determining an AS connection by determining a user terminal that can perform AS connection pre-recovery according to an AS context of the user terminal in the terminal group stored in advance; or, according to the group information of the terminal group and/or the information of the user terminal in the terminal group, The user terminal that performs the new AS context establishes an AS context.
  • the embodiment relates to a storage medium, where the program instruction is used to implement the technical solution of the first embodiment, wherein the program instruction is used to implement the following functions:
  • the access network element After receiving the connection request initiated by the user terminal B, the access network element first determines the terminal group to which the user terminal B belongs; then determines the user terminal that can perform connection pre-processing in the terminal group; and finally performs the determined user terminal. Connection preprocessing.
  • determining the terminal group to which the user terminal B belongs may adopt any of the following solutions:
  • the user terminal B When the user terminal B pre-allocates a dedicated physical random access channel PRACH resource for the terminal group, it is determined that the user terminal B is the user terminal in the terminal group; or
  • the user terminal B is determined to be the user terminal in the terminal group according to the ID of the user terminal B uploaded by the user terminal B or the group ID of the group to which the user terminal B belongs.
  • connection request initiated by the user terminal B may be a connection establishment request, a connection recovery request, or a data transmission request.
  • the user terminal that can perform connection pre-processing is: a user terminal that can be newly created in the access layer AS context; or a user terminal that can perform AS connection pre-recovery.
  • the pre-recovery of the AS connection includes at least: establishing signaling bearer, data bearer, and AS security.
  • the user terminal that can be newly created in the AS context or the pre-recovered user terminal that can perform the AS connection includes:
  • the user terminal that initially initiates the connection request or the connection recovery request in the previous terminal group, or the user terminal that continuously initiates the connection request or the connection recovery request exceeds the set threshold is determined to be operable.
  • the list of user terminals of the restored user terminal determines a user terminal that can be newly created by the AS context or a pre-recovered user terminal that can perform AS connection.
  • the user terminal that can perform connection pre-processing in the terminal group includes:
  • the user terminal in the terminal group that can determine the connection pre-processing is obtained.
  • the public part in the AS context of the user terminal B is used as the common part of the AS context of the target user terminal to be established in the AS context; or, an AS context is preset, and the public part in the preset AS context is used as the AS context to be established.
  • the public part of the AS context of the target user terminal; the proprietary part of the AS context of the target user terminal is established by the target user terminal in consultation with the network side.
  • the pre-recovery AS connection includes:
  • the AS context of the last AS connection of all the user terminals in the terminal group is saved; the terminal group recovery ID is assigned to the terminal group, or the corresponding recovery ID is assigned to each user terminal in the terminal group; when the pre-recovery AS connection is established, Finding an AS context corresponding thereto according to the recovery ID of the received terminal group or the recovery ID of the user terminal; pre-restoring the AS connection according to the AS context; or
  • the AS context of the last AS connection of the user terminal B is saved, and the common part of the AS context is stored as a common part of the AS context of all user terminals in the terminal group; the terminal group recovery ID is assigned to the terminal group, or is in the terminal group Each user terminal is assigned a corresponding recovery ID; when a pre-recovery AS connection is established, the AS context corresponding thereto is found according to the recovery ID of the received terminal group or the recovery ID of the user terminal; and the AS connection is pre-restored according to the AS context.
  • connection pre-processing is performed on the determined user terminal, which is:
  • Determining an AS connection by determining a user terminal that can perform AS connection pre-recovery according to an AS context of the user terminal in the terminal group stored in advance; or, according to the group information of the terminal group and/or the information of the user terminal in the terminal group, The user terminal that performs the new AS context establishes an AS context.
  • the embodiment relates to an access network element, including a processor and a memory.
  • the processor stores program instructions.
  • the processor implements the technical solution of the first embodiment by calling a program instruction stored in the memory. , wherein the program instruction is used to implement the following functions:
  • the access network element After receiving the connection request initiated by the user terminal B, the access network element first determines the terminal group to which the user terminal B belongs; then determines the user terminal that can perform connection pre-processing in the terminal group; and finally performs the determined user terminal. Connection preprocessing.
  • determining the terminal group to which the user terminal B belongs may adopt any of the following solutions:
  • the user terminal B When the user terminal B pre-allocates a dedicated physical random access channel PRACH resource for the terminal group, it is determined that the user terminal B is the user terminal in the terminal group; or
  • the user terminal B is determined to be the user terminal in the terminal group according to the ID uploaded by the user terminal B or the group ID of the group to which it belongs.
  • connection request initiated by the user terminal B may be a connection establishment request, a connection recovery request, or a data transmission request.
  • the user terminal that can perform connection pre-processing is: a user terminal that can be newly created in the access layer AS context; or a user terminal that can perform AS connection pre-recovery.
  • the pre-recovery of the AS connection includes at least: establishing signaling bearer, data bearer, and AS security.
  • the user terminal that can be newly created in the AS context or the pre-recovered user terminal that can perform the AS connection includes:
  • the user terminal that initially initiates the connection request or the connection recovery request in the previous terminal group, or the user terminal that continuously initiates the connection request or the connection recovery request exceeds the set threshold is determined to be operable.
  • the list of user terminals of the restored user terminal determines a user terminal that can be newly created by the AS context or a pre-recovered user terminal that can perform AS connection.
  • the user terminal that can perform connection pre-processing in the terminal group includes:
  • the user terminal in the terminal group that can determine the connection pre-processing is obtained.
  • the public part in the AS context of the user terminal B is used as the common part of the AS context of the target user terminal to be established in the AS context; or, an AS context is preset, and the public part in the preset AS context is used as the AS context to be established.
  • the public part of the AS context of the target user terminal; the proprietary part of the AS context of the target user terminal is established by the target user terminal in consultation with the network side.
  • the pre-recovery AS connection includes:
  • the AS context of the last AS connection of all the user terminals in the terminal group is saved; the terminal group recovery ID is assigned to the terminal group, or the corresponding recovery ID is assigned to each user terminal in the terminal group; when the pre-recovery AS connection is established, Finding an AS context corresponding thereto according to the recovery ID of the received terminal group or the recovery ID of the user terminal; pre-restoring the AS connection according to the AS context; or
  • the AS context of the last AS connection of the user terminal B is saved, and the common part of the AS context is stored as a common part of the AS context of all user terminals in the terminal group; the terminal group recovery ID is assigned to the terminal group, or is in the terminal group Each user terminal is assigned a corresponding recovery ID; when a pre-recovery AS connection is established, the AS context corresponding thereto is found according to the recovery ID of the received terminal group or the recovery ID of the user terminal; and the AS connection is pre-restored according to the AS context.
  • connection pre-processing is performed on the determined user terminal, which is:
  • Determining an AS connection by determining a user terminal that can perform AS connection pre-recovery according to an AS context of the user terminal in the terminal group stored in advance; or, according to the group information of the terminal group and/or the information of the user terminal in the terminal group, The user terminal that performs the new AS context establishes an AS context.
  • This embodiment relates to a method for establishing a connection, which is applied to a network element side of a core network.
  • the method includes:
  • the core network element receives the decision request sent by the access network element, where the decision request is used to request the core network element to determine whether the user terminal to be determined in the terminal group can perform connection preprocessing.
  • the core network element determines, according to the decision request, and feeds back a determination result to the access network element, where the determination result includes at least one of: a list of user terminals that allow connection pre-processing and a rejection A list of user terminals that perform connection pre-processing.
  • the core network element receives the decision request sent by the access network element, and requests the core network element to determine whether the user terminal in the terminal group can perform AS context creation or AS connection pre-recovery; wherein the decision request includes the user to be determined.
  • the core network element makes a decision for the request and feeds back to the access network element a list of user terminals that allow and/or reject AS context creation or AS connection pre-recovery.
  • the method further includes:
  • the core network connection pre-recovery includes: the core network element recovers the NAS connection and the S1 connection of the terminal according to the core network context of the user terminal saved in advance, where the S1 connection refers to the connection between the core network and the access network element. .
  • the core network connection pre-recovery further includes:
  • the core network context of the previous core network connection of all user terminals of the preset terminal group is saved in units of groups, or the core network context of the previous core network connection of one user terminal B in the terminal group is selected. Saving, and treating the public part of the core network context storage of the user terminal B as a common part of the core network context storage of all user terminals of the terminal group;
  • the core network context storage corresponding to the user terminal B is queried according to the recovery ID of the terminal group or the recovery ID of the user terminal B, and the core network connection of the user terminal B is established according to the stored core network context.
  • the technical solution in this embodiment performs a non-access stratum NAS context creation or a core network connection pre-recovery for determining a user terminal that performs AS context creation or AS connection pre-recovery, so that when these terminals initiate a request, when the connection establishment request is initiated again,
  • the RRC connection can be quickly established or restored, and the overhead cost of control plane signaling is effectively reduced.
  • the embodiment relates to a storage medium, where the program instruction is used to implement the technical solution of the embodiment 4, wherein the program instruction is used to implement the following functions:
  • the core network element receives the decision request sent by the access network element, and requests the core network element to determine whether the user terminal in the terminal group can perform AS context creation or AS connection pre-recovery; wherein the decision request includes the user to be determined.
  • the core network element makes a decision for the request and feeds back to the access network element a list of user terminals that allow and/or reject AS context creation or AS connection pre-recovery.
  • the method further includes:
  • the core network connection pre-recovery includes: the core network element recovers the NAS connection and the S1 connection of the terminal according to the core network context of the user terminal saved in advance, where the S1 connection refers to the connection between the core network and the access network element. .
  • the core network connection pre-recovery further includes:
  • the core network context of the previous core network connection of all user terminals of the preset terminal group is saved in units of groups, or the core network context of the previous core network connection of one user terminal B in the terminal group is selected. Saving, and treating the public part of the core network context storage of the user terminal B as a common part of the core network context storage of all user terminals of the terminal group;
  • the core network context storage corresponding to the user terminal B is queried according to the recovery ID of the terminal group or the recovery ID of the user terminal B, and the core network connection of the user terminal B is established according to the stored core network context.
  • the technical solution in this embodiment performs a non-access stratum NAS context creation or a core network connection pre-recovery for determining a user terminal that performs AS context creation or AS connection pre-recovery, so that when these terminals initiate a request, when the connection establishment request is initiated again,
  • the RRC connection can be quickly established or restored, and the overhead cost of control plane signaling is effectively reduced.
  • the embodiment relates to a core network element, including a processor and a memory.
  • the processor stores program instructions.
  • the processor implements the technical solution of the fourth embodiment by calling a program instruction stored in the memory.
  • the program instructions are used to implement the following functions:
  • Receiving a decision request sent by the network element of the access network requesting the core network element to determine whether the user terminal in the terminal group can perform AS context creation or AS connection pre-recovery; wherein the decision request includes a list of IDs of the user terminal to be determined. Or the group ID of the preset terminal group to which the user terminal to be determined belongs.
  • the method further includes:
  • the core network connection pre-recovery includes: restoring the NAS connection and the S1 connection of the terminal according to a core network context of the user terminal saved in advance, where the S1 connection refers to a connection between the core network and the access network element.
  • the core network connection pre-recovery further includes:
  • the core network context of the previous core network connection of all user terminals of the preset terminal group is saved in units of groups, or the core network context of the previous core network connection of one user terminal B in the terminal group is selected. Saving, and treating the public part of the core network context storage of the user terminal B as a common part of the core network context storage of all user terminals of the terminal group;
  • the core network context storage corresponding to the user terminal B is queried according to the recovery ID of the terminal group or the recovery ID of the user terminal B, and the core network connection of the user terminal B is established according to the stored core network context.
  • the decision request includes a list of identifier IDs of the user terminal to be determined, or a group identifier ID of the terminal group to which the user terminal to be determined belongs.
  • the technical solution in this embodiment performs a non-access stratum NAS context creation or a core network connection pre-recovery for determining a user terminal that performs AS context creation or AS connection pre-recovery, so that when these terminals initiate a request, when the connection establishment request is initiated again,
  • the RRC connection can be quickly established or restored, and the overhead cost of control plane signaling is effectively reduced.
  • a terminal group A is pre-defined on the mobile network element mobility management entity (A-MME) side, and the terminal group A includes multiple terminal identifiers, for example, including ID of 10 terminals (such as Serving-Temporary Mobile Subscriber Identity (S-TMSI) or International Mobile Subscriber Identification Number (IMSI)), evolved base station of MME-A (Evolved)
  • S-TMSI Serving-Temporary Mobile Subscriber Identity
  • IMSI International Mobile Subscriber Identification Number
  • eNB The Node Base, eNB
  • the Node Base, eNB has obtained the information of the group A from the MME-A in advance, and the terminal B (assuming it belongs to a member of the terminal group A) initiates the calling procedure, and initiates an eNB (the base station of the LTE RAN) of the MME-A
  • the RRC connection setup procedure after 5 minutes, another member terminal D of group A initiates an RRC connection recovery procedure to the eNB.
  • This example is used to explain how the Radio Access Network (RAN) and MME prepare the AS connection and core network connection of multiple group members in advance in the form of a group in the process of creating a new network connection.
  • FIG. 3 only shows a process in which the terminal B establishes an RRC connection pre-recovery for other terminals in the group during the process of initiating the establishment of the RRC connection
  • the AS connection is a general term for the connection between the radio access network and the terminal, and the RRC connection belongs to For the connection of the AS, and the establishment process of the RRC connection by the terminal in the subsequent group, the process of establishing the RRC connection by the terminal B is not included in FIG. 3, and the terminal B does not establish the RRC connection, but is not shown in FIG. .
  • the connection request initiated by the user terminal B may be: a connection establishment request, a connection recovery request, or a data transmission.
  • the method for establishing a multi-terminal connection based on a group form includes:
  • Step 301 The terminal B initiates an RRC connection establishment process to the eNB, and reports the user equipment (User Equipment, UE) identification ID (S-TMSI) in the RRC connection setup request message.
  • the current RRC connection establishment cause is the primary data service. (Mobile Origination Call Data, MO-data);
  • Step 302 The eNB queries whether the terminal B belongs to a member of a certain group, and determines that it belongs to the group A according to its ID; the member terminal of the same group is defined by the RAN or the core network element, and the group ID is assigned, and the member terminal in the group should be
  • the same characteristics are as follows: the same service, the same service model, the same service class, the same terminal type, or the same Access Point Name (APN).
  • API Access Point Name
  • Step 303 The eNB determines whether to perform pre-recovery of the RRC connection for the other nine group member terminals remaining in the group A.
  • the RRC connection pre-recovery is necessary for the eNB to store the AS context of the terminal in advance, and the terminal without the storage context cannot Performing RRC connection pre-recovery, and determining which group member terminals perform RRC connection pre-recovery on the basis of satisfying the necessary conditions includes:
  • the group member X is considered to be an inactive member, and the RAN is not Pre-recovering the RRC connection for the member;
  • the RAN may determine whether the information is based on the information. To pre-recover the RRC connection for this member; it can be:
  • the connection is a personal burst behavior of the UE, and the RRC connection of other group members is not pre-recovered.
  • the members in the group have multiple data periods, it is determined that the data periods and data transmission time offsets of the group members are consistent with the UE currently initiating the connection, and the RRC connection of the matching group member may be pre-restored.
  • the eNB determines, according to the indications, the group member UE that can pre-recover the RRC connection; if the MME specifies the UE list that rejects the pre-recovery connection, the eNB The RRC pre-establishment or pre-recovery of the UE in the list is not performed.
  • connection establishment reason of the terminal B that initiated the connection process is the called (Mobile Terminal Call, MT call)
  • the RAN has not received the paging paging from the MME to the other group A member UEs, or has not received any
  • the group paging group paging of the MME considers that the MT call is only a separate service of the UE, and other group A members do not need to pre-recover the RRC connection together.
  • one method may be selected to assist the judgment, or two or three methods may be used in combination, wherein the method indicated by the MME has the highest priority. That is, if the eNB itself determines that there are 8 terminals that can perform RRC connection pre-recovery, but the MME indicates that only 5 of the terminals are allowed to perform RRC connection pre-recovery, the eNB must comply with the indication of the MME.
  • the eNB determines that 7 of the remaining 9 terminals perform RRC pre-recovery.
  • Step 304 The eNB sends the list of the seven terminals that can be RRC pre-recovered to the MME for review.
  • the eNB can carry the list through the existing signaling of the S1 interface, for example, by using the initial UE message Initial UE Message, or Define an S1 port signaling.
  • the S1 interface refers to an interface between an eNB and an MME. Note: If the eNB decides to perform RRC connection pre-recovery for all the remaining terminals of group A, it can send only the ID of group A to the MME.
  • Step 305 The MME checks whether the seven terminals can pre-recover the core network connection. Similarly, the prerequisite for the core network connection pre-recovery is that the MME stores the core network context of the corresponding terminal in advance, if the MME does not store the corresponding terminal in advance. In the core network context, the terminal cannot perform pre-recovery of the core network connection. On the basis of satisfying the necessary conditions, the method of the review may also refer to the method of step 303. Due to the difference between the eNB and the MME algorithm and the parameters, and the MME shall consider additional factors such as its own load, the MME may reject the partial terminal. Pre-established.
  • the MME allows only six terminals to pre-recover the core network connection, and the MME will allow the pre-recovery of the list of terminals connected to the core network to be fed back to the eNB, and the list can be carried through the existing signaling of the S1 interface, for example, through the initial context.
  • the MME starts pre-recovering the core network connection of the six terminals, that is, recovers the S1 interface control plane bearer, the S1 port user plane bearer, the NAS security context, and the like for each terminal according to the corresponding terminal context stored in advance by the MME.
  • Step 306 The eNB finally determines the terminal that can perform RRC pre-recovery according to the MME list, and performs RRC connection pre-recovery of the terminal according to the AS context of each terminal stored by the eNB, where the signaling bearer is separately established for each terminal. , data bearing, and AS security context.
  • the terminal that completes the RRC connection pre-recovery and the pre-recovery of the core network connection is in a light connection state from the perspective of the LTE network side; inactive state (inactive state) from the perspective of the 5G new RAT network, that is, the terminal Both the network side and the network side maintain the context of the terminal, and the mobility of the terminal adopts a cell reselection mode, and the terminal monitors the paging of the RAN and the core network.
  • Step 307 After 5 minutes, it is assumed that the member terminal D of the group A is to initiate a service, and then initiates an RRC connection setup procedure or an RRC connection recovery procedure to the eNB, and reports its own UE in the RRC connection setup request message or in the RRC connection recovery request message. ID, the reason for this RRC connection establishment is the primary data service (MO-data).
  • the 5 minutes is only an example, and may be other minutes.
  • Step 308 The eNB queries whether the terminal D has pre-recovered the RRC connection. If the RRC connection has been pre-recovered, the pre-recovered RRC connection context (or AS context) is directly used to configure the RRC connection parameter for the terminal D and deliver the RRC connection parameter. At the same time, the MME terminal D can be informed that the connection can be restored, and the notification information should include the ID of the terminal D, and the notification information can be carried in the existing S1 port signaling, or a new S1 port signaling can be established; if the RRC connection is not pre-recovered, The RRC connection is still established for the terminal according to the process of the normal new RRC connection.
  • the pre-recovered RRC connection context or AS context
  • Step 309 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.
  • the application scenario of this embodiment is the same as that of Embodiment 7, except that when determining the terminal list that can perform RRC connection pre-recovery, in addition to the final decision made by the MME according to Embodiment 7, the following method may be adopted:
  • the RAN does not perform step 303, but directly sends the user terminal list of group A to the MME, and the MME makes a final decision to determine which user terminals can perform RRC connection pre-recovery.
  • the application scenario scenario of this embodiment is the same as that of Embodiment 7, except that when determining the terminal list that can perform RRC connection pre-recovery, in addition to the final decision made by the MME in Embodiment 7, the following method may also be adopted:
  • the RAN does not perform steps 304 and 305, but directly performs RRC connection pre-recovery on the user terminal of the group A that can determine the RRC connection pre-recovery determined by itself.
  • the RAN does not inform the MME of the user terminal list of the group A that is determined to perform the RRC connection pre-recovery, so that when the terminal that has previously restored the RRC connection accesses the network, the new core network connection may be established.
  • the RAN informs the MME of the user terminal list of the group A that is determined to perform the RRC connection pre-recovery, and the MME performs pre-recovery of the core network connection for the UE included in the list.
  • a terminal group A has been predefined on the RAN side, including IDs of 10 terminals (for example, S-TMSI or IMSI), and terminal B (assuming that it belongs to a member of the terminal group A) initiates a master.
  • an RRC connection setup procedure is initiated to the eNB (the base station of the LTE RAN); after 5 minutes, another member terminal D of the group A also initiates an RRC connection recovery procedure to the eNB.
  • This example is used to explain how the RAN prepares in advance the partial context of the AS connection of multiple group members in the form of a group in the process of establishing a new network connection, and uses it for the establishment or restoration of the RRC connection of the subsequent group member terminals. Process to reduce air interface signaling overhead and reduce the processing power consumption of the base station.
  • Step 401 The terminal B initiates an RRC connection establishment process to the eNB, and reports its own UE ID (S-TMSI) in the RRC connection setup request message.
  • the current RRC connection establishment cause is MO-data (calling data service).
  • Step 402 The eNB queries whether the terminal B belongs to a member of a certain group, and determines that it belongs to the group A according to its ID.
  • Step 403 The eNB determines whether the other nine group member terminals remaining in the group A have a stored AS context. If there is no stored AS context, only the AS context can be newly created. In this example, it is assumed that the eNB does not have the AS context stored by the 9 group member terminals, and then the eNB continues to determine which terminals to perform AS context creation, and the selection method includes:
  • the group member X According to the activity of the group member, if a group member X of the RRC connection of the previous group member does not initiate a connection, or if the group member X does not initiate an RRC connection for several consecutive times, the group member X is considered to be an inactive member, and the RAN is not Create an AS context for this member.
  • the RAN may determine whether to be the member according to the information. Create a new AS context; for example:
  • the connection is a personal burst behavior of the UE, and no new AS context is needed.
  • the members of the group have multiple data periods, it is determined which group members have the data period and the data transmission time offset corresponding to the currently initiated UE, and a new AS context can be created for the matching group member.
  • connection establishment reason of the terminal B that initiated the connection process is the called (Mobile Terminal Call, MT call)
  • the RAN has not received the paging paging from the MME to the other group A member UEs, or has not received any
  • the group paging group group of the MME considers that the MT call is only a separate service of the UE, and other group A members do not need to newly create an AS context.
  • one method may be selected to assist the judgment, or two or three methods may be used in combination.
  • the eNB determines that seven of the remaining nine terminals perform a new AS context.
  • Step 404 The eNB creates an AS context for the selected terminal, including the following two modes:
  • the AS context is newly created by using the AS context of the terminal B that is currently establishing the connection as a blueprint.
  • the AS context is divided into a public part and a proprietary part.
  • the public part refers to an AS context part that can be used with other UEs.
  • UE security capability In the LTE standard, one or more of the following are included: UE security capability, quality of service (QoS) information, and radio access. Radio Access Bearer (RAB) information, RRC context, and handover restriction list.
  • RRB Radio Access Bearer
  • the UE security capability and the QoS information may be different from the terminal, but for the same group of terminals having the same feature, the AS context common part may be universal.
  • the proprietary part refers to the AS-specific part of the UE that is different from other UEs, and includes at least: AS security information. Because the AS security information needs to be dynamically updated, other UEs cannot be used as a reference or a fixed blueprint for reference.
  • the establishment of the new AS context by the eNB for the selected terminal actually refers to the common part of the new AS context, and the proprietary part of the AS context of the terminal is to be newly created when the terminal initiates the RRC connection by itself.
  • Step 405 It is assumed that after 5 minutes, the member terminal D of the group A is to initiate a service, and then initiates an RRC connection setup procedure or an RRC connection recovery procedure to the eNB, and reports its own UE in the RRC connection setup request message or in the RRC connection recovery request message. ID, the reason for this RRC connection establishment is the primary data service (MO-data).
  • Step 406 The eNB queries whether the terminal D has created an AS context. If the AS context has been created, the public part of the context of the terminal D is established according to the newly created context, and the eNB regenerates the AS context for the terminal D. For example, the newly generated AS security information is sent to the terminal D, and the AS security handshake is completed with the terminal D to establish AS security.
  • the eNB when the eNB selects which of the remaining terminals of the group A can perform the RRC connection pre-recovery or the AS context new, if some of the remaining terminals are not previously saved in the eNB For example, the eNB may choose to use two methods at the same time, that is, the AS context is newly created for the terminal that does not save the AS context in advance, and the RRC connection pre-recovery is performed for the terminal that has the AS context saved in advance.
  • This embodiment describes how the eNB performs AS context saving and RRC connection recovery in units of groups, including:
  • the terminal AS context of the previous AS connection of all the user terminals of the terminal group A is saved in units of groups, and the corresponding group A recovery ID is allocated for the AS context storage; or each of the terminal groups A
  • the user terminal allocates a corresponding recovery ID;
  • 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 a common part of the AS context of all user terminals in the terminal group A. 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;
  • the RAN receives the recovery ID of the terminal group A or the recovery ID of the user terminal B, according to the recovery ID or the location of the terminal group A.
  • the recovery ID of the user terminal B is queried to the AS context storage corresponding to the terminal B, and the AS connection of the user terminal B is established according to the stored context.
  • This embodiment relates to a system for implementing the foregoing embodiment, where the system includes an access network element, a core network element, and a user terminal.
  • the access network element includes a memory (storage medium) and a processor, and the processor of the access network element implements the solution of the foregoing embodiment by calling a program instruction (software program) in a 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 core network element in the solution in the foregoing embodiment by calling a program instruction (software program) in the memory on the core network element. The function.
  • the storage medium refers to a physical carrier that stores program instruction data (software programs); it may be a floppy disk, an optical disk, a digital video disc (DVD), a hard disk, a flash memory, a Universal Serial Bus Flash Disk (Universal Serial Bus Flash Disk, USB flash drive, Compact Flash Card, Compact Digital Card, Secure Multi-Media Card, Smart Media Card, Smart Card A memory stick, a photo memory card (XD Picture Card, xD card), etc.; or a device including the above storage product. among them:
  • the user terminal that can perform connection preprocessing is:
  • a user terminal that can be newly created in the AS access layer context or,
  • a user terminal that can perform AS connection pre-recovery.
  • performing connection pre-processing on the determined user terminal includes:
  • Establishing an AS context for the user terminal that can perform AS context creation according to the group information of the terminal group and/or the information of the user terminal in the terminal group.
  • the pre-recoverable user terminal that can perform the AS connection refers to: the user terminal that stores the AS context in advance on the network side and the terminal side;
  • a user terminal that can be newly created in the AS access layer context refers to a user terminal that does not store an AS context on the network side and the terminal side.
  • connection request initiated by the user terminal B is: a connection establishment request, a connection recovery request, or a data transmission request.
  • determining that the user terminal B belongs to the terminal group includes:
  • the user terminal B After the user terminal B uses the dedicated PRACH resource, the user terminal B is determined to be the user terminal in the terminal group; or ,
  • the user terminal B is determined to be the user terminal in the terminal group according to the ID uploaded by the user terminal B or the group ID of the group to which it belongs.
  • determining, in the terminal group, a user terminal that can perform connection pre-processing includes:
  • establishing an AS context includes:
  • the proprietary part of the AS context of the target user terminal is established by the target user terminal in consultation with the network side.
  • the pre-recovery AS connection comprises:
  • the AS context corresponding to the terminal group is searched according to the received recovery ID of the terminal group or the recovery ID of the user terminal; and the AS connection is pre-restored according to the AS context.
  • the pre-recovery AS connection comprises:
  • the AS context corresponding to the terminal group is searched according to the received recovery ID of the terminal group or the recovery ID of the user terminal; and the AS connection is pre-restored according to the AS context.
  • determining the user terminal that can be newly created by the AS context or the pre-recoverable user terminal that can perform the AS connection includes:
  • the user terminal that initially initiates the connection request or the connection recovery request in the previous terminal group, or the user terminal that continuously initiates the connection request or the connection recovery request exceeds the set threshold is determined as A user terminal newly created by the AS context or a pre-recovered user terminal capable of AS connection can be performed.
  • determining the user terminal that can be newly created by the AS context or the pre-recoverable user terminal that can perform the AS connection includes:
  • the user terminal that matches the group data period and the data transmission time offset of the user terminal B is determined as the user terminal that can be newly created in the AS context. Or a pre-recoverable user terminal that can perform an AS connection;
  • the user terminal that matches the data period and the data transmission time offset of the user terminal B is determined to be the user terminal that can be newly created in the AS context or may be A pre-recovered user terminal that performs an AS connection.
  • determining the user terminal that can be newly created by the AS context or the pre-recoverable user terminal that can perform the AS connection includes:
  • the user terminal list of the restored user terminal determines the user terminal that can be newly created by the AS context or the pre-recovered user terminal that can perform the AS connection.
  • the pre-recovery of the AS connection includes at least: establishing a signaling bearer, a data bearer, and an AS security.
  • program instructions stored in the memory installed on the core network element are used to implement the following functions:
  • the core network element makes a determination for the request and feeds back to the RAN a list of user terminals that allow and/or reject AS context creation or AS connection pre-recovery.
  • the method further includes:
  • the core network connection pre-recovery includes: the core network element recovers the NAS connection and the S1 connection of the terminal according to a core network context of the user terminal saved in advance, where the S1 connection refers to a connection between the core network and the RAN.
  • the decision request includes a list of IDs of the user terminal to be determined, or a group ID of the preset terminal group to which the user terminal to be determined belongs.
  • the core network connection pre-recovery further includes:
  • the core network context of the previous core network connection of all user terminals of the preset terminal group is saved in units of groups, or the core network context of the previous core network connection of one user terminal B in the terminal group is selected. Saving, and treating the public part of the core network context storage of the user terminal B as a common part of the core network context storage of all user terminals of the terminal group;
  • the core network context storage corresponding to the user terminal B is queried according to the recovery ID of the terminal group or the recovery ID of the user terminal B, and the core network connection of the user terminal B is established according to the stored core network context.
  • the type of the access network element includes, in addition to the eNB, a small station, a home base station, a 5G new RAT, and another access network that is compatible with an Evolved Packet Core (EPC) architecture.
  • EPC Evolved Packet Core
  • the core network element type includes a service gateway node (CI-T Serving Gateway Node, C-SGN) and a Narrow Band-Intemet of Things (NBIoT) MME to support machine type communication and mobility management.
  • C-SGN service gateway node
  • NBIoT Narrow Band-Intemet of Things
  • each of the above-described modules or each step of the present disclosure can be implemented by a general-purpose computing device, which can be centralized on a single computing device or distributed over a network of multiple computing devices.
  • they may be implemented in program code executable by a computing device such that they may be stored in a storage device for execution by a computing device or separately fabricated into one or more integrated circuit modules. Or by making multiple modules or steps among them into a single integrated circuit module.
  • the disclosure is not limited to any specific combination of hardware and software.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本文公开了一种连接建立方法，包括：接入网网元确定发起连接请求的用户终端所属的终端组；接入网网元确定所述终端组中进行连接预处理的目标用户终端；接入网网元对确定的所述目标用户终端进行所述连接预处理。本文还公开了一种连接建立方法、一种存储介质、一种接入网网元、一种核心网网元以及一种系统。

Description

连接建立方法、网元、存储介质及系统
本公开要求申请日为2017年07月24日、申请号为201710607456.8的中国专利申请的优先权，该申请的全部内容通过引用结合在本公开中。
技术领域
本公开涉及通讯技术领域，例如涉及一种连接建立方法、存储介质、网元及系统。
背景技术
随着物联网的发展，用户终端数量不断增加成为行业背景，海量连接对网络接入的负荷问题、系统效率问题已经成为目前研究的重点之一。
低成本、小带宽、以及小数据是物联网设备的典型特征。这类设备接入网络的持续时间短，传输数据量小，但设备保有量非常巨大。每一次设备和无线通信网络建立连接都会导致大量空口的控制面信令以及地面侧的控制面信令的开销，其中以无线接入网(Radio Access Network，RAN)侧的上下文的建立过程消耗的控制面信令为主。但相比于设备传输的数据量来说，存在控制面信令开销大于用户面数据量的情况，这导致系统传输效率的低下。目前第三代合作伙伴计划(3rd Generation Partnership Project，3GPP)在增强机器类型通信(Machine-type communication，MTC)、窄带物联(Narrow Band Intemet of Things，NBIOT)、以及第五代移动通信新无线接入技术(5G new Radio Access Technology，5G new RAT)等研究中，将如何降低海量接入所带来的控制面信令开销成本作为研究方向之一。
在目前3GPP讨论的长期演进(Long Term Evolution，LTE)标准和5G new RAT标准中，分别在LTE引入了轻连接(light connected)状态，在5G new RAT引入了非活动(inactive)状态。这两个状态的本质类似，对LTE RAN和5G RAN 来说，light connected状态和inactive状态均属于无线资源控制(Radio Resource Control，RRC)连接态的子状态。当终端处于light connected状态或inactive状态时，终端与RAN的RRC连接仍然保持，信令承载和数据承载仍然保持。但与RRC连接态的区别在于：终端和RAN需保存终端上下文，终端的移动性采用小区重选方式，终端监听RAN和核心网(Core Network，CN)的寻呼。
上述两个新状态的引入可以部分减少终端的耗电以及终端从空闲(IDLE)态到连接态的切换次数，从而减少部分信令开销，但并没有对海量连接引发的信令开销起到本质性的减少作用。
发明内容
本公开提供一种连接建立方法、存储介质、网元及系统，以解决相关技术控制面信令开销成本高的问题。
在一实施例中，本公开提供一种连接建立方法，包括：
接入网网元确定发起连接请求的用户终端所属的终端组；
接入网网元确定所述终端组中进行连接预处理的目标用户终端；
接入网网元对确定的所述目标用户终端进行所述连接预处理。
在一实施例中，本公开还提供一种连接建立方法，包括：
核心网网元接收接入网网元发送的决策请求，其中，所述决策请求用于请求核心网网元判定终端组中的待决策的用户终端能否进行连接预处理；
核心网网元针对所述决策请求做出判定，并向接入网网元反馈判定结果，其中，所述判定结果包括以下至少之一：允许进行连接预处理的用户终端的列表和拒绝进行连接预处理的用户终端的列表。
在一实施例中，本公开还提供一种计算机可读存储介质，所述存储介质中存储有程序指令，所述程序指令被配置为实现接入网网元侧的连接建立方法。
在一实施例中，本公开还提供一种计算机可读存储介质，所述存储介质中 存储有程序指令，所述程序指令被配置为实现核心网网元侧的连接建立方法。
在一实施例中，本公开还提供一种接入网网元，包括处理器和存储器，所述存储器中存储有程序指令，所述处理器通过调用存储器中的所述程序指令，所述程序指令运行时执行接入网网元侧的连接建立方法。
在一实施例中，本公开还提供一种核心网网元，包括处理器和存储器，所述存储器中存储有程序指令，所述处理器通过调用存储器中的所述程序指令，所述程序指令运行时执行核心网网元侧的连接建立方法。
在一实施例中，本公开还提供一种系统，包括上述接入网网元、核心网网元和用户终端。
附图说明
图1为本公开实施例提供的一种连接建立方法的流程图；
图2为本公开实施例提供的另一种连接建立方法的流程图；
图3为本空开实施例中基于组形式的多终端连接建立方法的流程图；
图4为本公开实施例提供的LTE系统中连接建立方法的流程图。
具体实施方式
以下结合附图以及实施例，对本公开进行详细说明。此处所描述的实施例仅仅用以解释本公开，并不限定本公开。
组的概念虽然在3GPP被提出，但目前只运用在以组为单位的寻址、累积最大速率(Aggregate Maximum Bit Rate，AMBR)控制、广播形式的组消息发送、以及以组为单位的计费等方面，对于控制面信令产生的最大过程(连接建立过程)上，由于这是终端发起的个体离散性行为，无论是时间上还是连接性质上都难以以组的方式一次性实现，因此始终没有被业界关注和解决。
本公开将用户终端进行分组，当终端组中的任一用户终端发起连接请求(连接建立请求、连接恢复请求或者数据传输请求)时，对终端组中剩余的用户终 端进行筛选识别，选定可以进行连接预处理的用户终端，针对选定的用户终端在接入网侧和核心网侧进行预连接处理。这样，当已经建立预连接处理的用户终端再次发起连接请求时，直接用预连接的信息来建立连接，这样就会快速建立或恢复RRC连接，并且有效降低控制面信令的开销成本。
对终端组中剩余的用户终端进行筛选识别，选定可以进行预连接处理的用户终端时，要核心网侧进行决策时，则核心网网元接收接入网网元RAN侧发送的决策请求，请求核心网网元针对终端组中的用户终端能否进行AS上下文新建或者AS连接预恢复进行判定；核心网网元针对该请求做出判定，并向RAN反馈允许和/或拒绝进行AS上下文新建或者AS连接预恢复的用户终端的列表。
基站侧的预连接处理包括：根据预先存储的终端组中用户终端的AS上下文，对确定可进行AS连接预恢复的用户终端预恢复AS连接；或者，根据终端组的组信息和/或所述终端组内用户终端的信息，对可进行AS上下文新建的用户终端建立AS上下文。
核心网侧的预连接处理包括：对该用户终端进行非接入层(Non-Access-Stratum，NAS)上下文新建或者核心网连接预恢复；其中，核心网连接预恢复包括，核心网网元根据事先保存的用户终端的核心网上下文恢复所述终端的NAS连接和S1连接，其中S1连接指核心网和RAN之间的连接。
在一实施例中，接入网网元确定发起连接请求的用户终端(例如，移动终端B)所属的终端组。
所述接入网网元确定所述终端组中进行连接预处理的目标用户终端。
所述接入网网元对确定的所述目标用户终端进行所述连接预处理。
在一实施例中，所述进行连接预处理的目标用户终端为：
进行接入层AS上下文新建的目标用户终端；或者
进行接入层AS连接预恢复的目标用户终端。
在一实施例中，确定进行连接预处理的目标用户终端，包括以下之一：
将在所述发起连接请求的用户终端发起连接请求之前所述终端组中集中发 起连接请求的用户终端，确定为进行AS上下文新建的目标用户终端或者进行AS连接预恢复的目标用户终端；
将在所述发起连接请求的用户终端发起连接请求之前，连续发起连接请求的次数超过设定阈值的用户终端，确定为进行AS上下文新建的目标用户终端或者进行AS连接预恢复的目标用户终端。
在一实施例中，所述确定进行连接预处理的目标用户终端，包括：
将所述终端组中与所述用户终端的数据周期以及数据发送时间偏置相符的用户终端，确定为所述进行AS上下文新建的目标用户终端或者进行AS连接预恢复的目标用户终端。
在一实施例中，确定进行连接预处理的目标用户终端，包括以下之一：
根据所述核心网网元指定的进行AS上下文新建的目标用户终端的名单，确定所述进行AS上下文新建的目标用户终端；
根据所述核心网网元指定的进行AS连接预恢复的目标用户终端的名单，确定所述进行AS连接预恢复的目标用户终端；
根据所述核心网网元指定的拒绝进行AS上下文新建的目标用户终端的名单，确定所述进行AS上下文新建的目标用户终端；
根据所述核心网网元指定的拒绝进行AS连接预恢复的目标用户终端的名单，确定所述进行AS连接预恢复的目标用户终端。
在一实施例中，所述接入网网元确定所述终端组中进行连接预处理的目标用户终端，包括：
向核心网网元发送请求，以请求所述核心网网元确定所述终端组中进行连接预处理的目标用户终端；其中，所述请求中包含：所述终端组中除所述发起连接请求的用户终端以外的全部用户终端的标识ID、所述终端组的标识ID或者所述发起连接请求的用户终端的标识ID。
根据所述核心网网元反馈的确认指示，得到所述进行连接预处理的目标用户终端。
在一实施例中，对所述目标用户终端建立AS上下文包括：
将所述发起连接请求的用户终端的AS上下文中的公共部分作为待建立AS上下文的目标用户终端的AS上下文的公共部分；或者，
预设一个AS上下文，将预设的AS上下文中的公共部分作为待建立AS上下文的目标用户终端的AS上下文的公共部分；
所述接入网网元与所述目标用户终端协商建立所述目标用户终端的AS上下文的专有部分。
在一实施例中，对所述目标用户终端预恢复AS连接包括：
将所述终端组中的所有用户终端的上一次AS连接的AS上下文进行保存；
为所述终端组分配终端组恢复标识ID，其中，所述组恢复标识ID对应所述终端组中的所有用户终端；当预恢复AS连接时，根据所述终端组恢复标识ID，查找与所述终端组恢复标识ID对应的所有用户终端的AS上下文；
根据查找到的与所述终端组恢复标识ID对应的所有用户终端的AS上下文预恢复AS连接；
或者，
将所述终端组中的所有用户终端的上一次AS连接的AS上下文进行保存；
为所述终端组中的每个用户终端分配对应的恢复标识ID；
根据所述目标用户终端的恢复标识ID，查找与所述目标用户终端的恢复标识ID对应的AS上下文；
根据查找到的与所述目标用户终端的恢复标识ID对应的AS上下文预恢复AS连接。
在一实施例中，对所述目标用户终端预恢复AS连接包括：
保存所述发起连接请求的用户终端上一次AS连接的AS上下文，并将所述AS上下文的公共部分作为所述终端组中所有用户终端的AS上下文的公共部分进行存储；
为所述终端组分配终端组恢复标识ID，其中，所述终端组恢复标识ID对应 所述终端组中的所有用户终端；当预恢复AS连接时，根据所述终端组恢复标识ID，查找与所述终端组恢复标识ID对应的所有用户终端的AS上下文的公共部分；
根据查找到的所述终端组恢复标识ID对应的所有用户终端的AS上下文的公共部分预恢复AS连接；或者，
保存所述发起连接请求的用户终端上一次AS连接的AS上下文，并将所述AS上下文的公共部分作为所述终端组中所有用户终端的AS上下文的公共部分进行存储；
为所述终端组中的每个用户终端分配对应的恢复标识ID；
当预恢复AS连接时，根据所述目标用户终端的恢复标识ID，查找与所述目标用户终端的恢复标识ID对应的AS上下文的公共部分；
根据查找到的与所述目标用户终端的恢复标识ID对应的AS上下文的公共部分预恢复AS连接。
在一实施例中，对确定的所述目标用户终端进行所述连接预处理，包括：
当所述进行连接预处理的目标用户终端为进行AS连接预恢复的目标用户终端时，根据预先存储的所述终端组中所述目标用户终端的AS上下文，对所述目标用户终端预恢复AS连接；
当所述进行连接预处理的目标用户终端为进行AS上下文新建的目标用户终端时，根据下述至少一项信息对所述目标用户终端建立AS上下文：所述终端组的组信息和所述终端组内的用户终端的信息。
在一实施例中，核心网网元接收接入网网元发送的决策请求，其中，所述决策请求用于请求所述核心网网元判定终端组中的待决策的用户终端能否进行连接预处理。
核心网网元针对所述决策请求做出判定，并向接入网网元反馈判定结果，其中，所述判定结果包括以下至少之一：允许进行连接预处理的用户终端的列表和拒绝进行连接预处理的用户终端的列表。
在一实施例中，所述核心网网元判定终端组中待决策的用户终端能否进行连接预处理，包括：
所述核心网网元判定终端组中的用户终端能否进行接入层AS上下文新建或者接入层AS连接预恢复；
允许进行连接预处理的用户终端的列表，包括以下之一：允许进行AS上下文新建的用户终端的列表和允许进行AS连接预恢复的用户终端的列表；
拒绝进行连接预处理的用户终端的列表，包括以下之一：拒绝进行AS上下文新建的用户终端的列表和拒绝进行AS连接预恢复的用户终端的列表。
在一实施例中，在核心网网元针对所述决策请求做出判定之后，还包括：
当所述判定结果包括允许进行AS上下文新建的用户终端的列表时，对所述列表中的用户终端进行非接入层NAS上下文新建；或者
当所述判定结果包括允许进行AS连接预恢复的用户终端的列表时，对所述列表中的用户终端进行核心网连接预恢复；其中，核心网连接预恢复包括：所述核心网网元根据预先保存的用户终端的核心网上下文恢复所述用户终端的NAS连接和S1连接，其中，所述S1连接为所述核心网网元和所述接入网网元之间的连接。
在一实施例中，所述决策请求包括待决策的用户终端的标识ID列表、或者待决策的用户终端所属的终端组的组标识ID。
在一实施例中，所述核心网连接预恢复还包括：
以组为单位将终端组的所有用户终端的上一次核心网连接的核心网上下文进行保存，或者，选择所述终端组中发起连接请求的用户终端的上一次核心网连接的核心网上下文进行保存，并将所述发起连接请求的用户终端的核心网上下文存储的公共部分当做终端组所有用户终端的核心网上下文存储的公共部分；
为存储的所述核心网上下文分配对应的终端组恢复标识ID，其中，所述终端组恢复标识ID对应所述终端组中的所有用户终端；
当所述发起连接请求的用户终端再一次建立核心网连接时，接收所述发起 连接请求的用户终端或接入网网元发送的终端组恢复标识ID；
根据所述发起连接请求的用户终端或接入网网元发送的终端组恢复标识ID，查询到所述发起连接请求的用户终端对应的核心网上下文，根据存储的所述核心网上下文建立所述发起连接请求的用户终端的核心网连接；或者
以组为单位将终端组的所有用户终端的上一次核心网连接的核心网上下文进行保存，或者，选择所述终端组中的发起连接请求的用户终端的上一次核心网连接的核心网上下文进行保存，并将所述发起连接请求的用户终端的核心网上下文存储的公共部分当做所述终端组中所有用户终端的核心网上下文存储的公共部分；
为所述终端组的每个用户终端分配对应的用户终端恢复标识ID；
当所述发起连接请求的用户终端再一次建立核心网连接时，接收所述发起连接请求的用户终端或接入网网元发送的所述发起连接请求的用户终端的恢复标识ID；
根据所述发起连接请求的用户终端的恢复标识ID，查询到所述发起连接请求的用户终端对应的核心网上下文，根据存储的所述核心网上下文建立所述发起连接请求的用户终端的核心网连接。
下面通过实施例进行说明。
实施例1
本实施例涉及一种连接建立方法，该方法应用于接入网网元侧，参见图1，包括：
S110、接入网网元确定发起连接请求的用户终端所属的终端组。
S120、所述接入网网元确定所述终端组中进行连接预处理的目标用户终端。
S130、所述接入网网元对确定的所述目标用户终端进行所述连接预处理。
当收到用户终端B发起的连接请求后，接入网网元首先确定用户终端B所属的终端组；然后在该终端组中确定可进行连接预处理的用户终端；最后对确定的用户终端进行连接预处理。通过上述技术方案，完成了连接预处理的终端 再发起连接请求时，就可以快速建立或恢复RRC连接，有效降低控制面信令的开销成本。其中，用户终端B为接入网网元管理下的任意一个用户终端。
本实施例中，确定用户终端B所属的终端组，可以采用以下任一方案：
当用户终端B使用为终端组预分配专用的物理随机接入信道(Physical Random Access Channel，PRACH)资源时，则判定用户终端B为终端组中的用户终端；或者，
根据用户终端B上传的用户终端B的标识ID或用户终端B所属终端组的组标识ID，判定用户终端B为终端组中的用户终端。
上述方案中，用户终端B发起的连接请求可以为连接建立请求、连接恢复请求或者数据传输请求。可进行连接预处理的用户终端为：可进行接入层AS上下文新建的用户终端；或者，可进行AS连接预恢复的用户终端。其中，AS连接的预恢复至少包括：建立信令承载、数据承载和AS安全。
其中，可进行AS连接的预恢复的用户终端是指：在网络侧和终端侧预先均存储有AS上下文的用户终端；
可进行AS接入层上下文新建的用户终端是指：在网络侧和终端侧未存储AS上下文的用户终端。
其中，确定可进行AS上下文新建的用户终端或者可进行AS连接的预恢复的用户终端，包括：
对于终端组中的用户终端，将前一次终端组中集中发起连接请求或者连接恢复请求的的用户终端，或者连续发起连接请求或者连接恢复请求的次数超过设定阈值的用户终端，确定为可进行AS上下文新建的用户终端或者可进行AS连接的预恢复的用户终端；或者，
将终端组中与用户终端B的数据周期以及数据发送时间偏置相符的用户终端，确定为可进行AS上下文新建的用户终端或者可进行AS连接的预恢复的用户终端；或者，
根据核心网网元指定的可进行AS上下文新建的用户终端或者可进行AS连 接的预恢复的用户终端名单，或者核心网网元指定的拒绝进行AS上下文新建的用户终端或者拒绝进行AS连接的预恢复的用户终端的用户终端名单，确定可进行AS上下文新建的用户终端或者可进行AS连接的预恢复的用户终端。
上述方案中，在终端组中确定可进行连接预处理的用户终端，包括：
向核心网网元发送请求，以请求核心网网元确定终端组中可进行连接预处理的用户终端；请求中包含终端组中除用户终端B以外的全部用户终端的ID、终端组的ID或者用户终端B的ID；
根据核心网网元反馈的确认指示，得到终端组中确定可进行连接预处理的用户终端。
上述方案中，建立AS上下文包括：
将用户终端B的AS上下文中的公共部分作为待建立AS上下文的目标用户终端的AS上下文的公共部分；或者，预设一个AS上下文，将预设的AS上下文中的公共部分作为待建立AS上下文的目标用户终端的AS上下文的公共部分；目标用户终端的AS上下文的专有部分则由目标用户终端与网络侧协商建立。
上述方案中，预恢复AS连接包括：
将终端组中的所有用户终端的上一次AS连接的AS上下文进行保存；为终端组分配终端组恢复ID，或者为终端组中每个用户终端分配对应的恢复ID；建立预恢复AS连接时，根据接收的终端组的恢复ID或者用户终端的恢复ID，查找到与其对应的AS上下文；根据该AS上下文预恢复AS连接；或者，
保存用户终端B上一次AS连接的AS上下文，并将该AS上下文的公共部分作为终端组中所有用户终端的AS上下文的公共部分进行存储；为终端组分配终端组恢复ID，或者为终端组中每个用户终端分配对应的恢复ID；建立预恢复AS连接时，根据接收的终端组的恢复ID或者用户终端的恢复ID，查找到与其对应的AS上下文；根据该AS上下文预恢复AS连接。
上述方案中，对确定的用户终端进行连接预处理，为：
根据预先存储的终端组中用户终端的AS上下文，对确定可进行AS连接预 恢复的用户终端预恢复AS连接；或者，根据终端组的组信息和/或终端组内用户终端的信息，对可进行AS上下文新建的用户终端建立AS上下文。
实施例2
本实施例涉及一种存储介质，该存储介质中存储有程序指令，该程序指令用于实现实施例1的技术方案，其中，该程序指令用于实现如下功能：
当收到用户终端B发起的连接请求后，接入网网元首先确定用户终端B所属的终端组；然后在该终端组中确定可进行连接预处理的用户终端；最后对确定的用户终端进行连接预处理。通过上述技术方案，完成了连接预处理的终端再发起连接请求时，就可以快速建立或恢复RRC连接，有效降低控制面信令的开销成本。
本实施例中，确定用户终端B所属的终端组，可以采用以下任一方案：
当用户终端B使用为终端组预分配专用的物理随机接入信道PRACH资源时，则判定用户终端B为终端组中的用户终端；或者，
根据用户终端B上传的用户终端B的标识ID或用户终端B所属组的组ID，判定用户终端B为终端组中的用户终端。
上述方案中，用户终端B发起的连接请求可以为连接建立请求、连接恢复请求或者数据传输请求。可进行连接预处理的用户终端为：可进行接入层AS上下文新建的用户终端；或者，可进行AS连接预恢复的用户终端。其中，AS连接的预恢复至少包括：建立信令承载、数据承载和AS安全。
其中，确定可进行AS上下文新建的用户终端或者可进行AS连接的预恢复的用户终端，包括：
对于终端组中的用户终端，将前一次终端组中集中发起连接请求或者连接恢复请求的的用户终端，或者连续发起连接请求或者连接恢复请求的次数超过设定阈值的用户终端，确定为可进行AS上下文新建的用户终端或者可进行AS连接的预恢复的用户终端；或者，
将终端组中与用户终端B的数据周期以及数据发送时间偏置相符的用户终 端，确定为可进行AS上下文新建的用户终端或者可进行AS连接的预恢复的用户终端；或者，
根据核心网网元指定的可进行AS上下文新建的用户终端或者可进行AS连接的预恢复的用户终端名单，或者核心网网元指定的拒绝进行AS上下文新建的用户终端或者拒绝进行AS连接的预恢复的用户终端的用户终端名单，确定可进行AS上下文新建的用户终端或者可进行AS连接的预恢复的用户终端。
上述方案中，在终端组中确定可进行连接预处理的用户终端，包括：
向核心网网元发送请求，以请求核心网网元确定终端组中可进行连接预处理的用户终端；请求中包含终端组中除用户终端B以外的全部用户终端的ID、终端组的ID或者用户终端B的ID；
根据核心网网元反馈的确认指示，得到终端组中确定可进行连接预处理的用户终端。
上述方案中，建立AS上下文包括：
将用户终端B的AS上下文中的公共部分作为待建立AS上下文的目标用户终端的AS上下文的公共部分；或者，预设一个AS上下文，将预设的AS上下文中的公共部分作为待建立AS上下文的目标用户终端的AS上下文的公共部分；目标用户终端的AS上下文的专有部分则由目标用户终端与网络侧协商建立。
上述方案中，预恢复AS连接包括：
将终端组中的所有用户终端的上一次AS连接的AS上下文进行保存；为终端组分配终端组恢复ID，或者为终端组中每个用户终端分配对应的恢复ID；建立预恢复AS连接时，根据接收的终端组的恢复ID或者用户终端的恢复ID，查找到与其对应的AS上下文；根据该AS上下文预恢复AS连接；或者，
保存用户终端B上一次AS连接的AS上下文，并将该AS上下文的公共部分作为终端组中所有用户终端的AS上下文的公共部分进行存储；为终端组分配终端组恢复ID，或者为终端组中每个用户终端分配对应的恢复ID；建立预恢复AS连接时，根据接收的终端组的恢复ID或者用户终端的恢复ID，查找到与其 对应的AS上下文；根据该AS上下文预恢复AS连接。
上述方案中，对确定的用户终端进行连接预处理，为：
根据预先存储的终端组中用户终端的AS上下文，对确定可进行AS连接预恢复的用户终端预恢复AS连接；或者，根据终端组的组信息和/或终端组内用户终端的信息，对可进行AS上下文新建的用户终端建立AS上下文。
实施例3
本实施例涉及一种接入网网元，包括处理器和存储器，处理器中存储有程序指令，处理器通过调用存储器中存储的程序指令，该程序指令运行时来实现实施例1的技术方案，其中，该程序指令用于实现如下功能：
当收到用户终端B发起的连接请求后，接入网网元首先确定用户终端B所属的终端组；然后在该终端组中确定可进行连接预处理的用户终端；最后对确定的用户终端进行连接预处理。通过上述技术方案，完成了连接预处理的终端再发起连接请求时，就可以快速建立或恢复RRC连接，有效降低控制面信令的开销成本。
本实施例中，确定用户终端B所属的终端组，可以采用以下任一方案：
当用户终端B使用为终端组预分配专用的物理随机接入信道PRACH资源时，则判定用户终端B为终端组中的用户终端；或者，
根据用户终端B上传的其ID或其所属组的组ID，判定用户终端B为终端组中的用户终端。
上述方案中，用户终端B发起的连接请求可以为连接建立请求、连接恢复请求或者数据传输请求。可进行连接预处理的用户终端为：可进行接入层AS上下文新建的用户终端；或者，可进行AS连接预恢复的用户终端。其中，AS连接的预恢复至少包括：建立信令承载、数据承载和AS安全。
其中，确定可进行AS上下文新建的用户终端或者可进行AS连接的预恢复的用户终端，包括：
对于终端组中的用户终端，将前一次终端组中集中发起连接请求或者连接 恢复请求的的用户终端，或者连续发起连接请求或者连接恢复请求的次数超过设定阈值的用户终端，确定为可进行AS上下文新建的用户终端或者可进行AS连接的预恢复的用户终端；或者，
将终端组中与用户终端B的数据周期以及数据发送时间偏置相符的用户终端，确定为可进行AS上下文新建的用户终端或者可进行AS连接的预恢复的用户终端；或者，
根据核心网网元指定的可进行AS上下文新建的用户终端或者可进行AS连接的预恢复的用户终端名单，或者核心网网元指定的拒绝进行AS上下文新建的用户终端或者拒绝进行AS连接的预恢复的用户终端的用户终端名单，确定可进行AS上下文新建的用户终端或者可进行AS连接的预恢复的用户终端。
上述方案中，在终端组中确定可进行连接预处理的用户终端，包括：
向核心网网元发送请求，以请求核心网网元确定终端组中可进行连接预处理的用户终端；请求中包含终端组中除用户终端B以外的全部用户终端的ID、终端组的ID或者用户终端B的ID；
根据核心网网元反馈的确认指示，得到终端组中确定可进行连接预处理的用户终端。
上述方案中，建立AS上下文包括：
将用户终端B的AS上下文中的公共部分作为待建立AS上下文的目标用户终端的AS上下文的公共部分；或者，预设一个AS上下文，将预设的AS上下文中的公共部分作为待建立AS上下文的目标用户终端的AS上下文的公共部分；目标用户终端的AS上下文的专有部分则由目标用户终端与网络侧协商建立。
上述方案中，预恢复AS连接包括：
将终端组中的所有用户终端的上一次AS连接的AS上下文进行保存；为终端组分配终端组恢复ID，或者为终端组中每个用户终端分配对应的恢复ID；建立预恢复AS连接时，根据接收的终端组的恢复ID或者用户终端的恢复ID，查找到与其对应的AS上下文；根据该AS上下文预恢复AS连接；或者，
保存用户终端B上一次AS连接的AS上下文，并将该AS上下文的公共部分作为终端组中所有用户终端的AS上下文的公共部分进行存储；为终端组分配终端组恢复ID，或者为终端组中每个用户终端分配对应的恢复ID；建立预恢复AS连接时，根据接收的终端组的恢复ID或者用户终端的恢复ID，查找到与其对应的AS上下文；根据该AS上下文预恢复AS连接。
上述方案中，对确定的用户终端进行连接预处理，为：
根据预先存储的终端组中用户终端的AS上下文，对确定可进行AS连接预恢复的用户终端预恢复AS连接；或者，根据终端组的组信息和/或终端组内用户终端的信息，对可进行AS上下文新建的用户终端建立AS上下文。
实施例4
本实施例涉及一种连接建立方法，该方法应用于核心网网元侧，参见图2，包括：
S210、核心网网元接收接入网网元发送的决策请求，其中，所述决策请求用于请求所述核心网网元判定终端组中的待决策的用户终端能否进行连接预处理。
S220、核心网网元针对所述决策请求做出判定，并向接入网网元反馈判定结果，其中，所述判定结果包括以下至少之一：允许进行连接预处理的用户终端的列表和拒绝进行连接预处理的用户终端的列表。
核心网网元接收接入网网元发送的决策请求，请求核心网网元针对终端组中的用户终端能否进行AS上下文新建或者AS连接预恢复进行判定；其中，决策请求包括待决策的用户终端的ID列表、或者待决策的用户终端所属的预设终端组的组ID。
核心网网元针对该请求做出判定，并向接入网网元反馈允许和/或拒绝进行AS上下文新建或者AS连接预恢复的用户终端的列表。
在一实施例中，核心网网元针对该请求做出判定之后，还包括：
对该用户终端进行非接入层NAS上下文新建或者核心网连接预恢复；
其中，核心网连接预恢复包括，核心网网元根据事先保存的用户终端的核心网上下文恢复所述终端的NAS连接和S1连接，其中S1连接指核心网和接入网网元之间的连接。
其中，所述核心网连接预恢复还包括：
以组为单位将预设终端组的所有用户终端的前一次核心网连接的核心网上下文进行保存，或者，选择所述终端组中的一个用户终端B的前一次核心网连接的核心网上下文进行保存，并将所述用户终端B的核心网上下文存储的公共部分当做终端组所有用户终端的核心网上下文存储的公共部分；
为所述核心网上下文存储分配对应的终端组恢复ID，或者为终端组每个用户终端分配对应的用户终端恢复ID；
当所述用户终端B再一次建立核心网连接时，接收用户终端B或接入网网元发送的终端组的恢复ID或者用户终端B的恢复ID；
根据终端组的恢复ID或者用户终端B的恢复ID，查询到所述用户终端B对应的核心网上下文存储，根据所述存储的核心网上下文建立所述用户终端B的核心网连接。
本实施例技术方案对确定进行进行AS上下文新建或者AS连接预恢复的用户终端进行非接入层NAS上下文新建或者核心网连接预恢复，这样，当这些终端发起请求时，再发起连接建立请求时，就可以快速建立或恢复RRC连接，并且有效降低控制面信令的开销成本。
实施例5
本实施例涉及一种存储介质，该存储介质中存储有程序指令，该程序指令用于实现实施例4的技术方案，其中，该程序指令用于实现如下功能：
核心网网元接收接入网网元发送的决策请求，请求核心网网元针对终端组中的用户终端能否进行AS上下文新建或者AS连接预恢复进行判定；其中，决策请求包括待决策的用户终端的ID列表、或者待决策的用户终端所属的预设终端组的组ID。
核心网网元针对该请求做出判定，并向接入网网元反馈允许和/或拒绝进行AS上下文新建或者AS连接预恢复的用户终端的列表。
在一实施例中，核心网网元针对该请求做出判定之后，还包括：
对该用户终端进行非接入层NAS上下文新建或者核心网连接预恢复；
其中，核心网连接预恢复包括，核心网网元根据事先保存的用户终端的核心网上下文恢复所述终端的NAS连接和S1连接，其中S1连接指核心网和接入网网元之间的连接。
其中，所述核心网连接预恢复还包括：
以组为单位将预设终端组的所有用户终端的前一次核心网连接的核心网上下文进行保存，或者，选择所述终端组中的一个用户终端B的前一次核心网连接的核心网上下文进行保存，并将所述用户终端B的核心网上下文存储的公共部分当做终端组所有用户终端的核心网上下文存储的公共部分；
为所述核心网上下文存储分配对应的终端组恢复ID，或者为终端组每个用户终端分配对应的用户终端恢复ID；
当所述用户终端B再一次建立核心网连接时，接收用户终端B或接入网网元发送的终端组的恢复ID或者用户终端B的恢复ID；
根据终端组的恢复ID或者用户终端B的恢复ID，查询到所述用户终端B对应的核心网上下文存储，根据所述存储的核心网上下文建立所述用户终端B的核心网连接。
本实施例技术方案对确定进行进行AS上下文新建或者AS连接预恢复的用户终端进行非接入层NAS上下文新建或者核心网连接预恢复，这样，当这些终端发起请求时，再发起连接建立请求时，就可以快速建立或恢复RRC连接，并且有效降低控制面信令的开销成本。
实施例6
本实施例涉及一种核心网网元，包括处理器和存储器，处理器中存储有程序指令，处理器通过调用存储器中存储的程序指令，该程序指令运行时来实现 实施例4的技术方案，其中，该程序指令用于实现如下功能：
接收接入网网元发送的决策请求，请求核心网网元针对终端组中的用户终端能否进行AS上下文新建或者AS连接预恢复进行判定；其中，决策请求包括待决策的用户终端的ID列表、或者待决策的用户终端所属的预设终端组的组ID。
针对该请求做出判定，并向接入网网元反馈允许和/或拒绝进行AS上下文新建或者AS连接预恢复的用户终端的列表。
在一实施例中，针对该请求做出判定之后，还包括：
对该用户终端进行非接入层NAS上下文新建或者核心网连接预恢复；
其中，核心网连接预恢复包括，根据事先保存的用户终端的核心网上下文恢复所述终端的NAS连接和S1连接，其中S1连接指核心网和接入网网元之间的连接。
其中，所述核心网连接预恢复还包括：
以组为单位将预设终端组的所有用户终端的前一次核心网连接的核心网上下文进行保存，或者，选择所述终端组中的一个用户终端B的前一次核心网连接的核心网上下文进行保存，并将所述用户终端B的核心网上下文存储的公共部分当做终端组所有用户终端的核心网上下文存储的公共部分；
为所述核心网上下文存储分配对应的终端组恢复ID，或者为终端组每个用户终端分配对应的用户终端恢复ID；
当所述用户终端B再一次建立核心网连接时，接收用户终端B或接入网网元发送的终端组的恢复ID或者用户终端B的恢复ID；
根据终端组的恢复ID或者用户终端B的恢复ID，查询到所述用户终端B对应的核心网上下文存储，根据所述存储的核心网上下文建立所述用户终端B的核心网连接。
在一实施例中，所述决策请求包括待决策的用户终端的标识ID列表、或者待决策的用户终端所属的终端组的组标识ID。
本实施例技术方案对确定进行进行AS上下文新建或者AS连接预恢复的用 户终端进行非接入层NAS上下文新建或者核心网连接预恢复，这样，当这些终端发起请求时，再发起连接建立请求时，就可以快速建立或恢复RRC连接，并且有效降低控制面信令的开销成本。
下面，以实施例说明本公开基于组形式的多终端连接建立方法及相关网元设备。
实施例7
以LTE系统为例，假设在核心网元移动性管理实体-A(Mobile Management Equipment A，MME-A)侧已经预定义了一个终端组A，终端组A中包含多个终端标识，例如，包含10个终端的ID(例如临时移动用户标识(Serving-Temporary Mobile Subscriber Identity，S-TMSI)或国际移动设备识别码(International Mobile Subscriber Identification Number，IMSI))，MME-A下属的演进型基站(Evolved Node Base，eNB)已提前从MME-A获取组A的信息，终端B(假设其属于终端组A的一员)发起主叫流程，向MME-A下属的一个eNB(LTE RAN的基站)发起RRC连接建立过程；5分钟后，组A的另一个成员终端D向eNB发起RRC连接恢复过程。
本例用以说明在新建网络连接过程中，无线接入网(Radio Access Network，RAN)和MME如何以组的形式提前将多个组成员的AS连接和核心网连接提前准备好，并将之用于后续的组成员终端的RRC连接建立过程来减少空口信令开销的。
图3中只示出终端B在发起建立RRC连接过程中，为组内其它终端建立RRC连接预恢复的流程(注：AS连接是无线接入网和终端之间的连接的泛称，RRC连接归属于于AS连接)，以及后续组内终端发起RRC连接的建立流程，因此图3没有包括终端B建立RRC连接的流程，并不表示终端B不建立RRC连接，而只是在图3中没有示出。用户终端B发起的连接请求可以为：连接建立请求、连接恢复请求或者数据传输。
如图3所示，基于组形式的多终端连接建立方法包括：
步骤301：终端B向eNB发起RRC连接建立过程，在RRC连接建立请求消息中上报自己的用户终端(User Equipment，UE)标识ID(S-TMSI)，本次RRC连接建立原因为主叫数据业务(Mobile Origination Call Data，MO-data)；
步骤302：eNB查询终端B是否属于某个组的成员，根据其ID确定其属于组A；由RAN或者核心网网元定义同属一组的成员终端，并分配组ID，组内的成员终端应具有下述相同的特征：相同的业务、相同的业务模型、相同的业务种类、相同的终端类型、或者相同的接入点名称(Access Point Name，APN)。
步骤303：eNB判断是否对组A剩余的其他9个组成员终端进行RRC连接的预恢复；可进行RRC连接预恢复的必要条件是，eNB事先存储了终端的AS上下文，没有存储上下文的终端无法进行RRC连接预恢复，在满足该必要条件的基础上，选择哪些组成员终端进行RRC连接预恢复的判断方法包括：
根据组成员的活跃度判断：如果前一次组成员的RRC连接中某组成员X没有发起连接，或者连续数次组成员X没有发起RRC连接，则认为该组成员X为不活跃成员，RAN不为该成员预恢复RRC连接；
根据组成员的数据周期判断：如果组成员向RAN上报过自己的数据传输周期信息(数据周期)，或者RAN从MME获取过所述组A的数据传输周期信息，则RAN可根据该信息确定是否要为该成员预恢复RRC连接；可以为：
如果当前发起连接的UE不符合数据周期以及数据发送时间偏置，则判断这次连接是该UE的个人突发行为，不用预恢复其他组员的RRC连接。
如果组内成员有多种数据周期，则判断哪些组成员的数据周期和数据发送时间偏置与当前发起连接的UE相符，可预恢复相符的组员的RRC连接。
根据MME的反馈判断：若MME-A指定了可预恢复RRC连接的UE名单，eNB根据这些指示来确定可预恢复RRC连接的组成员UE；若MME指定了拒绝预恢复连接的UE名单，eNB不进行所述名单中的UE的RRC预建立或者预恢复。
如果当前发起连接过程的终端B的连接建立原因是被叫(Mobile Terminal  Call，MT call)，且RAN没有收到过来自MME的给其他组A成员UE的寻呼paging，或者没有收到过来自MME的组A的组寻呼group paging，则认为这次MT call只是该UE的单独业务，其他组A成员不用一起预恢复RRC连接。
上述方法中，可以选择1种方法来辅助判断，也可以两种或三种方法结合使用，其中MME指示的方法具有最高优先级。即如果eNB自己判断有8个终端可以进行RRC连接预恢复，但MME指示只有其中的5个终端允许进行RRC连接预恢复，那么eNB要遵守MME的指示。
在本例中，假设eNB判定为剩余9个终端中的7个终端进行RRC预恢复。
步骤304：eNB将选定可进行RRC预恢复的7个终端的名单发给MME审核，可通过S1口的已存在的信令携带该名单，例如通过初始UE消息Initial UE Message发送；也可以新定义一个S1口信令。所述S1口指eNB和MME的接口。注：如果eNB决定对组A剩余的所有终端进行RRC连接预恢复，可以只发送组A的ID给MME。
步骤305：MME审核这7个终端是否能够预恢复核心网连接，类似的，能进行核心网连接预恢复的必要条件是MME事先存储了对应终端的核心网上下文，如果MME事先没有存储对应终端的核心网上下文，该终端不能进行核心网连接预恢复。在满足该必要条件的基础上，审核的方法也可以参考步骤303的方法，由于eNB和MME算法以及参数的差异，此外MME要考虑自身的负荷等额外因素，MME的审核结果可能会拒绝部分终端的预建立。在本例中，假设MME只允许6个终端预恢复核心网连接，MME将允许预恢复核心网连接的终端名单反馈给eNB，可通过S1口的现有信令携带该名单，例如通过初始上下文设置请求Initial Context Setup Request发送；也可以新定义一个S1口信令。
同时，MME开始预恢复所述6个终端的核心网连接，即根据MME事先存储的对应的终端上下文，为每个终端分别恢复S1口控制面承载，S1口用户面承载，NAS安全上下文等。
步骤306：eNB根据MME的名单最终确定可以进行RRC预恢复的终端， 并根据eNB存储的每个终端的AS上下文进行所述终端的RRC连接预恢复，其中包括为每个终端分别建立信令承载，数据承载，以及AS安全上下文等。
注意：在上述步骤中，终端B的RRC连接和NAS连接建立的流程不受影响，与其他终端的RRC连接和核心网连接的预恢复可并行进行。
完成RRC连接预恢复和核心网连接预恢复的终端，从LTE网络侧角度来看属于轻连接状态(light connected状态)；从5G new RAT网络角度来看属于非活动状态(inactive状态)，即终端和网络侧均保存有终端的上下文，终端的移动性采用小区重选方式，终端监听RAN和核心网的寻呼。
步骤307：5分钟后，假设组A的成员终端D要发起业务，于是向eNB发起RRC连接建立过程或者RRC连接恢复过程，在RRC连接建立请求消息或者在RRC连接恢复请求消息中上报自己的UE ID，本次RRC连接建立原因为主叫数据业务(MO-data)。其中，在步骤306之后，且在假设组A的成员终端D要发起业务之前，5分钟仅是一种举例，也可以为其他分钟数。
步骤308：eNB查询该终端D是否已经预恢复过RRC连接，如果已经预恢复过RRC连接，则直接采用预恢复的RRC连接上下文(或称AS上下文)，为终端D配置RRC连接参数并下发，同时告知MME终端D可以进行连接恢复，告知信息中应包含终端D的ID，告知信息可以携带在现有S1口信令，或者新建一个S1口信令；如果没有预恢复过RRC连接，则仍按照普通新建RRC连接的流程为终端建立RRC连接。
步骤309：MME收到eNB发送的告知信息后，采用预恢复的核心网连接为终端D传输控制面信令。
实施例8：
本实施例应用场景和实施例7相同，其区别在于在确定可进行RRC连接预恢复的终端名单时，除了实施例7所述的由MME进行最终决策之外，还可以采用下述方法：
RAN不进行步骤303，而是直接将组A的用户终端列表发给MME，由MME 进行最终决策，确定哪些用户终端可以进行RRC连接预恢复。
实施例9：
本实施例应用场景假设和实施例7相同，区别在于在确定可进行RRC连接预恢复的终端名单时，除了实施例7所述的由MME进行最终决策之外，还可以采用下述方法：
RAN不进行步骤304、305，而是直接对自己确定的可以进行RRC连接预恢复的组A的用户终端进行RRC连接预恢复。
这里分为两种实施方式：
1、RAN不将所述确定进行RRC连接预恢复的组A的用户终端名单告知MME，这样当后续有预恢复过RRC连接的终端接入网络时，为其新建核心网连接即可。
2、RAN将所述确定进行RRC连接预恢复的组A的用户终端名单告知MME，MME对该名单中包括的UE进行核心网连接预恢复。
实施例10：
以LTE系统为例，假设在RAN侧已经预定义了一个终端组A，其中包含10个终端的ID(例如S-TMSI或IMSI)，终端B(假设其属于终端组A的一员)发起主叫流程，向eNB(LTE RAN的基站)发起RRC连接建立过程；5分钟后，组A的另一个成员终端D也向eNB发起RRC连接恢复过程。
本例用以说明在新建网络连接过程中，RAN如何以组的形式提前将多个组成员的AS连接的部分上下文提前准备好，并将之用于后续的组成员终端的RRC连接建立或者恢复过程来减少空口信令开销以及减少基站的处理能力消耗的。
步骤401：终端B向eNB发起RRC连接建立过程，在RRC连接建立请求消息中上报自己的UE ID(S-TMSI)，本次RRC连接建立原因为MO-data(主叫数据业务)。
步骤402：eNB查询终端B是否属于某个组的成员，根据其ID确定其属于组A。
步骤403：eNB判断组A剩余的其他9个组成员终端是否有存储的AS上下文，如果没有存储的AS上下文，那么只能进行AS上下文新建。在本例中假设eNB没有这9个组成员终端存储的AS上下文，那么eNB继续确定对哪几个终端进行AS上下文新建，选择方法包括：
根据组成员的活跃度判断：如果前一次组成员的RRC连接中某组成员X没有发起连接，或者连续数次组成员X没有发起RRC连接，则认为该组成员X为不活跃成员，RAN不为该成员新建AS上下文。
根据组成员的数据周期判断：如果组成员向RAN上报过自己的数据传输周期信息，或者RAN从MME获取过所述组A的数据传输周期信息，则RAN可根据该信息确定是否要为该成员新建AS上下文；例如为：
如果当前发起连接的UE不符合组数据周期以及数据发送时间偏置，则判断这次连接是该UE的个人突发行为，不用新建AS上下文。
如果组内成员有多种数据周期，则判断哪些组成员的数据周期和数据发送时间偏置与当前发起连接的UE相符，可为相符的组员新建AS上下文。
如果当前发起连接过程的终端B的连接建立原因是被叫(Mobile Terminal Call，MT call)，且RAN没有收到过来自MME的给其他组A成员UE的寻呼paging，或者没有收到过来自MME的组A的组寻呼group paging，则认为这次MT call只是该UE的单独业务，其他组A成员不用一起新建AS上下文。
上述方法中，可以选择1种方法来辅助判断，也可以两种或三种方法结合使用。
在本例中，假设eNB判定为剩余9个终端中的7个终端进行新建AS上下文。
步骤404：eNB为选定的终端新建AS上下文，包括下述2种方式：
1、以当前正在进行连接建立的终端B的AS上下文作为蓝本，进行AS上下文新建。
2、按照预设的缺省AS上下文作为蓝本，进行AS上下文新建。
所述AS上下文分为公共部分和专有部分。
其中，所述公共部分是指可以与其他UE通用的AS上下文部分，在LTE标准中，包括下述一种或者多种：UE安全能力，服务质量(Quality of Service，QoS)信息，无线接入承载(Radio Access Bearer，RAB)信息，RRC上下文，以及切换限制列表。其中，UE安全能力和Qos信息虽然可能随终端而不同，但是对于有相同特征的同一组终端，上述AS上下文公共部分是可以通用的。
所述专有部分是指UE自己特有的，与其他UE不同的AS上下文部分，至少包括：AS安全信息，因为AS安全信息需动态更新，因此无法采用其他UE作为参照或者采用固定蓝本进行参照。
所述eNB为选定的终端新建AS上下文实际是指新建AS上下文的公共部分，终端的AS上下文的专有部分要在终端自行发起RRC连接时进行新建。
步骤405：假设5分钟后，组A的成员终端D要发起业务，于是向eNB发起RRC连接建立过程或者RRC连接恢复过程，在RRC连接建立请求消息或者在RRC连接恢复请求消息中上报自己的UE ID，本次RRC连接建立原因为主叫数据业务(MO-data)。
步骤406：eNB查询该终端D是否已经新建过AS上下文，如果已经新建过AS上下文，则根据所述新建过的上下文建立终端D的上下文的公共部分，此外eNB为终端D重新生成AS上下文的专有部分，例如：将新生成的AS安全信息发送给终端D，与终端D完成AS安全的握手以建立AS安全。
实施例11：
结合实施例7和实施例10，在步骤303和步骤403中，当eNB选择组A剩余终端中哪些终端可以进行RRC连接预恢复或者AS上下文新建时，若剩余终端中一部分在eNB没有事先保存的上下文，一部分在eNB有事先保存的上下文，那么eNB可以选择同时采用两种方法，即：对于没有事先保存AS上下文的终端进行AS上下文新建，对于有事先保存AS上下文的终端进行RRC连接预恢复。
实施例12：
本实施例描述在eNB如何以组为单位进行AS上下文保存和RRC连接恢复，包括：
以组为单位将所述终端组A的所有用户终端的前一次AS连接的终端AS上下文进行保存，为所述AS上下文存储分配对应的组A恢复ID；或者为所述终端组A中每个用户终端分配对应的恢复ID；
或者，选择所述用户终端B的前一次AS连接的AS上下文进行保存，并将所述用户终端B的AS上下文的公共部分作为所述终端组A中所有用户终端的AS上下文的公共部分进行存储；为所述AS上下文存储分配对应的组A恢复ID；或者为所述终端组A中每个用户终端分配对应的恢复ID；
当组A中的用户终端B再一次要求建立AS连接时，RAN接收其发送的所述终端组A的恢复ID或者所述用户终端B的恢复ID，根据所述终端组A的恢复ID或者所述用户终端B的恢复ID查询到所述终端B对应的AS上下文存储，根据所述存储的上下文建立所述用户终端B的AS连接。
实施例13：
本实施例涉及实现上述实施例的系统，该系统包括接入网网元、核心网网元和用户终端。其中，接入网网元包括存储器(存储介质)和处理器，接入网网元的处理器通过调用接入网网元上的存储器中的程序指令(软件程序)，来实现上述实施例方案中接入网网元的功能。核心网网元包括存储器(存储介质)和处理器，核心网网元的处理器通过调用核心网网元上的存储器中的程序指令(软件程序)，来实现上述实施例方案中核心网网元的功能。存储介质是指存储程序指令数据(软件程序)的物理载体；可以是软盘、光盘、数字化视频光盘(Digital Video Disc，DVD)、硬盘、闪存、通用串行总线闪存盘(Universal Serial Bus Flash Disk，U盘)、闪存卡(Compact Flash Card，CF卡)、安全数字卡(Secure Digital Card，SD卡)、多媒体卡(Multi-Media Card，MMC卡)、智能媒体卡(Smart Media Card，SM卡)、记忆棒(Memory Stick)、照片存储卡(XD Picture Card， xD卡)等；也可以是包括上述存储产品的设备。其中：
一、接入网网元上安装的存储器中保存的程序指令实现如下功能：
当收到用户终端B发起的连接请求后，确定所述用户终端B所属的终端组；
在所述终端组中确定可进行连接预处理的用户终端；
对确定的用户终端进行连接预处理。
在一实施例中，所述可进行连接预处理的用户终端为：
可进行AS接入层上下文新建的用户终端；或者，
可进行AS连接预恢复的用户终端。
在一实施例中，对确定的用户终端进行连接预处理，包括：
根据预先存储的所述终端组中用户终端的AS上下文，对所述确定可进行AS连接预恢复的用户终端预恢复AS连接；或者，
根据所述终端组的组信息和/或所述终端组内用户终端的信息，对所述可进行AS上下文新建的用户终端建立AS上下文。
在一实施例中，可进行AS连接的预恢复的用户终端是指：在网络侧和终端侧预先均存储有AS上下文的用户终端；
可进行AS接入层上下文新建的用户终端是指：在网络侧和终端侧未存储AS上下文的用户终端。
在一实施例中，所述用户终端B发起的连接请求为：连接建立请求、连接恢复请求或者数据传输请求。
在一实施例中，确定所述用户终端B属于所述终端组，包括：
为所述终端组预分配专用的物理随机接入信道PRACH资源之后，当所述用户终端B使用所述专用PRACH资源时，则判定所述用户终端B为所述终端组中的用户终端；或者，
根据所述用户终端B上传的其ID或其所属组的组ID，判定所述用户终端B为所述终端组中的用户终端。
在一实施例中，在所述终端组中确定可进行连接预处理的用户终端，包括：
向核心网网元发送请求，以请求核心网网元确定所述终端组中可进行连接预处理的用户终端；所述请求中包含所述终端组中除用户终端B以外的全部用户终端的ID、终端组的ID或者所述用户终端B的ID；
根据所述核心网网元反馈的确认指示，得到所述终端组中确定可进行连接预处理的用户终端。
在一实施例中，建立AS上下文包括：
将所述用户终端B的AS上下文中的公共部分作为待建立AS上下文的目标用户终端的AS上下文的公共部分；或者，
预设一个AS上下文，将预设的AS上下文中的公共部分作为待建立AS上下文的目标用户终端的AS上下文的公共部分；
目标用户终端的AS上下文的专有部分则由目标用户终端与网络侧协商建立。
在一实施例中，所述预恢复AS连接包括：
将所述终端组中的所有用户终端的上一次AS连接的AS上下文进行保存；
为所述终端组分配终端组恢复ID，或者为所述终端组中每个用户终端分配对应的恢复ID；
建立预恢复AS连接时，根据接收的所述终端组的恢复ID或者用户终端的恢复ID，查找到与其对应的AS上下文；根据该AS上下文预恢复AS连接。
在一实施例中，所述预恢复AS连接包括：
保存所述用户终端B上一次AS连接的AS上下文，并将该AS上下文的公共部分作为所述终端组中所有用户终端的AS上下文的公共部分进行存储；
为所述终端组分配终端组恢复ID，或者为所述终端组中每个用户终端分配对应的恢复ID；
建立预恢复AS连接时，根据接收的所述终端组的恢复ID或者用户终端的恢复ID，查找到与其对应的AS上下文；根据该AS上下文预恢复AS连接。
在一实施例中，确定所述可进行AS上下文新建的用户终端或者可进行AS 连接的预恢复的用户终端，包括：
对于所述终端组中的用户终端，将前一次终端组中集中发起连接请求或者连接恢复请求的的用户终端，或者连续发起连接请求或者连接恢复请求的次数超过设定阈值的用户终端，确定为可进行AS上下文新建的用户终端或者可进行AS连接的预恢复的用户终端。
在一实施例中，确定所述可进行AS上下文新建的用户终端或者可进行AS连接的预恢复的用户终端，包括：
当所述终端组中的用户终端的组数据周期唯一时，将与所述用户终端B的组数据周期以及数据发送时间偏置相符的用户终端，确定为所述可进行AS上下文新建的用户终端或者可进行AS连接的预恢复的用户终端；
当所述终端组中的用户终端有多种数据周期，则将与所述用户终端B数据周期和数据发送时间偏置相符的用户终端，确定为所述可进行AS上下文新建的用户终端或者可进行AS连接的预恢复的用户终端。
在一实施例中，确定所述可进行AS上下文新建的用户终端或者可进行AS连接的预恢复的用户终端，包括：
根据核心网网元指定的可进行AS上下文新建的用户终端或者可进行AS连接的预恢复的用户终端名单，或者核心网网元指定的拒绝进行AS上下文新建的用户终端或者拒绝进行AS连接的预恢复的用户终端的用户终端名单，确定所述可进行AS上下文新建的用户终端或者可进行AS连接的预恢复的用户终端。
在一实施例中，所述AS连接的预恢复至少包括：建立信令承载、数据承载和AS安全。
二、核心网网元上安装的存储器中存储的程序指令用于实现如下功能：
接收无线接入网RAN侧发送的决策请求，请求核心网网元针对终端组中的用户终端能否进行AS上下文新建或者AS连接预恢复进行判定；
核心网网元针对该请求做出判定，并向RAN反馈允许和/或拒绝进行AS上下文新建或者AS连接预恢复的用户终端的列表。
在一实施例中，核心网网元针对该请求做出判定之后，还包括：
对该用户终端进行非接入层NAS上下文新建或者核心网连接预恢复；
其中，核心网连接预恢复包括，核心网网元根据事先保存的用户终端的核心网上下文恢复所述终端的NAS连接和S1连接，其中S1连接指核心网和RAN之间的连接。
在一实施例中，所述决策请求包括待决策的用户终端的ID列表、或者待决策的用户终端所属的预设终端组的组ID。
在一实施例中，所述核心网连接预恢复还包括：
以组为单位将预设终端组的所有用户终端的前一次核心网连接的核心网上下文进行保存，或者，选择所述终端组中的一个用户终端B的前一次核心网连接的核心网上下文进行保存，并将所述用户终端B的核心网上下文存储的公共部分当做终端组所有用户终端的核心网上下文存储的公共部分；
为所述核心网上下文存储分配对应的终端组恢复ID，或者为终端组每个用户终端分配对应的用户终端恢复ID；
当所述用户终端B再一次建立核心网连接时，接收用户终端B或RAN发送的终端组的恢复ID或者用户终端B的恢复ID；
根据终端组的恢复ID或者用户终端B的恢复ID，查询到所述用户终端B对应的核心网上下文存储，根据所述存储的核心网上下文建立所述用户终端B的核心网连接。
在上述实施例中，接入网网元的类型除了eNB之外，也包括小站small cell，家庭基站，5G new RAT以及兼容分组核心网(Evolved Packet Core，EPC)架构的其他接入网网元类型。
核心网网元的类型除了MME以外，也包括服务网关节点(CIoT Serving Gateway Node，C-SGN)和窄带物联网(Narrow Band-Intemet of Things，NBIoT)MME等支持机器类型通讯和移动性管理的核心网网元。
本领域的技术人员应该明白，上述的本公开的每个模块或每个步骤可以用 通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，在一实施例中，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，或者将它们分别制作成一个或多个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本公开不限制于任何特定的硬件和软件结合。

Claims (23)

  1. 一种连接建立方法，包括：
    接入网网元确定发起连接请求的用户终端所属的终端组；
    所述接入网网元确定所述终端组中进行连接预处理的目标用户终端；
    所述接入网网元对确定的所述目标用户终端进行所述连接预处理。
  2. 如权利要求1所述的方法，其中，所述进行连接预处理的目标用户终端为：
    进行接入层AS上下文新建的目标用户终端；或者
    进行接入层AS连接预恢复的目标用户终端。
  3. 如权利要求2所述的方法，其中，对确定的所述目标用户终端进行所述连接预处理，包括：
    当所述进行连接预处理的目标用户终端为进行AS连接预恢复的目标用户终端时，根据预先存储的所述终端组中所述目标用户终端的AS上下文，对所述目标用户终端预恢复AS连接；
    当所述进行连接预处理的目标用户终端为进行AS上下文新建的目标用户终端时，根据下述至少一项信息对所述目标用户终端建立AS上下文：所述终端组的组信息和所述终端组内的用户终端的信息。
  4. 如权利要求1所述的方法，其中，所述用户终端发起的连接请求为：连接建立请求、连接恢复请求或者数据传输请求。
  5. 如权利要求1或4所述的方法，其中，所述接入网网元确定发起连接请求的用户终端所属的终端组，包括：
    当所述发起连接请求的用户终端使用为所述终端组预分配的专用的物理随机接入信道PRACH资源时，则确定所述发起连接请求的用户终端为所述终端组中的用户终端；或者，
    根据所述发起连接请求的用户终端上传的所述发起连接请求的用户终端的标识ID或所述发起连接请求的用户终端所属终端组的组标识ID，确定所述发起 连接请求的用户终端为所述终端组中的用户终端。
  6. 如权利要求1所述的方法，其中，所述接入网网元确定所述终端组中进行连接预处理的目标用户终端，包括：
    向核心网网元发送请求，以请求所述核心网网元确定所述终端组中进行连接预处理的目标用户终端；其中，所述请求中包含：所述终端组中除所述发起连接请求的用户终端以外的全部用户终端的标识ID、所述终端组的标识ID或者所述发起连接请求的用户终端的标识ID。
    根据所述核心网网元反馈的确认指示，得到所述进行连接预处理的目标用户终端。
  7. 如权利要求3所述的连接建立方法，其中，对所述目标用户终端建立AS上下文包括：
    将所述发起连接请求的用户终端的AS上下文中的公共部分作为待建立AS上下文的目标用户终端的AS上下文的公共部分；或者，
    预设一个AS上下文，将预设的AS上下文中的公共部分作为待建立AS上下文的目标用户终端的AS上下文的公共部分；
    所述接入网网元与所述目标用户终端协商建立所述目标用户终端的AS上下文的专有部分。
  8. 如权利要求3所述的方法，其中，对所述目标用户终端预恢复AS连接包括：
    将所述终端组中的所有用户终端的上一次AS连接的AS上下文进行保存；
    为所述终端组分配终端组恢复标识ID，其中，所述组恢复标识ID对应所述终端组中的所有用户终端；当预恢复AS连接时，根据所述终端组恢复标识ID，查找与所述终端组恢复标识ID对应的所有用户终端的AS上下文；
    根据查找到的与所述终端组恢复标识ID对应的所有用户终端的AS上下文预恢复AS连接；
    或者，
    将所述终端组中的所有用户终端的上一次AS连接的AS上下文进行保存；
    为所述终端组中的每个用户终端分配对应的恢复标识ID；
    根据所述目标用户终端的恢复标识ID，查找与所述目标用户终端的恢复标识ID对应的AS上下文；
    根据查找到的与所述目标用户终端的恢复标识ID对应的AS上下文预恢复AS连接。
  9. 如权利要求3所述的方法，其中，对所述目标用户终端预恢复AS连接包括：
    保存所述发起连接请求的用户终端上一次AS连接的AS上下文，并将所述AS上下文的公共部分作为所述终端组中所有用户终端的AS上下文的公共部分进行存储；
    为所述终端组分配终端组恢复标识ID，其中，所述终端组恢复标识ID对应所述终端组中的所有用户终端；当预恢复AS连接时，根据所述终端组恢复标识ID，查找与所述终端组恢复标识ID对应的所有用户终端的AS上下文的公共部分；
    根据查找到的所述终端组恢复标识ID对应的所有用户终端的AS上下文的公共部分预恢复AS连接；或者，
    保存所述发起连接请求的用户终端上一次AS连接的AS上下文，并将所述AS上下文的公共部分作为所述终端组中所有用户终端的AS上下文的公共部分进行存储；
    为所述终端组中的每个用户终端分配对应的恢复标识ID；
    当预恢复AS连接时，根据所述目标用户终端的恢复标识ID，查找与所述目标用户终端的恢复标识ID对应的AS上下文的公共部分；
    根据查找到的与所述目标用户终端的恢复标识ID对应的AS上下文的公共部分预恢复AS连接。
  10. 如权利要求2所述的方法，其中，确定进行连接预处理的目标用户终 端，包括以下之一：
    将在所述发起连接请求的用户终端发起连接请求之前所述终端组中集中发起连接请求的用户终端，确定为进行AS上下文新建的目标用户终端或者进行AS连接预恢复的目标用户终端；
    将在所述发起连接请求的用户终端发起连接请求之前，连续发起连接请求的次数超过设定阈值的用户终端，确定为进行AS上下文新建的目标用户终端或者进行AS连接预恢复的目标用户终端。
  11. 如权利要求2所述的方法，其中，所述确定进行连接预处理的目标用户终端，包括：
    将所述终端组中与所述用户终端的数据周期以及数据发送时间偏置相符的用户终端，确定为所述进行AS上下文新建的目标用户终端或者进行AS连接预恢复的目标用户终端。
  12. 如权利要求2所述的方法，其中，确定进行连接预处理的目标用户终端，包括以下之一：
    根据所述核心网网元指定的进行AS上下文新建的目标用户终端的名单，确定所述进行AS上下文新建的目标用户终端；
    根据所述核心网网元指定的进行AS连接预恢复的目标用户终端的名单，确定所述进行AS连接预恢复的目标用户终端；
    根据所述核心网网元指定的拒绝进行AS上下文新建的目标用户终端的名单，确定所述进行AS上下文新建的目标用户终端；
    根据所述核心网网元指定的拒绝进行AS连接预恢复的目标用户终端的名单，确定所述进行AS连接预恢复的目标用户终端。
  13. 如权利要求2所述的方法，其中，所述AS连接预恢复至少包括：建立信令承载、数据承载以及AS安全。
  14. 一种连接建立方法，包括：
    核心网网元接收接入网网元发送的决策请求，其中，所述决策请求用于请 求所述核心网网元判定终端组中的待决策的用户终端能否进行连接预处理；
    核心网网元针对所述决策请求做出判定，并向接入网网元反馈判定结果，其中，所述判定结果包括以下至少之一：允许进行连接预处理的用户终端的列表和拒绝进行连接预处理的用户终端的列表。
  15. 如权利要求14所述的方法，其中，所述核心网网元判定终端组中待决策的用户终端能否进行连接预处理，包括：
    所述核心网网元判定所述终端组中的用户终端能否进行接入层AS上下文新建或者接入层AS连接预恢复；
    允许进行连接预处理的用户终端的列表，包括以下之一：允许进行AS上下文新建的用户终端的列表和允许进行AS连接预恢复的用户终端的列表；
    拒绝进行连接预处理的用户终端的列表，包括以下之一：拒绝进行AS上下文新建的用户终端的列表和拒绝进行AS连接预恢复的用户终端的列表。
  16. 如权利要求15所述的方法，在核心网网元针对所述决策请求做出判定之后，还包括：
    当所述判定结果包括允许进行AS上下文新建的用户终端的列表时，对所述列表中的用户终端进行非接入层NAS上下文新建；或者
    当所述判定结果包括允许进行AS连接预恢复的用户终端的列表时，对所述列表中的用户终端进行核心网连接预恢复；其中，核心网连接预恢复包括：所述核心网网元根据预先保存的用户终端的核心网上下文恢复所述用户终端的NAS连接和S1连接，其中，所述S1连接为所述核心网网元和所述接入网网元之间的连接。
  17. 如权利要求14或15所述的方法，其中，所述决策请求包括所述待决策的用户终端的标识ID列表、或者所述待决策的用户终端所属的终端组的组标识ID。
  18. 如权利要求16所述的方法，其中，所述核心网连接预恢复还包括：
    以组为单位将终端组的所有用户终端的上一次核心网连接的核心网上下文 进行保存，或者，选择所述终端组中发起连接请求的用户终端的上一次核心网连接的核心网上下文进行保存，并将所述发起连接请求的用户终端的核心网上下文存储的公共部分当做终端组所有用户终端的核心网上下文存储的公共部分；
    为存储的所述核心网上下文分配对应的终端组恢复标识ID，其中，所述终端组恢复标识ID对应所述终端组中的所有用户终端；当所述发起连接请求的用户终端再一次建立核心网连接时，接收所述发起连接请求的用户终端或接入网网元发送的终端组恢复标识ID；
    根据所述发起连接请求的用户终端或接入网网元发送的终端组恢复标识ID，查询到所述发起连接请求的用户终端对应的核心网上下文，根据存储的所述核心网上下文建立所述发起连接请求的用户终端的核心网连接；
    或者，
    以组为单位将终端组的所有用户终端的上一次核心网连接的核心网上下文进行保存，或者，选择所述终端组中的发起连接请求的用户终端的上一次核心网连接的核心网上下文进行保存，并将所述发起连接请求的用户终端的核心网上下文存储的公共部分当做所述终端组中所有用户终端的核心网上下文存储的公共部分；
    为所述终端组的每个用户终端分配对应的用户终端恢复标识ID；
    当所述发起连接请求的用户终端再一次建立核心网连接时，接收所述发起连接请求的用户终端或接入网网元发送的所述发起连接请求的用户终端的恢复标识ID；
    根据所述发起连接请求的用户终端的恢复标识ID，查询到所述发起连接请求的用户终端对应的核心网上下文，根据存储的所述核心网上下文建立所述发起连接请求的用户终端的核心网连接。
  19. 一种计算机可读存储介质，所述存储介质中存储有程序指令，所述程序指令被配置为实现权利要求1-13任一项所述的方法。
  20. 一种计算机可读存储介质，所述存储介质中存储有程序指令，所述程 序指令被配置为实现权利要求14-18任一项所述的方法。
  21. 一种接入网网元，包括处理器和存储器，所述存储器中存储有程序指令，所述处理器通过调用存储器中的所述程序指令，所述程序指令运行时执行权利要求1至13中任一项所述的方法。
  22. 一种核心网网元，包括处理器和存储器，所述存储器中存储有程序指令，所述处理器通过调用存储器中的所述程序指令，所述程序指令运行时执行权利要求14至18中任一项所述的方法。
  23. 一种系统，包括权利要求21所述的接入网网元、权利要求22所述的核心网网元，以及用户终端。
PCT/CN2018/096751 2017-07-24 2018-07-24 连接建立方法、网元、存储介质及系统 WO2019019990A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710607456.8A CN109548170A (zh) 2017-07-24 2017-07-24 一种连接建立方法、网元、存储介质及系统
CN201710607456.8 2017-07-24

Publications (1)

Publication Number Publication Date
WO2019019990A1 true WO2019019990A1 (zh) 2019-01-31

Family

ID=65040416

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/096751 WO2019019990A1 (zh) 2017-07-24 2018-07-24 连接建立方法、网元、存储介质及系统

Country Status (2)

Country Link
CN (1) CN109548170A (zh)
WO (1) WO2019019990A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113453292A (zh) * 2020-03-25 2021-09-28 华为技术有限公司 一种建立连接的方法和通信装置以及系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101998575A (zh) * 2009-08-24 2011-03-30 华为技术有限公司 一种接入控制的方法、装置和系统
US20110080825A1 (en) * 2008-01-18 2011-04-07 Telefonaktiebolaget Lm Ericsson (Publ) Method and Apparatus for Radio Link Failure Recovery in a Telecommunication System
CN104247553A (zh) * 2013-03-22 2014-12-24 华为技术有限公司 建立连接的方法及设备
WO2016064458A1 (en) * 2014-10-23 2016-04-28 Intel IP Corporation Connection control for machine type communication (mtc) devices
CN106961747A (zh) * 2016-01-12 2017-07-18 展讯通信（上海）有限公司 基站及配置连接恢复信息的方法、连接恢复的方法及装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2810520B1 (en) * 2012-01-31 2016-04-27 Telefonaktiebolaget LM Ericsson (publ) Connection setup with an access selection of a terminal
US9036652B2 (en) * 2012-03-16 2015-05-19 Fujitsu Limited Communication transmission system
CN103546871A (zh) * 2012-07-16 2014-01-29 普天信息技术研究院有限公司 M2m终端群组管理方法
DK3378273T3 (da) * 2015-11-17 2022-02-21 Ericsson Telefon Ab L M Fremgangsmåder og indretninger til udførelse af en genoptagelsesprocedure

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110080825A1 (en) * 2008-01-18 2011-04-07 Telefonaktiebolaget Lm Ericsson (Publ) Method and Apparatus for Radio Link Failure Recovery in a Telecommunication System
CN101998575A (zh) * 2009-08-24 2011-03-30 华为技术有限公司 一种接入控制的方法、装置和系统
CN104247553A (zh) * 2013-03-22 2014-12-24 华为技术有限公司 建立连接的方法及设备
WO2016064458A1 (en) * 2014-10-23 2016-04-28 Intel IP Corporation Connection control for machine type communication (mtc) devices
CN106961747A (zh) * 2016-01-12 2017-07-18 展讯通信（上海）有限公司 基站及配置连接恢复信息的方法、连接恢复的方法及装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113453292A (zh) * 2020-03-25 2021-09-28 华为技术有限公司 一种建立连接的方法和通信装置以及系统
CN113453292B (zh) * 2020-03-25 2023-09-01 华为技术有限公司 一种建立连接的方法和通信装置以及系统

Also Published As

Publication number Publication date
CN109548170A (zh) 2019-03-29

Similar Documents

Publication Publication Date Title
US20200396570A1 (en) Methods and apparatus for establishing a group session in a mobile network for subscribers associated with a group
CN106961456B (zh) 决定iot业务方法和设备、iot业务行为控制方法和设备
US10863436B2 (en) Apparatus and method for transceiving data by user terminal
RU2541173C2 (ru) Способ и устройство сохранения ресурса батареи в устройстве мобильной связи
US11219073B2 (en) Session connection establishment method and control plane network element
WO2020063666A1 (zh) 用户设备及其执行的方法、基站及其执行的方法、移动控制实体及其执行的方法
JP2017527182A (ja) デバイスツーデバイスリソースプールの設定方法、装置及びシステム
US20210120541A1 (en) Control of Radio Technology Usage by Scheduling Restriction
WO2012094982A1 (zh) 一种接入控制的方法及装置
CN102469519A (zh) 一种等待时间的控制方法和设备
EP2783538A1 (en) Paging off-line state terminals
CN108260192B (zh) 一种物联网终端及其省电模式的调整方法
CN102271367A (zh) 一种小数据的传输方法和设备
CN102149215A (zh) 传输保活信息的方法及终端和网络设备
US20180077628A1 (en) Terminal Discovery Method, Terminal, Server, Base Station, Management Entity, and System
WO2016180018A1 (zh) 一种接入方法及相应的接入节点、终端和通信网络
CN106162759A (zh) 决策服务质量QoS的方法、网络侧网元及系统
WO2020253627A1 (zh) 局域网隧道建立、释放的方法及设备
WO2021037130A1 (zh) 寻呼方法和设备
CN109309946B (zh) 一种拥塞控制的方法、设备及系统
WO2019019990A1 (zh) 连接建立方法、网元、存储介质及系统
WO2011116676A1 (zh) 状态迁移方法和网络设备
RU2645757C2 (ru) Способ для управления устройством пользовательского оборудования
WO2021088900A1 (zh) 一种通信方法及相关设备
WO2011124173A2 (zh) 网络拥塞处理方法和系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18837885

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18837885

Country of ref document: EP

Kind code of ref document: A1