Communication method, communication device, communication system, storage medium and program product
By requesting the sensing entity to revoke the sensing service through the sensing function, the problem of the sensing service not being able to terminate in a timely manner is solved, thus realizing the timely release of resources and improving system performance.
Patent Information
- Application Number
- PCT/CN2025/094062
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-09
- Publication Date
- 2026-11-12
AI Technical Summary
In existing communication systems, sensing services cannot be terminated in a timely manner, resulting in wasted resources and degraded system performance.
By sending a request to the sensing entity through the sensing function to revoke the sensing service, the sensing service is actively terminated, and related resources are released.
Stop unnecessary sensing operations in a timely manner to improve system performance, free up resources, and enhance the accuracy and efficiency of system operations.
Smart Images

Figure CN2025094062_12112026_PF_FP_ABST
Abstract
Description
Communication methods, communication equipment, communication systems, storage media and software products Technical Field
[0001] This disclosure relates to the field of communication technology, and in particular to a communication method, communication device, communication system, storage medium, and program product. Background Technology
[0002] Integrated Sensing and Communication (ISAC) is a novel communication technology that integrates sensing capabilities into the design of communication systems. This allows communication systems to provide sensing as a service along with communication to users. By sending and receiving sensing signals, network devices / terminals can sense information such as the distance, speed, and angle of targets / environments, thereby acquiring information about the surrounding targets / environment. Summary of the Invention
[0003] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.
[0004] According to a first aspect of the embodiments of this disclosure, a communication method is provided, executed by a sensing function, the method comprising:
[0005] A first request is sent to the sensing entity, the first request being used to request the sensing entity to revoke the sensing service.
[0006] According to a second aspect of the embodiments of this disclosure, a communication method is provided, performed by a sensing entity, the method comprising:
[0007] The system receives a first request from the sensing function, which requests the sensing entity to revoke the sensing service.
[0008] According to a third aspect of the embodiments of this disclosure, a communication method is provided, executed by a node, the method comprising:
[0009] Receive a revocation notification sent by the sensing function, the revocation notification including the reason for revoking the sensing service.
[0010] According to a fourth aspect of the embodiments of this disclosure, a sensing function is proposed, including:
[0011] The transceiver module is configured to send a first request to the sensing entity, the first request being used to request the sensing entity to revoke the sensing service.
[0012] According to a fifth aspect of the embodiments of this disclosure, a sensing entity is proposed, comprising:
[0013] The transceiver module is configured to receive a first request sent by the sensing function, the first request being used to request the sensing entity to revoke the sensing service.
[0014] According to a sixth aspect of the embodiments of this disclosure, a node is provided, comprising:
[0015] The transceiver module is configured to receive a revocation notification sent by the sensing function, the revocation notification including the reason for revoking the sensing service.
[0016] According to a seventh aspect of the present disclosure, a communication device is provided that can be used to perform the methods described in an optional implementation of the first, second, or third aspect.
[0017] According to an eighth aspect of the present disclosure, a communication system is proposed, including a sensing function, a sensing entity, and a node, wherein the sensing function is configured to perform a method as described in an optional implementation of the first aspect, the sensing entity is configured to perform a method as described in an optional implementation of the second aspect, and the node is configured to perform a method as described in an optional implementation of the third aspect.
[0018] According to a ninth aspect of the present disclosure, a storage medium is provided that stores instructions that, when executed on a communication device, cause the communication device to perform a method as described in an optional implementation of the first, second, or third aspect.
[0019] According to a tenth aspect of the present disclosure, a program product is provided, comprising at least one of a program and instructions, wherein the program and instructions, when executed by a communication device, implement the method described in an optional implementation of the first, second, or third aspect.
[0020] The technical solution provided in this disclosure can produce the following beneficial effects: the sensing function sends a first request to the sensing entity, the first request being used to request the sensing entity to revoke the sensing service. By requesting the sensing entity to revoke the sensing service through the sensing function, the sensing service can be actively terminated, thereby releasing relevant resources in a timely manner, stopping unnecessary sensing operations, and improving system performance.
[0021] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description
[0022] To more clearly illustrate the technical solutions in the embodiments of this disclosure, the accompanying drawings required for the description of the embodiments are introduced below. The following drawings are only some embodiments of this disclosure and do not impose specific limitations on the protection scope of this disclosure.
[0023] Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.
[0024] Figure 2 is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure.
[0025] Figure 3A is a flowchart illustrating a communication method according to an embodiment of the present disclosure.
[0026] Figure 3B is a flowchart illustrating a communication method according to an embodiment of the present disclosure.
[0027] Figure 3C is a flowchart illustrating a communication method according to an embodiment of the present disclosure.
[0028] Figure 4 is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure.
[0029] Figure 5A is a schematic diagram of the structure of a sensing function proposed in an embodiment of this disclosure.
[0030] Figure 5B is a schematic diagram of the structure of a sensing entity proposed in an embodiment of this disclosure.
[0031] Figure 5C is a schematic diagram of the structure of a node proposed in an embodiment of this disclosure.
[0032] Figure 6A is a schematic diagram of the structure of the communication device proposed in an embodiment of this disclosure.
[0033] Figure 6B is a schematic diagram of the chip structure proposed in an embodiment of this disclosure. Detailed Implementation
[0034] This disclosure provides a communication method, communication device, communication system, storage medium, and program product.
[0035] In a first aspect, embodiments of this disclosure propose a communication method executed by a sensing function, the method comprising:
[0036] A first request is sent to the sensing entity, the first request being used to request the sensing entity to revoke the sensing service.
[0037] In the above embodiments, by requesting the sensing entity to revoke the sensing service through the sensing function, the sensing service can be actively terminated, thereby releasing relevant resources in a timely manner, stopping unnecessary sensing operations, and improving system performance.
[0038] In conjunction with some embodiments of the first aspect, in some embodiments, the first request includes at least one of the following: the identifier of the sensing entity, the identifier of the sensing service.
[0039] In the above embodiments, the request to revoke the sensing service includes the identifier of the sensing entity and / or the identifier of the sensing service, which can accurately revoke a specific sensing service provided by a specific sensing entity, thereby improving the accuracy and efficiency of the operation.
[0040] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes at least one of the following:
[0041] Receive a second request, which is used to request the cancellation of the perception service;
[0042] Receive a trigger message for revoking the sensing service, the trigger message including at least one of the following: the authorization for the sensing service is revoked, or the sensing area cannot provide the sensing service.
[0043] The above embodiments can flexibly respond to service cancellation requests in different scenarios, improving the system's adaptability.
[0044] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:
[0045] Receive a response message sent by the sensing entity, the response message including the cancellation result of the sensing service.
[0046] In the above embodiments, by receiving a response message containing the cancellation result from the sensing entity, closed-loop confirmation of the cancellation operation of the sensing service can be achieved, ensuring that the system obtains accurate operation status feedback.
[0047] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:
[0048] Send a revocation notification to the node that requested the sensing service, the revocation notification including the reason for revoking the sensing service.
[0049] In the above embodiments, by sending a cancellation notification containing the reason for cancellation to the node requesting the awareness service, the node can clearly understand the reason for the service termination, thereby improving the transparency of system interaction and collaborative efficiency.
[0050] In conjunction with some embodiments of the first aspect, in some embodiments, the sensing entity includes at least one of the following: a sensing signal transmitter and a sensing signal receiver.
[0051] In the above embodiments, comprehensive management of the sensing signal transmission and reception functions can be achieved, ensuring the integrity and effectiveness of the termination of sensing services.
[0052] Secondly, embodiments of this disclosure propose a communication method performed by a sensing entity, the method comprising:
[0053] The system receives a first request from the sensing function, which requests the sensing entity to revoke the sensing service.
[0054] In conjunction with some embodiments of the second aspect, in some embodiments, the first request includes at least one of the following: the identifier of the sensing entity, the identifier of the sensing service.
[0055] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:
[0056] Terminate the perception service.
[0057] In the above embodiments, by terminating the sensing service, the corresponding sensing operation can be stopped directly, thereby releasing system resources in a timely manner and preventing the continuous operation of invalid services.
[0058] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:
[0059] Delete the configuration and / or parameters related to the perception service.
[0060] In the above embodiments, by deleting the configurations and / or parameters related to the perception service, service anomalies or resource redundancy caused by residual data can be avoided, thereby improving system performance.
[0061] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:
[0062] Send a response message to the sensing function, the response message including the cancellation result of the sensing service.
[0063] In conjunction with some embodiments of the second aspect, in some embodiments, the sensing entity includes at least one of the following: a sensing signal transmitter and a sensing signal receiver.
[0064] Thirdly, embodiments of this disclosure propose a communication method executed by a node, the method comprising:
[0065] Receive a revocation notification sent by the sensing function, the revocation notification including the reason for revoking the sensing service.
[0066] In conjunction with some embodiments of the third aspect, in some embodiments, the node is used to request the perception service.
[0067] Fourthly, embodiments of this disclosure propose a sensing function, which may include at least one of a transceiver module and a processing module; wherein the sensing function may be used to perform an optional implementation of the first aspect.
[0068] Fifthly, embodiments of this disclosure propose a sensing entity, which may include at least one of a transceiver module and a processing module; wherein the sensing entity may be used to perform an optional implementation of the second aspect.
[0069] In a sixth aspect, embodiments of this disclosure propose a node that may include at least one of a transceiver module and a processing module; wherein the node may be used to execute an optional implementation of the third aspect.
[0070] In a seventh aspect, embodiments of this disclosure provide a sensing function that may include one or more processors; wherein the sensing function may be used to perform an optional implementation of the first aspect.
[0071] In an eighth aspect, embodiments of this disclosure provide a sensing entity that may include one or more processors; wherein the sensing entity may be used to perform an optional implementation of the second aspect.
[0072] In a ninth aspect, embodiments of this disclosure provide a node that may include one or more processors; wherein the node may be used to perform an optional implementation of the third aspect.
[0073] In a tenth aspect, embodiments of this disclosure provide a communication system that may include: a sensing function, a sensing entity, and a node; wherein the sensing function is configured to perform the method described in the optional implementation of the first aspect, the sensing entity is configured to perform the method described in the optional implementation of the second aspect, and the node is configured to perform the method described in the optional implementation of the third aspect.
[0074] Eleventhly, embodiments of this disclosure provide a storage medium storing instructions that, when executed on a communication device, cause the communication device to perform the method as described in an optional implementation of the first, second, or third aspect.
[0075] In a twelfth aspect, embodiments of this disclosure provide a program product that, when executed by a communication device, causes the communication device to perform the method as described in an optional implementation of the first, second, or third aspect.
[0076] In a thirteenth aspect, embodiments of this disclosure provide a computer program that, when run on a computer, causes the computer to perform the methods described in an optional implementation of the first, second, or third aspect.
[0077] In a fourteenth aspect, embodiments of this disclosure provide a chip or chip system. The chip or chip system includes processing circuitry configured to perform the methods described in optional implementations of the first, second, or third aspects.
[0078] It is understood that the aforementioned sensing functions, sensing entities, nodes, communication devices, communication systems, storage media, program products, computer programs, chips, or chip systems can all be used to execute the methods proposed in the embodiments of this disclosure. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.
[0079] This disclosure provides a communication method, communication device, communication system, storage medium, and program product. In some embodiments, the terms "information transmission method" and "information processing method," "communication method," etc., can be used interchangeably; the terms "information transmission device" and "information processing device," "communication device," "communication equipment," etc., can be used interchangeably; and the terms "information processing system," "communication system," etc., can be used interchangeably.
[0080] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.
[0081] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.
[0082] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.
[0083] In this embodiment of the disclosure, unless otherwise stated, elements expressed in the singular form, such as "a," "an," "the," "the," "the," "the," "the," "the," "this," etc., can mean "one and only one," or "one or more," "at least one," etc. For example, when using articles such as "a," "an," "the," etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.
[0084] In some embodiments, "multiple" can refer to two or more.
[0085] In some embodiments, the terms “at least one of”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.
[0086] In some embodiments, the notation "at least one of A and B", "A and / or B", "A in one case, B in another", "in response to one case A, in response to another case B", etc., may include the following technical solutions depending on the situation: in some embodiments, A (execute A regardless of B); in some embodiments, B (execute B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, A and B (both A and B are executed). The same applies when there are more branches such as A, B, C, etc.
[0087] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execution of A regardless of B); in some embodiments, B (execution of B regardless of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The same applies when there are more branches such as A, B, C, etc.
[0088] The prefixes "first," "second," etc., used in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is found in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a "field," the ordinal numbers preceding "field" in "first field" and "second field" do not restrict the position or order of the "fields." "First" and "second" do not restrict whether the "fields" they modify are in the same message, nor do they restrict the order of "first field" and "second field." Similarly, if the descriptive object is a "level," the ordinal numbers preceding "level" in "first level" and "second level" do not restrict the priority between "levels." Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. For example, in "first device," the number of "devices" can be one or more. Furthermore, the objects modified by different prefixes can be the same or different. For example, if the object being described is "device", then "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the object being described is "information", then "first information" and "second information" can be the same information or different information, and their content can be the same or different.
[0089] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.
[0090] In some embodiments, the terms “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “if…”, “if…”, etc., can be used interchangeably.
[0091] In some embodiments, the terms “greater than,” “greater than or equal to,” “not less than,” “more than,” “more than or equal to,” “not less than,” “higher than,” “higher than or equal to,” “not lower than,” and “above” can be used interchangeably, as can the terms “less than,” “less than or equal to,” “not greater than,” “less than,” “less than or equal to,” “not more than,” “lower than,” “lower than or equal to,” “not higher than,” and “below”.
[0092] In some embodiments, devices, etc., may be interpreted as physical or virtual, and their names are not limited to those described in the embodiments. Terms such as “device,” “equipment,” “circuit,” “network element,” “node,” “function,” “unit,” “section,” “system,” “network,” “chip,” “chip system,” “entity,” and “subject” can be used interchangeably.
[0093] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).
[0094] In some embodiments, the terms "Access Network Device (AN Device)," "Radio Access Network Device (RAN Device)," "Base Station (BS)," "Radio Base Station," "Fixed Station," "Node," "Access Point," "Transmission Point (TP)," "Reception Point (RP)," "Transmission / Reception Point (TRP)," "Panel," "Antenna Panel," "Antenna Array," "Cell," "Macro Cell," "Small Cell," "Femto Cell," "Pico Cell," "Sector," "Cell Group," "Serving Cell," "Carrier," "Component Carrier," and "Bandwidth Part (BWP)" can be used interchangeably.
[0095] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", "subscriber station", "mobile unit", "subscriber unit", "wireless unit", "remote unit", "mobile device", "wireless device", "wireless communication device", "remote device", "mobile subscriber station", "access terminal", "mobile terminal", "wireless terminal", "remote terminal", "handset", "user agent", "mobile client", and "client" can be used interchangeably.
[0096] In some embodiments, access network devices, core network devices, or network devices can be replaced with terminals. For example, embodiments of this disclosure can also be applied to structures where communication between access network devices, core network devices, or network devices and terminals is replaced with communication between multiple terminals (e.g., device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the structure can also be configured such that the terminal has all or part of the functions of the access network device. Furthermore, terms such as "uplink" and "downlink" can be replaced with terms corresponding to communication between terminals (e.g., "sidelink"). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel or direct channel, and uplink link, downlink, etc., can be replaced with sidelink link or direct link.
[0097] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.
[0098] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.
[0099] In some embodiments, data, information, etc., may be obtained with the user's consent.
[0100] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.
[0101] Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. As shown in Figure 1, the communication system 100 may include a sensing function 101, a sensing entity 102, and a node 103.
[0102] In some embodiments, the Sensing Function (SF) 101 is used to support sensing services and is a network function involved in supporting sensing services.
[0103] In some embodiments, SF can be an independent network element in the core network, or it can be implemented by other network elements in the core network.
[0104] In some embodiments, the sensing entity 102 may include a sensing transmitter and / or a sensing receiver.
[0105] In some embodiments, node 103 may be a requester of the perception service, such as a third-party server or a perception service consumer, and the name is not limited thereto.
[0106] In some embodiments, a perception service consumer can be an entity that consumes perception results and can request perception results.
[0107] In some embodiments, the network device may include at least one of an access network device and a core network device.
[0108] In some embodiments, the access network device may be a node or device that connects a terminal device to a wireless network. The access network device may include, but is not limited to, at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation eNB (ng-eNB), next-generation Node B (gNB), node B (NB), home node B (HNB), home evolved node B (HeNB), radio backhaul device, radio network controller (RNC), base station controller (BSC), base transceiver station (BTS), base band unit (BBU), mobile switching center, base station in a 6G communication system, open RAN, cloud RAN, base station in other communication systems, and access node in a Wi-Fi system.
[0109] In some embodiments, the technical solutions of this disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within access network devices involved in the embodiments of this disclosure can be transformed into internal interfaces of Open RAN. The processes and information interactions between these internal interfaces can be implemented by software or programs.
[0110] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some protocol layer functions are centrally controlled by the CU, while the remaining part or all protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.
[0111] In some embodiments, the core network equipment may be a single device, multiple devices, or a group of devices. The core network may include at least one of the following: Evolved Packet Core (EPC), 5G Core Network (5GCN), and Next Generation Core (NGC).
[0112] In some embodiments, any one or more of the sensing function 101, sensing entity 102, and node 103 may be part of the access network device or the core network device, or may be independent of the access network device or the core network device. This disclosure does not limit this.
[0113] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions proposed in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions proposed in this disclosure are also applicable to similar technical problems.
[0114] The following embodiments of this disclosure can be applied to the communication system 100 shown in FIG1, or to some of the main bodies, but are not limited thereto. The main bodies shown in FIG1 are examples. The communication system may include all or some of the main bodies in FIG1, or may include other main bodies outside of FIG1. The number and form of each main body are arbitrary. Each main body may be physical or virtual. The connection relationship between the main bodies is an example. The main bodies may not be connected or may be connected. The connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.
[0115] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G New Radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future generation radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).
[0116] In some embodiments of this disclosure, a perception service consumer can be an entity that consumes perception results, or a perception service consumer can request perception results.
[0117] In some embodiments, a sensing entity refers to a sensing entity of a sensing transmitter or a sensing receiver.
[0118] In some embodiments, the sensing function represents the logical function that supports the sensing service.
[0119] In some embodiments, the sensing function cannot be a sensing entity.
[0120] In some embodiments, the sensing service collects and provides information about the characteristics of objects and / or the environment via radio signals.
[0121] In some embodiments, the authorization and revocation of a specific perceived service include:
[0122] Authorizing requests for sensing services and revoking ongoing sensing services;
[0123] Authorization and revocation of perception entities.
[0124] In some embodiments, the authorization of a sensing service request and the revocation of an ongoing sensing service include the following aspects:
[0125] Whether and how (if necessary) authorization for awareness service requests is performed, and the authorization criteria for awareness service requests;
[0126] Whether and how (if necessary) the revocation of the awareness service is performed, and the criteria for revocation;
[0127] Whether, how, and by which entity (if necessary) the authorization of the perception service request and the revocation of the perception service are carried out;
[0128] Whether and where to store authorization information for the perception service request and revocation information for the perception service, and whether and how (if necessary) to update the authorization and revocation information.
[0129] In some embodiments, authorization and revocation (if applicable) of a perceived entity includes the following aspects:
[0130] Whether, when, and by which entity the authorization and revocation of the perceived entity are performed;
[0131] If necessary, the granularity of entity authorization;
[0132] If necessary, the storage and management of entity authorization information.
[0133] In some embodiments, the authorization and revocation of a sensed entity are related to the discovery and selection of the sensed entity.
[0134] Figure 2 is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. This method can be executed by the aforementioned communication system. As shown in Figure 2, the method may include:
[0135] Step S2101: The sensing function receives a second request and / or a trigger message for canceling the sensing service.
[0136] In some embodiments, the sensing function may receive a second request sent by another subject and / or a trigger message for revoking the sensing service.
[0137] In some embodiments, the sensing function includes the logical functions that support the sensing service. It should be noted that the sensing function is not a sensing entity.
[0138] In some embodiments, the sensing function may provide configuration and / or parameters to the sensing entity, collect sensing measurement data from the sensing entity, process the sensing measurement data to generate sensing results, send the sensing results to the sensing service consumer, and perform the revocation of the ongoing sensing service.
[0139] In some embodiments, other entities may be user data management (UDM) or other network elements with network management functions, and this disclosure does not limit them.
[0140] In some embodiments, the sensing function may determine that the sensing service needs to be revoked based on operator policies or relevant regulations, in which case step S2101 can be omitted.
[0141] In some embodiments, the second request is used to request the cancellation of the sensing service, and the sensing function can receive the second request. For example, the sensing function can receive the second request sent by the UDM.
[0142] In some embodiments, the second request may include the identifier of the sensing entity and / or the identifier of the sensing service.
[0143] In some embodiments, the second request may be referred to as a perception service revocation request.
[0144] In some embodiments, other network elements or entities may send the second request to the sensing function if they determine that the authorization for the sensing service has been revoked or that the sensing area does not allow the provision of the sensing service.
[0145] In some embodiments, the trigger message includes at least one of the following: the authorization for the sensing service has been revoked, the sensing area cannot provide the sensing service, and the sensing function can receive the trigger message. For example, if the UDM determines that the authorization for the sensing service has been revoked, it can send the trigger message to the sensing function to request the revocation of the sensing service; or, if the UDM determines that the sensing area cannot provide the sensing service, it can send the trigger message to the sensing function to request the revocation of the sensing service.
[0146] In some embodiments, the trigger message may also be referred to as a trigger signal, trigger condition, etc., and this disclosure does not limit it.
[0147] In some embodiments, the sensing service may be to collect and provide information about the characteristics of objects and / or the environment via radio signals.
[0148] In some embodiments, the sensing service may include at least one of the following sensing operations: transmitting sensing signals, receiving sensing signals, processing sensing data to obtain sensing results, and sensing authorization.
[0149] In some embodiments, revoking a sensing service can be understood as stopping sensing operations, such as stopping the transmission of sensing signals, stopping the reception of sensing signals, stopping the processing of sensing data, and withdrawing sensing authorization.
[0150] In some embodiments, the sensing service to be withdrawn may be an ongoing sensing service.
[0151] In some embodiments, after the sensing service is initiated, sensing measurement data or sensing signals can be transmitted to the sensing function, which then sends the sensing results to the sensing service consumer. During the sensing service process, the sensing function may receive a second request and / or a trigger message for canceling the sensing service.
[0152] In some embodiments, revoking a sensing service can be understood as terminating an ongoing sensing service, or having the authorization for an ongoing sensing service withdrawn.
[0153] In some embodiments, after receiving a second request and / or a trigger message for revoking the sensing service, the sensing function may stop processing sensing data and stop sending sensing results to sensing service consumers.
[0154] Step S2102: The sensing function sends a first request to the sensing entity.
[0155] In some embodiments, the sensing entity receives a first request sent by the sensing function, but is not limited thereto. The sensing entity may also receive a first request sent by other entities, in which case step S2102 may be omitted.
[0156] In some embodiments, the first request may be used to request the sensing entity to revoke the sensing service.
[0157] In some embodiments, requesting the sensing entity to revoke the sensing service can be understood as requesting the sensing entity to stop sensing operations, such as requesting the sensing entity to stop transmitting sensing signals and / or stop receiving sensing signals.
[0158] In some embodiments, the first request may be referred to as a sensing service cancellation request or a sensing operation stop request.
[0159] In some embodiments, the sensing entity may include at least one of the following: a sensing signal transmitter and a sensing signal receiver.
[0160] For example, if the sensing entity is a sensing signal transmitter, the first request can be used to request the sensing signal transmitter to stop transmitting sensing signals; if the sensing entity is a sensing signal receiver, the first request can be used to request the sensing signal receiver to stop receiving sensing signals; if the sensing entity includes both a sensing signal transmitter and a sensing signal receiver, the first request can be used to request the sensing signal transmitter to stop transmitting sensing signals and to request the sensing signal receiver to stop receiving sensing signals.
[0161] In some embodiments, the first request may include at least one of the following: the identifier of the sensing entity, the identifier of the sensing service.
[0162] In some embodiments, if the first request includes an identifier of a sensing entity, it indicates a request for the specific sensing entity indicated by the identifier to revoke sensing services. For example, the sensing function may send the first request to a specific sensing signal transmitter to request that particular sensing signal transmitter to stop transmitting sensing signals.
[0163] In some embodiments, if the first request includes an identifier of a sensing service, it indicates a request to revoke the specific sensing service indicated by that identifier. For example, a sensing function may send the first request to a sensing signal receiver to request the receiver to stop receiving a specific sensing signal.
[0164] In some embodiments, the first request may also be referred to as a perception service revocation request.
[0165] In some embodiments, after receiving the second request or a trigger message for canceling the sensing service, the sensing function may send the first request to the sensing entity.
[0166] In some embodiments, the sensing function may also send the first request to the sensing entity if it determines that the authorization for the sensing service has been revoked or the sensing area does not allow the provision of the sensing service.
[0167] Step S2103: The sensing function sends a cancellation notification to the node that requested the sensing service.
[0168] In some embodiments, a node is used to request a perception service.
[0169] In some embodiments, a node may be referred to as a sensing service consumer or a requester. A sensing service consumer may be, for example, a third-party server, a core network device, etc.
[0170] In some embodiments, a node requesting a perception service can be understood as consuming the perception results corresponding to that perception service.
[0171] In some embodiments, a consumer of a sensing service can be an entity that consumes the sensing result or an entity that requests the sensing result.
[0172] In some embodiments, the revocation notification may include the reason for revoking the sensing service.
[0173] In some embodiments, the reasons for revoking a sensing service may include: the authorization for the sensing service is revoked, the sensing area does not allow the provision of the sensing service, the sensing service does not comply with relevant regulations, or the sensing service is revoked based on the operator's policy.
[0174] In some embodiments, after the sensing function sends the first request to the sensing entity, it may send a revocation notification to the node.
[0175] In some embodiments, the sensing function can send the revocation notification directly to the node, or it can send the revocation notification to the node through NEF.
[0176] It should be noted that step S2103 can be executed after step S2102 or after step S2106, and this embodiment of the present disclosure does not limit it in this way.
[0177] Step S2104: The sensing entity terminates the sensing service.
[0178] In some embodiments, terminating a sensing service by a sensing entity includes stopping the transmission of sensing signals and / or stopping the reception of sensing signals. For example, a sensing entity may stop a specific sensing service indicated by an identifier carried in a first request, such as a sensing transmitter stopping the transmission of a specific sensing signal.
[0179] Step S2105: Delete the configuration and / or parameters related to the sensing service for the sensing entity.
[0180] In some embodiments, the sensing entity may delete configurations and / or parameters associated with the identifier of the sensing service indicated by the first request.
[0181] Step S2106: The sensing entity sends a response message to the sensing function.
[0182] In some embodiments, the response message may include the revocation result of the awareness service, such as revocation success or revocation failure.
[0183] In some embodiments, after a sensing entity terminates the sensing service, it may send the response message to the sensing function.
[0184] By using the above method, the sensing entity can be asked to revoke the sensing service through the sensing function, thereby enabling the active termination of the sensing service, releasing relevant resources in a timely manner, stopping unnecessary sensing operations, and improving system performance.
[0185] The methods involved in the embodiments of this disclosure may include at least one of the steps S2101 to S2106 described above. For example, step S2101 may be implemented as an independent embodiment, step S2102 may be implemented as an independent embodiment, step S2104 may be implemented as an independent embodiment, step S2105 may be implemented as an independent embodiment, step S2101 + step S2102 may be implemented as an independent embodiment, step S2102 + step S2103 may be implemented as an independent embodiment, and step S2102 + step S2104 + step S2105 may be implemented as an independent embodiment, but are not limited thereto.
[0186] In some embodiments, the order of any two steps S2101 to S2106 can be interchanged or they can be performed simultaneously. For example, the order of steps S2104 and S2105 can be interchanged or they can be performed simultaneously.
[0187] In some embodiments, steps S2101 to S2106 are optional, and one or more of these steps may be omitted or substituted in different embodiments. For example, step S2101 may be omitted. As another example, step S2103 may be omitted. As yet another example, step S2106 may be omitted.
[0188] In some embodiments, other optional implementations described before or after the specification corresponding to FIG2 may be referred to.
[0189] In some embodiments, the names of information, etc., are not limited to the names described in the embodiments. Terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "symbol", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.
[0190] In some embodiments, the terms "codebook," "codeword," and "precoding matrix" can be used interchangeably. For example, a codebook can be a collection of one or more codewords / precoding matrices.
[0191] In some embodiments, the terms "uplink", "uplink", and "physical uplink" can be used interchangeably, as can the terms "downlink", "downlink", and "physical downlink", as well as the terms "sidelink", "sidelink", "sidelink communication", "sidelink communication", "direct connection", "direct link", "direct communication", and "direct link communication".
[0192] In some embodiments, the terms “downlink control information (DCI),” “downlink (DL) assignment,” “DL DCI,” “uplink (UL) grant,” and “UL DCI” can be used interchangeably.
[0193] In some embodiments, terms such as "physical downlink shared channel (PDSCH)" and "DL data" can be used interchangeably, as can terms such as "physical uplink shared channel (PUSCH)" and "UL data".
[0194] In some embodiments, the terms “radio”, “wireless”, “radio access network (RAN)”, “access network (AN)”, and “RAN-based” can be used interchangeably.
[0195] In some embodiments, the terms "search space", "search space set", "search space configuration", "search space set configuration", "control resource set (CORESET)", and "CORESET configuration" can be used interchangeably.
[0196] In some embodiments, the terms "synchronization signal (SS)," "synchronization signal block (SSB)," "reference signal (RS)," "pilot," and "pilot signal" can be used interchangeably.
[0197] In some embodiments, terms such as “moment,” “point in time,” “time,” and “time location” can be used interchangeably, as can terms such as “duration,” “segment,” “time window,” “window,” and “time.”
[0198] In some embodiments, the terms "component carrier (CC)," "cell," "frequency carrier," and "carrier frequency" can be used interchangeably.
[0199] In some embodiments, the terms “resource block (RB)”, “physical resource block (PRB)”, “sub-carrier group (SCG)”, “resource element group (REG)”, “PRB pair”, “RB pair”, “resource element (RE)”, and “sub-carrier” can be used interchangeably.
[0200] In some embodiments, terms such as wireless access scheme and waveform can be used interchangeably.
[0201] In some embodiments, the terms "precoding", "precoder", "weight", "precoding weight", "quasi-co-location (QCL)", "transmission configuration indication (TCI) status", "spatial relation", "spatial domain filter", "transmission power", "phase rotation", "antenna port", "antenna port group", "layer", "the number of layers", "rank", "resource", "resource set", "resource group", "beam", "beam width", "beam angle", "antenna", "antenna element", and "panel" can be used interchangeably.
[0202] In some embodiments, the terms “frame”, “radio frame”, “subframe”, “slot”, “sub-slot”, “mini-slot”, “symbol”, “symbol”, and “transmission time interval (TTI)” can be used interchangeably.
[0203] In some embodiments, "acquire," "get," "obtain," "receive," "transmit," "bidirectional transmission," and "send and / or receive" can be used interchangeably and can be interpreted as receiving from other entities, acquiring from protocols, acquiring from higher layers, obtaining through self-processing, or autonomous implementation. Protocols include, for example, at least one of the 3GPP protocol, Wi-Fi protocol, and audio and / or video protocols.
[0204] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.
[0205] In some embodiments, terms such as "certain," "preset," "default," "set," "indicated," "a certain," "any," and "first" can be used interchangeably. "Certain A," "preset A," "default A," "set A," "indicated A," "a certain A," "any A," and "first A" can be interpreted as A pre-defined in a protocol or the like, or as A obtained through setting, configuration, or instruction, or as specific A, a certain A, any A, or first A, but are not limited thereto.
[0206] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values (e.g., a comparison with a predetermined value), but is not limited thereto.
[0207] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data and / or instructions received; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the receiver to respond to the sent content.
[0208] In some embodiments, if an arrow in the interaction diagram representing the sending of information, signaling, etc. from one subject to another passes through other subjects, it can be interpreted as the information being forwarded from one subject to another via other subjects, or it can be interpreted as the information being sent from one subject to another without passing through other subjects.
[0209] Figure 3A is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3A, the present disclosure relates to a communication method that can be executed by a sensing function. The method may include:
[0210] Step S3101: Send the first request.
[0211] The optional implementation of step S3101 can be found in the optional implementation of step S2102 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0212] Step S3102: Send a cancellation notification.
[0213] The optional implementation of step S3102 can be found in the optional implementation of step S2103 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0214] Step S3103: Receive response message.
[0215] The optional implementation of step S3103 can be found in the optional implementation of step S2106 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0216] In some embodiments, the above steps are all optional.
[0217] Figure 3B is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3B, the present disclosure relates to a communication method that can be executed by a sensing function. The method may include:
[0218] Step S3201: Send the first request.
[0219] The optional implementation of step S3201 can be found in the optional implementation of step S2102 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0220] Step S3202: Receive response message.
[0221] The optional implementation of step S3202 can be found in the optional implementation of step S2106 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0222] Step S3203: Send a cancellation notification.
[0223] The optional implementation of step S3203 can be found in the optional implementation of step S2103 in Figure 2, as well as other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0224] In some embodiments, the above steps are all optional.
[0225] Figure 3C is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3C, the present disclosure relates to a communication method that can be executed by a sensing function. The method may include:
[0226] Step S3301: Send the first request.
[0227] The optional implementation of step S3301 can be found in the optional implementation of step S2102 in Figure 2 and other related parts in the embodiments involved in Figure 2, which will not be repeated here.
[0228] In some embodiments, the first request includes at least one of the following: the identifier of the sensing entity, and the identifier of the sensing service.
[0229] In some embodiments, the method further includes at least one of the following:
[0230] Receive a second request, which is used to request the cancellation of the perception service;
[0231] Receive a trigger message for revoking the sensing service, the trigger message including at least one of the following: the authorization for the sensing service is revoked, or the sensing area cannot provide the sensing service.
[0232] In some embodiments, the method further includes:
[0233] Receive a response message sent by the sensing entity, the response message including the cancellation result of the sensing service.
[0234] In some embodiments, the method further includes:
[0235] Send a revocation notification to the node that requested the sensing service, the revocation notification including the reason for revoking the sensing service.
[0236] In some embodiments, the sensing entity includes at least one of the following: a sensing signal transmitter and a sensing signal receiver.
[0237] In some embodiments, the problem of how to cancel an ongoing sensing service is addressed by defining a sensing function, specifically including:
[0238] Receive a trigger signal to cancel an ongoing sensing service;
[0239] Exchange sensing service cancellation request / response messages to terminate the sensing service in the sensing entity;
[0240] Send a notification of service cancellation with an appropriate reason to the consumer of the perceived service.
[0241] In some embodiments, the sensing function (SF) refers to the logical functions involved in supporting the sensing service, including providing configuration / parameters to sensing entities (sensing transmitters and / or sensing receivers), collecting sensing measurement data, processing sensing data to generate sensing results and passing them to sensing service consumers, and performing the revocation of ongoing sensing services.
[0242] Figure 4 is an interactive schematic diagram illustrating a communication method according to an embodiment of the present disclosure. This method can be executed by the aforementioned communication system. As shown in Figure 4, the method may include:
[0243] Step S4100: Start the perception service.
[0244] In some embodiments, a sensing service is initiated and identified by a sensing service ID. Sensing measurement data is transmitted to a sensing function, which then sends the sensing results to a sensing service consumer.
[0245] Step S4101: The sensing function receives the cancellation trigger condition / request for a specific sensing service.
[0246] In some embodiments, the sensing function receives a revocation trigger condition / request for a specific sensing service because the following conditions are met: for example, because the sensing service consumer is not authorized to request the service, or because the sensing target area does not allow the provision of sensing services.
[0247] Step S4102a: The sensing function sends a sensing service cancellation request to the sensing entity.
[0248] In some embodiments, the sensing entity includes a sensing transmitter and / or a sensing receiver, and the sensing service revocation request includes the sensing entity ID and / or the sensing service ID.
[0249] Step S4102b: The sensing function sends a sensing service cancellation notification to the sensing service consumer.
[0250] In some embodiments, the sensing function sends a sensing service withdrawal notification with an appropriate reason to the sensing service consumer, either directly or through the Network Exposure Function (NEF).
[0251] Step S4103: The sensing entity terminates the sensing service.
[0252] In some embodiments, terminating the sensing service includes stopping the sending and / or receiving of sensing signals and removing the configuration / parameters associated with the sensing service ID.
[0253] Step S4104: The sensing entity sends a sensing service cancellation response to the sensing function.
[0254] In some embodiments, the sensing entity sends a sensing service revocation response to the sensing function, which includes the result (success or failure).
[0255] Step S4105: The sensing function sends a sensing service cancellation notification to the sensing service consumer.
[0256] In some embodiments, the sensing function sends a sensing service withdrawal notification with an appropriate reason directly or via NEF to the sensing service consumer.
[0257] In some embodiments, if step S4102a has already been performed, then step S4105 is skipped.
[0258] In some embodiments of this disclosure, a communication system is provided, which may include a sensing function, a sensing entity, and a node. The sensing function may execute the communication method executed by the sensing function in the foregoing embodiments of this disclosure; the sensing entity may execute the communication method executed by the sensing entity in the foregoing embodiments of this disclosure; and the node may execute the communication method executed by the node in the foregoing embodiments of this disclosure.
[0259] This disclosure also provides embodiments of apparatus for implementing any of the above methods. For example, an apparatus is provided that includes units or modules for implementing the steps performed by the sensing function in any of the above methods. Alternatively, another apparatus is provided that includes units or modules for implementing the steps performed by the sensing function in any of the above methods. Yet another apparatus is provided that includes units or modules for implementing the steps performed by the node in any of the above methods.
[0260] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an Application-Specific Integrated Circuit (ASIC), and the functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a Programmable Logic Device (PLD), such as a Field Programmable Gate Array (FPGA), which can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.
[0261] In this embodiment, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a Graphics Processing Unit (GPU) (which can be understood as a microprocessor), or a Digital Signal Processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an Application-Specific Integrated Circuit (ASIC) or a Programmable Logic Device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be hardware circuits designed for artificial intelligence, which can be understood as ASICs, such as Neural Network Processing Units (NPUs), Tensor Processing Units (TPUs), and Deep Learning Processing Units (DPUs).
[0262] Figure 5A is a schematic diagram of the structure of a sensing function according to an embodiment of this disclosure. As shown in Figure 5A, the sensing function 5100 may include at least one of a transceiver module 5101, a processing module 5102, etc. In some embodiments, the transceiver module 5101 is configured to send a first request to a sensing entity, the first request being used to request the sensing entity to revoke the sensing service. Optionally, the transceiver module 5101 may be used to perform at least one of the communication steps (e.g., steps S2101, S2102, S2103, S2106, S3101, S3102, S3103, S3201, S3202, S3203, S3301, but not limited thereto) performed by the sensing function 5100 in any of the above methods, which will not be elaborated here. Optionally, the processing module 5102 may be used to perform at least one of the other steps performed by the sensing function 5100 in any of the above methods, which will not be elaborated here.
[0263] Figure 5B is a schematic diagram of the structure of a sensing entity according to an embodiment of this disclosure. As shown in Figure 5B, the sensing entity 5200 may include at least one of a transceiver module 5201, a processing module 5202, etc. In some embodiments, the transceiver module 5201 is configured to receive a first request sent by a sensing function, the first request being used to request the sensing entity to revoke the sensing service. Optionally, the transceiver module 5201 may be used to perform at least one of the communication steps (e.g., steps S2102, S2106, but not limited thereto) performed by the sensing entity 5200 in any of the above methods, which will not be elaborated here. Optionally, the processing module 5202 may be used to perform at least one of the other steps (e.g., steps S2104, S2105, but not limited thereto) performed by the sensing entity 5200 in any of the above methods, which will not be elaborated here.
[0264] Figure 5C is a schematic diagram of the structure of a node according to an embodiment of this disclosure. As shown in Figure 5C, the node 5300 may include at least one of a transceiver module 5301, a processing module 5302, etc. In some embodiments, the transceiver module 5301 is configured to receive a revocation notification sent by the sensing function, the revocation notification including the reason for revoking the sensing service. Optionally, the transceiver module 5301 may be used to perform at least one of the communication steps such as sending and / or receiving performed by the node 5300 in any of the above methods (e.g., step S2103, but not limited thereto), which will not be described in detail here. Optionally, the processing module 5302 may be used to perform at least one of the other steps performed by the node 5300 in any of the above methods, which will not be described in detail here.
[0265] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, which may be separate or integrated. Optionally, the transceiver module may be interchangeable with a transceiver.
[0266] In some embodiments, the processing module may be a single module or may include multiple sub-modules. Optionally, the multiple sub-modules may each perform all or part of the steps required by the processing module. Optionally, the processing module may be interchangeable with a processor.
[0267] Figure 6A is a schematic diagram of the structure of the communication device 6100 proposed in an embodiment of this disclosure. The communication device 6100 can be a network device (e.g., access network device, core network device, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports the network device in implementing any of the above methods, or a chip, chip system, or processor that supports the terminal in implementing any of the above methods. The communication device 6100 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.
[0268] As shown in Figure 6A, the communication device 6100 includes one or more processors 6101. The processor 6101 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit (CPU). The baseband processor can be used to process communication protocols and communication data, while the CPU can be used to control communication devices (e.g., base stations, baseband chips, IoT devices, IoT device chips, DUs or CUs, etc.), execute programs, and process program data. The communication device 6100 is used to execute any of the above methods.
[0269] In some embodiments, the communication device 6100 further includes one or more memories 6102 for storing instructions. Optionally, all or part of the memories 6102 may also be located outside the communication device 6100.
[0270] In some embodiments, the communication device 6100 further includes one or more transceivers 6103. When the communication device 6100 includes one or more transceivers 6103, the transceivers 6103 perform at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S2101, S2102, S2103, S2106, S3101, S3102, S3103, S3201, S3202, S3203, S3301, but not limited thereto), and the processor 6101 performs at least one of other steps (e.g., steps S2104, S2105, but not limited thereto).
[0271] In some embodiments, a transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, etc., may be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., may be used interchangeably; and the terms receiver, receiving unit, receiver, receiving circuit, etc., may be used interchangeably.
[0272] In some embodiments, the communication device 6100 may include one or more interface circuits. Optionally, the interface circuit is connected to the memory 6102, and the interface circuit can be used to receive signals from the memory 6102 or other devices, and can be used to send signals to the memory 6102 or other devices. For example, the interface circuit can read instructions stored in the memory 6102 and send the instructions to the processor 6101.
[0273] The communication device 6100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 6100 described in this disclosure is not limited thereto, and the structure of the communication device 6100 may not be limited by FIG. 6A. The communication device may be a standalone device or may be part of a larger device. For example, the communication device may be: (1) a standalone integrated circuit IC, or chip, or chip system or subsystem; (2) a collection of one or more ICs, optionally, the IC collection may also include storage components for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, terminal device, smart terminal device, cellular phone, wireless device, handheld device, mobile unit, vehicle device, network device, cloud device, artificial intelligence device, etc.; (6) others, etc.
[0274] Figure 6B is a schematic diagram of the structure of chip 6200 according to an embodiment of this disclosure. For cases where the communication device 6100 can be a chip or a chip system, please refer to the schematic diagram of chip 6200 shown in Figure 6B, but it is not limited thereto.
[0275] Chip 6200 includes one or more processors 6201, which are used to perform any of the above methods.
[0276] In some embodiments, chip 6200 further includes one or more interface circuits 6203. Optionally, interface circuit 6203 is connected to memory 6202, and interface circuit 6203 can be used to receive signals from memory 6202 or other devices, and interface circuit 6203 can be used to send signals to memory 6202 or other devices. For example, interface circuit 6203 can read instructions stored in memory 6202 and send the instructions to processor 6201.
[0277] In some embodiments, the interface circuit 6203 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S2101, S2102, S2103, S2106, S3101, S3102, S3103, S3201, S3202, S3203, S3301, but not limited thereto), and the processor 6201 performs at least one of other steps (e.g., steps S2104, S2105, but not limited thereto).
[0278] In some embodiments, the terms interface circuit, interface, transceiver pin, transceiver, etc., can be used interchangeably.
[0279] In some embodiments, chip 6200 further includes one or more memories 6202 for storing instructions. Optionally, all or part of the memories 6202 may be located outside of chip 6200.
[0280] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device 6100, cause the communication device 6100 to perform any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but not limited thereto; it may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but not limited thereto; it may also be a temporary storage medium.
[0281] This disclosure also provides a program product that, when executed by the communication device 6100, causes the communication device 6100 to perform any of the above methods. Optionally, the program product may be a computer program product.
[0282] This disclosure also proposes a computer program that, when run on a computer, causes the computer to perform any of the above methods.
Claims
1. A communication method, characterized in that, Performed by a sensing function, the method includes: A first request is sent to the sensing entity, the first request being used to request the sensing entity to revoke the sensing service.
2. The method according to claim 1, characterized in that, The first request includes at least one of the following: the identifier of the sensing entity, and the identifier of the sensing service.
3. The method according to claim 1 or 2, characterized in that, The method further includes at least one of the following: Receive a second request, which is used to request the cancellation of the perception service; Receive a trigger message for revoking the sensing service, the trigger message including at least one of the following: the authorization for the sensing service is revoked, or the sensing area cannot provide the sensing service.
4. The method according to any one of claims 1-3, characterized in that, The method further includes: Receive a response message sent by the sensing entity, the response message including the cancellation result of the sensing service.
5. The method according to any one of claims 1-4, characterized in that, The method further includes: Send a revocation notification to the node that requested the sensing service, the revocation notification including the reason for revoking the sensing service.
6. The method according to any one of claims 1-5, characterized in that, The sensing entity includes at least one of the following: a sensing signal transmitter and a sensing signal receiver.
7. A communication method, characterized in that, Performed by a perceiving entity, the method includes: The system receives a first request from the sensing function, which requests the sensing entity to revoke the sensing service.
8. The method according to claim 7, characterized in that, The first request includes at least one of the following: the identifier of the sensing entity, and the identifier of the sensing service.
9. The method according to claim 7 or 8, characterized in that, The method further includes: Terminate the perception service.
10. The method according to claim 9, characterized in that, The method further includes: Delete the configuration and / or parameters related to the perception service.
11. The method according to any one of claims 7-10, characterized in that, The method further includes: Send a response message to the sensing function, the response message including the cancellation result of the sensing service.
12. The method according to any one of claims 7-11, characterized in that, The sensing entity includes at least one of the following: a sensing signal transmitter and a sensing signal receiver.
13. A communication method, characterized in that, The method, executed by a node, includes: Receive a revocation notification sent by the sensing function, the revocation notification including the reason for revoking the sensing service.
14. The method according to claim 13, characterized in that, The node is used to request the perception service.
15. A sensing function, characterized in that, include: The transceiver module is configured to send a first request to the sensing entity, the first request being used to request the sensing entity to revoke the sensing service.
16. The sensing function according to claim 15, characterized in that, The first request includes at least one of the following: the identifier of the sensing entity, and the identifier of the sensing service.
17. The sensing function according to claim 15 or 16, characterized in that, The transceiver module is also configured to receive a second request, which is used to request the cancellation of the sensing service; The transceiver module is also configured to receive a trigger message for revoking the sensing service, the trigger message including at least one of the following: the authorization for the sensing service is revoked, or the sensing area cannot provide the sensing service.
18. The sensing function according to any one of claims 15-17, characterized in that, The transceiver module is also configured to receive a response message sent by the sensing entity, the response message including the cancellation result of the sensing service.
19. The sensing function according to any one of claims 15-18, characterized in that, The transceiver module is also configured to send a revocation notification to the node requesting the sensing service, the revocation notification including the reason for revoking the sensing service.
20. The sensing function according to any one of claims 15-19, characterized in that, The sensing entity includes at least one of the following: a sensing signal transmitter and a sensing signal receiver.
21. A perceptual entity, characterized in that, include: The transceiver module is configured to receive a first request sent by the sensing function, the first request being used to request the sensing entity to revoke the sensing service.
22. The sensing entity according to claim 21, characterized in that, The first request includes at least one of the following: the identifier of the sensing entity, and the identifier of the sensing service.
23. The sensing entity according to claim 21 or 22, characterized in that, The sensing entity also includes: The processing module is configured to terminate the perception service.
24. The sensing entity according to claim 23, characterized in that, The processing module is also configured to delete configurations and / or parameters related to the perception service.
25. The sensing entity according to any one of claims 21-24, characterized in that, The transceiver module is also configured to send a response message to the sensing function, the response message including the cancellation result of the sensing service.
26. The sensing entity according to any one of claims 21-25, characterized in that, The sensing entity includes at least one of the following: a sensing signal transmitter and a sensing signal receiver.
27. A node, characterized in that, include: The transceiver module is configured to receive a revocation notification sent by the sensing function, the revocation notification including the reason for revoking the sensing service.
28. The node according to claim 27, characterized in that, The node is used to request the perception service.
29. A communication device, characterized in that, The communication device is used to perform the communication method according to any one of claims 1-6, 7-12, and 13-14.
30. A communication system, characterized in that, It includes a sensing function, a sensing entity, and nodes, wherein the sensing function is configured to implement the communication method of any one of claims 1-6, the sensing entity is configured to implement the communication method of any one of claims 7-12, and the nodes are configured to implement the communication method of any one of claims 13-14.
31. A storage medium storing instructions, characterized in that, When the instruction is executed on the communication device, the communication device performs the communication method as described in any one of claims 1-6, 7-12, and 13-14.
32. A program product comprising at least one of a program and instructions, characterized in that, When at least one of the programs or instructions is executed by the communication device, it implements the steps of the method according to any one of claims 1-6, 7-12, and 13-14.
