CN113132985A

CN113132985A - Communication method and device

Info

Publication number: CN113132985A
Application number: CN201911400828.5A
Authority: CN
Inventors: 邢玮俊; 吴问付
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2019-12-30
Filing date: 2019-12-30
Publication date: 2021-07-16
Also published as: CN113412679B; WO2021136301A1; CN113412679A

Abstract

The application provides a communication method and device, which can solve the problem that proximity service cannot be carried out due to the fact that release parameters and monitoring parameters are not matched due to different network configuration main bodies, so that the reliability of the proximity service is improved, and the communication method and device can be applied to a vehicle networking system, a V2X system, an automatic driving system and an intelligent driving system. The method comprises the following steps: the first network element receives the application identifier from the terminal and sends the application identifier to the second network element. The first network element then receives the discovery parameters from the second network element and sends the discovery parameters to the terminal. Wherein the discovery parameter corresponds to the application identification. Then, the terminal can complete the discovery phase of the ProSe communication and establish the ProSe communication connection according to the discovery parameters.

Description

Communication method and device

Technical Field

The present application relates to the field of communications, and in particular, to a communication method and apparatus.

Background

Direct communication between terminals typically includes a discovery phase and a communication phase. Taking proximity-based services (ProSe) as an example, in the discovery phase, an issuing terminal (AUE) issues a ProSe communication request using an issuing parameter, and a listening terminal (MUE) listens whether the ProSe communication request exists using a listening parameter. If the monitoring parameters are matched with the publishing parameters (which may be collectively referred to as discovery parameters), it is considered that the publishing terminal is closer to the monitoring terminal, and ProSe communication can be established.

However, the publishing parameters are typically configured by a Home Public Land Mobile Network (HPLMN) of the publishing terminal, and the listening parameters are typically configured by the HPLMN of the listening terminal. When the HPLMN of the issuing terminal is different from the HPLMN of the monitoring terminal, or although the issuing terminal and the monitoring terminal belong to the same PLMN, but the configuration network element of the issuing parameter is different from the configuration network element of the monitoring parameter, there may be a phenomenon that the issuing parameter and the monitoring parameter are not matched, which causes a failure in the discovery phase and failure in the proximity service, that is, the reliability of the existing proximity service is poor.

Disclosure of Invention

The embodiment of the application provides a communication method and device, which can solve the problem that proximity service cannot be performed due to mismatching of release parameters and monitoring parameters caused by different network configuration main bodies, so that the reliability of the proximity service is improved.

In order to achieve the purpose, the technical scheme is as follows:

in a first aspect, a method of communication is provided. The communication method comprises the following steps: the first network element receives the application identifier from the terminal and sends the application identifier to the second network element. The first network element then receives the discovery parameters from the second network element and sends the discovery parameters to the terminal. Wherein the discovery parameter corresponds to the application identification.

Based on the communication method provided in the first aspect, the first network element may request the second network element to configure the discovery parameter corresponding to the application identifier according to the application identifier provided by the terminal, for example, the second network element may configure the publishing parameter for the publishing terminal according to the application identifier provided by the publishing terminal, and configure the monitoring parameter for the monitoring terminal according to the same application identifier provided by the monitoring terminal, that is, both the publishing parameter and the monitoring parameter correspond to the same application identifier, which may solve the problem of mismatch between the publishing parameter and the monitoring parameter caused by different network element configurations, and may improve the success rate of the discovery phase, thereby improving the reliability of the proximity service.

In one possible design approach, the terminal may include a publishing terminal, and the discovery parameters may include publishing parameters. The release parameter is used for releasing a proximity service ProSe communication request from a terminal. Accordingly, the communication method provided by the first aspect may further include: the first network element sends one or more of a discovery mode usable by the proximity service ProSe corresponding to the application identification, an identification of the issuing terminal, or a first request indication to the second network element. Wherein the first request indication is used for requesting to issue parameters.

In another possible design approach, the terminal may include a listening terminal, and the discovery parameters may include listening parameters. The monitoring parameter is used for monitoring the proximity service ProSe communication request monitored by the terminal. Accordingly, the communication method provided by the first aspect may further include: the first network element sends one or more of a discovery mode which can be used by proximity service ProSe and corresponds to the application identification, an identification of the monitoring terminal or a second request indication to the second network element. Wherein the second request indication is for requesting listening parameters.

In the embodiment of the application, the issuing terminal may correspond to the monitoring terminal, and the issuing parameter may correspond to the monitoring parameter. Accordingly, the publishing terminal may publish the proximity service ProSe communication request carrying the publishing parameter, and the monitoring terminal may monitor the proximity service ProSe communication request using the monitoring parameter. For example, the listening terminal may determine whether the listening parameters match the publishing parameters carried by the proximity services ProSe communication request. If so, the listening terminal may send a proximity services ProSe response to the publishing terminal. The proximity service ProSe response may carry configuration information for establishing the proximity service ProSe between the issuing terminal and the monitoring terminal, such as configuration information of radio resources. Then, the publishing terminal and the monitoring terminal can realize the communication of the proximity service ProSe based on the configuration information.

Optionally, the communication method provided in the first aspect may further include: and the third network element (e.g. a ProSe network element) sends the corresponding relation between the application identification, the authorized user identification of the terminal in the application corresponding to the application identification and the release parameter to the second network element (e.g. a UDR network element or a UDM network element). This may be further described with reference to fig. 10 or fig. 11, later.

Optionally, the communication method provided in the first aspect may further include: the first network element receives the valid time of the discovery parameter from the second network element and sends the valid time of the discovery parameter to the terminal. In this way, it can be avoided that the proximity service ProSe of one terminal occupies discovery resources (usually predefined by a protocol or pre-configured by a network) for a long time, which results in a situation that other terminals cannot publish or monitor the proximity service ProSe, thereby improving the communication efficiency of the proximity service ProSe.

In a second aspect, a method of communication is provided. The communication method comprises the following steps: the second network element receives the corresponding relation between the application identification and the discovery parameter from the third network element. The second network element then receives the application identification from the first network element and sends discovery parameters to the first network element.

In one possible design method, the communication method provided in the second aspect may further include: the second network element receives from the third network element a discovery pattern usable by the proximity service ProSe corresponding to the application identity and/or an identity of a terminal authorized to use the proximity service ProSe corresponding to the application identity.

In one possible design approach, the terminal may include a publishing terminal, and the discovery parameters may include publishing parameters. The release parameter is used for releasing a proximity service ProSe communication request from a terminal. Accordingly, the communication method provided by the second aspect may further include: the second network element receives one or more items of a discovery mode, an identifier of a release terminal and a first request instruction from the first network element; the first request indication is for requesting issuance of parameters.

In another possible design approach, the terminal may include a listening terminal, and the discovery parameters may include listening parameters. The monitoring parameter is used for monitoring the proximity service ProSe communication request monitored by the terminal. Accordingly, the communication method provided by the second aspect may further include: the second network element receives one or more items of a discovery mode, an identifier of a monitoring terminal and a second request instruction from the first network element; the second request indication is for requesting listening parameters.

Optionally, the communication method provided by the second aspect may further include: the second network element receives the valid time of the discovery parameter from the third network element and sends the valid time of the discovery parameter to the first network element.

The technical effects of the communication method provided by the second aspect may refer to the technical effects of the communication method provided by the first aspect, and are not described herein again.

Optionally, the communication method provided by the second aspect may be further replaced by: the second network element (e.g., UDR network element or UDM network element) may further receive, from a third network element (e.g., ProSe network element), an application identifier, and a correspondence between a user identifier of the terminal in an application corresponding to the application identifier and the publishing parameter. This may be further described with reference to fig. 10 or fig. 11, later.

In a third aspect, a method of communication is provided. The communication method comprises the following steps: the third network element obtains the application identifier. Then, the third network element sends the application identifier and the discovery parameter to the second network element. Wherein the discovery parameter corresponds to the application identification.

Illustratively, the discovery parameters may include a publish parameter and a listen parameter. The publishing parameter is used for publishing the proximity service PreSe request by the terminal, and the monitoring parameter is used for monitoring the proximity service ProSe communication request monitored by the terminal.

Optionally, the communication method provided in the third aspect may further include: and the third network element acquires the identifier of the terminal of the proximity service ProSe corresponding to the authorized application identifier and sends the identifier of the terminal to the second network element.

Optionally, the communication method provided in the third aspect may further include: and the third network element (e.g. a ProSe network element) sends the corresponding relation between the application identification, the authorized user identification of the terminal in the application corresponding to the application identification and the release parameter to the second network element (e.g. a UDR network element or a UDM network element). This may be further described with reference to fig. 10 or fig. 11, later.

Optionally, the communication method provided in the third aspect may further include: the third network element obtains a discovery pattern usable by the proximity service ProSe corresponding to the application identifier and sends the discovery pattern to the second network element.

Further, the communication method provided in the third aspect may further include: the third network element determines the valid time of the discovery parameter and sends the valid time of the discovery parameter to the second network element.

For technical effects of the communication method provided in the third aspect, reference may be made to the technical effects of the communication method provided in the first aspect, and details are not repeated here.

In a fourth aspect, a method of communication is provided. The communication method comprises the following steps: the first network element receives the application identifier from the terminal and sends the application identifier to the second network element. Then, the first network element learns that the second network element does not have the discovery parameter corresponding to the application identifier, and sends the application identifier to the third network element. Thereafter, the first network element receives discovery parameters from the third network element. Wherein the discovery parameter corresponds to the application identification.

Based on the communication method provided in the fourth aspect, the first network element may request, according to the application identifier provided by the terminal, the second network element to configure the discovery parameter corresponding to the application identifier, if there is no discovery parameter corresponding to the application identifier in the second network element, the first network element may send the application identity to the third network element, request the third network element to configure the discovery parameters corresponding to the application identity, for example, the third network element may configure the publishing terminal with publishing parameters according to the application identifier provided by the publishing terminal, and configure the monitoring terminal with monitoring parameters according to the same application identifier provided by the monitoring terminal, that is, the release parameter and the monitoring parameter are both corresponding to the same application identifier, which can solve the problem of mismatching between the release parameter and the monitoring parameter caused by different network element configurations, and can improve the success rate of the discovery phase, thereby improving the reliability of the proximity service.

In one possible design approach, the terminal may include a publishing terminal, and the discovery parameters may include publishing parameters. The release parameter is used for releasing a proximity service ProSe communication request from a terminal. Accordingly, the communication method provided by the fourth aspect may further include: the first network element sends one or more of a discovery mode usable by the proximity service ProSe corresponding to the application identity, an identity of the issuing terminal, or a first request indication to the third network element. Wherein the first request indication is used for requesting to issue parameters.

In another possible design approach, the terminal may include a listening terminal, and the discovery parameters may include listening parameters. The monitoring parameter is used for monitoring the proximity service ProSe communication request monitored by the terminal. Accordingly, the communication method provided by the fourth aspect may further include: the first network element sends one or more of a discovery mode usable by the proximity service ProSe corresponding to the application identification, an identification of the listening terminal, or a second request indication to the third network element. Wherein the second request indication is for requesting listening parameters.

Optionally, the communication method provided in the fourth aspect may further include: the first network element receives the valid time of the discovery parameter from the third network element and transmits the valid time of the discovery parameter to the terminal. In this way, it can be avoided that the proximity service ProSe of one terminal occupies discovery resources (usually predefined by a protocol or pre-configured by a network) for a long time, which results in a situation that other terminals cannot publish or monitor the proximity service ProSe, thereby improving the communication efficiency of the proximity service ProSe.

In a fifth aspect, a method of communication is provided. The communication method comprises the following steps: the third network element receives the application identification from the first network element. Then, the third network element determines a discovery parameter corresponding to the application identifier and sends the discovery parameter to the first network element.

In one possible design approach, the terminal may include a publishing terminal, and the discovery parameters may include publishing parameters. The release parameter is used for releasing a proximity service ProSe communication request from a terminal. Accordingly, the communication method provided by the fifth aspect may further include: the third network element receives, from the first network element, one or more of a discovery pattern usable by the proximity service ProSe corresponding to the application identity, an identity of the issuing terminal, or a first request indication. Wherein the first request indication is used for requesting to issue parameters.

In another possible design approach, the terminal may include a listening terminal, and the discovery parameters may include listening parameters. The monitoring parameter is used for monitoring the proximity service ProSe communication request monitored by the terminal. Accordingly, the communication method provided by the fifth aspect may further include: the third network element receives, from the first network element, one or more of a discovery mode usable by the proximity service ProSe corresponding to the application identity, an identity of the listening terminal, or a second request indication. Wherein the second request indication is for requesting listening parameters.

Optionally, the communication method provided by the fifth aspect may further include: the third network element determines the valid time of the discovery parameter and sends the valid time of the discovery parameter to the first network element.

Technical effects of the communication method provided by the fifth aspect may refer to technical effects of the communication method provided by the fourth aspect, and are not described herein again.

In a sixth aspect, a communications apparatus is provided. The communication device includes: the device comprises a receiving module and a sending module. The receiving module is used for receiving the application identification from the terminal. And the sending module is used for sending the application identifier to the second network element. A receiving module, further configured to receive a discovery parameter from a second network element; the discovery parameter corresponds to an application identification. And the sending module is further used for sending the discovery parameters to the terminal.

In one possible design, the terminal may include a publishing terminal and the discovery parameters may include publishing parameters. The release parameter is used for releasing a proximity service ProSe communication request from a terminal. Accordingly, the sending module is further configured to send, to the second network element, one or more of a discovery pattern usable by the proximity service ProSe corresponding to the application identifier, an identifier of the issuing terminal, or the first request indication. Wherein the first request indication is used for requesting to issue parameters.

In another possible design, the terminal may include a listening terminal and the discovery parameters may include listening parameters. The monitoring parameter is used for monitoring the proximity service ProSe communication request monitored by the terminal. Accordingly, the sending module is further configured to send, to the second network element, one or more of a discovery mode usable by the proximity service ProSe corresponding to the application identifier, an identifier of the listening terminal, or a second request indication. Wherein the second request indication is for requesting listening parameters.

Optionally, the receiving module is further configured to receive an effective time of the discovery parameter from the second network element; and the sending module is further used for sending the effective time of the discovery parameters to the terminal.

Optionally, the communication apparatus provided in the sixth aspect may further include a processing module and a storage module, where the storage module stores programs or instructions. The processing module, when executing the program or the instructions, enables the communication apparatus provided by the sixth aspect to execute the communication method provided by the first aspect.

It should be noted that the communication device provided in the sixth aspect may be a first network element, such as a PCF network element or an AMF network element configured to discover parameters for a terminal, or may be a chip or a chip system disposed in the first network element, which is not limited in this application.

Technical effects of the communication apparatus provided in the sixth aspect may refer to technical effects of the communication method provided in the first aspect, and are not described herein again.

In a seventh aspect, a communications apparatus is provided. The communication device includes: the device comprises a receiving module and a sending module. Wherein, the receiving module is configured to receive the corresponding relationship between the application identifier and the discovery parameter from the third network element. The receiving module is further configured to receive an application identifier from the first network element. A sending module, configured to send the discovery parameter to the first network element.

In one possible design, the receiving module is further configured to receive, from the third network element, a discovery pattern usable by the proximity service ProSe corresponding to the application identity, and/or an identity of a terminal authorized to use the proximity service ProSe corresponding to the application identity.

In one possible design, the terminal may include a publishing terminal and the discovery parameters may include publishing parameters. The release parameter is used for releasing a proximity service ProSe communication request from a terminal. Correspondingly, the receiving module is further configured to receive one or more of the discovery mode, the identifier of the issuing terminal, and the first request indication from the first network element. Wherein the first request indication is used for requesting to issue parameters.

In another possible design, the terminal may include a listening terminal and the discovery parameters may include listening parameters. The monitoring parameter is used for monitoring the proximity service ProSe communication request monitored by the terminal. Correspondingly, the receiving module is further configured to receive one or more of a discovery mode, an identity of the listening terminal, and a second request indication from the first network element. Wherein the second request indication is for requesting listening parameters.

Optionally, the receiving module is further configured to receive an effective time of the discovery parameter from the third network element; and the sending module is further configured to send the validity time of the discovery parameter to the first network element.

Optionally, the communication device provided in the seventh aspect may further include a processing module and a storage module, where the storage module stores programs or instructions. When the processing module executes the program or the instructions, the communication apparatus provided in the seventh aspect is enabled to execute the communication method provided in the second aspect.

It should be noted that the communication device provided in the seventh aspect may be a second network element, such as a UDR network element for storing the discovery parameter, or may be a chip or a chip system provided in the second network element, which is not limited in this application.

Technical effects of the communication apparatus provided in the seventh aspect may refer to technical effects of the communication method provided in the first aspect, and are not described herein again.

In an eighth aspect, a communication device is provided. The communication device includes: a processing module and a transceiver module. The processing module is used for acquiring the application identifier. And the transceiver module is used for sending the application identifier and the discovery parameters to the second network element. Wherein the discovery parameter corresponds to the application identification.

Optionally, the processing module is further configured to obtain an identifier of a terminal that is authorized to use proximity service ProSe corresponding to the application identifier; and the transceiver module is further used for sending the identifier of the terminal to the second network element.

Optionally, the processing module is further configured to obtain a discovery mode usable by a proximity service ProSe corresponding to the application identifier; and the transceiver module is further configured to send the discovery pattern to the second network element.

Further, the processing module is further configured to determine a valid time for discovering the parameter; and the transceiver module is further configured to send the valid time of the discovery parameter to the second network element.

Optionally, the communication device provided by the eighth aspect may further include a storage module, which stores the program or the instructions. When the processing module executes the program or the instructions, the communication apparatus provided by the eighth aspect may be caused to execute the communication method provided by the third aspect.

It should be noted that the communication device provided in the eighth aspect may be a third network element, such as a proximity service function (ProSe function) network element used for generating the discovery parameter, or a PCF network element, an AF network element, an NF network element, and the like having a ProSe network element function, or may be a chip or a chip system disposed in the third network element, which is not limited in this application.

Technical effects of the communication apparatus according to the eighth aspect may refer to technical effects of the communication method according to the first aspect, and are not described herein again.

In a ninth aspect, a communication device is provided. The communication device includes: a processing module and a transceiver module. The receiving and sending module is used for receiving the application identifier from the terminal and sending the application identifier to the second network element. And the processing module is used for acquiring that the second network element does not have the discovery parameter corresponding to the application identifier. The transceiver module further sends the application identifier to the third network element and receives the discovery parameter from the third network element. Wherein the discovery parameter corresponds to the application identification.

In one possible design, the terminal may include a publishing terminal and the discovery parameters may include publishing parameters. The release parameter is used for releasing a proximity service ProSe communication request from a terminal. Accordingly, the transceiver module is further configured to send, to the third network element, one or more of a discovery pattern usable by the proximity service ProSe corresponding to the application identifier, an identifier of the issuing terminal, or the first request indication. Wherein the first request indication is used for requesting to issue parameters.

In another possible design, the terminal may include a listening terminal and the discovery parameters may include listening parameters. The monitoring parameter is used for monitoring the proximity service ProSe communication request monitored by the terminal. Accordingly, the transceiver module is further configured to send, to the third network element, one or more of a discovery mode usable by the proximity service ProSe corresponding to the application identifier, an identifier of the listening terminal, or a second request indication. Wherein the second request indication is for requesting listening parameters.

Optionally, the transceiver module is further configured to receive the valid time of the discovery parameter from the third network element, and send the valid time of the discovery parameter to the terminal.

Optionally, the communication apparatus provided in the ninth aspect may further include a storage module, which stores the program or the instructions. The processing module, when executing the program or the instructions, enables the communication apparatus provided by the ninth aspect to execute the communication method provided by the fourth aspect.

It should be noted that the communication device provided in the ninth aspect may be a first network element, such as a PCF network element or an AMF network element configured to discover parameters for a terminal, or a chip system disposed in the first network element, which is not limited in this application.

Technical effects of the communication apparatus provided by the ninth aspect may refer to technical effects of the communication method provided by the fourth aspect, and are not described herein again.

In a tenth aspect, a communication device is provided. The communication device includes: a processing module and a transceiver module. The transceiver module is configured to receive an application identifier from a first network element. And the processing module is used for determining the discovery parameters corresponding to the application identifications. And the transceiver module is further configured to send the discovery parameter to the first network element.

In one possible design, the terminal may include a publishing terminal and the discovery parameters may include publishing parameters. The release parameter is used for releasing a proximity service ProSe communication request from a terminal. Accordingly, the transceiver module is further configured to receive, from the first network element, one or more of a discovery pattern usable by the proximity service ProSe corresponding to the application identity, an identity of the issuing terminal, or a first request indication. Wherein the first request indication is used for requesting to issue parameters.

In another possible design, the terminal may include a listening terminal and the discovery parameters may include listening parameters. The monitoring parameter is used for monitoring the proximity service ProSe communication request monitored by the terminal. Accordingly, the transceiver module is further configured to receive, from the first network element, one or more of a discovery mode usable by the proximity service ProSe corresponding to the application identity, an identity of the listening terminal, or a second request indication. Wherein the second request indication is for requesting listening parameters.

Optionally, the processing module is further configured to determine a valid time for discovering the parameter; and the transceiver module is further configured to send the validity time of the discovery parameter to the first network element.

Optionally, the communication device provided by the tenth aspect may further include a storage module, which stores the program or the instructions. When the processing module executes the program or the instructions, the communication apparatus provided by the tenth aspect is made to execute the communication method provided by the fifth aspect.

It should be noted that the communication device provided in the tenth aspect may be a third network element, such as a proximity service function (ProSe function) network element used for generating the discovery parameter, or a PCF network element, an AF network element, an NF network element, and the like having a function of the ProSe network element, or may be a chip or a chip system disposed in the third network element, which is not limited in this application.

Technical effects of the communication apparatus provided by the tenth aspect may refer to technical effects of the communication method provided by the fourth aspect, and are not described herein again.

In an eleventh aspect, a communication device is provided. The communication device includes: a processor coupled to a memory, the memory for storing a computer program; the processor is configured to execute the computer program stored in the memory to enable the communication apparatus to execute the communication method described in any one of the possible implementation manners of the first aspect to the fifth aspect.

In one possible design, the communications apparatus provided in the eleventh aspect may further include a transceiver. The transceiver may be a transmit-receive circuit or an input/output port. The transceiver may be used for the communication device to communicate with other communication devices.

In this application, the communication apparatus provided in the eleventh aspect may be a core network element, or a chip system disposed inside the core network element.

The technical effect of the communication apparatus provided in the eleventh aspect may refer to the technical effect of the communication method described in any one of the possible implementation manners of the first aspect to the fifth aspect, and is not described herein again.

In a twelfth aspect, a chip system is provided, which includes a processor and an input/output port, wherein the processor is configured to implement the processing functions of the first to fifth aspects, and the input/output port is configured to implement the transceiving functions of the first to fifth aspects.

In one possible design, the system-on-chip further includes a memory for storing program instructions and data implementing the functions referred to in the first through fifth aspects.

The chip system may be constituted by a chip, or may include a chip and other discrete devices.

In a thirteenth aspect, a communication system is provided. The system comprises a plurality of terminal devices, such as a publishing terminal and a monitoring terminal, and a plurality of core network elements, such as the first network element, the second network element, the third network element, and the like.

In a fourteenth aspect, a computer-readable storage medium is provided, comprising: the computer readable storage medium having stored therein computer instructions; when the computer instructions are run on a computer, the computer is caused to execute the communication method described in any one of the possible implementation manners of the first aspect to the fifth aspect.

In a fifteenth aspect, a computer program product is provided, which comprises a computer program or instructions that, when run on a computer, causes the computer to perform the communication method according to any one of the possible implementations of the first to fifth aspects.

Drawings

Fig. 1 is a first schematic architecture diagram of a communication system according to an embodiment of the present application;

fig. 2 is a schematic structural diagram of a communication system according to an embodiment of the present application;

fig. 3 is a first schematic structural diagram of a communication device according to an embodiment of the present disclosure;

fig. 4 is a first flowchart illustrating a communication method according to an embodiment of the present application;

fig. 5 is a second flowchart illustrating a communication method according to an embodiment of the present application;

fig. 6 is a third schematic flowchart of a communication method according to an embodiment of the present application;

fig. 7 is a fourth flowchart of a communication method according to an embodiment of the present application;

fig. 8 is a fifth flowchart of a communication method according to an embodiment of the present application;

fig. 9 is a sixth schematic flowchart of a communication method according to an embodiment of the present application;

fig. 10 is a seventh flowchart illustrating a communication method according to an embodiment of the present application;

fig. 11 is a flowchart illustrating an eighth communication method according to an embodiment of the present application;

fig. 12 is a second schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 13 is a third schematic structural diagram of a communication device according to an embodiment of the present application.

Detailed Description

The technical solution in the present application will be described below with reference to the accompanying drawings.

The technical solution of the embodiment of the present application may be applied to various communication systems, for example, a vehicle networking communication system, a V2X communication system, an inter-device (D2D) communication system, a Long Term Evolution (LTE) system, a Worldwide Interoperability for Microwave Access (WiMAX) communication system, a fifth generation (5th generation, 5G) mobile communication system, such as a new radio, NR) system, and a future communication system, such as a sixth generation (6th generation, 6G) mobile communication system, and the like.

This application is intended to present various aspects, embodiments or features around a system that may include a number of devices, components, modules, and the like. It is to be understood and appreciated that the various systems may include additional devices, components, modules, etc. and/or may not include all of the devices, components, modules etc. discussed in connection with the figures. Furthermore, a combination of these schemes may also be used.

In addition, in the embodiments of the present application, words such as "exemplarily", "for example", etc. are used for indicating as examples, illustrations or explanations. Any embodiment or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, the term using examples is intended to present concepts in a concrete fashion.

In the embodiments of the present application, "of", "corresponding" and "corresponding" may be sometimes used in combination, and it should be noted that the intended meaning is consistent when the difference is not emphasized.

The network architecture and the service scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not form a limitation on the technical solution provided in the embodiment of the present application, and as a person of ordinary skill in the art knows that along with the evolution of the network architecture and the appearance of a new service scenario, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems.

For the convenience of understanding the embodiments of the present application, a communication system applicable to the embodiments of the present application will be first described in detail by taking the communication system shown in fig. 1 as an example. Fig. 1 is a first schematic structural diagram of a communication system to which the communication method provided in the embodiment of the present application is applied. It should be noted that the solution in the embodiment of the present application may also be applied to other mobile communication systems, and the corresponding names may also be replaced with names of corresponding functions in other mobile communication systems.

As shown in fig. 1, the communication system includes a plurality of core network elements, such as a first network element, a second network element, and a third network element.

The first network element is configured to receive the application identifier from the terminal and send the application identifier to the second network element. And the first network element is also used for receiving the discovery parameters from the second network element and sending the discovery parameters to the terminal. Wherein the discovery parameter corresponds to the application identification.

Correspondingly, the second network element is configured to receive the corresponding relationship between the application identifier and the discovery parameter from the third network element. And the second network element is also used for receiving the application identifier from the first network element and sending the discovery parameters to the first network element.

And, correspondingly, the third network element is configured to obtain the application identity. And the third network element is further used for sending the application identifier and the discovery parameters to the second network element. The discovery parameter corresponds to the application identifier, that is, there is a correspondence between the discovery parameter and the application identifier.

Further, if the second network element does not have the discovery parameter corresponding to the application identifier, for example, the application or service corresponding to the application identifier is a new online application or service, the first network element may also directly request the third network element for the discovery parameter corresponding to the application identifier provided by the terminal.

The first network element is configured to receive the application identifier from the terminal and send the application identifier to the second network element. The first network element is further configured to learn that the second network element does not have the discovery parameter corresponding to the application identifier, and send the application identifier to the third network element. The first network element is further configured to receive discovery parameters from a third network element.

Accordingly, the third network element is configured to receive the application identification from the first network element. And the third network element is further configured to determine a discovery parameter corresponding to the application identifier, and send the discovery parameter to the first network element.

It should be noted that the first network element may also be referred to as a discovery parameter configuring network element, such as a PCF network element and an AMF network element, the second network element may also be referred to as a discovery parameter storing network element, such as a unified data storage function (UDR) network element or a Unified Data Management (UDM) network element, and the third network element may also be referred to as a discovery parameter generating network element, such as an independent ProSe network element, or a network element having a proximity service function, such as a PCF network element, an Application Function (AF) network element, a Network Function (NF) network element, and the like.

Fig. 2 is an example of a communication system that combines the communication system shown in fig. 1 with a 5G core network. As shown in fig. 2, the communication system may include a plurality of User Equipments (UEs), an access network, a core network, a Data Network (DN), and so on. The core network may include an access and mobility management function (AMF) network element, a PCF network element, a UDM network element, a UDR network element, a Session Management Function (SMF) network element, a User Plane Function (UPF) network element, a network open function (NEF), an Application Function (AF) network element, and the like. The network element to which the present application relates is described below with reference to fig. 2.

The UE may be referred to as a terminal (terminal), which may support proximity services, V2X communication, or other services. Such as: the user equipment supports reception or transmission of V2X messages, in which case the terminal may also be referred to as a V2X terminal. Among other things, the V2X messages may include, but are not limited to, vehicle to vehicle (V2V) messages, vehicle to vehicle (V2P) messages, vehicle to network (V2N) messages, vehicle to road infrastructure (V2I) information, vehicle to vehicle collision avoidance messages, entertainment application messages, vehicle to vehicle interactive navigation messages, and the like. Obviously, the terminal shown in fig. 2 may include, but is not limited to, a vehicle-mounted terminal, a mobile phone (mobile phone), a tablet computer or a computer with wireless transceiving function, an intelligent gas station, an intelligent signal lamp, and the like.

An access network may include one or more access network devices (or referred to as access network elements). The access network device is responsible for radio resource management, uplink and downlink data classification and quality of service (QoS) application, and completes signaling processing with a control plane (control plane) network element, and completes data forwarding and other functions with a UPF network element. For example, the access network device may be a base station, a broadband network service gateway (BNG), an aggregation switch, a non-3 GPP access device, or the like. The base stations may include various forms of base stations, such as: macro base stations, micro base stations (also referred to as small stations), relay stations, access points, and the like, which are not specifically limited in this embodiment of the present application. The device for the terminal to access the core network is collectively referred to as an access network device in the text, and will not be described again. For example, the access network device may be an evolved universal terrestrial radio access network (E-UTRAN) device in a 4G network, a next generation radio access network (NG-RAN) device in a 5G network, and so on.

The main functions of the AMF network element comprise a termination point of a control plane of a wireless access network, a termination point of non-access signaling, mobility management, legal monitoring, access authorization/authentication and the like.

UPF network element is used for route and transmission of packet data packet, QoS control of user plane data, accounting information statistics, etc.

The SMF network element is used for session management, Internet Protocol (IP) address allocation and management of the terminal, selection of a termination point that can manage a user plane function, a policy control and charging function interface, downlink data notification, and the like.

And the PCF network element is used for managing network behaviors and providing the terminal, the AMF network element or the SMF network element with relevant parameters of a user policy, an Access and Mobility (AM) management policy and a Session Management (SM) policy respectively. In the V2X communication scenario, the PCF network element provides information such as authentication and policy parameters related to V2X communication to the terminal and the access network device.

And the UDM network element is used for managing the subscription information, providing the subscription information for the related network element and the like.

And the UDR network element is used for providing storage and retrieval services for the PCF network element, storing and retrieving open structured data, storing user information requested by an application function and the like.

The NEF network element connects the core network element and an external application server (application server), and provides services such as authentication and data forwarding when the external application server initiates a service request to the core network.

The AF network element may specifically be an application server corresponding to the application, such as a localized application server. In the embodiment of the present application, a proximity service application server (ProSe APP server) may be regarded as an AF network element.

The DN is a network for transmitting data, such as the internet (internet), etc.

The communication interface between the terminal and the access network equipment is a Uu interface, and the communication interface between the terminal and the terminal is a PC5 interface. The transmission interface of the application layer between the terminal and the transmission data network is a V1 interface, and the transmission interface of the application between the terminals is a V5 interface.

It should be noted that a network formed by operator network elements other than the RAN may be referred to as a core network, and in a 4G network, the network includes network elements such as a Mobility Management Entity (MME), a service gateway (S-GW), a public data network (P-GW), a Home Subscriber Server (HSS), and the like, and in a 5G network, the network includes an AMF network element, an SMF network element, an UPF network element, an UDM network element, and a PCF network element. Fig. 2 is only an example of a 5G network, and does not specifically limit network elements of a core network.

It should be understood that fig. 1 or fig. 2 are simplified schematic diagrams that are merely examples for ease of understanding, and that the communication system may also include other network devices, and/or other terminal devices, which are not shown in fig. 1 or fig. 2.

The above access network device and core network element may also be collectively referred to as a network device. The access network device may include a device located on the network side of the communication system and having a wireless transceiving function, or a chip system that may be provided to the device. Access network devices include, but are not limited to: an Access Point (AP) in a wireless fidelity (WiFi) system, such as a home gateway, a router, a server, a switch, a bridge, etc., an evolved Node B (eNB), a Radio Network Controller (RNC), a Node B (NB), a Base Station Controller (BSC), a Base Transceiver Station (BTS), a home base station (e.g., home evolved Node B, or home Node B, HNB), a Base Band Unit (BBU), a wireless relay Node, a wireless backhaul Node, a transmission point (transmission and reception point, TRP or transmission point, etc.), and may be 5G, such as a new radio interface (NR) system, a TP, a Transmission Point (TP), a group of antennas including one or more antenna panels (antenna panels) in the system, alternatively, the network node may also be a network node forming a gNB or a transmission point, such as a baseband unit (BBU), or a Distributed Unit (DU), a roadside unit (RSU) having a base station function, or the like. Core network elements include, but are not limited to: AMF network elements, SMF network elements, PCF network elements, UPF network elements, NEF network elements, UDM network elements, UDR network elements, AF network elements, NF network elements and the like.

The terminal device is a terminal which is accessed to the communication system and has a wireless transceiving function or a chip system which can be arranged on the terminal. The terminal device can also be called a user equipment, access terminal, subscriber unit, subscriber station, mobile station, remote terminal, mobile device, user terminal, wireless communication device, user agent, or user device. The terminal device in the embodiment of the present application may be a mobile phone (mobile phone), a tablet computer (Pad), a computer with a wireless transceiving function, a Virtual Reality (VR) terminal device, an Augmented Reality (AR) terminal device, a wireless terminal in industrial control (industrial control), a wireless terminal in self driving (self driving), a wireless terminal in remote medical (remote medical), a wireless terminal in smart grid (smart grid), a wireless terminal in transportation safety (transportation safety), a wireless terminal in smart city (smart city), a wireless terminal in smart home (smart home), a vehicle-mounted terminal, an RSU with a terminal function, and the like. The terminal device of the present application may also be an on-board module, an on-board component, an on-board chip, or an on-board unit that is built in the vehicle as one or more components or units, and the vehicle may implement the communication method provided by the present application through the built-in on-board module, the on-board component, the on-board chip, or the on-board unit.

It should be noted that the communication method provided in this embodiment of the present application may be used for communication between a terminal supporting a ProSe service and a core network composed of a first network element, a second network element, and a third network element shown in fig. 1 in a discovery phase of a proximity service.

It should be noted that the ProSe service-supporting terminal mentioned in this application may include a publishing terminal and one or more listening terminals. The issuing terminal is a terminal which requests other terminals to provide proximity services in the same time period, and the monitoring terminal is a terminal which can monitor the ProSe communication request issued by the issuing terminal and provide the proximity services for the issuing terminal in the same time period.

In addition, the communication system architecture applied in the embodiment of the present application is not limited to the system architecture shown in fig. 1 or fig. 2. That is, the system architecture shown in fig. 1 or fig. 2 is only an exemplary architecture diagram, that is, the number of network elements included in the communication system, the type of the network elements, and the names of the network elements are not limited. For example, the communication system shown in fig. 1 or 2 may comprise further functional entities in addition to the network elements shown in fig. 1 or 2. For another example, the network element and the name of each network element in the communication system shown in fig. 1 or fig. 2 are only an example, and the name of each network element in the specific implementation may be other names, which is not specifically limited in this embodiment of the present application. Terminals with communication capability of the PC5 interface can communicate directly with each other via the PC5 interface, regardless of whether the terminals are connected to an access network device. In particular, terminals communicating directly over the PC5 interface may connect with access network devices using the Uu interface and directly with other terminals using the PC5 interface at the same time. For example, while terminals 1 and 4 in fig. 2 communicate directly using the PC5 interface, they may also communicate with the access network equipment using the Uu interface. As another example, while terminal 1 and terminal 2 in fig. 2 communicate directly using the PC5 interface, terminal 1 may also communicate with the access network device using the Uu interface, and terminal 2 does not communicate with the access network device. For another example, terminal 2 and terminal 3 in fig. 2 are only communicating directly using the PC5 interface, and neither is communicating with the access network equipment.

Fig. 3 is a first schematic structural diagram of a communication device that can be used to execute the communication method provided in the embodiment of the present application. The communication device may be any network element shown in fig. 1 or fig. 2, such as a first network element, a second network element, and a third network element, or may be a chip applied to any network element shown in fig. 1 or fig. 2, or other components having functions of any network element. As shown in fig. 3, the communication device 300 may include a processor 301. Optionally, the communication device 300 may also include a transceiver 302 and/or a memory 303. Wherein the processor 301 is coupled to the transceiver 302 and the memory 303, such as may be connected by a communication bus.

The respective constituent elements of the communication device 300 will be specifically described below with reference to fig. 3.

The processor 301 is a control center of the communication apparatus 300, and may be a single processor or a collective term for a plurality of processing elements. For example, the processor 301 is one or more Central Processing Units (CPUs), or may be an Application Specific Integrated Circuit (ASIC), or one or more integrated circuits configured to implement the embodiments of the present application, such as: one or more microprocessors (digital signal processors, DSPs), or one or more Field Programmable Gate Arrays (FPGAs).

Among other things, the processor 301 may perform various functions of the communication device 300 by running or executing software programs stored in the memory 303, as well as invoking data stored in the memory 303. For example, the communication apparatus 300 may perform the functions of the first network element or the second network element or the third network element as shown in any one of fig. 4-9 described below.

In particular implementations, processor 301 may include one or more CPUs such as CPU0 and CPU1 shown in fig. 3 for one embodiment.

In particular implementations, communication device 300 may also include multiple processors, such as processor 301 and processor 304 shown in fig. 3, as an example. Each of these processors may be a single-Core Processor (CPU) or a multi-Core Processor (CPU). A processor herein may refer to one or more communication devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

A transceiver 302 for communication with other communication devices. For example, the communication apparatus 300 may be a first network element or a second network element or a third network element, and the transceiver 302 may be used for communicating with other network elements or with terminal equipment. In addition, the transceiver 302 may include a receiver and a transmitter (not separately shown in fig. 3). Wherein the receiver is configured to implement a receive function and the transmitter is configured to implement a transmit function. The transceiver 302 may be integrated with the processor 301 or may be independent and coupled to the processor 301 through an input/output port (not shown in fig. 3) of the communication device 300, which is not specifically limited in this embodiment.

The memory 303 may be a read-only memory (ROM) or other types of static storage communication devices that can store static information and instructions, a Random Access Memory (RAM) or other types of dynamic storage communication devices that can store information and instructions, an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), a disk storage medium or other magnetic storage communication device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such. The memory 303 may be integrated with the processor 301 or may be independent and coupled to the processor 301 through an input/output port (not shown in fig. 3) of the communication device 300, which is not specifically limited in this embodiment.

The memory 303 is used for storing a software program for executing the present application, and the software program can be controlled by the processor 301 to execute. The specific implementation manner described above may refer to the following method embodiments, which are not described herein again.

It should be noted that the structure of the communication device 300 shown in fig. 3 does not constitute a limitation of the communication device, and an actual communication device may include more or less components than those shown, or combine some components, or arrange different components.

The communication method provided by the embodiment of the present application will be specifically described below with reference to fig. 4 to 11.

Fig. 4 is a first flowchart of a communication method according to an embodiment of the present application. The communication method may be applied to ProSe communication between different network elements shown in fig. 1 or fig. 2, so as to configure discovery parameters for ProSe communication between different terminals in a discovery phase, such as configuring a publishing parameter for a publishing terminal and configuring a monitoring parameter for a monitoring terminal.

The communication method shown in fig. 4 is described in detail below by taking the terminal, and the first network element, the second network element, and the third network element shown in fig. 1 as examples. As shown in fig. 4, the communication method includes the following S401-S406:

s401, the third network element obtains the application identifier.

Exemplarily, the third network element may also be referred to as a discovery parameter generation network element, such as an independent ProSe network element, or other network elements with proximity service function, such as a PCF network element, an AF network element, an NF network element, and the like in a 5G system, and is mainly used for generating a corresponding relationship between the application identifier and the discovery parameter. The embodiment of the present application does not specifically limit the type and number of the network elements of the third network element, and the setting manner between the third network element and other network elements.

Illustratively, the application identifier may be proximity service provided by an AF network element deployed by an operator, such as voice communication, APP ID (APP ID) of video communication, and the like, or may be an application provided by a third party, such as a Content Provider (CP), such as an identifier of WeChat, popular comment, and the like. The provider of the application or service corresponding to the application identifier and the type of the application or service corresponding to the application identifier are not specifically limited in the embodiment of the present application. The third network element may obtain the application identifier by being provided by the AF network element, or being preset in the third network element by an operator.

After obtaining the application identifier, the third network element may determine the discovery parameter corresponding to the application identifier. The discovery parameters may include a publishing parameter and a listening parameter, among others. The publishing parameters, such as ProSe discovery key parameters (e.g., ProSe APP code, ProSe query code, ProSe response code, relay service code, etc.), are used for publishing the proximity service ProSe request by the terminal. Monitoring parameters, such as discovery matching parameters (discovery filter, discovery query filter, discovery response filter, etc.), are used for monitoring the proximity service ProSe communication request of the terminal.

In the embodiment of the application, the issuing terminal corresponds to the monitoring terminal, and the issuing parameter corresponds to the monitoring parameter. Accordingly, the publishing terminal can publish the ProSe communication request carrying the publishing parameters, and the monitoring terminal can monitor the ProSe communication request using the monitoring parameters. For example, the monitoring terminal may determine whether the monitoring parameter matches with the release parameter carried by the ProSe communication request, such as determining whether the ProSe discovery matching parameter matches with the ProSe discovery key parameter. If so, the monitoring terminal can send a ProSe response to the issuing terminal. The ProSe response may carry configuration information used to establish ProSe communication between the issuing terminal and the monitoring terminal, such as configuration information of a wireless resource, Modulation and Coding Scheme (MCS), quality of service (QoS) parameters, an Internet Protocol (IP) address of the monitoring terminal, a Media Access Control (MAC) layer address, and the like. Then, the monitoring terminal can provide proximity service for the issuing terminal based on the configuration information.

Optionally, the communication method shown in fig. 4 may further include: the third network element obtains the identity of the terminal authorized to use the proximity service ProSe corresponding to the application identity and/or the discovery mode usable by the proximity service ProSe corresponding to the application identity. The terminal identifier and the discovery mode may also correspond to the discovery parameters, similar to the application identifier, so that the accuracy of the configured discovery parameters may be further improved, thereby improving the success rate of the discovery phase and the reliability and efficiency of ProSe communication.

Illustratively, a terminal authorized to use the proximity service ProSe corresponding to the application identifier refers to a terminal that supports the proximity service corresponding to the application identifier and has opened the proximity service at an operator or a third party. Correspondingly, the identifier of the terminal authorized to use the proximity service ProSe corresponding to the application identifier refers to an identifier (ProSe APP ID, application layer ID, UE ID, etc.) of the terminal that can be identified by the operator network element or the third-party network element. For example, the identifier may include an identifier of the terminal at a third-party application level, such as a micro signal, a mass-opinion account, an online game account, and the like. For another example, the identifier of the terminal may also include an identifier that is recognizable by a network element of the core network of the operator, such as a General Public Subscriber Identity (GPSI), a subscriber permanent identity (SUPI), a mobile phone number, an International Mobile Subscriber Identity (IMSI) of the terminal, and the like.

In a possible design method, if the identifier of the terminal uses an identifier of a third-party application layer, the terminal further adds an identifier that can be recognized by a core network element of an operator, such as a combination of a micro signal and an International Mobile Subscriber Identity (IMSI), to the request message so that the core network element recognizes the terminal.

In this embodiment, the number of terminals authorized to use the proximity service ProSe corresponding to the application identifier may be multiple, and the types may be multiple. Accordingly, the identifier of the terminal authorized to use the proximity service ProSe corresponding to the application identifier may be multiple, for example, a list of terminal identifiers including multiple different identifiers may be provided. The embodiment of the present application is not specifically limited to a terminal authorized to use proximity service ProSe corresponding to an application identifier and a specific implementation of the identifier.

Illustratively, the discovery pattern usable by the proximity service ProSe corresponding to the application identification may include an open discovery pattern (open discovery) or a restricted discovery pattern (restricted discovery). Wherein the discovery mode may be determined by a provider of the proximity service, such as an AF network element or a third party application server. For a certain proximity service, the public mode means that any terminal can use the proximity service, and the limited mode means that only a specific terminal can use the proximity service. Wherein, the designated terminal refers to a terminal authorized to use the proximity service. Therefore, when the discovery mode is the restricted mode, the third network element further needs to acquire identification information, such as an identification list, of the terminal device authorized to use the proximity service corresponding to the application identifier.

Further, the communication method shown in fig. 4 may further include: the third network element determines the valid time of the discovery parameter and sends the valid time of the discovery parameter to the second network element. In this way, it can be avoided that the proximity service ProSe of one terminal occupies discovery resources (usually predefined by a protocol or pre-configured by a network) for a long time, which results in a situation that other terminals cannot publish or monitor the proximity service ProSe, thereby improving the communication efficiency of the proximity service ProSe. In addition, the operator can control the time that the terminal can use the proximity service by setting the effective time of the discovery parameter, thereby facilitating management such as charging and the like.

S402, the third network element sends the corresponding relation between the application identification and the discovery parameter to the second network element. Accordingly, the second network element receives the correspondence between the application identifier and the discovery parameter from the third network element.

Exemplarily, the second network element may also be referred to as a discovery parameter storage network element, such as a UDR network element or a UDM network element in a 5G system, for uniformly storing the correspondence between the application identifier and the discovery parameter. The corresponding relationship may be multiple, for example, the corresponding relationship between multiple different types of application identifiers and respective discovery parameters generated by the same third network element or multiple different types of third network elements.

In one possible design method, the communication method shown in fig. 4 may further include: the third network element sends the discovery pattern usable by the proximity service ProSe corresponding to the application identity and/or the identity of the terminal authorized to use the proximity service ProSe corresponding to the application identity to the second network element. Accordingly, the second network element receives from the third network element a discovery pattern usable by the proximity service ProSe corresponding to the application identity and/or an identity of a terminal authorized to use the proximity service ProSe corresponding to the application identity.

Exemplarily, when the discovery mode is the restricted mode, the above correspondence relationship further needs to include an identifier of a terminal authorized to use the proximity service ProSe corresponding to the application identifier. It should be understood that when the discovery mode is the public mode, the above correspondence may not include the discovery mode and the identification of the terminal authorized to use the proximity service ProSe corresponding to the application identification.

In a possible design method, the third network element may directly send the corresponding relationship to the second network element, or may send the corresponding relationship to the second network element through other operator network elements, such as a network open function (NEF) network element in a 5G system. This is not particularly limited in the embodiments of the present application.

In this embodiment of the application, after performing S401 and S402, the second network element may collect, from one or more third network elements, corresponding relationships between multiple application identifiers and multiple sets of discovery parameters, and store the corresponding relationships in a storage space of the second network element in a unified manner. In this way, the second network element may configure the discovery parameters for the terminal according to the application identifier provided by the terminal, i.e. perform the following S403-S406.

It should be noted that, the correspondence between the multiple application identifiers and the multiple groups of discovery parameters may also be preconfigured in the second network element. In this case, S401-S402 may not be performed, i.e., S401-S402 are optional steps.

S403, the terminal sends the application identifier to the first network element. Accordingly, the first network element receives the application identification from the terminal.

Exemplarily, the first network element may also be referred to as a discovery parameter configuration network element, such as a PCF network element, an AMF network element, and the like in a 5G system, and is mainly configured to configure the discovery parameter for the terminal according to an application identifier provided by the terminal and a corresponding relationship between the application identifier and the discovery parameter. The embodiment of the present application does not specifically limit the type and number of the network elements of the first network element, and the deployment manner of the first network element and other network elements.

In one possible design approach, the terminal may include a publishing terminal, and the discovery parameters may include publishing parameters. The release parameter is used for releasing a proximity service ProSe communication request from a terminal. Correspondingly, the communication method shown in fig. 4 may further include: the publishing terminal sends one or more of a discovery pattern usable by the proximity service ProSe corresponding to the application identifier, an identifier of the publishing terminal, or a first request indication to the first network element. Accordingly, the first network element receives one or more of the discovery pattern, the identity of the publishing terminal, the first request indication from the publishing terminal. Wherein the first request indication is used for requesting to issue parameters. For example, the first request indication may be an operation indication as follows: command is annouce and ProSe response.

In another possible design approach, the terminal may include a listening terminal, and the discovery parameters may include listening parameters. The monitoring parameter is used for monitoring the proximity service ProSe communication request monitored by the terminal. Correspondingly, the communication method shown in fig. 4 may further include: the monitoring terminal sends one or more of a discovery mode which is usable by the proximity service ProSe and corresponds to the application identification, an identification of the monitoring terminal or a second request indication to the first network element. Accordingly, the first network element receives one or more of the discovery mode, the identity of the listening terminal, the second request indication from the listening terminal. Wherein the second request indication is for requesting listening parameters. For example, the first request indication may be an operation indication as follows: command is monitor and command is ProSe query.

It should be noted that the application identifier, the identifier of the publishing terminal, the discovery mode, and the first request indication may be sent by the publishing terminal to the first network element for multiple times, for example, may be sent in multiple discovery request messages (discovery requests) respectively, or may be sent to the first network element at the same time, for example, may be sent in the same discovery request message. Similarly, the application identifier, the identifier of the monitoring terminal, the discovery mode, and the second request indication may be sent to the first network element by the monitoring terminal for multiple times, for example, they may be sent in multiple discovery request messages respectively, or they may be sent to the first network element at the same time, for example, they may be sent in the same discovery request message. The embodiment of the present application is not specifically limited to the specific implementation manner in which the issuing terminal sends the application identifier, the identifier of the issuing terminal, the discovery mode, and the first request instruction to the first network element, and the implementation manner in which the monitoring terminal sends the application identifier, the identifier of the monitoring terminal, the discovery mode, and the second request instruction to the first network element.

It should be noted that, when the discovery mode is the restricted mode, the terminal needs to send the discovery mode and the identifier of the terminal to the first network element, so that the first network element and a second network element described below determine whether the terminal has the right to use the proximity service corresponding to the application identifier.

In addition, the first request indication and the second request indication may be explicitly indicated, such as the two operation indications, or implicitly indicated, such as distinguished by a message name. Specifically, the discovery request message initiated by the publishing terminal may be named as a publishing request message (publishing request) or a discovery key request message (discovery code request), and the discovery request message initiated by the listening terminal may be named as a listening request message (monitoring request) or a discovery matching parameter request message (discovery filter request). The implementation manners of the first request instruction and the second request instruction in the embodiments of the present application are not particularly limited.

S404, the first network element sends the application identifier to the second network element. Accordingly, the second network element receives the application identification from the first network element.

In one possible design approach, the terminal may include a publishing terminal, and the discovery parameters may include publishing parameters. The release parameter is used for releasing a proximity service ProSe communication request from a terminal. Correspondingly, the communication method shown in fig. 4 may further include: the first network element sends one or more of a discovery mode usable by the proximity service ProSe corresponding to the application identification, an identification of the issuing terminal, or a first request indication to the second network element. Accordingly, the second network element receives one or more of the discovery mode, the identity of the issuing terminal, the first request indication from the first network element. Wherein the first request indication is used for requesting to issue parameters.

In another possible design approach, the terminal may include a listening terminal, and the discovery parameters may include listening parameters. The monitoring parameter is used for monitoring the proximity service ProSe communication request monitored by the terminal. Correspondingly, the communication method shown in fig. 4 may further include: the first network element sends one or more of a discovery mode which can be used by proximity service ProSe and corresponds to the application identification, an identification of the monitoring terminal or a second request indication to the second network element. Correspondingly, the second network element receives one or more items of a discovery mode, an identification of the monitoring terminal and a second request indication from the first network element; the second request indication is for requesting listening parameters. Wherein the second request indication is for requesting listening parameters.

It should be noted that, the implementation manner in which the first network element sends the application identifier, the identifier of the terminal, the discovery mode, the first request instruction, or the second request instruction to the second network element may refer to the implementation manner in which the terminal sends the application identifier, the identifier of the terminal, the discovery mode, the first request instruction, or the second request instruction to the first network element in S403, and details are not described here again.

S405, the second network element sends the discovery parameter to the first network element. Accordingly, the first network element receives discovery parameters from the second network element.

The discovery parameter corresponds to the application identifier, that is, the discovery parameter is determined by the second network element according to the correspondence.

Optionally, the communication method of fig. 4 may further include: the second network element sends the effective time of the discovery parameter to the first network element. Optionally, the first network element receives a validity time of the discovery parameter from the second network element.

Illustratively, S405 may be embodied as: the second network element sends a discovery response message (discovery response) to the first network element. Accordingly, the first network element receives a discovery response message from the second network element. And the discovery response message carries the discovery parameters corresponding to the application identifier. The discovery parameter may include a publishing parameter or a listening parameter, among others. Optionally, the discovery response message may also carry the valid time of the discovery parameter.

It should be noted that, when the discovery mode is the restricted mode, if the terminal does not have the right to use the proximity service corresponding to the application identifier, the second network element may send a service rejection indication to the first network element. Wherein the indication of denial of service may be carried in the discovery response message. In this case, the second network element may not send the publishing parameter to the first network element.

S406, the first network element sends the discovery parameter to the terminal. Accordingly, the terminal receives discovery parameters from the first network element.

Illustratively, S406 may be embodied as: the first network element sends a discovery response message to the terminal. Accordingly, the terminal receives a discovery response message from the first network element. And the discovery response message carries the discovery parameters corresponding to the application identifier. The discovery parameter may include a publishing parameter or a listening parameter, among others. Optionally, the discovery response message may also carry the valid time of the discovery parameter.

It should be noted that, when the discovery mode is the restricted mode, if the terminal does not have the right to use the proximity service corresponding to the application identifier, the first network element may forward the service rejection indication received from the second network element to the terminal. Wherein the indication of denial of service may be carried in the discovery response message.

After S406 is executed, the terminal may complete the discovery phase of ProSe communication according to the discovery parameters, and then, between terminals, such as between the issuing terminal and the monitoring terminal, a ProSe communication connection may be established through signaling interaction, thereby implementing ProSe communication.

The communication method shown in fig. 4 is further described below with reference to specific examples.

Fig. 5 is a first example of the communication method shown in fig. 4. Referring to fig. 4 and 5, the first network element in fig. 4 may include the first PCF network element and the second PCF network element in fig. 5, the second network element in fig. 4 may be a UDR network element or a UDM network element in fig. 5, the third network element in fig. 4 may be a ProSe network element in fig. 5, and the terminal in fig. 4 may include the publishing terminal and the listening terminal in fig. 5.

It should be noted that the UDM network element and the UDR network element may be independent core network elements or may be the same core network element, and the specific implementation manner of the UDM network element and the UDR network element is not limited in this embodiment of the application.

In conjunction with fig. 4, as shown in fig. 5, the above S401 may be implemented as the following S501-S502:

s501, the AF network element sends an application identifier to the ProSe network element. Accordingly, the ProSe network element receives the application identification from the AF network element.

Illustratively, the AF network element may include an operator-deployed core network element, and the application identifier provided by the AF network element may include an APP ID. The AF network element may also be a third party, such as an application server deployed by a content provider, and the application identifier provided by the AF network element may include a third party application identifier. The embodiment of the present application does not limit specific implementation manners, such as providers of the AF network elements, the number of the AF network elements, or types of proximity services provided by the AF network elements.

Optionally, the ProSe network element may further receive, from the AF network element, an identifier of a terminal authorized to use the proximity service corresponding to the application identifier, such as an identifier list of terminals authorized to use the proximity service corresponding to the application identifier.

It should be noted that, if the proximity service corresponding to the application identifier defines a user that can use the application, the corresponding discovery mode is also set to the restricted mode, and the AF network element needs to provide the application identifier for the ProSe network element and the identifier of the terminal authorized to use the proximity service corresponding to the application identifier. If the discovery mode is the restricted mode, the AF further needs to provide, to the ProSe network element, user information authorized to use the application for ProSe communication, such as a user account, an identifier of a terminal bound to the user account, and the like. It should be understood that if the application identifier does not define the usage right for the corresponding proximity service, the AF network element may not send the discovery mode to the ProSe network element. In this case, it can also be understood that the discovery mode, in which the application identifies the corresponding proximity service, defaults to the public mode.

S502, the ProSe network element establishes/modifies/deletes the corresponding relationship between the application identifier and the discovery parameter.

For a specific implementation of the corresponding relationship, reference may be specifically made to relevant contents in S401, and details are not described here.

It should be noted that, if the AF network element has a function of a ProSe network element, for example, the AF network element includes a module or a component having the function of the ProSe network element, the AF network element may also locally obtain an application identifier of a proximity service provided by the AF network element, a discovery parameter, an identifier of a terminal authorized to use the proximity service corresponding to the application identifier, and a discovery mode, and establish the corresponding relationship based on the obtained information, that is, S501 to S502 may be regarded as internal operations executed by the same network element.

In the embodiment of the present application, the correspondence may be newly established, for example, when a new proximity service is online, or may be to be modified, for example, when an existing proximity service is adjusted, or may be to be deleted, for example, when an existing proximity service is offline.

With reference to fig. 4, as shown in fig. 5, the foregoing S402 may be specifically implemented as S503:

s503, the ProSe network element sends the corresponding relation between the application identifier and the discovery parameter to the UDR network element. Accordingly, the UDR receives and stores the correspondence of the application identity and the discovery parameters from the ProSe network element.

Exemplarily, when the discovery mode is the restricted mode, the above correspondence relationship further needs to include an identifier of a terminal authorized to use the proximity service ProSe corresponding to the application identifier. It is easily understood that when the discovery mode is the public mode, the above correspondence may not include the discovery mode and the identification of the terminal authorized to use the proximity service ProSe corresponding to the application identification.

It should be noted that, if the AF network element has the function of a ProSe network element, S503 may be specifically implemented as: and the AF network element sends the corresponding relation between the application identifier and the discovery parameter to the UDR network element. At this time, if the AF network element is a third-party application server, when the AF network element sends the corresponding relationship to the core network UDR network element, the NEF network element needs to be verified, and then the NEF network element forwards the verified corresponding relationship to the UDR network element, so as to ensure security.

In this embodiment of the present application, one UDR network element is usually used, and the one UDR network element may receive and store a plurality of corresponding relationships from a plurality of different types of AF network elements, and the plurality of corresponding relationships may be stored in a corresponding relationship table, where a plurality of entries in the corresponding relationship table correspond to the plurality of corresponding relationships one to one. It should be understood that the UDR network element may also store the above correspondence in other forms besides the correspondence table, for example, the above correspondence may also be stored in a configuration file. The embodiment of the present application does not specifically limit the storage manner of the correspondence.

The following describes the communication method provided in the embodiment of the present application in detail for a publishing terminal and a listening terminal, respectively.

With reference to fig. 4, as shown in fig. 5, for a discovery request initiated by a publishing terminal, such as a first discovery request message, the foregoing S403 to S406 may be specifically implemented as S504 to S509:

s504, the issuing terminal sends the first discovery request message to the first PCF network element via the first AMF network element. Accordingly, the first PCF network element receives the first discovery request message from the publishing terminal via the first AMF network element.

The first discovery request message carries an application identifier, such as an APP ID. Optionally, the first discovery request message may further carry one or more of an identifier of the publishing terminal (an application-level user identifier and/or a user identifier recognizable by a core network element), a discovery mode, and a first request indication. Wherein the first request indication is for requesting issuance of a parameter, such as a ProSe discovery key parameter.

Optionally, the first request indication may be explicitly carried in the first discovery request message, such as an indication field occupying 1 bit (bit) in the first discovery request message. Or, optionally, the first discovery request message may be a discovery key request message, that is, the first request indication may be implicitly carried by using a message name. Alternatively, the first discovery request message may be part of a non-access stratum (NAS) message. For example, the container (container) is sent by the publishing terminal to the first AMF network element as part of a NAS message, and then the first AMF network element forwards the container to the first PCF network element.

It should be noted that, when the discovery mode is the restricted mode, the first discovery request message further needs to carry the discovery mode and the identifier of the publishing terminal, so that the first PCF network element and the UDR network element determine whether the publishing terminal has the right to use the proximity service corresponding to the application identifier.

S505, the first PCF network element interacts with the UDM network element to complete the authentication of the issuing terminal.

Illustratively, the first PCF network element sends an authentication request message to the UDM network element. The authentication request message may carry an identifier of the issuing terminal, a PLMN identifier where the issuing terminal is located, and the like. Correspondingly, the UDM network element sends an authentication response message to the first PCF network element. If the authentication is successful, the authentication response message may carry authorization information, and if the authentication is failed, the authentication response message may carry an authentication failure indication.

Illustratively, if the issuing terminal has the right to use the PC5 for communication in the PLMN corresponding to the PLMN identifier, the UDM network element may send authorization information to the first PCF network element. Otherwise, the UDM network element may send an authentication failure indication to the first PCF network element.

It should be noted that, if the first PCF network element already knows that the issuing terminal has the right to use the PC5 for communication under the current PLMN, the first PCF network element may not initiate the authentication request to the UDM network element. That is, S505 is an optional step.

If the authentication of the issuing terminal is successful, or the first PCF network element has learned that the issuing terminal has the authority to use the PC5 for communication under the current PLMN, the following S506-S509 may be continuously performed. If the ProSe network element is integrated in the first PCF network element, S508 may be performed directly.

S506, the first PCF network element sends the first discovery request message to the UDR network element. Accordingly, the UDR network element receives a first discovery request message from the first PCF network element.

Optionally, when the discovery mode is the restricted mode, the first PCF network element further needs to carry the identifier of the publishing terminal when requesting to publish the discovery parameter of the terminal.

For a specific implementation of the first discovery request message, reference may be made to S504, which is not described herein again.

S507, the UDR network element sends a first discovery response message to the first PCF network element. Accordingly, the first PCF network element receives the first discovery response message from the UDR network element.

The first discovery response message may carry the publishing parameter. The release parameter corresponds to the application identifier carried by the first discovery request message. Wherein, the issue parameter may be a ProSe discovery key parameter. Optionally, the first discovery response message may further carry an expiration date of the publishing parameter.

It should be noted that, when the discovery mode is the restricted mode, the UDR further needs to match, according to the identifier of the publishing terminal carried in the first request message and the identifier of the terminal that is authorized to use the proximity service corresponding to the application identifier and received by the UDR from the AF network element, to verify whether the publishing terminal has the right to use the proximity service corresponding to the application identifier. After verification, the UDR will distribute the publishing parameters to the publishing terminal. Otherwise, the UDR network element feeds back a rejection indication to the first PCF network element to inform the first PCF network element that the authentication of the publishing terminal fails, i.e. the first discovery response message may carry the rejection indication and may not carry the publishing parameters.

Alternatively, the first discovery response message may be a discovery key response message.

In one possible design approach, in S506, the first PCF network element may subscribe to the UDR network element for a discovery parameter creation, update, or deletion request. The request message carries an application identifier. When the UDR network element receives the request for creating, updating or deleting the discovery parameter corresponding to the ProSe network element and the application identifier in S506, the UDR network element may send the corresponding relationship between the discovery parameter and the application identifier created, updated or deleted by the ProSe network element to the first PCF network element in S507. Therefore, the first PCF network element does not need to send the request message to the UDR network element every time the first request message is received, so that the signaling overhead is saved.

S508, the first PCF network element sends the first discovery response message to the publishing terminal via the first AMF network element. Accordingly, the publishing terminal receives the first discovery response message from the first PCF network element via the first AMF network element.

Wherein the first discovery response message carries a publishing parameter, such as a ProSe discovery key parameter. Optionally, the first discovery response message may further carry an expiration date of the publishing parameter. The release parameter is used for releasing the terminal to release the ProSe communication request.

It should be noted that, when the discovery mode is the restricted mode, the content carried by the first discovery response message may refer to S507, which is not described herein again.

And S509, the issuing terminal issues the ProSe communication request according to the issuing parameters.

Illustratively, the publishing terminal may apply for an air interface resource to the access network element, and broadcast the ProSe communication request message on the air interface resource. Wherein, the ProSe communication request message carries the release parameter.

It should be noted that, when the discovery mode is the restricted mode, and when the issuing terminal does not use the right of the proximity service corresponding to the application identifier provided by the issuing terminal, the issuing terminal cannot issue the ProSe communication request.

As shown in fig. 5, for a discovery request initiated by a listening terminal, such as a second discovery request message, the above S403-S406 may be specifically implemented as S510-S515:

s510, the monitoring terminal sends a second discovery request message to the second PCF network element via the second AMF network element. Accordingly, the second PCF network element receives the second discovery request message from the listening terminal via the second AMF network element.

Wherein the second discovery request message carries an application identifier, such as an APP ID. Optionally, the second discovery request message may further carry one or more of an identifier of the listening terminal, a discovery mode, and a second request indication. Wherein the second request indication is for requesting listening parameters, such as ProSe discovery match parameters.

Optionally, the second request indication may be explicitly carried in the second discovery request message. Or, optionally, the second discovery request message may be a discovery matching parameter request message, that is, the second request indication may be implicitly carried by using a message name.

It should be noted that, when the discovery mode is the restricted mode, the second discovery request message also needs to carry the discovery mode and the identifier of the monitoring terminal, so that the second PCF network element and the UDR network element determine whether the monitoring terminal has the right to use the proximity service corresponding to the application identifier.

S511, the second PCF network element interacts with the UDM network element to complete the authentication of the monitoring terminal.

Illustratively, the second PCF network element sends an authentication request message to the UDM network element. The authentication request message may carry an identifier of the monitoring terminal, a PLMN identifier where the monitoring terminal is located, and the like. And correspondingly, the UDM network element sends an authentication response message to the second PCF network element. If the authentication is successful, the authentication response message may carry authorization information, and if the authentication is failed, the authentication response message may carry an authentication failure indication.

Illustratively, if the listening terminal has the right to use the PC5 for communication in the PLMN corresponding to the PLMN identity, the UDM network element may send authorization information to the second PCF network element. Otherwise, the UDM network element may send an authentication failure indication to the second PCF network element.

It should be noted that, if the second PCF network element already knows that the monitoring terminal has the right to use the PC5 for communication under the current PLMN, the second PCF network element may not initiate the authentication request to the UDM network element. That is, S511 is an optional step.

If the authentication of the monitoring terminal is successful, or the second PCF network element has learned that the monitoring terminal has the right to use the PC5 for communication under the current PLMN, the following S512-S515 may be continuously performed. If the ProSe network element is integrated in the second PCF network element, S514 may be directly performed.

S512, the second PCF network element sends a second discovery request message to the UDR network element. Accordingly, the UDR network element receives a second discovery request message from the second PCF network element.

Optionally, when the discovery mode is the restricted mode, the second PCF network element further needs to carry the identifier of the monitoring terminal when requesting the discovery parameter of the monitoring terminal.

S510 may be referred to for a specific implementation manner of the second discovery request message, and details are not described here.

S513, the UDR network element sends a second discovery response message to the second PCF network element. Accordingly, the second PCF network element receives a second discovery response message from the UDR network element.

Wherein the second discovery response message may carry the listening parameter. The monitoring parameter corresponds to the application identifier carried in the second discovery request message. The monitoring parameter may be a ProSe discovery matching parameter.

It should be noted that, when the discovery mode is the restricted mode, the UDR further needs to match the identifier of the monitoring terminal carried in the second request message with the identifier of the terminal authorized to use the proximity service corresponding to the application identifier, which is received by the UDR from the AF network element, so as to verify whether the monitoring terminal has the right to use the proximity service corresponding to the application identifier. After verification, the UDR will allocate the listening parameters to the listening terminal. Otherwise, the UDR network element feeds back a rejection indication to the second PCF network element to inform the second PCF network element that the authentication of the monitoring terminal fails, that is, the second discovery response message may carry the rejection indication and may not carry the monitoring parameters.

Alternatively, the second discovery response message may be a discovery key response message.

In a possible design method, in S512, the second PCF network element may subscribe to a discovery parameter creation, update, or deletion request from the UDR network element, where the request message carries the application identifier. When the UDR network element receives the request for creating, updating or deleting the discovery parameter corresponding to the ProSe network element and the application identifier in S512, the UDR network element may send the correspondence between the application identifier created, updated or deleted by the ProSe network element and the discovery parameter to the second PCF network element in S513. Therefore, the second PCF network element does not need to send the request message to the UDR network element every time the second request message is received, so that the signaling overhead is saved.

S514, the second PCF network element sends a second discovery response message to the listening terminal via the second AMF network element. Accordingly, the listening terminal receives a second discovery response message from the second PCF network element via the second AMF network element.

Wherein the second discovery response message carries the listening parameter. Optionally, the second discovery response message may also carry a validity period of the listening parameter. The monitoring parameter is used for monitoring other terminals, such as the ProSe communication request issued by the issuing terminal.

Optionally, the second discovery response message may be a discovery match parameter response message.

It should be noted that, when the discovery mode is the restricted mode, reference may be made to S513 for the content carried in the second discovery response message, which is not described herein again.

And S515, the monitoring terminal monitors the ProSe communication request according to the monitoring parameters.

For example, the monitoring terminal may apply for an air interface resource to an access network element accessed by the monitoring terminal, and monitor, on the air interface resource, a ProSe communication request message issued by another terminal using a monitoring parameter, such as monitoring a ProSe communication request issued by the above-mentioned issuing terminal. For example, if the monitored parameters are matched with the published parameters, it is considered that the ProSe service request exists, otherwise, it is considered that the ProSe service request does not exist.

It should be noted that, when the discovery mode is the restricted mode and when the monitoring terminal does not use the right of the proximity service corresponding to the application identifier provided by the monitoring terminal, the monitoring terminal cannot monitor ProSe communication requests issued by other terminals.

In addition, the operation steps S510 to S515 for the listening terminal may be executed after or before the operation steps S504 to S509 for the issuing terminal are executed, or may be executed alternately in the same period of time, which is not specifically limited in the embodiment of the present application.

Fig. 6 is a second example of the communication method shown in fig. 4. Referring to fig. 4 and 6, the first network element in fig. 4 may include the first AMF network element and the second AMF network element in fig. 6, the second network element in fig. 4 may be a UDR network element in fig. 6, the third network element in fig. 4 may be a ProSe network element in fig. 6, and the terminal in fig. 4 may include the publishing terminal and the listening terminal in fig. 6.

In conjunction with fig. 4, as shown in fig. 6, the above-mentioned S401-S402 can be implemented as the following S601-S603:

s601, the AF network element sends an application identifier to the ProSe network element. Accordingly, the ProSe network element receives the application identification from the AF network element.

S602, the ProSe network element establishes/modifies/deletes the corresponding relationship between the application identifier and the discovery parameter.

S603, the ProSe network element sends the corresponding relation between the application identifier and the discovery parameter to the UDR network element. Accordingly, the UDR receives and stores the correspondence of the application identity and the discovery parameters from the ProSe network element.

For specific implementation of S601-S603, reference may be made to S501-S503, respectively, and details are not repeated here.

The communication method shown in fig. 6 is described in detail below for the publishing terminal and the listening terminal, respectively.

With reference to fig. 4, as shown in fig. 6, for a discovery request initiated by a publishing terminal, such as a first discovery request message, the foregoing S403 to S406 may be specifically implemented as S604 to S609:

s604, the issuing terminal sends a first discovery request message to the first AMF network element. Accordingly, the first AMF network element receives the first discovery request message from the publishing terminal.

The first discovery request message carries an application identifier, such as an APP ID. Optionally, the first discovery request message may further carry one or more of an identifier of the publishing terminal, a discovery mode, and a first request indication. Wherein the first request indication is for requesting issuance of a parameter, such as a ProSe discovery key parameter.

Optionally, the first request indication may be explicitly carried in the first discovery request message, such as an indication field occupying 1 bit (bit) in the first discovery request message. Or, optionally, the first discovery request message may be a discovery key request message, that is, the first request indication may be implicitly carried by using a message name.

S605, the first AMF network element interacts with the UDM network element to complete the authentication of the issuing terminal.

Illustratively, the first AMF network element sends an authentication request message to the UDM network element. The authentication request message may carry an identifier of the issuing terminal, a PLMN identifier where the issuing terminal is located, and the like. Correspondingly, the UDM network element sends an authentication response message to the first AMF network element. If the authentication is successful, the authentication response message may carry authorization information, and if the authentication is failed, the authentication response message may carry an authentication failure indication.

Illustratively, if the issuing terminal has the right to use the PC5 for communication in the PLMN corresponding to the PLMN identifier, the UDM network element may send authorization information to the first AMF network element. Otherwise, the UDM network element may send an authentication failure indication to the first AMF network element.

It should be noted that, if the first AMF network element already knows that the issuing terminal has the right to use the PC5 for communication under the current PLMN, the first PCF network element may not initiate the authentication request to the UDM network element. That is, S605 is an optional step.

If the authentication of the issuing terminal is successful, or the first AMF network element already knows that the issuing terminal has the authority to use the PC5 for communication under the current PLMN, the following steps S606-S609 may be continuously performed:

s606, the first AMF network element sends the first discovery request message to the UDR network element. Accordingly, the UDR network element receives a first discovery request message from the first AMF network element.

For a specific implementation of the first discovery request message, reference may be made to S604, which is not described herein again.

S607, the UDR network element sends a first discovery response message to the first AMF network element. Accordingly, the first AMF network element receives the first discovery response message from the UDR network element.

In a possible design method, in S606, the first AMF network element may subscribe to a discovery parameter creation, update, or deletion request from the UDR network element, where the request message carries an application identifier. When the UDR network element receives the request for creating, updating or deleting the discovery parameter corresponding to the ProSe network element and the application identifier at S606, the UDR network element may send the correspondence between the application identifier created, updated or deleted by the ProSe network element and the discovery parameter to the first AMF network element at S607. Therefore, the first AMF network element does not need to send the request message to the UDR network element every time the first request message is received, so that the signaling overhead is saved.

S608, the first AMF network element sends a first discovery response message to the publishing terminal. Accordingly, the issuing terminal receives the first discovery response message from the first AMF network element.

And S609, the release terminal releases the ProSe communication request according to the release parameters.

With reference to fig. 4, as shown in fig. 6, for a discovery request initiated by a listening terminal, such as a second discovery request message, the above S403-S406 may be specifically implemented as S610-S615:

s610, the monitoring terminal sends a second discovery request message to the second AMF network element. Accordingly, the second AMF network element receives the second discovery request message from the listening terminal.

S611, the second AMF network element interacts with the UDM network element to complete the authentication of the monitoring terminal.

Illustratively, the second AMF network element sends an authentication request message to the UDM network element. The authentication request message may carry an identifier of the monitoring terminal, a PLMN identifier where the monitoring terminal is located, and the like. Correspondingly, the UDM network element sends an authentication response message to the second AMF network element. If the authentication is successful, the authentication response message may carry authorization information, and if the authentication is failed, the authentication response message may carry an authentication failure indication.

Illustratively, if the listening terminal has the right to use the PC5 for communication in the PLMN corresponding to the PLMN identity, the UDM network element may send authorization information to the second AMF network element. Otherwise, the UDM network element may send an authentication failure indication to the second AMF network element.

It should be noted that, if the second AMF network element already knows that the monitoring terminal has the right to use the PC5 for communication under the current PLMN, the second AMF network element may not initiate the authentication request to the UDM network element. That is, S611 is an optional step.

If the authentication of the monitoring terminal is successful, or the second AMF network element already knows that the monitoring terminal has the right to use the PC5 for communication under the current PLMN, the following steps S612 to S615 may be continuously performed:

s612, the second AMF network element sends a second discovery request message to the UDR network element. Accordingly, the UDR network element receives a second discovery request message from the second AMF network element.

S610 may be referred to for a specific implementation manner of the second discovery request message, and details are not described here.

S613, the UDR network element sends a second discovery response message to the second AMF network element. Accordingly, the second AMF network element receives a second discovery response message from the UDR network element.

In a possible design method, in S612, the second AMF network element may subscribe to a discovery parameter creation, update, or deletion request from the UDR network element, where the request message carries an application identifier. When the UDR network element receives the request for creating, updating or deleting the discovery parameter corresponding to the ProSe network element and the application identifier in S612, the UDR network element may send the correspondence between the discovery parameter and the application identifier created, updated or deleted by the ProSe network element to the second AMF network element in S613. Therefore, the second AMF network element does not need to send the request message to the UDR network element every time the second request message is received, so that the signaling overhead is saved.

And S614, the second AMF network element sends a second discovery response message to the monitoring terminal. Accordingly, the listening terminal receives a second discovery response message from the second AMF network element.

S615, the monitoring terminal monitors the ProSe communication request according to the monitoring parameters.

It should be noted that the operation steps S610 to S615 for the listening terminal may be executed after or before the operation steps S604 to S609 for the publishing terminal are executed, or may be executed in a crossed manner within the same period of time, which is not specifically limited in the embodiment of the present application.

Furthermore, as can be understood from a comparison between fig. 6 and fig. 5, the communication method shown in fig. 6 differs from the communication method shown in fig. 5 in that: the steps performed by the first PCF network element in the communication method shown in fig. 5 are instead performed by the first AMF network element in the communication method shown in fig. 6, and the steps performed by the second PCF network element in the communication method shown in fig. 5 are instead performed by the second AMF network element in the communication method shown in fig. 6.

Based on the communication method shown in any one of fig. 4 to 6, the first network element may request the second network element to configure the discovery parameter corresponding to the application identifier according to the application identifier provided by the terminal, for example, the second network element may configure the publishing parameter for the publishing terminal according to the application identifier provided by the publishing terminal, and configure the monitoring parameter for the monitoring terminal according to the same application identifier provided by the monitoring terminal, that is, both the publishing parameter and the monitoring parameter correspond to the same application identifier, which may solve the problem of mismatch between the publishing parameter and the monitoring parameter caused by different network element configurations, and may improve the success rate of the discovery phase, thereby improving the reliability of the proximity service.

Further, referring to the communication method shown in any one of fig. 4 to 6, if the second network element, for example, the UDR network element does not have the discovery parameter corresponding to the application identifier provided by the terminal, for example, the proximity service corresponding to the application identifier is a newly online proximity service, or is adjusted, so that the original discovery parameter is no longer applicable to the proximity service, or the proximity service whose correspondence between the application identifier and the discovery parameter has been deleted due to a cause such as a malfunction, the communication method shown in any one of fig. 7 to 9 may also be executed. As described in detail below.

Fig. 7 is a fourth flowchart of the communication method according to the embodiment of the present application. The communication method may be applicable to the communication in the ProSe discovery phase between different network elements shown in fig. 1 or fig. 2, so as to configure discovery parameters for ProSe communication between different terminals, for example, configure a publishing parameter for a publishing terminal, and configure a monitoring parameter for a monitoring terminal.

The communication method shown in fig. 7 is described in detail below by taking the terminal, and the first network element, the second network element, and the third network element shown in fig. 1 as examples. As shown in fig. 7, the communication method includes the following S701-S708:

s701, the third network element obtains the application identifier.

S702, the third network element sends the corresponding relationship between the application identifier and the discovery parameter to the second network element. Accordingly, the second network element receives the correspondence between the application identifier and the discovery parameter from the third network element.

In one possible design approach, the communication method shown in fig. 7 may further include: the third network element sends the discovery pattern usable by the proximity service ProSe corresponding to the application identity and/or the identity of the terminal authorized to use the proximity service ProSe corresponding to the application identity to the second network element. Accordingly, the second network element receives from the third network element a discovery pattern usable by the proximity service ProSe corresponding to the application identity and/or an identity of a terminal authorized to use the proximity service ProSe corresponding to the application identity.

Further, the communication method shown in fig. 7 may further include: the third network element determines a validity time for the discovery parameter.

S703, the terminal sends the application identifier to the first network element. Accordingly, the first network element receives the application identification from the terminal.

In one possible design approach, the terminal may include a publishing terminal, and the discovery parameters may include publishing parameters. The release parameter is used for releasing a proximity service ProSe communication request from a terminal. Accordingly, the communication method shown in fig. 7 may further include: the publishing terminal sends one or more of a discovery pattern usable by the proximity service ProSe corresponding to the application identifier, an identifier of the publishing terminal, or a first request indication to the first network element. Accordingly, the first network element receives one or more of the discovery pattern, the identity of the publishing terminal, the first request indication from the publishing terminal. Wherein the first request indication is used for requesting to issue parameters. For example, the first request indication may be an operation indication as follows: command is an annouce.

In another possible design approach, the terminal may include a listening terminal, and the discovery parameters may include listening parameters. The monitoring parameter is used for monitoring the proximity service ProSe communication request monitored by the terminal. Accordingly, the communication method shown in fig. 7 may further include: the monitoring terminal sends one or more of a discovery mode which is usable by the proximity service ProSe and corresponds to the application identification, an identification of the monitoring terminal or a second request indication to the first network element. Accordingly, the first network element receives one or more of the discovery mode, the identity of the listening terminal, the second request indication from the listening terminal. Wherein the second request indication is for requesting listening parameters. For example, the first request indication may be an operation indication as follows: command is monitor.

S704, the first network element sends the application identifier to the second network element. Accordingly, the second network element receives the application identification from the first network element.

In one possible design approach, the terminal may include a publishing terminal, and the discovery parameters may include publishing parameters. The release parameter is used for releasing a proximity service ProSe communication request from a terminal. Accordingly, the communication method shown in fig. 7 may further include: the first network element sends one or more of a discovery mode usable by the proximity service ProSe corresponding to the application identification, an identification of the issuing terminal, or a first request indication to the second network element. Accordingly, the second network element receives one or more of the discovery mode, the identity of the issuing terminal, the first request indication from the first network element. Wherein the first request indication is used for requesting to issue parameters.

In another possible design approach, the terminal may include a listening terminal, and the discovery parameters may include listening parameters. The monitoring parameter is used for monitoring the proximity service ProSe communication request monitored by the terminal. Accordingly, the communication method shown in fig. 7 may further include: the first network element sends one or more of a discovery mode which can be used by proximity service ProSe and corresponds to the application identification, an identification of the monitoring terminal or a second request indication to the second network element. Correspondingly, the second network element receives one or more items of a discovery mode, an identification of the monitoring terminal and a second request indication from the first network element; the second request indication is for requesting listening parameters. Wherein the second request indication is for requesting listening parameters.

For a specific implementation manner of the above S701-S704, reference may be made to the relevant contents in the above S401-S404, and details are not described here again.

S705, the first network element learns that there is no discovery parameter corresponding to the application identifier in the second network element.

Illustratively, the first network element may learn from the second network element that there is no discovery parameter corresponding to the application identifier in the second network element. For example, if the proximity service corresponding to the application identifier is newly online, or is offline, or has been adjusted, and the corresponding discovery parameter is not updated, the discovery parameter corresponding to the application identifier may not exist in the second network element. At this time, the first network element may also send the application identifier to the third network element, and request the third network element to configure the corresponding discovery parameter, so that the following steps S706 to S708 may be performed:

s706, the first network element sends the application identifier to the third network element. Accordingly, the third network element receives the application identification from the first network element.

Wherein the discovery parameter corresponds to the application identification.

In one possible design approach, the terminal may include a publishing terminal, and the discovery parameters may include publishing parameters. The release parameter is used for releasing a proximity service ProSe communication request from a terminal. Accordingly, the communication method shown in fig. 7 may further include: the first network element sends one or more of a discovery mode usable by the proximity service ProSe corresponding to the application identity, an identity of the issuing terminal, or a first request indication to the third network element. Accordingly, the third network element receives one or more of the discovery mode, the identity of the issuing terminal, the first request indication from the first network element. Wherein the first request indication is used for requesting to issue parameters.

In another possible design approach, the terminal may include a listening terminal, and the discovery parameters may include listening parameters. The monitoring parameter is used for monitoring the proximity service ProSe communication request monitored by the terminal. Accordingly, the communication method shown in fig. 7 may further include: the first network element sends one or more of a discovery mode usable by the proximity service ProSe corresponding to the application identification, an identification of the listening terminal, or a second request indication to the third network element. Correspondingly, the third network element receives one or more items of a discovery mode, an identification of the monitoring terminal and a second request indication from the first network element; the second request indication is for requesting listening parameters. Wherein the second request indication is for requesting listening parameters.

S707, the third network element sends the discovery parameter to the first network element. Accordingly, the first network element receives discovery parameters from the third network element.

The discovery parameter corresponds to the application identifier, that is, the discovery parameter is generated by the third network element according to the application identifier.

Optionally, the communication method of fig. 7 may further include: the third network element generates the valid time of the discovery parameter and sends the valid time of the discovery parameter to the first network element. Accordingly, the first network element receives and saves the validity time of the discovery parameter from the third network element.

Illustratively, S707 may be embodied as: the third network element sends a discovery response message (discovery response) to the first network element. Accordingly, the first network element receives a discovery response message from the third network element. And the discovery response message carries the discovery parameters corresponding to the application identifier. The discovery parameter may include a publishing parameter or a listening parameter, among others. Optionally, the discovery response message may also carry the valid time of the discovery parameter.

Further, the communication method of fig. 7 may further include: and the third network element sends the application identifier, the discovery parameters corresponding to the application identifier and the effective time of the discovery parameters to the second network element. Correspondingly, the second network element receives the application identifier, the discovery parameter corresponding to the application identifier and the valid time thereof from the third network element to update the corresponding relationship between the application identifier and the discovery parameter stored locally by the second network element, such as modifying a corresponding relationship table or a configuration file, thereby ensuring that the corresponding relationship stored by the second network element is synchronous with the proximity service in the current system, so as to improve the success rate of the terminal requesting the discovery parameter, and further improve the efficiency of the proximity service.

S708, the first network element sends the discovery parameter to the terminal. Accordingly, the terminal receives discovery parameters from the first network element.

For specific implementation of S708, reference may be made to S406, which is not described herein again.

The communication method shown in fig. 7 is further described below with reference to specific examples.

Fig. 8 is a first example of the communication method shown in fig. 7. Referring to fig. 7 and 8, the first network element in fig. 7 may include the first PCF network element and the second PCF network element in fig. 8, the second network element in fig. 7 may be the UDR network element in fig. 8, the third network element in fig. 7 may be the ProSe network element in fig. 8, and the terminal in fig. 7 may include the publishing terminal and the listening terminal in fig. 8.

In conjunction with fig. 7, as shown in fig. 8, the above S701 may be implemented as the following S801-S802:

s801, the AF network element sends an application identifier to the ProSe network element. Accordingly, the ProSe network element receives the application identification from the AF network element.

S802, the ProSe network element establishes/modifies/deletes the corresponding relation between the application identification and the discovery parameter.

With reference to fig. 7, as shown in fig. 8, the above S702 may be specifically implemented as S803:

s803, the ProSe network element sends the corresponding relationship between the application identifier and the discovery parameter to the UDR network element. Accordingly, the UDR receives and stores the correspondence of the application identity and the discovery parameters from the ProSe network element.

For a specific implementation manner of the foregoing S801 to S803, reference may be made to the relevant contents in the foregoing S501 to S503, and details are not described here again.

With reference to fig. 7, as shown in fig. 8, for a discovery request initiated by a publishing terminal, such as a first discovery request message, the foregoing S703-S708 may be specifically implemented as S804-S811:

s804, the issuing terminal sends the first discovery request message to the first PCF network element via the first AMF network element. Accordingly, the first PCF network element receives the first discovery request message from the publishing terminal via the first AMF network element.

S805, the first PCF network element interacts with the UDM network element to complete the authentication of the issuing terminal.

If the authentication of the issuing terminal is successful, or the discovery mode is the open mode, or the first PCF network element has learned the authority of the issuing terminal to use the ProSe service corresponding to the application identifier under the current PLMN, the following S806-S809 may be continuously executed:

s806, the first PCF network element sends the first discovery request message to the UDR network element. Accordingly, the UDR network element receives a first discovery request message from the first PCF network element.

The specific implementation manners of S804-S806 may refer to S504-S506, which are not described herein again.

S807, the UDR network element sends the first indication information to the first PCF network element. Accordingly, the first PCF network element receives the first indication information from the UDR network element.

The first indication information is used for indicating that the second network element does not have the publishing parameter corresponding to the application identifier provided by the publishing terminal.

S808, the first PCF network element sends the first discovery request message to the ProSe network element. Accordingly, the ProSe network element receives a first discovery request message from the first PCF network element.

The content of the first discovery request message may refer to S804, which is not described herein again.

S809, the ProSe network element sends the first discovery response message to the first PCF network element. Accordingly, the first PCF network element receives the first discovery response message from the ProSe network element.

S810, the first PCF network element sends the first discovery response message to the publishing terminal via the first AMF network element. Accordingly, the publishing terminal receives the first discovery response message from the first PCF network element via the first AMF network element.

S809 may be referred to for the content of the first discovery response message, and details are not described here.

S811, the issuing terminal issues the ProSe communication request according to the issuing parameters.

For the specific implementation of S810-S811, reference may be made to S508-S509, which is not described herein again.

With reference to fig. 7, as shown in fig. 8, for a discovery request initiated by a listening terminal, such as a second discovery request message, the foregoing S703-S708 may be specifically implemented as S812-S819:

s812, the monitoring terminal sends a second discovery request message to the second PCF network element via the second AMF network element. Accordingly, the second PCF network element receives the second discovery request message from the listening terminal via the second AMF network element.

And the second discovery request message carries an application identifier. Optionally, the second discovery request message may further carry one or more of an identifier of the listening terminal, a discovery mode, and a second request indication. Wherein the second request indication is for requesting listening parameters.

S813, the second PCF network element interacts with the UDM network element to complete the authentication of the monitoring terminal.

If the authentication of the monitoring terminal is successful, or the discovery mode is an open mode, or the second PCF network element has already learned the permission of the monitoring terminal to use the ProSe service corresponding to the application identifier under the current PLMN, the following S814-S819 may be continuously executed:

s814, the second PCF network element sends a second discovery request message to the UDR network element. Accordingly, the UDR network element receives a second discovery request message from the second PCF network element.

The specific implementation of S812-S814 can refer to S510-S512, which are not described herein.

S815, the UDR network element sends the second indication information to the second PCF network element. Accordingly, the second PCF network element receives the second indication information from the UDR network element.

The second indication information is used for indicating that the second network element does not have the monitoring parameters corresponding to the application identifier provided by the monitoring terminal.

S816, the second PCF network element sends a second discovery request message to the ProSe network element. Accordingly, the ProSe network element receives a second discovery request message from the second PCF network element.

The content of the second discovery request message may refer to S812, which is not described herein again.

S817, the ProSe network element sends a second discovery response message to the second PCF network element. Accordingly, the second PCF network element receives a second discovery response message from the ProSe network element.

Wherein the second discovery response message carries the listening parameter. Optionally, the second discovery response message may also carry a validity period of the listening parameter. The monitoring parameters are used for monitoring terminals to issue ProSe communication requests.

S818, the second PCF network element sends a second discovery response message to the listening terminal. Accordingly, the listening terminal receives a second discovery response message from the second PCF network element.

S819, the monitoring terminal monitors the ProSe communication request according to the monitoring parameters.

For a specific implementation of S818-S819, reference may be made to S514-S515, which is not described herein again.

It should be noted that the operation steps S812-S819 for the listening terminal may be executed after or before the operation steps S804-S811 for the publishing terminal are executed, or may be executed in a cross manner within the same period of time, which is not specifically limited in this embodiment of the application.

Fig. 9 is a second example of the communication method shown in fig. 7. Referring to fig. 7 and 9, the first network element in fig. 7 may include the first AMF network element and the second AMF network element in fig. 9, the second network element in fig. 7 may be a UDR network element in fig. 9, the third network element in fig. 7 may be a ProSe network element in fig. 9, and the terminal in fig. 7 may include the publishing terminal and the listening terminal in fig. 9.

In conjunction with fig. 7, as shown in fig. 9, the above S701 may be implemented as the following S901-S902:

s901, the AF network element sends an application identifier to the ProSe network element. Accordingly, the ProSe network element receives the application identification from the AF network element.

S902, the ProSe network element establishes/modifies/deletes the corresponding relationship between the application identifier and the discovery parameter.

With reference to fig. 7, as shown in fig. 9, the above S702 may be specifically implemented as S903:

s903, the ProSe network element sends the corresponding relation between the application identifier and the discovery parameter to the UDR network element. Accordingly, the UDR receives and stores the correspondence of the application identity and the discovery parameters from the ProSe network element.

For a specific implementation manner of the above S901-S903, reference may be made to relevant contents in the above S601-S603, and details are not described here again.

With reference to fig. 7, as shown in fig. 9, for a discovery request initiated by a publishing terminal, such as a first discovery request message, the foregoing S703-S708 may be specifically implemented as S904-S911:

s904, the issuing terminal sends a first discovery request message to the first AMF network element. Accordingly, the first AMF network element receives the first discovery request message from the publishing terminal.

Wherein, the first discovery request message carries the application identifier. Optionally, the first discovery request message may further carry one or more of an identifier of the publishing terminal, a discovery mode, and a first request indication. Wherein the first request indication is used for requesting to issue parameters.

S905, the first AMF network element interacts with the UDM network element to complete the authentication of the issuing terminal.

If the authentication of the issuing terminal is successful, or the discovery mode is the public mode, or the first AMF network element has already learned the permission of the issuing terminal to use the ProSe service corresponding to the application identifier under the current PLMN, the following S906-S909 may be continuously executed:

s906, the first AMF network element sends a first discovery request message to the UDR network element. Accordingly, the UDR network element receives a first discovery request message from the first AMF network element.

The specific implementation manners of S904-S906 can refer to S604-S606, which are not described herein again.

And S907, the UDR network element sends the first indication information to the first AMF network element. Accordingly, the first AMF network element receives the first indication information from the UDR network element.

S908, the first AMF network element sends a first discovery request message to the ProSe network element. Accordingly, the ProSe network element receives a first discovery request message from the first AMF network element.

The content of the first discovery request message may refer to S904, which is not described herein again.

S909, the ProSe network element sends a first discovery response message to the first AMF network element. Accordingly, the first AMF network element receives a first discovery response message from the ProSe network element.

Wherein, the first discovery response message carries the publishing parameter. Optionally, the first discovery response message may further carry an expiration date of the publishing parameter. The release parameter is used for releasing the terminal to release the ProSe communication request.

S910, the first AMF network element sends a first discovery response message to the publishing terminal. Accordingly, the issuing terminal receives the first discovery response message from the first AMF network element.

And S911, the release terminal releases the ProSe communication request according to the release parameters.

For the specific implementation of S910 to S911, reference may be made to S608 to S609, which is not described herein again.

With reference to fig. 7, as shown in fig. 9, for a discovery request initiated by a listening terminal, such as a second discovery request message, the foregoing S703 to S708 may be specifically implemented as S912 to S919:

s912, the monitoring terminal sends a second discovery request message to the second AMF network element. Accordingly, the second AMF network element receives the second discovery request message from the listening terminal.

And S913, the second AMF network element interacts with the UDM network element to complete the authentication of the monitoring terminal.

If the authentication of the monitoring terminal is successful, or the discovery mode is the open mode, or the second AMF network element has already learned the permission of the monitoring terminal to use the ProSe service corresponding to the application identifier under the current PLMN, the following S914-S919 may be continuously executed:

s914, the second AMF network element sends a second discovery request message to the UDR network element. Accordingly, the UDR network element receives a second discovery request message from the second AMF network element.

The specific implementation of the above S912-S914 can refer to S610-S612, which is not described herein again.

S915, the UDR network element sends the second indication information to the second AMF network element. Accordingly, the second AMF network element receives the second indication information from the UDR network element.

S916, the second AMF network element sends a second discovery request message to the ProSe network element. Accordingly, the ProSe network element receives a second discovery request message from the second AMF network element.

The content of the second discovery request message may refer to S912, which is not described herein again.

S917, the ProSe network element sends a second discovery response message to the second AMF network element. Accordingly, the second AMF network element receives a second discovery response message from the ProSe network element.

S918, the second AMF network element sends a second discovery response message to the listening terminal. Accordingly, the listening terminal receives a second discovery response message from the second AMF network element.

S919, the monitoring terminal monitors the ProSe communication request according to the monitoring parameters.

For the specific implementation of S918-S919, reference may be made to S614-S615, which is not described herein again.

It should be noted that the operation steps S912 to S919 for the listening terminal may be executed after or before the operation steps S904 to S911 for the issuing terminal are executed, or may be executed in a crossed manner within the same time period, which is not specifically limited in this embodiment of the application.

Furthermore, as can be understood from a comparison between fig. 9 and fig. 8, the communication method shown in fig. 9 differs from the communication method shown in fig. 8 in that: the steps performed by the first PCF network element in the communication method shown in fig. 8 are instead performed by the first AMF network element in the communication method shown in fig. 9, and the steps performed by the second PCF network element in the communication method shown in fig. 8 are instead performed by the second AMF network element in the communication method shown in fig. 9.

Based on the communication method shown in any of fig. 7 to 9, the first network element may request, according to the application identifier provided by the terminal, the second network element to configure the discovery parameter corresponding to the application identifier, and in case there is no discovery parameter corresponding to the application identifier in the second network element, the first network element may send the application identity to the third network element, request the third network element to configure the discovery parameters corresponding to the application identity, for example, the third network element may configure the publishing terminal with publishing parameters according to the application identifier provided by the publishing terminal, and configure the monitoring terminal with monitoring parameters according to the same application identifier provided by the monitoring terminal, that is, the release parameter and the monitoring parameter are both corresponding to the same application identifier, which can solve the problem of mismatching between the release parameter and the monitoring parameter caused by different network element configurations, and can improve the success rate of the discovery phase, thereby improving the reliability of the proximity service.

It should be noted that, in the communication method shown in any one of fig. 5 to 6 and fig. 8 to 9, the issuing terminal and the listening terminal may be located in different PLMNs or may be located in the same PLMN. Further, when the distribution terminal and the monitoring terminal are located in the same PLMN, the first AMF network element and the second AMF network element may be the same network element or different network elements, and similarly, in the communication method shown in fig. 5 or fig. 8, when the distribution terminal and the monitoring terminal are located in the same PLMN, the first PCF network element and the second PCF network element may be the same network element or different network elements. The embodiment of the present application is not particularly limited to this.

Still further, the correspondence relationship related to the communication method shown in any one of fig. 4 to fig. 9 is described by taking an issuing terminal as an example. In practical applications, the same application identifier may also correspond to multiple issuing terminals, that is, there may be a case where multiple issuing terminals issue ProSe communication requests of the same application at the same time. At this time, for a certain monitoring terminal, the ProSe communication requests issued by the plurality of issuing terminals may be monitored simultaneously, and one of the monitored issuing terminals may be selected to establish ProSe communication. Correspondingly, besides the correspondence between the application identifier and the discovery parameter, the correspondence may also include a correspondence between an authorized user identifier in the application corresponding to the application identifier and the discovery parameter. It should be understood that when there are a plurality of issuing terminals, there are a plurality of authorized user identifiers, and the plurality of authorized user identifiers correspond to the plurality of issuing terminals one to one. The following is a detailed description with reference to examples.

Fig. 10 is a third example of the communication method shown in fig. 4. Referring to fig. 4, as shown in fig. 10, the first network element in fig. 4 may include the first AMF network element and the second AMF network element in fig. 10, the second network element in fig. 4 may be a UDR network element or a UDM network element in fig. 10, the third network element in fig. 4 may be the first ProSe network element in fig. 10, and the terminal in fig. 4 may include the publishing terminal and the listening terminal in fig. 10. Optionally, the third network element in fig. 4 may further include the second ProSe network element in fig. 10. The communication method shown in fig. 10 will be described in detail below with reference to the communication method shown in fig. 6.

As shown in fig. 10, the communication method may include the steps of:

s1001, the AF network element sends the application identification to the UDR network element or the UDM network element, and the authorized user identification in the application corresponding to the application identification. Correspondingly, the UDR network element or the UDM network element receives the application identifier from the AF network element, and the authorized user identifier in the application corresponding to the application identifier.

For example, the application identifier may correspond to one or more authorized user identifiers in the application, and the one or more authorized user identifiers may form a user identifier list. The authorized user identifier may be an account, a user name, or the like that the user logs in the application corresponding to the application identifier through the publishing terminal, or may be an identifier of the publishing terminal itself, so as to distinguish different users or different publishing terminals in the same application.

It should be noted that the S1001 is configured to provide, for the UDR network element or the UDM network element, a corresponding relationship between the application identifier and the authorized user identifier in the application identifier. It should be understood that this correspondence may also be obtained in other ways, that is, S1001 is an optional step, such as may be preconfigured or collected by performing the following S1008, which is not specifically limited in this embodiment of the application.

Optionally, the AF network element may further send an application identifier to one or more of the first ProSe network element or the second ProSe network element (if present), and an authorized user identifier in the application corresponding to the application identifier. Accordingly, the first ProSe network element or the second ProSe network element (if present) may receive the application identification from the AF network element, and the authorized user identification in the application corresponding to the application identification.

And the AF network element sends the application identifier and the authorized user identifier in the application corresponding to the application identifier to the UDR network element or the UDM network element (if the AF network element is a third-party AF network element, the application identifier needs to be forwarded through the NEF network element). The first ProSe network element may obtain the application identifier information from the UDR network element or the UDM network element in a subscription and acquisition manner, and whether to obtain an authorized user identifier in the application corresponding to the application identifier is used as an option. The reason for this is that: if the first ProSe network element can also verify in step S1008 whether the user identifier is authorized, then it is not necessary to store this information in the first ProSe network element. The same operation is performed also if a second ProSe network element is present.

The communication method shown in fig. 10 is described in detail below for the publishing terminal and the listening terminal, respectively.

As shown in fig. 10, for a discovery request initiated by a publishing terminal, such as a first discovery request message, the communication method shown in fig. 10 further includes S1002-S1008:

s1002, the issuing terminal sends a first discovery request message to the first AMF network element. Accordingly, the first AMF network element receives the first discovery request message from the publishing terminal.

The first discovery request message carries an application identifier, such as an APP ID, and a user identifier (a user identifier at an application level and/or a user identifier recognizable by a network element of a core network) of the terminal in an application corresponding to the application identifier. Optionally, the first discovery request message may further carry one or more of a discovery mode and a first request indication. Wherein the first request indication is for requesting issuance of a parameter, such as a ProSe discovery key parameter.

Optionally, the first request indication may be explicitly carried in the first discovery request message, such as an indication field occupying 1 bit (bit) in the first discovery request message. Or, optionally, the first discovery request message may be a discovery key request message, that is, the first request indication may be implicitly carried by using a message name. Alternatively, optionally, the first discovery request message may be sent by the issuing terminal to the first AMF network element as part of a non-access stratum (NAS) message, for example, as part of a container (container) in the NAS message.

For other specific implementations of the discovery mode and the first request indication, reference may be made to the related contents in S604, and details are not described here.

S1003, the first AMF network element sends a first discovery request message to the first ProSe network element. Accordingly, the first ProSe network element receives a first discovery request message from the first AMF network element.

S1002 may be referred to for a specific implementation manner of the first discovery request message, which is not described herein again.

S1004, the first ProSe network element interacts with the UDR network element or the UDM network element to complete the verification of the limited mode of the issuing terminal.

Illustratively, the first ProSe network element may send a restricted mode authentication request message to the UDR network element or the UDM network element. The restricted mode verification request message may carry an application identifier and a user identifier of the issuing terminal in an application corresponding to the application identifier. Accordingly, the UDR network element or the UDM network element may send a restricted mode verification response message to the first ProSe network element. The restricted mode verification response message may carry restricted mode verification result indication information, where the indication information is used to indicate whether the issuing terminal has permission to use the application corresponding to the application identifier for ProSe communication.

For example, if the user identifier of the issuing terminal exists in the authorized user identifier list in the application corresponding to the application identifier, it may be considered that the restricted mode verification is successful, otherwise, it is considered that the restricted mode verification is failed.

It should be noted that, if the first ProSe network element already knows that the issuing terminal has the right to use the application corresponding to the application identifier for ProSe communication, the first ProSe network element may not initiate the restricted mode verification request to the UDR network element or the UDM network element. That is, S1004 is an optional step.

If the verification of the limited mode of the issuing terminal is successful, or the first ProSe network element already knows that the issuing terminal has the right to use the application corresponding to the application identifier for ProSe communication, the following S1005-S1008 may be continuously executed:

s1005, the first ProSe network element sends a first discovery response message to the first AMF network element. Accordingly, the first AMF network element receives the first discovery response message from the first ProSe network element.

S1006, the first AMF network element sends a first discovery response message to the publishing terminal. Accordingly, the issuing terminal receives the first discovery response message from the first AMF network element.

The first discovery response message may carry the publishing parameter. The publishing parameter corresponds to the application identifier carried by the first discovery request message, and may be a ProSe discovery key parameter.

Optionally, the first discovery response message may further carry an expiration date of the publishing parameter.

And S1007, the release terminal releases the ProSe communication request according to the release parameters.

S1008, the first ProSe network element sends the application identifier, and the corresponding relationship between the user identifier and the publishing parameter of the publishing terminal in the application corresponding to the application identifier to the UDR network element or the UDM network element. Correspondingly, the UDR network element or the UDM network element receives and stores the application identifier, the user identifier of the issuing terminal in the application corresponding to the application identifier, and the corresponding relationship between the issuing parameters from the first ProSe network element.

Optionally, the correspondence may further include valid time of the release parameter.

It should be noted that, the above-mentioned S1002 to S1008 may be repeatedly executed for a plurality of issuing terminals, respectively, to collect the application identifier, the corresponding relationship between the user identifier and the issuing parameter of each of the plurality of issuing terminals in the application corresponding to the application identifier, and store the corresponding relationship in the UDR network element or the UDM network element for standby.

In addition, S1008 may be executed before executing S1005-S1007, may also be executed after executing S1005-S1007, and may also be executed in the process of executing S1005-S1007, which is not specifically limited in this embodiment of the present application.

As shown in fig. 10, for the discovery request initiated by the listening terminal, such as the second discovery request message, the communication method shown in fig. 10 may further include S1009-S1017:

s1009, the listening terminal sends a second discovery request message to the second AMF network element. Accordingly, the second AMF network element receives the second discovery request message from the listening terminal.

The second discovery request message carries an application identifier, a user identifier of the issuing terminal in an application corresponding to the application identifier, and a discovery mode.

Optionally, the second discovery request message may further carry one or more of a user identifier of the listening terminal in an application corresponding to the application identifier, or a second request indication. Wherein the second request indication is for requesting listening parameters, such as ProSe discovery match parameters.

In one possible design method, when the second ProSe network element exists, the first AMF network element may request the monitoring parameter from the UDR network element or the UDM network element through the second ProSe network element, and the following S1010-S1013 may be performed:

s1010, the second AMF network element sends a second discovery request message to the second ProSe network element. Accordingly, the second ProSe network element receives a second discovery request message from the second AMF network element.

S1009 may be referred to for a specific implementation manner of the second discovery request message, which is not described herein again.

S1011, the second ProSe network element sends a third discovery request message to the UDR network element or the UDM network element. Accordingly, the UDR network element or the UDM network element receives the third discovery request message from the second ProSe network element.

And the third discovery request message carries an application identifier, a user identifier of the issuing terminal in the application corresponding to the application identifier, and a discovery mode.

Optionally, the third discovery request message may further carry one or more of a user identifier of the listening terminal in an application corresponding to the application identifier, or a second request indication. Wherein the second request indication is for requesting listening parameters, such as ProSe discovery match parameters.

The user identifier of the monitoring terminal in the application corresponding to the application identifier is used for the interaction between the second ProSe network element and the UDR network element or the UDM network element to complete the restricted mode verification of the monitoring terminal, that is, to determine whether the monitoring terminal has the right to use the application corresponding to the application identifier for ProSe communication, and specific implementation may refer to the relevant content of the restricted mode verification performed on the issuing terminal in S1004, which is not described herein again.

S1012, the UDR network element or the UDM network element sends a third discovery response message to the second ProSe network element. Accordingly, the second ProSe network element receives a third discovery response message from the UDR network element or the UDM network element.

Wherein the third discovery response message carries the listening parameter. Optionally, the third discovery response message may further carry a validity period of the listening parameter. The monitoring parameter is used for monitoring other terminals, such as the ProSe communication request issued by the issuing terminal.

Optionally, the third discovery response message may be a discovery match parameter response message.

S1013, the second ProSe network element sends a second discovery response message to the second AMF network element. Accordingly, the second AMF network element receives a second discovery response message from the second ProSe network element.

The content of the second discovery response message may refer to the third discovery response message, which is not described herein again. Optionally, the second discovery response message may be a discovery match parameter response message.

In another possible design method, when the second ProSe network element does not exist, the first AMF network element may directly request the listening parameter from the UDR network element or the UDM network element, that is, the communication method shown in fig. 10 may further include S1014-S1015:

s1014, the second AMF network element sends a second discovery request message to the UDR network element or the UDM network element. Accordingly, the UDR network element or the UDM network element receives the second discovery request message from the second AMF network element.

For specific content of the second discovery request message, reference may be made to S1009, which is not described herein again.

S1015, the UDR network element or the UDM network element sends a second discovery response message to the second AMF network element. Accordingly, the second AMF network element receives a second discovery response message from the UDR network element or the UDM network element.

For a specific implementation manner of the second discovery response message, reference may be made to S1013, and details are not described here.

After the second AMF network element receives the second discovery response message from the second ProSe network element or the UDR network element or the UDM network element, the following S1016 may be performed.

S1016, the second AMF network element sends a second discovery response message to the listening terminal. Accordingly, the listening terminal receives a second discovery response message from the second AMF network element.

S1017, the monitoring terminal monitors the ProSe communication request according to the monitoring parameters.

For specific implementation of S1016-S1017, reference may be made to S614-S615, which is not described herein again.

Still further, the discovery parameter generating network element, such as the first ProSe network element shown in fig. 10, and the discovery parameter storing network element, such as the UDR network element or the UDM network element shown in fig. 10, may belong to different operators. In this case, for the sake of business information confidentiality, the home operator of the discovery parameter generation network element may not want to store the generated discovery parameters in the discovery parameter storage network element, but adopts the following alternative shown in fig. 11, that is, the discovery parameter storage network element stores the following correspondence relationship: and the application identifier, the authorized user identifier in the application corresponding to the application identifier and the identifier of the first ProSe network element.

Fig. 11 is a third example of the communication method shown in fig. 7. Referring to fig. 7 and 11, the first network element in fig. 7 may include the first AMF network element and the second AMF network element in fig. 11, the second network element in fig. 7 may be a UDR network element or a UDM network element in fig. 11, the third network element in fig. 7 may be the first ProSe network element in fig. 11, and the terminal in fig. 7 may include the publishing terminal and the listening terminal in fig. 11. Optionally, the third network element in fig. 7 may further include the second ProSe network element in fig. 11, and the second ProSe network element belongs to a different operator from the first ProSe network element. The communication method shown in fig. 11 will be described in detail below with reference to fig. 10.

As shown in fig. 11, the communication method may include the steps of:

s1101, the AF network element sends an application identifier to the UDR network element or the UDM network element, and an authorized user identifier in the application corresponding to the application identifier. Correspondingly, the UDR network element or the UDM network element receives the application identifier from the AF network element, and the authorized user identifier in the application corresponding to the application identifier.

Regarding a specific implementation manner of S1101, reference may be made to S1001 described above, which is not described herein again.

The following description is made for the publishing terminal and the listening terminal, respectively.

As shown in fig. 11, for a discovery request initiated by a publishing terminal, such as a first discovery request message, the communication method shown in fig. 11 may include the following S1102-S1108:

s1102, the issuing terminal sends a first discovery request message to the first AMF network element. Accordingly, the first AMF network element receives the first discovery request message from the publishing terminal.

S1103, the first AMF network element sends a first discovery request message to the first ProSe network element. Accordingly, the first ProSe network element receives a first discovery request message from the first AMF network element.

S1104, the first ProSe network element interacts with the UDR network element or the UDM network element to complete the verification of the limited mode of the issuing terminal.

S1105, the first ProSe network element sends a first discovery response message to the first AMF network element. Accordingly, the first AMF network element receives the first discovery response message from the first ProSe network element.

S1106, the first AMF network element sends a first discovery response message to the publishing terminal. Accordingly, the issuing terminal receives the first discovery response message from the first AMF network element.

S1107, the issuing terminal issues the ProSe communication request according to the issuing parameters.

For specific implementation manners of the above S1102 to S1107, reference may be made to the above S1002 to S1007, which is not described herein again.

S1108, the first ProSe network element sends an application identifier, a user identifier of the terminal in an application corresponding to the application identifier, and a corresponding relationship between the identifiers of the first ProSe network element to the UDR network element or the UDM network element. Correspondingly, the UDR network element or the UDM network element receives and stores the application identifier, the user identifier of the issuing terminal in the application corresponding to the application identifier, and the corresponding relationship between the identifiers of the first ProSe network element from the first ProSe network element.

That is, since the first ProSe network element does not belong to the same operator as the UDR network element or the UDM network element, the first ProSe network element may not store the discovery parameters corresponding to the application identification in the UDR network element or the UDM network element, but store the identification of the first ProSe network element in the UDR network element or the UDM network element, for business privacy reasons. In this way, the second AMF network element or the second ProSe network element may request the discovery parameter from the first ProSe network element after acquiring the identifier of the first ProSe network element from the UDR network element or the UDM network element.

It should be noted that, the above-mentioned S1102-S1108 may be repeatedly executed for a plurality of publishing terminals, respectively, to collect the application identifier, the corresponding relationship between the user identifier in the application corresponding to the application identifier and the identifier of the first ProSe network element of each publishing terminal, and store the corresponding relationship in the UDR network element or the UDM network element for standby.

In addition, S1108 may be executed before executing S1105 to S1107, after executing S1105 to S1107, or during executing S1105 to S1107, which is not specifically limited in this embodiment of the application.

As shown in fig. 11, for the discovery request initiated by the listening terminal, such as the second discovery request message, the communication method shown in fig. 11 may further include S1109-S1121:

s1109, the listening terminal sends a second discovery request message to the second AMF network element. Accordingly, the second AMF network element receives the second discovery request message from the listening terminal.

For a specific implementation of S1109, reference may be made to S1009 above, which is not described herein again.

In one possible design method, when there is a second ProSe network element, the first AMF network element may request, through the second ProSe network element, an identifier of the first ProSe network element from the UDR network element or the UDM network element, and receive a discovery parameter requested by the second ProSe network element from the first ProSe network element, that is, the communication method shown in fig. 11 may further include S1110-S1115:

s1110, the second AMF network element sends a second discovery request message to the second ProSe network element. Accordingly, the second ProSe network element receives a second discovery request message from the second AMF network element.

For a specific implementation of the second discovery request message, reference may be made to S1109, which is not described herein again.

S1111, the second ProSe network element sends a fourth discovery request message to the UDR network element or the UDM network element. Accordingly, the UDR network element or the UDM network element receives the fourth discovery request message from the second ProSe network element.

The specific implementation manner of the fourth discovery request message may refer to the third discovery request message in S1011, which is not described herein again.

S1112, the UDR network element or the UDM network element sends a fourth discovery response message to the second ProSe network element. Accordingly, the second ProSe network element receives a fourth discovery response message from the UDR network element or the UDM network element.

Referring to S1108, the fourth discovery response message does not carry the discovery parameters, but the identification of the first ProSe network element, whereas the first ProSe network element does not store the discovery parameters in the UDR or UDM network element, but stores the identification of the first ProSe network element in the UDR or UDM network element.

S1113, the second ProSe network element sends the second discovery request message to the first ProSe network element. Accordingly, the first ProSe network element receives a second discovery request message from the second ProSe network element.

S1114, the first ProSe network element sends a second discovery response message to the second ProSe network element. Accordingly, the second ProSe network element receives the second discovery response message from the first ProSe network element.

S1115, the second ProSe network element sends a second discovery response message to the second AMF network element. Accordingly, the second AMF network element receives a second discovery response message from the second ProSe network element.

The content of the second discovery request message may refer to S1013, and is not described herein again.

In another possible design method, when there is no second ProSe network element, the second AMF network element may directly request the identity of the first ProSe network element from the UDR network element or the UDM network element, and receive the discovery parameter requested from the first ProSe network element, that is, the communication method shown in fig. 11 may further include S1116-S1119:

s1116, the second AMF network element sends a fourth discovery request message to the UDR network element or the UDM network element. Accordingly, the UDR network element or the UDM network element receives the fourth discovery request message from the second AMF network element.

For a specific implementation manner of the fourth discovery request message, reference may be made to S1111, which is not described herein again.

S1117, the UDR network element or the UDM network element sends a fourth discovery response message to the second AMF network element. Accordingly, the second AMF network element receives the fourth discovery response message from the UDR network element or the UDM network element.

For a specific implementation manner of the fourth discovery response message, reference may be made to S1112, which is not described herein again.

S1118, the second AMF network element sends a second discovery request message to the first ProSe network element. Accordingly, the first ProSe network element receives a second discovery request message from the second AMF network element.

S1119, the first ProSe network element sends a second discovery response message to the second AMF network element. Accordingly, the second AMF network element receives the second discovery response message from the first ProSe network element.

For a specific implementation manner of the second discovery response message, reference may be made to S1114, which is not described herein again.

After the second AMF network element receives the second discovery response message from the second ProSe network element or the UDR network element or the UDM network element, the communication method shown in fig. 11 may further include S1120-S1121.

S1120, the second AMF network element sends a second discovery response message to the listening terminal. Accordingly, the listening terminal receives a second discovery response message from the second AMF network element.

And S1121, the monitoring terminal monitors the ProSe communication request according to the monitoring parameters.

For specific implementation of S1120-S1121, reference may be made to S1016-S1017, which is not described herein again.

The communication method provided by the embodiment of the present application is described in detail above with reference to fig. 3 to 11. Two other communication devices provided in the embodiments of the present application are described in detail below with reference to fig. 12 to 13.

Fig. 12 is a schematic structural diagram of a communication device according to an embodiment of the present application. As shown in fig. 12, the communication apparatus 1200 includes: a receiving module 1201 and a sending module 1202. For convenience of explanation, fig. 12 shows only the main components of the communication apparatus.

In one design, communications apparatus 1200 shown in fig. 12 may be adapted for use in the communications system shown in fig. 1 or fig. 2 to perform the function of the first network element in the communications method shown in any of fig. 4-6, or fig. 10.

The receiving module 1201 is configured to receive an application identifier from a terminal. A sending module 1202, configured to send the application identifier to the second network element. A receiving module 1201, further configured to receive a discovery parameter from a second network element; the discovery parameter corresponds to an application identification. The sending module 1202 is further configured to send the discovery parameter to the terminal.

In one possible design, the terminal may include a publishing terminal and the discovery parameters may include publishing parameters. The release parameter is used for releasing a proximity service ProSe communication request from a terminal. Accordingly, the sending module 1202 is further configured to send, to the second network element, one or more of a discovery mode usable by the proximity service ProSe corresponding to the application identifier, an identifier of the issuing terminal, or the first request indication. Wherein the first request indication is used for requesting to issue parameters.

In another possible design, the terminal may include a listening terminal and the discovery parameters may include listening parameters. The monitoring parameter is used for monitoring the proximity service ProSe communication request monitored by the terminal. Accordingly, the sending module 1202 is further configured to send, to the second network element, one or more of a discovery mode usable by the proximity service ProSe corresponding to the application identifier, an identifier of the listening terminal, or a second request indication. Wherein the second request indication is for requesting listening parameters.

Optionally, the receiving module 1201 is further configured to receive the validity time of the discovery parameter from the second network element; and a sending module 1202, further configured to send the validity time of the discovery parameter to the terminal.

Optionally, the communication apparatus 1200 shown in fig. 12 may further include a processing module and a storage module (neither shown in fig. 12) storing programs or instructions. The program or instructions, when executed by the processing module, enable the communications apparatus 1200 shown in fig. 12 to perform the functions of the first network element in the communications method shown in any one of fig. 4-6, or fig. 10.

It should be noted that the communication apparatus 1200 shown in fig. 12 may be a first network element, such as a PCF network element or an AMF network element configured to discover parameters for a terminal, or may be a chip or a chip system disposed in the first network element, which is not limited in this application.

In addition, for technical effects of the communication apparatus 1200 shown in fig. 12, reference may be made to a technical effect of the communication method shown in any one of fig. 4 to fig. 6 or fig. 10, which is not described herein again.

In another design, the communications apparatus 1200 shown in fig. 12 may also be applied to the communications system shown in fig. 1 or fig. 2, and perform the function of the second network element in the communications method shown in any one of fig. 4-6 or fig. 10.

Wherein, the receiving module 1201 is configured to receive a corresponding relationship between the application identifier and the discovery parameter from the third network element. The receiving module 1201 is further configured to receive an application identifier from the first network element. A sending module 1202, configured to send the discovery parameter to the first network element.

In one possible design, the receiving module 1201 is further configured to receive, from the third network element, a discovery pattern usable by the proximity service ProSe corresponding to the application identity, and/or an identity of a terminal authorized to use the proximity service ProSe corresponding to the application identity.

In one possible design, the terminal may include a publishing terminal and the discovery parameters may include publishing parameters. The release parameter is used for releasing a proximity service ProSe communication request from a terminal. Correspondingly, the receiving module 1201 is further configured to receive one or more of a discovery mode, an identifier of a publishing terminal, and an indication of a first request from a first network element. Wherein the first request indication is used for requesting to issue parameters.

In another possible design, the terminal may include a listening terminal and the discovery parameters may include listening parameters. The monitoring parameter is used for monitoring the proximity service ProSe communication request monitored by the terminal. Correspondingly, the receiving module 1201 is further configured to receive one or more of a discovery mode, an identity of a listening terminal, and a second request indication from the first network element. Wherein the second request indication is for requesting listening parameters.

Optionally, the receiving module 1201 is further configured to receive an effective time of the discovery parameter from the third network element; and a sending module 1202, further configured to send the validity time of the discovery parameter to the first network element.

Optionally, the communication apparatus 1200 shown in fig. 12 may further include a processing module and a storage module (neither shown in fig. 12) storing programs or instructions. The processing module, when executing the program or the instructions, causes the communication apparatus 1200 shown in fig. 12 to perform the communication method shown in any one of fig. 4-6 or fig. 10.

It should be noted that the communication apparatus 1200 shown in fig. 12 may be a second network element, such as a UDR network element that stores the correspondence between the application identifier and the discovery parameter in a unified manner, or may be a chip or a chip system disposed in the second network element, which is not limited in this application.

Fig. 13 is a third schematic structural diagram of a communication device according to an embodiment of the present application. As shown in fig. 13, the communication apparatus 1300 includes: a processing module 1301 and a transceiver module 1302. For convenience of explanation, fig. 13 shows only main components of the communication apparatus.

In one design, communications apparatus 1300 shown in fig. 13 may be adapted for use in the communications system shown in fig. 1 or 2 to perform the functions of the third network element in the communications method shown in any of fig. 4-6, or 10.

The processing module 1301 is configured to obtain an application identifier. A transceiver module 1302, configured to send the application identifier and the discovery parameter to the second network element. Wherein the discovery parameter corresponds to the application identification.

Optionally, the processing module 1301 is further configured to obtain an identifier of a terminal authorized to use proximity service ProSe corresponding to the application identifier; and a transceiver module 1302, configured to send the identifier of the terminal to the second network element.

Optionally, the processing module 1301 is further configured to obtain a discovery mode usable by the proximity service ProSe corresponding to the application identifier; and a transceiver module 1302, further configured to send the discovery pattern to the second network element.

Further, the processing module 1301 is further configured to determine a valid time of the discovery parameter; and a transceiver module 1302, configured to send the validity time of the discovery parameter to the second network element.

Optionally, the communications apparatus 1300 shown in fig. 13 may further include a storage module (not shown in fig. 13) that stores programs or instructions. The program or instructions, when executed by the processing module 1301, enable the communication apparatus 1300 shown in fig. 13 to perform the functions of the third network element in the communication method shown in any one of fig. 4 to 6 or fig. 10.

It should be noted that the communication apparatus 1300 shown in fig. 13 may be a third network element, such as a proximity service function (ProSe function) network element for generating discovery parameters, or a PCF network element, an AF network element, an NF network element, etc. having a function of the ProSe network element, or may be a chip or a chip system disposed in the third network element, which is not limited in this application.

Technical effects of the communication apparatus 1300 shown in fig. 13 can refer to technical effects of the communication method shown in any one of fig. 4-6 or fig. 10, and are not described herein again.

In another design, the communications apparatus 1300 shown in fig. 13 may also be applied in the communications system shown in fig. 1 or fig. 2 to perform the function of the first network element in the communications method shown in any one of fig. 7-9 or fig. 11.

Wherein, the transceiver module 1302 is configured to receive the application identifier from the terminal and send the application identifier to the second network element. A processing module 1301, configured to learn that there is no discovery parameter corresponding to the application identifier in the second network element. The transceiver module 1302 further sends the application identifier to the third network element and receives the discovery parameter from the third network element.

In one possible design, the terminal may include a publishing terminal and the discovery parameters may include publishing parameters. The release parameter is used for releasing a proximity service ProSe communication request from a terminal. Accordingly, the transceiver module 1302 is further configured to send one or more of a discovery pattern usable by the proximity service ProSe corresponding to the application identity, an identity of the issuing terminal, or the first request indication to the third network element. Wherein the first request indication is used for requesting to issue parameters.

In another possible design, the terminal may include a listening terminal and the discovery parameters may include listening parameters. The monitoring parameter is used for monitoring the proximity service ProSe communication request monitored by the terminal. Accordingly, the transceiver module 1302 is further configured to send one or more of a discovery mode available for proximity service ProSe corresponding to the application identity, an identity of the listening terminal, or a second request indication to the third network element. Wherein the second request indication is for requesting listening parameters.

Optionally, the transceiver module 1302 is further configured to receive the valid time of the discovery parameter from the third network element, and send the valid time of the discovery parameter to the terminal.

Optionally, the communications apparatus 1300 shown in fig. 13 may further include a storage module (not shown in fig. 13) that stores programs or instructions. The program or instructions, when executed by the processing module 1301, enable the communications apparatus 1300 shown in fig. 13 to perform the functions of the first network element in the communication method shown in any one of fig. 7 to 9, or fig. 11.

It should be noted that the communication apparatus 1300 shown in fig. 13 may be a first network element, such as a PCF network element or an AMF network element configured to discover parameters for a terminal, or may be a chip or a chip system disposed in the first network element, which is not limited in this application.

Technical effects of the communication apparatus 1300 shown in fig. 13 can refer to technical effects of the communication method shown in any one of fig. 7-9 or fig. 11, and are not described herein again.

In yet another design, the communications apparatus 1300 shown in fig. 13 may also be applied in the communications system shown in fig. 1 or fig. 2 to perform the function of the third network element in the communications method shown in any one of fig. 7-9 or fig. 11.

Wherein, the transceiver module 1302 is configured to receive an application identifier from a first network element. A processing module 1301, configured to determine a discovery parameter corresponding to the application identifier. The transceiver module 1302 is further configured to send the discovery parameter to the first network element.

In one possible design, the terminal may include a publishing terminal and the discovery parameters may include publishing parameters. The release parameter is used for releasing a proximity service ProSe communication request from a terminal. Accordingly, the transceiver module 1302 is further configured to receive, from the first network element, one or more of a discovery pattern usable by the proximity service ProSe corresponding to the application identity, an identity of the issuing terminal, or a first request indication. Wherein the first request indication is used for requesting to issue parameters.

In another possible design, the terminal may include a listening terminal and the discovery parameters may include listening parameters. The monitoring parameter is used for monitoring the proximity service ProSe communication request monitored by the terminal. Accordingly, the transceiver module 1302 is further configured to receive, from the first network element, one or more of a discovery mode available for proximity services ProSe corresponding to the application identity, an identity of the listening terminal, or a second request indication. Wherein the second request indication is for requesting listening parameters.

Optionally, the processing module 1301 is further configured to determine a valid time of the discovery parameter; and a transceiver module 1302, further configured to send the validity time of the discovery parameter to the first network element.

Optionally, the communications apparatus 1300 shown in fig. 13 may further include a storage module (not shown in fig. 13) that stores programs or instructions. The program or instructions, when executed by the processing module 1301, enable the communication apparatus 1300 shown in fig. 13 to perform the functions of the third network element in the communication method shown in any one of fig. 7 to 9 or fig. 11.

The embodiment of the application provides a chip system. The system on chip includes a processor for implementing the processing functions according to the above method embodiments, and an input/output port for implementing the transceiving functions according to the above method embodiments.

In one possible design, the system-on-chip further includes a memory for storing program instructions and data implementing the functions of the above-described method embodiments.

The embodiment of the application provides a communication system. The system comprises the terminal devices and a plurality of core network elements, such as a first network element, a second network element and a third network element.

An embodiment of the present application provides a computer-readable storage medium, including: the computer readable storage medium having stored therein computer instructions; the computer instructions, when executed on a computer, cause the computer to perform the communication method described in the method embodiments above.

The present application provides a computer program product containing instructions, including a computer program or instructions, which when run on a computer causes the computer to execute the communication method described in the above method embodiments.

It should be understood that the processor in the embodiments of the present application may be a Central Processing Unit (CPU), and the processor may also be other general purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

It will also be appreciated that the memory in the embodiments of the subject application can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The non-volatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. Volatile memory can be Random Access Memory (RAM), which acts as external cache memory. By way of example, but not limitation, many forms of Random Access Memory (RAM) are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM), and direct bus RAM (DR RAM).

The above embodiments may be implemented in whole or in part by software, hardware (e.g., circuitry), firmware, or any combination thereof. When implemented in software, the above-described embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product comprises one or more computer instructions or computer programs. The procedures or functions according to the embodiments of the present application are wholly or partially generated when the computer instructions or the computer program are loaded or executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by wire (e.g., infrared, wireless, microwave, etc.). 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, data center, etc. that contains one or more collections of available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. The semiconductor medium may be a solid state disk.

It should be understood that the term "and/or" herein is merely one type of association relationship that describes an associated object, meaning that three relationships may exist, e.g., a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone, wherein A and B can be singular or plural. In addition, the "/" in this document generally indicates that the former and latter associated objects are in an "or" relationship, but may also indicate an "and/or" relationship, which may be understood with particular reference to the former and latter text.

In the present application, "at least one" means one or more, "a plurality" means two or more. "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items. For example, at least one (one) of a, b, or c, may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or multiple.

It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a read-only memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of communication, comprising:

a first network element receives an application identifier from a terminal;

the first network element sends the application identifier to a second network element;

the first network element receiving discovery parameters from the second network element; the discovery parameter corresponds to the application identifier;

and the first network element sends the discovery parameters to the terminal.

2. The communication method according to claim 1, wherein the terminal comprises a publishing terminal, and the discovery parameter comprises a publishing parameter for the publishing terminal to publish a proximity services (ProSe) communication request;

the communication method further comprises:

the first network element sends one or more of a discovery mode which can be used by proximity service (ProSe) and corresponds to the application identifier, an identifier of the release terminal or a first request instruction to the second network element; the first request indication is used for requesting the publishing parameters.

3. The communication method according to claim 1, wherein the terminal comprises a listening terminal, and the discovery parameter comprises a listening parameter for the listening terminal to listen for proximity services, ProSe, communication requests;

the communication method further comprises:

the first network element sends one or more of a discovery mode which can be used by proximity service (ProSe) and corresponds to the application identifier, an identifier of the monitoring terminal or a second request instruction to the second network element; the second request indication is used for requesting the listening parameters.

4. A communication method according to any one of claims 1-3, characterized in that the communication method further comprises:

the first network element receiving the validity time of the discovery parameter from the second network element;

and the first network element sends the effective time of the discovery parameter to the terminal.

5. A method of communication, comprising:

the second network element receives the corresponding relation between the application identification and the discovery parameter from the third network element;

the second network element receives the application identification from the first network element;

and the second network element sends the discovery parameters to the first network element.

6. The communication method according to claim 5, further comprising:

the second network element receives, from the third network element, a discovery pattern usable by the proximity service ProSe corresponding to the application identity and/or an identity of a terminal authorized to use the proximity service ProSe corresponding to the application identity.

7. The communication method according to claim 6, wherein the terminal comprises a publishing terminal, and the discovery parameter comprises a publishing parameter for the publishing terminal to publish a proximity services ProSe communication request;

the communication method further comprises:

the second network element receives one or more items of the discovery mode, the identifier of the issuing terminal and the first request indication from the first network element; the first request indication is used for requesting the publishing parameters.

8. The communication method according to claim 6, wherein the terminal comprises a listening terminal, and the discovery parameter comprises a listening parameter for the listening terminal to listen for proximity services (ProSe) communication requests;

the communication method further comprises:

the second network element receives one or more items of the discovery mode, the identification of the monitoring terminal and a second request indication from the first network element; the second request indication is used for requesting the listening parameters.

9. The communication method according to any one of claims 5 to 8, characterized in that the communication method further comprises:

the second network element receiving the validity time of the discovery parameter from the third network element;

and the second network element sends the effective time of the discovery parameter to the first network element.

10. A method of communication, comprising:

the third network element acquires an application identifier;

the third network element sends the application identifier and the discovery parameter to a second network element; the discovery parameter corresponds to the application identification.

11. The communication method according to claim 10, wherein the discovery parameters include a publishing parameter and a listening parameter; the publishing parameter is used for publishing the proximity service PreSe request by the terminal, and the monitoring parameter is used for monitoring the proximity service ProSe communication request monitored by the terminal.

12. The communication method according to claim 10 or 11, characterized in that the communication method further comprises:

the third network element acquires the identifier of the terminal which is authorized to use the proximity service ProSe corresponding to the application identifier;

and the third network element sends the identifier of the terminal to the second network element.

13. The communication method according to any one of claims 10 to 12, characterized in that the communication method further comprises:

the third network element acquires a discovery mode which can be used by proximity service (ProSe) corresponding to the application identifier;

the third network element sends the discovery pattern to the second network element.

14. The communication method according to any one of claims 10 to 13, characterized in that the communication method further comprises:

the third network element determines the valid time of the discovery parameter;

and the third network element sends the effective time of the discovery parameter to the second network element.

15. A communications apparatus, comprising: the device comprises a receiving module and a sending module; wherein the content of the first and second substances,

the receiving module is used for receiving the application identification from the terminal;

the sending module is configured to send the application identifier to a second network element;

the receiving module is further configured to receive a discovery parameter from the second network element; the discovery parameter corresponds to the application identifier;

the sending module is further configured to send the discovery parameter to the terminal.

16. The apparatus according to claim 15, wherein the terminal comprises a publishing terminal, and the discovery parameter comprises a publishing parameter for the publishing terminal to publish a proximity services ProSe communication request;

the sending module is further configured to send, to the second network element, one or more of a discovery pattern usable by proximity service ProSe corresponding to the application identifier, an identifier of the publishing terminal, or a first request indication; the first request indication is used for requesting the publishing parameters.

17. The communications apparatus according to claim 15, wherein the terminal comprises a listening terminal, and the discovery parameter comprises a listening parameter for the listening terminal to listen for proximity services, ProSe, communication requests;

the sending module is further configured to send, to the second network element, one or more of a discovery mode available for proximity service ProSe corresponding to the application identifier, an identifier of the monitoring terminal, or a second request instruction; the second request indication is used for requesting the listening parameters.

18. The communication device according to any of claims 15-17,

the receiving module is further configured to receive, from the second network element, the valid time of the discovery parameter;

the sending module is further configured to send the effective time of the discovery parameter to the terminal.

19. A communications apparatus, comprising: the device comprises a receiving module and a sending module; wherein the content of the first and second substances,

the receiving module is configured to receive a corresponding relationship between an application identifier and a discovery parameter from a third network element;

the receiving module is further configured to receive the application identifier from the first network element;

the sending module is configured to send the discovery parameter to the first network element.

20. The communication device of claim 19,

the receiving module is further configured to receive, from the third network element, a discovery pattern usable by the proximity service ProSe corresponding to the application identifier, and/or an identifier of a terminal authorized to use the proximity service ProSe corresponding to the application identifier.

21. The apparatus according to claim 20, wherein the terminal comprises a publishing terminal, and the discovery parameter comprises a publishing parameter for the publishing terminal to publish a proximity services ProSe communication request;

the receiving module is further configured to receive, from the first network element, one or more of the discovery mode, the identifier of the issuing terminal, and a first request indication; the first request indication is used for requesting the publishing parameters.

22. The communications apparatus of claim 20, wherein the terminal comprises a listening terminal, and wherein the discovery parameters comprise a listening parameter for the listening terminal to listen for proximity services, ProSe, communication requests;

the receiving module is further configured to receive, from the first network element, one or more of the discovery mode, the identifier of the listening terminal, and a second request indication; the second request indication is used for requesting the listening parameters.

23. The communication device according to any of claims 19-22,

the receiving module is further configured to receive, from the third network element, the valid time of the discovery parameter;

the sending module is further configured to send the valid time of the discovery parameter to the first network element.

24. A communications apparatus, comprising: the device comprises a processing module and a transmitting-receiving module; wherein the content of the first and second substances,

the processing module is used for acquiring an application identifier;

the transceiver module is configured to send the application identifier and the discovery parameter to a second network element; the discovery parameter corresponds to the application identification.

25. The communications apparatus of claim 24, wherein the discovery parameters include a publish parameter and a listen parameter; the publishing parameter is used for publishing the proximity service PreSe request by the terminal, and the monitoring parameter is used for monitoring the proximity service ProSe communication request monitored by the terminal.

26. The communication device according to claim 24 or 25,

the processing module is further configured to acquire an identifier of a terminal that is authorized to use proximity service ProSe corresponding to the application identifier;

the transceiver module is further configured to send the identifier of the terminal to the second network element.

27. The communication device according to any of claims 24-26,

the processing module is further configured to acquire a discovery mode usable by a proximity service (ProSe) corresponding to the application identifier;

the transceiver module is further configured to send the discovery pattern to the second network element.

28. The communication device according to any of claims 24-27,

the processing module is further configured to determine a valid time of the discovery parameter;

the transceiver module is further configured to send the valid time of the discovery parameter to the second network element.

29. A communication apparatus, characterized in that the communication apparatus comprises: a processor coupled with a memory;

the memory for storing a computer program;

the processor configured to execute the computer program stored in the memory to cause the communication apparatus to perform the communication method according to any one of claims 1 to 14.

30. A chip system, characterized in that the chip system comprises a processor for implementing a processing function as claimed in any of the claims 1 to 14 and an input/output port for implementing a transceiving function as claimed in any of the claims 1 to 14.

31. A computer-readable storage medium, characterized in that the computer-readable storage medium includes a program or instructions which, when run on a computer, causes the computer to perform the communication method according to any one of claims 1 to 14.

32. A computer program product, the computer program product comprising: computer program code which, when run on a computer, causes the computer to carry out the communication method according to any one of claims 1 to 14.