Method and apparatus for indicating user equipment capabilities in sidelink transmission

Abstract

To provide a marking method and a marking device for user equipment capability in side-link transmission.SOLUTION: A mechanism that effectively marks UE capability can be provided, because, by using one specific user equipment ID to mark UE capability of a target UE, a transmitting end UE can provide settings that do not exceed the target UE capability and related information for maintaining the target UE based on the UE capability of the target UE.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] The present invention relates to the field of communications, and particularly to a method and apparatus for identifying user equipment capabilities in sidelink transmission.

Background Art

[0002] A communication service that connects vehicles and things is called a V2X service. The V2X service includes multiple types of services, such as Vehicle-to-Vehicle (V2V) communication service, Vehicle-to-Infrastructure (V2I) communication service, Vehicle-to-Pedestrian (V2P) communication service, etc. The V2X service can be provided by the PC5 interface and / or the Uu interface. The V2X service transmitted by the PC5 interface is provided by V2X sidelink communication, which is a communication mode in which user equipment (UE) can communicate directly with each other via the PC5 interface. In Long Term Evolution (LTE) or New Radio (NR), the UE can support the above-mentioned communication mode whether it is inside or outside the network coverage.

[0003] In conventional V2X communication, data is transmitted between vehicles as user equipment (UE) via the PC5 interface on the sidelink, and data is transmitted between the UE and the network equipment (NE) via the Uu interface by the uplink and downlink. In the sidelink, the UE that transmits data is called the transmitting-end UE or source UE, and the UE that receives data is called the receiving-end UE or destination UE.

[0004] The above-mentioned introduction of background art is intended to clearly and completely explain the proposed technical aspects of the present invention and to facilitate understanding by those skilled in the art. These technical aspects, as described in the background art of the present invention, should not be construed as being well-known to those skilled in the art. [Overview of the project] [Problems that the invention aims to solve]

[0005] Currently, the 3GPP (Third Generation Partnership Project) has agreed that a UE context is stored for a single target UE, and the UE context for sidelink transmission (SL UE context) may include at least the UE capability for sidelink transmission of the target UE. However, it is still undetermined whether access layer (AS layer) configuration information is also included in the UE capability for sidelink transmission. It has also been acknowledged that a UE can store the UE capability of the target UE for newly arriving services between two UEs in unicast, such as newly arriving unicast services, and that PC5-RRC connectivity supports synchronization between SL UE contexts between the two UEs.

[0006] The inventors have discovered that in LTE V2X, there is a correspondence between the destination layer-2 address (destination layer-2 ID, destination L2 ID) and the V2X service type. In NR V2X, there is discussion as to whether there is a correspondence between the cast mode (a transmission type, including unicast, groupcast, and broadcast) and the destination layer-2 address. In the SA2 discussion, multiple unicast services or unicast links between one UE and its peer UE may use the same or different source layer-2 addresses (source L2 ID). Therefore, for example, when multiple unicast services or unicast links exist between two UEs, it is currently not determined whether the source layer-2 address and / or destination layer-2 address have a one-to-one correspondence with the destination UE, and thus the problem of how to label the UE capabilities of the destination UE needs to be solved.

[0007] Embodiments of the present invention provide a method and apparatus for labeling user equipment capabilities in sidelink transmission, and since the UE capability of a target UE is labeled using a single specific user equipment ID, it can provide a mechanism for effectively labeling UE capabilities. [Means for solving the problem]

[0008] According to a first aspect of an embodiment of the present invention, a method for indicating user equipment capability (UE context) in sidelink transmission is provided, the method is applied to the first user equipment side, and the method is The user device capability of the second user device is identified using one of the following user device IDs (UE IDs): namely, one layer 2 address (L2 ID); one address pair consisting of one source layer 2 address (source L2 ID) and one destination layer 2 address; one access layer (AS layer) ID; one link ID; and one identifier used when the second user device transmits a PC5-RRC message, of which the sidelink transmission is the sidelink transmission between the first user device and the second user device.

[0009] According to a second aspect of the embodiment of the present invention, a method for indicating user equipment capability (UE context) in sidelink transmission is provided, the method being applied to the second user equipment side, and the method is This includes providing the first user device with the following user device ID (UE ID) so that the first user device uses the user device ID to indicate the user device capability of the second user device, namely, one destination L2 ID; one address pair consisting of one source L2 ID and one destination L2 address; one link ID; one access layer (AS layer) ID; and one identifier used by the second user device when transmitting PC5-RRC messages, of which the sidelink transmission is the sidelink transmission between the first user device and the second user device.

[0010] According to a third aspect of the embodiment of the present invention, a user equipment capability (UE context) indicator device in sidelink transmission is provided, the device is applied to the first user equipment side, and the device is The first marker unit includes a first marker unit which marks the user device capability of the second user device using one of the following user device IDs (UE IDs): namely, one Layer 2 address (L2 ID); one address pair consisting of one source Layer 2 address (source L2 ID) and one destination Layer 2 address; one access layer (AS layer) ID; one link ID; and one marker used when the second user device transmits a PC5-RRC message, of which the sidelink transmission is the sidelink transmission between the first user device and the second user device.

[0011] According to a fourth aspect of an embodiment of the present invention, a user equipment capability (UE context) indicator device in sidelink transmission is provided, the device is applied to the second user equipment side, and the device is The first providing unit includes, by providing the first user device with the following one user device ID (UE ID), so that the first user device uses the user device ID to identify the user device capability of the second user device, namely, one destination L2 ID; one address pair consisting of one source L2 ID and one destination L2 address; one link ID; one access layer (AS layer) ID; and one identifier used by the second user device when transmitting PC5-RRC messages, of which the sidelink transmission is the sidelink transmission between the first user device and the second user device.

[0012] According to a fifth aspect of the embodiment of the present invention, a user device is provided, which includes the device described in the third or fourth aspect of the embodiment of the present invention.

[0013] According to the sixth aspect of an embodiment of the present invention, a communication system is provided, the communication system including the user device described in the fifth aspect of an embodiment of the present invention.

[0014] According to the seventh aspect of an embodiment of the present invention, a computer-readable program is provided, and when the program is executed in a user-enhanced device or user device for identifying user-enhanced device (UE context) in sidelink transmission, the program causes the user-enhanced device or user device for identifying user-enhanced device (UE context) in sidelink transmission to execute the user-enhanced device (UE context) identification method for sidelink transmission described in the first or second aspect of an embodiment of the present invention.

[0015] According to the eighth aspect of an embodiment of the present invention, a storage medium is provided which stores a computer-readable program, the computer-readable program causing a user-enhanced device (UE context) indicator device or user device in sidelink transmission to execute the user-enhanced device (UE context) indicator method in sidelink transmission described in the first or second aspect of an embodiment of the present invention. [Effects of the Invention]

[0016] The advantageous effects of the present invention are as follows: By using a specific user device ID to label the UE capability of the target UE, the transmitting end UE can provide settings that do not exceed the target UE capability, and related information for maintaining the target UE, thereby providing a mechanism for effectively labeling UE capability.

[0017] Specific embodiments of the present invention will be disclosed in detail by referring to the following description and drawings, and will show how the principles of the present invention can be employed. However, the embodiments of the present invention are not limited to these in scope. Within the scope of the attached claims, embodiments of the present invention may include various changes, modifications and substitutions.

[0018] Furthermore, features described and / or shown for one embodiment may be used in the same or similar manner in one or more other embodiments, combined with or substituting features in other embodiments.

[0019] Note that terms such as "comprising / including" when used in this specification refer to the presence of features, elements, steps, or assemblies, but also refer to the fact that they do not exclude the presence or addition of one or more other features, elements, steps, or assemblies.

Brief Description of the Drawings

[0020] The included drawings are used to provide a further understanding of the embodiments of the present invention. These drawings form part of this specification, illustrate the embodiments of the present invention, and are used together with the written description to explain the principles of the present invention. Also, as is clear, the drawings described below are merely for showing some embodiments of the present invention, and those skilled in the art can obtain other drawings based on these drawings without creative labor. [Figure 1] It is a diagram showing a communication system according to an embodiment of the present invention. [Figure 2] It is a diagram showing a protocol stack of a PC5 interface according to an embodiment of the present invention. [Figure 3] It is a diagram showing a method for labeling user equipment capabilities in sidelink transmission according to Embodiment 1 of the present invention. [Figure 4] It is a diagram showing the labeling method of Example 1.1 in Embodiment 1 of the present invention. [Figure 5] It is a diagram showing information interaction by the protocol stack of the PC5 interface in Example 1.1 in Embodiment 1 of the present invention. [Figure 6] It is a diagram showing the labeling method of Example 1.2 in Embodiment 1 of the present invention, and this method is applied on the UE1 side. [Figure 7] It is a diagram showing information interaction by the protocol stack of the PC5 interface in Example 1.2 in Embodiment 1 of the present invention. [Figure 8] It is another diagram showing information interaction by the protocol stack of the PC5 interface in Example 1.2 in Embodiment 1 of the present invention. [Figure 9]Another figure showing the information interaction by the protocol stack of the PC5 interface in Example 1.2 in Embodiment 1 of the present invention. [Figure 10] Another figure showing the labeling method of Example 1.2 in Embodiment 1 of the present invention. [Figure 11] Another figure showing the information interaction by the protocol stack of the PC5 interface in Example 1.2 in Embodiment 1 of the present invention. [Figure 12] A figure showing the labeling method of Example 2 in Embodiment 1 of the present invention. [Figure 13] A figure showing the information interaction by the protocol stack of the PC5 interface in Example 2 in Embodiment 1 of the present invention. [Figure 14] Another figure showing the labeling method of Example 2 in Embodiment 1 of the present invention. [Figure 15] Another figure showing the information interaction by the protocol stack of the PC5 interface in Example 2 in Embodiment 1 of the present invention. [Figure 16] Another figure showing the labeling method of Example 3 in Embodiment 1 of the present invention. [Figure 17] A figure showing the method for generating configuration information in sidelink transmission in Embodiment 1 of the present invention. [Figure 18] A figure showing the labeling method of user equipment capabilities in sidelink transmission according to Embodiment 2 of the present invention. [Figure 19] A figure showing the labeling method of user equipment capabilities in sidelink transmission according to Embodiment 3 of the present invention. [Figure 20] A figure showing the labeling device of user equipment capabilities (UE context) in sidelink transmission in Embodiment 4 of the present invention. [Figure 21] A figure showing the labeling device of user equipment capabilities (UE context) in sidelink transmission in Embodiment 5 of the present invention. [Figure 22] A system configuration diagram of a user equipment in Embodiment 6 of the present invention. [Figure 23] This is a system configuration diagram of the user device in Embodiment 7 of the present invention. [Modes for carrying out the invention]

[0021] The aforementioned and other features of the present invention will become clear by referring to the attached drawings and the following description. While the specification and drawings disclose specific embodiments of the present invention, they represent only a limited number of embodiments that may employ the principles of the present invention. It should be understood that the present invention is not limited to the embodiments described, that is, it includes all modifications, variations, and substitutions within the scope of the attached claims.

[0022] In embodiments of the present invention, the terms "communication network" or "wireless communication network" may refer to a network conforming to any communication standard such as LTE (Long Term Evolution), LTE-A (LTE-Advanced), WCDMA (Wideband Code Division Multiple Access), HSPA (High-Speed ​​Packet Access), etc.

[0023] Furthermore, communication between devices in a communication system may be carried out according to any stage of communication protocol, and may include, but is not limited to, the following communication protocols: namely, 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G and future 5G, New Radio (NR), and / or other conventional or future-developed communication protocols.

[0024] In embodiments of the present invention, the term "network device" refers, for example, to a device in a communication system that connects terminal devices to a communication network and provides services to said terminal devices. A network device may include, but is not limited to, the following: base stations (BS), access points (AP), transmission and reception points (TRP), broadcast transmitters, mobile management entities (MME), network gateways, servers, radio network controllers (RNC), base station controllers (BSC), etc.

[0025] Among these, base stations may include, but are not limited to, Node B (NodeB or NB), Evolutionary Node B (eNodeB or eNB), and 5G base stations (gNB), and may also include RRH (Remote Radio Head), RRU (Remote Radio Unit), relay, or low-power nodes (e.g., femto, pico). Furthermore, the term "base station" may include some or all of these functions, and each base station can provide communication coverage to a specific geographic area. The term "cell" may refer to a base station and / or the area it covers, depending on the context of the term.

[0026] In embodiments of the present invention, the terms "User Equipment" (UE) or "Terminal Equipment" (TE) refer to, for example, a device that accesses a communication network via a network device and receives services from the network. User equipment may be fixed or mobile, and may also be referred to as a mobile station (MS), terminal, subscriber station (SS), access terminal (AT), station, etc.

[0027] Among these, user devices may include, but are not limited to, the following: cellular phones, PDAs (Personal Digital Assistants), wireless modems, wireless communication devices, carrier devices, machine-type communication devices, laptop computers, cordless telephones, smartphones, smartwatches, digital cameras, etc.

[0028] Furthermore, in scenarios such as IoT (Internet of Things), the user device may also be a monitoring or measurement device or apparatus, and may include, but is not limited to, the following: machine-type communication (MTC) terminals, in-vehicle communication terminals, D2D (device-to-device) terminals, M2M (machine-to-machine) terminals, etc.

[0029] The following describes a scenario relating to an embodiment of the present invention with reference to practical examples, but the present invention is not limited thereto.

[0030] Figure 1 shows a communication system in an embodiment of the present invention, illustrating an example of a case involving user equipment and network equipment. As shown in Figure 1, the communication system 100 may include network equipment 101 and user equipment 102, 103, and 104, where user equipment 102, 103, and 104 are, for example, vehicles. Of these, network equipment 101 is optional.

[0031] In embodiments of the present invention, conventional traffic (services) or future traffic can be transmitted between the network device 101 and user devices 102, 103, and 104. This traffic may include, but is not limited to, eMBB (enhanced Mobile Broadband), mMTC (massive Machine Type Communication), URLLC (Ultra-Reliable and Low-Latency Communication), etc.

[0032] Services (operations) can be performed on a sidelink between user devices 102 and 103, and between user devices 102 and 104. These services include, but are not limited to, V2X services and D2D services. For example, user device 102 is the first user device UE1, i.e., the transmitting end UE; user device 103 is the second user device UE2; user device 104 is the third user device UE3; and UE2 and UE3 are the receiving end UEs.

[0033] For example, UE1 and UE2 perform two V2X services, namely Service 1 and Service 2, while UE1 and UE3 perform one V2X service, namely Service 3. UE1 needs to store the UE context of the target UE, namely the UE contexts of target UE2 and target UE3, and the UE context includes the UE capabilities of the UE, and may also include the corresponding AS layer configuration (FFS).

[0034] Figure 2 shows the protocol stack of a PC5 interface according to an embodiment of the present invention. As shown in Figure 2, communication between UE1 and UE2, which are configured as sidelinks, is performed by PC5-signalling (PC5-S) messages at the upper layer, which is either the PC5-Signalling layer (PC5-S layer), the V2X layer, or the V2X application layer, and communication at the RRC layer is performed by PC5-RRC messages. At the transmitting UE (e.g., UE1), the upper layer can communicate the source L2 ID of the transmitting UE and the destination L2 ID of the receiving UE to the MAC layer. Furthermore, the protocol stack may also include an SDAP protocol layer, which is, for example, below the PC5-S layer and above the PDCP layer (not shown).

[0035] In embodiments of the present invention, the upper layer may be an application layer, a V2X layer, or a PC5-S layer. The access layer (AS layer) may include at least one of the RRC layer, SDAP layer, PDCP layer, RLC layer, MAC layer, and PHY layer. [Examples]

[0036] An embodiment of the present invention provides a method for labeling user equipment capabilities in sidelink transmission, which is applied to the first user equipment side. Figure 3 shows a method for labeling user equipment capabilities in sidelink transmission according to Embodiment 1 of the present invention. As shown in Figure 3, the method includes the following steps.

[0037] Step 301: Use one of the following User Equipment IDs (UE IDs) to label the User Equipment Capability of the second User Equipment, i.e., One Layer 2 Address (L2 ID); A single address pair consisting of one source layer 2 address (source L2 ID) and one destination layer 2 address; One link ID; ID of one access layer (AS layer); and This is one of the indicators used when a second user device sends a PC5-RRC message. Of these, the sidelink transmission is the sidelink transmission between the first user equipment and the second user equipment.

[0038] In this way, by using a single specific user device ID to label the UE capability of the target UE, the transmitting end UE can provide settings that do not exceed the target UE capability, as well as related information for maintaining the target UE, thus providing a mechanism for effectively labeling UE capability.

[0039] In this embodiment, sidelink transmission can be performed between the first user device and the second user device. For example, the first user device is the transmitting end UE and is denoted as UE1, and the second user device is the receiving end UE and is denoted as UE2.

[0040] In this embodiment, the link ID is, for example, the PC5 link ID.

[0041] In this embodiment, the method may further include the following steps.

[0042] Step 302: Store the user device capabilities of the second user device after it has been labeled with the user device ID.

[0043] In this embodiment, the method may further include the following steps.

[0044] Step 303: Receive the PC5-RRC message from the second user device; Step 304: Based on the user device ID indicated by the PC5-RRC message, store all or part of the information in the PC5-RRC message in the user device capacity corresponding to the user device ID.

[0045] In this embodiment, the PC5-RRC message includes, for example, UE capability information of the second user device.

[0046] In this embodiment, the user device ID may be provided by one of the first user device, the second user device, and the network device.

[0047] In this embodiment, the user device ID may be provided by the upper layer or access layer (AS layer) of the first user device or the second user device.

[0048] In this embodiment, the user device ID may be explicitly or implicitly included in the PC5-S message or the PC5-RRC message.

[0049] For example, in an explicit case, the PC5-S message or PC5-RRC message directly contains the user device ID, while in an implicit case, the PC5-S message or PC5-RRC message does not directly contain the user device ID, and it must be obtained by parsing the ID corresponding to the message, for example, the user device ID is included by the target UE in the subheader of the MAC PDU corresponding to the message, for example, the source L2 ID.

[0050] The following describes, based on Example 1-3, the method for obtaining a user device ID to label the user device capabilities of the second user device in this embodiment, and the labeling process. For the sake of explanation, the first user device as the transmitting end UE will be referred to as UE1, and the second user device as the target UE will be referred to as UE2.

[0051] Example 1) The user device ID for identifying the user device capability of UE2 is a single layer 2 address provided by the upper layer of UE1 or UE2, or a single address pair consisting of a single source layer 2 address and a single target layer 2 address, or a single link ID. In this embodiment, we will explain using a single layer 2 address as an example, but the processing method is the same for a single address pair and a single link ID.

[0052] Example 1.1) When the upper layer uses one Layer 2 address for multiple links of one UE, or uses multiple Layer 2 addresses for multiple links of one UE, but different Layer 2 addresses are considered to correspond to different target UEs. For example, for two unicast services or unicast links from UE1 to UE2, the source layer 2 addresses assigned to these two unicast services or unicast links in UE2 are the same; in other words, for UE1, the destination layer 2 addresses of these two unicast services or unicast links are the same; and for UE1, the source layer 2 addresses used by multiple unicast services or unicast links may be the same or different.

[0053] Furthermore, for example, regarding two unicast services or unicast links from UE1 to UE2, the source layer 2 addresses assigned to these two unicast services or unicast links in UE2 are different. In other words, for UE1, the destination layer 2 addresses of these two unicast services or unicast links are different, and these two destination layer 2 addresses are processed as two destination UEs.

[0054] Figure 4 shows the labeling method of Example 1.1 in Embodiment 1 of the present invention, which is applied to the UE1 side. As shown in Figure 4, the method includes the following steps.

[0055] Step 401: UE2 receives a PC5-S message sent using UE2's Layer 2 address as the source Layer 2 address; Step 402: The upper layer of UE1 notifies the RRC layer of the Layer 2 address of UE2 as the Layer 2 address that identifies the user device capability of UE2; and Step 403: When the RRC layer of UE1 receives a PC5-RRC message from the layer 2 address or a PC5-RRC message containing the layer 2 address, it stores all or part of the information in the PC5-RRC message in the user device capability corresponding to the source layer 2 address.

[0056] Figure 5 shows the information interaction by the protocol stack of the PC5 interface in Example 1.1 of Embodiment 1 of the present invention. As shown in Figure 5, in step 501, UE1 sends a PC5-S Direct Communication Request to UE2 using a source layer 2 address (source L2 ID) (e.g., L2 ID1) and a specific destination layer 2 address (destination L2 ID) (e.g., L2 ID2 corresponding to the V2X service type). In step 502, the upper layer of UE2 uses the source layer 2 address L2 ID1, which UE1 uses when sending the PC5-S Direct Communication Request, as the destination layer 2 address to send the PC5-S Direct Communication Accept message, and also determines its own source layer 2 address (e.g., L2 ID3) to send the PC5-S Direct Communication Accept message. In step 503, UE2 sends the PC5-S Direct Communication Accept message to UE1. In step 504, the PC5-S layer of UE1 uses the layer 2 address of UE2 corresponding to the accepted message (i.e., L2 ID3). UE1 obtains ID3), and UE1 can further use the Layer 2 address L2 ID3 for subsequent communications of unicast services or unicast link signaling and data services to UE2. In step 505, the PC5-S layers of UE1 and UE2 each notify the RRC layer of the Layer 2 address (i.e., L2 ID3), and in step 506, UE2 sends to UE1 a PC5-RRC message, for example, containing UE capability information. Subsequently, the RRC layer of UE1, after receiving the PC5-RRC message from the Layer 2 address (i.e., L2 ID3), stores all or part of the information in the PC5-RRC message in the UE capability corresponding to the Layer 2 address.

[0057] Example 1.2) When the upper layer uses multiple Layer 2 addresses for multiple links of a single UE, and the multiple Layer 2 addresses should correspond to a single purpose. For example, for two unicast services or unicast links in UE2, the source layer 2 addresses used for these two unicast services or unicast links in UE2 are different. In other words, for UE1, the destination layer 2 addresses for these two unicast services or unicast links are different.

[0058] In such cases, the user device ID may be one of a plurality of Layer 2 addresses provided by the upper layer of UE1 or UE2, one of a plurality of such address pairs, or one of a plurality of such link IDs. In this embodiment, we will explain using one of a plurality of Layer 2 addresses as an example, but the processing method is the same for one of a plurality of address pairs and one of a plurality of such link IDs.

[0059] Figure 6 shows the labeling method of Example 1.2 in Embodiment 1 of the present invention, which is applied to the UE1 side. As shown in Figure 6, the method includes the following steps.

[0060] Step 601: The upper layer or RRC layer of UE1 determines the user device ID; Step 602: UE1 indicates the user device ID by a PC5-S message or a PC5-RRC message; and Step 603: After the RRC layer of UE1 receives a PC5-RRC message from the user device ID, it stores all or part of the information in the PC5-RRC message in the user device capacity corresponding to the user device ID.

[0061] Figure 7 shows the information interaction by the protocol stack of the PC5 interface in Example 1.2 of Embodiment 1 of the present invention, in which the user device ID is indicated by a PC5-S message. As shown in Figure 7, in step 701, UE1 and UE2 exchange PC5-S direct connection requests and received messages of the request, and the layer 2 address for indicating the user device capability of UE2 can be indicated to the other party by UE1 or UE2 by including it in the PC5-S message. In step 702, the PC5-S layers of UE1 and UE2 each notify the RRC layer of the layer 2 address, and in step 703, UE2 sends a PC5-RRC message to UE1, for example, a message containing user device capability information (UE capability information), which explicitly or implicitly includes the layer 2 address. The RRC layer of UE1 stores all or part of the information in the PC5-RRC message in the user device capability corresponding to the layer 2 address.

[0062] Figure 8 is another diagram showing the information interaction by the protocol stack of the PC5 interface in Example 1.2 of Embodiment 1 of the present invention, in which the user device ID is indicated by the PC5-RRC message. As shown in Figure 8, in step 801, UE1 and UE2 exchange PC5-S direct connection requests and messages confirming receipt of such requests; in step 802, the PC5-S layer of UE1 notifies the RRC layer of the layer 2 address, or the PC5-S layer of UE1 notifies the RRC layer of a list of layer 2 addresses, and optionally, the PC5-S layer of UE2 notifies the RRC layer of a list of layer 2 addresses; in step 803, if the RRC layer of UE1 received the layer 2 address in step 802, it sends the layer 2 address to UE2 by a PC5-RRC message; if the RRC layer of UE1 received a list of layer 2 addresses in step 802, the RRC layer of UE1 determines the layer 2 address and sends the determined layer 2 address to UE2 by a PC5-RRC message; in step 804, UE2 sends a PC5-RRC message to UE1, for example, user equipment capability information (UE capability). A message containing information is sent, and the PC5-RRC message explicitly or implicitly includes the layer 2 address. The RRC layer of UE1 stores all or part of the information in the PC5-RRC message in the user device capability corresponding to the layer 2 address.

[0063] Figure 9 is another diagram showing the information interaction by the protocol stack of the PC5 interface in Example 1.2 of Embodiment 1 of the present invention. As shown in Figure 9, in step 901, PC5-S direct connection requests and received messages for the request are exchanged between UE1 and UE2; in step 902, the PC5-S layer of UE2 notifies the RRC layer of a layer 2 address, or the PC5-S layer of UE2 notifies the RRC layer of a list of layer 2 addresses, and optionally, the PC5-S layer of UE1 notifies the RRC layer of a list of layer 2 addresses; in step 903, UE2 sends UE1 a PC5-RRC message, for example, a message containing user equipment capability information, which explicitly or implicitly includes the layer 2 address. The RRC layer of UE1 stores all or part of the information in the PC5-RRC message in the user equipment capability corresponding to the layer 2 address.

[0064] Furthermore, the case where PC5-S establishes a new link and / or service after UE1 and UE2 have exchanged user device capabilities is explained below.

[0065] Figure 10 is another diagram showing the labeling method of Example 1.2 in Embodiment 1 of the present invention, which is applied to the UE1 side. As shown in Figure 10, the method includes the following steps.

[0066] Step 1001: The upper layer of UE1 receives a user device ID from UE2 via a PC5-S message to indicate the user device capability of UE2; and Step 1002: The upper layer of UE1 notifies the RRC layer of the user device ID.

[0067] Figure 11 is another diagram showing the information interaction by the protocol stack of the PC5 interface in Example 1.2 of Embodiment 1 of the present invention. As shown in Figure 11, in step 1101, the RRC layer of UE2 notifies the PC5-S layer of a Layer 2 address for identifying the user device capability, or if the PC5-S layer of UE2 already knows the Layer 2 address for identifying the user device capability, then step 1101 is omitted; in step 1102, the PC5-S between UE1 and UE2 exchanges direct connection requests and received messages for establishing a new link and / or service, of which the Layer 2 address is explicitly included in the PC5-S message by UE2 to instruct UE1, or UE2 implicitly instructs UE1 to include the Layer 2 address as the source L2 ID when sending the PC5-S message to UE1; in step 1103, the PC5-S layer of UE1 notifies the RRC layer of the Layer 2 address, and optionally, information about the newly established link and / or service may also be notified to the RRC layer along with the Layer 2 address so that the RRC layer can update the user device capability.

[0068] Example 2) The user device ID used to identify the user device capabilities of UE2 is a single access layer ID.

[0069] In this embodiment, the ID of the access layer is one of the following identifiers, namely, A label or index assigned by the access layer; Cell Radio Network Temporary Indicator (C-RNTI) assigned by the network device to UE2; and These are the cellular wireless network temporary beacon and physical cell beacon (PCI) that the network device assigns to UE2.

[0070] Figure 12 shows the labeling method of Example 2 in Embodiment 1 of the present invention, which is applied to the UE1 side. As shown in Figure 12, the method includes the following steps.

[0071] Step 1201: UE1 indicates one access layer ID as the user device ID via the PC5-S message; Step 1202: When the RRC layer of UE1 receives a PC5-RRC message containing the access layer ID, it stores all or part of the information in the PC5-RRC message in the user device capability corresponding to the access layer ID.

[0072] Figure 13 shows the information interaction by the protocol stack of the PC5 interface in Example 2 of Embodiment 1 of the present invention. As shown in Figure 13, in step 1301, the RRC layer of UE1 notifies the PC5-S layer of the ID of one access layer, in step 1302, UE1 and UE2 exchange PC5-S direct connection requests and received messages for the request, of which the access layer ID is included in the PC5-S message by UE1 and instructed to UE2, in step 1303, the PC5-S layer of UE2 notifies the RRC layer of the ID of the access layer, and in step 1304, UE2 sends UE1 a PC5-RRC message containing the access layer ID, for example, a message containing user device capability information, in which the PC5-RRC message explicitly or implicitly includes the access layer ID. The RRC layer of UE1 stores all or part of the information in the PC5-RRC message in the user device capability corresponding to the access layer ID.

[0073] Figure 14 is another diagram showing the labeling method of Example 2 in Embodiment 1 of the present invention, which is applied to the UE1 side. As shown in Figure 14, the method includes the following steps.

[0074] Step 1401: UE1 receives one access layer ID as the user device ID via a PC5-S message; Step 1402: When the RRC layer of UE1 receives a PC5-RRC message containing the access layer ID, it stores all or part of the information in the PC5-RRC message in the user device capability corresponding to the access layer ID.

[0075] Figure 15 is another diagram showing the information interaction by the protocol stack of the PC5 interface in Example 2 in Embodiment 1 of the present invention. As shown in Figure 15, in step 1501, the RRC layer of UE2 notifies the PC5-S layer of an access layer ID, in step 1502, UE1 and UE2 exchange PC5-S direct connection requests and received messages for the request, in which the access layer ID is included in the PC5-S message by UE2 and instructed to UE1, or UE2 uses the access layer ID as the source L2 ID when sending the PC5-S message to UE1, in step 1503, the PC5-S layer of UE2 notifies the RRC layer of the access layer ID, and in step 1504, UE2 sends UE1 a PC5-RRC message containing the access layer ID, for example, a message containing user equipment capability information, in which the access layer ID is explicitly or implicitly included. The RRC layer of UE1 stores all or part of the information in the PC5-RRC message in the user device capacity corresponding to the access layer ID.

[0076] Example 3) The user device ID is one source layer 2 address or one access layer ID used by UE2 when sending PC5-RRC messages.

[0077] Figure 16 is another diagram showing the labeling method of Example 3 in Embodiment 1 of the present invention, which is applied to the UE1 side. As shown in Figure 16, the method includes the following steps.

[0078] Step 1601: UE1 receives a PC5-RRC message from UE2; Step 1602: UE1 parses the data packet corresponding to the PC5-RRC message and obtains one source layer 2 address or one access layer ID to be used when UE2 transmits the PC5-RRC message as the user device ID; and Step 1603: After the RRC layer of UE1 receives a PC5-RRC message containing the user device ID, it stores all or part of the information in the PC5-RRC message in the user device capacity corresponding to the user device ID.

[0079] For example, one source layer 2 address or one access layer ID as a user device ID is included in the subheader of the MAC PDU, and the MAC layer of UE1 notifies the RRC layer of an indicator corresponding to the PC5-RRC message in the process of transmitting the MAC SDU corresponding to the PC5-RRC message containing user device capability information to the upper layer.

[0080] In this embodiment, the process for specifying the user device ID may be similar to that in Examples 1 and 2, so a detailed explanation is omitted here.

[0081] The above examples 1-3 illustrate the method for obtaining a user device ID for labeling the user device capabilities of the second user device in this embodiment, and the process for labeling it.

[0082] In this embodiment, the method may further include the following steps.

[0083] The upper layer of UE1 notifies the RRC layer of at least one of the following pieces of information in order to generate the access layer (AS layer) configuration: one layer 2 address between UE1 and UE2; an address pair consisting of one source layer 2 address and one destination layer 2 address between UE1 and UE2; a link ID between UE1 and UE2; and QoS information for the service corresponding to the destination layer 2 address and / or address pair and / or link ID; The RRC layer of UE1 generates access layer configurations corresponding to the service or link based on at least one of the above pieces of information; and The generated access layer configuration is included in the user device capabilities of UE2.

[0084] For example, service QoS information may include the ID of the QoS flow corresponding to the service, the PQI (PC5 QoS Class Indicator), the communication range, and QoS parameters (including, for example, rate information).

[0085] Furthermore, the above steps can be performed independently. Figure 17 shows a method for generating configuration information in sidelink transmission according to Embodiment 1 of the present invention. As shown in Figure 17, the method includes the following steps.

[0086] Step 1701: The upper layer of UE1 notifies the RRC layer of at least one of the following pieces of information in order to generate the access layer (AS layer) configuration: one layer 2 address between UE1 and UE2; an address pair consisting of one source layer 2 address and one destination layer 2 address between UE1 and UE2; a link ID between UE1 and UE2; and QoS information for the service corresponding to the destination layer 2 address and / or address pair; Step 1702: The RRC layer of UE1 generates an access layer configuration corresponding to the service based on at least one of the above pieces of information; and Step 1703: Include the generated access layer configuration in the UE2 user device capabilities.

[0087] As can be seen from the above embodiment, by using a specific user device ID to label the UE capability of the target UE, the transmitting end UE can provide settings that do not exceed the target UE capability, and related information for maintaining the target UE, thereby providing a mechanism for effectively labeling UE capability. [Examples]

[0088] Embodiment 2 of the present invention further provides a method for indicating user device capabilities in sidelink transmission, the method being applied to the second user device side. Since this method corresponds to the method for indicating user device capabilities in sidelink transmission on the first user device side in Embodiment 1, redundant explanations of the same content are omitted here.

[0089] Figure 18 shows a method for indicating user equipment capabilities in sidelink transmission according to Embodiment 2 of the present invention. As shown in Figure 18, the method includes the following steps.

[0090] Step 1801: Provide the first user device with the following User Device ID (UE ID) so that the first user device can use the User Device ID to identify the user device capabilities of the second user device, namely, one destination L2 ID; one address pair consisting of one source L2 ID and one destination L2 ID; one access layer (AS layer) ID; one link ID; and one identifier used by the second user device when sending PC5-RRC messages. Of these, sidelink transmission refers to sidelink transmission between the first user equipment and the second user equipment.

[0091] In this embodiment, the user device ID may be provided by one of the first user device, the second user device, and the network device.

[0092] In this embodiment, the user device ID may be provided by the upper layer or access layer (AS layer) of the first user device or the second user device.

[0093] In this embodiment, the user device ID may be explicitly or implicitly included in the PC5-S message or the PC5-RRC message.

[0094] For example, in an explicit case, the PC5-S message or PC5-RRC message directly contains the user device ID; in an implicit case, the PC5-S message or PC5-RRC message does not directly contain the user device ID, and it must be obtained by parsing the ID corresponding to the message, for example, the user device ID may be included in a subheader of the MAC PDU by the target UE.

[0095] In this embodiment, since it corresponds to Example 1 in Example 1, the specific steps can be found by referring to the relevant descriptions of UE2 in Figures 5, 7, 8, 9, and 11 in Example 1, and a detailed explanation is omitted here.

[0096] For example, the user device ID may be a layer 2 address provided by the upper layer of the first or second user device, or an address pair consisting of a source layer 2 address and a destination layer 2 address, or a link ID. In this case, the method may further include the following steps: the second user device transmits the source layer 2 address of the second user device to the first user device by a PC5-S message.

[0097] In this embodiment, the user device ID may be one of a plurality of Layer 2 addresses provided by the upper layer of the first user device or the second user device, or one of a plurality of address pairs, or one of a plurality of link IDs. In this case, the method may further include the following steps: the upper layer or RRC layer of the second user device establishes the user device ID; and the second user device indicates the user device ID by a PC5-S message or a PC5-RRC message.

[0098] In this embodiment, if PC5-S establishes a new link and / or service after UE1 and UE2 have exchanged user device capabilities, the method may further include the following steps: namely, the RRC layer of the second user device notifies the upper layer of its user device ID; and the second user device instructs the first user device of its user device ID via a PC5-S message.

[0099] In this embodiment, the steps for executing UE2 can be found in the descriptions in Figures 13 and 15, as they correspond to Example 2 in Example 1. A detailed explanation of these steps is omitted here.

[0100] In this embodiment, since it corresponds to Example 3 in Embodiment 1, the steps for executing UE2 can be described by referring to the description of UE2 in Example 3 in Embodiment 1, and a detailed explanation is omitted here.

[0101] As can be seen from the above embodiment, by using a specific user device ID to label the UE capability of the target UE, the transmitting end UE can provide settings that do not exceed the target UE capability, and related information for maintaining the target UE, thereby providing a mechanism for effectively labeling UE capability. [Examples]

[0102] Embodiment 3 of the present invention further provides a method for indicating user equipment capabilities in sidelink transmission, and this method is applied to the first user side and the second user side. This method corresponds to Embodiments 1 and 2, and redundant explanations of the same content are omitted here.

[0103] Figure 19 shows a method for indicating user equipment capabilities in sidelink transmission according to Embodiment 3 of the present invention. As shown in Figure 19, the method includes the following steps.

[0104] Step 1901: Provide the first user device with the following one user device ID (UE ID): namely, one destination L2 ID; one address pair consisting of one source L2 ID and one destination L2 ID; one link ID; one access layer (AS layer) ID; and one identifier used by the second user device when sending PC5-RRC messages; Step 1902: Use the user device ID to label the user device capability of the second user device; Step 1903: Store the user device capabilities of the second user device after it has been labeled with the user device ID; Step 1904: The second user device sends a PC5-RRC message to the first user device indicating the user device ID; Step 1905: The first user device stores all or part of the information in the PC5-RRC message in the user device capacity corresponding to the user device ID indicated by the PC5-RRC message.

[0105] In this embodiment, the method for obtaining and labeling the user device ID can be found in the specific description in Example 1, and a detailed explanation is omitted here.

[0106] As can be seen from the above embodiment, by using a specific user device ID to label the UE capability of the target UE, the transmitting end UE can provide settings that do not exceed the target UE capability, and related information for maintaining the target UE, thereby providing a mechanism for effectively labeling UE capability. [Examples]

[0107] Embodiment 4 of the present invention provides a user equipment capability (UE context) indicator device in sidelink transmission, the device being located on the first user equipment side. Since the principle by which the device solves the problem is similar to the method in Embodiment 1, its specific implementation can be found by referring to the implementation of the method in Embodiment 1, and redundant explanations that are the same or relevant are omitted here.

[0108] Figure 20 shows a user equipment capability (UE context) indicator device in sidelink transmission in Embodiment 4 of the present invention, and as shown in Figure 20, the device 2000 includes the following:

[0109] First Identifier Unit 2001: Identifies the user device capability of the second user device using one of the following user device IDs (UE IDs): namely, one Layer 2 address (L2 ID); one address pair consisting of one source Layer 2 address (source L2 ID) and one destination Layer 2 address; one access layer (AS layer) ID; one link ID; and one identifier used when the second user device transmits a PC5-RRC message. Of these, the sidelink transmission is the sidelink transmission between the first user device and the second user device.

[0110] In this embodiment, the apparatus 2000 may further include the following:

[0111] Second memory unit 2002: Used to store the user device capabilities of the second user device after it has been labeled with the user device ID.

[0112] Furthermore, the apparatus 2000 may include the following:

[0113] First receiving unit 2003: receives PC5-RRC messages from the second user device; and First storage unit 2004: Used to store all or part of the information in the PC5-RRC message in the user device capacity corresponding to the user device ID, based on the user device ID indicated by the PC5-RRC message.

[0114] In this embodiment, the method for obtaining the user device ID and the method for labeling the user device capabilities using the user device ID can be found in the description in Example 1, and a detailed explanation is omitted here.

[0115] As can be seen from the above embodiment, by using a specific user device ID to label the UE capability of the target UE, the transmitting end UE can provide settings that do not exceed the target UE capability, and related information for maintaining the target UE, thereby providing a mechanism for effectively labeling UE capability. [Examples]

[0116] Embodiment 5 of the present invention provides a user equipment capability (UE context) indicator device in sidelink transmission, the device being located on the second user equipment side. The principle by which the device solves the problem is similar to the method in Embodiment 2, so its specific implementation can be found by referring to the implementation of the method in Embodiment 2, and redundant explanations that are the same or related are omitted here.

[0117] Figure 21 shows a device for indicating user equipment capability (UE context) in sidelink transmission in Embodiment 5 of the present invention, and as shown in Figure 21, the device 2100 includes the following:

[0118] First provision unit 2101: Provides the first user device with the following single user device ID (UE ID), thereby enabling the first user device to use the user device ID to identify the user device capabilities of the second user device, namely, one destination L2 address; one address pair consisting of one source L2 address and one destination L2 address; one link ID; one access layer (AS layer) ID; and one identifier used by the second user device when transmitting PC5-RRC messages. Of these, the sidelink transmission is the sidelink transmission between the first user device and the second user device.

[0119] In this embodiment, the method by which the first supply unit 2101 provides the user device ID to the first user device can be found in the descriptions in Examples 1 and 2, and a detailed explanation is omitted here.

[0120] As can be seen from the above embodiment, by using a specific user device ID to label the UE capability of the target UE, the transmitting end UE can provide settings that do not exceed the target UE capability, and related information for maintaining the target UE, thereby providing a mechanism for effectively labeling UE capability. [Examples]

[0121] Embodiments of the present invention provide a user device, which includes a user device capability (UE context) indicator in sidelink transmission as described in Embodiment 4.

[0122] Figure 22 is a system configuration diagram of a user device in Embodiment 6 of the present invention. As shown in Figure 22, the user device 2200 may include a processor 2210 and a memory 2220, the memory 2220 being connected to the processor 2210. Note that this figure is merely illustrative, and telecommunication functions or other functions can be realized by supplementing or substituting this structure with other types of structures.

[0123] In one implementation, the function of the user equipment capability (UE context) indicator in sidelink transmission can be integrated into the processor 2210.

[0124] The processor 2210 may be configured as follows, namely, using one of the following user device IDs (UE IDs) to identify the user device capability of the second user device, namely, one layer 2 address (L2 ID); one address pair consisting of one source layer 2 address (source L2 ID) and one destination layer 2 address; one access layer (AS layer) ID; one link ID; and one identifier used when the second user device transmits a PC5-RRC message, of which the sidelink transmission is the sidelink transmission between the first user device and the second user device.

[0125] In another implementation, the user equipment capability (UE context) indicator in sidelink transmission may be located separately from the processor 2210. For example, the user equipment capability (UE context) indicator in sidelink transmission may be configured as a chip connected to the processor 2210, and the function of the user equipment capability (UE context) indicator in sidelink transmission may be realized by the control of the processor 2210.

[0126] As shown in Figure 22, the user device 2200 may further include a communication module 2230, an input unit 2240, a display 2250, a power supply 2260, and the like. Note that the user device 2200 does not need to include all the components shown in Figure 22. Furthermore, the user device 2200 may include components not shown in Figure 22, for which related technologies can be consulted.

[0127] As shown in Figure 22, the processor 2210 may be referred to as a controller or operation control, and may include a microprocessor or other processing unit and / or logic unit, which can receive inputs and control the operation of each component of the user device 2200.

[0128] Among these, the memory unit 2220 includes, for example, one or more of a buffer, fresh memory flash storage, HDD, movable medium, volatile memory, non-volatile memory, or other suitable device, and can store various types of data and further store programs for executing related information. The processor 2210 can store and process information by executing the programs stored in the memory unit 2220. The functions of the other components are similar to those of conventional devices, so a detailed explanation of them is omitted here. In addition, each component of the user device 2200 may be realized by dedicated hardware, firmware, software, or a combination thereof, but all of these are within the scope of the present invention.

[0129] As can be seen from the above embodiment, by using a specific user device ID to label the UE capability of the target UE, the transmitting end UE can provide settings that do not exceed the target UE capability, and related information for maintaining the target UE, thereby providing a mechanism for effectively labeling UE capability. [Examples]

[0130] Embodiments of the present invention provide a user device, which includes a user device capability (UE context) indicator in sidelink transmission as described in Embodiment 5.

[0131] Figure 23 is a system configuration diagram of a user device in Embodiment 7 of the present invention. As shown in Figure 23, the user device 2300 may include a processor 2310 and a memory 2320, with the memory 2320 connected to the processor 2310. Note that this figure is merely illustrative, and other types of structures may be used to supplement or substitute this structure to realize telecommunication functions or other functions.

[0132] In one implementation, the function of the user equipment capability (UE context) indicator in sidelink transmission can be integrated into the processor 2310.

[0133] The processor 2310 may be configured as follows: by providing the first user device with the following user device ID (UE ID), the first user device will use the user device ID to indicate the user device capability of the second user device, namely, one layer 2 address (destination L2 ID); one address pair consisting of one source layer 2 address (source L2 ID) and one destination layer 2 address; one link ID; one access layer (AS layer) ID; and one indicator used by the second user device when transmitting a PC5-RRC message, the sidelink transmission being the sidelink transmission between the first user device and the second user device.

[0134] In another implementation, the user equipment capability (UE context) indicator in sidelink transmission may be located separately from the processor 2310. For example, the user equipment capability (UE context) indicator in sidelink transmission may be configured as a chip connected to the processor 2310, and the function of the user equipment capability (UE context) indicator in sidelink transmission may be realized by the control of the processor 2310.

[0135] As shown in Figure 23, the user device 2300 may further include a communication module 2330, an input unit 2340, a display unit 2350, a power supply 2360, and the like. However, the user device 2300 does not need to include all the components shown in Figure 23. Furthermore, the user device 2300 may include components not shown in Figure 23, for which related technologies can be consulted.

[0136] As shown in Figure 23, the processor 2310 may be referred to as a controller or operation control, and may include a microprocessor or other processing unit and / or logic unit, and the processor 2310 can receive inputs and control the operation of each component of the user device 2300.

[0137] Among these, the memory unit 2320 includes, for example, one or more of a buffer, fresh memory flash storage, HDD, movable medium, volatile memory, non-volatile memory, or other suitable device, and can store various types of data and further store programs for executing related information. The processor 2310 can store and process information by executing the programs stored in the memory unit 2320. The functions of the other components are similar to those of conventional devices, so a detailed explanation of them is omitted here. Furthermore, each component of the user device 2300 may be realized by dedicated hardware, firmware, software, or a combination thereof, but all of these are within the scope of the present invention.

[0138] As can be seen from the above embodiment, by using a specific user device ID to label the UE capability of the target UE, the transmitting end UE can provide settings that do not exceed the target UE capability, and related information for maintaining the target UE, thereby providing a mechanism for effectively labeling UE capability. [Examples]

[0139] Embodiments of the present invention provide a communication system, which includes the user device described in Embodiment 6 and the user device described in Embodiment 7.

[0140] For example, the configuration of the communication system can be seen in Figure 1. As shown in Figure 1, the communication system 100 includes a network device 101 and user devices 102, 103, and 104. User device 102 is the same as the user device described in Example 6, and user devices 103 and 104 are the same as the user devices described in Example 7. A detailed explanation of these is omitted here.

[0141] Furthermore, the network device 101 is optional.

[0142] As can be seen from the above embodiment, by using a specific user device ID to label the UE capability of the target UE, the transmitting end UE can provide settings that do not exceed the target UE capability, and related information for maintaining the target UE, thereby providing a mechanism for effectively labeling UE capability.

[0143] Furthermore, the above-described apparatus and method may be implemented by software or hardware, or by a combination of hardware and software. The present invention further relates to a computer-readable program as described below, that is, the program, when executed by a logic component, causes the logic component to implement the above-described apparatus or component, or to the logic component to implement the above-described various methods or steps. The logic component may be, for example, an FPGA (Field Programmable Gate Array), a microprocessor, or a processor used in a computer. The present invention further relates to a storage medium storing the above-described program, for example, a hard disk, a magnetic disk, an optical hard disk, a DVD, or a flash memory.

[0144] Furthermore, one or more combinations of the functional blocks shown in the drawings and / or one or more combinations of functional blocks may be implemented as a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic component, discrete gate or transistor logic component, discrete hardware assembly or any other suitable combination for performing the functions described herein. Also, one or more combinations of the functional blocks shown in the drawings and / or one or more combinations of functional blocks may further be configured as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors connected to a DSP by communication or any other combination.

[0145] Although preferred embodiments of the present invention have been described above, the present invention is not limited to these embodiments, and any modification to the present invention falls within the technical scope of the present invention as long as it does not deviate from the spirit of the invention.

[0146] Furthermore, the following additional information is disclosed regarding the above-mentioned embodiments.

[0147] (Note 1) A user equipment capability (UE capability) indicator device for sidelink transmission, applied to the first user equipment side, It includes a first indicator unit that marks the user device capability of the second user device using one of the following user device IDs (UE IDs): namely, one layer 2 address (L2 ID); one address pair consisting of one source layer 2 address (source L2 ID) and one destination layer 2 address; one access layer (AS layer) ID; one link ID; and one indicator used when the second user device transmits a PC5-RRC message. Among these, the side link transmission is a side link transmission between the first user device and the second user device, in the marking device.

[0148] (Note 2) The marking device described in Appendix 1, The user device ID is provided by one of the first user device, the second user device, and the network device, according to the identification device.

[0149] (Note 3) The marking device described in Appendix 1, The user device ID is provided by the upper layer or access layer of the first user device or the second user device, according to the identification device.

[0150] (Note 4) The marking device described in Appendix 1, The user device ID is explicitly or implicitly included in the PC5-S message or PC5-RRC message, and is an identifier device.

[0151] (Note 5) A marking device as described in any one of the appendices 1-4, A first receiving unit that receives PC5-RRC messages from the second user device; and An identification device further comprising a first storage unit that stores all or part of the information in the PC5-RRC message in a user device capacity corresponding to the user device ID, based on the user device ID indicated by the PC5-RRC message.

[0152] (Note 6) A marking device as described in any one of the appendices 1-4, Identifying device, wherein the user device ID is one layer 2 address provided by the upper layer of the first user device or the second user device, or one address pair consisting of one source layer 2 address and one destination layer 2 address, or one link ID.

[0153] (Note 7) The marking device described in Appendix 6, A second receiving unit that receives a PC5-S message transmitted by the second user device using the second user device's layer 2 address as the source layer 2 address; and A marking device further comprising a first notification unit that causes the upper layer of the first user device to notify the RRC layer of the layer 2 address of the second user device as a layer 2 address marking the user device capability of the second user device.

[0154] (Note 8) A marking device as described in any one of the appendices 1-4, Identifying device, wherein the user device ID is one of a plurality of layer 2 addresses provided by the upper layer of the first user device or the second user device, or one of a plurality of the address pairs, or one of a plurality of link IDs.

[0155] (Note 9) The marking device described in Appendix 8, An indicator device further comprising a first instruction unit that causes the first user device to indicate the user device ID by a PC5-S message or a PC5-RRC message.

[0156] (Note 10) The marking device described in Appendix 9, A marking device further includes a first determination unit that causes the upper layer or RRC layer of the first user device to establish the user device ID.

[0157] (Note 11) The marking device described in Appendix 8, When the first user device and the second user device exchange user device capabilities, A second receiving unit that causes the upper layer of the first user device to receive the user device ID from the second user device via a PC5-S message to indicate the user device capability of the second user device; and A marking device further comprising a second notification unit that causes the upper layer of the first user device to notify the RRC layer of the user device ID.

[0158] (Note 12) A marking device as described in any one of the appendices 1-4, A marking device further comprising a second instruction unit that causes the first user device to indicate one access layer ID as the user device ID by a PC5-S message.

[0159] (Note 13) The marking device described in Appendix 12, The access layer ID, which is the user device ID, is one of the following identifiers, namely, An identifier or index assigned by the access layer; A network device assigns a Cell Radio Network Temporary Identifier (C-RNTI) to the second user device; and A marking device which is a cell wireless network temporary marking and a physical cell marking (PCI) assigned by the network device to the second user device.

[0160] (Note 14) A marking device as described in any one of the appendices 1-4, The user device ID is an identifier device, which is one source layer 2 address or one access layer ID used by the second user device when it transmits a PC5-RRC message.

[0161] (Note 15) The marking device described in Appendix 14, A third receiving unit that causes the first user device to receive the PC5-RRC message from the second user device; and An identification device further comprising a first analysis unit that causes the first user device to analyze the PC5-RRC message to obtain one source layer 2 address or one access layer ID as the user device ID.

[0162] (Note 16) The marking device described in Appendix 15, An identifier device in which one source layer 2 address or one access layer ID as the user device ID is included in the subheader of the MAC PDU.

[0163] (Note 17) A marking device as described in any one of the appendices 1-4, A marking device further comprising a second storage unit for storing the user device capabilities of a second user device after it has been marked using the user device ID.

[0164] (Note 18) A marking device as described in any one of the appendices 1-4, The above first user device further includes a third notification unit that causes the upper layer to notify the RRC layer of at least one of the following pieces of information in order to generate the access layer (AS layer) settings, namely, One layer 2 address between the first user device and the second user device; An address pair consisting of one source layer 2 address and one destination layer 2 address between the first user device and the second user device; and An indicator device that provides QoS information for the service corresponding to the aforementioned objective layer 2 address and / or the address pair.

[0165] (Note 19) The marking device described in Appendix 18, A marking device further comprising a first generation unit that causes the RRC layer of the first user device to generate an access layer setting corresponding to the service based on the at least one piece of information.

[0166] (Note 20) The marking device described in Appendix 19, A signage device further comprising a first setting unit that includes the generated access layer setting in the user device capability of the second user device.

[0167] (Note 21) A device for generating setting information in sidelink transmission, which is applied to the first user device side. The upper layer of the first user device includes a third notification unit that causes the RRC layer to notify the access layer (AS layer) of at least one of the following pieces of information in order to generate the access layer (AS layer) settings, namely, One layer 2 address between the first user device and the second user device; An address pair consisting of one source layer 2 address and one destination layer 2 address between the first user device and the second user device; and The QoS information for the service corresponding to the aforementioned objective layer 2 address and / or the address pair. Among these, the side link transmission is a side link transmission between the first user device and the second user device, in the marking device.

[0168] (Note 22) The marking device described in Appendix 21, A marking device further comprising a first generation unit that causes the RRC layer of the first user device to generate an access layer setting corresponding to the service based on the at least one piece of information.

[0169] (Note 23) The marking device described in Appendix 21, A signage device further comprising a first setting unit that includes the generated access layer setting in the user device capability of the second user device.

[0170] (Note 24) A user equipment capability (UE capability) indicator device for sidelink transmission, applied to the second user equipment side, The first providing unit includes a first user device that provides the first user device with the following single user device ID (UE ID), causing the first user device to use the user device ID to mark the user device capabilities of the second user device, namely, one destination L2 ID; one address pair consisting of one source L2 ID and one destination L2 address; one link ID; one access layer (AS layer) ID; and one mark used by the second user device when transmitting PC5-RRC messages. Among these, the side link transmission is a side link transmission between the first user device and the second user device, in the marking device.

[0171] (Note 25) The marking device described in Appendix 24, The user device ID is provided by one of the first user device, the second user device, and the network device, according to the identification device.

[0172] (Note 26) The marking device described in Appendix 24, The user device ID is provided by the upper layer or access layer of the first user device or the second user device, according to the identification device.

[0173] (Note 27) The marking device described in Appendix 24, The user device ID is explicitly or implicitly included in the PC5-S message or PC5-RRC message, and is an identifier device.

[0174] (Note 28) A marking device as described in any one of the items in Appendix 24-27, Identifying device, wherein the user device ID is one layer 2 address provided by the upper layer of the first user device or the second user device, or one address pair consisting of one source layer 2 address and one destination layer 2 address, or one link ID.

[0175] (Note 29) The marking device described in Appendix 28, A marker device further includes a second transmitting unit that causes the second user device to transmit the source layer 2 address of the second user device to the first user device by PC5-S message.

[0176] (Note 30) A marking device as described in any one of the items in Appendix 24-27, An identifier device in which the user device ID is one of a plurality of layer 2 addresses provided by the upper layer of the first user device or the second user device, or one of a plurality of the aforementioned address pairs, or one of a plurality of link IDs.

[0177] (Note 31) The marking device described in Appendix 30, An indicator device further comprising a third instruction unit that causes the second user device to indicate the user device ID by a PC5-S message or a PC5-RRC message.

[0178] (Note 32) The marking device described in Appendix 31, A marking device further comprising a second confirmation unit that causes the upper layer or RRC layer of the second user device to determine the user device ID.

[0179] (Note 33) The marking device described in Appendix 30, A marking device further comprising a fourth instruction unit that causes the second user device to instruct the first user device to provide the user device ID via a PC5-S message when the first user device and the second user device exchange user device capabilities.

[0180] (Note 34) The marking device described in Appendix 33, A marking device further comprising a fourth notification unit that causes the RRC layer of the second user device to notify the upper layer of the user device ID.

[0181] (Note 35) A user-defined signage device, including a signage device described in any one of the items in Appendix 1-34.

Claims

1. User device, A communication unit capable of side-link transmission with other user devices, A first identification unit that can identify the user device capabilities of the other user device by an ID pair consisting of a source layer 2 ID (source L2 ID) and a destination layer 2 ID (destination L2 ID), wherein the ID pair is provided to the RRC layer by the V2X layer of the user device or the other user device, A receiving unit capable of receiving a PC5-S message transmitted by the other user device, which includes the ID pair consisting of the layer 2 ID of the other user device as the source layer 2 ID and the layer 2 ID of the user device as the target layer 2 ID, A user device that receives PC5-RRC messages after establishing a corresponding PC5 unicast link via PC5 signaling.

2. The user device according to claim 1, wherein the side link transmission is performed using one or more unicast links between the user device and the other user device.

3. A user device that performs side-link transmission with other user devices, A communication unit capable of performing the aforementioned sidelink transmission, A control unit that provides the other user device with a user device ID (UE ID) consisting of a source layer 2 ID (source L2 ID) and a destination layer 2 ID (destination L2 ID), thereby enabling the other user device to use the user device ID to identify the user device capabilities of the user device, wherein the ID pair is provided to the RRC layer by the V2X layer of the user device or the other user device, and includes a control unit, The other user device receives a PC5-S message transmitted by the user device, which includes the ID pair consisting of the user device's layer 2 ID as the source layer 2 ID and the other user device's layer 2 ID as the target layer 2 ID. A user device that receives PC5-RRC messages after establishing a corresponding PC5 unicast link via PC5 signaling.

Images