WO2022127644A1 - 远端终端业务识别方法、装置、设备及存储介质 - Google Patents

远端终端业务识别方法、装置、设备及存储介质 Download PDF

Info

Publication number
WO2022127644A1
WO2022127644A1 PCT/CN2021/135984 CN2021135984W WO2022127644A1 WO 2022127644 A1 WO2022127644 A1 WO 2022127644A1 CN 2021135984 W CN2021135984 W CN 2021135984W WO 2022127644 A1 WO2022127644 A1 WO 2022127644A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
remote terminal
message
relay
remote
Prior art date
Application number
PCT/CN2021/135984
Other languages
English (en)
French (fr)
Inventor
刘佳敏
Original Assignee
维沃移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Priority to KR1020237018873A priority Critical patent/KR20230098855A/ko
Priority to EP21905573.8A priority patent/EP4216587A4/en
Priority to JP2023527817A priority patent/JP2023547724A/ja
Publication of WO2022127644A1 publication Critical patent/WO2022127644A1/zh
Priority to US18/308,591 priority patent/US20230345462A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/22—Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/27—Transitions between radio resource control [RRC] states
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H04W28/0263—Traffic management, e.g. flow control or congestion control per individual bearer or channel involving mapping traffic to individual bearers or channels, e.g. traffic flow template [TFT]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user

Definitions

  • the present application belongs to the field of communication technologies, and in particular relates to a remote terminal service identification method, apparatus, device and storage medium.
  • LTE Long Term Evolution
  • sidelink or translated as secondary link, side link, etc.
  • UE User Equipment
  • the remote terminal forwards its data to the base station through the sidelink link with the relay terminal (relay UE).
  • relay UE plays the role of data relay.
  • Uu Interface-oriented Packet Data Convergence Protocol Uu Packet Data Convergence Protocol
  • Uu PDCP Uu Packet Data Convergence Protocol
  • an adaptation layer which is mainly used for remote UE services Multiplexing, the services of multiple remote UEs can be multiplexed into a Uu RB (Radio Bearer, radio bearer) for transmission.
  • Uu RB Radio Bearer, radio bearer
  • the related art only proposes the basic functions of the adaptation layer, and does not provide a solution for how the adaptation layer differentiates the services of different remote UEs in the process of multiplexing the services of the remote UE. Therefore the adaptation layer is currently unable to work.
  • the purpose of the embodiments of the present application is to provide a remote terminal service identification method, device, equipment and storage medium, which can solve the problem of distinguishing the services of different remote UEs in the process of remote UE service multiplexing in the related art.
  • a first aspect provides a remote terminal service identification method, applied to a relay terminal, the method includes: receiving a first message sent by a first remote terminal; determining a relay bearer for forwarding the first message channel; forward the first message to the opposite-end communication device through the relay bearer channel, and the data packet header of the first message carries the terminal identification and/or bearer identification of the first remote terminal; wherein, the The peer communication device is a network side device, a next-hop relay terminal or a second remote terminal.
  • a method for identifying a service of a remote terminal is provided, which is applied to a network side device.
  • the method includes: receiving a first message sent by a relay terminal through a relay bearer channel; wherein, a data packet header of the first message carries the terminal identity and/or bearer identity of the first remote terminal.
  • a method for identifying a service of a remote terminal which is applied to a remote terminal, and includes: receiving a first message sent by a relay terminal through a relay bearer channel; wherein, a 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.
  • a remote terminal service identification device applied to a relay terminal, the device includes: a first receiving unit for receiving a first message sent by the first remote terminal; a first processing unit for using for determining a relay bearer channel for forwarding the first message; a first sending unit, configured to forward the first message to the opposite communication device through the relay bearer channel, the data packet header of the first message carries the terminal identifier and/or bearer identifier of the first remote terminal; wherein, the opposite terminal communication device is a network side device, a next-hop relay terminal or a second remote terminal.
  • a remote terminal service identification device applied to network side equipment, the device includes: a fifth receiving unit, configured to receive a first message sent by a relay terminal through a relay bearer channel; The data packet header of the first message carries the terminal identifier and/or bearer identifier of the first remote terminal.
  • a remote terminal service identification device applied to a terminal, the device includes: a sixth receiving unit, configured to receive a first message sent by a relay terminal through a relay bearer channel; wherein the first message The data packet header of a message carries the terminal identifier of the first remote terminal and/or the bearer identifier of the first remote terminal.
  • a terminal in a seventh aspect, includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor, when the program or instruction is executed by the processor.
  • a network-side device in an eighth aspect, includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor, the program or instruction being executed by the The processor implements the steps of the method as described in the second aspect when executed.
  • a readable storage medium is provided, and a program or an instruction is stored on the readable storage medium, and 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 as described in the first aspect are implemented.
  • a chip in a tenth aspect, includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a terminal or a network-side device program or instruction, implementing the first
  • the method described in the aspect either implements the method described in the second aspect, or realizes the method described in the third aspect.
  • the services of different remote UEs are differentiated, so that the relay terminal can multiplex different services of different remote terminals in the same transmission channel for transmission, thereby improving the It improves the transmission efficiency, and at the same time provides the identifiability of remote terminal services in end-to-end transmission, thus ensuring the service quality of remote terminal services, and considering the overall efficiency, it improves user experience and guarantees system efficiency.
  • FIG. 1 is a block diagram of a wireless communication system to which an embodiment of the application can be applied;
  • FIG. 2 is a schematic diagram of the L2 relay protocol stack architecture in the related art
  • FIG. 3 is one of the schematic flowcharts of a method for identifying a service of a remote terminal provided by an embodiment of the present application
  • FIG. 4 is a schematic diagram of two UEs simultaneously connecting to a network through a relay UE according to an embodiment of the present application
  • FIG. 5 is a second schematic flowchart of a method for identifying a service of a remote terminal provided by an embodiment of the present application
  • FIG. 6 is a third schematic flowchart of a method for identifying a service of a remote terminal provided by an embodiment of the present application.
  • FIG. 7 is one of the schematic structural diagrams of a remote terminal service identification device provided by an embodiment of the present application.
  • FIG. 8 is a second schematic structural diagram of a remote terminal service identification device provided by an embodiment of the present application.
  • FIG. 9 is a third schematic structural diagram of a remote terminal service identification device provided by an embodiment of the present application.
  • FIG. 10 is a schematic structural diagram of a communication device implementing an embodiment of the present application.
  • FIG. 11 is a schematic diagram of a hardware structure of a terminal implementing an embodiment of the present application.
  • FIG. 12 is a schematic diagram of a hardware structure of a network side device implementing an embodiment of the present application.
  • first, second and the like in the description and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It is to be understood that the data so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and "first”, “second” distinguishes Usually it is a class, and the number of objects is not limited.
  • the first object may be one or multiple.
  • “and/or” in the description and claims indicates at least one of the connected objects, and the character “/" generally indicates that the associated objects are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-Advanced LTE-Advanced
  • LTE-A Long Term Evolution-Advanced
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency-Division Multiple Access
  • system and “network” in the embodiments of the present application are often used interchangeably, and the described technology can be used not only for the above-mentioned systems and radio technologies, but also for other systems and radio technologies.
  • NR New Radio
  • the following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the description below, although these techniques are also applicable to applications other than NR system applications, such as 6th generation ( 6th Generation , 6G) communication system.
  • 6th generation 6th Generation
  • FIG. 1 shows a block diagram of a wireless communication system to which the embodiments of the present application can be applied.
  • the wireless communication system includes a remote terminal 11 , a network side device 12 and a relay terminal 13 .
  • the remote terminal 11/relay terminal 13 may also be referred to as a terminal device or a user terminal (User Equipment, UE), and the remote terminal 11/relay terminal 13 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop Laptop Computer (Laptop Computer) or notebook computer, Personal Digital Assistant (PDA), Handheld Computer, Netbook, Ultra-mobile Personal Computer (UMPC), Mobile Internet Device (Mobile Internet Device, MID), wearable device (Wearable Device) or vehicle-mounted device (VUE), pedestrian terminal (PUE) and other terminal-side devices, wearable devices include: bracelets, headphones, glasses, etc.
  • the network side device 12 may be a base station or a core network, wherein the base station may 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 (Basic Service Set, BSS), Extended Service Set (Extended Service Set, ESS), Node B, Evolved Node B (eNB), 5G Base Station (gNB) in 5G Network Architecture (next generation system), Home Node B , Home Evolved Node B, WLAN Access Point, WiFi Node, Transmitting Receiving Point (TRP) or some other suitable term in the field, as long as the same technical effect is achieved, the base station is not limited to a specific Technical vocabulary, it should be noted that in the embodiments of this application, only the base station in the NR system is used as an example, but the specific type of the base station is not
  • Figure 2 is a schematic diagram of the architecture of the L2 relay protocol stack in the related art.
  • Figure 2 shows an L2 relay protocol stack used when a remote terminal communicates with a network side device through a relay terminal (that is, when communicating based on a relay bearer). .
  • the Uu PDCP protocol stack There is a Uu PDCP protocol stack between the relay terminal and the network side device, and the Uu PDCP protocol stack will include several radio bearers (Radio Bearers, RB) for data transmission of the remote terminal.
  • Radio Bearers Radio Bearers
  • Adaptation Layer Under the Uu PDCP protocol stack of the relay terminal, there is an adaptation layer (Adaptation Layer), as shown in Figure 2, ADAPT, Adaptation Layer, is a new protocol layer, mainly for remote UE business multiplexing, multiple The services of the remote UE can be multiplexed into a Uu RB (Radio Bearer) for transmission.
  • Adaptation Layer Adaptation Layer
  • the adaptation layer needs to distinguish the data of the relay terminal and the remote terminal, or the data of different remote terminals. Specifically, the adaptation layer logical entity needs to distinguish whether the data is from/to the remote terminal or the relay terminal, and which bearer of which remote terminal the data belongs to.
  • the adaptation protocol layer are the radio link control layer (Radio Link Control, RLC), medium access control protocol layer (Medium Access Control, MAC) and physical layer (Physical, PHY) facing the Uu interface.
  • RLC Radio Link Control
  • MAC Medium Access Control
  • Physical, PHY Physical, PHY
  • the adaptation layer performs service differentiation of different remote UEs, how to determine the content of the UE ID, and how to allocate the UE ID. Therefore the adaptation layer is currently unable to work.
  • FIG. 3 is one of the schematic flowcharts of the remote terminal service identification method provided by the embodiment of the present application.
  • the execution body of the method is a relay terminal relay UE. As shown in FIG. 3 , the method includes the following steps:
  • Step 300 Receive the first message sent by the first remote terminal; it can be understood that, under the condition that the remote UE of the remote terminal and the relay UE of the relay terminal meet the conditions for relay communication, the remote UE sends the message to the relay UE through the PC5 interface First news.
  • the PC5 interface is the Sidelink link interface between the remote UE and the relay UE.
  • the first message is sent by the first remote terminal to the communication device at the opposite end, and is forwarded to the communication device at the opposite end via the relay UE.
  • the bearer type of the first message may be a signaling radio bearer (Signaling Radio Bearer, SRB) 0, SRB1, SRB2, or a data radio bearer (Data Radio Bearer, DRB).
  • SRB Signaling Radio Bearer
  • DRB Data Radio Bearer
  • 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 the first remote terminal. or bearer identity.
  • Step 301 Determine a relay bearer channel for forwarding the first message.
  • the relay UE can multiplex the services of each remote terminal mapped to the same radio link control channel into the same large pipe for transmission, or can transfer the services from the same remote terminal to different peers
  • the services of the communication equipment are multiplexed.
  • the relay UE After receiving the first message sent by the first remote terminal, the relay UE needs to determine which relay bearer channel to forward the first message to the opposite-end communication device.
  • the relay bearer channel is used to carry the end-to-end RB data of the remote terminal, and the relay bearer channel may be a relayed RLC channel.
  • the relay UE determines, 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, to forward the The relay bearer channel for the first message.
  • Step 302 Forward the first message to the opposite end communication device through the relay bearer channel, where the data packet header of the first message carries the terminal identification and/or bearer identification of the first remote terminal; relay UE The first message is forwarded to the opposite communication device through the relay bearer channel, and the terminal identifier UE ID and/or bearer identifier RB ID of the first remote terminal are carried in the data packet header of the first message , the network side device can distinguish the bearers from different remote UEs according to the UE ID and/or the RB ID carried in the data packet header of the first message, thereby realizing the identification of the services of the remote terminal remote UE.
  • the opposite-end communication device may be a network-side device, a next-hop relay terminal, or a second remote terminal.
  • the application scenario of the embodiment of the present application may be a U2N (UE to NW) scenario, that is, Remote UE ⁇ –>relay UE ⁇ –>NW, in which multiple hops are possible, that is, there are multiple serial relay UEs, among which the closest one to the remote UE A relay UE is recorded as an access relay UE, and a relay UE connected to the NW is recorded as a root relay UE.
  • the access relay Between the UE and the remote UE, if bearer multiplexing is required, the UE ID and/or the RB ID can be used to distinguish the remote UE and the bearer.
  • the application scenario of the embodiment of the present application may be a U2U (UE to UE) scenario, that is, Source remote UE ⁇ –>relay UE ⁇ –>Target remote UE, in which multiple hops are possible, that is, there are multiple serial relay UEs, where the distance The closest relay UE of 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.
  • the root relay UE a relay UE between the target remote UE and the access relay UE and the source 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.
  • the services of different remote UEs are differentiated, so that the relay terminal can multiplex different services of different remote terminals in the same transmission channel for transmission, thereby improving the It improves the transmission efficiency, and at the same time provides the identifiability of remote terminal services in end-to-end transmission, thus ensuring the service quality of remote terminal services, and considering the overall efficiency, it improves user experience and guarantees system efficiency.
  • the determining a relay bearer channel for forwarding the first message includes:
  • the relay bearer channel used for forwarding the first message is the first default radio link control channel; or, in the type of the first message In the case of not being an SRB0 message, based on the mapping relationship between the type of radio bearer data and the radio link control channel, determine that the relay bearer channel used to forward the first message has a mapping with the type of the first message relation to the radio link control channel.
  • the relay UE first determines 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. The type of a message, and then the relay bearer channel is determined based on the type of the first message.
  • the relay UE Since the SRB0 message is a radio resource control (Radio Resource Control, RRC) setup request request, the relay UE needs to have a default relayed RLC channel configuration for carrying the SRB0 message. Therefore, in the embodiment of the present application, the types of the first message are divided into two categories: SRB0 messages and non-SRB0 messages.
  • RRC Radio Resource Control
  • the network side device needs to configure the first default radio link control channel for the SRB0 message.
  • the first default radio link control channel is used to carry the SRB0 message.
  • the network side device also needs to configure a mapping relationship for other non-SRB0 messages, and the mapping relationship is specifically a mapping relationship between the type of radio bearer data and the radio link control channel.
  • the relay UE determines that the relay bearer channel used for forwarding the first message is the first default radio link control channel.
  • the relay UE determines, based on the mapping relationship between the type of radio bearer data and the radio link control channel, that the relay bearer channel for forwarding the first message is: A radio link control channel having a mapping relationship with the type of the first message.
  • the relay UE determines the type of the first message based on the logical channel identifier of the corresponding PC5 interface of the first message, and then determines the relay bearer channel based on the type of the first message.
  • the data distinction on the PC5 interface can be done in the following way: map different Uu RBs and PC5 RBs one by one for identification and distinction.
  • logical channels 0-3 on the PC5 interface are the existing PC5signling
  • 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.
  • FIG. 4 is a schematic diagram of two UEs simultaneously connecting to a network through one relay UE according to an embodiment of the present application.
  • Each type of bearer can be an independent pipeline, which is convenient for relay UE to distinguish data.
  • logical channels 0-3 correspond to PC5 SRB0, SRB1, SRB2 and SRB3 respectively, which are the existing PC5 bearer types;
  • logical channels 4-14 correspond to PC5 respectively DRB1 to DRB11;
  • logical channel 15 the default or configured relayed RLC channel used to carry Uu SRB0 of remote UE1;
  • logical channels 16-17 the configured relayed RLC channel used to carry Uu SRB1 and SRB2 of remote UE1;
  • logical Channels 18-31 The configured relayed RLC channel is used to carry the Uu DRB1 to DRB14 of the remote UE1; the interval 32-63 is used for the Uu interface, an extended logical channel.
  • the Relay UE receives the above-mentioned PC5 bearer content, and directly handles the bearer of the PC5 interface according to the existing process. For the data from the RLC channel, it needs to be forwarded to the network side device.
  • the relay UE 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 logic of the PC5 interface corresponding to the first message received by the relay UE When the channel identifier is 15, because the logical channel 15 is used to carry the Uu SRB0, it can be determined that the type of the first message is an SRB0 message at this time.
  • 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. For example, if the SRB0 identifier of the first message is 0, indicating that the first message is not an SRB0 message, then based on the mapping relationship between the radio bearer data type configured on the network side and the radio link control channel RLC channel the relay bearer channel of the first message. If the SRB0 identifier of the first message is 1, indicating that the first message is an SRB0 message, the first default radio link control channel default relayed RLC channel is used as the relay bearer channel of the first message.
  • the relay UE determines the type of the first message based on the end-to-end bearer identifier of the first remote terminal, and then determines a relay bearer channel for forwarding the first message.
  • the type of the first message is an SRB1 message
  • the relay UE is based on the type of radio bearer data configured by the network side and the radio link control channel RLC channel. The mapping relationship between them determines the relay bearer channel for forwarding the first message.
  • the determining a relay bearer channel for forwarding the first message further includes:
  • the type of the first message is not an SRB0 message
  • a radio link control channel that has a mapping relationship with the type of the first message does not exist, determine a relay bearer for forwarding the first message
  • the channel is the second default radio link control channel configured on the network side.
  • the network side does not configure the mapping relationship between the type of the first message and the radio link control channel, and the second default radio link control channel is used as the medium for forwarding the first message. Inherit the bearer channel. Wherein, 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.
  • the second default radio link control channel is the same as or different from the first default relay radio link control channel.
  • the relay bearer communication channel is determined based on the logical channel identifier or the SRB0 identifier or the end-to-end bearer identifier of the PC5 interface corresponding to the first message sent by the remote terminal, which realizes the difference between different remote terminals.
  • Service multiplexing is transmitted in the same transmission channel, which improves transmission efficiency.
  • the terminal identification includes one of the following items: PC5 link layer 2 identification PC5 link L2 ID;
  • the terminal identification UE ID can use the PC5 link layer 2 identification PC5 link L2 ID of the terminal identification, and the PC5 link L2 ID is the L2 ID used by the remote UE and the relay UE when communicating on the PC5 interface, and the length is 24bit.
  • the PC5 link L2 ID is the ID used by the existing PC5 communication, it can ensure that the UE identity can be uniquely determined within a certain range, which is more convenient to use.
  • the disadvantage is that the overhead is large, and each UE needs to use 24 bits for identification and distinction.
  • the 24-bit L2 ID can also be truncated, for example, the low-order 16-bit is taken, but the cost of saving overhead is that the UE ID may be repeated.
  • the main purpose of the UE ID is to distinguish different remote UEs linked to the same relay UE, or to distinguish different remote UEs mapped to the same radio link control channel. Therefore, other definitions and allocation methods can also be considered. Obtain a smaller UE ID length, thereby saving overhead and improving resource utilization.
  • the terminal identifier may also be the unique index of the remote terminal in the relay terminal, that is, it may also be the unique index allocated by the relay terminal to the remote terminal.
  • the remote terminal service identification method further includes: assigning a terminal identification index to each remote terminal connected to the relay terminal; or, for each remote terminal that is mapped to the same radio link control channel.
  • the remote terminal assigns the terminal identification index.
  • the UE ID is defined as the label/index index of all remote UEs connected to the same relay UE.
  • the relay terminal relay UE allocates a terminal identification index to each remote terminal connected to the relay UE, and one remote terminal corresponds to a unique terminal identification index.
  • a relay UE will have an upper limit on the number of UEs that can be served at the same time due to its limited processing capability. For example, if the upper limit is set to N, the label index of the remote UE that communicates with the network through the relay UE In the interval [0, N-1], each label uniquely identifies a remote UE. Inside the relay UE, the correspondence between the remote UE index and the real L2 ID is stored, so that correct communication can be performed. For NW, it is necessary to store the mapping relationship between the UE identity carried in the RRC signaling and the remote UE index, so as to transmit, receive and process correct UE data.
  • the UE ID is defined as the index of the remote UE mapped to the same radio link control channel. That is, the relay UE allocates a terminal identification index to each remote terminal mapped to the same radio link control channel.
  • the remote terminal service identification method further includes: sending the terminal identification index to the opposite communication device of the remote terminal corresponding to the terminal identification index through a radio resource control RRC message or an UP process.
  • the relay terminal relay UE After the relay terminal relay UE allocates the terminal identification index to the remote terminal, it sends the terminal identification index to the opposite communication device of the remote terminal corresponding to the terminal identification index through the radio resource control RRC message or the UP process.
  • the UE index is allocated by the relay UE and notified to the NW.
  • the terminal identifier may also be a unique index allocated by the network side device to the remote terminal.
  • the NW receives it, it interprets the message to determine the identity of the UE, and then assigns the UE a unique UE index within the relay UE.
  • the remote terminal service identification method further includes: receiving a radio resource control RRC message sent by the network side device, where the RRC message carries a terminal identification index allocated by the network side device for the remote terminal that has sent the SRB0 message .
  • the network side device informs the relay UE that an index is allocated to the remote UE through an RRC message with the relay UE, wherein the remote UE is distinguished in the RRC message, and the RRC setup request (that is, the SRB0 message) can be used. ) part of the content, for example, 40 bits in it to identify the remote UE. Since the RRC setup request message contains the UE identity, the network side indicates the UE by copying all or part of the content. For the relay UE, it needs to be the remote UE. The RRC setup request message forwarded by the UE is backed up and cached. Once the relay UE receives the configuration message, it can be compared to which remote UE is assigned the Index, and then the L2 ID of the remote UE is associated with the index and stored for Subsequent transit data transmission.
  • the remote terminal service identification method further includes: receiving a control protocol data unit/first data packet sent by a network-side device, where the control protocol data unit/first data packet carries an SRB0 message sent.
  • the remote terminal corresponding to the terminal identification index is determined.
  • the network side device informs the relay UE about the index allocation through the user plane (User Plane, UP) process.
  • the specific method is to use the UP control protocol data unit control PDU, which carries the remote UE identity information in the index and setup request messages, and the relay UE reads After that, it can be known that the network side device has allocated the corresponding index to the remote UE.
  • the network side device sends a first data packet, and the first data packet carries the newly allocated UE index and remote UE identity information. After the relay UE interprets it, a correct association between the remote UE and the index can also be established. , for subsequent transfer data transmission.
  • the number of remote UEs connected to a relay UE is not too many, such as 32 or 16. Therefore, in this way, the index used to distinguish remote UEs only needs a few bits, not more than one byte. Hence significant cost savings.
  • the relay UE assigns a unique index to each remote UE connected to it to identify different remote UEs.
  • the allocation method can be notified by PC5 RRC between the relay UE and the remote UE.
  • the bearer identification includes one of the following items: an end-to-end bearer identification; and a label of a bearer corresponding to a remote terminal mapped to the same radio link control channel.
  • the bearer identification RB ID may also be the bearer label corresponding to the remote terminal mapped to the same radio link control channel.
  • the number of existing end-to-end bearers is a maximum of 32, that is, if the RB ID identifies the end-to-end bearer, 5 bits are required.
  • the length of the RB ID can be reduced to 2 bits. It is equivalent to the mapping relationship of the RB that needs to be notified, and an example of the mapping is shown in Table 1 below.
  • the index y of the RLC channel x is to select the corresponding RLC channel based on the principle of the same or similar QoS, and then check whether the remote UE has other RBs mapped to this RLC channel, and sort the RBs mapped to the same RLC channel once within a group. .
  • the way of establishing and notifying the mapping is as follows: For the signaling radio bearer, due to the limited number of Uu SRBs (used in U2N scenarios) and PC5 SRBs (used in U2U scenarios) and their clear roles, each remote UE must have these SRBs. Therefore, a fixed mapping method can be adopted. By default or in advance, the SRB is mapped to the default RLC channel n, and the RB index is also fixed.
  • DRB because DRB has the characteristics of burstiness and diversity, only after the service arrives, it is configured by the base station to the relay UE through Uu RRC (for U2N scenario), or PC5 RRC (for U2U scenario) is configured by relay UE
  • Uu RRC for U2N scenario
  • PC5 RRC for U2U scenario
  • the UE is configured to the remote UE at both ends; after the configuration, normal communication can be performed.
  • the remote terminal service identification method further includes: assigning a bearer label to each remote terminal mapped to the same radio link control channel.
  • the relay UE allocates a bearer label to each remote terminal mapped to the same radio link control channel, and configures it to the corresponding remote UE through the PC5 RRC message.
  • the data of different target UE 2, target UE 3, and target UE 4 can be multiplexed, and the assigned bearer labels can respectively correspond to: the terminal between UE 1 and UE 2.
  • relay UE and target UE2 there is a difference:
  • the assigned bearer labels can respectively 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 end-to-end bearer.
  • the relay terminal or the network side device allocates a terminal identification index and/or a bearer label to the remote UE, and distinguishes the services of different remote UEs in the process of multiplexing the services of the remote UE, so that the relay terminal Multiplexing different services of different remote terminals in the same transmission channel for transmission improves transmission efficiency and reduces resource overhead.
  • the method for identifying a service of a remote terminal further includes: receiving a second message sent by the peer communication device; based on the terminal carried in the data packet header of the second message identification and/or bearer identification, and forward the second message to the corresponding remote terminal.
  • the relay UE receives the second message sent by the peer communication device.
  • the second message is an RRC Setup message. Then, based on the terminal identifier and/or the bearer identifier carried in the data packet header of the second message, the second message is forwarded to the corresponding remote terminal.
  • the method before the receiving the first message sent by the first remote terminal, the method further includes: after the first remote terminal satisfies the conditions for establishing relay communication, and the relay terminal communicates with the Under the condition that the link quality between the first remote terminal and the link quality between the relay terminal and the first communication device meet the conditions for establishing relay communication, perform communication with the first remote terminal through the PC5 interface. interaction, and it is determined that the relay terminal has the capability of relaying the service of the first remote terminal.
  • the remote UE is located at the edge of the cell, the RSRP is lower than the threshold configured by a network, and it cannot communicate with the NW directly. At this time, it needs to relay its data to the network through the relay UE. At this time, the first terminal meets the conditions for establishing relay communication.
  • 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. Make sure that subsequent communications work properly.
  • the remote UE and the relay UE need to exchange relay service information through the PC5 process.
  • the relay UE it is necessary to ensure that the relay UE can perform the relay service of the service to be initiated by the remote UE.
  • 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.
  • the UE ID and RB ID mentioned in this application can be used for the adaptation layer adaptation layer and are included in the adaptation layer header. But it is not limited to this, all protocol layers that need to perform data multiplexing can be used.
  • the following describes how to use UE ID and RB ID to distinguish bearers of different remote UEs in combination with specific application scenarios.
  • the L2 Remote UE ⁇ –>relay UE ⁇ –>NW scenario is taken as an example to illustrate how to use the UE ID and RB ID to distinguish the bearers of different remote UEs, so as to carry out normal relay communication.
  • UE ID is PC5 link L2 ID
  • RB ID is end-to-end bearer identification.
  • the process of establishing L2 relay U2N communication for remote UE and how to perform bearer multiplexing between relay and NW is given below:
  • Step a the remote UE satisfies the conditions for establishing L2 relay U2N communication, and finds a suitable relay UE.
  • the remote UE is at the edge of the cell, the RSRP is lower than a threshold configured by the network, and it cannot communicate with the NW directly. At this time, it needs to relay its data to the network through the relay UE.
  • the relay UE also needs to meet certain conditions. For example, the link condition from the relay UE itself to the NW is good enough, and the RSRP is higher than the threshold configured by a network. Optionally, the link condition from the relay UE to the NW cannot be too good, that is, at the same time If the RSRP is lower than a network-configured threshold, the advantage of doing so is to avoid excessive interference by the UE in the center of the cell when relaying the UE.
  • the link quality of the PC5 between the remote UE and the relay UE also needs to meet a certain threshold, that is, the PC5 RSRP (Reference Signal Receiving Power, reference signal receiving power) is higher than the threshold, so as to ensure normal subsequent communication.
  • the PC5 RSRP Reference Signal Receiving Power, reference signal receiving power
  • the remote UE and the relay UE need to exchange relay service information through the PC5 process.
  • the relay UE it is necessary to ensure that the relay UE can perform the relay service of the service to be initiated by the remote UE.
  • Step b After the relay UE decides to perform service relay service for the remote UE, it needs to make certain preparations on its own Uu interface. For example, it needs to have a default relayed RLC channel configuration, at least for carrying the remote UE without the configuration mapping relationship. End-to-end RB data.
  • the relay UE 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 feature is that it is configured as RLC AM (Acknowledge Mode) or UM (UnAcknowledge Mode), has adaptation layer and header, adaptation layer header contains UE ID and RB ID, and does not have any mapping relationship The default mapping of remote UE data to this RLC channel.
  • RLC AM Acknowledge Mode
  • UM UnAcknowledge Mode
  • the relay UE If the relay UE is already in the Connected state, and it still has its own Uu data transmission, or other remote UE relay data transmission, then it is likely that the default relayed RLC channel already exists at this time, which can carry remote without any mapping relationship. UE data.
  • Uu port logical channel number of relay UE 0 is its own SRB0 message, 1 is its own SRB1 message, 2 is its own SRB2 message, 4 is its own first DRB, 5 is its own second message DRB, 10 is the default relayed RLC channel, which is used to carry relay data without a mapping relationship, and 11-13 are other relayed RLC channels, which carry data of different QoS of other remote UEs configured with a mapping relationship.
  • Step c The remote UE sends the first Uu message - RRC Setup Request. This message is sent to the NW, but it needs to be sent to the relay UE and transferred therefrom.
  • the Remote UE sends the first Uu message to the relay UE through the PC5 interface; after the Relay UE receives the first message, it uses its own default relayed RLC channel obtained in step b to send the first message, in which the data packet
  • Step e The relay UE receives the RRC setup message, can find the corresponding remote UE from the UE ID read in the adaptation header, and forwards the RRC Setup message to the corresponding remote UE on the PC5 interface.
  • Step f When the remote UE receives the RRC Setup message, it establishes an SRB1 according to the configuration in the message, and sends a subsequent RRC Setup complete message on the newly established SRB1.
  • the subsequent steps will not be repeated.
  • the relayed RLC channel mapping and configuration of SRB1 in the relay UE Uu have been prepared in advance.
  • the SRB2 and DRB of the remote UE are similar.
  • the SRB1 pipeline 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 remote UE.
  • L2 ID and end-to-end RB ID can be used in a relay Uu RLC channel to clearly distinguish between different remote UEs and specific bearer content (SRB0/1/2/DRB).
  • the following describes how to use the UE ID and RB ID to distinguish the bearers of different remote UEs in the U2U scenario.
  • the L2 Source remote UE ⁇ –>relay UE ⁇ –>Target remote UE scenario is taken as an example to illustrate how to use the UE ID and RB ID to distinguish the bearers of different remote UEs, so as to carry out normal relay communication.
  • UE ID is PC5 link L2 ID
  • RB ID is end-to-end bearer identification
  • the relay UE can multiplex the data of multiple source remote UEs (because their target remote UEs are the same UE) to reduce the possibility of the second hop appearing.
  • 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 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.
  • the relay UE when the relay UE receives the data of the source remote UE through the first L2 ID on the PC5 interface, it needs to pass For the first L2 ID, find the corresponding second L2 ID and put it in the adaptation layer header to identify the source remote UE at the second hop; and carry the corresponding RB ID to identify which bearer of which source remote UE is.
  • the RB ID still uses the end-to-end RB ID between the source remote UE and the target remote UE.
  • SRB 0-3 corresponds to RB 0-3, and the remaining DRBs are established and allocated between the source and the target through the RRC signaling process. After the ID, use it again.
  • the relay UE can multiplex the data from the same source remote UE to different target remote UEs to reduce the number of bearers that may appear in the first hop: each Each target remote UE is still distinguished by its respective L2 ID, which needs to be identified 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 used with the target remote UE.
  • the L2 ID used in PC5 communication with the relay UE is the same or different. If it is different, it means that the target remote UE has at least two L2 IDs, one of which is used for PC5 transmission with the relay UE.
  • Another 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; And carry the corresponding RB ID to identify which bearer of which source remote UE is, the principle is the same as above;
  • the execution subject is a network side device.
  • the method includes: Step 500: Receive a first message sent by a relay terminal through a relay bearer channel, so The data packet header of the first message carries the terminal identifier and/or bearer identifier of the first remote terminal.
  • the network-side device as a peer communication device, receives the first message forwarded by the relay terminal through the relay bearer channel. According to the UE ID and/or RB ID carried in the data packet header of the first message, the network side device can distinguish the bearers from different remote UEs, thereby realizing the identification of the services of the remote terminal remote UE.
  • the services of different remote UEs are differentiated, so that the relay terminal can multiplex different services of different remote terminals in the same transmission channel for transmission, thereby improving the It improves the transmission efficiency, and at the same time provides the identifiability of remote terminal services in end-to-end transmission, thus ensuring the service quality of remote terminal services, and considering the overall efficiency, it improves user experience and guarantees system efficiency.
  • the terminal identification includes one of the following items: PC5 link layer 2 identifies PC5 link L2 ID or part of bits of the PC5 link L2 ID; the remote terminal is in the relay The unique index in the terminal; the unique index of the remote terminal in the network side device.
  • PC5 link layer 2 identifies PC5 link L2 ID or part of bits of the PC5 link L2 ID; the remote terminal is in the relay The unique index in the terminal; the unique index of the remote terminal in the network side device.
  • the bearer identifier includes one of the following items: an end-to-end bearer identifier of the remote terminal; an identifier of the bearer corresponding to the remote terminal mapped to the same radio link control channel label.
  • the remote terminal service identification method further includes: sending the configuration information of the radio bearer to the relay terminal; wherein the configuration information of the radio bearer carries the type of the radio bearer data and Mapping relationship between radio link control channels.
  • the network side device needs to configure corresponding radio link control channels for different types of radio bearer data. For example, configure the default relayed RLC channel for SRB0 messages, and configure the corresponding RLC channel for non-SRB0 messages.
  • the network side device sends configuration information of the radio bearer to the relay terminal; wherein the configuration information of the radio bearer carries the mapping relationship between the type of the radio bearer data and the radio link control channel.
  • 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.
  • the remote terminal service identification method further includes: receiving the SRB0 message forwarded by the relay terminal, and determining the identity information of the remote terminal sending the SRB0 message; for sending the SRB0 message
  • the remote terminal assigns a terminal identification index, and sends the terminal identification index to the relay terminal through a radio resource control RRC message or an UP process.
  • the terminal identifier may also be a unique index allocated by the network side device to the remote terminal.
  • 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.
  • 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.
  • the sending the terminal identification index to the relay terminal through a radio resource control RRC message or an UP process includes: sending an RRC message to the relay terminal, where the RRC message carries the terminal identification index Or, send the control protocol data unit/first data packet to the relay terminal through the UP process, and the control protocol data unit/first data packet carries the identity information of the remote terminal sending the SRB0 message and the Describe the terminal identification index corresponding to the remote terminal that has sent the SRB0 message.
  • the remote terminal service identification method further includes: assigning a unique terminal identification index to each remote terminal within the coverage.
  • UE ID definition is provided, so that the length of the UE ID can be located between the complete L2 ID 24bit and the unique index length in the relay, and the remote UE is allocated a unique in the cell.
  • Identifier generally 2 bytes long, to distinguish different remote UEs.
  • the network-side device can assign each remote UE a unique index within its own jurisdiction for distinguishing and identifying.
  • the way the network side device configures the index can establish the association between the remote UE and the index through the control plane (Control Plane, CP) process or the user plane UP process, through the remote UE identity of the setup request and various notification methods of the configured index. for subsequent communications.
  • the relay UE needs to transfer a lot of data, and it is also likely to be in the connected state and is scheduled by the network, the association between the remote UE and the index can be obtained from the network side device for subsequent communication. If the relay UE is not in the connected state or is offline, the index can only be determined by the relay UE itself.
  • the remote terminal service identification method further includes: assigning a bearer label to each remote terminal mapped to the same radio link control channel.
  • the network side device allocates a bearer label to each remote UE mapped to the same radio link control channel, and configures it to the relay UE through an RRC message.
  • the relay UE if the relay UE is in the connected state, the relay UE will report the status of each remote UE to the network, and the network will uniformly assign the bearer label corresponding to each remote UE.
  • the embodiments of the present application provide a method for identifying remote UE services when bearer multiplexing is required in the secondary link relay architecture, which can make relay UE operations more orderly, and reduce the number of bearers and the complexity of scheduling transmission.
  • the complexity ensures the service experience and system efficiency of the remote UE.
  • FIG. 6 is a third schematic flowchart of a method for identifying a service of a remote terminal provided by an embodiment of the present application, which is applied to a remote terminal and includes:
  • Step 600 Receive a first message sent by the relay terminal through the relay bearer channel, where 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.
  • the remote terminal as a peer communication device, receives the first message forwarded by the relay terminal through the relay bearer channel.
  • the remote device can distinguish 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 the identification of the services of the remote terminal remote UE.
  • the terminal identification includes one of the following items: PC5 link layer 2 identifies PC5 link L2 ID or part of bits of the PC5 link L2 ID; the unique index of the remote terminal in the relay terminal ; The unique index of the remote terminal in the network side device.
  • PC5 link layer 2 identifies PC5 link L2 ID or part of bits of the PC5 link L2 ID; the unique index of the remote terminal in the relay terminal ; The unique index of the remote terminal in the network side device.
  • the bearer identification includes one of the following items: an end-to-end bearer identification of a remote terminal; and a label of a bearer corresponding to the remote terminal mapped to the same radio link control channel.
  • an end-to-end bearer identification of a remote terminal mapped to the same radio link control channel.
  • the adaptation layer protocol header of the first message carries the terminal identifier and/or bearer identifier of the first remote terminal.
  • the embodiments of the present application provide a method for identifying remote UE services when bearer multiplexing is required in the secondary link relay architecture, which can make relay UE operations more orderly, and reduce the number of bearers and the complexity of scheduling transmission.
  • the complexity ensures the service experience and system efficiency of the remote UE.
  • the execution subject may be a remote terminal service identification device, or a method for executing the remote terminal service identification method in the remote terminal service identification device. control module.
  • the remote terminal service identification method provided by the embodiment of the present application is described by taking the remote terminal service identification device executing the remote terminal service identification method as an example.
  • FIG. 7 is one of the schematic structural diagrams of the remote terminal service identification device provided by the embodiment of the application, including: a first receiving unit 710, a first processing unit 720, and a first sending unit 730, wherein the first receiving unit 710 uses is used to receive the first message sent by the first remote terminal; the first processing unit 720 is used to determine the relay bearer channel for forwarding the first message; the first sending unit 730 is used to transmit the first message through the relay bearer The channel forwards the first message to the opposite end communication device, and the data packet header of the first message carries the terminal identification and/or bearer identification of the first remote terminal; wherein the opposite end communication device is the network side device, next-hop relay terminal, or second remote terminal.
  • the services of different remote UEs are differentiated, so that the relay terminal can multiplex different services of different remote terminals in the same transmission channel for transmission, thereby improving the It improves the transmission efficiency, and at the same time provides the identifiability of remote terminal services in end-to-end transmission, thus ensuring the service quality of remote terminal services, and considering the overall efficiency, it improves user experience and guarantees system efficiency.
  • the first processing unit 720 is configured to: 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 of the first remote terminal.
  • bearer identifier determine the type of the first message; if the type of the first message is an SRB0 message, determine that the relay bearer channel used to forward the first message is the first default RLC channel; or, in the case where the type of the first message is not an SRB0 message, based on the mapping relationship between the type of radio bearer data and the radio link control channel, determine the relay bearer for forwarding the first message
  • the channel is a radio link control channel that has a mapping relationship with the type of the first message.
  • the first processing unit 720 is further configured to: when the type of the first message is not an SRB0 message, and the radio link control channel that has a mapping relationship with the type of the first message does not exist In this case, it is determined that the relay bearer channel used for forwarding the first message is the second default radio link control channel configured by the network side; wherein the second default radio link control channel is the same as the first
  • the default relay radio link control channels are the same or different.
  • the terminal identification includes one of the following items: PC5 link layer 2 identifies PC5 link L2 ID or part of bits of the PC5 link L2 ID; the unique index of the remote terminal in the relay terminal ; The unique index of the remote terminal in the network side device.
  • the bearer identification includes one of the following items: an end-to-end bearer identification; and a label of a bearer corresponding to a remote terminal mapped to the same radio link control channel.
  • it also includes a first configuration unit for: assigning a terminal identification index to each remote terminal connected to the relay terminal; or, for each remote terminal mapped to the same radio link control channel The terminal assigns the terminal identification index.
  • the method further includes: a second sending unit, configured to send the terminal identification index to the opposite communication device of the remote terminal corresponding to the terminal identification index through a radio resource control RRC message or an UP process.
  • a second sending unit configured to send the terminal identification index to the opposite communication device of the remote terminal corresponding to the terminal identification index through a radio resource control RRC message or an UP process.
  • a second receiving unit configured to receive a radio resource control RRC message sent by the network side device, where the RRC message carries a terminal identification index allocated by the network side device for the remote terminal that has sent the SRB0 message.
  • a third receiving unit configured to receive a control protocol data unit/first data packet sent by the network side device, where the control protocol data unit/first data packet carries the remote end that sent the SRB0 message The identity information of the terminal and the terminal identification index allocated by the network side device to the remote terminal that has sent the SRB0 message; the second processing unit is configured to determine the remote terminal corresponding to the terminal identification index according to the identity information terminal.
  • the method further includes: a second configuration unit, configured to assign a bearer label to each remote terminal mapped to the same radio link control channel.
  • a fourth receiving unit configured to receive the second message sent by the opposite end communication device
  • a third processing unit configured to be based on the terminal identifier and/or the terminal identifier carried in the data packet header of the second message or bearer identifier, and forward the second message to the corresponding remote terminal.
  • the method before the receiving the first message sent by the first remote terminal, the method further includes: a fourth processing unit, configured to satisfy the conditions for establishing relay communication when the first remote terminal meets the conditions for establishing relay communication, and the relay terminal communicates with the When the link quality between 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 , it is determined that the relay terminal has the capability of relaying the service of the first remote terminal.
  • a fourth processing unit configured to satisfy the conditions for establishing relay communication when the first remote terminal meets the conditions for establishing relay communication, and the relay terminal communicates with the When the link quality between 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 , it is determined that the relay terminal has the capability of relaying the service of the first remote terminal.
  • 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.
  • the relay terminal or the network side device allocates a terminal identification index and/or a bearer label to the remote UE, and distinguishes the services of different remote UEs in the process of multiplexing the services of the remote UE, so that the relay terminal Multiplexing different services of different remote terminals in the same transmission channel for transmission improves transmission efficiency and reduces resource overhead.
  • the remote terminal service identification device in this embodiment of the present application may be a device, or may be a component, an integrated circuit, or a chip in a terminal.
  • the device may be a mobile terminal or a non-mobile terminal.
  • the mobile terminal may include, but is not limited to, the types of the remote terminal 11/relay terminal 13 listed above, and the non-mobile terminal may be a server, a Network Attached Storage (NAS), a personal computer (personal computer) , PC), television (television, TV), teller machine or self-service machine, etc., which are not specifically limited in the embodiments of the present application.
  • the remote terminal service identification device in this embodiment of the present application may be a device with an operating system.
  • the operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, which are not specifically limited in the embodiments of the present application.
  • the remote terminal service identification device provided in the embodiment of the present application can implement each process implemented by the method embodiments in FIG. 3 to FIG. 4 , and achieve the same technical effect. To avoid repetition, details are not repeated here.
  • FIG. 8 is the second schematic structural diagram of a remote terminal service identification device provided by an embodiment of the present application, including: a fifth receiving unit 810, configured to receive a first message sent by a relay terminal through a relay bearer channel; wherein the The data packet header of the first message carries the terminal identifier and/or bearer identifier of the first remote terminal.
  • the terminal identification includes one of the following items: PC5 link layer 2 identifies PC5 link L2 ID or part of bits of the PC5 link L2 ID; the unique index of the remote terminal in the relay terminal ; The unique index of the remote terminal in the network side device.
  • the bearer identification includes one of the following items: an end-to-end bearer identification of a remote terminal; and a label of a bearer corresponding to the remote terminal mapped to the same radio link control channel.
  • it further includes: a third sending unit, configured to send the configuration information of the radio bearer to the relay terminal; wherein, the configuration information of the radio bearer carries the relationship between the type of the radio bearer data and the radio link control channel mapping relationship.
  • a third sending unit configured to send the configuration information of the radio bearer to the relay terminal; wherein, the configuration information of the radio bearer carries the relationship between the type of the radio bearer data and the radio link control channel mapping relationship.
  • 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.
  • it further includes: 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; a third configuration unit, configured to send the SRB0 message The remote terminal assigns a terminal identification index to the remote terminal; the fourth sending unit is configured to send the terminal identification index to the relay terminal through a radio resource control RRC message or an UP process.
  • 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
  • a third configuration unit configured to send the SRB0 message
  • the remote terminal assigns a terminal identification index to the remote terminal
  • the fourth sending unit is configured to send the terminal identification index to the relay terminal through a radio resource control RRC message or an UP process.
  • the fourth sending unit is configured to: send an RRC message to the relay terminal, where the RRC message carries the terminal identification index; or send control protocol data to the relay terminal through an UP process Unit/first data packet, the control protocol data unit/first data packet carries the identity information of the remote terminal that sent the SRB0 message and the terminal identification index corresponding to the remote terminal that sent the SRB0 message.
  • a fourth configuration unit configured to assign a unique terminal identification index to each remote terminal within the coverage.
  • the method further includes: a fifth configuration unit, configured to assign a bearer label to each remote terminal mapped to the same radio link control channel.
  • the services of different remote UEs are differentiated, so that the relay terminal can multiplex different services of different remote terminals in the same transmission channel for transmission, thereby improving the It improves the transmission efficiency, and at the same time provides the identifiability of remote terminal services in end-to-end transmission, thus ensuring the service quality of remote terminal services, and considering the overall efficiency, it improves user experience and guarantees system efficiency.
  • the remote terminal service identification device in this embodiment of the present application may be a device, or may be a component, an integrated circuit, or a chip in a terminal.
  • the device may be a mobile terminal or a non-mobile terminal.
  • the mobile terminal may include, but is not limited to, the types of the remote terminal 11/relay terminal 13 listed above, and the non-mobile terminal may be a server, a Network Attached Storage (NAS), a personal computer (personal computer) , PC), television (television, TV), teller machine or self-service machine, etc., which are not specifically limited in the embodiments of the present application.
  • NAS Network Attached Storage
  • personal computer personal computer
  • PC personal computer
  • television television
  • teller machine or self-service machine etc.
  • the remote terminal service identification device in this embodiment of the present application may be a device with an operating system.
  • the operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, which are not specifically limited in the embodiments of the present application.
  • the apparatus for identifying a service of a remote terminal provided by the embodiment of the present application can implement each process implemented by the method embodiment in FIG. 5 , and achieve the same technical effect. To avoid repetition, details are not repeated here.
  • FIG. 9 is a third schematic structural diagram of a remote terminal service identification device provided by an embodiment of the present application, including: a sixth receiving unit 910, configured to receive a first message sent by a relay terminal through a relay bearer channel; wherein the 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.
  • the terminal identification includes one of the following items: PC5 link layer 2 identifies PC5 link L2 ID or part of bits of the PC5 link L2 ID; the unique index of the remote terminal in the relay terminal ; The unique index of the remote terminal in the network side device.
  • the bearer identification includes one of the following items: an end-to-end bearer identification of a remote terminal; and a label of a bearer corresponding to the remote terminal mapped to the same radio link control channel.
  • the adaptation layer protocol header of the first message carries the terminal identifier and/or bearer identifier of the first remote terminal.
  • the services of different remote UEs are differentiated, so that the relay terminal can multiplex different services of different remote terminals in the same transmission channel for transmission, thereby improving the It improves the transmission efficiency, and at the same time provides the identifiability of remote terminal services in end-to-end transmission, thus ensuring the service quality of remote terminal services, and considering the overall efficiency, it improves user experience and guarantees system efficiency.
  • the remote terminal service identification device in this embodiment of the present application may be a device, or may be a component, an integrated circuit, or a chip in a terminal.
  • the device may be a mobile terminal or a non-mobile terminal.
  • the mobile terminal may include, but is not limited to, the types of the remote terminal 11/relay terminal 13 listed above, and the non-mobile terminal may be a server, a Network Attached Storage (NAS), a personal computer (personal computer) , PC), television (television, TV), teller machine or self-service machine, etc., which are not specifically limited in the embodiments of the present application.
  • NAS Network Attached Storage
  • personal computer personal computer
  • PC personal computer
  • television television
  • teller machine or self-service machine etc.
  • the remote terminal service identification device in this embodiment of the present application may be a device with an operating system.
  • the operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, which are not specifically limited in the embodiments of the present application.
  • the apparatus for identifying a service of a remote terminal provided in this embodiment of the present application can implement each process implemented by the method embodiment in FIG. 6 , and achieve the same technical effect. To avoid repetition, details are not described here.
  • an embodiment of the present application further provides a communication device 1000, including a processor 1001, a memory 1002, a program or instruction stored in the memory 1002 and executable on the processor 1001,
  • a communication device 1000 including a processor 1001, a memory 1002, a program or instruction stored in the memory 1002 and executable on the processor 1001
  • the communication device 1000 is a terminal
  • the program or instruction is executed by the processor 1001
  • each process of the foregoing embodiments of the remote terminal service identification method is implemented, and the same technical effect can be achieved.
  • the communication device 1000 is a network-side device, when the program or instruction is executed by the processor 1001, each process of the above-mentioned embodiment of the remote terminal service identification method can be realized, and the same technical effect can be achieved. To avoid repetition, details are not repeated here. .
  • FIG. 11 is a schematic diagram of a hardware structure of a terminal implementing an embodiment of the present application.
  • the terminal 1100 includes but is not limited to: a radio frequency unit 1101, a network module 1102, an audio output unit 1103, an input unit 1104, a sensor 1105, a display unit 1106, a user input unit 1107, an interface unit 1108, a memory 1109, a processor 1110 and other components .
  • the terminal 1100 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 1110 through a power management system, so as to manage charging, discharging, and power consumption through the power management system management and other functions.
  • a power source such as a battery
  • the terminal structure shown in FIG. 11 does not constitute a limitation on the terminal, and the terminal may include more or less components than shown, or combine some components, or arrange different components, which will not be repeated here.
  • the input unit 1104 may include a graphics processor (Graphics Processing Unit, GPU) 11041 and a microphone 11042, and the graphics processor 11041 is used to communicate with the image capture device (such as camera) to obtain still pictures or video image data for processing.
  • the display unit 1106 may include a display panel 11061, which may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like.
  • 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, physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be described herein again.
  • the radio frequency unit 1101 receives the downlink data from the network side device, and then processes it to the processor 1110; in addition, sends the uplink data to the network side device.
  • the radio frequency unit 1101 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
  • Memory 1109 may be used to store software programs or instructions as well as various data.
  • the memory 1109 may mainly include a stored program or instruction area and a storage data area, wherein the stored program or instruction area may store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.) and the like.
  • 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 (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM) , PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • ROM Read-Only Memory
  • PROM programmable read-only memory
  • PROM erasable programmable read-only memory
  • Erasable PROM Erasable PROM
  • EPROM electrically erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • flash memory for example at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.
  • the processor 1110 may include one or more processing units; optionally, the processor 1110 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs or instructions, etc. Modem processors mainly deal with wireless communications, such as baseband processors. It can be understood that, the above-mentioned modulation and demodulation processor may not be integrated into the processor 1110.
  • the radio frequency unit 1101 is used to receive the first message sent by the first remote terminal; the processor 1110 is used to determine the relay bearer channel for forwarding the first message; The terminal communication device forwards the first message, and the data packet header of the first message carries the terminal identifier and/or bearer identifier of the first remote terminal; wherein, the opposite terminal communication device is a network side device, a downlink One-hop relay terminal or second remote terminal.
  • the services of different remote UEs are differentiated, so that the relay terminal can multiplex different services of different remote terminals in the same transmission channel for transmission, thereby improving the It improves the transmission efficiency, and at the same time provides the identifiability of remote terminal services in end-to-end transmission, thus ensuring the service quality of remote terminal services, and considering the overall efficiency, it improves user experience and guarantees system efficiency.
  • the processor 1110 is configured to: 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, determine the type of the first message; if the type of the first message is an SRB0 message, determine that the relay bearer channel used to forward the first message is the first default radio link control channel; or, in When the type of the first message is not the SRB0 message, based on the mapping relationship between the type of radio bearer data and the radio link control channel, it is determined that the relay bearer channel for forwarding the first message is the same as the radio link control channel.
  • the type of the first message has a radio link control channel in a mapping relationship.
  • the processor 1110 is further configured to: in the case that the type of the first message is not an SRB0 message, and the radio link control channel that has a mapping relationship with the type of the first message does not exist, determine the The relay bearer channel for forwarding the first message is the second default radio link control channel configured on the network side; wherein, the second default radio link control channel and the first default relay radio The link control channels are the same or different.
  • the terminal identification includes one of the following items: PC5 link layer 2 identification PC5 link L2 ID; part of the bits of the PC5 link L2 ID; the unique index of the remote terminal in the relay terminal ; The unique index of the remote terminal in the network side device.
  • the bearer identification includes one of the following items: an end-to-end bearer identification; and a label of a bearer corresponding to a remote terminal mapped to the same radio link control channel.
  • the processor 1110 is further configured to: allocate a terminal identification index to each remote terminal connected to the relay terminal; or allocate a terminal identification index to each remote terminal mapped to the same radio link control channel Terminal identification index.
  • the processor 1110 is further configured to: send the terminal identification index to the peer communication device of the remote terminal corresponding to the terminal identification index through a radio resource control RRC message or an UP process.
  • the processor 1110 is further configured to: receive a radio resource control RRC message sent by the network side device, where the RRC message carries a terminal identification index allocated by the network side device for the remote terminal that has sent the SRB0 message.
  • the processor 110 is further configured to: receive a control protocol data unit/first data packet sent by the network-side device, where the control protocol data unit/first data packet carries the data of the remote terminal that sent the SRB0 message.
  • the identity information and the terminal identification index assigned by the network side device to the remote terminal that has sent the SRB0 message; and the remote terminal corresponding to the terminal identification index is determined according to the identity information.
  • the processor 1110 is further configured to: assign a bearer label to each remote terminal mapped to the same radio link control channel.
  • the processor 1110 is further configured to: receive the second message sent by the peer communication device; The message is forwarded to the corresponding remote terminal.
  • the processor 1110 is further configured to: satisfy the conditions for establishing relay communication at the first remote terminal, and the link quality between the relay terminal and the first remote terminal and the quality of the link between the relay terminal and the first remote terminal.
  • the link quality between a communication device meets the conditions for establishing relay communication, interact with the first remote terminal through the PC5 interface to determine that the relay terminal has the service of relaying the first remote terminal Ability.
  • 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.
  • the relay terminal or the network side device allocates a terminal identification index and/or a bearer label to the remote UE, and distinguishes the services of different remote UEs in the process of multiplexing the services of the remote UE, so that the relay terminal Multiplexing different services of different remote terminals in the same transmission channel for transmission improves transmission efficiency and reduces resource overhead.
  • the radio frequency unit 1101 is configured to receive the first message sent by the relay terminal through the relay bearer channel; wherein, 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.
  • the terminal identification includes one of the following items: PC5 link layer 2 identifies PC5 link L2 ID or part of bits of the PC5 link L2 ID; the unique index of the remote terminal in the relay terminal ; The unique index of the remote terminal in the network side device.
  • the bearer identification includes one of the following items: an end-to-end bearer identification of a remote terminal; and a label of a bearer corresponding to the remote terminal mapped to the same radio link control channel.
  • the adaptation layer protocol header of the first message carries the terminal identifier and/or bearer identifier of the first remote terminal.
  • the embodiment of the present application provides a method for identifying remote UE services when bearer multiplexing is required in the secondary link relay architecture, which can make relay UE operations more orderly, reduce the number of bearers and schedule transmission
  • the complexity of the remote UE guarantees the service experience and system efficiency of the remote UE.
  • the network device 1200 includes: an antenna 1201 , a radio frequency device 1202 , and a baseband device 1203 .
  • the antenna 1201 is connected to the radio frequency device 1202 .
  • the radio frequency device 1202 receives information through the antenna 1201, and sends the received information to the baseband device 1203 for processing.
  • the baseband device 1203 processes the information to be sent and sends it to the radio frequency device 1202
  • the radio frequency device 1202 processes the received information and sends it out through the antenna 1201 .
  • the above-mentioned frequency band processing apparatus may be located in the baseband apparatus 1203 , and the method performed by the network side device in the above embodiments may be implemented in the baseband apparatus 1203 .
  • the baseband apparatus 1203 includes a processor 1204 and a memory 1205 .
  • the baseband device 1203 may include, for example, at least one baseband board on which a plurality of chips are arranged, as shown in FIG. 12 , one of the chips is, for example, the processor 1204 , which is connected to the memory 1205 to call the program in the memory 1205 to execute
  • the network devices shown in the above method embodiments operate.
  • the baseband device 1203 may further include a network interface 1206 for exchanging information with the radio frequency device 1202, and the interface is, for example, a common public radio interface (CPRI for short).
  • CPRI common public radio interface
  • the network-side device in 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 invokes the instructions or programs in the memory 1205 to execute the modules shown in FIG. 8 .
  • An embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, each process of the foregoing remote terminal service identification method embodiment is implemented, and The same technical effect can be achieved, and in order to avoid repetition, details are not repeated here.
  • the processor is the processor in the terminal described in the foregoing embodiment.
  • the readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.
  • An embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a network-side device program or instruction to implement the above-mentioned remote terminal.
  • the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-a-chip, or the like.
  • An embodiment of the present application further provides a computer software product, the computer software product is executed by at least one processor to implement each process of the foregoing remote terminal service identification method embodiment, and can achieve the same technical effect, in order to avoid repetition , which will not be repeated here.
  • the computer software product may be a computer program or a program product.
  • the terms "comprising”, “comprising” or any other variation thereof are intended to encompass non-exclusive inclusion, such that a process, method, article or device comprising a series of elements includes not only those elements, It also includes other elements not expressly listed or inherent to such a process, method, article or apparatus. Without further limitation, an element qualified by the phrase “comprising a" does not preclude the presence of additional identical elements in a process, method, article or apparatus that includes the element.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种远端终端业务识别方法、装置、设备及存储介质，属于通信技术领域。所述方法包括：接收第一远端终端发送的第一消息；确定用于转发所述第一消息的中继承载信道；通过所述中继承载信道向对端通信设备转发所述第一消息，所述第一消息的数据包头中携带所述第一远端终端的终端标识和/或承载标识；其中，所述对端通信设备为网络侧设备、下一跳中继终端或第二远端终端。本申请实施例中在进行远端终端的业务复用过程中对不同远端终端的业务进行区分，能够使中继终端将不同远端终端的不同业务复用在同一个传输通道中传输，提高了传输的效率，并考虑整体效率，在提升用户体验的同时保障了系统效率。

Description

远端终端业务识别方法、装置、设备及存储介质
优先权申明
本申请主张在2020年12月14提交中国专利局、申请号为：202011476469.4的中国专利申请的优先权，其全部内容通过引用包含于此。
技术领域
本申请属于通信技术领域，具体涉及一种远端终端业务识别方法、装置、设备及存储介质。
背景技术
长期演进(Long Term Evolution，LTE)系统从第12个发布版本开始支持侧链路
(sidelink，或译为副链路、边链路等)，用于终端(User Equipment，UE)之间不通过网络侧设备直接进行数据传输。典型的sidelink中继relay场景中，远端终端(remote UE)通过和中继终端(relay UE)之间的sidelink链路，由relay UE将它的数据与基站之间进行转发。在这个场景中，remote UE和基站之间进行数据传输，relay UE起到数据中转作用。
在相关技术中，在远端终端的面向Uu接口的分组数据汇聚协议(Uu Packet Data Convergence Protocol，简称Uu PDCP)层下面，有一个适配层(adaptation layer)，主要用于进行remote UE的业务复用，将多个remote UE的业务可以复用到一个Uu RB(Radio Bearer，无线承载)中进行传输。但是相关技术仅仅提出了adaptation layer的基本功能，并未给出adaptation layer如何在进行remote UE的业务复用过程中，对不同remote UE的业务进行区分的解决方案。因此adaptation layer目前是无法进行工作的。
发明内容
本申请实施例的目的是提供一种远端终端业务识别方法、装置、设备及存储介质，能够解决相关技术中在进行remote UE的业务复用过程中对不同remote UE的业务进行区分的问题。
为了解决上述技术问题，本申请是这样实现的：
第一方面，提供了一种远端终端业务识别方法，应用于中继终端，该方法包括：接收第一远端终端发送的第一消息；确定用于转发所述第一消息的中继承载信道；通过所述中继承载信道向对端通信设备转发所述第一消息，所述第一消息的数据包头中携带所述第一远端终端的终端标识和/或承载标识；其中，所述对端通信设备为网络侧设备、下一跳中继终端或第二远端终端。
第二方面，提供了一种远端终端业务识别方法，应用于网络侧设备，该方法包括：接收中继终端通过中继承载信道发送的第一消息；其中，所述第一消息的数据包头中携带第一远端终端的终端标识和/或承载标识。
第三方面，提供了一种远端终端业务识别方法，应用于远端终端，包括：接收中继终端通过中继承载信道发送的第一消息；其中，所述第一消息的数据包头中携带第一远端终端的终端标识和/或第一远端终端的承载标识。
第四方面，提供了一种远端终端业务识别装置，应用于中继终端，该装置包括：第一接收单元，用于接收第一远端终端发送的第一消息；第一处理单元，用于确定用于转发所述第一消息的中继承载信道；第一发送单元，用于通过所述中继承载信道向对端通信设备转发所述第一消息，所述第一消息的数据包头中携带所述第一远端终端的终端标识和/或承载标识；其中，所述对端通信设备为网络侧设备、下一跳中继终端或第二远端终端。
第五方面，提供了一种远端终端业务识别装置，应用于网络侧设备，该装置包括：第五接收单元，用于接收中继终端通过中继承载信道发送的第一消息；其中，所述第一消息的数据包头中携带第一远端终端的终端标识和/或承载标识。
第六方面，提供了一种远端终端业务识别装置，应用于终端，该装置包括：第六接收单元，用于接收中继终端通过中继承载信道发送的第一消息；其中，所述第一消息的数据包头中携带第一远端终端的终端标识和/或第一远端终端的承载标识。
第七方面，提供了一种终端，该终端包括处理器、存储器及存储在所述存储器上并可在所述 处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤，或者实现如第三方面所述的方法的步骤。
第八方面，提供了一种网络侧设备，该网络侧设备包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第二方面所述的方法的步骤。
第九方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤，或者实现如第二方面所述的方法的步骤，或者实现如第三方面所述的方法的步骤。
第十方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行终端或网络侧设备程序或指令，实现如第一方面所述的方法，或者实现如第二方面所述的方法，或者实现第三方面所述的方法。
在本申请实施例中，在进行remote UE的业务复用过程中对不同remote UE的业务进行区分，能够使中继终端将不同远端终端的不同业务复用在同一个传输通道中传输，提高了传输的效率，并且同时提供远端终端业务在端到端传输中的可识别性，从而保障了远端终端业务的服务质量，并考虑整体效率，在提升用户体验的同时保障了系统效率。
附图说明
图1为本申请实施例可应用的无线通信系统的框图；
图2为相关技术中L2 relay协议栈架构示意图；
图3为本申请实施例提供的远端终端业务识别方法的流程示意图之一；
图4为本申请实施例提供的两个UE同时通过一个relay UE连接到网络的示意图；
图5为本申请实施例提供的远端终端业务识别方法的流程示意图之二；
图6为本申请实施例提供的远端终端业务识别方法的流程示意图之三；
图7为本申请实施例提供的远端终端业务识别装置的结构示意图之一；
图8为本申请实施例提供的远端终端业务识别装置的结构示意图之二；
图9为本申请实施例提供的远端终端业务识别装置的结构示意图之三；
图10为实现本申请实施例的一种通信设备的结构示意图；
图11为实现本申请实施例的一种终端的硬件结构示意图；
图12为实现本申请实施例的一种网络侧设备的硬件结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(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)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和 无线电技术。然而，以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR术语，尽管这些技术也可应用于NR系统应用以外的应用，如第6代(6 th Generation，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括远端终端11、网络侧设备12以及中继终端13。其中，远端终端11/中继终端13也可以称作终端设备或者用户终端(User Equipment，UE)，远端终端11/中继终端13可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、可穿戴式设备(Wearable Device)或车载设备(VUE)、行人终端(PUE)等终端侧设备，可穿戴式设备包括：手环、耳机、眼镜等。需要说明的是，在本申请实施例并不限定终端的具体类型。网络侧设备12可以是基站或核心网，其中，基站可被称为节点B、演进节点B、接入点、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、B节点、演进型B节点(eNB)、5G网络架构(next generation system)中的5G基站(gNB)、家用B节点、家用演进型B节点、WLAN接入点、WiFi节点、发送接收点(Transmitting Receiving Point，TRP)或所述领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例，但是并不限定基站的具体类型。
下面结合附图，通过具体的实施例及其应用场景对本申请实施例提供的基于中继终端的切换方法、装置、设备及存储介质进行详细地说明。
为了便于更好地理解本申请实施例，首先对Sidelink Relay进行描述。
图2为相关技术中L2 relay协议栈架构示意图，图2显示了远端终端通过中继终端与网络侧设备通信时(即基于中继承载进行通信时)使用的一种L2中继协议栈,。
中继终端和网络侧设备之间具有Uu PDCP协议栈，在该Uu PDCP协议栈中，将包含若干个用于远端终端的数据传输的无线承载(Radio Bearer，RB)。
在中继终端的Uu PDCP协议栈下面，有一个适配层(Adaptation Layer)，如图2中的ADAPT，Adaptation Layer，是一个新的协议层，主要进行remote UE的业务复用，将多个remote UE的业务可以复用到一个Uu RB(Radio Bearer)中进行传输。
由于中继终端自身也有数据传输，因此该适配层需要区分中继终端和远端终端的数据，或者不同远端终端的数据。具体地，适配层逻辑实体需要区分数据是来自/去往远端终端还是中继终端的，以及数据属于哪个远端终端的哪个承载。在适配协议层的下方是面向Uu接口的无线链路控制层(Radio Link Control，RLC)、媒体接入控制协议层(Medium Access Control，MAC)和物理层(Physical，PHY)。另外，在PC5接口，即remote UE和relay UE之间，也可以有adaptation layer，用于进行业务复用。
在现有技术中，仅提出了adaptation layer的基本功能，并未给出adaptation layer如何进行不同remote UE的业务区分、UE ID内容如何确定以及UE ID如何分配的解决方案。因此adaptation layer目前是无法进行工作的。
图3为本申请实施例提供的远端终端业务识别方法的流程示意图之一，该方法的执行主体为中继终端relay UE，如图3所示，该方法包括以下步骤：
步骤300、接收第一远端终端发送的第一消息；可以理解的是，在远端终端remote UE与中继终端relay UE满足进行中继通信的条件下，remote UE通过PC5接口向relay UE发送第一消息。其中，PC5接口是remote UE与relay UE之间的Sidelink链路接口。所述第一消息是第一远端终端发送给对端通信设备的，经由relay UE转发给对端通信设备。
在本申请实施例中，第一消息的承载类型可以是信令无线承载(Signaling Radio Bearer,SRB)0、SRB1、SRB2或数据无线承载(Data Radio Bearer,DRB)。中继终端relay UE则通过PC5接口接收第一远端终端发送的第一消息。
需要说明的是，第一远端终端发送的第一消息中可以携带所述第一远端终端的终端标识和/或承载标识，也可以不携带所述第一远端终端的终端标识和/或承载标识。
步骤301、确定用于转发所述第一消息的中继承载信道。
在本申请实施例中，relay UE可以将映射到同一个无线链路控制信道的每个远端终端的业务复用到同一大管道中进行传输，也可以将来自同一远端终端到不同对端通信设备的业务进行复用。relay UE接收到第一远端终端发送的第一消息后，需要确定通过哪条中继承载信道将该第一消息转发给对端通信设备。
可以理解的是，中继承载信道用于承载远端终端的端到端RB数据，中继承载信道可以是中继无线链路控制信道relayed RLC channel。
可选的，relay UE基于所述第一消息对应的PC5接口的逻辑信道标识或者所述第一消息的SRB0标识或者所述第一远端终端的端到端承载标识，确定用于转发所述第一消息的中继承载信道。
步骤302、通过所述中继承载信道向对端通信设备转发所述第一消息，所述第一消息的数据包头中携带所述第一远端终端的终端标识和/或承载标识；relay UE通过所述中继承载信道向对端通信设备转发所述第一消息，并在所述第一消息的数据包头中携带所述第一远端终端的终端标识UE ID和/或承载标识RB ID，网络侧设备根据该第一消息的数据包头中携带的UE ID和/或RB ID，可以区分来自不同remote UE的承载，从而实现了对远端终端remote UE的业务的识别。
可选的，在本申请实施例中，所述对端通信设备可以为网络侧设备、下一跳中继终端或第二远端终端。
本申请实施例的应用场景可以为U2N(UE to NW)场景，即Remote UE<–>relay UE<–>NW，其中可以多跳，即有多个串行relay UE，其中距离remote UE最近的一个relay UE记作access relay UE，与NW连接的relay UE记作根relay UE的场景中，当前relay UE与下一跳或者前一跳relay UE之间，根relay UE和NW之间，access relay UE与remote UE之间，如果需要进行承载复用，可以使用UE ID和/或RB ID来区分remote UE及承载。
本申请实施例的应用场景可以为U2U(UE to UE)场景，即Source remote UE<–>relay UE<–>Target remote UE，其中，可以多跳，即有多个串行relay UE，其中距离source remote UE最近的一个relay UE记作access relay UE，与target remote UE连接的relay UE记作根relay UE的场景中，当前relay UE与下一跳或者前一跳relay UE之间，根relay UE和target remote UE之间，access relay UE与source remote UE之间，如果需要进行承载复用，可以使用UE ID和/或RB ID来区分remote UE及承载。
在本申请实施例中，在进行remote UE的业务复用过程中对不同remote UE的业务进行区分，能够使中继终端将不同远端终端的不同业务复用在同一个传输通道中传输，提高了传输的效率，并且同时提供远端终端业务在端到端传输中的可识别性，从而保障了远端终端业务的服务质量，并考虑整体效率，在提升用户体验的同时保障了系统效率。
可选的，所述确定用于转发所述第一消息的中继承载信道，包括：
基于所述第一消息对应的PC5接口的逻辑信道标识或者所述第一消息的SRB0标识或者所述第一远端终端的端到端承载标识，确定所述第一消息的类型；
在所述第一消息的类型为SRB0消息的情况下，确定用于转发所述第一消息的中继承载信道为第一缺省无线链路控制信道；或者，在所述第一消息的类型不是SRB0消息的情况下，基于无线承载数据的类型与无线链路控制信道之间的映射关系，确定用于转发所述第一消息的中继承载信道为与所述第一消息的类型具有映射关系的无线链路控制信道。
可以理解的是，relay UE首先基于所述第一消息对应的PC5接口的逻辑信道标识或者所述第一消息的SRB0标识或者所述第一远端终端的端到端承载标识，确定所述第一消息的类型，进而基于所述第一消息的类型确定中继承载通道。
由于SRB0消息是无线资源控制(Radio Resource Control，RRC)建立Setup请求 Request，relay UE需要有一个default relayed RLC channel配置，用于承载SRB0消息。因此，在本申请实施例中将第一消息的类型分为两类：SRB0消息和非SRB0消息。
为了实现承载复用，网络侧设备需要为SRB0消息配置第一缺省无线链路控制信道。其中，所述第一缺省无线链路控制信道用于承载SRB0消息。网络侧设备还需要为其他非SRB0消息配置映射关系，所述映射关系具体为无线承载数据的类型与无线链路控制信道之间的映射关系。
在所述第一消息的类型为SRB0消息的情况下，relay UE确定用于转发所述第一消息的中继承载信道为第一缺省无线链路控制信道。
在所述第一消息的类型不是SRB0消息的情况下，relay UE基于无线承载数据的类型与无线链路控制信道之间的映射关系，确定用于转发所述第一消息的中继承载信道为与所述第一消息的类型具有映射关系的无线链路控制信道。
在一个实施例中，relay UE基于所述第一消息的对应的PC5接口的逻辑信道标识，确定所述第一消息的类型，进而基于所述第一消息的类型确定中继承载通道。
在PC5接口上的数据区分可以采取如下方式：将不同的Uu RB和PC5 RB之间一一映射，以进行识别和区分。例如PC5接口上逻辑信道0-3是现有的PC5signling，逻辑信道4和5为legacy PC5业务，逻辑信道10承载remote UE Uu SRB0，逻辑信道11承载remote UE Uu SRB1，逻辑信道12承载remote UE Uu SRB2，逻辑信道14承载remote UE Uu DRB1，逻辑信道15承载remote UE Uu DRB2，等等。
图4为本申请实施例提供的两个UE同时通过一个relay UE连接到网络的示意图。如图4所示，在PC5接口，每个remote UE和relay UE之间可能有legacy的PC5SRBs，PC5DRBs,RLC channels for Uu SRBs和RLC channels for Uu DRBs等。每一个类型的承载，都可以是一个独立的管道，便于relay UE进行数据区分。
例如，Remote UE1与relay UE之间的逻辑信道如下划分：逻辑信道0-3：分别对应PC5 SRB0，SRB1，SRB2和SRB3，这是现有的PC5承载类型；逻辑信道4-14：分别对应PC5 DRB1到DRB11；逻辑信道15：为默认的或者配置的relayed RLC channel用于承载remote UE1的Uu SRB0；逻辑信道16-17：为配置的relayed RLC channel用于承载remote UE1的Uu SRB1和SRB2；逻辑信道18-31：为配置的relayed RLC channel用于承载remote UE1的Uu DRB1到DRB14；32-63的区间用于Uu接口，扩展的逻辑信道。
Relay UE接收到上述PC5承载内容，对PC5接口的承载，直接按照现有流程处理。对于RLC channel来的数据，需要向网络侧设备进行转发。
relay UE接收到第一消息后，基于所述第一消息的对应的PC5接口的逻辑信道标识，可以确定第一消息的类型，例如，若relay UE接收到的第一消息对应的PC5接口的逻辑信道标识为15时，因为逻辑信道15用于承载Uu SRB0，进而可以确定此时第一消息的类型为SRB0消息。
在一个实施例中，relay UE基于所述第一消息的SRB0标识，确定所述第一消息的类型，进而确定用于转发所述第一消息的中继承载信道。例如，第一消息的SRB0标识为0，说明第一消息不是SRB0消息，则可以基于网络侧配置的无线承载数据的类型与无线链路控制信道RLC channel之间的映射关系，确定用于转发所述第一消息的中继承载信道。若第一消息的SRB0标识为1，说明第一消息是SRB0消息，则将第一缺省无线链路控制信道default relayed RLC channel作为第一消息的中继承载信道。
可选的，relay UE基于所述第一远端终端的端到端承载标识，确定所述第一消息的类型，进而确定用于转发所述第一消息的中继承载信道。其中，所述第一远端终端的端到端承载标识是指该第一远端终端与网络侧通信的的RB ID，例如remote UE Uu SRB0，其RB ID＝0，remote UE SRB1，其RB ID＝1，remote UE SRB2，其RB ID＝2，其余的DRB，通过端到端的RRC过程进行配置并分配RB ID。例如，所述第一远端终端的端到端承载标识为1，则所述第一消息的类型为SRB1消息，relay UE基于网络侧配置的无线承载数据的类型与无线链路控制信道RLC channel之间的映射关系，确定用于转发所述第一消息的中继承载信道。
在一些可选的实施例中，所述确定用于转发所述第一消息的中继承载信道，还包括：
在所述第一消息的类型不是SRB0消息，并且，与所述第一消息的类型具有映射关系的无线链路控制信道不存在的情况下，确定用于转发所述第一消息的中继承载信道为网络侧配置的第二缺省无线链路控制信道。
在某些情形下，网络侧并未配置所述第一消息的类型与无线链路控制信道的映射关系，则将第二缺省无线链路控制信道作为用于转发所述第一消息的中继承载信道。其中，所述第二缺省无线链路控制信道用于承载没有配置映射关系的远端终端的无线承载数据。
所述第二缺省无线链路控制信道与所述第一缺省中继无线链路控制信道相同或不同。
在本申请实施例中，基于远端终端发送的第一消息对应的PC5接口的逻辑信道标识或者SRB0标识或者端到端承载标识，确定中继承载通信道，实现了将不同远端终端的不同业务复用在同一个传输通道中传输，提高了传输的效率。
可选的，所述终端标识包括以下各项中的一项：PC5链路层2标识PC5 link L2 ID；
所述PC5 link L2 ID的部分比特位；远端终端在中继终端内的唯一索引；远端终端在网络侧设备内的唯一索引。
在本申请实施例中，终端标识UE ID可以使用终端标识的PC5链路层2标识PC5 link L2 ID，PC5 link L2 ID是remote UE和relay UE在PC5接口进行通信时使用的L2 ID，长度为24bit。
由于PC5 link L2 ID是现有PC5通信使用的ID，能确保在一定范围内能唯一确定UE身份，使用较为便利。但是缺点是开销较大，每个UE都需要使用24bit进行标识和区分。
为了节省开销，也可以将24bit L2 ID进行截短，例如取其中低位的16bit，但节省开销的代价是有可能发生UE ID重复的情况。
UE ID的主要目的是区分链接到同一个relay UE的不同remote UE，或者，区分映射到同一个无线链路控制信道的不同remote UE，因此，还可以考虑使用其他的定义和分配的方式，以获得较小的UE ID长度，从而节省开销，提高资源利用率。
在一些可选的实施例中，终端标识也可以是远端终端在中继终端内的唯一索引，即也可以是中继终端为远端终端分配的唯一索引。
可选的，所述远端终端业务识别方法，还包括：为连接到所述中继终端的每个远端终端分配终端标识索引；或者，为映射到同一个无线链路控制信道的每个远端终端分配终端标识索引。
为了降低开销，在一个实施例中，UE ID定义为所有连接到同一个relay UE的remote UE的标号/索引index。中继终端relay UE为连接到该relay UE的每个远端终端分配终端标识索引，一个远端终端对应一个唯一的终端标识索引。
以U2N架构为例，一个relay UE由于其处理能力有限，同时能够服务的UE数量将会有一个上限，例如将这个上限定为N，则通过这个relay UE与网络进行通信的remote UE的标号index可以在区间[0，N-1]内，每个标号唯一标识一个remote UE。在relay UE内部，存储remote UE index和真正的L2 ID之间的对应关系，进而就可以进行正确的通信。对于NW，则需要存储RRC信令里携带的UE身份和remote UE index之间的映射关系，以进行正确的UE数据的收发和处理。
可选的，在一个实施例中，UE ID定义为映射到同一个无线链路控制信道的remote UE的索引。即中继终端relay UE为映射到同一个无线链路控制信道的每个远端终端分配终端标识索引。
可选的，所述远端终端业务识别方法，还包括：通过无线资源控制RRC消息或UP过程，向所述终端标识索引对应的远端终端的对端通信设备发送所述终端标识索引。
中继终端relay UE为远端终端分配了终端标识索引后，通过无线资源控制RRC消息或UP过程，向所述终端标识索引对应的远端终端的对端通信设备发送所述终端标识索引。
举例来说，当第一个remote UE连接到一个relay UE时，relay UE可以给它分配UE index＝0，并用UE index＝0和RB ID将该remote UE的SRB0消息RRC Setup request发送给网络，网络侧设备接收到之后将setup消息里的UE身份和relay UE下的UE index＝0进行关联，那么后 续发送给这个UE的所有下行消息和下行数据都使用UE index＝0和对应的RB ID进行区分，并在中继承载通道里发送给relay UE。Relay UE接收到之后，也可以通过UE index＝0识别到对应的remote UE，使用remote UE L2 ID进行PC5通信将数据发送给正确的remote UE。UE index由relay UE分配并通知NW。
在一些可选的实施例中，终端标识也可以是网络侧设备为远端终端分配的唯一索引。
所有连接到relay UE的remote UE由于他们的第一条消息为SRB0消息时，网络并没有任何这个remote UE的先验信息，因此可以采取一个特殊的Uu管道，这个Uu RLC channel并不携带任何remote UE ID和RB ID信息，即没有adaptation layer header，所有remote UE的SRB0消息都放在这里传输，不用区分。NW接收到之后，解读消息确定UE身份，再给该UE分配一个relay UE内唯一的UE index。
有如下两种方式通知relay UE网络侧为remote UE分配的终端标识索引index。
可选的，所述远端终端业务识别方法，还包括：接收网络侧设备发送的无线资源控制RRC消息，所述RRC消息携带网络侧设备为发送了SRB0消息的远端终端分配的终端标识索引。
可选的，网络侧设备通过和relay UE之间的RRC消息，告知relay UE给这个remote UE分配了index，其中在所述RRC消息里区分remote UE，就可以采取使用RRC setup request(即SRB0消息)的部分内容，例如其中的40bit来标识remote UE，由于RRC setup request消息里是含有UE身份的，网络侧通过复制全部或者部分该内容，来指示UE，对于relay UE来说，需要将为remote UE转发的RRC setup request消息进行备份缓存，一旦relay UE接收到配置消息，通过对比，即可得知是对哪个remote UE分配了Index，后续将remote UE的L2 ID和index关联进行存储，以进行后续中转数据传输。
可选的，所述远端终端业务识别方法，还包括：接收网络侧设备发送的控制协议数据单元/第一数据包，所述控制协议数据单元/第一数据包携带了发送了SRB0消息的远端终端的身份信息和所述网络侧设备为所述发送了SRB0消息的远端终端分配的终端标识索引；
根据所述身份信息，确定所述终端标识索引对应的远端终端。
网络侧设备通过用户面(User Plane,UP)过程告知relay UE关于index的分配，具体方式是使用UP的控制协议数据单元control PDU，携带index和setup request消息里的remote UE身份信息，relay UE读到之后，可以获知网络侧设备给remote UE分配了对应的index。
可选的，网络侧设备发送第一数据包，所述第一数据包中携带新分配的UE index和remote UE身份信息，relay UE解读之后，也可以建立正确的remote UE和index之间的关联，以进行后续中转数据传输。
在建立好remote UE的对应index之后，后续的收发包就可以用这个index对remote UE的数据进行标识，便于正确理解数据的归属。一般来说，一个relay UE下连接的remote UE个数不会太多，例如32或者16个，因此在此种方式中用于区分remote UE的index只需要几个比特，不超过一个字节，因此大大节省了开销。
需要说明的是，在U2U的架构中，也可以采取类似的方式，由relay UE为每个连接到它的remote UE分配一个唯一的index，以标识不同的remote UE。分配的方法，可以采取relay UE和remote UE之间的PC5 RRC告知。
可选的，所述承载标识包括以下各项中的一项：端到端承载标识；映射到同一个无线链路控制信道的远端终端所对应的承载的标号。
在一些可选的实施例中，承载标识RB ID可以直接使用remote UE跟NW通信的端到端的RB ID，例如remote UE Uu SRB0，其RB ID＝0，remote UE SRB1，其RB ID＝1，remote UE SRB2，其RB ID＝2，其余的DRB，通过端到端的RRC过程进行配置并分配RB ID。
在一些可选的实施例中，承载标识RB ID也可以是映射到同一个无线链路控制信道的远端终端所对应的承载标号。
由于现有的端到端的承载个数是最大支持32个，即RB ID如果标识端到端承载需要5bit。而对于一个remote UE内部能够复用到同一个大传输管道的RB个数并没有很多，需要QoS相 同或者接近，例如最多4个RB，那么RB ID的长度就可以减少到2bit。相当于需要通知RB的映射关系，映射举例说明如下表1所示。
表1 RB映射关系
映射之前 映射之后
RB 1 in Remote UE 1 Channel 1，remote UE1，RB＝0
RB 2 in Remote UE 1 Channel 1，remote UE1，RB＝1
RB 3 in Remote UE 1 Channel 1，remote UE1，RB＝2
RB 4 in Remote UE 1 Channel 2，remote UE1，RB＝0
RB 5 in Remote UE 1 Channel 2，remote UE1，RB＝1
… …
相当于需要通知的是，自由的32bit的传统端到端RB ID，映射到：
RLC channel x的index y。决策方式是通过QoS相同或者相近的原则，选择对应的RLC channel，然后看看这个remote UE是否有其它RB映射到这个RLC channel，对映射到同一个RLC channel的RB在进行一次小组内排序即可。
建立和通知映射的方式如下：对于信令无线承载来说，由于Uu SRB(用于U2N场景)和PC5SRB(用于U2U场景)个数有限且作用比较明确，每个remote UE必须有这些SRB，因此可以采取固定映射的方式，默认或者提前配置好SRB映射到default RLC channel n，且RB index也都固定好。
对于DRB来说，因为DRB具有突发性和多样性特点，因此只有业务到达之后，才通过Uu RRC(用于U2N场景)由基站配置给relay UE，或者PC5 RRC(用于U2U场景)由relay UE配置给两端的remote UE；配置好后，即可以进行正常的通信。
可选的，所述远端终端业务识别方法，还包括：为映射到同一个无线链路控制信道的每个远端终端分配承载标号。
可以理解的是，relay UE为映射到同一个无线链路控制信道的每个远端终端分配承载标号，并通过PC5 RRC消息配置给相应的remote UE。例如，Remote UE 1和relay UE之间，可以将不同的target UE 2，target UE 3，target UE 4的数据进行复用，分配的承载标号可以分别对应于：UE 1和UE 2之间的端到端承载，UE 1和UE 3之间的端到端承载，UE1和UE 4之间的端到端承载。例如，在relay UE和target UE2之间，有不同的：
source UE 1，source UE 5，source UE 6，因此分配的承载标号可以分别对应于：UE 1和UE2之间的端到端承载，UE 5和UE2之间的端到端承载，UE 6和UE2之间的端到端承载。
U2N场景类似，在此不再赘述。
在本申请实施例中，中继终端或网络侧设备为remote UE分配终端标识索引和/或承载标号，在进行remote UE的业务复用过程中对不同remote UE的业务进行区分，使中继终端将不同远端终端的不同业务复用在同一个传输通道中传输，提高了传输的效率，并且资源开销较小。
可选的，在上述实施例的基础上，所述远端终端业务识别方法，还包括：接收所述对端通信设备发送的第二消息；基于所述第二消息的数据包头中携带的终端标识和/或承载标识，将所述第二消息转发给相应的远端终端。
可以理解的是，relay UE接收所述对端通信设备发送的第二消息，例如，若第一消息为RRC Setup request消息，则第二消息为RRC Setup消息。然后，基于所述第二消息的数据包头中携带的终端标识和/或承载标识，将所述第二消息转发给相应的远端终端。
可选的，在上述实施例的基础上，所述接收第一远端终端发送的第一消息之前，还包括：在第一远端终端满足建立中继通信的条件，且中继终端与所述第一远端终端之间的链路质量以及中继终端与第一通信设备之间的链路质量满足建立中继通信的条件的情况下，通过PC5接口与所述第一远端终端进行交互，确定所述中继终端具备中转所述第一远端终端业务的能力。例如remote UE处于小区边缘，RSRP低于一个网络配置的门限，不能直接跟NW进行通信，这时候需要经由relay UE进行中转它的数据到网络，此时第一终端满足建立中继通信的条件。
relay UE也需要满足一定的条件，中继终端与所述第一远端终端之间的链路质量以及中继终端与第一通信设备之间的链路质量满足建立中继通信的条件，才能确保后续通信正常进行。
在满足上述基本链路条件之后，remote UE和relay UE之间，需要通过PC5过程，交互中转业务信息，例如进行discovery过程，需要确保relay UE可以进行remote UE将要发起的业务的中转服务。
可选的，所述第一消息的适配层协议头中携带所述第一远端终端的终端标识和/或所述第一远端终端的承载标识。
需要说明的是，本申请中提到的UE ID和RB ID可以用于适配层adaptation layer，包含在adaptation layer header中。但并不限于此，所有需要进行数据复用的协议层都可以使用。
下面结合具体的应用场景来说明如何使用UE ID和RB ID来区分不同remote UE的承载。
在U2N架构中，以L2 Remote UE<–>relay UE<–>NW场景为例，说明如何使用UE ID和RB ID来区分不同remote UE的承载，从而进行正常的relay通信。
首先，关于UE ID和RB ID的含义和取值，本例中采取如下原则：UE ID为PC5 link L2 ID，RB ID为端到端承载标识。下面给出remote UE建立L2 relay U2N通信，以及在relay和NW之间如何进行承载复用的过程：
步骤a，remote UE满足建立L2 relay U2N通信的条件，找到一个合适的relay UE。例如remote UE处于小区边缘，RSRP低于一个网络配置的门限，不能直接跟NW进行通信，这时候需要经由relay UE进行中转它的数据到网络。
relay UE也需要满足一定的条件，例如relay UE自己本身到NW的链路条件足够好，RSRP高于一个网络配置的门限，可选的，relay UE到NW的链路条件不能太好，即同时满足RSRP低于一个网络配置的门限，这样做的好处是避免小区中心的UE做relay UE干扰过大。
Remote UE和relay UE之间的PC5的链路质量也需要满足一定的门限，即PC5 RSRP(Reference Signal Receiving Power，参考信号接收功率)高于门限，才能确保后续通信正常进行。
在满足上述基本链路条件之后，remote UE和relay UE之间，需要通过PC5过程，交互中转业务信息，例如进行discovery过程，需要确保relay UE可以进行remote UE将要发起的业务的中转服务。
步骤b：relay UE在决定给remote UE进行业务中转服务之后，需要在自己的Uu接口进行一定的准备工作，例如需要有一个default relayed RLC channel配置，至少用于承载没有配置映射关系的remote UE的端到端RB数据。
举例说明，如果这个relay UE之前没有进入Connected状态，则为了中转数据，需要先进入Connected状态，并告知网络侧请求为其它remote UE进行数据中转，网络侧需要给这个relay UE配置一个default relayed RLC channel，它的特点是，配置为RLC AM(Acknowledge Mode)或者UM(UnAcknowledge Mode)，具有adaptation layer且有header，adaptation layer header里包含UE ID和RB ID，且没有任何映射关系的remote UE数据默认映射到这一条RLC channel上。
如果这个relay UE已经在Connected状态，且它还有自己的Uu数据传输，或者还有其它remote UE的中转数据传输，则此时很可能default relayed RLC channel已经存在，可以承载没有任何映射关系的remote UE数据。
举个例子：relay UE的Uu口逻辑信道号：0为自己的SRB0消息，1为自己的SRB1消息，2为自己的SRB2消息，4为自己的第一条DRB,5为自己的第二条DRB,10为default relayed RLC channel，用于承载没有映射关系的relay数据，11-13为其它relayed RLC channel，承载配置了映射关系的其它remote UE的不同QoS的数据。
步骤c：remote UE发送第一条Uu消息——RRC Setup Request，这个消息是发送给NW的，但需要先发送给relay UE并由其中转。Remote UE通过PC5接口将第一条Uu消息发送给relay UE；Relay UE接收到第一条消息之后，使用步骤b中得到的自己的default relayed RLC channel来发送这个第一条消息，其中该数据包的adaptation header里携带remote UE L2 ID以及 RB ID，由于第一条消息为SRB0消息，则RB ID＝0。
步骤d：网络侧通过default relayed RLC channel接收relay发来的数据，进行处理，并对其进行响应，发送RRC Setup消息(携带L2 ID和RB ID＝0)；其中，根据UE ID可以知道这是一个新的remote UE(因为未缓存该UE的配置)，通过RB ID＝0，可以知道是remote UE的SRB0消息，解读消息，并进行正常处理，响应生成RRC Setup消息。对这个RRC Setup消息，网络侧在下行的default relayed RLC channel上进行发送，将adaptation header的UE ID填写接收到的L2 ID,RB ID＝0,表明仍旧是SRB0进行发送。
由于RRC Setup消息，一般是建立SRB1，那么网络侧也需要对这个remote UE的SRB1在Uu接口上如何映射进行配置，并将配置的映射关系发送给relay UE，即可以使用现有的一个relayed RLC channel或者建立一个新的relayed RLC channel将这个remote UE的SRB1映射上去，其中remote UE使用UE ID＝L2 ID进行标识。
步骤e：relay UE接收到RRC setup消息，从adaptation header里读取的UE ID，可以找到对应的remote UE，则在PC5接口上将RRC Setup消息转发给相应的remote UE。
步骤f：remote UE接收到RRC Setup消息，则按照消息中的配置建立SRB1，并发送后续的RRC Setup complete消息在新建立的SRB1上。
后续步骤不再赘述，SRB1在relay UE Uu的relayed RLC channel mapping和配置已经提前准备好，后续relay UE使用remote UE对应的L2 ID和RB ID＝1，即可告知NW这是该remote UE的SRB1消息，下行同理。
并且针对remote UE的SRB2和DRB，也是类似的，通过SRB1管道即RRC信令过程，先配置SRB2和DRB的relay Uu RLC channel mapping，再将配置好的SRB2和DRB的relay Uu RLC channel mapping发送给remote UE。
建立好之后relay和NW之间，就可以在一个relay Uu RLC channel中使用L2 ID和端到端RB ID，来明确的区分不同remote UE和具体承载内容(SRB0/1/2/DRB)。
下面介绍U2U场景下如何使用UE ID和RB ID来区分不同remote UE的承载。
在U2U架构中，以L2 Source remote UE<–>relay UE<–>Target remote UE场景为例，说明如何使用UE ID和RB ID来区分不同remote UE的承载，从而进行正常的relay通信。
首先，关于UE ID和RB ID的含义和取值，本例中采取如下原则：UE ID为PC5 link L2 ID，RB ID为端到端承载标识。
在relay UE和Target remote UE(简称第二跳)之间，relay UE可以把多个source remote UE(因为他们的target remote UE是同一个UE)的数据进行复用，以降低第二跳可能出现的承载个数：每个source remote UE仍旧以各自的L2 ID来进行区分，这个L2 ID是需要能够被target remote UE识别的，例如在discovery过程中，交互了彼此的L2 ID；这里使用的L2 ID可以与source remote UE与relay UE之间PC5通信时使用的L2 ID是相同的，也可以是不同的。如果不同，意味着source remote UE至少有两个L2 ID，其中一个用于与relay UE之间进行PC5传输，另一个L2 ID用于source remote UE和target remote UE端到端通信时标识自己，如果是两个L2 ID，则relay UE需要存储两个L2 ID的对应关系，以便于在不同的场景进行使用，例如relay UE在PC5接口通过第一个L2 ID接收到source remote UE的数据，需要通过第一个L2 ID，找到对应的第二个L2 ID，放到adaptation layer header里用于在第二跳标识source remote UE；并携带对应的RB ID，以标识是哪个source remote UE的哪个承载，这里RB ID仍使用source remote UE和target remote UE之间的端到端的RB ID，例如SRB 0-3对应RB 0-3，其余DRB由source和target之间通过RRC信令过程进行建立并分配RB ID之后，再进行使用。
在Source remote UE和relay UE(简称第一跳)之间，relay UE可以把同一个source remote UE到不同的target remote UE的数据进行复用，以降低第一跳可能出现的承载个数：每个target remote UE仍旧以各自的L2 ID来进行区分，这个L2 ID是需要能够被source remote UE识别的，例如在discovery过程中，交互了彼此的L2 ID；这里使用的L2 ID可以与target remote UE与relay UE之间PC5通信时使用的L2 ID是相同的，也可以是不同的，如果不同，意味着target  remote UE至少有两个L2 ID，其中一个用于与relay UE之间进行PC5传输，另一个L2 ID用于target remote UE和source remote UE端到端通信时标识自己，如果是两个L2 ID，则relay UE需要存储两个L2 ID的对应关系，以便于在不同的场景进行使用；并携带对应的RB ID，以标识是哪个source remote UE的哪个承载，原理同上；
可选的，为了进一步降低复杂度并在第一跳和第二跳拥有相同的adaptation layer数据包格式，也可以：在第一跳同时携带source remote UE L2 ID和target remote UE L2 ID，前者标识不同的source UE，后者标识不同的target UE，并且后者还可以在多跳网络中起到路由作用；同样在UE ID之外，需要RB ID，区分不同承载，原理同上。
图5为本申请实施例提供的远端终端业务识别方法的示意图之二，执行主体为网络侧设备，该方法包括：步骤500、接收中继终端通过中继承载信道发送的第一消息，所述第一消息的数据包头中携带第一远端终端的终端标识和/或承载标识。本实施例中，网络侧设备作为对端通信设备，接收中继终端通过中继承载信道转发的第一消息。网络侧设备根据该第一消息的数据包头中携带的UE ID和/或RB ID，可以区分来自不同remote UE的承载，从而实现了对远端终端remote UE的业务的识别。
在本申请实施例中，在进行remote UE的业务复用过程中对不同remote UE的业务进行区分，能够使中继终端将不同远端终端的不同业务复用在同一个传输通道中传输，提高了传输的效率，并且同时提供远端终端业务在端到端传输中的可识别性，从而保障了远端终端业务的服务质量，并考虑整体效率，在提升用户体验的同时保障了系统效率。
在一些可选的实施例中，所述终端标识包括以下各项中的一项：PC5链路层2标识PC5 link L2 ID或所述PC5 link L2 ID的部分比特位；远端终端在中继终端内的唯一索引；远端终端在网络侧设备内的唯一索引。关于终端标识的相关内容可以参考前述实施例中的有关描述，在此不再赘述。
在一些可选的实施例中，所述承载标识包括以下各项中的一项：远端终端的端到端承载标识；映射到同一个无线链路控制信道的远端终端所对应的承载的标号。关于承载标识的相关内容可以参考前述实施例中的有关描述，在此不再赘述。
在一些可选的实施例中，所述远端终端业务识别方法，还包括：向中继终端发送无线承载的配置信息；其中，所述无线承载的配置信息携带所述无线承载数据的类型与无线链路控制信道之间的映射关系。
为了实现承载复用，网络侧设备需要为不同类型的无线承载数据配置相应的无线链路控制信道。例如，为SRB0消息配置default relayed RLC channel，为非SRB0消息配置对应的RLC channel。
可选的，网络侧设备向中继终端发送无线承载的配置信息；其中，所述无线承载的配置信息携带所述无线承载数据的类型与无线链路控制信道之间的映射关系。
在一些可选的实施例中，所述第一消息的适配层协议头中携带第一远端终端的终端标识和/或第一远端终端的承载标识。
在一些可选的实施例中，所述远端终端业务识别方法，还包括：接收中继终端转发的SRB0消息，确定发送所述SRB0消息的远端终端的身份信息；为发送所述SRB0消息的远端终端分配终端标识索引，并通过无线资源控制RRC消息或UP过程，将所述终端标识索引发送给中继终端。
可选的，终端标识也可以是网络侧设备为远端终端分配的唯一索引。
网络接收中继终端转发的SRB0消息，对所述SRB0消息进行解读，确定发送所述SRB0消息的远端终端的身份信息。
然后，为发送所述SRB0消息的远端终端分配终端标识索引，并通过无线资源控制RRC消息或UP过程，将所述终端标识索引发送给中继终端。
可选的，所述通过无线资源控制RRC消息或UP过程，将所述终端标识索引发送给中继终端，包括：向所述中继终端发送RRC消息，所述RRC消息携带所述终端标识索引；或者，通过 UP过程向所述中继终端发送控制协议数据单元/第一数据包，所述控制协议数据单元/第一数据包携带了发送所述SRB0消息的远端终端的身份信息和所述发送了SRB0消息的远端终端对应的终端标识索引。
在一些可选的实施例中，所述远端终端业务识别方法，还包括：为覆盖范围内的每个远端终端分配唯一的终端标识索引。
在本申请实施例中，提供另一种可行的用于UE ID定义的方式，使得UE ID的长度可以位于完整L2 ID 24bit和relay内唯一的index长度之间，给remote UE分配cell内唯一的标识，一般为2个字节长度，以区分不同的remote UE。
由于U2N场景中，remote UE和relay UE都处于连接态位于网络控制下，因此网络侧设备可以为每个remote UE分配一个自己管辖范围内的唯一index，用于区分和标识。网络侧设备配置index的方式，可以通过控制面(Control Plane，CP)过程或者用户面UP过程，通过setup request的remote UE身份标识和configured index的各种通知方式，建立remote UE和index的关联，用于后续通信。
在U2U场景中，由于relay UE要中转很多数据，也大概率处于连接态受网络的调度，因此可以从网络侧设备获得remote UE和index的关联，用于后续通信。如果relay UE并不处于连接态，或者是脱网状态，则index只能由relay UE自行决定。
在一些可选的实施例中，所述远端终端业务识别方法，还包括：为映射到同一个无线链路控制信道的每个远端终端分配承载标号。
可以理解的是，在U2N场景下，网络侧设备为映射到同一个无线链路控制信道的每个remote UE分配承载标号，并通过RRC消息配置给relay UE。在U2U场景下，若relay UE处于连接态，则该relay UE会将每个remote UE的情况上报给网络，由网络统一分配每个remote UE对应的承载标号。
本申请实施例给出了在副链路中继架构中需要进行承载复用时，对远端UE业务的识别方法，能够使得relay UE操作更有序的进行，降低了承载数目和调度传输的复杂度，保障了remote UE的业务体验和系统效率。
图6为本申请实施例提供的远端终端业务识别方法的流程示意图之三，应用于远端终端，包括：
步骤600、接收中继终端通过中继承载信道发送的第一消息，所述第一消息的数据包头中携带第一远端终端的终端标识和/或第一远端终端的承载标识。
本实施例中，远端终端作为对端通信设备，接收中继终端通过中继承载信道转发的第一消息。
远端设备根据该第一消息的数据包头中携带的UE ID和/或RB ID，可以区分来自不同remote UE的承载，从而实现了对远端终端remote UE的业务的识别。
可选的，所述终端标识包括以下各项中的一项：PC5链路层2标识PC5 link L2 ID或所述PC5 link L2 ID的部分比特位；远端终端在中继终端内的唯一索引；远端终端在网络侧设备内的唯一索引。关于终端标识的相关内容可以参考前述实施例中的有关描述，在此不再赘述。
可选的，所述承载标识包括以下各项中的一项：远端终端的端到端承载标识；映射到同一个无线链路控制信道的远端终端所对应的承载的标号。关于承载标识的相关内容可以参考前述实施例中的有关描述，在此不再赘述。
可选的，所述第一消息的适配层协议头中携带第一远端终端的终端标识和/或承载标识。
本申请实施例给出了在副链路中继架构中需要进行承载复用时，对远端UE业务的识别方法，能够使得relay UE操作更有序的进行，降低了承载数目和调度传输的复杂度，保障了remote UE的业务体验和系统效率。
需要说明的是，本申请实施例提供的远端终端业务识别方法，执行主体可以为远端终端业务识别装置，或者，该远端终端业务识别装置中的用于执行远端终端业务识别方法的控制模块。本申请实施例中以远端终端业务识别装置执行远端终端业务识别方法为例，说明本申请实施例提供 的远端终端业务识别装置。
图7为本申请实施例提供的远端终端业务识别装置的结构示意图之一，包括：第一接收单元710、第一处理单元720和第一发送单元730，其中，第一接收单元710，用于接收第一远端终端发送的第一消息；第一处理单元720，用于确定用于转发所述第一消息的中继承载信道；第一发送单元730，用于通过所述中继承载信道向对端通信设备转发所述第一消息，所述第一消息的数据包头中携带所述第一远端终端的终端标识和/或承载标识；其中，所述对端通信设备为网络侧设备、下一跳中继终端或第二远端终端。
在本申请实施例中，在进行remote UE的业务复用过程中对不同remote UE的业务进行区分，能够使中继终端将不同远端终端的不同业务复用在同一个传输通道中传输，提高了传输的效率，并且同时提供远端终端业务在端到端传输中的可识别性，从而保障了远端终端业务的服务质量，并考虑整体效率，在提升用户体验的同时保障了系统效率。
可选的，所述第一处理单元720，用于：基于所述第一消息对应的PC5接口的逻辑信道标识或者所述第一消息的SRB0标识或者所述第一远端终端的端到端承载标识，确定所述第一消息的类型；在所述第一消息的类型为SRB0消息的情况下，确定用于转发所述第一消息的中继承载信道为第一缺省无线链路控制信道；或者，在所述第一消息的类型不是SRB0消息的情况下，基于无线承载数据的类型与无线链路控制信道之间的映射关系，确定用于转发所述第一消息的中继承载信道为与所述第一消息的类型具有映射关系的无线链路控制信道。
可选的，所述第一处理单元720，还用于：在所述第一消息的类型不是SRB0消息，并且，与所述第一消息的类型具有映射关系的无线链路控制信道不存在的情况下，确定用于转发所述第一消息的中继承载信道为网络侧配置的第二缺省无线链路控制信道；其中，所述第二缺省无线链路控制信道与所述第一缺省中继无线链路控制信道相同或不同。可选的，所述终端标识包括以下各项中的一项：PC5链路层2标识PC5 link L2 ID或所述PC5 link L2 ID的部分比特位；远端终端在中继终端内的唯一索引；远端终端在网络侧设备内的唯一索引。
可选的，所述承载标识包括以下各项中的一项：端到端承载标识；映射到同一个无线链路控制信道的远端终端所对应的承载的标号。
可选的，还包括第一配置单元，用于：为连接到所述中继终端的每个远端终端分配终端标识索引；或者，为映射到同一个无线链路控制信道的每个远端终端分配终端标识索引。
可选的，还包括：第二发送单元，用于通过无线资源控制RRC消息或UP过程，向所述终端标识索引对应的远端终端的对端通信设备发送所述终端标识索引。
可选的，还包括：第二接收单元，用于接收网络侧设备发送的无线资源控制RRC消息，所述RRC消息携带网络侧设备为发送了SRB0消息的远端终端分配的终端标识索引。
可选的，还包括：第三接收单元，用于接收网络侧设备发送的控制协议数据单元/第一数据包，所述控制协议数据单元/第一数据包携带了发送了SRB0消息的远端终端的身份信息和所述网络侧设备为所述发送了SRB0消息的远端终端分配的终端标识索引；第二处理单元，用于根据所述身份信息，确定所述终端标识索引对应的远端终端。
可选的，还包括：第二配置单元，用于为映射到同一个无线链路控制信道的每个远端终端分配承载标号。
可选的，还包括：第四接收单元，用于接收所述对端通信设备发送的第二消息；第三处理单元，用于基于所述第二消息的数据包头中携带的终端标识和/或承载标识，将所述第二消息转发给相应的远端终端。
可选的，所述接收第一远端终端发送的第一消息之前，还包括：第四处理单元，用于在第一远端终端满足建立中继通信的条件，且中继终端与所述第一远端终端之间的链路质量以及中继终端与第一通信设备之间的链路质量满足建立中继通信的条件的情况下，通过PC5接口与所述第一远端终端进行交互，确定所述中继终端具备中转所述第一远端终端业务的能力。
可选的，所述第一消息的适配层协议头中携带所述第一远端终端的终端标识和/或所述第一远端终端的承载标识。
在本申请实施例中，中继终端或网络侧设备为remote UE分配终端标识索引和/或承载标号，在进行remote UE的业务复用过程中对不同remote UE的业务进行区分，使中继终端将不同远端终端的不同业务复用在同一个传输通道中传输，提高了传输的效率，并且资源开销较小。
本申请实施例中的远端终端业务识别装置可以是装置，也可以是终端中的部件、集成电路、或芯片。该装置可以是移动终端，也可以为非移动终端。示例性的，移动终端可以包括但不限于上述所列举的远端终端11/中继终端13的类型，非移动终端可以为服务器、网络附属存储器(Network Attached Storage，NAS)、个人计算机(personal computer，PC)、电视机(television，TV)、柜员机或者自助机等，本申请实施例不作具体限定。本申请实施例中的远端终端业务识别装置可以为具有操作系统的装置。该操作系统可以为安卓(Android)操作系统，可以为ios操作系统，还可以为其他可能的操作系统，本申请实施例不作具体限定。
本申请实施例提供的远端终端业务识别装置能够实现图3至图4的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
图8为本申请实施例提供的远端终端业务识别装置的结构示意图之二，包括：第五接收单元810，用于接收中继终端通过中继承载信道发送的第一消息；其中，所述第一消息的数据包头中携带第一远端终端的终端标识和/或承载标识。可选的，所述终端标识包括以下各项中的一项：PC5链路层2标识PC5 link L2 ID或所述PC5 link L2 ID的部分比特位；远端终端在中继终端内的唯一索引；远端终端在网络侧设备内的唯一索引。
可选的，所述承载标识包括以下各项中的一项：远端终端的端到端承载标识；映射到同一个无线链路控制信道的远端终端所对应的承载的标号。
可选的，还包括：第三发送单元，用于向中继终端发送无线承载的配置信息；其中，所述无线承载的配置信息携带所述无线承载数据的类型与无线链路控制信道之间的映射关系。
可选的，所述第一消息的适配层协议头中携带第一远端终端的终端标识和/或第一远端终端的承载标识。
可选的，还包括：第五处理单元，用于接收中继终端转发的SRB0消息，确定发送所述SRB0消息的远端终端的身份信息；第三配置单元，用于为发送所述SRB0消息的远端终端分配终端标识索引；第四发送单元，用于通过无线资源控制RRC消息或UP过程，将所述终端标识索引发送给中继终端。
可选的，所述第四发送单元，用于：向所述中继终端发送RRC消息，所述RRC消息携带所述终端标识索引；或者，通过UP过程向所述中继终端发送控制协议数据单元/第一数据包，所述控制协议数据单元/第一数据包携带了发送所述SRB0消息的远端终端的身份信息和所述发送了SRB0消息的远端终端对应的终端标识索引。
可选的，还包括：第四配置单元，用于为覆盖范围内的每个远端终端分配唯一的终端标识索引。
可选的，还包括：第五配置单元，用于为映射到同一个无线链路控制信道的每个远端终端分配承载标号。
在本申请实施例中，在进行remote UE的业务复用过程中对不同remote UE的业务进行区分，能够使中继终端将不同远端终端的不同业务复用在同一个传输通道中传输，提高了传输的效率，并且同时提供远端终端业务在端到端传输中的可识别性，从而保障了远端终端业务的服务质量，并考虑整体效率，在提升用户体验的同时保障了系统效率。
本申请实施例中的远端终端业务识别装置可以是装置，也可以是终端中的部件、集成电路、或芯片。该装置可以是移动终端，也可以为非移动终端。示例性的，移动终端可以包括但不限于上述所列举的远端终端11/中继终端13的类型，非移动终端可以为服务器、网络附属存储器(Network Attached Storage，NAS)、个人计算机(personal computer，PC)、电视机(television，TV)、柜员机或者自助机等，本申请实施例不作具体限定。
本申请实施例中的远端终端业务识别装置可以为具有操作系统的装置。该操作系统可以为安卓(Android)操作系统，可以为ios操作系统，还可以为其他可能的操作系统，本申请实施例不 作具体限定。
本申请实施例提供的远端终端业务识别装置能够实现图5的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
图9为本申请实施例提供的远端终端业务识别装置的结构示意图之三，包括：第六接收单元910，用于接收中继终端通过中继承载信道发送的第一消息；其中，所述第一消息的数据包头中携带第一远端终端的终端标识和/或第一远端终端的承载标识。
可选的，所述终端标识包括以下各项中的一项：PC5链路层2标识PC5 link L2 ID或所述PC5 link L2 ID的部分比特位；远端终端在中继终端内的唯一索引；远端终端在网络侧设备内的唯一索引。可选的，所述承载标识包括以下各项中的一项：远端终端的端到端承载标识；映射到同一个无线链路控制信道的远端终端所对应的承载的标号。
可选的，所述第一消息的适配层协议头中携带第一远端终端的终端标识和/或承载标识。
在本申请实施例中，在进行remote UE的业务复用过程中对不同remote UE的业务进行区分，能够使中继终端将不同远端终端的不同业务复用在同一个传输通道中传输，提高了传输的效率，并且同时提供远端终端业务在端到端传输中的可识别性，从而保障了远端终端业务的服务质量，并考虑整体效率，在提升用户体验的同时保障了系统效率。
本申请实施例中的远端终端业务识别装置可以是装置，也可以是终端中的部件、集成电路、或芯片。该装置可以是移动终端，也可以为非移动终端。示例性的，移动终端可以包括但不限于上述所列举的远端终端11/中继终端13的类型，非移动终端可以为服务器、网络附属存储器(Network Attached Storage，NAS)、个人计算机(personal computer，PC)、电视机(television，TV)、柜员机或者自助机等，本申请实施例不作具体限定。
本申请实施例中的远端终端业务识别装置可以为具有操作系统的装置。该操作系统可以为安卓(Android)操作系统，可以为ios操作系统，还可以为其他可能的操作系统，本申请实施例不作具体限定。
本申请实施例提供的远端终端业务识别装置能够实现图6的方法实施例实现的各个过程，并达到相同的技术效果，为避免重复，这里不再赘述。
可选的，如图10所示，本申请实施例还提供一种通信设备1000，包括处理器1001，存储器1002，存储在存储器1002上并可在所述处理器1001上运行的程序或指令，例如，该通信设备1000为终端时，该程序或指令被处理器1001执行时实现上述远端终端业务识别方法实施例的各个过程，且能达到相同的技术效果。该通信设备1000为网络侧设备时，该程序或指令被处理器1001执行时实现上述远端终端业务识别方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
图11为实现本申请实施例的一种终端的硬件结构示意图。该终端1100包括但不限于：射频单元1101、网络模块1102、音频输出单元1103、输入单元1104、传感器1105、显示单元1106、用户输入单元1107、接口单元1108、存储器1109、以及处理器1110等部件。
本领域技术人员可以理解，终端1100还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器1110逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图11中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元1104可以包括图形处理器(Graphics Processing Unit，GPU)11041和麦克风11042，图形处理器11041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元1106可包括显示面板11061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板11061。用户输入单元1107包括触控面板11071以及其他输入设备11072。触控面板11071，也称为触摸屏。触控面板11071可包括触摸检测装置和触摸控制器两个部分。其他输入设备11072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元1101将来自网络侧设备的下行数据接收后，给处理器1110处理；另外，将上行的数据发送给网络侧设备。通常，射频单元1101包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器1109可用于存储软件程序或指令以及各种数据。存储器1109可主要包括存储程序或指令区和存储数据区，其中，存储程序或指令区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器1109可以包括高速随机存取存储器，还可以包括非易失性存储器，其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。
处理器1110可包括一个或多个处理单元；可选的，处理器1110可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序或指令等，调制解调处理器主要处理无线通信，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器1110中。其中，射频单元1101，用于接收第一远端终端发送的第一消息；处理器1110，用于确定用于转发所述第一消息的中继承载信道；通过所述中继承载信道向对端通信设备转发所述第一消息，所述第一消息的数据包头中携带所述第一远端终端的终端标识和/或承载标识；其中，所述对端通信设备为网络侧设备、下一跳中继终端或第二远端终端。
在本申请实施例中，在进行remote UE的业务复用过程中对不同remote UE的业务进行区分，能够使中继终端将不同远端终端的不同业务复用在同一个传输通道中传输，提高了传输的效率，并且同时提供远端终端业务在端到端传输中的可识别性，从而保障了远端终端业务的服务质量，并考虑整体效率，在提升用户体验的同时保障了系统效率。
可选的，处理器1110用于：基于所述第一消息对应的PC5接口的逻辑信道标识或者所述第一消息的SRB0标识或者所述第一远端终端的端到端承载标识，确定所述第一消息的类型；在所述第一消息的类型为SRB0消息的情况下，确定用于转发所述第一消息的中继承载信道为第一缺省无线链路控制信道；或者，在所述第一消息的类型不是SRB0消息的情况下，基于无线承载数据的类型与无线链路控制信道之间的映射关系，确定用于转发所述第一消息的中继承载信道为与所述第一消息的类型具有映射关系的无线链路控制信道。
可选的，处理器1110还用于：在所述第一消息的类型不是SRB0消息，并且，与所述第一消息的类型具有映射关系的无线链路控制信道不存在的情况下，确定用于转发所述第一消息的中继承载信道为网络侧配置的第二缺省无线链路控制信道；其中，所述第二缺省无线链路控制信道与所述第一缺省中继无线链路控制信道相同或不同。
可选的，所述终端标识包括以下各项中的一项：PC5链路层2标识PC5 link L2 ID；所述PC5 link L2 ID的部分比特位；远端终端在中继终端内的唯一索引；远端终端在网络侧设备内的唯一索引。
可选的，所述承载标识包括以下各项中的一项：端到端承载标识；映射到同一个无线链路控制信道的远端终端所对应的承载的标号。
可选的，处理器1110，还用于：为连接到所述中继终端的每个远端终端分配终端标识索引；或者，为映射到同一个无线链路控制信道的每个远端终端分配终端标识索引。
可选的，处理器1110，还用于：通过无线资源控制RRC消息或UP过程，向所述终端标识索引对应的远端终端的对端通信设备发送所述终端标识索引。
可选的，处理器1110，还用于：接收网络侧设备发送的无线资源控制RRC消息，所述RRC消息携带网络侧设备为发送了SRB0消息的远端终端分配的终端标识索引。
可选的，处理器110，还用于：接收网络侧设备发送的控制协议数据单元/第一数据包，所述控制协议数据单元/第一数据包携带了发送了SRB0消息的远端终端的身份信息和所述网络侧设备为所述发送了SRB0消息的远端终端分配的终端标识索引；根据所述身份信息，确定所述终端标识索引对应的远端终端。
可选的，处理器1110，还用于：为映射到同一个无线链路控制信道的每个远端终端分配承载标号。
可选的，处理器1110，还用于：接收所述对端通信设备发送的第二消息；基于所述第二消息的数据包头中携带的终端标识和/或承载标识，将所述第二消息转发给相应的远端终端。
可选的，处理器1110，还用于：在第一远端终端满足建立中继通信的条件，且中继终端与所述第一远端终端之间的链路质量以及中继终端与第一通信设备之间的链路质量满足建立中继通信的条件的情况下，通过PC5接口与所述第一远端终端进行交互，确定所述中继终端具备中转所述第一远端终端业务的能力。
可选的，所述第一消息的适配层协议头中携带所述第一远端终端的终端标识和/或所述第一远端终端的承载标识。
在本申请实施例中，中继终端或网络侧设备为remote UE分配终端标识索引和/或承载标号，在进行remote UE的业务复用过程中对不同remote UE的业务进行区分，使中继终端将不同远端终端的不同业务复用在同一个传输通道中传输，提高了传输的效率，并且资源开销较小。
在一个实施例中，可选的，射频单元1101用于接收中继终端通过中继承载信道发送的第一消息；其中，所述第一消息的数据包头中携带第一远端终端的终端标识和/或第一远端终端的承载标识。
可选的，所述终端标识包括以下各项中的一项：PC5链路层2标识PC5 link L2 ID或所述PC5 link L2 ID的部分比特位；远端终端在中继终端内的唯一索引；远端终端在网络侧设备内的唯一索引。
可选的，所述承载标识包括以下各项中的一项：远端终端的端到端承载标识；映射到同一个无线链路控制信道的远端终端所对应的承载的标号。
可选的，所述第一消息的适配层协议头中携带第一远端终端的终端标识和/或承载标识。
本申请实施例给出了在副链路中继架构中需要进行承载复用时，对远端UE业务进行识别的方法，能够使得relay UE操作更有序的进行，降低了承载数目和调度传输的复杂度，保障了remote UE的业务体验和系统效率。
本申请实施例还提供了一种网络侧设备。如图12所示，该网络设备1200包括：天线1201、射频装置1202、基带装置1203。天线1201与射频装置1202连接。在上行方向上，射频装置1202通过天线1201接收信息，将接收的信息发送给基带装置1203进行处理。在下行方向上，基带装置1203对要发送的信息进行处理，并发送给射频装置1202，射频装置1202对收到的信息进行处理后经过天线1201发送出去。
上述频带处理装置可以位于基带装置1203中，以上实施例中网络侧设备执行的方法可以在基带装置1203中实现，该基带装置1203包括处理器1204和存储器1205。
基带装置1203例如可以包括至少一个基带板，该基带板上设置有多个芯片，如图12所示，其中一个芯片例如为处理器1204，与存储器1205连接，以调用存储器1205中的程序，执行以上方法实施例中所示的网络设备操作。
该基带装置1203还可以包括网络接口1206，用于与射频装置1202交互信息，该接口例如为通用公共无线接口(common public radio interface，简称CPRI)。
具体地，本发明实施例的网络侧设备还包括：存储在存储器1205上并可在处理器1204上运行的指令或程序，处理器1204调用存储器1205中的指令或程序执行图8所示各模块执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述远端终端业务识别方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述处理器为上述实施例中所述的终端中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行网络侧设备程序或指令，实现上述远端终端业务识别方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
本申请实施例另提供了一种计算机软件产品，所述计算机软件产品被至少一个处理器执行以实现上述远端终端业务识别方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
需要说明的是，所述计算机软件产品，可以是计算机程序，也可以是程序产品。需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (58)

  1. 一种远端终端业务识别方法，包括：
    中继终端接收第一远端终端发送的第一消息；
    所述中继终端确定用于转发所述第一消息的中继承载信道；
    所述中继终端通过所述中继承载信道向对端通信设备转发所述第一消息，所述第一消息的数据包头中携带所述第一远端终端的终端标识和/或承载标识；
    其中，所述对端通信设备为网络侧设备、下一跳中继终端或第二远端终端。
  2. 根据权利要求1所述的远端终端业务识别方法，其中，所述中继终端确定用于转发所述第一消息的中继承载信道，包括：
    所述中继终端基于所述第一消息对应的PC5接口的逻辑信道标识或者所述第一消息的SRB0标识或者所述第一远端终端的端到端承载标识，确定所述第一消息的类型；
    在所述第一消息的类型为SRB0消息的情况下，所述中继终端确定用于转发所述第一消息的中继承载信道为第一缺省无线链路控制信道；或者，
    在所述第一消息的类型不是SRB0消息的情况下，所述中继终端基于无线承载数据的类型与无线链路控制信道之间的映射关系，确定用于转发所述第一消息的中继承载信道为与所述第一消息的类型具有映射关系的无线链路控制信道。
  3. 根据权利要求2所述的远端终端业务识别方法，其中，所述中继终端确定用于转发所述第一消息的中继承载信道，还包括：
    在所述第一消息的类型不是SRB0消息，并且，与所述第一消息的类型具有映射关系的无线链路控制信道不存在的情况下，所述中继终端确定用于转发所述第一消息的中继承载信道为网络侧配置的第二缺省无线链路控制信道；
    其中，所述第二缺省无线链路控制信道与所述第一缺省中继无线链路控制信道相同或不同。
  4. 根据权利要求1所述的远端终端业务识别方法，其中，所述终端标识包括以下各项中的一项：
    PC5链路层2标识PC5 link L2 ID；
    所述PC5 link L2 ID的部分比特位；
    远端终端在中继终端内的唯一索引；
    远端终端在网络侧设备内的唯一索引。
  5. 根据权利要求1所述的远端终端业务识别方法，其中，所述承载标识包括以下各项中的一项：
    端到端承载标识；
    映射到同一个无线链路控制信道的远端终端所对应的承载的标号。
  6. 根据权利要求1所述的远端终端业务识别方法，其中，还包括：
    所述中继终端为连接到所述中继终端的每个远端终端分配终端标识索引；或者，
    所述中继终端为映射到同一个无线链路控制信道的每个远端终端分配终端标识索引。
  7. 根据权利要求6所述的远端终端业务识别方法，其中，还包括：
    所述中继终端通过无线资源控制RRC消息或UP过程，向所述终端标识索引对应的远端终端的对端通信设备发送所述终端标识索引。
  8. 根据权利要求1所述的远端终端业务识别方法，其中，还包括：
    所述中继终端接收网络侧设备发送的无线资源控制RRC消息，所述RRC消息携带网络侧设备为发送了SRB053消息的远端终端分配的终端标识索引。
  9. 根据权利要求1所述的远端终端业务识别方法，其中，还包括：
    所述中继终端接收网络侧设备发送的控制协议数据单元/第一数据包，所述控制协议数据单元/第一数据包携带了发送了SRB0消息的远端终端的身份信息和所述网络侧设备为所述发送了SRB0消息的远端终端分配的终端标识索引；
    所述中继终端根据所述身份信息，确定所述终端标识索引对应的远端终端。
  10. 根据权利要求1所述的远端终端业务识别方法，其中，还包括：
    所述中继终端为映射到同一个无线链路控制信道的每个远端终端分配承载标号。
  11. 根据权利要求1所述的远端终端业务识别方法，其中，还包括：
    所述中继终端接收所述对端通信设备发送的第二消息；
    所述中继终端基于所述第二消息的数据包头中携带的终端标识和/或承载标识，将所述第二消息转发给相应的远端终端。
  12. 根据权利要求1所述的远端终端业务识别方法，其中，所述中继终端接收第一远端终端发送的第一消息之前，还包括：
    在第一远端终端满足建立中继通信的条件，且中继终端与所述第一远端终端之间的链路质量以及中继终端与第一通信设备之间的链路质量满足建立中继通信的条件的情况下，所述中继终端通过PC5接口与所述第一远端终端进行交互，确定所述中继终端具备中转所述第一远端终端业务的能力。
  13. 根据权利要求1所述的远端终端业务识别方法，其中，所述第一消息的适配层协议头中携带所述第一远端终端的终端标识和/或所述第一远端终端的承载标识。
  14. 一种远端终端业务识别方法，包括：
    网络侧设备接收中继终端通过中继承载信道发送的第一消息；
    其中，所述第一消息的数据包头中携带第一远端终端的终端标识和/或承载标识。
  15. 根据权利要求14所述的远端终端业务识别方法，其中，所述终端标识包括以下各项中的一项：
    PC5链路层2标识PC5 link L2 ID或所述PC5 link L2 ID的部分比特位；
    远端终端在中继终端内的唯一索引；
    远端终端在网络侧设备内的唯一索引。
  16. 根据权利要求14所述的远端终端业务识别方法，其中，所述承载标识包括以下各项中的一项：
    远端终端的端到端承载标识；
    映射到同一个无线链路控制信道的远端终端所对应的承载的标号。
  17. 根据权利要求14所述的远端终端业务识别方法，其中，还包括：
    所述网络侧设备向中继终端发送无线承载的配置信息；
    其中，所述无线承载的配置信息携带所述无线承载数据的类型与无线链路控制信道之间的映射关系。
  18. 根据权利要求14所述的远端终端业务识别方法，其中，所述第一消息的适配层协议头中携带第一远端终端的终端标识和/或第一远端终端的承载标识。
  19. 根据权利要求14所述的远端终端业务识别方法，其中，还包括：
    所述网络侧设备接收中继终端转发的SRB0消息，确定发送所述SRB0消息的远端终端的身份信息；
    所述网络侧设备为发送所述SRB0消息的远端终端分配终端标识索引，并通过无线资源控制RRC消息或UP过程，将所述终端标识索引发送给中继终端。
  20. 根据权利要求19所述的远端终端业务识别方法，其中，所述通过无线资源控制RRC消息或UP过程，将所述终端标识索引发送给中继终端，包括：
    所述网络侧设备向所述中继终端发送RRC消息，所述RRC消息携带所述终端标识索引；或者，
    所述网络侧设备通过UP过程向所述中继终端发送控制协议数据单元/第一数据包，所述控制协议数据单元/第一数据包携带了发送所述SRB0消息的远端终端的身份信息和所述发送了SRB0消息的远端终端对应的终端标识索引。
  21. 根据权利要求14所述的远端终端业务识别方法，其中，还包括：
    所述网络侧设备为覆盖范围内的每个远端终端分配唯一的终端标识索引。
  22. 根据权利要求14所述的远端终端业务识别方法，其中，还包括：
    所述网络侧设备为映射到同一个无线链路控制信道的每个远端终端分配承载标号。
  23. 一种远端终端业务识别方法，包括：
    远端终端接收中继终端通过中继承载信道发送的第一消息；
    其中，所述第一消息的数据包头中携带第一远端终端的终端标识和/或第一远端终端的承载标识。
  24. 根据权利要求23所述的远端终端业务识别方法，其中，所述终端标识包括以下各项中的一项：
    PC5链路层2标识PC5 link L2 ID或所述PC5 link L2 ID的部分比特位；
    远端终端在中继终端内的唯一索引；
    远端终端在网络侧设备内的唯一索引。
  25. 根据权利要求23所述的远端终端业务识别方法，其中，所述承载标识包括以下各项中的一项：
    远端终端的端到端承载标识；
    映射到同一个无线链路控制信道的远端终端所对应的承载的标号。
  26. 根据权利要求23所述的远端终端业务识别方法，其中，所述第一消息的适配层协议头中携带第一远端终端的终端标识和/或承载标识。
  27. 一种远端终端业务识别装置，包括：
    第一接收单元，用于接收第一远端终端发送的第一消息；
    第一处理单元，用于确定用于转发所述第一消息的中继承载信道；
    第一发送单元，用于通过所述中继承载信道向对端通信设备转发所述第一消息，所述第一消息的数据包头中携带所述第一远端终端的终端标识和/或承载标识；
    其中，所述对端通信设备为网络侧设备、下一跳中继终端或第二远端终端。
  28. 根据权利要求27所述的远端终端业务识别装置，其中，所述第一处理单元，用于：
    基于所述第一消息对应的PC5接口的逻辑信道标识或者所述第一消息的SRB0标识或者所述第一远端终端的端到端承载标识，确定所述第一消息的类型；
    在所述第一消息的类型为SRB0消息的情况下，确定用于转发所述第一消息的中继承载信道为第一缺省无线链路控制信道；或者，
    在所述第一消息的类型不是SRB0消息的情况下，基于无线承载数据的类型与无线链路控制信道之间的映射关系，确定用于转发所述第一消息的中继承载信道为与所述第一消息的类型具有映射关系的无线链路控制信道。
  29. 根据权利要求28所述的远端终端业务识别装置，其中，所述第一处理单元，还用于：
    在所述第一消息的类型不是SRB0消息，并且，与所述第一消息的类型具有映射关系的无线链路控制信道不存在的情况下，确定用于转发所述第一消息的中继承载信道为网络侧配置的第二缺省无线链路控制信道；
    其中，所述第二缺省无线链路控制信道与所述第一缺省中继无线链路控制信道相同或不同。
  30. 根据权利要求27所述的远端终端业务识别装置，其中，所述终端标识包括以下各项中的一项：
    PC5链路层2标识PC5 link L2 ID或所述PC5 link L2 ID的部分比特位；
    远端终端在中继终端内的唯一索引；
    远端终端在网络侧设备内的唯一索引。
  31. 根据权利要求27所述的远端终端业务识别装置，其中，所述承载标识包括以下各项中的一项：
    端到端承载标识；
    映射到同一个无线链路控制信道的远端终端所对应的承载的标号。
  32. 根据权利要求27所述的远端终端业务识别装置，其中，还包括第一配置单元，用于：
    为连接到所述中继终端的每个远端终端分配终端标识索引；或者，
    为映射到同一个无线链路控制信道的每个远端终端分配终端标识索引。
  33. 根据权利要求32所述的远端终端业务识别装置，其中，还包括：
    第二发送单元，用于通过无线资源控制RRC消息或UP过程，向所述终端标识索引对应的远端终端的对端通信设备发送所述终端标识索引。
  34. 根据权利要求27所述的远端终端业务识别装置，其中，还包括：
    第二接收单元，用于接收网络侧设备发送的无线资源控制RRC消息，所述RRC消息携带网络侧设备为发送了SRB0消息的远端终端分配的终端标识索引。
  35. 根据权利要求27所述的远端终端业务识别装置，其中，还包括：
    第三接收单元，用于接收网络侧设备发送的控制协议数据单元/第一数据包，所述控制协议数据单元/第一数据包携带了发送了SRB0消息的远端终端的身份信息和所述网络侧设备为所述发送了SRB0消息的远端终端分配的终端标识索引；
    第二处理单元，用于根据所述身份信息，确定所述终端标识索引对应的远端终端。
  36. 根据权利要求27所述的远端终端业务识别装置，其中，还包括：
    第二配置单元，用于为映射到同一个无线链路控制信道的每个远端终端分配承载标号。
  37. 根据权利要求27所述的远端终端业务识别装置，其中，还包括：
    第四接收单元，用于接收所述对端通信设备发送的第二消息；
    第三处理单元，用于基于所述第二消息的数据包头中携带的终端标识和/或承载标识，将所述第二消息转发给相应的远端终端。
  38. 根据权利要求27所述的远端终端业务识别装置，其中，所述接收第一远端终端发送的第一消息之前，还包括：
    第四处理单元，用于在第一远端终端满足建立中继通信的条件，且中继终端与所述第一远端终端之间的链路质量以及中继终端与第一通信设备之间的链路质量满足建立中继通信的条件的情况下，通过PC5接口与所述第一远端终端进行交互，确定所述中继终端具备中转所述第一远端终端业务的能力。
  39. 根据权利要求27所述的远端终端业务识别装置，其中，所述第一消息的适配层协议头中携带所述第一远端终端的终端标识和/或所述第一远端终端的承载标识。
  40. 一种远端终端业务识别装置，包括：
    第五接收单元，用于接收中继终端通过中继承载信道发送的第一消息；
    其中，所述第一消息的数据包头中携带第一远端终端的终端标识和/或承载标识。
  41. 根据权利要求40所述的远端终端业务识别装置，其中，所述终端标识包括以下各项中的一项：
    PC5链路层2标识PC5 link L2 ID或所述PC5 link L2 ID的部分比特位；
    远端终端在中继终端内的唯一索引；
    远端终端在网络侧设备内的唯一索引。
  42. 根据权利要求40所述的远端终端业务识别装置，其中，所述承载标识包括以下各项中的一项：
    远端终端的端到端承载标识；
    映射到同一个无线链路控制信道的远端终端所对应的承载的标号。
  43. 根据权利要求40所述的远端终端业务识别装置，其中，还包括：
    第三发送单元，用于向中继终端发送无线承载的配置信息；
    其中，所述无线承载的配置信息携带所述无线承载数据的类型与无线链路控制信道之间的映射关系。
  44. 根据权利要求40所述的远端终端业务识别装置，其中，所述第一消息的适配层协议头中携带第一远端终端的终端标识和/或第一远端终端的承载标识。
  45. 根据权利要求40所述的远端终端业务识别装置，其中，还包括：
    第五处理单元，用于接收中继终端转发的SRB0消息，确定发送所述SRB0消息的远端终端的身份信息；
    第三配置单元，用于为发送所述SRB0消息的远端终端分配终端标识索引；
    第四发送单元，用于通过无线资源控制RRC消息或UP过程，将所述终端标识索引发送给中继终端。
  46. 根据权利要求45所述的远端终端业务识别装置，其中，所述第四发送单元，用于：
    向所述中继终端发送RRC消息，所述RRC消息携带所述终端标识索引；或者，
    通过UP过程向所述中继终端发送控制协议数据单元/第一数据包，所述控制协议数据单元/第一数据包携带了发送所述SRB0消息的远端终端的身份信息和所述发送了SRB0消息的远端终端对应的终端标识索引。
  47. 根据权利要求40所述的远端终端业务识别装置，其中，还包括：
    第四配置单元，用于为覆盖范围内的每个远端终端分配唯一的终端标识索引。
  48. 根据权利要求40所述远端终端业务识别装置，其中，还包括：
    第五配置单元，用于为映射到同一个无线链路控制信道的每个远端终端分配承载标号。
  49. 一种远端终端业务识别装置，包括：
    第六接收单元，用于接收中继终端通过中继承载信道发送的第一消息；
    其中，所述第一消息的数据包头中携带第一远端终端的终端标识和/或第一远端终端的承载标识。
  50. 根据权利要求49所述的远端终端业务识别装置，其中，所述终端标识包括以下各项中的一项：PC5链路层2标识PC5 link L2 ID或所述PC5 link L2 ID的部分比特位；远端终端在中继终端内的唯一索引；远端终端在网络侧设备内的唯一索引。
  51. 根据权利要求49所述的远端终端业务识别装置，其中，所述承载标识包括以下各项中的一项：远端终端的端到端承载标识；映射到同一个无线链路控制信道的远端终端所对应的承载的标号。
  52. 根据权利要求49所述的远端终端业务识别装置，其中，所述第一消息的适配层协议头中携带第一远端终端的终端标识和/或承载标识。
  53. 一种终端，包括处理器，存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1-13任一项所述的远端终端业务识别方法的步骤，或者实现如权利要求23-26所述的远端终端业务识别方法的步骤。
  54. 一种网络侧设备，包括处理器，存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求14-22任一项所述的远端终端业务识别方法的步骤。
  55. 一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如权利要求1-13中任一项所述的远端终端业务识别方法的步骤，或者实现如权利要求14-22中任一项所述的远端终端业务识别方法的步骤，或者实现如权利要求23-26中任一项所述的远端终端业务识别方法的步骤。
  56. 一种计算机软件产品，所述计算机软件产品被至少一个处理器执行以实现如权利要求1-13中任一项所述的远端终端业务识别方法，或实现如权利要求14-22中任一项所述的远端终端业务识别方法，或者实现如权利要求23-26中任一项所述的远端终端业务识别方法。
  57. 一种电子设备，包括电子设备被配置成用于执行如权利要求1-13中任一项所述的远端终端业务识别方法，或实现如权利要求14-22中任一项所述的远端终端业务识别方法，或者实现如权利要求23-26中任一项所述的远端终端业务识别方法。
  58. 一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如权利要求1-13中任一项所述的远端终端业务识别方法，或实现如权利要求14-22中任一项所述的远端终端业务识别方法，或者实现如权利要求23-26中任一项所述的远端终端业务识别方法。
PCT/CN2021/135984 2020-12-14 2021-12-07 远端终端业务识别方法、装置、设备及存储介质 WO2022127644A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
KR1020237018873A KR20230098855A (ko) 2020-12-14 2021-12-07 원격단말 서비스 식별 방법, 장치, 기기 및 저장 매체
EP21905573.8A EP4216587A4 (en) 2020-12-14 2021-12-07 REMOTE USER EQUIPMENT SERVICE IDENTIFICATION METHOD AND APPARATUS, DEVICE AND STORAGE MEDIUM
JP2023527817A JP2023547724A (ja) 2020-12-14 2021-12-07 リモート端末業務識別方法、装置、機器及び記憶媒体
US18/308,591 US20230345462A1 (en) 2020-12-14 2023-04-27 Method and apparatus for identifying remote terminal service, device, and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011476469.4A CN114630389A (zh) 2020-12-14 2020-12-14 远端终端业务识别方法、装置、设备及存储介质
CN202011476469.4 2020-12-14

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/308,591 Continuation US20230345462A1 (en) 2020-12-14 2023-04-27 Method and apparatus for identifying remote terminal service, device, and storage medium

Publications (1)

Publication Number Publication Date
WO2022127644A1 true WO2022127644A1 (zh) 2022-06-23

Family

ID=81896973

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/135984 WO2022127644A1 (zh) 2020-12-14 2021-12-07 远端终端业务识别方法、装置、设备及存储介质

Country Status (6)

Country Link
US (1) US20230345462A1 (zh)
EP (1) EP4216587A4 (zh)
JP (1) JP2023547724A (zh)
KR (1) KR20230098855A (zh)
CN (1) CN114630389A (zh)
WO (1) WO2022127644A1 (zh)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117377024A (zh) * 2022-06-30 2024-01-09 维沃移动通信有限公司 标识配置方法、装置、终端及存储介质
CN115606312A (zh) * 2022-08-15 2023-01-13 北京小米移动软件有限公司（Cn） 数据传输方法、装置、存储介质及芯片
WO2024060239A1 (zh) * 2022-09-23 2024-03-28 Oppo广东移动通信有限公司 通信方法、装置、设备、存储介质及程序产品
WO2024097304A1 (en) * 2022-11-01 2024-05-10 Ofinno, Llc Lossless path switching
CN117998672A (zh) * 2022-11-04 2024-05-07 华为技术有限公司 链路配置方法、通信装置及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106658380A (zh) * 2016-12-30 2017-05-10 宇龙计算机通信科技(深圳)有限公司 一种设备与设备中继网络的数据复用方法及智能终端
WO2017206186A1 (zh) * 2016-06-03 2017-12-07 广东欧珀移动通信有限公司 中继传输的方法和装置
CN108496330A (zh) * 2016-03-30 2018-09-04 Oppo广东移动通信有限公司 中继传输的方法和装置
CN110326359A (zh) * 2017-03-31 2019-10-11 华为技术有限公司 中继通信方法、装置和系统
US20190394700A1 (en) * 2018-06-22 2019-12-26 T-Mobile Usa, Inc. Telecommunications between remote terminal and relay terminal

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10484517B2 (en) * 2017-02-10 2019-11-19 Qualcomm Incorporated Quality of service support for layer 2 based device-to-device relay
WO2019059638A1 (ko) * 2017-09-22 2019-03-28 주식회사 케이티 릴레이 노드의 데이터 처리 방법 및 그 장치

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108496330A (zh) * 2016-03-30 2018-09-04 Oppo广东移动通信有限公司 中继传输的方法和装置
WO2017206186A1 (zh) * 2016-06-03 2017-12-07 广东欧珀移动通信有限公司 中继传输的方法和装置
CN106658380A (zh) * 2016-12-30 2017-05-10 宇龙计算机通信科技(深圳)有限公司 一种设备与设备中继网络的数据复用方法及智能终端
CN110326359A (zh) * 2017-03-31 2019-10-11 华为技术有限公司 中继通信方法、装置和系统
US20190394700A1 (en) * 2018-06-22 2019-12-26 T-Mobile Usa, Inc. Telecommunications between remote terminal and relay terminal

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
INTEL CORPORATION: "Impact on user plane protocol stack and control plane procedure for Sidelink relay", 3GPP DRAFT; R2-2007608, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. E-meeting; 20200817 - 20200828, 7 August 2020 (2020-08-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051912267 *
See also references of EP4216587A4 *

Also Published As

Publication number Publication date
EP4216587A1 (en) 2023-07-26
EP4216587A4 (en) 2024-01-24
KR20230098855A (ko) 2023-07-04
CN114630389A (zh) 2022-06-14
US20230345462A1 (en) 2023-10-26
JP2023547724A (ja) 2023-11-13

Similar Documents

Publication Publication Date Title
WO2022127644A1 (zh) 远端终端业务识别方法、装置、设备及存储介质
US10880799B2 (en) Method for establishing a fronthaul interface, method for performing access for a UE, method and apparatus for performing a handover for a UE, data forwarding method, user equipment and base station
US10911999B2 (en) Mobile communication system, user terminal, base station, processor, and communication control method
WO2018053852A1 (zh) 无线承载的配置方法、装置及系统
CN111901847A (zh) sidelink中继通信方法、装置、设备及介质
CN106162930B (zh) 在设备直通系统中承载的管理方法和装置
CN108307536B (zh) 一种路由方法和设备
WO2018201687A1 (zh) 一种信令传输方法及设备、计算机可读存储介质
WO2017012467A1 (zh) 一种资源分配的方法和设备
WO2016161764A1 (zh) 一种中继承载控制方法、装置和计算机存储介质
WO2017028610A1 (zh) 设备到设备标识冲突的解决方法、设备到设备用户设备
US9820133B2 (en) Method and user equipment for performing D2D service in wireless communication system
US20170230784A1 (en) Method and apparatus for transmitting and receiving a data in a mesh network using bluetooth
WO2016202227A1 (zh) 一种层2链路标识的选择、通知方法及装置
US10425881B2 (en) User terminal, network apparatus, and processor
US20230261826A1 (en) Communication method and apparatus
WO2018137364A1 (zh) 数据发送方法、数据发送终端以及基站
JP2023530186A (ja) 中継決定方法、配置方法、装置、端末及びネットワーク側機器
CN111800238A (zh) 载波聚合参数配置方法、设备及系统
US20230370945A1 (en) Method, device, and system for relay configuration in wireless networks
US20230093763A1 (en) Bearer configuration method and apparatus, and terminal
WO2022057892A1 (zh) 业务数据传输方法及装置、终端和基站
WO2023001172A1 (zh) 推荐比特率确定方法、装置及相关设备
WO2022206505A1 (zh) 业务数据处理方法、装置及设备
WO2023151615A1 (zh) 处理sl bsr的方法、装置、通信设备及可读存储介质

Legal Events

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

Ref document number: 21905573

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021905573

Country of ref document: EP

Effective date: 20230421

WWE Wipo information: entry into national phase

Ref document number: 2023527817

Country of ref document: JP

ENP Entry into the national phase

Ref document number: 20237018873

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE