Information processing methods, devices, communication equipment and storage media

Abstract

This disclosure provides an information processing method, apparatus, communication device, and storage medium. The information processing method, executed by a first network device, may include: receiving a first request message, wherein the first request message includes: a first identifier and a first configuration, the first identifier being used to identify a Personal Internet of Things (PINE), and the first configuration being used to configure a Personal Internet of Things (PIN), the PINE including: a Personal Internet of Things (PEGC) with gateway capabilities; determining first data of the Personal Internet of Things PIN based on the first identifier and the first configuration, the first data being data of a policy for generating the PIN. In the PIN creation process, PIN creation and policy data creation are implemented simultaneously, instead of using two separate processes for PIN creation and policy data creation, thus reducing the signaling overhead introduced by the creation process and the two creation processes.

Description

Technical Field

[0001] This disclosure relates to, but is not limited to, the field of wireless communication technology, and particularly to an information processing method apparatus, communication device, and storage medium. Background Technology

[0002] A Personal Internet of Things Network (PIN) may include one or more Personal IoT Network Elements (PINEs) (also known as Personal IoT Members). PINEs can be categorized into three types: ordinary PINEs, PINEs using a PIN Element with Management Capability (PEMC), also known as Personal IoT Management Devices, and PINEs using a PIN Element with Gateway Capability (PEGC), also known as Personal IoT Gateway Devices (Element with Gateway Capability, PEGC). PINEs can be locally managed by PEMCs and / or PEGCs.

[0003] During the PIN creation process, certain creations based on PIN communication are not covered. Summary of the Invention

[0004] This disclosure provides an information processing method, apparatus, communication device, and storage medium.

[0005] The first aspect of this disclosure provides an information processing method, wherein the method is executed by a first network device, and the method further includes:

[0006] Receive a first request message, wherein the first request message includes: a first identifier and a first configuration, the first identifier is used to identify a Personal Internet of Things Element (PINE), the first configuration is used to configure a PIN, and the PINE includes: a Personal Internet of Things Element (PEGC) with gateway capabilities;

[0007] Based on the first identifier and the first configuration, first data for determining the personal IoT PIN is determined, wherein the first data is data of the strategy for generating the PIN.

[0008] A second aspect of this disclosure provides an information processing method, wherein the method is executed by a second network device, and the method further includes:

[0009] Receive a third request message, wherein the third request message includes a first identifier and a first configuration, the first identifier is used to identify a Personal Internet of Things Element (PINE), the first configuration is used to configure a PIN, and the PINE includes: a Personal Internet of Things Element (PEGC) with gateway capabilities;

[0010] Create a PIN based on the third request message;

[0011] Send a third response message; wherein the third response message includes second information; the second information indicates the creation result of the PIN;

[0012] Send a first request message, wherein the first request message includes a first identifier and a first configuration; the first identifier and the first configuration are used to create first data; the first data is data of the strategy for generating the PIN.

[0013] A third aspect of this disclosure provides an information processing method, wherein the method is executed by a third network device, and the method further includes:

[0014] Send a first request message, wherein the first request message includes: a first identifier and a first configuration, the first identifier being used to identify a Personal Internet of Things Element (PINE), the first configuration being used to configure a PIN, and the PINE including: a Personal Internet of Things Element (PEGC) with gateway capabilities;

[0015] Receive a first response message; wherein the first response message includes first information; the first information is the creation result of the first data of the personal IoT PIN;

[0016] Send a second request message; wherein, if the first data creation fails, the second request message includes: a second identifier and / or a second configuration; wherein, the second request message is used to request the re-creation of the first data; wherein, the first data is used for the strategy of generating the PIN.

[0017] A fourth aspect of this disclosure provides an information processing method, wherein the method is executed by a first type of AF, and the method includes:

[0018] Send a first request message, the first request message including: a first identifier and a first configuration, the first identifier being used to identify a Personal Internet of Things Element (PINE), the first configuration being used to configure a PIN, the PINE including: a Personal Internet of Things Element (PEGC) with gateway capabilities;

[0019] Receive a first response message; wherein the first response message includes first information; the first information indicates the creation result of the first data of the personal IoT PIN;

[0020] Send a second request message; wherein, if the first data creation fails, the second request message includes: a second identifier and / or a second configuration; wherein, the second request message is used to request the first network device to recreate the second data; wherein, the policy data is used to generate the policy for the PIN; the second type of AF is located outside the trust domain of the first network device.

[0021] A fifth aspect of this disclosure provides an information processing method, wherein the method is executed by a second type of AF, and the method includes:

[0022] Send a first request message, which includes: the first identification information of the PINE and the first PIN configuration data; the PINE includes at least PEGC; wherein, the first request message is sent after the personal IoT PIN is successfully created, and is used to request the policy data for creating the PIN;

[0023] Receive the first response message; wherein the first response message includes: the creation result of the policy data;

[0024] If the first response message indicates that the policy data creation of the PIN has failed, a second request message is sent; wherein the second request message includes: the second identification information of the PINE and / or the second PIN configuration data; wherein the second request message is used to request the first network device to recreate the policy data of the PIN; wherein the policy data is used to generate the policy of the PIN; the second type of AF is located outside the trust domain of the first network device.

[0025] A sixth aspect of this disclosure provides an information processing method, wherein the method is executed by a core network device, and the method includes:

[0026] Receive a first request message; the first request message includes: a first identifier and a first configuration, the first identifier is used to identify a Personal Internet of Things Element (PINE), the first configuration is used to configure a PIN, the PINE includes: a Personal Internet of Things Element (PEGC) with gateway capabilities;

[0027] Based on the first request message, create the first data for the PIN;

[0028] Send a first response message, wherein the first response message includes: the creation result of the first data.

[0029] A seventh aspect of this disclosure provides an information processing method, wherein the method is executed by a communication system and includes:

[0030] A first network device receives a first request message; the first request message includes: a first identifier and a first configuration, the first identifier is used to identify a Personal Internet of Things Element (PINE), the first configuration is used to configure a PIN, and the PINE includes: a Personal Internet of Things Element (PEGC) with gateway capabilities;

[0031] The first network device creates the first data for the personal IoT PIN;

[0032] The first network device sends a first response message to the second network device, the third network device, or the first type of application function, wherein the first response message includes first information: the first information indicates the creation result of the first data; the first response message is forwarded or transparently transmitted by the third network device to the second type of application function AF.

[0033] An eighth aspect of this disclosure provides an information processing method, wherein the method is executed by a communication system, the method comprising:

[0034] A first network device receives a first request message; the first request message includes: a first identifier and a first configuration, the first identifier is used to identify a Personal Internet of Things Element (PINE), the first configuration is used to configure a PIN, and the PINE includes: a Personal Internet of Things Element (PEGC) with gateway capabilities;

[0035] The first network device creates the first data for the personal IoT PIN;

[0036] The first network device sends a first response message to the second network device, the third network device, or the first type of application function, wherein the first response message includes first information: the first information indicates the creation result of the first data; the first response message is forwarded or transparently transmitted by the third network device to the second type of application function AF.

[0037] A ninth aspect of this disclosure provides a first information processing apparatus, wherein the apparatus further includes:

[0038] A first receiving module is configured to receive a first request message, wherein the first request message includes: a first identifier and a first configuration, the first identifier being used to identify a Personal Internet of Things Element (PINE), and the first configuration being used to configure a PIN, wherein the PINE includes: a Personal Internet of Things Element (PEGC) with gateway capabilities;

[0039] The first creation module is configured to determine first data of a personal IoT PIN based on the first identifier and the first configuration, wherein the first data is data of a strategy for generating the PIN.

[0040] A tenth aspect of this disclosure provides a second information processing apparatus, wherein the apparatus further includes:

[0041] The second receiving module is configured to receive a third request message, wherein the third request message includes a first identifier and a first configuration, the first identifier being used to identify a Personal Internet of Things Element (PINE), and the first configuration being used to configure a PIN, wherein the PINE includes a Personal Internet of Things Element (PEGC) with gateway capabilities.

[0042] The second creation module is configured to create a PIN based on the third request message;

[0043] The second sending module is configured to send a third response message based on the creation result of the PIN; wherein the third response message includes second information; the second information indicates the creation result of the PIN;

[0044] The second sending module is configured to send a first request message, wherein the first request message includes a first identifier and a first configuration; the first identifier and the first configuration are used to create first data; the first data is data of the strategy for generating the PIN.

[0045] The eleventh aspect of this disclosure provides a third information processing apparatus, wherein the apparatus further includes:

[0046] The third receiving module is configured to receive a first response message, wherein the first response message includes first information; the first information indicates the creation result of the first data of the personal IoT PIN;

[0047] The third sending module is configured to send the first response message.

[0048] A twelfth aspect of this disclosure provides a fourth information processing apparatus, wherein the apparatus includes:

[0049] The fourth sending module is configured to send a first request message, wherein the first request message includes: a first identifier and a first configuration, the first identifier being used to identify a Personal Internet of Things Element (PINE), and the first configuration being used to configure a PIN, wherein the PINE includes: a Personal Internet of Things Element (PEGC) with gateway capabilities;

[0050] The fourth receiving module is configured to receive a first response message; wherein the first response message includes first information; the first information is the creation result of the first data of the personal IoT PIN;

[0051] The fourth sending module is configured to send a second request message; wherein, if the first data creation fails, the second request message includes: a second identifier and / or a second configuration; wherein, the second request message is used to request the re-creation of the first data; wherein, the first data is used for the strategy of generating the PIN.

[0052] A thirteenth aspect of this disclosure provides a fifth information processing apparatus, wherein the apparatus includes:

[0053] The fifth sending module is configured to send a first request message, the first request message including: a first identifier and a first configuration, the first identifier being used to identify a Personal Internet of Things Element (PINE), the first configuration being used to configure a PIN, the PINE including: a Personal Internet of Things Element (PEGC) with gateway capabilities;

[0054] The fifth receiving module is configured to receive a first response message; wherein the first response message includes first information; the first information indicates the creation result of the first data of the personal IoT PIN;

[0055] The fifth sending module is configured to send a second request message; wherein, if the first data creation fails, the second request message includes: a second identifier and / or a second configuration; wherein, the second request message is used to request the first network device to recreate the second data; wherein, the policy data is used to generate the policy for the PIN; the second type of AF is located outside the trust domain of the first network device.

[0056] A fourteenth aspect of this disclosure provides a communication system, wherein the system includes: a first network device; the system further includes: a second network device and / or a third network device;

[0057] The first network device is configured to receive a first request message; the first request message includes: a first identifier and a first configuration, the first identifier being used to identify a Personal Internet of Things Element (PINE), the first configuration being used to configure a PIN, the PINE including: a Personal Internet of Things Element with Gateway Capability (PEGC); determining first data of the Personal Internet of Things PIN based on the first identifier and the first configuration, the first data being data of a strategy for generating the PIN; sending a first response message to a second network device or a third network device, wherein the first response message includes first information; the first information indicating the creation result of the first data; wherein the first response message received by the second network device is sent to the third network device, and the first response message is sent by the third network device to a second type of application function (AF).

[0058] The fifteenth aspect of this disclosure provides a communication device, including a processor, a transceiver, a memory, and an executable program stored in the memory and executable by the processor, wherein when the processor runs the executable program, it performs the information processing method provided by any of the first to eighth aspects of the technology described above.

[0059] The sixteenth aspect of this disclosure provides a computer storage medium storing an executable program; after being executed by a processor, the executable program can implement the information processing method provided by any of the aforementioned first to eighth aspects.

[0060] In this embodiment of the disclosure, during the PIN creation process, at least one of UDM, NEF, or AF will trigger the UDR to create policy data. That is, the creation of PIN and policy data can be realized during the PIN creation process. Thus, there is no need for two separate processes to create PIN and policy data separately. Compared with creating PIN and policy data through two separate processes, the creation process can be reduced, signaling overhead can be saved, and the creation operation of AF can be simplified.

[0061] It should be understood that the technical solutions provided in the embodiments of this disclosure are exemplary and explanatory only, and are not intended to limit the embodiments of this disclosure. Attached Figure Description

[0062] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments of the invention and, together with the description, serve to explain the principles of the embodiments of the invention.

[0063] Figure 1 This is a schematic diagram illustrating the structure of a wireless communication system according to an exemplary embodiment;

[0064] Figure 2A This is a flowchart illustrating an information processing method according to an exemplary embodiment;

[0065] Figure 2B This is a flowchart illustrating an information processing method according to an exemplary embodiment;

[0066] Figure 3A This is a flowchart illustrating an information processing method according to an exemplary embodiment;

[0067] Figure 3B This is a flowchart illustrating an information processing method according to an exemplary embodiment;

[0068] Figure 3C This is a flowchart illustrating an information processing method according to an exemplary embodiment;

[0069] Figure 4A This is a flowchart illustrating an information processing method according to an exemplary embodiment;

[0070] Figure 4B This is a flowchart illustrating an information processing method according to an exemplary embodiment;

[0071] Figure 4C This is a flowchart illustrating an information processing method according to an exemplary embodiment;

[0072] Figure 4D This is a flowchart illustrating an information processing method according to an exemplary embodiment;

[0073] Figure 4E This is a flowchart illustrating an information processing method according to an exemplary embodiment;

[0074] Figure 5 This is a flowchart illustrating an information processing method according to an exemplary embodiment;

[0075] Figure 6 This is a flowchart illustrating an information processing method according to an exemplary embodiment;

[0076] Figure 7 This is a flowchart illustrating an information processing method according to an exemplary embodiment;

[0077] Figure 8 This is a flowchart illustrating an information processing method according to an exemplary embodiment;

[0078] Figure 9 This is a flowchart illustrating an information processing method according to an exemplary embodiment;

[0079] Figure 10 This is a flowchart illustrating an information processing method according to an exemplary embodiment;

[0080] Figure 11A This is a flowchart illustrating an information processing method according to an exemplary embodiment;

[0081] Figure 11B This is a flowchart illustrating an information processing method according to an exemplary embodiment;

[0082] Figure 11C This is a flowchart illustrating an information processing method according to an exemplary embodiment;

[0083] Figure 12A This is a schematic diagram of the structure of a first information processing apparatus according to an exemplary embodiment;

[0084] Figure 12B This is a schematic diagram of the structure of a second information processing apparatus according to an exemplary embodiment;

[0085] Figure 12C This is a schematic diagram of the structure of a third information processing apparatus according to an exemplary embodiment;

[0086] Figure 12D This is a schematic diagram of the structure of a fourth information processing apparatus according to an exemplary embodiment;

[0087] Figure 12E This is a schematic diagram of the structure of a fifth information processing apparatus according to an exemplary embodiment;

[0088] Figure 13 This is a schematic diagram of the structure of a communication device according to an exemplary embodiment. Detailed Implementation

[0089] This disclosure provides an information processing method. In some embodiments, the terms "PIN data processing method" and "information processing method," "communication method," etc., can be used interchangeably; the terms "PIN data processing device" and "information processing device," "communication device," etc., can be used interchangeably; and the terms "information processing system," "communication system," etc., can be used interchangeably.

[0090] This disclosure is not exhaustive, but merely illustrative of some embodiments, and is not intended to limit the scope of protection of this disclosure. Unless otherwise specified, each step in a particular embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a particular embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular embodiment can be arbitrarily interchanged. Furthermore, the optional implementation methods in a particular embodiment can be arbitrarily combined; moreover, the embodiments can be arbitrarily combined, for example, some or all steps of different embodiments can be arbitrarily combined, and a particular embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0091] In each of the disclosed embodiments, unless otherwise specified or in case of logical conflict, the terminology and / or descriptions of the embodiments are consistent and can be referenced by each other. Technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0092] The terminology used in the embodiments of this disclosure is for the purpose of describing particular embodiments only and is not intended to limit the scope of this disclosure.

[0093] In this disclosure, unless otherwise stated, elements expressed in a singular form, such as one, a kind, the, the above, described, the aforementioned, this, etc., can represent one and only one, or one or more, at least one, etc. For example, when using articles such as a, an, the, etc. in translation, the noun following the article can be understood as either a singular expression or a plural expression.

[0094] In the embodiments disclosed herein, "multiple" refers to two or more.

[0095] In some embodiments, the terms at least one of, at least one of, at least one of, one or more, a plurality of, and multiple can be used interchangeably.

[0096] The descriptions such as "at least one of A, B, C...", "A and / or B and / or C...", etc. in the embodiments of this disclosure include the case where any one of A, B, C... exists alone, as well as the case where any combination of any number of A, B, C... exists alone. Each case can exist alone. For example, "at least one of A, B, C" includes the cases of A alone, B alone, C alone, A and B combination, A and C combination, B and C combination, and A and B and C combination. For example, A and / or B includes the cases of A alone, B alone, and combinations of A and B.

[0097] In some embodiments, the description of a situation A and another situation B, or responding to a situation A and another situation B, may include the following technical solutions depending on the situation: executing A regardless of B, i.e., A in some embodiments; executing B regardless of A, i.e., B in some embodiments; selectively executing A and B, i.e., selecting to execute from A and B in some embodiments; and executing both A and B, i.e., A and B in some embodiments. The same applies when there are more branches such as A, B, C, etc.

[0098] The prefixes "first," "second," etc., in the embodiments of this disclosure are merely for distinguishing different descriptive objects and do not impose restrictions on the position, order, priority, quantity, or content of the descriptive objects. The description of the descriptive objects is given in the claims or the context of the embodiments, and the use of prefixes should not constitute unnecessary restrictions. For example, if the descriptive object is a field, the ordinal numbers preceding the fields in "first field" and "second field" do not restrict the position or order between the fields. "First" and "second" do not restrict whether the fields they modify are in the same message, nor do they restrict the order of the first and second fields. Similarly, if the descriptive object is a level, the ordinal numbers preceding the levels in "first level" and "second level" do not restrict the priority between levels. Furthermore, the number of descriptive objects is not limited by ordinal numbers and can be one or more. Taking "first device" as an example, the number of devices can be one or more. In addition, objects modified by different prefixes can be the same or different. For example, if the descriptive object is a device, "first device" and "second device" can be the same device or different devices, and their types can be the same or different. Similarly, if the descriptive object is information, "first information" and "second information" can be the same information or different information, and their content can be the same or different.

[0099] In some embodiments, including A, containing A, for indicating A, carrying A can be interpreted as directly carrying A or indirectly indicating A.

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

[0101] 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 lower than, and above can be used interchangeably, as can 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.

[0102] In some embodiments, devices, etc., can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as device, equipment, circuit, network element, node, function, unit, section, system, network, chip, chip system, entity, and subject can be used interchangeably.

[0103] In some embodiments, the terms access network device (AN device), radio access network device (RAN device), base station (BS), radio base station, fixed station, node, access point, transmission point (TP), reception point (RP), transmission / reception point (TRP), panel, antenna panel, antenna array, cell, macro cell, small cell, femto cell, pico cell, sector, cell group, carrier, component carrier, bandwidth part (BWP), etc., can be used interchangeably.

[0104] In some embodiments, the terms terminal, terminal device, user equipment (UE), user terminal, mobile station (MS), mobile terminal (MT), subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, and client can be used interchangeably.

[0105] In some embodiments, access network devices, core network devices, or network devices can be replaced with terminals. For example, embodiments of this disclosure can also be applied to structures that replace communication between access network devices, core network devices, or network devices and terminals with communication between multiple terminals (e.g., also referred to as device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, the terminal can also be configured to have all or part of the functions of the access network device. Furthermore, terms such as uplink and downlink can be replaced with terms corresponding to inter-terminal communication (e.g., sidelink). For example, uplink channel, downlink channel, etc., can be replaced with sidelink channel, and uplink link, downlink, etc., can be replaced with sidelink link.

[0106] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, core network device, or network device may also be configured to have all or some of the functions of the terminal.

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

[0108] In some embodiments, terms such as uplink, uplink, physical uplink, etc., can be used interchangeably; terms such as downlink, downlink, physical downlink, etc., can be used interchangeably; and terms such as sidelink, sidelink, sidelink communication, sidelink communication, direct connection, direct link, direct communication, direct link communication, direct link communication, etc., can be used interchangeably.

[0109] In some embodiments, terms such as downlink control information (DCI), downlink (DL) assignment, DL DCI, uplink (UL) grant, and ULDCI can be used interchangeably.

[0110] In some embodiments, terms such as Physical Downlink Shared Channel (PDSCH) and DL data can be used interchangeably, as can terms such as Physical Uplink Shared Channel (PUSCH) and UL data. In some embodiments, terms such as radio, wireless, radio access network (RAN), access network (AN), and RAN-based can be used interchangeably.

[0111] In some embodiments, the terms search space, search space set, search space configuration, search space set configuration, control resource set (CORESET), and CORESET configuration can be used interchangeably.

[0112] In some embodiments, the terms synchronization signal (SS), synchronization signal block (SSB), reference signal (RS), pilot, and pilot signal can be used interchangeably.

[0113] In some embodiments, terms such as moment, point in time, time, and time location can be used interchangeably, as can terms such as duration, time period, time window, window, and time.

[0114] In some embodiments, terms such as component carrier (CC), cell, frequency carrier, and carrier frequency can be used interchangeably.

[0115] In some embodiments, the terms resource block (RB), physical resource block (PRB), sub-carrier group (SCG), resource element group (REG), PRB pair, RB pair, and resource element (RE) can be used interchangeably.

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

[0117] In some embodiments, the terms precoding, precoder, weight, precoding weight, quasi-co-location (QCL), transmission configuration indication (TCI) status, spatial relation, spatial domain filter, transmission power, phase rotation, antenna port, antenna port group, layer, the number of layers, rank, resource, resource set, resource group, beam, beam width, beam angular degree, antenna, antenna element, and panel can be used interchangeably.

[0118] In some embodiments, the terms frame, radio frame, subframe, slot, sub-slot, mini-slot, symbol, symbol, and transmission time interval (TTI) can be used interchangeably.

[0119] In some embodiments, the terms "acquire," "get," "obtain," "receive," "transmit," "send," and / or "receive" can be used interchangeably and can be interpreted as receiving from other entities, acquiring from protocols, obtaining through self-processing, or autonomously implementing, among other meanings.

[0120] In some embodiments, terms such as send, report, distribute, transmit, send and / or receive can be used interchangeably.

[0121] In some embodiments, "predetermined" or "preset" can be interpreted as pre-defined in a protocol or the like, or as a device or the like performing a pre-set action.

[0122] In some embodiments, determining can be interpreted as judging, deciding, judging, calculating, computing, processing, deriving, investigating, searching, looking up, searching, querying, ascertaining, receiving, transmitting, inputting, outputting, accessing, resolving, selecting, choosing, establishing, comparing, assuming, expecting, considering, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc., but is not limited to these.

[0123] In some embodiments, the determination or judgment can be made by a value represented by 1 bit (0 or 1), or by a true or false value (boolean), or by a comparison of numerical values ​​(e.g., a comparison with a predetermined value), but is not limited thereto.

[0124] In some embodiments, a network can be interpreted as the devices included in the network (e.g., access network devices, core network devices, etc.).

[0125] 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 receiver to respond to the sent content.

[0126] In some embodiments, the acquisition of data, information, etc., may comply with the laws and regulations of the country where the location is situated.

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

[0128] Furthermore, each element, each row, or each column in the table of this disclosure can be implemented as an independent embodiment, and any combination of any element, any row, or any column can also be implemented as an independent embodiment.

[0129] like Figure 1 As shown, the communication system 100 includes a terminal 101, an access network device 102, and a core network device 103.

[0130] In some embodiments, terminal 101 includes, but is not limited to, at least one of the following: mobile phone, wearable device, Internet of Things device, car with communication function, smart car, tablet computer, computer with wireless transceiver function, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal device in industrial control, wireless terminal device in self-driving, wireless terminal device in remote medical surgery, wireless terminal device in smart grid, wireless terminal device in transportation safety, wireless terminal device in smart city, and wireless terminal device in smart home.

[0131] In some embodiments, the access network device 102 may be a node or device that connects a terminal to a wireless network. The access network device may include at least one of the following in a 5G communication system: an evolved Node B (eNB), a next-generation eNB (ng-eNB), a next-generation Node B (gNB), a node B (NB), a home node B (HNB), a home evolved node B (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 RAN, a cloud RAN, a base station in other communication systems, and an access node in a wireless fidelity (WiFi) system, but is not limited thereto.

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

[0133] In some embodiments, the access network device may be composed of a central unit (CU) and a distributed unit (DU). The CU may also be called a control unit. The CU-DU structure can separate the protocol layer of the access network device. Some of the protocol layer functions are centrally controlled by the CU, while the remaining part or all of the protocol layer functions are distributed in the DU and centrally controlled by the CU. However, this is not the only possibility.

[0134] In some embodiments, the core network device 103 may be a single device, including a first network element 1031, a second network element 1032, etc., or it may be multiple devices or a group of devices, each including all or part of the first network element 1031, the second network element 1032, etc. Network elements 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).

[0135] It is understood that the communication system described in this disclosure is for the purpose of more clearly illustrating the technical solutions of this disclosure, and does not constitute a limitation on the technical solutions provided in this disclosure. As those skilled in the art will know, with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in this disclosure are also applicable to similar technical problems.

[0136] The following embodiments of this disclosure can be applied to Figure 1 The communication system 100 shown, or a part thereof, but not limited to it. Figure 1 The entities shown are illustrative; a communication system may include... Figure 1 All or part of the main body, or may include Figure 1 Other entities besides the main body, the number and form of each entity are arbitrary, the connection relationship between the entities is illustrative, the entities may not be connected or may be connected, and the connection can be in any way, it can be a direct connection or an indirect connection, it can be a wired connection or a wireless connection.

[0137] The embodiments disclosed herein can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G new radio (NR), Future Radio Access (FRA), New-Radio Access Technology (RAT), New Radio (NR), New radio access (NX), Futuregeneration radio access (FX), Global System for Mobile communications (GSM), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), and IEEE 802.20, Ultra-Wideband (UWB), Bluetooth (a registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X) systems, systems utilizing other communication methods, and next-generation systems built upon them, etc. Furthermore, multiple systems can be combined (e.g., a combination of LTE or LTE-A with 5G).

[0138] Figure 1 The first network element 1031 and the second network element 1032 involved in the core network device 103 shown can be different network devices, which can correspond to UDM, UDR and / or PCF in the core network device.

[0139] The third network element 1033 can be a network device located outside the core network, including but not limited to various AFs.

[0140] For example, the PIN can be an Internet of Things (IoT) established with the terminal as the PMEC and connected via the PEMC. Figure 1 The communication system 100 shown.

[0141] PIN management involves determining the type of PINE and configuring the PIN. Network operators and third parties can authorize the creation and management of PINs. After a PIN is created, a PEGC can be added to or removed from the PIN; a regular PINE can be associated with a PEGC, or a regular PINE can be removed from the PIN.

[0142] Figure 2A The present disclosure provides a method for AF to manage PINs, which may include:

[0143] 001. The PIN AF uses a parameter configuration service to provide a PIN policy, which may include a PIN ID policy, a privacy policy, and / or a routing policy. For example, the PIN AF sends the data required to update the policy parameters to the UDM, which stores this data and sends the stored information related to the creation of the PIN policy to the PCF when the PCF creates the PIN policy; the PCF then generates the policy parameters based on the information received from the UDM.

[0144] 002. It can register with the network as a PEMC. The AMF can authorize the UE to act as a PEMC during the registration process.

[0145] 003. If the UE does not have a valid policy for PIN management, then the UE is triggered to initiate policy initialization. Policy initialization here can be understood as policy creation.

[0146] 004. The UE requests a PIN policy from the PCF. For example, the UE can request a PIN policy using the PIN AF identifier.

[0147] 005. The PCF obtains the UE's subscription data and / or other data required to generate the policy from the UDM. For example, it obtains the PIN policy based on the UE's subscription data. This PIN policy may include a PIN ID allocation policy, a privacy policy, a routing policy, etc. The PIN ID allocation policy here may be a policy by which the UDM assigns a first PIN ID to the PIN. For example, this PIN policy is a PIN policy.

[0148] PIN policies may also include: notifying the fifth-generation core network (5G core network). th The Generation Core (5GC) creates a PIN creation indicator. The PCF can provide the PIN policy to the UE through the UE configuration information update process.

[0149] 006. PINE performs PIN discovery and selection, and finally PINE is added to PIN.

[0150] 007. The UE notifies the AMF to establish a PIN, providing the PIN identifier and determining the valid geographic area and valid time of the PIN based on the UE's subscription data. The AMF may provide time- and geographic area-related policy information during this stage.

[0151] It can be seen that in Figure 2A The AF will trigger the PCF to configure the policy for the PIN through a dedicated process. That is, this process only covers the policy generation process.

[0152] Figure 2B The diagram illustrates a method for AF to manage PINs, which may include:

[0153] 010.AF requests a new PIN from UDM via NEF. The request message sent to UDM may include: PIN information and PINE information.

[0154] PIN information may include one or more of the following: PIN ID, PIN name, PIN transaction, PIN validity period, and a list of PINE information.

[0155] PINE information may include: PINE ID, PINE name, PINE type, PINE capability information, services supported by the PIN, services not supported by the PIN, and the PIN's validity period.

[0156] A PIN may include at least one or more PEMCs. A PIN may also include one or more PINEs.

[0157] 020. The UDM creates a PIN based on the AF's request and establishes PIN configuration information. For example, it creates a PIN configuration based on the UE's subscription data and / or PIN information received from the AF. Of course, the PIN parameters in the PIN configuration information can also be generated by the UDM. For example, PIN parameters generated by the UDM may include: internal PIN ID.

[0158] 030. UDM sends a PIN creation response to AF via NEF. This PIN creation response may include: the creation result. If a PIN is created, the response message may also include: PIN information and / or PIN parameters generated by UDM.

[0159] 040. UDM determines that the User Equipment Parameters Update (UPU) procedure is triggered to provide PIN information to the PEMC;

[0160] 050.UDM calls Nudm_SDM_Notification. This Nudm_SDM_Notification includes PIN information.

[0161] 060.UDM provides PIN information to gNB via AMF.

[0162] 070.PEMC updates the PIN information locally based on the parameters received from UDM.

[0163] visible Figure 2B The method shown only covers the PIN creation process. If PIN-related policies are involved, additional processes are required.

[0164] In view of this, embodiments of the present disclosure also provide an information processing method that can create a PIN and create policy data related to the PIN policy in a single process.

[0165] like Figure 3A As shown, this disclosure provides an information processing method executed by a wireless communication system, which may include:

[0166] S3110: A third request message sent by the first type AF to the UDM, the third request message is used to request the creation of a PIN; the third request message includes: the first identification information of the PINE and the first PIN configuration data; the PINE includes at least PEGC.

[0167] S3120: UDM creates a PIN based on the third request message.

[0168] S3130: UDM sends a first request message to UDR; the first request message includes: first identification information of Personal Internet of Things (PINE) and first PINE PIN configuration data; PINE includes at least a Personal Internet of Things (PEGC) with gateway capabilities.

[0169] S3140: The UDR creates policy data based on the first identification information and the first PIN configuration data; wherein, the policy data is used to generate the policy for the PIN.

[0170] S3150: UDR sends a first response message to UDM, wherein the first response message includes: the creation result of policy data.

[0171] S3160: UDM sends a third response message to the first type AF based on the first response message.

[0172] For example, the first type of AF is a kind of AF, and AF can be used for the control of one or more services and / or the provision of service data, etc.

[0173] For example, the first type of AF can be an AF located within the core network. This first type of AF resides in the same trust domain as the UDM and / or UDR. That is, the first type of AF can be an AF trusted by the UDM and / or UDR.

[0174] For example, the first type of AF can be an AF deployed by a telecommunications operator. This AF may belong to the same telecommunications operator as the UDM and / or UDR in the core network, or they may belong to friendly vendors with whom they have established cooperative relationships.

[0175] A PIN includes at least one PEGC; therefore, the first identification information of the PINE carried in the third request message includes at least the first identification information of the PEGC.

[0176] In other embodiments, the PINE indicated by the first identification information carried in the third request message may further include: PEMC and / or normal PINE. The normal PINE may be a PINE other than PEGC and PEMC.

[0177] For example, the first identification information may be simply referred to as the first identification; the first PIN configuration data may be simply referred to as the first configuration.

[0178] The strategy data here can be one type of first data.

[0179] The first response includes first information, which may include one or more bits indicating the creation result of the first data, that is, indicating the creation result of the policy data. This creation result may include: a failure result and a success result.

[0180] In this embodiment of the disclosure, the first type of AF can invoke a parameter provision creation request (Nudm_ParameterProvision_Create request) message based on the Nudm interface or a parameter provision update request (Nudm_ParameterProvision_Update request) based on the Nudm interface to create a PIN. Of course, the parameter provision creation request here is just one example of the aforementioned third request message, and the specific implementation is not limited to this example. The third request message can be any transmissible message between the first type of AF and the UDM.

[0181] Correspondingly, the third response message can be either a Nudm_ParameterProvision_Create response message or a Nudm_ParameterProvision_Update response message.

[0182] The third response message may include second information indicating the PIN creation result. The PIN creation result may include: a result indicating PIN creation failure or a result indicating PIN creation success.

[0183] The first identification information may include any information that can uniquely identify the PINE.

[0184] For example, the first identification information may include, but is not limited to, a Generic Public Subscription Identifier (GPSI). In other embodiments, the first identification information may also be other information that can uniquely identify the device, such as a physical address like the Media Access Control (MAC) address of the communication device, or other communication identifiers bound to the GPSI. Other communication identifiers bound to the GPSI may include instant messaging identifiers and / or email addresses. The instant messaging identifier may include communication identifiers of instant messaging applications such as WeChat, Weibo, QQ, or Facebook.

[0185] The first PIN configuration data may include various configuration data related to PIN creation, PIN-based communication, PIN-based PINE management, and PIN removal.

[0186] For example, the first PIN configuration data may include policy data, which may include data related to routing rules, data related to Quality of Service (QoS) parameters, and / or data related to PIN billing, etc.

[0187] PIN signing data can be various types of data generated when signing a PIN. This signing data may include, but is not limited to, at least one of the following: mobility signing data, used for PIN-based mobility management; session signing data, used for PIN-based session management.

[0188] In some embodiments, mobility subscription data can be used to determine whether a PIN is allowed to move across areas. For example, can a PIN created based on a user's mobile phone remain valid after the phone moves from one Tracking Area (TA) to another? This example of a tracking area is merely an illustration of cross-area movement; in actual implementations, cross-area movement may also involve Public Land Mobile Network (PLMN) related aspects. For example, whether the PIN remains valid when roaming within a PEGC-based PIN movement area, or billing control for PIN-based communications. In some embodiments, the area involved in cross-area movement may also include a specific area determined based on the first PIN configuration data. For example, this specific area may include one or more cells.

[0189] In some embodiments, session subscription data can be used to determine the session type or session parameters that a PIN-subscribed PIN service can use. For example, the session subscription data can be used to determine whether a PINE can initiate a group session based on a PIN. As another example, the session subscription data can be used to determine whether a PIN-initiated session by a PINE within a PIN can use network slicing or is a network slice that can be used.

[0190] In some embodiments, the first PIN configuration data may further include: time information, indicating the valid time for requesting PIN creation; area information, indicating the valid area for requesting PIN creation; and PIN service information, indicating PIN services that are permitted based on PIN communication.

[0191] Within the valid time period, a PINE within a PIN can initiate communication based on the PIN. Within the valid area, a PINE within a PIN can initiate communication based on the PIN.

[0192] The PINE within the PIN can use the PIN to communicate for the PIN-signed services.

[0193] Of course, the above are just examples of the configuration data for the first PIN, and the actual implementation is not limited to this example.

[0194] UDM can be used to create PINs; UDR is used to create policy data for PINs.

[0195] Creating a PIN using a UDM may include: storing the PIN's contractual data; and / or assigning a first PIN identifier to the PIN.

[0196] In some embodiments, after the PIN is created, the UDM sends a first request message to the UDR, or after the UDM completes the PIN creation, it triggers the NEF or AF to send a first request message to the UDR via a third response message.

[0197] In other embodiments, UDM, NEF, or AF can send a first request message to UDR during the PIN creation process, so that UDR will receive the first request message during the PIN creation process. At this time, UDR can synchronously create policy data while UDM is creating the PIN.

[0198] For example, the first request message may also include a first PIN identifier. The first PIN identifier may be an identifier assigned by the UDM during the PIN creation process or after the PIN creation is completed.

[0199] After receiving the third request message, the UDM will determine whether to create a PIN requested by the first type AF or the second type AF.

[0200] UDM can determine whether to create a PIN based on the AF's contracted business and / or the first PIN configuration data involved in the third request message.

[0201] When a PIN is created, the UDM will generate and save the PIN's contractual data, and / or assign a first PIN identifier to the PIN. This first PIN identifier is also known as the internal PIN identifier.

[0202] The first PIN configuration data may include PIN signing data and session signing data.

[0203] For example, the UDM can determine whether a first type of AF has permission to create the PIN based on the first PIN configuration data. If permission is granted, the UDM creates the PIN based on the first PIN configuration data and establishes PIN configuration information. This PIN configuration information may include: the first identification information of the PIN's PEGC, and the PIN configuration obtained based on the first PIN configuration data. This PIN configuration information can be stored in the UDM in the form of a PIN configuration file.

[0204] For example, a certain AF (Automatic Feedback Controller) only supports PIN creation for service A, but the UDM (User Device Manager) determines, based on the first PIN configuration data, that the PIN requested by the first type of AF is for communication of service B. Clearly, in this case, the first type of AF can be considered to lack the authority to create a PIN, and the UDM can refuse PIN creation.

[0205] For example, based on the subscription data of the UE represented by the first identification information of the PEGC, it is determined whether to allow the creation of a PIN using the UE as the PEGC. If the UE's subscription data indicates that it is not allowed to be used as the PEGC, the UDM will refuse to create the PIN, i.e., the PIN creation will fail. If the UE's subscription data indicates that it is allowed to be used as the PEGC, the UDM will create the PIN. In some embodiments, the UE's subscription data can also be used to determine which devices are allowed to join as a PINE based on the PIN created based on the UE. If at least one of the devices indicated by the first identification information carried in the third request message is not included in the list of devices that the UE's subscription data indicates are allowed to join the PIN, the UDM may also refuse to create the PIN.

[0206] For example, the third request message may include a creation indicator. This creation indicator is used by the AF to request the creation of a PIN.

[0207] The above is merely an example of creating a PIN in UDM; the actual implementation is not limited to this example.

[0208] In some embodiments, if the UDM fails to create a PIN, the UDM may directly send a third response message indicating the failure of PIN creation to the first type AF, informing the first type AF that the PIN creation has failed.

[0209] In some embodiments, when creating a PIN, the UDM also assigns a first PIN identifier to the PIN. This first PIN identifier is an identifier that can be recognized by any network device within the wireless communication system. The first PIN identifier may also be referred to as an internal PIN identifier.

[0210] This first PIN identifier will be recorded in the PIN configuration information generated by the UDM. This first PIN identifier can then be used by the PINE within the PIN to communicate using the wireless communication system.

[0211] In some embodiments, the first type of AF can also assign a second PIN identifier to the PIN it requests to create. This second PIN identifier can be a second PIN identifier that is recognizable by the client associated with the service of the first type of AF. If the second type of AF has assigned a second PIN identifier, the third request message can also carry the second PIN identifier. Thus, when the UDM creates a PIN, it also stores the second PIN identifier in the PIN configuration information. Subsequently, the PINE device can initiate PIN-based communication (i.e., PIN communication) based on the second PIN identifier. After receiving such a communication request, the wireless communication network device can convert the second PIN identifier to a first PIN identifier according to the PIN configuration data stored in the UDM and then provide PIN communication services to the PINE.

[0212] After the UDM successfully creates the PIN, it can directly notify the UDR to create policy data. At this point, the UDM can directly send a first request message to the UDR, which includes at least the first identification information of the PEGC and all or part of the first PIN configuration data. For example, the UDM can send the first PIN configuration data related to policy data from a third request message to the UDR. For example, the first PIN configuration data related to routing rules, QoS parameters, and / or accounting can be sent to the UDR.

[0213] In some embodiments, since the UDM successfully creates the PIN, a first PIN identifier is assigned to the PIN, and the first request message may also include: the first PIN identifier of the PIN.

[0214] In other embodiments, the UDM sends a first request message to the UDR during the PIN creation process to create policy data for the PIN being generated. If PIN creation fails, the UDR deletes the policy data after learning of the failure from the UDM.

[0215] For example, the UDM can invoke the Nudr interface-based data management creation request (Nudr_DM_Createrequest) message or the Nudr interface-based data management update request (Nudr_DM_Update request) message to request the UDM to create policy data for the PIN.

[0216] Of course, the parameter provided here is just one example of the first request message mentioned above. The actual implementation is not limited to this example. The third request message can be any transmissible message between UDM and UDR.

[0217] Correspondingly, the first response message can be either a Nudr_DM_Create response message or a Nudr_DM_Update response message.

[0218] This policy data can be used by PCF to generate PIN policies. These PIN policies can then be used to control PIN communication.

[0219] PIN policies may include at least one of the following: routing policies, i.e., routing rules; Quality of Service (QoS) parameters, etc.

[0220] In summary, the PIN policy may include: Policy and Charging Control (PCC) rules related to PIN-based communication, etc.

[0221] The policy data may include: minor control data, which can be used to control the PIN policy of the PCF.

[0222] For example, the policy control data may indicate the bandwidth range used by the PIN, and the PCF may generate a PIN policy based on the bandwidth range used.

[0223] As another example, the policy control data can indicate the range of values ​​for QoS parameters, and the PCF can generate a PIN policy based on the policy control data.

[0224] For example, when creating policy data, the UDR needs to verify whether each PINE is a legitimate device or can register with the device based on the first identification information, or it needs to verify whether the first PIN configuration information matches the subscription data of the UE acting as the PEGC. In short, the UDR can verify whether to create policy data when creating policy data. If the verification passes, the policy data is created; otherwise, the policy data creation is considered to have failed.

[0225] The creation result of strategy data can include: creation successful or creation failed.

[0226] If created successfully, the UDR will store the first identification information, the first PIN identifier, and policy data.

[0227] If creation fails, the UDR will not store the first identification information, the first PIN, and policy data, or the UDR will generate a creation failure record. This creation failure record may store the first identification information and the first PIN configuration data. Furthermore, the creation failure record may also store the reason for the failure, etc.

[0228] The creation result of the policy data can be carried in the first response message and returned to the UDM. The UDM then returns a third response message to the first type AF, thereby notifying the first type AF that the PIN creation failed.

[0229] For example, the third response message may indicate the creation result of the PIN and the creation result of the policy data. In this way, the first type of AF can know the creation results of the PIN and the policy data respectively based on this first response message.

[0230] As another example, the third response message may include: result information indicating success, which may represent both successful creation of the PIN and successful creation of the policy data; or, result information indicating failure, which may indicate that at least one of the PIN and / or policy data failed to be created.

[0231] If the PIN is created successfully, the third response message may also include: the first PIN identifier of the PIN.

[0232] If the policy data is created successfully, the PCF can then obtain the policy data from the UDR and create the PIN policy.

[0233] For example, after the PIN and policy data are successfully obtained, PINE can initiate PIN communication. Upon receiving the PIN communication, PCF can request policy data from UDR using the first PIN identifier carried in the PIN communication request and create a PIN policy.

[0234] For example, after the PIN and policy data are successfully registered, when the PIN's PEGC is registered to the network, the PCF can obtain the first identification information of the PEGC based on the PEGC's registration request, and obtain policy data from the UDR based on the first identification information, thereby creating the PIN policy.

[0235] In some embodiments of this application, if generating policy data fails or is unable to generate policy data, the first response message sent by the UDR to the UDM carries a failure identifier. After receiving the first response message, the UDM regenerates the creation PIN, i.e., it executes step S3120 again. Alternatively, after receiving the first response message, the UDM sends a third response message to the first type AF. After receiving the third response message indicating creation failure, the first type AF executes step S3110 again. Specifically, after determining that generating policy data has failed or is unable to generate a policy, the PCF sends a notification to the UDR, so that the UDR also determines that generating a policy has failed or is unable to generate a policy. At this time, the UDR sends a trigger notification via the NEF or directly to the AF, so that the AF provides information for updating the policy data within the UDR. Related details can be found below. Figure 3B The corresponding textual descriptions will not be repeated here.

[0236] It is worth noting that steps S3120 and S3130 can be executed simultaneously, or S3120 can be executed first and then S3130, or S3130 can be executed first and then S3120.

[0237] In summary, in the embodiments of this disclosure, during the PIN creation process, at least one of UDM, NEF, or AF will trigger the UDR to create policy data. That is, the creation of PIN and policy data can be realized during the PIN creation process. Thus, there is no need for two separate processes to create PIN and policy data separately. Compared with creating PIN and policy data through two separate processes, the creation process can be reduced, signaling overhead can be saved, and the creation operation of AF can be simplified.

[0238] like Figure 3B As shown, this disclosure provides an information processing method executed by a wireless communication system, which may include:

[0239] S3210: A third request message sent by the first type AF to the UDM, the third request message is used to request the creation of a PIN; the third request message includes: the first identification information of the PINE and the first PIN configuration data; the PINE includes at least the element PEGC;

[0240] S3220: UDM creates a PIN based on the third request message;

[0241] S3230: UDM sends a first request message to UDR; the first request message includes: first identification information of Personal Internet of Things (PINE) and first PINE PIN configuration data; PINE includes at least PEGC;

[0242] S3240: The UDR creates policy data based on the first identification information and the first PIN configuration data; wherein, the policy data is used to generate the policy for the PIN;

[0243] S3250: Sends a first response message to the UDM, wherein the first response message includes: the creation result of the policy data;

[0244] S3260: UDM sends a third response message to the first type AF based on the first response message.

[0245] S3370: If the creation result fails, receive a second request message sent by UDM, wherein the second request message includes: second PIN configuration data and / or second identification information of PINE;

[0246] S3380: Recreate policy data for the PIN based on the second PIN configuration data and / or the second identification information.

[0247] It is worth noting that steps S3220 and S3230 can be executed simultaneously, or S3220 can be executed first and then S3230, or S3230 can be executed first and then S3220.

[0248] In this embodiment of the disclosure, if the PIN is created successfully but the policy data creation fails, the UDM will re-obtain the PIN configuration data and / or identification information from the first type of AF. The re-obtained identification information is referred to as the second identification information, and the re-obtained PIN configuration data is referred to as the second PIN configuration data. Here, the second identification information can be abbreviated as the second identifier; the second PIN configuration data can be abbreviated as PIN.

[0249] The reason for the failure to create policy data may be that one or both of the first identification information and the first PIN configuration data are incorrect. The second request message can carry the updated second identification information and / or the second PIN configuration data, so that the UDR can recreate the policy data for the already established PIN based on the second identification information and / or the second PIN configuration data carried in the second request message.

[0250] The descriptions of the second identification information and the second PIN configuration data are the same as or similar to the first identification information and the first PIN configuration data in the foregoing embodiments, and will not be repeated here.

[0251] In this way, the UDR can recreate policy data for the PIN based on the reacquired second PIN configuration data and / or second identification information until the creation is successful.

[0252] In this embodiment, the steps for creating a PIN with the UDM and creating policy data with the UDR can be found in [reference needed]. Figure 3A The embodiments shown will not be repeated here.

[0253] For example, the second request message may include, but is not limited to, a Nudr_DM_Update request message that provides update request data management based on parameters of the Nudr interface. In some embodiments, the second request message may also include an update indicator to distinguish between the creation and updating of policy data. For example, the update indicator may also be referred to as a rebuild indicator or a retransmission indicator.

[0254] If UDM returns a second response message based on the second request message, the second response message may include: a data management update response (Nudr_DM_Update response) message based on the Nudr interface.

[0255] like Figure 3C As shown, this disclosure provides an information processing method executed by a wireless communication system, which may include:

[0256] S3310: A third request message sent by the first type AF to the UDM, the third request message is used to request the creation of a PIN; the third request message includes: the first identification information of the PINE and the first PIN configuration data; the PINE includes at least a PEGC;

[0257] S3320: UDM creates a PIN based on the third request message;

[0258] S3330: UDM sends a PIN creation success response message to Type 1 AF;

[0259] S3340: After receiving the PIN creation success response message, the first type AF sends a first request message to the UDR; the first request message includes: the first identification information of the PINE and the first person IoT PIN configuration data; the PINE includes at least PEGC;

[0260] S3350: The UDR creates policy data based on the first identification information and the first PIN configuration data; wherein, the policy data is used to generate the policy for the PIN;

[0261] S3360: Send a third response message to the first type AF.

[0262] In this embodiment of the disclosure, after the UDM successfully creates the PIN, it directly notifies the first type of AF, so that the first type of AF continues to execute the creation of policy data under this process. At this time, the first type of AF directly sends a first request message to the UDR and directly receives a first response message from the UDR.

[0263] In one embodiment, if the PIN is created successfully but the policy data creation fails, the first type of AF can directly send a second request message to the UDR, wherein the second request message includes: second PIN configuration data and / or second identification information of the PINE;

[0264] Recreate policy data for the PIN based on the second PIN configuration data and / or the second identification information.

[0265] In another embodiment, if the PIN creation is successful but the policy data creation fails, the first type of AF provides the UDM with the second PIN configuration data and / or the second identification information of the PINE;

[0266] The UDM receives the second PIN configuration data and / or the second identification information of the PINE provided by the first type of AF, and updates the locally stored PIN configuration information according to the second PIN configuration data and / or the second identification information of the PINE.

[0267] Optionally, in some embodiments of this disclosure, after the UDM receives the second PIN configuration data and / or the second identification information of the PINE, it sends a second request message to the UDR, wherein the second request message includes: the second PIN configuration data and / or the second identification information of the PINE;

[0268] Optionally, in some embodiments of this disclosure, policy data is recreated for the PIN based on the second PIN configuration data and / or the second identification information.

[0269] Optionally, in some embodiments of this disclosure, in step S3360, the UDR may not send a third response message to the AF, but may instead send a third response message to the UDM. Then, in step S3330, the UDM may add the content of the third response message to the PIN creation success response message. In this embodiment, steps S3340 and S3350 are executed before step S3330.

[0270] In summary, this disclosure provides a method for a first type of AF to request a UDM to create a PIN and a UDR to create policy data through a process, and a method for reconstructing policy data when policy data creation fails. This method is characterized by its simplicity and low signaling overhead.

[0271] It is worth noting that steps S3320 and S3330 can be executed simultaneously, or S3320 can be executed first and then S3330, or S3330 can be executed first and then S3320.

[0272] like Figure 4A As shown, this disclosure provides an information processing method executed by a wireless communication system, which may include:

[0273] S4110: A third request message sent by the second type AF to the NEF; the third request message is used to request the creation of a PIN; the third request message includes: the first identification information of the PINE and the first PIN configuration data; the PINE includes at least a PEGC;

[0274] S4120: NEF forwards or passes through the third request message to UDM;

[0275] S4130: UDM creates a PIN based on the third request message;

[0276] S4140: UDM sends a first request message to UDR; the first request message includes: the first identification information of PINE and the first person IoT PIN configuration data; PINE includes at least PEGC;

[0277] S4150: The UDR creates policy data based on the first identification information and the first PIN configuration data; wherein, the policy data is used to generate the policy for the PIN;

[0278] S4160: Send a first response message to the UDM, wherein the first response message includes: the creation result of the policy data;

[0279] S4170: UDM sends a third response message to NEF based on the first response message;

[0280] S4180: NEF forwards or transparently transmits the third response message to a Type 2 AF.

[0281] The second type of AF can be an AF located outside the trust domain of the UDM and / or UDR, or it can be an AF that is not trusted by the UDM and / or UDR. This second type of AF can be an AF deployed by a third party. The trust domain of the UDM and / or UDR can be the Core Network (CN).

[0282] This type of AF needs to connect to the core network of the wireless communication system via NEF. After receiving the first request message, NEF will perform security filtering and other processing on the first request message. If the security of the first request message is determined, the first request message will be forwarded or transparently transmitted to UDM, where UDM will create a PIN, and UDR will further create policy data.

[0283] The message contents of the first request message, the third request message, the first response message, and the third response message can be found in [reference needed]. Figure 3A The same parts as the illustrated embodiment; and the steps for UDM to create PIN and UDR to create policy data can also be found in the foregoing. Figure 3A The same part shown.

[0284] For example, in this embodiment of the disclosure, the third request message is first provided to the NEF by the second type of AF. At this time, the third request message may be: a creation request message based on the parameters of the Nnef interface (Nnef_ParameterProvision_Createrequest) or a creation update message based on the parameters of the Nnef interface (Nnef_ParameterProvision_Createrequest), requesting the creation of a PIN.

[0285] The third request message may include a creation indicator consisting of one or more bits.

[0286] For example, after NEF receives the third request message from the second type of AF, it will provide a creation request (Nudm_ParameterProvision_Create request) message based on the parameters of the Nudm interface or a creation update (Nudm_ParameterProvision_Create request) message based on the parameters of the Nudm interface, and forward the message content received from the second type of AF to UDM to request UDM to create a PIN and assign a first PIN identifier to the successfully created PIN, that is, assign an internal PIN identifier to the PIN.

[0287] Correspondingly, NEF can invoke either the Nnef_ParameterProvision_Create response message or the Nnef_ParameterProvision_Create reqsponse message based on the parameters of the Nnef interface to interact with the second type of AF. For example, NEF will invoke these two messages to forward or pass through the third response message of the UDM.

[0288] It is worth noting that steps S4120 and S4130 can be executed simultaneously, or S4120 can be executed first and then S4130, or S4130 can be executed first and then S4120.

[0289] In this embodiment of the disclosure, since the second type of AF is located outside the CN, it communicates with the UDM and UDR respectively through the NEF. Both the first type of AF and the second type of AF are AFs, that is, the AF can communicate with the UDM and UDR through the NEF, or it can communicate with the UDM and UDR without the NEF.

[0290] like Figure 4B As shown, this disclosure provides an information processing method executed by a wireless communication system, which may include:

[0291] S4210: A third request message sent by the second type of application function AF to NEF; the third request message is used to request the creation of a PIN; the third request message includes: the first identification information of the PINE and the first PIN configuration data; the PINE includes at least PEGC;

[0292] S4220: NEF forwards or passes through the third request message to UDM;

[0293] S4230: UDM creates a PIN based on the third request message;

[0294] S4240: UDM sends a first request message to UDR; the first request message includes: first identification information of PINE and first PIN configuration data; PINE includes at least PEGC;

[0295] S4250: The UDR creates policy data based on the first identification information and the first PIN configuration data; wherein, the policy data is used to generate the policy for the PIN;

[0296] S4260: Send a first response message to the UDM, wherein the first response message includes: the creation result of the policy data;

[0297] S4270: UDM sends a third response message to NEF based on the first response message;

[0298] S4280: NEF forwards or transparently transmits third response messages to Type 2 AF;

[0299] S4290: In the event that policy data creation fails, the NEF receives a second request message sent by the second type of AF; wherein the second request message includes: second PIN configuration data and / or second identification information of the PINE;

[0300] S4300: NEF will send the second request message directly to the UDR or through the UDM to the UDR;

[0301] S4310: The UDR recreates policy data for the PIN based on the second PIN configuration data and / or the second identification information.

[0302] The message contents of the first request message, the third request message, the first response message, and the third response message can be found in [reference needed]. Figure 3A The same parts as the illustrated embodiment; and the steps for UDM to create PIN and UDR to create policy data can also be found in the foregoing. Figure 3A The same part shown.

[0303] In this embodiment, not only is the creation of the PIN and the initial creation of the policy data realized in one process, but also the reconstruction of the policy data can be achieved through a second request message when the initial creation of the policy data fails, until the creation of the policy data is successful.

[0304] It is worth noting that steps S4220 and S4230 can be executed simultaneously, or S4220 can be executed first and then S4230, or S4230 can be executed first and then S4220.

[0305] like Figure 4C As shown, this disclosure provides an information processing method executed by a wireless communication system, which may include:

[0306] S4410: A third request message sent by the second type AF to the NEF; the third request message is used to request the creation of a PIN; the third request message includes: the first identification information of the PINE and the first PIN configuration data; the PINE includes at least a PEGC;

[0307] S4420: NEF forwards or passes through the third request message to UDM;

[0308] S4430: UDM creates a PIN based on the third request message;

[0309] S4440: UDM sends a third response message to NEF; the third response message includes: the result of PIN creation;

[0310] S4450: After NEF determines that the PIN has been successfully created based on the third response message, it sends a first request message to UDR; the first request message includes: the first identification information of the PINE and the first PIN configuration data; the PINE includes at least PEGC;

[0311] S4460: The UDR creates policy data based on the first identification information and the first PIN configuration data; wherein, the policy data is used to generate the policy for the PIN;

[0312] S4470: UDR sends a first response message to NEF, wherein the first response message includes: the creation result of policy data;

[0313] S4280: NEF sends a third response message to Type 2 AF.

[0314] In this embodiment of the disclosure, after the UDM successfully creates the PIN, it directly sends a third response message to the NEF. The NF then determines, based on the third response message, whether to send a first request message to the UDR requesting the creation of policy data.

[0315] For example, when a third response message indicates that PIN creation has failed, the NEF can directly send a third response message indicating failure to the second type of AF. This third response message may indicate that both PIN and policy data creation have failed, or it may indicate PIN creation failure alone, or it may indicate failure alone without specifying whether it is PIN creation failure or policy data creation failure.

[0316] In this embodiment of the disclosure, if the first response message indicates that the policy data has been created successfully, the NEF sends a third response message indicating successful creation to the second type AF, and the creation process of the PIN and policy data ends.

[0317] The message contents of the first request message, the third request message, the first response message, and the third response message can be found in [reference needed]. Figure 3A The same parts as the illustrated embodiment; and the steps for UDM to create PIN and UDR to create policy data can also be found in the foregoing. Figure 3A The same part shown.

[0318] like Figure 4D As shown, this disclosure provides an information processing method executed by a wireless communication system, which may include:

[0319] S4510: A third request message sent by the second type of application function AF to NEF; the third request message is used to request the creation of a PIN; the third request message includes: the first identification information of the PINE and the first PIN configuration data; the PINE includes at least PEGC;

[0320] S4520: NEF forwards or passes through the third request message to UDM;

[0321] S4530: UDM creates a PIN based on the third request message;

[0322] S4540: UDM sends a third response message to NEF; the third response message includes: the result of PIN creation;

[0323] S4550: After NEF confirms that the PIN has been successfully created based on the third response message, it sends a first request message to UDR; the first request message includes: the first identification information of the PINE and the first PIN configuration data; the PINE includes at least PEGC;

[0324] S4560: The UDR creates policy data based on the first identification information and the first PIN configuration data; wherein, the policy data is used to generate the policy for the PIN.

[0325] S4570: UDR sends a first response message to NEF, wherein the first response message includes: the creation result of policy data;

[0326] S4580: NEF sends a third response message to Type 2 AF.

[0327] S4590: In the event that policy data creation fails, the NEF receives a second request message sent by the second type of AF; wherein the second request message includes: second PIN configuration data and / or second identification information of the PINE;

[0328] S4600: NEF sends a second request message directly to the UDR or through the UDM to the UDR;

[0329] S4610: The UDR recreates policy data for the PIN based on the second PIN configuration data and / or the second identification information.

[0330] In this embodiment, the creation of the PIN and the initial creation of the policy data are achieved in one step during the PIN creation process. Moreover, if the initial creation of the policy data fails, the policy data can be rebuilt through a second request message until the creation of the policy data is successful.

[0331] The message contents of the first request message, the second request message, the third request message, the first response message, and the third response message can be found in [reference needed]. Figure 3A The same parts as the illustrated embodiment; and the steps for UDM to create PIN and UDR to create policy data can also be found in the foregoing. Figure 3A The same part shown.

[0332] like Figure 4EAs shown, this disclosure provides an information processing method executed by a wireless communication system, which may include:

[0333] S4710: A third request message sent by the second type AF to the NEF; the third request message is used to request the creation of a PIN; the third request message includes: the first identification information of the PINE and the first PIN configuration data; the PINE includes at least a PEGC;

[0334] S4720: NEF forwards or passes through the third request message to UDM;

[0335] S4730: UDM creates a PIN based on the third request message;

[0336] S4740: UDM sends a third response message to NEF; the third response message includes: the result of PIN creation;

[0337] S4750: NEF forwards or transparently transmits to Type 2 AF based on the third response message;

[0338] S4760: After the Type II AF determines that the PIN has been successfully created based on the third response message, it sends a first request message to the NEF; the first request message includes: the first identification information of the PINE and the first PIN configuration data; the PINE includes at least PEGC;

[0339] S4770: NEF sends a first request message directly to UDR, or sends a request message to UDR through UDM;

[0340] S4780: UDR sends a first response message to NEF, wherein the first response message includes: the creation result of policy data;

[0341] S4790: The NEF forwards or passes through the first response message to the Type 2 AF;

[0342] S4800: The second type of AF, based on the first response message, determines that the policy data creation has failed and sends a second request message to the NEF; wherein, the second request message includes: second PIN configuration data and / or second identification information of the PINE;

[0343] S4810: NEF sends a second request message directly to the UDR or through the UDM to the UDR;

[0344] S4820: The UDR recreates policy data for the PIN based on the second PIN configuration data and / or the second identification information.

[0345] In this embodiment, NEF can serve as a forwarding device or a transparent transmission device for the second type of AF and UDM and / or UDR.

[0346] The message contents of the first request message, the second request message, the third request message, the first response message, and the third response message can be found in [reference needed]. Figure 3A The same parts as the illustrated embodiment; and the steps for UDM to create PIN and UDR to create policy data can also be found in the foregoing. Figure 3A The same part shown.

[0347] In some cases, in combination with the above Figures 3A to 3C , Figures 4A to 4D If any of the following occurs: if the UDR creates policy data for the PIN based on the second request message, it will send the second request message to the NEF, UDM, or Type 1 AF, and return a second response message. This second response message may include the result of the policy data reconstruction. This reconstruction result can be a success or failure.

[0348] If the reconstruction result is a failure, the first type AF and / or the second type AF can continue to update one or both of the PIN configuration data and / or identification information, and continue to request PIN reconstruction until successful.

[0349] If the reconstruction is successful, the creation process is complete.

[0350] like Figure 5 As shown, this disclosure provides an information processing method, which is executed by a first network device, and the method further includes:

[0351] S5110: Receive a first request message, wherein the first request message includes: first identification information of the PINE and first PIN configuration data; the PINE includes at least a PEGC;

[0352] S5120: Create policy data based on the first identification information and the first PIN configuration data; wherein, the policy data is the policy used to generate the PIN.

[0353] For example, the first network device may be a UDR.

[0354] The specific content and function of the first request message, the first identification information, the first PIN configuration data, and the policy data can be found in any of the foregoing embodiments.

[0355] For a description of the UDR creating policy data based on the first request message, please refer to any of the foregoing embodiments; it will not be repeated here.

[0356] In this way, the UDR will also participate in the creation of policy data during the PIN creation process, thus realizing the creation of PIN and policy data in one process.

[0357] In some embodiments, the first request message is received by the first network device after the PIN is successfully created, or the first request message is received by the first network device after the first PIN identifier of the PIN is successfully assigned.

[0358] In some embodiments, receiving a first request message includes at least one of the following: receiving a first request message sent by a second network device; receiving a first request message sent by a third network device; or receiving a first request message sent by a first type of application function (AF).

[0359] In some embodiments, receiving a first request message includes at least one of the following: receiving a first request message sent by a second network device after creating a PIN; receiving a first request message sent by a third network device after being notified by the second network device that the PIN creation is complete; or receiving a first request message sent by a first type of application function AF after being notified that the PIN creation is complete.

[0360] For example, the second network device may be a PIN creation device. The second network device may also be a core network device. For example, the second network device may be a UDM.

[0361] The third network device can also be a core network device; for example, the third network device can be a NEF.

[0362] The first type of AF can be an AF deployed within the trust domain of the first network device, or an AF with the same home user as the first network device, or an AF that mutually authenticates and trusts with the first network device.

[0363] For example, a third network device receives a third request message sent by a second type of AF. The third request message includes: first identification information of a Personal Internet of Things (PINE) and first PINE PIN configuration data; the PINE includes at least a Personal Internet of Things (PEGC) with gateway capabilities. The third request message is used to request the creation of a PIN.

[0364] After receiving the third request message, the third network device forwards or transparently transmits the third request message to the second network device. The second network device creates a PIN based on the third request message. After receiving the third response message containing the PIN creation result, the third network device can send a first request message to the first network device when the third response message indicates that the PIN creation was successful.

[0365] The second network device creates a PIN based on the third request message. After the PIN is successfully created, the second network device will also send a first request message to the first network device.

[0366] Alternatively, after receiving the third response message forwarded or transparently transmitted by the third network device, the second type AF determines that the PIN has been successfully created based on the third response message, and then sends a first request message to the first network device through the third network device, or the second type AF sends a first request message to the first network device through both the third network device and the second network device at the same time.

[0367] This disclosure provides an information processing method, which is executed by a first network device, and the method further includes:

[0368] Receive a first request message, wherein the first request message includes: first identification information of PINE and first PIN configuration data; PINE includes at least a basic PEGC; create policy data based on the first identification information and the first PIN configuration data; wherein the policy data is a policy for generating PINs.

[0369] Send a first response message, which includes the creation result of the policy data.

[0370] The specific meaning of this strategy data can be found in the aforementioned embodiments, and will not be repeated here.

[0371] The creation result of this strategy data can be either successful or failed.

[0372] This disclosure provides an information processing method, which is executed by a first network device, and the method further includes:

[0373] Receive a first request message, wherein the first request message includes: first identification information of PINE and first PIN configuration data; PINE includes at least PEGC; create policy data based on the first identification information and first PIN configuration data; wherein the policy data is a policy for generating PINs.

[0374] If the creation fails, a second request message is received, wherein the second request message includes: second PIN configuration data and / or second identification information of the PINE;

[0375] Recreate policy data for the PIN based on the second PIN configuration data and / or the second identification information.

[0376] If the previous policy data creation failed, the UDM can reconstruct the PIN policy data based on the received second request message. For details, please refer to any of the foregoing embodiments; they will not be repeated here.

[0377] For example, if the creation fails, a second request message is received, including at least one of the following:

[0378] In the event that policy data creation fails, a second request message is received from the second network device that created the PIN; wherein the second request message sent by the second network device includes: second PIN configuration data and / or second identification information from the second type AF;

[0379] In the event that policy data creation fails, a second request message is received from a third network device; wherein the second request message sent by the third network device includes: second PIN configuration data and / or second identification information from a second type of AF;

[0380] If the creation of policy data fails, the UDR receives a second request message from the first type of AF, wherein the second request message packet contains: second PIN configuration information and second identification information from the first type of AF.

[0381] like Figure 6 As shown, this disclosure provides an information processing method, which is executed by a second network device, and the method further includes:

[0382] S6110: Receive a third request message, wherein the third request message is used to request the creation of a PIN; the third request message includes: first identification information of the PINE and first PIN configuration data; the PINE includes at least a PEGC;

[0383] S6120: Create a PIN based on the third request message;

[0384] S6130: Based on the PIN creation result, send a third response message; wherein the third response message includes: the PIN creation result;

[0385] S6140: Send a first request message, wherein the first request message includes first identification information and first PIN configuration data; wherein the first request message is used to request the creation of policy data; the policy data is used to generate a policy for the PIN.

[0386] The second network device can be a UDM. The UDM can receive a third response message, so that if the PIN is successfully created, the second network device can send a first request message to the UDR to request the creation of the PIN policy data.

[0387] If the third response message indicates that PIN creation failed, the UDM can simply send the third response message. PIN creation failure may be due to the AF not having permission to request PIN creation, not having permission to create a PIN of the specified type, or errors in the first identification information and / or first PIN configuration data requested for PIN creation. In these cases, simply indicating PIN creation failure via the third response message is sufficient. If the AF wants to recreate the PIN, it should re-initiate the PIN creation process.

[0388] In some cases, if the UDM successfully creates the PIN, it indicates that the probability of the PIN policy data creation failing due to the first PIN configuration data and / or the first identification information is low. In such cases, the UDM or NEF can directly send a first request message to the UDR, which defaults to the UDR's successful policy data creation. In this scenario, the UDR may not send a first response message, and therefore the UDM and / or NEF do not need to receive a first response message. In this situation, the UDM can directly send a third response message to the AF, or the NEF can send a third response message to the AF.

[0389] It is worth noting that the message content of the third request message, the first request message, the third request message, and the third request message in this embodiment can all refer to the foregoing embodiments, and will not be repeated here.

[0390] In some embodiments, sending a first request message by the UDM may include: the UDM sending a first request message to the UDR upon successful PIN creation, or sending a first request message to the UDR during the PIN creation process.

[0391] This disclosure provides an information processing method, which is executed by a second network device, and the method further includes:

[0392] Receive a third request message, wherein the third request message is used to request the creation of a PIN; the third request message includes: the first identification information of the PINE and the first PIN configuration data; the PINE includes at least a PEGC;

[0393] Create a PIN based on the third request message;

[0394] Based on the PIN creation result, a third response message is sent; wherein the third response message includes: the PIN creation result;

[0395] Send a first request message, wherein the first request message contains first identification information and first PIN configuration data; wherein the first request message is used to request the creation of policy data; the policy data is used to generate a policy for the PIN.

[0396] Receive the first response message, which includes: the creation result of the policy data;

[0397] The first response message is sent to a first type AF; or, the first response message is sent to a third network device, wherein the first response message is used by the third network device to send to a second type AF.

[0398] If PIN creation by the UDM fails, a third response message indicating PIN creation failure is sent directly to the NEF or a Type 1 AF. The third response message can be forwarded by the NEF or transparently transmitted to a Type 2 AF.

[0399] If the UDM successfully creates the PIN, it will send a first request message to the UDR and receive a first response message from the UDR. If the NEF receives the first response message, it can send it directly to the first type AF or directly to the second type AF through the NEF.

[0400] In one embodiment, sending a first request message may include sending a first request message upon successful PIN creation.

[0401] This disclosure provides an information processing method, which is executed by a second network device, and the method further includes:

[0402] Receive a third request message, wherein the third request message is used to request the creation of a PIN; the third request message includes: the first identification information of the PINE and the first PIN configuration data; the PINE includes at least a PEGC;

[0403] Create a PIN based on the third request message;

[0404] Based on the PIN creation result, a third response message is sent; wherein the third response message includes: the PIN creation result;

[0405] Send a first request message, wherein the first request message contains first identification information and first PIN configuration data; wherein the first request message is used to request the creation of policy data; the policy data is used to generate a policy for the PIN.

[0406] Receive the first response message, which includes: the creation result of the policy data;

[0407] The first response message is sent to a first type AF; or, the first response message is sent to a third network device, wherein the first response message is used by the third network device to send to a second type AF.

[0408] In the event that the creation of policy data fails, a fourth request message is received, wherein the fourth request message includes: PINE's second identification information and / or second configuration;

[0409] According to the fourth request message, a second request message is sent; wherein the second request message includes second identification information and / or second PIN configuration data, which is used by the first network device to recreate policy data for the PIN.

[0410] In this embodiment, the UDM sends the first response message to the NEF or directly to the first type of AF. If the creation of the policy data fails, the UDM or NEF may receive a fourth request message. The fourth request message includes the updated second identification information and second PIN configuration information from the first or second type of AF. Based on the fourth request message, a second request message is sent to the network device such as the UDR that created the policy data, thereby triggering the reconstruction of the PIN policy data.

[0411] In some embodiments, if the creation of policy data fails, a fourth request message is received, including:

[0412] In the event that the creation of policy data fails, the second network device receives a fourth request message sent by the third network device or the first type of AF;

[0413] Based on the fourth request message, send the second request message, including:

[0414] Based on the fourth request message, a second request message is sent to the first network device.

[0415] The third network device can be a NEF, and the third network device can forward or pass through the fourth request image message of the second type AF.

[0416] like Figure 7 As shown, this disclosure provides an information processing method, which is executed by a third network device, and the method further includes:

[0417] S7110: Receives a first response message, wherein the first response message includes: the creation result of the PIN policy data;

[0418] S7120: Send the first response message.

[0419] The third network device can be a NEF (Network Adapter). The NEF can be the connection interface between the core network's internal network and the core network's external network.

[0420] The first response message may come from the network device that created the policy data, such as a UDR.

[0421] After receiving the first response message, NEF will forward the first response message, making it convenient for network devices that need to receive the first response message to receive it.

[0422] For example, the third network device receives the first response message sent by the UDR and forwards or passes the first response message to the second type AF.

[0423] As another example, the third network device receives the first response message forwarded or transparently transmitted by the UDM, and forwards or transparently transmits the first response message to the second type AF.

[0424] This disclosure provides an information processing method, which is executed by a third network device, and the method further includes:

[0425] Receive the first response message, which includes: the creation result of the PIN policy data;

[0426] Send the first response message.

[0427] Receive a fourth request message, wherein the fourth request message is sent in the case of policy data creation, and the fourth request message includes: second identification information and / or second configuration of PEGC;

[0428] Send a second request message, wherein the second request message includes: second identification information and / or second PIN configuration data; wherein the second request message is used by the first network device to recreate policy data for the PIN.

[0429] If the first response message indicates that the policy data creation failed, the third network device will receive a fourth request message, which may include the second identification information and the second PIN configuration data required to recreate the policy data.

[0430] For example, NEF receives a fourth message from a second type of AF.

[0431] For example, after receiving the fourth response message, NEF forwards or transparently transmits the second request message to the UDR that created the policy data.

[0432] In some embodiments, receiving a first response message includes: receiving a first response message sent by a first network device or a second network device;

[0433] And / or, send a first response message, including: sending a first response message to a type 2 AF;

[0434] And / or, receive a fourth request message, including: receiving a fourth request message sent by a second type of AF;

[0435] And / or, send a second request message, including: sending a second request message to the first network device.

[0436] like Figure 8 As shown in the figure, an information processing method according to an embodiment of this disclosure, wherein the method is executed by a first type of AF, the method comprising:

[0437] S8110: Send a first request message, which includes: first identification information of the PINE and first PIN configuration data; the PINE includes at least a PEGC; and policy data for requesting the creation of a PIN.

[0438] S8120: Receive first response message;

[0439] S8130: If the first response message indicates that the creation of the PIN policy data has failed, a second request message is sent; wherein the second request message includes: the second identification information of the PINE and / or the second PIN configuration data; wherein the second request message is used to request the re-creation of the PIN policy data; wherein the policy data is used to generate the PIN policy.

[0440] The first type of AF can be an AF deployed within the core network. For example, the first type of AF can be an AF deployed by a telecommunications operator.

[0441] For example, the first type of AF may send a first request message to the UDR or UDM.

[0442] For example, the first type of AF may receive the first response message directly from the UDR, or receive the first response message forwarded or transparently transmitted from the UDR by the UDM. The first response message at least indicates the creation result of the PIN's policy data.

[0443] For example, the second request message may be sent to the NEF and forwarded or transparently transmitted by the NEF to the UDM and / or UDR.

[0444] In some embodiments, sending a first request message includes: sending a first request message to a first network device;

[0445] And / or, receiving a first response message, including: receiving a first response message sent by a first network device; wherein the first network device is used to create policy data for a PIN.

[0446] The first network device can be a UDR.

[0447] For example, sending a first request message includes: sending a first request message to a second network device;

[0448] And / or, receiving a first response message, including: receiving a first response message sent by a second network device; wherein the second network device is used to create a PIN and to forward a first request message to the second network device; the second network device is used to create policy data for the PIN.

[0449] The second network device can be a UDM. In this case, the first request message can be forwarded from the second network device to the first network device.

[0450] In some embodiments, the method further includes, before sending the first request message:

[0451] Send a third request message, wherein the third request message is used to request the creation of a PIN; the third request message includes: first identification information of the PINE and first PIN configuration data; the PINE includes at least a Personal Internet of Things Element (PEGC) with gateway capabilities;

[0452] Receive a third response message, which includes the result of PIN creation.

[0453] For example, a Type 1 AF can send a third request message to a second network device. This third request message is used to request the creation of a PIN. This third request message can be sent before the first request message.

[0454] The third response message can indicate the result of PIN creation.

[0455] In another embodiment, the third response message may include the creation result of the PIN and policy data.

[0456] For example, sending a third request message includes: sending a third request message to a second network device;

[0457] Receiving a third response message includes receiving a third response message sent by a second network device.

[0458] like Figure 9 As shown, this disclosure provides an information processing method, which is executed by a second type of AF, and the method includes:

[0459] S9110: Send a first request message, the first request message including: first identification information of PINE and first PIN configuration data; PINE includes at least PEGC; wherein, the first request message is used to request policy data for creating PIN;

[0460] S9120: Receive the first response message; wherein the first response message includes: the creation result of the PIN policy data;

[0461] S9130: If the first response message indicates that the policy data creation of the PIN has failed, a second request message is sent; wherein the second request message includes: the second identification information of the PINE and / or the second PIN configuration data; wherein the second request message is used to request the first network device to recreate the policy data of the PIN; wherein the policy data is used to generate the policy of the PIN; the second type AF is located outside the trust domain of the first network device.

[0462] The second type of application service (AF) can be an AF deployed by a third party, such as an application server deployed by the application's service provider.

[0463] The information content and / or functions of the first request message, the first response message, and the second request message can be found in any of the foregoing embodiments, and will not be repeated here.

[0464] In some embodiments, sending a first request message includes: sending a first request message to a third network device, wherein the first request message is forwarded or transparently transmitted by the third network device to the first network device; and / or receiving a first response message includes: receiving a first response message forwarded or transparently transmitted by the third network device.

[0465] In some embodiments, the method further includes, before sending the first request message:

[0466] Send a third request message, wherein the third request message is used to request the creation of a PIN; the third request message includes: first identification information of the PINE and first PIN configuration data; the PINE includes at least a Personal Internet of Things Element (PEGC) with gateway capabilities;

[0467] Receive a third response message, which includes the result of PIN creation.

[0468] The third request message can be sent from the second type of AF to the NEF, and then sent from the NEF to the UDR, etc.

[0469] For example, sending a third request message includes: sending a third request message to a third network device, wherein the third request message is forwarded or transparently transmitted by the third network device to the second network device that created the PIN;

[0470] And / or, receive a third response message, including: receive a third response message forwarded or transparently transmitted by a third network device.

[0471] like Figure 10 As shown in the embodiments of this disclosure, an information processing method is provided, wherein the method is executed by a core network device, and the method includes:

[0472] S0110: Receive a first request message; the first request message includes: first identification information of a Personal Internet of Things (PINE) and first PINE PIN configuration data; the PINE includes at least a Personal Internet of Things (PEGC) with gateway capabilities;

[0473] S0120: Based on the first request message, create the PIN policy data;

[0474] S0130: Send a first response message, wherein the first response message includes: the creation result of the policy data.

[0475] The core network equipment can be any network device, network element, or network function located within the CN.

[0476] For the steps of creating a PIN, please refer to the steps of creating a PIN using UDM in any of the foregoing embodiments.

[0477] In some embodiments, the first request message includes: a first network device receiving a first request message sent by a second network device or a third network device or a first type of application function (AF);

[0478] And / or, based on the first request message, create policy data for the PIN, including: the first network device creating policy data for the PIN based on the first request message;

[0479] And / or, sending a first response message, including: the first network device sending a first response message to the second network device or the third network device or the first type AF.

[0480] In some embodiments, the method further includes:

[0481] The third network device will pass through or forward the first response message to the second type of application function (AF).

[0482] In some embodiments, the method further includes:

[0483] The second network device forwards or transparently transmits the first response message to the third network device.

[0484] This disclosure provides an information processing method, executed by a communication system, the method comprising:

[0485] A first network device receives a first request message; the first request message includes: first identification information of the PINE and first PIN configuration data; the PINE includes at least a PEGC;

[0486] Based on the first request message, create the PIN policy data;

[0487] Send a first response message to a second network device or a third network device, wherein the first response message includes: the creation result of policy data; wherein the first response message received by the second network device is forwarded or transparently transmitted to the third network device, and the first response message is forwarded or transparently transmitted by the third network device to the second type AF.

[0488] In some embodiments, the first request message includes: the first network device receiving a first request message sent by the second network device or the third network device; and / or, sending a first response message includes: the first network device sending a first response message to the second network device or the third network device.

[0489] In other embodiments, the third network device receives a first request message sent by the second type of AF and forwards or transmits the first request message to the first network device. And / or the third network device receives a first response message and forwards or transmits the first response message to the second type of AF.

[0490] In some embodiments, the method further includes: a second network device receiving a third request message, the third request message including first identification information and first PIN configuration data; the third request message is used to request a PIN.

[0491] The third request message may include a PIN creation indicator, which can be used to request the creation of a PIN.

[0492] The method of creating PINs based on an authorized third party involves assigning PIN parameters by a UDM and storing PIN policies and PIN signing data.

[0493] Assuming that when AF decides to create a PIN, it determines the GPSIs of PEGC / PINE / PEMC, as well as the PIN configuration data consisting of PIN policy control data and PIN signing data.

[0494] like Figure 11A As shown in the embodiments of this disclosure, an information processing method is provided, which may include:

[0495] 1. AF calls the Nnef_ParameterProvision_Create request to send an external PIN identifier, GPSI(s), a PIN creation indicator, and PIN configuration data to NEF.

[0496] PIN configuration data includes:

[0497] Policy data, including routing rules, QoS parameters, etc.;

[0498] PIN signing data, including mobility signing data and / or session signing data, etc.

[0499] 2. NEF calls the Nudm_ParameterProvision_Create request to UDM, including the external PIN identifier, PIN creation indicator, GPSI(s), and PIN configuration data, in order to create a PIN for UDM.

[0500] 3. Upon receiving the creation instruction, the UDM assigns an internal PIN identifier to the PIN and associates it with the external PIN identifier and GPSI(s). This creation instruction indicates a request to create a PIN.

[0501] 4. UDM calls the Nudm_ParameterProvision_Create response and sends the result to NEF.

[0502] 5. NEF sends the result to AF by calling the Nnef_ParameterProvision_Create response.

[0503] 6. Once a PIN is created, when the AF decides to provide the PIN's policy data to the UDR via NEF, the AF calls the Nnef_ParameterProvision_Create or Nnef_ParameterProvision_update request, which may include the GPSI and the PIN's policy data.

[0504] 7. NEF calls the UDR to request Nudr_DM_Create or Nudr_DM_update, which includes PINpolicy control data and GPSI(s).

[0505] 8. The UDR uses the requested GPSI to create or update the policy data for the corresponding UE's PIN, and calls the Nudr_DM_Create response to send the result to the NEF.

[0506] 9. NEF sends the results to AF.

[0507] like Figure 11B As shown in the embodiments of this disclosure, an information processing method is provided, which may include:

[0508] 1. The AF calls the Nnef_ParameterProvision_Create request (external PIN identifier, GPSI(s), used for PIN creation indicator, PIN configuration data). GPSI(s) is the identifier of the PIN's PEGC, peemc, or PINE sent from the AF.

[0509] PIN configuration data includes:

[0510] Policy data, including routing rules, QoS parameters, etc.;

[0511] PIN signing data includes mobile signing data, session signing data, etc.

[0512] 2. NEF calls the Nudm_ParameterProvision_Create request to UDM, including the external PIN identifier, PIN creation indicator, GPSI(s), and PIN configuration data, in order to create a PIN for UDM.

[0513] 3. When the UDM receives the for PIN creation instruction, it assigns an internal PIN identifier to the PIN and associates it with the external PIN identifier and GPSI(s).

[0514] 4. UDM calls the Nudm_ParameterProvision_Create response to send the result to NEF.

[0515] 5. NEF directly calls Nudr_DM_Create to request the creation of PIN policy data for the UE(s) corresponding to the received GPSI.

[0516] 6. The UDR uses the requested GPSI to create or update the policy data for the corresponding UE's PIN, and calls the Nudr_DM_Create response to send the result to the NEF.

[0517] 7. NEF sends the results to AF.

[0518] like Figure 11C As shown in the embodiments of this disclosure, an information processing method is provided, which may include:

[0519] 1. The AF calls the Nnef_ParameterProvision_Create request (external PIN identifier, GPSI(s), used for PIN creation indicator, PIN configuration data). GPSI(s) is the identifier of the PIN's PEGC, PEMC, or PINE sent from the AF.

[0520] PIN configuration data includes:

[0521] Policy data, including routing rules, QoS parameters, etc.;

[0522] PIN signing data includes mobile signing data, session signing data, etc.

[0523] 2. NEF calls the Nudm_ParameterProvision_Create request to UDM, including the external PIN identifier, PIN creation indicator, GPSI(s), and PIN configuration data, in order to create a PIN for UDM.

[0524] 3. When the UDM receives the for PIN creation instruction, it assigns an internal PIN identifier to the PIN and associates it with the external PIN identifier and GPSI(s).

[0525] 4. The UDM calls either the Nudr_DM_Create request or the Nudr_DM_Update request to the UDR to create policy data for the PIN of the UE for which GPSI was requested.

[0526] 5. UDR sends the result to UDM by calling the Nudr_DM_Create or Nudr_DM_Update response.

[0527] 6. UDM calls the Nudm_ParameterProvision_Create response to send the result to NEF.

[0528] 7. NEF sends the result to AF by calling the Nnef_ParameterProvision_Create response.

[0529] This disclosure provides an information processing method that may include:

[0530] When the AF decides to create a PIN, it sends a PIN creation request to the NEF. This PIN creation request may include an external PINID, an optional list of PINEs (which may include device information for ordinary PINEs, PEGCs, and / or PEMCs), and / or optional PIN configuration data. This PIN creation request may be one of the aforementioned third request messages. For example, the third request message may also include instructions for creation.

[0531] For example, the PINE list may include device information such as device capability information and / or type information. The PIN configuration data may include various configuration data when a communication device acts as a PINE, such as, but not limited to, the role information of the communication device acting as a PINE, the effective time information of acting as a PINE, and / or the effective area information of acting as a PINE. The role information indicates whether the PINE is a regular PINE, a PEMC, or a PEGC. The effective time information indicates the time range during which the communication device acts as a PINE. The effective area information indicates the effective range of the communication device acting as a PINE. For example, if the communication device is outside the effective time and / or effective area, it will no longer act as a PINE.

[0532] The NEF sends the received external PIN ID, PEGC list, and PIN configuration data to the UDM.

[0533] UDM creates a unique internal PIN ID based on the external PIN ID and establishes a one-to-one mapping between the internal PIN ID and the external PIN ID. It also includes a list of PINEs, which can be device information for PINEs such as PINE, PEGC, and / or PEMC.

[0534] The UDM sends a PIN context to the UDR, including the internal PIN ID, external PIN ID, a list of PINEs (which can be PINE, PEGC, or pecc), and PIN configuration data. This PIN context may include a PIN profile.

[0535] UDM sends a PIN creation response to AF via NEF, including the response result.

[0536] Internal PIN IDs are uniquely identifiable in 5G networks. The specification phase will determine whether PIN IDs are defined as external PIN identifiers similar to external group identifiers and GPSI, and as 5G internal PIN identifiers similar to internal group identifiers.

[0537] However, a third-party assigned PIN ID is not guaranteed to be unique in 5GC. Therefore, it may be necessary to add a unique and identifiable PIN ID in 5GC, which is related to the third-party assigned PIN ID.

[0538] like Figure 12A As shown, this disclosure provides a first information processing apparatus, wherein the apparatus further includes:

[0539] The first receiving module 110 is configured to receive a first request message, wherein the first request message includes: first identification information of the PINE and first human IoT PIN configuration data; the PINE includes at least a Personal IoT Element PEGC with gateway capability; the first creation module 120 is configured to create policy data based on the first identification information and the first PIN configuration data; wherein the policy data is a policy for generating PINs.

[0540] The information processing device may be a first network device, which may be a UDR or the like.

[0541] For example, the first receiving module 110 and the first creating module 120 can be program modules that can perform the above operations after being executed by the processor.

[0542] In other embodiments, the first receiving module 110 and the first creating module 120 may be hardware-software hybrid modules, which may include, but are not limited to, various programmable arrays. These programmable arrays include, but are not limited to, field-programmable arrays and / or complex programmable arrays.

[0543] In some embodiments, the first receiving module 110 and the first creating module 120 may be pure hardware modules, which may include, but are not limited to, application-specific integrated circuits.

[0544] In some embodiments, the first receiving module 110 is configured to perform at least one of the following:

[0545] Receive the first request message sent by the second network device;

[0546] Receive the first request message sent by the third network device;

[0547] Receive the first request message sent by the first type of application function (AF).

[0548] In some embodiments, the first sending module is configured to send a first response message, wherein the first response message includes: the creation result of the policy data.

[0549] In some embodiments, the first receiving module 110 is configured to receive a second request message if the creation result fails, wherein the second request message includes: second PIN configuration data and / or second identification information of the PINE;

[0550] The first creation module 120 is also configured to recreate policy data for the PIN based on the second PIN configuration data and / or the second identification information.

[0551] In some embodiments, the first receiving module 110 is further configured to perform at least one of the following:

[0552] In the event that PIN policy control creation fails, a second request message is received from the second network device that created the PIN; wherein the second request message sent by the second network device includes: second PIN configuration data and / or second identification information from the second type AF;

[0553] In the event that PIN policy control creation fails, a second request message is received from a third network device; wherein the second request message sent by the third network device includes: second PIN configuration data and / or second identification information from a second type AF;

[0554] If the creation result fails, a second request message from the first type AF is received, wherein the second request message packet contains: second PIN information and second identification information from the first type AF.

[0555] like Figure 12B As shown, this disclosure provides a second information processing apparatus, wherein the apparatus further includes:

[0556] The second receiving module 210 is configured to receive a third request message, wherein the third request message is used to request the creation of a Personal Internet of Things (PINE); the third request message includes: first identification information and first PIN configuration data of a Personal Internet of Things (PINE); the PINE includes at least a Personal Internet of Things (PEGC) with gateway capabilities;

[0557] The second creation module 220 is configured to create a PIN based on a third request message;

[0558] The second sending module 230 is configured to send a third response message based on the PIN creation result; wherein the third response message includes: the PIN creation result;

[0559] The second sending module 230 is configured to send a first request message when the PIN is successfully created, wherein the first request message includes first identification information and first PIN configuration data; wherein the first request message is used to request creation policy data; the policy data is used to generate the PIN policy.

[0560] The information processing device may be a second network device, and the first network device may be a UDM, etc.

[0561] For example, the second receiving module 210, the second creating module 220, and the second sending module 230 can be program modules that can perform the above operations after being executed by the processor.

[0562] In other embodiments, the second receiving module 210, the second creating module 220, and the second sending module 230 may be hardware-software hybrid modules, which may include, but are not limited to, various programmable arrays. These programmable arrays include, but are not limited to, field-programmable arrays and / or complex programmable arrays.

[0563] In some embodiments, the second receiving module 210, the second creating module 220, and the second sending module 230 may be pure hardware modules, which may include, but are not limited to, application-specific integrated circuits.

[0564] Understandably, the second receiving module 210 is also configured to receive a first response message, wherein the first response message includes: the creation result of the policy data;

[0565] The second sending module 230 is configured to send a first response message to a first type of AF; or to send a first response message to a third network device, wherein the first response message is used by the third network device to send to a second type of application function.

[0566] Understandably, the second receiving module 210 is also configured to receive a fourth request message in the event that the creation of policy data fails, wherein the fourth request message includes: the second identification information and / or the second configuration of PINE;

[0567] The second sending module 230 is further configured to send a second request message according to the fourth request message; wherein the second request message includes second identification information and / or second PIN configuration data, for the first network device to recreate policy data for the PIN.

[0568] Understandably, the second receiving module 210 is also configured to receive a fourth request message sent by a third network device or a first type of AF in the event that the creation of policy data fails.

[0569] The second sending module 230 is also configured to send a second request message to the first network device in accordance with the fourth request message.

[0570] like Figure 12C As shown, this disclosure provides a third information processing apparatus, wherein the apparatus further includes:

[0571] The third receiving module 310 is configured to receive a first response message, wherein the first response message includes: the creation result of the policy data of the personal IoT PIN;

[0572] The third sending module 320 is configured to send the first response message.

[0573] The information processing device may be a third network device. The third network device may be NEF.

[0574] For example, the third receiving module 310 and the third sending module 320 can be program modules that can perform the above operations after being executed by the processor.

[0575] In other embodiments, the third receiving module 310 and the third transmitting module 320 may be hardware-software hybrid modules, which may include, but are not limited to, various programmable arrays. These programmable arrays include, but are not limited to, field-programmable arrays and / or complex programmable arrays.

[0576] In some embodiments, the third receiving module 310 and the third transmitting module 320 may be pure hardware modules, which may include, but are not limited to, application-specific integrated circuits.

[0577] Understandably, the third receiving module 310 is configured to receive a fourth request message, wherein the fourth request message is sent in the event of policy data creation, and the fourth request message includes: second identification information and / or second configuration of a Personal Internet of Things Element (PEGC) with gateway capabilities;

[0578] The third sending module 320 is configured to send a second request message, wherein the second request message includes: second identification information and / or second PIN configuration data; wherein the second request message is used by the first network device to recreate policy data for the PIN.

[0579] Understandably, the third receiving module 310 is configured to receive a first response message sent by the first network device or the second network device;

[0580] And / or, the third sending module 320 is configured to send a first response message to the second type of AF;

[0581] And / or, the third receiving module 310 is configured to receive a fourth request message sent by the second type of AF;

[0582] And / or, the third sending module 320 is configured to send a second request message to the first network device.

[0583] like Figure 12D As shown, this disclosure provides a fourth information processing apparatus, wherein the apparatus includes:

[0584] The fourth sending module 410 is configured to send a first request message, which includes: first identification information of a Personal Internet of Things (PINE) and first PINE PIN configuration data; the PINE includes at least a Personal Internet of Things (PEGC) with gateway capabilities; wherein the first request message is used to request policy data for creating a PIN;

[0585] The fourth receiving module 420 is configured to receive a first response message; wherein the first response message includes: the creation result of the PIN policy data;

[0586] The fourth sending module 410 is configured to send a second request message if the first response message indicates that the creation of the PIN policy data has failed; wherein the second request message includes: the second identification information of the PINE and / or the second PIN configuration data; wherein the second request message is used to request the re-creation of the PIN policy data; wherein the policy data is used to generate the PIN policy.

[0587] The information processing device may be a type I AF. This type I AF may be deployed within the core network. For example, this type I AF may be an AF deployed by an operator.

[0588] In some embodiments, the fourth sending module 410 and the fourth receiving module 420 may be program modules, which can perform the above operations after being executed by the processor.

[0589] In other embodiments, the fourth transmitting module 410 and the fourth receiving module 420 may be hardware-software hybrid modules, which may include, but are not limited to, various programmable arrays. These programmable arrays include, but are not limited to, field-programmable arrays and / or complex programmable arrays.

[0590] In some embodiments, the fourth transmitting module 410 and the fourth receiving module 420 may be pure hardware modules, which may include, but are not limited to, application-specific integrated circuits.

[0591] Understandably, the fourth sending module is configured to send a first request message to the first network device;

[0592] And / or, a fourth receiving module is configured to receive a first response message sent by a first network device; wherein the first network device is used to create policy data for a PIN.

[0593] Understandably, the fourth sending module is configured to send a first request message to the second network device;

[0594] And / or, the fourth receiving module is configured to receive a first response message sent by the second network device; wherein the second network device is used to create a PIN and to forward the first request message to the second network device; the second network device is used to create policy data for the PIN.

[0595] Understandably, before sending the first request message, the fourth sending module is also configured to send a third request message, wherein the third request message is used to request the creation of a PIN; the third request message includes: the first identification information of the PINE and the first PIN configuration data; the PINE includes at least a Personal Internet of Things Element (PEGC) with gateway capabilities;

[0596] Receive a third response message, which includes the result of PIN creation.

[0597] Understandably, the fourth sending module is configured to send a third request message to the second network device;

[0598] The fourth receiving module is configured to receive the third response message sent by the second network device.

[0599] like Figure 12E As shown, this disclosure provides a fifth information processing apparatus, wherein the apparatus includes:

[0600] The fifth sending module 510 is configured to send a first request message, which includes: first identification information of a Personal Internet of Things (PINE) and first PINE PIN configuration data; the PINE includes at least a Personal Internet of Things (PEGC) with gateway capabilities; wherein, the first request message is used to request policy data for creating a PIN;

[0601] The fifth receiving module 520 is configured to receive a first response message; wherein the first response message includes: the creation result of the policy data;

[0602] The fifth sending module 510 is configured to send a second request message if the first response message indicates that the creation of the PIN policy data has failed; wherein the second request message includes: the second identification information of the PINE and / or the second PIN configuration data; wherein the second request message is used to request the first network device to recreate the PIN policy data; wherein the policy data is used to generate the policy for the PIN; and the second type AF is located outside the trust domain of the first network device.

[0603] The information processing device may be a Class II AF.

[0604] In some embodiments, the fifth transmitting module and the fifth receiving module may be program modules, which, after being executed by the processor, can perform the above operations.

[0605] In other embodiments, the fifth transmitting module and the fifth receiving module may be hardware-software hybrid modules, which may include, but are not limited to, various programmable arrays. These programmable arrays include, but are not limited to, field-programmable arrays and / or complex programmable arrays.

[0606] In some embodiments, the fifth transmitting module and the fifth receiving module may be pure hardware modules, which may include, but are not limited to, application-specific integrated circuits.

[0607] This disclosure provides a communication system, which includes: a first network device; the system further includes: a second network device and / or a third network device;

[0608] A first network device is configured to receive a first request message; the first request message includes: first identification information of a Personal Internet of Things (PINE) and first PINE PIN configuration data; the PINE includes at least a Personal Internet of Things (PEGC) with gateway capabilities; based on the first request message, policy data for creating the PIN is created; a first response message is sent to a second network device or a third network device, wherein the first response message includes: the creation result of the policy data; wherein the first response message received by the second network device is forwarded or transparently transmitted to the third network device, and the first response message is forwarded or transparently transmitted by the third network device to the second type of application function (AF).

[0609] For example, the first network device may be a UDR; the second network device may be a UDM.

[0610] In addition to UDR and UDM, the communication system may also include at least one AF. The AF may be a type I AF or a type II AF.

[0611] For example, if the communication system includes a second type of AF, the communication system may also include a third network device. The third network device may be a NEF.

[0612] This disclosure provides a communication device, including:

[0613] Memory used to store processor-executable instructions;

[0614] The processor is connected to the memory.

[0615] The processor is configured to execute the information processing method provided by any of the aforementioned technical solutions.

[0616] The processor may include various types of storage media, which are non-transitory computer storage media that can continue to store information after the communication device loses power.

[0617] Here, the communication equipment includes: UE or network element, which can be any one of the aforementioned first to fourth network elements.

[0618] The processor can connect to memory via a bus or similar means to read executable programs stored in memory, as shown in Figure 4. Figure 9 At least one of the methods shown.

[0619] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory including instructions that can be executed by a processor to generate the above-described method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0620] like Figure 13 As shown in the illustration, one embodiment of this disclosure illustrates the structure of a network device. For example, the network device 900 can be provided as a network-side device. The communication device can be various network elements such as the aforementioned access network elements and / or network functions.

[0621] Reference Figure 13 The network device 900 includes a processing component 922, which further includes one or more processors, and memory resources represented by a memory 932 for storing instructions executable by the processing component 922, such as application programs. The application programs stored in the memory 932 may include one or more modules, each corresponding to a set of instructions. Furthermore, the processing component 922 is configured to execute instructions to perform any of the methods described above applied to the access device, for example, as shown in Figures 4 to 5. Figure 9 Any of the methods shown.

[0622] Network device 900 may also include a power supply component 926 configured to perform power management of network device 900, a wired or wireless network interface 950 configured to connect network device 900 to a network, and an input / output (I / O) interface 958. Network device 900 can operate on an operating system stored in memory 932, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, or similar.

[0623] It should be understood that the division of units or modules in the above device is only a logical functional division. In actual implementation, they can be fully or partially integrated into a single physical entity, or they can be physically separated. Furthermore, the units or modules in the device can be implemented by a processor calling software: for example, the device includes a processor connected to a memory containing instructions. The processor calls the instructions stored in the memory to implement any of the above methods or to implement the functions of the units or modules in the above device. The processor can be, for example, a general-purpose processor, such as a Central Processing Unit (CPU) or a microprocessor, and the memory can be internal or external to the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits. The functionality of some or all of the units or modules can be achieved through the design of these hardware circuits, which can be understood as one or more processors. For example, in one implementation, the hardware circuit is an application-specific integrated circuit (ASIC). The functionality of some or all of the units or modules is achieved through the design of the logical relationships between the components within the circuit. In another implementation, the hardware circuit can be implemented using a programmable logic device (PLD). Taking a field-programmable gate array (FPGA) as an example, it can include a large number of logic gates. The connection relationships between the logic gates are configured through configuration files, thereby achieving the functionality of some or all of the units or modules. All units or modules of the above device can be implemented entirely through processor-called software, entirely through hardware circuits, or partially through processor-called software with the remaining parts implemented through hardware circuits.

[0624] In this disclosure, the processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction read and execute capabilities, such as a Central Processing Unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a type of microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the aforementioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and configuring the hardware circuit can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be 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.

[0625] Unless otherwise specified, each step in a particular implementation or embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, the solution after removing some steps in a particular implementation or embodiment can also be implemented as an independent embodiment, and the order of the steps in a particular implementation or embodiment can be arbitrarily interchanged. In addition, the optional methods or examples in a particular implementation or embodiment can be arbitrarily combined. Furthermore, the implementations or embodiments can be arbitrarily combined with each other. For example, some or all of the steps in different implementations or embodiments can be arbitrarily combined, and a particular implementation or embodiment can be arbitrarily combined with the optional methods or examples of other implementations or embodiments.

[0626] Other embodiments of the present disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the embodiments of this disclosure that follow the general principles of the embodiments of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of the embodiments of this disclosure are indicated by the following claims.

[0627] It should be understood that the embodiments disclosed herein are not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from their scope. The scope of the embodiments disclosed herein is limited only by the appended claims.

Claims

1. An information processing method, wherein, Performed by a first network device, wherein the method includes: A first request message is received, wherein the first request message includes: a first identifier and a first configuration, the first identifier being used to identify a Personal Internet of Things Element (PINE), the first configuration being used to configure a PIN, and the PINE including: a Personal Internet of Things Element with Gateway Capability (PEGC); the first request message is received after the second network device successfully creates the PIN; Based on the first identifier and the first configuration, first data for determining the personal IoT PIN is determined, wherein the first data is data of the strategy for generating the PIN.

2. The method according to claim 1, wherein, The first request message is sent by the second network device, the third network device, or the first type of application function.

3. The method according to claim 1 or 2, wherein, The method further includes: Send a first response message, wherein the first response message includes first information, the first information indicating the creation result of the first data.

4. The method according to claim 3, wherein, The method further includes: Receive a second request message, wherein the first data creation failed; the second request message includes: a second configuration and / or a second identifier; The first data is recreated for the PIN based on the second configuration and / or the second identifier.

5. The method according to claim 4, wherein, The second request message is sent by a second network device, a third network device, or a first type AF.

6. An information processing method, wherein, Performed by a second network device, wherein the method includes: Receive a third request message, wherein the third request message includes a first identifier and a first configuration, the first identifier is used to identify a Personal Internet of Things Element (PINE), the first configuration is used to configure a PIN, and the PINE includes: a Personal Internet of Things Element (PEGC) with gateway capabilities; Create a PIN based on the third request message; Send a third response message; wherein the third response message includes second information; the second information indicates the creation result of the PIN; Send a first request message, wherein the first request message includes a first identifier and a first configuration; the first identifier and the first configuration are used to create first data; the first data is data of the strategy for generating the PIN; wherein the first request message is sent after the PIN is successfully created.

7. The method according to claim 6, wherein, The method further includes: Receive a first response message, wherein the first response message includes second information; the second information indicates the creation result of the first data; The first response message is sent to the first type of AF or the third network device.

8. The method according to claim 7, wherein, The method further includes: Receive a fourth request message, wherein the first data creation failed, and the fourth request message includes: a second identifier and / or a second configuration; According to the fourth request message, a second request message is sent; wherein the second request message includes a second identifier and / or a second configuration, for requesting the first network device to recreate the first data for the PIN.

9. The method according to claim 8, wherein, The fourth request message is sent by the third network device or the first type of AF.

10. An information processing method, wherein, Performed by a third network device, wherein the method includes: Receive a first response message, wherein the first response message includes first information; the first information indicates the creation result of the first data of the personal IoT PIN; Send the first response message; The first response message is sent by the first network device in response to the received first request message, which is sent by the second network device after successfully creating the PIN.

11. The method according to claim 10, wherein, The method includes: Receive a fourth request message, wherein the first data creation failed, and the fourth request message includes a second identifier and / or a second configuration. Send a second request message, wherein the second request message includes: the second identifier and / or the second configuration; wherein the second request message is used to recreate the first data.

12. An information processing method, wherein, Performed by a first type of AF, the method includes: Send a first request message, wherein the first request message includes: a first identifier and a first configuration, the first identifier being used to identify a Personal Internet of Things Element (PINE), the first configuration being used to configure a PIN, and the PINE including: a Personal Internet of Things Element (PEGC) with gateway capabilities; Receive a first response message; wherein the first response message includes first information; the first information is the creation result of the first data of the personal IoT PIN; the first response message is sent by the first network device in response to the received first request message, and the first request message is sent by the second network device after the PIN is successfully created; Send a second request message; wherein, if the first data creation fails, the second request message includes: a second identifier and / or a second configuration; wherein, the second request message is used to request the re-creation of the first data; wherein, the first data is used for the strategy of generating the PIN.

13. The method according to claim 12, wherein, Before sending the first request message, the method further includes: Send a third request message, wherein the third request message includes the first identifier and the first configuration, for requesting the creation of a PIN; Receive a third response message, wherein the third response message includes second information; the second information indicates the creation result of the PIN.

14. An information processing method, wherein, Performed by a second type of AF, the method includes: Send a first request message, the first request message including: a first identifier and a first configuration, the first identifier being used to identify a Personal Internet of Things Element (PINE), the first configuration being used to configure a PIN, the PINE including: a Personal Internet of Things Element (PEGC) with gateway capabilities; Receive a first response message; wherein the first response message includes first information; the first information indicates the creation result of first data of a personal IoT PIN; the first response message is sent by a first network device in response to a received first request message, the first request message being sent by a second network device after the PIN has been successfully created; Send a second request message; wherein, if the first data creation fails, the second request message includes: a second identifier and / or a second configuration; wherein, the second request message is used to request the first network device to recreate the second data; wherein, policy data is used to generate the policy for the PIN; the second type of AF is located outside the trust domain of the first network device.

15. The method according to claim 14, wherein, Before sending the first request message, the method further includes: Send a third request message, wherein the third request message is used to request the creation of a PIN; the third request message includes: the first identifier and the first configuration; the PINE includes at least a Personal Internet of Things Element (PEGC) with gateway capabilities; Receive a third response message, wherein the third response message includes second information; the second information indicates the creation result of the PIN.

16. An information processing method, wherein, Performed by core network equipment, the method includes: A first request message is received; the first request message includes: a first identifier and a first configuration, the first identifier being used to identify a Personal Internet of Things Element (PINE), the first configuration being used to configure a PIN, the PINE including: a Personal Internet of Things Element with gateway capabilities (PEGC); the first request message is received after the PIN has been successfully created; Based on the first request message, create the first data for the PIN; Send a first response message, wherein the first response message includes: the creation result of the first data.

17. An information processing method, wherein, Performed by a communication system, the method includes: A first network device receives a first request message; the first request message includes: a first identifier and a first configuration, the first identifier being used to identify a Personal Internet of Things Element (PINE), the first configuration being used to configure a PIN, the PINE including: a Personal Internet of Things Element with gateway capabilities (PEGC); the first request message is received after a second network device successfully creates the PIN; The first network device creates the first data for the personal IoT PIN; The first network device sends a first response message to the second network device, the third network device, or the first type of application function, wherein the first response message includes first information: the first information indicates the creation result of the first data; the first response message is forwarded or transparently transmitted by the third network device to the second type of application function AF.

18. A first information processing apparatus, wherein, The device includes: A first receiving module is configured to receive a first request message, wherein the first request message includes: a first identifier and a first configuration, the first identifier being used to identify a Personal Internet of Things Element (PINE), and the first configuration being used to configure a PIN, the PINE including: a Personal Internet of Things Element with Gateway Capability (PEGC); the first request message is received after the second network device successfully creates the PIN; The first creation module is configured to determine first data of a personal IoT PIN based on the first identifier and the first configuration, wherein the first data is data of a strategy for generating the PIN.

19. A second information processing apparatus, wherein, The device includes: The second receiving module is configured to receive a third request message, wherein the third request message includes a first identifier and a first configuration, the first identifier being used to identify a Personal Internet of Things Element (PINE), and the first configuration being used to configure a PIN, wherein the PINE includes a Personal Internet of Things Element (PEGC) with gateway capabilities. The second creation module is configured to create a PIN based on the third request message; The second sending module is configured to send a third response message based on the creation result of the PIN; wherein the third response message includes second information; the second information indicates the creation result of the PIN; The second sending module is configured to send a first request message, wherein the first request message includes a first identifier and a first configuration; the first identifier and the first configuration are used to create first data; the first data is data of the strategy for generating the PIN; wherein the first request message is sent after the PIN is successfully created.

20. A third information processing apparatus, wherein, The device includes: The third receiving module is configured to receive a first response message, wherein the first response message includes first information; the first information indicates the creation result of the first data of the personal IoT PIN; The third sending module is configured to send the first response message; wherein the first response message is sent by the first network device in response to a received first request message, and the first request message is sent by the second network device after successfully creating the PIN.

21. A fourth information processing device, wherein, The device includes: The fourth sending module is configured to send a first request message, wherein the first request message includes: a first identifier and a first configuration, the first identifier being used to identify a Personal Internet of Things Element (PINE), the first configuration being used to configure a PIN, and the PINE including: a Personal Internet of Things Element (PEGC) with gateway capabilities; The fourth receiving module is configured to receive a first response message; wherein the first response message includes first information; the first information is the creation result of the first data of the personal IoT PIN; the first response message is sent by the first network device in response to the received first request message, and the first request message is sent by the second network device after the PIN is successfully created; The fourth sending module is configured to send a second request message; wherein, if the first data creation fails, the second request message includes: a second identifier and / or a second configuration; wherein, the second request message is used to request the re-creation of the first data; wherein, the first data is used for the strategy of generating the PIN.

22. A fifth information processing device, wherein, The device includes: The fifth sending module is configured to send a first request message, the first request message including: a first identifier and a first configuration, the first identifier being used to identify a Personal Internet of Things Element (PINE), the first configuration being used to configure a PIN, the PINE including: a Personal Internet of Things Element (PEGC) with gateway capabilities; The fifth receiving module is configured to receive a first response message; wherein the first response message includes first information; the first information indicates the creation result of the first data of the personal IoT PIN; the first response message is sent by the first network device in response to the received first request message, and the first request message is sent by the second network device after the PIN is successfully created; The fifth sending module is configured to send a second request message; wherein, if the first data creation fails, the second request message includes: a second identifier and / or a second configuration; wherein, the second request message is used to request the first network device to recreate the second data; wherein, policy data is used to generate the policy for the PIN; the second type of AF is located outside the trust domain of the first network device.

23. A communication system, wherein, The system includes: a first network device; the system further includes: a second network device and / or a third network device; The first network device is configured to receive a first request message; the first request message includes: a first identifier and a first configuration, the first identifier being used to identify a Personal Internet of Things Element (PINE), the first configuration being used to configure a PIN, the PINE including: a Personal Internet of Things Element with Gateway Capability (PEGC), the first request message being received after the second network device successfully creates the PIN; determining first data of the Personal Internet of Things PIN based on the first identifier and the first configuration, the first data being data of a strategy for generating the PIN; sending a first response message to the second network device or a third network device, wherein the first response message includes first information; the first information indicating the creation result of the first data; wherein the first response message received by the second network device is sent to the third network device, and the first response message is sent by the third network device to a second type of application function (AF).

24. A communication device, comprising a processor, a transceiver, a memory, and an executable program stored in the memory and executable by the processor, wherein, When the processor runs the executable program, it performs the information processing method provided as claimed in any one of claims 1 to 5, 6 to 9, 10 to 11, 12 to 13, 14 to 15, 16 and 17.

25. A computer storage medium storing an executable program; the executable program, when executed by a processor, is capable of implementing the information processing method provided in any one of claims 1 to 5, 6 to 9, 10 to 11, 12 to 13, 14 to 15, 16 and 17.

Images