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

Abstract

The present application discloses a remote terminal service identification method, device, equipment and storage medium, which belongs to the field of communication technology. The method includes: receiving a first message sent by a first remote terminal; determining an intermediate bearer channel for forwarding the first message; forwarding the first message to a peer communication device through the intermediate bearer channel, wherein the data packet header of the first message carries a terminal identifier and / or a bearer identifier of the first remote terminal; wherein the peer communication device is a network side device, a next-hop relay terminal or a second remote terminal. In the embodiment of the present application, the services of different remote terminals are distinguished during the service multiplexing process of the remote terminal, 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 considering the overall efficiency, the system efficiency is guaranteed while improving the user experience.

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] Starting with Release 12, the Long Term Evolution (LTE) system supports sidelinks (also known as secondary links or side links), enabling direct data transmission between user equipment (UEs) without requiring network-side equipment. In a typical sidelink relay scenario, a remote UE (remote UE) establishes a sidelink link with a relay UE, which then forwards its data to and from the base station. In this scenario, the relay UE acts as a data relay for data transmission between the remote UE and the base station.

[0003] In related technologies, an adaptation layer exists beneath the Uu Packet Data Convergence Protocol (Uu PDCP) layer on the remote terminal's Uu interface. This layer is primarily used to multiplex services for remote UEs, multiplexing services from multiple remote UEs into a single Uu Radio Bearer (RB) for transmission. However, related technologies only outline the basic functions of the adaptation layer and fail to provide a solution for how the adaptation layer distinguishes services from different remote UEs during service multiplexing. Consequently, the adaptation layer currently does not function properly. Summary of the Invention

[0004] The purpose of the embodiments of the present application is to provide a remote terminal service identification method, apparatus, device 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. 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 bearer identifier of the first remote terminal;

[0010] The opposite-end 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. 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 and includes:

[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 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 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;

[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 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 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 runnable 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 the eighth aspect, a network side device is provided, which includes a processor, a memory, and a program or instruction stored in the memory and runnable on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the second aspect are implemented.

[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, which includes a processor and a communication interface, the communication interface and the processor are coupled, 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, thereby ensuring the service quality of the remote terminal services and taking into account the overall efficiency, thereby improving the user experience while ensuring the system efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0034] Figure 2 Schematic diagram of the L2 relay protocol stack architecture in related technologies;

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

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

[0037] Figure 5 Schematic diagram 2 of the remote terminal service identification method provided in an embodiment of the present application;

[0038] Figure 6 Flowchart 3 of the remote terminal service identification method provided in the embodiment of the present application;

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

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

[0041] Figure 9 The third structural diagram of the remote terminal service identification device provided in the embodiment of the present application;

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

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

[0044] Figure 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 this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of them. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0046] The terms "first," "second," and the like in the specification and claims of this application are used to distinguish similar objects, and are not used to describe a specific order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate, so that the embodiments of this application can be implemented in an order other than that illustrated or described herein, and that the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects; for example, the first object can be one or more. In addition, the term "and / or" in the specification and claims refers to at least one of the connected objects, and the character " / " generally indicates that the objects connected 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 technology described 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 description, although these technologies can also be applied to applications other than NR system applications, such as 6th generation (6G) systems. th Generation, 6G) communication system.

[0048] Figure 1The 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 referred to as 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 (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 wearable devices include: bracelets, headphones, 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, where the base station can be referred to as a node B, an evolved node B, an access point, a base transceiver station (BTS), a radio base station, a radio transceiver, a basic service set (BSS), an 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 (TRP) or other appropriate terms 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 following describes in detail the relay terminal-based switching method, apparatus, device, and storage medium provided in the embodiments of the present application through specific embodiments and their application scenarios in conjunction with the accompanying drawings.

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

[0051] Figure 2 This is a schematic diagram of the L2 relay protocol stack architecture in the related technology. Figure 2The diagram shows an L2 relay protocol stack used by a remote terminal when communicating with a network-side device through a relay terminal (i.e., 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] Under the Uu PDCP protocol stack of the relay terminal, there is an adaptation layer (Adaptation Layer), such as Figure 2 The ADAPT (Adaptation Layer) in the protocol is a new protocol layer that mainly multiplexes services of remote UEs. The services of multiple remote UEs can be multiplexed into one Uu RB (Radio Bearer) for transmission.

[0054] Because relay terminals also transmit data, the adaptation layer needs to distinguish between data from relay terminals and remote terminals, or between data from different remote terminals. Specifically, the adaptation layer logical entity needs to distinguish whether data is from / to a remote terminal or relay terminal, as well as which bearer the data belongs to. Below the adaptation protocol layer are 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, an adaptation layer may also be provided on the PC5 interface, that is, between the remote UE and the relay UE, for service multiplexing.

[0056] The existing technology only proposes the basic functions of the adaptation layer, but does not provide a solution for how the adaptation layer can differentiate services of different remote UEs, determine the UE ID content, or allocate UE IDs. Therefore, the adaptation layer is currently unable to function.

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

[0058] Step 300: Receive 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, or may 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 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.

[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 based on 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-end 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 can be a U2N (UE to NW) scenario, that is, Remote UE<–>relay UE<–>NW, where multiple hops are possible, that is, there are multiple serial relay UEs, where the relay UE closest to the remote UE is recorded as the access relay UE, and the relay UE connected to the NW is recorded as the root relay UE. 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, if bearer multiplexing is required, the UE ID and / or RB ID can be used to distinguish the remote UE and the bearer.

[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 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, UE ID and / or RB ID can be used to distinguish the remote UE and the bearer.

[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, thereby ensuring the service quality of the remote terminal services and taking into account the overall efficiency, thereby improving the user experience while ensuring the system efficiency.

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

[0077] Determining a type of the first message based on a logical channel identifier of the 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;

[0078] In a case where the type of the first message is an SRB0 message, determining that the relay 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 or 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 configured to carry the SRB0 message. Therefore, in the embodiment of the present application, the types of first messages are divided into two categories: SRB0 messages and non-SRB0 messages.

[0082] In order to implement bearer multiplexing, the network-side device needs to configure a 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 the first default radio link control channel.

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

[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 are mapped one-to-one with PC5 RBs 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 This is a schematic diagram of two UEs provided in an embodiment of the present application being connected to a network via a relay UE at the same time. Figure 4 As shown in Figure 1, on the PC5 interface, legacy PC5 SRBs, PC5 DRBs, RLC channels for Uu SRBs, and RLC channels for Uu DRBs may be present between each remote UE and relay UE. Each type of bearer can be an independent channel, making it easier for 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 and the extended logical channel.

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

[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 the 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, the relay bearer channel for forwarding 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 for 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 communication between the first remote terminal and the network side, for example, remote UE Uu SRB0, its RB ID = 0, remote UE SRB1, its RB ID = 1, remote UESRB2, its RB ID = 2, and the remaining DRBs are configured and allocated 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 radio 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 relay 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 the multiplexing of different services of different remote terminals in the same transmission channel, thereby improving the 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 when the remote UE and the relay UE communicate on the PC5 interface, and the length is 24 bits.

[0117] Because the PC5 link L2 ID is the same ID used in existing PC5 communications, it can uniquely identify the UE within a certain range and is relatively convenient to use. However, the disadvantage is that it is expensive, as each UE requires 24 bits for identification and differentiation.

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

[0119] The main purpose of the UE ID is to distinguish different remote UEs connected to the same relay UE, or to distinguish different remote UEs mapped to the same radio link control channel. Therefore, other definition 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] To reduce overhead, in one embodiment, the UE ID is defined as the number / index of all remote UEs connected to the same relay UE. The relay UE assigns a terminal identification index to each remote terminal connected to the relay UE. Each remote terminal corresponds to a unique terminal identification index.

[0125] Taking the U2N architecture as an example, a relay UE has limited processing capabilities, and therefore an upper limit on the number of UEs it can simultaneously serve. For example, let this upper limit be N. The index of the remote UE communicating with the network through this relay UE can be in the interval [0, N-1], with each index uniquely identifying a remote UE. Within the relay UE, the correspondence between the remote UE index and the actual L2 ID is stored, enabling correct communication. The NW, on the other hand, needs to store the mapping between the UE identity carried in RRC signaling and the remote UE index to correctly transmit, 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 allocating a terminal identification index to the remote terminal, the relay terminal UE sends 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 an UP process.

[0130] For example, when the first remote UE connects to a relay UE, the relay UE can assign it UEindex=0 and send the remote UE's SRB0 message RRC Setup request to the network using UE index=0 and RB ID. After receiving the message, the network-side device associates the UE identity in the setup message with the 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 the message, 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] Because the network has no prior knowledge of the remote UE when its first message is an SRB0 message, all remote UEs connected to the relay UE use a special Uu channel. This Uu RLC channel does not carry any remote UE ID or RB ID information, that is, it lacks an adaptation layer header. All remote UE SRB0 messages are transmitted here without differentiation. Upon receiving the message, the network interprets the message to determine the UE's identity and assigns the UE a unique UE index within 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 of the index 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 the 40 bits therein, can be used to identify the remote UE. Since the RRC setup request message contains the UE identity, the network side instructs 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 found out by comparison to which remote UE the index is assigned, and the L2 ID of the remote UE is subsequently associated with the index and stored for subsequent relay 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 assigned by the network-side device to the remote terminal that sends the SRB0 message;

[0139] Determine the remote terminal corresponding to the terminal identification index according to the identity information.

[0140] The network-side device informs the relay UE about the index allocation through the User Plane (UP) process. The specific method is to use the UP control protocol data unit control PDU, 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 carrying 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 remote UEs only requires a few bits, not more than one byte, thus greatly saving overhead.

[0144] It should be noted that in a U2U architecture, a similar approach can 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 number of the bearer corresponding to the remote terminal mapped to the same radio link control channel.

[0148] In some optional embodiments, the bearer identifier 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] The current end-to-end bearer support limit is 32, meaning that an RB ID requires 5 bits to identify an end-to-end bearer. However, the number of RBs that can be multiplexed within a remote UE into the same large transmission channel is limited, and the required QoS is the same or similar, for example, a maximum of 4 RBs. Therefore, the RB ID length 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] This means that the free 32-bit traditional end-to-end RB ID is mapped to index y of RLC channel x. The decision is made based on the principle of equal or similar QoS, selecting the corresponding RLC channel. The RBs mapped to the same RLC channel are then sorted within the group to see if any other RBs are mapped to the same RLC channel.

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

[0156] For signaling radio bearers, since the number of Uu SRBs (for U2N scenarios) and PC5 SRBs (for 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 pre-configured, 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 number 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 UEs 2, 3, and 4 can be multiplexed between Remote UE 1 and relay UE, and the allocated bearer numbers can 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. Therefore, the allocated bearer labels can 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 here.

[0164] In an embodiment of the present application, the relay terminal or the network-side device assigns a terminal identification index and / or a bearer number to the remote UE, and distinguishes the services of different remote UEs during the service multiplexing process 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 the 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 is understandable 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, if the remote UE is at the cell edge and its RSRP is lower than a network-configured threshold, it cannot communicate directly with the NW. In this case, the relay UE needs to forward its data to the network. 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 the 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 the terminal identifier of the first remote terminal and / or the 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 in the adaptation layer and included in the adaptation layer header.

[0176] However, 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, this article uses the L2 Remote UE<–>Relay UE<–>NW scenario as an example to explain how to use UE IDs and RB IDs to distinguish the bearers of different remote UEs, thereby enabling normal relay communication.

[0179] First, regarding the meaning and values ​​of UE ID and RB ID, this example adopts the following principles:

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

[0181] The following describes how the remote UE establishes L2 relay U2N communication and how bearer multiplexing is performed between the relay and the 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, if the remote UE is at the cell edge and its RSRP is lower than a network-configured threshold, it cannot communicate directly with the NW. In this case, the remote UE needs to transfer its data to the network via a relay UE.

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

[0185] The PC5 link quality between the remote UE and the relay UE also needs to meet a certain threshold, that is, the PC5 RSRP (Reference Signal Receiving Power) must be 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 the 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. For example, a default relayed RLC channel needs to be configured to carry at least 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. In addition, 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 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, and 11-13 are other relayed RLC channels, which carry data of different QoS of other remote UEs with configured mapping relationship.

[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 this first message. The adaptation header of the data packet carries the remote UE L2 ID and RB ID. Since the first message is an SRB0 message, the RB ID is 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] The UE ID indicates that this is a new remote UE (because the configuration of the UE is not cached). The RB ID = 0 indicates that this is an SRB0 message of the remote UE. The message is interpreted and processed normally, and an RRCSetup message is generated in response.

[0196] The network sends this RRC Setup message on the downlink default relayed RLC channel, and fills the UE ID in the adaptation header with the received L2 ID, 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 remote UE's SRB1 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 remote UE's SRB1, 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 from 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 described in detail. The relayed RLC channel mapping and configuration of SRB1 in the relay UE Uu have been prepared in advance. The relay UE will then use 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 Uu RLC 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, this article uses the L2 Source remote UE <–> Relay UE <–> Target remote UE scenario as an example to explain how to use UE IDs and RB IDs to distinguish the bearers of different remote UEs, thereby enabling normal relay communication.

[0205] First, regarding the meaning and values ​​of UE ID and RB ID, this example adopts the following principles:

[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 with 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, when 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 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. This L2 ID needs to be recognizable by the source remote UE. For example, during the discovery process, the L2 IDs of each other are exchanged. The L2 ID 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 between 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 correspondence between the two L2 IDs to facilitate 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, the 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. The method includes:

[0217] Step 500: Receive 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 the 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, thereby ensuring the service quality of the remote terminal services and taking into account the overall efficiency, thereby improving the user experience while ensuring the system efficiency.

[0222] In some optional embodiments, the terminal identifier 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 content about the terminal identification, please refer to the relevant description in the aforementioned embodiment and will not be repeated here.

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

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

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

[0230] For the relevant content about the bearer identifier, please refer to the relevant description in the aforementioned embodiment and 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] To implement bearer multiplexing, network-side equipment needs to configure corresponding radio link control channels for different types of radio bearer data. For example, configure a default relayed RLC channel for SRB0 messages and a 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 the terminal identifier of the first remote terminal and / or the 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 an 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 an UP process.

[0243] Optionally, 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, wherein 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] Assign a unique terminal identification index to each remote terminal within the coverage area.

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

[0249] In a U2N scenario, both the remote UE and the relay UE are connected and under network control. Therefore, the network-side device can assign a unique index within its jurisdiction to each remote UE for differentiation and identification. The network-side device can configure the index through a control plane (CP) procedure or a user plane UP procedure, using the remote UE identity in a 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 U2U scenarios, since the relay UE transfers a lot of data and is likely connected and scheduled by the network, it can obtain the association between the remote UE and the index from the network device for subsequent communication. If the relay UE is not connected or is offline, the index must 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 understood that in a 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 via an RRC message. In a U2U scenario, if the relay UE is in a connected state, it reports the status of each remote UE to the network, which then uniformly allocates a bearer number corresponding to each remote UE.

[0254] The embodiments of the present application provide 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 the 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 the relay terminal through the relay bearer channel;

[0257] In this embodiment, the remote terminal serves as a peer communication device and receives the 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 content about the terminal identification, please refer to the relevant description in the aforementioned embodiment and will not be repeated here.

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

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

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

[0268] For the relevant content about the bearer identifier, please refer to the relevant description in the aforementioned embodiment and 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 embodiments of the present application provide 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 the remote UE and system efficiency.

[0271] It should be noted that the remote terminal service identification method provided in the embodiments of the present application can be executed by a remote terminal service identification device, or by a control module in the remote terminal service identification device that is configured to execute the remote terminal service identification method. In the embodiments of the present application, the remote terminal service identification device executing the remote terminal service identification method is used as an example to illustrate the remote terminal service identification device provided in the embodiments of the present application.

[0272] Figure 7 One of the structural 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 the opposite communication device through the intermediate bearer channel, where the data packet header of the first message carries the terminal identifier and / or 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, thereby ensuring the service quality of the remote terminal services and taking into account the overall efficiency, thereby improving the user experience while ensuring the system efficiency.

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

[0279] Determining a type of the first message based on a logical channel identifier of the 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;

[0280] In a case where the type of the first message is an SRB0 message, determining that the relay 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 number 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 configured to send the terminal identification index to an 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 configured 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 the remote terminal that has sent the SRB0 message.

[0299] Optionally, also include:

[0300] A third receiving unit is configured 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 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;

[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 configured 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 configured to forward the second message to a 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 the terminal identifier of the first remote terminal and / or the bearer identifier of the first remote terminal.

[0310] In an embodiment of the present application, the relay terminal or the network-side device assigns a terminal identification index and / or a bearer number to the remote UE, and distinguishes the services of different remote UEs during the service multiplexing process 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 the transmission efficiency and reducing resource overhead.

[0311] The remote terminal service identification device in the embodiments 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. For example, mobile terminals can include, but are not limited to, the types of remote terminals 11 and relay terminals 13 listed above. Non-mobile terminals can include servers, network attached storage (NAS), personal computers (PCs), televisions (TVs), ATMs, or self-service kiosks, etc., and are not specifically limited in the embodiments 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 Figures 3 and 4 The various processes implemented by the method embodiment achieve the same technical effect and are not described here again 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 is 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 identifier of the remote terminal;

[0323] The number 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 radio bearer configuration information 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 the terminal identifier of the first remote terminal and / or the 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 is configured to allocate a terminal identification index to the remote terminal that sends the SRB0 message;

[0331] The fourth sending unit is configured 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 configured 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, wherein 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 configured 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 configured 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, thereby ensuring the service quality of the remote terminal services and taking into account the overall efficiency, thereby improving the user experience while ensuring the system efficiency.

[0340] The remote terminal service identification device in the embodiments 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. For example, mobile terminals can include, but are not limited to, the types of remote terminals 11 and relay terminals 13 listed above. Non-mobile terminals can include servers, network attached storage (NAS), personal computers (PCs), televisions (TVs), ATMs, or self-service kiosks, etc., and are not specifically limited in the embodiments 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 achieve the same technical effect and are not described here again to avoid repetition.

[0343] Figure 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 is 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 identifier of the remote terminal;

[0352] The number 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, thereby ensuring the service quality of the remote terminal services and taking into account the overall efficiency, thereby improving the user experience while ensuring the system efficiency.

[0355] The remote terminal service identification device in the embodiments 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. For example, mobile terminals can include, but are not limited to, the types of remote terminals 11 and relay terminals 13 listed above. Non-mobile terminals can include servers, network attached storage (NAS), personal computers (PCs), televisions (TVs), ATMs, or self-service kiosks, etc., and are not specifically limited in the embodiments 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 achieve the same technical effect and are not described here again to avoid repetition.

[0358] Optional, such as Figure 10 As shown, an embodiment of the present application further 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, when executed by the processor 1001, implements the various processes of the above-mentioned embodiment of the remote terminal service identification method, and can achieve the same technical effect. When the communication device 1000 is a network-side device, the program or instruction, when executed by the processor 1001, implements the various processes of the above-mentioned embodiment of the remote terminal service identification method, and can achieve the same technical effect. To avoid repetition, it will not be described here.

[0359] Figure 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 components such as 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 .

[0361] Those skilled in the art will understand that the terminal 1100 may also include a power supply (such as a battery) to power each component, and the power supply may be logically connected to the processor 1110 through a power management system, thereby implementing functions such as charging, discharging, and power consumption management through the power management system. Figure 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 repeated here.

[0362] It should be understood that in an embodiment of the present application, the input unit 1104 may include a graphics processing unit (GPU) 11041 and a microphone 11042, and the graphics processor 11041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an 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 an operating stick, which will not be repeated here.

[0363] In this embodiment of the present application, RF unit 1101 receives downlink data from a network-side device and transmits it to processor 1110 for processing. Furthermore, RF unit 1101 transmits uplink data to the network-side device. Typically, RF unit 1101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

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

[0365] Processor 1110 may include one or more processing units. Optionally, processor 1110 may integrate an application processor and a modem processor. The application processor primarily processes the operating system, user interface, and application programs or instructions, while the modem processor primarily processes wireless communications, such as a baseband processor. It is understood that the modem processor may not be integrated into 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 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, thereby ensuring the service quality of the remote terminal services and taking into account the overall efficiency, thereby improving the user experience while ensuring the system efficiency.

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

[0372] Determining a type of the first message based on a logical channel identifier of the 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;

[0373] In a case where the type of the first message is an SRB0 message, determining that the relay 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 number 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 assigned by the network-side device to the remote terminal that sends the SRB0 message;

[0395] Determine the remote terminal corresponding to the terminal identification index 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 the terminal identifier of the first remote terminal and / or the bearer identifier of the first remote terminal.

[0404] In an embodiment of the present application, the relay terminal or the network-side device assigns a terminal identification index and / or a bearer number to the remote UE, and distinguishes the services of different remote UEs during the service multiplexing process 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 the 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 identifier of the remote terminal;

[0413] The number 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 the remote UE and system efficiency.

[0416] The embodiment of the present application also provides a network side device. Figure 12 As shown, network device 1200 includes an antenna 1201, a radio frequency device 1202, and a baseband device 1203. Antenna 1201 is connected to radio frequency device 1202. In the uplink direction, radio frequency device 1202 receives information via antenna 1201 and sends the received information to baseband device 1203 for processing. In the downlink direction, baseband device 1203 processes the information to be transmitted and sends it to radio frequency device 1202. Radio frequency device 1202 processes the received information and then sends it through 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, such as Figure 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 and 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).

[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, so they will not be described here 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, the various processes of the above-mentioned remote terminal service identification method embodiment are 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 variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the statement "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be noted 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 the opposite 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 the necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this 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, magnetic disk, optical disk), and includes a number of instructions for enabling a terminal (which can be a mobile phone, computer, server, air conditioner, or 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 this application, ordinary technicians in this field can also make many forms without departing from the purpose of this application and the scope of protection of the claims, all of which are within the protection of this 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 the UE ID and the 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 first message is SRB0.

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 SRB0, 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 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: The unique index of the remote terminal in the relay terminal; Unique index of the remote terminal in the network-side device.

5. The remote terminal service identification method according to claim 1, characterized in that: Also includes: Receive a radio resource control 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.

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; Wherein, the second message carries the UE ID and bearer identifier of the first remote terminal; The bearer identifier is used to determine that the message type of the first message is SRB 0; and the first message is used to determine the intermediate bearer channel.

8. The remote terminal service identification method according to claim 7, characterized in that: The UE ID includes one of the following: The unique index of the remote terminal in the relay terminal; Unique index of the 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 the UE ID and the 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 UE ID and a bearer identifier of the first remote terminal; The bearer identifier is used to determine that the message type of the message is 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 SRB0, 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 RRC Setup request messages.

12. The remote terminal service identification device according to claim 9, characterized in that: The UE ID includes one of the following: The unique index of the remote terminal in the relay terminal; Unique index of the 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 a radio resource control 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 10 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; Wherein, the second message carries the UE ID and bearer identifier of the first remote terminal; The bearer identifier is used to determine that the message type of the first message is SRB 0; and the first message is used to determine the intermediate bearer channel.

16. The remote terminal service identification device according to claim 15, characterized in that: The UE ID includes one of the following: The unique index of the remote terminal in the relay terminal; Unique index of the 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