Communication method and apparatus, and terminal, chip, medium, program product and program

Abstract

Provided in the embodiments of the present application are a communication method and apparatus, and a terminal, a chip, a medium, a program product and a program. The method comprises: acquiring first information, the first information being used for identifying a data packet; and on the basis of the first information, executing at least one of the following: determining to process at a first node the data packet associated with the first information; and determining an egress of the data packet associated with the first information.

Description

Communication method and device, terminal, chip, medium, program product and program TECHNICAL FIELD

[0001] Embodiments of the present application relate to the field of mobile communication technology, in particular to a communication method and device, terminal, chip, medium, program product and program. BACKGROUND

[0002] Device to Device (D2D) communication is a kind of Sidelink (SL) transmission technology, which is different from the way of receiving or sending communication data through a base station in a cellular system. D2D uses a terminal-to-terminal direct communication mode, so it has higher spectrum efficiency and lower transmission delay.

[0003] D2D supports a single-hop scenario, in which only data transmission between a Remote UE and a network needs to be considered. In related technologies, a multi-hop relay scenario is introduced, in which the Remote UE and the network include multiple relay (Relay) devices. In this case, there are data transmissions between the Remote UE and the network (end-to-end multi-hop relay data), and there are data and signaling transmissions between two entities that are not end-to-end, such as between the Remote UE and the Relay UE2 or between the Relay1 and the network. However, the Relay UE cannot identify the two different data when receiving the data, resulting in the accuracy of communication.

[0004] SUMMARY

[0005] Embodiments of the present application provide a communication method and device, terminal, chip, medium, program product and program.

[0006] In a first aspect, embodiments of the present application provide a communication method applied to a first node, the method comprising:

[0007] obtaining first information, the first information being used to identify a data packet; wherein

[0008] based on the first information, performing at least one of the following:

[0009] determining to process the data packet associated with the first information at the first node;

[0010] determining an egress of the data packet associated with the first information.

[0011] In a second aspect, embodiments of the present application provide a communication device applied to a first node, the device comprising:

[0012] Obtaining first information, the first information being used to identify a data packet; wherein

[0013] Based on the first information, at least one of the following is performed:

[0014] Determining that the data packet associated with the first information is processed at the first node;

[0015] Determining an egress of the data packet associated with the first information.

[0016] In a third aspect, an embodiment of the present application provides a terminal, comprising a memory and a processor; wherein the memory is configured to store computer executable instructions; the processor is connected with the memory, and is configured to realize the method in the first aspect by executing the computer executable instructions.

[0017] In a fourth aspect, an embodiment of the present application provides a chip, comprising: a processor configured to call and run a computer program from a memory, so that a device installed with the chip performs the method in the first aspect.

[0018] In a fifth aspect, an embodiment of the present application provides a computer readable storage medium, which stores a computer program, and the computer program is executed by at least one processor to realize the method in the first aspect.

[0019] In a sixth aspect, an embodiment of the present application provides a computer program product, comprising computer program instructions, and the computer program instructions make a computer execute the method in the first aspect when the computer executes.

[0020] In a seventh aspect, an embodiment of the present application provides a computer program, which makes a computer execute the method in the first aspect when the computer executes.

[0021] Embodiments of the present application provide a communication method and device, terminal, chip, medium, program product and program. A first node obtains first information, the first information being used to identify a data packet; based on the first information, at least one of the following is performed: determining that the data packet associated with the first information is processed at the first node; determining an egress of the data packet associated with the first information. It can be seen that, in the embodiments of the present application, for end-to-end transmission, the egress of the associated data packet can be determined through the acquisition of the first information. For non-end-to-end transmission, the associated data packet can be processed through the first node by acquiring the first information. That is, the first node can determine accurate data routing by using the first information, thereby solving the problem that the Relay UE cannot identify two different data when receiving the data, and further improving the accuracy of communication. BRIEF DESCRIPTION OF DRAWINGS

[0022] The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and together with the description serve to explain the application. In the drawings:

[0023] Fig. 1 is a schematic diagram of an optional scenario of D2D communication according to an embodiment of the present application;

[0024] Fig. 2 is a schematic diagram of an optional scenario of D2D communication according to an embodiment of the present application;

[0025] Fig. 3 is a user plane protocol stack of U2N relay architecture according to an embodiment of the present application;

[0026] Fig. 4 is a control plane protocol stack of U2N relay architecture according to an embodiment of the present application;

[0027] Fig. 5 is a schematic diagram of an implementation flow of a communication method according to an embodiment of the present application;

[0028] Fig. 6 is a schematic diagram of a relay link according to an embodiment of the present application;

[0029] Fig. 7 is a schematic diagram of a relay link according to an embodiment of the present application;

[0030] Fig. 8 is a schematic diagram of a method for establishing a new link according to an embodiment of the present application;

[0031] Fig. 9 is a schematic diagram of a first adaptation layer identifier indication according to an embodiment of the present application;

[0032] Fig. 10 is a schematic diagram of a first adaptation layer identifier indication according to an embodiment of the present application;

[0033] Fig. 11 is a schematic diagram of a first adaptation layer identifier indication according to an embodiment of the present application;

[0034] Fig. 12 is a schematic diagram of a first adaptation layer identifier indication according to an embodiment of the present application;

[0035] Fig. 13 is a schematic diagram of a structure of a communication apparatus according to an embodiment of the present application;

[0036] Fig. 14 is a schematic diagram of a structure of a communication device according to an embodiment of the present application;

[0037] Fig. 15 is a schematic diagram of a structure of a chip according to an embodiment of the present application. DETAILED DESCRIPTION

[0038] With reference to the drawings of the embodiments of the present application, the technical solutions in the embodiments of the present application will be described. Obviously, the described embodiments are some but not all of the embodiments of the present application. Based on the embodiments of the present application, all other embodiments obtained by a person of ordinary skill in the art without creative work fall within the protection scope of the present application.

[0039] The technical solutions of the embodiments of the present application can be applied to various sidelink communication systems (which can also be referred to as sidelink systems). In order to facilitate understanding of the technical solutions of the embodiments of the present application, the related technologies in the sidelink communication system will be described below. The related technologies below can be combined with the technical solutions of the embodiments of the present application in any manner as optional solutions, and all of them belong to the protection scope of the embodiments of the present application.

[0040] A. Long Term Evolution (LTE) Device to Device (D2D) / Vehicle to Everything (V2X)

[0041] Device to Device communication is a kind of sidelink transmission technology (Sidelink, SL) based on D2D. Unlike the way of receiving or sending communication data through a base station in a traditional cellular system, the vehicle networking system adopts a terminal to terminal direct communication mode, so it has higher spectrum efficiency and lower transmission delay. In 3GPP, two transmission modes are defined: mode 3 and mode 4.

[0042] Mode 3: The transmission resource of the terminal is allocated by the base station, and the terminal transmits data on the sidelink according to the resource allocated by the base station; the base station can allocate single transmission resource to the terminal, or semi-static transmission resource to the terminal.

[0043] FIG. 1 is a schematic diagram of an optional scenario of D2D communication according to an embodiment of the present application. As shown in FIG. 1, the base station 210 allocates grant resources (Grant) to the terminal device 220 and the terminal device 230, and the terminal device 220 and the terminal device 230 transmit data based on the Grant allocated by the base station.

[0044] Mode 4: The vehicle terminal selects a resource in the resource pool for data transmission.

[0045] FIG. 2 is a schematic diagram of an optional scenario of D2D communication according to an embodiment of the present application. As shown in FIG. 2, the terminal device 220 and the terminal device 230 transmit data based on the resource obtained from the resource pool.

[0046] In 3GPP, D2D is studied in different stages.

[0047] Proximity based Service (ProSe): In Rel-12 / 13, device to device communication is studied for ProSe, which is mainly targeting public safety type of service.

[0048] In ProSe, by configuring the location of resource pool in time domain, for example, the resource pool is non-continuous in time domain, the user equipment (UE) can achieve non-continuous transmission / reception of data on sidelink, thereby achieving the effect of power saving.

[0049] Vehicle to everything (V2X): In Rel-14 / 15, vehicle to everything system is studied for vehicle to vehicle communication scenario, which mainly faces the vehicle to vehicle and vehicle to pedestrian communication service with relatively high speed.

[0050] In V2X, since the vehicle system has continuous power supply, power efficiency is not the main problem, and the delay of data transmission is the main problem, so the terminal device is required to continuously transmit and receive in system design.

[0051] Wearable device (Further Enhancements to LTE Device to Device (FeD2D)): In Rel-14, this scenario is studied for wearable devices to access the network through mobile phones, which mainly faces the scenario of low mobile speed and low power access.

[0052] In FeD2D, in the pre-research stage, 3GPP concluded that the base station can configure the discontinuous reception (DRX) parameters of the remote terminal through a relay terminal, but since this topic has not further entered the standardization stage, the specific details of how to configure DRX are not concluded.

[0053] B. New Radio (NR) V2X

[0054] NR V2X is based on LTE V2X, not limited to broadcast scenarios, but further expanded to unicast and groupcast scenarios, and studies the application of V2X in these scenarios.

[0055] Similar to LTE V2X, NR V2X also defines the above two resource authorization modes of mode-1 / 2.

[0056] Unlike LTE V2X, in addition to the feedback-less, UE-autonomous initiated Hybrid Automatic Repeat reQuest (HARQ) retransmission, NR V2X introduces feedback-based HARQ retransmission, not limited to unicast communication, but also including groupcast communication.

[0057] C. UE-to-Network Relay

[0058] The user plane protocol stack of a Layer-2 (L2) terminal-to-network (U2N) relay architecture is shown in FIG. 3, and the control plane protocol stack of the L2 U2N relay architecture is shown in FIG. 4. For L2 U2N relay, the SRAP sublayer is on top of the Radio Link Control (RLC) sublayer in the control plane and user plane at the PC5 interface and the Uu interface. The Service Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP), and Radio Resource Control (RRC) of the Uu interface terminate between the Remote UE and the base station (gNB), while the SRAP, RLC, Media Access Control (MAC), and PHY (Physical Layer) sublayers terminate at each link (i.e., the link between the Remote UE and the U2N relay UE, and the link between the U2N relay UE and the gNB).

[0059] For L2 U2N relay, the SRAP sublayer on the PC5 interface is only used for bearer mapping. For Broadcast Control Channel (BCCH) and Paging Control Channel (PCCH) messages for the Remote UE, the SRAP sublayer is not present on the PC5 interface. For Signal Radio Bearer (SRB) 0 messages for the Remote UE, the SRAP sublayer is also not present on the PC5 interface, but the SRAP sublayer is present on the uplink and downlink of the Uu interface.

[0060] For L2 U2N relay, for uplink:

[0061] The Uu interface SRAP sublayer supports the relay UE to perform bearer mapping between the RLC channel on the PC5 interface and the RLC channel on the Uu interface. For uplink relay service, different end-to-end bearers (SRB or Data Radio Bearer, DRB) of the same Remote UE and / or different Remote UEs can be multiplexed on the same RLC channel of the Uu interface.

[0062] The Uu interface SRAP sublayer supports the gNB to identify the Remote UE for uplink data. The bearer information and UE identity information of the Remote UE are contained in the SRAP header of the Uu interface, so that the gNB can associate the received data packet to the specific PDCP entity of the correct Remote UE.

[0063] The PC5 interface SRAP sublayer of the Remote UE supports the mapping between the wireless bearer of the Remote UE and the RLC channel of the PC5 interface.

[0064] For L2 U2N relay, for downlink:

[0065] The Uu interface SRAP sublayer supports the downlink bearer mapping of the gNB to map the wireless bearers (SRB and DRB) of the Remote UE to the RLC channel of the Uu interface through the Uu interface of the relay UE. The SRAP sublayer of the Uu interface can be used to map and multiplex multiple wireless bearers (SRB and DRB) of the Remote UE and / or different Remote UEs to one RLC channel on the Uu interface of the relay UE.

[0066] The Uu interface SRAP sublayer supports the Remote UE identification for downlink data. The gNB can map the received data packet of the specific Remote UE wireless bearer to the associated RLC channel of the PC5 interface by putting the index information of the Remote UE wireless bearer and the identity information of the Remote UE into the SRAP packet header of the Uu interface.

[0067] The PC5 interface SRAP sublayer of the relay UE supports the mapping between the wireless bearer of the Remote UE and the RLC channel of the PC5 interface.

[0068] The relay UE is configured by the gNB with Remote UE identity information for populating the SRAP packet header. Also, the gNB avoids collision in assigning Remote UE identity information, for example, the gNB can send updated Remote UE identity information to the relay UE through RRC reconfiguration message. Further, the gNB can perform Remote UE identity information update independently from the Layer 2 identity information update procedure over the PC5 unicast link.

[0069] Before user plane data transmission, the Remote UE needs to establish its own Protocol Data Unit (PDU) session and radio bearers with the network.

[0070] Currently, in multi-hop U2N relay, due to the existence of multiple Relay multiple hops, the topology structure is more complex, and the original single-hop U2N Relay recognizes the data packet according to the device identifier (UE ID) and the bearer identifier (BEARER ID) in the SRAP header, and derives the egress link (derive egress link) and the egress radio link control channel (egress RLC channel). The way is not enough to uniquely identify the data, and it is impossible to determine the routing direction of the data.

[0071] That is, due to the existence of multiple links in the multi-hop U2N relay, that is, there are multiple logical links, and multiple logical links share a physical link, at this time, it becomes a problem to be solved to distinguish multiple logical links on a shared physical link.

[0072] In the embodiments of the present application, in order to solve the SRAP routing problem in the multi-hop U2N relay technology, it is necessary to solve the problem of whether the data and control signaling between entities not directly connected on the link can share the established link, and if it can be shared, it is necessary to further solve the problem of identifying and distinguishing different data of the source and the target.

[0073] To solve the above problems, in the embodiments of the present application, the first node acquires first information, the first information being used to identify a data packet; and based on the first information, at least one of the following is performed: determining that the first node processes the data packet associated with the first information; and determining an egress of the data packet associated with the first information. It can be seen that, in the embodiments of the present application, for an end-to-end link, the egress of the associated data packet can be determined through acquisition of the first information, and for a non-end-to-end link, the associated data packet processed by the first node can be determined through acquisition of the first information. That is, the first node can determine accurate data routing by using the first information, thereby solving the problem that the Relay UE cannot identify two different data when receiving the data, and further distinguishing different logical links on one physical connection.

[0074] It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and / or" herein is only used to describe the association relationship of the associated objects, which means that there can be three relationships, for example, A and / or B, which can represent three cases of A alone, A and B together, and B alone. In addition, the character " / " herein generally represents an "or" relationship between the associated objects. It should also be understood that the "indication" mentioned in the embodiments of the present application can be direct indication or indirect indication, and can also represent an associated relationship. For example, A indicates B, which can mean that B can be obtained by A; or A indirectly indicates B, for example, A indicates C, and B can be obtained by C; or A and B have an associated relationship. It should also be understood that the "corresponding" mentioned in the embodiments of the present application can represent a direct or indirect corresponding relationship between the two, or an associated relationship between the two, or an indication and being indicated, configuration and being configured relationship. It should also be understood that the "predefined" or "predefined rule" mentioned in the embodiments of the present application can be realized by pre-saving corresponding codes, tables or other means for indicating related information in devices (such as terminal devices and network devices), and the specific implementation manner of the present application is not limited. For example, the predefined can mean defined in the protocol. It should also be understood that the "protocol" in the embodiments of the present application can refer to a standard protocol in the communication field.

[0075] In order to facilitate understanding of the technical solutions of the embodiments of the present application, the technical solutions of the present application are described in detail below through specific embodiments. The above related technologies can be combined with the technical solutions of the embodiments of the present application in any way, and all belong to the protection scope of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0076] An embodiment of the present application provides a communication method, which can be applied to a first node. The first node can be a relay terminal.

[0077] It should be noted that in the embodiments of the present application, the first node can be any relay terminal (Relay UE) in multi-hop U2N, which is not limited in the present application.

[0078] Further, in the embodiments of the present application, FIG. 5 is a flowchart of the implementation of the communication method provided by the embodiments of the present application, as shown in FIG. 5, the communication method can include the following steps:

[0079] S101, obtaining first information, the first information being used to identify a data packet;

[0080] S102, based on the first information, performing at least one of the following: determining that the data packet associated with the first information is processed at the first node; and determining an egress of the data packet associated with the first information.

[0081] In the embodiments of the present application, the egress includes an egress link (egress link) and / or an egress channel (egress RLC channel).

[0082] In the embodiments of the present application, the first node can obtain the first information, and then identify the data packet based on the first information, and further determine that the data packet associated with the first information is processed at the first node, or further determine the egress of the data packet associated with the first information, based on the first information.

[0083] In the embodiments of the present application, the first node can be a first relay terminal. The first relay terminal can be any relay terminal in a relay link, for example, the first relay terminal can include but is not limited to any relay terminal (Relay UE) in multi-hop U2N.

[0084] In the embodiments of the present application, in the multi-hop relay scenario, the relay link can include two or more relay terminals.

[0085] Exemplarily, in some embodiments, FIG. 6 is a schematic diagram of a relay link provided by the embodiments of the present application, as shown in FIG. 6, the relay link can include two relay terminals, which are Relay1 and Relay2 respectively, and also includes a remote terminal (Remote) and a network device (gNB), wherein the first node in the embodiments of the present application can be Relay1 in the relay link, or can be Relay2 in the relay link.

[0086] Exemplarily, in some embodiments, FIG. 7 is a schematic diagram of a relay link proposed in embodiments of the present application, as shown in FIG. 7, the relay link can include three relay terminals, respectively Relay1, Relay2, Relay3, and a remote terminal (Remote) and a network device (gNB), wherein the first node in embodiments of the present application can be Relay1 in the relay link, can also be Relay2 in the relay link, and can further be Relay3 in the relay link.

[0087] Of course, the number of relay terminals in the relay link in the multi-hop relay scenario is not limited to two or three, and the present application does not make specific limitation.

[0088] In embodiments of the present application, the first node can receive or send a first message. Wherein the first message carries first information.

[0089] That is to say, in embodiments of the present application, the first node can obtain the first information through the reception of the first message, or can send the first message carrying the first information after obtaining the first information.

[0090] In embodiments of the present application, the first message is sent by a third node, that is, the first node receives the first message sent from the third node.

[0091] In embodiments of the present application, the first message is sent to a second node, that is, the first node sends the first message to the second node.

[0092] In embodiments of the present application, the third node is different from the second node, that is, the third node can be another node in the relay link different from the second node.

[0093] In embodiments of the present application, the second node can include one or more of the following: a remote terminal, a second relay terminal, and a network device. Wherein the second relay terminal is different from the first relay terminal, that is, the second relay terminal can be another relay terminal on the relay link.

[0094] It can be understood that in embodiments of the present application, the second node is different from the first node, that is, the second node can be another node in the relay link different from the first node, and the second node can include one or more of the remote terminal, the network device, and the second relay terminal.

[0095] Exemplarily, in some embodiments, as shown in FIG. 6, assuming that the first node is Relay1 in the relay link, accordingly, the second node can be any one or more of Relay2, Remote, and gNB in the relay link.

[0096] Exemplarily, in some embodiments, as shown in FIG. 7, assuming that the first node is Relay3 in the relay link, the second node can be any one or more of Relay1, Relay2, Remote, and gNB in the relay link.

[0097] In embodiments of the present application, the third node can include one or more of a remote terminal, a network device, and a third relay terminal. Wherein the third relay terminal is different from the second relay terminal, which is not specifically limited in the present application.

[0098] Exemplarily, in some embodiments, as shown in FIG. 7, assuming that the first node is Relay1 in the relay link, the second node can be Relay3 in the relay link, and the third node can be any one of Relay2, Remote, and gNB.

[0099] Correspondingly, in embodiments of the present application, the first node receives the first message from the third node and sends the first message to the second node, for example, Relay1 (the third node) sends the first message to Relay3 (the second node) through Relay2 (the first node).

[0100] Exemplarily, in some embodiments, as shown in FIG. 7, assuming that the first node is Relay1 in the relay link, the second node can be gNB in the relay link, and the third node can be any one of Relay2, Relay3, and Remote.

[0101] Correspondingly, in embodiments of the present application, the third node can send the first message to the second node through the first node, for example, Relay1 can send the first message to gNB through Relay3.

[0102] In embodiments of the present application, the first information includes a first link identifier or a second link identifier. Wherein the first link identifier is used to confirm that the first node processes a data packet associated with the first link identifier; the second link identifier is used to confirm the egress of a data packet associated with the second link identifier. Wherein the first link is a non-end-to-end link associated with the first node; the second link is an end-to-end multi-hop U2N relay link or a non-end-to-end link not associated with the first node.

[0103] It should be noted that the end-to-end multi-hop U2N relay link here is a multi-hop U2N relay link from remote UE to network.

[0104] It should be noted that the non-end-to-end link associated with the first node here refers to a relay link where the source and destination nodes are not end-to-end, apart from the original multi-hop U2N relay link from the remote UE to the network, and one end of the source or destination node of the relay link is the first node.

[0105] In other words, in the embodiments of this application, after obtaining the first information, if the first information includes a first link identifier, then based on the first information, it can be further determined that the data packet associated with the first link identifier will be processed at the first node. If the first information includes a second link identifier, then based on the first information, it can be further determined that the exit point of the data packet associated with the second link identifier will be determined.

[0106] It is understood that, in the embodiments of this application, for relay links, there is data and / or signaling transmission between two entities that are not end-to-end, such as data and / or signaling transmission between two relay terminals, or data and / or signaling transmission between a remote terminal and a relay terminal, or data and / or signaling transmission between a relay terminal and a network device. For non-end-to-end links, the associated data packets can be indicated by the first link identifier in the first information, thereby allowing the received data packets to be directly delivered to the upper layer, such as the RRC layer and / or the PDCP layer.

[0107] It is understood that, in the embodiments of this application, for a relay link, there is data and / or signaling transmission between two end-to-end entities, such as data and / or signaling transmission between a remote terminal and a network device. Specifically, for an end-to-end link, the exit route of associated data packets can be indicated by the second link identifier in the first information, for example, by routing to the corresponding egress RLC channel according to the SRAP configuration.

[0108] In other words, in the embodiments of this application, different processing can be performed on end-to-end links and non-end-to-end links through the first link identifier or the second link identifier included in the first information.

[0109] In the embodiments of this application, the first node is a relay terminal on a relay link. The transmission of data and / or signaling between the first node and other nodes (such as the second node or the third node) can be understood as the transmission of data and / or signaling between two entities that are not end-to-end.

[0110] In the embodiments of this application, in order to distinguish different logical links, one implementation is to associate the bearers of different source / target entities with different physical links.

[0111] In embodiments of the present application, different bearers of different source / destination entities can be transmitted through different Layer 2 Identifiers (L2 IDs) / link identifiers (link IDs).

[0112] In the L2 protocol, L2 IDs or link IDs are generally used to uniquely identify a specific logical connection or bearer. These identifiers help networks and devices distinguish different transmission paths and data flows. By using different L2 IDs / link IDs, a UE can distinguish and manage different bearers. For example, when a UE needs to transmit data belonging to different source / destination entities, it can use different L2 IDs / link IDs to ensure that these data are correctly routed and transmitted.

[0113] In embodiments of the present application, the first node can first determine the second node and / or the third node; then establish a first link with the second node and / or the third node, respectively; the first link includes a first link identifier; wherein the second node and the third node are different relay terminals. The first node has a second link connected with the second node and the third node, respectively; the second link identifier of the second link is different from the first link identifier. Wherein, the first link is a non-end-to-end link associated with the first node; the second link is an end-to-end multi-hop U2N relay link or a non-end-to-end link not associated with the first node.

[0114] In embodiments of the present application, the second node can be understood as the next hop node corresponding to the first node, and the third node can be understood as the previous hop node corresponding to the first node.

[0115] In embodiments of the present application, the first link can be a newly established link between the first node and the second node, and / or a newly established link between the first node and the second node. That is, the first node can establish a link with the second node and the third node, respectively. Wherein, the first link identifier of the first link between the first node and the second node is different from the first link identifier of the first link between the first node and the third node.

[0116] In embodiments of the present application, the first node, the second node, and the third node can all be relay terminals. Accordingly, the first node and the second node, and the first node and the third node can be understood as non-end-to-end links on PC5.

[0117] Accordingly, in embodiments of the present application, the first link can be understood as a newly established PC5 link. Wherein, the first link can be a newly established PC5 link between the first node and the second node, and / or a newly established PC5 link between the first node and the second node.

[0118] In embodiments of the present application, the first link identifier can include an L2 ID / link ID / L2 ID pair (source and destination). Wherein, for different PC5 links, the corresponding L2 ID / link ID / L2 ID pair is different.

[0119] In embodiments of the present application, the L2 ID / link ID can be transmitted in the header of the physical layer or in the header of the MAC layer.

[0120] In embodiments of the present application, before the first link is established, the first node has a connected second link with the second node and the third node respectively. Wherein, the second link identifier of the second link is different from the first link identifier.

[0121] That is, in embodiments of the present application, before the first link is established, the establishment of the second link between the first node and other nodes has been completed, and the transmission of data and / or signaling is carried out through the second link.

[0122] It can be understood that in embodiments of the present application, the non-end-to-end link on PC5 and the end-to-end multi-hop U2N relay link can use different PC5 links, for example, the first link (non-end-to-end) and the second link (end-to-end).

[0123] Exemplarily, in some embodiments, if an end-to-end multi-hop U2N relay link has been established between two entities, for example, the first node has a connected second link with the second node and the third node respectively, and there is a need for non-end-to-end data and / or signaling transmission, then a relay link can be further established for this transmission requirement, for example, the first node establishes a first link with the second node and / or the third node respectively.

[0124] In embodiments of the present application, when the first node establishes a first link with the second node and / or the third node respectively, a separate L2 ID can be used for relay discovery, selection, and link establishment.

[0125] In embodiments of the present application, the first message carrying the first link identifier is transmitted on the first link; or the first message carrying the second link identifier is transmitted on the second link.

[0126] It can be understood that in embodiments of the present application, the first link identifier can be used to confirm the processing of data packets associated with the first link identifier at the first node; and the second link identifier can be used to confirm the exit of data packets associated with the second link identifier.

[0127] In an embodiment of the present application, the first node can establish the third link with the second node and / or the third node directly without relay discovery and / or selection; the third link comprises the first link identifier; wherein the second node and the third node are different relay terminals with relay capability.

[0128] In an embodiment of the present application, the second node can be understood as a next-hop node corresponding to the first node, and the third node can be understood as a previous-hop node corresponding to the first node.

[0129] In an embodiment of the present application, the second node and the third node are both relay terminals with relay capability.

[0130] In an embodiment of the present application, the first node has a connected second link with the second node and the third node respectively, and the first link identifier is different from a second link identifier of the second link.

[0131] Correspondingly, in an embodiment of the present application, before the first link is established, the establishment of the second link between the first node and other nodes has been completed, and the transmission of data and / or signaling is performed through the second link. Wherein, through the established second link, the first node can obtain the relay capability of the second node and / or the third node, and thus can directly establish the third link with the second node and / or the third node without relay discovery and / or selection.

[0132] In an embodiment of the present application, when obtaining the relay capability of the node, the first node can interact with the second node and / or the third node for capability information; the capability information is transmitted through the second link. That is, the first node can interact with the second node and / or the third node for capability information through the established second link, so as to obtain the relay capability of the second node and / or the third node.

[0133] In an embodiment of the present application, in the process of interacting for the capability information, the capability information can be carried in a PC5 message.

[0134] In an embodiment of the present application, the first node can receive a first request message, wherein the first request message carries a third link identifier. In response to the first request message, the first node sends a first request acceptance message; the first request acceptance message carries the third link identifier, and the first link identifier is determined based on the third link identifier.

[0135] Correspondingly, in an embodiment of the present application, the other node can also receive the first request message sent by the first node, and the first request message carries the third link identifier. Then in response to the first request message, the other node sends a first request acceptance message to the first node, and the first request acceptance message carries the first link identifier, which is determined based on the third link identifier.

[0136] In embodiments of the present application, the first request message can be a Direct Communication Request (DCR). The first request acceptance message can be a Direct Communication Accept (DCA).

[0137] In embodiments of the present application, the third link identification pair can include, but is not limited to, one or more of the following:

[0138] The first link identification pair determined through coordination of the second link;

[0139] The second link identification pair determined by default or based on a service type;

[0140] The third link identification pair determined based on the second link identification.

[0141] In embodiments of the present application, the first link identification pair can be the link identification of the first source node and the link identification of the destination node; wherein the link identification of the destination node is sent by the receiving node (e.g., the first node) to the sending node (e.g., the third node) through the second link; the second link identification pair determined by default or based on a service type can be the link identification of the first source node and a first value; the third link identification pair determined based on the second link identification can be the link identification of the second source node and the link identification of the destination node; wherein the first source node is the sending node; the second source node is different from the first source node.

[0142] That is, in embodiments of the present application, the third link identification that can be carried in the first request message and the first request acceptance message can include multiple determination methods.

[0143] Exemplarily, in some embodiments, one way of determining the third link identification is to communicate (through the second link coordination) through the first request message and the first request acceptance message on the already established second link, to determine the link identification of the first source node and the link identification of the destination node, thereby completing the determination of the third link identification. Wherein the link identification of the destination node can be sent by the receiving node to the sending node. For example, the sending node sends the link identification of the first source node to the receiving node through the first request message, and the receiving node sends the first request acceptance message carrying the link identification of the destination node to the sending node after receiving the first request message.

[0144] Exemplarily, in some embodiments, another way to determine the third link identifier is to communicate through the first request message and the first request acceptance message on the second link which has been established, to determine the link identifier of the first source node and a default first value, so as to complete the determination of the third link identifier. The first value is not limited in value.

[0145] Exemplarily, in some embodiments, still another way to determine the third link identifier is to communicate through the first request message and the first request acceptance message on the second link which has been established, to determine the link identifier of the second source node and the link identifier of the destination node, so as to complete the determination of the third link identifier. The second source node is different from the first source node, and the first source node can be understood as the sending node, while the second source node is not the sending node, but other node with different link identifier from the first source node.

[0146] In the embodiments of the present application, the first link identifier can be determined based on the third link identifier. That is, through the third link identifier, the first link identifier can be set to indicate that the first node processes the data packet associated with the first link identifier.

[0147] It should be noted that the sending node carries the link identifier of the first source node and the default first value (the second link identifier pair) in the DCR and sends it to the receiving node. The receiving node determines whether the requirement is met based on the service type, and in the case of meeting, the link identifier of the receiving node is taken as the destination link identifier, and the link identifier of the first source node and the link identifier of the receiving node (the first link identifier) are carried in the DCA.

[0148] Exemplarily, in some embodiments, FIG. 8 is a schematic diagram of a new link establishment method proposed in the embodiments of the present application. As shown in FIG. 8, when a link is established by a unicast DCR / DCA mode, assuming that Relay1 is a sending node and Relay2 is a destination node, a new PC5 link is established with the already connected Relay2 to transmit U2N of Relay1 to the network or U2U relay signaling / data of Relay1 to Relay3. The U2N and U2U relay establishment process can be a simplified U2N and U2U connection establishment process, that is, without relay discovery and / or selection. Wherein, Relay1 knows the capability information of Relay2 through unicast transmission on link1, such as whether to support single-hop U2N relay, U2U relay, and multi-hop U2N relay. The capability information is exchanged through PC5 RRC messages (capability exchange information) or PC5-S messages (discovery messages or link modification messages). Link2 is established by a unicast DCR / DCA receiving mode. The L2 ID used by link2 is the L2 ID information communicated on link1 (PC5 RRC messages or PC5-S messages), for example, the link identifier of the first source node and the link identifier of the destination node, such as (SRC2, DST2); or the L2 ID used by link2 is a default L2 ID, for example, the link identifier of the first source node and a first value, such as (SRC2, DST_default); or, Relay1 uses different source L2 ID and the same destination L2 ID, but sends DCR messages from different sources, for example, the link identifier of the second source node and the link identifier of the destination node, such as (SRC1, DST2), and Relay2 replies DCA messages to Relay1 using updated L2 ID.

[0149] In the embodiments of the present application, the capability information exchanged between different nodes can include one or more of the following: single-hop U2N relay; single-hop U2N relay; multi-hop U2N relay; multi-hop U2U relay.

[0150] Exemplarily, in some embodiments, the first node can obtain the capability information of the second node and / or the third node through unicast transmission on the second link. For example, the capability information can include but is not limited to whether to support single-hop U2N relay, single-hop U2U relay, multi-hop U2N relay, and multi-hop U2U relay. The exchange of the capability information can be realized through PC5 RRC messages or sidelink signaling PC5-S (such as discovery messages (Discovery messages) or link modification messages (Link Modification messages)).

[0151] It can be understood that, in the embodiments of the present application, the non-end-to-end link on the PC5 and the end-to-end multi-hop U2N relay link can use different PC5 links, for example, the third link and the second link.

[0152] In the embodiments of the present application, the third link can be a newly established link between the first node and the second node, and / or a newly established link between the first node and the second node, respectively. That is, the first node can establish a link with the second node and the third node, respectively. Wherein, the first link identifier of the third link between the first node and the second node is different from the first link identifier of the third link between the first node and the third node.

[0153] In the embodiments of the present application, between the first node and the second node, and between the first node and the third node, it can be understood as a non-end-to-end link on the PC5, therefore, the third link can be understood as a newly established PC5 link. Wherein, the third link can be a newly established PC5 link between the first node and the second node, and / or a newly established PC5 link between the first node and the second node, respectively.

[0154] In the embodiments of the present application, the first link identifier can include L2 ID / link ID / L2 ID pair. Wherein, for different PC5 links, the corresponding L2 ID / link ID is different. The L2 ID / link ID can be transmitted in the header of the physical layer, or can be transmitted in the header of the MAC layer.

[0155] Exemplarily, in some embodiments, if the end-to-end multi-hop U2N relay link has been established between two entities, for example, the first node has a connected second link with the second node and the third node, respectively, at this time there is a transmission demand of non-end-to-end data and / or signaling, then the relay link can be further established for this transmission demand, for example, the first node establishes a third link with the second node and / or the third node, respectively.

[0156] In the embodiments of the present application, when the first node establishes the third link with the second node and / or the third node, respectively, a simplified U2N, U2U connection establishment process can be established, that is, without relay discovery and / or selection.

[0157] In the embodiments of the present application, in the case that the second node is a network device and the first node is a first relay device, between the first node and the second node, it can be understood as a non-end-to-end link on the Uu link. In the case that the third node is a network device and the first node is a first relay device, between the first node and the third node, it can be understood as a non-end-to-end link on the Uu link.

[0158] In the embodiments of the present application, for the non-end-to-end link on the Uu link, in order to distinguish different logical links, the following one or more can be selected to be sent to the second node or the third node: the first link identifier and the second link identifier; the association relationship between the first source node in the first link identifier and the third source node in the second link identifier.

[0159] That is, in the embodiments of the present application, for the processing of the non-end-to-end link on the Uu, such as the non-end-to-end link between the relay terminal and the network device, the relay terminal needs to report to the network device that it uses two L2 IDs to access the network device, and the reporting can be performed through an RRC message.

[0160] In the embodiments of the present application, through the reporting of the first link identifier and the second link identifier, the network device can be informed of the corresponding source L2 ID for each link / destination L2 ID purpose data transmission / communication (non-discovery).

[0161] In the embodiments of the present application, through the reporting of the association relationship between the first source node in the first link identifier and the third source node in the second link identifier, the network device can be informed of the association relationship between the two source L2 IDs.

[0162] It can be understood that, in the embodiments of the present application, since the communication between the network device and the UE is performed at the Uu port, and the L2 ID is the device identifier of the UE on the PC5, the network device does not uniquely identify the UE through the L2 ID. Moreover, there is only one RRC connection between the same UE and the same network device at the same time, so even if different L2 IDs are used, Relay1 is still one user in the view of the network device, although it accesses the network device through different Relay links using different L2 IDs. Therefore, the UE needs to report to the network device that it uses two L2 IDs to access the network device.

[0163] In summary, by associating the bearers of different source / destination entities to different physical links through the obtained first information, different logical links can be effectively distinguished, accurate identification of data packets or data can be achieved, and the accuracy of communication can be improved.

[0164] In the embodiments of the present application, in order to distinguish different logical links, another implementation manner is to distinguish logical links according to different Local IDs / UE IDs in the SRAP layer packet header.

[0165] In some embodiments of the present application, the first information is carried in a packet header of a data packet of an adaptation layer, the data packet is carried in the first message, and the first information is associated with the data packet.

[0166] In some embodiments of the present application, the first information can include a first device identifier (UE ID), which can also be referred to as a first local identifier (Local ID), and the first device identifier can be used to confirm that the data packet associated with the first device identifier is processed at the first node. The first information can also include a second device identifier, and the second device identifier can be used to confirm the egress of the data packet associated with the second device identifier.

[0167] That is, in embodiments of the present application, after obtaining the first information, if the first device identifier is included in the first information, the first information can be used to further determine that the data packet associated with the first device identifier is processed at the first node. If the second device identifier is included in the first information, the first information can be used to further determine the egress of the data packet associated with the second device identifier.

[0168] It can be understood that, in embodiments of the present application, for a relay link, there is transmission of data and / or signaling between two entities that are not end-to-end, such as transmission of data and / or signaling between two relay terminals, or transmission of data and / or signaling between a remote terminal and a relay terminal, or transmission of data and / or signaling between a relay terminal and a network device. For a non-end-to-end link, the first device identifier in the first information can be used to indicate the associated data packet, so that the received data packet can be directly delivered to an upper layer, such as an RRC layer and / or a PDCP layer.

[0169] It can be understood that, in embodiments of the present application, for a relay link, there is transmission of data and / or signaling between two entities that are end-to-end, such as transmission of data and / or signaling between a remote terminal and a network device. For an end-to-end link, the second device identifier in the first information can be used to indicate the egress of the associated data packet, such as routing to a corresponding egress RLC channel according to an SRAP configuration.

[0170] That is, in embodiments of the present application, the first device identifier or the second device identifier included in the first information can be used to perform different processing for end-to-end links and non-end-to-end links.

[0171] In embodiments of the present application, the first message carrying the first device identifier is transmitted over a first link, or the first message carrying the second device identifier is transmitted over a second link.

[0172] In the embodiments of the present application, the first device identifier is related to the device identifier of the first node; the first device identifier is different from the device identifiers of other terminals on the multi-hop link; or the first device identifier is different from the device identifiers of other terminals on the link of the first relay terminal.

[0173] That is, in the embodiments of the present application, for any relay terminal on the relay link except the remote terminal (Remote UE), a multiple device identifier can be selected for the relay terminal, so that the source node or the target node corresponding to the corresponding data can be indicated by the device identifier. The device identifier of the relay terminal can be carried in the SRAP packet header.

[0174] In the embodiments of the present application, the first device identifier includes one or more of the following: one device identifier field; two device identifier fields.

[0175] Exemplarily, in some embodiments, one UE ID field (device identifier field) can be carried in the data SRAP packet header, or two UE ID fields (device identifier fields) can be carried.

[0176] In the embodiments of the present application, if the first node is the first relay terminal in the transmission between the first node and the network device, the one device identifier field is the device identifier of the first relay terminal; if the first node is the remote terminal in the transmission between the first node and the network device, the one device identifier field is the device identifier of the remote terminal or a second value; if the first node is the remote terminal in the transmission between the first node and the network device, the two device identifier fields include: the device identifiers of two remote terminals; or the device identifier of one remote terminal and a third value.

[0177] It can be understood that in the embodiments of the present application, for a non-end-to-end link between the relay terminal and the network device, the one device identifier field corresponding to the first node can be the device identifier of the first relay terminal.

[0178] Exemplarily, in some embodiments, for a non-end-to-end link between the relay terminal and the network device, one UE ID field can be the UE ID of the UE, which is used for non-end-to-end bearer transmission between the UE and the network device.

[0179] It can be understood that in the embodiments of the present application, for the case that one end is the network device and the other end is the remote terminal, the corresponding one device identifier field can be the device identifier of the remote terminal, or can be a preset value or a default value, for example, a second value, and the present application does not limit the specific value of the second value.

[0180] Exemplarily, in some embodiments, for the case that one end is a network device and the other end is a remote terminal, one UE ID field can be a default value (a second value) or a device identifier of the remote terminal.

[0181] It can be understood that, in the embodiments of the present application, for the end-to-end link between the remote terminal and the network device, the two device identifier fields can include: device identifiers of the two remote terminals; or, a device identifier of one remote terminal and a preset value or a default value, for example, a third value, and the present application does not limit the specific value of the third value.

[0182] Exemplarily, in some embodiments, for the end-to-end link between the remote terminal and the network device, the end-to-end Bearer from the remote terminal to the network device can omit one UE ID, or, both UE IDs can be set as the device identifier of the remote terminal (Remote UE ID), or, one UE ID is set as a default value (such as all 0 or all 1) and the other is set as the Remote UE ID.

[0183] In the embodiments of the present application, if, in the transmission from the first node to the remote terminal, the first node is the first relay terminal, the two device identifier fields include: the device identifier of the remote terminal and the device identifier of the first relay terminal.

[0184] It can be understood that, in the embodiments of the present application, for the non-end-to-end link between the remote terminal and the relay terminal, one of the two device identifier fields is used to indicate the device identifier of the source node, and the other is used to indicate the device identifier of the destination node.

[0185] Exemplarily, in some embodiments, if, in the transmission from the remote terminal to the first node, the first node is the relay terminal, the two device identifier fields include: one is the device identifier of the source node, that is, the UE ID corresponding to the remote terminal, and the other is the device identifier of the destination node, that is, the UE ID corresponding to the first node.

[0186] Exemplarily, in some embodiments, if, in the transmission from the relay terminal to the remote terminal, the first node is the relay terminal, the two device identifier fields include: one is the device identifier of the source node, that is, the UE ID corresponding to the first node, and the other is the device identifier of the destination node, that is, the UE ID corresponding to the remote terminal.

[0187] In the embodiments of the present application, if, in the transmission from the first node to the network device, the first node is the first relay terminal, the two device identifier fields include: the device identifier of the remote terminal and the device identifier of the first relay terminal.

[0188] It can be understood that, in the embodiments of the present application, for the non-end-to-end link between the relay terminal and the network device, one of the two device identification fields is used to indicate the device identification of the remote terminal, and the other device identification field is used to indicate the device identification of the relay terminal.

[0189] In the embodiments of the present application, the first message can be transmitted on the second link; wherein the second link is the link for the remote terminal to communicate with the network device.

[0190] It can be understood that, in the embodiments of the present application, the device identification for indicating the source node or the destination node can be carried in the SRAP header, which can be transmitted on the already established end-to-end physical link through the first message.

[0191] That is to say, in the embodiments of the present application, the device identification for distinguishing different logical links can share the end-to-end physical link.

[0192] In some embodiments of the present application, the first device identification is determined by one or more of the following: first node allocation; other terminal allocation; network device allocation.

[0193] It can be understood that, in the embodiments of the present application, the allocation mode of the first device identification can include a variety of different modes. Among them, it can be self-allocated, it can be allocated by other relay terminals, it can be allocated by remote terminals, and it can be allocated by network devices, which are not limited in the present application.

[0194] In the embodiments of the present application, if the first device identification is allocated by the first node, the first device identification is indicated to the other terminal and the network device through the first RRC message, or is indicated to the other terminal and the network device through the first multi-hop RRC message. The first multi-hop RRC message is the RRC message (one-hop RRC signaling) of each hop in the multi-hop link. The first multi-hop RRC message is the RRC message of each hop from the first node to the other terminal and the network device in the multi-hop link.

[0195] It should be noted that the first RRC message is the message directly sent by the first node to the other terminal, and the message directly sent by the first node to the network device. The first multi-hop RRC message is a one-hop RRC message sent to the next-hop third terminal from the first node to the second terminal (one of the other terminals) in the process of transmission, and then the next-hop third terminal reads the information from the one-hop RRC message, and continues to transmit to the next-hop fourth terminal by using the next-hop RRC message, until it is transmitted to the second terminal. Each one-hop RRC message in this process is a first multi-hop RRC message.

[0196] Exemplarily, in some embodiments, for the allocation mode that the first device identity is allocated by the first node itself, the UE ID information can be indicated to other UEs and network devices on the link by direct (direct RRC signaling) or forwarding (one-hop RRC signaling).

[0197] In the embodiments of the present application, if the first device identity is allocated by one of the other terminals, the first device identity is indicated to the first node, the remaining other terminals and the network device by a second RRC message, or is indicated to the first node, the remaining other terminals and the network device by a second multi-hop RRC message.

[0198] The second multi-hop RRC message is a one-hop RRC message transmitted from one of the other terminals to the remaining other terminals, the first node and the network device respectively.

[0199] It should be noted that the second RRC message is a message directly sent by one of the other terminals to the remaining other terminals, or a message directly sent by one of the other terminals to the network device, or a message directly sent by one of the other terminals to the first node. The second multi-hop RRC message is a one-hop RRC message sent to the next-hop second terminal from one of the other terminals in the process of transmitting to the destination device (one of the other terminals, the first node or the network device), and then the next-hop second terminal reads the information from the one-hop RRC message and continues to transmit to the next-hop third terminal by the next-hop RRC message until the destination device is reached. Each one-hop RRC message in the process is a second multi-hop RRC message.

[0200] Exemplarily, in some embodiments, for the allocation mode that the first device identity is allocated by the first node itself, the UE ID information can be indicated to other UEs and network devices on the link by direct (direct RRC signaling) or forwarding (one-hop RRC signaling).

[0201] Exemplarily, in some embodiments, for the allocation mode that the first device identity is allocated by the first node itself, the UE ID information can be indicated to other UEs and network devices on the link by direct (direct RRC signaling) or forwarding (one-hop RRC signaling).

[0202] In the embodiments of the present application, if the first device identifier is allocated by the network device, the first device identifier is indicated to the first node and the other terminal through a third RRC message or indicated to the first node and the other terminal through a third multi-hop RRC message; the first device identifier information is allocated by the network device based on the sidelink information; and the sidelink information is reported by the first node or the other terminal.

[0203] The third multi-hop RRC message is a one-hop RRC message sent to the next-hop second terminal in the process of transmission from the network device to the other terminal and the first node in the multi-hop link.

[0204] It should be noted that the third RRC message is a message sent directly by the network device to the other terminal or a message sent directly by the network device to the first node. The third multi-hop RRC message is a one-hop RRC message sent to the next-hop second terminal in the process of transmission from the network device to the destination terminal (one of the other terminals or the first node), and then the next-hop second terminal reads the information from the one-hop RRC message and continues to transmit the next-hop RRC message to the next-hop third terminal until it is transmitted to the destination terminal. Each one-hop RRC message in this process is a third multi-hop RRC message.

[0205] It can be understood that, in the embodiments of the present application, for the allocation manner of the network device allocation, that is, the network device allocates the corresponding first device identifier, the network device can further allocate the first device identifier according to the sidelink information after receiving the sidelink information reported by the first node or the other relay terminal or the remote key, and then select the first device identifier information to be directly indicated to the first node and the other terminal.

[0206] For example, in some embodiments, for the allocation manner of the network device allocation, that is, the network device allocates the corresponding first device identifier, the relay UE needs to report the sidelink information, and / or the other UE on the link reports the sidelink information of the link, so that the network device determines the topology of the multi-hop link, and the network device configures the UE ID for the relay UE according to the reported information, and indicates the UE ID information to the UE and the other UE on the link through direct (direct RRC signaling) or forwarding (one-hop-by-one-hop RRC signaling).

[0207] The topology can be understood as a list indexed by L2 ID, and based on the topology, the identity of the UE can be known, so that the allocation of the device identifier can be indexed by L2 ID.

[0208] In summary, different Local IDs / UE IDs carried in the SRAP layer packet header transmitted on the shared physical link can effectively distinguish different logical links, so as to accurately identify data packets or data, and further improve the accuracy of communication.

[0209] In the embodiments of the present application, in order to distinguish different logical links, another implementation is to explicitly indicate the target end (destination node) of the bearer in the SRAP packet header, so that each UE can identify whether the data is sent to itself according to the indication, thereby realizing the distinction of logical links.

[0210] In the embodiments of the present application, the first information can include a first adaptation layer identifier or a second adaptation layer identifier; wherein the first adaptation layer identifier is used to confirm that the first node processes the data packet associated with the first adaptation layer identifier; and the second adaptation layer identifier is used to confirm the egress of the data packet associated with the second adaptation layer identifier.

[0211] That is, in the embodiments of the present application, after obtaining the first information, if the first information includes the first adaptation layer identifier, then based on the first information, it can be further determined that the first node processes the data packet associated with the first adaptation layer identifier. If the first information includes the second adaptation layer identifier, then based on the first information, it can be further determined that the egress of the data packet associated with the second adaptation layer identifier.

[0212] It can be understood that, in the embodiments of the present application, for the relay link, there is transmission of data and / or signaling between two entities that are not end-to-end, for example, transmission of data and / or signaling between two relay terminals, or transmission of data and / or signaling between a remote terminal and a relay terminal, or transmission of data and / or signaling between a relay terminal and a network device. For the non-end-to-end link, the first adaptation layer identifier in the first information can be used to indicate the associated data packet, so that the received data packet can be directly delivered to the upper layer, such as the RRC layer and / or the PDCP layer.

[0213] It can be understood that, in the embodiments of the present application, for the relay link, there is transmission of data and / or signaling between two entities that are not end-to-end, for example, transmission of data and / or signaling between two relay terminals, or transmission of data and / or signaling between a remote terminal and a relay terminal, or transmission of data and / or signaling between a relay terminal and a network device. For the non-end-to-end link, the first adaptation layer identifier in the first information can be used to indicate the associated data packet, so that the received data packet can be directly delivered to the upper layer, such as the RRC layer and / or the PDCP layer.

[0214] That is, in the embodiments of the present application, different processing can be performed on the end-to-end link and the non-end-to-end link by the first adaptation layer identifier or the second adaptation layer identifier included in the first information.

[0215] In the embodiments of the present application, the first message carrying the first adaptation layer identifier is transmitted on the first link; or the first message carrying the second adaptation layer identifier is transmitted on the second link.

[0216] In the embodiments of the present application, the first adaptation layer identifier includes one or more of the following: source node identifier and / or destination node identifier on the second link; the second link is a multi-hop link for communication between the remote terminal and the network device; node indication information on the second link; one or more of the source node identifier and the destination node identifier on the second link, and hop count information.

[0217] That is, in the embodiments of the present application, for the first adaptation layer identifier in the first information, when determining and indicating the processing of the data packet associated with the first adaptation layer identifier at the first node, a plurality of indication methods can be used.

[0218] In the embodiments of the present application, one indication method is that the first adaptation layer identifier indicates the source node and the destination node on the second link. Wherein, the source node of the link can be indicated by the source node identifier on the second link, and the destination node of the link can be indicated by the destination node identifier on the second link.

[0219] It can be understood that in the embodiments of the present application, the second link can be a multi-hop link for communication between the remote terminal and the network device, that is, the second link can be an end-to-end link that has been established and connected.

[0220] In the embodiments of the present application, the source node identifier and / or the destination node identifier are indicated by a first number of bits of the binary of the unique identifier of the node according to the node order on the second link; the number of bits of the first number of bits is related to the number of terminals on the second link; and / or,

[0221] The source node identifier and / or the destination node identifier are indicated by the assigned device identifier.

[0222] In the embodiments of the present application, the number of terminals includes one or more of the following:

[0223] The first number of terminals on the second link except the remote terminal;

[0224] The second number of terminals on the second link except the remote terminal and the near-end relay terminal.

[0225] Exemplarily, in some embodiments, the source node and the destination node can be indicated in an ID manner, each ID being log2[user number on the link (all UEs) or user number-1 (only indicating the Relay UE, i.e., the first number) or user number-2 (the second number) bits. Wherein, the user number can be understood as the number of terminals.

[0226] Exemplarily, in some embodiments, the ID only needs to be unique within the link, and the ID can be protocol specified, i.e., Remote UE is 000, the first Relay is 001 in the node order (or the reverse order), or can be a configured ID, such as network configuration or Remote UE configuration, or a certain Relay configuration. Each UE determines whether the data is associated to itself or the corresponding routing path (egress link and / or RLC channel) according to the ID information in the received data packet header.

[0227] Exemplarily, in some embodiments, FIG. 9 is a schematic diagram of the first adaptation layer identifier indication according to an embodiment of the present application. As shown in FIG. 9, the source node identifier Source ID on the second link can be used to indicate the source node of the link, and at the same time, the destination node identifier Destination ID on the second link can be used to indicate the destination node of the link.

[0228] In an embodiment of the present application, another indication manner is that the first adaptation layer identifier indicates the source node or the destination node on the second link, and at the same time, indicates the hop number information. Wherein, the source node identifier on the second link can be used to indicate the source node of the link, or the destination node identifier on the second link can be used to indicate the destination node of the link. The hop number information on the second link can also be used to indicate the hop number hop.

[0229] It can be understood that, in an embodiment of the present application, in the case that the source node and the hop number are indicated by the first adaptation layer identifier, the corresponding destination node can be further determined; correspondingly, in the case that the destination node and the hop number are indicated by the first adaptation layer identifier, the corresponding source node can be further determined.

[0230] Exemplarily, in some embodiments, FIG. 10 is a schematic diagram II of the first adaptation layer identifier indication according to an embodiment of the present application. As shown in FIG. 10, the hop number can be indicated while indicating the source node (or the target node) in the link. Each ID is log2[user number (all UEs) or user number-1 (only indicating Relay UE) or user number-2 (only indicating intermediate UE) on the link] bits. The ID only needs to be unique in the link. The ID can be protocol specified, i.e., Remote UE is 000, the first Relay is 001 in order (or in reverse order), or can be a configured ID, such as network configuration or Remote UE configuration, or a certain Relay configuration. Each UE determines whether the data is associated to itself or the corresponding routing path (egress link and / or RLC channel) according to the ID information in the received data packet header and the hop number information.

[0231] In an embodiment of the present application, another indication manner is that the first adaptation layer identifier indicates each hop node on the second link. The corresponding each hop node can be indicated by the node indication information on the second link.

[0232] It can be understood that, in an embodiment of the present application, the node indication information on the second link is bitmap information, and each bit of the bitmap information corresponds to each hop node on the second link.

[0233] It should be noted that the node indication information on the second link is a domain value, the domain value is represented by a binary number, the domain value is determined by whether the bearer identifier in the adaptation layer identifier is associated with the node, and the domain value corresponds to each hop node on the second link.

[0234] It can be understood that, in an embodiment of the present application, the threshold value can be a value of H threshold, and the threshold value includes but is not limited to 0 and 1. If the threshold value is 0, the threshold value can indicate that the bearer identifier in the adaptation layer identifier is not associated with the node. If the threshold value is 1, the threshold value can indicate that the bearer identifier in the adaptation layer identifier is associated with the node.

[0235] Exemplarily, in some embodiments, FIG. 11 is a schematic diagram III of the first adaptation layer identifier indication according to an embodiment of the present application. As shown in FIG. 11, the bit graph can be used for indication. Each threshold H of the H domain from left to right indicates whether the bearer identifier in the adaptation layer identifier is associated with the node. For example, for a three-hop relay link from a Remote UE to a network device, for each Bearer, if the node is related to the Bearer (the source or target of the Bearer), the corresponding threshold of the H domain is filled with 1, otherwise, the corresponding threshold of the H domain is filled with 0. If the maximum number of nodes is 5, the last few bits are empty.

[0236] In summary, by explicitly indicating the target end (destination node) of the bearer in the SRAP layer packet header transmitted on the shared physical link, each UE can identify whether the data is sent to itself according to the indication, different logical links can be effectively distinguished, and the identification of the data packet or data can be accurately realized, thereby improving the accuracy of communication.

[0237] In some embodiments of the present application, the target end (i.e., the destination node) of the bearer is explicitly indicated in the SRAP packet header, and each UE can identify whether the data is sent to itself according to the indication. In this process, when the destination node of the bearer is explicitly indicated in the SRAP packet header, the UE ID can also be indicated, which has a corresponding relationship with the above-mentioned BEARER, so that the UE can identify whether the data is sent to itself according to the indication.

[0238] It should be noted that in the embodiments of the present application, the carrying and indicating manner of the UE ID can be consistent with the allocation manner of the first device identifier, and one device identifier field and / or two device identifier fields in the foregoing embodiments can be used for corresponding indication, which will not be described herein.

[0239] In the embodiments of the present application, in order to distinguish different logical links, another implementation manner is to use different bearer identifiers (BEARER IDs), so that the UE and the network can identify whether the data is sent to itself through different BEARER IDs in the SRAP packet header, thereby realizing the distinction of logical links.

[0240] In some embodiments of the present application, the first adaptation layer identifier includes a first bearer identifier, and the second adaptation layer identifier includes a second bearer identifier. The first bearer identifier and the second bearer identifier are identifiers of bearers associated with the first node corresponding to different source nodes; or the first bearer identifier and the second bearer identifier are identifiers of bearers associated with the first node corresponding to different destination nodes.

[0241] It can be understood that in the embodiments of the present application, the BEARER IDs used by the bearers associated with different source nodes are different, and the BEARER IDs used by the bearers associated with different target nodes are different. The BEARER ID can be obtained by allocation or calculation, which is not limited in the present application.

[0242] In the embodiments of the present application, the first bearer identifier or the second bearer identifier is allocated by the network device, and the first bearer identifier and the second bearer identifier are different from the bearer identifiers of other terminals on the multi-hop link.

[0243] It can be understood that in the embodiments of the present application, when the configuration of the BEARER ID is performed, the network device can be assigned a BEARER ID associated with the network device by the network, and the network device needs to ensure that the BEARER IDs between different UEs on the same multi-hop U2N relay link are different.

[0244] It can be understood that in the embodiments of the present application, the BEARER ID of the source node or the target node of the BEARER of the UE can be assigned by the network device, and the network device needs to ensure that the BEARER IDs between different UEs on the same multi-hop U2N relay link are different.

[0245] In the embodiments of the present application, if the source node and the destination node associated with the first bearer identifier are both terminals, the first bearer identifier is assigned to one or more of the following: a remote terminal; a relay terminal; wherein the first bearer identifier is different from the bearer identifier of other terminals on the multi-hop link assigned by the network device.

[0246] In the embodiments of the present application, the first bearer identifier is reported to the network device, so that the network device on the multi-hop link assigns a bearer identifier to other terminals, which is different from the first bearer identifier.

[0247] That is, in the embodiments of the present application, the BEARER ID of the source node or the target node of the BEARER of the UE can be assigned by the Remote UE. Among them, after the network device assigns, the Remote UE ensures that the BEARER IDs between different UEs on the same multi-hop U2N relay link are different; or, before the network device assigns, the Remote UE reports the assigned BEARER ID to the network device, and the network device ensures that the BEARER IDs between different UEs on the same multi-hop U2N relay link are different in subsequent assignments.

[0248] That is, in the embodiments of the present application, the BEARER ID of the source node or the target node of the BEARER of the UE can be assigned by the Relay UE. Among them, after the network device assigns, the Relay UE knows the BEARER ID assigned by the network device through direct or other UE forwarding, and ensures that the BEARER IDs between different UEs on the same multi-hop U2N relay link are different in subsequent assignments; or, before the network device assigns, the Relay UE reports the assigned BEARER ID to the network device through direct or other UE forwarding, and the network device ensures that the BEARER IDs between different UEs on the same multi-hop U2N relay link are different in subsequent assignments.

[0249] In the embodiments of the present application, the first bearer identifier is determined according to the second bearer identifier, the maximum number of bearers, the total number of hops, and the number of hops where the first node is located.

[0250] It can be understood that, in the embodiments of the present application, when the calculation of the BEARER ID is performed, the BEARER ID is calculated according to the actual value of the BEARER ID (for example, the value configured in the DRB ID or the SRB ID or the slrb-PC5-ConfigIndex), in combination with the maximum number of bearers (32) or the number of relays or the number of hops where the node is located. For example, in the scenario of two relays, the actual bit value of the end-to-end BEARER ID is 5, and the BEARER ID value from the network device to Relay1 is the actual value + 16. That is, the IDs are different between different hops, for example, the value corresponding to the remote terminal to the network device is 0-16; the value corresponding to Relay1 to the network device is 17-32.

[0251] In the embodiments of the present application, the second bearer identifier is one or more of the following: an identifier of a signaling bearer; an identifier of a data bearer; and a fourth configured value. The value of the fourth value is not specifically limited.

[0252] In the embodiments of the present application, the first information includes one or more bearer identifiers, wherein the one or more bearer identifiers include a third end-to-end bearer identifier and a fourth non-end-to-end bearer identifier, and the bearer identifiers correspond one-to-one to RRC connections.

[0253] It can be understood that, in the embodiments of the present application, more than one BEARER ID is included in the SRAP header, one of which is an end-to-end quality of service (E2E QoS) BEARER ID, that is, end-to-end, and the other is a UE-to-UE or UE-to-network device BEARER ID. In this case, it can be indicated which BEARER ID corresponds to which RRC connection in a protocol-defined manner or an explicit indication manner, and accordingly, the UE also needs to know whether it is for itself, that is, the UE can identify whether the data is sent to itself according to the indication.

[0254] In some embodiments of the present application, different BEARER IDs are used in the SRAP header, and each UE can identify whether the data is sent to itself according to the indication. In this process, when the BEARER ID is indicated in the SRAP header, the UE ID can also be indicated at the same time, and the UE ID corresponds to the above-mentioned BEARER, so that the UE can identify whether the data is sent to itself according to the indication.

[0255] It should be noted that in the embodiments of the present application, the carrying manner and the indicating manner of the UE ID can be consistent with the allocation manner of the first device identifier, and one device identifier field and / or two device identifier fields in the foregoing embodiments can be used for corresponding indication, which will not be described herein again.

[0256] In summary, by using different bearer identifiers (BEARER IDs) in the SRAP layer, the UE and the network device can identify whether the data is sent to itself through different BEARER IDs in the SRAP header, different logical links can be effectively distinguished, and the accuracy of communication can be improved.

[0257] In the embodiments of the present application, in order to distinguish different logical links, another implementation manner is to distinguish different Bearers according to different RLC channels to distinguish different logical links.

[0258] In the embodiments of the present application, the first information includes a first RLC channel or a second RLC channel; the first RLC channel is used to confirm that the data packet associated with the first RLC channel is processed at the first node; and the second adaptation layer identifier is used to confirm the exit of the data packet associated with the second RLC channel.

[0259] That is, in the embodiments of the present application, after obtaining the first information, if the first information includes the first RLC channel, it can be determined based on the first information that the data packet associated with the first RLC channel is processed at the first node. If the first information includes the second RLC channel, it can be determined based on the first information that the exit of the data packet associated with the second RLC channel.

[0260] It can be understood that in the embodiments of the present application, for the relay link, there is transmission of data and / or signaling between two entities that are not end-to-end, for example, transmission of data and / or signaling between two relay terminals, or transmission of data and / or signaling between a remote terminal and a relay terminal, or transmission of data and / or signaling between a relay terminal and a network device. For the non-end-to-end link, the associated data packet can be indicated through the first RLC channel in the first information, so that the received data packet can be directly delivered to the upper layer, for example, the RRC layer and / or the PDCP layer.

[0261] It can be understood that, in the embodiment of the present application, for the relay link, there is transmission of data and / or signaling between two entities of an end-to-end, such as transmission of data and / or signaling between a remote terminal and a network device. Among them, for the end-to-end link, the egress of the associated data packet can be indicated by the second RLC channel in the first information, for example, it can be routed to the corresponding egress RLC channel according to the configuration of SRAP.

[0262] That is, in the embodiment of the present application, different processing can be performed on the end-to-end link and the non-end-to-end link by the first RLC channel or the second RLC channel included in the first information.

[0263] In the embodiment of the present application, the first message carrying the second information is transmitted on the first link; or the first message carrying the third information is transmitted on the second link. Among them, the second information can include the first RLC channel, and correspondingly, the first RLC channel can be used to confirm the processing of the data packet associated with the first RLC channel at the first node; the third information can include the second RLC channel, and correspondingly, the second RLC channel can be used to confirm the egress of the data packet associated with the second RLC channel.

[0264] In the embodiment of the present application, the first RLC channel and the second RLC channel are RLC channels used by bearers associated with the first node corresponding to different source nodes; or the first RLC channel and the second RLC channel are RLC channels used by bearers associated with the first node corresponding to different destination nodes.

[0265] It can be understood that, in the embodiment of the present application, different bearers of the source node and the target node cannot be associated with the same RLC channel, that is, the UE identifies whether the data is sent to itself or needs to be further forwarded by the RLC channel receiving the data.

[0266] It can be understood that, in the embodiment of the present application, the association relationship between the Bearer and the RLC channel can be configured or can be specified by the protocol, and the present application does not make specific limitation.

[0267] In the embodiment of the present application, the first RLC channel or the second RLC channel is allocated by the network device, and the first RLC channel or the second RLC channel is different from the RLC channel used by the bearer of the other terminal on the multi-hop link.

[0268] It can be understood that, in the embodiments of the present application, the association relationship of the Bearer associated with the network, the Bearer and the RLC channel can be configured by the network device, and the network device needs to ensure that the RLC channels used by different Bearers between different UEs on the same multi-hop U2N relay link are different.

[0269] In the embodiments of the present application, if the source node and the destination node associated with the first RLC channel or the second RLC channel are both terminals, the first RLC channel or the second RLC channel is assigned to one or more of the following: a terminal acting as a sending node in each hop on the multi-hop link; a remote terminal; a relay terminal.

[0270] It can be understood that, in the embodiments of the present application, the source node or the target node is a BEARER of a UE, which can be allocated by the network device, and the network device needs to ensure that the RLC channels used by different Bearers between different UEs on the same multi-hop U2N relay link are different.

[0271] In the embodiments of the present application, if the first RLC channel or the second RLC channel is assigned to a terminal acting as a sending node, the first RLC channel or the second RLC channel is determined based on one or more of the following: the sending node or the receiving node of the Bearer associated with the first node; the associated quality of service information.

[0272] In the embodiments of the present application, the quality of service information includes one or more of the following: end-to-end quality of service information; quality of service information of a Uu segment in the first path, and / or quality of service information of one or more PC5 segments in the first path.

[0273] It can be understood that, in the embodiments of the present application, the source node or the target node is a BEARER of a UE, which can be configured by the sending UE of each hop, in which case the UE needs to know the associated sender and receiver information of each Bearer, the associated QoS information (E2E QoS and / or split QoS), which can be obtained through PC5 RRC or Uu RRC information, and then the RLC channel information can be derived according to the information, and it is ensured that the Bearers of different sending and receiving parties are associated with different RLC channels, and the corresponding receiving end is informed of the association relationship between the Bearer and the RLC channel.

[0274] In the embodiments of the present application, the first RLC channel or the second RLC channel is reported to the network device, so that the network device on the multi-hop link allocates RLC channels used by Bearers of other terminals to be different from the first RLC channel or the second RLC channel.

[0275] It can be understood that, in the embodiments of the present application, the source node or the target node is a BEARER of the UE, which can be configured by a sending UE of the Bearer, or configured for a remote UE, or configured for a relay UE. Wherein, after network allocation, the UE ensures that the RLC channels of different Bearers between different UEs on the same multi-hop U2N relay link are different; or, before network allocation, the UE reports the configured RLC channel to the network device, and the network device needs to ensure that the subsequent allocation of the RLC channels of different Bearers between different UEs on the same multi-hop U2N relay link are different.

[0276] In the embodiments of the present application, the first RLC channel or the second RLC channel is synchronized to other terminals in the multi-hop link; and the RLC channels used by the Bearers between each terminal in the multi-hop link are different.

[0277] It can be understood that, in the embodiments of the present application, the source node or the target node is a BEARER of the UE, which can be directly informed to other UEs or reported to the network.

[0278] It can be understood that, in the embodiments of the present application, the correspondence between the hop number and the RLC channel can be specified based on the protocol, and which Bearer uses which RLC channel for transmission can also be specified.

[0279] In summary, by identifying different Bearers according to different RLC channel configurations, different logical links can be effectively distinguished.

[0280] In summary, by using different channel identifiers (RLC channel IDs) at the RLC layer, the UE and the network device can identify whether the data is sent to itself through the different RLC channel IDs in the RLC layer packet header, and different logical links can be effectively distinguished, thereby improving the accuracy of communication.

[0281] The embodiment of the present application provides a communication method. A first node acquires first information, and the first information is used for identifying a data packet; and based on the first information, at least one of the following is performed: determining that the first node processes the data packet associated with the first information; and determining an egress of the data packet associated with the first information. Therefore, in the embodiment of the present application, for an end-to-end link, the egress of the associated data packet can be determined through acquisition of the first information, and for a non-end-to-end link, the associated data packet processed by the first node can be determined through acquisition of the first information. That is, the first node can determine accurate data routing by using the first information, thereby solving the problem that the Relay UE cannot identify two different data when receiving the data, and then different logical links can be distinguished, and the accuracy of communication is improved.

[0282] Based on the above embodiment, in another embodiment of the present application, a communication method capable of effectively distinguishing multiple logical links on a shared physical link is provided for the influence of introducing multi-hop on SRAP data routing.

[0283] As shown in FIG. 6 and FIG. 7, there is data transmission between Remote UE and network (that is, network equipment such as a base station) (end-to-end multi-hop terminal data), and there is also data and signaling transmission between two entities that are not end-to-end, such as data and signaling transmission between Remote UE and Relay UE2 or between Relay1 and the network. Since the source-target of the non-end-to-end Bearer is different from that of the end-to-end multi-hop relay data, that is, the end-to-end source and target of the end-to-end multi-hop relay data are Remote UE and the base station. The end-to-end source and target of the non-end-to-end control signaling and data transmission are Remote UE to Relay UE or Relay UE to the base station, and therefore the processing manner of the data in the SRAP is different:

[0284] For end-to-end relay data, the Relay UE is not the receiver of the data, and when the data is received from the receiving side of the SRAP, the data is directly routed to the corresponding egress RLC channel according to the configuration of the SRAP.

[0285] For non-end-to-end (PC5-S / PC5-RRC on PC5, or RRC / NAS signaling or data information between the network), the UE needs to directly deliver the received data to the upper layer (RRC layer and / or PDCP layer).

[0286] Therefore, the problem that the Relay UE cannot identify two different data when receiving the data needs to be solved.

[0287] The communication method provided by the embodiments of the present application can realize the differentiation of logical links by any of the following methods:

[0288] According to different L2 IDs / link IDs;

[0289] According to different Local IDs / UE IDs in the SRAP layer packet header;

[0290] Using explicit indication of the destination end of the BEARER in the SRAP packet header;

[0291] Using different BEARER IDs in the SRAP packet header;

[0292] According to different RLC channel configurations to identify different Bearers.

[0293] The wireless communication method provided by the embodiments of the present application is further described below.

[0294] Method one: when differentiating according to different L2 IDs / link IDs, different Bearers of the target end cannot be associated to the same link, that is, different L2 IDs / link IDs need to be used by the UE to send Bearers of different source / target entities.

[0295] For the processing of non-end-to-end links on PC5, such as the non-direct PC5 connection between Remote and Relay2 in FIG. 6, the connection between Relay1 and Relay2, or the non-direct PC5 connection between Relay1 and Relay3 in FIG. 7, the connection between Relay1 and Relay2, and the link between Relay1 and the network in FIG. 6, the connection between Relay2 and the network in FIG. 7, the connection between Relay2 and Relay3. The non-end-to-end link on PC5 uses a different PC5 link from the end-to-end multi-hop U2N relay link, that is, if an end-to-end multi-hop U2N relay link has been established between two entities, there is a demand for data and signaling transmission between non-end-to-end entities at this time:

[0296] Take Relay1 as an example: normal UE's U2N / U2U Relay link establishment procedure is carried out separately, including relay discovery, selection, link establishment using separate L2 ID (reference U2U / U2N relay establishment mechanism in R17 / R18). The U2N / U2U relay establishment process can select other relay UEs through Relay2 or not. The separate L2 ID is indicated by the upper layer (Prose layer) according to the business by default. Conversely, similar (the established U2U Relay link also has multi-hop U2N relay requirements). In this case, Relay1 using different L2 ID is an independent UE for Relay2. Because different sources / targets use different PC5 links, L2 ID, the UE can identify how to route and process the data packet when receiving the corresponding data packet.

[0297] A new PC5 link is re-established with the already connected Relay2 to transmit the U2N of Relay1 to the network or the U2U relay signaling / data of Relay1 to Relay3. The U2N, U2U relay establishment process can be a simplified U2N, U2U connection establishment process, i.e. without relay discovery and / or selection:

[0298] 1) Relay1 knows the capability information of Relay2 through unicast transmission on link1, such as whether to support single-hop U2N relay, U2U relay, multi-hop U2N relay, the capability information is exchanged through PC5 RRC message (capability exchange information) or PC5-S message (Discovery message or Link Modification message)

[0299] 2) Establish link2 through unicast DCR / DCA method. One way is that the L2 ID used by the link2 can be the L2 ID information communicated on the link1 for the L2 ID used on the link2 (PC5 RRC message or PC5-S message); another implementation way is that the L2 ID used by the link2 is the default L2 ID, and another implementation way is that Relay1 first uses different source L2 ID and the same destination L2 ID to send DCR message, and Relay2 replies DCA message to Relay1 using the updated L2 ID after receiving it.

[0300] In the case of distinguishing according to different L2 IDs / link IDs, the processing of non-end-to-end links on Uu is as shown in FIG. 6, the link between Relay 1 and the network, or the link between Relay 2 and the network. For the network, its communication with the UE is on the Uu port, and since the L2 ID is the device identifier of the UE on the PC5, the network cannot uniquely identify the UE by the L2 ID. Moreover, there is only one RRC connection between the same UE and the same network at the same time, so even if different L2 IDs are used, Relay 1 is still a user in the eyes of the network, although it accesses the network through different Relay links using different L2 IDs. Therefore, the UE needs to report to the network that it uses two L2 IDs to access the network, and the reporting method is through an RRC message.

[0301] The reporting content can be:

[0302] The corresponding source L2 ID for data transmission / communication (non-discovery) for each link / destination L2 ID;

[0303] The association relationship between the two source L2 IDs.

[0304] Method two: In the case of distinguishing according to different Local IDs / UE IDs in the SRAP layer packet header, for the link between Remote and Relay 2 as shown in FIG. 6, or the link between Relay 1 and Relay 3 as shown in FIG. 7, and the link between Relay 1 and the network as shown in FIG. 6, or the link between Relay 2 and the network as shown in FIG. 7. A UE ID (or Local ID) can be additionally allocated to the relay UE except the Remote UE on the link, and the UE ID information of the UE is carried in the SRAP packet header to identify that the data is sent to the UE or comes from the UE, that is, to indicate the source node and the target node.

[0305] The allocation method of the UE ID can be:

[0306] 1. The relay UE itself allocates the UE ID, and indicates the UE ID information to other UEs and the network on the link through direct (direct RRC signaling) or forwarding (one-hop RRC signaling).

[0307] 2. Or other relay UEs allocate the UE ID, and indicate the UE ID information to the UE and other UEs and the network on the link through direct (direct RRC signaling) or forwarding (one-hop RRC signaling).

[0308] 3. Or assigned by Remote UE, and the UE ID information is indicated to the UE and other UEs and network on the link by direct (direct RRC signaling) or forwarding (one-hop RRC signaling).

[0309] 4. Or assigned by network, in this case, the relay UE needs to report the sidelink information, and / or other UEs on the link report the sidelink information of the link (report through SUI), so that the network knows the topology of the multi-hop link. The network configures the UE ID for the relay UE according to the reported information (such as topology, i.e. list of layer 2 ID as index), and indicates the UE ID information to the UE and other UEs on the link by direct (direct RRC signaling) or forwarding (one-hop RRC signaling).

[0310] The assigned UE ID is different from the UE ID of other UEs on the link, and / or different from the UE ID of other UEs on all links of the relay UE

[0311] The node carries a UE ID field (device identifier field) or two UE ID fields in the SRAP header when sending data.

[0312] 1) One UE ID field is the UE ID of the UE, which is used for non-end-to-end Bearer transmission between the UE and the network, such as the Bearer between Relay1 and the network in FIG. 6, or the Bearer between Relay2 and the network in FIG. 7.

[0313] 2) Two UE ID fields are the IDs of the source and target entities (including UEs and networks);

[0314] The end-to-end Bearer of the Remote UE to the network omits one UE ID, or both fills the Remote UE ID or one fills the default value (such as all 0 or all 1) and the other fills the Remote UE ID;

[0315] The ID is the default value or the ID configured by the network in the case of one end being the network.

[0316] 3) Two UE ID fields are the UE ID and the Remote UE ID of the link, which are used for non-end-to-end Bearer transmission between the UE and the network, such as the Bearer between Relay1 and the network in FIG. 6, or the Bearer between Relay2 and the network in FIG. 7 (carrying the Remote ID and the UE id of itself.)

[0317] In the SRAP header, explicitly indicate the destination of the BEARER, so that each UE can identify whether the data is sent to itself according to the indication.

[0318] Method three: for the link between Remote and Relay2 as in Figure 6, or Relay1 and Relay3 as in Figure 7, and the link between Relay1 and network as in Figure 6, or Relay2 and network as in Figure 7, in addition to the UE ID and BEARER ID in the SRAP commonly used to identify how each Bearer is routed / processed, the following information explicitly indicating the data packet is additionally carried:

[0319] Target and / or source;

[0320] Is it a PC5 or Uu Bearer?

[0321] The number of hops experienced.

[0322] Based on the explicit indication in the SRAP header, one way to distinguish logical links is to indicate the source + target within the link:

[0323] 1) Indicate in ID: each ID is log2 [the number of users (all UEs) or the number of users - 1 (only need to indicate Relay UE) or the number of users - 2 (only need to indicate intermediate UE) on the link] bits. The ID only needs to be unique within the link, the ID can be protocol specified, i.e. Remote UE is 000, the first Relay in order is 001… (or the reverse order), or it can be a configured ID, such as network configuration or Remote UE configuration, or a certain Relay configuration. Each UE determines whether the data is associated with itself or the corresponding routing path (egress link and / or RLC channel) according to the ID information in the received data header.

[0324] 2) Indicate in bit map: as shown in Figure 7, each H from left to right represents a node, representing the three-hop relay link from Remote UE to network. For each Bearer, if the node is related to the Bearer (source or target of the Bearer), fill 1 in the corresponding H domain, otherwise fill 0, and the last one is empty if less than 5 bits.

[0325] 3) Another way to distinguish logical links based on explicit indication in SRAP header is to indicate the source (or destination) + hop number within the link. Where each ID is log2[the number of users (all UEs) or the number of users -1 (only need to indicate Relay UE) or the number of users -2 (only need to indicate intermediate UE)] bits. The ID only needs to be unique within this link, the ID can be protocol specified, i.e. Remote UE is 000, the first Relay is 001 in order (or the reverse order), or it can be a configured ID, such as network configuration or Remote UE configuration, or a certain Relay configuration. Each UE determines whether the data is associated to itself or the corresponding routing path (egress link and / or RLC channel) according to the ID information in the received data packet header and the hop number information.

[0326] Exemplarily, in some embodiments, FIG. 12 is a schematic diagram four of the first adaptation layer identification indication proposed in the embodiments of the present application, as shown in FIG. 12, the hop number can be indicated at the same time when indicating the target node within the link.

[0327] Method four: Different BEARER IDs are used, and the UE and the network can identify whether the data is sent to itself through different BEARER IDs in the SRAP packet header. Where the BEARER IDs used by the Bearers associated to different source / destination nodes are different, the BEARER ID can be configured or calculated.

[0328] 1) When configuring the BEARER ID:

[0329] a) to the network, the BEARER ID associated to the network is allocated by the network, and the network ensures that the BEARER IDs between different UEs on the same multi-hop U2N relay link are different.

[0330] b) the BEARER ID of the BEARER whose source and destination are both UEs is:

[0331] The BEARER ID allocated by the network ensures that the BEARER IDs between different UEs on the same multi-hop U2N relay link are different;

[0332] Or the BEARER ID is allocated by the Remote UE, after the network allocation, the Remote UE ensures that the BEARER IDs between different UEs on the same multi-hop U2N relay link are different; or before the network allocation, the Remote UE reports the allocated BEARER ID to the network, and the network ensures that the subsequent allocation of the BEARER IDs between different UEs on the same multi-hop U2N relay link are different;

[0333] Or the BEARER ID is assigned by the relay UE, after the network assignment, the relay UE knows the network assigned BEARER ID through direct or other UE forwarding, and ensures that the subsequent assignment of the BEARER ID between different UEs on the same multi-hop U2N relay link is different; or before the network assignment, the relay UE reports the assigned BEARER ID to the network through direct or other UE forwarding, and the network ensures that the subsequent assignment of the BEARER ID between different UEs on the same multi-hop U2N relay link is different.

[0334] 2) In the calculation of BEARER ID: the BEARER ID is calculated according to the actual BEARER ID value (DRB ID or SRB ID or slrb-PC5-ConfigIndex configured value) and the maximum BEARER number (32) / relay number / hop number, such as the scenario of two relays, the end-to-end BEARER ID is the actual value, and the BEARER ID value from the network to relay 1 is the actual value + 16.

[0335] More than one BEARER ID is included in the SRAP header, one of which is an E2E BEARER ID, and the others are UE-to-UE or UE-to-network. In this case, it can be indicated which BEARER ID corresponds to which RRC connection in a protocol-defined manner or an explicit identification manner.

[0336] Method five: Different Bearer is identified according to different RLC channel configuration. Among them, the different Bearers of the source and target cannot be associated to the same RLC channel, that is, the UE identifies whether the data received by the RLC channel is sent to itself or needs to be further forwarded by itself.

[0337] The association relationship between Bearer and RLC channel can be configured or protocol-defined.

[0338] 3) In the configuration of the association relationship between Bearer and RLC channel:

[0339] a) The Bearer associated with the network is configured by the network, and the network ensures that the RLC channel used by the Bearer between different UEs on the same multi-hop U2N relay link is different.

[0340] b) The Bearer of the source and target is:

[0341] The network-configured network ensures that the RLC channels used by different UEs on the same multi-hop U2N relay link are different.

[0342] Or each hop is configured by the transmitting UE, in which case the UE needs to know the associated transmitter and receiver information of each Bearer, the associated QoS information (E2E QoS and / or split QoS) (through PC5 RRC or Uu RRC information), and derive the RLC channel information according to the information, and ensure that the Bearers with different transmitter and receiver are associated with different RLC channels, and inform the corresponding receiver of the association between the Bearer and the RLC channel

[0343] The transmitting UE of the Bearer is configured, or the RLC channel is configured for the remote UE, or the relay UE is configured, and after network allocation, the UE ensures that the RLC channels of different UEs on the same multi-hop U2N relay link are different; or before network allocation, the UE reports the configured RLC channel to the network, and the network ensures that the RLC channels of different UEs on the same multi-hop U2N relay link are different in subsequent allocation.

[0344] Directly inform other UEs or report to the network.

[0345] Among them, the protocol can specify the correspondence between the number of hops and the RLC channel, and specify which RLC channel to use for which Bearer.

[0346] The embodiment of the application provides a communication method. For an end-to-end link, the first information can be used to determine the exit of the associated data packet. For a non-end-to-end link, the first information can be used to determine the associated data packet processed by the first node. That is, the first node can use the first information to determine the accurate data routing, thereby solving the problem that the Relay UE cannot identify two different data when receiving the data, and can distinguish different logical links on different physical links, or distinguish different logical links through different UE IDs / Bearer IDs of the SRAP layer through a shared physical link, or distinguish different logical links by using different RLC channels through a shared physical link, accurately identify data packets or data, and further improve the accuracy of communication.

[0347] The preferred embodiments of the present application are described in detail above with reference to the drawings, but the present application is not limited to the specific details of the above-described embodiments. Within the technical concept of the present application, various simple modifications can be made to the technical solutions of the present application, and these simple modifications all belong to the protection scope of the present application. For example, in the above-described specific embodiments, various specific technical features described in the embodiments can be combined in any appropriate manner without contradiction. In order to avoid unnecessary repetition, various possible combinations are not described again in the present application. For another example, various different embodiments of the present application can also be combined in any manner, as long as it does not deviate from the idea of the present application, and it should also be considered as disclosed in the present application. For another example, under the premise of no conflict, each embodiment described in the present application and / or technical features in each embodiment can be combined with any prior art, and the technical solutions obtained after combination should also fall within the protection scope of the present application.

[0348] It should also be understood that, in various method embodiments of the present application, the magnitude of the sequence number of the above-described processes does not mean the order of execution, and the execution order of the processes should be determined according to its function and inherent logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. In addition, in the embodiments of the present application, the terms "downlink", "uplink" and "sidelink" are used to represent the transmission direction of signals or data, wherein "downlink" is used to represent the first direction of the transmission direction of signals or data from the station to the user equipment of the cell, "uplink" is used to represent the second direction of the transmission direction of signals or data from the user equipment of the cell to the station, and "sidelink" is used to represent the third direction of the transmission direction of signals or data from the user equipment 1 to the user equipment 2. For example, "downlink signal" represents that the transmission direction of the signal is the first direction. In addition, in the embodiments of the present application, the term "and / or" is only used to describe the association relationship of the associated objects, and indicates that there can be three relationships. Specifically, A and / or B can represent three cases of A alone, A and B together, and B alone. In addition, the character " / " in this paper generally represents that the front and rear associated objects are in an "or" relationship.

[0349] FIG. 13 is a structural composition schematic diagram of a communication apparatus provided by the embodiments of the present application, which is applied to a first node, as shown in FIG. 13, the communication apparatus 130 comprises:

[0350] The acquisition unit 1301 is configured to acquire first information, wherein the first information is used to identify a data packet;

[0351] The determination unit 1302 is configured to perform at least one of the following based on the first information:

[0352] Determine to process the data packet associated with the first information at the first node;

[0353] determining an egress of a data packet associated with the first information.

[0354] In some embodiments, the egress comprises an egress link and / or an egress channel.

[0355] In some embodiments, a first message is received or sent; the first message carries the first information, the first message is sent by a third node; or the first message is sent to a second node.

[0356] In some embodiments, the first node is a first relay terminal;

[0357] The second node comprises one or more of the following: a remote terminal, a second relay terminal, and a network device.

[0358] The third node comprises one or more of the following: a remote terminal, a third relay terminal, and a network device.

[0359] In some embodiments, the first information comprises a first link identifier or a second link identifier; the first link identifier is used to confirm that a data packet associated with the first link identifier is processed at the first node; the second link identifier is used to confirm the egress of a data packet associated with the second link identifier; wherein,

[0360] The first link is a non-end-to-end link associated with the first node.

[0361] The second link is an end-to-end multi-hop U2N relay link or a non-end-to-end link not associated with the first node.

[0362] In some embodiments, the determining unit 1302 is further configured to determine the second node and / or the third node;

[0363] establish a first link with the second node and / or the third node, respectively; the first link comprises a first link identifier;

[0364] The first node has a connected second link with the second node and the third node, respectively; a second link identifier of the second link is different from the first link identifier.

[0365] In some embodiments, a first message carrying the first link identifier is transmitted on the first link; or,

[0366] a first message carrying the second link identifier is transmitted on the second link; wherein,

[0367] The first link is a non-end-to-end link associated with the first node.

[0368] The second link is an end-to-end multi-hop U2N relay link or a non-end-to-end link not associated with the first node.

[0369] In some embodiments, the first link identification comprises one of:

[0370] a link ID;

[0371] an L2 ID;

[0372] an L2 ID pair.

[0373] In some embodiments, the communication apparatus 130 further comprises:

[0374] a transceiver 1303, configured to establish a third link with a second node and / or a third node respectively; the third link comprises a first link identification;

[0375] the first node has a connected second link with the second node and the third node respectively, and the first link identification is different from a second link identification of the second link.

[0376] In some embodiments, the transceiver 1303 is further configured to interact with the second node and / or the third node for capability information; the capability information is transmitted through the second link.

[0377] receiving a first request message, the first request message carrying a third link identification;

[0378] in response to the first request message, sending a first request acceptance message; the first request acceptance message carries the first link identification, and the first link identification is determined based on the third link identification.

[0379] In some embodiments, the third link identification comprises one or more of:

[0380] a first link identification pair determined through second link coordination;

[0381] a second link identification pair determined based on a preset or a service type;

[0382] a third link identification pair determined based on a second link identification.

[0383] In some embodiments, the capability information comprises one or more of:

[0384] a single-hop U2N relay;

[0385] a single-hop U2U relay;

[0386] a multi-hop U2N relay;

[0387] a multi-hop U2U relay.

[0388] In some embodiments, the second node or the third node is a network device, and the first node is a first relay device; the communication apparatus 130 further includes:

[0389] a transceiver 1303, configured to send one or more of the following to the second node or the third node:

[0390] the first link identifier and the second link identifier;

[0391] an association relationship between a first source node in the first link identifier and a third source node in the second link identifier.

[0392] In some embodiments, the first information is carried in a packet header of a data packet of an adaptation layer, the data packet is carried in a first message, and the first information is associated with the data packet.

[0393] In some embodiments, the first information includes a first device identifier or a second device identifier; the first device identifier is used to confirm that the first node processes a data packet associated with the first device identifier; and the second device identifier is used to confirm an egress of a data packet associated with the second device identifier.

[0394] In some embodiments, the first device identifier is related to a device identifier of the first node;

[0395] the first device identifier is different from device identifiers of other terminals on a multi-hop link, or the first device identifier is different from device identifiers of other terminals on a link of a first relay terminal.

[0396] In some embodiments, the first device identifier includes one or more of the following:

[0397] one device identifier field;

[0398] two device identifier fields.

[0399] In some embodiments, if the first node is a first relay terminal in transmission between the first node and the network device, the one device identifier field is a device identifier of the first relay terminal.

[0400] If the first node is a remote terminal in transmission between the first node and the network device, the one device identifier field is a device identifier of the remote terminal or a second value.

[0401] If the first node is a remote terminal in transmission between the first node and the network device, the two device identifier fields include:

[0402] device identifiers of the two remote terminals; or

[0403] a device identifier of one of the remote terminals and a third value.

[0404] In some embodiments, if the first node is a first relay terminal in the transmission between the first node and the remote terminal, the two device identity fields include: a device identity of the remote terminal and a device identity of the first relay terminal.

[0405] In some embodiments, if the first node is a first relay terminal in the transmission between the first node and the network device, the two device identity fields include: a device identity of the remote terminal and a device identity of the first relay terminal.

[0406] In some embodiments, the first message is transmitted on a second link; the second link is a link for the remote terminal to communicate with the network device.

[0407] In some embodiments, the first device identity is determined by one or more of:

[0408] a first node allocation;

[0409] another terminal allocation;

[0410] a network device allocation.

[0411] In some embodiments, if the first device identity is allocated by the first node, the first device identity is indicated to the other terminals and the network device through a first RRC message, or to the other terminals and the network device through a first multi-hop RRC message; wherein,

[0412] the first multi-hop RRC message is a per-hop RRC message transmitted from the first node to the other terminals and the network device respectively in the multi-hop link.

[0413] In some embodiments, if the first device identity is allocated by one of the other terminals, the first device identity is indicated to the first node, the remaining other terminals and the network device through a second RRC message, or to the first node, the remaining other terminals and the network device through a second multi-hop RRC message;

[0414] the second multi-hop RRC message is a per-hop RRC message transmitted from one of the other terminals to the first node, the remaining other terminals and the network device respectively in the multi-hop link.

[0415] In some embodiments, if the first device identity is allocated by the network device, the first device identity is indicated to the first node and the other terminals through a third RRC message, or to the first node and the other terminals through a third multi-hop RRC message; the first device identity information is allocated by the network device based on sidelink information; the sidelink information is reported by the first node or the other terminals.

[0416] The third multi-hop RRC message is transmitted to each hop RRC message of the first node and the other terminals respectively from the network device in the multi-hop link.

[0417] In some embodiments, the first information includes a first adaptation layer identifier or a second adaptation layer identifier; the first adaptation layer identifier is used to confirm that the first node processes data packets associated with the first adaptation layer identifier; and the second adaptation layer identifier is used to confirm the egress of data packets associated with the second adaptation layer identifier.

[0418] In some embodiments, the first adaptation layer identifier includes one or more of the following:

[0419] A source node identifier and / or a destination node identifier on the second link; the second link is a multi-hop link for the remote terminal to communicate with the network device;

[0420] Node indication information on the second link;

[0421] One or more of the source node identifier and the destination node identifier on the second link, and hop number information.

[0422] In some embodiments, the node indication information on the second link is bitmap information;

[0423] Each bit of the bitmap information corresponds to each hop node on the second link.

[0424] In some embodiments, the source node identifier and / or the destination node identifier are indicated by a first number of bits of the binary of the unique identifier of the node according to the node order on the second link; the number of bits of the first number of bits is related to the number of terminals on the second link; and / or,

[0425] The source node identifier and / or the destination node identifier are indicated by the assigned device identifier.

[0426] In some embodiments, the number of terminals includes one or more of the following:

[0427] A first number of terminals on the second link except the remote terminal;

[0428] A second number of terminals on the second link except the remote terminal and the near-end relay terminal.

[0429] In some embodiments, the first adaptation layer identifier includes a first bearer identifier, and the second adaptation layer identifier includes a second bearer identifier.

[0430] In some embodiments, the first and second bearer identifiers are identifiers of bearers associated with the first node corresponding to different source node pairs; or

[0431] The first and second bearer identifiers are identifiers of bearers associated with the first node corresponding to different destination node pairs.

[0432] In some embodiments, the first or second bearer identifier is assigned by the network device, and the first or second bearer identifier is different from bearer identifiers of other terminals on the multi-hop link.

[0433] In some embodiments, if the source node and the destination node associated with the first bearer identifier are both terminals, the first bearer identifier is assigned to one or more of the following:

[0434] a remote terminal;

[0435] a relay terminal;

[0436] The first bearer identifier is different from bearer identifiers of other terminals assigned by the network device on the multi-hop link.

[0437] In some embodiments, the transceiver 1303 is further configured to report the first bearer identifier to the network device, so that the network device assigns a bearer identifier to other terminals on the multi-hop link, which is different from the first bearer identifier.

[0438] In some embodiments, the first bearer identifier is determined according to the second bearer identifier, the maximum number of bearers, the total number of hops, and the number of hops where the first node is located.

[0439] In some embodiments, the second bearer identifier is one or more of the following:

[0440] an identifier of a signaling bearer;

[0441] an identifier of a data bearer;

[0442] a fourth configured value.

[0443] In some embodiments, the first information includes one or more bearer identifiers; wherein

[0444] The one or more bearer identifiers include a third bearer identifier of an end-to-end and a fourth bearer identifier of a non-end-to-end;

[0445] The bearer identifier corresponds to an RRC connection one by one.

[0446] In some embodiments, the first information comprises a first RLC channel or a second RLC channel; the first RLC channel is used for acknowledging data packets associated with the first RLC channel at the first node; and the second adaptation layer identifies an egress for acknowledging data packets associated with the second RLC channel.

[0447] In some embodiments, the first RLC channel and the second RLC channel are RLC channels associated with bearers used by the first node for different source nodes; or,

[0448] The first RLC channel and the second RLC channel are RLC channels associated with bearers used by the first node for different destination nodes.

[0449] In some embodiments, the first RLC channel or the second RLC channel is assigned by a network device, and the first RLC channel or the second RLC channel is different from RLC channels used by other terminals on a multi-hop link.

[0450] In some embodiments, if the source node and the destination node associated with the first RLC channel or the second RLC channel are both terminals, the first RLC channel or the second RLC channel is assigned to one or more of:

[0451] a terminal acting as a transmitting node in each hop on the multi-hop link;

[0452] a remote terminal;

[0453] a relay terminal.

[0454] In some embodiments, if the first RLC channel or the second RLC channel is assigned to a terminal acting as a transmitting node, the first RLC channel or the second RLC channel is determined based on one or more of:

[0455] a transmitting node or a receiving node of a bearer associated with the first node;

[0456] associated quality of service information.

[0457] In some embodiments, the quality of service information comprises one or more of:

[0458] end-to-end quality of service information;

[0459] quality of service information of a Uu segment in the first path, and / or quality of service information of one or more PC5 segments in the first path.

[0460] In some embodiments, the transceiver 1303 is further configured to report the first RLC channel or the second RLC channel to a network device, so that the network device on the multi-hop link allocates the RLC channel used by the bearers of other terminals to be different from the first RLC channel or the second RLC channel.

[0461] In some embodiments, the transceiver 1303 is further configured to synchronize the first RLC channel or the second RLC channel to other terminals in the multi-hop link; the RLC channels used by the bearers of each terminal in the multi-hop link are different.

[0462] It can be understood that, for an end-to-end link, the first information can be used to determine the egress of the associated data packet, and for a non-end-to-end link, the first information can be used to determine the associated data packet processed by the first node. That is, the first node can use the first information to determine the accurate data routing, so as to solve the problem that the Relay UE cannot identify two different data when receiving the data, and can distinguish different logical links on different physical links, or distinguish different logical links through different UE IDs / Bearer IDs of the SRAP layer through the shared physical link, or distinguish different logical links through the shared physical link but using different RLC channels, accurately identify the data packet or data, and further improve the accuracy of communication.

[0463] Those skilled in the art should understand that the above description of the communication device of the embodiments of the present application can be understood with reference to the description of the communication method of the embodiments of the present application.

[0464] FIG. 14 is a schematic structural diagram of a communication device provided by an embodiment of the present application. The communication device 140 shown in FIG. 14 includes a processor 1401. The processor 1401 can call and run a computer program from a memory to implement the method in the embodiments of the present application.

[0465] Optionally, as shown in FIG. 14, the communication device 140 can further include a memory 1402. The processor 1401 can call and run a computer program from the memory 1402 to implement the method in the embodiments of the present application.

[0466] The memory 1402 can be a separate device independent of the processor 1401, or can be integrated in the processor 1401.

[0467] Optionally, as shown in FIG. 14, the communication device 140 can further include a transceiver 1403, which can be controlled by the processor 1401 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices.

[0468] The transceiver 1403 can include a transmitter and a receiver. The transceiver 1403 can further include one or more antennas.

[0469] The communication device 140 can be specifically a terminal of the embodiments of the present application, and can implement the corresponding processes realized by the terminal in the various methods of the embodiments of the present application. For brevity, details are not repeated here.

[0470] FIG. 15 is a schematic structural diagram of a chip according to an embodiment of the present application. The chip 150 shown in FIG. 15 includes a processor 1501, which can call and run a computer program from a memory to implement the method according to an embodiment of the present application.

[0471] Optionally, as shown in FIG. 15, the chip 150 can further include a memory 1502. The processor 1501 can call and run a computer program from the memory 1502 to implement the method according to an embodiment of the present application.

[0472] The memory 1502 can be a separate device independent of the processor 1501, or can be integrated in the processor 1501.

[0473] Optionally, the chip 150 can further include an input interface 1503. The processor 1501 can control the input interface 1503 to communicate with other devices or chips, specifically, to obtain information or data sent by other devices or chips.

[0474] Optionally, the chip 150 can further include an output interface 1504. The processor 1501 can control the output interface 1504 to communicate with other devices or chips, specifically, to output information or data to other devices or chips.

[0475] The chip can be applied to a terminal according to an embodiment of the present application, and can implement the corresponding processes realized by the terminal in the various methods of the embodiments of the present application. For brevity, details are not repeated here.

[0476] It should be understood that the chip mentioned in the embodiments of the present application can also be referred to as a system chip, a system-on-chip, a chip system or a system-on-chip, etc.

[0477] It should be understood that the processor of the embodiments of the present application can be an integrated circuit chip with a processing capability of signals. In the implementation process, each step of the method embodiments described above can be completed by the integrated logic circuit of hardware in the processor or the instructions in the form of software. The processor described above can be a general processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The disclosed methods, steps and logic block diagrams in the embodiments of the present application can be implemented or executed. The general processor can be a microprocessor or the processor can also be any conventional processor or the like. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as a hardware coding processor for execution, or a combination of hardware and software modules in the coding processor for execution. The software module can be located in a random access memory, a flash memory, a read only memory, a programmable read only memory or an electrically erasable programmable memory, a register or other mature storage medium in the art. The storage medium is located in the storage, and the processor reads the information in the storage, and combines the hardware to complete the steps of the above method.

[0478] It is to be understood that the memory in the embodiments of the present application can be a volatile memory or a nonvolatile memory, or can include both volatile and nonvolatile memory. Among them, the nonvolatile memory can be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or a flash memory. The volatile memory can be a random access memory (Random Access Memory, RAM) used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (Static RAM, SRAM), dynamic random access memory (Dynamic RAM, DRAM), synchronous dynamic random access memory (Synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (Synchlink DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM). It should be noted that the memory of the system and method described herein is intended to include, but not limited to, these and any other suitable types of memory.

[0479] It should be understood that the above-mentioned memory is exemplary but not limiting, for example, the memory in the embodiments of the present application can also be static random access memory (static RAM, SRAM), dynamic random access memory (dynamic RAM, DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synch link DRAM, SLDRAM) and direct memory bus random access memory (Direct Rambus RAM, DR RAM) and the like. That is, the memory in the embodiments of the present application is intended to include, but not limited to, these and any other suitable types of memory.

[0480] The embodiment of the present application further provides a computer readable storage medium for storing a computer program. The computer readable storage medium can be applied to the terminal in the embodiment of the present application, and the computer program causes the computer to execute the corresponding processes realized in the various methods of the embodiment of the present application. For brevity, details are not repeated here.

[0481] The embodiment of the present application further provides a computer program product comprising computer program instructions. The computer program product can be applied to the first node in the embodiment of the present application, and the computer program instructions cause the computer to execute the corresponding processes realized by the first node in the various methods of the embodiment of the present application. For brevity, details are not repeated here.

[0482] The embodiment of the present application further provides a computer program. The computer program can be applied to the terminal in the embodiment of the present application, and when the computer program runs on the computer, causes the computer to execute the corresponding processes realized by the first node in the various methods of the embodiment of the present application. For brevity, details are not repeated here.

[0483] Those skilled in the art can understand that the units and algorithm steps of the examples described in combination with the embodiments disclosed herein can be realized in electronic hardware or a combination of computer software and electronic hardware. Whether the functions are realized in hardware or software depends on the specific application and design constraints of the technical solutions. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0484] Those skilled in the art can clearly understand that, for the convenience and brevity of the description, the specific working processes of the above-described system, device and unit can refer to the corresponding processes in the foregoing method embodiments, and details are not repeated here.

[0485] In several embodiments provided in the present application, it should be understood that the disclosed system, device and method can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of the units is only a logical function division, and actual implementation can have another division manner, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interfaces, devices or units, and can be electrical, mechanical or other forms.

[0486] The units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed on multiple network units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiment scheme.

[0487] In addition, the functional units in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present alone, or two or more units can be integrated in one unit.

[0488] If the functions are realized in the form of software functional units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application or the parts that essentially contribute to the prior art or the parts of the technical solutions can be embodied in the form of software products. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and various program code storage media.

[0489] The above is only a specific embodiment of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in the present application, which should be covered within the protection scope of the present application. Therefore, the protection scope of the present application should be limited by the protection scope of the claims.

Claims

A communication method applied to a first node, the method comprising: obtaining first information, the first information being used to identify a data packet; based on the first information, performing at least one of the following: determining that the first node processes the data packet associated with the first information; determining an egress of the data packet associated with the first information. According to the method of claim 1, wherein, the egress comprises an egress link and / or an egress channel. The method according to claim 1 or 2, wherein The method further comprises: receiving or sending a first message; the first message carrying the first information, the first message being sent by a third node; or the first message being sent to a second node. According to the method of claim 3, wherein, the first node is a first relay terminal; the second node comprises one or more of the following: a remote terminal, a second relay terminal and a network device; the third node comprises one or more of the following: a remote terminal, a third relay terminal and a network device. According to the method of any one of claims 1 to 4, wherein, the first information comprises a first link identifier or a second link identifier; the first link identifier is used to confirm that the first node processes the data packet associated with the first link identifier; and the second link identifier is used to confirm the egress of the data packet associated with the second link identifier; wherein, the first link is a non-end-to-end link associated with the first node; the second link is an end-to-end multi-hop U2N relay link or a non-end-to-end link not associated with the first node. The method according to any one of claims 1 to 5, wherein The method further comprises: determining the second node and / or the third node; establishing a first link with the second node and / or the third node, respectively; the first link comprising a first link identifier; the first node has a connected second link with the second node and the third node, respectively; the first link identifier and a second link identifier of the second link are different. According to the method of claim 6, wherein, a first message carrying the first link identifier is transmitted on the first link; or, a first message carrying the second link identifier is transmitted on the second link; wherein, the first link is a non-end-to-end link associated with the first node; the second link is an end-to-end multi-hop U2N relay link or a non-end-to-end link not associated with the first node. According to the method of claim 6 or 7, wherein, the first link identifier comprises one of the following: a link ID; an L2 ID; an L2 ID pair. The method according to any one of claims 1 to 5, wherein The method further comprises: establishing a third link with the second node and / or the third node, respectively; the third link comprising a first link identifier; the first node has a connected second link with the second node and the third node, respectively; the first link identifier and a second link identifier of the second link are different. The method of claim 9, wherein, The method further comprises: interacting with the second node and / or the third node to obtain capability information; the capability information is transmitted through the second link; receiving a first request message, the first request message carrying a third link identifier; sending a first request acceptance message in response to the first request message, wherein the first request acceptance message carries the first link identifier, and the first link identifier is determined based on the third link identifier. The method of claim 10, wherein, The third link identifier comprises one or more of: a first link identifier pair determined by the second link coordination; a second link identifier pair preset or determined based on a service type; a third link identifier pair determined based on the second link identifier. The method according to claim 10 or 11, wherein The capability information comprises one or more of: single-hop U2N relay; single-hop U2U relay; multi-hop U2N relay; multi-hop U2U relay. The method of claim 5, wherein, The second node or the third node is a network device, and the first node is a first relay device; the method further comprises: sending one or more of the following to the second node or the third node: the first link identifier and the second link identifier; an association relationship between a first source node in the first link identifier and a third source node in the second link identifier. The method of any one of claims 1-4, wherein, The first information is carried in a packet header of a data packet of an adaptation layer, the data packet is carried in the first message, and the first information is associated with the data packet. The method of any one of claims 1-4 and 14, wherein, The first information comprises a first device identifier or a second device identifier; the first device identifier is used to confirm a data packet associated with the first device identifier processed at the first node; and the second device identifier is used to confirm an egress of a data packet associated with the second device identifier. The method of claim 14 or 15, wherein, The first device identifier is related to a device identifier of the first node; The first device identifier is different from device identifiers of other terminals on a multi-hop link; or the first device identifier is different from device identifiers of other terminals on a link of a first relay terminal. The method of any one of claims 14-16, wherein, The first device identifier comprises one or more of: one device identifier field; two device identifier fields. The method of claim 17, wherein, If the first node is a first relay terminal in transmission between the first node and the network device, the one device identifier field is a device identifier of the first relay terminal; If the first node is a remote terminal in transmission between the first node and the network device, the one device identifier field is a device identifier of the remote terminal or a second value; If the first node is a remote terminal in transmission between the first node and the network device, the two device identifier fields comprise: device identifiers of two remote terminals; or, a device identifier of one remote terminal and a third value. The method of claim 17, wherein, If the first node is a first relay terminal in transmission between the first node and the remote terminal, the two device identifier fields comprise: a device identifier of the remote terminal and a device identifier of the first relay terminal. The method of claim 17, wherein, If the first node is a first relay terminal in the transmission between the first node and the network device, the two device identifier fields include: a device identifier of the remote terminal and a device identifier of the first relay terminal. The method according to any one of claims 14 to 20, wherein, The first message is transmitted on a second link; the second link is a link for the remote terminal to communicate with the network device. The method according to any one of claims 14 to 21, wherein, The first device identifier is determined by one or more of: First node allocation; Other terminal allocation; Network device allocation. The method according to claim 22, wherein, If the first device identifier is allocated by the first node, the first device identifier is indicated to the other terminals and the network device by a first RRC message, or to the other terminals and the network device by a first multi-hop RRC message; wherein, The first multi-hop RRC message is a per-hop RRC message transmitted from the first node to the other terminals and the network device respectively in the multi-hop link. The method according to claim 22, wherein, If the first device identifier is allocated by one of the other terminals, the first device identifier is indicated to the first node, the remaining other terminals and the network device by a second RRC message, or to the first node, the remaining other terminals and the network device by a second multi-hop RRC message; The second multi-hop RRC message is a per-hop RRC message transmitted from the one of the other terminals to the first node, the remaining other terminals and the network device respectively in the multi-hop link. The method according to claim 22, wherein, If the first device identifier is allocated by the network device, the first device identifier is indicated to the first node and the other terminals by a third RRC message, or to the first node and the other terminals by a third multi-hop RRC message; the first device identifier information is allocated by the network device based on sidelink information; the sidelink information is reported by the first node or the other terminals; The third multi-hop RRC message is a per-hop RRC message transmitted from the network device to the first node and the other terminals respectively in the multi-hop link. The method according to any one of claims 1 to 4, 14, wherein, The first information includes a first adaptation layer identifier or a second adaptation layer identifier; the first adaptation layer identifier is used to confirm that the first node processes a data packet associated with the first adaptation layer identifier; and the second adaptation layer identifier is used to confirm an egress of a data packet associated with the second adaptation layer identifier. The method according to claim 26, wherein, The first adaptation layer identifier includes one or more of: A source node identifier and / or a destination node identifier on a second link; the second link is a multi-hop link for the remote terminal to communicate with the network device; Node indication information on the second link; One or more of the source node identifier and the destination node identifier on the second link, and hop count information. The method according to claim 27, wherein, The node indication information on the second link is bitmap information. Each bit of the bitmap information corresponds to each hop node on the second link. The method of claim 27, wherein, The source node identifier and / or the destination node identifier is indicated by a first number of bits of a unique identifier of a node according to an order of nodes on the second link; the number of bits of the first number of bits is related to a number of terminals on the second link; and / or, The source node identifier and / or the destination node identifier is indicated by an assigned device identifier. The method of claim 29, wherein, The number of terminals comprises one or more of: A first number of terminals on the second link excluding the far-end terminal; A second number of terminals on the second link excluding the far-end terminal and the near-end relay terminal. The method of claim 26, wherein, The first adaptation layer identifier comprises a first bearer identifier, and the second adaptation layer identifier comprises a second bearer identifier. The method of claim 31, wherein, The first bearer identifier and the second bearer identifier are identifiers of bearers associated with the first node corresponding to different source nodes; or, The first bearer identifier and the second bearer identifier are identifiers of bearers associated with the first node corresponding to different destination nodes. The method of claim 31 or 32, wherein, The first bearer identifier or the second bearer identifier is assigned by a network device, and the first bearer identifier, the second bearer identifier, and bearer identifiers of other terminals on the multi-hop link are all different. The method of claim 31 or 32, wherein, If the source node and the destination node associated with the first bearer identifier are both terminals, the first bearer identifier is assigned according to one or more of: The far-end terminal; The relay terminal; The first bearer identifier is different from bearer identifiers of other terminals on the multi-hop link assigned by the network device. The method of claim 34, wherein, The method further comprises: Reporting the first bearer identifier to the network device, so that the first bearer identifier is different from bearer identifiers of other terminals on the multi-hop link assigned by the network device. The method of any one of claims 31 to 35, wherein, The first bearer identifier is determined according to the second bearer identifier, a maximum number of bearers, a total number of hops, and a hop number at which the first node is located. The method of claim 36, wherein, The second bearer identifier comprises one or more of: An identifier of a signaling bearer; An identifier of a data bearer; A fourth value configured. The method of any one of claims 1 to 4, 14, wherein, The first information comprises one or more bearer identifiers; wherein, The one or more bearer identifiers comprise a third bearer identifier of an end-to-end bearer and a fourth bearer identifier of a non-end-to-end bearer; The bearer identifiers correspond to RRC connections one by one. The method of claim 1 or 3, wherein, The first information comprises a first RLC channel or a second RLC channel; the first RLC channel is used to confirm processing of a data packet associated with the first RLC channel at the first node; and the second adaptation layer identifier is used to confirm an exit of a data packet associated with the second RLC channel. The method of claim 39, wherein, The first RLC channel and the second RLC channel are RLC channels used by bearers associated with the first node corresponding to different source nodes; or The first RLC channel and the second RLC channel are RLC channels used by bearers associated with the first node corresponding to different destination nodes. The method of claim 39 or 40, wherein The first RLC channel or the second RLC channel is assigned by the network device, and the first RLC channel or the second RLC channel is different from RLC channels used by bearers of other terminals on the multi-hop link. The method of claim 39 or 40, wherein If the source node and the destination node associated with the first RLC channel or the second RLC channel are both terminals, the first RLC channel or the second RLC channel is assigned to one or more of the following: a terminal acting as a sending node in each hop on the multi-hop link; a remote terminal; a relay terminal. The method of claim 42, wherein If the first RLC channel or the second RLC channel is assigned to a terminal acting as a sending node, the first RLC channel or the second RLC channel is determined based on one or more of the following: a sending node or a receiving node of a bearer associated with the first node; associated quality of service information. The method of claim 43, wherein, The quality of service information includes one or more of the following: end-to-end quality of service information; quality of service information of a Uu segment in the first path, and / or quality of service information of one or more PC5 segments in the first path. The method of claim 42, wherein, The method further comprises: reporting the first RLC channel or the second RLC channel to the network device, so that the network device on the multi-hop link assigns RLC channels used by bearers of other terminals to be different from the first RLC channel or the second RLC channel. The method of any one of claims 42 to 45, wherein, The method further comprises: synchronizing the first RLC channel or the second RLC channel to other terminals in the multi-hop link; and RLC channels used by bearers between each terminal in the multi-hop link are different. A communication device applied to a first node, the communication device comprising: an obtaining unit configured to obtain first information, the first information being used to identify a data packet; based on the first information, performing at least one of the following: determining to process the data packet associated with the first information at the first node; determining an egress of the data packet associated with the first information. A terminal comprising: a processor and a memory, the memory being configured to store a computer program, and the processor being configured to invoke and run the computer program stored in the memory to perform the method of any one of claims 1 to 46. A chip comprising: a processor configured to invoke and run a computer program from a memory, so that a device installed with the chip performs the method of any one of claims 1 to 46. A computer readable storage medium configured to store a computer program, the computer program causing a computer to perform the method of any one of claims 1 to 46. A computer program product comprising computer program instructions, the computer program instructions causing a computer to perform the method of any one of claims 1 to 46. A computer program causing a computer to perform the method of any one of claims 1 to 46.

Images