WO2022257808A1 - 数据传输方法、用户设备、服务节点及存储介质 - Google Patents

数据传输方法、用户设备、服务节点及存储介质 Download PDF

Info

Publication number
WO2022257808A1
WO2022257808A1 PCT/CN2022/096114 CN2022096114W WO2022257808A1 WO 2022257808 A1 WO2022257808 A1 WO 2022257808A1 CN 2022096114 W CN2022096114 W CN 2022096114W WO 2022257808 A1 WO2022257808 A1 WO 2022257808A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
target
data
transmission
signaling
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2022/096114
Other languages
English (en)
French (fr)
Inventor
陈琳
汪梦珍
罗薇
黄莹
杜伟强
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to KR1020247000392A priority Critical patent/KR20240017923A/ko
Priority to EP22819406.4A priority patent/EP4354913A4/en
Priority to US18/565,789 priority patent/US20240276243A1/en
Publication of WO2022257808A1 publication Critical patent/WO2022257808A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/24—Multipath
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/22—Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/34—Modification of an existing route
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/005—Discovery of network devices, e.g. terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/10—Interfaces between hierarchically different network devices between terminal device and access point, i.e. wireless air interface
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices

Definitions

  • the present application relates to the technical field of wireless communication, for example, to a data transmission method, user equipment, service node and storage medium.
  • D2D Device-to-Device
  • the following types of UE local transmission paths can replace the traditional transmission path through the core network: single-hop or multi-hop UE-to-UE relay, data relay across centralized units (Centralized Unit, CU), and the same distributed unit Data relay within a Distributed Unit (DU), data relay across DUs within the same centralized unit (Centralized Unit, CU), etc.
  • DU Distributed Unit
  • CU Centralized Unit
  • CU Centralized Unit
  • DU Data relay across DUs within the same centralized unit
  • the transmission path between UEs is often predetermined before data transmission, and cannot be comprehensively decided according to the actual situation, and the flexibility is low, which affects communication efficiency.
  • the present application provides a data transmission method, user equipment, service node and storage medium, so as to improve the flexibility of UE to transmit data.
  • An embodiment of the present application provides a data transmission method, including:
  • Data is transmitted according to the transmission configuration information.
  • the embodiment of the present application also provides a data transmission method, including:
  • the embodiment of the present application also provides a data transmission method, including:
  • the embodiment of the present application also provides a data transmission method, including:
  • the embodiment of the present application also provides a user equipment, including: a memory, a processor, and a computer program stored in the memory and operable on the processor, and the processor implements the above-mentioned data transmission method when executing the computer program .
  • the embodiment of the present application also provides a service node, including: a memory, a processor, and a computer program stored in the memory and operable on the processor, and the processor implements the above-mentioned data transmission method when executing the computer program .
  • the embodiment of the present application also provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the above-mentioned data transmission method is implemented.
  • FIG. 1 is a flowchart of a data transmission method provided by an embodiment
  • Fig. 2 is a flow chart of a data transmission method provided by another embodiment
  • Fig. 3 is a flow chart of a data transmission method provided by yet another embodiment
  • Fig. 4 is a flow chart of a data transmission method provided by yet another embodiment
  • FIG. 5 is a schematic diagram of establishing a PC5 unicast connection between user equipments provided by an embodiment
  • FIG. 6 is a schematic diagram of a serving node assisting UE in neighbor discovery provided by an embodiment
  • FIG. 7 is a schematic diagram of a service node forwarding discovery information provided by an embodiment
  • FIG. 8 is a schematic diagram of a core network detecting a neighboring UE provided by an embodiment
  • FIG. 9 is a schematic structural diagram of a data transmission device provided by an embodiment.
  • FIG. 10 is a schematic structural diagram of a data transmission device provided by another embodiment.
  • Fig. 11 is a schematic structural diagram of a data transmission device provided in yet another embodiment.
  • Fig. 12 is a schematic structural diagram of a data transmission device provided in yet another embodiment
  • Fig. 13 is a schematic diagram of a hardware structure of a user equipment provided by an embodiment
  • Fig. 14 is a schematic diagram of a hardware structure of a service node provided by an embodiment.
  • FIG. 1 is a flow chart of a data transmission method provided by an embodiment. As shown in FIG. 1 , the method includes step 110 and step 120 .
  • step 110 transmission configuration information is received.
  • step 120 data is transmitted according to the transmission configuration information.
  • the transmission configuration information may be configured and sent by the service node, and the service node may be a base station, an Integrated Access Backhaul (IAB) node, a DU, a CU, etc., and the transmission configuration information includes that the service node is According to the transmission path and/or radio bearer configured by the UE, the UE can use the corresponding radio bearer to transmit data on the corresponding path according to the transmission configuration information.
  • IAB Integrated Access Backhaul
  • the serving node can use the proximity information reported by the UE or the information indicated by the core network to identify the relative position between the UEs, the serving cell, the interface status of the DU or CU, etc., analyze the potential transmission path, and comprehensively consider the strategy, channel status, Load and other factors, configure the most suitable transmission path for data transmission between UE node pairs, so as to carry out corresponding transmission, ensure the arrival in the most effective way, and improve the flexibility of data transmission between UEs.
  • the current short-distance communication corresponding to direct device communication can be applied to the fields of smart cars, smart terminals, smart homes, and smart manufacturing.
  • nodes in the system are divided into management nodes (G nodes) and managed nodes (T nodes).
  • G nodes management nodes
  • T nodes managed nodes
  • a single G node manages a certain number of T nodes, and the G node connects with these T nodes to complete specific communication functions.
  • a single G node and the T nodes connected to it together form a communication domain.
  • the cockpit domain controller (Cockpit Domain Controller, CDC) can be used as the G node, and various vehicle devices (such as microphones, speakers, etc.) can be used as the T node to jointly complete the cockpit entertainment function.
  • the CDC and the on-board equipment form a communication domain.
  • the mobile phone When the mobile phone is connected to the CDC, the mobile phone can also serve as a T node in the communication domain.
  • the mobile phone In the smart car environment, the mobile phone can also be used as a G node to connect to the wearable device. At this time, the mobile phone and the wearable device form another communication domain.
  • the TV and the attached audio device form a communication domain
  • the mobile phone and the earphone form another communication domain.
  • the two communication domains can be distinguished by the advanced/general communication domain, and the resource coordination is carried out by the advanced communication domain to realize multiple Coordinated coexistence between domains.
  • the UE may correspond to the T node in the above scenario
  • the serving node may correspond to the G node in the above scenario.
  • the service node mentioned in the embodiment of the present application forwards short-distance communication data for the UE Mechanisms, such as bearer configuration, path configuration, data transmission, etc., can be applied to G nodes to forward communication data between T nodes for T nodes.
  • a UE that is not clearly specified as a source UE or a target UE, it may refer to the source UE and/or the target UE.
  • the method further includes: Step 100: Sending proximity information of a target UE.
  • the source UE before receiving the transmission configuration information, can discover the adjacent target UE, and report the adjacent information about the target UE to the serving node, so that the serving node can make a comprehensive decision.
  • the proximity information includes at least one of the following information: source UE identity (Identity, ID), target UE identity, transmission type (Cast Type), source UE application identity (Application Identity, APP ID), target UE
  • the link status includes at least one of the following: link measurement results, link load, and SL resource usage.
  • the transmission configuration information includes bearer configuration information and/or path configuration information.
  • the bearer configuration information includes at least one of the following information:
  • Uu Radio Link Control Protocol Radio Link Control, RLC
  • Uu RLC channel identification Uu Logical Channel (Logical Channel) configuration
  • service data adaptation corresponding to Sidelink Radio Bearer (SL RB) Protocol (Service Data Adaptation Protocol, SDAP) configuration
  • SL RB corresponding packet data convergence protocol packet data convergence protocol, PDCP
  • SL RB and Uu RLC channel mapping information Radio Link Control Protocol
  • the bearer configuration information includes at least one of the following information:
  • SDAP configuration corresponding to SL RB PDCP configuration corresponding to SL RB
  • PC5 RLC channel configuration PC5 logical channel configuration.
  • the bearer configuration information includes mapping information between the information type and the Uu RLC channel; wherein, the information type includes at least one of the following: discovery information (information that the source UE requests to discover the target UE or triggers a neighboring discovery process), PC5- S, PC5 radio resource control (Radio Resource Control, RRC) information, SL signaling radio bearer (Signalling Radio Bearer, SRB) identification, SL data radio bearer (Data Radio Bearer, DRB) identification.
  • discovery information information that the source UE requests to discover the target UE or triggers a neighboring discovery process
  • PC5- S PC5 radio resource control
  • RRC Radio Resource Control
  • SL signaling radio bearer Simalling Radio Bearer, SRB
  • Data Radio Bearer Data Radio Bearer
  • the path configuration information includes one of the following information: Uu transmission path; SL transmission path; Uu transmission path and SL transmission path.
  • step 120 includes:
  • the transmission configuration information including the Uu transmission path, or including the Uu RLC channel configuration and the SL SRB associated with the Uu RLC channel, or including the Uu RLC channel configuration and the mapping information between the SL RB and the Uu RLC channel, transmit the corresponding SL through the Uu interface RB data;
  • the transmission configuration information including the SL transmission path, or including the SDAP configuration corresponding to the SL RB, the PDCP configuration corresponding to the SL RB, the PC5 RLC channel configuration and/or the PC5 logical channel configuration, and transmit the corresponding SL RB data through the PC5 interface;
  • the corresponding SL RB data is transmitted through the Uu and/or PC5 interface.
  • the transmission configuration information further includes at least one of the following: data copy indication, data separation transmission indication, data division threshold, data division ratio, primary path indication, auxiliary path indication, path switching indication; wherein, the path switching indication Including at least one of the following information: source UE identity, target UE identity, SL RB identity, path indication.
  • the source UE when the source UE can transmit SL RB data through the Uu and PC5 interfaces, the SL RB data can be transmitted on the two interfaces in the manner of data replication or data separation.
  • step 120 includes: transmitting the corresponding SL RB data with the target UE through the Uu interface and the PC5 interface by means of data replication or data division.
  • the method further includes: Step 10: Sending first discovery information or SL signaling or SL data through the PC5 interface.
  • the source UE may send the first discovery information or SL signaling or SL data through the PC5 interface to discover adjacent target UEs, wherein the first discovery information may be sent directly to the target UE, or may be sent by the relay UE Forwarded to the target UE, but all transmitted through the PC5 interface.
  • the method further includes: Step 12: receiving the second discovery information or SL signaling or SL data sent by the target UE or forwarded by the relay UE through the PC5 interface;
  • the second discovery information includes at least one of the following: the application layer identifier of the target UE, the serving node identifier of the target UE, the serving cell identifier, the camped cell identifier, the maximum hop count information, the transmitted hop count information, the relay node's Node ID.
  • the source UE can receive the second discovery information or SL signaling or SL data through the PC5 interface, so as to be discovered by the adjacent target UE, wherein the second discovery information can be received directly from the target UE, or can be received by a relay forwarded by UE or service node.
  • the method further includes: Step 14: Sending local transmission capability information or transmission indication information, where the local transmission capability information or transmission indication information is used to instruct or request the serving node to transmit discovery information or SL signaling through the Uu interface or SL data.
  • the source UE may instruct or request the serving node to forward the discovery information or SL signaling or SL data to other UEs through the Uu interface.
  • the serving node may assist the source UE to discover adjacent target UEs.
  • the discovery information or SL signaling or SL data is forwarded by the serving node through the Uu interface in a unicast or broadcast or multicast manner.
  • the discovery information or SL signaling or SL data sent through the Uu interface carries the source UE identifier, the target UE identifier, and/or the SL RB identifier.
  • the service node when the discovery information or SL signaling or SL data is forwarded by the service node through MBS (Multicast Broadcast Services, multicast broadcast service) broadcast or multicast, the service node transmits the multicast control channel ( Main Control Channel, MCCH) or proprietary signaling to transmit discovery information or SL signaling or MBS broadcast or multicast configuration of SL data;
  • MBS Multicast Broadcast Services, multicast broadcast service
  • MBS broadcast or multicast configuration includes at least one of the following: Group-Radio Network Tempory Identity (G-RNTI) for broadcasting SL signaling or SL data, SL information type, multicast traffic channel (Multicast Traffic Channel, MTCH) scheduling information;
  • G-RNTI Group-Radio Network Tempory Identity
  • MTCH multicast traffic channel
  • the SL information type includes at least one of the following: SL service type, SL SRB, SL DRB, PC5-S, PC5-RRC;
  • the MTCH scheduling information includes at least one of the following: the online duration of the UE after being woken up in the Discontinuous Reception (DRX) period, and keeps active after each successful decoding of the Physical Downlink Control Channel (PDCCH) after being woken up The duration, scheduling period, and scheduling offset.
  • DRX Discontinuous Reception
  • PDCCH Physical Downlink Control Channel
  • the method further includes: step 16: receiving discovery information or SL signaling or SL data sent by the target UE and forwarded by the serving node through the Uu interface, the discovery information or SL signaling or SL data Carry source UE identity, target UE identity, and/or SL RB identity.
  • the source UE may receive discovery information or SL signaling or SL data from the target UE forwarded by the serving node through the Uu interface, and on this basis, the serving node may assist the source UE to be discovered by adjacent target UEs.
  • the serving node in response to the known UE associated with the target identifier, sends a data packet including discovery information or SL data or SL signaling to the UE associated with the target identifier in a unicast manner; wherein , UEs associated with the target identifier include UEs corresponding to the target identifier, and/or UEs interested in receiving the target identifier.
  • the target identifier may be a target UE ID, a serving cell ID of the target UE, an application ID of the target UE, and the like.
  • Step 18 sending at least one of the following information to the service node:
  • the UE ID allocated by the core network Next Generation Core, NGC
  • the target ID corresponding to the service type of interest and the transmission type corresponding to the target ID.
  • the source UE may send the above information to the serving node, and on this basis, the serving node may assist the source UE in finding a nearby target UE.
  • the method further includes: Step 112: Sending the serving node forwarding SL data instruction to the target UE.
  • the source UE may send an indication that the serving node forwards the SL data to the target UE. On this basis, the target UE is ready to receive the SL data forwarded by the serving node. SL data.
  • Step 114 In response to the target UE being in the idle or inactive state, after receiving the serving node forwarding SL data indication, the target UE enters the RRC connection state.
  • the target UE in an idle or inactive state enters an RRC connection state after receiving an instruction to forward SL data from the serving node, thereby completing preparations for receiving SL data forwarded by the serving node.
  • Step 1000 receiving local transmission instruction information sent by a network element of the core network, where the local transmission instruction information is used to instruct or request the serving node to transmit discovery information or SL signaling or SL data through the Uu interface; wherein , the local transmission indication information includes at least one of the following: serving node forwarding request or indication, source UE identity, target UE identity, source UE serving node identity, target UE serving node identity, source UE serving cell identity, target UE’s Serving cell identity, QoS flow information; wherein, the QoS flow information includes at least one of the following: QoS flow identity (QoS Flow Identity, QFI), QoS parameters.
  • the UE can determine whether the serving node can forward the discovery information or SL signaling or SL data.
  • the transmission configuration information is sent by a service node; the service node includes a base station, a DU, a centralized unit CU or an IAB node.
  • FIG. 2 is a flowchart of a data transmission method provided by another embodiment. As shown in FIG. 2 , the method includes step 210 and step 220 . It should be noted that, for the operations performed by the service node in this embodiment, for technical details not described in detail in this embodiment, reference may be made to any of the foregoing embodiments.
  • step 210 receiving proximity information about the target UE
  • step 220 transmission configuration information is sent according to the proximity information.
  • the serving node can send corresponding transmission configuration information to the source UE and the target UE by receiving the proximity information about the target UE.
  • the serving node can use the proximity information reported by the UE or the information indicated by the core network to identify the relative position between the UEs, the serving cell, the interface status of the DU or CU, etc., analyze the potential transmission path, and comprehensively consider the strategy, channel, etc. Based on factors such as state and load, configure the most suitable transmission path for data transmission between UE node pairs, so as to carry out corresponding transmission, ensure the arrival in the most effective way, and improve the flexibility of data transmission between UEs.
  • the proximity information is sent by the source UE, or by a core network element.
  • the proximity information may be reported to the serving node by the source UE after discovering the target UE, or may be sent to the serving node by the core network after discovering the source UE and the target UE.
  • the method further includes: step 200: receiving discovery information or SL signaling or SL data, the discovery information or SL signaling or SL data carrying source UE identity, target UE identity, and/or SL RB logo.
  • the serving node may assist the source UE to discover adjacent target UEs by receiving discovery information or SL signaling or SL data sent by the source UE.
  • the method further includes: Step 202: receiving local transmission capability information or transmission indication information, the local transmission capability information or transmission indication information is used to instruct or request the serving node to transmit discovery information or SL information through the Uu interface command or SL data.
  • the serving node may transmit discovery information or SL signaling or SL data through the Uu interface according to local transmission capability information or transmission instruction information of the source UE, so as to assist the source UE to discover adjacent target UEs.
  • the method further includes: Step 204: Forwarding the discovery information or SL signaling or SL data through the Uu interface in a unicast, broadcast or multicast manner.
  • the service node may forward the discovery information or SL signaling or SL data through the Uu interface, so as to assist the source UE to discover the adjacent target UE.
  • the method further includes: Step 206: When the discovery information or SL signaling or SL data is forwarded by the serving node through MBS broadcast or multicast, transmit the SL signaling through MCCH or dedicated signaling MBS broadcast or multicast configuration of order or SL data; MBS broadcast or multicast configuration includes at least one of the following: G-RNTI, SL information type, MTCH scheduling information; wherein, the SL information type includes at least one of the following: SL service type , SL SRB, SL DRB, PC5-S, PC5-RRC; MTCH scheduling information includes at least one of the following: the online duration of the UE after being awakened in the DRX cycle, the duration of activation after each successful decoding of the PDCCH after being awakened, scheduling Period, scheduling offset.
  • MBS broadcast or multicast configuration includes at least one of the following: G-RNTI, SL information type, MTCH scheduling information; wherein, the SL information type includes at least one of the following: SL service type
  • the service node before forwarding discovery information or SL signaling or SL data through MBS broadcast or multicast, the service node can transmit MBS broadcast or multicast configuration of SL signaling or SL data through MCCH or dedicated signaling , so that the UE is ready to receive forwarded discovery information or SL signaling or SL data.
  • the method in response to the UE known to be associated with the target identifier, the method further includes: Step 205: Send a data packet containing discovery information or SL data or SL signaling to the target UE in a unicast manner Identify associated UEs; wherein, the UEs associated with the target identifier include UEs corresponding to the target identifier, and/or UEs interested in receiving the target identifier.
  • the service node before forwarding the discovery information or SL signaling or SL data, the service node can determine whether the target UE can be identified according to the target identifier, and if so, the service node will include the discovery information or SL data or SL signal in a unicast manner.
  • the commanded data packet can be sent to the UE associated with the target identifier.
  • FIG. 3 is a flow chart of a data transmission method provided by yet another embodiment. As shown in FIG. 3 , the method includes step 310 and step 320 . It should be noted that, for the operations performed by the service node in this embodiment, for technical details not described in detail in this embodiment, reference may be made to any of the foregoing embodiments.
  • step 310 SL forwarding request information is sent.
  • step 320 SL forwarding response information is received.
  • the serving node of the source UE may send SL forwarding request information to the serving node of the target UE, and receive the SL forwarding response information sent by the serving node of the target UE, thereby establishing an SL forwarding tunnel, and realizing the SL forwarding tunnel between UEs across serving nodes.
  • SL data transmission between UEs improving the flexibility of data transmission between UEs.
  • the SL forwarding request information includes at least one of the following information: SL sending request, SL receiving request, first SL forwarding user plane transport layer information, QoS information, SL RB identifier, PC5-S, PC5-RRC, PC5-D, source UE identification, target UE identification or target group identification or target broadcast identification, unicast or multicast or multicast indication; wherein, the first SL forwards user plane transport layer information including general packet radio service (General Packet Radio Service, GPRS) tunnel protocol information; QoS information includes at least one of the following: PC5 Quality Indication (PC5 Quality Indication, PQI), RLC mode, QoS parameters of SL RB, QoS flow identification mapped to SL RB, QoS parameters of QoS flow .
  • PC5 Quality Indication PC5 Quality Indication
  • PQI PC5 Quality Indication
  • RLC mode QoS parameters of SL RB
  • QoS flow identification mapped to SL RB
  • the SL forwarding response information includes at least one of the following: second SL forwarding user plane transport layer information, SL RB identification accepted or not accepted, QFI accepted or not accepted, PC5-S, PC5- RRC, PC5-D, source UE ID, target UE ID or target group ID or target broadcast ID; wherein, the second SL forwarding user plane transport layer information includes GPRS tunneling protocol information of the target serving node.
  • the target service node is a service node serving the target UE.
  • the method also includes:
  • Step 330 Determine the target serving node of the discovery information or SL data or SL signaling according to the target identification contained in the discovery information or SL data or SL signaling to be forwarded, and/or, according to the discovery information or SL data or SL to be forwarded
  • the SL RB identification contained in the signaling determines the SL forwarding tunnel for SL data or SL signaling between the target serving node
  • Step 340 delivering the discovery information or SL data or SL signaling to be forwarded to the SL forwarding tunnel and forwarding to the target service node;
  • the discovery information or SL information or SL signaling is forwarded by the target serving node to the target UE, or broadcast and sent in each serving cell of the target serving node.
  • the SL forwarding request information is sent by the first service node, and the SL forwarding response information is sent by the second service node;
  • the first service node is a first base station, a first distributed unit, a first centralized unit, a first IAB node or a third distributed unit;
  • the second service node is a second base station, a second distributed unit, a second centralized unit, a second IAB node, or a third centralized unit.
  • the interaction between SL forwarding request information and SL forwarding response information may be between different base stations, between different distributed units, between different centralized units, between different IAB nodes, or Between distributed units and centralized units.
  • FIG. 4 is a flow chart of a data transmission method provided by yet another embodiment. As shown in FIG. 4 , the method includes step 410 and step 420 . It should be noted that, for the operations performed by the service node in this embodiment, for technical details not described in detail in this embodiment, reference may be made to any of the foregoing embodiments.
  • step 410 receive local transmission information of the UE
  • step 420 local transmission confirmation information is sent to the core network.
  • the service node can receive the local transmission information sent by the network elements of the core network, and send local transmission confirmation information to the core network, so that with the assistance of the core network, the proximity discovery and SL data transmission between UEs can be completed, improving Flexibility of data transmission between UEs.
  • the method further includes: Step 430: sending transmission configuration information to the UE.
  • the serving node selects appropriate transmission paths for the source UE and the target UE according to local transmission information of the UE, and sends transmission configuration information to the UE.
  • the local transmission information is sent by the network element of the core network; the local transmission information includes at least one of the following: the serving node of the UE forwards discovery information or SL signaling or SL data authorization indication, and the serving node forwards the request Or indication, source UE identity, target UE identity, serving node identity of source UE, serving node identity of target UE, serving cell identity of source UE, serving cell identity of target UE, QoS flow information; wherein, the QoS flow information Including at least one of the following: QFI, QoS parameters.
  • the local transmission confirmation information includes at least one of the following: a local forwarding response of the serving node, the QoS flow information of the source UE that can be forwarded by the serving node, the QoS flow information of the source UE that cannot be forwarded by the serving node, and the QoS flow information that cannot be forwarded by the serving node.
  • the reason for service node forwarding includes at least one of the following: a local forwarding response of the serving node, the QoS flow information of the source UE that can be forwarded by the serving node, the QoS flow information of the source UE that cannot be forwarded by the serving node, and the QoS flow information that cannot be forwarded by the serving node. The reason for service node forwarding.
  • the source UE or the target UE transmits the SL RB data through the Uu interface RLC channel.
  • the method further includes: Step 440: Responding to receiving the UE's serving node forwarding authorization indication, forwarding the UE's SL signaling or SL data.
  • the serving node will forward the data between UEs only when the UE authorizes the serving node to forward.
  • the source UE and the target UE transmit PC5-S and/or PC5-RRC through a Uu interface RLC channel with fixed configuration or default configuration.
  • the data transmission method is described below with some examples.
  • the source UE and the target UE want to perform data transmission.
  • the source UE can obtain one or more of the following information through the application server or policy control function (Policy Control Function, PCF) or pre-configuration: PC5 communication of each public land mobile network (Public Land Mobile Network, PLMN) Authorization information, the radio access type (Radio Access Type, RAT) information authorized by the UE for PC5 communication, corresponding to each PC5 RAT and the air interface parameters under the geographical area, the mapping information from the service type to the PC5 RAT and the corresponding transmission configuration ( Tx Profile), the business type of the geographical area and the corresponding timer (the timer is used to indicate the update interval of the Long Term Evolution Layer 2 (L2) source device identity assigned by the UE itself, that is, the update of the assigned Source L2 ID interval), the mapping between service types and V2X (Vehicle to everything) frequencies and geographical regions, the mapping between service types and communication modes (such as broadcast, multicast or unicast), and the target UE identification corresponding to service
  • the source UE If the application layer of the source UE wants to initiate PC5 unicast for data transmission of a certain service type, the source UE first considers whether the existing PC5 unicast link can be reused, which can be based on the application layer identifier of the target UE, also known as the opposite end Judging by whether the UE application layer ID (Peer Application Layer ID) is the same as the network layer protocol, if there is a PC5 unicast link that can be reused, you can consider modifying the existing PC5 unicast link and adding a service type for the source UE Data transmission with the target UE; otherwise, the source UE will trigger the establishment of a new PC5 unicast link.
  • the application layer ID Peer Application Layer ID
  • the source UE can use the L2 ID of the target UE as the Destination L2 ID in the initial PC5 unicast link establishment signaling and unicast Transmit the initial PC5 unicast link establishment signaling, otherwise, the source UE uses the default broadcast destination L2 ID associated with the V2X service type corresponding to the PC5 unicast link establishment and broadcasts and transmits the initial PC5 unicast link establishment signaling.
  • Fig. 5 is a schematic diagram of establishing a PC5 unicast connection between user equipments according to an embodiment.
  • the application layer of the source UE provides the application layer information of the PC5 unicast communication.
  • the application layer information includes the service type and the application layer ID of the source UE.
  • the application layer information may also include the application layer ID of the target UE.
  • the application layer of the source UE will also provide the application requirements for unicast communication.
  • the source UE or target UE can determine the PC5 QoS parameters and Packet Flow Identifier (PFI) accordingly.
  • PFI Packet Flow Identifier
  • the target UE needs to determine the target L2 ID corresponding to receiving the PC5 unicast link establishment signaling.
  • the target UE can obtain the target L2 ID corresponding to the PC5 unicast link establishment signaling in the following ways: 1) It can be found during the process of establishing the PC5 unicast link between the source UE and the target UE; 2) According to the previous V2X communication perception ( For example, an existing or previously established unicast link corresponding to the same application layer ID); 3) Obtaining from application layer service announcement information.
  • the source UE sends a Direct Communication Request (Direct Communication Request) message, which may include the application layer ID of the source UE, the optional application layer ID of the target UE, and the service type, security information.
  • a Direct Communication Request Direct Communication Request
  • the source UE can use the Source L2 ID allocated by itself.
  • the source UE can send IP (Internet Protocol, Internet Protocol) address configuration information and/or PC5 QoS flow information to the target UE.
  • IP Internet Protocol
  • PC5 QoS flow information For example, for each PC5 QoS flow, it can include PFI, corresponding QoS parameters such as PQI, MFBR, GFBR, etc., and corresponding service types.
  • the target UE can send direct communication acceptance information to the source UE, and the direct communication acceptance
  • the information can contain information about the source user, such as the application layer ID of the source UE, IP address configuration information, and the PC5 QoS flow information requested by the target UE.
  • PFI can be included, and the corresponding QoS parameters such as PQI, MFBR, GFBR, etc., and the corresponding service types.
  • UEs (in this example, if the source UE or target UE is not specified, the UE can be the source UE and/or target UE) use L2 ID node pairs for subsequent PC5- S signaling and business data transmission.
  • the UE allocates a PC5 link identifier PLI to uniquely identify a PC5 unicast link.
  • Each PC5 unicast link is associated with a unicast link configuration, which includes the application layer ID (Application Layer ID) and L2 ID of the source UE, the application layer ID and L2 ID of the target UE, and PC5 QoS flow information.
  • the UE maintains the mapping relationship between the Application Layer ID used for the PC5 unicast link and its own Source L2 ID.
  • the UE's Source L2 ID changes, it will not affect the V2X application.
  • the Application Layer ID changes, the Source L2 ID of the corresponding PC5 unicast link should also change accordingly.
  • the UE sends the PC5 link identifier (PC5 Link Identifier, PLI), the L2 ID of the source UE and the target UE, and the corresponding PC5 QoS parameters to the AS layer, so that the AS layer can maintain PLI and PC5 unicast link related information.
  • PC5 link identifier PC5 Link Identifier
  • data can be transmitted between the source UE and the target UE.
  • the source UE can send a data packet, the PLI and/or PFI information corresponding to the data packet, and optionally, the source UE and the target UE
  • the L2 ID is sent to the AS layer.
  • PC5 RRC configuration continues between the source UE and the target UE, following proprietary signaling or system information block (System Information Block, SIB) or pre-configuration (Pre-Configuration) SL RB configuration in and exchange SL DRB configuration with the peer UE through PC5 RRC message.
  • SIB System Information Block
  • Pre-Configuration pre-configuration
  • UE will create a corresponding SL DRB according to the parameters of the PC5 QoS flow, including SDAP entity (if there is no SDAP entity), PDCP entity , an RLC entity, configuring a logical channel and assigning an LC (Logical Channel, logical channel) ID to the logical channel.
  • SDAP entity if there is no SDAP entity
  • PDCP entity if there is no SDAP entity
  • RLC entity if there is no SDAP entity
  • RLC Resource Control Channel, logical channel
  • the source UE When the source UE receives the RRC reconfiguration sidelink (Reconfiguration Sidelink) configuration sent by the target UE at the opposite end, which includes a new SL DRB, the source UE can also create a corresponding SL DRB, including SDAP entities, PDCP entities, RLC entities, and logical channel configurations (Using the LC ID configured by the peer UE), in addition, if the source UE is in the connected state, and the SL DRB is configured as a bidirectional DRB, and the source UE has not yet obtained the transmission parameter configuration of the bidirectional SL DRB, the source UE sends a direct link UE information (Sidelink UE Information) requests related configuration from the base station, for example, the source UE reports the RLC mode and optional PC5 QoS configuration.
  • Sidelink UE Information Servicelink UE Information
  • the AS layer of the source UE maps the data packet received from the upper layer to the corresponding SL RB, and then assembles the data packet into a MAC (Media Access Control, Media Access Control) PDU according to the only scheduling and sends it through the PC5 unicast link for transmission.
  • MAC Media Access Control, Media Access Control
  • one Application Layer ID can be associated with one or more direct-device applications in the UE. If the UE has multiple Application Layer IDs, from the perspective of the peer UE, each Application Layer ID of the same UE can be regarded as an Application Layer ID of a different UE.
  • One or more service types may be involved in a PC5 unicast link, but they must be associated with the same Application Layer ID. For example, UE A and UE B have two PC5 unicast links, one is between UE A's peer Application Layer ID 1 and UE B's Application Layer ID 2, and the other is between UE A's peer Application Layer ID 3 and UE B's Application Layer ID 4 of UE B.
  • the source UE When the source UE wants to communicate with the target UE, assuming that the source UE has not established a PC5 unicast link with the target UE, the source UE can carry the Application Layer ID of the source UE and the Application Layer ID of the target UE in the PC5 link establishment request , and then broadcast the PC5 link establishment request, and if the target UE receives the PC5 link establishment request, it sends a response message to the source UE.
  • the source UE and the target UE can discover each other and establish a PC5 unicast link, but in some scenarios, it may be necessary to select other transmission paths, for example, SL resource congestion, or the PC5 link between the source UE and the target UE The quality of the unicast link is degraded, etc., so it is necessary to consider the appropriate SL data transmission path from the overall perspective.
  • the service node can uniformly manage the planning of data transmission paths between UEs, and configure corresponding routes and bearers, so that UEs (in this example, if no source UE or target UE is specified, the UE can be The data transmission between the source UE and/or target UE) can meet localization requirements while ensuring low delay and high efficiency.
  • the following scenarios of transmitting discovery information through the PC5 interface for proximity detection can be considered:
  • the source UE can report the neighbor information to the serving node, and the neighbor information includes any combination of the following related information of the target UE : source UE ID, target UE ID (Destination L2 ID), transmission type (Cast Type), source UE's APP ID, target UE's APP ID, target UE's serving cell ID (Serving Cell ID), target UE's serving node ID, the link state between the source UE and the target UE, the QoS information of the data flow between the source UE and the target UE, the hop count between the source UE and the target UE, and the node ID of the relay node.
  • the link status between the source UE and the target UE may further include link measurement results between the source UE and the target UE, load and/or SL resource usage between the source UE and the target UE.
  • the serving node of the source UE analyzes possible paths between the source UE and the target UE, and selects the most suitable transmission path for data transmission between the source UE and the target UE.
  • the serving node of the source UE finds that the source UE and the target UE are served by the same serving node, and the serving node finds that the data transmission between the source UE and the target UE is forwarded through the serving node with the best resource utilization, then the serving node of the source UE Bearer configuration information and/or path configuration information may be sent to the source UE.
  • the bearer configuration information received by the source UE from the serving node includes any combination of the following information: Uu RLC channel configuration (including Uu RLC channel ID, Uu RLC and/or Uu logical channel (Logical Channel) configuration), SL RB ID (including SL SRB ID or SL DRB ID), SDAP configuration corresponding to SL DRB, and PDCP configuration corresponding to SL DRB or SRB.
  • Uu RLC channel configuration can be SL RB data transmission with a specific peer UE, such as the SL DRB 3 of the target UE, that is, the Uu RLC Channel can only transmit the data of SL DRB3 between the source UE and the target UE.
  • the bearer configuration information received by the source UE from the serving node includes the SL RB information associated with the Uu RLC Channel, or the Uu RLC Channel information associated with the SL RB.
  • the SL RB can be indicated by the source UE identifier, the target UE identifier, and the SL RB identifier information.
  • Uu RLC Channel can be indicated by Uu RLC Channel ID or Logical Channel ID.
  • the Uu RLC Channel configured by the serving node of the source UE for the source UE can also be used to transmit data between the source UE and different peer UEs or target UEs.
  • the SDAP configuration of the SL RB can include the mapping from the QoS flow of the source UE to the SL RB.
  • the source UE may also receive a mapping configuration between SL RBs and Uu RLC Channels, indicating which SL RBs can be mapped to which Uu RLC Channel.
  • the path configuration information may be a Uu transmission path, an SL transmission path, or information about a Uu transmission path and an SL transmission path.
  • Path configuration information can be implicitly or explicitly indicated.
  • the implicit configuration can be inferred by carrying configuration information.
  • the service node only configures the Uu RLC Channel for the UE, and configures the SL SRB associated with the Uu RLC Channel or configures the mapping between the SL RB and the Uu RLC Channel, which means that the service node instructs the UE to communicate with the peer through Uu transmission Corresponding SL RB data between UEs.
  • the serving node only configures the SDAP configuration, PDCP configuration, RLC channel configuration, and logical channel configuration corresponding to the SL RB for the UE, where the SDAP/PDCP/RLC/logical channel configurations all correspond to the SL or PC5 interface, then the implicit It means that UE transmits corresponding SL RB data through PC5.
  • the serving node configures Uu RLC Channel and PC5 RLC channel for UE at the same time, it implies that UE can choose Uu or PC5 for SL RB data transmission, or UE can perform SL RB through Uu and PC5 at the same time data transmission.
  • the granularity of path configuration information can be each group of UE node pairs, or each SL RB.
  • all SL RB transmissions between them use the same path. If it is each SL RB, it corresponds to a specific source UE, target UE, and SL RB ID combination, and the data transmission of the SL RB uses the same path (e.g. Uu, SL, or Uu and SL). This means that within a UE node pair, different SL RBs can use different paths for transmission.
  • the target UE may receive a similar configuration from the serving node.
  • the SL data can be transmitted through the Uu RLC Channel or PC5 RLC Channel.
  • PC5 two hops forwarding between the source UE and the target UE through the relay UE: the source UE sends the first discovery information including the application layer ID corresponding to the target UE through the PC5 interface. Assuming that the surrounding UE1 receives the first discovery information, and UE1 has the capability of forwarding PC5 information, UE1 can further forward the first discovery information.
  • the target UE If the target UE is near UE1 and receives a message containing the application layer ID corresponding to the target UE
  • the first discovery information the target UE sends the second discovery information, which may contain at least one of the following information: the application layer ID of the target UE, the serving node identifier of the target UE, the serving cell identifier, the resident cell identifier, and the maximum hop count information , the transmitted hop count information, and the node ID of the relay node.
  • the second discovery message After receiving the second discovery message, UE1 forwards it on the PC5 interface.
  • the source UE After receiving the second discovery message, the source UE sends the proximity information of the target UE to the serving node.
  • the proximity information includes at least one of the following information: source UE identity, Destination L2 ID, transmission type (Cast Type), APP ID of source UE, APP ID of target UE, Serving cell ID of target UE, serving node identifier of target UE, link status between source UE and target UE, source UE QoS information of the data flow between the source UE and the target UE, the number of hops between the source UE and the target UE, and the node identifier of the relay node.
  • the serving node of the source UE After receiving the above proximity information, the serving node of the source UE analyzes the possible paths between the source UE and the target UE, selects the most suitable transmission path for the data transmission between the source UE and the target UE, and sends the corresponding bearer configuration information and/or path configuration information.
  • the first discovery information sent by the source UE may further include information about the maximum number of hops allowed to be forwarded.
  • UE1 around the source UE receives the first discovery information, and UE1 has the capability of forwarding PC5 information, UE1 can further forward the first discovery information, and before UE1 forwards the first discovery information, UE1 will reduce the maximum hop count by 1 .
  • UE2 around UE1 receives the first discovery information
  • UE2 may continue to forward the first discovery information.
  • UE2 needs to decrement the maximum hop count information by 1 before forwarding.
  • the first discovery information may continue to be sequentially forwarded by neighboring UEs until the maximum hop count information in the first discovery message is reduced to 0.
  • the target UE sends the second discovery information, which may contain at least one of the following information: the application layer ID of the source UE, the target UE The application layer ID, serving node ID, serving cell ID, resident cell ID information, maximum hop count information, and transmitted hop count information.
  • the maximum hop information contained in the second discovery information is similar to the maximum hop information contained in the first discovery information, that is, the maximum hop information is reduced by 1 every time a relay forwarding node passes through, until the maximum hop information is reduced to 0, Then the second discovery information is received by the source UE and cannot be forwarded.
  • the target UE can set the transmitted hop count information in the second discovery information to 1, and when the adjacent UE receives the second discovery information, if it continues to forward, it will transmit the transmitted hop count information. Add 1 to the number information until the source UE receives the second discovery information.
  • the target UE After the source UE receives the second discovery information sent by the target UE, it can send the proximity information of the target UE to the serving node.
  • the proximity information includes at least one of the following information: Destination L2 ID, Serving cell ID, and the distance between the source UE and the target UE. Hop count, the QoS information of the data flow between the source UE and the target UE.
  • the serving node of the source UE After receiving the above proximity information, the serving node of the source UE analyzes the possible paths between the source UE and the target UE, selects the most suitable transmission path for the data transmission between the source UE and the target UE, and sends the corresponding Bearer and routing configuration.
  • each relay node when the first discovery information is forwarded by adjacent relay nodes, each relay node may include its own node identifier in the first discovery information, and the node identifier may be an L2 ID or a network assigned logo.
  • the target UE can transmit the second discovery message to the relay node through unicast according to the node identification list of the relay node carried in the first discovery information, and then pass through the relay node in turn forwarded until reaching the source UE.
  • the source UE sends the proximity information of the target UE to the serving node, it may carry node identities of all relay nodes passed between the source UE and the target UE.
  • the service node may dynamically update path configuration information according to channel status, data flow, load conditions, etc., such as switching from an SL transmission path to a Uu transmission path, or from a Uu transmission path to an SL transmission path, or Transmit from the Uu transmission path to the Uu transmission path and the SL transmission path for simultaneous transmission.
  • the serving node can further configure the UE to transmit data corresponding to the SL RB on the two paths in a data duplication (Data Duplication) or data split (Data Split) manner.
  • Data Duplication data duplication
  • Data Split data split
  • the serving node can further send a data copy instruction to the UE, and the source UE encrypts the data packet with SL PDCP and delivers the data packet to Uu RLC Channel and PC5 RLC Channel for transmission.
  • the target UE at the opposite end submits them to the SL PDCP entity for sorting, discarding duplicate packets, and other processing.
  • the serving node may further send the data splitting threshold, data splitting ratio, primary path indication, secondary path indication and/or path switching indication, etc. to the UE.
  • the path switch indication includes source UE identity, target UE identity, SL RB identity and/or path indication.
  • the UE can transmit the corresponding SL RB data in the form of data division according to the information configured by the serving node.
  • the specific information can include any combination of the following information: source UE identity, target UE identity, SL RB ID, path indication, data replication or data separation transmission indication.
  • the path indication can be Uu, SL, or Uu and SL.
  • a bitmap may be used to indicate the corresponding path.
  • the serving node assists in performing UE proximity discovery.
  • Fig. 6 is a schematic diagram of a serving node assisting a UE in performing proximity discovery provided by an embodiment.
  • UE1 that is, the source UE
  • UE2 that is, the target UE
  • the discovery information can include any combination of the following information: the application layer ID of the source UE, The application layer ID, service type, security information, and QoS information of the target UE.
  • the discovery information is forwarded by the serving node 1 to the UE2 served by the serving node 1 .
  • UE1 can transmit the discovery message through the Uu RLC Channel configured by the serving node 1, or transmit the discovery message through the Uu SRB.
  • UE1 can send local transmission capability information (also referred to as transmission instruction information) to serving node 1, thereby instructing or requesting serving node 1 to transmit through the Uu interface Discovery message or SL signaling or data.
  • Fig. 7 is a schematic diagram of a service node forwarding discovery information provided by an embodiment. As shown in Figure 7. After receiving the local transmission capability information, serving node 1 sends Uu RLC Channel configuration to UE1. In addition, service node 1 can configure the mapping of information types to Uu RLC Channel, where the information types can be any combination of the following types: discovery information, PC5 connection establishment information, PC5 connection modification information, PC5 connection release information, and PC5 Keep Alive information , security message, PC5-S, PC5-RRC, SL SRB ID, SL DRB ID. Similarly, UE2 may also send local transmission capability information to serving node 1, so as to instruct or request serving node 1 to transmit a discovery message or SL signaling or SL data through the Uu interface.
  • discovery information PC5 connection establishment information
  • PC5 connection modification information PC5 connection release information
  • PC5 Keep Alive information security message
  • PC5-S PC5-RRC
  • SL SRB ID SL DRB ID
  • UE2 may also send
  • Serving node 1 sends Uu RLC Channel configuration to UE2 after receiving the local transmission capability information.
  • service node 1 can configure the mapping of information types to Uu RLC Channel, where the information types can be any combination of the following types: discovery information, PC5 connection establishment information, PC5 connection modification information, PC5 connection release information, and PC5 Keep Alive information , security message, PC5-S, PC5-RRC, SL SRB ID, SL DRB ID.
  • the discovery information sent by UE1 may encapsulate the adaptation sub-header, which includes the source UE identifier, the target UE identifier and/or the SL RB identifier.
  • the service node 1 can forward the discovery information through the Uu interface. If service node 1 knows that the target UE ID contained in the discovery information corresponds to UE2, then service node 1 can send the discovery information to UE2 through unicast; if service node 1 does not know that the target UE ID contained in the discovery information corresponds to UE2, or UE2 is in an inactive state or an idle state, then the serving node 1 can broadcast and send the discovery information.
  • the discovery information can be transmitted by defining a new SIB, or transmitted through MBS broadcast or multicast.
  • the service node 1 can be a UE that supports the relay of SL data or SL signaling by the service node, or a UE that requests the service node to relay and forward SL signaling or SL data.
  • G-RNTI for broadcasting SL signaling or SL data.
  • serving node 1 can send MBS broadcast or multicast configuration of SL signaling or SL data to UE through MCCH or dedicated signaling.
  • MBS broadcast or multicast configuration can contain any combination of the following information: G-RNTI, SL information Type, MTCH scheduling information, etc.
  • the SL information type can include any combination of the following information: SL service type, SL SRB ID, SL DRB ID, PC5-S or PC5-RRC, etc.
  • the MTCH scheduling information can include the online duration (ondurationtimer) after the UE is awakened in the DRX cycle, the duration of activation after each successful decoding of the PDCCH after being awakened (drxInactivitytimer), the scheduling period, the scheduling offset, the scheduling period, and the scheduling offset amount etc.
  • the UE2 interested in receiving the SL signaling or SL data forwarded by the serving node 1 receives the discovery information sent by the serving node 1 .
  • UE2 finds that it is interested in the service type contained in the discovery information or that the application layer ID of UE2 corresponds to the application layer ID of the target UE contained in the discovery information, then UE2 can send a discovery message to service node 1 through Uu RLC Channel or SRB Response message.
  • the discovery response message can be broadcast.
  • broadcasts can be transmitted by defining SIBs, or by MBS broadcast or multicast. The process of MBS broadcasting or multicasting is similar to the process of sending discovery information by the service node described above.
  • UE1 After UE1 receives the discovery response information sent by serving node 1, it can complete the proximity discovery process with UE2. UE1 can report the discovered UE2 information to serving node 1, such as including at least one of the following information: source UEID, target UEID, source UE's application identification APP ID, target UE's APP ID, target UE's Serving cell ID, UE1 and QoS information of the data flow between UE2. After receiving the above information, serving node 1 analyzes the possible paths between UE1 and UE2, selects the most suitable transmission path for data transmission between UE1 and UE2, and sends corresponding bearer configuration information and /or path configuration information.
  • serving node 1 analyzes the possible paths between UE1 and UE2, selects the most suitable transmission path for data transmission between UE1 and UE2, and sends corresponding bearer configuration information and /or path configuration information.
  • the serving node can forward PC5 signaling messages between UEs, PC5 discovery messages, PC5 RRC signaling and PC5 data in the above manner.
  • the UE sends the above-mentioned PC5-related signaling or messages or data to the service node, it adopts unicast mode, and the service node can select according to the transmission type (Cast Type) of the signaling or data when forwarding the PC5-related signaling or messages or data downlink. Broadcast, multicast or unicast transmission is adopted on the Uu port.
  • PC5 signaling itself corresponds to PC5 interface broadcast transmission
  • the service node transmits downlink through Uu interface in broadcast mode
  • PC5 signaling itself corresponds to PC5 interface unicast transmission
  • service node downlink transmits through Uu interface through unicast mode.
  • the data packet can carry the transmission type of PC5-related signaling or messages or data, the source UE identification (Source ID) and/or the target UE identification (Destination ID).
  • the UE sends the Cast Type corresponding to the Destination ID to the serving node before sending PC5-related signaling or messages or data to the serving node.
  • the service node After receiving the Cast Type information corresponding to the data packet containing PC5-related signaling or messages or data, the service node can transmit the corresponding Cast Type on the Uu port.
  • the service node can send PC5-related signaling or messages or data through unicast
  • the data packets are sent to one or more UEs.
  • the Destination ID can be the ID allocated by the UE itself, or the ID configured for the UE by the serving node or NGC.
  • the UE can send the L2 ID allocated by itself or the ID allocated by NGC to the service base station.
  • the UE can send the Destination ID and/or the corresponding Cast Type corresponding to the service type it is interested in receiving to the base station.
  • Example 3 shows proximity discovery and/or data forwarding between UEs served by the same serving node through the serving node.
  • proximity discovery and/or data forwarding between UEs served by different serving nodes may be considered.
  • UE2 assuming that UE2 (that is, the source UE) wishes to perform data transmission with UE3 (that is, the target UE), UE2 assembles the direct communication request information, and the content contained in the direct communication request information can refer to any of the above-mentioned example 1.
  • UE2 sends the direct communication request information to service node 1 .
  • the service node 1 After the service node 1 receives the direct communication request information, if it can identify that the target UE of the direct communication request is served by the service node 1 through the target identifier contained in the direct communication request information, the service node 1 can forward the direct communication request information to UE3; otherwise , the service node 1 broadcasts and sends the direct communication request information within the scope of each cell.
  • the service node 1 broadcasts and sends the direct communication request information within the scope of each cell.
  • UE3 is not in the service area of service node 1 but is served by service node 2 , then service node 1 can send direct communication request information to adjacent service node 2 through the Xn interface.
  • Xn GTP GPRS Tunnel Protocol, GPRS Tunnel Protocol
  • Xn GTP-U tunnels can be established between the service node 1 and the service node 2 for forwarding of SL signaling and/or SL data.
  • These Xn GTP-U tunnels may be dedicated pilot (UE-specific), or non-dedicated pilot (non-UE-specific) or dedicated radio bearer (SL RB specific).
  • the UE-specific GTP-U tunnel corresponds to the SL signaling and/or SL data forwarding between two UE pairs served by the service node 1 and the service node 2 respectively; the SL RB specific Xn GTP-U tunnel, then Corresponding to one or more SL RBs between two UE pairs served by serving node 1 and serving node 2 respectively.
  • the SL-RB specific GTP-U tunnel may correspond to one SL RB, or may correspond to multiple SL RBs.
  • non-UE-specific Xn GTP-U tunnels can be used to forward broadcast or multicast data between UEs across serving nodes. In an example, corresponding to different broadcast or multicast target identities, it is possible to establish different non-UE-specific Xn GTP-U tunnels.
  • the GTP-U tunnel for forwarding SL signaling or SL data can be established according to the process shown in FIG. 3 .
  • Service node 1 sends an SL forwarding request to service node 2, which may contain any combination of the following information: SL sending request, SL receiving request, first SL forwarding user plane transport layer information, QoS information, SL-RB ID, PC5-S, PC5-RRC, PC5-D, source UE ID, target UE ID or target group ID or target broadcast ID, communication type (unicast or broadcast or multicast) indication.
  • the first SL forwarding user plane transport layer information may include GTP tunnel information, such as transport layer address and GTP-TEID (Tunnel Endpoint Identifier, tunnel endpoint identifier); QoS information may include any combination of the following information: PQI, RLC mode, SL The QoS parameter of RB is mapped to the QoS flow identifier of SL RB, and the QoS parameter of QoS flow.
  • GTP tunnel information such as transport layer address and GTP-TEID (Tunnel Endpoint Identifier, tunnel endpoint identifier)
  • QoS information may include any combination of the following information: PQI, RLC mode, SL
  • the QoS parameter of RB is mapped to the QoS flow identifier of SL RB, and the QoS parameter of QoS flow.
  • the SL forwarding response information can contain any combination of the following information: second SL forwarding user plane transport layer information, SL-RB ID, accepted QFI, PC5-S, PC5-RRC, PC5-D, source UE ID, target UE ID Or Target Group ID or Target Broadcast ID.
  • the second SL forwarding user plane transport layer information may include GTP tunnel information, such as transport layer address and GTP-TEID.
  • the first SL forwarding user plane transport layer information contained in the SL forwarding request information corresponds to the transport layer information on the serving node 1 side
  • the second SL forwarding user plane transport layer information contained in the SL forwarding response information corresponds to the service node 2 side transport layer information.
  • Transport layer information is included in the transport layer information.
  • SL forwarding user plane transport layer information in the SL forwarding request information and SL forwarding response information, corresponding to an SL-RB ID, there is a corresponding SL forwarding user plane transport layer information; if it is corresponding to UE-specific GTP-U tunnel, corresponding to a source UE identity and a target UE identity, there is a corresponding SL forwarding user plane transport layer information; if it is a non-UE specific GTP-U tunnel corresponding to broadcast or multicast, then Corresponding to a target group ID or target broadcast ID, there is an SL forwarding user plane transport layer information; if it is a non-UE specific GTP-U tunnel corresponding to different PC5 signaling types, it corresponds to a PC5-S or PC5 - RRC or PC5-D type, there is one SL to forward the user plane transport layer information. In addition, it is also possible to consider mapping one or more SSL SRBs or DRBs to an Xn GTP-U tunnel.
  • service node 1 can forward the direct communication request information received from UE1 to the adjacent service node 2 through the Xn interface, and service node 2 receives the direct communication request After information, if it can be identified that the target UE of the direct communication request is served by the serving node 2 through the target identifier contained in the direct communication request information, then the serving node 2 can forward the direct communication request information to UE3; otherwise, the serving node 2 in each cell Broadcast sends a direct communication request message.
  • UE3 receives the direct communication request information sent by service node 2 . If UE3 finds that it is interested in the service type or UE3's UE ID corresponds to the target UE ID or application ID contained in the direct communication request information, then UE3 can send direct communication response information to serving node 2. After receiving the direct communication response information, the service node 2 sends the direct communication response information to the service node 1 through the SL forwarding tunnel of the Xn interface. The serving node 1 may send the direct communication response information to the UE1 in a unicast or broadcast manner.
  • the PC5 connection establishment between the UEs served by the adjacent serving node is realized, and the PC5 RRC signaling can be further forwarded between UE2 and UE3 through the serving node to establish SL DRB, and through the service node's Forwarding for SL data transmission.
  • the serving node can perceive the proximity between the UE node pair, and the subsequent serving node can configure for the UE whether to use the serving node forwarding or through the device direct link Transfer PC5 data.
  • This embodiment discusses a scenario where the UE for local transmission is in an idle or inactive state (idle or inactive).
  • UE1 that is, the source UE
  • UE2 that is, the target UE
  • UE1 can assemble discovery information, where the discovery information can include any combination of the following information: Application layer ID of the source UE, application layer ID of the target UE, service type, security information, and QoS information.
  • the UE1 can transmit the discovery information through the Uu RLC Channel configured by the serving node, or transmit the discovery information through the Uu SRB. After the service node 1 receives the discovery information, the service node 1 can forward the discovery information through the Uu interface.
  • Service node 1 may send the discovery message by broadcast.
  • the specific broadcast can transmit discovery information by defining a new SIB, or transmit by MBS broadcast or multicast.
  • the service node 1 can be a UE that supports local transmission (that is, the service node relays SL data or SL signaling) or a UE that requests the service node to relay and forward SL signaling or SL data Configure the G-RNTI used to broadcast SL signaling or data.
  • the serving node 1 can send SL signaling or MBS broadcast or multicast configuration of SL data to UE through MCCH or dedicated signaling.
  • the UE2 in the RRC_IDLE or RRC_INACTIVE state receives the discovery information broadcast by the serving node 1 . Assuming that UE2 is interested in the service type or that the application layer ID of UE2 corresponds to the application layer ID of the target UE contained in the discovery information, UE2 can enter the connected state and send discovery response information to the service node 1 . After receiving the discovery response information, service node 1 sends the discovery response information to UE1. After UE1 receives the discovery response information sent by serving node 1, it can complete the proximity discovery process with UE2. UE1 can report the discovered information of UE2 to service node 1.
  • service node 1 After receiving the above information, service node 1 analyzes the possible paths between UE1 and UE2, selects the most suitable transmission path for data transmission between UE1 and UE2 and Send corresponding bearer configuration information and/or path configuration information to UE1 and/or UE2.
  • UE2 in the RRC_IDLE or RRC_INACTIVE state may also send discovery response information through the PC5 interface after receiving the discovery information broadcast by the serving node 1 . If UE1 can receive the discovery response information sent by UE2, UE1 completes the proximity discovery process with UE2. UE1 can report the discovered neighbor information about UE2 to serving node 1, such as including at least one of the following information: UE1 L2 ID, UE2 L2ID, UE1 APP ID, UE2 APP ID, serving cell ID of UE2, data between UE1 and UE2 Flow QoS information.
  • serving node 1 After receiving the above proximity information, serving node 1 analyzes possible paths between UE1 and UE2, and selects the most suitable transmission path for data transmission between UE1 and UE2. Assuming that the serving node 1 configures the UE1 to use the serving node to forward PC5 or SL data, the UE1 can send the base station forwarding data instruction to the UE2 through the PC5 interface. After receiving the indication information, UE2 enters the RRC connection state, receives the transmission of the serving node 1 or the relevant configuration of the base station forwarding data, and subsequently forwards the data between UE1 and UE2 through the serving node 1.
  • the base station forwarding data instruction sent by UE1 to UE2 can be encapsulated in PC5 signaling, but sent to service node 1 through Uu interface, and then service node 1 further broadcasts to UE2 in RRC_IDLE or RRC_INACTIVE state.
  • UE2 After receiving the indication information, UE2 enters the RRC connection state, receives the local transmission of the serving node 1 or the related configuration of the base station forwarding data, and subsequently transmits the data between UE1 and UE2 through the serving node 1.
  • This example presents a scenario where the core network detects the proximity of UE1 and UE2 and instructs the serving node to forward data between UE1 and UE2 through local transmission.
  • Fig. 8 is a schematic diagram of a core network detecting a neighboring UE provided by an embodiment.
  • UE1 and UE2 are served by the same service node, and the data transmission between UE1 and UE2 is realized through PDU (Protocol Data Unit) session (Session).
  • PDU Protocol Data Unit
  • Session the data sent by UE1 to UE2 passes through the service node, the core network, then to the application server, then to the core network, the service node, and finally sent from the service node to UE2.
  • the local switch (Local Switch) of the core network is introduced, that is, the core network element SMF (Session Management Function, session management function) determines the forwarding rules of the data PDU and provides it to the core network element UPF (User Plane Function, user plane function), UPF can determine the local transmission of some data streams according to the IP address of the data packet, that is, directly deliver the data packet sent from UE1 to UE2 from the UPF of UE1 to UE2 without going through the application server The UPF of UE2, the UPF of UE2 sends to the serving node of UE2, and finally the serving node of UE2 sends the data packet to UE2.
  • SMF Session Management Function, session management function
  • UPF receives the data packet from UE1, it will directly deliver the data packet to the PDU session corresponding to UE2, and send it to the serving node of UE2, and finally the serving base station of UE2 will send the data packet Send to UE2.
  • the core network element such as SMF can judge whether the PDU sessions of the two UEs correspond to the PDU sessions according to the source and destination IP addresses of the data packets. belong to the same local area network or local transmission group, the SMF can inform the core network element such as the identification information of the two UEs corresponding to the AMF (Access and Mobility Management Function, access and mobility management function). After receiving the information, the core network element such as the AMF further judges the serving cell and/or serving node information of the two UEs. Generally speaking, when the UE accesses the network, the serving node will send the location information of the UE to the AMF.
  • AMF Access and Mobility Management Function
  • the location information of the UE can be NCGI (NR cell global identifier), TAI (Tracking Area Identity, tracking area identifier), PScell (Primary Serving Cell, main serving cell) information, and the time stamp (Time Stamp) corresponding to the location information.
  • AMF can share the proximity information and/or data transmission information of UE1 and UE2 Inform the serving nodes of UE1 and UE2, for example, AMF sends any combination of local transmission information of UE1 and UE2 to the serving node of UE1: serving node forwarding request or indication, QoS flow information such as QFI, QoS parameters, peer UE identity, peer The serving node ID of the UE, and the serving cell ID of the peer UE.
  • the serving node of UE1 can judge whether to perform local data forwarding of the serving node according to the QoS parameters and/or air interface resource conditions.
  • the serving node can send any combination of local transmission confirmation information of UE1 and UE2 to the AMF: the serving node forwards the response, the QoS flow information that can be forwarded by the serving node such as QFI, QoS parameters of the QoS flow, and the identity of the peer UE , the serving service node identifier of the peer UE, the serving cell identifier of the peer UE, the QoS flow information of UE1 such as QFI that cannot be forwarded by the serving node, and the reason why the serving node cannot forward it.
  • the service node After the service node decides which QoS flow to forward, the service node configures Uu RLC Channel for UE1 and/or UE2 to transmit the data forwarded by the service node between UE1 and UE2. In addition, the serving node configures the UE identity corresponding to UE2 for UE1. Before data is forwarded between UE1 and UE2 through the service node, UE1 and UE2 can use the Uu RLC Channel configured by the service node to transmit PC5-S signaling and/or PC5-RRC, thereby completing PC5 connection establishment, security authentication, and secret key establishment And/or related configuration of SL RB.
  • the serving node can send to UE1 and/or UE2 the configuration of PDCP and/or SDAP corresponding to SL RB, the configuration of RLC entity and logical Channel corresponding to Uu RLC Channel, and/or the configuration of SL RB to Uu RLC Channel.
  • the SDAP configuration of SL RB includes which QoS flow is mapped to SL RB, that is, QFI is mapped to SL RB.
  • the base station sends the mapping from QFI to PFI and/or the mapping from PFI to SL RB to the UE.
  • UE1 and UE2 can map the data packets corresponding to QoS flow to SL RB and transmit them through Uu RLC Channel.
  • SL SRB and/or PC5-S signaling and/or PC5 RRC signaling can be delivered through a fixed configuration or a default configured Uu RLC channel.
  • the serving node receives a forwarding authorization instruction corresponding to a certain UE from the AMF. Node local forwarding.
  • the AMF sends the local transmission information of UE1 and UE2 to UE1, and the local transmission information includes any of the following information Combination:
  • the service node forwards the request or instruction, and the QoS flow information that can be forwarded by the service node, such as QFI, QoS parameters, peer UE ID, peer UE's serving node ID, and peer UE's serving cell ID.
  • UE1 can send a local forwarding request instruction to the service node, establish a PC5 connection through the forwarding of the service node, and transmit the data corresponding to the QoS flow through the forwarding of the service node.
  • Fig. 9 is a schematic structural diagram of a data transmission device provided by an embodiment. As shown in Figure 9, the data transmission device includes:
  • the configuration information receiving module 510 is configured to receive transmission configuration information
  • the data transmission module 520 is configured to transmit data according to the transmission configuration information.
  • the UE transmits data according to the transmission configuration information
  • the service node can analyze potential transmission paths, comprehensively consider factors such as strategies, channel states, and loads, and configure the most suitable data transmission between UE node pairs.
  • the transmission path so as to perform corresponding transmission, ensure the arrival in the most effective way, and improve the flexibility of data transmission between UEs.
  • the apparatus further includes: a proximity information sending module configured to send the proximity information of the target user equipment UE.
  • the proximity information includes at least one of the following information: source UE identity, target UE identity, transmission type, source UE application identity, target UE application identity, target UE serving cell identity, target UE serving node ID, the link status between the source UE and the target UE, the quality of service QoS of the data flow between the source UE and the target UE, the hop between the source UE and the target UE
  • the number is the node identifier of the relay node; wherein, the link status includes at least one of the following: link measurement results, link load, and SL resource usage.
  • the transmission configuration information includes bearer configuration information and/or path configuration information.
  • the bearer configuration information includes at least one of the following information: Uu radio link layer control protocol RLC channel configuration; Uu RLC channel identifier; Uu logical channel configuration; direct link radio bearer SL RB corresponding service data adaptation Protocol SDAP configuration; packet data convergence protocol PDCP configuration corresponding to SL RB; mapping information of SL RB and Uu RLC channel.
  • the bearer configuration information includes at least one of the following information: SDAP configuration corresponding to SL RB, PDCP configuration corresponding to SL RB, PC5 RLC channel configuration, and PC5 logical channel configuration.
  • the bearer configuration information includes mapping information between information types and Uu RLC channels; wherein, the information types include at least one of the following: discovery information, PC5-S, PC5 radio resource control RRC information, SL signaling radio The SRB flag is carried, and the SL data radio carries the DRB flag.
  • the path configuration information includes one of the following information: Uu transmission path; SL transmission path; Uu transmission path and SL transmission path.
  • the data transmission module 520 is configured to:
  • the transmission configuration information including the Uu transmission path, or including the Uu RLC channel configuration and the SL SRB associated with the Uu RLC channel, or including the Uu RLC channel configuration and the mapping information between the SL RB and the Uu RLC channel, transmit through the Uu interface Corresponding SL RB data;
  • the transmission configuration information including the SL transmission path, or including the SDAP configuration corresponding to the SL RB, the PDCP configuration corresponding to the SL RB, the PC5 RLC channel configuration and/or the PC5 logical channel configuration, and transmit the corresponding SL RB data through the PC5 interface;
  • the transmission configuration information including the SL transmission path and the Uu transmission path, or including the Uu RLC channel configuration and the PC5 RLC channel configuration corresponding to the SL RB, transmit the corresponding SL RB data through the Uu and/or PC5 interface.
  • the transmission configuration information further includes at least one of the following:
  • Data copy indication data separation transmission indication, data division threshold, data division ratio, main path indication, auxiliary path indication, path switching indication;
  • the path switching indication includes at least one of the following information: source UE identity, target UE identity, SL RB identity, path indication.
  • the data transmission module is set to:
  • the corresponding SL RB data is transmitted with the target UE through the Uu interface and the PC5 interface by means of data replication or data segmentation.
  • the device also includes:
  • the first information sending module is configured to send the first discovery information or SL signaling or SL data through the PC5 interface.
  • the device further includes: a second information receiving module, configured to receive the second discovery information or SL signaling or SL data sent by the target UE or forwarded by the relay UE through the PC5 interface;
  • the second discovery information includes at least one of the following: the application layer identifier of the target UE, the serving node identifier of the target UE, the serving cell identifier, the camped cell identifier, maximum hop count information, transmitted hop count information, The node ID of the relay node.
  • the device further includes: a transmission instruction sending module, configured to send local transmission capability information or transmission instruction information, and the local transmission capability information or transmission instruction information is used to instruct or request the service node to transmit discovery through the Uu interface Information or SL signaling or SL data.
  • a transmission instruction sending module configured to send local transmission capability information or transmission instruction information, and the local transmission capability information or transmission instruction information is used to instruct or request the service node to transmit discovery through the Uu interface Information or SL signaling or SL data.
  • the discovery information or SL signaling or SL data is forwarded by the serving node through the Uu interface in a unicast or broadcast or multicast manner.
  • the discovery information or SL signaling or SL data sent through the Uu interface carries the source UE identifier, the target UE identifier, and/or the SL RB identifier.
  • the service node when the discovery information or SL signaling or SL data is forwarded by the service node through MBS broadcast or multicast, the service node transmits the discovery information through a multicast control channel MCCH or dedicated signaling or MBS broadcast or multicast configuration of SL signaling or SL data;
  • the MBS broadcast or multicast configuration includes at least one of the following: radio network temporary identifier G-RNTI for broadcasting SL signaling or SL data, SL information type, multicast traffic channel MTCH scheduling information;
  • the SL information type includes at least one of the following: SL service type, SL SRB, SL DRB, PC5-S, PC5-RRC;
  • the MTCH scheduling information includes at least one of the following: the online duration of the UE after being awakened in the discontinuous reception DRX cycle, the duration of activation after each successful decoding of the physical downlink control channel PDCCH after being awakened, the scheduling period, and the scheduling offset .
  • the device further includes: a discovery information receiving module, configured to receive discovery information or SL signaling or SL data sent by the target UE and forwarded by the serving node through a Uu interface, the discovery information or SL signaling Order or SL data carries source UE identity, target UE identity, and/or SL RB identity.
  • a discovery information receiving module configured to receive discovery information or SL signaling or SL data sent by the target UE and forwarded by the serving node through a Uu interface, the discovery information or SL signaling Order or SL data carries source UE identity, target UE identity, and/or SL RB identity.
  • the serving node in response to the known UE associated with the target identifier, the serving node sends a data packet including discovery information or SL data or SL signaling to the UE associated with the target identifier in a unicast manner ;
  • the UE associated with the target identifier includes a UE corresponding to the target identifier, and/or a UE interested in receiving the target identifier.
  • the device further includes: a second information sending module configured to send at least one of the following information to the service node:
  • the device further includes: a forwarding indication sending module configured to send the serving node forwarding SL data indication to the target UE.
  • the target UE in response to the target UE being in an idle or inactive state, the target UE enters an RRC connected state after receiving an instruction from the serving node to forward SL data.
  • the device further includes: a transmission indication receiving module, configured to receive local transmission indication information sent by a network element of the core network, the local transmission indication information is used to instruct or request the service node to transmit discovery information or SL signaling or SL data;
  • a transmission indication receiving module configured to receive local transmission indication information sent by a network element of the core network, the local transmission indication information is used to instruct or request the service node to transmit discovery information or SL signaling or SL data;
  • the local transmission indication information includes at least one of the following: serving node forwarding request or indication, source UE identity, target UE identity, source UE serving node identity, target UE serving node identity, source UE serving cell identity, Target UE's serving cell identity, QoS flow information;
  • the QoS flow information includes at least one of the following: QoS flow identifier QFI, QoS parameters.
  • the transmission configuration information is sent by a service node; the service node includes a base station, a distributed unit DU, a centralized unit CU or an integrated access backhaul IAB node.
  • the data transmission device proposed in this embodiment and the data transmission method proposed in the above-mentioned embodiments belong to the same inventive concept, and the technical details not described in detail in this embodiment can be referred to any of the above-mentioned embodiments, and this embodiment has and executes a data transmission method Same beneficial effect.
  • Fig. 10 is a schematic structural diagram of a data transmission device provided by yet another embodiment. As shown in Figure 10, the data transmission device includes:
  • the proximity information receiving module 610 is configured to receive the proximity information about the target UE
  • the configuration information sending module 620 is configured to send transmission configuration information according to the proximity information.
  • the data transmission apparatus of this embodiment can send corresponding transmission configuration information to the source UE and the target UE by receiving the proximity information about the target UE.
  • the serving node can use the proximity information reported by the UE or the information indicated by the core network to identify the relative position between the UEs, the serving cell, the interface status of the DU or CU, etc., analyze the potential transmission path, and comprehensively consider the strategy, channel, etc. Based on factors such as state and load, configure the most suitable transmission path for data transmission between UE node pairs, so as to carry out corresponding transmission, ensure the arrival in the most effective way, and improve the flexibility of data transmission between UEs.
  • the proximity information is sent by the source UE, or by a core network element.
  • it further includes: a signaling information receiving module configured to receive discovery information or SL signaling or SL data, the discovery information or SL signaling or SL data carrying the source UE identifier, the target UE identifier, and/or or SL RB logo.
  • a signaling information receiving module configured to receive discovery information or SL signaling or SL data, the discovery information or SL signaling or SL data carrying the source UE identifier, the target UE identifier, and/or or SL RB logo.
  • it further includes: a transmission instruction receiving module, configured to receive local transmission capability information or transmission instruction information, the local transmission capability information or transmission instruction information is used to instruct or request the serving node to transmit discovery information or SL signaling or SL data.
  • a transmission instruction receiving module configured to receive local transmission capability information or transmission instruction information, the local transmission capability information or transmission instruction information is used to instruct or request the serving node to transmit discovery information or SL signaling or SL data.
  • it further includes: a discovery information forwarding module configured to forward the discovery information or SL signaling or SL data through the Uu interface in a unicast, broadcast or multicast manner.
  • this includes: configuring the transmission module, configured to transmit the discovery information or SL signaling or SL data through the MCCH or dedicated signaling in the case that the service node forwards the discovery information or SL signaling or SL data by means of MBS broadcast or multicast MBS broadcast or multicast configuration for transporting SL signaling or SL data;
  • the MBS broadcast or multicast configuration includes at least one of the following: G-RNTI, SL information type, MTCH scheduling information;
  • the SL information type includes at least one of the following: SL service type, SL SRB, SL DRB, PC5-S, PC5-RRC;
  • the MTCH scheduling information includes at least one of the following: the online duration of the UE after being awakened in the discontinuous reception DRX cycle, the duration of keeping active after each successful decoding of the PDCCH after being awakened, the scheduling period, and the scheduling offset.
  • the apparatus in response to the known UE associated with the target identity, the apparatus further includes:
  • the unicast module is configured to send a data packet containing discovery information or SL data or SL signaling to the UE associated with the target identifier in a unicast manner; wherein, the UE associated with the target identifier includes the UE associated with the target identifier The UE corresponding to the target identifier, and/or the UE interested in receiving the target identifier.
  • the data transmission device proposed in this embodiment and the data transmission method proposed in the above-mentioned embodiments belong to the same inventive concept, and the technical details not described in detail in this embodiment can be referred to any of the above-mentioned embodiments, and this embodiment has and executes a data transmission method Same beneficial effect.
  • Fig. 11 is a schematic structural diagram of a data transmission device provided by yet another embodiment. As shown in Figure 11, the data transmission device includes:
  • the forwarding request module 710 is configured to send SL forwarding request information
  • the forwarding response module 720 is configured to receive SL forwarding response information.
  • the data transmission device of this embodiment by sending SL forwarding request information to the serving node of the target UE, and receiving the SL forwarding response information sent by the serving node of the target UE, thereby establishing an SL forwarding tunnel, and realizing the communication between UEs across serving nodes SL data transmission improves the flexibility of data transmission between UEs.
  • the SL forwarding request information includes at least one of the following information: SL sending request, SL receiving request, first SL forwarding user plane transport layer information, QoS information, SL RB identifier, PC5-S, PC5- RRC, PC5-D, source UE ID, target UE ID or target group ID or target broadcast ID, unicast or groupcast or multicast indication;
  • the first SL forwarding user plane transport layer information includes general packet radio service GPRS tunneling protocol information
  • the QoS information includes at least one of the following: PQI, RLC mode, QoS parameters of SL RB, QoS flow identifier mapped to SL RB, and QoS parameters of QoS flow.
  • the SL forwarding response information includes at least one of the following: second SL forwarding user plane transport layer information, SL RB identification accepted or not accepted, QFI accepted or not accepted, PC5-S, PC5-RRC, PC5-D, source UE identity, target UE identity or target group identity or target broadcast identity;
  • the second SL forwarding user plane transport layer information includes GPRS tunnel protocol information of the target service node.
  • the device also includes:
  • the node determination module is configured to determine the target serving node of the discovery information or SL data or SL signaling according to the target identification contained in the discovery information or SL data or SL signaling to be forwarded, and/or, according to the discovery information or SL to be forwarded.
  • the SL RB identification contained in the data or SL signaling determines the SL forwarding tunnel of the SL data or SL signaling between the target serving node;
  • the discovery information or SL information or SL signaling is forwarded by the target serving node to the target UE, or broadcast and sent in each serving cell of the target serving node.
  • the SL forwarding request information is sent by the first service node, and the SL forwarding response information is sent by the second service node;
  • the first service node is a first base station, a first distributed unit, a first centralized unit, a first IAB node or a third distributed unit;
  • the second service node is a second base station, a second distributed unit, a second centralized unit, a second IAB node, or a third centralized unit.
  • the data transmission device proposed in this embodiment and the data transmission method proposed in the above-mentioned embodiments belong to the same inventive concept, and the technical details not described in detail in this embodiment can be referred to any of the above-mentioned embodiments, and this embodiment has and executes a data transmission method Same beneficial effect.
  • Fig. 12 is a schematic structural diagram of a data transmission device provided by yet another embodiment. As shown in Figure 12, the data transmission device includes:
  • the transmission information receiving module 810 is configured to receive the local transmission information of the UE
  • the confirmation information sending module 820 is configured to send local transmission confirmation information to the core network.
  • the data transmission device of this embodiment by receiving the local transmission information sent by the network element of the core network, and sending the local transmission confirmation information to the core network, thereby completing the proximity discovery and SL data transmission between UEs with the assistance of the core network, Improve the flexibility of data transmission between UEs.
  • the device further includes: a configuration information sending module configured to send transmission configuration information to the UE.
  • the local transmission information is sent by the network element of the core network; the local transmission information includes at least one of the following: the serving node of the UE forwards discovery information or SL signaling or SL data authorization indication, and the serving node forwards the request Or indication, source UE identity, target UE identity, serving node identity of source UE, serving node identity of target UE, serving cell identity of source UE, serving cell identity of target UE, QoS flow information; wherein, the QoS flow information Including at least one of the following: QFI, QoS parameters.
  • the local transmission confirmation information includes at least one of the following: a local forwarding response of the serving node, QoS flow information of the source UE that can be forwarded by the serving node, QoS flow information of the source UE that cannot be forwarded by the serving node, The reason why it cannot be forwarded by the service node.
  • the source UE or the target UE transmits the SL RB data through the Uu interface RLC channel.
  • the device also includes:
  • the discovery information forwarding module is configured to forward the UE's SL signaling or SL data in response to receiving the UE's serving node forwarding authorization indication.
  • the source UE and the target UE transmit PC5-S and/or PC5-RRC through a Uu interface RLC channel with fixed configuration or default configuration.
  • the data transmission device proposed in this embodiment and the data transmission method proposed in the above-mentioned embodiments belong to the same inventive concept, and the technical details not described in detail in this embodiment can be referred to any of the above-mentioned embodiments, and this embodiment has and executes a data transmission method Same beneficial effect.
  • FIG. 13 is a schematic structural diagram of a user equipment provided in an embodiment.
  • the user equipment provided in the present application includes a memory 902, a processor 901 and a storage A computer program that is stored in the memory and can run on the processor. When the processor 901 executes the program, the above-mentioned data transmission method is realized.
  • the user equipment may also include a memory 902; there may be one or more processors 901 in the user equipment, and one processor 901 is taken as an example in FIG. 13; the memory 902 is used to store one or more programs; the one or more A program is executed by the one or more processors 901, so that the one or more processors 901 implement the data transmission method described in the embodiment of the present application.
  • the user equipment further includes: a communication device 903 , an input device 904 and an output device 905 .
  • the processor 901, the memory 902, the communication device 903, the input device 904 and the output device 905 in the user equipment may be connected through a bus or in other ways. In FIG. 13, connection through a bus is taken as an example.
  • the input device 904 can be used to receive input numbers or character information, and generate key signal input related to user settings and function control of the user equipment.
  • the output device 905 may include a display device such as a display screen.
  • the communication device 903 may include a receiver and a transmitter.
  • the communication device 903 is configured to perform information sending and receiving communication according to the control of the processor 901 .
  • the memory 902 can be set to store software programs, computer-executable programs and modules, such as the program instructions/modules corresponding to the data transmission method described in the embodiment of the present application (for example, the configuration in the data transmission device Information receiving module 510, data transmission module 520).
  • the memory 902 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and an application program required by at least one function; the data storage area may store data created according to the use of the user equipment, and the like.
  • the memory 902 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage devices.
  • the memory 902 may further include a memory that is remotely located relative to the processor 901, and these remote memories may be connected to the user equipment through a network. Examples of the aforementioned networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • FIG. 14 is a schematic structural diagram of a service node provided by an embodiment.
  • the service node provided by this application includes a memory 912, a processor 911 and a storage A computer program that is stored in the memory and can run on the processor. When the processor 911 executes the program, the above-mentioned data transmission method is realized.
  • the service node may also include a memory 912; there may be one or more processors 911 in the service node, and one processor 911 is taken as an example in FIG. 14; the memory 912 is used to store one or more programs; the one or more A program is executed by the one or more processors 911, so that the one or more processors 911 implement the data transmission method described in the embodiment of the present application.
  • the service node also includes: a communication device 913 , an input device 914 and an output device 915 .
  • the processor 911, the memory 912, the communication device 913, the input device 914 and the output device 915 in the service node may be connected through a bus or in other ways. In FIG. 14, connection through a bus is taken as an example.
  • the input device 914 can be used to receive input numbers or character information, and generate key signal input related to user setting and function control of the service node.
  • the output device 915 may include a display device such as a display screen.
  • the communication device 913 may include a receiver and a transmitter.
  • the communication device 913 is configured to perform information sending and receiving communication according to the control of the processor 911 .
  • the memory 912 can be configured to store software programs, computer-executable programs and modules, such as program instructions/modules corresponding to the data transmission method described in the embodiment of the present application (for example, adjacent Information receiving module 610, configuration information sending module 620).
  • the memory 912 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and an application program required by at least one function; the data storage area may store data created according to the use of the service node, and the like.
  • the memory 912 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other non-volatile solid-state storage devices.
  • the memory 912 may further include a memory that is remotely located relative to the processor 911, and these remote memories may be connected to the service node through a network.
  • networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.
  • An embodiment of the present application further provides a storage medium, the storage medium stores a computer program, and when the computer program is executed by a processor, the data transmission method described in any one of the embodiments of the present application is implemented.
  • the method includes: receiving transmission configuration information; and transmitting data according to the transmission configuration information.
  • the method includes: receiving proximity information about the target UE; and sending path configuration information according to the proximity information.
  • the method includes: sending SL forwarding request information; receiving SL forwarding response information.
  • the method includes: receiving local transmission information of the UE; and sending local transmission confirmation information to the core network.
  • the computer storage medium in the embodiments of the present application may use any combination of one or more computer-readable media.
  • the computer readable medium may be a computer readable signal medium or a computer readable storage medium.
  • a computer-readable storage medium may be, for example, but not limited to: an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or any combination thereof.
  • Computer-readable storage media include: electrical connections with one or more conductors, portable computer disks, hard disks, Random Access Memory (RAM), read-only memory (Read Only Memory, ROM), Erasable Programmable Read Only Memory (EPROM), Flash Memory, Optical Fiber, Portable CD-ROM (Compact Disc Read-Only Memory), Optical Storage Devices, Magnetic Storage Devices , or any suitable combination of the above.
  • a computer readable storage medium may be any tangible medium that contains or stores a program for use by or in connection with an instruction execution system, apparatus, or device.
  • a computer readable signal medium may include a data signal carrying computer readable program code in baseband or as part of a carrier wave. Such propagated data signals may take many forms, including but not limited to: electromagnetic signals, optical signals, or any suitable combination of the foregoing.
  • a computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which can send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device. .
  • Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wires, optical cables, radio frequency (Radio Frequency, RF), etc., or any suitable combination of the above.
  • any appropriate medium including but not limited to: wireless, wires, optical cables, radio frequency (Radio Frequency, RF), etc., or any suitable combination of the above.
  • Computer program codes for performing the operations of the present application may be written in one or more programming languages or combinations thereof, including object-oriented programming languages such as Java, Smalltalk, C++, and conventional A procedural programming language, such as the "C" language or similar programming language.
  • the program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
  • the remote computer may be connected to the user's computer via any kind of network, including a local area network (LAN) or a wide area network (WAN), or it may be connected to an external computer such as use an Internet service provider to connect via the Internet).
  • LAN local area network
  • WAN wide area network
  • user terminal covers any suitable type of wireless user equipment, such as a mobile phone, a portable data processing device, a portable web browser or a vehicle-mounted mobile station.
  • the various embodiments of the present application can be implemented in hardware or special purpose circuits, software, logic or any combination thereof.
  • some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor or other computing device, although the application is not limited thereto.
  • Computer program instructions may be assembly instructions, Instruction Set Architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or written in any combination of one or more programming languages source or object code.
  • ISA Instruction Set Architecture
  • Any logic flow block diagrams in the drawings of the present application may represent program steps, or may represent interconnected logic circuits, modules and functions, or may represent a combination of program steps and logic circuits, modules and functions.
  • Computer programs can be stored on memory.
  • the memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as but not limited to Read-Only Memory (ROM), Random Access Memory (RAM), Optical Memory devices and systems (Digital Video Disc (DVD) or Compact Disk (CD), etc.
  • Computer-readable media may include non-transitory storage media.
  • Data processors may be any Types, such as but not limited to general-purpose computers, special-purpose computers, microprocessors, digital signal processors (Digital Signal Processing, DSP), application-specific integrated circuits (Application Specific Integrated Circuit, ASIC), programmable logic devices (Field-Programmable Gate Array , FGPA) and processors based on multi-core processor architectures.
  • DSP Digital Signal Processing
  • ASIC Application Specific Integrated Circuit
  • FGPA programmable logic devices
  • processors based on multi-core processor architectures.

Landscapes

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

Abstract

本申请提供一种数据传输方法、用户设备、服务节点及存储介质。该方法接收传输配置信息；根据所述传输配置信息传输数据。

Description

数据传输方法、用户设备、服务节点及存储介质
本申请要求在2021年06月07日提交中国专利局、申请号为202110633948.0的中国专利申请的优先权，以上申请的全部内容通过引用结合在本申请中。
技术领域
本申请涉及无线通信技术领域，例如涉及一种数据传输方法、用户设备、服务节点及存储介质。
背景技术
随着无线多媒体业务的发展，人们对高数据速率和用户体验的需求日益增长，从而对传统蜂窝网络的系统容量和覆盖提出了较高要求。此外，公共安全、社交网络、近距离数据共享、本地广告等应用场景使得人们对了解附近人或事物并与之通信(Proximity Services，邻近服务)的需求逐渐增加。传统的以基站为中心的蜂窝网络在高数据速率以及邻近服务的支持方面存在明显的局限性，在这种需求背景下，设备直通(Device-to-Device，D2D)技术应运而生。设备直通技术可以工作在授权频段或非授权频段，允许多个支持设备直通功能的用户设备(User Equipment，UE)在有网络基础设施或无网络基础设施的情况下进行直接发现或直接通信。以下几种的UE本地传输路径都可以取代传统经过核心网的传输路径：单跳或多跳的UE到UE中继、跨集中式单元(Centralized Unit，CU)的数据中继、同一分布式单元(Distributed Unit，DU)内的数据中继、同一集中式单元(Centralized Unit，CU)内跨DU的数据中继等。目前，UE之间的传输路径往往是在数据传输之前预定的，不能根据实际情况综合决策，灵活性低，影响通信效率。
发明内容
本申请提供一种数据传输方法、用户设备、服务节点及存储介质，以提高UE传输数据的灵活性。
本申请实施例提供一种数据传输方法，包括：
接收传输配置信息；
根据所述传输配置信息传输数据。
本申请实施例还提供了一种数据传输方法，包括：
接收关于目标UE的邻近信息；
根据所述邻近信息，发送路径配置信息。
本申请实施例还提供了一种数据传输方法，包括：
发送直通链路(Sidelink，SL)转发请求信息；
接收SL转发响应信息。
本申请实施例还提供了一种数据传输方法，包括：
接收UE的本地传输信息；
向核心网发送本地传输确认信息。
本申请实施例还提供了一种用户设备，包括：存储器、处理器以及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现上述的数据传输方法。
本申请实施例还提供了一种服务节点，包括：存储器、处理器以及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现上述的数据传输方法。
本申请实施例还提供了一种计算机可读存储介质，计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现上述的数据传输方法。
附图说明
图1为一实施例提供的一种数据传输方法的流程图；
图2为另一实施例提供的一种数据传输方法的流程图；
图3为再一实施例提供的一种数据传输方法的流程图；
图4为又一实施例提供的一种数据传输方法的流程图；
图5为一实施例提供的一种用户设备之间建立PC5单播连接的示意图；
图6为一实施例提供的一种服务节点辅助UE进行邻近发现的示意图；
图7为一实施例提供的一种服务节点转发发现信息的示意图；
图8为一实施例提供的一种核心网检测邻近UE的实现示意图；
图9为一实施例提供的一种数据传输装置的结构示意图；
图10为另一实施例提供的一种数据传输装置的结构示意图；
图11为再一实施例提供的一种数据传输装置的结构示意图；
图12为又一实施例提供的一种数据传输装置的结构示意图；
图13为一实施例提供的一种用户设备的硬件结构示意图；
图14为一实施例提供的一种服务节点的硬件结构示意图。
具体实施方式
下面结合附图和实施例对本申请进行说明。可以理解的是，此处所描述的具体实施例仅仅用于解释本申请，而非对本申请的限定。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。另外还需要说明的是，为了便于 描述，附图中仅示出了与本申请相关的部分而非全部结构。
在本申请实施例中，提供一种数据传输方法，可应用于UE，例如可以指源UE。图1为一实施例提供的一种数据传输方法的流程图，如图1所示，该方法包括步骤110和步骤120。
在步骤110中，接收传输配置信息。
在步骤120中，根据所述传输配置信息传输数据。
本实施例中，传输配置信息可以是服务节点配置并发送的，服务节点可以是基站、集成接入回传(Integrated Access Backhaul，IAB)节点、DU、CU等，传输配置信息包括了服务节点为UE配置的传输路径和/或无线承载等，UE根据传输配置信息可以在相应的路径上使用相应的无线承载传输数据。而服务节点可以利用UE上报的邻近信息或者核心网指示的信息，识别UE之间的相对位置，服务小区，DU或CU的接口状态等，分析潜在可能的传输路径，综合考虑策略、信道状态、负荷等因素，为UE节点对之间的数据传输配置最合适的传输路径，从而进行相应的传输，保证以最有效的方式到达，提高UE之间数据传输的灵活性。
需要说明的是，目前设备直通通信对应的短距通信可应用于智能汽车，智能终端，智能家居，智能制造领域。在这些短距通信系统中，系统内节点区分为管理节点(G节点)和被管理节点(T节点)。在具体的应用场景中，单个G节点管理一定数量的T结点，G节点与这些T节点连接共同完成特定的通信功能。单个G节点以及与其连接的T节点共同组成一个通信域。以智能汽车场景为例，座舱域控制器(Cockpit Domain Controller，CDC)可以作为G节点，各类车载设备(例如麦克风、扬声器等)作为T节点，共同完成座舱娱乐功能。这种情况下，CDC与车载设备组成了一个通信域，当手机与CDC连接时，手机也可以作为该通信域内的T节点。在智能汽车环境下，手机也可以作为G节点连接可穿戴设备，此时手机与可穿戴设备组成了另外一个通信域。智能家居场景，电视与下挂音频设备组成一个通信域，手机与耳机组成另外一个通信域，两个通信域之间可以通过高级/一般通信域进行区分，由高级通信域进行资源协调，实现多域之间的协调共存。
对于本申请实施例，UE可以对应于上述场景中的T节点，而服务节点可以对应于上述场景中的G节点，本申请实施例中提到的由服务节点为UE转发短距通信数据的机制，如承载配置、路径配置、数据传输等，可以应用于G节点为T节点转发T节点之间的通信数据。
需要说明的是，本申请实施例中，对于未明确说明是源UE还是目标UE的UE，可以指源UE和/或目标UE。
在一实施例中，该方法还包括：步骤100：发送目标UE的邻近信息。
本实施例中，在接收传输配置信息之前，源UE可以发现邻近的目标UE，并向服务节点上报关于目标UE的邻近信息，供服务节点做出综合决策。
在一实施例中，邻近信息包括以下信息至少之一：源UE标识(Identity，ID)，目标UE标识，传输类型(Cast Type)，源UE的应用标识(Application Identity，APP ID)，目标UE的应用标识，目标UE的服务小区(Serving Cell)标识，目标UE的服务节点标识，源UE与所述目标UE之间的链路状态，源UE与目标UE之间的数据流的服务质量(Quality of Service，QoS)，源UE与目标UE之间的跳数，中继节点的节点标识；其中，链路状态包括以下至少之一：链路测量结果，链路负荷，SL资源使用率。
在一实施例中，传输配置信息包括承载配置信息和/或路径配置信息。
在一实施例中，承载配置信息包括以下信息至少之一：
Uu无线链路层控制协议(Radio Link Control，RLC)信道配置；Uu RLC信道标识；Uu逻辑信道(Logical Channel)配置；直通链路无线承载(Sidelink Radio Bear，SL RB)对应的服务数据适配协议(Service Data Adaptation Protocol，SDAP)配置；SL RB对应的分组数据汇聚协议(packet data convergence protocol，PDCP)配置；SL RB与Uu RLC信道的映射信息。
在一实施例中，承载配置信息包括以下信息至少之一：
SL RB对应的SDAP配置，SL RB对应的PDCP配置，PC5 RLC信道配置，PC5逻辑信道配置。
在一实施例中，承载配置信息包括信息类型与Uu RLC信道的映射信息；其中，信息类型包括以下至少之一：发现信息(源UE请求发现目标UE或触发邻近发现过程的信息)，PC5-S，PC5无线资源控制(Radio Resource Control，RRC)信息，SL信令无线承载(Signalling Radio Bearer，SRB)标识，SL数据无线承载(Data Radio Bearer，DRB)标识。
在一实施例中，路径配置信息包括以下信息之一：Uu传输路径；SL传输路径；Uu传输路径和SL传输路径。
在一实施例中，步骤120，包括：
响应于传输配置信息包括Uu传输路径，或者包括Uu RLC信道配置以及该Uu RLC信道关联的SL SRB，或者包括Uu RLC信道配置以及SL RB与Uu RLC信道的映射信息，通过Uu接口传输对应的SL RB数据；
响应于传输配置信息包括SL传输路径，或者包括SL RB对应的SDAP配置、SL RB对应的PDCP配置、PC5 RLC信道配置和/或PC5逻辑信道配置，通过PC5接口传输对应的SL RB数据；
响应于传输配置信息包括SL传输路径和Uu传输路径，或包括SL RB对应的Uu RLC信道配置和PC5 RLC信道配置，通过Uu和/或PC5接口传输对应的SL RB数据。
在一实施例中，传输配置信息还包括以下至少之一：数据复制指示，数据分离传输指示，数据分割门限，数据分割比率，主路径指示，辅路径指示，路径切换指示；其中，路径切换指示包括以下信息至少之一：源UE标识，目标UE标识，SL RB标识，路径指示。
本实施例中，在源UE可以通过Uu和PC5接口传输SL RB数据的情况下，SL RB数据可以以数据复制或数据分离的方式在两种接口上传输。
在一实施例中，步骤120，包括：采用数据复制或数据分割的方式，通过Uu接口和PC5接口与所述目标UE传输对应的SL RB数据。
在一实施例中，该方法还包括：步骤10：通过PC5接口发送第一发现信息或SL信令或SL数据。
本实施例中，源UE可以通过PC5接口发送第一发现信息或SL信令或SL数据，以发现邻近的目标UE，其中，第一发现信息可能直接发送至目标UE，也可能由中继UE转发至目标UE，但都是通过PC5接口传输的。
在一实施例中，该方法还包括：步骤12：通过PC5接口接收目标UE发送或中继UE转发的第二发现信息或SL信令或SL数据；
所述第二发现信息包括以下至少之一：目标UE的应用层标识，目标UE的服务节点标识，服务小区标识，驻留小区标识，最大跳数信息，已传输跳数信息，中继节点的节点标识。
本实施例中，源UE可以通过PC5接口接收第二发现信息或SL信令或SL数据，以被邻近的目标UE发现，其中，第二发现信息可以直接从目标UE接收，也可以由中继UE或者服务节点转发而来。
在一实施例中，该方法还包括：步骤14：发送本地传输能力信息或者传输指示信息，本地传输能力信息或者传输指示信息用于指示或请求服务节点通过Uu接口传输发现信息或SL信令或SL数据。
本实施例中，源UE可以指示或请求服务节点通过Uu接口，将发现信息或SL信令或SL数据转发给其他UE，在此基础上，服务节点可辅助源UE发现邻近的目标UE。
在一实施例中，发现信息或SL信令或SL数据由所述服务节点通过Uu接口以单播或广播或多播的方式转发。
在一实施例中，通过Uu接口发送的发现信息或SL信令或SL数据携带源UE标识，目标UE标识，和/或SL RB标识。
在一实施例中，在发现信息或SL信令或SL数据由服务节点通过MBS(Multicast Broadcast Services，多播广播服务)广播或多播的方式转发的情况下，服务节点通过多播控制信道(Main Control Channel，MCCH)或专有信令传输发现信息或SL信令或SL数据的MBS广播或多播配置；
MBS广播或多播配置包括以下至少之一：用于广播SL信令或SL数据的分组无线网络临时标识(Group-Radio Network Tempory Identity，G-RNTI)，SL信息类型，多播业务信道(Multicast Traffice Channel，MTCH)调度信息；
其中，SL信息类型包括以下至少之一：SL业务类型，SL SRB，SL DRB，PC5-S，PC5-RRC；
MTCH调度信息包括以下至少之一：非连续接收(Discontinuous Reception，DRX)周期内UE被唤醒后的在线时长，被唤醒后每次成功解码物理下行控制信道(Physical Downlink Control Channel，PDCCH)后保持激活的时长，调度周期，调度偏移量。
在一实施例中，该方法还包括：步骤16：通过Uu接口接收目标UE发送的、所述服务节点转发的发现信息或SL信令或SL数据，所述发现信息或SL信令或SL数据携带源UE标识，目标UE标识，和/或SL RB标识。
本实施例中，源UE可以接收服务节点通过Uu接口转发的、来自于目标UE的发现信息或SL信令或SL数据，在此基础上，服务节点可辅助源UE被邻近的目标UE发现。
在一实施例中，响应于已知与目标标识关联的UE，服务节点通过单播的方式将包含发现信息或SL数据或SL信令的数据包发送至所述与目标标识关联的UE；其中，与目标标识关联的UE包括与所述目标标识对应的UE，和/或对目标标识接收感兴趣的UE。
本实施例中，目标标识可以是目标UE ID、目标UE的服务小区ID、目标UE的应用ID等。
在一实施例中，还包括：步骤18：将以下信息至少之一发送至服务节点：
核心网(Next Generation Core，NGC)分配的UE标识，感兴趣的业务类型对应的目标标识，目标标识对应的传输类型。
本实施例中，源UE可以将上述信息发送至服务节点，在此基础上，服务节点可辅助源UE发现邻近的目标UE。
在一实施例中，还包括：步骤112：向目标UE发送服务节点转发SL数据指示。
本实施例中，如果传输配置信息指示源UE通过服务节点与目标UE传输SL数据，则源UE可以将服务节点转发SL数据指示发送至目标UE，在此基础上，目标UE准备接收服务节点转发的SL数据。
在一实施例中，还包括：步骤114：响应于目标UE处于闲置或非激活状态，在收到 服务节点转发SL数据指示后，目标UE进入RRC连接状态。
本实施例中，处于闲置或非激活状态的目标UE，在接收到服务节点转发SL数据指示后，进入RRC连接状态，从而完成接收服务节点转发的SL数据的准备。
在一实施例中，还包括：步骤1000：接收核心网网元发送的本地传输指示信息，本地传输指示信息用于指示或请求服务节点通过Uu接口传输发现信息或SL信令或SL数据；其中，本地传输指示信息包括以下至少之一：服务节点转发请求或指示，源UE标识，目标UE标识，源UE的服务节点标识，目标UE的服务节点标识，源UE的服务小区标识，目标UE的服务小区标识，QoS流信息；其中，QoS流信息包括以下至少之一：QoS流标识(QoS Flow Identity，QFI)，QoS参数。在此基础上，UE通过接收本地传输指示信息，可以明确服务节点是否能够转发发现信息或SL信令或SL数据。
在一实施例中，传输配置信息由服务节点发送；服务节点包括基站、DU，集中式单元CU或IAB节点。
在本申请实施例中，还提供一种数据传输方法，可应用于服务节点。图2为另一实施例提供的一种数据传输方法的流程图，如图2所示，该方法包括步骤210和步骤220。需要说明的是，对于本实施例中服务节点执行的操作，未在本实施例中详尽描述的技术细节可参见上述任意实施例。
在步骤210中，接收关于目标UE的邻近信息；
在步骤220中，根据所述邻近信息，发送传输配置信息。
本实施例中，服务节点通过接收关于目标UE的邻近信息，可向源UE和目标UE发送相应的传输配置信息。具体的，服务节点可以利用UE上报的邻近信息或者核心网指示的信息，识别UE之间的相对位置，服务小区，DU或CU的接口状态等，分析潜在可能的传输路径，综合考虑策略、信道状态、负荷等因素，为UE节点对之间的数据传输配置最合适的传输路径，从而进行相应的传输，保证以最有效的方式到达，提高UE之间数据传输的灵活性。
在一实施例中，所述邻近信息由源UE发送，或者由核心网网元发送。
本实施例中，邻近信息可以是源UE发现目标UE后上报给服务节点的，也可以是由核心网发现源UE和目标UE后发送给服务节点的。
在一实施例中，该方法还包括：步骤200：接收发现信息或SL信令或SL数据，所述发现信息或SL信令或SL数据携带源UE标识，目标UE标识，和/或SL RB标识。
本实施例中，服务节点可以通过接收源UE发送的发现信息或SL信令或SL数据，辅助源UE发现邻近的目标UE。
在一实施例中，该方法还包括：步骤202：接收本地传输能力信息或者传输指示信息，所述本地传输能力信息或者传输指示信息用于指示或请求服务节点通过Uu接口传输发现信息或SL信令或SL数据。
本实施例中，服务节点可以根据源UE的本地传输能力信息或者传输指示信息，通过Uu接口传输发现信息或SL信令或SL数据，以辅助源UE发现邻近的目标UE。
在一实施例中，该方法还包括：步骤204：通过Uu接口以单播或广播或多播的方式转发发现信息或SL信令或SL数据。
本实施例中，服务节点可以通过Uu接口转发发现信息或SL信令或SL数据，以辅助源UE发现邻近的目标UE。
在一实施例中，该方法还包括：步骤206：在发现信息或SL信令或SL数据由服务节点通过MBS广播或多播的方式转发的情况下，通过MCCH或专有信令传输SL信令或SL数据的MBS广播或多播配置；MBS广播或多播配置包括以下至少之一：G-RNTI，SL信息类型，MTCH调度信息；其中，SL信息类型包括以下至少之一：SL业务类型，SL SRB，SL DRB，PC5-S，PC5-RRC；MTCH调度信息包括以下至少之一：DRX周期内UE被唤醒后的在线时长，被唤醒后每次成功解码PDCCH后保持激活的时长，调度周期，调度偏移量。
本实施例中，在通过MBS广播或多播的方式转发发现信息或SL信令或SL数据之前，服务节点可以通过MCCH或专有信令传输SL信令或SL数据的MBS广播或多播配置，以使UE准备接收转发的发现信息或SL信令或SL数据。
在一实施例中，响应于已知与目标标识关联的UE，该方法还包括：步骤205：通过单播的方式将包含发现信息或SL数据或SL信令的数据包发送至所述与目标标识关联的UE；其中，所述与目标标识关联的UE包括与所述目标标识对应的UE，和/或对所述目标标识接收感兴趣的UE。
本实施例中，在转发发现信息或SL信令或SL数据之前，服务节点可以根据目标标识确定是否能够识别目标UE，如果能，则通过单播的方式将包含发现信息或SL数据或SL信令的数据包发送至所述与目标标识关联的UE即可。
在本申请实施例中，还提供一种数据传输方法，可应用于服务节点，例如可以是为源UE服务的服务节点。图3为再一实施例提供的一种数据传输方法的流程图，如图3所示，该方法包括步骤310和步骤320。需要说明的是，对于本实施例中服务节点执行的操作，未在本实施例中详尽描述的技术细节可参见上述任意实施例。
在步骤310中，发送SL转发请求信息。
在步骤320中，接收SL转发响应信息。
本实施例中，源UE的服务节点可以向目标UE的服务节点发送SL转发请求信息，并接收目标UE的服务节点发送的SL转发响应信息，从而建立SL转发隧道，实现跨服务节点的UE之间的SL数据传输，提高UE之间数据传输的灵活性。
在一实施例中，SL转发请求信息包括以下信息至少之一：SL发送请求，SL接收请求，第一SL转发用户面传输层信息，QoS信息，SL RB标识，PC5-S，PC5-RRC，PC5-D，源UE标识，目标UE标识或目标组标识或目标广播标识，单播或组播或多播指示；其中，第一SL转发用户面传输层信息包括通用无线分组业务(General Packet Radio Service，GPRS)隧道协议信息；QoS信息包括以下至少之一：PC5质量指示(PC5 Quality Indication，PQI)，RLC模式，SL RB的QoS参数，映射到SL RB的QoS流标识，QoS流的QoS参数。
在一实施例中，SL转发响应信息包括以下至少之一：第二SL转发用户面传输层信息，接纳和或不接纳的SL RB标识，接纳和或不接纳的QFI，PC5-S，PC5-RRC，PC5-D，源UE标识，目标UE标识或目标组标识或目标广播标识；其中，所述第二SL转发用户面传输层信息包括目标服务节点的GPRS隧道协议信息。
本实施例中，目标服务节点为目标UE服务的服务节点。
在一实施例中，该方法还包括：
步骤330：根据待转发的发现信息或SL数据或SL信令包含的目标标识确定发现信息或SL数据或SL信令的目标服务节点，和/或，根据待转发的发现信息或SL数据或SL信令包含的SL RB标识确定与目标服务节点之间的SL数据或SL信令的SL转发隧道；
步骤340：将待转发的发现信息或SL数据或SL信令投递到SL转发隧道并转发至所述目标服务节点；
在一实施例中，发现信息或SL信息或SL信令由所述目标服务节点转发至目标UE，或者在目标服务节点的每个服务小区广播发送。
本实施例中，SL转发请求信息由第一服务节点发送，SL转发响应信息由第二服务节点发送；
其中，所述第一服务节点为第一基站、第一分布式单元、第一集中式单元、第一IAB节点或第三分布式单元；
相应的，所述第二服务节点为第二基站、第二分布式单元、第二集中式单元、第二IAB节点或第三集中式单元。
本实施例中，SL转发请求信息和SL转发响应信息的交互，可以是不同基站之间的、 不同分布式单元之间的、不同集中式单元之间的、不同IAB节点之间的，或者是分布式单元与集中式单元之间的。
在本申请实施例中，还提供一种数据传输方法，可应用于服务节点，例如可以是为源UE和/或目标UE服务的服务节点。图4为又一实施例提供的一种数据传输方法的流程图，如图4所示，该方法包括步骤410和步骤420。需要说明的是，对于本实施例中服务节点执行的操作，未在本实施例中详尽描述的技术细节可参见上述任意实施例。
在步骤410中，接收UE的本地传输信息；
在步骤420中，向核心网发送本地传输确认信息。
本实施例中，服务节点可以接收核心网网元发送的本地传输信息，并向核心网发送本地传输确认信息，从而在核心网的辅助下，完成UE之间的邻近发现和SL数据传输，提高UE之间数据传输的灵活性。
在一实施例中，还包括：步骤430：向UE发送传输配置信息。
本实施例中，服务节点根据UE的本地传输信息，为源UE和目标UE选择合适的传输路径，并向UE发送传输配置信息。
在一实施例中，本地传输信息由所述核心网网元发送；所述本地传输信息包括以下至少之一：UE的服务节点转发发现信息或SL信令或SL数据授权指示，服务节点转发请求或指示，源UE标识，目标UE标识，源UE的服务节点标识，目标UE的服务节点标识，源UE的服务小区标识，目标UE的服务小区标识，QoS流信息；其中，所述QoS流信息包括以下至少之一：QFI，QoS参数。
在一实施例中，本地传输确认信息包括以下至少之一：服务节点本地转发响应，可被服务节点转发的源UE的QoS流信息，不可被服务节点转发的源UE的QoS流信息，不可被服务节点转发的原因。
在一实施例中，源UE或目标UE通过Uu接口RLC信道传输SL RB数据。
在一实施例中，该方法还包括：步骤440：响应于接收到UE的服务节点转发授权指示，转发所述UE的SL信令或SL数据。
本实施例中，服务节点在UE授权进行服务节点转发的情况下，才会转发UE之间的数据。
在一实施例中，所述源UE和所述目标UE通过固定配置或默认配置的Uu接口RLC信道传输PC5-S和/或PC5-RRC。
以下通过一些示例对数据传输方法进行说明。
示例1
本示例中，源UE与目标UE希望进行数据传输。源UE可以通过应用服务器或策略控制功能(Policy Control Function，PCF)或预配置的方式获取如下信息中的一种或多种：每个公共陆地移动网(Public Land Mobile Network，PLMN)的PC5通信授权信息，UE授权进行PC5通信的无线接入类型(Radio Access Type，RAT)信息，对应于每个PC5 RAT及地理区域下的空口参数，业务类型到PC5 RAT的映射信息及对应的发送配置(Tx Profile)，地理区域的业务类型及对应的定时器(定时器用于指示UE自己分配的长期演进二层(Long Term Evolution Layer 2，L2)源设备标识的更新间隔，即分配Source L2 ID的更新间隔)，业务类型与V2X(Vehicle to everything)频率及地理区域的映射，业务类型与通信模式(如广播、组播或单播)的映射，业务类型与广播或组播对应的目标UE标识(即Destination L2 ID)的映射，业务类型与单播连接建立初始信令对应的默认Destination L2 ID的映射，业务类型与PC5 QoS参数(如PQI、最大流比特率(Maximum Flow Bit Rate，MFBR)、保证流比特率(Guaranteed Flow Bit Rate，GFBR)等)的映射，接入层(Access Stratum，AS)层配置(如PC5 QoS配置与无线承载的映射)，以及上述各种信息或参数的有效期等。
如果源UE的应用层希望发起PC5单播进行某个业务类型的数据传输，则源UE首先考虑是否可以重用已有的PC5单播链路，可以根据目标UE应用层标识，也称为对端UE应用层标识(Peer Application Layer ID)与网络层协议是否相同来判断，如果有可以重用的PC5单播链路，可以考虑修改已有的PC5单播链路，添加业务类型，用于源UE与目标UE的数据传输；否则，源UE将触发建立新的PC5单播链路。
如果源UE在与目标UE建立PC5单播链路之前已经知道目标UE的L2 ID，则源UE可以在初始PC5单播链路建立信令中使用目标UE的L2 ID作为Destination L2 ID并单播传输初始PC5单播链路建立信令，否则的话，源UE使用与PC5单播链路建立对应的V2X业务类型关联的默认广播destination L2 ID并广播传输初始PC5单播链路建立信令。
图5为一实施例提供的一种用户设备之间建立PC5单播连接的示意图。如图5所示，源UE的应用层提供PC5单播通信的应用层信息。应用层信息包括业务类型以及源UE的应用层ID。应用层信息中还可以包含目标UE的应用层ID。源UE的应用层还会提供单播通信的应用需求，在此基础上，源UE或目标UE可以相应的确定PC5 QoS参数以及分组流标识(Packet Flow Identifier，PFI)。
相应的，目标UE需要确定PC5单播链路建立信令接收对应的目标L2 ID。目标UE可以通过如下方式获取PC5单播链路建立信令对应的目标L2 ID：1)可以在源UE与目 标UE建立PC5单播链路的过程中发现；2)根据之前的V2X通信感知(例如对应于相同的应用层ID的已有或之前建立的单播链路)；3)从应用层业务公告信息获取。
假设源UE发起新的PC5单播链路建立，则源UE发送直接通信请求(Direct Communication Request)消息，该消息中可以包含源UE的应用层ID，可选的目标UE的应用层ID，业务类型，安全信息。传输直接通信请求消息的过程中，源UE可以使用自己分配的Source L2 ID。
接下来，源UE和目标UE之间建立安全保护，当安全保护使能后，源UE可向目标UE发送IP(Internet Protocol，网际互连协议)地址配置信息和/或PC5 QoS流信息。例如，对于每一个PC5 QoS流，可以包含PFI，对应的QoS参数如PQI、MFBR、GFBR等，以及对应的业务类型。相应的，如果目标UE发现自己与直接通信请求消息中包含的应用层ID匹配，或是对直接通信请求中包含的业务感兴趣，则目标UE可向源UE发送直接通信接受信息，直接通信接受信息中可包含源用户的相关信息，如源UE的应用层ID，IP地址配置信息，目标UE请求的PC5 QoS流信息，例如，对于每一个PC5 QoS流，可以包含PFI，对应的QoS参数如PQI、MFBR、GFBR等，以及对应的业务类型。
PC5单播链路建立之后，UE(本示例中，在未指定源UE或目标UE的情况下，UE可以是源UE和/或目标UE)之间使用L2 ID节点对用于后续的PC5-S信令及业务数据传输。对于每一个PC5单播链路，UE自己分配一个PC5链路标识PLI用于唯一的识别一个PC5单播链路。每个PC5单播链路关联一个单播链路配置，其中包括源UE的应用层标识(Application Layer ID)和L2 ID，目标UE的应用层标识和L2 ID，PC5 QoS流信息。UE维护用于PC5单播链路的Application Layer ID与自己的Source L2 ID之间的映射关系。当UE的Source L2 ID改变时，不会影响V2X应用。反之如果Application Layer ID改变，则对应的PC5单播链路的Source L2 ID也要相应的改变。UE建立了PC5单播链路后，UE将PC5链路标识符(PC5 Link Identifier，PLI)、源UE和目标UE的L2 ID以及对应的PC5 QoS参数发给AS层，从而使AS层可以维护PLI以及PC5单播链路相关信息。
PC5单播链路建立后，源UE和目标UE之间可以传输数据，例如源UE可将数据包，该数据包对应的PLI和/或PFI信息，可选的还可将源UE和目标UE的L2 ID，发给AS层。源UE的AS层收到上述QoS信息后，源UE和目标UE之间继续进行PC5 RRC的配置，遵循专有信令或系统信息块(System Information Block，SIB)或预配置(Pre-Configuration)中的SL RB配置并通过PC5 RRC消息与对端UE交互SL DRB配置。具体来说：如果专有信令或SIB或Pre-Configuration中的SL RB配置包含新建SL DRB，UE根据PC5 QoS流的参数新建相应SL DRB，包括SDAP实体(如果尚无SDAP 实体)、PDCP实体、RLC实体、配置逻辑信道并为该逻辑信道分配LC(Logical Channel,逻辑信道)ID。
当源UE接收到对端目标UE发送的RRC重配直通链路(Reconfiguration Sidelink)配置中包含新建SL DRB，源UE也可以新建相应SL DRB，包括SDAP实体、PDCP实体、RLC实体、逻辑信道配置(使用对端UE配置的LC ID)，此外，如果源UE为连接态，且该SL DRB被配置为双向DRB，且源UE尚未获得该双向SL DRB的发送参数配置，源UE发送直通链路UE信息(Sidelink UE Information)向基站请求相关配置，例如，源UE上报RLC模式及可选的PC5 QoS配置。
当SL RB创建后，源UE的AS层将从高层接收到的数据包映射到对应的SL RB，然后根据只有调度将该数据包组装成MAC(Media Access Control，介质访问控制)PDU并通过PC5单播链路进行传输。
需要注意的是，一个Application Layer ID可以关联UE内的一个或多个设备直通应用。如果UE有多个Application Layer ID，则从对端UE的角度来看，相同UE的每一个Application Layer ID可以看做是不同UE的Application Layer ID。一个PC5单播链路内可能涉及一个或多个业务类型，但是他们必须关联到相同的Application Layer ID。例如UE A和UE B有两个PC5单播链路，一个是在UE A的peer Application Layer ID 1和UE B的Application Layer ID 2之间，另一个是在UE A的peer Application Layer ID 3和UE B的Application Layer ID 4。
当源UE希望与目标UE进行通信时，假设源UE尚未与目标UE建立PC5单播链路，则源UE可以在PC5链路建立请求中携带源UE的Application Layer ID，目标UE的Application Layer ID，然后广播发送该PC5链路建立请求，如果目标UE收到该PC5链路建立请求，则向源UE发送响应消息。
示例二
通常情况下，源UE和目标UE可以相互发现并建立PC5单播链路，但在一些场景中，可能需要选择其他的传输路径，例如，SL资源拥塞，或是源UE和目标UE之间PC5单播链路的质量下降等，从而需要从全局考虑合适的SL数据传输路径。在这种情况下可以由服务节点统一管理UE之间的数据传输路径规划，配置相应的路由及承载，从而使得UE(本示例中，在未指定源UE或目标UE的情况下，UE可以是源UE和/或目标UE)之间的数据传输可以满足本地化需求，同时保证低时延，高效率。
对于源UE和目标UE之间的邻近情况检测，可以考虑如下几种通过PC5接口传输发现信息以进行邻近检测的场景：
1)PC5单跳：源UE和目标UE之间通过PC5接口进行发现并建立了PC5单播链路后，源UE可向服务节点上报邻近信息，邻近信息包括目标UE的以下相关信息的任意组合：源UE标识，目标UE标识(Destination L2 ID)，传输类型(Cast Type)，源UE的APP ID，目标UE的APP ID，目标UE的服务小区标识(Serving Cell ID)，目标UE的服务节点标识，源UE与目标UE之间的链路状态，源UE与目标UE之间的数据流的QoS信息，源UE与所述目标UE之间的跳数，中继节点的节点标识。其中源UE和目标UE之间的链路状态可进一步包括源UE和目标UE之间的链路测量结果，源UE和目标UE之间的负荷和/或SL资源使用率。源UE的服务节点收到上述信息后，分析源UE和目标UE之间有哪些可能的路径，为源UE和目标UE之间的数据传输选择最合适的传输路径。
假设源UE的服务节点发现源UE和目标UE由同一个服务节点服务，并且服务节点发现源UE和目标UE之间的数据传输通过服务节点进行转发资源利用率最好，则源UE的服务节点可向源UE发送承载配置信息和/或路径配置信息。例如，源UE从服务节点接收的承载配置信息包含以下信息任意组合：Uu RLC信道配置(可包含Uu RLC信道ID，Uu RLC和/或Uu逻辑信道(Logical Channel)配置)，SL RB ID(包括SL SRB ID或SL DRB ID)，SL DRB对应的SDAP配置，SL DRB或SRB对应的PDCP配置。其中Uu RLC Channel配置可以是与特定的对端UE之间的SL RB数据传输，如目标UE的SL DRB 3，即该Uu RLC Channel只能传输源UE和目标UE之间的SL DRB3的数据。这种情况下，源UE从服务节点接收到的承载配置信息中包含Uu RLC Channel关联的SL RB信息，或SL RB关联的Uu RLC Channel信息。其中SL RB可以通过源UE标识，目标UE标识，SL RB标识信息指示。Uu RLC Channel可以通过Uu RLC Channel ID或Logical Channel ID指示。此外源UE的服务节点为源UE配置的Uu RLC Channel也可用于传输源UE与不同对端UE或目标UE的数据。SL RB的SDAP配置中可包含源UE的QoS flow到SL RB的映射。在一示例中，源UE还可接收SL RB与Uu RLC Channel的映射的配置，指示哪些SL RB可以映射到哪个Uu RLC Channel上。
此外路径配置信息可以是Uu传输路径，SL传输路径，或者是Uu传输路径和SL传输路径的信息。路径配置信息可以隐式或显示指示。其中隐式配置可通过承载配置信息来推断。例如服务节点仅仅为UE配置了Uu RLC Channel，并配置了与该Uu RLC Channel关联的SL SRB或是配置了SL RB与Uu RLC Channel的映射，这意味着服务节点指示UE通过Uu传输与对端UE之间对应SL RB数据。又如，如果服务节点仅为UE配置了SL RB对应的SDAP配置，PDCP配置，RLC信道配置，逻辑信道配置，其中SDAP/PDCP/RLC/逻辑信道配置都对应于SL或PC5接口，则隐式意味着UE通过PC5 传输对应SL RB数据。在一示例中，如果服务节点为UE同时配置了Uu RLC Channel和PC5 RLC信道，则隐含意味着UE可选择Uu或PC5进行SL RB数据传输，或是UE可同时通过Uu以及PC5进行SL RB数据传输。
需要注意的是，路径配置信息的粒度可以是每组UE节点对，也可以是每个SL RB。如果是每组UE节点对，则对应于具体的源UE和目标UE，它们之间所有的SL RB传输使用相同的路径。如果是每个SL RB，则对应于具体的源UE，目标UE，SL RB ID组合，该SL RB的数据传输使用相同的路径(e.g.Uu，SL,或Uu和SL)。这意味着对于在一个UE节点对内，不同的SL RB可以使用不同的路径传输。
目标UE可从服务节点接收到类似的配置。当源UE和目标UE的承载和/或路径配置好后，就可以开始将SL数据通过Uu RLC Channel或PC5 RLC Channel进行传输。
2)PC5两跳：源UE和目标UE之间通过中继UE转发：源UE通过PC5接口发送包含目标UE对应的应用层ID的第一发现信息。假设周围的UE1接收到该第一发现信息，且UE1具备PC5信息转发能力，则UE1可以进一步转发该第一发现信息，如果目标UE在UE1附近并接收到包含有目标UE对应的应用层ID的第一发现信息，则目标UE发送第二发现信息，其中可包含以下信息至少之一：目标UE的应用层ID，目标UE的服务节点标识，服务小区标识，驻留小区标识，最大跳数信息，已传输跳数信息，中继节点的节点标识。UE1收到该第二发现信息后在PC5接口进行转发，源UE收到该第二发现消息后，向服务节点发送目标UE的邻近信息，邻近信息包含以下信息至少之一：源UE标识，Destination L2 ID，传输类型(Cast Type)，源UE的APP ID，目标UE的APP ID，目标UE的Serving cell ID，目标UE的服务节点标识，源UE与目标UE之间的链路状态，源UE与目标UE之间的数据流的QoS信息，源UE与所述目标UE之间的跳数，中继节点的节点标识。源UE的服务节点接收到上述邻近信息后，分析源UE和目标UE之间有哪些可能的路径，为源UE和目标UE之间的数据传输选择最合适的传输路径并向源UE发送对应的承载配置信息和/或路径配置信息。
3)PC5多跳：源UE发送的第一发现信息中进一步还可包含允许转发的最大跳数信息。当源UE周围的UE1接收到该第一发现信息，且UE1具备PC5信息转发能力，则UE1可以进一步转发该第一发现信息，在UE1转发该第一发现信息之前，UE1将最大跳数减1。假设UE1周围的UE2收到该第一发现信息，UE2可继续转发该第一发现信息，同样的，UE2在转发之前需要将最大跳数信息信息减1。该第一发现信息可以持续被相邻UE依次转发直到第一发现消息中的最大跳数信息减为0。假设目标UE在UE2附近并接收到包含有目标UE的应用层ID的第一发现信息，则目标UE发送第二发现信息，其中可包含以下信息至少之一：源UE的应用层ID，目标UE的应用层ID，服务节点标识， 服务小区标识，驻留小区标识信息，最大跳数信息，已传输跳数信息。第二发现信息中包含的最大跳数信息与第一发现信息包含的最大跳数信息的用法类似，即每经过一个中继转发节点最大跳数信息减1，直到最大跳数信息减为0，则该第二发现信息被源UE接收，不能再被转发。对于已传输跳数信息，则目标UE可以将第二发现信息中的已传输跳数信息设置为1，当相邻的UE接收到该第二发现信息后，如果继续转发，则将已传输跳数信息加1，直到源UE接收到该第二发现信息。源UE收到目标UE发送的第二发现信息后，可向服务节点发送目标UE的邻近信息，邻近信息包含以下信息至少之一：Destination L2 ID，Serving cell ID，源UE与目标UE之间的跳数，源UE与目标UE之间的数据流的QoS信息。源UE的服务节点接收到上述邻近信息后，分析源UE和目标UE之间有哪些可能的路径，为源UE和目标UE之间的数据传输选择最合适的传输路径并向源UE发送对应的承载及路由配置。
在一示例中，第一发现信息在经过相邻的中继节点转发过程中，每一个中继节点可在第一发现信息中包含自己的节点标识，该节点标识可以是L2 ID或是网络分配的标识。当第一发现信息到达目标UE时，目标UE可以根据第一发现信息中携带的中继节点的节点标识列表，将第二发现消息通过单播方式传输至中继节点，然后依次经过中继节点的转发直到到达源UE。在这种情况下，源UE向服务节点发送目标UE的邻近信息时，可以携带源UE与目标UE之间经过的所有中继节点的节点标识。
在一示例中，服务节点有可能根据信道状态，数据流量，负荷状况等动态更新路径配置信息，例如从SL传输路径转成Uu传输路径，或是从Uu传输路径转成SL传输路径，或是从Uu传输路径转成Uu传输路径与SL传输路径同时传输。对于Uu传输路径和SL传输路径同时传输的情况，服务节点可以进一步配置UE采用数据复制(Data Duplication)或数据分割(Data Split)方式在两条路径上传输对应SL RB的数据。如果UE被服务节点配置采用数据复制方式传递SL RB的数据，则服务节点可以进一步向UE发送数据复制指示，源UE将数据包进行SL PDCP加密后，将数据包投递到Uu RLC Channel以及PC5 RLC Channel进行传输。对端的目标UE通过服务节点配置的Uu RLC Channel以及与源UE之间的PC5 RLC Channel接收到数据包后，统一提交给SL PDCP实体进行排序，丢弃重复包等处理。如果UE被服务节点配置采用数据分割方式传递SL RB的数据，则服务节点可以进一步向UE发送数据分割门限，数据分割比率，主路径指示，辅路径指示和/或路径切换指示等。路径切换指示包括源UE标识、目标UE标识、SL RB标识和/或路径指示。UE可以根据服务节点配置的信息将对应的SL RB数据以数据分割的方式传输。
考虑到路径切换的时效性，可以考虑通过MAC CE(Control Element)发送路径切换指 示，例如通过MAC CE指示SL RB采用的路径，具体的可包含以下信息任意组合：源UE标识，目标UE标识，SL RB ID，路径指示，数据复制或数据分离传输指示。其中路径指示可以是Uu，SL，或Uu和SL。可选的，可以通过bitmap来指示对应的路径。
示例三
除了上述示例描述的UE之间根据PC5接口传输第一发现信息以进行UE邻近发现，还可以考虑由服务节点辅助进行UE邻近发现。
图6为一实施例提供的一种服务节点辅助UE进行邻近发现的示意图。如图6所示，假设UE1(即为源UE)希望与UE2(即为目标UE)进行数据传输，UE1可以组装发现信息，发现信息中可以包含以下信息任意组合：源UE的应用层ID，目标UE的应用层ID，业务类型，安全信息，QoS信息。该发现信息通过服务节点1转发至由服务节点1服务的UE2。
例如，UE1可以通过服务节点1配置的Uu RLC Channel传输发现消息，或是将发现消息通过Uu SRB进行传输。在服务节点1为UE1配置用于传输发现消息的Uu RLC Channel之前，UE1可向服务节点1发送本地传输能力信息(也可以称为传输指示信息)，从而指示或请求服务节点1通过Uu口传输发现消息或SL信令或数据。
图7为一实施例提供的一种服务节点转发发现信息的示意图。如图7所示。服务节点1收到本地传输能力信息后，向UE1发送Uu RLC Channel配置。此外服务节点1可以配置信息类型到Uu RLC Channel的映射，其中信息类型可以是以下类型任意组合：发现信息，PC5连接建立信息，PC5连接修改信息，PC5连接释放信息，PC5保持(Keep Alive)信息，安全消息，PC5-S，PC5-RRC，SL SRB ID，SL DRB ID。类似的，UE2也可向服务节点1发送本地传输能力信息，从而指示或请求服务节点1通过Uu口传输发现消息或SL信令或SL数据。服务节点1收到本地传输能力信息后向UE2发送Uu RLC Channel配置。此外服务节点1可以配置信息类型到Uu RLC Channel的映射，其中信息类型可以是以下类型任意组合：发现信息，PC5连接建立信息，PC5连接修改信息，PC5连接释放信息，PC5保持(Keep Alive)信息，安全消息，PC5-S，PC5-RRC，SL SRB ID，SL DRB ID。
UE1完成Uu RLC Channel配置后，将发现信息发送给服务节点1。UE1发送的发现信息可封装适配子头，其中包含源UE标识，目标UE标识和/或SL RB标识。服务节点1接收到该发现信息后，可以通过Uu口转发发现信息。如果服务节点1知道该发现信息包含的目标UE ID是对应于UE2，则服务节点1可以通过单播方式将发现信息发送给UE2；如果服务节点1不知道该发现信息包含的目标UE ID对应于UE2，或是UE2处于 非活动状态或闲置态，则服务节点1可以广播发送该发现信息。具体的广播可以通过定义新的SIB来传输该发现信息，或通过MBS广播或通过多播传输。对于MBS广播或多播传输的方式，服务节点1可以为支持由服务节点中继SL数据或SL信令的UE、或是为请求服务节点中继转发SL信令或SL数据的UE，配置用于广播SL信令或SL数据的G-RNTI。此外，服务节点1可通过MCCH或专有信令向UE发送SL信令或SL数据的MBS广播或多播配置，MBS广播或多播配置中可包含以下信息任意组合：G-RNTI，SL信息类型，MTCH调度信息等。其中SL信息类型可以包含以下信息任意组合：SL业务类型，SL SRB ID，SL DRB ID，PC5-S或PC5-RRC等。MTCH调度信息可以包含DRX周期内UE被唤醒后的在线时长(ondurationtimer)，被唤醒后每次成功解码PDCCH后保持激活的时长(drxInactivitytimer)，调度周期，调度偏移量，调度周期，调度偏移量等。
对服务节点1转发的SL信令或SL数据接收感兴趣的UE2接收服务节点1发送的发现信息。UE2发现对该发现信息中包含的业务类型感兴趣或是UE2的应用层ID对应于该发现信息中包含的目标UE的应用层ID，则UE2可以通过Uu RLC Channel或SRB向服务节点1发送发现响应信息。服务节点1收到发现响应信息后，如果服务节点1知道该发现响应信息包含的目标UE ID对应于UE1，则服务节点1可以通过单播方式将发现响应信息发送给UE1；如果服务节点1不知道该发现响应信息包含的目标UE ID对应于UE1，则可以广播该发现响应消息。例如，广播可以通过定义SIB来传输，或通过MBS广播或多播传输。MBS广播或多播的过程与前面描述的服务节点发送发现信息的过程类似。
UE1接收服务节点1发送的发现响应信息后就可以完成与UE2之间的邻近发现过程。UE1可以向服务节点1上报发现的UE2的信息，如包含以下信息至少之一：源UEID，目标UEID，源UE的应用标识APP ID，目标UE的APP ID，目标UE的Serving cell ID，UE1与UE2之间数据流的QoS信息。服务节点1接收到上述信息后，分析UE1和UE2之间有哪些可能的路径，为UE1和UE2之间的数据传输选择最合适的传输路径并向UE1和/或UE2发送对应的承载配置信息和/或路径配置信息。
类似的，可以通过上述方式由服务节点转发UE之间的PC5信令消息，PC5发现消息，PC5 RRC信令以及PC5数据。UE将上述PC5相关信令或消息或数据发送给服务节点时采用单播方式，而服务节点在下行转发PC5相关信令或消息或数据时可以根据信令或数据的传输类型(Cast Type)选择在Uu口采用广播或组播或单播方式传输。例如PC5信令本身对应于PC5接口广播传输，则服务节点在Uu口通过广播方式下行传输；如果PC5信令本身对应于PC5接口单播传输，则服务节点在Uu口通过单播方式下行传输。 为了实现这一点，UE在向服务节点发送PC5相关信令或消息或数据时，数据包可携带PC5相关信令或消息或数据的传输类型，源UE标识(Source ID)和/或目标UE标识(Destination ID)。或者UE在向服务节点发送PC5相关信令或消息或数据之前，向服务节点发送Destination ID对应的Cast Type。服务节点收到包含PC5相关信令或消息或数据的数据包对应的Cast Type信息后，可以在Uu口进行对应Cast Type的传输。在一示例中，如果服务节点明确的知道destination ID对应的UE，或是对Destination ID对应的业务类型感兴趣的UE，则服务节点可以通过单播的方式将包含PC5相关信令或消息或数据的数据包发送给一个或多个UE。这里需要注意的是，Destination ID可以是UE自己分配的ID，也可以是服务节点或NGC为UE配置的ID。为了支持服务节点能够根据Destination ID找到对应的UE，或是服务节点能获知对Destination ID对应的业务类型感兴趣的UE，UE可以将自己分配的L2 ID或是NGC为UE分配的ID发送给服务基站。此外UE可以将自己感兴趣接收的业务类型对应的Destination ID和/或对应的Cast Type发送给基站。
示例四
示例3给出了同一个服务节点服务的UE之间通过该服务节点进行邻近发现和/或数据转发，本示例中可以考虑由不同服务节点服务的UE之间的邻近发现和/或数据转发。
例如，如图6所示，假设UE2(即为源UE)希望与UE3(即为目标UE)进行数据传输，UE2组装直接通信请求信息，其中直接通信请求信息包含的内容可参考上述任意示例1。UE2将直接通信请求信息发送给服务节点1。服务节点1收到直接通信请求信息后，如果可以通过直接通信请求信息包含的目标标识识别出直接通信请求的目标UE由服务节点1服务，则服务节点1可以向UE3转发直接通信请求信息；否则，服务节点1在各个小区范围内广播发送直接通信请求信息。具体的广播传输方式可参考上述任意示例。
如图6所示的场景，UE3不在服务节点1的服务区域，而是由服务节点2服务，则服务节点1可向相邻的服务节点2通过Xn接口发送直接通信请求信息。例如，服务节点1和服务节点2之间可以建立一个或多个Xn GTP(GPRS Tunnel Protocol，GPRS隧道协议)-U隧道，用于SL信令和/或SL数据的转发。这些Xn GTP-U隧道有可能是专用导频(UE-specific)的，也有可能是非专用导频(non-UE-specific)的或专用无线承载(SL RB specific)。其中UE-specific的GTP-U隧道，对应于服务节点1和服务节点2分别服务的两个UE对之间的SL信令和/或SL数据转发；SL RB specific的Xn GTP-U隧道，则对应于服务节点1和服务节点2分别服务的两个UE对之间的一个或多个SL RB。这里 SL-RB specific的GTP-U隧道有可能对应于一个SL RB，也有可能是对应于多个SL RB。此外non-UE-specific的Xn GTP-U隧道可用于转发跨服务节点的UE之间的广播或组播数据。在一示例中，对应于不同的广播或组播的目标标识，有可能建立不同的non-UE-specific的Xn GTP-U隧道。
用于转发SL信令或SL数据的GTP-U隧道可以根据图3所示的流程建立。服务节点1向服务节点2发送SL转发请求，其中可包含以下信息任意组合：SL发送请求，SL接收请求，第一SL转发用户面传输层信息，QoS信息，SL-RB ID，PC5-S，PC5-RRC，PC5-D，源UE标识，目标UE标识或目标组标识或目标广播标识，通信类型(单播或广播或多播)指示。其中第一SL转发用户面传输层信息可包含GTP隧道信息，如传输层地址以及GTP-TEID(Tunnel Endpoint Identifier，隧道端点标识符)；QoS信息可以包含以下信息任意组合：PQI，RLC模式，SL RB的QoS参数，映射到SL RB的QoS flow标识，QoS flow的QoS参数。服务节点2收到SL转发请求信息后，向服务节点1发送SL转发响应信息。SL转发响应信息中可包含以下信息任意组合：第二SL转发用户面传输层信息，SL-RB ID，接受的QFI，PC5-S，PC5-RRC，PC5-D，源UE标识，目标UE标识或目标组标识或目标广播标识。其中第二SL转发用户面传输层信息可包含GTP隧道信息，如传输层地址以及GTP-TEID。SL转发请求信息中包含的第一SL转发用户面传输层信息对应于服务节点1侧的传输层信息，而SL转发响应信息中包含的第二SL转发用户面传输层信息对于服务节点2侧的传输层信息。如果是SL RB-specific GTP-U隧道，则SL转发请求信息和SL转发响应信息中，对应于一个SL-RB ID就有一个对应的SL转发用户面传输层信息；如果是对应于UE-specific GTP-U tunnel，则对应于一个源UE标识和一个目标UE标识，就有一个对应的SL转发用户面传输层信息；如果是对应于广播或多播的non-UE specific GTP-U tunnel，则对应于一个目标组标识或目标广播标识，就有一个SL转发用户面传输层信息；如果是对应于不同PC5信令类型的non-UE specific GTP-U tunnel，则对应于一个PC5-S或PC5-RRC或PC5-D类型，就有一个SL转发用户面传输层信息。此外还可以考虑将一个或多个SL SRB或DRB映射到一个Xn GTP-U tunnel。
当服务节点1和服务节点2之间的SL转发隧道建立后，服务节点1可向相邻的服务节点2通过Xn接口转发从UE1接收到的直接通信请求信息，服务节点2收到直接通信请求信息后，如果可以通过直接通信请求信息包含的目标标识识别出直接通信请求的目标UE是由服务节点2服务，则服务节点2可以向UE3转发直接通信请求信息；否则，服务节点2在各个小区广播发送直接通信请求信息。
UE3接收服务节点2发送的直接通信请求信息。如果UE3发现对业务类型感兴趣或是UE3的UE ID对应于直接通信请求信息中包含的目标UE ID或应用ID，则UE3可以 向服务节点2发送直接通信响应信息。服务节点2收到直接通信响应信息后，通过Xn接口的SL转发隧道发送直接通信响应信息给服务节点1。服务节点1可以通过单播或广播方式将直接通信响应信息发送给UE1。
通过上述服务节点的转发，实现了相邻服务节点服务的UE之间的PC5连接建立，后续UE2和UE3之间可以进一步的通过服务节点转发PC5 RRC信令，建立SL DRB，并通过服务节点的转发进行SL数据传输。
需要注意的是，服务节点在为UE节点对转发直接连接建立信息的过程中，可以感知UE节点对之间的邻近性状况，后续服务节点可以为UE配置采用服务节点转发还是通过设备直通链路传输PC5数据。
示例五
本实施例讨论本地传输的UE处于闲置或非激活状态(idle或inactive)状态的场景。如图6所示，假设UE1(即为源UE)希望与处于RRC_IDLE或RRC_INACTIVE态的UE2(即为目标UE)进行数据传输，UE1可以组装发现信息，其中发现信息中可以包含以下信息任意组合：源UE的应用层ID，目标UE的应用层ID，业务类型，安全信息，QoS信息。
UE1可以通过服务节点配置的Uu RLC Channel传输发现信息，或是将发现信息通过Uu SRB进行传输。服务节点1接收到该发现信息后，服务节点1可以通过Uu口转发发现信息。服务节点1可以广播发送该发现消息。具体的广播可以通过定义新的SIB来传输发现信息，或通过MBS广播或多播传输。对于MBS广播或多播传输的方式，服务节点1可以为支持本地传输(即服务节点中继SL数据或SL信令)的UE或是为请求服务节点中继转发SL信令或SL数据的UE配置用于广播SL信令或数据的G-RNTI。此外服务节点1可通过MCCH或专有信令向UE发送SL信令或SL数据的MBS广播或多播配置。
处于RRC_IDLE或RRC_INACTIVE态的UE2接收服务节点1广播发送的发现信息。假设UE2对业务类型感兴趣或是UE2的应用层ID对应于发现信息中包含的目标UE的应用层ID，则UE2可以进入连接态，向服务节点1发送发现响应信息。服务节点1收到发现响应信息后，将发现响应信息发送给UE1。UE1接收服务节点1发送的发现响应信息后就可以完成与UE2之间的邻近发现过程。UE1可以向服务节点1上报发现的UE2的信息，服务节点1接收到上述信息后，分析UE1和UE2之间有哪些可能的路径，为UE1和UE2之间的数据传输选择最合适的传输路径并向UE1和/或UE2发送对应的承载配置信息和/或路径配置信息。
此外，处于RRC_IDLE或RRC_INACTIVE态的UE2接收到服务节点1广播发送的发现信息后，也可以通过PC5接口发送发现响应信息。如果UE1能接收到UE2发送的发现响应信息，则UE1完成与UE2之间的邻近发现过程。UE1可以向服务节点1上报发现的关于UE2的邻近信息，如包含以下信息至少之一：UE1 L2 ID，UE2 L2ID，UE1 APP ID，UE2 APP ID，UE2的serving cell ID，UE1与UE2之间数据流的QoS信息。服务节点1接收到上述邻近信息后，分析UE1和UE2之间有哪些可能的路径，为UE1和UE2之间的数据传输选择最合适的传输路径。假设服务节点1配置UE1使用服务节点转发PC5或SL数据，则UE1可通过PC5接口向UE2发送基站转发数据指示。UE2接收到该指示信息后，进入RRC连接状态，接收服务节点1的传输或基站转发数据的相关配置，后续UE1和UE2之间通过服务节点1转发的数据。此外，UE1向UE2发送的基站转发数据指示可以封装在PC5信令，但是通过Uu口发送给服务节点1，再由服务节点1进一步广播发送给处于RRC_IDLE或RRC_INACTIVE态的UE2。UE2接收到该指示信息后，进入RRC连接状态，接收服务节点1的本地传输或基站转发数据的相关配置，后续UE1和UE2之间通过服务节点1转发的数据。
示例六
本示例给出核心网检测UE1和UE2的邻近性，并指示服务节点通过本地传输转发UE1和UE2之间的数据的场景。
图8为一实施例提供的一种核心网检测邻近UE的实现示意图。如图6所示，UE1和UE2由同一服务节点服务，UE1和UE2之间的数据传输通过PDU(Protocol Data Unit)会话(Session)实现。例如UE1向UE2发送的数据经过服务节点、核心网，然后到应用服务器，再到核心网、服务节点，最后从服务节点发送给UE2。在5G NR(New Radio)中，引入了核心网的本地开关(Local Switch)，即核心网网元SMF(Session Management Function，会话管理功能)确定数据PDU的转发规则，并提供给核心网网元UPF(User Plane Function，用户面功能)，UPF可以根据数据包的IP地址确定将一些数据流进行本地传输，即不经过应用服务器，直接将来自UE1发送给UE2的数据包从UE1的UPF投递到UE2的UPF，UE2的UPF发送至UE2的服务节点，最后由UE2的服务节点将数据包发送给UE2。此外如果UE1和UE2由同一个UPF服务，则UPF收到来自UE1的数据包后，直接将数据包投递到UE2对应的PDU session，发送给UE2的服务节点，最后由UE2的服务基站将数据包发送给UE2。
在一示例中，当UE1和UE2之间的数据传输启动后，核心网网元如SMF可以根据数据包的源和目标IP地址判断是否对应了两个UE的PDU session，如果这两个UE又属 于同一个局域网或本地传输组，则SMF可以告知核心网元如AMF(Access and Mobility Management Function，接入和移动性管理功能)对应的这两个UE的标识信息。核心网元如AMF收到该信息后，进一步判断这两个UE的服务小区和/或服务节点信息。一般来说，UE在接入网络时，服务节点会向AMF发送UE的位置信息，UE的位置信息可以是NCGI(NR cell global identifier)，TAI(Tracking Area Identity，跟踪区标识)，PScell(Primary Serving Cell，主服务小区)信息，以及位置信息对应的时间戳(Time Stamp)。如果UE1和UE2由同一个服务节点服务，或是由两个服务节点服务但这两个服务节点之间有直接接口如Xn接口，则AMF可以将UE1和UE2的邻近信息和/或数据传输信息告知UE1和UE2的服务节点，例如，AMF向UE1的服务节点发送UE1和UE2本地传输信息的任意组合：服务节点转发请求或指示，QoS flow信息如QFI，QoS参数，对端UE标识，对端UE的服务节点标识，对端UE的服务小区标识。UE1的服务节点收到上述信息后，可以根据QoS参数和/或空口资源情况判断是否进行服务节点本地数据转发。在一示例中，服务节点可向AMF发送UE1和UE2的本地传输确认信息的任意组合：服务节点转发响应，可进行服务节点转发的QoS flow信息如QFI，QoS flow的QoS参数，对端UE标识，对端UE的服务服务节点标识，对端UE的服务小区标识，不能进行服务节点转发的UE1的QoS flow信息如QFI，不能进行服务节点转发的原因。
服务节点决定哪些QoS flow进行转发后，服务节点为UE1和/或UE2配置Uu RLC Channel用于传输服务节点在UE1和UE2之间转发的数据。此外服务节点为UE1配置UE2对应的UE标识。在UE1和UE2之间通过服务节点转发数据之前，UE1和UE2可以使用服务节点配置的Uu RLC Channel传输PC5-S信令和/或PC5-RRC，从而完成PC5连接建立，安全认证，秘钥建立和/或SL RB的相关配置。此外服务节点可以向UE1和/或UE2发送SL RB对应的PDCP和/或SDAP的配置，Uu RLC Channel对应的RLC entity，logical Channel的配置，和/或SL RB到Uu RLC Channel的配置。其中SL RB的SDAP配置包含哪些QoS flow映射到SL RB上，即QFI映射到SL RB。或者基站向UE发送QFI到PFI的映射和/或PFI到SL RB的映射。SL RB及Uu RLC Channel配置完成后，UE1和UE2就可以将对应QoS flow的数据包映射到SL RB，并通过Uu RLC Channel进行传输。
除了服务节点配置SL RB及Uu RLC channel，为了减少传输路径转换的时延。可以通过固定配置或是默认配置的Uu RLC channel来传递SL SRB和/或PC5-S信令和/或PC5 RRC信令。
在一示例中，可以考虑服务节点从AMF收到对应于某个UE的服务节点转发授权指示，只有在UE授权进行服务节点转发的情况下，服务节点才会考虑将UE之间的数据通 过服务节点本地转发。
在一示例中，除了上述AMF告知服务节点UE之间的邻近性，由服务节点决策是否进行转发，也可以考虑由AMF向UE1发送UE1和UE2的本地传输信息，本地传输信息包括以下信息的任意组合：服务节点转发请求或指示，可被服务节点转发的QoS flow信息如QFI，QoS参数，对端UE标识，对端UE的服务节点标识，对端UE的服务小区标识。UE1收到上述信息后，可以向服务节点发送本地转发请求指示，通过服务节点的转发建立PC5连接，并将对应QoS flow的数据通过服务节点转发进行传输。
本申请实施例还提供一种数据传输装置。图9为一实施例提供的一种数据传输装置的结构示意图。如图9所示，所述数据传输装置包括：
配置信息接收模块510，设置为接收传输配置信息；
数据传输模块520，设置为根据所述传输配置信息传输数据。
本实施例的数据传输装置，UE根据传输配置信息传输数据，服务节点可以分析潜在可能的传输路径，综合考虑策略、信道状态、负荷等因素，为UE节点对之间的数据传输配置最合适的传输路径，从而进行相应的传输，保证以最有效的方式到达，提高UE之间数据传输的灵活性。
在一实施例中，该装置还包括：邻近信息发送模块，设置为发送目标用户设备UE的邻近信息。
在一实施例中，邻近信息包括以下信息至少之一：源UE标识，目标UE标识，传输类型，源UE的应用标识，目标UE的应用标识，目标UE的服务小区标识，目标UE的服务节点标识，所述源UE与所述目标UE之间的链路状态，所述源UE与所述目标UE之间的数据流的服务质量QoS，所述源UE与所述目标UE之间的跳数，中继节点的节点标识；其中，所述链路状态包括以下至少之一：链路测量结果，链路负荷，SL资源使用率。
在一实施例中，传输配置信息包括承载配置信息和/或路径配置信息。
在一实施例中，承载配置信息包括以下信息至少之一：Uu无线链路层控制协议RLC信道配置；Uu RLC信道标识；Uu逻辑信道配置；直通链路无线承载SL RB对应的服务数据适配协议SDAP配置；SL RB对应的分组数据汇聚协议PDCP配置；SL RB与Uu RLC信道的映射信息。
在一实施例中，承载配置信息包括以下信息至少之一：SL RB对应的SDAP配置，SL RB对应的PDCP配置，PC5 RLC信道配置，PC5逻辑信道配置。
在一实施例中，承载配置信息包括信息类型与Uu RLC信道的映射信息；其中，所 述信息类型包括以下至少之一：发现信息，PC5-S，PC5无线资源控制RRC信息，SL信令无线承载SRB标识，SL数据无线承载DRB标识。
在一实施例中，路径配置信息包括以下信息之一：Uu传输路径；SL传输路径；Uu传输路径和SL传输路径。
在一实施例中，数据传输模块520，设置为：
响应于所述传输配置信息包括Uu传输路径，或者包括Uu RLC信道配置以及所述Uu RLC信道关联的SL SRB，或者包括Uu RLC信道配置以及SL RB与Uu RLC信道的映射信息，通过Uu接口传输对应的SL RB数据；
响应于所述传输配置信息包括SL传输路径，或者包括SL RB对应的SDAP配置、SL RB对应的PDCP配置、PC5 RLC信道配置和/或PC5逻辑信道配置，通过PC5接口传输对应的SL RB数据；
响应于所述传输配置信息包括SL传输路径和Uu传输路径，或包括SL RB对应的Uu RLC信道配置和PC5 RLC信道配置，通过Uu和/或PC5接口传输对应的SL RB数据。
在一实施例中，传输配置信息还包括以下至少之一：
数据复制指示，数据分离传输指示，数据分割门限，数据分割比率，主路径指示，辅路径指示，路径切换指示；
其中，所述路径切换指示包括以下信息至少之一：源UE标识，目标UE标识，SL RB标识，路径指示。
在一实施例中，数据传输模块设置为：
采用数据复制或数据分割的方式，通过Uu接口和PC5接口与所述目标UE传输对应的SL RB数据。
在一实施例中，该装置还包括：
第一信息发送模块，设置为通过PC5接口发送第一发现信息或SL信令或SL数据。
在一实施例中，该装置还包括：第二信息接收模块，设置为通过PC5接口接收目标UE发送或中继UE转发的第二发现信息或SL信令或SL数据；
所述第二发现信息包括以下至少之一：所述目标UE的应用层标识，所述目标UE的服务节点标识，服务小区标识，驻留小区标识，最大跳数信息，已传输跳数信息，中继节点的节点标识。
在一实施例中，该装置还包括：传输指示发送模块，设置为发送本地传输能力信息或者传输指示信息，所述本地传输能力信息或者传输指示信息用于指示或请求服务节点通过Uu接口传输发现信息或SL信令或SL数据。
在一实施例中，发现信息或SL信令或SL数据由所述服务节点通过Uu接口以单播或广播或多播的方式转发。
在一实施例中，通过Uu接口发送的发现信息或SL信令或SL数据携带源UE标识，目标UE标识，和/或SL RB标识。
在一实施例中，在所述发现信息或SL信令或SL数据由服务节点通过MBS广播或多播的方式转发的情况下，服务节点通过多播控制信道MCCH或专有信令传输发现信息或SL信令或SL数据的MBS广播或多播配置；
所述MBS广播或多播配置包括以下至少之一：用于广播SL信令或SL数据的无线网络临时标识G-RNTI，SL信息类型，多播业务信道MTCH调度信息；
其中，所述SL信息类型包括以下至少之一：SL业务类型，SL SRB，SL DRB，PC5-S，PC5-RRC；
所述MTCH调度信息包括以下至少之一：非连续接收DRX周期内UE被唤醒后的在线时长，被唤醒后每次成功解码物理下行控制信道PDCCH后保持激活的时长，调度周期，调度偏移量。
在一实施例中，该装置还包括：发现信息接收模块，设置为通过Uu接口接收目标UE发送的、所述服务节点转发的发现信息或SL信令或SL数据，所述发现信息或SL信令或SL数据携带源UE标识，目标UE标识，和/或SL RB标识。
在一实施例中，响应于已知与目标标识关联的UE，所述服务节点通过单播的方式将包含发现信息或SL数据或SL信令的数据包发送至所述与目标标识关联的UE；其中，所述与目标标识关联的UE包括与所述目标标识对应的UE，和/或对所述目标标识接收感兴趣的UE。
在一实施例中，该装置还包括：第二信息发送模块，设置为将以下信息至少之一发送至服务节点：
NGC分配的UE标识，感兴趣的业务类型对应的目标标识，目标标识对应的传输类型。
在一实施例中，该装置还包括：转发指示发送模块，设置为向目标UE发送服务节点转发SL数据指示。
在一实施例中，响应于所述目标UE处于闲置或非激活状态，在收到服务节点转发SL数据指示后，目标UE进入RRC连接状态。
在一实施例中，该装置还包括：传输指示接收模块，设置为接收核心网网元发送的本地传输指示信息，所述本地传输指示信息用于指示或请求服务节点通过Uu接口传输发现信息或SL信令或SL数据；
其中，所述本地传输指示信息包括以下至少之一：服务节点转发请求或指示，源UE标识，目标UE标识，源UE的服务节点标识，目标UE的服务节点标识，源UE的服务小区标识，目标UE的服务小区标识，QoS流信息；
其中，所述QoS流信息包括以下至少之一：QoS流标识QFI，QoS参数。
在一实施例中，所述传输配置信息由服务节点发送；服务节点包括基站、分布式单元DU，集中式单元CU或集成接入回传IAB节点。
本实施例提出的数据传输装置与上述实施例提出的数据传输方法属于同一发明构思，未在本实施例中详尽描述的技术细节可参见上述任意实施例，并且本实施例具备与执行数据传输方法相同的有益效果。
本申请实施例还提供一种数据传输装置。图10为又一实施例提供的一种数据传输装置的结构示意图。如图10所示，所述数据传输装置包括：
邻近信息接收模块610，设置为接收关于目标UE的邻近信息；
配置信息发送模块620，设置为根据所述邻近信息，发送传输配置信息。
本实施例的数据传输装置，通过接收关于目标UE的邻近信息，可向源UE和目标UE发送相应的传输配置信息。具体的，服务节点可以利用UE上报的邻近信息或者核心网指示的信息，识别UE之间的相对位置，服务小区，DU或CU的接口状态等，分析潜在可能的传输路径，综合考虑策略、信道状态、负荷等因素，为UE节点对之间的数据传输配置最合适的传输路径，从而进行相应的传输，保证以最有效的方式到达，提高UE之间数据传输的灵活性。
在一实施例中，所述邻近信息由源UE发送，或者由核心网网元发送。
在一实施例中，还包括：发信信息接收模块，设置为接收发现信息或SL信令或SL数据，所述发现信息或SL信令或SL数据携带源UE标识，目标UE标识，和/或SL RB标识。
在一实施例中，还包括：传输指示接收模块，设置为接收本地传输能力信息或者传输指示信息，所述本地传输能力信息或者传输指示信息用于指示或请求服务节点通过Uu接口传输发现信息或SL信令或SL数据。
在一实施例中，还包括：发现信息转发模块，设置为通过Uu接口以单播或广播或多播的方式转发发现信息或SL信令或SL数据。
在一实施例中，该包括：配置传输模块，设置为在所述发现信息或SL信令或SL数据由服务节点通过MBS广播或多播的方式转发的情况下，通过MCCH或专有信令传输SL信令或SL数据的MBS广播或多播配置；
所述MBS广播或多播配置包括以下至少之一：G-RNTI，SL信息类型，MTCH调度信息；
其中，所述SL信息类型包括以下至少之一：SL业务类型，SL SRB，SL DRB，PC5-S，PC5-RRC；
所述MTCH调度信息包括以下至少之一：非连续接收DRX周期内UE被唤醒后的在线时长，被唤醒后每次成功解码PDCCH后保持激活的时长，调度周期，调度偏移量。
在一实施例中，响应于已知与目标标识关联的UE，该装置还包括：
单播模块，设置为通过单播的方式将包含发现信息或SL数据或SL信令的数据包发送至所述与目标标识关联的UE；其中，所述与目标标识关联的UE包括与所述目标标识对应的UE，和/或对所述目标标识接收感兴趣的UE。
本实施例提出的数据传输装置与上述实施例提出的数据传输方法属于同一发明构思，未在本实施例中详尽描述的技术细节可参见上述任意实施例，并且本实施例具备与执行数据传输方法相同的有益效果。
本申请实施例还提供一种数据传输装置。图11为再一实施例提供的一种数据传输装置的结构示意图。如图11所示，所述数据传输装置包括：
转发请求模块710，设置为发送SL转发请求信息；
转发响应模块720，设置为接收SL转发响应信息。
本实施例的数据传输装置，通过向目标UE的服务节点发送SL转发请求信息，并接收目标UE的服务节点发送的SL转发响应信息，从而建立SL转发隧道，实现跨服务节点的UE之间的SL数据传输，提高UE之间数据传输的灵活性。
在一实施例中，所述SL转发请求信息包括以下信息至少之一：SL发送请求，SL接收请求，第一SL转发用户面传输层信息，QoS信息，SL RB标识，PC5-S，PC5-RRC，PC5-D，源UE标识，目标UE标识或目标组标识或目标广播标识，单播或组播或多播指示；
其中，所述第一SL转发用户面传输层信息包括通用无线分组业务GPRS隧道协议信息；
所述QoS信息包括以下至少之一：PQI，RLC模式，SL RB的QoS参数，映射到SL RB的QoS流标识，QoS流的QoS参数。
在一实施例中，所述SL转发响应信息包括以下至少之一：第二SL转发用户面传输层信息，接纳和或不接纳的SL RB标识，接纳和或不接纳的QFI，PC5-S，PC5-RRC，PC5-D，源UE标识，目标UE标识或目标组标识或目标广播标识；
其中，所述第二SL转发用户面传输层信息包括目标服务节点的GPRS隧道协议信息。
在一实施例中，该装置还包括：
节点确定模块，设置为根据待转发的发现信息或SL数据或SL信令包含的目标标识确定发现信息或SL数据或SL信令的目标服务节点，和/或，根据待转发的发现信息或SL数据或SL信令包含的SL RB标识确定与目标服务节点之间的SL数据或SL信令的SL转发隧道；
将待转发的发现信息或SL数据或SL信令投递到SL转发隧道并转发至所述目标服务节点；
在一实施例中，所述发现信息或SL信息或SL信令由所述目标服务节点转发至目标UE，或者在目标服务节点的每个服务小区广播发送。
在一实施例中，所述SL转发请求信息由第一服务节点发送，所述SL转发响应信息由第二服务节点发送；
其中，所述第一服务节点为第一基站、第一分布式单元、第一集中式单元、第一IAB节点或第三分布式单元；
相应的，所述第二服务节点为第二基站、第二分布式单元、第二集中式单元、第二IAB节点或第三集中式单元。
本实施例提出的数据传输装置与上述实施例提出的数据传输方法属于同一发明构思，未在本实施例中详尽描述的技术细节可参见上述任意实施例，并且本实施例具备与执行数据传输方法相同的有益效果。
本申请实施例还提供一种数据传输装置。图12为又一实施例提供的一种数据传输装置的结构示意图。如图12所示，所述数据传输装置包括：
传输信息接收模块810，设置为接收UE的本地传输信息；
确认信息发送模块820，设置为向核心网发送本地传输确认信息。
本实施例的数据传输装置，通过接收核心网网元发送的本地传输信息，并向核心网发送本地传输确认信息，从而在核心网的辅助下，完成UE之间的邻近发现和SL数据传输，提高UE之间数据传输的灵活性。
在一实施例中，该装置还包括：配置信息发送模块，设置为向UE发送传输配置信息。
在一实施例中，本地传输信息由所述核心网网元发送；所述本地传输信息包括以下至少之一：UE的服务节点转发发现信息或SL信令或SL数据授权指示，服务节点转发请求或指示，源UE标识，目标UE标识，源UE的服务节点标识，目标UE的服务节点 标识，源UE的服务小区标识，目标UE的服务小区标识，QoS流信息；其中，所述QoS流信息包括以下至少之一：QFI，QoS参数。
在一实施例中，所述本地传输确认信息包括以下至少之一：服务节点本地转发响应，可被服务节点转发的源UE的QoS流信息，不可被服务节点转发的源UE的QoS流信息，不可被服务节点转发的原因。
在一实施例中，源UE或目标UE通过Uu接口RLC信道传输SL RB数据。
在一实施例中，该装置还包括：
发现信息转发模块，设置为响应于接收到UE的服务节点转发授权指示，转发所述UE的SL信令或SL数据。
在一实施例中，所述源UE和所述目标UE通过固定配置或默认配置的Uu接口RLC信道传输PC5-S和/或PC5-RRC。
本实施例提出的数据传输装置与上述实施例提出的数据传输方法属于同一发明构思，未在本实施例中详尽描述的技术细节可参见上述任意实施例，并且本实施例具备与执行数据传输方法相同的有益效果。
本申请实施例还提供了一种用户设备，图13为一实施例提供的一种用户设备的结构示意图，如图13所示，本申请提供的用户设备，包括存储器902、处理器901以及存储在存储器上并可在处理器上运行的计算机程序，处理器901执行所述程序时实现上述的数据传输方法。
用户设备还可以包括存储器902；该用户设备中的处理器901可以是一个或多个，图13中以一个处理器901为例；存储器902用于存储一个或多个程序；所述一个或多个程序被所述一个或多个处理器901执行，使得所述一个或多个处理器901实现如本申请实施例中所述的数据传输方法。
用户设备还包括：通信装置903、输入装置904和输出装置905。
用户设备中的处理器901、存储器902、通信装置903、输入装置904和输出装置905可以通过总线或其他方式连接，图13中以通过总线连接为例。
输入装置904可用于接收输入的数字或字符信息，以及产生与用户设备的用户设置以及功能控制有关的按键信号输入。输出装置905可包括显示屏等显示设备。
通信装置903可以包括接收器和发送器。通信装置903设置为根据处理器901的控制进行信息收发通信。
存储器902作为一种计算机可读存储介质，可设置为存储软件程序、计算机可执行程序以及模块，如本申请实施例所述数据传输方法对应的程序指令/模块(例如，数据传 输装置中的配置信息接收模块510、数据传输模块520)。存储器902可包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序；存储数据区可存储根据用户设备的使用所创建的数据等。此外，存储器902可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实例中，存储器902可进一步包括相对于处理器901远程设置的存储器，这些远程存储器可以通过网络连接至用户设备。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
本申请实施例还提供了一种服务节点，图14为一实施例提供的一种服务节点的结构示意图，如图14所示，本申请提供的服务节点，包括存储器912、处理器911以及存储在存储器上并可在处理器上运行的计算机程序，处理器911执行所述程序时实现上述的数据传输方法。
服务节点还可以包括存储器912；该服务节点中的处理器911可以是一个或多个，图14中以一个处理器911为例；存储器912用于存储一个或多个程序；所述一个或多个程序被所述一个或多个处理器911执行，使得所述一个或多个处理器911实现如本申请实施例中所述的数据传输方法。
服务节点还包括：通信装置913、输入装置914和输出装置915。
服务节点中的处理器911、存储器912、通信装置913、输入装置914和输出装置915可以通过总线或其他方式连接，图14中以通过总线连接为例。
输入装置914可用于接收输入的数字或字符信息，以及产生与服务节点的用户设置以及功能控制有关的按键信号输入。输出装置915可包括显示屏等显示设备。
通信装置913可以包括接收器和发送器。通信装置913设置为根据处理器911的控制进行信息收发通信。
存储器912作为一种计算机可读存储介质，可设置为存储软件程序、计算机可执行程序以及模块，如本申请实施例所述数据传输方法对应的程序指令/模块(例如，数据传输装置中的邻近信息接收模块610、配置信息发送模块620)。存储器912可包括存储程序区和存储数据区，其中，存储程序区可存储操作系统、至少一个功能所需的应用程序；存储数据区可存储根据服务节点的使用所创建的数据等。此外，存储器912可以包括高速随机存取存储器，还可以包括非易失性存储器，例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。在一些实例中，存储器912可进一步包括相对于处理器911远程设置的存储器，这些远程存储器可以通过网络连接至服务节点。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
本申请实施例还提供一种存储介质，所述存储介质存储有计算机程序，所述计算机程序被处理器执行时实现本申请实施例中任一所述的数据传输方法。该方法包括：接收传输配置信息；根据所述传输配置信息传输数据。或者该方法包括：接收关于目标UE的邻近信息；根据所述邻近信息，发送路径配置信息。或者该方法包括：发送SL转发请求信息；接收SL转发响应信息。或者该方法包括：接收UE的本地传输信息；向核心网发送本地传输确认信息。
本申请实施例的计算机存储介质，可以采用一个或多个计算机可读的介质的任意组合。计算机可读介质可以是计算机可读信号介质或者计算机可读存储介质。计算机可读存储介质例如可以是，但不限于：电、磁、光、电磁、红外线、或半导体的系统、装置或器件，或者任意以上的组合。计算机可读存储介质的更具体的例子(非穷举的列表)包括：具有一个或多个导线的电连接、便携式计算机磁盘、硬盘、随机存取存储器(Random Access Memory，RAM)、只读存储器(Read Only Memory，ROM)、可擦式可编程只读存储器(Erasable Programmable Read Only Memory，EPROM)、闪存、光纤、便携式CD-ROM(Compact Disc Read-Only Memory)、光存储器件、磁存储器件、或者上述的任意合适的组合。计算机可读存储介质可以是任何包含或存储程序的有形介质，该程序可以被指令执行系统、装置或者器件使用或者与其结合使用。
计算机可读的信号介质可以包括在基带中或者作为载波一部分传播的数据信号，其中承载了计算机可读的程序代码。这种传播的数据信号可以采用多种形式，包括但不限于：电磁信号、光信号或上述的任意合适的组合。计算机可读的信号介质还可以是计算机可读存储介质以外的任何计算机可读介质，该计算机可读介质可以发送、传播或者传输用于由指令执行系统、装置或者器件使用或者与其结合使用的程序。
计算机可读介质上包含的程序代码可以用任何适当的介质传输，包括但不限于：无线、电线、光缆、无线电频率(Radio Frequency，RF)等等，或者上述的任意合适的组合。
可以以一种或多种程序设计语言或其组合来编写用于执行本申请操作的计算机程序代码，所述程序设计语言包括面向对象的程序设计语言，诸如Java、Smalltalk、C++，还包括常规的过程式程序设计语言，诸如“C”语言或类似的程序设计语言。程序代码可以完全地在用户计算机上执行、部分地在用户计算机上执行、作为一个独立的软件包执行、部分在用户计算机上部分在远程计算机上执行、或者完全在远程计算机或服务器上执行。在涉及远程计算机的情形中，远程计算机可以通过任意种类的网络，包括局域网(LAN，Local Area Network)或广域网(WAN，Wide Area Network)，连接到用户计算机，或者， 可以连接到外部计算机(例如利用因特网服务提供商来通过因特网连接)。
以上所述，仅为本申请的示例性实施例而已，并非用于限定本申请的保护范围。
本领域内的技术人员应明白，术语用户终端涵盖任何适合类型的无线用户设备，例如移动电话、便携数据处理装置、便携网络浏览器或车载移动台。
一般来说，本申请的多种实施例可以在硬件或专用电路、软件、逻辑或其任何组合中实现。例如，一些方面可以被实现在硬件中，而其它方面可以被实现在可以被控制器、微处理器或其它计算装置执行的固件或软件中，尽管本申请不限于此。
本申请的实施例可以通过移动装置的数据处理器执行计算机程序指令来实现，例如在处理器实体中，或者通过硬件，或者通过软件和硬件的组合。计算机程序指令可以是汇编指令、指令集架构(Instruction Set Architecture，ISA)指令、机器指令、机器相关指令、微代码、固件指令、状态设置数据、或者以一种或多种编程语言的任意组合编写的源代码或目标代码。
本申请附图中的任何逻辑流程的框图可以表示程序步骤，或者可以表示相互连接的逻辑电路、模块和功能，或者可以表示程序步骤与逻辑电路、模块和功能的组合。计算机程序可以存储在存储器上。存储器可以具有任何适合于本地技术环境的类型并且可以使用任何适合的数据存储技术实现，例如但不限于只读存储器(Read-Only Memory，ROM)、随机访问存储器(Random Access Memory，RAM)、光存储器装置和系统(数码多功能光碟(Digital Video Disc，DVD)或光盘(Compact Disk，CD)等。计算机可读介质可以包括非瞬时性存储介质。数据处理器可以是任何适合于本地技术环境的类型，例如但不限于通用计算机、专用计算机、微处理器、数字信号处理器(Digital Signal Processing，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑器件(Field-Programmable Gate Array，FGPA)以及基于多核处理器架构的处理器。
通过示范性和非限制性的示例，上文已提供了对本申请的示范实施例的详细描述。但结合附图和权利要求来考虑，对以上实施例的多种修改和调整对本领域技术人员来说是显而易见的，但不偏离本申请的范围。因此，本申请的恰当范围将根据权利要求确定。

Claims (47)

  1. 一种数据传输方法，包括：
    接收传输配置信息；
    根据所述传输配置信息传输数据。
  2. 根据权利要求1所述的方法，还包括：
    发送目标用户设备UE的邻近信息。
  3. 根据权利要求2所述的方法，其中，所述邻近信息包括以下至少之一：
    源UE标识，目标UE标识，传输类型，源UE的应用标识，目标UE的应用标识，目标UE的服务小区标识，目标UE的服务节点标识，所述源UE与所述目标UE之间的链路状态，所述源UE与所述目标UE之间的数据流的服务质量QoS，所述源UE与所述目标UE之间的跳数，中继节点的节点标识；
    其中，所述链路状态包括以下至少之一：链路测量结果，链路负荷，直通链路SL资源使用率。
  4. 根据权利要求1所述的方法，其中，所述传输配置信息包括承载配置信息和路径配置信息中的至少一个。
  5. 根据权利要求4所述的方法，其中，所述承载配置信息包括以下至少之一：
    Uu无线链路层控制协议RLC信道配置；Uu RLC信道标识；Uu逻辑信道配置；直通链路无线承载SL RB对应的服务数据适配协议SDAP配置；SL RB对应的分组数据汇聚协议PDCP配置；SL RB与Uu RLC信道的映射信息。
  6. 根据权利要求4所述的方法，其中，所述承载配置信息包括以下至少之一：
    SL RB对应的SDAP配置，SL RB对应的PDCP配置，PC5 RLC信道配置，PC5逻辑信道配置。
  7. 根据权利要求4所述的方法，其中，所述承载配置信息包括信息类型与Uu RLC信道的映射信息；
    其中，所述信息类型包括以下至少之一：
    发现信息，PC5-S，PC5无线资源控制RRC信息，SL信令无线承载SRB标识，SL数据无线承载DRB标识。
  8. 根据权利要求4所述的方法，其中，所述路径配置信息包括以下之一：
    Uu传输路径；SL传输路径；Uu传输路径和SL传输路径。
  9. 根据权利要求1所述的方法，其中，根据所述传输配置信息传输数据，包括：
    响应于所述传输配置信息包括Uu传输路径，或者包括Uu RLC信道配置以及所述Uu RLC信道关联的SL SRB，或者包括Uu RLC信道配置以及SL RB与Uu RLC信道的映射信息，通过Uu接口传输对应的SL RB数据；
    响应于所述传输配置信息包括SL传输路径，或者包括SL RB对应的SDAP配置、SL RB对应的PDCP配置、PC5 RLC信道配置和PC5逻辑信道配置中的至少一个，通过PC5接口传输对应的SL RB数据；
    响应于所述传输配置信息包括SL传输路径和Uu传输路径，或包括SL RB对应的Uu RLC信道配置和PC5 RLC信道配置，通过Uu和PC5接口中的至少一个传输对应的SL RB数据。
  10. 根据权利要求1所述的方法，其中，所述传输配置信息还包括以下至少之一：
    数据复制指示，数据分离传输指示，数据分割门限，数据分割比率，主路径指示，辅路径指示，路径切换指示；
    其中，所述路径切换指示包括以下至少之一：源UE标识，目标UE标识，SL RB标识，路径指示。
  11. 根据权利要求10所述的方法，其中，根据所述传输配置信息传输数据，包括：
    采用数据复制或数据分割的方式，通过Uu接口和PC5接口与所述目标UE传输对应的SL RB数据。
  12. 根据权利要求1所述的方法，还包括：
    通过PC5接口发送第一发现信息或SL信令或SL数据。
  13. 根据权利要求1或12所述的方法，还包括：通过PC5接口接收目标UE发送或中继UE转发的第二发现信息或SL信令或SL数据；
    所述第二发现信息包括以下至少之一：所述目标UE的应用层标识，所述目标UE的服务节点标识，服务小区标识，驻留小区标识，最大跳数信息，已传输跳数信息，中继节点的节点标识。
  14. 根据权利要求1所述的方法，还包括：发送本地传输能力信息或者传输指示信息，所述本地传输能力信息或者传输指示信息用于指示或请求服务节点通过Uu接口传输发现信息或SL信令或SL数据。
  15. 根据权利要求1或14所述的方法，其中，所述发现信息或SL信令或SL数据由所述服务节点通过Uu接口以单播或广播或多播的方式转发。
  16. 根据权利要求15所述的方法，其中，
    通过Uu接口发送的所述发现信息或SL信令或SL数据携带以下至少之一：源UE标识，目标UE标识，SL RB标识。
  17. 根据权利要求15所述的方法，还包括：在所述发现信息或SL信令或SL数据由服务节点通过多播广播服务MBS广播或多播的方式转发的情况下，所述服务节点通过多播控制信道MCCH或专有信令传输发现信息或SL信令或SL数据的MBS广播或多播配置；
    所述MBS广播或多播配置包括以下至少之一：用于广播SL信令或SL数据的分组无线 网络临时标识G-RNTI，SL信息类型，多播业务信道MTCH调度信息；
    其中，所述SL信息类型包括以下至少之一：SL业务类型，SL SRB，SL DRB，PC5-S，PC5-RRC；
    所述MTCH调度信息包括以下至少之一：非连续接收DRX周期内UE被唤醒后的在线时长，被唤醒后每次成功解码物理下行控制信道PDCCH后保持激活的时长，调度周期，调度偏移量。
  18. 根据权利要求1或14所述的方法，还包括：通过Uu接口接收目标UE发送的、所述服务节点转发的发现信息或SL信令或SL数据，其中所述发现信息或SL信令或SL数据携带以下至少之一：源UE标识，目标UE标识，SL RB标识。
  19. 根据权利要求15所述的方法，还包括：响应于已知与目标标识关联的UE，所述服务节点通过单播的方式将包含发现信息或SL数据或SL信令的数据包发送至所述与目标标识关联的UE；
    其中，所述与目标标识关联的UE包括以下至少之一：与所述目标标识对应的UE，对所述目标标识接收感兴趣的UE。
  20. 根据权利要求1所述的方法，还包括：
    将以下至少之一发送至服务节点：
    核心网分配的UE标识，感兴趣的业务类型对应的目标标识，目标标识对应的传输类型。
  21. 根据权利要求1所述的方法，还包括：
    向目标UE发送服务节点转发SL数据指示。
  22. 根据权利要求21所述的方法，还包括：
    响应于所述目标UE处于闲置或非激活状态，在收到服务节点转发SL数据指示后，目标UE进入RRC连接状态。
  23. 根据权利要求1或14所述的方法，还包括：
    接收核心网网元发送的本地传输指示信息，所述本地传输指示信息用于指示或请求服务节点通过Uu接口传输发现信息或SL信令或SL数据；
    其中，所述本地传输指示信息包括以下至少之一：服务节点转发请求或指示，源UE标识，目标UE标识，源UE的服务节点标识，目标UE的服务节点标识，源UE的服务小区标识，目标UE的服务小区标识，QoS流信息；
    其中，所述QoS流信息包括以下至少之一：QoS流标识QFI，QoS参数。
  24. 根据权利要求1所述的方法，其中，所述传输配置信息由服务节点发送；
    所述服务节点包括基站、分布式单元DU，集中式单元CU或集成接入回传IAB节点。
  25. 一种数据传输方法，包括：
    接收关于目标UE的邻近信息；
    根据所述邻近信息，发送传输配置信息。
  26. 根据权利要求25所述的方法，其中，
    所述邻近信息由源UE发送，或者由核心网网元发送。
  27. 根据权利要求25所述的方法，还包括：
    接收发现信息或SL信令或SL数据，其中所述发现信息或SL信令或SL数据携带以下至少之一：源UE标识，目标UE标识，SL RB标识。
  28. 根据权利要求27所述的方法，还包括：
    接收本地传输能力信息或者传输指示信息，所述本地传输能力信息或者传输指示信息用于指示或请求服务节点通过Uu接口传输发现信息或SL信令或SL数据。
  29. 根据权利要求28所述的方法，还包括：
    通过Uu接口以单播或广播或多播的方式转发发现信息或SL信令或SL数据。
  30. 根据权利要求29所述的方法，还包括：在所述发现信息或SL信令或SL数据由服务节点通过MBS广播或多播的方式转发的情况下，通过MCCH或专有信令传输SL信令或SL数据的MBS广播或多播配置；
    所述MBS广播或多播配置包括以下至少之一：G-RNTI，SL信息类型，MTCH调度信息；
    其中，所述SL信息类型包括以下至少之一：SL业务类型，SL SRB，SL DRB，PC5-S，PC5-RRC；
    所述MTCH调度信息包括以下至少之一：非连续接收DRX周期内UE被唤醒后的在线时长，被唤醒后每次成功解码PDCCH后保持激活的时长，调度周期，调度偏移量。
  31. 根据权利要求29所述的方法，还包括：响应于已知与目标标识关联的UE，通过单播的方式将包含发现信息或SL数据或SL信令的数据包发送至所述与目标标识关联的UE；
    其中，所述与目标标识关联的UE包括以下至少之一：与所述目标标识对应的UE，对所述目标标识接收感兴趣的UE。
  32. 一种数据传输方法，包括：
    发送SL转发请求信息；
    接收SL转发响应信息。
  33. 根据权利要求32所述的方法，其中，
    所述SL转发请求信息包括以下至少之一：SL发送请求，SL接收请求，第一SL转发用户面传输层信息，QoS信息，SL RB标识，PC5-S，PC5-RRC，PC5-D，源UE标识，目标UE标识或目标组标识或目标广播标识，单播或组播或多播指示；
    其中，所述第一SL转发用户面传输层信息包括通用无线分组业务GPRS隧道协议信息；
    所述QoS信息包括以下至少之一：PC5质量指示PQI，RLC模式，SL RB的QoS参数，映射到SL RB的QoS流标识，QoS流的QoS参数。
  34. 根据权利要求32所述的方法，其中，所述SL转发响应信息包括以下至少之一：第二SL转发用户面传输层信息，接纳和或不接纳的SL RB标识，接纳和或不接纳的QFI，PC5-S，PC5-RRC，PC5-D，源UE标识，目标UE标识或目标组标识或目标广播标识；
    其中，所述第二SL转发用户面传输层信息包括目标服务节点的GPRS隧道协议信息。
  35. 根据权利要求32所述的方法，还包括：
    根据待转发的发现信息或SL数据或SL信令包含的目标标识确定发现信息或SL数据或SL信令的目标服务节点，和/或，根据待转发的发现信息或SL数据或SL信令包含的SL RB标识确定与目标服务节点之间的SL数据或SL信令的SL转发隧道；
    将待转发的发现信息或SL数据或SL信令投递到SL转发隧道并转发至所述目标服务节点。
  36. 根据权利要求35所述的方法，其中，所述发现信息或SL信息或SL信令由所述目标服务节点转发至目标UE，或者在目标服务节点的每个服务小区广播发送。
  37. 根据权利要求32所述的方法，其中，
    所述SL转发请求信息由第一服务节点发送，所述SL转发响应信息由第二服务节点发送；
    其中，所述第一服务节点为第一基站、第一分布式单元、第一集中式单元、第一IAB节点或第三分布式单元；
    相应的，所述第二服务节点为第二基站、第二分布式单元、第二集中式单元、第二IAB节点或第三集中式单元。
  38. 一种数据传输方法，包括：
    接收UE的本地传输信息；
    向核心网发送本地传输确认信息。
  39. 根据权利要求38所述的方法，还包括：
    向UE发送传输配置信息。
  40. 根据权利要求38所述的方法，其中，所述本地传输信息由所述核心网网元发送；
    所述本地传输信息包括以下至少之一：UE的服务节点转发发现信息或SL信令或SL数据授权指示，服务节点转发请求或指示，源UE标识，目标UE标识，源UE的服务节点标识，目标UE的服务节点标识，源UE的服务小区标识，目标UE的服务小区标识，QoS流信息；
    其中，所述QoS流信息包括以下至少之一：QFI，QoS参数。
  41. 根据权利要求38所述的方法，其中，
    所述本地传输确认信息包括以下至少之一：服务节点本地转发响应，可被服务节点转发 的源UE的QoS流信息，不可被服务节点转发的源UE的QoS流信息，不可被服务节点转发的原因。
  42. 根据权利要求38或39所述的方法，其中，源UE或目标UE通过Uu接口RLC信道传输SL RB数据。
  43. 根据权利要求40所述的方法，还包括：
    响应于接收到UE的服务节点转发授权指示，转发所述UE的SL信令或SL数据。
  44. 根据权利要求42所述的方法，其中，所述源UE和所述目标UE通过固定配置或默认配置的Uu接口RLC信道传输PC5-S和PC5-RRC中的至少一个。
  45. 一种用户设备，包括存储器、处理器以及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现如权利要求1-24中任一项所述的数据传输方法。
  46. 一种服务节点，包括存储器、处理器以及存储在存储器上并可在处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现如权利要求25-44中任一项所述的数据传输方法。
  47. 一种计算机可读存储介质，所述计算机可读存储介质上存储有计算机程序，所述计算机程序被处理器执行时实现如权利要求1-44中任一所述的数据传输方法。
PCT/CN2022/096114 2021-06-07 2022-05-31 数据传输方法、用户设备、服务节点及存储介质 Ceased WO2022257808A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
KR1020247000392A KR20240017923A (ko) 2021-06-07 2022-05-31 데이터 전송 방법, 사용자 기기, 서빙 노드 및 기록 매체
EP22819406.4A EP4354913A4 (en) 2021-06-07 2022-05-31 Data transmission method, user equipment, service node and storage medium
US18/565,789 US20240276243A1 (en) 2021-06-07 2022-05-31 Data transmission method, user equipment, service node and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110633948.0A CN115515094A (zh) 2021-06-07 2021-06-07 数据传输方法、用户设备、服务节点及存储介质
CN202110633948.0 2021-06-07

Publications (1)

Publication Number Publication Date
WO2022257808A1 true WO2022257808A1 (zh) 2022-12-15

Family

ID=84424628

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/096114 Ceased WO2022257808A1 (zh) 2021-06-07 2022-05-31 数据传输方法、用户设备、服务节点及存储介质

Country Status (5)

Country Link
US (1) US20240276243A1 (zh)
EP (1) EP4354913A4 (zh)
KR (1) KR20240017923A (zh)
CN (1) CN115515094A (zh)
WO (1) WO2022257808A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024152223A1 (zh) * 2023-01-17 2024-07-25 北京小米移动软件有限公司 目标感知方法、系统及装置、通信设备及存储介质

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022208435A1 (en) * 2021-04-02 2022-10-06 Telefonaktiebolaget Lm Ericsson (Publ) Communication device power saving when communication device monitors multicast control channel notification channel
CN117561764A (zh) * 2021-06-23 2024-02-13 瑞典爱立信有限公司 用于侧链路不连续接收的方法和装置
CN115811804B (zh) * 2021-09-14 2026-03-13 大唐移动通信设备有限公司 一种信息处理方法、装置、终端设备及网络设备
US20230327977A1 (en) * 2022-04-12 2023-10-12 Qualcomm Incorporated Configuration for forwarding signals over different types of wireless communication links
US20240064553A1 (en) * 2022-08-22 2024-02-22 Qualcomm Incorporated Priority based channel access procedure for sidelink communications
CN119631456A (zh) * 2023-01-19 2025-03-14 中兴通讯股份有限公司 用于多径传输的数据拆分
CN116339717B (zh) * 2023-05-30 2023-08-25 北京拓普丰联信息科技股份有限公司 一种数据执行方法、装置、设备和介质
KR20250015908A (ko) * 2023-07-21 2025-02-03 아서스 테크놀러지 라이센싱 아이엔씨. 무선 통신 시스템에서 다중-홉 ue-대-네트워크 릴레이를 지원하기 위한 방법 및 장치
WO2025240687A1 (en) * 2024-05-16 2025-11-20 Interdigital Patent Holdings, Inc. Methods, architectures, apparatuses and systems for one to many communication with multihop device-to-device relay

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015003395A1 (zh) * 2013-07-12 2015-01-15 华为技术有限公司 一种多用户协同通信触发方法及设备
CN105101430A (zh) * 2014-05-08 2015-11-25 中兴通讯股份有限公司 D2d资源的配置、分配方法及装置
CN108391285A (zh) * 2017-02-03 2018-08-10 中兴通讯股份有限公司 一种设备直通系统的通信方法、数据转发方法及装置

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109417695B (zh) * 2017-01-10 2020-10-23 华为技术有限公司 一种通信路径转换方法及设备
EP4344325A3 (en) * 2017-05-04 2024-12-11 Koninklijke Philips N.V. Intra-group communication
CN108990125B (zh) * 2017-06-01 2020-12-22 华为技术有限公司 数据传输的方法、终端设备和网络设备
CN116405902A (zh) * 2018-08-10 2023-07-07 中兴通讯股份有限公司 车联网中直通链路的资源配置方法及装置
KR102858140B1 (ko) * 2019-01-30 2025-09-10 삼성전자주식회사 무선 통신 시스템에서 직접 통신 베어러의 서비스 품질을 관리 및 설정하는 장치 및 방법
KR102823446B1 (ko) * 2019-07-02 2025-06-20 삼성전자주식회사 무선 통신 시스템에서 사이드링크 데이터 베어러 설정 방법 및 장치
US11601893B2 (en) * 2019-08-15 2023-03-07 Qualcomm Incorporated Sidelink coordination for power control
US11765616B2 (en) * 2019-11-19 2023-09-19 Huawei Technologies Co., Ltd. Methods, apparatus, and systems for UE cooperation with UE relaying
CN121418946A (zh) * 2020-02-13 2026-01-27 中兴通讯股份有限公司 sidelink中继通信方法、通信设备及存储介质
CN111901836A (zh) * 2020-02-13 2020-11-06 中兴通讯股份有限公司 链路切换、链路切换配置方法、装置、通信节点及介质
CN113473614B (zh) * 2020-03-30 2024-11-26 华为技术有限公司 确定资源的方法和装置
CN113573327B (zh) * 2020-04-28 2023-11-10 维沃移动通信有限公司 远端ue的传输方法、配置方法、装置及电子设备
EP4162716B1 (en) * 2020-07-24 2026-02-11 Apple Inc. Data exchange procedures for relay wireless devices
KR20230156708A (ko) * 2021-03-18 2023-11-14 퀄컴 인코포레이티드 사이드링크 사용자 장비 식별 포지셔닝

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015003395A1 (zh) * 2013-07-12 2015-01-15 华为技术有限公司 一种多用户协同通信触发方法及设备
CN104429142A (zh) * 2013-07-12 2015-03-18 华为技术有限公司 一种多用户协同通信触发方法及设备
CN105101430A (zh) * 2014-05-08 2015-11-25 中兴通讯股份有限公司 D2d资源的配置、分配方法及装置
CN108391285A (zh) * 2017-02-03 2018-08-10 中兴通讯股份有限公司 一种设备直通系统的通信方法、数据转发方法及装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
CATT: "NR Sidelink UP Protocol Stack and Functions", 3GPP DRAFT; R2-1816892, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Spokane, USA; 20181112 - 20181116, 2 November 2018 (2018-11-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051480832 *
See also references of EP4354913A4

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024152223A1 (zh) * 2023-01-17 2024-07-25 北京小米移动软件有限公司 目标感知方法、系统及装置、通信设备及存储介质

Also Published As

Publication number Publication date
CN115515094A (zh) 2022-12-23
KR20240017923A (ko) 2024-02-08
EP4354913A4 (en) 2025-06-25
EP4354913A1 (en) 2024-04-17
US20240276243A1 (en) 2024-08-15

Similar Documents

Publication Publication Date Title
WO2022257808A1 (zh) 数据传输方法、用户设备、服务节点及存储介质
CN111901847B (zh) sidelink中继通信方法、装置、设备及介质
US11917449B2 (en) Communication method and device and storage medium
TWI681687B (zh) 處理尋呼的方法和裝置
US20230371111A1 (en) Communication method, apparatus, and system
WO2021164564A1 (zh) 传输组播业务的方法和装置
US20240121659A1 (en) Data transmission method, user equipment, and storage medium
WO2021088661A1 (zh) 通信方法、装置及设备
WO2020001317A1 (zh) V2x通信方法、装置及系统
WO2016161886A1 (zh) 在设备直通系统中用户终端与中继节点的通信方法和装置
CN106162512A (zh) 一种中继承载控制方法和装置
CN106162930A (zh) 在设备直通系统中承载的管理方法和装置
KR102689205B1 (ko) 브로드캐스트/멀티캐스트 서비스 관리 방법, 장치, 전자 설비, 저장 매체
WO2017024909A1 (zh) 一种进行数据传输的方法和设备
WO2024027412A1 (zh) 通信方法、通信装置及通信系统
CN115734170B (zh) 一种组播/广播会话管理方法及通信装置
WO2023087321A1 (zh) 通信方法及装置
CN115515186A (zh) 一种数据转发方法及装置、网络设备
CN109474913B (zh) 一种多跳传输方法和装置
WO2024074148A1 (zh) 通信方法、装置及系统
WO2024037210A1 (zh) 广播安全通信的方法和装置
WO2023231032A1 (zh) 非激活态组播业务区域的确定方法、配置方法、及装置
WO2022213799A1 (zh) 一种多播业务的通信方法及装置
WO2024099230A1 (zh) 广播安全通信的方法和装置
GB2640971A (en) Methods and apparatus for managing relay communication in multi-hop relay

Legal Events

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

Ref document number: 22819406

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 18565789

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 202317089358

Country of ref document: IN

ENP Entry into the national phase

Ref document number: 20247000392

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 1020247000392

Country of ref document: KR

WWE Wipo information: entry into national phase

Ref document number: 2022819406

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2022819406

Country of ref document: EP

Effective date: 20240108