Communication method and apparatus

Abstract

The present application relates to the field of communications. Disclosed are a communication method and apparatus. The method comprises: a first network element sending a first request message to a sensing service control function network element, wherein the first request message is used for indicating a request to acquire first sensing data; the sensing service control function network element sending a first control message to a second network element, wherein the first control message is used for indicating the sending of the first sensing data; and the second network element sending the first sensing data, wherein the first network element may be a data requester or a network exposure function network element. In the present application, a sensing capability of a communication system can be used to acquire first sensing data, and sensing data obtained by a second network element is exposed / transmitted to a data requester, so as to provide effective data support for the data requester to implement subsequent sensing services or functions.

Description

Communication method and device

[0001] This application claims priority to Chinese patent application number 202410067424.3, filed on January 16, 2024, entitled “Communication Method and Device,” the entire contents of which are incorporated herein by reference. Technical Field

[0002] The present application relates to the field of communications, and in particular to a communication method and device. Background Art

[0003] In a communication system, the transmitter modulates electromagnetic wave signals so that they carry information about the source. During propagation, these signals are affected by the wireless environment, meaning they are modulated by the environment and thus carry environmental information. By analyzing these signals, the receiver can not only obtain the source information but also extract perceptual information reflecting the characteristics of the propagation environment. This makes integrated sensing and communication (ISAC) possible.

[0004] By utilizing the perception capabilities of the communication system to provide perception data to consumers (or users) of the perception data, effective data support can be provided for consumers to use the perception data to realize various functions and services.

[0005] Summary of the Invention

[0006] The present application provides a communication method and apparatus that can utilize the perception capability of a communication system to open / transmit perception data in the communication system to a data requester.

[0007] In a first aspect, the present application provides a communication method, which is applied to a perception service control function (SSCF) network element, and the method includes: receiving a first request message from a first network element, the first request message being used to indicate a request to obtain first perception data; and sending a first control message to a second network element, the first control message being used to indicate sending the first perception data.

[0008] Exemplarily, the method described in the first aspect can be applied to an SSCF network element, for example, the method is executed by a communication device that deploys or carries an SSCF network element, or by a device (such as a chip or software module) in a communication device that deploys or carries an SSCF network element.

[0009] In a possible scenario, the first network element may be a data requester of the perception data, such as a third-party entity or a network function (NF) network element within the network.

[0010] In another possible scenario, the first network element may also be another core network element that communicates with the data requester of the perception data, such as a network open function (NEF) network element. The data requester (such as a third-party entity) may send a request message to the NEF network element to request the first perception data. After receiving the request message from the data requester, the NEF network element may send a first request message to the SSCF network element. This application does not limit the implementation of the first network element.

[0011] In a possible scenario, the second network element may be a perception data processing function (SDPF) network element, and the first perception data may refer to the perception data processed by the SDPF network element.

[0012] In another possible scenario, the second network element may be an access network (RAN) network element serving as a receiving perception entity, and the first perception data may refer to original perception data obtained by the RAN network element or perception data processed by the RAN network element.

[0013] In one possible design, the above-mentioned first network element can be a data requester of the perception data, and the second network element can directly send the first perception data to the first network element.

[0014] In another possible design, the above-mentioned first network element may be a NEF network element, and the second network element may send the first perception data to the third-party entity through the NEF network element.

[0015] This communication method can utilize the perception capabilities of the communication system to obtain first perception data and open / transmit the perception data obtained by the second network element (receiving perception entity or SDPF network element) to a third-party entity or a data requester such as a NF network element, providing effective data support for the data requester to implement subsequent perception services or functions. Opening / transmitting the perception data to a third-party entity via the NEF network element can improve data transmission security.

[0016] Optionally, in the design in which the second network element directly sends the first perception data to the first network element, and / or when the first network element is an NEF network element, in the design in which the second network element sends the first perception data to a third-party entity through the NEF network element, the first control message is specifically used to instruct the sending of the first perception data to the first network element.

[0017] In one possible design, the method also includes: sending a first response message to the first network element, the first response message is used to indicate a first topic, the first topic is used to subscribe to the first perception data from the data communication agent (DCP) network element; the first topic is the publishing topic of the first perception data in the data communication agent network element, and the first perception data comes from the second network element.

[0018] Optionally, the first response message may be an “Nsscf_SensingService_Response” interface message.

[0019] In this design, the second network element can send the first perception data to the first network element through the DCP network element. The second network element can be an SDPF network element or a RAN network element serving as a receiving perception entity, and the first network element can be an NEF network element or a data requester (e.g., a third-party entity). For example, the second network element can send the first perception data to the DCP network element according to the first topic. That is, the first perception data is published in the DCP network element according to the first topic. The first network element can obtain the first perception data from the DCP network element according to the first topic. The first topic can be sent by the SSCF network element to the first network element.

[0020] In this design, when exposing or transmitting sensor data to data requesters (such as third-party entities), DCP network elements can be used to improve data transmission efficiency. In addition, DCP network elements can support multiple transmission protocols to meet the needs of different business scenarios.

[0021] Optionally, in the design in which the above-mentioned second network element sends the first perception data to the first network element through the DCP network element, the first control message is specifically used to instruct the first perception data to be published to the data communication agent network element according to the first topic.

[0022] The second network element can know, based on the instruction of the first control message, that the first perception data needs to be published to the DCP network element according to the first topic.

[0023] In one possible design, the method also includes: sending a first response message to the first network element, the first response message is used to indicate a first data access address; the first data access address is provided by the second network element and is used to obtain the first perception data.

[0024] In this design, the first network element can be a NEF network element or a third-party entity. The second network element can provide a first data access address as an interface for accessing the first perception data. The second network element can be an SDPF network element or a RAN network element serving as a receiving perception entity. The third-party entity can obtain the first data access address. The third-party entity can actively obtain the first perception data by accessing the first data access address. Exemplarily, the third-party entity can flexibly choose the time to actively obtain the first perception data according to demand. For example, the third-party entity can choose the appropriate time to send the first access request according to its own traffic conditions to avoid excessive data volume and inability to bear the traffic.

[0025] In another possible design, the method also includes: sending a first response message to the first network element, the first response message is used to indicate a first data access address; the first data access address is provided by a user plane function (UPF) network element and is used to obtain first perception data, and the first perception data in the user plane function network element comes from the second network element.

[0026] In this design, the first network element can be a NEF network element or a third-party entity. The UPF network element can provide a first data access address as an interface for accessing the first perception data. The second network element can be an SDPF network element or a RAN network element serving as a receiving perception entity. The third-party entity can obtain the first data access address. The third-party entity can actively obtain the first perception data by accessing the first data access address. Exemplarily, the third-party entity can flexibly choose the time to actively obtain the first perception data according to demand. For example, the third-party entity can choose the appropriate time to send the first access request according to its own traffic conditions to avoid excessive data volume and inability to bear the traffic.

[0027] Optionally, in the design where the first data access address is provided by the second network element, the first control message is specifically used to instruct the first data access address to be used as an interface for obtaining the first perception data. In other words, the first control message can specifically instruct the second network element to provide the data access address as an interface for obtaining the first perception data.

[0028] Optionally, in the design where the above-mentioned first data access address is provided by a user plane functional network element, the first control message is specifically used to instruct sending the first perception data to the user plane functional network element.

[0029] Optionally, in a design where the first data access address is provided by a user plane function network element, the method may further include: sending a second control message to the user plane function network element, the second control message being used to instruct the UPF network element to use the first data access address as an interface for obtaining the first perception data. Alternatively, the second control message may specifically instruct the UPF network element to provide the data access address as an interface for obtaining the first perception data.

[0030] Optionally, in the design where the above-mentioned first data access address is provided by a user plane functional network element, the method may further include: receiving a second control response message from the user plane functional network element, the second control response message being used to indicate the first data access address.

[0031] Exemplarily, the first data access address may be sent by the UPF network element to the SSCF network element.

[0032] Optionally, in the design where the above-mentioned first data access address is provided by the second network element, the method may further include: receiving a first control response message from the second network element, the first control response message being used to indicate the first data access address.

[0033] Exemplarily, the first data access address may be sent by the second network element to the SSCF network element.

[0034] In one possible design, the first request message is also used to indicate a first data push address provided by a third-party entity, and the first control message is also used to indicate the first data push address; the first data push address is used by the second network element to send the first perception data.

[0035] In this design, the first network element can be an NEF network element or a third-party entity. The second network element can be an SDPF network element or a RAN network element serving as a receiving perception entity. The third-party entity can provide a first data push address, and the second network element can send the first perception data to the third-party entity by sending the first perception data to the first data push address. The third-party entity can passively receive the first perception data from the second network element using the first data push address.

[0036] In another possible design, the first request message is further used to indicate a first data push address provided by the third-party entity, and the first control message is further used to indicate the first data push address. The first data push address is used by the user plane function network element to send the first perception data, and the first perception data in the user plane function network element comes from the second network element.

[0037] In this design, the first network element can be an NEF network element or a third-party entity. The second network element can be an SDPF network element or a RAN network element serving as a receiving perception entity. The third-party entity can provide a first data push address, and the UPF network element can send the first perception data to the third-party entity by sending the first perception data to the first data push address. The third-party entity can passively receive the first perception data sent by the UPF network element using the first data push address. The first perception data in the UPF network element originates from the second network element.

[0038] Optionally, the above-mentioned third-party entity provides a first data push address, and in the design in which the second network element sends the first perception data to the first data push address, the first data push address is used by the second network element to send the first perception data, and the first control message is specifically used to instruct the sending of the first perception data to the first data push address.

[0039] Optionally, the above-mentioned third-party entity provides a first data push address, and in the design in which the UPF network element sends the first perception data to the first data push address, the first data push address is used by the UPF network element to send the first perception data, and the first control message is specifically used to instruct the UPF network element to send the first perception data.

[0040] Optionally, in a design where the third-party entity provides a first data push address and the UPF network element sends the first perception data to the first data push address, the method may further include: sending a second control message to the user plane function network element, where the second control message is used to instruct the UPF network element to send the first perception data to the first data push address. Alternatively, the second network element may instruct the UPF network element to send the first perception data to the first data push address.

[0041] In one possible design, the method also includes: sending a first response message to the first network element, the first response message being used to indicate obtaining first perception data from a data analysis repository function (ADRF) network element, the first perception data in the data analysis repository function network element coming from the second network element.

[0042] In this design, the first network element can be a NF network element within the network. The second network element can be an SDPF network element or a RAN network element serving as a receiving perception entity. The second network element can store the first perception data in an ADRF network element, and the NF network element obtains the first perception data from the ADRF network element.

[0043] Optionally, in the design where the second network element stores the first perception data in the ADRF network element and the NF network element obtains the first perception data from the ADRF network element, the first control message is specifically used to instruct the first perception data to be sent to the data analysis repository function network element. The second network element may be aware of the need to send the first perception data to the ADRF network element based on the instruction of the first control message.

[0044] Optionally, in the design in which the second network element sends the first perception data to the first network element or the DCP network element, or in the design in which the first data access address is provided by the second network element or the UPF network element, or in the design in which a third-party entity provides the first data push address and the second network element or the UPF network element sends the first perception data to the first data push address, the first network element may be a network open function network element or a third-party entity.

[0045] Optionally, in the design in which the above-mentioned second network element stores the first perception data to the ADRF network element and the NF network element obtains the first perception data from the ADRF network element, the first network element may be a network function network element.

[0046] Optionally, in any of the above designs, the second network element is an access network element or a perception data processing function network element.

[0047] Optionally, the first request message may include one or more of the following perception information: perception user ID, perception service type, perception area, security requirements, perception accuracy requirements, event reporting duration, reporting interval, maximum sampling interval, start time, end time, priority, etc. The perception user ID may indicate the identity information of the data requester (e.g., a third-party entity), such as the identifier of the third-party entity.

[0048] Optionally, the first request message may be an “Nsscf_SensingService_Request” interface message.

[0049] In a second aspect, the present application provides a communication device having the functionality to implement the method described in the first aspect. The functionality can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the functionality of the method described in the first aspect, such as a receiving unit, a sending unit, and the like.

[0050] Exemplarily, the communication device may be applied to a sensor service control function network element. For example, the communication device may be a communication device that deploys or carries an SSCF network element, or may be a device (e.g., a chip or software module) in a communication device that deploys or carries an SSCF network element.

[0051] The receiving unit is used to receive a first request message from a first network element, where the first request message is used to indicate a request to obtain first perception data.

[0052] A sending unit is used to send a first control message to the second network element, where the first control message is used to instruct the sending of first perception data.

[0053] In one possible design, the sending unit is specifically used to send first perception data to a first network element, where the first network element is a data requester (such as a third-party entity) or an NEF network element, and the first control message is specifically used to instruct the sending of the first perception data to the first network element.

[0054] In one possible design, the second network element sends the first perception data to the first network element via the DCP network element. The sending unit is further configured to send a first response message to the first network element. The first response message is configured to indicate a first topic, where the first topic is used to subscribe the first perception data to a data communication proxy (DCP) network element; the first topic is a publishing topic for the first perception data in the data communication proxy network element, and the first perception data comes from the second network element.

[0055] Optionally, in the design in which the above-mentioned second network element sends the first perception data to the first network element through the DCP network element, the first control message is specifically used to instruct the first perception data to be published to the data communication agent network element according to the first topic.

[0056] In one possible design, the second network element may provide a first data access address as an interface for accessing the first perception data. The sending unit is further configured to send a first response message to the first network element. The first response message is configured to indicate the first data access address; the first data access address is provided by the second network element and is used to obtain the first perception data.

[0057] In another possible design, the UPF network element may provide a first data access address as an interface for accessing the first perception data. The sending unit is further configured to send a first response message to the first network element. The first response message indicates the first data access address; the first data access address is provided by the user plane function (UPF) network element and is used to obtain the first perception data, where the first perception data in the user plane function network element comes from the second network element.

[0058] Optionally, in the design where the first data access address is provided by the second network element, the first control message is specifically used to instruct the first data access address to be used as an interface for obtaining the first perception data. In other words, the first control message can specifically instruct the second network element to provide the data access address as an interface for obtaining the first perception data.

[0059] Optionally, in the design where the above-mentioned first data access address is provided by a user plane functional network element, the first control message is specifically used to instruct sending the first perception data to the user plane functional network element.

[0060] Optionally, in a design where the first data access address is provided by a user plane function network element, the sending unit is further configured to send a second control message to the user plane function network element. The second control message is configured to instruct the UPF network element to use the first data access address as an interface for obtaining the first perception data. In other words, the second control message may specifically instruct the UPF network element to provide the data access address as an interface for obtaining the first perception data.

[0061] Optionally, in the design where the above-mentioned first data access address is provided by a user plane functional network element, the receiving unit is further used to receive a second control response message from the user plane functional network element, where the second control response message is used to indicate the first data access address.

[0062] Optionally, in the design where the first data access address is provided by the second network element, the receiving unit is further used to receive a first control response message from the second network element, where the first control response message is used to indicate the first data access address.

[0063] In one possible design, the first request message is also used to indicate a first data push address provided by a third-party entity, and the first control message is also used to indicate the first data push address; the first data push address is used by the second network element to send the first perception data.

[0064] In another possible design, the first request message is further used to indicate a first data push address provided by the third-party entity, and the first control message is further used to indicate the first data push address. The first data push address is used by the user plane function network element to send the first perception data, and the first perception data in the user plane function network element comes from the second network element.

[0065] Optionally, the above-mentioned third-party entity provides a first data push address, and in the design in which the second network element sends the first perception data to the first data push address, the first data push address is used by the second network element to send the first perception data, and the first control message is specifically used to instruct the sending of the first perception data to the first data push address.

[0066] Optionally, the above-mentioned third-party entity provides a first data push address, and in the design in which the UPF network element sends the first perception data to the first data push address, the first data push address is used by the UPF network element to send the first perception data, and the first control message is specifically used to instruct the UPF network element to send the first perception data.

[0067] Optionally, in the design where the third-party entity provides a first data push address and the UPF network element sends the first perception data to the first data push address, the sending unit is further configured to send a second control message to the user plane function network element. The second control message is used to instruct the UPF network element to send the first perception data to the first data push address. Alternatively, the second network element may instruct the UPF network element to send the first perception data to the first data push address.

[0068] In one possible design, the first network element may be a NF network element within the network. The second network element may store the first perception data in an ADRF network element, and the NF network element obtains the first perception data from the ADRF network element.

[0069] The sending unit is further configured to send a first response message to the first network element. The first response message is used to instruct the acquisition of first perception data from a data analysis repository function (ADRF) network element, where the first perception data in the data analysis repository function network element comes from the second network element.

[0070] Optionally, in the design where the second network element stores the first perception data in the ADRF network element and the NF network element obtains the first perception data from the ADRF network element, the first control message is specifically used to instruct the first perception data to be sent to the data analysis repository function network element. The second network element may be aware of the need to send the first perception data to the ADRF network element based on the instruction of the first control message.

[0071] Optionally, in the design in which the second network element sends the first perception data to the first network element or the DCP network element, or in the design in which the first data access address is provided by the second network element or the UPF network element, or in the design in which a third-party entity provides the first data push address and the second network element or the UPF network element sends the first perception data to the first data push address, the first network element may be a network open function network element or a third-party entity.

[0072] Optionally, in the design in which the above-mentioned second network element stores the first perception data to the ADRF network element and the NF network element obtains the first perception data from the ADRF network element, the first network element may be a network function network element.

[0073] Optionally, in any of the above designs, the second network element is an access network element or a perception data processing function network element.

[0074] In a third aspect, the present application also provides a communication device, comprising: a processor for executing computer instructions stored in a memory, so that when the computer instructions are executed, the device executes the method described in the first aspect or any possible design of the first aspect.

[0075] In a fourth aspect, the present application also provides a communication device, comprising: a processor and an interface circuit, the processor being used to communicate with other devices through the interface circuit and execute the method described in the first aspect or any possible design of the first aspect.

[0076] Illustratively, in the third aspect and the fourth aspect, the processor is configured to execute the method described in the first aspect or any possible design of the first aspect.

[0077] The communication device described in the second to fourth aspects above may be a communication device that deploys or carries an SSCF network element, or may be a device in a communication device that deploys or carries an SSCF network element.

[0078] In a fifth aspect, the present application further provides a computer-readable storage medium comprising: computer software instructions, or instructions; when the computer software instructions are executed, the method described in the first aspect or any possible design of the first aspect is implemented. For example, when the computer software instructions are executed in a communication device or an apparatus built into the communication device, the communication device implements the method described in the first aspect or any possible design of the first aspect.

[0079] It can be understood that the beneficial effects that can be achieved by the second to fifth aspects provided above can refer to the beneficial effects in the first aspect and any possible design thereof, and will not be repeated here.

[0080] In a sixth aspect, the present application provides a communication method, applied to a second network element, the method comprising: receiving a first control message from a perception service control function network element, the first control message being used to instruct sending first perception data. Sending the first perception data.

[0081] Exemplarily, the method described in the sixth aspect can be applied to the second network element, for example, the method is executed by a communication device that deploys or carries the second network element, or by a device (such as a chip or software module) in the communication device that deploys or carries the second network element.

[0082] In a possible scenario, the second network element may be a perception data processing function (SDPF) network element, and the first perception data may refer to the perception data processed by the SDPF network element.

[0083] In another possible scenario, the second network element may be an access network (RAN) network element serving as a receiving perception entity, and the first perception data may refer to original perception data obtained by the RAN network element or perception data processed by the RAN network element.

[0084] In one possible design, the sending of the first perception data may include: sending the first perception data to the first network element.

[0085] In a possible scenario, the first network element may be a data requester of the perception data, such as a third-party entity or a network function (NF) network element within the network. The second network element may directly send the first perception data to the first network element.

[0086] In another possible scenario, the first network element may also be another core network element that communicates with the data requester of the perception data, such as a network open function (NEF) network element. The data requester (e.g., a third-party entity) may send a request message to the NEF network element to request the first perception data. After receiving the request message from the data requester, the NEF network element may send the first request message to the SSCF network element. The second network element may send the first perception data to the third-party entity via the NEF network element.

[0087] This application does not limit the implementation of the first network element and the second network element.

[0088] This communication method can utilize the perception capabilities of the communication system to obtain first perception data and open / transmit the perception data obtained by the second network element (receiving perception entity or SDPF network element) to a third-party entity or a data requester such as a NF network element, providing effective data support for the data requester to implement subsequent perception services or functions. Opening / transmitting the perception data to a third-party entity via the NEF network element can improve data transmission security.

[0089] Optionally, in the design in which the second network element directly sends the first perception data to the first network element, and / or when the first network element is an NEF network element, in the design in which the second network element sends the first perception data to a third-party entity through the NEF network element, the first control message is specifically used to instruct the sending of the first perception data to the first network element.

[0090] In one possible design, the sending of the first perception data includes: sending the first perception data to the data communication agent network element according to the first topic.

[0091] In this design, the second network element can send the first perception data to the first network element through the DCP network element. The second network element can be an SDPF network element or a RAN network element serving as a receiving perception entity, and the first network element can be an NEF network element or a data requester (e.g., a third-party entity). For example, the second network element can send the first perception data to the DCP network element according to the first topic. That is, the first perception data is published in the DCP network element according to the first topic. The first network element can obtain the first perception data from the DCP network element according to the first topic. The first topic can be sent by the SSCF network element to the first network element.

[0092] In this design, when exposing or transmitting sensor data to data requesters (such as third-party entities), DCP network elements can be used to improve data transmission efficiency. In addition, DCP network elements can support multiple transmission protocols to meet the needs of different business scenarios.

[0093] Optionally, in the design in which the above-mentioned second network element sends the first perception data to the first network element through the DCP network element, the first control message is specifically used to instruct the first perception data to be published to the data communication agent network element according to the first topic.

[0094] The second network element can know, based on the instruction of the first control message, that the first perception data needs to be published to the DCP network element according to the first topic.

[0095] In one possible design, the sending of the first perception data includes: using a first data access address as an interface for obtaining the first perception data, and the first data access address is provided by the second network element.

[0096] In this design, the second network element can provide a first data access address as an interface for accessing the first perception data. The second network element can be an SDPF network element or a RAN network element serving as a receiving perception entity. A third-party entity can obtain the first data access address. The third-party entity can actively obtain the first perception data by accessing the first data access address. Exemplarily, the third-party entity can flexibly choose the time to actively obtain the first perception data based on demand. For example, the third-party entity can choose an appropriate time to send the first access request based on its own traffic conditions to avoid excessive data volume and inability to bear the traffic.

[0097] Optionally, in the design where the first data access address is provided by the second network element, the first control message is specifically used to instruct the first data access address to be used as an interface for obtaining the first perception data. In other words, the first control message can specifically instruct the second network element to provide the data access address as an interface for obtaining the first perception data.

[0098] Optionally, in the design where the above-mentioned first data access address is provided by the second network element, the method may further include: sending a first control response message to the perception service control function network element, where the first control response message is used to indicate the first data access address.

[0099] Exemplarily, the first data access address may be sent by the second network element to the SSCF network element.

[0100] In another possible design, the sending of the first perception data includes: sending the first perception data to a user plane functional network element.

[0101] In this design, the second network element can send the first perception data to the UPF network element. The UPF network element can provide a first data access address as an interface for accessing the first perception data. The second network element can be an SDPF network element or a RAN network element serving as a receiving perception entity. A third-party entity can obtain the first data access address. The third-party entity can actively obtain the first perception data by accessing the first data access address. Exemplarily, the third-party entity can flexibly choose the time to actively obtain the first perception data based on demand. For example, the third-party entity can choose an appropriate time to send the first access request based on its own traffic conditions to avoid excessive data volume and inability to bear the traffic.

[0102] Alternatively, in this design, the second network element can send the first perception data to the UPF network element. The second network element can be an SDPF network element or a RAN network element serving as a receiving perception entity. A third-party entity can provide a first data push address, and the UPF network element can send the first perception data to the third-party entity by sending the first perception data to the first data push address. The third-party entity can use the first data push address to passively receive the first perception data sent by the UPF network element. The first perception data in the UPF network element originates from the second network element.

[0103] Optionally, in the design where the above-mentioned first data access address is provided by a user plane functional network element, the first control message is specifically used to instruct sending the first perception data to the user plane functional network element.

[0104] In one possible design, the sending of the first perception data to the user plane functional network element includes: sending the first perception data to the user plane functional network element through a General Packet Radio Service Tunneling Protocol-User Plane (GTPU) tunnel.

[0105] Optionally, in the design where the second network element sends the first perception data to the UPF network element, the third-party entity provides a first data push address, and the UPF network element sends the first perception data to the first data push address, the first control message is further used to indicate the first data push address provided by the third-party entity. The data packet of the first perception data sent by the second network element to the user plane function network element is encapsulated with the first data push address, and the first data push address is used by the user plane function network element to send the first perception data.

[0106] In a possible design, the first control message is further used to indicate a first data push address provided by a third-party entity. The sending of the first perception data includes: sending the first perception data to the first data push address.

[0107] In this design, the second network element can be an SDPF network element or a RAN network element serving as a receiving perception entity. A third-party entity can provide a first data push address, and the second network element can send the first perception data to the third-party entity by sending the first perception data to the first data push address. The third-party entity can passively receive the first perception data from the second network element using the first data push address.

[0108] Optionally, the above-mentioned third-party entity provides a first data push address, and in the design in which the second network element sends the first perception data to the first data push address, the first data push address is used by the second network element to send the first perception data, and the first control message is specifically used to instruct the sending of the first perception data to the first data push address.

[0109] In one possible design, the sending of the first perception data includes: sending the first perception data to a data analysis repository functional network element.

[0110] In this design, the second network element can be an SDPF network element or a RAN network element serving as a receiving perception entity. The second network element can store the first perception data in an ADRF network element, and the NF network element obtains the first perception data from the ADRF network element.

[0111] Optionally, in the design where the second network element stores the first perception data in the ADRF network element and the NF network element obtains the first perception data from the ADRF network element, the first control message is specifically used to instruct the first perception data to be sent to the data analysis repository function network element. The second network element may be aware of the need to send the first perception data to the ADRF network element based on the instruction of the first control message.

[0112] Optionally, the first network element is a network open function network element or a third-party entity.

[0113] Optionally, the above-mentioned second network element is an access network element or a perception data processing function network element.

[0114] Optionally, when the second network element is an SDPF network element, the perception data in the SDPF network element comes from a RAN network element serving as a receiving perception entity. The RAN network element serving as the receiving perception entity may send the perception data to the SDPF network element. The perception data received by the SDPF network element may be raw perception data obtained by the RAN network element or perception data processed by the RAN network element.

[0115] In one possible design, when the RAN network element serving as a receiving perception entity sends perception data to the SDPF network element, it may also send the perception data to the SDPF network element through the DCP network element in a topic publishing and subscription manner.

[0116] In a seventh aspect, the present application provides a communication device having the functionality to implement the method described in the sixth aspect. The functionality can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the functionality of the method described in the sixth aspect, such as a receiving unit, a sending unit, and the like.

[0117] Exemplarily, the communication device may be applied to the second network element. For example, the communication device may be a communication device that deploys or carries the second network element, or may be a device (such as a chip or software module) in the communication device that deploys or carries the second network element.

[0118] Among them, the receiving unit is used to receive a first control message from the perception service control function network element, and the first control message is used to instruct the sending of first perception data.

[0119] A sending unit, used to send first perception data.

[0120] In one possible design, the sending unit is specifically used to send first perception data to the first network element.

[0121] Optionally, the first control message is specifically used to instruct sending first perception data to the first network element.

[0122] In one possible design, the sending unit is specifically used to send first perception data to the data communication agent network element according to the first topic.

[0123] Optionally, the first control message is specifically used to instruct to publish the first perception data to the data communication agent network element according to the first topic.

[0124] In one possible design, the sending unit is specifically used to use the first data access address as an interface for obtaining the first perception data, and the first data access address is provided by the second network element.

[0125] Optionally, the first control message is specifically used to instruct the first data access address to be used as an interface for obtaining the first perception data. In other words, the first control message may specifically instruct the second network element to provide a data access address as an interface for obtaining the first perception data.

[0126] Optionally, in the design where the above-mentioned first data access address is provided by the second network element, the sending unit is further used to send a first control response message to the perception service control function network element, and the first control response message is used to indicate the first data access address.

[0127] In another possible design, the sending unit is specifically used to send first perception data to the user plane functional network element.

[0128] Optionally, the first control message is specifically used to instruct sending first perception data to the user plane functional network element.

[0129] In one possible design, the sending unit is specifically used to send the first perception data to the user plane functional network element through a General Packet Radio Service Tunneling Protocol-User Plane (GTPU) tunnel.

[0130] Optionally, the first control message is further used to indicate a first data push address provided by a third-party entity. The data packet of the first perception data sent by the second network element to the user plane function network element is encapsulated with the first data push address, and the first data push address is used by the user plane function network element to send the first perception data.

[0131] In a possible design, the first control message is further used to indicate a first data push address provided by a third-party entity. The sending unit is specifically used to send the first perception data to the first data push address.

[0132] Optionally, the first data push address is used by the second network element to send the first perception data, and the first control message is specifically used to instruct the first perception data to be sent to the first data push address.

[0133] In one possible design, the sending unit is specifically used to send first perception data to a data analysis repository functional network element.

[0134] Optionally, the first control message is specifically used to instruct sending first perception data to a data analysis repository functional network element.

[0135] Optionally, the first network element is a network open function network element or a third-party entity.

[0136] Optionally, the above-mentioned second network element is an access network element or a perception data processing function network element.

[0137] In an eighth aspect, the present application also provides a communication device, comprising: a processor for executing computer instructions stored in a memory, so that when the computer instructions are executed, the device executes the method described in the sixth aspect or any possible design of the sixth aspect.

[0138] In the ninth aspect, the present application also provides a communication device, comprising: a processor and an interface circuit, the processor being used to communicate with other devices through the interface circuit and execute the method described in the sixth aspect or any possible design of the sixth aspect.

[0139] Illustratively, in the eighth and ninth aspects, the processor is configured to execute the method described in the sixth aspect or any possible design of the sixth aspect.

[0140] The communication device described in the seventh to ninth aspects above may be a communication device that deploys or carries the second network element, or may be a device in a communication device that deploys or carries the second network element.

[0141] In a tenth aspect, the present application further provides a computer-readable storage medium comprising: computer software instructions, or instructions; when the computer software instructions are executed, the method described in the sixth aspect or any possible design of the sixth aspect is implemented. For example, when the computer software instructions are executed in a communication device or an apparatus built into the communication device, the communication device implements the method described in the sixth aspect or any possible design of the sixth aspect.

[0142] It can be understood that the beneficial effects that can be achieved in the seventh to tenth aspects provided above can be referred to the beneficial effects in the sixth aspect and any possible design thereof, and will not be repeated here.

[0143] In an eleventh aspect, the present application provides a communication method, the method being applied to a first network element, the method comprising: sending a first request message to a perception service control function network element, the first request message being used to indicate a request to obtain first perception data; and receiving the first perception data from a second network element.

[0144] Exemplarily, the method described in the eleventh aspect can be applied to the first network element, for example, the method is executed by a communication device that deploys or carries the first network element, or by a device (such as a chip or software module) in the communication device that deploys or carries the first network element.

[0145] In a possible scenario, the first network element may be a data requester of the perception data, such as a third-party entity or a network function (NF) network element within the network.

[0146] In another possible scenario, the first network element may also be another core network element that communicates with the data requester of the perception data, such as a network open function (NEF) network element. The data requester (such as a third-party entity) may send a request message to the NEF network element to request the first perception data. After receiving the request message from the data requester, the NEF network element may send a first request message to the SSCF network element. This application does not limit the implementation of the first network element.

[0147] In a possible scenario, the second network element may be a perception data processing function (SDPF) network element, and the first perception data may refer to the perception data processed by the SDPF network element.

[0148] In another possible scenario, the second network element may be an access network (RAN) network element serving as a receiving perception entity, and the first perception data may refer to original perception data obtained by the RAN network element or perception data processed by the RAN network element.

[0149] This communication method can utilize the perception capabilities of the communication system to obtain first perception data and open / transmit the perception data obtained by the second network element (receiving perception entity or SDPF network element) to a third-party entity or a data requester such as a NF network element, providing effective data support for the data requester to implement subsequent perception services or functions. Opening / transmitting the perception data to a third-party entity via the NEF network element can improve data transmission security.

[0150] In one possible design, the method further includes: receiving a first response message from a perception service control function network element, the first response message being used to indicate the first topic; sending a subscription request message to a data communication proxy network element, the subscription request message being used to indicate the first topic and being used to subscribe to the first perception data from the data communication proxy network element; receiving a subscription response message from the data communication proxy network element; and receiving the first perception data from the second network element, including receiving the first perception data sent by the data communication proxy network element, the first perception data being from the second network element.

[0151] In this design, the second network element can send the first perception data to the first network element through the DCP network element. The second network element can be an SDPF network element or a RAN network element serving as a receiving perception entity, and the first network element can be an NEF network element or a data requester (e.g., a third-party entity). For example, the second network element can send the first perception data to the DCP network element according to the first topic. That is, the first perception data is published in the DCP network element according to the first topic. The first network element can obtain the first perception data from the DCP network element according to the first topic. The first topic can be sent by the SSCF network element to the first network element.

[0152] In this design, when exposing or transmitting sensor data to data requesters (such as third-party entities), DCP network elements can be used to improve data transmission efficiency. In addition, DCP network elements can support multiple transmission protocols to meet the needs of different business scenarios.

[0153] Optionally, the first network element is a network open function network element or a third-party entity. When the first network element is a network open function network element, the method further includes: sending the first perception data to the third-party entity.

[0154] In one possible design, the first network element is a third-party entity, and the method further includes: receiving a first response message from a perception service control function network element, the first response message being used to indicate a first data access address, the first data access address being provided by a second network element or a user plane function network element. According to the first data access address, a first access request is sent, the first access request being used to request acquisition of first perception data. Receiving the first perception data from the second network element includes: receiving a first access response message, the first access response message including the first perception data, the first perception data being from the second network element.

[0155] In this design, the first network element may be a third-party entity. The second network element may provide a first data access address as an interface for accessing the first perception data. The second network element may be an SDPF network element or a RAN network element serving as a receiving perception entity. The third-party entity may obtain the first data access address. The third-party entity may actively obtain the first perception data by accessing the first data access address. Exemplarily, the third-party entity may flexibly choose the time to actively obtain the first perception data based on demand. For example, the third-party entity may choose an appropriate time to send the first access request based on its own traffic conditions to avoid excessive data volume and inability to bear the traffic.

[0156] Alternatively, in this design, the first network element may be a third-party entity. The UPF network element may provide a first data access address as an interface for accessing the first perception data. The second network element may be an SDPF network element or a RAN network element serving as a receiving perception entity. The third-party entity may obtain the first data access address. The third-party entity may actively obtain the first perception data by accessing the first data access address. Exemplarily, the third-party entity may flexibly choose the time to actively obtain the first perception data based on demand. For example, the third-party entity may choose an appropriate time to send the first access request based on its own traffic conditions to avoid excessive data volume and inability to bear the traffic.

[0157] In one possible design, the first network element is a third-party entity, and the first request message is further used to indicate a first data push address provided by the third-party entity; the first data push address is used by the second network element to send the first perception data; or the first data push address is used by a user plane function network element to send the first perception data, and the first perception data in the user plane function network element comes from the second network element. Receiving the first perception data from the second network element includes: receiving the first perception data from the first data push address.

[0158] In this design, the first network element can be a third-party entity. The second network element can be an SDPF network element or a RAN network element serving as a receiving perception entity. The third-party entity can provide a first data push address, and the second network element can send the first perception data to the third-party entity by sending the first perception data to the first data push address. The third-party entity can passively receive the first perception data from the second network element using the first data push address.

[0159] Alternatively, in this design, the first network element can be a third-party entity. The second network element can be an SDPF network element or a RAN network element serving as a receiving perception entity. The third-party entity can provide a first data push address, and the UPF network element can send the first perception data to the third-party entity by sending the first perception data to the first data push address. The third-party entity can passively receive the first perception data sent by the UPF network element using the first data push address. The first perception data in the UPF network element originates from the second network element.

[0160] In one possible design, the first network element is a network function network element, and the method further includes: receiving a first response message from a perception service control function network element, the first response message being used to instruct the acquisition of first perception data from a data analysis repository function network element. Sending a perception data request message to the data analysis repository function network element, the perception data request message being used to request the acquisition of the first perception data. Receiving the first perception data from the second network element includes: receiving a perception data response message from the data analysis repository function network element, the perception data response message including the first perception data. The first perception data in the data analysis repository function network element comes from the second network element.

[0161] In this design, the first network element can be a NF network element within the network. The second network element can be an SDPF network element or a RAN network element serving as a receiving perception entity. The second network element can store the first perception data in an ADRF network element, and the NF network element obtains the first perception data from the ADRF network element.

[0162] Optionally, the second network element is an access network element or a perception data processing function network element.

[0163] In a twelfth aspect, the present application provides a communication device having the functionality to implement the method described in the eleventh aspect. The functionality can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the functionality of the method described in the eleventh aspect, such as a transmitting unit, a receiving unit, etc.

[0164] Exemplarily, the communication device may be applied to a first network element. For example, the communication device may be a communication device deployed or carrying the first network element, or may be a device (eg, a chip or software module) in a communication device deployed or carrying the first network element.

[0165] Among them, the sending unit is used to send a first request message to the perception service control function network element, and the first request message is used to indicate a request to obtain first perception data.

[0166] A receiving unit is used to receive first perception data from a second network element.

[0167] In one possible design, the receiving unit is further configured to receive a first response message from the perception service control function network element, the first response message being used to indicate the first topic. The sending unit is further configured to send a subscription request message to the data communication proxy network element, the subscription request message being used to indicate the first topic and being used to subscribe to the first perception data from the data communication proxy network element. The receiving unit is further configured to receive a subscription response message from the data communication proxy network element. The receiving unit is specifically configured to receive the first perception data sent by the data communication proxy network element, the first perception data being from the second network element.

[0168] Optionally, the first network element is a network open function network element or a third-party entity. When the first network element is a network open function network element, the sending unit is further configured to send the first sensing data to the third-party entity.

[0169] In one possible design, the first network element is a third-party entity, and the receiving unit is further configured to receive a first response message from the perception service control function network element, where the first response message is used to indicate a first data access address, where the first data access address is provided by the second network element or the user plane function network element. The sending unit is further configured to send a first access request based on the first data access address, where the first access request is used to request acquisition of the first perception data.

[0170] The receiving unit is specifically configured to receive a first access response message, where the first access response message includes first perception data, and the first perception data comes from the second network element.

[0171] In one possible design, the first network element is a third-party entity, and the first request message is also used to indicate a first data push address provided by the third-party entity; the first data push address is used by the second network element to send the first perception data; or, the first data push address is used by the user plane function network element to send the first perception data, and the first perception data in the user plane function network element comes from the second network element.

[0172] The receiving unit is specifically configured to receive first perception data from a first data push address.

[0173] In one possible design, the first network element is a network function network element, and the receiving unit is further configured to receive a first response message from the perception service control function network element, where the first response message is used to instruct the acquisition of the first perception data from the data analysis repository function network element. The sending unit is further configured to send a perception data request message to the data analysis repository function network element, where the perception data request message is used to request the acquisition of the first perception data.

[0174] The receiving unit is specifically configured to receive a perception data response message from a data analysis and storage repository functional network element, wherein the perception data response message includes first perception data. The first perception data in the data analysis and storage repository functional network element comes from a second network element.

[0175] Optionally, the second network element is an access network element or a perception data processing function network element.

[0176] In the thirteenth aspect, the present application also provides a communication device, including: a processor for executing computer instructions stored in a memory, when the computer instructions are executed, the device executes the method described in the eleventh aspect or any possible design of the eleventh aspect.

[0177] In the fourteenth aspect, the present application also provides a communication device, including: a processor and an interface circuit, the processor is used to communicate with other devices through the interface circuit, and execute the method described in the eleventh aspect or any possible design of the eleventh aspect.

[0178] Illustratively, in the thirteenth aspect and the fourteenth aspect, the processor is configured to execute the method described in the eleventh aspect or any possible design of the eleventh aspect.

[0179] The communication device described in the above aspects 12 to 14 may be a communication device that deploys or carries the first network element, or may be a device in the communication device that deploys or carries the first network element.

[0180] In a fifteenth aspect, the present application further provides a computer-readable storage medium comprising: computer software instructions, or instructions; when the computer software instructions are executed, the method described in the eleventh aspect or any possible design of the eleventh aspect is implemented. For example, when the computer software instructions are executed in a communication device or a device (e.g., a chip) built into the communication device, the communication device implements the method described in the eleventh aspect or any possible design of the eleventh aspect.

[0181] It can be understood that the beneficial effects that can be achieved in the twelfth to fifteenth aspects provided above can be referred to the beneficial effects in the eleventh aspect and any possible design thereof, and will not be repeated here.

[0182] In a sixteenth aspect, the present application provides a communication method, the method being applied to a network open function network element, the method comprising: sending a first request message to a perception service control function network element, the first request message being used to indicate a request to obtain first perception data; receiving a first response message from the perception service control function network element, the first response message being used to indicate a first data access address, the first data access address being provided by a second network element or a user plane function network element and being used to obtain the first perception data; and sending the first data access address to a third-party entity.

[0183] Exemplarily, the method described in aspect 16 can be applied to a NEF network element, for example, the method is executed by a communication device that deploys or carries the NEF network element, or by a device (such as a chip or software module) in a communication device that deploys or carries the NEF network element.

[0184] In a possible scenario, the second network element may be a perception data processing function (SDPF) network element, and the first perception data may refer to the perception data processed by the SDPF network element.

[0185] In another possible scenario, the second network element may be an access network (RAN) network element serving as a receiving perception entity, and the first perception data may refer to original perception data obtained by the RAN network element or perception data processed by the RAN network element.

[0186] In this communication method, the first network element may be a NEF network element. The second network element may provide a first data access address as an interface for accessing the first perception data. The second network element may be an SDPF network element or a RAN network element serving as a receiving perception entity. A third-party entity may obtain the first data access address. The third-party entity may actively obtain the first perception data by accessing the first data access address. Exemplarily, the third-party entity may flexibly choose the time to actively obtain the first perception data based on demand. For example, the third-party entity may select an appropriate time to send the first access request based on its own traffic conditions to avoid excessive data volume and inability to bear the traffic.

[0187] Alternatively, in the communication method, the first network element may be a NEF network element. The UPF network element may provide a first data access address as an interface for accessing the first perception data. The second network element may be an SDPF network element or a RAN network element serving as a receiving perception entity. A third-party entity may obtain the first data access address. The third-party entity may actively obtain the first perception data by accessing the first data access address. Exemplarily, the third-party entity may flexibly choose the time to actively obtain the first perception data based on demand. For example, the third-party entity may choose an appropriate time to send the first access request based on its own traffic conditions to avoid excessive data volume and inability to withstand traffic.

[0188] This communication method can utilize the perception capability of the communication system to obtain the first perception data, and open / transmit the perception data obtained by the second network element (receiving perception entity or SDPF network element) to a third-party entity or NF network element and other data requesters, providing effective data support for the data requester to implement subsequent perception services or functions.

[0189] Optionally, the second network element is an access network element or a perception data processing function network element.

[0190] In a seventeenth aspect, the present application provides a communication device having the functionality to implement the method described in the sixteenth aspect. The functionality can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the functionality of the method described in the sixteenth aspect, such as a sending unit, a receiving unit, etc.

[0191] Exemplarily, the communication apparatus may be applied to a NEF network element. For example, the communication apparatus may be a communication device that deploys or carries the NEF network element, or may be a device (eg, a chip or software module) in a communication device that deploys or carries the NEF network element.

[0192] Among them, the sending unit is used to send a first request message to the perception service control function network element, and the first request message is used to indicate a request to obtain first perception data.

[0193] A receiving unit is used to receive a first response message from a perception service control function network element, where the first response message is used to indicate a first data access address, which is provided by a second network element or a user plane function network element and is used to obtain first perception data.

[0194] The sending unit is further configured to send the first data access address to the third-party entity.

[0195] Optionally, the second network element is an access network element or a perception data processing function network element.

[0196] In the eighteenth aspect, the present application also provides a communication device, including: a processor for executing computer instructions stored in a memory, when the computer instructions are executed, the device executes the method described in the sixteenth aspect or any possible design of the sixteenth aspect.

[0197] In the nineteenth aspect, the present application also provides a communication device, comprising: a processor and an interface circuit, the processor being used to communicate with other devices through the interface circuit and execute the method described in the sixteenth aspect or any possible design of the sixteenth aspect.

[0198] Illustratively, in aspect 18 and aspect 19, the processor is configured to execute the method described in aspect 16 or any possible design of aspect 16.

[0199] The communication device described in aspects 17 to 19 above may be a communication device for deploying or carrying NEF network elements, or may be a device (such as a chip or software module) in a communication device for deploying or carrying NEF network elements.

[0200] In a twentieth aspect, the present application further provides a computer-readable storage medium comprising: computer software instructions, or instructions; when the computer software instructions are executed, the method described in aspect 16 or any possible design of aspect 16 is implemented. For example, when the computer software instructions are executed in a communication device or a device (e.g., a chip) built into the communication device, the communication device implements the method described in aspect 16 or any possible design of aspect 16.

[0201] It can be understood that the beneficial effects that can be achieved in the seventeenth to twentieth aspects provided above can be referred to the beneficial effects in the sixteenth aspect and any possible design thereof, and will not be repeated here.

[0202] In a twenty-first aspect, the present application provides a communication method, the method being applied to a network open function network element, the method comprising: sending a first request message to a perception service control function network element, the first request message being used to indicate a request to obtain first perception data, and being used to indicate a first data push address provided by a third-party entity. The first data push address is used by a second network element to send the first perception data; alternatively, the first data push address is used by a user plane function network element to send the first perception data, where the first perception data in the user plane function network element comes from the second network element.

[0203] Optionally, the method further includes: receiving a first response message from the perception service control function. The first response message is used to confirm receipt of the first data push address.

[0204] Exemplarily, the method described in aspect 21 can be applied to a NEF network element, for example, the method is executed by a communication device that deploys or carries the NEF network element, or by a device (such as a chip or software module) in a communication device that deploys or carries the NEF network element.

[0205] In a possible scenario, the second network element may be a perception data processing function (SDPF) network element, and the first perception data may refer to the perception data processed by the SDPF network element.

[0206] In another possible scenario, the second network element may be an access network (RAN) network element serving as a receiving perception entity, and the first perception data may refer to original perception data obtained by the RAN network element or perception data processed by the RAN network element.

[0207] In this communication method, the first network element may be a NEF network element. A third-party entity may provide a first data push address, and the second network element may send the first perception data to the third-party entity by sending the first perception data to the first data push address. The third-party entity may passively receive the first perception data from the second network element using the first data push address.

[0208] Alternatively, in this communication method, the first network element may be a NEF network element. A third-party entity may provide a first data push address, and the UPF network element may send the first perception data to the third-party entity by sending the first perception data to the first data push address. The third-party entity may passively receive the first perception data sent by the UPF network element using the first data push address, and the first perception data in the UPF network element originates from the second network element.

[0209] This communication method can utilize the perception capability of the communication system to obtain the first perception data, and open / transmit the perception data obtained by the second network element (receiving perception entity or SDPF network element) to a third-party entity or NF network element and other data requesters, providing effective data support for the data requester to implement subsequent perception services or functions.

[0210] Optionally, the second network element is an access network element or a perception data processing function network element.

[0211] In aspect 22, the present application provides a communication device having the functionality to implement the method described in aspect 21 above. The functionality can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the functionality of the method described in aspect 21 above, such as a sending unit, a receiving unit, and the like.

[0212] Exemplarily, the communication apparatus may be applied to a NEF network element. For example, the communication apparatus may be a communication device that deploys or carries the NEF network element, or may be a device (eg, a chip or software module) in a communication device that deploys or carries the NEF network element.

[0213] The sending unit is configured to send a first request message to a perception service control function network element, where the first request message is used to indicate a request to obtain first perception data and a first data push address provided by a third-party entity. The first data push address is used by a second network element to send the first perception data; alternatively, the first data push address is used by a user plane function network element to send the first perception data, where the first perception data in the user plane function network element comes from the second network element.

[0214] The receiving unit is configured to receive a first response message from the perception service control function. The first response message is used to confirm receipt of the first data push address. The receiving unit may be an optional module.

[0215] Optionally, the second network element is an access network element or a perception data processing function network element.

[0216] In aspect 23, the present application also provides a communication device, comprising: a processor for executing computer instructions stored in a memory, so that when the computer instructions are executed, the device executes the method described in aspect 21 or any possible design of aspect 21.

[0217] In aspect 24, the present application also provides a communication device comprising: a processor and an interface circuit, the processor being used to communicate with other devices through the interface circuit and execute the method described in aspect 21 or any possible design of aspect 21.

[0218] Illustratively, in aspect 23 and aspect 24, the processor is configured to execute the method described in aspect 21 or any possible design of aspect 21.

[0219] The communication device described in aspects 22 to 24 above may be a communication device for deploying or carrying NEF network elements, or may be a device (such as a chip or software module) in a communication device for deploying or carrying NEF network elements.

[0220] In a twenty-fifth aspect, the present application further provides a computer-readable storage medium comprising: computer software instructions, or instructions; when the computer software instructions are executed, the method described in aspect twenty-first or any possible design of aspect twenty-first is implemented. For example, when the computer software instructions are executed in a communication device or a device built into the communication device, the communication device implements the method described in aspect twenty-first or any possible design of aspect twenty-first.

[0221] It can be understood that the beneficial effects that can be achieved in the above-mentioned aspects 22 to 25 can be referred to the beneficial effects in aspect 21 and any possible design thereof, and will not be repeated here.

[0222] In aspect 26, the present application provides a communication method, the method being applied to a user plane function network element, the method comprising: receiving first perception data from a second network element; using a first data access address as an interface for obtaining the first perception data, the first data access address being provided by the user plane function network element; or sending the first perception data to a first data push address provided by a third-party entity.

[0223] Exemplarily, the method described in Aspect 21 can be applied to a UPF network element, for example, the method is executed by a communication device that deploys or carries a UPF network element, or by a device (such as a chip or software module) in a communication device that deploys or carries a UPF network element.

[0224] In this communication method, the UPF network element may provide a first data access address as an interface for accessing the first perception data. The second network element may be an SDPF network element or a RAN network element serving as a receiving perception entity. A third-party entity may obtain the first data access address. The third-party entity may actively obtain the first perception data by accessing the first data access address. Exemplarily, the third-party entity may flexibly select the time to actively obtain the first perception data based on demand. For example, the third-party entity may select an appropriate time to send the first access request based on its own traffic conditions to avoid excessive data volume and inability to bear the traffic.

[0225] Alternatively, in this communication method, the third-party entity may provide a first data push address, and the UPF network element may send the first perception data to the first data push address to achieve the sending of the first perception data to the third-party entity. The third-party entity may use the first data push address to passively receive the first perception data sent by the UPF network element, and the first perception data in the UPF network element comes from the second network element.

[0226] This communication method can utilize the perception capability of the communication system to obtain the first perception data, and open / transmit the perception data obtained by the second network element (receiving perception entity or SDPF network element) to a third-party entity or NF network element and other data requesters, providing effective data support for the data requester to implement subsequent perception services or functions.

[0227] In one possible design, the receiving of the first perception data from the second network element includes: receiving the first perception data from the second network element through a general packet radio service tunneling protocol-user plane tunnel.

[0228] In one possible design, the received data packet of the first perception data is encapsulated with the first data push address.

[0229] In one possible design, the method further includes: receiving a second control message from a perception service control function network element, wherein the second control message is used to indicate that the first data access address is used as an interface for obtaining the first perception data.

[0230] In one possible design, the method further includes: sending a second control response message to the perception service control function network element, where the second control response message is used to indicate the first data access address.

[0231] In one possible design, the method further includes: receiving a second control message from a perception service control function network element, where the second control message is used to instruct sending the first perception data to a first data push address provided by a third-party entity.

[0232] Optionally, the second network element is an access network element or a perception data processing function network element.

[0233] In aspect 27, the present application provides a communication device having the functionality to implement the method described in aspect 26 above. The functionality can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the functionality of the method described in aspect 26 above, for example, a receiving unit, a sending unit, etc.

[0234] Exemplarily, the communication device may be applied to a UPF network element. For example, the communication device may be a communication device that deploys or carries a UPF network element, or may be a device (e.g., a chip or software module) in a communication device that deploys or carries a UPF network element.

[0235] Among them, the receiving unit is used to receive first perception data from the second network element.

[0236] The sending unit is configured to use a first data access address as an interface for obtaining the first perception data, where the first data access address is provided by the user plane function network element, or to send the first perception data to a first data push address provided by a third-party entity.

[0237] In one possible design, the receiving unit is specifically used to receive the first perception data from the second network element through a general packet radio service tunneling protocol-user plane tunnel.

[0238] In one possible design, the received data packet of the first perception data is encapsulated with the first data push address.

[0239] In one possible design, the receiving unit is further used to receive a second control message from a perception service control function network element, where the second control message is used to indicate that the first data access address is used as an interface for obtaining the first perception data.

[0240] In one possible design, the sending unit is also used to send a second control response message to the perception service control function network element, where the second control response message is used to indicate the first data access address.

[0241] In one possible design, the receiving unit is further used to receive a second control message from a perception service control function network element, where the second control message is used to instruct sending the first perception data to a first data push address provided by a third-party entity.

[0242] Optionally, the second network element is an access network element or a perception data processing function network element.

[0243] In aspect 28, the present application also provides a communication device, comprising: a processor for executing computer instructions stored in a memory, so that when the computer instructions are executed, the device executes the method described in aspect 26 or any possible design of aspect 26.

[0244] In aspect 29, the present application also provides a communication device comprising: a processor and an interface circuit, the processor being used to communicate with other devices through the interface circuit and execute the method described in aspect 26 or any possible design of aspect 26.

[0245] Illustratively, in aspect 28 and aspect 29, the processor is configured to execute the method described in aspect 26 or any possible design of aspect 26.

[0246] The communication device described in aspects 27 to 29 above may be a communication device that deploys or carries a UPF network element, or may be a device (such as a chip or software module) in a communication device that deploys or carries a UPF network element.

[0247] In a thirtieth aspect, the present application further provides a computer-readable storage medium comprising: computer software instructions, or instructions; when the computer software instructions are executed, the method described in aspect twenty-six or any possible design of aspect twenty-six is ​​implemented. For example, when the computer software instructions are executed in a communication device or a device built into the communication device, the communication device implements the method described in aspect twenty-six or any possible design of aspect twenty-six.

[0248] It can be understood that the beneficial effects that can be achieved in the above-mentioned aspects 27 to 30 can be referred to the beneficial effects in aspect 26 and any possible design thereof, and will not be repeated here.

[0249] In a thirty-first aspect, the present application provides a communication method, the method being applied to a data communication proxy network element, the method comprising: receiving a subscription request message from a first network element, the subscription request message being used to indicate a first topic and being used to subscribe to first perception data from the data communication proxy network element; sending a subscription response message to the first network element; receiving first perception data from a second network element, the first perception data being published according to a first topic; and sending the first perception data to the first network element.

[0250] Exemplarily, the method described in aspect 31 can be applied to a DCP network element, for example, the method is executed by a communication device that deploys or carries a DCP network element, or by a device (such as a chip or software module) in a communication device that deploys or carries a DCP network element.

[0251] In a possible scenario, the first network element may be a data requester of the perception data, such as a third-party entity or a network function (NF) network element within the network.

[0252] In another possible scenario, the first network element may also be another core network element that communicates with the data requester of the perception data, such as a network open function (NEF) network element. The data requester (such as a third-party entity) may send a request message to the NEF network element to request the first perception data. After receiving the request message from the data requester, the NEF network element may send a first request message to the SSCF network element. This application does not limit the implementation of the first network element.

[0253] In a possible scenario, the second network element may be a perception data processing function (SDPF) network element, and the first perception data may refer to the perception data processed by the SDPF network element.

[0254] In another possible scenario, the second network element may be an access network (RAN) network element serving as a receiving perception entity, and the first perception data may refer to original perception data obtained by the RAN network element or perception data processed by the RAN network element.

[0255] In this communication method, the second network element can send the first perception data to the first network element through the DCP network element. The second network element can be an SDPF network element or a RAN network element serving as a receiving perception entity, and the first network element can be an NEF network element or a data requester (e.g., a third-party entity). For example, the second network element can send the first perception data to the DCP network element according to the first topic. That is, the first perception data is published in the DCP network element according to the first topic. The first network element can obtain the first perception data from the DCP network element according to the first topic. The first topic can be sent by the SSCF network element to the first network element.

[0256] In this communication method, when opening or transmitting perception data to a data requester (such as a third-party entity), DCP network elements can be used to improve data transmission efficiency. In addition, DCP network elements can support multiple transmission protocols to meet the needs of different business scenarios.

[0257] This communication method can utilize the perception capabilities of the communication system to obtain first perception data and open / transmit the perception data obtained by the second network element (receiving perception entity or SDPF network element) to a third-party entity or a data requester such as a NF network element, providing effective data support for the data requester to implement subsequent perception services or functions. Opening / transmitting the perception data to a third-party entity via the NEF network element can improve data transmission security.

[0258] Optionally, the second network element is an access network element or a perception data processing function network element.

[0259] In aspect 32, the present application provides a communication device having the functionality to implement the method described in aspect 31 above. The functionality can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the functionality of the method described in aspect 31 above, such as a receiving unit, a sending unit, etc.

[0260] Exemplarily, the communication apparatus may be applied to a DCP network element. For example, the communication apparatus may be a communication device that deploys or carries a DCP network element, or may be a device (such as a chip or software module) in a communication device that deploys or carries a DCP network element.

[0261] The receiving unit is configured to receive a subscription request message from a first network element, the subscription request message being used to indicate a first topic and being used to subscribe to first perception data from a data communication proxy network element. The sending unit is configured to send a subscription response message to the first network element.

[0262] The receiving unit is further used to receive first perception data from the second network element, where the first perception data is published according to the first topic.

[0263] A sending unit is used to send the first perception data to the first network element.

[0264] Optionally, the second network element is an access network element or a perception data processing function network element.

[0265] In aspect 33, the present application also provides a communication device, comprising: a processor for executing computer instructions stored in a memory, so that when the computer instructions are executed, the device executes the method described in aspect 31 or any possible design of aspect 31.

[0266] In aspect 34, the present application also provides a communication device comprising: a processor and an interface circuit, the processor being used to communicate with other devices through the interface circuit and execute the method described in aspect 31 or any possible design of aspect 31.

[0267] Illustratively, in aspect 33 and aspect 34, the processor is configured to execute the method described in aspect 31 or any possible design of aspect 31.

[0268] The communication device described in aspects 32 to 34 above may be a communication device that deploys or carries a DCP network element, or may be a device (such as a chip or software module) in a communication device that deploys or carries a DCP network element.

[0269] In a thirty-fifth aspect, the present application further provides a computer-readable storage medium comprising: computer software instructions, or instructions; when the computer software instructions are executed, the method described in aspect 31 or any possible design of aspect 31 is implemented. For example, when the computer software instructions are executed in a communication device or a device built into the communication device, the communication device implements the method described in aspect 31 or any possible design of aspect 31.

[0270] It can be understood that the beneficial effects that can be achieved in the above-mentioned aspects 32 to 35 can be referred to the beneficial effects in aspect 31 and any possible design thereof, and will not be repeated here.

[0271] In a thirty-sixth aspect, the present application provides a communication method, the method being applied to a data analysis repository functional network element, the method comprising: receiving first perception data from a second network element; receiving a perception data request message from a first network element, the perception data request message being used to request acquisition of the first perception data; and sending a perception data response message to the first network element, the perception data response message including the first perception data.

[0272] Exemplarily, the method described in Aspect 36 can be applied to an ADRF network element, for example, the method is executed by a communication device that deploys or carries an ADRF network element, or by a device (such as a chip or software module) in a communication device that deploys or carries an ADRF network element.

[0273] In a possible scenario, the first network element may be a data requester of the perception data, such as a third-party entity or a network function (NF) network element within the network.

[0274] In another possible scenario, the first network element may also be another core network element that communicates with the data requester of the perception data, such as a network open function (NEF) network element. The data requester (such as a third-party entity) may send a request message to the NEF network element to request the first perception data. After receiving the request message from the data requester, the NEF network element may send a first request message to the SSCF network element. This application does not limit the implementation of the first network element.

[0275] In a possible scenario, the second network element may be a perception data processing function (SDPF) network element, and the first perception data may refer to the perception data processed by the SDPF network element.

[0276] In another possible scenario, the second network element may be an access network (RAN) network element serving as a receiving perception entity, and the first perception data may refer to original perception data obtained by the RAN network element or perception data processed by the RAN network element.

[0277] Exemplarily, in the communication method, the first network element may be a NF network element within the network. The second network element may store the first perception data in an ADRF network element, and the NF network element obtains the first perception data from the ADRF network element.

[0278] This communication method can utilize the perception capabilities of the communication system to obtain first perception data and open / transmit the perception data obtained by the second network element (receiving perception entity or SDPF network element) to a third-party entity or a data requester such as a NF network element, providing effective data support for the data requester to implement subsequent perception services or functions. Opening / transmitting the perception data to a third-party entity via the NEF network element can improve data transmission security.

[0279] Optionally, the second network element is an access network element or a perception data processing function network element.

[0280] In aspect 37, the present application provides a communication device having the functionality to implement the method described in aspect 36 above. The functionality can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more units or modules corresponding to the functionality of the method described in aspect 36 above, such as a receiving unit, a sending unit, and the like.

[0281] Exemplarily, the communication device may be applied to an ADRF network element. For example, the communication device may be a communication device that deploys or carries an ADRF network element, or may be a device (eg, a chip or software module) in a communication device that deploys or carries an ADRF network element.

[0282] Among them, the receiving unit is used to receive first perception data from the second network element.

[0283] The receiving unit is further used to receive a perception data request message from the first network element, where the perception data request message is used to request acquisition of the first perception data.

[0284] A sending unit is configured to send a perception data response message to the first network element, where the perception data response message includes the first perception data.

[0285] Optionally, the second network element is an access network element or a perception data processing function network element.

[0286] In aspect 38, the present application also provides a communication device, comprising: a processor for executing computer instructions stored in a memory, so that when the computer instructions are executed, the device executes the method described in aspect 36 or any possible design of aspect 36.

[0287] In aspect thirty-ninth, the present application also provides a communication device, comprising: a processor and an interface circuit, the processor being used to communicate with other devices through the interface circuit and execute the method described in aspect thirty-sixth or any possible design of aspect thirty-sixth.

[0288] Illustratively, in aspect 8 and aspect 9, the processor is configured to execute the method described in aspect 36 or any possible design of aspect 36.

[0289] The communication device described in aspects 37 to 39 above may be a communication device that deploys or carries an ADRF network element, or may be a device (such as a chip or software module) in a communication device that deploys or carries an ADRF network element.

[0290] In a fortieth aspect, the present application further provides a computer-readable storage medium comprising: computer software instructions, or instructions; when the computer software instructions are executed, the method described in aspect 36 or any possible design of aspect 36 is implemented. For example, when the computer software instructions are executed in a communication device or a device built into the communication device, the communication device implements the method described in aspect 36 or any possible design of aspect 36.

[0291] It can be understood that the beneficial effects that can be achieved in the above-mentioned aspects 37 to 40 can be referred to the beneficial effects in the 36th aspect and any possible design thereof, and will not be repeated here.

[0292] In the forty-first aspect, the present application provides a communication device, comprising: a transceiver unit and a processing unit. The transceiver unit can be used to send and receive information, or to communicate with other network elements. The processing unit can be used to process data. The device can implement the method as described in the first aspect and any possible design thereof, or the method as described in the sixth aspect and any possible design thereof, or the method as described in the eleventh aspect and any possible design thereof, or the method as described in the sixteenth aspect and any possible design thereof, or the method as described in the twenty-first aspect and any possible design thereof, or the method as described in the twenty-sixth aspect and any possible design thereof, or the method as described in the thirty-first aspect and any possible design thereof, or the method as described in the thirty-sixth aspect and any possible design thereof, through the transceiver unit and the processing unit.

[0293] In aspect 42, the present application also provides a computer program product, which, when executed, can implement the method as described in aspect 1 and any possible design thereof; or the method as described in aspect 6 and any possible design thereof; or the method as described in aspect 11 and any possible design thereof; or the method as described in aspect 16 and any possible design thereof; or the method as described in aspect 21 and any possible design thereof; or the method as described in aspect 26 and any possible design thereof; or the method as described in aspect 31 and any possible design thereof; or the method as described in aspect 36 and any possible design thereof.

[0294] In aspect 43, the present application also provides a chip system, which includes one or more interface circuits and one or more processors; the interface circuits and the processors are interconnected through lines; the processor receives and executes computer instructions from the memory of the electronic device through the interface circuit to implement the method as described in aspect 1 and any possible design thereof; or the method as described in aspect 6 and any possible design thereof; or the method as described in aspect 11 and any possible design thereof; or the method as described in aspect 16 and any possible design thereof; or the method as described in aspect 21 and any possible design thereof; or the method as described in aspect 26 and any possible design thereof; or the method as described in aspect 31 and any possible design thereof; or the method as described in aspect 36 and any possible design thereof.

[0295] In aspect 44, the present application further provides a communication system comprising one or more of the following network elements: the SSCF network element as described in aspect 1, the second network element as described in aspect 6, the first network element as described in aspect 11 (or the NEF network element as described in aspect 16 or aspect 21), the UPF network element as described in aspect 26, the DCP network element as described in aspect 31, and the ADRF network element as described in aspect 36. The aforementioned network elements cooperate to implement the methods mentioned in aspects 1 to 40. For example, each network element performs the steps described in the aforementioned corresponding aspects.

[0296] In aspect 45, the present application also provides a communication device, which can be used to implement the method as described in aspect 1 and any possible design thereof; or the method as described in aspect 6 and any possible design thereof; or the method as described in aspect 11 and any possible design thereof; or the method as described in aspect 16 and any possible design thereof; or the method as described in aspect 21 and any possible design thereof; or the method as described in aspect 26 and any possible design thereof; or the method as described in aspect 31 and any possible design thereof; or the method as described in aspect 36 and any possible design thereof.

[0297] It can be understood that the beneficial effects that can be achieved in the forty-first to forty-fifth aspects provided above can refer to the beneficial effects described in the first to fortieth aspects, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0298] FIG1 is a schematic diagram of a communication system provided in an embodiment of the present application;

[0299] FIG2 shows a schematic diagram of a perception scenario provided by an embodiment of the present application;

[0300] FIG3 shows a schematic diagram of the composition of a communication device provided in an embodiment of the present application;

[0301] FIG4 shows a flow chart of a communication method according to an embodiment of the present application;

[0302] FIG5 shows another flow chart of the communication method provided in an embodiment of the present application;

[0303] FIG6 shows another flow chart of the communication method provided in an embodiment of the present application;

[0304] FIG7 shows another schematic flow chart of the communication method provided in an embodiment of the present application;

[0305] FIG8 shows another schematic flow chart of the communication method provided in an embodiment of the present application;

[0306] FIG9 shows another schematic flow chart of the communication method provided in an embodiment of the present application;

[0307] FIG10 shows another schematic flow chart of the communication method provided in an embodiment of the present application;

[0308] FIG11 shows another schematic flow chart of the communication method provided in an embodiment of the present application;

[0309] FIG12 shows another schematic flow chart of the communication method provided in an embodiment of the present application;

[0310] FIG13 shows another schematic flow chart of the communication method provided in an embodiment of the present application;

[0311] FIG14 shows another schematic flow chart of the communication method provided in an embodiment of the present application;

[0312] FIG15 shows another schematic flow chart of the communication method provided in an embodiment of the present application;

[0313] FIG16 shows another schematic flow chart of a communication method according to an embodiment of the present application;

[0314] FIG17 shows another schematic flow chart of the communication method provided in an embodiment of the present application;

[0315] FIG18 shows another schematic flow chart of a communication method according to an embodiment of the present application;

[0316] FIG19 shows a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0317] FIG20 shows another schematic structural diagram of a communication device provided in an embodiment of the present application;

[0318] FIG21 shows another schematic structural diagram of a communication device provided in an embodiment of the present application;

[0319] FIG22 shows another schematic structural diagram of a communication device provided in an embodiment of the present application;

[0320] FIG23 shows another schematic structural diagram of a communication device provided in an embodiment of the present application;

[0321] FIG24 shows another schematic structural diagram of a communication device provided in an embodiment of the present application;

[0322] FIG25 shows another schematic structural diagram of a communication device provided in an embodiment of the present application;

[0323] FIG26 shows another structural diagram of the communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0324] Perception is the process of collecting and processing data to generate perception results. For example, collected data can be used to determine the distance, shape, and type of surrounding obstacles. Another example is the use of collected data to determine the breathing rate and heart rate of the monitored subject. The collected data can be collected by sensors or wireless signals. The process of performing perception through wireless signal data collection is also called wireless perception.

[0325] Wireless sensing and wireless communications are both based on electromagnetic wave theory. In a communication system, the transmitter can modulate the electromagnetic wave signal so that the electromagnetic wave carries the source information. During propagation, the electromagnetic wave signal is affected by the wireless environment, that is, the electromagnetic wave signal is modulated by the environment and therefore also carries environmental information. By analyzing the electromagnetic wave signal, the receiver can not only obtain the carried source information but also extract the perception information reflecting the characteristics of the propagation environment. This makes integrated sensing and communication (ISAC) possible. ISAC can also be called joint communications and sensing (JCAS) or synaesthesia integration. Compared with systems that separate sensing and communication, ISAC has a series of advantages, such as cost savings, reduced equipment size, lower power consumption, improved frequency efficiency, and reduced mutual interference between communication and sensing.

[0326] By utilizing the perception capabilities of the communication system to provide perception data to consumers (also known as users or requesters), effective data support can be provided for consumers to use the perception data to realize various functions and services.

[0327] Against this background, the present application provides a communication method that can utilize the perception capability of the communication system to open / transmit perception data in the communication system to a data requester.

[0328] The term "data requester" refers to the object or entity that requests or consumes sensory data, or is described as a consumer or user of sensory services. This application does not restrict this term, and may also refer to data consumers, data users, data consumers, sensory subscribers, or sensory subscribers.

[0329] In some possible scenarios, the data requester may be a third-party entity, such as a server, terminal device, data processing system, etc.

[0330] For example, in embodiments of the present application, sensory data can be used to implement one or more services and functions, including high-precision positioning and tracking, simultaneous imaging, map construction and positioning, human sensory enhancement, and gesture and motion recognition. Third-party entities can be servers, systems, devices, and the like used to implement the aforementioned services and functions, such as positioning systems and autonomous driving systems.

[0331] In some other possible scenarios, the data requester may also be a network function (NF) element or entity within the network, such as an application function (AF) element or entity, a data network (DN), etc.

[0332] This application does not limit the specific type of data requester.

[0333] For example, Figure 1 is a schematic diagram of a communication system provided in an embodiment of the present application. The communication method provided in the present application can be applied to the communication system shown in Figure 1.

[0334] As shown in Figure 1, the communication system may include: an access network (radio access network, RAN) network element 110, a sensing service control function (sensing service control function, SSCF) network element 120, a sensing data processing function (sensing data process function, SDPF) network element 130, and a first network element 140.

[0335] The RAN network element 110 may be used to obtain the sensing data. The RAN network element 110 may be a network element in an access network (also known as a radio access network), such as an access network device. The RAN network element 110 may also be referred to as a RAN node (or device).

[0336] In one possible scenario, the RAN network element 110 may be a base station, an evolved NodeB (eNodeB), a transmitting and receiving point (TRP), a transmitting point (TP), a next generation NodeB (gNB), a next generation base station in a 6G system, a base station in a future mobile communication system, a satellite, an integrated access and backhaul (IAB) node, a mobile switching center, or an access network device in a non-terrestrial network (NTN) communication system, that is, it may be deployed on a high-altitude platform or a satellite. The RAN network element 110 may be a macro base station, a micro base station, an indoor station, a relay node or a donor node, or a wireless controller in a cloud radio access network (CRAN) scenario. The RAN network element 110 may also be a device that functions as a base station in device-to-device (D2D) communication, vehicle-to-vehicle communication, drone communication, or machine communication. Optionally, the RAN network element 110 may also be a server, a wearable device, a vehicle or an onboard device, etc. For example, the RAN network element 110 in the vehicle to everything (V2X) technology may be a road side unit (RSU).

[0337] All or part of the functions of the RAN network element 110 in this application may also be implemented through software functions running on hardware, or through virtualized functions instantiated on a platform (e.g., a cloud platform). The RAN network element 110 in this application may also be a logical node, logical module, or software that can implement all or part of the functions of the RAN network element 110.

[0338] In another possible scenario, multiple RAN network elements 110 collaborate to implement the function of acquiring sensing data, with different RAN network elements 110 implementing part of the functions. For example, the RAN network element 110 can be a centralized unit (CU), a distributed unit (DU), a CU-control plane (CP), a CU-user plane (UP), or a radio unit (RU). The CU and DU can be configured separately or included in the same network element, such as a baseband unit (BBU). The RU can be included in a radio frequency device or radio frequency unit, such as a remote radio unit (RRU), an active antenna unit (AAU), or a remote radio head (RRH). It is understood that the RAN network element 110 can be a CU node, a DU node, or a device including a CU node and a DU node. In addition, the CU can be classified as a network device in the access network RAN, or the CU can be classified as a network device in the core network CN, without limitation here.

[0339] In different systems, CU (or CU-CP and CU-UP), DU or RU may have different names, but those skilled in the art can understand their meanings. For example, in an open access network (open RAN, O-RAN or ORAN) system, CU may also be called O-CU (open CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, CU-UP may also be called O-CU-UP, and RU may also be called O-RU. Any unit among CU (or CU-CP, CU-UP), DU and RU can be implemented by a software module, a hardware module, or a combination of software and hardware modules.

[0340] Exemplarily, the perception data acquired by the RAN network element 110 can be collected by a sensing entity (SE). A sensing entity is a logical entity and can also be referred to as a logical sensing entity. In a perception scenario, a sensing entity is divided into a sensing entity that sends a perception signal (such as Tx) and a sensing entity that receives a perception signal (such as Rx). The perception signal can be the aforementioned electromagnetic wave signal. The sensing entity that sends the perception signal can be referred to as a sending perception entity or a first perception entity, and the sensing entity that receives the perception signal can be referred to as a receiving perception entity or a second perception entity. The perception signal that can be received by the second perception entity carries the perception data. In some scenarios, a perception entity can serve as both a first perception entity and a second perception entity, that is, a perception entity can have the functions of sending and receiving perception signals at the same time.

[0341] The aforementioned perception entities (including the first perception entity and the second perception entity) can be deployed on a network device or a terminal device. That is, a network device and / or a terminal device with perception capabilities can serve as a perception entity, or a perception entity can include a network device and / or a terminal device with perception capabilities. Different perception entities can form different perception scenarios.

[0342] For example, Figure 2 shows a schematic diagram of a perception scenario provided by an embodiment of the present application. As shown in Figure 2, based on the type of the perception entity, the perception scenario can include six types shown in (a) to (f) in Figure 2.

[0343] In scenario 1, shown in (a) of Figure 2, a network device (e.g., a base station) can act as both a sensing entity that sends and receives sensing signals. That is, the network device can simultaneously act as both a transmitter (Tx) and receiver (Rx) of sensing signals. The sensing signal sent by the network device reaches a target object (e.g., a vehicle, a person, or other object, with a vehicle being used as an example in Figure 2). After being reflected by the target object, the network device receives the sensing signal and processes it to obtain a sensing result, such as sensing data.

[0344] In scenario 2, shown in Figure 2(b), one network device (e.g., base station 1) can serve as the sensing entity that sends the sensing signal, while another network device (e.g., base station 2) can serve as the sensing entity that receives the sensing signal. The transmitting end (Tx) and receiving end (Rx) of the sensing signal can be different network devices. The sensing signal sent by network device 1 reaches the target object. After being reflected by the target object, network device 2 can receive the sensing signal and process it to obtain a sensing result, such as sensing data.

[0345] The perception scenarios shown in (a) and (b) of FIG1 may be referred to as network device-based perception scenarios, or BS-to-BS perception scenarios.

[0346] In scenario 3, shown in Figure 2 (c), a network device (e.g., a base station) can serve as the sensing entity that transmits the sensing signal, and a terminal device (e.g., a mobile phone) can serve as the sensing entity that receives the sensing signal. The transmitting end (Tx) of the sensing signal can be the network device, and the receiving end (Rx) can be the terminal device. The sensing signal sent by the network device reaches the target object, is reflected by the target object, and is received by the terminal device. The terminal device then processes the sensing signal to obtain a sensing result, such as sensing data.

[0347] In scenario 4, shown in (d) of Figure 2, a terminal device (e.g., a mobile phone) can serve as the sensing entity that sends the sensing signal, and a network device (e.g., a base station) can serve as the sensing entity that receives the sensing signal. The sensing signal's transmitter (Tx) can be the terminal device, and the receiver (Rx) can be the network device. The sensing signal sent by the terminal device reaches the target object, reflects off the target object, and is then received by the network device. The network device then processes the sensing signal to obtain sensing results, such as sensing data.

[0348] The perception scenarios shown in (c) and (d) of Figure 2 can be called perception scenarios based on network devices and terminal devices, or, scenario 3 can be called BS-to-UE perception scenario, and scenario 4 can be called UE-to-BS perception scenario.

[0349] In scenario 5, shown in (e) of Figure 2 , a terminal device (e.g., a mobile phone) can act as both a sensing entity that sends and receives sensing signals. That is, the terminal device can simultaneously act as both a transmitter (Tx) and receiver (Rx) of sensing signals. The sensing signal sent by the terminal device reaches the target object, reflects off the target object, and is then received by the terminal device. The terminal device can then process the sensing signal to obtain a sensing result, such as sensing data.

[0350] In scenario 6 shown in (f) of Figure 2 , one terminal device (e.g., mobile phone 1) can serve as the sensing entity that sends the perception signal, while another terminal device (e.g., mobile phone 2) can serve as the sensing entity that receives the perception signal. The transmitter (Tx) and receiver (Rx) of the perception signal can be different terminal devices. The perception signal sent by terminal device 1 reaches the target object. After being reflected by the target object, the perception signal is received by terminal device 2, which then processes the perception signal to obtain a perception result, such as perception data.

[0351] The perception scenarios shown in (e) and (f) of Figure 2 can be called terminal device-based perception scenarios, or UE-to-UE perception scenarios.

[0352] The perception signal sent by the transmitting end may be referred to as a first perception signal, and the perception signal received by the receiving end may be referred to as a second perception signal. The second perception signal carries more information than the first perception signal. For example, the second perception signal may carry information source information and environmental information. In the scenario shown in FIG2 , the RAN network element 110 may serve as a receiving end of the perception signal to obtain perception data, or the RAN network element 110 may communicate with the receiving end of the perception signal to obtain perception data, without limitation herein.

[0353] Optionally, in embodiments of the present application, the network device may refer to the implementation of the RAN network element 110 described above. A terminal device may also be referred to as user equipment (UE). In some examples, the terminal device may be a wireless terminal. A wireless terminal may be a device that provides voice and / or other service data connectivity to a user, a handheld device with wireless connectivity, or other processing device connected to a wireless modem. For example, the terminal device can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a cellular phone, a personal communication service (PCS) phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a personal digital assistant (PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal in a 5G or 6G mobile communication system or a terminal in a future evolution network, etc.

[0354] It should be understood that this application does not limit the specific product forms of terminal devices and network devices.

[0355] The SSCF network element 120 and SDPF network element 130 shown in Figure 1 may be core network functional modules. The SSCF network element 120 implements control plane functions for sensory services, such as receiving sensory capability information from sensory entities and orchestrating sensory services based on this information. Sensory services are also called sensory services. The SDPF network element 130 implements data plane functions for sensory services, such as processing sensory data to obtain sensory results.

[0356] SSCF network element 120 and SDPF network element 130 can be integrated, deployed separately, or deployed together with other core network functional modules. After the control plane functions and data plane functions of the perception service are independently deployed, the number of control plane functional entities and data plane functional entities can be flexibly configured and adjusted based on resources and service conditions. Furthermore, attacks on the data plane will not affect the control plane, which can improve the reliability and security of the perception service.

[0357] The above-mentioned orchestration of the sensing service may include selecting a sending sensing entity and a receiving sensing entity according to sensing capability information of the sensing entity.

[0358] Exemplarily, the perception capability information of the perception entity includes: device identification, role identification, device type, geographic location information, perception processing capability, and supported perception service types.

[0359] Among them, the device identifier is used to uniquely identify the perception entity. For example, if the first perception entity is a terminal device, the device identifier can be an international mobile equipment identity (IMEI), a user permanent identifier (SUPI), a user hidden identifier (SUCI), a media access control (MAC) address, etc. For another example, if the first perception entity is a network device, the device identifier can be a cell identifier and / or a tracking area identity (TAI), etc., and the cell identifier can be, for example, a physical cell identifier (PCI).

[0360] The role identifier is used to indicate that the sensing entity is a sending sensing entity and / or a receiving sensing entity.

[0361] The device type is used to indicate whether the sensing entity is a network device or a terminal device. Optionally, if it is a network device, the device type can also indicate whether the network device is a base station, CU, or DU. If it is a terminal device, the device type can also indicate whether the terminal device is a UE, IoT device, flight device, or VR device.

[0362] The geographic location information may be used to indicate one or more of the following: the current geographic location of the sensing entity, the geographic location range that the sensing entity can sense, and the geographic location, such as latitude and longitude information, global positioning system (GPS) location information, etc.

[0363] The perception processing capability is used to indicate that the perception entity has one or more of layer 1 (layer1, L1) perception capability, layer 2 (layer2, L2) perception capability, and layer 3 (layer3, L3) perception capability.

[0364] Among them, the L1 perception processing capability is used to perceive raw data. Raw data refers to basic information of the perception signal, such as amplitude, phase, and whether the perception signal is an I-channel signal or a Q-channel signal, among other information.

[0365] L2 perception processing capability is used to perceive measurement data. Measurement data refers to data obtained by processing raw data and is used to characterize the measurement dimension. It may include but is not limited to one or more of the following information: sampling point latency, perception signal reception angle, perception signal strength, Doppler (i.e., perception signal frequency offset), target object location, target object speed, etc.; sampling points refer to signal values ​​at specific moments or locations selected during the discretization of continuous signals during signal processing.

[0366] L3 perception processing capability is used to process perception data to obtain perception results. The perception data can be raw data and / or measurement data. The perception results can include but are not limited to one or more of the following information: the distance between the perception entity and the target object, the speed of the target object, the position of the target object, the angle between the perception entity and the target object, the moving path of the target object, the breathing rate of the target object, the heartbeat of the target object, etc.

[0367] The supported perception service types are used to indicate the types of perception services that the perception entity can provide, and may include but are not limited to one or more of the following types: environment type, monitoring type, imaging type, positioning type, etc. The environment type may include but are not limited to one or more of the following: ambient temperature, ambient humidity, air quality, weather conditions, crowd density, traffic density, air pressure, etc. The monitoring type may include but are not limited to one or more of the following: mobile monitoring, intrusion monitoring, fall monitoring, health monitoring, etc. Mobile monitoring may include but are not limited to one or more of the following: distance monitoring, location monitoring, mobile speed monitoring, mobile path monitoring, etc. Health monitoring may include but are not limited to one or more of the following: respiratory rate, heartbeat, etc. The imaging type may include but are not limited to one or more of the following: medical imaging, 3D map imaging, 3D map construction, building imaging, body temperature imaging, etc.

[0368] The above-mentioned processing of the perception data may include processing the original perception data received or measured by the receiving perception entity to obtain processed perception data.

[0369] Optionally, the SSCF network element 120 may also be referred to as a perception control entity, a perception service control network element, or a perception control network element, etc. The SDPF network element 130 may also be referred to as a perception processing entity, a perception data processing network element, or a perception processing network element, etc.

[0370] The names of the SSCF network element 120 and the SDPF network element 130 mentioned in this application are for example only and do not constitute a limitation. With the development of communication technology and perception technology, these two modules may adopt other names.

[0371] The first network element 140 shown in FIG1 may be a data requester, such as a third-party entity or a NF network element. Alternatively, the first network element 140 may be another network element in the communication system that interacts with the data requester (such as a third-party entity), such as a network exposure function (NEF) network element. The NEF network element may also be called a network service presentation function network element.

[0372] When the first network element 140 is a third-party entity or an NF network element, the first network element 140 can directly interact with the RAN network element 110, the SSCF network element 120, the SDPF network element 130, etc. to obtain perception data.

[0373] When the first network element 140 is an NEF network element, the data requester (such as a third-party entity) can interact with the RAN network element 110, the SSCF network element 120, the SDPF network element 130, etc. through the NEF network element to obtain the perception data. For example, the perception data can be made available to the data requester through the NEF network element.

[0374] Optionally, the communication system shown in Figure 1 may include but is not limited to: a narrowband Internet of Things (NB-IoT) system, a global system for mobile communications (GSM) system, an enhanced data rate for GSM evolution (EDGE) system, a wideband code division multiple access (WCDMA) system, a code division multiple access (CDMA) 2000 system, a time division-synchronization code division multiple access (TD-SCDMA) system, a long term evolution (LTE) system, a 5G mobile communication system and a next-generation 5G mobile communication system, enhanced Mobile Broadband (eMBB), ultra-reliable low-latency communication (URLLC) and massive Machine-Type Communications (mMTC), a long range Internet of Things (LoRa) system or a vehicle network system, or a future 6G communication system or other evolved communication systems. This application does not limit the type of communication system to which the communication method can be applied.

[0375] For example, FIG3 shows a schematic diagram of the composition of a communication device provided in an embodiment of the present application. The communication device may be the aforementioned network device or terminal device. The network device may be the aforementioned perception entity or a device that deploys the perception entity, or may be any network element involved in the embodiments of the present application or a device that carries / deploys the network element, such as an access network element, an SSCF network element, an SDPF network element, a first network element, a third-party entity, or a NF network element.

[0376] As shown in FIG3 , the communication device may include: at least one processor 31 , a memory 32 , a communication interface 33 , and a bus 34 .

[0377] The processor 31 is the control center of the communication device and can be a single processor or a collective term for multiple processing elements. For example, the processor 31 can be a central processing unit (CPU), 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).

[0378] The processor 31 can execute various functions of the communication device by running or executing the software program stored in the memory 32 and calling the data stored in the memory 32. For example, when the communication device is a network element involved in the communication method provided in the embodiment of the present application or a device that carries the network element, the steps performed by the network element in the communication method provided in the embodiment of the present application can be executed. For example, the steps performed by the access network network element, or the SSCF network element, or the SDPF network element, or the first network element, or the third party entity, or the NF network element can be executed.

[0379] In a specific implementation, as an embodiment, the processor 31 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG. 3 .

[0380] In a specific implementation, as an embodiment, a communication device may include multiple processors, such as processor 31 and processor 35 shown in FIG3 . Each of these processors may be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). A processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., computer program instructions).

[0381] The memory 32 can store a software program for the method steps performed by the communication device and be controlled for execution by the processor 31. The memory 32 can be a read-only memory (ROM) or other type of static storage device that can store static information and instructions, a random access memory (RAM) or other type of dynamic storage device 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, an optical disc storage (including a compact disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage 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 can be accessed by a computer, but is not limited to these.

[0382] The memory 32 may be independent and connected to the processor 31 via the bus 34. Alternatively, the memory 32 may be integrated with the processor 31, which is not limited here.

[0383] Communication interface 33, using any transceiver or other device, is used to communicate with other devices or communication networks. Communication interface 33 may include an Ethernet interface, a radio access network (RAN) interface, a wireless local area network (WLAN) interface, etc. Communication interface 33 may include a receiving unit to implement a receiving function and a sending unit to implement a sending function.

[0384] Bus 34 can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus. This bus can be classified as an address bus, a data bus, a control bus, etc. For ease of illustration, FIG3 shows only one thick line, but this does not mean that there is only one bus or only one type of bus.

[0385] Although the bus 34 is used in FIG. 3 , it is understandable that the bus can be replaced by other forms of connection relationships and is not limited to the bus itself.

[0386] Optionally, any network element or device that carries / deploys the network element involved in the embodiments of the present application, such as an access network element, an SSCF network element, an SDPF network element, a first network element, a third-party entity, an NF network element, etc., may also include more or fewer components than those shown in Figure 3, which is not limited here.

[0387] The following is an exemplary description of the communication method provided in the embodiments of the present application. The processing described below as being performed by a single execution subject can also be divided into multiple execution subjects, which can be logically and / or physically separated. It should also be understood that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0388] It should be noted that in the description of the embodiments of the present application, the words "first" and "second" are merely for distinguishing descriptions and are not used to specifically limit a particular feature. That is, the first or second can include more content, rather than being limited to a specific concept. "And / or" describes the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship. At least one refers to one or more; multiple refers to two or more. The embodiments of the present application may only perform fewer steps than all the steps, or perform more steps, without limitation. "At least one of the following" or similar expressions is used to indicate any combination of the listed items; for example, at least one of A, B, and / or C can mean the following: A exists alone, B exists alone, C exists alone, A and B exist at the same time, B and C exist at the same time, A and C exist at the same time, and A, B, and C exist at the same time, where A, B, and C can be single or multiple.

[0389] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art in the art of this application. The terms used in the specification of this application are only for the purpose of describing specific embodiments and are not intended to limit the present invention.

[0390] For example, in each process described below in this application, the steps performed by each network element (such as the first network element, the second network element, the SSCF network element, etc.) can be specifically performed by the communication device that carries / deploys the network element, or a device (for example, a software module or chip) built into the communication device that carries / deploys the network element. The communication device can be a network device or a terminal device.

[0391] Figure 4 shows a flow chart of a communication method provided by an embodiment of the present application. As shown in Figure 4, the communication method may include S401-S403.

[0392] S401. The first network element sends a first request message to the SSCF network element, where the first request message is used to indicate a request to obtain first perception data.

[0393] Correspondingly, the SSCF network element may receive the first request message from the first network element.

[0394] In one possible scenario, the first network element may be a data requester of the perception data, such as a third-party entity or a NF network element within the network. The meanings of the third-party entity and the NF network element can be found in the above embodiments and will not be repeated here.

[0395] In this scenario, the first network element may send a first request message to the SSCF network element to request the SSCF network element to perform a sensing task orchestration so as to provide sensing data to the first network element through the second network element described below. The sensing data requested by the first request message may be referred to as first sensing data.

[0396] Exemplarily, taking the first network element as a third-party entity as an example, the third-party entity can also be referred to as an entity requesting a perception service. The first request message can also be referred to as a perception service request message or other names. In some implementations, the first request message can be used to indicate a request to obtain the perception result of the first perception service, and the perception result of the first perception service is referred to as the first perception data. The first request message may include one or more of the following information: an identifier of the third-party entity, area information of the first perception service, a perception service type of the first perception service, perception requirement information of the first perception service, etc. The aforementioned information included in the first request message may indicate the perception service requested by the third-party entity. Among them, the identifier of the third-party entity is used to identify the third-party entity.

[0397] In some other implementations, a third-party entity may subscribe to a perception service from the SSCF network element in advance. The first request message may carry or indicate a perception service identifier of the perception service to which the third-party entity subscribes. The perception service identifier is used to indicate a request to obtain the perception result of the perception service to which the third-party entity subscribes. For example, a third-party entity subscribes to a first perception service from the SSCF network element, and the first request message carries the perception service identifier of the first perception service, which is used to indicate a request to obtain the perception result of the first perception service. The perception result of the first perception service is referred to as first perception data. In this implementation, the third-party entity may also be referred to as a perception subscription terminal.

[0398] Optionally, the awareness service identifier that may be carried in the first request message may be generated by the SSCF and fed back to the third-party entity, so that the third-party entity may request the corresponding awareness service.

[0399] In another possible scenario, the first network element may also be another core network element that communicates with the data requester of the perception data, such as an NEF network element. The data requester (such as a third-party entity) may send a request message to the NEF network element to request the first perception data. After receiving the request message from the data requester, the NEF network element may send a first request message to the SSCF network element. This application does not limit the implementation of the first network element.

[0400] After receiving the first request message, the SSCF network element may execute S402.

[0401] S402. The SSCF network element sends a first control message to the second network element, where the first control message is used to instruct the sending of first perception data.

[0402] Accordingly, the second network element may receive the first control message from the SSCF network element.

[0403] The second network element may send the first sensing data in response to the first control message, for example, by executing S403.

[0404] S403. The second network element sends the first perception data.

[0405] Exemplarily, taking the first perception data as the perception result of the first perception service as an example, after receiving the first request message, the SSCF network element may send a control message (or perception control message) to the sending perception entity and the receiving perception entity respectively to trigger the sending perception entity and the receiving perception entity to perform the perception task and obtain the perception data. For example, the SSCF network element may send a control message to the sending perception entity to instruct the sending entity to send a perception signal, and send a control message to the receiving perception entity to instruct the receiving perception entity to receive the perception signal. The perception signal received by the receiving perception entity carries the perception data. The receiving perception entity may determine the perception data based on the received perception signal, and the perception data may be referred to as original perception data.

[0406] In one implementation, the receiving perception entity may send raw perception data to an SDPF network element, which may process the raw perception data to obtain processed perception data. The SSCF network element may also send a control message to the SDPF network element, instructing the SDPF network element to process the perception data sent by the receiving perception entity. For example, the SDPF network element may be specifically instructed to perform L2 perception processing and / or L3 perception processing on the received perception data.

[0407] In another implementation, the receiving perception entity may also have the ability to process the original perception data. After the receiving perception entity obtains the original perception data, it may process the original perception data, such as performing L2 perception processing and / or L3 perception processing, to obtain processed perception data. The receiving perception entity may send the processed perception data to the SDPF network element, and the SDPF network element may further process the processed perception data sent by the receiving perception entity, such as fusing the processed perception data sent by different receiving perception entities or performing L3 perception processing, to obtain the perception data processed by the SDPF network element. The SSCF network element may also send a control message to the SDPF network element, instructing the SDPF network element to process the perception data sent by the receiving perception entity, such as specifically instructing the SDPF network element to fuse or perform L3 perception processing on the received perception data.

[0408] Optionally, the SSCF network element may select a sending sensing entity and a receiving sensing entity based on information carried in the first request message (for information content, see the explanation of S401) and sensing capability information of each sensing entity. The SSCF network element may select one or more sending sensing entities and one or more receiving sensing entities.

[0409] Exemplarily, the first request message may carry a perception service identifier, and the perception service identifier is used to indicate a request to obtain the first perception data corresponding to the first perception service. The SSCF network element may determine the sending perception entity and the receiving perception entity associated with the first perception service based on the perception service identifier. For example, the SSCF network element may obtain the perception service type, regional information, and perception requirement information of the first perception service subscribed by the data requester based on the first perception service identifier, and assign the task ID of the first perception service based on this information. Alternatively, the SSCF network element may assign the task ID of the first perception service based on the perception service type, regional information, and perception requirement information of the first perception service carried in the first perception service request message. Optionally, the task IDs of different perception services are different. The SSCF network element may control the sending perception entity, the receiving perception entity, the SDPF network element, etc. to perform the perception task based on the task ID to obtain the perception data.

[0410] For example, a third-party entity requests the first perception service of area 1, and the type of the requested first perception service is mobile monitoring. The demand information indicates that the positioning accuracy error of the first perception service is within 10 cm. The current latitude and longitude information of perception entity a and perception entity b are within the range of area 1. The role identification of perception entity a is a sending perception entity, and the role identification of perception entity b is a receiving perception entity. Both perception entity a and perception entity b can support mobile information monitoring of mobile targets. Then the SSCF network element can select perception entity a as the sending perception entity for processing the first perception service, and select perception entity b as the receiving perception entity for processing the first perception service.

[0411] Optionally, as an optional embodiment, the sending sensing entity and the receiving sensing entity may be the same. For example, sensing entity 1 may serve as a sending sensing entity to send sensing signals and may also serve as a receiving sensing entity to receive sensing signals.

[0412] In a possible scenario, the second network element described in S402 and S403 above may be an SDPF network element, the first control message may be a control message sent by the SSCF network element to the SDPF network element, and the first perception data may refer to the perception data processed by the SDPF network element.

[0413] In another possible scenario, the second network element described in S402 and S403 above may be a RAN network element serving as a receiving perception entity. The first control message may be a control message sent by the SSCF network element to the RAN network element, and the first perception data may refer to raw perception data obtained by the RAN network element or perception data processed by the RAN network element.

[0414] In one possible design, the first network element may be a data requester of the perception data, such as a third-party entity or a NF network element within the network, and the second network element may directly send the first perception data to the first network element. S403 may include: the second network element sending the first perception data to the first network element.

[0415] For example, taking the first network element as a third-party entity and the second network element as an SDPF network element as an example, Figure 5 shows another flow diagram of the communication method provided by an embodiment of the present application. As shown in Figure 5, the communication method may include S501-S505.

[0416] S501. A third-party entity sends a request message 1 to the SSCF network element, where the request message 1 is used to indicate a request to obtain first perception data.

[0417] The request message 1 may be the first request message mentioned above.

[0418] Accordingly, the SSCF network element may receive the request message 1 from the third-party entity.

[0419] S502. The SSCF network element sends a control message 1 to the SDPF network element. The control message 1 is used to instruct the sending of the first perception data.

[0420] The control message 1 may be the first control message mentioned above.

[0421] Accordingly, the SDPF network element may receive the control message 1 from the SSCF network element.

[0422] S503. The SSCF network element sends a control message 2 to the RAN network element. The control message 2 is used to instruct the reception of the perception signal.

[0423] The control message 2 may be a control message sent by the SSCF network element to the RAN network element serving as the receiving perception entity. The process of the SSCF network element sending the control message to the sending perception entity is omitted here and will not be further described.

[0424] Accordingly, the RAN network element may receive the control message 2 from the SSCF network element.

[0425] The order of S502 and S503 is not limited.

[0426] S504. The RAN network element sends the sensing data to the SDPF network element.

[0427] Accordingly, the SDPF network element can receive and process the perception data to obtain processed perception data.

[0428] As mentioned above, the perception data received by the SDPF network element may be original perception data obtained by the RAN network element or perception data processed by the RAN network element. This article uses the example that the perception data received by the SDPF network element may be original perception data obtained by the RAN network element.

[0429] After the SDPF network element obtains the processed perception data, it may execute S505.

[0430] S505. The SDPF network element sends the processed sensing data to the third-party entity.

[0431] Accordingly, the third-party entity receives the processed perception data.

[0432] In S505, the SDPF network element sends the processed perception data, namely the first perception data, to the third-party entity.

[0433] For another example, taking the first network element as a third-party entity and the second network element as a RAN network element serving as a receiving and sensing entity, Figure 6 shows another flow chart of the communication method provided in an embodiment of the present application. As shown in Figure 6, the communication method may include S601-S603.

[0434] S601. The third-party entity sends a request message 1 to the SSCF network element, where the request message 1 is used to indicate a request to obtain first perception data.

[0435] The request message 1 may be the first request message mentioned above.

[0436] Accordingly, the SSCF network element may receive the request message 1 from the third-party entity.

[0437] S602. The SSCF network element sends a control message 1 to the RAN network element. The control message 1 is used to instruct the reception of a perception signal and the sending of first perception data.

[0438] The control message 1 may be the first control message mentioned above. For example, the control message 1 may be a control message sent by the SSCF network element to the RAN network element serving as the receiving perception entity. The process of the SSCF network element sending the control message to the sending perception entity is omitted here and will not be further described.

[0439] Accordingly, the RAN network element may receive the control message 1 from the SSCF network element.

[0440] Optionally, the SSCF network element may also send a control message to the SDPF network element to instruct the SDPF network element to process the sensing data.

[0441] S603. The RAN network element sends the sensing data to the third-party entity.

[0442] Accordingly, the third party entity receives the sensing data.

[0443] The perception data sent by the RAN network element to the third-party entity is the first perception data. The first perception data may be original perception data obtained by the RAN network element or perception data processed by the RAN network element.

[0444] Optionally, in an embodiment of the present application, the step of the RAN network element serving as a receiving perception entity interacting with a third-party entity or other network elements may also be implemented through another intermediate RAN network element. For example, the RAN1 network element sends perception data to the RAN2 network element, and the RAN2 network element sends perception data to the third-party entity. The RAN1 network element serves as the receiving perception entity, and this is not limited here.

[0445] In another possible design, the above-mentioned first network element may be an NEF network element, and the third-party entity may send a request message to the NEF network element to request to obtain the first perception data. After receiving the request message from the data requester, the NEF network element may send the first request message to the SSCF network element. The above-mentioned S403 may include: the second network element sends the first perception data to the NEF network element. The method may also include: the NEF network element sends the first perception data to the third-party entity. That is, the second network element may send the first perception data to the third-party entity through the NEF network element.

[0446] For example, taking the first network element as an NEF network element and the second network element as an SDPF network element as an example, Figure 7 shows another flow chart of the communication method provided in an embodiment of the present application. As shown in Figure 7, the communication method may include S701-S707.

[0447] S701. A third-party entity sends a request message 1 to an NEF network element, where the request message 1 is used to indicate a request to obtain first perception data.

[0448] Accordingly, the NEF network element may receive the request message 1 from the third-party entity.

[0449] Exemplarily, the request message 1 may include one or more of the following perception information: perception user ID, perception service type, perception area, security requirements, perception accuracy requirements, event reporting duration, reporting interval, maximum sampling interval, start time, end time, priority, etc. The perception user ID may indicate identity information of a third-party entity, such as an identifier of the third-party entity.

[0450] Optionally, the request message 1 can be a NEF event open subscription interface message. For example, the event open subscription interface can be described as "Nnef_EventExposure_Subscribe". In one implementation, one or more fields can be added to the "Nnef_EventExposure_Subscribe" interface, and the newly added fields can be used to indicate a request to obtain the first perception data, such as used to indicate the various perception information included in the above request message 1. In another implementation, one or more existing fields in the "Nnef_EventExposure_Subscribe" interface can be modified or extended, and the modified or extended fields can be used to indicate a request to obtain the first perception data. This application does not limit the implementation of the request message 1.

[0451] S702. The NEF network element sends a request message 2 to the SSCF network element. The request message 2 is used to indicate a request to obtain the first perception data.

[0452] Request message 2 may be the first request message mentioned above.

[0453] Correspondingly, the SSCF network element may receive the request message 2 from the NEF network element.

[0454] Exemplarily, the request message 2 may also include various perception information included in the request message 1, to indicate a request to obtain the first perception data. In other words, the NEF network element may forward the perception service request sent by the third-party entity to the SSCF network element.

[0455] Optionally, the request message 2 may be an “Nsscf_SensingService_Request” interface message.

[0456] Optionally, after receiving the request message 2, the SSCF network element may return a response message to the NEF network element, such as response message 2. Response message 2 may be an "Nsscf_SensingService_Response" interface message. Response message 2 may be used to indicate confirmation of receipt of the request message 2 or other functions.

[0457] S703. The SSCF network element sends a control message 1 to the SDPF network element. The control message 1 is used to instruct the sending of the first perception data.

[0458] The control message 1 may be the first control message mentioned above.

[0459] Accordingly, the SDPF network element may receive the control message 1 from the SSCF network element.

[0460] S704. The SSCF network element sends a control message 2 to the RAN network element. The control message 2 is used to instruct the reception of the perception signal.

[0461] The control message 2 may be a control message sent by the SSCF network element to the RAN network element serving as the receiving perception entity. The process of the SSCF network element sending the control message to the sending perception entity is omitted here and will not be further described.

[0462] Accordingly, the RAN network element may receive the control message 2 from the SSCF network element.

[0463] The order of S703 and S704 is not limited.

[0464] S705. The RAN network element sends the sensing data to the SDPF network element.

[0465] Accordingly, the SDPF network element can receive and process the perception data to obtain processed perception data.

[0466] As mentioned above, the perception data received by the SDPF network element may be original perception data obtained by the RAN network element or perception data processed by the RAN network element. This article uses the example that the perception data received by the SDPF network element may be original perception data obtained by the RAN network element.

[0467] After the SDPF network element obtains the processed perception data, it may execute S706.

[0468] S706. The SDPF network element sends the processed sensing data to the NEF network element.

[0469] Correspondingly, the NEF network element receives the processed sensing data.

[0470] S707. The NEF network element sends the processed sensing data to the third-party entity.

[0471] Accordingly, the third-party entity receives the processed perception data.

[0472] In S706 and S707, the processed perception data sent by the SDPF network element to the third-party entity through the NEF network element is the above-mentioned first perception data.

[0473] Exemplarily, the NEF network element may send an event exposure notification interface message to the third-party entity, and the event exposure notification interface message may include the first perception data. For example, the event exposure notification interface may be an "Nnef_EventExposure_Notify" interface.

[0474] For another example, taking the first network element as an NEF network element and the second network element as a RAN network element serving as a receiving sensing entity, Figure 8 shows another flow chart of the communication method provided in an embodiment of the present application. As shown in Figure 8, the communication method may include S801-S805.

[0475] S801. A third-party entity sends a request message 1 to an NEF network element, where the request message 1 is used to indicate a request to obtain first perception data.

[0476] Accordingly, the NEF network element may receive the request message 1 from the third-party entity.

[0477] S802. The NEF network element sends a request message 2 to the SSCF network element. The request message 2 is used to indicate a request to obtain the first perception data.

[0478] Request message 2 may be the first request message mentioned above.

[0479] Correspondingly, the SSCF network element may receive the request message 2 from the NEF network element.

[0480] S801-S802 can refer to S701-S702 and will not be described in detail.

[0481] S803. The SSCF network element sends a control message 1 to the RAN network element. The control message 1 is used to instruct the reception of a perception signal and the sending of first perception data.

[0482] The control message 1 may be the first control message mentioned above. For example, the control message 1 may be a control message sent by the SSCF network element to the RAN network element serving as the receiving perception entity. The process of the SSCF network element sending the control message to the sending perception entity is omitted here and will not be further described.

[0483] Accordingly, the RAN network element may receive the control message 1 from the SSCF network element.

[0484] Optionally, the SSCF network element may also send a control message to the SDPF network element to instruct the SDPF network element to process the sensing data.

[0485] S804. The RAN network element sends the sensing data to the NEF network element.

[0486] Accordingly, the NEF network element can receive the sensing data.

[0487] S805. The NEF network element sends the sensing data to the third-party entity.

[0488] Accordingly, the third party entity receives the sensing data.

[0489] S805 can refer to the above S707 and will not be described in detail.

[0490] In S804 and S805, the perception data sent by the RAN network element to the third party entity via the NEF network element is the first perception data. The first perception data may be original perception data obtained by the RAN network element or perception data processed by the RAN network element.

[0491] In the communication method described above, the perception capabilities of the communication system can be utilized to obtain first perception data, and the perception data obtained by the second network element (receiving perception entity or SDPF network element) can be opened / transmitted to a third-party entity or a data requester such as a NF network element, providing effective data support for the data requester to implement subsequent perception services or functions. Opening / transmitting the perception data to a third-party entity via the NEF network element can improve data transmission security.

[0492] Optionally, in the above-described embodiment in which the second network element sends the first perception data to the first network element, the first control message received by the second network element may be specifically used to instruct the second network element to send the first perception data to the first network element. The second network element may know that the first perception data needs to be sent to the first network element based on the instruction of the first control message.

[0493] Optionally, in some embodiments, the second network element may also send the first perception data to the first network element via a data communication proxy (DCP) network element. The second network element may be an SDPF network element or a RAN network element serving as a receiving perception entity, and the first network element may be an NEF network element or a data requester (e.g., a third-party entity). In other words, the second network element may publish the first perception data to the DCP network element, and the first network element may subscribe to the first perception data from the DCP network element to obtain the first perception data.

[0494] Here, DCP is only an example name, and DCP can be replaced by other names. Any device with the same function as DCP can be regarded as DCP, and this application does not limit this.

[0495] The DCP can be deployed as a standalone network element in a 3GPP network, or it can be integrated with network elements or devices in a 3GPP network. Alternatively, the DCP can be deployed in an access network or in a core network. This application does not limit the implementation of the DCP network element.

[0496] When the second network element sends the first perception data to the first network element through the DCP network element, the second network element can act as a data producer to send the first perception data to the DCP, such as publishing the first perception data on the DCP network element in a topic publish manner. The first network element can act as a data consumer to subscribe to and extract data from the DCP network element, such as obtaining the first perception data in a topic subscribe manner.

[0497] Optionally, the DCP network element can support multiple transmission protocols, such as the transmission control protocol (TCP), the user datagram protocol (UDP), or the quick UDP internet connection (QUIC) protocol or other transmission protocols. The DCP network element may include an adapter layer and a distributed message queue (DMQ) to support efficient data distribution. The adaptation layer can complete the adaptation of the client's (such as data producer or data consumer) transmission protocol (such as TCP, UDP, QUIC transmission protocol, etc.), interact directly with the client, and distribute the client's request to the processing thread. DMQ can complete the message exchange function and distribute the messages published by the data producer to the corresponding data consumer. DCP supports the concept of data consumer groups, that is, the same message can only be consumed by one data consumer belonging to the same data consumer group, but can be consumed by different data consumer groups at the same time.

[0498] It should be understood that when the second network element sends the first perception data to the first network element via the DCP network element, the above S403 may include: the second network element sends the first perception data to the DCP network element according to the first topic. That is, the first perception data is published in the DCP network element according to the first topic. The method may also include: the first network element obtains the first perception data from the DCP network element according to the first topic. The first topic may be sent by the SSCF network element to the first network element.

[0499] The following uses the example of the first network element being an NEF network element and the third-party entity obtaining the first perception data through the NEF network element to illustrate the process of the second network element sending the first perception data to the first network element through the DCP network element. The case where the first network element is a third-party entity is similar to this, except that the third-party entity does not directly interact with the SSCF network element and the DCP network element through the NEF network element, which will not be further described.

[0500] For example, taking the first network element as an NEF network element and the second network element as an SDPF network element as an example, Figure 9 shows another flow chart of the communication method provided in an embodiment of the present application. As shown in Figure 9, the communication method may include S901-S911.

[0501] S901. A third-party entity sends a request message 1 to an NEF network element, where the request message 1 is used to indicate a request to obtain first perception data.

[0502] Accordingly, the NEF network element may receive the request message 1 from the third-party entity.

[0503] S902. The NEF network element sends a request message 2 to the SSCF network element. The request message 2 is used to indicate a request to obtain the first perception data.

[0504] Request message 2 may be the first request message mentioned above.

[0505] Correspondingly, the SSCF network element may receive the request message 2 from the NEF network element.

[0506] S903. The SSCF network element sends a control message 1 to the SDPF network element. The control message 1 is used to instruct the sending of the first perception data.

[0507] The control message 1 may be the first control message mentioned above.

[0508] Accordingly, the SDPF network element may receive the control message 1 from the SSCF network element.

[0509] S904. The SSCF network element sends a control message 2 to the RAN network element. The control message 2 is used to instruct the reception of the perception signal.

[0510] The control message 2 may be a control message sent by the SSCF network element to the RAN network element serving as the receiving perception entity. The process of the SSCF network element sending the control message to the sending perception entity is omitted here and will not be further described.

[0511] Accordingly, the RAN network element may receive the control message 2 from the SSCF network element.

[0512] S901-S904 can refer to the above S701-S704 and will not be described in detail.

[0513] S905. The SSCF network element sends a response message 1 to the NEF network element. The response message 1 is used to indicate topic 1, and topic 1 is used to subscribe to the first perception data from the DCP network element.

[0514] The response message 1 may be a response message to the request message 2 .

[0515] Topic 1 is the publishing topic of the first perception data in the DCP network element. The first perception data comes from the SDPF network element. Please refer to the following steps for details.

[0516] Exemplarily, the response message 1 may be the “Nsscf_SensingService_Response” interface message described above.

[0517] Correspondingly, the NEF network element receives the response message 1.

[0518] The order of S903 - S905 is not limited.

[0519] S906. The RAN network element sends the sensing data to the SDPF network element.

[0520] Accordingly, the SDPF network element can receive and process the perception data to obtain processed perception data.

[0521] As mentioned above, the perception data received by the SDPF network element may be original perception data obtained by the RAN network element or perception data processed by the RAN network element. This article uses the example that the perception data received by the SDPF network element may be original perception data obtained by the RAN network element.

[0522] After the SDPF network element obtains the processed perception data, it may execute S909.

[0523] S907. The NEF network element sends a subscription request message 1 to the DCP network element. The subscription request message 1 is used to indicate topic 1 to subscribe to the first perception data from the DCP network element.

[0524] Correspondingly, the DCP network element receives the subscription request message 1.

[0525] After receiving the subscription request message 1, the DCP network element may execute the following S908.

[0526] S908. The DCP network element sends a subscription response message 1 to the NEF network element.

[0527] Optionally, the subscription response message 1 is used to indicate confirmation of receipt of the subscription request message 1.

[0528] Correspondingly, the NEF network element receives the subscription response message 1.

[0529] S909. The SDPF network element sends the first perception data to the DCP network element. The publishing topic of the first perception data in the DCP network element is Topic 1.

[0530] In other words, the SDPF network element sends the first perception data to the DCP network element according to Topic 1. The first perception data refers to the perception data processed by the SDPF network element.

[0531] Correspondingly, the DCP network element receives the first perception data published according to topic 1.

[0532] S910. The DCP network element sends first perception data to the NEF network element.

[0533] Exemplarily, the DCP network element has received the subscription request message 1. After receiving the first perception data, the DCP network element may send the first perception data to the NEF network element.

[0534] Correspondingly, the NEF network element receives the first perception data.

[0535] S911. The NEF network element sends first perception data to the third-party entity.

[0536] Accordingly, the third-party entity receives the first perception data.

[0537] Optionally, in the process shown in Figure 9, the control message 1 sent by the SSCF network element to the SDPF network element in S903 can instruct the SDPF network element to send the first perception data to the DCP network element after a certain time delay, so that the perception data subscription process can be completed between the NEF network element and the DCP network element, and the DCP network element can normally send the first perception data to the NEF network element when receiving the first perception data, and will not discard the data. Alternatively, the control message 2 sent by the SSCF network element to the RAN network element in S904 can instruct the RAN network element to send the perception data to the SDPF network element after a certain time delay, so that the perception data subscription process can be completed between the NEF network element and the DCP network element, and the DCP network element can normally send the first perception data to the NEF network element when receiving the first perception data, and will not discard the data.

[0538] Alternatively, the timing when the SSCF network element sends control message 1 to the SDPF network element in S903, and / or the timing when the SSCF network element sends control message 2 to the RAN network element in S904, can be after the SSCF network element sends response message 1 to the NEF network element in S905, so that the perception data subscription process between the NEF network element and the DCP network element can be completed in time. When the DCP network element receives the first perception data, it can send the first perception data to the NEF network element normally and will not discard the data.

[0539] This application does not limit the execution order of the above steps.

[0540] In the process shown in Figure 9, the SDPF network element can publish the first perception data to the DCP network element, and the NEF network element can subscribe to and obtain the first perception data from the DCP network element.

[0541] For another example, taking the first network element as an NEF network element and the second network element as a RAN network element, Figure 10 shows another flow chart of the communication method provided in an embodiment of the present application. As shown in Figure 10, the communication method may include S1001-S1009.

[0542] S1001. A third-party entity sends a request message 1 to an NEF network element, where the request message 1 is used to indicate a request to obtain first perception data.

[0543] Accordingly, the NEF network element may receive the request message 1 from the third-party entity.

[0544] S1002. The NEF network element sends a request message 2 to the SSCF network element. The request message 2 is used to indicate a request to obtain the first perception data.

[0545] Request message 2 may be the first request message mentioned above.

[0546] Correspondingly, the SSCF network element may receive the request message 2 from the NEF network element.

[0547] S1001-S1002 can refer to the above S701-S702 and will not be repeated here.

[0548] S1003. The SSCF network element sends a control message 1 to the RAN network element. The control message 1 is used to instruct the reception of a perception signal and the sending of first perception data.

[0549] The control message 1 may be the first control message mentioned above. For example, the control message 1 may be a control message sent by the SSCF network element to the RAN network element serving as the receiving perception entity. The process of the SSCF network element sending the control message to the sending perception entity is omitted here and will not be further described.

[0550] Accordingly, the RAN network element may receive the control message 1 from the SSCF network element.

[0551] Optionally, the SSCF network element may also send a control message to the SDPF network element to instruct the SDPF network element to process the sensing data.

[0552] S1004. The SSCF network element sends a response message 1 to the NEF network element. The response message 1 is used to indicate topic 1, and topic 1 is used to subscribe to the first perception data from the DCP network element.

[0553] Topic 1 is the publishing topic of the first perception data in the DCP network element. The first perception data comes from the SDPF network element. Please refer to the following steps for details.

[0554] Exemplarily, the response message 1 may be the “Nsscf_SensingService_Response” interface message described above.

[0555] Correspondingly, the NEF network element receives the response message 1.

[0556] The order of S1003 and S1004 is not limited.

[0557] S1005. The NEF network element sends a subscription request message 1 to the DCP network element. The subscription request message 1 is used to indicate topic 1 to subscribe to the first perception data from the DCP network element.

[0558] Correspondingly, the DCP network element receives the subscription request message 1.

[0559] After receiving the subscription request message 1, the DCP network element may execute the following S1006.

[0560] S1006. The DCP network element sends a subscription response message 1 to the NEF network element.

[0561] Optionally, the subscription response message 1 is used to indicate confirmation of receipt of the subscription request message 1.

[0562] Correspondingly, the NEF network element receives the subscription response message 1.

[0563] S1007. The RAN network element sends the first perception data to the DCP network element. The publishing topic of the first perception data in the DCP network element is Topic 1.

[0564] In other words, the RAN network element sends the first perception data to the DCP network element according to Topic 1. The first perception data refers to original perception data obtained by the RAN network element or perception data processed by the RAN network element.

[0565] Correspondingly, the DCP network element receives the first perception data published according to topic 1.

[0566] S1008. The DCP network element sends the first perception data to the NEF network element.

[0567] Exemplarily, the DCP network element has received the subscription request message 1. After receiving the first perception data, the DCP network element may send the first perception data to the NEF network element.

[0568] Correspondingly, the NEF network element receives the first perception data.

[0569] S1009. The NEF network element sends the first perception data to the third-party entity.

[0570] Accordingly, the third-party entity receives the first perception data.

[0571] Optionally, in the process shown in Figure 10, the control message 1 sent by the SSCF network element to the RAN network element in S1003 can instruct the RAN network element to send perception data to the DCP network element after a certain delay, so that the perception data subscription process (such as S1005-S1006) can be completed in time between the NEF network element and the DCP network element. When the DCP network element receives the first perception data, it can send the first perception data to the NEF network element normally without discarding the data.

[0572] Alternatively, the timing for the SSCF network element to send control message 1 to the RAN network element in S1003 may be after the SSCF network element sends response message 1 to the NEF network element in S1004, so that the perception data subscription process between the NEF network element and the DCP network element can be completed in a timely manner. When the DCP network element receives the first perception data, it can send the first perception data to the NEF network element normally without discarding the data.

[0573] This application does not limit the execution order of the above steps.

[0574] In the process shown in FIG10 , the RAN network element serving as a receiving perception entity may publish the first perception data to the DCP network element, and the NEF network element may subscribe to obtain the first perception data from the DCP network element.

[0575] As can be seen from the processes shown in Figures 9 and 10, in the embodiment of the present application, the second network element (RAN network element or SDPF network element) can send the first perception data to the first network element via the DCP network element. In other words, the second network element can publish the first perception data to the DCP network element, and the first network element can subscribe to obtain the first perception data from the DCP network element.

[0576] For example, in this communication method, the SSCF network element may send a first response message to the first network element, and the first network element may receive the first response message. The first response message is used to indicate a first topic, and the first topic is used to subscribe to the first perception data from the DCP network element. The first topic is the publication topic of the first perception data in the DCP network element, and the first perception data comes from the second network element. The second network element sending the first perception data may mean that the second network element sends the first perception data to the DCP network element according to the first topic. The DCP network element may receive the first perception data from the second network element, and the first perception data is published according to the first topic. After receiving the first response message, the first network element may send a subscription request message to the DCP network element, and the DCP network element may receive the subscription request message. The subscription request message is used to indicate the first topic and to subscribe to the first perception data from the DCP network element. After receiving the subscription request message, the DCP network element may send a subscription response message to the first network element and send a subscription response message to the first network element. Accordingly, the first network element receives the subscription response message. The first network element receives first perception data from the second network element, which may include: the first network element receives first perception data sent by the DCP network element, where the first perception data comes from the second network element.

[0577] For example, in the process shown in Figure 9 above, the first response message may be response message 1 sent by the SSCF network element to the NEF network element, the first topic may be topic 1, the subscription request message may be subscription request message 1 sent by the NEF network element to the DCP network element, and the subscription response message may be subscription response message 1 sent by the DCP network element to the NEF network element.

[0578] In the above-described embodiment in which the second network element (RAN network element or SDPF network element) transmits the first perception data to the first network element via the DCP network element, the DCP network element can be used to improve data transmission efficiency when opening or transmitting the perception data to the data requester (e.g., a third-party entity). In addition, the DCP network element can support multiple transmission protocols to meet the requirements of different service scenarios.

[0579] Optionally, in the embodiment described above in which the second network element sends the first perception data to the first network element via the DCP network element, the first control message received by the second network element may be specifically used to instruct the second network element to publish the first perception data to the DCP network element according to the first topic. The second network element may know, based on the instruction of the first control message, that the first perception data needs to be published to the DCP network element according to the first topic.

[0580] Exemplarily, the first control message may carry or indicate the first topic, for example, may include a field indicating the first topic.

[0581] Optionally, in an embodiment of the present application, when the RAN network element serving as a receiving perception entity sends perception data to the SDPF network element, it may also send perception data to the SDPF network element through the DCP network element in a topic publishing and subscription manner, which will not be repeated here.

[0582] Optionally, in some other embodiments, when the first network element is a NF network element within the network (i.e., the network internal data is open), the second network element may also store / send the first perception data to an analytics data repository function (ADRF) network element, and the NF network element obtains the first perception data from the ADRF network element. The second network element may be an SDPF network element or a RAN network element serving as a receiving perception entity.

[0583] For example, in this communication method, the SSCF network element may send a first response message to the first network element, and the first network element may receive the first response message. The first response message is used to indicate that the first perception data is obtained from the ADRF network element, and the first perception data in the ADRF network element comes from the second network element. The second network element sending the first perception data may refer to: the second network element sending the first perception data to the ADRF network element. The ADRF network element may receive the first perception data from the second network element. After receiving the first response message, the first network element may send a perception data request message to the ADRF network element, and the ADRF network element may receive the perception data request message. The perception data request message is used to request the acquisition of the first perception data. After receiving the perception data request message, the ADRF network element may send a perception data response message to the first network element, and the first network element may receive the perception data response message. The perception data response message includes the first perception data. In other words, the first network element receiving the first perception data from the second network element may include: receiving a perception data response message from the ADRF network element, and the perception data response message includes the first perception data. The first perception data in the ADRF network element comes from the second network element.

[0584] Among them, the first network element can be a NF network element inside the network.

[0585] The following is an exemplary description of the process in which the second network element stores the first perception data to the ADRF network element and the NF network element obtains the first perception data from the ADRF network element.

[0586] For example, taking the second network element as an SDPF network element, Figure 11 shows another flow chart of the communication method provided in an embodiment of the present application. As shown in Figure 11, the communication method may include S1101-S1108.

[0587] S1101. The NF network element sends a request message 1 to the SSCF network element. The request message 1 is used to indicate a request to obtain the first perception data.

[0588] The request message 1 may be the first request message mentioned above.

[0589] Accordingly, the SSCF network element can receive the request message 1 from the NF network element.

[0590] S1102. The SSCF network element sends a control message 1 to the SDPF network element. The control message 1 is used to instruct the sending of the first perception data.

[0591] The control message 1 may be the first control message mentioned above.

[0592] Accordingly, the SDPF network element may receive the control message 1 from the SSCF network element.

[0593] S1103. The SSCF network element sends a control message 2 to the RAN network element. The control message 2 is used to instruct the reception of the perception signal.

[0594] The control message 2 may be a control message sent by the SSCF network element to the RAN network element serving as the receiving perception entity. The process of the SSCF network element sending the control message to the sending perception entity is omitted here and will not be further described.

[0595] Accordingly, the RAN network element may receive the control message 2 from the SSCF network element.

[0596] S1101-S1103 can refer to the above-mentioned S501-S503 and will not be repeated here.

[0597] S1104. The SSCF network element sends a response message 1 to the NF network element. The response message 1 is used to instruct the acquisition of the first perception data from the ADRF network element.

[0598] Accordingly, the NF network element receives a response message 1. The response message 1 may be a response message to the request message 1. The response message 1 may be referred to as the first response message.

[0599] There is no limitation on the execution order of S1102 to S1104. For example, S1104 can be executed before S1102 and S1103.

[0600] S1105. The RAN network element sends the sensing data to the SDPF network element.

[0601] Accordingly, the SDPF network element can receive and process the perception data to obtain processed perception data.

[0602] As mentioned above, the perception data received by the SDPF network element may be original perception data obtained by the RAN network element or perception data processed by the RAN network element. This article uses the example that the perception data received by the SDPF network element may be original perception data obtained by the RAN network element.

[0603] After the SDPF network element obtains the processed perception data, it may execute S1106.

[0604] S1106. The SDPF network element sends the first perception data to the ADFR network element.

[0605] Among them, the first perception data refers to the perception data processed by the SDPF network element.

[0606] Correspondingly, the ADFR network element receives and stores the first sensing data.

[0607] Exemplarily, the SDPF network element may send a data management storage request interface message to the ADFR network element, where the message includes the first sensing data. For example, the data management storage request interface may be a "Nadrf_DataManagement_StorageRequest" interface.

[0608] Optionally, the ADRF network element may return a response message to the SDPF network element to indicate confirmation of receipt of the first sensing data. For example, the response message may be a "Nadrf_DataManagement_StorageResponse" interface message.

[0609] The NF network element can execute S1107 according to the instructions of the response message 1 sent by the SSCF network element.

[0610] S1107. The NF network element sends a request message 2 to the ADRF network element, where the request message 2 is used to indicate a request to obtain the first perception data.

[0611] Correspondingly, the ADRF network element receives the request message 2. The request message 2 may be referred to as the aforementioned perception data request message.

[0612] Exemplarily, the request message 2 may be a data management retrieval request interface message. For example, the data management retrieval request interface may be a “Nadrf_DataManagement_RetrievalRequest” interface.

[0613] Optionally, the request message 2 may include a newly added field for indicating the acquisition of the first perception data. Alternatively, the request message 2 may also include a field obtained by modifying or extending an existing field to indicate the acquisition of the first perception data.

[0614] After the ADRF network element receives the request message 2, it can execute the following S1108 to return the first perception data to the NF network element.

[0615] Optionally, S1107 may also be executed before S1105, S1106, etc. This application does not limit the execution order of S1107. For example, after the NF network element receives the response message 1 from the SSCF network element and knows that the first perception data can be obtained from the ADRF network element, it can execute S1107. If the first perception data has not been received in the ADRF network element at this time, the ADRF network element can return an empty result to the NF network element.

[0616] S1108. The ADRF network element sends a response message 2 to the NF network element, where the response message 2 includes the first perception data.

[0617] Correspondingly, the NF network element receives response message 2, thereby receiving the first perception data.

[0618] Response message 2 may be the above-mentioned perception data response message.

[0619] Exemplarily, the response message 2 may be a data management retrieval response interface message. For example, the data management retrieval response interface may be a “Nadrf_DataManagement_RetrievalResponse” interface.

[0620] In the process shown in Figure 11, the SDPF network element can store the first perception data to the ADRF network element, and the NF network element obtains the first perception data from the ADRF network element.

[0621] For another example, taking the second network element as a RAN network element, Figure 12 shows another flow chart of the communication method provided in an embodiment of the present application. As shown in Figure 12, the communication method may include S1201-S1206.

[0622] S1201. The NF network element sends a request message 1 to the SSCF network element. The request message 1 is used to indicate a request to obtain the first perception data.

[0623] The request message 1 may be the first request message mentioned above.

[0624] Accordingly, the SSCF network element can receive the request message 1 from the NF network element.

[0625] S1202. The SSCF network element sends a control message 1 to the RAN network element. The control message 1 is used to instruct the reception of a perception signal and the sending of first perception data.

[0626] The control message 1 may be the first control message mentioned above. The control message 1 may be the control message sent by the SSCF network element to the RAN network element serving as the receiving perception entity. The process of the SSCF network element sending the control message to the sending perception entity is omitted here and will not be further described.

[0627] Accordingly, the RAN network element may receive the control message 1 from the SSCF network element.

[0628] S1201-S1202 can refer to the above-mentioned S601-S602 and will not be repeated here.

[0629] S1203. The SSCF network element sends a response message 1 to the NF network element. The response message 1 is used to instruct the acquisition of the first perception data from the ADRF network element.

[0630] Accordingly, the NF network element receives a response message 1. The response message 1 may be a response message to the request message 1. The response message 1 may be referred to as the first response message.

[0631] There is no restriction on the execution order of S1202 and S1203. For example, S1203 can be executed before S1202.

[0632] S1204. The RAN network element sends the first sensing data to the ADFR network element.

[0633] Correspondingly, the ADFR network element receives and stores the first sensing data.

[0634] As mentioned above, the first perception data may be original perception data obtained by the RAN network element or perception data processed by the RAN network element.

[0635] Exemplarily, the RAN network element may send a data management storage request interface message to the ADFR network element, where the message includes the first sensing data. For example, the data management storage request interface may be a "Nadrf_DataManagement_StorageRequest" interface.

[0636] Optionally, the ADRF network element may return a response message to the RAN network element to indicate confirmation of receiving the first sensing data. For example, the response message may be a "Nadrf_DataManagement_StorageResponse" interface message.

[0637] The NF network element can execute S1205 according to the instructions of the response message 1 sent by the SSCF network element.

[0638] S1205. The NF network element sends a request message 2 to the ADRF network element, where the request message 2 is used to indicate a request to obtain the first perception data.

[0639] Correspondingly, the ADRF network element receives the request message 2. The request message 2 may be referred to as the aforementioned perception data request message.

[0640] Exemplarily, the request message 2 may be a data management retrieval request interface message. For example, the data management retrieval request interface may be a “Nadrf_DataManagement_RetrievalRequest” interface.

[0641] Optionally, the request message 2 may include a newly added field for indicating the acquisition of the first perception data. Alternatively, the request message 2 may also include a field obtained by modifying or extending an existing field to indicate the acquisition of the first perception data.

[0642] After receiving the request message 2, the ADRF network element can execute the following S1206 to return the first perception data to the NF network element.

[0643] Optionally, S1205 may also be executed before S1204. This application does not limit the execution order of S1205. For example, after the NF network element receives the response message 1 from the SSCF network element and knows that the first perception data can be obtained from the ADRF network element, it can execute S1205. If the first perception data has not been received in the ADRF network element at this time, the ADRF network element can return an empty result to the NF network element.

[0644] S1206. The ADRF network element sends a response message 2 to the NF network element, where the response message 2 includes the first perception data.

[0645] Correspondingly, the NF network element receives response message 2, thereby receiving the first perception data.

[0646] Response message 2 may be the above-mentioned perception data response message.

[0647] Exemplarily, the response message 2 may be a data management retrieval response interface message. For example, the data management retrieval response interface may be a “Nadrf_DataManagement_RetrievalResponse” interface.

[0648] In the process shown in FIG12 , the RAN network element serving as the receiving perception entity may store the first perception data in the ADRF network element, and the NF network element obtains the first perception data from the ADRF network element.

[0649] Optionally, in the embodiment described above where the second network element stores the first perception data in the ADRF network element, and the NF network element obtains the first perception data from the ADRF network element, the first control message received by the second network element can specifically be used to instruct the second network element to send the first perception data to the ADRF network element. The second network element can be aware of the need to send the first perception data to the ADRF network element based on the instruction of the first control message.

[0650] Optionally, in some other embodiments, the second network element may also provide a data access address, and the second network element may use the data access address provided by the second network element as an interface for obtaining the first perception data, and the SSCF network element may send the data access address provided by the second network element to the first network element to implement sending the first perception data to the data requester. For example, when the first network element is an NEF network element, the first network element may send the data access address provided by the second network element to a third-party entity, and the third-party entity may access the data access address provided by the second network element to obtain the first perception data. Alternatively, when the first network element is a third-party entity, the third-party entity may directly access the data access address provided by the second network element to obtain the first perception data. The second network element may be an SDPF network element or a RAN network element serving as a receiving perception entity.

[0651] For example, the data access address provided by the second network element may be referred to as the first data access address. In this communication method, the SSCF network element may send a first response message to the first network element, and the first network element may receive the first response message. The first response message is used to indicate the first data access address. The first data access address is provided by the second network element and is used to obtain the first perception data. The second network element sending the first perception data may include: using the first data access address as an interface for obtaining the first perception data.

[0652] When the first network element is an NEF network element, a first data access address may be sent to a third-party entity. The third-party entity may send a first access request based on the first data access address, where the first access request is used to request the acquisition of first perception data. The second network element may receive the first access request. After receiving the first access request, the second network element may return a first access response message to the third-party entity. The first access response message includes the first perception data. The third-party entity may receive the first access response message to receive the first perception data from the second network element.

[0653] When the first network element is a third-party entity, the third-party entity can directly obtain the first data access address based on the first response message sent by the SSCF network element, and send a first access request based on the first data access address. The first access request is used to request to obtain the first perception data. The second network element can receive the first access request. After receiving the first access request, the second network element can return a first access response message to the third-party entity. The first access response message includes the first perception data. The third-party entity can receive the first access response message to receive the first perception data from the second network element.

[0654] Optionally, the first data access address may be sent by the second network element to the SSCF network element. For example, after receiving the first control message from the SSCF, the second network element may send a first control response message to the SSCF network element, where the first control response message indicates the first data access address. The SSCF network element may receive the first control response message. After obtaining the first data access address, the SSCF network element may send a first response message to the first network element.

[0655] Alternatively, the first data access address may be pre-obtained by the SSCF network element. For example, address interfaces corresponding to different perception services may be configured or pre-defined in the SSCF network element. These address interfaces are all address interfaces provided by the SDPF network element. That is, the first data access address provided by the SDPF network element may be configured or pre-defined in the SSCF network element. This application does not limit the manner in which the SSCF network element obtains the first data access address.

[0656] The following uses the example of a first network element being an NEF network element, a second network element being an SDPF network element, and a third-party entity sending a perception service request to an SSCF network element via the NEF network element as an example to illustrate the process in which the second network element provides a first data access address, and the third-party entity accesses the first data access address to obtain first perception data. The case where the first network element is a third-party entity is similar to this, except that the third-party entity does not interact with the SSCF network element via the NEF network element, which will not be further described.

[0657] For example, taking the first network element as an NEF network element and the second network element as an SDPF network element as an example, Figure 13 shows another flow chart of the communication method provided in an embodiment of the present application. As shown in Figure 13, the communication method may include S1301-S1310.

[0658] S1301. The third-party entity sends a request message 1 to the NEF network element, where the request message 1 is used to indicate a request to obtain first perception data.

[0659] Accordingly, the NEF network element may receive the request message 1 from the third-party entity.

[0660] S1302. The NEF network element sends a request message 2 to the SSCF network element. The request message 2 is used to indicate a request to obtain the first perception data.

[0661] Request message 2 may be the first request message mentioned above.

[0662] Correspondingly, the SSCF network element may receive the request message 2 from the NEF network element.

[0663] S1303. The SSCF network element sends a control message 1 to the SDPF network element. The control message 1 is used to instruct the sending of the first perception data.

[0664] The control message 1 may be the first control message mentioned above.

[0665] Accordingly, the SDPF network element may receive the control message 1 from the SSCF network element.

[0666] Optionally, the SDPF network element may return a response message to the SSCF network element, such as a first control response message, where the response message is used to indicate the first data access address provided by the SDPF network element.

[0667] S1304. The SSCF network element sends a control message 2 to the RAN network element. The control message 2 is used to instruct the reception of the perception signal.

[0668] The control message 2 may be a control message sent by the SSCF network element to the RAN network element serving as the receiving perception entity. The process of the SSCF network element sending the control message to the sending perception entity is omitted here and will not be further described.

[0669] Accordingly, the RAN network element may receive the control message 2 from the SSCF network element.

[0670] S1301-S1304 can refer to the above S701-S704 and will not be repeated here.

[0671] S1305. The SSCF network element sends a response message 1 to the NEF network element. The response message 1 is used to indicate the first data access address.

[0672] The response message 1 may be a response message to the request message 2. In this embodiment, the response message 1 may be referred to as a first response message. The first data access address is provided by the SDPF network element.

[0673] Correspondingly, the NEF network element receives the response message 1.

[0674] There is no restriction on the execution order of S1303 - S1305 .

[0675] S1306. The RAN network element sends the sensing data to the SDPF network element.

[0676] Accordingly, the SDPF network element can receive and process the perception data to obtain processed perception data.

[0677] As mentioned above, the perception data received by the SDPF network element may be original perception data obtained by the RAN network element or perception data processed by the RAN network element. This article uses the example that the perception data received by the SDPF network element may be original perception data obtained by the RAN network element.

[0678] After the SDPF network element obtains the processed perception data, it may execute S1307.

[0679] S1307. The SDPF network element uses the first data access address as an interface for obtaining the first perception data.

[0680] Among them, the first perception data refers to the perception data processed by the SDPF network element.

[0681] S1308. The NEF network element sends the first data access address to the third-party entity.

[0682] Accordingly, the third-party entity receives the first data access address.

[0683] Optionally, S1308 may also be executed before S1306, S1307, etc. This application does not limit the execution order of S1308. For example, after the NEF network element receives the response message 1 from the SSCF network element and knows the first data access address, it can execute S1308 and send the first data access address to the third-party entity.

[0684] Exemplarily, the first data access address may be sent in a response message sent by the NEF network element to the third-party entity. The response message may be a response message to the request message 1 .

[0685] S1309. The third-party entity sends a first access request according to the first data access address.

[0686] The first access request is used to request to obtain first perception data.

[0687] For example, a third-party entity may access the first data access address to obtain the first perception data.

[0688] Correspondingly, the SDPF network element receives the first data access request.

[0689] S1310. The SDPF network element sends a first access response message to the third-party entity, where the first access response message includes first perception data.

[0690] Accordingly, the third-party entity receives the first access response message, thereby receiving the first sensing data.

[0691] In the process shown in Figure 13, the SDPF network element can provide a first data access address as an interface for accessing the first perception data, and the third-party entity can actively obtain the first perception data by accessing the first data access address.

[0692] Optionally, the case where the second network element is a RAN network element serving as a receiving perception entity is similar to the case where the second network element is an SDPF network element as shown in Figure 13, with the difference that the first data access address is provided by the RAN network element, and the first perception data can be the original perception data obtained by the RAN network element or the perception data processed by the RAN network element. For details, please refer to the relevant embodiments in which the second network element is a RAN network element, which will not be repeated here.

[0693] It should be noted that when the third-party entity accesses the first data access address, if the first perception data is not yet ready, the second network element (e.g., SDPF network element) may return a special error code to the third-party entity. Alternatively, the third-party entity may be instructed to resend the first access request after a certain period of time to obtain the first perception data.

[0694] In the embodiment described above, in which the second network element provides the first data access address as an interface for accessing the first perception data, and the third-party entity actively obtains the first perception data by accessing the first data access address, the third-party entity can flexibly select the timing of actively obtaining the first perception data based on demand. For example, the third-party entity can select an appropriate time to send the first access request based on its own traffic conditions to avoid excessive data volume that cannot be handled by the traffic.

[0695] Optionally, in the embodiment where the second network element described above provides a first data access address as an interface for accessing the first perception data, and the third-party entity actively obtains the first perception data by accessing the first data access address, the first control message sent by the SSCF network element to the second network element can be specifically used to instruct the first data access address to be used as an interface for obtaining the first perception data. In other words, the first control message can specifically instruct the second network element to provide the data access address as an interface for obtaining the first perception data.

[0696] Optionally, in some other embodiments, the second network element may also transmit the first perception data to a user plane function (UPF) network element. The UPF network element may provide a data access address, and the UPF network element may use the data access address provided by the UPF network element as an interface for obtaining the first perception data. The SSCF network element may send the data access address provided by the UPF network element to the first network element to implement sending the first perception data to the data requester. For example, when the first network element is an NEF network element, the first network element may send the data access address provided by the UPF network element to a third-party entity, and the third-party entity may access the data access address provided by the UPF network element to obtain the first perception data. Alternatively, when the first network element is a third-party entity, the third-party entity may directly access the data access address provided by the UPF network element to obtain the first perception data. The second network element may be an SDPF network element or a RAN network element serving as a receiving perception entity.

[0697] For example, the data access address provided by the UPF network element can be called the first data access address. In this communication method, the SSCF network element can send a first response message to the first network element, and the first network element can receive the first response message. The first response message is used to indicate the first data access address. The first data access address is provided by the UPF network element and is used to obtain the first perception data. The second network element sending the first perception data may include: sending the first perception data to the UPF network element. The UPF network element can receive the first perception data from the second network element. After receiving the first perception data, the UPF network element can use the first data access address as an interface for obtaining the first perception data.

[0698] When the first network element is an NEF network element, a first data access address can be sent to a third-party entity. The third-party entity can send a first access request based on the first data access address, and the first access request is used to request to obtain the first perception data. The UPF network element can receive the first access request. After receiving the first access request, the UPF can return a first access response message to the third-party entity. The first access response message includes the first perception data. The third-party entity can receive the first access response message to receive the first perception data.

[0699] When the first network element is a third-party entity, the third-party entity can directly obtain the first data access address based on the first response message sent by the SSCF network element, and send a first access request based on the first data access address. The first access request is used to request to obtain the first perception data. The UPF network element can receive the first access request. After receiving the first access request, the UPF network element can return a first access response message to the third-party entity. The first access response message includes the first perception data. The third-party entity can receive the first access response message to receive the first perception data.

[0700] Optionally, the SSCF network element may further send a control message, such as a second control message, to the UPF network element to instruct the UPF network element to send the first sensing data. Accordingly, the UPF network element receives the second control message, where the second control message is used to instruct the sending of the first sensing data.

[0701] Optionally, the first data access address may be sent by the UPF network element to the SSCF network element. For example, after receiving the second control message from the SSCF, the UPF network element may send a second control response message to the SSCF network element, where the second control response message indicates the first data access address provided by the UPF network element. The SSCF network element may receive the second control response message. After obtaining the first data access address, the SSCF network element may send a first response message to the first network element.

[0702] Alternatively, the first data access address may be pre-obtained by the SSCF network element. For example, address interfaces corresponding to different perception services may be configured or pre-defined in the SSCF network element. These address interfaces are all address interfaces provided by the UPF network element. That is, the first data access address provided by the UPF network element may be configured or pre-defined in the SSCF network element. This application does not limit the manner in which the SSCF network element obtains the first data access address.

[0703] The following uses the example of a first network element being an NEF network element, a second network element being an SDPF network element, and a third-party entity sending a perception service request to an SSCF network element via the NEF network element as an example to illustrate the process in which the UPF network element provides a first data access address, and the third-party entity accesses the first data access address to obtain first perception data. The case in which the first network element is a third-party entity is similar, except that the third-party entity does not interact with the SSCF network element via the NEF network element, which will not be further described.

[0704] For example, taking the first network element as an NEF network element and the second network element as an SDPF network element as an example, Figure 14 shows another flow chart of the communication method provided in an embodiment of the present application. As shown in Figure 14, the communication method may include S1401-S1412.

[0705] S1401. The third-party entity sends a request message 1 to the NEF network element, where the request message 1 is used to indicate a request to obtain first perception data.

[0706] Accordingly, the NEF network element may receive the request message 1 from the third-party entity.

[0707] S1402. The NEF network element sends a request message 2 to the SSCF network element. The request message 2 is used to indicate a request to obtain the first perception data.

[0708] Request message 2 may be the first request message mentioned above.

[0709] Correspondingly, the SSCF network element may receive the request message 2 from the NEF network element.

[0710] S1403. The SSCF network element sends a control message 1 to the SDPF network element. The control message 1 is used to instruct the sending of the first perception data.

[0711] The control message 1 may be the first control message mentioned above.

[0712] Accordingly, the SDPF network element may receive the control message 1 from the SSCF network element.

[0713] S1404. The SSCF network element sends a control message 2 to the RAN network element. The control message 2 is used to instruct the reception of the perception signal.

[0714] The control message 2 may be a control message sent by the SSCF network element to the RAN network element serving as the receiving perception entity. The process of the SSCF network element sending the control message to the sending perception entity is omitted here and will not be further described.

[0715] Accordingly, the RAN network element may receive the control message 2 from the SSCF network element.

[0716] S1401-S1404 can refer to the above S701-S704 and will not be repeated here.

[0717] S1405. The SSCF network element sends a control message 3 to the UPF network element. The control message 3 is used to instruct the sending of the first perception data.

[0718] The control message 3 may be the second control message mentioned above.

[0719] Accordingly, the UPF network element can receive control message 3 from the SSCF network element.

[0720] Optionally, the UPF network element may return a response message, such as a second control response message, to the SSCF network element, where the response message is used to indicate the first data access address provided by the UPF network element.

[0721] S1406. The SSCF network element sends a response message 1 to the NEF network element. The response message 1 is used to indicate the first data access address.

[0722] The response message 1 may be a response message to the request message 2. In this embodiment, the response message 1 may be referred to as a first response message. The first data access address is provided by the UPF network element.

[0723] Correspondingly, the NEF network element receives the response message 1.

[0724] There is no restriction on the execution order of S1403 - S1406 .

[0725] S1407. The RAN network element sends the sensing data to the SDPF network element.

[0726] Accordingly, the SDPF network element can receive and process the perception data to obtain processed perception data.

[0727] As mentioned above, the perception data received by the SDPF network element may be original perception data obtained by the RAN network element or perception data processed by the RAN network element. This article uses the example that the perception data received by the SDPF network element may be original perception data obtained by the RAN network element.

[0728] After the SDPF network element obtains the processed perception data, it may execute S1408.

[0729] S1408. The SDPF network element sends the first perception data to the UPF network element.

[0730] Among them, the first perception data refers to the perception data processed by the SDPF network element.

[0731] Correspondingly, the UPF network element receives the first perception data.

[0732] S1409. The UPF network element uses the first data access address as an interface for obtaining the first perception data.

[0733] S1410. The NEF network element sends a first data access address to the third-party entity.

[0734] Accordingly, the third-party entity receives the first data access address.

[0735] Optionally, S1410 may also be executed before S1407, S1408, S1409, etc. This application does not limit the execution order of S1410. For example, after the NEF network element receives the response message 1 from the SSCF network element and knows the first data access address, it can execute S1410 and send the first data access address to the third-party entity.

[0736] S1411. The third-party entity sends a first access request according to the first data access address.

[0737] The first access request is used to request to obtain first perception data.

[0738] For example, a third-party entity may access the first data access address to obtain the first perception data.

[0739] Correspondingly, the UPF network element receives the first data access request.

[0740] S1412. The UPF network element sends a first access response message to the third-party entity, where the first access response message includes the first perception data.

[0741] Accordingly, the third-party entity receives the first access response message, thereby receiving the first sensing data.

[0742] In the process shown in Figure 14, the UPF network element can provide a first data access address as an interface for accessing the first perception data, and a third-party entity can actively obtain the first perception data by accessing the first data access address.

[0743] Optionally, the case where the second network element is a RAN network element serving as a receiving perception entity is similar to the case where the second network element is an SDPF network element as shown in Figure 14, with the difference that the first perception data in the UPF network element comes from the RAN network element, or the RAN network element sends the first perception data to the UPF network element, and the first perception data can be the original perception data obtained by the RAN network element or the perception data processed by the RAN network element. For details, please refer to the relevant embodiments in which the second network element is a RAN network element, which will not be repeated here.

[0744] It should be noted that when the third-party entity accesses the first data access address, if the first perception data is not yet ready, the UPF network element may return a special error code to the third-party entity. Alternatively, the third-party entity may be instructed to resend the first access request after a certain period of time to obtain the first perception data.

[0745] In the embodiment described above, the UPF network element provides a first data access address as an interface for accessing the first perception data. In the embodiment where the third-party entity actively obtains the first perception data by accessing the first data access address, the third-party entity can flexibly select the timing of actively obtaining the first perception data as needed. For example, the third-party entity can select an appropriate timing to send the first access request based on its own traffic conditions to avoid excessive data volume that cannot be handled by the traffic.

[0746] Optionally, in the embodiment where the UPF network element described above provides a first data access address as an interface for accessing the first perception data, and a third-party entity actively obtains the first perception data by accessing the first data access address, the first control message sent by the SSCF network element to the second network element can be specifically used to instruct the UPF network element to send the first perception data. The second control message sent by the SSCF network element to the UPF network element can be specifically used to instruct the first data access address to be used as an interface for obtaining the first perception data. In other words, the second control message can specifically instruct the UPF network element to provide the data access address as an interface for obtaining the first perception data.

[0747] In one possible design, the UPF network element described above provides a first data access address as an interface for accessing the first perception data. In an embodiment in which a third-party entity actively obtains the first perception data by accessing the first data access address, when a second network element (e.g., an SDPF network element or a RAN network element) sends the first perception data to the UPF network element, the first perception data can be sent to the UPF network element via a general packet radio service tunneling protocol user plane (GTPU) tunnel. Accordingly, the UPF network element receives the first perception data via the GTPU tunnel. General Packet Radio Service is referred to as GPRS.

[0748] For example, the GTPU tunneling protocol uses two layers of encapsulation addresses: an inner encapsulation address and an outer encapsulation address. The inner encapsulation address refers to the source and destination IP addresses of the user data packet and can be used to identify the actual source and destination of the user data packet. The outer encapsulation address refers to the source and destination IP addresses used during GTPU tunnel transmission and can be used to identify the source and destination of the GTPU tunnel.

[0749] In this embodiment, the second network element (e.g., an SDPF network element or a RAN network element) can encapsulate the first perception data to obtain a data packet of the first perception data. In the inner encapsulation address, the source IP address can be the IP address of the second network element, and the destination IP address can be the IP address of the UPF network element. In the outer encapsulation address, the source IP address can also be the IP address of the second network element, and the destination IP address can also be the IP address of the UPF network element. The second network element can send the data packet of the first perception data to the UPF network element via the GTPU tunnel.

[0750] It should be understood that before the second network element sends the first perception data to the UPF network element through the GTPU tunnel, a GTPU tunnel needs to be established in advance between the second network element and the UPF network element. In some implementations, the second network element may send a GTPU tunnel establishment request message to the UPF network element after receiving the first control message from the SSCF network element, and the UPF network element may return a GTPU tunnel establishment response message to the second network element, thereby establishing a GTPU tunnel between the two. Alternatively, the UPF network element may send a GTPU tunnel establishment request message to the second network element after receiving the second control message from the SSCF network element, and the second network element may return a GTPU tunnel establishment response message to the UPF network element, thereby establishing a GTPU tunnel between the two. Alternatively, the GTPU tunnel may also be established in advance. This application does not limit the timing and method of establishing the GTPU tunnel.

[0751] For example, taking the first network element as an NEF network element and the second network element as an SDPF network element as an example, Figure 15 shows another flow chart of the communication method provided in an embodiment of the present application. As shown in Figure 15, the communication method may include S1501-S1515.

[0752] S1501. A third-party entity sends a request message 1 to the NEF network element, where the request message 1 is used to indicate a request to obtain first perception data.

[0753] Accordingly, the NEF network element may receive the request message 1 from the third-party entity.

[0754] S1502. The NEF network element sends a request message 2 to the SSCF network element. The request message 2 is used to indicate a request to obtain the first perception data.

[0755] Correspondingly, the SSCF network element may receive the request message 2 from the NEF network element.

[0756] S1503. The SSCF network element sends a control message 1 to the SDPF network element. The control message 1 is used to instruct the sending of the first perception data.

[0757] Accordingly, the SDPF network element may receive the control message 1 from the SSCF network element.

[0758] S1504. The SSCF network element sends a control message 2 to the RAN network element. The control message 2 is used to instruct the reception of the perception signal.

[0759] Accordingly, the RAN network element may receive the control message 2 from the SSCF network element.

[0760] S1505. The SSCF network element sends a control message 3 to the UPF network element. The control message 3 is used to instruct the sending of the first perception data.

[0761] Accordingly, the UPF network element can receive control message 3 from the SSCF network element.

[0762] S1506. The SSCF network element sends a response message 1 to the NEF network element. The response message 1 is used to indicate the first data access address.

[0763] Correspondingly, the NEF network element receives the response message 1.

[0764] S1501-S1506 can refer to the above S1401-S1406 and will not be repeated here.

[0765] S1507. The SDPF network element sends a GTPU tunnel establishment request message to the UPF network element. The GTPU tunnel establishment request message is used to indicate a request to establish a GTPU tunnel.

[0766] Correspondingly, the UPF network element receives the GTPU tunnel establishment request message.

[0767] S1508. The UPF network element sends a GTPU tunnel establishment response message to the SDPF network element. The GTPU tunnel establishment response message is used to indicate confirmation of establishing the GTPU tunnel.

[0768] Correspondingly, the SDPF network element receives the GTPU tunnel establishment response message.

[0769] It should be understood that S1507-S1508 can be executed at any time before S1510 in Figure 15, and there is no limitation on the execution timing of S1507-S1508 (and the execution order compared with other steps).

[0770] S1509. The RAN network element sends the sensing data to the SDPF network element.

[0771] Accordingly, the SDPF network element can receive and process the perception data to obtain processed perception data.

[0772] S1509 can refer to S1407 and will not be described in detail.

[0773] After the SDPF network element obtains the processed perception data, it may execute S1510.

[0774] S1510. The SDPF network element encapsulates the first perception data to obtain a data packet of the first perception data.

[0775] The first perception data refers to the perception data processed by the SDPF network element. The inner encapsulation address and outer encapsulation address of the first perception data can be referred to as described above and will not be repeated here.

[0776] S1511. The SDPF network element sends a data packet of the first perception data to the UPF network element.

[0777] Correspondingly, the UPF network element receives the data packet of the first perception data.

[0778] After the UPF network element receives the data packet of the first perception data, it can parse the data packet to obtain the first perception data.

[0779] S1512. The UPF network element uses the first data access address as an interface for obtaining the first perception data.

[0780] S1513. The NEF network element sends the first data access address to the third-party entity.

[0781] Accordingly, the third-party entity receives the first data access address.

[0782] S1514. The third-party entity sends a first access request according to the first data access address.

[0783] The first access request is used to request to obtain first perception data.

[0784] Correspondingly, the UPF network element receives the first data access request.

[0785] S1515. The UPF network element sends a first access response message to the third-party entity, where the first access response message includes the first perception data.

[0786] Accordingly, the third-party entity receives the first access response message, thereby receiving the first sensing data.

[0787] S1512-S1515 can refer to the above S1409-S1412 and will not be repeated here.

[0788] In the process shown in Figure 15, a GTPU tunnel can be established between the SDPF network element and the UPF network element. The SDPF network element can send the first perception data to the UPF network element through the GTPU tunnel. The UPF network element can provide a first data access address as an interface for accessing the first perception data. A third-party entity can actively obtain the first perception data by accessing the first data access address.

[0789] The above introduces two solutions in which the second network element or UPF network element provides the first data access address as an interface for accessing the first perception data, and the third-party entity actively obtains the first perception data by accessing the first data access address.

[0790] Optionally, in some other embodiments, the data requester (such as a third-party entity) may provide a data push address when sending a perception service request, and the data push address may be sent to the SSCF network element. The SSCF network element may send the data push address provided by the data requester to the second network element. The second network element may send the first perception data to the data requester by sending the first perception data to the data push address. For example, when the first network element is an NEF network element, the third-party entity may send the data push address provided by the third-party entity to the first network element, and the first network element may send the data push address provided by the third-party entity to the SSCF network element. Alternatively, when the first network element is a third-party entity, the third-party entity may directly send the data push address provided by the third-party entity to the SSCF network element. The second network element may be an SDPF network element or a RAN network element serving as a receiving perception entity.

[0791] For example, the data push address provided by the third-party entity can be called the first data push address. In this communication method, when the first network element is an NEF network element, the third-party entity can send a perception service request (or called a second request message) to the NEF network element, and the perception service request carries or indicates the first data push address. The NEF network element can receive the perception service request and send a first request message to the SSCF network element, the first request message is used to indicate a request to obtain the first perception data, and indicates or carries the first data push address. The SSCF network element can receive the first request message and send a first control message to the second network element, the first control message is used to indicate the sending of the first perception data, and is used to indicate the first data push address. The first data push address is used for the second network element to send the first perception data. The second network element can receive the first control message. The second network element sends the first perception data, which may include: the second network element sends the first perception data to the first data push address. The third-party entity can receive the first perception data from the first data push address to receive the first perception data from the second network element.

[0792] When the first network element is a third-party entity, the third-party entity can directly send a first request message to the SSCF network element, where the first request message is used to indicate a request to obtain the first perception data and indicates or carries a first data push address. The SSCF network element can receive the first request message and send a first control message to the second network element, where the first control message is used to indicate the sending of the first perception data and to indicate the first data push address. The first data push address is used for the second network element to send the first perception data. The second network element can receive the first control message. The second network element sending the first perception data can include: the second network element sending the first perception data to the first data push address. The third-party entity can receive the first perception data from the first data push address to receive the first perception data from the second network element.

[0793] Optionally, the first data push address can also be pre-configured or sent to the SSCF network element and the second network element through other messages. For example, address interfaces corresponding to different perception services can be configured or predefined in the SSCF network element or the second network element. The address interfaces are all address interfaces provided by a third-party entity, that is, the first data push address provided by the third-party entity can be configured or predefined in the SSCF network element or the second network element. This application does not limit the way in which the SSCF network element and the second network element obtain the first data push address.

[0794] The following example uses the case where the first network element is an NEF network element, the second network element is an SDPF network element, and a third-party entity sends a perception service request to the SSCF network element through the NEF network element. The process of providing a first data push address to the third-party entity and the second network element sending the first perception data to the first data push address is exemplified. The case where the first network element is a third-party entity is similar to this, except that the third-party entity does not interact with the SSCF network element through the NEF network element, which will not be described in detail.

[0795] For example, taking the first network element as an NEF network element and the second network element as an SDPF network element as an example, Figure 16 shows another flow chart of the communication method provided in an embodiment of the present application. As shown in Figure 16, the communication method may include S1601-S1607.

[0796] S1601. A third-party entity sends a request message 1 to the NEF network element. The request message 1 is used to indicate a first data push address and request to obtain first perception data.

[0797] The request message 1 may be referred to as a second request message, and the first data push address is provided by a third-party entity.

[0798] Accordingly, the NEF network element may receive the request message 1 from the third-party entity.

[0799] S1602. The NEF network element sends a request message 2 to the SSCF network element. The request message 2 is used to indicate the first data push address and request to obtain the first perception data.

[0800] Request message 2 may be the first request message mentioned above.

[0801] Correspondingly, the SSCF network element may receive the request message 2 from the NEF network element.

[0802] S1603. The SSCF network element sends a control message 1 to the SDPF network element. The control message 1 is used to indicate the first data push address and send the first perception data.

[0803] The control message 1 may be the first control message mentioned above.

[0804] Accordingly, the SDPF network element may receive the control message 1 from the SSCF network element.

[0805] Optionally, the SDPF network element may return a response message to the SSCF network element.

[0806] S1604. The SSCF network element sends a control message 2 to the RAN network element. The control message 2 is used to instruct the reception of the perception signal.

[0807] The control message 2 may be a control message sent by the SSCF network element to the RAN network element serving as the receiving perception entity. The process of the SSCF network element sending the control message to the sending perception entity is omitted here and will not be further described.

[0808] Accordingly, the RAN network element may receive the control message 2 from the SSCF network element.

[0809] S1601-S1604 can refer to the above S701-S704, the difference is that in the steps described in S1601-S1603, the message indicates or carries the first data push address, which is used by the SDPF network element to send the first perception data. The other similar or identical parts will not be repeated.

[0810] S1605. The SSCF network element sends a response message 1 to the NEF network element.

[0811] Response message 1 may be a response message to request message 2. In this embodiment, response message 1 may be referred to as a first response message. Response message 1 may be used to indicate confirmation of receipt of the first data push address. Similarly, the NEF network element may send a response message to the third-party entity to indicate confirmation of receipt of the first data push address. S1605 may not be performed and is not limited here.

[0812] Correspondingly, the NEF network element receives the response message 1.

[0813] There is no restriction on the execution order of S1603 - S1605 .

[0814] S1606. The RAN network element sends the sensing data to the SDPF network element.

[0815] Accordingly, the SDPF network element can receive and process the perception data to obtain processed perception data.

[0816] As mentioned above, the perception data received by the SDPF network element may be original perception data obtained by the RAN network element or perception data processed by the RAN network element. This article uses the example that the perception data received by the SDPF network element may be original perception data obtained by the RAN network element.

[0817] After the SDPF network element obtains the processed perception data, it may execute S1607.

[0818] S1607. The SDPF network element sends the first perception data to the first data push address.

[0819] Among them, the first perception data refers to the perception data processed by the SDPF network element.

[0820] Accordingly, the third-party entity may receive the first perception data from the first data push address to achieve reception of the first perception data from the SDPF network element.

[0821] In the process shown in Figure 16, the third-party entity can provide a first data push address as an interface for the SDPF network element to send the first perception data. The SDPF network element can send the first perception data to the first data push address. The third-party entity can receive the first perception data from the first data push address. In other words, the third-party entity can passively receive the first perception data.

[0822] Optionally, the case where the second network element is a RAN network element serving as a receiving perception entity is similar to the case where the second network element is an SDPF network element shown in Figure 16, with the difference that the first perception data is sent by the RAN network element to the first data push address, and the first perception data may be the original perception data obtained by the RAN network element or the perception data processed by the RAN network element. For details, please refer to the relevant embodiments in which the second network element is a RAN network element, which will not be repeated here.

[0823] The third-party entity described above provides a first data push address, and the second network element sends the first perception data to the first data push address to implement an embodiment of sending the first perception data to the third-party entity. The third-party entity can use the first data push address to passively receive the first perception data from the second network element.

[0824] Optionally, the third-party entity mentioned above provides a first data push address, and the second network element sends the first perception data to the first data push address to implement an embodiment of sending the first perception data to the third-party entity. The first control message sent by the SSCF network element to the second network element can be specifically used to instruct the sending of the first perception data to the first data push address.

[0825] Optionally, in some other embodiments, the data requester (e.g., a third-party entity) may provide a data push address when sending a perception service request, and the data push address may be sent to the SSCF network element. The SSCF network element may send the data push address provided by the data requester to the UPF network element. The second network element may transmit the first perception data to the UPF network element, and the UPF network element may send the first perception data to the data requester by sending the first perception data to the data push address. For example, when the first network element is an NEF network element, the third-party entity may send the data push address provided by the third-party entity to the first network element, and the first network element may send the data push address provided by the third-party entity to the SSCF network element. Alternatively, when the first network element is a third-party entity, the third-party entity may directly send the data push address provided by the third-party entity to the SSCF network element. Among them, the second network element may be an SDPF network element or a RAN network element serving as a receiving perception entity.

[0826] For example, the data push address provided by the third-party entity can be called the first data push address. In this communication method, when the first network element is an NEF network element, the third-party entity can send a perception service request (or called a second request message) to the NEF network element, and the perception service request carries or indicates the first data push address. The NEF network element can receive the perception service request and send a first request message to the SSCF network element. The first request message is used to indicate a request to obtain the first perception data and indicates or carries the first data push address. The first data push address is used for the UPF network element to send the first perception data. The SSCF network element can receive the first request message and send a first control message to the second network element. The first control message is used to indicate the sending of the first perception data. The second network element can receive the first control message. The second network element sending the first perception data can include: the second network element sending the first perception data to the UPF network element. The UPF network element can receive the first perception data and send the first perception data to the first data push address. The third-party entity can receive the first perception data from the first data push address.

[0827] When the first network element is a third-party entity, the third-party entity can directly send a first request message to the SSCF network element, where the first request message is used to indicate a request to obtain the first perception data and indicates or carries the first data push address. The first data push address is used for the UPF network element to send the first perception data. The SSCF network element can receive the first request message and send a first control message to the second network element, where the first control message is used to indicate the sending of the first perception data. The second network element can receive the first control message. The second network element sending the first perception data may include: the second network element sending the first perception data to the UPF network element. The UPF network element can receive the first perception data and send the first perception data to the first data push address. The third-party entity can receive the first perception data from the first data push address.

[0828] Optionally, the SSCF network element may further send a control message, such as a second control message, to the UPF network element to instruct the UPF network element to send the first sensing data. Accordingly, the UPF network element receives the second control message, where the second control message is used to instruct the sending of the first sensing data.

[0829] In one implementation, the first data push address may be sent by the SSCF network element to the second network element, and then sent by the second network element to the UPF network element. For example, the first control message may also be used to indicate the first data push address. The first sensing data packet sent by the second network element to the UPF network element may carry or indicate the first data push address, so that the UPF network element can obtain the first data push address.

[0830] In another implementation, the first data push address may be sent directly by the SSCF network element to the UPF network element. For example, the communication method may further include: the SSCF network element sending a second control message to the UPF network element, where the second control message may indicate or carry the first data push address. The UPF network element may receive the second control message to obtain the first data push address.

[0831] Optionally, the second control message may not indicate or carry the first data push address, and the first data push address may also be sent to the UPF network element through pre-configuration, other methods, or other messages. For example, address interfaces corresponding to different perception services can be configured or predefined in the SSCF network element, the second network element, or the UPF network element. The address interfaces are all address interfaces provided by a third-party entity, that is, the first data push address provided by the third-party entity can be configured or predefined in the SSCF network element or the second network element, or in the UPF network element. This application does not limit the implementation method of the UPF network element obtaining the first data push address.

[0832] The following uses an example in which the first network element is an NEF network element, the second network element is an SDPF network element, and a third-party entity sends a perception service request to the SSCF network element via the NEF network element. The following describes an exemplary process in which a first data push address is provided to the third-party entity, and the UPF network element sends the first perception data to the first data push address to implement the sending of the first perception data to the third-party entity. The case in which the first network element is a third-party entity is similar, except that the third-party entity does not interact with the SSCF network element via the NEF network element, which is not described in detail here.

[0833] For example, taking the first network element as an NEF network element and the second network element as an SDPF network element as an example, Figure 17 shows another flow chart of the communication method provided in an embodiment of the present application. As shown in Figure 17, the communication method may include S1701-S1709.

[0834] S1701. The third-party entity sends a request message 1 to the NEF network element, where the request message 1 is used to indicate a first data push address and request to obtain first perception data.

[0835] The request message 1 may be referred to as a second request message, and the first data push address is provided by a third-party entity.

[0836] Accordingly, the NEF network element may receive the request message 1 from the third-party entity.

[0837] S1702. The NEF network element sends a request message 2 to the SSCF network element. The request message 2 is used to indicate the first data push address and request to obtain the first perception data.

[0838] Request message 2 may be the first request message mentioned above.

[0839] Correspondingly, the SSCF network element may receive the request message 2 from the NEF network element.

[0840] S1703. The SSCF network element sends a control message 1 to the SDPF network element. The control message 1 is used to indicate the first data push address and send the first perception data.

[0841] The control message 1 may be the first control message mentioned above.

[0842] Accordingly, the SDPF network element may receive the control message 1 from the SSCF network element.

[0843] Optionally, the SDPF network element may return a response message to the SSCF network element.

[0844] S1704. The SSCF network element sends a control message 2 to the RAN network element. The control message 2 is used to instruct the reception of the perception signal.

[0845] The control message 2 may be a control message sent by the SSCF network element to the RAN network element serving as the receiving perception entity. The process of the SSCF network element sending the control message to the sending perception entity is omitted here and will not be further described.

[0846] Accordingly, the RAN network element may receive the control message 2 from the SSCF network element.

[0847] S1701-S1704 can refer to the above S701-S704, the difference is that in the steps described in S1701-S1703, the message indicates or carries the first data push address, which is used by the UPF network element to send the first perception data, and the other similar or identical parts will not be repeated.

[0848] S1705. The SSCF network element sends a control message 3 to the UPF network element. The control message 3 is used to instruct the sending of the first perception data.

[0849] The control message 3 may be the second control message mentioned above.

[0850] Accordingly, the UPF network element can receive control message 3 from the SSCF network element.

[0851] Optionally, the UPF network element may return a response message, such as a second control response message, to the SSCF network element.

[0852] S1706. The SSCF network element sends a response message 1 to the NEF network element.

[0853] Response message 1 may be a response message to request message 2. In this embodiment, response message 1 may be referred to as a first response message. Response message 1 may be used to indicate confirmation of receipt of the first data push address. Similarly, the NEF network element may send a response message to the third-party entity to indicate confirmation of receipt of the first data push address. S1706 may not be performed and is not a limitation here.

[0854] Correspondingly, the NEF network element receives the response message 1.

[0855] There is no restriction on the execution order of S1703 - S1706 .

[0856] S1707. The RAN network element sends the sensing data to the SDPF network element.

[0857] Accordingly, the SDPF network element can receive and process the perception data to obtain processed perception data.

[0858] As mentioned above, the perception data received by the SDPF network element may be original perception data obtained by the RAN network element or perception data processed by the RAN network element. This article uses the example that the perception data received by the SDPF network element may be original perception data obtained by the RAN network element.

[0859] After the SDPF network element obtains the processed perception data, it may execute S1708.

[0860] S1708. The SDPF network element sends the first perception data to the UPF network element. The data packet of the first perception data carries the first data push address.

[0861] Among them, the first perception data refers to the perception data processed by the SDPF network element.

[0862] Correspondingly, the UPF network element receives the first perception data.

[0863] S1709. The UPF network element sends the first perception data to the first data push address.

[0864] Accordingly, the third-party entity may receive the first perception data from the first data push address.

[0865] In the process shown in Figure 17, the third-party entity can provide a first data push address as the interface for the UPF network element to send the first perception data. The SDPF network element can send the first perception data to the UPF network element, and the UPF network element can send the first perception data to the first data push address. The third-party entity can receive the first perception data from the first data push address. In other words, the third-party entity can passively receive the first perception data.

[0866] Optionally, the case where the second network element is a RAN network element serving as a receiving perception entity is similar to the case where the second network element is an SDPF network element as shown in Figure 17, with the difference that the first perception data is sent by the RAN network element to the UPF network element, and the UPF network element sends the first perception data to the first data push address, and the first perception data can be the original perception data obtained by the RAN network element or the perception data processed by the RAN network element. For details, please refer to the relevant embodiments in which the second network element is a RAN network element, which will not be repeated here.

[0867] The third-party entity mentioned above provides a first data push address, and in an embodiment in which the UPF network element sends the first perception data to the first data push address to send the first perception data to the third-party entity, the third-party entity can use the first data push address to passively receive the first perception data sent by the UPF network element, and the first perception data in the UPF network element comes from the second network element.

[0868] Optionally, in an embodiment in which the third-party entity described above provides a first data push address, and the UPF network element sends the first perception data to the first data push address to implement sending the first perception data to the third-party entity, the first control message sent by the SSCF network element to the second network element can be specifically used to instruct the UPF network element to send the first perception data. The second control message sent by the SSCF network element to the UPF network element can be specifically used to instruct the UPF network element to send the first perception data to the first data push address, or the second network element can also instruct the UPF network element to send the first perception data to the first data push address.

[0869] Optionally, similar to the embodiment described above in which the UPF network element provides a first data access address as an interface for a third-party entity to access the first perception data, in a possible design, the third-party entity described above provides a first data push address, and in an embodiment in which the UPF network element sends the first perception data to the first data push address, when the second network element (e.g., an SDPF network element or a RAN network element) sends the first perception data to the UPF network element, the first perception data may be sent to the UPF network element through a GTPU tunnel. Accordingly, the UPF network element receives the first perception data through the GTPU tunnel.

[0870] In this embodiment, the second network element (such as an SDPF network element or a RAN network element) can encapsulate the first perception data to obtain a data packet of the first perception data. In the inner encapsulation address, the source IP address can be the IP address of the second network element, and the destination IP address can be the first data push address provided by a third-party entity. In the outer encapsulation address, the source IP address can be the IP address of the second network element, and the destination IP address can be the IP address of the UPF network element. The second network element can send a data packet of the first perception data to the UPF network element through the GTPU tunnel. The UPF network element can parse the data packet of the first perception data, obtain the first perception data and the first data push address, and send the first perception data to the first data push address. In other words, the second network element can encapsulate the first data push address in the data packet of the first perception data to instruct the UPF network element to send the first perception data to the first data push address.

[0871] It should also be understood that before the second network element sends the first perception data to the UPF network element through the GTPU tunnel, a GTPU tunnel needs to be established in advance between the second network element and the UPF network element. The GTPU tunnel establishment process can be referred to the above embodiment and will not be repeated here.

[0872] For example, taking the first network element as an NEF network element and the second network element as an SDPF network element as an example, Figure 18 shows another flow chart of the communication method provided in an embodiment of the present application. As shown in Figure 18, the communication method may include S1801-S1812.

[0873] S1801. A third-party entity sends a request message 1 to an NEF network element. The request message 1 is used to indicate a first data push address and request to obtain first perception data.

[0874] Accordingly, the NEF network element may receive the request message 1 from the third-party entity.

[0875] S1802. The NEF network element sends a request message 2 to the SSCF network element. The request message 2 is used to indicate the first data push address and request to obtain the first perception data.

[0876] Correspondingly, the SSCF network element may receive the request message 2 from the NEF network element.

[0877] S1803. The SSCF network element sends a control message 1 to the SDPF network element. The control message 1 is used to indicate the first data push address and send the first perception data.

[0878] Accordingly, the SDPF network element may receive the control message 1 from the SSCF network element.

[0879] S1804. The SSCF network element sends a control message 2 to the RAN network element. The control message 2 is used to instruct the reception of the perception signal.

[0880] Accordingly, the RAN network element may receive the control message 2 from the SSCF network element.

[0881] S1805. The SSCF network element sends a control message 3 to the UPF network element. The control message 3 is used to instruct the sending of the first perception data.

[0882] Accordingly, the UPF network element can receive control message 3 from the SSCF network element.

[0883] S1806. The SSCF network element sends a response message 1 to the NEF network element.

[0884] Correspondingly, the NEF network element receives the response message 1.

[0885] S1801-S1806 can refer to the above S1701-S1706 and will not be repeated here.

[0886] S1807. The SDPF network element sends a GTPU tunnel establishment request message to the UPF network element. The GTPU tunnel establishment request message is used to indicate a request to establish a GTPU tunnel.

[0887] Correspondingly, the UPF network element receives the GTPU tunnel establishment request message.

[0888] S1808. The UPF network element sends a GTPU tunnel establishment response message to the SDPF network element. The GTPU tunnel establishment response message is used to indicate confirmation of establishing the GTPU tunnel.

[0889] Correspondingly, the SDPF network element receives the GTPU tunnel establishment response message.

[0890] It should be understood that S1807-S1808 can be executed at any time before S1810 in Figure 18, and there is no limitation on the execution timing of S1807-S1808 (and the execution order compared with other steps).

[0891] S1809. The RAN network element sends the sensing data to the SDPF network element.

[0892] Accordingly, the SDPF network element can receive and process the perception data to obtain processed perception data.

[0893] S1809 can refer to S1807 and will not be repeated here.

[0894] After the SDPF network element obtains the processed perception data, it may execute S1810.

[0895] S1810. The SDPF network element encapsulates the first perception data to obtain a data packet of the first perception data.

[0896] The first perception data refers to the perception data processed by the SDPF network element. The inner encapsulation address and outer encapsulation address of the first perception data can be referred to as described above and will not be repeated here.

[0897] S1811. The SDPF network element sends a data packet of the first perception data to the UPF network element.

[0898] Correspondingly, the UPF network element receives the data packet of the first perception data.

[0899] After the UPF network element receives the data packet of the first perception data, it can parse the data packet to obtain the first perception data and the first data push address.

[0900] S1812. The UPF network element sends the first perception data to the first data push address.

[0901] Accordingly, the third-party entity may receive the first perception data from the first data push address.

[0902] In the process shown in Figure 18, a GTPU tunnel can be established between the SDPF network element and the UPF network element. The SDPF network element can send the first perception data to the UPF network element through the GTPU tunnel. A third-party entity can provide a first data push address as an interface for the UPF network element to send the first perception data. The UPF network element can send the first perception data to the first data push address. The third-party entity can receive the first perception data from the first data push address. In other words, the third-party entity can passively receive the first perception data.

[0903] It should be understood that the manner in which a data requester obtains sensory data in the various embodiments described above in this application is applicable to any type of data requester. The descriptions of NF network elements, third-party entities, and the like described above are merely examples. This application does not limit the specific form or type of data requester for any of the aforementioned methods of exposing sensory data.

[0904] For example, the second network element (e.g., an SDPF network element or a RAN network element) may also store the first perception data in an ADRF network element, and the third-party entity may obtain the first perception data from the ADRF network element. For example, the second network element may transmit the first perception data to the ADRF network element, and the NEF network element may obtain the first perception data from the ADRF network element. The NEF network element may transmit the obtained first perception data to the third-party entity.

[0905] For another example, the second network element (e.g., an SDPF network element or a RAN network element) may also provide a first data access address, and the NF network element within the network may access the first data access address to obtain the first perception data. Alternatively, the second network element (e.g., an SDPF network element or a RAN network element) may also transmit the first perception data to the UPF network element. The UPF network element may provide the first data access address, and the NF network element within the network may access the first data access address to obtain the first perception data.

[0906] For another example, a NF network element within the network may also provide a first data push address. A second network element (e.g., an SDPF network element or a RAN network element) may send the first perception data to the NF network element via the first data push address. Alternatively, the second network element (e.g., an SDPF network element or a RAN network element) may also transmit the first perception data to a UPF network element, and the UPF network element may send the first perception data to the NF network element via the first data push address.

[0907] As described in the above embodiments, the manner in which the second network element (eg, SDPF network element or RAN network element) transmits the perception data to the data requester may be indicated by the SSCF network element through the first control message.

[0908] Optionally, in some embodiments, a transmission policy may be configured in the SSCF network element. The SSCF network element may determine, based on the configured transmission policy, the manner in which the second network element (e.g., an SDPF network element or a RAN network element) transmits the perception data to the data requester. For example, the transmission policy may be: when the data requester sends a data push address, instructing the second network element (e.g., an SDPF network element or a RAN network element) or the UPF network element to send the perception data to the data push address. When the data requester does not send a data push address, instructing the second network element (e.g., an SDPF network element or a RAN network element) or the UPF network element to provide a data access address to send the perception data to the data requester, or the second network element transmits the perception data through the DCP network element, etc.

[0909] Alternatively, the transmission strategy may also be related to the service. For example, the data requester may request perception data for different perception services. The same or different transmission methods can be configured for different perception services. For example, for perception service 1, the second network element (such as an SDPF network element or a RAN network element) or the UPF network element provides a data access address to send the perception data to the data requester. For perception service 2, the second network element (such as an SDPF network element or a RAN network element) transmits the perception data through the DCP network element, etc.

[0910] Alternatively, in some other embodiments, the transmission policy may be directly configured in the second network element, and the second network element may directly transmit the sensing data according to the transmission policy. This application does not limit the transmission policy and configuration method.

[0911] Optionally, in some other embodiments, the data requester can independently select a method for obtaining the perception data. For example, the perception service request (such as the first request message described above) sent by the data requester can carry or indicate a result response method. The result response method indicates the method by which the data requester expects the second network element (e.g., SDPF network element or RAN network element) to transmit the perception data to the data requester.

[0912] For example, when the result response method includes a data push address, it indicates that the data requester expects the second network element (e.g., SDPF network element or RAN network element) or UPF network element to send the perception data to the data requester through the data push address. For another example, the result response method may indicate that the second network element (e.g., SDPF network element or RAN network element) or UPF network element is expected to provide a data access address, and the data requester can obtain the perception data through the data access address.

[0913] Similarly, when the data requester independently selects a method for obtaining perception data, the same or different perception data transmission methods may be selected for different perception services.

[0914] In other words, the first request message described in the above embodiment may also include a result response mode, such as the result response mode may be a field. The result response mode is used to indicate the desired perception data transmission mode, and the perception data transmission mode may be as described in the above embodiment. For example, the second network element (such as an SDPF network element or a RAN network element) transmits perception data to the data requester through the first data access address, or the UPF network element transmits perception data to the data requester through the first data access address, or the second network element (such as an SDPF network element or a RAN network element) sends perception data to the first data push address, or the UPF network element sends perception data to the first data push address, or the second network element sends perception data through the DCP network element, etc.

[0915] Optionally, in each of the above-described embodiments, when any two network elements (taking network element 1 and network element 2 as an example) interact with each other, after network element 1 sends a request message or a control message to network element 2, network element 2 may return a response message to network element 1. This response message may carry other information or may not carry any information and is merely used to confirm receipt. This application does not further describe these response messages.

[0916] Optionally, the names of the various messages mentioned in the embodiments of the present application, such as the first control message, the first request message, the first response message, etc., may also be other descriptions, and each message may be implemented through the same or different interfaces. For example, each message can utilize the existing interface between the interacting network elements or define a new interface when implemented. This application does not limit the name and implementation method of each message.

[0917] Optionally, in an embodiment of the present application, the SSCF network element can be mounted on a service-based inferface (SBI) bus to communicate with other core network function modules. The SDPF network element can be mounted on an SBI bus to communicate with other core network function modules via the SBI, or can communicate through a separate interface, for example, through a separate interface to communicate with other SDPF network elements, or through a separate interface to communicate with an SSCF network element.

[0918] In one possible networking architecture, RAN network elements connect to SSCF network elements via the access and mobility management function (AMF), and RAN network elements connect to SDPF network elements via the user plane function (UPF). SDPF network elements are attached to the SBI bus via the SBI, and SSCF network elements are attached to the SBI bus via the SBI. RAN network elements can communicate with SSCF network elements on the control plane via the AMF network element, and communicate with SDPF network elements on the data plane via the UPF network element.

[0919] In another possible networking architecture, RAN network elements can be directly connected to SSCF network elements. RAN network elements can also be connected to SDPF network elements through UPF network elements. SDPF network elements are attached to the SBI bus through the SBI interface, while SSCF network elements are not attached to the SBI bus. RAN network elements can directly communicate with SSCF network elements on the control plane, and can communicate with SDPF network elements on the data plane through UPF network elements.

[0920] In another possible networking architecture, RAN network elements connect to SSCF network elements through AMF network elements, and RAN network elements connect to SDPF network elements through UPF network elements. SDPF network elements are not mounted on the SBI bus, and SSCF network elements are mounted on the SBI bus through SBI. RAN network elements can communicate with SSCF network elements on the control plane through AMF network elements, and communicate with SDPF network elements on the data plane through UPF network elements.

[0921] In another possible networking architecture, RAN network elements can directly connect to SSCF network elements, and RAN network elements can connect to SDPF network elements through UPF network elements. SDPF network elements are not mounted on the SBI bus, and SSCF network elements are not mounted on the SBI bus. RAN network elements can directly communicate with SSCF network elements on the control plane, and can communicate with SDPF network elements on the data plane through UPF network elements.

[0922] In another possible networking architecture, RAN network elements connect to SSCF network elements through AMF network elements. RAN network elements can directly connect to SDPF network elements. SDPF network elements are mounted to the SBI bus through SBI, and SSCF network elements are mounted to the SBI bus through SBI. RAN network elements can communicate with SSCF network elements on the control plane through AMF network elements, and RAN network elements can communicate directly with SDPF network elements on the data plane.

[0923] In another possible networking architecture, RAN network elements can be directly connected to SSCF network elements, and RAN network elements can be directly connected to SDPF network elements. SDPF network elements are mounted to the SBI bus via SBI, while SSCF network elements are not mounted to the SBI bus. RAN network elements can directly communicate with SSCF network elements on the control plane, and RAN network elements can directly communicate with SDPF on the data plane.

[0924] In another possible networking architecture, RAN network elements connect to SSCF network elements through AMF network elements. RAN network elements can directly connect to SDPF network elements. SDPF network elements are not mounted on the SBI bus, and SSCF network elements are mounted on the SBI bus through SBI. RAN network elements can communicate with SSCF network elements on the control plane through AMF network elements, and RAN network elements can communicate directly with SDPF network elements on the data plane.

[0925] In another possible networking architecture, RAN network elements can be directly connected to SSCF network elements, and RAN network elements can be directly connected to SDPF network elements. SDPF network elements are not mounted on the SBI bus, and SSCF network elements are not mounted on the SBI bus. RAN network elements can directly communicate with SSCF network elements on the control plane, and RAN network elements can directly communicate with SDPF network elements on the data plane.

[0926] As described above, in the embodiments of the present application, the RAN network element can directly communicate with the SSCF network element on the control plane, or communicate with the SSCF network element on the control plane through the AMF network element. The SDPF network element can be mounted on the SBI bus or not mounted on the SBI bus. The RAN network element can directly communicate with the SDPF network element on the data plane, or communicate with the SDPF network element on the data plane through the UPF network element. Among them, control plane communication refers to the transmission of control plane messages, such as the control messages in the embodiments of the present application; data plane communication refers to the transmission of perception data and / or perception results. The interaction between network elements such as the RAN network element, UPF network element, SSCF network element, and SDPF network element in the aforementioned embodiments of the present application can be implemented based on any of the possible networking architectures described above, and the present application does not impose any restrictions on this.

[0927] Optionally, the SSCF network element and the SDPF network element can be independently upgraded and maintained, so that the network can flexibly deploy and manage core network functional entities. In actual implementation, the number of SDPF network elements can also be increased or decreased according to actual needs.

[0928] Based on the above embodiments, the embodiments of the present application actually provide methods that can be applied to different network element sides, for example, the SSCF network element, the first network element, the second network element, etc. The method corresponding to each network element side can refer to the steps performed by each network element in the above embodiments.

[0929] It should be noted that for the aforementioned method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by this application.

[0930] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of the interaction between various network elements. It is understandable that each network element, such as the SSCF network element, the first network element, the second network element, the DCP network element, the UPF network element, etc., includes the corresponding hardware structure and / or software module to perform each function in order to implement the above functions.

[0931] For example, an embodiment of the present application may provide a communication device for implementing the functions of the above-mentioned SSCF network element. The communication device may be a communication device that deploys or carries the SSCF network element, or may be a device (e.g., a chip or software module) in a communication device that deploys or carries the SSCF network element. Figure 19 shows a schematic structural diagram of the communication device provided in an embodiment of the present application. As shown in Figure 19, the communication device may include: a sending unit 1901 and a receiving unit 1902.

[0932] Among them, the receiving unit 1901 is used to receive a first request message from a first network element, and the first request message is used ...

Claims

1. A communication method, characterized in that, The method is applied to a perception service control function network element, and the method includes: Receiving a first request message from a first network element, where the first request message is used to indicate a request to obtain first perception data; Sending a first control message to a second network element, where the first control message is used to indicate sending the first perception data.

2. The method according to claim 1, characterized in that, Specifically, the first control message is used to indicate sending the first perception data to the first network element.

3. The method according to claim 1, characterized in that The method further includes: Sending a first response message to the first network element, where the first response message is used to indicate a first topic, and the first topic is used to subscribe to the first perception data from a data communication proxy network element; The first topic is a publishing topic of the first perception data in the data communication proxy network element, and the first perception data comes from the second network element.

4. The method according to claim 3, wherein Specifically, the first control message is used to indicate publishing the first perception data to the data communication proxy network element according to the first topic.

5. The method according to claim 1, characterized in that The method further includes: Sending a first response message to the first network element, where the first response message is used to indicate a first data access address; The first data access address is provided by the second network element and is used to obtain the first perception data; Alternatively, the first data access address is provided by a user plane function network element and is used to obtain the first perception data, and the first perception data in the user plane function network element comes from the second network element.

6. The method according to claim 5, wherein The first data access address is provided by the second network element, and specifically, the first control message is used to indicate using the first data access address as an interface for obtaining the first perception data; Alternatively, the first data access address is provided by the user plane function network element, and specifically, the first control message is used to indicate sending the first perception data to the user plane function network element.

7. The method according to claim 5 or 6, characterized in that, The first data access address is provided by the user plane function network element, and the method further includes: Sending a second control message to the user plane function network element, where the second control message is used to indicate using the first data access address as an interface for obtaining the first perception data.

8. The method according to claim 7, wherein The method further includes: Receiving a second control response message from the user plane function network element, where the second control response message is used to indicate the first data access address.

9. The method according to claim 5 or 6, characterized in that, The first data access address is provided by the second network element, and the method further includes: Receiving a first control response message from the second network element, where the first control response message is used to indicate the first data access address.

10. The method according to claim 1, characterized in that, The first request message is further used to indicate a first data push address provided by a third-party entity, and the first control message is further used to indicate the first data push address; The first data push address is used for the second network element to send the first perception data; Alternatively, the first data push address is used for the user plane function network element to send the first perception data, and the first perception data in the user plane function network element comes from the second network element.

11. The method according to claim 10, characterized in that, The first data push address is used for the second network element to send the first perception data, and specifically, the first control message is used to indicate sending the first perception data to the first data push address.

12. The method according to claim 10, wherein The first data push address is used for the user plane function network element to send the first perception data, and the first control message is specifically used to instruct to send the first perception data to the user plane function network element.

13. The method according to claim 12, wherein The method further includes: Sending a second control message to the user plane function network element, where the second control message is used to instruct to send the first perception data to the first data push address.

14. The method according to claim 1, characterized in that The method further includes: Sending a first response message to the first network element, where the first response message is used to instruct to obtain the first perception data from the data analysis and storage repository function network element, and the first perception data in the data analysis and storage repository function network element comes from the second network element.

15. The method according to claim 14, wherein The first control message is specifically used to instruct to send the first perception data to the data analysis and storage repository function network element.

16. The method according to any one of claims 1-13, characterized in that, The first network element is a network openness function network element or a third-party entity.

17. The method according to any one of claims 1, 14, and 15, characterized in that The first network element is a network function network element.

18. A communication method, characterized in that, The method is applied to a second network element, and the method includes: Receiving a first control message from a perception service control function network element, where the first control message is used to instruct to send first perception data; Sending the first perception data.

19. The method according to claim 18, characterized in that, The sending of the first perception data includes: Sending the first perception data to a first network element.

20. The method according to claim 19, wherein The first control message is specifically used to instruct to send the first perception data to the first network element.

21. The method according to claim 18, wherein The sending of the first perception data includes: Sending the first perception data to a data communication proxy network element according to a first topic.

22. The method according to claim 21, wherein The first control message is specifically used to instruct to send the first perception data to the data communication proxy network element according to a first topic.

23. The method according to claim 18, wherein The sending of the first perception data includes: Using a first data access address as an interface for obtaining the first perception data, where the first data access address is provided by the second network element.

24. The method according to claim 23, wherein The first control message is specifically used to instruct to use the first data access address as an interface for obtaining the first perception data.

25. The method according to claim 23 or 24, characterized in that, The method further includes: Sending a first control response message to the perception service control function network element, where the first control response message is used to indicate the first data access address.

26. The method according to claim 18, wherein The sending of the first perception data includes: Sending the first perception data to a user plane function network element.

27. The method according to claim 26, wherein The first control message is specifically used to instruct to send the first perception data to the user plane function network element.

28. The method according to claim 26 or 27, characterized in that, The sending of the first perception data to the user plane function network element includes: Sending the first perception data to the user plane function network element through a General Packet Radio Service Tunnel Protocol - User Plane Tunnel.

29. The method according to any one of claims 26 - 28, characterized in that, The first control message is further used to indicate a first data push address provided by a third-party entity; The data packet of the first perception data sent to the user plane function network element is encapsulated with the first data push address, and the first data push address is used for the user plane function network element to send the first perception data.

30. The method according to claim 18, characterized in that, The first control message is further used to indicate a first data push address provided by a third-party entity, and the sending of the first perception data includes: Sending the first perception data to the first data push address.

31. The method according to claim 30, characterized in that, The first control message is specifically used to instruct to send the first sensed data to the first data push address.

32. The method according to claim 18, wherein The sending of the first sensed data includes: Sending the first sensed data to the data analysis and storage repository functional network element.

33. The method according to claim 32, wherein The first control message is specifically used to instruct to send the first sensed data to the data analysis and storage repository functional network element.

34. The method according to claim 19 or 20, characterized in that, The first network element is a network exposure function network element or a third-party entity.

35. A communication method, characterized in that, The method is applied to a first network element, and the method includes: Sending a first request message to a sensing service control functional network element, the first request message being used to instruct to request to obtain first sensed data; Receiving the first sensed data from a second network element.

36. The method according to claim 35, wherein The method further includes: Receiving a first response message from the sensing service control functional network element, the first response message being used to indicate a first topic; Sending a subscription request message to a data communication proxy network element, the subscription request message being used to indicate the first topic and to subscribe to the first sensed data from the data communication proxy network element; Receiving a subscription response message from the data communication proxy network element; The receiving of the first sensed data from the second network element includes: Receiving the first sensed data sent by the data communication proxy network element.

37. The method according to claim 35 or 36, characterized in that, The first network element is a network exposure function network element or a third-party entity; When the first network element is the network exposure function network element, the method further includes: Sending the first sensed data to a third-party entity.

38. The method according to claim 35, wherein When the first network element is a third-party entity, the method further includes: Receiving a first response message from the sensing service control functional network element, the first response message being used to indicate a first data access address provided by the second network element or the user plane function network element; Sending a first access request according to the first data access address, the first access request being used to request to obtain the first sensed data; The receiving of the first sensed data from the second network element includes: Receiving a first access response message, the first access response message including the first sensed data from the second network element.

39. The method according to claim 35, wherein When the first network element is a third-party entity, the first request message is further used to indicate a first data push address provided by the third-party entity; The first data push address is used for the second network element to send the first sensed data; Alternatively, the first data push address is used for the user plane function network element to send the first sensed data, and the first sensed data in the user plane function network element comes from the second network element; The receiving of the first sensed data from the second network element includes: Receiving the first sensed data from the first data push address.

40. The method according to claim 35, characterized in that, When the first network element is a network function network element, the method further includes: Receiving a first response message from the sensing service control functional network element, the first response message being used to indicate to obtain the first sensed data from the data analysis and storage repository functional network element; Sending a sensed data request message to the data analysis and storage repository functional network element, the sensed data request message being used to request to obtain the first sensed data; Receiving the first sensing data from a second network element includes: Receiving a sensing data response message from the data analysis and storage repository function network element, where the sensing data response message includes the first sensing data, and the first sensing data in the data analysis and storage repository function network element comes from the second network element.

41. A communication method, characterized in that, The method is applied to a network exposure function network element, and the method includes: Sending a first request message to a sensing service control function network element, where the first request message is used to indicate a request to obtain first sensing data; Receiving a first response message from the sensing service control function network element, where the first response message is used to indicate a first data access address provided by a second network element or a user plane function network element for obtaining the first sensing data; Sending the first data access address to a third-party entity.

42. A communication method, characterized in that, The method is applied to a network exposure function network element, and the method includes: Sending a first request message to a sensing service control function network element, where the first request message is used to indicate a request to obtain first sensing data and is used to indicate a first data push address provided by a third-party entity; The first data push address is used for the second network element to send the first sensing data; Alternatively, the first data push address is used for the user plane function network element to send the first sensing data, and the first sensing data in the user plane function network element comes from the second network element.

43. A communication method, characterized in that, The method is applied to a user plane function network element, and the method includes: Receiving the first sensing data from a second network element; Using the first data access address as an interface for obtaining the first sensing data, where the first data access address is provided by the user plane function network element; Alternatively, sending the first sensing data to a first data push address provided by a third-party entity.

44. The method according to claim 43, wherein Receiving the first sensing data from a second network element includes: Receiving the first sensing data from the second network element through a General Packet Radio Service Tunneling Protocol - User Plane Tunnel.

45. The method according to claim 43 or 44, characterized in that The data packet of the received first sensing data is encapsulated with the first data push address.

46. The method according to claim 43 or 44, characterized in that, The method further includes: Receiving a second control message from the sensing service control function network element, where the second control message is used to indicate using the first data access address as an interface for obtaining the first sensing data.

47. The method according to claim 46, characterized in that, The method further includes: Sending a second control response message to the sensing service control function network element, where the second control response message is used to indicate the first data access address.

48. The method according to claim 43 or 44, characterized in that, The method further includes: Receiving a second control message from the sensing service control function network element, where the second control message is used to indicate sending the first sensing data to a first data push address provided by a third-party entity.

49. A communication method, characterized in that, The method is applied to a data communication proxy network element, and the method includes: Receiving a subscription request message from a first network element, where the subscription request message is used to indicate a first topic and is used to subscribe to first sensing data from the data communication proxy network element; Sending a subscription response message to the first network element; Receiving the first sensing data from a second network element, where the first sensing data is published according to the first topic; Sending the first sensing data to the first network element.

50. A communication method, characterized in that, The method is applied to a data analysis repository functional network element, and the method includes: Receiving first perception data from a second network element; Receiving a perception data request message from a first network element, where the perception data request message is used to request to obtain the first perception data; Sending a perception data response message to the first network element, where the perception data response message includes the first perception data.

51. The method according to any one of claims 1-50, characterized in that, The second network element is an access network element or a perception data processing functional network element.

52. A communication device, characterized in that, The communication device includes a module for executing the method according to any one of claims 1-51.

53. A communication device, characterized in that, The device includes: a processor configured to execute the method according to any one of claims 1-51.

54. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes instructions that, when run, cause the method according to any one of claims 1-51 to be implemented.

55. A computer program product, characterized in that, When the computer program product is executed, the method according to any one of claims 1-51 is implemented.

56. A chip system, characterized in that, The chip system includes one or more interface circuits and one or more processors; The interface circuit and the processor are interconnected by a line; The processor receives and executes computer instructions from the memory of the electronic device through the interface circuit to implement the method according to any one of claims 1-51.

Images