WO2024065117A1

WO2024065117A1 - Temporary identifier scheduling method and apparatus, device, storage medium, and chip

Info

Publication number: WO2024065117A1
Application number: PCT/CN2022/121490
Authority: WO
Inventors: 杨星
Original assignee: 北京小米移动软件有限公司
Priority date: 2022-09-26
Filing date: 2022-09-26
Publication date: 2024-04-04
Also published as: CN116097635A

Abstract

The present invention relates to the technical field of communications, and provides a temporary identifier scheduling method and apparatus, a device, a storage medium, and a chip, which are applied to a first relay device. The method comprises: receiving a temporary identifier of at least one device in a sidelink; and, in response to there being a temporary identifier conflict with the temporary identifier of the device, sending a conflict indication to a peer device of the device. Using the method for scheduling a temporary identifier set forth in the present disclosure, a conflict indication can be sent to a peer device so as to instruct the peer device to reallocate the temporary identifier for the device, thereby preventing the occurrence of data loss caused by temporary identifier conflict.

Description

Temporary identification scheduling method, device, equipment, storage medium and chip

Technical Field

The present disclosure relates to the field of communication technology, and in particular to a temporary identification scheduling method, device, equipment, storage medium and chip.

Background technique

In order to support direct communication between UE (user equipment) and UE, the sidelink communication mode is introduced. UE and UE can communicate through the PC-5 interface (direct communication interface). When a UE needs to communicate with a base station but is outside the coverage of the base station network, it can use the relay of another UE within the coverage of the base station network to achieve communication with the base station. Among them, the UE that is not connected to the base station is called a remote UE (remote UE), and the UE that provides relay function is called a relay UE (relay UE). The remote UE and the relay UE can communicate in unicast, multicast and broadcast through the sidelink. When the remote UE sends data, it needs to indicate the source address and destination address of the data. The relay UE can forward the data based on the source address and destination address, and the peer UE receives the data based on the source address or destination address.

In the related technology, temporary identifiers can be allocated to the remote UE and the opposite UE in the relay group to determine the remote UE and the opposite UE. The relay group includes the remote UE, the relay UE and the opposite UE. The UE can act as a relay UE in one relay group and as a remote UE in another relay group. When the UE receives a temporary identifier sent by the opposite UE as a relay UE in a relay group, and it is the same as the temporary identifier sent by the UE as a remote UE in another relay group. The UE cannot distinguish whether the received temporary identifier needs to be forwarded by the UE to a remote device in a certain relay group, or is sent by the relay UE in another relay group to the UE itself. As a result, there may be a situation where the resolution error leads to data loss.

Summary of the invention

In order to overcome the problems existing in the related art, the present disclosure provides a temporary identification scheduling method, device, equipment, storage medium and chip.

According to a first aspect of an embodiment of the present disclosure, a temporary identification scheduling method is provided, which is applied to a first relay device, including:

receiving a temporary identification of at least one device in a sidelink;

In response to a temporary identifier conflict existing in the temporary identifiers of the device, a conflict indication is sent to a peer device of the device.

According to a second aspect of an embodiment of the present disclosure, a temporary identifier scheduling method is provided, which is applied to a first remote device, including:

forwarding the conflict indication sent by the first relay device to a device in the sidelink;

Receives a temporary identification of a device in the sidelink.

According to a third aspect of an embodiment of the present disclosure, a temporary identifier scheduling method is provided, which is applied to a first peer device, including:

receiving a conflict indication sent by a device on a side link;

A temporary identifier is reallocated to the corresponding device according to the conflict indication.

According to a fourth aspect of an embodiment of the present disclosure, a temporary identification scheduling device is provided, which is applied to a first relay device, including:

A first receiving module is configured to receive a temporary identification of at least one device in a sidelink;

The first sending module is configured to send a conflict indication to a peer device of the device in response to a temporary identifier conflict existing in the temporary identifiers of the device.

According to a fifth aspect of an embodiment of the present disclosure, a temporary identification scheduling device is provided, which is applied to a first remote device, including:

a conflict indication forwarding module, configured to forward the conflict indication sent by the first relay device to a device in the sidelink;

The second receiving module is configured to receive a temporary identifier sent by a device in the side link.

According to a sixth aspect of an embodiment of the present disclosure, a temporary identifier scheduling device is provided, which is applied to a first opposite-end device, including:

A conflict indication receiving module, configured to receive a conflict indication sent by a sidelink device;

The temporary identification allocation module is configured to reallocate a temporary identification to the corresponding device according to the conflict indication.

According to a seventh aspect of an embodiment of the present disclosure, a relay device is provided, including:

processor;

a memory for storing processor-executable instructions;

The processor is configured to implement the temporary identification scheduling method provided in the first aspect of the embodiment of the present disclosure when executing the executable instructions.

According to an eighth aspect of an embodiment of the present disclosure, a remote device is provided, including:

processor;

a memory for storing processor-executable instructions;

The processor is configured to implement the temporary identification scheduling method provided in the second aspect of an embodiment of the present disclosure when executing the executable instructions.

According to a ninth aspect of an embodiment of the present disclosure, a peer device is provided, including:

processor;

a memory for storing processor-executable instructions;

Among them, the processor is configured to implement the temporary identification scheduling method provided by the third aspect of the embodiment of the present disclosure when executing the executable instructions.

According to the tenth aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided, on which computer program instructions are stored. When the program instructions are executed by a processor, the steps of the temporary identification scheduling method provided by the first aspect of the present disclosure are implemented, or the steps of the temporary identification scheduling method provided by the second aspect of the present disclosure are implemented, or the steps of the temporary identification scheduling method provided by the third aspect of the present disclosure are implemented.

According to the eleventh aspect of an embodiment of the present disclosure, a chip is provided, comprising a processor and an interface; the processor is used to read instructions to execute the steps of the temporary identification scheduling method provided by the first aspect of the present disclosure, or to execute the steps of the temporary identification scheduling method provided by the second aspect of the present disclosure, or to execute the steps of the temporary identification scheduling method provided by the third aspect of the present disclosure.

The technical solution provided by the embodiments of the present disclosure may have the following beneficial effects:

Through the above technical solution, when the first relay device receives a temporary identifier of at least one device in the side link and there is a temporary identifier conflict, it can send a conflict indication to the opposite device of the device, instructing the opposite device to reallocate a temporary identifier for the device based on the conflict indication, so as to avoid data loss caused by the temporary identifier conflict.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

Fig. 1 is a flow chart showing a temporary identification scheduling method according to an exemplary embodiment.

Fig. 2 is a schematic diagram showing a first relay group and a second relay group according to an exemplary embodiment.

Fig. 3 is a flow chart showing a temporary identification scheduling method according to an exemplary embodiment.

Fig. 4 is a flow chart showing a temporary identification scheduling method according to an exemplary embodiment.

Fig. 5 is a flow chart showing a temporary identification scheduling method according to an exemplary embodiment.

Fig. 6 is a flow chart showing a temporary identification scheduling method according to an exemplary embodiment.

Fig. 7 is a flow chart showing a temporary identification scheduling method according to an exemplary embodiment.

Fig. 8 is a flow chart showing a temporary identification scheduling method according to an exemplary embodiment.

Fig. 9 is a flow chart showing a temporary identification scheduling method according to an exemplary embodiment.

Fig. 10 is a flow chart showing a temporary identification scheduling method according to an exemplary embodiment.

Fig. 11 is a flow chart showing a temporary identification scheduling method according to an exemplary embodiment.

Fig. 12 is a block diagram showing a temporary identification scheduling device according to an exemplary embodiment.

Fig. 13 is a block diagram showing a temporary identification scheduling device according to an exemplary embodiment.

Fig. 14 is a block diagram showing a temporary identification scheduling device according to an exemplary embodiment.

Fig. 15 is a block diagram of a device according to an exemplary embodiment.

Detailed ways

Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

It is to be understood that in the present disclosure, "plurality" refers to two or more than two, and other quantifiers are similar thereto. "And/or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and/or B may represent: A exists alone, A and B exist at the same time, and B exists alone. The character "/" generally indicates that the associated objects before and after are in an "or" relationship. The singular forms "a", "the" and "the" are also intended to include the plural forms, unless the context clearly indicates other meanings.

It is further understood that the terms "first", "second", etc. are used to describe various information, but such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other, and do not indicate a specific order or degree of importance. In fact, the expressions "first", "second", etc. can be used interchangeably. For example, without departing from the scope of the present disclosure, the first remote device can be referred to as a first peer device, the second remote device can be referred to as a second peer device, and the first relay device can be referred to as a second relay device. Similarly, the first peer device can also be referred to as a first remote device, the second peer device can also be referred to as a first peer device, and the second relay device can also be referred to as a first relay device.

It is further understood that, although the operations are described in a specific order in the drawings in the embodiments of the present disclosure, it should not be understood as requiring the operations to be performed in the specific order shown or in a serial order, or requiring the execution of all the operations shown to obtain the desired results. In certain environments, multitasking and parallel processing may be advantageous.

It should be noted that all actions of acquiring signals, information or data in this application are carried out in compliance with the relevant data protection laws and policies of the country where they are located and with the authorization given by the owner of the corresponding device.

Fig. 1 is a flow chart showing a temporary identification scheduling method according to an exemplary embodiment. As shown in Fig. 1 , the temporary identification scheduling method is used in a first relay device and includes the following steps.

In step S101, a temporary identification of at least one device in a sidelink is received.

Among them, at least one device in the sidelink includes at least one of a peer device, a relay device and a remote device. The sidelink (SL) supports communication between UEs. The sidelink includes a physical sidelink control channel (PSCCH) and a physical sidelink shared channel (PSSCH). The sending UE sends sidelink control information (SCI) on the PSCCH channel and sends the second-stage SCI on the PSSCH channel. The SCI carries the resource location of the transmission data, the source identifier of the sending UE and the target identifier of the receiving UE.

The sending UE is the party that sends data or signaling, and can be a relay UE, a remote UE, or a peer UE; the receiving UE is the party that receives data or signaling, and can be a relay UE, a remote UE, or a peer UE. In the present disclosure, a UE may communicate with a base station through the relay of another UE without being directly connected to the base station, wherein a UE that is not connected to the base station is called a remote UE (remote UE), and a UE that provides a relay function is called a relay UE (relay UE). This architecture is called U2N (UE to NW) relay. Among them, the equipment in the side link includes a remote UE, a relay UE, and a peer UE, and the peer UE is a UE that communicates with the remote UE through the relay UE.

The relay UE, remote UE and opposite UE may be mobile phones, tablets, portable computers, computers with wireless transceiver functions, virtual reality (virtual reality, VR) terminal devices, augmented reality (augmented reality, AR) terminal devices, wireless terminals in industrial control, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, etc. The present disclosure does not limit the application scenarios. UE may sometimes also be referred to as terminal equipment, terminal, access terminal, UE unit, UE station, mobile device, mobile station, mobile station, mobile client, etc. For ease of description, the present disclosure may refer to the first relay UE as a first relay device, the first remote UE as a first remote device, the first opposite UE as a first opposite device, the second relay UE as a second relay device, the second remote UE as a second remote device, and the second opposite device as a second opposite device.

The sidelink can be a D2D (Device to Device) link, such as a mobile phone to mobile phone communication link or a mobile phone to a wearable device communication link; in the Internet of Vehicles, the sidelink can also be a vehicle to vehicle (V2V) communication link, a vehicle to pedestrian (V2P) communication link, a vehicle to infrastructure (V2I) link or a vehicle to any device (V2X) communication link.

Sidelink communication supports three communication modes: unicast, multicast and broadcast. Unicast refers to a sending UE transmitting information to a receiving UE, and each receiving UE in unicast corresponds to a destination identifier; multicast refers to a sending UE transmitting information to multiple receiving UEs, and each group of receiving UEs in multicast corresponds to a destination identifier; broadcast refers to a sending UE transmitting information to all receiving UEs within its network coverage, and in broadcast, all receiving UEs within the network coverage of the sending UE correspond to a destination identifier.

Among them, in order to support direct communication between UEs, in this embodiment, data communication can be established between UEs through 5G (fifth generation mobile communication system) and 4G (fifth generation mobile communication system) communication technologies, and based on the sidelink communication mode, UEs can communicate directly with each other through the PC-5 interface. In the embodiments of the present disclosure, the UE can be based on a variety of network standards and use the sidelink communication mode to communicate directly with other UEs. It should be noted that the various network standards may include 4G, 5G, or 4G, 5G evolution technology, etc.

In the present disclosure, there may be multiple relay groups in the network, each of which includes a remote device, a relay device, and a peer device. For example, referring to FIG2 , a first relay device in a first relay group may be used as a link for communication between a first peer device and a first remote device, and a second relay device in a second relay group may be used as a link for communication between a second peer device and a second remote device.

When the peer device allocates a temporary identifier to the remote device, the relay device needs to forward it. When the remote device allocates a temporary identifier to the peer device, the relay device also needs to forward it. Therefore, the relay device can receive the temporary identifiers allocated by the peer device and the remote device to each other in the side link.

Wherein, in the case where the relay device receives a temporary identifier assigned by the peer device to the remote device, the relay device can obtain the temporary identifier from the peer device and/or the remote device; in the case where the relay device receives a temporary identifier assigned by the remote device to the peer device, the relay device can obtain the temporary identifier from the remote device and/or the peer device. Specifically, please refer to FIG2 , when the first relay device determines the temporary identifier of the first remote device, the first relay device receives the temporary identifier of the first remote device from the first remote device, and/or the first relay device receives the temporary identifier of the first remote device from the first peer device; when the first relay device determines the temporary identifier of the first peer device, the first relay device receives the temporary identifier of the first peer device from the first peer device, and/or the first relay device receives the temporary identifier of the first peer device from the first remote device.

Among them, the temporary identifier is generated to save signaling. For example, when the remote device as a sending device sends data to the opposite device, it needs to indicate the source address of the remote device and the destination address of the opposite device, so that the relay device can forward the data according to the source address and the destination address, and the opposite device as a receiving device can receive the data according to the source address. In this process, the string of signaling corresponding to the source address and the destination address is relatively long, resulting in the remote device and the relay device needing to use more network resources to achieve data transmission, wasting signaling and causing network resources to be occupied.

In order to save signaling, the remote device can carry a temporary identifier assigned by the remote device to the other device in the data when sending data to the other device. For example, 1 is used. The temporary identifier has a shorter string, which saves signaling. Therefore, the remote device and the relay device can use fewer network resources to realize data transmission, thus releasing some network resources.

In step S102, in response to a temporary identifier conflict existing among the temporary identifiers of the device, a conflict indication is sent to a peer device of the device.

The devices communicate with each other through a relay device. For example, when the device is a peer device, the peer device of the device may be a remote device, and when the device is a remote device, the peer device of the device may be a peer device. That is, two devices connected to each other through a relay device are each other's peer device and remote device. The peer device and the remote device may assign temporary identifiers to each other, so when there is a temporary identifier conflict between the temporary identifiers of the device, a conflict indication may be sent to the peer device of the device so that the peer device can reallocate a temporary identifier to the device. The relay device sends the conflict indication to the peer device or forwards the conflict indication to the peer device through the remote device.

Although allocating temporary identifiers between the peer device and the remote device can save signaling and release some network resources, there may be temporary identifier conflicts, resulting in the relay device being unable to correctly forward data.

For example, please refer to FIG. 2. C, as a first relay device, can forward the temporary identifier assigned by the first peer device B to the first remote device D to the first remote device D. C, as a second remote device, can also receive the temporary identifier returned by the second peer device A to the device C itself through the second relay device B. When the temporary identifier sent to C by the first peer device B and received by C as the first relay device is the same as the temporary identifier assigned to C by the second peer device A, C is not sure whether the temporary identifier is assigned to itself by the second peer device A through the second relay device B, or whether the first peer device B needs to forward it to the first remote device D through itself. In other words, C does not know whether it is a relay device or a remote device in the two devices connected through the relay device, that is, C does not know whether the temporary identifier is assigned to itself or needs to be sent to other devices through itself. Therefore, there is a possibility of misidentification, and if misidentification occurs, data loss will result.

In order to avoid data loss, the present disclosure proposes that when a temporary identifier of a device received by a relay device has a temporary identifier conflict, a conflict indication will be sent to a peer device of the device.

For example, when the first relay device determines that the temporary identifier assigned by the first peer device to the first remote device is the same as the temporary identifier of the first relay device itself, it confirms that there is a temporary identifier conflict between the first relay device and the first remote device, and a conflict indication can be sent to the first peer device.

The temporary identifier conflict refers to the situation that the relay device cannot distinguish the devices corresponding to the two temporary identifiers based on the two temporary identifiers it has received.

The conflict indication carries information about a conflict between two temporary identifiers, and is used to instruct the device's peer device to reallocate a temporary identifier to the device based on the conflict indication; the conflict indication may also carry a temporary identifier suggested by the first relay device, which is different from the conflicting temporary identifier, so as to distinguish it from the conflicting temporary identifier.

The reallocation in any embodiment of the present disclosure may include: before the device has not received the temporary identifier allocated by the opposite device of the device, determining that there is a temporary conflict, and the opposite device of the device reallocates the temporary identifier to the device.

For example, before the remote device receives the temporary identifier assigned by the peer device, the relay device determines that the temporary identifier to be assigned to the remote device conflicts with the temporary identifier of the relay device itself. In order to avoid the relay device being unable to distinguish different devices based on the same temporary identifier, the relay device sends a conflict indication to the peer device of the device. The peer device of the device can reallocate a temporary identifier for the remote device, and the remote device receives the reallocated temporary identifier.

FIG3 is a flow chart of a temporary identification scheduling method shown in an exemplary embodiment. As shown in FIG3 , the temporary identification scheduling method is used in a first relay device and includes the following steps.

In step S201, a temporary identification of at least one device in a sidelink is received.

For example, the method for receiving a temporary identifier of a device in a sidelink in an embodiment of the present disclosure can refer to the above step S101 and will not be repeated. At least one device includes a first remote device or a first opposite device, and in response to a temporary identifier conflict existing in the temporary identifier of the device, sending a conflict indication to the opposite device of the device includes at least one item in step S202.

In step S202, in response to a temporary identification conflict between the first relay device and the first remote device, a conflict indication is sent to the first remote device; in response to a temporary identification conflict between the first relay device and the first remote device, a conflict indication is sent to the first remote device; wherein, the first remote device is a remote device to which the first remote device is connected via the first relay device.

Among them, when there is a temporary identification conflict between the first relay device and the first remote device, the first relay device directly forwards the conflict indication to the first opposite device or forwards the conflict indication to the first opposite device through the first remote device; when there is a temporary identification conflict between the first opposite device and the first relay device, the first relay device directly forwards the conflict indication to the first remote device or forwards the conflict indication to the first remote device through the first opposite device.

For example, if the first relay device has the ability to parse, process and forward content, it can directly receive the temporary identifier assigned by the first peer device to the first remote device, and generate a first conflict indication when it is determined that the temporary identifier conflicts with its own temporary identifier; the first conflict indication is then sent directly to the first peer device, and the first peer device reallocates a temporary identifier to the first remote device based on the first conflict indication, and the reallocated temporary identifier is then forwarded to the first remote device via the first relay device, so that the first remote device uses the reallocated temporary identifier.

If the first relay device does not perform the function of parsing and processing the forwarded content, the content of the forwarded data cannot be determined. At this time, the first relay device can forward the temporary identifier assigned by the first counterpart device to the first remote device to the first remote device, and then receive the temporary identifier determined by the first remote device, and generate a first conflict indication when it is determined that the temporary identifier sent by the first remote device conflicts with its own temporary identifier; then the first conflict indication is forwarded to the first remote device, the first remote device parses and determines the first conflict indication, and then returns the first conflict indication to the first relay device, and forwards it to the first counterpart device through the first relay device.

In some embodiments, in response to a temporary identifier conflict between the first relay device and the first remote device, a conflict indication may be sent to the first opposite device.

For example, please refer to Figure 2. Since the remote device assigns a temporary identifier to the opposite device and the opposite device assigns a temporary identifier to the remote device, when the first relay device acts as the second remote device, the temporary identifier assigned to the first remote device received by the first relay device from the second opposite device is the temporary identifier of the first relay device itself; the temporary identifier received by the first relay device from the first opposite device is the temporary identifier of the first remote device. If the two temporary identifiers conflict, the first relay device cannot distinguish whether the temporary identifier is its own or that of the first remote device.

At this time, the first relay device may send a conflict indication to the first opposite device in response to a temporary identifier conflict between the first relay device and the first remote device, to instruct the first opposite device to reallocate a temporary identifier different from the temporary identifier of the first remote device to the first remote device.

In some embodiments, in response to a temporary identifier conflict between the first relay device and the first peer device, a conflict indication may be sent to the first remote device.

For example, please refer to Figure 2, the temporary identifier received by the first relay device from the second peer device is the temporary identifier of the first relay device itself, and the temporary identifier received by the first relay device from the first remote device is the first peer device. If the two temporary identifiers conflict, the first relay device cannot distinguish whether the temporary identifier is its own or that of the first peer device.

At this time, the first relay device can send a conflict indication to the first remote device in response to a temporary identifier conflict between the first relay device and the first counterpart device, to instruct the first remote device to reallocate a temporary identifier different from the temporary identifier of the first counterpart device to the first counterpart device.

In some embodiments, in response to a temporary identification conflict between the first relay device and the first remote device, a conflict indication may be sent to the first remote device, and in response to a temporary identification conflict between the first relay device and the first remote device, a conflict indication may be sent to the first remote device.

For example, please refer to Figure 2, when the temporary identifiers of the first relay device, the first peer device and the first remote device conflict, it indicates that the first relay device cannot distinguish whether the temporary identifier is its own, the first remote device, or the first peer device.

At this time, the first relay device sends a conflict indication to the first remote device in response to a temporary identifier conflict between the first relay device and the first remote device, instructing the first remote device to reallocate a temporary identifier that is different from the temporary identifier of the first remote device to the first remote device so as to distinguish it from the temporary identifier of the first relay device itself; and the first relay device sends a conflict indication to the first remote device in response to a temporary identifier conflict between the first relay device and the first remote device, instructing the first remote device to reallocate an identifier that is different from the temporary identifier of the first remote device to the first remote device so as to distinguish it from the temporary identifier of the first relay device itself.

Among them, when the temporary identifiers of the first relay device conflict with the first counterpart device, and the temporary identifiers of the first relay device conflict with the first remote device, the temporary identifier reallocated by the first counterpart device to the first remote device is different from the temporary identifier reallocated by the first remote device to the first counterpart device.

Through the above technical scheme, when the temporary identifier received by the first relay device from the first peer device conflicts with the temporary identifier of the first relay device, a conflict indication can be sent to the first remote device to inform the first remote device that there is a temporary identifier conflict between the first peer device and the first relay device, and instruct the first remote device to reallocate a temporary identifier to the first peer device to avoid the first relay device being unable to distinguish between the temporary identifier of the first peer device and the temporary identifier of the first relay device itself; when the temporary identifier received by the first relay device from the first remote device is the same as the temporary identifier of the first relay device, a conflict indication can be sent to the first remote device to inform the first remote device that there is a temporary identifier conflict between the first remote device and the first relay device, and instruct the first remote device to reallocate a temporary identifier to the first remote device to avoid the first relay device being unable to distinguish between the temporary identifier of the first remote device and the temporary identifier of the first relay device itself.

FIG. 4 is a flow chart of a temporary identification scheduling method according to an exemplary embodiment. As shown in FIG. 4 , the temporary identification scheduling method is used in a first relay device and includes the following steps.

In step S301, a temporary identification of at least one device in a sidelink is received.

For example, the method for receiving a temporary identifier of a device in a sidelink in an embodiment of the present disclosure may refer to the above-mentioned step S101, which will not be described in detail.

In step S302, when the first temporary identifier of the first relay device is the same as the second temporary identifier of the first remote device, it is determined that there is a temporary identifier conflict between the first relay device and the first remote device.

The first relay device forwards the second temporary identifier assigned by the first peer device to the first remote device in the first relay group to the first remote device; when the first relay device is in the second relay group as the second remote device, it receives the first temporary identifier assigned by the second peer device to the first relay device. In any embodiment of the present disclosure, if the first relay group and the second relay group have the same devices, a temporary identifier conflict may occur, for example, the first relay group and the second relay group have the same B and C.

Among them, when the first temporary identifier of the first relay device is the same as the second temporary identifier of the first remote device, the first relay device cannot distinguish whether the first temporary identifier and the second temporary identifier should be its own or need to be forwarded to the first remote device, so there will be a temporary identifier conflict.

In step S303, in response to a temporary identifier conflict between the first relay device and the first remote device, a first conflict indication is sent to the first opposite device, where the first conflict indication is used to instruct the first opposite device to reallocate a temporary identifier to the first remote device.

When the first relay device determines that the first temporary identifier conflicts with the second temporary identifier, a first conflict indication may be generated and the first conflict indication may be directly forwarded to the first opposite-end device.

For example, if the first relay device has the ability to parse and process the forwarded content, the first conflict indication can be sent directly to the first peer device. The first peer device reallocates a temporary identifier for the first remote device based on the first conflict indication. The temporary identifier is different from the first temporary identifier and the second temporary identifier. The reallocated temporary identifier is then forwarded to the first remote device via the first relay device so that the first remote device uses the reallocated temporary identifier.

The first conflict indication may carry a temporary identifier recommended by the first relay device for the first remote device. The first opposite device may use the recommended temporary identifier to reallocate to the first remote device. The recommended temporary identifier is different from the first temporary identifier and the second temporary identifier. Of course, the first opposite device may not adopt the recommended temporary identifier, but regenerate a temporary identifier that is different from the first temporary identifier and the second temporary identifier to reallocate to the first remote device.

In any embodiment of the present disclosure, the first peer device may be a first remote device, and the first remote device may be a first peer device, so the above steps may be converted into the first remote device allocating a temporary identifier to the first peer device, and the specific steps are similar to the above steps and will not be repeated.

Through the above technical solution, when the first relay device receives a second temporary identifier of the first remote device that is identical to the first temporary identifier of the first relay device, it is determined that there is a temporary identifier conflict. At this time, a first conflict indication can be sent to the first opposite device to instruct the first opposite device to reallocate the temporary identifier to the first remote device based on the first conflict indication. When the first remote device has a reallocated temporary identifier that is different from the first temporary identifier, the first relay device can distinguish the temporary identifier of the first remote device from the temporary identifier of the first relay device itself based on the different temporary identifiers to avoid data loss.

FIG. 5 is a flow chart of a temporary identification scheduling method according to an exemplary embodiment. As shown in FIG. 5 , the temporary identification scheduling method is used in a first relay device and includes the following steps.

In step S401, a temporary identification of at least one device in a sidelink is received.

In step S402, when the first temporary identifier of the first relay device is the same as the second temporary identifier of the first remote device, it is determined that there is a temporary identifier conflict between the first relay device and the first remote device.

For example, the method for determining the conflict between the temporary identifiers of the first relay device and the first remote device in the embodiment of the present disclosure may refer to the above step S302, which will not be described in detail.

In step S403, in response to a temporary identifier conflict between the first relay device and the first remote device, the first conflict indication is sent to the first remote device; the first conflict indication is used to instruct the first opposite device to reallocate a temporary identifier to the first remote device.

When the first relay device determines that the first temporary identifier conflicts with the second temporary identifier, a first conflict indication may be generated and forwarded to the first opposite-end device via the first remote device.

For example, if the first relay device does not have the ability to parse and process the forwarded content, the first conflict indication can be sent directly to the first remote device. After the first remote device parses and determines the first conflict indication, it forwards the first conflict indication to the first relay device, and then uses the first relay device to forward it to the first opposite device. At this time, the first relay device plays the role of forwarding data without parsing and processing the data forwarded by the first opposite device and the first remote device; the first opposite device reallocates a temporary identifier for the first remote device based on the first conflict indication, and the temporary identifier is different from the first temporary identifier and the second temporary identifier. The reallocated temporary identifier is then forwarded to the first remote device through the first relay device, so that the first remote device uses the reallocated temporary identifier.

Through the above technical solution, when the first relay device receives a second temporary identifier of the first remote device that is identical to the first temporary identifier of the first relay device, it is determined that there is a temporary identifier conflict. At this time, a first conflict indication can be sent to the first remote device. The first remote device returns the first conflict indication to the first opposite device through the first relay device to instruct the first opposite device to reallocate a temporary identifier to the first remote device based on the first conflict indication. When the first remote device has a reallocated temporary identifier that is different from the first temporary identifier, the relay device can distinguish the temporary identifier of the first remote device from the temporary identifier of the first relay device based on different temporary identifiers to avoid data loss.

FIG. 6 is a flow chart of a temporary identification scheduling method according to an exemplary embodiment. As shown in FIG. 6 , the temporary identification scheduling method is used in a first relay device and includes the following steps.

In step S501, a temporary identification of at least one device in a sidelink is received.

In step S502, when the third temporary identifier of the first peer device is the same as the fourth temporary identifier of the second peer device, it is determined that there is a temporary identifier conflict between the first peer device and the second peer device.

The first relay device can not only receive the third temporary identifier of the first peer device and the second temporary identifier of the first remote device, but also determine the fourth temporary identifier allocated to the second peer device as the second remote device.

For example, in the second relay group, since the second remote device and the second opposite device can assign temporary identifiers to each other, the first relay device, as the second remote device, can directly determine the temporary identifier of the second opposite device.

When the first relay device determines that the temporary identifiers of the first peer device and the second peer device are the same, the second relay device cannot determine whether the temporary identifier is what the second remote device wants to forward to the second peer device through itself, or whether the second relay device is acting as the first peer device and the first remote device allocates it to itself, and there is a conflict between the temporary identifier of the second peer device and the temporary identifier of the first peer device.

In step S503, in response to a temporary identifier conflict between the first peer device and the second peer device, a conflict indication is sent to the peer device of the device; the second peer device is a peer device to which the second remote device is connected via the second relay device.

Among them, when the first relay device determines that the temporary identifier of the first counterpart device conflicts with the temporary identifier of the second counterpart device, since the first relay device is the second remote device in the second relay group, the first relay device can directly reallocate a temporary identifier to the second counterpart device. The temporary identifier is different from the temporary identifier of the second counterpart device and the temporary identifier of the second relay device. The temporary identifier is carried in the conflict indication. The second counterpart device parses the conflict indication and obtains the temporary identifier reallocated to it by the second remote device from the conflict indication.

The conflict indication sent by the first relay device to the second remote device carries a temporary identifier allocated to the second remote device.

Of course, the second relay device in the second relay group can also determine by itself whether the temporary identifier of the second counterpart device conflicts with its own temporary identifier. When the second counterpart device receives two reallocated temporary identifiers, it can select one temporary identifier from them. The second relay device in the second relay group does not need to determine whether the temporary identifier of the second counterpart device conflicts with its own temporary identifier. The first relay device can also make the judgment.

In any embodiment of the present disclosure, the first relay device may be the second relay device, and the second relay device may be the first relay device. In this way, the second relay device may perform the functions implemented by the first relay device, and the first relay device may also perform the functions implemented by the second relay device. The present disclosure does not make any limitation hereto.

Through the above technical solution, when the first relay device determines that the temporary identifier of the first peer device is the same as the first temporary identifier of the second peer device, it is determined that there is a temporary identifier conflict. At this time, a conflict indication can be sent to the second peer device, and the second peer device parses the conflict indication to obtain a reallocated temporary identifier. When the second remote device has a reallocated temporary identifier that is different from the fourth temporary identifier, the second relay device can distinguish the temporary identifier of the second peer device from its own temporary identifier based on the different temporary identifiers, thereby avoiding data loss.

FIG. 7 is a flow chart of a temporary identification scheduling method according to an exemplary embodiment. As shown in FIG. 7 , the temporary identification scheduling method is used in a first relay device and includes the following steps.

In step S601, a temporary identifier and an identifier of a first remote device sent by the first remote device are received; and/or, a temporary identifier and an identifier of a first remote device sent by the first remote device are received.

In some embodiments, receiving the temporary identifier and identifier of the first peer device sent by the first remote device may specifically include: receiving the identifier and temporary identifier of the first peer device sent by the first remote device; determining, based on the identifier of the first peer device, that the peer device corresponding to the identifier is the first peer device of the first remote device; and sending the temporary identifier allocated by the first remote device to the first peer device to the first peer device.

Among them, the first remote device, as the party that assigns the temporary identifier to the first peer device, can determine the temporary identifier assigned to the first peer device; and there may be multiple peer devices communicating with the first remote device through the first relay device, so the first remote device needs to determine the object to which the temporary identifier is sent through the identifier of the peer device.

For example, the first remote device has identifiers of multiple peer devices, which can uniquely identify a peer device. When the first remote device determines that a temporary identifier needs to be assigned to the first peer device, the identifier of the first peer device and the temporary identifier assigned to the first peer device can be sent to the first relay device; the first relay device determines that the assignment object of the temporary identifier is the first peer device based on the identifier, so the first relay device sends the temporary identifier to the first peer device corresponding to the identifier.

For example, the opposite devices B and F communicate with the first remote device through the first relay device. When the first remote device determines to reallocate a temporary identifier for B based on the conflict indication, B's identifier and the temporary identifier can be sent to the first relay device. The first relay device determines that the temporary identifier is assigned to B based on the identifier, so the temporary identifier is sent to B corresponding to the identifier.

In some embodiments, receiving a temporary identifier and an identifier of a first remote device sent by a first peer device may specifically include: receiving an identifier and a temporary identifier of the first remote device sent by the first peer device; determining the first remote device as the first peer device based on the identifier of the first remote device; and sending the temporary identifier allocated by the first peer device to the first remote device to the first remote device.

Among them, the first peer device, as the party that assigns the temporary identifier to the first remote identifier, can determine the temporary identifier assigned to the first remote device; and there may be multiple remote devices communicating with the first peer device through the first relay device, so the first peer device needs to determine the object to which the temporary identifier is sent.

For example, the first counterpart device has identifiers of multiple remote devices, which can uniquely identify a remote device. When the first counterpart device determines that a temporary identifier needs to be assigned to the first remote device, the identifier of the first remote device and the temporary identifier assigned to the first remote device can be sent to the first relay device; the first relay device determines that the temporary identifier is assigned to the first remote device based on the identifier, so the first relay device forwards the temporary identifier to the first remote device corresponding to the identifier.

In some embodiments, it is also possible to receive a temporary identifier and an identifier of the first opposite device sent by the first remote device; and receive a temporary identifier and an identifier of the first remote device sent by the first opposite device.

For example, when the first peer device allocates a temporary identifier for the first remote device, it is necessary to send the identifier of the first remote device and the temporary identifier allocated to the first remote device to the first relay device, and the first relay device sends the temporary identifier to the first remote device corresponding to the identifier based on the identifier; and, when the first remote device allocates a temporary identifier for the first peer device, it is necessary to send the identifier of the first peer device and the temporary identifier allocated to the first peer device to the first relay device, and the first relay device sends the temporary identifier to the first peer device corresponding to the identifier based on the identifier.

Among them, the method of determining the corresponding opposite device or remote device based on the identifier can be used for the allocation of temporary identifiers before a conflict occurs in the temporary identifiers, and can also be used for the reallocation of temporary identifiers after a conflict occurs in the temporary identifiers. The present disclosure does not limit the specific application scenarios.

In step S602, in response to a temporary identifier conflict existing among the temporary identifiers of the device, a conflict indication is sent to a peer device of the device.

For example, the step of sending the conflict indication in the embodiment of the present disclosure may refer to the above-mentioned step S102, which will not be described in detail.

Through the above technical solution, after the first relay device receives the temporary identifier and the identifier of the remote device, the temporary identifier can be forwarded to the remote device corresponding to the identifier; after the first relay device receives the temporary identifier and the identifier of the opposite device, the temporary identifier can also be forwarded to the opposite device corresponding to the identifier. This enables the first opposite device to allocate the temporary identifier to the correct first remote device, and the first remote device can also allocate the temporary identifier to the correct first opposite device, avoiding the occurrence of an error in the allocation of the temporary identifier.

FIG8 is a flow chart of a temporary identification scheduling method according to an exemplary embodiment. As shown in FIG8 , the temporary identification scheduling method is used in a first remote device and includes the following steps.

In step S701, the conflict indication sent by the first relay device is forwarded to a device in the sidelink.

Among them, the device in the side link can be a first relay device and/or a first peer device, and the conflict indication carries a temporary identifier that the first relay device recommends the first peer device to assign to the first remote device, and the temporary identifier is different from the temporary identifier of the first remote device.

After determining that the temporary identifier of the first relay device conflicts with the temporary identifier of the first remote device, the first relay device will forward the conflict indication to the first remote device; the first remote device will then forward the conflict indication to the first relay device, which will forward the conflict indication to the first opposite device through the first relay device; the first opposite device will then reallocate a temporary identifier to the first remote device based on the conflict indication; or after determining that the temporary identifier of the first relay device conflicts with the temporary identifier of the first remote device, the first relay device will send the conflict indication directly to the first opposite device.

The conflict indication carries a temporary identifier that the first relay device recommends the first opposite-end device to allocate to the first remote device, and the temporary identifier is different from the temporary identifier of the first remote device.

In step S702, a temporary identification of a device in a sidelink is received.

When the first opposite-end device receives the conflict indication determined by the first relay device or the first remote device, the temporary identifier suggested in the conflict indication may be used to reallocate a temporary identifier to the first remote device.

For example, the first peer device sends the reallocated temporary identifier to the first relay device, and the first relay device forwards the reallocated temporary identifier to the first remote device. After determining its own temporary identifier, the first remote device may also forward its own temporary identifier to other relay devices or other peer devices.

Through the above technical solution, when the first relay device receives a temporary identifier of a device in the side link and there is a temporary identifier conflict, a conflict indication can be sent to the first opposite device to inform the device in the side link that there is a conflict between the temporary identifiers of the first relay device and the first remote device, thereby enabling the first remote device to receive the reallocated temporary identifier returned by the device in the side link to avoid data loss caused by the temporary identifier conflict.

FIG. 9 is a flow chart of a temporary identification scheduling method according to an exemplary embodiment. As shown in FIG. 9 , the temporary identification scheduling method is used in a first remote device and includes the following steps.

In step S801, the conflict indication sent by the first relay device is forwarded to a device in the sidelink.

For example, the step of forwarding the conflict indication in the embodiment of the present disclosure may refer to the above-mentioned step S701, which will not be described in detail.

In step S802, a temporary identifier sent by the first relay device is received, and/or a temporary identifier sent by a first opposite device of the first remote device is received.

The first remote device interacts with the first relay device, so the first remote device can receive the temporary identifier forwarded by the first relay device to the first remote device. The first remote device can be a new identifier recipient, receiving the temporary identifier forwarded by the first peer device to the first remote device through the first relay device.

In some embodiments, the first remote device may receive a temporary identifier sent by the first relay device.

When the first relay device can parse the forwarded content, it indicates that the first relay device can parse the forwarded content and obtain the temporary identifier assigned by the first peer device to the first remote device. Therefore, the first relay device can directly receive the temporary identifier from the first peer device and send the temporary identifier to the first remote device.

In this process, the first remote UE serves as the destination UE, and the first relay device serves as the source UE.

For example, the temporary identifier sent by the first relay device is that when the first relay device receives the identifier and temporary identifier of the first remote device sent by the first counterpart device, the first relay device sends the temporary identifier allocated by the first counterpart device to the first remote device to the first remote device according to the identifier of the first remote device.

In some embodiments, the first remote device may receive a temporary identifier allocated to the first remote device by the first peer device.

When the first relay device can forward data but does not parse the data, it indicates that the first relay device does not perform the function of parsing and forwarding content. At this time, the first relay device plays the function of forwarding data, so the first remote device receives the temporary identifier assigned by the first peer device.

In this process, the first remote device serves as the destination UE, and the first opposite device serves as the source UE.

It is worth noting that the temporary identifier assigned by the first opposite device and received by the first remote device may be a temporary identifier forwarded by the first relay device without performing a function of parsing and forwarding content.

In some embodiments, the first remote device may receive a temporary identifier allocated by the first remote device to the first remote device and a temporary identifier sent by the first relay device.

It is worth noting that, before the first remote device receives the conflict indication, when the first relay device performs the function of parsing and forwarding data, the first relay device can directly obtain the temporary identifier of the first remote device from the first opposite device to determine whether its own temporary identifier conflicts with the first remote device; when the first relay device does not perform the function of parsing and forwarding data, the first remote device receives the temporary identifier forwarded to the first remote device by the first opposite device via the first relay device, and forwards the temporary identifier to the first relay device, and the first relay device determines whether its own temporary identifier conflicts with the first remote device.

Through the above-mentioned technical solution, after forwarding the conflict indication to the device in the side link, the first remote device can receive the temporary identifier reallocated for the first remote device forwarded by the first relay device, and/or receive the temporary identifier reallocated for the first remote device by the first opposite device, so that after the temporary identifier of the first remote device conflicts with that of the first relay device, it can receive a temporary identifier different from the temporary identifier of the first relay device to distinguish it from the temporary identifier of the first relay device.

FIG. 10 is a flow chart of a temporary identification scheduling method shown in an exemplary embodiment. As shown in FIG. 10 , the temporary identification scheduling method is used in a first opposite-end device and includes the following steps.

In step S901, a conflict indication sent by a sidelink device is received.

The first opposite-end device may receive a conflict indication sent by the first remote-end device in the sidelink, or may receive a conflict indication sent by the first relay device in the sidelink.

Wherein, when the first relay device does not perform the function of parsing and forwarding data, the first opposite-end device, as the destination UE, can receive the conflict indication sent by the first remote device, as the source UE.

For example, the first remote device obtains a conflict indication from the first relay device, and the first remote device, as a source UE, forwards the conflict indication to the first opposite device, as a destination UE, through the first relay device.

In the case where the first relay device performs the function of parsing and forwarding data, the first opposite-end device, as the destination UE, can receive the conflict indication sent by the first relay device, as the source UE.

For example, the first remote device may directly obtain the conflict indication from the first relay device.

The first opposite device is the party that allocates the identifier to the first remote device, and the conflict indication carries the temporary identifier that the first relay device recommends the first opposite device to allocate to the first remote device.

In step S902, a temporary identifier is reallocated to the corresponding device according to the conflict indication.

The first opposite-end device may reallocate an identifier to the first remote-end device according to the suggested temporary identifier carried in the conflict indication, or may regenerate a temporary identifier allocated to the first remote-end device by itself.

The first peer device allocates a temporary identifier to the first remote device, and/or receives a temporary identifier allocated by the first remote device to the first peer device.

Through the above technical solution, when the temporary identifiers of the first remote device and the first relay device conflict, the first opposite-end device can receive a conflict indication sent by the side link device, and reallocate a temporary identifier for the first remote device based on the conflict indication, so that the temporary identifier of the first remote device is different from the temporary identifier of the first relay device, and the first relay device can distinguish between different temporary identifiers to forward different temporary identifiers to different devices.

FIG. 11 is a flow chart of a temporary identification scheduling method shown in an exemplary embodiment. As shown in FIG. 11 , the temporary identification scheduling method is used in a first opposite-end device and includes the following steps.

In step S110, the temporary identifier of the first remote device and/or the identifier of the first remote device is sent to a first relay device, and the first remote device communicates with the first opposite device through the first relay device.

In some embodiments, the temporary identifier of the first remote device is sent to the first relay device.

Among them, the first opposite device sends the temporary identifier of the first remote device directly to the first relay device, and/or the first opposite device forwards the temporary identifier of the first remote device to the first remote device, and then forwards it to the first relay device through the first remote device. The method of forwarding the temporary identifier in the embodiment of the present disclosure can refer to the above step S802 and will not be repeated here.

In some embodiments, an identification of the first remote device is sent to the first relay device.

For example, the method for forwarding an identifier in the embodiment of the present disclosure may refer to the above step S802, which will not be described in detail.

In some embodiments, the temporary identifier and the identifier of the first remote device are sent to the first relay device.

For example, the method for forwarding a temporary identifier in the embodiment of the present disclosure may refer to the above step S802, which will not be described in detail.

Fig. 12 is a block diagram of a temporary identifier scheduling device according to an exemplary embodiment. Referring to Fig. 12 , the temporary identifier scheduling device 120 applied to a first relay device includes a first receiving module 121 and a first sending module 122 .

The first receiving module 121 is configured to receive a temporary identification of at least one device in the sidelink;

The first sending module 122 is configured to send a conflict indication to a peer device of the device in response to a temporary identifier conflict between the temporary identifiers of the device.

Optionally, the device includes a first remote device or a first opposite device, and the first sending module 122 includes at least one of the following modules:

A first conflict indication sending module, configured to send a conflict indication to the first opposite-end device in response to a temporary identification conflict between the first relay device and the first remote device;

The second conflict indication sending module is configured to send a conflict indication to the first remote device in response to a temporary identification conflict between the first relay device and the first opposite device; wherein the first opposite device is a opposite device to which the first remote device is connected via the first relay device.

Optionally, the temporary identification scheduling device 120 includes:

The first conflict confirmation module is configured to determine that a temporary identifier conflict exists between the first relay device and the first remote device when the first temporary identifier of the first relay device is the same as the second temporary identifier of the first remote device.

Optionally, the first conflict indication sending module includes:

The third conflict indication sending module is configured to send a first conflict indication to the first opposite device in response to a temporary identifier conflict between the first relay device and the first remote device, wherein the first conflict indication is used to instruct the first opposite device to reallocate a temporary identifier for the first remote device.

Optionally, the first conflict indication sending module includes:

a fourth conflict indication sending module, configured to send the first conflict indication to the first remote device in response to a temporary identifier conflict between the first relay device and the first remote device;

The first conflict indication is used to instruct the first opposite-end device to reallocate a temporary identifier to the first remote-end device.

Optionally, the temporary identification scheduling device 120 includes:

The indication forwarding module is configured to forward the first conflict indication received from the first remote device to the first opposite end device.

Optionally, the first conflict indication includes a temporary identifier suggested for the first remote device.

Optionally, the device includes a second remote device and a second opposite device,

Optionally, the first sending module 122 includes:

The fifth conflict indication sending module is configured to send a conflict indication to the opposite device of the device in response to a temporary identification conflict between the first opposite device and the second opposite device; the second opposite device is the opposite device to which the second remote device is connected via the second relay device.

Optionally, the temporary identification scheduling device 120 includes:

The second conflict confirmation module is configured to determine that a temporary identifier conflict exists between the first peer device and the second peer device when the third temporary identifier of the first peer device is the same as the fourth temporary identifier of the second peer device.

Optionally, the second conflict confirmation module includes:

The temporary identifier reallocation module is configured to send a conflict indication to the second peer device in response to the temporary identifiers of the first peer device and the second peer device being the same, wherein the conflict indication carries the temporary identifier reallocated to the second peer device.

Optionally, the device includes a first remote device or a first opposite device, and the first receiving module 121 includes:

A first identification receiving module is configured to receive a temporary identification and an identification of a first opposite-end device sent by the first remote device; and/or,

The second identification receiving module is configured to receive the temporary identification and the identification of the first remote device sent by the first opposite device.

Optionally, the second identification receiving module includes:

A third identification receiving module is configured to receive the identification and temporary identification of the first remote device sent by the first peer device;

A first remote device confirmation module is configured to determine the first remote device as the first opposite-end device according to the identifier of the first remote device;

The first temporary identifier forwarding module is configured to send the temporary identifier allocated by the first opposite-end device to the first remote device to the first remote device.

Optionally, the first identification receiving module includes:

a fourth identification receiving module, configured to receive an identification and a temporary identification of the first peer device sent by the first remote device;

A first peer device confirmation module, configured to determine the first peer device as the first remote device according to the identifier of the first peer device;

The second temporary identifier forwarding module is configured to send the temporary identifier allocated by the first remote device to the first opposite device to the first opposite device.

Fig. 13 is a block diagram of a temporary identifier scheduling device according to an exemplary embodiment. Referring to Fig. 13 , the temporary identifier scheduling device 220 applied to a first remote device includes a conflict indication forwarding module 221 and a second receiving module 222 .

A conflict indication forwarding module 221, configured to forward the conflict indication sent by the first relay device to a device in the sidelink;

The second receiving module 222 is configured to receive a temporary identifier sent by a device in the sidelink.

Optionally, the second receiving module 222 includes:

The third receiving module is configured to receive a temporary identifier sent by the first relay device and/or receive a temporary identifier sent by a first opposite device of the first remote device.

Optionally, the temporary identifier sent by the first relay device is the temporary identifier allocated by the first counterpart device to the first remote device according to the identifier of the first remote device when the first relay device receives the identifier and the temporary identifier of the first remote device, and sends it to the first remote device.

Optionally, the conflict indication forwarding module 221 includes:

The first conflict indication forwarding module is configured to send the conflict indication to a first opposite-end device of the first remote device.

Optionally, the first conflict indication forwarding module includes:

The second conflict indication forwarding module is configured to send the conflict indication to the first opposite device in response to the conflict indication sent by the first relay device, wherein the conflict indication is used to instruct the first opposite device to reallocate a temporary identifier for the first remote device.

Optionally, the conflict indication includes a temporary identifier suggested for the first remote device.

Fig. 14 is a block diagram of a temporary identifier scheduling device according to an exemplary embodiment. Referring to Fig. 14 , the temporary identifier scheduling device 330 applied to a first peer device includes a conflict indication forwarding module 331 and a second receiving module 332 .

The conflict indication receiving module 331 is configured to receive a conflict indication sent by a sidelink device;

The temporary identifier allocation module 332 is configured to reallocate a temporary identifier to the corresponding device according to the conflict indication.

Optionally, the device includes a first remote device, and the temporary identifier allocation module 332 includes:

According to the conflict indication, the reallocated temporary identifier is sent to the first remote device.

Optionally, the temporary identification scheduling device 330 includes:

The identifier forwarding module is configured to send the temporary identifier of the first remote device and/or the identifier of the first remote device to a first relay device, and the first remote device communicates with the first opposite device through the first relay device.

Optionally, the temporary identification scheduling device 330 includes:

The temporary identifier transceiver module is configured to allocate a temporary identifier to the first remote device and/or receive a temporary identifier allocated by the first remote device to the first opposite device.

Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

The present disclosure also provides a computer-readable storage medium having computer program instructions stored thereon, and when the program instructions are executed by a processor, the steps of the temporary identification scheduling method provided by the present disclosure are implemented.

Fig. 15 is a block diagram of a device according to an exemplary embodiment, and the device can be any one of a relay device, a remote device and a peer device. For example, the device 800 can be a mobile phone, a computer, a digital broadcast terminal, a message transceiver device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

15 , the apparatus 800 may include one or more of the following components: a processing component 802 , a memory 804 , a power component 806 , a multimedia component 808 , an audio component 810 , an input/output interface 812 , a sensor component 814 , and a communication component 816 .

The processing component 802 generally controls the overall operation of the device 800, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to complete all or part of the steps of the above-mentioned method. In addition, the processing component 802 may include one or more modules to facilitate the interaction between the processing component 802 and other components. For example, the processing component 802 may include a multimedia module to facilitate the interaction between the multimedia component 808 and the processing component 802.

The memory 804 is configured to store various types of data to support operations on the device 800. Examples of such data include instructions for any application or method operating on the device 800, contact data, phone book data, messages, pictures, videos, etc. The memory 804 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

The power supply component 806 provides power to the various components of the device 800. The power supply component 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 800.

The multimedia component 808 includes a screen that provides an output interface between the device 800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front camera and/or a rear camera. When the device 800 is in an operating mode, such as a shooting mode or a video mode, the front camera and/or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

The audio component 810 is configured to output and/or input audio signals. For example, the audio component 810 includes a microphone (MIC), and when the device 800 is in an operating mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 804 or sent via the communication component 816. In some embodiments, the audio component 810 also includes a speaker for outputting audio signals.

The input/output interface 812 provides an interface between the processing component 802 and the peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: a home button, a volume button, a start button, and a lock button.

The sensor assembly 814 includes one or more sensors for providing various aspects of the status assessment of the device 800. For example, the sensor assembly 814 can detect the open/closed state of the device 800, the relative positioning of components, such as the display and keypad of the device 800, and the sensor assembly 814 can also detect the position change of the device 800 or a component of the device 800, the presence or absence of user contact with the device 800, the orientation or acceleration/deceleration of the device 800, and the temperature change of the device 800. The sensor assembly 814 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 814 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 may also include an accelerometer, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

The communication component 816 is configured to facilitate wired or wireless communication between the device 800 and other devices. The device 800 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 816 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 816 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

In an exemplary embodiment, the apparatus 800 may be implemented by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic components to perform the above method.

In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 804 including instructions, and the instructions can be executed by the processor 820 of the device 800 to perform the above method. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

In addition to being an independent electronic device, the above-mentioned device can also be a part of an independent electronic device. For example, in one embodiment, the device can be an integrated circuit (IC) or a chip, wherein the integrated circuit can be an IC or a collection of multiple ICs; the chip can include but is not limited to the following types: GPU (Graphics Processing Unit), CPU (Central Processing Unit), FPGA (Field Programmable Gate Array), DSP (Digital Signal Processor), ASIC (Application Specific Integrated Circuit), SOC (System on Chip, SoC), etc. The above-mentioned integrated circuit or chip can be used to execute executable instructions (or codes) to implement the above-mentioned temporary identification scheduling method. The executable instructions can be stored in the integrated circuit or chip, or can be obtained from other devices or equipment, for example, the integrated circuit or chip includes a processor, a memory, and an interface for communicating with other devices. The executable instruction can be stored in the memory, and when the executable instruction is executed by the processor, the above-mentioned temporary identification scheduling method is implemented; alternatively, the integrated circuit or chip can receive the executable instruction through the interface and transmit it to the processor for execution, so as to implement the above-mentioned temporary identification scheduling method.

In another exemplary embodiment, a computer program product is further provided. The computer program product includes a computer program that can be executed by a programmable device. The computer program has a code portion for executing the temporary identification scheduling method when executed by the programmable device.

The embodiment of the present disclosure also provides a communication system, which includes a remote UE, a remote UE's opposite UE and a relay UE, wherein the remote UE and the opposite UE are each other's remote UEs. The remote UE and the relay UE can execute the above temporary identification scheduling method.

Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the present disclosure. This application is intended to cover any variations, uses or adaptations of the present disclosure, which follow the general principles of the present disclosure and include common knowledge or customary technical means in the art that are not disclosed in the present disclosure. The specification and examples are to be regarded as exemplary only, and the true scope and spirit of the present disclosure are indicated by the following claims.

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

Claims

A temporary identification scheduling method, wherein the method is applied to a first relay device, comprising:

receiving a temporary identification of at least one device in a sidelink;

In response to a temporary identifier conflict existing in the temporary identifiers of the device, a conflict indication is sent to a peer device of the device.
The method according to claim 1, wherein the device comprises a first remote device or a first opposite device, and the sending of a conflict indication to the opposite device of the device in response to a temporary identifier conflict between the temporary identifiers of the device comprises at least one of the following:

In response to a temporary identifier conflict between the first relay device and the first remote device, sending a conflict indication to the first opposite device;

In response to a temporary identifier conflict between the first relay device and the first opposite device, a conflict indication is sent to the first remote device; wherein the first opposite device is a opposite device to which the first remote device is connected via the first relay device.
The method according to claim 2, wherein the method further comprises:

When the first temporary identifier of the first relay device is the same as the second temporary identifier of the first remote device, it is determined that there is a temporary identifier conflict between the first relay device and the first remote device.
The method according to claim 2, wherein

In response to a temporary identifier conflict between the first relay device and the first remote device, a first conflict indication is sent to the first opposite device, where the first conflict indication is used to instruct the first opposite device to reallocate a temporary identifier to the first remote device.
The method according to claim 2, wherein

In response to a temporary identifier conflict between the first relay device and the first remote device, sending the first conflict indication to the first remote device;

The first conflict indication is used to instruct the first opposite-end device to reallocate a temporary identifier to the first remote-end device.
The method according to claim 5, wherein the method further comprises:

The first conflict indication received from the first remote device is forwarded to the first opposite device.
The method according to any one of claims 4 to 6, wherein the first conflict indication includes a temporary identifier suggested for the first remote device.
The method according to claim 1, wherein the device comprises a second remote device and a second opposite device, and the sending of a conflict indication to the opposite device of the device in response to a temporary identifier conflict between the temporary identifiers of the device comprises:

In response to a temporary identifier conflict between the first peer device and the second peer device, a conflict indication is sent to the peer device of the device; the second peer device is a peer device to which the second remote device is connected via the second relay device.
The method according to claim 8, wherein the method further comprises:

When the third temporary identifier of the first peer device is the same as the fourth temporary identifier of the second peer device, it is determined that a temporary identifier conflict exists between the first peer device and the second peer device.
The method according to claim 8, wherein, in response to a temporary identifier conflict existing in the temporary identifier of the device, sending a conflict indication to the opposite device of the device comprises:

In response to the temporary identifiers of the first peer device and the second peer device being the same, a conflict indication is sent to the second peer device, where the conflict indication carries the temporary identifier reallocated to the second peer device.
The method according to claim 1, wherein the device comprises a first remote device or a first opposite device, and the temporary identification of at least one device in the receiving side link comprises:

receiving a temporary identifier and an identifier of a first peer device sent by the first remote device; and/or

Receive the temporary identifier and the identifier of the first remote device sent by the first peer device.
The method according to claim 11, wherein the receiving the temporary identifier and the identifier of the first remote device sent by the first peer device comprises:

receiving an identifier and a temporary identifier of the first remote device sent by the first peer device;

Determine, according to the identifier of the first remote device, a first remote device as the first peer device;

The temporary identifier allocated by the first opposite-end device to the first remote device is sent to the first remote device.
The method according to claim 11, wherein the receiving the temporary identifier of the first peer device sent by the first remote device comprises:

receiving an identifier and a temporary identifier of the first peer device sent by the first remote device;

Determining, according to the identifier of the first peer device, a first peer device as the first remote device;

The temporary identifier allocated by the first remote device to the first peer device is sent to the first peer device.
A temporary identification scheduling method, wherein the method is applied to a first remote device, comprising:

forwarding the conflict indication sent by the first relay device to a device in the sidelink;

Receive the temporary identifier sent by the device in the side link.
The method according to claim 14, wherein the receiving side temporary identifier sent by the device in the link comprises:

Receive a temporary identifier sent by the first relay device, and/or receive a temporary identifier sent by a first opposite device of the first remote device.
The method according to claim 15, wherein the temporary identifier sent by the first relay device is that when the first relay device receives the identifier and the temporary identifier of the first remote device, the first relay device sends the temporary identifier allocated by the first counterpart device to the first remote device to the first remote device according to the identifier of the first remote device.
The method according to claim 14, wherein the forwarding of the conflict indication sent by the first relay device to the device in the sidelink comprises:

The conflict indication is sent to a first opposite end device of the first remote end device.
The method according to claim 17, wherein the sending the conflict indication to the first peer device of the first remote device comprises:

In response to the conflict indication sent by the first relay device, the conflict indication is sent to the first opposite-end device, where the conflict indication is used to instruct the first opposite-end device to reallocate a temporary identifier to the first remote device.
The method according to claim 17 or 18, wherein the conflict indication includes a temporary identifier proposed for the first remote device.
A temporary identification scheduling method, wherein the method is applied to a first peer device, comprising:

receiving a conflict indication sent by a device on a side link;

A temporary identifier is reallocated to the corresponding device according to the conflict indication.
The method according to claim 20, wherein the device comprises a first remote device, and the reallocating a temporary identifier to the corresponding device according to the conflict indication comprises:

According to the conflict indication, the reallocated temporary identifier is sent to the first remote device.
The method according to claim 20, wherein the method further comprises:

The temporary identifier of the first remote device and/or the identifier of the first remote device is sent to a first relay device, and the first remote device communicates with the first opposite device through the first relay device.
The method according to claim 20, wherein the method further comprises:

Allocate a temporary identifier for the first remote device, and/or receive a temporary identifier allocated by the first remote device to the first opposite device.
A temporary identification scheduling device, which is applied to a first relay device, comprising:

A first receiving module is configured to receive a temporary identification of at least one device in a sidelink;

The first sending module is configured to send a conflict indication to a peer device of the device in response to a temporary identifier conflict existing in the temporary identifiers of the device.
A temporary identification scheduling device, which is applied to a first remote device, comprises:

a conflict indication forwarding module, configured to forward the conflict indication sent by the first relay device to a device in the sidelink;

The second receiving module is configured to receive a temporary identifier sent by a device in the side link.
A temporary identification scheduling device, which is applied to a first opposite-end device, comprises:

A conflict indication receiving module, configured to receive a conflict indication sent by a sidelink device;

The temporary identification allocation module is configured to reallocate a temporary identification to the corresponding device according to the conflict indication.
A relay device, comprising:

processor;

a memory for storing processor-executable instructions;

Wherein, the processor is configured to implement the steps of the method according to any one of claims 1 to 13 when executing the executable instructions.
A remote device, comprising:

processor;

a memory for storing processor-executable instructions;

Wherein, the processor is configured to implement the steps of the method described in any one of claims 14 to 19 when executing the executable instructions.
A peer device, comprising:

processor;

a memory for storing processor-executable instructions;

Wherein, the processor is configured to implement the steps of the method described in any one of claims 20 to 23 when executing the executable instructions.
A computer-readable storage medium having computer program instructions stored thereon, wherein when the program instructions are executed by a processor, the steps of the method described in any one of claims 1 to 13 are implemented, or the steps of the method described in any one of claims 14 to 19 are implemented, or the steps of the method described in any one of claims 20 to 23 are implemented.
A chip, comprising a processor and an interface; the processor is used to read instructions to execute the steps of the method described in any one of claims 1 to 13, or to execute the steps of the method described in any one of claims 14 to 19, or to execute the steps of the method described in any one of claims 20 to 23.