Relay communication method, device and system

Abstract

The present application discloses a relay communication method, device, and system, which belongs to the field of communication technology. The method includes: a relay terminal receives a first message sent by an access network device, the first message including configuration information of a first bearer; the relay terminal configures an adaptation layer logical entity for the first bearer according to the first message, the first bearer being a bearer between the relay terminal and the access network device, and the adaptation layer logical entity being used to distinguish data between the relay terminal and a remote terminal, or data from different remote terminals. The present application instructs the relay terminal to configure an adaptation layer logical entity for the first bearer through a first message, thereby supporting the configuration of a relay bearer for a relay terminal that adopts an L2 relay protocol stack.

Description

[0001] This application is a divisional application of the invention patent application with application date of March 31, 2017, application number 201780085180.X, and invention name “Relay Communication Method, Device and System”. Technical Field

[0002] The present application relates to the field of communication technology, and in particular to a relay communication method, device and system. Background Art

[0003] With the emergence and continuous improvement of smart watches, smart bracelets, and smart glasses, wearable devices have become increasingly popular and favored. Applications based on wearable devices and communication technologies for wearable devices have also become a research hotspot in the global communications industry.

[0004] In a typical wearable device application scenario, wearable devices typically establish a wireless connection and communicate with cellular networks (such as Long Term Evolution (LTE) networks) through a relay terminal (such as a smartphone). This allows users to directly transmit data for various services to the network through various applications (apps) on the wearable device. This communication method of wearable devices, which uses relay terminals to relay data, is also known as user equipment (UE)-to-network relay (UE-to-Network Relay) transmission.

[0005] To implement the relay function of a relay terminal, a layer 2 relay function is added to the communication protocol stack architecture of the relay terminal. This layer 2 relay function is located above the Radio Link Control (RLC) layer (excluding the RLC layer) and below the Internet Protocol (IP) layer or the Radio Resource Control (RRC) layer (excluding the IP and RRC layers). However, the current communication protocol stack architecture between terminals and access network devices does not include this relay function. Therefore, the access network device cannot configure the relay function of the relay terminal, and therefore does not support the configuration of relay bearer for relay terminals that use this relay function. Summary of the Invention

[0006] In order to solve the problem that the prior art does not support the configuration of relay bearer for a relay terminal using the relay function, embodiments of the present invention provide a relay communication method, apparatus, and system.

[0007] In a first aspect, an embodiment of the present invention provides a relay communication method, the method comprising: a relay terminal receives a first message sent by an access network device, the first message including configuration information of a first bearer; the relay terminal configures an adaptation layer logical entity for the first bearer according to the first message, the first bearer being a bearer between the relay terminal and the access network device, and the adaptation layer logical entity being used to distinguish data between the relay terminal and a remote terminal, or data from different remote terminals.

[0008] In a possible implementation, the configuration information of the first bearer includes a first bearer identifier and adaptation function configuration information. The adaptation function configuration information includes an identifier of the remote terminal and / or a bearer identifier of the remote terminal.

[0009] Furthermore, the relay terminal configures an adaptation layer logical entity for the first bearer according to the first message, which may include the following situations:

[0010] The first method is that the relay terminal does not establish the first bearer and creates a new first bearer according to the first message. In this case, if the first bearer does not exist in the existing bearers of the relay terminal, the relay terminal establishes the first bearer and establishes an adaptation layer logical entity for the first bearer according to the adaptation function configuration information.

[0011] Second, the relay terminal has established a first bearer, and configures the adaptation layer logical entity of the first bearer according to the adaptation function configuration information. The configuration here may include establishing an adaptation layer logical entity for the first bearer; or reconfiguring the adaptation layer logical entity of the first bearer; or releasing the adaptation layer logical entity of the first bearer.

[0012] In another possible implementation, the configuration information of the first bearer includes a first bearer identifier and bearer release indication information. The relay terminal configuring an adaptation layer logical entity for the first bearer based on the first message means that the relay terminal has established the first bearer and releases the first bearer based on the first message. Specifically, releasing the first bearer includes releasing resources of the first bearer, where the resources of the first bearer include the adaptation layer logical entity.

[0013] In another possible implementation, the configuration information of the first bearer includes a first bearer identifier and a bearer type, where the bearer type is a relay bearer or a normal bearer. The relay bearer is used to transmit data of a remote terminal or for transmitting data of a remote terminal and a relay terminal, and the normal bearer is used to transmit data of the relay terminal.

[0014] Furthermore, the relay terminal configures an adaptation layer logical entity for the first bearer according to the first message, which may include the following situations:

[0015] In the first method, if the relay terminal has not established the first bearer and the bearer type in the first message is a relay bearer, a new first bearer is created according to the first message. In this case, if the first bearer does not exist in the existing bearers of the relay terminal, the relay terminal establishes the first bearer and establishes an adaptation layer logical entity for the first bearer.

[0016] The second method is that the relay terminal has established a first bearer, and an adaptation layer logical entity of the first bearer is configured according to the bearer type. Specifically, when the first bearer among the existing bearers is a normal bearer and the bearer type is an inherit bearer, the adaptation layer logical entity is established for the first bearer, thereby changing the normal bearer to an inherit bearer; or when the first bearer among the existing bearers is an inherit bearer and the bearer type is a normal bearer, the adaptation layer logical entity of the first bearer is released, thereby changing the inherit bearer to a normal bearer.

[0017] In second aspect, an embodiment of the present invention provides a relay communication method, the method comprising: an access network device determines configuration information of a first bearer, where the first bearer is a bearer between the access network device and a relay terminal; the access network device sends a first message to the relay terminal, where the first message includes configuration information of the first bearer, and the configuration information of the first bearer is used to instruct the relay terminal to configure an adaptation layer logical entity for the first bearer, where the adaptation layer logical entity is used to distinguish data between the relay terminal and a remote terminal, or data from different remote terminals.

[0018] In the aforementioned first and second aspects, the access network device instructs the relay terminal through a first message to configure an adaptation layer logical entity for the first bearer, thereby supporting the configuration of the relay bearer of the relay terminal using the L2 relay protocol stack. There are multiple types of L2 relay protocol stacks, and the protocol stacks with relay functions above the RLC layer (excluding the RLC layer), the IP layer or below the RRC layer (excluding the IP layer and the RRC layer) all belong to the L2 relay protocol stack. Configuring the adaptation layer logical entity for the first bearer here includes establishing, modifying or releasing the adaptation layer logical entity. The adaptation layer logical entity is specifically used to distinguish whether the data is from / to the remote terminal or the relay terminal, or to distinguish which bearer the data belongs to of the remote terminal, or to distinguish whether the data is from / to different remote terminals.

[0019] In the aforementioned first and second aspects, the first message may be an RRC connection reconfiguration message, an RRC connection establishment message, or other authorization message sent by the access network device to the relay terminal.

[0020] In the first and second aspects, the adaptation layer logical entity may be an adaptation protocol entity or an adaptation function of a PDCP protocol entity. When the adaptation layer logical entity is an adaptation protocol entity, the adaptation function configuration information further includes an on or off indication, the on or off indication being used to instruct the relay terminal to turn on or off the adaptation function of the PDCP protocol entity.

[0021] In a third aspect, an embodiment of the present invention provides a relay communication method, generating a MAC PDU, wherein the MAC PDU includes a MAC CE, the MAC CE includes an identifier of a remote terminal, and the MAC PDU carries the signaling bearer SRB0 data of the remote terminal; and sending the MAC PDU.

[0022] The relay communication method of the third aspect can be executed by an access network device or a remote terminal. When executed by an access network device, the SRB0 data can be an RRC connection establishment message, and when executed by a remote terminal, the SRB0 data can be an RRC connection establishment request.

[0023] In a fourth aspect, an embodiment of the present invention provides a relay communication method, which includes: receiving a MAC PDU, wherein the MAC PDU includes a media access control protocol control element MAC CE, wherein the MAC CE includes an identifier of a remote terminal, and wherein the MAC PDU carries the signaling bearer SRB0 data of the remote terminal; obtaining the identifier of the remote terminal from the MAC CE of the MAC PDU; and sending the MAC PDU.

[0024] In the third and fourth aspects, the remote terminal identifier is a local identifier of the remote terminal, which is an identifier used between the access network device and the relay terminal to identify the remote terminal. During implementation, it can be allocated by the access network device or the relay terminal.

[0025] In a fifth aspect, an embodiment of the present invention provides a relay communication device, which includes a unit for implementing the method described in the first aspect, such as a receiving unit and a configuration unit.

[0026] In a sixth aspect, an embodiment of the present invention provides a relay communication device, which includes a unit for implementing the method described in the second aspect, such as a generating unit and a sending unit.

[0027] In a seventh aspect, an embodiment of the present invention provides a relay communication device, which includes a unit for implementing the method described in the third aspect, such as a generating unit and a sending unit.

[0028] In an eighth aspect, an embodiment of the present invention provides a relay communication device, which includes units for implementing the method described in the fourth aspect, such as a receiving unit, an acquiring unit, and a sending unit.

[0029] In the ninth aspect, an embodiment of the present invention also provides a relay communication device for a relay terminal, the device comprising: a memory, a processor connected to the memory, the memory being used to store software programs and modules, and when the processor is used to run or execute the software programs and modules stored in the memory, the method described in the first aspect or the fourth aspect can be executed.

[0030] In the tenth aspect, an embodiment of the present invention also provides a relay communication device for access network equipment, the device comprising: a memory, a processor connected to the memory, the memory being used to store software programs and modules, and when the processor is used to run or execute the software programs and modules stored in the memory, the method described in the second aspect or the third aspect can be executed.

[0031] In the eleventh aspect, an embodiment of the present invention further provides a computer-readable medium for storing program code for execution by a terminal, wherein the program code includes instructions for executing the method described in the first aspect or the fourth aspect.

[0032] In a twelfth aspect, an embodiment of the present invention further provides a computer-readable medium for storing program code for execution by an access network device, wherein the program code includes instructions for executing the method described in the second aspect or the third aspect.

[0033] In the thirteenth aspect, an embodiment of the present invention further provides a communication chip, which is used in a mobile communication system device, and the communication chip includes: a processor, a memory, and a communication interface; the processor, the memory, and the communication interface are coupled through a bus, and the memory is used to store program instructions. The processor executes the program instructions stored in the memory so that the communication system device equipped with the communication chip can execute the method provided in any possible implementation method of the first, second, third, or fourth aspects mentioned above.

[0034] In a fourteenth aspect, an embodiment of the present invention further provides a relay communication system, comprising an access network device, a relay terminal, and a remote terminal, wherein the access network device comprises the relay communication apparatus provided in the sixth aspect, and the relay terminal comprises the relay communication apparatus provided in the fifth aspect. Alternatively, the access network device comprises the relay communication apparatus provided in the ninth aspect, and the relay terminal comprises the relay communication apparatus provided in the tenth aspect.

[0035] In the fifteenth aspect, an embodiment of the present invention further provides a relay communication system, which includes an access network device, a relay terminal and a remote terminal, the access network device and the remote terminal include the relay communication device provided in the seventh aspect, and the relay terminal includes the relay communication device provided in the eighth aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 1 is a schematic diagram of the architecture of a relay communication system provided by an embodiment of the present invention;

[0037] Figure 2a It is a schematic diagram of the wireless protocol stack used when the terminal communicates with the access network equipment;

[0038] Figure 2b This is a schematic diagram of the wireless protocol stack used when a remote terminal communicates with an access network device through a relay terminal;

[0039] Figure 3a It is a flowchart of the existing bearer establishment process between the terminal and the access network equipment;

[0040] Figure 3b It is a flow chart of the bearer modification process between the existing terminal and the access network equipment;

[0041] Figure 3c It is a flow chart of the bearer release process between the existing terminal and the access network equipment;

[0042] Figure 4 This is a schematic diagram of the hardware structure of an access network device provided by an embodiment of the present invention;

[0043] Figure 5 1 is a schematic diagram of the hardware structure of a terminal provided by an embodiment of the present invention;

[0044] Figure 6 is a flow chart of a relay communication method provided by an embodiment of the present invention;

[0045] Figure 7 is a flow chart of another relay communication method provided by an embodiment of the present invention;

[0046] Figure 8 is a flow chart of another relay communication method provided by an embodiment of the present invention;

[0047] Figure 9 is a flow chart of another relay communication method provided by an embodiment of the present invention;

[0048] Figure 10 is a flow chart of another relay communication method provided by an embodiment of the present invention;

[0049] Figure 11is a flow chart of another relay communication method provided by an embodiment of the present invention;

[0050] Figure 12 is a flow chart of another relay communication method provided by an embodiment of the present invention;

[0051] Figure 13a is a flow chart of another relay communication method provided by an embodiment of the present invention;

[0052] Figure 13b is a flow chart of another relay communication method provided by an embodiment of the present invention;

[0053] Figure 14 This is a schematic diagram of the format of a MAC PDU provided by an embodiment of the present invention;

[0054] Figure 15 This is a structural block diagram of a relay communication device provided by an embodiment of the present invention;

[0055] Figure 16 is a structural block diagram of another relay communication device provided by an embodiment of the present invention;

[0056] Figure 17 is a structural block diagram of another relay communication device provided by an embodiment of the present invention;

[0057] Figure 18 is a structural block diagram of another relay communication device provided by an embodiment of the present invention;

[0058] Figure 19 This is a structural diagram of a communication chip provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0059] The "module" mentioned in this article refers to a program or instruction stored in the memory that can implement certain functions; the "unit" mentioned in this article refers to a functional structure divided according to logic, and the "unit" can be implemented by pure hardware or a combination of software and hardware.

[0060] Figure 1 FIG1 shows a relay communication system provided by an embodiment of the present invention. The relay communication system 100 may be an LTE system, a 5G system or a subsequent evolution system thereof. Figure 1 As shown, the relay communication system includes an access network device 11, a relay terminal 12, and a remote terminal 13. The remote terminal 13 communicates with the access network device 11 through the relay terminal 12.

[0061] Furthermore, the relay terminal 12 is connected to the access network device 11 via a cellular network (including an uplink and a downlink). The remote terminal 13 and the relay terminal 12 communicate via a short-range communication link, such as a sidelink, Bluetooth, or a wireless local area network (WLAN).

[0062] In the uplink transmission direction, that is, from remote terminal 13 to access network device 11, when remote terminal 13 has data to send, remote terminal 13 first transmits the data to relay terminal 12 via a direct link. Then, relay terminal 12 sends the received data to access network device 11 via a cellular uplink. In the downlink transmission direction, that is, from access network device 11 to remote terminal 13, access network device 11 first sends the data to relay terminal 12 via a cellular downlink. Then, relay terminal 12 sends the data to remote terminal 13 via a direct link.

[0063] exist Figure 1 In the relay communication system shown, the relay terminal 12 can be a smartphone, a personal communication service (PCS) phone, a cordless phone, a session initial protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), or other devices. A terminal can also be referred to as a system, a subscriber unit (SU), a subscriber station (SS), a mobile station (MS), a mobile station (MS), a remote station (RS), an access point (AP), a remote terminal (RT), an access terminal (AT), a user terminal (UT), a user agent (UA), or a user equipment (UE). The remote terminal 13 can be a UE, an IoT device, or a wearable device, such as a smart bracelet, a smart watch, or smart glasses.

[0064] The relay terminal 12 communicates with one or more access network devices 11 via a radio access network (RAN).

[0065] The access network device 11 acts as a router between the relay terminal 12 and the rest of the access network, which may include an Internet Protocol (IP) network. The access network device 11 may also coordinate the attribute management of the air interface. For example, the access network device 11 may be a base transceiver station (BTS) in a Global System for Mobile Communication (GSM) or Code Division Multiple Access (CDMA) system, a base station (NodeB) in Wideband Code Division Multiple Access (WCDMA), or an eNB in ​​LTE, although this is not limited in the present invention.

[0066] A relay terminal 12 can provide a relay function for one or more remote terminals 13 (e.g. Figure 1 In the example, a relay terminal 12 provides a relay function for two remote terminals 13. When providing the relay function, one radio bearer RB of the relay terminal 12 can be used to transmit data from one or more RBs of the remote terminals 13. The data from one or more RBs of the remote terminals 13 can be multiplexed with the data from the relay terminal on one RB of the relay terminal for transmission at the Uu interface (the wireless interface between the base station and the UE). When one RB of the relay terminal 12 is used to transmit data from multiple RBs of the remote terminals 13, these multiple RBs belong to different remote terminals. For example, Figure 1 In the example, RB1 and RB2 belong to different remote terminals, but the data on RB1 and RB2 are both transmitted using the relay terminal's bearer RB0.

[0067] In the embodiment of the present invention, the RB of the remote terminal refers to the RB between the access network device and the remote terminal, which is a logical Uu bearer; and the RB of the relay terminal refers to the RB between the access network device and the relay terminal. In the present application, the RB of the relay terminal is divided into a normal bearer and a relay bearer, wherein the normal bearer refers to the RB that only carries the relay terminal's own data, and the relay bearer refers to the RB used to carry the remote terminal's data or the RB that carries both the remote terminal's data and the relay terminal's own data. The signaling process for establishing the RB of the remote terminal can be similar to the signaling process for establishing the normal bearer of the relay terminal, and the messages in the process of establishing the RB of the remote terminal (such as the RRC connection establishment request message, the RRC connection establishment message, etc.) can be forwarded through the relay terminal.

[0068] The protocol stack used when the relay terminal and the access network device communicate (i.e., when communicating based on a common bearer) is as follows: Figure 2a As shown. For normal bearers, they need to go through PDCP / RLC / MAC / PHY processing. Establishing an RB means establishing a corresponding PDCP / RLC entity for it based on the RB's QoS parameters, establishing a corresponding logical channel at the MAC layer, and configuring the logical channel. Modifying an RB means modifying the configuration of the corresponding PDCP / RLC entity and the logical channel. Releasing an RB means releasing the corresponding PDCP / RLC entity and logical channel.

[0069] Figure 2b This figure shows an L2 relay protocol stack used by a remote terminal when communicating with an access network device through a relay terminal (i.e., when communicating over a relay bearer). This L2 relay protocol stack is identical to the UE-network relay wireless protocol stack for wearable device communications defined in the 3rd Generation Partnership Project (3GPP) standard.

[0070] like Figure 2bAs shown, a Packet Data Convergence Protocol (PDCP) protocol stack (hereinafter referred to as Uu PDCP) for the Uu interface is provided between the remote terminal and the access network device. The Uu PDCP protocol stack includes several radio bearers (RBs) for data transmission from the remote terminal. Furthermore, below the Uu PDCP protocol stack of the remote terminal is an adaptation layer (Adaptation Layer), whose functions include at least one of the following: adding a packet header to the remote terminal's data, the header including the remote terminal's identifier; adding the remote terminal's radio bearer identifier (RBID) to the data; identifying data from relay terminals and remote terminals; identifying data from different remote terminals; and identifying data from different radio bearers (RBs) of remote terminals, so that the network side can distinguish data from different remote terminals and send it to different core network gateways and servers for subsequent processing.

[0071] Below the adaptation protocol layer is the PC5 interface wireless protocol stack, which includes the Radio Link Control (RLC) layer (PC5), the Media Access Control (MAC) protocol (PC5), and the Physical (PHY) layer (PC5). The PC5 interface enables direct data communication between remote terminals and relay terminals. It is the air interface for LTE D2D technology, as defined in the 3GPP standard. The direct link corresponding to the PC5 interface is called the "D2D direct link."

[0072] See again Figure 2bBetween the relay terminal and the access network device, a Packet Data Convergence Protocol (PDCP) protocol stack (hereinafter referred to as Uu PDCP) for the Uu interface is implemented (not shown). The Uu PDCP protocol stack includes several radio bearers (RBs) for data transmission to remote terminals. Furthermore, below the Uu PDCP protocol stack of the relay terminal, there is an adaptation layer (Adaptation Layer), whose function is to relay data from remote terminals. Since the relay terminal also transmits data, the adaptation layer can be used to distinguish data from the relay terminal and remote terminals, or data from different remote terminals. Specifically, the adaptation layer logical entity is used to distinguish whether data is from / to the remote terminal or the relay terminal, as well as which bearer the data belongs to. Below the adaptation protocol layer are the RLC (Uu), MAC (Uu), and PHY (Uu) for the Uu interface.

[0073] Figures 3a-3c The signaling processes for establishing, modifying (also called reconfiguring) and releasing a common bearer are shown separately. Figures 3a-3c The establishment, modification and release processes of common bearers are described respectively.

[0074] like Figure 3a As shown in the figure, the process of establishing a common bearer includes:

[0075] S301a: After the terminal context is established, the Mobility Management Entity (MME) sends an Evolved Radio Access Bearer (E-RAB) setup request E-RAB SETUP REQUEST to the eNB to trigger the establishment of a normal bearer.

[0076] S302a: After receiving the request, the eNB sends an RRC connection reconfiguration message to the terminal. The RRC reconfiguration message includes a bearer establishment modification list (drb-ToAddModList) in the dedicated radio resource configuration Radio Resource Config Dedicated.

[0077] Accordingly, after receiving the RRC connection reconfiguration message, the UE establishes a corresponding PDCP protocol entity and configures corresponding security parameters; establishes an RLC entity and configures it; establishes a MAC layer logical channel and configures the logical channel.

[0078] S303a: After the UE configuration is completed, it sends an RRC connection reconfiguration complete message to the eNB.

[0079] S304a: The eNB sends an E-RAB Setup Response message to the MME.

[0080] like Figure 3b As shown in the figure, the modification process of a common bearer includes:

[0081] S301b: The MME sends an E-RAB modification request E-RAB MODIFY REQUEST to the eNB to trigger the modification of the normal bearer.

[0082] S302b: After receiving the request, the eNB sends an RRC connection reconfiguration message to the terminal. The RRC reconfiguration message includes a bearer establishment modification list (drb-ToAddModList) in the dedicated radio resource configuration Radio Resource Config Dedicated.

[0083] Accordingly, after receiving the RRC connection reconfiguration message, the UE reconfigures the corresponding PDCP protocol entity, RLC entity, and logical channel;

[0084] S303b: After the UE configuration is completed, it sends an RRC connection reconfiguration complete message to the eNB.

[0085] S304b: The eNB sends an E-RAB Modify Response message to the MME.

[0086] like Figure 3c As shown in the figure, the release process of a common bearer includes:

[0087] S301c: The MME sends an E-RAB release command E-RAB RELEASE COMMAND to the eNB to trigger the release of the normal bearer.

[0088] S302c: After receiving the request, the eNB sends an RRC connection reconfiguration message to the terminal. The RRC reconfiguration message includes a bearer release list (drb-ToReleaseList) in the dedicated radio resource configuration Radio Resource Config Dedicated.

[0089] Accordingly, after receiving the RRC connection reconfiguration message, the UE releases the corresponding PDCP protocol entity, RLC entity and logical channel;

[0090] S303c: After the UE configuration is completed, it sends an RRC connection reconfiguration complete message to the eNB.

[0091] S304c: The eNB sends an E-RAB release response E-RAB RELEASE Response message to the MME.

[0092] In addition, the common bearer may also be released together with the signaling link.

[0093] from Figure 3a-3c It can be seen from the relevant processes that the establishment, modification and release of ordinary bearers do not involve the configuration of the adaptation layer logical entity. Therefore, the existing protocol stack does not support the establishment, modification and release of relay bearers for relay terminals that use the L2 relay protocol stack. To this end, this application adds adaptation function configuration information or bearer type in the RRC connection reconfiguration message (see below for details). Figure 6-Figure 14 The relevant description of the embodiment) is used to implement the configuration of the adaptation layer logical entity, where the configuration includes establishment, modification and release.

[0094] The following describes the terminal and access network device provided by the embodiment of the present invention in conjunction with a specific hardware structure.

[0095] Figure 4 The hardware structure of an access network device 400 provided in an embodiment of the present invention is shown. The access network device 400 may be an eNB, such as Figure 4 As shown, the access network device 400 includes: a processor 41, a transceiver 42, and a memory 43.

[0096] The processor 41 includes one or more processing cores. The processor 41 executes various functional applications and information processing by running software programs and modules.

[0097] The transceiver 42 includes a receiver Rx and a transmitter Tx. The transceiver 42 can also be implemented as a communication chip. The communication chip can include a receiving module, a transmitting module, and a modulation and demodulation module, etc., which are used to modulate and demodulate information and receive or send the information through wireless signals.

[0098] The transceiver 42, the memory 43, and the processor 41 are coupled via a bus. The memory 43 can be used to store software programs and modules, including an operating system 44 and an application module 45 for at least one function.

[0099] The application module 45 at least includes: a determination module 451 and a sending module 452 .

[0100] Optionally, the processor 41 is used to execute each module in the application module 45 to implement the following Figure 6-Figure 12 The steps that need to be performed by the access network equipment.

[0101] Alternatively, the application module 45 includes at least a generating module and a sending module. In this case, the processor 41 is used to execute each module in the application module 45 to implement the following Figures 13a-13b The steps that need to be performed by the access network equipment.

[0102] In addition, the memory 43 is a computer-readable storage medium that can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0103] Those skilled in the art will understand that Figure 4 The structure of the access network device 400 shown in the figure does not constitute a limitation on the access network device, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0104] Figure 5 The hardware structure of a terminal 500 provided by an embodiment of the present invention is shown. The terminal 500 may be the aforementioned relay terminal or remote terminal, specifically a mobile terminal such as a smart phone. Figure 5 As shown, the terminal 500 includes: a processor 51, a transceiver 52, and a memory 53.

[0105] The processor 51 includes one or more processing cores. The processor 51 executes various functional applications and information processing by running software programs and modules.

[0106] The transceiver 52 includes a receiver Rx and a transmitter Tx. The transceiver 52 can also be implemented as a communication chip. The communication chip can include a receiving module, a transmitting module, and a modulation and demodulation module, etc., which are used to modulate and demodulate information and receive or send the information through wireless signals.

[0107] The transceiver 52, the memory 53, and the processor 51 are coupled via a bus. The memory 53 can be used to store software programs and modules, including an operating system 54 and an application module 55 for at least one function.

[0108] The application module 55 at least includes: a receiving module 551 and a configuration module 552 .

[0109] Optionally, the processor 51 is used to execute each module in the application module 55 to implement the following Figure 6-Figure 12 The steps that need to be performed by the relay terminal.

[0110] Alternatively, the application module 55 includes at least a receiving module, an acquiring module, and a sending module. In this case, the processor 51 is used to execute each module in the application module 55 to implement the following Figures 13a-13b The steps that need to be performed by the relay terminal.

[0111] Alternatively, the application module 55 includes at least a generating module and a sending module. In this case, the processor 51 is used to execute each module in the application module 55 to implement the following Figures 13a-13b The steps that need to be performed by the remote terminal.

[0112] In addition, the memory 53 is a computer-readable storage medium that can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as SRAM, EEPROM, EPROM, PROM, ROM, magnetic memory, flash memory, magnetic disk or optical disk.

[0113] Those skilled in the art will understand that Figure 5 The structure of the terminal 500 shown in the figure does not constitute a limitation of the terminal, and the terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0114] Hereinafter, for ease of description, the embodiments of the present invention will be described in detail by taking the access network device as a base station, the relay terminal as a relay user equipment (English: Relay UE), and the remote terminal as a remote user equipment (English: Remote UE) as an example.

[0115] Figure 6 This is a flowchart of a relay communication method provided by an embodiment of the present invention. Taking the relay terminal creating a new relay bearer according to the adaptation function configuration information as an example, the relay communication method of this application is described in detail. Figure 6 As shown, the method includes:

[0116] S601: The base station sends a first message to the relay terminal.

[0117] The first message may be an RRC connection reconfiguration message, including configuration information of a first bearer. The configuration information of the first bearer includes a first bearer identifier and adaptation function configuration information. The first bearer is a bearer between the base station and the relay terminal, that is, the RB of the relay terminal.

[0118] Optionally, the first bearer may be a data radio bearer (English: Data Radio Bear, abbreviated: DRB) or a signaling radio bearer (English: Signaling Radio Bear, abbreviated: SRB).

[0119] In actual application, the first message includes a bearer establishment modification list, and the first bearer identifier is included in the bearer establishment modification list. In one implementation, the bearer establishment modification list can be divided into a signaling radio bearer establishment modification list srb-ToAddModList and a data radio bearer establishment modification list drb-ToAddModList, the signaling radio bearer establishment modification list srb-ToAddModList includes a signaling radio bearer identifier, and the data radio bearer establishment modification list drb-ToAddModList includes a data radio bearer identifier, and the first message includes at least one of these two lists. In another implementation, the bearer establishment modification list may not distinguish between the signaling radio bearer establishment modification list and the data radio bearer establishment modification list, and the first message uses a list that includes both the signaling radio bearer identifier and the data radio bearer identifier. In these two implementations, the first bearer is any bearer in the bearer establishment modification list that has adaptation function configuration information.

[0120] Of course, the bearer establishment modification list may also include configuration information of a bearer without adaptation function configuration information, and the relay terminal may establish a common bearer according to the configuration information of the bearer without adaptation function configuration information.

[0121] Furthermore, the first bearer identifier may be a specific numerical value, which is used to uniquely represent a first bearer.

[0122] S602: The relay terminal receives a first message and obtains configuration information of a first bearer in the first message.

[0123] S603: The relay terminal determines whether the existing bearers of the relay terminal include the first bearer.

[0124] Specifically, the relay terminal determines whether its current configuration includes the first bearer identifier. If so, it indicates that the existing bearers of the relay terminal include the first bearer. If not, it indicates that the existing bearers of the relay terminal do not include the first bearer.

[0125] S604: If the existing bearers of the relay terminal do not include the first bearer, the first bearer is established, and an adaptation layer logical entity is established for the first bearer.

[0126] In a possible implementation, the adaptation layer logical entity may be a separate protocol entity, namely, an adaptation protocol entity (referred to as the adaptation layer entity in this application). In this implementation, the adaptation function configuration information adaptation-Config is included in the first message as an independent part. Accordingly, in this implementation, establishing the adaptation layer logical entity for the first bearer includes: establishing an adaptation protocol entity according to the adaptation function configuration information. Optionally, the adaptation function configuration information includes at least one of an identifier of the remote terminal and a bearer identifier of the remote terminal. The identifier of the remote terminal may be a local identifier Local ID of the remote terminal. The local identifier is used to identify the remote terminal between the remote base station and the relay terminal, and may be allocated by the base station or the relay terminal. Furthermore, establishing the adaptation protocol entity includes: configuring parameters of the adaptation entity according to the adaptation function configuration information adaptation-Config. The parameter may be a radio bearer identifier of the remote terminal or an identifier of the remote terminal.

[0127] In another possible implementation, the adaptation layer logical entity may be a function of the PDCP protocol entity. In this implementation, the adaptation function configuration information is included as a component in the PDCP configuration information carried by the first message. In this implementation, establishing an adaptation layer logical entity for the bearer corresponding to the first bearer identifier refers to turning on the adaptation function of the PDCP protocol entity. Accordingly, in this implementation, establishing an adaptation layer logical entity for the first bearer includes: establishing a PDCP protocol entity and turning on the adaptation function of the PDCP protocol entity. Optionally, the adaptation function configuration information may include at least one of the following: an identifier of the remote terminal, a bearer identifier of the remote terminal, indication information for indicating whether the adaptation function of the PDCP protocol entity is turned on, indication information for indicating the deletion of the adaptation layer entity, and indication information for indicating the establishment of the adaptation layer entity.

[0128] It is easy to know that after the first bearer is established, in addition to establishing an adaptation layer logical entity for the first bearer, a PDCP protocol entity, an RLC protocol entity and a logical channel will also be established for the first bearer.

[0129] S605: The relay terminal sends a response message to the first message to the base station.

[0130] Specifically, when the first message is an RRC connection reconfiguration message, the response message to the first message is an RRC connection reconfiguration complete message.

[0131] Figure 7 A flowchart of a relay communication method provided by an embodiment of the present invention. Figure 7In the embodiment shown, the relay terminal modifies the ordinary bearer into the relay bearer according to the adaptation function configuration information as an example to describe the relay communication method of the present application in detail. Figure 7 As shown, the method includes:

[0132] S701: The base station sends a first message to the relay terminal.

[0133] Regarding the content of the first message, please refer to S601 and will not be repeated here.

[0134] S702: The relay terminal receives a first message and obtains configuration information of a first bearer in the first message.

[0135] S703: The relay terminal determines whether the existing bearers of the relay terminal include the first bearer.

[0136] The implementation of step S703 is the same as that of step S603, and detailed description is omitted here.

[0137] S704: If the existing bearers of the relay terminal include the first bearer, and the existing first bearer does not have an adaptation layer logical entity, establish an adaptation layer logical entity for the first bearer.

[0138] Specifically, determining whether the existing first bearer has an adaptation layer logical entity may be performed in the following manner:

[0139] Determine whether the current configuration of the relay terminal includes the adaptation function configuration information in the first message. If the current configuration of the relay terminal includes the adaptation function configuration information in the first message, it means that the existing first bearer of the relay terminal has an adaptation layer logical entity. If the current configuration of the relay terminal does not include the adaptation function configuration information in the first message, it means that the existing first bearer of the relay terminal does not have an adaptation layer logical entity.

[0140] Alternatively, determining whether the existing first bearer has an adaptation layer logical entity may be performed in the following manner:

[0141] Determine whether the adaptation function of the PDCP protocol entity corresponding to the first bearer of the relay terminal is turned on. If it is turned on, it means that the existing first bearer of the relay terminal has an adaptation layer logical entity. If it is turned off, it means that the existing first bearer of the relay terminal does not have an adaptation layer logical entity.

[0142] Regarding the implementation of establishing an adaptation layer logical entity for the first bearer, in this implementation, the adaptation function configuration information is included as a component in the PDCP configuration information carried by the first message. In this implementation, establishing an adaptation layer logical entity for the bearer corresponding to the first bearer identifier refers to turning on the adaptation function of the PDCP protocol entity. Correspondingly, in this implementation, establishing an adaptation layer logical entity for the first bearer includes: turning on the adaptation function of the PDCP protocol entity. Optionally, the adaptation function configuration information may include at least one of the following: an identifier of the remote terminal, a bearer identifier of the remote terminal, indication information for indicating whether the adaptation function of the PDCP protocol entity is turned on, indication information for indicating deletion of the adaptation layer entity, and indication information for indicating establishment of an adaptation layer entity. In one possible implementation, the adaptation layer logical entity may be a separate protocol entity, i.e., an adaptation layer entity. See step S604, which will not be repeated here.

[0143] Regarding the content implementation of the adaptation layer logic entity, please refer to step S604 and will not be described in detail here.

[0144] S705: The relay terminal sends a response message to the first message to the base station.

[0145] Figure 8 A flowchart of a relay communication method provided by an embodiment of the present invention. Figure 8 In the embodiment shown, the relay terminal reconfigures the relay bearer according to the adaptation function configuration information as an example to describe the relay communication method of the present application in detail. Figure 8 As shown, the method includes:

[0146] S801: The base station sends a first message to the relay terminal.

[0147] Regarding the content of the first message, please refer to S601 and will not be repeated here.

[0148] S802: The relay terminal receives the first message and obtains configuration information of the first bearer in the first message.

[0149] S803: The relay terminal determines whether the existing bearers of the relay terminal include the first bearer.

[0150] The implementation of step S703 is the same as that of step S603, and detailed description is omitted here.

[0151] S804: If the existing bearers of the relay terminal include the first bearer, and the existing first bearer has an adaptation layer logical entity, reconfigure the adaptation layer logical entity of the first bearer according to the adaptation function configuration information in the first message.

[0152] The method of determining whether the existing first bearer has an adaptation layer logical entity can be referred to step S704 , and the content of the adaptation layer logical entity can be referred to step S604 , so they are not described in detail here.

[0153] In addition, the adaptation layer logical entity of the first bearer is reconfigured, including at least one of adding new parameters and modifying existing parameters. The parameter may be at least one of the identifier of the radio bearer of the remote terminal and the identifier of the remote terminal. For example, if the relay terminal's relay bearer originally carried data for a certain RB of the relay terminal and the first remote terminal, and now the relay bearer also carries data for a certain RB of a second remote terminal, the identifier of the radio bearer of the second remote terminal and the identifier of the second remote terminal are added to the parameters of the adaptation layer logical entity of the first bearer. The first remote terminal and the second remote terminal are two different terminals. For another example, if the relay terminal's relay bearer originally carried data for a certain RB of the relay terminal and the first remote terminal, and now the relay bearer also carries data for a certain RB of the relay terminal and the second remote terminal, the identifier of the RB of the first remote terminal and the identifier of the first remote terminal are replaced in the parameters of the adaptation layer logical entity of the first bearer with the identifier of the radio bearer of the second remote terminal and the identifier of the second remote terminal, respectively. For another example, the relay terminal's relay bearer originally carried data of itself and a certain RB of the first remote terminal, as well as data of a certain RB of the second remote terminal. Now the relay bearer no longer carries data of a certain RB of the second remote terminal, then the wireless bearer identifier of the second remote terminal and the identifier of the second remote terminal are deleted from the parameters of the adaptation layer logical entity of the first bearer.

[0154] S805: The relay terminal sends a response message to the first message to the base station.

[0155] Figure 9 A flowchart of a relay communication method provided by an embodiment of the present invention. Figure 9 In the embodiment shown, the relay terminal modifies the relay bearer of the relay terminal to a common bearer according to the adaptation function configuration information as an example, and the relay communication method of the present application is described in detail. Figure 9 As shown, the method includes:

[0156] S901: The base station sends a first message to the relay terminal.

[0157] Regarding the content of the first message, please refer to S601 and will not be repeated here.

[0158] S902: The relay terminal receives the first message and obtains configuration information of the first bearer in the first message.

[0159] S903: The relay terminal determines whether the existing bearers of the relay terminal include the first bearer.

[0160] The implementation of step S903 is the same as that of step S603, and detailed description is omitted here.

[0161] S904: If the existing bearers of the relay terminal include the first bearer, and the existing first bearer has an adaptation layer logical entity, release the adaptation layer logical entity of the first bearer according to the adaptation function configuration information in the first message.

[0162] In one possible implementation, the adaptation layer logical entity may be a separate protocol entity, namely, an adaptation protocol entity (hereinafter referred to as the adaptation layer entity). Accordingly, in this implementation, if the adaptation function configuration information includes instruction information instructing the relay terminal to release the adaptation layer entity, the relay terminal releases the adaptation layer logical entity of the first bearer. Releasing the adaptation layer logical entity of the first bearer includes: releasing the adaptation layer entity.

[0163] In another possible implementation, the adaptation layer logical entity may be a function of the PDCP protocol entity. Accordingly, in this implementation, if the adaptation function configuration information includes instruction information indicating that the adaptation function of the PDCP protocol entity is disabled, the relay terminal releases the adaptation layer logical entity of the first bearer. Releasing the adaptation layer logical entity of the first bearer includes: disabling the adaptation layer function of the PDCP protocol entity.

[0164] S905: The relay terminal sends a response message to the first message to the base station.

[0165] Figure 10 A flowchart of a relay communication method provided by an embodiment of the present invention. Figure 10 In the embodiment shown, the relay communication method of the present application is described in detail by taking the example of the relay terminal releasing the relay bearer according to the configuration information of the first bearer. Figure 10 As shown, the method includes:

[0166] S1001: The base station sends a first message to the relay terminal.

[0167] The first message may be an RRC connection reconfiguration message, including a first bearer identifier and bearer release indication information. The first bearer is a bearer between the base station and the relay terminal, i.e., the RB of the relay terminal. Optionally, the first bearer may be a data radio bearer or a signaling radio bearer.

[0168] In actual application, the first message includes a bearer release list, and the first bearer identifier is included in the bearer release list. In one implementation, the bearer release list can be divided into a signaling radio bearer release list srb-ToReleaseList and a data radio bearer release list drb-ToReleaseList, the signaling radio bearer release list srb-ToReleaseList includes a signaling radio bearer identifier, and the data radio bearer release list drb-ToReleaseList includes a data radio bearer identifier, and the first message includes at least one of these two lists. In another implementation, the bearer release list may not distinguish between the signaling radio bearer release list and the data radio bearer release list, and the first message uses a list that includes both the signaling radio bearer identifier and the data radio bearer identifier. In these two implementations, the first bearer is any bearer in the bearer release list that has adaptation function configuration information. Of course, the bearer establishment modification list may also include bearers that do not have adaptation function configuration information.

[0169] Furthermore, the first bearer identifier may be a specific numerical value, which is used to uniquely represent a first bearer.

[0170] S1002: The relay terminal receives a first message and obtains configuration information of a first bearer in the first message.

[0171] S1003: The relay terminal determines whether the existing bearers of the relay terminal include the first bearer.

[0172] The specific determination method may refer to step S603 and detailed description is omitted here.

[0173] S1004: If the existing bearers of the relay terminal include the first bearer, release resources corresponding to the first bearer.

[0174] The resources corresponding to the first bearer include an adaptation layer logical entity.

[0175] S1005: The relay terminal sends a response message to the first message to the base station.

[0176] Figure 11 A flowchart of a relay communication method provided by an embodiment of the present invention. Figure 11 In the embodiment shown, the relay terminal creates a new relay bearer according to the bearer type as an example to describe the relay communication method in detail. Figure 11 As shown, the method includes:

[0177] S1101: The base station sends a first message to the relay terminal.

[0178] The first message may be an RRC connection reconfiguration message, including configuration information of the first bearer. The configuration information of the first bearer includes a first bearer identifier and a bearer type, where the bearer type includes the aforementioned normal bearer and relay bearer. In actual applications, the first message includes a bearer establishment modification list, and the first bearer identifier is included in the bearer establishment modification list.

[0179] For detailed description of the first bearer and the bearer establishment modification list, please refer to step S601, and the detailed description is omitted here.

[0180] S1102: The relay terminal receives the first message and obtains configuration information of the first bearer in the first message.

[0181] S1103: The relay terminal determines whether the existing bearers of the relay terminal include the first bearer.

[0182] The specific determination method may refer to step S603 and detailed description is omitted here.

[0183] S1104: If the existing bearers of the relay terminal do not include the first bearer, and the bearer type corresponding to the first bearer identifier is a relay bearer, the first bearer is established, and an adaptation layer logical entity is established for the first bearer.

[0184] If the configuration information of the first bearer also includes the aforementioned adaptation layer logical entity configuration information, the specific implementation of establishing the adaptation layer logical entity for the first bearer is shown in step S604, and detailed description is omitted here.

[0185] S1105: The relay terminal sends a response message to the first message to the base station.

[0186] Figure 12 A flowchart of a relay communication method provided by an embodiment of the present invention. Figure 12 In the embodiment shown, the relay communication method of the present application is described in detail by taking the example of a relay terminal releasing an adaptation layer logical entity of an existing relay bearer according to the bearer type or establishing an adaptation layer logical entity for an existing relay bearer. Figure 12 As shown, the method includes:

[0187] S1201: The base station sends a first message to the relay terminal.

[0188] For the description of the first message, please refer to step S1101 and the detailed description is omitted here.

[0189] S1202: The relay terminal receives the first message and obtains configuration information of the first bearer in the first message.

[0190] S1203: The relay terminal determines whether the existing bearers of the relay terminal include the first bearer.

[0191] The specific determination method may refer to step S603 and detailed description is omitted here.

[0192] S1204: If the existing bearers of the relay terminal include a first bearer that is a normal bearer, and the bearer type corresponding to the first bearer identifier in the first message is a relay bearer, an adaptation layer logical entity is established for the first bearer; or, if the existing bearers of the relay terminal include a first bearer that is a normal bearer, and the bearer type corresponding to the first bearer identifier in the first message is a normal bearer, the adaptation layer logical entity of the first bearer is released.

[0193] The method of establishing the adaptation layer logical entity may refer to step S604, and the method of releasing the adaptation layer logical entity of the first bearer may refer to step S904.

[0194] S1205: The relay terminal sends a response message to the first message to the base station.

[0195] It should be noted that the triggering conditions for the base station to send the RRC connection reconfiguration message to the relay terminal are the same as Figure 3a-3c The conditions shown are the same and will not be repeated here.

[0196] It should be noted that the embodiment of the present invention is described using the RRC connection reconfiguration message as an example of the first message. The first message can also be implemented using other messages, such as an RRC connection establishment message, other authorization messages sent by the base station to the relay terminal, etc.

[0197] Figure 13a This is a flow chart of another relay communication method provided by an embodiment of the present invention. Figure 13a , the method comprising:

[0198] S1301a: The access network device generates a Media Access Control (MAC) Protocol Data Unit (PDU).

[0199] The MAC PDU carries SRB0 data sent to the remote terminal. SRB0 is a type of signaling radio bearer, typically used to transmit signaling for establishing or reestablishing an RRC connection between a UE and a base station. For example, the RRC connection request message sent by the UE to the base station and the RRC connection establishment message sent by the base station to the UE are both transmitted via SRB0. The SRB0 data in this step can be an RRC connection establishment message.

[0200] Figure 14 A schematic diagram of the format of a MAC PDU provided by an embodiment of the present invention. Figure 14The MAC PDU includes a MAC control element (CE) specifically used to distinguish data from a relay terminal and a remote terminal, or to distinguish data from different remote terminals. The MAC CE includes a remote terminal identifier or indication information, which indicates whether the data is data from a relay terminal or a remote terminal. The remote terminal identifier can be an identifier used by the base station and relay terminal to identify the remote terminal, such as a local ID.

[0201] S1302a: The access network device sends a MAC PDU to the relay terminal.

[0202] Specifically, the access network device learns which terminal is the relay of the remote terminal according to the context information of the relay terminal stored in the access network device or the context information of the remote terminal, and sends the MAC PDU to the relay terminal corresponding to the remote terminal.

[0203] S1303a: The relay terminal receives the MAC PDU sent by the access network device, and obtains the identifier of the remote terminal from the MAC CE.

[0204] S1304a: The relay terminal sends the MAC PDU to the remote terminal to which the remote terminal identifier belongs.

[0205] Figure 13b This is a flow chart of another relay communication method provided by an embodiment of the present invention. Figure 13b , the method comprising:

[0206] S1301b: The remote terminal generates a MAC PDU.

[0207] The MAC PDU carries SRB0 data sent to the base station, for example, an RRC connection request message sent to the base station.

[0208] S1302b: The remote terminal sends a MAC PDU to the relay terminal.

[0209] S1303b: The relay terminal receives the MAC PDU sent by the remote terminal, and obtains the identifier of the remote terminal from the MAC CE.

[0210] S1304b: The relay terminal sends the MAC PDU to the access network device using the relay bearer corresponding to the identifier of the remote terminal.

[0211] exist Figure 13a and Figure 13bIn the illustrated embodiment, since SRB0 does not have a corresponding PDCP protocol entity and a real RLC entity, the adaptation function of SRB0 data is implemented at the MAC layer, that is, the data of the relay terminal and the data of the remote terminal are distinguished at the MAC layer, or the data of different remote terminals are distinguished.

[0212] Figure 15 A block diagram of a relay communication device provided by one embodiment of the present invention is shown. The relay communication device can be implemented as all or part of a relay terminal using dedicated hardware circuitry, or a combination of software and hardware. The relay communication device includes a receiving unit 1501 and a configuration unit 1502. Receiving unit 1501 is configured to receive a first message sent by an access network device. Configuration unit 1502 is configured to configure an adaptation layer logical entity for a first bearer based on the first message received by receiving unit 1501.

[0213] Optionally, the first message may be an RRC connection reconfiguration message, an RRC connection establishment message, other authorization messages sent by the base station to the relay terminal, etc.

[0214] In one implementation, the configuration information of the first bearer includes a first bearer identifier and adaptation function configuration information.

[0215] Furthermore, the configuration unit 1502 is used to establish a first bearer when the first bearer does not exist in the existing bearers of the relay terminal, and to establish an adaptation layer logical entity for the first bearer according to the adaptation function configuration information, or the configuration unit 1502 is used to configure the adaptation layer logical entity of the first bearer according to the adaptation function configuration information when the first bearer exists in the existing bearers of the relay terminal.

[0216] Furthermore, when the first bearer exists in the existing bearers of the relay terminal, the configuration unit 1502 is specifically used to establish an adaptation layer logical entity for the first bearer; or, reconfigure the adaptation layer logical entity of the first bearer; or, release the adaptation layer logical entity of the first bearer.

[0217] In another implementation, the configuration information of the first bearer may include a first bearer identifier and bearer release indication information.

[0218] Accordingly, the configuration unit 1502 is configured to release resources of the first bearer, where the resources of the first bearer include an adaptation layer logical entity.

[0219] In another embodiment, the configuration information of the first bearer includes a first bearer identifier and a bearer type, where the bearer type is a relay bearer or a normal bearer. The relay bearer is used to transmit data of a remote terminal or for transmitting data of a remote terminal and a relay terminal, and the normal bearer is used to transmit data of a relay terminal.

[0220] In this embodiment, the configuration unit 1502 is used to establish the first bearer according to the bearer type and establish an adaptation layer logical entity for the first bearer when the first bearer does not exist in the existing bearers of the relay terminal and the bearer type is a relay bearer; or, the configuration unit 1502 is used to configure the adaptation layer logical entity of the first bearer according to the bearer type when the first bearer exists in the existing bearers of the relay terminal.

[0221] Furthermore, the configuration unit 1502 is specifically used to establish an adaptation layer logical entity for the first bearer when the first bearer in the existing bearer is a normal bearer and the bearer type is a relay bearer; or, when the first bearer in the existing bearer is a relay bearer and the bearer type is a normal bearer, release the adaptation layer logical entity of the first bearer.

[0222] Optionally, the adaptation layer logical entity is an adaptation protocol entity or an adaptation function of a PDCP protocol entity.

[0223] When the adaptation layer logical entity is the adaptation function of the PDCP protocol entity, the adaptation function configuration information may further include instruction information for instructing the relay terminal to turn on or off the adaptation function of the PDCP protocol entity.

[0224] For details, please refer to Figure 6-Figure 12 Method embodiment.

[0225] It should be noted that the configuration unit 1502 may be implemented by a processor or by the processor executing program instructions in a memory, and the receiving unit 1501 may be implemented by a receiver Rx or by the processor cooperating with the receiver.

[0226] Figure 16 A block diagram of a relay communication device provided by one embodiment of the present invention is shown. The relay communication device can be implemented as all or part of an access network device through dedicated hardware circuitry, or a combination of software and hardware. The relay communication device includes a determining unit 1601 and a sending unit 1602. Determining unit 1601 is configured to determine configuration information for a first bearer. Sending unit 1602 is configured to send a first message to a relay terminal, the first message including the configuration information for the first bearer determined by determining unit 1601.

[0227] In one implementation, the configuration information for the first bearer includes a first bearer identifier and a bearer type, where the bearer type is either a relay bearer or a normal bearer. A relay bearer is used to transmit data from a remote terminal or from a remote terminal and a relay terminal, while a normal bearer is used to transmit data from a relay terminal. In another implementation, the configuration information for the first bearer includes a first bearer identifier and adaptation function configuration information. In another embodiment, the configuration information for the first bearer includes a first bearer identifier and bearer release indication information.

[0228] Optionally, the adaptation function configuration information includes at least one of an identifier of the remote terminal and a bearer identifier of the remote terminal.

[0229] Optionally, the adaptation layer logical entity is an adaptation protocol entity or an adaptation function of a PDCP protocol entity.

[0230] When the adaptation layer logical entity is the adaptation function of the PDCP protocol entity, the adaptation function configuration information further includes instruction information for instructing the relay terminal to turn on or off the adaptation function of the PDCP protocol entity.

[0231] For details, please refer to Figure 6-Figure 12 Method embodiment.

[0232] It should be noted that the above-mentioned determining unit 1601 can be implemented by a processor or by the processor executing program instructions in a memory, and the above-mentioned sending unit 1602 can be implemented by a transmitter or by the processor cooperating with the transmitter.

[0233] Figure 17 The block diagram of a relay communication device provided by an embodiment of the present invention is shown. The relay communication device can be implemented as all or part of a relay terminal through a dedicated hardware circuit, or a combination of software and hardware. The relay communication device includes: a receiving unit 1701, an acquiring unit 1702, and a sending unit 1703. The receiving unit is used to receive a MAC PDU, the MAC PDU includes a media access control protocol control element MAC CE, the MAC CE includes an identifier of a remote terminal, and the MAC PDU carries the signaling bearer SRB0 data of the remote terminal; the acquiring unit 1702 is used to acquire the identifier of the remote terminal from the MAC CE of the MAC PDU received by the receiving unit 1701; and the sending unit 1703 is used to send the MAC PDU received by the receiving unit 1701.

[0234] For details, please refer to Figure 13a 、 Figure 13b and Figure 14 Method embodiment.

[0235] It should be noted that the above-mentioned acquisition unit 1702 can be implemented by a processor or by the processor executing program instructions in the memory, the above-mentioned receiving unit 1701 can be implemented by a receiver or by the processor cooperating with the receiver, and the above-mentioned sending unit 1703 can be implemented by a transmitter or by the processor cooperating with the transmitter.

[0236] Figure 18A block diagram of a relay communication device provided by an embodiment of the present invention is shown. The relay communication device can be implemented as all or part of an access network device or a remote terminal through a dedicated hardware circuit, or a combination of software and hardware. The relay communication device includes: a generating unit 1801 and a sending unit 1802. The generating unit 1801 is used to generate a media access control protocol data unit MAC PDU, the MAC PDU includes a media access control protocol control element MAC CE, the MAC CE includes an identifier of the remote terminal, and the MAC PDU carries the signaling bearer SRB0 data of the remote terminal; the sending unit 1802 is used to send the MAC PDU generated by the generating unit 1801 to the relay terminal.

[0237] The identifier of the remote terminal is an identifier used between the access network device and the relay terminal to identify the remote terminal, such as a local identifier.

[0238] For details, please refer to Figure 13a 、 Figure 13b and Figure 14 Method embodiment.

[0239] It should be noted that the above-mentioned generating unit 1801 can be implemented by a processor or by the processor executing program instructions in the memory, and the above-mentioned sending unit 1802 can be implemented by a transmitter or by the processor cooperating with the transmitter.

[0240] Figure 19 19 is a schematic diagram of the structure of a communication chip provided in an embodiment of the present invention, which is used in mobile communication system equipment, such as the aforementioned access network equipment or terminal. The communication chip includes a processor 1910, a memory 1920, and a communication interface 1930. Processor 1910 is connected to memory 1920 and communication interface 1930 via a bus.

[0241] The communication interface 1930 is used to implement communication with other communication devices.

[0242] The processor 1910 includes one or more processing cores and runs an operating system or application modules.

[0243] Optionally, the memory 1920 may store an operating system 1922 and an application module 1924 required for at least one function. Optionally, the application module 1924 includes a receiving module 1924a, a processing module 1924b, and a sending module 1924c. The receiving module 1924a is configured to implement steps related to receiving; the processing module 1924b is configured to implement steps related to calculation or processing; and the sending module 1924c is configured to implement steps related to sending.

[0244] In addition, the memory 1920 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as SRAM, EEPROM, EPROM, PROM, ROM, magnetic memory, flash memory, magnetic disk or optical disk.

[0245] Those skilled in the art will understand that Figure 19 The structure shown in the figure does not constitute a limitation of the above-mentioned communication chip, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0246] The above description is merely an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A relay communication method, used for a relay terminal, characterized in that: The method comprises: receiving a first message from an access network device, where the first message includes configuration information of a relay bearer and Packet Data Convergence Protocol (PDCP) configuration information, where the PDCP configuration information includes adaptation function configuration information, and the relay bearer is a bearer between the relay terminal and the access network device; According to the first message, a PDCP protocol entity is configured for the relay bearer, the PDCP protocol entity including an adaptation function, and the adaptation function included in the PDCP protocol entity is used to distinguish data from the relay terminal and the remote terminal, or to distinguish data from different remote terminals.

2. The method according to claim 1, characterized in that The configuration information of the intermediate load includes an intermediate load identifier.

3. The method according to claim 2, characterized in that The adaptation function configuration information includes at least one of an identifier of the remote terminal and a bearer identifier of the remote terminal.

4. The method according to claim 2 or 3, characterized in that The configuring a PDCP protocol entity for the relay bearer according to the first message includes: Establish the PDCP protocol entity and enable the adaptation function of the PDCP protocol entity.

5. The method according to any one of claims 1 to 3, characterized in that The first message is a radio resource control RRC connection reconfiguration message.

6. The method according to any one of claims 1 to 3, characterized in that The method is executed by the relay terminal or a chip in the relay terminal.

7. A relay communication method for access network equipment, characterized in that: The method comprises: Determine configuration information of a relay bearer, where the relay bearer is a bearer between the access network device and the relay terminal; A first message is sent to the relay terminal, the first message including configuration information of the relay bearer and packet data convergence protocol PDCP configuration information, the PDCP configuration information including adaptation function configuration information, the first message is used to instruct the relay terminal to configure a PDCP protocol entity for the relay bearer, the PDCP protocol entity includes an adaptation function, and the adaptation function included in the PDCP protocol entity is used to distinguish data from the relay terminal and remote terminals, or data from different remote terminals.

8. The method according to claim 7, characterized in that The configuration information of the intermediate load includes an intermediate load identifier.

9. The method according to claim 8, characterized in that The adaptation function configuration information includes at least one of an identifier of the remote terminal and a bearer identifier of the remote terminal.

10. The method according to any one of claims 7 to 9, characterized in that The first message is a radio resource control RRC connection reconfiguration message.

11. The method according to any one of claims 7 to 9, characterized in that The method is executed by the access network device or a chip in the access network device.

12. A relay communication device, used for a relay terminal, characterized in that: The device includes: a processor, a memory, and a communication interface; the memory is used to store software programs and modules, and the processor implements the following by running or executing the software programs and / or modules stored in the memory: receiving a first message from an access network device, where the first message includes configuration information of a relay bearer and Packet Data Convergence Protocol (PDCP) configuration information, where the PDCP configuration information includes adaptation function configuration information, and the relay bearer is a bearer between the relay terminal and the access network device; According to the first message, a PDCP protocol entity is configured for the relay bearer, the PDCP protocol entity including an adaptation function, and the adaptation function included in the PDCP protocol entity is used to distinguish data from the relay terminal and the remote terminal, or to distinguish data from different remote terminals.

13. The device according to claim 12, characterized in that The configuration information of the intermediate load includes an intermediate load identifier.

14. The device according to claim 13, characterized in that The adaptation function configuration information includes at least one of an identifier of the remote terminal and a bearer identifier of the remote terminal.

15. The device according to claim 13 or 14, characterized in that When configuring the PDCP protocol entity for the relay bearer according to the first message, the processor implements the following by running or executing a software program and / or module stored in the memory: Establish the PDCP protocol entity and enable the adaptation function of the PDCP protocol entity.

16. The device according to any one of claims 12 to 14, characterized in that The first message is a radio resource control RRC connection reconfiguration message.

17. The device according to any one of claims 12 to 14, characterized in that The device is the relay terminal or a chip in the relay terminal.

18. A relay communication device for accessing network equipment, characterized in that: The device includes: a processor, a memory, and a communication interface; the memory is used to store software programs and modules, and the processor implements the following by running or executing the software programs and / or modules stored in the memory: Determine configuration information of a relay bearer, where the relay bearer is a bearer between the access network device and the relay terminal; A first message is sent to the relay terminal, the first message including configuration information of the relay bearer and packet data convergence protocol PDCP configuration information, the PDCP configuration information including adaptation function configuration information, the first message is used to instruct the relay terminal to configure a PDCP protocol entity for the relay bearer, the PDCP protocol entity includes an adaptation function, and the adaptation function included in the PDCP protocol entity is used to distinguish data from the relay terminal and remote terminals, or data from different remote terminals.

19. The device according to claim 18, characterized in that The configuration information of the intermediate carrier includes the intermediate carrier identifier and adaptation function configuration information.

20. The device according to claim 19, characterized in that The adaptation function configuration information includes at least one of an identifier of the remote terminal and a bearer identifier of the remote terminal.

21. The device according to any one of claims 18 to 20, characterized in that The first message is a radio resource control RRC connection reconfiguration message.

22. The device according to any one of claims 18 to 20, characterized in that The device is the access network device or a chip in the access network device.

23. A communication device, characterized in that: The communication device includes a processor and a storage medium, wherein the storage medium stores instructions. When the instructions are executed by the processor, the method according to any one of claims 1 to 6 is implemented, or the method according to any one of claims 7 to 11 is implemented.

24. A computer-readable storage medium, characterized in that The computer-readable storage medium comprises instructions, and when the instructions are executed by a processor, the method according to any one of claims 1 to 6 is implemented, or the method according to any one of claims 7 to 11 is implemented.

25. A computer program product, characterized in that The computer program product comprises instructions, which, when executed by a processor, enable the method according to any one of claims 1 to 6 to be implemented, or enable the method according to any one of claims 7 to 11 to be implemented.

Images