WO2015018013A1 - Method and device for connecting initial signaling - Google Patents

Abstract

The present invention relates to the field of communications. Provided in an embodiment of the present invention are a method and device for connecting initial signaling, thus enabling a B-UE to establish single-link MUCC without being connected to an eNB. The method comprises: a benefitting device accesses a support device, and transmits to the support device a radio resource control (RRC) message via an IP address, thus facilitating the support device transmitting an uplink RRC message to a base station, such that a mobility management entity corresponding to the base station and the benefiting device establishes a core network side bearer and context information for the benefiting device, the uplink RRC message comprising the RRC message; and after the base station and the support device configure a protocol stack for a composite bearer, and when the support device receives a downlink RRC message transmitted by the base station, the benefiting device receives an RRC connection reconfiguration message transmitted by the support device, the downlink RRC message comprising the RRC connection reconfiguration message, such that single-link MUCC is conducted between the benefiting device and the support device. The embodiment of the present invention is used to connect initial signaling by a proxy.

Description

 Method and device for connecting initial signaling

The present invention relates to the field of communications, and in particular, to a method and an apparatus for connecting initial signaling. Background technique

 A smartphone can simultaneously support short-range communication technologies (such as WiFi or BlueTooth) and cellular communication technologies (such as LTE, 3G UMTS or CDMA, 2G GSM, WiMAX, etc.), a scenario of cooperative communication between a single network node and multiple users ( In the scenario of multiple UEs cooperative communication (MUCC), when at least two UEs have the characteristics of supporting both WiFi and LTE, in order to increase reliability and throughput, the at least two UEs can be established. A MUCC relationship, that is, one of the at least two UEs needs to send or receive data, and other UEs other than the one UE can support and assist the one UE to communicate; usually, the one UE is named as a benefit UE. (B-UE), the other UEs except the one UE are named as supporting UEs (S-UE). In the initial stage, the single-link MUCC technology requires the B-UE and the S-UE to be connected to the eNB first, and the eNB assists them in completing the single-link MUCC establishment process, and then the connection between the B-UE and the eNB is transferred to the gait state. The B-UE can communicate with the eNB by means of the composite bearer on the S-UE. However, because the channel quality between the B-UE and the eNB is not good, or the eNB does not cover the B-UE, the B-UE cannot connect to the eNB normally, even if the B-UE and the S-UE can communicate with each other with high quality, but the single The link MUCC still cannot be established.

SUMMARY OF THE INVENTION Embodiments of the present invention provide a method and a device for connecting initial signaling, which enable a B-UE to establish a single-link MUCC without being connected to an eNB. To achieve the above objective, the embodiment of the present invention uses the following technical solution: In a first aspect, a method for connecting initial signaling is provided, including: receiving, by a receiving device, a broadcast message sent by a supporting device, according to the broadcast message accessing station Supporting the device, and acquiring an IP address allocated by the supporting device; the benefit device sending a radio resource control RRC message to the supporting device by using the IP address, so that the supporting device sends an uplink RRC message to the base station, so that The base station and the mobility management entity corresponding to the benefit device establish a core network for the benefit device And the RRC message is sent by the supporting device, where the RRC connection reconfiguration message is that the supporting device is the After the beneficial device configuration is configured to be sent after the protocol stack on the supporting device side, and after receiving the downlink RR C message sent by the base station, the downlink RRC message includes the RRC connection reconfiguration message, so that the benefit device Single-link multi-user device synthesis communication is performed with the supporting device. With reference to the first aspect, in a first possible implementation manner of the first aspect, the benefit device receives a broadcast message sent by the support device, accesses the support device according to the broadcast, and acquires the support The IP address assigned by the device includes: the benefit device accessing the mobility management entity corresponding to the support device by using the support device; the benefit device receiving the broadcast message sent by the support device, the broadcast cancellation packet The short message communication identifier of the supporting device is sent; the broadcast message is sent after the mobility management entity corresponding to the supporting device establishes the core network side bearer and context information for the supporting device; Accessing the supporting device according to the short-distance communication identifier; the receiving device receives an allocation message sent by the supporting device, where the allocation message includes an IP address allocated by the supporting device to the benefit device. With reference to the first aspect or the first possible implementation manner of the first aspect, in a second possible implementation manner of the first aspect, the benefit device sends the RRC to the supporting device by using the IP address Before the message, the method further includes: the benefit device knowing that the supporting device is in a connected state; or knowing that the supporting device is not connected to the base station and is in an idle state. With reference to the first aspect or the second possible implementation manner of the first aspect, in a third possible implementation manner of the first aspect, the benefit device, that the supporting device is in a connected state, includes: the benefit device The supporting device sends a request message; when the supporting device is connected to the base station and is in a connected state, the benefit device receives a response message returned by the supporting device; or Receiving, by the benefit device, a response message returned by the supporting device, where the supporting device sends an RRC connection request to the base station, when the supporting device is not connected to the base station and is in an idle state. Transmitting, by the base station, the initial message to the mobility management entity corresponding to the supporting device, so that the mobility management entity corresponding to the supporting device sends the bearer and the context information after the supporting device is sent; or the benefit Receiving, by the device, a response message returned by the supporting device, where the RRC connection request message includes the request message, where the response message is included in the RRC connection response message; The base station sends an RRC connection request message, and the base station sends an initial message to the mobility management entity corresponding to the supporting device, where the mobility management entity corresponding to the supporting device sends the bearer and the context information after the supporting device sends the . With reference to the first aspect or the third possible implementation manner of the first aspect, in a fourth possible implementation manner of the first aspect, the RR C message includes a globally unique temporary user equipment identifier GUTI of the benefit device; The RRC connection request message includes a temporary mobile subscriber identity code S-TMSI of the supporting device; the initial message includes a temporary mobile subscriber identity code S-TMSI of the supporting device.

In a second aspect, a method for connecting initial signaling is provided, where: the supporting device sends a broadcast message to the benefit device, so that the benefit device accesses the supporting device according to the broadcast message, and acquires the allocated device Receiving, by the supporting device, the first RRC message that the benefit device sends the radio resource by using the IP address; the supporting device sends a second RRC message to the base station, where the second RRC message includes the first The RR C message is configured to enable the mobility management entity corresponding to the base station and the benefit device to establish core network side bearer and context information for the benefit device; and the supporting device receives the first RRC connection reconfiguration message sent by the base station And configuring, by the first RRC connection reconfiguration message, a protocol stack that is configured to be carried on the supporting device side, where the supporting device receives the third RRC message sent by the base station; The supporting device parses the third RRC message, acquires a second RRC connection reconfiguration message sent by the base station to the beneficiary device, and sends the second RRC connection reconfiguration message to the benefit device. And causing the benefit device to establish a synthetic communication with the single-link multi-user device between the supporting devices.

 With reference to the second aspect, in a first possible implementation manner of the second aspect, the sending, by the supporting device, the sending of the broadcast message to the receiving device includes: the supporting device accessing the mobility management entity corresponding to the supporting device, so that The mobility management entity corresponding to the supporting device establishes bearer and context information of the core network side for the supporting device; the supporting device sends the broadcast message to the benefit device, where the broadcast message includes the short of the supporting device a communication identifier, so that the benefit device accesses the support device according to the short-range communication identifier; the support device sends an assignment message to the benefit device, where the assignment message includes the support device as the benefit The IP address assigned by the device.

 With reference to the second aspect or the first possible implementation manner of the second aspect, in a second possible implementation manner of the second aspect, the receiving device receives, by the supporting device, the first sending by the benefit device by using the IP address After the RRC message, the method further includes: establishing, by the supporting device, a connection with the base station.

 With the second aspect or the second possible implementation manner of the second aspect, in a third possible implementation manner of the second aspect, the establishing, by the supporting device, the connection with the base station includes: When the base station is connected and in the connected state, the supporting device sends the second RRC message to the base station; or when the supporting device is not connected to the base station and is in an idle state, the supporting device goes to the The base station sends an RRC connection request message, and triggers the base station to send an initial message to the mobility management entity corresponding to the supporting device, so that the mobility management entity corresponding to the supporting device establishes bearer and context information for the supporting device.

With reference to the second aspect or the first possible implementation manner of the second aspect, in a fourth possible implementation manner of the second aspect, the receiving device receives, by the supporting device, the first sending by the benefit device by using the IP address Before the RRC message, the method further includes: The supporting device notifies the benefit device that the supporting device is in a connected state. With reference to the second aspect or the fourth possible implementation manner of the second aspect, in a fifth possible implementation manner of the second aspect, the supporting device notifying the benefit device that the supporting device is in a connected state includes: Receiving, by the supporting device, a request message sent by the benefiting device; when the supporting device is connected to the base station and in a connected state, the supporting device sends a response message to the benefiting device; or in the supporting device When the base station is disconnected and is in an idle state, the supporting device returns a response message to the benefit device, where the response message is that the supporting device sends an RRC connection request message to the base station, triggering the base station to The mobility management entity corresponding to the supporting device sends an initial message, so that the mobility management entity corresponding to the supporting device sends the bearer and context information for the supporting device, or the supporting device returns to the beneficial device. In response to the message, the RRC connection request message includes the request message, and the response message is a packet In the RRC connection response message, the response message is that the supporting device sends an RRC connection request message to the base station, and the base station sends an initial message to the mobility management entity of the supporting device, where the support The mobility management entity corresponding to the device is sent after the bearer and context information is established by the supporting device. With reference to the second aspect or the third possible implementation manner of the second aspect or the fifth possible implementation manner, in a sixth possible implementation manner of the second aspect, the RRC message includes the global a unique temporary user equipment identifier GUTI; the RRC connection request message includes a temporary mobile subscriber identity code S-TMSI of the supporting device; the initial message includes a temporary mobile subscriber identity code S-TMSI of the supporting device. In a third aspect, a method for connecting initial signaling is provided, the method includes: after a benefiting device sends a first RRC message to a supporting device, the base station receives a second RRC message sent by the supporting device, where the second RRC The message includes the first RRC message, and the base station establishes core network side bearer and context information for the benefit device by using the mobility management entity corresponding to the benefit device according to the second RRC message; The base station configures a protocol stack on the base station side for the supporting device and the benefit device respectively;

 Sending, by the base station, a first RRC connection reconfiguration message to the supporting device, so that the supporting device configures, for the benefit device, a protocol stack that is carried on the supporting device side; and the base station sends a third RRC to the supporting device. a message, so that the supporting device parses the third RRC message, acquires a second RRC connection reconfiguration message sent by the base station to the beneficiary device, and sends the second RRC connection reconfiguration message to The benefiting device; the base station establishes a single-link multi-user device synthesis communication between the benefit device and the supporting device. With reference to the third aspect, in a first possible implementation manner of the third aspect, the base station, according to the second RRC message, establishes a core network for the benefit device by using a mobility management entity corresponding to the benefit device The side bearer and the context information includes: the base station acquires a non-access stratum message of the beneficiary device from the first RRC message carried by the second RRC message; the base station sends the non-access stratum message To the mobility management entity corresponding to the benefit device, so that the mobility management entity corresponding to the benefit device establishes core network sideloading and context information for the benefit device. With the third aspect or the first possible implementation manner of the third aspect, in a second possible implementation manner of the third aspect, after the benefit device sends the RRC message to the supporting device, The method also includes: the base station establishing a connection with the supporting device.

With the third aspect or the second possible implementation manner of the third aspect, in a third possible implementation manner of the third aspect, the establishing, by the base station, the connection for the supporting device includes: When the base station is connected and in the connected state, the base station receives the second RRC message sent by the supporting device; or when the supporting device is not connected to the base station and is in an idle state, the base station receives the supporting device Sending an RRC connection request message, sending an initial message to the mobility management entity corresponding to the supporting device, so that the mobility management entity corresponding to the supporting device is the Support the device to establish bearer and context information.

 In conjunction with the third aspect or the first possible implementation manner of the third aspect, in a fourth possible implementation manner of the third aspect, the benefit device sends the

Before the RRC message, the method further includes: establishing, by the base station, a connection with the supporting device.

 With the third aspect or the fourth possible implementation manner of the third aspect, in a fifth possible implementation manner of the third aspect, the establishing, by the base station, the connection with the supporting device includes: The supporting device sends a request message, when the supporting device is not connected to the base station and is in an idle state, the base station receives an RRC connection request message sent by the supporting device; and the mobility of the base station to the supporting device The management entity sends an initial message, so that after the mobility management entity corresponding to the supporting device establishes bearer and context information for the supporting device, the supporting device returns a response message to the benefit device; or The supporting device sends a request message, and when the supporting device is not connected to the base station and is in an idle state, the base station receives an RRC connection request message sent by the supporting device, where the RRC connection request message includes the request Message: the base station sends an initial message to the mobility management entity of the supporting device, so that Supporting device corresponding to said mobility management entity to establish a bearer context information and said supporting device;

 And the base station returns an RRC connection response message to the supporting device, so that the supporting device returns a response message to the benefit device, where the response message is included in the RR C connection response message.

With reference to the third aspect or the third possible implementation manner of the third aspect or the fifth possible implementation manner, in a sixth possible implementation manner of the third aspect, the RRC message includes the global a unique temporary user equipment identifier GUTI; the RRC connection request message includes a temporary mobile subscriber identity code S-TMSI of the supporting device; the initial message includes a temporary mobile subscriber identity code S-TMSI of the supporting device. In a fourth aspect, a benefit device is provided, including: a receiving unit, configured to receive a broadcast message sent by the supporting device, where the access unit is configured to access the supporting device according to the broadcast message received by the receiving unit;

 An obtaining unit, configured to acquire, after the access unit is accessed, the allocated device

IP address;

Sending a radio resource control RRC message, so that the supporting device sends an uplink RRC message to the base station, so that the base station and the mobility management entity corresponding to the beneficiary device establish a core network side bearer and context information for the beneficiary device, where The uplink RRC message includes the RRC message;

 The receiving unit is configured to receive an RRC connection reconfiguration message sent by the supporting device, where the RRC connection reconfiguration message is configured after the supporting device configures, for the benefit device, a protocol stack that is carried on the supporting device side, After receiving the downlink RRC message sent by the base station, the downlink RRC message includes the RRC connection reconfiguration message, and the communication unit is configured to perform single-link multi-user device synthesis communication with the supporting device.

 With reference to the fourth aspect, in a first possible implementation manner of the fourth aspect, the access unit is further configured to access, by using the supporting device, a mobility management entity corresponding to the supporting device;

 The receiving unit is specifically configured to: receive a broadcast message of the supporting device, where the broadcast message includes a short-distance communication identifier of the supporting device, a broadcast cancellation of the supporting device, and a packet, and the mobility management entity is The supporting device sends the core network side bearer and the context information, and then sends the information;

 The access unit is specifically configured to: access the supporting device according to the short-distance communication identifier, so that the supporting device sends an allocation message to the beneficiary device, where the allocation message includes that the supporting device is the benefit IP address assigned by the device;

The receiving unit is specifically configured to: receive an allocation message sent by the supporting device, where the allocation message includes an IP address allocated by the supporting device to the benefit device. In combination with the fourth aspect or the first possible implementation of the fourth aspect, in the fourth aspect In a second possible implementation manner, the benefit device further includes:

Before sending the RRC message, it is known that the supporting device is connected to the base station and is in a connected state; or it is known that the supporting device is not connected to the base station and is in an idle state. With reference to the fourth aspect or the second possible implementation manner of the fourth aspect, in a third possible implementation manner of the fourth aspect, the obtaining unit includes: a sending subunit, configured to send a request to the supporting device a receiving subunit, configured to receive a response message returned by the supporting device when the learning unit learns that the supporting device is connected to the base station and is in a connected state, or is configured to learn at the learning unit Receiving a response message returned by the supporting device when the supporting device is not connected to the base station and is in an idle state, the response message is that the supporting device triggers the base station by sending an RRC connection request message to the base station. Sending an initial message to the mobility management entity corresponding to the supporting device, so that the mobility management entity corresponding to the supporting device sends the bearer and the context information after the supporting device is sent; or receiving the response message returned by the supporting device The RRC connection request message includes the request message, and the response message is included in the R In the RC connection response message, the response message is that the supporting device sends an RRC connection request message to the base station, and the base station sends an initial message to the mobility management entity corresponding to the supporting device, where the supporting device corresponds to The mobility management entity sends the bearer and context information for the supporting device. With reference to the third possible implementation manner of the fourth aspect, in a fourth possible implementation manner of the fourth aspect, the RRC message sent by the sending unit includes a global unique temporary user equipment identifier GUTI of the benefit device The RR C connection request message received by the receiving subunit includes a temporary mobile subscriber identity code S-TMSI of the supporting device, and the initial message includes a temporary mobile subscriber identity code S-TMSI of the supporting device. The fifth aspect provides a supporting device, including: a sending unit, configured to send a broadcast message to the benefit device, so that the benefit device accesses the supporting device according to the broadcast message, and acquires an IP allocated by the supporting device. An receiving unit, configured to receive the first wireless that is sent by the benefit device by using the IP address a resource control RRC message, the sending unit, configured to send a second RRC message to the base station, where the second RRC message includes a first RRC message received by the receiving unit, and the mobile station corresponds to the mobile device And the receiving unit is configured to receive a first RRC connection reconfiguration message sent by the base station, and a configuration unit, configured to receive, according to the receiving unit, a core network side bearer and context information. The RRC connection reconfiguration message is configured to configure, by the benefit device, a protocol stack that is carried on the supporting device side; the receiving unit is configured to receive a third RRC message sent by the base station, and a processing unit, configured to receive the The third RRC message received by the unit is parsed, and the second RRC connection reconfiguration message sent by the base station to the beneficiary device is obtained, where the sending unit is configured to The distribution message is sent to the benefit device, so that the benefit device establishes a synthetic communication with the single-link multi-user device between the support devices. With reference to the fifth aspect, in a first possible implementation manner of the fifth aspect, the access unit is configured to access the mobility management entity corresponding to the supporting device, so that the mobility management entity corresponding to the supporting device is The supporting device establishes bearer and context information of the core network side; the sending unit is specifically configured to: send the broadcast message to the benefit device, where the broadcast message includes a short-distance communication identifier of the supporting device, so as to facilitate The receiving device is configured to access the supporting device according to the short-distance communication identifier; the sending unit is further configured to: send an allocation message to the benefit device, where the allocation message includes the supporting device as the benefit device The assigned IP address. With the fifth aspect or the first possible implementation manner of the fifth aspect, in a second possible implementation manner of the fifth aspect, the supporting device further includes: an establishing unit, configured to receive, at the receiving unit, After the benefit device sends the RRC message by using the IP address, establish a connection with the base station. With reference to the fifth aspect or the second possible implementation manner of the fifth aspect, in a third possible implementation manner of the fifth aspect, the establishing unit includes: a first sending subunit, configured to be used in the supporting device Connected to and connected to the base station Transmitting the second RRC message to the base station, or the first sending unit, configured to send an RRC connection request to the base station when the supporting device is not connected to the base station and is in an idle state. The message is sent to the base station to send an initial message to the mobility management entity corresponding to the supporting device, so that the mobility management entity corresponding to the supporting device establishes bearer and context information for the supporting device. With the fifth aspect or the first possible implementation manner of the fifth aspect, in a fourth possible implementation manner of the fifth aspect, the supporting device further includes: a notification unit, configured to receive at the receiving subunit Before the benefiting device sends the first RRC message by using the IP address, the beneficiary device is notified that the supporting device is in a connected state. With the fifth aspect or the first possible implementation manner of the fifth aspect, in a fifth possible implementation manner of the fifth aspect, the notification unit includes:

a second receiving subunit, configured to receive a request message sent by the beneficiary device, where the second sending subunit is configured to send a response message to the beneficiary device when the supporting device is connected to the base station and is in a connected state Or the second sending subunit, configured to: when the supporting device is not connected to the base station and in an idle state, return a response message to the benefit device, where the response message is in the sending subunit The base station sends an RRC connection request message, and the base station is triggered to send an initial message to the mobility management entity corresponding to the supporting device, so that the mobility management entity corresponding to the supporting device establishes bearer and context information for the supporting device. Or sending a response message to the benefit device when the supporting device is not connected to the base station and is in an idle state, the RRC connection request message includes the request message, and the response message is included in In the RRC connection response message, the response message is that the supporting device sends an RRC connection to the base station The request message, the base station sends an initial message to the mobility management entity of the supporting device, and the mobility management entity corresponding to the supporting device sends the bearer and context information after the supporting device establishes the bearer. With reference to the fifth aspect or the third possible implementation manner of the fifth aspect or the fifth possible implementation manner, in a sixth possible implementation manner of the fifth aspect, the RRC message includes the global Unique temporary user equipment identification GUTI; The RRC connection request message includes a temporary mobile subscriber identity code S-TMSI of the supporting device; the initial message includes a temporary mobile subscriber identity code S-TMSI of the supporting device. According to a sixth aspect, a base station is provided, including: a receiving unit, configured to receive a second RRC message sent by the supporting device after the benefiting device sends a first RRC message to the supporting device, where the second RRC message is sent And the establishing unit is configured to establish, according to the second RRC message that is received by the receiving unit, a core network side bearer and the bearer device by using a mobility management entity corresponding to the benefit device a configuration unit, configured to separately configure a protocol stack of the base station side for the supporting device and the benefit device, and a sending unit, configured to send a first RRC connection reconfiguration message to the supporting device, so that the supporting device Configuring, by the benefit device, a protocol stack that is carried on the supporting device side; the sending unit is further configured to send a third RRC message to the supporting device, so that the supporting device parses the third RRC message Obtaining, by the base station, a second RRC connection reconfiguration message sent by the base station, and sending the second RRC connection reconfiguration message To benefit from the device; the establishing means, for the benefit of multi-user equipment establishes communication synthetic single link between the device and the supporting device. With reference to the sixth aspect, in a first possible implementation manner of the sixth aspect, the establishing unit is specifically configured to: obtain, by using the first RRC message that is carried by the second RRC message, the non-benefit device The access layer message is sent to the mobility management entity corresponding to the benefit device, so that the mobility management entity corresponding to the benefit device establishes a core network side bearer and context for the benefit device. information. With reference to the sixth aspect or the first possible implementation manner of the sixth aspect, in a second possible implementation manner of the sixth aspect, the establishing unit is further configured to: After the supporting device sends the first RRC message, establish a connection with the supporting device. With reference to the sixth aspect or the second possible implementation manner of the sixth aspect, in a third possible implementation manner of the sixth aspect, the establishing unit includes: a receiving subunit, configured to be in the supporting device and the Receiving the second RRC message sent by the supporting device when the base station is connected and in the connected state; or receiving the subunit, when the supporting device is not connected to the base station and is in an idle state, receiving the Supporting an RRC connection request message sent by the device; a sending subunit, configured to send an initial message to the mobility management entity corresponding to the supporting device, so that the mobility management entity corresponding to the supporting device establishes a bearer and a context for the supporting device information. With the sixth aspect or the first possible implementation manner of the sixth aspect, in a third possible implementation manner of the sixth aspect, the establishing unit is further configured to send, at the benefit device, the supporting device Before the RRC message, a connection is established with the supporting device. With reference to the sixth aspect or the third possible implementation manner of the sixth aspect, in a fourth possible implementation manner of the sixth aspect, the establishing unit specifically includes: a receiving subunit 1, configured to be in the benefit device Sending a request message to the supporting device, when the supporting device is not connected to the base station and is in an idle state, receiving an RRC connection request message sent by the supporting device, and sending a subunit 1 for corresponding to the supporting device The mobility management entity sends an initial message, so that the mobility management entity corresponding to the supporting device returns a response message to the benefit device after establishing the bearer and context information for the supporting device; or

 The receiving sub-unit 1 is configured to send, by the benefiting device, a request message to the supporting device, where the supporting device is not connected to the base station and is in an idle state, receiving an RRC connection request message sent by the supporting device The RRC connection request message includes the request message;

The sending subunit 1 is configured to send an initial message to the mobility management entity of the supporting device, so that the mobility management entity corresponding to the supporting device establishes bearer and context information for the supporting device; The supporting device returns an RRC connection response message, so that And the supporting device returns a response message to the benefit device, where the response message is included in the RRC connection response message. With reference to the sixth aspect, or the second possible implementation manner of the sixth aspect, or the fourth possible implementation manner, in the fifth possible implementation manner of the sixth aspect, the first RRC message received by the receiving unit includes The global unique temporary user equipment identifier GUTI of the benefit device; the RRC connection request message includes a temporary mobile subscriber identity code S-TMSI of the supporting device; the initial message includes a temporary mobile subscriber identity code S of the supporting device -TMSI. The seventh aspect provides a benefit device, including: a receiver, configured to receive a broadcast message sent by the support device, and a processor, configured to access the support device according to the broadcast message received by the receiver, and obtain the Support the IP address assigned by the device;

a transmitter, configured to send, by using the IP address obtained by the processor, a radio resource control RRC message to the supporting device, so that the supporting device sends an uplink RRC message to the base station, so that the base station and the benefit device correspond to The mobility management entity establishes a core network side bearer and context information for the benefit device, the uplink RRC message includes the RRC message, and the receiver receives an RRC connection reconfiguration message sent by the supporting device, where the RRC connection The re-allocation message is sent after the supporting device configures the protocol stack that is carried on the supporting device side, and receives the downlink RRC message sent by the base station, where the downlink RRC message includes the RRC. And the processor is configured to perform single-link multi-user device synthesis communication with the supporting device after the receiver receives the RRC connection reconfiguration message. With reference to the seventh aspect, in a first possible implementation manner of the seventh aspect, the processor is further configured to access, by using the supporting device, a mobility management entity corresponding to the supporting device; Receiving a broadcast message sent by the supporting device, where the broadcast message includes a short-distance communication identifier of the supporting device, a broadcast cancellation of the supporting device, and a packet for the mobility management entity to establish for the supporting device After the core network side bearers and context information is sent; The processor is specifically configured to: access the supporting device according to the short-distance communication identifier, so that the supporting device sends an allocation message to the benefit device, where the allocation message includes that the supporting device is the beneficial device And the receiver is configured to: receive an allocation message sent by the supporting device, where the allocation message includes an IP address allocated by the supporting device to the benefit device. With reference to the seventh aspect, or the first possible implementation manner of the seventh aspect, in a second possible implementation manner of the seventh aspect, the processor is further configured to: pass the IP address to the transmitter Before the RRC message is sent by the supporting device, it is learned that the supporting device is in a connected state; or that the supporting device is not connected to the base station and is in an idle state. With reference to the seventh aspect, or the second possible implementation manner of the seventh aspect, in a third possible implementation manner of the seventh aspect, the transmitter is specifically configured to: send a request message to the supporting device; The receiver is specifically configured to: when the processor learns that the supporting device is connected to the base station and is in a connected state, receive a response message returned by the supporting device; or the receiver is specifically configured to: The receiver receives the response message returned by the supporting device when the supporting device is not connected to the base station and is in an idle state, and the response message is that the supporting device sends an RRC connection to the base station. a request message, the base station is triggered to send an initial message to the mobility management entity corresponding to the supporting device, so that the mobility management entity corresponding to the supporting device sends the bearer and context information after the supporting device is sent; or the receiving station a response message returned by the supporting device, where the RRC connection request message includes the request message, and the response message is Enclosed in the RRC connection response message, the response message is that the supporting device sends an RRC connection request message to the base station, and the base station sends an initial message to the mobility management entity corresponding to the supporting device, where The mobility management entity corresponding to the supporting device is sent after the bearer and context information is established by the supporting device. With reference to the seventh aspect, or the third possible implementation manner of the seventh aspect, in a fourth possible implementation manner of the seventh aspect, the RRC message sent by the transmitter includes a global unique temporary user equipment of the benefit device Identifying a GUTI; the RRC Connection Request message includes a temporary mobile subscriber identity of the supporting device S-TMSI; the initial message includes a temporary mobile subscriber identity code S-TMSI of the supporting device. According to an eighth aspect, a support device is provided, including: a transmitter, configured to send a broadcast message to a benefit device, so that the benefit device accesses the support device according to the broadcast message, and acquires an IP allocated by the support device And a receiver, configured to receive a first RRC message that is sent by the benefit device by using the IP address, where the transmitter is configured to send a second RRC message to the base station, where the second RRC message includes Determining, by the receiver, the first RRC message, that the base station and the mobility management entity corresponding to the benefit device establish core network side bearer and context information for the benefit device; and the receiver is configured to receive the base station a first RRC connection reconfiguration message sent by the processor, configured to configure, according to the RRC connection reconfiguration message received by the receiving unit, a protocol stack that is configured to be carried on the supporting device side, where the receiving device is configured; And a third RRC message sent by the base station, where the processor is configured to parse the third RRC message received by the receiver, and obtain And the second RRC connection reconfiguration message sent by the base station to the benefit device, where the transmitter is configured to send the second RRC connection reconfiguration message acquired by the processor to the benefit device, so that The benefit device establishes a synthetic communication with the single-link multi-user device between the supporting devices. With reference to the eighth aspect, in a first possible implementation manner of the eighth aspect, the processor is configured to access a mobility management entity corresponding to the supporting device, so that the mobility management entity corresponding to the supporting device is The supporting device establishes bearer and context information on the core network side;

The transmitter is specifically configured to send the broadcast message to the benefit device, where the broadcast message includes a short-range communication identifier of the supporting device, so that the benefit device accesses the short-distance communication identifier according to the The supporting device is configured to send an allocation message to the beneficiary device, where the allocation message includes an IP address allocated by the supporting device to the beneficiary device. With reference to the eighth aspect, or the first possible implementation manner of the eighth aspect, in a second possible implementation manner of the eighth aspect, the method further includes: the transmitter, configured to receive the benefit at the receiver After the device sends an RRC message through the IP address, establish a connection with the base station. With reference to the eighth aspect, or the second possible implementation manner of the eighth aspect, in a third possible implementation manner of the eighth aspect, the transmitter is configured to connect to the base station and And transmitting, by the base station, the uplink RRC message to the base station; or the transmitter, configured to send an RRC connection request message to the base station when the supporting device is not connected to the base station and is in an idle state, The base station is triggered to send an initial message to the mobility management entity corresponding to the supporting device, so that the mobile device corresponding to the supporting device establishes bearer and context information for the supporting device. With reference to the eighth aspect, or the first possible implementation manner of the eighth aspect, in a fourth possible implementation manner of the eighth aspect, the method further includes: the transmitter, configured to receive the benefit at the receiver Before the device sends the RRC message by using the IP address, the device is notified that the supporting device is in the connected state. With reference to the eighth aspect, or the fourth possible implementation manner of the eighth aspect, in a fifth possible implementation manner of the eighth aspect, the transmitter is configured to connect to the base station and In the connected state, the transmitter sends a response message to the benefit device; or

And returning, to the benefit device, a response message when the supporting device is not connected to the base station and is in an idle state, where the response message is that the transmitter sends an RRC connection request message to the base station, and triggers The base station sends an initial message to the mobility management entity corresponding to the supporting device, so that the mobility management entity corresponding to the supporting device sends the bearer and context information after the supporting device is sent; or is used in the processor When the base station is not connected and is in an idle state, the transmitter returns a response message to the benefit device, the RRC connection request message includes the request message, and the response message is included in the RRC connection response message. The response message is that the transmitter sends an RRC connection request message to the base station, and the base station sends an initial message to the mobility management entity of the supporting device, so as to facilitate the mobility of the supporting device. The management entity sends the bearer and context information for the supporting device. With reference to the eighth aspect, or the third possible implementation manner of the eighth aspect, or the fifth possible implementation manner, in a sixth possible implementation manner of the eighth aspect, the first RRC message sent by the transmitter includes The global unique temporary user equipment identifier GUTI of the benefit device; the RRC connection request message includes a temporary mobile subscriber identity code S-TMSI of the supporting device; the initial message includes a temporary mobile subscriber identity code S of the supporting device -TMSI. According to a ninth aspect, a base station is provided, including: a receiver, configured to receive a second RRC message sent by the supporting device after the benefit device sends a first radio resource control RR C message to the supporting device, where the second RRC The message includes the first RRC message, a processor, configured to establish, according to the second RRC message received by the receiver, a core network side bearer and a context for the beneficiary device by using a mobility management entity corresponding to the benefit device information;

 The processor is configured to configure a protocol stack of the base station side for the supporting device and the benefit device, and a transmitter, configured to send a first RRC connection reconfiguration message to the supporting device, so that the supporting device is The benefit device is configured to synthesize a protocol stack that is carried on the supporting device side; the transmitter is configured to send a third RRC message to the supporting device, so that the supporting device parses the third RRC message, and obtains Sending, by the base station, a second RRC connection reconfiguration message to the benefit device, and sending the second RRC connection reconfiguration message to the benefit device;

The processor is configured to establish a single-link multi-user device synthesis communication between the benefit device and the support device. With reference to the ninth aspect, in a first possible implementation manner of the ninth aspect, the processor is configured to obtain, by using the first RRC message that is carried by the second RRC message, the non-benefit device The access layer message is specifically configured to send the non-access stratum message to a mobility management entity corresponding to the beneficiary device, so that the mobility management entity corresponding to the beneficiary device is the benefit The device establishes core network side bearer and context information. With the ninth aspect or the first possible implementation manner of the ninth aspect, in a second possible implementation manner of the ninth aspect, the processor is further configured to: send, by the benefit device, the supporting device After the first RRC message, a connection is established with the supporting device. With the second possible implementation manner of the ninth aspect, in a third possible implementation manner of the ninth aspect, the receiver is further configured to: when the supporting device is connected to the base station and in a connected state Receiving a second RRC message sent by the supporting device, or for receiving an RRC connection request message sent by the supporting device when the supporting device is not connected to the base station and in an idle state, the transmitter Sending an initial message to the mobility management entity corresponding to the supporting device, so that the mobility management entity corresponding to the supporting device establishes bearer and context information for the supporting device.

 With the ninth aspect or the first possible implementation manner of the ninth aspect, in a fourth possible implementation manner of the ninth aspect, the processor is further configured to: send, by the benefit device, the supporting device Before the RRC message, a connection is established with the supporting device.

With reference to the ninth aspect or the fourth possible implementation manner of the ninth aspect, in a fifth possible implementation manner of the ninth aspect, the receiver is further configured to: Sending a request message, when the supporting device is not connected to the base station and is in an idle state, receiving an RRC connection request message sent by the supporting device; the transmitter is further configured to perform mobility management corresponding to the supporting device The entity sends an initial message, so that after the mobility management entity corresponding to the supporting device establishes bearer and context information for the supporting device, the supporting device returns a response message to the benefit device; or is used for the benefit The device sends a request message to the supporting device, and when the supporting device is not connected to the base station and is in an idle state, the receiver receives an RRC connection request message sent by the supporting device, where the RRC connection request message includes The request message is further configured to send an initial message to the mobility management entity of the supporting device, so that The mobility management entity corresponding to the supporting device establishes bearer and context information for the supporting device; and is further configured to return an RRC connection response message to the supporting device, so that the supporting device returns a response message to the benefit device, where The response message is included in the RRC Connection Response message. With reference to the third possible implementation manner of the ninth aspect to the fifth possible implementation manner, in a sixth possible implementation manner of the ninth aspect, the first RRC message received by the receiver includes the benefit device The global unique temporary user equipment identity GUTI; the RRC connection request message includes a temporary mobile subscriber identity code S-TMSI of the supporting device; the initial message includes a temporary mobile subscriber identity code S-TMSI of the supporting device. The embodiment of the present invention provides a method and a device for connecting initial signaling, where the receiving device receives a broadcast message sent by the supporting device, accesses the supporting device according to the broadcast message, and obtains an IP address allocated by the supporting device, and the benefit device supports the IP address through the IP address. The device sends a radio resource control RRC message, so that the supporting device sends an uplink RRC message to the base station, so that the base station and the mobility management entity corresponding to the beneficiary device establish the core network side bearer and context information for the benefit device, and the uplink RRC message includes the RRC message, the base station. The protocol stack of the base station is configured for the benefit device and the supporting device, and the benefit device receives the RRC connection reconfiguration message sent by the supporting device. The RRC connection reconfiguration message is configured after the supporting device configures the protocol stack of the supporting device for the beneficial device. After receiving the downlink RRC message sent by the base station, the downlink RRC message includes an RRC connection reconfiguration message, so that the beneficiary device establishes a single-link multi-user device synthesis communication with the supporting device, and can enable B- The UE can be established without being connected to the eNB. Link MUCC.

 BRIEF DESCRIPTION OF THE DRAWINGS In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings to be used in the embodiments or the description of the prior art will be briefly described below, and obviously, in the following description The drawings are only some of the embodiments of the present invention, and those skilled in the art can obtain other drawings based on these drawings without any creative work. FIG. 1 is a schematic flowchart of a method for connecting initial signaling according to an embodiment of the present invention; FIG. 2 is a schematic flowchart of a method for connecting initial signaling according to another embodiment of the present invention;

 3 is a schematic flow chart of a method for connecting initial signaling according to another embodiment of the present invention;

FIG. 4 is a schematic flowchart of a method for connecting initial signaling according to another embodiment of the present invention; Figure

 FIG. 5 is a schematic diagram of interaction between devices according to an embodiment of the present invention;

 FIG. 6 is a schematic diagram of interaction between another device according to an embodiment of the present invention; FIG. 7 is a schematic diagram of another interaction between devices according to an embodiment of the present invention; FIG. 8 is still another embodiment of the present invention. FIG. 9 is a schematic diagram of a control plane protocol stack before a single-link MU CC is established according to an embodiment of the present invention;

 FIG. 10 is a schematic diagram of a control plane protocol stack after a single-link MUCC is established according to an embodiment of the present disclosure;

 FIG. 11 is a schematic diagram of a user plane protocol stack after a single-link MUCC is established according to an embodiment of the present invention;

 FIG. 12 is a schematic structural diagram of a benefit device according to an embodiment of the present invention;

 FIG. 13 is a schematic structural diagram of a benefit device according to an embodiment of the present invention;

 FIG. 14 is a schematic structural diagram of a benefit device according to an embodiment of the present invention;

 FIG. 15 is a schematic structural diagram of a supporting device according to an embodiment of the present invention; FIG. 16 is a schematic structural diagram of a supporting device according to an embodiment of the present invention; FIG. 17 is a schematic structural diagram of a supporting device according to an embodiment of the present invention; FIG. 18 is a schematic structural diagram of a supporting device according to an embodiment of the present invention; FIG. 19 is a schematic structural diagram of a base station according to an embodiment of the present invention;

 FIG. 20 is a schematic structural diagram of a base station according to an embodiment of the present disclosure;

 FIG. 21 is a schematic structural diagram of a base station according to an embodiment of the present disclosure;

 FIG. 22 is a schematic structural diagram of a benefit device according to an embodiment of the present disclosure;

 FIG. 23 is a schematic structural diagram of a supporting device according to an embodiment of the present invention; FIG. 24 is a schematic structural diagram of a base station according to an embodiment of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS The technical solutions in the embodiments of the present invention will be described below with reference to the accompanying drawings in the embodiments of the present invention. The invention is described in a clear and complete manner, and it is obvious that the described embodiments are only a part of the embodiments of the invention, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention. In the MUCC (Multiple UEs Cooperative Communication) technology, an eNB (evolved NodeB, base station) can directly communicate with the UE in a conventional manner when communicating with a certain UE (User Equipment). It is possible to communicate with another UE in the vicinity of the UE, and let another UE forward the data of the UE. The two UEs can communicate through SRC (Short Range Communication) mode, Bluetooth, WiFi (Wireless Fidelity). In this way, the UE with the best channel condition can be selected among certain UEs to transmit uplink and downlink data, and the effect of multi-user diversity is achieved. The UE that serves as the forwarding function is the S-UE (Supporting UE), and the destination UE is called the B-UE (Beneficial User Equipment). An S-UE may have multiple B-UEs. Conversely, one B-UE may have multiple S-UEs. A UE can act as both a B-UE and an S-UE. An embodiment of the present invention provides a method for connecting initial signaling, as shown in FIG. 1 , including:

101. The receiving device receives the broadcast message sent by the supporting device, and accesses the supporting device according to the broadcast message to obtain an IP address allocated by the supporting device. Exemplarily, the benefit device B-UE and the support device S-UE may be user equipment such as a mobile phone. Before the B-UE receives the broadcast message sent by the S-UE, the S-UE is attached to the MME corresponding to the S-UE.

On the Mobility Management Entity (Mobility Management Entity), the S-MME indicates that the S-MME establishes the 7-load and context information on the core network side for the S-UE. Then, the S-UE sends a broadcast message to the B-UE, where the broadcast message includes the S-UE short-range communication SRC id

(identity, identity), when the B-UE receives the SRC id, uses the SRC id to access the S-UE through the SRC mode, and the S-UE allocates an internal IP to the accessed B-UE (Internet Protocol, Internet communication) Protocol) Address, so that the B-UE communicates with the S-UE through the IP address.

102. The benefit device sends a radio resource control RRC message to the supporting device by using the IP address, so that the supporting device sends an uplink RR C message to the base station, so that the base station and the mobility management entity corresponding to the benefit device establish a core network side bearer and context for the benefit device. Information, the uplink RR C message includes an RRC message. Specifically, after acquiring the IP address, the B-UE can use the IP address to send an RRC message to the S-UE in an SRC manner, where the RRC message can include a GU- (Globally Unique Temporary UE Identity) of the B-UE. The temporary UE identifier is configured to enable the MME corresponding to the B-UE to identify the B-UE by using the identifier. When receiving the RRC (Radio Resource Control) message, the S-UE sends an uplink RRC message to the eNB, where the uplink RRC message includes an RRC message sent by the B-UE to the SUE. The RRC message includes a NAS (Non Access Stratum) message of the B-UE. After receiving the uplink RRC message sent by the S-UE, the eNB obtains an RRC message sent by the B-UE to the S-UE from the uplink RRC message, and solves the NAS message of the B-UE in the RRC message, where the eNB will The NAS message is sent to the MME corresponding to the B-UE, and is represented by the B-MME. The B-MME establishes a core network side bearer for the B-UE, and establishes context information for the B-UE on the eNB. When the S-UE receives the RRC message sent by the B-UE, the S-UE may be in an idle state or may be in a connected state. Considering this situation, the B-UE sends an RRC to the S-UE through the IP address. Before the message, the B-UE learns that the S-UE is in the connected state, or learns that the S-UE is not connected to the eNB and is in an idle state.

 Specifically, the B-UE sends a request message to the S-UE, and when the S-UE is connected to the eNB and is in the connected state, the B-UE receives the response message returned by the S-UE; or, the S-UE is not connected to the eNB. When in the idle state, the B-UE receives a response message returned by the S-UE, where the S-UE sends an initial message to the mobility management entity corresponding to the S-UE by sending an RRC connection request message to the eNB. The mobility management entity corresponding to the S-UE is sent after the bearer and context information is established for the S-UE.

Alternatively, the B-UE receives the response message returned by the S-UE, and the RRC connection request message includes a request message, where the response message is included in the RRC connection response message. The response message is that the S-UE sends an RRC connection request message to the eNB, the eNB sends an initial message to the mobility management entity corresponding to the S-UE, and the mobility management entity corresponding to the S-UE establishes the bearer and the context information for the S-UE. Sent. The request message or the response message may be an RRC message, or may be other special format messages, and may be preset in the S-UE and the B-UE, for example, setting a bit on the B-UE. "For the format of the request message, the response message is a three-bit "111" response message. Or, after the S-UE receives the RRC message sent by the B-UE by using the IP address, the S-UE establishes a connection with the eNB. Specifically, when the S-UE is connected to the eNB and is in the connected state, the S-UE sends an uplink RRC message to the eNB; or, when the S-UE is not connected to the eNB and is in an idle state, the S-UE sends an RRC connection to the eNB. The request message is used to trigger the eNB to send an initial message to the S-MME corresponding to the S-UE, so that the S-MME establishes bearer and context information for the S-UE. The RRC connection request message includes an S-TMS (System Architecture Evolution)-Temporary Mobile Subscriber Identity (Scenario Mobile Subscriber Identity), and the S-UE is also included in the initial message. S-TMSI, in this way, after receiving the S-TMSI initial message including the S-UE sent by the eNB, the S-MME can establish the core network side bearer and context information for the S-UE. In this way, when the S-UE is connected to the eNB, the S-UE sends an uplink RRC message to the eNB. The uplink RRC message includes an RRC message received by the S-UE from the B-UE.

The benefit device receives the RRC connection reconfiguration message sent by the supporting device, and the RRC connection reconfiguration message is sent after the supporting device configures the protocol stack that is carried on the supporting device side for the benefit device, and sends the downlink RRC message sent by the base station. The downlink RRC message includes an RRC connection reconfiguration message, so that the single-link multi-user device synthesis communication is performed between the benefit device and the supporting device. Specifically, after the B-MME completes the establishment of the core network side bearer and the context information for the B-UE, the eNB configures the single-link MUCC for the S-UE and the B-UE, that is, configures the S-UE and the B-UE respectively. Protocol stack on the eNB side. Then, the eNB sends an RRC connection reconfiguration message to the S-UE, so that the S-UE configures the B-UE to synthesize the protocol stack carried on the S-UE side. The eNB sends an RRC connection reconfiguration message to the B-UE in the downlink RRC message of the eNB to the S-UE, and the eNB sends a downlink RRC message to the S-UE, where the downlink RRC message includes the RRC connection to be eNB connected to the B-UE. With the message, the S-UE sends the RRC connection reconfiguration message to the B-UE in the SRC mode. In this way, after receiving the RRC connection reconfiguration message of the B-UE, the S-UE establishes a single-link MUCC between the S-UE and the B-UE, and the B-UE can send data to the eNB through the single-link MUCC. That is, the B-UE can communicate with the eNB by forwarding data through the S-UE. The embodiment of the present invention provides a method for connecting initial signaling, and the benefit device receives the broadcast message sent by the support device, and accesses the support device according to the broadcast message to obtain the IP address allocated by the support device, and the benefit device supports the IP address. Device sends radio resource control The RRC message is configured to enable the supporting device to send an uplink RRC message to the base station, so that the mobility management entity corresponding to the base station and the benefit device establishes core network side bearer and context information for the benefit device, and the uplink RRC message includes an RRC message, and the base station is a benefit device and The supporting device configures the protocol stack on the base station side, and the supporting device configures the protocol stack on the supporting device side for the benefit device. After the supporting device receives the downlink RRC message sent by the base station, the receiving device receives the RRC sent by the supporting device. The reconfiguration message is connected, and the downlink RRC message includes an RRC connection reconfiguration message, and the single-link multi-user equipment synthesis communication is successfully established between the benefit device and the supporting device, so that the B-UE can establish a single chain without connecting to the eNB. Road MUCC. A further embodiment of the present invention provides a method for connecting initial signaling, as shown in FIG. 2, including:

201. The supporting device sends a broadcast message to the benefit device, so that the benefit device accesses the supporting device according to the broadcast message, and obtains an IP address allocated by the supporting device. Exemplarily, when the S-UE is attached to the S-MME, the S-MME establishes core network side bearer and context information for the S-UE, and then the S-UE sends a broadcast message to the B-UE, where The broadcast message includes the id of the S-UE. In this way, when receiving the id sent by the S-UE, the B-UE can access the S-UE in the SRC mode by using the id, and the S-UE sends an allocation message to the B-UE, where the allocation message includes the S-UE. B - The IP address assigned by the UE, and the assigned IP address is sent to the S-UE.

202. The supporting device receives the radio resource sent by the benefit device by using the IP address to control the first RRC message. Specifically, after obtaining the IP address, the B-UE may use the IP address and send the first RRC message to the S-UE in an SRC manner, where the first RRC message may include the GUTI identifier of the B-UE, such that B- The MME corresponding to the UE may identify the B-UE by using the identifier.

203. The supporting device sends a second RRC message to the base station, where the second RRC message includes the first RR C message, so that the base station and the mobility management entity corresponding to the benefit device establish a core network side bearer and context information for the benefit device. Specifically, after receiving the first RRC message sent by the B-UE, the S-UE sends a second RRC message to the eNB, where the second RRC message includes the first that the B-UE sends to the S-UE. RRC message. The NAS message of the B-UE is included in the first RRC message. After receiving the second RRC message sent by the S-UE, the eNB obtains a first RRC message sent by the B-UE to the S-UE from the second RRC message, and solves the B-UE in the first RRC message. The eNB sends the NAS message to the MME corresponding to the B-UE, and the B-MME indicates that the B-MME establishes a core network side bearer for the B-UE, and establishes context information for the B-UE on the eNB. The S-UE establishes a connection with the eNB after the S-UE receives the first RRC message sent by the B-UE through the IP address. Specifically, when the S-UE is connected to the eNB and is in the connected state, the S-UE sends the second RRC message to the eNB; or, when the S-UE is not connected to the eNB and is in the idle state, the S-UE sends the RRC to the eNB. The connection request message is sent to the eNB to send an initial message to the S-MME corresponding to the S-UE, so that the S-MME establishes bearer and context information for the S-UE. The RRC connection request message includes the S-TMSI of the S-UE, and the initial message also includes the S-TMSI of the S-UE, such that the S-MME receives the S-TMSI including the S-UE sent by the eNB. After the initial message, bearer and context information can be established for the S-UE. In this way, when the S-UE is in the connected state with the eNB, the S-UE sends an uplink RRC message to the eNB. The uplink RRC message includes an RRC message received by the S-UE from the B-UE. Or, in the case that the S-UE may be in the idle state or the connected state, before the S-UE receives the first RRC message sent by the B-UE by using the IP address, the S-UE notifies the B-UE that the S-UE is in the connected state. .

 Specifically, the S-UE receives the request message sent by the B-UE, and when the S-UE is connected to the eNB and is in the connected state, the S-UE sends a response message to the B-UE, so that the B-UE learns that the S-UE is connected. state.

Or, when the S-UE is not connected to the eNB and is in an idle state, the S-UE returns a response message to the B-UE, where the response message is that the S-UE sends an RRC connection request message to the eNB, and the triggering eNB corresponds to the S-UE. The mobility management entity sends an initial message, so that the mobility management entity corresponding to the S-UE sends the bearer and the context information after the S-UE is established; or the S-UE returns a response message to the B-UE, where the RRC connection request message includes the request. And the response message is included in the RRC connection response message, where the S-UE sends an RRC connection request message to the eNB, and the eNB sends an initial message to the MME corresponding to the S-UE, where the MME corresponding to the S-UE is S-UE is sent after the bearer and context information is established. The request message sent by the B-UE to the S-UE or the response message sent by the S-UE to the B-UE may be an RRC message, or may be a special agreement between the UEs, and may be in the S-UE and The B-UE is preset, for example, a bit "l" is set in the format of the request message on the B-UE, and the response message is a three-bit "111" as a response message, and no limitation is made here. The RRC connection request message may include an S-TMSI of the S-UE. After receiving the RRC connection request message, the eNB encapsulates the S-TMSI of the S-UE in the connection request message in an initial message to the S- The MME sends an initial message including the S-TMSI of the S-UE, so that the S-MME establishes core network side bearer and context information for the S-UE.

204. The supporting device receives the first RRC connection reconfiguration message sent by the base station, and configures, according to the first RRC connection reconfiguration message, a protocol stack that is carried on the supporting device side. Specifically, before the S-UE receives the first RRC connection reconfiguration message sent by the eNB, the B-MME completes establishment of the core network side bearer and context information for the B-UE, and the eNB configures the S-UE and the B-UE for the B-UE. The link MUCC is configured to configure the protocol stack on the base station side for the S-UE and the B-UE, respectively. Then, the eNB sends an RRC connection reconfiguration message to the S-UE, so that the S-UE configures the B-UE to synthesize the protocol stack carried on the supporting device side.

 205. The supporting device receives a third RRC message sent by the base station. The third RRC message includes an RRC connection reconfiguration message sent by the eNB to the B-UE, that is, the eNB sends the RRC connection reconfiguration message to the B-UE in the third RRC message of the eNB to the S-UE.

206. The supporting device parses the third RRC message, obtains a second RRC connection reconfiguration message sent by the base station to the benefit device, and sends the second RRC connection reconfiguration message to the benefit device, so that the benefit device establishes a connection with the supporting device. Link multi-user equipment synthesizes communications. Specifically, the third RRC message includes a second RRC connection reconfiguration message to be sent by the eNB to the B-UE, and after receiving the third RRC message, the S-UE parses the third RRC message to obtain a third RRC message. The second RRC connection reconfiguration message is sent by the S-UE to the B-UE by using the SRC mode. In this way, after receiving the second RRC connection reconfiguration message of the S-UE, the B-UE establishes a single-link MUCC between the S-UE and the B-UE, and the B-UE can pass the single-link MUCC to the eNB. The data is transmitted, that is, the B-UE can communicate with the eNB by forwarding data through the S-UE. The embodiment of the present invention provides a method for connecting initial signaling, where the supporting device sends a broadcast message to the benefit device, so that the benefit device accesses the supporting device according to the broadcast message, and obtains an IP address allocated by the supporting device, and the supporting device receives the benefit device through the IP. The radio resource sent by the address controls the first RRC message, and further sends a second RRC message to the base station, where the second RRC message includes The first RRC message is configured to enable the mobility management entity corresponding to the base station and the benefit device to establish the core network side bearer and context information for the benefit device, and after the base station configures the protocol stack of the base station side for the benefit device and the support device respectively, the support device receives the base station and sends the base station. The first RRC connection reconfiguration message is configured to synthesize a protocol stack that is carried on the supporting device side for the benefit device according to the first RRC connection reconfiguration message, and the supporting device receives the third RRC message sent by the base station, and the supporting device performs the third RRC message. Parsing, obtaining a second RRC connection reconfiguration message sent by the base station to the benefit device, and sending the second RRC connection reconfiguration message to the benefit device, so that the benefit device establishes a single-link multi-user device synthesis communication with the supporting device, which enables The B-UE can establish a single-link MUCC without connecting to the eNB. A further embodiment of the present invention provides a method for connecting initial signaling, as shown in FIG. 3, including:

301. After the benefiting device sends the first radio resource control RR C message to the supporting device, the base station receives the second RRC message sent by the supporting device, where the second RRC message includes the first RRC message. Exemplarily, before the B-UE sends the first RRC message to the S-UE, the S-UE is attached to the MME corresponding to the S-UE, and is represented by the S-MME, and the S-MME establishes the core network side for the S-UE. Bearer and context information. Then, the S-UE sends a broadcast message to the B-UE, where the broadcast message includes the short-range communication SRC id of the S-UE, so that the B-UE accesses the S-UE by using the SRC id when receiving the SRC id. The S-UE allocates an internal IP address to the accessed B-UE, so that the B-UE communicates with the S-UE through the IP address. Then, the B-UE sends the first RRC message to the S-UE in the SRC mode, where the first RRC message includes the GUTI of the B-UE, so that the MME corresponding to the B-UE can identify the B-UE through the GUTI. Then, the S-UE sends a second RRC message to the eNB, where the second RRC message includes a first RRC message sent by the B-UE to the S-UE. After the B-UE sends the first radio resource control RRC message to the S-UE, the eNB establishes a connection with the S-UE. Specifically, when the S-UE is connected to the eNB and is in the connected state, the eNB receives the second uplink RRC message sent by the S-UE; when the S-UE is not connected to the eNB and is in the idle state, the eNB receives the S-UE transmission. The RRC connection request message sends an initial message to the mobility management entity corresponding to the S-UE, so that the mobility management entity corresponding to the S-UE establishes bearer and context information for the S-UE. Alternatively, the eNB establishes a connection with the S-UE before the B-UE sends the radio resource control RRC message to the S-UE.

 Specifically, when the B-UE sends a request message to the S-UE, and the S-UE is not connected to the eNB and is in an idle state, the eNB receives the RRC connection request message sent by the S-UE, and the eNB receives the RRC sent by the S-UE. After the connection request message is sent, the initial message is sent to the mobility management entity corresponding to the S-UE, so that the mobility management entity corresponding to the S-UE establishes bearer and context information for the S-UE, and the S-UE returns a response message to the B-UE. . Or, when the B-UE sends a radio resource control RRC message to the S-UE, and the S-UE is not connected to the eNB and is in an idle state, the eNB receives an RRC connection request message sent by the S-UE, where the RRC connection request message includes a request message. The eNB sends an initial message to the mobility management entity of the S-UE, so that the mobility management entity corresponding to the S-UE establishes bearer and context information for the S-UE, and then the eNB returns an RRC connection response message to the S-UE, so that the S- The UE returns a response message to the B-UE, and the response message is included in the RRC Connection Response message.

 The request message sent by the B-UE to the S-UE or the response message sent by the S-UE to the B-UE may be an RRC message, or may be a special agreement between the UEs, and may be in the S-UE and the B- The UE is preset in advance, for example, a bit "l" is set in the format of the request message on the B-UE, and the response message is a three-bit "111" as a response message, and no limitation is made here.

302. The base station establishes a core network side bearer and context information for the benefit device by using the mobility management entity corresponding to the benefit device according to the second RRC message. Specifically, the eNB sends the NAS message of the B-UE to the first RRC message sent by the B-UE to the S-UE, and the RRC message of the B-UE is included in the second RRC message sent by the S-UE to the eNB. Deleting the NAS message of the B-UE in the received second RRC message, and sending the NAS message to the B-MME, the B-MME establishes a core network side bearer for the B-UE according to the NAS message, and is in the eNB. The B-UE establishes context information.

303. The base station configures a protocol stack on the base station side for the supporting device and the benefit device respectively.

304. The base station sends a first RRC connection reconfiguration message to the supporting device, so that the supporting device configures, for the benefit device, a protocol stack that is carried on the supporting device side. Specifically, after the B-MME establishes the core network side bearer and context information for the B-UE, the eNB configures the single-link MUCC for the S-UE and the B-UE, that is, the S-UE and the B-UE are respectively configured. a protocol stack on the base station side, and then the eNB sends a first RRC connection reconfiguration message to the S-UE, so that The S-UE configures a protocol stack that is carried on the supporting device side for the B-UE.

305. The base station sends a third RRC message to the supporting device, so that the supporting device parses the third RRC message, obtains a second RRC connection reconfiguration message sent by the base station to the benefiting device, and sends the second RRC connection reconfiguration message to the Benefit from equipment. Specifically, after the S-UE establishes a composite bearer corresponding to the bearer for the B-UE, the eNB sends a second RRC connection reconfiguration message to the B-UE in the third RRC message of the eNB to the S-UE, and the eNB goes to the S. The UE sends a third RRC message, the third RRC message includes a second RRC connection reconfiguration message to be sent by the eNB to the B-UE, and the S-UE parses the received third RRC message to obtain the second RRC message included therein. The RRC connects the reconfiguration message, and sends the second RRC connection reconfiguration message to the B-UE in an SRC manner.

306. The base station establishes a single-link multi-user device synthesis communication between the benefit device and the support device.

 In this way, after receiving the RRC connection reconfiguration message of the B-UE, the S-UE establishes a single-link MUCC between the S-UE and the B-UE, and the B-UE can send data to the eNB through the single-link MUCC. That is, the B-UE can communicate with the eNB by forwarding data through the S-UE. The embodiment of the present invention provides a method for connecting initial signaling. After the benefiting device sends the first radio resource control RR C message to the supporting device, the base station receives the second RRC message sent by the supporting device, where the second RRC message includes the first RRC message. The base station, according to the second RRC message, establishes a core network side bearer and context information for the benefit device by using the mobility management entity corresponding to the benefit device, and the base station configures the protocol stack of the base station side for the supporting device and the benefit device respectively, and sends the protocol stack to the supporting device. The first RRC is connected to the reconfiguration message, so that the supporting device configures the protocol stack that is carried on the supporting device side for the benefit device, and the base station sends a third RRC message to the supporting device, so that the supporting device parses the third RRC message, and obtains the base station to send Sending a second RRC connection reconfiguration message to the benefit device, and sending a second RRC connection reconfiguration message to the benefit device, the base station establishes a single link multi-user device synthesis communication between the benefit device and the support device, enabling the B-UE to A single-link MUCC can be established without being connected to the eNB. Another embodiment of the present invention provides a method for connecting initial signaling, as shown in FIG. 4, including:

401. The supporting device accesses the mobility management entity corresponding to the supporting device, so that the mobility management entity corresponding to the supporting device establishes a core network side bearer and a context for the supporting device. Information. Specifically, when the S-UE attaches (attached) to the S-MME, the S-MME establishes core network side loading and context information for the S-UE. The MME is a control node that processes signaling interaction between the UE and the core network, and the main functions include saving mobility management context information of the UE, such as user identifier, mobility management status, location information, etc., and processing the NAS signaling. , responsible for the security of NAS signaling.

402. The supporting device sends a broadcast message to the benefit device. Specifically, after the S-MME establishes the core network side bearer and the context information for the S-UE, the S-UE sends a broadcast message to the B-UE, where the broadcast message may include short-distance communication between the S-UE and the B-UE. SRC id. The SRC can be a technology such as Bluetooth or WiFi.

403. The beneficiary device accesses the supporting device according to the broadcast message, and obtains an IP address allocated by the supporting device. Specifically, after receiving the SRC id sent by the S-UE, the B-UE can access the S-UE in an SRC manner according to the id, and the S-UE allocates an internal IP address to the B-UE, and allocates the allocated IP address. The address is sent to the B-UE so that the B-UE communicates with the S-UE through the IP address.

404. The beneficiary device sends a radio resource control RRC message to the supporting device by using an IP address. Specifically, after receiving the IP address sent by the S-UE, the B-UE sends an RRC message to the S-UE in an SRC manner according to the IP address, where the RRC message may include the GUTI of the B-UE, so as to facilitate The MME corresponding to the B-UE can identify the B-UE through the GUTI.

405. The supporting device sends an uplink RRC message to the base station. Exemplarily, after the S-UE receives the RRC message sent by the B-UE by using the IP address, if the S-UE is connected to the eNB and is in the connected state, the S-UE sends an uplink RRC message to the eNB, between the devices. The interaction is as shown in FIG. 5; if the S-UE is not connected to the eNB and is in the idle state, the S-UE sends an RRC connection request message to the eNB, so that the eNB sends an initial message to the S-MME corresponding to the S-UE, that is, the S-MME, The S-MME is configured to establish bearer and context information for the S-UE. The RRC connection request message includes the S-TMSI of the S-UE, and the initial message also includes the S-TMSI of the S-UE, such that the S-MME receives the S-TMSI including the S-UE sent by the eNB. After the initial message, the core network side bearer and context information can be established for the S-UE. In this way, when the S-UE is connected to the eNB, the S-UE sends an uplink RRC message to the eNB. The uplink RRC The message includes the RRC message received by the S-UE from the B-UE, and the interaction between the devices is as shown in FIG. 6. Or, in the case that the S-UE may be in an idle state or a connected state, optionally, before the S-UE receives the radio resource control RRC message sent by the B-UE by using the IP address, the S-UE receives the B-UE transmission. Requesting a message, so that the B-UE establishes a connection with the S-UE. When the S-UE is connected to the eNB and is in the connected state, the S-UE sends a response message to the B-UE, so that the B-UE learns that the S-UE is connected. When the S-UE is not connected to the eNB and is in an idle state, the S-UE sends an RRC Connection Request message to the eNB, so that the eNB sends an initial message to the mobility management entity corresponding to the S-UE, so that the S-UE corresponds to The mobility management entity establishes bearer and context information for the S-UE, and the S-UE sends a response message to the B-UE, so that the B-UE learns that the S-UE is in the connected state. Then, the S-UE receives the radio resource control RRC message sent by the B-UE through the IP address, and the interaction between the devices is as shown in FIG. 7. The request message sent by the B-UE to the S-UE may be an RRC message, or may be a special agreement between the UEs. The RRC connection request message may include an S-TMSI of the S-UE. After receiving the RRC connection request message, the eNB encapsulates the S-TMSI of the S-UE in the connection request message in an initial message, to the S- The MME sends an initial message containing the S-TMSI of the S-UE, so that the S-MME establishes bearer and context information for the S-UE. Or, for the case that the S-UE may be in an idle state or a connected state, before the S-UE receives the RRC message sent by the B-UE by using the IP address, the S-UE receives the request message sent by the B-UE, so as to facilitate the B- The UE establishes a connection with the S-UE. When the S-UE is connected to the eNB and is in the connected state, the S-UE returns a response message to the B-UE, so that the B-UE learns that the S-UE is in the connected state; when the S-UE is not connected to the eNB and is in the idle state The S-UE sends an RRC connection request message to the eNB, where the RRC connection request message includes a request message sent by the B-UE to the S-UE, so that the eNB sends an initial message to the S-MME of the S-UE, so as to be corresponding to the S-UE. The mobility management entity establishes bearer and context information for the S-UE. Then, the S-UE receives the RRC connection response message returned by the eNB, and the connection response message includes a response message that the eNB returns to the B-UE, so that the S-UE sends the response message to the B-UE, and the interaction between the devices is as shown in FIG. 8. Shown. The request message sent by the B-UE to the S-UE may be an RRC message, or may be a special agreement between the UEs, which is not limited herein. The RRC connection request message includes the S-TMSI of the S-UE, and the eNB is in connection with the request message sent by the B-UE to the S-UE. After receiving the RRC connection request message, the S-TMSI packet of the S-UE in the connection request message is sent to the S-MME to send an initial message including the S-TMSI of the S-UE to the S-MME. The MME establishes bearer and context information for the S-UE. Then, the eNB sends a response message to the B-UE in the RRC connection response message of the eNB to the S-UE, and sends the RRC connection response message to the S-UE, and then the S-UE sends the response of the eNB to the B-UE. The message is sent to the B-UE, so that the B-UE knows that the S-UE is already in the connected state and continues to connect the initial signaling with the S-UE. The response message sent by the eNB to the B-UE may be an RRC message, or may be other conventions, which is not limited herein. In the idle state, the UE receives the system information broadcast by the eNB, and the MME allocates an identifier to identify the UE independently in one tracking area, and the eNB does not store the RRC context information of the UE. When the UE is in the connected state, the UE establishes an RRC connection, the eNB stores the context information of the UE, the eNB knows the cell to which the UE belongs, the network can perform data transmission and reception with the UE, and the network controls the mobility process, such as handover, etc., the eNB controls The DRX (Discontinuous Reception) period is configured according to the activation level of the UE, so that the UE can save power and utilize resources efficiently. When the UE is in the connected state, it can be divided into a synchronous state and an out-of-step state. When the UE is in the connection synchronization state, the uplink data may be sent to the eNB. When the UE is in the out-of-synchronization state, the UE cannot send uplink data to the eNB except for initiating random access. To recover from the lost gait state to the synchronous state, the UE needs to initiate random access.

 406. The base station establishes core network side bearer and context information for the benefit device according to the uplink RRC message, and the mobility management entity corresponding to the benefit device, where the uplink RR C message includes an RRC message.

 For example, the eNB includes an RRC message sent by the B-UE to the S-UE in the RRC message received by the eNB, where the RRC message includes the NAS message of the B-UE, and the eNB receives the uplink RRC message. Then, the NAS message of the B-UE is obtained from the uplink RRC message, and the NAS message is sent to the B-MME corresponding to the B-UE, and the B-MME establishes a core for the B-UE according to the NAS message. The network side carries the bearer, and establishes core network side bearer and context information for the B-UE on the eNB.

 When the eNB does not find the MME corresponding to the B-UE, the eNB selects a suitable new MME for the B-UE, and sends the GUTI in the NAS message of the B-UE to the new MME.

407. The base station configures a protocol stack on the base station side for the beneficiary device and the supporting device. Specifically, after the core network side bearer and context information are established for the B-UE, the eNB configures a single-link MUCC for the S-UE and the B-UE, that is, respectively configured for the S-UE and the B-UE. The protocol stack on the base station side. The granularity of the application of the MUCC technology is a bearer, and the bearer is used for transmitting control signaling on the control plane, and transmitting service parameters on the user plane. When a bearer is set up on the B-UE, and the MUCC is to be applied to the bearer, the S-UE has a composite bearer corresponding to the bearer, and the composite bearer established on the S-UE is only served by the B-UE. The S-UE's own data will not be transmitted. Correspondingly, the eNB also establishes two corresponding composite payloads for the bearer on the B-UE and the composite bearer on the S-UE. In addition, the protocol stack of the MUCC technology is different from the traditional LTE (Long Term Evolution) protocol stack. A composite layer needs to be added to the protocol stack. The composite layer can be added in different locations, for example, can be added to the PDCP ( At the Packet Data Convergence Protocol layer, it can also be added between the PDCP layer and the RLC (Radio Link Control) layer. For example, in the case of uplink data transmission, when the uplink data is transmitted by using the MUCC technology, the main function of the composite layer on the B-UE is packet shunting and passing. The SRC method transmits the data packet to the S-UE. In order to distinguish which composite bearer the data packet belongs to on the S-UE, some header information is added to the data packet. The main function of the synthesis layer on the S-UE is to map each packet from the B-UE received through the SRC mode to a certain composite bearer on the S-UE according to the header information added on the S-UE synthesis layer. . At the transmitting end, each layer receives an SDU (Service Data Unit) from a higher layer, and outputs a PDU (Protocol Data Unit) to the bottom layer. For example, the RLC layer receives packets from the PDCP layer, which are PDCP PDUs from the perspective of PDCP, and are RLC SDUs from the perspective of RLC, and the RLC layer is generated for the MAC (Medium Access Control) layer. Packets, these packets passed to the MAC are RLC PDUs from the perspective of the RLC, and MAC SDUs from the MAC perspective. At the receiving end, this process is reversed. Each layer sends an SDU to the upper layer, and the upper layer receives it as a PDU. In this way, on the B-UE, the PDCP SDU enters the PDCP layer, outputs the PDCP PDU, enters the synthesis layer, and sends the PDCP PDU to the S-UE through the SRC mode. The S-UE maps the PDCP PDU to the corresponding composite bearer, and further proceeds to enter the RLC layer of the composite bearer, and The RLC PDU is output, and then enters the MAC layer, the PHY (Physical Layer), and is sent to the eNB. The data received by the eNB is changed into a MAC SDU through the PHY layer and the MAC layer, and the composite bearer corresponding to the S-UE is entered on the eNB, and then mapped to the bearer corresponding to the B-UE on the eNB through the RLC layer, and enters the PDCP layer. Convergence with the data of the bearer sent by the B-UE, gathered together. The protocol stack of the single-link MUCC is similar to that of the general MUCC. The difference is that the B-UE can communicate with only the composite bearer of the S-UE, and cannot directly communicate with the eNB.

408. The base station sends an RRC connection reconfiguration message to the supporting device, so that the supporting device configures, for the benefit device, a protocol stack that is carried on the supporting device side.

 Specifically, after the eNB configures the protocol stack of the base station side for the B-UE and the S-UE, the eNB sends an RRC connection reconfiguration message to the S-UE, so that the S-UE configures the composite bearer on the supporting device side for the B-UE. Protocol stack.

409. The base station sends a downlink RRC message to the supporting device, where the downlink RRC message carries an RRC connection reconfiguration message to be sent by the base station to the benefit device.

 Specifically, after the S-UE establishes the composite bearer for the B-UE, the eNB sends the RRC connection reconfiguration message to the B-UE in the downlink RRC message of the eNB to the S-UE, and then the eNB sends the S-UE to the S-UE. And a downlink RRC message, where the downlink RRC message includes an RRC connection reconfiguration message sent by the eNB to the B-UE.

410. The supporting device sends an RRC connection reconfiguration message to the benefit device, and the single-link multi-user device synthesis communication between the supporting device and the benefit device is completed.

Specifically, when the S-UE receives the downlink RRC message sent by the eNB, the downlink RRC message includes an RRC connection reconfiguration message sent by the eNB to the B-UE, and the S-UE sends the RRC connection reconfiguration message through the SRC mode. To the B-UE, in this way, the single-link MUCC establishment between the S-UE and the B-UE is completed, and the B-UE can transmit the data through the established single-link MUCC with the S-UE as the medium-turning eNB. In this way, when the S-UE can be normally connected to the eNB, the channel quality between the B-UE and the eNB is not good, or the eNB does not cover the B-UE, and the B-UE cannot connect to the eNB normally, the B-UE does not have to The eNB establishes a connection direct communication, and can establish a single link MUCC with the nearby S-UE, thereby communicating with the eNB by means of the composite bearer on the S-UE. That is, the single-link MUCC is completed by the agent of the S-UE, and enters the lost gait state. At the same time, when the B-UE moves, if it is detached The coverage of the S-UE may first consider restoring uplink synchronization with the eNB without first initiating reconstruction, and also increasing the coverage of the eNB. As shown in FIG. 9, a schematic diagram of control signaling transmission in a control plane protocol stack before a single-link MUCC is established, and FIG. 10 is a schematic diagram of control signaling transmission in a control plane protocol stack after a single-link MUCC is established, FIG. The data transmission diagram in the user plane protocol stack after the establishment of the single-link MUCC is similar to the data transmission diagram of the user plane protocol stack before the single-link MUCC is established. The embodiment of the present invention provides a method for connecting initial signaling, and the benefit device receives the broadcast message sent by the support device, and accesses the support device according to the broadcast message to obtain the IP address allocated by the support device, and the benefit device supports the IP address. The device sends a radio resource control RRC message, so that the supporting device sends an uplink RRC message to the base station, so that the base station and the mobility management entity corresponding to the benefit device establish a core network side bearer and context information for the benefit device, and the uplink RRC message includes an RRC message. The base station configures the protocol stack on the base station side for the benefit device and the support device, and the support device configures the protocol stack on the support device side for the benefit device. After the support device receives the downlink RRC message sent by the base station, the receiving device receives the downlink RRC message. Supporting the RRC connection reconfiguration message sent by the device, the downlink RRC message includes the RRC connection reconfiguration message, and the single link multi-user device synthetic communication is successfully established between the benefit device and the supporting device, so that the benefit device can complete the single link through the agent supporting the device. Synthetic communication, and increase The coverage of the base station is large.

A further embodiment of the present invention provides a benefit device 01, as shown in FIG. 12, comprising: a receiving unit 011, configured to receive a broadcast message sent by a supporting device. The access unit 012 is configured to access the supporting device according to the broadcast message received by the receiving unit. The obtaining unit 013 is configured to obtain an IP address allocated by the supporting device after the access unit 012 is accessed. The sending unit 014 is configured to send a radio resource control RRC message to the supporting device by using the IP address acquired by the acquiring unit 013, so as to facilitate the support. The device sends an uplink RRC message to the base station, so that the mobility management entity corresponding to the base station and the benefit device establishes a core network side bearer and context information for the benefit device, and the uplink RRC message includes an RRC message. The receiving unit 011 is configured to receive an RRC connection reconfiguration message sent by the supporting device, where the RRC connection reconfiguration message is configured on the supporting device to configure the composite bearer on the supporting device side. After the protocol stack is sent and received by the downlink RRC message sent by the base station, the downlink RRC message includes an RRC connection reconfiguration message. The communication unit 015 is configured to perform single-link multi-user device synthesis communication with the supporting device.

 Further, the access unit 012 is further configured to access the mobility management entity corresponding to the supporting device by using the supporting device. The receiving unit 011 may be specifically configured to: receive a broadcast message of the supporting device, where the broadcast message includes a short-distance communication identifier of the supporting device; The broadcast message of the supporting device is sent after the mobility management entity establishes the core network side bearer and context information for the supporting device;

 The access unit 012 may be specifically configured to: send an access message to the receiving device according to the short-distance communication identifier, so that the supporting device sends an allocation message to the receiving device, where the allocation message includes an IP address allocated by the supporting device for the benefit device; and the receiving unit 011 may be specifically configured to: Receiving an allocation message sent by the supporting device, where the allocation message includes an IP address allocated by the supporting device for the benefit device. Optionally, as shown in FIG. 13, the benefit device 01 may further include:

Before the message, it is known that the supporting device is connected to the base station and is in a connected state; or it is known that the supporting device is not connected to the base station and is in an idle state. Optionally, as shown in FIG. 14, the learning unit 016 includes: a sending subunit 0161, configured to send a request message to the supporting device;

The receiving subunit 0162 is configured to receive, when the learning unit 016 is connected to the base station and in the connected state, receive a response message returned by the supporting device, or to receive the receiving device when the learning unit learns that the supporting device is not connected to the base station and is in an idle state. Supporting the response message returned by the device, the response message is that the supporting device sends the initial message to the mobility management entity corresponding to the supporting device by sending the RRC connection request message to the base station, so that the mobility management entity corresponding to the supporting device establishes the supporting device. After receiving the bearer and the context information, or receiving a response message returned by the supporting device, the RRC connection request message includes a request message, where the response message is included in the RRC connection response message, and the response message is that the supporting device sends the RRC connection request message to the base station. The base station sends an initial to the mobility management entity corresponding to the supporting device. The message is sent after the mobility management entity corresponding to the supporting device establishes bearer and context information for the supporting device. Optionally, the RRC message sent by the sending unit 014 includes the global unique temporary user equipment identifier GUTI of the benefit device; the RRC connection request message received by the receiving subunit 0162 includes the temporary mobile subscriber identity code S-TMSI of the supporting device, and the initial message includes the support. The temporary mobile subscriber identity code S-TMSI of the equipment. An embodiment of the present invention provides a benefit device, which receives a broadcast message sent by a support device through a benefit device, and accesses the support device according to the broadcast message to obtain an IP address allocated by the support device, and the benefit device sends the wireless resource to the support device by using the IP address. Controlling the RRC message, so that the supporting device sends the uplink RRC message to the base station, so that the base station and the mobility management entity corresponding to the benefiting device establish the core network side bearer and context information for the benefiting device, and the uplink RR C message includes the RRC message, which benefits the base station. The device and the supporting device respectively configure the protocol stack on the base station side, and the supporting device configures the protocol stack on the supporting device side for the beneficial device. After the supporting device receives the downlink RRC message sent by the base station, the receiving device receives the supporting device to send. The RRC connection reconfiguration message, the downlink RRC message includes an RRC connection reconfiguration message, and the single-link multi-user device synthesis communication is successfully established between the benefit device and the supporting device, so that the B-UE can be established without being connected to the eNB. Single link MUCC. A further embodiment of the present invention provides a support device 02, as shown in FIG. 15, comprising: a sending unit 021, configured to send a broadcast message to the benefit device, so that the benefit device accesses the support device according to the broadcast message, and obtains the support device allocation. IP address. The receiving unit 022 is configured to receive a first RRC message that is sent by the receiving device by using the IP address, and the sending unit 021 is configured to send a second RRC message to the base station, where the second RRC message includes a first RRC message received by the receiving unit, The mobility management entity corresponding to the base station and the benefit device establishes core network side bearer and context information for the benefit device. The receiving unit 022 is configured to receive a first RRC connection reconfiguration message sent by the base station, where the configuration unit 023 is configured to configure, according to the RRC connection reconfiguration message received by the receiving unit, a protocol stack that is configured to be carried on the supporting device side; The receiving unit 022 is configured to receive a third RRC message sent by the base station, where the processing unit 024 is configured to parse the third RRC message received by the receiving unit, and obtain a second RRC connection reconfiguration message sent by the base station to the benefit device.

 The sending unit 021 is configured to send, by the processing unit, the second RRC connection reconfiguration message to the benefit device, so that the benefit device establishes a single-link multi-user device synthesis communication with the supporting device.

 Further, as shown in FIG. 16, the access unit 025 is configured to access the mobility management entity corresponding to the supporting device, so that the mobility management entity corresponding to the supporting device establishes context information and the core network side for the supporting device. The sending unit 021 is specifically configured to: send a broadcast message to the benefit device, where the broadcast message includes a short-distance communication identifier of the supporting device, so that the benefit device accesses the supporting device according to the short-distance communication identifier;

 The sending unit 021 is further configured to: send an allocation message to the beneficiary device, where the allocation message includes an IP address allocated by the supporting device for the beneficiary device.

 Optionally, as shown in FIG. 17, the supporting device may further include: an establishing unit 026, configured to establish a connection with the base station after the receiving unit 022 receives the first RRC message sent by the beneficial device by using the IP address. Optionally, the establishing unit 026 may include: a first sending subunit 0261, configured to send a second RRC message to the base station when the supporting device is connected to the base station and in a connected state; or the first sending subunit 0261 is configured to When the supporting device is not connected to the base station and is in an idle state, the RRC connection request message is sent to the base station, and the base station is triggered to send an initial message to the mobility management entity corresponding to the supporting device, so that the mobility management entity corresponding to the supporting device establishes a bearer for the supporting device. Contextual information.

Optionally, as shown in FIG. 18, the supporting device may further include: a notification unit 027, configured to notify the receiving device that the supporting device is in a connected state before the receiving unit 022 receives the benefiting device sending the first RRC message by using the IP address. Optionally, the notification unit 027 includes: a second receiving subunit 0271, configured to receive a request message sent by the benefit device; a second sending subunit 0272, configured to send a response message to the benefiting device when the supporting device is connected to the base station and in the connected state; or a second sending subunit 0272, when the supporting device is connected to the base station and is in an idle state, Returning a response message to the benefiting device, the response message is that the sending sub-unit sends an RRC connection request message to the base station, and the triggering base station sends an initial message to the mobility management entity corresponding to the supporting device, so that the mobility management entity corresponding to the supporting device establishes the supporting device. After the bearer and the context information are sent; or when the supporting device is not connected to the base station and is in an idle state, returning a response message to the benefit device, the RRC connection request message includes a request message, and the response message is included in the RRC connection response message; The message is that the supporting device sends an RRC connection request message to the base station, and the base station sends an initial message to the mobility management entity corresponding to the supporting device, and the mobility management entity corresponding to the supporting device sends the bearer and the context information after the supporting device establishes the bearer and the context information. The RRC message includes a global unique temporary user equipment identifier GUTI of the benefit device;

The RRC Connection Request message includes a Temporary Mobile Subscriber Identity S-TMSI supporting the device; the initial message includes a Temporary Mobile Subscriber Identity S-TMSI supporting the device. The embodiment of the present invention provides a supporting device, where the supporting device sends a broadcast message to the benefiting device, so that the benefiting device accesses the supporting device according to the broadcast message, and obtains the IP address allocated by the supporting device, and the supporting device receives the wireless device that the benefit device sends through the IP address. The resource controls the first RRC message, and further sends a second RRC message to the base station, where the second RRC message includes the first RRC message, so that the base station and the mobility management entity corresponding to the benefit device establish the core network side bearer and context information for the benefit device, After the base station configures the protocol stack of the base station side for the benefit device and the supporting device, the supporting device receives the first RRC connection reconfiguration message sent by the base station, and configures a protocol for synthesizing the bearer on the supporting device side according to the first RRC connection reconfiguration message. The stacking device receives the third RRC message sent by the base station, and the supporting device parses the third RRC message, obtains a second RRC connection reconfiguration message sent by the base station to the benefiting device, and sends the second RRC connection reconfiguration message to the benefit. Equipment, so that the benefiting device establishes a single link with the supporting device. Synthesis communication user equipment, B-UE can be made under the premise of without connecting to the eNB, the single link may be established MUCC. A further embodiment of the present invention provides a base station 03, as shown in FIG. 19, including: a receiving unit 031, configured to send, by a beneficiary device, a first radio resource control to a supporting device. After the RRC message, the second RRC message sent by the supporting device is received, where the second RRC message includes the first RRC message. The establishing unit 032 is configured to establish, according to the second RRC message received by the receiving unit 031, the core network side bearer and context information for the benefit device by the mobility management entity corresponding to the benefit device.

 a configuration unit 033, configured to separately configure a protocol stack on the base station side for the supporting device and the benefit device;

 The sending unit 034 is configured to send a first RRC connection reconfiguration message to the supporting device, so that the supporting device configures, for the benefit device, a protocol stack that is carried on the supporting device side.

 The sending unit 034 is further configured to send a third RRC message to the supporting device, so that the supporting device parses the third RRC message, acquires a second RRC connection reconfiguration message sent by the base station to the benefit device, and connects the second RRC connection. The matching message is sent to the benefit device; the establishing unit 032 is configured to establish a single-link multi-user device synthesis communication between the benefit device and the supporting device. Further, the establishing unit 032 may be specifically configured to: obtain a non-access stratum message of the benefit device from the first RRC message carried in the second RRC message;

 The non-access stratum message is sent to the mobility management entity corresponding to the benefit device, so that the mobility management entity corresponding to the benefit device establishes core network side bearer and context information for the benefit device.

 Optionally, the establishing unit 032 is further configured to establish a connection with the supporting device after the benefiting device sends the first RRC message to the supporting device.

Optionally, as shown in FIG. 20, the establishing unit 032 includes: a receiving subunit 0321, configured to receive a second RRC message sent by the supporting device when the supporting device is connected to the base station and in a connected state; or receive the subunit 0321, The RRC connection request message sent by the supporting device is received when the supporting device is not connected to the base station and is in an idle state; the sending subunit 0322 is configured to send an initial to the mobility management entity corresponding to the supporting device. The message enables the mobility management entity corresponding to the supporting device to establish bearer and context information for the supporting device. Optionally, the establishing unit 032 is further configured to establish a connection with the supporting device before the benefiting device sends the RRC message to the supporting device. Optionally, as shown in FIG. 21, the establishing unit 032 specifically includes: a receiving subunit 1032, configured to send a request message to the supporting device when the receiving device is not connected to the base station, and when the supporting device is in an idle state, the receiving supporting device sends RRC connection request message;

 The sending sub-unit 0324 is configured to send an initial message to the mobility management entity corresponding to the supporting device, so that the mobility management entity corresponding to the supporting device returns a response message to the benefit device after establishing the bearer and context information for the supporting device. Or the receiving sub-unit 0323 is configured to send a request message to the supporting device when the receiving device is not connected to the base station and is in an idle state, and receive an RRC connection request message sent by the supporting device, where the RRC connection request message includes a request message; a sub-unit 0324, configured to send an initial message to the mobility management entity of the supporting device, so that the mobility management entity corresponding to the supporting device establishes bearer and context information for the supporting device, and returns an RRC connection response message to the supporting device, so that The supporting device returns a response message to the benefiting device, and the response message is included in the RRC connection response message. The first RRC message received by the receiving unit 031 includes a globally unique temporary user equipment identifier GUTI of the benefit device;

The RRC Connection Request message includes a Temporary Mobile Subscriber Identity S-TMSI supporting the device; the initial message includes a Temporary Mobile Subscriber Identity S-TMSI supporting the device. The embodiment of the present invention provides a base station, after the benefiting device sends the first radio resource control RRC message to the supporting device, the base station receives the second RRC message sent by the supporting device, where the second RRC message includes the first RRC message, and the base station according to the second RRC message, and the core network side bearer and context information are established for the benefit device by the mobility management entity corresponding to the benefit device, the base station configures the protocol stack of the base station side for the supporting device and the benefit device, and sends the first RRC connection reconfiguration to the supporting device. The message is configured to enable the supporting device to configure the protocol stack that is carried on the supporting device side for the benefit device, and the base station sends a third RRC message to the supporting device, so that the supporting device will The third RRC message is parsed, the second RRC connection reconfiguration message sent by the base station to the benefit device is obtained, and the second RRC connection reconfiguration message is sent to the benefit device, and the base station establishes a single link multi-user between the benefit device and the support device. The device synthesizes communication, enabling the B-UE to establish a single-link MUCC without connecting to the eNB. A further embodiment of the present invention provides a benefit device 04, as shown in FIG. 22, comprising: a bus 041, a processor 0412, a transmitter 043, a receiver 044, and a memory 045, wherein the memory 045 is configured to store an instruction, where The receiver 044 executes the instruction for receiving a broadcast message sent by the supporting device, and the processor 042 is configured to execute the instruction for accessing the supporting device according to the broadcast message received by the receiver 044, and acquiring an IP address allocated by the supporting device; The 043 is configured to send the RRC message to the supporting device by using the IP address obtained by the processor 042, so that the supporting device sends the uplink RRC message to the base station, so that the base station and the mobility management entity corresponding to the benefit device benefit. The RRC connection reconfiguration message is sent by The device configuration is synthesized and carried in the protocol stack on the supporting device side, and receives the downlink RRC sent by the base station. Downlink RRC message comprises transmitting an RRC connection reconfiguration message, the processor 042 for executing instructions for the synthesis of a communication between the receiver receives the RRC connection reconfiguration message, a single link with a supporting device for a multi-user equipment. In the embodiment of the present invention, optionally, the processor 042 executes the instruction, and is used to access the mobility management entity corresponding to the supporting device by using the supporting device. The receiver 044 executes the instruction, where the instruction is specifically used to: receive a broadcast message of the supporting device. The broadcast message includes a short-distance communication identifier of the supporting device; the broadcast message of the supporting device is sent after the mobility management entity establishes the core network-side bearer and context information for the supporting device; the processor 042 executes the instruction specifically for: according to the short distance The communication identifier is connected to the support device, so that the support device sends an assignment message to the benefit device, and the assignment message includes an IP address allocated by the support device for the benefit device. The receiver 044 performs the instruction specifically for: receiving an assignment message sent by the support device, and allocating the message. Includes the IP address assigned to the benefit device by the supporting device. In the embodiment of the present invention, optionally, the processor 042 executes the instruction, and is further configured to: before the transmitter 043 executes the instruction, to send an RRC message to the supporting device by using an IP address, The supporting device is in a connected state; or it is known that the supporting device is not connected to the base station and is in an idle state. In the embodiment of the present invention, optionally, the transmitter 043 executes the instruction to send a request message to the supporting device. The receiver 044 executes the command, specifically for the processor 042 to learn that the supporting device is connected to the base station and is in the connection. Receiving a response message returned by the supporting device; or the receiver 044 executing the instruction is specifically configured to: when the processor 042 learns that the supporting device is not connected to the base station and is in an idle state, the receiver 044 receives a response message returned by the supporting device, The response message is sent by the supporting device by sending an RRC connection request message to the base station, and triggering the base station to send an initial message to the mobility management entity corresponding to the supporting device, so that the mobility management entity corresponding to the supporting device sends the bearer and context information for the supporting device. Or receiving a response message returned by the supporting device, the RRC connection request message includes a request message, and the response message is included in the RRC connection response message; the response message is that the supporting device sends an RRC connection request message to the base station, and the base station corresponds to the supporting device. Mobility management entity sends initial After sending a message, the supporting device corresponding mobility management entity to establish a bearer for the supporting device and context information. In the embodiment of the present invention, optionally, the RRC message sent by the transmitter 043 includes the global unique temporary user equipment identifier GUTI of the benefit device;

The RRC Connection Request message includes a Temporary Mobile Subscriber Identity S-TMSI supporting the device; the initial message includes a Temporary Mobile Subscriber Identity S-TMSI supporting the device. Therefore, the benefit device provided by the embodiment of the present invention receives the broadcast message sent by the support device through the benefit device, and accesses the support device according to the broadcast message to obtain the IP address allocated by the support device, and the benefit device sends the wireless device to the support device through the IP address. The resource control RRC message is configured to enable the supporting device to send an uplink RRC message to the base station, so that the mobility management entity corresponding to the base station and the benefit device establishes a core network side bearer and context information for the benefit device, and the uplink RR C message includes an RRC message, where the base station is The benefit device and the support device respectively configure the protocol stack on the base station side, and the support device configures the protocol stack on the support device side for the benefit device. After the support device receives the downlink RRC message sent by the base station, the benefit device receives the support device. The RRC connection reconfiguration message is sent, and the downlink RRC message includes an RRC connection reconfiguration message, and the single-link multi-user equipment synthesis communication is successfully established between the benefit device and the supporting device, so that the B-UE can be connected to the eNB without being connected to the eNB. Establish a single link MUCC. The embodiment of the present invention provides a support device 05, as shown in FIG. 23, including: a bus 051, a processor 052, a transmitter 053, a receiver 054, and a memory 055, wherein the memory 055 is used to store instructions, and the transmitter 053 Executing the instruction is used to send a broadcast message to the benefit device, so that the benefit device accesses the support device according to the broadcast message, and obtains an IP address allocated by the support device; the receiver 054 is configured to execute the instruction, and the receiving benefit device sends the IP address through the IP address. The first radio resource control RRC message, the transmitter 053 performs the instruction for sending a second RRC message to the base station, where the second RRC message includes the first RRC message received by the receiver 054, so that the base station and the beneficiary device correspond to mobility management. The entity establishes core network side bearer and context information for the benefit device; the receiver 054 is configured to perform the instruction, and is further configured to receive the first RRC connection reconfiguration message sent by the base station; the processor 052 is configured to execute the instruction, for receiving, according to the receiver The RRC connection reconfiguration message is configured to synthesize a protocol stack that is carried on the supporting device side for the benefit device; the receiver 054 is configured to The instruction is used to receive a third RRC message sent by the base station, where the processor 052 is configured to perform the step of parsing the third RRC message received by the receiver, and acquiring a second RRC connection reconfiguration message sent by the base station to the benefiting device. The transmitter 053 is configured to execute the instruction, where the second RRC connection reconfiguration message acquired by the processor is sent to the benefit device, so that the benefit device establishes a single-link multi-user device synthesis communication with the supporting device. In the embodiment of the present invention, the processor 052 is configured to execute the instruction for accessing the mobility management entity corresponding to the supporting device, so that the mobility management entity corresponding to the supporting device establishes context information and a core for the supporting device. a bearer on the network side; the transmitter 053 is configured to execute the instruction, and send a broadcast message to the beneficiary device, where the broadcast message includes a short-distance communication identifier of the supporting device, so that the benefit device accesses the supporting device according to the short-distance communication identifier; 053 is configured to execute the instruction, and send an allocation message to the beneficiary device, where the allocation message includes an IP address allocated by the supporting device for the beneficiary device. In the embodiment of the present invention, optionally, the processor 052 is configured to execute the instruction for establishing a connection with the base station after the receiver 054 receives the RRC message sent by the benefit device by using the IP address. In the embodiment of the present invention, optionally, the transmitter 053 is configured to execute the instruction, when the supporting device is connected to the base station and is in a connected state, send an uplink RRC message to the base station; or the transmitter 053 is configured to execute the command. In the supporting device and the base station are not connected and are empty In the idle state, the RRC connection request message is sent to the base station, and the base station is triggered to send an initial message to the mobility management entity corresponding to the supporting device, so that the mobility management entity corresponding to the supporting device establishes bearer and context information for the supporting device. In the embodiment of the present invention, optionally, the transmitter 053 executes the instruction to notify the beneficiary device that the supporting device is in the connected state before the receiver receives the RRC message sent by the benefit device by using the IP address. In the embodiment of the present invention, optionally, the transmitter 053 is configured to execute the instruction, when the supporting device is connected to the base station and is in a connected state, the transmitter sends a response message to the benefit device; or is used to support the device and the base station. When there is no connection and is in the idle state, the response message is returned to the benefit device. The response message is that the transmitter sends an RRC connection request message to the base station, and the trigger base station sends an initial message to the mobility management entity corresponding to the supporting device, so that the corresponding device moves. Transmitting, after the processor establishes bearer and context information for the supporting device, or when the processor is not connected to the base station and is in an idle state, the transmitter returns a response message to the benefit device, where the RRC connection The request message includes the request message, and the response message is included in the RRC connection response message; the response message is that the transmitter sends an RRC connection request message to the base station, and the base station reports the The mobility management entity supporting the device sends an initial message to facilitate the corresponding support device Moving '\ is sent after establishing the bearer supporting device and context information ί management entity. In the embodiment of the present invention, optionally, the first RRC message sent by the transmitter 053 includes a globally unique temporary user equipment identifier GUTI of the benefit device;

The RRC Connection Request message includes a Temporary Mobile Subscriber Identity S-TMSI supporting the device; the initial message includes a Temporary Mobile Subscriber Identity S-TMSI supporting the device. Therefore, in the support device provided by the embodiment of the present invention, the supporting device sends a broadcast message to the benefit device, so that the benefit device accesses the support device according to the broadcast message, and obtains an IP address allocated by the support device, and the support device receives the benefit device by using the IP address. The radio resource controls the first RRC message, and then sends a second RRC message to the base station, where the second RRC message includes the first RRC message, so that the base station and the mobility management entity corresponding to the benefit device establish the core network side bearer and context information for the benefit device. After the base station configures the protocol stack on the base station side for the benefit device and the supporting device, the supporting device receives the first RRC connection reconfiguration message sent by the base station, according to the first The RRC connection reconfiguration message is configured to synthesize a protocol stack that is carried on the supporting device side, and the supporting device receives the third RRC message sent by the base station, and the supporting device parses the third RRC message to obtain the second RRC sent by the base station to the benefit device. The reconfiguration message is sent, and the second RRC connection reconfiguration message is sent to the benefit device, so that the benefit device establishes a single-link multi-user device synthesis communication with the supporting device, so that the B-UE can be connected to the eNB without being connected to the eNB. A single link MUCC can be established.

 The embodiment of the present invention provides a base station 06, as shown in FIG. 24, including: a bus 061, a processor 062, a transmitter 063, a receiver 064, and a memory 065, where the memory 065 is used to store instructions, and the receiver 064 performs The command is used to receive a second RRC message sent by the supporting device after the benefiting device sends the first RRC message to the supporting device, where the second RRC message includes a first RRC message; the processor 062 executes the command for receiving according to the receiving The second RRC message is received by the device 064, and the core network side bearer and the context information are established for the benefit device by the mobility management entity corresponding to the benefit device. The processor 062 performs the instruction and is also configured to separately configure the base station side for the supporting device and the benefit device. The transmitter 063 is configured to execute the instruction, and send the first RRC connection reconfiguration message to the supporting device, so that the supporting device configures the protocol stack that is carried on the supporting device side for the benefit device; and the transmitter 063 executes the command. Sending a third RRC message to the supporting device, so that the supporting device sends the third RRC message. Performing a parsing, acquiring a second RRC connection reconfiguration message sent by the base station to the beneficiary device, and sending the second RRC connection reconfiguration message to the benefit device; the processor 062 executing the instruction to establish a single between the beneficiary device and the supporting device Link multi-user equipment synthesizes communications. In the embodiment of the present invention, the processor 062 is configured to: obtain the non-access stratum message of the benefit device from the first RRC message carried by the second RRC message;

The transmitter 063 is configured to send the non-access stratum message to the mobility management entity corresponding to the benefit device, so that the mobility management entity corresponding to the benefit device establishes core network side bearer and context information for the benefit device. In the embodiment of the present invention, the processor 062 is configured to: after the benefit device sends the first RRC message to the supporting device, establish a connection with the supporting device. In the embodiment of the present invention, the receiver 064 is further configured to: when the supporting device is connected to the base station and in the connected state, receive the second RRC message sent by the supporting device; or The RRC connection request message sent by the supporting device is received when the supporting device is not connected to the base station and is in an idle state, and the transmitter 063 is configured to execute the instruction for sending an initial message to the mobility management entity corresponding to the supporting device, so that the initial message is sent to the mobility management entity corresponding to the supporting device. The mobility management entity corresponding to the supporting device establishes context information and bearer for the supporting device. In the embodiment of the present invention, the processor 062 is configured to execute the instruction, and establish a connection with the supporting device before the benefiting device sends the RRC message to the supporting device. In the embodiment of the present invention, optionally, the receiving, by the receiver 064, the instruction is further configured to: when the receiving device sends a request message to the supporting device, when the supporting device is not connected to the base station and is in an idle state, receiving an RRC connection request sent by the supporting device. Message

 The transmitter 063 performs the instruction, and is further configured to send an initial message to the mobility management entity corresponding to the supporting device, so that the mobility management entity corresponding to the supporting device returns a response message to the benefit device after establishing the context information and the bearer for the supporting device. Or, after the receiving device sends a request message to the supporting device, when the supporting device is not connected to the base station and is in an idle state, receiving an RRC connection request message sent by the supporting device, where the RRC connection request message includes a request message; The executing the instruction is further used to send an initial message to the mobility management entity supporting the device, so that the mobility management entity corresponding to the supporting device establishes context information and bearer for the supporting device; and is also used for

 The supporting device returns an RRC connection response message, so that the supporting device returns a response message to the benefit device, and the response message is included in the RRC connection response message. In the embodiment of the present invention, optionally, the first RRC message received by the receiver 064 includes a globally unique temporary user equipment identifier GUTI of the benefit device;

The RRC Connection Request message includes a Temporary Mobile Subscriber Identity S-TMSI supporting the device; the initial message includes a Temporary Mobile Subscriber Identity S-TMSI supporting the device. Therefore, the base station provided by the present invention, after the benefiting device sends the RRC message to the supporting device, the base station receives the second RRC message sent by the supporting device, where the second RRC message includes the first RRC message, and the base station according to the second RRC The message, and the core network side bearer and context information are established for the benefit device by the mobility management entity corresponding to the benefit device, and the base station configures the protocol stack of the base station side for the support device and the benefit device respectively, and sends the first to the support device. The RRC connects the reconfiguration message, so that the supporting device configures the protocol stack that is carried on the supporting device side for the benefit device, and the base station sends a third RRC message to the supporting device, so that the supporting device parses the third RRC message, and obtains the base station to send the benefit. The second RRC connection reconfiguration message of the device is sent to the benefit device, and the base station establishes a single-link multi-user device synthesis communication between the benefit device and the support device, so that the B-UE can be disconnected. On the premise of the eNB, a single-link MUCC can be established.

 In the several embodiments provided herein, it should be understood that the disclosed apparatus and methods may be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored, or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be electrical, mechanical or otherwise. Further, in the devices and systems in the various embodiments of the present invention, each functional unit may be integrated in one processing unit, or each unit may be physically included separately, or two or more units may be integrated in one unit. The above units can be implemented in the form of hardware or in the form of hardware plus software functional units. All or part of the steps of implementing the foregoing method embodiments may be performed by hardware related to the program instructions. The foregoing program may be stored in a computer readable storage medium, and when executed, the program includes the steps of the foregoing method embodiments; The foregoing storage medium includes: a USB flash drive, a removable hard disk, a read only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. medium. The above is only the specific embodiment of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope of the present invention. It should be covered by the scope of the present invention. Therefore, the scope of the invention should be determined by the scope of the claims.

Claims

claims 1. A method for initial signaling of connection, characterized by including: The beneficiary device receives the broadcast message sent by the supporting device, accesses the supporting device according to the broadcast message, and obtains the IP address assigned by the supporting device; The beneficiary device sends a radio resource control RRC message to the supporting device through the IP address, so that the supporting device sends an uplink RRC message to the base station, so that the mobility management entity corresponding to the base station and the beneficiary device is The beneficiary device establishes a core network side bearer and context information, and the uplink RRC message includes the RRC message; The beneficiary device receives the RRC connection reconfiguration message sent by the supporting device. The RRC connection reconfiguration message is received after the supporting device configures and synthesizes a protocol stack carried on the supporting device side for the beneficiary device. The downlink RRC message is sent after the downlink RRC message sent by the base station, and the downlink RRC message includes the RRC connection reconfiguration message, so that the beneficiary device and the supporting device can perform single-link multi-user device composite communication. 2. The method according to claim 1, characterized in that: the beneficiary device receives a broadcast message sent by a supporting device, accesses the supporting device according to the broadcast message, and obtains the IP address allocated by the supporting device, including: : The beneficiary device accesses the mobility management entity corresponding to the support device through the support device; The beneficiary device receives the broadcast message sent by the supporting device, and the broadcast message includes the short-range communication identification of the supporting device; the broadcast message is established by the mobility management entity for the supporting device. Sent after the core network side bearer and context information; The beneficiary device accesses the supporting device according to the short-distance communication identifier; the beneficiary device receives an allocation message sent by the supporting device, and the allocation message includes the IP address allocated by the supporting device to the beneficiary device. . 3. The method according to claim 2, characterized in that, before the beneficiary device sends the RRC message to the supporting device through the IP address, it further includes: The beneficiary device learns that the supporting device is in a connected state; or learns that the supporting device is not connected to the base station and is in an idle state. 4. The method according to claim 3, wherein the beneficiary device learning that the supporting device is in a connected state includes: The beneficiary device sends a request message to the supporting device; When the supporting device is connected to the base station and is in a connected state, the beneficiary device receives Receive the response message returned by the support device; or When the supporting device is not connected to the base station and is in an idle state, the beneficiary device receives a response message returned by the supporting device. The response message is generated when the supporting device sends an RRC connection request to the base station. message, triggering the base station to send an initial message to the mobility management entity corresponding to the supporting device, so that the mobility management entity establishes the bearer and context information for the supporting device and sends it; or the beneficiary device receives the The response message returned by the supporting device, the RRC connection request message includes the request message, the response message is included in the RRC connection response message; the response message is sent by the supporting device to the base station RRC connection request message, the base station sends an initial message to the mobility management entity corresponding to the supporting device, which is sent after the mobility management entity corresponding to the supporting device establishes bearer and context information for the supporting device. 5. The method according to claim 4, wherein the RRC message includes the globally unique temporary user equipment identification GUTI of the beneficiary device; The RRC connection request message includes the temporary mobile subscriber identity code S-TMSI of the supporting device; the initial message includes the temporary mobile subscriber identity code S-TMSI of the supporting device. 6. A method for initial signaling of connection, characterized by including: The supporting device sends a broadcast message to the beneficiary device, so that the beneficiary device accesses the supporting device according to the broadcast message and obtains the IP address assigned by the supporting device; The supporting device receives the radio resource control first RRC message sent by the beneficiary device through the IP address; The supporting device sends a second RRC message to the base station, where the second RRC message includes the first RRC message, so that the mobility management entity corresponding to the base station and the beneficiary device establishes a core network side for the beneficiary device. Bearer and contextual information; The supporting device receives the first RRC connection reconfiguration message sent by the base station, and configures and synthesizes a protocol stack carried on the supporting device side for the beneficiary device according to the first RRC connection reconfiguration message; The support device receives the third RRC message sent by the base station; The supporting device parses the third RRC message, obtains the second RRC connection reconfiguration message sent by the base station to the beneficiary device, and sends the second RRC connection reconfiguration message to the beneficiary device. , enabling the beneficiary device to establish single-link multi-user device composite communication with the supporting device. 7. The method according to claim 6, wherein the supporting device sending a broadcast message to the beneficiary device includes: The support device accesses the mobility management entity corresponding to the support device, so that the mobility management entity corresponding to the support device establishes bearer and context information on the core network side for the support device; The supporting device sends the broadcast message to the beneficiary device, where the broadcast message includes the short-range communication identifier of the supporting device, so that the beneficiary device accesses the supporting device according to the short-range communication identifier; The supporting device sends an allocation message to the beneficiary device, where the allocation message includes the IP address allocated by the supporting device to the beneficiary device. 8. The method according to claim 7, characterized in that, after the supporting device receives the first RRC message sent by the beneficiary device through the IP address, it further includes: The support device establishes a connection with the base station. 9. The method according to claim 8, characterized in that establishing a connection between the support device and the base station includes: When the supporting device is connected to the base station and is in a connected state, the supporting device sends the second RRC message to the base station; or When the support device is not connected to the base station and is in an idle state, the support device sends an RRC connection request message to the base station, triggering the base station to send an initial message to the mobility management entity corresponding to the support device, The mobility management entity corresponding to the supporting device is caused to establish bearer and context information for the supporting device. 10. The method according to claim 7, characterized in that, before the supporting device receives the first RRC message sent by the beneficiary device through the IP address, it further includes: The supporting device notifies the beneficiary device that the supporting device is in a connected state. 11. The method according to claim 10, wherein the supporting device notifying the beneficiary device that the supporting device is in a connected state includes: The supporting device receives the request message sent by the beneficiary device; When the supporting device is connected to the base station and is in a connected state, the supporting device returns a response message to the beneficiary device; or When the supporting device is not connected to the base station and is in an idle state, the supporting device returns a response message to the beneficiary device. The response message is when the supporting device sends an RRC connection request message to the base station, Triggering the corresponding movement of the base station to the supporting equipment The mobility management entity sends an initial message, so that the mobility management entity corresponding to the supporting device establishes bearers and context information for the supporting device; or, the supporting device returns a response message to the beneficiary device, and the RRC The connection request message includes the request message, and the response message is included in the RRC connection response message; the response message is when the support device sends the RRC connection request message to the base station, and the base station sends the RRC connection request message to the base station. The mobility management entity corresponding to the support device sends an initial message, which is sent after the mobility management entity corresponding to the support device establishes bearer and context information for the support device. 12. The method according to claim 9 or 11, characterized in that the RRC message includes the globally unique temporary user equipment identification GUTI of the beneficiary device; The RRC connection request message includes the temporary mobile subscriber identity code S-TMSI of the supporting device; the initial message includes the temporary mobile subscriber identity code S-TMSI of the supporting device. 13. A method for initial signaling of connection, characterized by including: After the beneficiary device sends the first radio resource control RRC message to the supporting device, the base station receives the second RRC message sent by the supporting device, where the second RRC message includes the first RRC message; The base station establishes the core network side bearer and context information for the beneficiary device according to the second RRC message and through the mobility management entity corresponding to the beneficiary device; The base station configures a protocol stack on the base station side for the supporting device and the beneficiary device respectively; The base station sends a first RRC connection reconfiguration message to the supporting device, so that the supporting device configures and synthesizes a protocol stack carried on the supporting device side for the beneficiary device; The base station sends a third RRC message to the supporting device, so that the supporting device parses the third RRC message, obtains the second RRC connection reconfiguration message sent by the base station to the beneficiary device, and Send the second RRC connection reconfiguration message to the beneficiary device; The base station establishes single-link multi-user equipment composite communication between the beneficiary equipment and the supporting equipment. 14. The method according to claim 13, characterized in that, the base station establishes a core network side bearer and context for the beneficiary device according to the second RRC message and through the mobility management entity corresponding to the beneficiary device. Information includes: The base station obtains the first RRC message carried in the second RRC message. The base station sends the non-access layer message to the mobility management entity corresponding to the beneficiary device, so that the mobility management entity corresponding to the beneficiary device establishes core network side bearer and context information for the beneficiary device. . 15. The method according to claim 14, characterized in that, after the beneficiary device sends the first RRC message to the supporting device, it further includes: The base station establishes a connection with the supporting device. 16. The method according to claim 15, wherein the base station establishing a connection for the support device includes: When the supporting device is connected to the base station and is in the connected state, the base station receives the second RRC message sent by the supporting device; or When the supporting device is not connected to the base station and is in an idle state, the base station receives the RRC connection request message sent by the supporting device, and sends an initial message to the mobility management entity corresponding to the supporting device, so that the The mobility management entity corresponding to the supporting device establishes bearer and context information for the supporting device. 17. The method according to claim 14, characterized in that, before the beneficiary device sends the RRC message to the supporting device, it further includes: The base station establishes a connection with the supporting device. 18. The method according to claim 17, wherein establishing a connection between the base station and the support device includes: When the beneficiary device sends a request message to the supporting device, and the supporting device has no connection with the base station and is in an idle state, the base station receives the RRC connection request message sent by the supporting device; The base station sends an initial message to the mobility management entity corresponding to the supporting device, so that after the mobility management entity corresponding to the supporting device establishes bearer and context information for the supporting device, the supporting device sends the benefit to the supporting device. The device returns a response message; or When the beneficiary device sends a request message to the supporting device, and the supporting device has no connection with the base station and is in an idle state, the base station receives the RRC connection request message sent by the supporting device, and the RRC connection request The message includes the request message; The base station sends an initial message to the mobility management entity of the supporting device, so that the mobility management entity corresponding to the supporting device establishes bearer and context information for the supporting device; The base station returns an RRC connection response message to the supporting device, so that the supporting device returns a response message to the beneficiary device, and the response message is included in the RRC connection response message. 19. The method according to claim 16 or 18, characterized in that the RRC message includes the globally unique temporary user equipment identification GUTI of the beneficiary device; The RRC connection request message includes the temporary mobile subscriber identity code S-TMSI of the supporting device; the initial message includes the temporary mobile subscriber identity code S-TMSI of the supporting device. 20. A benefit device, characterized by including: A receiving unit, used to receive broadcast messages sent by the supporting device; An access unit, configured to access the support device according to the broadcast message received by the receiving unit; An acquisition unit, configured to acquire the IP address allocated by the support device after the access unit is connected; A sending unit, configured to send a radio resource control RRC message to the supporting device through the IP address obtained by the acquiring unit, so that the supporting device sends an uplink RRC message to the base station, so that the base station and the beneficiary device correspond to each other. The mobility management entity establishes core network side bearers and context information for the beneficiary device, and the uplink RRC message includes the RRC message; The receiving unit is configured to receive an RRC connection reconfiguration message sent by the supporting device. The RRC connection reconfiguration message is generated after the supporting device configures and synthesizes a protocol stack carried on the supporting device side for the beneficiary device. and is sent after receiving the downlink RRC message sent by the base station, where the downlink RRC message includes the RRC connection reconfiguration message, A communication unit, used for performing single-link multi-user equipment composite communication with the support equipment. 21. The benefit device according to claim 20, characterized in that, The access unit is also used to access the mobility management entity corresponding to the support device through the support device; The receiving unit is specifically configured to: receive a broadcast message of the supporting device, where the broadcast message includes a short-distance communication identifier of the supporting device; the broadcast message packet of the supporting device is the mobility management entity. Sent after the supporting device establishes the core network side bearer and context information; The access unit is specifically configured to: access the support device according to the short-distance communication identifier. The equipment is configured to cause the supporting device to send an allocation message to the beneficiary device, where the allocation message includes the IP address allocated by the supporting device to the beneficiary device; The receiving unit is specifically configured to: receive an allocation message sent by the support device, where the allocation message includes the IP address allocated by the support device to the beneficiary device. 22. The beneficiary device according to claim 21, characterized in that the beneficiary device further includes: before the RRC message, learning that the supporting device is connected to the base station and in a connected state; or learning that the supporting device is connected to the base station and in a connected state; or learning that the supporting device is connected to the base station and is in a connected state; There is no connection with the base station and it is in idle state. 23. The benefit device according to claim 22, characterized in that the learning unit includes: A sending subunit, used to send a request message to the support device; A receiving subunit, configured to receive a response message returned by the supporting device when the learning unit learns that the supporting device is connected to the base station and is in a connected state; or used to learn that the supporting device is known by the learning unit. When there is no connection with the base station and is in an idle state, receive a response message returned by the support device. The response message is when the support device sends an RRC connection request message to the base station, triggering the base station to send a request to the base station. The mobility management entity corresponding to the support device sends an initial message, so that the mobility management entity corresponding to the support device sends the bearer and context information for the support device; or receives a response message returned by the support device, The RRC connection request message includes the request message, and the response message is included in the RRC connection response message; the response message is when the support device sends the RRC connection request message to the base station, and the base station sends the RRC connection request message to the base station. The mobility management entity corresponding to the support device sends an initial message, which is sent after the mobility management entity corresponding to the support device establishes bearer and context information for the support device. 24. The beneficiary device according to claim 23, wherein the RRC message sent by the sending unit includes the globally unique temporary user equipment identity GUTI of the beneficiary device; The RRC connection request message received by the receiving subunit includes the temporary mobile subscriber identity code S-TMSI of the support device, and the initial message includes the temporary mobile subscriber identity code S-TMSI of the support device. 25. A support equipment, characterized by including: A sending unit, configured to send a broadcast message to the beneficiary device, so that the beneficiary device can The broadcast message accesses the supporting device and obtains the IP address assigned by the supporting device; a receiving unit configured to receive the first radio resource control RRC message sent by the beneficiary device through the IP address; The sending unit is configured to send a second RRC message to the base station, where the second RRC message includes the first RRC message received by the receiving unit, so that the mobility management entity corresponding to the base station and the beneficiary device is the The beneficiary device establishes the core network side bearer and context information; the receiving unit is used to receive the first RRC connection reconfiguration message sent by the base station; the configuration unit is used to receive the RRC connection reconfiguration message according to the receiving unit Configure and synthesize a protocol stack carried on the supporting device side for the beneficiary device; The receiving unit is configured to receive the third RRC message sent by the base station; A processing unit, configured to parse the third RRC message received by the receiving unit and obtain the second RRC connection reconfiguration message sent by the base station to the beneficiary device; The sending unit is configured to send the second RRC connection reconfiguration message obtained by the processing unit to the beneficiary device, so that the beneficiary device establishes single-link multi-user equipment synthetic communication with the support device. . 26. The support equipment according to claim 25, characterized in that, An access unit, configured to access the mobility management entity corresponding to the support device, so that the mobility management entity corresponding to the support device establishes core network side bearers and context information for the support device; The sending unit is specifically configured to: send the broadcast message to the beneficiary device, where the broadcast message includes the short-range communication identifier of the supporting device, so that the beneficiary device can access all the communication devices based on the short-range communication identifier. The above support equipment; The sending unit is further specifically configured to: send an allocation message to the beneficiary device, where the allocation message includes the IP address allocated by the support device to the beneficiary device. 27. The supporting equipment according to claim 26, characterized in that, the supporting equipment further includes: An establishing unit, configured to establish a connection with the base station after the receiving unit receives the first RRC message sent by the beneficiary device through the IP address. 28. The support equipment according to claim 27, characterized in that the establishment unit includes: A first sending subunit, configured to send the second RRC message to the base station when the support device is connected to the base station and is in a connected state; or The first sending subunit is configured to send an RRC connection request message to the base station when the support device is not connected to the base station and is in an idle state, to trigger the corresponding mobility of the base station to the support device. The management entity sends an initial message, so that the mobility management entity corresponding to the support device establishes bearer and context information for the support device. 29. The supporting equipment according to claim 26, characterized in that, the supporting equipment further includes: A notification unit, configured to notify the beneficiary device that the supporting device is in a connected state before the receiving subunit receives the first RRC message sent by the beneficiary device through the IP address. 30. The support equipment according to claim 26, characterized in that the notification unit includes: The second receiving subunit is used to receive the request message sent by the beneficiary device; The second sending subunit is configured to return a response message to the beneficiary device when the supporting device is connected to the base station and is in the connected state; or The second sending subunit is configured to return a response message to the beneficiary device when the supporting device is connected to the base station and is in an idle state. The response message is sent by the sending subunit to the base station. Send an RRC connection request message to trigger the base station to send an initial message to the mobility management entity corresponding to the support device, so that the mobility management entity corresponding to the support device establishes bearer and context information for the support device and sends it after; Or when the supporting device has no connection with the base station and is in an idle state, a response message is returned to the beneficiary device, where the RRC connection request message includes the request message, and the response message is included in the RRC connection In the response message: The response message is when the support device sends an RRC connection request message to the base station, and the base station sends an initial message to the mobility management entity corresponding to the support device, and the mobility management entity corresponding to the support device Sent after the property management entity establishes bearer and context information for the supporting device. 31. The support device according to claim 28 or 30, characterized in that the RRC message includes the globally unique temporary user equipment identification GUTI of the beneficiary device; The RRC connection request message includes the temporary mobile subscriber identity code S-TMSI of the support device; the initial message includes the temporary mobile subscriber identity code S-TMSL of the support device. 32. A base station, characterized by including: A receiving unit, configured to receive a second RRC message sent by the supporting device after the beneficiary device sends the first radio resource control RRC message to the supporting device, where the second RRC message includes The first RRC message; An establishment unit, configured to establish core network side bearers and context information for the beneficiary device according to the second RRC message received by the receiving unit through the mobility management entity corresponding to the beneficiary device; A configuration unit configured to respectively configure the protocol stack on the base station side for the supporting equipment and the beneficiary equipment; A sending unit, configured to send a first RRC connection reconfiguration message to the supporting device, so that the supporting device configures and synthesizes a protocol stack carried on the supporting device side for the beneficiary device; The sending unit is also configured to send a third RRC message to the supporting device, so that the supporting device parses the third RRC message and obtains the second RRC connection sent by the base station to the beneficiary device. reconfiguration message, and send the second RRC connection reconfiguration message to the beneficiary device; The establishment unit is configured to establish single-link multi-user equipment synthetic communication between the beneficiary equipment and the supporting equipment. 33. The base station according to claim 32, characterized in that the establishment unit is specifically used for: Obtain the non-access stratum message of the beneficiary device from the first RRC message carried in the second RRC message; The non-access layer message is sent to the mobility management entity corresponding to the beneficiary device, so that the mobility management entity corresponding to the beneficiary device establishes the core network side bearer and context information for the beneficiary device. 34. The base station according to claim 33, characterized in that, The establishing unit is also configured to: establish a connection with the supporting device after the beneficiary device sends the first RRC message to the supporting device. 35. The base station according to claim 34, characterized in that the establishment unit includes: a receiving subunit, configured to receive the data sent by the supporting device when the supporting device is connected to the base station and is in a connected state. second RRC message; or The receiving subunit is configured to receive an RRC connection request message sent by the supporting device when the supporting device has no connection with the base station and is in an idle state; The sending subunit is configured to send an initial message to the mobility management entity corresponding to the supporting device, so that the mobility management entity corresponding to the supporting device establishes bearer and context information for the supporting device. 36. The base station according to claim 33, characterized in that, The establishing unit is also configured to establish a connection with the supporting device before the beneficiary device sends the RRC message to the supporting device. 37. The base station according to claim 36, characterized in that the establishment unit specifically includes: Receiving subunit one, configured to receive the RRC connection request message sent by the supporting device when the beneficiary device sends a request message to the supporting device, and when the supporting device has no connection with the base station and is in an idle state; Sending subunit one is used to send an initial message to the mobility management entity corresponding to the supporting device, so that after the mobility management entity corresponding to the supporting device establishes bearer and context information for the supporting device, the supporting device Return a response message to the beneficiary device; or The receiving subunit one is configured to receive the RRC connection request message sent by the supporting device when the beneficiary device sends a request message to the supporting device and the supporting device has no connection with the base station and is in an idle state. , the RRC connection request message includes the request message; The sending subunit one is used to send an initial message to the mobility management entity of the support device, so that the mobility management entity corresponding to the support device establishes bearer and context information for the support device; and is used to send the support device to the mobility management entity of the support device. The supporting device returns an RRC connection response message, so that the supporting device returns a response message to the beneficiary device, and the response message is included in the RRC connection response message. 38. The base station according to claim 35 or 37, characterized in that the first RRC message received by the receiving unit includes the globally unique temporary user equipment identification GUTI of the beneficiary device; The RRC connection request message includes the temporary mobile subscriber identity code S-TMSI of the supporting device; the initial message includes the temporary mobile subscriber identity code S-TMSI of the supporting device. 39. A benefit device, characterized by including: Receiver, used to receive broadcast messages sent by supporting devices; A processor, configured to access the support device according to the broadcast message received by the receiver, and obtain the IP address assigned by the support device; A transmitter, configured to send wireless signals to the support device through the IP address obtained by the processor. Resource control RRC message, so that the supporting device sends an uplink RRC message to the base station, so that the mobility management entity corresponding to the base station and the beneficiary device establishes the core network side bearer and context information for the beneficiary device, the uplink The RRC message includes the RRC message; The receiver receives the RRC connection reconfiguration message sent by the supporting device. The RRC connection reconfiguration message is received after the supporting device configures and synthesizes a protocol stack carried on the supporting device side for the beneficiary device. Sent after the downlink RRC message sent by the base station, the downlink RRC message includes the RRC connection reconfiguration message; The processor is configured to perform single-link multi-user equipment synthetic communication with the support device after the receiver receives the RRC connection reconfiguration message. 40. The benefit device according to claim 39, wherein the processor is further configured to access the mobility management entity corresponding to the support device through the support device; The receiver is specifically configured to: receive a broadcast message from the support device, where the broadcast message includes a short-distance communication identifier of the support device; a broadcast message from the support device; and the information indicates that the mobility management entity is the Sent after the above support equipment establishes the core network side bearer and context information; The processor is specifically configured to: access the support device according to the short-range communication identification, so that the support device sends an allocation message to the beneficiary device, where the allocation message includes that the support device is the beneficiary device. assigned IP address; The receiver is specifically configured to: receive an allocation message sent by the supporting device, where the allocation message includes the IP address allocated by the supporting device to the beneficiary device. 41. The beneficiary device according to claim 40, wherein the processor is further configured to: before, learn that the support device is in a connected state; or learn that the support device is not connected to the base station and is idle. state. 42. The benefit device according to claim 41, characterized in that, The transmitter is specifically configured to send a request message to the support device; The receiver is specifically configured to, when the processor learns that the support device is connected to the base station and is in a connected state, receive a response message returned by the support device; or The receiver is specifically configured to: when the processor learns that the support device has no connection with the base station and is in an idle state, the receiver receives a response message returned by the support device, and the response message is in The support device sends an RRC connection request message to the base station. information, triggering the base station to send an initial message to the mobility management entity corresponding to the supporting device, so that the mobility management entity corresponding to the supporting device establishes the bearer and context information for the supporting device and sends it; or receiving the The response message returned by the supporting device, the RRC connection request message includes the request message, the response message is included in the RRC connection response message; the response message is sent by the supporting device to the base station RR C connection request message, the base station sends an initial message to the mobility management entity corresponding to the supporting device, and sends the message after the mobility management entity corresponding to the supporting device establishes bearer and context information for the supporting device. 43. The beneficiary device according to claim 42, wherein the RRC message sent by the transmitter includes the globally unique temporary user equipment identity GUTI of the beneficiary device; the RRC connection request message includes the GUTI of the supporting device. Temporary Mobile Subscriber Identity S-TMSI; The initial message includes the Temporary Mobile Subscriber Identity S-TMSI of the support device. 44. A support equipment, characterized by including: A transmitter, configured to send a broadcast message to the beneficiary device, so that the beneficiary device accesses the supporting device according to the broadcast message and obtains the IP address assigned by the supporting device; A receiver configured to receive a first radio resource control RRC message sent by the beneficiary device through the IP address; The transmitter is configured to send a second RRC message to the base station, where the second RRC message includes the first RRC message received by the receiver, so that the mobility management entity corresponding to the base station and the beneficiary device is the The above-mentioned beneficiary equipment establishes core network side bearer and context information; The receiver is configured to receive the first RRC connection reconfiguration message sent by the base station; the processor is configured to configure the synthesized bearer for the beneficiary device based on the RRC connection reconfiguration message received by the receiver. Support the protocol stack on the device side; The receiver is configured to receive the third RRC message sent by the base station; The processor is configured to parse the third RRC message received by the receiver and obtain the second RRC connection reconfiguration message sent by the base station to the beneficiary device; The transmitter is configured to send the second RRC connection reconfiguration message obtained by the processor to the beneficiary device, so that the beneficiary device establishes single-link multi-user equipment synthetic communication with the support device. . 45. The support device according to claim 44, wherein the processor is configured to access the mobility management entity corresponding to the support device, so that the support device corresponding The mobility management entity establishes bearers and context information on the core network side for the supporting device; the transmitter is specifically configured to send the broadcast message to the beneficiary device, where the broadcast message includes the short-range distance of the supporting device. Communication identification to facilitate the beneficiary device to access the supporting device according to the short-distance communication identification; The transmitter is specifically configured to send an allocation message to the beneficiary device, where the allocation message includes the IP address allocated by the support device to the beneficiary device. 46. The support device according to claim 45, further comprising: the processor, configured to communicate with the receiver after the receiver receives the RRC message sent by the beneficiary device through the IP address. The base station establishes a connection. 47. The support equipment according to claim 46, characterized in that, The transmitter is configured to send the uplink RRC message to the base station when the support device is connected to the base station and is in a connected state; or The transmitter is configured to send an RRC connection request message to the base station when the supporting device has no connection with the base station and is in an idle state, and triggers the base station to send a request message to the mobility management entity corresponding to the supporting device. The initial message enables the mobile management entity corresponding to the support device to establish bearer and context information for the support device. 48. The support device according to claim 45, further comprising: the transmitter, configured to send the RRC message to the beneficiary device before the receiver receives the RRC message sent by the beneficiary device through the IP address. The beneficiary device notifies the supporting device that it is in a connected state. 49. The support device according to claim 48, characterized in that: the transmitter is configured to send a response to the beneficiary device when the support device is connected to the base station and is in a connected state. message; or Used to return a response message to the beneficiary device when the supporting device has no connection with the base station and is in an idle state. The response message is triggered when the transmitter sends an RRC connection request message to the base station. The base station sends an initial message to the mobility management entity corresponding to the supporting device, so that the mobility management entity corresponding to the supporting device establishes bearer and context information for the supporting device; or For when the processor is not connected to the base station and is in an idle state, the transmitter returns a response message to the beneficiary device, where the RRC connection request message includes the request message, and the response message includes In the RRC connection response message; the response message is when the transmitter sends an RRC connection request message to the base station, and the base station sends an initial message to the mobility management entity of the supporting device, so that the The corresponding movement of the support equipment mentioned above Sent after the mobility management entity establishes bearer and context information for the supporting device. 50. The support device according to claims 47 to 49, characterized in that the first RRC message sent by the transmitter includes the globally unique temporary user equipment identification GUTI of the beneficiary device; The RRC connection request message includes the temporary mobile subscriber identity code S-TMSI of the supporting device; the initial message includes the temporary mobile subscriber identity code S-TMSI of the supporting device. 51. A base station, characterized by including: A receiver, configured to receive a second RRC message sent by the supporting device after the beneficiary device sends the first radio resource control RRC message to the supporting device, where the second RRC message includes the first RRC message; A processor, configured to establish the core network side bearer and context information for the beneficiary device through the mobility management entity corresponding to the beneficiary device according to the second RRC message received by the receiver; The processor is configured to respectively configure a protocol stack on the base station side for the supporting device and the beneficiary device; A transmitter configured to send a first RRC connection reconfiguration message to the supporting device, so that the supporting device configures and synthesizes a protocol stack carried on the supporting device side for the beneficiary device; The transmitter is configured to send a third RRC message to the supporting device, so that the supporting device parses the third RRC message and obtains the second RRC connection reconnection sent by the base station to the beneficiary device. configuration message, and send the second RRC connection reconfiguration message to the beneficiary device; The processor is configured to establish single-link multi-user equipment synthetic communication between the beneficiary device and the supporting device. 52. The base station according to claim 51, wherein the processor is specifically configured to obtain the non-access stratum message of the beneficiary device from the first RRC message carried in the second RRC message. ; The transmitter is specifically configured to send the non-access layer message to the mobility management entity corresponding to the beneficiary device, so that the mobility management entity corresponding to the beneficiary device establishes a core network side for the beneficiary device. Bearer and contextual information. 53. The base station according to claim 52, wherein the processor is further configured to: after the beneficiary device sends the first RRC message to the supporting device, communicate with the Establish a connection with the above support equipment. 54. The base station according to claim 53, characterized in that, The receiver is also configured to receive the second RRC message sent by the supporting device when the supporting device is connected to the base station and is in a connected state; or, is also configured to receive a second RRC message sent by the supporting device when the supporting device is connected to the base station. When there is no connection and is in an idle state, the RRC connection request message sent by the supporting device is received, and the transmitter sends an initial message to the mobility management entity corresponding to the supporting device, so that the mobility management entity corresponding to the supporting device Establish bearer and context information for the support device. 55. The base station according to claim 52, characterized in that, The processor is further configured to establish a connection with the supporting device before the beneficiary device sends the RRC message to the supporting device. 56. The base station according to claim 55, characterized in that, The receiver is also configured to receive an RRC connection request message sent by the supporting device when the beneficiary device sends a request message to the supporting device, and when the supporting device has no connection with the base station and is in an idle state; The transmitter is also configured to send an initial message to the mobility management entity corresponding to the supporting device, so that after the mobility management entity corresponding to the supporting device establishes bearer and context information for the supporting device, the supporting device The device returns a response message to the beneficiary device; or is further configured to receive a request message sent by the supporting device when the beneficiary device sends a request message to the supporting device and the supporting device is not connected to the base station and is in an idle state. The RRC connection request message includes the request message; The transmitter is also used to send an initial message to the mobility management entity of the support device, so that the mobility management entity corresponding to the support device establishes bearer and context information for the support device; and is also used to send the support device to the mobility management entity of the support device. The supporting device returns an RRC connection response message, so that the supporting device returns a response message to the beneficiary device, and the response message is included in the RRC connection response message. 57. The base station according to claims 54 to 56, characterized in that the first RRC message received by the receiver includes the globally unique temporary user equipment identity GUTI of the beneficiary device; The RRC connection request message includes the temporary mobile subscriber identity code S-TMSI of the supporting device; the initial message includes the temporary mobile subscriber identity code S-TMSI of the supporting device.