WO2022057892A1 - 业务数据传输方法及装置、终端和基站 - Google Patents

业务数据传输方法及装置、终端和基站 Download PDF

Info

Publication number
WO2022057892A1
WO2022057892A1 PCT/CN2021/119043 CN2021119043W WO2022057892A1 WO 2022057892 A1 WO2022057892 A1 WO 2022057892A1 CN 2021119043 W CN2021119043 W CN 2021119043W WO 2022057892 A1 WO2022057892 A1 WO 2022057892A1
Authority
WO
WIPO (PCT)
Prior art keywords
wlan
entity
service data
logically connected
protocol stack
Prior art date
Application number
PCT/CN2021/119043
Other languages
English (en)
French (fr)
Inventor
金巴·迪·阿达姆布巴卡
杨晓东
Original Assignee
维沃移动通信有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 维沃移动通信有限公司 filed Critical 维沃移动通信有限公司
Priority to EP21868714.3A priority Critical patent/EP4216658A4/en
Publication of WO2022057892A1 publication Critical patent/WO2022057892A1/zh
Priority to US18/119,680 priority patent/US20230217464A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/25—Control channels or signalling for resource management between terminals via a wireless link, e.g. sidelink
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/15—Setup of multiple wireless link connections
    • H04W76/16—Involving different core network technologies, e.g. a packet-switched [PS] bearer in combination with a circuit-switched [CS] bearer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0268—Traffic management, e.g. flow control or congestion control using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
    • H04W28/0263—Traffic management, e.g. flow control or congestion control per individual bearer or channel involving mapping traffic to individual bearers or channels, e.g. traffic flow template [TFT]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/22—Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • 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
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/02—Data link layer protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/10—Small scale networks; Flat hierarchical networks
    • H04W84/12—WLAN [Wireless Local Area Networks]
    • 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/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/02—Inter-networking arrangements
    • 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 belongs to the technical field of wireless communication, and in particular relates to a service data transmission method and device, a terminal and a base station.
  • the Uu interface between the network side equipment and the terminal user equipment can support interoperability with the wireless local area network (Wireless Local Area Network, WLAN), but the secondary link ( Sidelink, SL) interface does not support interoperability with WLAN.
  • WLAN Wireless Local Area Network
  • SL Sidelink
  • the WLAN interface uses unlicensed spectrum, the bandwidth is shared, and the cost is low or no cost. And the UE has a WLAN interface, which is already standard, and there is no additional hardware cost. If the SL interface between the UE and the UE supports interoperability with the WLAN, the transmission rate between the UEs will be greatly improved, and the path configuration of different services can be performed according to the service characteristics, and the user experience can be improved on the basis of ensuring QoS.
  • the purpose of the embodiments of the present application is to provide a service data transmission method and device, a terminal and a base station, which can solve the problem of currently not supporting the interoperation between SL and WLAN.
  • a first aspect provides a service data transmission method, which is applied to a terminal, and the method includes:
  • the service data is sent and/or received.
  • a service data transmission method applied to a base station, and the method includes:
  • the service data is sent and/or received.
  • a service data transmission device including:
  • the transmission module is used for sending and/or receiving service data according to the SL and WLAN interoperation configuration information.
  • a communication device comprising a processor, a memory, and a program or instruction stored on the memory and executable on the processor, the program or instruction being executed by the processor When executed, the steps of the method according to the first aspect are realized; or, when the program or instructions are executed by the processor, the steps of the method according to the second aspect are realized.
  • a readable storage medium is provided, and a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the steps of the method according to the first aspect are implemented; or the The programs or instructions, when executed by a processor, implement the steps of the method as described in the second aspect.
  • a sixth aspect provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a network-side device program or instruction, implementing the method as described in the first aspect. or, implement the method described in the second aspect.
  • a program product is provided, the program product is stored in a non-volatile storage medium, and the program product is executed by at least one processor to implement the method according to the first aspect; or, the The program product is executed by at least one processor to implement the method of the second aspect.
  • the relay terminal and the remote terminal in the secondary link can better use the unlicensed spectrum WLAN and SL to perform interoperation transmission operation, thereby improving user services.
  • speed guarantees the QoS of UE services, improves user experience, and guarantees system efficiency and network spectrum utilization.
  • FIG. 1 is a block diagram of a wireless communication system to which an embodiment of the present application can be applied;
  • FIG. 2 is a schematic diagram of a user plane protocol stack of a sidelink interface in the related art
  • FIG. 3 is a schematic diagram of a control plane protocol stack of a sidelink interface in the related art
  • FIG. 4 is a schematic flowchart of a service data transmission method according to an embodiment of the present application.
  • FIG. 5 is a schematic diagram of a control plane architecture of an SL and WLAN interoperability scenario involved in an embodiment of the present application
  • Fig. 6 is the schematic diagram of the user plane protocol stack structure of the SL and WLAN interoperability scenario involved in Fig. 5;
  • FIG. 7 is a schematic diagram of a control plane architecture of an SL and WLAN interoperability scenario involved in another embodiment of the present application.
  • Fig. 8 is the schematic diagram of the user plane protocol stack structure of the SL and WLAN interoperability scenario involved in Fig. 7;
  • FIG. 9 is a schematic diagram of a control plane architecture of an SL and WLAN interoperation scenario involved in another embodiment of the present application.
  • Figure 10 is a schematic diagram of the user plane protocol stack structure of the SL and WLAN interoperability scenario involved in Figure 9;
  • FIG. 11 is a schematic structural diagram of a service data transmission apparatus according to an embodiment of the present application.
  • FIG. 12 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • FIG. 13 is a schematic diagram of a hardware structure of a terminal implementing an embodiment of the present application.
  • FIG. 14 is a schematic diagram of a hardware structure of a base station implementing an embodiment of the present application.
  • first, second and the like in the description and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It is to be understood that the data so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and "first”, “second” distinguishes Usually it is a class, and the number of objects is not limited.
  • the first object may be one or multiple.
  • “and/or” in the description and claims indicates at least one of the connected objects, and the character “/" generally indicates that the associated objects are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-Advanced LTE-Advanced
  • LTE-A Long Term Evolution-Advanced
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency-Division Multiple Access
  • system and “network” in the embodiments of the present application are often used interchangeably, and the described technology can be used not only for the above-mentioned systems and radio technologies, but also for other systems and radio technologies.
  • NR New Radio
  • the following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the description below, although these techniques are also applicable to applications other than NR system applications, such as 6th generation ( 6th Generation , 6G) communication system.
  • 6th generation 6th Generation
  • FIG. 1 shows a block diagram of a wireless communication system to which the embodiments of the present application can be applied.
  • the wireless communication system includes a terminal 11 and a network-side device 12 .
  • the terminal 11 may also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital computer Assistant (Personal Digital Assistant, PDA), PDA, Netbook, Ultra-mobile Personal Computer (UMPC), Mobile Internet Device (MID), Wearable Device (Wearable Device) or vehicle-mounted device (Vehicle User Equipment, VUE), pedestrian terminal (Pedestrian User Equipment, PUE) and other terminal-side devices, wearable devices include: bracelets, headphones, glasses, etc.
  • the network side device 12 may be a base station or a core network, wherein the base station may be referred to as a Node B, an evolved Node B, an access point, a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a basic service Set (Basic Service Set, BSS), Extended Service Set (Extended Service Set, ESS), Node B, Evolved Node B (eNB), Home Node B, Home Evolved Node B, WLAN Access Point, WiFi Node, Send Transmitting Receiving Point (TRP) or some other suitable term in the field, as long as the same technical effect is achieved, the base station is not limited to specific technical terms.
  • the base station in the NR system is taken as an example, but the specific type of the base station is not limited.
  • LTE Long Term Evolution
  • sidelinks sidelinks, or translated as sidelinks, sidelinks, sidelinks, etc.
  • end-user equipment User Equipment, Direct data transmission between UEs, which may also be referred to as terminals for short, is not performed through network-side devices.
  • LTE sidelink is suitable for specific public safety affairs (such as emergency communication in fire sites or disaster sites such as earthquakes), or vehicle to everything (V2X) communication.
  • Vehicle networking communication includes various services, such as basic safety communication, advanced (autonomous) driving, formation, sensor expansion, and so on. Since the LTE sidelink only supports broadcast communication, it is mainly used for basic security communication. Other advanced V2X services with strict quality of service (QoS) requirements in terms of delay and reliability will be transmitted through the new air interface (New Radio, NR) sidelink support.
  • QoS quality of service
  • the 5G NR system can be used in the working frequency band above 6 GHz that is not supported by LTE, and supports a larger working bandwidth.
  • the current version of the NR system only supports the interface between the base station and the terminal, and does not yet support the Sidelink interface for direct communication between terminals.
  • Sidelink link interface can also be called PC5 interface.
  • the current sidelink transmission is also mainly divided into several transmission forms: broadcast (broadcast), multicast (groupcast), and unicast (unicast).
  • Unicast as its name implies, is one-to-one transmission.
  • Multicast is a one-to-many transmission. Broadcasting is also a one to many transmission, but broadcasting does not have the concept that UEs belong to the same group.
  • HARQ Hybrid Automatic Repeat reQuest
  • the resource allocation modes of Sidelink UE are divided into two categories:
  • Base station scheduling mode (Mode 1): It is controlled by the base station and allocates resources to each UE.
  • UE autonomous mode each UE autonomously selects resources.
  • the user plane (User Plane, UP) protocol stack between two UEs includes from the bottom layer to the high layer: physical layer (physical layer, PHY), media access control (Media access control (Media Access Control) Access Control, MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), Service Data Adaption Protocol (SDAP).
  • the control plane (Control Plane, CP) protocol stack includes from the bottom layer to the high layer: PHY, MAC, RLC, PDCP, Radio Resource Control (Radio Resource Control, RRC) (PC5-S).
  • FIG. 4 is a schematic flowchart of a service data transmission method according to an embodiment of the present application.
  • the method is applied to a communication device.
  • the communication device may be a terminal or a base station.
  • the methods described include:
  • Step 41 Send and/or receive service data according to the SL and the wireless local area network WLAN interoperability configuration information.
  • the relay terminal and the remote terminal in the secondary link can better use the unlicensed spectrum WLAN and SL to perform interoperation transmission operation, thereby improving user services. rate, to ensure the quality of service (Quality of Service, QoS) of UE services, and to improve user experience while ensuring system efficiency and network spectrum utilization.
  • QoS Quality of Service
  • the SL and WLAN interoperation configuration information includes at least one of SL and WLAN interoperation configuration information configured by the base station and SL and WLAN interoperation configuration information configured by the relay terminal.
  • the SL and WLAN interoperation configuration information configured by the base station includes at least one of the following:
  • DRB Data Radio Bearer
  • Service QoS flow information capable of WLAN offloading or replication, distribution and transmission
  • Service DRB information capable of WLAN offloading or replication, distribution and transmission
  • Interface or port information for WLAN to transmit data
  • the SL and WLAN interoperation configuration information configured by the relay terminal includes at least one of the following:
  • the communication device is a relay terminal, and according to the SL and WLAN interoperability configuration information, before sending and/or receiving service data, it further includes at least one of the following:
  • the communication device is a remote terminal, and before sending and/or receiving service data according to the SL and WLAN interoperability configuration information, the method further includes:
  • the communication device is a base station, and before sending and/or receiving service data according to the SL and WLAN interoperability configuration information, the method further includes:
  • the base station may send the SL and WLAN interoperability configuration information to the relay terminal and/or the remote terminal through dedicated radio resource control (Radio Resource Control, RRC) signaling.
  • RRC Radio Resource Control
  • the base station sends the SL and WLAN interoperation configuration information to the relay terminal through RRC dedicated signaling, and the relay terminal forwards it to the remote terminal.
  • the base station sends the SL and WLAN interoperability configuration information to the relay terminal and the remote terminal in a broadcast manner (eg, a System Information Block (SIB) message).
  • SIB System Information Block
  • sending and/or receiving service data includes one of the following:
  • the transmission and/or reception of service data is completely accomplished through the WLAN bearer.
  • the above three bearer modes may include the bearer of service data and the bearer of signaling.
  • FIG. 5 is a schematic diagram of a control plane architecture of an SL and WLAN interoperability scenario involved in an embodiment of the application.
  • the relay terminal in the secondary link is connected to the base station through the Uu interface, and the relay terminal At the same time, as the SL node and the WLAN node, the relay terminal and the remote end are connected through the PC5 interface and the WLAN interface, that is, the SL and the WLAN node are co-located.
  • FIG. 6 is a schematic diagram of a user plane protocol stack structure of the SL and WLAN interoperation scenario involved in FIG. 5 .
  • the interoperability of SL and WLAN means that in the existing SL architecture, a part of the data flow needs to be offloaded to WLAN for transmission, and unified management and control are performed.
  • the three types of bearers mentioned above are:
  • SL bearer a bearer that is completely transmitted through the PC5 interface and resources
  • SL and WLAN offload bearer bearer transmitted through PC5 interface and resources and WLAN interface and resources;
  • WLAN bearer A bearer that is transported entirely through the WLAN interface and resources.
  • the above three bearer modes may include the bearer of service data and the bearer of signaling.
  • both the relay terminal and the remote terminal include: a first protocol stack, where the first protocol stack is used to carry the PC5 interface and the WLAN interface between the relay terminal and the remote terminal.
  • the first protocol stack includes a first PDCP entity, a first RLC entity logically connected to the first PDCP entity, a MAC entity logically connected to the first RLC entity, and a PHY entity logically connected to the MAC entity (Fig. not shown), an adaptation entity (SLWAAP) logically connected to the first PDCP entity, a WLAN entity logically connected to the adaptation entity, and a PHY entity (not shown) logically connected to the WLAN entity .
  • the first PDCP entity performs reordering and copying and distribution operations.
  • the above-mentioned completing the sending and/or receiving of the service data through the SL and the WLAN offload bearer includes: sending and/or receiving the service data through the first protocol stack.
  • the relay terminal and the remote terminal further include: a fourth protocol stack, where the fourth protocol stack is used to carry the PC5 interface between the relay terminal and the remote terminal, and the fourth protocol stack is used to carry the PC5 interface between the relay terminal and the remote terminal.
  • the four-protocol stack includes: a second PDCP entity, a second RLC entity logically connected to the second PDCP entity, a MAC entity logically connected to the second RLC entity, and a PHY entity logically connected to the MAC entity (Fig. not shown).
  • the first protocol stack and the fourth protocol stack share one MAC entity.
  • the above-mentioned complete sending and/or receiving of service data through the SL bearer includes: sending and/or receiving service data through the fourth protocol stack.
  • the relay terminal and the remote terminal may further include: a fifth protocol stack, where the fifth protocol stack is used to carry the WLAN interface between the relay terminal and the remote terminal, the The fifth protocol stack includes: a WLAN entity (not shown in the figure) and a PHY entity (not shown in the figure) logically connected with the WLAN entity.
  • the above-mentioned complete sending and/or receiving of service data through the WLAN bearer includes: sending and/or receiving service data through the fifth protocol stack.
  • FIG. 7 is a schematic diagram of a control plane architecture of an SL and WLAN interoperability scenario involved in another embodiment of the present application.
  • a relay terminal acts as an SL node and is set independently from a WLAN node, that is, the SL and WLAN Nodes are not co-located.
  • the WLAN node may be, for example, a 5G-RG (5G Home Gateway).
  • the relay terminal and the WLAN node can be connected to the base station (gNB) through the Uu interface, the relay terminal is connected to the remote terminal through the PC5 interface, and the WLAN node is connected to the remote terminal through the WLAN interface.
  • the WLAN may use a WiFi connection.
  • FIG. 8 is a schematic diagram of a user plane protocol stack structure of the SL and WLAN interoperation scenario involved in FIG. 7 .
  • Uu-PC5 and Uu-WLAN interoperate, and the data flow is distributed from the base station to the centralized flow 1 to Uu-PC5 and flow 2 to Uu-WLAN.
  • SL bearer a bearer that is completely transmitted through the Uu-PC5 interface and resources;
  • SL and WLAN offload bearer bearer transmitted through Uu-PC5 interface and resources and Uu-WLAN interface and resources at the same time;
  • WLAN bearer A bearer that is transmitted entirely through the Uu-WLAN interface and resources.
  • the above three bearer modes may include the bearer of service data and the bearer of signaling.
  • the base station includes a second protocol stack, and the second protocol stack includes a first PDCP entity (for example, NR PDCP), and a first RLC entity (for example, a primary network node (MN) RLC entity) logically connected to the first PDCP entity. ), a MAC entity logically connected to the first RLC entity, a PHY entity (not shown in the figure) logically connected to the MAC entity, a second RLC entity logically connected to the first PDCP entity (for example, a secondary A network node (SN) RLC entity), a MAC entity logically connected to the second RLC entity, and a PHY entity (not shown) logically connected to the MAC entity.
  • a first PDCP entity for example, NR PDCP
  • MN primary network node
  • the above-mentioned completing the sending and/or receiving of the service data through the SL and the WLAN offload bearer includes: sending and/or receiving the service data between the second protocol stack and the remote terminal.
  • the base station further includes a sixth protocol stack, where the sixth protocol stack includes a second PDCP entity (for example, an NR PDCP), and a third RLC entity (for example, an MN RLC entity) logically connected to the second PDCP entity. ), a MAC entity logically connected to the third RLC entity, and a PHY entity (not shown in the figure) logically connected to the MAC entity.
  • the sixth protocol stack includes a second PDCP entity (for example, an NR PDCP), and a third RLC entity (for example, an MN RLC entity) logically connected to the second PDCP entity. ), a MAC entity logically connected to the third RLC entity, and a PHY entity (not shown in the figure) logically connected to the MAC entity.
  • the above-mentioned complete sending and/or receiving of service data through the SL bearer includes: sending and/or receiving service data between the sixth protocol stack and the remote terminal.
  • the base station further includes a seventh protocol stack, where the seventh protocol stack includes a third PDCP entity (for example, an NR PDCP), and a fourth RLC entity (for example, an SN RLC entity) that is logically connected to the third PDCP entity. ), a MAC entity logically connected to the fourth RLC entity, and a PHY entity (not shown in the figure) logically connected to the MAC entity.
  • the seventh protocol stack includes a third PDCP entity (for example, an NR PDCP), and a fourth RLC entity (for example, an SN RLC entity) that is logically connected to the third PDCP entity. ), a MAC entity logically connected to the fourth RLC entity, and a PHY entity (not shown in the figure) logically connected to the MAC entity.
  • the seventh protocol stack includes a third PDCP entity (for example, an NR PDCP), and a fourth RLC entity (for example, an SN RLC entity) that is logically
  • the above-mentioned complete sending and/or receiving of service data through the WLAN bearer includes: sending and/or receiving service data between the seventh protocol stack and the remote terminal.
  • the remote terminal includes: a first protocol stack, where the first protocol stack includes a first PDCP entity, a first RLC entity logically connected to the first PDCP entity, and a first RLC entity that is logically connected to the first PDCP entity.
  • a MAC entity logically connected to the first RLC entity, a PHY entity (not shown in the figure) logically connected to the MAC entity, an adaptation entity (SLWAAP) logically connected to the first PDCP entity, and the adaptation entity
  • a WLAN entity that is logically connected and a PHY entity (not shown) that is logically connected to the WLAN entity.
  • the above-mentioned completing the sending and/or receiving of the service data through the SL and the WLAN offloading bearer includes: the remote terminal sends and/or receives the service data through the first protocol stack.
  • the remote terminal further includes: a fourth protocol stack, where the fourth protocol stack includes: a second PDCP entity, a second RLC entity logically connected to the second PDCP entity, and a second RLC entity that is logically connected to the second PDCP entity A logically connected MAC entity, and a PHY entity (not shown) logically connected to the MAC entity.
  • the first protocol stack and the fourth protocol stack in the remote terminal share one MAC entity.
  • the above-mentioned complete sending and/or receiving of service data through the SL bearer includes: the remote terminal sends and/or receives service data through the fourth protocol stack.
  • the remote terminal further includes: a fifth protocol stack, where the fifth protocol stack includes: a WLAN entity (not shown in the figure) and a PHY entity (not shown in the figure) that is logically connected to the WLAN entity.
  • the fifth protocol stack includes: a WLAN entity (not shown in the figure) and a PHY entity (not shown in the figure) that is logically connected to the WLAN entity.
  • the above-mentioned complete sending and/or receiving of the service data through the WLAN bearer includes: the remote terminal sends and/or receives the service data through the fifth protocol stack.
  • the relay terminal includes a fourth protocol stack
  • the fourth protocol stack includes a second PDCP entity, a second RLC entity logically connected to the second PDCP entity, and a second RLC entity that is logically connected to the second PDCP entity.
  • a MAC entity logically connected to the RLC entity and a PHY entity (not shown in the figure) logically connected to the MAC entity.
  • the above-mentioned complete sending and/or receiving of the service data through the SL bearer includes: the relay terminal sends and/or receives the service data through the fourth protocol stack.
  • the WLAN node includes an eighth protocol stack
  • the eighth protocol stack includes a PDCP entity, an adaptation entity (SLWAAP) logically connected to the PDCP entity, and an adaptation entity (SLWAAP) logically connected to the adaptation entity.
  • SLWAAP adaptation entity
  • a WLAN entity and a PHY entity (not shown) logically connected to the WLAN entity.
  • the above-mentioned completing the sending and/or receiving of the service data through the SL and the WLAN offloading bearer includes: the WLAN node sends and/or receives the service data through the eighth protocol stack.
  • the WLAN node further includes: a ninth protocol stack, where the ninth protocol stack includes a WLAN entity, and a PHY entity (not shown in the figure) that is logically connected to the WLAN entity.
  • the above-mentioned complete sending and/or receiving of the service data through the WLAN bearer includes: the WLAN node sends and/or receives the service data through the fifth protocol stack.
  • FIG. 9 is a schematic diagram of a control plane architecture of an SL and WLAN interoperability scenario involved in another embodiment of the present application.
  • WLAN nodes are not co-located.
  • the WLAN node may be, for example, a 5G-RG (5G Home Gateway).
  • the relay terminal is connected to the remote terminal through the PC5 interface, and the WLAN node is connected to the remote terminal through the WLAN interface.
  • the WLAN may use a WiFi connection.
  • the relay terminal and the WLAN node can interact in the following ways: Uu interface, PC5 interface or xUu interface.
  • FIG. 10 is a schematic diagram of a user plane protocol stack structure of the SL and WLAN interoperation scenario involved in FIG. 9 .
  • the interoperability of SL and WLAN means that in the existing SL architecture, a part of the data flow needs to be offloaded to WLAN for transmission, and unified management and control are performed.
  • the three types of bearers mentioned above are:
  • SL bearer a bearer that is completely transmitted through the PC5 interface and resources
  • SL and WLAN offload bearer the bearer transmitted through PC5 interface and resources and WLAN interface and resources;
  • WLAN bearer A bearer that is transported entirely through the WLAN interface and resources.
  • the above three bearer modes may include the bearer of service data and the bearer of signaling.
  • the remote terminals all include: a first protocol stack, where the first protocol stack is used to carry the PC5 interface and the WLAN interface between the relay terminal and the remote terminal, and the first protocol stack includes the first PDCP entity, a first RLC entity logically connected to the first PDCP entity, a MAC entity logically connected to the first RLC entity, a PHY entity (not shown in the figure) logically connected to the MAC entity, and the An adaptation entity (SLWAAP) logically connected to the first PDCP entity, a WLAN entity logically connected to the adaptation entity, and a PHY entity (not shown in the figure) logically connected to the WLAN entity.
  • the first PDCP entity performs reordering and copying and distribution operations.
  • the above-mentioned completing the sending and/or receiving of the service data through the SL and the WLAN offloading bearer includes: the remote terminal sends and/or receives the service data through the first protocol stack.
  • the middle and remote terminals further include: a fourth protocol stack, where the fourth protocol stack is used to carry the PC5 interface between the relay terminal and the remote terminal, and the fourth protocol stack It includes: a second PDCP entity, a second RLC entity logically connected to the second PDCP entity, a MAC entity logically connected to the second RLC entity, and a PHY entity logically connected to the MAC entity (not shown in the figure). ).
  • the first protocol stack and the fourth protocol stack share one MAC entity.
  • the above-mentioned complete sending and/or receiving of service data through the SL bearer includes: the remote terminal sends and/or receives service data through the fourth protocol stack.
  • the remote terminal may further include: a fifth protocol stack, where the fifth protocol stack is used to carry the WLAN interface between the relay terminal and the remote terminal, and the fifth protocol stack It includes: a WLAN entity (not shown in the figure) and a PHY entity (not shown in the figure) logically connected with the WLAN entity.
  • the above-mentioned complete sending and/or receiving of the service data through the WLAN bearer includes: the remote terminal sends and/or receives the service data through the fifth protocol stack.
  • the relay terminal includes: a third protocol stack, where the third protocol stack is used to carry the PC5 interface and the WLAN interface between the relay terminal and the remote terminal, the third protocol stack
  • the stack includes a first PDCP entity, a first RLC entity logically connected to the first PDCP entity, a MAC entity logically connected to the first RLC entity, and a PHY entity logically connected to the MAC entity (not shown in the figure). ), an adaptation entity (SLWAAP) logically connected to the first PDCP entity.
  • SLWAAP adaptation entity
  • the WLAN node includes a tenth protocol stack, where the tenth protocol stack is used to carry the WLAN interface with the remote terminal in the SL and WLAN offload bearer, and the tenth protocol stack includes a logical connection with the adaptation entity in the relay terminal
  • the WLAN entity is a PHY entity (not shown in the figure) that is logically connected to the WLAN entity.
  • the relay terminal also has a fourth protocol stack, where the fourth protocol stack is used to carry the PC5 interface with the remote terminal, and the fourth protocol stack includes a second PDCP entity that communicates with the second PDCP.
  • a second RLC entity that is logically connected to the entity, a MAC entity that is logically connected to the second RLC entity, and a PHY entity (not shown in the figure) that is logically connected to the MAC entity.
  • the first protocol stack and the fourth protocol stack may share a MAC entity.
  • the above-mentioned method for transmitting service data further includes: receiving the WLAN measurement configuration information sent by the base station and/or the relay terminal.
  • the above-mentioned method for transmitting service data further includes:
  • the WLAN measurement configuration information sent by the base station is received and forwarded to the remote terminal.
  • the above-mentioned method for transmitting service data further includes:
  • the WLAN measurement configuration information is sent to the remote terminal through the relay terminal.
  • the WLAN measurement configuration information includes at least one of the following:
  • the WLAN measurement configuration parameters include at least one of the following:
  • WLAN frequency band indication list (bandIndicatorListWLAN): including the WLAN frequency band list.
  • the value band2dot4 represents the 2.4GHz band
  • the value band5 represents the 5GHz band
  • the value band60 represents the 60GHz band.
  • WLAN carrier information list contains the WLAN carrier information list of the measurement object
  • EventId The event ID that triggers the WLAN measurement; the maximum number of cells to be included in the measurement report (excluding serving cells). Only applies if the purpose is ReportStrongTestCellsForSON set to a value of 1. For cross-RAT WLANs, it is the maximum number of WLANs to be included in the measurement report;
  • RSSI Received Signal Strength Indication
  • WLAN-CarrierInfo WLAN carrier information
  • WLAN channel number (channelNumbers);
  • WLAN-Name The name of the WLAN (WLAN-Name); if configured, the UE performs WLAN measurements only according to the identified name. For each name, it refers to the Service Set Identifier (SSID) defined in the protocol;
  • SSID Service Set Identifier
  • Event W2 All WLANs within the WLAN mobility set become worse than threshold 1, and WLANs outside the WLAN mobility set become better than threshold 2;
  • Event W3 All WLANs in the WLAN mobility set become worse than the threshold.
  • the WLAN measurement reporting parameters include at least one of the following:
  • WLAN accessible capacity availableAdmissionCapacityWLAN
  • WLAN backhaul downlink bandwidth (backhaulDL-BandwidthWLAN); WLAN backhaul available downlink bandwidth is equal to the downlink speed multiplied by the downlink load defined by Wi-Fi Alliance Hotspot 2.0;
  • WLAN backhaul uplink bandwidth (backhaulUL-BandwidthWLAN WLAN); WLAN backhaul available uplink bandwidth is equal to the uplink speed multiplied by the uplink load defined by Wi-Fi Alliance Hotspot 2.0;
  • WLAN channel occupancy information indicates the sample percentage when RSSI is higher than the configured ChannelOccupmentNCythreshold
  • indication information for indicating whether the remote terminal is connected to the WLAN to which the measurement result is applicable
  • WLAN measurement result list (measResultListWLAN); a measurement result list of the maximum number of best WLANs reported in addition to the WLAN mobility set identified by the WLAN measurement and the connected WLAN (if any);
  • WLAN RSSI measurement result (rssiWLAN); measure WLAN RSSI result in dBm;
  • the total number of stations associated with the WLAN (stationCountWLAN); indicates the total number of stations currently associated with this WLAN defined by the protocol;
  • WLAN identifiers (wlan-Identifiers); Indicates WLAN parameters used to identify the WLAN to which the measurement result is applicable;
  • the WLAN round-trip event RTT information includes at least one of the following:
  • rttValue This field specifies the round-trip time (RTT) measurement between the target device and the WLAN access point, in units specified by the field rttUnits;
  • rttUnits This field specifies the units for the fields rttValue and rttAccuracy. Available units are 1000ns, 100ns, 10ns, 1ns and 0.1ns;
  • rttAccuracy This field provides the estimated accuracy of the provided rttValue, expressed in units given by the field rttUnits.
  • the 5G system is used as an example, but the above-mentioned transmission method of service data can be extended to other communication systems.
  • the WLAN may use a Wifi interface, and may also use other Bluetooth interfaces, for example.
  • the execution body may be a service data transmission apparatus, or a control module in the service data transmission apparatus for executing the service data transmission method.
  • the device for the service data transmission method provided by the embodiment of the present application is described by taking the service data transmission apparatus executing the service data transmission method as an example.
  • an embodiment of the present application provides a service data transmission apparatus 110, including:
  • the transmission module 111 is configured to send and/or receive service data according to the SL and the wireless local area network WLAN interoperability configuration information.
  • the SL and WLAN interoperation configuration information includes at least one of SL and WLAN interoperation configuration information configured by the base station and SL and WLAN interoperation configuration information configured by the relay terminal.
  • the SL and WLAN interoperation configuration information configured by the base station includes at least one of the following:
  • Service data that can be transmitted by WLAN wirelessly bears DRB information
  • Service QoS flow information capable of WLAN offloading or replication, distribution and transmission
  • Service DRB information capable of WLAN offloading or replication, distribution and transmission
  • Interface or port information for WLAN to transmit data
  • the SL and WLAN interoperation configuration information configured by the relay terminal includes at least one of the following:
  • the service data transmission device is a relay terminal, and the service data transmission device also includes at least one of the following:
  • a first sending module configured to send the SL and WLAN interoperability configuration information to the remote terminal
  • the first receiving module is configured to receive the SL and WLAN interoperation configuration information sent by the base station and forward it to the remote terminal.
  • the service data transmission device is a remote terminal, and the service data transmission device further includes:
  • the second receiving module is configured to receive the SL and WLAN interoperation configuration information sent by the base station and/or the relay terminal.
  • the service data transmission device is a base station, and the service data transmission device further includes:
  • the second sending module is configured to send the SL and WLAN interoperation configuration information to the relay terminal and/or the remote terminal.
  • the transmission module performs one of the following:
  • the transmission and/or reception of service data is completely accomplished through the WLAN bearer.
  • the service data transmission device is a terminal, and the terminal includes a first protocol stack, and the first protocol stack is used to carry the PC5 interface and the WLAN interface between the relay terminal and the remote terminal, and the first protocol stack is used to carry the PC5 interface and the WLAN interface between the relay terminal and the remote terminal.
  • a protocol stack includes a first PDCP entity, a first RLC entity logically connected to the first PDCP entity, a MAC entity logically connected to the first RLC entity, a PHY entity logically connected to the MAC entity, and a The adaptation entity logically connected to the first PDCP entity, the WLAN entity logically connected to the adaptation entity, and the PHY entity logically connected to the WLAN entity.
  • the transmission module is configured to send and/or receive service data through the first protocol stack.
  • the service data transmission device is a base station, and includes a second protocol stack, and the second protocol stack includes a first PDCP entity, a first RLC entity logically connected to the first PDCP entity, and a first RLC entity logically connected to the first PDCP entity.
  • a MAC entity logically connected to an RLC entity, a PHY entity logically connected to the MAC entity, a second RLC entity logically connected to the PDCP entity, a MAC entity logically connected to the second RLC entity, and the MAC entity logically connected to the second RLC entity The PHY entity to which the entity is logically connected.
  • the transmission module is configured to send and/or receive service data between the second protocol stack and the remote terminal.
  • the service data transmission device is a relay terminal, and includes a third protocol stack, the third protocol stack is used to carry the PC5 interface and the WLAN interface between the remote terminal and the remote terminal, and the third protocol stack includes: a first PDCP entity, a first RLC entity logically connected to the first PDCP entity, a MAC entity logically connected to the first RLC, a PHY entity logically connected to the MAC entity, and the first PDCP entity A logically connected adaptation entity, the adaptation entity is logically connected to the WLAN entity of the WLAN node.
  • the transmission module is configured to send and/or receive service data between the second protocol stack and the remote terminal.
  • the relay terminal and the remote terminal in the secondary link can better use the unlicensed spectrum WLAN and SL to perform interoperation transmission operation, thereby improving user services.
  • speed guarantees the QoS of UE services, improves user experience, and guarantees system efficiency and network spectrum utilization.
  • the service data transmission apparatus in this embodiment of the present application may be a device, or may be a component, an integrated circuit, or a chip in a terminal.
  • the device may be a mobile terminal or a non-mobile terminal.
  • the mobile terminal may include, but is not limited to, the types of terminals 11 listed above, and the non-mobile terminal may be a server, a network attached storage (NAS), a personal computer (personal computer, PC), a television ( television, TV), teller machine, or self-service machine, etc., which are not specifically limited in the embodiments of the present application.
  • the service data transmission device in the embodiment of the present application may be a device with an operating system.
  • the operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, which are not specifically limited in the embodiments of the present application.
  • an embodiment of the present application further provides a communication device 120, including a processor 121, a memory 122, and a program or instruction stored in the memory 122 and running on the processor 121
  • the communication device 120 may be a terminal, and when the program or instruction is executed by the processor 121, each process of the above-mentioned embodiment of the method for transmitting service data applied to the terminal can be realized, and the same technical effect can be achieved. To avoid repetition, here No longer.
  • the communication device 120 may also be a base station, and when the program or instruction is executed by the processor 121, each process of the above-mentioned embodiment of the method for transmitting service data applied to the base station is implemented, and the same technical effect can be achieved, In order to avoid repetition, details are not repeated here.
  • FIG. 13 is a schematic diagram of a hardware structure of a terminal implementing an embodiment of the present application.
  • the terminal 130 includes but is not limited to: a radio frequency unit 131, a network module 132, an audio output unit 133, an input unit 134, a sensor 135, a display unit 136, a user input unit 137, an interface unit 138, a memory 139, and a processor 1310 and other components .
  • the terminal 130 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 1310 through a power management system, so as to manage charging, discharging, and power consumption through the power management system management and other functions.
  • a power source such as a battery
  • the terminal structure shown in FIG. 13 does not constitute a limitation on the terminal, and the terminal may include more or less components than shown, or combine some components, or arrange different components, which will not be repeated here.
  • the input unit 134 may include a graphics processor (Graphics Processing Unit, GPU) 1341 and a microphone 1342. Such as camera) to obtain still pictures or video image data for processing.
  • the display unit 136 may include a display panel 1361, which may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like.
  • the user input unit 137 includes a touch panel 1371 and other input devices 1372 .
  • the touch panel 1371 is also called a touch screen.
  • the touch panel 1371 may include two parts, a touch detection device and a touch controller.
  • Other input devices 1372 may include, but are not limited to, physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which will not be described herein again.
  • the radio frequency unit 131 receives the downlink data from the network side device, and then processes it to the processor 1310; in addition, sends the uplink data to the network side device.
  • the radio frequency unit 131 includes, but is not limited to, an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
  • Memory 139 may be used to store software programs or instructions as well as various data.
  • the memory 139 may mainly include a stored program or instruction area and a storage data area, wherein the stored program or instruction area may store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.) and the like.
  • the memory 139 may include a high-speed random access memory, and may also include a non-volatile memory, wherein the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM) , PROM), erasable programmable read-only memory (Erasable PROM, EPROM), electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • ROM Read-Only Memory
  • PROM programmable read-only memory
  • PROM erasable programmable read-only memory
  • Erasable PROM Erasable PROM
  • EPROM electrically erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • flash memory for example at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.
  • the processor 1310 may include one or more processing units; optionally, the processor 1310 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, application programs or instructions, etc., Modem processors mainly deal with wireless communications, such as baseband processors. It can be understood that, the above-mentioned modulation and demodulation processor may not be integrated into the processor 1310.
  • the processor 1310 is configured to send and/or receive service data according to the SL and the wireless local area network WLAN interoperability configuration information.
  • the relay terminal and the remote terminal in the secondary link can better use the unlicensed spectrum WLAN and SL to perform interoperation transmission operation, thereby improving user services.
  • speed guarantees the QoS of UE services, improves user experience, and guarantees system efficiency and network spectrum utilization.
  • the SL and WLAN interoperation configuration information includes at least one of SL and WLAN interoperation configuration information configured by the base station and SL and WLAN interoperation configuration information configured by the relay terminal.
  • the SL and WLAN interoperation configuration information configured by the base station includes at least one of the following:
  • Service data that can be transmitted by WLAN wirelessly bears DRB information
  • Service QoS flow information capable of WLAN offloading or replication, distribution and transmission
  • Service DRB information capable of WLAN offloading or replication, distribution and transmission
  • Interface or port information for WLAN to transmit data
  • the SL and WLAN interoperation configuration information configured by the relay terminal includes at least one of the following:
  • the terminal is a relay terminal
  • the radio frequency unit 131 is configured to send the SL and WLAN interoperation configuration information to the remote terminal; or, receive the SL and WLAN interoperation configuration information sent by the base station and forward it to the remote terminal. end terminal.
  • the terminal is a remote terminal
  • the radio frequency unit 131 is configured to receive the SL and WLAN interoperation configuration information sent by the base station and/or the relay terminal.
  • processor 1310 is configured to execute one of the following:
  • the transmission and/or reception of service data is completely accomplished through the WLAN bearer.
  • the terminal includes a first protocol stack
  • the first protocol stack is used to carry the PC5 interface and the WLAN interface between the relay terminal and the remote terminal
  • the first protocol stack includes a first PDCP entity, A first RLC entity logically connected to the first PDCP entity, a MAC entity logically connected to the first RLC entity, a PHY entity logically connected to the MAC entity, and an adapter logically connected to the first PDCP entity.
  • the processor 1310 is configured to send and/or receive service data through the first protocol stack.
  • the terminal is a relay terminal and includes a third protocol stack, where the third protocol stack is used to carry the PC5 interface and the WLAN interface between the terminal and the remote terminal, and the third protocol stack includes the first PDCP entities, a first RLC entity logically connected to the first PDCP entity, a MAC entity logically connected to the first RLC entity, a PHY entity logically connected to the MAC entity, and a PHY entity logically connected to the first PDCP entity An adaptation entity, which is logically connected to the WLAN entity of the WLAN node.
  • the processor 1310 is configured to send and/or receive service data between the second protocol stack and the remote terminal.
  • the base station 140 includes: an antenna 141 , a radio frequency device 142 , and a baseband device 143 .
  • the antenna 141 is connected to the radio frequency device 142 .
  • the radio frequency device 142 receives information through the antenna 141, and sends the received information to the baseband device 143 for processing.
  • the baseband device 143 processes the information to be sent and sends it to the radio frequency device 142
  • the radio frequency device 142 processes the received information and sends it out through the antenna 141 .
  • the above-mentioned frequency band processing apparatus may be located in the baseband apparatus 143 , and the method performed by the network side device in the above embodiments may be implemented in the baseband apparatus 143 .
  • the baseband apparatus 143 includes a processor 144 and a memory 145 .
  • the baseband device 143 may include, for example, at least one baseband board on which a plurality of chips are arranged, as shown in FIG. 14 , one of the chips is, for example, the processor 144 , which is connected to the memory 145 to call a program in the memory 145 to execute
  • the network devices shown in the above method embodiments operate.
  • the baseband device 143 may further include a network interface 146 for exchanging information with the radio frequency device 142, and the interface is, for example, a common public radio interface (CPRI).
  • CPRI common public radio interface
  • the network-side device in the embodiment of the present invention further includes: an instruction or program stored in the memory 145 and executable on the processor 144, and the processor 144 invokes the instruction or program in the memory 145 to execute the service data shown in FIG. 11 .
  • the transmission device is a base station
  • the method executed by each module achieves the same technical effect, so it is not repeated here in order to avoid repetition.
  • Embodiments of the present application further provide a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, each process of the above-mentioned embodiment of the method for transmitting service data can be achieved, and can achieve The same technical effect, in order to avoid repetition, will not be repeated here.
  • the processor is the processor in the terminal described in the foregoing embodiment.
  • the readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.
  • An embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used for running network-side device programs or instructions to realize the above-mentioned service data transmission
  • the chip includes a processor and a communication interface
  • the communication interface is coupled to the processor
  • the processor is used for running network-side device programs or instructions to realize the above-mentioned service data transmission
  • the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-a-chip, or the like.
  • An embodiment of the present application further provides a program product, the program product is stored in a non-volatile storage medium, the program product is executed by at least one processor to implement each process of the foregoing service data transmission method embodiments, and The same technical effect can be achieved, and in order to avoid repetition, details are not repeated here.

Landscapes

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

Abstract

本申请公开了一种业务数据传输方法及装置、终端和基站。该业务数据传输方法包括：根据SL和WLAN互操作配置信息，进行业务数据的发送和/或接收。

Description

业务数据传输方法及装置、终端和基站
相关申请的交叉引用
本申请主张在2020年9月21日在中国提交的中国专利申请号No.202010997371.7的优先权，其全部内容通过引用包含于此。
技术领域
本申请属于无线通信技术领域，具体涉及一种业务数据传输方法及装置、终端和基站。
背景技术
在相关技术中，网络侧设备与终端用户设备(User Equipment，UE，也可以简称为终端)之间的Uu接口可以支持与无线局域网(Wireless Local Area Network，WLAN)互操作，但副链路(Sidelink，SL)接口并不支持与WLAN互操作。
由于WLAN接口是使用非授权频谱，带宽共享，费用较低或者没有费用。且UE具有WLAN接口已经属于标配，没有额外的硬件成本。如果在UE与UE之间的SL接口支持与WLAN互操作，将大大提升UE之间的传输速率，并可以根据业务特性进行不同业务的路径配置，在保证QoS的基础上，提升用户体验。
然而，目前并不支持SL与WLAN互操作。
发明内容
本申请实施例的目的是提供一种业务数据传输方法及装置、终端和基站，能够解决目前不支持SL与WLAN互操作的问题。
为了解决上述技术问题，本申请是这样实现的：
第一方面，提供了一种业务数据传输方法，应用于终端，该方法包括：
根据SL和无线局域网WLAN互操作配置信息，进行业务数据的发送和/或接收。
第二方面，提供了一种业务数据传输方法，应用于基站，该方法包括：
根据SL和无线局域网WLAN互操作配置信息，进行业务数据的发送和/或接收。
第三方面，提供了一种业务数据传输装置，包括：
传输模块，用于根据SL和WLAN互操作配置信息，进行业务数据的发送和/或接收。
第四方面，提供了一种通信设备，该通信设备包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法的步骤；或者，所述程序或指令被所述处理器执行时实现如第二方面所述的方法的步骤。
第五方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的方法的步骤；或者所述程序或指令被处理器执行时实现如第二方面所述的方法的步骤。
第六方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行网络侧设备程序或指令，实现如第一方面所述的方法；或者，实现如第二方面所述的方法。
第七方面，提供了一种程序产品，所述程序产品存储在非易失的存储介质中，所述程序产品被至少一个处理器执行以实现如第一方面所述的方法；或者，所述程序产品被至少一个处理器执行以实现如第二方面所述的方法。
本申请实施例中，根据SL和WLAN互操作配置信息，能够使副链路中的中继终端和远端终端更好的利用非授权频谱WLAN与SL进行互操作传输操作，从而提升用户的业务速率，保障UE业务的QoS，在提升用户体验的同时保障了系统效率和网络频谱的利用率。
附图说明
图1是本申请实施例可应用的一种无线通信系统的框图；
图2是相关技术中的sidelink接口的用户面协议栈示意图；
图3是相关技术中的sidelink接口的控制面协议栈示意图；
图4是本申请实施例的业务数据传输方法的流程示意图；
图5是本申请一实施例涉及的SL和WLAN互操作场景的控制面架构示意图；
图6是图5中涉及的SL和WLAN互操作场景的用户面协议栈结构示意图；
图7是本申请另一实施例涉及的SL和WLAN互操作场景的控制面架构示意图；
图8是图7中涉及的SL和WLAN互操作场景的用户面协议栈结构示意图；
图9是本申请又一实施例涉及的SL和WLAN互操作场景的控制面架构示意图；
图10是图9中涉及的SL和WLAN互操作场景的用户面协议栈结构示意图；
图11是本申请实施例的业务数据传输装置的结构示意图；
图12是本申请一实施例的通信设备的结构示意图；
图13是实现本申请实施例的一种终端的硬件结构示意图；
图14是实现本申请实施例的一种基站的硬件结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(Code Division Multiple Access，CDMA)、时分多址(Time Division Multiple Access，TDMA)、频分多址(Frequency Division Multiple Access，FDMA)、正交频分多址(Orthogonal Frequency Division Multiple Access，OFDMA)、单载波频分多址(Single-carrier Frequency-Division Multiple Access，SC-FDMA)和其他系统。本申请实施例中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。然而，以下描述出于示例目的描述了新空口(New Radio，NR)系统，并且在以下大部分描述中使用NR术语，尽管这些技术也可应用于NR系统应用以外的应用，如第6代(6 th Generation，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端11和网络侧设备12。其中，终端11也可以称作终端设备或者用户终端(User Equipment，UE)，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、可穿戴式设备(Wearable Device)或车载设备(Vehicle User Equipment，VUE)、行人终端(Pedestrian User Equipment，PUE)等终端侧设备，可穿戴式设备包括：手环、耳机、眼镜等。需要说明的是，在本申请实施例并不限定终端11的具体类型。网络侧设备12可以是基站或核心网，其中，基站可被称为节点B、演进节点B、接入点、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、B节点、演进型B节点(eNB)、家用B节点、家用演进型B节点、WLAN接入点、WiFi节点、发送接收点(Transmitting Receiving Point，TRP)或所述领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例，但是并不限定基站的具体类型。
下面首先介绍与本申请有关的通信术语。
1、Sidelink介绍
长期演进(Long Term Evolution，LTE)系统从第12个发布版本开始支持副链路(sidelink，或译为侧链路，边链路，旁链路等)，用于终端用户设备(User Equipment，UE，也可以简称为终端)之间不通过网络侧设备进行直接数据传输。
LTE sidelink的设计适用于特定的公共安全事务(如火灾场所或地震等灾难场所进行紧急通讯)，或车联网(vehicle to everything，V2X)通信等。车联网通信包括各种业务，例如，基本安全类通信，高级(自动)驾驶，编队，传感器扩展等等。由于LTE sidelink只支持广播通信，因此主要用于基本安全类通信，其他在时延、可靠性等方面具有严格服务质量(Quality of Service，QoS)需求的高级V2X业务将通过新空口(New Radio，NR)sidelink支持。
5G NR系统可用于LTE所不支持的6GHz以上工作频段，支持更大的工作带宽，但目前版本的NR系统只支持基站与终端间的接口，尚不支持终端之间直接通信的Sidelink接口。Sidelink链路接口又可以称作PC5接口。
2、Sidelink的传输形式
目前的sidelink传输也主要分广播(broadcast)，组播(groupcast)，单播(unicast)几种传输形式。单播顾名思义就是一对一(one to one)的传输。组播为一对多(one to many)的传输。广播也是one to many的传输，但是广播并没有UE属于同一个组的概念。
目前Sidelink单播和组播通信支持物理层混合自动重传请求(Hybrid Automatic Repeat reQuest，HARQ)反馈机制。
3、资源分配模式mode 1和mode 2
Sidelink UE的资源分配模式总共分为两类：
1)基站调度模式(Mode 1)：由基站控制并为每个UE分配资源。
2)UE自主模式(Mode 2)：由每个UE自主选择资源。
4、SL协议栈
传统的SL(sidelink)接口，如图2所示，两个UE之间用户面(User Plane，UP)协议栈从底层到高层包括：物理层(physical layer，PHY)，媒体 接入控制(Media Access Control，MAC)，无线链路控制(Radio Link Control，RLC)，分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)，业务数据适应协议(Service Data Adaption Protocol，SDAP)。如图3所示，控制面(Control Plane，CP)协议栈从底层到高层包括：PHY，MAC，RLC，PDCP，无线资源控制(Radio Resource Control，RRC)(PC5-S)。
目前SL并不支持与WLAN互操作，因此没有相关的协议栈或/和WLAN和SL节点之间的接口。
下面结合附图，通过具体的实施例及其应用场景对本申请实施例提供的业务数据的传输方法、终端及通信设备进行详细地说明。
请参考图4，图4为本申请实施例的一种业务数据传输方法的流程示意图，该方法应用于通信设备，本申请实施例中，所述通信设备可以为终端，也可以为基站，所述方法包括：
步骤41：根据SL和无线局域网WLAN互操作配置信息，进行业务数据的发送和/或接收。
本申请实施例中，根据SL和WLAN互操作配置信息，能够使副链路中的中继终端和远端终端更好的利用非授权频谱WLAN与SL进行互操作传输操作，从而提升用户的业务速率，保障UE业务的服务质量(Quality of Service，QoS)，在提升用户体验的同时保障了系统效率和网络频谱的利用率。
本申请实施例中，可选的，所述SL和WLAN互操作配置信息包括基站配置的SL和WLAN互操作配置信息和中继终端配置的SL和WLAN互操作配置信息中的至少一项。
本申请实施例中，可选的，基站配置的SL和WLAN互操作配置信息包括以下至少一项：
支持SL和WLAN互操作；
能够进行WLAN传输的业务特征；
能够进行WLAN传输的业务QoS流信息；
能够进行WLAN传输的业务数据无线承载(Data Radio Bearer，DRB)信息；
能够进行WLAN传输的业务对应的协议栈层的配置；协议栈层例如为 PDCP和/或SDPA等；
能够进行WLAN分流或复制分发(duplication)传输的业务特征；
能够进行WLAN分流或复制分发传输的业务QoS流信息；
能够进行WLAN分流或复制分发传输的业务DRB信息；
能够进行WLAN分流或复制分发传输的业务对应的协议栈层的配置；协议栈层例如为PDCP和/或SDPA等；
进行SL传输的业务特征；
进行SL传输的业务QoS流信息；
进行SL传输的业务DRB信息；
进行SL传输的业务对应的协议栈层的配置；
WLAN传输数据的接口或端口信息。
本申请实施例中，可选的，中继终端配置的SL和WLAN互操作配置信息包括以下至少一项：
WLAN DRB的配置信息；
映射到WLAN DRB的QoS流的配置信息；
WLAN分流或复制分发DRB的配置信息；
映射到WLAN分流DRB的QoS流的配置信息；
WLAN接口或端口配置信息；
SL DRB的配置信息；
映射到SL DRB的QoS流的配置信息；
关于SL和WLAN互操作涉及的WLAN MAC地址信息。
在本申请的一些实施例中，可选的，所述通信设备为中继终端，根据SL和WLAN互操作配置信息，进行业务数据的发送和/或接收之前还包括以下至少一项：
向远端终端发送SL和WLAN互操作配置信息；
接收基站发送的SL和WLAN互操作配置信息并转发给远端终端。
在本申请的一些实施例中，可选的，所述通信设备为远端终端，根据SL和WLAN互操作配置信息，进行业务数据的发送和/或接收之前还包括：
接收基站和/或中继终端发送的SL和WLAN互操作配置信息。
在本申请的一些实施例中，可选的，所述通信设备为基站，根据SL和WLAN互操作配置信息，进行业务数据的发送和/或接收之前还包括：
向中继终端和/或远端终端发送SL和WLAN互操作配置信息。
本申请实施例中，可选的，基站可以通过无线资源控制(Radio Resource Control，RRC)专用信令将SL和WLAN互操作配置信息发送给中继终端和/或远端终端。或者，基站通过RRC专用信令将SL和WLAN互操作配置信息发送给中继终端，由中继终端转发给远端终端。或者，基站通过广播方式(如系统信息块(System Information Block，SIB)消息)将SL和WLAN互操作配置信息发送给中继终端和远端终端。
可选的，根据SL和WLAN互操作配置信息，进行业务数据的发送和/或接收包括以下一项：
完全通过SL承载完成业务数据的发送和/或接收；
通过SL和WLAN分流承载完成业务数据的发送和/或接收；
完全通过WLAN承载完成业务数据的发送和/或接收。
本申请实施例中，可选的，上述三种承载方式，即可以包括业务数据的承载，也可以包括信令的承载。
请参考图5，图5为本申请一实施例涉及的SL和WLAN互操作场景的控制面架构示意图，该种架构下，副链路中的中继终端通过Uu接口与基站连接，中继终端同时作为SL节点和WLAN节点，中继终端和远端之间通过PC5接口和WLAN接口连接，即SL和WLAN节点共站。
请参考图6，图6为图5中涉及的SL和WLAN互操作场景的用户面协议栈结构示意图。
SL与WLAN互操作，则意味着在现有的SL架构中，有一部分数据流要分流到WLAN进行传输，并且进行统一的管理和管控。上述三种类型的承载分别为：
SL承载：完全通过PC5接口及资源进行传输的承载；
SL和WLAN分流承载：通过PC5接口及资源和WLAN接口及资源进行传输的承载；
WLAN承载：完全通过WLAN接口及资源进行传输的承载。
本申请实施例中，可选的，上述三种承载方式，即可以包括业务数据的承载，也可以包括信令的承载。
从图6中可以看出，中继终端和远端终端均包括：第一协议栈，所述第一协议栈用于承载中继终端与远端终端之间的PC5接口和WLAN接口，所述第一协议栈包括第一PDCP实体，与所述第一PDCP实体逻辑连接的第一RLC实体、与所述第一RLC实体逻辑连接的MAC实体、与所述MAC实体逻辑连接的PHY实体(图未示出)、与所述第一PDCP实体逻辑连接的适配实体(SLWAAP)、与所述适配实体逻辑连接的WLAN实体和与所述WLAN实体逻辑连接的PHY实体(图未示出)。其中，在业务数据传输过程中，由第一PDCP实体进行重排序和复制分发操作。
上述通过SL和WLAN分流承载完成业务数据的发送和/或接收包括：通过所述第一协议栈进行业务数据的发送和/或接收。
本申请实施例中，可选的，中继终端和远端终端还包括：第四协议栈，所述第四协议栈用于承载中继终端与远端终端之间的PC5接口，所述第四协议栈包括：第二PDCP实体，与所述第二PDCP实体逻辑连接的第二RLC实体、与所述第二RLC实体逻辑连接的MAC实体，与所述MAC实体逻辑连接的PHY实体(图未示出)。本申请实施例中，第一协议栈和第四协议栈共用一个MAC实体。
上述完全通过SL承载完成业务数据的发送和/或接收包括：通过所述第四协议栈进行业务数据的发送和/或接收。
本申请实施例中，可选的，中继终端和远端终端还可以包括：第五协议栈，所述第五协议栈用于承载中继终端与远端终端之间的WLAN接口，所述第五协议栈包括：WLAN实体(图未示出)以及与所述WLAN实体逻辑连接的PHY实体(图未示出)。
上述完全通过WLAN承载完成业务数据的发送和/或接收包括：通过所述第五协议栈进行业务数据的发送和/或接收。
请参考图7，图7为本申请另一实施例涉及的SL和WLAN互操作场景的控制面架构示意图，该种架构下，中继终端作为SL节点，与WLAN节点独立设置，即SL和WLAN节点不共站。WLAN节点例如可以为5G-RG(5G 家庭网关)。中继终端和WLAN节点可以通过Uu接口与基站(gNB)连接，中继终端通过PC5接口与远端终端连接，WLAN节点通过WLAN接口与远端终端连接。WLAN例如可以采用WiFi连接方式。
请参考图8，图8为图7中涉及的SL和WLAN互操作场景的用户面协议栈结构示意图。
Uu-PC5与Uu-WLAN互操作，数据流从基站分流集中流1走Uu-PC5和流2走Uu-WLAN。
通过Uu-SL与Uu-WLAN互操作，则意味着在现有的Uu-SL架构中，有一部分数据流要分流到Uu-WLAN进行传输，并且进行统一的管理和管控。上述三种类型的承载分别为：
SL承载(bearer)：完全通过Uu-PC5接口及资源进行传输的承载；
SL和WLAN分流承载：同时通过Uu-PC5接口及资源和Uu-WLAN接口及资源进行传输的承载；
WLAN承载：完全通过Uu-WLAN接口及资源进行传输的承载。
本申请实施例中，可选的，上述三种承载方式，即可以包括业务数据的承载，也可以包括信令的承载。
从图8中可以看出：
基站包括第二协议栈，所述第二协议栈包括第一PDCP实体(例如为NR PDCP)，与所述第一PDCP实体逻辑连接的第一RLC实体(例如为主网络节点(MN)RLC实体)、与所述第一RLC实体逻辑连接的MAC实体、与所述MAC实体逻辑连接的PHY实体(图未示出)、与所述第一PDCP实体逻辑连接的第二RLC实体(例如为辅网络节点(SN)RLC实体)，与所述第二RLC实体逻辑连接的MAC实体以及与所述MAC实体逻辑连接的PHY实体(图未示出)。
上述所述通过SL和WLAN分流承载完成业务数据的发送和/或接收包括：通过所述第二协议栈与远端终端之间进行业务数据的发送和/或接收。
可选的，基站还包括第六协议栈，所述第六协议栈包括第二PDCP实体(例如为NR PDCP)，与所述第二PDCP实体逻辑连接的第三RLC实体(例如为MN RLC实体)、与所述第三RLC实体逻辑连接的MAC实体、与所述 MAC实体逻辑连接的PHY实体(图未示出)。
上述完全通过SL承载完成业务数据的发送和/或接收包括：通过所述第六协议栈与远端终端之间进行业务数据的发送和/或接收。
可选的，基站还包括第七协议栈，所述第七协议栈包括第三PDCP实体(例如为NR PDCP)，与所述第三PDCP实体逻辑连接的第四RLC实体(例如为SN RLC实体)、与所述第四RLC实体逻辑连接的MAC实体、与所述MAC实体逻辑连接的PHY实体(图未示出)。
上述完全通过WLAN承载完成业务数据的发送和/或接收包括：通过所述第七协议栈与远端终端之间进行业务数据的发送和/或接收。
本申请实施例中，可选的，远端终端包括：第一协议栈，所述第一协议栈包括第一PDCP实体，与所述第一PDCP实体逻辑连接的第一RLC实体、与所述第一RLC实体逻辑连接的MAC实体、与所述MAC实体逻辑连接的PHY实体(图未示出)、与所述第一PDCP实体逻辑连接的适配实体(SLWAAP)、与所述适配实体逻辑连接的WLAN实体以及与所述WLAN实体逻辑连接的PHY实体(图未示出)。
上述通过SL和WLAN分流承载完成业务数据的发送和/或接收包括：远端终端通过所述第一协议栈进行业务数据的发送和/或接收。
可选的，远端终端还包括：第四协议栈，所述第四协议栈包括：第二PDCP实体，与所述第二PDCP实体逻辑连接的第二RLC实体、与所述第二RLC实体逻辑连接的MAC实体、与所述MAC实体逻辑连接的PHY实体(图未示出)。本申请实施例中，远端终端中的第一协议栈和第四协议栈共用一个MAC实体。
上述完全通过SL承载完成业务数据的发送和/或接收包括：远端终端通过所述第四协议栈进行业务数据的发送和/或接收。
可选的，远端终端还包括：第五协议栈，所述第五协议栈包括：WLAN实体(图未示出)以及与所述WLAN实体逻辑连接的PHY实体(图未示出)。
上述完全通过WLAN承载完成业务数据的发送和/或接收包括：远端终端通过所述第五协议栈进行业务数据的发送和/或接收。
本申请实施例中，可选的，中继终端包括第四协议栈，所述第四协议栈 包括第二PDCP实体，与所述第二PDCP实体逻辑连接的第二RLC实体、与所述第二RLC实体逻辑连接的MAC实体以及与所述MAC实体逻辑连接的PHY实体(图未示出)。
上述完全通过SL承载完成业务数据的发送和/或接收包括：中继终端通过所述第四协议栈进行业务数据的发送和/或接收。
本申请实施例中，可选的，WLAN节点包括第八协议栈，所述第八协议栈包括PDCP实体，与所述PDCP实体逻辑连接的适配实体(SLWAAP)、与适配实体逻辑连接的WLAN实体以及与所述WLAN实体逻辑连接的PHY实体(图未示出)。
上述通过SL和WLAN分流承载完成业务数据的发送和/或接收包括：WLAN节点通过所述第八协议栈进行业务数据的发送和/或接收。
可选的，WLAN节点还包括：第九协议栈，所述第九协议栈包括WLAN实体，与所述WLAN实体逻辑连接的PHY实体(图未示出)。
上述完全通过WLAN承载完成业务数据的发送和/或接收包括：WLAN节点通过所述第五协议栈进行业务数据的发送和/或接收。
请参考图9，图9为本申请又一实施例涉及的SL和WLAN互操作场景的控制面架构的示意图，该种架构下，中继终端作为SL节点，与WLAN节点独立设置，即SL和WLAN节点不共站。WLAN节点例如可以为5G-RG(5G家庭网关)。中继终端通过PC5接口与远端终端连接，WLAN节点通过WLAN接口与远端终端连接。WLAN例如可以采用WiFi连接方式。中继终端和WLAN节点之间可以通过以下方式交互：Uu接口、PC5接口或xUu接口。
请参考图10，图10为图9中涉及的SL和WLAN互操作场景的用户面协议栈结构示意图。
SL与WLAN互操作，则意味着在现有的SL架构中，有一部分数据流要分流到WLAN进行传输，并且进行统一的管理和管控。上述三种类型的承载分别为：
SL承载：完全通过PC5接口及资源进行传输的承载；
SL和WLAN分流承载：通过PC5接口及资源和WLAN接口及资源进 行传输的承载；
WLAN承载：完全通过WLAN接口及资源进行传输的承载。
本申请实施例中，可选的，上述三种承载方式，即可以包括业务数据的承载，也可以包括信令的承载。
从图10中可以看出：
可选的，远端终端均包括：第一协议栈，所述第一协议栈用于承载中继终端与远端终端之间的PC5接口和WLAN接口，所述第一协议栈包括第一PDCP实体，与所述第一PDCP实体逻辑连接的第一RLC实体、与所述第一RLC实体逻辑连接的MAC实体、与所述MAC实体逻辑连接的PHY实体(图未示出)、与所述第一PDCP实体逻辑连接的适配实体(SLWAAP)、与所述适配实体逻辑连接的WLAN实体和与所述WLAN实体逻辑连接的PHY实体(图未示出)。其中，在业务数据传输过程中，由第一PDCP实体进行重排序和复制分发操作。
上述通过SL和WLAN分流承载完成业务数据的发送和/或接收包括：远端终端通过所述第一协议栈进行业务数据的发送和/或接收。
本申请实施例中，可选的，中远端终端还包括：第四协议栈，所述第四协议栈用于承载中继终端与远端终端之间的PC5接口，所述第四协议栈包括：第二PDCP实体，与所述第二PDCP实体逻辑连接的第二RLC实体、与所述第二RLC实体逻辑连接的MAC实体，与所述MAC实体逻辑连接的PHY实体(图未示出)。本申请实施例中，第一协议栈和第四协议栈共用一个MAC实体。
上述完全通过SL承载完成业务数据的发送和/或接收包括：远端终端通过所述第四协议栈进行业务数据的发送和/或接收。
本申请实施例中，可选的，远端终端还可以包括：第五协议栈，所述第五协议栈用于承载中继终端与远端终端之间的WLAN接口，所述第五协议栈包括：WLAN实体(图未示出)以及与所述WLAN实体逻辑连接的PHY实体(图未示出)。
上述完全通过WLAN承载完成业务数据的发送和/或接收包括：远端终端通过所述第五协议栈进行业务数据的发送和/或接收。
本申请实施例中，可选的，中继终端包括：第三协议栈，所述第三协议栈用于承载中继终端与远端终端之间的PC5接口和WLAN接口，所述第三协议栈包括第一PDCP实体，与所述第一PDCP实体逻辑连接的第一RLC实体、与所述第一RLC实体逻辑连接的MAC实体、与所述MAC实体逻辑连接的PHY实体(图未示出)、与所述第一PDCP实体逻辑连接的适配实体(SLWAAP)。
WLAN节点包括第十协议栈，第十协议栈用于在SL和WLAN分流承载中承载与远端终端之间的WLAN接口，所述第十协议栈包括与中继终端中的适配实体逻辑连接的WLAN实体，与所述WLAN实体逻辑连接的PHY实体(图未示出)。
可选的，中继终端还第四协议栈，所述第四协议栈用于承载与远端终端之间的PC5接口，所述第四协议栈包括第二PDCP实体，与所述第二PDCP实体逻辑连接的第二RLC实体、与所述第二RLC实体逻辑连接的MAC实体以及与所述MAC实体逻辑连接的PHY实体(图未示出)。本申请实施例中，第一协议栈和第四协议栈可以共用MAC实体。
本申请实施例中，可选的，若通信设备为远端终端，上述业务数据的传输方法还包括：接收所述基站和/或所述中继终端发送的所述WLAN测量配置信息。
本申请实施例中，可选的，若通信设备为中继终端，上述业务数据的传输方法还包括：
向所述中继终端发送的WLAN测量配置信息；
或者，接收基站发送的WLAN测量配置信息并转发给远端终端。
本申请实施例中，可选的，若通信设备为基站，上述业务数据的传输方法还包括：
向远端终端发送的WLAN测量配置信息；
或者，通过中继终端向远端终端发送WLAN测量配置信息。
可选的，所述WLAN测量配置信息包括以下至少一项：
WLAN测量配置参数；
WLAN测量上报参数。
可选的，所述WLAN测量配置参数包括以下至少一项：
1)WLAN频段指示列表(bandIndicatorListWLAN)：包括WLAN频段列表。值band2dot4表示2.4GHz频段，值band5表示5GHz频段，值band60表示60GHz频段。
2)WLAN载波信息列表(carrierInfoListWLAN)：包含测量对象的WLAN载波信息列表；
3)需要添加到测量配置中的WLAN标识符列表(wlan-ToAddModList)；
4)需要从测量配置中删除的WLAN标识符列表(wlan-ToRemoveList)；
5)测量报告中是否包括WLAN可接入容量(availableAdmissionCapacityRequestWLAN)；值true表示UE应在测量报告中包括WLAN可用的接入容量(如果可用)；
6)测量报告中是否包括WLAN回程上行和/或下行链路带宽；backhaulUL-BandwidthRequestWLAN、backhaulDL-BandwidthRequestWLAN；值true表示UE应在测量报告中包括WLAN回程上行和/或下行链路带宽(如果可用)；
7)测量报告中是否包括WLAN频段(bandRequestWLAN)；值true表示UE在测量报告中应包括WLAN频段；
8)测量报告中是否包括WLAN载波信息(carrierInfoRequestWLAN)；值true表示UE应在测量报告中包括WLAN载波信息(如果可用)；
9)测量报告中是否包括WLAN信道利用率(channelUtilizationRequest-WLAN)；值true表示UE应在测量报告中包括WLAN信道利用率(如果可用)；
10)触发WLAN测量的事件ID(eventId)；要包含在测量报告中的最大小区个数(不包括服务小区)。如果目的为ReportStrongTestCellsForSON设置为仅值1适用。对于跨RAT WLAN，它是测量报告中要包含的WLAN的最大数量；
11)测量报告中的小区最大个数(maxReportCells)；
12)WLAN接收信号强度指示(received signal strength indication，RSSI)测量报告配置(measRSSI-ReportConfigNR)；如果该字段存在，则UE应执行 RSSI(Received Signal Strength Indication，接收信号强度指示)和信道占用的测量报告；
13)上报满足触发互操作请求的任何WLAN接入点(reportAnyWLAN)；表示UE上报满足触发要求的任何WLAN接入点；
14)WLAN载波信息(WLAN-CarrierInfo)；
15)WLAN信道数量(channelNumbers)；
16)WLAN的国家或地区代码(countryCode)；
17)WLAN的操作级别(operatingClass)；
18)WLAN的名称(WLAN-Name)；如果配置，UE仅根据识别的名称执行WLAN测量。对于每个名称，它指的是协议中定义的服务集标识符(SSID)；
19)触发WLAN测量的事件。
如：
Event W1：WLAN变得比阈值更好；
Event W2：WLAN移动集内的所有WLAN变得比阈值1差，并且WLAN移动集外部的WLAN变得比阈值2更好；
Event W3：WLAN移动集内的所有WLAN变得比阈值更差。
可选的，所述WLAN测量上报参数包括以下至少一项：
1)WLAN可接入容量(availableAdmissionCapacityWLAN)；
2)WLAN回程下行链路带宽(backhaulDL-BandwidthWLAN)；WLAN回程可用下行带宽，等于下行速度乘以Wi-Fi联盟热点2.0定义的下行负载；
3)WLAN回程上行链路带宽(backhaulUL-BandwidthWLAN WLAN)；WLAN回程可用上行带宽，等于上行速度乘以Wi-Fi联盟热点2.0定义的上行负载；
4)WLAN载波信息(carrierInfoWLAN)；
5)WLAN信道占用信息(channelOccupancy)；指示当RSSI高于配置的ChannelOccupmentNCythreshold时的样本百分比；
6)WLAN信道利用率(channelUtilizationWLAN)；
7)用于指示所述远端终端是否连接到测量结果适用的WLAN的指示信 息(connectedWLAN)；
8)WLAN测量结果列表(measResultListWLAN)；WLAN测量标识的WLAN移动性集和已连接WLAN(如果有)之外报告的最佳WLAN的最大数量的测量结果列表；
9)WLAN RSSI测量结果(rssiWLAN)；以dBm为单位测量WLAN RSSI结果；
10)与WLAN关联的站点总数(stationCountWLAN)；指示协议定义的当前与此WLAN关联的站点总数；
11)WLAN标识符(wlan-Identifiers)；表示用于识别测量结果适用的WLAN的WLAN参数；
12)WLAN往返事件RTT信息。
可选的，WLAN往返事件RTT信息包括以下至少一项：
rttValue：此字段指定目标设备和WLAN接入点之间的往返时间(RTT)测量值，单位由字段rttUnits指定；
rttUnits：此字段指定字段rttValue和rttAccuracy的单位。可用单位为1000ns、100ns、10ns、1ns和0.1ns；
rttAccuracy：此字段提供所提供的rttValue的估计精度，用字段rttUnits给定的单位表示。
本申请的上述各实施例中，以5G系统举例，但上述业务数据的传输方法可以扩展到其它通信系统。
本申请的上述各实施例中，WLAN可以采用Wifi接口，也可以采用例如其它蓝牙接口等。
需要说明的是，本申请实施例提供的业务数据的传输方法，执行主体可以为业务数据传输装置，或者，该业务数据传输装置中的用于执行业务数据传输方法的控制模块。本申请实施例中以业务数据传输装置执行业务数据传输方法为例，说明本申请实施例提供的业务数据传输方法的装置。
请参考图11，本申请实施例提供一种业务数据传输装置110，包括：
传输模块111，用于根据SL和无线局域网WLAN互操作配置信息，进行业务数据的发送和/或接收。
可选的，所述SL和WLAN互操作配置信息包括基站配置的SL和WLAN互操作配置信息和中继终端配置的SL和WLAN互操作配置信息中的至少一项。
可选的，基站配置的SL和WLAN互操作配置信息包括以下至少一项：
支持SL和WLAN互操作；
能够进行WLAN传输的业务特征；
能够进行WLAN传输的业务服务质量QoS流信息；
能够进行WLAN传输的业务数据无线承载DRB信息；
能够进行WLAN传输的业务对应的协议栈层的配置；
能够进行WLAN分流或复制分发传输的业务特征；
能够进行WLAN分流或复制分发传输的业务QoS流信息；
能够进行WLAN分流或复制分发传输的业务DRB信息；
能够进行WLAN分流或复制分发传输的业务对应的协议栈层的配置；
进行SL传输的业务特征；
进行SL传输的业务QoS流信息；
进行SL传输的业务DRB信息；
进行SL传输的业务对应的协议栈层的配置；
WLAN传输数据的接口或端口信息。
可选的，中继终端配置的SL和WLAN互操作配置信息包括以下至少一项：
WLAN DRB的配置信息；
映射到WLAN DRB的QoS流的配置信息；
WLAN分流或复制分发DRB的配置信息；
映射到WLAN分流DRB的QoS流的配置信息；
WLAN接口或端口配置信息；
SL DRB的配置信息；
映射到SL DRB的QoS流的配置信息；
关于SL和WLAN互操作涉及的WLAN MAC地址信息。
可选的，所述业务数据传输装置为中继终端，所述业务数据传输装置还 包括以下至少一项：
第一发送模块，用于向远端终端发送SL和WLAN互操作配置信息；
第一接收模块，用于接收基站发送的SL和WLAN互操作配置信息并转发给远端终端。
可选的，所述业务数据传输装置为远端终端，所述业务数据传输装置还包括：
第二接收模块，用于接收基站和/或中继终端发送的SL和WLAN互操作配置信息。
可选的，所述业务数据传输装置为基站，所述业务数据传输装置还包括：
第二发送模块，用于向中继终端和/或远端终端发送SL和WLAN互操作配置信息。
可选的，所述传输模块执行以下一项：
完全通过SL承载完成业务数据的发送和/或接收；
通过SL和WLAN分流承载完成业务数据的发送和/或接收；
完全通过WLAN承载完成业务数据的发送和/或接收。
可选的，所述业务数据传输装置为终端，所述终端包括第一协议栈，所述第一协议栈用于承载中继终端与远端终端之间的PC5接口和WLAN接口，所述第一协议栈包括第一PDCP实体，与所述第一PDCP实体逻辑连接的第一RLC实体、与所述第一RLC实体逻辑连接的MAC实体、与所述MAC实体逻辑连接的PHY实体、与所述第一PDCP实体逻辑连接的适配实体、与所述适配实体逻辑连接的WLAN实体以及与所述WLAN实体逻辑连接的PHY实体。
可选的，所述传输模块用于通过所述第一协议栈进行业务数据的发送和/或接收。
可选的，所述业务数据传输装置为基站，包括第二协议栈，所述第二协议栈包括第一PDCP实体，与所述第一PDCP实体逻辑连接的第一RLC实体、与所述第一RLC实体逻辑连接的MAC实体、与所述MAC实体逻辑连接的PHY实体、与所述PDCP实体逻辑连接的第二RLC实体，与所述第二RLC实体逻辑连接的MAC实体以及与所述MAC实体逻辑连接的PHY实 体。
可选的，所述传输模块用于通过所述第二协议栈与远端终端之间进行业务数据的发送和/或接收。
可选的，所述业务数据传输装置为中继终端，包括第三协议栈，所述第三协议栈用于承载与远端终端之间的PC5接口和WLAN接口，所述第三协议栈包括第一PDCP实体，与所述第一PDCP实体逻辑连接的第一RLC实体、与所述第一RLC逻辑连接的MAC实体、与所述MAC实体逻辑连接的PHY实体、与所述第一PDCP实体逻辑连接的适配实体，所述适配实体与WLAN节点的WLAN实体逻辑连接。
可选的，所述传输模块用于通过所述第二协议栈与远程终端之间进行业务数据的发送和/或接收。
本申请实施例中，根据SL和WLAN互操作配置信息，能够使副链路中的中继终端和远端终端更好的利用非授权频谱WLAN与SL进行互操作传输操作，从而提升用户的业务速率，保障UE业务的QoS，在提升用户体验的同时保障了系统效率和网络频谱的利用率。
本申请实施例中的业务数据传输装置可以是装置，也可以是终端中的部件、集成电路、或芯片。该装置可以是移动终端，也可以为非移动终端。示例性的，移动终端可以包括但不限于上述所列举的终端11的类型，非移动终端可以为服务器、网络附属存储器(Network Attached Storage，NAS)、个人计算机(personal computer，PC)、电视机(television，TV)、柜员机或者自助机等，本申请实施例不作具体限定。
本申请实施例中的业务数据传输装置可以为具有操作系统的装置。该操作系统可以为安卓(Android)操作系统，可以为ios操作系统，还可以为其他可能的操作系统，本申请实施例不作具体限定。
如图12所示，本申请实施例还提供一种通信设备120，包括处理器121，存储器122，存储在存储器122上并可在所述处理器121上运行的程序或指令，本申请实施例中，所述通信设备120可以为终端，该程序或指令被处理器121执行时实现上述应用于终端的业务数据传输方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。本申请实施例中，所 述通信设备120也可以为基站，该程序或指令被处理器121执行时实现上述应用于基站的业务数据传输方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
图13为实现本申请实施例的一种终端的硬件结构示意图。该终端130包括但不限于：射频单元131、网络模块132、音频输出单元133、输入单元134、传感器135、显示单元136、用户输入单元137、接口单元138、存储器139、以及处理器1310等部件。
本领域技术人员可以理解，终端130还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器1310逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图13中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元134可以包括图形处理器(Graphics Processing Unit，GPU)1341和麦克风1342，图形处理器1341对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元136可包括显示面板1361，可以采用液晶显示器、有机发光二极管等形式来配置显示面板1361。用户输入单元137包括触控面板1371以及其他输入设备1372。触控面板1371，也称为触摸屏。触控面板1371可包括触摸检测装置和触摸控制器两个部分。其他输入设备1372可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元131将来自网络侧设备的下行数据接收后，给处理器1310处理；另外，将上行的数据发送给网络侧设备。通常，射频单元131包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放大器、双工器等。
存储器139可用于存储软件程序或指令以及各种数据。存储器139可主要包括存储程序或指令区和存储数据区，其中，存储程序或指令区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器139可以包括高速随机存取存储器，还可以包 括非易失性存储器，其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。
处理器1310可包括一个或多个处理单元；可选的，处理器1310可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序或指令等，调制解调处理器主要处理无线通信，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器1310中。
其中，处理器1310，用于根据SL和无线局域网WLAN互操作配置信息，进行业务数据的发送和/或接收。
本申请实施例中，根据SL和WLAN互操作配置信息，能够使副链路中的中继终端和远端终端更好的利用非授权频谱WLAN与SL进行互操作传输操作，从而提升用户的业务速率，保障UE业务的QoS，在提升用户体验的同时保障了系统效率和网络频谱的利用率。
可选的，所述SL和WLAN互操作配置信息包括基站配置的SL和WLAN互操作配置信息和中继终端配置的SL和WLAN互操作配置信息中的至少一项。
可选的，基站配置的SL和WLAN互操作配置信息包括以下至少一项：
支持SL和WLAN互操作；
能够进行WLAN传输的业务特征；
能够进行WLAN传输的业务服务质量QoS流信息；
能够进行WLAN传输的业务数据无线承载DRB信息；
能够进行WLAN传输的业务对应的协议栈层的配置；
能够进行WLAN分流或复制分发传输的业务特征；
能够进行WLAN分流或复制分发传输的业务QoS流信息；
能够进行WLAN分流或复制分发传输的业务DRB信息；
能够进行WLAN分流或复制分发传输的业务对应的协议栈层的配置；
进行SL传输的业务特征；
进行SL传输的业务QoS流信息；
进行SL传输的业务DRB信息；
进行SL传输的业务对应的协议栈层的配置；
WLAN传输数据的接口或端口信息。
可选的，中继终端配置的SL和WLAN互操作配置信息包括以下至少一项：
WLAN DRB的配置信息；
映射到WLAN DRB的QoS流的配置信息；
WLAN分流或复制分发DRB的配置信息；
映射到WLAN分流DRB的QoS流的配置信息；
WLAN接口或端口配置信息；
SL DRB的配置信息；
映射到SL DRB的QoS流的配置信息；
关于SL和WLAN互操作涉及的WLAN MAC地址信息。
可选的，所述终端为中继终端，所述射频单元131，用于向远端终端发送SL和WLAN互操作配置信息；或者，接收基站发送的SL和WLAN互操作配置信息并转发给远端终端。
可选的，所述终端为远端终端，所述射频单元131，用于接收基站和/或中继终端发送的SL和WLAN互操作配置信息。
可选的，所述处理器1310用于执行以下一项：
完全通过SL承载完成业务数据的发送和/或接收；
通过SL和WLAN分流承载完成业务数据的发送和/或接收；
完全通过WLAN承载完成业务数据的发送和/或接收。
可选的，所述终端包括第一协议栈，所述第一协议栈用于承载中继终端与远端终端之间的PC5接口和WLAN接口，所述第一协议栈包括第一PDCP实体，与所述第一PDCP实体逻辑连接的第一RLC实体、与所述第一RLC实体逻辑连接的MAC实体、与所述MAC实体逻辑连接的PHY实体、与所述第一PDCP实体逻辑连接的适配实体、与所述适配实体逻辑连接的WLAN实体以及与所述WLAN实体逻辑连接的PHY实体。
可选的，所述处理器1310用于通过所述第一协议栈进行业务数据的发送和/或接收。
可选的，所述终端为中继终端，包括第三协议栈，所述第三协议栈用于承载与远端终端之间的PC5接口和WLAN接口，所述第三协议栈包括第一PDCP实体，与所述第一PDCP实体逻辑连接的第一RLC实体、与所述第一RLC逻辑连接的MAC实体、与所述MAC实体逻辑连接的PHY实体、与所述第一PDCP实体逻辑连接的适配实体，所述适配实体与WLAN节点的WLAN实体逻辑连接。
可选的，所述处理器1310用于通过所述第二协议栈与远程终端之间进行业务数据的发送和/或接收。
本申请实施例还提供了一种基站。如图14所示，该基站140包括：天线141、射频装置142、基带装置143。天线141与射频装置142连接。在上行方向上，射频装置142通过天线141接收信息，将接收的信息发送给基带装置143进行处理。在下行方向上，基带装置143对要发送的信息进行处理，并发送给射频装置142，射频装置142对收到的信息进行处理后经过天线141发送出去。
上述频带处理装置可以位于基带装置143中，以上实施例中网络侧设备执行的方法可以在基带装置143中实现，该基带装置143包括处理器144和存储器145。
基带装置143例如可以包括至少一个基带板，该基带板上设置有多个芯片，如图14所示，其中一个芯片例如为处理器144，与存储器145连接，以调用存储器145中的程序，执行以上方法实施例中所示的网络设备操作。
该基带装置143还可以包括网络接口146，用于与射频装置142交互信息，该接口例如为通用公共无线接口(common public radio interface，CPRI)。
具体地，本发明实施例的网络侧设备还包括：存储在存储器145上并可在处理器144上运行的指令或程序，处理器144调用存储器145中的指令或程序执行图11所示业务数据传输装置为基站时各模块执行的方法，并达到相同的技术效果，为避免重复，故不在此赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程 序或指令，该程序或指令被处理器执行时实现上述业务数据传输方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
其中，所述处理器为上述实施例中所述的终端中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行网络侧设备程序或指令，实现上述业务数据传输方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
本申请实施例另提供了一种程序产品，所述程序产品存储在非易失的存储介质中，所述程序产品被至少一个处理器执行以实现上述业务数据传输方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体 现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (30)

  1. 一种业务数据传输方法，应用于终端，包括：
    根据副链路SL和无线局域网WLAN互操作配置信息，进行业务数据的发送和/或接收。
  2. 如权利要求1所述的方法，其中，所述SL和WLAN互操作配置信息包括基站配置的SL和WLAN互操作配置信息和中继终端配置的SL和WLAN互操作配置信息中的至少一项。
  3. 如权利要求2所述的方法，其中，基站配置的SL和WLAN互操作配置信息包括以下至少一项：
    支持SL和WLAN互操作；
    能够进行WLAN传输的业务特征；
    能够进行WLAN传输的业务服务质量QoS流信息；
    能够进行WLAN传输的业务数据无线承载DRB信息；
    能够进行WLAN传输的业务对应的协议栈层的配置；
    能够进行WLAN分流或复制分发传输的业务特征；
    能够进行WLAN分流或复制分发传输的业务QoS流信息；
    能够进行WLAN分流或复制分发传输的业务DRB信息；
    能够进行WLAN分流或复制分发传输的业务对应的协议栈层的配置；
    进行SL传输的业务特征；
    进行SL传输的业务QoS流信息；
    进行SL传输的业务DRB信息；
    进行SL传输的业务对应的协议栈层的配置；
    WLAN传输数据的接口或端口信息。
  4. 如权利要求2所述的方法，其中，中继终端配置的SL和WLAN互操作配置信息包括以下至少一项：
    WLAN DRB的配置信息；
    映射到WLAN DRB的QoS流的配置信息；
    WLAN分流或复制分发DRB的配置信息；
    映射到WLAN分流DRB的QoS流的配置信息；
    WLAN接口或端口配置信息；
    SL DRB的配置信息；
    映射到SL DRB的QoS流的配置信息；
    关于SL和WLAN互操作涉及的WLAN MAC地址信息。
  5. 如权利要求1至4任一项所述的方法，其中，所述终端为中继终端，根据SL和WLAN互操作配置信息，进行业务数据的发送和/或接收之前还包括以下至少一项：
    向远端终端发送SL和WLAN互操作配置信息；
    接收基站发送的SL和WLAN互操作配置信息并转发给远端终端。
  6. 如权利要求1至4任一项所述的方法，其中，所述终端为远端终端，根据SL和WLAN互操作配置信息，进行业务数据的发送和/或接收之前还包括：
    接收基站和/或中继终端发送的SL和WLAN互操作配置信息。
  7. 如权利要求1所述的方法，其中，根据SL和WLAN互操作配置信息，进行业务数据的发送和/或接收包括以下一项：
    完全通过SL承载完成业务数据的发送和/或接收；
    通过SL和WLAN分流承载完成业务数据的发送和/或接收；
    完全通过WLAN承载完成业务数据的发送和/或接收。
  8. 如权利要求7所述的方法，其中，所述终端包括第一协议栈，所述第一协议栈用于承载中继终端与远端终端之间的PC5接口和WLAN接口，所述第一协议栈包括第一PDCP实体，与所述第一PDCP实体逻辑连接的第一RLC实体、与所述第一RLC实体逻辑连接的MAC实体、与所述MAC实体逻辑连接的PHY实体、与所述第一PDCP实体逻辑连接的适配实体、与所述适配实体逻辑连接的WLAN实体以及与所述WLAN实体逻辑连接的PHY实体。
  9. 如权利要求8所述的方法，其中，所述通过SL和WLAN分流承载完成业务数据的发送和/或接收包括：
    通过所述第一协议栈进行业务数据的发送和/或接收。
  10. 如权利要求7所述的方法，其中，所述终端为中继终端，包括第三协议栈，所述第三协议栈用于承载与远端终端之间的PC5接口和WLAN接口，所述第三协议栈包括第一PDCP实体，与所述第一PDCP实体逻辑连接的第一RLC实体、与所述第一RLC逻辑连接的MAC实体、与所述MAC实体逻辑连接的PHY实体、与所述第一PDCP实体逻辑连接的适配实体，所述适配实体与WLAN节点的WLAN实体逻辑连接。
  11. 如权利要求10所述的方法，其中，所述通过SL和WLAN分流承载完成业务数据的发送和/或接收包括：
    通过所述第三协议栈与远端终端之间进行业务数据的发送和/或接收。
  12. 一种业务数据传输方法，应用于基站，包括：
    根据副链路SL和无线局域网WLAN互操作配置信息，进行业务数据的发送和/或接收。
  13. 如权利要求12所述的方法，其中，所述SL和WLAN互操作配置信息包括以下至少一项：
    支持SL和WLAN互操作；
    能够进行WLAN传输的业务特征；
    能够进行WLAN传输的业务服务质量QoS流信息；
    能够进行WLAN传输的业务数据无线承载DRB信息；
    能够进行WLAN传输的业务对应的协议栈层的配置；
    能够进行WLAN分流或复制分发传输的业务特征；
    能够进行WLAN分流或复制分发传输的业务QoS流信息；
    能够进行WLAN分流或复制分发传输的业务DRB信息；
    能够进行WLAN分流或复制分发传输的业务对应的协议栈层的配置；
    进行SL传输的业务特征；
    进行SL传输的业务QoS流信息；
    进行SL传输的业务DRB信息；
    进行SL传输的业务对应的协议栈层的配置；
    WLAN传输数据的接口或端口信息。
  14. 如权利要求12所述的方法，其中，根据SL和WLAN互操作配置信 息，进行业务数据的发送和/或接收之前还包括：
    向中继终端和/或远端终端发送SL和WLAN互操作配置信息。
  15. 如权利要求12所述的方法，其中，根据SL和WLAN互操作配置信息，进行业务数据的发送和/或接收包括以下一项：
    完全通过SL承载完成业务数据的发送和/或接收；
    通过SL和WLAN分流承载完成业务数据的发送和/或接收；
    完全通过WLAN承载完成业务数据的发送和/或接收。
  16. 如权利要求15所述的方法，其中，所述基站包括第二协议栈，所述第二协议栈包括第一PDCP实体，与所述第一PDCP实体逻辑连接的第一RLC实体、与所述第一RLC实体逻辑连接的MAC实体、与所述MAC实体逻辑连接的PHY实体、与所述PDCP实体逻辑连接的第二RLC实体，与所述第二RLC实体逻辑连接的MAC实体以及与所述MAC实体逻辑连接的PHY实体。
  17. 如权利要求16所述的方法，其中，所述通过SL和WLAN分流承载完成业务数据的发送和/或接收包括：
    通过所述第二协议栈与远端终端之间进行业务数据的发送和/或接收。
  18. 一种业务数据传输装置，包括：
    传输模块，用于根据SL和WLAN互操作配置信息，进行业务数据的发送和/或接收。
  19. 如权利要求18所述的装置，其中，所述传输模块用于执行以下一项：
    完全通过SL承载完成业务数据的发送和/或接收；
    通过SL和WLAN分流承载完成业务数据的发送和/或接收；
    完全通过WLAN承载完成业务数据的发送和/或接收。
  20. 如权利要求19所述的装置，其中，所述业务数据传输装置为终端，包括第一协议栈，所述第一协议栈用于承载中继终端与远端终端之间的PC5接口和WLAN接口，所述第一协议栈包括第一PDCP实体，与所述第一PDCP实体逻辑连接的第一RLC实体、与所述第一RLC实体逻辑连接的MAC实体、与所述MAC实体逻辑连接的PHY实体、与所述第一PDCP实体逻辑连接的适配实体、与所述适配实体逻辑连接的WLAN实体以及与所述WLAN 实体逻辑连接的PHY实体。
  21. 如权利要求20所述的装置，其中，所述传输模块，用于通过所述第一协议栈进行业务数据的发送和/或接收。
  22. 如权利要求19所述的装置，其中，所述业务数据传输装置为中继终端，包括第三协议栈，所述第三协议栈用于承载与远端终端之间的PC5接口和WLAN接口，所述第三协议栈包括第一PDCP实体，与所述第一PDCP实体逻辑连接的第一RLC实体、与所述第一RLC逻辑连接的MAC实体、与所述MAC实体逻辑连接的PHY实体、与所述第一PDCP实体逻辑连接的适配实体，所述适配实体与WLAN节点的WLAN实体逻辑连接。
  23. 如权利要求22所述的装置，其中，所述传输模块，用于通过所述第三协议栈与远端终端之间进行业务数据的发送和/或接收。
  24. 如权利要求19所述的装置，其中，所述业务数据传输装置为基站，包括第二协议栈，所述第二协议栈包括第一PDCP实体，与所述第一PDCP实体逻辑连接的第一RLC实体、与所述第一RLC实体逻辑连接的MAC实体、与所述MAC实体逻辑连接的PHY实体、与所述PDCP实体逻辑连接的第二RLC实体，与所述第二RLC实体逻辑连接的MAC实体以及与所述MAC实体逻辑连接的PHY实体。
  25. 如权利要求24所述的装置，其中，所述传输模块，用于通过所述第二协议栈与远端终端之间进行业务数据的发送和/或接收。
  26. 一种通信设备，包括处理器，存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至11任一项所述的业务数据传输方法的步骤；或者，所述程序或指令被所述处理器执行时实现如权利要求12至17任一项所述的业务数据传输方法的步骤。
  27. 一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如权利要求1至11任一项所述的业务数据传输方法；或者，所述程序或指令被处理器执行时实现如权利要求12至17任一项所述的业务数据传输方法。
  28. 一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处 理器耦合，所述处理器用于运行程序或指令，实现如权利要求1至17任一项所述的业务数据传输方法的步骤。
  29. 一种程序产品，所述程序产品被至少一个处理器执行以实现如权利要求1至17任一项所述的业务数据传输方法的步骤。
  30. 一种通信设备，被配置成用于执行如权利要求1至17任一项所述的业务数据传输方法的步骤。
PCT/CN2021/119043 2020-09-21 2021-09-17 业务数据传输方法及装置、终端和基站 WO2022057892A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP21868714.3A EP4216658A4 (en) 2020-09-21 2021-09-17 SERVICE DATA TRANSMISSION METHOD AND APPARATUS, TERMINAL AND BASE STATION
US18/119,680 US20230217464A1 (en) 2020-09-21 2023-03-09 Service data transmission method and apparatus, terminal, and base station

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010997371.7 2020-09-21
CN202010997371.7A CN114258156B (zh) 2020-09-21 2020-09-21 业务数据传输方法及装置、终端和基站

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/119,680 Continuation US20230217464A1 (en) 2020-09-21 2023-03-09 Service data transmission method and apparatus, terminal, and base station

Publications (1)

Publication Number Publication Date
WO2022057892A1 true WO2022057892A1 (zh) 2022-03-24

Family

ID=80775928

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/119043 WO2022057892A1 (zh) 2020-09-21 2021-09-17 业务数据传输方法及装置、终端和基站

Country Status (4)

Country Link
US (1) US20230217464A1 (zh)
EP (1) EP4216658A4 (zh)
CN (1) CN114258156B (zh)
WO (1) WO2022057892A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023207900A1 (zh) * 2022-04-26 2023-11-02 维沃移动通信有限公司 终端的发现方法、装置、终端及网络侧设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107295669A (zh) * 2016-04-11 2017-10-24 中兴通讯股份有限公司 通信间隔的配置方法及装置
CN108307472A (zh) * 2016-08-12 2018-07-20 中兴通讯股份有限公司 设备直通系统的通信方法及装置、通信系统
CN108781452A (zh) * 2016-04-01 2018-11-09 三星电子株式会社 无线通信系统中的用于无线通信的方法和设备
US20200029353A1 (en) * 2016-09-30 2020-01-23 Huawei Technologies Co., Ltd. Resource Request Method and System, and Device

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107517489A (zh) * 2016-06-17 2017-12-26 中兴通讯股份有限公司 实现业务连续性的通信方法及装置
KR20210126691A (ko) * 2019-02-13 2021-10-20 콘비다 와이어리스, 엘엘씨 5g에서의 접속 지향 차량-대-x(vtx) 통신을 위한 장치, 시스템, 방법 및 컴퓨터 판독가능 매체

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108781452A (zh) * 2016-04-01 2018-11-09 三星电子株式会社 无线通信系统中的用于无线通信的方法和设备
CN107295669A (zh) * 2016-04-11 2017-10-24 中兴通讯股份有限公司 通信间隔的配置方法及装置
CN108307472A (zh) * 2016-08-12 2018-07-20 中兴通讯股份有限公司 设备直通系统的通信方法及装置、通信系统
US20200029353A1 (en) * 2016-09-30 2020-01-23 Huawei Technologies Co., Ltd. Resource Request Method and System, and Device

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI, HISILICON: "Corrections on V2X functionalities in TS 36.331", 3GPP DRAFT; R2-2006430, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20200601 - 20200612, 25 June 2020 (2020-06-25), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051906279 *
See also references of EP4216658A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023207900A1 (zh) * 2022-04-26 2023-11-02 维沃移动通信有限公司 终端的发现方法、装置、终端及网络侧设备

Also Published As

Publication number Publication date
CN114258156A (zh) 2022-03-29
EP4216658A4 (en) 2024-03-13
EP4216658A1 (en) 2023-07-26
CN114258156B (zh) 2024-04-02
US20230217464A1 (en) 2023-07-06

Similar Documents

Publication Publication Date Title
US11438941B2 (en) Communication method and communications apparatus
US9635530B2 (en) User equipment (UE) supporting packet-switched emergency calls over IP multimedia subsystem (IMS)
US20230144480A1 (en) Method for configuring sidelink relay architecture and terminal
CN110602654A (zh) 使用mbms中继装置管理多媒体广播多播服务
WO2017215275A1 (zh) 实现业务连续性的通信方法及装置
WO2014019510A1 (zh) 用户设备到用户设备的通信方法及设备
CN113905397B (zh) 中继确定方法、配置方法、装置、终端及网络侧设备
WO2019214733A1 (zh) 一种通信方法及装置
JP2018515967A (ja) パケットデータネットワーク接続のオフロード用のアテンション（ａｔ）コマンド
US20230217464A1 (en) Service data transmission method and apparatus, terminal, and base station
US20230300695A1 (en) Sidelink transmission processing method and apparatus, terminal, and network device
WO2017215469A1 (en) System and method for paging in a communications system
WO2023001172A1 (zh) 推荐比特率确定方法、装置及相关设备
WO2022100667A1 (zh) 基于侧链路中继的切换方法、装置、设备及存储介质
WO2022206543A1 (zh) 中继处理方法及装置、终端及可读存储介质
WO2022156751A1 (zh) 路径切换的方法、终端及网络侧设备
WO2022057916A1 (zh) Sl和wlan互操作方法、装置及通信设备
WO2021078170A1 (zh) 一种通信方法及装置
WO2023220954A1 (zh) 通信方法、终端、通信设备以及网络设备
WO2024120351A1 (zh) 消息传输方法、装置、ue及存储介质
WO2024020862A1 (zh) 侧行链路的切换方法、装置、设备、系统及介质
WO2024067475A1 (zh) 数据传输方法和通信装置
WO2023160706A1 (zh) 一种通信方法及装置
WO2023116740A1 (zh) 通信方法和通信装置
WO2023134566A1 (zh) 一种通信方法、装置及系统

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: 21868714

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021868714

Country of ref document: EP

Effective date: 20230421