Temporary identifier scheduling methods, devices, equipment, storage media and chips

Abstract

A temporary identifier scheduling method, apparatus, device, storage medium, and chip are disclosed, relating to the field of communication technology and applied to a first relay device. The method includes: a temporary identifier for at least one device in a receiving-side crosslink; and, in response to a temporary identifier conflict, sending a conflict indication to a peer device. Using the temporary identifier scheduling method proposed in this disclosure, a conflict indication can be sent to the peer device to instruct it to reallocate a temporary identifier for the device, thus avoiding data loss caused by temporary identifier conflicts.

Description

Technical Field

[0001] This disclosure relates to the field of communication technology, and in particular to a temporary identifier scheduling method, apparatus, device, storage medium and chip. Background Technology

[0002] To support direct communication between UEs (user equipment), a sidelink communication method was introduced. UEs can communicate with each other via the PC-5 interface (direct communication interface). When a UE needs to communicate with a base station but is outside the base station's network coverage, it can use another UE within the base station's network coverage as a relay to achieve communication with the base station. The UE not connected to the base station is called a remote UE, and the UE providing relay functionality is called a relay UE. Remote UEs and relay UEs can communicate via unicast, multicast, and broadcast through the sidelink. When a remote UE sends data, it needs to specify the source and destination addresses. The relay UE forwards the data based on the source and destination addresses, and the remote UE receives the data based on either the source or destination address.

[0003] In related technologies, temporary identifiers can be assigned to remote UEs and peer UEs in a relay group to identify them. A relay group includes remote UEs, relay UEs, and peer UEs. A UE can act as a relay UE in one relay group and as a remote UE in another relay group. When a UE receives a temporary identifier sent by a peer UE as a relay UE in a relay group, and the UE receives the same temporary identifier sent by a relay 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 one relay group or sent by a relay UE in another relay group to the UE itself. This can lead to misidentification and data loss. Summary of the Invention

[0004] To overcome the problems existing in related technologies, this disclosure provides a temporary identifier scheduling method, apparatus, device, storage medium, and chip.

[0005] According to a first aspect of the present disclosure, a temporary identifier scheduling method is provided, applied to a first relay device, comprising:

[0006] Temporary identifier of at least one device in the receiving-side crosslink;

[0007] In response to a temporary identifier conflict with the device, a conflict indication is sent to the peer device of the device.

[0008] According to a second aspect of the present disclosure, a temporary identifier scheduling method is provided, applied to a first remote device, comprising:

[0009] Forward the conflict indication sent by the first relay device to the device in the side link;

[0010] Temporary identifier of the device in the receiving side crosslink.

[0011] According to a third aspect of the present disclosure, a temporary identifier scheduling method is provided, applied to a first peer device, comprising:

[0012] The collision indication sent by the receiving side crosslink device;

[0013] The corresponding temporary identifier is reassigned to the device based on the conflict indication.

[0014] According to a fourth aspect of the present disclosure, a temporary identifier scheduling device is provided, applied to a first relay device, comprising:

[0015] The first receiving module is configured as a temporary identifier for at least one device in the receiving-side crosslink;

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

[0017] According to a fifth aspect of the present disclosure, a temporary identifier scheduling device is provided, applied to a first remote device, comprising:

[0018] The conflict indication forwarding module is configured to forward the conflict indication sent by the first relay device to the device in the side link;

[0019] The second receiving module is configured to receive temporary identifiers sent by devices in the crosslink.

[0020] According to a sixth aspect of the present disclosure, a temporary identifier scheduling device is provided, applied to a first peer device, comprising:

[0021] The collision indication receiving module is configured to receive collision indications sent by devices on the side link;

[0022] The temporary identifier allocation module is configured to reallocate a temporary identifier to the corresponding device based on the conflict indication.

[0023] According to a seventh aspect of the present disclosure, a relay device is provided, comprising:

[0024] processor;

[0025] Memory used to store processor-executable instructions;

[0026] The processor is configured to implement the temporary identifier scheduling method provided in the first aspect of the present disclosure when executing the executable instructions.

[0027] According to an eighth aspect of the present disclosure, a remote device is provided, comprising:

[0028] processor;

[0029] Memory used to store processor-executable instructions;

[0030] The processor is configured to implement the temporary identifier scheduling method provided in the second aspect of the present disclosure when executing the executable instructions.

[0031] According to a ninth aspect of the present disclosure, a peer device is provided, comprising:

[0032] processor;

[0033] Memory used to store processor-executable instructions;

[0034] The processor is configured to implement the temporary identifier scheduling method provided in the third aspect of the present disclosure when executing the executable instructions.

[0035] According to a tenth aspect of the present disclosure, a computer-readable storage medium is provided, having stored thereon computer program instructions that, when executed by a processor, implement the steps of the temporary identifier scheduling method provided in the first aspect of the present disclosure, or implement the steps of the temporary identifier scheduling method provided in the second aspect of the present disclosure, or implement the steps of the temporary identifier scheduling method provided in the third aspect of the present disclosure.

[0036] According to an eleventh aspect of the present disclosure, a chip is provided, including a processor and an interface; the processor is configured to read instructions to execute the steps of the temporary identifier scheduling method provided in the first aspect of the present disclosure, or to execute the steps of the temporary identifier scheduling method provided in the second aspect of the present disclosure, or to execute the steps of the temporary identifier scheduling method provided in the third aspect of the present disclosure.

[0037] The technical solutions provided by the embodiments of this disclosure may include the following beneficial effects:

[0038] With the above technical solution, when the first relay device receives a temporary identifier conflict from at least one device in the side link, it can send a conflict indication to the peer device of that device, instructing the peer device to reallocate a temporary identifier for that device according to the conflict indication, so as to avoid data loss caused by temporary identifier conflict.

[0039] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

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

[0041] Figure 1 This is a flowchart illustrating a temporary identifier scheduling method according to an exemplary embodiment.

[0042] Figure 2 This is a schematic diagram illustrating a first relay group and a second relay group according to an exemplary embodiment.

[0043] Figure 3 This is a flowchart illustrating a temporary identifier scheduling method according to an exemplary embodiment.

[0044] Figure 4 This is a flowchart illustrating a temporary identifier scheduling method according to an exemplary embodiment.

[0045] Figure 5 This is a flowchart illustrating a temporary identifier scheduling method according to an exemplary embodiment.

[0046] Figure 6 This is a flowchart illustrating a temporary identifier scheduling method according to an exemplary embodiment.

[0047] Figure 7 This is a flowchart illustrating a temporary identifier scheduling method according to an exemplary embodiment.

[0048] Figure 8 This is a flowchart illustrating a temporary identifier scheduling method according to an exemplary embodiment.

[0049] Figure 9 This is a flowchart illustrating a temporary identifier scheduling method according to an exemplary embodiment.

[0050] Figure 10 This is a flowchart illustrating a temporary identifier scheduling method according to an exemplary embodiment.

[0051] Figure 11 This is a flowchart illustrating a temporary identifier scheduling method according to an exemplary embodiment.

[0052] Figure 12 This is a block diagram illustrating a temporary identifier scheduling device according to an exemplary embodiment.

[0053] Figure 13This is a block diagram illustrating a temporary identifier scheduling device according to an exemplary embodiment.

[0054] Figure 14 This is a block diagram illustrating a temporary identifier scheduling device according to an exemplary embodiment.

[0055] Figure 15 This is a block diagram illustrating a device according to an exemplary embodiment. Detailed Implementation

[0056] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this disclosure. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this disclosure as detailed in the appended claims.

[0057] It is understood that in this disclosure, "multiple" refers to two or more, and other quantifiers are similar. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. The character " / " generally indicates that the preceding and following related objects 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 otherwise.

[0058] It is further understood that the terms "first," "second," etc., are used to describe various types of information, but this information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another and do not indicate a specific order or degree of importance. In fact, the expressions "first," "second," etc., are completely interchangeable. For example, without departing from the scope of this disclosure, a first remote device may be referred to as a first peer device, a second remote device may be referred to as a second peer device, and a first relay device may be referred to as a second relay device. Similarly, a first peer device may also be referred to as a first remote device, a second peer device may also be referred to as a first peer device, and a second relay device may also be referred to as a first relay device.

[0059] It is further understood that although operations are described in a specific order in the accompanying drawings in the embodiments of this disclosure, this should not be construed as requiring these operations to be performed in the specific order or serial order shown, or requiring all of the shown operations to be performed to obtain the desired result. In certain environments, multitasking and parallel processing may be advantageous.

[0060] It should be noted that all actions involving the acquisition of signals, information, or data in this application are carried out in compliance with the relevant data protection laws and policies of the country where the application is located, and with the authorization granted by the owner of the relevant device.

[0061] Figure 1 This is a flowchart illustrating a temporary identifier scheduling method according to an exemplary embodiment, such as... Figure 1 As shown, the temporary identifier scheduling method is used in the first relay device and includes the following steps.

[0062] In step S101, a temporary identifier of at least one device in the receiving side link is obtained.

[0063] 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 and includes a Physical Sidelink Control Channel (PSCCH) and a Physical Sidelink Shared Channel (PSSCH). The sending UE transmits Sidelink Control Information (SCI) on the PSCCH channel and a second-stage SCI on the PSSCH channel. The SCI carries the resource location of the transmitted data, the source identifier of the sending UE, and the target identifier of the receiving UE.

[0064] The transmitting 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 this disclosure, a UE can communicate with the base station without directly connecting to it, but through the relay of another UE. The UE not connected to the base station is called a remote UE, and the UE providing relay functionality is called a relay UE. This architecture is called U2N (UE to NW) relay. The devices in the sidelink include remote UEs, relay UEs, and peer UEs. The peer UE is the UE that communicates with the remote UE through the relay UE.

[0065] The relay UE, remote UE, and peer UE can be mobile phones, tablets, laptops, computers with wireless transceiver capabilities, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminals in industrial control, smart grids, transportation safety, smart cities, smart homes, etc. This disclosure does not limit the application scenario. UEs can sometimes also be referred to as terminal devices, terminals, access terminals, UE units, UE stations, mobile devices, mobile stations, mobile stations, mobile clients, etc. For ease of description, this disclosure may refer to the first relay UE as the first relay device, the first remote UE as the first remote device, the first peer UE as the first peer device, the second relay UE as the second relay device, the second remote UE as the second remote device, and the second peer device as the second peer device.

[0066] Sidelinks can be D2D (Device to Device) links, such as communication links between mobile phones or between mobile phones and wearable devices. In the Internet of Vehicles (IoV), sidelinks can also be communication links between vehicles (V2V), between vehicles (V2P), between vehicles (V2I), or between vehicles and any device (V2X).

[0067] Sidelink communication supports three communication modes: unicast, multicast, and broadcast. Unicast refers to a sending UE transmitting information to a receiving UE, where each receiving UE corresponds to a destination identifier. Multicast refers to a sending UE transmitting information to multiple receiving UEs, where each group of receiving UEs corresponds to a destination identifier. Broadcast refers to a sending UE transmitting information to all receiving UEs within its network coverage area, where all receiving UEs within the sending UE's network coverage area correspond to a destination identifier.

[0068] To support direct communication between UEs, this embodiment allows UEs to establish data communication via 5G (Fifth Generation Mobile Communication System) and 4G (Fifth Generation Mobile Communication System) technologies. Based on sidelink communication, UEs can also communicate directly via the PC-5 interface. In this embodiment, UEs can communicate directly with other UEs using sidelink communication based on various network standards. It should be noted that these various network standards may include 4G, 5G, or evolutions of 4G and 5G.

[0069] In this disclosure, multiple relay groups can exist in the network, each relay group including a remote device, a relay device, and a peer device. For example, please refer to [link to example]. Figure 2 As shown, the first relay device in the first relay group can be used as a communication link between the first peer device and the first remote device, and the second relay device in the second relay group can be used as a communication link between the second peer device and the second remote device.

[0070] When the peer device assigns a temporary identifier to the remote device, it needs to be forwarded by the relay device. When the remote device assigns a temporary identifier to the peer device, it also needs to be forwarded by the relay device. Therefore, the relay device can receive the temporary identifiers assigned to each other by the peer device and the remote device in the side link.

[0071] Specifically, when 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; when 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. For details, please refer to [link to relevant documentation]. Figure 2 As shown, 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.

[0072] Temporary identifiers are used to save signaling. For example, when a remote device sends data to a peer device, it needs to specify the source address of the remote device and the destination address of the peer device. Only then can the relay device forward the data based on the source and destination addresses, and the peer device, acting as the receiving device, can receive the data based on the source address. In this process, the signaling strings corresponding to the source and destination addresses are quite long, causing the remote device and relay device to use more network resources to achieve data transmission, wasting signaling and resulting in network resource occupation.

[0073] To save signaling, remote devices can carry a temporary identifier assigned to the peer device in the data when sending data to the peer device, such as 1. The temporary identifier string is short, which saves signaling. Therefore, remote devices and relay devices can use less network resources to achieve data transmission, thus freeing up some network resources.

[0074] In step S102, in response to a temporary identifier conflict in the temporary identifier of the device, a conflict indication is sent to the peer device of the device.

[0075] In this system, communication between devices is achieved through relay devices. For example, if a device is a peer device, its peer device can also be a remote device; conversely, if a device is a remote device, its peer device can also be a peer device. That is, two devices connected via relay devices are both peer and remote devices. Peer and remote devices can assign temporary identifiers to each other. Therefore, when a device's temporary identifiers conflict, a conflict indication can be sent to the peer device, allowing it to reassign a temporary identifier. The relay device either sends the conflict indication to the peer device or forwards it to the peer device via the remote device.

[0076] While the mutual allocation of temporary identifiers between peer and remote devices can save signaling and free up some network resources, temporary identifier conflicts may occur, causing relay devices to be unable to forward data correctly.

[0077] For example, please refer to Figure 2As shown, C, acting as the first relay device, can forward the temporary identifier assigned by the first peer device B to the first remote device D. C, acting as the second remote device, can also receive the temporary identifier returned by the second peer device A to itself via the second relay device B. When the temporary identifier received by C as the first relay device from the first peer device B is the same as the temporary identifier assigned to C by the second peer device A, C is unsure whether this temporary identifier was assigned to it by the second peer device A via the second relay device B, or whether the first peer device B needs to forward it to the first remote device D through C. In other words, C does not know whether it is acting as a relay device or is the remote device among the two connected devices via a relay device; that is, C does not know whether the temporary identifier was assigned to it or needs to be sent to other devices through it. Therefore, there is a possibility of misidentification, which could lead to data loss.

[0078] To avoid data loss, this disclosure proposes that if a relay device receives a temporary identifier from another device and there is a temporary identifier conflict, it will send a conflict indication to the other end device.

[0079] For example, when the first relay device determines that the temporary identifier assigned to the first remote device by the first peer 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 at this time, a conflict indication can be sent to the first peer device.

[0080] Temporary identifier conflict refers to a situation where a relay device, based on two temporary identifiers it receives, is unable to distinguish which device corresponds to which temporary identifier.

[0081] The conflict indication carries information about two conflicting temporary identifiers, which is used to instruct the peer device of the device to reassign a temporary identifier to the device according to 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.

[0082] The reallocation in any embodiment of this disclosure may include: determining that a temporary conflict exists before the device has received a temporary identifier assigned by the peer device, and the peer device reallocating a temporary identifier for the device.

[0083] 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 relay device's own temporary identifier. 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 can reassign a temporary identifier to the remote device, and what the remote device receives is the reassigned temporary identifier.

[0084] With the above technical solution, when the first relay device receives a temporary identifier conflict from at least one device in the side link, it can send a conflict indication to the peer device of that device, instructing the peer device to reallocate a temporary identifier for that device according to the conflict indication, so as to avoid data loss caused by temporary identifier conflict.

[0085] Figure 3 This is a flowchart illustrating a temporary identifier scheduling method in an exemplary embodiment, such as... Figure 3 As shown, the temporary identifier scheduling method is used in the first relay device and includes the following steps.

[0086] In step S201, a temporary identifier of at least one device in the receiving side link is obtained.

[0087] For example, the method for receiving a temporary identifier of a device in the side-link in the embodiments of this disclosure can refer to step S101 above, and will not be repeated here. At least one device includes a first remote device or a first peer device, and the step of sending a conflict indication to the peer device of the device in response to a temporary identifier conflict of the temporary identifier of the device includes at least one of the steps in S202.

[0088] In step S202, in response to a temporary identifier conflict between the first relay device and the first remote device, a conflict indication is sent to the first peer device; in response to a temporary identifier conflict between the first relay device and the first peer device, a conflict indication is sent to the first remote device; wherein, the first peer device is the peer device that the first remote device connects to through the first relay device.

[0089] In the event of a temporary identifier conflict between the first relay device and the first remote device, the first relay device directly forwards the conflict indication to the first peer device or forwards the conflict indication to the first peer device through the first remote device; in the event of a temporary identifier conflict between the first peer 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 peer device.

[0090] For example, if the first relay device has the ability to parse and process forwarded content, it can directly receive the temporary identifier allocated by the first peer device to the first remote device, generate a first conflict indication if it determines that the temporary identifier conflicts with its own temporary identifier, and then send the first conflict indication directly to the first peer device. The first peer device reallocates a temporary identifier for the first remote device according to the first conflict indication, and the reallocated temporary identifier is then forwarded to the first remote device through the first relay device so that the first remote device can use the reallocated temporary identifier.

[0091] If the first relay device does not perform the function of parsing and processing the forwarded content, it cannot determine the content of the forwarded data. In this case, the first relay device can forward the temporary identifier allocated by the first peer device to the first remote device to the first remote device, and then receive the temporary identifier determined by the first remote device. If it is determined that the temporary identifier sent by the first remote device conflicts with its own temporary identifier, a first conflict indication is generated. The first conflict indication is then 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, which forwards it to the first peer device.

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

[0093] For example, please refer to Figure 2 As shown, since the remote device assigns a temporary identifier to the peer device, and the peer 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 by the second peer device received by the first relay device is the temporary identifier of the first relay device itself; the temporary identifier received by the first relay device from the first peer 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 belongs to itself or the first remote device.

[0094] At this time, the first relay device may respond to the temporary identifier conflict between the first relay device and the first remote device by sending a conflict indication to the first peer device, instructing the first peer device to reassign a temporary identifier to the first remote device that is different from the temporary identifier of the first remote device.

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

[0096] For example, please refer to Figure 2As shown, 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 temporary identifier of the first peer device. If the two temporary identifiers conflict, the first relay device cannot distinguish whether the temporary identifier belongs to itself or the first peer device.

[0097] At this time, the first relay device may respond to the temporary identifier conflict between the first relay device and the first peer device by sending a conflict indication to the first remote device, instructing the first remote device to reassign a temporary identifier to the first peer device that is different from the temporary identifier of the first peer device.

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

[0099] For example, please refer to Figure 2 As shown, when the temporary identifiers of the first relay device, the temporary identifier of the first peer device, and the temporary identifier of the first remote device conflict, it indicates that the first relay device cannot distinguish whether the temporary identifier belongs to itself, the first remote device, or the first peer device.

[0100] At this time, in response to the temporary identifier conflict between the first relay device and the first remote device, the first relay device sends a conflict indication to the first peer device, instructing the first peer device to reassign a temporary identifier different from the temporary identifier of the first remote device, so as to distinguish it from the temporary identifier of the first relay device itself; and in response to the temporary identifier conflict between the first relay device and the first peer device, the first relay device sends a conflict indication to the first remote device, instructing the first remote device to reassign a temporary identifier different from the temporary identifier of the first peer device, so as to distinguish it from the temporary identifier of the first relay device itself.

[0101] In cases where the temporary identifiers of the first relay device and the first peer device conflict, and the temporary identifiers of the first relay device and the first remote device conflict, the temporary identifier reassigned by the first peer device to the first remote device is different from the temporary identifier reassigned by the first remote device to the first peer device.

[0102] Through the above technical solution, when the first relay device receives a temporary identifier that conflicts with the temporary identifier of the first peer device, it can send a conflict indication to the first remote device to inform the first remote device that there is a conflict between the temporary identifiers of the first peer device and the first relay device, and instruct the first remote device to reassign a temporary identifier to the first peer device, so as to avoid the first relay device being unable to distinguish between the temporary identifier of the first peer device and its own temporary identifier; when the first relay device receives a temporary identifier that is the same as the temporary identifier of the first remote device, it can send a conflict indication to the first peer device to inform the first peer device that there is a conflict between the temporary identifiers of the first remote device and the first relay device, and instruct the first peer device to reassign a temporary identifier to the first remote device, so as to avoid the first relay device being unable to distinguish between the temporary identifier of the first remote device and its own temporary identifier.

[0103] Figure 4 This is a flowchart illustrating a temporary identifier scheduling method in an exemplary embodiment, such as... Figure 4 As shown, the temporary identifier scheduling method is used in the first relay device and includes the following steps.

[0104] In step S301, a temporary identifier of at least one device in the receiving side link is obtained.

[0105] For example, the method for receiving the temporary identifier of a device in the receiving side link in the embodiments of this disclosure can refer to step S101 above, and will not be repeated here.

[0106] In step S302, if 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.

[0107] In this embodiment, the first relay device, within the first relay group, forwards the second temporary identifier assigned by the first peer device to the first remote device. When the first relay device acts as the second remote device in the second relay group, it receives the first temporary identifier assigned by the second peer device. In any embodiment of this 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 may have the same identifiers B and C.

[0108] In the case where 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 belong to itself or need to be forwarded to the first remote device, so there will be a temporary identifier conflict.

[0109] 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 peer device. The first conflict indication is used to instruct the first peer device to reassign a temporary identifier to the first remote device.

[0110] When the first relay device determines that the first temporary identifier and the second temporary identifier conflict, it can generate a first conflict indication and forward the first conflict indication directly to the first peer device.

[0111] For example, if the first relay device has the ability to parse and process forwarded content, it can send the first conflict indication 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. This 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 can use the reallocated temporary identifier.

[0112] The first conflict indication may carry a temporary identifier suggested by the first relay device for the first remote device. The first peer device may use the suggested temporary identifier to reassign the first remote device. The suggested temporary identifier is different from the first temporary identifier and the second temporary identifier. Of course, the first peer device may also choose not to use the suggested temporary identifier, but instead generate a new temporary identifier that is different from the first temporary identifier and the second temporary identifier to reassign the first remote device.

[0113] In any embodiment of this disclosure, the first peer device can be the first remote device, and the first remote device can be the first peer device. Therefore, the above steps can be converted into the first remote device assigning a temporary identifier to the first peer device. The specific steps are similar to the above steps and will not be repeated here.

[0114] With the above technical solution, when the first relay device receives a second temporary identifier from the first remote device that is the same as the first temporary identifier of the first relay device, it determines that there is a temporary identifier conflict. At this time, it can send a first conflict indication to the first peer device to instruct the first peer device to reallocate a temporary identifier for the first remote device according to 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 its own temporary identifier based on the different temporary identifiers, thus avoiding data loss.

[0115] Figure 5 This is a flowchart illustrating a temporary identifier scheduling method in an exemplary embodiment, such as... Figure 5 As shown, the temporary identifier scheduling method is used in the first relay device and includes the following steps.

[0116] In step S401, a temporary identifier of at least one device in the receiving side link is obtained.

[0117] For example, the method for receiving the temporary identifier of a device in the receiving side link in the embodiments of this disclosure can refer to step S101 above, and will not be repeated here.

[0118] In step S402, if 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.

[0119] For example, the method for determining the temporary identifier conflict between the first relay device and the first remote device in the embodiments of this disclosure can refer to step S302 above, and will not be repeated here.

[0120] 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 peer device to reassign a temporary identifier to the first remote device.

[0121] Specifically, when the first relay device determines that the first temporary identifier and the second temporary identifier conflict, it can generate a first conflict indication and forward the first conflict indication to the first peer device through the first remote device.

[0122] For example, if the first relay device does not have the ability to parse and process forwarded content, it can directly send the first conflict indication to the first remote device. After parsing and determining the first conflict indication, the first remote device forwards the first conflict indication to the first relay device, which then forwards it to the first peer device. In this case, the first relay device acts as a data forwarder without parsing or processing the data forwarded between the first peer device and the first remote device. The first peer device reallocates a temporary identifier for the first remote device based on the first conflict indication. This 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 can use the reallocated temporary identifier.

[0123] In any embodiment of this disclosure, the first peer device can be the first remote device, and the first remote device can be the first peer device. Therefore, the above steps can be converted into the first remote device assigning a temporary identifier to the first peer device. The specific steps are similar to the above steps and will not be repeated here.

[0124] With the above technical solution, when the first relay device receives a second temporary identifier from the first remote device that is the same as the first temporary identifier of the first relay device, it determines that there is a temporary identifier conflict. At this time, it can send a first conflict indication to the first remote device. The first remote device returns the first conflict indication to the first peer device through the first relay device, so as to instruct the first peer device to reallocate a temporary identifier for the first remote device according to 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 according to the different temporary identifiers, thus avoiding data loss.

[0125] Figure 6 This is a flowchart illustrating a temporary identifier scheduling method in an exemplary embodiment, such as... Figure 6 As shown, the temporary identifier scheduling method is used in the first relay device and includes the following steps.

[0126] In step S501, a temporary identifier of at least one device in the receiving side link is obtained.

[0127] For example, the method for receiving the temporary identifier of a device in the receiving side link in the embodiments of this disclosure can refer to step S101 above, and will not be repeated here.

[0128] In step S502, if 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.

[0129] 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 to be assigned to the second peer device by the second remote device.

[0130] For example, in the second relay group, since the second remote device and the second peer 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 peer device.

[0131] 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 something the second remote device wants to forward to the second peer device through itself, or whether the second relay device, as the first peer device, was assigned to itself by the first remote device. In this case, the temporary identifiers of the second peer device and the first peer device conflict.

[0132] 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 the peer device that the second remote device connects to through the second relay device.

[0133] Specifically, when the first relay device determines that the temporary identifier of the first peer device conflicts with the temporary identifier of the second peer device, since the first relay device is the second remote device in the second relay group, the first relay device can directly reassign a temporary identifier to the second peer device. This temporary identifier is different from the temporary identifier of the second peer device and the temporary identifier of the second relay device. This temporary identifier is carried in the conflict indication. The second peer device parses the conflict indication and obtains the temporary identifier reassigned by the second remote device from the conflict indication.

[0134] The collision indication sent by the first relay device to the second remote device carries a temporary identifier assigned to the second peer device.

[0135] Of course, the second relay device in the second relay group can also determine whether the temporary identifier of the second peer device conflicts with its own temporary identifier. When the second peer device receives two reassigned temporary identifiers, it can choose one of them. Alternatively, the second relay device in the second relay group does not need to determine whether the temporary identifier of the second peer device conflicts with its own temporary identifier; the first relay device can make the determination.

[0136] In any embodiment of this disclosure, the first relay device can be a second relay device, and the second relay device can be a first relay device. In this way, the second relay device can perform the functions implemented by the first relay device, and the first relay device can also perform the functions implemented by the second relay device. This disclosure does not impose any limitations on this.

[0137] 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, a temporary identifier conflict is identified. At this time, a conflict indication can be sent to the second peer device, which then parses the conflict indication to obtain a reassigned temporary identifier. When the second remote device has a reassigned 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, thus avoiding data loss.

[0138] Figure 7 This is a flowchart illustrating a temporary identifier scheduling method in an exemplary embodiment, such as... Figure 7 As shown, the temporary identifier scheduling method is used in the first relay device and includes the following steps.

[0139] In step S601, the temporary identifier and identifier of the first peer device sent by the first remote device are received; and / or, the temporary identifier and identifier of the first remote device sent by the first peer device are received.

[0140] 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 assigned by the first remote device to the first peer device.

[0141] In this context, 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 recipient of the temporary identifier through the identifier of the peer device.

[0142] For example, the first remote device has multiple identifiers for peer devices, each of which can uniquely identify a peer device. When the first remote device determines that it needs to assign a temporary identifier to the first peer device, it can send the identifier of the first peer device and the temporary identifier assigned to the first peer device to the first relay device. The first relay device determines that the recipient 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.

[0143] For example, if there are two peer devices B and F communicating with the first remote device through the first relay device, when the first remote device determines that a temporary identifier needs to be reallocated for B based on the conflict indication, it can send B's identifier and the temporary identifier to the first relay device. The first relay device determines that the temporary identifier is allocated to B based on the identifier, so it sends the temporary identifier to the B corresponding to the identifier.

[0144] 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 the 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 assigned by the first peer device to the first remote device to the first remote device.

[0145] In this context, 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 since there may be multiple remote devices communicating with the first peer device through the first relay device, the first peer device needs to determine the recipient to which the temporary identifier is sent.

[0146] For example, the first peer device has multiple identifiers for remote devices, each of which can uniquely identify a remote device. When the first peer device determines that it needs to assign a temporary identifier to the first remote device, it can send the identifier of the first remote device and the temporary identifier assigned to the first remote device to the first relay device. The first relay device determines that the recipient of the temporary identifier is 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.

[0147] In some embodiments, the device may also receive a temporary identifier and identifier of the first peer device sent by the first remote device; and receive a temporary identifier and identifier of the first remote device sent by the first peer device.

[0148] For example, when the first peer device assigns a temporary identifier to the first remote device, it needs to send the identifier of the first remote device and the temporary identifier assigned to the first remote device to the first relay device. The first relay device then sends the temporary identifier to the first remote device corresponding to the identifier. Similarly, when the first remote device assigns a temporary identifier to the first peer device, it needs to send the identifier of the first peer device and the temporary identifier assigned to the first peer device to the first relay device. The first relay device then sends the temporary identifier to the first peer device corresponding to the identifier.

[0149] The method of determining the corresponding peer device or remote device based on the identifier can be used for the allocation of temporary identifiers before a conflict occurs, or for the redistribution of temporary identifiers after a conflict occurs. This disclosure does not limit the specific application scenario.

[0150] In step S602, in response to a temporary identifier conflict between the temporary identifiers of the device, a conflict indication is sent to the peer device of the device.

[0151] For example, the step of sending a conflict indication in the embodiments of this disclosure can refer to step S102 above, and will not be repeated here.

[0152] Through the above technical solution, after the first relay device receives the temporary identifier and the identifier of the remote device, it can forward the temporary identifier to the remote device corresponding to the identifier; after the first relay device receives the temporary identifier and the identifier of the peer device, it can also forward the temporary identifier to the peer device corresponding to the identifier. This enables the first peer device to assign the temporary identifier to the correct first remote device, and the first remote device to assign the temporary identifier to the correct first peer device, avoiding the occurrence of incorrect temporary identifier assignment.

[0153] Figure 8This is a flowchart illustrating a temporary identifier scheduling method in an exemplary embodiment, such as... Figure 8 As shown, the temporary identifier scheduling method is used in the first remote device and includes the following steps.

[0154] In step S701, the conflict indication sent by the first relay device is forwarded to the device in the side link.

[0155] In this context, the device in the side link can be a first relay device and / or a first peer device. The conflict indication carries a temporary identifier that the first relay device suggests the first peer device assign to the first remote device. This temporary identifier is different from the temporary identifier of the first remote device.

[0156] 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 then forward the conflict indication to the first peer device; the first peer device will then reallocate a temporary identifier for 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 directly send the conflict indication to the first peer device.

[0157] The conflict indication carries a temporary identifier that the first relay device suggests the first peer device assign to the first remote device, which is different from the temporary identifier of the first remote device.

[0158] In step S702, a temporary identifier of the device in the receiving side crosslink is obtained.

[0159] When the first peer device receives a conflict indication determined by the first relay device or the first remote device, it can use the temporary identifier suggested in the conflict indication to reassign a temporary identifier to the first remote device.

[0160] For example, the first peer device sends the reassigned temporary identifier to the first relay device, which then forwards the reassigned temporary identifier to the first remote device. After determining its own temporary identifier, the first remote device can also forward its own temporary identifier to other relay devices or other peer devices.

[0161] With the above technical solution, when the first relay device receives a temporary identifier conflict from a device in the side link, it can send a conflict indication to the first peer 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. This allows the first remote device to receive a reassigned temporary identifier returned by the device in the side link, thereby avoiding data loss caused by the temporary identifier conflict.

[0162] Figure 9 This is a flowchart illustrating a temporary identifier scheduling method in an exemplary embodiment, such as... Figure 9 As shown, the temporary identifier scheduling method is used in the first remote device and includes the following steps.

[0163] In step S801, the conflict indication sent by the first relay device is forwarded to the device in the side link.

[0164] For example, the steps for forwarding conflict indications in the embodiments of this disclosure can refer to step S701 above, and will not be repeated here.

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

[0166] The first remote device interacts with the first relay device, so the first remote device can receive the temporary identifier forwarded to it by the first relay device. The first remote device can be the recipient of the new identifier and receive the temporary identifier forwarded to it by the first peer device through the first relay device.

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

[0168] If the first relay device can parse and forward the content, it means that the first relay device can parse and forward the content and obtain the temporary identifier assigned to the first remote device by the first peer 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.

[0169] In this process, the first remote UE is the destination UE, and the first relay device is the source UE.

[0170] For example, the temporary identifier sent by the first relay device is, when the first relay device receives the identifier of the first remote device and the temporary identifier sent by the first peer device, it sends the temporary identifier assigned by the first peer device to the first remote device according to the identifier of the first remote device.

[0171] In some embodiments, the first remote device may receive a temporary identifier assigned to the first remote device by the first peer device.

[0172] If the first relay device can forward data but does not parse or process the data, it means that the first relay device does not perform the function of parsing and forwarding content. In this case, the first relay device performs the function of forwarding data, so the first remote device receives the temporary identifier assigned by the first peer device.

[0173] In this process, the first remote device acts as the destination UE, and the first peer device acts as the source UE.

[0174] It is worth noting that the temporary identifier allocated by the first remote device to the first peer device can be a temporary identifier forwarded by the first relay device without performing the function of parsing and forwarding content.

[0175] In some embodiments, the first remote device may receive a temporary identifier assigned to it by the first remote device and a temporary identifier sent by the first relay device.

[0176] It is worth noting that, before the first remote device receives a conflict indication, if 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 peer device to determine whether its own temporary identifier conflicts with the first remote device; if the first relay device does not perform the function of parsing and forwarding data, the first remote device receives the temporary identifier forwarded to it by the first peer device through 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.

[0177] Through the above technical solution, after forwarding the conflict indication to the device in the side link, the first remote device can receive the temporary identifier reassigned to the first remote device by the first relay device, and / or receive the temporary identifier reassigned to the first remote device by the first peer device, so that after the temporary identifier of the first remote device conflicts with the temporary identifier of the first relay device, it can receive a temporary identifier different from the temporary identifier of the first relay device, so as to distinguish it from the temporary identifier of the first relay device.

[0178] Figure 10 This is a flowchart illustrating a temporary identifier scheduling method in an exemplary embodiment, such as... Figure 10 As shown, the temporary identifier scheduling method is used in the first peer device and includes the following steps.

[0179] In step S901, a collision indication is sent by the receiving device on the crosslink side.

[0180] The first peer device can receive a collision indication sent by the first remote device in the side link, or it can receive a collision indication sent by the first relay device in the side link.

[0181] In the case where the first relay device does not perform the function of parsing and forwarding data, the first peer device, as the destination UE, can receive the conflict indication sent by the first remote device, which is the source UE.

[0182] For example, the first remote device obtains a conflict indication from the first relay device. The first remote device, as the source UE, forwards the conflict indication to the first peer device, which is the destination UE, through the first relay device.

[0183] In the case where the first relay device performs the function of parsing and forwarding data, the first peer device, as the destination UE, can receive the conflict indication sent by the first relay device, which is the source UE.

[0184] For example, the first remote device can obtain the conflict indication directly from the first relay device.

[0185] The first peer device, as the party assigning the identifier to the first remote device, carries in the conflict indication a temporary identifier that the first relay device suggests the first peer device assign to the first remote device.

[0186] In step S902, a temporary identifier is reassigned to the corresponding device according to the conflict indication.

[0187] The first peer device can reassign an identifier to the first remote device based on the suggested temporary identifier carried in the conflict indication, or it can generate a new temporary identifier to be assigned to the first remote device itself.

[0188] The first peer device assigns a temporary identifier to the first remote device and / or receives a temporary identifier assigned by the first remote device to the first peer device.

[0189] With the above technical solution, when the temporary identifiers of the first remote device and the first relay device conflict, the first peer device can receive the conflict indication sent by the device on the side link and reallocate the temporary identifier for the first remote device according to the conflict indication, so that the temporary identifier of the first remote device is different from the temporary identifier of the first relay device. The first relay device can distinguish between the different temporary identifiers and forward the different temporary identifiers to different devices.

[0190] Figure 11 This is a flowchart illustrating a temporary identifier scheduling method in an exemplary embodiment, such as... Figure 11 As shown, the temporary identifier scheduling method is used in the first peer device and includes the following steps.

[0191] In step S110, the temporary identifier of the first remote device and / or the identifier of the first remote device are sent to the first relay device, and the first remote device communicates with the first peer device through the first relay device.

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

[0193] In this embodiment, the first peer device directly sends the temporary identifier of the first remote device to the first relay device, and / or the first peer device forwards the temporary identifier of the first remote device to the first remote device, which then forwards it to the first relay device. The method of forwarding the temporary identifier in this embodiment can refer to the above step S802, and will not be repeated here.

[0194] In some embodiments, the identifier of the first remote device is sent to the first relay device.

[0195] For example, the method for forwarding the identifier in the embodiments of this disclosure can refer to step S802 above, and will not be repeated here.

[0196] In some embodiments, a temporary identifier and an identifier of the first remote device are sent to the first relay device.

[0197] For example, the method for forwarding temporary identifiers in the embodiments of this disclosure can refer to step S802 above, and will not be repeated here.

[0198] With the above technical solution, when the temporary identifiers of the first remote device and the first relay device conflict, the first peer device can receive the conflict indication sent by the device on the side link and reallocate the temporary identifier for the first remote device according to the conflict indication, so that the temporary identifier of the first remote device is different from the temporary identifier of the first relay device. The first relay device can distinguish between the different temporary identifiers and forward the different temporary identifiers to different devices.

[0199] Figure 12 This is a block diagram illustrating a temporary identifier scheduling device according to an exemplary embodiment. (Refer to...) Figure 12 The temporary identifier scheduling device 120, which is applied to the first relay device, includes a first receiving module 121 and a first sending module 122.

[0200] The first receiving module 121 is configured as a temporary identifier for at least one device in the receiving-side crosslink;

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

[0202] Optionally, the device includes a first remote device or a first peer device, and the first transmitting module 122 includes at least one of the following modules:

[0203] The first conflict indication sending module is configured to send a conflict indication to the first peer device in response to a temporary identifier conflict between the first relay device and the first remote device.

[0204] The second conflict indication sending module is configured to send a conflict indication to the first remote device in response to a temporary identifier conflict between the first relay device and the first peer device; wherein the first peer device is the peer device that the first remote device connects to through the first relay device.

[0205] Optionally, the temporary identifier scheduling device 120 includes:

[0206] The first conflict confirmation module is configured to determine that there is a temporary identifier conflict between the first relay device and the first remote device if the first temporary identifier of the first relay device is the same as the second temporary identifier of the first remote device.

[0207] Optionally, the first collision indication sending module includes:

[0208] The third conflict indication sending module is configured to send a first conflict indication to the first peer 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 peer device to reassign a temporary identifier to the first remote device.

[0209] Optionally, the first collision indication sending module includes:

[0210] The fourth conflict indication sending module is 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.

[0211] The first conflict indication is used to instruct the first peer device to reassign a temporary identifier to the first remote device.

[0212] Optionally, the temporary identifier scheduling device 120 includes:

[0213] The instruction forwarding module is configured to forward a first conflict indication received from the first remote device to the first peer device.

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

[0215] Optionally, the device includes a second remote device and a second peer device.

[0216] Optionally, the first transmitting module 122 includes:

[0217] The fifth conflict indication sending module is configured to send a conflict indication to the peer device of the device in response to a temporary identifier conflict between the first peer device and the second peer device; the second peer device is the peer device that the second remote device connects to through the second relay device.

[0218] Optionally, the temporary identifier scheduling device 120 includes:

[0219] The second conflict confirmation module is configured to determine that there is a temporary identifier conflict between the first peer device and the second peer device if the third temporary identifier of the first peer device is the same as the fourth temporary identifier of the second peer device.

[0220] Optionally, the second conflict confirmation module includes:

[0221] The temporary identifier reassignment module is configured to send a conflict indication to the second peer device in response to the first peer device and the second peer device having the same temporary identifier, the conflict indication carrying a temporary identifier reassigned for the second peer device.

[0222] Optionally, the device includes a first remote device or a first peer device, and the first receiving module 121 includes:

[0223] The first identifier receiving module is configured to receive the temporary identifier and identifier of the first peer device sent by the first remote device; and / or

[0224] The second identifier receiving module is configured to receive the temporary identifier and identifier of the first remote device sent by the first peer device.

[0225] Optionally, the second identifier receiving module includes:

[0226] The third identifier receiving module is configured to receive the identifier and temporary identifier of the first remote device sent by the first peer device;

[0227] The first remote device confirmation module is configured to determine the first remote device of the first peer device based on the identifier of the first remote device.

[0228] The first temporary identifier forwarding module is configured to send the temporary identifier assigned by the first peer device to the first remote device to the first remote device.

[0229] Optionally, the first identifier receiving module includes:

[0230] The fourth identifier receiving module is configured to receive the identifier and temporary identifier of the first peer device sent by the first remote device;

[0231] The first peer device confirmation module is configured to determine the first peer device of the first remote device based on the identifier of the first peer device.

[0232] The second temporary identifier forwarding module is configured to send the temporary identifier assigned by the first remote device to the first peer device to the first peer device.

[0233] Figure 13 This is a block diagram illustrating a temporary identifier scheduling device according to an exemplary embodiment. (Refer to...) Figure 13 The temporary identifier scheduling device 220, which is applied to the first remote device, includes a conflict indication forwarding module 221 and a second receiving module 222.

[0234] The conflict indication forwarding module 221 is configured to forward the conflict indication sent by the first relay device to the device in the side link;

[0235] The second receiving module 222 is configured to receive temporary identifiers sent by devices in the crosslink.

[0236] Optionally, the second receiving module 222 includes:

[0237] 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 the first peer device of the first remote device.

[0238] Optionally, the temporary identifier sent by the first relay device is, upon receiving the identifier and temporary identifier of the first remote device, the first relay device sends the temporary identifier allocated by the first peer device to the first remote device to the first remote device based on the identifier of the first remote device.

[0239] Optionally, the conflict indication forwarding module 221 includes:

[0240] The first conflict indication forwarding module is configured to send the conflict indication to the first peer device of the first remote device.

[0241] Optionally, the first conflict indication forwarding module includes:

[0242] The second conflict indication forwarding module is configured to send the conflict indication to the first peer device in response to the conflict indication sent by the first relay device. The conflict indication is used to instruct the first peer device to reallocate a temporary identifier for the first remote device.

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

[0244] Figure 14 This is a block diagram illustrating a temporary identifier scheduling device according to an exemplary embodiment. (Refer to...) Figure 14The temporary identifier scheduling device 330, which is applied to the first peer device, includes a conflict indication forwarding module 331 and a second receiving module 332.

[0245] The collision indication receiving module 331 is configured to receive collision indications sent by devices on the side link;

[0246] Temporary identifier allocation module 332 is configured to reallocate temporary identifiers to the corresponding devices based on the conflict indication.

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

[0248] Based on the conflict indication, the reassigned temporary identifier is sent to the first remote device.

[0249] Optionally, the temporary identification scheduling device 330 includes:

[0250] 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 the first relay device, through which the first remote device and the first peer device communicate.

[0251] Optionally, the temporary identification scheduling device 330 includes:

[0252] The temporary identifier transceiver module is configured to assign a temporary identifier to the first remote device and / or receive a temporary identifier assigned by the first remote device to the first peer device.

[0253] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0254] This disclosure also provides a computer-readable storage medium having stored thereon computer program instructions that, when executed by a processor, implement the steps of the temporary identifier scheduling method provided in this disclosure.

[0255] Figure 15 This is a block diagram illustrating an apparatus according to an exemplary embodiment. The apparatus can be any one of a relay device, a remote device, and a peer device. For example, apparatus 800 can be a mobile phone, a computer, a digital broadcasting terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

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

[0257] Processing component 802 typically controls the overall operation of device 800, such as operations associated with display, telephone calls, data communication, camera operation, and recording. Processing component 802 may include one or more processors 820 to execute instructions to perform all or part of the steps of the methods described above. Furthermore, processing component 802 may include one or more modules to facilitate interaction between processing component 802 and other components. For example, processing component 802 may include a multimedia module to facilitate interaction between multimedia component 808 and processing component 802.

[0258] Memory 804 is configured to store various types of data to support the operation of device 800. Examples of such data include instructions for any application or method operating on device 800, contact data, phonebook data, messages, pictures, videos, etc. 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 storage, flash memory, magnetic disk, or optical disk.

[0259] Power supply component 806 provides power to various components of device 800. Power supply component 806 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power to device 800.

[0260] 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 touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 808 includes a front-facing camera and / or a rear-facing camera. When the device 800 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.

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

[0262] Input / output interface 812 provides an interface between processing component 802 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.

[0263] Sensor assembly 814 includes one or more sensors for providing status assessments of various aspects of device 800. For example, sensor assembly 814 may detect the on / off state of device 800, the relative positioning of components such as the display and keypad of device 800, changes in the position of device 800 or a component of device 800, the presence or absence of user contact with device 800, the orientation or acceleration / deceleration of device 800, and temperature changes of device 800. Sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 814 may also include an accelerometer, a gyroscope, a magnetometer, a pressure sensor, or a temperature sensor.

[0264] Communication component 816 is configured to facilitate wired or wireless communication between device 800 and other devices. Device 800 can access wireless networks based on communication standards, such as WiFi, 2G, or 3G, or combinations thereof. In one exemplary embodiment, communication component 816 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 816 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0265] 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 methods described above.

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

[0267] The aforementioned device can be a standalone electronic device or a part of a standalone electronic device. For example, in one embodiment, the device can be an integrated circuit (IC) or a chip, wherein the integrated circuit can be a single 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), and SoC (System on Chip). The aforementioned integrated circuit or chip can be used to execute executable instructions (or code) to implement the aforementioned temporary identifier scheduling method. The executable instructions can be stored in the integrated circuit or chip or obtained from other devices or equipment. For example, the integrated circuit or chip includes a processor, 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, it implements the temporary identifier scheduling method described above; or, the integrated circuit or chip can receive the executable instruction through the interface and transmit it to the processor for execution to implement the temporary identifier scheduling method described above.

[0268] In another exemplary embodiment, a computer program product is also provided, the computer program product comprising a computer program executable by a programmable device, the computer program having a code portion for performing the temporary identifier scheduling method described above when executed by the programmable device.

[0269] This disclosure also provides a communication system including a remote UE, a peer UE of the remote UE, and a relay UE, wherein the remote UE and the peer UE are each other's remote UEs. The remote UE and the relay UE can execute the temporary identifier scheduling method described above.

[0270] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of this disclosure. This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this disclosure are indicated by the following claims.

[0271] It should be understood that this disclosure is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this disclosure is limited only by the appended claims.

Claims

1. A temporary identifier scheduling method, wherein, The first relay device applied in the first relay group includes: Temporary identifier of at least one device in the receiving-side crosslink; In response to a temporary identifier conflict in the temporary identifier of the device, a conflict indication is sent to the peer device of the device; the conflict indication is used to instruct the peer device to reassign a temporary identifier to the device. The device includes a first remote device or a first peer device in a first relay group, or the device includes a first peer device in the first relay group and a second peer device in a second relay group, wherein the first relay device can function as a second remote device or a second peer device in the second relay group; the step of sending a conflict indication to the peer device of the device in response to a temporary identifier conflict of the device includes at least one of the following: In response to a temporary identifier conflict between the first relay device and the first remote device, a conflict indication is sent to the first peer device. In response to a temporary identifier conflict between the first relay device and the first peer device, a conflict indication is sent to the first remote device; wherein, the first peer device is the peer device that the first remote device connects to through the first relay device; 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 the peer device that the second remote device connects to through the second relay device in the second relay group.

2. The method according to claim 1, wherein, The method further includes: If 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.

3. The method according to claim 1, 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 peer device. The first conflict indication is used to instruct the first peer device to reassign a temporary identifier to the first remote device.

4. The method according to claim 1, 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 remote device; The first conflict indication is used to instruct the first peer device to reassign a temporary identifier to the first remote device.

5. The method according to claim 4, wherein, The method further includes: The first conflict indication received from the first remote device is forwarded to the first peer device.

6. The method according to any one of claims 3 to 5, wherein, The first conflict indication includes a temporary identifier suggested for the first remote device.

7. The method according to claim 1, wherein, The method further includes: If 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.

8. The method according to claim 1, wherein, The step of sending a conflict indication to the peer device in response to a temporary identifier conflict of the device includes: In response to the fact that the temporary identifiers of the first peer device and the second peer device are the same, a conflict indication is sent to the second peer device, the conflict indication carrying a temporary identifier reassigned for the second peer device.

9. The method according to claim 1, wherein, The device includes a first remote device or a first peer device, and the temporary identifier of at least one device in the receiving-side crosslink includes: Receive the temporary identifier and identifier of the first peer device sent by the first remote device; and / or Receive the temporary identifier and identifier of the first remote device sent by the first peer device.

10. The method according to claim 9, wherein, The receipt of the temporary identifier and identifier of the first remote device sent by the first peer device includes: Receive the identifier and temporary identifier of the first remote device sent by the first peer device; Based on the identifier of the first remote device, it is determined to be the first remote device of the first peer device; The temporary identifier assigned by the first peer device to the first remote device is sent to the first remote device.

11. The method according to claim 9, wherein, The receipt of the temporary identifier of the first peer device sent by the first remote device includes: Receive the identifier and temporary identifier of the first peer device sent by the first remote device; Based on the identifier of the first peer device, it is determined to be the first peer device of the first remote device; The temporary identifier assigned by the first remote device to the first peer device is sent to the first peer device.

12. A temporary identifier scheduling method, wherein, The first remote device applied in the first relay group includes: The conflict indication sent by the first relay device in the first relay group is forwarded to the device in the side link. The conflict indication is sent by the first relay device to the peer device of the device when there is a temporary identifier conflict between the temporary identifiers of at least one device in the side link. The conflict indication is used to instruct the peer device of the device to reallocate a temporary identifier for the device. Temporary identifiers sent by devices in the receiving crosslink; The device includes a first remote device or a first peer device in a first relay group, or the device includes a first peer device in the first relay group and a second peer device in a second relay group, wherein the first relay device can function as a second remote device or a second peer device in the second relay group; the temporary identifier conflict includes at least one of the following: The first relay device and the first remote device have a temporary identifier conflict; The first relay device and the first peer device have a temporary identifier conflict, wherein the first peer device is the peer device that the first remote device connects to through the first relay device; If there is 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 first peer device.

13. The method according to claim 12, wherein, The temporary identifier sent by the device in the receiving-side cross link includes: Receive a temporary identifier sent by the first relay device, and / or receive a temporary identifier sent by the first peer device of the first remote device.

14. The method according to claim 13, wherein, The temporary identifier sent by the first relay device is, upon receiving the identifier and temporary identifier of the first remote device, the first relay device sends the temporary identifier assigned to the first remote device by the first peer device to the first remote device based on the identifier of the first remote device.

15. The method according to claim 12, wherein, The step of forwarding the collision indication sent by the first relay device to the device in the side link includes: The conflict indication is sent to the first peer device of the first remote device.

16. The method according to claim 15, wherein, The step of sending the conflict indication to the first peer device of the first remote device includes: In response to a conflict indication sent by the first relay device, the conflict indication is sent to the first peer device, the conflict indication being used to instruct the first peer device to reassign a temporary identifier to the first remote device.

17. The method according to claim 15 or 16, wherein, The conflict indication includes a temporary identifier suggested for the first remote device.

18. A temporary identifier scheduling method, wherein, The first peer device applied in the first relay group includes: The device receiving the side link sends a conflict indication; the conflict indication is used to instruct the peer device to reassign a temporary identifier to the device, and the conflict indication is sent by the first relay device in the first relay group to the peer device of the device when there is a temporary identifier conflict between the temporary identifiers of at least one device in the side link; Based on the conflict indication, a temporary identifier is reassigned to the corresponding device; The device includes a first remote device or a first peer device in a first relay group, or the device includes a first peer device in the first relay group and a second peer device in a second relay group, wherein the first relay device can function as a second remote device or a second peer device in the second relay group; the temporary identifier conflict includes at least one of the following: The first relay device and the first remote device have a temporary identifier conflict; The first relay device and the first peer device have a temporary identifier conflict, wherein the first peer device is the peer device that the first remote device connects to through the first relay device; If there is 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 first peer device.

19. The method according to claim 18, wherein, The device includes a first remote device, and the step of reallocating a temporary identifier for the corresponding device according to the conflict indication includes: Based on the conflict indication, the reassigned temporary identifier is sent to the first remote device.

20. The method according to claim 18, wherein, The method further includes: The temporary identifier of the first remote device and / or the identifier of the first remote device are sent to the first relay device, and the first remote device communicates with the first peer device through the first relay device.

21. The method according to claim 18, wherein, The method further includes: Assign a temporary identifier to the first remote device, and / or receive a temporary identifier assigned by the first remote device to the first peer device.

22. A temporary identifier scheduling device, wherein, The first relay device applied in the first relay group includes: The first receiving module is configured as a temporary identifier for at least one device in the receiving-side crosslink; the conflict indication is used to instruct the peer device to reallocate a temporary identifier for the device. The first sending module is configured to send a conflict indication to the peer device of the device in response to a temporary identifier conflict of the temporary identifier of the device. The device includes a first remote device or a first peer device in a first relay group, or the device includes a first peer device in the first relay group and a second peer device in a second relay group, wherein the first relay device can function as a second remote device or a second peer device in the second relay group; the first transmitting module includes at least one of the following modules: The first conflict indication sending module is configured to send a conflict indication to the first peer device in response to a temporary identifier 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 identifier conflict between the first relay device and the first peer device; wherein the first peer device is the peer device that the first remote device connects to through the first relay device. The fifth conflict indication sending module is configured to send a conflict indication to the peer device of the device in response to a temporary identifier conflict between the first peer device and the second peer device; the second peer device is the peer device that the second remote device connects to through the second relay device.

23. A temporary identifier scheduling device, wherein, The first remote device applied in the first relay group includes: The conflict indication forwarding module is configured to forward a conflict indication sent by the first relay device in the first relay group to a device in the side link. The conflict indication is sent by the first relay device to the peer device of the device when there is a temporary identifier conflict between the temporary identifiers of at least one device in the side link. The conflict indication is used to instruct the peer device of the device to reallocate a temporary identifier for the device. The second receiving module is configured to receive temporary identifiers sent by devices in the receiving side link; The device includes a first remote device or a first peer device in a first relay group, or the device includes a first peer device in the first relay group and a second peer device in a second relay group, wherein the first relay device can function as a second remote device or a second peer device in the second relay group; the temporary identifier conflict includes at least one of the following: The first relay device and the first remote device have a temporary identifier conflict; The first relay device and the first peer device have a temporary identifier conflict, wherein the first peer device is the peer device that the first remote device connects to through the first relay device; If there is 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 first peer device.

24. A temporary identifier scheduling device, wherein, The first peer device applied in the first relay group includes: The conflict indication receiving module is configured to receive a conflict indication sent by a device on the side link; the conflict indication is used to instruct the peer device to reassign a temporary identifier to the device, and the conflict indication is sent by the first relay device in the first relay group to the peer device of the device when there is a temporary identifier conflict between the temporary identifiers of at least one device on the side link; The temporary identifier allocation module is configured to reallocate a temporary identifier to the corresponding device based on the conflict indication; The device includes a first remote device or a first peer device in a first relay group, or the device includes a first peer device in the first relay group and a second peer device in a second relay group, wherein the first relay device can function as a second remote device or a second peer device in the second relay group; the temporary identifier conflict includes at least one of the following: The first relay device and the first remote device have a temporary identifier conflict; The first relay device and the first peer device have a temporary identifier conflict, wherein the first peer device is the peer device that the first remote device connects to through the first relay device; If there is 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 first peer device.

25. A relay device, wherein, include: processor; Memory used to store processor-executable instructions; The processor is configured to implement the steps of the method according to any one of claims 1 to 11 when executing the executable instructions.

26. A remote device, wherein, include: processor; Memory used to store processor-executable instructions; The processor is configured to implement the steps of the method according to any one of claims 12 to 17 when executing the executable instructions.

27. A peer device, wherein, include: processor; Memory used to store processor-executable instructions; The processor is configured to implement the steps of the method according to any one of claims 18 to 21 when executing the executable instructions.

28. A computer-readable storage medium having stored thereon computer program instructions, wherein, When executed by a processor, the program instructions implement the steps of the method according to any one of claims 1 to 11, or the steps of the method according to any one of claims 12 to 17, or the steps of the method according to any one of claims 18 to 21.

29. A chip, wherein, It includes a processor and an interface; the processor is configured to read instructions to perform the steps of the method according to any one of claims 1 to 11, or to perform the steps of the method according to any one of claims 12 to 17, or to perform the steps of the method according to any one of claims 18 to 21.

Images