Communication processing method, first entity, second entity, third entity

Abstract

The present disclosure relates to a communication processing method, a first entity, a second entity, and a third entity. The method comprises: a first entity sending a first message to a second entity, wherein the first message is used for providing related information of a specific private Internet of Things (PIN); and receiving a fifth message sent by a second entity, wherein the fifth message is used for indicating an authorization result, and the authorization result comprises authorization success or authorization failure. Thus, the communication efficiency is effectively improved.

Description

Communication processing method, first entity, second entity, third entity Technical Field

[0001] The present disclosure relates to the field of communication technologies, and in particular to a communication processing method, a first entity, a second entity, and a third entity. Background Art

[0002] In wireless communications, application functions in the communication network supported by the communication system are configured through functional entities in the core network.

[0003] Summary of the Invention

[0004] The embodiments of the present disclosure provide a communication processing method, a first entity, a second entity, and a third entity, thereby improving communication efficiency.

[0005] According to a first aspect of an embodiment of the present disclosure, a communication processing method is provided, the method comprising:

[0006] Sending a first message to a second entity, wherein the first message is used to provide information related to a specific private Internet of Things PIN;

[0007] A fifth message sent by the second entity is received, wherein the fifth message is used to indicate an authorization result, wherein the authorization result includes authorization passed or authorization failed.

[0008] According to a second aspect of an embodiment of the present disclosure, a communication processing method is proposed, the method comprising:

[0009] receiving a first message sent by a first entity, and generating a second message according to the first message;

[0010] A fifth message is sent to the first entity, wherein the fifth message is used to indicate the authorization result, wherein the authorization result includes authorization passed or authorization failed.

[0011] According to a third aspect of an embodiment of the present disclosure, a communication processing method is provided, the method comprising:

[0012] receiving a second message or a sixth message sent by a second entity;

[0013] performing authorization based on relevant information in the second message or the sixth message;

[0014] Sending a third message or a seventh message to the second entity, wherein the third message or the seventh message is used to indicate the authorization result.

[0015] According to a fourth aspect of an embodiment of the present disclosure, a communication processing method is provided, the method comprising:

[0016] The first entity sends a first message to the second entity, wherein the first message is used to provide relevant information about a specific private Internet of Things PIN;

[0017] The second entity receives the first message sent by the first entity, generates a second message according to the first message, and sends the second message to the third entity;

[0018] The third entity receives the second message sent by the second entity, and performs authorization based on relevant information in the second message;

[0019] The third entity sends a third message to the second entity, wherein the third message is used to indicate the authorization result;

[0020] The second entity receives the third message sent by the third entity, and sends a fifth message to the first entity, wherein the fifth message is used to indicate the authorization result, wherein the authorization result includes authorization passed or authorization failed;

[0021] The first entity receives a fifth message sent by the second entity.

[0022] According to a fifth aspect of an embodiment of the present disclosure, a first entity is provided, wherein the apparatus includes:

[0023] a transceiver module, configured to send a first message to a second entity, wherein the first message is used to provide relevant information about a specific private IoT PIN;

[0024] The transceiver module is used to receive a fifth message sent by the second entity, wherein the fifth message is used to indicate an authorization result, wherein the authorization result includes authorization passed or authorization failed.

[0025] According to a sixth aspect of the embodiments of the present disclosure, two entities are proposed, and the apparatus includes:

[0026] a transceiver module, configured to receive a first message sent by a first entity, and generate a second message according to the first message;

[0027] The transceiver module is used to send a fifth message to the first entity, wherein the fifth message is used to indicate the authorization result, wherein the authorization result includes authorization passed or authorization failed.

[0028] According to a seventh aspect of an embodiment of the present disclosure, a third entity is provided, wherein the apparatus includes:

[0029] a transceiver module, configured to receive a second message or a sixth message sent by a second entity;

[0030] a processing module, configured to perform authorization based on relevant information in the second message or the sixth message;

[0031] The transceiver module is used to send a third message or a seventh message to the second entity, wherein the third message or the seventh message is used to indicate an authorization result.

[0032] According to an eighth aspect of the embodiments of the present disclosure, a first entity is provided, including:

[0033] one or more processors;

[0034] The first entity is configured to execute any one of the methods described in the first aspect.

[0035] According to a ninth aspect of the embodiments of the present disclosure, a second entity is proposed, including:

[0036] one or more processors;

[0037] The second entity is used to execute any one of the methods in the second aspect.

[0038] According to a tenth aspect of the embodiments of the present disclosure, a third entity is proposed, including:

[0039] one or more processors;

[0040] The third entity is used to execute any one of the methods in the third aspect.

[0041] According to the eleventh aspect of an embodiment of the present disclosure, a communication system is proposed, comprising a first entity, a second entity, and a third entity, wherein the first entity is configured to implement the method described in any one of the first aspects, the second entity is configured to implement the method described in any one of the second aspects, and the third entity is configured to implement the method described in any one of the third aspects.

[0042] According to the twelfth aspect of an embodiment of the present disclosure, a storage medium is proposed, which stores instructions. When the instructions are executed on a communication device, the communication device executes a method as described in any one of the first aspect, the second aspect, or the third aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] 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.

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

[0045] FIG2 is an exemplary interaction diagram of a communication processing method provided according to an embodiment of the present disclosure.

[0046] FIG3A is a flow chart illustrating a communication processing method according to an embodiment of the present disclosure.

[0047] FIG4A is a flow chart illustrating a communication processing method according to an embodiment of the present disclosure.

[0048] FIG4B is a flow chart illustrating a communication processing method according to an embodiment of the present disclosure.

[0049] FIG4C is a flow chart illustrating a communication processing method according to an embodiment of the present disclosure.

[0050] FIG4D is a flow chart illustrating a communication processing method according to an embodiment of the present disclosure.

[0051] FIG5A is an interactive schematic diagram illustrating a communication processing method according to an embodiment of the present disclosure.

[0052] FIG6 is a schematic diagram showing a communication processing method according to an embodiment of the present disclosure.

[0053] FIG7A is a schematic structural diagram of the first entity proposed in an embodiment of the present disclosure.

[0054] FIG7B is a schematic structural diagram of the second entity proposed in an embodiment of the present disclosure.

[0055] FIG7C is a schematic structural diagram of the third entity proposed in an embodiment of the present disclosure.

[0056] FIG8A is a schematic structural diagram of a communication device 8100 proposed in an embodiment of the present disclosure.

[0057] FIG8B is a schematic structural diagram of a chip 8200 according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0058] The embodiments of the present disclosure provide a communication processing method, a first entity, a second entity, a third entity, and a core network device.

[0059] In a first aspect, an embodiment of the present disclosure provides a communication processing method, the method comprising:

[0060] Sending a first message to a second entity, wherein the first message is used to provide information related to a specific private IoT PIN;

[0061] A fifth message sent by the second entity is received, where the fifth message is used to indicate an authorization result, where the authorization result includes authorization passed or authorization failed.

[0062] In the above embodiment, the first message provides relevant information of a specific private IoT PIN and authorizes it, so that the 5GS limits the AF to the granularity of a specific PIN, preventing the AF from configuring information for a PIN ID that is not managed by itself and affecting the user experience, thereby improving the quality of communication.

[0063] In conjunction with some embodiments of the first aspect, in some embodiments, the first message includes at least one of the following:

[0064] Application capability AF identifier;

[0065] Application function AF service identifier;

[0066] General Public User Identifier GPSI;

[0067] PIN identifier.

[0068] In a second aspect, an embodiment of the present disclosure provides a communication processing method, the method comprising:

[0069] receiving a first message sent by a first entity, and generating a second message according to the first message;

[0070] A fifth message is sent to the first entity, where the fifth message is used to indicate an authorization result, where the authorization result includes authorization passed or authorization failed.

[0071] In the above embodiment, the first message provides relevant information of a specific private IoT PIN and authorizes it, so that the 5GS limits the AF to the granularity of a specific PIN, preventing the AF from configuring information for a PIN ID that is not managed by itself and affecting the user experience, thereby improving the quality of communication.

[0072] In conjunction with some embodiments of the second aspect, in some embodiments, the first message includes at least one of the following:

[0073] Application capability AF identifier;

[0074] AF service identifier;

[0075] General Public User Identifier GPSI;

[0076] PIN identifier.

[0077] In conjunction with some embodiments of the second aspect, in some embodiments, the second message includes at least one of the following specific PIN related information:

[0078] AF identifier;

[0079] Single network slice selection assistance information S-NSSAI;

[0080] Data network name DNN;

[0081] Application function AF service identifier;

[0082] General Public User Identifier GPSI;

[0083] PIN identifier.

[0084] In conjunction with some embodiments of the second aspect, in some embodiments, generating the second message according to the first message includes:

[0085] Determine the corresponding S-NSSAI and / or DNN based on the AF service identifier in the first message.

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

[0087] sending a second message to a third entity;

[0088] A third message sent by a third entity is received, where the third message is used to indicate an authorization result.

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

[0090] In response to the third message indicating that the authorization is passed, a fourth message is sent to the fourth network element.

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

[0092] Authorization is performed according to the second message.

[0093] In conjunction with some embodiments of the second aspect, in some embodiments, performing authorization according to the second message includes:

[0094] Obtain a locally stored mapping relationship table, where the mapping relationship table includes a mapping relationship between the S-NSSAI and / or DNN and the PIN identifier.

[0095] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes at least one of the following:

[0096] Querying a target PIN identifier that has a mapping relationship with the S-NSSAI and / or DNN in the second message based on a locally stored mapping relationship table; or,

[0097] The target S-NSSAI and / or target DNN that has a mapping relationship with the PIN identifier in the second message is queried based on the locally stored mapping relationship table.

[0098] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes any one of the following:

[0099] If the target PIN identifier is consistent with the PIN identifier in the second message, determining that a mapping relationship exists between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message;

[0100] If the target S-NSSAI and / or target DNN are consistent with the S-NSSAI and / or DNN in the second message, determining that a mapping relationship exists between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message;

[0101] Otherwise, it is determined that there is no mapping relationship between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message.

[0102] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes any one of the following:

[0103] If a mapping relationship exists between the S-NSSAI and / or the DNN in the second message and the PIN identifier in the second message, generating a sixth message and sending the sixth message to the third entity;

[0104] If there is no mapping relationship between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message, an authorization result of failed authorization is generated, wherein the fifth message carries the authorization result of failed authorization.

[0105] In conjunction with some embodiments of the second aspect, in some embodiments, the sixth message includes at least one of the following:

[0106] AF identifier;

[0107] Single network slice selection assistance information S-NSSAI;

[0108] Data network name DNN;

[0109] Application function AF service identifier;

[0110] General Public User Identifier GPSI.

[0111] According to a third aspect of an embodiment of the present disclosure, a communication processing method is proposed, the method comprising:

[0112] receiving a second message or a sixth message sent by a second entity;

[0113] performing authorization based on relevant information in the second message or the sixth message;

[0114] Sending the third message or the seventh message to the second entity, wherein the third message or the seventh message is used to indicate the authorization result.

[0115] In the above embodiment, the first message provides relevant information of a specific private IoT PIN and authorizes it, so that the 5GS limits the AF to the granularity of a specific PIN, preventing the AF from configuring information for a PIN ID that is not managed by itself and affecting the user experience, thereby improving the quality of communication.

[0116] In conjunction with some embodiments of the third aspect, in some embodiments, the second message includes at least one of the following specific PIN related information:

[0117] AF identifier;

[0118] Single network slice selection assistance information S-NSSAI;

[0119] Data network name DNN;

[0120] Application function AF service identifier;

[0121] General Public User Identifier GPSI;

[0122] PIN identifier.

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

[0124] Obtain a locally stored mapping relationship table, where the mapping relationship table includes a mapping relationship between the S-NSSAI and / or DNN and the PIN identifier.

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

[0126] Obtain the corresponding user permanent identifier SUPI according to GPSI.

[0127] In conjunction with some embodiments of the third aspect, in some embodiments, authorization based on relevant information of a specific PIN in the second message includes at least one of the following:

[0128] Querying a target PIN identifier that has a mapping relationship with the S-NSSAI and / or DNN in the second message based on a locally stored mapping relationship table; or,

[0129] The target S-NSSAI and / or target DNN that has a mapping relationship with the PIN identifier in the second message is queried based on the locally stored mapping relationship table.

[0130] In conjunction with some embodiments of the third aspect, in some embodiments, the method further includes any one of the following:

[0131] If the target PIN identifier is consistent with the PIN identifier in the second message, determining that a mapping relationship exists between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message;

[0132] If the target S-NSSAI and / or target DNN are consistent with the S-NSSAI and / or DNN in the second message, determining that a mapping relationship exists between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message;

[0133] Otherwise, it is determined that there is no mapping relationship between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message.

[0134] In conjunction with some embodiments of the third aspect, in some embodiments, authorization is performed based on relevant information of a specific PIN in the second message, including:

[0135] Query the subscription information corresponding to the GPSI or SUPI, where the subscription information includes the target S-NSSAI and / or DNN.

[0136] In conjunction with some embodiments of the third aspect, in some embodiments, authorization is performed based on relevant information of a specific PIN in the second message, further comprising:

[0137] Query the permission information corresponding to the AF identifier, where the permission information is used to indicate that the AF corresponding to the AF identifier can modify the user routing policy URSP information of the GPSI or SUPI related terminal, or that the AF corresponding to the AF identifier cannot modify the URSP information of the GPSI or SUPI related terminal.

[0138] In conjunction with some embodiments of the third aspect, in some embodiments, the method further includes any one of the following:

[0139] If the S-NSSAI and / or DNN in the second message is mapped to the PIN identifier in the second message, and the S-NSSAI and / or DNN in the second message is the target S-NSSAI and / or DNN in the subscription information, and the AF corresponding to the AF identifier can modify the URSP information of the GPSI or SUPI-related terminal, an authorization result of authorization approval is generated;

[0140] If there is no mapping relationship between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message, generating an authorization result of authorization failure;

[0141] If the S-NSSAI and / or DNN in the second message is not the target S-NSSAI or DNN in the subscription information, an authorization result indicating authorization failure is generated;

[0142] If the AF corresponding to the AF identifier cannot modify the URSP information of the GPSI or SUPI related terminal, an authorization result of authorization failure is generated.

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

[0144] receiving a sixth message sent by the second entity;

[0145] A seventh message is sent to the second entity, where the seventh message includes an authorization result, wherein the authorization result includes authorization passed or authorization failed.

[0146] In conjunction with some embodiments of the third aspect, in some embodiments, the sixth message includes at least one of the following:

[0147] AF identifier;

[0148] Single network slice selection assistance information S-NSSAI;

[0149] Data network name DNN;

[0150] Application function AF service identifier;

[0151] General Public User Identifier GPSI.

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

[0153] Authorization is performed according to the sixth message to generate an authorization result.

[0154] According to a fourth aspect of the embodiments of the present disclosure, a communication processing method is proposed, the method comprising:

[0155] The first entity sends a first message to the second entity, wherein the first message is used to provide relevant information about a specific private IoT PIN;

[0156] The second entity receives the first message sent by the first entity, generates a second message or a sixth message according to the first message, and sends the second message or the sixth message to the third entity;

[0157] The third entity receives the second message or the sixth message sent by the second entity, and performs authorization based on relevant information in the second message or the sixth message;

[0158] The third entity sends a third message or a seventh message to the second entity, wherein the third message or the seventh message is used to indicate the authorization result;

[0159] The second entity receives the third message or the seventh message sent by the third entity, and sends a fifth message to the first entity, wherein the fifth message is used to indicate an authorization result, wherein the authorization result includes authorization passed or authorization failed;

[0160] The first entity receives a fifth message sent by the second entity.

[0161] According to a fifth aspect of an embodiment of the present disclosure, a first entity is provided, wherein the apparatus includes:

[0162] a transceiver module, configured to send a first message to a second entity, wherein the first message is used to provide information related to a specific private IoT PIN;

[0163] The transceiver module is used to receive a fifth message sent by the second entity, wherein the fifth message is used to indicate an authorization result, wherein the authorization result includes authorization passed or authorization failed.

[0164] According to a sixth aspect of the embodiments of the present disclosure, two entities are proposed, and the apparatus includes:

[0165] a transceiver module, configured to receive a first message sent by a first entity, and generate a second message according to the first message;

[0166] The transceiver module is used to send a fifth message to the first entity, wherein the fifth message is used to indicate an authorization result, wherein the authorization result includes authorization passed or authorization failed.

[0167] According to a seventh aspect of the embodiments of the present disclosure, a third entity is proposed, the apparatus including:

[0168] a transceiver module, configured to receive a second message or a sixth message sent by a second entity;

[0169] a processing module, configured to perform authorization based on relevant information in the second message or the sixth message;

[0170] The transceiver module is used to send the third message or the seventh message to the second entity, wherein the third message or the seventh message is used to indicate the authorization result.

[0171] According to an eighth aspect of the embodiments of the present disclosure, a first entity is provided, including:

[0172] one or more processors;

[0173] The first entity is configured to execute any one of the methods in the first aspect.

[0174] According to a ninth aspect of the embodiments of the present disclosure, a second entity is proposed, including:

[0175] one or more processors;

[0176] The second entity is used to execute any one of the methods in the second aspect.

[0177] According to a tenth aspect of the embodiments of the present disclosure, a third entity is proposed, including:

[0178] one or more processors;

[0179] The third entity is used to execute any one of the methods in the third aspect.

[0180] According to the eleventh aspect of an embodiment of the present disclosure, a communication system is proposed, comprising a first entity, a second entity, and a third entity, wherein the first entity is configured to implement any method of the first aspect, the second entity is configured to implement any method of the second aspect, and the third entity is configured to implement any method of the third aspect.

[0181] According to the twelfth aspect of the embodiment of the present disclosure, a storage medium is proposed, which stores instructions. When the instructions are executed on a communication device, the communication device executes a method as described in any one of the first aspect, the second aspect, or the third aspect.

[0182] In the thirteenth aspect, an embodiment of the present disclosure proposes a first entity, which includes at least one of a transceiver module and a processing module; wherein the first entity is used to execute optional implementation methods of the first and fifth aspects.

[0183] In the fourteenth aspect, an embodiment of the present disclosure proposes a second entity, which includes at least one of a transceiver module and a processing module; wherein the second entity is used to execute optional implementation methods of the second and sixth aspects.

[0184] In the fifteenth aspect, an embodiment of the present disclosure proposes a third entity, which includes at least one of a transceiver module and a processing module; wherein the third entity is used to execute optional implementation methods of the third aspect and the seventh aspect.

[0185] In the sixteenth aspect, an embodiment of the present disclosure proposes a core network device, which includes at least one of a transceiver module and a processing module; wherein the core network device is used to execute the optional implementation method of the fourth aspect.

[0186] In the seventeenth aspect, an embodiment of the present disclosure proposes a first entity, which includes: one or more processors; wherein the first entity is used to execute optional implementation methods of the first and fifth aspects.

[0187] In the eighteenth aspect, an embodiment of the present disclosure proposes a second entity, which includes: one or more processors; wherein the second entity is used to execute optional implementation methods of the second aspect and the sixth aspect.

[0188] In the nineteenth aspect, an embodiment of the present disclosure proposes a third entity, including: one or more processors; wherein the above-mentioned third entity is used to execute optional implementation methods of the third aspect and the seventh aspect.

[0189] In the twentieth aspect, an embodiment of the present disclosure proposes a core network device, comprising: one or more processors; wherein the above-mentioned core network device is used to execute the optional implementation method of the fourth aspect.

[0190] In aspect 21, an embodiment of the present disclosure proposes a communication system, which includes: a first entity, a second entity, and a third entity; wherein the first entity is configured to execute the method described in the optional implementation of the first and fifth aspects, the eighth and thirteenth aspects, the second entity is configured to execute the method described in the optional implementation of the second and sixth aspects, the ninth and fourteenth aspects, and the third entity is configured to execute the method described in the optional implementation of the third aspect, the seventh aspect, the tenth and fifteenth aspects.

[0191] In aspect 22, an embodiment of the present disclosure proposes a storage medium, which stores instructions. When the instructions are executed on a communication device, the communication device executes the method described in the optional implementation of the first and second aspects, the third and fourth aspects.

[0192] In the twenty-third 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 and second aspects, the third and fourth aspects.

[0193] In the twenty-fourth 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 aspect, the second aspect, the third aspect, and the fourth aspect.

[0194] In a twenty-fifth aspect, an embodiment of the present disclosure provides a chip or a chip system, wherein the chip or chip system includes a processing circuit configured to execute the method described in the optional implementation of the first aspect, the second aspect, the third aspect, and the fourth aspect.

[0195] It is understandable that the above-mentioned terminal, access network device, first network element, second network element, core network device, communication system, storage medium, program product, computer program, chip or chip system are all used to perform the method proposed in the embodiment of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding method and will not be repeated here.

[0196] The embodiments of the present disclosure provide a communication processing method, a first entity, a second entity, a third entity, and a core network device. In some embodiments, the terms "communication processing method" and "information processing method" and "communication method" are interchangeable; the terms "communication processing device" and "information processing device" and "communication device" are interchangeable; and the terms "information processing system" and "communication system" are interchangeable.

[0197] 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.

[0198] 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.

[0199] 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.

[0200] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when articles such as "a", "an", "the" in English are used in translation, the noun following the article may be understood as a singular expression or a plural expression.

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

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

[0203] 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.

[0204] 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.

[0205] 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.

[0206] 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.

[0207] 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.

[0208] 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.

[0209] 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.

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

[0211] 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.

[0212] 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.

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

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

[0215] 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.

[0216] FIG1 is a schematic diagram of the architecture of a communication system according to an embodiment of the present disclosure. As shown in FIG1 , a communication system 100 includes a terminal 101 , an access network device 102 , and a core network device 103 .

[0217] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, 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 at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0218] In some embodiments, the access network device 102 is, for example, a node or device that accesses a terminal to a wireless network. The access network device may include an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home node B (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G communication system, an open base station (Open RAN), a cloud base station (Cloud RAN), a base station in other communication systems, and at least one of an access node in a Wi-Fi system, but is not limited thereto.

[0219] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0220] In some embodiments, the access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0221] In some embodiments, the core network device 103 may be a single device including a first entity 1031, a second entity 1032, a third entity 1033, a fourth entity 1034, etc., or may be a plurality of devices or a device group including all or part of the first entity 1031, the second entity 1032, the third entity 1033, the fourth entity 1034, etc. The 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).

[0222] In some embodiments, the first entity 1031 is, for example, an application function (AF) entity.

[0223] In some embodiments, the first entity 1031 is used to “provide application services”, and the name is not limited thereto.

[0224] In some embodiments, the second entity 1032 is, for example, a Network Exposure Function (NEF) entity.

[0225] In some embodiments, the second entity 1032 is used to “manage externally open network data”, and the name is not limited thereto.

[0226] In some embodiments, the third entity 1033 is, for example, a unified data management function (UDM).

[0227] In some embodiments, the third entity 1033 is used to “perform network authentication”, and the name is not limited thereto.

[0228] In some embodiments, the third entity 1033 may be independent of the core network device 103 .

[0229] In some embodiments, the third entity 1033 may be a part of the core network device 103 .

[0230] In some embodiments, the fourth entity 1034 is, for example, a unified data repository (UDR).

[0231] In some embodiments, the fourth entity 1034 is used to “provide a unified data repository service”, and the name is not limited thereto.

[0232] 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.

[0233] 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.

[0234] 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 utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0235] In one embodiment provided herein, certain aspects of a Personal IoT Network (PIN) network supported by a 5G system (5GS) may be configured by an Application Function (AF) entity via a 5G Network Application Function (NEF). For example, to enable the 5GS to generate a User Route Selection Policy (URSP) rule associated with a specific PIN Elements with Gateway Capability (PEGC) in a specific PIN, the AF may provide the 5GS with URSP-related information for the PEGC. This procedure may be referred to as a PIN-related application guide for locating a URSP.

[0236] From a security perspective, the scope of access / operations granted to the AF needs to be limited to the PIN level and must comply with the permissions granted by the PEGC. Otherwise, a malicious AF may configure PIN-related policies for PINs that are not under the AF's control. PIN elements in the victim's PIN may result in a poor user experience due to the policies provided by the malicious AF.

[0237] In one possible embodiment, in order to authorize the modification of the URSP, the UDM only checks whether the Single Network Slice Selection Assistance information (S-NSSAI) and / or the Data Network Name (DNN) is subscribed to the UE or UE group, and whether the AF can modify the URSP of the specified UE / UE group. If the malicious AF is authorized to modify the URSP of a specific UE / UE group, the malicious AF can provide the authorized S-NSSAI / DNN to the UDM through the NEF. The AF provides the PIN ID that it cannot manage to the NEF. Since the UDM does not check the PIN ID, the 5GC will allow the malicious AF to manage any PIN. There is no existing solution that allows the 5GS to limit the AF to the level of a specific PIN. There is no solution in this embodiment that allows the 5GS to limit the AF to the level of a specific PIN.

[0238] FIG2 is an interactive diagram of a communication processing method according to an embodiment of the present disclosure. As shown in FIG2 , the embodiment of the present disclosure relates to a communication processing method, which includes:

[0239] Step S2101 : The first entity 101 sends a first message to the second entity 102 .

[0240] In some embodiments, the second entity 102 receives the first message.

[0241] In some embodiments, the first message is used to provide information related to a specific private IoT PIN.

[0242] In some embodiments, the first entity 101 is, for example, an AF entity.

[0243] In some embodiments, the first entity 101 is used to "provide application services", but the name is not limited thereto.

[0244] In some embodiments, the second entity 102 is, for example, a NEF entity.

[0245] In some embodiments, the second entity 102 is used to “manage externally open network data”, and the name is not limited thereto.

[0246] In some embodiments, the first message includes at least one of the following: an application function AF identifier; an application function AF service identifier (AF-service-identifier); a universal public user identifier GPSI; and a PIN identifier (PINID).

[0247] In some embodiments, the GPSI may be a GPSI corresponding to a PEGC.

[0248] In some embodiments, the PIN identification may be a PIN identifier corresponding to a PEGC.

[0249] Step S2102: The second entity 102 generates a second message.

[0250] In some embodiments, the second entity 102 locally stores a locally stored mapping relationship table, wherein the mapping relationship table includes a mapping relationship between the S-NSSAI and / or DNN and the PIN identifier.

[0251] In some embodiments, the second entity 102 determines the corresponding S-NSSAI and / or DNN based on the AF service identifier in the first message.

[0252] In some embodiments, the second entity 102 searches the mapping relationship table to find the S-NSSAI and / or DNN that has a mapping relationship with the AF service identifier in the first message.

[0253] In some embodiments, the second message includes relevant information of at least one of the following specific PINs: AF identifier; single network slice selection assistance information S-NSSAI; data network name DNN; application function AF service identifier; general public user identifier GPSI; PIN identifier.

[0254] Step S2103 : The second entity 102 sends a second message to the third entity 103 .

[0255] In some embodiments, the third entity 103 receives the second message.

[0256] In some embodiments, the third entity 103 is, for example, a UDM entity.

[0257] In some embodiments, the third entity 103 is used for “performing authorization”, and the name is not limited thereto.

[0258] Step S2104: The second entity 102 performs authorization according to the second message.

[0259] In some embodiments, the second entity 102 locally stores a locally stored mapping relationship table, wherein the mapping relationship table includes a mapping relationship between the S-NSSAI and / or DNN and the PIN identifier.

[0260] In some embodiments, the second entity 102 searches for a target PIN identifier that has a mapping relationship with the S-NSSAI and / or DNN in the second message based on a locally stored mapping relationship table.

[0261] In some embodiments, the second entity 102 searches for a target S-NSSAI and / or a target DNN that has a mapping relationship with the PIN identifier in the second message based on a locally stored mapping relationship table.

[0262] In some embodiments, if the target PIN identifier is consistent with the PIN identifier in the second message, the second entity 102 determines that a mapping relationship exists between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message.

[0263] In some embodiments, if the target S-NSSAI and / or target DNN are consistent with the S-NSSAI and / or DNN in the second message, the second entity 102 determines that a mapping relationship exists between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message;

[0264] In some embodiments, the target S-NSSAI and / or target DNN are inconsistent with the S-NSSAI and / or DNN in the second message, and the second entity 102 determines that there is no mapping relationship between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message.

[0265] In some embodiments, the target PIN identifier is inconsistent with the PIN identifier in the second message, and the second entity 102 determines that there is no mapping relationship between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message.

[0266] In some embodiments, if there is a mapping relationship between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message, the second entity 102 generates a sixth message and sends the sixth message to the third entity;

[0267] In some embodiments, if there is no mapping relationship between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message, the second entity 102 generates an authorization result indicating that the authorization is rejected.

[0268] In some embodiments, the authorization result of authorization failure generated by the second entity 102 is carried in the fifth message, and the fifth message is sent by the second entity 102 to the first entity 101.

[0269] Step S2105 : The second entity 102 sends a sixth message to the third entity 103 .

[0270] In some embodiments, the third entity 103 receives the sixth message.

[0271] In some embodiments, the sixth message includes at least one of the following: AF identifier; single network slice selection assistance information S-NSSAI; data network name DNN; application function AF service identifier; general public user identifier GPSI.

[0272] Step S2106: The third entity 103 performs authorization.

[0273] In some embodiments, the third entity 103 performs authorization according to the second message.

[0274] In some embodiments, the second message includes relevant information of at least one of the following specific PINs: AF identifier; single network slice selection assistance information S-NSSAI; data network name DNN; application function AF service identifier; general public user identifier GPSI; PIN identifier.

[0275] In some embodiments, the third entity 103 locally stores a locally stored mapping relationship table, wherein the mapping relationship table includes a mapping relationship between the S-NSSAI and / or DNN and the PIN identifier.

[0276] In some embodiments, the third entity 103 obtains the corresponding user permanent identifier SUPI according to the GPSI in the second message.

[0277] In some embodiments, the third entity 103 searches for a target PIN identifier that has a mapping relationship with the S-NSSAI and / or DNN in the second message based on a locally stored mapping relationship table; or

[0278] In some embodiments, the third entity 103 searches for a target S-NSSAI and / or a target DNN that has a mapping relationship with the PIN identifier in the second message based on a locally stored mapping relationship table.

[0279] In some embodiments, if the target PIN identifier is consistent with the PIN identifier in the second message, the third entity 103 determines that there is a mapping relationship between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message.

[0280] In some embodiments, if the target S-NSSAI and / or target DNN are consistent with the S-NSSAI and / or DNN in the second message, the third entity 103 determines that a mapping relationship exists between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message;

[0281] In some embodiments, the target S-NSSAI and / or target DNN are inconsistent with the S-NSSAI and / or DNN in the second message, and the third entity 103 determines that there is no mapping relationship between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message.

[0282] In some embodiments, the target PIN identifier is inconsistent with the PIN identifier in the second message, and the third entity 103 determines that there is no mapping relationship between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message.

[0283] In some embodiments, the third entity 103 queries subscription information corresponding to the GPSI or SUPI, where the subscription information includes the target S-NSSAI and / or DNN.

[0284] In some embodiments, the third entity 103 queries the permission information corresponding to the AF identifier, where the permission information is used to indicate that the AF corresponding to the AF identifier can modify the user routing policy URSP information of the GPSI or SUPI-related terminal, or that the AF corresponding to the AF identifier cannot modify the URSP information of the GPSI or SUPI-related terminal.

[0285] In some embodiments, if the S-NSSAI and / or DNN in the second message has a mapping relationship with the PIN identifier in the second message, and the S-NSSAI and / or DNN in the second message is the target S-NSSAI and / or DNN in the subscription information, and the AF corresponding to the AF identifier can modify the URSP information of the GPSI or SUPI-related terminal, the third entity 103 generates an authorization result of authorization approval.

[0286] The purpose of this is to allow the PEGC to process PINE's request after obtaining the URSP rules. Because PINE sends the PEGC a PIN ID, the PEGC needs to convert the PIN ID into S-NSSAI and DNN and establish a Protocol Data Unit (PDU) session based on this information.

[0287] Because the current core network does not store the mapping between S-NSSAI and / or DNN and PIN IDs, the UDM only performs the first two checks below. This can result in the AF configuring an S-NSSAI and / or DNN that the UE has subscribed to for a PIN ID to which no mapping exists. Furthermore, the AF can configure S-NSSAI and / or DNN information for a PIN ID that it does not manage, impacting the PIN ID user experience.

[0288] If there is no mapping relationship between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message, the third entity 103 generates an authorization result indicating that the authorization is not passed;

[0289] In some embodiments, if the S-NSSAI and / or DNN in the second message is not the target S-NSSAI or DNN in the subscription information, the third entity 103 generates an authorization result indicating that the authorization is not passed;

[0290] In some embodiments, if the AF corresponding to the AF identifier is not allowed to modify the URSP information of the GPSI or SUPI-related terminal, the third entity 103 generates an authorization result indicating that the authorization is not passed.

[0291] Step S2107 : The third entity 103 sends a third message to the second entity 102 .

[0292] In some embodiments, the second entity 102 receives the third message.

[0293] In some embodiments, the authorization result generated by the third entity 103 includes authorization passed or authorization failed.

[0294] In some embodiments, the third message carries the authorization result.

[0295] Step S2108 : The third entity 103 sends a seventh message to the second entity 102 .

[0296] In some embodiments, the second entity 102 receives the seventh message.

[0297] In some embodiments, the third entity 103 performs authorization according to the received sixth message.

[0298] In some embodiments, the sixth message includes at least one of the following: AF identifier; single network slice selection assistance information S-NSSAI; data network name DNN; application function AF service identifier; general public user identifier GPSI.

[0299] In some embodiments, the third entity 103 queries subscription information corresponding to the GPSI or SUPI, where the subscription information includes the target S-NSSAI and / or DNN.

[0300] In some embodiments, the third entity 103 queries the permission information corresponding to the AF identifier, where the permission information is used to indicate that the AF corresponding to the AF identifier can modify the user routing policy URSP information of the GPSI or SUPI-related terminal, or that the AF corresponding to the AF identifier cannot modify the URSP information of the GPSI or SUPI-related terminal.

[0301] In some embodiments, if the S-NSSAI and / or DNN in the second message is the target S-NSSAI and / or DNN in the subscription information, and the AF corresponding to the AF identifier can modify the URSP information of the GPSI or SUPI-related terminal, the third entity 103 generates an authorization result of authorization approval;

[0302] In some embodiments, if the S-NSSAI and / or DNN in the second message is not the target S-NSSAI or DNN in the subscription information, the third entity 103 generates an authorization result indicating that the authorization is not passed;

[0303] In some embodiments, if the AF corresponding to the AF identifier is not allowed to modify the URSP information of the GPSI or SUPI-related terminal, the third entity 103 generates an authorization result indicating that the authorization is not passed.

[0304] In some embodiments, the authorization result generated by the third entity 103 according to the sixth message is carried by the seventh message and sent to the second entity 102.

[0305] Step S2109 : The second entity 102 sends a fourth message to the fourth entity 104 .

[0306] In some embodiments, the fourth entity 104 receives the fourth message.

[0307] In some embodiments, the fourth message is information related to a specific PIN.

[0308] In some embodiments, the relevant information of a specific PIN includes, but is not limited to: an application function AF identifier; an application function AF service identifier; a universal public user identifier GPSI; and a PIN identifier.

[0309] In some embodiments, in response to the third message or the seventh message indicating that the authorization is passed, a fourth message is sent to the fourth network element.

[0310] In some embodiments, in response to the third message or the seventh message indicating that the authorization is rejected, the fourth message is not sent to the fourth network element.

[0311] In some embodiments, the fourth entity 104 is, for example, a UDR entity.

[0312] In some embodiments, the fourth entity 104 is used to “provide a unified data repository service”, and the name is not limited thereto.

[0313] Step S2110 : The second entity 102 sends a fifth message to the first entity 101 .

[0314] In some embodiments, the first entity 101 receives the fifth message.

[0315] In some embodiments, the fifth message includes an authorization result. Optionally, the authorization result includes authorization passed or authorization failed.

[0316] 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", "symbol", "codeword", "codebook", "codeword", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

[0317] In some embodiments, the terms "radio", "wireless", "radio access network (RAN)", "access network (AN)", "RAN-based" and the like may be used interchangeably.

[0318] In some embodiments, the terms "search space", "search space set", "search space configuration", "search space set configuration", "control resource set (CORESET)", "CORESET configuration" and the like may be used interchangeably.

[0319] In some embodiments, the terms "component carrier (CC)", "cell", "frequency carrier", "carrier frequency" and the like can be used interchangeably.

[0320] In some embodiments, "obtain", "get", "get", "receive", "transmit", "bidirectional transmission", "send and / or receive" can be interchangeable, and can be interpreted as receiving from other entities, obtaining from protocols, obtaining from higher layers, obtaining by self-processing, autonomous implementation, etc.

[0321] In some embodiments, terms such as "send", "transmit", "report", "download", "transmit", "bidirectional transmission", "send and / or receive" can be used interchangeably.

[0322] 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.

[0323] 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.

[0324] The communication method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2110. For example, step S2101 may be implemented as an independent embodiment, step S2102 may be implemented as an independent embodiment, steps S2101+S2103 may be implemented as independent embodiments, and steps S2101+S2102+S2103 may be implemented as independent embodiments, but the present invention is not limited thereto.

[0325] In some embodiments, steps S2107 and S2108 may be executed in an interchanged order or simultaneously.

[0326] In some embodiments, steps S2104, S2105, and S2108 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

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

[0328] FIG3A is a flow chart of a communication processing method according to an embodiment of the present disclosure. As shown in FIG3A , the present disclosure embodiment relates to a communication processing method, which includes:

[0329] Step S3101, sending the first message.

[0330] The optional implementation of step S3101 can refer to the optional implementation of step S2101 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0331] Step S3102, receive the fifth message.

[0332] The optional implementation of step S3102 can refer to the optional implementation of step S2110 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0333] The communication method involved in the embodiments of the present disclosure may include at least one of steps S3101 and S3102. For example, step S3101 may be implemented as an independent embodiment, step S3102 may be implemented as an independent embodiment, and step S3101 + step S3102 may be implemented as independent embodiments, but the present invention is not limited thereto.

[0334] In some embodiments, step S3101 and step S3102 may be executed in an interchanged order or simultaneously.

[0335] In some embodiments, step S3101 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0336] In some embodiments, step S3102 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0337] FIG4A is a flow chart of a communication processing method according to an embodiment of the present disclosure. As shown in FIG4A , the present disclosure embodiment relates to a communication processing method, which includes:

[0338] Step S4101, receiving a first message.

[0339] The optional implementation of step S4101 can refer to the optional implementation of step S2101 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0340] Step S4102: Determine the corresponding S-NSSAI and / or DNN based on the AF service identifier in the first message.

[0341] The optional implementation of step S4102 can refer to the optional implementation of step S2102 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0342] Step S4103: Generate a second message based on the first message.

[0343] The optional implementation of step S4103 can refer to the optional implementation of step S2102 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0344] Step S4104: Send the second message to the third entity.

[0345] The optional implementation of step S4104 can refer to the optional implementation of step S2103 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0346] Step S4105: Receive a third message sent by a third entity.

[0347] The optional implementation of step S4105 can refer to the optional implementation of step S2107 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0348] Step S4106: In response to the third message or the seventh message indicating that the authorization is passed, a fourth message is sent to the fourth network element.

[0349] The optional implementation of step S4106 can refer to the optional implementation of step S2109 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0350] Step S4107: Obtain the mapping relationship table stored locally.

[0351] The optional implementation of step S4107 can refer to the optional implementation of step S2104 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0352] Step S4108: Search the locally stored mapping relationship table for a target PIN identifier that has a mapping relationship with the S-NSSAI and / or DNN in the second message.

[0353] The optional implementation of step S4108 can refer to the optional implementation of step S2104 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0354] Step S4109: Query the target S-NSSAI and / or target DNN that has a mapping relationship with the PIN identifier in the second message based on the locally stored mapping relationship table.

[0355] The optional implementation of step S4109 can refer to the optional implementation of step S2104 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0356] Step S4110: If the target PIN identifier is consistent with the PIN identifier in the second message, determine that there is a mapping relationship between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message.

[0357] The optional implementation of step S4110 can refer to the optional implementation of step S2104 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0358] Step S4111: If the target S-NSSAI and / or target DNN are consistent with the S-NSSAI and / or DNN in the second message, determine that there is a mapping relationship between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message.

[0359] The optional implementation of step S4111 can refer to the optional implementation of step S2104 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0360] Step S4112: If there is a mapping relationship between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message, a sixth message is generated.

[0361] The optional implementation of step S4112 can refer to the optional implementation of step S2104 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0362] Step S4113: Send the sixth message to the third entity 103.

[0363] The optional implementation of step S4113 can refer to the optional implementation of step S2105 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0364] In step S4114, if there is no mapping relationship between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message, an authorization result indicating that the authorization is not passed is generated, wherein the fifth message carries the authorization result indicating that the authorization is not passed.

[0365] The optional implementation of step S4114 can refer to the optional implementation of step S2104 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0366] The communication method according to the embodiments of the present disclosure may include at least one of steps S4101 to S4114. For example, step S4101 may be implemented as an independent embodiment, step S4102 may be implemented as an independent embodiment, steps S4101+S4103 may be implemented as independent embodiments, and steps S4101+S4102+S4103 may be implemented as independent embodiments, but the present invention is not limited thereto.

[0367] In some embodiments, steps S4101 and S4104 may be executed in an interchanged order or simultaneously.

[0368] In some embodiments, steps S4105 and S4106 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0369] FIG4B is a flow chart of a communication processing method according to an embodiment of the present disclosure. As shown in FIG4B , the present disclosure embodiment relates to a communication processing method, which includes:

[0370] Step S4201: Determine the S-NSSAI and / or DNN corresponding to the AF service identifier.

[0371] The optional implementation of step S4201 can refer to step S2101 in Figure 2, the optional implementation of step S4102 in Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0372] Step S4202: Send the fourth message.

[0373] The optional implementation of step S4202 can refer to step S2109 in Figure 2, the optional implementation of step S4106 in Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0374] Step S4203: Perform authorization according to the second message.

[0375] The optional implementation of step S4201 can refer to step S2104 in Figure 2, the optional implementation of steps S4107-S4111 in Figure 4A, and other related parts in the embodiments involved in Figures 2 and 4A, which will not be repeated here.

[0376] The communication method according to the embodiments of the present disclosure may include at least one of steps S4201 to S4203. For example, step S4201 may be implemented as an independent embodiment, step S4202 may be implemented as an independent embodiment, steps S4201+S4203 may be implemented as independent embodiments, and steps S4201+S4202+S4203 may be implemented as independent embodiments, but the present invention is not limited thereto.

[0377] In some embodiments, steps S4201 and S4202 may be executed in an interchanged order or simultaneously.

[0378] In some embodiments, step S4203 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0379] FIG4C is a flow chart of a communication processing method according to an embodiment of the present disclosure. As shown in FIG4C , the present disclosure embodiment relates to a communication processing method, which includes:

[0380] Step S4301: Receive a second message sent by a second entity.

[0381] The optional implementation of step S4301 can refer to the optional implementation of step S2103 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0382] Step S4302: Receive a sixth message sent by the second entity.

[0383] The optional implementation of step S4302 can refer to the optional implementation of step S2105 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0384] Step S4303: Obtain the mapping relationship table stored locally.

[0385] The optional implementation of step S4303 can refer to the optional implementation of step S2106 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0386] Step S4304: Obtain the corresponding user permanent identifier SUPI according to the GPSI.

[0387] The optional implementation of step S4304 can refer to the optional implementation of step S2106 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0388] Step S4305: Query the target PIN identifier that has a mapping relationship with the S-NSSAI and / or DNN in the second message based on the locally stored mapping relationship table.

[0389] The optional implementation of step S4305 can refer to the optional implementation of step S2106 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0390] Step S4306: Query the target S-NSSAI and / or target DNN that has a mapping relationship with the PIN identifier in the second message based on the locally stored mapping relationship table.

[0391] The optional implementation of step S4306 can refer to the optional implementation of step S2106 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0392] Step S4307: If the target PIN identifier is consistent with the PIN identifier in the second message, determine that there is a mapping relationship between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message.

[0393] The optional implementation of step S4307 can refer to the optional implementation of step S2106 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0394] Step S4308: If the target S-NSSAI and / or target DNN are consistent with the S-NSSAI and / or DNN in the second message, determine that there is a mapping relationship between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message.

[0395] The optional implementation of step S4308 can refer to the optional implementation of step S2106 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0396] Step S4309: If the target PIN identifier is inconsistent with the PIN identifier in the second message, determine that there is no mapping relationship between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message.

[0397] The optional implementation of step S4309 can refer to the optional implementation of step S2106 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0398] Step S4310: If the target S-NSSAI and / or target DNN are inconsistent with the S-NSSAI and / or DNN in the second message, determine that there is no mapping relationship between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message.

[0399] The optional implementation of step S4310 can refer to the optional implementation of step S2106 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0400] Step S4311: query the subscription information corresponding to the GPSI or SUPI.

[0401] The optional implementation of step S4311 can refer to the optional implementation of step S2106 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0402] Step S4312: query the authority information corresponding to the AF identifier.

[0403] The optional implementation of step S4312 can refer to the optional implementation of step S2106 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0404] Step S4313: If there is a mapping relationship between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message, and the S-NSSAI and / or DNN in the second message is the target S-NSSAI and / or DNN in the subscription information, and the AF corresponding to the AF identifier can modify the URSP information of the GPSI or SUPI-related terminal, an authorization result of authorization approval is generated.

[0405] The optional implementation of step S4313 can refer to the optional implementation of step S2106 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0406] Step S4314: If there is no mapping relationship between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message, an authorization result indicating that the authorization is not passed is generated.

[0407] The optional implementation of step S4314 can refer to the optional implementation of step S2106 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0408] Step S4315: If the S-NSSAI and / or DNN in the second message is not the target S-NSSAI or DNN in the subscription information, an authorization result of failed authorization is generated.

[0409] The optional implementation of step S4315 can refer to the optional implementation of step S2106 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0410] Step S4316: If the AF corresponding to the AF identifier cannot modify the URSP information of the GPSI or SUPI related terminal, an authorization result of authorization failure is generated.

[0411] The optional implementation of step S4316 can refer to the optional implementation of step S2106 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0412] Step S4317: Send a seventh message to the second entity.

[0413] The optional implementation of step S4317 can refer to the optional implementation of step S2108 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0414] Step S4318: Send a third message to the second entity.

[0415] The optional implementation of step S4318 can refer to the optional implementation of step S2107 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0416] The communication method according to the embodiments of the present disclosure may include at least one of steps S4301 to S4318. For example, step S4101 may be implemented as an independent embodiment, step S4302 may be implemented as an independent embodiment, steps S4301+S4303 may be implemented as independent embodiments, and steps S4301+S4302+S4303 may be implemented as independent embodiments, but the present invention is not limited thereto.

[0417] In some embodiments, steps S4301 and S4304 may be executed in an interchanged order or simultaneously.

[0418] In some embodiments, steps S4305 and S4306 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0419] FIG4D is a flow chart of a communication processing method according to an embodiment of the present disclosure. As shown in FIG4D , the embodiment of the present disclosure relates to a communication processing method, which includes:

[0420] Step S4401: Perform authorization based on the relevant information in the second message.

[0421] The optional implementation of step S4401 can refer to step S2106 in Figure 2, the optional implementation of steps S4303-S4316 in Figure 4C, and other related parts in the embodiments involved in Figures 2 and 4C, which will not be repeated here.

[0422] Step S4402: Perform authorization based on the relevant information in the sixth message.

[0423] The optional implementation of step S4402 can refer to step S2106 in Figure 2, the optional implementation of steps S4303-S4316 in Figure 4C, and other related parts in the embodiments involved in Figures 2 and 4C, which will not be repeated here.

[0424] FIG5A is an interactive diagram of a communication processing method according to an embodiment of the present disclosure. As shown in FIG5A , the embodiment of the present disclosure relates to a communication processing method, which includes:

[0425] In step S5101, a first entity sends a first message to a second entity, where the first message is used to provide relevant information of a specific private IoT PIN.

[0426] The optional implementation of step S5101 can refer to the optional implementation of step S2101 in Figure 2, step S3101 in Figure 3, and other related parts in the embodiments involved in Figures 2, 3, and 4, which will not be repeated here.

[0427] In some embodiments, the above method may include the methods of the above-mentioned embodiments of the communication system side, terminal side, access network equipment side, core network equipment side, first network element side, second network element side, etc., which will not be repeated here.

[0428] Step S5102: The first entity receives a fifth message sent by the second entity, where the fifth message is used to indicate an authorization result, where the authorization result includes authorization passed or authorization failed.

[0429] The optional implementation of step S5102 can refer to step S2110 in Figure 2, the optional implementation of step S3102 in Figure 3, and other related parts in the embodiments involved in Figures 2, 3, and 4, which will not be repeated here.

[0430] Step S5103: The second entity receives the first message sent by the first entity, and generates a second message according to the first message.

[0431] The optional implementation of step S5103 can refer to the optional implementation of step S2102 in Figure 2, step S4103 in Figure 4, and other related parts in the embodiments involved in Figures 2, 3, and 4, which will not be repeated here.

[0432] Step S5104: The second entity sends a fifth message to the first entity, where the fifth message is used to indicate an authorization result, where the authorization result includes authorization passed or authorization failed.

[0433] The optional implementation of step S5104 can refer to the optional implementation of step S2110 in Figure 2, step S4114 in Figure 4, and other related parts in the embodiments involved in Figures 2, 3, and 4, which will not be repeated here.

[0434] Step S5105: The third entity receives the second message or the sixth message sent by the second entity.

[0435] The optional implementation of step S5105 can refer to the optional implementation of steps S2103 and S2105 in Figure 2, steps S4301 and S4302 in Figure 4, and other related parts in the embodiments involved in Figures 2, 3 and 4, which will not be repeated here.

[0436] Step S5106: The third entity performs authorization based on the relevant information in the second message or the sixth message.

[0437] The optional implementation of step S5106 can refer to the optional implementation of step S2106 in Figure 2, steps S4303-S4316 in Figure 4, and other related parts in the embodiments involved in Figures 2, 3, and 4, which will not be repeated here.

[0438] Step S5107: The third entity sends a third message or a seventh message to the second entity, where the third message or the seventh message is used to indicate the authorization result.

[0439] The optional implementation of step S5107 can be found in steps S2107 and S2108 of Figure 2, the optional implementation of steps S4317 and S4318 of Figure 4, and other related parts in the embodiments involved in Figures 2, 3, and 4, which will not be repeated here.

[0440] Figure 6 is a schematic diagram of a communication processing method according to an embodiment of the present disclosure. As shown in Figure 6, the embodiment of the present disclosure relates to a communication processing method, which includes:

[0441] Step S6101: AF sends first information to NEF.

[0442] Optionally, AF is the first entity mentioned above.

[0443] Optionally, the first information includes relevant information of a specific PIN.

[0444] Optionally, the relevant information of a specific PIN includes AFID, AF-service-identifier, GPSI of PEGC and PIN ID.

[0445] Step S6102: NEF generates second information based on the first information.

[0446] Optionally, NEF is the second entity mentioned above.

[0447] Optionally, the NEF locally stores a mapping relationship between the S-NSSAI / DNN and the PIN ID.

[0448] Optionally, NEF converts AF-service-identifier to a combination of DNN and S-NSSAI

[0449] Optionally, the NEF searches for the S-NSSAI / DNN and PIN ID corresponding to the PIN ID according to the mapping relationship.

[0450] Optionally, the NEF adds the S-NSSAI / DNN and PIN ID corresponding to the PIN ID to the second information.

[0451] Optionally, the second information includes AF identifier; S-NSSAI; DNN; AF service identifier; GPSI; and PIN ID.

[0452] Step S6103: NEF performs mapping verification based on information related to the specific PIN.

[0453] Optionally, the NEF determines whether the S-NSSAI / DNN in the second information and the PIN ID in the second information have a mapping relationship based on the mapping relationship between the S-NSSAI / DNN and the PIN ID.

[0454] Optionally, the S-NSSAI / DNN in the second information has a mapping relationship with the PIN ID in the second information, and the request information is sent to the UMD.

[0455] Optionally, the request information includes single network slice selection auxiliary information S-NSSAI; data network name DNN; application function AF service identifier; and general public user identifier GPSI.

[0456] Optionally, the S-NSSAI / DNN in the second information has no mapping relationship with the PIN ID in the second information, and an authorization result of authorization failure is generated and sent to the AF.

[0457] Step S6104: NEF sends a request message to UDM.

[0458] Optionally, the UDM is the third entity mentioned above.

[0459] Optionally, the request information includes S-NSSAI, DNN, AFID, AF-service-identifier, and GPSI of PEGC.

[0460] Optionally, the request information includes a PINID.

[0461] Step S6105: UDM performs authorization verification based on the request information.

[0462] Optionally, UDM performs mapping verification.

[0463] Optionally, the UDM stores mapping information between the S-NSSAI / DNN and the PIN ID locally.

[0464] Optionally, if the S-NSSAI / DNN in the request information has a mapping relationship with the PIN ID in the request information, the mapping verification passes.

[0465] Optionally, if the S-NSSAI / DNN in the request information does not have a mapping relationship with the PIN ID in the request information, the mapping verification fails and the authorization result is failed.

[0466] Optionally, UDM performs subscription verification.

[0467] Optionally, the UDM obtains the corresponding user permanent identifier SUPI according to the GPSI in the request information.

[0468] Optionally, the UDM queries subscription information corresponding to the GPSI or SUPI, where the subscription information includes a target S-NSSAI and / or DNN.

[0469] Optionally, if the S-NSSAI and / or DNN in the request information is the target S-NSSAI and / or DNN in the subscription information, the subscription verification passes.

[0470] Optionally, if the S-NSSAI and / or DNN in the request information is not the target S-NSSAI and / or DNN in the subscription information, the subscription verification fails and the authorization result is failed.

[0471] Optionally, UDM performs modification permission verification.

[0472] Optionally, the UDM queries the permission information corresponding to the AFID in the request information, wherein the permission information is used to indicate that the AF corresponding to the AF identifier can modify the user routing policy URSP information of the GPSI or SUPI related terminal, or that the AF corresponding to the AF identifier cannot modify the URSP information of the GPSI or SUPI related terminal.

[0473] Optionally, if the authority information corresponding to the AFID is used to indicate that the AF corresponding to the AF identifier can modify the user routing policy URSP information of the GPSI or SUPI related terminal, the modification authority check is passed.

[0474] Optionally, if the authority information corresponding to the AFID is used to indicate that the AF corresponding to the AF identifier cannot modify the user routing policy URSP information of the GPSI or SUPI related terminal, the modification authority check fails and the authorization result is not passed.

[0475] Optionally, if the mapping verification, subscription verification, and modification permission verification all pass, an authorization result indicating authorization passed is generated.

[0476] In step S6106, the UDM sends the authorization result to the NEF.

[0477] In step S6107, the NEF sends the relevant information of the specific PIN to the UDR according to the authorization result.

[0478] Optionally, the UDR is the fourth entity mentioned above.

[0479] Optionally, if the authorization result is failed, this step is not performed.

[0480] In step S6108, the NEF sends the authorization result to the AF.

[0481] The communication method according to the embodiments of the present disclosure may include at least one of steps S6101 to S6108. For example, step S6101 may be implemented as an independent embodiment, step S6102 may be implemented as an independent embodiment, steps S6101+S6103 may be implemented as independent embodiments, and steps S6101+S6102+S6103 may be implemented as independent embodiments, but the present invention is not limited thereto.

[0482] In some embodiments, step S6107 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0483] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0484] 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.

[0485] 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.

[0486] In the embodiments of the present disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit. The logical relationship of the above-mentioned hardware circuit is fixed or reconfigurable. For example, the processor is a hardware circuit implemented by 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.

[0487] Figure 7A is a schematic diagram of the structure of the first entity proposed in an embodiment of the present disclosure. As shown in Figure 7A, the first entity 7100 may include at least one of a transceiver module 7101 and a processing module 7102. Optionally, the transceiver module is configured to perform at least one of the communication steps, such as sending and / or receiving, performed by terminal 101 in any of the above methods, and further description thereof is omitted here. Optionally, the processing module is configured to perform at least one of the other steps performed by the first entity in any of the above methods, and further description thereof is omitted here.

[0488] Figure 7B is a schematic diagram of the structure of the second entity proposed in an embodiment of the present disclosure. As shown in Figure 7B, the second entity 7200 may include at least one of a transceiver module 7201 and a processing module 7202. Optionally, the transceiver module is configured to perform at least one of the communication steps, such as sending and / or receiving, performed by the second entity in any of the above methods, and the details thereof are not further described here. Optionally, the processing module is configured to perform at least one of the other steps performed by the second entity in any of the above methods, and the details thereof are not further described here.

[0489] Figure 7C is a schematic diagram of the structure of the third entity proposed in an embodiment of the present disclosure. As shown in Figure 7C, the third entity 7300 may include: at least one of a transceiver module 7301 and a processing module 7302. Optionally, the transceiver module is configured to perform at least one of the communication steps, such as sending and / or receiving, performed by the third entity in any of the above methods, and the details thereof are not further described here. Optionally, the processing module is configured to perform at least one of the other steps performed by each entity of the third entity in any of the above methods, and the details thereof are not further described here.

[0490] In some embodiments, the transceiver module may include a transmitting module and / or a receiving module, and the transmitting module and the receiving module may be separate or integrated. Optionally, the transceiver module may be interchangeable with the transceiver.

[0491] In some embodiments, the processing module can be a single module or can include multiple submodules. Optionally, the multiple submodules respectively execute all or part of the steps required to be executed by the processing module. Optionally, the processing module can be interchangeable with the processor.

[0492] Figure 8A is a schematic diagram of the structure of a communication device 8100 proposed in an embodiment of the present disclosure. Communication device 8100 can be a network device (e.g., an access network device, a core network device, etc.), a terminal (e.g., a user equipment, etc.), a chip, a chip system, or a processor that supports a network device to implement any of the above methods, or a chip, a chip system, or a processor that supports a terminal to implement any of the above methods. Communication device 8100 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.

[0493] As shown in Figure 8A, the communication device 8100 includes one or more processors 8101. The processor 8101 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 the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. The communication device 8100 is used to perform any of the above methods.

[0494] In some embodiments, the communication device 8100 further includes one or more memories 8102 for storing instructions. Optionally, all or part of the memories 8102 may be located outside the communication device 8100.

[0495] In some embodiments, the communication device 8100 further includes one or more transceivers 8103. When the communication device 8100 includes one or more transceivers 8103, the transceiver 8103 performs at least one of the communication steps such as sending and / or receiving in the above method, and the processor 8101 performs at least one of the other steps.

[0496] 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.

[0497] In some embodiments, the communication device 8100 may include one or more interface circuits 8104. Optionally, the interface circuit 8104 is connected to the memory 8102. The interface circuit 8104 may be configured to receive signals from the memory 8102 or other devices, and may be configured to send signals to the memory 8102 or other devices. For example, the interface circuit 8104 may read instructions stored in the memory 8102 and send the instructions to the processor 8101.

[0498] The communication device 8100 described in the above embodiments may be a network device or a terminal, but the scope of the communication device 8100 described in the present disclosure is not limited thereto, and the structure of the communication device 8100 may not be limited by FIG. 8A. 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.

[0499] FIG8B is a schematic diagram of the structure of a chip 8200 according to an embodiment of the present disclosure. If the communication device 8100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 8200 shown in FIG8B , but the present disclosure is not limited thereto.

[0500] The chip 8200 includes one or more processors 8201 , and the chip 8200 is configured to execute any of the above methods.

[0501] In some embodiments, the chip 8200 further includes one or more interface circuits 8202. Optionally, the interface circuit 8202 is connected to the memory 8203. The interface circuit 8202 can be used to receive signals from the memory 8203 or other devices, and can be used to send signals to the memory 8203 or other devices. For example, the interface circuit 8202 can read instructions stored in the memory 8203 and send the instructions to the processor 8201.

[0502] In some embodiments, the interface circuit 8202 performs at least one of the communication steps such as sending and / or receiving in the above method, and the processor 8201 performs at least one of the other steps (but not limited to these).

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

[0504] In some embodiments, the chip 8200 further includes one or more memories 8203 for storing instructions. Alternatively, all or part of the memories 8203 may be outside the chip 8200.

[0505] The present disclosure also proposes a storage medium having instructions stored thereon, which, when executed on the communication device 8100, causes the communication device 8100 to execute 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 temporary storage medium.

[0506] The present disclosure also provides a program product, which, when executed by the communication device 8100, enables the communication device 8100 to perform any of the above methods. Optionally, the program product is a computer program product.

[0507] 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 processing method, characterized in that: The method comprises: Sending a first message to a second entity, wherein the first message is used to provide relevant information about a specific private IoT PIN; A fifth message sent by the second entity is received, wherein the fifth message is used to indicate an authorization result, wherein the authorization result includes authorization passed or authorization failed.

2. The method according to claim 1, characterized in that The first message includes at least one of the following: Application capability AF identifier; Application function AF service identifier; General Public User Identifier GPSI; PIN identifier.

3. A communication processing method, characterized in that: The method comprises: receiving a first message sent by a first entity, and generating a second message according to the first message; A fifth message is sent to the first entity, wherein the fifth message is used to indicate the authorization result, wherein the authorization result includes authorization passed or authorization failed.

4. The method according to claim 3, characterized in that The first message includes at least one of the following: Application capability AF identifier; AF service identifier; General Public User Identifier GPSI; PIN identifier.

5. The method according to claim 3, characterized in that: The second message includes at least one of the following specific PIN related information: AF identifier; Single network slice selection auxiliary information S-NSSAI; Data network name DNN; Application function AF service identifier; General Public User Identifier GPSI; PIN identifier.

6. The method according to claim 4 or 5, characterized in that: The generating the second message according to the first message includes: Determine the corresponding S-NSSAI and / or DNN based on the AF service identifier in the first message.

7. The method according to any one of claims 3 to 6, characterized in that: The method further comprises: sending the second message to a third entity; A third message sent by the third entity is received, wherein the third message is used to indicate an authorization result.

8. The method according to any one of claims 7, characterized in that The method further comprises: In response to the third message indicating that the authorization is passed, a fourth message is sent to the fourth network element.

9. The method according to any one of claims 3 to 6, characterized in that: The method further comprises: Authorization is performed according to the second message.

10. The method according to claim 9, characterized in that The performing authorization according to the second message includes: Obtain a locally stored mapping relationship table, wherein the mapping relationship table includes a mapping relationship between the S-NSSAI and / or DNN and the PIN identifier.

11. The method according to claim 10, characterized in that The method further comprises at least one of the following: Querying the target PIN identifier having a mapping relationship with the S-NSSAI and / or DNN in the second message based on the locally stored mapping relationship table; or, Based on the locally stored mapping relationship table, query the target that has a mapping relationship with the PIN identifier in the second message S-NSSAI and / or target DNN.

12. The method according to claim 11, characterized in that The method further includes any of the following: If the target PIN identifier is consistent with the PIN identifier in the second message, determining that there is a mapping relationship between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message; If the target S-NSSAI and / or target DNN are consistent with the S-NSSAI and / or DNN in the second message, determine that there is a mapping relationship between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message; Otherwise, it is determined that there is no mapping relationship between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message.

13. The method according to claim 11, characterized in that The method further includes any of the following: If there is a mapping relationship between the S-NSSAI and / or the DNN in the second message and the PIN identifier in the second message, generate a sixth message, and send the sixth message to the third entity; If there is no mapping relationship between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message, an authorization result of failed authorization is generated, wherein the fifth message carries the authorization result of failed authorization.

14. The method according to claim 13, characterized in that The sixth message includes at least one of the following: AF identifier; Single network slice selection auxiliary information S-NSSAI; Data network name DNN; Application function AF service identifier; General Public User Identifier GPSI.

15. A communication processing method, characterized in that: The method comprises: receiving a second message or a sixth message sent by a second entity; Performing authorization based on the relevant information in the second message or the sixth message; Sending a third message or a seventh message to the second entity, wherein the third message or the seventh message is used to indicate an authorization result.

16. The method according to claim 15, characterized in that The second message includes at least one of the following specific PIN related information: AF identifier; Single network slice selection auxiliary information S-NSSAI; Data network name DNN; Application function AF service identifier; General Public User Identifier GPSI; PIN identifier.

17. The method according to claim 15 or 16, characterized in that The method further comprises: Obtain a locally stored mapping relationship table, wherein the mapping relationship table includes a mapping relationship between the S-NSSAI and / or DNN and the PIN identifier.

18. The method according to claim 15 or 16, characterized in that The method further comprises: The corresponding user permanent identifier SUPI is obtained according to the GPSI.

19. The method according to claim 17, characterized in that The authorization based on the relevant information of the specific PIN in the second message includes at least one of the following: Querying the target PIN identifier having a mapping relationship with the S-NSSAI and / or DNN in the second message based on the locally stored mapping relationship table; or, Based on the locally stored mapping relationship table, query the target S-NSSAI and / or target DNN that has a mapping relationship with the PIN identifier in the second message.

20. The method according to claim 19, characterized in that The method further includes any of the following: If the target PIN identifier is consistent with the PIN identifier in the second message, determine the S-NSSAI in the second message and / or a mapping relationship exists between the DNN and the PIN identifier in the second message; If the target S-NSSAI and / or target DNN are consistent with the S-NSSAI and / or DNN in the second message, determine that there is a mapping relationship between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message; Otherwise, it is determined that there is no mapping relationship between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message.

21. The method according to any one of claims 16 to 18, characterized in that The performing authorization based on the relevant information of the specific PIN in the second message includes: and querying subscription information corresponding to the GPSI or the SUPI, wherein the subscription information includes a target S-NSSAI and / or DNN.

22. The method according to any one of claims 16 to 18, characterized in that The authorization based on the relevant information of the specific PIN in the second message further includes: querying the permission information corresponding to the AF identifier, wherein the permission information is used to indicate that the AF corresponding to the AF identifier can modify the user routing policy URSP information of the terminal related to the GPSI or the SUPI, or that the AF corresponding to the AF identifier cannot modify the URSP information of the terminal related to the GPSI or the SUPI.

23. The method according to any one of claims 19 to 22, characterized in that The method further includes any of the following: If there is a mapping relationship between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message, and the S-NSSAI and / or DNN in the second message is the target S-NSSAI and / or DNN in the subscription information, and the AF corresponding to the AF identifier can modify the URSP information of the GPSI or the SUPI-related terminal, an authorization result of authorization passing is generated; If there is no mapping relationship between the S-NSSAI and / or DNN in the second message and the PIN identifier in the second message, generating an authorization result indicating that the authorization is not passed; If the S-NSSAI and / or DNN in the second message is not the target S-NSSAI or DNN in the subscription information, generating an authorization result indicating that the authorization is not passed; If the AF corresponding to the AF identifier cannot modify the URSP information of the terminal related to the modified GPSI or the SUPI, an authorization result of authorization failure is generated.

24. The method according to claim 15, characterized in that The method further comprises: receiving a sixth message sent by the second entity; A seventh message is sent to the second entity, where the seventh message includes an authorization result, wherein the authorization result includes authorization passed or authorization failed.

25. The method according to claim 24, characterized in that The sixth message includes at least one of the following: AF identifier; Single network slice selection auxiliary information S-NSSAI; Data network name DNN; Application function AF service identifier; General Public User Identifier GPSI.

26. The method according to claim 24 or 25, characterized in that The method further comprises: Authorization is performed according to the sixth message to generate an authorization result.

27. A first entity, characterized in that: The device comprises: A transceiver module, configured to send a first message to a second entity, wherein the first message is used to provide relevant information of a specific private IoT PIN; A fifth message sent by the second entity is received, wherein the fifth message is used to indicate an authorization result, wherein the authorization result includes authorization passed or authorization failed.

28. A second entity, characterized in that: The device comprises: A transceiver module, configured to receive a first message sent by a first entity, and generate a second message according to the first message; A fifth message is sent to the first entity, wherein the fifth message is used to indicate the authorization result, wherein the authorization result includes authorization passed or authorization failed.

29. A third entity, characterized in that: The device comprises: A transceiver module, configured to receive a second message or a sixth message sent by a second entity; A processing module, configured to perform authorization based on relevant information in the second message or the sixth message; The transceiver module is further used to send a third message or a seventh message to the second entity, wherein the third message or the seventh message is used to indicate an authorization result.

30. A first entity, characterized in that: include: one or more processors; The first entity is used to execute the method according to any one of claims 1 to 2.

31. A second entity, characterized in that: include: one or more processors; The second entity is used to execute the method according to any one of claims 3 to 14.

32. A third entity, characterized in that: include: one or more processors; The third entity is used to execute the method according to any one of claims 15-26.

33. A communication system, characterized in that: Includes a first entity, a second entity, and a third entity, wherein the first entity is configured to implement the method of any one of claims 1-2, the second entity is configured to implement the method of any one of claims 3-14, and the third entity is configured to implement the method of any one of claims 15-26.

34. A storage medium storing instructions, characterized in that: When the instruction is executed on a communication device, the communication device is caused to execute the method as described in any one of claims 1-2, 3-14 or 15-26.

Images