Communication method, network element, communication system, storage medium, and program product
By introducing the function of receiving and authorizing the perception service request in the network, the problem of the legitimacy of perception service requests in the network architecture is solved, the perception task is executed efficiently and securely, and network security and user experience are improved.
Patent Information
- Application Number
- PCT/CN2025/094075
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-09
- Publication Date
- 2026-11-12
AI Technical Summary
The lack of effective mechanisms for service request authorization and management in the existing network architecture leads to insufficient network security.
By implementing the function of receiving and authorizing the perception service request in the first network element, it is determined whether the node is authorized to request the perception service, and when the authorization is successful, a suitable second network element is selected to provide the perception service, thus ensuring the efficient and secure execution of the perception task.
It improved network security, ensured the legality and accuracy of perception services, optimized resource allocation, and enhanced the system's intelligence level and user experience.
Smart Images

Figure CN2025094075_12112026_PF_FP_ABST
Abstract
Description
Communication methods, network elements, 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, network element, communication system, storage medium, and program product. Background Technology
[0002] With the development of communication technology, the demand for network sensing services is increasing. Sensing services support the acquisition of relevant sensing data from devices in the network. This sensing data can include device status, location, environmental information, etc. Although the current network architecture provides certain network functions and service interfaces, there is a lack of effective mechanisms for authorizing and managing sensing service requests. Summary of the Invention
[0003] To enhance network security, embodiments of this disclosure provide a communication method, network element, communication system, storage medium, and program product.
[0004] According to a first aspect of the present disclosure, a communication method is provided, executed by a first network element, the method comprising: receiving a first request sent by a node, the first request being for requesting a sensing service; and determining whether the node is authorized to request the sensing service.
[0005] According to a second aspect of the present disclosure, a communication method is provided, executed by a node, the method comprising: sending a first request to a first network element, the first request being used to request a sensing service, the first request being used by the first network element to determine whether the node is authorized to request the sensing service.
[0006] According to a third aspect of the present disclosure, a communication method is provided, executed by a second network element, the method comprising: receiving a second request generated and sent by a first network element based on a first request, wherein the first request is used for a node to request a sensing service from the first network element, and the second request is generated and sent by the first network element after determining that the node is authorized to request the sensing service; and determining, based on the second request, whether there exists a sensing entity performing a sensing task.
[0007] According to a fourth aspect of the present disclosure, a first network element is proposed, comprising: a transceiver module for receiving a first request sent by a node, the first request being for requesting a sensing service; and a processing module for determining whether the node is authorized to request the sensing service.
[0008] According to a fifth aspect of the present disclosure, a node is provided, comprising: a transceiver module, configured to send a first request to a first network element, the first request being used to request a sensing service, and the first request being used by the first network element to determine whether the node is authorized to request the sensing service.
[0009] According to a sixth aspect of the present disclosure, a second network element is proposed, comprising: a transceiver module, configured to receive a second request generated and sent by a first network element based on a first request, wherein the first request is used for a node to request a sensing service from the first network element, and the second request is generated and sent by the first network element when it is determined that the node is authorized to request the sensing service; and a processing module, configured to determine, based on the second request, whether there exists a sensing entity performing a sensing task.
[0010] According to a seventh aspect of the present disclosure, a first network element is provided, comprising: one or more processors; and a memory coupled to the processors, the memory storing executable instructions, which, when executed by the processors, cause the first network element to perform the communication method described in the first aspect.
[0011] According to an eighth aspect of the present disclosure, a node is provided, comprising: one or more processors; and a memory coupled to the processors, the memory storing executable instructions that, when executed by the processors, enable the communication method of the second aspect of the node.
[0012] According to a ninth aspect of the present disclosure, a second network element is provided, comprising: one or more processors; and a memory coupled to the processors, the memory storing executable instructions, which, when executed by the processors, cause the second network element to perform the communication method described in the third aspect.
[0013] According to a tenth aspect of the present disclosure, a communication system is provided, including a first network element, a node, and a second network element, wherein the first network element is configured to implement the communication method described in the first aspect, the node is configured to implement the communication method described in the second aspect, and the second network element is configured to implement the communication method described in the third aspect.
[0014] According to an eleventh aspect of the present disclosure, a storage medium is provided that stores instructions, which, when executed on a communication device, cause the communication device to perform the communication method described in the first, second, or third aspect.
[0015] According to a twelfth aspect of the present disclosure, a program product is provided, including at least one of a program and instructions, wherein the at least one of the program and instructions, when executed by a communication device, implements a communication method of the method described in the first aspect, the second aspect, or the third aspect.
[0016] By adopting the above technical solution, at least the following beneficial technical effects can be achieved:
[0017] The first network element receives a first request sent by a node, which is used to request a sensing service. The first network element determines whether the node is authorized to request the sensing service. The above-mentioned technical solution of this disclosure effectively solves the problem of the legitimacy of sensing service requests by implementing the functions of receiving and authorizing the verification of sensing service requests in the first network element, thereby improving network security. Attached Figure Description
[0018] 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.
[0019] Figure 1 is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure.
[0020] Figure 2A is an interactive schematic diagram of a communication method proposed according to an embodiment of the present disclosure.
[0021] Figure 2B is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure.
[0022] Figure 2C is an interactive schematic diagram of a communication method proposed according to an embodiment of the present disclosure.
[0023] Figure 3A is a flowchart illustrating a communication method according to an embodiment of the present disclosure.
[0024] Figure 3B is a flowchart illustrating a communication method according to an embodiment of the present disclosure.
[0025] Figure 3C is a flowchart illustrating a communication method according to an embodiment of the present disclosure.
[0026] Figure 4 is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure.
[0027] Figure 5A is a schematic diagram of the structure of the first network element proposed according to an embodiment of the present disclosure.
[0028] Figure 5B is a schematic diagram of the structure of the second network element proposed according to an embodiment of the present disclosure.
[0029] Figure 5C is a schematic diagram of the structure of the second network element proposed according to an embodiment of the present disclosure.
[0030] Figure 6A is a schematic diagram of the structure of a communication device according to an embodiment of the present disclosure.
[0031] Figure 6B is a schematic diagram of the structure of a chip according to an embodiment of the present disclosure. Detailed Implementation
[0032] This disclosure provides a communication method, network element, communication system, storage medium, and program product.
[0033] In a first aspect, embodiments of this disclosure propose a communication method executed by a first network element, the method comprising: receiving a first request sent by a node, the first request being used to request a sensing service; and determining whether the node is authorized to request the sensing service.
[0034] In the above embodiments, by implementing the function of receiving and authorizing the perception service request in the first network element, the problem of the legitimacy of the perception service request can be effectively solved, thereby improving network security.
[0035] In conjunction with some embodiments of the first aspect, in some embodiments, the first request includes at least one of the following:
[0036] The identifier of the node;
[0037] Time information;
[0038] Sensing precision information;
[0039] Sensing area information;
[0040] Perceive entity information.
[0041] In the above embodiments, by including at least one of the following in the first request: node identifier, time information, perception accuracy information, perception area information, or perception entity information, perception requirements can be defined more accurately, thereby improving the pertinence and efficiency of perception tasks.
[0042] In conjunction with some embodiments of the first aspect, in some embodiments, determining whether the node is authorized to request the perception service includes: determining that the node is authorized to request the perception service;
[0043] The method further includes: determining a second network element based on the sensing area information, wherein the second network element is one of a plurality of network elements providing the sensing service; sending a second request to the second network element, wherein the second request includes some or all of the information in the first request, and the second request is used to request the sensing service.
[0044] In the above embodiments, when the authorization verification of the node is successful, a suitable second network element is selected based on the sensing area information, and then the second request is sent to the second network element, thereby realizing efficient and secure scheduling of sensing services and ensuring the accurate execution of sensing tasks.
[0045] In conjunction with some embodiments of the first aspect, in some embodiments, determining the second network element based on the sensing area information includes: determining one of the multiple network elements as the second network element based on the sensing area information and the correspondence between multiple sensing areas stored on the first network element and the service areas of the multiple network elements.
[0046] In the above embodiments, by storing the correspondence between the sensing area and the service area of the network element on the first network element, and matching a suitable second network element according to the sensing area information, the most suitable network element can be accurately selected from multiple network elements that provide sensing services, thereby optimizing resource allocation and improving the efficiency and accuracy of sensing services.
[0047] In conjunction with some embodiments of the first aspect, in some embodiments, determining the second network element based on the sensing area information includes: determining one of the multiple network elements as the second network element based on the sensing area information and the correspondence between multiple sensing areas stored on the first network element and the service areas of the multiple network elements.
[0048] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: determining that the node is authorized to request the sensing service; determining a second network element providing the sensing service based on the sensing area information; sending a second request to the second network element, the second request including some or all of the information in the first request, the second request being used to request the sensing service.
[0049] In the above embodiments, when the authorization verification of the node is successful, a suitable second network element is selected based on the sensing area information, and then the second request is sent to the second network element, thereby realizing efficient and secure scheduling of sensing services and ensuring the accurate execution of sensing tasks.
[0050] In conjunction with some embodiments of the first aspect, in some embodiments, the number of network elements providing the sensing service is multiple, and the first network element stores a correspondence between a sensing area and a service area supported by the network element providing the sensing service; determining the second network element providing the sensing service based on the sensing area information includes: determining the second network element from multiple network elements providing the sensing service based on the sensing area information and the correspondence.
[0051] In the above embodiments, by storing the correspondence between the sensing area and the service area of the network element on the first network element, and matching a suitable second network element according to the sensing area information, the most suitable network element can be accurately selected from multiple network elements that provide sensing services, thereby optimizing resource allocation and improving the efficiency and accuracy of sensing services.
[0052] In conjunction with some embodiments of the first aspect, in some embodiments, determining the second network element providing the sensing service based on the sensing area information includes: requesting a third network element to determine the second network element based on the sensing area information.
[0053] In the above embodiments, by introducing a third network element and utilizing the correspondence between its stored sensing area and network element service area, the second network element is determined based on the sensing area information. This enables flexible and efficient selection of a suitable sensing service provider in a complex network architecture, thereby improving the system's intelligence level and resource scheduling capabilities.
[0054] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: receiving a response message sent by the second network element; sending the perception result to the node if the response message includes a perception result corresponding to the perception service; or, sending a rejection message to the node if the response message indicates that there is no perception entity performing the perception task, the rejection message including a rejection reason.
[0055] In the above embodiments, by receiving the response message from the second network element and sending the perception result or rejection message (including the reason for rejection) to the node according to the content of the response message, the closed-loop processing of the perception service request is realized, ensuring that the node can obtain feedback in a timely manner, and improving the interactivity of the system and the user experience.
[0056] In conjunction with some embodiments of the first aspect, in some embodiments, determining whether the node is authorized to request the sensing service includes: determining that the node is not authorized to request the sensing service;
[0057] The method further includes sending a rejection message to the node, the rejection message including a reason for rejection.
[0058] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes: determining that the node is not authorized to request the sensing service, and sending a rejection message to the node, the rejection message including a reason for rejection.
[0059] In the above embodiments, by promptly sending a rejection message containing the reason for rejection to a node when it is detected that it is not authorized, unauthorized awareness service requests can be effectively prevented, ensuring the security of the system. At the same time, it provides clear feedback to the node, enhancing the reliability of the system and the user experience.
[0060] In conjunction with some embodiments of the first aspect, in some embodiments, the node includes at least one of the following:
[0061] Third-party application functionality (AF);
[0062] Core network equipment.
[0063] In the above embodiments, by incorporating third-party application functions (AF) or core network devices into the node category, flexible expansion and optimization of network functions are achieved, thereby improving the overall network performance and application support capabilities.
[0064] In conjunction with some embodiments of the first aspect, in some embodiments, the first network element is a Network Open Function (NEF).
[0065] In conjunction with some embodiments of the first aspect, in some embodiments, the second network element is a sensing function SF.
[0066] In conjunction with some embodiments of the first aspect, in some embodiments, the third network element is the Access and Mobility Management Function (AMF).
[0067] Secondly, this disclosure provides a communication method executed by a node, the method comprising: sending a first request to a first network element, the first request being used to request a sensing service, the first request being used by the first network element to determine whether the node is authorized to request the sensing service.
[0068] In conjunction with some embodiments of the second aspect, in some embodiments, the first request includes at least one of the following:
[0069] The identifier of the node;
[0070] Time information;
[0071] Sensing precision information;
[0072] Sensing area information;
[0073] Perceive entity information.
[0074] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes: receiving a sensing result sent by the first network element; or, receiving a rejection message sent by the first network element, the rejection message including a rejection reason.
[0075] In conjunction with some embodiments of the second aspect, in some embodiments, the node includes at least one of the following:
[0076] Third-party application functionality (AF);
[0077] Core network equipment.
[0078] In conjunction with some embodiments of the second aspect, in some embodiments, the first network element is a Network Open Function (NEF).
[0079] Thirdly, this disclosure provides a communication method executed by a second network element. The method includes: receiving a second request generated and sent by a first network element based on a first request, wherein the first request is used for a node to request a sensing service from the first network element, and the second request is generated and sent by the first network element when it is determined that the node is authorized to request the sensing service; and determining whether there is a sensing entity performing a sensing task based on the second request.
[0080] In conjunction with some embodiments of the third aspect, in some embodiments, a second request is received, the second request being used to request a sensing service; and based on the second request, it is determined whether a sensing entity exists to perform a sensing task.
[0081] In the above embodiments, by receiving the second request through the second network element and determining whether there is a sensing entity performing the sensing task, the feasibility of the sensing service can be quickly verified, providing a basis for subsequent sensing task execution and optimizing the scheduling process of the sensing service.
[0082] In conjunction with some embodiments of the third aspect, in some embodiments, receiving the second request generated and sent by the first network element according to the first request includes: receiving the second request directly sent by the first network element; or, receiving the second request indirectly sent by the first network element through a third network element.
[0083] In the above embodiments, by receiving a second request sent directly by the first network element or indirectly by the first network element through a third network element, the second network element can flexibly adapt to different network architectures and request paths, ensuring that the reception of perception service requests has broad compatibility and efficiency, thereby providing a stable foundation for subsequent perception task processing.
[0084] In conjunction with some embodiments of the third aspect, in some embodiments, the first request includes at least one of the following:
[0085] The identifier of the node;
[0086] Time information;
[0087] Sensing precision information;
[0088] Sensing area information;
[0089] Perceive entity information.
[0090] In the above embodiments, by including at least one of the following in the second request: node identifier, time information, perception accuracy information, perception area information, or perception entity information, the second network element can more accurately understand the needs of the perception service, thereby more efficiently determining whether there is a perception entity performing the perception task, and improving the pertinence and accuracy of the perception service.
[0091] In conjunction with some embodiments of the third aspect, in some embodiments, the second request includes at least one of the following:
[0092] The identifier of the node;
[0093] Time information;
[0094] Sensing precision information;
[0095] Sensing area information;
[0096] Perceive entity information.
[0097] In conjunction with some embodiments of the third aspect, in some embodiments, determining whether a sensing entity performing a sensing task exists based on the second request includes: the sensing entity performing the sensing task exists; the method further includes: sending a third request to the sensing entity, the third request being used to request sensing data.
[0098] In conjunction with some embodiments of the third aspect, in some embodiments, determining whether a sensing entity performing a sensing task exists according to the second request includes: the sensing entity performing the sensing task does not exist; the method further includes: sending a response message to the first network element, the response message indicating that the sensing entity performing the sensing task does not exist.
[0099] In some embodiments, in conjunction with the third aspect, the method further includes: determining that there exists a sensing entity performing a sensing task, and sending a third request to the sensing entity, the third request being used to request sensing data.
[0100] In the above embodiments, after determining that there is a sensing entity performing a sensing task, the second network element sends a third request to the sensing entity to request sensing data. This process ensures the smooth execution of the sensing task, realizes the effective connection from sensing service request to sensing data acquisition, and further promotes the complete process of sensing service.
[0101] In conjunction with some embodiments of the third aspect, in some embodiments, the third request includes at least one of the following:
[0102] The identifier of the perceived entity;
[0103] Time information;
[0104] Perceive precision information.
[0105] In the above embodiments, by including at least one of the identifier of the sensing entity, time information, or sensing accuracy information in the third request, the specific requirements for data collection can be conveyed to the sensing entity more accurately, thereby improving the accuracy and reliability of the sensing data and ensuring the efficient execution of the sensing task.
[0106] In conjunction with some embodiments of the third aspect, in some embodiments, the method further includes: receiving sensing data sent by the sensing entity; processing the sensing data to obtain a sensing result; and sending a response message to a first network element, the response message including the sensing result.
[0107] In the above embodiments, by receiving sensing data sent by sensing entities, processing it and generating sensing results, and then feeding the results back to the first network element, the effective collection, processing and transmission of sensing data are realized, ensuring the complete closed loop of sensing services and improving the overall performance of the system and user experience.
[0108] In some embodiments, in conjunction with the third aspect, the method further includes: determining that there is no sensing entity performing the sensing task, and sending a response message to the first network element, the response message indicating that there is no sensing entity performing the sensing task.
[0109] In the above embodiments, by sending an explicit response message to the first network element when it is determined that there is no sensing entity to perform the sensing task, the situation that the sensing task cannot be executed is promptly reported, which avoids invalid waiting and waste of resources and improves the efficiency and reliability of the system.
[0110] In conjunction with some embodiments of the third aspect, in some embodiments, the node includes at least one of the following:
[0111] Third-party application functionality (AF);
[0112] Core network equipment.
[0113] In conjunction with some embodiments of the third aspect, in some embodiments, the first network element is a Network Open Function (NEF).
[0114] Fourthly, the present disclosure provides a first network element, which includes at least one of a transceiver module and a processing module; wherein the first network element is used to execute the optional implementation of the first aspect.
[0115] Fifthly, embodiments of this disclosure propose a node, which includes at least one of a transceiver module and a processing module; wherein the node is used to execute an optional implementation of the second aspect.
[0116] In a sixth aspect, embodiments of this disclosure propose a second network element, which includes at least one of a transceiver module and a processing module; wherein the second network element is used to execute the optional implementation of the third aspect.
[0117] In a seventh aspect, embodiments of this disclosure propose a first network element, which includes one or more processors; wherein the first network element is used to execute an optional implementation of the first aspect.
[0118] Eighthly, embodiments of this disclosure provide a node, which includes one or more processors; wherein the node is used to execute an optional implementation of the second aspect.
[0119] In a ninth aspect, embodiments of this disclosure provide a second network element, which includes one or more processors; wherein the second network element is used to execute an optional implementation of the third aspect.
[0120] In a tenth aspect, embodiments of this disclosure provide a communication system comprising: a first network element, a node, and a second network element; wherein the first network element is configured to perform the method described in the optional implementation of the first aspect, the node is configured to perform the method described in the optional implementation of the second aspect, and the second network element is configured to perform the method described in the optional implementation of the third aspect.
[0121] 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 described in the optional implementations of the first, second, and third aspects.
[0122] 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 the optional implementations of the first, second, and third aspects.
[0123] 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 the optional implementations of the first, second, and third aspects.
[0124] 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 according to optional implementations of the first, second, and third aspects above.
[0125] It is understood that the aforementioned first network element, node, second network element, third network element, communication system, storage medium, program product, computer program, chip, or chip system are all 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.
[0126] This disclosure provides a communication method, a network element, a communication system, a storage medium, and a program product. In some embodiments, the terms "communication method" and "information processing method," "authorization verification method for a third-party triggered perception service request," etc., can be used interchangeably.
[0127] 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. In all embodiments of this disclosure, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the embodiments are consistent and can be mutually referenced. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.
[0128] 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.
[0129] 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.
[0130] In the embodiments of this disclosure, "multiple" refers to two or more.
[0131] In some embodiments, the terms “at least one of A or B, at least one of A and B”, “one or more”, “a plurality of”, “multiple”, etc., may be used interchangeably.
[0132] 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 whether there is a branch B); in some embodiments, B (execute B regardless of whether there is a branch A); in some embodiments, execution is selected from A and B (A and B are selectively executed); in some embodiments, both A and B are executed. The same applies when there are more branches such as A, B, C, etc.
[0133] In some embodiments, the notation "A or B" may include the following technical solutions, depending on the situation: in some embodiments, A (execute A regardless of whether a branch B exists); in some embodiments, B (execute B regardless of whether a branch A exists); 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, and C.
[0134] 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.
[0135] In some embodiments, “including A,” “containing A,” “for indicating A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.
[0136] In some embodiments, terms such as "time / frequency" and "time-frequency domain" refer to the time domain and / or frequency domain.
[0137] In some embodiments, terms such as “in response to…”, “in response to determining…”, “in the case of…”, “when…”, “when…”, “if…”, etc. can be used interchangeably. These descriptions all refer to the device making a corresponding action under certain objective circumstances. They do not necessarily limit the time, nor do they require the device to make a judgment action when implementing it, nor do they mean that there must be other limitations.
[0138] 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”.
[0139] 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,” “network function,” “network device,” “function,” “node,” “unit,” “section,” “system,” “network,” “chip,” “chip system,” “entity,” and “subject” are interchangeable.
[0140] In some embodiments, "network" can be interpreted as devices included in a network (e.g., access network devices, core network devices, etc.).
[0141] 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.
[0142] 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.
[0143] In some embodiments, access network devices, core network devices, or network devices can be replaced by 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 by 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, and uplink link, downlink, etc., can be replaced with sidelink link.
[0144] 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.
[0145] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.
[0146] In some embodiments, data, information, etc., may be obtained with the user's consent.
[0147] 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.
[0148] 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 at least one of a first network element 101, a second network element 102, a third network element 103, a sensing entity 104, and a node 105.
[0149] In some embodiments, the function of the first network element 101 includes exposing network capabilities to third-party applications. Optionally, the name of the first network element 101 is not limited, and its name may be, for example, network device, network exposure function (NEF), external interface, etc.
[0150] In some embodiments, the second network element 102 is a logical function that supports the sensing service. Optionally, the name of the second network element 102 is not limited, and its name may be, for example, network device, sensing function (SF), sensing network element, etc.
[0151] In some embodiments, the functions of the third network element 103 include access control and mobility management. Access control refers to the control of user access to the network. Mobility management refers to the management of user mobility, including handover and roaming. Optionally, the name of the third network element 103 is not limited, and the name of the third network element 1023 may be network device, Access and Mobility Function (AMF), Mobility Management Network Element, Access Management Network Element, etc.
[0152] In some embodiments, the function of sensing entity 104 includes transmitting and / or receiving sensing signals. Optionally, the name of sensing entity 104 is not limited, and its name may be, for example, a sensing transmitter, a sensing receiver, a sensing sensor, a terminal or network device with sensing signal transmission / reception function, etc.
[0153] In some embodiments, node 105 can be a network device, a third-party application function (AF), etc. The network device may be, for example, a core network element or an access network device. The AF may be, for example, a server.
[0154] In some embodiments, the terminal includes, but is not limited to, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home.
[0155] In some embodiments, the network device may include at least one of an access network device and a core network device.
[0156] Optionally, the network device is an access network device. Optionally, the access network device is, for example, a node or device that connects a terminal to a wireless network. The access network device may include at least one of the following in a 5G communication system: evolved Node B (eNB), next-generation evolved Node B (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, but is not limited thereto.
[0157] In some embodiments, the network device is a base station. Optionally, the base station may be, for example, a macro base station, a micro base station (also called a small station), a relay station, an access point, a 5G base station or a future base station, a satellite, a Transmitting and Receiving Point (TRP), a Transmitting Point (TP), a mobile switching center, or other equipment that performs base station functions in a communication system, etc., and this disclosure does not specifically limit this type of device. For ease of description, in all embodiments of this disclosure, the apparatus that provides wireless communication functions for terminal devices is collectively referred to as a network device or a base station.
[0158] In some embodiments, the network device is a core network device. Optionally, the core network device can be a single device, including a first network element, a second network element, etc., or it can be multiple devices or a group of devices, each including all or part of the first network element, the second network element, etc. Network elements can be virtual or physical. The core network includes, for example, at least one of the Evolved Packet Core (EPC), 5G Core Network (5GCN), and Next Generation Core (NGC).
[0159] 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.
[0160] 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 of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.
[0161] 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.
[0162] 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 illustrative. 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 illustrative. 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.
[0163] 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).
[0164] In some embodiments of this disclosure, a node refers to a Sensing Service Consumer, which is an entity that may use the sensing results. Optionally, a Sensing Service Consumer may also request the sensing results.
[0165] In some embodiments of this disclosure, the sensing entity refers to an entity with sensing and measurement capabilities, which may be a sensing transmitter and / or a sensing receiver, or a terminal, network device, etc., that has sensing transmitter and / or sensing receiver functions.
[0166] In some embodiments of this disclosure, a sensing function (SF) refers to a logical function that supports sensing services. Optionally, a sensing function may not be a sensing entity.
[0167] In some embodiments of this disclosure, a sensing service refers to the ability to collect and provide characteristic information about objects and / or the environment via wireless signals.
[0168] In some embodiments, in order to support the authorization and revocation of sensing services, a key issue may be to address the authorization and revocation of specific sensing services, including: authorization of sensing service requests and revocation of ongoing sensing services; and, where applicable, authorization and revocation of sensing entities.
[0169] In some embodiments, the authorization of sensing service requests and the revocation of ongoing sensing services may require addressing the following aspects:
[0170] If necessary, whether and how to authorize requests for awareness services.
[0171] If necessary, whether and how to revoke the awareness service when needed, and the criteria for revocation.
[0172] If necessary, who, how, and which entity authorizes and revokes the perception service request.
[0173] If necessary, whether and where to store perception service request authorization information and perception service revocation information, and when and how to update authorization and revocation information.
[0174] In some embodiments, the research needs to address the following aspects regarding the authorization and revocation (if applicable) of perceived entities:
[0175] Whether, when, and by which entity the authorization and revocation of a perceived entity are performed.
[0176] If necessary, the granularity of entity authorization.
[0177] If necessary, store and manage the authorization information of the perceived entity.
[0178] The authorization and revocation of a perceived entity may be related to the discovery and selection of the perceived entity.
[0179] In some embodiments, since there is no solution in the related art to authorize sensing service requests initiated by sensing consumers, this disclosure proposes a communication method, network element, communication system, storage medium, and program product to address the problem of how a network authorizes sensing service requests initiated by nodes by defining Network Open Function (NEF).
[0180] Figure 2A is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2A, the present disclosure relates to a communication method executed by a communication system 100, and the method includes at least one of the following steps:
[0181] Step S2101: Node 105 sends a first request to the first network element 101.
[0182] In some embodiments, the first network element receives a first request. For example, the first network element 101 receives a first request sent by node 105. For example, assuming the name of the first network element is NEF, the node sends a first request to NEF, and NEF receives the first request sent by the node.
[0183] In some embodiments, the first request is used to request a perception service.
[0184] In some embodiments, the name of the first request is not limited, and its name may be, for example, a perception service request, a perception data request, a perception result request, etc.
[0185] In some embodiments, the first request includes at least one of the following:
[0186] Node identifier;
[0187] Time information;
[0188] Sensing precision information;
[0189] Sensing area information;
[0190] Perceive entity information.
[0191] In some embodiments, the identifier of a node may be a node ID, a unique identifier of the node, etc.
[0192] In some embodiments, time information includes the sensing time point, sensing duration, sensing time window, etc. The sensing time point may be, for example, the start time point of sensing, the end time point of sensing, etc.
[0193] In some embodiments, the perceived accuracy information includes information such as measurement accuracy, resolution, and response time.
[0194] In some embodiments, the sensing area information indicates the geographical area that the node requests to sense.
[0195] In some embodiments, the perceived entity information includes information such as the perceived entity identifier and location.
[0196] For example, the first request includes the node's identifier, time information, perception accuracy information, and perception area information.
[0197] For example, the first request includes the node's identifier, perception accuracy information, and perception entity information.
[0198] In some embodiments, where the sensed entity information includes sensed entity location information, the first request may include one of the sensed entity information and sensed area information. The first network element can determine the sensed area based on the sensed entity location information. For example, the sensed area may be defined as the location of the sensed entity or an area of a certain size including the location of the sensed entity.
[0199] In some embodiments, the terms "sensing service" can be used interchangeably with "sensing business", "sensing task", "sensing function", etc.
[0200] It should be explained that, in the embodiments of this disclosure, the sensing service refers to the ability to collect and extract feature information of objects and / or the environment through wireless signals, and the ability to provide feature information to nodes. The sensing service can utilize the reflection and propagation characteristics of wireless signals to acquire relevant sensing data such as the position, speed, shape, and size of objects, as well as environmental factors such as temperature, humidity, and illumination. In some embodiments, after obtaining the sensing data, relevant algorithms can be combined to calculate the sensing results and improve sensing accuracy and efficiency, thereby providing data support for applications of sensing technologies such as intelligent transportation, environmental monitoring, and industrial automation.
[0201] In some embodiments, a node refers to an entity that may use or request the perceived results / data. The name of a node is not limited, and its name may be, for example, a node, the sender of the first request, etc.
[0202] In some embodiments, a node is a consumer of the perception service and a requester of the perception service.
[0203] In some embodiments, a node may specifically be an access network device, a core network device, or a third-party application function (AF).
[0204] It should be explained that AF can represent a functional entity of a third-party application or service provider. For example, AF can be a third-party server.
[0205] In step S2102, the first network element 101 determines whether node 105 is authorized to request the perception service.
[0206] In some embodiments, the function of the first network element includes authenticating nodes requesting the sensing service. Optionally, the function of the first network element includes determining whether the node has the relevant permissions for the sensing service. Relevant permissions include the permission to send a sensing service request, the permission to request the sensing service, etc. For example, the first network element can determine whether the node is authorized to request the sensing service. For example, the first network element can determine whether the node is authorized to send a first request to request the sensing service.
[0207] In some embodiments, the first network element may store relevant permission information of the node. Alternatively, the first network element may obtain or query relevant permission information of the node from relevant storage network elements such as the Network Repository Function (NRF) or Unified Data Management (UDM). Furthermore, the first network element can determine whether the node is authorized to request the awareness service based on the node's permission information.
[0208] In some embodiments, if the first network element determines that the node has not been authorized to request the sensing service, subsequent steps S2103 to S2110 are not executed. In some embodiments, as shown in FIG2B, the first network element may send a rejection message to the node. The rejection message may include a rejection reason, such as the node not being authorized to request the sensing service, the node not having service permissions, or the node failing authentication.
[0209] In some embodiments, if it is determined that the node has been authorized to request the awareness service, i.e., the node authentication has been passed, step S2103 is executed.
[0210] In step S2103, the first network element 101 determines the second network element 102 that provides sensing services.
[0211] In some embodiments, the number of network elements providing sensing services is multiple.
[0212] In some embodiments, a network element capable of providing sensing services refers to the logical functions involved in supporting sensing services. This includes providing configuration / parameters for sensing entities (sensing transmitters and / or sensing receivers), collecting sensing measurement data, processing sensing data to generate sensing results and transmitting them to sensing service nodes, etc.
[0213] In some embodiments, the name of the network element providing sensing services may be sensing network element, sensing function SF, etc.
[0214] In some embodiments, different network elements providing sensing services can provide sensing services for different regions. In some embodiments, a first network element stores a correspondence between sensing regions and service regions supported by the network element providing the sensing service. The sensing region may refer to a geographical region. The correspondence is provided by the network element providing the sensing service.
[0215] In some embodiments, the implementation of the first network element determining the second network element that provides sensing services includes: the first network element determining the second network element that provides sensing services based on sensing area information.
[0216] Optionally, the implementation of the first network element determining the second network element providing sensing services based on the sensing area information can be as follows: the first network element can determine at least one second network element from multiple network elements providing sensing services based on the sensing area information and the above-mentioned correspondence stored on the first network element.
[0217] Optionally, the implementation method for the first network element to determine the second network element providing sensing services based on the sensing area information can be: the first network element requests the third network element to determine the second network element based on the sensing area information. The name of the third network element is not limited, and its name may be, for example, AMF.
[0218] It should be noted that the first network element can select or determine the corresponding third network element based on at least one of the sensing area information and sensing entity information. For example, the first network element determines the third network element responsible for access and mobility management within the corresponding sensing area based on the sensing area information. Similarly, the first network element determines the third network element responsible for access and mobility management for the corresponding sensing entity based on the sensing entity information. It should also be noted that there are multiple network elements responsible for access and mobility management, with different network elements responsible for access and mobility management within different areas. The correspondence between each network element and its area can be obtained directly or indirectly from relevant storage network elements such as NRF or UDM.
[0219] In some embodiments, the implementation of the first network element requesting the third network element to determine an available second network element can be as follows: the first network element sends a request to the third network element, the request including sensing area information. The third network element obtains or queries the correspondence between the sensing area and the service area supported by the network element providing the sensing service from relevant storage network elements. The third network element determines the second network element based on the correspondence and the sensing area information. The third network element feeds back the relevant information of the second network element to the first network element. The relevant storage network elements are, for example, NRF, UDM, etc.
[0220] In some embodiments, the implementation of the first network element requesting the third network element to determine an available second network element can be as follows: the first network element sends a request to the third network element, the request including sensing area information. The third network element sends a request to a relevant storage network element, the request including sensing area information. The relevant storage network element determines the second network element based on the correspondence between locally stored sensing areas and the service areas supported by the network element providing sensing services, and the sensing area information. The relevant storage network element feeds back relevant information about the second network element to the third network element. The third network element feeds back relevant information about the second network element to the first network element.
[0221] In step S2104, the first network element 101 sends a second request to the second network element 102.
[0222] In some embodiments, the second network element receives a second request. For example, the second network element 102 receives a second request sent by the first network element 101. For example, assuming the name of the first network element is NEF and the name of the second network element is SF, then NEF sends a second request to SF, and SF receives the second request sent by NEF.
[0223] In some embodiments, the second request is used to request a perception service.
[0224] In some embodiments, the name of the second request is not limited, and its name may be, for example, a perception service request, a perception data request, a perception result request, etc.
[0225] In some embodiments, the second request includes some or all of the information in the first request. Optionally, the second request includes at least one of the following:
[0226] The identifier of the node requesting the awareness service;
[0227] Time information;
[0228] Sensing precision information;
[0229] Sensing area information;
[0230] Perceive entity information.
[0231] For example, the second request includes time information, perception accuracy information, and perception area information.
[0232] For example, the second request includes perception accuracy information and perception entity information.
[0233] In some embodiments, the first network element can directly send a second request to the second network element. The second network element receives the second request sent directly by the first network element.
[0234] In some embodiments, the implementation of the first network element sending a second request to the second network element can be: the first network element directly sends the second request to the second network element.
[0235] In some embodiments, the implementation of the first network element sending a second request to the second network element can be as follows: the first network element can indirectly send the second request to the second network element through a third network element. For example, the first network element sends a sensing service request to the third network element, the third network element generates a second request based on the sensing service request, and the third network element sends the second request to the second network element. The second network element receives the second request sent by the third network element triggered by the first network element.
[0236] In step S2105, the second network element 102 determines whether there is a sensing entity 104 performing a sensing task.
[0237] Among them, the perception task refers to the perception measurement task that the perception entity needs to perform in order to provide perception services.
[0238] In some embodiments, the implementation of the second network element determining whether a sensing entity performing a sensing task exists includes: the second network element determining whether a sensing entity performing a sensing task exists based on a second request. For example, the second network element determines whether a sensing entity meeting the requirements exists based on at least one of time information, sensing accuracy information, sensing area information, and sensing entity information.
[0239] For example, the sensing entity information includes the sensing entity ID, and the second network element queries whether a corresponding sensing entity exists based on the sensing entity ID.
[0240] For example, the second network element queries whether there is a sensing entity that meets the corresponding sensing accuracy requirements based on the sensing accuracy information.
[0241] For example, the second network element queries whether there is an idle sensing entity that can perform sensing measurements on the corresponding sensing area based on the sensing area information.
[0242] In some embodiments, steps S2106 to S2110 are not executed if no sensing entity is performing the sensing task. In some embodiments, as shown in FIG2C, the second network element may send a response message to the first network element indicating that no sensing entity is performing the sensing task. The first network element sends a rejection message to the node, which includes a rejection reason, namely, that no sensing entity is performing the sensing task.
[0243] In some embodiments, if a sensing entity is present to perform a sensing task, step S2106 is performed.
[0244] In step S2106, the second network element 102 sends a third request to the sensing entity 104.
[0245] In some embodiments, the sensing entity receives a third request.
[0246] In some embodiments, the third request is used to request the acquisition of perceived data.
[0247] In some embodiments, the third request is used to request a perception service.
[0248] In some embodiments, the third request is used to instruct the execution of a perception task.
[0249] In some embodiments, the name of the third request is not limited, and it may be, for example, a sensing measurement indication, a data acquisition indication, etc.
[0250] In some embodiments, the third request includes at least one of the following:
[0251] The identification of perceived entities;
[0252] Time information;
[0253] Perceive precision information.
[0254] For example, the third request includes time information and perception accuracy information.
[0255] For example, the third request includes the identifier and time information of the perceived entity.
[0256] For example, the third request includes time information.
[0257] In some embodiments, the sensing entity is an entity with sensing and measurement capabilities. The sensing entity may be a terminal, network device, Internet of Things (IoT) device, etc.
[0258] In step S2107, the sensing entity 104 sends sensing data to the second network element 102.
[0259] In some embodiments, upon receiving a third request, the sensing entity can perform a sensing task, i.e., perform sensing measurements, according to the requirements of the third request, thereby obtaining sensing data. The sensing entity then sends the sensing data to the second network element.
[0260] In step S2108, the second network element 102 processes the sensing data to obtain the sensing result.
[0261] In some embodiments, the second network element receives sensing data sent by the sensing entity. The second network element can process the sensing data to obtain sensing results. Processing methods include, but are not limited to, noise removal and target value calculation. Target values may be, for example, ambient temperature, humidity, or the speed and shape of the sensed target.
[0262] For implementation methods of processing the perceived data to obtain the perceived results, please refer to related technologies; the embodiments disclosed herein will not be described in detail.
[0263] In step S2109, the second network element 102 sends a response message including the sensing result to the first network element 101.
[0264] In some embodiments, after determining the sensing result, the second network element may send a response message including the sensing result to the first network element.
[0265] In some embodiments, the first network element receives a response message from the second network element that includes the sensing results.
[0266] In step S2110, the first network element 101 sends the sensing result to node 105.
[0267] In some embodiments, upon receiving the sensing result, the first network element sends the sensing result to the node, thereby completing the response to the first request and achieving the purpose of providing sensing services to the node.
[0268] In some embodiments, a node receives sensing results. For example, node 105 receives sensing results sent by a first network element 101.
[0269] 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", and "data" can be used interchangeably.
[0270] 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.”
[0271] 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.
[0272] In some embodiments, terms such as “send,” “transmit,” “report,” “distribute,” “transfer,” “bidirectional transmission,” “send and / or receive” can be used interchangeably.
[0273] 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.
[0274] 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.
[0275] 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.
[0276] The communication method involved in the embodiments of this disclosure may include at least one of steps S2101 to S2110. For example, step S2102 may be implemented as a separate embodiment, step S2105 may be implemented as a separate embodiment, and steps S2102 and S2105 may be implemented as separate embodiments, but are not limited thereto.
[0277] In some embodiments, the order of any two steps in steps S2101 to S2110 can be interchanged or they can be performed simultaneously.
[0278] In some embodiments, steps S2101 and S2103 to S2110 are optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0279] In some embodiments, steps S2101 to S2104 and steps S2106 to S2110 are optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0280] In some embodiments, steps S2101, S2103, S2104, and S2106 to S2110 are optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0281] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0282] Figure 2B is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2B, the present disclosure relates to a communication method executed by a communication system 100, and the method includes at least one of the following steps:
[0283] Step S2201: Node 105 sends a first request to the first network element 101.
[0284] The optional implementation of step S2201 can be found in the optional implementation of step S2101 in Figure 2A, and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.
[0285] Step S2202: The first network element 101 determines whether node 105 is authorized to request the perception service.
[0286] The optional implementation of step S2202 can be found in the optional implementation of step S2102 in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.
[0287] In step S2203, node 105 is not authorized to request the perception service, and the first network element 101 sends a rejection message to node 105.
[0288] In some embodiments, a node receives a rejection message. For example, node 105 receives a rejection message sent by first network element 101.
[0289] In some embodiments, the rejection message may include a rejection reason, such as the node not being authorized to request the awareness service, the node not having service permissions, or the node failing authentication.
[0290] The communication method involved in the embodiments of this disclosure may include at least one of steps S2201 to S2203. For example, step S2202 may be implemented as a standalone embodiment, but is not limited thereto.
[0291] In some embodiments, the order of any two steps in steps S2201 and S2203 can be interchanged or they can be performed simultaneously.
[0292] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0293] Figure 2C is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 2C, the present disclosure relates to a communication method executed by a communication system 100, and the method includes at least one of the following steps:
[0294] Step S2301: Node 105 sends a first request to the first network element 101.
[0295] The optional implementation of step S2301 can be found in the optional implementation of step S2101 in Figure 2A, and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.
[0296] Step S2302: The first network element 101 determines whether node 105 is authorized to request the perception service.
[0297] The optional implementation of step S2302 can be found in the optional implementation of step S2102 in Figure 2A and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.
[0298] In step S2303, node 105 is authorized to request the perception service, and the first network element 101 determines the second network element 102 to provide the perception service.
[0299] The optional implementation of step S2303 can be found in the optional implementation of step S2103 in Figure 2A, and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.
[0300] In step S2304, the first network element 101 sends a second request to the second network element 102.
[0301] The optional implementation of step S2304 can be found in the optional implementation of step S2104 in Figure 2A, and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.
[0302] In step S2305, the second network element 102 determines whether there is a sensing entity 104 performing a sensing task.
[0303] The optional implementation of step S2305 can be found in the optional implementation of step S2105 in Figure 2A, and other related parts in the embodiments involved in Figure 2A, which will not be repeated here.
[0304] In step S2306, if there is no sensing entity performing the sensing task, the second network element 102 sends a response message to the first network element 101 indicating that there is no sensing entity performing the sensing task.
[0305] In some embodiments, the first network element receives a response message sent by the second network element and generates a rejection message based on the content indicated by the response message that there is no sensing entity performing the sensing task.
[0306] In step S2307, the first network element 101 sends a rejection message to node 105.
[0307] In some embodiments, the node receives a rejection message sent by a first network element. For example, the node receives a rejection message sent by a first network element.
[0308] In some embodiments, the rejection message includes a rejection reason, such as the absence of a sensing entity performing the sensing task.
[0309] The communication method involved in the embodiments of this disclosure may include at least one of steps S2301 to S2307. For example, step S2302 may be implemented as a separate embodiment, step S2305 may be implemented as a separate embodiment, and steps S2302 and S2305 may be implemented as separate embodiments, but are not limited thereto.
[0310] In some embodiments, the order of any two steps in steps S2301 to S2307 can be interchanged or they can be performed simultaneously.
[0311] In some embodiments, steps S2301 and S2303 to S2307 are optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0312] In some embodiments, steps S2301 to S2304, S2306, and S2307 are optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0313] In some embodiments, steps S2301, S2303, S2304, and S2306 to S2307 are optional, and one or more of these steps may be omitted or substituted in different embodiments.
[0314] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0315] Figure 3A is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3A, the embodiment of the present disclosure relates to a communication method executed by a first network element, the method comprising:
[0316] Step S3101: Receive the first request sent by the receiving node. The first request is used to request the perception service.
[0317] Optionally, the first request includes at least one of the following:
[0318] Node identifier;
[0319] Time information;
[0320] Sensing precision information;
[0321] Sensing area information;
[0322] Perceive entity information.
[0323] Step S3102: Determine whether the node is authorized to request the awareness service.
[0324] Optionally, determining whether a node is authorized to request a sensing service includes: determining that the node is authorized to request a sensing service; the communication method further includes: determining a second network element that provides the sensing service based on the sensing area information; sending a second request to the second network element, the second request including some or all of the information in the first request, the second request being used to request the sensing service.
[0325] Optionally, there are multiple network elements providing sensing services. The first network element stores a correspondence between a sensing area and a service area supported by the network element providing the sensing service. The first network element determines the second network element providing the sensing service based on the sensing area information, including: determining the second network element from multiple network elements providing the sensing service based on the sensing area information and the correspondence.
[0326] Optionally, the first network element determines the second network element that provides sensing services based on the sensing area information, including: requesting the third network element to determine the second network element based on the sensing area information.
[0327] Optionally, the communication method further includes: receiving a response message sent by the second network element; sending the perception result to the node if the response message includes the perception result corresponding to the perception service; or, sending a rejection message to the node if the response message indicates that there is no perception entity performing the perception task, the rejection message including a rejection reason.
[0328] Optionally, determining whether a node is authorized to request the awareness service includes: determining that the node is not authorized to request the awareness service; the communication method further includes: sending a rejection message to the node, the rejection message including a rejection reason.
[0329] Optionally, the node is a third-party application function (AF) and / or a core network device.
[0330] Optionally, the first network element is a Network Open Function (NEF).
[0331] Optionally, the second network element is a sensing function (SF).
[0332] Optionally, the third network element is the Access and Mobility Management Function (AMF).
[0333] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0334] Figure 3B is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3B, the embodiment of the present disclosure relates to a communication method executed by a second network element, the method comprising:
[0335] Step S3201: Receive a second request, which is used to request the perception service.
[0336] Optionally, a second request generated and sent by the first network element according to the first request is received. The first request is used by the node to request the sensing service from the first network element, and the second request is generated and sent by the first network element when it determines that the node is authorized to request the sensing service.
[0337] Optionally, receiving a second request includes: receiving a second request directly sent by the first network element; or receiving a second request indirectly sent by the first network element through a third network element.
[0338] Optionally, the second request includes at least one of the following:
[0339] The identifier of the node requesting the awareness service;
[0340] Time information;
[0341] Sensing precision information;
[0342] Sensing area information;
[0343] Perceive entity information.
[0344] Step S3202: Determine whether there is a sensing entity performing the sensing task based on the second request.
[0345] Optionally, determining whether a sensing entity performing a sensing task exists based on the second request includes: determining that a sensing entity performing a sensing task exists; the communication method further includes: sending a third request to the sensing entity, the third request being used to request sensing data.
[0346] Optionally, the third request includes at least one of the following:
[0347] The identification of perceived entities;
[0348] Time information;
[0349] Perceive precision information.
[0350] Optionally, the communication method further includes:
[0351] Receive sensing data sent by the sensing entity;
[0352] The perceived data is processed to obtain the perceived results;
[0353] Send a response message to the first network element. The response message includes the sensing result.
[0354] Optionally, determining whether a sensing entity performing a sensing task exists according to the second request includes: determining that no sensing entity performing a sensing task exists; the communication method further includes: sending a response message to the first network element, the response message indicating that no sensing entity performing a sensing task exists.
[0355] Optionally, the node is a third-party application function (AF) and / or a core network device.
[0356] Optionally, the first network element is a Network Open Function (NEF).
[0357] Optionally, the second network element is a sensing function (SF).
[0358] Optionally, the third network element is the Access and Mobility Management Function (AMF).
[0359] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0360] Figure 3C is a flowchart illustrating a communication method according to an embodiment of the present disclosure. As shown in Figure 3B, this embodiment of the disclosure relates to a communication method executed by a node, the method including:
[0361] Step S3301: Send a first request to the first network element. The first request is used to request the sensing service. The first request is used by the first network element to determine whether the node is authorized to request the sensing service.
[0362] Optionally, the first / second request includes at least one of the following:
[0363] The identifier of the node;
[0364] Time information;
[0365] Sensing precision information;
[0366] Sensing area information;
[0367] Perceive entity information.
[0368] Optionally, the communication method further includes: receiving a sensing result sent by the first network element; or receiving a rejection message sent by the first network element, wherein the rejection message includes a rejection reason.
[0369] Optionally, the node includes at least one of the following:
[0370] Third-party application functionality (AF);
[0371] Core network equipment.
[0372] Optionally, the first network element is a Network Open Function (NEF).
[0373] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0374] The communication method disclosed herein addresses the issue of how the 5G core network (5GC) authorizes sensing service requests initiated by sensing service consumers by defining a network open function (i.e., the first network element). In embodiments of this disclosure, the network open function includes at least one of the following functions:
[0375] Whether authorized sensing service consumers are allowed to send sensing service requests;
[0376] Based on the mapping relationship between the stored geographic regions and the sensing service regions (provided by the sensing functions), the sensing functions are discovered and selected.
[0377] Furthermore, embodiments of this disclosure also define a sensing function to check whether the sensing service is authorized under specific conditions / requirements provided by the sensing service consumer.
[0378] In some embodiments, the sensing function (SF) represents the logical functions involved in supporting the sensing service. This includes providing configuration / parameters for sensing entities (sensing transmitters and / or sensing receivers), collecting sensing measurement data, processing the sensing data to generate sensing results and delivering them to sensing service consumers, etc.
[0379] In some embodiments, it is assumed that the Network Open Function (NEF) stores a mapping between the target perceived geographic area and the perceived service area provided by the Sensing Function (SF).
[0380] Figure 4 is an interactive schematic diagram of a communication method according to an embodiment of the present disclosure. As shown in Figure 4, the present disclosure relates to a communication method executed by a communication system, and the method includes at least one of the following steps:
[0381] Step 1: The sensing service consumer (i.e., the requester in the aforementioned embodiments, such as a third-party application function AF) decides to send a sensing service request (i.e., the first request in the aforementioned embodiments) to the network open function (i.e., the first network element in the aforementioned embodiments) in 5GC or 6GC. The request content includes information such as consumer ID, specific time, sensing duration, sensing accuracy, target sensing geographical area, and the location of sensing transmitter and / or receiver.
[0382] Optionally, in 5GC, the Network Opening Function is NEF. Optionally, in 6GC, the Network Opening Function may be a dedicated Network Function (NF).
[0383] Step 2: When the network open function receives a sensing service request, it checks whether the sensing service consumer has the right to request the sensing service.
[0384] Optionally, if the sensing service consumer is authorized, the Network Open Function will discover and select sensing functions (SFs) based on the target sensing geographic area. It is assumed that the Network Open Function stores a mapping between the target sensing geographic area and the sensing service areas provided by the sensing functions (SFs).
[0385] Optionally, if the Sensing Function (SF) is not found, the Network Open Function will report the reason for the failure to the Sensing Service consumer.
[0386] Step 3: The network open function sends the sensing service request (i.e., the second request in the aforementioned embodiment) to the selected sensing function (i.e., the second network element in the aforementioned embodiment, such as SF). The request content includes the parameters specified in step 1.
[0387] Step 4: The sensing function determines the discovery and selection of sensing entities (sensing transmitters / receivers) by considering conditions such as specific time, sensing duration, and the geographic area of the target sensing.
[0388] Optionally, if no suitable sensing entity is found, the sensing function (SF) will send a response to the sensing service consumer via the network open function.
[0389] Step 5: The sensing function (SF) sends a request to initiate sensing service (i.e., the third request in the aforementioned embodiments) to the selected sensing entity. The request includes the sensing entity ID (e.g., sensing transmitter ID and / or sensing receiver ID) and sensing service requirements (specific time, sensing duration, sensing accuracy, etc.).
[0390] Step 6: The sensing entity (i.e., the sensing transmitter and / or receiver) begins to sense the target area and generates sensing measurement data.
[0391] Step 7: Sensing Service. The sensing data is sent to the sensing function (SF) for processing, and the sensing results are then passed to the sensing service consumer.
[0392] In some embodiments, the steps and their optional implementations in other embodiments described before or after this embodiment, as well as other related parts in the specification, can be referred to, and will not be repeated here.
[0393] This disclosure also proposes apparatus (also referred to as communication equipment, etc.) for implementing any of the above methods. For example, an apparatus is proposed that includes units or modules for implementing the steps performed by a node in any of the above methods. Another apparatus is proposed that includes units or modules for implementing the steps performed by a first network element in any of the above methods. Yet another apparatus is proposed that includes units or modules for implementing the steps performed by a second network element in any of the above methods. Yet another apparatus is proposed that includes units or modules for implementing the steps performed by a third network element in any of the above methods. And yet another apparatus is proposed that includes units or modules for implementing the steps performed by a sensing entity in any of the above methods.
[0394] 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). 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). Taking a field-programmable gate array (FPGA) as an example, it 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.
[0395] 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. Furthermore, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a Neural Network Processing Unit (NPU), a Tensor Processing Unit (TPU), or a Deep Learning Processing Unit (DPU).
[0396] Figure 5A is a schematic diagram of the structure of a first network element according to an embodiment of the present disclosure. As shown in Figure 5A, the first network element 5100 may include at least one of a transceiver module 5101, a processing module 5102, etc. In some embodiments, the transceiver module 5101 is used to receive a first request sent by a node, the first request being used to request a sensing service; the processing module 5102 is used to determine whether the node is authorized to request the sensing service. Optionally, the transceiver module is used to perform at least one of the communication steps such as sending and / or receiving performed by the first network element 101 in any of the above methods (e.g., steps S2101, S2104, S2106, S2107, S2109, S2110, S2201, S2203, S2301, S2304, S2306, S2307, but not limited thereto), which will not be described in detail here. Optionally, the above processing module is used to execute at least one of the other steps executed by the first network element 101 in any of the above methods (e.g., steps S2102, S2103, S2105, S2108, S2202, S2302, S2303, S2305, but not limited thereto), which will not be elaborated here.
[0397] Figure 5B is a schematic diagram of the structure of a second network element according to an embodiment of the present disclosure. As shown in Figure 5B, the second network element 5200 may include at least one of a transceiver module 5201, a processing module 5202, etc. In some embodiments, the transceiver module 5201 is used to receive a second request, the second request being used to request a sensing service; optionally, the processing module 5202 is used to determine whether a sensing entity performing a sensing task exists based on the second request. Optionally, the transceiver module is used to perform at least one of the communication steps (e.g., steps S2101, S2104, S2106, S2107, S2109, S2110, S2201, S2203, S2301, S2304, S2306, S2307, but not limited thereto) performed by the second network element 102 in any of the above methods, which will not be described in detail here. Optionally, the above processing module is used to execute at least one of the other steps executed by the second network element 102 in any of the above methods (e.g., steps S2102, S2103, S2105, S2108, S2202, S2302, S2303, S2305, but not limited thereto), which will not be elaborated here.
[0398] Figure 5C is a schematic diagram of the node structure according to an embodiment of the present disclosure. As shown in Figure 5C, node 5300 may include at least one of a transceiver module 5301, a processing module 5302, etc. In some embodiments, the transceiver module 5301 sends a first request to a first network element, the first request being used to request a sensing service, and the first request being used by the first network element to determine whether the node is authorized to request the sensing service. Optionally, the transceiver module is used to perform at least one of the communication steps (e.g., steps S2101, S2104, S2106, S2107, S2109, S2110, S2201, S2203, S2301, S2304, S2306, S2307, but not limited thereto) performed by node 105 in any of the above methods, which will not be described in detail here. Optionally, the above processing module is used to execute at least one of the other steps executed by node 105 in any of the above methods (e.g., steps S2102, S2103, S2105, S2108, S2202, S2302, S2303, S2305, but not limited thereto), which will not be elaborated here.
[0399] 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.
[0400] 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.
[0401] Figure 6A is a schematic diagram of the structure of a communication device 6100 according to an embodiment of the present disclosure. The communication device 6100 can be a network device (e.g., a first network element, a second network element, a third network element, a sensing entity, a node, etc.), a terminal (e.g., a sensing entity), 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.
[0402] As shown in Figure 6A, the communication device 6100 is used to execute any of the above methods. In some embodiments, the communication device 6100 includes one or more processors 6101. The processor 6101 may be a general-purpose processor or a special-purpose processor, such as a baseband processor or a central processing unit. The baseband processor may be used to process communication protocols and communication data, and the central processing unit may be used to control communication devices (e.g., base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Optionally, the communication device 6100 is used to execute any of the above methods. Optionally, one or more processors 6101 are used to invoke instructions to cause the communication device 6100 to execute any of the above methods.
[0403] In some embodiments, the communication device 6100 further includes one or more transceivers 6102. When the communication device 6100 includes one or more transceivers 6102, the transceivers 6102 perform at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S2101, S2104, S2106, S2107, S2109, S2110, S2201, S2203, S2301, S2304, S2306, S2307, but not limited thereto), and the processor 6101 performs at least one of other steps (e.g., steps S2102, S2103, S2105, S2108, S2202, S2302, S2303, S2305, but not limited thereto). In optional embodiments, the transceiver may include a receiver and / or a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, transceiver circuit, interface circuit, interface, etc., can be used interchangeably; the terms transmitter, transmitting unit, transmitter, transmitting circuit, etc., can be used interchangeably; the terms receiver, receiving unit, receiver, receiving circuit, etc., can be used interchangeably.
[0404] In some embodiments, the communication device 6100 further includes one or more memories 6103 for storing data and / or instructions. Optionally, one or more processors 6101 are used to invoke instructions stored in the memory 6103 to cause the communication device 6100 to perform any of the above methods. Optionally, all or part of the memory 6103 may also be located outside the communication device 6100. In an optional embodiment, the communication device 6100 may include one or more interface circuits 6104. Optionally, the interface circuit 6104 is connected to the memory 6103 and can be used to receive data and / or instructions from the memory 6103 or other devices, and can be used to send data and / or instructions to the memory 6103 or other devices. For example, the interface circuit 6104 can read data and / or instructions stored in the memory 6103 and send the data and / or instructions to the processor 6101.
[0405] 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 a 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, programs and / or instructions; (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.
[0406] Figure 6B is a schematic diagram of the structure of chip 6200 according to an embodiment of the present disclosure. For cases where the communication device 6100 can be a chip or a chip system, the schematic diagram of chip 6200 shown in Figure 6B can be referenced, but is not limited thereto.
[0407] Chip 6200 includes one or more processors 6201. Chip 6200 is used to perform any of the methods described above.
[0408] In some embodiments, chip 6200 further includes one or more interface circuits 6202. Optionally, terms such as interface circuit, interface, and transceiver pin can be used interchangeably. In some embodiments, chip 6200 further includes one or more memories 6203 for storing data and / or instructions. Optionally, all or part of the memories 6203 may be located outside of chip 6200. Optionally, interface circuit 6202 is connected to memory 6203, and interface circuit 6202 can be used to receive data and / or instructions from memory 6203 or other devices, and interface circuit 6202 can be used to send data and / or instructions to memory 6203 or other devices. For example, interface circuit 6202 can read data and / or instructions stored in memory 6203 and send the data and / or instructions to processor 6201.
[0409] In some embodiments, the interface circuit 6202 performs at least one of the communication steps such as sending and / or receiving in the above method (e.g., steps S2101, S2104, S2106, S2107, S2109, S2110, S2201, S2203, S2301, S2304, S2306, S2307, but not limited thereto). For example, the interface circuit 6202 performing the communication steps such as sending and / or receiving in the above method means that the interface circuit 6202 performs data and / or instruction interaction between the processor 6201, the chip 6200, the memory 6203, or the transceiver device. In some embodiments, the processor 6201 performs at least one of other steps (e.g., steps S2102, S2103, S2105, S2108, S2202, S2302, S2303, S2305, but not limited thereto).
[0410] The modules and / or devices described in the various embodiments, such as virtual devices, physical devices, and chips, can be combined or separated arbitrarily as needed. Optionally, some or all steps can also be performed collaboratively by multiple modules and / or devices, which is not limited here.
[0411] This disclosure also proposes a storage medium storing instructions that, when executed on a communication device, cause the communication device 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.
[0412] This disclosure also proposes a program product, including a program and / or instructions, which, when executed by a communication device, cause the communication device to perform any of the above methods. Optionally, the program product is a computer program product. Optionally, the program product is stored on the storage medium.
[0413] 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, The method, executed by the first network element, includes: The receiving node sends a first request, which is used to request the perception service; Determine whether the node is authorized to request the perception 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 node; Time information; Sensing precision information; Sensing area information; Perceive entity information.
3. The method according to claim 2, characterized in that, Determining whether the node is authorized to request the perception service includes: The node is determined to authorize the perception service; The method further includes: The second network element is determined based on the sensing area information, and the second network element is one of the multiple network elements that provide the sensing service; A second request is sent to the second network element. The second request includes some or all of the information in the first request. The second request is used to request the sensing service.
4. The method according to claim 3, characterized in that, Determining the second network element based on the sensing area information includes: Based on the sensing area information and the correspondence between the multiple sensing areas stored on the first network element and the service areas of the multiple network elements, one of the multiple network elements is determined as the second network element.
5. The method according to claim 3, characterized in that, Determining the second network element based on the sensing area information includes: The third network element is requested to determine the second network element based on the sensing area information.
6. The method according to any one of claims 3-5, characterized in that, The method further includes: Receive the response message sent by the second network element; If the response message includes the perception result corresponding to the perception service, the perception result is sent to the node; or, If the response message indicates that there is no sensing entity performing the sensing task, a rejection message is sent to the node, the rejection message including a reason for rejection.
7. The method according to claim 1 or 2, characterized in that, Determining whether the node is authorized to request the perception service includes: It was determined that the node was not authorized to request the perception service; The method further includes: A rejection message is sent to the node, the rejection message including a reason for rejection.
8. The method according to any one of claims 1-7, characterized in that, The node is a third-party application function (AF) and / or a core network device.
9. The method according to any one of claims 1-8, characterized in that, The first network element is the Network Open Function (NEF).
10. The method according to any one of claims 3-6, characterized in that, The second network element is the sensing function SF.
11. The method according to claim 5, characterized in that, The third network element is the Access and Mobility Management Function (AMF).
12. A communication method, characterized in that, The method, executed by a node, includes: A first request is sent to a first network element. The first request is used to request a sensing service. The first request is used by the first network element to determine whether the node is authorized to request the sensing service.
13. The method according to claim 12, characterized in that, The first request includes at least one of the following: The identifier of the node; Time information; Sensing precision information; Sensing area information; Perceive entity information.
14. The method according to claim 12 or 13, characterized in that, The method further includes: Receive the sensing result sent by the first network element; or, receive the rejection message sent by the first network element, wherein the rejection message includes a rejection reason.
15. The method according to any one of claims 12-14, characterized in that, The node is a third-party application function (AF) and / or a core network device.
16. The method according to any one of claims 12-14, characterized in that, The first network element is the Network Open Function (NEF).
17. A communication method, characterized in that, The method, executed by the second network element, includes: The system receives a second request generated and sent by a first network element based on a first request. The first request is used by the node to request a sensing service from the first network element. The second request is generated and sent by the first network element when it determines that the node is authorized to request the sensing service. Determine whether a sensing entity exists to perform a sensing task based on the second request.
18. The method according to claim 17, characterized in that, The first request includes at least one of the following: The identifier of the node; Time information; Sensing precision information; Sensing area information; Perceive entity information.
19. The method according to claim 17 or 18, characterized in that, The second request includes at least one of the following: The identifier of the node; Time information; Sensing precision information; Sensing area information; Perceive entity information.
20. The method according to any one of claims 17-19, characterized in that, The step of determining whether a sensing entity performs a sensing task based on the second request includes: There exists a sensing entity that performs the sensing task; The method further includes: A third request is sent to the sensing entity, the third request being used to request sensing data.
21. The method according to claim 20, characterized in that, The third request includes at least one of the following: The identifier of the perceived entity; Time information; Perceive precision information.
22. The method according to claim 20 or 21, characterized in that, The method further includes: Receive sensing data sent by the sensing entity; The sensing data is processed to obtain the sensing results; A response message is sent to the first network element, the response message including the sensing result.
23. The method according to any one of claims 17-19, characterized in that, The step of determining whether a sensing entity performs a sensing task based on the second request includes: The sensing entity performing the sensing task does not exist; The method further includes: A response message is sent to the first network element, the response message indicating that there is no sensing entity performing the sensing task.
24. The method according to any one of claims 17-23, characterized in that, The node is a third-party application function (AF) and / or a core network device.
25. The method according to any one of claims 17-24, characterized in that, The first network element is the Network Open Function (NEF).
26. A Network Open Function (NEF) characterized in that, include: The transceiver module is used to receive the first request sent by the node, which is used to request the perception service; The processing module is used to determine whether the node is authorized to request the perception service.
27. A node, characterized in that, include: The transceiver module is used to send a first request to a first network element. The first request is used to request a sensing service, and the first request is used by the first network element to determine whether the node is authorized to request the sensing service.
28. A sensing function SF, characterized in that, include: The transceiver module is used to receive a second request generated and sent by the first network element according to the first request. The first request is used by the node to request the sensing service from the first network element. The second request is generated and sent by the first network element when it is determined that the node is authorized to request the sensing service. The processing module is used to determine whether there is a sensing entity performing a sensing task based on the second request.
29. A Network Open Function (NEF) characterized in that, include: One or more processors; A memory coupled to the processor, the memory storing executable instructions, which, when executed by the processor, cause the first network element to perform the communication method according to any one of claims 1-11.
30. A node, characterized in that, include: One or more processors; A memory coupled to the processor, the memory storing executable instructions, which, when executed by the processor, cause the node to perform the communication method of any one of claims 12-16.
31. A sensing function SF, characterized in that, Includes: One or more processors; A memory coupled to the processor, the memory storing executable instructions, which, when executed by the processor, cause the second network element to perform the communication method of any one of claims 17-25.
32. A communication system, characterized in that, The system includes a first network element, a node, and a second network element, wherein the first network element is configured to implement the communication method of any one of claims 1-11, the node is configured to implement the communication method of any one of claims 12-16, and the second network element is configured to implement the communication method of any one of claims 17-25.
33. A storage medium storing instructions, characterized in that, When the instructions are executed on the communication device, the communication device performs the communication method according to any one of claims 1-25.
34. 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 a communication device, it implements the communication method of any one of claims 1-25.
