WO2023065109A1 - 信息发送方法、信息接收方法、装置和系统 - Google Patents

信息发送方法、信息接收方法、装置和系统 Download PDF

Info

Publication number
WO2023065109A1
WO2023065109A1 PCT/CN2021/124652 CN2021124652W WO2023065109A1 WO 2023065109 A1 WO2023065109 A1 WO 2023065109A1 CN 2021124652 W CN2021124652 W CN 2021124652W WO 2023065109 A1 WO2023065109 A1 WO 2023065109A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
rrc
identification information
identifier
message
Prior art date
Application number
PCT/CN2021/124652
Other languages
English (en)
French (fr)
Inventor
李国荣
张磊
王昕�
Original Assignee
富士通株式会社
李国荣
张磊
王昕�
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 富士通株式会社, 李国荣, 张磊, 王昕� filed Critical 富士通株式会社
Priority to PCT/CN2021/124652 priority Critical patent/WO2023065109A1/zh
Publication of WO2023065109A1 publication Critical patent/WO2023065109A1/zh

Links

Images

Definitions

  • This application relates to the field of communication.
  • the terminal equipment is connected to the network part through the Uu interface, and the terminal equipment communicates with other terminal equipment through the PC5 interface.
  • the side link relay (SL relay) has been studied in R17, as shown in Figure 1
  • the schematic diagram of the side link relay scenario is shown.
  • scenario 1 the remote terminal equipment (remote UE) is not within the coverage of the base station or cell, and the relay terminal equipment (relay UE) is within the coverage of the base station or cell.
  • Scenario 2 In Scenario 3, both the remote terminal device and the relay terminal device are within the coverage of a base station or a cell.
  • the remote terminal device and the relay terminal device are within the coverage of different base stations or cells.
  • NR New Radio
  • Uu is used on the Uu link of the relay UE
  • the NR side link is used on the PC5 between the relay UE and the remote UE.
  • an adaptation layer (adaptation layer) is introduced in the protocol stack of the R17SL relay (relay), and the identification related to the remote terminal device and its Uu can be added to the header of the adaptation layer (header)
  • the identification of the radio bearer so that the serving base station of the relay terminal equipment can identify the remote terminal equipment, but currently there is no method for how to allocate the identification related to the remote terminal equipment.
  • embodiments of the present application provide an information sending method, an information receiving method, an apparatus, and a system.
  • an information receiving device configured in a first terminal device, wherein the device includes:
  • a processing unit which establishes a connection with at least one second terminal device
  • a first sending unit which sends first identification information to a network device, where the first identification information is used to indicate a first identification related to the at least one second terminal device;
  • a first receiving unit configured to receive second identification information sent by the network device, where the second identification information is used to indicate a second identification of the at least one second terminal device.
  • an information sending device configured in a network device, wherein the device includes:
  • a third receiving unit which receives first identification information sent by the first terminal device, where the first identification information is used to indicate the at least one first identification related to the second terminal device connected to the first terminal device;
  • a third sending unit configured to send second identification information to the first terminal device, where the second identification information is used to indicate a second identification of at least one second terminal device.
  • a communication system including the network device described in the foregoing aspect and/or the first terminal device described in the foregoing aspect.
  • the identity of the second terminal device can be configured by the serving network device of the first terminal device, so that the first terminal device forwards the data of the second terminal device (such as RRC messages and user plane data) etc.), this identifier can be used to help the RRC message and user plane data of the second terminal device be correctly identified by the network device.
  • Figure 1 is a schematic diagram of remote UE and relay UE application scenarios
  • 2 to 4 are schematic diagrams of protocol stacks in a terminal device-network device relay scenario
  • FIG. 5 is a schematic diagram of establishing a connection for uplink and downlink transmission in a terminal device-network device relay scenario
  • FIG. 6 is a schematic diagram of an information sending method according to an embodiment of the present application.
  • FIG. 7 is a schematic diagram of an information receiving method according to an embodiment of the present application.
  • FIGS. 8 to 11 are schematic diagrams of uplink and downlink transmission methods in a terminal device-network device relay scenario according to an embodiment of the present application.
  • FIG. 12 is a schematic diagram of an information sending method according to an embodiment of the present application.
  • FIG. 13 is a schematic diagram of an information receiving method according to an embodiment of the present application.
  • FIG. 14 is a schematic diagram of a method for sending and receiving information according to an embodiment of the present application.
  • FIG. 15 is a schematic diagram of a method for sending and receiving information according to an embodiment of the present application.
  • FIG. 16 is a schematic diagram of an information sending method according to an embodiment of the present application.
  • 17 to 18 are schematic diagrams of handover methods in a terminal device-network device relay scenario according to an embodiment of the present application.
  • FIG. 19 is a schematic diagram of an information sending method according to an embodiment of the present application.
  • FIG. 20 is a schematic diagram of an information receiving method according to an embodiment of the present application.
  • FIG. 21 is a schematic diagram of a method for sending and receiving information according to an embodiment of the present application.
  • FIG. 22 is a schematic diagram of an information receiving device according to an embodiment of the present application.
  • Fig. 23 is a schematic diagram of an information receiving device according to an embodiment of the present application.
  • FIG. 24 is a schematic diagram of an information sending device according to an embodiment of the present application.
  • FIG. 25 is a schematic diagram of an information sending and receiving device according to an embodiment of the present application.
  • Fig. 26 is a schematic diagram of an information sending and receiving device according to an embodiment of the present application.
  • FIG. 27 is a schematic diagram of an information sending device according to an embodiment of the present application.
  • Fig. 28 is a schematic diagram of an information sending device according to an embodiment of the present application.
  • Fig. 29 is a schematic diagram of an information receiving device according to an embodiment of the present application.
  • FIG. 30 is a schematic diagram of a communication system according to an embodiment of the present application.
  • FIG. 31 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • Fig. 32 is a schematic diagram of a network device according to an embodiment of the present application.
  • the terms “first”, “second”, etc. are used to distinguish different elements from the title, but do not indicate the spatial arrangement or time order of these elements, and these elements should not be referred to by these terms restricted.
  • the term “and/or” includes any and all combinations of one or more of the associated listed items.
  • the terms “comprising”, “including”, “having” and the like refer to the presence of stated features, elements, elements or components, but do not exclude the presence or addition of one or more other features, elements, elements or components.
  • the term “communication network” or “wireless communication network” may refer to a network conforming to any of the following communication standards, such as New Radio (NR, New Radio), Long Term Evolution (LTE, Long Term Evolution), Enhanced Long-term evolution (LTE-A, LTE-Advanced), wideband code division multiple access (WCDMA, Wideband Code Division Multiple Access), high-speed packet access (HSPA, High-Speed Packet Access), etc.
  • NR New Radio
  • New Radio Long Term Evolution
  • LTE-A Long-term evolution
  • LTE-A Long-term evolution
  • WCDMA Wideband Code Division Multiple Access
  • HSPA High-Speed Packet Access
  • the communication between devices in the communication system can be carried out according to any stage of communication protocol, for example, it can include but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and future 5G, 6G, etc., and/or other communication protocols that are currently known or will be developed in the future.
  • 1G generation
  • 2G 2.5G
  • 2.75G 3G
  • 4G 4G
  • 4.5G future 5G, 6G, etc.
  • future 5G, 6G, etc. and/or other communication protocols that are currently known or will be developed in the future.
  • Network device refers to, for example, a device in a communication system that connects a terminal device to a communication network and provides services for the terminal device.
  • Network equipment may include but not limited to the following equipment: base station (BS, Base Station), access point (AP, Access Point), transmission and reception point (TRP, Transmission Reception Point), broadcast transmitter, mobile management entity (MME, Mobile Management Entity), gateway, server, radio network controller (RNC, Radio Network Controller), base station controller (BSC, Base Station Controller) and so on.
  • the base station may include but not limited to: Node B (NodeB or NB), evolved Node B (eNodeB or eNB), and 5G base station (gNB), etc., and may also include Remote Radio Head (RRH, Remote Radio Head) , Remote Radio Unit (RRU, Remote Radio Unit), relay (relay) or low-power node (such as femto, pico, etc.).
  • NodeB Node B
  • eNodeB or eNB evolved Node B
  • gNB 5G base station
  • RRH Remote Radio Head
  • RRU Remote Radio Unit
  • relay relay
  • low-power node such as femto, pico, etc.
  • base station may include some or all of their functions, each base station may provide communication coverage for a particular geographic area.
  • the term "cell” can refer to a base station and/or its coverage area depending on the context in which the term is used.
  • the term "User Equipment” refers to, for example, a device that accesses a communication network through a network device and receives network services, and may also be called “Terminal Equipment” (TE, Terminal Equipment).
  • a terminal device may be fixed or mobile, and may also be referred to as a mobile station (MS, Mobile Station), terminal, user, subscriber station (SS, Subscriber Station), access terminal (AT, Access Terminal), station, etc. wait.
  • the terminal equipment may include but not limited to the following equipment: Cellular Phone (Cellular Phone), Personal Digital Assistant (PDA, Personal Digital Assistant), wireless modem, wireless communication equipment, handheld equipment, machine-type communication equipment, laptop computer, Cordless phones, smartphones, smart watches, digital cameras, and more.
  • Cellular Phone Cellular Phone
  • PDA Personal Digital Assistant
  • wireless modem wireless communication equipment
  • handheld equipment machine-type communication equipment
  • laptop computer Cordless phones
  • Cordless phones smartphones, smart watches, digital cameras, and more.
  • the terminal device can also be a machine or device for monitoring or measurement, such as but not limited to: a machine type communication (MTC, Machine Type Communication) terminal, Vehicle communication terminal, device to device (D2D, Device to Device) terminal, machine to machine (M2M, Machine to Machine) terminal, etc.
  • MTC Machine Type Communication
  • Vehicle communication terminal device to device (D2D, Device to Device) terminal
  • M2M Machine to Machine
  • Relay UE means a relay-capable terminal device (UE-to-Network Relay UE) that can directly communicate with a network device
  • Remote UE means a terminal device that needs to be relayed through a Relay UE to communicate with a network device Terminal Equipment.
  • the signaling radio bearers SRB include SRB0, SRB1, SRB2 and so on.
  • a signaling radio bearer is a radio bearer used to transmit RRC and NAS messages.
  • SRB0 transmits RRC messages using the common control channel (common control channel, CCCH) logical channel (such as RRC setup request RRC setup request or RRC setup RRC setup or RRC rejection RRC reject or RRC re-establishment request RRC re-establishment Request or RRC recovery request RRC resume request).
  • SRB1 transmits RRC messages (possibly including piggybacked NAS messages) and NAS messages before SRB2 is established, using a dedicated control channel (dedicated control channel, DCCH) logical channel.
  • SRB2 transmits the NAS message and the RRC message including the log measurement message, using the DCCH logical channel.
  • SRB2 has a lower priority than SRB1 and can be configured by the network after access stratum (AS) security activation.
  • AS access stratum
  • Figure 2 and Figure 3 are schematic diagrams of the control plane protocol stack in the Layer-2 (Layer-2) terminal equipment-network equipment relay (UE-to-Network Relay) scenario
  • Figure 4 is a Layer-2 terminal equipment-network equipment relay scenario Schematic diagram of the user plane protocol stack.
  • the PC5 interface can support the adaptation layer (such as ADAPT in the figure), which is only used for bearer mapping.
  • the adaptation layer such as ADAPT in the figure
  • the identity of the remote UE and the identity information of its Uu radio bearer are included in the header of the adaptation layer.
  • the adaptation layer does not appear on the PC5 interface (applicable).
  • the adaptation layer appears (applicable).
  • the protocol stack of the Relay UE and Remote UE on the PC5 interface includes the physical layer PHY, the medium access control MAC layer above the PHY layer (providing packet filtering, logical channel priority processing, scheduling request, data multiplexing and demultiplexing, logic channel and transport channel mapping, etc.), the radio link layer control protocol RLC layer above the MAC layer, and the radio resource control layer PC5-RRC layer above the RLC layer (RRC signaling interaction on the PC5 interface), wherein, the PHY provides services for the MAC layer in the form of transport channels, and the MAC layer provides services for the RLC layer in the form of logical channels.
  • the Relay UE also communicates with the gNB through the NR Uu interface protocol stack, and the Non-Access Stratum (NAS) of the Remote UE is equivalent to the NAS layer in the core network.
  • NAS Non-Access Stratum
  • Figure 5 is a schematic diagram of establishing a connection for uplink and downlink transmission in a terminal device-network device relay scenario.
  • an RRC connection is established with the network device through the relay UE, and then you can For uplink and downlink transmission, at present, the first RRC message sent by the remote UE (such as RRC setup request or RRC re-establishment request or RRC re-establishment request or RRC resume request) is carried on SRB0, and SRB0 is carried on Uu
  • An adaptation layer will be used on the interface, and an identifier related to the remote terminal device can be added to the header of the adaptation layer so that the serving base station of the relay terminal device can identify the remote terminal device.
  • a method of identification related to the remote terminal equipment is a method of identification related to the remote terminal equipment.
  • the identification related to the remote terminal device in the header of the adaptation layer , so that the serving base station of the relay terminal device (the base station for initial access or the target base station after handover) can identify the remote terminal device, the following describes how to allocate The identification related to the remote terminal equipment, how to allocate the identification related to the remote terminal equipment during the handover process is described in conjunction with the embodiments of the third aspect to the fifth aspect.
  • An embodiment of the present application provides a method for sending information, which is applied to a first terminal device, where the first terminal device may be a Relay UE, and the second terminal device may be a Remote UE.
  • Figure 6 is a schematic diagram of the information sending method, as shown in Figure 6, the method includes:
  • the first terminal device establishes a connection with at least one second terminal device
  • the first terminal device sends first identification information to a network device, where the first identification information is used to indicate a first identification related to the at least one second terminal device.
  • establishing a connection between the first terminal device and at least one second terminal device may include that the second terminal device performs relay discovery, relay selection or relay reselection, or the connection between the first terminal device and the second terminal device.
  • the process of establishing a unicast link (unicast link) between PC5 connections or sidelink (sidelink, SL) connections, such as PC5-RRC connections or PC5-AS (Access Stratum, access layer) connections or PC5 single A broadcast link (PC5 unicast link) regarding the relay discovery process, relay selection or relay reselection process, and unicast link establishment process, reference may be made to the prior art, which will not be repeated here.
  • the first terminal device may establish a connection with one or more second terminal devices, and during the process of establishing a connection with each second terminal device, the first terminal device may acquire the Related first identification
  • the first identification can be the destination identification (destination ID) of the second terminal equipment, such as layer 2 identification (layer-2 ID, L2 ID), or in order to save overhead, the first identification can also be It is a first index shorter than the length of the destination identifier, and the first identifier indicates the identifier of the second terminal device communicating in the PC5 interface (communicating with the first terminal device), and is used to explicitly indicate the second terminal device.
  • the first identifier may also be an identifier (PC5 unicast link ID) of a PC5 unicast link between the first terminal device and the second terminal device, for example, the first terminal device and a second terminal device One or more than one PC5 unicast link can be established between each other.
  • PC5 unicast link ID PC5 unicast link ID
  • a PC5 unicast link ID uniquely identifies a PC5 unicast link, corresponding to the destination identifier or the first index of the second terminal device, that is, implicitly indicating the second (the destination identifier or the first index of the terminal device); and/or, the first identifier can also be the identifier (PC5-RRC connection ID) of the PC5-RRC connection between the first terminal device and the second terminal device,
  • PC5-RRC connection ID the identifier (PC5-RRC connection ID) of the PC5-RRC connection between the first terminal device and the second terminal device.
  • one or more PC5 RRC connections can be established between a first terminal device and a second terminal device, and a PC5-RRC connection ID uniquely identifies a PC5-RRC connection, corresponding to the destination identifier or
  • the first index that is, implicitly indicates (the destination identifier or the first index) of the second terminal device; and/or, the first identifier may be the source identifier and the destination
  • the first identifier may be carried by a side link signaling message or a side link RRC message between the first terminal device and the second terminal device; for example, the side link signaling message may be a discovery message or a direct communication request message (direct communication request) or a direct communication accept message (direct communication accept), the side link RRC message may be an RRC reconfiguration side link message (RRCReconfigurationSidelink) message or an RRC reconfiguration complete side link message
  • the (RRCReconfigurationCompleteSidelink) message, etc. are not described here one by one.
  • the first index is used instead of the transmission of the destination indication, the first terminal device or the second terminal device also needs to pre-allocate the first index.
  • the first index is used instead of the transmission of the destination indication, the first terminal device or the second terminal device also needs to pre-allocate the first index.
  • the allocation of the first index please refer to the sixth aspect The embodiment will not be repeated here.
  • the first identification information is used to indicate a first identification related to a second terminal device that establishes a connection with the first terminal device, and the second terminal device newly establishes a connection with the first terminal device terminal device, or the first identification information is used to indicate first identifications related to all second terminal devices that establish connections with the first terminal device.
  • the bearing manner and format of the first identification information will be described in detail in (1) and (2) below.
  • the method may also include:
  • the first terminal device receives second identification information sent by the network device, where the second identification information is used to indicate a second identification of the at least one second terminal device.
  • the network device may assign a second identification according to the first identification information, and generate second identification information, which will be the at least one second terminal device (first identification).
  • first identification The second identifier assigned by the information identifier is notified to the first terminal device, the second identifier is the local/temporary identifier of the second terminal device, and the local/temporary identifier may be included in the header of the Uu interface adaptation layer ( header).
  • header The carrying manner and format of the second identification information will be described in detail in (1) and (2) below.
  • the local/temporary identity represents the identity of the second terminal device communicating in the Uu interface, including at least one of the following:
  • the second index of the second terminal device is used to uniquely identify the second terminal device that has a connection relationship with the first terminal device; that is, the second index is connected to the first terminal device It is unique within the second terminal device that has a connection (such as PC5-RRC connection).
  • a connection such as PC5-RRC connection.
  • n bits n is greater than or equal to 3 and less than or equal to 8, or it can also be represented by an integer (for example, any integer from 0 to 16), etc.
  • a part of the destination identifier of the second terminal device is represented by 24bit, and the second identifier can be a part of the 24bit bits, such as high X bit or low X bit, etc., and X can be is an integer ranging from 2 to 5, etc., which is not limited in this embodiment.
  • the network device in order for the first terminal device to determine the correspondence between the first identifier and the second identifier, that is, for the first terminal device to know which second terminal device (first identification), the network device may explicitly or implicitly indicate the corresponding relationship, for example, the network device indicates the first identification corresponding to at least one second identification (explicit indication) while sending the second identification information; or, in The arrangement order of the second identification in the second identification information is the same as the appearance order of the first identification related to the at least one second terminal device in the first identification information (implicit indication), and the appearance order of the first identification Include the order of appearance in the same message, or the order of appearance in different messages.
  • the first identification information when there are multiple second terminal devices connected to the first terminal device, the first identification information includes first identifications related to the multiple second terminal devices, and the order of appearance of the second identifications is the same as that of the second terminal device.
  • the order of appearance of the identifiers is one-to-one, or, the first identifier information includes a first identifier related to the second terminal device, but the first terminal device sends more than one uplink message, and each uplink message carries a first
  • the order of appearance of the second identification corresponds to the order in which the plurality of uplink messages are received, that is, one-to-one correspondence with the order of appearance of the first identification in each uplink message, or the first identification information includes a
  • the network device allocates a second identifier each time it receives a first identifier, and the first terminal device sends the next first identifier information after receiving a second identifier.
  • the configuration of the second identification will be further described in (1) or (2) below
  • the method may also include: (not shown)
  • the first terminal device uses or stores or retains the correspondence between the first identifier and the second identifier.
  • the first terminal device can determine which second terminal device (first identifier) the second identifier assigned by the network device corresponds to according to the correspondence indicated by the above-mentioned network device in an explicit or implicit manner.
  • the device may use or store or retain the corresponding relationship between the first identification and the second identification, for example, for subsequent relay transmission of uplink and/or downlink data of the second terminal device.
  • the first terminal device may be in an RRC connected (RRC_CONNECTED) mode, or may also be in an RRC idle mode (RRC_IDLE) or an RRC inactive (RRC_INACTIVE) mode, which will be described respectively below.
  • RRC_CONNECTED RRC connected
  • RRC_IDLE RRC idle mode
  • RRC_INACTIVE RRC inactive
  • the first terminal device is in RRC connection mode
  • the first terminal device since the first terminal device is in the RRC connection mode, the first terminal device may directly send an uplink message to the network device, and in 602, the uplink message may be used to carry the first identification information, for example , the uplink message may be a sidelink UE information (sidelink UE information, SUI) message, and the SUI is used as an example for description below, but this application is not limited by this.
  • the uplink message may be a sidelink UE information (sidelink UE information, SUI) message, and the SUI is used as an example for description below, but this application is not limited by this.
  • SUI sidelink UE information
  • the first terminal device when the first trigger condition is met, sends the first identification information to the network device (or in other words, when the first trigger condition is met, the first terminal device sends the SUI to the network device ), the first trigger condition includes at least one of the following conditions: the first terminal device establishes a connection with the second terminal device; a side link capability message is transmitted between the first terminal device and the second terminal device; the The first terminal device receives the first RRC message sent by the second terminal device and directed to the second terminal device.
  • the sending of the SUI message may be triggered.
  • the first terminal device when the first terminal device establishes a connection with the second terminal device and/or the When a side link capability message is transmitted between the first terminal device and the second terminal device and/or when the first terminal device receives the first RRC message sent by the second terminal device for the second terminal device, it may also trigger Sending of SUI messages.
  • the sending of the SUI message can be triggered;
  • the sending of the SUI message is triggered, wherein the first terminal device may notify the first terminal device
  • the second terminal device may notify the first terminal device of the side link capability and/or relay capability of the first terminal device, and/or serve as the second terminal device.
  • this application is not limited by it;
  • the first terminal device receives the first RRC message sent by the second terminal device for the second terminal device, triggering the sending of the SUI message, and the first RRC message may be the first RRC message sent by the second terminal device after the connection is established.
  • the first RRC message sent by the device to the first terminal device is either an RRC message sent using a specific SRB (for example, SRB0) or an RRC message sent using a specific layer 2 configuration (for example, using a layer 2 configuration corresponding to SRB0).
  • the first RRC message of the second terminal device means that the RRC message is generated by the RRC of the second terminal device (for uplink), or is received or parsed or processed by the RRC of the second terminal device (for downlink), for example, the first An RRC message includes RRC setup request or RRC re-establishment request or RRC resume request message, etc., and this application is not limited by this.
  • the first terminal device may send the SUI to the network device, which includes the first identification information, for example: the SUI may be expressed in the abstract syntax notation ASN.1 data format as:
  • the first identification information sl-RemoteUEList-r16 includes first identifications (for example, sl-DestinationIdentity-r16 ), the arrangement (appearance) order of the first identifiers may be arranged according to the time order of establishing a connection with the first terminal device, but this embodiment of the present application is not limited thereto.
  • the SUI can also use the abstract syntax notation ASN.1 data format expressed as:
  • the first identification information SL-TxResourceReq-r16 includes all the second terminal devices currently establishing connections or newly establishing connections (for example, sl-RemoteUE is used to indicate whether a destination ID corresponds to a remote terminal device, That is, the first identity (for example, sl-DestinationIdentity-r16) related to the second terminal device).
  • the second identification information may be carried by a fourth RRC message for the first terminal device, and the fourth RRC message for the first terminal device refers to the RRC message sent by the first terminal device Receiving or parsing or processing, for example, the fourth RRC message includes RRC reconfiguration or RRC re-establishment or RRC resume message, etc.
  • the fourth RRC message may include second identification information, and the arrangement order of the second identification in the second identification information is related to the at least one second terminal device in the first identification information
  • the order of appearance of the first identifiers is the same, and the order of appearance of the first identifiers includes the order of appearance in the same SUI, or the order of appearance in different SUI messages.
  • the first identification information when there are more than one second terminal devices connected to the first terminal device, the first identification information includes first identifications related to the more than one second terminal equipment, and the order of appearance of the second identifications is the same as The order of appearance of the first identifiers is one-to-one, or, the first identifier information includes a first identifier related to the second terminal device, but the first terminal device sends more than one SUI message, and each SUI message carries
  • the order of appearance of the second identification corresponds to the order of receiving the more than one SUI messages, that is, corresponds to the order of appearance of the first identification in each SUI message one-to-one. Therefore, the correspondence between the second identifier and the first identifier is indicated in this implicit manner.
  • the fourth RRC message may also indicate the second identity and the first identity corresponding to the second identity at the same time, thereby indicating the correspondence between the second identity and the first identity in this explicit manner relation.
  • the first terminal device may add the second identifier to the header of the adaptation layer.
  • the information exchange process between the terminal device and the network device will be described in the embodiment of the second aspect.
  • the first terminal device is in RRC idle or inactive mode
  • the method in (1) when the first terminal device is in the RRC idle or inactive mode, after entering the RRC connected mode, the method in (1) can be used to send the first identification information and receive the second identification information, for example, the The method may further include: the first terminal device receives the first RRC message directed at the second terminal device sent by the second terminal device, and enters the RRC connection mode, and after entering the RRC connection mode, the first terminal device can use (1)
  • the first terminal device receives the first RRC message directed at the second terminal device sent by the second terminal device, and enters the RRC connection mode, and after entering the RRC connection mode, the first terminal device can use (1)
  • the implementation manner of the first RRC message please refer to (1), which will not be repeated here.
  • the first terminal device when the first terminal device is in the RRC idle or inactive mode, it can execute an RRC connection establishment process or an RRC resume (RRC resume) process, and send a message during the RRC connection establishment or RRC resume process.
  • RRC resume RRC resume
  • the second RRC message for the first terminal device may be used to carry the first identification information
  • the second RRC message for the first terminal device means that the RRC message is sent by the first terminal device RRC generation (for uplink), or received or parsed or processed by the RRC of the first terminal device (for downlink), the second RRC message may be the first terminal device's own RRC connection establishment process or RRC restart process
  • the RRC message sent to the network device in the message includes RRC setup request or RRC setup complete or RRC resume request or RRC resume complete, etc.
  • the second identification information may be carried by a third RRC message for the first terminal device, where the third RRC message for the first terminal device refers to being received or processed by the RRC of the first terminal device,
  • the third RRC message includes an RRC setup or RRC resume or RRC reconfiguration message, etc.
  • the third RRC message may include second identification information, and the arrangement order of the second identification in the second identification information is related to the at least one second terminal device in the first identification information
  • the order of appearance of the first identifiers is the same, and the order of appearance of the first identifiers includes the order of appearance in the same second RRC message.
  • the first identification information includes first identifications related to the more than one second terminal equipment, and the order of appearance of the second identifications is the same as There is a one-to-one correspondence between the appearance order of the first identifiers. Therefore, the correspondence between the second identifier and the first identifier is indicated in this implicit manner.
  • the third RRC message may also indicate the second identity and the first identity corresponding to the second identity at the same time, thereby indicating the correspondence between the second identity and the first identity in this explicit manner relation.
  • the third RRC message may be RRC setup/resume or RRC reconfiguration, or, when the second RRC message is RRC setup/resume complete, the third RRC message It can be RRC reconfiguration, no more examples here.
  • the first terminal device may add the second identifier to the header of the adaptation layer.
  • the information exchange process between the terminal device and the network device will be described in the embodiment of the second aspect.
  • the identity of the second terminal device can be configured by the serving network device of the first terminal device, so that the first terminal device can use This identification helps the RRC message and user plane data of the second terminal device to be correctly identified by the network device.
  • An embodiment of the present application provides an information receiving method, which is applied to a network device side.
  • Figure 7 is a schematic diagram of the information receiving method, as shown in Figure 7, the method includes:
  • the network device receives first identification information sent by the first terminal device, where the first identification information is used to indicate the at least one first identification related to the second terminal device connected to the first terminal device.
  • the implementation of 701 corresponds to 602 in the embodiment of the first aspect. Please refer to the embodiment of the first aspect for the first identification, the carrying mode and format of the first identification information, etc., which are not described here. Let me repeat.
  • the method may also include:
  • the network device sends second identification information to the first terminal device, where the second identification information is used to indicate a second identification of the at least one second terminal device.
  • the implementation manner of 702 corresponds to 603 in the embodiment of the first aspect. Please refer to the embodiment of the first aspect for the second identifier, the bearing method and format of the second identifier information, etc., which are not mentioned here. Let me repeat.
  • the method may further include: (not shown) the network device using or storing the correspondence between the first identifier and the second identifier, or the network device may also use or store the first identifier, the second identifier The corresponding relationship between the identifier and the assigned C-RNTI.
  • FIG. 8 to FIG. 11 are schematic diagrams of uplink and downlink transmission methods in a terminal device-network device relay scenario according to an embodiment of the present application, and are described below in conjunction with FIG. 8 to FIG. 11 .
  • Fig. 8 is a schematic diagram of the method when the first terminal equipment is in the RRC connection mode, as shown in Fig. 8, the method includes:
  • the first terminal device establishes a connection with the second terminal device
  • the second terminal device sends a first RRC message to the first terminal device (for example, using the default layer 2 configuration on the PC5 interface to send the first RRC message), so as to establish a connection with the network device through the first terminal device;
  • the first terminal device sends the SUI to the network device, where the SUI carries first identification information;
  • the network device sends a fourth RRC message to the first terminal device, where the fourth RRC message carries the second identification information;
  • the first terminal device forwards the first RRC message to the network device, where the second identifier is included in the header of the adaptation layer;
  • the network device accepts the connection establishment request of the second terminal device, reply to the first terminal device with an RRC setup message (the fifth RRC message) for the second terminal device, where the message includes the first RRC setup message in the header of the adaptation layer Two identifiers, optionally including the C-RNTI of the second terminal device;
  • the first terminal device forwards the RRC setup message to the second terminal device (for example, using the default layer 2 configuration on the PC5 interface to forward the fifth RRC message);
  • the header file of the adaptation layer of the PC5 interface may include the identifier of the bearer
  • the data of the uplink and/or downlink radio bearer of the Uu interface may include the second ID and Uu radio bearer ID, so that the network device can identify the second terminal device, that is, determine which second terminal device the uplink and downlink transmission corresponds to.
  • FIG. 9 is a schematic diagram of a method when the first terminal device is in RRC idle or inactive mode. As shown in FIG. 9, the method includes:
  • the first terminal device establishes a connection with the second terminal device
  • the second terminal device sends a first RRC message to the first terminal device (for example, using the default layer 2 configuration on the PC5 interface to send the first RRC message), so as to establish a connection with the network device through the first terminal device;
  • the first terminal device executes its own RRC connection establishment process or RRC resume process, and enters the RRC connection mode. For details, reference may be made to the prior art, and details are not repeated here.
  • the first terminal device sends the SUI to the network device, where the SUI carries first identification information;
  • the network device sends a fourth RRC message to the first terminal device, where the fourth RRC message carries the second identification information;
  • the first terminal device forwards the first RRC message to the network device, where the second identifier is included in the header of the adaptation layer;
  • the network device accepts the connection establishment request of the second terminal device, reply to the first terminal device with an RRC setup message (the fifth RRC message) for the second terminal device, where the message includes the first RRC setup message in the header of the adaptation layer Two identifiers, optionally including the C-RNTI of the second terminal device;
  • the first terminal device forwards the RRC setup message to the second terminal device (for example, using the default layer 2 configuration on the PC5 interface to forward the fifth RRC message);
  • the header file of the adaptation layer of the PC5 interface may include the identifier of the bearer
  • the data of the uplink and/or downlink radio bearer of the Uu interface may include the second ID and the Uu radio bearer ID of the second terminal device, so that the network device can identify the second terminal device, that is, determine which second terminal device the uplink and downlink transmission corresponds to.
  • FIG. 10 is a schematic diagram of a method when the first terminal device is in RRC idle or inactive mode. As shown in FIG. 10, the method includes:
  • the first terminal device establishes a connection with the second terminal device
  • the second terminal device sends a first RRC message to the first terminal device (for example, using the default layer 2 configuration on the PC5 interface to send the first RRC message), so as to establish a connection with the network device through the first terminal device;
  • the first terminal device executes its own RRC connection establishment process or RRC resume process, and sends a second RRC message to the network device, the second RRC message carries the first identification information, and the second RRC message is an RRC setup request message or RRC resume request message;
  • the network device After receiving the second RRC message, the network device sends a third RRC message to the first terminal device, where the third RRC message carries the second identification information, and the third RRC message is an RRC setup message or an RRC resume message;
  • the first terminal device sends its own RRC setup complete message or RRC resume complete message to the network device to complete its own RRC connection process or RRC resume process;
  • the network device sends an RRC reconfiguration message to the first terminal device
  • the first terminal device forwards the first RRC message to the network device, where the second identifier is included in the header of the adaptation layer;
  • the network device accepts the connection establishment request of the second terminal device, reply to the first terminal device with an RRC setup message (the fifth RRC message) for the second terminal device, the message includes the first RRC setup message in the header of the adaptation layer Two identifiers, optionally including the C-RNTI of the second terminal device;
  • the first terminal device forwards the RRC setup message for the second terminal device to the second terminal device (for example, using the default layer 2 configuration on the PC5 interface to forward the fifth RRC message);
  • the header file of the adaptation layer of the PC5 interface may include the identifier of the bearer
  • the data of the uplink and/or downlink radio bearer of the Uu interface may include the second ID and the Uu radio bearer ID of the second terminal device, so that the network device can identify the second terminal device, that is, determine which second terminal device the uplink and downlink transmission corresponds to.
  • FIG. 11 is a schematic diagram of a method when the first terminal device is in RRC idle or inactive mode. As shown in FIG. 9, the method includes:
  • the first terminal device establishes a connection with the second terminal device
  • the second terminal device sends a first RRC message to the first terminal device (for example, using the default layer 2 configuration on the PC5 interface to send the first RRC message), so as to establish a connection with the network device through the first terminal device;
  • the first terminal device executes its own RRC connection establishment process or RRC resume process, and sends an RRC setup/resume request message for itself to the network device;
  • the network device After receiving the RRC setup/resume request message, the network device sends an RRC setup/resume message aimed at the first terminal device to the first terminal device;
  • the first terminal device sends a second RRC message to the network device, where the second RRC message carries the first identification information, and the second RRC message is an RRC setup/resume complete message;
  • the network device sends a third RRC message to the first terminal device, where the third RRC message carries second identification information, and the third RRC message is an RRC reconfiguration message;
  • the first terminal device forwards the first RRC message to the network device, where the second identifier is included in the header of the adaptation layer;
  • the network device accepts the connection establishment request of the second terminal device, reply to the first terminal device with an RRC setup message (the fifth RRC message) for the second terminal device, the message includes the first RRC setup message in the header of the adaptation layer Two identifiers, optionally including the C-RNTI of the second terminal device;
  • the first terminal device forwards the RRC setup message for the second terminal device to the second terminal device (for example, using the default layer 2 configuration on the PC5 interface to forward the fifth RRC message);
  • the PC5 interface can use the source layer 2 or destination layer 2 identifier to perform the uplink and/or downlink radio bearer
  • the header file of the adaptation layer of the PC5 interface may include the identifier of the bearer
  • the data of the uplink and/or downlink radio bearer of the Uu interface may include the second ID and the Uu radio bearer ID of the second terminal device, so that the network device can identify the second terminal device, that is, determine which second terminal device the uplink and downlink transmission corresponds to.
  • the implementation of 801-805, 901-905, 1001-1005, and 1101-1105 may refer to the embodiment of the first aspect.
  • operation 802 may be performed before 803 or after 803, or 804 Or it is executed after 805, which is not limited in this embodiment of the present application.
  • the identity of the second terminal device can be configured by the serving network device of the first terminal device, so that the first terminal device can use This identification helps the RRC message and user plane data of the second terminal device to be correctly identified by the network device.
  • the above embodiments of the first aspect and the second aspect illustrate how to allocate the identification related to the remote terminal equipment during the initial access process.
  • Identification related to terminal equipment Identification related to terminal equipment.
  • the second identity can be configured or reconfigured by the network device.
  • An embodiment of the present application provides a method for sending information, which is applied to a network device (hereinafter referred to as a target network device) side.
  • Figure 12 is a schematic diagram of the information sending method, as shown in Figure 12, the method includes:
  • the network device determines that the second terminal device is switched to connect to the network device through the first terminal device;
  • the network device sends second identification information to the first terminal device, where the second identification information is used to indicate a second identification of the second terminal device.
  • the switching of the second terminal device includes the first switching or the second switching, and the first switching means that the second terminal device is connected to the source network device through the Uu interface (direct link direct link Road) to switch to the second terminal device to connect to the target network device through the first terminal device (indirect link indirect link); the second switch means that the second terminal device is connected to the source network device through the source first terminal device Switching to switching between the target first terminal device and the target network device (indirect link to indirect link), the source network device and the target network device may be the same or different, and this embodiment of the present application is not limited by this, the network device determines Whether/how the second terminal device switches may be determined according to the measurement report reported by the second terminal device, for details, reference may be made to the prior art, and details will not be repeated here.
  • the network device may assign a new second identifier to the second terminal device, and notify the first terminal device (target first terminal device) of the newly assigned second identifier
  • the second identifier information may be carried by the first RRC reconfiguration message.
  • the first terminal device and the second terminal device may establish a connection, or The connection may not be established yet, which will be described below.
  • the network device may send the second identification information to the first terminal device before the handover of the second terminal device is completed.
  • the first terminal device does not know the first identifier related to the second terminal device, and therefore does not know which second terminal device the assigned second identifier corresponds to.
  • the method may also include: (not shown )
  • the network device sends the second identification information to the second terminal device.
  • the network device may use the second RRC reconfiguration message to carry the second identification information sent to the second terminal device, so that during or after the connection establishment between the first terminal device and the second terminal device, the first The terminal device and the network device may determine the correspondence between the first identifier and the second identifier, that is, the method may further include: (not shown)
  • the network device After the first terminal device establishes a connection with the second terminal device, the network device receives the first identification information and the corresponding second identification information sent by the first terminal device, and the first identification information is used to indicate that the second terminal device
  • the meaning of the first identifier can refer to the embodiment of the first aspect.
  • the first terminal device after establishing a connection between the first terminal device and the second terminal device, the first terminal device can determine the corresponding relationship between the second identifier and the first identifier (details will be described in the embodiment of the fourth aspect), the The first terminal device may send the first identification information and the corresponding second identification information to the network device, and the method may further include: the network device uses or stores a correspondence relationship between the first identification and the second identification.
  • the first identification information and the corresponding second identification information may be carried by a SUI message, for example, it may be a newly added information element sl-RemoteUEList-r16 in the SUI, for example, the newly added
  • the information element includes the first identifier and the second identifier, which are either included in the side link failure information element sl-FailureList-r16, or included in the side link transmission resource request information element SL-TxResourceReq-r16.
  • the network The device can identify which side link radio link identification (SL RLF) has occurred between the second terminal device and the first terminal device, and stop sending data to the second terminal device through the first terminal device, saving overhead.
  • SL RLF side link radio link identification
  • the method may also include: (not shown)
  • the network device After the first terminal device establishes a connection with the second terminal device, the network device receives the first identification information sent by the second terminal device, and the first identification information is used to indicate the first identification related to the second terminal device .
  • the second terminal device may carry the first identification information through a measurement report message, that is, before the handover, the network device has learned the first identification related to the second terminal device, then in 1202,
  • the network device may simultaneously notify the first terminal device of the second identification information and the first identification corresponding to the second identification, that is, the first RRC reconfiguration message not only carries the second identification information, but also indicates the
  • the first identifier corresponding to the second identifier that is, the method may further include: (not shown in the figure) the network device uses or stores a correspondence relationship between the first identifier and the second identifier.
  • the identity of the second terminal device can be configured by the serving network device of the first terminal device, so that the first terminal device can use This identification helps the RRC message and user plane data of the second terminal device to be correctly identified by the network device.
  • the embodiment of the present application provides an information receiving method, which is applied to the side of the first terminal device (hereinafter referred to as the target first terminal device).
  • Figure 13 is a schematic diagram of the information receiving method, as shown in Figure 13, the method includes:
  • the first terminal device receives second identification information sent by the network device, where the second identification information is used to indicate a second identification of the second terminal device, where the second terminal device determines to switch to the network through the first terminal device. Connect to the network device.
  • the second identification information may be carried by the first RRC reconfiguration message.
  • the method may also include:
  • the first terminal device receives the second identification information sent by the second terminal device.
  • the second identification information sent by the second terminal device is carried by a side link signaling message or a side link RRC message between the first terminal device and the second terminal device, and the side link
  • the link signaling (PC5-S) message or the side link RRC (PC5-RRC) message is also used to indicate the first identifier, for example, the first identifier may be explicitly included in the above message or through the lower layer ( For example, the MAC layer and/or the physical layer) implicitly indicates the first identifier.
  • the side link signaling message may be a discovery message or a direct communication request message (direct communication request) or a direct communication accept message (direct communication accept)
  • the side link RRC message may be an RRC reconfiguration side link message ( RRCReconfigurationSidelink) message or RRCReconfigurationCompleteSidelink message (RRCReconfigurationCompleteSidelink) message
  • the above-mentioned message can be to perform relay discovery, relay selection or relay reselection, or PC5unicast link establishment process between the second terminal device and the first terminal device sent during or after.
  • the first identifier and the second identifier are indicated by the side link signaling message or the side link RRC message between the first terminal device and the second terminal device, then the first terminal device and the second terminal device After the terminal device establishes the connection, the first terminal device can determine the correspondence between the second identifier and the first identifier.
  • the method may further include:
  • the first terminal device sends the first identification information and the corresponding second identification information to the network device, the first identification information is used to indicate the first identification related to the second terminal device, and the first identification information
  • the meaning can refer to the embodiment of the first aspect.
  • the first terminal device may send the first identifier information and the corresponding second identifier information to the network device.
  • the method may further include: (not shown) using or storing the correspondence between the first identifier and the second identifier by the first terminal device.
  • the first identification information sent by the first terminal device and the corresponding second identification information may be carried by a SUI message.
  • SUI message For details, reference may be made to the embodiment of the third aspect, which will not be repeated here.
  • the first RRC reconfiguration message may indicate the second identity and the corresponding first identity at the same time, and the first terminal device receives the first RRC After the reconfiguration message, the corresponding relationship between the second identifier and the first identifier can be determined.
  • the method may further include: (not shown) using or storing the correspondence between the first identifier and the second identifier by the first terminal device.
  • the identifier of the second terminal device can be configured by the serving network device of the first terminal device, so that the first terminal device can use the identifier when forwarding the data of the second terminal device (such as RRC messages and user plane data, etc.), which helps The RRC message and user plane data of the second terminal device are correctly identified by the network device.
  • An embodiment of the present application provides a method for sending and receiving information, which is applied to a second terminal device side.
  • Figure 14 is a schematic diagram of the information sending and receiving method, as shown in Figure 14, the method includes:
  • the second terminal device sends first identification information to the network device, where the first identification information is used to indicate a first identification related to the second terminal device; and/or,
  • the second terminal device receives second identification information sent by the network device, where the second identification information is used to indicate a second identification of the second terminal device.
  • Figure 15 is a schematic diagram of the information sending and receiving method, as shown in Figure 15, the method includes:
  • the second terminal device receives second identification information sent by the network device, where the second identification information is used to indicate a second identification of the second terminal device;
  • the second terminal device sends the second identification information to the first terminal device.
  • the second identification information may be carried by a second RRC reconfiguration message, for example, an RRC reconfiguration message (such as a handover command) containing relevant information of handover to the target first terminal device, about which
  • RRC reconfiguration message such as a handover command
  • the second identification information may be carried by an edge link signaling message or an edge link RRC message between the first terminal device and the second terminal device, and the edge link
  • the link signaling message or the side link RRC message is also used to indicate the first identifier, and for the implementation manner thereof, reference may be made to the embodiment of the fourth aspect, which will not be repeated here.
  • Figure 16 is a schematic diagram of the information sending method, as shown in Figure 16, the method includes:
  • the second terminal device sends first identification information to a network device, where the first identification information is used to indicate a first identification related to the second terminal device.
  • the first identification information may be carried by a measurement report message, and for details, refer to the embodiment of the third aspect.
  • the switching method will be described below by taking switching from a direct link to an indirect link as an example with reference to FIGS. 17 to 18 .
  • Fig. 17 is a schematic diagram of the method when the connection between the first terminal device and the second terminal device has not been established before handover. As shown in Fig. 17, the method includes:
  • the (target) network device sends the measurement configuration to the second terminal device;
  • the second terminal device performs measurement according to the measurement configuration, and reports a measurement report, which may include at least one candidate first terminal device identifier (Relay UE ID), the serving cell of the first terminal device, and side link measurement results;
  • a measurement report which may include at least one candidate first terminal device identifier (Relay UE ID), the serving cell of the first terminal device, and side link measurement results;
  • the network device determines, according to the measurement report, that the second terminal device switches to connect to the network device through the first terminal device;
  • the network device sends to the first terminal device a first RRC reconfiguration message used for handover of the second terminal device, where the message includes second identification information, and Uu and PC5 RLC configuration and bearer mapping configuration for relay;
  • the first terminal device completes RLC configuration and bearer mapping configuration with the corresponding PC5 interface and Uu interface according to the first RRC reconfiguration message;
  • the first terminal device sends an RRC reconfiguration complete message (corresponding to 1704) to the network device.
  • RRC reconfiguration complete message (corresponding to 1704)
  • the network device sends a second RRC reconfiguration message for the second terminal device to the second terminal device, for example, a switching command to switch to the network device through the first terminal device, where the message includes second identification information, and The identification (Relay UE ID) of the first terminal device, the PC5 RLC configuration of the relay service and the related end-to-end radio bearer (radio bearer) configuration; the second terminal device determines to switch to the radio bearer according to the second RRC reconfiguration message Which first terminal device is connected to the network device.
  • a second RRC reconfiguration message for the second terminal device to the second terminal device, for example, a switching command to switch to the network device through the first terminal device, where the message includes second identification information, and The identification (Relay UE ID) of the first terminal device, the PC5 RLC configuration of the relay service and the related end-to-end radio bearer (radio bearer) configuration; the second terminal device determines to switch to the radio bearer according to the second RRC reconfiguration message Which first terminal device is connected to the network device
  • the second terminal device establishes a connection with the first terminal device.
  • the side link signaling message or the side link RRC message between the two carries the second identification information, and the side link signaling (PC5-S) message or the side link RRC (PC5-RRC) message is also used to indicate the First logo.
  • PC5-S side link signaling
  • PC5-RRC side link RRC
  • the first terminal device sends the first identification information and the corresponding second identification information to the network device, for example, using the SUI to carry the first identification information and the corresponding second identification information, which will not be described here repeat.
  • the first identification information sent by the first terminal device to the network device and the corresponding second identification information are included in the side link failure information element sl-FailureList-r16 of the SUI message, this step is performed in the side chain Executed when a radio link failure is detected.
  • the first terminal device uses or stores the correspondence between the first identifier and the second identifier.
  • the second terminal device sends an RRC reconfiguration complete message to the network device via the first terminal device (corresponding to 1706).
  • the handover of the second terminal device is completed, and the second terminal device and the network device send and receive uplink and/or downlink radio bearer data via the first terminal device, where the PC5 interface can use source layer 2 or destination Layer 2 identifies the data to be sent and/or received by the uplink and/or downlink radio bearer.
  • the header file of the adaptation layer of the PC5 interface may include the bearer identifier.
  • the data of the uplink and/or downlink radio bearer is in The header of the adaptation layer of the Uu interface includes the second identifier and the Uu radio bearer identifier of the second terminal device, so that the network device can identify the second terminal device, that is, determine which second terminal device the uplink and downlink transmission corresponds to.
  • FIG. 18 is a schematic diagram of the method in the case where the connection between the first terminal device and the second terminal device is established before handover. As shown in FIG. 18 , the method includes:
  • the second terminal device establishes a connection with the first terminal device
  • the (target) network device sends the measurement configuration to the second terminal device;
  • the second terminal device performs measurement according to the measurement configuration, and reports a measurement report;
  • the measurement report may include at least one candidate first terminal device identifier (Relay UE ID), the serving cell and the side chain of the first terminal device
  • the road measurement result may also include first identification information;
  • the network device determines, according to the measurement report, that the second terminal device switches to connect to the network device through the first terminal device;
  • the network device sends to the first terminal device a first RRC reconfiguration message for handover of the second terminal device, where the message simultaneously indicates the second identity and the first identity corresponding to the second identity (obtained according to 1803), and Uu and PC5 RLC configuration and bearer mapping configuration for relaying; the first terminal device completes the RLC configuration and bearer mapping configuration of the corresponding PC5 interface and Uu interface according to the first RRC reconfiguration message;
  • the network device sends a second RRC reconfiguration message for the second terminal device to the second terminal device, where the message includes the identifier (Relay UE ID) of the first terminal device, the PC5 RLC configuration of the relay service, and the relevant end-to-end terminal radio bearer (radio bearer) configuration; the second terminal device determines, according to the second RRC reconfiguration message, which first terminal device to connect to the network device through.
  • the message includes the identifier (Relay UE ID) of the first terminal device, the PC5 RLC configuration of the relay service, and the relevant end-to-end terminal radio bearer (radio bearer) configuration
  • the second terminal device determines, according to the second RRC reconfiguration message, which first terminal device to connect to the network device through.
  • the first terminal device uses or stores the correspondence between the first identifier and the second identifier.
  • the second terminal device sends an RRC reconfiguration complete message to the network device via the first terminal device (corresponding to 1806).
  • the handover of the second terminal device is completed, and the second terminal device and the network device send and receive uplink and/or downlink radio bearer data via the first terminal device, wherein the PC5 interface can use source layer 2 or destination Layer 2 identifies the data to be sent and/or received by the uplink and/or downlink radio bearer.
  • the header file of the adaptation layer of the PC5 interface may include the bearer identifier.
  • the data of the uplink and/or downlink radio bearer is in The header of the adaptation layer of the Uu interface includes the second identifier and the Uu radio bearer identifier of the second terminal device, so that the network device can identify the second terminal device, that is, determine which second terminal device the uplink and downlink transmission corresponds to.
  • the identity of the second terminal device can be configured by the serving network device of the first terminal device, so that the first terminal device can use This identification helps the RRC message and user plane data of the second terminal device to be correctly identified by the network device.
  • the first index may be used instead of the destination identifier for transmission.
  • the length of the first index is smaller than the length of the destination identifier, but the destination identifier can be uniquely identified.
  • the embodiment of the present application proposes an information sending method, by carrying the first index and the second identifier or the destination identifier in the side link failure related information sent by the first terminal device to the network device, so that the network The device correctly identifies which SL of the PC5 interface detects the RLF.
  • An embodiment of the present application provides an information sending method, which is applied to a first terminal device side.
  • Figure 19 is a schematic diagram of the information sending method, as shown in Figure 19, the method includes:
  • the first terminal device sends information related to side link failure to the network device, where the information related to side link failure includes a destination identifier of at least one second terminal device where side link failure occurs, and the side link failure occurs.
  • the first index can be used instead of the destination identifier for transmission, the length of the first index is smaller than the length of the destination identifier, but the destination identifier can be uniquely identified, for example , the first terminal device or the second terminal device may assign the first index, and notify the other party and/or the network device, when the first index is assigned by the first terminal device, the method may further include:
  • the first terminal device allocates the first index and sends second information indicating the first index to the second terminal device, for example, the second information may be carried by a side link signaling message or a side link RRC message,
  • the side link signaling message or the side link RRC message is as described in the previous embodiment, and will not be repeated here.
  • the method may further include:
  • the first terminal device receives the first information indicating the first index assigned and sent by the second terminal device, for example, the second information may be carried by a side link signaling message or a side link RRC message, and the side link
  • the link signaling message or the side link RRC message is as described in the previous embodiment, and will not be repeated here.
  • the method may also include:
  • the first terminal device sends third information indicating the first index to the network device.
  • the first terminal device when it detects the side link RLF of the PC5 interface, it will report the side link RLF of the PC5 interface to the network device, for example, use the information related to the side link failure to notify the network device that the detected RLF, the side link failure related information includes the destination identifier of at least one second terminal device where the side link failure occurs, and the second identifier of the second terminal device where the side link failure occurs and/or the The first identifier related to the second terminal device where the side link failure occurs, the first identifier is the first index, the implementation of the second identifier is as described above, and will not be repeated here.
  • the side link failure-related information may be carried by the SUI, and in the existing method, the sl-FailureList-r16 includes at least one second terminal where a side link failure occurs
  • the destination identifier of the device in this embodiment of the application, may further include the first identifier, or the second identifier, or, the first identifier and the second identifier.
  • An embodiment of the present application provides an information receiving method, which is applied to a network device side.
  • Figure 20 is a schematic diagram of the information receiving method, as shown in Figure 20, the method includes:
  • the network device receives information related to side link failure sent by the first terminal device, where the information related to side link failure includes a destination identifier of at least one second terminal device where side link failure occurs, and the side link failure occurs The second identifier of the second terminal device that failed the link and/or the first identifier related to the second terminal device that failed the side link.
  • the implementation of the first identification and the second identification is as described above, and details are not repeated here.
  • the method may also include:
  • the network device receives third information indicating the first index sent by the first terminal device, so as to determine the first index assigned to the destination identifier by the first terminal device or the second terminal device.
  • An embodiment of the present application provides a method for sending and receiving information, which is applied to a second network device side.
  • Figure 21 is a schematic diagram of the information sending and receiving method, as shown in Figure 21, the method includes:
  • the second terminal device allocates a first index, and sends first information indicating the first index to the first terminal device; or, the second terminal device receives information indicating the first index sent by the first terminal device. Second information; the first index corresponds to the destination identifier of the second terminal device.
  • the method may also include:
  • the network device receives third information indicating the first index sent by the first terminal device, so as to determine the first index assigned to the destination identifier by the first terminal device or the second terminal device.
  • the first information or the second information may be carried by a side link signaling message or a side link RRC message.
  • the side link signaling message or the side link RRC message is as described in the previous embodiment.
  • An embodiment of the present application provides an information sending/receiving apparatus configured in a first terminal device.
  • Fig. 22 is a schematic diagram of an information receiving apparatus according to an embodiment of the present application, and this embodiment of the present application is described from the side of the first terminal device.
  • the implementation principle of the information receiving device in the embodiment of the present application is similar to the implementation in the embodiment of the first aspect, and the same content will not be described again.
  • the information receiving device 2200 of the embodiment of the present application includes:
  • a processing unit 2201 which establishes a connection with at least one second terminal device
  • a first sending unit 2202 configured to send first identification information to a network device, where the first identification information is used to indicate a first identification related to the at least one second terminal device;
  • the first receiving unit 2203 is configured to receive second identification information sent by the network device, where the second identification information is used to indicate a second identification of the at least one second terminal device.
  • the first identification information is carried by the SUI or the second RRC message directed to the first terminal device.
  • the first terminal device is in RRC connected mode; or, when the first terminal device is in RRC idle or inactive mode, the apparatus further includes: (not shown, optional)
  • a second receiving unit which receives the first RRC message sent by the second terminal device and is directed to the second terminal device, and enters an RRC connection mode.
  • the second RRC message for the first terminal device includes RRC setup request or RRC setup complete or RRC resume request or RRC resume complete.
  • the first RRC message for the second terminal device includes an RRC setup request or RRC re-establishment request or RRC resume request message.
  • the first sending unit when a first trigger condition is met, sends the first identification information to the network device, where the first trigger condition includes at least one of the following conditions:
  • the first terminal device receives the first RRC message sent by the second terminal device and directed to the second terminal device.
  • the first identifier is a destination identifier (destination ID) or a first index, and/or an identifier of a PC5 unicast link, and/or, an identifier of a PC5-RRC connection, and/or a source identifier pair with the destination ID.
  • the first identification information includes a first identification related to a second terminal device
  • the second terminal device is a terminal device that newly establishes a connection with the first terminal device
  • the first identification information includes First identifiers related to all second terminal devices that have established connections with the first terminal device.
  • the second identity is a local/temporary identity of the second terminal device.
  • the local/temporary identification includes at least one of the following:
  • a second index of the second terminal device where the second index is used to uniquely identify a second terminal device that has a connection relationship with the first terminal device
  • the second identification information is carried by a fourth RRC message for the first terminal device or a third RRC message for the first terminal device, and the fourth RRC message includes RRC reconfiguration or RRC re-establishment or RRC resume message, the third RRC message for the first terminal device includes RRC setup or RRC resume or RRC reconfiguration.
  • an arrangement order of the second identifications in the second identification information is the same as an appearance order of the first identifications related to the at least one second terminal device in the first identification information.
  • the third RRC message is further used to indicate the first identity corresponding to the second identity
  • the fourth RRC message is further used to indicate the first identity corresponding to the second identity
  • the device also includes: (not shown, optional)
  • the first storage unit uses or stores the correspondence between the first identifier and the second identifier.
  • the device also includes: (not shown, optional)
  • the second sending unit is configured to send information related to side link failure to the network device, where the information related to side link failure includes a destination identifier of at least one second terminal device where side link failure occurs, and the side link failure occurs The second identifier of the second terminal device whose side link failed and/or the first identifier related to the second terminal device whose side link failed.
  • Fig. 23 is a schematic diagram of an information receiving apparatus according to an embodiment of the present application, and this embodiment of the present application is described from the side of the first terminal device.
  • the implementation principle of the information receiving device in the embodiment of the present application is similar to the implementation in the embodiment of the fourth aspect, and the same content will not be described again.
  • the information receiving device 2300 of the embodiment of the present application includes:
  • the eleventh receiving unit 2301 is configured to receive the second identification information sent by the network device, the second identification information is used to indicate the second identification of the second terminal device, where the second terminal device determines to switch to the first terminal through the first terminal The device is connected to the network device.
  • the device also includes: (not shown, optional)
  • a twelfth receiving unit configured to receive the second identification information sent by the second terminal device.
  • the second identification information received by the twelfth receiving unit is carried by a side link signaling message or a side link RRC message between the first terminal device and the second terminal device, and the side link The link signaling message or the side link RRC message is also used to indicate the first identifier.
  • the second identification information received by the eleventh receiving unit is carried by a first RRC reconfiguration message.
  • the first RRC reconfiguration message is also used to indicate the first identity corresponding to the second identity.
  • the device also includes: (not shown, optional)
  • the fifth storage unit uses or stores the corresponding relationship between the first identifier and the second identifier.
  • the device also includes: (not shown, optional)
  • a thirteenth sending unit configured to send the first identification information and the corresponding second identification information to the network device.
  • the first identification information and the corresponding second identification information are carried by the SUI.
  • the first identification information and the corresponding second identification information are newly added information elements in the SUI, or are included in the side link failure information element, or are included in the side link transmission resource in the request information element.
  • Fig. 24 is a schematic diagram of an information sending apparatus according to an embodiment of the present application, and this embodiment of the present application is described from the side of the first terminal device.
  • the implementation principle of the information sending device in the embodiment of the present application is similar to the implementation in the embodiment of the sixth aspect, and the same content will not be described again.
  • the information sending device 2400 of the embodiment of the present application includes:
  • a fourth sending unit 2401 which sends information related to side link failure to the network device, where the information related to side link failure includes a destination identifier of at least one second terminal device where side link failure occurs, and the side link failure occurs The second identifier of the second terminal device that failed the link and/or the first identifier related to the second terminal device that failed the side link.
  • the second identity is a local/temporary identity of the second terminal device.
  • the local/temporary identification includes at least one of the following:
  • a second index of the second terminal device where the second index is used to uniquely identify the second terminal device
  • the first identifier is a first index of the second terminal device.
  • the device also includes: (not shown, optional)
  • a fifth receiving unit which receives the first information indicating the first index allocated and sent by the second terminal device; or, a fifth sending unit, which allocates the first index and sends the first information indicating the first index to the second terminal device Indexed second information.
  • the first information and/or the second information are carried by a PC5-RRC message or a PC5-S message.
  • the information sending/receiving apparatuses 2200, 2300, and 2400 in this embodiment of the present application may also include other components or modules, and for specific contents of these components or modules, reference may be made to related technologies.
  • connection relationship or signal direction between the various components or modules is only shown in Figure 22 to Figure 24 as an example, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used .
  • the above-mentioned components or modules may be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc.; the implementation of the present application is not limited thereto.
  • An embodiment of the present application provides an information sending and receiving apparatus, which is configured in a second terminal device.
  • Fig. 25 is a schematic diagram of an information receiving apparatus according to an embodiment of the present application, and this embodiment of the present application is described from the side of the second terminal device.
  • the implementation principle of the information sending device in the embodiment of the present application is similar to the implementation in the embodiment of the fifth aspect, and the same content will not be described again.
  • a tenth sending unit 2501 which sends first identification information to the network device, where the first identification information is used to indicate the first identification related to the second terminal device; and/or,
  • the tenth receiving unit 2502 is configured to receive second identification information sent by the network device, where the second identification information is used to indicate the second identification of the second terminal device.
  • the device also includes: (optional, not shown)
  • An eleventh sending unit configured to send the second identification information to the first terminal device.
  • the second identification information is carried by a side link signaling message or a side link RRC message between the first terminal device and the second terminal device, and the side link signaling message or side chain
  • the RRC message is also used to indicate the first identity.
  • the tenth receiving unit receives the second identification information sent by the network device through a second RRC reconfiguration message.
  • the tenth sending unit sends the first identification information to the network device through a measurement report message.
  • Fig. 26 is a schematic diagram of an information sending and receiving apparatus according to an embodiment of the present application, and this embodiment of the present application is described from the side of the second terminal device.
  • the implementation principle of the information sending and receiving device in the embodiment of the present application is similar to the implementation in the embodiment of the eighth aspect, and the same content will not be described again.
  • the seventh sending unit 2601 which allocates the first index, and sends the first information indicating the first index to the first terminal device; or, the seventh receiving unit 2602, which receives the first information sent by the first terminal device and indicates the first The second information of the index; the first index corresponds to the destination identifier of the second terminal device.
  • the information transceiving apparatuses 2500-2600 in this embodiment of the present application may also include other components or modules, and for specific content of these components or modules, reference may be made to related technologies.
  • Fig. 25 to Fig. 26 only exemplarily show the connection relationship or signal direction among the various components or modules, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used .
  • the above-mentioned components or modules may be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc.; the implementation of the present application is not limited thereto.
  • An embodiment of the present application provides an information sending/receiving device configured in a network device.
  • Fig. 27 is a schematic diagram of an information sending apparatus according to an embodiment of the present application, and the embodiment of the present application is described from the side of a network device.
  • the implementation principle of the information sending device in the embodiment of the present application is similar to the implementation in the embodiment of the second aspect, and the same content will not be described again.
  • the information sending device 2700 of the embodiment of the present application includes:
  • a third receiving unit 2701 which receives first identification information sent by the first terminal device, where the first identification information is used to indicate the at least one first identification related to the second terminal device connected to the first terminal device;
  • a third sending unit 2702 configured to send second identification information to the first terminal device, where the second identification information is used to indicate a second identification of the at least one second terminal device.
  • the first identification information is carried by the SUI or the second RRC message directed to the first terminal device.
  • the second RRC message for the first terminal device includes RRC setup request or RRC setup complete or RRC resume request or RRC resume complete.
  • the third receiving unit receives the first identification information sent by the first terminal device, where the first trigger condition includes at least one of the following conditions:
  • the first terminal device receives the first RRC message sent by the second terminal device and directed to the second terminal device.
  • the first identifier is a destination identifier (destination ID) or a first index.
  • the first identification information includes a first identification related to a second terminal device
  • the second terminal device is a terminal device that newly establishes a connection with the first terminal device
  • the first identification information includes First identifiers related to all second terminal devices that have established connections with the first terminal device.
  • the second identity is a local/temporary identity of the second terminal device.
  • the local/temporary identification includes at least one of the following:
  • a second index of the second terminal device where the second index is used to uniquely identify a second terminal device that has a connection relationship with the first terminal device
  • the second identification information is carried by a fourth RRC message for the first terminal device or a third RRC message for the first terminal device, and the fourth RRC message includes RRC reconfiguration or RRC re-establishment or RRC resume message, the third RRC message for the first terminal device includes RRC setup or RRC resume or RRC reconfiguration.
  • an arrangement order of the second identifications in the second identification information is the same as an appearance order of the first identifications related to the at least one second terminal device in the first identification information.
  • the third RRC message is further used to indicate the first identity corresponding to the second identity
  • the fourth RRC message is further used to indicate the first identity corresponding to the second identity
  • the device also includes: (optional, not shown)
  • the second storage unit uses or stores the correspondence between the first identifier and the second identifier.
  • the device also includes: (optional, not shown)
  • the third storage unit uses or stores the correspondence between the first identifier, the second identifier and the allocated C-RNTI.
  • the device also includes: (optional, not shown)
  • a fourth receiving unit configured to receive information related to side link failure sent by the first terminal device, where the information related to side link failure includes a destination identifier of at least one second terminal device where side link failure occurs, and the The second identifier of the second terminal device where the side link failure occurred and/or the first identifier related to the second terminal device where the side link failure occurred.
  • Fig. 28 is a schematic diagram of an information sending apparatus according to an embodiment of the present application, and the embodiment of the present application is described from the side of a network device.
  • the implementation principle of the information sending device in the embodiment of the present application is similar to the implementation in the embodiment of the third aspect, and the same content will not be described again.
  • the information sending device 2800 of the embodiment of the present application includes:
  • a determining unit 2801 which determines that the second terminal device is switched to connect to the network device through the first terminal device;
  • An eighth sending unit 2802 configured to send second identification information to the first terminal device, where the second identification information is used to indicate the second identification of the second terminal device.
  • the device also includes: (optional, not shown)
  • a ninth sending unit configured to send the second identification information to the second terminal device.
  • the device also includes: (optional, not shown)
  • An eighth receiving unit after the first terminal device establishes a connection with the second terminal device, receives the first identification information sent by the first terminal device and the corresponding second identification information, and the first identification information is used for A first identifier related to the second terminal device is indicated.
  • the device also includes: (optional, not shown)
  • a fourth storage unit which uses or stores the correspondence between the first identifier and the second identifier.
  • the second identification information sent by the eighth sending unit is carried by the first RRC reconfiguration message.
  • the second identification information sent by the ninth sending unit is carried in a second RRC reconfiguration message.
  • the device also includes: (optional, not shown)
  • a ninth receiving unit which receives first identification information sent by the second terminal device after the first terminal device establishes a connection with the second terminal device, where the first identification information is used to indicate the First logo.
  • the first identification information is carried by a measurement report message.
  • the first RRC reconfiguration message is also used to indicate the first identity corresponding to the second identity.
  • the first identification information and the corresponding second identification information are carried by the SUI.
  • the first identification information and the corresponding second identification information are newly added information elements in the SUI, or are included in the side link failure information element, or are included in the side link transmission resource in the request information element.
  • FIG. 29 is a schematic diagram of an information receiving apparatus according to an embodiment of the present application.
  • the embodiment of the present application is described from the side of a network device.
  • the implementation principle of the information receiving device in the embodiment of the present application is similar to the implementation in the embodiment of the seventh aspect, and the same content will not be described again.
  • the information receiving device 2900 of the embodiment of the present application includes:
  • the sixth receiving unit 2901 is configured to receive information related to side link failure sent by the first terminal device, where the information related to side link failure includes a destination identifier of at least one second terminal device where side link failure occurs, and the The second identifier of the second terminal device where the side link failure occurred and/or the first identifier related to the second terminal device where the side link failure occurred.
  • the second identity is a local/temporary identity of the second terminal device.
  • the local/temporary identification includes at least one of the following:
  • a second index of the second terminal device where the second index is used to uniquely identify the second terminal device
  • the first identifier is a first index of the second terminal device.
  • the first index is allocated by the first terminal device or allocated by the second terminal device.
  • the information sending/receiving apparatuses 2700-2900 in this embodiment of the present application may also include other components or modules, and for specific content of these components or modules, reference may be made to related technologies.
  • connection relationship or signal direction between the various components or modules is only shown in Figure 27 to Figure 29 as an example, but it should be clear to those skilled in the art that various related technologies such as bus connection can be used .
  • the above-mentioned components or modules may be implemented by hardware facilities such as processors, memories, transmitters, receivers, etc.; the implementation of the present application is not limited thereto.
  • FIG. 30 is a schematic diagram of the communication system. As shown in FIG. 30 , the communication system includes a network device 3001, a first terminal device 3002, and at least one second terminal device 3003;
  • the network device 3001 is configured to execute the method executed by the network device in the embodiment of the second, third, or seventh aspect, and may include any apparatus in FIG. 27 to FIG. 29 .
  • the first terminal device 3002 is configured to execute the method in the embodiment of the first, fourth or sixth aspect, which may include any of the apparatuses in FIG. 22 to FIG. 24 .
  • the second terminal device 3003 is configured to execute the method in the embodiment of the fifth or eighth aspect, which may include any one of the apparatuses in FIG. 25 and FIG. 26 .
  • the embodiment of the present application also provides a terminal device.
  • Fig. 31 is a schematic diagram of a terminal device according to an embodiment of the present application.
  • the terminal device 3100 may include a processor 3101 and a memory 3102 ; the memory 3102 stores data and programs, and is coupled to the processor 3101 . It is worth noting that this figure is exemplary; other types of structures may also be used in addition to or instead of this structure to implement telecommunication functions or other functions.
  • the processor 3101 may be configured to execute a program to implement the methods in the embodiments of the first or fourth to sixth or eighth aspects.
  • the terminal device 3100 may further include: a communication module 3103 , an input unit 3104 , a display 3105 , and a power supply 3106 .
  • a communication module 3103 the terminal device 3100 may further include: a communication module 3103 , an input unit 3104 , a display 3105 , and a power supply 3106 .
  • the functions of the above components are similar to those of the prior art, and will not be repeated here. It should be noted that the terminal device 3100 does not necessarily include all the components shown in FIG. have technology.
  • the embodiment of the present application also provides a network device.
  • Fig. 32 is a schematic diagram of a network device according to an embodiment of the present application.
  • a network device 3200 may include: a processor (such as a central processing unit CPU) 3201 and a memory 3202 ; the memory 3202 is coupled to the processor 3201 .
  • the memory 3202 can store various data; in addition, it also stores information processing programs, and executes the programs under the control of the central processing unit 3201 .
  • the processor 3201 may be configured to execute a program to implement the method in the embodiment of the second or third or seventh aspect.
  • the network device 3200 may further include: a transceiver 3203 and an antenna 3204 ; wherein, the functions of the above components are similar to those of the prior art, and will not be repeated here. It should be noted that the network device 3200 does not necessarily include all components shown in FIG. 32 ; in addition, the network device 3200 may also include components not shown in FIG. 32 , and reference may be made to the prior art.
  • the embodiment of the present application also provides a computer-readable program, wherein when the program is executed in the terminal device, the program causes the computer to execute the first or fourth to sixth or eighth Methods in the Examples of Aspects.
  • the embodiment of the present application also provides a storage medium storing a computer-readable program, wherein the computer-readable program enables the computer to execute the method in the embodiment of the first or fourth to sixth or eighth aspect in the terminal device .
  • the embodiment of the present application also provides a computer-readable program, wherein when the program is executed in the network device, the program causes the computer to execute the method in the second, third or seventh aspect of the embodiment in the network device .
  • the embodiment of the present application also provides a storage medium storing a computer-readable program, wherein the computer-readable program enables a computer to execute the method in the second, third, or seventh embodiment in the network device.
  • the above devices and methods in this application can be implemented by hardware, or by combining hardware and software.
  • the present application relates to a computer-readable program that, when executed by a logic component, enables the logic component to realize the above-mentioned device or constituent component, or enables the logic component to realize the above-mentioned various methods or steps.
  • Logic components such as field programmable logic components, microprocessors, processors used in computers, and the like.
  • the present application also relates to storage media for storing the above programs, such as hard disks, magnetic disks, optical disks, DVDs, flash memories, and the like.
  • the method/device described in conjunction with the embodiments of the present application may be directly embodied as hardware, a software module executed by a processor, or a combination of both.
  • one or more of the functional block diagrams shown in the figure and/or one or more combinations of the functional block diagrams may correspond to each software module or each hardware module of the computer program flow.
  • These software modules may respectively correspond to the steps shown in the figure.
  • These hardware modules for example, can be realized by solidifying these software modules by using a Field Programmable Gate Array (FPGA).
  • FPGA Field Programmable Gate Array
  • a software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM or any other form of storage medium known in the art.
  • a storage medium can be coupled to the processor such that the processor can read information from, and write information to, the storage medium, or it can be an integral part of the processor.
  • the processor and storage medium can be located in the ASIC.
  • the software module can be stored in the memory of the mobile terminal, or can be stored in a memory card that can be inserted into the mobile terminal.
  • the software module can be stored in the MEGA-SIM card or large-capacity flash memory device.
  • One or more of the functional blocks described in the accompanying drawings and/or one or more combinations of the functional blocks can be implemented as a general-purpose processor, a digital signal processor (DSP) for performing the functions described in this application ), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or any suitable combination thereof.
  • DSP digital signal processor
  • ASICs application specific integrated circuits
  • FPGAs field programmable gate arrays
  • One or more of the functional blocks described in the drawings and/or one or more combinations of the functional blocks can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors processor, one or more microprocessors in communication with a DSP, or any other such configuration.
  • a method for sending information, applied to a first terminal device characterized in that the method comprises:
  • the first terminal device sends first identification information to the network device, where the first identification information is used to indicate a first identification related to the at least one second terminal device.
  • the first terminal device receives the first RRC message directed to the second terminal device sent by the second terminal device, and enters an RRC connection mode.
  • the first RRC message for the second terminal device includes an RRC setup request or RRC re-establishment request or RRC resume request message.
  • the first terminal device receives the first RRC message sent by the second terminal device and directed to the second terminal device.
  • the first identification is a destination identification (destination ID) or a first index, and/or an identification of a PC5 unicast link, and/or , the identifier of the PC5-RRC connection, and/or a source identifier and destination identifier pair.
  • the first identification information includes a first identification related to a second terminal device
  • the second terminal device is a A terminal device that newly establishes a connection with the device
  • the first identification information includes all first identifications related to a second terminal device that establishes a connection with the first terminal device.
  • the first terminal device receives second identification information sent by the network device, where the second identification information is used to indicate a second identification of the at least one second terminal device.
  • a second index of the second terminal device where the second index is used to uniquely identify a second terminal device that has a connection relationship with the first terminal device
  • the first terminal device uses or stores the correspondence between the first identifier and the second identifier.
  • the first terminal device sends side link failure-related information to the network device, where the side link failure-related information includes a destination identifier of at least one second terminal device where a side link failure occurs, and the The second identifier of the second terminal device where the side link failure occurred and/or the first identifier related to the second terminal device where the side link failure occurred.
  • a method for receiving information, applied to a network device characterized in that the method comprises:
  • the network device receives first identification information sent by the first terminal device, where the first identification information is used to indicate the at least one first identification related to the second terminal device connected to the first terminal device.
  • the first terminal device receives the first RRC message sent by the second terminal device and directed to the second terminal device.
  • the first identifier is a destination identifier (destination ID) or a first index, and/or an identifier of a PC5 unicast link, and/or , the identifier of the PC5-RRC connection, and/or a source identifier and destination identifier pair.
  • the first identification information includes a first identification related to a second terminal device
  • the second terminal device is a A terminal device that newly establishes a connection with the device
  • the first identification information includes all first identifications related to a second terminal device that establishes a connection with the first terminal device.
  • the network device sends second identification information to the first terminal device, where the second identification information is used to indicate a second identification of at least one second terminal device.
  • a second index of the second terminal device where the second index is used to uniquely identify a second terminal device that has a connection relationship with the first terminal device
  • the network device uses or stores the correspondence between the first identifier and the second identifier.
  • the network device uses or stores the correspondence between the first identifier, the second identifier and the allocated C-RNTI.
  • the network device receives information related to side link failure sent by the first terminal device, where the information related to side link failure includes a destination identifier of at least one second terminal device where side link failure occurs, and the The second identifier of the second terminal device where the side link failure occurs and/or the first identifier related to the second terminal device where the side link failure occurs.
  • a method for sending information, applied to a first terminal device characterized in that the method comprises:
  • the first terminal device sends side link failure-related information to the network device, where the side link failure-related information includes a destination identifier of at least one second terminal device where a side link failure occurs, and the The second identifier of the second terminal device where the side link failure occurred and/or the first identifier related to the second terminal device where the side link failure occurred.
  • a second index of the second terminal device where the second index is used to uniquely identify the second terminal device
  • the first terminal device receives the first information indicating the first index allocated and sent by the second terminal device; or, the first terminal device allocates the first index and sends an indication to the second terminal device The second information of the first index.
  • a method for receiving information, applied to a network device comprising:
  • the network device receives information related to side link failure sent by the first terminal device, where the information related to side link failure includes a destination identifier of at least one second terminal device where side link failure occurs, and the occurrence The second identifier of the second terminal device that failed the side link and/or the first identifier related to the second terminal device that failed the side link.
  • a second index of the second terminal device where the second index is used to uniquely identify the second terminal device
  • the second terminal device allocates a first index, and sends first information indicating the first index to the first terminal device; or, the second terminal device receives the first information sent by the first terminal device indicating the first index Second information of an index; the first index corresponds to the destination identifier of the second terminal device.
  • a method for sending information, applied to a network device characterized in that the method comprises:
  • the network device determines that the second terminal device is switched to connect to the network device through the first terminal device
  • the network device sends second identification information to the first terminal device, where the second identification information is used to indicate a second identification of the second terminal device.
  • the network device sends the second identification information to the second terminal device.
  • the network device After the first terminal device establishes a connection with the second terminal device, the network device receives the first identification information and the corresponding second identification information sent by the first terminal device, and the first identification The information is used to indicate the first identifier related to the second terminal device.
  • the network device uses or stores the correspondence between the first identifier and the second identifier.
  • the network device After the first terminal device establishes a connection with the second terminal device, the network device receives first identification information sent by the second terminal device, where the first identification information is used to indicate that the second terminal The first identifier associated with the device.
  • a method for sending and receiving information, applied to a second terminal device characterized in that the method comprises:
  • the second terminal device sends first identification information to the network device, where the first identification information is used to indicate a first identification related to the second terminal device; and/or,
  • the second terminal device receives second identification information sent by the network device, where the second identification information is used to indicate a second identification of the second terminal device.
  • the second terminal device sends the second identification information to the first terminal device.
  • a method for receiving information, applied to a first terminal device characterized in that the method comprises:
  • the first terminal device receives second identification information sent by the network device, where the second identification information is used to indicate a second identification of the second terminal device, where the second terminal device determines to switch to the A terminal device is connected to the network device.
  • the first terminal device receives the second identification information sent by the second terminal device.
  • the first terminal device uses or stores the correspondence between the first identifier and the second identifier.
  • the first terminal device sends the first identification information and the corresponding second identification information to the network device.
  • a network device comprising a memory and a processor, the memory stores a computer program, wherein the processor is configured to execute the computer program to implement any one of Supplements 17 to 31, 44 to 53 the method described.
  • a terminal device comprising a memory and a processor, wherein the memory stores a computer program, wherein the processor is configured to execute the computer program to implement the following items as in Supplementary Notes 1 to 16, 32 to 43, and 54 to 67. The method of any one of.
  • a communication system including a network device, a first terminal device, and a second terminal device, wherein the network device is configured to execute the method described in any one of Supplementary Notes 17 to 31, 44 to 53, the The first terminal device is configured to execute the method described in any one of Supplements 1 to 16, 59 to 67, and the second terminal device is configured to execute any one of Supplements 32 to 43, 54 to 58 Methods.

Abstract

本申请实施例提供了一种信息发送方法、信息接收方法、装置和系统，该信息发送方法包括：第一终端设备与至少一个第二终端设备建立连接；所述第一终端设备向网络设备发送第一标识信息，所述第一标识信息用于指示所述至少一个第二终端设备相关的第一标识。

Description

信息发送方法、信息接收方法、装置和系统 技术领域
本申请涉及通信领域。
背景技术
在当前通信网络中，终端设备通过Uu接口接入到网络部分，终端设备通过PC5接口与其他终端设备通信，目前，在R17中已经开始研究边链路中继(SL relay)，图1中示出了边链路中继场景示意图，场景一中，远端终端设备(remote UE)不在基站或小区的覆盖范围内，中继终端设备(relay UE)在基站或小区的覆盖范围内，场景二中，远端终端设备和中继终端设备都在基站或小区的覆盖范围内，场景三中，远端终端设备和中继终端设备在不同基站或小区的覆盖范围内。其中，relay UE的Uu链路上使用NR(新无线)Uu，在relay UE和remote UE之间的PC5上使用NR边链路。
应该注意，上面对技术背景的介绍只是为了方便对本申请的技术方案进行清楚、完整的说明，并方便本领域技术人员的理解而阐述的。不能仅仅因为这些方案在本申请的背景技术部分进行了阐述而认为上述技术方案为本领域技术人员所公知。
发明内容
为了支持SL中继通信，在R17SL中继(relay)的协议栈中，引入了适应层(adaptation layer)，在适应层的头(header)中可以加入与远端终端设备有关的标识以及其Uu无线承载的标识，以便中继终端设备的服务基站可以识别远端终端设备，但目前还没有解决如何分配与远端终端设备有关的标识的方法。
为了解决上述问题的至少一种或其它类似问题，本申请实施例提供了一种信息发送方法、信息接收方法、装置和系统。
根据本申请实施例的一方面，提供一种信息接收装置，配置于第一终端设备，其中，该装置包括：
处理单元，其与至少一个第二终端设备建立连接；
第一发送单元，其向网络设备发送第一标识信息，所述第一标识信息用于指示所 述至少一个第二终端设备相关的第一标识；
第一接收单元，其接收所述网络设备发送的第二标识信息，所述第二标识信息用于指示所述至少一个第二终端设备的第二标识。
根据本申请实施例的一方面，提供一种信息发送装置，配置于网络设备，其中，该装置包括：
第三接收单元，其接收第一终端设备发送的第一标识信息，所述第一标识信息用于指示所述至少一个与所述第一终端设备连接的第二终端设备相关的第一标识；
第三发送单元，其向所述第一终端设备发送第二标识信息，所述第二标识信息用于指示至少一个所述第二终端设备的第二标识。
根据本申请实施例的一方面，提供一种通信系统，包括前述一方面所述的网络设备和/或前述一方面所述的第一终端设备。
本申请实施例的有益效果之一在于：第二终端设备的标识可以被第一终端设备的服务网络设备配置，以便第一终端设备在转发第二终端设备的数据(例如RRC消息和用户面数据等)时可以使用该标识，有助于第二终端设备的RRC消息和用户面数据被网络设备正确识别。
参照后文的说明和附图，详细公开了本申请的特定实施方式，指明了本申请的原理可以被采用的方式。应该理解，本申请的实施方式在范围上并不因而受到限制。在所附权利要求的精神和条款的范围内，本申请的实施方式包括许多改变、修改和等同。
针对一种实施方式描述和/或示出的特征可以以相同或类似的方式在一个或更多个其它实施方式中使用，与其它实施方式中的特征相组合，或替代其它实施方式中的特征。
应该强调，术语“包括/包含”在本文使用时指特征、整件、步骤或组件的存在，但并不排除一个或更多个其它特征、整件、步骤或组件的存在或附加。
附图说明
在本申请实施例的一个附图或一种实施方式中描述的元素和特征可以与一个或更多个其它附图或实施方式中示出的元素和特征相结合。此外，在附图中，类似的标号表示几个附图中对应的部件，并可用于指示多于一种实施方式中使用的对应部件。
所包括的附图用来提供对本申请实施例的进一步的理解，其构成了说明书的一部 分，用于例示本申请的实施方式，并与文字描述一起来阐释本申请的原理。显而易见地，下面描述中的附图仅仅是本申请的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其它的附图。在附图中：
图1是remote UE和relay UE应用场景示意图；
图2至图4是终端设备-网络设备中继场景中协议栈的示意图；
图5是终端设备-网络设备中继场景中建立连接进行上下行传输示意图；
图6是本申请实施例的信息发送方法的一个示意图；
图7是本申请实施例的信息接收方法的一个示意图；
图8至图11是本申请实施例终端设备-网络设备中继场景中上下行传输方法示意图；
图12是本申请实施例的信息发送方法的一个示意图；
图13是本申请实施例的信息接收方法的一个示意图；
图14是本申请实施例的信息收发方法的一个示意图；
图15是本申请实施例的信息收发方法的一个示意图；
图16是本申请实施例的信息发送方法的一个示意图；
图17至图18是本申请实施例的终端设备-网络设备中继场景中切换方法示意图；
图19是本申请实施例的信息发送方法的一个示意图；
图20是本申请实施例的信息接收方法的一个示意图；
图21是本申请实施例的信息收发方法的一个示意图；
图22是本申请实施例的信息接收装置的一个示意图；
图23是本申请实施例的信息接收装置的一个示意图；
图24是本申请实施例的信息发送装置的一个示意图；
图25是本申请实施例的信息收发装置的一个示意图；
图26是本申请实施例的信息收发装置的一个示意图；
图27是本申请实施例的信息发送装置的一个示意图；
图28是本申请实施例的信息发送装置的一个示意图；
图29是本申请实施例的信息接收装置的一个示意图；
图30是本申请实施例的通信系统的一个示意图；
图31是本申请实施例的终端设备的一个示意图；
图32是本申请实施例的网络设备的一个示意图。
具体实施方式
参照附图，通过下面的说明书，本申请的前述以及其它特征将变得明显。在说明书和附图中，具体公开了本申请的特定实施方式，其表明了其中可以采用本申请的原则的部分实施方式，应了解的是，本申请不限于所描述的实施方式，相反，本申请包括落入所附权利要求的范围内的全部修改、变型以及等同物。
在本申请实施例中，术语“第一”、“第二”等用于对不同元素从称谓上进行区分，但并不表示这些元素的空间排列或时间顺序等，这些元素不应被这些术语所限制。术语“和/或”包括相关联列出的术语的一种或多个中的任何一个和所有组合。术语“包含”、“包括”、“具有”等是指所陈述的特征、元素、元件或组件的存在，但并不排除存在或添加一个或多个其他特征、元素、元件或组件。
在本申请实施例中，单数形式“一”、“该”等包括复数形式，应广义地理解为“一种”或“一类”而并不是限定为“一个”的含义；此外术语“所述”应理解为既包括单数形式也包括复数形式，除非上下文另外明确指出。此外术语“根据”应理解为“至少部分根据……”，术语“基于”应理解为“至少部分基于……”，除非上下文另外明确指出。
在本申请实施例中，术语“通信网络”或“无线通信网络”可以指符合如下任意通信标准的网络，例如新无线(NR，New Radio)、长期演进(LTE，Long Term Evolution)、增强的长期演进(LTE-A，LTE-Advanced)、宽带码分多址接入(WCDMA，Wideband Code Division Multiple Access)、高速报文接入(HSPA，High-Speed Packet Access)等等。
并且，通信系统中设备之间的通信可以根据任意阶段的通信协议进行，例如可以包括但不限于如下通信协议：1G(generation)、2G、2.5G、2.75G、3G、4G、4.5G以及未来的5G、6G等等，和/或其他目前已知或未来将被开发的通信协议。
在本申请实施例中，术语“网络设备”例如是指通信系统中将终端设备接入通信网络并为该终端设备提供服务的设备。网络设备可以包括但不限于如下设备：基站(BS，Base Station)、接入点(AP、Access Point)、发送接收点(TRP，Transmission Reception Point)、广播发射机、移动管理实体(MME、Mobile Management Entity)、 网关、服务器、无线网络控制器(RNC，Radio Network Controller)、基站控制器(BSC，Base Station Controller)等等。
其中，基站可以包括但不限于：节点B(NodeB或NB)、演进节点B(eNodeB或eNB)以及5G基站(gNB)，等等，此外还可包括远端无线头(RRH，Remote Radio Head)、远端无线单元(RRU，Remote Radio Unit)、中继(relay)或者低功率节点(例如femto、pico等等)。并且术语“基站”可以包括它们的一些或所有功能，每个基站可以对特定的地理区域提供通信覆盖。术语“小区”可以指的是基站和/或其覆盖区域，这取决于使用该术语的上下文。
在本申请实施例中，术语“用户设备”(UE，User Equipment)例如是指通过网络设备接入通信网络并接收网络服务的设备，也可以称为“终端设备”(TE，Terminal Equipment)。终端设备可以是固定的或移动的，并且也可以称为移动台(MS，Mobile Station)、终端、用户、用户台(SS，Subscriber Station)、接入终端(AT，Access Terminal)、站，等等。
其中，终端设备可以包括但不限于如下设备：蜂窝电话(Cellular Phone)、个人数字助理(PDA，Personal Digital Assistant)、无线调制解调器、无线通信设备、手持设备、机器型通信设备、膝上型计算机、无绳电话、智能手机、智能手表、数字相机，等等。
再例如，在物联网(IoT，Internet of Things)等场景下，终端设备还可以是进行监控或测量的机器或装置，例如可以包括但不限于：机器类通信(MTC，Machine Type Communication)终端、车载通信终端、设备到设备(D2D，Device to Device)终端、机器到机器(M2M，Machine to Machine)终端，等等。
在本申请实施例中，Relay UE表示可以与网络设备直接通信的可以进行中继的终端设备(UE-to-Network Relay UE)，Remote UE表示需要经由Relay UE中继才能与网络设备进行通信的终端设备。
在本申请实施例中，信令无线承载SRB包括SRB0，SRB1，SRB2等。信令无线承载是用来传输RRC和NAS消息的无线承载。SRB0传输使用公共控制信道(common control channel，CCCH)逻辑信道的RRC消息(例如RRC建立请求RRC setup request或RRC建立RRC setup或RRC拒绝RRC reject或RRC重建立请求RRC re-establishment Request或RRC恢复请求RRC resume request)。SRB1传输RRC消息 (可能包含捎带(piggybacked)的NAS消息)和SRB2建立之前的NAS消息，使用专用控制信道(dedicated control channel，DCCH)逻辑信道。SRB2传输NAS消息和包含了日志测量消息的RRC消息，使用DCCH逻辑信道。SRB2比SRB1的优先级低，可以在接入层(access stratum，AS)安全激活之后由网络配置。
图2和图3是层2(Layer-2)终端设备-网络设备中继(UE-to-Network Relay)场景中控制面协议栈示意图，图4是层2终端设备-网络设备中继场景中用户面协议栈示意图，目前，在PC5接口，可以支持适应层(例如图中ADAPT)，只用于承载映射(bearer mapping)。如图3和图4所示，在Uu接口，对remote UE的非SRB0的Uu无线承载的上下行传输，remote UE的标识和它的Uu无线承载的标识信息被包括在适应层的header中。如图2所示，对remote UE的SRB0的上下行传输，在PC5接口，适应层不出现(适用)。在Uu接口，对remote UE的SRB0的上下行传输，适应层都出现(适用)。此外，Relay UE和Remote UE在PC5接口的协议栈包括物理层PHY，PHY层之上的介质访问控制MAC层(提供包过滤、逻辑信道优先级处理、调度请求、数据复用和解复用、逻辑信道和传输信道之间的映射等)，MAC层之上的无线链路层控制协议RLC层，以及RLC层之上的无线资源控制层PC5-RRC层(PC5接口上的RRC信令交互)，其中，PHY以传输信道的方式为MAC层提供服务，MAC层以逻辑信道的方式为RLC层提供服务。此外，Relay UE还通过NR Uu接口协议栈与gNB进行通信，Remote UE的非接入层(Non-Access Stratum，NAS)与核心网中的NAS层对等。
图5是终端设备-网络设备中继场景中建立连接进行上下行传输示意图，如图5所示，remote UE与relay UE之间建立连接后，再通过relay UE与网络设备建立RRC连接，然后可以进行上下行传输，目前，remote UE发送的第一条RRC消息(例如RRC建立请求RRC setup request或RRC重建立请求RRC re-establishment request或RRC恢复请求RRC resume request)在SRB0上承载，SRB0在Uu接口上会使用适应层，在适应层的头(header)中可以加入与远端终端设备有关的标识，以便中继终端设备的服务基站可以识别远端终端设备，但目前还没有解决如何分配与远端终端设备有关的标识的方法。
在本申请实施例中，远端终端设备在初始接入过程中，或者切换过程中，都需要在适应层的头(header)中加入与远端终端设备有关的标识以及其Uu无线承载的标 识，以便中继终端设备的服务基站(初始接入的基站或切换后的目标基站)可以识别远端终端设备，以下结合第一方面和第二方面的实施例说明在初始接入过程中如何分配与远端终端设备有关的标识，结合第三方面至第五方面的实施例说明在切换过程中如何分配与远端终端设备有关的标识。
下面结合附图对本申请的各种实施方式进行说明。这些实施方式只是示例性的，不是对本申请的限制。
第一方面的实施例
本申请实施例提供一种信息发送方法，应用于第一终端设备侧，该第一终端设备可以是Relay UE，该第二终端设备可以是Remote UE。
图6是该信息发送方法示意图，如图6所示，该方法包括：
601，该第一终端设备与至少一个第二终端设备建立连接；
602，该第一终端设备向网络设备发送第一标识信息，该第一标识信息用于指示该至少一个第二终端设备相关的第一标识。
在一些实施例中，第一终端设备与至少一个第二终端设备建立连接可以包括第二终端设备执行中继发现、中继选择或中继重选、或第一终端设备与第二终端设备之间建立单播链路(unicast link)等过程，该连接是PC5连接或边链路(sidelink，SL)连接，例如PC5-RRC连接或PC5-AS(Access Stratum，接入层)连接或PC5单播链路(PC5 unicast link)，关于该中继发现过程、中继选择或中继重选的过程、单播链路建立过程可以参考现有技术，此处不再赘述。
在一些实施例中，该第一终端设备可以与一个或多个第二终端设备建立连接，在与每个第二终端设备建立连接的过程中，第一终端设备可以获取到该第二终端设备相关的第一标识，该第一标识可以是第二终端设备的目的地标识(destination ID)，例如层2标识(layer-2 ID，L2 ID)，或者为了节省开销，该第一标识还可以是比该目的地标识长度更短的第一索引，该第一标识表示第二终端设备在PC5接口中通信(与第一终端设备通信)的标识，用于显式的指示第二终端设备。和/或，该第一标识还可以是第一终端设备与第二终端设备之间的PC5单播链路的标识(PC5 unicast link ID)，例如，第一终端设备与一个第二终端设备之间可以建立一条或多于一条PC5单播链路，一个PC5 unicast link ID唯一地标识一条PC5单播链路，对应第二终端设备 的目的地标识或第一索引，即隐式地指示第二终端设备(的目的地标识或第一索引)；和/或，该第一标识还可以是第一终端设备与第二终端设备之间的PC5-RRC连接的标识(PC5-RRC connection ID)，例如，第一终端设备与一个第二终端设备之间可以建立一个或多于一个PC5 RRC连接，一个PC5-RRC connection ID唯一地标识一PC5-RRC连接，对应第二终端设备的目的地标识或第一索引，即隐式地指示第二终端设备(的目的地标识或第一索引)；和/或，该第一标识可以是第一终端设备与第二终端设备之间的源标识和目的地标识对(a pair(s)of source layer-2 ID and destination L2 ID)，例如是第一终端设备的L2 ID与第二终端设备的L2 ID的对(pair)等，本实施例并不以此作为限制。
例如，该第一标识可以由所述第一终端设备和所述第二终端设备之间的边链路信令消息或边链路RRC消息承载；例如，该边链路信令消息可以是发现消息或直接通信请求消息(direct communication request)或直接通信接受消息(direct communication accept)，该边链路RRC消息可以是RRC重配置边链路消息(RRCReconfigurationSidelink)消息或RRC重配置完成边链路消息(RRCReconfigurationCompleteSidelink)消息等，此处不再一一举例。在一些实施例中，如果使用第一索引代替目的地表示的传输，第一终端设备或第二终端设备还需要预先分配该第一索引，关于该第一索引的分配相关请参考第六方面的实施例，此处不再赘述。
在一些实施例中，该第一标识信息用于指示一个与该第一终端设备建立连接的第二终端设备相关的第一标识，该一个第二终端设备是与该第一终端设备新建立连接的终端设备，或者该第一标识信息用于指示所有与该第一终端设备建立连接的第二终端设备相关的第一标识。关于该第一标识信息承载方式和格式将在后述(一)和(二)进行详细说明。
在一些实施例中，该方法还可以包括：
603，该第一终端设备接收该网络设备发送的第二标识信息，该第二标识信息用于指示所述至少一个第二终端设备的第二标识。
在一些实施例中，该网络设备接收到该第一标识信息后，可以根据该第一标识信息分配第二标识，并生成第二标识信息，将为该至少一个第二终端设备(第一标识信息标识获知的)分配的第二标识通知给第一终端设备，该第二标识是所述第二终端设 备的本地/临时标识，该本地/临时标识可以被包括在Uu接口adaptation layer的头(header)中。关于该第二标识信息承载方式和格式将在后述(一)和(二)进行详细说明。
在一些实施例中，所述本地/临时标识表示第二终端设备在Uu接口中通信的标识，包括以下至少一种：
1)所述第二终端设备的第二索引，所述第二索引用于唯一标识与所述第一终端设备有连接关系的第二终端设备；即该第二索引在与该第一终端设备有连接(例如PC5-RRC连接)的第二终端设备内唯一，例如假设第一终端设备与3个第二终端设备有连接，则可以采用3个第二索引来标识这3个第二终端设备，一个第二索引用于标识一个第二终端设备，例如可以n比特表示，n大于等于3小于等于8，或者，也可以用整数表示(例如0～16的任一整数)等；
2)所述第二终端设备的小区无线网络临时标识C-RNTI；
3)所述第二终端设备的目的地标识的一部分；例如，该目的地标识是24bit表示的，该第二标识可以是该24bit的部分比特，例如高X bit或低X bit等，X可以是取值2到5的整数等，本实施例并不以此作为限制。
在一些实施例中，为了使得第一终端设备确定第一标识和第二标识的对应关系，即为了使第一终端设备获知网络设备分配的第二标识分别对应哪一个第二终端设备(第一标识)，该网络设备可以显式或隐式的指示该对应关系，例如网络设备在发送第二标识信息的同时指示与至少一个第二标识对应的第一标识(显式指示)；或者，在该第二标识信息中第二标识的排列顺序与所述第一标识信息中所述至少一个第二终端设备相关的第一标识的出现顺序相同(隐式指示)，该第一标识的出现顺序包括在同一消息中的出现顺序，或者在不同消息中的出现顺序。例如，在与第一终端设备连接的第二终端设备为多个时，在第一标识信息中包括了该多个第二终端设备相关的第一标识，该第二标识的出现顺序与该第一标识的出现顺序一一对应，或者，在第一标识信息中包括了一个第二终端设备相关的第一标识，但第一终端设备发送了多于一个上行消息，每个上行消息承载一个第一标识信息时，该第二标识的出现顺序与接收该多个上行消息的顺序对应，也即与每个上行消息中该第一标识的出现顺序一一对应，或者，第一标识信息包括一个第二终端设备相关的第一标识，网络设备在每次收到一个第一标识时分配一个第二标识，第一终端设备在收到一个第二标识后，再发送下一 个第一标识信息。关于第二标识的配置方式将在后述(一)或(二)中进一步说明。
在一些实施例中，该方法还可以包括：(未图示)
该第一终端设备使用或存储或保留该第一标识和该第二标识的对应关系。
例如，该第一终端设备根据上述网络设备通过显式或隐式的方式指示的对应关系即可确定网络设备分配的第二标识对应哪一个第二终端设备(第一标识)，该第一终端设备在收到第二标识信息后，可以使用或存储或保留该第一标识和该第二标识的对应关系，例如用于后续该第二终端设备的上行和/或下行数据的中继传输。
在一些实施例中，该第一终端设备可以处于RRC连接(RRC_CONNECTED)模式，或者也可以处于RRC空闲模式(RRC_IDLE)或RRC非激活(RRC_INACTIVE)模式，以下分别进行说明。
(一)第一终端设备处于RRC连接模式
在一些实施例中，由于该第一终端设备处于RRC连接模式，因此，该第一终端设备可以直接向网络设备发送上行消息，在602中，可以使用该上行消息承载该第一标识信息，例如，该上行消息可以是边链路UE信息(sidelink UE information，SUI)消息，以下以SUI为例进行说明，但本申请并不以此作为限制。
在一些实施例中，在满足第一触发条件时，该第一终端设备向该网络设备发送第一标识信息(或者说在满足第一触发条件时，该第一终端设备向网络设备发送该SUI)，该第一触发条件包括以下条件的至少之一：该第一终端设备与该第二终端设备建立连接；该第一终端设备与该第二终端设备之间传输边链路能力消息；该第一终端设备接收到该第二终端设备发送的针对第二终端设备的第一RRC消息。
例如，在现有技术中，在对边链路业务感兴趣时，可以触发SUI消息的发送，在本申请实施例中，在该第一终端设备与该第二终端设备建立连接和/或该第一终端设备与该第二终端设备之间传输边链路能力消息和/或该第一终端设备接收到该第二终端设备发送的针对第二终端设备的第一RRC消息时，也可以触发SUI消息的发送。
例如，在操作601中建立连接(如前面所述)后，即可以触发SUI消息的发送；
或者，在建立连接后，第一终端设备与第二终端设备之间通过PC5-RRC消息传输边链路能力(sidelink capability)后，触发SUI消息的发送，其中，可以是第一终端设备通知第二终端设备关于第一终端设备的边链路能力和/或中继能力，也可以是第二终端设备通知第一终端设备关于第二终端设备的边链路能力和/或作为第二终端 设备的能力，本申请并不以此作为限制；
或者，在建立连接后该第一终端设备接收到该第二终端设备发送的针对第二终端设备的第一RRC消息，触发SUI消息的发送，该第一RRC消息可以是建立连接后第二终端设备向第一终端设备发送的第一条RRC消息或者是采用特定SRB(例如SRB0)发送的RRC消息或者是采用特定层2配置(例如采用SRB0对应的层2配置)发送的RRC消息，针对该第二终端设备的第一RRC消息是指该RRC消息由第二终端设备的RRC生成(针对上行)，或者由该第二终端设备的RRC接收或解析或处理(针对下行)，例如，该第一RRC消息包括RRC setup request或RRC re-establishment request或RRC resume request消息等，本申请并不以此作为限制。
在满足触发条件时，在602中，第一终端设备可以向网络设备发送SUI，其中，包括第一标识信息，例如：该SUI使用抽象语法标记ASN.1数据格式可以表示为：
Figure PCTCN2021124652-appb-000001
或
Figure PCTCN2021124652-appb-000002
在上述实施例中，该第一标识信息sl-RemoteUEList-r16中包括当前所有的建立连接或新建立连接的第二终端设备(一个或多个)相关的第一标识(例如sl-DestinationIdentity-r16)，该第一标识的排列(出现)顺序可以按照与第一终端设备建立连接的时间顺序排列，但本申请实施例并不以此作为限制。
例如：该SUI还可以使用抽象语法标记ASN.1数据格式表示为：
Figure PCTCN2021124652-appb-000003
Figure PCTCN2021124652-appb-000004
在上述实施例中，该第一标识信息SL-TxResourceReq-r16中包括当前所有的建立连接或新建立连接的第二终端设备(例如sl-RemoteUE用于指示一个destination ID是否对应远端终端设备，即第二终端设备)相关的第一标识(例如sl-DestinationIdentity-r16)。
在一些实施例中，在603中，该第二标识信息可以由针对第一终端设备的第四RRC消息承载，针对该第一终端设备的第四RRC消息是指由该第一终端设备的RRC接收或解析或处理，例如，第四RRC消息包括RRC reconfiguration或RRC re-establishment或RRC resume消息等。
在一些实施例中，该第四RRC消息中，可以包括第二标识信息，在该第二标识信息中第二标识的排列顺序与所述第一标识信息中所述至少一个第二终端设备相关的第一标识的出现顺序相同，该第一标识的出现顺序包括在同一SUI中的出现顺序，或者在不同SUI消息中的出现顺序。例如，在与第一终端设备连接的第二终端设备为多于一个时，在第一标识信息中包括了该多于一个第二终端设备相关的第一标识，该第二标识的出现顺序与该第一标识的出现顺序一一对应，或者，在第一标识信息中包括了一个第二终端设备相关的第一标识，但第一终端设备发送了多于一个SUI消息，每个SUI消息承载一个第一标识信息时，该第二标识的出现顺序与接收该多于一个SUI消息的顺序对应，也即与每个SUI消息中该第一标识的出现顺序一一对应。由此，通过该隐式的方式指示第二标识和第一标识的对应关系。
在一些实施例中，该第四RRC消息中，还可以同时指示第二标识以及与第二标识对应的第一标识，由此，通过该显式的方式指示第二标识和第一标识的对应关系。
在一些实施例中，第一终端设备在接收到网络设备分配的第二标识后，可以在适应层的头中加入该第二标识，具体可以参考现有技术，关于第一终端设备、第二终端设备、网络设备之间的信息交互过程将在第二方面的实施例进行说明。
(二)第一终端设备处于RRC空闲或非激活模式
在一些实施例中，在第一终端设备处于RRC空闲或非激活模式时，可以进入RRC 连接模式后，再用(一)中的方式发送第一标识信息以及接收第二标识信息，例如，该方法还可以包括：第一终端设备接收该第二终端设备发送的针对第二终端设备的第一RRC消息，并进入RRC连接模式，在进入RRC连接模式后，第一终端设备可以使用(一)中的方式发送第一标识信息以及接收第二标识信息等，关于该第一RRC消息的实施方式可以参考(一)，此处不再赘述。
在一些实施例中，在第一终端设备处于RRC空闲或非激活模式时，可以执行RRC连接建立过程或RRC重新开始(RRC resume)过程，并在该RRC连接建立或RRC重新开始的过程中发送该第一标识信息，以下进行说明。
例如，在602中，可以使用针对该第一终端设备的第二RRC消息承载该第一标识信息，例如，针对该第一终端设备的第二RRC消息是指该RRC消息由第一终端设备的RRC生成(针对上行)，或者由该第一终端设备的RRC接收或解析或处理(针对下行)，该第二RRC消息可以是该第一终端设备在自己的RRC连接建立过程或RRC重新开始过程中的向网络设备发送的RRC消息，包括RRC setup request或RRC setup complete或RRC resume request或RRC resume complete等。
例如，在603中，该第二标识信息可以由针对第一终端设备的第三RRC消息承载，针对该第一终端设备的第三RRC消息是指由该第一终端设备的RRC接收或处理，例如，第三RRC消息包括RRC setup或RRC resume或RRC reconfiguration消息等。
在一些实施例中，该第三RRC消息中，可以包括第二标识信息，在该第二标识信息中第二标识的排列顺序与所述第一标识信息中所述至少一个第二终端设备相关的第一标识的出现顺序相同，该第一标识的出现顺序包括在同一第二RRC消息中的出现顺序。例如，在与第一终端设备连接的第二终端设备为多于一个时，在第一标识信息中包括了该多于一个第二终端设备相关的第一标识，该第二标识的出现顺序与该第一标识的出现顺序一一对应。由此，通过该隐式的方式指示第二标识和第一标识的对应关系。
在一些实施例中，该第三RRC消息中，还可以同时指示第二标识以及与第二标识对应的第一标识，由此，通过该显式的方式指示第二标识和第一标识的对应关系。
例如，在第二RRC消息是RRC setup/resume request时，该第三RRC消息可以是RRC setup/resume或RRC reconfiguration，或者，该第二RRC消息是RRC setup/resume complete时，该第三RRC消息可以是RRC reconfiguration，此处不再一 一举例。
在一些实施例中，第一终端设备在接收到网络设备分配的第二标识后，可以在适应层的头中加入该第二标识，具体可以参考现有技术，关于第一终端设备、第二终端设备、网络设备之间的信息交互过程将在第二方面的实施例进行说明。
由上述实施例可知，第二终端设备的标识可以被第一终端设备的服务网络设备配置，以便第一终端设备在转发第二终端设备的数据(例如RRC消息和用户面数据等)时可以使用该标识，有助于第二终端设备的RRC消息和用户面数据被网络设备正确识别。
第二方面的实施例
本申请实施例提供一种信息接收方法，应用于网络设备侧。
图7是该信息接收方法示意图，如图7所示，该方法包括：
701，网络设备接收第一终端设备发送的第一标识信息，该第一标识信息用于指示所述至少一个与所述第一终端设备连接的第二终端设备相关的第一标识。
在一些实施例中，该701的实施方式与第一方面的实施例中602对应，关于该第一标识，第一标识信息的承载方式以及格式等请参考第一方面的实施例，此处不再赘述。
在一些实施例中，该方法还可以包括：
702，网络设备向该第一终端设备发送第二标识信息，该第二标识信息用于指示该至少一个第二终端设备的第二标识。
在一些实施例中，该702的实施方式与第一方面的实施例中603对应，关于该第二标识，第二标识信息的承载方式以及格式等请参考第一方面的实施例，此处不再赘述。
在一些实施例中，该方法还可以包括：(未图示)网络设备使用或存储该第一标识和第二标识的对应关系，或者，网络设备还可以使用或存储该第一标识、第二标识以及分配的C-RNTI的对应关系。
图8至图11是本申请实施例中终端设备-网络设备中继场景中上下行传输方法示意图，以下结合附图8至11分别进行说明。
图8是在第一终端设备处于RRC连接模式下的方法示意图，如图8所示，该方 法包括：
801，第一终端设备与第二终端设备建立连接；
802，第二终端设备向第一终端设备发送第一RRC消息(例如使用PC5接口上默认的层2配置发送该第一RRC消息)，以通过第一终端设备与网络设备建立连接；
803，满足第一触发条件，触发SUI的发送；
804，该第一终端设备向网络设备发送该SUI，该SUI承载第一标识信息；
805，网络设备向第一终端设备发送第四RRC消息，该第四RRC消息承载第二标识信息；
806，第一终端设备将该第一RRC消息转发至网络设备，其中，在适应层的头中包括该第二标识；
807，在网络设备接受该第二终端设备的连接建立请求时，向第一终端设备回复针对第二终端设备的RRC setup消息(第五RRC消息)，该消息在适应层的头中包括该第二标识，可选的还可以包括第二终端设备的C-RNTI；
808，第一终端设备向第二终端设备转发该RRC setup消息(例如使用PC5接口上默认的层2配置转发该第五RRC消息)；
809，第二终端设备和网络设备之间经由第一终端设备收发上行和/或下行无线承载的数据，其中，在PC5接口可以使用源层2或目的地层2标识进行上行和/或下行无线承载的数据的发送和/或接收，在PC5接口的适应层的头文件中可以包括承载的标识，在Uu接口，上行和/或下行无线承载的数据在Uu接口的适应层的头中包括第二标识和Uu无线承载标识，以便网络设备识别第二终端设备，即确定上下行传输对应哪一个第二终端设备。
图9是在第一终端设备处于RRC空闲或非激活模式下的方法示意图，如图9所示，该方法包括：
901，第一终端设备与第二终端设备建立连接；
902，第二终端设备向第一终端设备发送第一RRC消息(例如使用PC5接口上默认的层2配置发送该第一RRC消息)，以通过第一终端设备与网络设备建立连接；
903，第一终端设备执行其自己的RRC连接建立过程或RRC resume过程，进入RRC连接模式，具体可以参考现有技术，此处不再赘述。
904，满足第一触发条件，触发SUI的发送；
905，该第一终端设备向网络设备发送该SUI，该SUI承载第一标识信息；
906，网络设备向第一终端设备发送第四RRC消息，该第四RRC消息承载第二标识信息；
907，第一终端设备将该第一RRC消息转发至网络设备，其中，在适应层的头中包括该第二标识；
908，在网络设备接受该第二终端设备的连接建立请求时，向第一终端设备回复针对第二终端设备的RRC setup消息(第五RRC消息)，该消息在适应层的头中包括该第二标识，可选的还可以包括第二终端设备的C-RNTI；
909，第一终端设备向第二终端设备转发该RRC setup消息(例如使用PC5接口上默认的层2配置转发该第五RRC消息)；
910，第二终端设备和网络设备之间经由第一终端设备收发上行和/或下行无线承载的数据，其中，在PC5接口可以使用源层2和目的地层2标识进行上行和/或下行无线承载的数据的发送和/或接收，在PC5接口的适应层的头文件中可以包括承载的标识，在Uu接口，上行和/或下行无线承载的数据在Uu接口的适应层的头中包括第二标识和第二终端设备的Uu无线承载标识，以便网络设备识别第二终端设备，即确定上下行传输对应哪一个第二终端设备。
图10是在第一终端设备处于RRC空闲或非激活模式下的方法示意图，如图10所示，该方法包括：
1001，第一终端设备与第二终端设备建立连接；
1002，第二终端设备向第一终端设备发送第一RRC消息(例如使用PC5接口上默认的层2配置发送该第一RRC消息)，以通过第一终端设备与网络设备建立连接；
1003，第一终端设备执行其自己的RRC连接建立过程或RRC resume过程，向网络设备发送第二RRC消息，该第二RRC消息中承载第一标识信息，该第二RRC消息是RRC setup request消息或RRC resume request消息；
1004，网络设备收到该第二RRC消息后向第一终端设备发送第三RRC消息，该第三RRC消息承载该第二标识信息，该第三RRC消息是RRC setup消息或RRC resume消息；
1005，第一终端设备向网络设备发送针对其自身的RRC setup complete消息或RRC resume complete消息，以完成其自身的RRC连接过程或RRC resume过程；
1006，网络设备向第一终端设备发送RRC reconfiguration消息；
1007，第一终端设备将该第一RRC消息转发至网络设备，其中，在适应层的头中包括该第二标识；
1008，在网络设备接受该第二终端设备的连接建立请求时，向第一终端设备回复针对第二终端设备的RRC setup消息(第五RRC消息)，该消息在适应层的头中包括该第二标识，可选的还可以包括第二终端设备的C-RNTI；
1009，第一终端设备向第二终端设备转发该针对第二终端设备的RRC setup消息(例如使用PC5接口上默认的层2配置转发该第五RRC消息)；
1010，第二终端设备和网络设备之间经由第一终端设备收发上行和/或下行无线承载的数据，其中，在PC5接口可以使用源层2和目的地层2标识进行上行和/或下行无线承载的数据的发送和/或接收，在PC5接口的适应层的头文件中可以包括承载的标识，在Uu接口，上行和/或下行无线承载的数据在Uu接口的适应层的头中包括第二标识和第二终端设备的Uu无线承载标识，以便网络设备识别第二终端设备，即确定上下行传输对应哪一个第二终端设备。
图11是在第一终端设备处于RRC空闲或非激活模式下的方法示意图，如图9所示，该方法包括：
1101，第一终端设备与第二终端设备建立连接；
1102，第二终端设备向第一终端设备发送第一RRC消息(例如使用PC5接口上默认的层2配置发送该第一RRC消息)，以通过第一终端设备与网络设备建立连接；
1103，第一终端设备执行其自己的RRC连接建立过程或RRC resume过程，向网络设备发送针对其自身的RRC setup/resume request消息；
1104，网络设备收到该RRC setup/resume request消息后向第一终端设备发送针对第一终端设备的RRC setup/resume消息；
1105，第一终端设备向网络设备发送第二RRC消息，该第二RRC消息中承载第一标识信息，该第二RRC消息是RRC setup/resume complete消息；
1106，网络设备向第一终端设备发送第三RRC消息，该第三RRC消息中承载第二标识信息，该第三RRC消息是RRC reconfiguration消息；
1107，第一终端设备将该第一RRC消息转发至网络设备，其中，在适应层的头中包括该第二标识；
1108，在网络设备接受该第二终端设备的连接建立请求时，向第一终端设备回复针对第二终端设备的RRC setup消息(第五RRC消息)，该消息在适应层的头中包括该第二标识，可选的还可以包括第二终端设备的C-RNTI；
1109，第一终端设备向第二终端设备转发该针对第二终端设备的RRC setup消息(例如使用PC5接口上默认的层2配置转发该第五RRC消息)；
1110，第二终端设备和网络设备之间经由第一终端设备收发上行和/或下行无线承载的数据，其中，在PC5接口可以使用源层2或目的地层2标识进行上行和/或下行无线承载的数据的发送和/或接收，在PC5接口的适应层的头文件中可以包括承载的标识，在Uu接口，上行和/或下行无线承载的数据在Uu接口的适应层的头中包括第二标识和第二终端设备的Uu无线承载标识，以便网络设备识别第二终端设备，即确定上下行传输对应哪一个第二终端设备。
在上述实施例中，801-805,901-905,1001-1005,1101-1105的实施方式可以参考第一方面的实施例，另外，操作802可以在803前执行，也可以在803后执行，或者804或者805后执行，本申请实施例并不以此作为限制。
由上述实施例可知，第二终端设备的标识可以被第一终端设备的服务网络设备配置，以便第一终端设备在转发第二终端设备的数据(例如RRC消息和用户面数据等)时可以使用该标识，有助于第二终端设备的RRC消息和用户面数据被网络设备正确识别。
以上第一方面和第二方面的实施例说明在初始接入过程中如何分配与远端终端设备有关的标识，以下结合第三方面至第五方面的实施例说明在切换过程中如何分配与远端终端设备有关的标识。在切换过程中，第二标识可以被网络设备配置或重配置。
第三方面的实施例
本申请实施例提供一种信息发送方法，应用于网络设备(以下是指目标网络设备)侧。
图12是该信息发送方法示意图，如图12所示，该方法包括：
1201，网络设备确定第二终端设备切换至通过第一终端设备与所述网络设备连接；
1202，网络设备向该第一终端设备发送第二标识信息，该第二标识信息用于指示所述第二终端设备的第二标识。
在一些实施例中，在1201中，第二终端设备的切换包括第一切换或第二切换，该第一切换是指该第二终端设备通过Uu接口与源网络设备连接(直接链路direct链路)切换至该第二终端设备通过第一终端设备与目标网络设备连接(间接链路indirect链路)；该第二切换是指该第二终端设备通过源第一终端设备与源网络设备连接切换至通过目标第一终端设备与目标网络设备切换(indirect链路至indirect链路)，该源网络设备与目标网络设备可以相同或不同，本申请实施例并不以此作为限制，网络设备确定第二终端设备是否/如何切换可以是根据第二终端设备上报的测量报告确定的，具体可以参考现有技术，此处不再赘述。
在一些实施例中，由于要进行切换，在1202中，网络设备可以为第二终端设备分配新的第二标识，并通知第一终端设备(目标第一终端设备)该新分配的第二标识，该第二标识的含义可以参考第一方面的实施例，例如，该第二标识信息可以通过第一RRC重配置消息承载，这时第一终端设备和第二终端设备可以建立了连接，也可以还未建立连接，以下分别进行说明。
(一)第一终端设备和第二终端设备之间的连接在切换前还未建立
在该实施例中，该网络设备可以在第二终端设备切换完成前，向该第一终端设备发送第二标识信息，由于切换时第一终端设备和第二终端设备之间还未建立连接，第一终端设备并不了解第二终端设备相关的第一标识，因此也不知道分配的第二标识对应哪一个第二终端设备，在该实施例中，该方法还可以包括：(未图示)
网络设备向所述第二终端设备发送所述第二标识信息。
在该实施例中，网络设备可以通过第二RRC重配置消息承载该向第二终端设备发送的第二标识信息，以便后续第一终端设备和第二终端设备建立连接过程中或之后，第一终端设备和网络设备可以确定第一标识和第二标识的对应关系，即该方法还可以包括：(未图示)
在该第一终端设备与该第二终端设备建立连接后，该网络设备接收该第一终端设备发送的第一标识信息以及对应的该第二标识信息，该第一标识信息用于指示该第二终端设备相关的第一标识，该第一标识的含义可以参考第一方面的实施例。
在该实施例中，第一终端设备和第二终端设备经过建立连接，第一终端设备即可以确定第二标识和第一标识的对应关系(具体将在第四方面的实施例说明)，该第一终端设备可以将该第一标识信息以及对应的所述第二标识信息发送给网络设备，该方 法还可以包括：网络设备使用或存储该第一标识与第二标识的对应关系。
在一些实施例中，该第一标识信息以及对应的所述第二标识信息可以由SUI消息承载，例如，其可以是所述SUI中的新增信息元sl-RemoteUEList-r16，例如该新增信息元包括第一标识和第二标识，或者被包含在边链路失败信息元sl-FailureList-r16中，或者被包含在边链路发送资源请求信息元SL-TxResourceReq-r16中。
例如，在被包含在边链路失败信息元sl-FailureList-r16中时，如果第一终端设备检测到与第二终端设备之间的边链路无线链路失败，并发送了SUI时，网络设备可以识别哪一个第二终端设备与第一终端设备之间发生了边链路无线链路识别(SL RLF)，并停止通过第一终端设备向该第二终端设备发送数据，节省了开销。
(二)第一终端设备和第二终端设备之间的连接在切换前被建立
在该实施例中，由于切换时第一终端设备和第二终端设备之间已经建立连接，也就是说，第一终端设备已经了解了第二终端设备相关的第一标识，因此，在该实施例中，该方法还可以包括：(未图示)
在该第一终端设备与该第二终端设备建立连接后，该网络设备接收该第二终端设备发送的第一标识信息，该第一标识信息用于指示该第二终端设备相关的第一标识。
在该实施例中，第二终端设备可以通过测量报告消息承载该第一标识信息，也就是说，在切换前，网络设备已经获知了第二终端设备相关的第一标识，则在1202中，该网络设备可以同时将第二标识信息以及与该第二标识对应的该第一标识通知第一终端设备，也即，该第一RRC重配置消息除了承载该第二标识信息外，还指示与该第二标识对应的第一标识，即该方法还可以包括：(未图示)网络设备使用或存储该第一标识与第二标识的对应关系。具体实施方式可以参考第二方面的实施例，此处不再赘述。
由上述实施例可知，第二终端设备的标识可以被第一终端设备的服务网络设备配置，以便第一终端设备在转发第二终端设备的数据(例如RRC消息和用户面数据等)时可以使用该标识，有助于第二终端设备的RRC消息和用户面数据被网络设备正确识别。
第四方面的实施例
本申请实施例提供一种信息接收方法，应用于第一终端设备(以下是指目标第一 终端设备)侧。
图13是该信息接收方法示意图，如图13所示，该方法包括：
1301，该第一终端设备接收网络设备发送的第二标识信息，该第二标识信息用于指示第二终端设备的第二标识，其中，该第二终端设备确定切换至通过该第一终端设备与该网络设备连接。
在一些实施例中，1301与1202的实施方式对应，此处不再赘述。
(一)第一终端设备和第二终端设备之间的连接在切换前还未建立
在一些实施例中，在1301中，可以由第一RRC重配置消息承载该第二标识信息。
在一些实施例中，该方法还可以包括：
所述第一终端设备接收所述第二终端设备发送的所述第二标识信息。
例如，所述第二终端设备发送的所述第二标识信息由所述第一终端设备和所述第二终端设备之间的边链路信令消息或边链路RRC消息承载，所述边链路信令(PC5-S)消息或边链路RRC(PC5-RRC)消息还用于指示所述第一标识，例如可以将该第一标识显式的包含在上述消息中或通过低层(例如MAC层和/或物理层)隐式的指示该第一标识。
例如，该边链路信令消息可以是发现消息或直接通信请求消息(direct communication request)或直接通信接受消息(direct communication accept)，该边链路RRC消息可以是RRC重配置边链路消息(RRCReconfigurationSidelink)消息或RRC重配置完成边链路消息(RRCReconfigurationCompleteSidelink)消息，上述消息可以是在第二终端设备和第一终端设备执行中继发现、中继选择或中继重选、或PC5unicast link建立过程中或之后发送的。也就是说，由所述第一终端设备和所述第二终端设备之间的边链路信令消息或边链路RRC消息指示第一标识和第二标识，则第一终端设备和第二终端设备经过建立连接后，第一终端设备即可以确定第二标识和第一标识的对应关系。
在一些实施例中，在所述第一终端设备与所述第二终端设备建立连接后，该方法还可以包括：
所述第一终端设备向网络设备发送第一标识信息以及对应的所述第二标识信息，所述第一标识信息用于指示所述第二终端设备相关的第一标识，该第一标识的含义可以参考第一方面的实施例。
也就是说，该第一终端设备在确定第二标识和第一标识的对应关系后，可以将该第一标识信息以及对应的所述第二标识信息发送给网络设备。该方法还可以包括：(未图示)第一终端设备使用或存储该第一标识与第二标识的对应关系。具体实施方式可以参考第二方面的实施例，此处不再赘述。
在一些实施例中，该第一终端设备发送的第一标识信息以及对应的所述第二标识信息可以由SUI消息承载，具体可以参考第三方面的实施例，此处不再赘述。
(二)第一终端设备和第二终端设备之间的连接在切换前被建立
在该实施例中，由于切换时第一终端设备和第二终端设备之间已经建立连接，也就是说，第一终端设备已经了解了第二终端设备相关的第一标识(具体可以参考第一方面的实施例)，因此，在该实施例中，在1301中，可以由第一RRC重配置消息同时指示第二标识和与其对应的第一标识，第一终端设备在接收到该第一RRC重配置消息后即可以确定第二标识和第一标识的对应关系。该方法还可以包括：(未图示)第一终端设备使用或存储该第一标识与第二标识的对应关系。具体实施方式可以参考第二方面的实施例，此处不再赘述。
第二终端设备的标识可以被第一终端设备的服务网络设备配置，以便第一终端设备在转发第二终端设备的数据(例如RRC消息和用户面数据等)时可以使用该标识，有助于第二终端设备的RRC消息和用户面数据被网络设备正确识别。
第五方面实施例
本申请实施例提供一种信息收发方法，应用于第二终端设备侧。
图14是该信息收发方法示意图，如图14所示，该方法包括：
1401，该第二终端设备向网络设备发送第一标识信息，该第一标识信息用于指示该第二终端设备相关的第一标识；和/或，
1402，该第二终端设备接收网络设备发送的第二标识信息，该第二标识信息用于指示该第二终端设备的第二标识。
在一些实施例中，1401-1402的实施方式可以参考第三方面或第四方面的实施例，此处不再赘述。
(一)第一终端设备和第二终端设备之间的连接在切换前还未建立
图15是该信息收发方法示意图，如图15所示，该方法包括：
1501，该第二终端设备接收网络设备发送的第二标识信息，该第二标识信息用于指示该第二终端设备的第二标识；
1502，该第二终端设备向该第一终端设备发送该第二标识信息。
在一些实施例中，在1501中，该第二标识信息可以由第二RRC重配置消息承载，例如包含切换到目标第一终端设备的相关信息的RRC重配置消息(例如切换命令)，关于其实施方式可以参考第三方面的实施例，此处不再赘述。
在一些实施例中，在1502中，该第二标识信息可以由所述第一终端设备和所述第二终端设备之间的边链路信令消息或边链路RRC消息承载，所述边链路信令消息或边链路RRC消息还用于指示所述第一标识，关于其实施方式可以参考第四方面的实施例，此处不再赘述。
(二)第一终端设备和第二终端设备之间的连接在切换前被建立
图16是该信息发送方法示意图，如图16所示，该方法包括：
1601，所述第二终端设备向网络设备发送第一标识信息，所述第一标识信息用于指示所述第二终端设备相关的第一标识。
在一些实施例中，在1601中，该第一标识信息可以通过测量报告消息承载，具体可以参考第三方面的实施例。
以下结合附图17至18以直接链路切换到间接链路为例说明切换方法。
图17是第一终端设备和第二终端设备之间的连接在切换前还未建立的情况下的该方法示意图，如图17所示，该方法包括：
1701，(目标)网络设备向第二终端设备发送测量配置；
1702，第二终端设备根据该测量配置进行测量，并上报测量报告，其中可以包括至少一个候选第一终端设备的标识(Relay UE ID)、第一终端设备的服务小区和边链路测量结果；
1703，网络设备根据测量报告确定第二终端设备切换至通过第一终端设备与所述网络设备连接；
1704，网络设备向第一终端设备发送用于第二终端设备切换的第一RRC重配置消息，该消息包括第二标识信息，以及用于中继的Uu和PC5 RLC配置和承载映射配置；该第一终端设备根据该第一RRC重配置消息完成与对应的PC5接口和Uu接口的RLC配置和承载映射配置；
1705，第一终端设备向网络设备发送RRC重配置完成消息(与1704对应)，具体可以参考现有技术。
1706，网络设备向第二终端设备发送针对第二终端设备的第二RRC重配置消息，例如切换至通过第一终端设备与所述网络设备连接的切换命令，该消息包括第二标识信息，以及第一终端设备的标识(Relay UE ID)、中继业务的PC5 RLC配置和相关的端到端无线承载(radio bearer)配置；该第二终端设备根据该第二RRC重配置消息确定切换至通过哪个第一终端设备与所述网络设备连接。
1707，第二终端设备和第一终端设备建立连接，具体实施方式可以参考第一方面实施例，例如，在建立连接过程中或之后，由所述第一终端设备和所述第二终端设备之间的边链路信令消息或边链路RRC消息承载第二标识信息，所述边链路信令(PC5-S)消息或边链路RRC(PC5-RRC)消息还用于指示所述第一标识。
1708，(可选)第一终端设备向网络设备发送第一标识信息以及对应的所述第二标识信息，例如，使用SUI承载该第一标识信息以及对应的第二标识信息，此处不再赘述。在第一终端设备向网络设备发送的第一标识信息以及对应的所述第二标识信息被包含在SUI消息的边链路失败信息元sl-FailureList-r16中的情况下，此步骤在边链路无线链路失败被检测到时被执行。
1709，第一终端设备使用或存储该第一标识与第二标识的对应关系。
1710，第二终端设备经由第一终端设备向网络设备发送RRC重配置完成消息(与1706对应)。
1711，(可选)第二终端设备切换完成，第二终端设备和网络设备之间经由第一终端设备收发上行和/或下行无线承载的数据，其中，在PC5接口可以使用源层2或目的地层2标识进行上行和/或下行无线承载的数据的发送和/或接收，在PC5接口的适应层的头文件中可以包括承载的标识，在Uu接口，上行和/或下行无线承载的数据在Uu接口的适应层的头中包括第二标识和第二终端设备的Uu无线承载标识，以便网络设备识别第二终端设备，即确定上下行传输对应哪一个第二终端设备。
图18是第一终端设备和第二终端设备之间的连接在切换前被建立的情况下的该方法示意图，如图18所示，该方法包括：
1801，第二终端设备与第一终端设备建立连接；
1802，(目标)网络设备向第二终端设备发送测量配置；
1803，第二终端设备根据该测量配置进行测量，并上报测量报告；在该测量报告中可以包括至少一个候选第一终端设备的标识(Relay UE ID)、第一终端设备的服务小区和边链路测量结果，还可以包括第一标识信息；
1804，网络设备根据测量报告确定第二终端设备切换至通过第一终端设备与所述网络设备连接；
1805，网络设备向第一终端设备发送用于第二终端设备切换的第一RRC重配置消息，该消息同时指示第二标识和与该第二标识对应的第一标识(根据1803获得)，以及用于中继的Uu和PC5 RLC配置和承载映射配置；该第一终端设备根据该第一RRC重配置消息完成对应的PC5接口和Uu接口的RLC配置和承载映射配置；
1806，网络设备向第二终端设备发送针对第二终端设备的第二RRC重配置消息，该消息包括第一终端设备的标识(Relay UE ID)、中继业务的PC5 RLC配置和相关的端到端无线承载(radio bearer)配置；该第二终端设备根据该第二RRC重配置消息确定切换至通过哪个第一终端设备与所述网络设备连接。
1807，第一终端设备使用或存储该第一标识与第二标识的对应关系。
1808，第二终端设备经由第一终端设备向网络设备发送RRC重配置完成消息(与1806对应)。
1809，(可选)第二终端设备切换完成，第二终端设备和网络设备之间经由第一终端设备收发上行和/或下行无线承载的数据，其中，在PC5接口可以使用源层2或目的地层2标识进行上行和/或下行无线承载的数据的发送和/或接收，在PC5接口的适应层的头文件中可以包括承载的标识，在Uu接口，上行和/或下行无线承载的数据在Uu接口的适应层的头中包括第二标识和第二终端设备的Uu无线承载标识，以便网络设备识别第二终端设备，即确定上下行传输对应哪一个第二终端设备。
上述1709和1807的执行顺序不限于此，本申请实施例并不以此作为限制，另外，图中未示出，在网络设备侧也可以使用或存储该第一标识与第二标识的对应关系，此处不再赘述。
由上述实施例可知，第二终端设备的标识可以被第一终端设备的服务网络设备配置，以便第一终端设备在转发第二终端设备的数据(例如RRC消息和用户面数据等)时可以使用该标识，有助于第二终端设备的RRC消息和用户面数据被网络设备正确识别。
在前述实施例中，为了节省传输开销，可以使用第一索引代替目的地标识的来传输，该第一索引的长度小于目的地标识的长度，但可以唯一标识目的地标识，但在检测到PC5接口的SL无线链路失败(RLF)时，如果仍使用第一索引代替目的地标识，那么由于网络设备不知道第二终端设备的目的地标识，因此无法识别是哪个PC5接口的SL检测到了RLF，本申请实施例提出一种信息发送方法，通过在第一终端设备向网络设备发送的边链路失败相关的信息中承载第一索引的同时，还承载第二标识或目的地标识，以便网络设备正确识别是哪个PC5接口的SL检测到了RLF。以下结合第六方面至第八方面的实施例进行说明。
第六方面的实施例
本申请实施例提供一种信息发送方法，应用于第一终端设备侧。
图19是该信息发送方法示意图，如图19所示，该方法包括：
1901，该第一终端设备向该网络设备发送边链路失败相关的信息，该边链路失败相关的信息包括发生边链路失败的至少一个第二终端设备的目的地标识，以及该发生边链路失败的第二终端设备的第二标识和/或该发生边链路失败的第二终端设备相关的第一标识。
在一些实施例中，如前该，为了节省传输开销，可以使用第一索引代替目的地标识的来传输，该第一索引的长度小于目的地标识的长度，但可以唯一标识目的地标识，例如，可以由第一终端设备或第二终端设备分配该第一索引，并通知对方和/或网络设备，在该第一索引由第一终端设备分配时，该方法还可以包括：
该第一终端设备分配该第一索引并向该第二终端设备发送指示该第一索引的第二信息，例如，该第二信息可以由边链路信令消息或边链路RRC消息承载，关于该边链路信令消息或边链路RRC消息如前实施例所述，此处不再赘述。
在一些实施例中，在该第一索引由第二终端设备分配时，该方法还可以包括：
该第一终端设备接收该第二终端设备分配并发送的指示第一索引的第一信息，，例如，该第二信息可以由边链路信令消息或边链路RRC消息承载，关于该边链路信令消息或边链路RRC消息如前实施例该，此处不再赘述。
在一些实施例中，该方法还可以包括：
该第一终端设备向该网络设备发送指示该第一索引的第三信息。
在一些实施例中，在第一终端设备检测到PC5接口的边链路RLF时，会向网络设备上报PC5接口的边链路RLF，例如，使用边链路失败相关的信息通知网络设备检测到RLF，该边链路失败相关信息中包括发生边链路失败的至少一个第二终端设备的目的地标识，以及所述发生边链路失败的第二终端设备的第二标识和/或所述发生边链路失败的第二终端设备相关的第一标识，该第一标识是第一索引，该第二标识的实施方式如前所述，此处不再赘述。
在一些实施例中，该边链路失败相关信息(例如sl-FailureList-r16)可以由SUI承载，在现有方法中，该sl-FailureList-r16包括发生边链路失败的至少一个第二终端设备的目的地标识，在本申请实施例中，还可以包括第一标识，或第二标识或，第一标识和第二标识。
由上述实施例可知，通过在第一终端设备向网络设备发送的边链路失败相关的信息中承载第一索引的同时，还承载第二标识或目的地标识，以便网络设备正确识别是哪个PC5接口的SL检测到了RLF。
第七方面的实施例
本申请实施例提供一种信息接收方法，应用于网络设备侧。
图20是该信息接收方法示意图，如图20所示，该方法包括：
2001，该网络设备接收第一终端设备发送的边链路失败相关的信息，该边链路失败相关的信息包括发生边链路失败的至少一个第二终端设备的目的地标识，以及该发生边链路失败的第二终端设备的第二标识和/或该发生边链路失败的第二终端设备相关的第一标识。
在一些实施例中，2001的实施方式可以参考1901，该第一标识，第二标识的实施方式如前所述，此处不再赘述。
在一些实施例中，该方法还可以包括：
该网络设备接收该第一终端设备发送的指示该第一索引的第三信息，以便确定第一终端设备或第二终端设备为目的地标识分配的第一索引。
由上述实施例可知，通过在第一终端设备向网络设备发送的边链路失败相关的信息中承载第一索引的同时，还承载第二标识或目的地标识，以便网络设备正确识别是哪个PC5接口的SL检测到了RLF。
第八方面的实施例
本申请实施例提供一种信息收发方法，应用于第二网络设备侧。
图21是该信息收发方法示意图，如图21所示，该方法包括：
2101，该第二终端设备分配第一索引，并向第一终端设备发送指示该第一索引的第一信息；或者，该第二终端设备接收该第一终端设备发送的指示该第一索引的第二信息；该第一索引与该第二终端设备的目的地标识对应。
在一些实施例中，该方法还可以包括：
该网络设备接收该第一终端设备发送的指示该第一索引的第三信息，以便确定第一终端设备或第二终端设备为目的地标识分配的第一索引。
例如，该第一信息或第二信息可以由边链路信令消息或边链路RRC消息承载，关于该边链路信令消息或边链路RRC消息如前实施例所述，关于该第一索引的实施方式请参考第六方面的实施例，此处不再赘述。
值得注意的是，以上附图6-21仅对本申请实施例进行了示意性说明，但本申请不限于此。例如可以适当地调整各个操作之间的执行顺序，此外还可以增加其它的一些操作或者减少其中的某些操作。本领域的技术人员可以根据上述内容进行适当地变型，而不仅限于上述附图6-21的记载。
以上各个实施例仅对本申请实施例进行了示例性说明，但本申请不限于此，还可以在以上各个实施例的基础上进行适当的变型。例如，可以单独使用上述各个实施例，也可以将以上各个实施例中的一种或多种结合起来。例如，第一至第五方面的实施例中，在第一标识是第一索引时，第一至第五方面的实施例可以与第六至第八方面的实施例结合实施。
第九方面的实施例
本申请实施例提供一种信息发送/接收装置，配置在第一终端设备中。
图22是本申请实施例的信息接收装置的一个示意图，本申请实施例从第一终端设备的一侧进行说明。其中，本申请实施例的信息接收装置的实施原理与第一方面的实施例的实施类似，内容相同之处不再重复说明。
如图22所示，本申请实施例的信息接收装置2200包括：
处理单元2201，其与至少一个第二终端设备建立连接；
第一发送单元2202，其向网络设备发送第一标识信息，该第一标识信息用于指示该至少一个第二终端设备相关的第一标识；
第一接收单元2203，其接收该网络设备发送的第二标识信息，该第二标识信息用于指示该至少一个第二终端设备的第二标识。
在一些实施例中，该第一标识信息由SUI或针对第一终端设备的第二RRC消息承载。
在一些实施例中，该第一终端设备处于RRC连接模式；或者，在该第一终端设备处于RRC空闲或非激活模式时，该装置还包括：(未图示，可选)
第二接收单元，其接收该第二终端设备发送的针对第二终端设备的第一RRC消息，并进入RRC连接模式。
在一些实施例中，该针对第一终端设备的第二RRC消息包括RRC setup request或RRC setup complete或RRC resume request或RRC resume complete。
在一些实施例中，该针对第二终端设备的第一RRC消息包括RRC setup request或RRC re-establishment request或RRC resume request消息。
在一些实施例中，在满足第一触发条件时，该第一发送单元向该网络设备发送第一标识信息，该第一触发条件包括以下条件的至少之一：
该第一终端设备与该第二终端设备建立连接；
该第一终端设备与该第二终端设备之间传输边链路能力消息；
该第一终端设备接收到该第二终端设备发送的针对第二终端设备的第一RRC消息。
在一些实施例中，该第一标识是目的地标识(destination ID)或第一索引，和/或PC5单播链路的标识，和/或，PC5-RRC连接的标识，和/或源标识和目的地标识对。
在一些实施例中，该第一标识信息包括一个第二终端设备相关的第一标识，该一个第二终端设备是与该第一终端设备新建立连接的终端设备，或者该第一标识信息包括所有与该第一终端设备建立连接的第二终端设备相关的第一标识。
在一些实施例中，该第二标识是该第二终端设备的本地/临时标识。
在一些实施例中，该本地/临时标识包括以下至少一种：
该第二终端设备的第二索引，该第二索引用于唯一标识与该第一终端设备有连接关系的第二终端设备；
该第二终端设备的C-RNTI；
该第二终端设备的目的地标识的一部分。
在一些实施例中，该第二标识信息由针对第一终端设备的第四RRC消息或针对第一终端设备的第三RRC消息承载，该第四RRC消息包括RRC reconfiguration或RRC re-establishment或RRC resume消息，该针对第一终端设备的第三RRC消息包括RRC setup或RRC resume或RRC reconfiguration。
在一些实施例中，该第二标识信息中第二标识的排列顺序与该第一标识信息中该至少一个第二终端设备相关的第一标识的出现顺序相同。
在一些实施例中，该第三RRC消息还用于指示与该第二标识对应的该第一标识，和/或该第四RRC消息还用于指示与该第二标识对应的该第一标识。
在一些实施例中，该装置还包括：(未图示，可选)
第一存储单元，其使用或存储该第一标识和该第二标识的对应关系。
在一些实施例中，该装置还包括：(未图示，可选)
第二发送单元，其向该网络设备发送边链路失败相关的信息，该边链路失败相关的信息包括发生边链路失败的至少一个第二终端设备的目的地标识，以及该发生边链路失败的第二终端设备的第二标识和/或该发生边链路失败的第二终端设备相关的第一标识。
上述各个单元模块的实施方式可以参考第一方面的实施例，重复之处不再赘述。
图23是本申请实施例的信息接收装置的一个示意图，本申请实施例从第一终端设备的一侧进行说明。其中，本申请实施例的信息接收装置的实施原理与第四方面的实施例的实施类似，内容相同之处不再重复说明。
如图23所示，本申请实施例的信息接收装置2300包括：
第十一接收单元2301，其接收网络设备发送的第二标识信息，该第二标识信息用于指示第二终端设备的第二标识，其中，该第二终端设备确定切换至通过该第一终端设备与该网络设备连接。
在一些实施例中，该装置还包括：(未图示，可选)
第十二接收单元，其接收该第二终端设备发送的该第二标识信息。
在一些实施例中，该第十二接收单元接收的该第二标识信息由该第一终端设备和该第二终端设备之间的边链路信令消息或边链路RRC消息承载，该边链路信令消息或边链路RRC消息还用于指示该第一标识。
在一些实施例中，该第十一接收单元接收的该第二标识信息通过第一RRC重配置消息承载。
在一些实施例中，该第一RRC重配置消息还用于指示与该第二标识对应的第一标识。
在一些实施例中，该装置还包括：(未图示，可选)
第五存储单元，其使用或存储该第一标识与该第二标识对应关系。
在一些实施例中，该装置还包括：(未图示，可选)
第十三发送单元，其向该网络设备发送该第一标识信息以及对应的该第二标识信息。
在一些实施例中，第一标识信息以及对应的该第二标识信息通过SUI承载。
在一些实施例中，该第一标识信息以及对应的该第二标识信息是该SUI中的新增信息元，或者被包含在边链路失败信息元中，或者被包含在边链路发送资源请求信息元中。
上述各个单元模块的实施方式可以参考第四方面的实施例，重复之处不再赘述。
图24是本申请实施例的信息发送装置的一个示意图，本申请实施例从第一终端设备的一侧进行说明。其中，本申请实施例的信息发送装置的实施原理与第六方面的实施例的实施类似，内容相同之处不再重复说明。
如图24所示，本申请实施例的信息发送装置2400包括：
第四发送单元2401，其向该网络设备发送边链路失败相关的信息，该边链路失败相关的信息包括发生边链路失败的至少一个第二终端设备的目的地标识，以及该发生边链路失败的第二终端设备的第二标识和/或该发生边链路失败的第二终端设备相关的第一标识。
在一些实施例中，该第二标识是该第二终端设备的本地/临时标识。
在一些实施例中，该本地/临时标识包括以下至少一种：
该第二终端设备的第二索引，该第二索引用于唯一标识第二终端设备；
该第二终端设备的C-RNTI；
该第二终端设备的目的地标识的一部分。
在一些实施例中，该第一标识是该第二终端设备的第一索引。
在一些实施例中，该装置还包括：(未图示，可选)
第五接收单元，其接收该第二终端设备分配并发送的指示第一索引的第一信息；或者，第五发送单元，其分配该第一索引并向该第二终端设备发送指示该第一索引的第二信息。
在一些实施例中，该第一信息和/或该第二信息通过PC5-RRC消息或PC5-S消息承载。
上述各个单元模块的实施方式可以参考第六方面的实施例，重复之处不再赘述。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。本申请实施例的信息发送/接收装置2200,2300,2400还可以包括其它部件或者模块，关于这些部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图22至图24中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
第十方面的实施例
本申请实施例提供一种信息收发装置，配置在第二终端设备中。
图25是本申请实施例的信息接收装置的一个示意图，本申请实施例从第二终端设备的一侧进行说明。其中，本申请实施例的信息发送装置的实施原理与第五方面的实施例的实施类似，内容相同之处不再重复说明。
第十发送单元2501，其向网络设备发送第一标识信息，该第一标识信息用于指示该第二终端设备相关的第一标识；和/或，
第十接收单元2502，其接收网络设备发送的第二标识信息，该第二标识信息用于指示该第二终端设备的第二标识。
在一些实施例中，该装置还包括：(可选，未图示)
第十一发送单元，其向该第一终端设备发送该第二标识信息。
在一些实施例中，该第二标识信息由该第一终端设备和该第二终端设备之间的边 链路信令消息或边链路RRC消息承载，该边链路信令消息或边链路RRC消息还用于指示该第一标识。
在一些实施例中，该第十接收单元通过第二RRC重配置消息接收该网络设备发送的该第二标识信息。
在一些实施例中，该第十发送单元通过测量报告消息向该网络设备发送该第一标识信息。
图26是本申请实施例的信息收发装置的一个示意图，本申请实施例从第二终端设备的一侧进行说明。其中，本申请实施例的信息收发装置的实施原理与第八方面的实施例的实施类似，内容相同之处不再重复说明。
第七发送单元2601，其分配第一索引，并向第一终端设备发送指示该第一索引的第一信息；或者，第七接收单元2602，其接收该第一终端设备发送的指示该第一索引的第二信息；该第一索引与该第二终端设备的目的地标识对应。
上述各个单元模块的实施方式可以参考第五或第八方面的实施例，重复之处不再赘述。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。本申请实施例的信息收发装置2500-2600还可以包括其它部件或者模块，关于这些部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图25至图26中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
第十一方面的实施例
本申请实施例提供一种信息发送/接收装置，配置在网络设备中。
图27是本申请实施例的信息发送装置的一个示意图，本申请实施例从网络设备的一侧进行说明。其中，本申请实施例的信息发送装置的实施原理与第二方面的实施例的实施类似，内容相同之处不再重复说明。
如图27所示，本申请实施例的信息发送装置2700包括：
第三接收单元2701，其接收第一终端设备发送的第一标识信息，该第一标识信 息用于指示该至少一个与该第一终端设备连接的第二终端设备相关的第一标识；
第三发送单元2702，其向该第一终端设备发送第二标识信息，该第二标识信息用于指示该至少一个第二终端设备的第二标识。
在一些实施例中，该第一标识信息由SUI或针对第一终端设备的第二RRC消息承载。
在一些实施例中，该针对第一终端设备的第二RRC消息包括RRC setup request或RRC setup complete或RRC resume request或RRC resume complete。
在一些实施例中，在满足第一触发条件时，该第三接收单元接收第一终端设备发送的第一标识信息，该第一触发条件包括以下条件的至少之一：
该第一终端设备与该第二终端设备建立连接；
该第一终端设备与该第二终端设备之间传输边链路能力消息；
该第一终端设备接收到该第二终端设备发送的针对第二终端设备的第一RRC消息。
在一些实施例中，该第一标识是目的地标识(destination ID)或第一索引。
在一些实施例中，该第一标识信息包括一个第二终端设备相关的第一标识，该一个第二终端设备是与该第一终端设备新建立连接的终端设备，或者该第一标识信息包括所有与该第一终端设备建立连接的第二终端设备相关的第一标识。
在一些实施例中，该第二标识是该第二终端设备的本地/临时标识。
在一些实施例中，该本地/临时标识包括以下至少一种：
该第二终端设备的第二索引，该第二索引用于唯一标识与该第一终端设备有连接关系的第二终端设备；
该第二终端设备的C-RNTI；
该第二终端设备的目的地标识的一部分。
在一些实施例中，该第二标识信息由针对第一终端设备的第四RRC消息或针对第一终端设备的第三RRC消息承载，该第四RRC消息包括RRC reconfiguration或RRC re-establishment或RRC resume消息，该针对第一终端设备的第三RRC消息包括RRC setup或RRC resume或RRC reconfiguration。
在一些实施例中，该第二标识信息中第二标识的排列顺序与该第一标识信息中该至少一个第二终端设备相关的第一标识的出现顺序相同。
在一些实施例中，该第三RRC消息还用于指示与该第二标识对应的该第一标识，和/或该第四RRC消息还用于指示与该第二标识对应的该第一标识。
在一些实施例中，该装置还包括：(可选，未图示)
第二存储单元，其使用或存储该第一标识和该第二标识的对应关系。
在一些实施例中，该装置还包括：(可选，未图示)
第三存储单元，其使用或存储该第一标识，该第二标识以及分配的C-RNTI的对应关系。
在一些实施例中，该装置还包括：(可选，未图示)
第四接收单元，其接收该第一终端设备发送的边链路失败相关的信息，该边链路失败相关的信息包括发生边链路失败的至少一个第二终端设备的目的地标识，以及该发生边链路失败的第二终端设备的第二标识和/或该发生边链路失败的第二终端设备相关的第一标识。
上述各个单元模块的实施方式可以参考第二方面的实施例，重复之处不再赘述。
图28是本申请实施例的信息发送装置的一个示意图，本申请实施例从网络设备的一侧进行说明。其中，本申请实施例的信息发送装置的实施原理与第三方面的实施例的实施类似，内容相同之处不再重复说明。
如图28所示，本申请实施例的信息发送装置2800包括：
确定单元2801，其确定第二终端设备切换至通过第一终端设备与该网络设备连接；
第八发送单元2802，其向该第一终端设备发送第二标识信息，该第二标识信息用于指示该第二终端设备的第二标识。
在一些实施例中，该装置还包括：(可选，未图示)
第九发送单元，其向该第二终端设备发送该第二标识信息。
在一些实施例中，该装置还包括：(可选，未图示)
第八接收单元，其在该第一终端设备与该第二终端设备建立连接后，接收该第一终端设备发送的第一标识信息以及对应的该第二标识信息，该第一标识信息用于指示该第二终端设备相关的第一标识。
在一些实施例中，该装置还包括：(可选，未图示)
第四存储单元，其使用或存储该第一标识与该第二标识的对应关系。
在一些实施例中，该第八发送单元发送的第二标识信息通过第一RRC重配置消息承载。
在一些实施例中，该第九发送单元发送的第二标识信息通过第二RRC重配置消息承载。
在一些实施例中，该装置还包括：(可选，未图示)
第九接收单元，其在该第一终端设备与该第二终端设备建立连接后，接收该第二终端设备发送的第一标识信息，该第一标识信息用于指示该第二终端设备相关的第一标识。
在一些实施例中，该第一标识信息通过测量报告消息承载。
在一些实施例中，该第一RRC重配置消息还用于指示与该第二标识对应的第一标识。
在一些实施例中，第一标识信息以及对应的该第二标识信息通过SUI承载。
在一些实施例中，该第一标识信息以及对应的该第二标识信息是该SUI中的新增信息元，或者被包含在边链路失败信息元中，或者被包含在边链路发送资源请求信息元中。
上述各个单元模块的实施方式可以参考第三方面的实施例，重复之处不再赘述。
图29是本申请实施例的信息接收装置的一个示意图，本申请实施例从网络设备的一侧进行说明。其中，本申请实施例的信息接收装置的实施原理与第七方面的实施例的实施类似，内容相同之处不再重复说明。
如图29所示，本申请实施例的信息接收装置2900包括：
第六接收单元2901，其接收第一终端设备发送的边链路失败相关的信息，该边链路失败相关的信息包括发生边链路失败的至少一个第二终端设备的目的地标识，以及该发生边链路失败的第二终端设备的第二标识和/或该发生边链路失败的第二终端设备相关的第一标识。
在一些实施例中，该第二标识是该第二终端设备的本地/临时标识。
在一些实施例中，该本地/临时标识包括以下至少一种：
该第二终端设备的第二索引，该第二索引用于唯一标识第二终端设备；
该第二终端设备的C-RNTI；
该第二终端设备的目的地标识的一部分。
在一些实施例中，该第一标识是该第二终端设备的第一索引。
在一些实施例中，该第一索引是该第一终端设备分配的或者是该第二终端设备分配的。
上述各个单元模块的实施方式可以参考第七方面的实施例，重复之处不再赘述。
值得注意的是，以上仅对与本申请相关的各部件或模块进行了说明，但本申请不限于此。本申请实施例的信息发送/接收装置2700-2900还可以包括其它部件或者模块，关于这些部件或者模块的具体内容，可以参考相关技术。
此外，为了简单起见，图27至图29中仅示例性示出了各个部件或模块之间的连接关系或信号走向，但是本领域技术人员应该清楚的是，可以采用总线连接等各种相关技术。上述各个部件或模块可以通过例如处理器、存储器、发射机、接收机等硬件设施来实现；本申请实施并不对此进行限制。
第十二方面的实施例
本申请实施例提供了一种通信系统，图30是该通信系统的示意图，如图30所示，该通信系统包括网络设备3001，第一终端设备3002，至少一个第二终端设备3003；
在一些实施例中，网络设备3001被配置为执行第二或第三或第七方面的实施例中网络设备所执行的方法，可以包含图27至图29的任一装置。在一些实施例中，第一终端设备3002被配置为执行第一或第四或第六方面的实施例中的方法，可以包含图22至图24的任一装置。在一些实施例中，第二终端设备3003被配置为执行第五或第八方面的实施例中的方法，可以包括图25和图26的任一装置。
本申请实施例还提供一种终端设备。
图31是本申请实施例的终端设备的示意图。如图31所示，该终端设备3100可以包括处理器3101和存储器3102；存储器3102存储有数据和程序，并耦合到处理器3101。值得注意的是，该图是示例性的；还可以使用其它类型的结构，来补充或代替该结构，以实现电信功能或其它功能。
例如，处理器3101可以被配置为执行程序而实现如第一或第四至第六或第八方面的实施例中的方法。
如图31所示，该终端设备3100还可以包括：通信模块3103、输入单元3104、显示器3105、电源3106。其中，上述部件的功能与现有技术类似，此处不再赘述。 值得注意的是，终端设备3100也并不是必须要包括图31中所示的所有部件，上述部件并不是必需的；此外，终端设备3100还可以包括图31中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种网络设备。
图32是本申请实施例的网络设备的示意图。如图32所示，网络设备3200可以包括：处理器(例如中央处理器CPU)3201和存储器3202；存储器3202耦合到处理器3201。其中该存储器3202可存储各种数据；此外还存储信息处理的程序，并且在中央处理器3201的控制下执行该程序。
例如，处理器3201可以被配置为执行程序而实现如第二或第三或第七方面的实施例中的方法。
此外，如图32所示，网络设备3200还可以包括：收发机3203和天线3204等；其中，上述部件的功能与现有技术类似，此处不再赘述。值得注意的是，网络设备3200也并不是必须要包括图32中所示的所有部件；此外，网络设备3200还可以包括图32中没有示出的部件，可以参考现有技术。
本申请实施例还提供一种计算机可读程序，其中当在终端设备中执行所述程序时，所述程序使得计算机在所述第一终端设备中执行第一或第四至第六或第八方面的实施例中的方法。
本申请实施例还提供一种存储有计算机可读程序的存储介质，其中所述计算机可读程序使得计算机在终端设备中执行第一或第四至第六或第八方面的实施例中的方法。
本申请实施例还提供一种计算机可读程序，其中当在网络设备中执行所述程序时，所述程序使得计算机在所述网络设备中执行第二或三或七方面的实施例中的方法。
本申请实施例还提供一种存储有计算机可读程序的存储介质，其中所述计算机可读程序使得计算机在网络设备中执行第二或三或七方面的实施例中的方法。
本申请以上的装置和方法可以由硬件实现，也可以由硬件结合软件实现。本申请涉及这样的计算机可读程序，当该程序被逻辑部件所执行时，能够使该逻辑部件实现上文所述的装置或构成部件，或使该逻辑部件实现上文所述的各种方法或步骤。逻辑部件例如现场可编程逻辑部件、微处理器、计算机中使用的处理器等。本申请还涉及用于存储以上程序的存储介质，如硬盘、磁盘、光盘、DVD、flash存储器等。
结合本申请实施例描述的方法/装置可直接体现为硬件、由处理器执行的软件模块或二者组合。例如，图中所示的功能框图中的一个或多个和/或功能框图的一个或多个组合，既可以对应于计算机程序流程的各个软件模块，亦可以对应于各个硬件模块。这些软件模块，可以分别对应于图中所示的各个步骤。这些硬件模块例如可利用现场可编程门阵列(FPGA)将这些软件模块固化而实现。
软件模块可以位于RAM存储器、闪存、ROM存储器、EPROM存储器、EEPROM存储器、寄存器、硬盘、移动磁盘、CD-ROM或者本领域已知的任何其它形式的存储介质。可以将一种存储介质耦接至处理器，从而使处理器能够从该存储介质读取信息，且可向该存储介质写入信息；或者该存储介质可以是处理器的组成部分。处理器和存储介质可以位于ASIC中。该软件模块可以存储在移动终端的存储器中，也可以存储在可插入移动终端的存储卡中。例如，若设备(如移动终端)采用的是较大容量的MEGA-SIM卡或者大容量的闪存装置，则该软件模块可存储在该MEGA-SIM卡或者大容量的闪存装置中。
针对附图中描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，可以实现为用于执行本申请所描述功能的通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)或者其它可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件或者其任意适当组合。针对附图描述的功能方框中的一个或多个和/或功能方框的一个或多个组合，还可以实现为计算设备的组合，例如，DSP和微处理器的组合、多个微处理器、与DSP通信结合的一个或多个微处理器或者任何其它这种配置。
以上结合具体的实施方式对本申请进行了描述，但本领域技术人员应该清楚，这些描述都是示例性的，并不是对本申请保护范围的限制。本领域技术人员可以根据本申请的精神和原理对本申请做出各种变型和修改，这些变型和修改也在本申请的范围内。
关于本实施例公开的上述实施方式，还公开了如下的附记：
1.一种信息发送方法，应用于第一终端设备，其特征在于，所述方法包括：
第一终端设备与至少一个第二终端设备建立连接；
所述第一终端设备向网络设备发送第一标识信息，所述第一标识信息用于指示所述至少一个第二终端设备相关的第一标识。
2.根据附记1所述的方法，其中，所述第一标识信息由SUI或针对第一终端设备的第二RRC消息承载。
3.根据附记1或2所述的方法，其中，所述第一终端设备处于RRC连接模式；或者，在所述第一终端设备处于RRC空闲或非激活模式时，所述方法还包括：
所述第一终端设备接收所述第二终端设备发送的针对第二终端设备的第一RRC消息，并进入RRC连接模式。
4.根据附记2所述的方法，其中，所述针对第一终端设备的第二RRC消息包括RRC setup request或RRC setup complete或RRC resume request或RRC resume complete。
5.根据附记3所述的方法，其中，所述针对第二终端设备的第一RRC消息包括RRC setup request或RRC re-establishment request或RRC resume request消息。
6.根据附记1至5任一项所述的方法，其中，在满足第一触发条件时，所述第一终端设备向所述网络设备发送第一标识信息，所述第一触发条件包括以下条件的至少之一：
所述第一终端设备与所述第二终端设备建立连接；
所述第一终端设备与所述第二终端设备之间传输边链路能力消息；
所述第一终端设备接收到所述第二终端设备发送的针对第二终端设备的第一RRC消息。
7.根据附记1至6任一项所述的方法，其中，所述第一标识是目的地标识(destination ID)或第一索引，和/或PC5单播链路的标识，和/或，PC5-RRC连接的标识，和/或源标识和目的地标识对。
8.根据附记1至7任一项所述的方法，其中，所述第一标识信息包括一个第二终端设备相关的第一标识，所述一个第二终端设备是与所述第一终端设备新建立连接的终端设备，或者所述第一标识信息包括所有与所述第一终端设备建立连接的第二终端设备相关的第一标识。
9.根据附记1至8任一项所述的方法，其中，所述方法还包括：
所述第一终端设备接收所述网络设备发送的第二标识信息，所述第二标识信息用于指示所述至少一个第二终端设备的第二标识。
10.根据附记9所述的方法，其中，所述第二标识是所述第二终端设备的本地/ 临时标识。
11.根据附记10所述的方法，其中，所述本地/临时标识包括以下至少一种：
所述第二终端设备的第二索引，所述第二索引用于唯一标识与所述第一终端设备有连接关系的第二终端设备；
所述第二终端设备的C-RNTI；
所述第二终端设备的目的地标识的一部分。
12.根据附记9或10或11所述的方法，其中，所述第二标识信息由针对第一终端设备的第四RRC消息或针对第一终端设备的第三RRC消息承载，所述第四RRC消息包括RRC reconfiguration或RRC re-establishment或RRC resume消息，所述针对第一终端设备的第三RRC消息包括RRC setup或RRC resume或RRC reconfiguration。
13.根据附记9至12任一项所述的方法，其中，所述第二标识信息中第二标识的排列顺序与所述第一标识信息中所述至少一个第二终端设备相关的第一标识的出现顺序相同。
14.根据附记12所述的方法，其中，所述第三RRC消息还用于指示与所述第二标识对应的所述第一标识，和/或所述第四RRC消息还用于指示与所述第二标识对应的所述第一标识。
15.根据附记1至14任一项所述的方法，其中，所述方法还包括：
所述第一终端设备使用或存储所述第一标识和所述第二标识的对应关系。
16.根据附记1至15任一项所述的方法，其中，所述方法还包括：
所述第一终端设备向所述网络设备发送边链路失败相关的信息，所述边链路失败相关的信息包括发生边链路失败的至少一个第二终端设备的目的地标识，以及所述发生边链路失败的第二终端设备的第二标识和/或所述发生边链路失败的第二终端设备相关的第一标识。
17.一种信息接收方法，应用于网络设备，其特征在于，所述方法包括：
所述网络设备接收第一终端设备发送的第一标识信息，所述第一标识信息用于指示所述至少一个与所述第一终端设备连接的第二终端设备相关的第一标识。
18.根据附记17所述的方法，其中，所述第一标识信息由SUI或针对第一终端设备的第二RRC消息承载。
19.根据附记2所述的方法，其中，所述针对第一终端设备的第二RRC消息包 括RRC setup request或RRC setup complete或RRC resume request或RRC resume complete。
20.根据附记17至19任一项所述的方法，其中，在满足第一触发条件时，所述网络设备接收第一终端设备发送的第一标识信息，所述第一触发条件包括以下条件的至少之一：
所述第一终端设备与所述第二终端设备建立连接；
所述第一终端设备与所述第二终端设备之间传输边链路能力消息；
所述第一终端设备接收到所述第二终端设备发送的针对第二终端设备的第一RRC消息。
21.根据附记17至20任一项所述的方法，其中，所述第一标识是目的地标识(destination ID)或第一索引，和/或PC5单播链路的标识，和/或，PC5-RRC连接的标识，和/或源标识和目的地标识对。
22.根据附记17至21任一项所述的方法，其中，所述第一标识信息包括一个第二终端设备相关的第一标识，所述一个第二终端设备是与所述第一终端设备新建立连接的终端设备，或者所述第一标识信息包括所有与所述第一终端设备建立连接的第二终端设备相关的第一标识。
23.根据附记17至22任一项所述的方法，其中，所述方法还包括：
所述网络设备向所述第一终端设备发送第二标识信息，所述第二标识信息用于指示至少一个所述第二终端设备的第二标识。
24.根据附记23所述的方法，其中，所述第二标识是所述第二终端设备的本地/临时标识。
25.根据附记24所述的方法，其中，所述本地/临时标识包括以下至少一种：
所述第二终端设备的第二索引，所述第二索引用于唯一标识与所述第一终端设备有连接关系的第二终端设备；
所述第二终端设备的C-RNTI；
所述第二终端设备的目的地标识的一部分。
26.根据附记23或24或25所述的方法，其中，所述第二标识信息由针对第一终端设备的第四RRC消息或针对第一终端设备的第三RRC消息承载，所述第四RRC消息包括RRC reconfiguration或RRC re-establishment或RRC resume消息，所述针对 第一终端设备的第三RRC消息包括RRC setup或RRC resume或RRC reconfiguration。
27.根据附记23至25任一项所述的方法，其中，所述第二标识信息中第二标识的排列顺序与所述第一标识信息中所述至少一个第二终端设备相关的第一标识的出现顺序相同。
28.根据附记26所述的方法，其中，所述第三RRC消息还用于指示与所述第二标识对应的所述第一标识，和/或所述第四RRC消息还用于指示与所述第二标识对应的所述第一标识。
29.根据附记17至28任一项所述的方法，其中，所述方法还包括：
所述网络设备使用或存储所述第一标识和所述第二标识的对应关系。
30.根据附记17至28任一项所述的方法，其中，所述方法还包括：
所述网络设备使用或存储所述第一标识，所述第二标识以及分配的C-RNTI的对应关系。
31.根据附记17至30任一项所述的方法，其中，所述方法还包括：
所述网络设备接收所述第一终端设备发送的边链路失败相关的信息，所述边链路失败相关的信息包括发生边链路失败的至少一个第二终端设备的目的地标识，以及所述发生边链路失败的第二终端设备的第二标识和/或所述发生边链路失败的第二终端设备相关的第一标识。
32.一种信息发送方法，应用于第一终端设备，其特征在于，所述方法包括：
所述第一终端设备向所述网络设备发送边链路失败相关的信息，所述边链路失败相关的信息包括发生边链路失败的至少一个第二终端设备的目的地标识，以及所述发生边链路失败的第二终端设备的第二标识和/或所述发生边链路失败的第二终端设备相关的第一标识。
33.根据附记32所述的方法，其中，所述第二标识是所述第二终端设备的本地/临时标识。
34.根据附记33所述的方法，其中，所述本地/临时标识包括以下至少一种：
所述第二终端设备的第二索引，所述第二索引用于唯一标识第二终端设备；
所述第二终端设备的C-RNTI；
所述第二终端设备的目的地标识的一部分。
35.根据附记32所述的方法，其中，所述第一标识是所述第二终端设备的第一 索引。
36.根据附记35所述的方法，其中，所述方法还包括：
所述第一终端设备接收所述第二终端设备分配并发送的指示第一索引的第一信息；或者，所述第一终端设备分配所述第一索引并向所述第二终端设备发送指示所述第一索引的第二信息。
37.根据附记36所述的方法，其中，所述第一信息和/或所述第二信息通过PC5-RRC消息或PC5-S消息承载。
38.一种信息接收方法，应用于网络设备，其特征在于，所述方法包括：
所述网络设备接收第一终端设备发送的边链路失败相关的信息，所述边链路失败相关的信息包括发生边链路失败的至少一个第二终端设备的目的地标识，以及所述发生边链路失败的第二终端设备的第二标识和/或所述发生边链路失败的第二终端设备相关的第一标识。
39.根据附记38所述的方法，其中，所述第二标识是所述第二终端设备的本地/临时标识。
40.根据附记39所述的方法，其中，所述本地/临时标识包括以下至少一种：
所述第二终端设备的第二索引，所述第二索引用于唯一标识第二终端设备；
所述第二终端设备的C-RNTI；
所述第二终端设备的目的地标识的一部分。
41.根据附记38所述的方法，其中，所述第一标识是所述第二终端设备的第一索引。
42.根据附记41所述的方法，其中，所述第一索引是所述第一终端设备分配的或者是所述第二终端设备分配的。
43.一种信息发送方法，应用于第二终端设备，其特征在于，所述方法包括：
所述第二终端设备分配第一索引，并向第一终端设备发送指示所述第一索引的第一信息；或者，所述第二终端设备接收所述第一终端设备发送的指示所述第一索引的第二信息；所述第一索引与所述第二终端设备的目的地标识对应。
44.一种信息发送方法，应用于网络设备，其特征在于，所述方法包括：
所述网络设备确定第二终端设备切换至通过第一终端设备与所述网络设备连接；
所述网络设备向所述第一终端设备发送第二标识信息，所述第二标识信息用于指 示所述第二终端设备的第二标识。
45.根据附记44所述的方法，其中，所述方法还包括：
所述网络设备向所述第二终端设备发送所述第二标识信息。
46.根据附记44或45所述的方法，其中，所述方法还包括：
在所述第一终端设备与所述第二终端设备建立连接后，所述网络设备接收所述第一终端设备发送的第一标识信息以及对应的所述第二标识信息，所述第一标识信息用于指示所述第二终端设备相关的第一标识。
47.根据附记46所述的方法，其中，所述方法还包括：
所述网络设备使用或存储所述第一标识与所述第二标识的对应关系。
48.根据附记44至47任一项所述的方法，其中，所述网络设备向第一终端设备发送的第二标识信息通过第一RRC重配置消息承载，所述网络设备向第二终端设备发送的第二标识信息通过第二RRC重配置消息承载。
49.根据附记44或45所述的方法，其中，所述方法还包括：
在所述第一终端设备与所述第二终端设备建立连接后，所述网络设备接收所述第二终端设备发送的第一标识信息，所述第一标识信息用于指示所述第二终端设备相关的第一标识。
50.根据附记49所述的方法，其中，所述第一标识信息通过测量报告消息承载。
51.根据附记50所述的方法，其中，所述第一RRC重配置消息还用于指示与所述第二标识对应的第一标识。
52.根据附记46所述的方法，其中，第一标识信息以及对应的所述第二标识信息通过SUI承载。
53.根据附记52所述的方法，其中，所述第一标识信息以及对应的所述第二标识信息是所述SUI中的新增信息元，或者被包含在边链路失败信息元中，或者被包含在边链路发送资源请求信息元中。
54.一种信息收发方法，应用于第二终端设备，其特征在于，所述方法包括：
所述第二终端设备向网络设备发送第一标识信息，所述第一标识信息用于指示所述第二终端设备相关的第一标识；和/或，
所述第二终端设备接收网络设备发送的第二标识信息，所述第二标识信息用于指示所述第二终端设备的第二标识。
55.根据附记54所述的方法，其中，所述方法还包括：
所述第二终端设备向所述第一终端设备发送所述第二标识信息。
56.根据附记55所述的方法，其中，所述第二标识信息由所述第一终端设备和所述第二终端设备之间的边链路信令消息或边链路RRC消息承载，所述边链路信令消息或边链路RRC消息还用于指示所述第一标识。
57.根据附记54所述的方法，其中，所述第二终端设备通过第二RRC重配置消息接收所述网络设备发送的所述第二标识信息。
58.根据附记54所述的方法，其中，所述第二终端设备通过测量报告消息向所述网络设备发送所述第一标识信息。
59.一种信息接收方法，应用于第一终端设备，其特征在于，所述方法包括：
所述第一终端设备接收网络设备发送的第二标识信息，所述第二标识信息用于指示第二终端设备的第二标识，其中，所述第二终端设备确定切换至通过所述第一终端设备与所述网络设备连接。
60.根据附记59所述的方法，其中，所述方法还包括：
所述第一终端设备接收所述第二终端设备发送的所述第二标识信息。
61.根据附记60所述的方法，其中，所述第二终端设备发送的所述第二标识信息由所述第一终端设备和所述第二终端设备之间的边链路信令消息或边链路RRC消息承载，所述边链路信令消息或边链路RRC消息还用于指示所述第一标识。
62.根据附记59所述的方法，其中，所述网络设备发送的所述第二标识信息通过第一RRC重配置消息承载。
63.根据附记62所述的方法，其中，所述第一RRC重配置消息还用于指示与所述第二标识对应的第一标识信息。
64.根据附记61或63所述的方法，其中，所述方法还包括：
所述第一终端设备使用或存储所述第一标识与所述第二标识对应关系。
65.根据附记61所述的方法，其中，所述方法还包括：
所述第一终端设备向所述网络设备发送所述第一标识信息以及对应的所述第二标识信息。
66.根据附记65所述的方法，其中，第一标识信息以及对应的所述第二标识信息通过SUI承载。
67.根据附记66所述的方法，其中，所述第一标识信息以及对应的所述第二标识信息是所述SUI中的新增信息元，或者被包含在边链路失败信息元中，或者被包含在边链路发送资源请求信息元中。
68.一种网络设备，包括存储器和处理器，所述存储器存储有计算机程序，其中，所述处理器被配置为执行所述计算机程序而实现如附记17至31,44至53任一项所述的方法。
69.一种终端设备，包括存储器和处理器，所述存储器存储有计算机程序，其中，所述处理器被配置为执行所述计算机程序而实现如附记1至16,32至43,54至67任一项所述的方法。
70.一种通信系统，包括网络设备、以及第一终端设备和第二终端设备，其中，所述网络设备被配置为执行附记17至31,44至53任一项所述的方法，所述第一终端设备被配置为执行附记1至16,59至67任一项所述的方法，所述第二终端设备被配置为执行附记32至43,54至58任一项所述的方法。

Claims (20)

  1. 一种信息接收装置，配置于第一终端设备，其特征在于，所述装置包括：
    处理单元，其与至少一个第二终端设备建立连接；
    第一发送单元，其向网络设备发送第一标识信息，所述第一标识信息用于指示所述至少一个第二终端设备相关的第一标识；
    第一接收单元，其接收所述网络设备发送的第二标识信息，所述第二标识信息用于指示所述至少一个第二终端设备的第二标识。
  2. 根据权利要求1所述的装置，其中，所述第一标识信息由SUI或针对第一终端设备的第二RRC消息承载。
  3. 根据权利要求1所述的装置，其中，所述第一终端设备处于RRC连接模式；或者，在所述第一终端设备处于RRC空闲或非激活模式时，所述装置还包括：
    第二接收单元，其接收所述第二终端设备发送的针对第二终端设备的第一RRC消息，并进入RRC连接模式。
  4. 根据权利要求2所述的装置，其中，所述针对第一终端设备的第二RRC消息包括RRC setup request或RRC setup complete或RRC resume request或RRC resume complete。
  5. 根据权利要求3所述的装置，其中，所述针对第二终端设备的第一RRC消息包括RRC setup request或RRC re-establishment request或RRC resume request消息。
  6. 根据权利要求1所述的装置，其中，在满足第一触发条件时，所述第一发送单元向所述网络设备发送第一标识信息，所述第一触发条件包括以下条件的至少之一：
    所述第一终端设备与所述第二终端设备建立连接；
    所述第一终端设备与所述第二终端设备之间传输边链路能力消息；
    所述第一终端设备接收到所述第二终端设备发送的针对第二终端设备的第一RRC消息。
  7. 根据权利要求1所述的装置，其中，所述第一标识是目的地标识(destination ID)或第一索引，和/或PC5单播链路的标识，和/或，PC5-RRC连接的标识，和/或源标识和目的地标识对。
  8. 根据权利要求1所述的装置，其中，所述第一标识信息包括一个第二终端设 备相关的第一标识，所述一个第二终端设备是与所述第一终端设备新建立连接的终端设备，或者所述第一标识信息包括所有与所述第一终端设备建立连接的第二终端设备相关的第一标识。
  9. 根据权利要求1所述的装置，其中，所述第二标识是所述第二终端设备的本地/临时标识。
  10. 根据权利要求9所述的装置，其中，所述本地/临时标识包括以下至少一种：
    所述第二终端设备的第二索引，所述第二索引用于唯一标识与所述第一终端设备有连接关系的第二终端设备；
    所述第二终端设备的C-RNTI；
    所述第二终端设备的目的地标识的一部分。
  11. 根据权利要求1所述的装置，其中，所述第二标识信息由针对第一终端设备的第四RRC消息或针对第一终端设备的第三RRC消息承载，所述第四RRC消息包括RRC reconfiguration或RRC re-establishment或RRC resume消息，所述针对第一终端设备的第三RRC消息包括RRC setup或RRC resume或RRC reconfiguration。
  12. 根据权利要求1所述的装置，其中，所述装置还包括：
    第二发送单元，其向所述网络设备发送边链路失败相关的信息，所述边链路失败相关的信息包括发生边链路失败的至少一个第二终端设备的目的地标识，以及所述发生边链路失败的第二终端设备的第二标识和/或所述发生边链路失败的第二终端设备相关的第一标识。
  13. 一种信息发送装置，应用于网络设备，其特征在于，所述装置包括：
    第三接收单元，其接收第一终端设备发送的第一标识信息，所述第一标识信息用于指示所述至少一个与所述第一终端设备连接的第二终端设备相关的第一标识；
    第三发送单元，其向所述第一终端设备发送第二标识信息，所述第二标识信息用于指示至少一个所述第二终端设备的第二标识。
  14. 根据权利要求13所述的装置，其中，所述第一标识信息由SUI或针对第一终端设备的第二RRC消息承载。
  15. 根据权利要求13所述的装置，其中，在满足第一触发条件时，所述第三接收单元接收第一终端设备发送的第一标识信息，所述第一触发条件包括以下条件的至少之一：
    所述第一终端设备与所述第二终端设备建立连接；
    所述第一终端设备与所述第二终端设备之间传输边链路能力消息；
    所述第一终端设备接收到所述第二终端设备发送的针对第二终端设备的第一RRC消息。
  16. 根据权利要求13所述的装置，其中，所述第一标识是目的地标识(destination ID)或第一索引，和/或PC5单播链路的标识，和/或，PC5-RRC连接的标识，和/或源标识和目的地标识对。
  17. 根据权利要求13所述的装置，其中，所述第一标识信息包括一个第二终端设备相关的第一标识，所述一个第二终端设备是与所述第一终端设备新建立连接的终端设备，或者所述第一标识信息包括所有与所述第一终端设备建立连接的第二终端设备相关的第一标识。
  18. 根据权利要求13所述的装置，其中，所述第二标识是所述第二终端设备的本地/临时标识。
  19. 根据权利要求13所述的装置，其中，所述第二标识信息由针对第一终端设备的第四RRC消息或针对第一终端设备的第三RRC消息承载，所述第四RRC消息包括RRC reconfiguration或RRC re-establishment或RRC resume消息，所述针对第一终端设备的第三RRC消息包括RRC setup或RRC resume或RRC reconfiguration。
  20. 一种通信系统，包括权利要求13至19任一项所述的网络设备和/或权利要求1至12任一项所述的第一终端设备。
PCT/CN2021/124652 2021-10-19 2021-10-19 信息发送方法、信息接收方法、装置和系统 WO2023065109A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/124652 WO2023065109A1 (zh) 2021-10-19 2021-10-19 信息发送方法、信息接收方法、装置和系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2021/124652 WO2023065109A1 (zh) 2021-10-19 2021-10-19 信息发送方法、信息接收方法、装置和系统

Publications (1)

Publication Number Publication Date
WO2023065109A1 true WO2023065109A1 (zh) 2023-04-27

Family

ID=86057796

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/124652 WO2023065109A1 (zh) 2021-10-19 2021-10-19 信息发送方法、信息接收方法、装置和系统

Country Status (1)

Country Link
WO (1) WO2023065109A1 (zh)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020087365A1 (zh) * 2018-10-31 2020-05-07 富士通株式会社 边链路数据的发送和配置方法以及装置
CN111212459A (zh) * 2018-11-22 2020-05-29 华为技术有限公司 一种中继通信方法及装置

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2020087365A1 (zh) * 2018-10-31 2020-05-07 富士通株式会社 边链路数据的发送和配置方法以及装置
CN111212459A (zh) * 2018-11-22 2020-05-29 华为技术有限公司 一种中继通信方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
INTEL CORPORATION: "Remaining Issues of L2 Relay Connection Management", 3GPP TSG-RAN WG2 MEETING#115E E-MEETING, R2-2107306, 6 August 2021 (2021-08-06), XP052034031 *

Similar Documents

Publication Publication Date Title
US11632788B2 (en) Data scheduling method, base station, and system
US11064557B2 (en) Method and device for establishing radio resource control connection
US9801228B2 (en) Systems, apparatuses, and methods for lightweight over-the-air signaling mechanisms in data communications
CN107231623B (zh) 一种数据调度方法、基站及系统
CN108476535B (zh) 无线终端、无线站、方法及其介质
JP2018038072A (ja) 無線通信システムにおけるｄ２ｄ関連情報を送信する方法及び装置
US20160323846A1 (en) Method and apparatus for providing group communication service enabler (gcse) service in wireless communication system
US11140732B2 (en) Method for performing sidelink communication in wireless communication system and apparatus therefor
US10412674B2 (en) Method and apparatus for reducing signaling overhead and reducing battery of terminal
WO2021174913A1 (zh) 通信方法及设备
WO2018127018A1 (zh) 多链接通信方法、设备和终端
CN113661772A (zh) 边链路传输中用户设备上下文的标识方法及装置
TW201914280A (zh) 與長期演進網路及新無線網路通訊的裝置及方法
US20230309155A1 (en) Methods and apparatus for radio connection
CN110100476B (zh) 用于信号传输的方法及设备、网络设备
WO2023065109A1 (zh) 信息发送方法、信息接收方法、装置和系统
WO2022205485A1 (zh) 信息收发方法以及装置
WO2023010298A1 (zh) 信息发送方法，信息处理方法以及装置
WO2023130368A1 (zh) 收发信息的方法、装置和通信系统
WO2023197185A1 (zh) Iab节点设备、iab宿主设备以及传输地址确定方法
WO2023130260A1 (zh) Rrc消息的配置方法、装置和系统
WO2022082690A1 (zh) 群组切换的方法、装置和系统
WO2023065108A1 (zh) 信息获取方法，信息发送方法、装置和系统
WO2023197184A1 (zh) Iab宿主设备以及传输地址配置方法
WO2022082686A1 (zh) 波束失败信息的上报方法以及装置