Remote terminal service identification method, apparatus and device, and storage medium

Abstract

The invention discloses a remote terminal service identification method and device, equipment and a storage medium, and belongs to the technical field of communication. The method comprises the following steps: receiving a first message sent by a first remote terminal; determining a relay carrier channel used for forwarding the first message; forwarding the first message to an opposite-end communication device through the relay bearer channel, wherein a data packet header of the first message carries a terminal identifier and / or a bearer identifier of the first remote terminal; wherein the opposite-end communication equipment is network side equipment, a next-hop relay terminal or a second far-end terminal. In the embodiment of the invention, the services of different remote terminals are distinguished in the service multiplexing process of the remote terminals, so that the relay terminal can multiplex the different services of the different remote terminals in the same transmission channel for transmission, the transmission efficiency is improved, the overall efficiency is considered, and the user experience is improved. And the system efficiency is guaranteed while the user experience is improved.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to a remote terminal service identification method, device, equipment and storage medium. Background Art

[0002] The Long Term Evolution (LTE) system has supported sidelinks since the 12th release, which are used for direct data transmission between terminals (User Equipment, UE) without going through network-side devices. In a typical sidelink relay scenario, the remote terminal (remote UE) uses the sidelink link between the remote terminal (relay UE) and the relay UE to forward its data to the base station. In this scenario, data is transmitted between the remote UE and the base station, and the relay UE plays the role of data transfer.

[0003] In the related art, there is an adaptation layer below the Uu Packet Data Convergence Protocol (Uu PDCP) layer facing the Uu interface of the remote terminal, which is mainly used for service multiplexing of remote UEs, and multiple services of remote UEs can be multiplexed into one Uu RB (RadioBearer) for transmission. However, the related art only proposes the basic functions of the adaptation layer, and does not provide a solution for how the adaptation layer can distinguish services of different remote UEs during the service multiplexing process of remote UEs. Therefore, the adaptation layer cannot work at present. Summary of the invention

[0004] The purpose of the embodiments of the present application is to provide a remote terminal service identification method, device, equipment and storage medium, which can solve the problem of distinguishing services of different remote UEs during service multiplexing of remote UEs in the related art.

[0005] In order to solve the above technical problems, this application is implemented as follows:

[0006] In a first aspect, a remote terminal service identification method is provided, which is applied to a relay terminal, and the method includes:

[0007] Receiving a first message sent by a first remote terminal;

[0008] determining a relay bearer channel for forwarding the first message;

[0009] Forwarding the first message to the opposite communication device through the intermediate bearer channel, wherein the data packet header of the first message carries the terminal identifier and / or the bearer identifier of the first remote terminal;

[0010] The opposite communication device is a network side device, a next hop relay terminal or a second remote terminal.

[0011] In a second aspect, a remote terminal service identification method is provided, which is applied to a network side device, and the method includes:

[0012] Receiving a first message sent by the relay terminal through the relay bearer channel;

[0013] The data packet header of the first message carries the terminal identifier and / or bearer identifier of the first remote terminal.

[0014] In a third aspect, a remote terminal service identification method is provided, which is applied to a remote terminal, including:

[0015] Receiving a first message sent by the relay terminal through the relay bearer channel;

[0016] The data packet header of the first message carries the terminal identifier of the first remote terminal and / or the bearer identifier of the first remote terminal.

[0017] In a fourth aspect, a remote terminal service identification device is provided, which is applied to a relay terminal, and the device includes:

[0018] A first receiving unit, configured to receive a first message sent by a first remote terminal;

[0019] A first processing unit, configured to determine a relay bearer channel for forwarding the first message;

[0020] A first sending unit, configured to forward the first message to a peer communication device through the intermediate bearer channel, wherein a data packet header of the first message carries a terminal identifier and / or a bearer identifier of the first remote terminal;

[0021] The opposite-end communication device is a network-side device, a next-hop relay terminal or a second remote terminal.

[0022] In a fifth aspect, a remote terminal service identification device is provided, which is applied to a network side device, and the device includes:

[0023] A fifth receiving unit, configured to receive a first message sent by the relay terminal through the relay bearer channel;

[0024] The data packet header of the first message carries the terminal identifier and / or bearer identifier of the first remote terminal.

[0025] In a sixth aspect, a remote terminal service identification device is provided, which is applied to a terminal, and the device includes:

[0026] A sixth receiving unit, configured to receive a first message sent by the relay terminal through the relay bearer channel;

[0027] The data packet header of the first message carries the terminal identifier of the first remote terminal and / or the bearer identifier of the first remote terminal.

[0028] In the seventh aspect, a terminal is provided, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the first aspect, or implements the steps of the method described in the third aspect.

[0029] In an eighth aspect, a network side device is provided, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the second aspect.

[0030] In the ninth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented, or the steps of the method described in the third aspect are implemented.

[0031] In the tenth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run terminal or network side device programs or instructions to implement the method described in the first aspect, or the method described in the second aspect, or the method described in the third aspect.

[0032] In an embodiment of the present application, the services of different remote UEs are distinguished during the service multiplexing process of the remote UE, so that the relay terminal can multiplex different services of different remote terminals in the same transmission channel for transmission, thereby improving the transmission efficiency and providing the identifiability of the remote terminal services in end-to-end transmission at the same time, thereby ensuring the service quality of the remote terminal services and taking into account the overall efficiency, thereby ensuring the system efficiency while improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] Figure 1 A block diagram of a wireless communication system to which the embodiments of the present application can be applied;

[0034] Figure 2 It is a schematic diagram of the L2 relay protocol stack architecture in the related technology;

[0035] Figure 3 One of the flow charts of the remote terminal service identification method provided in the embodiment of the present application;

[0036] Figure 4 A schematic diagram of two UEs provided in an embodiment of the present application being connected to a network simultaneously through a relay UE;

[0037] Figure 5 A second schematic diagram of a remote terminal service identification method provided in an embodiment of the present application;

[0038] Figure 6 A third flowchart of a remote terminal service identification method provided in an embodiment of the present application;

[0039] Figure 7 One of the structural schematic diagrams of the remote terminal service identification device provided in the embodiment of the present application;

[0040] Figure 8 A second structural diagram of the remote terminal service identification device provided in an embodiment of the present application;

[0041] Fig. 9 A third structural diagram of the remote terminal service identification device provided in an embodiment of the present application;

[0042] Fig.10 A schematic diagram of the structure of a communication device for implementing an embodiment of the present application;

[0043] Fig.11 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application;

[0044] Fig.12 A schematic diagram of the hardware structure of a network-side device for implementing an embodiment of the present application. DETAILED DESCRIPTION

[0045] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0046] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first" and "second" are generally of the same type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally represents that the objects associated with each other are in an "or" relationship.

[0047] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the systems and radio technologies mentioned above as well as for other systems and radio technologies. However, the following description describes a New Radio (NR) system for illustrative purposes, and the NR terminology is used in most of the following descriptions, although these technologies can also be applied to applications other than NR system applications, such as the 6th generation (6 th Generation, 6G) communication system.

[0048] Figure 1A block diagram of a wireless communication system applicable to the embodiment of the present application is shown. The wireless communication system includes a remote terminal 11, a network side device 12 and a relay terminal 13. Among them, the remote terminal 11 / relay terminal 13 can also be called a terminal device or a user terminal (User Equipment, UE), and the remote terminal 11 / relay terminal 13 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), a wearable device (Wearable Device) or a vehicle-mounted device (VUE), a pedestrian terminal (PUE) and other terminal side devices, and the wearable device includes: a bracelet, a headset, glasses, etc. It should be noted that the specific type of the terminal is not limited in the embodiment of the present application. The network side device 12 can be a base station or a core network, wherein the base station can be referred to as a node B, an evolved node B, an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a B node, an evolved B node (eNB), a 5G base station (gNB) in a 5G network architecture (next generation system), a home B node, a home evolved B node, a WLAN access point, a WiFi node, a transmitting and receiving point (Transmitting Receiving Point, TRP) or some other suitable term in the field. As long as the same technical effect is achieved, the base station is not limited to a specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is taken as an example, but the specific type of the base station is not limited.

[0049] The switching method, apparatus, device and storage medium based on the relay terminal provided in the embodiments of the present application are described in detail below with reference to the accompanying drawings through specific embodiments and their application scenarios.

[0050] In order to better understand the embodiments of the present application, the Sidelink Relay is first described.

[0051] Figure 2 It is a schematic diagram of the L2 relay protocol stack architecture in the related technology. Figure 2It shows an L2 relay protocol stack used when a remote terminal communicates with a network side device through a relay terminal (ie, when communicating based on a relay bearer).

[0052] There is a Uu PDCP protocol stack between the relay terminal and the network side device. The Uu PDCP protocol stack includes several radio bearers (RBs) for data transmission of remote terminals.

[0053] Below the Uu PDCP protocol stack of the relay terminal, there is an adaptation layer, such as Figure 2 The ADAPT, Adaptation Layer, is a new protocol layer that mainly multiplexes the services of remote UEs. The services of multiple remote UEs can be multiplexed into one Uu RB (Radio Bearer) for transmission.

[0054] Since the relay terminal itself also has data transmission, the adaptation layer needs to distinguish the data of the relay terminal and the remote terminal, or the data of different remote terminals. Specifically, the adaptation layer logical entity needs to distinguish whether the data comes from / goes to the remote terminal or the relay terminal, and which bearer of which remote terminal the data belongs to. Below the adaptation protocol layer is the Radio Link Control (RLC) layer, the Media Access Control (MAC) protocol layer, and the Physical (PHY) layer for the Uu interface.

[0055] In addition, there may also be an adaptation layer between the PC5 interface, that is, the remote UE and the relay UE, for service multiplexing.

[0056] In the prior art, only the basic functions of the adaptation layer are proposed, but no solution is given on how the adaptation layer distinguishes services of different remote UEs, how the UE ID content is determined, and how the UE ID is allocated. Therefore, the adaptation layer is currently unable to work.

[0057] Figure 3 One of the flow diagrams of the remote terminal service identification method provided in the embodiment of the present application, the execution subject of the method is the relay terminal relay UE, such as Figure 3 As shown, the method comprises the following steps:

[0058] Step 300: receiving a first message sent by a first remote terminal;

[0059] It can be understood that, when the remote terminal remote UE and the relay terminal relay UE meet the conditions for relay communication, the remote UE sends the first message to the relay UE through the PC5 interface.

[0060] Among them, the PC5 interface is the Sidelink interface between the remote UE and the relay UE.

[0061] The first message is sent by the first remote terminal to the opposite communication device, and is forwarded to the opposite communication device via the relay UE.

[0062] In an embodiment of the present application, the bearer type of the first message may be a signaling radio bearer (SRB) 0, SRB1, SRB2 or a data radio bearer (DRB).

[0063] The relay terminal relay UE receives the first message sent by the first remote terminal through the PC5 interface.

[0064] It should be noted that the first message sent by the first remote terminal may carry the terminal identifier and / or bearer identifier of the first remote terminal, or may not carry the terminal identifier and / or bearer identifier of the first remote terminal.

[0065] Step 301: determine a relay bearer channel for forwarding the first message;

[0066] In the embodiment of the present application, the relay UE may multiplex the services of each remote terminal mapped to the same radio link control channel into the same large pipe for transmission, and may also multiplex the services from the same remote terminal to different opposite-end communication devices.

[0067] After receiving the first message sent by the first remote terminal, the relay UE needs to determine through which relay bearer channel to forward the first message to the opposite communication device.

[0068] It can be understood that the relay bearer channel is used to carry end-to-end RB data of the remote terminal, and the relay bearer channel can be a relayed radio link control channel relayed RLC channel.

[0069] Optionally, the relay UE determines a relay bearer channel for forwarding the first message based on a logical channel identifier of a PC5 interface corresponding to the first message, an SRB0 identifier of the first message, or an end-to-end bearer identifier of the first remote terminal.

[0070] Step 302: forwarding the first message to the opposite communication device through the intermediate bearer channel, wherein the data packet header of the first message carries the terminal identifier and / or bearer identifier of the first remote terminal;

[0071] The relay UE forwards the first message to the opposite communication device through the relay bearer channel, and carries the terminal identification UE ID and / or bearer identification RB ID of the first remote terminal in the data packet header of the first message. The network side device can distinguish the bearers from different remoteUEs according to the UE ID and / or RB ID carried in the data packet header of the first message, thereby realizing the identification of the service of the remote terminal remote UE.

[0072] Optionally, in an embodiment of the present application, the opposite communication device may be a network side device, a next-hop relay terminal or a second remote terminal.

[0073] The application scenario of the embodiment of the present application may be a U2N (UE to NW) scenario, i.e., Remote UE<–>relay UE<–>NW, where there may be multiple hops, i.e., there are multiple serial relay UEs, where the relay UE closest to the remote UE is denoted as the access relay UE, and the relay UE connected to the NW is denoted as the root relay UE. If bearer multiplexing is required, UE ID and / or RB ID may be used to distinguish the remote UE and the bearer between the current relay UE and the next hop or previous hop relay UE, between the root relay UE and the NW, and between the access relay UE and the remote UE.

[0074] The application scenario of the embodiment of the present application can be a U2U (UE to UE) scenario, that is, Source remote UE<–>relay UE<–>Target remote UE, where multiple hops are possible, that is, there are multiple serial relay UEs, where the relay UE closest to the source remote UE is recorded as the access relay UE, and the relay UE connected to the target remote UE is recorded as the root relay UE. If bearer multiplexing is required, UE ID and / or RB ID can be used to distinguish remote UEs and bearers between the current relay UE and the next hop or previous hop relay UE, between the root relay UE and the target remote UE, and between the access relay UE and the source remote UE.

[0075] In an embodiment of the present application, the services of different remote UEs are distinguished during the service multiplexing process of the remote UE, so that the relay terminal can multiplex different services of different remote terminals in the same transmission channel for transmission, thereby improving the transmission efficiency and providing the identifiability of the remote terminal services in end-to-end transmission at the same time, thereby ensuring the service quality of the remote terminal services and taking into account the overall efficiency, thereby ensuring the system efficiency while improving the user experience.

[0076] Optionally, determining the relay bearer channel corresponding to the first message includes:

[0077] Determine the type of the first message based on the logical channel identifier of the PC5 interface corresponding to the first message, the SRB0 identifier of the first message, or the end-to-end bearer identifier of the first remote terminal;

[0078] In a case where the type of the first message is an SRB0 message, determining that the intermediate bearer channel used to forward the first message is a first default radio link control channel; or,

[0079] When the type of the first message is not an SRB0 message, based on the mapping relationship between the type of wireless bearer data and the wireless link control channel, the intermediate bearer channel used to forward the first message is determined to be a wireless link control channel having a mapping relationship with the type of the first message.

[0080] It can be understood that the relay UE first determines the type of the first message based on the logical channel identifier of the PC5 interface corresponding to the first message, the SRB0 identifier of the first message, or the end-to-end bearer identifier of the first remote terminal, and then determines the relay bearer channel based on the type of the first message.

[0081] Since the SRB0 message is a Radio Resource Control (RRC) Setup Request, the relay UE needs to have a default relayed RLC channel configuration for carrying the SRB0 message. Therefore, in the embodiment of the present application, the types of the first message are divided into two categories: SRB0 message and non-SRB0 message.

[0082] In order to implement bearer multiplexing, the network side device needs to configure the first default radio link control channel for the SRB0 message.

[0083] The first default radio link control channel is used to carry SRB0 messages.

[0084] The network side device also needs to configure a mapping relationship for other non-SRB0 messages, where the mapping relationship is specifically a mapping relationship between the type of radio bearer data and the radio link control channel.

[0085] In a case where the type of the first message is an SRB0 message, the relay UE determines that the relay bearer channel used to forward the first message is a first default radio link control channel.

[0086] When the type of the first message is not an SRB0 message, the relay UE determines, based on the mapping relationship between the type of wireless bearer data and the wireless link control channel, that the relay bearer channel used to forward the first message is a wireless link control channel having a mapping relationship with the type of the first message.

[0087] In one embodiment, the relay UE determines the type of the first message based on the logical channel identifier of the PC5 interface corresponding to the first message, and further determines the relay bearer channel based on the type of the first message.

[0088] Data differentiation on the PC5 interface can be done in the following ways:

[0089] Different Uu RBs and PC5 RBs are mapped one by one for identification and distinction. For example, logical channels 0-3 on the PC5 interface are the existing PC5 signling, logical channels 4 and 5 are legacy PC5 services, logical channel 10 carries remote UE Uu SRB0, logical channel 11 carries remote UE Uu SRB1, logical channel 12 carries remote UE Uu SRB2, logical channel 14 carries remote UE Uu DRB1, logical channel 15 carries remote UE Uu DRB2, and so on.

[0090] Figure 4 The present invention provides a schematic diagram of two UEs connected to the network through a relay UE at the same time. Figure 4 As shown in the figure, on the PC5 interface, there may be legacy PC5 SRBs, PC5 DRBs, RLC channels for Uu SRBs and RLC channels for Uu DRBs between each remote UE and relay UE. Each type of bearer can be an independent channel to facilitate the relay UE to distinguish data.

[0091] For example, the logical channels between Remote UE1 and relay UE are divided as follows:

[0092] Logical channels 0-3: correspond to PC5 SRB0, SRB1, SRB2 and SRB3 respectively, which are the existing PC5 bearer types;

[0093] Logical channels 4-14: correspond to PC5 DRB1 to DRB11 respectively;

[0094] Logical channel 15: is the default or configured relayed RLC channel used to carry Uu SRB0 of remote UE1;

[0095] Logical channels 16-17: are configured relayed RLC channels used to carry Uu SRB1 and SRB2 of remote UE1;

[0096] Logical channels 18-31: are configured relayed RLC channels used to carry Uu DRB1 to DRB14 of remote UE1;

[0097] The range 32-63 is used for the Uu interface, an extended logical channel.

[0098] The Relay UE receives the PC5 bearer content and directly processes the bearer of the PC5 interface according to the existing process. The data from the RLC channel needs to be forwarded to the network side device.

[0099] After the relay UE receives the first message, it can determine the type of the first message based on the logical channel identifier of the PC5 interface corresponding to the first message. For example, if the logical channel identifier of the PC5 interface corresponding to the first message received by the relay UE is 15, because logical channel 15 is used to carry Uu SRB0, it can be determined that the type of the first message at this time is an SRB0 message.

[0100] In one embodiment, the relay UE determines the type of the first message based on the SRB0 identifier of the first message, and further determines a relay bearer channel for forwarding the first message.

[0101] For example, if the SRB0 identifier of the first message is 0, indicating that the first message is not an SRB0 message, then the relay bearer channel used to forward the first message can be determined based on the mapping relationship between the type of radio bearer data configured on the network side and the radio link control channel RLC channel. If the SRB0 identifier of the first message is 1, indicating that the first message is an SRB0 message, the first default radio link control channel default relayed RLC channel is used as the relay bearer channel of the first message.

[0102] Optionally, the relay UE determines the type of the first message based on the end-to-end bearer identifier of the first remote terminal, and further determines a relay bearer channel for forwarding the first message.

[0103] Among them, the end-to-end bearer identifier of the first remote terminal refers to the RB ID of the first remote terminal communicating with the network side, for example, remote UE Uu SRB0, its RB ID = 0, remote UE SRB1, its RB ID = 1, remote UE SRB2, its RB ID = 2, and the remaining DRBs are configured and assigned RB IDs through the end-to-end RRC process.

[0104] For example, if the end-to-end bearer identifier of the first remote terminal is 1, the type of the first message is an SRB1 message, and the relay UE determines the relay bearer channel used to forward the first message based on the mapping relationship between the type of wireless bearer data configured on the network side and the wireless link control channel RLC channel.

[0105] In some optional embodiments, determining the relay bearer channel corresponding to the first message further includes:

[0106] When the type of the first message is not an SRB0 message and a radio link control channel having a mapping relationship with the type of the first message does not exist, the relay bearer channel used to forward the first message is determined to be a second default radio link control channel configured on the network side.

[0107] In some cases, if the network side does not configure a mapping relationship between the type of the first message and the radio link control channel, the second default radio link control channel is used as the intermediate bearer channel for forwarding the first message.

[0108] The second default radio link control channel is used to carry radio bearer data of a remote terminal for which no mapping relationship is configured.

[0109] The second default radio link control channel is the same as or different from the first default relay radio link control channel.

[0110] In an embodiment of the present application, the successor bearer communication channel is determined based on the logical channel identifier or SRB0 identifier or end-to-end bearer identifier of the PC5 interface corresponding to the first message sent by the remote terminal, thereby realizing multiplexing of different services of different remote terminals in the same transmission channel, thereby improving transmission efficiency.

[0111] Optionally, the terminal identifier includes one of the following:

[0112] PC5 link L2 ID;

[0113] Some bits of the PC5 link L2 ID;

[0114] The unique index of the remote terminal in the relay terminal;

[0115] Unique index of the remote terminal in the network-side device.

[0116] In the embodiment of the present application, the terminal identifier UE ID can use the PC5 link layer 2 identifier PC5link L2 ID of the terminal identifier. The PC5 link L2 ID is the L2 ID used by the remote UE and the relay UE when communicating on the PC5 interface, and the length is 24 bits.

[0117] Since the PC5 link L2 ID is the ID used in existing PC5 communications, it can ensure that the UE identity can be uniquely determined within a certain range, and is relatively convenient to use. However, the disadvantage is that the cost is high, and each UE needs to use 24 bits for identification and distinction.

[0118] In order to save overhead, the 24-bit L2 ID may also be truncated, for example, by taking the lower 16 bits, but the cost of saving overhead is the possibility of UE ID duplication.

[0119] The main purpose of UE ID is to distinguish different remote UEs linked to the same relay UE, or to distinguish different remote UEs mapped to the same radio link control channel. Therefore, other definitions and allocation methods can also be considered to obtain a smaller UE ID length, thereby saving overhead and improving resource utilization.

[0120] In some optional embodiments, the terminal identifier may also be a unique index of the remote terminal in the relay terminal, that is, it may also be a unique index allocated by the relay terminal to the remote terminal.

[0121] Optionally, the remote terminal service identification method further includes:

[0122] allocating a terminal identification index to each remote terminal connected to the relay terminal; or,

[0123] A terminal identification index is allocated to each remote terminal mapped to the same radio link control channel.

[0124] In order to reduce the overhead, in one embodiment, UE ID is defined as the number / index of all remote UEs connected to the same relay UE. The relay terminal relay UE allocates a terminal identification index to each remote terminal connected to the relay UE, and one remote terminal corresponds to a unique terminal identification index.

[0125] Taking the U2N architecture as an example, a relay UE has limited processing power, and the number of UEs that can be served at the same time will have an upper limit. For example, if this upper limit is N, then the index of the remote UE that communicates with the network through this relay UE can be in the interval [0, N-1], and each index uniquely identifies a remote UE. Inside the relay UE, the correspondence between the remote UE index and the real L2 ID is stored, so that correct communication can be carried out. For NW, it is necessary to store the mapping relationship between the UE identity carried in the RRC signaling and the remote UE index to correctly send, receive and process UE data.

[0126] Optionally, in one embodiment, the UE ID is defined as the index of the remote UE mapped to the same radio link control channel, that is, the relay terminal relay UE allocates a terminal identification index to each remote terminal mapped to the same radio link control channel.

[0127] Optionally, the remote terminal service identification method further includes:

[0128] The terminal identification index is sent to the opposite-end communication device of the remote terminal corresponding to the terminal identification index through a radio resource control RRC message or a UP process.

[0129] After the relay terminal relay UE allocates a terminal identification index to the remote terminal, it sends the terminal identification index to the opposite communication device of the remote terminal corresponding to the terminal identification index through a radio resource control RRC message or a UP process.

[0130] For example, when the first remote UE is connected to a relay UE, the relay UE can assign UEindex=0 to it, and send the remote UE's SRB0 message RRC Setup request to the network with UE index=0 and RB ID. After receiving it, the network-side device associates the UE identity in the setup message with UE index=0 under the relay UE. Then all subsequent downlink messages and downlink data sent to this UE are distinguished by UE index=0 and the corresponding RB ID, and sent to the relay UE in the relay bearer channel. After receiving it, the relay UE can also identify the corresponding remote UE through UEindex=0, and use the remote UE L2 ID for PC5 communication to send data to the correct remote UE. The UE index is assigned by the relay UE and notified to the NW.

[0131] In some optional embodiments, the terminal identifier may also be a unique index allocated by the network-side device to the remote terminal.

[0132] Since the first message of all remote UEs connected to the relay UE is an SRB0 message, the network does not have any prior information about the remote UE. Therefore, a special Uu channel can be used. This Uu RLC channel does not carry any remote UE ID and RB ID information, that is, there is no adaptation layer header. All SRB0 messages of remote UEs are transmitted here without distinction. After receiving the message, the NW interprets the message to determine the UE identity, and then assigns a unique UE index to the UE in the relay UE.

[0133] There are two ways to notify the relay UE of the terminal identification index allocated by the network side to the remote UE.

[0134] Optionally, the remote terminal service identification method further includes:

[0135] A radio resource control RRC message sent by a network side device is received, where the RRC message carries a terminal identification index allocated by the network side device to a remote terminal that has sent an SRB0 message.

[0136] Optionally, the network-side device informs the relay UE that an index is assigned to the remote UE through an RRC message between the relay UE and the relay UE. To distinguish the remote UE in the RRC message, part of the content of the RRC setup request (i.e., SRB0 message), such as 40 bits, can be used to identify the remote UE. Since the RRC setup request message contains the UE identity, the network side indicates the UE by copying all or part of the content. For the relay UE, the RRC setup request message forwarded for the remote UE needs to be backed up and cached. Once the relay UE receives the configuration message, it can be compared to know which remote UE is assigned the index, and then the L2 ID of the remote UE is associated with the index for storage for subsequent transit data transmission.

[0137] Optionally, the remote terminal service identification method further includes:

[0138] Receive a control protocol data unit / first data packet sent by a network side device, where the control protocol data unit / first data packet carries identity information of a remote terminal that sends an SRB0 message and a terminal identification index allocated by the network side device to the remote terminal that sends the SRB0 message;

[0139] The remote terminal corresponding to the terminal identification index is determined according to the identity information.

[0140] The network side device informs the relay UE about the allocation of the index through the user plane (UP) process. The specific method is to use the control protocol data unit control PDU of the UP, which carries the index and the remote UE identity information in the setup request message. After reading it, the relay UE can know that the network side device has allocated the corresponding index to the remote UE.

[0141] Optionally, the network side device sends a first data packet, which carries the newly allocated UE index and remote UE identity information. After the relay UE interprets it, it can also establish a correct association between the remote UE and the index for subsequent relay data transmission.

[0142] After the corresponding index of the remote UE is established, the subsequent sending and receiving packets can use this index to identify the data of the remote UE, so as to correctly understand the ownership of the data.

[0143] Generally speaking, the number of remote UEs connected to a relay UE is not too large, such as 32 or 16. Therefore, in this method, the index used to distinguish the remote UE only needs a few bits, not more than one byte, thus greatly saving overhead.

[0144] It should be noted that in the U2U architecture, a similar approach can also be adopted, where the relay UE assigns a unique index to each remote UE connected to it to identify different remote UEs. The assignment method can be PC5 RRC notification between the relay UE and the remote UE.

[0145] Optionally, the bearer identifier includes one of the following:

[0146] End-to-end bearer identification;

[0147] The label of the bearer corresponding to the remote terminal mapped to the same radio link control channel.

[0148] In some optional embodiments, the bearer identification RB ID can directly use the end-to-end RB ID for communication between the remote UE and the NW, for example, remote UE Uu SRB0, its RB ID = 0, remote UE SRB1, its RB ID = 1, remoteUE SRB2, its RB ID = 2, and the remaining DRBs are configured and assigned RB IDs through the end-to-end RRC process.

[0149] In some optional embodiments, the bearer identifier RB ID may also be a bearer number corresponding to a remote terminal mapped to the same radio link control channel.

[0150] Since the maximum number of end-to-end bearers supported is 32, that is, RB ID needs 5 bits to identify the end-to-end bearer. However, the number of RBs that can be multiplexed into the same large transmission channel within a remote UE is not large, and the QoS needs to be the same or similar, for example, a maximum of 4 RBs, then the length of RB ID can be reduced to 2 bits.

[0151] This is equivalent to the mapping relationship that needs to be notified to the RB, and an example of the mapping is shown in Table 1 below.

[0152] Table 1 RB mapping relationship

[0153] Before Mapping After mapping RB 1in Remote UE 1 Channel 1, remote UE1, RB=0 RB 2in Remote UE 1 Channel 1, remote UE1, RB=1 RB 3in Remote UE 1 Channel 1, remote UE1, RB=2 RB 4in Remote UE 1 Channel 2, remote UE1, RB=0 RB 5in Remote UE 1 Channel 2, remote UE1, RB=1 … …

[0154] It is equivalent to notifying that the free 32-bit traditional end-to-end RB ID is mapped to index y of RLC channel x. The decision is made by selecting the corresponding RLC channel based on the principle of the same or similar QoS, and then checking whether the remote UE has other RBs mapped to this RLC channel, and sorting the RBs mapped to the same RLC channel in a group.

[0155] The mapping is created and notified as follows:

[0156] For signaling radio bearers, since the number of Uu SRBs (used in U2N scenarios) and PC5 SRBs (used in U2U scenarios) is limited and their functions are relatively clear, each remote UE must have these SRBs. Therefore, a fixed mapping method can be adopted, and the SRBs are mapped to the default RLC channel n by default or configured in advance, and the RB indexes are also fixed.

[0157] For DRB, because DRB has the characteristics of burstiness and diversity, it is only configured by the base station to the relay UE through Uu RRC (for U2N scenarios) after the service arrives, or by the relay UE to the remote UEs at both ends through PC5 RRC (for U2U scenarios); after configuration, normal communication can be carried out.

[0158] Optionally, the remote terminal service identification method further includes:

[0159] A bearer label is allocated to each remote terminal mapped to the same radio link control channel.

[0160] It can be understood that the relay UE allocates a bearer label to each remote terminal mapped to the same radio link control channel, and configures it to the corresponding remote UE through a PC5 RRC message.

[0161] For example, data of different target UE 2, target UE 3, and target UE 4 may be multiplexed between Remote UE 1 and relay UE, and the allocated bearer numbers may correspond to: end-to-end bearer between UE 1 and UE 2, end-to-end bearer between UE 1 and UE 3, and end-to-end bearer between UE 1 and UE 4, respectively.

[0162] For example, between the relay UE and the target UE2, there are different source UE 1, source UE 5, and source UE 6, so the allocated bearer numbers may correspond to: the end-to-end bearer between UE 1 and UE2, the end-to-end bearer between UE 5 and UE2, and the end-to-end bearer between UE 6 and UE2, respectively.

[0163] The U2N scenario is similar and will not be described in detail here.

[0164] In an embodiment of the present application, a relay terminal or a network-side device allocates a terminal identification index and / or a bearer number to a remote UE, and distinguishes services of different remote UEs during service multiplexing of the remote UE, so that the relay terminal multiplexes different services of different remote terminals in the same transmission channel for transmission, thereby improving transmission efficiency and reducing resource overhead.

[0165] Optionally, based on the above embodiment, the remote terminal service identification method further includes:

[0166] Receiving a second message sent by the opposite communication device;

[0167] Based on the terminal identifier and / or bearer identifier carried in the data packet header of the second message, the second message is forwarded to the corresponding remote terminal.

[0168] It can be understood that the relay UE receives the second message sent by the opposite communication device, for example, if the first message is an RRC Setup request message, the second message is an RRC Setup message, and then forwards the second message to the corresponding remote terminal based on the terminal identifier and / or bearer identifier carried in the data packet header of the second message.

[0169] Optionally, based on the above embodiment, before receiving the first message sent by the first remote terminal, the method further includes:

[0170] When the first remote terminal meets the conditions for establishing relay communication, and the link quality between the relay terminal and the first remote terminal and the link quality between the relay terminal and the first communication device meet the conditions for establishing relay communication, interact with the first remote terminal through the PC5 interface to determine whether the relay terminal has the ability to transfer the first remote terminal service.

[0171] For example, the remote UE is at the edge of the cell, and the RSRP is lower than a threshold configured by the network, so it cannot communicate directly with the NW. At this time, it needs to transfer its data to the network via the relay UE. At this time, the first terminal meets the conditions for establishing relay communication.

[0172] The relay UE also needs to meet certain conditions. The link quality between the relay terminal and the first remote terminal and the link quality between the relay terminal and the first communication device meet the conditions for establishing relay communication to ensure that subsequent communication proceeds normally.

[0173] After the above basic link conditions are met, the remote UE and the relay UE need to exchange transfer service information through the PC5 process, such as performing a discovery process, to ensure that the relay UE can perform the transfer service of the service to be initiated by the remote UE.

[0174] Optionally, the adaptation layer protocol header of the first message carries a terminal identifier of the first remote terminal and / or a bearer identifier of the first remote terminal.

[0175] It should be noted that the UE ID and RB ID mentioned in this application can be used for the adaptation layer and included in the adaptation layer header.

[0176] But it is not limited to this, and all protocol layers that require data multiplexing can be used.

[0177] The following describes how to use UE ID and RB ID to distinguish the bearers of different remote UEs in conjunction with specific application scenarios.

[0178] In the U2N architecture, the L2 Remote UE<–>relay UE<–>NW scenario is taken as an example to explain how to use UE ID and RB ID to distinguish the bearers of different remote UEs so as to perform normal relay communication.

[0179] First, regarding the meaning and value of UE ID and RB ID, the following principles are adopted in this example:

[0180] UE ID is the PC5 link L2 ID, and RB ID is the end-to-end bearer identifier.

[0181] The following is the process of how the remote UE establishes L2 relay U2N communication and how to perform bearer multiplexing between the relay and NW:

[0182] Step a: The remote UE meets the conditions for establishing L2 relay U2N communication and finds a suitable relay UE.

[0183] For example, when the remote UE is at the edge of a cell and its RSRP is lower than a threshold configured by the network, it cannot communicate directly with the NW. In this case, the data needs to be transferred to the network via the relay UE.

[0184] The relay UE also needs to meet certain conditions. For example, the link condition from the relay UE itself to the NW is good enough and the RSRP is higher than a threshold configured by the network. Optionally, the link condition from the relay UE to the NW cannot be too good, that is, the RSRP must be lower than a threshold configured by the network. The advantage of this is to avoid excessive interference from the UE in the cell center acting as a relay UE.

[0185] The link quality of PC5 between the remote UE and the relay UE also needs to meet a certain threshold, that is, the PC5 RSRP (Reference Signal Receiving Power) is higher than the threshold to ensure normal subsequent communication.

[0186] After the above basic link conditions are met, the remote UE and the relay UE need to exchange transfer service information through the PC5 process, such as performing a discovery process, to ensure that the relay UE can perform the transfer service of the service to be initiated by the remote UE.

[0187] Step b: After the relay UE decides to provide service relay services to the remote UE, it needs to make certain preparations on its own Uu interface, such as configuring a default relayed RLC channel, at least to carry the end-to-end RB data of the remote UE for which no mapping relationship is configured.

[0188] For example, if the relay UE has not entered the Connected state before, in order to transfer data, it needs to enter the Connected state first and inform the network side to request data transfer for other remote UEs. The network side needs to configure a default relayed RLC channel for the relay UE. Its characteristics are that it is configured as RLC AM (Acknowledge Mode) or UM (UnAcknowledge Mode), has an adaptation layer and a header, and the adaptation layer header contains UE ID and RB ID. The remote UE data without any mapping relationship is mapped to this RLC channel by default.

[0189] If the relay UE is already in the Connected state and it has its own Uu data transmission, or has relayed data transmission from other remote UEs, then it is very likely that a default relayed RLC channel already exists and can carry remote UE data without any mapping relationship.

[0190] For example: The logical channel number of the Uu port of the relay UE is: 0 is its own SRB0 message, 1 is its own SRB1 message, 2 is its own SRB2 message, 4 is its first DRB, 5 is its second DRB, 10 is the default relayed RLC channel, which is used to carry relay data without mapping relationship, 11-13 are other relayed RLC channels, which carry data of different QoS of other remote UEs with mapping relationship configured.

[0191] Step c: The remote UE sends the first Uu message - RRC Setup Request. This message is sent to the NW, but needs to be sent to the relay UE first and forwarded by it.

[0192] The Remote UE sends the first Uu message to the relay UE via the PC5 interface;

[0193] After receiving the first message, the relay UE uses its own default relayedRLC channel obtained in step b to send the first message, where the adaptation header of the data packet carries the remoteUE L2 ID and RB ID. Since the first message is an SRB0 message, the RB ID = 0;

[0194] Step d: The network side receives the data sent by the relay through the default relayed RLC channel, processes it, and responds to it by sending an RRC Setup message (carrying L2 ID and RB ID = 0);

[0195] Among them, according to the UE ID, it can be known that this is a new remote UE (because the configuration of the UE is not cached), and through RB ID=0, it can be known that it is an SRB0 message of the remote UE. The message is interpreted and processed normally, and an RRCSetup message is generated in response.

[0196] For this RRC Setup message, the network side sends it on the downlink default relayed RLC channel, fills in the received L2 ID with the UE ID in the adaptation header, and RB ID = 0, indicating that SRB0 is still used for transmission.

[0197] Since the RRC Setup message generally establishes SRB1, the network side also needs to configure how to map the SRB1 of the remote UE on the Uu interface and send the configured mapping relationship to the relay UE, that is, an existing relayed RLC channel can be used or a new relayed RLC channel can be established to map the SRB1 of the remote UE, where the remote UE is identified by UE ID = L2 ID.

[0198] Step e: The relay UE receives the RRC setup message and reads the UE ID in the adaptation header to find the corresponding remote UE. It then forwards the RRC Setup message to the corresponding remote UE on the PC5 interface.

[0199] Step f: When the remote UE receives the RRC Setup message, it establishes SRB1 according to the configuration in the message and sends a subsequent RRC Setup Complete message on the newly established SRB1.

[0200] The subsequent steps will not be repeated here. The relayed RLC channel mapping and configuration of SRB1 in the relay UE Uu have been prepared in advance. The relay UE uses the L2 ID and RB ID=1 corresponding to the remote UE to inform the NW that this is the SRB1 message of the remote UE. The same applies to the downlink.

[0201] And for the SRB2 and DRB of the remote UE, it is similar. Through the SRB1 channel, that is, the RRC signaling process, first configure the relay Uu RLC channel mapping of SRB2 and DRB, and then send the configured relay UuRLC channel mapping of SRB2 and DRB to the remote UE.

[0202] After the relay and NW are established, L2 ID and end-to-end RB ID can be used in a relay Uu RLC channel to clearly distinguish different remote UEs and specific bearer content (SRB0 / 1 / 2 / DRB).

[0203] The following describes how to use UE ID and RB ID to distinguish the bearers of different remote UEs in the U2U scenario.

[0204] In the U2U architecture, taking the L2 Source remote UE<–>relay UE<–>Target remote UE scenario as an example, this article explains how to use UE ID and RB ID to distinguish the bearers of different remote UEs, so as to perform normal relay communication.

[0205] First, regarding the meaning and value of UE ID and RB ID, the following principles are adopted in this example:

[0206] UE ID is the PC5 link L2 ID, and RB ID is the end-to-end bearer identifier.

[0207] Between the relay UE and the target remote UE (referred to as the second hop), the relay UE can multiplex the data of multiple source remote UEs (because their target remote UE is the same UE) to reduce the number of bearers that may appear in the second hop:

[0208] Each source remote UE is still distinguished by its own L2 ID, and this L2 ID needs to be recognizable by the target remote UE. For example, during the discovery process, the L2IDs of each other are exchanged. The L2 ID used here can be the same as the L2 ID used for PC5 communication between the source remote UE and the relay UE, or it can be different. If they are different, it means that the source remote UE has at least two L2 IDs, one of which is used for PC5 transmission between the relay UE and the other L2 ID is used to identify itself during end-to-end communication between the source remote UE and the target remote UE. If there are two L2 IDs, the relay UE needs to store the corresponding relationship between the two L2 IDs for use in different scenarios. For example, the relay UE receives data from the source remote UE through the first L2 ID on the PC5 interface. It needs to find the corresponding second L2 ID through the first L2 ID and put it in the adaptation layer header to identify the source remote UE at the second hop.

[0209] And carry the corresponding RB ID to identify which bearer of which source remote UE. Here, the RB ID still uses the end-to-end RB ID between the source remote UE and the target remote UE. For example, SRB 0-3 corresponds to RB0-3. The remaining DRBs are established and allocated RB IDs between the source and target through the RRC signaling process before they are used.

[0210] Between the source remote UE and the relay UE (referred to as the first hop), the relay UE can multiplex the data from the same source remote UE to different target remote UEs to reduce the number of bearers that may appear in the first hop:

[0211] Each target remote UE is still distinguished by its own L2 ID, which needs to be recognizable by the source remote UE. For example, in the discovery process, the L2 IDs of each other are exchanged. The L2ID used here can be the same as the L2 ID used for PC5 communication between the target remote UE and the relay UE, or it can be different. If they are different, it means that the target remote UE has at least two L2 IDs, one of which is used for PC5 transmission with the relay UE, and the other L2 ID is used to identify itself during end-to-end communication between the target remote UE and the source remote UE. If there are two L2 IDs, the relay UE needs to store the corresponding relationship between the two L2 IDs for use in different scenarios.

[0212] And carry the corresponding RB ID to identify which bearer of which source remote UE, the principle is the same as above;

[0213] Optionally, to further reduce complexity and have the same adaptationlayer packet format on the first and second hops, you can also:

[0214] The first hop carries both the source remote UE L2 ID and the target remote UE L2 ID. The former identifies different source UEs, and the latter identifies different target UEs. The latter can also play a routing role in the multi-hop network.

[0215] In addition to the UE ID, an RB ID is also required to distinguish different bearers. The principle is the same as above.

[0216] Figure 5 The second schematic diagram of the remote terminal service identification method provided in the embodiment of the present application is executed by a network side device, and the method includes:

[0217] Step 500: receiving a first message sent by a relay terminal through a relay bearer channel;

[0218] In this embodiment, the network-side device serves as a peer communication device and receives a first message forwarded by the relay terminal through the relay bearer channel.

[0219] The data packet header of the first message carries the terminal identifier and / or bearer identifier of the first remote terminal.

[0220] The network-side device can distinguish the bearers from different remote UEs according to the UE ID and / or RB ID carried in the data packet header of the first message, thereby realizing identification of the service of the remote terminal remote UE.

[0221] In an embodiment of the present application, the services of different remote UEs are distinguished during the service multiplexing process of the remote UE, so that the relay terminal can multiplex different services of different remote terminals in the same transmission channel for transmission, thereby improving the transmission efficiency and providing the identifiability of the remote terminal services in end-to-end transmission at the same time, thereby ensuring the service quality of the remote terminal services and taking into account the overall efficiency, thereby ensuring the system efficiency while improving the user experience.

[0222] In some optional embodiments, the terminal identification includes one of the following:

[0223] PC5 link layer 2 identifier PC5 link L2 ID or some bits of the PC5 link L2 ID;

[0224] The unique index of the remote terminal in the relay terminal;

[0225] Unique index of the remote terminal in the network-side device.

[0226] For the relevant contents about the terminal identification, please refer to the relevant description in the aforementioned embodiment, which will not be repeated here.

[0227] In some optional embodiments, the bearer identifier includes one of the following:

[0228] End-to-end bearer identification of the remote terminal;

[0229] The label of the bearer corresponding to the remote terminal mapped to the same radio link control channel.

[0230] For the relevant contents about the bearer identification, please refer to the relevant description in the aforementioned embodiment, which will not be repeated here.

[0231] In some optional embodiments, the remote terminal service identification method further includes:

[0232] Sending radio bearer configuration information to the relay terminal;

[0233] The configuration information of the radio bearer carries a mapping relationship between the type of the radio bearer data and the radio link control channel.

[0234] In order to achieve bearer multiplexing, the network side equipment needs to configure corresponding radio link control channels for different types of radio bearer data. For example, configure the default relayed RLC channel for SRB0 messages and configure the corresponding RLC channel for non-SRB0 messages.

[0235] Optionally, the network side device sends configuration information of the radio bearer to the relay terminal; wherein the configuration information of the radio bearer carries a mapping relationship between the type of the radio bearer data and the radio link control channel.

[0236] In some optional embodiments, the adaptation layer protocol header of the first message carries a terminal identifier of the first remote terminal and / or a bearer identifier of the first remote terminal.

[0237] In some optional embodiments, the remote terminal service identification method further includes:

[0238] Receive an SRB0 message forwarded by a relay terminal, and determine identity information of a remote terminal that sends the SRB0 message;

[0239] A terminal identification index is allocated to the remote terminal that sends the SRB0 message, and the terminal identification index is sent to the relay terminal through a radio resource control RRC message or a UP process.

[0240] Optionally, the terminal identifier may also be a unique index allocated by the network-side device to the remote terminal.

[0241] The network receives the SRB0 message forwarded by the relay terminal, interprets the SRB0 message, and determines the identity information of the remote terminal that sends the SRB0 message.

[0242] Then, a terminal identification index is allocated to the remote terminal that sends the SRB0 message, and the terminal identification index is sent to the relay terminal through a radio resource control RRC message or a UP process.

[0243] Optionally, the sending the terminal identification index to the relay terminal through a radio resource control RRC message or a UP process includes:

[0244] Sending an RRC message to the relay terminal, where the RRC message carries the terminal identification index; or,

[0245] A control protocol data unit / first data packet is sent to the relay terminal through the UP process, and the control protocol data unit / first data packet carries the identity information of the remote terminal that sends the SRB0 message and the terminal identification index corresponding to the remote terminal that sends the SRB0 message.

[0246] In some optional embodiments, the remote terminal service identification method further includes:

[0247] A unique terminal identification index is assigned to each remote terminal within the coverage area.

[0248] In an embodiment of the present application, another feasible method for defining UE ID is provided, so that the length of UE ID can be between the complete L2 ID 24 bits and the unique index length in the relay, and a unique identifier in the cell is assigned to the remote UE, which is generally 2 bytes in length, to distinguish different remote UEs.

[0249] Since in the U2N scenario, both the remote UE and the relay UE are in a connected state and under the control of the network, the network-side device can assign a unique index within its jurisdiction to each remote UE for distinction and identification. The network-side device can configure the index through the control plane (CP) process or the user plane UP process, through the remote UE identity of the setup request and various notification methods of the configured index, to establish an association between the remote UE and the index for subsequent communication.

[0250] In the U2U scenario, since the relay UE has to transfer a lot of data and is likely to be in a connected state and scheduled by the network, it can obtain the association between the remote UE and the index from the network side device for subsequent communication. If the relay UE is not in a connected state or is offline, the index can only be determined by the relay UE itself.

[0251] In some optional embodiments, the remote terminal service identification method further includes:

[0252] A bearer label is allocated to each remote terminal mapped to the same radio link control channel.

[0253] It is understandable that in the U2N scenario, the network side device allocates a bearer number to each remote UE mapped to the same radio link control channel, and configures it to the relay UE through an RRC message. In the U2U scenario, if the relay UE is in a connected state, the relay UE will report the situation of each remote UE to the network, and the network will uniformly allocate the corresponding bearer number to each remote UE.

[0254] The embodiment of the present application provides a method for identifying remote UE services when bearer multiplexing is required in a secondary link relay architecture, which can enable relay UE operations to be performed more orderly, reduce the number of bearers and the complexity of scheduling transmission, and ensure the service experience of remote UE and system efficiency.

[0255] Figure 6 The third flow chart of the remote terminal service identification method provided in the embodiment of the present application is applied to the remote terminal, including:

[0256] Step 600: Receive a first message sent by a relay terminal through a relay bearer channel;

[0257] In this embodiment, the remote terminal serves as a peer communication device and receives a first message forwarded by the relay terminal through the relay bearer channel.

[0258] The data packet header of the first message carries the terminal identifier of the first remote terminal and / or the bearer identifier of the first remote terminal.

[0259] The remote device can distinguish the bearers from different remote UEs according to the UE ID and / or RB ID carried in the data packet header of the first message, thereby realizing identification of the service of the remote terminal remote UE.

[0260] Optionally, the terminal identifier includes one of the following:

[0261] PC5 link layer 2 identifier PC5 link L2 ID or some bits of the PC5 link L2 ID;

[0262] The unique index of the remote terminal in the relay terminal;

[0263] Unique index of the remote terminal in the network-side device.

[0264] For the relevant contents about the terminal identification, please refer to the relevant description in the aforementioned embodiment, which will not be repeated here.

[0265] Optionally, the bearer identifier includes one of the following:

[0266] End-to-end bearer identification of the remote terminal;

[0267] The label of the bearer corresponding to the remote terminal mapped to the same radio link control channel.

[0268] For the relevant contents about the bearer identification, please refer to the relevant description in the aforementioned embodiment, which will not be repeated here.

[0269] Optionally, the adaptation layer protocol header of the first message carries a terminal identifier and / or a bearer identifier of the first remote terminal.

[0270] The embodiment of the present application provides a method for identifying remote UE services when bearer multiplexing is required in a secondary link relay architecture, which can enable relay UE operations to be performed more orderly, reduce the number of bearers and the complexity of scheduling transmission, and ensure the service experience of remote UE and system efficiency.

[0271] It should be noted that the execution subject of the remote terminal service identification method provided in the embodiment of the present application may be a remote terminal service identification device, or a control module in the remote terminal service identification device for executing the remote terminal service identification method. In the embodiment of the present application, the remote terminal service identification device executing the remote terminal service identification method is taken as an example to illustrate the remote terminal service identification device provided in the embodiment of the present application.

[0272] Figure 7 One of the structural schematic diagrams of the remote terminal service identification device provided in the embodiment of the present application includes: a first receiving unit 710, a first processing unit 720 and a first sending unit 730, wherein:

[0273] The first receiving unit 710 is configured to receive a first message sent by a first remote terminal;

[0274] A first processing unit 720 is configured to determine a relay bearer channel for forwarding the first message;

[0275] A first sending unit 730 is configured to forward the first message to a peer communication device through the intermediate bearer channel, wherein a data packet header of the first message carries a terminal identifier and / or a bearer identifier of the first remote terminal;

[0276] The opposite-end communication device is a network-side device, a next-hop relay terminal or a second remote terminal.

[0277] In an embodiment of the present application, the services of different remote UEs are distinguished during the service multiplexing process of the remote UE, so that the relay terminal can multiplex different services of different remote terminals in the same transmission channel for transmission, thereby improving the transmission efficiency and providing the identifiability of the remote terminal services in end-to-end transmission at the same time, thereby ensuring the service quality of the remote terminal services and taking into account the overall efficiency, thereby ensuring the system efficiency while improving the user experience.

[0278] Optionally, the first processing unit 720 is configured to:

[0279] Determine the type of the first message based on the logical channel identifier of the PC5 interface corresponding to the first message, the SRB0 identifier of the first message, or the end-to-end bearer identifier of the first remote terminal;

[0280] In a case where the type of the first message is an SRB0 message, determining that the intermediate bearer channel used to forward the first message is a first default radio link control channel; or,

[0281] When the type of the first message is not an SRB0 message, based on the mapping relationship between the type of wireless bearer data and the wireless link control channel, the intermediate bearer channel used to forward the first message is determined to be a wireless link control channel having a mapping relationship with the type of the first message.

[0282] Optionally, the first processing unit 720 is further configured to:

[0283] When the type of the first message is not an SRB0 message and a radio link control channel having a mapping relationship with the type of the first message does not exist, determining that the relay bearer channel used to forward the first message is a second default radio link control channel configured on the network side;

[0284] The second default radio link control channel is the same as or different from the first default relay radio link control channel.

[0285] Optionally, the terminal identifier includes one of the following:

[0286] PC5 link layer 2 identifier PC5 link L2 ID or some bits of the PC5 link L2 ID;

[0287] The unique index of the remote terminal in the relay terminal;

[0288] Unique index of the remote terminal in the network-side device.

[0289] Optionally, the bearer identifier includes one of the following:

[0290] End-to-end bearer identification;

[0291] The label of the bearer corresponding to the remote terminal mapped to the same radio link control channel.

[0292] Optionally, the method further includes a first configuration unit, configured to:

[0293] allocating a terminal identification index to each remote terminal connected to the relay terminal; or,

[0294] A terminal identification index is allocated to each remote terminal mapped to the same radio link control channel.

[0295] Optionally, also include:

[0296] The second sending unit is used to send the terminal identification index to the opposite-end communication device of the remote terminal corresponding to the terminal identification index through a radio resource control RRC message or a UP process.

[0297] Optionally, also include:

[0298] The second receiving unit is used to receive a radio resource control RRC message sent by a network side device, where the RRC message carries a terminal identification index allocated by the network side device to a remote terminal that has sent an SRB0 message.

[0299] Optionally, also include:

[0300] A third receiving unit is used to receive a control protocol data unit / first data packet sent by a network side device, where the control protocol data unit / first data packet carries the identity information of the remote terminal that sends the SRB0 message and the terminal identification index allocated by the network side device to the remote terminal that sends the SRB0 message;

[0301] The second processing unit is configured to determine the remote terminal corresponding to the terminal identification index according to the identity information.

[0302] Optionally, also include:

[0303] The second configuration unit is used to allocate a bearer label to each remote terminal mapped to the same radio link control channel.

[0304] Optionally, also include:

[0305] A fourth receiving unit, configured to receive a second message sent by the opposite communication device;

[0306] The third processing unit is used to forward the second message to the corresponding remote terminal based on the terminal identifier and / or bearer identifier carried in the data packet header of the second message.

[0307] Optionally, before receiving the first message sent by the first remote terminal, the method further includes:

[0308] The fourth processing unit is used to interact with the first remote terminal through the PC5 interface to determine whether the relay terminal has the ability to transfer the first remote terminal service when the first remote terminal meets the conditions for establishing relay communication and the link quality between the relay terminal and the first remote terminal and the link quality between the relay terminal and the first communication device meet the conditions for establishing relay communication.

[0309] Optionally, the adaptation layer protocol header of the first message carries a terminal identifier of the first remote terminal and / or a bearer identifier of the first remote terminal.

[0310] In an embodiment of the present application, a relay terminal or a network-side device allocates a terminal identification index and / or a bearer number to a remote UE, and distinguishes services of different remote UEs during service multiplexing of the remote UE, so that the relay terminal multiplexes different services of different remote terminals in the same transmission channel for transmission, thereby improving transmission efficiency and reducing resource overhead.

[0311] The remote terminal service identification device in the embodiment of the present application can be a device, or a component, integrated circuit, or chip in a terminal. The device can be a mobile terminal or a non-mobile terminal. Exemplarily, the mobile terminal can include but is not limited to the types of remote terminals 11 / relay terminals 13 listed above, and the non-mobile terminal can be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television, TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.

[0312] The remote terminal service identification device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.

[0313] The remote terminal service identification device provided in the embodiment of the present application can achieve Figure 3 to Figure 4 The various processes implemented by the method embodiment and achieving the same technical effect are not described here to avoid repetition.

[0314] Figure 8 The second structural diagram of the remote terminal service identification device provided in the embodiment of the present application includes:

[0315] A fifth receiving unit 810, configured to receive a first message sent by the relay terminal through the relay bearer channel;

[0316] The data packet header of the first message carries the terminal identifier and / or bearer identifier of the first remote terminal.

[0317] Optionally, the terminal identifier includes one of the following:

[0318] PC5 link layer 2 identifier PC5 link L2 ID or some bits of the PC5 link L2 ID;

[0319] The unique index of the remote terminal in the relay terminal;

[0320] Unique index of the remote terminal in the network-side device.

[0321] Optionally, the bearer identifier includes one of the following:

[0322] End-to-end bearer identification of the remote terminal;

[0323] The label of the bearer corresponding to the remote terminal mapped to the same radio link control channel.

[0324] Optionally, also include:

[0325] A third sending unit, configured to send the configuration information of the radio bearer to the relay terminal;

[0326] The configuration information of the radio bearer carries a mapping relationship between the type of the radio bearer data and the radio link control channel.

[0327] Optionally, the adaptation layer protocol header of the first message carries a terminal identifier of the first remote terminal and / or a bearer identifier of the first remote terminal.

[0328] Optionally, also include:

[0329] a fifth processing unit, configured to receive the SRB0 message forwarded by the relay terminal, and determine the identity information of the remote terminal that sends the SRB0 message;

[0330] A third configuration unit, configured to allocate a terminal identification index to a remote terminal that sends the SRB0 message;

[0331] The fourth sending unit is used to send the terminal identification index to the relay terminal through a radio resource control RRC message or a UP process.

[0332] Optionally, the fourth sending unit is used to:

[0333] Sending an RRC message to the relay terminal, where the RRC message carries the terminal identification index; or,

[0334] A control protocol data unit / first data packet is sent to the relay terminal through the UP process, and the control protocol data unit / first data packet carries the identity information of the remote terminal that sends the SRB0 message and the terminal identification index corresponding to the remote terminal that sends the SRB0 message.

[0335] Optionally, also include:

[0336] The fourth configuration unit is used to allocate a unique terminal identification index to each remote terminal within the coverage area.

[0337] Optionally, also include:

[0338] The fifth configuration unit is used to allocate a bearer label to each remote terminal mapped to the same radio link control channel.

[0339] In an embodiment of the present application, the services of different remote UEs are distinguished during the service multiplexing process of the remote UE, so that the relay terminal can multiplex different services of different remote terminals in the same transmission channel for transmission, thereby improving the transmission efficiency and providing the identifiability of the remote terminal services in end-to-end transmission at the same time, thereby ensuring the service quality of the remote terminal services and taking into account the overall efficiency, thereby ensuring the system efficiency while improving the user experience.

[0340] The remote terminal service identification device in the embodiment of the present application can be a device, or a component, integrated circuit, or chip in a terminal. The device can be a mobile terminal or a non-mobile terminal. Exemplarily, the mobile terminal can include but is not limited to the types of remote terminals 11 / relay terminals 13 listed above, and the non-mobile terminal can be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television, TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.

[0341] The remote terminal service identification device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.

[0342] The remote terminal service identification device provided in the embodiment of the present application can achieve Figure 5 The various processes implemented by the method embodiment and achieving the same technical effect are not described here to avoid repetition.

[0343] Fig. 9 The third structural diagram of the remote terminal service identification device provided in the embodiment of the present application includes:

[0344] A sixth receiving unit 910, configured to receive a first message sent by the relay terminal through the relay bearer channel;

[0345] The data packet header of the first message carries the terminal identifier of the first remote terminal and / or the bearer identifier of the first remote terminal.

[0346] Optionally, the terminal identifier includes one of the following:

[0347] PC5 link layer 2 identifier PC5 link L2 ID or some bits of the PC5 link L2 ID;

[0348] The unique index of the remote terminal in the relay terminal;

[0349] Unique index of the remote terminal in the network-side device.

[0350] Optionally, the bearer identifier includes one of the following:

[0351] End-to-end bearer identification of the remote terminal;

[0352] The label of the bearer corresponding to the remote terminal mapped to the same radio link control channel.

[0353] Optionally, the adaptation layer protocol header of the first message carries a terminal identifier and / or a bearer identifier of the first remote terminal.

[0354] In an embodiment of the present application, the services of different remote UEs are distinguished during the service multiplexing process of the remote UE, so that the relay terminal can multiplex different services of different remote terminals in the same transmission channel for transmission, thereby improving the transmission efficiency and providing the identifiability of the remote terminal services in end-to-end transmission at the same time, thereby ensuring the service quality of the remote terminal services and taking into account the overall efficiency, thereby ensuring the system efficiency while improving the user experience.

[0355] The remote terminal service identification device in the embodiment of the present application can be a device, or a component, integrated circuit, or chip in a terminal. The device can be a mobile terminal or a non-mobile terminal. Exemplarily, the mobile terminal can include but is not limited to the types of remote terminals 11 / relay terminals 13 listed above, and the non-mobile terminal can be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television, TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.

[0356] The remote terminal service identification device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.

[0357] The remote terminal service identification device provided in the embodiment of the present application can achieve Figure 6 The various processes implemented by the method embodiment and achieving the same technical effect are not described here to avoid repetition.

[0358] Optional, such as Fig.10 As shown, the embodiment of the present application also provides a communication device 1000, including a processor 1001, a memory 1002, and a program or instruction stored in the memory 1002 and executable on the processor 1001. For example, when the communication device 1000 is a terminal, the program or instruction is executed by the processor 1001 to implement the various processes of the above-mentioned remote terminal service identification method embodiment, and can achieve the same technical effect. When the communication device 1000 is a network side device, the program or instruction is executed by the processor 1001 to implement the various processes of the above-mentioned remote terminal service identification method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0359] Fig.11 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.

[0360] The terminal 1100 includes but is not limited to: a radio frequency unit 1101, a network module 1102, an audio output unit 1103, an input unit 1104, a sensor 1105, a display unit 1106, a user input unit 1107, an interface unit 1108, a memory 1109, and a processor 1110 and other components.

[0361] Those skilled in the art will appreciate that the terminal 1100 may also include a power source (such as a battery) for supplying power to each component, and the power source may be logically connected to the processor 1110 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Fig.11 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0362] It should be understood that in the embodiment of the present application, the input unit 1104 may include a graphics processor (Graphics Processing Unit, GPU) 11041 and a microphone 11042, and the graphics processor 11041 processes the image data of the static picture or video obtained by the image capture device (such as a camera) in the video capture mode or the image capture mode. The display unit 1106 may include a display panel 11061, and the display panel 11061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1107 includes a touch panel 11071 and other input devices 11072. The touch panel 11071 is also called a touch screen. The touch panel 11071 may include two parts: a touch detection device and a touch controller. Other input devices 11072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0363] In the embodiment of the present application, the radio frequency unit 1101 receives downlink data from the network side device and sends it to the processor 1110 for processing; in addition, the uplink data is sent to the network side device. Generally, the radio frequency unit 1101 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0364] The memory 1109 can be used to store software programs or instructions and various data. The memory 1109 can mainly include a program or instruction storage area and a data storage area, wherein the program or instruction storage area can store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 1109 can include a high-speed random access memory, and can also include a non-volatile memory, wherein the non-volatile memory can be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or a flash memory. For example, at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device.

[0365] The processor 1110 may include one or more processing units; optionally, the processor 1110 may integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, and application programs or instructions, etc., and the modem processor mainly processes wireless communications, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 1110.

[0366] The radio frequency unit 1101 is configured to receive a first message sent by a first remote terminal;

[0367] Processor 1110, configured to determine a relay bearer channel for forwarding the first message;

[0368] Forwarding the first message to the opposite communication device through the intermediate bearer channel, wherein the data packet header of the first message carries the terminal identifier and / or the bearer identifier of the first remote terminal;

[0369] The opposite-end communication device is a network-side device, a next-hop relay terminal or a second remote terminal.

[0370] In an embodiment of the present application, the services of different remote UEs are distinguished during the service multiplexing process of the remote UE, so that the relay terminal can multiplex different services of different remote terminals in the same transmission channel for transmission, thereby improving the transmission efficiency and providing the identifiability of the remote terminal services in end-to-end transmission at the same time, thereby ensuring the service quality of the remote terminal services and taking into account the overall efficiency, thereby ensuring the system efficiency while improving the user experience.

[0371] Optionally, the processor 1110 is configured to:

[0372] Determine the type of the first message based on the logical channel identifier of the PC5 interface corresponding to the first message, the SRB0 identifier of the first message, or the end-to-end bearer identifier of the first remote terminal;

[0373] In a case where the type of the first message is an SRB0 message, determining that the intermediate bearer channel used to forward the first message is a first default radio link control channel; or,

[0374] When the type of the first message is not an SRB0 message, based on the mapping relationship between the type of wireless bearer data and the wireless link control channel, the intermediate bearer channel used to forward the first message is determined to be a wireless link control channel having a mapping relationship with the type of the first message.

[0375] Optionally, the processor 1110 is further configured to:

[0376] When the type of the first message is not an SRB0 message and a radio link control channel having a mapping relationship with the type of the first message does not exist, determining that the relay bearer channel used to forward the first message is a second default radio link control channel configured on the network side;

[0377] The second default radio link control channel is the same as or different from the first default relay radio link control channel.

[0378] Optionally, the terminal identifier includes one of the following:

[0379] PC5 link L2 ID;

[0380] Some bits of the PC5 link L2 ID;

[0381] The unique index of the remote terminal in the relay terminal;

[0382] Unique index of the remote terminal in the network-side device.

[0383] Optionally, the bearer identifier includes one of the following:

[0384] End-to-end bearer identification;

[0385] The label of the bearer corresponding to the remote terminal mapped to the same radio link control channel.

[0386] Optionally, the processor 1110 is further configured to:

[0387] allocating a terminal identification index to each remote terminal connected to the relay terminal; or,

[0388] A terminal identification index is allocated to each remote terminal mapped to the same radio link control channel.

[0389] Optionally, the processor 1110 is further configured to:

[0390] The terminal identification index is sent to the opposite-end communication device of the remote terminal corresponding to the terminal identification index through a radio resource control RRC message or a UP process.

[0391] Optionally, the processor 1110 is further configured to:

[0392] A radio resource control RRC message sent by a network side device is received, where the RRC message carries a terminal identification index allocated by the network side device to a remote terminal that has sent an SRB0 message.

[0393] Optionally, the processor 110 is further configured to:

[0394] Receive a control protocol data unit / first data packet sent by a network side device, where the control protocol data unit / first data packet carries identity information of a remote terminal that sends an SRB0 message and a terminal identification index allocated by the network side device to the remote terminal that sends the SRB0 message;

[0395] The remote terminal corresponding to the terminal identification index is determined according to the identity information.

[0396] Optionally, the processor 1110 is further configured to:

[0397] A bearer label is allocated to each remote terminal mapped to the same radio link control channel.

[0398] Optionally, the processor 1110 is further configured to:

[0399] Receiving a second message sent by the opposite communication device;

[0400] Based on the terminal identifier and / or bearer identifier carried in the data packet header of the second message, the second message is forwarded to the corresponding remote terminal.

[0401] Optionally, the processor 1110 is further configured to:

[0402] When the first remote terminal meets the conditions for establishing relay communication, and the link quality between the relay terminal and the first remote terminal and the link quality between the relay terminal and the first communication device meet the conditions for establishing relay communication, interact with the first remote terminal through the PC5 interface to determine whether the relay terminal has the ability to transfer the first remote terminal service.

[0403] Optionally, the adaptation layer protocol header of the first message carries a terminal identifier of the first remote terminal and / or a bearer identifier of the first remote terminal.

[0404] In an embodiment of the present application, a relay terminal or a network-side device allocates a terminal identification index and / or a bearer number to a remote UE, and distinguishes services of different remote UEs during service multiplexing of the remote UE, so that the relay terminal multiplexes different services of different remote terminals in the same transmission channel for transmission, thereby improving transmission efficiency and reducing resource overhead.

[0405] In one embodiment, optionally, the radio frequency unit 1101 is configured to receive a first message sent by the relay terminal through a relay bearer channel;

[0406] The data packet header of the first message carries the terminal identifier of the first remote terminal and / or the bearer identifier of the first remote terminal.

[0407] Optionally, the terminal identifier includes one of the following:

[0408] PC5 link layer 2 identifier PC5 link L2 ID or some bits of the PC5 link L2 ID;

[0409] The unique index of the remote terminal in the relay terminal;

[0410] Unique index of the remote terminal in the network-side device.

[0411] Optionally, the bearer identifier includes one of the following:

[0412] End-to-end bearer identification of the remote terminal;

[0413] The label of the bearer corresponding to the remote terminal mapped to the same radio link control channel.

[0414] Optionally, the adaptation layer protocol header of the first message carries a terminal identifier and / or a bearer identifier of the first remote terminal.

[0415] The embodiment of the present application provides a method for identifying remote UE services when bearer multiplexing is required in a secondary link relay architecture, which can enable relay UE operations to be performed more orderly, reduce the number of bearers and the complexity of scheduling transmission, and ensure the service experience of remote UE and system efficiency.

[0416] The present application embodiment also provides a network side device. Fig.12 As shown, the network device 1200 includes: an antenna 1201, a radio frequency device 1202, and a baseband device 1203. The antenna 1201 is connected to the radio frequency device 1202. In the uplink direction, the radio frequency device 1202 receives information through the antenna 1201 and sends the received information to the baseband device 1203 for processing. In the downlink direction, the baseband device 1203 processes the information to be sent and sends it to the radio frequency device 1202, and the radio frequency device 1202 processes the received information and sends it out through the antenna 1201.

[0417] The frequency band processing device may be located in the baseband device 1203 . The method performed by the network-side device in the above embodiment may be implemented in the baseband device 1203 . The baseband device 1203 includes a processor 1204 and a memory 1205 .

[0418] The baseband device 1203 may include, for example, at least one baseband board on which a plurality of chips are arranged. Fig.12 As shown, one of the chips is, for example, a processor 1204, which is connected to a memory 1205 to call a program in the memory 1205 to execute the network device operations shown in the above method embodiment.

[0419] The baseband device 1203 may further include a network interface 1206 for exchanging information with the radio frequency device 1202 . The interface may be, for example, a common public radio interface (CPRI for short).

[0420] Specifically, the network side device of the embodiment of the present invention further includes: instructions or programs stored in the memory 1205 and executable on the processor 1204, and the processor 1204 calls the instructions or programs in the memory 1205 to execute Figure 8 The methods executed by the modules shown achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.

[0421] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the above-mentioned remote terminal service identification method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0422] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0423] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run network-side device programs or instructions to implement the various processes of the above-mentioned remote terminal service identification method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0424] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0425] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0426] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0427] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

1. A remote terminal service identification method, applied to a relay terminal, characterized in that: include: Receiving a first message sent by a first remote terminal; The first message does not include a user equipment identifier UE ID and a bearer identifier of the first remote terminal; determining a relay bearer channel for forwarding the first message; Sending a second message to the network side device through the relay bearer channel, where the second message carries the UE ID and the bearer identifier of the first remote terminal; The bearer identifier is used to determine that the message type of the second message is signaling radio bearer SRB 0.

2. The remote terminal service identification method according to claim 1, characterized in that: The determining the relay bearer channel corresponding to the first message includes: Determining a type of the first message based on a logical channel identifier of the PC5 interface corresponding to the first message; According to whether the type of the first message is SRB 0, a relay radio link control channel relay RLC channel used to forward the first message is determined.

3. The remote terminal service identification method according to claim 1, characterized in that: The first message and the second message are both radio resource control setup request RRC Setup request messages.

4. The remote terminal service identification method according to claim 1, characterized in that: The UE ID includes one of the following: A unique index of the first remote terminal in the relay terminal; The unique index of the first remote terminal in the network side device.

5. The remote terminal service identification method according to claim 1, characterized in that: Also includes: Receive an RRC Setup message sent by the network side device, where the RRC Setup message carries the UE ID allocated by the network side device to the first remote terminal.

6. The remote terminal service identification method according to any one of claims 1 to 5, characterized in that: The adaptation layer protocol header of the second message carries the UE ID and bearer identifier of the first remote terminal.

7. A remote terminal service identification method, applied to a network side device, characterized in that: include: receiving a second message sent by the relay terminal through the relay bearer channel; The second message carries a user equipment identifier UEID and a bearer identifier of the first remote terminal; The bearer identifier is used to determine that the message type of the second message is signaling radio bearer SRB 0.

8. The remote terminal service identification method according to claim 7, characterized in that: The UE ID includes one of the following: A unique index of the first remote terminal in the relay terminal; The unique index of the first remote terminal in the network side device.

9. A remote terminal service identification device, applied to a relay terminal, characterized in that: include: A first receiving unit, configured to receive a first message sent by a first remote terminal; The first message does not include a user equipment identifier UEID and a bearer identifier of the first remote terminal; A first processing unit, configured to determine a relay bearer channel for forwarding the first message; A first sending unit, configured to send a second message to a network side device through the relay bearer channel, wherein the second message carries a UEID and a bearer identifier of the first remote terminal; The bearer identifier is used to determine that the message type of the second message is signaling radio bearer SRB 0.

10. The remote terminal service identification device according to claim 9, characterized in that: The first processing unit is configured to: Determining a type of the first message based on a logical channel identifier of the PC5 interface corresponding to the first message; According to whether the type of the first message is SRB 0, a relay radio link control channel relay RLC channel used to forward the first message is determined.

11. The remote terminal service identification device according to claim 9, characterized in that: The first message and the second message are both radio resource control setup request RRC Setup request messages.

12. The remote terminal service identification device according to claim 9, characterized in that: The UEID includes one of the following: A unique index of the first remote terminal in the relay terminal; The unique index of the first remote terminal in the network side device.

13. The remote terminal service identification device according to claim 9, characterized in that: The first receiving unit is further used for: Receive an RRC Setup message sent by a network side device, where the RRC Setup message carries the UE ID allocated by the network side device to the first remote terminal.

14. The remote terminal service identification device according to any one of claims 9 to 13, characterized in that: The adaptation layer protocol header of the second message carries the UE ID and bearer identifier of the first remote terminal.

15. A remote terminal service identification device, applied to a network side device, characterized in that: include: A fifth receiving unit, configured to receive a second message sent by the relay terminal through the relay bearer channel; The second message carries a user equipment identifier UE ID and a bearer identifier of the first remote terminal; The bearer identifier is used to determine that the message type of the second message is signaling radio bearer SRB 0.

16. The remote terminal service identification device according to claim 15, characterized in that: The UE ID includes one of the following: A unique index of the first remote terminal in the relay terminal; The unique index of the first remote terminal in the network side device.

17. A terminal, characterized in that: It includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the remote terminal service identification method as described in any one of claims 1 to 6.

18. A network side device, characterized in that: It comprises a processor, a memory and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the remote terminal service identification method as claimed in claim 7 or 8.

19. A readable storage medium, characterized in that: The readable storage medium stores a program or instruction, and when the program or instruction is executed by the processor, it implements the steps of the remote terminal service identification method as described in any one of claims 1-6, or implements the steps of the remote terminal service identification method as described in claim 7 or 8.

Images