Communication method, network functional entity, and user equipment

Abstract

The embodiments of the present disclosure relate to a communication method, a network functional entity, and a user equipment (UE). The communication method comprises: a first network functional entity sending a first request, wherein the first request is used for requesting the acquisition of authorization information for executing a first operation, the first operation comprising associating a sensing result with identification information related to a UE. By means of the method, a more improved authorization mechanism is provided, and after receiving authorization information, a first network functional entity can associate on the basis of the authorization information a sensing result with identification information related to a UE.

Description

Communication method, network function entity and user equipment Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a communication method, a network function entity, and a user equipment. Background Art

[0002] The purpose of wireless sensing technology is to obtain information about remote objects and their characteristics without physical contact. By analyzing the sensing data of the remote object and its surroundings, meaningful information about the remote object and its characteristics can be obtained.

[0003] By sensing the wireless communication channel and environment, the performance of the communication system can be further improved. Currently, it is necessary to further improve the sensing mechanism to further improve the performance and security of the communication system.

[0004] Summary of the Invention

[0005] The embodiments of the present disclosure provide a communication method, a network function entity, and a user equipment to further improve the perception mechanism.

[0006] In a first aspect, an embodiment of the present disclosure provides a communication method, performed by a first network function entity, the method comprising:

[0007] Sending a first request; wherein the first request is used to request authorization information for performing a first operation; the first operation includes associating the perception result with identification information related to the user equipment UE.

[0008] In a second aspect, an embodiment of the present disclosure further provides a communication method, which is performed by a third network function entity, and the method includes:

[0009] A first request sent by a first network function entity is received; wherein the first request is used to request authorization information for performing a first operation; and the first operation includes associating a perception result with identification information related to a user equipment UE.

[0010] In a third aspect, an embodiment of the present disclosure further provides a communication method, which is performed by a user equipment UE, and the method includes:

[0011] Sending a third message to the first network function entity;

[0012] The third message includes authorization information for performing the first operation; or the third message indicates authorization failure; and the first operation includes identification information related to the associated perception result and the user equipment UE.

[0013] In a fourth aspect, an embodiment of the present disclosure further provides a network function entity, wherein the network function entity includes a first network function entity, and the first network function entity includes:

[0014] A sending module is used to send a first request; wherein, the first request is used to request authorization information for performing a first operation; the first operation includes associating the perception result with identification information related to the user equipment UE.

[0015] In a fifth aspect, an embodiment of the present disclosure further provides a network function entity, wherein the network function entity includes a third network function entity, and the third network function entity includes:

[0016] A receiving module is used to receive a first request sent by a first network function entity; wherein the first request is used to request authorization information for performing a first operation; the first operation includes associating the perception result with identification information related to the user equipment UE.

[0017] In a sixth aspect, an embodiment of the present disclosure further provides a user equipment UE, the user equipment including:

[0018] A sending module, configured to send a third message to the first network function entity;

[0019] The third message includes authorization information for performing the first operation; or the third message indicates authorization failure; and the first operation includes identification information related to the associated perception result and the user equipment UE.

[0020] In a seventh aspect, an embodiment of the present disclosure further provides a communication device, including:

[0021] one or more processors;

[0022] The communication device is used to execute the communication method described in the first aspect of the embodiment of the present disclosure.

[0023] In an eighth aspect, an embodiment of the present disclosure further provides a communication device, including:

[0024] one or more processors;

[0025] The communication device is used to execute the communication method described in the second aspect of the embodiment of the present disclosure.

[0026] In a ninth aspect, an embodiment of the present disclosure further provides a communication device, including:

[0027] one or more processors;

[0028] The communication device is used to execute the communication method described in the third aspect of the embodiment of the present disclosure.

[0029] In the tenth aspect, an embodiment of the present disclosure further provides a communication system, comprising a first network function entity, a third network function entity and a user device; wherein the first network function entity is configured to implement the communication method described in the first aspect, the third network function entity is configured to implement the communication method described in the second aspect, and the user device is configured to implement the communication method described in the third aspect.

[0030] In the eleventh aspect, an embodiment of the present disclosure further provides a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes the communication method described in the first, second, and third aspects of the embodiment of the present disclosure.

[0031] In an embodiment of the present disclosure, the first operation includes associating the perception result with identification information related to the user equipment UE. The first network function entity sends a first request, and the first request is used to request authorization information for performing the first operation. In this way, after receiving the authorization information, the first network function entity can perform related operations of associating the perception result with identification information related to the user equipment UE based on the authorization information, thereby providing a more complete perception mechanism.

[0032] Additional aspects and advantages of the embodiments of the present disclosure will be given in part in the following description, which will become apparent from the following description or be learned through practice of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0033] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

[0034] FIG1 is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure;

[0035] FIG2 is one of exemplary interaction diagrams of a method provided according to an embodiment of the present disclosure;

[0036] FIG3 is a second exemplary interaction diagram of a method provided according to an embodiment of the present disclosure;

[0037] FIG4 is a third exemplary interaction diagram of a method provided according to an embodiment of the present disclosure;

[0038] FIG5 is a fourth exemplary interaction diagram of a method provided according to an embodiment of the present disclosure;

[0039] FIG6 is a fifth exemplary interaction diagram of a method provided according to an embodiment of the present disclosure;

[0040] FIG7 is a flow chart of a communication method according to an embodiment of the present disclosure;

[0041] FIG8 is a second flow chart of the communication method provided in an embodiment of the present disclosure;

[0042] FIG9 is a third flow chart of the communication method provided in an embodiment of the present disclosure;

[0043] FIG10 is a fourth flow chart of the communication method provided in an embodiment of the present disclosure;

[0044] FIG11 is a fifth flow chart of the communication method provided in an embodiment of the present disclosure;

[0045] FIG12 is a sixth flow chart of the communication method provided in an embodiment of the present disclosure;

[0046] FIG13 is a seventh flow chart of a communication method according to an embodiment of the present disclosure;

[0047] FIG14 is a flow chart of the communication method according to an embodiment of the present disclosure;

[0048] FIG15 is a sixth exemplary interaction diagram of a method according to an embodiment of the present disclosure;

[0049] FIG16 is a schematic structural diagram of a first network function entity proposed in an embodiment of the present disclosure;

[0050] FIG17 is a schematic structural diagram of a third network function entity proposed in an embodiment of the present disclosure;

[0051] FIG18 is a schematic diagram of the structure of a user equipment proposed in an embodiment of the present disclosure;

[0052] FIG19 is a schematic diagram of the structure of a terminal proposed in an embodiment of the present disclosure;

[0053] FIG20 is a schematic diagram of the structure of the chip proposed in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0054] The embodiments of the present disclosure provide a communication method, a network function entity, and a user equipment.

[0055] In a first aspect, an embodiment of the present disclosure provides a communication method, which is performed by a first network function entity, including:

[0056] Sending a first request; wherein the first request is used to request authorization information for performing a first operation; the first operation includes associating the perception result with identification information related to the user equipment UE.

[0057] In the above embodiment, a more complete perception mechanism is provided, wherein the first operation includes associating the perception result with identification information related to the user equipment UE, the first network function entity sends a first request, and the first request is used to request authorization information for performing the first operation. In this way, after receiving the authorization information, the first network function entity can perform related operations of associating the perception result with the identification information related to the user equipment UE according to the authorization information.

[0058] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0059] Determine that association authorization indication information or a perception request is received, and send the first request; wherein the association authorization indication information is used to indicate the association of the perception result with identification information related to the UE; the perception request is used to request perception of the perception target; or

[0060] Determine that the perception result or the identification information related to the UE is received, and send the first request.

[0061] In the above embodiment, the first network function entity can trigger an operation of requesting to obtain authorization information for executing the association of the perception result with the identification information related to the user equipment UE when receiving the association authorization indication information indicating the association of the perception result with the identification information related to the UE, the perception request requesting to perceive the perception target, the perception result or the identification information related to the UE, thereby improving the reliability of triggering the execution of the first operation.

[0062] In conjunction with some embodiments of the first aspect, in some embodiments, determining that association authorization indication information or a perception request has been received includes at least one of the following:

[0063] Determining that the association authorization indication information or the perception request sent by the second network function entity is received;

[0064] Determining that the association authorization indication information or the perception request sent by the access network device is received;

[0065] Determine whether the association authorization indication information or the perception request sent by the UE, or a client on the UE, or an application function is received.

[0066] In the above embodiment, the first network function entity may receive the associated authorization indication information or the perception request through interactive operations with the second network function entity, the access network device, the UE, or the client on the UE, or the application function on the UE.

[0067] In conjunction with some embodiments of the first aspect, in some embodiments, sending the first request includes:

[0068] Send a first request to the third network function entity.

[0069] In the above embodiment, the first network function entity sends a first request to the third network function entity to further interact with the third network function entity to obtain authorization information for associating the perception result with the identification information related to the user equipment UE.

[0070] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0071] A first message sent by the third network function entity is received; the first message instructs the first network function entity to send the first request to the UE.

[0072] In the above embodiment, the first network function entity interacts with the third network function entity, and after obtaining the first message, can obtain information based on the first message that further interaction with the UE is required to obtain authorization information for executing the associated perception result and the identification information related to the user equipment UE.

[0073] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0074] A first request is sent to the UE.

[0075] In the above embodiment, after obtaining the first message, the first network function entity may continue to send a first request to the UE, so as to obtain authorization information for performing the association of the perception result with the identification information related to the user equipment UE through further interaction with the UE.

[0076] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0077] receiving a second message sent by the third network function entity;

[0078] The second message includes the authorization information; or the second message indicates that the authorization failed.

[0079] In the above embodiment, the first network function entity interacts with the third network function entity, and after obtaining the second message, can obtain whether the third network function entity successfully authorizes the first network function entity according to the second message: associate the perception result with the identification information related to the user equipment UE.

[0080] In combination with some embodiments of the first aspect, in some embodiments, when the second message includes the authorization information, the method further includes:

[0081] The first operation is performed.

[0082] In the above embodiment, when the first network function entity obtains through the second message that the third network function entity successfully authorizes the first network function entity to associate the perception result with the identification information related to the user equipment UE, the first network function entity can associate the perception result with the identification information related to the user equipment UE.

[0083] In combination with some embodiments of the first aspect, in some embodiments, the first network function entity sends the first request after receiving the perception request, and the method further includes:

[0084] sensing the sensing target;

[0085] or

[0086] Triggering the fourth network function entity to perceive the perception target.

[0087] In the above embodiment, after receiving the perception request, the first network function entity sends the first request to the third network function entity. If it is determined based on the second message that the third network function entity has successfully authorized the first network function entity to associate the perception result with the identification information related to the user equipment UE, the first network function entity may perform an operation of perceiving the perception target. Specifically, when perceiving the perception target, the first network function entity may perceive the perception target itself, or the fourth network function entity may be triggered to perceive the perception target.

[0088] In combination with some embodiments of the first aspect, in some embodiments, associating the perception result with identification information related to the UE includes:

[0089] Determining that the first request carries first identification information, and the second message indicates that associating the perception result with the second identification information is allowed, and associating the perception result with the second identification information;

[0090] The UE-related identification information includes the first identification information and the second identification information, and the relationship between the first identification information and the second identification information is: the same or there is a mapping relationship.

[0091] In the above embodiment, the relationship between the first identification information and the second identification information is: the same or a mapping relationship exists, and the first identification information of the UE can be carried in the first request to request authorization information for performing the first operation; at the same time, the third network function entity can instruct the first network function entity to associate the perception result with the second identification information based on the relationship between the first identification information and the second identification information. In this way, the first network function entity can associate the perception information with the second identification information of the UE when the second identification information of the specified UE is carried in the authorization information.

[0092] In conjunction with some embodiments of the first aspect, in some embodiments, when the second message indicates that the authorization fails, the method further includes:

[0093] The first operation is not performed.

[0094] In the above embodiment, when the first network function entity obtains the identification information related to the user equipment UE through the second message that the third network function entity fails to authorize the first network function entity to associate the perception result with the user equipment UE, the first network function entity may not associate the perception result with the identification information related to the user equipment UE.

[0095] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0096] If the first network function entity sends the first request after receiving the perception request, it does not perceive the perception target.

[0097] In the above embodiment, after receiving the perception request, the first network function entity sends the first request to the third network function entity, and according to the second message, when the third network function entity fails to authorize the first network function entity to associate the perception result with the user equipment UE, the operation of perceiving the perception target is not performed.

[0098] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0099] receiving a third message sent by the UE;

[0100] The third message includes the authorization information; or the third message indicates authorization failure.

[0101] In the above embodiment, the first network function entity interacts with the UE and, after obtaining the third message, can obtain whether the UE successfully authorizes the first network function entity based on the third message: associate the perception result with identification information related to the user equipment UE.

[0102] In conjunction with some embodiments of the first aspect, in some embodiments, when the third message includes the authorization information, the method further includes:

[0103] The first operation is performed.

[0104] In the above embodiment, when the first network function entity obtains, through the third message, that the UE successfully authorizes the first network function entity to associate the perception result with the identification information related to the user equipment UE, the first network function entity may associate the perception result with the identification information related to the user equipment UE.

[0105] In combination with some embodiments of the first aspect, in some embodiments, the first network function entity sends the first request after receiving the perception request, and the method further includes:

[0106] sensing the sensing target;

[0107] or

[0108] Triggering the fifth network function entity to perceive the perception target.

[0109] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0110] Determining that the first request carries first identification information, and the third message indicates that associating the perception result with the second identification information is allowed, and associating the second identification information of the UE with the perception result;

[0111] The UE-related identification information includes the first identification information and the second identification information, and the relationship between the first identification information and the second identification information is: the same or there is a mapping relationship.

[0112] In the above embodiment, after receiving the perception request, the first network function entity sends the first request to the UE, and when it is determined based on the third message that the UE has successfully authorized the first network function entity to associate the perception result with the identification information related to the user equipment UE, the first network function entity may perform an operation of perceiving the perception target. Specifically, when perceiving the perception target, the first network function entity may perceive the perception target itself, or the fifth network function entity may be triggered to perceive the perception target.

[0113] In conjunction with some embodiments of the first aspect, in some embodiments, the third message indicates an authorization failure, and the method further includes:

[0114] The first operation is not performed.

[0115] In the above embodiment, when the first network function entity obtains the identification information related to the user equipment UE through the third message and associates the perception result with the identification information related to the user equipment UE, the first network function entity may not associate the perception result with the identification information related to the user equipment UE.

[0116] In combination with some embodiments of the first aspect, in some embodiments, the first network function entity sends the first request after receiving the perception request, and the method further includes:

[0117] The perception target is not perceived.

[0118] In the above embodiment, after receiving the perception request, the first network function entity sends a first request to the UE, and according to the third message, obtains the identification information related to the UE authorization failure and the first network function entity associates the perception result with the user equipment UE, and does not perform the operation of perceiving the perception target.

[0119] In conjunction with some embodiments of the first aspect, in some embodiments, if the first network function entity further receives a first message or a second message sent by a third network function entity, the priority of the third message is higher than the priority of the first message, and the priority of the third message is higher than the priority of the second message;

[0120] The first message indicates that the first network function entity sends the first request to the UE; the second message includes the authorization information; or the second message indicates that the authorization fails.

[0121] In the above embodiment, by setting the priority of the third message to be higher than the priority of the first message, and the priority of the third message to be higher than the priority of the second message, the first network function entity can, when simultaneously receiving the first message sent by the third network function entity and the third message sent by the UE, or when simultaneously receiving the second message sent by the third network function entity and the third message sent by the UE, give priority to determining whether to perform an operation of associating the perception result with the identification information related to the user equipment UE according to the third message sent by the UE.

[0122] In a second aspect, an embodiment of the present disclosure provides a communication method, which is performed by a third network function entity. The method includes:

[0123] A first request sent by a first network function entity is received; wherein the first request is used to request authorization information for performing a first operation; and the first operation includes associating a perception result with identification information related to a user equipment UE.

[0124] In the above embodiment, the third network function entity may determine whether to authorize the first network function entity to perform the first operation according to the received first request sent by the first network function entity.

[0125] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0126] A first message is sent to the first network function entity; the first message instructs the first network function entity to send the first request to the UE.

[0127] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0128] Sending a second message to the first network function entity;

[0129] The second message includes the authorization information; or the second message indicates that the authorization failed.

[0130] In a third aspect, an embodiment of the present disclosure provides a communication method, which is performed by a user equipment (UE). The method includes:

[0131] Sending a third message to the first network function entity;

[0132] The third message includes authorization information for performing the first operation; or the third message indicates authorization failure; and the first operation includes identification information related to the associated perception result and the user equipment UE.

[0133] In the above embodiment, the UE may instruct the first network function entity through the third message whether the UE or the first network function entity performs the first operation.

[0134] In conjunction with some embodiments of the third aspect, in some embodiments, the method further includes:

[0135] Receive a first request sent by the first network function entity; wherein the first request is used to request to obtain the authorization information.

[0136] In a fourth aspect, an embodiment of the present disclosure further provides a network function entity, wherein the network function entity includes a first network function entity, and the above-mentioned first network function entity includes at least one of the sending modules; wherein the above-mentioned first network function entity is used to execute the optional implementation method of the first aspect.

[0137] In a fifth aspect, an embodiment of the present disclosure further provides a network function entity, wherein the network function entity includes a third network function entity, and the third network function entity includes: a receiving module; wherein the third network function entity is used to execute the optional implementation method of the second aspect.

[0138] In a sixth aspect, an embodiment of the present disclosure further provides a user equipment, comprising: a sending module; wherein the sending module is used to execute the optional implementation method of the third aspect.

[0139] In a seventh aspect, an embodiment of the present disclosure further provides a communication device, including:

[0140] one or more processors;

[0141] The communication device is used to execute the optional implementation of the first aspect.

[0142] In an eighth aspect, an embodiment of the present disclosure further provides a communication device, including:

[0143] one or more processors;

[0144] The communication device is used to execute the optional implementation of the second aspect.

[0145] In a ninth aspect, an embodiment of the present disclosure further provides a communication device, including:

[0146] one or more processors;

[0147] The communication device is used to execute the optional implementation of the third aspect.

[0148] In the tenth aspect, an embodiment of the present disclosure further provides a communication system, comprising a first network function entity, a third network function entity, and a user device; wherein, the first network function entity is configured to perform the optional implementation method as described in the first aspect, the third network function entity is configured as the optional implementation method as described in the second aspect, and the user device is configured as the optional implementation method as described in the third aspect.

[0149] In the eleventh aspect, an embodiment of the present disclosure further provides a storage medium storing instructions, which, when executed on a communication device, enables the communication device to execute the optional implementation methods described in the first, second, and third aspects.

[0150] In the twelfth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the optional implementation of the first aspect, the second aspect, and the third aspect.

[0151] In a thirteenth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the optional implementation of the first, second, and third aspects.

[0152] In a fourteenth aspect, an embodiment of the present disclosure provides a chip or a chip system, which includes a processing circuit configured to execute the method described in the optional implementation of the first, second, and third aspects above.

[0153] It is understandable that the aforementioned network function entities, user equipment, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to perform the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0154] The embodiments of the present disclosure provide a communication method, a network function entity, a user equipment, and a communication system. In some embodiments, the terms communication method, signal transmission method, wireless frame transmission method, etc. are interchangeable, and the terms information processing system, communication system, etc. are interchangeable.

[0155] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain 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 certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0156] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0157] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0158] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0159] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0160] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0161] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0162] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0163] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0164] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0165] In some embodiments, terms such as "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 less than", and "above" can be replaced with each other, and terms such as "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" can be replaced with each other.

[0166] In some embodiments, devices and equipment can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc.

[0167] In some embodiments, "network" can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.

[0168] In some embodiments, "access network device (AN device)" may also be referred to as "radio access network device (RAN device)", "base station (BS)", "radio base station", "fixed station", and in some embodiments may also be understood as "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission and / or 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", "bandwidth part (BWP)", etc.

[0169] In some embodiments, "terminal" or "terminal device" may be referred to as "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, client, etc.

[0170] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0171] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0172] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment. Figure 1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure.

[0173] As shown in FIG1 , a communication system 100 includes a network device 101 and a user equipment 102 .

[0174] In some embodiments, the network device 101 may include at least one of a core network device and an access network device. The core network device may include at least one of a first network function entity 1011, a third network function entity 1012, a second network function entity (not shown in FIG1 ), a fourth network function entity (not shown in FIG1 ), and a fifth network function entity (not shown in FIG1 ). For example, the network device 101 may be a base station.

[0175] In some embodiments, a core network device may be a device including one or more network elements (i.e., network function entities), or may be multiple devices or device groups, each including all or part of the one or more network elements. A network element may be virtual or physical. The core network may include, for example, at least one of an Evolved Packet Core (EPC), a 5G Core Network (5GCN), and a Next Generation Core (NGC).

[0176] In some embodiments, the user device 102 may also be referred to as a terminal, and may include, for example, but not limited to, at least one of a mobile phone, a wearable device, an Internet of Things device, a car with communication capabilities, a smart car, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and a wireless terminal device in a smart home, but is not limited thereto.

[0177] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0178] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1 , or a portion thereof, but are not limited thereto. The entities shown in FIG1 are illustrative only. The communication system may include all or part of the entities shown in FIG1 , or may include other entities outside of FIG1 . The number and form of the entities are arbitrary, and the entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0179] The embodiments of the present disclosure 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 (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (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, Open Radio Access Network (O-RAN) systems, systems utilizing other resource determination methods, and next-generation systems based on and extended from these systems, such as the sixth-generation mobile communication system (6G). Furthermore, a combination of multiple systems (e.g., a combination of LTE or LTE-A with 5G) may also be employed.

[0180] Wireless sensing technology aims to obtain information about remote objects and their characteristics without physical contact, and to obtain meaningful information about remote objects and their characteristics by analyzing the sensing data of remote objects and their surroundings.

[0181] For example, radar (radio detection and ranging) is a widely used wireless sensing technology that uses radio waves to determine the distance (or range), angle, or instantaneous linear velocity of a target. In addition, other sensing technologies including non-RF sensors have also been widely used, such as time-of-flight cameras, accelerometers, gyroscopes, and lidar.

[0182] FIG2 is one of interaction schematic diagrams illustrating a communication method according to an embodiment of the present disclosure.

[0183] As shown in FIG2 , the above method includes:

[0184] Step 201: A first network function entity sends a first request, wherein the first request is used to request authorization information for performing a first operation; the first operation includes associating a perception result with identification information (UE identity) related to a user equipment UE.

[0185] In 3GPP systems, integrated sensing and communication means that both sensing and communication capabilities are provided by the same wireless communication system and communications infrastructure. Furthermore, in 3GPP-supported sensing systems, both UEs and access network equipment can serve as sensing senders and receivers. These access network equipment include NR RAN (New Radio) nodes.

[0186] In a perception-assisted communication scenario, in compliance with regulations and with user consent, when perceiving a perception target associated with a UE serving the same network, the network (e.g., 5GS) can associate the perception result of the perception target with the identification information related to the UE (e.g., the UE's 3GPP user identity) to further assist communication based on the perception result and improve the performance of the communication system. Considering that the UE may refuse to associate the perception result with its related identification information, the network needs to obtain the UE's consent / permission / authorization information before making the association. However, there is currently no relevant mechanism for the network function entity in the core network to obtain the UE's consent / permission / authorization information to further associate the perception result of the perception target with the UE's related identification information.

[0187] Based on this, an embodiment of the present disclosure provides a communication method that enables a first network function entity in a core network to obtain authorization information for associating a perception result with identification information related to a user equipment UE, so as to improve the existing perception mechanism.

[0188] Optionally, the first network function entity (Network Function, NF) may include but is not limited to NWDAF (Network Data Analytics Function), a perception module, LMF (Location Management Function), GMLC (Gateway Mobile Location Center), a sensing function, etc.

[0189] Optionally, the first request may include UE-related identification information. Optionally, the UE-related identification information may include the UE's own identification, and may also include an identification related to the UE's user. The identification related to the user of the user may include, but is not limited to, a user permanent identifier (SUBS cription Permanent Identifier, SUPI), a UE's general public identification (Generic Public Subscription Identifier, GPSI), a UE's SUCI (Subscription Concealed Identifier, subscription hidden identifier), a UE's MSISDN (Mobile Subscriber International ISDN / PSTN number (ISDN is the Integrated Services Digital Network, which is the abbreviation of Integrated Service Digital Network; PSTN is the public switched telephone network, which is the abbreviation of Public Switched Telephone Network), a mobile user number), a UE's application identifier, etc.

[0190] Optionally, there is a mapping relationship between different related identification information of the UE. In this way, when the identification information related to the UE includes A and B, B can be determined based on A and the mapping relationship between A and B.

[0191] Optionally, the sensing result is specifically a sensing result obtained by sensing the sensing target, and the sensing result may include but is not limited to the UE's position, speed, motion trajectory, channel environment, etc. By sensing the wireless communication channel and environment, the performance of the communication system can be further improved.

[0192] Optionally, the sensing operation can be performed in the following sensing-assisted communication scenarios:

[0193] 1. Sense the UE’s location and channel environment to narrow the beam scanning range and shorten the beam training time.

[0194] Second, perceive the terminal UE’s position, speed, motion trajectory, and channel environment for beam prediction, and reduce the overhead of beam measurement and the delay of beam tracking.

[0195] 3. Perceive the properties of the terminal UE and the channel environment to improve the performance of channel estimation.

[0196] Optionally, based on actual applications, use cases for communication-assisted awareness services provided by 5GS (5G System, a general term for all 5G network elements, including base stations (NG-RAN) and core networks (5GC)) may include the following:

[0197] 1. Real-time environmental monitoring: Using wireless signals to reconstruct environmental maps to further improve positioning accuracy and associate the environment with applications. For example, these applications include dynamic 3D maps for driving assistance, crowd counting, intrusion detection, traffic detection, and other real-time monitoring applications.

[0198] Unmanned Aerial Vehicles (UVAs): Unmanned aerial vehicles (UVAs) and drones share common functional requirements. For example, they should all support detect and avoid (DAA) capabilities. Furthermore, they should be able to monitor road conditions, including route selection and compliance with traffic regulations.

[0199] 3. Air pollution monitoring: The quality of the received wireless signal will show different attenuation characteristics as the air humidity, particulate matter (PM) concentration, carrier frequency, etc. change. Therefore, weather or air quality detection can be performed based on the quality of the received wireless signal.

[0200] 4. Indoor health care and intrusion detection: It can realize functions such as respiratory rate estimation, respiratory depth estimation, apnea detection, vital signs monitoring of the elderly, and indoor intrusion detection.

[0201] Optionally, in the embodiment of the present disclosure, the authorization information allows the first network function entity to associate the perception result with identification information related to the UE.

[0202] Optionally, the authorization information may specifically include allowing the first network function entity to associate the perception result with a specific identification information of the UE.

[0203] For example, when the UE-related identification information includes the UE's own identification, SUPI, SUCI, GPSI, MSISDN, UE's application identification, etc., the authorization information may include allowing the first network function entity to associate the perception result with at least one identification information of the above-mentioned UE-related identification information.

[0204] Optionally, in an embodiment of the present disclosure, the above method further includes:

[0205] The first NF determines that the association authorization indication information or the perception request is received, and sends the first request; wherein the association authorization indication information is used to indicate the association of the perception result with the identification information related to the UE; the perception request is used to request perception of the perception target; or

[0206] The first NF determines that it has received the perception result or the identification information related to the UE, and sends the first request.

[0207] Optionally, when the first NF receives the above message, the first NF will be triggered to perform an association authorization operation, that is, the first NF sends a first request.

[0208] Optionally, in the first NF, it may be pre-configured that when the first NF receives the sensing result and the identification information related to the UE, the association authorization is triggered. Specifically, it may be configured through the local policy of the NF.

[0209] Optionally, in the embodiment of the present disclosure, the first network function entity determines that the association authorization indication information or the perception request is received, including at least one of the following:

[0210] Determining that association authorization indication information or perception request sent by the second network function entity is received;

[0211] Determining that association authorization indication information or perception request sent by the access network device is received;

[0212] Determine whether to receive association authorization indication information or perception request sent by the UE, or a client on the UE, or an application function.

[0213] Optionally, the access network device may include NG-RAN (Next Generation Radio Access Network).

[0214] Optionally, the client on the UE is a client installed on the UE.

[0215] Optionally, the second network function entity may include other network function entities in the core network device except the first network function entity.

[0216] Optionally, the second NF or NG-RAN can trigger the first NF to initiate an association authorization operation by sending association authorization indication information, perception results or UE-related identification information to the first NF.

[0217] Optionally, a third party (eg, UE, client on the UE, application function, etc.) may trigger the first NF to initiate an association authorization operation by sending association authorization indication information or a perception request to the first NF.

[0218] Optionally, in the embodiment of the present disclosure, the recipient of the first request may include but is not limited to a third network function entity, a UE, etc. That is, the first network function entity may send the first request to the third network function entity; the first network function entity may also send the first request to the UE.

[0219] Optionally, the third network function entity may include other network function entities in the core network device except the first network function entity. Optionally, the third network function entity may be the same as the second network function entity or may be different from the second network function entity.

[0220] Specifically, the third network functional entity may include but is not limited to a unified data management entity (Unified Data Management, UDM) or a unified data storage entity (Unified Data Repository, UDR).

[0221] Optionally, the first NF may interact with a third NF and send a first request to the third NF to indirectly detect, through the third NF, whether the first NF can be authorized to associate the perception result with identification information related to the user equipment UE. Alternatively, the first NF may directly interact with the UE and send the first request to the UE to directly request the UE to authorize the first NF to associate the perception result with identification information related to the user equipment UE. The identity of the UE may include the aforementioned identification information related to the UE.

[0222] Step 202: The recipient of the first request sends a message to the first network function entity.

[0223] Optionally, the message sent by the recipient of the first request may include: a first message, a second message, a third message, etc.

[0224] The first message instructs the first network function entity to send a first request to the UE;

[0225] The second message includes an authorization message, or the second message indicates that the authorization failed;

[0226] The third message includes an authorization message, or the third message indicates that the authorization fails.

[0227] Step 203: The first network function entity performs a second operation according to the message sent by the recipient.

[0228] The second operation may include any one of the following:

[0229] If the message sent by the recipient includes a first message, and the first message instructs the first network function entity to send a first request to the UE, the first network function entity sends the first request to the UE;

[0230] If the message sent by the recipient includes the second message, and the second message includes the authorization message, the first network function entity associates the perception result with identification information related to the user equipment UE;

[0231] If the message sent by the recipient includes the second message, and the second message includes the authorization message, and the first network function entity sends the first request after receiving the perception request, the first network function entity perceives the perception target; or, the first network function entity triggers the fourth network function entity to perceive the perception target;

[0232] If the message sent by the recipient includes the second message, and the second message indicates that the authorization fails, the first network function entity does not associate the perception result with the identification information related to the user equipment UE;

[0233] If the message sent by the recipient includes the second message, and the second message indicates that the authorization fails, and the first network function entity sends the first request after receiving the perception request, the first network function entity does not perceive the perception target;

[0234] If the message sent by the recipient includes the third message, and the third message includes the authorization message, the first network function entity associates the perception result with identification information related to the user equipment UE;

[0235] If the message sent by the recipient includes the third message, and the third message includes the authorization message, and the first network function entity sends the first request after receiving the perception request, the first network function entity perceives the perception target; or, the first network function entity triggers the fifth network function entity to perceive the perception target;

[0236] If the message sent by the recipient includes the third message, and the third message indicates that the authorization fails, the first network function entity does not associate the perception result with the identification information related to the user equipment UE;

[0237] If the message sent by the recipient includes a third message, and the third message indicates authorization failure, and the first network function entity sends the first request after receiving the perception request, the first network function entity does not perceive the perception target.

[0238] Optionally, the fourth network function entity may include other network function entities in the core network device except the first network function entity. Optionally, the fourth network function entity may be the same as one of the second network function entity and the third network function entity, or may be different from both the second network function entity and the third network function entity.

[0239] Optionally, the fifth network function entity may include other network function entities in the core network device except the first network function entity. Optionally, the fifth network function entity may be the same as one of the second network function entity, the third network function entity, and the fourth network function entity, or may be different from the second network function entity, the third network function entity, and the fourth network function entity.

[0240] Optionally, in an embodiment of the present disclosure, if the message sent by the recipient includes a first message, and the first message instructs the first network function entity to send a first request to the UE, that is, during the process of the first NF being used for the recipient of the first request to perform an interactive operation, the recipient of the first request can also trigger the first NF to further send a first request to the UE, that is, trigger the first NF to initiate an association authorization operation to the UE.

[0241] Optionally, if the message sent by the recipient includes a second message, and the second message includes an authorization message, and the first network function entity sends the first request after receiving the perception request, the first network function entity can also obtain the perception result of perceiving the perception target (including but not limited to: the perception result of the first network function entity perceiving the perception target; or, the perception result of the fourth network function entity perceiving the perception target), and associate the perception result with identification information related to the user equipment UE.

[0242] Optionally, if the message sent by the recipient includes a third message, and the third message includes an authorization message, and the first network function entity sends the first request after receiving the perception request, the first network function entity can also obtain the perception result of perceiving the perception target (including but not limited to: the perception result of the first network function entity perceiving the perception target; or, the perception result of the fifth network function entity perceiving the perception target), and associate the perception result with the identification information related to the user equipment UE.

[0243] Optionally, in an embodiment of the present disclosure, if the recipient includes a UE and a third network function entity, and the first network function entity receives a third message sent by the UE while receiving the first message or the second message sent by the third network function entity, the priority of the third message is higher than the priority of the first message, and the priority of the third message is higher than the priority of the second message;

[0244] The first message instructs the first network function entity to send a first request to the UE; the second message includes authorization information; or the second message indicates an authorization failure.

[0245] Optionally, the priority of the third message is higher than the priority of the first message, and the priority of the third message is higher than the priority of the second message. This can be understood as follows: if the first NF receives both the message sent by the third NF (i.e., the first message or the second message) and the third message sent by the UE, the first NF performs subsequent operations based on the third message. If the first NF only receives the message sent by the third NF, the first NF directly performs subsequent operations based on the message. If the first NF only receives the message sent by the UE, the first NF directly performs subsequent operations based on the message.

[0246] As an example, if the first NF simultaneously receives authorization information sent by the UE (i.e., the third message) or authorization information of the third NF (the second message), and the third message indicates that the UE does not allow the perception result to be associated with the identification information related to the UE, and the second message indicates that the third NF allows the perception result to be associated with the identification information related to the UE, then the first NF performs subsequent operations according to the third message, that is, terminates the association of the perception result with the identification information related to the UE.

[0247] Optionally, in the embodiment of the present disclosure, the first NF may further determine that the first request carries the first identification information, and the second message indicates that association of the perception result with the second identification information is allowed, and associate the perception result with the second identification information;

[0248] The UE-related identification information includes first identification information and second identification information, and the relationship between the first identification information and the second identification information is: the same or a mapping relationship exists.

[0249] Optionally, as mentioned above, the UE-related identification information includes the UE's own identification, and may also include an identification related to the UE's user. The identification related to the user may include, but is not limited to, at least one of the UE's SUPI, SUCI, UE's GPSI, UE's MSISDN, and UE's application identification. Furthermore, a mapping relationship exists between different related identification information of the UE. Thus, when the UE-related identification information includes A and B, B can be determined based on A and the mapping relationship between A and B.

[0250] As an example, assuming that the first identification information of the UE includes the SUPI of the UE and the second identification information of the UE includes the GPSI of the UE, the first NF can carry the SUPI of the UE in the first request and send the first request to the UE; if the third message sent by the UE to the first NF carries the GPSI of the UE, the first NF can associate the perception result with the GPSI of the UE after receiving the authorization message.

[0251] Optionally, in the embodiment of the present disclosure, the first NF may further determine that the first request carries the first identification information, and the third message indicates that association of the perception result with the third identification information is allowed, and associate the perception result with the third identification information;

[0252] The UE-related identification information includes first identification information and third identification information, and the relationship between the first identification information and the third identification information is: the same or a mapping relationship exists.

[0253] Optionally, the UE-related identification information includes first identification information, second identification information and third identification information, wherein the relationship between the first identification information, the second identification information and the third identification information is: at least two of the three are the same, and there is a mapping relationship between the three.

[0254] Optionally, when the third message indicates that association of the perception result with the third identification information is allowed, the method of associating the perception result with the third identification information can be specifically referred to the method of associating the perception result with the second identification information when the second message indicates that association of the perception result with the second identification information is allowed, and will not be repeated here.

[0255] Optionally, if the recipient of the first request is a UE, the UE may generate authorization information through a privacy policy on the UE side, and carry the authorization information through a third message to send the authorization information to the first NF.

[0256] Optionally, the privacy policy on the terminal side may be stored in the core network device. The UE obtains the privacy policy through interaction with the core network device and uses the obtained privacy policy as the privacy policy on the terminal side.

[0257] Optionally, each step provided in the embodiment of the present disclosure may be implemented independently, and may be implemented in any combination and in a reversed order under the condition that the steps are not contradictory.

[0258] The communication method involved in the embodiments of the present disclosure may include at least one of the aforementioned steps and embodiments. For example, step 201 may be implemented as an independent embodiment, step 202 may be implemented as an independent embodiment, and step 203 may be implemented as an independent embodiment; the combination of step 201 and step 202 may be implemented as an independent embodiment, the combination of step 201, step 202, and step 203 may be implemented as an independent embodiment, and the combination of step 202 and step 203 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0259] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2 .

[0260] FIG3 is a second interactive schematic diagram of a communication method according to an embodiment of the present disclosure.

[0261] As shown in FIG3 , in some embodiments of the present disclosure, a first NF may send a first request to a third NF by interacting with the third NF, so as to indirectly detect, through the third NF, whether the first NF can be authorized to associate a perception result with identification information related to a user equipment UE. The method may include:

[0262] Step 301: The first network function entity sends a first request to a third network function entity; wherein the first request is used to request authorization information for performing a first operation; and the first operation includes associating a perception result with identification information related to a user equipment UE.

[0263] Optionally, in an embodiment of the present disclosure, the above method further includes:

[0264] The first NF determines that it has received the association authorization indication information or the perception request, and sends a first request to the third NF; wherein the association authorization indication information is used to indicate the association of the perception result with the identification information related to the UE; the perception request is used to request perception of the perception target; or

[0265] The first NF determines that it has received the perception result or the identification information related to the UE, and sends a first request to the third NF.

[0266] Optionally, in the embodiment of the present disclosure, the first network function entity determines that the association authorization indication information or the perception request is received, including at least one of the following:

[0267] Determining that association authorization indication information or perception request sent by the second network function entity is received;

[0268] Determining that association authorization indication information or perception request sent by the access network device is received;

[0269] Determine whether to receive association authorization indication information or perception request sent by the UE, or a client on the UE, or an application function.

[0270] Optionally, in the embodiment of the present disclosure, the first network function entity determines that the association authorization indication information or the perception request is received, including at least one of the following:

[0271] Determining that association authorization indication information or perception request sent by the second network function entity is received;

[0272] Determining that association authorization indication information or perception request sent by the access network device is received;

[0273] Determine whether to receive association authorization indication information or perception request sent by the UE, or a client on the UE, or an application function.

[0274] Optional implementations of step 301 may refer to step 201 in FIG. 2 and other related parts of the embodiment involved in FIG. 2 , which will not be described in detail here.

[0275] Step 302: The third NF sends a first message to the first NF; wherein the first message instructs the first network function entity to send the first request to the UE.

[0276] Optional implementations of step 302 may refer to step 202 in FIG. 2 and other related parts of the embodiment involved in FIG. 2 , and will not be described in detail here.

[0277] Step 303: The first NF sends a first request to the UE.

[0278] Optional implementations of step 303 may refer to step 203 in FIG. 2 and other related parts of the embodiment involved in FIG. 2 , which will not be described in detail here.

[0279] Step 304: The UE sends a third message to the first NF;

[0280] The third message includes authorization information; or the third message indicates authorization failure.

[0281] Optional implementations of step 304 may refer to step 203 in FIG. 2 and other related parts of the embodiment involved in FIG. 2 , which will not be described in detail here.

[0282] Step 305: The first NF performs a third operation according to the third message.

[0283] Here, step 305 may include step 3051 or step 3052.

[0284] Step 3051: The first NF performs the first operation; wherein the third message includes authorization information.

[0285] Optionally, in an embodiment of the present disclosure, if the first NF sends the first request to the UE after receiving the perception request, the first NF perceives the perception target; or, the first NF triggers the fifth NF to perceive the perception target.

[0286] Optionally, if the first NF can also obtain the perception result of perceiving the perception target (including but not limited to: the perception result of the first NF perceiving the perception target; or, the perception result of the fifth NF perceiving the perception target), associate the perception result with the identification information related to the user equipment UE.

[0287] Optionally, in the embodiment of the present disclosure, the first NF may further determine that the first request carries the first identification information, and the third message indicates that association of the perception result with the third identification information is allowed, and associate the perception result with the third identification information;

[0288] The UE-related identification information includes first identification information and third identification information, and the relationship between the first identification information and the third identification information is: the same or a mapping relationship exists.

[0289] Step 3052: The first NF does not perform the first operation; wherein the third message includes authorization failure.

[0290] Optionally, in an embodiment of the present disclosure, if the first NF sends the first request to the UE after receiving the perception request, the first NF does not perceive the perception target.

[0291] Optional implementations of step 305, step 3051, and step 3052 can be found in step 203 of FIG. 2 and other related parts of the embodiment involved in FIG. 2, and will not be described in detail here.

[0292] Optionally, each step provided in the embodiment of the present disclosure may be implemented independently, and may be implemented in any combination and in a reversed order under the condition that the steps are not contradictory.

[0293] The communication method involved in the embodiments of the present disclosure may include at least one of the aforementioned steps and embodiments. For example, step 301 can be implemented as an independent embodiment, step 302 can be implemented as an independent embodiment, step 303 can be implemented as an independent embodiment, step 304 can be implemented as an independent embodiment, step 305 can be implemented as an independent embodiment, step 3051 can be implemented as an independent embodiment, and step 3052 can be implemented as an independent embodiment; the combination of step 301 and step 302 can be implemented as an independent embodiment, and the combination of step 301, step 302 and step 303 can be implemented as an independent embodiment. For example, the combination of step 301, step 302, step 303 and step 304 can be implemented as an independent embodiment, the combination of step 301, step 302, step 303, step 304 and step 305 can be implemented as an independent embodiment, the combination of step 301, step 302, step 303, step 304 and step 3051 can be implemented as an independent embodiment, and the combination of step 301, step 302, step 303, step 304 and step 3052 can be implemented as an independent embodiment, but is not limited thereto.

[0294] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 3 .

[0295] FIG4 is a third interactive schematic diagram of a communication method according to an embodiment of the present disclosure.

[0296] As shown in FIG4 , in some embodiments of the present disclosure, a first NF may send a first request to a third NF by interacting with the third NF, so as to indirectly detect, through the third NF, whether the first NF can be authorized to associate a perception result with identification information related to a user equipment UE. The method may include:

[0297] Step 401: The first NF sends a first request to the third NF; wherein the first request is used to request authorization information for performing a first operation; and the first operation includes associating the perception result with identification information related to the user equipment UE.

[0298] Optionally, in an embodiment of the present disclosure, the above method further includes:

[0299] The first NF determines that it has received the association authorization indication information or the perception request, and sends a first request to the third NF; wherein the association authorization indication information is used to indicate the association of the perception result with the identification information related to the UE; the perception request is used to request perception of the perception target; or

[0300] The first NF determines that it has received the perception result or the identification information related to the UE, and sends a first request to the third NF.

[0301] Optionally, in the embodiment of the present disclosure, the first NF determines that the association authorization indication information or the perception request is received, including at least one of the following:

[0302] Determining that the association authorization indication information or the perception request sent by the second NF is received;

[0303] Determining that association authorization indication information or perception request sent by the access network device is received;

[0304] Determine whether to receive association authorization indication information or perception request sent by the UE, or a client on the UE, or an application function.

[0305] Optionally, in the embodiment of the present disclosure, the first NF determines that the association authorization indication information or the perception request is received, including at least one of the following:

[0306] Determining that the association authorization indication information or the perception request sent by the second NF is received;

[0307] Determining that association authorization indication information or perception request sent by the access network device is received;

[0308] Determine whether to receive association authorization indication information or perception request sent by the UE, or a client on the UE, or an application function.

[0309] Optional implementations of step 401 may refer to step 201 in FIG. 2 and other related parts of the embodiment involved in FIG. 2 , and will not be described in detail here.

[0310] Step 402: The third NF sends a second message to the first NF; wherein the second message includes authorization information; or the second message indicates authorization failure.

[0311] Optional implementations of step 402 may refer to step 202 in FIG. 2 and other related parts of the embodiment involved in FIG. 2 , which will not be described in detail here.

[0312] Step 403: The first NF performs a fourth operation according to the second message.

[0313] Here, step 403 may include step 4031 or step 4032.

[0314] Step 4031: The first NF performs a first operation; wherein the second message includes authorization information.

[0315] Optionally, in the embodiment of the present disclosure, if the first NF sends the first request to the third NF after receiving the perception request, the first NF perceives the perception target; or, the first NF triggers the fourth NF to perceive the perception target.

[0316] Optionally, if the first NF can also obtain the perception result of perceiving the perception target (including but not limited to: the perception result of the first NF perceiving the perception target; or, the perception result of the fourth NF perceiving the perception target), associate the perception result with the identification information related to the user equipment UE.

[0317] Optionally, in the embodiment of the present disclosure, the first NF may further determine that the first request carries the first identification information, and the second message indicates that association of the perception result with the second identification information is allowed, then the first NF associates the perception information with the second identification information;

[0318] The UE-related identification information includes the first identification information and the second identification information, and the relationship between the first identification information and the second identification information is: the same or there is a mapping relationship.

[0319] In step 4032, the first NF does not perform the first operation; wherein the second message indicates authorization failure.

[0320] Optionally, in the embodiment of the present disclosure, if the first NF sends the first request to the third NF after receiving the perception request, the first NF does not perceive the perception target.

[0321] Optional implementations of step 403, step 4031, and step 4032 can be found in step 203 of FIG. 2 and other related parts of the embodiment involved in FIG. 2, and will not be described in detail here.

[0322] Optionally, each step provided in the embodiment of the present disclosure may be implemented independently, and may be implemented in any combination and in a reversed order under the condition that the steps are not contradictory.

[0323] The communication method involved in the embodiments of the present disclosure may include at least one of the aforementioned steps and embodiments. For example, step 401 can be implemented as an independent embodiment, step 402 can be implemented as an independent embodiment, step 403 can be implemented as an independent embodiment, step 4031 can be implemented as an independent embodiment, and step 4032 can be implemented as an independent embodiment; the combination of step 402 and step 403 can be implemented as an independent embodiment, the combination of step 401, step 402, and step 403 can be implemented as an independent embodiment, the combination of step 401, step 402, and step 4031 can be implemented as an independent embodiment, and the combination of step 401, step 402, and step 4032 can be implemented as an independent embodiment, but is not limited thereto.

[0324] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 4 .

[0325] FIG5 is a fourth interactive schematic diagram of a communication method according to an embodiment of the present disclosure.

[0326] As shown in FIG5 , in some embodiments of the present disclosure, the first NF may directly interact with the UE and send a first request to the UE to directly request the UE to authorize the first NF to associate the perception result with identification information related to the user equipment UE. The method may include:

[0327] Step 501: The first network function entity sends a first request to the UE; wherein the first request is used to request authorization information for performing a first operation; the first operation includes authorization information for associating an associated perception result with identification information related to the user equipment UE.

[0328] Optionally, in an embodiment of the present disclosure, the above method further includes:

[0329] The first NF determines that it has received the association authorization indication information or the perception request, and sends a first request to the UE; wherein the association authorization indication information is used to indicate the association of the perception result with the identification information related to the UE; the perception request is used to request perception of the perception target; or

[0330] The first NF determines that it has received the perception result or the identification information related to the UE, and sends a first request to the UE.

[0331] Optionally, in the embodiment of the present disclosure, the first network function entity receives the association authorization indication information or the perception request, including at least one of the following:

[0332] receiving association authorization indication information or perception request sent by the second network function entity;

[0333] Receiving association authorization indication information or perception request sent by the access network device;

[0334] Receive association authorization indication information or perception request sent by UE, or client on UE, or application function.

[0335] Optional implementations of step 501 may refer to step 201 in FIG. 2 and other related parts of the embodiment involved in FIG. 2 , which will not be described in detail here.

[0336] Step 502: The UE sends a third message to the first NF; the third message includes the authorization information; or the third message indicates authorization failure.

[0337] Optional implementations of step 502 may refer to step 202 in FIG. 2 and other related parts of the embodiment involved in FIG. 2 , and will not be described in detail here.

[0338] Step 503: The first network function entity performs a third operation based on the third message.

[0339] Among them, step 503 may include step 5031 or step 5032.

[0340] Step 5031: The first NF performs the first operation; wherein the third message includes authorization information.

[0341] Optionally, in an embodiment of the present disclosure, if the first NF sends the first request to the UE after receiving the perception request, the first NF perceives the perception target; or, the first NF triggers the fifth NF to perceive the perception target.

[0342] Optionally, if the first NF can also obtain the perception result of perceiving the perception target (including but not limited to: the perception result of the first NF perceiving the perception target; or, the perception result of the fifth NF perceiving the perception target), associate the perception result with the identification information related to the user equipment UE.

[0343] Optionally, in the embodiment of the present disclosure, the first NF may further determine that the first request carries the first identification information, and the third message indicates that association of the perception result with the third identification information is allowed, and then the first NF associates the perception information with the third identification information;

[0344] The UE-related identification information includes the first identification information and the third identification information, and the relationship between the first identification information and the third identification information is: the same or a mapping relationship exists.

[0345] Step 5032: The first NF does not perform the first operation; wherein the third message indicates authorization failure.

[0346] Optionally, in an embodiment of the present disclosure, if the first NF sends the first request to the UE after receiving the perception request, the first NF does not perceive the perception target.

[0347] Optional implementations of step 503, step 5031, and step 5032 can be found in step 203 of FIG. 2 and other related parts of the embodiment involved in FIG. 2, and will not be described in detail here.

[0348] Optionally, each step provided in the embodiment of the present disclosure may be implemented independently, and may be implemented in any combination and in a reversed order under the condition that the steps are not contradictory.

[0349] The communication method involved in the embodiments of the present disclosure may include at least one of the aforementioned steps and embodiments. For example, step 501 can be implemented as an independent embodiment, step 502 can be implemented as an independent embodiment, step 503 can be implemented as an independent embodiment, step 5031 can be implemented as an independent embodiment, and step 5032 can be implemented as an independent embodiment; the combination of step 502 and step 503 can be implemented as an independent embodiment, the combination of step 501, step 502 and step 503 can be implemented as an independent embodiment, the combination of step 501, step 502 and step 5031 can be implemented as an independent embodiment, and the combination of step 501, step 502 and step 5032 can be implemented as an independent embodiment, but the present invention is not limited thereto.

[0350] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 5 .

[0351] FIG6 is a fifth interactive schematic diagram of a communication method according to an embodiment of the present disclosure.

[0352] As shown in FIG6 , in some embodiments of the present disclosure, the UE may also directly send to the first NF information indicating whether the UE authorizes the first NF to associate the perception result with identification information related to the user equipment UE. The method may include:

[0353] Step 601: The UE sends a third message to the first NF; the third message includes authorization information for performing the first operation; or, the third message indicates that the authorization fails; the first operation includes associating the perception result with identification information related to the user equipment UE.

[0354] Optional implementations of step 601 may refer to step 202 in FIG. 2 and other related parts of the embodiment involved in FIG. 2 , which will not be described in detail here.

[0355] Step 602: The first network function entity performs a third operation based on the third message.

[0356] In which, step 602 may include step 6021 or step 6022.

[0357] Step 6021: The first NF performs the first operation; wherein the third message includes authorization information.

[0358] Optionally, in an embodiment of the present disclosure, if the first NF sends the first request to the UE after receiving the perception request, the first NF perceives the perception target; or, the first NF triggers the fifth NF to perceive the perception target.

[0359] Optionally, if the first NF can also obtain the perception result of perceiving the perception target (including but not limited to: the perception result of the first NF perceiving the perception target; or, the perception result of the fifth NF perceiving the perception target), associate the perception result with the identification information related to the user equipment UE.

[0360] Optionally, in the embodiment of the present disclosure, the first NF may further determine that the first request carries the first identification information, and the third message indicates that association of the perception result with the fourth identification information is allowed, and the first NF associates the perception information with the fourth identification information;

[0361] The UE-related identification information includes the first identification information and the fourth identification information, and the relationship between the first identification information and the fourth identification information is: the same or there is a mapping relationship.

[0362] Step 6022: The first NF does not perform the first operation; wherein the third message indicates authorization failure.

[0363] Optionally, in an embodiment of the present disclosure, if the first NF sends the first request to the UE after receiving the perception request, the first NF does not perceive the perception target.

[0364] Optional implementations of step 602, step 6021, and step 6022 can be found in step 203 of FIG. 2 and other related parts of the embodiment involved in FIG. 2, and will not be described in detail here.

[0365] Optionally, each step provided in the embodiment of the present disclosure may be implemented independently, and may be implemented in any combination and in a reversed order under the condition that the steps are not contradictory.

[0366] The communication method involved in the embodiments of the present disclosure may include at least one of the aforementioned steps and embodiments. For example, step 601 can be implemented as an independent embodiment, step 602 can be implemented as an independent embodiment, step 6021 can be implemented as an independent embodiment, and step 6022 can be implemented as an independent embodiment; the combination of step 601 and step 602 can be implemented as an independent embodiment, the combination of step 601 and step 6021 can be implemented as an independent embodiment, and the combination of step 601 and step 6022 can be implemented as an independent embodiment, but the present invention is not limited thereto.

[0367] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 6 .

[0368] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0369] In some embodiments, terms such as "moment", "time point", "time", and "time position" can be replaced with each other, and terms such as "duration", "period", "time window", "window", and "time" can be replaced with each other.

[0370] In some embodiments, terms such as wireless access scheme and waveform may be used interchangeably.

[0371] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, or first A, etc., but not limited to this.

[0372] In some embodiments, the determination or judgment can be performed by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values ​​(for example, comparison with a predetermined value), but is not limited thereto.

[0373] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data after receiving it; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the recipient to respond to the content sent.

[0374] FIG7 is a flowchart of a communication method according to an embodiment of the present disclosure.

[0375] As shown in FIG7 , the above method may be applied to a first network function entity, and the above method includes:

[0376] Step 701: A first network function entity sends a first request; wherein the first request is used to request authorization information for performing a first operation; and the first operation includes associating a perception result with identification information related to a user equipment UE.

[0377] Optionally, in the embodiment of the present disclosure, the above method further includes:

[0378] The first NF determines that the association authorization indication information or the perception request is received, and sends the first request; wherein the association authorization indication information is used to indicate the association of the perception result with the identification information related to the UE; the perception request is used to request perception of the perception target; or

[0379] The first NF determines that it has received the perception result or the identification information related to the UE, and sends the first request.

[0380] Optionally, in the embodiment of the present disclosure, the first network function entity determines that the association authorization indication information or the perception request is received, including at least one of the following:

[0381] Determining that association authorization indication information or perception request sent by the second network function entity is received;

[0382] Determining that association authorization indication information or perception request sent by the access network device is received;

[0383] Determine whether to receive association authorization indication information or perception request sent by the UE, or a client on the UE, or an application function.

[0384] Optional implementations of step 701 may refer to step 201 in FIG. 2 and other related parts of the embodiment involved in FIG. 2 , which will not be described in detail here.

[0385] Step 702: The first network function entity receives a message sent by a recipient of the first request.

[0386] Optionally, in the embodiment of the present disclosure, the recipient of the first request may include but is not limited to a third network function entity, a UE, etc.

[0387] Optionally, the message sent by the recipient of the first request may include: a first message, a second message, a third message, etc., wherein the first message instructs the first network function entity to send the first request to the UE; the second message includes an authorization message, or the second message indicates an authorization failure; and the third message includes an authorization message, or the third message indicates an authorization failure.

[0388] Optional implementations of step 702 may refer to step 202 in FIG. 2 and other related parts of the embodiment involved in FIG. 2 , and will not be described in detail here.

[0389] Step 703: The first network function entity performs a second operation according to the message sent by the recipient.

[0390] The second operation may include any one of the following:

[0391] If the message sent by the recipient includes the first message, and the first message instructs the first network function entity to send a first request to the UE, the first network function entity sends the first request to the UE;

[0392] If the message sent by the recipient includes the second message, and the second message includes the authorization message, the first network function entity associates the perception result with identification information related to the user equipment UE;

[0393] If the message sent by the recipient includes the second message, and the second message includes the authorization message, and the first network function entity sends the first request after receiving the perception request, the first network function entity perceives the perception target; or, the first network function entity triggers the fourth network function entity to perceive the perception target;

[0394] If the message sent by the recipient includes the second message, and the second message indicates that the authorization fails, the first network function entity does not associate the perception result with the identification information related to the user equipment UE;

[0395] If the message sent by the recipient includes the second message, and the second message indicates that the authorization fails, and the first network function entity sends the first request after receiving the perception request, the first network function entity does not perceive the perception target;

[0396] If the message sent by the recipient includes the third message, and the third message includes the authorization message, the first network function entity associates the perception result with identification information related to the user equipment UE;

[0397] If the message sent by the recipient includes the third message, and the third message includes the authorization message, and the first network function entity sends the first request after receiving the perception request, the first network function entity perceives the perception target; or, the first network function entity triggers the fifth network function entity to perceive the perception target;

[0398] If the message sent by the recipient includes the third message, and the third message indicates that the authorization fails, the first network function entity does not associate the perception result with the identification information related to the user equipment UE;

[0399] If the message sent by the recipient includes a third message, and the third message indicates authorization failure, and the first network function entity sends the first request after receiving the perception request, the first network function entity does not perceive the perception target.

[0400] Optionally, in an embodiment of the present disclosure, if the recipient includes a UE and a third network function entity, and the first network function entity receives a third message sent by the UE while receiving the first message or the second message sent by the third network function entity, the priority of the third message is higher than the priority of the first message, and the priority of the third message is higher than the priority of the second message;

[0401] The first message instructs the first network function entity to send a first request to the UE; the second message includes authorization information; or the second message indicates an authorization failure.

[0402] Optionally, in the embodiment of the present disclosure, the first NF may further determine that the first request carries the first identification information, and the second message indicates that association of the perception result with the second identification information is allowed, and associate the association perception result with the second identification information of the UE;

[0403] The UE-related identification information includes the first identification information and the second identification information, and the relationship between the first identification information and the second identification information is: the same or there is a mapping relationship.

[0404] Optionally, in the embodiment of the present disclosure, the first NF may further determine that the first request carries the first identification information, and the third message indicates that association of the perception result with the third identification information is allowed, and associate the perception result with the third identification information;

[0405] The UE-related identification information includes first identification information and third identification information, and the relationship between the first identification information and the third identification information is: the same or a mapping relationship exists.

[0406] Optional implementations of step 703 may refer to step 203 in FIG. 2 and other related parts of the embodiment involved in FIG. 2 , which will not be described in detail here.

[0407] Optionally, each step provided in the embodiment of the present disclosure may be implemented independently, and may be implemented in any combination and in a reversed order under the condition that the steps are not contradictory.

[0408] The communication method involved in the embodiments of the present disclosure may include at least one of the aforementioned steps and embodiments. For example, step 701 may be implemented as an independent embodiment, step 702 may be implemented as an independent embodiment, and step 703 may be implemented as an independent embodiment; the combination of step 701 and step 702 may be implemented as an independent embodiment, and the combination of step 701, step 702, and step 703 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0409] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 7 .

[0410] FIG8 is a second flow chart of a communication method according to an embodiment of the present disclosure.

[0411] As shown in FIG8 , the above method may be applied to a first network function entity, and the above method includes:

[0412] Step 801: The first network function entity sends a first request to the third NF; wherein the first request is used to request authorization information for performing a first operation; and the first operation includes associating the perception result with identification information related to the user equipment UE.

[0413] Optionally, in an embodiment of the present disclosure, the above method further includes:

[0414] The first NF determines that it has received the association authorization indication information or the perception request, and sends the first request to the third NF; wherein the association authorization indication information is used to indicate the association of the perception result with the identification information related to the UE; the perception request is used to request perception of the perception target; or

[0415] The first NF determines that it has received the perception result or the identification information related to the UE, and sends the first request to the third NF.

[0416] Optionally, in the embodiment of the present disclosure, the first network function entity determines that the association authorization indication information or the perception request is received, including at least one of the following:

[0417] Determining that association authorization indication information or perception request sent by the second network function entity is received;

[0418] Determining that association authorization indication information or perception request sent by the access network device is received;

[0419] Determine whether to receive association authorization indication information or perception request sent by the UE, or a client on the UE, or an application function.

[0420] Optional implementations of step 801 may refer to step 301 in FIG. 3 and other related parts of the embodiment involved in FIG. 3 , and will not be described in detail here.

[0421] Step 802: The first network function entity receives a first message sent by the third NF; wherein the first message instructs the first network function entity to send the first request to the UE.

[0422] Optional implementations of step 802 may refer to step 302 in FIG. 3 and other related parts of the embodiment involved in FIG. 3 , and will not be described in detail here.

[0423] Step 803: The first NF sends a first request to the UE.

[0424] Optional implementations of step 803 may refer to step 303 in FIG. 3 and other related parts of the embodiment involved in FIG. 3 , which will not be described in detail here.

[0425] Step 804: The first NF receives a third message sent by the UE;

[0426] The third message includes authorization information; or the third message indicates authorization failure.

[0427] Optional implementations of step 804 may refer to step 304 in FIG. 3 and other related parts of the embodiment involved in FIG. 3 , which will not be described in detail here.

[0428] Step 805: The first NF performs a third operation according to the third message.

[0429] Among them, step 805 may include step 8051 or step 8052.

[0430] Step 8051: The first NF performs the first operation; wherein the third message includes authorization information.

[0431] Optionally, in an embodiment of the present disclosure, if the first NF sends the first request to the UE after receiving the perception request, the first NF perceives the perception target; or, the first NF triggers the fifth NF to perceive the perception target.

[0432] Optionally, if the first NF can also obtain the perception result of perceiving the perception target (including but not limited to: the perception result of the first NF perceiving the perception target; or, the perception result of the fifth NF perceiving the perception target), associate the perception result with the identification information related to the user equipment UE.

[0433] Optionally, in the embodiment of the present disclosure, the first NF may further determine that the first request carries the first identification information, and the third message indicates that association of the perception result with the third identification information is allowed, and associate the perception result with the third identification information;

[0434] The UE-related identification information includes first identification information and third identification information, and the relationship between the first identification information and the third identification information is: the same or a mapping relationship exists.

[0435] Step 8052: The first NF does not perform the first operation; wherein the third message includes authorization failure.

[0436] Optionally, in an embodiment of the present disclosure, if the first NF sends the first request to the UE after receiving the perception request, the first NF does not perceive the perception target.

[0437] Optional implementations of step 805, step 8051, and step 8052 can be found in step 305, step 3051, step 3052 of FIG. 3 and other related parts of the embodiment involved in FIG. 3, which will not be repeated here.

[0438] Optionally, each step provided in the embodiment of the present disclosure may be implemented independently, and may be implemented in any combination and in a reversed order under the condition that the steps are not contradictory.

[0439] The communication method involved in the embodiments of the present disclosure may include at least one of the aforementioned steps and embodiments. For example, step 801 can be implemented as an independent embodiment, step 802 can be implemented as an independent embodiment, step 803 can be implemented as an independent embodiment, step 804 can be implemented as an independent embodiment, step 805 can be implemented as an independent embodiment, step 8051 can be implemented as an independent embodiment, and step 8052 can be implemented as an independent embodiment; the combination of step 801 and step 802 can be implemented as an independent embodiment, and the combination of step 801, step 802 and step 803 can be implemented as an independent embodiment. For example, the combination of step 801, step 802, step 803 and step 804 can be implemented as an independent embodiment, the combination of step 801, step 802, step 803, step 804 and step 805 can be implemented as an independent embodiment, the combination of step 801, step 802, step 803, step 804 and step 8051 can be implemented as an independent embodiment, and the combination of step 801, step 802, step 803, step 804 and step 8052 can be implemented as an independent embodiment, but is not limited to this.

[0440] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 8 .

[0441] FIG9 is a third interactive schematic diagram of a communication method according to an embodiment of the present disclosure.

[0442] As shown in FIG9 , the above method may be applied to a first network function entity, and the above method includes:

[0443] Step 901: The first NF sends a first request to the third NF; wherein the first request is used to request authorization information for performing a first operation; and the first operation includes associating the perception result with identification information related to the user equipment UE.

[0444] Optionally, in the embodiment of the present disclosure, the above method further includes:

[0445] The first NF determines that it has received the association authorization indication information or the perception request, and sends a first request to the third NF; wherein the association authorization indication information is used to indicate the association of the perception result with the identification information related to the UE; the perception request is used to request perception of the perception target; or

[0446] The first NF determines that it has received the perception result or the identification information related to the UE, and sends a first request to the third NF.

[0447] Optionally, in the embodiment of the present disclosure, the first NF determines that the association authorization indication information or the perception request is received, including at least one of the following:

[0448] Determining that the association authorization indication information or the perception request sent by the second NF is received;

[0449] Determining that association authorization indication information or perception request sent by the access network device is received;

[0450] Determine whether to receive association authorization indication information or perception request sent by the UE, or a client on the UE, or an application function.

[0451] Optionally, in the embodiment of the present disclosure, the first NF determines that the association authorization indication information or the perception request is received, including at least one of the following:

[0452] Determining that the association authorization indication information or the perception request sent by the second NF is received;

[0453] Determining that association authorization indication information or perception request sent by the access network device is received;

[0454] Determine whether to receive association authorization indication information or perception request sent by the UE, or a client on the UE, or an application function.

[0455] Optional implementations of step 901 may refer to step 401 in FIG. 4 and other related parts of the embodiment involved in FIG. 4 , and will not be described in detail here.

[0456] Step 902: The first NF receives a second message sent by the third NF; wherein the second message includes authorization information; or the second message indicates authorization failure.

[0457] Optional implementations of step 902 may refer to step 402 in FIG. 4 and other related parts of the embodiment involved in FIG. 4 , and will not be described in detail here.

[0458] Step 903: The first NF performs a fourth operation according to the second message.

[0459] Among them, step 903 may include step 9031 or step 9032.

[0460] Step 9031: The first NF performs a first operation; wherein the second message includes authorization information.

[0461] Optionally, in the embodiment of the present disclosure, if the first NF sends the first request to the third NF after receiving the perception request, the first NF perceives the perception target; or, the first NF triggers the fourth NF to perceive the perception target.

[0462] Optionally, if the first NF can also obtain the perception result of perceiving the perception target (including but not limited to: the perception result of the first NF perceiving the perception target; or, the perception result of the fourth NF perceiving the perception target), associate the perception result with the identification information related to the user equipment UE.

[0463] Optionally, in the embodiment of the present disclosure, the first NF may further determine that the first request carries the first identification information, and the second message indicates that association of the perception result with the second identification information is allowed, then the first NF associates the perception information with the second identification information;

[0464] The UE-related identification information includes the first identification information and the second identification information, and the relationship between the first identification information and the second identification information is: the same or there is a mapping relationship.

[0465] Step 9032: The first NF does not perform the first operation; wherein the second message indicates authorization failure.

[0466] Optionally, in the embodiment of the present disclosure, if the first NF sends the first request to the third NF after receiving the perception request, the first NF does not perceive the perception target.

[0467] Optional implementations of step 903, step 9031, and step 9032 can be found in step 403 of FIG. 4 and other related parts of the embodiment involved in FIG. 4, and will not be described in detail here.

[0468] Optionally, each step provided in the embodiment of the present disclosure may be implemented independently, and may be implemented in any combination and in a reversed order under the condition that the steps are not contradictory.

[0469] The communication method involved in the embodiments of the present disclosure may include at least one of the aforementioned steps and embodiments. For example, step 901 can be implemented as an independent embodiment, step 902 can be implemented as an independent embodiment, step 903 can be implemented as an independent embodiment, step 9031 can be implemented as an independent embodiment, and step 9032 can be implemented as an independent embodiment; the combination of step 902 and step 903 can be implemented as an independent embodiment, the combination of step 901, step 902, and step 903 can be implemented as an independent embodiment, the combination of step 901, step 902, and step 9031 can be implemented as an independent embodiment, and the combination of step 901, step 902, and step 9032 can be implemented as an independent embodiment, but is not limited thereto.

[0470] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 9 .

[0471] FIG10 is a fourth interactive schematic diagram of a communication method according to an embodiment of the present disclosure.

[0472] As shown in FIG10 , the above method may be applied to a first network function entity, and the above method includes:

[0473] Step 1001: A first network function entity sends a first request to a UE; wherein the first request is used to request authorization information for performing a first operation; and the first operation includes authorization information for associating an associated perception result with identification information related to a user equipment UE.

[0474] Optionally, in an embodiment of the present disclosure, the above method further includes:

[0475] The first NF determines that it has received the association authorization indication information or the perception request, and sends a first request to the UE; wherein the association authorization indication information is used to indicate the association of the perception result with the identification information related to the UE; the perception request is used to request perception of the perception target; or

[0476] The first NF determines that it has received the perception result or the identification information related to the UE, and sends a first request to the UE.

[0477] Optionally, in the embodiment of the present disclosure, the first network function entity receives the association authorization indication information or the perception request, including at least one of the following:

[0478] receiving association authorization indication information or perception request sent by the second network function entity;

[0479] Receiving association authorization indication information or perception request sent by the access network device;

[0480] Receive association authorization indication information or perception request sent by UE, or client on UE, or application function.

[0481] Optional implementations of step 1001 may refer to step 501 in FIG. 5 and other related parts of the embodiment involved in FIG. 5 , and will not be described in detail here.

[0482] Step 1002: The first NF receives a third message sent by the UE; the third message includes the authorization information; or the third message indicates authorization failure.

[0483] Optional implementations of step 1002 may refer to step 502 in FIG. 5 and other related parts of the embodiment involved in FIG. 5 , and will not be described in detail here.

[0484] Step 1003: The first network function entity performs a third operation according to the third message.

[0485] Among them, step 1003 may include step 10031 or step 10032.

[0486] Step 10031: The first NF performs the first operation; wherein the third message includes authorization information.

[0487] Optionally, in an embodiment of the present disclosure, if the first NF sends the first request to the UE after receiving the perception request, the first NF perceives the perception target; or, the first NF triggers the fifth NF to perceive the perception target.

[0488] Optionally, if the first NF can also obtain the perception result of perceiving the perception target (including but not limited to: the perception result of the first NF perceiving the perception target; or, the perception result of the fifth NF perceiving the perception target), associate the perception result with the identification information related to the user equipment UE.

[0489] Optionally, in the embodiment of the present disclosure, the first NF may further determine that the first request carries the first identification information, and the third message indicates that association of the perception result with the third identification information is allowed, and then the first NF associates the perception information with the third identification information;

[0490] The UE-related identification information includes the first identification information and the third identification information, and the relationship between the first identification information and the third identification information is: the same or a mapping relationship exists.

[0491] Step 10032: The first NF does not perform the first operation; wherein the third message indicates that the authorization fails.

[0492] Optionally, in an embodiment of the present disclosure, if the first NF sends the first request to the UE after receiving the perception request, the first NF does not perceive the perception target.

[0493] Optional implementations of step 1003, step 10031, and step 10032 can be found in step 503 of FIG. 5 and other related parts of the embodiment involved in FIG. 5 , and will not be described in detail here.

[0494] Optionally, each step provided in the embodiment of the present disclosure may be implemented independently, and may be implemented in any combination and in a reversed order under the condition that the steps are not contradictory.

[0495] The communication method involved in the embodiments of the present disclosure may include at least one of the aforementioned steps and embodiments. For example, step 1001 can be implemented as an independent embodiment, step 1002 can be implemented as an independent embodiment, step 1003 can be implemented as an independent embodiment, step 10031 can be implemented as an independent embodiment, and step 10032 can be implemented as an independent embodiment; the combination of step 1002 and step 1003 can be implemented as an independent embodiment, the combination of step 1001, step 1002, and step 1003 can be implemented as an independent embodiment, the combination of step 1001, step 1002, and step 10031 can be implemented as an independent embodiment, and the combination of step 1001, step 1002, and step 10032 can be implemented as an independent embodiment, but the present invention is not limited thereto.

[0496] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 10 .

[0497] FIG11 is a fifth interactive schematic diagram of a communication method according to an embodiment of the present disclosure.

[0498] As shown in FIG11 , the above method may be applied to a first network function entity, and the above method includes:

[0499] Step 1101, the first NF receives a third message sent by the UE; the third message includes authorization information for performing the first operation; or, the third message indicates that the authorization fails; the first operation includes associating the perception result with identification information related to the user equipment UE.

[0500] Optional implementations of step 1101 may refer to step 202 of FIG. 2 and other related parts of the embodiment involved in FIG. 2 , which will not be described in detail here.

[0501] Step 1102: The first NF performs a fifth operation based on the third message.

[0502] Among them, step 1102 may include step 11021 or step 11022.

[0503] Step 11021: The first NF performs the first operation; wherein the third message includes authorization information.

[0504] Optionally, in an embodiment of the present disclosure, if the first NF sends the first request to the UE after receiving the perception request, the first NF perceives the perception target; or, the first NF triggers the fifth NF to perceive the perception target.

[0505] Optionally, if the first NF can also obtain the perception result of perceiving the perception target (including but not limited to: the perception result of the first NF perceiving the perception target; or, the perception result of the fifth NF perceiving the perception target), associate the perception result with the identification information related to the user equipment UE.

[0506] Optionally, in the embodiment of the present disclosure, the first NF may further determine that the first request carries the first identification information, and the third message indicates that association of the perception result with the fourth identification information is allowed, and the first NF associates the perception information with the fourth identification information;

[0507] The UE-related identification information includes the first identification information and the fourth identification information, and the relationship between the first identification information and the fourth identification information is: the same or there is a mapping relationship.

[0508] Step 11022: The first NF does not perform the first operation; wherein the third message indicates authorization failure.

[0509] Optionally, in an embodiment of the present disclosure, if the first NF sends the first request to the UE after receiving the perception request, the first NF does not perceive the perception target.

[0510] Optional implementations of step 1102, step 11021, and step 11022 can be found in step 203 of FIG. 2 and other related parts of the embodiment involved in FIG. 2 , and will not be described in detail here.

[0511] Optionally, each step provided in the embodiment of the present disclosure may be implemented independently, and may be implemented in any combination and in a reversed order under the condition that the steps are not contradictory.

[0512] The communication method involved in the embodiments of the present disclosure may include at least one of the aforementioned steps and embodiments. For example, step 1101 may be implemented as an independent embodiment, step 1102 may be implemented as an independent embodiment, step 11021 may be implemented as an independent embodiment, and step 11022 may be implemented as an independent embodiment; the combination of step 1101 and step 1102 may be implemented as an independent embodiment, the combination of step 1101 and step 11021 may be implemented as an independent embodiment, and the combination of step 1101 and step 11022 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0513] In some embodiments, reference may be made to other optional implementations recorded before or after the description corresponding to FIG. 11 .

[0514] FIG12 is a sixth flowchart of a communication method according to an embodiment of the present disclosure.

[0515] As shown in FIG12 , the above method may be applied to a third network function entity, and the above method includes:

[0516] Step 1201: The third network function entity receives a first request sent by the first network function entity; wherein the first request is used to request authorization information for performing a first operation; the first operation includes associating a perception result with identification information related to a user equipment UE.

[0517] Optional implementations of step 1201 may refer to step 201 in FIG. 2 , step 301 in FIG. 3 , step 401 in FIG. 4 and other related parts in the embodiments involved in FIG. 2 , FIG. 3 and FIG. 4 , which will not be described in detail here.

[0518] Step 1202: The third network function entity sends a first message or a second message to the first network function entity.

[0519] The first message instructs the first network function entity to send a first request to the UE;

[0520] The second message includes an authorization message, or the second message indicates that the authorization failed.

[0521] Optional implementations of step 1202 may refer to step 202 in FIG. 2 , step 302 in FIG. 3 , step 402 in FIG. 4 and other related parts in the embodiments involved in FIG. 2 , FIG. 3 and FIG. 4 , which will not be described in detail here.

[0522] Optionally, each step provided in the embodiment of the present disclosure may be implemented independently, and may be implemented in any combination and in a reversed order under the condition that the steps are not contradictory.

[0523] The communication method involved in the embodiments of the present disclosure may include at least one of the aforementioned steps and embodiments. For example, step 1201 may be implemented as an independent embodiment, and step 1202 may be implemented as an independent embodiment; the combination of step 1201 and step 1202 may be implemented as an independent embodiment, but is not limited thereto.

[0524] In some embodiments, reference may be made to other optional implementations recorded before or after the description corresponding to FIG. 12 .

[0525] FIG13 is a seventh flowchart of a communication method according to an embodiment of the present disclosure.

[0526] As shown in FIG13 , the above method may be applied to a UE, and the above method includes:

[0527] Step 1301: The UE sends a third message to the first network function entity; the third message includes authorization information for performing the first operation; or, the third message indicates authorization failure; the first operation includes associating the perception result with identification information related to the UE.

[0528] In this embodiment, the UE may proactively send to the first network function entity information indicating whether the UE authorizes the first NF to associate the perception result with identification information related to the user equipment UE.

[0529] Optional implementations of step 1301 may refer to step 601 in FIG. 6 and other related parts of the embodiment involved in FIG. 6 , which will not be described in detail here.

[0530] In some embodiments, reference may be made to other optional implementations recorded before or after the description corresponding to FIG. 13 .

[0531] FIG14 is an eighth flowchart of a communication method according to an embodiment of the present disclosure.

[0532] As shown in FIG14 , the above method may be applied to a UE, and the above method includes:

[0533] Step 1401: The UE receives a first request sent by a first network function entity; wherein the first request is used to request authorization information for performing a first operation, and the first operation includes associating a perception result with identification information related to the user equipment UE.

[0534] Optional implementations of step 1401 may refer to step 501 in FIG. 5 and other related parts of the embodiment involved in FIG. 5 , and will not be described in detail here.

[0535] Step 1402: The UE sends a third message to the first network function entity; the third message includes the authorization information; or the third message indicates authorization failure.

[0536] Optional implementations of step 1402 may refer to step 502 in FIG. 5 and other related parts of the embodiment involved in FIG. 5 , and will not be described in detail here.

[0537] Optionally, each step provided in the embodiment of the present disclosure may be implemented independently, and may be implemented in any combination and in a reversed order under the condition that the steps are not contradictory.

[0538] The communication method involved in the embodiments of the present disclosure may include at least one of the aforementioned steps and embodiments. For example, step 1401 may be implemented as an independent embodiment, and step 1402 may be implemented as an independent embodiment; the combination of step 1401 and step 1402 may be implemented as an independent embodiment, but is not limited thereto.

[0539] In some embodiments, reference may be made to other optional implementations recorded before or after the description corresponding to FIG. 14 .

[0540] With respect to the foregoing record, in the communication method provided in the embodiment of the present disclosure, the first network function entity can obtain authorization information for associating the perception result with the identification information related to the user equipment UE, so as to associate the UE-related identification information with the perception result. Referring to FIG. 15 below, the method is specifically described:

[0541] Optionally, the NF may be an NWDAF, a perception module, an LMF, a GMLC, a Sensing Function, etc. And the local policy in the NF may indicate that when the NF receives the perception result and the identification information related to the UE, an authorization operation of associating the perception result with the identification information related to the user equipment UE (hereinafter referred to as association authorization) is triggered.

[0542] Step 1: Trigger the first NF to initiate association authorization.

[0543] Optionally, the factors triggering the first NF to initiate association authorization may include at least one of the following:

[0544] (1) Another network function entity (the second NF) or an access network device (e.g., NG-RAN) triggers the first NF to initiate association authorization. Specifically, the other network function entity or access network device (e.g., NG-RAN) may trigger the first NF to initiate association authorization by sending an association authorization indication, a perception result, or UE-related identification information to the NF.

[0545] (2) A third party (such as a terminal, a client on the terminal, or an AF) can trigger the first NF to perform association authorization by sending an association authorization indication or a perception request to the first NF.

[0546] Step 2: The first NF interacts with the third NF to determine whether the UE-related identification information (e.g., GPSI, SUPI, SUCI, application layer ID, MSISDN, and other terminal-related IDs) can be associated with the sensing result. Specifically, the first NF may send the UE-related identification information to the third NF to obtain corresponding authorization information.

[0547] Step 3: The first NF may interact with the UE to obtain authorization information or perception results. The UE may determine the authorization information based on the privacy policy on the terminal side.

[0548] Optionally, the privacy policy on the terminal side may be stored in a core network device, and the UE obtains the privacy policy through interaction with the core network device, and uses the obtained privacy policy as the privacy policy on the terminal side.

[0549] Optionally, the NF may perform any one of steps 2 and 3.

[0550] Optionally, step 3 may be triggered during the execution of step 2. For example, when the authorization information sent by the third NF indicates that the authorization information needs to be obtained by interacting with the UE, the first NF may execute step 3.

[0551] Optionally, the authorization information / perception result sent by the UE may overwrite the authorization information / result provided by the third NF, that is, the priority of the authorization information / perception result sent by the UE is higher than the priority of the authorization information / result provided by the third NF.

[0552] Step 4: After the first NF obtains the authorization information or the perception result, it executes step 4a or 4b.

[0553] Step 4a, if the authorization information / authorization result indicates that the UE-related identification information is allowed to be associated with the perception result, the first NF initiates the process of associating the perception result with the identification information related to the user equipment UE or starts the perception process of the perception target, or the first NF can also trigger other network function entities to perform the process of associating the perception result with the identification information related to the user equipment UE or the perception process of the perception target.

[0554] In addition, the authorization information / authorization result may further indicate whether the designated identification information of the UE (eg, GPSI, SUPI, application layer ID) can be associated with the perception result.

[0555] Step 4b, if the authorization information / authorization result indicates that the UE-related identification information is not allowed to be associated with the perception result, the first NF does not associate (for example, terminates) the process of associating the perception result with the identification information related to the user equipment UE, or does not (for example, terminates) the perception process of the perception target.

[0556] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0557] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0558] In the embodiment of the present disclosure, the processor is a circuit with signal processing capability. In one implementation, the processor can be a circuit with instruction reading and execution capability, 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 relationship of the hardware circuit, and the logical relationship of the above hardware circuit is fixed or reconfigurable, such as a hardware circuit implemented by a processor as 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 implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be 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), a deep learning processing unit (DPU), etc.

[0559] FIG16 is a schematic diagram of the structure of a first network function entity proposed in an embodiment of the present disclosure. As shown in FIG16 , the first network function entity 1600 may be a first network function entity, and at least includes: a sending module 1601.

[0560] In some embodiments, the sending module 1601 is used to send a first request; wherein, the first request is used to request authorization information for performing a first operation; the first operation includes associating the perception result with identification information related to the user equipment UE.

[0561] Optionally, the above-mentioned sending module 1601 is used to execute at least one of the sending and receiving steps performed by the first network function entity 1012 in any of the above methods (for example, step 201, step 301, step 303, step 3041, step 401, step 501, step 701, step 702, step 801, step 802, step 803, step 804, step 901, step 902, step 1001, step 1002, step 1101, but not limited to this), which is not repeated here.

[0562] Optionally, the first network function entity 1600 may further include a processing module.

[0563] Optionally, the above-mentioned processing module is used to execute at least one of the communication steps performed by the first network function entity 1011 in any of the above methods (for example, step 203, step 305, step 3051, step 3052, step 403, step 4031, step 4032, step 503, step 5031, step 5032, step 602, step 6021, step 6022, step 703, step 805, step 8051, step 8052, step 903, step 9031, step 9032, step 1003, step 10031, step 10032, step 1102, step 11021, step 11022, but not limited to these), which are not repeated here.

[0564] FIG17 is a schematic diagram of the structure of a third network function entity proposed in an embodiment of the present disclosure. As shown in FIG17 , the third network function entity 1700 may include: a receiving module 1701 .

[0565] In some embodiments, the above-mentioned receiving module 1701 is used to receive a first request; wherein, the first request is used to request authorization information for performing a first operation; the first operation includes associating the perception result with identification information related to the user equipment UE.

[0566] Optionally, the above-mentioned receiving module 1701 is used to execute at least one of the sending and receiving steps (for example, step 302, step 402, step 1201, step 1202, but not limited to these) performed by the third network function entity 1012 in any of the above methods, which will not be repeated here.

[0567] FIG18 is a schematic diagram of the structure of a user equipment proposed in an embodiment of the present disclosure. As shown in FIG18 , the user equipment 1800 may include: a sending module 1801 .

[0568] In some embodiments, the above-mentioned sending module 1801 is used to send a third message; the third message includes authorization information for performing the first operation; or, the third message indicates that the authorization failed; the first operation includes associating the perception result with identification information related to the user equipment UE.

[0569] Optionally, the sending module 1801 is used to execute at least one of the sending and receiving steps (such as step 502, step 601, step 1301, step 1401, but not limited thereto) performed by the user equipment 102 in any of the above methods, which will not be repeated here.

[0570] Figure 19 is a schematic diagram of the structure of a terminal 1900 (e.g., user equipment) proposed in an embodiment of the present disclosure. Terminal 1900 can be a chip, chip system, or processor that supports a network device implementing any of the above methods, or a chip, chip system, or processor that supports a terminal implementing any of the above methods. Terminal 1900 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0571] As shown in Figure 19, terminal 1900 includes one or more processors 1901. Processor 1901 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control communication devices (such as base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Terminal 1900 is used to perform any of the above methods.

[0572] In some embodiments, the terminal 1900 further includes one or more memories 1902 for storing instructions. Optionally, all or part of the memories 1902 may be located outside the terminal 1900.

[0573] In some embodiments, the terminal 1900 further includes one or more transceivers 1904. When the terminal 1900 includes one or more transceivers 1904, the transceiver 1904 performs the communication steps such as sending and / or receiving in the above method (for example, step 201, step 301, step 302, step 303, step 3041, step 401, step 402, step 501, step 502, step 601, step 701, step 702, step 801, step 802, step 803, step 804, step 901, step 902, step 1001, step 1002, step 1101, step 1201, step 1202, step 1301, step 1401, but not limited to) In the embodiment of the present invention, the processor 1901 executes at least one of the other steps (for example, step 203, step 305, step 3051, step 3052, step 403, step 4031, step 4032, step 503, step 5031, step 5032, step 602, step 6021, step 6022, step 703, step 805, step 8051, step 8052, step 903, step 9031, step 9032, step 1003, step 10031, step 10032, step 1102, step 11021, step 11022, but not limited to these).

[0574] In some embodiments, a transceiver may include a receiver and / or a transmitter. The receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0575] In some embodiments, terminal 1900 may include one or more interface circuits 1903. Optionally, interface circuit 1903 is connected to memory 1902. Interface circuit 1903 may be configured to receive signals from memory 1902 or other devices, and may be configured to send signals to memory 1902 or other devices. For example, interface circuit 1903 may read instructions stored in memory 1902 and send the instructions to processor 1901.

[0576] The terminal 1900 described in the above embodiment may be a communication device such as a user device, but the scope of the terminal 1900 described in the present disclosure is not limited thereto, and the structure of the terminal 1900 may not be limited by FIG. 19 . The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: (1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0577] FIG20 is a schematic diagram of the structure of a chip 2000 according to an embodiment of the present disclosure. In the case where the terminal 1900 may be a chip or a chip system, reference may be made to the schematic diagram of the structure of the chip 2000 shown in FIG20 , but the present disclosure is not limited thereto.

[0578] The chip 2000 includes one or more processors 2001 , and the chip 2000 is configured to execute any of the above methods.

[0579] In some embodiments, chip 2000 further includes one or more 2003. Optionally, interface circuit 2003 is connected to memory 2002. Interface circuit 2003 can be used to receive signals from memory 2002 or other devices, and can be used to send signals to memory 2002 or other devices. For example, interface circuit 2003 can read instructions stored in memory 2002 and send the instructions to processor 2001.

[0580] In some embodiments, the interface circuit 2003 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step 201, step 301, step 302, step 303, step 3041, step 401, step 402, step 501, step 502, step 601, step 701, step 702, step 801, step 802, step 803, step 804, step 901, step 902, step 1001, step 1002, step 1101, step 1201, step 1202, step 1301, step 1401, but not limited thereto). The processor 2001 executes at least one of the other steps (for example, step 203, step 305, step 3051, step 3052, step 403, step 4031, step 4032, step 503, step 5031, step 5032, step 602, step 6021, step 6022, step 703, step 805, step 8051, step 8052, step 903, step 9031, step 9032, step 1003, step 10031, step 10032, step 1102, step 11021, step 11022, but not limited to these).

[0581] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.

[0582] In some embodiments, the chip 2000 further includes one or more memories 2002 for storing instructions. Alternatively, all or part of the memory 2002 may be external to the chip 2000.

[0583] The present disclosure also provides a storage medium having instructions stored thereon. When the instructions are executed on the terminal 1900, the terminal 1900 executes 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 is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a transient storage medium.

[0584] The present disclosure also provides a program product, which, when executed by the terminal 1900, enables the terminal 1900 to perform any of the above methods. Optionally, the program product is a computer program product.

[0585] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Claims

1. A communication method, performed by a first network function entity, characterized in that: The method comprises: Sending a first request; wherein the first request is used to request authorization information for performing a first operation; the first operation includes associating the perception result with identification information related to the user equipment UE.

2. The communication method according to claim 1, wherein: The method further comprises: Determine that association authorization indication information or a perception request is received, and send the first request; wherein the association authorization indication information is used to indicate the association of the perception result with identification information related to the UE; the perception request is used to request perception of the perception target; or Determine that the perception result or the identification information related to the UE is received, and send the first request.

3. The communication method according to claim 2, wherein: The determining that the association authorization indication information or the perception request is received includes at least one of the following: Determining that the association authorization indication information or the perception request sent by the second network function entity is received; Determining that the association authorization indication information or the perception request sent by the access network device is received; Determine whether the association authorization indication information or the perception request sent by the UE, or a client on the UE, or an application function is received.

4. The communication method according to claim 1, wherein: The sending of the first request includes: Send a first request to the third network function entity.

5. The communication method according to claim 4, wherein: The method further comprises: A first message sent by the third network function entity is received; the first message instructs the first network function entity to send the first request to the UE. The communication method according to claim 5 , wherein: The method further comprises: A first request is sent to the UE.

7. The communication method according to claim 4, wherein: The method further comprises: receiving a second message sent by the third network function entity; The second message includes the authorization information; or the second message indicates that the authorization failed.

8. The communication method according to claim 7, wherein: In a case where the second message includes the authorization information, the method further includes: The first operation is performed.

9. The communication method according to claim 8, wherein: The first network function entity sends the first request after receiving the perception request, and the method further includes: sensing the sensing target; or Triggering the fourth network function entity to perceive the perception target.

10. The communication method according to claim 8 or 9, characterized in that: The method further comprises: Determining that the first request carries first identification information, and the second message indicates that associating the perception result with the second identification information is allowed, and associating the perception result with the second identification information; The UE-related identification information includes the first identification information and the second identification information, and the relationship between the first identification information and the second identification information is: the same or there is a mapping relationship.

11. The communication method according to claim 7, wherein: In a case where the second message indicates that the authorization fails, the method further includes: The first operation is not performed.

12. The communication method according to claim 11, wherein: The method further comprises: If the first network function entity sends the first request after receiving the perception request, it does not perceive the perception target Mark.

13. The communication method according to claim 3 or 6, characterized in that: The method further comprises: receiving a third message sent by the UE; The third message includes the authorization information; or the third message indicates authorization failure.

14. The communication method according to claim 13, wherein: In a case where the third message includes the authorization information, the method further includes: The first operation is performed.

15. The communication method according to claim 14, wherein: The first network function entity sends the first request after receiving the perception request, and the method further includes: sensing the sensing target; or Triggering the fifth network function entity to perceive the perception target.

16. The communication method according to claim 14, wherein: The method further comprises: Determining that the first request carries first identification information, and the third message indicates that associating the perception result with the second identification information is allowed, and associating the second identification information of the UE with the perception result; The UE-related identification information includes the first identification information and the second identification information, and the relationship between the first identification information and the second identification information is: the same or there is a mapping relationship.

17. The communication method according to claim 13, wherein: The third message indicates that the authorization failed, and the method further includes: The first operation is not performed.

18. The communication method according to claim 17, wherein: The first network function entity sends the first request after receiving the perception request, and the method further includes: The perception target is not perceived.

19. The communication method according to claim 13, wherein: if the first network function entity further receives a first message or a second message sent by a third network function entity, the priority of the third message is higher than the priority of the first message, and the priority of the third message is higher than the priority of the second message; The first message indicates that the first network function entity sends the first request to the UE; the second message includes the authorization information; or the second message indicates that the authorization fails.

20. A communication method, performed by a third network function entity, characterized in that: The method comprises: A first request sent by a first network function entity is received; wherein the first request is used to request authorization information for performing a first operation; and the first operation includes associating a perception result with identification information related to a user equipment UE.

21. The communication method according to claim 20, wherein: The method further comprises: A first message is sent to the first network function entity; the first message instructs the first network function entity to send the first request to the UE.

22. The communication method according to claim 20, wherein: The method further comprises: Sending a second message to the first network function entity; The second message includes the authorization information; or the second message indicates that the authorization failed.

23. A communication method, performed by a user equipment UE, characterized in that: The method comprises: Sending a third message to the first network function entity; The third message includes authorization information for performing the first operation; or the third message indicates authorization failure; and the first operation includes identification information related to the associated perception result and the user equipment UE.

24. The communication method according to claim 23, wherein: The method further comprises: Receive a first request sent by the first network function entity; wherein the first request is used to request to obtain the authorization information.

25. A network function entity, characterized in that: include: A sending module, configured to send a first request; wherein the first request is used to request authorization information for performing a first operation; The first operation includes associating the sensing result with identification information related to the user equipment UE.

26. A network function entity, characterized in that: include: A receiving module, configured to receive a first request; wherein the first request is used to request authorization information for performing a first operation; The first operation includes associating the sensing result with identification information related to the user equipment UE.

27. A user equipment UE, characterized in that The user equipment includes: A sending module, configured to send a third message to the first network function entity; The third message includes authorization information for performing the first operation; or the third message indicates authorization failure; and the first operation includes associating the perception result with identification information related to the UE.

28. A communication device comprising: one or more processors; The communication device is used to execute the communication method according to any one of claims 1 to 19.

29. A communication device comprising: one or more processors; The communication device is used to execute the communication method according to any one of claims 20 to 22.

30. A communication device comprising: one or more processors; Wherein, the communication device is used to execute the communication method described in claim 23 or claim 24.

31. A communication system, characterized in that: The invention comprises a first network function entity, a third network function entity and a user equipment; wherein, the first network function entity is configured to implement the communication method according to any one of claims 1 to 19, the third network function entity is configured to implement the communication method according to any one of claims 20 or 22, and the user equipment is configured to implement the communication method according to claim 23 or claim 24.

32. A storage medium storing instructions, characterized in that: When the instruction is executed on a communication device, the communication device executes the communication method according to any one of claims 1 to 19, or executes the communication method according to any one of claims 20 or 22, or executes the communication method according to claim 23 or claim 24.

33. A program product, characterized in that When the program product is executed by a communication device, the communication device executes the communication method according to any one of claims 1 to 19, or the communication method according to any one of claims 20 or 22, or the communication method according to claim 23 or claim 24.

Images