CN111527780B

CN111527780B - Method, device and computer readable medium for device-to-device communication

Info

Publication number: CN111527780B
Application number: CN201780097606.3A
Authority: CN
Inventors: 许翔; 李海涛; 于�玲; V·V·潘
Original assignee: Nokia Shanghai Bell Co Ltd; Nokia Solutions and Networks Oy
Current assignee: Nokia Shanghai Bell Co Ltd; Nokia Solutions and Networks Oy
Priority date: 2017-12-11
Filing date: 2017-12-11
Publication date: 2023-03-24
Anticipated expiration: 2037-12-11
Also published as: CN111527780A; WO2019113739A1

Abstract

Embodiments of the present disclosure provide a method and apparatus for D2D communication. The network device may allocate D2D communication resources for the set of terminal devices based on information received from the arbitrating terminal device. The information indicates an amount of resources potentially required by the set of terminal devices. The network device also configures a bearer set for the terminal device set. If the terminal device is to establish the target D2D communication, the arbitration terminal device or the terminal device itself may send a resource request to the network device. The terminal device may monitor the identifier of the sidelink bearer and use the D2D communication resource associated with the sidelink bearer. In this way, the network device allocates D2D communication resources in an efficient manner.

Description

Method, device and computer readable medium for device-to-device communication

Technical Field

Embodiments of the present disclosure relate generally to communication technology and, more particularly, relate to a method, device, and computer-readable medium for device-to-device (D2D) communication.

Background

In recent communication systems, such as Long Term Evolution (LTE) communication systems, D2D communication (also referred to as sidelink communication) has been proposed. Generally, D2D communication supports two resource allocations, namely autonomous resource selection and scheduled resource allocation. For scheduling resource allocation, the terminal device requests transmission resources from the base station, and the base station schedules the transmission resources for the terminal device to establish D2D communication.

Disclosure of Invention

In general, embodiments of the present disclosure relate to a method for modulation of downlink transmissions and corresponding network and terminal devices.

In a first aspect, embodiments of the present disclosure provide a method implemented at a network device for communication. The method comprises the following steps: in response to receiving a resource request by a first terminal device for performing target D2D communication, determining a resource for the target D2D communication from a set of resources configured for a set of terminal devices, the set of terminal devices comprising the first terminal device and an arbitrating terminal device configured to control the D2D communication performed between the set of terminal devices; determining a sidelink bearer for the target D2D communication from a set of bearers configured to the set of terminal devices, the set of resources and the set of bearers being configured to be associated with D2D communications performed in the set of terminal devices; and transmitting information on the determined resources and the determined side link bearers.

In a second aspect, embodiments of the present disclosure provide a method implemented at an arbitrating terminal device of a set of terminal devices, and the arbitrating terminal device is configured to control D2D communications performed between the set of terminal devices. The method comprises the following steps: in response to receiving a request from a first terminal device for the first terminal device to perform a target D2D communication, determining whether the first terminal device is allowed to perform the target D2D communication, an arbitrating terminal device configured to control the D2D communication performed between a set of terminal devices, the set of terminal devices including the first terminal device and the arbitrating terminal device; requesting a network device resource in response to the first terminal device being allowed to perform the target D2D communication; and receiving, from the network device, information on resources and sidelink bearers determined for the target D2D communication, the resources being determined from a set of resources configured to the set of terminal devices, the sidelink bearers being determined from a set of bearers configured to the set of terminal devices, the set of resources and the set of bearers being configured to be associated with D2D communications performed in the set of terminal devices.

In a third aspect, embodiments of the present disclosure provide a network device. The network device includes: at least one processor; and a memory coupled with the at least one processor, the memory storing instructions therein, which when executed by the at least one processor, cause the network device to perform acts comprising: in response to receiving a resource request by a first terminal device for performing target D2D communication, determining a resource for the target D2D communication from a set of resources configured for a set of terminal devices, the set of terminal devices comprising the first terminal device and an arbitrating terminal device configured to control the D2D communication performed between the set of terminal devices; determining a sidelink bearer for the target D2D communication from a set of bearers configured to the set of terminal devices, the set of resources and the set of bearers being configured to be associated with D2D communications performed in the set of terminal devices; and transmitting information on the determined resources and the determined sidelink bearers.

In a fourth aspect, embodiments of the present disclosure provide an arbitrating terminal device, the arbitrating terminal device being in a set of terminal devices, the arbitrating terminal device being configured to control device-to-device, D2D, communications performed between the set of terminal devices. The arbitration terminal device includes: at least one processor; a memory coupled with the at least one processor, the memory storing instructions therein, which when executed by the at least one processor, cause the terminal device to perform acts comprising: in response to receiving a request from a first terminal device for the first terminal device to perform a target D2D communication, determining whether the first terminal device is allowed to perform the target D2D communication, an arbitrating terminal device configured to control the D2D communication performed between a set of terminal devices, the set of terminal devices including the first terminal device and the arbitrating terminal device; requesting a network device resource in response to the first terminal device being allowed to perform the target D2D communication; and receiving, from the network device, information on resources and sidelink bearers determined for the target D2D communication, the resources being determined from a set of resources configured to the set of terminal devices, the sidelink bearers being determined from a set of bearers configured to the set of terminal devices, the set of resources and the set of bearers being configured to be associated with D2D communications performed in the set of terminal devices.

In a fifth aspect, embodiments of the present disclosure provide a computer-readable medium. The computer-readable medium stores thereon instructions that, when executed by at least one processing unit of a machine, cause the machine to perform: in response to receiving a resource request for a first terminal device to perform target D2D communication, determining a resource for the target D2D communication from a set of resources configured to a set of terminal devices, the set of terminal devices including the first terminal device and an arbitrating terminal device configured to control the D2D communication performed between the set of terminal devices; determining a sidelink bearer for the target D2D communication from a set of bearers configured to the set of terminal devices, the set of resources and the set of bearers being configured to be associated with D2D communications performed in the set of terminal devices; and transmitting information on the determined resources and the determined side link bearers.

In a sixth aspect, embodiments of the present disclosure provide another computer-readable medium. A further computer-readable medium stores thereon instructions that, when executed by at least one processing unit of a machine, cause the machine to perform: in response to receiving a request from a first terminal device for the first terminal device to perform a target D2D communication, determining whether the first terminal device is allowed to perform the target D2D communication, an arbitrating terminal device configured to control the D2D communication performed between a set of terminal devices, the set of terminal devices including the first terminal device and the arbitrating terminal device; requesting a network device resource in response to the first terminal device being allowed to perform the target D2D communication; and receiving, from the network device, information on resources and sidelink bearers determined for the target D2D communication, the resources being determined from a set of resources configured to the set of terminal devices, the sidelink bearers being determined from a set of bearers configured to the set of terminal devices, the set of resources and the set of bearers being configured to be associated with D2D communications performed in the set of terminal devices.

Other features and advantages of embodiments of the present disclosure will also be apparent from the following description of specific embodiments, when taken in conjunction with the accompanying drawings which illustrate, by way of example, the principles of embodiments of the disclosure.

Drawings

Embodiments of the present disclosure are presented by way of example and their advantages are explained in more detail below with reference to the drawings, in which

Fig. 1 shows a schematic diagram of a communication system according to an embodiment of the present disclosure;

FIG. 2 illustrates an interaction diagram for communication operations in accordance with an embodiment of the present disclosure;

FIG. 3 illustrates an interaction diagram for communication operations, according to an example embodiment of the present disclosure;

fig. 4 illustrates a flow diagram of a method for communication implemented at a network device in accordance with an embodiment of the disclosure;

fig. 5 shows a flow diagram of a method for communication implemented at a terminal device in accordance with an embodiment of the present disclosure; and

fig. 6 shows a schematic diagram of an apparatus according to an embodiment of the present disclosure.

Throughout the drawings, the same or similar reference numerals denote the same or similar elements.

Detailed Description

The subject matter described herein will now be discussed with reference to several exemplary embodiments. It is understood that these embodiments are discussed only for the purpose of enabling those skilled in the art to better understand and thereby implement the subject matter described herein, and are not intended to imply any limitation as to the scope of the subject matter.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises," "comprising," "includes" and/or "including," when used herein, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

It should also be noted that, in some alternative implementations, the functions/acts noted may occur out of the order noted in the figures. For example, two functions or acts shown in succession may in fact be executed substantially concurrently or the functions or acts may sometimes be executed in the reverse order, depending upon the functionality/acts involved.

As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as Long Term Evolution (LTE), LTE-advanced (LTE-a), wideband Code Division Multiple Access (WCDMA), high Speed Packet Access (HSPA), and so forth. Further, communication between the terminal device and the network devices in the communication network may be performed according to any suitable communication protocol, including, but not limited to, a first generation (1G) communication protocol, a second generation (2G) communication protocol, a 2.5G communication protocol, a 2.75G communication protocol, a third generation (3G) communication protocol, a fourth generation (4G) communication protocol, a 4.5G communication protocol, a future fifth generation (5G) communication protocol, and/or any other protocol currently known or to be developed in the future.

Embodiments of the present disclosure may be applied to various communication systems. Given the rapid development of communications, there will of course also be future types of communication technologies and systems in which the present disclosure may be implemented. The scope of the present disclosure should not be limited to only the above-described systems.

The term "network device" includes, but is not limited to, a Base Station (BS), a gateway, a management entity, and other suitable devices in a communication system. The term "base station" or "BS" denotes a node B (NodeB or NB), evolved NodeB (eNodeB or eNB), NR NodeB (gNB), remote Radio Unit (RRU), radio Head (RH), remote Radio Head (RRH), relay station, low power node (e.g. femto, pico, etc.).

The term "terminal device" includes, but is not limited to, "User Equipment (UE)" and other suitable terminal devices capable of communicating with the network device. By way of example, "terminal equipment" may refer to a terminal, a Mobile Terminal (MT), a Subscriber Station (SS), a portable subscriber station, a Mobile Station (MS), or an Access Terminal (AT).

The term "device-to-device (D2D) communication" as used herein refers to a technique that enables direct communication between terminal devices by reusing cell resources under system control, so that user data can be directly transmitted between the terminal devices without network transmission. D2D communication may be performed between two terminal devices. That is, a transmission from one terminal device is targeted to another terminal device. D2D communication may also be performed between a set of terminal devices (e.g., three or more terminal devices). That is, a transmission from one terminal device targets two or more terminal devices. The term "bearer" as used herein refers to a logical path between two communication devices. The term "resource" as used herein refers to any kind of communication resource, e.g. physical resource blocks and/or resource elements. The term "arbitrating terminal device" as used herein refers to a terminal device in a group of terminal devices that may control D2D communication performed in the group.

As described above, D2D communication has been proposed. For example, the 3GPP standard TS22.280 defines mission critical service (MCX) requirements specific to off-network usage. Specifically, an MCX service operating in an off-network mode includes a set of functions to provide MCX (e.g., MCPTT, MCVideo, MCData, etc.) over D2D communications. TS23.281 defines off-network transport control. In TS23.281 it is described that transmission control is performed by using a transmission control information stream between a transmission control participant and a transmission control arbiter. The transmission control arbiter is a terminal device of a group of terminal devices. For example, in the MCX scenario, the transmission control arbiter is, for example, an MCVideo UE of an MCVideo group, wherein transmission rules are applied. Off-network transmission control may be performed in two ways: single arbiter and self-arbitration.

For a single arbiter scenario, the transmitting participant responds to a single participant designated as the transmitting arbiter to arbitrate the request to send. In this case, a procedure of transferring the grant will be described below. The first terminal device, called MCVideo client, sends a transfer request message (MCX signaling) to the MCVideo group. The MCVideo group comprises several terminal devices. The second terminal device (called the transmission arbiter) checks whether the configured maximum simultaneous transmission limit has been reached. If the maximum simultaneous transmission limit is not reached, the second terminal device sends a transmission permission message to the MCVideo group indicating the first terminal device as the intended sender. The MCVideo user at the first terminal device may be informed that the video is now available for transmission. The first terminal device transmits video (i.e., MCX Media) to the MCVideo group.

In a single arbiter scenario, a process for transmitting an overwrite (override) is described below. This is typically used when the arbitrator overwrites (preempts) existing transmissions to support transmissions from high priority UEs. The first terminal device (called MCVideo client) sends a transfer request message to the MCVideo group. The second terminal device (called the transmission arbiter) will check the overwrite policy since the configuration limit for maximum simultaneous transmission has been reached. If the first terminal device is authorized to overwrite (based on e.g. the transmission priority), the second terminal device sends a transmission cancel message to the MCVideo group. The transmission cancellation message indicates that the permission has been revoked from the third terminal device as the intended sender. The third terminal device stops the transmission of the video and may notify the MCVideo user on the third terminal device that the transmission permission has been cancelled. The second terminal device sends a transmission permission message to the MCVideo group. The transmission permission message indicates that the first terminal device is the intended sender. The MCVideo user on the first terminal device may be informed that the video is now available for transmission. The first terminal device sends the video to the MCVideo group.

According to TS23.281, after the arbiter grants the transmission request, the arbiter announces that the MCX media transmission will be started by the particular end device. This is known as part of the so-called floor control in a group call or communication. It is assumed that the UE can successfully start MCX media transmission. However, in an off-network situation where sidelink D2D communication is used and the terminal device needs to request sidelink communication resources, this may not be the case. In case of high eNB load, the terminal device may not be able to acquire sidelink communication resources and may not be able to initiate MCX media transmission.

In order to solve the above problem, a conventional method is to introduce a service similar to Guaranteed Bit Rate (GBR) in a sidelink. The terminal may request a GBR-like sidelink communication resource before the terminal device requests MCX media transmission rights. However, it has some disadvantages. When a bearer is established, resources like GBR need to be reserved at the eNB. This means that the base station needs to reserve a sidelink communication resource for the terminal device even before the terminal device obtains the MCX transmission permission from the arbiter. The GBR service in the Uu interface is on a per terminal equipment basis. If GBR-like resource allocation is used in the sidelink, the base station must reserve sidelink communication resources for many terminal devices in the MCX group. The above conventional method is inefficient if only a few terminal devices in the MCX group are allowed to transmit the MCX media at the same time.

Another conventional approach is to apply the concept of D2D cluster and Cluster Head (CH) to the MCX group and arbiter. From a resource allocation perspective, the conventional solution for D2D CH to allocate resources between D2D clusters is a solution to support MCX at the access layer (AS) level. However, this solution has the following drawbacks. The terminal device acting AS an arbiter requires additional AS-level terminal device functions, e.g. similar to the resource allocation function in the base station. Additional resources and corresponding signaling procedures are required between the D2D CH (arbiter) and the D2D cluster members to perform resource allocation through the sidelink. Since coordination between the base station and the D2D CH (arbiter) is required to adapt to the resources allocated to a given MCX group, it is difficult to achieve a fast adaptation of the resources required for each MCX group.

To address at least in part the above and other potential problems, embodiments of the present disclosure provide a solution for D2D communication. Some example embodiments of the present disclosure are now described below with reference to the drawings. However, those skilled in the art will readily appreciate that the detailed description given herein with respect to these figures is for explanatory purposes as the disclosure extends beyond these limited embodiments.

Fig. 1 shows a schematic diagram of a communication system in which embodiments of the present disclosure may be implemented. Communication system 100, which is part of a communication network, includes a network device 120 and one or more terminal devices 110-1, 110-2, 110-3, 110-4. It should be noted that communication system 100 may also include other elements that have been omitted for clarity. Network device 120 may communicate with terminal device 110. It should be understood that the number of network devices and terminal devices shown in fig. 1 is given for illustrative purposes and does not suggest any limitation. Network 100 may include any suitable number of network devices and terminal devices. Terminal device 110-1, terminal device 110-2, terminal device 110-3, and terminal device 110-4 are in the same set of terminal devices 130. By way of example, terminal device 110-1, terminal device 110-2, terminal device 110-3, and terminal device 110-4 may belong to the same MCX group.

Communications in communication system 100 may be implemented in accordance with any suitable communication protocol, including, but not limited to, cellular communication protocols such as first-generation (1G) cellular communication protocols, second-generation (2G) cellular communication protocols, third-generation (3G) cellular communication protocols, fourth-generation (4G) cellular communication protocols, fifth-generation (5G) cellular communication protocols, and so forth, wireless local area network communication protocols such as Institute of Electrical and Electronics Engineers (IEEE) 802.11, and so forth, and/or any other protocol now known or later developed. Further, the communication may utilize any suitable wireless communication technology, including but not limited to: code Division Multiple Access (CDMA), frequency Division Multiple Address (FDMA), time Division Multiple Address (TDMA), frequency Division Duplex (FDD), time Division Duplex (TDD), multiple Input Multiple Output (MIMO), orthogonal Frequency Division Multiple Access (OFDMA), and/or any other currently known or later developed technique.

Network device 120 may allocate D2D communication resources for the set of terminal devices 130 based on information received from terminal device 110-1 or from a core network (not shown in fig. 1). This information indicates the amount of resources potentially needed by the set of terminal devices 130. Network device 120 also configures a set of bearers including one or more sidelink bearers for the set of terminal devices 130. Terminal device 110-1 or terminal device 110-2 itself sends a resource request if terminal device 110-2 is to establish a D2D communication between itself and terminal device 110-4 (referred to as a second terminal device). Terminal device 110-2 may monitor the identifier of the sidelink bearer and use the D2D communication resource associated with the sidelink bearer. In this manner, network device 120 allocates D2D communications in a more efficient manner than GBR-like approaches. No additional functionality is required for terminal device 110-1. Some example embodiments of the present disclosure are now described below with reference to fig. 2-5.

Fig. 2 illustrates an example interaction diagram of operations 200 according to some embodiments of the present disclosure. In some embodiments, a core network/application server (CN/AS) (not shown) may inform whether an end device (e.g., end device 110-1) is authorized to be an arbitrator for a set of end devices (e.g., end device set 130) if the end device is attached to the network.

The end device 110-1 (referred to as the arbitrating end device) may transmit 204 information (referred to as first information) related to the D2D communication within the set of end devices 130. In an example embodiment, the information related to D2D communications within the set of terminal devices 130 may include a quality of service of the D2D communications. For example, in case of MCX service, the information includes quality of service (QoS) of each MCX media. The first information may further include the number of sidelinks in the set of terminal devices 130. In another example, the information may include a number of concurrent D2D communications in the set of terminal devices 130. The information may include any combination of: qoS of D2D communication, number of side links, and number of concurrent D2D communications. In some embodiments, the first information may be sent to network device 120 via RRC signaling during or after an RRC connection establishment procedure. In some other embodiments, a core network/application server (CN/AS) (not shown) may inform network device 120 about information about D2D communications within the set of terminal devices 130 if a new terminal device is attached to the network.

In some embodiments, terminal device 110-1 may periodically retransmit information related to D2D communications. In other embodiments, terminal device 110-1 may retransmit the updated first information if the set of terminal devices 130 changes. For example, if the QoS of the D2D communication changes, terminal device 110-1 may retransmit the changed QoS. Similarly, if the number of sidelink communications and/or the number of concurrent D2D communications changes, terminal device 110-1 may send the updated number to network device 120.

The network device 120 may allocate 208 the set of resources to the set of terminal devices 130 based on the first information. For example, network device 120 may reserve some Physical Resource Blocks (PRBs) for terminal device set 130 for D2D communication. In this way, network device 120 allocates an amount of resources to the set of terminal devices, rather than to a particular terminal device that may not initiate D2D communication. Thus, resources are allocated in a more efficient manner than in GRB-like approaches. In some embodiments, if terminal device set 130 is released, network device 120 may release all allocated D2D communication resources.

Network device 120 may configure 212 a set of bearers to set of terminal devices 130. The set of bearers includes at least one side link bearer. As described above, the number of sidelink bearers in the configured set of bearers may be determined based on information sent from terminal device 110-1 to network device 120. In some embodiments, network device 120 may configure logical channels to the sidelink bearer. Each sidelink bearer has a bearer-specific identifier. For example, a side chain bearer may have CRNTI specific to the bearer.

In other embodiments, network device 120 may assign a particular amount of resources to a particular sidelink bearer. In this example, terminal device 110-1 may update the first information if one or more sidelink bearers require additional resources. In other embodiments, network device 120 may not pre-allocate resources to the sidelink bearers before one or more terminal devices request MCX media transmission. In some embodiments, network device 120 may send information about the allocated D2D communication resources and the configured sidelink bearers to terminal device 110-1 via RRC signaling.

In some embodiments, terminal device 110-2 (referred to as a first terminal device) may send 216 a request for D2D communication resources for control signaling. In some embodiments, the D2D communication resources requested here are resources for control signaling that may be shared among several groups of terminal devices.

In some embodiments, network device 120 may respond 220 to the request sent from terminal device 110-2. For example, network device 120 may grant resources to terminal device 110-2 for sending control signaling.

After obtaining the control signaling resources from network device 120, terminal device 110-2 may send 224 a request to terminal device 110-1 for performing D2D communication (referred to as target D2D communication). For example, in the case of the MCX service, the terminal device 110-2 transmits an MCX transmission request message to the terminal device 110-1. In an example embodiment, terminal device 110-2 may also send a Buffer Status Report (BSR) to terminal device 110-1. The BSR may carry information about how much data to send in the buffer of terminal device 110-2.

Terminal device 110-1 may respond 228 to the request. For example, terminal device 110-1 may permit D2D communication for terminal device 110-2. For example, terminal device 110-1 may permit D2D communication if the maximum number of concurrent D2D communications for the set of terminal devices 130 has not been reached. In other embodiments, although the maximum number of concurrent D2D communications for the set of terminal devices 130 is reached, terminal device 110-1 may grant D2D communications by cancelling other D2D communications if the priority level of terminal device 110-2 is higher than the terminal device currently performing D2D communications. The terminal device 110-1 may also reject the request if the maximum number of concurrent D2D communications of the set of terminal devices 130 is reached and the priority level of the terminal device 110-2 is not high enough to cancel the D2D communications of the other terminal devices in the set of terminal devices 130.

In an example embodiment, terminal device 110-1 may send 232 a resource request for D2D communication resources to network device 120. For example, the resource request may be a message for D2D communication resources. Terminal device 110-1 notifies network device 120 that terminal device 110-2 has been allowed to perform D2D communications. As described above, terminal device 110-1 may receive a BSR from terminal device 110-2. In this example, terminal device 110-1 may transmit the received BSR to network device 120. In some embodiments, the network device 120 may allocate D2D communication resources upon receiving a request for D2D communication resources from the set of terminal devices 130.

In other embodiments, terminal device 110-2 may send 236 a request for D2D communication resources to network device 120. Terminal device 110-2 may also notify network device 120 that terminal device 110-2 is related to terminal device set 130. Terminal device 110-2 may send the BSR of terminal device 110-2 to network device 120.

The network device 120 may adjust 240 the allocated D2D communication resources based on the request. For example, the network device 120 may allocate new communication resources to the set of terminal devices 130 and configure new sidelink bearers. In other embodiments, network device 120 may update the resource allocation for the configured sidelink bearers. For example, the network device 120 may initially allocate a small amount of resources to the set of terminal devices 130. Terminal device 120-2 having a large video file to be transmitted may require additional resources and network device 120 may increase the amount of resources allocated.

The network device 120 determines resources from the allocated 208D 2D communication resources. In some embodiments, the resources may be determined based on the BSR of terminal device 110-2. In other embodiments, the resources may be determined based on the type of D2D communication. Network device 120 also determines a sidelink bearer from the configured set of bearers.

Network device 120 sends information regarding the determined resources and the determined sidelink bearers. As an example, network device 120 may send information regarding the determined resources and the determined sidelink bearers to terminal device 110-1, and terminal device 110-1 may relay the information to terminal device 110-2. In other example embodiments, network device 120 may send 244 information regarding the determined resources and the determined sidelink bearers to terminal device 110-2. In another embodiment, network device 120 may send 248 information regarding the determined resources and the determined sidelink bearers to both terminal devices 110-1 and 110-2. The network device 120 may also send information about the determined resources and the determined sidelink bearers to another terminal device that is to perform D2D communication with the second terminal device. Terminal device 110-2 may monitor 252 the sidelink bearer with the identifier. For example, the side link bearer can be scrambled with a cell radio network temporary identifier (C-RNTI) dedicated to the bearer, and terminal device 110-2 can monitor the side link bearer with the C-RNTI and descramble the side link bearer using the C-RNTI. In some embodiments, the information about the determined sidelink bearer comprises a bearer specific identifier.

Fig. 3 illustrates an example interaction diagram of operations 300 according to some embodiments of the present disclosure. In some embodiments, terminal device 110-2 is performing D2D communication using the determined 242 resources and the determined 243 sidelink bearers.

Terminal device 110-3 (referred to as a third terminal device) wants to perform D2D communication. Terminal device 110-3 may transmit 304D 2D communication resources for control signaling. As described above, the D2D communication resource requested here is a resource for control signaling that can be shared among several groups of terminal devices.

Network device 120 may respond 308 to the request sent from terminal device 110-3. For example, network device 120 may grant some resources to terminal device 110-2 for transmission of control signaling.

After obtaining resources for control signaling for network device 120, terminal device 110-3 may send 312 a request to terminal device 110-1 to perform D2D communication. For example, in the case of the MCX service, the terminal device 110-3 transmits an MCX transmission request message to the terminal device 110-1. In an example embodiment, terminal device 110-3 may also send the BSR for terminal device 110-3 to terminal device 110-1. The BSR may carry information about how much data to send in the buffer of terminal device 110-3. In an example embodiment, terminal device 110-3 may not send its BSR to terminal device 110-1 if the currently allocated D2D communication resources may meet the requirements of terminal device 110-3.

Terminal device 110-1 may determine 314 a priority level for terminal device 110-3. The priority level may be preconfigured to the terminal device. The priority level may be determined based on the type of D2D communication requested by the terminal device. Terminal device 110-1 may respond 316 to the request based on the determination. Terminal device 110-1 may reject the request if the priority level of terminal device 110-3 is lower than the priority level of terminal device 110-2. Terminal device 110-1 may allow terminal device 110-3 to perform D2D communication if the priority level of terminal device 110-3 is higher than the priority level of terminal device 110-2. In some embodiments, terminal device 110-1 may also notify terminal device 110-2 to stop ongoing D2D communications.

Terminal device 110-1 may send 317 a re-write indication to network device 120 indicating that terminal device 110-3 in terminal device set 130 is allowed to perform another D2D communication. Another resource request may be a message for D2D communication resources. In some embodiments, if only one D2D communication is allowed in the set of terminal devices 130, the overwrite indication sent 317 by terminal device 110-1 may be a switch bit indicating that resources need to be reallocated to a different terminal device. In some other embodiments, if there are multiple simultaneous D2D communications in terminal device set 130, the indication sent 317 by terminal device 110-1 may include an identifier of terminal device 110-3, an identifier of terminal device 110-2, and/or an identifier of a sidelink bearer used by terminal device 110-2. Network device 120 may identify the associated D2D communication resource and the associated sidelink bearer. In some embodiments, the rewrite indication may include a resource request from terminal device 110-3 to D2D communication, for example, when terminal device 110-3 requires a different resource than terminal device 110-2.

Network device 120 may send 318 a modification indication to terminal device 110-3 that terminal device 110-3 is allowed to perform another D2D communication. In some embodiments, the network device may also send 320 a modification indication to terminal device 110-2. The modification indication indicates that terminal device 110-3 is to use the resources and sidelink bearers determined for the target D2D communication. The modification indication comprises information on the D2D communication resources to be allocated to the terminal device 110-3 and an identifier of a sidelink bearer to be configured to the terminal device 110-3. For example, the modification indication may include a C-RNTI of the sidelink bearer.

The modification indication may also comprise another switch bit. Another switch bit indicates that the D2D communication resource has been reassigned to another terminal device. For example, terminal device 110-2 may understand that D2D communication resources are to be allocated to different terminal devices and may stop its D2D communication after receiving the modification indication. Additionally, the modification indication may include an identification of terminal device 110-2 and an identification of terminal device 110-3. The modification indication may also indicate that terminal device 110-2 should stop D2D communication for the previously configured sidelink bearer. Terminal device 110-2 may also cease using the previously configured sidelink bearers. In an example embodiment, terminal device 110-2 may release previously allocated D2D communication resources if the allocated resources are semi-persistent scheduling. Terminal device 110-3 may perform D2D communication using the allocated resources.

In some embodiments, network device 120 may allocate 322 the resources and sidelink bearers determined for the target D2D communication to terminal device 110-3. In some embodiments, network device 120 may send the determined resources and the determined sidelink bearers to terminal device 110-1, and terminal device 110-1 may relay the information to terminal device 110-3. Network device 120 may also stop allocating resources to terminal device 110-2 by sending 324 a cancel indication to terminal device 110-2. In some other embodiments, network device 120 may send a cancel indication to terminal device 110-1, and terminal device 110-1 may relay the information to terminal device 110-2.

Fig. 4 shows a flow diagram of a method 400 according to an example embodiment of the present disclosure. Method 400 may be implemented at network device 120.

At block 405, after receiving the resource request of the first terminal device 110-2 for performing the target D2D communication, the network device 120 determines resources for the target D2D communication from a set of resources configured to the set of terminal devices 130. The set of end devices 130 includes a first end device 110-2 and an arbitrating end device 110-1. Arbitrating terminal device 110-1 is configured to control D2D communications performed between the set of terminal devices 130.

At block 410, the network device 120 determines a sidelink bearer for the target D2D communication from the set of bearers configured to the set of terminal devices 130. The set of resources and the set of bearers are configured to be associated with D2D communications performed in the set of terminal devices 130.

In some embodiments, network device 120 may receive information from arbitrating terminal device 110-1 regarding D2D communications performed between a set of terminal devices, and configure a set of resources and a set of bearers to the set of terminal devices based on the received information. In some embodiments, the network device 120 may receive information from the core network regarding D2D communications performed between the set of terminal devices and configure the set of resources and the set of bearers to the set of terminal devices based on the received information. The information may include at least one of: quality of service (QoS) of D2D communications performed in the set of terminal devices, number of sidelink bearers used in D2D communications performed in the set of terminal devices, and maximum number of concurrent D2D communications performed between the set of terminal devices.

In an example embodiment, network device 120 may configure a logical channel and/or a sidelink bearer-specific identifier to a sidelink bearer in the set of bearers.

At block 415, the network device 120 sends information regarding the determined resources and the determined sidelink bearers. In some embodiments, network device 120 may send information regarding the determined resources and the determined sidelink bearers to at least one of first terminal device 110-2, a second terminal device in set of terminal devices 130 (e.g., terminal device 110-4), and arbitrating terminal device 110-1. The second terminal device will perform the target D2D communication with the first terminal device 110-2.

In some embodiments, network device 120 may allocate the new resource to the set of resources based on the resource request. In another embodiment, network device 120 may configure a new sidelink bearer to the set of bearers based on the resource request.

In some embodiments, network device 120 may receive the rewrite indication from the arbitrating terminal device. The override indication indicates that the third terminal device 110-3 in the set of terminal devices 130 is to be allowed to perform another D2D communication. The third terminal device 110-3 has a higher priority level than the first terminal device 110-2.

Network device 120 may transmit a modification indication indicating that the resources and side link bearers determined for the target D2D communication are to be used by the third terminal device. In some embodiments, network device 120 may send the modification indication directly to terminal device 110-2 and terminal device 110-3. In some other embodiments, network device 120 may send the modification indication to terminal device 110-1, and terminal device 110-1 then forwards the modification indication to terminal device 110-2 and terminal device 110-3.

In some embodiments, network device 120 may allocate the resources and side link bearers determined for the target D2D communication to a third terminal device, e.g., terminal device 110-3.

In some embodiments, the modification indication may include a switch bit indicating that terminal device 110-3 is to use the D2D communication resources used by terminal device 110-2. Additionally, the modification indication may include an identification of terminal device 110-2. The modification indication may also include an identification of terminal device 110-3.

Fig. 5 shows a flow chart of a method 500 according to an example embodiment of the present disclosure. Method 500 may be implemented at terminal device 110-1 as an arbitrating terminal device.

At block 505, after receiving a request from terminal device 110-1 for terminal device 110-2 to perform target D2D communication, terminal device 110-1 determines whether terminal device 110-2 is allowed to perform target D2D communication. The terminal device 110-1 is configured to control D2D communication performed between a set of terminal devices 130, the set of terminal devices 130 comprising the terminal device 110-1 and the terminal device 110-2.

At block 510, terminal device 110-1 sends a resource request to network device 120 if terminal device 110-2 is allowed to perform the target D2D communication.

At block 515, terminal device 110-1 receives information from network device 120 regarding resources and sidelink bearers determined for the target D2D communication. Resources are determined from the set of resources configured to the set of terminal devices 130 and sidelink bearers are determined from the set of bearers configured to the set of terminal devices 130. The set of resources and the set of sidelink bearers are configured to be associated with D2D information performed between the set of terminal devices 130.

In some embodiments, terminal device 110-1 may send information to network device 120 regarding D2D communications performed between the set of terminal devices 130. The information may include at least one of: qoS of D2D communication performed between the set of terminal devices 130, the number of sidelink bearers used in D2D communication performed between the set of terminal devices 130, and the maximum number of concurrent D2D communication performed between the set of terminal devices 130.

In some embodiments, terminal device 110-1 may compare the priority level of terminal device 110-3 to the priority level of terminal device 110-2 after receiving another request from terminal device 110-3 to perform another D2D communication.

In some embodiments, terminal device 110-1 may allow terminal device 110-3 to perform another D2D communication if the priority level of terminal device 110-3 is higher than the priority level of terminal device 110-2.

In some embodiments, terminal device 110-1 may send a rewrite indication to network device 120. The override indication indicates that terminal device 110-3 will use the resources and sidelink bearers assigned to terminal device 110-2.

Fig. 6 is a simplified block diagram of a device 600 suitable for implementing embodiments of the present disclosure. Device 600 may be implemented at network device 120. Device 600 may also be implemented at terminal device 110. As shown, the device 600 includes one or more processors 610, one or more memories 620 coupled to the processor(s) 610, one or more transmitters and/or receivers (TX/RX) 640 coupled to the processor 610.

The processor 610 may be of any type suitable to the local technology network and may include one or more of general purpose computers, special purpose computers, microprocessors, digital Signal Processors (DSPs) and processors based on a multi-core processor architecture, as non-limiting examples. The device 600 may have multiple processors, such as application specific integrated circuit chips, that are time dependent from a clock synchronized with the main processor.

The memory 620 may be of any type suitable to the local technology network and may be implemented using any suitable data storage technology, such as non-transitory computer-readable storage media, semiconductor-based storage devices, magnetic storage devices and systems, optical storage devices and systems, fixed memory and removable memory, as non-limiting examples.

Memory 620 stores at least a portion of program 630. TX/RX 640 is used for bi-directional communication. TX/RX 640 has at least one antenna to facilitate communication, although in practice an access node referred to in this application may have multiple antennas. The communication interface may represent any interface necessary to communicate with other network elements.

The programs 630 are assumed to include program instructions that, when executed by the associated processor 610, enable the device 600 to operate in accordance with embodiments of the present disclosure, as discussed with reference to fig. 2-5. That is, embodiments of the present disclosure may be implemented by computer software executable by the processor 610 of the device 600, or by hardware, or by a combination of software and hardware.

While this specification contains many specific implementation details, these should not be construed as limitations on the scope of any disclosure or of what may be claimed, but rather as descriptions of features specific to particular embodiments of particular disclosures. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. And (6) obtaining the result. In some cases, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

Various modifications to the foregoing exemplary embodiments of this disclosure will become apparent to those skilled in the art from the foregoing description, when read in conjunction with the accompanying drawings. Any and all modifications will still fall within the scope of the non-limiting and exemplary embodiments of this disclosure. Moreover, other embodiments of the present disclosure set forth herein will suggest themselves to those skilled in the art having the benefit of the teachings presented in the foregoing description and the associated drawings.

Therefore, it is to be understood that the embodiments of the disclosure are not to be limited to the specific embodiments disclosed and that modifications and other embodiments are intended to be included within the scope of the appended claims. Although specific terms are employed herein, they are used in a generic and descriptive sense only and not for purposes of limitation.

Claims

1. A method implemented at a network device, comprising:

in response to receiving a resource request by a first terminal device for performing target device-to-device (D2D) communication, determining a resource for the target D2D communication from a set of resources configured to a set of terminal devices, the set of terminal devices including the first terminal device and an arbitrating terminal device configured to control D2D communication performed between the set of terminal devices;

determining a sidelink bearer for the target D2D communication from a set of bearers configured to the set of terminal devices, the set of resources and the set of bearers being configured to be associated with the D2D communication performed between the set of terminal devices; and

transmitting information about the determined resources and the determined sidelink bearers.

2. The method of claim 1, further comprising:

receiving, from the arbitrating terminal device, information about the D2D communications performed between the set of terminal devices; and

and configuring the resource set and the bearing set to the terminal equipment set based on the received information.

3. The method of claim 2, wherein configuring the set of bearers comprises:

configuring at least one of the following to a side bearer in the bearer set: logical channels and sidelinks carry specific identifiers.

4. The method of claim 2, wherein the information about the D2D communication performed between the set of terminal devices comprises at least one of:

a quality of service (QoS) of the D2D communication performed between the set of terminal devices,

a number of sidelink bearers used in the D2D communication performed between the set of terminal devices, and

a maximum number of concurrent D2D communications performed between the set of terminal devices.

5. The method of claim 1, wherein sending information about the determined resources and the determined sidelink bearers comprises:

sending the information about the determined resources and the determined side link bearers to at least one of:

the first terminal device is configured to be able to receive the first message,

a second terminal device of the set of terminal devices to perform the target D2D communication with the first terminal device, an

The arbitration terminal device.

6. The method of any of claims 1-5, further comprising:

receiving a rewrite indication from the arbitrating terminal device, the rewrite indication indicating that a third terminal device of the set of terminal devices is allowed to perform another D2D communication, the third terminal device having a higher priority level than the first terminal device;

sending a modification indication indicating that the resources and the sidelink bearers determined for the target D2D communication are to be used by the third terminal device; and

allocating the resources and the side link bearer determined for the target D2D communication to the third terminal device.

7. The method of claim 6, wherein the modification indication comprises at least one of:

a handover bit indicating that the resources and the side link bearer determined for the target D2D communication are to be used by the third terminal device,

an identity of the first terminal device, and

an identity of the third terminal device.

8. A method implemented at an arbitrating terminal device, comprising:

in response to receiving a request from a first terminal device for the first terminal device to perform target device-to-device (D2D) communication, determining whether the first terminal device is allowed to perform the target D2D communication, the arbitrating terminal device being configured to control D2D communication performed between a set of terminal devices, the set of terminal devices including the first terminal device and the arbitrating terminal device;

in response to the first terminal device being allowed to perform the target D2D communication, sending a resource request to a network device; and

receiving, from the network device, information on resources determined for the target D2D communication and a sidelink bearer, the resources being determined from a set of resources configured to the set of terminal devices, the sidelink bearer being determined from a set of bearers configured to the set of terminal devices, the set of resources and the set of bearers being configured to be associated with the D2D communication performed between the set of terminal devices.

9. The method of claim 8, further comprising:

sending information about the D2D communication performed between the set of terminal devices to the network device.

10. The method of claim 9, wherein the information about the D2D communication performed between the set of terminal devices comprises at least one of:

11. The method according to any one of claims 8-10, further comprising:

in response to receiving another request from a third terminal device to perform another D2D communication, comparing the priority level of the third terminal device with the priority level of the first terminal device;

in response to the priority level of the third terminal device being higher than the priority level of the first terminal device, allowing the third terminal device to perform the further D2D communication; and

sending a rewrite indication to the network device, the rewrite indication indicating that the third terminal device of the set of terminal devices is to use the resources and the side link bearer assigned to the first terminal device.

12. A network device, comprising:

at least one processor; and

a memory coupled with the at least one processor, the memory storing instructions therein, which when executed by the at least one processor, cause the network device to perform acts comprising:

13. The network device of claim 12, wherein the actions further comprise:

14. The network device of claim 13, wherein configuring the set of bearers comprises:

15. The network device of claim 13, wherein the information about the D2D communication performed between the set of terminal devices comprises at least one of:

16. The network device of claim 12, wherein sending information about the determined resources and the determined sidelink bearers comprises:

sending the information about the determined resources and the determined sidelink bearers to at least one of:

The arbitration terminal device.

17. The network device of any of claims 12-16, wherein the actions further comprise:

18. The network device of claim 17, wherein the modification indication comprises at least one of:

a switch bit indicating that the resources and the side link bearer determined for the target D2D communication are to be used by the third terminal device,

an identity of the first terminal device, and

an identity of the third terminal device.

19. An arbitrating terminal device, the arbitrating terminal device being in a set of terminal devices, the arbitrating terminal device configured to control device-to-device (D2D) communications performed in the set of terminal devices, the arbitrating terminal device comprising:

at least one processor; and

a memory coupled with the at least one processor, the memory storing instructions therein, which when executed by the at least one processor, cause the terminal device to perform acts comprising:

20. The arbitrating terminal device of claim 19, wherein the actions further comprise:

21. The arbitrating terminal device of claim 19, wherein the information about the D2D communications performed between the set of terminal devices comprises at least one of:

22. The arbitrating terminal device of any one of claims 19-21, wherein the actions further comprise:

sending a rewrite indication to the network device, the rewrite indication indicating that the third terminal device of the set of terminal devices is to use the resources and the sidelink bearer allocated to the first terminal device.

23. A computer-readable medium having stored thereon instructions that, when executed by at least one processing unit of a machine, cause the machine to perform the method of any one of claims 1 to 7.

24. A computer-readable medium having stored thereon instructions that, when executed by at least one processing unit of a machine, cause the machine to perform the method of any one of claims 8-11.