Terminal inspection method, communication device, communication system and storage medium

Abstract

The invention relates to a terminal checking method, communication equipment, a communication system and a storage medium. The terminal checking method comprises the steps that first information sent by a second terminal is received, the first information at least comprises second terminal information, and the second terminal information is used for describing the second terminal; and checking whether the second terminal information meets the first service requirement or not, and determining whether to execute an operation related to the link of the first service or not. Therefore, whether the terminal information of other terminals meets the service requirements or not is checked on the terminal side so as to support effective implementation of corresponding services.

Description

Terminal inspection method, communication equipment, communication system, and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a terminal inspection method, communication equipment, a communication system, and a storage medium. Background Art

[0002] In order to support direct communication between terminals, a sidelink (SL) communication method is introduced. Ranging refers to determining the distance between two or more terminals, or the direction from one terminal to another, through a PC5 interface. A PC5 interface refers to a communication interface between terminals, such as a short-range direct communication interface between vehicles, people, and road infrastructure. Sidelink SL positioning refers to estimating the position of a located terminal based on the sidelink SL. For example, ranging or sidelink SL positioning can be performed on a located terminal (e.g., a target terminal (target user equipment, target UE)) based on information from a terminal (e.g., a positioning terminal (located user equipment, located UE)). The reference terminal can be, for example, an SL reference terminal whose position is known or can be known in ranging or sidelink SL positioning. For another example, the relative position information of a terminal (e.g., a target terminal (target user equipment, target UE)) and another terminal (e.g., an SL reference terminal (sidelink reference user equipment, sidelink reference UE)) can be determined through ranging or sidelink SL positioning.

[0003] Summary of the Invention

[0004] The embodiments of the present disclosure provide a terminal inspection method, network device, terminal, device, chip system, storage medium, computer program and computer program product, which can be applied in the field of communication technology to solve the technical problem that "the relevant technology does not support checking on the terminal side whether the terminal information of other terminals meets business requirements, thereby affecting the effective implementation of the corresponding business."

[0005] The present disclosure provides a terminal inspection method, a communication device, a communication system, and a storage medium.

[0006] According to a first aspect of an embodiment of the present disclosure, a terminal inspection method is proposed, which is executed by a first terminal and includes: receiving first information sent by a second terminal, wherein the first information includes at least second terminal information, and the second terminal information is used to describe the second terminal; checking whether the second terminal information meets the first business requirements, and determining whether to perform operations related to the link of the first business.

[0007] According to a second aspect of an embodiment of the present disclosure, a terminal inspection method is proposed, which is executed by a second terminal, including: sending first information to a first terminal, wherein the first information includes at least second terminal information, the second terminal information is used to describe the second terminal, and the first information is used by the first terminal to check whether the second terminal information meets the first business requirements.

[0008] According to a third aspect of an embodiment of the present disclosure, a terminal inspection method is proposed, comprising: a second terminal sends first information to a first terminal, wherein the first information includes at least second terminal information, and the second terminal information is used to describe the second terminal; the first terminal receives the first information, and checks whether the second terminal information meets the first business requirements, and determines whether to perform operations related to the link of the first business.

[0009] According to the fourth aspect of an embodiment of the present disclosure, a terminal is proposed, comprising: a transceiver module for receiving first information sent by a second terminal, wherein the first information includes at least second terminal information, and the second terminal information is used to describe the second terminal; a processing module for checking whether the second terminal information meets the first business requirements and determining whether to perform operations related to the link of the first business.

[0010] According to the fifth aspect of an embodiment of the present disclosure, a terminal is proposed, comprising: a transceiver module for sending first information to a first terminal, wherein the first information includes at least second terminal information, the second terminal information is used to describe the second terminal, and the first information is used by the first terminal to check whether the second terminal information meets the first business requirement.

[0011] According to the sixth aspect of an embodiment of the present disclosure, a communication device is proposed, comprising: one or more processors; wherein the processor is used to call instructions to enable the communication device to execute the terminal inspection method of any one of the first aspect, the second aspect, and the third aspect.

[0012] According to the seventh aspect of an embodiment of the present disclosure, a communication system is proposed, characterized in that it includes a first terminal and a second terminal, wherein the first terminal is configured to implement the terminal inspection method of the first aspect, and the second terminal is configured to implement the terminal inspection method of the second aspect.

[0013] According to the eighth aspect of the embodiment of the present disclosure, a storage medium is proposed, which stores instructions, and is characterized in that when the instructions are executed on a communication device, the communication device executes a terminal inspection method as described in any one of the first, second, and third aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the background technology, the drawings required for use in the embodiments of the present disclosure or the background technology will be described below.

[0015] FIG1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure;

[0016] FIG2A is an interactive diagram illustrating a terminal inspection method according to an embodiment of the present disclosure;

[0017] FIG2B is an interactive diagram illustrating a terminal checking method according to another embodiment of the present disclosure;

[0018] FIG2C is an interactive diagram illustrating a terminal checking method according to another embodiment of the present disclosure;

[0019] FIG3A is an interactive schematic diagram illustrating a terminal checking method according to another embodiment of the present disclosure;

[0020] FIG3B is an interactive diagram illustrating a terminal checking method according to another embodiment of the present disclosure;

[0021] FIG3C is an interactive diagram illustrating a terminal checking method according to another embodiment of the present disclosure;

[0022] FIG3D is an interactive diagram illustrating a terminal checking method according to another embodiment of the present disclosure;

[0023] FIG4A is an interactive diagram illustrating a terminal checking method according to another embodiment of the present disclosure;

[0024] FIG4B is an interactive diagram illustrating a terminal checking method according to another embodiment of the present disclosure;

[0025] FIG4C is an interactive diagram illustrating a terminal checking method according to yet another embodiment of the present disclosure;

[0026] FIG4D is an interactive diagram illustrating a terminal checking method according to yet another embodiment of the present disclosure;

[0027] FIG5 is an interactive diagram illustrating a terminal checking method according to yet another embodiment of the present disclosure;

[0028] FIG6A is a schematic diagram of terminal inspection based on ProSe direct communication at the PC5 reference point in an embodiment of the present disclosure;

[0029] FIG6B is a schematic diagram of a terminal check process during modification of the layer 2 link in an embodiment of the present disclosure;

[0030] FIG6C is a schematic diagram of a terminal check process during service data exchange according to an embodiment of the present disclosure;

[0031] FIG7A is a schematic structural diagram of a terminal proposed in an embodiment of the present disclosure;

[0032] FIG7B is a schematic structural diagram of a terminal proposed in another embodiment of the present disclosure;

[0033] FIG8A is a schematic structural diagram of a communication device proposed in an embodiment of the present disclosure;

[0034] FIG8B is a schematic diagram of the structure of the chip proposed in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0035] The present disclosure provides terminal inspection methods, communication devices, communication systems, and storage media. In some embodiments, the terms "terminal inspection method," "information processing method," and "communication method" are interchangeable; the terms "terminal inspection device," "information processing device," and "communication device" are interchangeable; and the terms "information processing system" and "communication system" are interchangeable.

[0036] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0037] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0038] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0039] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0040] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0041] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0042] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0043] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0044] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different. For another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0045] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0046] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0047] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0048] In some embodiments, devices and equipment can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc.

[0049] In some embodiments, "network" can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.

[0050] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", and in some embodiments may also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission and / or reception point (TRP)" "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)", etc.

[0051] In some embodiments, "terminal" or "terminal device" may be referred to as "user equipment (UE)", "user terminal" "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc.

[0052] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0053] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0054] FIG1 is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0055] As shown in FIG1 , a communication system 100 includes a terminal 101, a terminal 102, a core network device 103, and an access network device 104. Terminal 101 or terminal 102 can be connected to core network device 103 via access network device 104. In some embodiments, terminal 101 or terminal 102 includes, for example, at least one of a mobile phone, a wearable device, an Internet of Things device, a car with communication capabilities, a smart car, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and a wireless terminal device in a smart home, but is not limited thereto.

[0056] In some embodiments, the communication system 100 may further include an access network device, which is, for example, a node or device that accesses a terminal to a wireless network. The access network device may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a wireless fidelity (WiFi) system, but is not limited thereto.

[0057] In some embodiments, the access network device 104 is, for example, a node or device that accesses the terminal to a wireless network. The access network device 104 may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a WiFi system, but is not limited thereto.

[0058] In some embodiments, the access network device 104 can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0059] In some embodiments, the core network device 103 may be a single device, or may be multiple devices or a group of devices. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0060] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution provided by the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present disclosure is also applicable to similar technical problems.

[0061] The following embodiments of the present disclosure may be applied to the communication system 100 shown in Figure 1, or a portion thereof, but are not limited thereto. The entities shown in Figure 1 are illustrative only. The communication system may include all or part of the entities shown in Figure 1, or may include other entities outside of Figure 1. The number and form of the entities may be arbitrary. The connection relationship between the entities is illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0062] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), future radio access (FRA), new radio access technology (RAT), new radio (NR), new radio access (NX), future generation radio access (FX), Global System for Mobile Communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0063] In order to support direct communication between terminals, a sidelink (SL) communication method is introduced. Ranging refers to determining the distance between two or more terminals, or the direction from one terminal to another, through a PC5 interface. A PC5 interface refers to a communication interface between terminals, such as a short-range direct communication interface between vehicles, people, and road infrastructure. Sidelink SL positioning refers to estimating the position of a located terminal based on the sidelink SL. For example, ranging or sidelink SL positioning can be performed on a located terminal (e.g., a target terminal (target user equipment, target UE)) based on information from a terminal (e.g., a positioning terminal (located user equipment, located UE)). The reference terminal can be, for example, an SL reference terminal whose position is known or can be known in ranging or sidelink SL positioning. For another example, the relative position information of a terminal (e.g., a target terminal (target user equipment, target UE)) and another terminal (e.g., an SL reference terminal (sidelink reference user equipment, sidelink reference UE)) can be determined through ranging or sidelink SL positioning.

[0064] Optionally, during the network-assisted sidelink positioning process, the position of the located terminal can be estimated with the help of the network by using the position of one or more positioning terminals, and the distance and / or direction between the positioning terminal and the located terminal, without limitation.

[0065] In some embodiments, "network" can be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).

[0066] Optionally, one or more positioning terminals may be discovered by the terminal or core network device to support network-assisted sidelink positioning, which is not limited.

[0067] Optionally, a terminal with a non-access stratum (NAS) signaling connection is in the CM-Connected state and can interact with the 5G core network (5G Core, 5GC) to estimate the terminal's location with the help of the network.

[0068] Optionally, when the LMF network element determines to use network-assisted sidelink positioning, the LMF network element may trigger the target terminal to perform positioning terminal discovery.

[0069] Optionally, to assist the target terminal, a Location Management Function (LMF) network element may provide the target terminal with a list of candidate positioning terminals. In this case, the LMF may maintain a list of candidate positioning terminals, which may include, for example, capabilities and location information of the positioning terminals.

[0070] Optionally, terminal discovery may be performed based on Mode A and Mode B.

[0071] Optionally, mode A involves a terminal announcing "I am here". In mode A, two roles are defined for terminals that participate in Proximity Services (ProSe) direct discovery and have ProSe enabled:

[0072] Announcement terminal: An announcement terminal can announce some information, which can be used by nearby terminals with discovery permissions.

[0073] Monitoring terminal: A terminal that monitors some interesting information published by the announcement terminal.

[0074] In mode A, the advertising terminal broadcasts discovery messages at a predefined discovery interval, and the listening terminals that are interested in these messages read and process them.

[0075] Optionally, mode B involves a terminal asking "Who's there?" and / or "Are you there?".

[0076] When using the constrained discovery type, in mode B, two roles are defined for ProSe-enabled terminals participating in ProSe direct discovery:

[0077] Discovery Terminal: A discovery terminal may send a request message, which may contain certain information about the discovery terminal that the discovery terminal is interested in discovering.

[0078] Discovered terminal: A discovered terminal can receive a request message and can also respond with some information related to the request message of the discovered terminal.

[0079] Mode B may be equivalent to asking “Who is there?” and / or “Are you there?” The discovery terminal may send information about other UEs that wish to receive a response, for example, the information may be a ProSe application identifier corresponding to a group, and members of the group may respond.

[0080] Optionally, terminal positioning assisted by SL positioning involves the 5G Core (5GC), which uses the positions of one or more positioning terminals, as well as the distance and / or direction between the target terminal and the positioning terminal, to estimate the location of the target terminal with the assistance of the network. For example, 5GC Mobile Originated Location Request (5GC-MO-LR) and 5GC Mobile Terminated Location Request (5GC-MT-LR) services.

[0081] Optionally, the ranging / SL positioning results may include: absolute position, relative position, distance and direction, depending on the service requirements. If the target terminal decides to start the SL-MO-LR process, the target terminal may include information about one or more SL reference terminals and / or positioning terminals in the service request message. If the Location Services Client (LCS Client) or the Application Function (AF) network element decides to obtain the ranging / SL positioning results of a group of n terminals (n≥2), i.e., terminal 1, terminal 2, ..., terminal n, the Gateway Mobile Location Center (GMLC) may specify the target terminal from the n terminals, and specify one or more reference terminals and / or positioning terminals, and then the SL-MT-LR process may be applied.

[0082] Optionally, discovery based on Mode A and Mode B can be used to support 5G ProSe terminal discovery (including commercial and public safety use cases). When a ranging / SL positioning terminal is directly discovered, the discovery type is "ranging / SL positioning"; when a ranging / SL positioning group member is discovered, the "Application Layer Group ID" indicates the ranging / SL positioning group to which the terminal belongs.

[0083] Optionally, some communication protocols define a V2X communication process over the PC5 reference point for discovering terminals supporting V2X services. When using unicast mode V2X communication, the "Service Type" during Layer 2 link establishment is "Ranging / SL Positioning." When using broadcast or multicast mode V2X communication, the "Service Type" is "Ranging / SL Positioning."

[0084] Optionally, the role of the discovered terminal (e.g., target terminal, SL reference terminal, SL positioning server terminal, positioning terminal) can be included as RSPP-specific metadata in the discovery message (for terminals supporting 5G ProSe) and the unicast link establishment message (for terminals supporting vehicle to everything (V2X)).

[0085] Optionally, when SL positioning is applied to determine the absolute position of the target terminal, the target terminal discovers and selects the positioning terminal. When the LMF network element decides to apply SL positioning to the target terminal, the LMF triggers the target terminal to discover the positioning terminal. The LMF network element may provide the target terminal with a list of candidate positioning terminals as auxiliary data.

[0086] Optionally, when SL positioning is applied to determine the relative position of the target terminal, the target terminal may discover one or more SL reference terminals.

[0087] Optionally, the proximity service includes all PC5 services, for example, the proximity service ProSe identifier is "ranging / SL positioning", or the proximity service ProSe identifier is other ProSe services.

[0088] Optionally, for terminals with ProSe function enabled. When the terminal is discovered to perform ranging / SL positioning, it can be implemented based on mode A and mode B. In addition, the role information of the discovered terminal (such as the target terminal, SL reference terminal, SL positioning server terminal, positioning terminal) can be included in the discovery message (for terminals with ProSe function enabled). However, the ranging / SL positioning service is performed between terminals with specific role information, for example, requesting the relative position, distance and direction between the target terminal and the reference terminal, or requesting the absolute position of the target terminal based on SL positioning between the target terminal and the reference terminal. For discovery based on mode A, since the listening terminal does not send a response message to the announcement terminal, the role information of the listening terminal is not confirmed. For related terminals, the role information of the terminal may also change after the terminal is discovered. Therefore, it is necessary to check on the terminal side whether the terminal information (such as role information) of other terminals meets the business requirements to support the effective implementation of the corresponding business.

[0089] Based on this, the present disclosure proposes a terminal inspection method.

[0090] The embodiments of the present disclosure provide a method that can be applied to a first service scenario. For example, it can be applied to a ranging or SL positioning scenario. Alternatively, it can be applied to proximity services. Of course, the method of the present disclosure can also be applied to any other possible service scenario.

[0091] FIG2A is an interactive diagram of a terminal inspection method according to an embodiment of the present disclosure. As shown in FIG2A , the present disclosure embodiment relates to a terminal inspection method, which can be used in a communication system 100. The method includes:

[0092] Step S2101: The second terminal sends a direct communication request message to the first terminal.

[0093] In some embodiments, the terminal being inspected may be referred to as the second terminal, and the terminal inspecting the inspected terminal may be referred to as the first terminal. For example, the second terminal may be a listening terminal in a terminal discovery process based on Mode A, and the first terminal may be an announcing terminal in a terminal discovery process based on Mode A, without limitation.

[0094] In some embodiments, the second terminal may directly send a direct communication request message to the first terminal, and carry the second terminal information in the communication request message to notify the first terminal of the current second terminal information. There is no limitation to this.

[0095] In some embodiments, the second terminal can detect whether the terminal information of the terminal has changed. If it has changed, it can trigger the sending of a direct communication request message to the first terminal, carrying the second terminal information in the communication request message to notify the first terminal of the updated second terminal information.

[0096] In some embodiments, a direct communication request message may be used to trigger establishment of a link between a first terminal and a second terminal, and the direct communication request message includes first information. The first information may be information used to trigger the first terminal to check the second terminal, and the first information may include at least second terminal information, where the second terminal information is used to describe the second terminal.

[0097] The information used to describe the second terminal may be referred to as second terminal information. In some embodiments, the second terminal information includes at least one of the following: a second terminal identifier, role information of the second terminal, and Ranging and Sidelink Positioning Protocol (RSPP) metadata information, wherein the RSPP metadata information includes the role information of the second terminal. This effectively improves the accuracy of the second terminal information indication.

[0098] In some embodiments, the role information of the second terminal includes any one of the following: a piece of role information of the second terminal; a role information list, wherein the role information list includes: a plurality of pieces of role information of the second terminal. Thus, the flexibility of indicating the role information of the second terminal can be effectively improved.

[0099] That is, the number of role information of the second terminal can be one or more. If the number of role information of the second terminal is multiple, the multiple role information can constitute a role information list to indicate the multiple role information of the second terminal in the form of the role information list.

[0100] In some embodiments, the role information of the second terminal can be used to indicate the terminal role corresponding to the second terminal in the first service. The terminal role is, for example, a target terminal, an SL reference terminal, an SL positioning server terminal, or a positioning terminal, without limitation.

[0101] In some embodiments, the first service may be, for example, a proximity service (ProSe), thereby enabling the terminal side to check whether the terminal information of other terminals meets the service requirements of the proximity service (ProSe), thereby supporting the effective implementation of the proximity service (ProSe).

[0102] In some embodiments, the first service may be, for example, a ranging or SL positioning service, thereby enabling the terminal side to check whether the terminal information of other terminals meets the ranging or SL positioning service requirements, thereby supporting the effective implementation of the ranging or SL positioning service.

[0103] In some embodiments, the role information of the second terminal may be carried by the second terminal information, such as included in the second terminal information. For example, the second terminal information may include one or more role information corresponding to the corresponding second terminal.

[0104] In some embodiments, the role information of the second terminal may be carried by RSPP metadata information, for example, included in the RSPP metadata information, which in turn is included in the second terminal information. For example, the RSPP metadata information may include one or more role information corresponding to the corresponding second terminal. Of course, the RSPP metadata information may also include any other possible information, without limitation.

[0105] In some embodiments, the role information of different second terminals may be the same or different.

[0106] In some embodiments, the first information may further include at least one of the following: security information; first service information; first terminal information, where the first terminal information describes the first terminal; and RSPP metadata information, where the RSPP metadata information includes role information of the first terminal and / or role information of the second terminal. This effectively improves the comprehensiveness and flexibility of the first information indication.

[0107] In some embodiments, the first service information is used to describe the first service. The first service information is, for example, a service type.

[0108] The information used to describe the first terminal may be referred to as first terminal information. The first terminal information may be, for example, an application layer ID of the first terminal. The security information is used to support a security establishment process between the first terminal and the second terminal.

[0109] In some embodiments, the first terminal information includes at least one of the following: a first terminal identifier; role information of the first terminal; and RSPP metadata information, wherein the RSPP metadata information includes the role information of the first terminal. This effectively improves the flexibility and effectiveness of the first terminal information indication.

[0110] In some embodiments, the role information of the first terminal includes any one of the following: a piece of role information of the first terminal; a role information list, wherein the role information list includes: a plurality of pieces of role information of the first terminal. Thus, the flexibility of indicating the role information of the first terminal can be effectively improved.

[0111] That is, the number of role information of the first terminal may be one or more. If the number of role information of the first terminal is multiple, the multiple role information may constitute a role information list to indicate the multiple role information of the first terminal in the form of the role information list.

[0112] In some embodiments, the role information of the first terminal can be used to indicate the terminal role corresponding to the first terminal in the first service, and the terminal role is, for example, a target terminal, an SL reference terminal, an SL positioning server terminal, or a positioning terminal, without limitation. The first service can be, for example, a proximity service (ProSe), or a ranging or sidelink (SL) positioning service.

[0113] In some embodiments, the role information of the first terminal may be carried by the first terminal information, such as included in the first terminal information. For example, the first terminal information may include one or more role information corresponding to the first terminal.

[0114] In some embodiments, the role information of the first terminal may be carried by RSPP metadata information, for example, included in the RSPP metadata information, which in turn is included in the first terminal information. For example, the RSPP metadata information may include one or more role information corresponding to the corresponding first terminal. Of course, the RSPP metadata information may also include any other possible information, without limitation.

[0115] In some embodiments, the role information of different first terminals may be the same or different.

[0116] In some embodiments, the first information may also include RSPP metadata information, which may include the role information of the first terminal, or may also include the role information of the second terminal, or may also include the role information of the first terminal and the role information of the second terminal, thereby effectively improving the indication flexibility of the role information of the first terminal and the role information of the second terminal.

[0117] In some embodiments, the second terminal may send a direct communication request message to the first terminal and include the second terminal information in the direct communication request message to indicate the second terminal information to the first terminal, supporting the first terminal to check whether the second terminal information meets the first service requirement.

[0118] Step S2102: The first terminal receives a direct communication request message sent by the second terminal.

[0119] In some embodiments, the first terminal may receive a direct communication request message sent by the second terminal and obtain information about the second terminal. The first terminal may determine whether to accept the direct communication request message based on the information about the second terminal.

[0120] In some embodiments, the first terminal may check whether the second terminal information meets a first service requirement. The first service requirement refers to information, content, etc. required to implement the first service. For example, the terminal information required for the first service requirement may be determined, and then a determination may be made as to whether the second terminal information matches the terminal information required for the first service requirement. If so, the second terminal information is determined to meet the first service requirement; if not, the second terminal information is determined to not meet the first service requirement. This is not a limitation.

[0121] Step S2103: The first terminal checks whether the second terminal information meets the first service requirement.

[0122] In some embodiments, the first terminal may check whether the second terminal information meets the first service requirement, and then the first terminal may determine whether to perform operations related to the link of the first service based on whether the second terminal information meets the first service requirement.

[0123] In some embodiments, the number of first service requirements may be one or more. If the number of first service requirements is one, then it may be determined whether the second terminal information satisfies the one first service requirement. If the number of first service requirements is multiple, then it may be determined whether the second terminal information satisfies any one of the first service requirements, without limitation.

[0124] In some embodiments, if there are multiple first service requirements, the multiple first service requirements may correspond to multiple service requests respectively, or the multiple first service requirements may correspond to one service request together, which is not limited.

[0125] Step S2104: When the second terminal information meets the first service requirement, the first terminal sends a direct communication acceptance message to the second terminal.

[0126] In some embodiments, if the second terminal information meets the first service requirements, the first terminal sends a direct communication acceptance message to the second terminal. The direct communication acceptance message is used to indicate acceptance of establishing a link between the first terminal and the second terminal. This can support the effective implementation of the first service.

[0127] In some embodiments, the second terminal information meeting the first service requirement includes: the second terminal information in the first information matching the first service; and / or the RSPP metadata information in the first information matching the first service; and / or the role information of the second terminal in the first information matching the first service; and / or the second terminal information in the first information matching the link used for the first service. This effectively improves the flexibility and effectiveness of checking whether the second terminal information meets the first service requirement.

[0128] In some embodiments, the second terminal information meets the first service requirement, which may be, for example, that the second terminal information in the first information matches the first service.

[0129] In some embodiments, the second terminal information meets the first service requirement, which may be, for example, that the RSPP metadata information in the first information matches the first service.

[0130] In some embodiments, the second terminal information meets the first service requirement, which may be, for example, that the role information of the second terminal in the first information matches the first service.

[0131] In some embodiments, the second terminal information meets the first service requirement, which may be, for example, that the second terminal information in the first information matches the link used for the first service.

[0132] In some embodiments, the second terminal information meeting the first service requirement may be, for example, any combination of at least two of the four aforementioned situations. For example, the second terminal information in the first information matches the first service, and the RSPP metadata information in the first information matches the first service. Alternatively, the second terminal information in the first information matches the first service, and the role information of the second terminal in the first information matches the first service, and so on, without limitation.

[0133] Of course, the first service requirement may be flexibly set, and whether the second terminal information meets the first service requirement may be determined based on any other possible method, and there is no limitation on this.

[0134] Step S2105: When the second terminal information does not meet the first service requirement, the first terminal sends a direct communication rejection message to the second terminal.

[0135] In some embodiments, the direct communication rejection message is used to indicate that there is no need to establish a link between the first terminal and the second terminal.

[0136] In some embodiments, if the second terminal information does not meet the first service requirement, the first terminal sends a direct communication rejection message to the second terminal. This indicates that the first terminal has determined that a link between the first terminal and the second terminal is not necessary. This avoids establishing a link with the second terminal information that does not meet the first service requirement.

[0137] The terminal inspection method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2105. For example, step S2101 can be implemented as an independent embodiment, step S2102 can be implemented as an independent embodiment, and so on, but the present invention is not limited thereto. Steps S2101+S2102 can be implemented as independent embodiments, and steps S2101+S2102+S2103 can be implemented as independent embodiments, but the present invention is not limited thereto.

[0138] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0139] In this embodiment, the second terminal sends a direct communication request message to the first terminal. The first terminal receives the direct communication request message sent by the second terminal. The first terminal checks whether the second terminal information meets the first service requirement. If the second terminal information meets the first service requirement, the first terminal sends a direct communication acceptance message to the second terminal. If the second terminal information does not meet the first service requirement, the first terminal sends a direct communication rejection message to the second terminal. This allows the terminal side to check whether the terminal information of other terminals meets the service requirement during the link establishment process, thereby supporting the effective implementation of the corresponding service.

[0140] It should be noted that, for the description of the same or corresponding terms and method steps in the following embodiments, please refer to the above embodiments for details and will not be repeated here.

[0141] FIG2B is an interactive diagram of a terminal inspection method according to another embodiment of the present disclosure. As shown in FIG2B , the present disclosure embodiment relates to a terminal inspection method that can be used in a communication system 100. The method includes:

[0142] Step S2201: The second terminal sends a link modification request message to the first terminal.

[0143] This embodiment can be applied when a link between a first terminal and a second terminal has been established. The second terminal can detect whether its terminal information has changed. If so, and if it is determined that a link between the first terminal and the second terminal has been established, it can trigger the transmission of a link modification request message to the first terminal, carrying the second terminal information in the link modification request message, to notify the first terminal of the updated second terminal information. This is not limited to this.

[0144] In some embodiments, a link modification request message is used to request modification of a link between a first terminal and a second terminal. The link modification request message includes first information, and the first information includes at least second terminal information. For example, the second terminal may include the first information in the link modification request message and indicate the first information to the first terminal by sending the link modification request message to the first terminal.

[0145] Step S2202: The first terminal receives a link modification request message.

[0146] In some embodiments, the first terminal may receive a link modification request message and obtain first information in the link modification request message, thereby determining the second terminal information.

[0147] Step S2203: The first terminal checks whether the second terminal information meets the first service requirement.

[0148] In some embodiments, the first terminal may check whether the second terminal information meets the first service requirement, and determine whether to perform operations related to the link of the first service based on whether the second terminal information meets the first service requirement.

[0149] Step S2204: When the second terminal information meets the first service requirement, the first terminal sends a link modification acceptance message to the second terminal.

[0150] The link modification accept message is used to indicate acceptance of modification of the link between the first terminal and the second terminal.

[0151] In some embodiments, if the second terminal information meets the first service requirement, the first terminal may send a link modification acceptance message to the second terminal, indicating that the first terminal accepts the modification of the link between the first terminal and the second terminal. Optionally, the modification of the link between the first terminal and the second terminal may be triggered.

[0152] Step S2205: Modify the link between the first terminal and the second terminal, and release the service data flow that does not match the second terminal information.

[0153] In some embodiments, service data flows in the link that do not match the second terminal's information can be released. In some embodiments, the second terminal can cooperate with the first terminal to complete the release of the service data flows. For example, the first terminal initiates a new link modification process to the second terminal to delete the service data flows that do not match the second terminal's information.

[0154] In some embodiments, the first terminal may release the service data flow that does not match the second terminal information.

[0155] In some embodiments, if the first terminal checks and determines that the second terminal information meets the requirements of the first service, then the second terminal information is compatible with the first service. If the relevant service data flow is already included in the link, the service data flow that matches the second terminal information can be retained, and the service data flow that does not match the second terminal information can be released. This can effectively avoid excessive transmission resource usage and improve the efficiency of the first service.

[0156] In some embodiments, once the service data stream that does not match the second terminal's information has been transmitted, the first terminal can release the service data stream that does not match the second terminal's information. In other embodiments, the first terminal can directly release the service data stream that does not match the second terminal's information. This effectively increases the flexibility of selecting the timing for releasing the service data stream and is effectively applicable to personalized communication scenarios.

[0157] It should be noted that before sending the link modification acceptance message, the link between the first terminal and the second terminal in step S2205 can be triggered to modify the link and release the service data flow that does not match the information of the second terminal. Alternatively, after sending the link modification acceptance message, the link between the first terminal and the second terminal in step S2205 can be triggered to modify the link and release the service data flow that does not match the information of the second terminal. In other words, there is no restriction on the execution order of step S2204 and step S2205.

[0158] Step S2206: Modify the link between the first terminal and the second terminal to add a service data flow matching the second terminal information to the link.

[0159] In some embodiments, if the second terminal's information meets the requirements of the first service, and the relevant service data flow is not already included in the link, the first terminal can trigger modification of the link between the first terminal and the second terminal to add the service data flow that matches the second terminal's information to the link. For example, the first terminal may initiate a new link modification process to the second terminal to add the service data flow that matches the second terminal's information. This supports the effective implementation of the first service based on the established link.

[0160] In some embodiments, the second terminal may cooperate with the first terminal to complete the addition of the service data flow.

[0161] It should be noted that before sending the link modification acceptance message, the link between the first terminal and the second terminal in step S2206 can be triggered to modify the link to add a business data flow that matches the second terminal information to the link. Alternatively, after sending the link modification acceptance message, the link between the first terminal and the second terminal in step S2206 can be triggered to modify the link to add a business data flow that matches the second terminal information to the link. In other words, there is no restriction on the execution order of step S2204 and step S2206.

[0162] Step S2207: If the second terminal information does not meet the first service requirement, release the link between the first terminal and the second terminal.

[0163] In some embodiments, when the second terminal information does not meet the first service requirement, the first terminal may release the link between the first terminal and the second terminal.

[0164] In some embodiments, if the second terminal information does not meet the first service requirement, the first terminal may also send a link modification accept message or a link modification reject message to the second terminal. In other embodiments, the link between the first terminal and the second terminal may be released before sending the link modification accept message or the link modification reject message. In other embodiments, the link between the first terminal and the second terminal may also be released after sending the link modification accept message or the link modification reject message.

[0165] In some embodiments, in the process of releasing the link between the first terminal and the second terminal, the first terminal can initiate the release of the link between the first terminal and the second terminal, and the second terminal can cooperate with the first terminal to complete the link release. Alternatively, the second terminal can initiate the release of the link between the first terminal and the second terminal. For example, after receiving the link modification acceptance message or the link modification rejection message sent by the first terminal, the second terminal can initiate the release of the link between the first terminal and the second terminal based on the reason value carried in the link modification acceptance message or the link modification rejection message (the reason value can indicate that there is no matching service). There is no restriction on this.

[0166] In some embodiments, the link between the first terminal and the second terminal can be released if the second terminal information does not meet the first service requirement and the ongoing transmission of the first service data stream is completed. In other embodiments, the link between the first terminal and the second terminal can be directly released. Thus, since the second terminal information does not match the first service requirement, indicating that the established link is not suitable for the second terminal, the release of the link between the first terminal and the second terminal can be triggered.

[0167] The terminal inspection method involved in the embodiments of the present disclosure may include at least one of steps S2201 to S2207. For example, step S2201 can be implemented as an independent embodiment, step S2202 can be implemented as an independent embodiment, and so on, but the present invention is not limited thereto. Steps S2201+S2202 can be implemented as independent embodiments, and steps S2201+S2202+S2203 can be implemented as independent embodiments, but the present invention is not limited thereto.

[0168] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0169] In this embodiment, the second terminal sends a link modification request message to the first terminal, the first terminal receives the link modification request message, checks whether the second terminal information meets the first business requirement, and if the second terminal information meets the first business requirement, the first terminal sends a link modification acceptance message to the second terminal, modifies the link between the first terminal and the second terminal to release the business data flow that does not match the second terminal information, and / or modifies the link between the first terminal and the second terminal to add a business data flow that matches the second terminal information in the link. And if the second terminal information does not meet the first business requirement, the link between the first terminal and the second terminal is released. In this way, during the link modification process, the terminal side checks whether the terminal information of other terminals meets the business requirement to support the effective implementation of the corresponding business.

[0170] FIG2C is an interactive diagram of a terminal inspection method according to another embodiment of the present disclosure. As shown in FIG2C , the present disclosure embodiment relates to a terminal inspection method that can be used in a communication system 100. The method includes:

[0171] Step S2301: The second terminal sends a first service message or a first data packet to the first terminal.

[0172] This embodiment can be applied when a link between a first terminal and a second terminal has been established. The second terminal can detect whether its terminal information has changed. If so, and if it is determined that a link between the first terminal and the second terminal has been established, the second terminal can indicate the updated second terminal information to the first terminal during the first service data exchange with the first terminal.

[0173] In some embodiments, the second terminal may send a first service message to the first terminal and carry the first information in the first service message, where the first information includes at least the second terminal information, so as to indicate the second terminal information to the first terminal.

[0174] In some embodiments, the second terminal may send a first data packet to the first terminal and carry the first information in the first data packet, where the first information includes at least the second terminal information, so as to indicate the second terminal information to the first terminal.

[0175] Step S2302: The first terminal receives a first service message or a first data packet.

[0176] In some embodiments, the first terminal may receive a first service message sent by the second terminal, and obtain the second terminal information included in the first information from the first service message to trigger an inspection of the second terminal.

[0177] In some embodiments, the first terminal may receive a first data packet sent by the second terminal, and obtain the second terminal information included in the first information from the first data packet to trigger an inspection of the second terminal.

[0178] Step S2303: The first terminal checks whether the second terminal information meets the first service requirement.

[0179] Step S2304: When the second terminal information meets the first service requirement, retain the link between the first terminal and the second terminal.

[0180] Optionally, modification of the link between the first terminal and the second terminal may be triggered.

[0181] Step S2305: Modify the link between the first terminal and the second terminal, and release the service data flow that does not match the second terminal information.

[0182] In some embodiments, the first terminal may release the service data flow that does not match the second terminal information.

[0183] In some embodiments, if the first terminal checks and determines that the second terminal information meets the requirements of the first service, it indicates that the second terminal information is compatible with the first service. In this case, the service data stream that matches the second terminal information can be retained, and the service data stream that does not match the second terminal information can be released. This effectively avoids excessive transmission resource usage and improves the efficiency of the first service.

[0184] In some embodiments, once the service data stream that does not match the second terminal's information has been transmitted, the first terminal can release the service data stream that does not match the second terminal's information. In other embodiments, the first terminal can directly release the service data stream that does not match the second terminal's information. This effectively increases the flexibility of selecting the timing for releasing the service data stream and is effectively applicable to personalized communication scenarios.

[0185] Step S2306: Modify the link between the first terminal and the second terminal to add a service data flow matching the second terminal information to the link.

[0186] Step S2307: If the second terminal information does not meet the first service requirement, release the link between the first terminal and the second terminal.

[0187] In some embodiments, the link between the first terminal and the second terminal can be released if the second terminal information does not meet the first service requirement and the ongoing transmission of the first service data stream is completed. In other embodiments, the link between the first terminal and the second terminal can be directly released. Thus, since the second terminal information does not match the first service requirement, indicating that the established link is not suitable for the second terminal, the release of the link between the first terminal and the second terminal can be triggered.

[0188] For detailed description of steps S2303 to S2307, please refer to the above embodiment and will not be repeated here.

[0189] The terminal inspection method involved in the embodiments of the present disclosure may include at least one of steps S2301 to S2307. For example, step S2301 can be implemented as an independent embodiment, step S2302 can be implemented as an independent embodiment, and so on, but the present invention is not limited thereto. Steps S2301+S2302 can be implemented as independent embodiments, and steps S2301+S2302+S2303 can be implemented as independent embodiments, but the present invention is not limited thereto.

[0190] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0191] In this embodiment, the second terminal sends a first service message or a first data packet to the first terminal, the first terminal receives the first service message or the first data packet, checks whether the second terminal information meets the first service requirement, and if the second terminal information meets the first service requirement, retains the link between the first terminal and the second terminal, modifies the link between the first terminal and the second terminal, and releases the service data flow that does not match the second terminal information and / or adds the service data flow that matches the second terminal information in the link. If the second terminal information does not meet the first service requirement, the link between the first terminal and the second terminal is released. In this way, in the service data exchange, it is realized that the terminal information of other terminals meets the service requirement on the terminal side to support the effective implementation of the corresponding service.

[0192] FIG3A is an interactive diagram of a terminal inspection method according to another embodiment of the present disclosure. As shown in FIG3A , the present disclosure embodiment relates to a terminal inspection method that can be used for a first terminal. The method includes:

[0193] Step S3101: Receive first information sent by a second terminal, where the first information at least includes second terminal information, and the second terminal information is used to describe the second terminal.

[0194] Step S3102: Check whether the second terminal information meets the first service requirement, and determine whether to perform operations related to the link of the first service.

[0195] The terminal inspection method involved in the embodiments of the present disclosure may include at least one of steps S3101 and S3102. For example, step S3101 can be implemented as an independent embodiment, step S3102 can be implemented as an independent embodiment, and so on, but the present disclosure is not limited thereto. Steps S3101 and S3102 can be implemented as independent embodiments, but the present disclosure is not limited thereto.

[0196] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0197] FIG3B is an interactive diagram of a terminal inspection method according to another embodiment of the present disclosure. As shown in FIG3B , the present disclosure embodiment relates to a terminal inspection method that can be used for a first terminal. The method includes:

[0198] Step S3201: Receive a direct communication request message sent by a second terminal, wherein the direct communication request message is used to trigger establishment of a link between the first terminal and the second terminal, and the direct communication request message includes first information, the first information includes at least second terminal information, and the second terminal information is used to describe the second terminal.

[0199] Step S3202: The second terminal information meets the first service requirement, and a direct communication acceptance message is sent to the second terminal, wherein the direct communication acceptance message is used to indicate acceptance of establishing a link between the first terminal and the second terminal.

[0200] Step S3203: The second terminal information does not meet the first service requirement, and a direct communication rejection message is sent to the second terminal, wherein the direct communication rejection message is used to indicate that there is no need to establish a link between the first terminal and the second terminal.

[0201] The terminal inspection method involved in the embodiments of the present disclosure may include at least one of steps S3201 to S3203. For example, step S3201 can be implemented as an independent embodiment, step S3202 can be implemented as an independent embodiment, and so on, but the present invention is not limited thereto. Steps S3201+S3202 can be implemented as independent embodiments, and steps S3201+S3202+S3203 can be implemented as independent embodiments, but the present invention is not limited thereto.

[0202] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0203] FIG3C is an interactive diagram of a terminal inspection method according to another embodiment of the present disclosure. As shown in FIG3C , the present disclosure embodiment relates to a terminal inspection method that can be used for a first terminal. The method includes:

[0204] Step S3301: Receive a link modification request message sent by a second terminal, wherein the link modification request message is used to request modification of a link between a first terminal and a second terminal, and the link modification request message includes first information, the first information includes at least second terminal information, and the second terminal information is used to describe the second terminal.

[0205] Step S3302: The second terminal information meets the first service requirement, and a link modification accept message is sent to the second terminal, wherein the link modification accept message is used to indicate acceptance of modification of the link between the first terminal and the second terminal.

[0206] Step S3303: The second terminal information does not meet the first service requirement, and the link between the first terminal and the second terminal is released.

[0207] The terminal inspection method involved in the embodiments of the present disclosure may include at least one of steps S3301 to S3303. For example, step S3301 can be implemented as an independent embodiment, step S3302 can be implemented as an independent embodiment, and so on, but the present invention is not limited thereto. Steps S3301+S3302 can be implemented as independent embodiments, and steps S3301+S3302+S3303 can be implemented as independent embodiments, but the present invention is not limited thereto.

[0208] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0209] FIG3D is an interactive diagram of a terminal inspection method according to another embodiment of the present disclosure. As shown in FIG3D , the present disclosure embodiment relates to a terminal inspection method that can be used for a first terminal. The method includes:

[0210] Step S3401: Receive the first service message or the first data packet sent by the second terminal, wherein the first service message includes first information, or the first data packet includes first information, the first information includes at least second terminal information, and the second terminal information is used to describe the second terminal.

[0211] Step S3402: The second terminal information meets the first service requirement, and the link between the first terminal and the second terminal is retained.

[0212] Step S3403: The second terminal information does not meet the first service requirement, and the link between the first terminal and the second terminal is released.

[0213] The terminal inspection method involved in the embodiments of the present disclosure may include at least one of steps S3401 to S3403. For example, step S3401 can be implemented as an independent embodiment, step S3402 can be implemented as an independent embodiment, and so on, but the present invention is not limited thereto. Steps S3401+S3402 can be implemented as independent embodiments, and steps S3401+S3402+S3403 can be implemented as independent embodiments, but the present invention is not limited thereto.

[0214] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0215] FIG4A is an interactive diagram of a terminal inspection method according to another embodiment of the present disclosure. As shown in FIG4A , the present disclosure embodiment relates to a terminal inspection method that can be used for a second terminal. The method includes:

[0216] Step S4101: Send first information to a first terminal, wherein the first information includes at least second terminal information, the second terminal information is used to describe the second terminal, and the first information is used by the first terminal to check whether the second terminal information meets a first service requirement.

[0217] The terminal inspection method involved in the embodiment of the present disclosure may include step S4101. For example, step S4101 may be implemented as an independent embodiment, but is not limited thereto.

[0218] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0219] FIG4B is an interactive diagram of a terminal inspection method according to another embodiment of the present disclosure. As shown in FIG4B , the present disclosure embodiment relates to a terminal inspection method that can be used for a second terminal. The method includes:

[0220] Step S4201: Send a direct communication request message to the first terminal, where the direct communication request message is used to trigger establishment of a link between the first terminal and the second terminal, and the direct communication request message includes first information, the first information includes at least second terminal information, and the second terminal information is used to describe the second terminal.

[0221] Step S4202: Receive a direct communication acceptance message sent by the first terminal, wherein the direct communication acceptance message is used to indicate acceptance of establishing a link between the first terminal and the second terminal, and information of the second terminal meets the first service requirement.

[0222] Step S4203: Receive a direct communication rejection message sent by the first terminal, wherein the direct communication rejection message is used to indicate that there is no need to establish a link between the first terminal and the second terminal, and the second terminal information does not meet the first service requirement.

[0223] The terminal inspection method involved in the embodiments of the present disclosure may include at least one of steps S4201 to S4204. For example, step S4201 can be implemented as an independent embodiment, step S4202 can be implemented as an independent embodiment, and so on, but the present invention is not limited thereto. Steps S4201+S4202 can be implemented as independent embodiments, and steps S4201+S4202+S4203 can be implemented as independent embodiments, but the present invention is not limited thereto.

[0224] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0225] FIG4C is an interactive diagram of a terminal inspection method according to another embodiment of the present disclosure. As shown in FIG4C , the present disclosure embodiment relates to a terminal inspection method that can be used for a second terminal. The method includes:

[0226] Step S4301: Send a link modification request message to the first terminal, where the link modification request message is used to request modification of the link between the first terminal and the second terminal, and the link modification request message includes first information, the first information includes at least second terminal information, and the second terminal information is used to describe the second terminal.

[0227] Step S4302: Receive a link modification acceptance message sent by the first terminal, wherein the link modification acceptance message is used to indicate acceptance of modification of the link between the first terminal and the second terminal, and the second terminal information meets the first service requirement.

[0228] Step S4303: Receive a link modification rejection message sent by the first terminal, wherein the link modification rejection message is used to indicate rejection of modification of the link between the first terminal and the second terminal, and the second terminal information does not meet the first service requirement.

[0229] The terminal inspection method involved in the embodiments of the present disclosure may include at least one of steps S4301 to S4303. For example, step S4301 can be implemented as an independent embodiment, step S4302 can be implemented as an independent embodiment, and so on, but the present invention is not limited thereto. Steps S4301 + S4302 can be implemented as independent embodiments, but the present invention is not limited thereto.

[0230] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0231] FIG4D is an interactive diagram of a terminal inspection method according to another embodiment of the present disclosure. As shown in FIG4D , the present disclosure embodiment relates to a terminal inspection method that can be used for a second terminal. The method includes:

[0232] Step S4401: Send a first service message or a first data packet to a first terminal, wherein the first service message includes first information, or the first data packet includes first information, the first information includes at least second terminal information, and the second terminal information is used to describe the second terminal.

[0233] Step S4402: retaining a link between the first terminal and the second terminal, wherein the second terminal information meets the first service requirement.

[0234] Step S4403: releasing the link between the first terminal and the second terminal, wherein the second terminal information does not meet the first service requirement.

[0235] The terminal inspection method involved in the embodiments of the present disclosure may include at least one of steps S4401 to S4403. For example, step S4401 can be implemented as an independent embodiment, step S4402 can be implemented as an independent embodiment, and so on, but the present disclosure is not limited thereto. Steps S4401+S4402 can be implemented as independent embodiments, but the present disclosure is not limited thereto.

[0236] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0237] In the embodiment of the present disclosure, when implementing the above-mentioned step of releasing the service data flow that does not match the second terminal information, the second terminal can cooperate with the first terminal to complete the release of the service data flow.

[0238] In the embodiment of the present disclosure, when implementing the above-mentioned step of adding a service data flow matching the second terminal information in the link, the second terminal may cooperate with the first terminal to complete the addition of the service data flow.

[0239] In the embodiment of the present disclosure, in the step of implementing the above-mentioned release of the link between the first terminal and the second terminal, the first terminal can initiate the release of the link between the first terminal and the second terminal, and the second terminal can cooperate with the first terminal to complete the link release. Alternatively, the second terminal can initiate the release of the link between the first terminal and the second terminal. For example, after receiving the link modification acceptance message or the link modification rejection message sent by the first terminal, the second terminal can initiate the release of the link between the first terminal and the second terminal according to the cause value carried in the link modification acceptance message or the link modification rejection message (the cause value can indicate that there is no matching service). There is no restriction on this.

[0240] FIG5 is an interactive diagram of a terminal inspection method according to another embodiment of the present disclosure. As shown in FIG5 , the present disclosure embodiment relates to a terminal inspection method that can be used in a communication system. The communication system includes a first terminal and a second terminal, and the method includes:

[0241] Step S5101: The second terminal sends first information to the first terminal, where the first information at least includes second terminal information, and the second terminal information is used to describe the second terminal.

[0242] Step S5102: The first terminal receives the first information, checks whether the second terminal information meets the first service requirement, and determines whether to perform an operation related to the link of the first service.

[0243] The terminal inspection method involved in the embodiments of the present disclosure may include at least one of steps S5101 and S5102. For example, step S5101 can be implemented as an independent embodiment, step S5102 can be implemented as an independent embodiment, and so on, but the present invention is not limited thereto. Steps S5101 and S5102 can be implemented as independent embodiments, but the present invention is not limited thereto.

[0244] In this embodiment or example, unless there is any contradiction, each step can be independent, arbitrarily combined or exchanged in order, the optional methods or optional examples can be arbitrarily combined, and can be arbitrarily combined with any steps of other embodiments or other examples.

[0245] The terminal inspection method provided by the embodiments of the present disclosure can be applied during the terminal communication process after terminal discovery based on Mode A. It can check and confirm the terminal information of the initiating terminal to determine whether the initiating terminal is suitable for executing the corresponding service. Furthermore, the method takes into account the user information of the initiating terminal, ensuring that the appropriate links for the service are established and releasing unnecessary links.

[0246] The terminal checking method provided in the embodiments of the present disclosure can be applied to a terminal communication process after terminal discovery based on mode A. When an advertising terminal receives a link establishment request sent by a listening terminal based on terminal information of the advertising terminal (the listening terminal), the advertising terminal decides to communicate with the listening terminal, including:

[0247] The initiating terminal sends a link establishment request to the target terminal, or sends a link modification request / first data exchange to the target terminal through the established link, which includes metadata information, such as the terminal role of the initiating terminal.

[0248] The target terminal considers the received terminal information of the initiating terminal and decides whether to communicate with the initiating terminal or how to communicate with the initiating terminal.

[0249] The indicated information, such as the terminal role of the listening terminal, may be used as a condition to be checked during the ProSe function-enabled terminal communication process on the PC 5 and may be applied together with any possible terminal communication conditions.

[0250] The following is an exemplary introduction to the above method.

[0251] Optional embodiment:

[0252] As shown in Figure 6A, Figure 6A is a schematic diagram of terminal inspection based on ProSe direct communication of the PC5 reference point in an embodiment of the present disclosure. Take the first terminal as UE-1 (announcement terminal), the second terminal as UE-2 (listening terminal), UE-3 (listening terminal), and UE-4 (listening terminal) as an example. UE inspection process when ProSe direct communication is performed through the PC5 reference point. For example, UE-1 acts as the target terminal, and the network or the application layer of UE-1 initiates a service request to request to determine the absolute position of UE-1 with the assistance of a nearby positioning terminal. UE-2, UE-3, and UE-4 are near UE-1, UE-3 does not support ranging / SL positioning services, UE-2 supports ranging / SL positioning services and can be used as a positioning terminal, and UE-4 supports ranging / SL positioning services and can be used as an SL reference terminal. The following steps are included:

[0253] 1. UE-1 sends a ranging / SL positioning announcement message.

[0254] The ranging / SL positioning announcement message may be, for example, a Ranging and Sidelink positioning Announcement message.

[0255] In some embodiments, the announcing terminal (UE-1) may send a ranging / SL positioning announcement message, which may include a discovery message type, a security protection element, RSPP metadata information, and a user ID of the announcing terminal.

[0256] In some embodiments, a destination layer 2 ID (Destination Layer-2 ID) for sending ranging / SL positioning announcement messages may be configured.

[0257] In some embodiments, the source layer 2 identifier (Source Layer-2 ID) for sending the ranging / SL positioning announcement message may be allocated by the announcement terminal (UE-1).

[0258] In some embodiments, if the advertising terminal is authorized as the corresponding terminal role in the RSPP metadata information, the advertising terminal sends a ranging / SL positioning advertising message.

[0259] In some embodiments, if the terminal role of the announcement terminal is a positioning terminal, the ranging / SL positioning announcement message further includes the Public Land Mobile Network (PLMN) information serving the announcement terminal.

[0260] In some embodiments, the user information ID of the advertising terminal is the application layer ID of the advertising terminal.

[0261] In some embodiments, the monitoring terminal may select the advertising terminal according to the information received in step 1. In this embodiment, both UE-2 and UE-4 select UE-1.

[0262] 2. UE-2 and UE-4 send a direct communication request message (RSPP metadata).

[0263] In some embodiments, the direct communication request message may be, for example, a Direct Communication Request message.

[0264] In some embodiments, UE-2 and UE-4 send a direct communication request message to trigger the unicast layer 2 link establishment process. The direct communication request message includes:

[0265] Source user information: the application layer ID of the initiating terminal (eg, the application layer ID of UE-1) and / or the role information of the initiating terminal. For example, the role information may also be included in the RSPP metadata.

[0266] RSPP metadata: metadata of the initiating terminal, for example, the role information of the initiating terminal. Optionally, the role information of the initiating terminal may be included in the RSPP metadata.

[0267] Target terminal information: Set the application layer ID of the target terminal (for example, the application layer ID of UE-2) to the application layer ID of UE-1.

[0268] Proximity Service (ProSe) information: information related to the ProSe identity for requesting to establish a layer 2 link.

[0269] Security information: Information used for security establishment.

[0270] 3. Consider the information of the initiating terminal and decide whether to accept the direct communication request message.

[0271] In some embodiments, after receiving the direct communication request message, the terminal determines whether to accept the direct communication request message based on the user information included in the RSPP metadata or the source user information.

[0272] In this embodiment, after the terminal discovery process based on ranging / SL positioning in Mode A, a unicast layer 2 link is established. The listening terminal in the terminal discovery process acts as the initiating terminal in the unicast layer 2 link establishment process, including the terminal role of the initiating terminal. The target terminal in the unicast layer 2 link establishment process checks whether the role information of the initiating terminal matches the terminal role required for executing the service that triggered the terminal discovery process, and whether it matches the terminal role required for the service that triggered the unicast layer 2 link establishment process.

[0273] In some embodiments, upon receiving direct communication request messages from UE-2 and UE-4, UE-1 decides to accept the direct communication request message from UE-2 because the terminal role of UE-2 matches the terminal role required by UE-1. Furthermore, UE-1 decides not to accept the direct communication request message from UE-4 because the terminal role of UE-4 does not match the terminal role required by UE-1.

[0274] In some embodiments, there may be multiple business requests, and all recorded business requests may be considered, or only business requests mapped to the corresponding discovery process may be considered.

[0275] 4. Security establishment process.

[0276] The security setup between UE-1 and UE-2 is as follows:

[0277] In some embodiments, if security protection is enabled, UE-1 sends the following information to the target terminal:

[0278] If Internet Protocol (IP) communication is used:

[0279] IP address configuration: For IP communication, the IP address configuration value required by the link.

[0280] Link-local IPv6 address: If UE-1 does not support the IPv6 address allocation mechanism, that is, if "IP address configuration" is set to "does not support IPv6 address allocation", a link-local IPv6 address is generated locally.

[0281] Quality of Service (QoS) information: PC5 QoS Flow information. For each PC5 QoS Flow, its PC5 QoS Flow information may include a PC5 QoS Flow Identifier (PFI), corresponding PC5 QoS parameters, and related ProSe identifiers.

[0282] Optionally, PC5 QoS rules.

[0283] In some embodiments, the source layer 2 ID used in the security establishment process may be determined. The destination layer 2 ID is set to the source layer 2 ID in the received direct communication request message.

[0284] In some embodiments, after receiving the security establishment process message, UE-1 may obtain the layer 2 ID of the opposite UE for future communications, so as to transmit signaling and data traffic based on the unicast link.

[0285] 5. UE-1 sends a direct communication acceptance message to UE-2.

[0286] In some embodiments, the direct communication accept message may be, for example, a Direct Communication Accept message.

[0287] In some embodiments, the target terminal that has successfully established a security relationship with UE-2 sends a direct communication acceptance message to UE-2. The direct communication acceptance message includes:

[0288] Source user information: the application layer ID of the terminal that sends the direct communication acceptance message (for example, the application layer ID of UE-1).

[0289] QoS information: PC5 QoS Flow information. For each PC5 QoS Flow, the PC5 QoS Flow information may include PFI, the corresponding PC5 QoS parameters requested by UE-1, and the related ProSe identifier.

[0290] Optionally, PC5 QoS rules.

[0291] Optionally, updated RSPP metadata information of UE-1.

[0292] If Internet Protocol (IP) communication is used:

[0293] IP address configuration: For IP communication, the IP address configuration value required by the link.

[0294] Link-local IPv6 address: If the target terminal does not support the IPv6 address allocation mechanism (that is, if "IP Address Configuration" is set to "Not Supporting IPv6 Address Allocation"), a link-local IPv6 address is generated locally. Furthermore, if UE-1 includes a link-local IPv6 address in the Direct Communication Request message, the link-local IPv6 address generated locally by the target terminal will not conflict with the link-local IPv6 address included in the Direct Communication Request message.

[0295] In some embodiments, if all terminals (the initiating terminal and the target terminal) choose to use the link-local IPv6 address, the duplicate address detection function may be disabled.

[0296] In some embodiments, the ProSe layer of a terminal establishing a PC5 unicast link can pass the PC5 link identifier and related information of the PC5 unicast link allocated to the unicast link to the access stratum (AS). The PC5 unicast link related information includes Layer 2 ID information (e.g., source Layer 2 ID and destination Layer 2 ID). Thus, the AS layer can maintain both the PC5 link identifier and related information of the PC5 unicast link.

[0297] In some embodiments, two terminals may negotiate the configuration of PC5 discontinuous reception (DRX) at the AS layer, and may configure parameter values ​​of PC5 DRX for the source layer 2 ID and the destination layer 2 ID at the AS layer.

[0298] 5a. UE-1 sends a direct communication rejection message to UE-4.

[0299] In some embodiments, the direct communication rejection message may be, for example, a Direct Communication Reject message.

[0300] In some embodiments, UE-1 may send a direct communication rejection message to UE4 to indicate to UE-4 that there is no need to establish a link between UE-1 and UE-4 due to the mismatch of the terminal roles of UE-4.

[0301] 6. Transmit ProSe data on a unicast link.

[0302] In some embodiments, ProSe data is transmitted over the established unicast link as follows:

[0303] Provides the PC5 link identifier, PFI, and ProSe data to the AS layer.

[0304] Optionally, layer 2 identification information (source layer 2 ID and destination layer 2 ID) is provided to the AS layer.

[0305] UE-1 sends ProSe data using a source layer 2 ID (e.g., the layer 2 ID of UE-1 on the unicast link) and a destination layer 2 ID (e.g., the layer 2 ID of the opposite UE on the unicast link).

[0306] As shown in Figure 6B, Figure 6B is a schematic diagram of the terminal inspection process during the layer 2 link modification process in the embodiment of the present disclosure. Take the first terminal as UE-1 and the second terminal as UE-2 as an example. As shown in Figure 6B, this is the layer 2 link modification process of the unicast link, for example, updating the RSPP metadata at both ends of the link. For another example, UE-1 supports ranging / SL positioning services and serves as the target terminal. UE-2 supports ranging / SL positioning services and serves as the positioning terminal. A link is established between UE-1 and UE-2, which is triggered by a service request from the network or the application layer of UE-1, requesting to determine the absolute position of UE-1 with the assistance of a nearby positioning terminal. Due to changes in the UE-2 service protocol, UE-2 is no longer configured as a positioning terminal.

[0307] 0. Unicast link.

[0308] In some embodiments, a unicast link has been established between UE-1 and UE2.

[0309] 1. The terminal information of UE-2 changes (for example, the role information changes).

[0310] In some embodiments, the ranging / SL positioning layer in UE-2 is configured with updated parameters. For example, UE-2's role information is updated to not act as a positioning terminal, such as updating UE-2's role information to a reference terminal. If UE-2 determines that a PC5 unicast link exists between UE-1 and UE-2, UE-2 may decide to modify the established unicast link with UE-1.

[0311] 2. UE-2 sends a link modification request message (including updated terminal information) to UE-1.

[0312] In some embodiments, the link modification request message may be, for example, a Link Modification Request.

[0313] In some embodiments, UE-2 sends a link modification request message to UE-1 to indicate the change of terminal information on the UE-2 side. The link modification request message includes the updated terminal information of the initiating terminal.

[0314] 3. Check for updated terminal information.

[0315] In some embodiments, UE-1 checks the updated terminal information to determine whether it affects the link between UE-1 and UE-2 and the ongoing service. If the updated terminal information does not affect the link between UE-1 and UE-2 and the service is still ongoing, step 4 is executed. Alternatively, if it is determined based on the updated terminal information that the link between UE-1 and UE-2 is still needed and the service is still ongoing, steps 4b and 4 are executed. Otherwise, steps 4a and 4 are executed.

[0316] 4a. Release the unicast link.

[0317] In some embodiments, based on the updated terminal information, if the link between UE-1 and UE-2 is no longer needed, the link is released. Alternatively, based on the execution situation, the link can be released after the ongoing service is completed, or immediately.

[0318] For example, currently, the only service between UE-1 and UE-2 that requires the terminal role to be a positioning terminal is service, and there is no other ranging / SL positioning service.

[0319] 4b. Modify the unicast link.

[0320] In some embodiments, based on the updated terminal information, it is determined that the link between UE-1 and UE-2 still needs to be used. Optionally, unmatched service data flows may be released and matched service data flows may be added.

[0321] For example, there is currently a service between UE-1 and UE-2 in which the required terminal role is a positioning terminal and a reference terminal. Since UE-2 is updated from a positioning terminal to a reference terminal, the data flow of the ranging / SL positioning service in which the required terminal role is a positioning terminal is deleted and released, and the data flow of the ranging / SL positioning service in which the required terminal role is a reference terminal can be added.

[0322] 4. Accept the link modification.

[0323] In some embodiments, UE-1 may respond with a Link Modification Accept message.

[0324] As shown in Figure 6C, Figure 6C is a schematic diagram of the terminal check process during service data exchange in an embodiment of the present disclosure. For example, the first terminal is UE-1 and the second terminal is UE-2. The terminal check process during service data exchange is shown in Figure 6C. Assume that a link has been established between UE-1 and UE-2. UE-1 and UE-2 can perform ranging / SL positioning services in any role.

[0325] 0. Unicast link.

[0326] In some embodiments, a unicast link has been established between UE-1 and UE2.

[0327] 1. First business data exchange (RSPP metadata).

[0328] In some embodiments, the ranging / SL positioning layer in UE-2 may initiate data exchange between UE-2 and UE-1 and may include RSPP metadata in the first service message or first data packet of the exchange.

[0329] For example, the first service message or the first data packet exchanged may be a service request related to ranging / SL positioning to request location information or a sidelink positioning protocol (SLPP) message, such as an SLPP message for capability exchange. UE-1 or UE-2 may be a target terminal, a positioning terminal, an SL server terminal, an SL reference terminal, or an SL client terminal.

[0330] 2. Check for updated terminal information.

[0331] In some embodiments, UE-1 may check the received information to determine whether the link between UE-1 and UE-2 is valid.

[0332] In some embodiments, if the terminal role of UE-2 in the RSPP metadata received in step 1 matches the terminal role required by the service, step 3 is executed to retain the link and exchange subsequent service data as required.

[0333] In some embodiments, if the terminal role of UE-2 in the RSPP metadata received in step 1 does not match the terminal role required by the service, step 3a is performed, and the link may be released or modified.

[0334] 3. Exchange subsequent business data.

[0335] In some embodiments, the link may be retained and subsequent service data may be exchanged if necessary.

[0336] 3a. Modify or release the unicast link.

[0337] In some embodiments, a link can be released or modified. When there is no other business data exchanged on the link, the link can be released. Otherwise, only the specific business data flow in the link that does not match the terminal role is deleted.

[0338] The embodiments of the present disclosure further provide a device for implementing any of the above methods. For example, a device is provided, which includes units or modules for implementing each step executed by the terminal in any of the above methods.

[0339] FIG7A is a schematic diagram of the structure of a terminal proposed in an embodiment of the present disclosure. As shown in FIG7A , the terminal 7100 may include: at least one of a transceiver module 7101 and a processing module 7102. The terminal 7100 may include:

[0340] The transceiver module 7101 is configured to receive first information sent by a second terminal, where the first information at least includes second terminal information, and the second terminal information is used to describe the second terminal.

[0341] The processing module 7102 is configured to check whether the second terminal information meets the first service requirement, and determine whether to perform an operation related to the link of the first service.

[0342] In some embodiments of the present disclosure, the second terminal information includes at least one of the following:

[0343] Second terminal identification;

[0344] role information of the second terminal;

[0345] RSPP metadata information, wherein the RSPP metadata information includes: role information of the second terminal.

[0346] In some embodiments of the present disclosure, the role information of the second terminal includes any of the following:

[0347] A role information of the second terminal;

[0348] A role information list, wherein the role information list includes: multiple role information of the second terminal.

[0349] In some embodiments of the present disclosure, the first information further includes at least one of the following:

[0350] safety information;

[0351] First business information;

[0352] First terminal information, wherein the first terminal information is used to describe the first terminal;

[0353] RSPP metadata information, wherein the RSPP metadata information includes: role information of the first terminal and / or role information of the second terminal.

[0354] In some embodiments of the present disclosure, the first terminal information includes at least one of the following:

[0355] First terminal identification;

[0356] role information of the first terminal;

[0357] RSPP metadata information, wherein the RSPP metadata information includes: role information of the first terminal.

[0358] In some embodiments of the present disclosure, the role information of the first terminal includes any of the following:

[0359] A role information of the first terminal;

[0360] A role information list, wherein the role information list includes: multiple role information of the first terminal.

[0361] In some embodiments of the present disclosure, the transceiver module 7101 is specifically configured to:

[0362] A direct communication request message sent by the second terminal is received, wherein the direct communication request message is used to trigger establishment of a link between the first terminal and the second terminal, and the direct communication request message includes first information.

[0363] In some embodiments of the present disclosure, the processing module 7102 is specifically configured to:

[0364] The second terminal information meets the first service requirement, and a direct communication acceptance message is sent to the second terminal, where the direct communication acceptance message is used to indicate acceptance of establishing a link between the first terminal and the second terminal.

[0365] In some embodiments of the present disclosure, the processing module 7102 is specifically configured to:

[0366] The second terminal information does not meet the first service requirement, and a direct communication rejection message is sent to the second terminal, where the direct communication rejection message is used to indicate that there is no need to establish a link between the first terminal and the second terminal.

[0367] In some embodiments of the present disclosure, the transceiver module 7101 is further configured to:

[0368] A link modification request message sent by the second terminal is received, wherein the link modification request message is used to request modification of a link between the first terminal and the second terminal, and the link modification request message includes first information.

[0369] In some embodiments of the present disclosure, the processing module 7102 is further configured to:

[0370] The second terminal information meets the first service requirement, and a link modification accept message is sent to the second terminal, wherein the link modification accept message is used to indicate acceptance of modification of the link between the first terminal and the second terminal.

[0371] In some embodiments of the present disclosure, the processing module 7102 is further configured to:

[0372] Release the service data flow that does not match the second terminal information.

[0373] In some embodiments of the present disclosure, the transceiver module 7101 is further configured to:

[0374] A first service message or a first data packet sent by a second terminal is received, wherein the first service message includes first information, or the first data packet includes first information.

[0375] In some embodiments of the present disclosure, the processing module 7102 is further configured to:

[0376] The second terminal information meets the first service requirement, and the link between the first terminal and the second terminal is retained.

[0377] In some embodiments of the present disclosure, the processing module 7102 is further configured to:

[0378] The link between the first terminal and the second terminal is modified to add a service data flow matching the second terminal information to the link.

[0379] In some embodiments of the present disclosure, the processing module 7102 is further configured to:

[0380] The second terminal information does not meet the first service requirement, and the link between the first terminal and the second terminal is released.

[0381] In some embodiments of the present disclosure, the second terminal information satisfies the first service requirement, including at least one of the following:

[0382] The second terminal information in the first information matches the first service;

[0383] The RSPP metadata information in the first information matches the first service;

[0384] The role information of the second terminal in the first information matches the first service; or

[0385] The second terminal information in the first information matches the link used for the first service.

[0386] In some embodiments of the present disclosure, the first service is a proximity service (ProSe), or the first service is a ranging or sidelink (SL) positioning service.

[0387] FIG7B is a schematic diagram of the structure of a terminal proposed in another embodiment of the present disclosure. As shown in FIG7B , the terminal 7200 may include: at least one of a transceiver module 7201 and a processing module 7202. The terminal 7200 may include:

[0388] The transceiver module 7201 is used to send first information to the first terminal, wherein the first information includes at least second terminal information, the second terminal information is used to describe the second terminal, and the first information is used by the first terminal to check whether the second terminal information meets the first service requirement.

[0389] In some embodiments of the present disclosure, the second terminal information includes at least one of the following:

[0390] Second terminal identification;

[0391] role information of the second terminal;

[0392] RSPP metadata information, wherein the RSPP metadata information includes: role information of the second terminal.

[0393] In some embodiments of the present disclosure, the role information of the second terminal includes any of the following:

[0394] A role information of the second terminal;

[0395] A role information list, wherein the role information list includes: multiple role information of the second terminal.

[0396] In some embodiments of the present disclosure, the first information further includes at least one of the following:

[0397] safety information;

[0398] First business information;

[0399] First terminal information, wherein the first terminal information is used to describe the first terminal;

[0400] RSPP metadata information, wherein the RSPP metadata information includes: role information of the first terminal and / or role information of the second terminal.

[0401] In some embodiments of the present disclosure, the first terminal information includes at least one of the following:

[0402] First terminal identification;

[0403] role information of the first terminal;

[0404] RSPP metadata information, wherein the RSPP metadata information includes: role information of the first terminal.

[0405] In some embodiments of the present disclosure, the role information of the first terminal includes any of the following:

[0406] A role information of the first terminal;

[0407] A role information list, wherein the role information list includes: multiple role information of the first terminal.

[0408] In some embodiments of the present disclosure, the transceiver module 7201 is specifically configured to:

[0409] A direct communication request message is sent to the first terminal, where the direct communication request message is used to trigger establishment of a link between the first terminal and the second terminal, and the direct communication request message includes first information.

[0410] In some embodiments of the present disclosure, the transceiver module 7201 is further configured to:

[0411] A direct communication acceptance message sent by the first terminal is received, wherein the direct communication acceptance message is used to indicate acceptance of establishing a link between the first terminal and the second terminal, and information of the second terminal meets the first service requirement.

[0412] In some embodiments of the present disclosure, the transceiver module 7201 is further configured to:

[0413] A direct communication rejection message sent by the first terminal is received, wherein the direct communication rejection message is used to indicate that there is no need to establish a link between the first terminal and the second terminal, and the second terminal information does not meet the first service requirement.

[0414] In some embodiments of the present disclosure, the transceiver module 7201 is further configured to:

[0415] A link modification request message is sent to the first terminal, wherein the link modification request message is used to request modification of a link between the first terminal and the second terminal, and the link modification request message includes first information.

[0416] In some embodiments of the present disclosure, the transceiver module 7201 is further configured to:

[0417] A link modification accept message sent by the first terminal is received, wherein the link modification accept message is used to indicate acceptance of modification of a link between the first terminal and the second terminal, and information of the second terminal meets the first service requirement.

[0418] In some embodiments of the present disclosure, the transceiver module 7201 is further configured to:

[0419] A first service message or a first data packet is sent to the first terminal, wherein the first service message includes first information, or the first data packet includes the first information.

[0420] In some embodiments of the present disclosure, the second terminal information satisfies the first service requirement, including:

[0421] The second terminal information in the first information matches the first service; and / or

[0422] The RSPP metadata information in the first information matches the first service; and / or

[0423] The role information of the second terminal in the first information matches the first service; and / or

[0424] The second terminal information in the first information matches the link used for the first service.

[0425] In some embodiments of the present disclosure, the first service is a proximity service (ProSe), or the first service is a ranging or sidelink (SL) positioning service.

[0426] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, and the transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.

[0427] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

[0428] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0429] In the embodiment of the present disclosure, the processor is a circuit with signal processing capability. In one implementation, the processor can be a circuit with instruction reading and execution capability, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP); in another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit, and the logical relationship of the above hardware circuit is fixed or reconfigurable, such as a hardware circuit implemented by a processor as an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0430] Figure 8A is a schematic diagram of the structure of a communication device proposed in an embodiment of the present disclosure. Communication device 8100 can be a terminal, a network device, a chip, a chip system, or a processor that supports a terminal implementing any of the above methods, or a chip, a chip system, or a processor that supports a network device implementing any of the above methods. Communication device 8100 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0431] As shown in Figure 8A, the communication device 8100 includes one or more processors 8101. The processor 8101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. The communication device 8100 is used to perform any of the above methods.

[0432] In some embodiments, the communication device 8100 further includes one or more memories 8102 for storing instructions. Optionally, all or part of the memories 8102 may be located outside the communication device 8100.

[0433] In some embodiments, the communication device 8100 further includes one or more transceivers 8103. When the communication device 8100 includes one or more transceivers 8103, the transceiver 8103 performs at least one of the communication steps such as sending and / or receiving in the above method, and the processor 8101 performs the other steps.

[0434] In some embodiments, a transceiver may include a receiver and / or a transmitter. The receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0435] In some embodiments, the communication device 8100 may include one or more interface circuits 8104. Optionally, the interface circuit 8104 is connected to the memory 8102. The interface circuit 8104 may be configured to receive signals from the memory 8102 or other devices, and may be configured to send signals to the memory 8102 or other devices. For example, the interface circuit 8104 may read instructions stored in the memory 8102 and send the instructions to the processor 8101.

[0436] The communication device 8100 described in the above embodiments may be a terminal, a network device, or a third entity, but the scope of the communication device 8100 described in the present disclosure is not limited thereto, and the structure of the communication device 8100 may not be limited by FIG. 8A. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: 1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0437] FIG8B is a schematic diagram of the structure of a chip proposed in an embodiment of the present disclosure. If the communication device 8100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 8200 shown in FIG8B , but the present disclosure is not limited thereto.

[0438] The chip 8200 includes one or more processors 8201 , and the chip 8200 is configured to execute any of the above methods.

[0439] In some embodiments, the chip 8200 further includes one or more interface circuits 8202. Optionally, the interface circuit 8202 is connected to the memory 8203. The interface circuit 8202 can be used to receive signals from the memory 8203 or other devices, and can be used to send signals to the memory 8203 or other devices. For example, the interface circuit 8202 can read instructions stored in the memory 8203 and send the instructions to the processor 8201.

[0440] In some embodiments, the interface circuit 8202 performs at least one of the communication steps such as sending and / or receiving in the above method, and the processor 8201 performs the other steps.

[0441] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.

[0442] In some embodiments, the chip 8200 further includes one or more memories 8203 for storing instructions. Alternatively, all or part of the memories 8203 may be outside the chip 8200.

[0443] The present disclosure also proposes a storage medium having instructions stored thereon, which, when executed on the communication device 8100, causes the communication device 8100 to execute any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto, and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto, and may also be a temporary storage medium.

[0444] The present disclosure also provides a program product, which, when executed by the communication device 8100, enables the communication device 8100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0445] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

[0446] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented using software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer programs. When the computer program is loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present disclosure are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer program can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer program can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0447] Those skilled in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0448] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0449] The above description is merely a specific embodiment of the present disclosure, but the scope of protection of the present disclosure is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this disclosure should be included in the scope of protection of the present disclosure. Therefore, the scope of protection of the present disclosure should be based on the scope of protection of the claims.

Claims

1. A terminal inspection method, characterized in that, Executed by a first terminal, the method includes: Receiving first information sent by a second terminal, where the first information at least includes second terminal information for describing the second terminal; Checking whether the second terminal information meets a first service requirement and determining whether to perform an operation related to the link of the first service.

2. The method according to claim 1, characterized in that, The second terminal information includes at least one of the following: Second terminal identifier; Role information of the second terminal; RSPP metadata information, where the RSPP metadata information includes: role information of the second terminal.

3. The method according to claim 2, characterized in that, The role information of the second terminal includes any one of the following: One role information of the second terminal; List of role information, where the list of role information includes: multiple role information of the second terminal.

4. The method according to any one of claims 1-3, characterized in that, The first information further includes at least one of the following: Security information; First service information; First terminal information for describing the first terminal; RSPP metadata information, where the RSPP metadata information includes: role information of the first terminal and / or role information of the second terminal.

5. The method according to claim 4, characterized in that, The first terminal information includes at least one of the following: First terminal identifier; Role information of the first terminal; RSPP metadata information, where the RSPP metadata information includes: role information of the first terminal.

6. The method according to claim 5, characterized in that, The role information of the first terminal includes any one of the following: One role information of the first terminal; List of role information, where the list of role information includes: multiple role information of the first terminal.

7. The method according to any one of claims 1-6, characterized in that, The receiving the first information sent by the second terminal includes: Receiving a direct communication request message sent by the second terminal, where the direct communication request message is used to trigger the establishment of a link between the first terminal and the second terminal, and the direct communication request message includes the first information.

8. The method according to claim 7, characterized in that, The checking whether the second terminal information meets the first service requirement and determining whether to perform an operation related to the link of the first service includes: When the second terminal information meets the first service requirement, sending a direct communication acceptance message to the second terminal, where the direct communication acceptance message is used to indicate acceptance of the establishment of the link between the first terminal and the second terminal.

9. The method according to claim 7, characterized in that, The checking whether the second terminal information meets the first service requirement and determining whether to perform an operation related to the link of the first service includes: When the second terminal information does not meet the first service requirement, sending a direct communication rejection message to the second terminal, where the direct communication rejection message is used to indicate that there is no need to establish a link between the first terminal and the second terminal.

10. The method according to any one of claims 1-9, characterized in that, The receiving the first information sent by the second terminal includes: Receiving a link modification request message sent by the second terminal, where the link modification request message is used to request modification of the link between the first terminal and the second terminal, and the link modification request message includes the first information.

11. The method according to claim 10, wherein, The checking whether the second terminal information meets the first service requirement and determining whether to perform an operation related to the link of the first service includes: The second terminal information meets the first service requirement, and a link modification acceptance message is sent to the second terminal, where the link modification acceptance message is used to indicate acceptance of modifying the link between the first terminal and the second terminal.

12. The method according to any one of claims 10 - 11, wherein, The method further includes: Releasing service data flows that do not match the second terminal information.

13. The method according to any one of claims 1 - 6, wherein, Receiving the first information sent by the second terminal includes: Receiving the first service message or the first data packet sent by the second terminal, where the first service message includes the first information, or the first data packet includes the first information.

14. The method according to claim 13, wherein, Checking whether the second terminal information meets the first service requirement and determining whether to perform operations related to the link of the first service includes: If the second terminal information meets the first service requirement, the link between the first terminal and the second terminal is retained.

15. The method according to any one of claims 10 - 11, 13 - 14, wherein, The method further includes: Modifying the link between the first terminal and the second terminal to add service data flows that match the second terminal information to the link.

16. The method according to claim 10 or 13, wherein, Checking whether the second terminal information meets the first service requirement and determining whether to perform operations related to the link of the first service includes: If the second terminal information does not meet the first service requirement, the link between the first terminal and the second terminal is released.

17. The method according to any one of claims 1 - 16, wherein, The second terminal information meeting the first service requirement includes at least one of the following: The second terminal information in the first information matches the first service; The RSPP metadata information in the first information matches the first service; The role information of the second terminal in the first information matches the first service; or The second terminal information in the first information matches the link for the first service.

18. The method according to any one of claims 1 - 17, wherein, The first service is Proximity Service (ProSe), or the first service is ranging or sidelink (SL) positioning service.

19. A terminal inspection method, wherein, When executed by the second terminal, the method includes: Sending first information to the first terminal, where the first information includes at least second terminal information for describing the second terminal, and the first information is used for the first terminal to check whether the second terminal information meets the first service requirement.

20. The method according to claim 19, wherein, The second terminal information includes at least one of the following: Second terminal identifier; Role information of the second terminal; RSPP metadata information, where the RSPP metadata information includes: role information of the second terminal.

21. The method according to claim 20, wherein, The role information of the second terminal includes any one of the following: One role information of the second terminal; List of role information, where the list of role information includes: multiple role information of the second terminal.

22. The method according to any one of claims 19 - 21, characterized in that, The first information further includes at least one of the following: Security information; First service information; First terminal information for describing the first terminal; RSPP metadata information, where the RSPP metadata information includes: role information of the first terminal and / or role information of the second terminal.

23. The method according to claim 22, characterized in that, The first terminal information includes at least one of the following: First terminal identifier; Role information of the first terminal; RSPP metadata information, where the RSPP metadata information includes: role information of a first terminal.

24. The method according to claim 23, characterized in that, The role information of the first terminal includes any one of the following: One role information of the first terminal; A list of role information, where the list of role information includes: multiple role information of the first terminal.

25. The method according to any one of claims 19 - 24, characterized in that, Sending the first information to the first terminal includes: Sending a direct communication request message to the first terminal, where the direct communication request message is used to trigger the establishment of a link between the first terminal and the second terminal, and the direct communication request message includes the first information.

26. The method according to claim 25, characterized in that, The method further includes: Receiving a direct communication acceptance message sent by the first terminal, where the direct communication acceptance message is used to indicate acceptance of the establishment of a link between the first terminal and the second terminal, and the second terminal information meets the first service requirement.

27. The method according to claim 25, characterized in that, The method further includes: Receiving a direct communication rejection message sent by the first terminal, where the direct communication rejection message is used to indicate that there is no need to establish a link between the first terminal and the second terminal, and the second terminal information does not meet the first service requirement.

28. The method according to any one of claims 19 - 26, characterized in that, Sending the first information to the first terminal includes: Sending a link modification request message to the first terminal, where the link modification request message is used to request modification of the link between the first terminal and the second terminal, and the link modification request message includes the first information.

29. The method according to claim 28, characterized in that, The method further includes: Receiving a link modification acceptance message sent by the first terminal, where the link modification acceptance message is used to indicate acceptance of the modification of the link between the first terminal and the second terminal, and the second terminal information meets the first service requirement.

30. The method according to any one of claims 19 - 24, characterized in that, The method further includes: Sending a first service message or a first data packet to the first terminal, where the first service message includes the first information, or the first data packet includes the first information.

31. The method according to any one of claims 19 - 30, characterized in that, The second terminal information meets the first service requirement, including: The second terminal information in the first information matches the first service; and / or The RSPP metadata information in the first information matches the first service; and / or The role information of the second terminal in the first information matches the first service; and / or The second terminal information in the first information matches the link for the first service.

32. The method according to any one of claims 19 - 31, characterized in that, The first service is Proximity Service (ProSe), or the first service is ranging or sidelink (SL) positioning service.

33. A terminal inspection method, characterized in that, The method includes: A second terminal sends first information to a first terminal, where the first information at least includes second terminal information, and the second terminal information is used to describe the second terminal; The first terminal receives the first information and checks whether the second terminal information meets the first service requirement to determine whether to perform an operation related to the link of the first service.

34. A terminal, characterized in that, The terminal includes: A transceiver module, configured to receive the first information sent by the second terminal, where the first information at least includes second terminal information, and the second terminal information is used to describe the second terminal; A processing module, configured to check whether the second terminal information meets a first service requirement and determine whether to perform an operation related to the link of the first service.

35. A terminal, characterized in that, The terminal includes: A transceiver module, configured to send first information to a first terminal, where the first information at least includes second terminal information for describing the second terminal, and the first information is used for the first terminal to check whether the second terminal information meets a first service requirement.

36. A communication device, characterized in that, It includes: One or more processors; Wherein, the processor is configured to execute the terminal checking method according to any one of claims 1-33.

37. A storage medium storing instructions, characterized in that, When the instruction runs on a communication device, the communication device is caused to execute the terminal checking method according to any one of claims 1-33.

38. A communication system, characterized in that, It includes a first terminal and a second terminal, wherein the first terminal is configured to execute the terminal checking method according to any one of claims 1-18, and the second terminal is configured to execute the terminal checking method according to any one of claims 19-32.

Images