CN111866796A - Method and apparatus for acquiring radio bearer configuration - Google Patents

Method and apparatus for acquiring radio bearer configuration Download PDF

Info

Publication number
CN111866796A
CN111866796A CN201910365478.7A CN201910365478A CN111866796A CN 111866796 A CN111866796 A CN 111866796A CN 201910365478 A CN201910365478 A CN 201910365478A CN 111866796 A CN111866796 A CN 111866796A
Authority
CN
China
Prior art keywords
terminal device
radio bearer
drb
qos
configuration information
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.)
Granted
Application number
CN201910365478.7A
Other languages
Chinese (zh)
Other versions
CN111866796B (en
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.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201910365478.7A priority Critical patent/CN111866796B/en
Priority to PCT/CN2020/087703 priority patent/WO2020221281A1/en
Publication of CN111866796A publication Critical patent/CN111866796A/en
Application granted granted Critical
Publication of CN111866796B publication Critical patent/CN111866796B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

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
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition

Abstract

The application provides a method and a device for acquiring radio bearer configuration. The first terminal device obtains the radio bearer configuration information, the radio bearer configuration information comprises the index corresponding to the first SL DRB and the first parameter, the index corresponding to the first SL DRB has an association relation with the first parameter, and performs side chain transmission based on the radio bearer configuration information, without directly obtaining all configuration of the SL DRBs, the configuration of the SL DRBs predefined by the corresponding standards can be obtained through the index corresponding to the SL DRBs, which is beneficial to saving signaling overhead.

Description

Method and apparatus for acquiring radio bearer configuration
Technical Field
The present application relates to the field of communications, and more particularly, to a method and apparatus for obtaining a radio bearer configuration.
Background
The third Generation Partnership Project (3 GPP) international organization for standardization started to conduct a research on vehicle networking (V2X) from Long Term Evolution (LTE) R14, and proposed a V2X communication architecture. The V2X communication architecture includes two communication interfaces, a PC5 interface and a Uu interface. The V2X PC5 interface is a direct communication interface between V2X UEs, the direct communication link between V2X UEs is also defined as sidelink or Sidechain (SL); the V2X Uu interface communication is a communication mode that a transmitting party V2X UE transmits V2X data to a base station through a Uu interface, the data are transmitted to a V2X application server through the base station to be processed, then the data are transmitted to the base station by the V2X application server, and the data are transmitted to a receiving party V2X UE through the base station; in the V2X Uu interface communication mode, the base station that forwards the uplink data from the UE to the server and the base station that forwards the downlink data sent by the server to the UE at the receiving party may be the same base station, or may be different base stations, and may specifically be determined by the application server.
The configuration of SL RBs in LTE V2X is relatively simple, such as fixed PDCP SN length, RLC UM mode, etc. Therefore, communication on the lte pc5 does not require the originating Tx UE and the terminating Rx UE to interact with configuration information of the SL RB, and the terminating UE transmits data to a corresponding upper layer of the protocol stack for processing according to the source layer 2 identifier (source L2 ID), the destination layer 2 identifier (destination L2 ID), and the logical channel identifier (LCH ID).
LTE V2X only supports UEs using one resource allocation pattern at the same time. NR V2X supports two resource configuration modes: mode (mode)1 and mode 2. NR V2X has agreed to support mode concurrency, i.e. one UE can be in both modes at the same time. Currently, there is no clear definition in NR V2X about how to obtain SL DRB configuration corresponding to different modes. In the SL RB configuration in the prior art, all information about the SL RB is delivered to the UE, and the SL DRB configuration may include many parameters, which may bring a large signaling overhead and is not favorable for saving the signaling overhead.
Disclosure of Invention
In view of this, the present application provides a method and an apparatus for acquiring a radio bearer configuration, which can save signaling overhead.
In a first aspect, a method for obtaining a radio bearer configuration is provided, including: a first terminal device obtains radio bearer configuration information of a side chain, wherein the radio bearer configuration information includes an index corresponding to a first side chain data radio bearer (SL DRB) and a first parameter, the index corresponding to the first SL DRB and the first parameter have an association relationship, the first parameter includes a first quality of service (QoS) parameter and/or a resource configuration mode of the first terminal device, and the side chain is a radio link between the first terminal device and a second terminal device; performing a side chain transmission based on the radio bearer configuration information. In this way, the first terminal device can obtain the configuration associated with the first SL DRB predefined by the standard through the index corresponding to the SL DRB, so that the signaling overhead can be saved.
The resource configuration mode includes mode 1 and mode 2.
In one possible implementation, the first terminal device is in a radio resource control, RRC, connected state, and the method further includes: the first terminal device sends a first RRC message to a network device, where the first RRC message includes the first QoS parameter and first indication information, and the first indication information is used to indicate that a resource configuration mode corresponding to the first QoS parameter is mode 2. Therefore, the first terminal device may inform the network device of the resource configuration mode through an RRC message, so that the network device configures the SL DRB.
In a possible implementation manner, the obtaining, by the first terminal device, radio bearer configuration information of a side chain includes: the first terminal device receives a second RRC message sent by a network device, where the second RRC message includes the radio bearer configuration information, and the radio bearer configuration information is side chain radio bearer configuration information associated with the mode 2, or the radio bearer configuration information is side chain radio bearer configuration information associated with the mode 1. Therefore, the terminal device can obtain the sidechain radio bearer configuration information configured by the network device and associated with the resource configuration mode.
Optionally, the first RRC message further includes second indication information, where the second indication information is used to indicate that the first QoS parameter is standard predefined or non-standard predefined.
In one possible implementation, the method further includes: and the access stratum AS of the first terminal equipment receives the second indication information from the V2X layer or the APP layer of the first terminal equipment.
Optionally, the first RRC message further includes a preconfigured SL DRB associated with the first QoS parameter, or the first RRC message further includes a SL DRB associated with the first QoS parameter, acquired by the first terminal device by receiving a SIB broadcast message. Therefore, the first terminal device may send the SL DRB acquired by pre-configuration or the SL DRB acquired through the SIB to the network device for the network device to refer to.
Optionally, the first SL DRB includes a logical channel configuration, where the logical channel configuration includes a logical channel index, and the logical channel index is used to obtain a logical channel ID according to a preset rule. This can solve the problem of logical channel ID collision.
In another possible implementation manner, the first terminal device is in a radio resource control RRC idle state or an inactive state, and the obtaining, by the first terminal device, radio bearer configuration information of a side chain includes: the first terminal equipment receives a System Information Block (SIB) broadcast message sent by network equipment, wherein the SIB broadcast message comprises the radio bearer configuration information; or, the first terminal device triggers RRC connection establishment, and acquires the radio bearer configuration information by receiving an RRC response message. Therefore, the first terminal device may acquire the radio bearer configuration information sent by the network device through the SIB broadcast message.
Optionally, the first QoS parameter is standard predefined. For example, the PC5QoS flow identification PFI is standard predefined.
In one possible implementation, the first QoS parameter includes one or more of the following information: the PC5QoS flow identification PFI, the PC5 fifth generation communication system service quality identification PQI, the guarantee flow bit rate GFBR, the maximum flow bit rate MFBR, the minimum demand communication distance, the allocation and reservation priority ARP.
In a second aspect, a method for obtaining a radio bearer configuration is provided, including: the network equipment determines an index and a first parameter corresponding to a first side-link data radio bearer (SL DRB), wherein the index and the first parameter have an association relationship, and the first parameter comprises a first quality of service (QoS) parameter and/or a resource configuration mode of first terminal equipment; the network device sends radio bearer configuration information of a side chain to the first terminal device, where the radio bearer configuration information includes an index corresponding to the first SL DRB and the first parameter, and the side chain is a radio link between the first terminal device and a second terminal device. In this way, the first terminal device can obtain the configuration associated with the first SL DRB predefined by the standard through the index corresponding to the SL DRB, so that the signaling overhead can be saved.
In one possible implementation manner, the sending, by the network device, radio bearer configuration information of a side chain includes: the network device receives a first RRC message sent by a first terminal device, where the first RRC message includes the first QoS parameter and first indication information, and the first indication information is used to indicate that a resource configuration mode corresponding to the first QoS parameter is mode 2; the network device sends a second RRC message to the first terminal device, where the second RRC message includes the radio bearer configuration information, and the radio bearer configuration information is side chain radio bearer configuration information associated with the mode 2, or the side chain radio bearer configuration information is side chain radio bearer configuration information associated with the mode 1. Therefore, the network device may configure, for the first terminal device, the sidechain radio bearer configuration information associated with the resource configuration mode based on the resource configuration mode reported by the first terminal device.
Optionally, the first RRC message further includes second indication information, where the second indication information is used to indicate that the first QoS parameter is standard predefined or non-standard predefined.
Optionally, the first RRC message further includes a preconfigured SL DRB associated with the first QoS parameter, and correspondingly, the network device sends a second RRC message to the first terminal device according to the preconfigured SL DRB; or, the first RRC message further includes a SL DRB associated with the first QoS parameter, acquired by the first terminal device through reception of a SIB broadcast message, and accordingly includes: and the network equipment sends a second RRC message to the first terminal equipment according to the SL DRB acquired by the first terminal equipment through SIB broadcast messages. Therefore, the network device may configure the sidechain radio bearer configuration information for the first terminal device with reference to the SL DRB configuration reported by the first terminal device.
Optionally, the first SL DRB includes a logical channel configuration, where the logical channel configuration includes a logical channel index, and the logical channel index is used for the first terminal device to obtain a logical channel ID according to a preset rule. This can solve the problem of logical channel ID collision.
In a possible implementation manner, the first terminal device is in a radio resource control RRC idle state or an inactive state, and the network device sends radio bearer configuration information of a side chain, including: the network device sends a system information block, SIB, broadcast message, the SIB broadcast message including the radio bearer configuration information. Accordingly, the network device transmits the radio bearer configuration information of the sidechain through the SIB broadcast message.
In a third aspect, a method for obtaining a QoS profile of a data packet is provided, including: an access AS layer of a terminal device acquires a PC5 QoS flow identification PFI and a QoS configuration file, wherein the PFI and the QoS configuration file have a corresponding relation, and the QoS configuration file comprises one or more of the following information: the PC5 fifth generation communication system service quality identification PQI ensures the stream bit rate GFBR, the maximum stream bit rate MFBR, the minimum required communication distance, and the allocation and reservation priority ARP; and the terminal equipment determines a QoS configuration file corresponding to the first data packet based on the corresponding relation. Therefore, the terminal device can obtain the QoS configuration file corresponding to the data packet based on the corresponding relationship.
Optionally, the obtaining, by the AS layer of the terminal device, a corresponding relationship between the PFI and the QoS configuration file includes: the V2X layer or the APP layer of the terminal device obtains the corresponding relationship from a core network, or obtains the pre-configured corresponding relationship; and the access layer AS of the terminal equipment receives the corresponding relation from the V2X layer or the APP layer of the terminal equipment.
In a fourth aspect, a method for obtaining a packet QoS profile is provided, including: an Access Stratum (AS) of a terminal device receives a first data packet from a V2X layer or an APP layer of the terminal device, wherein the first data packet carries a PC5 QoS flow identification (PFI) associated with the first data packet and a QoS configuration file associated with the first data packet; and the terminal equipment acquires the PFI and the QoS configuration file which have corresponding relation from the first data packet. Therefore, by carrying the PC5 QoS flow id PFI and QoS profile in each packet, the terminal device can obtain the QoS profile from the packet.
In a fifth aspect, a communication device is provided, which comprises means for performing the method of the first aspect or any possible implementation manner of the first aspect, or means for performing the method of the third aspect or any possible implementation manner of the third aspect, or means for performing the method of the fourth aspect or any possible implementation manner of the fourth aspect.
In a sixth aspect, there is provided a communication device comprising means for performing the method of the second aspect or any possible implementation manner of the second aspect.
In a seventh aspect, a communication apparatus is provided, which may be the terminal device designed by the method, or a chip disposed in the terminal device. The communication device includes: a processor, coupled to the memory, and configured to execute the instructions in the memory to implement the method performed by the terminal device in the first aspect and any one of the possible implementations of the first aspect, or to implement the method performed by the terminal device in the third aspect and any one of the possible implementations of the third aspect, or to implement the method performed by the terminal device in the fourth aspect and any one of the possible implementations of the fourth aspect. Optionally, the communication device further comprises a memory. Optionally, the communication device further comprises a communication interface, the processor being coupled to the communication interface.
When the communication device is a terminal device, the communication interface may be a transceiver, or an input/output interface.
When the communication means is a chip provided in the terminal device, the communication interface may be an input/output interface.
Alternatively, the transceiver may be a transmit-receive circuit. Alternatively, the input/output interface may be an input/output circuit.
In an eighth aspect, a communication apparatus is provided, which may be a network device designed by the method, or a chip disposed in the network device. The communication device includes: a processor, coupled to the memory, may be configured to execute the instructions in the memory to implement the method performed by the network device in the second aspect and any one of the possible implementations thereof. Optionally, the communication device further comprises a memory. Optionally, the communication device further comprises a communication interface, the processor being coupled to the communication interface.
When the communication device is a network device, the communication interface may be a transceiver, or an input/output interface.
When the communication device is a chip provided in a network device, the communication interface may be an input/output interface.
Alternatively, the transceiver may be a transmit-receive circuit. Alternatively, the input/output interface may be an input/output circuit.
A ninth aspect provides a program for performing the method of any one of the first or third or fourth aspects and possible implementations thereof when executed by a processor.
In a tenth aspect, a program is provided for performing the method of the second aspect and any of its possible embodiments when executed by a processor.
In an eleventh aspect, there is provided a program product comprising: program code for causing a communication device to perform any of the methods of the first or third or fourth aspects and possible embodiments thereof described above, when the program code is run by a communication unit, processing unit or transceiver, processor of a communication apparatus (e.g. a terminal device).
In a twelfth aspect, a program product is provided, the program product comprising: program code which, when executed by a communication unit, processing unit or transceiver, processor of a communication apparatus (e.g. a network device), causes the communication device to perform any of the methods of the second aspect and its possible embodiments described above.
In a thirteenth aspect, there is provided a computer readable storage medium storing a program which, when executed, causes a communication apparatus (e.g. a terminal device) to perform the method of any one of the above first aspect and its possible embodiments; or, the program, when executed, causes a communication apparatus (e.g. a terminal device) to perform the method of any of the third aspect and its possible embodiments described above; alternatively, the program, when executed, causes a communication apparatus (e.g., a terminal device) to perform any of the methods of the fourth aspect and its possible embodiments described above.
In a fourteenth aspect, a computer-readable storage medium is provided, which stores a program that, when executed, causes a communication apparatus (e.g., a network device) to perform any of the methods of the second aspect and its possible embodiments.
In a fifteenth aspect, a communication system for obtaining a radio bearer configuration is provided, comprising: a terminal device for performing any of the methods of the first aspect and its possible embodiments and a network device for performing any of the methods of the second aspect and its possible embodiments.
Optionally, the communication system may further include other devices that interact or communicate with the terminal device and/or the network device.
Drawings
FIG. 1 is an exemplary diagram of a system architecture to which embodiments of the present application may be applied;
fig. 2 is a schematic interaction diagram of a method for obtaining a radio bearer configuration according to an embodiment of the present application;
FIG. 3 is a schematic flow chart diagram of a method of obtaining a profile for a data package according to an embodiment of the present application;
FIG. 4 is a schematic block diagram of a communication device according to an embodiment of the present application;
Fig. 5 is a schematic configuration diagram of a communication apparatus according to an embodiment of the present application;
FIG. 6 is a schematic block diagram of a communication device according to another embodiment of the present application;
fig. 7 is a schematic configuration diagram of a communication apparatus according to another embodiment of the present application.
Detailed Description
The technical solution in the present application will be described below with reference to the accompanying drawings.
In the description of the embodiments of the present application, the meaning of "plurality" or "items" is two or more unless otherwise specified.
The technical scheme of the embodiment of the application can be applied to various communication systems, for example: a global system for mobile communications (GSM) system, a Code Division Multiple Access (CDMA) system, a Wideband Code Division Multiple Access (WCDMA) system, a General Packet Radio Service (GPRS), a long term evolution (long term evolution, LTE) system, a LTE Frequency Division Duplex (FDD) system, a LTE Time Division Duplex (TDD), a Universal Mobile Telecommunications System (UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) communication system, a future fifth generation (5G) or new generation (2X) networking system, a radio frequency network (NR 2) system, and the like. Alternatively, the V2X system may be embodied as any of the following systems: vehicle-to-internet (V2N), vehicle-to-vehicle communication (V2V), vehicle-to-vehicle communication (V2P), and vehicle-to-infrastructure communication (V2I).
One participant of V2N is a terminal device and the other participant is a service entity. V2N is the most widely used form of car networking, and its main function is to connect the vehicle to the cloud server through the mobile network, so as to provide navigation, entertainment, anti-theft functions through the cloud server.
Both participants of V2P are terminal devices. V2V may be used as an inter-vehicle information interaction reminder, the most typical application being for inter-vehicle collision avoidance safety systems.
Both participants of V2P are terminal devices. V2P may be used to provide safety warnings to pedestrians or non-motor vehicles on the road.
One participant in V2I is a terminal device and the other participant is an infrastructure (or infrastructure). V2I may be used for vehicle-to-infrastructure communications, e.g., where the infrastructure may be roads, traffic lights, roadblocks, etc., where road management information such as timing of traffic light signals may be obtained.
In the embodiment of the present application, the transmitting end and the receiving end in V2X may both be D2D devices, and the V2X devices, for example, terminal devices.
A terminal device in this embodiment may refer to a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user equipment. The terminal device may also be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handheld device with a wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted communication apparatus, a vehicle-mounted communication chip, a wearable device, a terminal device in a future 5G network or a terminal device in a future evolved Public Land Mobile Network (PLMN), and the like, which is not limited in this embodiment.
The network device in the embodiment of the present application may be a device for communicating with a terminal device, and the network device may be a Base Transceiver Station (BTS) in a global system for mobile communications (GSM) system or a Code Division Multiple Access (CDMA) system, a base station (NodeB) in a Wideband Code Division Multiple Access (WCDMA) system, an evolved NodeB (eNB) or eNodeB) in an LTE system, a wireless controller in a Cloud Radio Access Network (CRAN) scenario, or a relay station, an access point, a vehicle-mounted device, a wearable device, a network device in a future 5G network, a network device in a future evolved PLMN network, a next generation base station (next generation base station) in a 5G mobile communication system, a gNB), a transmission point, a base station in a future mobile communication system or an access node in a wireless fidelity (Wi-Fi) system, one or a group (including multiple antenna panels) of antenna panels of a base station in a 5G system, a 5G relay node, or also a network node forming a gNB or a transmission point, such as a baseband unit (BBU), or a Distributed Unit (DU), etc. The embodiments of the present application do not limit the specific technologies and the specific device forms adopted by the radio access network device. In some deployments, the gNB may include a Centralized Unit (CU) and a DU. The gNB may also include an Active Antenna Unit (AAU). The CU implements part of the function of the gNB and the DU implements part of the function of the gNB. For example, the CU is responsible for processing non-real-time protocols and services, and implementing functions of a Radio Resource Control (RRC) layer and a Packet Data Convergence Protocol (PDCP) layer. The DU is responsible for processing a physical layer protocol and a real-time service, and implements functions of a Radio Link Control (RLC) layer, a Medium Access Control (MAC) layer, and a Physical (PHY) layer. The AAU implements part of the physical layer processing functions, radio frequency processing and active antenna related functions. Since the information of the RRC layer is finally carried in the information of the PHY layer, under this architecture, higher layer signaling, such as RRC layer signaling, can also be considered to be sent by the DU, or, sent by the DU + AAU. It is to be understood that the network device may be a device comprising one or more of a CU node, a DU node, an AAU node.
In the embodiment of the application, the terminal device or the network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a Central Processing Unit (CPU), a Memory Management Unit (MMU), and a memory (also referred to as a main memory). The operating system may be any one or more computer operating systems that implement business processing through processes (processes), such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a windows operating system. The application layer comprises applications such as a browser, an address list, word processing software, instant messaging software and the like. Furthermore, the embodiment of the present application does not particularly limit the specific structure of the execution main body of the method provided by the embodiment of the present application, as long as the communication can be performed according to the method provided by the embodiment of the present application by running the program recorded with the code of the method provided by the embodiment of the present application, for example, the execution main body of the method provided by the embodiment of the present application may be a terminal device or a network device, or a functional module capable of calling the program and executing the program in the terminal device or the network device.
In addition, various aspects or features of the present application may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques. The term "article of manufacture" as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media. For example, computer-readable media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips, etc.), optical disks (e.g., Compact Disk (CD), Digital Versatile Disk (DVD), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROM), card, stick, or key drive, etc.). In addition, various storage media described herein can represent one or more devices and/or other machine-readable media for storing information. The term "machine-readable medium" can include, without being limited to, wireless channels and various other media capable of storing, containing, and/or carrying instruction(s) and/or data.
The embodiment of the application can be applied to an internet of things system, such as a vehicle to electronic (V2X) system. V2X is a device that provides vehicle information by sensors, vehicle terminals, and the like mounted on a vehicle, and realizes mutual communication between vehicles, between vehicles and people, between vehicles and roadside infrastructure, and between vehicles and a network by various communication techniques.
Fig. 1 is a diagram of an example of a system architecture to which an embodiment of the present application is applied. As shown in fig. 1, the communication system includes: V2X application server (application server), V2X devices (including V2X device 1 and V2X device 2), and network devices. The V2X devices communicate with each other through a PC5 interface. The communication link between V2X devices is defined as a Sidelink (SL). The communication between the V2X device and the V2X application server needs to be forwarded through the network device, specifically: for uplink, the sending end V2X device sends the V2X data to the network device through the Uu interface, and the network device sends the data to the V2X application server for processing, and then the V2X application server sends the data to the receiving end V2X device; for downstream, the V2X application server sends V2X data to the network device, which sends V2X data to the V2X device over the Uu interface. It should be understood that the V2X device in fig. 1 is an internet of things device, such as a UE.
It should be further understood that the flow direction of the arrow in fig. 1 is only exemplarily described with the V2X device 1, and is not limited to the embodiment of the present application, and in fact, the communication between the V2X device 1 and the V2X device 2 may be bidirectional, and the V2X device 2 may also perform uplink communication with the network device, which is not particularly limited.
Some terms or concepts related to the embodiments of the present application will be briefly described below.
The broadcast mode is that a sending end transmits data in a broadcast mode, and all receiving ends can analyze side link control information (SCI) and traffic channel information (SSCH). In the sidelink, the way of ensuring that all terminal devices can analyze the control information is: the control information data is not scrambled or uses a scrambling code known to all terminal devices.
The multicast mode means that the sending end sends data in a multicast mode, and all receiving ends belonging to the multicast group can analyze SCI and SSCH. For example: the SSCH includes a corresponding group destination identifier, and only the terminal device belonging to the multicast group configures the multicast destination identifier, so that SSCH data can be analyzed.
The unicast mode is that one terminal device (such as a vehicle-mounted module) sends data to another terminal device, and the other terminal device does not need or can not parse the data.
The QoS parameters include one or more of the following parameters: PC5 QoS flow identifier (PC5 QoS flow identifier, PFI), PC5 fifth generation communication system quality of service identifier (PC 55G QoS identifier, PQI), Allocation and Reservation Priority (ARP), Guaranteed Flow Bit Rate (GFBR), Maximum Flow Bit Rate (MFBR), minimum required communication distance (range).
PFI is a scalar that uniquely identifies a PC5 QoS flow within a terminal device or within a PC5-S connection of a terminal device. A PFI may correspond to a QoS profile (QoS profile) that contains one or more of PQI, ARP, MFBR, GFBR, and range.
The PQI is also a scalar used to index into the corresponding 5G QoS feature. The PQI is divided into standardized PQI, pre-configured PQI, and dynamically allocated PQI. For a standardized PQI, there is a one-to-one correspondence with a set of standardized 5G QoS characteristic values; for the pre-configured PQI, the corresponding 5G QoS characteristic value is pre-configured on an access network element or a terminal device, and for the dynamically allocated PQI, the corresponding 5G QoS characteristic is sent to the access network element or the terminal device by a core network device through a QoS configuration file (QoS profile).
ARP contains priority level, preemption capability, and preempted capability.
GFBR represents the bit rate that is expected to be provided to a Guaranteed Bit Rate (GBR) QoS flow.
The MFBR limits the bit rate provided to the GBR QoS flow, i.e., the maximum bit rate provided to the GBR QoS flow. E.g., exceeding the bit rate, the packet may be dropped.
Range represents the minimum communication distance required to meet these QoS parameters.
QoS model: in NR V2X systems, to meet higher V2X traffic quality of service requirements, per-flow QoS models based on QoS flows (flows) are proposed. The QoS model is applicable to unicast, multicast and broadcast. At the V2X layer of the terminal device, mapping the V2X data packet at the lower of the application layer to a corresponding PC5 QoSflow according to the configured PC5 QoS rules, and identifying a corresponding PC5 QoS flow by PFI; when the V2X layer of the terminal device delivers the V2X packet to the AS layer, the V2X layer indicates the PC5 QoS stream identifier PFI corresponding to the V2X packet, and the AS layer of the terminal device puts the packet below the V2X layer into a corresponding SL DRB for data transmission according to the mapping from the configured QoS stream to the radio data bearer (SL DRB).
There are two ways for the terminal device to obtain the SL resource, one is that before the terminal device sends the V2X service data, it needs to request the network device for the resource, and the network device allocates the V2X SL resource as needed, and this mode is called mode (mode) 1; the other is that the terminal device can contend for acquisition in the V2X SL resource broadcast by the network device or the V2X SL resource pre-configured by the V2X control function (control function), and this type of mode is called mode 2. Mode 2 may also be understood as the resource that the terminal device transmits each time is selected in sequence from the configured resource pool.
The terminal device of mode 1 can only be in the RRC connected state. The terminal device of mode 2 may be in an RRC connected (connected) state, an RRC idle (idle) state, an RRC inactive (inactive) state, or an out of range (OOC) state. If a terminal currently supports both mode 1 and mode 2, it can only be in RRC connected state.
A method for acquiring a radio bearer configuration according to an embodiment of the present application will be described below with reference to fig. 2 to 7.
Fig. 2 shows a schematic flow diagram of a method 200 for obtaining a radio bearer configuration according to an embodiment of the application. As shown in fig. 2, the illustrated method 200 includes:
s210, a first terminal device obtains radio bearer configuration information of a side chain, where the radio bearer configuration information includes an index corresponding to a first side chain data radio bearer SL DRB and a first parameter, and the index corresponding to the first SL DRB has an association with the first parameter, where the first parameter includes a first quality of service QoS parameter and/or a resource configuration mode of the first terminal device, and the side chain is a radio link between the first terminal device and a second terminal device.
The resource configuration mode may include mode 1 and/or mode 2.
It should be understood that the association relationship between the index corresponding to the first SL DRB and the first parameter may include: the index corresponding to the first SL DRB has an association with one parameter, or has an association with one parameter list (list), or has an association with different parameter types. For example, one QoS parameter may be mapped to one SL DRB, and multiple QoS parameters (e.g., similar QoS parameters) may be mapped to one SL DRB, or one QoS parameter and resource pattern may be mapped to one SL DRB in common, or multiple QoS parameters associated with the same resource configuration pattern may be mapped to one SL DRB in common.
Wherein the configuration of the first SL DRB is standard predefined. The first terminal device may obtain a standard predefined configuration of the corresponding first SL DRB based on the index of the first SL DRB.
The first parameter comprises a first QoS parameter; or, the first parameter includes a resource configuration mode of the first terminal device; or, the first parameter includes a first quality of service QoS parameter and a resource configuration mode of the first terminal device, and the first QoS parameter has an association relationship with the resource configuration mode of the first terminal device.
Optionally, the first QoS parameter comprises one or more of the following information: PC5 QoS flow id PC5 QFI (i.e. PFI), PC5 fifth generation communication system quality of service identity PQI, guaranteed flow bit rate GFBR, maximum flow bit rate MFBR, minimum required communication distance, allocation and reservation priority ARP. For example, the radio bearer configuration information includes an index and a PFI corresponding to the first SL DRB.
In embodiments of the present application, the PFI may be standard predefined or non-standard predefined. Optionally, if the PFI is standard predefined, the QoS profiles corresponding to the same PFI are the same for all terminal devices or all connections of one terminal device (e.g., PC5-S connections); if the PFI is predefined by non-standards, it may also be called dynamically allocated, and for different terminal devices or different connections in the same terminal device, even the QoS profiles corresponding to the same PFI are not necessarily the same (e.g. PFI 1 of UE 1 corresponds to PQI 1, and PFI 1 of UE 2 corresponds to PQI 2). The terminal device may support either standard or non-standard predefined PFIs, depending on the configuration of the core network or the control function (control function) of V2X.
S220, the first terminal device performs side chain transmission based on the radio bearer configuration information.
In this embodiment of the present application, after obtaining the radio bearer configuration information of the side chain, the first terminal device may obtain, through an index corresponding to the first SL DRB, a configuration of the first SL DRB predefined by the standard, and may further obtain a first parameter associated with the first SL DRB, thereby performing side chain transmission. That is to say, the first terminal device can obtain the configuration of the first SL DRB predefined by the standard through the index corresponding to the first SL DRB, and does not need to send the complete configuration of the SL DRB each time, thereby saving the overhead.
How the first terminal device acquires the radio bearer configuration information in different states will be described below.
In a first implementation manner, the first terminal device may obtain the radio bearer configuration information through an RRC message.
The first terminal device is in an RRC connected state, the method 200 further includes: the first terminal device sends a first RRC message to a network device, where the first RRC message includes the first QoS parameter and first indication information, and the first indication information is used to indicate that a resource configuration mode corresponding to the first QoS parameter is mode 2.
When the first terminal device is in the RRC connected state, the first terminal device may be in mode 1, may be in mode 2, or may coexist in both modes.
Optionally, the first RRC message may further include one or more of the following: a communication mode (e.g., unicast, multicast, or broadcast) associated with the SL DRB, source address information for establishing the SL DRB, destination address information for establishing the SL DRB, connection identification information for establishing the SL DRB, logical channel information (indicating an available Logical Channel (LCH) or an unavailable LCH).
Optionally, the source address information for establishing the SL DRB and the destination address information for establishing the SL DRB may be associated with each service or upper layer PC5-S connection, and the UE may internally correspond to a plurality of destination address information; alternatively, it may be associated with the UE, i.e. the source address information and the destination address information are unique for each UE. The connection identification information for establishing the SL DRB refers to information obtained by converting source address information for establishing the SL DRB and destination address information for establishing the SL DRB by the UE, or the connection identification information for establishing the SL DRB is identification information allocated by a PC5-S upper layer (the upper layer refers to a V2X layer or an application layer) connection.
Optionally, the destination address information used for establishing the SL DRB is an opposite UE ID for unicast, a group destination ID (group destination ID) for group identifier conversion for multicast, and a destination ID obtained by service type conversion for broadcast.
In this implementation manner, if the first terminal device is in an RRC connected state, the first terminal device may send a first QoS parameter and first indication information to the network device, where the first indication information is used to indicate that the first QoS parameter is a QoS parameter in mode 2, so that the network device configures corresponding side-chain radio bearer configuration information for the first terminal device.
Illustratively, the first RRC message may be a message for requesting establishment of a sidelink radio bearer, such as an SLDRB establishment request message, a sidelink UE information message, or a UE association information message.
As an optional implementation manner, the network device may send a second RRC message to the first terminal device, where the second RRC message includes the radio bearer configuration information, and the radio bearer configuration information is side chain radio bearer configuration information associated with the mode 2, or the radio bearer configuration information is side chain radio bearer configuration information associated with the mode 1. Accordingly, S210 includes: s211, the first terminal device receives a second RRC message sent by the network device.
For example, if the first indication information is used to indicate that the first QoS parameter is a QoS parameter in mode 2, the network device may configure the first terminal device with the sidechain radio bearer configuration information associated with mode 2, or may configure the first terminal device with the sidechain radio bearer configuration information associated with mode 1.
Alternatively, the first indication information may indicate that the resource configuration mode corresponding to the first QoS parameter is mode 1. Accordingly, the network device may configure the first terminal device with the sidechain radio bearer configuration information associated with mode 1, or may configure the first terminal device with the sidechain radio bearer configuration information associated with mode 2.
For example, the second RRC message may be a SL DRB setup response message, or may also be another RRC message, which is not limited in this embodiment of the present application.
The sidechain radio bearer configuration information associated with mode 2 or mode 1, which is sent by the network device to the first terminal device, may include an index corresponding to the first SL DRB and the first parameter, that is, the first SL DRB is predefined by the standard. Or, in the sidechain radio bearer configuration information associated with mode 2 or mode 1, which is sent by the network device to the first terminal device, the specific configuration of the first SL DRB and the first parameter are included, that is, the first SL DRB is predefined by non-standard, where the specific configuration of the first SL DRB has an association relationship with the first parameter.
Illustratively, the specific configuration of the first SL DRB may include one or more of: identification of the first SL DRB, configuration of each protocol layer of the first SL DRB, communication mode, source address information, destination address information and connection identification information.
Wherein the communication modes include unicast, multicast and broadcast, and the detailed explanation can refer to the foregoing description. The source and destination address information may be associated with each traffic or upper layer PC5-S connection, and the UE may have multiple address information internal to it, or may be associated with the UE, i.e., the source and destination address information may be unique for each UE. The connection identification information is information obtained by converting the source address information and the destination address information by the UE, or the connection identification information for establishing the SL DRB is identification information allocated by the PC5-S upper layer (the upper layer refers to the V2X layer or the application layer) connection.
Optionally, the first SL DRB comprises: identification of the first SL DRB, configuration of each protocol layer of the first SL DRB, communication mode, source address information, destination address information and connection identification information. The communication mode, the source address information, the destination address information, the connection identification information, the configuration of each protocol layer of the first SL DRB and the identification of the first SL DRB have an association relationship.
Optionally, each protocol layer configuration of the first SL DRB comprises one or more of the following configurations: service data protocol (SDAP) configuration, Packet Data Convergence Protocol (PDCP) configuration, Radio Link Control (RLC) configuration, Logical Channel (LCH) configuration, and the like.
Wherein the SDAP configuration may include one or more of the following information: parameter information (such as QoS parameters, communication mode, source address information, destination address information, connection identification information) mapped to the first SL DRB; indication information of whether default (default) SL DRB configuration is available; the SDAP layer packet header information.
Illustratively, the PDCP configuration may include one or more of the following information: a timer discardTimer for controlling a time that a Service Data Unit (SDU) can be stored in the PDCP buffer; a timer t-Reordering for waiting for out-of-order packets in a Reordering function; whether the PDCP layer can deliver data packets to an upper layer out of order; whether the PDCP layer adopts sidelink data compression and relevant configuration of the sidelink data compression, such as the size of a compression buffer, a dictionary adopted by the compression, and the like; a Sequence Number (SN) length adopted by the PDCP layer PDU; security configuration adopted by the PDCP entity comprises whether encryption and/or integrity protection is adopted; a security algorithm (integrity protection algorithm and encryption algorithm) and/or a secret key and the like adopted by the PDCP entity; whether the PDCP adopts a duplicate mechanism and a duplicate configuration or not, if the duplicate mechanism is adopted, the PDCP entity corresponds to two/more RLC entities and the LCH; and (3) related configuration of a PDCP layer header compression algorithm, such as whether header compression is adopted. The duplicate mechanism refers to that the PDCP entity duplicates PDCP PDUs and delivers them to the associated two/multiple RLC entities for processing and transmission.
Illustratively, the RLC configuration may include: the RLC entity may adopt a Mode, such as an Acknowledged Mode (AM) Mode, an Unacknowledged Mode (UM) Mode, or a Transparent Mode (TM) Mode (where the RLC layer configuration may not be considered in the TM Mode). If the transmitting RLC entity is configured to adopt AM mode, the RLC configuration further includes one or more of the following information: the SN length of the RLC layer PDU is used for controlling a timer t-PollRecransmit for initiating poll (poll refers to that a sending end AM RLC entity indicates a receiving end AM RLC entity to perform status report feedback through a poll bit in an MAC PDU) retransmission, a parameter poll PDU for controlling how many RLC PDUs are sent and need to initiate poll, a parameter poll byte for controlling how many bytes of RLC PDUs are sent and need to initiate poll, the maximum retransmission times maxRetxThreshold of the RLC layer, a timer t-Reassembly for controlling the RLC layer to wait for segmentation, and a timer t-StatusProhibit for controlling the RLC layer to avoid frequently sending status reports.
Illustratively, if the transmitting RLC entity is configured to adopt UM mode, the RLC configuration further includes one or more of the following information: and controlling a timer t-response of the RLC layer waiting for segmentation according to the SN length of the PDU of the RLC layer.
Illustratively, the LCH configuration can include one or more of the following information: LCH identification (e.g., LCH ID); an identification of the logical channel group of the LCH; relevant parameters for logical channel priority processing: priority, Priority Bit Rate (PBR), token bucket size duration; carrier information of data in the LCH can be transmitted; resource mode information, such as mode 1, or mode 2, or mode 1 and mode 2, that can transmit data in the LCH; base parameter set numerology information of resources where data in the LCH can be transmitted, such as subcarrier spacing, cyclic prefix length, resource time domain duration, whether grant resources can be configured, etc.; controlling whether the LCH can trigger a parameter SR-mask of the SR; controlling whether the LCH can delay the parameter SR-DelayTimerApplied triggering the SR.
Optionally, the LCH configuration may further include a logical channel index, where the logical channel index is used to obtain a logical channel ID, such as the LCH ID, according to a preset rule. The first terminal device may use the logical channel index to complete the mapping of the logical channel index to the logical channel ID. Assuming that the first terminal device is a transmitting end, for the transmitting end, the LCH ID uniquely identifies a logical channel within a target address information. Since some LCH IDs may have been occupied by the SL DRB configuration of mode 1 or the SL DRB configuration of mode 2, a logical channel index needs to be introduced to solve the problem of LCH ID collision of mode 1 and mode 2 for the same destination address information by the first terminal device. For example, the first terminal acquires logical channel indexes, selects unoccupied logical channel IDs for certain specific destination address information, and associates the logical channel indexes with the selected logical channel IDs. For example, the first terminal device may associate logical channel index 1 to the selected smallest logical channel ID, and logical channel index 2 to the selected logical channel ID next to the smallest logical channel ID (i.e. larger than the smallest logical channel ID only); alternatively, the first terminal device may associate logical channel index 1 to the selected largest logical channel ID, and logical channel index 2 to the selected logical channel ID next to the largest logical channel only (i.e., smaller than the largest logical channel ID only). Alternatively, the preset rule for associating the logical channel index to the logical channel ID may also be implemented in other ways, which are not limited to this.
While the specific configuration of the first SL DRB is described above, it is described herein as a unified description, in the embodiment of the present application, the specific configuration of the first SL DRB described above is applicable regardless of whether the SLDRB is predefined by a standard, that is, the corresponding SL DRB configuration is searched through an index corresponding to the first SL DRB, or the network device configuration, and the specific configuration of the first SL DRB described above is not limited thereto.
Optionally, the first RRC message sent by the first terminal device to the network device may further include second indication information. Wherein the second indication information is used to indicate that the first QoS parameter is predefined by standard or is predefined by non-standard, for example, the first QoS parameter is PFI. Alternatively, the second indication information is used to indicate that the first QoS parameter is non-standard predefined, such as PFI is dynamically configured.
For example, taking the first QoS parameter as PFI as an example, the standard predefined PFI refers to: the QoS profile associated with the PFI value is the same for all connections of one or more terminal devices. If a terminal device uses a PFI value predefined by the standard, a QoS profile associated with the PFI value is also well defined in the standard. The QoS profile associated with the PFI value is determined, regardless of which terminal device, or which connection, is available from the standard.
For example, for the case of dynamically configuring PFI, the core network or V2X control function may configure multiple different PFIs for different terminal devices, e.g., configure PFI1, PFI2, and PFI3 for UE1, and configure PFI2, PFI3, and PFI4 for UE2, where respective associated QoS profiles are different for the same PFI in UE1 and UE2, e.g., QoS profile associated with PFI2 of UE1 is different from QoS profile associated with PFI2 of UE 2. Alternatively, different connections of the same end device (such as a PC5-S connection) may correspond to different PFIs, and QoS profiles associated with the same PFI within different connections may be different.
Here, whether the first QoS parameter is standard predefined may depend on an indication of an upper layer of the UE. For example, the second indication information may be submitted by the V2X layer or APP layer of the first terminal device to the AS layer of the first terminal device.
The second implementation mode comprises the following steps: when the first terminal device is in an RRC idle state or an inactive state, there is no interaction of RRC messages between the first terminal device and the network device, so that radio bearer configuration information is obtained through listening to system broadcast messages.
Optionally, the method 200 further comprises: a network device sends a System Information Block (SIB) broadcast message, the SIB broadcast message including the radio bearer configuration information. Accordingly, S210 includes: s212, the first terminal device receives a system information block SIB broadcast message sent by the network device.
For example, when the first terminal device is in an RRC idle state or an inactive state, the resource configuration mode adopted by the first terminal device is mode 2, and the radio bearer configuration information may be obtained through an SIB broadcast message sent by the network device. Here, the radio bearer configuration information includes an index corresponding to the first SL DRB and the first parameter, and the index corresponding to the SL DRB has an association relationship with the first parameter. The index corresponding to the first SL DRB is standard predefined. In this way, the first terminal device may obtain the standard predefined first SL DRB configuration according to the index corresponding to the first SL DRB. It should be understood that the standard predefined first SL DRB may refer to the description in S211, and for brevity, will not be described in detail here.
Or, optionally, the radio bearer configuration information in the SIB broadcast message includes a specific configuration of the first SL DRB and the first parameter, where the specific configuration of the first SL DRB has an association relationship with the first parameter. It should be understood that the specific configuration of the first SLDRB may refer to the description in S211, and is not described herein for brevity.
Or, when the first terminal device is in the RRC idle state or the inactive state, the RRC connection establishment may be triggered, and the radio bearer configuration information may be acquired from the RRC response message. Here, the first terminal device obtains the specific description of the radio bearer configuration information from the RRC response message, refer to the first implementation manner, where the first terminal device obtains the specific description of the radio bearer configuration information through the second RRC message, and for brevity, the detailed description is omitted here.
Optionally, the first QoS parameter may be standard predefined, for example, the PFI is standard predefined, when the first terminal device is in the RRC idle state or the inactive state.
The above describes a manner in which the first terminal device obtains the radio bearer configuration information through an RRC message or an SIB broadcast message, and the first terminal device may also obtain the radio bearer configuration information through a preconfigured manner.
Optionally, the first terminal device is in an RRC idle state or an inactive state, and may obtain the radio bearer configuration information from the pre-configuration information. The pre-configuration information comprises an index corresponding to the SL DRB and a first parameter, and the index corresponding to the SL DRB has an association relation with the first parameter. The index corresponding to the first SL DRB is standard predefined. In this way, the first terminal device may obtain the standard predefined first SL DRB configuration according to the index corresponding to the first SL DRB. It should be understood that the standard predefined first SL DRB may refer to the description in S211, and for brevity, will not be described in detail here.
Optionally, the radio bearer configuration information in the preconfiguration information includes a specific configuration of the first SL DRB and the first parameter, where the specific configuration of the first SL DRB has an association relationship with the first parameter. It should be understood that the description of the specific configuration of the first SL DRB may refer to the description of S211, and for brevity, will not be described herein.
Optionally, the first QoS parameter in the provisioning information may be standard predefined, for example, the PFI is standard predefined.
Optionally, when the first terminal device exceeds the coverage OOC, the radio bearer configuration information may be obtained from the pre-configuration information. It should be understood that some specific implementation manners of the radio bearer configuration information are similar to the description of obtaining the radio bearer configuration information from the pre-configuration information when the first terminal device is in the RRC idle state or the inactive state, and for brevity, no detailed description is given.
In the embodiment of the present application, a priority order for acquiring the radio bearer configuration information may be defined, so that the first terminal device decides which way to use to acquire the radio bearer configuration information based on the priority order.
For example, the priority order for acquiring the radio bearer configuration information may be sequentially decreased according to the following order: the method comprises the steps of acquiring the sidechain radio bearer configuration information through an RRC message, acquiring the sidechain radio bearer configuration information through an SIB message, and acquiring the sidechain radio bearer configuration information through a pre-configuration mode.
In the various implementations described above, after obtaining the radio bearer configuration information, the first terminal device may send the radio bearer configuration information to an opposite terminal device, such as the second terminal device.
Optionally, the method 200 further comprises: the first terminal device may send the radio bearer configuration information to a second terminal device. Wherein the radio bearer configuration information comprises one or more of: (1) SL DRB configurations related to only data transmission, (2) SL DRB configurations related to only data reception, and (3) SL DRB configurations related to both data transmission and reception. Here, if the radio bearer configuration information includes a plurality of items of the above-mentioned contents, the included plurality of items of the contents have an association relationship. For brevity, the numbers (1), (2) and (3) are used for description, and the corresponding specific contents of the numbers can be referred to above. For example, the radio bearer configuration information includes: (1) and (2) and (3), then the (1), (2) and (3) have an association relationship; for another example, the radio bearer configuration information includes: (1) and (3), then there is a correlation between (1) and (3); for another example, the radio bearer configuration information includes: (2) and (3), then there is a correlation between (2) and (3); for another example, the radio bearer configuration information includes: (1) and (2), then (1) and (2) have a correlation.
For example, the first terminal device may be an originating UE, and the second terminal device may be a receiving UE. The first terminal device may send the SL DRB configuration related to data transmission to the second terminal device, so that the second terminal device may perform data transmission on the SL using the SL DRB configuration related to data transmission when performing the transmission action.
For example, the first terminal device may be an originating UE, and the second terminal device may be a receiving UE. The first terminal device may send the SL DRB configuration related to data reception to the second terminal device, so that the second terminal device may perform data reception on the SL using the SL DRB configuration related to data reception when performing a reception action.
For example, whether the first terminal device is a receiving UE or an originating UE, or whether the second terminal device is a receiving UE or an originating UE, the first terminal device may send the SL DRB configuration related to both data transmission and data reception to the second terminal device, so that the second terminal device may also use the SL DRB configuration related to both data transmission and data reception to transmit or receive data on the SL when performing transceiving actions.
For the case that the first terminal device acquires the radio bearer configuration information by using the index and the first parameter corresponding to the first SL DRB, when the first terminal device sends the radio bearer configuration information to the second terminal device, the first terminal device may send the index corresponding to the SL DRB to the second terminal device. The second terminal device can know the SL DRB configuration predefined by the corresponding standard based on the index corresponding to the SL DRB. Optionally, the first terminal device may further send, to the second terminal device, the first parameter associated with the index corresponding to the SL DRB, so that the second terminal device may know the related information of the first parameter associated with the standard predefined SLDRB.
Optionally, the method 200 further comprises: the first terminal device obtains a SL DRB configuration only related to data reception.
For example, the data reception-only SL DRB configuration may also be one or more of the following parameters associated with the SL DRB corresponding to the data reception-only SL DRB configuration by the first terminal device: QoS parameter, resource configuration mode, communication type, source address, destination address, connection identification and other information.
For example, the first terminal device determines the SL DRB configuration only related to data reception according to the SL DRB configuration only related to data transmission corresponding to the SL DRB configuration only related to data reception.
For example, the first terminal device determines the SL DRB configuration related to only data reception according to the SL DRB configuration related to both data transmission and reception corresponding to the SL DRB configuration related to only data reception.
For example, the first terminal device determines the SL DRB configuration related to only data reception according to the SL DRB configuration related to only data transmission corresponding to the SL DRB configuration related to only data reception and the SL DRB configuration related to both data transmission and reception corresponding to the SL DRB configuration related to only data reception.
Optionally, the SL DRB configuration related to data reception only is sent to the first terminal device by the second terminal device. For example, the second terminal device may obtain the SL DRB configuration only related to data reception from an RRC message, an SIB message, or pre-configuration information.
For example, the second terminal device configures one or more of the following parameters associated with the SLDRB corresponding to the data reception-related SL DRB only: and information such as QoS parameters, resource configuration modes, communication types, source addresses, target addresses, connection identifiers and the like determines SL DRB configuration only relevant to data reception.
For example, the second terminal device determines the SL DRB configuration only related to data reception according to the SL DRB configuration only related to data transmission corresponding to the SL DRB configuration only related to data reception.
For example, the second terminal device determines the SL DRB configuration related to only data reception according to the SL DRB configuration related to both data transmission and reception corresponding to the SL DRB configuration related to only data reception.
For example, the second terminal device corresponds to the SL DRB configuration related to data reception only: SL DRB configurations related to both data transmission and reception and SL DRB configurations related to only data transmission, the SL DRB configuration related to only data reception is determined.
For both the first terminal device and the second terminal device, the information such as the QoS parameter, the resource allocation mode, and the communication type associated with the SL DRB corresponding to the SL DRB configuration related to data reception only can be used; or, determining the SL DRB configuration related to only data reception according to the SL DRB configuration related to only data transmission and/or the SL DRB configuration related to both data transmission and reception corresponding to the SL DRB configuration related to only data reception.
Alternatively, whether for the first terminal device or the second terminal device, the SL DRB configuration rule related to only data reception may be correspondingly determined through an RRC message, an SIB message, or pre-configuration, or the SL DRB configuration related to only data reception may be determined by itself. Optionally, the corresponding priority levels are sequentially decreased by RRC message, SIB message, or pre-configuring SL DRB configuration rules that correspondingly determine only data reception related.
Having described the above related embodiments of the first terminal device acquiring the radio bearer configuration information of the side chain, the following describes a technical solution of the terminal device acquiring the QoS configuration file associated with the V2X data packet.
Whether unicast, multicast or broadcast, the AS layer of the end device needs to know the specific PC5 QoS profile associated with each V2X packet. In NR V2X, where unicast, multicast and broadcast are based on per-flow QoS model, each V2X packet at the upper layer will carry a PC5 QoS flow id PFI. Further, the terminal device also needs to acquire the QoS profile associated with the V2X packet. In view of the above, the present application further provides a method for obtaining a QoS profile of a data packet.
Fig. 3 shows a schematic flow chart of a method 300 for obtaining a QoS profile for a data packet according to another embodiment of the present application. As shown in fig. 3, the method 300 includes:
s310, an Access (AS) layer of a terminal device acquires a PC5 QoS flow identification PFI and a QoS configuration file, wherein the PFI and the QoS configuration file have a corresponding relation, and the QoS configuration file comprises one or more of the following information: the PC5 fifth generation communication system quality of service identity PQI, guaranteed stream bit rate GFBR, maximum stream bit rate MFBR, minimum required communication distance, allocation and reservation priority ARP.
Wherein, the AS layer comprises an SDAP layer, a PDCP layer, an RLC layer, an MAC layer and a PHY layer.
As an optional implementation manner, S310 includes: the AS layer of the terminal device may obtain the correspondence from an upper layer (V2X layer or APP layer).
Optionally, the obtaining, by the access stratum AS of the terminal device, the corresponding relationship from the V2X layer or the APP layer includes:
the V2X layer or APP layer of the terminal device obtains the corresponding relationship from a core network, or the V2X layer or APP layer of the terminal device obtains the pre-configured corresponding relationship; and the access layer AS of the terminal equipment receives the corresponding relation from the V2X layer or the APP layer of the terminal equipment.
Optionally, the AS layer of the terminal device may also obtain the corresponding relationship through a V2X control function (control function).
Optionally, if the corresponding relationship is changed or updated, the core network or the V2X control function may send an update instruction to the V2X layer or APP layer of the terminal device, so as to instruct the terminal device to update the corresponding relationship. And the V2X layer or the APP layer of the terminal equipment submits the updating indication to the AS layer of the terminal equipment so that the AS layer of the terminal equipment obtains the updated corresponding relation.
As another optional implementation manner, S310 includes: and the AS layer of the terminal equipment receives the corresponding relation sent by the network equipment.
For example, the receiving, by the AS layer of the terminal device, the correspondence sent by the network device includes: the AS layer of the terminal equipment receives an RRC message sent by the network equipment, wherein the RRC message comprises the corresponding relation; or, the AS layer of the terminal device receives an SIB message sent by the network device, where the SIB message includes the correspondence.
Optionally, if the corresponding relationship is changed or updated, the network device may send an update instruction to the AS layer of the terminal device, so AS to instruct the terminal device to update the corresponding relationship. The AS layer of the terminal device may update the corresponding relationship based on the update indication to obtain an updated corresponding relationship.
S320, the terminal device determines a QoS configuration file corresponding to the first data packet based on the corresponding relation. Wherein the first packet is used to generically refer to a V2X packet.
When the first data packet is delivered to the AS layer from an upper layer (including the V2X layer or the APP layer), the upper layer of the terminal device carries the PFI associated with the first data packet instead of the packet header of the first data packet in an interlayer primitive between the upper layer and the AS layer (wherein the interlayer primitive may be understood AS an interlayer interaction), or the upper layer of the terminal device carries the PFI in the packet header of the first data packet delivered to the AS layer. And after the terminal equipment obtains the corresponding relation, the terminal equipment can further obtain the QoS configuration file corresponding to the first data packet. In this way, it can be ensured that the AS layer of the terminal device can know the QoS configuration file of each V2X data packet, where the QoS configuration file of the V2X data packet can be used for resource selection, parameter configuration, and the like during transmission of corresponding SL data.
Optionally, assuming that the terminal device is an originating UE, the originating UE may send the obtained correspondence to a receiving UE. Here, the originating UE may send via PC5-RRC message (e.g., may send with radio bearer configuration information (SLDRB configuration), or may send via RRC reconfiguration message, or may send when establishing PC5RRC connection, or may carry PC5 QFI in the header of the SDAP, or may send via PC5-S message on PC5-S upper layer connection).
Each V2X data packet submitted to the AS layer by an upper layer (including a V2X layer or an APP layer) carries the QoS configuration file and the PFI in an inter-layer source language, so that the AS layer of the terminal device can know the QoS configuration file of each V2X data packet.
An Access Stratum (AS) of a terminal device receives a first data packet from a V2X layer or an APP layer of the terminal device, wherein the first data packet carries (specifically, the first data packet may be carried by an inter-layer primitive or a header of the first data packet) a PC5 QoS flow identifier (PFI) associated with the first data packet, and a QoS configuration file associated with the first data packet; and the terminal equipment acquires the PFI and the QoS configuration file which have an association relationship from the first data packet.
Specifically, an upper layer (such AS a V2X layer or an APP layer) of the terminal device may carry the associated PFI in each V2X packet, AS well AS the QoS profile, in an inter-layer primitive or a header of the V2X packet when submitting the V2X packet to the AS layer. In this way, after receiving the V2X data packet, the AS layer of the terminal device obtains the PFI and the QoS profile having an association relationship from the V2X data packet. The terminal device may continuously update the association relationship between the PFI and the QoS configuration file according to the PFI and the QoS configuration file carried by the V2X data packet (specifically, carried by the inter-layer primitive or carried by the packet header of the first data packet) at the lower layer. The AS layer of the terminal device may use the PFI for matching to obtain a QoS profile associated with the corresponding PFI.
Therefore, the terminal device may obtain the PFI and the QoS profile having an association relationship in the PFI and the QoS profile carried by the V2X packet.
It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
It should also be understood that the various aspects of the embodiments of the present application can be combined and used reasonably, and the explanation or illustration of the various terms appearing in the embodiments can be mutually referred to or explained in the various embodiments, which is not limited.
The method for acquiring the radio bearer configuration according to the embodiment of the present application is described in detail above with reference to fig. 1 to 3. A communication apparatus according to an embodiment of the present application will be described below with reference to fig. 4 to 7. It should be understood that the technical features described in the method embodiments are equally applicable to the following apparatus embodiments.
Fig. 4 shows a schematic block diagram of a communication device 400 according to an embodiment of the present application. The apparatus 400 is configured to perform the method performed by the terminal device in the foregoing method embodiment. Optionally, the specific form of the apparatus 400 may be a terminal device or a module (e.g., a chip) in the terminal device, which is not limited in this application. Alternatively, the device 400 may be an in-vehicle communication device, an in-vehicle communication chip. For example, the apparatus 400 is a first terminal device, and the apparatus 400 includes: a transceiver module 410 and a processing module 420.
A transceiver module 410, configured to obtain radio bearer configuration information of a side chain, where the radio bearer configuration information includes an index corresponding to a first side chain data radio bearer SL DRB and a first parameter, and the index corresponding to the first SLDRB has an association relationship with the first parameter, where the first parameter includes a first quality of service QoS parameter and/or a resource configuration mode of the first terminal device, and the side chain is a radio link between the first terminal device and a second terminal device.
A processing module 420, configured to perform a side-chain transmission based on the radio bearer configuration information.
In one possible implementation manner, the transceiver module 410 is further configured to: and sending a first RRC message to a network device, wherein the first RRC message comprises the first QoS parameter and first indication information, and the first indication information is used for indicating that a resource configuration mode corresponding to the first QoS parameter is a mode 2.
Optionally, the transceiver module 410 is configured to obtain radio bearer configuration information of a side chain, including: receiving a second RRC message sent by a network device, wherein the second RRC message comprises the radio bearer configuration information, and the radio bearer configuration information is sidechain radio bearer configuration information associated with the mode 2, or the sidechain radio bearer configuration information is sidechain radio bearer configuration information associated with the mode 1.
Optionally, the first RRC message further includes second indication information, where the second indication information is used to indicate that the first QoS parameter is standard predefined or non-standard predefined.
Optionally, the transceiver module 410 is further configured to: receiving the second indication information from the V2X layer or APP layer of the first terminal device.
Optionally, the first RRC message further includes a preconfigured SL DRB associated with the first QoS parameter, or the first RRC message further includes a SL DRB acquired by the first terminal device associated with the first QoS parameter by receiving a SIB broadcast message.
Optionally, the first SL DRB includes a logical channel configuration, where the logical channel configuration includes a logical channel index, and the logical channel index is used to obtain a logical channel ID according to a preset rule.
In a possible implementation manner, the transceiver module 410 is configured to acquire radio bearer configuration information of a side chain, and specifically includes: receiving a System Information Block (SIB) broadcast message sent by a network device, wherein the SIB broadcast message includes the radio bearer configuration information; alternatively, the processing module 420 is configured to trigger RRC connection establishment, and acquire the radio bearer configuration information by receiving an RRC response message.
Optionally, the first QoS parameter is standard predefined.
Optionally, the first QoS parameter comprises one or more of the following information: the method comprises the steps that a PC5 QoS flow identifies PFI, a PC5 fifth generation communication system service quality identification PQI guarantees a flow bit rate GFBR, a maximum flow bit rate MFBR, a minimum required communication distance and a distribution and reservation priority ARP.
It should be understood that the apparatus 400 for power control according to the embodiment of the present application may correspond to the method of the terminal device in the foregoing method embodiment, for example, the method in fig. 2, and the above and other management operations and/or functions of each module in the apparatus 400 are respectively for implementing corresponding steps of the method of the terminal device in the foregoing method embodiment, so that beneficial effects in the foregoing method embodiment may also be implemented, and for brevity, no repeated description is provided here.
Alternatively, the apparatus 400 (for example, the apparatus 400 is a terminal device) may further execute the method for acquiring the QoS configuration file of the data packet according to the embodiment of the present application, which is specifically as follows:
a transceiver module 410, configured to obtain a PC5 QoS flow identifier PFI and a QoS profile, where the PFI and the QoS profile have a corresponding relationship, and the QoS profile includes one or more of the following information: the PC5 fifth generation communication system service quality identification PQI ensures the stream bit rate GFBR, the maximum stream bit rate MFBR, the minimum required communication distance, and the allocation and reservation priority ARP;
A processing module 420, configured to determine a QoS profile corresponding to the first data packet based on the correspondence relationship.
In a possible implementation manner, the obtaining, by the AS layer of the terminal device, a corresponding relationship between the PFI and the QoS configuration file includes: the V2X layer or the APP layer of the terminal device obtains the corresponding relationship from a core network, or obtains the pre-configured corresponding relationship; and the access layer AS of the terminal equipment receives the corresponding relation from the V2X layer or the APP layer of the terminal equipment.
It should be understood that the communication apparatus 400 according to the embodiment of the present application may correspond to the method of the terminal device in the foregoing method embodiment, for example, the method in fig. 3, and the above and other management operations and/or functions of each module in the apparatus 400 are respectively for implementing corresponding steps of the method of the terminal device in the foregoing method embodiment, so that beneficial effects in the foregoing method embodiment may also be implemented, and for brevity, no repeated description is provided here.
Alternatively, the apparatus 400 (for example, the apparatus 400 is a terminal device) may further execute the method for acquiring the QoS configuration file of the data packet according to the embodiment of the present application, which is specifically as follows: a transceiving module 410, configured to receive a first packet from a V2X layer or an APP layer of the terminal device, where the first packet carries (carried by an inter-layer primitive or carried by a header of the first packet) a PC5 QoS flow identification PFI associated with the first packet, and a QoS profile associated with the first packet; a processing module 420, configured to obtain the PFI and the QoS profile having a corresponding relationship from the first data packet.
It should also be understood that the various modules in the apparatus 400 may be implemented in software and/or hardware, and are not particularly limited in this regard. In other words, the apparatus 400 is presented in the form of a functional module. As used herein, a "module" may refer to an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor and memory that execute one or more software or firmware programs, an integrated logic circuit, and/or other devices that may provide the described functionality. Alternatively, in a simple embodiment, one skilled in the art will recognize that apparatus 400 may take the form shown in FIG. 5. The processing module 420 may be implemented by the processor 501 shown in fig. 5. The transceiver module 410 may be implemented by the transceiver 503 shown in fig. 5. In particular, the processor is implemented by executing a computer program stored in the memory. Alternatively, when the apparatus 400 is a chip, then the functions and/or implementation processes of the transceiver module 410 can also be implemented by pins or circuits, etc. Optionally, the memory is a storage unit in the chip, such as a register, a cache, and the like, and the storage unit may also be a storage unit located outside the chip in the computer device, such as the memory 502 in fig. 5.
Fig. 5 shows a schematic block diagram of a communication apparatus 500 according to an embodiment of the present application. Alternatively, the device 500 may be an in-vehicle communication device, an in-vehicle communication chip. As shown in fig. 5, the apparatus 500 includes: a processor 501.
In one possible implementation, the processor 501 is configured to invoke an interface to perform the following actions: acquiring radio bearer configuration information of a side chain, wherein the radio bearer configuration information comprises an index corresponding to a first side chain data radio bearer (SL DRB) and a first parameter, the index corresponding to the first SL DRB and the first parameter have an association relationship, the first parameter comprises a first quality of service (QoS) parameter and/or a resource configuration mode of the first terminal device, and the side chain is a radio link between the first terminal device and a second terminal device; the processor 501 is further configured to perform a side-chain transmission based on the radio bearer configuration information.
Alternatively, the processor 501 is configured to: acquiring a PC5 QoS flow identifier (PFI) and a QoS configuration file, wherein the PFI and the QoS configuration file have a corresponding relation, and the QoS configuration file comprises one or more of the following information: the PC5 fifth generation communication system service quality identification PQI ensures the stream bit rate GFBR, the maximum stream bit rate MFBR, the minimum required communication distance, and the allocation and reservation priority ARP; the processor 501 is further configured to determine a QoS profile corresponding to the first data packet based on the correspondence relationship.
Or, the processor 501 is configured to receive a first packet from a V2X layer or an APP layer of the terminal device, where the first packet carries (carried by an inter-layer primitive or a header of the first packet) a PC5 QoS flow identifier PFI associated with the first packet, and a QoS profile associated with the first packet; and obtaining the PFI and the QoS configuration file with corresponding relation from the first data packet.
It should be understood that the processor 501 may invoke an interface to perform the transceiving actions, wherein the invoked interface may be a logical interface or a physical interface, which is not limited thereto. Alternatively, the physical interface may be implemented by a transceiver. Optionally, the apparatus 500 further comprises a transceiver 503.
Optionally, the apparatus 500 further includes a memory 502, and the memory 502 may store the program codes in the above method embodiments for the processor 501 to call.
Specifically, if the apparatus 500 includes a processor 501, a memory 502 and a transceiver 503, the processor 501, the memory 502 and the transceiver 503 communicate with each other via an internal connection path to transmit control and/or data signals. In one possible design, the processor 501, the memory 502, and the transceiver 503 may be implemented by chips, and the processor 501, the memory 502, and the transceiver 503 may be implemented in the same chip, or may be implemented in different chips, or any two functions may be implemented in one chip. The memory 502 may store program code that the processor 501 calls upon stored by the memory 502 to implement the corresponding functionality of the apparatus 500.
It should be understood that the apparatus 500 may also be used to perform other steps and/or operations on the terminal device side in the foregoing embodiments, and details are not described herein for brevity.
Fig. 6 shows a schematic block diagram of a communication device 600 according to an embodiment of the present application. The apparatus 600 is configured to perform the method performed by the network device in the foregoing method embodiment. Alternatively, the specific form of the apparatus 600 may be a network device or a module (e.g., a chip) in the network device. Alternatively, the device 600 may be a vehicle-mounted communication device, a vehicle-mounted communication chip. The embodiments of the present application do not limit this. The apparatus 600 comprises: a processing module 610 and a transceiver module 620.
A processing module 610, configured to determine an index corresponding to a first side-link data radio bearer SL DRB and a first parameter, where the index corresponding to the first SL DRB has an association relationship with the first parameter, and the first parameter includes a first quality of service QoS parameter and/or a resource configuration mode of the first terminal device.
A transceiver module 620, configured to send radio bearer configuration information of a side chain, where the radio bearer configuration information includes an index corresponding to the first SL DRB and the first parameter, and the side chain is a radio link between the first terminal device and a second terminal device.
In one possible implementation manner, the transceiver module 620 is configured to transmit the radio bearer configuration information of the side chain, including: receiving a first RRC message sent by a first terminal device, where the first RRC message includes the first QoS parameter and first indication information, and the first indication information is used to indicate that a resource configuration mode corresponding to the first QoS parameter is mode 2; sending a second RRC message to the first terminal device, the second RRC message including the radio bearer configuration information, the radio bearer configuration information being either side chain radio bearer configuration information associated with the mode 2 or side chain radio bearer configuration information associated with the mode 1.
In a possible implementation manner, the first RRC message further includes second indication information, where the second indication information is used to indicate that the first QoS parameter is standard predefined or non-standard predefined.
In a possible implementation manner, the first RRC message further includes a preconfigured SL DRB associated with the first QoS parameter, and accordingly, the transceiver module 620 is configured to send a second RRC message to the first terminal device, specifically including: sending a second RRC message to the first terminal equipment according to the pre-configured SL DRB; or, the first RRC message further includes an SLDRB associated with the first QoS parameter, which is acquired by the first terminal device through an SIB broadcast message, and accordingly, the transceiver module 620 is configured to send the second RRC message to the first terminal device, which specifically includes: and sending a second RRC message to the first terminal equipment according to the SL DRB acquired by the first terminal equipment through SIB broadcast message.
Optionally, the first SL DRB includes a logical channel configuration, where the logical channel configuration includes a logical channel index, and the logical channel index is used for the first terminal device to obtain a logical channel ID according to a preset rule.
In a possible implementation manner, the first terminal device is in a radio resource control RRC idle state or an inactive state, and the transceiver module 620 is configured to send radio bearer configuration information of a side chain, which specifically includes: transmitting a system information block, SIB, broadcast message, the SIB broadcast message including the radio bearer configuration information.
It should be understood that the communication apparatus 600 according to the embodiment of the present application may correspond to the method of the network device in the foregoing method embodiment, for example, the method in fig. 2, and the above and other management operations and/or functions of each module in the apparatus 600 are respectively for implementing corresponding steps of the method of the network device in the foregoing method embodiment, so that beneficial effects in the foregoing method embodiment may also be implemented, and for brevity, no repeated description is provided here.
It should also be understood that the various modules in the apparatus 600 may be implemented in software and/or hardware, and are not particularly limited in this regard. In other words, the apparatus 600 is presented in the form of a functional module. As used herein, a "module" may refer to an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor and memory that execute one or more software or firmware programs, an integrated logic circuit, and/or other devices that may provide the described functionality. Alternatively, in a simple embodiment, those skilled in the art will appreciate that the apparatus 600 may take the form shown in FIG. 7. The processing module 610 may be implemented by the processor 701 shown in fig. 7. The transceiver module 620 may be implemented by the transceiver 703 shown in fig. 7. In particular, the processor is implemented by executing a computer program stored in the memory. Alternatively, when the apparatus 600 is a chip, the functions and/or implementation processes of the transceiver module 620 may be implemented by pins, circuits or the like. Optionally, the memory is a storage unit in the chip, such as a register, a cache, and the like, and the storage unit may also be a storage unit located outside the chip in the computer device, such as the memory 702 in fig. 7.
Fig. 7 shows a schematic block diagram of a communication device 700 according to an embodiment of the present application. Alternatively, the device 700 may be an in-vehicle communication device, an in-vehicle communication chip. As shown in fig. 7, the apparatus 700 includes: a processor 701.
In one possible implementation, the processor 701 is configured to: the method comprises the steps of determining an index corresponding to a first side-link data radio bearer (SL DRB) and a first parameter, wherein the index corresponding to the first SL DRB has an association relation with the first parameter, and the first parameter comprises a first quality of service (QoS) parameter and/or a resource configuration mode of the first terminal equipment; the processor 701 is configured to invoke an interface to perform the following actions: and sending radio bearer configuration information of a side chain, wherein the radio bearer configuration information includes an index corresponding to the first SL DRB and the first parameter, and the side chain is a radio link between the first terminal device and a second terminal device.
It should be understood that the processor 701 may invoke an interface to perform the above transceiving action, wherein the invoked interface may be a logical interface or a physical interface, which is not limited thereto. Alternatively, the physical interface may be implemented by a transceiver. Optionally, the apparatus 700 further comprises a transceiver 703.
Optionally, the apparatus 700 further includes a memory 702, and the memory 702 may store the program codes in the above method embodiments, so as to be called by the processor 701.
Specifically, if the apparatus 700 includes the processor 701, the memory 702 and the transceiver 703, the processor 701, the memory 702 and the transceiver 703 communicate with each other through an internal connection path to transmit control and/or data signals. In one possible design, the processor 701, the memory 702, and the transceiver 703 may be implemented by chips, and the processor 701, the memory 702, and the transceiver 703 may be implemented in the same chip, or may be implemented in different chips, or any two functions may be implemented in one chip. The memory 702 may store program code, and the processor 701 may call the program code stored by the memory 702 to implement the corresponding functions of the apparatus 700.
It should be understood that the apparatus 700 may also be used to perform other steps and/or operations on the network device side in the foregoing embodiments, and therefore, for brevity, the detailed description is omitted here.
The method disclosed in the embodiments of the present application may be applied to a processor, or may be implemented by a processor. The processor may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The processor may be a general purpose processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, a system on chip (SoC), a Central Processing Unit (CPU), a Network Processor (NP), a Digital Signal Processor (DSP), a Microcontroller (MCU), a programmable logic controller (PLD), or other integrated chip. The various methods, steps, and logic blocks disclosed in the embodiments of the present application may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware decoding processor, or implemented by a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.
It will be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), double data rate SDRAM, enhanced SDRAM, SLDRAM, Synchronous Link DRAM (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to comprise, without being limited to, these and any other suitable types of memory.
It should be understood that, in the embodiment of the present application, the numbers "first" and "second" … introduced for terms are only used for distinguishing different objects, such as different messages, and do not limit the scope of the embodiment of the present application, and the embodiment of the present application is not limited thereto.
It should also be understood that, in the various embodiments of the present application, the size of the serial number of each process described above does not mean the execution sequence, and the execution sequence of each process should be determined by the function and the inherent logic of each process. The various numbers or serial numbers involved in the above processes are merely used for convenience of description and should not be construed as limiting the implementation processes of the embodiments of the present application in any way.
It should also be understood that the term "and/or" herein is merely one type of association that describes an associated object, meaning that three relationships may exist, e.g., a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.
Items appearing in this application as similar to "include one or more of the following: the meaning of the expressions A, B, and C "generally means that the item may be any of the following, unless otherwise specified: a; b; c; a and B; a and C; b and C; a, B and C; a and A; a, A and A; a, A and B; a, A and C, A, B and B; a, C and C; b and B, B, B and C, C and C; c, C and C, and other combinations of A, B and C. The above description is made by taking 3 elements of a, B and C as examples of optional items of the item, and when the expression "item" includes at least one of the following: a, B, … …, and X ", i.e., more elements in the expression, then the items to which the item may apply may also be obtained according to the aforementioned rules.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a U disk, a removable hard disk, a read-only memory ROM, a random access memory RAM, a magnetic disk, or an optical disk.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (24)

1. A method for obtaining a radio bearer configuration, comprising:
a first terminal device obtains radio bearer configuration information of a side chain, wherein the radio bearer configuration information includes an index corresponding to a first side chain data radio bearer (SL DRB) and a first parameter, the index corresponding to the first SL DRB and the first parameter have an association relationship, the first parameter includes a first quality of service (QoS) parameter and/or a resource configuration mode of the first terminal device, and the side chain is a radio link between the first terminal device and a second terminal device;
and the first terminal equipment carries out side chain transmission based on the radio bearer configuration information.
2. The method of claim 1, further comprising:
The first terminal device sends a first Radio Resource Control (RRC) message to a network device, wherein the first RRC message comprises the first QoS parameter and first indication information, and the first indication information is used for indicating that a resource configuration mode corresponding to the first QoS parameter is a mode 2.
3. The method according to claim 1 or 2, wherein the first terminal device acquires radio bearer configuration information of a side chain, comprising:
the first terminal device receives a second RRC message sent by a network device, where the second RRC message includes the radio bearer configuration information, and the radio bearer configuration information is side chain radio bearer configuration information associated with the mode 2, or the radio bearer configuration information is side chain radio bearer configuration information associated with the mode 1.
4. The method according to claim 2 or 3, wherein the first RRC message further comprises second indication information indicating that the first QoS parameter is standard predefined or non-standard predefined.
5. The method of claim 4, further comprising:
and the access stratum AS of the first terminal equipment receives the second indication information from the V2X layer or the APP layer of the first terminal equipment.
6. The method according to any of claims 2 to 5, wherein the first RRC message further comprises a pre-configured SL DRB associated with the first QoS parameter, or wherein the first RRC message further comprises a SL DRB associated with the first QoS parameter that is acquired by the first terminal device by receiving a System information Block, SIB, broadcast message.
7. The method according to any of claims 1 to 6, wherein the first SL DRB comprises a logical channel configuration, wherein the logical channel configuration comprises a logical channel index, and wherein the logical channel index is used for acquiring a logical channel Identifier (ID) according to a preset rule.
8. The method of claim 1, wherein the obtaining, by the first terminal device, radio bearer configuration information of a side chain comprises:
the first terminal equipment receives a System Information Block (SIB) broadcast message sent by network equipment, wherein the SIB broadcast message comprises the radio bearer configuration information;
or, the first terminal device triggers the establishment of the radio resource control RRC connection, and acquires the radio bearer configuration information by receiving an RRC response message.
9. The method of claim 8, wherein the first QoS parameter is standard predefined.
10. The method according to any of claims 1 to 9, wherein the first QoS parameter comprises one or more of the following information: the PC5 QoS flow identification PFI, the PC5 fifth generation communication system QoS identification PQI, the guaranteed flow bit rate GFBR, the maximum flow bit rate MFBR, the minimum required communication distance, the allocation and the reservation priority ARP.
11. A method for obtaining a radio bearer configuration, comprising:
the network equipment determines an index and a first parameter corresponding to a first side-link data radio bearer (SL DRB), wherein the index and the first parameter have an association relationship, and the first parameter comprises a first quality of service (QoS) parameter and/or a resource configuration mode of first terminal equipment;
the network device sends radio bearer configuration information of a side chain, where the radio bearer configuration information includes an index corresponding to the first SL DRB and the first parameter, and the side chain is a radio link between the first terminal device and a second terminal device.
12. The method of claim 11, wherein the network device sends radio bearer configuration information for the sidechain, comprising:
The network device receives a first Radio Resource Control (RRC) message from the first terminal device, wherein the first RRC message comprises the first QoS parameter and first indication information, and the first indication information is used for indicating that a resource configuration mode corresponding to the first QoS parameter is a mode 2;
the network device sends a second RRC message to the first terminal device, where the second RRC message includes the radio bearer configuration information, and the radio bearer configuration information is side chain radio bearer configuration information associated with the mode 2, or the side chain radio bearer configuration information is side chain radio bearer configuration information associated with the mode 1.
13. The method of claim 12, wherein the first RRC message further comprises second indication information indicating that the first QoS parameter is either standard predefined or non-standard predefined.
14. The method according to claim 12 or 13, wherein the first RRC message further comprises a pre-configured SL DRB associated with the first QoS parameter,
correspondingly, the sending, by the network device, the second RRC message to the first terminal device includes:
The network device sends a second RRC message to the first terminal device according to the pre-configured SL DRB associated with the first QoS parameter;
or, the first RRC message further comprises a SL DRB associated with the first QoS parameter acquired by the first terminal device by receiving a SIB broadcast message,
correspondingly, the sending, by the network device, the second RRC message to the first terminal device includes:
and the network equipment sends a second RRC message to the first terminal equipment according to the SL DRB which is associated with the first QoS parameter and is acquired by the first terminal equipment through receiving SIB broadcast messages.
15. The method according to any of claims 11 to 14, wherein the first SL DRB comprises a logical channel configuration, wherein the logical channel configuration comprises a logical channel index, and the logical channel index is used for the first terminal device to obtain a logical channel ID according to a preset rule.
16. The method of claim 11, wherein the first terminal device is in a radio resource control, RRC, idle state or an inactive state, and wherein the network device sends radio bearer configuration information for a sidelink, comprising:
The network device sends a system information block, SIB, broadcast message, the SIB broadcast message including the radio bearer configuration information.
17. A method for obtaining a quality of service, QoS, profile for a data packet, comprising:
an access AS layer of a terminal device acquires a PC5 QoS flow identification PFI and a QoS configuration file, wherein the PFI and the QoS configuration file have a corresponding relation, and the QoS configuration file comprises one or more of the following information: the PC5 fifth generation communication system service quality identification PQI ensures the stream bit rate GFBR, the maximum stream bit rate MFBR, the minimum required communication distance, and the allocation and reservation priority ARP;
and the terminal equipment determines a QoS configuration file corresponding to the first data packet based on the corresponding relation.
18. The method AS claimed in claim 17, wherein the obtaining, by the AS layer of the terminal device, the corresponding relationship between the PFI and the QoS profile includes:
the Internet of vehicles V2X layer or the application APP layer of the terminal equipment acquires the corresponding relation from a core network, or acquires the pre-configured corresponding relation;
and the access layer AS of the terminal equipment receives the corresponding relation from the V2X layer or the APP layer of the terminal equipment.
19. A communications device comprising means for performing the method of any of claims 1 to 10, or the method of any of claims 17 to 18.
20. A communications apparatus, comprising means for performing the method of any of claims 11-16.
21. A communications device comprising a processor and interface circuitry for receiving and transmitting signals from or sending signals to other communications devices than the communications device, the processor being arranged to implement the method of any one of claims 1 to 10 by means of logic circuitry or executing code instructions, or to implement the method of any one of claims 17 to 18.
22. A communications device comprising a processor and interface circuitry for receiving and transmitting signals from or sending signals to a communications device other than the communications device, the processor being operable by logic circuitry or executing code instructions to implement the method of any of claims 11 to 16.
23. A computer-readable storage medium, in which a program or instructions are stored which, when executed, implement the method of any one of claims 1 to 10, or 17 to 18.
24. A computer-readable storage medium, in which a program or instructions are stored which, when executed, implement the method of any one of claims 11 to 16.
CN201910365478.7A 2019-04-30 2019-04-30 Method and apparatus for obtaining radio bearer configuration Active CN111866796B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201910365478.7A CN111866796B (en) 2019-04-30 2019-04-30 Method and apparatus for obtaining radio bearer configuration
PCT/CN2020/087703 WO2020221281A1 (en) 2019-04-30 2020-04-29 Method and apparatus for acquiring radio bearer configuration

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910365478.7A CN111866796B (en) 2019-04-30 2019-04-30 Method and apparatus for obtaining radio bearer configuration

Publications (2)

Publication Number Publication Date
CN111866796A true CN111866796A (en) 2020-10-30
CN111866796B CN111866796B (en) 2022-07-22

Family

ID=72965753

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910365478.7A Active CN111866796B (en) 2019-04-30 2019-04-30 Method and apparatus for obtaining radio bearer configuration

Country Status (2)

Country Link
CN (1) CN111866796B (en)
WO (1) WO2020221281A1 (en)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022134030A1 (en) * 2020-12-25 2022-06-30 华为技术有限公司 Data transmission method and apparatus
WO2023011219A1 (en) * 2021-08-03 2023-02-09 华为技术有限公司 Communication method and apparatus
WO2023011101A1 (en) * 2021-08-06 2023-02-09 华为技术有限公司 Data transmission method and communication apparatus
WO2023020148A1 (en) * 2021-08-19 2023-02-23 华为技术有限公司 Method and apparatus for processing exception in unicast connection establishment
WO2023036038A1 (en) * 2021-09-13 2023-03-16 华为技术有限公司 Communication method and apparatus

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113347694B (en) * 2021-06-30 2022-12-06 锐迪科微电子科技（上海）有限公司 Radio bearer release method, apparatus, device and medium
CN116939704A (en) * 2022-03-30 2023-10-24 华为技术有限公司 Data packet processing method and device
CN117354810A (en) * 2022-07-05 2024-01-05 华为技术有限公司 Information transmission method and communication device

Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106470384A (en) * 2015-08-18 2017-03-01 北京信威通信技术股份有限公司 A kind of carrying collocation method in D2D communication
CN107018162A (en) * 2016-01-28 2017-08-04 电信科学技术研究院 A kind of method and terminal carried out data transmission
CN107040959A (en) * 2016-02-04 2017-08-11 中兴通讯股份有限公司 The method and device of car networking traffic congestion control
WO2017158515A1 (en) * 2016-03-15 2017-09-21 Telefonaktiebolaget Lm Ericsson (Publ) Systems and methods for quality of service differentiation for non-ip bearers
WO2017173586A1 (en) * 2016-04-05 2017-10-12 华为技术有限公司 User terminal management method and related device
CN107295644A (en) * 2016-03-31 2017-10-24 北京信威通信技术股份有限公司 Communication processing method and device
WO2017206168A1 (en) * 2016-06-03 2017-12-07 华为技术有限公司 V2x message communication method and device
CN107580340A (en) * 2016-07-05 2018-01-12 普天信息技术有限公司 A kind of resource regulating method in V2X networks
WO2018066905A1 (en) * 2016-10-07 2018-04-12 엘지전자 주식회사 Method and device for performing v2x communication
CN108307472A (en) * 2016-08-12 2018-07-20 中兴通讯股份有限公司 The communication means and device of equipment direct communication system, communication system
CN109314841A (en) * 2016-07-18 2019-02-05 松下电器（美国）知识产权公司 Improved support to the service quality of V2X transmission
CN110831075A (en) * 2018-08-10 2020-02-21 中兴通讯股份有限公司 Data transmission method and device and service switching method and device
CN111447678A (en) * 2019-01-16 2020-07-24 华为技术有限公司 Communication method and communication device
CN111757476A (en) * 2019-03-28 2020-10-09 华为技术有限公司 Communication method and device

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10484517B2 (en) * 2017-02-10 2019-11-19 Qualcomm Incorporated Quality of service support for layer 2 based device-to-device relay
CN108260082B (en) * 2017-12-13 2020-06-30 中国联合网络通信集团有限公司 Method and device for selecting resources in V2X resource pool

Patent Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106470384A (en) * 2015-08-18 2017-03-01 北京信威通信技术股份有限公司 A kind of carrying collocation method in D2D communication
CN107018162A (en) * 2016-01-28 2017-08-04 电信科学技术研究院 A kind of method and terminal carried out data transmission
CN107040959A (en) * 2016-02-04 2017-08-11 中兴通讯股份有限公司 The method and device of car networking traffic congestion control
WO2017158515A1 (en) * 2016-03-15 2017-09-21 Telefonaktiebolaget Lm Ericsson (Publ) Systems and methods for quality of service differentiation for non-ip bearers
CN107295644A (en) * 2016-03-31 2017-10-24 北京信威通信技术股份有限公司 Communication processing method and device
WO2017173586A1 (en) * 2016-04-05 2017-10-12 华为技术有限公司 User terminal management method and related device
WO2017206168A1 (en) * 2016-06-03 2017-12-07 华为技术有限公司 V2x message communication method and device
CN107580340A (en) * 2016-07-05 2018-01-12 普天信息技术有限公司 A kind of resource regulating method in V2X networks
CN109314841A (en) * 2016-07-18 2019-02-05 松下电器（美国）知识产权公司 Improved support to the service quality of V2X transmission
CN108307472A (en) * 2016-08-12 2018-07-20 中兴通讯股份有限公司 The communication means and device of equipment direct communication system, communication system
WO2018066905A1 (en) * 2016-10-07 2018-04-12 엘지전자 주식회사 Method and device for performing v2x communication
CN110831075A (en) * 2018-08-10 2020-02-21 中兴通讯股份有限公司 Data transmission method and device and service switching method and device
CN111447678A (en) * 2019-01-16 2020-07-24 华为技术有限公司 Communication method and communication device
CN111757476A (en) * 2019-03-28 2020-10-09 华为技术有限公司 Communication method and device

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
CATT: "QoS Management for NR V2X", 《3GPP TSG-RAN WG2 MEETING #104 R2-1816899》 *
HUAWEI: "Support of QoS for PC5-based V2V transport", 《3GPP TSG-RAN WG2 MEETING #94 R2-163811》 *
LENOVO: "Discussion on QoS management for NR V2X", 《3GPP TSG-RAN WG2 MEETING #104 R2-1817118》 *
SESSION CHAIR: "Report from session on LTE V2X and NR V2X", 《3GPP TSG-RAN WG2 MEETING #105BIS R2-190XXXX》 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022134030A1 (en) * 2020-12-25 2022-06-30 华为技术有限公司 Data transmission method and apparatus
WO2023011219A1 (en) * 2021-08-03 2023-02-09 华为技术有限公司 Communication method and apparatus
WO2023011101A1 (en) * 2021-08-06 2023-02-09 华为技术有限公司 Data transmission method and communication apparatus
WO2023020148A1 (en) * 2021-08-19 2023-02-23 华为技术有限公司 Method and apparatus for processing exception in unicast connection establishment
WO2023036038A1 (en) * 2021-09-13 2023-03-16 华为技术有限公司 Communication method and apparatus

Also Published As

Publication number Publication date
WO2020221281A1 (en) 2020-11-05
CN111866796B (en) 2022-07-22

Similar Documents

Publication Publication Date Title
CN111866796B (en) Method and apparatus for obtaining radio bearer configuration
US20190387383A1 (en) DESIGN OF SCHEDULING REQUEST FOR FURTHER ENHANCED NARROWBAND INTERNET OF THINGS (feNB-IoT)
WO2017166141A1 (en) Data sending method and apparatus, and base station
CN111586643B (en) Method and communication device for unicast transmission
CN110622545A (en) Resource configuration method, terminal equipment and network equipment
WO2018059518A1 (en) Data transmission method, device and system
CN113573355B (en) Communication method and device
US20220159696A1 (en) Wireless communication method, terminal device, and network device
CN111417215A (en) Configuration method of radio bearer, terminal and communication device
WO2021249430A1 (en) Communication method and related device
CN113826370A (en) Communication method and communication device
CN112385269A (en) Path selection method, terminal equipment and network equipment
CN113950851A (en) Wireless communication method and apparatus
CN114364040B (en) Wireless communication method and terminal device
CN111918313B (en) Method, network device and communication device for resource allocation
US20210185711A1 (en) Information transmission method, communications device, and network device
WO2021000701A1 (en) Communication method and related device
WO2018227564A1 (en) Communication method, terminal device, and network device
CN111757293B (en) Communication method and communication device
CN107409349B (en) Discovery information transmission method, device and communication system
CN111212398B (en) Method for supporting data repetition, transmitting terminal device, receiving terminal device and storage medium
CN114503649A (en) Communication method and communication device
CN110731108B (en) Carrier selection method in Internet of vehicles and terminal equipment
WO2019033416A1 (en) Wireless communication method, terminal device, and network device
WO2024032285A1 (en) Communication method and apparatus

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant