System and method for implementing local aware as service in mobile network

Abstract

The sensing as a service is a new normal form for researchers to start to explore recently, and is another way for providing value for cellular service consumers and network operators. This normal form transformation will implement a variety of potential applications, including local awareness services, such as positioning, tracking, V2X applications, environmental monitoring, and the like. In addition to the method, the invention also discloses a new network entity / network function, namely a sensing manager (SM). The SM processes the network node gNB and the perceptual functionality of the connected (registered) external sensor. Any available network entity in the current network does not support the function executed by the new network entity.

Description

Technical Field

[0001] The present invention relates to a communication network, and more particularly, to a method and device for sensing and communicating in a communication network. Background Art

[0002] Over the past decade, sensors have become an essential part of modern life. Innovative sensor solutions and sensor networks have greatly improved our daily lives. Some sensor networks exist in the form of private Internet of Things (IoT) networks; many of these networks are already commercially available, while others are in the development stage, including the 3rd Generation Partnership Project (3GPP) discussion on massive machine type communication (mMTC).

[0003] Integrated sensing and communication (ISAC) is a recently introduced technology that relies on RF sensing. Its vision is to transform the network into a wide-area sensing network that can be applied to a range of applications, including: tracking and positioning, smart home and in-vehicle sensing, connected vehicles, smart manufacturing and industrial IoT, remote sensing, and environmental monitoring. This sensing and communication network is ubiquitous and is seen as a great opportunity to further enhance our daily experience.

[0004] RF sensing has its limitations compared to the envisioned applications. Therefore, in order to unleash the potential of sensing networks, in addition to ISACs, it is expected that future networks will also integrate other forms of sensing applications, such as IoT sensors owned by operators, sensing nodes that sell data to operators, and joint communication and radar capabilities of future networks. Different forms of sensing combined together will form a powerful sensing network that can provide valuable services / products to a range of customers from large companies to small businesses (security companies, hospitals, nursing homes) and even individual consumers.

[0005] ISAC has been extensively explored in recent publications as a joint operation that enables the integration of communications and radar-like functions that coexist on the same waveform. ISAC primarily develops the necessary technology to enable communications and radar-like functions from a physical layer perspective. Many publications also discuss the fundamental limitations of the technology and envision a variety of possible applications that could be realized.

[0006] Ongoing research and development (R&D) projects are mainly focused on the device and system level development of sensing technologies to enable them to be energy efficient and operate accurately, as well as on envisioning various end-user applications for these technologies. However, the methods that network operators can use to provide sensing as a service for monetization purposes are only assumed to exist without clearly defining the process. There is a lack of description in the literature on the methods by which sensing service consumers can make sensing service requests and how such requests are handled by the serving network node gNB. There is also no proper guidance in this regard in the published telecommunication standards.

[0007] Therefore, a method and system for implementing perception as a service is needed to eliminate or reduce one or more limitations in the prior art.

[0008] The purpose of this background technology is to disclose information that the applicant believes may be relevant to the present invention. It is not intended to admit, nor should it be interpreted, that any of the above information constitutes prior art relative to the present invention. Summary of the invention

[0009] The purpose of the present disclosure is to provide a method, apparatus and system for implementing a perceptual operation. The embodiment solves the task of receiving and satisfying a UE's request for a perceptual service. This may include distinguishing between a communication service request and a perceptual service request. This may also include a network interpreting and satisfying a perceptual service request. As used herein, a "perceptual service request" may also be referred to as a request for a network perceptual service.

[0010] According to an embodiment, a provided method describes the interaction between a user device and a network node that provides network access. The user device (for example, a mobile device, a phone, a tablet, a PC, a smart car, a TV, etc.) is network enabled. For simplicity, this document generally refers to the network node that provides network access as a gNB, but other types of network nodes may also be used. In addition, messaging and specific data exchanged between network entities to implement local awareness services are specified. In addition, a process that is triggered when the network recognizes a perception service request from a user device is described. The embodiment specifies the control operations and signal flows required to manage awareness functions and to satisfy perception service requests locally without going through the core network.

[0011] In addition, an apparatus is provided that includes a network entity such as a network function. The network entity does not currently exist in the network, but is necessary to provide the perception service to the client. In addition, the new network entity performs functions that are not currently supported by any other network entity. The new network entity is called a "perception manager". Among other tasks, the perception manager handles perception service request interpretation by converting perception service requests into machine understandable instructions, and is responsible for sensor processing.

[0012] The sensing manager (SM) can be responsible for determining which sensor or sensors are required for a specific sensing service request and submitting this information to the network node (gNB). The gNB can then communicate with the indicated sensors and can collect the sensing data of the indicated sensors. Therefore, the collected sensing data can be sent to the SM for verification and accuracy checks, and encoded to protect privacy. One possible advantage of having the SM be responsible for determining the sensors required for the task is to avoid overly complex system modifications. The SM can perform all the logical operations required and can complete all the necessary calculations. Therefore, the gNB can still be used mainly as a relay and access node, ensuring that data is transmitted back and forth between terminals.

[0013] The SM may be responsible for building a database of available sensors. The database of available sensors enables the perception manager to make timely decisions on one or more of the following aspects: the feasibility of the perception task from a resource perspective, the type of perception tasks that can be accomplished, the quality of perception service (QoS) that can be provided given the available sensors, the scalability of the database (because new sensors can be easily added to the database), the security and privacy of the collected perception data, the accuracy of the collected perception data relative to the perception service request, and the locality of the perception task (because the perception manager has access to the perception coverage capabilities of local sensors).

[0014] In addition, the SM may also be responsible for ensuring perceived QoS and preparing utility reports for charging users for perceived services.

[0015] Unlike conventional communication service requests, perception service requests may involve two types of services working together to satisfy the request, namely communication and perception. While perception depends on the type and quality of available sensors, it may also be affected by the quality of the communications used to collect and send the perception data back to the perception consumer. Therefore, in the present disclosure, the SM can handle and monitor QoS (communication and perception) through the currently standardized 3GPP architecture. The SM can work with the gNB to satisfy the perception service request, and the SM can also help meet the QoS requirements.

[0016] After completing the sensing service task, the SM may generate a resource utility report indicating the amount of resources consumed. The prepared utility report may be sent to an access and mobility management function (AMF), etc. The AMF may then interact with a policy control function (PCF) and a charging function (CHF) to charge the sensing consumer, etc. Advantages that may be brought by the disclosed arrangement may include compatibility with conventional systems and standards, including a pay-per-use type of billing, which provides flexibility for both the network and the sensing consumer.

[0017] According to an embodiment of the present disclosure, a message may be received by a network node providing network access. The received message may be a message on a physical uplink control channel (PUCCH), which has a standardized uplink control information (UCI) format of type 2, 3 or 4. The received message may include at least one predetermined bit, which is set to a predetermined value to indicate a sensing service request. In addition, according to some embodiments, the message is received on a predetermined wireless communication channel. The predetermined wireless communication channel may transmit messages for networked sensing services and networked communication services.

[0018] Upon detecting that the message indicates a sensing service request (SSR), coordination with the perception manager function may be performed to satisfy the SSR. Such detection may involve distinguishing the message from a message indicating a communication service request. The request may be satisfied using a sensor registered with the perception manager function.

[0019] According to some embodiments, coordinating with the perception manager function may include: sending to the perception manager function detailed information of a perception service request, wherein the detailed information of the perception service request includes one or both of the following: a location to be sensed; and perception-related information required to satisfy the perception service request. In addition, the coordination may include: receiving from the perception manager function: a first indication of one or more sensors for satisfying the perception service request, and a second indication of required perception data from each of the one or more sensors. Coordinating with the perception manager function may also include: interacting with the one or more sensors according to the first indication and the second indication to obtain the required perception data from each of the one or more sensors. In some embodiments, interacting with the one or more sensors includes: indicating to each of the one or more sensors a communication resource allocated to the sensor for providing the perception data to the network node, and receiving the perception data that can be used to satisfy the perception service request through the communication resource allocated to the sensor for use. In addition, after receiving the first indication from the perception manager function, the initiator of the perception service request or the related device (e.g., a perception consumer or user device) may receive an indication of the communication resource allocated for subsequently receiving the perception data associated with the perception service request from the network node or the related device.

[0020] In some embodiments, interacting with one or more sensors may also include: initializing the sensors and maintaining one or both of: a registration of the one or more sensors in a database accessible to the perception manager, the registration including the location and capabilities of the one or more sensors; and communication resources available for communication between the network node and the one or more sensors.

[0021] Interacting with the perception manager may be performed to register the one or more sensors with the perception manager. Interacting with the perception manager may include: receiving an indication from the perception manager to update a state of at least one of the one or more sensors at a specified update frequency; reporting the state of at least one of the one or more sensors to the perception manager at the specified update frequency. Alternatively, interacting with the perception manager may include: receiving a request from the perception manager to update a state of at least one of the one or more sensors; and in response to the request, reporting the state of at least one of the one or more sensors to the perception manager. The reported state may include one or more of: sensor responsiveness, sensor capability, and sensor location.

[0022] The present disclosure includes a SSR authentication method. The method may include: interacting with an access and mobility management function (AMF) to authenticate the perception service request in advance. This interaction with the AMF may be performed before interacting with the perception manager function. The AMF may also be used to authenticate the request to use the network communication service.

[0023] In some embodiments of the present disclosure, after detecting a message indicating a sensing service request, detailed information of the sensing service request may be requested and received. The detailed information of the sensing service request may include one or both of the following: the location to be sensed; and the sensing-related information required to satisfy the sensing service request.

[0024] Some embodiments of the present disclosure may include, together with a request for detailed information of the awareness service request, an indication of a communication resource allocated for further communication with a network node regarding the awareness service request. The received detailed information of the awareness service request may be transmitted via the communication resource.

[0025] According to some embodiments, the perception manager function may include a first entity and a second entity, the first entity being co-located with a network node or located at another location at the edge of the communication and perception network, and the second entity being located at a core of the communication and perception network or located at another location away from the edge of the communication and perception network. In some embodiments, sending detailed information of the perception service request to the perception manager function may include: communicating with the second entity. In some embodiments, the first indication and the second indication are received from the second entity. After receiving the first indication and the second indication from the second entity, interaction may be performed with the first entity to confirm the first indication and the second indication.

[0026] Implementing the awareness manager functionality partially or entirely at the edge of the network may have the effect of reducing the latency of local awareness tasks since these awareness tasks can be completed without traversing the network.

[0027] Some embodiments of the present disclosure include: receiving sensory data that can be used to satisfy a sensory service request. After verifying that the received sensory data satisfies the sensory service request, the received sensory data can be provided to an initiator of the sensory service request or a related device. Verifying that the received sensory data satisfies the sensory service request can be accomplished by communicating with a sensory manager function. Communicating with the sensory manager function to verify that the received sensory data satisfies the sensory service request can include: communicating with a first entity.

[0028] In some embodiments, after determining that the perceived service request has been satisfied, a utility report may be transmitted to an access and mobility management function (AMF) or other network function. The utility report provides an indication that the perceived service request has been satisfied. The utility report may include an indication of the amount of resources consumed in satisfying the perceived service request and may be used to charge for satisfying the perceived service request.

[0029] Yet another embodiment provides one or more network nodes implementing a perception manager function and a method in combination with the one or more network nodes implementing the perception manager function. The method includes: maintaining information indicating the location and capabilities of one or more sensors local to the perception manager function. The method also includes: receiving detailed information of a perception service request from a network node providing network access, wherein the detailed information of the perception service request includes one or both of the following: the location to be sensed; the perception-related information required to satisfy the perception service request. The method also includes: sending a first indication of one or more sensors used to satisfy the perception service request and a second indication of the required perception data from each of the one or more sensors to the network node providing network access, wherein the first indication and the second indication are based on the maintained information. In some embodiments, the method also includes: receiving perception data that may be used to satisfy the perception service request from the network node providing network access, wherein the perception data originates from the one or more sensors; when the perception data satisfies the perception service request, sending an indication that the perception data satisfies the perception service request to the network node providing network access. In some embodiments, the method includes: monitoring and processing one or more quality of service (QoS) requirements related to the content of the perception data, and determining whether the sensor local to the network node providing network access can satisfy the perception service request.

[0030] When the sensor local to the network node providing network access is able to satisfy the sensing service request, the first indication and the second indication may be sent.

[0031] When the sensor local to the network node providing network access cannot satisfy the sensing service request, for example, an indication that the sensor local to the network node providing network access cannot satisfy the sensing service request may be sent by or through the network node providing network access.

[0032] The perception manager function may include a first entity and a second entity, wherein the first entity is co-located with a network node providing network access or located at another location at the edge of the communication and perception network, and the second entity is located at the core of the communication and perception network or located at another location away from the edge of the communication and perception network.

[0033] The second entity may perform the following operations: maintaining information indicating the location and capabilities of the one or more sensors, receiving detailed information of the sensing service request, and sending the first indication and the second indication. The network node providing network access may interact with the first entity to confirm the first indication and the second indication. The first entity may also perform the receiving of the sensing data and the sending of the sensing data to satisfy the indication of the sensing service request.

[0034] After determining that the awareness service request has been satisfied, a utility report that the awareness service request has been satisfied may be sent to an access and mobility management function (AMF) or other network function. The utility report may be used to charge for satisfying the awareness service request.

[0035] Other embodiments disclose a mobile device for accessing a network and a method in combination with the mobile device for accessing the network. The method includes: sending a message to a network node on a predetermined wireless communication channel, wherein the wireless communication channel is used to support network awareness services and network communication services, and the network node provides access to the network. The message can be used to indicate an awareness service request. In addition, the message can be a message on a physical uplink control channel (PUCCH), and the message has a standardized uplink control information (UCI) format of type 2, 3 or 4. In addition, the message can include at least one predetermined bit, and the at least one predetermined bit is set to a predetermined value to indicate the awareness service request. The method also includes: receiving a request for detailed information of the awareness service request, wherein the detailed information of the awareness service request includes one or both of the following: a location to be sensed; awareness-related information required to satisfy the awareness service request; sending detailed information of the awareness service request to the network node. Some embodiments provide a method. The method includes: receiving an indication of a communication resource allocated for further communication with the network node regarding the awareness service request together with a request for detailed information of the awareness service request, wherein the detailed information of the awareness service request is sent via the communication resource. In some embodiments, the method includes: receiving, from a network node providing access to a network, sensory data that may be used to satisfy a sensory service request; and when the sensory data satisfies the sensory service request, sending an indication to the network node providing access to the network that the sensory data satisfies the sensory service request. In some embodiments, the method further includes: determining whether the sensory data satisfies the sensory service request based at least in part on evaluating whether the sensory data satisfies one or more quality of service (QoS) requirements related to content of the sensory data.

[0036] An embodiment provides a network node, such as a gNB, for providing network access. The network node is configured to receive a message on a predetermined wireless communication channel, wherein the predetermined wireless communication channel transmits a message for a network awareness service and a network communication service, the message indicating a request for the network awareness service. The network node is configured to coordinate with a perception manager function to satisfy the request for the network awareness service using sensors registered with the perception manager function.

[0037] An embodiment provides a device, which includes a perception manager function implemented by one or more network nodes. The perception manager function is used to maintain information indicating the location and capabilities of one or more sensors local to the perception manager function. The perception manager function is used to receive detailed information of a request for a network perception service from a network node that provides network access, wherein the detailed information of the request for the network perception service includes one or both of the following: the location to be perceived; and the perception-related information required to satisfy the request for the network perception service. The perception manager function is used to send a first indication of one or more sensors used to satisfy the request for the network perception service and a second indication of the required perception data from each of the one or more sensors to the network node that provides network access, wherein the first indication and the second indication are based on the maintained information.

[0038] The embodiment provides a mobile device for accessing a network. The mobile device is used to send a message to a network node on a predetermined wireless communication channel, wherein the wireless communication channel is used to support a network awareness service and a network communication service, and the network node provides access to the network. The message is used to indicate a request for the network awareness service.

[0039] The embodiment provides a system, which includes a combination of two or more of the network node, apparatus, and mobile device described above.

[0040] The embodiment provides a computer program product, which includes a non-transitory computer-readable medium having statements and instructions recorded thereon, and when the statements and instructions are executed on one or more computers, the one or more computers are enabled to implement the above-described method.

[0041] Embodiments are described above in conjunction with various aspects of the present invention, and these embodiments can be implemented based on these aspects. It will be appreciated by those skilled in the art that embodiments can be implemented in conjunction with the aspects describing these embodiments, but can also be implemented together with other embodiments of this aspect. When the embodiments are mutually exclusive or incompatible with each other, this will be apparent to those skilled in the art. Some embodiments can be described in conjunction with an aspect, but can also be applied to other aspects, which will be apparent to those skilled in the art. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] Other features and advantages of the present invention will become apparent through the following specific embodiments in conjunction with the accompanying drawings, in which:

[0043] Figure 1It is a block diagram of the radio access network (RAN) communicating with the core network (CN) and user equipment through the sensing consumer.

[0044] Figure 2 It is a network node gNB environment with multiple sensors nearby.

[0045] Figure 3 It is a network node gNB that supports perception and a sensing manager (SM) co-located with the network node gNB.

[0046] Figure 4 It is a flowchart for implementing local awareness as a service in a network node gNB with ISAC capability.

[0047] Figure 5 is a flow chart of periodic sensor status updates.

[0048] Figure 6 is a flow chart for updating the sensor status based on the request.

[0049] Figure 7 It is an environment where SM adopts a hierarchical form of supporting perception network nodes gNB.

[0050] Figure 8 It is a flowchart for implementing local awareness in a hierarchical gNB with ISAC-capable SM.

[0051] Fig. 9 It is a flow chart of periodic sensor status update under E-SM / SM-F control.

[0052] Fig.10 It is a flow chart for updating the sensor status according to the E-SM / SM-F request.

[0053] Fig.11 is a block diagram of a user device (eg, a mobile device).

[0054] It should be noted that throughout the drawings, like features are identified by like reference numerals. DETAILED DESCRIPTION

[0055] Future computing applications and daily activities are expected to rely heavily on various sensory data (autonomous driving, object tracking, remote control, smart agriculture, virtual reality, etc.). Integrated sensing and communication (ISAC) is a new paradigm that enables mobile networks to perceive the surrounding environment through radar-like functions. The antenna installed on the network node gNB sends a signal and monitors the reflection of the signal. The signal processing module in the base station converts the reflection into useful information, such as object detection, object classification, or imaging. In addition to ISAC perception, the network node gNB can also access different IoT sensors, such as cameras, LIDAR / LADAR, ultrasonic sensors, etc. These sensors can send the data of these sensors back to the network wirelessly through nearby network nodes.

[0056] However, even in the future, user equipment is not expected to be able to integrate all sensors required to meet all possible application requirements on its hardware. Therefore, we envision that future user equipment (UE) will rely more on peripheral, temporary (e.g., roadside) sensors that can be accessed on demand. Therefore, in these future networks, the network node gNB is expected to have access to a large number of sensors with various capabilities, such as ISAC-enabled antennas, visible / IR cameras, LIDAR / LADAR, ultrasonic sensors, humidity sensors, etc.

[0057] Conventional network nodes gNB cannot interpret detailed perception requests, such as "detect objects in the area" or "count the number of cars on the street". With current technology, it is difficult for the network to process these perception requests, instead, these requests are usually implemented as part of the application. In order to implement such complex perception services without relying on third-party applications, the embodiments of the present disclosure provide a way by which perception consumers can transmit their perception requests directly to the network node gNB. In addition, the embodiments provide a way by which the network node gNB can interpret abstract perception service requests and convert the request into machine-understandable instructions.

[0058] Many research and development (R&D) projects focus on developing technologies that ensure the integration of global and local perception capabilities with communication networks, where the above-mentioned global / local perception capabilities can be provided to customers through user equipment (UE) units. These research and development (R&D) projects envision several possible applications that can be realized through these new technologies. With the help of a network architecture that supports communication and perception, network operators can monetize on-demand perception services by providing perception services as a value-added solution to network consumers. To fill the gaps in these efforts, the embodiments of the present disclosure provide a mechanism for providing perception services to consumers (both globally and locally).

[0059] Therefore, embodiments of the present disclosure provide a technique that defines an ISAC-enabled network as a perception service provider for network-enabled perception consumers (e.g., network-enabled mobile devices or other network-enabled devices). A method and system are provided that define the interaction between a perception consumer (e.g., a mobile device) and its serving network node gNB in ​​an ISAC-enabled network. In addition, steps are provided to implement perception services for various applications based on currently implemented commercial networks with the lowest possible modification cost. Embodiments of the present disclosure provide a mechanism for a user device to make a perception service request. Other embodiments provide a mechanism for a perception network node gNB to distinguish between a perception service request and a communication service request. Other embodiments provide a mechanism for distinguishing between a local perception service request and a global perception service request (i.e., distinguishing between a perception consumer seeking information from one of the sensors within the coverage area of ​​the serving network node gNB and a perception consumer seeking information from other network nodes gNB). Some other embodiments of the present disclosure provide a mechanism for a network to interpret and satisfy a perception service request, wherein the network node gNB can determine which sensor or sensors (selected from multiple available sensors) are required for the task. Some embodiments address the task of billing sensing consumers for sensing services and ensuring quality of service (QoS) requirements.

[0060] Conventionally, a network node (e.g., a gNB) is only connected to a core AMF entity, which handles network communication services. In this setting, the network node does not need to determine where to send incoming control signals, because there is only one choice, namely to send to the AMF. In contrast, in an embodiment of the present disclosure, the network node determines how to process or where to send incoming control messages. The network node examines the incoming control message and determines whether the control message indicates a perception service request or a communication service request. The network node then processes the message accordingly, for example, sending the message to an appropriate management entity, such as an AMF for communication service requests or a perception manager function for perception service requests. Therefore, the network node can detect that the message indicates a perception service request at least in part by distinguishing the message from a message indicating a communication service request.

[0061] Local awareness as a service application does not necessarily require interaction between the consumer and the (e.g., 3GPP) core network. Therefore, it is possible that local awareness tasks are handled in a semi-independent manner in the serving network node gNB, and embodiments of the present disclosure include this possibility. Therefore, this disclosure does not explicitly cover issues such as routing, mobility, or switching of awareness services within a global awareness network, but these capabilities may exist.

[0062] A subset of the above-mentioned perception applications can be classified as local perception applications. These applications refer to perception tasks that do not require cross-network connectivity. Instead, these tasks can be accomplished by local sensors or ISAC functions of the serving cell that communicate with the serving network node (gNB). Therefore, local sensors or ISAC sensors of the serving cell may only require local interaction between network-enabled perception consumers (e.g., network-enabled mobile devices) and their serving network node gNB. Exemplary applications include: farms need local weather condition reports, VR / XR games need local perception for a complete immersive experience, autonomous vehicles use nearby roadside units (RSUs) as peripheral sensors to extend their visual range, and so on. For these applications, the serving network node gNB needs to have sufficient intelligence to be able to complete local perception tasks. Conventional mobile networks do not provide these services themselves, nor do they provide the required intelligence in the network node gNB that can complete the "local perception as a service" application.

[0063] IoT sensors together with the ISAC functionality of the associated network node gNB form part of what can be defined as a local awareness network. Mobile devices (user equipment) requesting awareness information from this local awareness network is using the local awareness as a service functionality of the mobile network.

[0064] Requesting a local sensing service can be a multi-step process. According to one embodiment, the process includes the following operations. The user equipment connects to the network node gNB. The network node gNB authenticates the user equipment for the service (to ensure that the user is subscribed to the requested service). The user equipment notifies the network node gNB of the specific content that needs to be sensed. The network node gNB interprets the details of the sensing service task indicated by the user equipment. The network node gNB determines whether the sensing service request is a local sensing service request or a global sensing service request. For local sensing services, the network node gNB determines whether the available sensing capabilities (the IoT sensors used and the ISAC capabilities of the network node) are capable of completing the sensing service. The network node gNB then collects the requested sensing data from the IoT sensors and the ISAC function.

[0065] The collected sensing data will be evaluated against the sensing service request of the user equipment for authentication and verification. The network node gNB then sends the verified data back to the user equipment. The user equipment verifies whether the requested sensing service task is completed correctly or whether more sensing data is required. If the sensing service task is marked as completed, the network charges the user or other entity for the sensing service.

[0066] For the purpose of this disclosure, it is assumed that sensor technology has been developed and the network is able to provide sensing functions, and the focus is on methods and systems by which users (UEs) can access sensing services.

[0067] Figure 1 A block diagram of a radio access network (RAN) 1010 in communication with a core network (CN) 1000 and a perception consumer (e.g., UE or mobile device) 6 provided in some embodiments is shown. The RAN 1010 includes a plurality of network nodes (gNBs) 7. The perception consumer 6 may perform the following tasks: interact with the network node 7 to make a perception service request, receive perception data, and determine and indicate whether the perception data satisfies the perception service request, etc. Although the network node is shown to be a gNB, other types of network nodes may also be used in some embodiments, which typically access communication and perception services through a wireless communication interface.

[0068] Figure 2An environment is shown with a network node gNB 7 and a plurality of sensors 1 to 5 (although there may be more or fewer sensors). The plurality of sensors 1 to 5 may provide sensing data to a sensing consumer 6. However, conventional network nodes are only used to transmit communication data and manage radio resources. Therefore, in a conventional network, the gNB 7 cannot distinguish between a communication service request and a sensing service request submitted by the sensing consumer 6 without taking further measures (e.g., the measures described herein). These sensors are communicatively coupled to the gNB, e.g., directly coupled, and are thus located locally at the gNB. The physical location of these sensors is also typically relatively close to the gNB, e.g., within the direct wireless communication range of the gNB. Therefore, these sensors typically acquire sensor data for the local environment of the sensing consumer, thereby providing local sensing services. Although not shown, other devices such as other UEs, sensing consumer UEs, or communication service consumer UEs may appear near the gNB and be served by the gNB. Therefore, embodiments of the present disclosure may involve simultaneously serving multiple sensing service consumers, multiple communication service consumers, or a combination thereof.

[0069] Therefore, the embodiments of the present disclosure provide a way to distinguish between conventional communication tasks and perception service tasks. In various embodiments, to facilitate this distinction, bits of standard UCI formats 2, 3, or 4 are used as "indication bits". Other formats may also be used to achieve this purpose. In this way, the gNB can process the message of the perception consumer as a perception service request or a communication service request based on the values ​​of these bits set in the message.

[0070] like Figure 3 As shown, a perception consumer 6 (whether a UE, a small business, a large company or its electronic device) will access perception services, such as local perception services, in its serving network node gNB 7. In addition to having ISAC capabilities, the serving network node gNB 7 can also access various different types of (e.g., operator-owned or other entity-owned) sensors 1 to 5, such as cameras, LIDAR / LADAR, sonar, temperature sensors, humidity sensors, magnetic sensors, accelerometers, microphones, wireless receivers, etc. The perception consumer 6 can request local perception services. Local perception services are perception tasks that can be accomplished through the ISAC function of the serving network node gNB 7, through multiple operator-owned or other entity-owned sensors 1 to 5 used by the serving network node gNB 7, or through a combination of them. A perception manager 8 is provided, which implements the functions responsible for sensor processing and perception service request processing (among other tasks). The perception manager function can be an entity co-located with the network node or located elsewhere at the edge of the network (e.g., in a computing device local to the gNB). The perception manager function can alternatively include a first entity and a second entity, such as Figure 7As shown. The first entity (e.g., E-SM 8-1) is co-located with the network node or located at another location at the edge of the communication and perception network. The second entity (e.g., SM-F 8-2) is located at the core of the communication and perception network or located at another location away from the edge of the communication and perception network. As described above, other devices such as other UEs, perception consumer UEs, communication service consumer UEs, etc. can appear near the gNB and be served by the gNB.

[0071] The embodiments of the present disclosure presented below describe an implementation of the perception manager SM 8 as part of an edge computing network close to a single network node gNB 7.

[0072] SM 8 collects information about sensors 1 to 5 (which may be IoT sensors) within the coverage area 1011 of the network node gNB 7. The information is collected periodically or upon request by SM 8. The information may be collected wirelessly, in which case it is assumed that the sensors 1 to 5 have access to the network served by the network node gNB 7. SM 8 may be responsible for managing and controlling the ISAC function (if present) of the associated network node gNB 7, where the ISAC function may be considered as one of multiple local sensors. SM 8 uses the collected information to generate and maintain a database of available sensors, which is used to evaluate the perception capabilities of the local cell.

[0073] The information collected by SM 8 may include some or all of the following: energy level of the sensor, location of the sensor, type of sensed data, default size of data packets generated, availability of sensing tasks, direction, and processing capabilities.

[0074] For the ISAC function, the SM 8 collects information about some or all of the following: available RF resources, beam width, number of antennas, operating frequency bands, channel state information, etc. An ISAC sensor may be a sensor that detects physical objects based on observations of the RF environment.

[0075] For mobile sensors entering and leaving the coverage area, in addition to the above information, a registration process is provided, during which the SM 8 authenticates the new sensor and assigns an ID to facilitate addressing. Mobile sensors can also provide information about their trajectory and speed. Sensing consumers or other devices (e.g., UE) equipped with sensors in the network can also be used to obtain sensing information, which may involve monetary or other incentives. These devices may need to meet certain trust criteria to become available sensors.

[0076] like Figure 4As shown, a perception consumer (UE 6 in this case) sends an uplink message to its serving network node gNB 7 to indicate a request for a task to be performed. When the task is a perception service and the message is a perception service request message, UE 6 uses a format that supports a sufficient number of bits to indicate this situation. Therefore, the message can be a message on a physical uplink control channel (PUCCH) with a standardized uplink control information (UCI) format of type 2, 3 or 4. In the present disclosure, UCI formats 2, 3 or 4 may be referred to as "perception formats". Several bits of the perception format may be used as indication bits to distinguish between a request for a communication service and a perception service request. In some embodiments, the perception format relies on bit-based control signaling already used in telecommunications. By using UCI to indicate whether the request message is a perception service request or a communication service request, the embodiments of the present disclosure are consistent with the current network architecture and only minimal modifications to the system are required to incorporate the present disclosure into the standard.

[0077] Therefore, the details of the awareness service request can be standardized and encoded into bits that are easily recognized by the network (e.g., only limited processing is required) and translated into understandable instructions by the SM. The awareness consumer (mobile device) can indicate the details of the awareness service request through standardized uplink control (UCI) and downlink control (DCI) communication resources.

[0078] More generally, the awareness service request is sent on a predetermined wireless communication channel, which transmits messages for network awareness services and network communication services (e.g., messages transmitting user data), and the network node gNB receives the awareness service request.

[0079] In various embodiments, the sensing service request message includes an indication bit or is otherwise used to indicate to the gNB that the message is a sensing service request. At least one predetermined bit of the indication bits may be set to a predetermined value to indicate that the message is related to a sensing service request. The gNB 7 reads these bits (or other indications) to detect 41 that the message indicates a sensing service request (SSR). Thus, the gNB distinguishes between messages related to sensing and messages related to other operations such as communication. If the message indicates other operations, the gNB may process the message accordingly in other ways.

[0080] After such detection, a series of authentication procedures with the AMF 9 may be initiated. This may include: the gNB 7 sending a sensing service authentication request 42a to the AMF 9; if authentication is successful, receiving a sensing service authentication confirmation 42b from the AMF 9; upon receiving the confirmation 42b, sending other messages 42c to the UE 6.

[0081] In more detail, the purpose of the AMF authentication process (e.g. involving messages 42a and 42b) is to ensure that the UE 6 is appropriately subscribed to the Sensing as a Service or otherwise authorized to use the Sensing service. Therefore, the AMF 9 can be used to authenticate the request to use the network communication service. In addition, the AMF 9 can also handle the mobility of the UE 6 in terms of communication and sensing services: if the UE 6 moves from the coverage area of ​​the current network node gNB 7 to the coverage area of ​​other gNBs, the AMF 9 can redirect the sensing data to the new cell.

[0082] After UE 6 is authenticated by AMF 9, the current network node gNB 7 may assign a unique task ID (e.g., an integer vector including a temporary ID that becomes substantially unique when mixed with the UE ID) for use by UE 6 and gNB 7 to mark and track interactions related to the requested sensing service. gNB 7 also indicates the uplink (UL) communication resources allocated to UE 6 for transmitting the details of its sensing service request. gNB 7 assigns the task to the local SM 8 by indicating the task ID and UE ID. The current network node gNB 7 may be associated with one or more SMs, depending on the size of the cell and the number of sensors in the coverage area. gNB 7 confirms the service indicating that UE 6 is authenticated. The above content (including the assigned task ID, the allocated UL resources, and the confirmation) may be included in other messages 42c sent from gNB 7 to UE 6 after authentication (if authentication is performed).

[0083] After the perception service request of UE 6 is authenticated and allocated with UL communication resources on the UL control channel, UE 6 sends back detailed information about the perception service request to the network node gNB 7 using the perception format (in a message 43a that also includes the assigned task ID). The detailed information of the perception service request may include the location to be sensed and the perception-related information required to satisfy the perception service request. The perception-related information may include, for example, what type of perception information is required, the resolution of the perception information, the quality of the perception information, the time window of the perception information, etc. In some embodiments, the detailed information of the SSR may be attached to the original perception service request message of UE 6. Therefore, the message or accompanying message indicating the perception service request includes the detailed information of the perception service request. The detailed information of the perception service request includes one or both of the following: the location to be sensed; the perception-related information required to satisfy the perception service request. In other words, the original perception service request message or a subsequent (e.g., upon request) message may include these details.

[0084] The SM may periodically update the list of available sensing functions in each gNB. This list may then be announced to all sensing consumer UEs in the coverage area. The announcement may be broadcast on a broadcast channel or signaled together with the authentication signal. Each sensing function in the list may have a specific indication code known to both the UE and the gNB. The sensing consumer UE may then use some of the sensing format bits to signal the code of the desired sensing function in the announced list. The number of sensing format bits used depends on the number of possible sensing functions that the gNB can handle. For location information, this information may be provided by any location indication method, e.g., longitude and latitude, as long as the information can be encoded using the remaining sensing format bits. The gNB then extracts this information and sends it to the sensing manager (SM) for further processing.

[0085] After receiving the message 43a, the network node gNB 7 sends the sensing service request details 43b to the assigned SM 8, including the location to be sensed and the nature of the sensing task. The task ID may also be included.

[0086] The assigned SM 8 can use this information to determine the locality and feasibility of the sensing task, which can be performed as part of the interpretation 44 of the sensing request. The sensing request interpretation can additionally or alternatively include operations such as determining how to satisfy the sensing request, determining which sensors are used to satisfy the sensing request, determining the instructions to be sent to these sensors, etc. In order to determine locality and feasibility, the SM compares the location of the sensing service task with the reachable range / coverage area of ​​the available local sensors. If the location of the task is within the coverage area, the task is considered local. However, not all local tasks are feasible, because the feasibility depends on the nature of the task and the available sensing capabilities. For example, if the sensing consumer needs to sense the humidity level in the middle of the coverage cell, but the SM cannot access the humidity sensor at the time of the sensing service request, the task is considered local but not feasible. Therefore, in various embodiments, the SM will only accept the sensing service request (SSR) if it is local and feasible. The SM can use a 2-bit confirmation system to distinguish between four cases, namely, a local and feasible SSR, a local but currently infeasible SSR, a local but infeasible SSR due to a lack of sensors, and a non-local (e.g., global) SSR.

[0087] In this embodiment, for example, if the SSR is local and feasible, the SM sends two positive bits (e.g., "1") indicating that the task is accepted. If the SSR is local but not feasible at the time of the request due to load conditions, etc., a positive bit followed by a negative bit (e.g., "0") may be transmitted to indicate that a delay may occur. If the SSR is local but not feasible due to the lack of required sensors, a negative bit followed by a positive bit is transmitted to indicate a denial of service and rejection of this type of sensing task. The sensing user can retry the same SSR after querying an updated list of available sensing services. Finally, if the SSR is not local, two negative bits are transmitted.

[0088] If the SSR is local and feasible, the SM 8 sends a message 45 back to the gNB 7 along with an acknowledgment, the message including a first indication of one or more sensors (e.g., one or more sensor IDs) for satisfying the sensing service request and a second indication of the required sensor data from each of the one or more sensors. The first indication and the second indication are based on the maintained information. The first indication and the second indication may be separate or integrated.

[0089] In the event that the sensor local to the network node gNB providing network access cannot satisfy the sensing service request, the SM indicates to the gNB that the sensing service request cannot be satisfied. More generally, if the SSR cannot be satisfied, the SM, AMF, gNB or a combination thereof may generate an informative message. The informative message may then be propagated to the corresponding sensing consumers.

[0090] If the SM 8 identifies the SSR as local and feasible, the UE 6 is allowed access to the local sensing service and is allocated downlink (DL) resources, which are then used to transmit the sensing data. Accordingly, a message 46 is sent from the gNB 7 to the UE 6, including an acknowledgement of the SSR, a task ID, and an indication of the DL resources allocated to the UE 6 for subsequent monitoring.

[0091] In addition, after receiving the message 45 from the SM 8, the gNB 7 may establish a connection with the one or more sensors, which are identified based on the first indication carried in the message 45. In this embodiment, the first indication identifies sensor 1. The connection with sensor 1 may be established by a corresponding detection message 47a. The detection message 47a may include instructions to turn on the addressed sensor (sensor 1 in this embodiment), so that the addressed sensor provides specified measurement results in a specified manner, etc. The detection message 47a may also indicate the UL resources allocated to sensor 1 for sending sensing data to the gNB 7 (for example, in message 47b). The detection message 47a may also include a task ID, which sensor 1 may include in subsequent reports of sensing data. The detection message 47a may be used to reflect or specify the portion of the second indication of sensor data required from the sensor. The detection message 47a may specify the UL resources used by sensor 1 to provide sensing data.

[0092] The sensor 1 receiving the probe message 47a may then collect the required sensing data (e.g., as indicated in the probe message 47a) and send the sensing data back to the gNB 7 using the indicated UL resources via a response message 47b. Other measured key performance indicators (KPIs) may be included in the response message. The probe and response messages 47a, 47b may be sent to and from each of the one or more sensors from which sensor data is to be collected to support SSR.

[0093] After receiving the required sensing data and KPIs, the network node gNB 7 providing network access may send a message 48a including the sensing data and KPIs to the SM for verification and validation. If the sensing data is valid and verified relative to the UE request, the SM 8 may send an indication 48b to the gNB 7 that the sensing data satisfies the sensing service request. The SM may process the sensing data to determine whether the sensing data satisfies the SSR and, therefore, whether the sensing task is completed. This may involve comparing the sensing data with the information provided by the SM in the message 45. After the SM 8 verifies and validates the requested sensing data, the gNB 7 may send a message 48c including the requested sensing data to the UE 6 using the allocated DL resources. In response, the UE 6 may send a confirmation message 48d indicating that the data has been received.

[0094] UE 6 may also verify whether the requested sensing data meets its requirements. That is, UE may determine whether the sensing data meets the sensing service request. It should be noted that in the above, both SM and UE perform the operation of verifying or checking the sensing data. In other embodiments, only one of SM and UE performs the operation of verifying or checking the sensing data.

[0095] In some embodiments, the UE (or SM) may indicate that the received sensing data does not satisfy the sensing service request. In this case, the UE may notify the SM that the sensing service request is not satisfied. Subsequently, according to the UE's indication, the sensing service may end if it is not satisfied, or the sensing service may be retried and the SM may be instructed to improve the reported sensing data.

[0096] If the check at UE 6 succeeds, the task is deemed completed and UE 6 may send a task completion confirmation message 49a to gNB 7. The task completion confirmation may be propagated to SM 8. SM 8 may then close the perception service request and prepare a utility report (UR). The utility report may include an indication of the amount of resources consumed in satisfying the perception service request. The utility report is forwarded to AMF 9 via gNB 7 using message 49b. Alternatively, the utility report may be sent from SM 8 to AMF 9 using message 49b-1 without involving the gNB. The utility report may include a user ID and a confirmation that the SSR is closed. More generally, the gNB, SM, or a combination thereof may generate a utility report indicating the resources consumed in satisfying the perception service request. AMF 9 may use the utility report to charge UE 6 or an associated user for the perception service. AMF 9 may send a confirmation message 49c to gNB 7 (or alternatively to the SM) indicating that task charging has been completed.

[0097] In some embodiments, in addition to or in lieu of sending the sensing data to the UE 6 and subsequently communicating with the UE, the communication regarding the sensing data may involve another device 10 or multiple other devices. The other device may be a gNB-local or other gNB-local other UE, a designated data storage device, or other network electronic device directly or indirectly coupled to the gNB via a wired link or a wireless link. The other device 10 may be a virtualized device located in the cloud, a remote computer, etc. The other device 10 may be specified in the previously transmitted sensing service request details or subsequently specified. As shown, in lieu of or in lieu of sending a message 48c including the requested data to the UE 6, the gNB (or other associated device) may send a message 48c-1 including the requested data to the other device 10. The other device 10 may send a confirmation message 48d-1 to the gNB indicating that the data has been received. In some embodiments, the other device may also send a task completion confirmation 49a-1 to the gNB or other associated device, indicating that (for example) after analyzing the data, the sensing task has been completed.

[0098] Some embodiments of the present disclosure may include different ways of charging the perceived consumer for the services provided. In addition to or in lieu of the billing process disclosed above, the SM, AMF, gNB, or a combination thereof may generate a cost estimate for the perceived service request. If the perceived consumer agrees to the cost estimate, the cost estimate may be provided to the perceived consumer before satisfying the SSR. If the perceived consumer disagrees with the cost estimate, the SSR may be abandoned. Some embodiments of the present disclosure may include other or alternative processes for negotiating a cost estimate for the SSR, other or alternative payment processes (e.g., prepayment).

[0099] In various embodiments, the SM interacts with the sensor in order to register the sensor in the database of the sensor. The sensor registration information may include the location and capabilities of the sensor. The sensing manager (SM) may access the database of the sensor. The SM may additionally or alternatively interact with the sensor to allocate communication resources that may be used for communication between the sensor and the network node gNB. Sensors registered with the SM may then be used to satisfy sensing service requests. These sensors may be local to the network node and used for sensing tasks. Thus, the network node and the SM may facilitate access to various sensors.

[0100] In order to enable the sensing manager (SM) to perform its duties, such as updating the list of available local sensing services, checking the locality and feasibility of sensing service requests, indicating which sensor or sensors are to be used for sensing tasks, and preparing utility reports for charging users, the SM maintains a database of available sensors. The present disclosure details two processes by which the SM can build and maintain such a database: one is based on a periodic update process, and the other is a process for updating the database of available sensors on demand. It should be noted that the following process applies to both IoT sensors (e.g., owned by an operator or other entity) and the ISAC function at the network node gNB. For sensors with mobile characteristics or sensors that enter and leave the local cell (i.e., only temporarily available), authentication and authorization steps can be used to assign temporary sensor IDs before these temporarily available sensors can be added to the sensing database. These temporary sensor IDs will be used to communicate with these types of sensors, and these IDs will be discarded once these sensors leave the cell or no longer voluntarily provide sensing resources.

[0101] In the case of periodic sensor status updates, the process includes: receiving an indication (e.g., a request) from a sensing manager (SM) to update the status of at least one sensor at a specified update frequency. The process also includes: in response to the indication, periodically reporting the status of the at least one sensor to the sensing manager according to the specified update frequency. The reported status may include sensor responsiveness, sensor capability, and sensor location.

[0102] Figure 5 An embodiment of a periodic sensor status update process is illustrated as follows.

[0103] In the initial setup, SM 8 sends a message 51 including the update frequency, request ID and sensor ID to gNB 7. In this embodiment, the sensor identified by the sensor ID in message 51 is sensor 1. On a dedicated DL channel (referred to herein as the physical downlink sensor control channel (PDSCCH)), the network node gNB 7 sends a broadcast probe message 52 including the sensor ID and the UL & DL communication resources allocated for sensor control and communication. The sensor monitors the PDSCCH in a regular manner, etc. Once the sensor detects a message including the sensor ID (in this embodiment, sensor 1), sensor 1 responds by sending a message 53 broadcasting an "ON" signal (e.g., subcarrier) (sensor ID) on the allocated UL communication resources. Sensors that need more "data" UL resources also use message 53 to request more UL resources. In response to message 53, gNB 7 sends a message 54 back to sensor 1 on the allocated DL control resources to acknowledge (ACK) the requested resources. Message 54 also includes the update frequency details, request ID and the ID of SM 8. After receiving the message 54, the sensor 1 sends back a message 55 to the gNB 7 confirming the allocated UL communication resources and the update frequency. At the end of the initial setup, the gNB 7 sends a synchronization message 56 to the sensor 1 including the update start time point.

[0104] Sensor 1 waits until each update instance starts and checks if the allocated UL resources are available by sending a broadcast message 57 indicating the sensor ID and the request ID. If the resources are available, gNB 7 sends a resource grant message 58 on the allocated DL resources. In response to receiving message 58, sensor 1 sends a message 59a including the requested update and the ID of SM 8. Message 59a is sent back to gNB 7 on the allocated UL resources. Network node gNB 7 forwards the update information together with the sensor ID to SM 8 in message 59b. SM 8 acknowledges receipt of message 59b including the update information and the sensor ID by sending message 59c back to gNB 7. Upon receiving message 59c, network node gNB 7 forwards to sensor 1 a message 59d acknowledging that SM 8 received the update information. Message 59d includes the SM ID.

[0105] In the case of updating the sensor state according to the request, the process includes: receiving a request for updating the state of at least one of the sensors from the perception manager, and reporting the state of the at least one of the sensors to the perception manager in response to the request. The reported state may include sensor responsiveness, sensor capability, and sensor location.

[0106] Figure 6 An example of an embodiment of a sensor status process according to a request update is shown as follows.

[0107] In the initial setup, SM 8 sends an update request message 61 to gNB 7. Message 61 includes a request ID and a sensor ID. In this embodiment, the sensor selected by SM 8 is sensor 1. Therefore, the sensor ID corresponds to sensor 1. In response to message 61, gNB 7 broadcasts a probe message 62. The probe message 62 includes the sensor ID and the UL & DL resources allocated for control and communication. The probe message 62 is broadcast on a dedicated DL channel (PDSCCH). The sensor monitors the PDSCCH regularly and once the sensor (in this embodiment, sensor 1) detects a message including the sensor ID, sensor 1 responds with a message 63 broadcasting an "ON" signal and the sensor ID. Message 63 is broadcast on the allocated UL control resources. Sensors that need more "data" UL resources also use this step to request more resources. gNB 7 responds to message 63 by sending a message 64 acknowledging (ACK) the UL request resource grant on the allocated DL control resources and sending the update request details, request ID and SM ID. In this embodiment, the SM ID corresponds to SM 8. Sensor 1 acknowledges receipt of message 64 (Update Request ACK) by sending message 65 back to gNB 7. gNB 7 forwards the Update Request ACK to SM 8.

[0108] In the update instance phase, sensor 1 sends message 66a including requested update information and SM ID. Message 66a is sent to gNB 7 on the allocated UL resources. Network node gNB 7 forwards the requested update information together with the request ID and sensor ID to SM 8 in message 66b. In response to message 66b, SM 8 sends a confirmation message 66c back to gNB 7. Message 66c includes the request ID and sensor ID. In response to message 66c, gNB 7 forwards a confirmation of receipt of the requested update information to sensor 1 in message 66d. Message 66d includes the request ID and SM ID.

[0109] The perception manager function may include a first entity (referred to herein as E-SM) and a second entity (referred to herein as SM-F), wherein the first entity is co-located with the network node gNB or located at another location at the edge of the communication and perception network, and the second entity is located at the core of the communication and perception network or located at another location away from the edge of the communication and perception network. Therefore, the SM can be divided into at least two interoperating parts. This allows the SM to provide fast response capabilities through its part located at the edge and use the abundant resources that are readily available through its part located at the core. In addition or alternatively, the part located at the edge is very suitable for interacting with other edge adjacent devices (e.g., sensors) to implement certain SM functions, while the part located at the core is very suitable for interacting with core network functions to implement other SM functions.

[0110] Figure 7 An embodiment of a perception manager function in a multi-part or hierarchical form is shown. A first entity E-SM 8-1 is co-located with the gNB 7. The first entity E-SM 8-1 is responsible for local management and control. A second entity SM-F 8-2 is integrated in a 3GPP service-based architecture. The SM-F 8-2 is responsible for core functions such as policy control, charging, determining the locality of perception, and mobility management from a perception perspective. The E-SM 8-1 collects information about one or more available sensors within the coverage area 1011 of the connected network node gNB 7 and updates a sensor database in the SM-F 8-2. In this embodiment, the coverage area 1011 includes sensors 1 to 5. Information about available sensors is collected periodically or upon request of the E-SM 81. The information may be collected wirelessly. The E-SM 8-1 is used to manage and control the ISAC function of the gNB 7. Based at least in part on the content of the collected information, the SM-F 8-2 generates a database of available sensors. The database of available sensors can be used to evaluate the perception capabilities of the local cell. The information collected may include some or all of the following: the energy level of the sensor, location, type of sensed data, default size of the generated data packet, availability of sensing tasks, direction, and processing capabilities. The E-SM 8-1 authenticates the new sensor. The new sensor may be a mobile sensor that enters and leaves the coverage area 1011. The E-SM 8-1 assigns an ID to the new sensor for easy addressing.

[0111] Mobile sensors entering and leaving coverage areas may correspond to a semi-dynamic perception environment that may be provided according to an embodiment. In such an environment, the local perception capabilities of a network node are not fixed in time, but depend on the type of available sensors, the location of the sensors, the number of connected sensors, and so on. For ISAC capabilities, the perception capabilities may depend on the available perception bandwidth, which is also variable and depends on the load conditions in the network node. All of these parameters may change over time. Sensors may arrive and leave or become available or unavailable at different times, and accordingly, a database of sensors may be saved and managed by a sensor manager. Other sensors may be more or less continuously available. In some embodiments, more sensors may be deployed as needed, for example, in areas of high demand, more sensors may be deployed upon request of a network node. For example, an operator may install sensors on drones, which may be deployed as needed.

[0112] For the ISAC function, the E-SM 8-1 collects information about some or all of the following: available RF resources, beam width, number of antennas, operating frequency bands, and channel status information, etc.

[0113] Sensing consumers in the network may also be used to obtain sensing information, which may involve monetary incentives or other incentives. Sensing consumers 6 may need to meet certain trust criteria.

[0114] Figure 8 A further embodiment of local sensing in a network node gNB 7 in which the sensing manager SM 8 adopts a hierarchical form is shown. Figure 8 Various operations in Figure 4 The operation is similar to that in , except that SM is provided in two parts.

[0115] In this embodiment, SM-F 8-2 is part of the core functions, and the database of the sensor is created and maintained in the core network. In order to further improve the security of the collected data, SM-F can be implemented close to the cloud RAN or as part of the data center.

[0116] The network node gNB 7 receives a message on a predetermined wireless communication channel that transmits messages for network sensing services and network communication services. The message may include an indication bit. At least one predetermined bit of these indication bits may be set to a predetermined value to indicate a sensing service request. gNB 7 reads the indication bit (or other indication) to detect 81 that the message indicates a sensing service request (SSR). Therefore, gNB 7 distinguishes between messages related to sensing and messages related to other operations such as communication. If the message indicates other operations, gNB 7 may process the message in other ways accordingly.

[0117] After detection 81, a series of authentication procedures with AMF 9 can be initiated. gNB 7 can send an SSR authentication request 82a to AMF 9; if the authentication is successful, receive an SSR authentication confirmation 82b from AMF 9; when receiving the confirmation message 82b, send other messages 82c to UE6.

[0118] In more detail, the purpose of the AMF authentication process (eg, involving messages 82a and 82b) is to ensure that the UE 6 is properly subscribed to the Awareness Service or otherwise authorized to use the Awareness Service. Thus, the AMF 9 may be used to authenticate the SSR using the network communication service.

[0119] AMF 9 handles UE communication mobility: When UE 6 moves from the coverage area of ​​the current network node gNB 7 to the coverage area of ​​another gNB, AMF 9 redirects communication related data to the new cell. SM-F 8-2 handles perception mobility: If UE 6 moves from the coverage area of ​​gNB 7 to the coverage area of ​​another gNB, SM-F 8-2 redirects perception data and perception tasks to the new cell.

[0120] After the message SSR of UE 6 is authenticated by AMF 9, the current network node gNB 7 may assign a unique task ID (e.g., an integer vector including a temporary ID that becomes substantially unique when mixed with the UE ID) for use by UE 6 and gNB 7 to mark and track RSS-related interactions. gNB 7 also indicates the uplink (UCI) communication resources allocated to UE 6 for transmitting SSR details. gNB 7 assigns the task to the local SM by indicating the task ID and UE ID. The current network node gNB 7 may be associated with one or more SMs, depending on the size of the cell and the number of sensors in the coverage area. gNB 7 confirms the service indicating that UE 6 is authenticated. The above content (including the assigned task ID, the allocated UL resources, and the SSR confirmation) may be included in other messages 82c sent from gNB 7 to UE 6 after authentication (if authentication is performed).

[0121] In response to receiving message 82c, UE 6 sends back message 83a including the task ID and SSR details to gNB 7. UE 6 may send the SSR details using the sensing format. The details of the sensing service request may include the location to be sensed and the sensing related information required to satisfy the sensing service request.

[0122] The SM may periodically update the list of available sensing functions in each gNB. For example, the SM-F may periodically update the list of available sensing functions. This list may then be announced to all sensing consumer UEs in the coverage area. The announcement may be broadcast on a broadcast channel or may be signaled only together with the authentication signal. Each sensing function in the list may have a specific indication code known to both the UE and the gNB. The sensing consumer UE may then use some of the sensing format bits to signal the code of the desired sensing function in the announced list. The number of sensing format bits used depends on the number of possible sensing functions. For location information, this information may be provided by any location indication method, e.g., longitude and latitude, as long as the information can be encoded using the remaining sensing format bits.

[0123] The current network node gNB 7 communicates with the perception manager function. In this embodiment, the perception manager function includes: a first entity E-SM 8-1 co-located with the network node or located at another location at the edge of the communication and perception network, and a second entity SM-F 8-2 located at the core of the communication and perception network or located at another location away from the edge of the communication and perception network. As shown in the figure, the gNB can communicate with both the first entity and the second entity. In other embodiments, the gNB can communicate with only one of the two entities. In response to message 83a, gNB 7 sends a message 83b to the assigned SM-F 8-2. Message 83b includes a task ID and SSR details. The SSR details may include the location that needs to be sensed and the perception-related information required to satisfy the perception service request.

[0124] The assigned SM-F 8-2 uses the SSR details to determine the locality and feasibility of the sensing task. As part of the sensing request interpretation 84, the SM-F 8-2 can compare the location of the SSR with the coverage area of ​​the local sensor. If the location of the task (SSR) is within the sensor coverage area, the task is considered local. However, not all local tasks are feasible, because the feasibility depends on the nature of the task and the available sensing capabilities. In various embodiments, the SM-F 8-2 will accept the sensing service request only if the SSR is local and feasible. (If the task is global, the SM-F 8-2 will forward the task to the appropriate E-SM.) The SM-F 8-2 uses a confirmation system (e.g., a 2-bit confirmation system) to send back to the UE 6 information about the locality and feasibility of the requested sensing service. The sensing request interpretation 84 may include other operations, such as determining which sensors are to be used to satisfy the sensing request, and determining the instructions to be sent to these sensors.

[0125] SM-F 8-2 may control a database of sensors. After receiving message 83b, SM-F 8-2 may determine a first indication of one or more sensors (e.g., one or more sensor IDs) for satisfying the sensing service request and a second indication of the sensor data required from each of the one or more sensors. Thus, the first indication and the second indication may be sent to gNB 7 in an SSR confirmation message 85a. In addition to the first indication and the second indication, message 85a may also include one or more sensor IDs and a task ID. After receiving the first indication and the second indication from the second entity SM-F 8-2, gNB 7 may interact with the first entity E-SM 8-1 to confirm the first indication and the second indication. gNB7 may send a status update message 85b to E-SM 8-1. Message 85b includes the sensor ID, SSR details, and a status update request. In response to message 85b, E-SM 81 may send a status message 85c back to gNB 7. If the E-SM 8-1 determines that the database of the sensor is not up to date after evaluating the first indication and the second indication, a sensor update cycle may be started to update the sensor database in the SM-F 8-2. Once the sensor database is updated, the SM-F 8-2 may rerun the sensor selection algorithm, update the first indication and the second indication, and may send the updated set to the gNB 7. After obtaining the updated set of the first indication and the second indication, the gNB 7 may continue to complete the sensing task.

[0126] If the SSR of UE 6 is identified by SM-F 8-2 as local and feasible, UE 6 (or any other device initiating a sensing service request) may be allowed to join the local sensing service and allocated downlink (DL) communication resources, which are to be used to send sensing data associated with the sensing service request from network node gNB 7 or related equipment. gNB 7 may send an SSR confirmation message 86 including a task ID and an indication of the allocated DL resources to UE 6. In addition, gNB 7 may establish a connection with each of the one or more sensors and indicate to the sensor the uplink (UL) communication resources allocated to the sensor to provide the sensing data to network node gNB 7. In this embodiment, gNB 7 establishes a connection with sensor 1 by sending a detection message 87a including a task ID and an indication of the allocated UL resources. Message 87a may also be used to turn on sensor 1.

[0127] In response to message 87a, sensor 1 may collect the required perception data and send the perception data back to gNB 7 (via the UL communication resources allocated to sensor 1 for use). Message 87b transmitting the required perception data to gNB 7 may also include other measured key performance indicators (KPIs). gNB 7 may forward the required perception data and KPIs to E-SM 8-1 in message 88a for verification and validation. If the data is valid and verified with respect to the perception service request of UE 6, E-SM 8-1 sends an indication to network node gNB 7 in message 88b (Task Complete ACK) that the perception data satisfies the perception service request.

[0128] The requested sensing data is sent to the UE 6 (or any other initiator of the sensing service request) on the allocated UL resources in a message 88c. In response, the UE 6 may send an acknowledgement message 88d indicating that the data has been received.

[0129] In response to message 88c, UE 6 may verify the requested perception data: if the verification is successful, the task is deemed completed and UE 6 may send a task completion confirmation message 89a to gNB 7. The task completion confirmation may be propagated to E-SM 8-1 (or SM-F 8-2), which then closes the SSR and prepares a utility report (UR). The utility report may include an indication of the amount of resources consumed in satisfying the perception service request. The utility report is forwarded to AMF 9 via gNB 7 using message 89b. Alternatively, the utility report may be sent from E-SM 8-1 or SM-F 8-2 to AMF 9 using a message (not shown) without involving the gNB. AMF 9 may send a confirmation message 89c to gNB 7 (or alternatively to the E-SM or SM-F) indicating that the task charging has been completed.

[0130] and Figure 4 Similarly, instead of or in addition to sending a message 88c including the requested data to the UE 6, the gNB (or other associated device) may send a message 88c-1 including the requested data to the other device 10. The other device 10 may send a confirmation message 88d-1 to the gNB indicating that the data has been received. In some embodiments, the other device may also send a task completion confirmation 89a-1 to the gNB or other associated device, indicating that (for example) after analyzing the data, the perceived task has been completed.

[0131] Fig. 9 An example of an embodiment of a periodic sensor status update process of a perception manager in a hierarchical form is shown as follows.

[0132] In the initial setup, the E-SM 8-1 sends a message 91 including the update frequency, request ID and sensor ID to the gNB 7. In this embodiment, the sensor identified by the sensor ID in the message 91 is sensor 1. On a dedicated DL channel (referred to herein as the physical downlink sensor control channel (PDSCCH)), the network node gNB 7 sends a broadcast probe message 92 including the sensor ID and an indication of the UL & DL communication resources allocated for sensor control and communication. The sensor monitors the PDSCCH in a regular manner, etc. Once the sensor (in this embodiment, sensor 1) detects the message including the sensor ID, sensor 1 responds by sending a message 93 broadcasting an "ON" signal (sensor ID) on the allocated UL communication resources. Sensors that need more "data" UL resources also use message 93 to request more UL resources. In response to message 93, the gNB 7 can send a UL resource grant message 94 back to sensor 1 on the allocated DL control resources. Message 94 also includes the update frequency details, request ID and SM ID. In this embodiment, the SM ID is the ID of SM 8. After receiving the message 94, the sensor 1 sends back to the gNB 7 an acknowledgement message 95 confirming the allocated UL communication resources and the updated frequency. The gNB 7 can propagate the acknowledgement message (allocated UL resources and updated frequency ACK) to the E-SM 8-1. At the end of the initial setup, the gNB 7 sends to the sensor 1 a synchronization message 96 including the update start time point.

[0133] Sensor 1 waits until each update instance starts and checks if the allocated UL resources are available by sending a broadcast message 97 indicating the sensor ID and the request ID. If the resources are available, the gNB 7 sends a resource grant message 98 on the allocated DL resources. In response to receiving message 98, sensor 1 sends a message 99a including the requested update information and the SM ID. Message 99a is sent back to gNB 7 on the allocated UL resources. The network node gNB 7 forwards the update information together with the sensor ID to the E-SM 8-1 in a message 99b. The E-SM 8-1 confirms the receipt of the message 99b including the update information and the sensor ID by sending an acknowledgement message 99c back to the gNB 7. Upon receiving message 99c, the network node gNB 7 forwards a message 99d to the sensor 1 confirming that the E-SM 8-1 received the update information. Message 99d includes the SM ID. In addition, the E-SM 8-1 may send a sensor database update request message 99e to the SM-F 8-2. Message 99e may include the update information and the sensor ID.

[0134] Fig.10An example of an embodiment of a sensor status process updated upon request by a sensing manager (SM) in a hierarchical form is shown as follows.

[0135] In the initial setup, the E-SM 8-1 sends an update request message 101 to the gNB 7. The update request message 101 may include a request ID and a sensor ID. In this embodiment, the sensor selected by the E-SM 8-1 is sensor 1. Therefore, the sensor ID corresponds to sensor 1. In response to message 101, the gNB 7 may broadcast a probe message 102. The probe message 102 includes the sensor ID and an indication of the UL & DL resources allocated for control and communication. The probe message 102 is broadcast on a dedicated DL channel (PDSCCH). The sensor monitors the PDSCCH regularly, and once the sensor detects a message including the sensor ID (in this embodiment, sensor 1), the sensor 1 responds with a message 103 that broadcasts an "ON" signal (sensor ID). Message 103 is broadcast on the allocated UL control resources. Sensors that need more "data" UL resources also use message 103 to request more resources. The gNB 7 may respond to message 103 by sending a UL resource grant message 104 on the allocated DL control resources. Message 104 may include update request details, request ID, and SM ID. In this embodiment, the SM ID corresponds to SM 8. Sensor 1 acknowledges receipt of message 104 (Update Request ACK) by sending message 105 back to gNB 7. gNB 7 forwards the Update Request ACK to E-SM 8-1.

[0136] In the update instance phase, sensor 1 sends a message 106a including requested update information, a request ID and an SM ID. Message 106a is sent to gNB 7 on the allocated UL resources. Network node gNB 7 forwards the requested update information together with the request ID and the sensor ID to E-SM 8-1 in message 106b. In response to message 106b, E-SM 8-1 sends a confirmation message 106c back to gNB 7. The confirmation message 106c may include the request ID and the sensor ID. In response to message 106c, gNB 7 forwards a confirmation of receipt of the requested update information to sensor 1 in message 106d. Message 106d may include the request ID and the SMID. In addition, E-SM 8-1 may send a sensor database update request message 107 to SM-F 8-2. Message 107 may include the update information and the sensor ID.

[0137] In some embodiments, the SM may configure one or more sensors to satisfy the perceived service request with a sufficient (e.g., the highest possible) quality of service. Such configuration may involve sending a message to the sensor using configuration instructions via a network node (e.g., a gNB) providing network access. Such sensor configuration may be performed in the initial setup of the sensor to satisfy the perceived service request, for example, as part of a probe message such as messages 47a and 87a. Configuring the sensor may include adjusting the operation, mode, position, orientation, or a combination thereof of each of the one or more sensors. Such a configuration may be set so as to obtain a set of optimal or at least sufficient sensor measurements. In response to these configuration instructions from the SM, the sensor may be repositioned, recalibrated, or otherwise adjusted to perform certain operations. The SM may determine the configuration instructions through calculations such as optimization calculations.

[0138] Accordingly, the SM may adjust or optimize the configuration, position, orientation, and / or angle of the sensors that have been registered with the SM. To support this, the SM may run one or more optimization functions and send the results to the sensors (that have been registered in the sensor database) to be used to satisfy the sensing service request in the form of control messages transmitted by the network nodes. The sensors may then perform operations to implement the instructions in the control messages and then begin the process of satisfying the sensing request, as described elsewhere herein.

[0139] In some embodiments, for example, by adjusting sensors as described above, the SM can adjust (e.g., optimize) the sensing capabilities of the network nodes that provide network access. Additionally or alternatively, the SM can adjust (e.g., optimize) the sensing capabilities of the network nodes by having additional sensors register to associate or connect with the network nodes. These additional sensors may be owned by one or more sensor providers (e.g., a network operator or one or more third parties).

[0140] In some embodiments, the SM may query its sensor database and determine whether certain additional sensors (e.g., additional types of sensors, additional numbers of sensors, or both) are needed, either in general or to satisfy the perception service request. After determining that additional sensors are needed, the SM may send a request to one or more sensor providers (e.g., a network operator, a third party, or other one or more entities), including detailed information about the additional sensors required. The request may be sent to the recipient through a network node (e.g., a gNB) that provides network access or through other routes. When the sensor provider receives the request, if the requested one or more sensors can be provided within a limited time frame to satisfy the perception service request, the one or more sensors may be deployed and used to satisfy the perception service request. Once the deployed sensors come into the vicinity of the network node, a registration process may be performed with the SMF, and the SMF may add the sensors to the database accordingly, and then instruct their operation. The perception process then continues as described elsewhere in this document.

[0141] Fig.11 1 is a block diagram of an electronic device 6 represented as a user equipment (UE) (or a sensing consumer or mobile device) in the present disclosure. For example, a computer equipped with network functions can be configured as the electronic device 6. The electronic device 6 may correspond to a portion of a sensing consumer (UE), a network node (e.g., a gNB) providing network access, or a network node providing part or all of the sensing manager functions.

[0142] As shown, device 6 includes a processor 111 (e.g., a central processing unit (CPU) or a special processor (e.g., a graphics processing unit (GPU) or other such processor unit)), a memory 140, a non-transitory mass storage 112, an I / O interface 115, a network interface 113, and a transceiver 116, all of which are communicatively coupled via a bidirectional bus 117. According to certain embodiments, any or all of the units described may be utilized, or only a subset of the units may be utilized. In addition, device 6 may include multiple instances of certain units, such as multiple processors, multiple memories, or multiple transceivers. In addition, units in the hardware device may be directly coupled to other units without a bidirectional bus. In addition to or in place of the processor and memory, other electronic devices such as integrated circuits may also be used to perform the required logical operations.

[0143] The memory 114 may include any type of non-transitory memory, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous DRAM (SDRAM), read-only memory (ROM), or any combination thereof. The mass storage element 112 may include any type of non-transitory storage device, such as a solid-state drive, a hard disk drive, a disk drive, an optical drive, a USB drive, or any computer program product for storing data and machine executable program code. According to some embodiments, the memory 114 or the mass storage 112 may record thereon statements and instructions executed by the processor 111 for performing any of the above-mentioned method operations.

[0144] Within the scope of the present technology, a computer program product or program element is provided, or a program storage or storage device such as a magnetic wire, tape, disk or optical fiber, optical tape or optical disc, for storing machine-readable signals for controlling the operation of a computer according to the method of the present technology and / or for constructing some or all of its components according to the system of the present technology.

[0145] The actions associated with the methods described herein may be implemented as coded instructions in a computer program product. In other words, a computer program product is a computer-readable medium on which software codes are recorded to perform the methods when the computer program product is loaded into a memory and executed on a microprocessor of a wireless communication device.

[0146] In addition, each operation of the method can be performed on any computing device such as a personal computer, a server, a PDA, and according to one or more program units, modules or objects or a part of the one or more program units, modules or objects generated from any programming language such as C++, Java, etc. In addition, each operation or a file or object that implements each operation can be performed by dedicated hardware or a circuit module designed for this purpose.

[0147] Through the description of the above embodiments, the present invention can be implemented only by hardware, or by software and necessary general hardware platforms. Based on this understanding, the technical solution of the present invention can be embodied in the form of a software product. The software product can be stored in a non-volatile or non-transient storage medium, which can be a compact disk read-only memory (CD-ROM), a USB flash drive, or a removable hard disk. The software product includes many instructions that enable a computer device (a personal computer, a server, or a network device) to perform the method provided in the embodiment of the present invention. For example, such execution may correspond to the simulation of the logical operation described herein. The software product may additionally or alternatively include a plurality of instructions that enable a computer device to perform operations for configuring or programming a digital logic device according to an embodiment of the present invention.

[0148] Although the present invention has been described with reference to specific features and embodiments of the present invention, it is apparent that various modifications and combinations of the present invention may be made without departing from the present invention. Therefore, the specification and drawings are only considered as illustrations of the present invention as defined by the appended claims, and are intended to cover any and all modifications, variations, combinations or equivalents falling within the scope of the present invention.

Claims

1. A method comprising: Network nodes that provide network access: receiving a message on a predetermined wireless communication channel, wherein the predetermined wireless communication channel transmits a message for a network awareness service and a network communication service, the message indicating a request for the network awareness service; Coordinate with an awareness manager function to satisfy the request for the network awareness service using sensors registered with the awareness manager function.

2. The method according to claim 1, wherein: The coordinating with the sensor manager function is performed upon detecting that the message is indicative of the request for the network-aware service, the detecting being performed at least in part by distinguishing the message from a message indicative of a request for a communication service.

3. The method according to claim 1, wherein: The perception manager function includes a first entity and a second entity, wherein the first entity is co-located with the network node or located at another location at the edge of the communication and perception network, and the second entity is located at the core of the communication and perception network or located at another location away from the edge of the communication and perception network.

4. The method according to any one of claims 1 to 3, wherein: The predetermined wireless communication channel is a physical uplink control channel (PUCCH), and the message has a standardized uplink control information (UCI) format of type 2, 3 or 4.

5. The method according to any one of claims 1 to 4, wherein: The message comprises at least one predetermined bit, the at least one predetermined bit being set to a predetermined value to indicate the request for the network-aware service.

6. The method according to any one of claims 1 to 5, further comprising: Prior to said coordinating with the awareness manager function, interacting with an access and mobility management function (AMF) to authenticate said request for said network awareness service.

7. The method according to any one of claims 1 to 6, further comprising: Request and receive detailed information of the request for the network awareness service, wherein the detailed information of the request for the network awareness service includes one or both of the following: a location to be sensed; and perception-related information required to satisfy the request for the network awareness service.

8. The method according to claim 7, wherein: The detailed information of the request for the network awareness service includes: indicating communications resources; The detailed information of receiving the request for the network awareness service includes: The detailed information is received via the communication resource.

9. The method according to any one of claims 1 to 8, wherein: The coordination with the perception manager function includes: Sending detailed information of the request for the network awareness service to the awareness manager function, wherein the detailed information of the request for the network awareness service includes one or both of the following: a location to be sensed; and awareness-related information required to satisfy the request for the network awareness service; receiving from the awareness manager function a first indication of one or more sensors for satisfying the request for the network awareness service and a second indication of desired awareness data from each of the one or more sensors; According to the first indication and the second indication, interact with the one or more sensors to obtain the required perception data from each of the one or more sensors.

10. The method according to claim 9, wherein: The awareness manager function comprises a first entity and a second entity, the first entity being co-located with the network node or located elsewhere at the edge of the communication and awareness network, the second entity being located at the core of the communication and awareness network or located elsewhere away from the edge of the communication and awareness network; The sending of the detailed information of the request for the network awareness service to the awareness manager function comprises: sending the detailed information to the second entity; Receiving the first indication and the second indication includes: receiving the first indication and the second indication from the second entity.

11. The method according to claim 10, further comprising: After receiving the first indication and the second indication from the second entity, interacting with the first entity to confirm the first indication and the second indication.

12. The method according to claim 9, wherein: The interacting with the one or more sensors includes: indicating to each of the one or more sensors the communication resources allocated to the one or more sensors for providing the perception data to the network node, and receiving the perception data that can be used to satisfy the request for the network perception service through the communication resources allocated to the one or more sensors for use.

13. The method according to claim 9, further comprising: After receiving the first indication from the awareness manager function, indicating communication resources to an initiator of the request for the network awareness service or a related device, wherein the network node uses the communication resources to send the awareness data associated with the awareness request to the initiator or the related device.

14. The method according to any one of claims 1 to 13, further comprising: receiving sensing data that can be used to satisfy the request for the network sensing service; communicating with the awareness manager function to verify that the received awareness data satisfies the request of the network awareness service; After verifying that the received sensing data satisfies the request of the network sensing service, the sensing data is provided to the initiator of the request of the network sensing service or the related device.

15. The method according to claim 14, wherein: The awareness manager function comprises a first entity and a second entity, the first entity being co-located with the network node or located elsewhere at the edge of the communication and awareness network, the second entity being located at the core of the communication and awareness network or located elsewhere away from the edge of the communication and awareness network; The communicating with the awareness manager function to verify that the received awareness data satisfies the request for the network awareness service includes communicating with the first entity.

16. The method according to any one of claims 1 to 15, further comprising: After determining that the request for the network-aware service has been satisfied, a utility report is sent to the AMF or other network functions indicating that the request for the network-aware service has been satisfied, wherein the utility report can be used to charge for satisfying the request for the network-aware service.

17. The method according to claim 16, wherein: The utility report includes an indication of an amount of resources consumed in satisfying the request for the network-aware service.

18. The method according to any one of claims 1 to 17, further comprising: Interact with one or more sensors to initialize and maintain one or more of: a registration of the one or more sensors in a database accessible to the perception manager function, the registration including the location and capabilities of the one or more sensors; a configuration of the one or more sensors to satisfy the perception service request with sufficient quality of service; and communication resources available for communication between the network node and the one or more sensors.

19. The method according to any one of claims 1 to 18, further comprising: Interacting with the perception manager function to register the one or more sensors with the perception manager function.

20. The method according to claim 19, wherein: The interacting with the perception manager function includes: receiving from the perception manager function: an indication to update a status of at least one of the one or more sensors at a specified update frequency; The status of the at least one sensor of the one or more sensors is reported to the perception manager function at the specified update frequency.

21. The method according to claim 19, wherein: The interacting with the perception manager function includes: receiving a request from the perception manager to update a state of at least one of the one or more sensors; In response to the request, the state of the at least one sensor among the one or more sensors is reported to the perception manager.

22. The method according to any one of claims 20 to 21, wherein: The reported status includes one or more of the following: sensor responsiveness, sensor capability, and sensor location.

23. The method according to any one of claims 1 to 22, further comprising: Interact with the perception manager function to: receiving a configuration instruction for configuring one or more of the sensors to satisfy the sensing service request, and forwarding the instruction to the one or more of the sensors; or Receive a request for one or more other sensors to be registered with the perception manager function, and forward the request for the one or more other sensors to one or more sensor providers.

24. A method comprising: One or more network nodes that implement the Awareness Manager functionality: maintaining information indicative of the location and capabilities of one or more sensors local to the perception manager function; Receiving detailed information of a request for a network awareness service from a network node providing network access, wherein the detailed information of the request for the network awareness service includes one or both of the following: a location to be sensed; and awareness-related information required to satisfy the request for the network awareness service; Sending a first indication of one or more sensors for satisfying the request for the network sensing service and a second indication of required sensing data from each of the one or more sensors to the network node providing network access, wherein the first indication and the second indication are based on the maintained information.

25. The method according to claim 24, wherein: The perception manager function includes a first entity and a second entity, wherein the first entity is co-located with the network node providing network access or located at other locations at the edge of the communication and perception network, and the second entity is located at the core of the communication and perception network or located at other locations away from the edge of the communication and perception network.

26. The method according to claim 25, wherein: The maintaining information indicating locations and capabilities of the one or more sensors, the receiving details of the request for the network-aware service, and the sending the first indication and the second indication are performed by the second entity.

27. The method according to claim 26, further comprising: The first entity interacts with the network node providing network access to confirm the first indication and the second indication.

28. The method according to any one of claims 24 to 27, further comprising: receiving sensory data from the network node providing network access, wherein the sensory data originates from the one or more sensors; When the perception data satisfies the request for the network perception service, an indication that the perception data satisfies the request for the network perception service is sent to the network node providing network access.

29. The method according to claim 28, wherein: The awareness manager function comprises a first entity and a second entity, the first entity being co-located with the network node providing network access or located at another location at the edge of the communication and awareness network, the second entity being located at the core of the communication and awareness network or located at another location away from the edge of the communication and awareness network; The receiving of the sensing data and the sending of the indication of the sensing data satisfying the request for the network sensing service are performed by the first entity.

30. The method according to any one of claims 24 to 29, further comprising: After determining that the request for the network-aware service has been met, a utility report is sent to an access and mobility management function (AMF) or other network function indicating that the request for the network-aware service has been met, wherein the utility report can be used to charge for meeting the request for the network-aware service.

31. The method according to any one of claims 24 to 30, further comprising: One or more quality of service (QoS) requirements associated with content of the sensory data are monitored and processed.

32. The method according to any one of claims 24 to 27, further comprising: Determining whether a sensor local to the network node providing network access can satisfy the request for the network awareness service; When the sensor local to the network node providing network access can satisfy the request for the network awareness service, the first indication and the second indication are sent.

33. The method of claim 32, further comprising: When the sensor local to the network node providing network access cannot satisfy the request for the network awareness service, it is indicated that the sensor local to the network node providing network access cannot satisfy the request for the network awareness service.

34. The method according to any one of claims 24 to 33, further comprising: sending a configuration instruction for configuring one or more of the sensors to satisfy the sensing service request; or Sending a request for one or more additional sensors to be registered with the perception manager function.

35. A method comprising: Mobile devices connected to the network: A message is sent to a network node on a predetermined wireless communication channel, wherein the predetermined wireless communication channel is used to support network awareness services and network communication services, the network node provides access to the network, and the message is used to indicate a request for the network awareness service.

36. The method of claim 35, wherein: The message is a message on a physical uplink control channel (PUCCH) having a standardized uplink control information (UCI) format of type 2, 3 or 4.

37. The method according to claim 35 or 36, wherein: The message comprises at least one predetermined bit, the at least one predetermined bit being set to a predetermined value to indicate the request for the network-aware service.

38. The method according to any one of claims 35 to 37, further comprising: Receiving a request for detailed information of the request for the network awareness service, wherein the detailed information of the request for the network awareness service includes one or both of the following: a location to be sensed; and awareness-related information required to satisfy the request for the network awareness service; The detailed information of the request for the network-aware service is sent to the network node.

39. The method of claim 38, further comprising: receiving, together with the request for the detailed information of the request for the network-aware service, an indication of communication resources allocated for further communication with the network node regarding the request for the network-aware service, wherein the detailed information of the request for the network-aware service is sent via the communication resources.

40. The method according to any one of claims 35 to 39, further comprising: receiving sensing data from said network node providing access to said network; When the sensing data satisfies the request for the network awareness service, an indication that the sensing data satisfies the request for the network awareness service is sent to the network node providing access to the network.

41. The method of claim 40, further comprising: A determination is made whether the sensed data satisfies the request for the network sensing service based at least in part on evaluating whether the sensed data satisfies one or more quality of service (QoS) requirements associated with content of the sensed data.

42. A method comprising a combination of the method of any one of claims 1 to 23 and the method of any one of claims 24 to 34.

43. A network node providing network access, for: receiving a message on a predetermined wireless communication channel, the predetermined wireless communication channel transmitting messages for a network awareness service and a network communication service, the message indicating a request for the network awareness service; Coordinate with an awareness manager function to satisfy the request for the network awareness service using sensors registered with the awareness manager function.

44. The network node according to claim 43, wherein: The coordinating with the sensor manager function is performed upon detecting that the message is indicative of the request for the network-aware service, the detecting being performed at least in part by distinguishing the message from a message indicative of a request for a communication service.

45. The network node of claim 43, wherein: The perception manager function includes a first entity and a second entity, wherein the first entity is co-located with the network node or located at other locations at the edge of the communication and perception network, and the second entity is located at the core of the communication and perception network or located at other locations away from the edge of the communication and perception network.

46. ​​A network node according to any one of claims 43 to 45, wherein: The predetermined wireless communication channel is a physical uplink control channel (PUCCH), and the message has a standardized uplink control information (UCI) format of type 2, 3 or 4.

47. A network node according to any one of claims 43 to 46, wherein: The message comprises at least one predetermined bit, the at least one predetermined bit being set to a predetermined value to indicate the request for the network-aware service.

48. The network node according to any one of claims 43 to 47 is further used to: interact with an access and mobility management function (AMF) to authenticate the request for the network awareness service before coordinating with the awareness manager function.

49. The network node according to any one of claims 43 to 48, further configured to: request and receive detailed information of the request for the network-aware service, wherein: The detailed information of the request for the network awareness service includes one or both of the following: a location to be sensed; Awareness-related information required to satisfy the request for the network awareness service.

50. The network node of claim 49, wherein: The detailed information of the request for the network awareness service includes: indicating communications resources; The detailed information of receiving the request for the network awareness service includes: The detailed information is received via the communication resource.

51. A network node according to any one of claims 43 to 50, wherein: The coordination with the perception manager function includes: Sending detailed information of the request for the network awareness service to the awareness manager function, wherein the detailed information of the request for the network awareness service includes one or both of the following: a location to be sensed; and awareness-related information required to satisfy the request for the network awareness service; receiving from the awareness manager function a first indication of one or more sensors for satisfying the request for the network awareness service and a second indication of desired awareness data from each of the one or more sensors; According to the first indication and the second indication, interact with the one or more sensors to obtain the required perception data from each of the one or more sensors.

52. The network node of claim 51, wherein: The awareness manager function comprises a first entity and a second entity, the first entity being co-located with the network node or located elsewhere at the edge of the communication and awareness network, the second entity being located at the core of the communication and awareness network or located elsewhere away from the edge of the communication and awareness network; The sending of the detailed information of the request for the network awareness service to the awareness manager function comprises: sending the detailed information to the second entity; The receiving the first indication and the second indication includes: receiving the first indication and the second indication from the second entity.

53. The network node of claim 52, further configured to interact with the first entity to confirm the first indication and the second indication after receiving the first indication and the second indication from the second entity.

54. The network node of claim 51, wherein: The interacting with the one or more sensors includes: indicating to each of the one or more sensors the communication resources allocated to the one or more sensors for providing the perception data to the network node, and receiving the perception data that can be used to satisfy the request for the network perception service through the communication resources allocated to the one or more sensors for use.

55. The network node according to claim 51 is further configured to: after receiving the first indication from the awareness manager function, indicate communication resources to the initiator of the request for the network awareness service or a related device, wherein The network node sends the sensing data associated with the sensing request to the initiator or the related device using the communication resources.

56. The network node according to any one of claims 43 to 55, further configured to: receiving sensing data that can be used to satisfy the request for the network sensing service; communicating with the awareness manager function to verify that the received awareness data satisfies the request of the network awareness service; After verifying that the received sensing data satisfies the request of the network sensing service, the sensing data is provided to the initiator of the request of the network sensing service or the related device.

57. The network node of claim 56, wherein: The awareness manager function comprises a first entity and a second entity, the first entity being co-located with the network node or located elsewhere at the edge of the communication and awareness network, the second entity being located at the core of the communication and awareness network or located elsewhere away from the edge of the communication and awareness network; The communicating with the awareness manager function to verify that the received awareness data satisfies the request for the network awareness service includes communicating with the first entity.

58. The network node according to any one of claims 43 to 57 is further configured to: after determining that the request for the network-aware service has been satisfied, send a utility report to an AMF or other network function that the request for the network-aware service has been satisfied, wherein: The utility report may be used to bill for satisfying the request for the network-aware service.

59. The network node of claim 57, wherein: The utility report includes an indication of an amount of resources consumed in satisfying the request for the network-aware service.

60. The network node according to any one of claims 43 to 59 is also used to: interact with one or more sensors to initialize and maintain one or both of the following: registration of the one or more sensors in a database accessible to the perception manager function, the registration including the location and capabilities of the one or more sensors; communication resources that can be used for communication between the network node and the one or more sensors.

61. The network node according to any one of claims 43 to 60, further configured to interact with the perception manager function to register the one or more sensors with the perception manager function.

62. The network node according to claim 61, wherein: The interacting with the perception manager function includes: receiving from the perception manager function: an indication to update a status of at least one of the one or more sensors at a specified update frequency; The status of the at least one sensor of the one or more sensors is reported to the perception manager function at the specified update frequency.

63. The network node of claim 61, wherein: The interacting with the perception manager function includes: receiving a request from the perception manager to update a state of at least one of the one or more sensors; In response to the request, the state of the at least one sensor among the one or more sensors is reported to the perception manager.

64. A network node according to any one of claims 62 to 63, wherein: The reported status includes one or more of the following: sensor responsiveness, sensor capability, and sensor location.

65. An apparatus comprising an awareness manager function implemented by one or more network nodes, wherein: The perception manager function is used to: maintaining information indicative of the location and capabilities of one or more sensors local to the perception manager function; Receiving detailed information of a request for a network awareness service from a network node providing network access, wherein the detailed information of the request for the network awareness service includes one or both of the following: a location to be sensed; and awareness-related information required to satisfy the request for the network awareness service; Sending a first indication of one or more sensors for satisfying the request for the network sensing service and a second indication of required sensing data from each of the one or more sensors to the network node providing network access, wherein the first indication and the second indication are based on the maintained information.

66. The apparatus of claim 65, wherein: The perception manager function includes a first entity and a second entity, wherein the first entity is co-located with the network node providing network access or located at other locations at the edge of the communication and perception network, and the second entity is located at the core of the communication and perception network or located at other locations away from the edge of the communication and perception network.

67. The apparatus of claim 66, wherein: The maintaining information indicating locations and capabilities of the one or more sensors, the receiving details of the request for the network-aware service, and the sending the first indication and the second indication are performed by the second entity.

68. The apparatus of claim 67, wherein: The first entity is used to interact with the network node providing network access to confirm the first indication and the second indication.

69. The device according to any one of claims 65 to 68, further used for: Receiving sensing data from the network node providing network access, wherein: The sensory data is derived from the one or more sensors; When the perception data satisfies the request for the network perception service, an indication that the perception data satisfies the request for the network perception service is sent to the network node providing network access.

70. The apparatus of claim 69, wherein: The awareness manager function comprises a first entity and a second entity, the first entity being co-located with the network node providing network access or located at another location at the edge of the communication and awareness network, the second entity being located at the core of the communication and awareness network or located at another location away from the edge of the communication and awareness network; The receiving of the sensing data and the sending of the indication of the sensing data satisfying the request for the network sensing service are performed by the first entity.

71. The apparatus according to any one of claims 65 to 70, further configured to: after determining that the request for the network-aware service has been satisfied, send a utility report to an access and mobility management function (AMF) or other network function that the request for the network-aware service has been satisfied, wherein: The utility report may be used to bill for satisfying the request for the network-aware service.

72. The apparatus of any one of claims 65 to 71, further configured to monitor and process one or more quality of service (QoS) requirements associated with content of the sensory data.

73. The device according to any one of claims 65 to 68 is also used to: determine whether the sensor local to the network node providing network access can meet the request for the network awareness service; when the sensor local to the network node providing network access can meet the request for the network awareness service, send the first indication and the second indication.

74. The apparatus according to claim 73 is further used to indicate that the sensor local to the network node providing network access cannot satisfy the request for the network awareness service when the sensor local to the network node providing network access cannot satisfy the request for the network awareness service.

75. A mobile device for accessing a network, used for: Sending a message to a network node on a predetermined wireless communication channel, wherein: The predetermined wireless communication channel is used to support a network-aware service and a network communication service, the network node provides access to the network, and the message is used to indicate a request for the network-aware service.

76. The mobile device of claim 75, wherein: The message is a message on a physical uplink control channel (PUCCH) having a standardized uplink control information (UCI) format of type 2, 3 or 4.

77. A mobile device according to claim 75 or 76, wherein The message comprises at least one predetermined bit, the at least one predetermined bit being set to a predetermined value to indicate the request for the network-aware service.

78. The mobile device according to any one of claims 75 to 77, further configured to: receiving a request for details of the request for the network-aware service, wherein: The detailed information of the request for the network awareness service includes one or both of the following: a location to be sensed; The perception-related information required to satisfy the request for the network perception service; The detailed information of the request for the network-aware service is sent to the network node.

79. The mobile device of claim 78, further configured to receive, together with the request for the detailed information of the request for the network-aware service, an indication of communication resources allocated for further communication with the network node regarding the request for the network-aware service, wherein The detailed information of the request for the network-aware service is sent via the communication resource.

80. The mobile device according to any one of claims 75 to 79, further configured to: receiving sensing data from said network node providing access to said network; When the sensing data satisfies the request for the network awareness service, an indication that the sensing data satisfies the request for the network awareness service is sent to the network node providing access to the network.

81. The mobile device of claim 80, further configured to determine whether the sensed data satisfies the request for the network sensing service based at least in part on evaluating whether the sensed data satisfies one or more quality of service (QoS) requirements associated with content of the sensed data.

82. A system comprising a combination of a network node according to any one of claims 43 to 64 and an apparatus according to any one of claims 65 to 74.

83. A computer program product comprising a non-transitory computer readable medium having recorded thereon statements and instructions, wherein: When the statements and instructions are executed on one or more computers, the one or more computers are caused to implement the method according to any one of claims 1 to 42.

Images