Method and apparatus for sensing data transmission protocol negotiation, device and program product

Abstract

The present disclosure relates to a method and device for sensing data transmission protocol negotiation, an electronic device and a computer program product, and relates to the technical field of wireless communication, which can be applied to integrated sensing and communication scenarios in future networks. The method is applied to a sensing function, and includes: performing protocol negotiation with an associated function entity based on a received sensing service request, obtaining a protocol negotiation result, and the protocol negotiation result includes a target protocol stack, which is used for transmitting sensing data in the sensing service request. The present disclosure can dynamically adjust the target protocol stack according to different sensing service requests, and can flexibly adapt to diversified sensing and communication requirements.

Description

Technical Field

[0001] This disclosure relates to the field of wireless communication technology, and more specifically, to a method for negotiating a sensing data transmission protocol, an apparatus for negotiating a sensing data transmission protocol, an electronic device, and a computer program product. Background Technology

[0002] Integrated Sensing and Communication (ISAC) is a technology that integrates sensing and communication functions into the same network to enable the sensing and data transmission of the physical world. Sensing control signaling between the Sensing Function (SF), Radio Access Network (RAN), and User Equipment (UE) is transmitted through the Access and Mobility Management function (AMF). Sensing measurement data acquired by the RAN or UE can be forwarded to the SF via the User Plane Function (UPF).

[0003] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this disclosure, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0004] The purpose of this disclosure is to provide a method, apparatus, electronic device, computer-readable storage medium, and computer program product for negotiating a sensing data transmission protocol, thereby overcoming, to at least a certain extent, the problem that the interaction between sensing functions and core network functional entities can only use a fixed protocol, lacks flexibility in the selection and management of the protocol stack, and cannot dynamically adjust the protocol stack, resulting in resource waste and performance bottlenecks.

[0005] Other features and advantages of this disclosure will become apparent from the following detailed description, or may be learned in part by practice of the invention.

[0006] According to a first aspect of this disclosure, a method for negotiating a sensing data transmission protocol is provided, applied to a sensing function. The method includes: negotiating a protocol with an associated functional entity based on a received sensing service request to obtain a protocol negotiation result. The protocol negotiation result includes a target protocol stack, which is used to transmit sensing data in the sensing service request.

[0007] In one exemplary embodiment of this disclosure, the associated functional entity includes a user plane function. The step of negotiating a protocol with the associated functional entity based on the received perception service request to obtain a protocol negotiation result includes: sending a data connection establishment request to the user plane function, the data connection establishment request being used to negotiate a protocol with the user plane function; receiving a data connection establishment response returned by the user plane function and performing data transmission, the data connection establishment response being used to send the protocol negotiation result.

[0008] In one exemplary embodiment of this disclosure, the method further includes: establishing the data connection establishment request, the data connection establishment request being established based on a protocol negotiation request, the protocol negotiation request being established based on the sensing service request sent by the service requester, and the sensing service request being generated based on one or more of the sensing data type, business requirements, and network status.

[0009] In one exemplary embodiment of this disclosure, the data connection establishment request includes one or more of the following fields: request message type, request transaction identifier, request source perception function identifier corresponding to the perception function, target user plane function identifier, perception service type, service quality requirement parameters, and candidate protocol list.

[0010] In one exemplary embodiment of this disclosure, the data connection establishment response includes one or more of the following fields: response message type, response transaction identifier, response status code, the target protocol stack, the transmission parameters corresponding to the target protocol stack, and error information.

[0011] In one exemplary embodiment of this disclosure, the associated functional entity includes a user plane function, and the method further includes: receiving the perception data sent by the user plane function based on the target protocol stack, wherein the perception data is sent to the user plane function by a service requester; processing the perception data to obtain a perception processing result; and sending the perception processing result to the service requester through the user plane function based on the target protocol stack.

[0012] According to a second aspect of this disclosure, a method for negotiating a sensing data transmission protocol is provided, applied to an associated functional entity, comprising: negotiating a protocol with a sensing function based on a received data connection establishment request, and obtaining a protocol negotiation result, wherein the protocol negotiation result includes a target protocol stack, the target protocol stack being used to transmit sensing data in a sensing service request.

[0013] In one exemplary embodiment of this disclosure, the step of negotiating a protocol with the sensing function based on the received data connection establishment request to obtain a protocol negotiation result includes: receiving a data connection establishment request sent by the sensing function, the data connection establishment request being established by the sensing function based on a received sensing service request; sending a data connection establishment response to the sensing function and performing data transmission, the data connection establishment response being used to return the protocol negotiation result.

[0014] In one exemplary embodiment of this disclosure, the method further includes: receiving sensing data sent by a service requester; sending the sensing data to the sensing function based on the target protocol stack, the sensing function being used to process the sensing data to obtain a sensing processing result; receiving the sensing processing result based on the target protocol stack, and sending the sensing processing result to the service requester.

[0015] According to a third aspect of this disclosure, an apparatus for negotiating a sensing data transmission protocol is provided, applied to a sensing function. The apparatus includes a first protocol negotiation module, which is used to negotiate a protocol with an associated functional entity based on a received sensing service request to obtain a protocol negotiation result. The protocol negotiation result includes a target protocol stack, which is used to transmit the sensing data in the sensing service request.

[0016] In one exemplary embodiment of this disclosure, the associated functional entity includes a user plane function, and the first protocol negotiation module includes a first protocol negotiation unit, configured to: send a data connection establishment request to the user plane function, the data connection establishment request being used to negotiate a protocol with the user plane function; receive a data connection establishment response returned by the user plane function, and perform data transmission, the data connection establishment response being used to send the protocol negotiation result.

[0017] In one exemplary embodiment of this disclosure, the first protocol negotiation unit includes a request establishment subunit, configured to: establish the data connection establishment request, the data connection establishment request being established based on the protocol negotiation request, the protocol negotiation request being established based on the sensing service request sent by the service requester, and the sensing service request being generated based on one or more of sensing data types, service requirements, and network status.

[0018] In one exemplary embodiment of this disclosure, the associated functional entity includes a user plane function, and the apparatus for negotiating the perception data transmission protocol further includes a first data transmission module, configured to: receive the perception data sent by the user plane function based on the target protocol stack, wherein the perception data is sent by a service requester to the user plane function; process the perception data to obtain a perception processing result; and send the perception processing result to the service requester through the user plane function based on the target protocol stack.

[0019] According to a fourth aspect of this disclosure, an apparatus for negotiating a sensing data transmission protocol is provided, applied to an associated functional entity. The apparatus includes a second protocol negotiation module, which is used to negotiate a protocol with a sensing function based on a received data connection establishment request, and obtain a protocol negotiation result. The protocol negotiation result includes a target protocol stack, which is used to transmit sensing data in a sensing service request.

[0020] In one exemplary embodiment of this disclosure, the second protocol negotiation module includes a second protocol negotiation unit, configured to: receive a data connection establishment request sent by the sensing function, the data connection establishment request being established by the sensing function based on a received sensing service request; send the data connection establishment response to the sensing function and perform data transmission, the data connection establishment response being used to return the protocol negotiation result.

[0021] In one exemplary embodiment of this disclosure, the apparatus for negotiating the sensing data transmission protocol further includes a second data transmission module, configured to: receive sensing data sent by a service requester; send the sensing data to the sensing function based on the target protocol stack, wherein the sensing function processes the sensing data to obtain a sensing processing result; receive the sensing processing result based on the target protocol stack, and send the sensing processing result to the service requester.

[0022] According to a fifth aspect of this disclosure, an electronic device is provided, comprising: a processor; and a memory storing computer-readable instructions that, when executed by the processor, implement a method for negotiating a sensing data transmission protocol according to any one of the preceding claims.

[0023] According to a sixth aspect of this disclosure, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements a method for negotiating a sensing data transmission protocol according to any one of the preceding claims.

[0024] According to a seventh aspect of this disclosure, a computer program product is provided, comprising a computer program that, when executed by a processor, implements the method for negotiating a perceptual data transmission protocol as described in any one of the preceding claims.

[0025] The technical solution provided in this disclosure may include the following beneficial effects:

[0026] The method for negotiating a sensing data transmission protocol in the exemplary embodiments of this disclosure, on the one hand, dynamically adjusts the target protocol stack according to different sensing service requests, which can flexibly adapt to diverse sensing and communication needs. On the other hand, the collaboration mechanism between the sensing function and the associated functional entities can achieve enhanced coordination between the two, making the protocol negotiation process more efficient.

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

[0028] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort. In the drawings:

[0029] Figure 1 The schematic diagram illustrates the architecture of the sensor fusion network in the relevant scheme;

[0030] Figure 2 The diagram illustrates the user plane protocol stack of the user equipment and sensing functions in the relevant scheme.

[0031] Figure 3 A flowchart illustrating a method for negotiating a sensing data transmission protocol according to an exemplary embodiment of the present disclosure is shown schematically.

[0032] Figure 4 This illustration schematically shows an ISAC sensing data processing flowchart with a protocol negotiation mechanism according to an exemplary embodiment of the present disclosure;

[0033] Figure 5 The illustration schematically depicts the interaction between signaling in a protocol negotiation mechanism according to an exemplary embodiment of the present disclosure;

[0034] Figure 6 A flowchart illustrating a method for negotiating a sense data transmission protocol according to another exemplary embodiment of this disclosure is shown schematically;

[0035] Figure 7The illustration shows a schematic diagram of sensing data transmission in a low-altitude unmanned aerial vehicle ranging scenario according to an exemplary embodiment of the present disclosure;

[0036] Figure 8 The illustration schematically depicts a perception data transmission process in an autonomous driving scenario according to an exemplary embodiment of the present disclosure.

[0037] Figure 9 This schematically illustrates a block diagram of an apparatus for negotiating a sensing data transmission protocol according to an exemplary embodiment of the present disclosure;

[0038] Figure 10 A block diagram schematically illustrates an apparatus for negotiating a sensing data transmission protocol according to another exemplary embodiment of the present disclosure;

[0039] Figure 11 The illustration schematically shows a computer-readable storage medium according to an exemplary embodiment of the present disclosure;

[0040] Figure 12 A block diagram of an electronic device according to an exemplary embodiment of the present disclosure is shown schematically. Detailed Implementation

[0041] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the embodiments set forth herein; rather, they are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the exemplary embodiments to those skilled in the art. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted.

[0042] Furthermore, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to give a thorough understanding of embodiments of this disclosure. However, those skilled in the art will recognize that the technical solutions of this disclosure can be practiced without one or more of the specific details described, or other methods, components, apparatuses, steps, etc., can be employed. In other instances, well-known structures, methods, apparatuses, implementations, materials, or operations are not shown or described in detail to avoid obscuring various aspects of this disclosure.

[0043] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software, or in one or more software-hardened modules, or in different network and / or processor devices and / or microcontroller devices.

[0044] refer to Figure 1 , Figure 1 The schematic diagram illustrates the architecture of the sensor fusion network in the relevant scheme. From Figure 1 As can be seen, the sensing function network element sets up interfaces and interacts with the 5G core network (5GC) network elements such as the Access and Mobility Management function (AMF), the Network Exposure Function (NEF), the Unified Data Management function (UDM), the Network Data Analytics Function (NWDAF), the Policy Control Function (PCF), the Location Management Function (LMF), and the UPF. Figure 1 The architecture is designed to maximize the reuse of existing 5G network functions, interfaces, and protocols.

[0045] refer to Figure 2 , Figure 2 The diagram illustrates the user plane protocol stack of the user equipment and sensing functions in the relevant scheme. Figure 2 In the UE (User Equipment) sensing device, sensing measurement data is acquired. If the sensing demand is made by the UE and used locally, it does not need to report to the network side; otherwise, the sensing measurement data needs to be reported to the SF (Service Provider). Similar to the user plane connection established between the UE and the ProSe network element in Proximity Services (ProSe), the UE can establish a connection between the two based on the SF's Internet Protocol Address (IP address) and carry it through the UE's Protocol Data Unit (PDU) session. That is, the NR Sensing Protocol for the User plane (NRSP-U) is designed as an independent protocol and can be directly carried over existing PDU sessions.

[0046] In future networks, integrated sensing and communication must simultaneously support diverse sensing services (such as ranging, positioning, and imaging) and high-throughput, low-latency communication requirements. In the aforementioned schemes, the interaction between the sensing function (SF) and core network functional entities (such as UPF) typically uses fixed protocols (such as UDP and IP). This lack of flexibility in protocol stack selection and management prevents dynamic adjustment of the protocol stack based on the type of sensing data, Quality of Service (QoS) requirements, and network conditions, leading to resource waste and performance bottlenecks.

[0047] Based on this, according to embodiments of the present disclosure, a method for sensing data transmission protocol negotiation, an apparatus for sensing data transmission protocol negotiation, a computer-readable storage medium, an electronic device, and a computer program product are proposed.

[0048] In this article, it's important to understand that the terminology used, such as User Datagram Protocol (UDP), is a simple, connectionless, unreliable datagram transport layer protocol. Quick UDP Internet Connections (QUIC) is a low-latency transport protocol based on UDP that supports multiplexing and built-in encryption for sensitive data transmission, improving security and efficiency.

[0049] Remote Direct Memory Access (RDMA) is a high-efficiency data transfer technology that allows computers to read or write data directly from each other's memory without CPU intervention. This technology significantly reduces latency and improves data transfer efficiency by bypassing the operating system kernel.

[0050] In this example embodiment, a method for negotiating a sensing data transmission protocol is first provided. This method is applied to a sensing function and can be implemented using a server or a terminal device. The terminal described in this disclosure may include mobile terminals such as mobile phones, tablets, laptops, handheld computers, and personal digital assistants (PDAs), as well as fixed terminals such as desktop computers. Figure 3 The illustration schematically depicts a method flow for negotiating a sense data transmission protocol according to some embodiments of the present disclosure. (Reference) Figure 3 The method for negotiating the sensing data transmission protocol may include the following steps:

[0051] Step S310: Based on the received perception service request, perform protocol negotiation with the associated functional entity to obtain the protocol negotiation result. The protocol negotiation result includes the target protocol stack, which is used to transmit the perception data in the perception service request.

[0052] According to the method for negotiating the sensing data transmission protocol in this example embodiment, on the one hand, the target protocol stack can be dynamically adjusted according to different sensing service requests, which can flexibly adapt to diverse sensing and communication needs. On the other hand, the collaboration mechanism between the sensing function and the associated functional entities can achieve enhanced synergy between the two, making the protocol negotiation process more efficient.

[0053] The method for negotiating the sensing data transmission protocol in this example embodiment will be further explained below.

[0054] For step S310, protocol negotiation is performed with the associated functional entity based on the received perception service request to obtain the protocol negotiation result. The protocol negotiation result includes the target protocol stack, which is used to transmit the perception data in the perception service request.

[0055] According to some exemplary embodiments of this disclosure, the sensing function (SF) can be a functional network element responsible for authorization, control, data processing, and result feedback of sensing services. A sensing service request refers to a message or instruction sent by a user equipment (UE) to a network device or functional entity in a sensing network to request specific sensing data or to perform sensing-related operations. A functional entity (FE) can be various functional nodes in the sensing network, such as user plane functions or access networks (ANs). A user plane function can be a functional network element in the sensing network that undertakes important data forwarding and processing tasks, ensuring accurate data transmission and efficient processing. An associated functional entity can be a functional entity that transmits sensing data with the sensing function; in a sensing network, an associated functional entity can be used to receive sensing service requests sent by a service requester.

[0056] Protocol negotiation can be a process of dynamically selecting the optimal protocol stack between the sensing function (SF) and the functional entity (FE) to meet different sensing and communication needs. The protocol negotiation result can be the protocol stack determined by the sensing function (SF) and the functional entity (FE) after protocol negotiation. The target protocol stack can be the protocol stack used for transmitting and processing sensed data after protocol negotiation between the sensing function (SF) and the functional entity. Sensed data can be data related to the network environment, user behavior, device status, etc., collected through various sensing devices and technologies. Sensed data can be data collected or obtained by the service requester.

[0057] refer to Figure 4 , Figure 4 The diagram illustrates an exemplary embodiment of the ISAC sensing data processing flowchart with a protocol negotiation mechanism according to this disclosure. In different sensing service scenarios, the user equipment (UE) can generate corresponding sensing service requests based on the specific scenario. For example, in a drone ranging scenario, a ranging or tracking sensing service request can be generated; in an autonomous driving scenario, a positioning sensing service request can be generated; and in a security monitoring scenario, a tracking sensing service request can also be generated.

[0058] The UE sends the generated perception service request to the perception function. Figure 4 In this context, the UE can send a perception service request by creating a PDU session. For example, the UE can send a perception service request through the AMF. The UE can first request the AMF to establish a user plane connection, carrying the UE address in the user plane connection request. After receiving the above request, the AMF forwards it to the SF. After receiving the perception service request, the SF returns a response to the UE through the AMF, carrying the SF address in the response.

[0059] Upon receiving a sensing service request, the SF can negotiate a protocol with the associated functional entity, such as the UPF in this disclosure. The SF can send a request to the UPF and then negotiate a protocol with it to determine the negotiation result. After determining the negotiation result, the UPF will send the result back to the SF. The protocol negotiation result determined through the negotiation includes the target protocol stack, which the UPF and SF can then use to transmit the sensing data in the sensing service request.

[0060] In one exemplary embodiment of this disclosure, step S310, which involves negotiating a protocol with an associated functional entity based on the received perception service request to obtain a protocol negotiation result, includes: sending a data connection establishment request to a user plane function, wherein the data connection establishment request is used to negotiate a protocol with the user plane function; receiving a data connection establishment response returned by the user plane function and performing data transmission, wherein the data connection establishment response is used to send the protocol negotiation result.

[0061] The data connection establishment request can be a request signaling used by the sensing function and the user plane function to establish a communication connection for protocol negotiation. The data connection establishment response can be a response signaling generated by the user plane function based on the data connection establishment request, which is used to feed back the protocol negotiation results to the sensing function.

[0062] After receiving a perception service request, SF establishes a data interaction connection with UPF, referring to... Figure 5 , Figure 5The diagram illustrates the interaction between signaling in a protocol negotiation mechanism according to an exemplary embodiment of this disclosure. The SF establishes a data connection establishment request (Nsf_DataConnectionSetup_Request) with the UPF, and negotiates the protocol with the UPF by sending the data connection establishment request to the UPF, thereby obtaining the protocol negotiation result.

[0063] After the SF and UPF complete protocol negotiation and determine the negotiation result, the UPF sends the determined negotiation result to the SF. (Continue to refer to...) Figure 5 , Figure 5 The UPF can send the protocol negotiation result using a data connection establishment response (Nsf_DataConnectionSetup_Response). This response can be signaling corresponding to the data connection establishment request sent by the SF. Therefore, some fields in the response can be determined based on the data connection establishment request, and it includes the target protocol stack determined through protocol negotiation. The UPF can send the target protocol stack, determined through protocol negotiation, to the SF via the data connection establishment response, so that the target protocol stack can be used in subsequent communication networks to transmit the sensing data in the sensing service request. By sending the data connection establishment request, the SF and UPF can negotiate protocols and dynamically adjust the protocol stack used in the sensor network.

[0064] In one exemplary embodiment of this disclosure, a data connection establishment request is established. The data connection establishment request is established based on a protocol negotiation request. The protocol negotiation request is established based on a sensed service request sent by the service requester. The sensed service request is generated based on one or more of the sensed data type, business requirements, and network status.

[0065] Here, a protocol negotiation request can be a request sent by a sensing function when it wants to negotiate a protocol with an associated functional entity. A service requester can be an entity that has a need for sensing services and sends a service request to the sensing network or related systems; for example, a service requester can include, but is not limited to, a user equipment (UE) or a network function. The sensing data type can be the specific type of sensing data included in the current sensing data transmission scenario. Service requirements can be the specific requirements for sensing service communication in the sensing network, and service requirements can include communication requirements and quality of service requirements. Communication requirements can be requirements such as low latency and high throughput for sensing data transmission. Quality of service requirements can refer to the specific requirements of the service requester for the sensing service in terms of performance, reliability, and timeliness. Network status can be the current network status of the sensing network.

[0066] Continue to refer to Figure 4In a sensory network, a User Equipment (UE) or network function can generate sensing service requests based on different sensing data types, service requirements, and network conditions. For example, the sensing data type is determined by different application scenarios, such as data types in ranging, positioning, and tracking scenarios. Service requirements can include, but are not limited to, sensing accuracy and latency, and can also be determined based on QoS requirements. Furthermore, the sensing service request can also consider network conditions, such as whether the current network condition is good, average, or poor. The sensing service request generated by the UE or network function can include the above information.

[0067] After generating a sensing service request, the service requester sends the sensing service request to the SF. Upon receiving the sensing service request, the SF can negotiate a protocol with the relevant functional entity (FE) based on the sensing service request. The associated functional entity can be a UPF. For example, the SF can establish a protocol negotiation request with the UPF based on the sensing service request to conduct subsequent protocol negotiation processes and determine the protocol negotiation result. The specific content of the protocol negotiation between the SF and the UPF can include, but is not limited to, the protocol type and transmission parameters. The protocol type can include, but is not limited to, File Transfer Protocol (FTP), RDMA, QUIC, etc.

[0068] After the SF and UPF complete protocol negotiation, they obtain the negotiation result. The UPF sends the result to the SF, which receives it to transmit the sensed data accordingly. If the SF and UPF use the selected protocol stack (i.e., the target protocol stack) for the transmission and processing of the sensed data, the SF will feed back the processed results to the requesting party. This protocol negotiation mechanism allows the SF and UPF to dynamically select the optimal protocol stack based on the type of sensed data and service requirements, significantly improving the flexibility, transmission efficiency, and adaptability of the sensor network.

[0069] In one exemplary embodiment of this disclosure, the data connection establishment request includes one or more of the following fields: request message type, request transaction identifier, request source perception function identifier corresponding to the perception function, target user plane function identifier, perception service type, service quality requirement parameters, and candidate protocol list.

[0070] The protocol negotiation mechanism between SF and UPF can be implemented based on the data interaction signaling between the two. The data connection establishment request sent by SF to UPF may include, but is not limited to, the fields listed in Table 1. Table 1 shows the field name, field type, field length and field description of different fields.

[0071] Table 1 shows the data format for establishing a data connection.

[0072]

[0073]

[0074] The request message type in Table 1 can be a specific type corresponding to a data connection establishment request, generally fixed as Nsf_DataConnectionSetup_Request. The request transaction identifier can be a unique identifier corresponding to the sensing service request, used to identify the correspondence between the request and response. The request source sensing function identifier can be the ID corresponding to the sensing function (SF) that sent the protocol negotiation request. The sensing service type can be the service type corresponding to the sensing service scenario; the corresponding sensing data type can be determined based on the sensing service type. The target user plane function identifier can be the ID corresponding to the user plane function UPF.

[0075] Service quality requirement parameters can be parameters corresponding to the service quality requirements of sensed data transmission, and may include parameters such as latency and throughput. The candidate protocol list, also known as the protocol preference list, can be a list of preferred protocol stacks for data transmission in the sensor network. Multiple protocols in the candidate protocol list can be sorted according to protocol priority. By defining the data format of the data connection establishment request, the SF can negotiate protocols with the UPF based on interactive signaling containing the above fields, dynamically adjusting the target protocol stack.

[0076] In one exemplary embodiment of this disclosure, the data connection establishment response includes one or more of the following fields: response message type, response transaction identifier, response status code, target protocol stack, transmission parameters corresponding to the target protocol stack, and error information.

[0077] After determining the protocol negotiation result, the UPF can send the protocol negotiation result to the SF based on the data connection establishment response. The data connection establishment response sent by the UPF to the SF may include, but is not limited to, the fields listed in Table 2. Table 2 shows the field name, field type, field length and field description of different fields.

[0078] Table 2 shows the data format for establishing a data connection response.

[0079]

[0080]

[0081] In Table 2, the response message type can be the specific type corresponding to the data connection establishment response, and can generally be fixed as Nsf_DataConnectionSetup_Response. The response transaction identifier can be a unique identifier corresponding to the response signaling used to respond to the sensing service request, and the response transaction identifier corresponds to the Transaction ID in the data connection establishment request. The response status code can be the status code corresponding to the data connection establishment response. The target protocol stack can be the protocol stack that best matches the current sensing service request. The error message can be the information displayed when the response status code indicates failure.

[0082] Through a protocol negotiation mechanism, SF can dynamically select the optimal protocol stack based on different sensing and communication needs, significantly improving the flexibility and adaptability of the sensor network. Furthermore, the protocol negotiation mechanism can select the most suitable protocol stack based on business requirements, optimizing the transmission efficiency of sensed data, reducing latency, improving network resource utilization, and enhancing data security.

[0083] In one exemplary embodiment of this disclosure, the user plane function receives perception data sent by the target protocol stack, and the perception data is sent to the user plane function by the service requester; the perception data is processed to obtain a perception processing result; and the perception processing result is sent to the service requester through the user plane function based on the target protocol stack.

[0084] The perceived data can be the data to be processed contained in the perceived service request. The perceived processing result can be the result obtained after processing the perceived data.

[0085] Continue to refer to Figure 4 The service requester can report sensing data through the UPF. The UPF can then send the sensing data to the SF using the target protocol stack. The SF processes the sensing data and obtains the corresponding sensing processing results. The SF then feeds back the processed sensing results to the service requester via the UPF based on the target protocol stack. This sensing result feedback mechanism enables the sensing data to be used to optimize network performance and improve the overall intelligence level of the network.

[0086] In summary, the method for negotiating a sensing data transmission protocol for sensing functions disclosed herein negotiates a protocol with associated functional entities based on a received sensing service request, resulting in a target protocol stack used to transmit the sensing data in the sensing service request. On one hand, the target protocol stack can be dynamically adjusted according to different sensing service requests, flexibly adapting to diverse sensing and communication needs. On the other hand, the collaborative mechanism between the sensing function and associated functional entities enhances their synergy, making the protocol negotiation process more efficient. Furthermore, by selecting the most suitable protocol stack, the transmission performance of sensing data is optimized, improving the overall network efficiency, and the sensing result feedback mechanism can use the sensing data to optimize network performance, enhancing the overall network intelligence level. Finally, by supporting multiple protocol stacks, the security of sensing data can be protected, preventing data leakage and tampering, and providing flexibility for future network expansion and upgrades.

[0087] In addition, this disclosure also provides a method for negotiating a perceptual data transmission protocol, which is applied to associated functional entities. The perceptual data transmission protocol negotiation method of this disclosure can be implemented using a server or a terminal device. Figure 6 The illustration schematically depicts a method flow for negotiating a sense data transmission protocol according to some embodiments of the present disclosure. (Reference) Figure 6 The method for negotiating the sensing data transmission protocol may include the following steps:

[0088] Step S610: Based on the received data connection establishment request, the sensing function performs protocol negotiation to obtain the protocol negotiation result. The protocol negotiation result includes the target protocol stack, which is used to transmit the sensing data in the sensing service request.

[0089] According to the method for negotiating the sensing data transmission protocol in this example embodiment, on the one hand, the target protocol stack can be dynamically adjusted according to different sensing service requests, which can flexibly adapt to diverse sensing and communication needs. On the other hand, the collaboration mechanism between the sensing function and the associated functional entities can achieve enhanced synergy between the two, making the protocol negotiation process more efficient.

[0090] The method for negotiating the sensing data transmission protocol in this example embodiment will be further explained below.

[0091] Step S610: Based on the received data connection establishment request, the sensing function performs protocol negotiation to obtain the protocol negotiation result. The protocol negotiation result includes the target protocol stack, which is used to transmit the sensing data in the sensing service request.

[0092] According to some exemplary embodiments of this disclosure, the associated functional entity may be a user plane function, and so on. Figure 4 The service requester (such as UE or network function) can generate the corresponding perception service request based on the current business scenario. Taking the UE as the service requester, the UE can create a user plane connection through the AMF request. The connection carries the UE address and sends the perception service request to the SF. The SF returns a response to the corresponding UE based on the received user plane connection. The response carries the SF address.

[0093] Then, the SF establishes a data connection with the UPF based on the sensing service request and sends the data connection establishment request to the UPF. After receiving the data connection establishment request, the UPF negotiates a protocol with the SF and obtains the protocol negotiation result. The protocol negotiation result can include the target protocol stack required for subsequent use in the sensor network, so that the sensing data can be transmitted based on the target protocol stack.

[0094] In one exemplary embodiment of this disclosure, step S610, which involves negotiating a protocol with the sensing function based on the received data connection establishment request to obtain a protocol negotiation result, includes: receiving a data connection establishment request sent by the sensing function, wherein the data connection establishment request is established by the sensing function based on the received sensing service request; sending a data connection establishment response to the sensing function and performing data transmission, wherein the data connection establishment response is used to return the protocol negotiation result.

[0095] Continue to refer to Figure 5 After receiving the perception service request sent by the service requester, the SF establishes a data connection establishment request with the UPF and sends the data connection establishment request to the UPF. The fields included in the data connection establishment request have been described in detail in Table 1, and will not be repeated here.

[0096] After receiving a data connection establishment request, the UPF generates a corresponding data connection establishment response based on the request and returns the protocol negotiation result to the SF through the data connection establishment response. Similarly, the fields included in the data connection establishment response are detailed in Table 2, and will not be repeated here. According to the fields in Table 2, the protocol negotiation result returned by the UPF to the SF includes the target protocol stack. The subsequent sensing network will transmit the sensed data based on the determined target protocol stack.

[0097] In one exemplary embodiment of this disclosure, sensing data sent by a service requester is received; the sensing data is sent to a sensing function based on a target protocol stack, and the sensing function processes the sensing data to obtain a sensing processing result; the sensing processing result is received based on the target protocol stack and then sent to the service requester.

[0098] Continue to refer to Figure 4 After the UE establishes a secure connection with the SF, the UE can report sensing data, such as... Figure 4 In this process, the sensed data is sent to the UPF, which then sends the sensed data to the SF based on the target protocol stack determined through a protocol negotiation mechanism. Upon receiving the sensed data, the SF processes it to obtain the processing result. Then, the SF can also send the processing result back to the UPF based on the target protocol stack, so that the UPF can return the processing result to the service requester, such as the UE, based on the target protocol stack. This sensed result feedback mechanism enables the use of sensed data to optimize network performance and improve the overall intelligence level of the network.

[0099] First, the technical solution disclosed herein introduces a dynamic protocol negotiation mechanism, which allows the sensing function (SF) and the functional entity (FE) to dynamically select the optimal protocol stack based on the type of sensing service request and business requirements.

[0100] In existing sensor networks, the protocol stack is usually fixed and cannot be dynamically adjusted according to different service requirements. For example, in low-altitude UAV ranging scenarios, a fixed protocol stack may not meet the requirements for low latency.

[0101] Compared with existing sensor networks, the advantages of this disclosure are reflected in the following three aspects: (1) Flexibility: It can dynamically select the protocol stack according to different sensing and communication needs, which significantly improves the flexibility of the sensor network. (2) Transmission efficiency: By selecting the most suitable protocol stack, the transmission efficiency of sensing data is optimized, the latency is reduced, and the utilization rate of network resources is improved. (3) Adaptability: It can better adapt to diverse service needs, such as low latency, high throughput, and high precision.

[0102] Secondly, this disclosure enhances the Sensing Function (SF) network element and user plane functions. This disclosure focuses on introducing the Sensing Function (SF) network element and aims to achieve synergistic enhancement between it and user plane functions. The SF network element is not only responsible for the control, data processing, and result sharing of the sensing service, but also deeply participates in the interaction optimization with user plane functions. Through close integration with user plane functions, the SF network element can better support key operations such as protocol negotiation.

[0103] In traditional sensor networks, perception service management and user plane functions are relatively independent and lack a close collaboration mechanism, which leads to limitations in dealing with complex business needs and diverse protocol choices.

[0104] Compared to existing sensor networks, this disclosure can achieve the following beneficial effects: (1) Efficient protocol negotiation support. Enhanced collaboration between SF network elements and user plane functions makes the protocol negotiation process more efficient; SF network elements can jointly determine the optimal protocol stack with user plane functions based on real-time service requirements and network status, ensuring the efficiency and stability of data transmission. (2) Improved flexibility and adaptability. This enhancement enables the network to adapt more flexibly to different sensing and communication scenarios, whether it is ranging tasks with low latency requirements or autonomous driving with high real-time requirements, it can quickly adjust the protocol selection. (3) Enhanced quality of service assurance. Provides users with more stable and reliable quality of service, meeting the specific requirements of accuracy, latency, etc. in different application scenarios.

[0105] Furthermore, this disclosure supports multiple protocol stacks, such as FTP, RDMA, and QUIC, to meet the needs of different sensing and communication scenarios.

[0106] Existing sensor networks typically only support one or a few fixed protocol stacks, which cannot meet diverse business needs.

[0107] Compared with existing sensor networks, this disclosure can achieve the following beneficial effects: (1) Diverse support: It supports multiple protocol stacks, which can meet the service needs of different sensing and communication scenarios, such as low latency, high throughput, and encrypted transmission. (2) Optimized performance: By selecting the most suitable protocol stack, the transmission performance of sensing data is optimized, and the overall efficiency of the network is improved. (3) Scalability: It supports multiple protocol stacks, providing flexibility for future network expansion and upgrades.

[0108] This disclosure applies to various scenarios in ISAC networks, including but not limited to low-altitude UAV ranging, vehicle tracking, and intelligent transportation. In such scenarios, the UE sends a perception service request to the SF, the SF negotiates a protocol with the UPF, and transmits perception data through the UPF based on the negotiation result. The SF processes the perception data and feeds the processing result back to the UE for use in optimizing core network performance. The following will describe in detail the method of perception data transmission protocol negotiation in this disclosure using low-altitude UAV ranging and autonomous driving scenarios.

[0109] refer to Figure 7 , Figure 7 This illustration schematically depicts a sensing data transmission process in a low-altitude unmanned aerial vehicle (UAV) ranging scenario according to an exemplary embodiment of the present disclosure. Figure 7 In low-altitude UAV ranging scenarios, low-altitude UAVs need to perform real-time ranging to ensure flight safety, requiring low latency and high accuracy for the ranging service. Based on the aforementioned method for negotiating the sensing data transmission protocol, the technical solution for low-altitude UAV ranging scenarios includes the following implementation steps:

[0110] (1) Generate a perception service request. Executing entity: UE (UAV); Triggering condition: The UAV initiates a ranging task; Processing action: The UE sends a ranging request to the SF, which includes ranging accuracy and latency requirements. Result: The SF receives the request.

[0111] (2) Protocol negotiation process. Executing entity: SF; Triggering condition: SF receives a ranging request; Processing action: SF and UPF negotiate the protocol, ultimately selecting the RDMA protocol stack for low-latency data transmission. Result: The negotiation result is the use of the RDMA protocol stack.

[0112] (3) Sensing data transmission. Execution entity: UPF; Triggering condition: Protocol negotiation completed; Processing action: UPF transmits ranging data to SF via the RDMA protocol stack. Result: SF receives the ranging data.

[0113] (4) Perception Result Feedback. Executor: SF; Triggering Condition: SF completes ranging data processing; Processing Action: SF feeds back the ranging result to UE and uses the data to optimize network performance. Result: UE receives the ranging result, and network performance is optimized. Specifically, SF can send the UAV ranging perception processing result to UPF, and UPF returns the perception processing result to UE.

[0114] By employing a protocol negotiation mechanism to dynamically adjust the target protocol stack in low-altitude UAV ranging scenarios, the RDMA protocol stack can be dynamically adjusted for low-latency data transmission, resulting in the following benefits: Low-latency transmission, such as significantly reducing the latency of ranging data transmission through the RDMA protocol stack; High-precision ranging, ensuring high accuracy of UAV ranging and improving flight safety through data transmission processing using the RDMA protocol stack; and the ability to optimize network resource allocation and improve overall network performance using the perceived data.

[0115] This disclosure also provides a specific implementation process for an autonomous driving scenario, referencing... Figure 8 , Figure 8 This diagram schematically illustrates perception data transmission in an autonomous driving scenario according to an exemplary embodiment of the present disclosure. Figure 8 In autonomous driving scenarios, vehicles need to perceive their own state and surrounding environment in real time, including positioning, speed measurement, and distance measurement, to achieve safe and efficient driving. The technical solutions for autonomous driving scenarios include the following implementation steps:

[0116] (1) Autonomous Driving Perception Request. Executor: Vehicle (UE); Triggering Condition: Autonomous driving system starts; Processing Action: The vehicle sends a perception request to the SF, including specific requirements such as positioning accuracy, speed range, and distance measurement accuracy. Result: The SF receives the request and initiates the perception service process.

[0117] (2) Protocol Negotiation Process. Executing Entity: SF; Triggering Condition: SF receives a sensing request; Processing Action: SF negotiates the protocol with UPF to select the most suitable protocol stack, such as the QUIC protocol stack, to meet the requirements of low latency and high reliability. Result: The protocol stack used is determined, ensuring the quality of data transmission.

[0118] (3) Sensing data transmission. Executor: UPF; Triggering condition: Protocol negotiation completed; Processing action: UPF transmits the sensing data to SF through the selected protocol stack. Result: SF successfully receives the sensing measurement data.

[0119] (4) Perception Result Feedback. Execution Entity: SF; Triggering Condition: SF completes processing of perception data; Processing Action: SF feeds back the result to the requester and uses the data to optimize network performance. Result: The vehicle obtains the result, and network performance is optimized. Specifically, SF can send the perception processing result of autonomous driving to UPF, and UPF returns the perception processing result to UE.

[0120] In autonomous driving scenarios, the QUIC protocol stack can be dynamically adjusted for encrypted transmission and low latency, achieving the following beneficial effects: High-precision tracking; the QUIC protocol stack ensures high precision, real-time performance, and safety for autonomous driving. Data security; the encryption mechanism of the QUIC protocol stack protects the security of perception data and safeguards vehicle privacy; furthermore, perception data is used to optimize network resource allocation and improve overall network performance.

[0121] The target protocol stack used in vehicle autonomous driving scenarios and the low-altitude drone ranging scenarios use different protocol stacks for data transmission, achieving different beneficial effects. For example, autonomous driving scenarios focus more on data security, real-time performance, and privacy.

[0122] In conjunction with the above embodiments, the technical solution disclosed herein has the following beneficial effects: Through the protocol negotiation mechanism, the optimal protocol stack can be dynamically selected according to different sensing and communication needs, significantly improving the flexibility of the sensor network. The protocol negotiation mechanism can select the most suitable protocol stack according to business requirements, optimizing the transmission efficiency of sensing data, reducing latency, and improving network resource utilization. It supports the use of encryption protocols (such as QUIC) to protect the security of sensing data and prevent data leakage and tampering.

[0123] It should be noted that although the steps of the method in this invention are described in a specific order in the accompanying drawings, this does not require or imply that the steps must be performed in that specific order, or that all the steps shown must be performed to achieve the desired result. Additional or alternative steps may be omitted, multiple steps may be combined into one step, and / or one step may be broken down into multiple steps.

[0124] Furthermore, in this exemplary embodiment, an apparatus for negotiating a sensing data transmission protocol is also provided, which is applied to a sensing function. (See reference...) Figure 9 The sensing data transmission protocol negotiation device 900 may include a first protocol negotiation module 910.

[0125] Specifically, the first protocol negotiation module 910 is used to negotiate the protocol with the associated functional entity based on the received perception service request to obtain the protocol negotiation result. The protocol negotiation result includes the target protocol stack, which is used to transmit the perception data in the perception service request.

[0126] In one exemplary embodiment of this disclosure, the associated functional entity includes a user plane function, and the first protocol negotiation module includes a first protocol negotiation unit, configured to: send a data connection establishment request to the user plane function, the data connection establishment request being used to negotiate a protocol with the user plane function; receive a data connection establishment response returned by the user plane function, and perform data transmission, the data connection establishment response being used to send the protocol negotiation result.

[0127] In one exemplary embodiment of this disclosure, the first protocol negotiation unit includes a request establishment subunit, configured to: establish a data connection establishment request, wherein the data connection establishment request is established based on a protocol negotiation request, the protocol negotiation request is established based on a sensed service request sent by a service requester, and the sensed service request is generated based on one or more of the sensed data type, service requirements, and network status.

[0128] In one exemplary embodiment of this disclosure, the associated functional entity includes a user plane function, and the apparatus for negotiating the sensing data transmission protocol further includes a first data transmission module, configured to: receive sensing data sent by the user plane function based on a target protocol stack, wherein the sensing data is sent from the service requester to the user plane function; process the sensing data to obtain a sensing processing result; and send the sensing processing result to the service requester through the user plane function based on the target protocol stack.

[0129] Furthermore, in this example embodiment, an apparatus for sensing data transmission protocol negotiation is also provided, which is applied to associated functional entities. (See reference...) Figure 10 The sensing data transmission protocol negotiation device 1000 may include a second protocol negotiation module 1010.

[0130] Specifically, the second protocol negotiation module 1010 is used to negotiate the protocol with the sensing function based on the received data connection establishment request and obtain the protocol negotiation result. The protocol negotiation result includes the target protocol stack, which is used to transmit the sensing data in the sensing service request.

[0131] In one exemplary embodiment of this disclosure, the second protocol negotiation module 1010 includes a second protocol negotiation unit, configured to: receive a data connection establishment request sent by the sensing function, the data connection establishment request being established by the sensing function based on a received sensing service request; send a data connection establishment response to the sensing function and perform data transmission, the data connection establishment response being used to return a protocol negotiation result.

[0132] In one exemplary embodiment of this disclosure, the sensing data transmission protocol negotiation apparatus 1000 further includes a second data transmission module, configured to: receive sensing data sent by a service requester; send the sensing data to a sensing function based on a target protocol stack, wherein the sensing function processes the sensing data to obtain a sensing processing result; receive the sensing processing result based on the target protocol stack, and send the sensing processing result to the service requester.

[0133] The specific details of the virtual modules of the devices for negotiating the sensing data transmission protocols mentioned above have been described in detail in the corresponding methods for negotiating sensing data transmission protocols. For any undisclosed details, please refer to the implementation methods in the method section, and therefore will not be repeated here.

[0134] It should be noted that although several modules or units of the apparatus for sensing data transmission protocol negotiation have been mentioned in the detailed description above, this division is not mandatory. In fact, according to embodiments of this disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0135] Furthermore, in an exemplary embodiment of this disclosure, an electronic device capable of implementing the above-described method is also provided.

[0136] Those skilled in the art will understand that various aspects of this disclosure can be implemented as a system, method, or program product. Therefore, various aspects of this disclosure can be embodied in the following forms: a completely hardware embodiment, a completely software embodiment (including firmware, microcode, etc.), or an embodiment combining hardware and software aspects, collectively referred to herein as a "circuit," "module," or "system."

[0137] An exemplary embodiment of this disclosure also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the aforementioned method for negotiating a sense data transmission protocol.

[0138] In one implementation, the computer program product may be a tangible product containing a computer program, such as a computer-readable storage medium storing the computer program. (See reference...) Figure 11 , Figure 11 The schematic diagram illustrates a computer-readable storage medium 1100 according to an exemplary embodiment of the present disclosure. The computer-readable storage medium 1100 can be a storage medium based on electrical, magnetic, optical, electromagnetic, infrared, or other signals, including but not limited to: random access memory (RAM), read-only memory (ROM), magnetic tape, floppy disk, flash memory, hard disk drive (HDD), solid-state drive (SSD), etc. Exemplarily, a computer program product can be implemented as a non-volatile storage medium storing a computer program, such as read-only memory, NAND flash memory, etc.

[0139] In one implementation, the computer program product can be an intangible product containing a computer program. For example, the computer program product can be implemented as a virtual digital product, such as an executable file, installation package, or other digital file storing the computer program.

[0140] Computer program code can be written in one or more programming languages. Examples of programming languages ​​include C, Java, and C++. Program code can execute entirely on the user's computing device, partially on the user's computing device, or as a standalone software package. It can also execute partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, such as a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via an internet connection provided by a mobile network operator).

[0141] Computer programs can be carried or transmitted via signals such as electrical, magnetic, optical, electromagnetic, and infrared rays. Electronic devices can convert the signals carrying computer programs into digital signals, thereby running the computer programs. When a computer program runs on an electronic device, its code is used to cause the electronic device to execute (more specifically, the processor of the electronic device to execute) the method steps of various exemplary embodiments of this disclosure, such as the method for negotiating the sensing data transmission protocol described above.

[0142] Exemplary embodiments of this disclosure also provide an electronic device, which may include a processor and a memory. The memory stores executable instructions of the processor, such as a computer program. The processor executes the executable instructions to perform the method steps of various exemplary embodiments of this disclosure. Furthermore, the electronic device may also include a display for displaying a graphical user interface.

[0143] The following is for reference. Figure 12 The electronic device is illustrated by way of a general-purpose computing device. It should be understood that... Figure 12The electronic device 1200 shown is merely an example and should not be construed as limiting the functionality and scope of use of the embodiments disclosed herein.

[0144] like Figure 12 As shown, the electronic device 1200 may include: a processor 1210, a memory 1220, a bus 1230, an I / O (input / output) interface 1240, a network adapter 1250, and a display 1260.

[0145] Memory 1220 may include volatile memory, such as RAM 1221 and cache unit 1222, and may also include non-volatile memory, such as ROM 1223. Memory 1220 may also include one or more program modules 1224, such program modules 1224 including, but not limited to: operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include an implementation of a network environment. For example, program module 1224 may include the modules in the above-described apparatus.

[0146] The processor 1210 may include one or more processing units, such as an AP (Application Processor), a modem processor, a GPU (Graphics Processing Unit), an ISP (Image Signal Processor), a controller, an encoder, a decoder, a DSP (Digital Signal Processor), a baseband processor, and / or an NPU (Neural-Network Processing Unit).

[0147] The processor 1210 can be used to execute executable instructions stored in the memory 1220, such as the method described above for negotiating the perceptual data transmission protocol.

[0148] Bus 1230 is used to connect different components of electronic device 1200, and may include data bus, address bus and control bus.

[0149] Electronic device 1200 can communicate with one or more external devices 1300 (e.g., keyboard, mouse, external controller, etc.) through I / O interface 1240.

[0150] Electronic device 1200 can communicate with one or more networks via network adapter 1250. For example, network adapter 1250 can provide mobile communication solutions such as 3G / 4G / 5G, or wireless communication solutions such as wireless LAN, Bluetooth, and near-field communication. Network adapter 1250 can communicate with other modules of electronic device 1200 via bus 1230.

[0151] The electronic device 1200 can display a graphical user interface, such as an interface that displays the results of sensor data processing, through the display 1260.

[0152] although Figure 12 As not shown in the diagram, other hardware and / or software modules may also be configured in the electronic device 1200, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0153] As can be seen from the above, the technical solutions disclosed herein can be implemented as methods, apparatus, systems, computer program products, storage media, electronic devices, etc. Those skilled in the art will understand that various aspects of this disclosure can be specifically implemented in the following forms: a completely hardware implementation, a completely software implementation (including firmware, microcode, etc.), or a combination of hardware and software implementations, which may be referred to as "circuit," "module," or "system," respectively.

[0154] It should be understood that this disclosure is not limited to the specific methods, steps, or structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. Those skilled in the art will readily conceive of other embodiments based on the specific implementations provided in this disclosure. Therefore, the specific implementations provided in this disclosure are merely exemplary, and the scope and spirit of this disclosure are indicated by the claims, and should cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary technical means in the art not disclosed in this disclosure.

Claims

1. A method for negotiating a sensing data transmission protocol, characterized in that, Applied to sensing functions, the method includes: Based on the received perception service request, a protocol negotiation is performed with the associated functional entity to obtain a protocol negotiation result. The protocol negotiation result includes a target protocol stack, which is used to transmit the perception data in the perception service request.

2. The method according to claim 1, characterized in that, The associated functional entities include user plane functions. The process of negotiating a protocol between the perception service request and the associated functional entities to obtain the protocol negotiation result includes: Send a data connection establishment request to the user plane function, the data connection establishment request being used to negotiate a protocol with the user plane function; The system receives a data connection establishment response returned by the user plane function and performs data transmission. The data connection establishment response is used to send the protocol negotiation result.

3. The method according to claim 2, characterized in that, The method further includes: The data connection establishment request is established based on a protocol negotiation request, which is based on the sensing service request sent by the service requester. The sensing service request is generated based on one or more of the sensing data type, business requirements, and network status.

4. The method according to claim 2 or 3, characterized in that, The data connection establishment request includes one or more of the following fields: request message type, request transaction identifier, request source perception function identifier corresponding to the perception function, target user plane function identifier, perception service type, service quality requirement parameters, and candidate protocol list.

5. The method according to claim 2, characterized in that, The data connection establishment response includes one or more of the following fields: response message type, response transaction identifier, response status code, target protocol stack, transmission parameters corresponding to the target protocol stack, and error information.

6. The method according to claim 1, characterized in that, The associated functional entities include user plane functions, and the method further includes: The user plane function receives the perception data sent by the user plane function based on the target protocol stack, and the perception data is sent to the user plane function by the service requester; The sensed data is processed to obtain the sensed processing result; Based on the target protocol stack, the perception processing result is sent to the service requester through the user plane function.

7. A method for negotiating a sensing data transmission protocol, characterized in that, Applied to associated functional entities, including: Based on the received data connection establishment request, the sensing function performs protocol negotiation to obtain the protocol negotiation result, which includes a target protocol stack, and the target protocol stack is used to transmit the sensing data in the sensing service request.

8. The method according to claim 7, characterized in that, The step of negotiating a protocol with the sensing function based on the received data connection establishment request to obtain the protocol negotiation result includes: The sensing function receives a data connection establishment request, which is established by the sensing function based on the received sensing service request. The system sends a data connection establishment response to the sensing function and performs data transmission. The data connection establishment response is used to return the protocol negotiation result.

9. The method according to claim 7, characterized in that, The method further includes: Receive sensing data sent by the service requester; The sensing data is sent to the sensing function based on the target protocol stack, and the sensing function is used to process the sensing data to obtain the sensing processing result; The perception processing result is received based on the target protocol stack, and the perception processing result is sent to the service requester.

10. An apparatus for sensing data transmission protocol negotiation, characterized in that, The device, used for sensing functions, includes a first protocol negotiation module. The first protocol negotiation module is used to negotiate the protocol with the associated functional entity based on the received perception service request to obtain the protocol negotiation result. The protocol negotiation result includes a target protocol stack, which is used to transmit the perception data in the perception service request.

11. An apparatus for sensing data transmission protocol negotiation, characterized in that, Applied to associated functional entities, the device includes a second protocol negotiation module. The second protocol negotiation module is used to negotiate the protocol with the sensing function based on the received data connection establishment request and obtain the protocol negotiation result. The protocol negotiation result includes a target protocol stack, which is used to transmit the sensing data in the sensing service request.

12. An electronic device, characterized in that, include: processor; Memory used to store the processor's executable instructions; The processor is configured to execute the instructions to implement the method for negotiating a perceptual data transmission protocol as described in any one of claims 1 to 9.

13. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the method for negotiating the perceptual data transmission protocol as described in any one of claims 1 to 9.

Images