Method and device for unicast side link communication

Abstract

The invention provides a unicast side link communication method and a device thereof. The unicast side link communication method is executed by first user equipment UE, and the method comprises the following steps: sending a reconfiguration message to second UE; receiving a reconfiguration failure message including a reconfiguration failure reason sent by the second UE in response to the reconfiguration failure; updating a reconfiguration message based on the reconfiguration failure reason; and transmitting the updated reconfiguration message to the second UE.

Description

Technical Field

[0001] The present disclosure generally relates to the field of wireless communication technology, and more particularly to a method and apparatus for unicast sidelink communication. Background Art

[0002] Unicast sidelink communication can be understood as direct communication (one-to-one communication) between the first user equipment (UE) and the second UE based on the new radio (NR) PC5 interface. Unicast sidelink communication can also be used for vehicle-to-everything (V2X) communication, allowing direct communication between vehicles. Those UEs authorized for special communications can adopt unicast sidelink communication. Unicast sidelink communication can provide information interaction not only within the network coverage service range, but also in places without network coverage.

[0003] In order to provide more reliable, shorter latency and higher data rate communication services on the unicast side link, it may be necessary to improve the communication performance of the terminal in various special scenarios. Currently, if the transmitting UE receives a radio resource control reconfiguration failure side link (RRCReconfigurationFailureSidelink) message sent by the opposite UE during the link establishment process, the side link service cannot be carried out normally, reducing the security and reliability of the communication. Summary of the invention

[0004] The embodiments of the present disclosure relate to a method and apparatus for unicast side link communication, which can solve part or all of the above problems.

[0005] According to one aspect of the present disclosure, a method for unicast sidelink communication is provided, which is performed by a first user equipment UE, and the method includes: sending a reconfiguration message to a second UE; receiving a reconfiguration failure message, the reconfiguration failure message indicating a reconfiguration failure related to the reconfiguration message, sent by the second UE in response to the reconfiguration failure and including a reconfiguration failure cause; updating the reconfiguration message based on the reconfiguration failure cause; and sending the updated reconfiguration message to the second UE.

[0006] In various embodiments:

[0007] The reconfiguration failure cause may be indicated by an extension field included in the reconfiguration failure message, wherein the extension field may be set by the second UE using the received reconfiguration message according to whether a radio link control RLC mode conflict occurs for the same logical channel.

[0008] The updating of the reconfiguration message based on the reconfiguration failure cause may include: based on determining that the reconfiguration failure cause is an RLC mode conflict, reallocating the logical channel identifier, and updating the reconfiguration message according to the reallocated logical channel identifier; or based on determining that the reconfiguration failure cause is that at least one other side link radio bearer SLRB parameter is not applicable, updating the reconfiguration message according to the default SLRB resources.

[0009] The method may further include: after receiving the reconfiguration failure message, checking whether optimization processing of reconfiguration failure is started via upper layer configuration; and in the case where optimization processing of reconfiguration failure is started, determining whether the cause of the reconfiguration failure is an RLC mode conflict.

[0010] The reallocation of the logical channel identifier may include: releasing the original logical channel identifier and the related context, and reallocating a logical channel identifier different from the original logical channel identifier.

[0011] The reallocation of a logical channel identifier different from the original logical channel identifier may include: reallocating an unused logical channel identifier, or reallocating a successful logical channel identifier when the second UE reconfigures a previously successful logical channel identifier of the first UE.

[0012] The updating of the reconfiguration message according to the default SLRB resources may include: acquiring the default SLRB resources from different information according to the current state of the first UE; and updating the reconfiguration message according to the acquired default SLRB resources.

[0013] The method of obtaining the default SLRB resources from different information according to the current state of the first UE includes: releasing the current SLRB resource context; in response to being in a radio resource control (RRC) connection state, obtaining the default SLRB resources in an RRC reconfiguration message; in response to being in an RRC idle / inactive state, obtaining the default SLRB resources in a system information block SIB12; or in response to being in an out-of-coverage (OOC) state, obtaining the default SLRB resources in the side link preconfiguration information.

[0014] According to another aspect of the present disclosure, a method for unicast sidelink communication is provided, which is performed by a second user equipment UE, and the method includes: receiving a reconfiguration message sent by a first UE; in response to a reconfiguration failure related to the reconfiguration message, sending a reconfiguration failure message including a reconfiguration failure cause to the first UE; receiving an updated reconfiguration message sent by the first UE, wherein the updated reconfiguration message is a reconfiguration message updated by the first UE based on the reconfiguration failure cause.

[0015] The sending of a reconfiguration failure message including a reconfiguration failure cause to the first UE comprises: using the received reconfiguration message to set an extension field included in the reconfiguration failure message according to whether a radio link control RLC mode conflict occurs for the same logical channel; and sending the reconfiguration failure message including the reconfiguration failure cause indicated by the extension field to the first UE.

[0016] The first UE reallocates the logical channel identifier based on determining that the cause of the reconfiguration failure is an RLC mode conflict, and updates the reconfiguration message based on the reallocated logical channel identifier; or the first UE updates the reconfiguration message based on the default SLRB resources based on determining that the cause of the reconfiguration failure is that at least one other side link radio bearer SLRB parameter is not applicable.

[0017] The logical channel identifier is a logical channel identifier that is reallocated by the first UE after releasing the original logical channel identifier and the related context and is different from the original logical channel identifier.

[0018] The logical channel identifier is an unused logical channel identifier reallocated by the first UE, or the logical channel identifier is a successful logical channel identifier reallocated by the first UE when the second UE reconfigures the previously successful logical channel identifier of the first UE.

[0019] The first UE obtains the default SLRB resource from different information according to the current state of the first UE, and updates the reconfiguration message according to the obtained default SLRB resource.

[0020] The default SLRB resource is obtained by the first UE in the RRC reconfiguration message in response to the first UE being in a radio resource control (RRC) connected state after releasing the current SLRB resource context, obtained in the system information block SIB12 in response to the first UE being in an RRC idle / inactive state, or obtained in the side link preconfiguration information in response to the first UE being in an out-of-coverage (OOC) state.

[0021] According to another aspect of the present disclosure, a first user equipment UE includes: a sending circuit configured to send a reconfiguration message to a second UE and send an updated reconfiguration message to the second UE; a receiving circuit configured to receive a reconfiguration failure message, wherein the reconfiguration failure message indicates a reconfiguration failure associated with the reconfiguration message, is sent by the second UE in response to the reconfiguration failure and includes a reconfiguration failure cause; and an updating circuit configured to update the reconfiguration message based on the reconfiguration failure cause to generate an updated reconfiguration message.

[0022] The reconfiguration failure cause is indicated by an extension field included in the reconfiguration failure message, wherein the extension field is set by the second UE using the received reconfiguration message according to whether a radio link control RLC mode conflict occurs for the same logical channel.

[0023] The update circuit is configured to: based on determining that the cause of the reconfiguration failure is an RLC mode conflict, reallocate the logical channel identifier, and update the reconfiguration message according to the reallocated logical channel identifier; or based on determining that the cause of the reconfiguration failure is that at least one other side link radio bearer SLRB parameter is not applicable, update the reconfiguration message according to the default SLRB resource.

[0024] The first UE also includes: an optimization start circuit, which is configured to: after receiving the reconfiguration failure message, check whether the optimization processing of the reconfiguration failure is started through the upper layer configuration; when the optimization processing of the reconfiguration failure is started, determine whether the cause of the reconfiguration failure is an RLC mode conflict.

[0025] The updating circuit is configured to: release the original logical channel identifier and the related context, and reallocate a logical channel identifier different from the original logical channel identifier.

[0026] The updating circuit is configured to reallocate an unused logical channel identifier, or, when the second UE reconfigures a previously successful logical channel identifier when the first UE is reconfigured, reallocate a successful logical channel identifier.

[0027] The updating circuit is configured to: obtain a default SLRB resource from different information according to a current state of the first UE; and update a reconfiguration message according to the obtained default SLRB resource.

[0028] The update circuit is configured to: release the current SLRB resource context; in response to being in a radio resource control (RRC) connected state, obtain the default SLRB resource in the RRC reconfiguration message; in response to being in an RRC idle / inactive state, obtain the default SLRB resource in the system information block SIB12; or in response to being in an out-of-coverage (OOC) state, obtain the default SLRB resource in the side link preconfiguration information.

[0029] According to another aspect of the present disclosure, a second user equipment UE includes: a receiving circuit configured to receive a reconfiguration message sent by a first UE and to receive an updated reconfiguration message sent by the first UE; and a sending circuit configured to send a reconfiguration failure message including a reconfiguration failure cause to the first UE in response to a reconfiguration failure associated with the reconfiguration message, wherein the updated reconfiguration message is a reconfiguration message updated by the first UE based on the reconfiguration failure cause.

[0030] The sending circuit is configured to: use the received reconfiguration message to set the extension field included in the reconfiguration failure message according to whether a radio link control RLC mode conflict occurs for the same logical channel; and send the reconfiguration failure message including the reconfiguration failure cause indicated by the extension field to the first UE.

[0031] The first UE reallocates the logical channel identifier based on determining that the cause of the reconfiguration failure is an RLC mode conflict, and updates the reconfiguration message based on the reallocated logical channel identifier; or the first UE updates the reconfiguration message based on the default SLRB resources based on determining that the cause of the reconfiguration failure is that at least one other side link radio bearer SLRB parameter is not applicable.

[0032] The logical channel identifier is a logical channel identifier that is reallocated by the first UE after releasing the original logical channel identifier and the related context and is different from the original logical channel identifier.

[0033] The logical channel identifier is an unused logical channel identifier reallocated by the first UE, or the logical channel identifier is a successful logical channel identifier reallocated by the first UE when the second UE reconfigures the previously successful logical channel identifier of the first UE.

[0034] The first UE obtains the default SLRB resource from different information according to the current state of the first UE, and updates the reconfiguration message according to the obtained default SLRB resource.

[0035] The default SLRB resource is obtained by the first UE in the RRC reconfiguration message in response to the first UE being in a radio resource control (RRC) connected state after releasing the current SLRB resource context, obtained in the system information block SIB12 in response to the first UE being in an RRC idle / inactive state, or obtained in the side link preconfiguration information in response to the first UE being in an out-of-coverage (OOC) state.

[0036] According to another aspect of the present disclosure, a system for unicast sidelink communication is provided, the system comprising: a first UE and a second UE having the capabilities outlined above.

[0037] According to another aspect of the present disclosure, an electronic device is provided, characterized in that it includes: a processor; and a memory storing a computer program, which, when executed by the processor, implements one of the methods of unicast side link communication as described above.

[0038] According to another aspect of the present disclosure, a computer-readable storage medium is provided, characterized in that a computer program is stored thereon, and when the program is executed, one of the methods of unicast sidelink communication as described above is implemented.

[0039] The technical solution provided according to the embodiments of the present disclosure produces at least one or more of the following beneficial effects: First, the reconfiguration failure can be optimized according to whether the cause of the reconfiguration failure is an RLC mode conflict. When the cause of the failure is an RLC mode conflict, only the logical channel ID is reallocated without adjusting other SLRB parameters. This can fully guarantee the quality of service and achieve the same communication effect as normal. In the case where the cause of the side link reconfiguration failure is not an RLC mode conflict (for example, the cause of the reconfiguration failure is that at least one other SLRB parameter is not applicable), the default SLRB parameter configuration can be used. Although it will affect the quality of service, it can ensure the reliability and continuity of communication under abnormal circumstances. In addition, the way in which the default SLRB resource is selected by the transmitting UE can reduce the conflict of SLRB resources, and the selected default SLRB resource can be more matched with the transmitting UE capability. The method and device for unicast side link communication according to the present disclosure can provide more reliable quality of service, more robust communication capabilities and safer performance.

[0040] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] The drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the description are used to explain the principles of the present disclosure, and do not constitute improper limitations on the present disclosure.

[0042] Figure 1 The flowchart of successful unicast side link reconfiguration is shown.

[0043] Figure 2 A flow chart of unicast side link reconfiguration failure is shown.

[0044] Figure 3 A flowchart of unicast link establishment and reconfiguration failure optimization according to an embodiment of the present disclosure is shown.

[0045] Figure 4 A flowchart of a method for unicast sidelink communication applied to a first UE according to an embodiment of the present disclosure is shown.

[0046] Figure 5 A flow chart of receiving a reconfiguration message according to an embodiment of the present disclosure is shown.

[0047] Figure 6 A flow chart of receiving a reconfiguration failure message according to an embodiment of the present disclosure is shown.

[0048] Figure 7 A flowchart of logical channel ID reallocation according to an embodiment of the present disclosure is shown.

[0049] Figure 8 A default SLRB acquisition flow chart according to an embodiment of the present disclosure is shown.

[0050] Fig. 9 A flowchart of successful reconfiguration of the second UE according to an embodiment of the present disclosure is shown.

[0051] Fig.10 A flowchart of successful reconfiguration of the first UE according to an embodiment of the present disclosure is shown.

[0052] Fig.11 A flowchart of a method for unicast sidelink communication applied to a second UE according to an embodiment of the present disclosure is shown.

[0053] Fig.12 A block diagram of a first UE according to an embodiment of the present disclosure is shown.

[0054] Fig.13 A block diagram of a second UE according to an embodiment of the present disclosure is shown.

[0055] Fig.14 A system for unicast sidelink communication according to an embodiment of the present disclosure is shown.

[0056] Fig.15 A block diagram of an electronic device according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0057] In order to facilitate understanding of the inventive concept and technical solution of this article, the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings.

[0058] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The implementation methods described in the following examples do not represent all implementation methods consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the attached claims.

[0059] It should be noted that the phrase "at least one of the items" in the present disclosure includes three types of parallel situations: "any one of the items", "a combination of any number of the items", and "all of the items". For example, "including at least one of A and B" includes the following three parallel situations: (1) including A; (2) including B; (3) including A and B. Another example is "performing at least one of operation 1 and operation 2" which means the following three parallel situations: (1) performing operation 1; (2) performing operation 2; (3) performing operation 1 and operation 2.

[0060] Unicast sidelink communication is direct communication between user equipment (UE) and UE based on the NR PC5 interface. When the upper layer requests to establish unicast sidelink (Sidelink, SL) communication and there is data to be sent, if the UE is in the radio resource control connected (RRC_CONNECTED) state, a matching sidelink radio bearer (SLRB) resource is selected in the radio resource control (RRC) reconfiguration (RRCReconfiguration) message according to the quality of service (QoS) parameters provided by the upper layer. If the UE is in the RRC idle / inactive (RRC_IDLE / INACTIVE) state, a matching SLRB resource is selected in the system information block (SIB) 12 according to the QoS parameters. If the UE is in the out of coverage (OOC) state, a matching SLRB resource is selected in the sidelink preconfiguration (e.g., SL-PreconfigurationNR) information according to the QoS parameters.

[0061] Figure 1 The unicast side link reconfiguration successful flow chart is shown. Figure 1 The transmitting (Tx) UE sends an RRC Reconfiguration Sidelink message carrying SLRB resource information to the receiving (Rx) UE. The receiving UE configures resources at each layer. If the configuration is successful, it returns an RRC Reconfiguration Complete Sidelink message to the transmitting UE, and the unicast sidelink communication service can proceed normally.

[0062] Some abnormal situations of unicast sidelink communication that may occur in the UE are as follows: 1) The radio link control (RLC) mode carried in the receiving UE conflicts with that carried in the RRCReconfigurationSidelink message, that is, for the same logical channel, the RLC mode configured by the transmitting UE is different from the RLC mode configured by the receiving UE; 2) The SLRB parameter configuration information carried in the RRCReconfigurationSidelink message is not applicable to the receiving UE.

[0063] Figure 2 The unicast side link reconfiguration failure flow chart is shown. Figure 2 , the transmitting UE sends an RRCReconfigurationSidelink message carrying SLRB resource information to the receiving UE, and the receiving UE fails to reconfigure due to the above abnormal situation. The receiving UE then returns an RRCReconfigurationFailureSidelink message to the transmitting UE.

[0064] If the transmitting UE is in the RRC connected state, this problem can be solved by updating the parameter configuration sent by the network. The transmitting UE needs to report error information to the network. This processing method requires multiple air interface interactions and requires a large delay. If the transmitting UE is in the RRC inactive state, idle state or OOC scenario, unicast side link communication will not be possible in the case of SLRRC reconfiguration during link establishment. If high-priority autonomous driving services, such as emergency obstacle avoidance and highly automated vehicle scheduling, cannot send and receive unicast side link data in a timely manner, it will seriously affect safety and reliability.

[0065] To solve the above problems, the present disclosure proposes a method and device for unicast side link communication. Figures 3 to 15 The method and apparatus for unicast sidelink communication according to the present disclosure are described in detail.

[0066] Figure 3 A schematic diagram of the optimization process of unicast link establishment and reconfiguration failure according to an embodiment of the present disclosure is shown.

[0067] exist Figure 3In the optimization process, the entities involved include the sending end UE and the receiving end UE. UE can be any electronic device with sufficient communication capabilities to perform the above operations. Some examples may include: mobile terminals (such as smart phones, mobile phones, video phones, etc.), wearable devices (such as smart glasses, head-mounted displays (HMD), electronic clothing, electronic bracelets, electronic necklaces, electronic accessories, electronic tattoos or smart watches, etc.), sensors, mobile medical devices, Internet of Things devices, tablet computers, desktops, laptops, handheld computers, notebook computers, netbooks, personal digital assistants (personal digital assistant, PDA), vehicle-to-everything (V2X) devices (such as vehicle user equipment (V-UE), road user equipment (I-UE), pedestrian user equipment (P-UE) or network user equipment (N-UE), etc.), augmented reality (AR) / virtual reality (VR) and other devices, but the present disclosure is not limited thereto. UE can access the network and communicate through cellular communication networks (such as 4G networks, 5G networks, etc.) and other wireless networks (such as WLAN, WiFi, etc.).

[0068] Reference Figure 3 , the transmitting UE sends an RRCReconfigurationSidelink message carrying SLRB resource information to the receiving UE. The receiving UE fails to reconfigure due to an abnormal situation, and the receiving UE will return an RRCReconfigurationFailureSidelink message to the transmitting UE. The transmitting UE can readjust the configuration parameters, which may include reallocating the logical channel identifier (hereinafter also represented as logical channel ID or LCID) or using the default SLRB resources. Specifically, the transmitting UE can determine whether the cause of the reconfiguration failure is an RLC mode conflict. If so, the transmitting UE can reallocate the logical channel ID. In the case where the cause of the reconfiguration failure is not an RLC mode conflict, the transmitting UE can use the default SLRB resources. The transmitting UE again sends an RRCReconfigurationSidelink message carrying the adjusted configuration parameters to the receiving UE. The receiving UE successfully establishes the reconfiguration and returns the RRCReconfigurationCompleteSidelink message to the transmitting UE, and the unicast sidelink communication service can proceed normally.

[0069] The entities involved in the above optimization process may also include network nodes, such as base stations (such as gNobeB). After the transmitting UE receives the RRCReconfigurationFailureSidelink message sent by the receiving UE, as an optional operation, the transmitting UE may report the UE-related sidelink information (SidelinkUEinformationNR), for example, reporting error information to the network.

[0070] It should be understood that the above unicast link establishment and reconfiguration failure optimization process is only an example, and the present disclosure is not limited thereto.

[0071] The optimization process of reconfiguration failure mainly adopted by the unicast side link communication method of the present disclosure may include the following four operations:

[0072] 1) After receiving the RRCReconfigurationFailureSidelink message, the transmitting UE readjusts (eg, changes) the configuration parameters and sends the RRCReconfigurationSidelink message again to reconfigure the receiving UE.

[0073] 2) Add an extended field sl-RLC-Mode-Conflict in the RRCReconfigurationFailureSidelink message, which is used to indicate whether the cause of the failure is an RLC mode conflict. If the RLC mode of the logical channel indicated by the logical channel ID carried in the RRCReconfigurationSidelink message received by the receiving UE is inconsistent with the RLC mode of the local end, the extended field sl-RLC-Mode-Conflict is set to true (True), otherwise, it is set to false (False).

[0074] 3) Reallocate (e.g., change) the logical channel ID. When the transmitting UE receives the RRCReconfigurationFailureSidelink message and the value of the extended field sl-RLC-Mode-Conflict in the message is True, it will release the previously allocated logical channel ID and reallocate a different logical channel ID.

[0075] 4) Using the default SLRB in some cases: When the transmitting UE receives the RRCReconfigurationFailureSidelink message, and the message does not carry the sl-RLC-Mode-Conflict field, or the value of the sl-RLC-Mode-Conflict field is False, the default SLRB resource is selected and the paired UE is re-matched.

[0076] The above points 1)-3) are applicable not only to the side link reconfiguration process when establishing a link (ie, link building), but also to the side link reconfiguration process corresponding to all unicast QoS parameter updates.

[0077] In the following description, the first UE may be a transmitting UE (Tx UE), and the second UE may be a receiving UE (Rx UE).

[0078] Figure 4 A flowchart of a method for unicast sidelink communication applied to a first UE according to an embodiment of the present disclosure is shown.

[0079] In operation S410, a reconfiguration message is sent to a second UE.

[0080] In an embodiment of the present disclosure, when the upper layer requests to establish a unicast side link communication and there is data to be sent, the first UE may send an RRCReconfigurationSidelink message carrying SLRB resource information to the second UE. The SLRB resource information may include SLRB parameters, where examples of SLRB parameters may include: SLRB index (SLRB index), service data adaptation protocol (SDAP) configuration, packet data convergence protocol (PDCP) configuration, radio link control (RLC) configuration, and media access control (MAC) logical channel configuration, etc., but the present disclosure is not limited to this. The MAC logical channel configuration includes a logical channel ID. The RLC configuration includes an RLC mode. In unicast side link communication, the RLC mode may include an acknowledgement mode (AM) and an unacknowledgement mode (UM).

[0081] If the first UE receives the RRCReconfigurationCompleteSidelink message returned by the second UE, the unicast sidelink communication is performed normally. If the first UE receives the RRCReconfigurationFailureSidelink message returned by the second UE, it indicates that the sidelink reconfiguration fails.

[0082] In operation S420, a reconfiguration failure message is received, where the reconfiguration failure message indicates a reconfiguration failure associated with the reconfiguration message, is sent by the second UE in response to a reconfiguration failure, and includes a reconfiguration failure cause.

[0083] According to an embodiment of the present disclosure, the reconfiguration failure cause may be indicated by an extension field included in a reconfiguration failure message, wherein the extension field may be set by the second UE using the received reconfiguration message according to whether an RLC mode conflict of the same logical channel occurs.

[0084] In an embodiment of the present disclosure, after the second UE receives the RRCReconfigurationSidelink message sent by the first UE, the second UE can use the message and obtain the logical channel ID and RLC mode of the first UE carried in the message. If the obtained logical channel ID of the first UE is LCID4, the corresponding RLC mode is AM, and the second UE configures the RLC mode corresponding to LCID4 as UM, then an RLC mode conflict problem of the same logical channel (same LCID4) occurs, and reconfiguration failure may occur.

[0085] After the second UE receives the RRCReconfigurationSidelink message, if no RLC mode conflict occurs, but at least one other SLRB parameter carried in the message is not applicable to the second UE. For example, at least one other SLRB parameter for which the parameter is not applicable may include an SLRB index and an SDAP header. For example, the situation where the parameter is not applicable may include that the SLRB index carried in the RRCReconfigurationSidelink message does not appear in the SLRB resources stored by the second UE, that is, the second UE does not store the SLRB resources including the SLRB index. The UE can store multiple SLRB resources that can be configured by itself. These SLRB resources can be selected or configured by the UE from different information according to different states. For example, if the UE is in the RRC_CONNECTED state, the SLRB resources can be selected and stored from the RRCReconfiguration message. For another example, the situation where the parameters are not applicable may also include that the SLRB index carried in the RRCReconfigurationSidelink message appears in the SLRB resources stored by the second UE, but the SDAP Header configured in the SLRB resources including the SLRB index is inconsistent with the SDAP Header carried in the RRCReconfigurationSidelink message. The reconfiguration failure will also occur if at least one other SLRB parameter is not applicable. In the event of a reconfiguration failure, the second UE will return an RRCReconfigurationFailureSidelink message to the first UE. In addition, if the SLRB index carried in the RRCReconfigurationSidelink message appears in the SLRB resources stored by the second UE, but the SLRB resources including the SLRB index in the second UE have not been used, then the SLRB resources may not have been configured with an SDAP Header. In this case, the second UE can use the SDAP Header carried in the RRCReconfigurationSidelink message for configuration without the situation where at least one other SLRB parameter is not applicable.

[0086] It should be understood that the above-mentioned logical channel IDs and corresponding modes are merely examples, and the case where at least one other SLRB parameter is not applicable is also merely an example, and the present disclosure is not limited thereto.

[0087] In an embodiment of the present disclosure, an extended field sl-RLC-Mode-Conflict is added to the RRCReconfigurationFailureSidelink message, and the extended field may be used to indicate whether the cause of the reconfiguration failure is an RLC mode conflict.

[0088] Figure 5 A flow chart of receiving a reconfiguration message according to an embodiment of the present disclosure is shown.

[0089] Reference Figure 5 , in operation S510, the second UE receives the RRCReconfigurationSidelink message sent by the first UE. After receiving the message, in operation S520, the second UE determines whether the reconfiguration is successful. If the reconfiguration is successful, in operation S530, the second UE sends an RRCReconfigurationCompleteSidelink message to the first UE. If the reconfiguration fails, in operation S540, the second UE determines whether an RLC mode conflict occurs. If an RLC mode conflict occurs, in operation S550, the second UE sets the extended field sl-RLC-Mode-Conflict in the RRCReconfigurationFailureSidelink message to True. If the reconfiguration fails due to other circumstances (i.e., at least one other SLRB parameter is not applicable), in operation S560, the second UE sets the extended field sl-RLC-Mode-Conflict in the RRCReconfigurationFailureSidelink message to False. And in operation S570, an RRCReconfigurationFailureSidelink message is sent to the first UE so that the second UE delivers a detailed failure cause of the sidelink reconfiguration to the first UE.

[0090] As described above, the unicast side link communication method disclosed in the present invention can add an extended field (e.g., sl-RLC-Mode-Conflict) in the reconfiguration failure message to indicate whether the cause of the reconfiguration failure is an RLC mode conflict, and can convey the detailed failure cause of the side link reconfiguration to the transmitting UE, thereby facilitating the transmitting UE to optimize the handling of the reconfiguration failure.

[0091] return Figure 4 , in operation S430, based on the reconfiguration failure reason, the reconfiguration message is updated.

[0092] In operation S440, the updated reconfiguration message is sent to the second UE.

[0093] According to an embodiment of the present disclosure, the method of unicast side link communication may further include: after receiving the reconfiguration failure message, checking whether the optimization processing of the reconfiguration failure has been initiated via the upper layer configuration; and when the optimization processing of the reconfiguration failure has been initiated, determining whether the cause of the reconfiguration failure is an RLC mode conflict.

[0094] Figure 6 A flow chart of receiving a reconfiguration failure message according to an embodiment of the present disclosure is shown.

[0095] Reference Figure 6 In operation S610, the first UE receives the RRCReconfigurationFailureSidelink message sent by the second UE. After receiving the message, in operation S620, the second UE checks whether the optimization processing of reconfiguration failure is started via the upper layer configuration. If the optimization processing of reconfiguration failure is not started, in operation S630, the unicast side link communication fails to establish a link. If the optimization processing of reconfiguration failure is not started, according to the 3GPP protocol requirements, the first UE and the second UE can use the previous configuration resources at this time. If it is the first time to perform side link RRC reconfiguration, that is, the reconfiguration initiated when the unicast link is established, the previous configuration cannot be used, which will cause the unicast link to be released, and the unicast side link communication will not be able to proceed. When the service quality requirements are high, such as emergency trajectory coordination, coordinated collision avoidance, etc., the optimization processing of reconfiguration failure can be configured to start, which can improve the reliability and stability of unicast side link communication. If the optimization processing of reconfiguration failure has been started, in operation S640, the first UE determines whether the cause of the reconfiguration failure is an RLC mode conflict. The first UE may use the extended field sl-RLC-Mode-Conflict carried in the RRCReconfigurationFailureSidelink message to determine whether the cause of the reconfiguration failure is an RLC mode conflict. When the extended field sl-RLC-Mode-Conflict is True, it is determined that the cause of the reconfiguration failure is an RLC mode conflict, and in operation S650, the first UE may reallocate the logical channel ID. When the extended field sl-RLC-Mode-Conflict is False, it is determined that the cause of the reconfiguration failure is not an RLC mode conflict, but at least one other SLRB parameter is not applicable, and in operation S660, the first UE may use the default SLRB resource.

[0096] According to an embodiment of the present disclosure, based on determining that the reconfiguration failure cause is an RLC mode conflict, a logical channel identifier may be reallocated, and a reconfiguration message may be updated according to the reallocated logical channel identifier.

[0097] According to an embodiment of the present disclosure, reallocating a logical channel identifier may include: releasing an original logical channel identifier and a related context, and reallocating a logical channel identifier different from the original logical channel identifier.

[0098] According to an embodiment of the present disclosure, an unused logical channel identifier may be reallocated, or, in the case where a previously successful logical channel identifier is reconfigured by a second UE when the first UE is reconfigured, a successful logical channel identifier may be reallocated.

[0099] In an embodiment of the present disclosure, if the reason for the reconfiguration failure is an RLC mode conflict, this may mean that the RLC mode corresponding to the logical channel ID allocated to the first UE is inconsistent with the RLC mode corresponding to the same logical channel ID of the second UE. Since the RRC layer is responsible for allocating and managing logical channel IDs, its flexibility can be fully utilized to dynamically adjust the allocation strategy of logical channels according to resource conditions.

[0100] Figure 7 A flowchart of logical channel ID reallocation according to an embodiment of the present disclosure is shown.

[0101] Reference Figure 7 In operation S710, the first UE may release the original logical channel ID and related context, and in operation S720, the first UE may reallocate a logical channel ID different from the previous one to the current SLRB resource. Here, the relevant context may include: (i) information indicating whether the logical channel ID has been allocated and (ii) relevant information of the corresponding SLRB. The relevant information of the corresponding SLRB may include SLRB index, RLC mode, etc. After reallocating the logical channel ID, the first UE also reconfigures the second UE. The first UE may update the RRCReconfigurationSidelink message according to the reallocated logical channel ID. In operation S730, the first UE sends the updated RRCReconfigurationSidelink message to the first UE. Specifically, the first UE may send the RRCReconfigurationSidelink message including the reallocated logical channel ID to the second UE.

[0102] For example, after the second UE receives the RRCReconfigurationSidelink message sent by the first UE, if the logical channel ID of the first UE obtained from the message is LCID4, the corresponding RLC mode is AM, and the second UE configures the RLC mode corresponding to LCID4 as UM, then an RLC mode conflict occurs for the same logical channel (same LCID4). The second UE may return an RRCReconfigurationFailureSidelink message carrying the reason for the reconfiguration failure as an RLC mode conflict to the first UE. Based on the fact that the reason for the reconfiguration failure is an RLC mode conflict, the first UE may reallocate LCID5 whose corresponding RLC mode is AM. Here, the RLC mode corresponding to the reallocated logical channel ID should be consistent with the RLC mode currently configured by the first UE. That is, for the SLRB parameter carried by the RRCReconfigurationSidelink message, the logical channel ID is reallocated without changing the RLC mode. Subsequently, the first UE may send an RRCReconfigurationSidelink message including LCID5 and the corresponding RLC mode (i.e., AM, the RLC mode has not changed) to the second UE, and the second UE may obtain the LCID5 and the corresponding RLC mode (i.e., AM) of the first UE included in the message, and check whether the RLC mode corresponding to the LCID5 configured by the second UE is AM, and when the RLC mode corresponding to the LCID5 configured by the second UE is AM, no RLC mode conflict occurs and subsequent reconfiguration may be successful. If an RLC mode conflict occurs again, for example, the RLC mode corresponding to the LCID5 configured by the second UE is UM, the above operation may be repeated, for example, the second UE may return an RRCReconfigurationFailureSidelink message carrying the reason for the reconfiguration failure as the RLC mode conflict to the first UE, and the first UE may reallocate the corresponding RLC mode as AM LCID6 and send an RRCReconfigurationSidelink message carrying LCID6 and the corresponding RLC mode (i.e., AM, the RLC mode has not changed) to the second UE again.

[0103] In an embodiment of the present disclosure, an unused logical channel ID can be reallocated (replacing a previously allocated logical channel ID). Since an unused logical channel ID means that neither the first UE nor the second UE has configured the corresponding RLC mode, allocating an unused logical channel ID (e.g., LCID7) will not cause an RLC mode conflict. After allocating the unused LCID7, the first UE may send an RRCReconfigurationSidelink message carrying LCID7 and the RLC mode currently configured by the first UE (e.g., AM, the RLC mode has not changed) to the second UE. The second UE may use LCID7 and configure the corresponding RLC mode to the RLC mode carried by the RRCReconfigurationSidelink message (e.g., AM), and no RLC mode conflict will occur and subsequent reconfiguration may be successful. In an embodiment of the present disclosure, in the case where the second UE reconfigures the previously successful logical channel ID of the first UE, the successful logical channel ID may be reallocated. For example, if the second UE has sent a reconfiguration message to the first UE, and the reconfiguration is successful, and the LCID8 and the corresponding RLC mode are AM (i.e., its RLC mode is consistent with the RLC mode currently configured by the first UE), the first UE can reallocate LCID8, and send an RRCReconfigurationSidelink message carrying LCID8 and the corresponding RLC mode is AM to the second UE. Since the second UE has configured LCID8 and the corresponding RLC mode is AM, there will be no RLC mode conflict and the subsequent reconfiguration can be successful. In addition, in the case where the first UE stores multiple logical channel IDs of which the second UE has successfully reconfigured the first UE (when the second UE is the sending UE), the first UE can select a logical channel ID whose corresponding RLC mode is the RLC mode currently configured by the first UE (e.g., AM).

[0104] It should be understood that the above-mentioned logical channel IDs and corresponding modes are merely examples and the present disclosure is not limited thereto.

[0105] As described above, in the unicast side link communication method disclosed in the present invention, when the reconfiguration failure is caused by RLC mode conflict, the transmitting UE reallocates the logical channel ID by itself without the need for multiple wireless interactions with the network, thereby reducing processing delays. In this case, the logical channel ID is reallocated without adjusting at least one other SLRB parameter, which can fully guarantee the quality of service.

[0106] According to an embodiment of the present disclosure, the reconfiguration message may be updated according to the default SLRB resources based on determining that the cause of the reconfiguration failure is that at least one other side link radio bearer SLRB parameter is not applicable.

[0107] According to an embodiment of the present disclosure, updating the reconfiguration message according to the default SLRB resources may include: acquiring the default SLRB resources from different information according to the current state of the first UE; and updating the reconfiguration message according to the acquired default SLRB resources.

[0108] According to an embodiment of the present disclosure, obtaining the default SLRB resources in different information according to the current state of the first UE may include: releasing the current SLRB resource context; in response to being in a radio resource control RRC connected state, obtaining the default SLRB resources in an RRC reconfiguration message; in response to being in an RRC idle / inactive state, obtaining the default SLRB resources in a system information block SIB12 (SIB12 is a system information block containing information about NR side link communication); or in response to being in an out-of-coverage OOC state, obtaining the default SLRB resources in the side link preconfiguration information.

[0109] Figure 8 A default SLRB acquisition flow chart according to an embodiment of the present disclosure is shown.

[0110] If the first UE determines that the reason for the reconfiguration failure is that at least one other SLRB parameter carried in the RRCReconfigurationSidelink message is not applicable, the first UE will release the current SLRB resource and obtain the default SLRB resource. The current SLRB resource of the first UE may be the SLRB resource corresponding to the QoS parameter. Figure 8 , in operation S810, the first UE releases the SLRB resource context corresponding to the QoS parameters. Then, in operation S820, the first UE determines its current state. If the first UE is in the RRC_CONNECTED state, in operation S830, the first UE selects the default SLRB resource in the RRCReconfiguration message; if the first UE is in the RRC_IDLE / INACTIVE state, in operation S840, the first UE selects the default SLRB resource in SIB12; if the first UE is in the OOC state, in operation S850, the first UE selects the default SLRB resource in the SL-PreconfigurationNR.

[0111] In an embodiment of the present disclosure, if the UE is in the RRC_CONNECTED state, it means that the first UE has successfully accessed the network and is in normal communication with the base station. In this case, the first UE needs to find and select the default SLRB resource in the RRCReconfiguration message. If the first UE is in the RRC_IDLE / INACTIVE state, the first UE is in an idle or inactive state and cannot transmit data. In these states, the first UE will periodically listen to broadcast messages to obtain system information. At this time, the first UE can find and select the default SLRB resource in SIB12. SIB12 usually contains configuration information related to sidelink communication, which can help the first UE obtain the resources required for sidelink communication without restoring the RRC connection. If the first UE is in the OOC state, that is, the first UE is completely outside the network coverage area and cannot receive signals from the base station, the first UE will rely on the sidelink preconfiguration information for sidelink communication. In this case, the UE can find and select the default SLRB resource in the sidelink preconfiguration SL-PreconfigurationNR information. SL-PreconfigurationNR contains preconfigured sidelink communication parameters and resource information that the UE can use when it is in the OOC state. After acquiring the default SLRB resource, the first UE may release the current logical channel ID, and may reselect the logical channel ID corresponding to the logical channel configured with the same RLC mode according to the RLC mode in the parameter corresponding to the default SLRB resource. Here, the RLC mode corresponding to the reselected logical channel ID should be consistent with the RLC mode in the parameter corresponding to the default SLRB resource, and the method for reselecting the logical channel ID may refer to the method for reallocating the logical channel ID in the above-mentioned RLC mode conflict scenario.

[0112] After acquiring the default SLRB resources, the first UE also reconfigures the second UE. The first UE may update the RRCReconfigurationSidelink message according to the parameters corresponding to the default SLRB resources. In operation S860, the first UE sends the updated RRCReconfigurationSidelink message to the first UE. Specifically, the first UE may send the RRCReconfigurationSidelink message including the parameters corresponding to the default SLRB resources to the second UE. In addition, the updated RRCReconfigurationSidelink message may also include the reselected logical channel ID. The second UE that receives the updated RRCReconfigurationSidelink message may no longer encounter the abnormal situation that at least one other SLRB parameter is not applicable, and may reconfigure successfully.

[0113] In an embodiment of the present disclosure, after the first UE receives the RRCReconfigurationFailureSidelink message, the upper layer configuration may initiate optimization processing of the reconfiguration failure. In this case, if the RRCReconfigurationFailureSidelink message does not include the extended field sl-RLC-Mode-Conflict, the first UE may update the reconfiguration message according to the default SLRB resources. That is, in this case, regardless of whether the cause of the reconfiguration failure is an RLC mode conflict, it is handled with reference to the above-mentioned "at least one other SLRB parameter is not applicable" abnormal situation, and the first UE will obtain the default SLRB resources and reconfigure the second UE.

[0114] As described above, the unicast side link communication method disclosed in the present invention obtains the default SLRB parameter configuration when the reason for the reconfiguration failure is that at least one other SLRB parameter is not applicable, and the default SLRB resources corresponding to the RRC state will be fully utilized, and the side link service cannot be carried out normally under this abnormal situation, thereby improving the security and reliability of communication.

[0115] Fig. 9 FIG. 2 shows a second UE reconfiguration success flow chart according to an embodiment of the present disclosure. Fig. 9 In operation S910, the second UE receives an RRCReconfigurationSidelink message, which may be an updated RRCReconfigurationSidelink message sent by the first UE. After receiving the RRCReconfigurationSidelink message, in operation S920, the second UE reconfigures each layer successfully. And in the case of successful reconfiguration, in operation S930, the second UE sends an RRCReconfigurationCompleteSidelink message to the first UE.

[0116] Fig.10 FIG. 2 shows a first UE reconfiguration success flow chart according to an embodiment of the present disclosure. Fig.10 In operation S1010, the first UE receives an RRCReconfigurationCompleteSidelink message sent by the second UE. After receiving the RRCReconfigurationCompleteSidelink message sent by the second UE, in operation S1020, the first UE configures each layer successfully. And in the case of successful configuration, in operation S1030, the first UE can perform unicast sidelink communication normally.

[0117] As described above, the method for unicast side link communication disclosed in the present invention adopts different processing methods according to whether the cause of reconfiguration failure is RLC mode conflict. In the abnormal case where the cause of side link reconfiguration failure is RLC mode conflict, the method can reallocate the logical channel ID without adjusting other SLRB parameters, which can fully guarantee the quality of service and achieve the same communication effect as normal. In the case where the cause of side link reconfiguration failure is not RLC mode conflict (that is, the cause of reconfiguration failure is that at least one other SLRB parameter is not applicable), the method can adopt the default SLRB parameter configuration, which will affect the quality of service to a certain extent, but can ensure the reliability and continuity of communication under abnormal conditions. In addition, the mode of selecting the default SLRB resource by the transmitting UE (that is, the first UE) can reduce the conflict of SLRB resources, and the selected default SLRB resource can be more matched with the transmitting UE capability (for example, the UE capability reported by the UE in the network mode). Therefore, the embodiment of the method for unicast side link communication disclosed in the present invention can optimize the processing of reconfiguration failure according to whether the cause of reconfiguration failure is RLC mode conflict, which can maximize the quality of service and the robustness and security of communication.

[0118] In addition, the embodiments of the unicast side link communication method disclosed in the present invention may not limit the status of the UE and may be applicable to the in-coverage (IC) and out-of-coverage (OOC) states of the UE, and the method may achieve high reliability and low latency when applied in specific fields (for example, vehicle-to-everything (V2X)).

[0119] Fig.11 A flowchart of a method for unicast sidelink communication applied to a second UE according to an embodiment of the present disclosure is shown.

[0120] In operation S1110, a reconfiguration message sent by a first UE is received.

[0121] In operation S1120, in response to a reconfiguration failure associated with the reconfiguration message, a reconfiguration failure message including a reconfiguration failure cause is sent to the first UE.

[0122] According to an embodiment of the present disclosure, sending a reconfiguration failure message including a reconfiguration failure cause to a first UE may include: using the received reconfiguration message to set an extension field included in the reconfiguration failure message according to whether an RLC mode conflict occurs for the same logical channel; and sending a reconfiguration failure message including the reconfiguration failure cause indicated by the extension field to the first UE.

[0123] In operation S1130, an updated reconfiguration message sent by the first UE is received, wherein the updated reconfiguration message is a reconfiguration message updated by the first UE based on a reconfiguration failure reason.

[0124] According to an embodiment of the present disclosure, the first UE reallocates the logical channel identifier based on determining that the cause of the reconfiguration failure is an RLC mode conflict, and updates the reconfiguration message based on the reallocated logical channel identifier; or the first UE updates the reconfiguration message based on the default SLRB resources based on determining that the cause of the reconfiguration failure is that at least one other side link radio bearer SLRB parameter is not applicable.

[0125] According to an embodiment of the present disclosure, the logical channel identifier is a logical channel identifier different from the original logical channel identifier and reallocated by the first UE after releasing the original logical channel identifier and the related context.

[0126] According to an embodiment of the present disclosure, the logical channel identifier is an unused logical channel identifier reallocated by the first UE, or the logical channel identifier is a successful logical channel identifier reallocated by the first UE in the presence of a previously successful logical channel identifier when the second UE reconfigures the first UE.

[0127] According to an embodiment of the present disclosure, the first UE obtains a default SLRB resource from different information according to its current state, and updates a reconfiguration message according to the obtained default SLRB resource.

[0128] According to an embodiment of the present disclosure, the default SLRB resource is obtained by the first UE in the RRC reconfiguration message in response to the first UE being in a radio resource control RRC connected state after releasing the current SLRB resource context, obtained in the system information block SIB12 in response to the first UE being in an RRC idle / inactive state, or obtained in the side link preconfiguration information in response to the first UE being in an out-of-coverage OOC state.

[0129] Fig.12 A block diagram of a first UE according to an embodiment of the present disclosure is shown.

[0130] Reference Fig.12 The first UE 1200 includes a sending circuit 1210, a receiving circuit 1220 and an updating circuit 1230, wherein the sending circuit 1210 can send a reconfiguration message to the second UE and send the updated reconfiguration message to the second UE, the receiving circuit 1220 can receive a reconfiguration failure message, the reconfiguration failure message indicates a reconfiguration failure associated with the reconfiguration message, is sent by the second UE in response to the reconfiguration failure and includes a reconfiguration failure cause, and the updating module 1230 can update the reconfiguration message based on the reconfiguration failure cause to generate an updated reconfiguration message.

[0131] According to an embodiment of the present disclosure, the reconfiguration failure cause is indicated by an extension field included in the reconfiguration failure message, wherein the extension field is set by the second UE using the received reconfiguration message according to whether an RLC mode conflict of the same logical channel occurs.

[0132] According to an embodiment of the present disclosure, the update circuit 1230 may reallocate the logical channel identifier based on determining that the cause of the reconfiguration failure is an RLC mode conflict, and update the reconfiguration message based on the reallocated logical channel identifier; or update the reconfiguration message based on the default SLRB resources based on determining that the cause of the reconfiguration failure is that at least one other side link radio bearer SLRB parameter is not applicable.

[0133] According to an embodiment of the present disclosure, the first UE may further include: an optimization start circuit (not shown), wherein the optimization start circuit may check whether the optimization processing of the reconfiguration failure is started via the upper layer configuration after receiving the reconfiguration failure message; and when the optimization processing of the reconfiguration failure is started, determine whether the cause of the reconfiguration failure is an RLC mode conflict.

[0134] According to an embodiment of the present disclosure, the updating circuit 1230 may release the original logical channel identifier and the related context, and reallocate a logical channel identifier different from the original logical channel identifier.

[0135] According to an embodiment of the present disclosure, the updating circuit 1230 may reallocate an unused logical channel identifier, or reallocate a successful logical channel identifier when the second UE reconfigures the previous successful logical channel identifier of the first UE.

[0136] According to an embodiment of the present disclosure, the updating circuit 1230 may obtain a default SLRB resource from different information according to a current state of the first UE; and update a reconfiguration message according to the obtained default SLRB resource.

[0137] According to an embodiment of the present disclosure, the update circuit 1230 may release the current SLRB resource context; in response to being in a radio resource control RRC connected state, obtain the default SLRB resource in the RRC reconfiguration message; in response to being in an RRC idle / inactive state, obtain the default SLRB resource in the system information block SIB12; or in response to being in an out-of-coverage OOC state, obtain the default SLRB resource in the side link preconfiguration information.

[0138] Fig.13 A block diagram of a second UE according to an embodiment of the present disclosure is shown.

[0139] Reference Fig.13The second UE 1300 includes a receiving circuit 1310 and a sending circuit 1320, wherein the receiving circuit 1310 can receive a reconfiguration message sent by the first UE, and receive an updated reconfiguration message sent by the first UE, and the sending circuit 1320 can send a reconfiguration failure message including a reconfiguration failure cause to the first UE in response to a reconfiguration failure related to the reconfiguration message, wherein the updated reconfiguration message is a reconfiguration message updated by the first UE based on the reconfiguration failure cause.

[0140] According to an embodiment of the present disclosure, the sending module 1320 may use the received reconfiguration message to set the extension field included in the reconfiguration failure message according to whether an RLC mode conflict occurs for the same logical channel; and send a reconfiguration failure message including the cause of the reconfiguration failure indicated by the extension field to the first UE.

[0141] Fig.14 A system for unicast sidelink communication according to an embodiment of the present disclosure is shown.

[0142] Reference Fig.14 , a system 1400 for unicast sidelink communication includes a first UE 1410 and a second UE 1420. The first UE 1410 may send a reconfiguration message to the second UE 1420; receive a reconfiguration failure message, the reconfiguration failure message indicating a reconfiguration failure associated with the reconfiguration message, sent by the second UE 1420 in response to the reconfiguration failure and including a reconfiguration failure cause; update the reconfiguration message based on the reconfiguration failure cause; and send the updated reconfiguration message to the second UE 1420. The second UE 1420 may receive the reconfiguration message sent by the first UE 1410; send a reconfiguration failure message including a reconfiguration failure cause to the first UE 1410 in response to the reconfiguration failure associated with the reconfiguration message; and receive the updated reconfiguration message sent by the first UE 1410.

[0143] In addition, regarding Fig.14 Any relevant details involved in the operations performed by the first UE 1410 and the second UE 1420 can be found in Fig.12 and Fig.13 The corresponding description will not be repeated here.

[0144] Fig.15 A block diagram of an electronic device according to an embodiment of the present disclosure is shown.

[0145] The electronic device 1500 may be the first UE (Tx UE) or the second UE (Rx UE) of the embodiment of the present disclosure. Fig.15The electronic device 1500 may include at least one memory 1510 and at least one processor 1520, wherein the at least one memory stores a set of computer executable instructions, and when the computer executable instruction set is executed by the at least one processor, the method of unicast side link communication according to an embodiment of the present disclosure is executed.

[0146] Here, the electronic device is not necessarily a single electronic device, but may be any device or circuit collection that can execute the above instructions (or instruction sets) individually or jointly. The electronic device may also be part of an integrated control system or system manager, or may be configured as a portable electronic device that is interconnected with a local or remote (e.g., via wireless transmission) interface.

[0147] In electronic devices, the processor may include a central processing unit (CPU), a graphics processing unit (GPU), a programmable logic device, a dedicated processor system, a microcontroller or a microprocessor. As an example and not limitation, the processor may also include an analog processor, a digital processor, a microprocessor, a multi-core processor, a processor array, a network processor, etc.

[0148] The processor can execute instructions or codes stored in the memory, wherein the memory can also store data. Instructions and data can also be sent and received through the network via the network interface device, wherein the network interface device can adopt any known transmission protocol.

[0149] The memory may be integrated with the processor, for example, RAM or flash memory is arranged within an integrated circuit microprocessor or the like. In addition, the memory may include a separate device, such as an external disk drive, a storage array, or any other storage device that can be used by a database system. The memory and the processor may be operatively coupled, or may communicate with each other, such as through an I / O port, a network connection, etc., so that the processor can read files stored in the memory.

[0150] In addition, the electronic device may also include a video display (such as a liquid crystal display) and a user interaction interface (such as a keyboard, a mouse, a touch input device, etc.) All components of the electronic device may be connected to each other via a bus and / or a network.

[0151] In addition, the electronic device may be a device having wired and wireless communication capabilities, and may further include a transceiver to enable transmission and reception of communication signals.

[0152] According to an embodiment of the present disclosure, a computer-readable storage medium may also be provided, wherein a computer program is stored thereon, and when the program is executed, the method of unicast side link communication according to the present disclosure is implemented. Examples of computer-readable storage media here include: read-only memory (ROM), random access programmable read-only memory (PROM), electrically erasable programmable read-only memory (EEPROM), random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), flash memory, non-volatile memory, CD-ROM, CD-R, CD+R, CD-RW, CD+RW, DVD-ROM, DVD-R, DVD+R, DVD-RW, DVD+RW, DVD-RAM, BD-ROM, BD-R, BD-R LTH, BD-RE, Blu-ray or optical disk storage, hard disk drive (HDD), solid state drive (SSD), card storage (such as, multimedia card, secure digital (SD) card or extreme digital (XD) card), magnetic tape, floppy disk, magneto-optical data storage device, optical data storage device, hard disk, solid state disk and any other device, any other device is configured to store computer programs and any associated data, data files and data structures in a non-transitory manner and provide the computer programs and any associated data, data files and data structures to a processor or computer so that the processor or computer can execute the computer program. The computer program in the above-mentioned computer-readable storage medium can be run in an environment deployed in a computer device such as a terminal, a client, a host, an agent device, a server, etc. In addition, in one example, the computer program and any associated data, data files and data structures are distributed on a networked computer system, so that the computer program and any associated data, data files and data structures are stored, accessed and executed in a distributed manner by one or more processors or computers.

[0153] The method and apparatus for unicast side link communication disclosed in the present invention as described above optimize the processing of reconfiguration failures according to whether the cause of reconfiguration failure is an RLC mode conflict. In the abnormal case where the cause of side link reconfiguration failure is an RLC mode conflict, the logical channel ID is reallocated without adjusting other SLRB parameters, which can fully guarantee the quality of service and achieve the same communication effect as in normal situations. In the case where the cause of side link reconfiguration failure is not an RLC mode conflict (i.e., the cause of reconfiguration failure is that at least one other SLRB parameter is not applicable), the default SLRB parameter configuration can be used. Although it will affect the quality of service, it can ensure the reliability and continuity of communication in abnormal situations. In addition, the way in which the default SLRB resource is selected by the transmitting UE can reduce the conflict of SLRB resources, and the selected default SLRB resource can be more matched with the transmitting UE capability. The method and apparatus for unicast side link communication disclosed in the present invention can provide more reliable quality of service, more robust communication capabilities and safer performance.

[0154] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. The present disclosure is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The embodiments provided in the specification are to be considered as exemplary only, and the true scope and spirit of the present disclosure are indicated by the following claims.

[0155] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A method for unicast sidelink communication, performed by a first user equipment UE, the method comprising: Sending a reconfiguration message to the second UE; receiving a reconfiguration failure message, the reconfiguration failure message indicating a reconfiguration failure associated with the reconfiguration message, sent by the second UE in response to the reconfiguration failure and including a reconfiguration failure cause; Based on the reconfiguration failure reason, updating the reconfiguration message; as well as The updated reconfiguration message is sent to the second UE.

2. The method of claim 1, wherein: The updating of the reconfiguration message based on the reconfiguration failure reason includes: Based on determining that the reconfiguration failure reason is an RLC mode conflict, reallocating a logical channel identifier, and updating a reconfiguration message according to the reallocated logical channel identifier; or Based on determining that the reconfiguration failure reason is that at least one other side link radio bearer SLRB parameter is not applicable, the reconfiguration message is updated according to the default SLRB resources.

3. The method of claim 2, wherein: The reallocating of the logical channel identifier comprises: Release the original logical channel identifier and related context; and A logical channel identifier different from the original logical channel identifier is reallocated.

4. The method of claim 3, wherein: The reallocating of a logical channel identifier different from an original logical channel identifier includes: reallocate unused logical channel identities; or In case that the second UE reconfigures the previously successful logical channel identifier of the first UE, the successful logical channel identifier is reallocated.

5. The method of claim 2, wherein: The updating of the reconfiguration message according to the default SLRB resource includes: Obtaining a default SLRB resource from different information according to a current state of the first UE; and Update the reconfiguration message based on the acquired default SLRB resources.

6. A method for unicast sidelink communication, performed by a second user equipment UE, the method comprising: Receiving a reconfiguration message sent by the first UE; In response to a reconfiguration failure associated with the reconfiguration message, sending a reconfiguration failure message including a reconfiguration failure cause to the first UE; as well as receiving an updated reconfiguration message sent by the first UE, The updated reconfiguration message is a reconfiguration message updated by the first UE based on the reconfiguration failure reason.

7. A first user equipment UE, comprising: a sending circuit configured to send a reconfiguration message to the second UE, and send the updated reconfiguration message to the second UE; a receiving circuit configured to receive a reconfiguration failure message, the reconfiguration failure message indicating a reconfiguration failure associated with the reconfiguration message, sent by the second UE in response to the reconfiguration failure and including a reconfiguration failure cause; as well as The updating circuit is configured to update the reconfiguration message based on the reconfiguration failure reason to generate an updated reconfiguration message.

8. A second user equipment UE, comprising: A receiving circuit configured to receive a reconfiguration message sent by the first UE, and receive an updated reconfiguration message sent by the first UE; as well as a sending circuit, configured to send a reconfiguration failure message including a reconfiguration failure cause to the first UE in response to a reconfiguration failure associated with the reconfiguration message, The updated reconfiguration message is a reconfiguration message updated by the first UE based on the reconfiguration failure reason.

9. An electronic device, characterized in that: include: processor; as well as A memory storing a computer program, wherein when the computer program is executed by a processor, the method according to any one of claims 1 to 6 is implemented.

10. A computer-readable storage medium, characterized in that: A computer program is stored thereon, and when the program is executed, the method according to any one of claims 1 to 6 is implemented.

Images