Discovery methods and terminals

Abstract

The application relates to a discovery method and a terminal. The discovery method comprises: a near distance service layer of the terminal discovering based on a discovery type of a near distance service. In the application, the near distance service layer of the terminal discovers based on the discovery type of the near distance service, so that the terminal can distinguish different discovery types of the near distance service, and the terminal can discover according to the discovery type.

Description

Technical Field

[0001] This application relates to the field of communications, and more specifically, to a discovery method and terminal. Background Technology

[0002] With the continuous development of 5G applications, new business models have emerged, such as Network Controlled Interactive Services (NCIS). NCIS primarily targets applications such as Augmented Reality (AR), Virtual Reality (VR), and gaming, placing high demands on service quality in terms of speed, latency, packet loss rate, and high-speed encoding / decoding. For example, VR games require speeds of 10Gbps and a packet loss rate not exceeding 10E-4 (i.e., 10...). -4 A session established for NCIS services is an NCIS session. UEs in the same NCIS session can be considered to form an NCIS group, such as a team in a game.

[0003] Within 3GPP, the 5G Proximity Service (ProSe) project allows for the design of near-field communication solutions. ProSe can include NCIS (Non-Computer Integrated Services). For ProSe, terminal discovery is a key consideration. Summary of the Invention

[0004] This application provides a discovery method and terminal, which can perform the discovery process according to the discovery type.

[0005] This application provides a discovery method, including: the terminal's near-field service layer performing discovery based on the discovery type of near-field services.

[0006] This application provides a terminal, including: a discovery unit, used to perform discovery based on the discovery type of near-field service through the near-field service layer.

[0007] This application provides a terminal, including a processor and a memory. The memory stores a computer program, and the processor calls and runs the computer program stored in the memory to enable the terminal to perform the discovery method described above.

[0008] This application provides a chip for implementing the above-described discovery method.

[0009] Specifically, the chip includes a processor for calling and running a computer program from memory, causing a device equipped with the chip to perform the discovery method described above.

[0010] This application provides a computer-readable storage medium for storing a computer program that, when run by a device, causes the device to perform the discovery method described above.

[0011] This application provides a computer program product, including computer program instructions that cause a computer to execute the discovery method described above.

[0012] This application provides a computer program that, when run on a computer, causes the computer to perform the discovery method described above.

[0013] In this embodiment, the terminal's near-field service layer performs discovery based on the discovery type of the near-field service, which enables the terminal to distinguish different discovery types of the near-field service and facilitates the terminal to perform the discovery process according to the discovery type. Attached Figure Description

[0014] Figure 1 This is a schematic diagram of an application scenario according to an embodiment of this application.

[0015] Figure 2 This is an example diagram of a 5G network system architecture.

[0016] Figure 3 This is a schematic flowchart of pattern A.

[0017] Figure 4 This is a schematic flowchart of pattern B.

[0018] Figure 5 This is a schematic flowchart for directly establishing a PC5 connection.

[0019] Figure 6 This is a schematic flowchart of a discovery method according to an embodiment of this application.

[0020] Figure 7 This is a schematic flowchart of Example 1 of a discovery method according to an embodiment of this application.

[0021] Figure 8 This is a schematic flowchart of Example 2 of a discovery method according to an embodiment of this application.

[0022] Figure 9 This is a schematic block diagram of a terminal according to an embodiment of this application.

[0023] Figure 10 This is a schematic block diagram of a terminal according to another embodiment of this application.

[0024] Figure 11 This is a schematic flowchart of a discovery method according to an embodiment of this application.

[0025] Figure 12 This is a schematic block diagram of a network device according to an embodiment of this application.

[0026] Figure 13 This is a schematic block diagram of a communication device according to an embodiment of this application.

[0027] Figure 14 This is a schematic block diagram of a chip according to an embodiment of this application.

[0028] Figure 15 This is a schematic block diagram of a communication system according to an embodiment of this application. Detailed Implementation

[0029] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0030] The technical solutions of this application embodiment can be applied to various communication systems, such as: Global System for Mobile Communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio (NR) system, evolution of NR system, LTE-based access to unlicensed spectrum (LTE-U) system, NR-based access to unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), and Wireless Fidelity (WF). Fidelity (WiFi), fifth-generation communication (5G) systems, or other communication systems.

[0031] Traditional communication systems typically support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication but also, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication. The embodiments of this application can also be applied to these communication systems.

[0032] Optionally, the communication system in this application embodiment can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) network deployment scenario.

[0033] Optionally, the communication system in this application embodiment can be applied to unlicensed spectrum, wherein unlicensed spectrum can also be considered as shared spectrum; or, the communication system in this application embodiment can also be applied to licensed spectrum, wherein licensed spectrum can also be considered as non-shared spectrum.

[0034] This application describes various embodiments in conjunction with network devices and terminal devices. The terminal device may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device, etc.

[0035] Terminal devices can be stations (STAION, ST) in WLANs, cellular phones, cordless phones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, Personal Digital Assistant (PDA) devices, handheld devices with wireless communication capabilities, computing devices or other processing devices connected to a wireless modem, in-vehicle devices, wearable devices, terminal devices in next-generation communication systems such as NR networks, or terminal devices in future evolved Public Land Mobile Network (PLMN) networks, etc.

[0036] In the embodiments of this application, the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; it can also be deployed on water (such as ships); and it can also be deployed in the air (such as airplanes, balloons and satellites).

[0037] In the embodiments of this application, the terminal device may be a mobile phone, 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 care, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, or a wireless terminal device in a smart home, etc.

[0038] By way of example and not limitation, in this embodiment, the terminal device can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. Broadly speaking, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific type of application function and require the use of other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0039] In the embodiments of this application, the network device can be a device for communicating with mobile devices. The network device can be an access point (AP) in WLAN, a base station (BTS) in GSM or CDMA, a base station (NodeB, NB) in WCDMA, an evolved Node B (eNB or eNodeB) in LTE, a relay station or access point, or a vehicle-mounted device, wearable device, or a network device (gNB) in an NR network, or a network device in a future evolved PLMN network or an NTN network, etc.

[0040] By way of example and not limitation, in this embodiment, the network device may have mobility characteristics; for example, the network device may be a mobile device. Optionally, the network device may be a satellite or a balloon station. For example, the satellite may be a low Earth orbit (LEO) satellite, a medium Earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, etc. Optionally, the network device may also be a base station located on land, water, or other similar locations.

[0041] In this embodiment, the network device can provide services to a cell. The terminal device communicates with the network device through the transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell. The cell can be the cell corresponding to the network device (e.g., a base station). The cell can belong to a macro base station or to a base station corresponding to a small cell. The small cell can include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage area and low transmission power, and are suitable for providing high-speed data transmission services.

[0042] Figure 1 An exemplary communication system 100 is shown. The communication system includes one network device 110 and two terminal devices 120. Optionally, the communication system 100 may include multiple network devices 110, and the coverage area of ​​each network device 110 may include other numbers of terminal devices 120; this embodiment of the application does not limit this.

[0043] Optionally, the communication system 100 may also include other network entities such as a Mobility Management Entity (MME) and an Access and Mobility Management Function (AMF), which are not limited in this application embodiment.

[0044] Network equipment can be further divided into access network equipment and core network equipment. That is, the wireless communication system also includes multiple core networks used to communicate with the access network equipment. Access network equipment can be evolved Node Bs (eNBs or e-NodeBs) in Long-Term Evolution (LTE), Next-Generation Radio (NR) (mobile communication system), or Authorized Auxiliary Access Long-Term Evolution (LAA-LTE) systems, such as macro base stations, micro base stations (also called "small base stations"), pico base stations, access points (APs), transmission points (TPs), or new generation Node Bs (gNodeBs).

[0045] It should be understood that devices with communication functions in the network / system of this application embodiment can be referred to as communication devices. Figure 1 Taking the communication system shown as an example, the communication equipment may include network devices and terminal devices with communication functions. The network devices and terminal devices may be specific devices in the embodiments of this application, which will not be described in detail here. The communication equipment may also include other devices in the communication system, such as network controllers, mobility management entities and other network entities, which are not limited in the embodiments of this application.

[0046] It should be understood that the terms "system" and "network" are often used interchangeably in this document. The term "and / or" in this document merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. Furthermore, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0047] It should be understood that the term "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0048] In the description of the embodiments of this application, the term "correspondence" may indicate that there is a direct or indirect correspondence between two things, or that there is an association between two things, or that there is a relationship of instruction and being instructed, configuration and being configured, etc.

[0049] To facilitate understanding of the technical solutions of the embodiments of this application, the relevant technologies of the embodiments of this application are described below. The following relevant technologies are optional solutions and can be combined with the technical solutions of the embodiments of this application in any way, and they all fall within the protection scope of the embodiments of this application.

[0050] Figure 2 An exemplary 5G network system architecture is illustrated. The UE connects to the Access Network (AN) via the Uu radio interface to establish an access layer connection, exchanging access layer messages and radio data. The UE connects to the Access and Mobility Management Function (AMF) via the N1 interface to establish a non-access layer (NAS) connection, exchanging NAS messages. The AMF is responsible for the access and mobility management network elements in the core network, and the Session Management Function (SMF) is responsible for the session management network elements in the core network. In addition to managing the UE's mobility, the AMF is also responsible for forwarding session management-related messages between the UE and the SMF. The Policy Control Function (PCF) is the policy management function in the core network, responsible for formulating policies related to UE mobility management, session management, and charging. The User Plane Function (UPF) is the user plane function in the core network, transmitting data with the external data network via the N6 interface and with the AN (or RAN) via the N3 interface.

[0051] After the UE accesses the 5G network through the Uu interface, it transmits service data through the network. When a service is initiated, the UE's network layer obtains the QoS requirements of the service from the upper layer (such as the operating system or application). The UE converts the QoS requirements of the service into QoS parameters of the Uu interface, and transmits data through the corresponding QoS stream between the UE and the UPF under the control of the SMF.

[0052] Communication between UEs requires establishing a PC5 connection. Before a PC5 connection can be established, the two UEs need to discover each other and know that the other is nearby.

[0053] The following are the discovery processes in several connection establishment modes:

[0054] 1. First, perform the Model A / B discovery process, such as... Figure 3 and Figure 4 As shown, then establish a PC5 connection.

[0055] 2. Step S53 of directly establishing a PC5 connection, as follows: Figure 5 As shown.

[0056] If the UE supports the above multiple connection establishment modes, it is difficult to distinguish between mode A, mode B and step S53 of the connection establishment process.

[0057] See Figure 3 In Mode A, UE-1 is used for announcing, while UE-2, UE-3, UE-4, and UE-5 are used for monitoring. The discovery process in Mode A may include: UE-1 broadcasting or unicasting an announcement message, which may carry the services that UE-1 supports or needs to communicate with in PC5 (S31). Other UEs, such as UE-2, UE-3, UE-4, and UE-5, monitor. If a UE detects a service it needs, it initiates a service connection with UE-1. If UE-1 uses the L2 ID (Layer 2 identifier) ​​for the discovery message, it broadcasts the announcement message; if it uses the L2 ID for the target UE, it unicasts the announcement message.

[0058] See Figure 4In Mode B, UE-1 can be the discoverer, and UE-2, UE-3, UE-4, and UE-5 can be discoverees. The discovery process in Mode B may include: UE-1 broadcasting or unicasting a solicitation message, which may carry its own service requirements (S41). UEs receiving this message, if they find they can support the service requirement, can send a response message to UE-1. For example, UE-2 and UE-3 send response messages to UE-1 (S42a and S42b) to indicate the services they support. UE-1 can then select the desired UE to initiate a service connection. If UE-1 uses the L2 ID for the discovery message, it broadcasts the solicitation message; if it uses the L2 ID for the target UE, it unicasts the solicitation message.

[0059] See Figure 5 The process of directly establishing a PC5 connection can include:

[0060] S51a. UE-2 determines the destination Layer-2 ID for signalling reception.

[0061] S51b.UE-3 determines the target layer 2 identifier used for signaling reception.

[0062] S51c.UE-4 determines the target layer 2 identifier used for signaling reception.

[0063] S51a, S51b, and S51c have no timing restrictions and can be executed independently.

[0064] The ProSe application layer of S52.UE-1 provides application information for PC5 unicast communication.

[0065] S53. UE-1 sends a Direct Communication Request (Broadcast or Unicast). UE-1 can directly broadcast or unicast a direct communication request, which may include its required service information, such as the service capabilities or service requirements it needs. If it is a unicast request, the target UE's identifier may be included in the request. The target UE can respond to the request.

[0066] A) The process of UE-oriented Layer-2 link establishment is as follows:

[0067] S54a. Establishing a security context between UE-1 and UE-2.

[0068] S55a. Direct Communication Accept (Unicast) between UE-1 and UE-2

[0069] S56a. ProSe service data over unicast link between UE-1 and UE-2.

[0070] B) ProSe service-oriented Layer-2 link establishment

[0071] S54b. Establishing a security context between UE-1 and UE-2

[0072] S55b. Direct Communication Accept (Unicast) between UE-1 and UE-2

[0073] S54c. Establish a security context between UE-1 and UE-4.

[0074] S55c. Direct communication acceptance between UE-1 and UE-4 (unicast).

[0075] ProSe service data on the unicast link between S56b.UE-1 and UE-2.

[0076] ProSe service data on the unicast link between S56c.UE-1 and UE-4.

[0077] Figure 6 This is a schematic flowchart of a discovery method 200 according to an embodiment of this application. The method can optionally be applied to... Figure 1 , Figure 2 The system shown is not limited to this. The method includes at least a portion of the following.

[0078] S210. The terminal's near-field service layer performs discovery based on the discovery type of near-field services.

[0079] Optionally, the discovery type of the near-field service includes at least one of the following:

[0080] Pattern A;

[0081] Pattern B;

[0082] Establish a connection directly.

[0083] Specifically, the detailed process for Mode A can be found in [link to relevant documentation]. Figure 3 And its related description. For the specific process of Mode B, please refer to... Figure 4 And related descriptions. For the specific process of establishing a direct connection, please refer to... Figure 5 And its related descriptions.

[0084] Optionally, the Proximity Services (ProSe) layer receives indication information from the application layer of the terminal, which includes the discovery type.

[0085] Optionally, the terminal may include a proximity service layer and an application layer. The application layer can be built on top of the proximity service layer. The application layer can interact with the application server and send information from the application server to the proximity service layer. The proximity service layer can support various proximity services (ProSe).

[0086] For example, the application layer of a terminal can receive indication information from an application server. This indication information may include which discovery type the terminal needs to use for discovery. Different discovery types can be distinguished using different indication information.

[0087] Optionally, the indication information may also include a ProSe ID. For example, the proximal service layer receives indication information including the discovery type and the ProSe ID from the application layer. The ProSe ID can be used to establish a connection and perform data transmission, etc.

[0088] Optionally, the indication information may also include whether the terminal is the initiator or the destination.

[0089] For example, a terminal can negotiate its role information with an application server. For instance, two terminals can negotiate with the application server to determine that one terminal is the initiator and the other is the destination. The application server can then send indication information to both terminals. The indication information sent by the application server to the initiator includes the discovery type and the information that the terminal is the initiator. The indication information sent by the application server to the destination includes the discovery type and the information that the terminal is the destination.

[0090] Optionally, the near-field service layer receives configuration information from core network elements, and the configuration information includes the mapping relationship between the near-field service identifier and the discovery type.

[0091] Optionally, the mapping relationship may include a list of multiple near-field service identifiers and their corresponding discovery types.

[0092] For example, a terminal can obtain the discovery type from configuration information received from the core network. This configuration information can be a UE policy. For instance, the terminal receives configuration information including its discovery type from one or more network elements in the core network. This configuration information may include a mapping between the terminal's ProSe identifier and the discovery type. When an application triggers the near-field service layer to discover near-field services, the terminal can determine the discovery type of the corresponding near-field service or application based on the ProSe identifier. The near-field service or application uses the discovery type for the discovery process. For example, App1-ModelA / B indicates that application APP1 corresponds to mode A or mode B.

[0093] Optionally, the configuration information may also include whether the terminal is the initiator or the destination. For example, the mapping relationship in the configuration information may also include whether the terminal is the initiator or the destination.

[0094] For example, the terminal can also obtain its role information from the core network. For instance, configuration information received by the terminal from one or more network elements of the core network includes the terminal's discovery type and whether the terminal is an initiator or a destination. Specifically, the mapping relationship in the configuration information may include the terminal's discovery type, whether the terminal is an initiator or a destination, and a near-field service identifier. When an application triggers the near-field service layer to discover near-field services, the terminal can determine the discovery type of the corresponding near-field service or application based on the ProSe identifier. The near-field service or application uses the mapping relationship to determine whether the terminal is an initiator or a destination, and performs the discovery process based on the discovery type.

[0095] Optionally, the near-field service layer receives configuration information from the core network elements, which includes a mapping relationship between the near-field service identifier and the Layer 2 identifier of the discovery message.

[0096] For example, the configuration information received by the terminal's ProSe layer from the core network may also include a mapping relationship between the ProSe identifier and the Layer 2 ID of the discovery message. If the terminal is the initiator, it can send the discovery message based on the Layer 2 ID; if the terminal is the destination, it can listen for discovery messages based on the Layer 2 ID.

[0097] For example, in conjunction with the process of obtaining the discovery type described above, the configuration information received by the terminal's ProSe layer from the core network may include the terminal's discovery type, whether the terminal is an initiator or a destination, and the mapping relationship between the ProSe identifier and the Layer2 ID of the discovery message.

[0098] For example, combined with the process of obtaining the discovery type described above, the terminal can obtain its discovery type and whether it is an initiator or a destination from the application server. Furthermore, the terminal can obtain the mapping relationship between the ProSe identifier and the Layer 2 ID of the discovery message from the core network.

[0099] Optionally, the near-field service layer receives configuration information from the core network elements, which includes a mapping relationship between the near-field service identifier and the Layer 2 ID of the discovery message of the discovery type.

[0100] For example, the configuration information received by the terminal's ProSe layer from the core network may also include a mapping relationship between the ProSe identifier and the Layer 2 ID of the discovery message of the discovery type. Discovery messages of different discovery types may have different Layer 2 IDs.

[0101] For example, in conjunction with the process of obtaining the discovery type described above, the configuration information received by the terminal's ProSe layer from the core network may include the terminal's discovery type, whether the terminal is an initiator or a destination, and the mapping relationship between the ProSe identifier and the Layer 2 ID of the discovery message of the discovery type.

[0102] For example, in conjunction with the process of obtaining the discovery type described above, the terminal can obtain its discovery type and whether it is an initiator or a destination from the application server. Furthermore, the terminal can obtain the mapping relationship between the ProSe identifier and the Layer 2 ID of the discovery message for the discovery type from the core network.

[0103] Optionally, before receiving configuration information from the core network element, the terminal indicates the type of configuration information requested to the core network element. In this way, the core network element can return the required configuration information based on the type requested by the terminal. It is not necessary to return all types of configuration information.

[0104] Optionally, the type of configuration information includes at least one of the following:

[0105] Configuration information used for discovery;

[0106] Configuration information for PC5 interface communication;

[0107] Configuration information for relay terminals used in UE-to-network connections;

[0108] Configuration information for remote terminals in UE-to-network communication;

[0109] Configuration information for relay terminals in UE-to-UE communication;

[0110] Configuration information for remote terminals in terminal-to-terminal (UE-to-UE) communication.

[0111] For example, the type of policy the UE sends a request to the PCF, such as configuration information for discovery, configuration information for communication, configuration information as a relay, etc.

[0112] Optionally, the mapping relationship also includes the associated region. Thus, when the terminal is within the associated region, it can use the mapping relationship.

[0113] For example, the configuration information received by the terminal's ProSe layer from the core network may include the terminal's discovery type, whether the terminal is an initiator or a destination, and the mapping relationship between associated areas.

[0114] For example, the configuration information received by the terminal's ProSe layer from the core network may include the terminal's discovery type, whether the terminal is an initiator or a destination, the associated region, and the mapping relationship between ProSe identifiers.

[0115] For example, the configuration information received by the terminal's ProSe layer from the core network may include the terminal's discovery type, whether the terminal is an initiator or a destination, the associated region, and the mapping relationship between the ProSe identifier and the Layer 2 ID of the discovery message.

[0116] For example, the configuration information received by the terminal's ProSe layer from the core network may include the terminal's discovery type, whether the terminal is an initiator or a destination, the associated region, and the mapping relationship between the ProSe identifier and the Layer 2 ID of the discovery message of the discovery type.

[0117] Optionally, the area includes at least one of the following:

[0118] Public terrestrial mobile communication network (PLMN);

[0119] A set of cell IDs;

[0120] A set of Tracking Area Identity (TAI) identifiers;

[0121] The Global Positioning System (GPS) suite.

[0122] Optionally, the core network element includes at least one of the following:

[0123] Policy Control Function (PCF);

[0124] Access and Mobility Management Function (AMF);

[0125] Unified Data Management (UDM).

[0126] Optionally, the near-field service layer of the S210 terminal performs discovery based on the discovery type of the near-field service, which may specifically include: when the terminal is the initiator, the terminal generates signaling corresponding to the discovery type.

[0127] For example, a terminal can determine its discovery type and role information based on indication information or configuration information. Assume two terminals, one an initiator and the other a destination. The initiator can generate signaling corresponding to its discovery type and then send the signaling to the destination. The destination can then monitor the signaling on the logical channel corresponding to its discovery type.

[0128] Optionally, the signaling can be a discovery message or a connection establishment request message.

[0129] For example, in discovery types of mode A or mode B, the signaling generated by the initiator can be a discovery message corresponding to mode A or mode B. The initiator can then send this discovery message to the destination.

[0130] For example, in the discovery type of direct connection establishment, the signaling generated by the initiator can be a connection establishment request message. The initiator can then send this connection establishment request message to the destination.

[0131] Optionally, different discovery types correspond to different signaling formats.

[0132] For example, the signaling corresponding to mode A and mode B can have different formats. Similarly, the signaling corresponding to mode A, mode B, and direct connection establishment can have different formats. Furthermore, the signaling corresponding to mode A and mode B may have the same format, but the signaling corresponding to mode A and mode B may have a different format than the signaling corresponding to direct connection establishment.

[0133] Optionally, the signaling may include the discovery type.

[0134] For example, signaling with the same format can represent different discovery types using different parameter values. For instance, signaling A1 corresponding to mode A and signaling B1 corresponding to mode B have the same format, but different parameter values ​​are used in signaling A1 and signaling B1 to represent different discovery types. As another example, different parameter values ​​are used in the signaling corresponding to mode A, mode B, and direct connection establishment to represent different discovery types.

[0135] Optionally, signaling corresponding to different discovery types is transmitted through different logical channels and uses different layer 2 IDs.

[0136] For example, logical channels of different discovery types can use different layer 2 IDs.

[0137] Optionally, the near-field service layer of the S210 terminal performs discovery based on the discovery type of the near-field service, which may specifically include: when the terminal is the destination, the terminal monitors signaling on the logical channel corresponding to the discovery type.

[0138] In this embodiment, the terminal's near-field service layer performs discovery based on the discovery type of the near-field service. This allows the terminal to distinguish between different discovery types of near-field services, facilitating the discovery process according to the discovery type. For example, the initiating terminal can generate and send signaling according to the acquired discovery type, and the destination terminal can monitor the signaling according to the acquired discovery type. This facilitates rapid and accurate discovery and connection.

[0139] In a specific application example, the UE can obtain the mapping relationship between ProSe and discovery types; then, the initiating UE can select the corresponding discovery type based on the mapping relationship and generate a discovery message. The destination UE can monitor signaling on the logical channel corresponding to the discovery type.

[0140] Example 1, see Figure 7 This example may include the following steps:

[0141] In S71a, the application layer within UE1 can determine which discovery type (or discovery method) to use and send an indication message (or simply indication) to the ProSe layer. This indication message can specify discovery types such as Model A, Model B, or direct connection establishment. For example, Model A, Model B, and direct connection establishment each correspond to different indication messages. It can also be used to distinguish between one indication message for Model A / B and another for direct connection establishment. The application layer also indicates whether UE1 is the initiating UE or the destination UE.

[0142] In S71b, the application layer within UE2 can also send the same indication information to the ProSe layer of UE2. The application layer can also indicate that UE2 is a destination UE or an initiating UE.

[0143] S71a and S71b have no timing restrictions and can be executed independently by the two terminals. Before executing S71a and S71b, the two UEs can negotiate with the application server to determine their discovery type, role information, etc.

[0144] After receiving the indication information, the ProSe layer of S72a and U1 generates signaling corresponding to the indication information (or discovery type). For example, a discovery message or a direct link establishment request message. The corresponding signaling can have different formats and contain different parameters. Optionally, Mode A and Mode B can also be distinguished using the same signaling type. Optionally, Mode A, Mode B, and direct link establishment can be transmitted using different logical channels.

[0145] After receiving the indication information, if the ProSe layer of S72b and UE2 determines that it is the destination UE, it can decide to monitor signaling on the logical channel corresponding to the discovery type.

[0146] S72a and S72b have no timing restrictions and can be executed independently by the two terminals respectively.

[0147] Example 2, see Figure 8 This example may include the following steps:

[0148] S81 and network elements configure UE1 and UE2 respectively. This configuration information can be a UE policy. It can include the mapping relationship (or correspondence) between ProSe IDs and discovery types. This mapping relationship can also be associated with a specific area, so that the UE can only use this mapping relationship within that area. The area can be represented by: PLMN, cell ID set, TAI set, GPS set, etc. Furthermore, if the discovery type only represents one type, then other ProSe IDs not within this mapping relationship can use discovery types other than that one. Optionally, it can also indicate whether the UE is the initiator or the destination.

[0149] After receiving the mapping relationship, S82a and UE1ProSe layer, if they determine that they are the initiating UE, generate signaling corresponding to the ProSeID. This signaling can have different formats and contain different parameters. Optionally, Mode A and Mode B can also be distinguished using the same signaling type. Optionally, Mode A, Mode B, and direct connection establishment can use different logical channels for transmission.

[0150] After receiving the mapping information, if the ProSe layer of S82b and UE2 determines that it is the destination UE, it can decide to monitor signaling on the logical channel corresponding to the discovery type.

[0151] S82a and S82b have no timing restrictions and can be executed independently by the two terminals respectively.

[0152] Figure 9 This is a schematic block diagram of a terminal 400 according to an embodiment of this application. The terminal 400 may include:

[0153] Discovery unit 410 is used to perform discovery based on the discovery type of the near-field service through the near-field service layer.

[0154] Optionally, such as Figure 10 As shown, the terminal also includes:

[0155] The first receiving unit 420 is configured to receive indication information from the application layer of the terminal through the proximity service layer, the indication information including the discovery type.

[0156] Optionally, the indication information may also include whether the terminal is the initiator or the destination.

[0157] Optionally, the terminal also includes:

[0158] The second receiving unit 430 is used to receive configuration information from the core network element through the near-field service layer. The configuration information includes the mapping relationship between the near-field service identifier and the discovery type.

[0159] Optionally, the configuration information may also include whether the terminal is the initiator or the destination. For example, the mapping relationship in the configuration information may also include whether the terminal is the initiator or the destination.

[0160] Optionally, the terminal also includes:

[0161] The third receiving unit 440 is used to receive configuration information from the core network element through the near-field service layer. The configuration information includes the mapping relationship between the near-field service identifier and the Layer 2 identifier of the discovery message.

[0162] Optionally, the terminal also includes:

[0163] The fourth receiving unit 450 is used to receive configuration information from the core network element through the near-field service layer. The configuration information includes the mapping relationship between the near-field service identifier and the Layer 2 ID of the discovery message of the discovery type.

[0164] Optionally, the terminal also includes:

[0165] The instruction unit 460 is used to indicate to the core network element the type of configuration information requested before receiving configuration information from the core network element through the near-field service layer.

[0166] Optionally, the type of configuration information includes at least one of the following:

[0167] Configuration information used for discovery;

[0168] Configuration information for PC5 interface communication;

[0169] Configuration information for relay terminals used in UE-to-network connections;

[0170] Configuration information for remote terminals in UE-to-network communication;

[0171] Configuration information for relay terminals in UE-to-UE communication;

[0172] Configuration information for remote terminals in terminal-to-terminal (UE-to-UE) communication.

[0173] Optionally, the mapping relationship may also include associated regions.

[0174] Optionally, the area includes at least one of the following:

[0175] Public land-based mobile communication network (PLMN);

[0176] Collection of community signs;

[0177] Tracking region identifier (TAI) set;

[0178] The Global Positioning System (GPS) suite.

[0179] Optionally, the core network element includes at least one of the following:

[0180] Policy control function (PCF);

[0181] Access and Mobility Management Function (AMF);

[0182] Unified Data Management (UDM).

[0183] Optionally, the discovery unit is also used to generate signaling corresponding to the discovery type when the terminal is the initiator.

[0184] Optionally, the signaling can be a discovery message or a connection establishment request message.

[0185] Optionally, different discovery types correspond to different signaling formats.

[0186] Optionally, the signaling may include the discovery type.

[0187] Optionally, signaling corresponding to different discovery types is transmitted through different logical channels and uses different layer 2 IDs.

[0188] Optionally, the discovery unit is also used to monitor signaling on the logical channel corresponding to the discovery type when the terminal is the destination.

[0189] Optionally, the discovery type includes at least one of the following:

[0190] Pattern A;

[0191] Pattern B;

[0192] Establish a connection directly.

[0193] The terminal 400 in this embodiment can implement the corresponding functions of the terminal in the foregoing method embodiments. The processes, functions, implementation methods, and beneficial effects of each module (sub-module, unit, or component, etc.) in the terminal 400 can be found in the corresponding descriptions in the above method embodiments, and will not be repeated here. It should be noted that the functions described for each module (sub-module, unit, or component, etc.) in the terminal 400 of this embodiment can be implemented by different modules (sub-modules, units, or components, etc.) or by the same module (sub-module, unit, or component, etc.).

[0194] Figure 11 This is a schematic flowchart of a discovery method 300 according to an embodiment of this application. The method can optionally be applied to... Figure 1 , Figure 2 The system shown is not limited to this. The method includes at least a portion of the following.

[0195] S310. The network device sends the discovery type of the near-field service to the terminal. This enables the terminal's near-field service layer to perform discovery based on the discovery type of the near-field service.

[0196] Optionally, the discovery type of the near-field service includes at least one of the following:

[0197] Pattern A;

[0198] Pattern B;

[0199] Establish a connection directly.

[0200] Optionally, the network device can be an application server. The network device can send indication information to the application layer of the terminal, which includes the discovery type of near-field services.

[0201] Optionally, the terminal may include a proximity service layer and an application layer. The application layer can be built on top of the proximity service layer. The application layer can interact with the application server and send information from the application server to the proximity service layer. The proximity service layer can support various proximity services (ProSe).

[0202] For example, the application layer of a terminal can receive indication information from an application server. This indication information may include which discovery type the terminal needs to use for discovery. Different discovery types can be distinguished using different indication information.

[0203] Optionally, the indication information may also include a ProSe ID. For example, the proximal service layer receives indication information including the discovery type and the ProSe ID from the application layer. The ProSe ID can be used to establish a connection and perform data transmission, etc.

[0204] Optionally, the indication information may also include whether the terminal is the initiator or the destination.

[0205] Optionally, the network device can be a core network element. The network device can send configuration information to the terminal, including the mapping relationship between the near-field service identifier and the discovery type.

[0206] Optionally, the mapping relationship may include a list of multiple near-field service identifiers and their corresponding discovery types.

[0207] For example, a terminal can obtain the discovery type from configuration information received from the core network. This configuration information can be a UE policy. For instance, the terminal receives configuration information including its discovery type from one or more network elements in the core network. This configuration information may include a mapping between the terminal's ProSe identifier and the discovery type. When an application triggers the near-field service layer to discover near-field services, the terminal can determine the discovery type of the corresponding near-field service or application based on the ProSe identifier. The near-field service or application uses the discovery type for the discovery process. For example, App1-ModelA / B indicates that application APP1 corresponds to mode A or mode B.

[0208] Optionally, the configuration information may also include whether the terminal is the initiator or the destination. For example, the mapping relationship may also include whether the terminal is the initiator or the destination.

[0209] For example, the core network can also send the terminal's role information to the terminal. For instance, configuration information received by the terminal from one or more network elements of the core network includes the terminal's discovery type and whether the terminal is an initiator or a destination. Specifically, the mapping relationship in the configuration information may include the terminal's discovery type, whether the terminal is an initiator or a destination, and a near-field service identifier, among other information. When an application triggers the near-field service layer to discover near-field services, the terminal can determine the discovery type of the corresponding near-field service or application based on the ProSe identifier. The near-field service or application uses the mapping relationship to determine whether the terminal is an initiator or a destination, and performs the discovery process based on the discovery type.

[0210] Optionally, the core network element sends configuration information to the terminal's near-field service layer. This configuration information includes the mapping relationship between the near-field service identifier and the Layer 2 identifier of the discovery message.

[0211] Optionally, the core network element sends configuration information to the terminal's near-field service layer. This configuration information includes a mapping relationship between the near-field service identifier and the Layer 2 ID of the discovery message of this discovery type.

[0212] Optionally, before sending configuration information to the terminal's near-field service layer, the core network element receives an indication of the type of configuration information requested by the terminal. This allows the core network element to return the required configuration information based on the type requested by the terminal, without needing to return all types of configuration information.

[0213] Optionally, the type of configuration information includes at least one of the following:

[0214] Configuration information used for discovery;

[0215] Configuration information for PC5 interface communication;

[0216] Configuration information for relay terminals used in UE-to-network connections;

[0217] Configuration information for remote terminals in UE-to-network communication;

[0218] Configuration information for relay terminals in UE-to-UE communication;

[0219] Configuration information for remote terminals in terminal-to-terminal (UE-to-UE) communication.

[0220] For example, the type of policy the UE sends a request to the PCF, such as configuration information for discovery, configuration information for communication, configuration information as a relay, etc.

[0221] Optionally, the mapping relationship also includes the associated region. Thus, when the terminal is within the associated region, it can use the mapping relationship.

[0222] Optionally, the area includes at least one of the following:

[0223] Public terrestrial mobile communication network (PLMN);

[0224] A set of cell IDs;

[0225] A set of Tracking Area Identity (TAI) identifiers;

[0226] The Global Positioning System (GPS) suite.

[0227] Optionally, the core network element includes at least one of the following:

[0228] Policy Control Function (PCF);

[0229] Access and Mobility Management Function (AMF);

[0230] Unified Data Management (UDM).

[0231] For a specific example of the network device executing method 300 in this embodiment, please refer to the relevant description of network devices such as application servers or core network elements in the above method 200. For the sake of brevity, it will not be repeated here.

[0232] Figure 12 This is a schematic block diagram of a network device 500 according to an embodiment of this application. The network device 500 may include:

[0233] The sending unit 510 is used to send the discovery type of near-field services to the terminal. In this way, the terminal's near-field service layer can perform discovery based on the discovery type of near-field services.

[0234] Optionally, the discovery type of the near-field service includes at least one of the following:

[0235] Pattern A;

[0236] Pattern B;

[0237] Establish a connection directly.

[0238] Optionally, the network device can be an application server. The sending unit 510 of the network device can send indication information to the application layer of the terminal, which includes the discovery type of near-field services.

[0239] Optionally, the indication information may also include a ProSe ID. For example, the proximal service layer receives indication information including the discovery type and the ProSe ID from the application layer. The ProSe ID can be used to establish a connection and perform data transmission, etc.

[0240] Optionally, the indication information may also include whether the terminal is the initiator or the destination.

[0241] Optionally, the network device can be a core network element. The transmitting unit 510 of the network device can send configuration information to the terminal, including the mapping relationship between the near-field service identifier and the discovery type.

[0242] Optionally, the mapping relationship may include a list of multiple near-field service identifiers and their corresponding discovery types.

[0243] Optionally, the configuration information may also include whether the terminal is the initiator or the destination. For example, the mapping relationship may also include whether the terminal is the initiator or the destination.

[0244] Optionally, the sending unit 510 of the core network element sends configuration information to the near-field service layer of the terminal. The configuration information includes the mapping relationship between the near-field service identifier and the Layer 2 identifier (Layer 2 ID) of the discovery message.

[0245] Optionally, the sending unit 510 of the core network element sends configuration information to the near-field service layer of the terminal. The configuration information includes the mapping relationship between the near-field service identifier and the Layer 2 ID of the discovery message of the discovery type.

[0246] Optionally, before the core network element's sending unit 510 sends configuration information to the terminal's near-field service layer, the core network element receives an indication of the type of configuration information requested by the terminal. In this way, the core network element can return the configuration information required by the terminal based on the type of configuration information requested. It is not necessary to return all types of configuration information.

[0247] Optionally, the type of configuration information includes at least one of the following:

[0248] Configuration information used for discovery;

[0249] Configuration information for PC5 interface communication;

[0250] Configuration information for relay terminals used in UE-to-network connections;

[0251] Configuration information for remote terminals in UE-to-network communication;

[0252] Configuration information for relay terminals in UE-to-UE communication;

[0253] Configuration information for remote terminals in terminal-to-terminal (UE-to-UE) communication.

[0254] For example, the type of policy the UE sends a request to the PCF, such as configuration information for discovery, configuration information for communication, configuration information as a relay, etc.

[0255] Optionally, the mapping relationship also includes the associated region. Thus, when the terminal is within the associated region, it can use the mapping relationship.

[0256] Optionally, the area includes at least one of the following:

[0257] Public terrestrial mobile communication network (PLMN);

[0258] A set of cell IDs;

[0259] A set of Tracking Area Identity (TAI) identifiers;

[0260] The Global Positioning System (GPS) suite.

[0261] Optionally, the core network element includes at least one of the following:

[0262] Policy Control Function (PCF);

[0263] Access and Mobility Management Function (AMF);

[0264] Unified Data Management (UDM).

[0265] The network device 500 of this application embodiment can realize the corresponding functions of the network device in the foregoing method embodiments. The processes, functions, implementation methods, and beneficial effects of each module (sub-module, unit, or component, etc.) in the network device 500 can be found in the corresponding descriptions in the above method embodiments, and will not be repeated here. It should be noted that the functions described for each module (sub-module, unit, or component, etc.) in the network device 500 of the application embodiment can be implemented by different modules (sub-modules, units, or components, etc.) or by the same module (sub-module, unit, or component, etc.).

[0266] Figure 13 This is a schematic structural diagram of a communication device 600 according to an embodiment of this application. The communication device 600 includes a processor 610, which can call and run computer programs from memory to enable the communication device 600 to implement the methods in the embodiments of this application.

[0267] Optionally, the communication device 600 may further include a memory 620. The processor 610 can retrieve and run computer programs from the memory 620 to enable the communication device 600 to implement the methods described in the embodiments of this application.

[0268] The memory 620 can be a separate device independent of the processor 610, or it can be integrated into the processor 610.

[0269] Optionally, the communication device 600 may also include a transceiver 630, which the processor 610 can control to communicate with other devices. Specifically, it can send information or data to other devices or receive information or data sent by other devices.

[0270] The transceiver 630 may include a transmitter and a receiver. The transceiver 630 may further include antennas, and the number of antennas may be one or more.

[0271] Optionally, the communication device 600 may be a terminal in the embodiments of this application, and the communication device 600 may implement the corresponding processes implemented by the terminal in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0272] Optionally, the communication device 600 may be a network device in the embodiments of this application, and the communication device 600 may implement the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0273] Figure 14 This is a schematic structural diagram of a chip 700 according to an embodiment of this application. The chip 700 includes a processor 710, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0274] Optionally, the chip 700 may further include a memory 720. The processor 710 can retrieve and run computer programs from the memory 720 to implement the methods executed by the terminal in this embodiment.

[0275] The memory 720 can be a separate device independent of the processor 710, or it can be integrated into the processor 710.

[0276] Optionally, the chip 700 may also include an input interface 730. The processor 710 can control the input interface 730 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips.

[0277] Optionally, the chip 700 may also include an output interface 740. The processor 710 can control the output interface 740 to communicate with other devices or chips, specifically, to output information or data to other devices or chips.

[0278] Optionally, the chip can be applied to the terminal in the embodiments of this application, and the chip can implement the corresponding processes implemented by the terminal in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0279] Optionally, the chip can be applied to the network device in the embodiments of this application, and the chip can implement the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0280] The chips used in network equipment and terminal equipment can be the same chip or different chips.

[0281] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0282] The processors mentioned above can be general-purpose processors, digital signal processors (DSPs), field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), or other programmable logic devices, transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processors mentioned above can be microprocessors or any conventional processor.

[0283] The aforementioned memory can be volatile memory or non-volatile memory, or a combination of both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM).

[0284] It should be understood that the above-described memory is exemplary and not a limiting description. For example, the memory in the embodiments of this application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DR RAM), etc. That is to say, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0285] Figure 15 This is a schematic block diagram of a communication system 800 according to an embodiment of this application. The communication system 800 includes at least two terminals, such as terminal 810 and terminal 820.

[0286] Terminals 810 and 820 are used for discovery based on the discovery type of the near-field service through the near-field service layer.

[0287] Terminals 810 and 820 can be used to implement the corresponding functions performed by the terminals in the above method. For the sake of brevity, they will not be described in detail here.

[0288] In one implementation, if terminal 810 is the initiating end, it generates signaling corresponding to the discovery type. Furthermore, terminal 810 can also send this signaling using mode A, mode B, or by directly establishing a connection. If terminal 820 is the destination end, it monitors the signaling on the logical channel corresponding to the discovery type.

[0289] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state drives (SSDs)).

[0290] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0291] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0292] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A discovery method, comprising: The terminal's near-field service layer performs discovery based on the discovery type of near-field services; The method further includes: The near-field service layer receives configuration information from core network elements to enable terminals to distinguish different discovery types of near-field services. The configuration information includes a mapping relationship between the near-field service identifier and the Layer 2 ID of the discovery message; wherein the mapping relationship also includes an associated region; the region includes at least one of the following: Public land-based mobile communication network (PLMN); Collection of community signs; Tracking region identifier (TAI) set; Global Positioning System (GPS) suite; The configuration information also includes whether the terminal is the initiator or the terminal is the destination. The configuration information mentioned above is the UE policy. Before the near-field service layer receives configuration information from the core network element, the terminal indicates to the core network element the type of configuration information requested, so that the core network element can return the configuration information required by the terminal according to the type of configuration information requested by the terminal.

2. The method according to claim 1, wherein, The method further includes: The proximity service layer receives indication information from the application layer of the terminal, and the indication information includes the discovery type.

3. The method according to claim 2, wherein, The indication information also includes whether the terminal is the initiator or the destination.

4. The method according to any one of claims 1 to 3, wherein, The method further includes: The near-field service layer receives configuration information from core network elements, and the configuration information includes a mapping relationship between the near-field service identifier and the discovery type.

5. The method according to any one of claims 1 to 3, wherein, The method further includes: The near-field service layer receives configuration information from the core network elements. The configuration information includes a mapping relationship between the near-field service identifier and the Layer 2 ID of the discovery message of the discovery type.

6. The method according to claim 1, wherein, The types of configuration information include at least one of the following: Configuration information used for discovery; Configuration information for PC5 interface communication; Configuration information for relay terminals used in UE-to-network connections; Configuration information for remote terminals in UE-to-network communication; Configuration information for relay terminals in UE-to-UE communication; Configuration information for remote terminals in terminal-to-terminal (UE-to-UE) communication.

7. The method according to any one of claims 1 to 3, wherein, The core network element includes at least one of the following: Policy control function (PCF); Access and Mobility Management Functions (AMF); Unified Data Management (UDM).

8. The method according to any one of claims 1 to 3, wherein, The terminal's near-field service layer performs discovery based on the near-field service discovery type, including: When the terminal is the initiator, the terminal generates the signaling corresponding to the discovery type.

9. The method according to claim 8, wherein, The signaling is either a discovery message or a connection establishment request message.

10. The method according to claim 8, wherein, Different discovery types correspond to different signaling formats.

11. The method according to claim 8, wherein, The signaling includes the discovery type.

12. The method according to claim 8, wherein, The signaling corresponding to different discovery types is transmitted through different logical channels and uses different layer 2 IDs.

13. The method according to any one of claims 1 to 3, wherein, The terminal's near-field service layer performs discovery based on the near-field service discovery type, including: When the terminal is the destination, the terminal monitors signaling on the logical channel corresponding to the discovery type.

14. The method according to any one of claims 1 to 3, wherein, The discovery type includes at least one of the following: Pattern A; Pattern B; Establish a connection directly.

15. A terminal, comprising: The discovery unit is used to perform discovery based on the discovery type of the proximity service through the proximity service layer; as well as The third receiving unit is configured to receive configuration information from core network elements through the near-field service layer, so that the terminal can distinguish different discovery types of near-field services. The configuration information includes a mapping relationship between the near-field service identifier and the Layer 2 ID of the discovery message; wherein the mapping relationship also includes an associated region; the region includes at least one of the following: Public land-based mobile communication network (PLMN); Collection of community signs; Tracking region identifier (TAI) set; Global Positioning System (GPS) suite; The configuration information also includes whether the terminal is the initiator or the terminal is the destination. The configuration information mentioned above is the UE policy. The terminal also includes: The instruction unit is used to indicate to the core network element the type of configuration information requested before receiving configuration information from the core network element through the near-field service layer, so that the core network element can return the configuration information required by the terminal according to the type of configuration information requested by the terminal.

16. The terminal according to claim 15, wherein, The terminal also includes: The first receiving unit is configured to receive indication information from the application layer of the terminal through the near-field service layer, the indication information including the discovery type.

17. The terminal according to claim 16, wherein, The indication information also includes whether the terminal is the initiator or the destination.

18. The terminal according to any one of claims 15 to 17, wherein, The terminal also includes: The second receiving unit is used to receive configuration information from the core network element through the near-field service layer. The configuration information includes a mapping relationship between the near-field service identifier and the discovery type.

19. The terminal according to any one of claims 15 to 17, wherein the terminal further comprises: The fourth receiving unit is used to receive configuration information from the core network element through the near-field service layer. The configuration information includes a mapping relationship between the near-field service identifier and the Layer 2 ID of the discovery message of the discovery type.

20. The terminal according to claim 15, wherein, The types of configuration information include at least one of the following: Configuration information used for discovery; Configuration information for PC5 interface communication; Configuration information for relay terminals used in UE-to-network connections; Configuration information for remote terminals in UE-to-network communication; Configuration information for relay terminals in UE-to-UE communication; Configuration information for remote terminals in terminal-to-terminal (UE-to-UE) communication.

21. The terminal according to any one of claims 15 to 17, wherein, The core network element includes at least one of the following: Policy control function (PCF); Access and Mobility Management Functions (AMF); Unified Data Management (UDM).

22. The terminal according to any one of claims 15 to 17, wherein, The discovery unit is also used to generate signaling corresponding to the discovery type when the terminal is the initiating terminal.

23. The terminal according to claim 22, wherein, The signaling is either a discovery message or a connection establishment request message.

24. The terminal according to claim 22, wherein, Different discovery types correspond to different signaling formats.

25. The terminal according to claim 22, wherein, The signaling includes the discovery type.

26. The terminal according to claim 22, wherein, The signaling corresponding to different discovery types is transmitted through different logical channels and uses different layer 2 IDs.

27. The terminal according to any one of claims 15 to 17, wherein, The discovery unit is also used to monitor signaling on the logical channel corresponding to the discovery type when the terminal is the destination.

28. The terminal according to any one of claims 15 to 17, wherein, The discovery type includes at least one of the following: Pattern A; Pattern B; Establish a connection directly.

29. A terminal, comprising: A processor and a memory for storing computer programs, the processor for calling and running the computer programs stored in the memory to cause the terminal to perform the method as described in any one of claims 1 to 14.

30. A chip, comprising: A processor for retrieving and running a computer program from memory, causing a device on which the chip is mounted to perform the method as described in any one of claims 1 to 14.

31. A computer-readable storage medium for storing a computer program that, when run by a device, causes the device to perform the method as described in any one of claims 1 to 14.

32. A computer program product comprising computer program instructions that cause a computer to perform the method as described in any one of claims 1 to 14.

Images