CN115336379A - Client device for exchanging sidelink configuration - Google Patents

Abstract

The present disclosure relates to a first client device for exchanging assistance information and sidelink configurations with a network entity and one or more second client devices with which the first client device The second client device engages in sidelink communication. The first client device obtains assistance information from the one or more second client devices, and sends the assistance information to the network entity. In response to said sending said assistance information, said first client device receives an updated sidelink configuration from said network entity, and sends said updated sidelink configuration to said one or more second client devices. at least part of the link configuration. Accordingly, said network entity is enabled to update said sidelink configuration of said one or more second client devices via said first client device.

Description

Client devices for exchanging sidelink configurations

technical field

The present disclosure relates to a first client device for exchanging sidelink configurations with a network entity and one or more second client devices. Furthermore, the present disclosure also relates to corresponding methods and computer programs.

Background technique

Vehicle-to-anything (V2X) communication is one of the key enablers of future cooperative intelligent transportation system (C-ITS). The term V2X collectively refers to vehicles communicating with anything on or along the road. There are two working modes for V2X communication, one is called PC5 or sidelink (sidelink, SL) communication, that is, direct device-to-device (D2D) communication, and the other is Uu interface communication, the Uu interface is an interface between a user equipment (user equipment, UE) and a base station. These modes can be used independently by the UE or jointly by the UE. The V2X communication on Uu consists of the long term evolution (LTE) connected to the 5G core network (5G core network, 5GC) and/or the evolved common terrestrial radio in the new air interface (new radio, NR) connected to the 5GC. Access (evolved universal terrestrial radio access, EUTRA) support. The interworking between 5GS V2X and evolved packet system (EPS) V2X does not require any new interface between 5GS V2X and EPS V2X architecture, and does not affect the evolved packet core network (evolved packet core, EPC) and 5GC. Existing network functional entities. V2X SL is introduced in LTE, supports direct communication between UEs, and is in the dedicated ITS spectrum for V2X services, mainly in the 5.9GHz frequency band. SL is specially designed to meet the requirements of advanced security applications. Compared with LTE which supports broadcast mode, NR SL should also support unicast, multicast and broadcast communication. The carriers supported by NR SL for direct SL communication are licensed spectrum (which can also be used for NR Uu/LTE Uu operation) and dedicated ITS spectrum for two working scenarios.

The parameter configuration for V2X communication via PC5 or SL can be provided to UE in various ways. If the UE resides in the cell, the parameter can be transmitted from the next generation node B (next generation node B, gNB), network node (such as policy control function (policy control function, PCF) through the radio resource control (radio resource control, RRC) message , session management function (session management function, SMF, etc.), or provide/update from the V2X application server (application server, AS) through the V1 interface. Some of these parameters can be pre-configured in a mobile equipment (ME) or in a universal integrated circuit card (UICC) for out-of-coverage or partial-coverage operation.

Contents of the invention

An object of embodiments of the present invention is to provide a solution to reduce or solve the disadvantages and problems of conventional solutions.

The above and other objects are achieved by the subject-matter of the independent claims. Further advantageous embodiments of the invention are provided in the dependent claims.

According to the first aspect of the present invention, the above and other objects are achieved by a first client device for a communication system, the first client device is configured to communicate with one or more first sidelinks based on a first sidelink configuration Two client devices perform sidelink communication, and the first client device is also used for:

obtaining assistance information associated with the sidelink communication from the one or more second client devices;

sending the assistance information to a network entity;

receiving, from the network entity, a second sidelink configuration associated with the sidelink communication in response to the sending the assistance information;

At least a portion of the second sidelink configuration is sent to the one or more second client devices.

The assistance information associated with sidelink communications may be any information that can assist in determining a sidelink configuration for sidelink communications.

According to the first aspect, an advantage of the first client device is that assistance information associated with the sidelink communication, eg assistance information about a second client device not within network coverage, is provided to the network entity. The assistance information can then be used to determine the sidelink configuration in order to improve the robustness and reliability of the system. For example, assistance information can be used to determine resources needed for efficient and reliable sidelink communications. Thus system performance can be optimized.

According to the first aspect, in an implementation manner of the first client device, obtaining the auxiliary information from the one or more second client devices includes:

The assistance information is received from the one or more second client devices in one or more direct link setup messages or one or more application layer messages.

The advantage of this implementation is that the auxiliary information can be obtained by the first client device in various ways, which improves the robustness of obtaining information from one or more second client devices. The received information may then be used by the first client device or sent to a network entity to determine a new sidelink configuration for efficient and reliable sidelink communications.

According to the first aspect, in an implementation manner of the first client device, after receiving the second sidelink configuration, based on the second sidelink configuration, communicate with the one or more The second client device engages in sidelink communication.

The advantage of this implementation is that system performance can be optimized in terms of robustness and reliability.

According to the first aspect, in an implementation manner of the first client device, after it is determined that the first client device is within the coverage of a cell, the assistance information is sent to the network entity.

In the present disclosure, the first client device within the coverage may be understood to mean that the first client device is connected to a cell and/or registered in the cell. In the present disclosure, a cell may be understood as a cell supporting a sidelink function.

The advantage of this implementation is that the first client device being in coverage is beneficial and plays a key role by sending assistance information to network entities, which allows the network to understand that it may be out of coverage and unable to connect to the network One or more second client devices for .

According to the first aspect, in an implementation manner of the first client device, after determining that the first client device is within the coverage of the cell, and determining that the one or more second client devices are within After the coverage of the cell is out of range, send the auxiliary information to the network entity.

In the present disclosure, one or more second client devices being out of coverage may be understood to mean that one or more second client devices are not connected to the cell and/or are not registered in the cell.

An advantage of this implementation is that the information sent by the first client device is about the second client device which is not connected to the network and thus is unknown to the network. After the information is received by the network, the network can use the information to optimize system performance and determine the resources required for efficient and reliable sidelink communications.

According to the first aspect, in an implementation manner of the first client device, the first client device is configured to:

sending a measurement report to said network entity;

receiving an anchor point configuration from said network entity in response to said sending said measurement report;

Becoming an anchor client device based on the anchor configuration prior to sending the second sidelink configuration to the one or more second client devices.

The advantage of this implementation is that the first client device can serve as the anchor of the network entity, and multiple anchor devices can be connected to the cell at the same time. Anchor devices configured and/or managed by the network can help reduce signaling overhead and minimize interference.

According to the first aspect, in an implementation of the first client device, the measurement report is associated with at least one of the following: signal strength, channel-to-duty ratio in the sidelink, guaranteed sidelink Link quality-of-service (QoS) and priority vehicle information.

The advantage of this implementation is that these parameters are general enough to be well-defined measures for determining whether the system state is reliable and robust.

According to the first aspect, in an implementation manner of the first client device, the auxiliary information is at least one of the following items: client device capability, subscription information, vehicle to anything (V2X) service Type, sidelink QoS parameters, special priority information, application layer information, sidelink network layer protocol and sidelink group information.

The advantage of this implementation is that these parameters summarize the necessary information that may be needed on the network to understand the system requirements and determine the sidelink configuration for a reliable and robust system according to time constraints.

According to the first aspect, in an implementation manner of the first client device, the assistance information is group assistance information of the first client device and the one or more second client devices or a single client Individual auxiliary information for the device.

An advantage of this implementation is that a first client device, being part of a group or communicating with individual second client devices, receives relevant information from one or more second client devices out of coverage. Therefore, this information can be fully shared to the network for different use cases, reducing the complexity of client device implementation.

According to the first aspect, in an implementation manner of the first client device, the first sidelink configuration and the second sidelink configuration are at least one of the following: radio bearer configuration , resource configuration, per-region resource configuration, and region configuration.

The advantage of this implementation is that well-defined containers are used to provide or update sidelink configurations, thereby reducing interference and enabling optimal resource selection for sidelink communications in a well-defined and deterministic manner.

According to the first aspect, in an implementation manner of the first client device, the second sidelink configuration is received in any one of a radio resource control message, a non-access stratum signaling, or an application message.

The advantage of this implementation is that it covers many possible known options for information exchange, thereby reducing the complexity of the client device implementation.

According to the first aspect, in an implementation manner of the first client device, the network entity is at least one of the following items: a roadside unit, a base station, an access and mobility management function, a policy control function, Unified data management, V2X control function, V2X application server, V2X network function, or V2X application function.

The advantage of this implementation is that it covers many possible options for network entities, thereby reducing the complexity of client device implementation.

According to a second aspect of the present invention, the above and other objects are achieved by a method for a first client device for communicating with one or more second A client device performs sidelink communication, the method comprising:

obtaining assistance information associated with the sidelink communication from the one or more second client devices;

sending the assistance information to a network entity;

receiving, from the network entity, a second sidelink configuration associated with the sidelink communication in response to the sending the assistance information;

At least a portion of the second sidelink configuration is sent to the one or more second client devices.

The method according to the second aspect may be extended to an implementation corresponding to the implementation of the first client device according to the first aspect. An implementation of the method therefore comprises the features of a corresponding implementation of the first client device.

The advantages of the method according to the second aspect are the same as those of the corresponding implementation of the first client device according to the first aspect.

Embodiments of the present invention also relate to a computer program, which is characterized in that program code, when the computer program is run by at least one processor, causes the at least one processor to execute any method provided by the embodiments of the present invention . In addition, embodiments of the present invention also relate to a computer program product, including a computer-readable medium and the computer program, wherein the computer program is included in the computer-readable medium, and includes one or more of the following groups: Multiple: read-only memory (read-only memory, ROM), programmable ROM (programmable ROM, PROM), erasable PROM (erasable PROM, EPROM), flash memory, electrical EPROM (electrically EPROM, EEPROM) and hard drives.

Other applications and advantages of embodiments of the invention will be apparent from the following detailed description.

Description of drawings

The accompanying drawings are intended to illustrate and explain various embodiments of the invention. In the attached picture:

FIG. 1 shows a first client device provided by an embodiment of the present invention;

FIG. 2 shows a method for a first client device provided by an embodiment of the present invention;

3a to 3b show a communication system provided by an embodiment of the present invention;

FIG. 4 shows an interface between a first client device, a second client device, and a network entity provided by an embodiment of the present invention;

FIG. 5 shows a method for a first client device provided by an embodiment of the present invention;

Fig. 6 shows a method for a first client device provided by an embodiment of the present invention.

Detailed ways

In the 3GPP NR V2X work item of Rel-16, at least two SL resource allocation modes, Mode 1 and Mode 2, are defined. In Mode 1, Node B (node B, NB) schedules SL resources, and in Mode 2, UE determines SL transmission resources within SL resources configured by NB and/or network or within pre-configured SL resources. NB here means evolved node B (evolved nodeB, eNB) or gNB, because both can control NR SL.

Within the work item, four subcategories are assigned for SL resource allocation mode 2:

In Mode 2a, UE autonomously selects SL resources for transmission.

In Mode 2b, the UE assists other UEs in selecting SL resources.

In mode 2c, NR-configured grants (such as type 1) are configured for UE for SL transmission.

In Mode 2d, the UE schedules SL transmissions of other UEs.

Mode 1, Mode 2a and Mode 2c have been considered for Rel.16 work items, but Mode 2b and Mode 2d (where UEs can assist or schedule SL transmission resources for other UEs) are left for future releases.

For Mode 1 and Mode 2, when the UE is within coverage, the NB can directly provide the UE with SL resource configuration. For mode 2, a transmission pool can also be pre-configured for the UE. Mode 2b and Mode 2d provide enhancements to the resource allocation mechanism for both V2X and non-V2X cases. The key aspects related to these patterns are:

(1) UE relays resource configuration from gNB to another UE, and

(2) Scheduling the UE to determine SL resources for other UEs (for example, a group of UEs).

The benefits of UE assisting or scheduling resources for other UEs are mainly to improve packet transmission reliability, optimize resources and reduce communication overhead. A UE that assists or schedules resources for other UEs may be referred to as a scheduling UE, a relay UE, or an anchor UE.

In 3GPP TSG RAN WG1 meeting No. 96, it was agreed that NR V2X in the context of mode 2d for multicast communication supports the following functions: UE informs NB of information about group members, and NB communicates via the UE, for example, through RRC signaling Each group member UE in the same group provides an individual resource configuration. It does not require a connection between each member UE and NB. However, the UE cannot modify the configuration provided by the NB. Additionally, higher layer (L2, L3) signaling will be used to provide configuration.

Therefore, in the context of multicast communication, it is suggested that the NB can provide individual resource configuration to each group member called member UE through the anchor UE, but the details are yet to be specified. This concept provides additional benefits, especially in cases where group members are out of coverage and the anchor UE is in coverage.

An out-of-coverage UE (OoC UE) can also establish a unicast link with an in-coverage UE. Then, the UE within the coverage can establish a Uu link with the network. However, the in-coverage UE may not have enough information from the OoC UE to transmit to the network, such as the capabilities of other UEs belonging to the same group as the OoC UE, subscription information of the OoC UE and its group members, etc.

At least the following issues were identified from the above suggestions:

The anchor UE does not provide the network with the required information about OoC UEs or member UEs so that resources can be determined and configuration provided.

All information required for UE subscription authorization, granting of service requests and resource estimation may or may not be available to the anchor UE. The anchor UE obtains the information required by the network from the member UEs through side link communication, or determines itself according to the previously obtained information, and then passes the information to the network.

No connection is required between the member UEs and the NB, which means that all required information must be exchanged through the anchor UE, and higher layer signaling will be used to provide the configuration. Details about how the process will work and which high-level officials will be involved are unclear.

When an OoC UE wishes to send information to the network via a unicast link via a relaying UE, there is currently no mechanism to include the required information in the unicast link establishment.

Therefore, there is a need for a solution to the above disadvantages. It is therefore an object of this disclosure to identify and specify the information content and parameters in signaling from an anchor UE to a network entity to enable different types of sidelink communications. Another object is to provide a method for exchanging information between OoC UE and anchor UE and between anchor UE and network entities, especially when anchor UE is in coverage and is being out of coverage and not connected to NB At least one UE scheduling resource or assisting relay resource configuration.

Fig. 1 shows a first client device 100 provided by an embodiment of the present invention. In the embodiment shown in FIG. 1 , the first client device 100 includes a processor 102 , a transceiver 104 and a memory 106 . Processor 102 may be coupled to transceiver 104 and memory 106 through a communications module 108 as is known in the art. The first client device 100 may also include an antenna or antenna array 110 coupled to the transceiver 104, which means that the first client device 100 may be used to communicate in the communication system.

The fact that the first client device 100 can be used to perform certain actions in the present disclosure can be understood to mean that the first client device 100 includes suitable modules for performing the described actions, such as the processor 102 and the transceiver 104 .

The processor 102 of the first client device 100 may be referred to as one or more general-purpose central processing units (central processing unit, CPU), one or more digital signal processors (digital signal processor, DSP), one or more dedicated An application-specific integrated circuit (ASIC), one or more field programmable gate arrays (FPGA), one or more programmable logic devices, one or more discrete gates, one or more transistors logic device, one or more discrete hardware components, one or more chipsets.

The memory 106 of the first client device 100 may be a ROM, a random access memory or a non-volatile random access memory (non-volatile random access memory, NVRAM).

The transceiver 104 of the first client device 100 may be a transceiver circuit, a power controller, an antenna, or an interface for communicating with other modules or devices.

In an embodiment, the transceiver 104 of the first client device 100 may be a separate chipset, or it may be integrated with the processor 102 in one chipset. However, in some embodiments, the processor 102, transceiver 104 and memory 106 of the first client device 100 are integrated into one chipset.

According to an embodiment of the present invention, the first client device 100 is configured to perform sidelink communication with one or more second client devices 600a, 600b, . . . , 600n based on a first sidelink configuration. The first client device 100 is further configured to obtain assistance information associated with sidelink communications from one or more second client devices 600a, 600b, ..., 600n. The first client device 100 is further configured to send assistance information to the network entity 300; receive from the network entity 300 a second sidelink configuration associated with the sidelink communication in response to sending the assistance information; and send to one or more A second client device 600a, 600b, ..., 600n transmits at least a portion of a second sidelink configuration.

FIG. 2 shows a flowchart of a corresponding method 200 that can be executed in the first client device 100 (the first client device shown in FIG. 1 ). The first client device 100 is configured to perform sidelink communication with one or more second client devices 600a, 600b, ..., 600n based on the first sidelink configuration. The method 200 includes obtaining (202) assistance information associated with sidelink communications from one or more second client devices 600a, 600b, ..., 600n. The method 200 also includes: sending (204) the assistance information to the network entity 300; receiving (206) from the network entity 300 a second sidelink configuration associated with the sidelink communication in response to sending the assistance information; The or plurality of second client devices 600a, 600b, ..., 600n transmit (208) at least a portion of the second sidelink configuration.

Fig. 3a to Fig. 3b show a communication system 500 provided by an embodiment of the present invention. The communication system 500 comprises a network entity 300 , a first client device 100 and one or more second client devices 600 a , 600 b , . . . , 600 n , all configured to operate in the communication system 500 . In the embodiment shown in Figures 3a-3b, a first client device 100 and one or more second client devices 600a, 600b, ..., 600n are used to perform multicast sidelinks with each other through the PC5 interface communication. However, sidelink communications may also be unicast communications or broadcast communications. In an embodiment, the sidelink communication may be a V2X communication for a V2X service or application. In addition, the sidelink communication may be based on NR or LTE radio access technology (radioaccess technology, RAT), but is not limited thereto.

In Fig. 3a, the first client device 100 and the one or more second client devices 600a, 600b, . The first client device 100 and the one or more second client devices 600a, 600b, ..., 600n thus communicate within the group via sidelinks using preconfigured or provided resources.

In Fig. 3b, the group has moved and the first client device 100 has entered cell coverage. After entering the coverage of the cell, the first client device 100 may detect the cell identity and connect or register with the cell. Therefore, the first client device 100 is within coverage and connected to the network. In the embodiments shown in FIGS. 3 a to 3 b , the network entity 300 is a base station, and a Uu interface is established between the first client device 100 and the network entity 300 . However, in an embodiment, the network entity 300 may be replaced by at least one of the following items: roadside unit, base station, access and mobility management function, policy control function, unified data management, V2X control function, V2X application A server, a V2X network function, or a V2X application function.

The connection between the first client device 100 and the network node 300 enables the network entity 300 to exchange information with one or more second client devices 600a, 600b, ..., 600n through the first client device 100, that is, the first Client device 100 may act as an anchor and/or relay client device. If the network entity 300 wishes to provide a separate resource pool configuration and/or a separate resource configuration to one or more second client devices 600a, 600b, ..., 600n through the first client device 100, the network entity 300 needs One or more second client devices 600a, 600b, ..., 600n and certain information about their current status. Embodiments of the present invention provide for exchanging these way of information. This information may be assistance information that may assist in determining a sidelink configuration and/or a sidelink configuration for sidelink communications.

According to an embodiment of the present invention, the exchange of assistance information and sidelink configuration may take place over different interfaces. FIG. 4 shows an example of an interface (shown by arrows in FIG. 4 ) between a first client device 100 and a second client device 600n and between the first client device 100 and a network entity 300, with the aid of Information and sidelink configuration can be transmitted over these interfaces. The network entity 300 may be a base station (NB) in FIG. 4 , an access and mobility management function (access and mobility management function, AMF) in a core network (CN), and an application (application) in a data network (datanetwork, DN). , APP) server in any one.

FIG. 5 shows a flowchart of a method 400 for exchanging auxiliary information and sidelink configuration provided by an embodiment of the present invention. When the first client device 100 is used for sidelink communication with one or more second client devices 600a, 600b, ..., 600n based on the first sidelink configuration, the method 400 may be performed by the first client device End device 100 executes. The first sidelink configuration may be at least one of the following: radio bearer configuration, resource configuration, per-area resource configuration, and area configuration.

The sidelink communication based on the first sidelink configuration between the first client device 100 and one or more second client devices 600a, 600b, ..., 600n may be unicast, multicast, and/or Broadcast communication, and can be done, for example, via the PC5 interface. Sidelink communication can be performed to exchange information, such as safety messages (such as cooperative awareness message (CAM), decentralized environment notification message (decentralizedenvironmental notification message, DENM)), or in upper layers (such as client device 100, The non-secure message received by the application layer in 600a, 600b, ..., 600n). Some of this information may be forwarded further to lower layers.

In step 402, the first client device 100 obtains assistance information associated with sidelink communications from one or more second client devices 600a, 600b, ..., 600n. The first client device 100 may receive data from one or more second client devices 600a, 600b, . . . Get auxiliary information. In an embodiment, the first client device 100 may communicate with one or more second client devices 600a, 600b, ..., 600n in one or more direct link setup messages or in one or more application layer Receive auxiliary information in the message to obtain auxiliary information.

When the first client device 100 receives assistance information from one or more second client devices 600a, 600b, ..., 600n in one or more direct link setup messages, the assistance information may be included in one or more in one or more containers within a direct link setup message, eg as one or more cells. In the V2X scenario, the direct link establishment message may be a direct link establishment request message defined in 3GPP technical specification 24.587. The direct link setup request message may be sent from the second client device 600a, 600b, ..., 600n to the first client device 100 during unicast sidelink setup. The Direct Link Setup Request message may be extended/enhanced with a new V2X Information Container including assistance information. Table 1 shows the content of this extended direct link setup request message including the V2X information container.

Table 1

Similar V2X information containers may also be included in setup messages for broadcast and multicast communications.

As mentioned above, assistance information may also be received from one or more second client devices 600a, 600b, . . . , 600n in one or more application layer messages. The one or more application layer messages may be, for example, messages exchanged via the V5 interface between the first client device 100 and the V2X applications in the one or more second client devices 600a, 600b, . . . , 600n respectively, see Figure 4.

According to an embodiment of the present invention, the auxiliary information may be at least one of the following: client device capabilities, subscription information, vehicle-to-everything (V2X) service type, sidelink QoS parameters, special priority information, application layer information, network layer protocols for sidelinks, and sidelink group information. In a non-limiting example:

Client device capabilities may include V2X capability parameters.

Subscription information may include data related to a client device's subscription or policy.

The V2X service type may include a provider service identifier (provider service identifier, PSI)/intelligent transportation system (intelligent transportation system, ITS) application ID of the V2X application.

The sidelink QoS parameters may include QoS parameters associated with the V2X service, such as PC5 flow ID (PC5 flowID, PFI), PC5 5G QoS indication (PC5 5G QoS indication, PQI), range, packet priority, etc.

Special priority information may include information about special vehicles (such as rescue vehicles, ambulance vehicles, or safety vehicles) that may require dedicated resources to ensure certain QoS. This information may include vehicle role, vehicle type, individual vehicles or groups of vehicles moving in the convoy, and other geographic data.

The application layer information may include the application layer ID of the client device. The application layer ID can be used at the lower layer that dynamically forms the group, and the application does not notify the group ID to the V2X layer. Instead, the V2X layer passes the mapping of application ID and group ID along with 5QI and range parameters to the access layer for group formation.

Network layer protocols for sidelinks may vary across different stacks and implementations (e.g. GeoNetworking, WSMP, IPv6, etc.).

Sidelink group information may include:

- General group related information such as group size in terms of number of vehicles, dimensions of each vehicle, total weight including container weight (if applicable), distance between vehicles, position of vehicles in the queue, platooning level or automation level.

- When the first client device 100 is not part of a group, the destination layer 2 ID of the group, also called group ID.

- when the group leader leads the multicast communication, the UE layer 2 ID of the group leader.

- UE Layer 2 ID of the group members; makes each group member aware to the network. This allows the network to be better informed, since group members are also participating in other multicast or unicast communications.

- The corresponding coverage status of the member client device, ie in coverage or out of coverage.

Furthermore, the assistance information may be group assistance information of the first client device 100 and one or more second client devices 600a, 600b, . . . , 600n or individual assistance information of a single client device. This way, side information can be tailored to different use cases. For example, group assistance information may relate to a group of client devices configured for multicast communication on a sidelink for use cases such as platooning. In this case, group assistance information may include information about group size, number of members, direction, capabilities, type and size of vehicles in the group, and the like.

In step 404 of FIG. 4 , the first client device 100 sends assistance information to the network entity 300 . The sent auxiliary information may include all or part of the auxiliary information acquired by the first client device 100 in step 402 . The assistance information informs the network entity 300 about the information of one or more second client devices 600a, 600b, ..., 600n participating in the sidelink communication with the first client device 100, and assists the network entity 300 in determining whether to change and/or update the first sidelink configuration. In an embodiment, the first client device 100 may send the assistance information to the network entity 300 in an existing RRC message, in a new container in an existing RRC message or in a new RRC message. Examples of existing RRC messages that may be used are the Sidelink UEInformation message or the UE AssistanceInformation message specified for EUTRA.

In an embodiment, after determining that the first client device 100 is within the coverage of the cell, the first client device 100 may send assistance information to the network entity 300 . The fact that the first client device 100 is within the coverage of the cell may be understood to mean that the first client device 100 is connected to the cell and/or registered in the cell, for example, the first client device 100 resides in the cell. Thus, in an embodiment, the sending of assistance information to the network entity 300 may be triggered when the first client device 100 moves from outside the coverage of the cell to within the coverage, i.e. when connected to and/or registered in the cell. .

Furthermore, after determining that the first client device 100 is within the coverage of the cell, and determining that one or more second client devices 600a, 600b, . . . , 600n are outside the coverage of the cell, the first client device 100 The assistance information may be sent to the network entity 300 . As such, assistance information may be sent to the network entity 300 to inform the network entity 300 about one or more second client devices 600a, 600b, . . . participating in sidelink communication with the first client device 100 . . . 600n the information that the one or more second client devices are out of coverage and therefore not in direct communication with the network entity 300 .

In step 406, in response to sending the assistance information, the first client device 100 receives from the network entity 300 a second sidelink configuration associated with the sidelink communication. The received second sidelink configuration may be determined by the network entity 300 based on assistance information received from the first client device 100, and optionally based on additional information obtained by the network entity 300 from other client devices or network entities . For example, assistance information may be provided from one or more second client devices 600a, 600b, ..., 600n directly to Network entity 300 . In a V2X scenario, the V2X application in the second client device 600a, 600b, ..., 600n can provide auxiliary information to the V2X application server in the network through the V1 interface, and the V2X control function can interact with the V2X application server through the V2 interface . When the network entity 300 is a core network node, the auxiliary information may also be sent to the network entity 300 by using non-access stratum (non access stratum, NAS) signaling. The network entity 300 may also receive configuration updates from the core network and application servers. The second sidelink configuration may also be determined by the network entity 300 in cooperation with one or more other network nodes.

The first client device 100 may receive the second sidelink configuration in any one of a radio resource control message, a non-access stratum signaling or an application message. In the same manner as the first sidelink configuration, the second sidelink configuration may be at least one of the following: radio bearer configuration, resource configuration, per-area resource configuration, and area configuration. The radio bearer configuration may include physical information and/or configuration, such as hybrid automatic repeat request (hybrid automatic repeat request, HARQ) and channel state information (channel state information, CSI). For example, the resource configuration may be a resource pool or dedicated resources for each QoS flow of each V2X service, where the resources may be time and/or frequency resources. Per-area resource configuration may include one or more resource pools per area configured by the network, and this mapping may be sent via an RRC message in one of the containers, e.g. One. Furthermore, the zone configuration may indicate the zone configuration of one or more second client devices 600a, 600b, ..., 600n outside the coverage area specific to the cell, which may be sent via an RRC message in one of the containers (eg ZoneConfig, etc.) .

In step 408, the first client device 100 sends at least a part of the second sidelink configuration to one or more second client devices 600a, 600b, ..., 600n. The first client device 100 may send the first client device 100 to one or more second client devices 600a, 600b, . At least a portion of two sidelink configurations.

Depending on the content of the second sidelink configuration and its applicability to one or more second client devices 600a, 600b, ..., 600n, the first client device 100 may assign the complete second sidelink The configuration or subset of the second sidelink configuration is sent to one or more second client devices 600a, 600b, . . . , 600n. The first client device 100 may also determine and allocate specific resources to one or more second client devices 600a, 600b, . . . , 600n based on the second sidelink configuration. For example, in a platoon use case, the first client device 100 may be a platoon leader leading a group of vehicles. The first client device 100 may then determine and allocate resources for each member of the group based on the second sidelink configuration. In this case, the first client device 100 may also consider assistance information from members of the group when determining and allocating resources.

In step 410, after receiving the second sidelink configuration, the first client device 100 may communicate with one or more second client devices 600a, 600b, . . . , 600n based on the second sidelink configuration. Conduct sidelink communications. Step 410 is performed when the second sidelink configuration is applicable to the first client device 100, for example, when the first client device 100 is part of a unicast or multicast sidelink communication, the network has utilized the second The second sidelink configuration allocates a new resource configuration for said unicast or multicast sidelink communication. When the second sidelink configuration is not applicable to the first client device 100, the first client device 100 only relays in step 408 the second sidelink configuration received from the network entity 300 in step 406 to one or more second client devices 600a, 600b, . . . link communication.

According to an embodiment of the present invention, the first client device 100 may be configured to serve as an anchor client device for one or more second client devices 600a, 600b, . . . , 600n. A first client 100 may be within coverage and configured to act as an anchor client device for one or more second client devices 600a, 600b, . . . , 600n that are out of coverage. In this way, a first client 100 within coverage and thus able to communicate directly with the network entity 300 may relay information to one or more second client devices 600a, 600b, . . . , 600n.

Fig. 6 shows a flowchart of a method 600 for configuring the first client device 100 as an anchor client device provided by an embodiment of the present invention. The method 600 may be executed in the first client device 100 , and may be initiated by the first client device 100 , for example, when the first client device 100 moves within the coverage of a cell and establishes communication with the network entity 300 .

In step 602, the first client device 100 may indicate to the network entity 300 that the first client device 100 is sidelinking with one or more second client devices 600a, 600b, ... 600n out of coverage road communication. The indication may comprise very basic or limited information about one or more second client devices 600a, 600b, ..., 600n.

Once the network entity 300 has identified one or more out-of-coverage second client devices 600a, 600b, ..., 600n, the network entity 300 may wish to assist the one or more second client devices 600a, 600b, ... , 600n for resource allocation. To this end, the network entity 300 may request the first client device 100 to perform measurements and report measurement results.

Accordingly, the first client device 100 may perform measurements and monitor measurement results in step 604 , wherein the measurement results may be monitored based on thresholds and/or trigger conditions received from the network entity 300 .

In step 606 , the first client device 100 sends a measurement report to the network entity 300 . Measurement reports may be sent when threshold and/or trigger conditions are detected to be met. The measurement report may be associated with at least one of: signal strength, channel-to-duty ratio in the sidelink, guaranteed sidelink quality of service (QoS), and priority vehicle information.

In response to sending the measurement report, in step 608 the first client device 100 receives an anchor point configuration from the network entity 300 . The anchor point configuration may include information for at least one of: enabling the first client device 100 to acquire information from one or more second client devices 600a, 600b, . . . , 600n; enabling the first The client device 100 can send the obtained information and the auxiliary information to the network entity 300; and enable the first client device 100 to provide one or more second client devices by processing the obtained information and determining suitable resources 600a, 600b, ..., 600n schedule resources.

In step 610, the first client device 100 is configured as an anchor client device based on the anchor configuration. For example, a first client device 100 acting as an anchor client device may assist in relaying resource configurations from the network entity 300 to one or more second client devices 600a, 600b, ..., 600n out of coverage. For example, a first client device 100 acting as an anchor client device may relay a second sidelink configuration to one or more second client devices 600a, 600b, . . . , 600n, as described with reference to FIG. stated. In this case, before sending the second sidelink configuration to the one or more second client devices 600a, 600b, ..., 600n, ie before step 408 in method 400, the first client The device 100 is configured as an anchor client device based on the anchor configuration. In an embodiment, method 600 may be performed prior to method 400, such that after first client device 100 has been configured to act as an anchor client device, first client device 100 receives information from one or more second client devices 600a, 600b, ..., 600n receive auxiliary information.

The assistance information from the one or more second client devices 600a, 600b, ..., 600n to the first client device 100 acting as an anchor client device may be application specific for certain use cases. The following is when the first client device 100 acts as an anchor client device, from one or more second client devices 600a, 600b, ..., 600n (hereinafter referred to as out-of-coverage, OoC ) UE) to some examples of possible assistance information of the first client device 100:

Client device capability: the OoC UE may indicate its V2X capability parameters to the first client device 100, for example, UE supporting LTE or NR (v2x-EUTRA). Depending on whether the OoC UE is pre-configured with radio access parameters, such as radio frequency, physical layer or layer 2 parameters, there are two options:

- Pre-configuration: In this case it is enough for the network entity 300 to know whether the OoC UE supports LTE or NR.

Therefore, the first client device 100 collects this information and may send eg the number of LTE-capable OoC UEs and the number of NR-capable OoC UEs to the network entity 300 .

- Not pre-configured: In this case, the first client device 100 needs to collect OoC UE capabilities and send them to the network entity 300 . The first client device 100 may extend the existing mechanism (for example, receive "PC5

RRC message" to collect the capability information of the OoC UE. The first client device 100 may query the OoC UE for the UE capability information in the "PC5 UE Capability Query", or the OoC UE may ask the first client device 100 advertises capability information. Once the information is collected by the first client device 100, this information may be sent to the network entity 300 in a UE-EUTRA-Capability and/or UE-NR-Capability information element, for example:

Existing RRC messages (eg SidelinkUEInformation) can be extended to carry new information elements, or new messages can be defined.

V2X service type and associated PC5 QoS parameters: In case of multicast communication, these parameters are known to all group members when the group is established, also in case of unicast. However, if the first client device 100 is scheduling resources for unicast or multicast sidelink communications where the first client device 100 is not part of the unicast or multicast communication, the first client device 100 does not know these parameters. Therefore, the group members have to provide parameters to the first client device 100, such as the V2X traffic type, such as the provider service identifier (PSI)/ITS application ID of the V2X application, and for each V2X traffic type, the associated QoS parameters , such as PC5 Flow ID (PFI), PC5 5G QoS Indication (PQI), range, packet priority, etc., as auxiliary information.

In an embodiment, the first client device 100 serving as an anchor client device may be a roadside unit (road side unit, RSU) in a V2X application, and one or more second client devices 600a, 600b, . . . ..., 600n The communication between RSU and RSU can be sidelink communication or Uu communication, depending on whether RSU is UE type or gNB type. The RSU unit can be any device/node deployed along the road to improve vehicle network performance, as well as extend coverage. The RSU unit may be a stand-alone device/node, or may be integrated with eg a network access node.

The first client device 100 and one or more second client devices 600a, 600b, ..., 600 in the present disclosure include, but are not limited to: UEs, such as smart phones, cellular phones, cordless phones, session initiation protocols (sessioninitiation protocol, SIP) telephone, wireless local loop (wireless local loop, WLL) station, personal digital assistant (personal digital assistant, PDA), handheld device with communication function, computing device or other processing device connected to a wireless modem, vehicle-mounted Devices, wearable devices, integrated access and backhaul (IAB) nodes, such as mobile cars or devices installed in cars, drones, device-to-device (D2D) devices, Wireless cameras, mobile stations, access terminals, subscriber units, wireless devices, wireless local access network (WLAN) stations, wireless-capable tablet computers, laptop embedded devices, universal serial bus (universal serial bus) , USB) converter, wireless customer premise equipment (customer-premises equipment, CPE) and/or chipset. In an Internet of things (Internet of things, IOT) scenario, the first client device 100 may represent a machine or another device or chipset that communicates with another wireless device and/or network device.

A UE may also be called a mobile phone, a cellular phone, a wireless-capable tablet or a laptop. In this context, a UE may be, for example, a portable, pocket-storage, handheld, computer-composed or vehicle-mounted mobile device capable of transmitting voice and/or or data. The UE may be a station (station, STA), which is a medium access control (media access control, MAC) and a physical layer (physical layer, PHY) interface to the wireless medium (wireless medium, WM) conforming to IEEE802.11 any device. The UE can also be used to communicate in 3GPP-related LTE and LTE-Advanced, in WiMAX and its evolution, and in fifth-generation wireless technologies such as NR.

In addition, any method provided by the embodiments of the present invention may be implemented in a computer program with code modules, and when the computer program is run by the processing module, the processing module executes the method steps. The computer program is embodied on a computer readable medium of a computer program product. The computer readable medium can include basically any memory, such as read-only memory (read-only memory, ROM), programmable read-only memory (programmable read-only memory, PROM), erasable PROM (erasable PROM, EPROM), Flash memory, electrically erasable PROM (electrically erasable PROM, EEPROM) or hard disk drive.

Furthermore, those skilled in the art realize that the embodiment of the first client device 100 comprises the necessary communication capabilities in the form of eg functions, modules, units, elements etc. for implementing the scheme. Examples of other such modules, units, elements and functions are: processors, memories, buffers, control logic, encoders, decoders, rate matchers, derate matchers, mapping units, multipliers, decision units, selection Unit, switch, interleaver, deinterleaver, modulator, demodulator, input terminal, output terminal, antenna, amplifier, receiving unit, transmitting unit, DSP, MSD, TCM encoder, TCM decoder, power supply unit, power supply Feeders, communication interfaces, communication protocols, etc., which are properly arranged together to implement the scheme.

In particular, the processor of the first client device 100 may include, for example, one or more of the following: a central processing unit (CPU), a processing unit, a processing circuit, a processor, an application specific integrated circuit (ASIC), a microprocessor, or Other processing logic that can interpret and execute instructions. The expression "processor" may thus denote processing circuitry comprising a plurality of processing circuits, such as any, some, or all of the above-listed items. The processing circuitry may also perform data processing functions for inputting, outputting, and processing data, including data buffering and device control functions, such as call processing control, user interface control, and the like.

Finally, it should be understood that the embodiments of the invention are not limited to the above-described embodiments, but also relate to and incorporate all embodiments within the scope of the appended independent claims.

Claims (14)

1. A first client device (100) for a communication system (500), the first client device (100) for sidelink communication with one or more second client devices (600 a, 600b, \8230; 600 n) based on a first sidelink configuration, the first client device (100) further for:

obtaining auxiliary information associated with the sidelink communications from the one or more second client devices (600 a, 600b, \8230; 600 n);

sending the assistance information to a network entity (300);

receiving, from the network entity (300), a second sidelink configuration associated with the sidelink communication in response to the sending the assistance information;

at least a portion of the second sidelink configuration is transmitted to the one or more second client devices (600 a, 600b, \8230;, 600 n).

2. The first client device (100) of claim 1, wherein obtaining the assistance information from the one or more second client devices (600 a, 600b, \8230;, 600 n) comprises:

the assistance information is received from the one or more second client devices (600 a, 600b, \8230;, 600 n) in one or more direct link setup messages or one or more application layer messages.

3. The first client device (100) of claim 1 or 2, configured to:

sidelink communications with the one or more second client devices (600 a, 600b, \ 8230; \8230;, 600 n) based on the second sidelink configuration are performed after receiving the second sidelink configuration.

4. The first client device (100) of any one of the preceding claims, configured to:

upon determining that the first client device (100) is within a coverage area of a cell, sending the assistance information to the network entity (300).

5. The first client device (100) of claim 4, configured to:

upon determining that the first client device (100) is within a coverage area of the cell and determining that the one or more second client devices (600 a, 600b, \8230; 600 n) are outside the coverage area of the cell, sending the assistance information to the network entity (300).

6. The first client device (100) of any one of the preceding claims, configured to:

sending a measurement report to the network entity (300);

receiving an anchor point configuration from the network entity (300) in response to the sending of the measurement report;

prior to sending the second sidelink configuration to the one or more second client devices (600 a, 600b, \8230;, 600 n), the client device is configured to become an anchor client device based on the anchor configuration.

7. The first client device (100) of claim 6, wherein the measurement report is associated with at least one of: signal strength, channel busy ratio in the sidelink, guaranteed sidelink quality of service (QoS), and priority vehicle information.

8. The first client device (100) according to any one of the preceding claims, wherein the assistance information is at least one of: client device capabilities, subscription information, vehicle networking (V2X) traffic type, sidelink QoS parameters, special priority information, application layer information, network layer protocol for sidelink, and sidelink group information.

9. The first client device (100) of any one of the preceding claims, wherein the assistance information is group assistance information of the first client device (100) and the one or more second client devices (600 a, 600b, \8230;, 600 n) or individual assistance information of a single client device.

10. The first client device (100) of any one of the preceding claims, wherein the first sidelink configuration and the second sidelink configuration are at least one of: radio bearer configuration, resource configuration, per-region resource configuration, and region configuration.

11. The first client device (100) of any one of the preceding claims, being configured to:

receiving the second sidelink configuration in any of a radio resource control message, non-access stratum signaling, or an application message.

12. The first client device (100) according to any one of the preceding claims, wherein the network entity (300) is at least one of: a road side unit, a base station, an access and mobility management function, a policy control function, a unified data management, a V2X control function, a V2X application server, a V2X network function, or a V2X application function.

13. A method (200) for a first client device (100), the first client device (100) for sidelink communication with one or more second client devices (600 a, 600b, \8230; 600 n) based on a first sidelink configuration, the method (200) comprising:

obtaining (202) secondary information associated with the sidelink communications from the one or more second client devices (600 a, 600b, \8230; 600 n);

sending (204) the assistance information to a network entity (300);

receiving (206), from the network entity (300), a second sidelink configuration associated with the sidelink communication in response to the sending the assistance information;

sending (208) at least a portion of the second sidelink configuration to the one or more second client devices (600 a, 600b, \8230;, 600 n).

14. A computer program having a program code for performing the method according to claim 13, when the computer program runs on a computer.

Images