Side link priority sorting method, user equipment and base station

Abstract

The present invention provides a sidelink priority sorting method executable in a user equipment. After receiving an initial priority value of a sidelink service, the user equipment determines the service type of the sidelink channel and generates a refined priority value for the sidelink service based on the initial priority value according to the service type of the sidelink service.

Description

Technical field

[0001] The present invention relates to the field of communication systems, and in particular to a side link priority sorting method, user equipment, and a base station. [Background Technology]

[0002] Wireless communication systems such as the third-generation (3G) mobile phone standards and technologies are well known. Such 3G standards and technologies have been developed by the Third Generation Partnership Project (3GPP). Third-generation wireless communications have generally been developed to support macrocellular mobile phone communications. Communication systems and networks have been developed towards broadband and mobile systems. In a cellular wireless communication system, user equipment (UE) is connected to a radio access network (RAN) via a radio link. The RAN includes a set of base stations (BSs) that provide radio links to UEs located in cells covered by the base stations, as well as an interface to a core network (CN) for overall network control. As will be understood, the RAN and CN each perform corresponding functions related to the overall network. The Third Generation Partnership Project developed the so-called Long Term Evolution (LTE) system, or Evolved Universal Mobile Telecommunications System Territorial Radio Access Network (E-UTRAN), a mobile access network for one or more macrocells supported by base stations called eNodeBs or eNBs (evolved NodeBs). More recently, LTE has evolved further into so-called 5G or new radio (NR) systems, in which one or more cells are supported by base stations called gNBs. NR is proposed to use the orthogonal frequency division multiplexing (OFDM) physical transmission format. In traditional cellular communication networks, all signaling occurs between each mobile device and the base station, rather than directly between mobile devices, even when the mobile devices are within wireless communication range of each other. This can lead to inefficient use of radio transmission resources and potentially increase base station resource utilization. Sidelink communication allows multiple mobile devices to communicate directly with each other, rather than through the base station, potentially improving both radio and base station resource utilization. Sidelink communication is particularly well-suited for machine-to-machine communication, particularly vehicle-to-vehicle (V2V) and vehicle-to-everything (V2X) communication. The following embodiments of the present invention relate to various improvements to various cellular wireless communication systems, particularly those related to sidelink communication in these systems. [Summary of the invention]

[0003] The purpose of the embodiments of the present invention is to provide a side link priority sorting method, user equipment and base station.

[0004] In a first aspect, an embodiment of the present invention provides a side link priority sorting method executable in a user device, comprising: receiving an initial priority value of a side link service; determining a service type of the side link channel; and generating a refined priority value of the side link service based on the initial priority value according to the service type of the side link service.

[0005] In second aspect, an embodiment of the present invention provides a side link priority sorting method executable in a base station, comprising: receiving an initial priority value of a side link service; determining the service type of the side link channel; generating a refined priority value of the side link service based on the initial priority value according to the service type of the side link service; and providing the refined priority value as part of side link control information SCI associated with the side link service.

[0006] In a third aspect, an embodiment of the present invention provides a user device comprising a processor, wherein the processor is configured to perform the following steps: receiving an initial priority value of a side link service; determining a service type of the side link channel; and generating a refined priority value of the side link service based on the initial priority value according to the service type of the side link service.

[0007] In a fourth aspect, an embodiment of the present invention provides a base station, comprising a processor, which is used to perform the following steps: receiving an initial priority value of a side link service; determining the service type of the side link channel; generating a refined priority value of the side link service based on the initial priority value according to the service type of the side link service; and providing the refined priority value as part of side link control information SCI associated with the side link service.

[0008] A non-transitory computer-readable medium storing a computer-executable program for implementing the above-disclosed method may include at least one of a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a read-only memory, a programmable read-only memory, an erasable programmable read-only memory, an EPROM, an electrically erasable programmable read-only memory, and a flash memory.

Brief Description of the Drawings

[0009] In order to more clearly illustrate the embodiments of the present invention or related technologies, the following drawings will be described in conjunction with a brief introduction to the embodiments. Obviously, the drawings are only some embodiments of the present invention, and those skilled in the art can derive other drawings based on these drawings without any creative work.

[0010] Figure 1 A schematic diagram of a mobile communication system is provided.

[0011] Figure 2 Schematic diagram of a side link priority sorting method provided by an embodiment of the present invention.

[0012] Figure 3 It is a schematic diagram of a side link priority sorting method provided by another embodiment of the present invention.

[0013] Figure 4 This is a schematic diagram of a side link priority sorting method provided by another embodiment of the present invention.

[0014] Figure 5 It is a schematic diagram of a framework of a wireless communication system provided by an embodiment of the present invention. [Specific implementation method]

[0015] The technical content, structural features, objectives and effects of the embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It is particularly noted that the terms in the embodiments of the present invention are only used to illustrate the purpose of the embodiments of the present invention and are not used to limit the present invention.

[0016] Fifth Generation (5G) wireless systems are typically Frequency Range 2 (FR2) cellular communication systems. FR2 operates in the 24.25 GHz to 52.6 GHz band. Base stations (BSs) and / or user equipment (UEs) employ multiplexed transmit and receive beams to combat the significant path loss in the high-frequency band. Due to hardware limitations and cost considerations, BSs and UEs may only be equipped with a limited number of transmit and receive units (TXRUs).

[0017] The main idea of ​​the present invention is to provide a new design for Quality of Service (QoS) management. QoS management is related to vehicle to everything / anything (V2X) communication in terms of resource allocation, congestion control, in-device coexistence, power control and Sidelink Radio Bearer (SLRB) configuration. The multiple physical layer parameters involved in QoS management may include priority, latency, reliability and minimum required communication range defined by multiple higher layer parameters of the current transmission service. For sidelink (SL) unicast, multicast and broadcast, the QoS parameters of the V2X data packets are provided by multiple higher layers to the access stratum (AS).

[0018] Any user equipment configured to receive a group destination Layer 2 Identifier (ID) is allowed to receive multicast transmissions, whether within or outside the "minimum communication range" provided by multiple higher layers.

[0019] Sidelink transmissions from different service types (e.g., unicast, multicast, and broadcast) may be treated differently, resulting in different priorities for multiple service types. The embodiments of the present invention propose a more flexible mechanism, and the sidelink transmission of each service type may have a configurable priority to meet different communication situations and QoS requirements. The embodiments of the present invention propose a QoS management mechanism that considers service types for multiple Non-Access Stratum (NAS) layers and / or multiple AS layers. For specific communication situations such as congestion control, starvation avoidance, sensing processes, and preemption, specific service types may require higher priorities to ensure transmission quality and improve QoS for a given priority level.

[0020] In order to balance drop events between multiple service priorities and multiple service types in the case of channel congestion, embodiments of the present invention provide a solution at the physical layer that considers service types in distributed congestion control (DCC), and proposes CR-limit compensation for multicast and broadcast.

[0021] The distinction between multiple service types and the priority information for each transmission can be determined by multiple higher-layer parameters. These higher-layer parameters can distinguish service types and modify priority information. Furthermore, the physical layer can use priority information containing information about multiple service types. The higher layers may include layers above the physical layer in the protocol stack. For example, in the Long Term Evolution (LTE) protocol stack, these multiple higher layers may include the Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), Radio Resource Control (RRC), and the Non-Access Stratum (NAS). Furthermore, QoS handled in the physical layer may result in a very draconian solution at the radio interface, such as dropping transmissions for congestion control, while QoS handled by multiple higher layers is more flexible.

[0022] The main idea of ​​the present invention is to provide a new design for QoS management, in which the priority sorting process for each side link transmission can take into account multiple service types. In certain specific transmission situations, such as congestion control, starvation avoidance, sensing process and preemption, a specific service type may require a refined priority that is higher or lower than the assigned initial priority. For example, in a specific scenario, since the QoS impact of multicast or broadcast on packet loss is several times that of unicast on packet loss, multicast and broadcast require a higher priority to meet the QoS requirements. For another example, for bursty unicast transmission tasks, the highest priority is required to ensure transmission quality. Therefore, a flexible QoS management mechanism with a configurable relationship between priority and service type is needed, which can be used to meet different scenarios and improve robustness. In an embodiment of the present invention, several solutions are proposed at the NAS layer and / or AS layer to provide multiple QoS management mechanisms that take into account service types.

[0023] Please refer to Figure 1 , user equipment 10a, user equipment 10b, base station 200a and network entity device 300 perform a side link priority sorting method provided by an embodiment of the present invention. The connection between the device and the device components is Figure 1, shown as lines and arrows. User equipment 10a may include a processor 11a, a memory 12a, and a transceiver 13a. User equipment 10b may include a processor 11b, a memory 12b, and a transceiver 13b. Base station 200a may include a processor 201a, a memory 202a, and a transceiver 203a. Network entity device 300 may include a processor 301, a memory 302, and a transceiver 303. Processors 11a, 11b, 201a, and 301 may each be configured to implement the intended functions, programs, and / or methods described in the embodiments of the present invention. The layers of the wireless interface protocol may be implemented in processors 11a, 11b, 201a, and 301. Memories 12a, 12b, 202a, and 302 each store various programs and information to operate the connected processors. Transceivers 13a, 13b, 203a, and 303 are each coupled to the connected processors and transmit and / or receive wireless signals or wired signals. The user equipment 10a communicates with the user equipment 10b via the side link 110. The base station 200a may be an eNB (evolved NodeB), a gNB, or one of other radio nodes, and may configure the side link 110 between the user equipment 10a and the user equipment 10b.

[0024] The processors 11a, 11b, 201a and 301 may each include an application-specific integrated circuit (ASIC), other chipsets, logic circuits and / or data processing devices. The memories 12a, 12b, 202a and 302 may each include a read-only memory (ROM), a random access memory (RAM), a flash memory, a memory card, a storage medium and / or other storage devices. The transceivers 13a, 13b, 203a and 303 may each include a baseband circuit and a radio frequency (RF) circuit to process radio frequency signals. When the embodiments of the present invention are implemented in software, the technical solutions described herein may be implemented by modules, programs, functions, entities, etc. that perform the functions described herein. The module may be stored in a memory and executed by a processor. The memory may be implemented within the processor or outside the processor, and may be communicatively coupled to the processor in various ways known in the art.

[0025] Communication between user devices can be achieved through device-to-device (D2D) communication or vehicle-to-everything (V2X) communication. Based on the sidelink technology developed in 3GPP Releases 14, 15, and 16 and above, V2X communication includes vehicle-to-vehicle (V2V) communication, vehicle-to-pedestrian (V2P) communication, and vehicle-to-infrastructure / network (V2I / N) communication. User devices communicate directly with each other via a sidelink interface, such as the PC5 interface.

[0026] The network entity device 300 may be a node in a core network (CN). The CN may include an LTE CN or a 5G core (5GC), which includes a user plane function (UPF), a session management function (SMF), a mobility management function (AMF), a unified data management (UDM), a policy control function (PCF), a control plane (CP) / user plane (UP) separation (CUPS), an authentication server (AUSF), a network slice selection function (NSSF), and a network exposure function (NEF).

[0027] Please refer to Figure 2, a user device (e.g., user device 10a or user device 10b) includes a processor configured to perform a side link prioritization method. In an embodiment of the present invention, the user device receives an initial priority value of a side link service (e.g., side link 110) (step 222) and determines the service type of the side link channel (step 224). The user device generates a refined priority value of the side link service based on the initial priority value according to the service type of the side link service (step 226). The initial priority value of the side link service is represented by a short-range communication data packet priority (ProSe Per-Packet Priority, PPPP), a short-range communication data packet reliability (ProSe Per-Packet Reliability, PPPR), or a combination of PPPP and PPPR. The initial priority value of the side link service is a priority used in the AS, NAS, logical channel allocation or channel busy ratio (CBR) level processing process. The embodiment of the present invention can be derived from any combination of the following multiple solutions.

[0028] NAS is a functional layer in the LTE wireless communication protocol stack between a communication system, such as the Universal Mobile Telecommunications System (UMTS), and the core network and user equipment (UE). The NAS layer is used to manage the establishment of communication sessions and maintain continuous communication with mobile UE devices. The definition of NAS is in contrast to the AS, which is responsible for transmitting information in the radio access network. NAS is a protocol used to transmit messages between the UE and the CN entity. CN entities are also called core nodes, such as the Mobile Switching Center (MSC), the Serving GPRS Support Node (SGSN), and the Mobility Management Entity (MME). NAS messages are transparently transmitted over the radio access network (RAN). NAS messages include, for example, update or additional messages, authentication messages, and service requests. Once the UE establishes a radio connection, it uses this radio connection to communicate with the core node to coordinate services. The AS is used explicitly between the UE and the wireless network, while the NAS is used between the UE and the core node.

[0029] The access stratum (AS) is a functional layer in the wireless communication protocol stack between mobile communication systems such as UMTS and LTE, the wireless network and the user equipment (UE). Although the definition of the access stratum in LTE is very different from that in UMTS, the access stratum in both LTE and UMTS is responsible for transmitting data over the radio connection and managing radio resources.

[0030] In the following, the prioritization process in the NAS and AS is used to distinguish QoS authorizations on sidelink transmissions. In this embodiment of the present invention, service types include unicast, multicast, broadcast, etc. The number of service types is represented by a configurable parameter TrafficTypeNum, and a specific service type is represented by the parameter TrafficTypex.

[0031] The method disclosed in the embodiment of the present invention can be applied in NAS, and is described in detail as follows.

[0032] The 5G QoS Identifier (5QI) is a scalar that serves as a reference to the specific QoS forwarding behavior (e.g., packet loss rate and packet delay budget) to be provided to a 5G QoS flow. 5QI can be implemented in the access network through multiple 5QI reference node-specific parameters that control the QoS forwarding process, such as scheduling weights, admission thresholds, queue management thresholds, and link layer protocol configuration. PC5 QoS characteristics associated with the PC5 5QI (PQI), including priority, have the same format and meaning as the PPPP defined in Technical Specification (TS) 23.285. When a Proximity Service (ProSe) upper layer above the PC5 access layer transmits a Protocol Data Unit (PDU) to the PC5 access layer, the ProSe upper layer provides a PPPP within a range of 8 possible values. As described in 3GPP 23.303 Section 4.5.1.1.2.3.1, a user equipment (eg, user equipment 10a or user equipment 10b) may configure a PPPP value as an initial priority value for transmitting a PC5-S message.

[0033] V2X service data across different communication modes (e.g., broadcast, multicast, and unicast) can use different priority levels. When QoS requirements cannot be met for all PC5 service data, priority levels are used as a baseline to prioritize data processing. For example, PC5 service data with a smaller priority level value, N, takes precedence over PC5 service data with larger priority level values ​​(e.g., N+1, N+2, etc.). A smaller priority level value indicates a higher priority.

[0034] To handle multiple service types in different scenarios, a higher-level configuration flag, CastTypeFlag, is defined. CastTypeFlag is an n-bit flag used to determine whether to consider the service type of the sidelink service when determining its priority level, where n >= 1. In one embodiment, CastTypeFlag is 1 bit, meaning n = 1. CastTypeFlag = 1 indicates that the priority level includes service type information.

[0035] If the priority level needs to take the business type into consideration, the priority level can be divided into three levels: high priority, medium priority and low priority. Each level includes several consecutive priority levels, each corresponding to a specific business type.

[0036] Refer to Table 1. For example, when TrafficTypeNum = 3, different QoS levels are used for various service flows of three service types (e.g., unicast, multicast, and broadcast). Using an n-bit parameter PPPP (n = 3 in this example), the high priority level and the medium priority level each have three priority levels. At the low priority level, multicast and broadcast have the same priority level. The specific mapping relationship between priority and various service types can be configured by the communications operator. Table 1 is an example of the descending priority order of various service types provided by the operator.

[0037] Table 1

[0038]

[0039]

[0040] As shown in Table 2, in another alternative embodiment where the CastTypeFlag is 2 bits, that is, n=2, different values ​​of CastTypeFlag correspond to different priority sorting processes for various service types:

[0041] Table 2

[0042]

[0043] The method disclosed in the embodiment of the present invention can be applied to AS, and is described in detail as follows.

[0044] The V field in the MAC header of the Sidelink Shared Channel (SL-SCH) indicates which version of the SL-SCH subheader is used. For V2X sidelink communications, if the V field is set to "0001," it indicates a multicast identifier; if the V field is set to "0010," it indicates a unicast identifier. Therefore, information about the service type can be obtained from the V field.

[0045] The SL-Priority information element (IE) indicates one or more priorities associated with a MAC layer resource pool used for sidelink communications. The SL-Priority value is derived from the PPPP. The PPPP is a scalar value associated with a protocol data unit (PDU) that defines the priority of that PDU's transmission. In one example, SL-Priority can be used to prioritize V2X service data across different service types. The physical layer in the user equipment (UE) complies with the SL-Priority configuration.

[0046] The following is a detailed description of a new technical solution using the above-mentioned SL-Priority and logical channel group (LCG). Each sidelink logical channel is assigned to an LCG based on a priority, such as SL-Priority or PPPR of the sidelink logical channel. PPPR is a scalar value associated with a protocol data unit, which defines the reliability of the transmission of the protocol data unit. Multiple high-level parameters provide a mapping between a single LCG identifier (ID) in the logicalChGroupInfoList and a priority value of a single logical channel (such as PPPR of the logical channel). Service types can be used in the above-mentioned channel allocation. Each LCG is associated with a short-range service target address. The following description is from two aspects: SL-Priority and logical channel allocation.

[0047] A technical solution for the above-mentioned SL-Priority is described in detail below, which uses a priorityOffset. Logical channel allocation is performed based on the above-mentioned SL-Priority. In an embodiment of the present invention, the SL-Priority value uses an n-bit parameter priorityOffset, where n≥1. Each SL-Priority value represents a priority level, and the smaller the SL-Priority value, the higher its priority. priorityOffset can be associated with different service types respectively, and it can be configured for different situations.

[0048] The first option using priorityOffset is used to distinguish between unicast and non-unicast transmissions.

[0049] The priorityOffset parameter can indicate unicast and non-unicast transmission. In one example, priorityOffset is a 1-bit parameter. The value of priorityOffset is one of {0, 1}, which can be used to adjust the SL-Priority to generate a refined priority value SL-Priority(i), which is shown in the following formula:

[0050] SL-Priority(i)=min{(PPPP(i)-priorityOffset(j)),1}, (1)

[0051] where i∈{1,2,…8}

[0052] priorityOffset(j)=j, (2)

[0053] where j∈{0,1}

[0054] For example, the value of priorityOffset can be configured as:

[0055]

[0056] Alternatively, the value of priorityOffset can be configured as:

[0057]

[0058] The variable i is a PPPP number. The second option using priorityOffset is to distinguish between multiple non-unicast transmissions based on the number of group members.

[0059] The priorityOffset can represent a unicast service type and multiple non-unicast service types. In a user device group including multiple user device members, the multiple non-unicast service types can be divided into at least two service types based on the number of user device group members. The priority level of SL-Priority can be modified using priorityOffset based on the multiple service types and the number of group members to generate a refined priority value. In another example, priorityOffset is a 2-bit parameter, and the SL-Priority can be modified according to the following formula:

[0060] SL-Priority(i)=min{(PPPP(i)-priorityOffset(j)),1}, (5)

[0061] where i∈{1,2,…8}

[0062] priorityOffset(j)=j, (6)

[0063] where j∈{0,1,2}

[0064] A configurable parameter groupmemberThre can be used as a threshold to distinguish one-to-many transmission, which is a non-unicast service type. A parameter membernum indicates the number of group members. For example, the above priorityOffset can be configured according to the following formula:

[0065]

[0066] The above mapping relationship is configurable.

[0067] The third option of using priorityOffset is used to distinguish multiple business types.

[0068] In an alternative embodiment, priorityOffset is a 2-bit parameter. The value of priorityOffset is one of {0, 1, 2}. According to the following formula, priorityOffset can be used to modify the priority level of SL-Priority based on various service types and the number of group members. This mapping relationship is configurable.

[0069] SL-Priority(i)=min{(PPPP(i)-priorityOffset(j)),1}, (8)

[0070] where i∈{1,2,…8}

[0071] priorityOffset(j)=j, (9)

[0072] where j∈{0,1}

[0073]

[0074] For example, in congestion control, the impact of packet loss on multicast or broadcast in the feedback channel is several times greater than that on unicast. In this case, the priorityOffset of multicast and broadcast can be increased, while the unicast service type is associated with priorityOffset(0) to maintain the priority level of unicast at the original level. The priorityOffset of multicast can be 1, and the priorityOffset of broadcast can be 2, as shown in the following formula:

[0075]

[0076] An embodiment of the method disclosed in the present invention can be applied to logical channel allocation, and this embodiment will be described in detail below.

[0077] One embodiment of the present invention is to modify the above SL-Priority based on multiple traffic types.An alternative embodiment of the present invention provides for sidelink logical channel allocation based on multiple traffic types, wherein one SL-Priority is maintained at the original level.

[0078] Each sidelink logical channel can be assigned to an LCG, and the assignment depends on the service type and priority of the sidelink logical channel. In LTE, the mapping between an LCG's ID and the priority of the LCG is provided by multiple high-level parameters in logicalChGroupInfoList. logicalChGroupInfoList indicates a list of multiple associated priority levels for each LCG. In an embodiment of the present invention, logicalChGroupInfoList includes multiple service types, as shown in Table 3:

[0079] Table 3

[0080]

[0081] The value of TrafficTypeNum is configurable and ranges from 1 to m, where m ≥ 1. In an example where m = 3, TrafficTypeNum = 1 means that this traffic type is not considered in the prioritization process, TrafficTypeNum = 2 means that the prioritization process distinguishes between multiple traffic types based on unicast and non-unicast, and TrafficTypeNum = 3 means that the prioritization process distinguishes between multiple traffic types based on all three traffic types.

[0082] In an example where TrafficTypeNum=3, the association between LCG and SL-Priority is shown in Table 4 with logical channel group identifiers arranged in ascending order, where:

[0083] Table 4

[0084]

[0085] The parameter maxLCG is an integer representing the total number of logical channel groups. The mapping relationship between the parameter TrafficType x and various actual service types is configurable.

[0086] In addition, in the second column of Table 4 above, the LCG of a single service type may include LCG(0), LCG(1), ..., LCG(TrafficTypeNum×maxLCG-1). In the third column of Table 4 above, the SL-priorityList of a single service type may include SL-priorityList(0), SL-priorityList(1), ..., SL-priorityList(TrafficTypeNum×maxLCG-1), where TrafficTypeNum represents the number of service types. In the example of Table 4 above, TrafficTypeNum = 3. Any combination described above is possible.

[0087] An embodiment of the method disclosed in the present invention can be applied to logical channel priority sorting, and this embodiment will be described in detail below.

[0088]

[0014] Sidelink logical channels are prioritized for new transmissions according to a sidelink logical channel prioritization process. Each sidelink logical channel has an associated priority level represented by a PPPP or an associated PPPR. If multiple sidelink logical channels have the same priority level, the prioritization process for these channels considers multiple traffic types for the sidelink logical channels to accommodate different scenarios. Prioritization of multiple traffic types includes first determining the traffic type of the sidelink logical channel. Each traffic type has a list of multiple priorities for multiple logical channels.

[0089] The priority of multiple service types is arranged in descending order from TrafficType1 to TrafficType3. The mapping relationship between the parameter TrafficType x and the multiple service types is configured by multiple higher layers.

[0090] Please refer to Figure 3In a user equipment (such as user equipment 10a or user equipment 10b), a processing entity such as a MAC layer performs the following logical channel prioritization process for each sidelink control information (SCI) within a single sidelink control (SC) period in a sidelink transmission, or for each SCI corresponding to a new transmission in V2X sidelink communication. The MAC layer may be implemented by a computer program executed by a processor of the user equipment.

[0091] Extracting a PDU, such as a MAC PDU, associated with the SCI in a sidelink service that is one of a plurality of sidelink logical channels belonging to the same selected close proximity service target address (step 230);

[0092] Allocate resources to one of the plurality of sidelink logical channels having the highest priority in a particular traffic type (e.g., TrafficType1), the particular traffic type being selected from a plurality of traffic types associated with the plurality of sidelink logical channels (step 232);

[0093] If resources are available, the plurality of sidelink logical channels belonging to the same selected close range service target address are served according to the priority of each of the plurality of traffic types (such as TrafficType1 to TrafficType3) until the data of the sidelink logical channel or the SL grant is exhausted, whichever is satisfied first (step 234). Sidelink logical channels configured with the same priority should receive equal service.

[0094] When the data of the sidelink logical channel is no longer available for the priority processing flow, the data of the sidelink logical channel is determined to be exhausted. When there are no more SL grants available for the sidelink logical channel, the SL grant is determined to be exhausted. For example, in certain cases, the broadcast service type may have the highest priority, TrafficType1 may correspond to the broadcast service type, TrafficType2 to the multicast service type, and TrafficType3 to the unicast service type. The priority is arranged in descending order as shown in the following table:

[0095] Table 5

[0096]

[0097]

[0098] An embodiment of the method disclosed in the present invention can be applied to the channel busy rate (CBR) level processing flow described in detail below.

[0099] In one embodiment, the information element IE SL-CBR-CommonTxConfigList indicates a list of various physical sidelink shared channel (PSSCH) transmission parameters in SL-CBR-PSSCH-TxConfigList, and a list of various CBR levels in cbr-RangeCommonConfigList, where the PSSCH transmission parameters include modulation and coding scheme (MCS), number of subchannels, number of retransmissions, and CR-limit. The user equipment can use the IE SL-CBR-CommonTxConfigList to configure congestion control for V2X sidelink communication.

[0100] Multiple entries in cbr-RangeCommonConfigList and the mapping relationship between cbr-ConfigIndex and SL-CBR-Levels-Config can be configured as shown in Table 6. The cbr-ConfigIndex in SL-CBR-PPPP-TxConfigList and cbr-RangeCommonConfigList:

[0101] Table 6

[0102]

[0103] The parameter maxSL-V2X-CBRConfig indicates the maximum number of multiple CBR level configurations. 3GPP TS 36.331 v15.6.0 defines maxSL-V2X-CBRConfig = 4. The parameter maxCBR-Level indicates the maximum number of multiple CBR levels. 3GPP TS 36.331 v15.6.0 defines maxCBR-Level = 16. In Table 6, n = maxSL-V2X-CBRConfig.

[0104] Represents each entry of SL-CBR-Levels-Config, where x represents a cbr-ConfigIndex value and y represents a CBR level indicator. In the SL-CBR-PSSCH-TxConfig within the sl-CBR-PSSCH-TxConfigList, each CR-limit is represented by an indicator in tx-ConfigIndexList, and it is in turn mapped to a CBR level represented by cbr-ConfigIndex. The parameter tx-ConfigIndexList is a parameter associated with CR-limit in the SL-CBR-PPPP-TxConfigList. Both CR-limit and priority are used to determine a CBR level in the case of congestion control. New NR V2X features (such as multiple service types) may affect the Distributed Congestion Control (DCC) processing flow, and it is essential in determining the CBR level.

[0105] The first option for using service types in the CBR process is to use additional configuration for cbr-RangeCommonConfigList, as described below.

[0106] Each traffic type corresponds to one of several CBR levels. The cbr-RangeCommonConfigList in the SL-CBR-CommonTxConfigList represents a list of various CBR levels. Each entry in this list indicates the upper limit of the CBR level for the corresponding entry in the SL-CBR-Levels-Config. To incorporate traffic types into the CBR level configuration, the size of the CBR level list can be expanded.

[0107] For example, you can modify the cbr-RangeCommonConfigList in SL-CBR-CommonTxConfigList and the cbr-ConfigIndex in SL-CBR-PPPP-TxConfigList, as shown in Table 7 and Table 8. Table 7 is an example of IE SL-CBR-CommonTxConfigList, and Table 8 is an example of IE SL-CBR-PPPP-TxConfigList.

[0108] Table 7

[0109]

[0110] Table 8

[0111]

[0112] The mapping between service types and cbr-ConfigIndex is shown in the following table:

[0113] Table 9

[0114]

[0115] TrafficTypeNum has a configurable value range of 1 to m, where m ≥ 1. In an embodiment where m = 3, TrafficTypeNum = 1 indicates that the CBR level processing process does not consider the traffic type. TrafficTypeNum = 2 indicates that the CBR level processing process distinguishes between unicast and non-unicast traffic types. TrafficTypeNum = 3 indicates that the CBR level processing process distinguishes between the three types of traffic. The specific traffic type of TrafficType x can be configured, and TrafficType x is selected from TrafficType1 to TrafficType3.

[0116] The second option for using traffic types in CBR processing is to incorporate a TrafficType field in the SL-CBR-CommonTxConfigList, as described below.

[0117] As described in Option 1, the cbr-RangeCommonConfigList in the SL-CBR-CommonTxConfigList represents a list containing multiple CBR levels. Each entry in the list represents the upper limit of the CBR level of the corresponding entry in the SL-CBR-Levels-Config. To merge multiple service types, different service types can be distinguished by different entries in the cbr-RangeCommonConfigList in the SL-CBR-CommonTxConfigList. Each cbr-ConfigIndex can indicate one of the multiple service types and is configurable. Table 10 is an example of the cbr-RangeCommonConfigList, where:

[0118] Table 10

[0119] cbr-ConfigIndex Traffic Type 0 Traffic Type 1 1 Traffic Type 2 ... ... maxSL-V2X-CBRConfig-1 Traffic Type n

[0120] In Table 10, n=maxSL-V2X-CBRConfig, and maxSL-V2X-CBRConfig represents the maximum number of multiple CBR level configurations. 3GPP TS 36.331 v15.6.0 defines maxSL-V2X-CBRConfig=4.

[0121] The mapping between TrafficType x and the actual service type is configurable. For example, TrafficType 1 can correspond to unicast, TrafficType 2 can correspond to multicast, and TrafficType 3 can correspond to broadcast, and the redundant bit can be zero.

[0122] An embodiment of the method disclosed in the present invention can be applied to redesign side link control information SCI, as described below.

[0123] The SCI transmits sidelink scheduling information. The SCI processing flow may follow the downlink control information (DCI). The priority indicator of the sidelink transmission may be carried by the SCI payload. A base station such as base station 200a may determine the priority in the SCI of the sidelink based on the service type of the sidelink. The processor of the base station (e.g., base station 200a) may execute the method disclosed in the present invention.

[0124] Please refer to Figure 4 A higher layer receives an initial priority value for a sidelink service (step 242), for example, a sidelink 110 associated with two user devices (such as user device 10a and user device 10b), and determines a service type for the sidelink channel (step 244). The higher layer generates a refined priority value for the sidelink service based on the initial priority value according to the service type of the sidelink service (step 246), and provides the refined priority value as part of the SCI associated with the sidelink service (step 248). The higher layer can be a higher layer in the base station or in either user device 10a or user device 10b.

[0125] A first option to redesign the SCI to use multiple service types is to use a PriorityFlag parameter as detailed below.

[0126] An n-bit parameter PriorityFlag can be used to adjust the initial priority value in the SCI of the current side link transmission, where n≥1. The initial priority value of the side link service can be represented by a PPPP, a PPPR, or a CBR level indicator. The refined priority value in the SCI of a side link transmission can be obtained based on a PPPP from multiple higher layers minus the value of the PriorityFlag. A smaller PPPP value may represent a higher priority. In one embodiment, if n=2, each value of PriorityFlag indicates a degree of priority adjustment, as shown in the following formula:

[0127]

[0128] The parameter PriorityFlag, used as a priority offset, can be configured by multiple higher layers according to various service types.

[0129] The second option for redesigning the SCI to use multiple service types is to use a service type identifier in the SCI, as described below.

[0130] An n-bit parameter TrafficTypeIdentifier can be added as part of the SCI to indicate one of multiple service types. The number of service types can be configured by multiple higher layers. TrafficTypeIdentifier can be configured to be associated with TrafficType x, as shown in Table 11:

[0131] Table 11

[0132] TrafficTypeIdentifier Traffic Type 00 Traffic type1 01 Traffic type2 10 Traffic type3 ... ...

[0133] The mapping between a single TrafficType value x and the actual service type is configurable. For example, TrafficType 1 can correspond to unicast, Traffic Type 2 can correspond to multicast, and Traffic Type 3 can correspond to broadcast. As described in the above embodiments of the present invention, a priority can be assigned to each of the above service types in the SCI during the prioritization process.

[0134] The user equipment may use the service type information of a specific scenario to modify QoS management, such as QoS management for congestion control.

[0135] Figure 5 7 is a schematic diagram of a system 700 for wireless communication provided by an embodiment of the present invention. The embodiment of the present invention can apply any appropriately configured hardware and / or software to the system. Figure 5In the embodiment, the system 700 includes a radio frequency (RF) circuit 710, a baseband circuit 720, a processing unit 730, a memory / storage 740, a display 750, a camera 760, a sensor 770, and an input / output (I / O) interface 780 coupled to each other.

[0136] Processing unit 730 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processors may include any combination of general-purpose processors and specialized processors, such as a graphics processor and an application processor. The processors may be coupled to memory / storage and configured to execute instructions stored in the memory / storage to enable various applications and / or operating systems running on the system.

[0137] The baseband circuitry 720 may include circuitry, such as, but not limited to, one or more single-core or multi-core processors. The processor may include a baseband processor. The baseband circuitry may handle various wireless control functions that enable communication with one or more wireless networks via RF circuitry. The wireless control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency offset, etc. In some embodiments, the baseband circuitry may provide communications compatible with one or more wireless technologies. For example, in some embodiments, the baseband circuitry may support communication with 5G NR, LTE, Evolved Universal Terrestrial Radio Access Network (EUTRAN) and / or other Wireless Metropolitan Area Networks (WMANs), Wireless Local Area Networks (WLANs), and Wireless Personal Area Networks (WPANs). In some embodiments, a baseband circuitry configured to support wireless communications of at least one wireless protocol may be referred to as a multimode baseband circuitry. In various embodiments, the baseband circuitry 720 may include circuitry for operating on signals that are not strictly considered to be in the baseband frequency. For example, in some embodiments, baseband circuitry may include circuitry for operating on signals having an intermediate frequency that is between the baseband frequency and the radio frequency.

[0138] RF circuitry 710 can enable communication with a wireless network using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry can include switches, filters, amplifiers, and the like to facilitate communication with the wireless network. In various embodiments, the RF circuitry 710 can include circuitry for operating on signals not strictly considered radio frequencies. For example, in some embodiments, the RF circuitry can include circuitry for operating on signals having an intermediate frequency (IF) between baseband and RF.

[0139] In various embodiments, the transmitter circuitry, control circuitry, or receiver circuitry described herein for a UE, eNB, or gNB may be embodied in whole or in part in one or more of the RF circuitry, baseband circuitry, and / or RF circuitry. As used herein, "circuitry" may refer to, pertain to, or include an Application Specific Integrated Circuit (ASIC), electronic circuitry, a processor (shared, dedicated, or grouped), and / or memory (shared, dedicated, or grouped) to execute one or more software or firmware programs, combinatorial logic circuitry, and / or other suitable hardware components that provide the described functionality. In some embodiments, electronic device circuitry may be implemented in one or more software or firmware modules, or the functionality associated with the circuitry may be implemented by one or more software or firmware modules. In some embodiments, some or all of the components of the baseband circuitry, processing unit, and / or memory / storage may be implemented together on a System on a Chip (SOC).

[0140] Memory / storage 740 can be used for, for example, system, to load and store data and / or instructions.In one embodiment, memory / storage can include suitable volatile memory, such as dynamic random access memory (DRAM), and / or any combination of non-volatile memory (such as flash memory).In various embodiments, I / O interface 780 can include one or more user interfaces and / or peripheral component interfaces, and this user interface is designed to allow user to interact with system, and peripheral component interface is designed to allow peripheral component to interact with system.User interface can include but not limited to physical keyboard or keypad, touchpad, loudspeaker, microphone etc.Peripheral component interface can include but not limited to non-volatile memory port, universal serial bus (USB) port, audio jack and power interface.

[0141] In various embodiments, sensor 770 may include one or more sensing devices to determine environmental conditions and / or location information related to the system. In some embodiments, the sensors may include, but are not limited to, gyroscope sensors, accelerometers, proximity sensors, ambient light sensors, and positioning units. The positioning unit may also be part of or interact with baseband circuitry and / or RF circuitry to communicate with components of a positioning network, such as a Global Positioning System (GPS) satellite. In various embodiments, display 750 may include a display such as a liquid crystal display and a touch screen display. In various embodiments, system 700 may be a mobile computing device, such as, but not limited to, a laptop computer, a tablet computer, a netbook, an ultrabook, a smartphone, etc. In various embodiments, the system may have more or fewer components and / or a different architecture. Where appropriate, the methods provided in embodiments of the present invention may be implemented as computer programs. The computer programs may be stored on a storage medium, such as a non-transitory storage medium.

[0142] The embodiment of the present invention is a combination of techniques / processes that can be adopted in 3GPP specifications to create a final product.

[0143] It will be appreciated by those skilled in the art that the various units, algorithms, and steps described and disclosed in the embodiments of the present invention are implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether each function is run in hardware or software depends on the application conditions and the design requirements of the technical solution. Those skilled in the art may use different methods to implement the functions for each specific application, but such implementation should not exceed the scope of protection of the present invention. It will be appreciated by those skilled in the art that since the working processes of the above-mentioned systems, devices, and units are basically the same, reference may be made to the working processes of the systems, devices, and units in the above-mentioned embodiments. For ease of description and simplification, these working processes will not be described in detail.

[0144] It is understood that the systems, devices and methods disclosed in the embodiments of the present invention can be implemented in other ways, and the above embodiments are merely exemplary. The division of the above units is based solely on logical functions, and other divisions may exist in implementation. Multiple units or components may be combined or integrated into another system, and certain features may be omitted or skipped. On the other hand, the mutual coupling, direct coupling or communication coupling shown or discussed above is achieved through some ports, devices or units, whether indirectly or through electrical, mechanical or other types of communication.

[0145] Units described as separate components may or may not be physically separate. The units used for illustration may or may not be physical units, i.e., located in one location or distributed across multiple network units. Depending on the purpose of the embodiments of the present invention, some or all of the above-described units may be used. Furthermore, the various functional units in various embodiments may be integrated into a single processing unit, physically independent, or comprise two or more units integrated into a single processing unit.

[0146] If the software functional unit is used and sold as a product, it can be stored in a readable storage medium in a computer. Based on this understanding, the technical solution proposed in the present invention can be implemented basically or partially in the form of a software product. Alternatively, some technical solutions that are advantageous to the prior art can be implemented in the form of a software product. The software product in the computer is stored in a storage medium, which includes multiple commands for a computer device (such as a personal computer, server or network device) to run all or part of the steps disclosed in the embodiment of the present invention. The present disclosure. The storage medium includes a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a floppy disk or other medium capable of storing program code.

[0147] The method disclosed in the embodiment of the present invention provides flexible QoS management based on sidelink service type. According to the embodiment of the present invention, the sidelink transmission of each service type can have a configurable priority to meet different communication situations and QoS requirements.

[0148] Although the embodiments disclosed in the present invention have been considered to be the most practical and preferred embodiments, it should be understood that the embodiments of the present invention are not limited to the disclosed embodiments, but are intended to cover various arrangements made without departing from the scope of protection of the broadest interpretation of the appended claims.

Claims

1. A side link priority sorting method executable in a user equipment, characterized in that: include: receiving an initial priority value of a side link service, wherein the initial priority value of the side link service is represented by a short range communication data packet priority (PPPP), a short range communication data packet reliability (PPPR), or a combination of the PPPP and the PPPR; determining a service type of the sidelink channel, wherein the service type comprises at least one of unicast, multicast, and broadcast; and combining the initial priority value with the priority offset based on a priority offset corresponding to the traffic type of the sidelink service to generate a refined priority value for the sidelink service; Prioritizing the sidelink logical channels among the plurality of logical channels according to the refined priority value; The priority offset is determined based on the value of the configuration parameter CastTypeFlag. The value of CastTypeFlag is used to control whether to distinguish service types and whether to further distinguish the number of members in the multicast group. And the side link control information SCI of the user equipment carries the refined priority value and the identifier of the service type.

2. The method according to claim 1, characterized in that When the service type of the side link service is unicast, the priority offset is assigned a first value; when the service type of the side link service is multicast, the priority offset is assigned a second value; when the service type of the side link service is broadcast, the priority offset is assigned a third value.

3. The method according to claim 1, characterized in that The service type of the side link service is one of unicast and non-unicast, where the non-unicast service includes a multicast service type and a broadcast service type; when the service type of the side link service is unicast, the priority offset is assigned a unicast offset value; When the traffic type of the sidelink service is non-unicast, the priority offset is assigned a non-unicast offset value.

4. The method according to claim 3, characterized in that When the service type of the side link service is multicast, and the multicast is associated with a multicast group whose number of group members is not greater than a threshold, the priority offset is assigned a first multicast offset value; and when the service type of the side link service is multicast, and the multicast is associated with a multicast group whose number of group members is greater than the threshold, the priority offset is assigned a second multicast offset value.

5. The method according to claim 1, wherein The initial priority value of the sidelink service is a priority used in access stratum (AS), non-access stratum (NAS) or logical channel allocation.

6. The method according to claim 1, characterized in that The initial priority value of the side link service is represented by a channel busy rate CBR level indicator.

7. The method according to claim 6, characterized in that The service type of the side link service is one of multiple service types, and at least one of the parameters cbr-RangeCommonConfigList-r14 and cbr-ConfigIndex-r14 is obtained according to the number of the multiple service types.

8. The method according to claim 1, characterized in that The sidelink service is one of a plurality of sidelink logical channels, the plurality of sidelink logical channels belonging to a same selected close proximity service target address; the method further comprising: allocating resources to one of the plurality of sidelink logical channels having the highest priority in a particular traffic type selected from a plurality of traffic types associated with the plurality of sidelink logical channels; and According to the priority ranking of each service type in the plurality of service types, services are provided to the plurality of side link logical channels belonging to the same selected close range service target address until data or side link grants of the side link logical channels are exhausted.

9. A side link priority sorting method executable in a base station, characterized in that: include: receiving an initial priority value of a side link service, wherein the initial priority value of the side link service is represented by a short range communication data packet priority (PPPP), a short range communication data packet reliability (PPPR), or a combination of the PPPP and the PPPR; determining a service type of the sidelink channel, wherein the service type comprises at least one of unicast, multicast, and broadcast; Prioritizing the sidelink logical channels among the multiple logical channels according to the refined priority value; The priority offset is determined based on the value of the configuration parameter CastTypeFlag. The value of CastTypeFlag is used to control whether to distinguish between service types and whether to further distinguish between the number of members in the multicast group. and carrying the refined priority value and the identifier of the service type in the side link control information SCI of the user equipment; and The refined priority value is provided as part of sidelink control information SCI associated with the sidelink service.

10. The method according to claim 9, characterized in that Also includes: The refined priority value of the side link service is generated by subtracting a value of a parameter PriorityFlag from the initial priority value, wherein the parameter PriorityFlag is determined based on the service type.

11. The method according to claim 10, characterized in that The PriorityFlag is a priority adjustment degree expressed according to the following formula, where:

12. The method according to claim 9, characterized in that Also includes: An identification of the traffic type is provided as part of the SCI associated with the sidelink service.

13. The method according to claim 9, characterized in that The initial priority value of the sidelink service is a priority used in access stratum (AS), non-access stratum (NAS) or logical channel allocation.

14. The method according to claim 9, wherein The initial priority value of the side link service is represented by a channel busy rate CBR level indicator.

15. A user equipment, characterized in that: The device comprises a processor configured to perform the following steps: The initial priority value of the link service on the receiving side; determining a traffic type of the sidelink channel; and According to the traffic type of the side link service, a refined priority value of the side link service is generated based on the initial priority value.

16. The user equipment according to claim 15, characterized in that When the service type of the side link service is unicast, the priority offset is assigned a first value; when the service type of the side link service is multicast, the priority offset is assigned a second value; when the service type of the side link service is broadcast, the priority offset is assigned a third value.

17. The user equipment according to claim 15, wherein: The service type of the side link service is one of unicast and non-unicast, and the non-unicast includes a multicast service type and a broadcast service type; when the service type of the side link service is unicast, the priority offset is assigned a unicast offset value; when the service type of the side link service is non-unicast, the priority offset is assigned a non-unicast offset value.

18. The user equipment according to claim 17, wherein: When the service type of the side link service is multicast, and the multicast is associated with a multicast group whose number of group members is not greater than a threshold, the priority offset is assigned a first multicast offset value; and when the service type of the side link service is multicast, and the multicast is associated with a multicast group whose number of group members is greater than the threshold, the priority offset is assigned a second multicast offset value.

19. The user equipment according to claim 15, wherein: The initial priority value of the sidelink service is a priority used in access stratum (AS), non-access stratum (NAS) or logical channel allocation.

20. The user equipment according to claim 15, wherein: The initial priority value of the side link service is represented by a channel busy rate CBR level indicator.

21. The user equipment according to claim 20, wherein: The service type of the side link service is one of multiple service types, and at least one of the parameters cbr-RangeCommonConfigList-r14 and cbr-ConfigIndex-r14 is obtained according to the number of the multiple service types.

22. The user equipment according to claim 15, wherein: The sidelink service is one of a plurality of sidelink logical channels, the plurality of sidelink logical channels belonging to a same selected close proximity service target address; allocating resources to one of a plurality of sidelink logical channels having a highest priority in a particular service type, the particular service type being selected from a plurality of service types associated with the plurality of sidelink logical channels; as well as According to the priority ranking of each service type in the plurality of service types, services are provided to the plurality of side link logical channels belonging to the same selected close range service target address until data or side link grants of the side link logical channels are exhausted.

23. A base station, characterized in that: The device comprises a processor configured to perform the following steps: receiving an initial priority value of a side link service, wherein the initial priority value of the side link service is represented by a short range communication data packet priority (PPPP), a short range communication data packet reliability (PPPR), or a combination of the PPPP and the PPPR; determining a service type of the sidelink channel, wherein the service type comprises at least one of unicast, multicast, and broadcast; combining the initial priority value with the priority offset based on a priority offset corresponding to the traffic type of the sidelink service to generate a refined priority value for the sidelink service; Prioritizing the sidelink logical channels among the plurality of logical channels according to the refined priority value; The priority offset is determined based on the value of the configuration parameter CastTypeFlag. The value of CastTypeFlag is used to control whether to distinguish service types and whether to further distinguish the number of members in the multicast group. and carrying the refined priority value and the identifier of the service type in the side link control information SCI of the user equipment; and The refined priority value is provided as part of sidelink control information SCI associated with the sidelink service.

24. The base station according to claim 23, characterized in that The steps also include: The refined priority value of the side link service is generated by subtracting a value of a parameter PriorityFlag from the initial priority value, wherein the parameter PriorityFlag is determined based on the service type.

25. The base station according to claim 24, characterized in that The PriorityFlag is a priority adjustment degree expressed according to the following formula, where:

26. The base station according to claim 23, wherein The steps also include: An identification of the traffic type is provided as part of the SCI associated with the sidelink service.

27. The base station according to claim 23, wherein The initial priority value of the sidelink service is a priority used in access stratum (AS), non-access stratum (NAS) or logical channel allocation.

28. The base station according to claim 23, wherein The initial priority value of the side link service is represented by a channel busy rate CBR level indicator.

Images