WO2017148281A1 - 连接建立方法、用户设备、网络设备及计算机存储介质 - Google Patents

连接建立方法、用户设备、网络设备及计算机存储介质 Download PDF

Info

Publication number
WO2017148281A1
WO2017148281A1 PCT/CN2017/073935 CN2017073935W WO2017148281A1 WO 2017148281 A1 WO2017148281 A1 WO 2017148281A1 CN 2017073935 W CN2017073935 W CN 2017073935W WO 2017148281 A1 WO2017148281 A1 WO 2017148281A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
context
connection establishment
connection
response
Prior art date
Application number
PCT/CN2017/073935
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 WO2017148281A1 publication Critical patent/WO2017148281A1/zh

Links

Images

Classifications

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

Definitions

  • the present invention relates to the field of wireless communications, and in particular, to a connection establishment method, a user equipment (UE, User Equipment), a network device, and a computer storage medium.
  • UE user equipment
  • UE User Equipment
  • the embodiments of the present invention provide a connection establishment method, a UE, a network device, and a computer storage medium.
  • connection establishment method which is applied to a UE, and the method includes:
  • connection establishment request carries the first information and the second information; the first information indicates whether the UE has a context; and the second information represents context extraction information when the UE has a context;
  • the generated connection establishment request is sent to the network device.
  • the first information is included in the second information.
  • connection establishment request is radio resource control (RRC, Radio Resource). Control) Connection establishment request.
  • RRC Radio Resource control
  • the generating a connection establishment request includes:
  • the RRC connection setup request includes a context identifier (ID);
  • the context activation option is first information; the context ID is second information.
  • the generating a connection establishment request includes:
  • IE Information Element
  • the context ID is second information.
  • the generating a connection establishment request includes:
  • the UE ID is replaced with a context ID at the UE ID of the RRC connection setup request, or a context ID is added in the RRC connection setup request.
  • the method further includes:
  • connection establishment response is further parsed to obtain fifth information; the fourth information represents scheduling required information, and the fifth information represents a conflict resolution result.
  • the sixth information when the connection establishment response is parsed, the sixth information is also obtained; and the sixth information represents the connection configuration related information.
  • the sixth information represents connection configuration information corresponding to the activation connection, or connection activation confirmation information
  • the sixth information represents connection configuration information corresponding to the complete connection.
  • the method further includes:
  • the fourth information represents scheduling required information
  • the fifth information represents a conflict resolution result.
  • the method further includes:
  • the third information indicates that the UE resource with the context competes successfully
  • the corresponding response is further parsed to obtain the fifth information.
  • the fourth information is a temporary cell radio network temporary identifier (TC-RNTI); and the fifth information is a UE identifier and/or a UE related parameter that competes for resources.
  • TC-RNTI temporary cell radio network temporary identifier
  • connection establishment method which is applied to a network device, and the method includes:
  • Parsing the connection establishment request obtaining first information and second information; the first information characterizing whether the UE has a context; and the second information characterizing context extraction information when the UE has a context;
  • a connection is established based on the acquired context of the UE.
  • the first information is included in the second information.
  • the connection establishment request is an RRC connection establishment request.
  • the parsing the connection establishment request, obtaining the first information and the second information include:
  • the context activation option is first information; the context ID is second information.
  • the parsing the connection establishment request to obtain the first information and the second information includes:
  • the context ID is second information.
  • the parsing the connection establishment request to obtain the first information and the second information includes:
  • the method further includes:
  • connection establishment response carries fourth information and fifth information; the fourth information represents scheduling required information; and the fifth information represents a conflict resolution result.
  • connection establishment response further carries sixth information; the sixth information represents connection configuration related information.
  • the sixth information represents connection configuration information corresponding to the activation connection
  • the sixth information represents connection configuration information corresponding to the complete connection.
  • the method further includes:
  • the conflict resolution response carries fourth information and fifth information;
  • the fourth information represents information required for scheduling;
  • the fifth information represents a conflict resolution result;
  • the generated corresponding response further carries the third information; the third information indicates that the UE with the context or the UE with no context competes successfully.
  • the fourth information is a TC-RNTI;
  • the fifth information is a UE identity and/or a UE related parameter that competes for resources.
  • the method further includes: when the judgment result indicates that the UE does not have a context, establishing a complete connection including context establishment.
  • the embodiment of the present invention further provides a UE, including: a first generating unit and a first sending unit;
  • the first generating unit is configured to generate a connection establishment request; the connection establishment request carries the first information and the second information; the first information indicates whether the UE has a context; and the second information indicates that the UE has the Context extraction information in context;
  • the first sending unit is configured to send the generated connection establishment request to the network device.
  • the UE further includes: a first receiving unit and a first analyzing unit; wherein
  • the first receiving unit is configured to receive a connection establishment response sent by the network device
  • the first parsing unit is configured to parse the connection establishment response to obtain fourth information; and further parse the connection establishment response to obtain fifth information; the fourth information represents scheduling required information, and the fifth Information characterizes conflict resolution results.
  • the first parsing unit is further configured to: when parsing the connection establishment response, obtain sixth information; and the sixth information represents connection configuration related information.
  • the UE further includes: a third parsing unit;
  • the first receiving unit is further configured to receive a conflict resolution response sent by the network device
  • the third parsing unit is configured to parse the conflict resolution response to obtain fourth information; and further parse the conflicting vertical response to obtain fifth information; Information is needed, and the fifth information represents a conflict resolution result.
  • the UE further includes: a second parsing unit configured to parse the received corresponding response, obtain the fourth information, and parse the received corresponding response to obtain the third information before obtaining the fifth information;
  • the corresponding response is parsed by the corresponding parsing unit to obtain the fifth information.
  • the embodiment of the present invention further provides a network device, where the device includes: a second receiving unit, a fourth analyzing unit, a determining unit, an obtaining unit, and a connection establishing unit;
  • the second receiving unit is configured to receive a connection establishment request sent by the UE;
  • the fourth parsing unit is configured to parse the connection establishment request to obtain first information and second information; the first information indicates whether the UE has a context; and the second information indicates that the UE has a context Context extraction information;
  • the determining unit is configured to determine, according to the first information, whether the UE has a context
  • the acquiring unit is configured to acquire a context of the UE by using the second information when the judgment result indicates that the UE has a context;
  • the connection establishing unit is configured to establish a connection based on the acquired context of the UE.
  • the device further includes: a second generating unit and a second sending unit; wherein
  • the second generating unit is configured to generate a connection establishment response, and the second sending unit is configured to send the connection establishment response to the UE;
  • connection establishment response carries fourth information and fifth information; the fourth information represents scheduling required information; and the fifth information represents a conflict resolution result.
  • the device further includes a third generating unit and a third sending unit, where
  • the third generating unit is configured to generate a conflict resolution response; the conflict resolution response carries fourth information and fifth information; the fourth information represents scheduling required information; and the fifth information represents a conflict resolution result;
  • the third sending unit is configured to send the conflict resolution response to the UE.
  • connection establishing unit is further configured to: when the judgment result indicates that the UE does not have a context, establish a complete connection including context establishment.
  • the embodiment of the present invention further provides a computer storage medium, the computer storage medium includes a set of instructions, when the instruction is executed, causing at least one processor to perform the connection establishment method on the UE side, or executing the network device side The connection establishment method.
  • connection establishment method the UE, the network device, and the computer storage medium provided by the embodiment of the present invention
  • the UE generates a connection establishment request;
  • the connection establishment request carries the first information and the second information; and the first information indicates whether the UE has a context
  • the second information characterizes the context extraction information when the UE has the context; and sends the generated connection establishment request to the network device; after receiving the connection establishment request sent by the UE, the network device resolves the connection establishment Requesting, obtaining the first information and the second information; determining, according to the first information, whether the UE has a context; and when the determining result indicates that the UE has a context, acquiring the context of the UE by using the second information;
  • the context of the UE, establishing a connection, and carrying the first information and the second information in the connection establishment request enables the context-enabled UE to timely and effectively inform the network of its context-related information, so that the network establishment is based on The fast connection of the context, as such, can effectively
  • FIG. 1 is a schematic diagram of a service trigger processing process in related art
  • FIG. 2 is a schematic flowchart of a method for establishing a connection on a UE side according to an embodiment of the present invention
  • FIG. 3 is a schematic flowchart of a method for establishing a connection on a network device side according to an embodiment of the present invention
  • connection establishment method 4 is a schematic flowchart of a connection establishment method according to an embodiment of the present invention.
  • FIG. 5 is a schematic flowchart of a method for establishing a connection according to Embodiment 2 of the present invention.
  • FIG. 6 is a schematic flowchart of a method for establishing a connection according to Embodiment 3 of the present invention.
  • FIG. 7 is a schematic flowchart of a method for establishing a connection according to Embodiment 4 of the present invention.
  • FIG. 8 is a schematic structural diagram of a UE according to Embodiment 5 of the present invention.
  • FIG. 9 is a schematic structural diagram of a network device according to Embodiment 5 of the present invention.
  • FIG. 10 is a schematic structural diagram of a connection establishment system according to Embodiment 5 of the present invention.
  • FIG. 11 is a schematic diagram of a processing procedure after a network device receives UE context information according to an embodiment of the present invention.
  • FIG. 1 is a schematic diagram of a process flow of a service triggering process, that is, a process flow in which a UE establishes a connection with a network side.
  • the entire flow of the RRC connection process involves 18 signaling and 265 bytes of signaling overhead.
  • the communication delay is prolonged, and on the other hand, the signaling burden Heavier.
  • the UE generates a connection establishment request; the connection establishment request carries the first information and the second information; the first information indicates whether the UE has a context; the second information Characterizing context extraction information when the UE has context; and
  • the device sends the generated connection establishment request; after receiving the connection establishment request sent by the UE, the network device parses the connection establishment request, obtains the first information and the second information, and determines, according to the first information, whether the UE has the a context; when the judgment result indicates that the UE has a context, acquiring the context of the UE by using the second information; and establishing a connection based on the acquired context of the UE.
  • This embodiment provides a connection establishment method, which is applied to a UE.
  • FIG. 2 is a schematic flowchart of a method for establishing a connection on a UE side. As shown in FIG. 2, the method includes the following steps:
  • Step 201 In the service triggering process, generate a connection establishment request.
  • connection establishment request carries the first information and the second information.
  • the first information indicates whether the UE has a context; and the second information represents context extraction information when the UE has a context.
  • the connection establishment request may be an RRC connection establishment request.
  • the specific implementation of this step may include:
  • the UE adds a context activation option in the establishment cause indication of the RRC connection setup request; and the RRC connection setup request includes a content identifier (ID, IDentity);
  • the context activation option is first information; the content ID is second information.
  • the UE ID may be replaced with the content ID at the UE ID of the RRC connection setup request; or the content ID may be added in the RRC connection setup request.
  • the specific implementation manner of replacing the UE ID with the content ID at the UE ID of the RRC connection setup request may be: filling in the content ID directly at the location of the IE of the RRC connection setup request UE ID. Rather than filling in the UE ID; it may also be: directly replacing the IE of the RRC connection setup request with the IE of the content ID, and Fill in the corresponding content ID.
  • the addition of the content ID in the RRC connection establishment request means that the content ID is added to the RRC connection establishment request, for example, the content ID may be added to the UE ID, and the resource of the UE ID is not occupied. The content ID is added after the UE ID.
  • the length of the content ID may not be the same as the length of the UE ID specified by the protocol, in other words The length of the content ID may be less than the length of the UE ID. In this case, the content ID only occupies part of the resources of the UE ID.
  • the specific implementation of this step may include:
  • the IE is used to indicate that the UE has a context; and the RRC connection establishment request includes a content ID; the content ID is a second information.
  • the UE ID may be replaced with the content ID at the UE ID of the RRC connection setup request; or the content ID may be added in the RRC connection setup request.
  • the specific implementation manner of replacing the UE ID with the content ID at the UE ID of the RRC connection setup request may be: filling in the content ID directly at the location of the IE of the RRC connection setup request UE ID.
  • the IE of the RRC connection setup request is directly replaced with the IE of the content ID, and the corresponding content ID is filled in at the location.
  • the addition of the content ID in the RRC connection establishment request means that the content ID is added to the RRC connection establishment request, for example, the content ID may be added to the UE ID, and the resource of the UE ID is not occupied. The content ID is added after the UE ID.
  • the added IE is generally 1 bit. For example, when the RRC connection setup request is incremented by 1 bit, when the value is 1, it indicates that the UE has a context; when the value is 0, it indicates that the UE does not have the upper and lower Text.
  • the length of the content ID may not be the same as the length of the UE ID specified by the protocol, in other words, content
  • the length of the ID may be less than the length of the UE ID. In this case, the content ID only occupies part of the resources of the UE ID.
  • the performance may be the traditional temporary mobile user identity (S-TMSI), (the length is 40 bits), or may be the temporary wireless network of the cell allocated by the network to the UE before the service is triggered.
  • S-TMSI temporary mobile user identity
  • the C-RNTI Cell-Radio Network Temporary Identifier
  • RAN Radio Access Network
  • the UE may directly use an existing ID as the content ID.
  • an ID established by the UE connection such as S-TMSI, is stored as the context ID of the UE.
  • the network side stores the same context ID as the UE.
  • the first information may be included in the second information. Specifically, it may be implicitly included in the second information, and the specific implementation may be in multiple manners. For example, by using the format or value of the second information (for example, using different fields, More specifically, it is assumed that the second information is a content ID, and the content ID occupies the resource of the IE of the UE ID.
  • the protocol specifies that the IE of the UE ID is 48 bits, and the first information may be represented by a 0 or a first, when the beginning is 1 The time indicates that the UE has a context, and when the beginning is 0, it indicates that the UE does not have a context) to implement implicitly including the first information in the second information.
  • Step 202 Send the generated connection establishment request to the network device.
  • the network device parses the connection establishment request, obtains the first information and the second information, and determines the UE according to the first information. Whether the context is provided; when the judgment result indicates that the UE has a context, the second information is used to acquire the context of the UE; and the connection is established based on the acquired context of the UE. Since the connection is established based on the context of the UE, during the connection establishment process, each The communication of the context of the UE is not required between the network devices, and thus, the connection can be quickly established. In other words, a quick connection is established based on the acquired context of the UE.
  • the network device may return a connection establishment response to the UE.
  • connection setup response is not only a response to the connection establishment request, but also: conflict resolution of possible collisions, and no greater delay, and saving UE waiting.
  • the network device (such as a base station) establishes a background connection (this delay is likely to be higher than the air interface delay) and re-initiates the delay of the access process.
  • the reason for sending a connection setup response is that, in actual application, as shown in FIG. 1 , in Msg1, the UE randomly selects an access preamble (Preamble), then, two UEs may just pick the same. In the case of Preamble; then for both UEs, the same scheduling information is received in msg2, and the same scheduling information is used for transmission in msg3, causing a collision of transmissions.
  • Preamble access preamble
  • the content carried by the msg4 shown in FIG. 1 includes: the UE ID or the random value + the establishment of the bearer in the msg3 and the configuration of the user media access control (MAC) layer and the physical (PHY) layer.
  • MAC user media access control
  • PHY physical
  • the method may further include:
  • connection establishment response is further parsed to obtain fifth information; the fourth information represents scheduling required information, and the fifth information represents a conflict resolution result.
  • the sixth information when parsing the connection establishment response, the sixth information is also obtained; the sixth information table Link connection configuration related information.
  • the sixth information represents connection configuration information corresponding to the activation connection, or connects activation confirmation information
  • the sixth information represents connection configuration information corresponding to the complete connection.
  • connection configuration information may be different when there is a context to establish a quick connection (activating a connection) and a context without a context to establish a complete connection.
  • the sixth information and the fourth and fifth information may be transmitted together or separately.
  • the method may further include:
  • connection establishment response is further parsed to obtain the fifth information.
  • a 1 bit identifier (third information) may be added to msg4 shown in FIG. 1 to indicate that there is a contextual UE or a contextless UE, and the contention resources are successful.
  • the UE selects whether to further read msg4 according to its own state (whether or not there is context). Specifically, when the UE has a context, selecting to further read msg4, that is, further parsing the connection establishment response, to obtain fourth information and fifth information; the fourth information represents scheduling required information, and the fifth information represents a conflict. Solve the result. When the UE does not have context, it does not choose to read msg4 further.
  • the conflict resolution result may also be separately sent. Based on this, the method may further include:
  • the fourth information represents scheduling required information
  • the fifth information represents a conflict resolution result.
  • the method further includes: before the obtaining the fifth information, the method may further include:
  • the conflict resolution response is further parsed to obtain the fifth information.
  • the fourth information refers to the scheduled ID; the fourth information may be a TC-RNTI; and the fifth information is a UE identifier and/or a UE related parameter that competes for the resource.
  • the English expression of the UE identity that contends to the resource may be a Resolution ID; the Resolution ID is the UE ID carried in the msg3 message.
  • the UE related parameter refers to a UE related parameter carried in the msg3 message.
  • connection establishment request does not carry the first information and the second information.
  • connection establishment request After the network device receives the connection establishment request, a complete connection including context establishment is established.
  • the embodiment of the invention further provides a connection establishment method, which is applied to a network device.
  • the network device refers to a centralized decision entity on the wireless network side, and the centralized decision entity is related to a future wireless network architecture.
  • the centralized decision entity is an RRC function, and the function may be located at a base station, or may be a new node different from the base station under an emerging network architecture.
  • FIG. 3 is a schematic flowchart of a method for establishing a connection on a network device side. As shown in FIG. 3, the method includes the following steps:
  • Step 301 Receive a connection establishment request sent by the UE.
  • connection establishment request may be an RRC connection setup request.
  • Step 302 Parse the connection establishment request, and obtain first information and second information.
  • the first information indicates whether the UE has a context
  • the second information represents context extraction information when the UE has a context
  • connection establishment request is an RRC connection establishment request
  • specific implementation of this step may include:
  • the network device obtains a context activation option in an establishmentcause indication of the RRC connection setup request; and obtains a content ID in the RRC connection setup request;
  • the context activation option is first information; the content ID is second information.
  • the network device obtains a content ID at a UE ID of the RRC connection establishment request, or obtains a content ID at an IE newly added by the RRC connection establishment request.
  • the UE may directly fill in the content ID at the location of the IE of the RRC connection setup request, instead of filling in the UE ID; or may be: the UE ID of the RRC connection setup request.
  • the IE is directly replaced with the content ID IE, and the corresponding content ID is filled in the location, and the network device obtains the content ID at the UE ID of the RRC connection setup request, so that the network device can establish the RRC connection.
  • the requested UE ID gets the content ID at this IE.
  • the content ID obtained by the IE added in the RRC connection establishment request is: the UE adds a content ID IE in the RRC connection establishment request, for example, the content ID may be added to the UE ID, The UE ID resource is occupied, and the content ID is added after the UE ID, so that the network device can obtain the content ID at the IE of the RRC connection setup request UE ID.
  • the length of the content ID may not be the same as the length of the UE ID specified by the protocol, in other words The length of the content ID may be less than the length of the UE ID. In this case, the content ID only occupies part of the resources of the UE ID.
  • connection establishment request is an RRC connection establishment request
  • specific implementation of this step may include:
  • the network device obtains an added IE in the RRC connection setup request, where the IE is used to indicate that the UE has a context; and obtains a content ID in the RRC connection setup request;
  • the content ID is second information.
  • the network device obtains a content ID at the UE ID of the RRC connection setup request, or obtains a content ID at an IE newly added in the RRC connection setup request.
  • the specific implementation manner in which the UE may replace the UE ID with the content ID at the UE ID of the RRC connection setup request may be: directly at the location of the IE of the RRC connection setup request UE ID
  • the content ID is filled in instead of the UE ID.
  • the IE of the RRC connection setup request is directly replaced with the IE of the content ID, and the corresponding content ID is filled in the location, so that the network device is configured.
  • the content ID may be obtained at the IE of the RRC Connection Setup Request UE ID.
  • the obtaining the content ID in the IE added by the RRC connection establishment request means that the UE adds a content ID IE in the RRC connection establishment request, for example, the content ID may be added to the UE ID, and the content ID is not occupied.
  • the resource of the UE ID is added with the content ID after the UE ID, so that the network device can obtain the content ID at the IE of the UE ID of the RRC connection establishment request.
  • the length of the content ID may not be the same as the length of the UE ID specified by the protocol, in other words The length of the content ID may be less than the length of the UE ID. In this case, the content ID only occupies part of the resources of the UE ID.
  • the added IE is generally 1 bit. For example, add 1 bit in the RRC connection setup request, when the value is 1 indicates that the UE has a context; when the value is 0, it indicates that the UE does not have a context.
  • the length of the content ID may not be the same as the length of the UE ID specified by the protocol, in other words, content
  • the length of the ID may be less than the length of the UE ID. In this case, the content ID only occupies part of the resources of the UE ID.
  • the content ID may be a traditional S-TMSI (a length of 40 bits), or may be a C-RNTI allocated by the network to the UE before the service is triggered, or may be a new cross.
  • the UE may directly use an existing ID as the content ID.
  • an ID established by the UE connection such as S-TMSI, is stored as the context ID of the UE.
  • the network side stores the same context ID as the UE.
  • the first information may be included in the second information. Specifically, it may be implicitly included in the second information, and the specific implementation may be in multiple manners. For example, by using the format or value of the second information (for example, using different fields, More specifically, it is assumed that the second information is a content ID, and the content ID occupies the resource of the IE of the UE ID.
  • the protocol specifies that the IE of the UE ID is 48 bits, and the first information may be represented by a 0 or a first, when the beginning is 1 The time indicates that the UE has a context, and when the beginning is 0, it indicates that the UE does not have a context) to implement implicitly including the first information in the second information.
  • Step 303 Determine, according to the first information, whether the UE has a context.
  • Step 304 When the judgment result indicates that the UE has a context, use the second information to acquire a context of the UE.
  • the network device may use the second information to acquire the context of the UE from other network elements that store the UE context information.
  • the network device is established to include The complete connection established below.
  • Step 305 Establish a connection based on the acquired context of the UE.
  • the network device parses the connection establishment request, obtains the first information and the second information, and determines the UE according to the first information. Whether the context is provided; when the judgment result indicates that the UE has a context, the second information is used to acquire the context of the UE; and the connection is established based on the acquired context of the UE. Since the connection is established based on the context of the UE, the network device does not need to communicate with the context of the UE again, and the connection is activated. Thus, the connection can be quickly established. In other words, a quick connection is established based on the acquired context of the UE.
  • the network device may return a connection establishment response to the UE.
  • connection setup response is not only a response to the connection establishment request, but also: conflict resolution of possible collisions, and no greater delay, and saving UE waiting.
  • the network device (such as a base station) establishes a background connection (this delay is likely to be higher than the air interface delay) and re-initiates the delay of the access process.
  • the reason for sending a connection setup response is that, in actual application, as shown in FIG. 1 , in Msg1, the UE randomly selects an access preamble (Preamble), then, two UEs may just pick the same. In the case of Preamble; then for both UEs, the same scheduling information is received in msg2, and the same scheduling information is used for transmission in msg3, causing a collision of transmissions.
  • Preamble access preamble
  • the content carried by the msg4 shown in FIG. 1 includes: the UE ID or the random value + the establishment of the bearer in the msg3 and the configuration of the user MAC layer and the PHY layer.
  • the application scenario of the embodiment of the present invention is mainly directed to a UE that already has a context, it may be considered to directly activate an existing bearer without communicating a new bearer. Therefore, only the UE ID of the assigned ID+msg3 needs to be resolved.
  • the method may further include:
  • the network device generates a connection establishment response; the connection establishment response carries fourth information and fifth information; the fourth information represents scheduling required information; and the fifth information represents a conflict resolution result;
  • connection establishment response may further carry sixth information; the sixth information represents connection configuration related information.
  • the sixth information represents connection configuration information corresponding to the activation connection, or connects activation confirmation information
  • the sixth information represents connection configuration information corresponding to the complete connection.
  • connection configuration information may be different when there is a context to establish a quick connection (activating a connection) and a context without a context to establish a complete connection.
  • connection establishment response further carries third information; the third information indicates that the UE with the context or the UE with no context competes successfully.
  • a 1-bit identifier (third information) may be added to the msg4 shown in FIG. 1 to indicate that the UE has a context or a UE without context, and the contention resource is successful.
  • the UE selects whether to further read msg4 according to its own state (whether or not there is context). Specifically, when the UE has a context, selecting to further read msg4, that is, further parsing the connection establishment response, to obtain fourth information and fifth information; the fourth information represents scheduling required information, and the fifth information represents a conflict. Solve the result. When the UE does not have context, it does not choose to read msg4 further.
  • the conflict resolution result may also be separately sent. Based on this, the method may further include:
  • the conflict resolution response carries fourth information and fifth information;
  • the fourth information represents information required for scheduling;
  • the fifth information represents a conflict resolution result;
  • the conflict resolution response further carries third information; the third information represents that the UE with the context or the UE with no context competes successfully.
  • the fourth information refers to the scheduled ID; the fourth information may be a TC-RNTI; and the fifth information is a UE identifier and/or a UE related parameter that competes for the resource.
  • the English expression of the UE identity that contends to the resource may be a Resolution ID; the Resolution ID is the UE ID carried in the msg3 message.
  • the UE related parameter refers to a UE related parameter carried in the msg3 message.
  • This embodiment also provides a connection establishment method. As shown in FIG. 4, the method includes the following steps:
  • Step 401 During the service triggering process, the UE generates a connection establishment request, and sends the generated connection establishment request to the network device.
  • connection establishment request carries the first information and the second information; the first information indicates whether the UE has a context; and the second information represents context extraction information when the UE has a context.
  • Step 402 After receiving the connection establishment request sent by the UE, the network device parses the connection establishment request to obtain the first information and the second information, and determines, according to the first information, whether the UE has a context.
  • Step 403 When the judgment result indicates that the UE has a context, the network device acquires a context of the UE by using the second information, and establishes a connection according to the obtained context of the UE.
  • connection establishment method in the service triggering process, the UE generates a connection connection
  • the first request and the second information are carried in the connection establishment request; the first information indicates whether the UE has a context; the second information represents context extraction information when the UE has a context; and the network device is Sending the generated connection establishment request; after receiving the connection establishment request sent by the UE, the network device parses the connection establishment request to obtain first information and second information; and determining, according to the first information, whether the UE has a context
  • the second information is used to acquire the context of the UE; and based on the obtained context of the UE, a connection is established, and the first information and the second information are carried in the connection establishment request.
  • the manner of information enables the context-enabled UE to inform its network context-related information in a timely and effective manner, so that the network establishes a fast connection based on the context, thus effectively reducing communication delay and signaling overhead.
  • the network device generates a connection establishment response; the connection establishment response carries fourth information and fifth information; the fourth information represents scheduling required information; the fifth information represents a conflict resolution result; to the UE Sending the connection establishment response; or, the network device generates a conflict resolution response; the conflict resolution response carries fourth information and fifth information; the fourth information represents scheduling required information; and the fifth information represents a conflict Solving the result; sending the conflict resolution response to the UE, because the UE is a UE with a context, in the process of establishing a connection, only the existing bearer needs to be activated, and no new bearer needs to be created, so The connection establishment response or the conflict resolution response only needs to carry the fourth information and the fifth information to resolve the conflict, thus further reducing the signaling overhead.
  • This embodiment describes in detail how to implement the connection establishment process on the basis of the first embodiment.
  • a method for establishing a connection includes the following steps:
  • Step 501 When the service is triggered, the UE sends an Msg1 message to the new base station, that is, sends a random access request to notify the random access preamble;
  • Step 502 After receiving the message, the new base station returns an Msg2 message to the UE, that is, returns a random connection. In response
  • Step 503 After receiving the message, the UE sends an Msg3 message, that is, an RRC connection establishment request, to the new base station.
  • the UE carrying 1 bit in the Msg3 message has a context indication or a data bearer activation indication (including a context activation option); the Msg3 message also carries a content ID.
  • Step 504 After receiving the Msg3 message, the new base station returns an Msg4 message to the UE.
  • the Msg4 message carries the TC-RNTI and the Resolution ID.
  • the Resolution ID is the UE ID carried in the msg3 message.
  • step 504 is an optional step.
  • the Msg4 message is an optional message.
  • Step 505 After receiving the Msg3 message, the new base station determines that the UE is a UE with a context, and extracts a context of the UE from the old base station that stores the UE context according to the content ID.
  • steps 504 and 505 are in no particular order, and step 504 may be performed first, and then step 505 may be performed; step 505 may be performed first, then step 504 may be performed; and steps 504 and 505 may be performed simultaneously.
  • Step 506 After receiving the message, the old base station transfers the context of the UE to the new base station.
  • Step 507 After receiving the context of the UE, the new base station sends a path switch request to the mobility management entity (MME, Mobility Management Entity).
  • MME Mobility Management Entity
  • Step 508 After receiving the request, the MME sends a data bearer modification request to the service control gateway.
  • this step is to activate the default or stored data bearer.
  • Step 509 After receiving the request, the service control gateway returns a data bearer modification confirmation to the MME.
  • Step 510 After receiving the acknowledgement, the MME sends a path switch confirmation to the new base station.
  • Step 511 After receiving the acknowledgement, the new base station sends a link activation confirmation to the UE.
  • steps 507-511 are procedures for establishing a quick connection.
  • the TC-RNTI and Resolution ID can also be carried in the link activation confirmation.
  • step 511 data transmission can be performed between the UE and the new base station.
  • the context of the UE is distributed and stored at different sites.
  • the communication flow with or without context is distinguished.
  • the context and the corresponding wireless link are quickly activated to communicate quickly.
  • the scheme of this embodiment is compared to the process of such a conventional asynchronous connection when the UE retains the context.
  • the UE is allowed to acquire the corresponding context across the cell, and the connection is quickly established. Compared with the handover, the user does not need to spend a lot of signaling for context transfer, but transfers on demand, thereby saving network overhead.
  • Msg4 only carries TC-RNTI and Resolution ID to resolve conflicts, thus further reducing signaling overhead.
  • This embodiment describes in detail how to implement the connection establishment process on the basis of the first embodiment.
  • the application scenario of this embodiment is that the wireless network side has a centralized wireless control unit, and the context can be uniformly stored in the wireless control unit, and when the UE needs it, apply for the acquisition context and the path configuration to the wireless control unit.
  • the method for establishing a connection in this embodiment includes the following steps:
  • Step 601 When the service is triggered, the UE sends an Msg1 message to the new base station, that is, sends a random access request to notify the random access preamble;
  • Step 602 After receiving the message, the new base station returns an Msg2 message to the UE, that is, returns a random access response.
  • Step 603 After receiving the message, the UE sends an Msg3 message, that is, an RRC connection establishment request, to the new base station.
  • the UE carrying 1 bit in the Msg3 message has a context indication or data bearer activation. Indication (including the context activation option); the Msg3 message also carries the content ID.
  • Step 604 After receiving the Msg3 message, the new base station returns an Msg4 message to the UE.
  • the Msg4 message carries the TC-RNTI and the Resolution ID.
  • the Resolution ID is the UE ID carried in the msg3 message.
  • step 604 is an optional step.
  • the Msg4 message is an optional message.
  • Step 605 After receiving the Msg3 message, the new base station determines that the UE is a UE with a context, and sends a bearer activation request to the wireless controller/network controller that stores the UE context according to the content ID.
  • the role of the bearer activation request is to apply for acquisition context and path configuration.
  • Step 606 After receiving the request, the wireless controller/network controller sends a data bearer activation request/modification request to the service control gateway.
  • this step is to activate the default or stored data bearer.
  • Step 607 After receiving the request, the service control gateway returns a data bearer activation confirmation/modification confirmation to the wireless controller/network controller.
  • Step 608 After receiving the acknowledgement, the wireless controller/network controller sends a bearer activation confirmation to the new base station.
  • Step 609 After receiving the acknowledgement, the new base station sends a link activation confirmation to the UE.
  • steps 605-609 are procedures for establishing a quick connection.
  • the TC-RNTI and Resolution ID can also be carried in the link activation confirmation.
  • step 609 data transmission can be performed between the UE and the new base station.
  • the context of the UE is distributed and stored in the centralized wireless control unit.
  • the communication flow with or without context is distinguished.
  • the context and the corresponding wireless link are quickly activated to communicate quickly.
  • the scheme of this embodiment is compared to the process of such a conventional asynchronous connection when the UE retains the context.
  • the UE is allowed to acquire the corresponding context across the cell, and the connection is quickly established. Compared with the handover, the user does not need to spend a lot of signaling for context transfer, but transfers on demand, thereby saving network overhead.
  • Msg4 only carries TC-RNTI and Resolution ID to resolve conflicts, thus further reducing signaling overhead.
  • This embodiment describes in detail how to implement the connection establishment process on the basis of the first embodiment.
  • the application scenario of this embodiment is: a macro-micro heterogeneous scenario, and the macro base station station stores a context; the wireless controller is carried by the macro base station.
  • the method for establishing a connection in this embodiment includes the following steps:
  • Step 701 When the service is triggered, the UE sends an Msg1 message to the new base station, that is, sends a random access request to notify the random access preamble;
  • Step 702 After receiving the message, the new base station returns an Msg2 message to the UE, that is, returns a random access response.
  • Step 703 After receiving the message, the UE sends an Msg3 message, that is, an RRC connection establishment request, to the new base station.
  • the UE carrying 1 bit in the Msg3 message has a context indication or a data bearer activation indication (including a context activation option); the Msg3 message also carries a content ID.
  • Step 704 After receiving the Msg3 message, the new base station returns an Msg4 message to the UE.
  • the Msg4 message carries the TC-RNTI and the Resolution ID.
  • the Msg4 message is an optional message.
  • the Resolution ID is the UE ID carried in the msg3 message.
  • step 704 is an optional step.
  • Step 705 After receiving the Msg3 message, the new base station determines that the UE is a UE with a context, and sends a bearer activation request to the new wireless controller/network control.
  • the request carries the content ID.
  • steps 704 and 705 is in no particular order, and step 704 may be performed first, and then step 705 may be performed; step 705 may be performed first, and then step 704 may be performed; steps 704 and 705 may also be performed simultaneously.
  • Step 706 After receiving the request, the wireless controller/network controller extracts the context of the UE from the old wireless controller/network controller storing the UE context according to the content ID.
  • Step 707 After receiving the message, the old wireless controller/network control transfers the context of the UE to the old and new wireless controller/network control;
  • Step 708 After receiving the context of the UE, the new and old wireless controller/network control sends a data bearer modification request to the service control gateway.
  • this step is to activate the default or stored data bearer.
  • Step 709 After receiving the request, the service control gateway returns a data bearer modification confirmation to the new wireless controller/network controller.
  • Step 710 After receiving the acknowledgement, the new wireless controller/network controller sends a bearer activation confirmation to the new base station.
  • Step 711 After receiving the acknowledgement, the new base station sends a link activation confirmation to the UE.
  • steps 708-711 are procedures for establishing a quick connection.
  • the TC-RNTI and Resolution ID can also be carried in the link activation confirmation.
  • step 711 data transmission can be performed between the UE and the new base station.
  • the context of the UE is distributed and stored at different sites.
  • the communication flow with or without context is distinguished.
  • Quickly activate the context and the corresponding wireless link in case of context Communicate quickly.
  • the scheme of this embodiment is compared to the process of such a conventional asynchronous connection when the UE retains the context.
  • the UE is allowed to acquire the corresponding context across the cell, and the connection is quickly established. Compared with the handover, the user does not need to spend a lot of signaling for context transfer, but transfers on demand, thereby saving network overhead.
  • Msg4 only carries TC-RNTI and Resolution ID to resolve conflicts, thus further reducing signaling overhead.
  • the embodiment provides a UE.
  • the UE includes: a first generating unit 81 and a first sending unit 82.
  • the first generating unit 81 is configured to generate a connection establishment request during the service triggering process; the connection establishment request carries the first information and the second information; the first information indicates whether the UE has a context; and the second Information characterizing the context extraction information when the UE has a context;
  • the first sending unit 82 is configured to send the generated connection establishment request to the network device.
  • the connection establishment request may be an RRC connection establishment request.
  • the first generating unit 81 is specifically configured to:
  • the RRC connection setup request includes a content ID
  • the context activation option is first information; the content ID is second information.
  • the first generating unit 81 may replace the UE ID with the content ID at the UE ID of the RRC connection setup request; or may add a content ID in the RRC connection setup request.
  • the specific implementation manner of replacing the UE ID with the content ID at the UE ID of the RRC connection setup request may be: the UE ID of the RRC connection setup request.
  • the location of the IE is directly filled in the content ID, instead of filling in the UE ID.
  • the IE of the RRC connection setup request is directly replaced with the IE of the content ID, and the corresponding content ID is filled in the location.
  • the addition of the content ID in the RRC connection establishment request means that the content ID is added to the RRC connection establishment request, for example, the content ID may be added to the UE ID, and the resource of the UE ID is not occupied. The content ID is added after the UE ID.
  • the length of the content ID may not be the same as the length of the UE ID specified by the protocol, in other words, The length of the content ID may be less than the length of the UE ID. In this case, the content ID only occupies part of the resources of the UE ID.
  • the first generating unit 81 is specifically configured to:
  • the IE is used to indicate that the UE has a context; and the RRC connection establishment request includes a content ID;
  • the content ID is second information.
  • the generating unit 81 may replace the UE ID with the content ID at the UE ID of the RRC connection setup request; or may add a content ID in the RRC connection setup request.
  • the specific implementation manner of replacing the UE ID with the content ID at the UE ID of the RRC connection setup request may be: filling in the content ID directly at the location of the IE of the RRC connection setup request UE ID.
  • the IE of the RRC connection setup request is directly replaced with the IE of the content ID, and the corresponding content ID is filled in at the location.
  • the addition of the content ID in the RRC connection establishment request means that the content ID is added to the RRC connection establishment request, for example, the content ID may be added to the UE ID, and the resource of the UE ID is not occupied. The content ID is added after the UE ID.
  • the added IE is generally 1 bit. For example, when the RRC connection setup request is incremented by 1 bit, when the value is 1, it indicates that the UE has a context; when the value is 0, it indicates that the UE does not have a context.
  • the length of the content ID may not be the same as the length of the UE ID specified by the protocol.
  • the content ID The length may be less than the length of the UE ID. In this case, the content ID only occupies part of the resources of the UE ID.
  • the content ID may be a traditional S-TMSI (a length of 40 bits), or may be a C-RNTI allocated by the network to the UE before the service is triggered, or may be a new cross.
  • the first generating unit 81 may directly use an existing ID as a content ID.
  • an ID established by the UE connection such as S-TMSI, is used as the context ID of the UE. storage.
  • the network side stores the same context ID as the UE.
  • the first information may be included in the second information. Specifically, it may be implicitly included in the second information, and the specific implementation may be in multiple manners. For example, by using the format or value of the second information (for example, using different fields, More specifically, it is assumed that the second information is a content ID, and the content ID occupies the resource of the IE of the UE ID.
  • the protocol specifies that the IE of the UE ID is 48 bits, and the first information may be represented by a 0 or a first, when the beginning is 1 The time indicates that the UE has a context, and when the beginning is 0, it indicates that the UE does not have a context) to implement implicitly including the first information in the second information.
  • the network device parses the connection establishment request, obtains the first information and the second information, and determines, according to the first information, whether the UE has Context; when the judgment result indicates that the UE has a context, acquiring the context of the UE by using the second information; establishing a connection based on the acquired context of the UE Pick up. Since the connection is established based on the context of the UE, the network device does not need to communicate with the context of the UE in the connection establishment process, so that the connection can be quickly established. In other words, a quick connection is established based on the acquired context of the UE.
  • the network device may return a connection establishment response to the UE.
  • the purpose of sending the connection establishment response is to resolve the possible collisions without causing a larger delay and saving the UE waiting.
  • the network device (such as a base station) establishes a background connection (this delay is likely to be higher than the air interface delay) and re-initiates the delay of the access process.
  • the reason for sending the connection establishment response is: in actual application, as shown in FIG. 1 , in the Msg1, the UE randomly selects the Preamble by itself, then, it may happen that two UEs just pick the same Preamble; For these two UEs, the same scheduling information will be received in msg2, and the same scheduling information will be used for transmission in msg3, causing a collision of transmission.
  • the content carried by the msg4 shown in FIG. 1 includes: the UE ID or the random value + the establishment of the bearer in the msg3 and the configuration of the MAC layer and the PHY layer.
  • the application scenario of the embodiment of the present invention is mainly directed to a UE that already has a context, it may be considered to directly activate an existing bearer without communicating a new bearer. Therefore, only the UE ID of the assigned ID+msg3 needs to be resolved.
  • the UE may further include: a first receiving unit, configured to receive a connection establishment response sent by the network device.
  • the UE may further include: a first parsing unit and a second parsing unit; wherein
  • the first receiving unit is configured to receive a connection establishment response sent by the network device
  • the first parsing unit is configured to parse the connection establishment response to obtain fourth information; and after obtaining the fourth information, further parse the connection establishment response to obtain fifth information;
  • the fourth information represents information required for scheduling, and the fifth information represents a conflict resolution result.
  • the first parsing unit further obtains sixth information when parsing the connection establishment response, and the sixth information represents connection configuration related information.
  • the sixth information represents connection configuration information corresponding to the activation connection, or connects activation confirmation information
  • the sixth information represents connection configuration information corresponding to the complete connection.
  • connection configuration information may be different when there is a context to establish a quick connection (activating a connection) and a context without a context to establish a complete connection.
  • the UE may further include: a second parsing unit configured to further parse the connection establishment response after obtaining the fourth information, and parse the connection establishment response to obtain the third information before obtaining the fifth information;
  • the first parsing unit is configured to further parse the connection establishment response to obtain the fifth information when the third information indicates that the UE resource with the context has successfully competed.
  • a 1-bit identifier (third information) may be added to the msg4 shown in FIG. 1 to indicate that the UE has a context or a UE without context, and the contention resource is successful.
  • the UE selects whether to further read msg4 according to its own state (whether or not there is context). Specifically, when the UE has a context, selecting to further read msg4, that is, further parsing the connection establishment response, to obtain fourth information and fifth information; the fourth information represents scheduling required information, and the fifth information represents a conflict. Solve the result. When the UE does not have context, it does not choose to read msg4 further.
  • the conflict resolution result may be separately sent, and the UE may further include: a third parsing unit;
  • the first receiving unit is further configured to receive a conflict resolution response sent by the network device
  • the third parsing unit is configured to parse the conflict resolution response to obtain fourth information; And after obtaining the fourth information, further parsing the conflict resolution corresponding to obtain fifth information; the fourth information represents scheduling required information, and the fifth information represents a conflict resolution result.
  • the second parsing unit is configured to parse the conflict resolution response to obtain third information.
  • the third parsing unit is configured to further parse the conflict resolution response to obtain the fifth information when the third information indicates that the UE resource with the context has successfully competed.
  • the fourth information refers to the scheduled ID; the fourth information may be a TC-RNTI; and the fifth information is a UE identifier and/or a UE related parameter that competes for the resource.
  • the English expression of the UE identity that contends to the resource may be a Resolution ID; the Resolution ID is the UE ID carried in the msg3 message.
  • the UE related parameter refers to a UE related parameter carried in the msg3 message.
  • the first generating unit 81 generates a traditional connection establishment request, that is, the connection establishment request does not carry the first information and the first Two information.
  • connection establishment request After the network device receives the connection establishment request, a complete connection including context establishment is established.
  • the first generating unit 81, the first analyzing unit, the second analyzing unit, and the third analyzing unit may be a central processing unit (CPU), a microprocessor (MCU, a Micro Control Unit) in the UE. , a digital signal processor (DSP) or a programmable logic array (FPGA); the first transmitting unit 82 and the first receiving unit can be implemented by a transceiver in the UE.
  • CPU central processing unit
  • MCU microprocessor
  • Micro Control Unit Micro Control Unit
  • DSP digital signal processor
  • FPGA programmable logic array
  • the embodiment further provides a network device.
  • the device includes: a second receiving unit 91, a fourth analyzing unit 91, a determining unit 93, an obtaining unit 94, and Connection establishing unit 95; wherein
  • the second receiving unit 94 is configured to receive a connection establishment request sent by the UE;
  • the fourth parsing unit 92 is configured to parse the connection establishment request to obtain first information and second information; the first information indicates whether the UE has a context; and the second information indicates that the UE has a context Context extraction information;
  • the determining unit 93 is configured to determine, according to the first information, whether the UE has a context
  • the obtaining unit 94 is configured to acquire the context of the UE by using the second information when the judgment result indicates that the UE has a context;
  • the connection establishing unit 95 is configured to establish a connection based on the acquired context of the UE.
  • the network device refers to a centralized decision entity on the wireless network side, and the centralized decision entity is related to a future wireless network architecture.
  • the centralized decision entity is an RRC function, and the function may be located at a base station, or may be a new node different from the base station under an emerging network architecture.
  • the connection establishment request may be an RRC connection setup request.
  • the fourth parsing unit 92 is specifically configured to:
  • the context activation option is first information; the content ID is second information.
  • the fourth parsing unit 92 may obtain the content ID at the UE ID of the RRC connection establishment request, or obtain the content ID at the IE newly added by the RRC connection establishment request.
  • the UE may directly fill in the content ID at the location of the IE of the RRC connection setup request, instead of filling in the UE ID; or may be: the UE ID of the RRC connection setup request.
  • the IE is directly replaced with the content ID IE, and the corresponding content ID is filled in the location, and the network device obtains the content ID at the UE ID of the RRC connection setup request, so that the fourth parsing unit 92 can be in the RRC connection
  • the content ID is obtained at the IE where the requested UE ID is established.
  • the content ID obtained by the IE added in the RRC connection setup request is: the UE adds a content ID IE in the RRC connection setup request, for example, the content ID may be added at the UEID, and the content ID is not occupied.
  • the resource of the UE ID is added, and the content ID is added after the UE ID, so that the fourth parsing unit 92 can obtain the content ID in the IE newly added in the RRC connection establishment request.
  • the length of the content ID may not be the same as the length of the UE ID specified by the protocol, in other words The length of the content ID may be less than the length of the UE ID. In this case, the content ID only occupies part of the resources of the UE ID.
  • the fourth parsing unit 92 is specifically configured to:
  • the network device obtains an added IE in the RRC connection establishment request, where the IE is used to indicate whether the UE has a context, and obtains a content ID in the RRC connection establishment request;
  • the context ID is second information.
  • the fourth parsing unit 92 may obtain the content ID at the UE ID of the RRC connection setup request, or obtain the content ID at the ID added at the UE ID of the RRC connection setup request.
  • the specific implementation manner in which the UE may replace the UE ID with the content ID at the UE ID of the RRC connection setup request may be: directly at the location of the IE of the RRC connection setup request UE ID
  • the content ID is filled in instead of the UE ID.
  • the IE of the RRC connection setup request is directly replaced with the IE of the content ID, and the corresponding content ID is filled in the location, so that the fourth The parsing unit 92 may obtain the content ID at the IE of the UE ID of the RRC connection setup request.
  • the content ID obtained by the IE added in the RRC connection establishment request refers to: the resource that does not occupy the UE ID, but the content ID is added after the UE ID, so that the fourth parsing unit 92 can be located in the
  • the content ID is obtained by adding an IE in the RRC connection establishment request.
  • the length of the content ID may not be the same as the length of the UE ID specified by the protocol, in other words The length of the content ID may be less than the length of the UE ID. In this case, the content ID only occupies part of the resources of the UE ID.
  • the added IE is generally 1 bit. For example, when the RRC connection setup request is incremented by 1 bit, when the value is 1, it indicates that the UE has a context; when the value is 0, it indicates that the UE does not have a context.
  • the length of the content ID may not be the same as the length of the UE ID specified by the protocol, in other words, content
  • the length of the ID may be less than the length of the UE ID. In this case, the content ID only occupies part of the resources of the UE ID.
  • the content ID may be a traditional S-TMSI (a length of 40 bits), or may be a C-RNTI allocated by the network to the UE before the service is triggered, or may be a new cross.
  • the UE may directly use an existing ID as the content ID.
  • an ID established by the UE connection such as S-TMSI, is stored as the context ID of the UE.
  • the network side stores the same context ID as the UE.
  • the first information may be included in the second information. Specifically, it may be implicitly included in the second information, and the specific implementation may be in multiple manners. For example, by using the format or value of the second information (for example, using different fields, More Specifically, it is assumed that the second information is a content ID, and the content ID occupies the resource of the IE of the UE ID.
  • the protocol specifies that the IE of the UE ID is 48 bits, and the first information may be represented by a 0 or 1 at the beginning, when the beginning is 1 It is indicated that the UE has a context, and when the beginning is 0, it identifies that the UE does not have a context) to implement implicitly including the first information in the second information.
  • the obtaining unit 94 may use the second information to acquire the context of the UE from other network elements that store the UE context information.
  • connection establishing unit 95 establishes a complete connection including context establishment.
  • the fourth parsing unit 92 parses the connection establishment request to obtain the first information and the second information;
  • the determining unit 93 determines, according to the first information, whether the UE has a context; when the judgment result indicates that the UE has a context, the acquiring unit 94 acquires a context of the UE by using the second information; the connection establishing unit 95 A connection is established based on the acquired context of the UE. Since the connection is established based on the context of the UE, the network device does not need to communicate with the context of the UE again, and the connection is activated. Thus, the connection can be quickly established. In other words, a quick connection is established based on the acquired context of the UE.
  • the network device may return a connection establishment response to the UE.
  • connection setup response is not only a response to the connection establishment request, but also: conflict resolution of possible collisions, and no greater delay, and saving UE waiting.
  • the network device (such as a base station) establishes a background connection (this delay is likely to be higher than the air interface delay) and re-initiates the delay of the access process.
  • the reason for sending a connection setup response is that, in actual application, as shown in FIG. 1 , in Msg1, the UE randomly selects an access preamble (Preamble), then, two UEs may just pick the same. Preamble case; then for both UEs, it will be in msg2 The same scheduling information is received, and the same scheduling information is used for transmission in msg3, causing a collision of transmission.
  • Preamble access preamble
  • the content carried by the msg4 shown in FIG. 1 includes: the UE ID or the random value + the establishment of the bearer in the msg3 and the configuration of the user MAC layer and the PHY layer.
  • the application scenario of the embodiment of the present invention is mainly directed to a UE that already has a context, it may be considered to directly activate an existing bearer without communicating a new bearer. Therefore, only the UE ID of the assigned ID+msg3 needs to be resolved.
  • the device may further include: a second generating unit and a second sending unit;
  • the second generating unit is configured to generate a connection establishment response
  • the two sending unit is configured to send the connection establishment response to the UE.
  • the connection establishment response may carry fourth information and fifth information; the fourth information represents scheduling required information; and the fifth information represents a conflict resolution result.
  • connection establishment response may further carry sixth information; the sixth information represents connection configuration related information.
  • the sixth information represents connection configuration information corresponding to the activation connection, or connects activation confirmation information
  • the sixth information represents connection configuration information corresponding to the complete connection.
  • connection configuration information may be different when there is a context to establish a quick connection (activating a connection) and a context without a context to establish a complete connection.
  • connection establishment response further carries third information; the third information indicates that the UE with the context or the UE with no context competes successfully.
  • a 1 bit identifier (third information) may be added to msg4 shown in FIG. 1 to indicate that there is a contextual UE or a contextless UE, and the contention resources are successful.
  • the conflict resolution result may be separately sent, and the device may further include: a third generating unit and a third sending unit;
  • the third generating unit is configured to generate a conflict resolution response; the conflict resolution response carries fourth information and fifth information; the fourth information represents scheduling required information; and the fifth information represents a conflict resolution result;
  • the third sending unit is configured to send the conflict resolution response to the UE.
  • the conflict resolution response further carries third information; the third information represents that the UE with the context or the UE with no context competes successfully.
  • the fourth information refers to the scheduled ID; the fourth information may be a TC-RNTI; and the fifth information is a UE identity and/or UE related parameters that compete for resources.
  • the English expression of the UE identity that contends to the resource may be a Resolution ID; the Resolution ID is the UE ID carried in the msg3 message.
  • the UE related parameter refers to a UE related parameter carried in the msg3 message.
  • the second receiving unit 91, the second sending unit, and the third sending unit may be implemented by a transceiver of the network device;
  • the fourth analyzing unit 92, the determining unit 93, the second generating unit, and the third generating unit may be implemented by a network.
  • the CPU, MCU, DSP or FPGA of the device is implemented;
  • the obtaining unit 94 and the connection establishing unit 95 can be implemented by a CPU, an MCU, a DSP or an FPGA of the network device in combination with the transceiver.
  • the embodiment further provides a connection establishment system.
  • the system includes: a UE 101 and a network device 102;
  • the UE 101 is configured to generate a connection establishment request in a service triggering process; the connection establishment request carries the first information and the second information; the first information indicates whether the UE 101 has a context; and the second information representation The UE 101 has context extraction information when context is present; and sends the generated connection establishment request to the network device 102;
  • the network device 102 is configured to receive a connection establishment request sent by the UE 101, parse the connection establishment request, obtain first information and second information, and determine, according to the first information, whether the UE 101 has a context; Determining that the UE 101 has a context, acquiring the context of the UE 101 using the second information; and establishing a connection based on the acquired context of the UE 101.
  • the UE in the service triggering process, the UE generates a connection establishment request; the connection establishment request carries the first information and the second information; the first information indicates that the UE has a context; and the second information representation
  • the UE has the context extraction information in the context; and sends the generated connection establishment request to the network device; after receiving the connection establishment request sent by the UE, the network device parses the connection establishment request to obtain the first information and Determining, according to the first information, whether the UE has a context; when the judgment result indicates that the UE has a context, acquiring the context of the UE by using the second information; and based on the acquired context of the UE, Establishing a connection, and carrying the first information and the second information in the connection establishment request, enables the context-enabled UE to timely and effectively inform the network of its context-related information, so that the network establishes a fast connection based on the context. In this way, communication delay and signaling overhead can be effectively reduced.
  • the network device generates a connection establishment response; the connection establishment response carries fourth information and fifth information; the fourth information represents scheduling required information; and the fifth information represents Dissolving the result; transmitting the connection establishment response to the UE; or the network device generates a conflict resolution response; the conflict resolution response carries fourth information and fifth information; and the fourth information represents information required for scheduling
  • the fifth information is used to represent the conflict resolution result; the conflict resolution response is sent to the UE. Since the UE is a UE with a context, in the process of establishing a connection, only the existing bearer needs to be activated, and A new bearer is created, so the connection establishment response or the conflict resolution response only needs to carry the fourth information and the fifth information to resolve the conflict, thus further reducing the signaling overhead.
  • the network device first acquires UE context-related information (step 1101), and obtains a context indication according to the acquired UE context-related information.
  • the context extracts information, then establishes a quick connection based on the context, ie, activates the connection based on the context (step 1102a); when no context is obtained according to the acquired context-related information, the network device establishes a complete connection including context establishment (step 1102b).
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention can take the form of a hardware embodiment, a software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
  • an embodiment of the present invention further provides a computer storage medium, where the computer storage medium includes a set of instructions, when the instruction is executed, causing at least one processor to perform the connection establishment method on the UE side, or perform the above Connection establishment method on the network device side.
  • the UE generates a connection establishment request; the connection establishment request carries the first information and the second information; the first information indicates whether the UE has a context; and the second information indicates that the UE has the UE Context-releasing context information; and transmitting the generated connection establishment request to the network device; after receiving the connection establishment request sent by the UE, the network device parses the connection establishment request to obtain the first information and the second information; Determining, by the first information, whether the UE has a context; when the judgment result indicates that the UE has a context, acquiring the context of the UE by using the second information; and establishing a connection according to the obtained context of the UE,
  • the manner in which the connection establishment request carries the first information and the second information enables the UE with the context to timely and effectively inform the network of its context-related information, so that the network is established. Based on the fast connection of the context, the communication delay and signaling overhead can be effectively reduced.

Abstract

本发明公开了一种连接建立方法，包括：用户设备(UE)生成连接建立请求；连接建立请求中携带第一信息及第二信息；所述第一信息表征所述UE是否具备上下文；所述第二信息表征所述UE具备上下文时的上下文提取信息；向网络设备发送生成的连接建立请求。本发明同时还公开了一种UE、网络设备及计算机存储介质。

Description

连接建立方法、用户设备、网络设备及计算机存储介质 技术领域
本发明涉及无线通信领域，尤其涉及一种连接建立方法、用户设备(UE，User Equipment)、网络设备及计算机存储介质。
背景技术
目前4G网络中，用户采用固定流程完成业务的触发和发送行为。具体流程符合3GPP TR 36.822的规定。整个流程涉及到18条信令，以及265个字节的信令开销。这样，一方面，会导致通信时延的延长；另一方面，与新兴的包括机器类型通信(MTC，Machine Type Communication)的小数据包业务自身相比，信令负担较重，如此，就难以满足低时延、低开销业务的需求。
发明内容
为解决现有存在的技术问题，本发明实施例提供一种连接建立方法、UE、网络设备及计算机存储介质。
本发明实施例的技术方案是这样实现的：
本发明实施例提供了一种连接建立方法，应用于UE，所述方法包括：
生成连接建立请求；连接建立请求中携带第一信息及第二信息；所述第一信息表征所述UE是否具备上下文；所述第二信息表征所述UE具备上下文时的上下文提取信息；
向网络设备发送生成的连接建立请求。
上述方案中，所述第一信息包含在所述第二信息中。
上述方案中，所述连接建立请求为无线资源控制(RRC，Radio Resource  Control)连接建立请求。
上述方案中，所述生成连接建立请求，包括：
在所述RRC连接建立请求的连接建立请求原因(establishmentcause)指示中添加上下文激活(context activation)选项；且所述RRC连接建立请求包含上下文标识(ID)；
所述context activation选项为第一信息；所述上下文ID为第二信息。
上述方案中，所述生成连接建立请求，包括：
在所述RRC连接建立请求中增加一信息元素(IE，Information Element)，所述IE用于指示所述UE具备上下文；且所述RRC连接建立请求包含上下文ID；
所述上下文ID为第二信息。
上述方案中，所述生成连接建立请求，包括：
在所述RRC连接建立请求的UE ID处将UE ID替换为上下文ID，或者在所述RRC连接建立请求中新增上下文ID。
上述方案中，所述方法还包括：
接收所述网络设备发送的连接建立响应；
解析所述连接建立响应，得到第四信息；
进一步解析所述连接建立响应，得到第五信息；所述第四信息表征调度所需信息，所述第五信息表征冲突解决结果。
上述方案中，解析所述连接建立响应时，还得到第六信息；所述第六信息表征连接配置相关信息。
上述方案中，当所述UE为具备上下文的UE时，所述第六信息表征激活连接对应的连接配置信息，或者连接激活确认信息；
当所述UE为不具备上下文的UE时，所述第六信息表征完整连接对应的连接配置信息。
上述方案中，所述方法还包括：
接收所述网络设备发送的冲突解决响应；
解析所述冲突解决响应，得到第四信息；
进一步解析所述冲突解决响应，得到第五信息；所述第四信息表征调度所需信息，所述第五信息表征冲突解决结果。
上述方案中，解析接收的相应响应，得到第四信息后，且在得到第五信息之前，所述方法还包括：
解析所述相应响应，得到第三信息；
当第三信息表征具备上下文的UE资源竞争成功时，进一步解析所述相应响应，得到第五信息。
上述方案中，所述第四信息为临时小区无线网络临时标识(TC-RNTI)；所述第五信息为竞争到资源的UE标识和/或UE相关参数。
本发明实施例还提供了一种连接建立方法，应用于网络设备，所述方法包括：
接收UE发送的连接建立请求；
解析所述连接建立请求，获得第一信息及第二信息；所述第一信息表征所述UE是否具备上下文；所述第二信息表征所述UE具备上下文时的上下文提取信息；
根据第一信息判断所述UE是否具备上下文；
当判断结果表征所述UE具备上下文时，利用所述第二信息获取所述UE的上下文；
基于获取的所述UE的上下文，建立连接。
上述方案中，所述第一信息包含在所述第二信息中。
上述方案中，所述连接建立请求为RRC连接建立请求。
上述方案中，所述解析所述连接建立请求，获得第一信息及第二信息， 包括：
在所述RRC连接建立请求的establishmentcause指示中获得context activation选项；并在所述RRC连接建立请求中获得上下文ID；
所述context activation选项为第一信息；所述上下文ID为第二信息。
上述方案中，所述解析所述连接建立请求，获得第一信息及第二信息，包括：
在所述RRC连接建立请求中获得增加的IE，所述IE用于指示所述UE具备上下文；并在所述RRC连接建立请求中获得上下文ID；
所述上下文ID为第二信息。
上述方案中，所述解析所述连接建立请求，获得第一信息及第二信息，包括：
在所述RRC连接建立请求的UE ID处获得上下文ID，或者在所述RRC连接建立请求新增的IE处获得上下文ID。
上述方案中，所述方法还包括：
生成连接建立响应；向所述UE发送所述连接建立响应；
所述连接建立响应携带第四信息及第五信息；所述第四信息表征调度所需信息；所述第五信息表征冲突解决结果。
上述方案中，所述连接建立响应还携带第六信息；所述第六信息表征连接配置相关信息。
上述方案中，当所述UE为具备上下文的UE时，所述第六信息表征激活连接对应的连接配置信息；
当所述UE为不具备上下文的UE时，所述第六信息表征完整连接对应的连接配置信息。
上述方案中，所述方法还包括：
生成冲突解决响应；所述冲突解决响应携带第四信息及第五信息；所 述第四信息表征调度所需信息；所述第五信息表征冲突解决结果；
向所述UE发送所述冲突解决响应。
上述方案中，生成的相应响应中还携带第三信息；所述第三信息表征具备上下文的UE或是不具备上下文的UE资源竞争成功。
上述方案中，所述第四信息为TC-RNTI；所述第五信息为竞争到资源的UE标识和/或UE相关参数。
上述方案中，所述方法还包括：当判断结果表征所述UE不具备上下文时，建立包括上下文建立的完整连接。
本发明实施例又提供了一种UE，包括：第一生成单元及第一发送单元；其中，
所述第一生成单元，配置为生成连接建立请求；连接建立请求中携带第一信息及第二信息；所述第一信息表征所述UE是否具备上下文；所述第二信息表征所述UE具备上下文时的上下文提取信息；
所述第一发送单元，配置为向网络设备发送生成的连接建立请求。
上述方案中，所述UE还包括：第一接收单元及第一解析单元；其中，
所述第一接收单元，配置为接收所述网络设备发送的连接建立响应；
所述第一解析单元，配置为解析所述连接建立响应，得到第四信息；并进一步解析所述连接建立响应，得到第五信息；所述第四信息表征调度所需信息，所述第五信息表征冲突解决结果。
上述方案中，所述第一解析单元，还配置为解析所述连接建立响应时，得到第六信息；所述第六信息表征连接配置相关信息。
上述方案中，所述UE还包括：第三解析单元；其中，
所述第一接收单元，还配置为接收所述网络设备发送的冲突解决响应；
所述第三解析单元，配置为解析所述冲突解决响应，得到第四信息；并进一步解析所述冲突立响应，得到第五信息；所述第四信息表征调度所 需信息，所述第五信息表征冲突解决结果。
上述方案中，所述UE还包括：第二解析单元，配置为解析接收的相应响应，得到第四信息后，且在得到第五信息之前，解析收到的相应响应，得到第三信息；
相应地，当第三信息表征具备上下文的UE资源竞争成功时，由相应的解析单元解析所述相应响应，得到第五信息。
本发明实施例还提供了一种网络设备，所述设备包括：第二接收单元、第四解析单元、判断单元、获取单元及连接建立单元；其中，
所述第二接收单元，配置为接收UE发送的连接建立请求；
所述第四解析单元，配置为解析所述连接建立请求，获得第一信息及第二信息；所述第一信息表征所述UE是否具备上下文；所述第二信息表征所述UE具备上下文时的上下文提取信息；
所述判断单元，配置为根据第一信息判断所述UE是否具备上下文；
所述获取单元，配置为当判断结果表征所述UE具备上下文时，利用所述第二信息获取所述UE的上下文；
所述连接建立单元，配置为基于获取的所述UE的上下文，建立连接。
上述方案中，所述设备还包括：第二生成单元及第二发送单元；其中，
所述第二生成单元，配置为生成连接建立响应；所述二发送单元，配置为向所述UE发送所述连接建立响应；
所述连接建立响应携带第四信息及第五信息；所述第四信息表征调度所需信息；所述第五信息表征冲突解决结果。
上述方案中，所述设备还包括第三生成单元及第三发送单元；其中，
所述第三生成单元，配置为生成冲突解决响应；所述冲突解决响应携带第四信息及第五信息；所述第四信息表征调度所需信息；所述第五信息表征冲突解决结果；
所述第三发送单元，配置为向所述UE发送所述冲突解决响应。
上述方案中，所述连接建立单元，还用于当判断结果表征所述UE不具备上下文时，建立包括上下文建立的完整连接。
本发明实施例还提供了一种计算机存储介质，所述计算机存储介质包括一组指令，当执行所述指令时，引起至少一个处理器执行上述UE侧的连接建立方法，或者执行上述网络设备侧的连接建立方法。
本发明实施例提供的连接建立方法、UE、网络设备及计算机存储介质，UE生成连接建立请求；连接建立请求中携带第一信息及第二信息；所述第一信息表征所述UE是否具备上下文；所述第二信息表征所述UE具备上下文时的上下文提取信息；并向网络设备发送生成的连接建立请求；接收到所述UE发送的连接建立请求后，所述网络设备解析所述连接建立请求，获得第一信息及第二信息；根据第一信息判断所述UE是否具备上下文；当判断结果表征所述UE具备上下文时，利用所述第二信息获取所述UE的上下文；并基于获取的所述UE的上下文，建立连接，通过连接建立请求中携带第一信息及第二信息的方式，能使具备上下文的UE及时、有效地将自身的上下文相关信息告知网络，以使网络建立基于所述上下文的快速连接，如此，能有效地降低通信时延及信令开销。
附图说明
在附图(其不一定是按比例绘制的)中，相似的附图标记可在不同的视图中描述相似的部件。具有不同字母后缀的相似附图标记可表示相似部件的不同示例。附图以示例而非限制的方式大体示出了本文中所讨论的各个实施例。
图1为相关技术中业务触发处理流程示意图；
图2为本发明实施例一UE侧的连接建立方法流程示意图；
图3为本发明实施例一网络设备侧的连接建立方法流程示意图；
图4为本发明实施例一连接建立方法流程示意图；
图5为本发明实施例二建立连接的实现方法流程示意图；
图6为本发明实施例三建立连接的实现方法流程示意图；
图7为本发明实施例四建立连接的实现方法流程示意图；
图8为本发明实施例五UE结构示意图；
图9为本发明实施例五网络设备结构示意图；
图10为本发明实施例五连接建立系统结构示意图；
图11为本发明实施例网络设备收到UE上下文信息后的处理过程示意图。
具体实施方式
下面结合附图及实施例对本发明再作进一步详细的描述。
在描述本发明实施例之前，先详细了解一下目前业务触发的处理流程。
图1示出了在业务触发处理流程示意图，即UE与网络侧建立连接的处理流程示意图。
结合图1所描述的流程，对连接建立过程所需要的信令及各信令对应的字节进行了总结，如表1所示。
Figure PCTCN2017073935-appb-000001
Figure PCTCN2017073935-appb-000002
表1
从表1中可以看出，RRC连接过程的整个流程涉及18条信令，以及265个字节的信令开销，如此，一方面，会导致通信时延的延长，另一方面，信令负担较重。
因此，业务触发过程中如何减少信令开销是目前亟待解决的问题。
经过对图1描述的处理流程的仔细分析可以得出：这些流程很多都是为了进行用户上下文的沟通，包括用户的标识、用户的同步、用户接入原因、用户终端的能力、用户的安全参数、用户的承载类型等。如果能保留用户的上下文，以达到在建立连接的过程中减少节约用户和网络交互的信令开销和通信时延，特别地，对于解决MTC这种偏静态、业务类型单一的业务形态，能够实现较高的效率。目前，已经有相关方提出，通过尽可能保留用户上下文，来节约用户和网络交互的信令开销和通信时延。
基于此，在本发明的各种实施例中：UE生成连接建立请求；连接建立请求中携带第一信息及第二信息；所述第一信息表征所述UE是否具备上下文；所述第二信息表征所述UE具备上下文时的上下文提取信息；并向网络 设备发送生成的连接建立请求；接收到所述UE发送的连接建立请求后，所述网络设备解析所述连接建立请求，获得第一信息及第二信息；根据第一信息判断所述UE是否具备上下文；当判断结果表征所述UE具备上下文时，利用所述第二信息获取所述UE的上下文；并基于获取的所述UE的上下文，建立连接。
实施例一
本实施例提供一种连接建立方法，应用于UE。
图2为UE侧的连接建立方法流程示意图。如图2所示，该方法包括以下步骤：
步骤201：业务触发过程中，生成连接建立请求；
这里，连接建立请求中携带第一信息及第二信息。
所述第一信息表征所述UE是否具备上下文；所述第二信息表征所述UE具备上下文时的上下文提取信息。
其中，所述连接建立请求可以为RRC连接建立请求。
基于此，在一实施例中，本步骤的具体实现可以包括：
所述UE在所述RRC连接建立请求的establishmentcause指示中添加context activation选项；且所述RRC连接建立请求包含上下文(content)标识(ID，IDentity)；
所述context activation选项为第一信息；所述content ID为第二信息。
具体地，可以在所述RRC连接建立请求的UE ID处将UE ID替换为content ID；或者，还可以在所述RRC连接建立请求中新增content ID。
这里，实际应用时，在所述RRC连接建立请求的UE ID处将UE ID替换为content ID的具体实现方式可以是：在所述RRC连接建立请求的UE ID这个IE的位置直接填写content ID，而不是填写UE ID；还可以是：将所述RRC连接建立请求的UE ID这个IE直接替换为content ID这个IE，并在该 位置填写对应的content ID。
所述在所述RRC连接建立请求中新增content ID是指：在所述RRC连接建立请求中新增content ID这个IE，比如可以在UE ID处增加content ID，不占用UE ID的资源，而是在UE ID后面再增加content ID。
其中，实际应用时，当采用在所述RRC连接建立请求的UE ID处将UE ID替换为content ID这一方案时，content ID的长度与协议规定的UE ID的长度可能不相同，换句话说，content ID的长度可能小于UE ID的长度，这种情况下，content ID只占用了UE ID这个IE的部分资源。
在另一实施例中，本步骤的具体实现可以包括：
在所述RRC连接建立请求中增加一IE，所述IE用于指示所述UE具备上下文；且所述RRC连接建立请求包含content ID；所述content ID为第二信息。
具体地，可以在所述RRC连接建立请求的UE ID处将UE ID替换为content ID；或者，还可以在所述RRC连接建立请求中新增content ID。
这里，实际应用时，在所述RRC连接建立请求的UE ID处将UE ID替换为content ID的具体实现方式可以是：在所述RRC连接建立请求的UE ID这个IE的位置直接填写content ID，而不是填写UE ID；还可以是：将所述RRC连接建立请求的UE ID这个IE直接替换为content ID这个IE，并在该位置填写对应的content ID。
所述在所述RRC连接建立请求中新增content ID是指：在所述RRC连接建立请求中新增content ID这个IE，比如可以在UE ID处增加content ID，不占用UE ID的资源，而是在UE ID后面再增加content ID。
其中，实际应用时，为了节省信令字节的开销，增加的IE一般为1比特。举个例子来说，在在所述RRC连接建立请求中增加1比特，当取值为1时，表示所述UE具备上下文；当取值为0时，表示所述UE不具备上下 文。
实际应用时，当采用在所述RRC连接建立请求的UE ID处将UE ID替换为content ID这一方案时，content ID的长度与协议规定的UE ID的长度可能不相同，换句话说，content ID的长度可能小于UE ID的长度，这种情况下，content ID只占用了UE ID的部分资源。
实际应用时，对于content ID，其表现方式可以是传统的临时移动用户身份(S-TMSI)，(长度为40bit)，也可以是所述业务触发之前网络给所述UE分配的小区无线网络临时标识(C-RNTI，Cell-Radio Network Temporary Identifier)，还可以是新的跨多个小区的无线接入网(RAN)ID。
其中，实际应用时，UE可以直接使用既有的某种ID作为content ID，举个例子来说，将UE连接建立的某个ID，比如S-TMSI，作为UE的context ID并存储。当然，网络侧与UE存储相同的context ID。
实际应用时，所述第一信息可以包含在所述第二信息中。具体地，可以隐式地包含在所述第二信息中，其具体实现形式可以是多种方式，举个例子来说，通过第二信息的格式或取值(比如：采用不同字段的方式，更具体地，假设第二信息是content ID，且content ID占用UE ID这个IE的资源，协议规定UE ID这个IE是48位，可以用开头是0或1来体现第一信息，当开头是1时表示UE是具备上下文的，开头是0时标识UE是不具备上下文的)来实现将第一信息隐式地包含在第二信息中。
步骤202：向网络设备发送生成的连接建立请求。
这里，实际应用时，所述网络设备收到所述连接建立请求后，解析所述连接建立请求，获得所述第一信息及所述第二信息；并根据所述第一信息判断所述UE是否具备上下文；当判断结果表征所述UE具备上下文时，利用所述第二信息获取所述UE的上下文；基于获取的所述UE的上下文，建立连接。由于是基于所述UE的上下文，建立连接，连接建立过程中，各 网络设备之间不需要再进行所述UE的上下文的沟通，如此，能快速建立连接。换句话说，基于获取的所述UE的上下文，建立快速连接。
相应地，所述网络设备收到所述连接建立请求后，可能会向所述UE返回连接建立响应。
实际应用时，发送连接建立响应的目的除了是对连接建立请求的一个响应外，还可以是：对可能存在的碰撞进行冲突解决，并且不会带来更大的时延，同时可以节约UE等待网络设备(比如基站)后台连接建立(这个时延很可能高于空口时延)、重新发起接入过程的时延。
其中，发送连接建立响应的原因是：实际应用时，如图1所示，在Msg1中，UE都是随机自己挑选接入前导(Preamble)，那么，就可能会出现两个UE刚好挑选了相同Preamble的情况；那么对于这两个UE，就会在msg2中接收到相同的调度信息，并且在msg3中就会使用相同的调度信息进行传输，从而引发传输的冲突。
同时，对于传统的冲突解决方案，图1所示的msg4携带的内容包括：msg3中传递的UE ID或者随机值+承载的建立以及用户媒体访问控制(MAC)层和物理(PHY)层的配置。但是，由于本发明实施例的应用场景主要针对已经具备上下文的UE的，所以可以考虑直接激活已有的承载，不需要沟通新的承载。所以就只需要调度的ID+msg3的UE ID进行冲突解决。
基于此，在一实施例中，该方法还可以包括：
接收所述网络设备发送的连接建立响应；
解析所述连接建立响应，得到第四信息；
得到第四信息后，进一步解析所述连接建立响应，得到第五信息；所述第四信息表征调度所需信息，所述第五信息表征冲突解决结果。
其中，解析所述连接建立响应时，还得到第六信息；所述第六信息表 征连接配置相关信息。
具体地，当所述UE为具备上下文的UE时，所述第六信息表征激活连接对应的连接配置信息，或者连接激活确认信息；
当所述UE为不具备上下文的UE时，所述第六信息表征完整连接对应的连接配置信息。
这里，在具备上下文建立快速连接(激活连接)和不具备上下文建立完整连接时的连接配置信息可能有所不同。
实际应用时，所述第六信息和第四、第五信息可以一起或者分开传输。
在一实施例中，所述解析所述连接建立响应，得到第四信息后，进一步解析所述连接建立响应，得到第五信息之前，该方法还可以包括：
解析所述连接建立响应，得到第三信息；
当第三信息表征具备上下文的UE资源竞争成功时，进一步解析所述连接建立响应，得到第五信息。
实际应用时，可以在图1所示的msg4中新增1bit标识(第三信息)，来指示是有上下文的UE或者无上下文的UE，竞争资源成功。UE收到后，根据自身的状态(是否具备上下文)，选择是否进一步阅读msg4。具体地，当UE具备上下文时，选择进一步阅读msg4，即进一步解析所述连接建立响应，得到第四信息及第五信息；所述第四信息表征调度所需信息，所述第五信息表征冲突解决结果。当UE不具备上下文时，不选择进一步阅读msg4。
在一实施例中，还可以单独发送冲突解决结果，基于此，该方法还可以包括：
所述UE接收所述网络设备发送的冲突解决响应；
解析所述冲突解决响应，得到第四信息；
得到第四信息后，进一步解析所述冲突解决响应，得到及第五信息； 所述第四信息表征调度所需信息，所述第五信息表征冲突解决结果。
其中，在一实施例中，所述得到第四信息后，进一步解析所述冲突解决响应，得到第五信息之前，该方法还可以包括：
解析所述冲突解决响应，得到第三信息；
当第三信息表征具备上下文的UE资源竞争成功时，进一步解析所述冲突解决响应，得到第五信息。
其中，所述第四信息就是指调度的ID；所述第四信息可以为TC-RNTI；所述第五信息为竞争到资源的UE标识和/或UE相关参数。
实际应用时，所述竞争到资源的UE标识的英文表述可以采用Resolution ID；所述Resolution ID是指msg3消息中携带的UE ID。所述UE相关参数是指msg3消息中携带的UE相关参数。
需要说明的是：实际应用时，如果所述UE是不具备上下文的UE时，则生成传统的连接建立请求，即所述连接建立请求中不携带第一信息及第二信息。
那么，所述网络设备收到连接建立请求后，会建立包含上下文建立的完整连接。
本发明实施例还提供了一种连接建立方法，应用于网络设备。
其中，所述网络设备是指：无线网络侧的集中决策实体，这个集中决策实体跟未来的无线网络架构相关。举个例子来说，当通过RRC连接来建立承载时，那么集中决策实体是一个RRC功能体，该功能体可以位于基站，也可以是在一个新兴网络架构下不同于基站的新节点。
图3为网络设备侧的连接建立方法流程示意图。如图3所示，该方法包括以下步骤：
步骤301：接收UE发送的连接建立请求；
这里，所述连接建立请求可以为RRC连接建立请求。
步骤302：解析所述连接建立请求，获得第一信息及第二信息；
这里，所述第一信息表征所述UE是否具备上下文；所述第二信息表征所述UE具备上下文时的上下文提取信息。
当所述连接建立请求为RRC连接建立请求时，在一实施例中，本步骤的具体实现可以包括：
所述网络设备在所述RRC连接建立请求的establishmentcause指示中获得context activation选项；并在所述RRC连接建立请求中获得content ID；
所述context activation选项为第一信息；所述content ID为第二信息。
具体地，所述网络设备在所述RRC连接建立请求的UE ID处获得content ID，或者在所述RRC连接建立请求新增的IE处获得content ID。
这里，实际应用时，所述UE可以在所述RRC连接建立请求的UE ID这个IE的位置直接填写content ID，而不是填写UE ID；还可以是：将所述RRC连接建立请求的UE ID这个IE直接替换为content ID这个IE，并在该位置填写对应的content ID所述网络设备在所述RRC连接建立请求的UE ID处获得content ID，从而使得所述网络设备可以在所述RRC连接建立请求的UE ID这个IE处获得content ID。
所述在所述RRC连接建立请求中新增的IE处获得content ID是指：所述UE在所述RRC连接建立请求中新增content ID这个IE，比如可以在UE ID处增加content ID，不占用UE ID的资源，而是在UE ID后面再增加content ID，从而使得所述网络设备可以在所述RRC连接建立请求的UE ID这个IE处获得content ID。
其中，实际应用时，当采用在所述RRC连接建立请求的UE ID处将UE ID替换为content ID这一方案时，content ID的长度与协议规定的UE ID的长度可能不相同，换句话说，content ID的长度可能小于UE ID的长度，这种情况下，content ID只占用了UE ID的部分资源。
当所述连接建立请求为RRC连接建立请求时，在另一实施例中，本步骤的具体实现可以包括：
所述网络设备在所述RRC连接建立请求中获得增加的IE，所述IE用于指示所述UE具备上下文；并在所述RRC连接建立请求中处获得content ID；
所述content ID为第二信息。
具体地，所述网络设备在所述RRC连接建立请求的UE ID处获得content ID，或者在所述RRC连接建立请求中新增的IE处获得content ID。
这里，实际应用时，所述UE可以在所述RRC连接建立请求的UE ID处将UE ID替换为content ID的具体实现方式可以是：在所述RRC连接建立请求的UE ID这个IE的位置直接填写content ID，而不是填写UE ID；还可以是：将所述RRC连接建立请求的UE ID这个IE直接替换为content ID这个IE，并在该位置填写对应的content ID，从而使得所述网络设备可以在所述RRC连接建立请求的UE ID这个IE处获得content ID。
所述在所述RRC连接建立请求新增的IE处获得content ID是指：所述UE在所述RRC连接建立请求中新增content ID这个IE，比如可以在UE ID处增加content ID，不占用UE ID的资源，而是在UE ID后面再增加content ID，从而使得所述网络设备可以在所述RRC连接建立请求的UE ID这个IE处获得content ID。
其中，实际应用时，当采用在所述RRC连接建立请求的UE ID处将UE ID替换为content ID这一方案时，content ID的长度与协议规定的UE ID的长度可能不相同，换句话说，content ID的长度可能小于UE ID的长度，这种情况下，content ID只占用了UE ID的部分资源。
其中，实际应用时，为了节省信令字节的开销，增加的IE一般为1比特。举个例子来说，在在所述RRC连接建立请求中增加1比特，当取值为 1时，表示所述UE具备上下文；当取值为0时，表示所述UE不具备上下文。
实际应用时，当采用在所述RRC连接建立请求的UE ID处将UE ID替换为content ID这一方案时，content ID的长度与协议规定的UE ID的长度可能不相同，换句话说，content ID的长度可能小于UE ID的长度，这种情况下，content ID只占用了UE ID的部分资源。
实际应用时，对于content ID，其表现方式可以是传统的S-TMSI，(长度为40bit)，也可以是所述业务触发之前网络给所述UE分配的C-RNTI，还可以是新的跨多个小区的RAN ID。
其中，实际应用时，UE可以直接使用既有的某种ID作为content ID，举个例子来说，将UE连接建立的某个ID，比如S-TMSI，作为UE的context ID并存储。当然，网络侧与UE存储相同的context ID。
实际应用时，所述第一信息可以包含在所述第二信息中。具体地，可以隐式地包含在所述第二信息中，其具体实现形式可以是多种方式，举个例子来说，通过第二信息的格式或取值(比如：采用不同字段的方式，更具体地，假设第二信息是content ID，且content ID占用UE ID这个IE的资源，协议规定UE ID这个IE是48位，可以用开头是0或1来体现第一信息，当开头是1时表示UE是具备上下文的，开头是0时标识UE是不具备上下文的)来实现将第一信息隐式地包含在第二信息中。
步骤303：根据第一信息判断所述UE是否具备上下文；
步骤304：当判断结果表征所述UE具备上下文时，利用所述第二信息获取所述UE的上下文；
这里，实际应用时，所述网络设备可以利用所述第二信息，从其它存储有所述UE上下文信息的网元处获取所述UE的上下文。
当判断结果表征所述UE不具备上下文时，则所述网络设备建立包括上 下文建立的完整连接。
步骤305：基于获取的所述UE的上下文，建立连接。
这里，实际应用时，所述网络设备收到所述连接建立请求后，解析所述连接建立请求，获得所述第一信息及所述第二信息；并根据所述第一信息判断所述UE是否具备上下文；当判断结果表征所述UE具备上下文时，利用所述第二信息获取所述UE的上下文；基于获取的所述UE的上下文，建立连接。由于是基于所述UE的上下文，建立连接，连接建立过程中，各网络设备之间不需要再进行所述UE的上下文的沟通，激活连接即可，如此，能快速建立连接。换句话说，基于获取的所述UE的上下文，建立快速连接。
相应地，所述网络设备收到所述连接建立请求后，可能会向所述UE返回连接建立响应。
实际应用时，发送连接建立响应的目的除了是对连接建立请求的一个响应外，还可以是：对可能存在的碰撞进行冲突解决，并且不会带来更大的时延，同时可以节约UE等待网络设备(比如基站)后台连接建立(这个时延很可能高于空口时延)、重新发起接入过程的时延。
其中，发送连接建立响应的原因是：实际应用时，如图1所示，在Msg1中，UE都是随机自己挑选接入前导(Preamble)，那么，就可能会出现两个UE刚好挑选了相同Preamble的情况；那么对于这两个UE，就会在msg2中接收到相同的调度信息，并且在msg3中就会使用相同的调度信息进行传输，从而引发传输的冲突。
同时，对于传统的冲突解决方案，图1所示的msg4携带的内容包括：msg3中传递的UE ID或者随机值+承载的建立以及用户MAC层和PHY层的配置。但是，由于本发明实施例的应用场景主要针对已经具备上下文的UE的，所以可以考虑直接激活已有的承载，不需要沟通新的承载。所以就只需要调度的ID+msg3的UE ID进行冲突解决。
基于此，在一实施例中，该方法还可以包括：
所述网络设备生成连接建立响应；所述连接建立响应携带第四信息及第五信息；所述第四信息表征调度所需信息；所述第五信息表征冲突解决结果；
向所述UE发送所述连接建立响应。
这里，所述连接建立响应中还可以携带第六信息；所述第六信息表征连接配置相关信息。
具体地，当所述UE为具备上下文的UE时，所述第六信息表征激活连接对应的连接配置信息，或者连接激活确认信息；
当所述UE为不具备上下文的UE时，所述第六信息表征完整连接对应的连接配置信息。
这里，在具备上下文建立快速连接(激活连接)和不具备上下文建立完整连接时的连接配置信息可能有所不同。
在一实施例中，所述连接建立响应中还携带第三信息；所述第三信息表征具备上下文的UE或是不具备上下文的UE资源竞争成功。
其中，实际应用时，可以在图1所示的msg4中新增1bit标识(第三信息)，来指示是有上下文的UE或者无上下文的UE，竞争资源成功。UE收到后，根据自身的状态(是否具备上下文)，选择是否进一步阅读msg4。具体地，当UE具备上下文时，选择进一步阅读msg4，即进一步解析所述连接建立响应，得到第四信息及第五信息；所述第四信息表征调度所需信息，所述第五信息表征冲突解决结果。当UE不具备上下文时，不选择进一步阅读msg4。
在一实施例中，还可以单独发送冲突解决结果，基于此，该方法还可以包括：
生成冲突解决响应；所述冲突解决响应携带第四信息及第五信息；所 述第四信息表征调度所需信息；所述第五信息表征冲突解决结果；
向所述UE发送所述冲突解决响应。
这里，在一实施例中，所冲突解决响应中还携带第三信息；所述第三信息表征具备上下文的UE或是不具备上下文的UE资源竞争成功。
其中，所述第四信息就是指调度的ID；所述第四信息可以为TC-RNTI；所述第五信息为竞争到资源的UE标识和/或UE相关参数。
实际应用时，所述竞争到资源的UE标识的英文表述可以采用Resolution ID；所述Resolution ID是指msg3消息中携带的UE ID。所述UE相关参数是指msg3消息中携带的UE相关参数。
本实施例还提供了一种连接建立方法，如图4所示，该方法包括以下步骤：
步骤401：业务触发过程中，UE生成连接建立请求；并向网络设备发送生成的连接建立请求；
这里，连接建立请求中携带第一信息及第二信息；所述第一信息表征所述UE是否具备上下文；所述第二信息表征所述UE具备上下文时的上下文提取信息。
步骤402：接收到所述UE发送的连接建立请求后，所述网络设备解析所述连接建立请求，获得第一信息及第二信息；并根据第一信息判断所述UE是否具备上下文；
步骤403：当判断结果表征所述UE具备上下文时，所述网络设备利用所述第二信息获取所述UE的上下文；并基于获取的所述UE的上下文，建立连接。
这里，需要说明的是：所述UE和网络设备的具体处理过程已在上文详述，这里不再赘述。
本发明实施例提供的连接建立方法，业务触发过程中，UE生成连接建 立请求；连接建立请求中携带第一信息及第二信息；所述第一信息表征所述UE是否具备上下文；所述第二信息表征所述UE具备上下文时的上下文提取信息；并向网络设备发送生成的连接建立请求；接收到所述UE发送的连接建立请求后，所述网络设备解析所述连接建立请求，获得第一信息及第二信息；根据第一信息判断所述UE是否具备上下文；当判断结果表征所述UE具备上下文时，利用所述第二信息获取所述UE的上下文；并基于获取的所述UE的上下文，建立连接，通过连接建立请求中携带第一信息及第二信息的方式，能使具备上下文的UE及时、有效地将自身的上下文相关信息告知网络，以使网络建立基于所述上下文的快速连接，如此，能有效地降低通信时延及信令开销。
另外，所述网络设备生成连接建立响应；所述连接建立响应携带第四信息及第五信息；所述第四信息表征调度所需信息；所述第五信息表征冲突解决结果；向所述UE发送所述连接建立响应；或者，所述网络设备生成冲突解决响应；所述冲突解决响应携带第四信息及第五信息；所述第四信息表征调度所需信息；所述第五信息表征冲突解决结果；向所述UE发送所述冲突解决响应，由于所述UE为具备上下文的UE，建立连接的过程中，只需要激活已有的承载即可，不需要创建新的承载，所以所述连接建立响应或冲突解决响应只需要携带第四信息及第五信息来解决冲突即可，如此，进一步降低了信令开销。
实施例二
本实施例在实施例一的基础上，详细描述如何实现连接建立的过程。
本实施例建立连接的实现方法，如图5所示，包括以下步骤：
步骤501：业务触发时，UE向新基站发送Msg1消息，即发送随机接入请求，以告知随机接入前导；
步骤502：新基站收到消息后，向UE返回Msg2消息，即返回随机接 入响应；
步骤503：UE收到消息后，向新基站发送Msg3消息，即RRC连接建立请求；
这里，Msg3消息中携带1比特的UE具备上下文指示或数据承载激活指示(包含context activation选项)；Msg3消息中还携带content ID。
步骤504：新基站收到Msg3消息后，向UE返回Msg4消息；
这里，Msg4消息中携带TC-RNTI及Resolution ID。
其中，Resolution ID是指msg3消息中携带的UE ID。
实际应用时，步骤504是可选步骤。Msg4消息是可选消息。
步骤505：新基站收到Msg3消息后，确定UE为具备上下文的UE，根据content ID，向存储有UE上下文的旧基站提取UE的上下文；
这里，实际应用时，步骤504和505的执行顺序不分先后，可以先执行步骤504，再执行步骤505；也可以先执行步骤505，再执行步骤504；还可以步骤504和505同时执行。
步骤506：旧基站收到消息后，将UE的上下文转移给新基站；
步骤507：新基站收到UE的上下文后，向移动性管理实体(MME，Mobility Management Entity)发送路径切换请求；
步骤508：MME收到请求后，向业务控制网关发送数据承载修改请求；
这里，本步骤执行的目的是：激活默认的或者存储的数据承载。
步骤509：业务控制网关收到请求后，向MME返回数据承载修改确认；
步骤510：MME收到确认后，向新基站发送路径切换确认；
步骤511：新基站收到确认后，向UE发送链路激活确认；
这里，步骤507～511为建立快速连接的过程。
实际应用时，若无Msg4消息，TC-RNTI及Resolution ID也可以携带在链路激活确认中。
步骤511完成后，UE与新基站之间可以进行数据传输。
从上面的描述中可以看出，本实施例中，UE的上下文分布式存储在各个不同的站点。通过在Msg3中携带上下文指示，从而区分开有无上下文的通信流程。在有上下文的情况下，快速激活上下文以及对应的无线链路，快速进行通信。可以认为是一种Context自适应的连接过程，具有高效、自适应的优点。
如果站点在同小区，UE失步，本实施例的方案与这种传统的异步连接的过程相比，当UE保留有上下文时。允许UE跨小区获取相应的上下文，快速建立连接；相比切换，用户无需耗费很多信令用于上下文转移，而是按需转移，从而节约了网络开销。
另外，Msg4中仅携带TC-RNTI及Resolution ID，以解决冲突，如此，进一步降低了信令开销。
实施例三
本实施例在实施例一的基础上，详细描述如何实现连接建立的过程。
本实施例的应用场景为：无线网络侧具有集中的无线控制单元，上下文可统一存储在这个无线控制单元，且在UE需要时，向该无线控制单元申请获取上下文，以及路径配置。
本实施例建立连接的实现方法，如图6所示，包括以下步骤：
步骤601：业务触发时，UE向新基站发送Msg1消息，即发送随机接入请求，以告知随机接入前导；
步骤602：新基站收到消息后，向UE返回Msg2消息，即返回随机接入响应；
步骤603：UE收到消息后，向新基站发送Msg3消息，即RRC连接建立请求；
这里，Msg3消息中携带1比特的UE具备上下文指示或数据承载激活 指示(包含context activation选项)；Msg3消息中还携带content ID。
步骤604：新基站收到Msg3消息后，向UE返回Msg4消息；
这里，Msg4消息中携带TC-RNTI及Resolution ID。
其中，Resolution ID是指msg3消息中携带的UE ID。
实际应用时，步骤604是可选步骤。Msg4消息为可选消息。
步骤605：新基站收到Msg3消息后，确定UE为具备上下文的UE，根据content ID，向存储有UE上下文的无线控制器/网络控制器发送承载激活请求；
这里，所述承载激活请求的作用是：申请获取上下文及路径配置。
步骤606：无线控制器/网络控制器收到请求后，向业务控制网关发送数据承载激活请求/修改请求；
这里，本步骤执行的目的是：激活默认的或者存储的数据承载。
步骤607：业务控制网关收到请求后，向无线控制器/网络控制器返回数据承载激活确认/修改确认；
步骤608：无线控制器/网络控制器收到确认后，向新基站发送承载激活确认；
步骤609：新基站收到确认后，向UE发送链路激活确认；
这里，步骤605～609为建立快速连接的过程。
实际应用时，实际应用时，若无Msg4消息，TC-RNTI及Resolution ID也可以携带在链路激活确认中。
步骤609完成后，UE与新基站之间可以进行数据传输。
从上面的描述中可以看出，本实施例中，UE的上下文分布式存储在集中的无线控制单元。通过在Msg3中携带上下文指示，从而区分开有无上下文的通信流程。在有上下文的情况下，快速激活上下文以及对应的无线链路，快速进行通信。可以认为是一种Context自适应的连接过程，具有高效、 自适应的优点。
如果站点在同小区，UE失步，本实施例的方案与这种传统的异步连接的过程相比，当UE保留有上下文时。允许UE跨小区获取相应的上下文，快速建立连接；相比切换，用户无需耗费很多信令用于上下文转移，而是按需转移，从而节约了网络开销。
另外，Msg4中仅携带TC-RNTI及Resolution ID，以解决冲突，如此，进一步降低了信令开销。
实施例四
本实施例在实施例一的基础上，详细描述如何实现连接建立的过程。
本实施例的应用场景为：宏微异构场景，且宏基站站存储上下文；无线控制器由宏基站承载。
本实施例建立连接的实现方法，如图7所示，包括以下步骤：
步骤701：业务触发时，UE向新基站发送Msg1消息，即发送随机接入请求，以告知随机接入前导；
步骤702：新基站收到消息后，向UE返回Msg2消息，即返回随机接入响应；
步骤703：UE收到消息后，向新基站发送Msg3消息，即RRC连接建立请求；
这里，Msg3消息中携带1比特的UE具备上下文指示或数据承载激活指示(包含context activation选项)；Msg3消息中还携带content ID。
步骤704：新基站收到Msg3消息后，向UE返回Msg4消息；
这里，Msg4消息中携带TC-RNTI及Resolution ID。Msg4消息是可选消息。
其中，Resolution ID是指msg3消息中携带的UE ID。
实际应用时，步骤704是可选步骤。
步骤705：新基站收到Msg3消息后，确定UE为具备上下文的UE，向新无线控制器/网络控制发送承载激活请求；
这里，请求中携带content ID。
这里，实际应用时，步骤704和705的执行顺序不分先后，可以先执行步骤704，再执行步骤705；也可以先执行步骤705，再执行步骤704；还可以步骤704和705同时执行。
步骤706：无线控制器/网络控制器收到请求后，根据content ID，向存储有UE上下文的旧无线控制器/网络控制器提取UE的上下文；
步骤707：旧无线控制器/网络控制收到消息后，将UE的上下文转移给新旧无线控制器/网络控制；
步骤708：新旧无线控制器/网络控制收到UE的上下文后，向业务控制网关发送数据承载修改请求；
这里，本步骤执行的目的是：激活默认的或者存储的数据承载。
步骤709：业务控制网关收到请求后，向新无线控制器/网络控制器返回数据承载修改确认；
步骤710：新无线控制器/网络控制器收到确认后，向新基站发送承载激活确认；
步骤711：新基站收到确认后，向UE发送链路激活确认；
这里，步骤708～711为建立快速连接的过程。
实际应用时，若无Msg4消息，TC-RNTI及Resolution ID也可以携带在链路激活确认中。
步骤711完成后，UE与新基站之间可以进行数据传输。
从上面的描述中可以看出，本实施例中，UE的上下文分布式存储在各个不同的站点。通过在Msg3中携带上下文指示，从而区分开有无上下文的通信流程。在有上下文的情况下，快速激活上下文以及对应的无线链路， 快速进行通信。可以认为是一种Context自适应的连接过程，具有高效、自适应的优点。
如果站点在同小区，UE失步，本实施例的方案与这种传统的异步连接的过程相比，当UE保留有上下文时。允许UE跨小区获取相应的上下文，快速建立连接；相比切换，用户无需耗费很多信令用于上下文转移，而是按需转移，从而节约了网络开销。
另外，Msg4中仅携带TC-RNTI及Resolution ID，以解决冲突，如此，进一步降低了信令开销。
实施例五
为实现本发明实施例的方法，本实施例提供了一种UE，如图8所示，该UE包括：第一生成单元81及第一发送单元82；其中，
所述第一生成单元81，配置为业务触发过程中，生成连接建立请求；连接建立请求中携带第一信息及第二信息；所述第一信息表征所述UE是否具备上下文；所述第二信息表征所述UE具备上下文时的上下文提取信息；
所述第一发送单元82，配置为向网络设备发送生成的连接建立请求。
其中，所述连接建立请求可以为RRC连接建立请求。
基于此，在一实施例中，所述第一生成单元81，具体配置为：
在所述RRC连接建立请求的establishmentcause指示中添加context activation选项；且所述RRC连接建立请求包含content ID；
所述context activation选项为第一信息；所述content ID为第二信息。
具体地，所述第一生成单元81可以在所述RRC连接建立请求的UE ID处将UE ID替换为content ID；或者，还可以在所述RRC连接建立请求中新增content ID。
这里，实际应用时，在所述RRC连接建立请求的UE ID处将UE ID替换为content ID的具体实现方式可以是：在所述RRC连接建立请求的UE ID 这个IE的位置直接填写content ID，而不是填写UE ID；还可以是：将所述RRC连接建立请求的UE ID这个IE直接替换为content ID这个IE，并在该位置填写对应的content ID。
所述在所述RRC连接建立请求中新增content ID是指：在所述RRC连接建立请求中新增content ID这个IE，比如可以在UE ID处增加content ID，不占用UE ID的资源，而是在UE ID后面再增加content ID。
其中，实际应用时，当采用在所述RRC连接建立请求的UE ID处将UE ID替换content ID这一方案时，content ID的长度与协议规定的UE ID的长度可能不相同，换句话说，content ID的长度可能小于UE ID的长度，这种情况下，content ID只占用了UE ID的部分资源。
在另一实施例中，所述第一生成单元81，具体配置为：
在所述RRC连接建立请求中增加一IE，所述IE用于指示所述UE具备上下文；且所述RRC连接建立请求包含content ID；
所述content ID为第二信息。
具体地，所述生成单元81可以在所述RRC连接建立请求的UE ID处将UE ID替换content ID；或者，还可以在所述RRC连接建立请求中新增content ID。
这里，实际应用时，在所述RRC连接建立请求的UE ID处将UE ID替换为content ID的具体实现方式可以是：在所述RRC连接建立请求的UE ID这个IE的位置直接填写content ID，而不是填写UE ID；还可以是：将所述RRC连接建立请求的UE ID这个IE直接替换为content ID这个IE，并在该位置填写对应的content ID。
所述在所述RRC连接建立请求中新增content ID是指：在所述RRC连接建立请求中新增content ID这个IE，比如可以在UE ID处增加content ID，不占用UE ID的资源，而是在UE ID后面再增加content ID。
其中，实际应用时，为了节省信令字节的开销，增加的IE一般为1比特。举个例子来说，在在所述RRC连接建立请求中增加1比特，当取值为1时，表示所述UE具备上下文；当取值为0时，表示所述UE不具备上下文。
实际应用时，当采用在所述RRC连接建立请求的UE ID处将UE ID替换content ID这一方案时，content ID的长度与协议规定的UE ID的长度可能不相同，换句话说，content ID的长度可能小于UE ID的长度，这种情况下，content ID只占用了UE ID的部分资源。
实际应用时，对于content ID，其表现方式可以是传统的S-TMSI，(长度为40bit)，也可以是所述业务触发之前网络给所述UE分配的C-RNTI，还可以是新的跨多个小区的RAN ID。
实际应用时，所述第一生成单元81可以直接使用既有的某种ID作为content ID，举个例子来说，将UE连接建立的某个ID，比如S-TMSI，作为UE的context ID并存储。当然，网络侧与UE存储相同的context ID。
实际应用时，所述第一信息可以包含在所述第二信息中。具体地，可以隐式地包含在所述第二信息中，其具体实现形式可以是多种方式，举个例子来说，通过第二信息的格式或取值(比如：采用不同字段的方式，更具体地，假设第二信息是content ID，且content ID占用UE ID这个IE的资源，协议规定UE ID这个IE是48位，可以用开头是0或1来体现第一信息，当开头是1时表示UE是具备上下文的，开头是0时标识UE是不具备上下文的)来实现将第一信息隐式地包含在第二信息中。
实际应用时，所述网络设备收到所述连接建立请求后，解析所述连接建立请求，获得所述第一信息及所述第二信息；并根据所述第一信息判断所述UE是否具备上下文；当判断结果表征所述UE具备上下文时，利用所述第二信息获取所述UE的上下文；基于获取的所述UE的上下文，建立连 接。由于是基于所述UE的上下文，建立连接，连接建立过程中，各网络设备之间不需要再进行所述UE的上下文的沟通，如此，能快速建立连接。换句话说，基于获取的所述UE的上下文，建立快速连接。
相应地，所述网络设备收到所述连接建立请求后，可能会向所述UE返回连接建立响应。
实际应用时，除了是对连接建立请求的一个响应外，还可以发送连接建立响应的目的是：对可能存在的碰撞进行冲突解决，并且不会带来更大的时延，同时可以节约UE等待网络设备(比如基站)后台连接建立(这个时延很可能高于空口时延)、重新发起接入过程的时延。
其中，发送连接建立响应的原因是：实际应用时，如图1所示，在Msg1中，UE都是随机自己挑选Preamble，那么，就可能会出现两个UE刚好挑选了相同Preamble的情况；那么对于这两个UE，就会在msg2中接收到相同的调度信息，并且在msg3中就会使用相同的调度信息进行传输，从而引发传输的冲突。
同时，对于传统的冲突解决方案，图1所示的msg4携带的内容包括：msg3中传递的UE ID或者随机值+承载的建立以及MAC层和PHY层的配置。但是，由于本发明实施例的应用场景主要针对已经具备上下文的UE的，所以可以考虑直接激活已有的承载，不需要沟通新的承载。所以就只需要调度的ID+msg3的UE ID进行冲突解决。
基于此，在一实施例中，该UE还可以包括：第一接收单元，配置为接收所述网络设备发送的连接建立响应。
该UE还可以包括：第一解析单元及第二解析单元；其中，
所述第一接收单元，配置为接收所述网络设备发送的连接建立响应；
所述第一解析单元，配置为解析所述连接建立响应，得到第四信息；并在得到第四信息后，进一步解析所述连接建立响应，得到第五信息；所 述第四信息表征调度所需信息，所述第五信息表征冲突解决结果。
其中，所述第一解析单元解析所述连接建立响应时，还得到第六信息；所述第六信息表征连接配置相关信息。
具体地，当所述UE为具备上下文的UE时，所述第六信息表征激活连接对应的连接配置信息，或者连接激活确认信息；
当所述UE为不具备上下文的UE时，所述第六信息表征完整连接对应的连接配置信息。
这里，在具备上下文建立快速连接(激活连接)和不具备上下文建立完整连接时的连接配置信息可能有所不同。
该UE还可以包括：第二解析单元，配置为得到第四信息后，进一步解析所述连接建立响应，得到第五信息之前，解析所述连接建立响应，得到第三信息；
相应地，所述第一解析单元，配置为当第三信息表征具备上下文的UE资源竞争成功时，进一步解析所述连接建立响应，得到第五信息。
其中，实际应用时，可以在图1所示的msg4中新增1bit标识(第三信息)，来指示是有上下文的UE或者无上下文的UE，竞争资源成功。UE收到后，根据自身的状态(是否具备上下文)，选择是否进一步阅读msg4。具体地，当UE具备上下文时，选择进一步阅读msg4，即进一步解析所述连接建立响应，得到第四信息及第五信息；所述第四信息表征调度所需信息，所述第五信息表征冲突解决结果。当UE不具备上下文时，不选择进一步阅读msg4。
在一实施例中，还可以单独发送冲突解决结果，基于此，该UE还可以包括：第三解析单元；其中，
所述第一接收单元，还配置为接收所述网络设备发送的冲突解决响应；
所述第三解析单元，配置为解析所述冲突解决响应，得到第四信息； 并在得到第四信息后，进一步解析所述冲突解决相应，得到第五信息；所述第四信息表征调度所需信息，所述第五信息表征冲突解决结果。
其中，对于上述情况，所述第二解析单元，配置为解析所述冲突解决响应，得到第三信息；
相应地，所述第三解析单元，配置为当第三信息表征具备上下文的UE资源竞争成功时，进一步解析所述冲突解决响应，得到第五信息。
其中，所述第四信息就是指调度的ID；所述第四信息可以为TC-RNTI；所述第五信息为竞争到资源的UE标识和/或UE相关参数。
实际应用时，所述竞争到资源的UE标识的英文表述可以采用Resolution ID；所述Resolution ID是指msg3消息中携带的UE ID。所述UE相关参数是指msg3消息中携带的UE相关参数。
需要说明的是：实际应用时，如果所述UE是不具备上下文的UE时，则所述第一生成单元81生成传统的连接建立请求，即所述连接建立请求中不携带第一信息及第二信息。
那么，所述网络设备收到连接建立请求后，会建立包含上下文建立的完整连接。
实际应用时，所述第一生成单元81、第一解析单元、第二解析单元及第三解析单元可由UE中的中央处理器(CPU，Central Processing Unit)、微处理器(MCU，Micro Control Unit)、数字信号处理器(DSP，Digital Signal Processor)或可编程逻辑阵列(FPGA，Field－Programmable Gate Array)实现；所述第一发送单元82及第一接收单元可由UE中的收发机实现。
为实现本发明实施例的方法，本实施例还提供了一种网络设备，如图9所示，该设备包括：第二接收单元91、第四解析单元91、判断单元93、获取单元94及连接建立单元95；其中，
所述第二接收单元94，配置为接收UE发送的连接建立请求；
所述第四解析单元92，配置为解析所述连接建立请求，获得第一信息及第二信息；所述第一信息表征所述UE是否具备上下文；所述第二信息表征所述UE具备上下文时的上下文提取信息；
所述判断单元93，配置为根据第一信息判断所述UE是否具备上下文；
所述获取单元94，配置为当判断结果表征所述UE具备上下文时，利用所述第二信息获取所述UE的上下文；
所述连接建立单元95，配置为基于获取的所述UE的上下文，建立连接。
其中，所述网络设备是指：无线网络侧的集中决策实体，这个集中决策实体跟未来的无线网络架构相关。举个例子来说，当通过RRC连接来建立承载时，那么集中决策实体是一个RRC功能体，该功能体可以位于基站，也可以是在一个新兴网络架构下不同于基站的新节点。
所述连接建立请求可以为RRC连接建立请求。
基于此，在一实施例中，所述第四解析单元92，具体配置为：
在所述RRC连接建立请求的establishmentcause指示中获得context activation选项；并在所述RRC连接建立请求中获得content ID；
所述context activation选项为第一信息；所述content ID为第二信息。
具体地，所述第四解析单元92可以在所述RRC连接建立请求的UE ID处获得content ID，或者在所述RRC连接建立请求新增的IE处获得content ID。
这里，实际应用时，所述UE可以在所述RRC连接建立请求的UE ID这个IE的位置直接填写content ID，而不是填写UE ID；还可以是：将所述RRC连接建立请求的UE ID这个IE直接替换为content ID这个IE，并在该位置填写对应的content ID所述网络设备在所述RRC连接建立请求的UE ID处获得content ID，从而使得所述第四解析单元92可以在所述RRC连接 建立请求的UE ID这个IE处获得content ID。
所述在所述RRC连接建立请求中新增的IE处获得content ID是指：所述UE在所述RRC连接建立请求中新增content ID这个IE，比如可以在UEID处增加content ID，不占用UE ID的资源，而是在UE ID后面再增加content ID，从而使得所述第四解析单元92可以在所述RRC连接建立请求中新增的IE处获得content ID。
其中，实际应用时，当采用在所述RRC连接建立请求的UE ID处将UE ID替换为content ID这一方案时，content ID的长度与协议规定的UE ID的长度可能不相同，换句话说，content ID的长度可能小于UE ID的长度，这种情况下，content ID只占用了UE ID的部分资源。
当所述连接建立请求为RRC连接建立请求时，在另一实施例中，所述第四解析单元92，具体配置为：
所述网络设备在所述RRC连接建立请求中获得增加的IE，所述IE用于指示所述UE是否具备上下文；并在所述RRC连接建立请求中获得content ID；
所述上下文ID为第二信息。
具体地，所述第四解析单元92可以在所述RRC连接建立请求的UE ID处获得content ID，或者在所述RRC连接建立请求的UE ID处增加的ID处获得content ID。
这里，实际应用时，所述UE可以在所述RRC连接建立请求的UE ID处将UE ID替换为content ID的具体实现方式可以是：在所述RRC连接建立请求的UE ID这个IE的位置直接填写content ID，而不是填写UE ID；还可以是：将所述RRC连接建立请求的UE ID这个IE直接替换为content ID这个IE，并在该位置填写对应的content ID，从而使得所述第四解析单元92可以在所述RRC连接建立请求的UE ID这个IE处获得content ID。
所述在所述RRC连接建立请求中新增的IE处获得content ID是指：不占用UE ID的资源，而是在UE ID后面再增加content ID从而使得所述第四解析单元92可以在所述RRC连接建立请求中新增的IE处获得content ID。
其中，实际应用时，当采用在所述RRC连接建立请求的UE ID处将UE ID替换为content ID这一方案时，content ID的长度与协议规定的UE ID的长度可能不相同，换句话说，content ID的长度可能小于UE ID的长度，这种情况下，content ID只占用了UE ID的部分资源。
其中，实际应用时，为了节省信令字节的开销，增加的IE一般为1比特。举个例子来说，在在所述RRC连接建立请求中增加1比特，当取值为1时，表示所述UE具备上下文；当取值为0时，表示所述UE不具备上下文。
实际应用时，当采用在所述RRC连接建立请求的UE ID处将UE ID替换为content ID这一方案时，content ID的长度与协议规定的UE ID的长度可能不相同，换句话说，content ID的长度可能小于UE ID的长度，这种情况下，content ID只占用了UE ID的部分资源。
实际应用时，对于content ID，其表现方式可以是传统的S-TMSI，(长度为40bit)，也可以是所述业务触发之前网络给所述UE分配的C-RNTI，还可以是新的跨多个小区的RAN ID。
其中，实际应用时，UE可以直接使用既有的某种ID作为content ID，举个例子来说，将UE连接建立的某个ID，比如S-TMSI，作为UE的context ID并存储。当然，网络侧与UE存储相同的context ID。
实际应用时，所述第一信息可以包含在所述第二信息中。具体地，可以隐式地包含在所述第二信息中，其具体实现形式可以是多种方式，举个例子来说，通过第二信息的格式或取值(比如：采用不同字段的方式，更 具体地，假设第二信息是content ID，且content ID占用UE ID这个IE的资源，协议规定UE ID这个IE是48位，可以用开头是0或1来体现第一信息，当开头是1时表示UE是具备上下文的，开头是0时标识UE是不具备上下文的)来实现将第一信息隐式地包含在第二信息中。
这里，实际应用时，所述获取单元94可以利用所述第二信息，从其它存储有所述UE上下文信息的网元处获取所述UE的上下文。
当判断结果表征所述UE不具备上下文时，则所述连接建立单元95建立包括上下文建立的完整连接。
实际应用时，所述第二接收单元91收到所述连接建立请求后，由所述第四解析单元92解析所述连接建立请求，获得所述第一信息及所述第二信息；所述判断单元93根据所述第一信息判断所述UE是否具备上下文；当判断结果表征所述UE具备上下文时，所述获取单元94利用所述第二信息获取所述UE的上下文；连接建立单元95基于获取的所述UE的上下文，建立连接。由于是基于所述UE的上下文，建立连接，连接建立过程中，各网络设备之间不需要再进行所述UE的上下文的沟通，激活连接即可，如此，能快速建立连接。换句话说，基于获取的所述UE的上下文，建立快速连接。
相应地，所述网络设备收到所述连接建立请求后，可能会向所述UE返回连接建立响应。
实际应用时，发送连接建立响应的目的除了是对连接建立请求的一个响应外，还可以是：对可能存在的碰撞进行冲突解决，并且不会带来更大的时延，同时可以节约UE等待网络设备(比如基站)后台连接建立(这个时延很可能高于空口时延)、重新发起接入过程的时延。
其中，发送连接建立响应的原因是：实际应用时，如图1所示，在Msg1中，UE都是随机自己挑选接入前导(Preamble)，那么，就可能会出现两个UE刚好挑选了相同Preamble的情况；那么对于这两个UE，就会在msg2 中接收到相同的调度信息，并且在msg3中就会使用相同的调度信息进行传输，从而引发传输的冲突。
同时，对于传统的冲突解决方案，图1所示的msg4携带的内容包括：msg3中传递的UE ID或者随机值+承载的建立以及用户MAC层和PHY层的配置。但是，由于本发明实施例的应用场景主要针对已经具备上下文的UE的，所以可以考虑直接激活已有的承载，不需要沟通新的承载。所以就只需要调度的ID+msg3的UE ID进行冲突解决。
基于此，在一实施例中，该设备还可以包括：第二生成单元及第二发送单元；其中，
所述第二生成单元，配置为生成连接建立响应；
所述二发送单元，配置为向所述UE发送所述连接建立响应。
其中，所述连接建立响应可以携带第四信息及第五信息；所述第四信息表征调度所需信息；所述第五信息表征冲突解决结果。
这里，所述连接建立响应中还可以携带第六信息；所述第六信息表征连接配置相关信息。
具体地，当所述UE为具备上下文的UE时，所述第六信息表征激活连接对应的连接配置信息，或者连接激活确认信息；
当所述UE为不具备上下文的UE时，所述第六信息表征完整连接对应的连接配置信息。
这里，在具备上下文建立快速连接(激活连接)和不具备上下文建立完整连接时的连接配置信息可能有所不同。
在一实施例中，所述连接建立响应中还携带第三信息；所述第三信息表征具备上下文的UE或是不具备上下文的UE资源竞争成功。
实际应用时，可以在图1所示的msg4中新增1bit标识(第三信息)，来指示是有上下文的UE或者无上下文的UE，竞争资源成功。UE收到后， 根据自身的状态(是否具备上下文)，选择是否进一步阅读msg4。具体地，当UE具备上下文时，选择进一步阅读msg4，即进一步解析所述连接建立响应，得到第四信息及第五信息；所述第四信息表征调度所需信息，所述第五信息表征冲突解决结果。当UE不具备上下文时，不选择进一步阅读msg4。
在一实施例中，还可以单独发送冲突解决结果，基于此，该设备还可以包括：第三生成单元及第三发送单元；其中，
所述第三生成单元，配置为生成冲突解决响应；所述冲突解决响应携带第四信息及第五信息；所述第四信息表征调度所需信息；所述第五信息表征冲突解决结果；
所述第三发送单元，配置为向所述UE发送所述冲突解决响应。
这里，在一实施例中，所冲突解决响应中还携带第三信息；所述第三信息表征具备上下文的UE或是不具备上下文的UE资源竞争成功。
所述第四信息就是指调度的ID；所述第四信息可以为TC-RNTI；所述第五信息为竞争到资源的UE标识和/或UE相关参数。
实际应用时，所述竞争到资源的UE标识的英文表述可以采用Resolution ID；所述Resolution ID是指msg3消息中携带的UE ID。所述UE相关参数是指msg3消息中携带的UE相关参数。
实际应用时，第二接收单元91、第二发送单元及第三发送单元可由网络设备的收发机实现；所述第四解析单元92、判断单元93、第二生成单元及第三生成单元可由网络设备的CPU、MCU、DSP或FPGA实现；所述获取单元94及连接建立单元95可由网络设备的CPU、MCU、DSP或FPGA结合收发机实现。
为实现本发明实施例的方法，本实施例还提供了一种连接建立系统， 如图10所示，该系统包括：UE 101及网络设备102；其中，
所述UE 101，配置为业务触发过程中，生成连接建立请求；连接建立请求中携带第一信息及第二信息；所述第一信息表征所述UE 101是否具备上下文；所述第二信息表征所述UE 101具备上下文时的上下文提取信息；并向所述网络设备102发送生成的连接建立请求；
所述网络设备102，配置为接收所述UE 101发送的连接建立请求；解析所述连接建立请求，获得第一信息及第二信息；根据第一信息判断所述UE 101是否具备上下文；当判断结果表征所述UE 101具备上下文时，利用所述第二信息获取所述UE 101的上下文；以及基于获取的所述UE 101的上下文，建立连接。
这里，需要说明的是：所述UE 101和网络设备102的具体功能已在上文详述，这里不再赘述。
本发明实施例提供的方案，业务触发过程中，UE生成连接建立请求；连接建立请求中携带第一信息及第二信息；所述第一信息表征所述UE具备上下文；所述第二信息表征所述UE具备上下文时的上下文提取信息；并向网络设备发送生成的连接建立请求；接收到所述UE发送的连接建立请求后，所述网络设备解析所述连接建立请求，获得第一信息及第二信息；根据第一信息判断所述UE是否具备上下文；当判断结果表征所述UE具备上下文时，利用所述第二信息获取所述UE的上下文；并基于获取的所述UE的上下文，建立连接，通过连接建立请求中携带第一信息及第二信息的方式，能使具备上下文的UE及时、有效地将自身的上下文相关信息告知网络，以使网络建立基于所述上下文的快速连接，如此，能有效地降低通信时延及信令开销。
另外，所述网络设备生成连接建立响应；所述连接建立响应携带第四信息及第五信息；所述第四信息表征调度所需信息；所述第五信息表征冲 突解决结果；向所述UE发送所述连接建立响应；或者，所述网络设备生成冲突解决响应；所述冲突解决响应携带第四信息及第五信息；所述第四信息表征调度所需信息；所述第五信息表征冲突解决结果；向所述UE发送所述冲突解决响应，由于所述UE为具备上下文的UE，建立连接的过程中，只需要激活已有的承载即可，不需要创建新的承载，所以所述连接建立响应或冲突解决响应只需要携带第四信息及第五信息来解决冲突即可，如此，进一步降低了信令开销。
综上所述，本发明实施例的方案，对于网络设备来说，如图11所示，网络设备首先获取UE上下文相关信息(步骤1101)，当根据获取的UE上下文相关信息，得到上下文指示及上下文提取信息，则基于上下文建立快速连接，即基于上下文快速激活连接(步骤1102a)；当根据获取的上下文相关信息，得到无上下文时，网络设备建立包括上下文建立的完整连接(步骤1102b)。
本领域内的技术人员应明白，本发明的实施例可提供为方法、系统、或计算机程序产品。因此，本发明可采用硬件实施例、软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功 能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
基于此，本发明实施例还提供了一种计算机存储介质，所述计算机存储介质包括一组指令，当执行所述指令时，引起至少一个处理器执行上述UE侧的连接建立方法，或者执行上述网络设备侧的连接建立方法。
以上所述，仅为本发明的较佳实施例而已，并非用于限定本发明的保护范围。
工业实用性
本发明实施例提供的方案，UE生成连接建立请求；连接建立请求中携带第一信息及第二信息；所述第一信息表征所述UE是否具备上下文；所述第二信息表征所述UE具备上下文时的上下文提取信息；并向网络设备发送生成的连接建立请求；接收到所述UE发送的连接建立请求后，所述网络设备解析所述连接建立请求，获得第一信息及第二信息；根据第一信息判断所述UE是否具备上下文；当判断结果表征所述UE具备上下文时，利用所述第二信息获取所述UE的上下文；并基于获取的所述UE的上下文，建立连接，通过连接建立请求中携带第一信息及第二信息的方式，能使具备上下文的UE及时、有效地将自身的上下文相关信息告知网络，以使网络建立 基于所述上下文的快速连接，如此，能有效地降低通信时延及信令开销。

Claims (35)

  1. 一种连接建立方法，应用于用户设备UE，所述方法包括：
    生成连接建立请求；连接建立请求中携带第一信息及第二信息；所述第一信息表征所述UE是否具备上下文；所述第二信息表征所述UE具备上下文时的上下文提取信息；
    向网络设备发送生成的连接建立请求。
  2. 根据权利要求1所述的方法，其中，所述第一信息包含在所述第二信息中。
  3. 根据权利要求1所述的方法，其中，所述连接建立请求为无线资源控制RRC连接建立请求。
  4. 根据权利要求3所述的方法，其中，所述生成连接建立请求，包括：
    在所述RRC连接建立请求的连接建立请求原因establishmentcause指示中添加上下文激活context activation选项；且所述RRC连接建立请求包含上下文ID；
    所述context activation选项为第一信息；所述上下文ID为第二信息。
  5. 根据权利要求3所述的方法，其中，所述生成连接建立请求，包括：
    在所述RRC连接建立请求中增加一信息元素IE，所述IE用于指示所述UE具备上下文；且所述RRC连接建立请求包含上下文ID；
    所述上下文ID为第二信息。
  6. 根据权利要求4或5所述的方法，其中，所述生成连接建立请求，包括：
    在所述RRC连接建立请求的UE标识ID处将UE ID替换为上下文ID，或者在所述RRC连接建立请求中新增上下文ID。
  7. 根据权利要求1所述的方法，其中，所述方法还包括：
    接收所述网络设备发送的连接建立响应；
    解析所述连接建立响应，得到第四信息；
    进一步解析所述连接建立响应，得到第五信息；所述第四信息表征调度所需信息，所述第五信息表征冲突解决结果。
  8. 根据权利要求7所述的方法，其中，解析所述连接建立响应时，还得到第六信息；所述第六信息表征连接配置相关信息。
  9. 根据权利要求8所述的方法，其中，当所述UE为具备上下文的UE时，所述第六信息表征激活连接对应的连接配置信息，或者连接激活确认信息；
    当所述UE为不具备上下文的UE时，所述第六信息表征完整连接对应的连接配置信息。
  10. 根据权利要求1所述的方法，其中，所述方法还包括：
    接收所述网络设备发送的冲突解决响应；
    解析所述冲突解决响应，得到第四信息；
    进一步解析所述冲突解决响应，得到第五信息；所述第四信息表征调度所需信息，所述第五信息表征冲突解决结果。
  11. 根据权利要求7至10任一项所述的方法，其中，解析接收的相应响应，得到第四信息后，且在得到第五信息之前，所述方法还包括：
    解析所述相应响应，得到第三信息；
    当第三信息表征具备上下文的UE资源竞争成功时，进一步解析所述相应响应，得到第五信息。
  12. 根据权利要求7至10任一项所述的方法，其中，所述第四信息为临时小区无线网络临时标识TC-RNTI；所述第五信息为竞争到资源的UE标识和/或UE相关参数。
  13. 一种连接建立方法，应用于网络设备，所述方法包括：
    接收UE发送的连接建立请求；
    解析所述连接建立请求，获得第一信息及第二信息；所述第一信息表征所述UE是否具备上下文；所述第二信息表征所述UE具备上下文时的上下文提取信息；
    根据第一信息判断所述UE是否具备上下文；
    当判断结果表征所述UE具备上下文时，利用所述第二信息获取所述UE的上下文；
    基于获取的所述UE的上下文，建立连接。
  14. 根据权利要求13所述的方法，其中，所述第一信息包含在所述第二信息中。
  15. 根据权利要求13所述的方法，其中，所述连接建立请求为RRC连接建立请求。
  16. 根据权利要求15所述的方法，其中，所述解析所述连接建立请求，获得第一信息及第二信息，包括：
    在所述RRC连接建立请求的establishmentcause指示中获得context activation选项；并在所述RRC连接建立请求中获得上下文ID；
    所述context activation选项为第一信息；所述上下文ID为第二信息。
  17. 根据权利要求15所述的方法，其中，所述解析所述连接建立请求，获得第一信息及第二信息，包括：
    在所述RRC连接建立请求中获得增加的IE，所述IE用于指示所述UE具备上下文；并在所述RRC连接建立请求中获得上下文ID；
    所述上下文ID为第二信息。
  18. 根据权利要求16或17所述的方法，其中，所述解析所述连接建立请求，获得第一信息及第二信息，包括：
    在所述RRC连接建立请求的UE ID处获得上下文ID，或者在所述RRC连接建立请求新增的IE处获得上下文ID。
  19. 根据权利要求13所述的方法，其中，所述方法还包括：
    生成连接建立响应；向所述UE发送所述连接建立响应；
    所述连接建立响应携带第四信息及第五信息；所述第四信息表征调度所需信息；所述第五信息表征冲突解决结果。
  20. 根据权利要求19所述的方法，其中，所述连接建立响应还携带第六信息；所述第六信息表征连接配置相关信息。
  21. 根据权利要求20所述的方法，其中，当所述UE为具备上下文的UE时，所述第六信息表征激活连接对应的连接配置信息，或者连接激活确认信息；
    当所述UE为不具备上下文的UE时，所述第六信息表征完整连接对应的连接配置信息。
  22. 根据权利要求13所述的方法，其中，所述方法还包括：
    生成冲突解决响应；所述冲突解决响应携带第四信息及第五信息；所述第四信息表征调度所需信息；所述第五信息表征冲突解决结果；
    向所述UE发送所述冲突解决响应。
  23. 根据权利要求19至22任一项所述的方法，其中，生成的相应响应中还携带第三信息；所述第三信息表征具备上下文的UE或是不具备上下文的UE资源竞争成功。
  24. 根据权利要求19至22任一项所述的方法，其中，所述第四信息为TC-RNTI；所述第五信息为竞争到资源的UE标识和/或UE相关参数。
  25. 根据权利要求13所述的方法，其中，所述方法还包括：
    当判断结果表征所述UE不具备上下文时，建立包括上下文建立的完整连接。
  26. 一种UE，所述UE包括：第一生成单元及第一发送单元；其中，
    所述第一生成单元，配置为生成连接建立请求；连接建立请求中携带 第一信息及第二信息；所述第一信息表征所述UE是否具备上下文；所述第二信息表征所述UE具备上下文时的上下文提取信息；
    所述第一发送单元，配置为向网络设备发送生成的连接建立请求。
  27. 根据权利要求26所述的UE，其中，所述UE还包括：第一接收单元及第一解析单元；其中，
    所述第一接收单元，配置为接收所述网络设备发送的连接建立响应；
    所述第一解析单元，配置为解析所述连接建立响应，得到第四信息；并进一步解析所述连接建立响应，得到第五信息；所述第四信息表征调度所需信息，所述第五信息表征冲突解决结果。
  28. 根据权利要求27所述的UE，其中，所述第一解析单元，还配置为解析所述连接建立响应时，得到第六信息；所述第六信息表征连接配置相关信息。
  29. 根据权利要求26所述的UE，其中，所述UE还包括：第三解析单元；其中，
    所述第一接收单元，还配置为接收所述网络设备发送的冲突解决响应；
    所述第三解析单元，配置为解析所述冲突解决响应，得到第四信息；并进一步解析所述冲突立响应，得到第五信息；所述第四信息表征调度所需信息，所述第五信息表征冲突解决结果。
  30. 根据权利要求27至29任一项所述的UE，其中，所述UE还包括：第二解析单元，配置为解析接收的相应响应，得到第四信息后，且在得到第五信息之前，解析收到的相应响应，得到第三信息；
    相应地，当第三信息表征具备上下文的UE资源竞争成功时，由相应的解析单元解析所述相应响应，得到第五信息。
  31. 一种网络设备，所述设备包括：第二接收单元、第四解析单元、判断单元、获取单元及连接建立单元；其中，
    所述第二接收单元，配置为接收UE发送的连接建立请求；
    所述第四解析单元，配置为解析所述连接建立请求，获得第一信息及第二信息；所述第一信息表征所述UE是否具备上下文；所述第二信息表征所述UE具备上下文时的上下文提取信息；
    所述判断单元，配置为根据第一信息判断所述UE是否具备上下文；
    所述获取单元，配置为当判断结果表征所述UE具备上下文时，利用所述第二信息获取所述UE的上下文；
    所述连接建立单元，配置为基于获取的所述UE的上下文，建立连接。
  32. 根据权利要求31所述的设备，其中，所述设备还包括：第二生成单元及第二发送单元；其中，
    所述第二生成单元，配置为生成连接建立响应；所述二发送单元，配置为向所述UE发送所述连接建立响应；
    所述连接建立响应携带第四信息及第五信息；所述第四信息表征调度所需信息；所述第五信息表征冲突解决结果。
  33. 根据权利要求31所述的设备，其中，所述设备还包括第三生成单元及第三发送单元；其中，
    所述第三生成单元，配置为生成冲突解决响应；所述冲突解决响应携带第四信息及第五信息；所述第四信息表征调度所需信息；所述第五信息表征冲突解决结果；
    所述第三发送单元，配置为向所述UE发送所述冲突解决响应。
  34. 根据权利要求31所述的设备，其中，所述连接建立单元，还用于当判断结果表征所述UE不具备上下文时，建立包括上下文建立的完整连接。
  35. 一种计算机存储介质，所述计算机存储介质包括一组指令，当执行所述指令时，引起至少一个处理器执行如权利要求1至12任一项所述的 连接建立方法，或者执行如权利要求13至25任一项所述的连接建立方法。
PCT/CN2017/073935 2016-02-29 2017-02-17 连接建立方法、用户设备、网络设备及计算机存储介质 WO2017148281A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610113489.2A CN107135549A (zh) 2016-02-29 2016-02-29 连接建立方法、用户设备及网络设备
CN201610113489.2 2016-02-29

Publications (1)

Publication Number Publication Date
WO2017148281A1 true WO2017148281A1 (zh) 2017-09-08

Family

ID=59721676

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/073935 WO2017148281A1 (zh) 2016-02-29 2017-02-17 连接建立方法、用户设备、网络设备及计算机存储介质

Country Status (2)

Country Link
CN (1) CN107135549A (zh)
WO (1) WO2017148281A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019084790A1 (zh) * 2017-10-31 2019-05-09 Oppo广东移动通信有限公司 上下文标识的指示方法、获取方法、用户设备及基站
WO2019095319A1 (en) 2017-11-17 2019-05-23 Zte Corporation Handover-based connection resume technique

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101472306A (zh) * 2007-12-29 2009-07-01 华为技术有限公司 一种ap间切换的方法、装置和系统
WO2010107223A2 (en) * 2009-03-16 2010-09-23 Samsung Electronics Co., Ltd. Method and system for improving call drop caused by radio link failure in mobile communication system
CN104247553A (zh) * 2013-03-22 2014-12-24 华为技术有限公司 建立连接的方法及设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101472306A (zh) * 2007-12-29 2009-07-01 华为技术有限公司 一种ap间切换的方法、装置和系统
WO2010107223A2 (en) * 2009-03-16 2010-09-23 Samsung Electronics Co., Ltd. Method and system for improving call drop caused by radio link failure in mobile communication system
CN104247553A (zh) * 2013-03-22 2014-12-24 华为技术有限公司 建立连接的方法及设备

Also Published As

Publication number Publication date
CN107135549A (zh) 2017-09-05

Similar Documents

Publication Publication Date Title
US20200383135A1 (en) Method for random access in idle state and device
US11140676B2 (en) Data transmission method, terminal device, and access network device
JP7106653B2 (ja) 通信方法、通信デバイス、および通信システム
TWI747078B (zh) 協定資料單元會話建立程序期間資源不足處理方法及其使用者設備
WO2018014741A1 (zh) 一种数据发送、接收和传输方法及装置
US9084263B2 (en) Network connection method and system
EP2515597B1 (en) Method for wireless resource scheduling, network element of access network and terminal thereof
CN107155218B (zh) 一种配置上行半持续调度的方法和设备
JP6844913B2 (ja) 移動性管理の方法、端末および基地局
JP2020505877A (ja) ベアラ変換
JP2018523948A (ja) Ｍｔｃ ｕｅランダムアクセス方法及び装置
JP2020523847A (ja) システム情報取得手順に参加するユーザ機器および基地局
JP2020535695A (ja) 優先順位付けされたランダムアクセスに関与するユーザ機器および基地局
US20200084598A1 (en) Data packet transmission method and device
WO2018024016A1 (zh) 无线网络中的接入方法及设备
WO2016061735A1 (zh) 一种接入网络的方法以及相关装置
WO2012041184A1 (zh) 一种会话管理退避指示方法及网络侧装置、和会话管理退避方法及用户设备
WO2014196908A1 (en) Telecommunications apparatus and method relating to a random access procedure
WO2015196370A1 (zh) 一种接入网设备及通信方法
WO2017148281A1 (zh) 连接建立方法、用户设备、网络设备及计算机存储介质
JP7367186B2 (ja) ページング方法と機器
CN114902630B (zh) 一种应用于接入网的数据传输方法及设备
WO2013029553A1 (zh) 组呼的方法及设备
WO2012062169A1 (zh) 广播和接收系统信息的方法、设备及系统
WO2013113240A1 (zh) 一种传输rn信息、寻呼ue的方法及装置

Legal Events

Date Code Title Description
NENP Non-entry into the national phase

Ref country code: DE

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

Ref document number: 17759132

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 17759132

Country of ref document: EP

Kind code of ref document: A1