Communication method, apparatus, computer readable storage medium and program product

Abstract

Embodiments of the present disclosure provide a communication method, apparatus, computer readable storage medium and computer program product. In the method, a first network element receives a first request message for requesting a sensing service from a sensing service consumer. Based on receiving the first request message, the first network element determines quality of service (QoS) information corresponding to the sensing service. Then, the first network element sends a second request message for requesting the second network element or a terminal device to perform at least one of execution or transmission of the sensing service. Based on the request message, the second network element can determine a priority associated with the sensing service. In this way, in the case of resource limitation, the second network element can reasonably schedule the two services by comparing the priorities of the communication service and the sensing service, thereby meeting the needs of users.

Description

Technical Field

[0001] This disclosure generally relates to the field of communications, and more specifically to a communication method, apparatus, computer-readable storage medium, and computer program product. Background Technology

[0002] With the rapid development of 5G networks, their application scenarios have expanded from traditional mobile broadband communication to emerging fields such as smart cities, autonomous driving, and the industrial internet. These scenarios place higher demands on networks, requiring not only high-speed, low-latency communication capabilities but also environmental awareness capabilities, such as real-time acquisition of object location, speed, and distance information. To meet these needs, the integration of communication and sensing functions has become crucial, which can not only improve resource utilization efficiency but also reduce deployment costs. However, communication and sensing have different resource requirements and may even conflict. Therefore, achieving a good balance between their performance has become a critical issue that urgently needs to be addressed. Summary of the Invention

[0003] Embodiments of this disclosure provide a communication method, apparatus, system, computer-readable storage medium, and computer program product that enable the rational scheduling of sensing services and communication services under resource constraints, thereby meeting the needs of users in different scenarios.

[0004] Firstly, a communication method is provided. The implementing entity of the method provided in the first aspect can be a first network element, which can be, for example, a Sensing Function (SF). Unless otherwise specified, the first network element in this disclosure can refer to the first network element itself, a component within the first network element (e.g., a processor, chip, or chip system), or a logical module or software capable of implementing all or part of the functions of the first network element. The following example uses the first network element itself. In some implementations, the first network element receives a first request message from a sensing service consumer to request a sensing service. For example, the sensing service consumer can be a UE or an application function (AF). In some implementations, the first request message may include the identifier of the sensing service, the type of the sensing service, and the requirements of the sensing service. Based on the received first request message, the first network element determines the Quality of Service (QoS) information corresponding to the sensing service. For example, the QoS information corresponding to the sensing service may include a 5G Quality of Service Identifier (5QI) associated with the sensing service, a priority level, an Allocation and Reservation Priority (ARP), QoS rules, and a Quality of Service Flow Identifier (QFI). Then, the first network element sends a second request message to the second network element (e.g., a Radio Access Network (RAN) node) or the terminal device (e.g., User Equipment (UE)). The second request message requests the second network element or the terminal device to perform at least one of the following: execution or transmission of a sensing service. In this way, the second network element or the UE can flexibly schedule sensing services according to network conditions and needs, thereby improving resource utilization efficiency and service execution effectiveness.

[0005] In some implementations, after receiving the first request message, the first network element can send a request message to the Policy Control Function (PCF) to obtain the subscription data corresponding to the perceived service. This subscription data can be used to determine the QoS information corresponding to the perceived service.

[0006] In some implementations, the second request message may include the QoS information and the requirements of the sensing service, such as the accuracy, latency, and region of the sensing service. In this way, the second network element or UE can determine the first QoS information corresponding to the execution of the sensing service and / or the second QoS information corresponding to the transmission of the sensing service based on the second request message, so as to further determine the priority of the execution and / or transmission of the sensing service, ensuring that high-priority services obtain the required resources first, thereby meeting the user needs in different scenarios.

[0007] Alternatively, in some implementations, the first network element can determine at least one of first QoS information or second QoS information based on receiving the first request message. In these implementations, the second request message may include at least one of the first QoS information or second QoS information. In this way, the second network element or UE can directly determine the priority of the execution and / or transmission of sensed services based on the first QoS information and / or the second QoS information, reducing the additional decision-making logic on the second network element or UE side and lowering the complexity of network implementation.

[0008] In some implementations, when communication services take precedence over sensing services, or when a sensing service being executed is preempted by a communication service, the first network element can receive a notification message from the second network element indicating that the sensing service has failed. In these implementations, the notification message may include an identifier of the unexecuted or preempted sensing service, or a reason value indicating the sensing service failure. In this way, notification and feedback on sensing service failures can be achieved, enabling timely identification and handling of service failures, thereby optimizing the utilization of network resources.

[0009] Secondly, a communication method is provided. The execution entity of the method provided in the second aspect can be a second network element, such as a RAN node. Unless otherwise specified, the second network element in this disclosure can refer to the second network element itself, a component within the second network element (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the second network element. Here, we take the case where the second network element is the second network element itself as an example. In some implementations, the second network element receives a request message for requesting at least one of the execution or transmission of a sensing service. This request message can be a second request message as described in the method of the first aspect, or it can be a request message as described in the third aspect below. Based on this request message, the second network element determines the priority associated with the sensing service. In this way, under resource constraints, the second network element can reasonably schedule the two services by comparing their priorities, thereby meeting the user's needs.

[0010] In some implementations, the request message may include QoS information corresponding to the sensing service, as well as the requirements of the sensing service, such as the accuracy, latency, and region of the sensing service. As described in the first aspect, the QoS information corresponding to the sensing service may include 5QI, priority level, ARP, QoS rules, and QFI associated with the sensing service. In these implementations, the second network element may determine, based on the request message, first QoS information corresponding to the execution of the sensing service and / or second QoS information corresponding to the transmission of the sensing service. Alternatively, in some implementations, the request message may include at least one of the first QoS information or the second QoS information. In these implementations, the first QoS information and / or the second QoS information may be determined, for example, by the first network element (e.g., SF) in the first aspect, or by the third network element (e.g., Session Management Function (SMF)) in the third aspect. In some implementations, when determining the priority associated with the sensing service, the second network element may determine a first priority for the execution of the sensing service based on the first QoS information, or a second priority for the transmission of the sensing service based on the second QoS information. In this way, the second network element can flexibly determine the priority of sensing service execution and transmission based on request messages, ensuring that sensing services are executed and transmitted efficiently and accurately as required.

[0011] In some implementations, the second network element can determine whether to execute and / or transmit the sensing service based on a first priority, a second priority, and a third priority for communication services. Alternatively, in some implementations, the second network element can first determine whether to execute the sensing service based on the first and third priorities. If it is determined that the sensing service should be executed, the second network element can then determine whether to transmit the sensing service based on the second and third priorities. In this way, the second network element can comprehensively consider the priorities of sensing services and communication services, flexibly decide whether to execute and / or transmit the sensing service, ensure efficient resource allocation, and meet service requirements and system performance requirements.

[0012] In some implementations, based on the determination to execute a communication service, the second network element can send a first notification message about the perceived service failure to the first network element. This first notification message may include an identifier of the unexecuted or preempted perceived service, or a reason value indicating the failure. In other implementations, based on the determination to execute or transmit a perceived service, the second network element can send a second notification message about the communication service failure to the third network element. This second notification message may include an identifier of the unexecuted or preempted communication service, or a reason value indicating the failure. In this way, notification and feedback on perceived service or communication service failures can be achieved, enabling timely identification and handling of service failures, thereby optimizing the utilization of network resources.

[0013] Thirdly, a communication method is provided. The execution entity of the method provided in the third aspect can be a third network element, which can be, for example, a Session Management Function (SMF). Unless otherwise specified, the third network element in this disclosure can refer to the third network element itself, a component within the third network element (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the functions of the third network element. The following example uses the third network element itself. In some implementations, the third network element receives QoS information corresponding to the sensing service. As described in the first and second aspects, the QoS information corresponding to the sensing service may include 5QI, priority level, ARP, QoS rules, and QFI associated with the sensing service. Based on the received QoS information, the third network element then sends a request message to a second network element (e.g., a RAN node) or a UE. This request message requests the second network element or terminal device to perform at least one of the following: execution or transmission of the sensing service. In this way, the second network element or UE can flexibly schedule the sensing service according to network status and requirements, thereby improving resource utilization efficiency and service execution effectiveness.

[0014] In some implementations, the request message may include the QoS information and the requirements of the sensing service, such as the accuracy, latency, and region of the sensing service. In this way, the second network element or UE can determine the first QoS information corresponding to the execution of the sensing service and / or the second QoS information corresponding to the transmission of the sensing service based on the request message, so as to further determine the priority of the execution and / or transmission of the sensing service, ensuring that high-priority services obtain the required resources first, thereby meeting the user needs in different scenarios.

[0015] Alternatively, in some implementations, the third network element can determine at least one of the first QoS information or the second QoS information based on the received QoS information. In these implementations, the request message may include at least one of the first QoS information or the second QoS information. In this way, the second network element or the UE can directly determine the priority of the execution and / or transmission of the sensed service based on the first QoS information and / or the second QoS information, reducing the additional decision-making logic on the second network element or UE side and reducing the complexity of network implementation.

[0016] In some implementations, when a sensing service takes precedence over a communication service, or when a communication service being executed is preempted by a sensing service, the third network element can receive a notification message from the second network element indicating a communication service failure. In these implementations, the notification message may include an identifier of the unexecuted or preempted communication service, or a reason value for the communication service failure. In this way, notification and feedback of communication service failures can be achieved, enabling timely identification and handling of service failures, thereby optimizing the utilization of network resources.

[0017] Fourthly, a communication method is provided. The execution entity of the method provided in the fourth aspect can be a terminal device (e.g., a UE). Unless otherwise specified, the terminal device in this disclosure can refer to the terminal device itself, a component within the terminal device (e.g., a processor, chip, or chip system), or a logic module or software capable of implementing all or part of the terminal device's functions. Here, we take the case where the terminal device is the terminal device itself as an example. In some implementations, the terminal device receives a request message for requesting at least one of the execution or transmission of a sensing service. This request message can be a second request message as described in the method of the first aspect, or a request message as described in the third aspect. Based on this request message, the terminal device determines the priority associated with the sensing service. In this way, under resource constraints, the terminal device can reasonably schedule the two services by comparing their priorities, thereby meeting the user's needs.

[0018] In some implementations, the request message may include QoS information corresponding to the sensing service, as well as the requirements of the sensing service, such as the accuracy, latency, and region of the sensing service. As described in the first to third aspects, the QoS information corresponding to the sensing service may include 5QI, priority level, ARP, QoS rules, and QFI associated with the sensing service. In these implementations, the terminal device may determine first QoS information corresponding to the execution of the sensing service and / or second QoS information corresponding to the transmission of the sensing service based on the request message. Alternatively, in some implementations, the request message may include at least one of the first QoS information or the second QoS information. In these implementations, the first QoS information and / or the second QoS information may be determined, for example, by a first network element (e.g., SF) in the first aspect, or by a third network element (e.g., SMF) in the third aspect. In some implementations, when determining the priority associated with the sensing service, the terminal device may determine a first priority for the execution of the sensing service based on the first QoS information, or may determine a second priority for the transmission of the sensing service based on the second QoS information. In this way, terminal devices can flexibly determine the priority of sensing service execution and transmission based on request messages, ensuring that sensing services are executed and transmitted efficiently and accurately as needed.

[0019] In some implementations, the terminal device can determine whether to execute and / or transmit a sensing service based on a first priority, a second priority, and a third priority for communication services. Alternatively, in some implementations, the terminal device can first determine whether to execute the sensing service based on the first and third priorities. If it is determined that the sensing service should be executed, the terminal device can then determine whether to transmit the sensing service based on the second and third priorities. In this way, the terminal device can comprehensively consider the priorities of sensing services and communication services, flexibly decide whether to execute and / or transmit the sensing service, ensure efficient resource allocation, and meet service requirements and system performance requirements.

[0020] Fifthly, a communication device is provided. This communication device has the function of implementing the behaviors described in the method examples of the first, second, third, or fourth aspects above. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the aforementioned functions. The descriptions of the first network element of the first aspect, the second network element of the second aspect, the third network element of the third aspect, or the terminal device of the fourth aspect also apply to the communication device of the fifth aspect; that is, the communication device of the fifth aspect can refer to the communication device itself, or to components within the communication device (e.g., processor, chip, or chip system), or it can be a logic module or software capable of implementing all or part of the functions of the communication device. In one possible design, the communication device includes a unit that executes the methods of the first, second, third, or fourth aspects, or their implementations. The beneficial effects of implementing the communication device of the fifth aspect can be found in the descriptions of the first, second, third, or fourth aspects, and will not be repeated here.

[0021] A sixth aspect provides an apparatus comprising a processor and a memory storing a computer program or instructions. When executed by the processor, the computer program or instructions cause the apparatus to perform any method according to the first, second, third, or fourth aspect and its implementations.

[0022] In a seventh aspect, a computer-readable storage medium is provided, which stores a computer program or instructions that, when executed by an electronic device, cause the electronic device to perform the methods performed by the apparatus in the above aspects.

[0023] Eighthly, a computer program or computer program product is provided, the computer program or computer program product including computer program instructions, which, when executed by an electronic device, cause the electronic device to perform the methods performed by the apparatus in the above aspects.

[0024] Ninthly, embodiments of this disclosure provide a chip system including a processor for implementing the functions of the means in the methods of the above aspects. In one possible design, the chip system further includes a memory for storing computer programs or instructions and / or data. The chip system may include a chip, and may further include other discrete devices.

[0025] In a tenth aspect, embodiments of this disclosure also provide a communication system, which includes a first network element for performing the first aspect, a second network element for performing the second aspect, a third network element for performing the third aspect, or a terminal device for performing the fourth aspect. Attached Figure Description

[0026] Figure 1A A schematic diagram of a communication system according to some embodiments of the present disclosure is shown.

[0027] Figure 1B A schematic diagram of a 5G network architecture based on a service-oriented architecture is shown.

[0028] Figure 1C A schematic diagram of a 5G network architecture based on a point-to-point interface is shown.

[0029] Figure 1D and Figure 1E Two methods for deploying sensing functions in the core network are shown.

[0030] Figure 2A A schematic diagram of the communication flow of some embodiments of this disclosure is shown.

[0031] Figure 2B A schematic diagram of the communication flow of some embodiments of this disclosure is shown.

[0032] Figure 3A A schematic diagram illustrating the independent configuration of communication and sensing quality of service parameters according to some embodiments of this disclosure is shown.

[0033] Figure 3B A schematic diagram illustrating the joint configuration of communication and sensing service quality parameters according to some embodiments of this disclosure is shown.

[0034] Figure 4 Exemplary communication flows of some embodiments of this disclosure are shown.

[0035] Figure 5 Exemplary communication flows of some embodiments of this disclosure are shown.

[0036] Figure 6 Exemplary communication flows of some embodiments of this disclosure are shown.

[0037] Figure 7 Exemplary communication flows of some embodiments of this disclosure are shown.

[0038] Figure 8 Exemplary communication flows of some embodiments of this disclosure are shown.

[0039] Figure 9 A schematic flowchart illustrating some embodiments of this disclosure implemented at a first network element is shown.

[0040] Figure 10 A schematic flowchart illustrating the implementation of some embodiments of this disclosure at a second network element is shown.

[0041] Figure 11 A schematic flowchart illustrating the implementation of some embodiments of this disclosure at a third network element is shown.

[0042] Figure 12 A schematic flowchart illustrating the implementation of some embodiments of this disclosure at a terminal device is shown.

[0043] Figure 13 This is a block diagram of a device that can be used to implement some embodiments of this application.

[0044] Figure 14 This is a schematic diagram of the structure of an apparatus according to some embodiments of this application.

[0045] Figure 15 This is a schematic diagram of the structure of an apparatus according to some embodiments of this application.

[0046] Figure 16 This is a schematic diagram of the structure of an apparatus according to some embodiments of this application.

[0047] Figure 17 This is a schematic diagram of the structure of an apparatus according to some embodiments of this application. Detailed Implementation

[0048] Embodiments of this disclosure will now be described in more detail with reference to the accompanying drawings. While some embodiments of this disclosure are shown in the drawings, it should be understood that embodiments of this disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of this disclosure. It should be understood that the accompanying drawings and embodiments of this disclosure are for illustrative purposes only and are not intended to limit the scope of protection of this disclosure.

[0049] In the description of embodiments of this disclosure, the term "comprising" and similar terms should be understood as open-ended inclusion, i.e., "including but not limited to". The term "based on" should be understood as "at least partially based on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The terms "first", "second", etc., may refer to different or the same objects. Other explicit and implicit definitions may also be included below.

[0050] The embodiments disclosed herein can be implemented according to any suitable communication protocol, including but not limited to fourth-generation (4G), fifth-generation (5G), and future communication protocols (e.g., future cellular communication protocols, wireless LAN communication protocols such as IEEE 802.11, and / or any other protocols currently known or to be developed in the future). The technical solutions provided in this application can also be applied to device-to-device (D2D) communication, vehicle-to-everything (V2X) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), and Internet of Things (IoT) communication systems or other communication systems.

[0051] Figure 1A A schematic diagram of a communication system according to some embodiments of this disclosure is shown. For example... Figure 1AAs shown, the communication system 100 in this embodiment includes a radio access network (RAN) and a core network (CN). The RAN and CN interact through a specific standardized interface and a bearer network. The core network may include a first network element 110 (such as a sensing function, SF) and a third network element 130 (such as a session management function, SMF). Furthermore, the core network may also include other network entities, such as the Access and Mobility Management function (AMF), Unified Data Management (UDM), Unified Data Repository (UDR), Application Function (AF), User Plane Function (UPF), Network Repository Function (NRF), Policy Control Function (PCF), and so on. The radio access network may include a second network element 120 (e.g., a RAN node) and a terminal device 140 (e.g., a UE). The second network element 120 and the terminal device 140 can communicate with each other. For example, the second network element 120 can provide network access services to the terminal device 140. The terminal device 140 may have wireless transceiver capabilities, enabling it to communicate (e.g., wirelessly) with one or more network devices in one or more communication systems and receive network services provided by the network devices. The second network element 120 and the terminal device 140 may have both high-frequency and low-frequency communication capabilities. In embodiments of this disclosure, the transmission link from the second network element 120 to the terminal device 140 may be referred to as a downlink (DL), and the transmission link from the terminal device 140 to the second network element 120 may be referred to as an uplink (UL). It should be understood that... Figure 1A The communication system 100 shown is merely illustrative, and the embodiments of this disclosure can also be applied to other scenarios. For example, the second network element 120 and the terminal device 140 can communicate directly or perform multi-hop transmission via other relays. It should also be understood that... Figure 1A The number of network elements or terminal devices shown is for illustrative purposes only. There may be more or fewer network elements or terminal devices, and this disclosure makes no limitation in this regard.

[0052] exist Figure 1AIn the communication system 100 shown, the Sensing Function (SF) is primarily responsible for receiving, processing, and releasing measurement data from various sensing devices, while also managing sensing services, controlling sensing processes, and ensuring the compliant use of sensing data. The SMF is mainly responsible for UP element selection, UP element reselection, IP address allocation, bearer establishment, modification, and release, and QoS control. The AMF is responsible for user mobility management, including mobility state management, allocating temporary user identities, authenticating and authorizing users. The UDM is responsible for managing subscription data and notifying the relevant network elements when subscription data is modified. The UDR is responsible for storing and retrieving subscription data, policy data, and common architecture data; providing relevant data to the UDM, PCF, and NEF; employing different data access authentication mechanisms for different types of data, such as subscription data and policy data, to ensure data access security; and returning a failure response with an appropriate reason value for illegal service operations or data access requests. The AF is responsible for providing certain application layer services to the UE, notifying the network of QoS and charging policy requirements, and obtaining application-related information from the core network. UPF is responsible for interconnecting Protocol Data Unit (PDU) sessions with the data network, packet routing and forwarding, and packet inspection. NRF is responsible for network element registration and discovery, and maintains network element information, such as the network element instance identifier, type, PLMN, slice-related identifier, IP address or FQDN, the network element's capabilities, and supported services.

[0053] Furthermore, it should be understood that the communication system 100 in this disclosure embodiment can be applied to various scenarios. For example, the communication system 100 may include, but is not limited to, the three major application scenarios of narrowband Internet of Things (NB-IoT), long term evolution (LTE), long term evolution advanced (LTE-A), and 5G mobile communication systems: enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and enhanced machine-type communication (eMTC).

[0054] In Long Term Evolution (LTE) / Long Term Evolution Advanced (LTE-A) communication systems and New Radio (NR) systems, duplex modes can be mainly divided into Frequency Division Duplex (FDD) and Time Division Duplex (TDD). For wireless communication systems operating in TDD mode, the downlink and uplink carriers share the same carrier frequency. Multiple access methods typically employ Orthogonal Frequency Division Multiplexing (OFDMA). The main characteristic of OFDMA is that it divides transmission resources into mutually orthogonal time-frequency resource elements (REs). Signals transmitted by the transmitter are carried on REs and transmitted to the receiver. Because different REs are orthogonal, the receiver can receive the signal transmitted on each RE individually. The time-frequency resource unit is the smallest resource granularity in an OFDM (Orthogonal Frequency Division Multiplexing) system. In the time domain, it is an OFDM symbol (the smallest time unit in the OFDM system), and in the frequency domain, it is a subcarrier.

[0055] The solutions disclosed herein are applicable to Long Term Evolution (LTE) systems, LTE Frequency Division Duplex (FDD) systems, LTE Time Division Duplex (TDD) systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) systems, 5th Generation (5G) systems, and future communication systems. Of course, the solutions of this disclosure can also be applied to other possible communication systems, such as Internet of Things (IoT) networks, wireless local area network systems supporting the 802.11 series protocols, wireless personal area network systems based on ultra-wideband (UWB), sensing systems, vehicle-to-everything (V2X), machine-type communication (MTC), long-term evolution-machine (LTE-M), machine-to-machine (M2M), vehicle-to-vehicle (V2V), long-term evolution-vehicle (LTE-V), and satellite communication systems. The communication systems described above applicable to this disclosure are merely illustrative examples, and the communication systems applicable to this disclosure are not limited thereto. They are uniformly described here and will not be repeated below.

[0056] Figure 1B and Figure 1C The diagrams show 5G network architectures based on service-oriented architecture and point-to-point interfaces, respectively. The functions of each network element in both diagrams can be found by referring to... Figure 1A The description in [the document] will not be repeated here. The main difference between the two lies in the interface type: in [the document]... Figure 1C In the 5G network architecture 102, various network elements are directly connected through dedicated point-to-point interfaces. This architecture is relatively simple in structure, but relatively limited in flexibility and scalability. Figure 1BIn the 5G network architecture 101, various network elements interact through standardized service interfaces. The advantage of service interfaces lies in their high flexibility and scalability, enabling dynamic deployment and efficient collaboration of network functions, supporting more efficient resource sharing and functional decoupling, and providing better support for key 5G technologies such as network slicing and edge computing.

[0057] It is important to note that SF can be deployed in different ways in different implementations. Figure 1D and Figure 1E This illustrates two different ways to deploy SF in the core network. Figure 1D In the network architecture 103 shown, the SF can be deployed as a single network element in the core network, responsible for sending sensed data to the Network Open Function (NEF), which then further transmits the sensed data to the Application Function (AF). Figure 1E In the network architecture 104 shown, SF can be divided into the sensing function of the control plane (SF-C) and the sensing function of the user plane (SF-U). SF-C is mainly responsible for the management of sensing services, the transmission of control information, and the selection of appropriate sensing executors and SF-U for data processing. SF-U is mainly responsible for acquiring sensing data, performing sensing calculations, and opening the processed sensing data to third-party applications or other network function entities, thereby realizing the decoupling and coordination of sensing functions between the control plane and the user plane.

[0058] A terminal device is a device with wireless transceiver capabilities. It can communicate with one or more core network (CN) devices (or core equipment) via access network devices (or access equipment) in a radio access network (RAN). Terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water (such as on ships); and they can be deployed in the air (e.g., on airplanes, balloons, and satellites). In this disclosure, the terminal device may also be referred to as user equipment (UE), which may be a mobile phone, mobile station (MS), tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, wireless terminal device in smart home, subscriber unit, cellular phone, wireless data card, personal digital assistant (PDA) computer, tablet computer, laptop computer, machine type communication (MTC) terminal device, drone, etc. Terminal devices may include various handheld devices, in-vehicle devices, wearable devices, computing devices, or other processing devices connected to a wireless modem with wireless communication capabilities. Optionally, terminal devices may be handsets with wireless communication capabilities, terminal devices in the Internet of Things or the Internet of Vehicles, or any form of terminal device in 5G and subsequent communication systems; this disclosure does not limit this. In this disclosure, the means for implementing the functions of the terminal device may be the terminal device itself, or it may be a means that supports the terminal device in implementing the functions, such as a chip system or a chip, which may be installed in the terminal device. In this application, the chip system may consist of chips or may include chips and other discrete components.

[0059] Access network equipment (such as) Figure 1A The second network element 120 can be any device with wireless transceiver capabilities that can communicate with terminal devices, such as a radio access network (RAN) node that connects terminal devices to a wireless network. Examples of RAN nodes currently include: macro base stations, micro base stations (also known as small cells), relay stations, access points, gNBs, transmission reception points (TRPs), evolved Node Bs (eNBs), radio network controllers (RNCs), home base stations (e.g., home-evolved Node Bs, or home Node Bs, HNBs), base band units (BBUs), WiFi access points (APs), integrated access and backhaul (IABs), satellites, and drones.

[0060] In this embodiment of the disclosure, the device for implementing the function of the network element can be a network device or a device capable of supporting the network device in implementing the function, such as a chip system or a chip, which can be installed in the network device. In this embodiment, the chip system can be composed of chips or can include chips and other discrete devices.

[0061] Wireless signals in the environment (such as sound, light, and radio frequency) can be used for environmental sensing while fulfilling their primary functions (such as lighting and communication). Taking radio frequency signals as an example, radio waves undergo direct propagation, reflection, and scattering, forming multipath propagation, which allows the receiver signal to carry spatial information. Wireless sensing technology analyzes these signal changes to obtain channel characteristics and achieve environmental sensing. For example, changes in Wi-Fi signal strength can reflect the location of a device and its environment; a weak signal may indicate a greater distance, while a sudden drop in signal strength may indicate entering an enclosed space such as an elevator. The selection of signal characteristics has a crucial impact on sensing accuracy and reliability.

[0062] Radar sensing is a common wireless sensing technology that analyzes target echoes to extract the target's position, shape, motion characteristics, and infer environmental features. Compared to visual sensors, radar is unaffected by light, can penetrate obstructions, and protects privacy; compared to ultrasonic technology, radar has a longer sensing range and is harmless. Millimeter-wave radar is widely used in automotive driver assistance systems to detect pedestrians and vehicles ahead, enabling collision avoidance warnings. Furthermore, radar has wide applications in smart homes, autonomous driving, and wearable devices. With the development of low-power, small radar sensors, radar technology is increasingly widely used in smart devices and electronic products. The advantage of radar technology lies in its efficient detection of moving targets, utilizing the Doppler effect of target echoes to accurately analyze the target's direction and speed. The introduction of multi-channel sensors allows for the capture of target trajectories from multiple angles, and by combining real-time and historical data, accurate identification of complex motion patterns can be achieved.

[0063] The following uses the detection of the presence of a target object and the perception of its motion direction as an example to briefly explain the basic principles of perception technology and algorithms: In a perception system, device A sends a perception signal, which is received and detected by device B to achieve environmental perception. Typically, in line-of-sight (LOS) detection scenarios, the system detects whether a target object crosses the monitoring area based on fluctuations in the Received Signal Strength Indicator (RSSI). Furthermore, in non-line-of-sight (NLOS) detection scenarios, by extracting physical layer features from the Channel State Information (CSI) and performing preprocessing such as filtering on the amplitude and phase data to replace traditional RSSI detection, the accuracy of target detection is significantly improved, effectively overcoming multipath interference. Based on channel state information data collected by multiple receivers, a multi-node joint solution method can be used to achieve vector analysis of the target's movement direction (such as dynamic estimation of parameters like trajectory deflection angle and motion speed).

[0064] With the rapid development of 5G networks, their application scenarios have expanded from traditional mobile broadband communication to emerging fields such as smart cities, autonomous driving, and the industrial internet. These scenarios place higher demands on networks, requiring not only high-speed, low-latency communication capabilities but also environmental awareness capabilities, such as real-time acquisition of information like the location, speed, and distance of objects. To meet these needs, the integration of communication and sensing functions has become crucial, which can not only improve resource utilization efficiency but also reduce deployment costs. For example, future 5G networks can deploy integrated radar and communication base stations, leveraging the high-precision sensing capabilities of radar to improve communication efficiency. The communication and sensing resources of the base station can be time-division multiplexed or space-division multiplexed to achieve efficient perception of the surrounding environment or objects. This sensing capability is particularly important in security scenarios where cameras cannot be installed, such as detecting drone intrusions in specific industrial parks or using roadside base stations for traffic flow statistics and vehicle navigation in traffic scenarios. In addition, 5G terminals can also have sensing capabilities for detecting the surrounding environment or objects. For example, a terminal can send sensing measurement signals and receive signals reflected back from the surrounding environment; this mode can be called a "self-transmitting and self-receiving" mode. In another mode, one terminal device (such as a UE) can send a sensing signal, while other terminal devices receive the reflected signal; this mode can be called "UE transmits, other UEs receive." Different sensing modes have different requirements for terminal capabilities. Therefore, in practical applications, an appropriate sensing mode can be selected for environmental sensing measurements based on the specific scenario requirements. This flexibility and diversity provides broader possibilities for the application of 5G networks in diverse scenarios.

[0065] However, in synergistic sensing scenarios, the resource requirements of communication and sensing differ significantly and may even conflict. For example, communication services require stable bandwidth and low latency, while sensing services rely on high-precision signal processing capabilities. Existing resource allocation methods, however, primarily optimize for single functions and are ill-suited to the dynamic demands of communication and sensing fusion scenarios. Therefore, how to dynamically coordinate communication and sensing resources to achieve a good balance in their performance has become a critical issue that urgently needs to be addressed.

[0066] Specifically, when the Radio Access Network (RAN) simultaneously undertakes communication and sensing functions and resources are limited, it is necessary to clearly distinguish the Quality of Service (QoS) parameters for the two. The QoS characteristics required for sensing services may include key indicators such as sensing latency and sensing accuracy. However, the current QoS parameter system (such as resource type, default priority, packet delay budget, packet error rate, default maximum data burst size, and default average window) is mainly designed for communication services and does not fully consider the needs of sensing services. In particular, parameters such as resource type, packet error rate, default maximum data burst size, and default average window are not applicable in sensing scenarios. Furthermore, the QoS characteristics specific to sensing services have not yet been incorporated into the current communication QoS framework, making it difficult to effectively correlate and guarantee the performance requirements of sensing services by directly using the existing system. Therefore, there is an urgent need to design a more suitable QoS mechanism for integrated sensing and communication scenarios.

[0067] Furthermore, when terminal devices (such as UEs) and RANs simultaneously perceive a certain area and employ different perception architectures, how the RAN can efficiently process perception data from the UE and itself to improve perception accuracy becomes a key issue addressed in this patent. This involves not only optimizing resource allocation but also improvements in perception data fusion and collaborative processing to achieve higher-precision environmental perception capabilities.

[0068] Based on the above analysis and discussion, this disclosure proposes a method for dynamically coordinating sensing and communication resources. In some embodiments, by designing QoS parameters corresponding to sensing services, when the UE and / or RAN simultaneously support sensing and communication services, the priority of service execution is dynamically determined based on the QoS parameters of the sensing and communication services. This enables reasonable scheduling of the two services when resources are limited, ensuring that service execution meets user needs.

[0069] Figure 2A A schematic diagram of the communication flow of some embodiments of this disclosure is shown. For clarity and without any limitation, flow 200 will be combined with… Figure 1A To describe it. Figure 2A Involving Figure 1A The network consists of a first network element 110, a second network element 120, a third network element 130, and a terminal device 140. The first network element 110 may be, for example, the SF or SF-CP described above, the second network element 120 may be, for example, a RAN node, the third network element 130 may be, for example, an SMF, and the terminal device 140 may be, for example, a UE.

[0070] In process 200, at point 210, the first network element 110 receives a first request message from the sensing service consumer (or what may be referred to as the sensing service requester, such as a UE, or an AF associated with the sensing service) to request a sensing service. In some implementations, the first request message may include at least one of the following: an identifier of the sensing service, the type of the sensing service (e.g., but not limited to, UAV detection, traffic monitoring and analysis, environmental monitoring, etc.), and the requirements of the sensing service (i.e., key performance indicators (KPIs), such as but not limited to, accuracy, latency, false alarm rate, the geographical range of the sensing, and the type of sensing result (e.g., the expected output format of the sensing result, such as raw data, point cloud data, RV spectrum, RVA spectrum, etc.)). Through the first request message, the first network element 110 can determine the terminal equipment participating in the sensing, the RAN node, and the transmission mode of the sensing signal (e.g., may include UE self-transmission and reception, first UE transmitting and second UE receiving, RAN node self-transmission and reception, first RAN node transmitting and second RAN node receiving, UE transmitting and RAN node receiving, and RAN node transmitting and UE receiving, etc.).

[0071] Optionally, in some implementations, after receiving the first request message, the first network element 110 may send a request message to the Policy Control Function (PCF) to obtain subscription data associated with the sensed service. This process aims to obtain QoS configuration information associated with the target sensed service, where the subscription data can be stored in a core network data management entity, such as a Unified Data Management (UDM) or a Unified Data Repository (UDR). This subscription data may include, for example, 5G system subscription sensed QoS information, such as a subscribed sensed QoS profile (5GS Subscribed sensing QoS profile), which can serve as the basis for the first network element 110 to determine the sensed service QoS policy. It should be noted that the sensed service can adopt a flexible configuration scheme; it can use the same QoS parameter system as the communication service (such as 5QI), or it can define a dedicated sensed service quality identifier (such as Sensing QoS ID, or sensing 5QI) based on service requirements. Detailed examples will be given in Tables 2 and 3 below. The QoS information subscribed to by a 5G system can include at least one of the following parameters: the required service level information corresponding to the sensed service, such as a service level identifier, which in this paper can be a Quality of Service identifier (e.g., 5QI, or sensing QoS ID, or sensing 5QI), and the quality of service identifier can be associated with a set of QoS characteristics (such as priority, packet latency, packet error rate, etc.); information indicating priority (representing the importance of the service), preemptibility (indicating whether preemption of other service resources is allowed), and / or vulnerability to preemption (defining whether it is possible to be preempted by a higher priority service), which in this paper can be, for example, allocation and retention priority (ARP); or optionally, the scheduling priority corresponding to the QoS flow or sensed data transmission, or the identifier corresponding to the QoS flow or sensed data flow, and other QoS parameters associated with the sensed service. This configuration scheme ensures compatibility with traditional 5G systems while meeting the differentiated quality of service requirements of various sensed services.

[0072] Optionally, at point 220, the first network element 110 can determine the Quality of Service (QoS) information corresponding to the perceived service. Here, two scenarios are possible:

[0073] Scenario #1: The QoS information corresponding to the sensed service determined by the first network element 110 may include information associated with the priority of the sensed service, such as service quality identifiers (e.g., 5QI, or sensing QoS ID, or sensing5QI), priority levels indicating priority (representing the importance of the service), preemptibility (indicating whether preemption of other service resources is allowed), and / or vulnerability to preemption (defining whether it is possible to be preempted by higher priority services) (e.g., ARP), and identifiers corresponding to QoS flows or sensed data flows (e.g., QFI), etc., at least one of the following. Furthermore, the aforementioned QoS information may also include QoS rules, which may include one or more of the following information: bandwidth, latency, packet loss rate, traffic scheduling, the degree of matching between data packets and QoS flows, priority, etc., and one or more of the service quality-related information described above.

[0074] Scenario #2: Alternatively, the first network element 110 may also determine at least one of the following: first QoS information corresponding to the execution of the sensing service, and second QoS information corresponding to the transmission of the sensing service. Specifically, the first QoS information may refer to the quality of service information used by the terminal device and / or the second network element when performing the sensing operation. The first QoS information may include, but is not limited to: priority information associated with the execution of the sensing service, such as a quality of service identifier (e.g., 5QI, or sensing QoS ID, or sensing 5QI); priority level (indicating the importance of the service), preemption information (indicating whether preemption of other service resources is allowed), and / or vulnerability to preemption (defining whether it is possible to be preempted by a higher priority service), such as ARP; and identifiers corresponding to QoS flows or sensing data flows (e.g., QFI). In addition, the first QoS information may also include QoS rules associated with the execution of the sensing service. An introduction to QoS rules can be found above and will not be repeated here. The second QoS information can refer to the quality of service information used by the terminal device and / or the second network element when transmitting the sensed data after the execution of the sensed service. The second QoS information may include, but is not limited to: priority information associated with the transmission of the sensed service, such as a quality of service identifier (e.g., 5QI, or sensing QoS ID, or sensing 5QI); priority levels (indicating the importance of the service), preemption information (indicating whether preemption of other service resources is allowed), and / or vulnerability to preemption (defining whether it is possible to be preempted by a higher priority service), such as ARP; and identifiers corresponding to QoS flows or sensed data flows (e.g., QFI). Furthermore, the first QoS information may also include QoS rules associated with the transmission of the sensed service. An introduction to QoS rules can be found above and will not be repeated here.

[0075] At 232-1, the first network element 110 can send a second request message 234-1 to the second network element (e.g., RAN node) 120.

[0076] In some embodiments, the second request message 234-1 can be sent from the first network element 110 to the second network element 120 via an intermediate network node (such as an AMF). In other embodiments, the second request message 234-1 can be sent directly from the first network element 110 to the second network element 120.

[0077] In some embodiments, the second request message 234-1 is used to request the second network element 120 to perform sensing services. Depending on the implementation of step 220, several scenarios are described here:

[0078] Case #A: Corresponding to Case #1 in 220, the second request message 234-1 may include QoS information corresponding to the sensed service, such as the Quality of Service identifier (5QI, or sensing 5QI, or Sensing QoS ID) as described in Case #1 above, information indicating priority level (representing the importance of the service), preemptibility (indicating whether preemption of other service resources is allowed), and / or vulnerability to preemption (defining whether it may be preempted by a higher priority service) (such as ARP), and the identifier corresponding to the QoS flow or sensed data flow (e.g., QFI), etc. In these embodiments, after receiving the second request message 234-1, at 240, the second network element 120 can determine at least one of the above-mentioned first QoS information and / or second QoS information. A detailed description of the first QoS information and the second QoS information can be found in the description of Case #2 above, and will not be repeated here.

[0079] Case #B: Corresponding to Case #2 in 220, the second request message 234-1 may include at least one of first QoS information and / or second QoS information. A detailed description of the first QoS information and the second QoS information can be found in the description of Case #2 above, and will not be repeated here. Then, the second network element 120 can determine the execution priority of the sensed service based on the first QoS information, and / or determine the transmission priority of the sensed service based on the second QoS information.

[0080] Optionally, in some embodiments, step 220 above may not be performed. In these embodiments, the second request message 234-1 may be equivalent to the first request message for requesting a sensed service described in step 210 above, without including specific sensed service QoS information. Therefore, the specific description of the second request message 234-1 here can refer to the description of the first request message in step 210 above, and will not be repeated here. Similar to cases #1 and #2 in step 220 above, in these embodiments, after receiving the second request message 234-1, two situations may also exist:

[0081] Case #C: The second network element 120 can determine the QoS information corresponding to the sensing service based on the second request message 234-1. Here, the description of the QoS information corresponding to the sensing service can be found in the relevant description in Case #1 at step 220 above, and will not be repeated here. Then, the second network element 120 can further determine the first QoS information corresponding to the execution of the sensing service and / or the second QoS information corresponding to the transmission of the sensing service based on the determined QoS information corresponding to the sensing service. The specific description of the first QoS information and the second QoS information can be found in the description in Case #2 above, and will not be repeated here.

[0082] Case #D: The second network element 120 can also directly determine the first QoS information corresponding to the execution of the sensing service and / or the second QoS information corresponding to the transmission of the sensing service based on the second request message 234-1. For a detailed description of the first QoS information and the second QoS information, please refer to the description in Case #2 above, which will not be repeated here.

[0083] It should be understood that in the QoS information corresponding to the sensed service mentioned above, the service quality identifier (e.g., 5QI, or sensing 5QI, or Sensing QoS ID), priority (sensing PriorityLevel), preemptibility (which can indicate whether preemption of other service resources is allowed), and / or vulnerability to preemption (defining whether it is possible to be preempted by higher priority services), ARP (e.g., sensing ARP) and other information can reflect the priority status of the sensed service.

[0084] Furthermore, in the aforementioned first QoS information, the service quality identifier (e.g., 5QI, or sensing 5QI, or Sensing QoS ID) corresponding to the execution of the sensing service, the priority (sensing PriorityLevel) corresponding to the execution of the sensing service, the preemptibility (which can indicate whether preemption of other service resources is allowed) corresponding to the execution of the sensing service, and / or the vulnerability to preemption (defining whether it may be preempted by higher priority services) corresponding to the execution of the sensing service, and the ARP (e.g., sensing ARP) corresponding to the execution of the sensing service can reflect the priority status corresponding to the first QoS information.

[0085] Furthermore, in the aforementioned second QoS information, the QoS identifier corresponding to the sensed data transmission (e.g., 5QI, or sensing 5QI, or Sensing QoS ID), the priority corresponding to the sensed data transmission (sensing PriorityLevel), the preemptibility of the sensed data transmission (which can indicate whether preemption of other service resources is allowed) and / or the vulnerability of the sensed data transmission to being preempted (defining whether it may be preempted by higher priority services), and the ARP (sensing ARP) corresponding to the sensed data transmission can reflect the priority status corresponding to the sensed second QoS information.

[0086] At point 250, the second network element 120 can determine whether to prioritize the execution of the sensing service and / or the transmission of sensing data based on the determined first QoS information and / or second QoS information, and the third QoS information corresponding to the communication service. If the priority of the sensing service is higher than that of the communication service, the sensing service is executed or scheduled first, and the communication service is rejected or not executed first; conversely, if the priority of the communication service is higher, the communication service is executed first.

[0087] Specifically, in some implementations, the second network element 120 can determine a first priority for the execution of the sensing service based on the first QoS information, and / or determine a second priority for the transmission of the sensing service based on the second QoS information. Furthermore, the second network element 120 can also determine third QoS information corresponding to the communication service based on the acquired QoS information associated with the communication service (e.g., obtained from the AMF or SMF via a PDU session establishment request). In some embodiments, the third QoS information may include QoS information corresponding to the second network element 120, including but not limited to: QoS profiles (e.g., 5G QoS identifier (5QI) for identifying the priority and characteristics of a QoS flow; ARP for indicating the priority of resource allocation; Guaranteed Flow Bit Rate (GFBR) for GBR QoS flows, including uplink and downlink; Maximum Flow Bit Rate (MFBR) for GBR QoS flows, including uplink and downlink; Maximum Packet Loss Rate for GBR QoS flows, including uplink and downlink); QoS flow related parameters (e.g., QoS Flow Identifier (QFI) for uniquely identifying a QoS flow in a PDU session; type of QoS Flow, such as whether the QoS flow is guaranteed bit rate (GBR) or non-guaranteed bit rate (Non-GBR); etc.). The second network element 120 may determine the third priority based on one or more of the above parameters in the third QoS information.

[0088] Subsequently, in order to determine whether to execute and / or transmit sensing services, the second network element 120 can determine whether to prioritize the execution of sensing services and / or the transmission of sensing data based on the aforementioned first priority, second priority, and third priority. Note that the sensing data here can be either the sensing data corresponding to the terminal device 140 or the sensing data corresponding to the second network element 120.

[0089] Alternatively, in some implementations, the second network element 120 can first determine whether to prioritize the execution of sensing services based on a first priority and a third priority. If it is determined that the sensing services should be executed first, the second network element 120 can then determine whether to prioritize the transmission of sensing data based on a second priority and a third priority. In this way, the priorities of sensing services and communication services can be comprehensively considered, and decisions can be made flexibly on whether to execute and / or transmit sensing services, ensuring efficient resource allocation and meeting service requirements and system performance requirements.

[0090] In some embodiments, the priority of the execution of the communication service and the execution of the sensed service can be compared based on at least one parameter in the first QoS information corresponding to the execution of the sensed service and the third QoS information corresponding to the communication service (such as a Quality of Service identifier (e.g., 5QI, or sensing QoS ID, or sensing 5QI), a priority level indicating priority (representing the importance of the service), preemptibility (indicating whether preemption of other service resources is allowed), and / or vulnerability to preemption (defining whether preemption by a higher priority service is possible) (e.g., ARP), and a QoS flow identifier, etc.). Furthermore, the priority of the execution of the communication service and the transmission of the sensed service can also be compared based on at least one parameter in the second QoS information corresponding to the transmission of the sensed service and the third QoS information corresponding to the communication service (similarly, information such as a Quality of Service identifier, a priority level indicating priority, preemptibility, and / or vulnerability to preemption, and a QoS flow identifier, etc.).

[0091] For example, the ARP values ​​of sensing and communication services can be used to determine whether to accept or reject a UE's communication service request under resource constraints; or whether to accept or reject the establishment of a new communication QoS flow when a sensing service is currently being executed. Furthermore, priority level can be used to indicate the priority of sensing and communication resource scheduling under congestion conditions. In congestion, if sensing and communication services need to be executed simultaneously on the RAN, and the sensing service has a higher scheduling priority, then sensing is executed first, and sensing data / results are transmitted first; conversely, the opposite is also true. Additionally, in non-congestion conditions, priority can be used to indicate the priority between sensing and communication services. In non-congestion conditions, it indicates the priority between sensing services or between sensing and communication services. Furthermore, the 5QI value can be used for priority comparison. For example, for sensing services with strict latency requirements (such as scenarios requiring a 200ms latency), SF-CP (or SF) can determine that the 5QI for sensing execution is 1, and the latency for sensing execution is 100ms. Additionally, it can determine that the 5QI for sensing data transmission is 1, and its packet latency is also 100ms. Thus, the RAN node can compare the 5QI for sensing execution and data transmission with the 5QI for communication (e.g., the 5QI for communication is 1.5). Under this configuration, according to the QoS comparison rules (i.e., the smaller the 5QI value, the higher the priority), the RAN node can decide to prioritize sensing tasks and ensure the priority transmission of sensing data. Therefore, the execution of sensing services and the transmission of sensing data can be successfully completed within the preset latency requirements.

[0092] Furthermore, at step 232-2, the first network element 110 can also send a third request message 234-2 to the terminal device 140. Note that step 232-2 can be performed simultaneously with step 232-1 as described above, or it can be performed at different times. In some embodiments, the third request message 234-2 can be sent from the first network element 110 to the terminal device 140 via an intermediate network node (such as an AMF). In other embodiments, the third request message 234-2 can be sent from the first network element 110 to the terminal device 140 via a first intermediate network node (such as an SMF) and a second intermediate network node (such as an AMF), respectively. In still other embodiments, the third request message 234 can be sent directly from the first network element 110 to the terminal device 140.

[0093] In some embodiments, the third request message 234-2 is used to request the terminal device 140 to perform a sensing service. Similar to the second request message 234-1 described above, depending on the implementation at step 220, several cases are described here (e.g., cases #A to #D described above). For a detailed description of these different cases, please refer to the description of the second request message 234-1 above, which will not be repeated here.

[0094] It should be noted that the specific information contained in the second request message 234-1 and the third request message 234-2 may be the same or different, depending on the specific implementation. Furthermore, it should be noted that depending on the different transmission modes of the sensed signal (e.g., UE self-transmission and reception, first UE transmission and second UE reception, RAN node self-transmission and reception, first RAN node transmission and second RAN node reception, UE transmission and RAN node reception, and RAN node transmission and UE reception, etc.), the first network element 110 may send the second request message 234-1 only to the RAN node, or send the third request message 234-2 only to the UE, or send request messages to both the UE and the RAN. Alternatively, in other scenarios, the first network element 110 may send multiple second request messages 234-1 to multiple RAN nodes, or multiple third request messages 234-2 to multiple UEs; this disclosure does not impose any restrictions on this.

[0095] Subsequently, similar to the behavior of the second network element 120 at location 250, at location 250, the terminal device 140 can also determine whether to prioritize the execution of the sensing service and / or the transmission of sensing data based on the determined first QoS information and / or second QoS information, and the third QoS information corresponding to the communication service. If the priority of the sensing service is higher than that of the communication service, the sensing service is executed or scheduled first, and the communication service is rejected or not executed first; conversely, if the priority of the communication service is higher, the communication service is executed first.

[0096] Specifically, in some implementations, terminal device 140 may determine a first priority for the execution of the sensing service based on first QoS information, and / or determine a second priority for the transmission of the sensing service based on second QoS information. Furthermore, terminal device 140 may also determine third QoS information corresponding to the communication service based on the acquired QoS information associated with the communication service (e.g., obtained from AMF or SMF via a PDU session establishment request). In some embodiments, the third QoS information may include QoS information corresponding to terminal device 140, including but not limited to: QoS flow identifier (e.g., QFI); QoS rule (e.g., including QFI, packet filter set, and priority value); and other QoS parameters (e.g., 5GQI (5G QoS Identifier) ​​or 5QI, ARP, stream bit rate, aggregate bit rate); etc. Terminal device 140 may determine a third priority based on one or more of the above parameters in the third QoS information.

[0097] Subsequently, in order to determine whether to execute and / or transmit sensing services, terminal device 140 can determine whether to prioritize the execution of sensing services and / or the transmission of sensing data based on the aforementioned first priority, second priority, and third priority. Note that the sensing data here can be either the sensing data corresponding to terminal device 140 or the sensing data corresponding to the second network element 120.

[0098] Alternatively, in some implementations, the second network element 120 can first determine whether to prioritize the execution of sensing services based on a first priority and a third priority. If it is determined that the sensing services should be executed first, the second network element 120 can then determine whether to prioritize the transmission of sensing data based on a second priority and a third priority. In this way, the priorities of sensing services and communication services can be comprehensively considered, and decisions can be made flexibly on whether to execute and / or transmit sensing services, ensuring efficient resource allocation and meeting service requirements and system performance requirements.

[0099] Based on the different results determined at point 250, two options are possible. In option 1, based on the determination (260-1) that communication services are prioritized, the second network element 120 can send a first notification message 274-1 (272-1) indicating a sensing service failure to the first network element 110. The first notification message 274-1 may include the identifier of the sensing service that was not executed or was preempted, or the reason value for the sensing service failure. For example, when a sensing service cannot be successfully established, the RAN node can send a notification message directly to the SF-CP (or SF), or send a notification message to the SF-CP (or SF) via an intermediate node (e.g., AMF or SMF). This notification message contains information that can be used to indicate the obstruction of the sensing service's execution, such as the affected sensing ID or sensing task ID. In addition, the message may selectively include the specific reason that caused the sensing service to fail to execute, such as prioritizing communication services, or the sensing service being executed corresponding to the sensing ID or sensing task ID being preempted by the communication service. Furthermore, the message can also explicitly indicate which specific communication service is preempting the currently executing sensing service; that is, the message can include an identifier corresponding to that communication service (e.g., PDU session ID).

[0100] Subsequently, optionally, the SF-CP (or SF) can directly send a sensing service response message or a sensing failure notification message to the UE or sensing AF, or send it via an intermediate node (such as AMF, SMF, etc.), to notify the UE or sensing AF that the communication service is being prioritized, or that the sensing service being executed has been preempted by the communication service. The information contained in this response message / notification message may be the same as the information contained in the notification message received by the SF-CP (or SF) from the RAN node above, or may include other necessary information to ensure that the UE or sensing AF can fully understand the reason for the sensing service establishment failure and its priority relationship with the communication service.

[0101] In Option 2, based on the determination (260-2) of executing a sensing service or the transmission of a sensing service, the second network element 120 can send a second notification message 274-2 (272-2) indicating communication service failure to the third network element 130 (such as a Session Management Function (SMF)). The second notification message 274-2 may include an identifier of the communication service that was not executed or was preempted, or a reason value for the communication service failure. For example, when a communication service cannot be successfully established, the RAN node can send the notification message directly to the SMF, or via an intermediate node (e.g., the AMF). This notification message contains information that can be used to indicate the obstruction of communication service execution, such as the affected PDU session ID and / or UE ID. Furthermore, the message may selectively include a specific reason why the communication service could not be executed, such as prioritizing the execution of a sensing service, or the communication service being executed associated with the PDU session ID and / or UE ID being preempted by the sensing service. Furthermore, the message can also explicitly indicate which specific sensing service is preempting the ongoing communication service; that is, the message can include an identifier corresponding to that sensing service (e.g., sensing ID or sensing task ID).

[0102] Subsequently, optionally, the SMF can directly send a PDU session establishment response message or a communication failure notification message to the UE, or send it to the UE via the AMF, to notify the UE that the sensed service is being prioritized, or that the currently executing communication service has been preempted by the sensed service. The information contained in this response message / notification message may be the same as the information contained in the notification message received by the SMF from the RAN node above, or it may also include other necessary information to ensure that the UE can fully understand the reason for the communication service establishment failure and its priority relationship with the sensed service.

[0103] In this way, notifications and feedback on the failure of perceived or communication services can be achieved, enabling timely identification and handling of service failures, thereby optimizing the utilization of network resources.

[0104] Figure 2B A schematic diagram of the communication flow of some embodiments of this disclosure is shown. For clarity and without limitation, flow 205 will be combined with… Figure 1A To describe it. With Figure 2A resemblance, Figure 2B Also involved Figure 1A The network consists of a first network element 110, a second network element 120, a third network element 130, and a terminal device 140. The first network element 110 may be, for example, the SF or SF-CP described above, the second network element 120 may be, for example, a RAN node, the third network element 130 may be, for example, an SMF, and the terminal device 140 may be, for example, a UE.

[0105] Notice, Figure 2B The steps in the process are basically Figure 2A The steps are similar, except that at step 226', the third network element 130 can receive the fourth request message 224' from the first network element 110 (or alternatively, from the terminal device 140, or from the policy control function PCF). Figure 2A Similarly, depending on the implementation at step 220', the fourth request message 224' can be described in several ways:

[0106] Case #A': Similar to Case #1 in 220' (see details) Figure 2A Corresponding to case #1) in 220, the fourth request message 224' may include QoS information corresponding to the perceived service, such as, as described above. Figure 2A The Quality of Service (QoS) identifier (5QI, or sensing 5QI, or sensing QoS ID) described in Case #1 of 220 is used to indicate priority level (representing the importance of the service), preemptibility (indicating whether preemption of other service resources is allowed), and / or vulnerability to preemption (defining whether it may be preempted by a higher priority service) information (such as ARP), as well as the identifier corresponding to the QoS flow or sensed data flow (e.g., QFI). In some embodiments, after receiving the fourth request message 224', the third network element 130 can determine at least one of the above-mentioned first QoS information and / or second QoS information. A detailed description of the first QoS information and the second QoS information can be found above. Figure 2A The description in case #2 of 220 will not be repeated here. Accordingly, in case A', the second request message 234-1' (corresponding to Figure 2A The second request message 234-1 may include QoS information corresponding to the perceived service; or alternatively, it may include first QoS information and / or second QoS information.

[0107] Case #B': Similar to Case #2 in 220 (see details) Figure 2A Corresponding to case #2) in case 220, the fourth request message 224' may include at least one of the first QoS information and / or the second QoS information. A detailed description of the first QoS information and the second QoS information can be found in the description of case #2 above, and will not be repeated here. Accordingly, in case B', the second request message 234-1' may include the aforementioned first QoS information and / or second QoS information.

[0108] Optionally, in some embodiments, step 220' may not be performed. In these embodiments, the fourth request message 224' may be equivalent to step 210' (see details). Figure 2AThe first request message described at (210) is for requesting a sensed service, but does not include specific sensed service QoS information. Furthermore, the second request message 234-1' can also be equivalent to step 210' above (see details). Figure 2A The first request message at (210) does not include specific perceived service QoS information. Therefore, the detailed description of the fourth request message 224' and the second request message 234-1' can be found in the above description. Figure 2A The description of the first request message in step 210 will not be repeated here. (As mentioned above...) Figure 2A Similar to cases #C' and #D' at step 220, in these embodiments, after the second network element 120 receives the second request message 234-1', two situations may also exist:

[0109] Case #C': The second network element 120 can determine the QoS information corresponding to the sensed service based on the second request message 234-1'. For a description of the QoS information corresponding to the sensed service, please refer to the above. Figure 2A The relevant description in step 220 of case #1 will not be repeated here. Then, the second network element 120 can further determine, based on the determined QoS information corresponding to the sensing service, first QoS information corresponding to the execution of the sensing service, and / or second QoS information corresponding to the transmission of the sensing service. For a detailed description of the first QoS information and the second QoS information, please refer to the above. Figure 2A The description of case #2 at step 220 will not be repeated here.

[0110] Case #D: The second network element 120 can also directly determine the first QoS information corresponding to the execution of the sensing service and / or the second QoS information corresponding to the transmission of the sensing service based on the second request message 234-1'. For a detailed description of the first QoS information and the second QoS information, please refer to the above. Figure 2A The description of case #2 at step 220 will not be repeated here.

[0111] For steps 232-2' and subsequent steps related to terminal device 140, and Figure 2B For other operating steps, please refer to Figure 2A The corresponding descriptions in [the relevant section] will not be repeated here.

[0112] and Figure 2A In comparison, Figure 2B In this system, the capability to determine QoS information related to perceived services is deployed at the third network element 130. This enables notification and feedback of perceived or communication service failures, allowing for timely identification and handling of service failures, thereby optimizing network resource utilization.

[0113] To compare the priorities of communication and sensing services and ensure efficient allocation of network resources, the UE or RAN needs to configure QoS characteristic tables corresponding to the communication and sensing services. The QoS characteristic table is the basis for network resource scheduling, defining key parameters such as priority, latency, and resource type for different service types. In the embodiments of this disclosure, two options are provided to meet the needs of different scenarios.

[0114] The first option is the independent configuration method. In this method, separate QoS characteristic tables are configured for communication services and sensing services, as shown in Table 1 and Table 2 below.

[0115] Table 1 Communication QoS Characteristics Table

[0116]

[0117] Table 2 Sensitive QoS Characteristics Table

[0118]

[0119] In Tables 1 and 2, the QoS parameters for communication services and the QoS parameters for sensing services are set with different values ​​to achieve a clear distinction, such as... Figure 3A As shown in the image. Figure 3A A schematic diagram illustrating the independent configuration of communication and sensing quality of service parameters according to some embodiments of this disclosure is shown. Figure 3A As can be seen, communication and perception correspond to different 5QI (QoSIdentifier, Quality of Service Identifier), priority level, and ARP (Assignment and Retention Priority).

[0120] exist Figure 3A In this context, a star shape can represent the 5QI / priority level / ARP corresponding to communication, while a triangle represents the 5QI / priority level / ARP corresponding to sensing. From... Figure 3AAs can be seen, the QoS parameters for communication and sensing are clearly distinguished, and their values ​​are independent of each other. This means that suitable quality of service, priority, and resource allocation strategies can be configured for communication and sensing functions respectively according to different needs. For example, suppose the 5G QoS Identifier (5QI) value corresponding to a certain communication service X is 1, while the 5QI value corresponding to a sensing service Y is 1.5. According to QoS rules, the smaller the ARP value, the higher the priority. Therefore, when communication service X and sensing service Y exist simultaneously, their priorities can be determined by comparing their 5QI values. Since the 5QI of communication service X is less than that of sensing service Y, communication service X has a higher priority. Note that this only uses the 5QI corresponding to sensing and communication as an example; the priorities of the two can also be determined by comparing other parameters (such as priority or ARP value), and this disclosure does not limit this in this respect.

[0121] In this scenario, the RAN (or terminal device) can make the following decisions based on priority rules: First, when resources are insufficient, the RAN can prioritize the resource requirements of communication service X while rejecting resource requests from the sensing service Y; second, if communication service X is in operation and the sensing service Y attempts to establish a new QoS flow or occupy resources, the RAN can reject the QoS flow request from the sensing service Y to ensure that the service quality of communication service X is not affected. This independent configuration approach helps to optimize and allocate resources more flexibly to meet the needs of different applications or scenarios.

[0122] The second option is a joint configuration approach. In this approach, the sensing service can directly reuse the QoS characteristic table corresponding to the communication service, as shown in Table 3 below. This approach simplifies the configuration process by reusing the QoS parameter settings of the communication service and leverages the existing priority and resource allocation mechanisms of the communication service to support the sensing service, thereby quickly integrating it into the existing network scheduling mechanism. This approach is particularly suitable for scenarios where the sensing service and the communication service have high similarity in resource requirements, reducing configuration complexity and network management overhead.

[0123] Table 3 Communication and Sensing QoS Characteristics

[0124]

[0125] In Table 3, compared with communication services, the QoS parameters for sensing services have been optimized in the following ways: First, the original Packet Delay Budget parameter has been expanded to Packet Delay Budget / Response Time to more comprehensively reflect the different latency performance requirements of sensing and communication services. Second, a Sensing Accuracy parameter has been added to accurately describe the specific requirements of sensing services for measurement or detection accuracy. This parameter optimization design can meet the performance requirements of sensing services while maintaining compatibility with the QoS parameter system of communication services.

[0126] Table 3 shows the values ​​of QoS parameters corresponding to some or all of the communication services used in the perception service, such as... Figure 3B As shown in the image. Figure 3B A schematic diagram illustrating the joint configuration of communication and sensing quality of service parameters according to some embodiments of this disclosure is shown. Figure 3B In this context, a star shape can represent the 5QI / priority level / ARP corresponding to communication, while a triangle represents the 5QI / priority level / ARP corresponding to sensing. From... Figure 3B As can be seen, the QoS parameter values ​​for communication and sensing partially overlap. When sensing and communication services coexist, the system can determine their priority based on their QoS parameter values. When the QoS parameter values ​​for sensing and communication services are the same, the system can determine whether to prioritize the sensing or communication service based on locally configured rules.

[0127] In Tables 2 and 3 above, different perception accuracies can be specified according to different perception service types. For example, in the autonomous driving pedestrian recognition scenario, the perception accuracy can be specified as a detection accuracy rate ≥ 99.9%; in the unmanned and positioning scenario, the perception accuracy can be specified as a positioning error ≤ 0.05 meters; and so on.

[0128] In addition, it should be noted that the QoS characteristic values ​​in Tables 1 and 2 above are listed for illustrative purposes only and not for limiting purposes. In some other instances, any suitable values ​​other than those listed above may be used.

[0129] The choice between these two options depends on the specific application scenario and network requirements. If the resource requirements of communication and sensing services differ significantly, or if independent resource guarantees are needed for sensing services, then independent configuration is more suitable. If the resource requirements of communication and sensing services are similar, and to simplify the configuration process, joint configuration is the better choice. These two configuration options allow for dynamic adjustment of the priority and resource allocation of communication and sensing services based on actual business needs, thereby ensuring the quality of communication services while supporting the efficient operation of sensing services.

[0130] To present the technical solution of this disclosure more intuitively and clearly, the following will be combined with... Figures 4 to 8 Several example embodiments are described below.

[0131] Figure 4 Exemplary communication flows of some embodiments of this disclosure are shown. For example... Figure 4 As shown, process 400 involves UE 401, RAN node 402, SMF 403, SF-CP (or SF in some embodiments) 404, PCF 405, and UDM (or UDR) 406. UE 401 can be as follows: Figure 1A The example of terminal device 140 shown can be RAN node 402 as follows: Figure 1A The example of the second network element 120 shown, SMF 403 can be as follows: Figure 1A The example shown is the third network element 130, and the SF-CP404 can be as follows: Figure 1A An example of the first network element 110 shown.

[0132] At 410, UDM / UDR 406 stores the subscription information corresponding to the sensing service. This subscription data may include, for example, a 5G system subscription sensing QoS profile, which serves as the basis for SF-CP 404 to determine the QoS policy for the sensing service. As described above, the QoS profile may contain at least one of the following parameters: the required service level information corresponding to the sensing service, such as a service level identifier, such as 5QI; information indicating priority, preemption capabilities, and / or vulnerability to preemption, such as ARP; optionally, the scheduling priority of the QoS flow; and other QoS parameters associated with the sensing service.

[0133] At point 415, UE 401 establishes a Protocol Data Unit (PDU) session for communication services, allowing SMF 403 to determine communication-related QoS information (e.g., ARP and 5QI corresponding to the communication service). Subsequently, SMF 403 can send the communication-related QoS information to RAN node 402 via an intermediate node (e.g., AMF) or directly. Optionally, SMF can also send this communication-related QoS information to UE 401.

[0134] At position 420, SF-CP 404 can receive a sensing service request message from the sensing service consumer (e.g., UE 401, or the AF associated with the sensing service). This step could, for example, correspond to... Figure 2A Step 210 or Figure 2B Step 210'. As mentioned above, the sensing service request message may carry one or more of the following: the identifier of the sensing service; the type of sensing service, such as UAV detection, traffic monitoring, environmental monitoring, etc.; the requirements of the sensing service, such as accuracy, latency, false alarm rate, sensing range, and sensing result type (e.g., the expected output format of the sensing result, such as raw data, point cloud data, RV spectrum, RVA spectrum, etc.). SF-CP 404 can determine the sensing participants (such as RAN nodes, UEs) and the transmission mode of the sensing signal (such as RAN transmits and UE receives, first UE transmits and second UE receives, RAN node self-transmits and receives, first RAN node transmits and second RAN node receives, UE transmits and RAN node receives, and RAN node transmits and UE receives) based on the sensing service request message, etc.

[0135] Optionally, at 425, after receiving the sensing service request message, SF-CP 404 can send a request message to PCF 405, which is used to retrieve the subscription information corresponding to the sensing stored in UDM / UDR 406. Subsequently, at 430, SF-CP 404 receives the subscription information corresponding to the sensing from PCF 405.

[0136] At point 435, SF-CP 404 can determine QoS information corresponding to the sensed service based on the subscription information. For example, the QoS information corresponding to the sensed service may include information associated with the priority of the sensed service, such as one or more of 5QI, priority level, ARP, QoS rules, and QFI. Alternatively, SF-CP 404 can also determine at least one of first QoS information corresponding to the execution of the sensed service and second QoS information corresponding to the transmission of the sensed service based on the subscription information. For example, the first QoS information and / or the second QoS information may include information associated with the priority of the execution and / or transmission of the sensed service, such as at least one of 5QI, priority level, ARP, QoS rules, and QFI.

[0137] Then, at 440-1, SF-CP 404 can send a request message to RAN node 402 to request the execution and / or transmission of the sensing service, which may correspond to, for example, a... Figure 2A The second request message 234-1, or Figure 2B The fourth request message 234-1' in the protocol. In some embodiments, this request message can be sent from SF-CP 404 to RAN node 402 via an intermediate network node (such as AMF). In other embodiments, the request message can also be sent directly from SF-CP 404 to RAN node 402.

[0138] In some embodiments, the request message may include QoS information corresponding to the sensing service, such as 5QI (sensing 5QI), priority level, ARP (sensing ARP), etc. In these embodiments, after receiving the request message, at 445, the second network element 120 may determine first QoS information corresponding to the execution of the sensing service, and / or second QoS information corresponding to the transmission of the sensing service.

[0139] Alternatively, in other embodiments, the request message may include at least one of a first QoS information and / or a second QoS information determined at SF-CP 404, which can then be directly used to determine a first priority for sensing execution and / or a second priority for communication transmission.

[0140] Alternatively, in some embodiments, the request message may include only a request for a sensed service to RAN node 402, without including specific sensed service QoS information. In these embodiments, upon receiving the request message, RAN node 402 may determine at least one of the QoS information corresponding to the sensed service, such as 5QI, priority level, ARP, QoS rules, and QFI. Then, it may further determine at least one of first QoS information corresponding to the execution of the sensed service and second QoS information corresponding to the transmission of the sensed service.

[0141] Then, at 445, the second network element 120 can determine whether to execute and / or transmit the sensing service based on the determined or received first QoS information and / or second QoS information. If the sensing service has a higher priority than the communication service, the sensing service is executed or scheduled first, and the communication service is rejected or not executed first; conversely, if the communication service has a higher priority, the communication service is executed first.

[0142] Specifically, in some implementations, the second network element 120 may determine a first priority for the execution of the sensed service based on first QoS information, and / or determine a second priority for the transmission of the sensed service based on second QoS information. Furthermore, the second network element 120 may also determine a third priority for the communication service, for example, based on QoS information associated with the communication service received from the AMF (e.g., via a PDU session establishment request).

[0143] Optionally, at 440-2, SF-CP 404 may send a request message to UE 401 for requesting the execution and / or transmission of a sense service, such request message may correspond to, for example, a request message for requesting the execution and / or transmission of a sense service. Figure 2A The third request message 234-2 in the middle, or Figure 2B The fifth request message 234-2' in the protocol. In some embodiments, this request message can be sent from SF-CP 404 to UE 401 via an intermediate network node (such as AMF). In other embodiments, the request message can also be sent directly from SF-CP 404 to UE 401.

[0144] In some embodiments, the request message may include QoS information corresponding to the sensing service, such as 5QI (sensing 5QI), priority level, ARP (sensing ARP), etc. In these embodiments, after receiving the request message, at 445, UE 401 may determine first QoS information corresponding to the execution of the sensing service, and / or second QoS information corresponding to the transmission of the sensing service.

[0145] Alternatively, in other embodiments, the request message may include at least one of a first QoS information and / or a second QoS information determined at SF-CP 404, which can then be directly used to determine a first priority for sensing execution and / or a second priority for communication transmission.

[0146] Alternatively, in some embodiments, the request message may only include a request for a sensed service for UE 401, without including specific sensed service QoS information. In these embodiments, after receiving the request message, UE 401 can determine at least one of the QoS information corresponding to the sensed service, such as 5QI, priority level, ARP, QoS rules, and QFI. Then, it can further determine at least one of first QoS information corresponding to the execution of the sensed service and second QoS information corresponding to the transmission of the sensed service.

[0147] Then, at 445, UE 401 can determine whether to execute and / or transmit a sensed service based on the determined or received first QoS information and / or second QoS information. If the sensed service has a higher priority than the communication service, the sensed service is executed or scheduled first, and the communication service is rejected or not executed first; conversely, if the communication service has a higher priority, the communication service is executed first.

[0148] Specifically, in some implementations, UE 401 may determine a first priority for the execution of the sensed service based on first QoS information, and / or determine a second priority for the transmission of the sensed service based on second QoS information. Furthermore, UE 401 may also determine a third priority for the communication service, for example, based on QoS information associated with the communication service received from the AMF (e.g., via a PDU session establishment request).

[0149] Note that the specific information contained in the request message sent to RAN node 402 in step 440-1 and the request message sent to UE 401 in step 440-2 may be the same or different, depending on the specific implementation. Furthermore, it should be noted that depending on the different transmission modes of the sensed signal (e.g., UE self-transmission and reception, first UE transmission and second UE reception, RAN node self-transmission and reception, first RAN node transmission and second RAN node reception, UE transmission and RAN node reception, and RAN node transmission and UE reception, etc.), SF-CP 404 may send the request message only to RAN node 402, only to UE 401, or to both UE and RAN. Alternatively, in other scenarios, SF-CP 404 may send multiple request messages to multiple RAN nodes or multiple UEs, and this disclosure does not limit this.

[0150] As can be seen, in the above process 400, the sensing service requirement can be broken down into first QoS information corresponding to sensing execution and / or second QoS information corresponding to sensing transmission at different stages and by different network elements (such as RAN nodes, UEs, SF-CP, or SMF). Thus, the RAN node and / or UE can determine the priority of execution / transmission for sensing based on the first QoS information and / or the second QoS information, and thereby decide whether to execute the sensing service. The following... Figures 5 to 7 An example procedure for determining first QoS information and / or second QoS information is described.

[0151] Figure 5 Exemplary communication flows of some embodiments of this disclosure are shown. For example... Figure 5 As shown, process 500 involves UE 501, RAN node 502, SMF 503, SF-CP (or SF in some embodiments) 504, and the perceived service consumer (or requester) 505. UE 501 can be as follows: Figure 1A The example of terminal device 140 shown can be RAN node 502 as follows: Figure 1A The example of the second network element 120 shown, SMF 503 can be as follows: Figure 1A The example of the third network element 130 shown, and the SF-CP 504 can be as follows: Figure 1A An example of the first network element 110 shown.

[0152] At point 510, SF-CP 504 can receive a sensed service request message from sensed service consumer 505. Alternatively, in some embodiments, SF-CP 504 can also receive the sensed service request message from UE 501. This step may correspond, for example, to... Figure 2A Step 210 Figure 2BStep 210' or Figure 4 Step 420. The content of this sensing service request message can be referred to the previous introduction, and will not be repeated here. SF-CP 504 can determine the sensing participants (such as RAN nodes, UEs) and the transmission mode of sensing signals (such as RAN sending and UE receiving, first UE sending and second UE receiving, RAN node self-transmitting and receiving, first RAN node sending and second RAN node receiving, UE sending and RAN node receiving, and RAN node sending and UE receiving), etc.

[0153] At step 515, SF-CP 504 can determine, for example, first QoS information corresponding to the execution of the sensed service based on sensed service-related subscription information received from the PCF. This first QoS information may include one or more of the following associated with the execution of the sensed service: 5QI, priority level, ARP, QoS rules, and QFI. Subsequently, at step 520-1, SF-CP 504 can send a request message to RAN node 502 requesting the execution of the sensed service. In some embodiments, this request message can be sent from SF-CP 504 to RAN node 502 via an intermediate network node (such as AMF). In other embodiments, the request message can also be sent directly from SF-CP 504 to RAN node 502. Alternatively, SF-CP 504 can also send the request message directly or indirectly (e.g., via AMF) to UE 501.

[0154] At point 525, RAN node 502 and / or UE 501 can determine whether to perform a sensing service or a communication service based on the request message. As mentioned earlier, the execution priority of communication and sensing can be compared based on at least one parameter among those used for sensing and communication, such as ARP, priority level, QFI, and 5QI. For example, if the execution priority of sensing is determined to be higher than that of communication, then sensing can be performed. This can be illustrated using a RAN-transmitter-UE-receiver mode as an example. For instance, after determining to perform sensing, RAN 502 can transmit a sensing signal, which is then directed to the target object. Upon receiving the signal, the target object will reflect it back to UE 501. After receiving the reflected sensing signal, UE 501 can acquire relevant sensing measurement data. Subsequently, UE 501 can further process this data, perform calculations, and ultimately generate sensing results or data.

[0155] After the sensing operation is completed, at 530, UE 501 can send a sensing session establishment request message to SMF 503. This message may include sensing-related information, such as UE ID, sensing ID, or sensing task ID. Then, at 535, this message is forwarded by SMF 503 to SF-CP 504. In some embodiments, the sensing session establishment request message may also be sent directly from UE 501 to SF-CP 504. At 540, based on the received sensing session establishment request message, SF-CP 504 can determine the second QoS information corresponding to the sensing service transmission. For example, the second QoS information may include information associated with the sensing service transmission, such as one or more of 5QI, priority level, ARP, QoS rules, and QFI. Then, at 545, SF-CP 504 can send the second QoS information to SMF 503 via a sensing session establishment accept message. SMF 503 can then forward the second QoS information to RAN node 502 via a sensing session establishment accept message at 550-1. Alternatively, SF-CP 504 can directly send the second QoS information to RAN node 502 via a sense session establishment accept message. Furthermore, SMF 503 can also send the second QoS information to UE 501 at 550-2 directly or indirectly (e.g., via at least one of SMF 503 and AMF) via a sense session establishment accept message.

[0156] At point 555, RAN 502 and / or UE 501 can determine the priority relationship between the sensed transmission and the communication service based on the second QoS information and the QoS information corresponding to the communication, and thus determine whether to perform the sensed service transmission. As mentioned above, the priority relationship between the execution of communication and the sensed transmission can be compared based on at least one of the parameters used for sensed transmission, such as ARP, priority level, QFI, and 5QI. For example, if it is determined that the priority of the sensed transmission is higher than the priority of the communication execution, then it can be determined to perform the sensed transmission.

[0157] Alternatively, in some implementations, at 515, SF-CP 504 may not determine the QoS information related to sensing, but instead only send a sensing service request to at least one of RAN 502 and / or UE 501. In this case, at 530, UE 501 may send a sensing session establishment request message to SMF 503, which may include only information for requesting sensing services, but not information related to the sensing to be performed. Then, at 535, the message is forwarded by SMF 503 to SF-CP 504. In other embodiments, the sensing session establishment request message may also be sent directly from UE 501 to SF-CP 504. At point 540, based on the received sensing session establishment request message, SF-CP 504 can determine first QoS information corresponding to the execution of the sensing service and second QoS information corresponding to the transmission of the sensing service. For example, the first QoS information and / or the second QoS information may include information associated with the execution and / or transmission of the sensing service, such as one or more of 5QI, priority level, ARP, QoS rules, and QFI. Then, at point 545, SF-CP 504 can send the first QoS information and / or the second QoS information to SMF 503 via a sensing session establishment accept message. SMF 503 can then forward the first QoS information and / or the second QoS information to RAN node 502 via a sensing session establishment accept message at point 550-1. Alternatively, SF-CP 504 can directly send the first QoS information and / or the second QoS information to RAN node 502 via a sensing session establishment accept message. In addition, SMF 503 can also send the first QoS information and / or the second QoS information to UE 501 directly or indirectly (e.g., via at least one of SMF 503 and AMF) at 550-2 through a sense session establishment accept message.

[0158] In this implementation, at point 555, RAN 502 and / or UE 501 can determine the priority relationship between the execution / transmission of the sensed service and the communication service based on the first QoS information, the second QoS information, and the QoS information corresponding to the communication, and thus determine whether to execute / transmit the sensed service. Alternatively, RAN node 502 and / or UE 501 can first determine whether to execute the sensed service based on the first QoS information and the QoS information corresponding to the communication. If the sensed service is executed, RAN node 502 and / or UE 501 can subsequently determine whether to transmit the sensed service based on the second QoS information and the QoS information corresponding to the communication. As mentioned above, the priority relationship between the execution of the communication and the transmission of the sensed service can be compared based on at least one of the parameters used for sensed and communication, such as ARP, priority level, QFI, and 5QI. For example, if it is determined that the priority of the sensed transmission is higher than the priority of the communication execution, then the execution of the sensed transmission can be determined.

[0159] Alternatively, in some implementations, at step 515, SF-CP 504 can determine first QoS information and second QoS information, which can then be included in the request message sent to RAN 502 and / or UE 501. At step 525, RAN node 402 and / or UE 401 can determine whether to execute and / or transmit the sensing service based on the first QoS information and / or the second QoS information, as well as the QoS information corresponding to the communication. Alternatively, RAN node 402 and / or UE 401 can first determine whether to execute the sensing service based on the first QoS information and the QoS information corresponding to the communication. If the sensing service is executed, RAN node 402 and / or UE 401 can subsequently determine whether to transmit the sensing service based on the second QoS information and the QoS information corresponding to the communication. In this case, steps 530 to 555 can be omitted.

[0160] Figure 6 Exemplary communication flows of some embodiments of this disclosure are shown. For example... Figure 6 As shown, process 600 involves UE 601, RAN node 602, SMF 603, SF-CP (or SF in some embodiments) 604, and the perceived service consumer (or requester) 605. UE 601 can be as follows: Figure 1A The example of terminal device 140 shown can be RAN node 602 as follows: Figure 1A The example of the second network element 120 shown, SMF 603 can be as follows: Figure 1A The example of the third network element 130 shown, and the SF-CP 604 can be as follows: Figure 1AAn example of the first network element 110 shown.

[0161] Note that steps 610 to 635 and steps 650-1 to 655 of process 600 correspond to steps 510 to 535 and steps 550-1 to 555 of process 500. See details [link to documentation]. Figure 5 The corresponding steps are not described here. The difference is that after receiving the sensing session establishment request message at 630, at step 640, SF-CP 604 may not determine the second QoS information about the sensing transmission, but directly send a sensing session establishment acceptance message to SMF 603. This sensing session establishment acceptance message may include sensing-related information, such as UE ID, sensing ID, or sensing task ID.

[0162] Then, at 645, after receiving the sensing session establishment request message, SMF 603 can determine the second QoS information corresponding to the transmission of the sensing service. For example, the second QoS information may include one or more of the information associated with the transmission of the sensing service, such as 5QI, priority level, ARP, QoS rules, and QFI.

[0163] Then, at 650-1, SMF 503 can send the second QoS information to RAN node 602 via a sense session establishment accept message. Furthermore, at 650-2, SMF 603 can also send the second QoS information directly or indirectly (e.g., via AMF) to UE 501 via a sense session establishment accept message.

[0164] At point 655, RAN 602 and / or UE 601 can determine the priority relationship between the sensed transmission and the communication service based on the second QoS information and the QoS information corresponding to the communication, and thus determine whether to perform the sensed service transmission. As mentioned above, the priority relationship between the execution of communication and the sensed transmission can be compared based on at least one of the parameters used for sensed transmission, such as ARP, priority level, QFI, and 5QI. For example, if it is determined that the priority of the sensed transmission is higher than the priority of the communication execution, then it can be determined to perform the sensed transmission.

[0165] Alternatively, in some implementations, SF-CP 604 may not determine the QoS information related to sensing, but instead only send a sensing service request to at least one of RAN 602 and / or UE 601. Therefore, steps 615 and 625 can be omitted. In this case, at 640, the sensing session establishment accept message sent from SF-CP 604 to SMF 603 may only include the sensing service request. Based on the receipt of this sensing session establishment request message, at 645, SMF 603 can determine first QoS information corresponding to the execution of the sensing service and second QoS information corresponding to the transmission of the sensing service. For example, the first QoS information and / or second QoS information may include information associated with the execution and / or transmission of the sensing service, such as one or more of 5QI, priority level, ARP, QoS rules, and QFI. Then, SMF 603 can subsequently forward the first QoS information and / or second QoS information to RAN node 602 via the sensing session establishment accept message at 650-1. In addition, SMF 603 can also send the first QoS information and / or the second QoS information directly or indirectly (e.g., via AMF) to UE 601 at 650-2 via a sense session establishment accept message.

[0166] In this implementation, at point 655, RAN 602 and / or UE 601 can determine the priority relationship between the execution / transmission of the sensed service and the communication service based on the first QoS information, the second QoS information, and the QoS information corresponding to the communication, and thus determine whether to execute / transmit the sensed service. Alternatively, RAN node 602 and / or UE 601 can first determine whether to execute the sensed service based on the first QoS information and the QoS information corresponding to the communication. If the sensed service is executed, RAN node 602 and / or UE 601 can subsequently determine whether to transmit the sensed service based on the second QoS information and the QoS information corresponding to the communication. As mentioned above, the priority relationship between the execution of the communication and the transmission of the sensed service can be compared based on at least one of the parameters used for sensed and communication, such as ARP, priority level, QFI, and 5QI. For example, if it is determined that the priority of the transmission of the sensed service is higher than the priority of the execution of the communication service, then it can be determined to execute the transmission of the sensed service.

[0167] Figure 7 Exemplary communication flows of some embodiments of this disclosure are shown. For example... Figure 7 As shown, process 700 involves UE 701, RAN node 702, SMF 703, SF-CP (or SF in some embodiments) 704, and the perceived service consumer (or requester) 705. UE 701 can be as follows: Figure 1AThe example of terminal device 140 shown can be RAN node 702 as follows: Figure 1A The example of the second network element 120 shown, SMF 703 can be as follows: Figure 1A The example of the third network element 130 shown is illustrated, and the SF-CP 704 can be as follows: Figure 1A An example of the first network element 110 shown.

[0168] The descriptions of steps 710 to 720-2 in process 700 can be found in steps 510 to 520-2 of process 500 and steps 610 to 620-2 of process 600, and will not be repeated here. The difference lies in that at step 740 of process 700, UE 701 can directly send a sensing session establishment request message to SMF 703, or send it via AMF to SMF 703, without needing to forward it via SF-CP 704. Then, at step 735, after receiving the sensing session establishment request message, SMF 703 determines the second QoS information corresponding to the transmission of the sensing service. For example, this second QoS information may include information associated with the transmission of the sensing service, such as one or more of 5QI, priority level, ARP, QoS rules, and QFI.

[0169] Alternatively, in some implementations, SF-CP 704 may not determine the QoS information related to sensing, but instead only send a sensing service request to at least one of RAN 702 and / or UE 701. Therefore, steps 715 and 725 can be omitted. In this case, at 730, the sensing session establishment acceptance message sent from UE 701 to SMF 703 may only include the sensing service request. Based on receiving the sensing session establishment request message, at 735, SMF 703 can determine first QoS information corresponding to the execution of the sensing service and second QoS information corresponding to the transmission of the sensing service. For example, the first QoS information and / or the second QoS information may include information associated with the execution and / or transmission of the sensing service, such as one or more of 5QI, priority level, ARP, QoS rules, and QFI.

[0170] The subsequent steps 740-1 to 745 can be referred to the descriptions of steps 550-1 to 555 in process 500 and steps 650-1 to 655 in process 600, and will not be repeated here.

[0171] In some implementations, to notify and respond to failures of sensing or communication services, promptly identify and handle service failures, and thus optimize network resource utilization, after determining the priorities of sensing and communication services, the RAN node needs to send a notification message of the failure of the sensing or communication service to the corresponding network element, such as... Figure 8 As shown in the image.

[0172] Figure 8 Exemplary communication flows of some embodiments of this disclosure are shown. For example... Figure 8 As shown, process 800 involves service consumer 801, RAN node 802, AMF 803, SMF 804, and SF-CP (or SF in some embodiments) 805. Figure 8 In this context, RAN node 802 can be as follows: Figure 1A The example of the second network element 120 shown, SMF 804 can be as follows: Figure 1A The example of the third network element 130 shown, SF-CP 805 can be as follows: Figure 1A An example of the first network element 110 shown.

[0173] like Figure 8 As shown, at 810, RAN node 802 can obtain first QoS information and / or second QoS information corresponding to the execution and transmission of the sensed service from service consumer 801 (here, the sensed service consumer, such as a UE, or an AF associated with the sensed service) through a sensed service request message. Alternatively, RAN node 802 can determine the first QoS information and / or second QoS information based on the sensed service request message. Furthermore, RAN node 802 can also obtain third QoS information corresponding to the communication service through a PDU session establishment request message. Then, RAN node 802 can determine the priority relationship between the execution and / or transmission of the sensed service and the communication service based on the determined first QoS information and / or second QoS information, and the third QoS information, to determine whether to execute and / or transmit the sensed service. If the priority of the sensed service is higher than that of the communication service, the sensed service is executed or scheduled first, and the communication service is rejected or not executed first; conversely, if the priority of the communication service is higher, the communication service is executed first. The process for obtaining or determining the first QoS information and the second QoS information, and the process for determining whether to execute the sensed service, described above, can be referred to as above. Figures 4 to 7 The description in the text will not be repeated here.

[0174] Next, depending on the comparison results, process 800 may include the following two options.

[0175] In option 1, the business consumer 801 can be as follows: Figure 1AExample of terminal device 140 shown. At 815, RAN node 802 determines that the execution and / or transmission priority of the sensing service is higher than the priority of the communication service, or that a new high-priority sensing service has emerged and resources are insufficient to support the communication service simultaneously. In this case, the RAN may prioritize the execution of the sensing service and send (825) a first notification message to SMF 804 via forwarding (820) from AMF 803 to notify of the failure of the communication service. Alternatively, the first notification message may also be sent directly from RAN node 802 to SMF 804 without forwarding via AMF 803. The first notification message may contain information that can be used to indicate the obstruction of the communication service execution, such as the affected PDU session ID and / or UE ID. In addition, the first notification message may selectively include the specific reason for the failure of the communication service execution, such as the priority of the sensing service execution, or that the ongoing communication service associated with the PDU session ID and / or UE ID has been preempted by the sensing service. Furthermore, the message can also explicitly indicate which specific sensing service is preempting the ongoing communication service; that is, the message can include an identifier corresponding to that sensing service (e.g., sensing ID or sensing task ID).

[0176] Optionally, SMF 804 may then send a PDU session establishment response message (835) to service consumer 801 via forwarding (830) of AMF 803 to notify service consumer 801 that the communication service is currently unavailable. Alternatively, the PDU session establishment response message may be sent directly to service consumer 801 without forwarding via AMF 803. The information carried in the PDU session establishment response message may be the same as that contained in the first notification message received by SMF 804 at 825, or may include other necessary information to ensure that the UE can fully understand the reason for the communication service establishment failure and its priority relationship with the perceived service.

[0177] Alternatively, in option 2, business consumer 801 can refer to the business-aware requester, as previously described, which can be, for example... Figure 1AThe terminal device 140 shown may be an AF associated with the sensing service. At 815', RAN node 802 determines that the execution and / or transmission priority of the sensing service is lower than the priority of the communication service, or that a new high-priority communication service has emerged and resources are insufficient to support the sensing service simultaneously. In this case, the RAN may prioritize the execution of the communication service and send (825') a second notification message to SF-CP 805 via forwarding (820') of AMF 803 to notify of the sensing service failure. Alternatively, the second notification message may be sent directly to SF-CP 805 without forwarding via AMF 803. The second notification message may contain information that can be used to indicate the obstruction of the sensing service execution, such as the affected sensing ID or sensing task ID. In addition, the second notification message may selectively include the specific reason for the service failure, such as prioritizing the execution of the communication service, or the sensing service being executed corresponding to the sensing ID or sensing task ID being preempted by the communication service. Furthermore, the message can also explicitly indicate which specific communication service is preempting the currently executing sensing service; that is, the message can include an identifier corresponding to that communication service (e.g., PDU session ID).

[0178] Optionally, SF-CP 805 can then send a perceived service response message (835') to service consumer 801 via forwarding (830') of AMF 803 to notify service consumer 801 that the perceived service is currently unable to be executed. Alternatively, the perceived service response message can also be sent directly to service consumer 801 without forwarding via AMF 803. The information carried in the perceived service response message may be the same as that contained in the second notification message received by SF-CP 805 at 825', or may include other necessary information to ensure that the UE can fully understand the reason for the perceived service establishment failure and its priority relationship with the communication service.

[0179] The above mechanisms facilitate the immediate notification and feedback process for perceived business and communication service failures, enabling rapid identification of service interruptions or failures and promoting timely fault handling.

[0180] Figure 9 A schematic flowchart illustrating the implementation of some embodiments of this disclosure at a first network element is shown. For example... Figure 9 As shown, process 900 can be executed by the first network element, and the first network element executing process 900 can be, for example, such as... Figure 1AThe first network element 110 shown, or the chip, module, or assembly within the first network element 110, etc. Here, we will use the execution of process 900 by the first network element as an example for illustration. In block 910, the first network element receives a first request message from the sensing service consumer for requesting a sensing service. In block 920, based on the received first request message, the first network element determines QoS information corresponding to the sensing service. In block 930, the first network element sends a second request message for requesting at least one of the execution or transmission of the sensing service from a second network element or terminal device. In some embodiments, process 900 may also include elements combined with those described in this disclosure. Figures 2A to 8 Other operations described at the first network element.

[0181] Figure 10 Schematic flowcharts illustrating the implementation of some embodiments of this disclosure at a second network element are shown. For example... Figure 10 As shown, process 1000 can be executed by a second network element. The second network element executing process 1000 can be, for example, such as... Figure 1A The second network element 120 shown, or the chip, module, or assembly within the second network element 120, etc. Here, we will illustrate with an example of the second network element executing process 1000. In block 1010, the second network element receives a request message for requesting at least one of the execution or transmission of a sensing service. In block 1020, based on the request message, the second network element determines the priority associated with the sensing service. In some embodiments, process 1000 may further include elements combined with the embodiments of this disclosure. Figures 2A to 8 Other operations performed at the second network element are described.

[0182] Figure 11 Schematic flowcharts illustrating the implementation of some embodiments of this disclosure at a third network element are shown. For example... Figure 11 As shown, process 1100 can be executed by a third network element. The third network element executing process 1100 can be, for example, such as... Figure 1A The third network element 130 shown, or the chip, module, or assembly within the third network element 130, etc. Here, we will use the execution of process 1100 by the third network element as an example for explanation. In block 1110, the third network element receives QoS information corresponding to the sensing service. In block 1120, based on the received QoS information, the third network element sends a request message to request the second network element or terminal device to perform at least one of the execution or transmission of the sensing service. In some embodiments, process 1100 may further include, in conjunction with embodiments of this disclosure... Figures 2A to 8 Other operations described at the third network element.

[0183] Figure 12 Schematic flowcharts illustrating the implementation of some embodiments of this disclosure at a third network element are shown. For example... Figure 12As shown, process 1200 can be executed by a terminal device, and the terminal device executing process 1200 can be, for example, Figure 1A The terminal device 140 shown, or the chip, module, or assembly within the terminal device 140, etc., will be described here as an example of the terminal device executing process 1200. In block 1210, the terminal device receives a request message for requesting at least one of the execution or transmission of a sensing service. In block 1220, based on the request message, the terminal device determines the priority associated with the sensing service. In some embodiments, process 1200 may further include elements incorporated in this disclosure embodiment. Figures 2A to 8 Other operations described that are performed at the terminal device.

[0184] Figure 13This is a block diagram of the device 1300 that can be used to implement some embodiments of the present application. In some embodiments, device 1300 may be an element of a communication network infrastructure, such as a base station (e.g., NodeB, evolved NodeB (eNodeB or eNB), next-generation NodeB (sometimes called next-generation NodeB, gNodeB or gNB), home subscriber server (HSS), gateway (GW), such as packet gateway (PGW) or serving gateway (SGW), or various other nodes or functions within a core network (CN) or Public Land Mobility Network (PLMN). In other embodiments, device 1300 may be a device connected to the network infrastructure via a wireless interface, such as a mobile phone, smartphone, or other such device that can be classified as user equipment (UE). In some embodiments, device 1300 may be machine-type communication (M2C). Communications (MTC) devices (also known as machine-to-machine (M2M) devices), or another type of device that, although not providing direct service to a user, can be classified as a UE. In some embodiments, device 1300 may be a roadside unit (RSU), a vehicle UE (V-UE), a pedestrian UE (P-UE), or an infrastructure UE (I-UE). In some scenarios, device 1300 may also be referred to as a mobile device, a term intended to reflect a device connected to a mobile network, regardless of whether the device itself is designed for or capable of being mobile. A particular device may utilize all or only a subset of the components shown, and the level of integration may vary depending on the device. Furthermore, device 1300 may contain multiple instances of components, such as multiple processors, memories, transmitters, receivers, etc.

[0185] Device 1300 typically includes a processor 1302, such as a central processing unit (CPU), and may further include a dedicated processor, such as a graphics processing unit (GPU) or other such processor, memory 1304, a network interface 1306, and a bus 1308 for connecting the components of device 1300. Optionally, device 1300 may also include components such as a mass storage device 1310, a video adapter 1312, and an I / O interface 1316 (shown in dashed lines).

[0186] Memory 1304 may include any type of non-transitory system memory readable by processor 1302, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), or combinations thereof. In one embodiment, memory 1304 may include more than one type of memory, such as ROM used at startup and DRAM used for program and data storage during program execution. Bus 1308 may be one or more of a plurality of bus architectures of any type, including a memory bus or memory controller, a peripheral bus, or a video bus.

[0187] Device 1300 may also include one or more network interfaces 1306, which may include at least one of wired network interfaces and wireless network interfaces. For example... Figure 13 As shown, network interface 1306 may include a wired network interface for connecting to network 1322, and may also include a wireless access network interface 1320 for connecting to other devices via a wireless link. When device 1300 is a network infrastructure element, the wireless access network interface 1320 may be omitted for nodes or functions that are elements of a PLMN rather than elements at the wireless edge. When device 1300 is infrastructure at the wireless edge of the network, both wired and wireless network interfaces may be included. When device 1300 is a wirelessly connected device, such as a user equipment, the wireless access network interface 1320 may be present and may be supplemented by other wireless interfaces such as a WiFi network interface. Network interface 1306 allows device 1300 to communicate with remote entities such as those connected to network 1322.

[0188] Mass storage 1310 may include any type of non-transitory storage device configured to store data, programs, and other information and make the data, programs, and other information accessible via bus 1308. Mass storage 1310 may include, for example, one or more of a solid-state drive, hard disk drive, disk drive, or optical disk drive. In some embodiments, mass storage 1310 may be located remotely from device 1300 and may be accessed using a network interface such as interface 1306. In the illustrated embodiment, mass storage 1310 is distinct from the memory 1304 that includes it, and mass storage 1310 typically performs storage tasks compatible with higher latency but typically provides low or no fluctuation. In some embodiments, mass storage 1310 may be integrated with heterogeneous memory 1304.

[0189] Optional video adapter 1312 and I / O interface 1316 (shown in dashed lines) provide interfaces for coupling device 1300 to external input and output devices. Examples of input and output devices include a display 66 coupled to video adapter 1312 and an I / O device 1318, such as a touchscreen, coupled to I / O interface 1316. Other devices may be coupled to device 1300 and may utilize additional or fewer interfaces. For example, a serial interface such as Universal Serial Bus (USB) (not shown) may be used to provide interfaces for external devices. Those skilled in the art will understand that in embodiments where device 1300 is part of a data center, I / O interface 1316 and video adapter 1312 may be virtualized and provided via network interface 1306.

[0190] Figure 14 This is a schematic diagram of the structure of a device 1400 according to some embodiments of this application. For example... Figure 14 As shown, the device 1400 includes a receiving unit 1402, a determining unit 1404, and a transmitting unit 1406. The device 1400 can be applied to applications such as... Figure 1A The communication system shown can implement any of the methods provided in the preceding embodiments (e.g., method 900). Optionally, the physical manifestation of device 1400 can be a communication device, such as... Figure 1AThe first network element 110 is shown in the diagram. Alternatively, device 1400 can be other devices capable of implementing the functions of a communication device, such as a processor or chip inside the communication device. Specifically, device 1400 can be a programmable chip, such as a field-programmable gate array (FPGA), a complex programmable logic device (CPLD), an application-specific integrated circuit (ASIC), or a system on a chip (SOC).

[0191] In some embodiments, the receiving unit 1402 may be configured to receive a first request message from a sensing service consumer for requesting a sensing service. The determining unit 1404 may be configured to determine QoS information corresponding to the sensing service based on the received first request message. The sending unit 1406 may be configured to send a second request message for requesting at least one of the execution or transmission of a sensing service by a second network element or terminal device.

[0192] In some other embodiments, the apparatus 1400 may include various other units or modules that can be configured to perform the various operations or functions described with respect to the foregoing method embodiments. Specific details can be obtained by referring to the detailed description of the foregoing method embodiments, and will not be repeated here.

[0193] Figure 15 This is a schematic diagram of the structure of a device 1500 according to some embodiments of this application. For example... Figure 15 As shown, the device 1500 includes a receiving unit 1502 and a determining unit 1504. The device 1500 can be applied to applications such as... Figure 1A The communication system shown can implement any of the methods provided in the foregoing embodiments (e.g., method 1000). Optionally, the physical manifestation of device 1500 can be a communication device, such as... Figure 1AThe second network element 120 is shown in the diagram. Alternatively, device 1500 can be other devices capable of implementing the functions of a communication device, such as a processor or chip inside the communication device. Specifically, device 1500 can be a programmable chip, such as a field-programmable gate array (FPGA), a complex programmable logic device (CPLD), an application-specific integrated circuit (ASIC), or a system on a chip (SOC).

[0194] In some embodiments, the receiving unit 1502 may be configured to receive a request message for requesting at least one of the execution or transmission of a sensing service. The determining unit 1504 may be configured to determine a priority associated with the sensing service based on the request message.

[0195] In some embodiments, the apparatus 1500 may include various other units or modules that can be configured to perform the various operations or functions described with respect to the foregoing method embodiments. Specific details can be obtained by referring to the detailed description of the foregoing method embodiments, and will not be repeated here.

[0196] Figure 16 This is a schematic diagram of the structure of device 1600 according to some embodiments of this application. For example... Figure 16 As shown, the device 1600 includes a receiving unit 1602 and a transmitting unit 1604. The device 1600 can be applied to, for example... Figure 1A The communication system shown can implement any of the methods provided in the foregoing embodiments (e.g., method 1100). Optionally, the physical manifestation of device 1600 can be a communication device, such as... Figure 1A The third network element 130 shown is illustrated. Alternatively, device 1600 can be other devices capable of implementing the functions of a communication device, such as a processor or chip within the communication device. Specifically, device 1600 can be a programmable chip, such as a field-programmable gate array (FPGA), a complex programmable logic device (CPLD), an application-specific integrated circuit (ASIC), or a system on a chip (SOC).

[0197] In some embodiments, the receiving unit 1602 may be configured to receive QoS information corresponding to the sensing service. The sending unit 1604 may be configured to, based on the received QoS information, send a request message for requesting the second network element or terminal device to perform at least one of the execution or transmission of the sensing service.

[0198] In some embodiments, the apparatus 1600 may include various other units or modules that can be configured to perform the various operations or functions described with respect to the foregoing method embodiments. Specific details can be obtained by referring to the detailed description of the foregoing method embodiments, and will not be repeated here.

[0199] Figure 17 This is a schematic diagram of the structure of device 1700 according to some embodiments of this application. For example... Figure 17 As shown, the device 1700 includes a receiving unit 1702 and a determining unit 1704. The device 1700 can be applied to, for example... Figure 1A The communication system shown can implement any of the methods provided in the preceding embodiments (e.g., method 1200). Optionally, the physical manifestation of device 1700 can be a communication device, such as... Figure 1A The terminal device 140 shown is an example. Alternatively, device 1700 can be other devices capable of implementing the functions of a communication device, such as a processor or chip within the communication device. Specifically, device 1700 can be a programmable chip, such as a field-programmable gate array (FPGA), a complex programmable logic device (CPLD), an application-specific integrated circuit (ASIC), or a system-on-a-chip (SOC).

[0200] In some embodiments, the receiving unit 1702 may be configured to receive a request message for requesting at least one of the execution or transmission of a sensing service. The determining unit 1704 may be configured to determine a priority associated with the sensing service based on the request message.

[0201] In some embodiments, apparatus 1700 may include various other units or modules that may be configured to perform the various operations or functions described with respect to the foregoing method embodiments. Specific details can be obtained by referring to the detailed description of the foregoing method embodiments, and will not be repeated herein.

[0202] It should be noted that the module division in the above embodiments of this application is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods. Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, exist as separate physical units, or be integrated into one unit by two or more units. The integrated units described above can be implemented in hardware or as software functional units.

[0203] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, or all or part of it, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0204] Based on the above embodiments, this application also provides a computer program that, when run on a computer, causes the computer to execute any of the methods provided in the above embodiments.

[0205] Based on the above embodiments, this application also provides a computer-readable storage medium storing a computer program. When the computer program is executed by a computer, it causes the computer to perform any of the methods provided in the above embodiments. The storage medium can be any available medium that can be accessed by a computer. By way of example, but not limited to, a computer-readable medium may include RAM, ROM, electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code having the form of instructions or data structures and that can be accessed by a computer.

[0206] Based on the above embodiments, this application also provides a chip for reading a computer program stored in a memory and implementing any of the methods provided in the above embodiments.

[0207] Based on the above embodiments, this application provides a chip system including a processor for supporting a computer device in implementing the functions involved in the communication devices in the above embodiments. In one possible design, the chip system further includes a memory for storing necessary programs and data of the computer device. This chip system may be composed of chips or may include chips and other discrete components.

[0208] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0209] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or one or more blocks of the block diagrams.

[0210] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0211] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

[0212] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of protection of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A communication method applied to a first network element, the method comprising: Receive the first request message from the sensing service consumer to request the sensing service; Based on receiving the first request message, determine the Quality of Service (QoS) information corresponding to the perceived service; as well as Send a second request message for requesting at least one of the execution or transmission of sensing services of a second network element or terminal device.

2. The method according to claim 1, wherein the second request message comprises: The QoS information and the requirements of the sensing service.

3. The method of claim 1, wherein the second request message comprises at least one of the following: First QoS information corresponding to the execution of the sensing service, wherein the first QoS information is used to indicate a first priority for the execution of the sensing service; or The second QoS information corresponding to the transmission of the sensing service, the second QoS information being used to indicate the second priority of the transmission of the sensing service.

4. The method according to claim 3, further comprising: Based on receiving the first request message, determine at least one of the first QoS information or the second QoS information.

5. The method according to any one of claims 1 to 4, wherein the first request message includes at least one of the following: an identifier of the sensing service, a type of the sensing service, and a requirement of the sensing service.

6. The method according to any one of claims 2 to 5, wherein the requirement of the sensing service includes at least one of the following: Precision of perceived business operations; Perceive the latency of the service; or The area where the business is perceived.

7. The method according to any one of claims 1 to 6, further comprising: In cases where communication services are executed before sensing services, or where a sensing service in progress is preempted by a communication service, a notification message indicating that the sensing service has failed is received from the second network element.

8. The method of claim 7, wherein the notification message comprises: Identifiers of sensing services that have not been executed or have been preempted; or The reason value for sensing business failure.

9. The method according to any one of claims 1 to 8, wherein the sensing service consumer is one of the terminal device or application function (AF).

10. The method according to any one of claims 1 to 9, wherein: The first network element includes a sensing function (SF); or The second network element includes the RAN node.

11. A communication method applied to a second network element, the method comprising: Receive a request message for at least one of the execution or transmission of a request-aware service; as well as Based on the request message, the priority associated with the sensing service is determined.

12. The method of claim 11, wherein determining the priority associated with the sensing service includes at least one of the following: Based on the first QoS information corresponding to the execution of the sensing service, a first priority for the execution of the sensing service is determined; or Based on the second QoS information corresponding to the transmission of the sensing service, a second priority for the transmission of the sensing service is determined.

13. The method of claim 11 or 12, wherein the request message comprises: The Quality of Service (QoS) information corresponding to the perceived service, and the requirements of the perceived service.

14. The method of claim 13, further comprising: Based on the request message, at least one of the first QoS information or the second QoS information is determined.

15. The method of claim 13 or 14, wherein the requirement of the sensing service includes at least one of the following: Precision of perceived business operations; Perceive the latency of the service; or The area where the business is perceived.

16. The method of claim 11 or 12, wherein the request message includes at least one of the first QoS information or the second QoS information.

17. The method according to any one of claims 12 to 16, further comprising: Based on the first priority, the second priority, and the third priority for communication services, it is determined whether to execute the sensing service and the transmission of the sensing service.

18. The method according to any one of claims 12 to 16, further comprising: Based on the first priority and the third priority used for communication services, it is determined whether to execute the sensing service.

19. The method of claim 18, further comprising: Based on the determination to execute the sensing service, and based on the second priority and the third priority for the communication service, it is determined whether to execute the transmission of the sensing service.

20. The method according to any one of claims 17 to 19, further comprising: Based on the determination to execute the communication service, a first notification message for sensing service failure is sent to the first network element.

21. The method of claim 20, wherein the first notification message comprises: Identifiers of sensing services that have not been executed or have been preempted; or The reason value for sensing business failure.

22. The method according to any one of claims 17 to 19, further comprising: Based on the determination of executing the sensing service or the transmission of the sensing service, a second notification message of communication service failure is sent to the third network element.

23. The method of claim 22, wherein the second notification message comprises: Identifiers of communication services that have not been executed or have been preempted; or The reason for the communication service failure.

24. The method according to any one of claims 12 to 23, wherein: The first network element includes a sensing function (SF); The second network element includes a Radio Access Network (RAN) node; or The third network element includes a Session Management Function (SMF).

25. A communication method applied to a third network element, the method comprising: Receive Quality of Service (QoS) information corresponding to the perceived service; as well as Based on the received QoS information, a request message is sent to request the second network element or terminal device to perform at least one of the execution or transmission of sensing services.

26. The method of claim 25, wherein the request message comprises: The QoS information and the requirements of the sensing service.

27. The method of claim 25, wherein the request message comprises at least one of the following: First QoS information corresponding to the execution of the sensing service, wherein the first QoS information is used to indicate a first priority for the execution of the sensing service; or The second QoS information corresponding to the transmission of the sensing service, the second QoS information being used to indicate the second priority of the transmission of the sensing service.

28. The method of claim 27, further comprising: Based on the received QoS information, at least one of the first QoS information or the second QoS information is determined.

29. The method according to any one of claims 26 to 28, wherein the requirement of the sensing service includes at least one of the following: Precision of perceived business operations; Perceive the latency of the service; or The area where the business is perceived.

30. The method according to any one of claims 25 to 29, further comprising: In cases where sensing services are executed before communication services, or where a sensing service preempts a communication service that is currently being executed, a notification message indicating that the communication service has failed is received from the second network element.

31. The method of claim 30, wherein the notification message comprises: Identifiers of communication services that have not been executed or have been preempted; or The reason for the communication service failure.

32. The method according to any one of claims 25 to 31, wherein: The second network element includes a Radio Access Network (RAN) node; or The third network element includes a Session Management Function (SMF).

33. A communication method applied to a terminal device, the method comprising: Receive a request message for at least one of the execution or transmission of a request-aware service; as well as Based on the request message, the priority associated with the sensing service is determined.

34. The method of claim 33, wherein determining the priority associated with the sensing service includes at least one of the following: Based on the first QoS information corresponding to the execution of the sensing service, a first priority for the execution of the sensing service is determined; or Based on the second QoS information corresponding to the transmission of the sensing service, a second priority for the transmission of the sensing service is determined.

35. The method of claim 33 or 34, wherein the request message comprises: The Quality of Service (QoS) information corresponding to the perceived service, and the requirements of the perceived service.

36. The method of claim 35, further comprising: Based on the request message, at least one of the first QoS information or the second QoS information is determined.

37. The method of claim 36 or 36, wherein the requirement of the sensing service includes at least one of the following: Precision of perceived business operations; Perceive the latency of the service; or The area where the business is perceived.

38. The method of claim 33 or 34, wherein the request message includes at least one of the first QoS information or the second QoS information.

39. The method according to any one of claims 34 to 38, further comprising: Based on the first priority, the second priority, and the third priority for communication services, it is determined whether to execute the sensing service and the transmission of the sensing service.

40. The method according to any one of claims 34 to 38, further comprising: Based on the first priority and the third priority used for communication services, it is determined whether to execute the sensing service.

41. The method of claim 40, further comprising: Based on the determination to execute the sensing service, and based on the second priority and the third priority for the communication service, it is determined whether to execute the transmission of the sensing service.

42. A communication device, comprising: A processor for performing the method according to any one of claims 1 to 10, 11 to 24, 25 to 32, or 33 to 41.

43. A computer-readable storage medium storing instructions that, when executed, cause the method according to any one of claims 1 to 10, 11 to 24, 25 to 32, or 33 to 41 to be performed.

44. A computer program product comprising instructions for causing the method according to any one of claims 1 to 10, 11 to 24, 25 to 32, or 33 to 41 to be implemented.

45. A communication system comprising a first network element, a second network element, a third network element, and a terminal device, wherein the first network element is configured to perform the method as described in any one of claims 1 to 10, the second network element is configured to perform the method as described in any one of claims 11 to 24, the third network element is configured to perform the method as described in any one of claims 25 to 32, and the terminal device is configured to perform the method as described in any one of claims 33 to 41.

Images