UE information reporting method, vehicle network resource configuration method and device

Abstract

This application proposes a method for reporting UE information, a method and apparatus for configuring Internet of Vehicles resources, and a storage medium. The method includes: a first user equipment (UE) obtaining identification information of a second UE; and the first UE sending the second UE's identification information before and after adjustment to a network element device on the network side to report the UE information. This application implements UE information reporting and resource configuration processing based on a 5G sidelink.

Description

Technical Field

[0001] The present application relates to a wireless communication network, and specifically to a method for reporting UE information, a method and device for configuring vehicle network resources, and a storage medium. Background Art

[0002] The Internet of Vehicles (IoV) refers to a system network constructed according to agreed communication protocols and data exchange standards. Communications based on the IoV are collectively referred to as vehicle-to-external information exchange (V2X) communications. V2X enables wireless communication and information exchange between vehicles, vehicles and pedestrians, vehicles and roadside equipment, and the Internet. With technological advancements and the development of the automation industry, V2X communication scenarios have been extended from the 3rd Generation Partnership Project (3GPP) organization for the standardization of third-generation mobile communications to 5G and have higher performance requirements. Currently, there is no UE information reporting and resource allocation solution based on 5G sidelink for IoV communications based on 5G radio (NR) and 5G sidelink. Summary of the Invention

[0003] The present application provides a method for reporting user information (UE) information, a method and device for configuring vehicle network resources, and a storage medium.

[0004] This embodiment of the present application provides a method for reporting UE information, including:

[0005] The first UE obtains identification information of the second UE;

[0006] The first UE sends the identification information of the second UE before adjustment and the identification information after adjustment to the network element device on the network side to report UE information.

[0007] The present invention provides a method for applying for Internet of Vehicles resources, the method comprising:

[0008] The first UE obtains layer 2 identification information of the second UE;

[0009] Determining, by the first UE, identification information of the second UE;

[0010] The first UE sends the identification information of the second UE to the network element device on the network side to apply for resource configuration.

[0011] The present invention provides a method for configuring Internet of Vehicles resources, the method comprising:

[0012] The UE receives the sidelink bearer configuration information configured by the network element device on the network side;

[0013] The bearer configuration information includes at least one of target identification information, target UE information, and transmission type information.

[0014] An embodiment of the present application provides a method for a medium access control (MAC) entity to process a logical channel priority, the method comprising:

[0015] The logical channel priorities are sorted in descending order as follows:

[0016] MAC control element for the Cell Radio Network Temporary Identity (C-RNTI) or data from the Uplink Common Control Channel (UL-CCCH);

[0017] MAC control unit for sidelink retransmission buffer status report (BSR);

[0018] A MAC control unit for a sidelink BSR, wherein the sidelink BSR includes: a sidelink BSR excluding a sidelink BSR for padding.

[0019] An embodiment of the present application provides a method for a MAC entity to process logical channel priorities, the method comprising:

[0020] For a retransmitted BSR, the MAC entity uses the priority of the logical channel with the highest priority included in the transport block corresponding to the retransmitted BSR as the priority of the retransmitted BSR;

[0021] For a sidelink BSR, the MAC entity uses the priority of the logical channel with the highest priority included in the sidelink BSR as the priority of the sidelink BSR.

[0022] The present invention provides a method for configuring Internet of Vehicles resources, the method comprising:

[0023] The UE receives configuration grant configuration information;

[0024] The UE sends data using the configure grant configuration information;

[0025] The configure grant configuration information includes at least one of target identification information, target UE information, and transmission type information.

[0026] The present invention provides a method for configuring Internet of Vehicles resources, the method comprising:

[0027] The UE receives HARQ Process ID list information;

[0028] The UE determines a HARQ Process ID according to the HARQ Process ID list;

[0029] The HARQ Process ID list indicates the HARQ Process ID list under the resource allocation mode that can be used by the UE to select transmission resources.

[0030] The present invention provides a method for configuring Internet of Vehicles resources, the method comprising:

[0031] The first UE obtains information about UEs in the sidelink multicast communication group;

[0032] The first UE determines the sidelink feedback channel (PSFCH, Physical sidelink Feedback channel) resource information of the UE in the sidelink multicast communication group.

[0033] An embodiment of the present application provides a device for reporting UE information, the device comprising:

[0034] A first acquisition module, configured to acquire identification information of a second UE;

[0035] The first sending module is used to send the identification information of the second UE before adjustment and the identification information after adjustment to the network element device on the network side to report UE information.

[0036] An embodiment of the present application provides a vehicle networking resource application device, the device comprising:

[0037] A second acquisition module, configured to acquire layer 2 identification information of a second UE;

[0038] A first determining module, configured to determine identification information of a second UE;

[0039] The second sending module is used to send the identification information of the second UE to the network element device on the network side to apply for resource configuration.

[0040] An embodiment of the present application provides a vehicle network resource configuration device, the device comprising:

[0041] A first receiving module is used for sidelink bearer configuration information configured by a network element device on the network side;

[0042] The bearer configuration information includes at least one of target identification information, target UE information, and transmission type information.

[0043] An embodiment of the present application provides a device for a MAC entity to process logical channel priorities. The device includes a first priority sorting module configured to:

[0044] The logical channel priorities are sorted in descending order as follows:

[0045] MAC control element for the cell C-RNTI or data from the UL-CCCH;

[0046] MAC control unit for sidelink retransmission BSR;

[0047] A MAC control unit for a sidelink BSR, wherein the sidelink BSR includes: a sidelink BSR excluding a sidelink BSR for padding.

[0048] An embodiment of the present application provides a device for a MAC entity to process logical channel priorities, the device including a second priority sorting module, configured to:

[0049] For a retransmitted BSR, the MAC entity uses the priority of the logical channel with the highest priority included in the transport block corresponding to the retransmitted BSR as the priority of the retransmitted BSR;

[0050] For a sidelink BSR, the MAC entity uses the priority of the logical channel with the highest priority included in the sidelink BSR as the priority of the sidelink BSR.

[0051] An embodiment of the present application provides a vehicle network resource configuration device, the device comprising:

[0052] The second receiving module is used to receive configure grant configuration information;

[0053] The UE sends data using the configure grant configuration information;

[0054] The configure grant configuration information includes at least one of target identification information, target UE information, and transmission type information.

[0055] An embodiment of the present application provides a vehicle network resource configuration device, the device comprising:

[0056] A third receiving module is used to receive HARQ Process ID list information;

[0057] A second determining module, configured to determine a HARQ Process ID according to the HARQ Process ID list;

[0058] The HARQ Process ID list indicates the HARQ Process ID list under the resource allocation mode that can be used by the UE to select transmission resources.

[0059] An embodiment of the present application provides a vehicle network resource configuration device, the device comprising:

[0060] The third acquisition module is used to obtain information about UEs in the sidelink multicast communication group;

[0061] The third determining module is used to determine the PSFCH resource information of the UE in the sidelink multicast communication group.

[0062] An embodiment of the present application provides a storage medium storing a computer program. When the computer program is executed by a processor, any one of the UE information reporting method and the vehicle network resource configuration method in the embodiment of the present application is implemented.

[0063] Using this application, the first user equipment UE obtains the identification information of the second UE; the first UE sends the identification information of the second UE before adjustment and the identification information after adjustment to the network element device on the network side to report the UE information, thereby realizing the reporting of UE information based on 5G sidelink.

[0064] With respect to the above embodiments and other aspects of the present application and their implementation, further description is provided in the accompanying drawings, detailed description and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0065] Figure 1 This is a schematic diagram of the scenario of the Internet of Vehicles architecture according to an embodiment of the present application;

[0066] Figure 2 Schematic diagram of the UE information reporting method of the embodiment of the present application Figure 1 ;

[0067] Figure 3 This is a schematic diagram of the process of applying for Internet of Vehicles resources in this embodiment of the application Figure 1 ;

[0068] Figure 4 This is a schematic diagram of the process of configuring the Internet of Vehicles resources according to the embodiment of the present application. Figure 1 ;

[0069] Figure 5 This is a schematic diagram of the process of configuring the Internet of Vehicles resources according to the embodiment of the present application. Figure 2 ;

[0070] Figure 6 This is a schematic diagram of the process of configuring the Internet of Vehicles resources according to the embodiment of the present application. Figure 3 ;

[0071] Figure 7 The frame of the UE information reporting device of the embodiment of the present application Figure 1 ;

[0072] Figure 8 Hardware diagram of the reporting device for this application embodiment Figure 1 ;

[0073] Figure 9 This is a schematic diagram of the structure of an embodiment of the present application in which the reporting device is located in a terminal device;

[0074] Figure 10-11 Two schematic diagrams of the communication system structure provided in the embodiments of the present application. DETAILED DESCRIPTION

[0075] To make the purpose, technical solutions and advantages of this application more clear, the embodiments of this application will be described in detail below with reference to the accompanying drawings. It should be noted that, unless there is a conflict, the embodiments and features in the embodiments of this application can be combined with each other in any way.

[0076] The Internet of Vehicles refers to a large-scale system network that conducts wireless communication and information exchange between vehicles, pedestrians, roadside equipment and the Internet in accordance with agreed communication protocols and data interaction standards. Through Internet of Vehicles communication, vehicles can achieve driving safety, improve traffic efficiency, and obtain convenient or entertainment information. Classified by the objects of wireless communication, Internet of Vehicles communication includes three different types: vehicle-to-vehicle communication (V2V), vehicle-to-infrastructure / vehicle-to-network communication (V2I / V2N), and vehicle-to-pedestrian communication (V2P), collectively referred to as V2X communication. In the 3GPP organization's V2X communication research based on Long Term Evolution (LTE), the V2X communication method based on direct / sidelink links between UEs is one of the ways to implement the V2X standard, that is, the service data is not forwarded by the base station and the core network, but is directly transmitted from the source user equipment to the target user equipment through the air interface, such as Figure 1 As shown, Figure 1 This is a schematic diagram of the scenario of the Internet of Vehicles architecture of the embodiment of this application. Figure 1As shown, the way in which each UE in the Internet of Vehicles architecture communicates through Sidelink can be a V2X communication way, referred to as PC5-based V2X communication or V2X sidelink communication.

[0077] With the advancement of technology and the development of the automation industry, V2X communication scenarios have been further extended and have higher performance requirements. Advanced V2X services are mainly divided into four categories: vehicle platooning, extended sensors, advanced driving (semi-automated or fully-automated driving), and remote driving. The required performance requirements are: data packet size supports 50 to 12,000 bytes, transmission rate 2 to 50 messages per second, maximum end-to-end delay 3-500 milliseconds, reliability 90%-99.999%, data rate 0.5-1000Mbps, and transmission range supports 50-1000 meters. 3GPP has launched a project to study vehicle-to-vehicle communication based on the fifth generation mobile communication technology (5G, 5th Generation), including vehicle-to-vehicle communication based on 5G air interface and vehicle-to-vehicle communication based on 5G sidelink. In this regard, the embodiment of the present application proposes a resource configuration solution based on 5G direct link.

[0078] Figure 2 Schematic diagram of the UE information reporting method of the embodiment of the present application Figure 1 ,like Figure 2 Shown, including:

[0079] S101. A first UE obtains identification information of a second UE;

[0080] S102. The first UE sends the identification information of the second UE before adjustment and the identification information after adjustment to a network element device on the network side to report UE information.

[0081] In an exemplary embodiment, the identification information of the second UE includes layer 2 identification information of the UE.

[0082] Figure 3 This is a schematic diagram of the process of applying for Internet of Vehicles resources in this embodiment of the application Figure 1 ,like Figure 3 Shown, including:

[0083] S201. A first UE obtains layer 2 identification information of a second UE.

[0084] S202. The first UE determines identification information of a second UE.

[0085] S203. The first UE sends identification information of the second UE to a network element device on the network side to apply for resource configuration.

[0086] In an exemplary embodiment, the first UE determining the identification information of the second UE includes:

[0087] The first UE uses the layer 2 identification information of the second UE as the identification information of the second UE; or, the first UE allocates UE identification information to the second UE.

[0088] In one exemplary embodiment, in one case, the method further includes: after the first UE obtains the layer 2 identification information of the second UE, the first UE uses the layer 2 identification information of the second UE as the identification of the second UE. In another case, the method further includes: after the first UE establishes a connection with the second UE, using the layer 2 identification information of the second UE obtained for the first time as the identification of the second UE.

[0089] The first UE receives the layer 2 identification information of the second UE again, the first UE associates the received layer 2 identification information of the second UE with the identification of the second UE, and updates the layer 2 identification information of the second UE according to the received layer 2 identification information of the second UE.

[0090] The method for configuring Internet of Vehicles resources in an embodiment of the present application includes:

[0091] S301. A UE receives sidelink bearer configuration information configured by a network element device on the network side.

[0092] The bearer configuration information includes at least one of target identification information, target UE information, and transmission type information.

[0093] In an exemplary embodiment, the transmission type information includes at least one of unicast, multicast, and broadcast.

[0094] In an exemplary embodiment, the UE receiving sidelink bearer configuration information configured by a network element device on the network side includes: the UE receiving Service Data Protocol (SDAP) layer configuration information. The SDAP layer configuration information includes: at least one of target identification information, target UE information, and transmission type information.

[0095] In an exemplary embodiment, the transmission type information includes at least one of unicast, multicast, and broadcast.

[0096] The method for a MAC entity to process logical channel priorities in an embodiment of the present application includes:

[0097] S401. Sort the priorities of logical channels in descending order of priority as follows.

[0098] In descending order of priority they include:

[0099] MAC control element for the cell C-RNTI or data from the UL-CCCH;

[0100] MAC control unit for sidelink retransmission BSR;

[0101] A MAC control unit for a sidelink BSR, wherein the sidelink BSR includes: a sidelink BSR excluding a sidelink BSR for padding.

[0102] In one exemplary embodiment, the descending priority order further comprises:

[0103] MAC control element for the cell C-RNTI or data from the UL-CCCH;

[0104] A MAC control element for a sidelink BSR, wherein the sidelink BSR includes: a sidelink BSR other than a sidelink BSR for padding;

[0105] MAC control unit for sidelink retransmission BSR.

[0106] The method for a MAC entity to process logical channel priorities in an embodiment of the present application includes:

[0107] For a retransmitted BSR, the MAC entity uses the priority of the logical channel with the highest priority included in the transport block corresponding to the retransmitted BSR as the priority of the retransmitted BSR;

[0108] For a sidelink BSR, the MAC entity uses the priority of the logical channel with the highest priority included in the sidelink BSR as the priority of the sidelink BSR.

[0109] Figure 4 This is a schematic diagram of the process of configuring the Internet of Vehicles resources according to the embodiment of the present application. Figure 1 ,like Figure 4 Shown, including:

[0110] S501, UE receives configuration grant configuration information;

[0111] S502: The UE sends data using the configure grant configuration information.

[0112] The configure grant configuration information includes at least one of target identification information, target UE information, and transmission type information.

[0113] In an exemplary embodiment, the transmission type information includes at least one of unicast, multicast, and broadcast.

[0114] In an exemplary embodiment, the configure grant configuration information further includes: indication information of whether transmission of retransmission packets is supported.

[0115] In an exemplary embodiment, if the configure grant configuration information indicates that transmission of retransmission packets is supported, then when no new transmission packets arrive at the resource location indicated by the configured grant configuration, it can be used to send retransmission data packets.

[0116] Figure 5 This is a schematic diagram of the process of configuring the Internet of Vehicles resources according to the embodiment of the present application. Figure 2 ,like Figure 5 Shown, including:

[0117] S601. UE receives HARQ Process ID list information;

[0118] S602. The UE determines a HARQ Process ID according to the HARQ Process ID list.

[0119] The HARQ Process ID list indicates the HARQ Process ID list under the resource allocation mode that can be used by the UE to select transmission resources.

[0120] In an exemplary embodiment, the HARQ Process ID list information is carried in a system message or in a dedicated radio resource control (RRC) signaling.

[0121] In an exemplary embodiment, the HARQ Process ID list information may also be carried through sidelink resource pool configuration information.

[0122] In an exemplary embodiment, the UE includes: a UE that supports both network-side network element device scheduling and UE selection of transmission resources.

[0123] Figure 6 This is a schematic diagram of the process of configuring the Internet of Vehicles resources according to the embodiment of the present application. Figure 3 ,like Figure 6 Shown, including:

[0124] S701. A first UE obtains information about UEs in a sidelink multicast communication group.

[0125] S702. The first UE determines PSFCH resource information of UEs in a sidelink multicast communication group.

[0126] In an exemplary embodiment, the method further includes: after the first UE obtains the information of the UEs in the sidelink multicast communication group, the first UE sends the information of the UEs in the sidelink multicast communication group to the network element device on the network side; the first UE receives the PSFCH resource information of the UEs in the group.

[0127] In an exemplary embodiment, the PSFCH resource information includes: a PSFCH resource pool or N PSFCH resources, where N is the number of receiving UEs in a group or the number of receiving UE groups / categories.

[0128] In an exemplary embodiment, the information of the UEs in the group includes: identification information of the UEs in the group, quantity information of the UEs in the group, or category identification information of the UEs in the group.

[0129] In an exemplary embodiment, the method for obtaining the identification information of the UE in the group includes:

[0130] Notifying the identity of the UE in the access stratum (AS) layer group via the non-access stratum (NAS) layer of the UE; or:

[0131] The UE establishes a connection with the UEs in the group to obtain identification information of the UEs in the group.

[0132] In an exemplary embodiment, the method for obtaining the number information of UEs in the group includes: notifying the AS layer of the number of UEs in the group through the NAS layer of the UE; or obtaining the number information of UEs in the group through the UE establishing a connection with the UEs in the group.

[0133] In an exemplary embodiment, the method for obtaining the category identification information of the UE in the group includes: notifying the AS layer of the category identification of the UE in the group through the NAS layer of the UE; or establishing a connection between the UE and the UE in the group to obtain the category identification of the UE in the group.

[0134] In an exemplary embodiment, the method further comprises:

[0135] The first UE obtains PSFCH resource pool information;

[0136] The first UE determines PSFCH resource information of UEs in the group, including:

[0137] The first UE determines the PSFCH resource information of the UEs in the group according to the information of the UEs in the group and the PSFCH resource pool information.

[0138] In an exemplary embodiment, the method further includes: after the first UE determines the PSFCH resource information of the UEs in the group, the first UE sends the PSFCH resource information to the second UE.

[0139] In an exemplary embodiment, the method further includes: the first UE carries the PSFCH resource information of all UEs in the group through (SCI, sidelink control information); the PSFCH resource information of the UEs in the group includes: the identifier of the UE in the group and the PSFCH resources corresponding to the identifier; or: the category identifier of the UE in the group and the PSFCH resources corresponding to the category identifier.

[0140] In an exemplary embodiment, the PSFCH resource information of the UE in the group may also include a PSFCH resource list. For example, if there are eight receiving UEs and the SCI carries eight resources, then the receiving UE identified as 1 uses the first resource, the one identified as 2 uses the second resource, and so on.

[0141] In an exemplary embodiment, the PSFCH resource information of the UE in the group may also include a PSFCH resource list. For example, there are eight categories of receiving UEs, and the SCI carries eight resources. Then, the receiving UE category identified as 1 uses the first resource, the category identified as 2 uses the second resource, and so on.

[0142] Application examples:

[0143] The research scope of NR V2X includes sidelink unicast, sidelink multicast, and sidelink broadcast. Generally speaking, sidelink V2X communication can be categorized into unicast, multicast, and broadcast. It should be noted that sidelink unicast communication typically requires two UEs performing unicast communication to first discover each other before initiating unicast-based sidelink V2X communication. Generally speaking, sidelink discovery is also based on broadcast transmission. In this disclosure, sidelink broadcast refers broadly to both sidelink broadcast communication and sidelink discovery.

[0144] Example 1:

[0145] The base station needs to allocate sidelink resources to the UE. The general process is as follows:

[0146] The UE first reports the sidelink UE information. If only broadcast and multicast are considered, the sidelink UE information includes:

[0147]

[0148] However, after the introduction of unicast, since the receiving UE's layer 2 ID is generated by itself and often changes, if the layer 2 UE ID changes, how to report it to the base station? The present invention proposes the following solution:

[0149] When the sending UE learns that the layer 2 ID of the receiving UE has changed, it reports a new destination ID list, or reports the destination ID list through add and remove to save signaling. After the base station receives the information, it uses the new destination ID when sending SLRB configuration information subsequently.

[0150] When the sending UE establishes a connection with the receiving UE, the layer 2 ID information of the receiving UE is obtained and used as the ID of the receiving UE. Alternatively, the sending UE assigns a UE ID to the receiving UE performing unicast communication, saves it locally, and subsequently reports the ID as the ID of the receiving UE to the base station. Changes in the layer 2 ID of the receiving UE do not affect changes in the ID of the receiving UE.

[0151] The sending UE informs the base station of the destination ID before and after the update. After receiving the information, the base station uses the new destination ID when sending SLRB configuration information subsequently. However, if only the destination ID in the configuration changes and other parameters remain unchanged, there is no need to send the updated SLRB configuration.

[0152] For NR V2X, in addition to reporting the SL-DestinationInfoList information, it is also necessary to indicate the cast type corresponding to the destination ID and, optionally, the RAT information corresponding to the destination ID. Furthermore, it is also necessary to indicate the QoS information corresponding to the destination ID.

[0153] After obtaining the above information, the base station can configure SL RB for the UE, similar to configuring DRB of the Uu interface, and configure SDAP, PDCP, and each RLC bearer, logical channel, etc. of each SL DRB respectively.

[0154] In Uu, UE configures SDAP based on different PDU-SessionIDs respectively, while for NR V2X, it is necessary to distinguish different destination IDs. Therefore, it is possible to consider configuring SDAP based on different destination IDs. All configured instances of SDAP-Config with the same value of destination ID correspond to the same SDAP entity.

[0155] Therefore, the destination ID is included in the SDAP-Config configuration IE or in the DRB-ToAddMod IE.

[0156] Alternatively, you can directly list the unicast, multicast, and broadcast destination ID lists in sequence and configure SL DRBs based on each destination ID.

[0157] Based on the QoS (QFI) information corresponding to each destination ID reported by the UE, the base station configures the corresponding DRB list for the UE. Then, based on the SDAP configuration information, the destination ID corresponding to each DRB ID can be determined, thereby determining its corresponding cast type and corresponding QFI. Through the configuration of RLC-BearerConfig, the SL logical channel ID is associated with the DRB ID. In other words, one destination ID may correspond to multiple DRBs and LCIDs, but each DRB and LCID can only correspond to one destination ID.

[0158] Example 2

[0159] For sidelink UEs, a new BSR is introduced based on retransmission resource request: sidelink retransmission BSR.

[0160] The content of the retransmitted BSR includes: 1 or more HARQ process ids

[0161] Retransmission BSR triggering condition: receiving NACK sent by the receiving UE

[0162] The cancel condition for retransmitting a BSR includes any of the following:

[0163] If any HARQ process ID of the MAC entity has no data available for retransmission, the triggered Sidelink Retx BSR should be canceled.

[0164] If a HARQ process ID of the MAC entity has no data available for retransmission, the Sidelink Retx BSR associated with the process should be canceled.

[0165] When a Sidelink Retx BSR is transmitted in a MAC PDU, the Sidelink Retx BSR shall be cancelled.

[0166] When the upper layer configures autonomous resource selection, all triggered Sidelink Retx BSRs should be canceled.

[0167] Further:

[0168] The logical channel priority of the sidelink retransmitted BSR needs to be considered, including the following two methods:

[0169] 1) It is stipulated that the priority of the sidelink retransmission BSR is higher than that of the sidelink BSR.

[0170] 2) For a retransmitted transport block, the MAC entity needs to identify the highest-priority logical channel among the logical channels it contains. The priority of the highest-priority logical channel in the transport block then represents the priority of the transport block, and thus the priority of the sidelink retransmission BSR. The priority is then compared with the sidelink BSR.

[0171] Example 3

[0172] If the configure grant is allocated to a broadcast service, no corresponding ACK / NACK resources are allocated. If a unicast service uses it, additional ACK / NACK resources need to be requested, which is more complicated. Therefore, we propose that the base station carry the available cast type information in the configure grant configuration.

[0173] Furthermore, the base station can configure each configure grant to determine whether it supports the transmission of retransmitted transport blocks. If supported, the configure grant can be used to transmit the configure grant. The UE needs to determine whether to transmit a new data packet or a retransmitted data packet based on the configure grant, thereby determining its HARQ process ID. If the high-priority LCID of the configure grant is restricted, then when the data packet of this LCID does not arrive, which one has higher priority, the retransmitted data packet or the new data packet of the low-priority LCID? The priority is determined based on the highest priority or the latency requirement.

[0174] Example 4

[0175] The HARQ Process ID is calculated based on the symbol position of the configured grant resource. According to the agreed calculation formula, both the base station and the UE can determine the HARQ Process ID. For V2X configured grant, the HARQ Process ID can also be calculated in a similar way. For the dynamic scheduling of PC5, the HARQ Process ID can also be allocated by the base station. In order to distinguish different processes, the sending UE needs to carry the HARQ Process ID in the SCI. In addition, if the UE supports both base station scheduling (mode1) and UE selection of transmission resources (mode2) modes, since the HARQ Process ID of mode2 is determined by the UE itself, in order to avoid conflicts with the HARQ Process ID allocated by the base station dynamic scheduling, it is necessary to negotiate with the base station, for example, the base station allocates a HARQ Process ID list dedicated to mode2.

[0176] Example 5

[0177] For multicast, if you need to configure different PSFCHs or PSFCH pools based on different UEs, you can consider the following solutions:

[0178] For dynamic scheduling, after receiving the BSR, the base station determines whether the requested resources are for unicast, multicast or broadcast. If it is for multicast, it is necessary to further determine the number of receiving UEs, determine to divide the receiving UEs into N groups, and then allocate resources for transmitting data and N groups of ACK / NACK resources. For each multicast destination id, the number of receiving UEs or the classification level of the receiving UE is reported through the sidelink UE information. For configured grant scheduling, the base station allocates resources based on UE auxiliary information. After the sending UE receives N groups of ACK / NACK resources and carries the ACK / NACK resource location through SCI, the receiving UE decides which receiving UE uses which ACK / NACK resource based on the resource pool, or the sending UE determines the ACK / NACK resource location of each receiving UE and indicates it through SCI (one by one).

[0179] For multicast, if different PSFCHs need to be configured for different UEs, that is, for multicast, each receiving UE needs to be allocated different PSFCH resources, then the base station needs to know the number of PSFCH resources that need to be allocated when allocating resources (the UE reports through sidelink UE information). The specific PSFCH resource used by which receiving UE can be determined by the base station or the sending UE, and then the PSFCH resource information is carried through SCI signaling to indicate the PSFCH resources of the receiving UE of each destination ID.

[0180] So, how does the sending UE know which receiving UEs are in the group and their identifiers? 1) The NAS layer notifies the AS layer; 2) A unicast connection is established with all UEs in the group in advance to exchange information such as UE identifiers and PSFCH resources, but multicast messages are still sent via multicast. If the sending UE establishes a unicast connection with all UEs in the group, then each receiving UE can be assigned an intra-group identifier when the connection is established. Then, when the sending UE sends a data packet, it carries N PSFCH resource information in the SCI. The receiving UE determines which PSFCH resource to use based on its own identifier. (For example, if there are eight receiving UEs and the SCI carries eight resources, then the receiving UE with identifier 1 uses the first resource, and the receiving UE with identifier 2 uses the second resource.)

[0181] Example 6

[0182] For sidelink resource allocation, the purpose of introducing the exceptional resource pool is to maintain the continuity of sidelink transmission. When there is a possibility of interruption, the UE will use the exceptional resource pool to randomly select resources for use. Specifically, it can be divided into the following situations:

[0183] The gNB configures the UE to use mode 1 dynamic resource allocation:

[0184] If the UE detects RLF, the UE cannot receive SL grant from the base station. During this period, the UE can use the abnormal resource pool for random resource selection.

[0185] The gNB configures the UE to use mode 1 dynamic resource allocation. The gNB also configures type 1 configured grant.

[0186] If the UE detects RLF, the UE cannot receive the dynamic SL grant from the base station. The following two situations can be considered:

[0187] Assuming that a Type 1 configured grant is configured to allow the use of an SL logical channel, the UE can continue to use the Type 1 configured grant to schedule the associated SL logical channel. For other SL logical channels, it can consider using the exception resource pool to randomly select resources for sidelink transmission. It should be noted that this means that the UE uses two modes at the same time, namely Mode 1 corresponding to the Type 1 configured grant and Mode 2 corresponding to autonomous resource selection from the exception resource pool.

[0188] If a Type 1 configured grant does not specify an SLlogical channel that allows it, the UE can consider temporarily using the Type 1 configured grant to transmit all data packets. It should be noted that Type 1 configured grant resources are limited and periodic, and may not necessarily meet the UE's buffered data volume and transmission latency requirements. If the UE is allowed to use the exception resource pool simultaneously to transmit data with higher latency requirements or to carry some data traffic, it means that the UE will need to use both modes simultaneously.

[0189] The gNB configures the UE to use mode 1 dynamic resource allocation. The gNB also configures type 2 configured grant.

[0190] If the UE detects RLF and cannot receive an SL grant from the base station, the following situations may apply:

[0191] For a UE with type 2 SPS activated, if RLF is detected, consider continuing to use the SPS grant to transmit data on the logical channel corresponding to the traffic pattern. The problem with this approach is that during the RLF period, the base station may deactivate the SPS grant and allocate the original SPS resources to other UEs, resulting in conflicts.

[0192] For a UE with type 2 SPS activated, if an RLF is detected, consider continuing to use the SPS grant to transmit data for the logical channel corresponding to the traffic pattern. Data for other logical channels is transmitted using resources from the exception resource pool. The problem with this approach is that during the RLF period, the base station may deactivate the SPS grant and allocate the original SPS resources to other UEs, resulting in conflicts. Furthermore, this means that the UE needs to use both modes simultaneously.

[0193] For a UE with type 2 SPS activated, if RLF is detected, consider continuing to use the SPS pattern to transmit data on all logical channels. The problem with this approach is that during the RLF period, the base station may deactivate the SPS grant and allocate the original SPS resources to other UEs, resulting in conflicts.

[0194] For a UE with type 2 SPS activated, if RLF is detected, it switches to using the abnormal resource pool for all logical channel data transmission. This is the current approach used by LTE V2X, which uses a mode switch to solve the problem.

[0195] Proposal 1: If both mode 1 and mode 2 are not considered, if the UE experiences RLF, either allow the UE to use the type 1 configured grant to transmit data on all logical channels, or directly switch to the abnormal resource pool for data transmission.

[0196] Proposal 2: If both mode 1 and mode 2 are configured, then if RLF occurs in the UE, the UE can transfer all data of the logical channels corresponding to mode 1 to the mode 2 resource pool with available sensing results for transmission. Only when the sensing result of the mode 2 resource pool is not available, will the data be transferred to the abnormal resource pool for transmission.

[0197] The resource allocation method configured by the gNB for the UE changes;

[0198] There are several possibilities for changes in resource allocation:

[0199] From mode 1 to mode 2: This method may cause the sensing results of the mode 2 resource pool to be unavailable, so the UE needs to temporarily use the abnormal resource pool;

[0200] From mode 2 to mode 1: In this mode, the UE can directly request resources from the base station without using the exception resource pool;

[0201] From Mode 1 to Mode 1+Mode 2: In this mode, if the configured resource allocation mode is not associated with a logical channel / logical channel group, the UE can continue to use Mode 1 until the sensing result of the Mode 2 resource pool is available, and then transmit data on some logical channels / logical channel groups through the Mode 2 resource pool. If the configured resource allocation mode is associated with a logical channel / logical channel group, the UE can temporarily use the abnormal resource pool or use Mode 1 resource allocation to transmit data packets on the logical channels / logical channel groups associated with Mode 2 resource allocation.

[0202] From mode 2 to mode 1 + mode 2: In this mode, the UE can directly request grant from the base station for mode 1 data transmission based on the base station configuration or by selecting some logical channels / logical channel groups by itself, without using the abnormal resource pool.

[0203] From mode 1+mode 2 to mode 1: In this mode, the UE can directly request resources from the base station without using the abnormal resource pool;

[0204] From mode 1+mode 2 to mode 2: In this mode, the UE can directly transmit data packets of all logical channels / logical channel groups through mode 2 without using the exception resource pool;

[0205] The mode 2 resource pool configured by the base station changes (such as D, F): In this case, the UE needs to sense the new mode 2 resource pool. Before the sensing result is available, for D, the UE can temporarily use mode 1 resources for all data transmission or use the abnormal resource pool for data transmission of the logical channel / logical channel group associated with mode 2; for F, the UE can use the abnormal resource pool for data transmission.

[0206] It should be noted that if a Mode 2 UE is allowed to select multiple Mode 2 resource pools for data transmission, the availability of sensing results must also be considered. If no sensing results are available in all selected resource pools, the UE can first use the abnormal resource pool. If sensing results are available in one or more resource pools, the UE can use those resource pools.

[0207] The gNB configures both mode 1 resource allocation and mode 2 resource allocation for the UE

[0208] In this mode, if the configured resource allocation mode is not associated with a logical channel / logical channel group, the UE can first use Mode 1 until the sensing result of the Mode 2 resource pool is available, and then transmit data on some logical channels / logical channel groups through the Mode 2 resource pool. If the configured resource allocation mode is associated with a logical channel / logical channel group, the UE can temporarily use the abnormal resource pool or use Mode 1 resource allocation to transmit data packets on the logical channels / logical channel groups associated with Mode 2 resource allocation.

[0209] Proposal 3: In non-RLF scenarios, NR V2X still needs to consider the situation where the sensing result of the mode 2 resource pool is unavailable under the normal resource mode configuration. When this happens, the following methods can be considered: 1) use the abnormal resource pool; 2) temporarily use the mode 1 resource allocation method to transmit all data (requires the base station to configure multiple modes at the same time, and the base station does not configure the association between the resource allocation mode and the logical channel / logical channel group).

[0210] When the UE switches or configures a new SCell

[0211] NR V2X can refer to the methods mentioned in LTE V2X. For example, the handover command can include the abnormal transmission resource pool of the target cell to reduce transmission interruption. If the UE is configured with a base station as a synchronization source, the UE can use the transmission resource pool of the target cell before completing synchronization with the target cell. If the UE is configured with GNSS as a synchronization source, the UE can use the transmission resource pool of the target cell after synchronizing with the GNSS. If the handover command includes an abnormal transmission resource pool, the UE can randomly select resources from the abnormal transmission resource pool after receiving the handover command. If the handover command configures the UE to use base station scheduling resources, the UE can continue to use the abnormal transmission resource pool when the handover-related timer allows. If the handover command configures the UE to use autonomous resource selection, the UE can also use the abnormal transmission resource pool before the sensing result of the resource pool corresponding to the autonomous resource selection is available.

[0212] Specifically for NR V2X, if multiple resource allocation modes are allowed to be configured simultaneously, and the resource allocation mode configured by the base station for the UE is associated with a logical channel / logical channel group, the UE can consider the modes corresponding to different logical channels to determine when to stop using the abnormal resource pool to transmit data of the corresponding logical channel / logical channel group. If the resource allocation mode configured by the base station for the UE is not associated with a logical channel / logical channel group, the UE can stop using the abnormal resource pool based on the earliest occurrence of the handover-related timer stop or the sensing result availability.

[0213] Proposal 4: NR V2X can reuse the abnormal transmission resource pool of the target cell in the LTE V2X handover command. If multiple resource allocation modes are allowed to be configured simultaneously, and the resource allocation mode configured by the base station for the UE is associated with a logical channel / logical channel group, the UE can consider the modes corresponding to different logical channels to determine when to stop using the abnormal resource pool to transmit the data of the corresponding logical channel / logical channel group. If the resource allocation mode configured by the base station for the UE is not associated with a logical channel / logical channel group, the UE can stop using the abnormal resource pool based on the earliest occurrence of the handover-related timer stop or the sensing result availability.

[0214] It should be pointed out that:

[0215] 1. The sending UE needs to report the receiving UE's ID to the base station. However, the receiving UE's source ID is constantly changing. Consider the following solutions:

[0216] 1) When the UE learns that the destination ID has changed, it reports the new destination ID list, or reports it in the add and remove mode to save signaling. After the base station receives the information, it uses the new destination ID when sending the SLRB configuration information subsequently. However, if only the destination ID in the configuration changes and other parameters remain unchanged, there is no need to send the updated SLRB configuration.

[0217] 2) When the sending UE establishes a connection with the receiving UE, it obtains the ID information of the receiving UE and uses it as the ID of the receiving UE. The ID is subsequently reported to the base station as the ID of the receiving UE. The change of the receiving UE destination ID does not affect the change of the receiving UE ID.

[0218] 3) Inform the base station of the destination ID before and after the update. After receiving this information, the base station uses the new destination ID when sending SLRB configuration information subsequently. However, if only the destination ID in the configuration changes and other parameters remain unchanged, there is no need to send the updated SLRB configuration.

[0219] 2. Include the destination ID in the SDAP-Config configuration IE or in the DRB-ToAddMod IE.

[0220] Alternatively, you can directly list the unicast, multicast, and broadcast destination ID lists in sequence and configure SL DRBs based on each destination ID.

[0221] The content of this part is in the above embodiment 1 and will not be repeated here.

[0222] 3. If a new rxt-BSR is defined, the impact on logical channel priorities needs to be considered. For a retransmitted TB block, the MAC entity identifies the highest-priority logical channel among the logical channels it contains. The priority of this highest-priority logical channel in the TB block represents the priority of the TB block. The priority is then compared with the sidelink BSR and BSR.

[0223] The content of this part is in the above embodiment 2 and will not be repeated here.

[0224] 4. For V2X, if multiple Type 1 or type 2 configured grants are configured, the cast type indication needs to be added to the ConfiguredGrantConfig configuration.

[0225] The content of this part is in the above embodiment 3 and will not be repeated here.

[0226] 5. If the UE supports both mode 1 and mode 2, the base station allocates a HARQ Process ID list dedicated to mode 2.

[0227] The content of this part is in the above embodiment 4 and will not be repeated here.

[0228] 6. If different PSFCHs need to be configured for different UEs, that is, for multicast, each receiving UE needs to be allocated different PSFCH resources, then the base station needs to know the number of PSFCH resources that need to be allocated when allocating resources (the UE reports through sidelink UE information). The specific PSFCH resource used by which receiving UE can be determined by the base station or the sending UE, and then the PSFCH resource information is carried through SCI signaling to indicate the PSFCH resources of the receiving UE of each destination ID.

[0229] So, how does the sending UE know which receiving UEs are in the group and the identifiers of the receiving UEs? 1) The NAS layer notifies the AS layer; 2) a unicast connection is established with all UEs in the group in advance to exchange information such as UE identifiers and PSFCH resources, but multicast messages are still sent via multicast. If the sending UE establishes a unicast connection with all UEs in the group, then an intra-group identifier can be assigned to each receiving UE when the connection is established. Then, when the sending UE sends a data packet, it carries N PSFCH resource information in the SCI, and the receiving UE determines which PSFCH resource to use based on its own identifier. (For example, if there are eight receiving UEs and the SCI carries eight resources, then the receiving UE with identifier 1 uses the first resource, and the receiving UE with identifier 2 uses the second resource.)

[0230] The content of this part is in the above embodiment 5 and will not be repeated here.

[0231] Figure 7 The frame of the UE information reporting device of the embodiment of the present application Figure 1 ,like Figure 7 As shown, it includes: a first acquisition module 21, used for the first UE to obtain the identification information of the second UE; a first sending module 22, used for the first UE to send the identification information of the second UE before adjustment and the identification information after adjustment to the network element device on the network side to report UE information.

[0232] In an exemplary embodiment, the identification information of the second UE includes layer 2 identification information of the UE.

[0233] An embodiment of the present application provides a vehicle networking resource application device, the device comprising:

[0234] A second acquisition module, configured for the first UE to acquire layer 2 identification information of the second UE;

[0235] A first determining module, configured for the first UE to determine identification information of a second UE;

[0236] The second sending module is used for the first UE to send the identification information of the second UE to the network element device on the network side to apply for resource configuration.

[0237] In an exemplary embodiment, the first determining module is further configured to:

[0238] The first UE uses the layer 2 identification information of the second UE as the identification information of the second UE; or,

[0239] The first UE allocates UE identification information to the second UE.

[0240] In an exemplary embodiment, the apparatus further comprises: a first processing module configured to:

[0241] The first UE uses the layer 2 identification information of the second UE as the identification of the second UE;

[0242] The first UE receives the layer 2 identification information of the second UE again, the first UE associates the received layer 2 identification information of the second UE with the identification of the second UE, and updates the layer 2 identification information of the second UE according to the received layer 2 identification information of the second UE.

[0243] An embodiment of the present application provides a vehicle network resource configuration device, the device comprising:

[0244] A first receiving module is configured for a user equipment UE to receive sidelink bearer configuration information configured by a network element device on a network side;

[0245] The bearer configuration information includes at least one of target identification information, target UE information, and transmission type information.

[0246] In an exemplary embodiment, the transmission type information includes at least one of unicast, multicast, and broadcast.

[0247] In an exemplary embodiment, the first receiving module is further configured to: the UE receives SDAP layer configuration information;

[0248] The SDAP layer configuration information includes at least one of target identification information, target UE information, and transmission type information.

[0249] In an exemplary embodiment, the transmission type information includes at least one of unicast, multicast, and broadcast.

[0250] The apparatus for a MAC entity processing logical channel priorities in an embodiment of the present application includes a first priority sorting module configured to:

[0251] The logical channel priorities are sorted in descending order as follows:

[0252] MAC control element for the cell C-RNTI or data from the UL-CCCH;

[0253] MAC control unit for sidelink retransmission BSR;

[0254] A MAC control unit for a sidelink BSR, wherein the sidelink BSR includes: a sidelink BSR excluding a sidelink BSR for padding.

[0255] An apparatus for a MAC entity to process logical channel priorities according to an embodiment of the present application includes a second priority sorting module configured to:

[0256] For a retransmitted BSR, the MAC entity uses the priority of the logical channel with the highest priority included in the transport block corresponding to the retransmitted BSR as the priority of the retransmitted BSR;

[0257] For a sidelink BSR, the MAC entity uses the priority of the logical channel with the highest priority included in the sidelink BSR as the priority of the sidelink BSR.

[0258] An embodiment of the present application provides a vehicle network resource configuration device, the device comprising:

[0259] The second receiving module is used for the UE to receive the configure grant configuration information;

[0260] The UE sends data using the configure grant configuration information;

[0261] The configure grant configuration information includes at least one of target identification information, target UE information, and transmission type information.

[0262] In an exemplary embodiment, the transmission type information includes at least one of unicast, multicast, and broadcast.

[0263] In an exemplary embodiment, the configure grant configuration information further includes: indication information of whether transmission of retransmission packets is supported.

[0264] An embodiment of the present application provides a vehicle network resource configuration device, the device comprising:

[0265] The third receiving module is used for the UE to receive HARQ Process ID list information;

[0266] A second determining module is configured for the UE to determine a HARQ Process ID according to the HARQ Process ID list;

[0267] The HARQ Process ID list indicates the HARQ Process ID list under the resource allocation mode that can be used by the UE to select transmission resources.

[0268] In an exemplary embodiment, the HARQ Process ID list information is carried in a manner including: carried through a system message, or carried through RRC dedicated signaling.

[0269] In an exemplary embodiment, the UE includes: a UE that supports both network-side network element device scheduling and UE selection of transmission resources.

[0270] An embodiment of the present application provides a vehicle network resource configuration device, the device comprising:

[0271] A third acquisition module is used for the first UE to obtain information about UEs in the sidelink multicast communication group;

[0272] The third determination module is used by the first UE to determine the PSFCH resource information of the UE in the sidelink multicast communication group.

[0273] In one exemplary embodiment, the apparatus further comprises:

[0274] A third sending module is used for the first UE to send information about UEs in the sidelink multicast communication group to a network element device on the network side;

[0275] The fourth receiving module is used for the first UE to receive PSFCH resource information of UEs in the group.

[0276] In an exemplary embodiment, the PSFCH resource information includes: a PSFCH resource pool or N PSFCH resources.

[0277] In an exemplary embodiment, the information of the UEs in the group includes: identification information of the UEs in the group, quantity information of the UEs in the group, or category identification information of the UEs in the group.

[0278] In an exemplary embodiment, the method for obtaining the identification information of the UE in the group includes:

[0279] Notify the AS layer of the identity of the UE in the group through the NAS layer of the UE; or:

[0280] The UE establishes a connection with the UEs in the group to obtain identification information of the UEs in the group.

[0281] In one exemplary embodiment, the apparatus further comprises:

[0282] A fourth acquisition module, configured for the first UE to acquire PSFCH resource pool information;

[0283] The third determining module is further used for the first UE to determine the PSFCH resource information of the UEs in the group according to the information of the UEs in the group and the PSFCH resource pool information.

[0284] In an exemplary embodiment, the apparatus further includes: a fourth sending module, configured for the first UE to send PSFCH resource information to a second UE.

[0285] In an exemplary embodiment, the apparatus further comprises: a second processing module configured to:

[0286] The first UE carries PSFCH resource information of all UEs in the group through the SCI;

[0287] The PSFCH resource information of the UEs in the group includes: identifiers of the UEs in the group and PSFCH resources corresponding to the identifiers; or: category identifiers of the UEs in the group and PSFCH resources corresponding to the category identifiers.

[0288] Figure 8 Hardware diagram of the reporting device for this application embodiment Figure 1 , the reporting device of the UE information of the embodiment of the present application can be located at the terminal device side, that is. Figure 8 As shown, the terminal device may include mobile terminals such as mobile phones, smart phones, laptop computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), navigation devices, etc., as well as fixed terminals such as digital TVs, desktop computers, etc. Below, it is assumed that the terminal is a mobile terminal. However, it will be understood by those skilled in the art that, in addition to components specifically for mobile purposes, the configuration according to the embodiments of the present invention can also be applied to fixed-type terminals.

[0289] The terminal device may include a wireless communication unit, specifically consisting of a transmitter 61 and a receiver 62, as shown in the figure, a memory 63, a processor 64, a power supply unit 65, and the like. The figure shows a terminal device having various components, but it should be understood that implementation of all illustrated components is not required. More or fewer components may alternatively be implemented. The aforementioned transmitter may be the physical component of the sending module in this embodiment; the processor may be the indication module, the first determination module, the second determination module, the third determination module, the fourth determination module, or the fifth determination module in this embodiment.

[0290] Figure 9 This is a schematic diagram of the structure of the transmitting device of the transmission channel state in the embodiment of the present application located in the terminal device embodiment, as shown in FIG. Figure 9 As shown, terminal device 130 includes a memory 1303 and a processor 1304. Terminal device 130 may also include an interface 1301 and a bus 1302. Interface 1301, memory 1303, and processor 1304 are connected via bus 1302. Memory 1303 is used to store instructions. Processor 1304 is configured to read the instructions to execute the technical solution of the above-described method embodiment applied to the terminal device. The implementation principles and technical effects are similar and will not be further described here.

[0291] Figure 10-11 Two schematic diagrams of the communication system structure provided in the embodiments of this application. Figure 10 As shown, in this embodiment, the network side device is a base station 101, and the terminal device can be the user equipment (UE) 110, 120, 130 in the figure. The functions of the above base station and UE are the same as those in the above embodiment and will not be repeated. Figure 11 As shown, the system includes: the user equipment 130 of the above embodiment and the base station 140 of the above embodiment. Similarly, the base station in the figure can be the network device in the implementation mode, and the user equipment is the above terminal device, and the functions it can implement are also the same as the above functions, which will not be repeated here.

[0292] The above description is merely an exemplary embodiment of the present application and is not intended to limit the scope of protection of the present application.

[0293] It will be appreciated by those skilled in the art that the term user terminal covers any suitable type of wireless user equipment, such as a mobile phone, a portable data processing device, a portable web browser or a vehicle-mounted mobile station.

[0294] In general, various embodiments of the present application may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although the present application is not limited thereto.

[0295] Embodiments of the present application may be implemented by executing computer program instructions by a data processor of a mobile device, for example, in a processor entity, or by hardware, or by a combination of software and hardware. The computer program instructions may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages.

[0296] The block diagram of any logical flow in the accompanying drawings of the present application may represent program steps, or may represent interconnected logical circuits, modules and functions, or may represent a combination of program steps and logical circuits, modules and functions. The computer program may be stored on a memory. The memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology. The memory in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM) or a flash memory, etc. The volatile memory may be a random access memory (RAM), which is used as an external cache. RAM can include various forms, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus random access memory (DRRAM). The memory of the systems and methods described herein includes, but is not limited to, these and any other suitable types of memory.

[0297] The processor of the embodiment of the present application can be any type suitable for the local technical environment, such as but not limited to a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable logic device (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, or a processor based on a multi-core processor architecture. The general-purpose processor can be a microprocessor or any conventional processor, etc. The above-mentioned processor can implement or execute the steps of the disclosed methods in the embodiment of the present application. The software module can be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

[0298] The above description of exemplary embodiments of the present application has been provided by way of exemplary and non-limiting examples. However, various modifications and adaptations to the above embodiments will be apparent to those skilled in the art, when considered in conjunction with the accompanying drawings and claims, without departing from the scope of the present invention. Therefore, the proper scope of the present invention will be determined by reference to the claims.

Claims

1. A wireless communication resource configuration method, characterized in that: The method comprises: The user equipment UE receives the sidelink bearer configuration information configured by the network element device on the network side, where the bearer configuration information includes service data protocol SDAP layer configuration information, and the SDAP layer configuration information includes transmission type information; and The UE configures an SDAP entity corresponding to the destination ID according to the destination ID and the transmission type information, where the destination ID is used to indicate a layer 2 ID of a peer user equipment UE communicating with the UE.

2. The method according to claim 1, characterized in that The transmission type information includes at least one of unicast, multicast, and broadcast.

3. The method according to claim 1, characterized in that The SDAP layer configuration information further includes: at least one of the destination ID and target UE information.

4. The method according to claim 3, characterized in that The transmission type information includes at least one of unicast, multicast, and broadcast.

5. A wireless communication resource configuration device, characterized in that: The device comprises: A first receiving module is configured to receive sidelink bearer configuration information configured by a network element device on the network side, wherein the bearer configuration information includes service data protocol (SDAP) layer configuration information, and the SDAP layer configuration information includes transmission type information; and A configuration module is configured to configure an SDAP entity corresponding to the destination ID according to the destination ID and the transmission type information, where the destination ID is used to indicate a layer 2 ID of a peer user equipment UE communicating with the user equipment UE.

6. The device according to claim 5, characterized in that The transmission type information includes at least one of unicast, multicast, and broadcast.

7. The device according to claim 5, characterized in that The SDAP layer configuration information further includes: at least one of the destination ID and target UE information.

8. The device according to claim 7, characterized in that The transmission type information includes at least one of unicast, multicast, and broadcast.

9. A wireless communication apparatus comprising a memory for storing a computer program and at least one processor, the at least one processor being configured to execute the computer program to cause the wireless communication apparatus to: Receiving sidelink bearer configuration information configured by a network element device on the network side, the bearer configuration information including service data protocol (SDAP) layer configuration information, the SDAP layer configuration information including transmission type information; and An SDAP entity corresponding to the destination ID is configured according to the destination ID and the transmission type information, where the destination ID is used to indicate a layer 2 ID of a counterpart user equipment UE communicating with the user equipment UE.

10. A wireless communication device comprising a memory for storing a computer program and at least one processor, the at least one processor being configured to execute the computer program to implement the method according to any one of claims 2 to 4.

11. A computer storage medium for storing a computer program, wherein the computer program, when executed by at least one processor of a wireless communication device, is configured to cause the wireless communication device to: Receiving sidelink bearer configuration information configured by a network element device on the network side, the bearer configuration information including service data protocol (SDAP) layer configuration information, the SDAP layer configuration information including transmission type information; and An SDAP entity corresponding to the destination ID is configured according to the destination ID and the transmission type information, where the destination ID is used to indicate a layer 2 ID of a counterpart user equipment UE communicating with the user equipment UE.

12. A storage medium, characterized in that: The storage medium stores a computer program, and when the computer program is executed by a processor, the method according to any one of claims 2 to 4 is implemented.

Images