Information processing method and apparatus, information transmission method and apparatus, and related device

Obtain gateway information through the PIN server to determine whether there are available gateway functions in the PIN, which solves the problem that the device cannot communicate normally due to lack of gateway functions, and realizes the reliability of communication.

WO2024235037A1PCT designated stage expired Publication Date: 2024-11-21VIVO MOBILE COMM CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/091301
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-12
Filing Date
2024-05-07
Publication Date
2024-11-21

AI Technical Summary

Technical Problem

In a personal IoT network, if there is no suitable PIN element as the PIN element of the gateway function, the PIN server may indicate that the PIN element that does not have the gateway function as the gateway, causing the device to be unable to route data or communication normally.

Method used

The PIN server obtains information related to the PIN network element with gateway function to determine whether there is an available gateway function. If it does not exist, it refuses to establish a PIN or deactivate the PIN. If it exists, it indicates an available gateway function to ensure that the device can route normally. Data or communication.

Benefits of technology

It effectively reduces the probability that devices cannot route data or communication normally due to lack of gateway functions, and ensures the reliability of communication.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024091301_21112024_PF_FP_ABST
    Figure CN2024091301_21112024_PF_FP_ABST
Patent Text Reader

Abstract

The present application belongs to the technical field of communications. Disclosed are an information processing method and apparatus, an information transmission method and apparatus, and a related device. The information processing method in the embodiments of the present application comprises: a personal IoT network (PIN) server receiving first information, wherein the first information satisfies at least one of the following: the first information being related to a PIN element (PINE) with gateway capability (PEGC), and the first information comprising a first request, which is used for requesting the establishment of a PIN; and the PIN server executing a first operation according to the first information, wherein the first operation comprises at least one of the following: determining PEGC information in the PIN, rejecting the first request, deactivating the PIN, updating PINE information of the PEGC in the PIN, and sending second information to a PINE with management capability (PEMC), the second information being used for indicating the PINE accepted as the PEGC in the PIN, or the second information indicating the acceptance of the first request.
Need to check novelty before this filing date? Find Prior Art

Description

Information processing method, information transmission method, device and related equipment

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese patent application No. 202310543097.X filed in China on May 12, 2023, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present application belongs to the field of communication technology, and specifically relates to an information processing method, an information transmission method, an apparatus and related equipment. Background Art

[0004] In a personal IoT network (PIN), a PIN element with management capability (PEMC) is needed to manage the PIN, and a PIN element with gateway capability (PEGC) is needed to provide data routing or communication for devices in the PIN.

[0005] However, in some cases, there will be no PEGC in the PIN. For example, when PEMC is creating a PIN, if there is no suitable PIN element (PINE) that can serve as the PEGC in the PIN, the PIN server will indicate a PEMC that may not have the relevant functions of PEGC or other PINE that does not have PEGC capabilities as the PEGC, which will cause the devices in the PIN to be unable to route data or communicate normally due to the lack of PEGC.

[0006] Summary of the Invention

[0007] The embodiments of the present application provide an information processing method, an information transmission method, an apparatus and related equipment, so that a PIN server can obtain first information related to a PIN network element PEGC with a gateway function, and then determine whether there is an available PEGC in a specific PIN based on the first information. If not, the request to establish the PIN can be rejected or the PIN can be deactivated; if it exists, the PECG can be indicated for the PIN in a targeted manner, thereby reducing the probability that the device in the PIN cannot route data or communicate normally due to the lack of PEGC.

[0008] In a first aspect, an information processing method is provided, the method comprising:

[0009] The personal Internet of Things PIN server receives first information, where the first information satisfies at least one of the following:

[0010] The first information is related to a PIN element PEGC having gateway capability;

[0011] The first information includes a first request, and the first request is used to request to establish a PIN;

[0012] The PIN server performs a first operation according to the first information, wherein the first operation includes at least one of the following:

[0013] Determine the PEGC information in the PIN;

[0014] rejecting the first request;

[0015] Deactivate PIN;

[0016] Update the personal Internet of Things network element PINE information of PEGC in PIN;

[0017] Sending second information to the PIN element PEMC with management function, wherein the second information is used to indicate that the PINE as PEGC is accepted in the PIN, or the second information indicates acceptance of the first request.

[0018] In a second aspect, an information transmission method is provided, the method comprising:

[0019] The PEMC sends the first information to the PIN server;

[0020] Wherein, the first information includes at least one of the following:

[0021] The first identification information is used to identify the PINE that does not accept becoming a PEGC in the PIN;

[0022] Second identification information is used to identify the PEMC, and the PEMC does not have a gateway capability;

[0023] First indication information, used to indicate that the PIN established by the PEMC is in a deactivated state or that there is no available PEGC in the PIN;

[0024] Second indication information, used to indicate that the PINE corresponding to the first identification information does not accept becoming a PEGC in a PIN, or that the PEMC corresponding to the second identification information does not have a gateway capability;

[0025] A first request is used to request to establish a PIN.

[0026] In a third aspect, a method for transmitting information is provided, the method comprising:

[0027] PINE sends a first message to the PIN server;

[0028] The first information includes at least one of the following:

[0029] The third indication information is used to indicate whether the PINE has a gateway capability or not;

[0030] Fourth indication information, used to instruct the PINE to accept or reject being a PEGC in the PIN;

[0031] Parameter information of the PINE.

[0032] In a fourth aspect, an information processing device is provided, comprising:

[0033] The first receiving module is configured to receive first information, wherein the first information satisfies at least one of the following:

[0034] The first information is related to a PIN element PEGC having gateway capability;

[0035] The first information includes a first request, and the first request is used to request to establish a PIN;

[0036] A first execution module is configured to perform a first operation according to the first information, wherein the first operation includes at least one of the following:

[0037] Determine the PEGC information in the PIN;

[0038] rejecting the first request;

[0039] Deactivate PIN;

[0040] Update the personal Internet of Things network element PINE information of PEGC in PIN;

[0041] Sending second information to the PIN element PEMC with management function, wherein the second information is used to indicate that the PINE as PEGC is accepted in the PIN, or the second information indicates acceptance of the first request.

[0042] In a fifth aspect, an information transmission device is provided, comprising:

[0043] A first sending module, configured to send first information to a PIN server;

[0044] Wherein, the first information includes at least one of the following:

[0045] The first identification information is used to identify the PINE that does not accept becoming a PEGC in the PIN;

[0046] The second identification information is used to identify the PEMC, where the PEMC does not have a gateway capability;

[0047] First indication information, used to indicate that the PIN established by the PEMC is in a deactivated state or that there is no available PEGC in the PIN;

[0048] Second indication information, used to indicate that the PINE corresponding to the first identification information does not accept becoming a PEGC in a PIN, or that the PEMC corresponding to the second identification information does not have a gateway capability;

[0049] A first request is used to request to establish a PIN.

[0050] In a sixth aspect, an information transmission device is provided, comprising:

[0051] A second sending module, configured to send the first information to the PIN server;

[0052] The first information includes at least one of the following:

[0053] The third indication information is used to indicate whether the PINE has a gateway capability or not;

[0054] Fourth indication information, used to instruct PINE to accept or reject as a PEGC in PIN;

[0055] PINE parameter information.

[0056] In the seventh aspect, a terminal is provided, which includes a processor and a memory, wherein the memory stores a program or instruction that can be run on the processor, and when the program or instruction is executed by the processor, the steps of the method described in the second aspect or the third aspect are implemented.

[0057] In an eighth aspect, a terminal is provided, comprising a processor and a communication interface;

[0058] The communication interface is used to send first information to the PIN server;

[0059] Wherein, the first information includes at least one of the following:

[0060] The first identification information is used to identify the PINE that does not accept becoming a PEGC in the PIN;

[0061] The second identification information is used to identify the PEMC, where the PEMC does not have a gateway capability;

[0062] First indication information, used to indicate that the PIN established by the PEMC is in a deactivated state or that there is no available PEGC in the PIN;

[0063] Second indication information, used to indicate that the PINE corresponding to the first identification information does not accept becoming a PEGC in a PIN, or that the PEMC corresponding to the second identification information does not have a gateway capability;

[0064] a first request for requesting to establish a PIN;

[0065] or,

[0066] The communication interface is used to send first information to the PIN server;

[0067] The first information includes at least one of the following:

[0068] The third indication information is used to indicate whether the PINE has a gateway capability or not;

[0069] Fourth indication information, used to instruct PINE to accept or reject as a PEGC in PIN;

[0070] PINE parameter information.

[0071] In the ninth aspect, a network side device is provided, which includes a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the program or instructions are executed by the processor, the steps of the method described in the first aspect, the second aspect, or the third aspect are implemented.

[0072] In a tenth aspect, a network-side device is provided, including a processor and a communication interface;

[0073] The communication interface is configured to receive first information, wherein the first information satisfies at least one of the following:

[0074] The first information is related to a PIN element PEGC having gateway capability;

[0075] The first information includes a first request, and the first request is used to request to establish a PIN;

[0076] The processor is configured to perform a first operation according to the first information, wherein the first operation includes at least one of the following:

[0077] Determine the PEGC information in the PIN;

[0078] rejecting the first request;

[0079] Deactivate PIN;

[0080] Update the personal Internet of Things network element PINE information of PEGC in PIN;

[0081] Sending second information to the PIN element PEMC with management function, wherein the second information is used to indicate that the PINE as the PEGC is accepted in the PIN, or the second information indicates that the first request is accepted;

[0082] or,

[0083] The communication interface is used to send first information to the PIN server;

[0084] Wherein, the first information includes at least one of the following:

[0085] The first identification information is used to identify the PINE that does not accept becoming a PEGC in the PIN;

[0086] The second identification information is used to identify the PEMC, where the PEMC does not have a gateway capability;

[0087] First indication information, used to indicate that the PIN established by the PEMC is in a deactivated state or that there is no available PEGC in the PIN;

[0088] Second indication information, used to indicate that the PINE corresponding to the first identification information does not accept becoming a PEGC in a PIN, or that the PEMC corresponding to the second identification information does not have a gateway capability;

[0089] a first request for requesting to establish a PIN;

[0090] or,

[0091] The communication interface is used to send first information to the PIN server;

[0092] The first information includes at least one of the following:

[0093] The third indication information is used to indicate whether the PINE has a gateway capability or not;

[0094] Fourth indication information, used to instruct PINE to accept or reject as a PEGC in PIN;

[0095] PINE parameter information.

[0096] In the eleventh aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the second aspect are implemented, or the steps of the method described in the third aspect are implemented.

[0097] In the twelfth aspect, a communication system is provided, including: a PIN server, a PEMC and a PINE, wherein the PIN server can be used to execute the steps of the method described in the first aspect, the PEMC can be used to execute the steps of the method described in the second aspect, and the PINE can be used to execute the steps of the method described in the third aspect.

[0098] In the thirteenth aspect, a chip is provided, which includes a processor and a communication interface, the communication interface and the processor are coupled, and the processor is used to run programs or instructions to implement the method as described in the first aspect, or the method as described in the second aspect, or the method as described in the third aspect.

[0099] In the fourteenth aspect, a computer program / program product is provided, which is stored in a storage medium and is executed by at least one processor to implement the steps of the information processing method described in the first aspect, or the steps of the information processing method described in the second aspect, or the steps of the information processing method described in the third aspect.

[0100] In an embodiment of the present application, the PIN server can obtain first information related to PEGC, and then determine whether there is an available PEGC in a specific PIN based on the first information. If not, the request to establish the PIN can be rejected, or the PIN can be deactivated or the PIN established and deactivated. If it is, the PECG can be specifically indicated for the PIN. Alternatively, the PIN server can update the PINE information that supports the PEGC in the PIN based on the first information, so that the PEMC can determine the available PEGC based on the updated PINE information that supports the PEGC in the PIN. In this way, the probability that the device in the PIN cannot route data or communicate normally due to the lack of PEGC can be effectively reduced, thereby ensuring the reliability of communication. BRIEF DESCRIPTION OF THE DRAWINGS

[0101] FIG1a is a schematic structural diagram of a wireless communication system to which an embodiment of the present application can be applied;

[0102] FIG1b is a flow chart of establishing a PIN in the related art;

[0103] FIG2 is a flow chart of an information processing method provided in an embodiment of the present application

[0104] FIG3 is a flow chart of an information transmission method provided in an embodiment of the present application;

[0105] FIG4 is a flowchart of another information transmission method provided in an embodiment of the present application;

[0106] Figure 5a is a schematic diagram of one of the interactions between the PIN server, PEMC, and PINE;

[0107] FIG5b is a second diagram of the interaction between the PIN server, PEMC and PINE;

[0108] Figure 5c is a third diagram of the interaction between the PIN server, PEMC, and PINE;

[0109] FIG6 is a schematic structural diagram of an information processing device provided in an embodiment of the present application;

[0110] FIG7 is a schematic structural diagram of an information transmission device provided in an embodiment of the present application;

[0111] FIG8 is a schematic structural diagram of another information transmission device provided in an embodiment of the present application;

[0112] FIG9 is a schematic structural diagram of a communication device provided in an embodiment of the present application;

[0113] FIG10 is a schematic structural diagram of a terminal provided in an embodiment of the present application;

[0114] FIG11 is a schematic structural diagram of a network-side device provided in an embodiment of the present application;

[0115] FIG12 is a schematic structural diagram of another network-side device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0116] The following will be combined with the accompanying drawings in the embodiments of this application to clearly describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field are within the scope of protection of this application.

[0117] The terms "first", "second", etc. in this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way are interchangeable where appropriate, so that the embodiments of the present application can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "or" in this application represents at least one of the connected objects. For example, "A or B" covers three options, namely, Option 1: including A but not including B; Option 2: including B but not including A; Option 3: including both A and B. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.

[0118] The term "indication" in this application can be either a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, the operation to be performed, or the requested result, etc. in the instruction sent; an indirect indication can be understood as the receiver determining the corresponding information based on the instruction sent by the sender, or making a judgment and determining the operation to be performed or the requested result, etc. based on the judgment result.

[0119] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) or other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the technology described can be used for the systems and radio technologies mentioned above, as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for illustrative purposes, and NR terminology is used in most of the following description, but these technologies can also be applied to systems other than NR systems, such as 6th generation (6G) systems. th Generation, 6G) communication system.

[0120] FIG1a shows a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (flight vehicle), a vehicle user equipment (VUE), a ship-borne device, a pedestrian user equipment (PUE), a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, or furniture), a game console, a personal computer (PC), an ATM, or a self-service machine, or other terminal-side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 may include an access network device or a core network device, wherein the access network device may also be called a radio access network (Radio Access Network, RAN) device, a radio access network function or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AP) or a wireless fidelity (WiFi) node, etc.Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home evolved Node B (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the relevant field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0121] The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (MME), access mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), policy and charging rules function unit (PCRF), edge application service discovery function (EASDF), unified data management (UDM), unified data repository (UDR), home user server (HSS), centralized network configuration (CNC), network storage function (NRF), network exposure function (NEF), local NEF (L-NEF), binding support function (BSF), application function ( Function, AF), etc. It should be noted that in the embodiments of the present application, only the core network device in the NR system is used as an example for introduction, and the specific type of the core network device is not limited. It should be noted that in the embodiments of the present application, only the core network device in the NR system is used as an example for introduction, and the specific type of the core network device is not limited.

[0122] As shown in FIG1b , in related art, the process of creating a PIN is as follows:

[0123] Step 1: The PEMC sends a PIN creation request to the PIN server to create a PIN. The PIN creation request includes the security credentials of the User Equipment (UE) or PINE-1 received during the authorization process (e.g., obtained via Bluetooth or PIN), and may include a UE identifier, such as a Generic Public Subscription Identifier (GPSI), a PIN client identifier (ID), a UE location, and PIN client profile information.

[0124] It should be noted that the PEMC's request for creating a PIN may include details of other PIN elements (PIN list) with which a connection has been established. The details of the PIN elements may include UE identifiers such as GPSI, PIN client ID, UE location, and PIN client profile information. If the PEMC's request for creating a PIN does not include other PIN elements, the PEMC request includes its own PIN.

[0125] In order to save the process of involving several PEMCs for a specific PIN as separate PEMCs, the PEMC can carry the GPSI or PIN client ID of the additional PEMC in the PIN creation request to indicate the additional PEMC that is allowed to manage the PIN. This procedure does not conflict with other PEMCs requesting to join a specific PIN and become a separate PEMC. Note that for a certain PIN, only one PEMC can be assigned the primary role at a time, and other PEMCs (if any) can be assigned secondary roles.

[0126] Step 2: The PIN server processes the PIN creation request.

[0127] In this step, the PIN server may perform an authorization check upon receiving the request to verify whether the PEMC (PINE 1) has the authorization to perform the PIN creation operation.

[0128] Step 3. The PIN Server sends a PIN Create Response to the PEMC, which includes the newly assigned PIN ID indicating the PIN. It also includes a list of PIN elements and their identifiers. If the PIN Create Request contains a list of PIN elements to be included in the PIN, these PIN elements and their identifiers are authorized and become members of the newly created PIN.

[0129] It should be noted that if the PIN creation request fails, the PIN server should give a failure response indicating the reason for the failure of the PIN creation request.

[0130] If there are no other PIN elements in the PIN creation request and the PIN creation is successful, the PIN server indicates that the PEMC is a PEGC. A PEMC that already plays the PEMC role can also play the PEGC role.

[0131] If one or more PEGCs are indicated in the PIN creation response, the PIN server indicates the PIN client ID or GPSI of a PINE as the PEGC. In addition, the assigned IP address or port number is passed in the PIN creation response to the PEMC. In addition, the PIN server also sends PEGC information about access control in the response. Among them, the access control information includes: user name, account, service set identifier (SSID), basic service set identifier (BSSID). The PIN element in the PIN uses all information to access the fifth-generation (5G) communication system or access other applications outside the PIN.

[0132] Among them, the PIN server or PEMC can determine the access control information in certain PEGCs.

[0133] 1) If the access control information is determined by the PIN server, the PIN server sends the access control information to the PEMC via a PIN Create Response. The PEMC passes the access control information to the PEGC via a PIN Create Notify Request.

[0134] 2) If the access control information is determined by the PEMC, the PEMC passes the access control information to the PEGC through a PIN creation notification request.

[0135] Steps 4a-4c: If the PIN creation response contains a list of PIN elements, the PEMC generates a PIN creation notification request (e.g., a PIN Creation notification request) for each PIN based on the list received in step 3. The notification request includes the PIN ID of the newly created PIN and also includes an instruction to make the PIN element a member of the newly created PIN.

[0136] Steps 5a-5c: Each PIN element sends a PIN Create Notification Response to the PEMC to acknowledge receipt of the notification. PIN elements that receive a PIN Create Notification Request with a Join indication should not join the PIN by issuing a PIN Join Request, as they are already members of the PIN.

[0137] From the above process, we can see that the relevant technology has the following defects:

[0138] 1) If there is no suitable PINE that can serve as the PEGC in the PIN, the PIN server will instruct the PEMC to serve as the PEGC. However, as a terminal with gateway capabilities in the PIN, the PEGC needs to route data or communications for the devices in the PIN. The PEMC may not have the relevant PEGC functions, which will result in the devices in the PIN being unable to route data or communicate normally due to the lack of a PEGC.

[0139] 2) After obtaining the PINE list, PEMC will send a notification message to the relevant PINE to inform that the PINE has been added to the PIN. The PEMC notification message contains: PIN ID and one or more of access control information, PIN member indication, PEGC address, and PEGC ID. However, for PEGC, as a terminal with gateway capabilities in the PIN, it is possible to reject the PEMC's request. The reason is that when the PIN is created, the PEGC is selected by the PIN server and no agreement is reached between the PEMC and PEGC. Therefore, if PEGC rejects PEMC, the devices in the PIN will not be able to route data or communicate normally because there is no PEGC.

[0140] In an embodiment of the present application, the PIN server can obtain first information related to PEGC, and then determine whether there is an available PEGC in a specific PIN based on the first information. If not, the request to establish the PIN can be rejected, or the PIN can be deactivated or the deactivated PIN can be established. In this way, the probability that the PIN cannot route data or communication normally due to the absence of an available PEGC in the PIN can be reduced.

[0141] To facilitate understanding of the information processing method and information transmission method provided in the embodiments of the present application, the following terms in the embodiments of the present application are first explained:

[0142] Application layer support for Personal IoT Networks (PIN APPs) builds on the significant increase in the number of consumer IoT devices. Users primarily use all of these devices in their homes or around their bodies to create personal IoT networks. Application layer support for Personal IoT Networks provides the application layer architecture and related processes for implementing PIN applications on 3GPP networks.

[0143] PIN: It is a personal network composed of Internet of Things (IoT) devices. It includes: at least one PEGC, at least one PEMC and a group of configured and managed PINEs, wherein a group of PINEs can communicate with each other directly, communicate with each other through the PEGC, or use the PEGC to communicate with devices or servers outside the PIN through the 5G network. At least one PEGC is managed by the PEMC. Optionally, if an application function (AF) is deployed, PIN management can be implemented with the support of the AF. In the embodiments of the present application, the AF may sometimes also be referred to as a PIN server.

[0144] PINE: It is the basic unit in the PIN and can include UE or non-3rd Generation Partnership Project (3GPP) devices. It can communicate within the PIN (through PINE to PINE direct connection or PINE to PIN indirect connection) or outside the PIN through PEGC and 5G Core Network (5GC).

[0145] PEGC: Serves as a gateway within a PIN, possessing communication capabilities and enabling PINEs to route data to one another. For example, a PEGC can provide data network (DN) connectivity to other PIN components via a 5G network and / or relay communications between PIN components. Typically, only the UE can act as a PEGC.

[0146] PEMC: It is the administrator in the PIN and has communication capabilities. It is used to manage the authorization of various things in the PIN. Optionally, the UE as a PIN element can act as both PEMC and PEGC.

[0147] No PEGC available in PIN, including:

[0148] 1) During the process of establishing a PIN, the PEGC indicated by the PIN server to the PEMC refuses to become the PEGC in the PIN established by the PEMC, or the PEGC indicated by the PIN server to the PEMC is unreachable, or there is no PINE that accepts it as the PEGC in the PIN established by the PEMC;

[0149] 2) The PEMC requesting to establish a PIN does not have gateway capabilities.

[0150] There is no PINE that accepts being the PEGC in the PIN established by the PEMC, where "accept" can be understood as: support or agreement, for example: there is no PINE in the PIN that supports gateway capabilities, or, after requesting PINE to be the PEGC in the PIN, PINE refuses to become the PEGC in the PIN.

[0151] The information transmission method, information processing method, information transmission device, information processing device and related equipment provided in the embodiments of the present application are described in detail below with reference to some embodiments and their application scenarios in combination with the accompanying drawings.

[0152] Please refer to Figure 2, an embodiment of the present application provides an information processing method, the execution subject of which may be a PIN server. As shown in Figure 2, the information processing method may include the following steps:

[0153] Step 201: The PIN server receives first information, where the first information satisfies at least one of the following:

[0154] The first information is related to a PIN element PEGC having gateway capability;

[0155] The first information includes a first request, where the first request is used to request establishment of a PIN.

[0156] In one implementation, the first information may include information related to the PIN element PEGC with gateway capability and the first request.

[0157] Alternatively, the first request may be a PIN establishment request.

[0158] In another embodiment, the first information includes information related to a PIN element PEGC with gateway capability.

[0159] In another embodiment, the first information includes a first request, and the first request carries information related to the PIN element PEGC with gateway capability.

[0160] In another embodiment, the PEMC sends a first request to a PIN server to create a PIN. After receiving the first request, the PIN server interacts with the PINE in the PIN to obtain first information, thereby determining the PEGC information in the PIN. The first information is associated with the PEGC element of the PIN with gateway capabilities. In this embodiment, the PEMC's sending of the first request to the PIN server can also be understood as triggering the PIN server to obtain information related to the PEGC, which is then used to determine the PEGC information in the PIN.

[0161] In some embodiments, the first information is related to a PIN element PEGC with gateway capability. It can also be understood that the first information is used to determine the PEGC in the PIN, for example: the first information indicates which PINE(s) are accepted as the PEGC in the PIN.

[0162] Step 202: The PIN server performs a first operation based on the first information, where the first operation includes at least one of the following:

[0163] Determine the PEGC information in the PIN;

[0164] rejecting the first request;

[0165] Deactivate PIN;

[0166] Update the personal Internet of Things network element PINE information of PEGC in PIN;

[0167] Sending second information to the PIN element PEMC with management function, wherein the second information is used to indicate that the PINE as PEGC is accepted in the PIN, or the second information indicates acceptance of the first request.

[0168] Optionally, the first information may come from PEMC or PINE.

[0169] Alternatively, the first information may be obtained through multiple steps, for example, first obtaining a portion of the first information from the PEMC and then obtaining another portion of the first information from the PINE; or first obtaining a portion of the first information from the PINE and then obtaining another portion of the first information from the PEMC. In this case, steps 201 and 202 may be performed alternately, such as first performing a portion of the first operation in step 202 based on a portion of the first information and then performing a portion of the first operation in step 202 based on another portion of the first information. The order of performing steps 201 and 202 is not limited herein.

[0170] In one implementation, the PEMC may send the first information to the PIN server during the process of establishing the PIN.

[0171] In another embodiment, the PEMC may send the above-mentioned first information to the PIN server after establishing the PIN. For example, during the process of establishing the PIN, some of the PINEs in the PINE list indicated by the PIN server are accepted as PEGCs in the PIN, while the other part are rejected as PEGCs in the PIN. At this time, the PEMC may determine the PEGC in the PIN based on the PINEs accepted as PEGCs in the PIN, and feedback the information of the PINEs rejected as PEGCs in the PIN to the PIN server, so that the PIN server updates the PINE information of the PEGCs in the PIN accordingly.

[0172] In another embodiment, the PINE may send the first information to the PIN server. For example, during the PINE registration process, the registration information sent to the PIN server includes whether the PINE has a gateway function, or whether it is accepted as a PEGC in the PIN.

[0173] It is worth mentioning that in the related art, the registration process of PINE is as follows:

[0174] 1. PINE (including PINE, PEMC and PEGC) sends a PINE registration request to the PIN server.

[0175] The registration request includes the security credentials of the PINE received during the authorization process, and the registration request may also include PINE identification information such as GPSI, Media Access Control (MAC) address, vendor name, device description, and PINE address.

[0176] If it is the PEMC that triggers the registration request, the registration request carries the PIN ID of the PIN for which it intends to register as a PEMC, and the PIN element may indicate whether it is assigned the primary or secondary PEMC role.

[0177] 2. The PIN server interacts with the 5G System (5GS) to check whether the PINE identified by GPSI has been subscribed as a PEMC.

[0178] Additionally, the PIN Server can check whether the PINE identified by the GPSI is already subscribed as a PEMC. If so, it checks the PIN profile to see if the requested PIN element can be assigned a primary or secondary role and authorizes the PIN element accordingly. If a PIN has already been created, the requesting PIN element is assigned the secondary PEMC role, regardless of the role requested by the PIN element.

[0179] 3. In a successful response, the PIN Server responds to PINE with a PINE Registration Response that assigns the PIN Client ID. If the registration process fails, the PIN Server shall issue a Failure Response to indicate the reason why the registration request failed.

[0180] From the above, it can be seen that in the related art, there is no essential difference between the registration of PEGC and PINE, that is, after a PEGC with gateway capability registers with the PIN server, the PIN server cannot distinguish whether the PINE has gateway capability.

[0181] Through the above-mentioned implementation of the present application, PEGC can carry the first information during the process of registering with the PIN server. For example: during the PINE registration process, the registration information sent to the PIN server includes whether the PINE has a gateway function, or whether it is accepted as a PEGC in the PIN, etc. In this way, the PIN server can support the PINE with a gateway function or accepted as a PEGC in the PIN to the PEMC as the PEGC in the PIN, so that the devices in the PIN can perform normal data routing or communication based on PEGC.

[0182] In an optional implementation, determining the PEGC information in the PIN in the first operation may include: the PIN server may determine whether there is available PEGC in the PIN based on the first information.

[0183] In one embodiment, if the PIN server determines that there is no available PEGC in the PIN based on the first information, the PIN server may reject the first request for establishing the PIN, i.e., reject the establishment of the PIN. In this way, the establishment of a PIN without an available PEGC can be avoided.

[0184] In another embodiment, if the PIN server determines that there is no available PEGC in the PIN based on the first information, the PIN server may deactivate the PIN, for example, by agreeing to the PEMC to establish the PIN and indicating that the established PIN is in a deactivated state, or by only agreeing to the PEMC to establish the PIN without indicating an available PEGC for the PIN. In this case, the established PIN is in a deactivated state.

[0185] Optionally, after establishing a deactivated PIN, if the PIN server obtains a usable PEGC in the PIN, the PIN can be activated. For example, if a gateway-capable PINE in the PIN registers with the PIN server, the PIN server can designate the PINE as the PEGC in the deactivated PIN and activate the PIN. This allows a deactivated PIN to be established if there is no usable PEGC in the PIN, and then reactivated when a usable PEGC becomes available. Compared to the previous embodiment, which rejected PIN establishment if there is no usable PEGC in the PIN, this reduces the probability of repeatedly establishing the PIN due to a lack of usable PEGC.

[0186] It is worth mentioning that a PIN in a deactivated state is unavailable, for example, no data routing or data transmission is performed between the PINEs in the PIN.

[0187] Unlike related art, where the PIN server does not know whether there is an available PEGC in the PIN, and thus, when there is no available PEGC in the PIN, an unusable PIN is established, in the embodiment of the present application, the PIN server can determine whether there is an available PEGC in the PIN, and thus, when there is no available PEGC in the PIN, it refuses to establish the PIN or establishes a deactivated PIN.

[0188] In another optional implementation, determining the PEGC information in the PIN in the first operation may include: the PIN server may determine available PEGC in the PIN based on the first information.

[0189] For example, during the registration process, the PINE sends first information to the PIN server to indicate whether the PINE has gateway capability. In this way, the PIN server can determine, based on the first information, that the PINE with gateway capability can be used as a PEGC available in the PIN.

[0190] In this embodiment, the PIN server determines the available PEGCs in the PIN according to the first information, so as to specifically indicate the available PEGCs in the established PIN to the PEMC.

[0191] In an optional implementation manner, the sending of the second information to the PEMC in the first operation may include:

[0192] The PIN server determines the PINE to be accepted as the PEGC in the PIN based on the first information, and notifies the PEMC to accept the PINE as the PEGC in the PIN.

[0193] For example: during the PIN establishment process, the PIN server receives a first request from the PEMC, and based on the first request, sends a second request to the PINE in the PIN to request the PINE to serve as the PEGC in the PIN. The PINE then feeds back a response to the PIN server. The PIN server may agree to the first request and notify the PEMC through the second information that it will accept the PINE as the PEGC in the PIN as the PEGC in the PIN.

[0194] In this embodiment, the PIN server requests the PINE as the PEGC in the PIN according to the first information, thereby being able to specifically instruct the PEMC to accept the PINE as the PEGC in the PIN it has established.

[0195] In an optional implementation manner, the sending of the second information to the PEMC in the first operation may include:

[0196] The PIN server accepts the first request based on the first information and when determining that there is no available PEGC in the PIN established by the PEMC.

[0197] It should be noted that although the PIN server accepts the first request, since there is no available PEGC in the PIN, only a deactivated PIN can be established. For example, the second message carries an instruction to deactivate the PIN, or the second message carries the identification information of the PEMC, and the PEMC does not have gateway capabilities.

[0198] In this embodiment, activation of a PIN without available PEGC can be avoided.

[0199] In an optional implementation, updating the PINE information of the PEGC in the PIN in the first operation may include:

[0200] During the PIN establishment process, the PIN server indicates the PINEs that can be used as PEGCs to the PEMC, but some PINEs refuse to be used as PEGCs in the PIN established by the PEMC. At this time, the PEMC can feedback to the PIN server the PINEs that refuse to be used as PEGCs in the PIN established by the PEMC, so that the PIN server can update the PINE information of the PEGCs in the PIN accordingly, for example: deleting the PINEs that refuse to be used as PEGCs in the PIN established by the PEMC from the list of PINEs that are accepted as PEGCs in the PIN, etc.

[0201] In an optional implementation, updating the PINE information of the PEGC in the PIN in the first operation may include:

[0202] After the PIN is established, the PIN server receives registration information from the PINE, which may indicate whether the PINE has gateway capability or whether it is accepted as a PEGC in the PIN. The PIN server may update the PINE information of the PEGC in the PIN based on the PINE that has gateway capability or is accepted as a PEGC in the PIN, for example, adding the PINE that has gateway capability or is accepted as a PEGC in the PIN as a PEGC in the PIN.

[0203] As in the above embodiment, by updating the PINE information of the PEGC in the PIN, the available PEGC in the PIN can be updated in time, so that data routing or communication in the PIN is performed based on the available PEGC.

[0204] As an optional implementation manner, the second information indicating that the PINE as PEGC is accepted in the PIN includes at least one of the following:

[0205] The second information indicates a PINE that is a primary PEGC in the PIN established by the PEMC;

[0206] The second information indicates a PINE which is a secondary PEGC in the PIN established by the PEMC.

[0207] In this embodiment, the PIN server may indicate one primary PEGC, or one primary PEGC and at least one secondary PEGC to the PEMC.

[0208] Optionally, the PIN Server may indicate one or more PEGCs during the PIN creation process:

[0209] (1) If the primary PEGC refuses to become the PEGC in the PIN or the primary PEGC is unreachable, and there is at least one secondary PEGC that does not refuse the PEMC, the PEMC can use the secondary PEGC as the primary PEGC in the PIN;

[0210] (2) If the primary PEGC does not reject the PEMC's request (and is reachable), the PEMC can use the primary PEGC as the primary PEGC in the PIN and ignore the rejected or unreachable PEGC.

[0211] In one embodiment, when there is at least one PEGC that can serve the PIN, the PEMC reports information of the PEGC that refuses to serve the PIN to the PIN server while ignoring the rejected or unreachable PEGC.

[0212] In another embodiment, when there is at least one PEGC that can serve the PIN, the PIN server can update the PEGC information to the PIN.

[0213] In another embodiment, the PIN server confirms during PIN creation that a certain PINE can serve as the PEGC in the PIN. However, for some reason, a certain PEGC, although it agrees to serve as the PEGC, is unreachable when the PEMC sends the PIN notification message: If the primary PEGC is unreachable, the PEMC can use the secondary PEGC as the primary PEGC in the PIN; if the secondary PEGC is unreachable, the PEMC can use the primary PEGC as the primary PEGC in the PIN and ignore the rejected or unreachable PEGC.

[0214] Optionally, if at least one PEGC is unreachable when the PEMC sends the PIN notification message, the PEMC may also report the information of the unreachable PEGC to the PIN server, so that the PIN server updates the PEGC information in the PIN accordingly.

[0215] As an optional implementation manner, the first information includes at least one of the following:

[0216] The first identification information is used to identify the PINE that does not accept becoming a PEGC in the PIN;

[0217] The second identification information is used to identify the PEMC that does not have the gateway capability;

[0218] The first indication information is used to indicate that the PIN is in a deactivated state or that there is no available PEGC in the PIN;

[0219] Second indication information, used to indicate that the PINE corresponding to the first identification information does not accept becoming a PEGC in a PIN, or that the PEMC corresponding to the second identification information does not have a gateway capability;

[0220] The third indication information is used to indicate whether the PINE has a gateway capability or not;

[0221] Fourth indication information, used to instruct PINE to accept or reject as a PEGC in PIN;

[0222] PINE parameter information;

[0223] The first request.

[0224] In one implementation, the first identification information and the second identification information may be any information identifying the PINE, such as a PINE ID or a PINE address.

[0225] In one implementation, the first information may include first identification information and second indication information. In this case, the second indication information explicitly indicates that the PINE corresponding to the first identification information does not accept becoming a PEGC in a PIN or does not have gateway capability.

[0226] In another embodiment, the first information may only include the first identification information. In this case, the PINE indicated by the first identification information is considered by default to be a PINE that does not accept becoming a PEGC in a PIN or does not have a gateway capability.

[0227] In another embodiment, the first information may include second identification information and second indication information. In this case, the second indication information explicitly indicates whether the PEMC corresponding to the second identification information has or does not have gateway capability. For example, in the process of establishing a PIN, the PEMC sends a message carrying the second identification information and the second indication information to indicate that the PEMC does not have gateway capability. The PIN server may not indicate the PEMC as the PEGC in the PIN established for it if there are other available PEGCs.

[0228] In another embodiment, the first information may only include the second identification information. In this case, it may be assumed that the PEMC indicated by the second identification information does not have the gateway capability.

[0229] In another embodiment, the PEMC may, upon determining that no PEGC is available, send first indication information to the PIN server to indicate that the PIN is in a deactivated state or that no PEGC is available in the PIN. For example, during the PIN establishment process, the PEMC receives a list of PINEs fed back by the PIN server and sends a third request to these PINEs requesting them to serve as PEGCs in the PIN. If all PINEs reject the third request and the PEMC does not have a gateway function, the PEMC may send the first indication information to the PIN server to indicate that the PIN is in a deactivated state or that no PEGC is available in the PIN.

[0230] In another embodiment, PINE may send third indication information or fourth indication information to the PIN server, for example, carrying the third indication information or fourth indication information in the PINE registration message. If the third indication information or the fourth indication information indicates that PINE does not have gateway capability or does not accept it as the PEGC in the PIN, the PIN server may not instruct PEMC to use it as the PEGC in the PIN.

[0231] In another implementation, the PINE may send its parameter information to the PIN server, for example, by carrying the PINE parameter information in a PINE registration message, so that the PIN server determines whether the PINE supports being used as a PEGC in the PIN based on the PINE parameter information.

[0232] Optionally, the parameter information of the PINE includes at least one of the following:

[0233] PINE's MAC address;

[0234] PINE's Internet Protocol (IP) address;

[0235] PINE's port number;

[0236] PINE's ability information.

[0237] In one embodiment, based on the MAC address, IP address or port number of the PINE, it can be determined whether it can provide data routing or communication between PINEs in the PIN, and further whether it supports serving as a PEGC in the PIN.

[0238] In another embodiment, whether the PINE has the capability to serve as a PEGC in a PIN can be determined based on its capability information.

[0239] Optionally, the capability information of the PINE includes at least one of the following:

[0240] The maximum number of PINEs supported when PINE is used as PEGC;

[0241] The maximum transfer rate supported by PINE;

[0242] The maximum transmission rate supported by PINE as PEGC;

[0243] Maximum number of PINs supported when PINE is used as PEGC.

[0244] Among them, based on the above capability information, as well as the number of PINEs in the corresponding PIN, business requirements, etc., it is determined whether the PINE supports being the PEGC in the PIN, and the number of PEGCs required in the PIN, etc.

[0245] As an optional implementation manner, the PIN server performs a first operation according to the first information, including:

[0246] If the PIN server determines, based on the first information, that there is no available PEGC in the PIN, the first request is rejected, or the PIN is deactivated, or the first request is accepted.

[0247] In one embodiment, when the PIN server determines that there is no available PEGC in the PIN based on the first information, deactivating the PIN may mean that the PIN server sends an acceptance response to the PEMC, and the acceptance response carries indication information that the PIN is in a deactivated state.

[0248] Optionally, the PIN server sends a second message to the PEMC, where the second message is used to accept the first request, and the second message includes eighth indication information, where the eighth indication information is used to indicate that no PEGC is available in the PIN or that the PIN is not activated. In this way, the PEMC can determine that a deactivated PIN has been established based on the second message carrying the eighth indication information.

[0249] In another embodiment, if the PIN server determines, based on the first information, that there is no available PEGC in the PIN, then accepting the first request may mean that the PIN server sends an acceptance response to the PEMC. In this case, the PEMC determines that the established PIN is a deactivated PIN based on the absence of an available PEGC. For example, if the PIN server determines that there is no PINE accepted as a PEGC, it sends an acceptance response to the PEMC. The acceptance response carries the PEMC identifier. In this case, the PEMC determines whether it has gateway capabilities based on the PEMC identifier in the acceptance response. If not, the established PIN is determined to be a deactivated PIN. If so, the PEMC is determined to still serve as the PEGC in the established PIN.

[0250] In another embodiment, when the PIN server refuses to establish a PIN or deactivate a PIN, the PIN server may indicate the reason for refusing to establish a PIN or deactivate a PIN to the PEMC.

[0251] For example, the rejecting the first request or deactivating the PIN includes:

[0252] The PIN server sends seventh information to the PEMC, where the seventh information is used to indicate a reason for a PIN establishment failure or a reason for a PIN deactivation.

[0253] Optionally, the seventh information is used to indicate at least one of the following:

[0254] No PEGC available;

[0255] PIN is not activated.

[0256] In this embodiment, the PEMC may be informed through the seventh information that the reason why the PIN server refuses to establish or deactivate the PIN is that there is no available gateway in the PIN, or directly indicates that the PIN is not activated.

[0257] As an optional implementation manner, in a case where the first information includes the first request from the PEMC, the PIN server performs a first operation according to the first information, including:

[0258] The PIN server sends second information to the PEMC based on the first request, wherein the second information includes third identification information, and the third identification information is used to identify the PINE indicated by the PIN server as the PEGC in the PIN established by the PEMC, or the second information indicates that the PEMC requests the PINE identified by the third identification information as the PEGC in the PIN established by the PEMC.

[0259] Optionally, the third identification information is used to identify at least one of the following:

[0260] A PINE that is a primary PEGC in a PIN established by the PEMC;

[0261] The PINE is a secondary PEGC in the PIN established by the PEMC.

[0262] In this embodiment, during the PIN establishment process, the PIN server indicates the PINE corresponding to the candidate PEGC to the PEMC. At this time, the PEMC may send a third request to the PINE corresponding to the candidate PEGC to request it to serve as the PEGC in the PIN established by the PEMC.

[0263] It should be noted that after PEMC can send the third request to the PINE corresponding to the candidate PEGC, the PINE may accept or reject the third request, wherein the PINE that rejects the third request does not accept the PEGC in the PIN established as the PEMC, and the PINE that accepts the third request accepts the PEGC in the PIN established as the PEMC.

[0264] Optionally, if all third requests are rejected, the PIN server receives the first information, further comprising:

[0265] The PIN server receives third information from the PEMC, wherein the first information also includes the third information, and the third information is used to request an update of the PEGC in the PIN established by the PEMC, or to indicate that all PINEs corresponding to the third identification information refuse to become PEGCs in the PIN established by the PEMC, or that the PEMC does not have gateway capability.

[0266] In this embodiment, when all third requests are rejected and the PEMC does not have gateway capability, there is no available PEGC in the PIN established by the PEMC. At this time, the PEMC may request the PIN server to update the PEGC in the PIN established by the PEMC.

[0267] Optionally, the PIN server performing the first operation according to the first information further includes at least one of the following:

[0268] The PIN server updates, based on the first information, the PINE information of the PEGC accepted as part of the PIN established by the PEMC;

[0269] The PIN server sends, to the PEMC, based on the first information, updated identification information of the PINE that accepts becoming the PEGC in the PIN established by the PEMC;

[0270] The PIN server sends the identification information of the PEMC to the PEMC according to the first information, instructing the PEMC to serve as the PEGC in the PIN established by it;

[0271] The PIN server sends a first response to the PEMC according to the first information, where the first response is used to reject the first request, or deactivate the PIN established by the PEMC, or receive the first request.

[0272] In one embodiment, the PIN server updates the PINE information accepted as the PEGC in the PIN established by the PEMC based on the first information. This may be: when there is a PINE that can be used as the PEGC in the PIN among the newly registered PINEs, the PIN server adds the PINE as the PINE information accepted as the PEGC in the PIN established by the PEMC; or, during the PIN establishment process, when there is a PINE that refuses to be the PEGC in the PIN established by the PEMC, the PIN server deletes the PINE from the PINE information accepted as the PEGC in the PIN established by the PEMC.

[0273] In one embodiment, the PIN server sends, based on the first information, to the PEMC updated identification information of the PINE that accepts to become the PEGC in the PIN established by the PEMC. This may be done by: if a PINE that can serve as the PEGC in the PIN is present among the newly registered PINEs, the PIN server sends the identification information of the PINE to the PEMC, so that the PEMC will select the PINE as the PEGC in the PIN; or, during the PIN establishment process, if all PINEs indicated by the PIN server as capable of serving as the PEGC are unreachable or refuse to serve as the PEGC in the PIN, the PIN server may update the PEGC information in the PIN and indicate the updated PEGC information to the PEMC.

[0274] In one embodiment, the PIN server sends the identification information of the PEMC to the PEMC based on the first information, instructing the PEMC to serve as the PEGC in the PIN it establishes. It can be that when the PIN server fails to obtain a PINE other than the PEMC that can be used as the PEGC in the PIN, the PIN server instructs the PEMC to use the PEMC as the PEGC in the PIN.

[0275] In one embodiment, the PIN server sends a first response to the PEMC based on the first information, and the first response is used to reject the first request, or deactivate the PIN established by the PEMC, or receive the first request, which can be: during the PIN establishment process, when the PIN server determines that there is no available PEGC in the PIN requested to be established by the PEMC, it refuses to establish the PIN, or establishes a deactivated PIN, or establishes a PIN, but the PIN is in a deactivated state based on the lack of available PEGC.

[0276] As an optional implementation manner, the first information further includes fifth indication information, wherein the fifth indication information is used to indicate that the PIN established by the PEMC is in a deactivated state, or to indicate that there is no available PEGC in the PIN established by the PEMC.

[0277] In this embodiment, when the PEMC determines that there are no available PEGCs in the PIN, for example, when all PEGCs indicated by the PIN server are unreachable or refuse to become PEGCs in the PIN, and the PEMC does not have a gateway function, the PEMC may send a fifth indication message to the PIN server to indicate that the PIN established by the PEMC is in a deactivated state, or to indicate that there are no available PEGCs in the PIN established by the PEMC. Based on this fifth indication message, the PIN server may update the PEGC in the PIN or establish a deactivated PIN.

[0278] As an optional implementation manner, the PIN server receives the first information including:

[0279] The PIN server receives registration information from a PINE, where the first information includes the registration information, and the registration information includes indication information indicating whether the PINE has gateway capability or not, or whether the PINE accepts or does not accept being a PEGC in a PIN.

[0280] In this embodiment, the PINE reports whether the PINE has gateway capability or not, or whether the PINE accepts or does not accept the indication information as PEGC in the PIN during the registration process, so that the PIN server can determine whether it supports PEGC as the PIN based on the registration information.

[0281] As an optional implementation manner, the PIN server performs a first operation according to the first information, including at least one of the following:

[0282] The PIN server determines, based on the registration information, to accept the PINE as the PEGC in the PIN;

[0283] When the PIN server determines, based on the registration information, that the PINE accepted as the PEGC in the PIN has changed, the PIN server sends fourth information to the PEMC of the PIN, or determines that there is no available PEGC in the PIN, wherein the fourth information indicates the changed PINE accepted as the PEGC in the PIN;

[0284] Upon receiving the first request from the PEMC, if the PIN server determines that there is a target PINE among the registered PINEs that accepts being used as the PEGC in the PIN established by the PEMC, the PIN server sends sixth indication information to the PEMC, wherein the sixth indication information instructs the PEMC to request the target PINE to be used as the PEGC in the PIN established by the PEMC; or

[0285] When the PIN server receives the first request from the PEMC, if it determines that there is no target PINE among the registered PINEs that accepts the PEGC in the PIN established by the PEMC, it sends seventh indication information to the PEMC, wherein the seventh indication information instructs the PEMC to be the PEGC in the PIN established by it, or indicates that the PIN established by the PEMC is in a deactivated state, or rejects the PEMC from establishing the PIN.

[0286] Optionally, the fourth information includes at least one of the following:

[0287] the identification information of the changed PINE accepted as the PEGC in the PIN;

[0288] Modification type;

[0289] Identification information of the PIN (PIN ID);

[0290] PIN profile information;

[0291] Dynamic PIN profile information.

[0292] In one implementation, after the PIN is established, if a newly registered PINE is accepted as the PEGC in the PIN, the PIN server may send the PINE to the PEMC so that the PEMC may use the PINE as the PEGC in the PIN.

[0293] In another embodiment, after the PIN is established, if a PINE is unreachable or the registration information is modified to not accept the PEGC in the PIN, the PIN server can determine that the PINE is changed to not accept the PEGC in the PIN. At this time, if all PEGCs in the PIN are changed to not accept the PEGC in the PIN, the PIN server can indicate to the PEMC that there is no available PEGC in the PIN.

[0294] In one embodiment, during the PIN establishment process, the PIN server may determine, based on the registration information of the registered PINE, the target PINE to be accepted as the PEGC in the PIN established by the PEMC request, thereby sending sixth indication information to the PEMC to instruct the PEMC to request the target PINE to be the PEGC in the PIN it establishes.

[0295] In one embodiment, during the PIN establishment process, if the PIN server determines based on the registration information of the registered PINE that there is no target PINE that accepts the PEGC in the PIN established by the PEMC request, the PEMC may send a seventh indication message to instruct the PEMC to be the PEGC in the PIN it establishes, or to indicate that the PIN established by the PEMC is in a deactivated state, or to reject the PEMC from establishing the PIN.

[0296] It should be noted that, when the seventh indication information indicates that the PEMC serves as the PEGC in the PIN established by it, if the PEMC has gateway capability, the PEMC serves as the PEGC in the established PIN; if the PEMC does not have gateway capability, the PEMC as the established PIN can be in a deactivated state.

[0297] As an optional implementation manner, in a case where the first information includes the first request from the PEMC, the PIN server performs a first operation according to the first information, including:

[0298] The PIN server sends a second request to the first PINE, wherein the second request is used to request the first PINE to serve as the PEGC in the PIN established by the PEMC;

[0299] The PIN server receives first information, including:

[0300] The PIN server receives a second response from the first PINE, wherein the second response carries first information, and the first information indicates whether the first PINE accepts or rejects the PEGC in the PIN established by the PEMC.

[0301] In this embodiment, during the PIN establishment process, the PIN server requests the first PINE for the PEGC in the PIN that it requested to establish as a PEMC. At this point, the first PINE can respond with an acceptance or rejection response to the PIN server. Based on this response, the PIN server can determine the PEGC in the PIN, determine whether the PEGC is available in the PIN, reject or accept the first request, or determine whether the established PIN is in an activated or deactivated state.

[0302] Optionally, the PIN server performing the first operation according to the first information further includes at least one of the following:

[0303] The PIN server updates, according to the second response, information of the PINE that is accepted as the PEGC in the PIN established by the PEMC, for example, determining the first PINE that sends the acceptance response as the updated PINE that is accepted as the PEGC in the PIN established by the PEMC;

[0304] The PIN server sends identification information of a target first PINE to the PEMC according to the second response, wherein the target first PINE is the first PINE that accepts the PEGC in the PIN established by the PEMC, for example, by sending a second message to the PEMC, and the second message carries identification information of the first PINE that sends the acceptance response;

[0305] The PIN server sends the identification information of the PEMC to the PEMC according to the second response, instructing the PEMC to serve as the PEGC in the PIN established by it. For example, if all the first PINEs send rejection responses, the PIN server sends the second information to the PEMC, and the second information carries the identification information of the PEMC;

[0306] The PIN server sends a first response to the PEMC based on the second response, wherein the first response is used to respond to the first request, for example, if all the first PINEs send rejection responses, the first request is rejected or the PIN requested to be established by the first request is deactivated.

[0307] Optionally, after the PIN server sends the identification information of the PEMC to the PEMC according to the first response, instructing the PEMC to serve as the PEGC in the PIN established by it, the PIN server performs a first operation according to the first information, further comprising:

[0308] The PIN server receives fifth information from the PEMC, where the fifth information indicates whether the PEMC accepts or does not accept the PEGC in the PIN it establishes, or whether the PEMC has a gateway capability or not.

[0309] In this embodiment, the PIN server can determine, based on the first response, that the first PINE completely refuses to become the PEGC in the PIN established by the PEMC, and then send the identification information of the PEMC to the PEMC, instructing the PEMC to be the PEGC in the PIN established by it. At this time, if the PEMC does not have the gateway capability, it will feedback the fifth information to the PIN server that it does not accept it as the PEGC in the PIN established by it, or that it does not have the gateway capability.

[0310] In one implementation, the PIN server may determine whether there is an available PEGC in the PIN based on the first response and the fifth information.

[0311] Optionally, when the PIN server determines that there is no available PEGC in the PIN established by the PEMC, the first response is used to reject the first request, or to deactivate the PIN established by the PEMC, or to accept the first request.

[0312] It is worth mentioning that when the PIN server determines that there is no available PEGC in the PIN established by the PEMC, the first response is used to accept the first request. It may be that although the PIN server agrees to establish the PIN, based on the fact that there is no available PEGC in the PIN, the PIN is in a deactivated or other unavailable state.

[0313] As an optional implementation manner, the first information further includes PEMC-related information or PIN-related information;

[0314] The first operation further includes:

[0315] The sixth information is updated, where the sixth information includes at least one of the following:

[0316] PEMC information;

[0317] PIN profile information.

[0318] In this embodiment, in addition to the PEGC in the PIN, other information in the PIN may also be updated based on the first information, such as PEMC information or PIN profile information, etc. For example, when the PEMC is unreachable, the PEMC in the PIN is updated.

[0319] In an embodiment of the present application, the PIN server can obtain first information related to PEGC, and then determine whether there is an available PEGC in a specific PIN based on the first information. If not, the request to establish the PIN can be rejected, or the PIN can be deactivated or the PIN established and deactivated can be deactivated; if it is, the PECG can be specifically indicated for the PIN; or the PIN server can update the PINE information supported as the PEGC in the PIN based on the first information, so that the PEMC can determine the available PEGC based on the updated PINE information supported as the PEGC in the PIN. In this way, the probability that the device in the PIN cannot route data or communicate normally due to the lack of PEGC can be reduced.

[0320] Please refer to Figure 3, which is a flow chart of an information transmission method provided in an embodiment of the present application. The execution subject of the information transmission method may be a PEMC. As shown in Figure 3, the method may include the following steps:

[0321] Step 301: PEMC sends first information to the PIN server;

[0322] Wherein, the first information includes at least one of the following:

[0323] The first identification information is used to identify the PINE that does not accept becoming a PEGC in the PIN;

[0324] Second identification information is used to identify the PEMC, and the PEMC does not have a gateway capability;

[0325] First indication information, used to indicate that the PIN established by the PEMC is in a deactivated state or that there is no available PEGC in the PIN;

[0326] Second indication information, used to indicate that the PINE corresponding to the first identification information does not accept becoming a PEGC in a PIN, or that the PEMC corresponding to the second identification information does not have a gateway capability;

[0327] A first request is used to request to establish a PIN.

[0328] It should be noted that the various contents of the above-mentioned first information in the embodiment of the present application have the same meaning and function as the corresponding contents of the first information in the method embodiment shown in Figure 2. For details, please refer to the explanation in Figure 2 and will not be repeated here. In addition, PEMC can provide the PIN server with the first information for assisting in determining the PEGC in the PIN. For example: whether there is an available PEGC in the PIN, which PEGCs are not accepted as PEGCs in the PIN, whether PEMC can be used as the PEGC in the PIN, etc., when there is no PINE in the PIN that is accepted as a PEGC, how to deal with it, such as: deactivating the PIN, refusing to establish the PIN, or updating the PEGC in the PIN, etc. It can achieve similar beneficial effects as the method embodiment shown in Figure 2. In order to avoid repetition, it will not be repeated here.

[0329] Optionally, the method further includes:

[0330] The PEMC receives second information from the PIN server, wherein the second information is used to indicate that the second PINE as the PEGC is accepted in the PIN established by the PEMC, or the second information indicates acceptance of the first request;

[0331] The PEMC determines the PEGC in the established PIN according to the second information, or establishes a deactivated PIN.

[0332] In one embodiment, the second PINE can be determined by the PIN server sending a second request, that is, during the PIN establishment process, the PIN server sends a second request to the PINE to request it to serve as the PEGC in the PIN. The PINE can then feedback an acceptance response or a rejection response to the PIN server, and the PIN server determines the PINE corresponding to the acceptance response as the second PINE.

[0333] In another embodiment, the second PINE may include a PINE that is supported as a PEGC in the PIN and is determined by the PIN server according to the registration information.

[0334] In another embodiment, the second PINE may include any PINE in the PIN, such as all or part of the PINE.

[0335] In another embodiment, during the PIN registration process, the PIN server may first update the registration information of the PINE to filter the first PINE supported as the PEGC in the PIN, and during the PIN establishment process, request the first PINE to be the PEGC in the established PIN, and determine the first PINE that sends the acceptance response as the second PINE.

[0336] After receiving the second information indicating the second PINE, the PEMC may directly use the second PINE as the PEGC in the PIN it establishes, or request the second PINE to be used as the PEGC in the PIN it establishes.

[0337] As an optional implementation, the method further includes:

[0338] The PEMC sends a third request to the second PINE, wherein the third request is used to request the second PINE to serve as a PEGC in the PIN established by the PEMC.

[0339] In one embodiment, the method further comprises:

[0340] The PEMC receives a third response from the second PINE, wherein the third response is used to indicate that the second PINE accepts or refuses to become a PEGC in the PIN.

[0341] In another embodiment, the PEMC only receives the third response from the second PINE that accepts to become the PEGC in the PIN. In this case, the PEMC defaults to determining that the second PINE that does not receive the third response refuses to become the PEGC in the PIN.

[0342] In this embodiment, during the PIN establishment process, the PIN server indicates to the PEMC a second PINE that can serve as the PEGC in the established PIN. The PEMC then requests the second PINE to serve as the PEGC in the established PIN. During this process, the second PINE may refuse or accept to serve as the PEGC in the PIN, or the second PINE may be unreachable.

[0343] Optionally, in the case where a second PINE refuses to become the PEGC in the PIN established by the PEMC, the first information is also used to request an update of the PEGC in the PIN established by the PEMC, or to instruct the second PINE to completely refuse to become the PEGC in the PIN established by the PEMC.

[0344] In this embodiment, the PEGC information in the PIN can be updated in time to avoid designating the PEGC in the PIN established by the PEMC as the PEGC in the PIN in the subsequent process of establishing the PIN.

[0345] As an optional implementation manner, the second PINE includes:

[0346] A PINE that is the master PEGC of the PIN established by the PEMC;

[0347] The PINE is a secondary PEGC of the PIN established by the PEMC.

[0348] Optionally, the PEMC determines, according to the second information, a PEGC in the established PIN, including at least one of the following:

[0349] In the event that the primary PEGC is unreachable or refuses to become the PEGC in the PIN established by the PEMC, and there is at least one secondary PEGC that does not refuse to become the PEGC in the PIN established by the PEMC, the PEMC uses the secondary PEGC as the primary PEGC in the PIN established by it;

[0350] In the case that the primary PEGC is reachable and does not refuse to become the PEGC in the PIN established by the PEMC, the PEMC uses the primary PEGC as the primary PEGC in the PIN established by it;

[0351] In the case that the primary PEGC is reachable and does not refuse to become the PEGC in the PIN established by the PEMC, the PEMC ignores the target PEGC, wherein the target PEGC is unreachable or refuses to become the PEGC in the PIN established by the PEMC.

[0352] In this embodiment, during the PIN establishment process, if the PIN server indicates a primary PEGC and at least one secondary PEGC, the PEMC gives priority to using the primary PEGC as the PEGC in the PIN it establishes. When the primary PEGC is unreachable or refuses to become the PEGC in the PIN established by the PEMC, the secondary PEGC that does not refuse to become the PEGC in the PIN established by the PEMC can be used as the primary PEGC in the PIN it establishes.

[0353] As an optional implementation manner, the PEMC establishes a deactivated PIN according to the second information, including:

[0354] In the case where the second information is used to accept the first request, if the second information includes eighth indication information, and the eighth indication information is used to indicate that there is no available PEGC in the PIN, or the PIN is not activated, the PEMC establishes a deactivated PIN.

[0355] In this embodiment, if there is no available PEGC in the PIN, and the PIN server accepts the establishment of the PIN, the PIN server may send a second message carrying the eighth indication information to the PEMC to indicate that the PIN establishment is accepted, but there is no available PEGC in the PIN or the PIN is in a deactivated state. In this way, the PEMC may determine, based on the eighth indication information, that a PIN with no available PEGC or deactivated is established. Subsequently, the PEMC may manage the PIN in the PIN with no available PEGC or deactivated PIN to not route data.

[0356] As an optional implementation, the method further includes:

[0357] The PEMC receives seventh information from the PIN server, wherein the seventh information is used to indicate a reason for a PIN establishment failure or a reason for a PIN deactivation.

[0358] Optionally, the seventh information is used to indicate at least one of the following:

[0359] No PEGC available;

[0360] PIN is not activated.

[0361] In this embodiment, if the PIN server refuses to establish the PIN or determines to deactivate the PIN when there is no available PEGC in the PIN, the PIN server may inform the PEMC of the reason for refusing to establish the PIN or deactivating the PIN through the seventh message. Subsequently, based on the reason for the PIN server's refusal to establish the PIN or deactivate the PIN, the PEMC may request to re-establish or re-activate the PIN by requesting to update the PEGC or adding a PINE with management functions to the PIN.

[0362] As an optional implementation, the method further includes:

[0363] The PEMC sends ninth indication information to the PINE in the PIN based on the seventh information or the eighth indication information, where the ninth indication information is used to indicate at least one of the following: no available PEGC in the PIN, no available gateway in the PIN, and the PIN is not activated.

[0364] In this embodiment, when PEMC learns that there is no available PEGC in the PIN, PEMC can send a notification message to the PINE in the PIN. The purpose is to synchronize the status of no available PEGC in the PIN or the PIN is not activated with the PINE in the PIN, so that PINE will not send data to PEMC when there is no gateway in the PIN, resulting in waste of signaling and resources.

[0365] In the embodiment of the present application, the information transmission method performed by the PEMC corresponds to the information processing method performed by the PIN server in the method embodiment shown in Figure 2, and can achieve similar beneficial effects as the method embodiment shown in Figure 2. To avoid repetition, it will not be repeated here.

[0366] Please refer to Figure 4, which is a flowchart of another information transmission method provided in an embodiment of the present application. The execution subject of the information transmission method may be PINE. As shown in Figure 4, the method may include the following steps:

[0367] Step 401: PINE sends a first message to a PIN server.

[0368] The first information includes at least one of the following:

[0369] The third indication information is used to indicate whether the PINE has a gateway capability or not;

[0370] Fourth indication information, used to instruct the PINE to accept or reject being a PEGC in the PIN;

[0371] Parameter information of the PINE.

[0372] It should be noted that the various contents of the above-mentioned first information in the embodiment of the present application have the same meaning and function as the corresponding contents of the first information in the method embodiment shown in Figure 2. For details, please refer to the explanation in Figure 2 and will not be repeated here. In addition, PINE can provide the PIN server with first information for assisting in determining the PEGC in the PIN. For example: whether there is an available PEGC in the PIN, which PEGCs are not accepted as PEGCs in the PIN, whether PEMC can be used as a PEGC in the PIN, etc., when there is no PINE in the PIN that is accepted as a PEGC, how to deal with it, such as: deactivating the PIN, refusing to establish the PIN, or updating the PEGC in the PIN, etc. It can achieve similar beneficial effects as the method embodiment shown in Figure 2. In order to avoid repetition, it will not be repeated here.

[0373] Optionally, the parameter information of the PINE includes at least one of the following:

[0374] The media access control MAC address of the PINE;

[0375] The Internet Protocol (IP) address of the PINE;

[0376] The port number of the PINE;

[0377] Capability information of the PINE.

[0378] Optionally, the capability information of the PINE includes at least one of the following:

[0379] The maximum number of PINEs supported when the PINE is used as a PEGC;

[0380] The maximum transmission rate supported by the PINE;

[0381] The maximum transmission rate supported by PINE as PEGC;

[0382] The maximum number of PINs supported when the PINE is used as a PEGC.

[0383] In a first implementation, the PINE sends first information to the PIN server, including:

[0384] The PINE sends registration information to the PIN server, where the first information includes the registration information, and the registration information is used to indicate whether the PINE has gateway capability or not, or to indicate whether the PINE accepts or does not accept being a PEGC in the PIN.

[0385] In a second embodiment, before the PINE sends the first information to the PIN server, the method further includes:

[0386] The PINE receives a second request from the PIN server, wherein the second request is for requesting the PINE to serve as a PEGC in the PIN;

[0387] The PINE sends first information to the PIN server, including:

[0388] The PINE sends a second response to the PIN server, wherein the second response carries the first information, and the first information indicates whether the PINE accepts or rejects the PEGC in the PIN.

[0389] In a third embodiment, the method further comprises:

[0390] The PINE receives a third request from the PEMC, wherein the third request is used to request the PINE to serve as a PEGC in the PIN established by the PEMC;

[0391] The PINE sends a third response to the PEMC, where the third response is used to indicate whether the PINE accepts or refuses to become a PEGC in the PIN.

[0392] It should be noted that the final PEGC in the PIN can be determined by combining at least one of the above three implementation methods.

[0393] For example: determined based on the registration information and the second request of the PIN server, or determined based on the registration information and the third request of the PEMC, or determined based on the second request of the PIN server and the third request of the PEMC, or determined based on the registration information, the second request of the PIN server and the third request of the PEMC.

[0394] In the embodiment of the present application, the information transmission method performed by PINE corresponds to the information processing method performed by the PIN server in the method embodiment shown in Figure 2, and can achieve similar beneficial effects as the method embodiment shown in Figure 2. To avoid repetition, it will not be repeated here.

[0395] To facilitate understanding of the information processing method and information transmission method provided in the embodiments of the present application, the following four implementations are used as examples to illustrate the interactions between the PIN server, PEMC, and PINE:

[0396] Example 1: After PIN is created, PEMC synchronizes PINE information that cannot become PEGC to the PIN server

[0397] As shown in Figure 5a, the interaction between the PIN server, PEMC, and PINE includes the following steps:

[0398] Step 1: After the PIN is created, the PEMC sends a third request (such as a PIN Creation notification request) to the PEGC indicated by the PIN server. The purpose of this request may include: 1. notifying the PEGC that it is added to the PIN; 2. indicating that PINE-1 is the PEGC in the PIN.

[0399] Step 2: PINE-1 cannot become the PEGC in the PIN indicated by the PEMC due to device issues, capability issues (e.g., user settings, or the maximum number of supported PINs has been reached). Therefore, PINE-1 sends a third response (e.g., PIN creation notification reject) to the PEMC.

[0400] It should be noted that the above steps 1 and 2 are optional steps. For example, if there is no suitable PEGC, the PIN server may instruct the PEMC to become the PEGC in the PIN, then there will be no interaction between steps 1 and 2 for the PEMC.

[0401] Step 3: The PEMC sends a third message to the PIN server (assuming that the message carrying the third message is the first request message). The third message is used to request the PIN server to update the PEGC in the PIN.

[0402] For example: after PEMC receives the PIN creation notification reject message from PINE-1; or after PEMC receives the instruction from the PIN server to become the PEGC in the PIN, and PEMC determines that it cannot become the PEGC, PEMC requests the PIN server to update the PEGC in the PIN.

[0403] Optionally, the first request message carrying the third information may specifically be: a PIN configuration request message, or a PIN creation notification request message.

[0404] It is worth noting that in related technologies, the PIN creation notification request is only used by the PEMC to notify the PEGC that is added to the PIN or to indicate that PINE-1 is the PEGC in the PIN. In the embodiment of the present application, the PIN creation notification request can be reused to request the PIN server to update the PEGC in the PIN.

[0405] Optionally, the first request message includes first indication information, where the first indication information indicates that the PIN is in a deactivated state, or indicates that no PEGC is available in the PIN. The deactivated state of the PIN means that although the PIN is successfully created, it cannot be successfully activated, and the reason may be that there is no available PEGC in the PIN.

[0406] In some implementations, the first request message is a PIN creation notification request message, wherein the PEGC identifier is set to:

[0407] (a) the PINE-1ID (i.e., the PINE that sent the PIN creation notification reject message and refused to become a PEGC); or

[0408] (b) PEMC ID (i.e., the PEMC is instructed to become a PEGC but the PEMC itself does not have the relevant capabilities of the PEGC).

[0409] The PEGC address is set to:

[0410] (a) the PINE-1 address information (i.e., the PINE that sent the PIN creation notification reject message and refused to become a PEGC); or

[0411] (b) PEMC address information (ie, the PEMC is instructed to become a PEGC but the PEMC itself does not have the relevant capabilities of the PEGC).

[0412] The format and content of the PIN creation notification request message are shown in Table 1 below:

[0413] Table 1

[0414] In some implementations, the first request message is a PIN configuration request message, wherein:

[0415] (1) The Authorization type is set to PEGC role change; and

[0416] (2) The PINE ID of the specified role (PINE ID of predecessor in the role) is set to:

[0417] (a) the PINE-1ID (i.e., the PINE that sent the PIN creation notification reject message and refused to become a PEGC); and / or,

[0418] (b) PEMC ID (i.e., the PEMC is instructed to become a PEGC but the PEMC itself does not have the relevant capabilities of the PEGC).

[0419] When both (a) and (b) are included, the PINE ID of predecessor in the role can be understood as a list containing at least one ID information.

[0420] The format and content of the PIN creation notification request message are shown in Table 2 below:

[0421] Table 2

[0422] Step 4: The PIN server receives the first request message sent by the PEMC.

[0423] Optionally, the first request message is a PIN configuration request message or a PIN creation notification request message.

[0424] In some embodiments, the first request message is a PIN creation notification request message. After receiving the PIN creation notification request message sent by the PEMC, the PIN server performs at least one of the following:

[0425] (1) The PINE identified by the Identifier of PEGCs in the PIN creation notification request message is regarded as a PINE in the PIN that cannot become a PEGC;

[0426] (2) Based on the PEGC information sent by the PIN server to the PEMC during the PIN creation process, perform at least one of the following:

[0427] (a) updating the PEGC information in the PIN, the PIN being identified by the PIN ID;

[0428] (b) Sending a PIN creation notification response message to the PEMC, including the PIN server's updated PEGC information in the PIN. If no other PINE besides the PEMC can serve as the PEGC, the PEGC information in the updated PIN is set to the PEMC's information. At this point, the PIN server determines that there is no available PEGC in the PIN.

[0429] In some embodiments, the first request message is a PIN configuration request message. After receiving the PIN configuration request message sent by the PEMC, the PIN server performs at least one of the following:

[0430] (1) The PINE identified by the PINE ID of predecessor in the role in the PIN configuration request message is regarded as a PINE in the PIN that cannot become a PEGC;

[0431] (2) Based on the PEGC information sent by the PIN server to the PEMC during the PIN creation process, perform at least one of the following:

[0432] (a) updating the PEGC information in the PIN, the PIN being identified by the PIN ID;

[0433] (b) Sending a PIN Configuration Response message to the PEMC, including the PIN server's updated PEGC information in the PIN. If no other PINE besides the PEMC can serve as the PEGC, the PEGC information in the updated PIN is set to the PEMC's information. At this point, the PIN server determines that no PEGC is available in the PIN.

[0434] After receiving the PIN configuration response message, the PEMC performs at least one of the following:

[0435] (1) updating the PEGC information in the PIN based on the PEGC information in the PIN updated by the PIN server;

[0436] (2) If the PEGC information in the PIN updated by the PIN server is the PEMC information, and:

[0437] (a) The PIN configuration request message sent by the PEMC meets the following conditions:

[0438] (i) Authorization type is set to PEGC role change; and

[0439] (ii) PINE ID of predecessor in the role (PINE ID of the predecessor in the PEGC role) includes: PEMC ID;

[0440] Then, the PEMC considers that the PIN server has determined that there is no available PEGC in the PIN; or

[0441] (b) If condition (i) or only (ii) is satisfied, or if both (i) and (ii) are not satisfied, the PEMC must confirm whether it can become a PEGC. If the PEMC cannot become a PEGC, then step 3 of this embodiment is executed. That is, at this time, the PEMC satisfies conditions (2)-(b) of step 3: the PEMC receives an instruction from the PIN server to become a PEGC in the PIN, and the PEMC determines that it cannot become a PEGC.

[0442] Example 2: After the PIN is created, the PIN server triggers the update of the PEGC in the PIN to the PEMC

[0443] As shown in Figure 5b, the interaction between the PIN server, PEMC, and PINE includes the following steps:

[0444] Step 1: PINE-2 sends registration information (e.g., a PINE registration request) to a PIN server to register with the PIN server. The PINE registration request message includes indication information indicating at least one of the following: PINE-2 has gateway capability; PINE-2 can become a gateway in a PIN.

[0445] Optionally, the PINE registration request also includes: MAC address, IP address, port number, and capability information. Optionally, the capability information may also be referred to as performance information, such as the maximum number of PINEs supported by the gateway, the maximum supported rate, the maximum number of PINs supported, etc.

[0446] Step 2: The PIN server sends a PINE Registration Accept message to PINE-2, confirming that PINE-2 has successfully registered with the PIN server. It's worth noting that Step 2, as an independent process associated with Step 1, can also be performed after Step 3 or Step 4. The order of Steps 1, 2, 3, and 4 is not limited.

[0447] Step 3: If at least one of the following is met:

[0448] (1) The PEGC information in the PIN changes;

[0449] (2) The PIN server determines that there is no available PEGC in the PIN;

[0450] When the PIN server sends the fourth information to the PEMC (assuming that the fourth information is carried in the second request message), the second request message is used to update the PEGC information in the PIN.

[0451] Optionally, the second request message includes at least one of the following: PIN ID; modification type; PINE ID of predecessor in the role; PIN profile information; dynamic PIN profile information.

[0452] Exemplarily, the second request message may be a PIN configuration command, the contents of which are shown in Table 3 below:

[0453] Table 3

[0454] Step 4: The PEMC responds to the second request message in step 3 to indicate the execution result of step 3.

[0455] Exemplarily, the PEMC may respond to the second request message with a PIN configuration complete message. Exemplarily, the PIN configuration complete message includes at least one of the following: a PIN ID; result information indicating a result of the second request message; a cause value indicating a cause of failure; and a PINE ID of failure indicating a PINE ID of the failed execution.

[0456] For example, the contents of a PIN configuration complete are shown in Table 4 below:

[0457] Table 4

[0458] Example 3: During PIN creation, the PIN server confirms the role of the PEGC

[0459] As shown in Figure 5c, the interaction between the PIN server, PEMC, and PINE includes the following steps:

[0460] Step 1: PEMC sends a PIN Creation request to the PIN server to create a PIN.

[0461] Step 2: After receiving the PIN Creation request from the PEMC, the PIN server performs at least one of the following:

[0462] (1) Identify PINEs (except PEMC) in PIN that can serve as PEGC, such as PINE-3.

[0463] (2) Send a second request (assuming it is carried in a third request message) to PINE-3. The third request message is used to determine whether PINE-3 can become a PEGC in the PIN. If at least one PINE can become a PEGC in the PIN, the third request message is sent to all of these PINEs. In some embodiments, the third request message may be a PIN management request message.

[0464] Step 3: After receiving the third request message from the PIN server, PINE determines whether it can become a PEGC in the PIN and sends a message in response to the third request message. Exemplarily, the response to the third request message is based on a second response (e.g., a PIN management response message).

[0465] Step 4: The PIN server receives the response message from PINE in step 3. Based on the response message, the PIN server performs at least one of the following:

[0466] (1) Update the PINE in PIN to become PEGC information;

[0467] (2) Based on the updated PEGC information, a PIN Creation response message is sent to the PEMC to respond to the PIN Creation request message sent by the PEMC in step 1 (i.e., the PIN Creation response message in the related art is reused).

[0468] It is worth noting that, in some embodiments, if there is no other PINE other than PEMC that can serve as the PEGC in the PIN, the PIN server rejects the PEMC's request to create a PIN, or responds to the PEMC's request to create a PIN, wherein the response message carries indication information, and the indication information indicates that the PIN is in an inactive state, or indicates that there is no available PEGC in the PIN.

[0469] Example 4: During the PIN creation process, the PIN server instructs multiple PEGCs, and only some of the PEGCs reject the PEMC's request

[0470] In this embodiment, the PIN server may indicate one or more PEGCs during the PIN creation process, including a primary PEGC and one or more secondary PEGCs:

[0471] (1) If the primary PEGC refuses to become the PEGC in the PIN or the primary PEGC is unreachable, and there is at least one secondary PEGC that does not refuse the PEMC, the PEMC can use the secondary PEGC as the primary PEGC in the PIN;

[0472] (2) If the primary PEGC does not reject the PEMC's request (and is reachable), the PEMC can use the primary PEGC as the primary PEGC in the PIN and ignore the rejected or unreachable PEGC.

[0473] It is worth noting that the fourth embodiment described above can be used in conjunction with the first embodiment shown in FIG5 a. For example, when at least one PEGC can serve a PIN, the PEMC can also use the first embodiment to report information about the PEGC that cannot serve the PIN to the PIN server while ignoring rejected or unreachable PEGCs.

[0474] The fourth embodiment described above can be used in combination with the second embodiment shown in Figure 5b. For example, when at least one PEGC can serve the PIN, the PIN server can also update the PEGC information to the PIN.

[0475] The fourth embodiment described above can be used in conjunction with the third embodiment shown in Figure 5c. For example, during PIN creation, the PIN server confirms that a certain PINE can serve as the PEGC in the PIN. However, for some reason, a certain PEGC, although agreed to serve as the PEGC, is unreachable in the PIN notification message. If the primary PEGC is unreachable, the PEMC can use the secondary PEGC as the primary PEGC in the PIN. If the secondary PEGC is unreachable, the PEMC can use the primary PEGC as the primary PEGC in the PIN and ignore the rejected or unreachable PEGC.

[0476] The above-mentioned fourth embodiment, the first embodiment as shown in FIG5a , and the third embodiment as shown in FIG5c can be used in combination. For example, the PIN server confirms that a certain PINE can be used as the PEGC in the PIN during the creation of the PIN. However, for some reason, although a certain PEGC agrees to be used as the PEGC, it is unreachable in the PIN notification message: if the primary PEGC is unreachable, the PEMC can use the secondary PEGC as the primary PEGC in the PIN; if the secondary PEGC is unreachable, the PEMC can use the primary PEGC as the primary PEGC in the PIN and ignore the rejected or unreachable PEGC. Thereafter, the PEMC can also use the first embodiment to report the information of the PEGC that cannot serve the PIN to the PIN server while ignoring the rejected or unreachable PEGC.

[0477] The information processing method provided in the embodiment of the present application can be executed by an information processing device. In the embodiment of the present application, the information processing device provided in the embodiment of the present application is described by taking the information processing device executing the information processing method as an example.

[0478] Please refer to FIG. 6 . The information processing device 600 provided in the embodiment of the present application may be a device within a PIN server.

[0479] As shown in FIG6 , the information processing device 600 may include the following modules:

[0480] The first receiving module 601 is configured to receive first information, where the first information satisfies at least one of the following conditions:

[0481] The first information is related to a PIN element PEGC having gateway capability;

[0482] The first information includes a first request, and the first request is used to request to establish a PIN;

[0483] The first execution module 602 is configured to execute a first operation according to the first information, wherein the first operation includes at least one of the following:

[0484] Determine the PEGC information in the PIN;

[0485] rejecting the first request;

[0486] Deactivate PIN;

[0487] Update the personal Internet of Things network element PINE information of PEGC in PIN;

[0488] Sending second information to the PIN element PEMC with management function, wherein the second information is used to indicate that the PINE as PEGC is accepted in the PIN, or the second information indicates acceptance of the first request.

[0489] Optionally, the second information indicating that the PINE is accepted as PEGC in the PIN includes at least one of the following:

[0490] The second information indicates a PINE that is a primary PEGC in the PIN established by the PEMC;

[0491] The second information indicates a PINE that is a secondary PEGC in the PIN established by the PEMC.

[0492] Optionally, the first receiving module 601 is specifically configured to:

[0493] The PIN server receives the first information from the PEMC or PINE.

[0494] Optionally, the first information includes at least one of the following:

[0495] The first identification information is used to identify the PINE that does not accept becoming a PEGC in the PIN;

[0496] The second identification information is used to identify the PEMC that does not have the gateway capability;

[0497] The first indication information is used to indicate that the PIN is in a deactivated state or that there is no available PEGC in the PIN;

[0498] Second indication information, used to indicate that the PINE corresponding to the first identification information does not accept becoming a PEGC in a PIN, or that the PEMC corresponding to the second identification information does not have a gateway capability;

[0499] The third indication information is used to indicate whether the PINE has a gateway capability or not;

[0500] Fourth indication information, used to instruct PINE to accept or reject as a PEGC in PIN;

[0501] PINE parameter information;

[0502] The first request.

[0503] Optionally, the parameter information of the PINE includes at least one of the following:

[0504] PINE's media access control MAC address;

[0505] PINE's Internet Protocol (IP) address;

[0506] PINE's port number;

[0507] PINE's ability information.

[0508] Optionally, the capability information of the PINE includes at least one of the following:

[0509] The maximum number of PINEs supported when PINE is used as PEGC;

[0510] The maximum transfer rate supported by PINE;

[0511] The maximum transmission rate supported by PINE as PEGC;

[0512] Maximum number of PINs supported when PINE is used as PEGC.

[0513] Optionally, the first execution module 602 is specifically configured to:

[0514] If the PIN server determines, based on the first information, that there is no available PEGC in the PIN, the first request is rejected, or the PIN is deactivated, or the first request is accepted.

[0515] Optionally, the first execution module 602 is further configured to:

[0516] Sending seventh information to the PEMC, where the seventh information is used to indicate a reason for a PIN establishment failure or a reason for a PIN deactivation.

[0517] Optionally, the seventh information is used to indicate at least one of the following:

[0518] No PEGC available;

[0519] PIN is not activated.

[0520] Optionally, the first execution module 602 is further configured to:

[0521] Second information is sent to the PEMC, where the second information is used to accept the first request, and the second information includes eighth indication information, where the eighth indication information is used to indicate that there is no available PEGC in the PIN, or the PIN is not activated.

[0522] Optionally, there is no available PEGC in the PIN, including:

[0523] The PEGC indicated by the PIN server to the PEMC refuses to become the PEGC in the PIN established by the PEMC, or the PEGC indicated by the PIN server to the PEMC is unreachable, or there is no PINE that accepts it as the PEGC in the PIN established by the PEMC;

[0524] The PEMC does not have gateway capabilities.

[0525] Optionally, when the first information includes the first request from the PEMC, the first execution module 602 is further configured to:

[0526] According to the first request, second information is sent to the PEMC, wherein the second information includes third identification information, and the third identification information is used to identify the PINE indicated by the PIN server as the PEGC in the PIN established by the PEMC, or the second information indicates that the PEMC requests the PINE identified by the third identification information as the PEGC in the PIN established by the PEMC.

[0527] Optionally, the first receiving module 601 is specifically configured to:

[0528] Receive third information from the PEMC, wherein the first information also includes the third information, and the third information is used to request an update of the PEGC in the PIN established by the PEMC, or to indicate that all PINEs corresponding to the third identification information refuse to become PEGCs in the PIN established by the PEMC, or that the PEMC does not have gateway capability.

[0529] Optionally, the third identification information is used to identify at least one of the following:

[0530] A PINE that is a primary PEGC in a PIN established by the PEMC;

[0531] The PINE is a secondary PEGC in the PIN established by the PEMC.

[0532] Optionally, the first execution module 602 is specifically configured to:

[0533] updating, according to the first information, the PINE information of the PEGC accepted as the PIN established by the PEMC;

[0534] sending, to the PEMC, updated identification information of the PINE that accepts becoming the PEGC in the PIN established by the PEMC, based on the first information;

[0535] Sending identification information of the PEMC to the PEMC according to the first information, instructing the PEMC to serve as a PEGC in the PIN established by it;

[0536] A first response is sent to the PEMC according to the first information, where the first response is used to reject the first request, or deactivate the PIN established by the PEMC, or receive the first request.

[0537] Optionally, the first information further includes fifth indication information, wherein the fifth indication information is used to indicate that the PIN established by the PEMC is in a deactivated state, or to indicate that there is no available PEGC in the PIN established by the PEMC.

[0538] Optionally, the first receiving module 601 is specifically configured to:

[0539] Registration information is received from a PINE, where the first information includes the registration information, and the registration information includes indication information indicating whether the PINE has or does not have gateway capability, or whether the PINE accepts or does not accept being a PEGC in a PIN.

[0540] Optionally, the first execution module 602 is specifically configured to execute at least one of the following:

[0541] The PIN server determines, based on the registration information, to accept the PINE as the PEGC in the PIN;

[0542] When the PIN server determines, based on the registration information, that the PINE accepted as the PEGC in the PIN has changed, the PIN server sends fourth information to the PEMC of the PIN, or determines that there is no available PEGC in the PIN, wherein the fourth information indicates the changed PINE accepted as the PEGC in the PIN;

[0543] Upon receiving the first request from the PEMC, if the PIN server determines that there is a target PINE among the registered PINEs that accepts being used as the PEGC in the PIN established by the PEMC, the PIN server sends sixth indication information to the PEMC, wherein the sixth indication information instructs the PEMC to request the target PINE to be used as the PEGC in the PIN established by the PEMC; or

[0544] When the PIN server receives the first request from the PEMC, if it determines that there is no target PINE among the registered PINEs that accepts the PEGC in the PIN established by the PEMC, it sends seventh indication information to the PEMC, wherein the seventh indication information instructs the PEMC to be the PEGC in the PIN established by it, or indicates that the PIN established by the PEMC is in a deactivated state, or rejects the PEMC from establishing the PIN.

[0545] Optionally, the fourth information includes at least one of the following:

[0546] the identification information of the changed PINE accepted as the PEGC in the PIN;

[0547] Modification type;

[0548] identification information of the PIN;

[0549] PIN profile information;

[0550] Dynamic PIN profile information.

[0551] Optionally, when the first information includes the first request from the PEMC, the first execution module 602 is further configured to:

[0552] Sending a second request to the first PINE, wherein the second request is used to request the first PINE to serve as a PEGC in the PIN established by the PEMC;

[0553] The first receiving module 601 is further configured to:

[0554] A second response is received from the first PINE, wherein the second response carries first information, and the first information indicates that the first PINE accepts or rejects the PEGC in the PIN established by the PEMC.

[0555] Optionally, the first execution module 602 is further configured to execute at least one of the following:

[0556] updating, according to the second response, PINE information of the PEGC accepted as part of the PIN established by the PEMC;

[0557] sending identification information of a target first PINE to the PEMC according to the second response, wherein the target first PINE is a first PINE that accepts the PEGC in the PIN established by the PEMC;

[0558] sending identification information of the PEMC to the PEMC according to the second response, instructing the PEMC to serve as a PEGC in the PIN established by the PEMC;

[0559] According to the second response, a first response is sent to the PEMC, wherein the first response is used to respond to the first request.

[0560] Optionally, the first execution module 602 is further configured to:

[0561] Fifth information is received from the PEMC, where the fifth information indicates whether the PEMC accepts or does not accept the PEGC in the PIN established by the PEMC, or whether the PEMC has or does not have gateway capability.

[0562] Optionally, when the PIN server determines that there is no available PEGC in the PIN established by the PEMC, the first response is used to reject the first request, or to deactivate the PIN established by the PEMC, or to accept the first request.

[0563] Optionally, the first information further includes PEMC-related information or PIN-related information;

[0564] The first operation further includes:

[0565] The sixth information is updated, where the sixth information includes at least one of the following:

[0566] PEMC information;

[0567] PIN profile information.

[0568] The information processing device 600 provided in the embodiment of the present application can implement each process implemented by the method embodiment shown in Figure 2 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0569] The information transmission method provided in the embodiment of the present application can be executed by an information transmission device. In the embodiment of the present application, the information transmission device provided in the embodiment of the present application is described by taking the information transmission method executed by the information transmission device as an example.

[0570] Please refer to FIG. 7 . The information transmission device 700 provided in the embodiment of the present application may be a device within a PEMC.

[0571] As shown in FIG7 , the information transmission device 700 may include the following modules:

[0572] A first sending module 701 is configured to send first information to a PIN server;

[0573] Wherein, the first information includes at least one of the following:

[0574] The first identification information is used to identify the PINE that does not accept becoming a PEGC in the PIN;

[0575] The second identification information is used to identify the PEMC, where the PEMC does not have a gateway capability;

[0576] First indication information, used to indicate that the PIN established by the PEMC is in a deactivated state or that there is no available PEGC in the PIN;

[0577] Second indication information, used to indicate that the PINE corresponding to the first identification information does not accept becoming a PEGC in a PIN, or that the PEMC corresponding to the second identification information does not have a gateway capability;

[0578] A first request is used to request to establish a PIN.

[0579] Optionally, the information transmission device 700 further includes:

[0580] a second receiving module, configured to receive second information from the PIN server, wherein the second information is used to indicate that the second PINE as the PEGC is accepted in the PIN established by the PEMC, or the second information indicates acceptance of the first request;

[0581] The second execution module is configured to determine the PEGC in the established PIN according to the second information, or to establish a deactivated PIN.

[0582] Optionally, the information transmission device 700 further includes:

[0583] The third sending module is configured to send a third request to the second PINE, wherein the third request is used to request the second PINE to serve as the PEGC in the PIN established by the PEMC.

[0584] Optionally, the information transmission device 700 further includes:

[0585] The third receiving module is configured to receive a third response from the second PINE, wherein the third response is used to indicate whether the second PINE accepts or refuses to become a PEGC in the PIN.

[0586] Optionally, the first information is further used to request updating of the PEGC in the PIN established by the PEMC, or to instruct the second PINE to completely refuse to become the PEGC in the PIN established by the PEMC.

[0587] Optionally, the second PINE includes:

[0588] A PINE that is the master PEGC of the PIN established by the PEMC;

[0589] The PINE is a secondary PEGC of the PIN established by the PEMC.

[0590] Optionally, the second execution module is specifically configured to execute at least one of the following:

[0591] In the event that the primary PEGC is unreachable or refuses to become the PEGC in the PIN established by the PEMC, and there is at least one secondary PEGC that does not refuse to become the PEGC in the PIN established by the PEMC, the PEMC uses the secondary PEGC as the primary PEGC in the PIN established by it;

[0592] In the case that the primary PEGC is reachable and does not refuse to become the PEGC in the PIN established by the PEMC, the PEMC uses the primary PEGC as the primary PEGC in the PIN established by it;

[0593] In the case that the primary PEGC is reachable and does not refuse to become the PEGC in the PIN established by the PEMC, the PEMC ignores the target PEGC, wherein the target PEGC is unreachable or refuses to become the PEGC in the PIN established by the PEMC.

[0594] Optionally, the second execution module is further configured to:

[0595] In the case where the second information is used to accept the first request, if the second information includes eighth indication information, and the eighth indication information is used to indicate that there is no available PEGC in the PIN, or the PIN is not activated, a deactivated PIN is established.

[0596] Optionally, the information transmission device 700 further includes:

[0597] The sixth receiving module is configured to receive seventh information from the PIN server, wherein the seventh information is used to indicate a reason for a PIN establishment failure or a reason for a PIN deactivation.

[0598] Optionally, the seventh information is used to indicate at least one of the following:

[0599] No PEGC available;

[0600] PIN is not activated.

[0601] Optionally, the information transmission device 700 further includes:

[0602] The fifth sending module is used to send ninth indication information to the PINE in the PIN based on the seventh information or the eighth indication information, where the ninth indication information is used to indicate at least one of the following: no available PEGC in the PIN, no available gateway in the PIN, and the PIN is not activated.

[0603] The information transmission device 700 provided in the embodiment of the present application can implement each process implemented by the method embodiment shown in Figure 3 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0604] Please refer to FIG. 8 . The information transmission device 800 provided in the embodiment of the present application may be a device within PINE.

[0605] As shown in FIG8 , the information transmission device 800 may include the following modules:

[0606] The second sending module 801 is used to send the first information to the PIN server;

[0607] The first information includes at least one of the following:

[0608] The third indication information is used to indicate whether the PINE has a gateway capability or not;

[0609] Fourth indication information, used to instruct PINE to accept or reject as a PEGC in PIN;

[0610] PINE parameter information.

[0611] Optionally, the parameter information of the PINE includes at least one of the following:

[0612] The media access control MAC address of the PINE;

[0613] The Internet Protocol (IP) address of the PINE;

[0614] The port number of the PINE;

[0615] Capability information of the PINE.

[0616] Optionally, the capability information of the PINE includes at least one of the following:

[0617] The maximum number of PINEs supported when the PINE is used as a PEGC;

[0618] The maximum transmission rate supported by the PINE;

[0619] The maximum transmission rate supported by PINE as PEGC;

[0620] The maximum number of PINs supported when the PINE is used as a PEGC.

[0621] Optionally, the second sending module 801 is specifically configured to:

[0622] Sending registration information to a PIN server, where the first information includes the registration information, and the registration information is used to indicate whether the PINE has or does not have gateway capability, or to indicate whether the PINE accepts or does not accept being a PEGC in a PIN.

[0623] Optionally, the information transmission device 800 further includes:

[0624] a fourth receiving module, configured to receive a second request from the PIN server, wherein the second request is used to request the PINE to serve as a PEGC in the PIN;

[0625] The second sending module 801 is further configured to:

[0626] A second response is sent to the PIN server, wherein the second response carries the first information, and the first information indicates whether the PINE is accepted or rejected as a PEGC in the PIN.

[0627] Optionally, the information transmission device 800 further includes:

[0628] a fifth receiving module, configured to receive a third request from the PEMC, wherein the third request is used to request the PINE to serve as a PEGC in the PIN established by the PEMC;

[0629] The fourth sending module is configured to send a third response to the PEMC, wherein the third response is used to instruct the PINE to accept or refuse to become the PEGC in the PIN.

[0630] The information transmission device 800 provided in the embodiment of the present application can implement each process implemented by the method embodiment shown in Figure 4 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0631] As shown in Figure 9, an embodiment of the present application further provides a communication device 900, including a processor 901 and a memory 902, wherein the memory 902 stores programs or instructions that can be run on the processor 901. For example, when the communication device 900 is a PIN server, the program or instruction is executed by the processor 901 to implement the various steps of the method embodiment shown in Figure 2, and can achieve the same technical effect. When the communication device 900 is a PEMC, the program or instruction is executed by the processor 901 to implement the various steps of the method embodiment shown in Figure 3, and can achieve the same technical effect. When the communication device 900 is a PINE, the program or instruction is executed by the processor 901 to implement the various steps of the method embodiment shown in Figure 4, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0632] The present application also provides a terminal comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in FIG3 or FIG4 . This terminal embodiment corresponds to the above-described PEMC-side method embodiment or PINE-side method embodiment. The various implementation processes and implementation methods of the above-described method embodiments are applicable to this terminal embodiment and can achieve the same technical effects. Specifically, FIG10 is a schematic diagram of the hardware structure of a terminal implementing an embodiment of the present application.

[0633] The terminal 1000 includes but is not limited to: a radio frequency unit 1001, a network module 1002, an audio output unit 1003, an input unit 1004, a sensor 1005, a display unit 1006, a user input unit 1007, an interface unit 1008, a memory 1009 and at least some of the components of the processor 1010.

[0634] Those skilled in the art will appreciate that the terminal 1000 may also include a power supply (such as a battery) to power various components. The power supply may be logically connected to the processor 1010 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The terminal structure shown in FIG10 does not limit the terminal. The terminal may include more or fewer components than shown, or may combine certain components, or have different component arrangements, which will not be described in detail here.

[0635] It should be understood that in an embodiment of the present application, the input unit 1004 may include a graphics processing unit (GPU) 10041 and a microphone 10042, and the graphics processor 10041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 1006 may include a display panel 10061, and the display panel 10061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1007 includes a touch panel 10071 and at least one of other input devices 10072. The touch panel 10071 is also called a touch screen. The touch panel 10071 may include two parts: a touch detection device and a touch controller. Other input devices 10072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and an operating stick, which will not be repeated here.

[0636] In the embodiment of the present application, after receiving downlink data from a network-side device, the RF unit 1001 may transmit the data to the processor 1010 for processing. Furthermore, the RF unit 1001 may send uplink data to the network-side device. Typically, the RF unit 1001 includes, but is not limited to, an antenna, an amplifier, a transceiver, a coupler, a low-noise amplifier, a duplexer, and the like.

[0637] The memory 1009 can be used to store software programs or instructions and various data. The memory 1009 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, the memory 1009 may include a volatile memory or a non-volatile memory. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM), and a direct memory bus random access memory (DRRAM). The memory 1009 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

[0638] Processor 1010 may include one or more processing units. Optionally, processor 1010 integrates an application processor and a modem processor. The application processor primarily handles operations related to the operating system, user interface, and application programs, while the modem processor primarily processes wireless communication signals, such as a baseband processor. It is understood that the modem processor may not be integrated into processor 1010.

[0639] In one implementation, the terminal 1000 serves as a PEMC.

[0640] The radio frequency unit 1001 is configured to send the first information to the PIN server;

[0641] Wherein, the first information includes at least one of the following:

[0642] The first identification information is used to identify the PINE that does not accept becoming a PEGC in the PIN;

[0643] Second identification information is used to identify the PEMC, and the PEMC does not have a gateway capability;

[0644] First indication information, used to indicate that the PIN established by the PEMC is in a deactivated state or that there is no available PEGC in the PIN;

[0645] Second indication information, used to indicate that the PINE corresponding to the first identification information does not accept becoming a PEGC in a PIN, or that the PEMC corresponding to the second identification information does not have a gateway capability;

[0646] A first request is used to request to establish a PIN.

[0647] Optionally, the radio frequency unit 1001 is further configured to receive second information from the PIN server, wherein the second information is used to indicate that the second PINE as the PEGC is accepted in the PIN established by the PEMC, or the second information indicates acceptance of the first request;

[0648] The processor 1010 is configured to determine, according to the second information, a PEGC in the established PIN, or to establish a deactivated PIN.

[0649] Optionally, the radio frequency unit 1001 is further configured to send a third request to the second PINE, wherein the third request is used to request the second PINE to serve as the PEGC in the PIN established by the PEMC.

[0650] Optionally, the radio frequency unit 1001 is further configured to receive a third response from the second PINE, wherein the third response is used to indicate that the second PINE accepts or refuses to become a PEGC in the PIN.

[0651] Optionally, the first information is further used to request updating of the PEGC in the PIN established by the PEMC, or to instruct the second PINE to completely refuse to become the PEGC in the PIN established by the PEMC.

[0652] Optionally, the second PINE includes:

[0653] A PINE that is the master PEGC of the PIN established by the PEMC;

[0654] The PINE is a secondary PEGC of the PIN established by the PEMC.

[0655] Optionally, the determining, by the processor 1010, of the PEGC in the established PIN according to the second information includes at least one of the following:

[0656] In the event that the primary PEGC is unreachable or refuses to become the PEGC in the PIN established by the PEMC, and there is at least one secondary PEGC that does not refuse to become the PEGC in the PIN established by the PEMC, use the secondary PEGC as the primary PEGC in the PIN established by it;

[0657] In the case that the primary PEGC is reachable and does not refuse to become the PEGC in the PIN established by the PEMC, using the primary PEGC as the primary PEGC in the PIN established by it;

[0658] In case the primary PEGC is reachable and does not refuse to become the PEGC in the PIN established by the PEMC, a target PEGC is ignored, wherein the target PEGC is unreachable or refuses to become the PEGC in the PIN established by the PEMC.

[0659] Optionally, the step of establishing a deactivated PIN according to the second information executed by the processor 1010 includes:

[0660] In the case where the second information is used to accept the first request, if the second information includes eighth indication information, and the eighth indication information is used to indicate that there is no available PEGC in the PIN, or the PIN is not activated, a deactivated PIN is established.

[0661] Optionally, the radio frequency unit 1001 is further configured to receive seventh information from the PIN server, wherein the seventh information is used to indicate a reason for a PIN establishment failure or a reason for a PIN deactivation.

[0662] Optionally, the seventh information is used to indicate at least one of the following:

[0663] No PEGC available;

[0664] PIN is not activated.

[0665] Optionally, the radio frequency unit 1001 is further used to send ninth indication information to the PINE in the PIN based on the seventh information or the eighth indication information, where the ninth indication information is used to indicate at least one of the following: there is no available PEGC in the PIN, there is no available gateway in the PIN, and the PIN is not activated.

[0666] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the information transmission method embodiment shown in Figure 3, and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.

[0667] In another embodiment, the terminal 1000 functions as a PINE.

[0668] The radio frequency unit 1001 is configured to send the first information to the PIN server;

[0669] The first information includes at least one of the following:

[0670] The third indication information is used to indicate whether the PINE has a gateway capability or not;

[0671] Fourth indication information, used to instruct the PINE to accept or reject being a PEGC in the PIN;

[0672] Parameter information of the PINE.

[0673] Optionally, the parameter information of the PINE includes at least one of the following:

[0674] The media access control MAC address of the PINE;

[0675] The Internet Protocol (IP) address of the PINE;

[0676] The port number of the PINE;

[0677] Capability information of the PINE.

[0678] Optionally, the capability information of the PINE includes at least one of the following:

[0679] The maximum number of PINEs supported when the PINE is used as a PEGC;

[0680] The maximum transmission rate supported by the PINE;

[0681] The maximum transmission rate supported by PINE as PEGC;

[0682] The maximum number of PINs supported when the PINE is used as a PEGC.

[0683] Optionally, the sending of the first information to the PIN server performed by the radio frequency unit 1001 includes:

[0684] Sending registration information to a PIN server, where the first information includes the registration information, and the registration information is used to indicate whether the PINE has or does not have gateway capability, or to indicate whether the PINE accepts or does not accept being a PEGC in a PIN.

[0685] Optionally, the radio frequency unit 1001 is further configured to receive a second request from the PIN server, where the second request is used to request the PINE to serve as a PEGC in the PIN;

[0686] The sending of the first information to the PIN server performed by the radio frequency unit 1001 includes:

[0687] A second response is sent to the PIN server, wherein the second response carries the first information, and the first information indicates whether the PINE is accepted or rejected as a PEGC in the PIN.

[0688] Optionally, the radio frequency unit 1001 is further configured to:

[0689] receiving a third request from the PEMC, wherein the third request is used to request the PINE to serve as a PEGC in the PIN established by the PEMC;

[0690] A third response is sent to the PEMC, wherein the third response is used to indicate that the PINE accepts or refuses to become a PEGC in the PIN.

[0691] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the information transmission method embodiment shown in Figure 4, and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.

[0692] An embodiment of the present application further provides a network-side device, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the method embodiment shown in Figure 2, Figure 3, or Figure 4. This network-side device embodiment corresponds to the aforementioned PIN server-side method embodiment, PEMC-side method embodiment, or PINE-side method embodiment. Each implementation process and implementation method of the aforementioned method embodiments are applicable to this network-side device embodiment and can achieve the same technical effects.

[0693] Specifically, embodiments of the present application also provide a network-side device. As shown in Figure 11, the network-side device 1100 includes an antenna 1101, a radio frequency device 1102, a baseband device 1103, a processor 1104, and a memory 1105. Antenna 1101 is connected to radio frequency device 1102. In the uplink direction, radio frequency device 1102 receives information via antenna 1101 and sends the received information to baseband device 1103 for processing. In the downlink direction, baseband device 1103 processes the information to be transmitted and sends it to radio frequency device 1102. Radio frequency device 1102 processes the received information and then sends it through antenna 1101.

[0694] The method executed by the network-side device in the above embodiment may be implemented in the baseband device 1103 , which includes a baseband processor.

[0695] The baseband device 1103 may, for example, include at least one baseband board, on which multiple chips are arranged, as shown in Figure 11, one of the chips is, for example, a baseband processor, which is connected to the memory 1105 through a bus interface to call the program in the memory 1105 and execute the network device operations shown in the above method embodiment.

[0696] The network side device may further include a network interface 1106 , which is, for example, a Common Public Radio Interface (CPRI).

[0697] Specifically, the network side device 1100 of the embodiment of the present application also includes: instructions or programs stored in the memory 1105 and executable on the processor 1104. The processor 1104 calls the instructions or programs in the memory 1105 to execute the methods executed by the modules shown in FIG6 or FIG7 or FIG8 and achieve the same technical effect. To avoid repetition, they will not be elaborated here.

[0698] Specifically, the embodiment of the present application further provides a network-side device. As shown in FIG12 , the network-side device 1200 includes: a processor 1201, a network interface 1202, and a memory 1203. The network interface 1202 is, for example, a Common Public Radio Interface (CPRI).

[0699] Specifically, the network side device 1200 of the embodiment of the present application also includes: instructions or programs stored in the memory 1203 and executable on the processor 1201. The processor 1201 calls the instructions or programs in the memory 1203 to execute the method executed by each module as shown in Figure 6 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0700] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the method embodiment shown in Figure 2 or Figure 3 or Figure 4 are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0701] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk. In some examples, the readable storage medium may be a non-transitory readable storage medium.

[0702] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the method embodiment shown in Figure 2 or Figure 3 or Figure 4, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0703] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0704] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium and is executed by at least one processor to implement the various processes of the method embodiment shown in Figure 2 or Figure 3 or Figure 4, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0705] An embodiment of the present application also provides a communication system, including: a PIN server, a PEMC, and a PINE. The PIN server can be used to execute the steps of the method embodiment shown in Figure 2, the PEMC can be used to execute the steps of the method embodiment shown in Figure 3, and the PINE can be used to execute the steps of the method embodiment shown in Figure 4.

[0706] It should be noted that, in this article, the terms "comprise", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the presence of other identical elements in the process, method, article or device comprising the element. In addition, it should be noted that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in the opposite order according to the functions involved. For example, the described method may be performed in an order different from that described, and various steps may also be added, omitted or combined. In addition, the features described with reference to certain examples, embodiments or embodiments may be combined in other examples, embodiments or embodiments.

[0707] Through the description of the above embodiments, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of a computer software product plus a hardware platform, or of course, by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, magnetic disk, optical disk, etc.) and includes a number of instructions for enabling a terminal or network-side device to execute the methods described in each embodiment of the present application.

[0708] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of this application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of this application and the scope of protection of the claims. These implementation methods are all within the protection of this application.

Claims

1. An information processing method, comprising: The personal Internet of Things PIN server receives first information, wherein the first information satisfies at least one of the following: The first information is related to a PIN element PEGC having gateway capability; The first information includes a first request, and the first request is used to request to establish a PIN; The PIN server performs a first operation according to the first information, wherein the first operation includes at least one of the following: Determine the PEGC information in the PIN; rejecting the first request; Deactivate PIN; Update the personal Internet of Things network element PINE information of PEGC in PIN; Sending second information to the PIN element PEMC having management function, wherein the second information is used to indicate that the PINE as the PEGC is accepted in the PIN, or the second information indicates acceptance of the first request.

2. The method according to claim 1, wherein: The second information indicates that the PINE is accepted as the PEGC in the PIN, including at least one of the following: The second information indicates a PINE that is a primary PEGC in the PIN established by the PEMC; The second information indicates a PINE which is a secondary PEGC in a PIN established by the PEMC.

3. The method according to claim 1 or 2, wherein: The PIN server receives first information, including: The PIN server receives the first information from the PEMC or PINE.

4. The method according to any one of claims 1 to 3, wherein: The first information includes at least one of the following: The first identification information is used to identify the PINE that does not accept becoming a PEGC in the PIN; The second identification information is used to identify the PEMC that does not have the gateway capability; The first indication information is used to indicate that the PIN is in a deactivated state or that there is no available PEGC in the PIN; The second indication information is used to indicate that the PINE corresponding to the first identification information does not accept to become a PEGC in the PIN, or the PEMC corresponding to the second identification information does not have a gateway capability; The third indication information is used to indicate whether the PINE has a gateway capability or not; Fourth indication information, used to instruct PINE to accept or reject as PEGC in PIN; PINE parameter information; The first request.

5. The method according to claim 4, wherein: The parameter information of the PINE includes at least one of the following: PINE's media access control MAC address; PINE's Internet Protocol (IP) address; The port number of PINE; PINE's capabilities information.

6. The method according to claim 5, wherein: The capability information of the PINE includes at least one of the following: The maximum number of PINEs supported when PINE is used as PEGC; The maximum transfer rate supported by PINE; The maximum transmission rate supported by PINE as PEGC; Maximum number of PINs supported when PINE is used as PEGC.

7. The method according to any one of claims 1 to 6, wherein: The PIN server performs a first operation according to the first information, including: When the PIN server determines, based on the first information, that there is no available PEGC in the PIN, the first request is rejected, or the PIN is deactivated, or the first request is accepted.

8. The method according to claim 7, wherein: The rejecting the first request, or deactivating the PIN, comprises: The PIN server sends seventh information to the PEMC, where the seventh information is used to indicate a reason for a PIN establishment failure or a reason for a PIN deactivation.

9. The method according to claim 8, wherein: The seventh information is used to indicate at least one of the following: No PEGC available; PIN is not activated.

10. The method according to claim 7, wherein: The accepting the first request comprises: The PIN server sends second information to the PEMC, where the second information is used to accept the first request, and the second information includes eighth indication information, where the eighth indication information is used to indicate that there is no available PEGC in the PIN, or the PIN is not activated.

11. The method according to any one of claims 7 to 10, wherein: There are no PEGCs available in the PIN, including: The PEGC indicated by the PIN server to the PEMC refuses to become the PEGC in the PIN established by the PEMC, or the PEGC indicated by the PIN server to the PEMC is unreachable, or there is no PINE that accepts being the PEGC in the PIN established by the PEMC; The PEMC does not have gateway capabilities.

12. The method according to any one of claims 1 to 11, wherein: In a case where the first information includes the first request from the PEMC, the PIN server performs a first operation according to the first information, including: The PIN server sends second information to the PEMC based on the first request, wherein the second information includes third identification information, and the third identification information is used to identify the PINE indicated by the PIN server as the PEGC in the PIN established by the PEMC, or the second information indicates that the PEMC requests the PINE identified by the third identification information as the PEGC in the PIN established by the PEMC.

13. The method according to claim 12, wherein: The PIN server receives the first information, further comprising: The PIN server receives third information from the PEMC, wherein the first information also includes the The third information is used to request to update the PEGC in the PIN established by the PEMC, or to indicate that all PINEs corresponding to the third identification information refuse to become the PEGC in the PIN established by the PEMC, or that the PEMC does not have gateway capability.

14. The method according to claim 12 or 13, wherein: The third identification information is used to identify at least one of the following: A PINE that is a master PEGC in a PIN established by the PEMC; The PINE is a secondary PEGC in the PIN established by the PEMC.

15. The method according to any one of claims 12 to 14, wherein: The PIN server performs at least one of the following according to the first information: The PIN server updates the PINE information of the PEGC in the PIN established by the PEMC according to the first information; The PIN server sends, to the PEMC, based on the first information, updated identification information of the PINE that accepts to become the PEGC in the PIN established by the PEMC; The PIN server sends the identification information of the PEMC to the PEMC according to the first information, indicating the PEMC as the PEGC in the PIN established by it; The PIN server sends a first response to the PEMC according to the first information, where the first response is used to reject the first request, or to deactivate the PIN established by the PEMC, or to receive the first request.

16. The method according to any one of claims 12 to 15, wherein: The first information also includes fifth indication information, wherein the fifth indication information is used to indicate that the PIN established by the PEMC is in a deactivated state, or to indicate that there is no available PEGC in the PIN established by the PEMC.

17. The method according to any one of claims 1 to 16, wherein: The PIN server receives first information, including: The PIN server receives registration information from a PINE, wherein the first information includes the registration information, and the registration information includes indication information for indicating whether the PINE has or does not have gateway capability, or whether the PINE accepts or does not accept being a PEGC in a PIN.

18. The method according to claim 17, wherein: The PIN server performs a first operation according to the first information, including at least one of the following: The PIN server determines, based on the registration information, to accept the PINE as the PEGC in the PIN; When the PIN server determines, according to the registration information, that the PINE accepted as the PEGC in the PIN has changed, the PIN server sends fourth information to the PEMC of the PIN, or determines that there is no available PEGC in the PIN, wherein the fourth information indicates the changed PINE accepted as the PEGC in the PIN; When the PIN server receives the first request from the PEMC, if it is determined that there is a target PINE among the registered PINEs that accepts the PEGC in the PIN established by the PEMC, the PIN server sends sixth indication information to the PEMC, wherein the sixth indication information instructs the PEMC to request the target PINE to be the PEGC in the PIN established by the PEMC; or When the PIN server receives the first request from the PEMC, if it determines that there is no target PINE among the registered PINEs that accepts the PEGC in the PIN established by the PEMC, it sends the seventh indication information to the PEMC, wherein the seventh indication information indicates the PEMC as the PEGC in the PIN established by it, or indicates that the PIN established by the PEMC is in a deactivated state, or rejects the PEMC from establishing the PIN.

19. The method according to claim 18, wherein: The fourth information includes at least one of the following: The identification information of the PINE accepted as the PEGC in the PIN after the change; Modification type; Identification information of the PIN; PIN profile information; Dynamic PIN profile information.

20. The method according to any one of claims 1 to 16, wherein: In a case where the first information includes the first request from the PEMC, the PIN server performs a first operation according to the first information, including: The PIN server sends a second request to the first PINE, wherein the second request is used to request the first PINE to serve as a PEGC in the PIN established by the PEMC; The PIN server receives first information, including: The PIN server receives a second response from the first PINE, wherein the second response carries first information, and the first information indicates that the first PINE accepts or rejects the PEGC in the PIN established by the PEMC.

21. The method according to claim 20, wherein: The PIN server performs a first operation according to the first information, further comprising at least one of the following: The PIN server updates, according to the second response, the PINE information of the PEGC accepted as part of the PIN established by the PEMC; The PIN server sends identification information of a target first PINE to the PEMC according to the second response, wherein the target first PINE is a first PINE that accepts the PEGC in the PIN established by the PEMC; The PIN server sends the identification information of the PEMC to the PEMC according to the second response, indicating that the PEMC serves as the PEGC in the PIN established by it; The PIN server sends a first response to the PEMC according to the second response, wherein the first response is used to respond to the first request.

22. The method according to claim 21, wherein: After the PIN server sends the identification information of the PEMC to the PEMC according to the first response, indicating that the PEMC is used as the PEGC in the PIN established by it, the PIN server performs a first operation according to the first information, further comprising: The PIN server receives fifth information from the PEMC, the fifth information indicating that the PEMC accepts or does not accept the PEGC in the PIN established by it, or that the PEMC has or does not have a gateway capability.

23. The method according to claim 21 or 22, wherein: In the case where the PIN server determines that there is no available PEGC in the PIN established by the PEMC, the first response is used to reject the first request, or to deactivate the PIN established by the PEMC, or to accept the first request.

24. The method according to any one of claims 1 to 23, wherein: The first information also includes PEMC related information or PIN related information; The first operation further includes: The sixth information is updated, where the sixth information includes at least one of the following: PEMC information; PIN profile information.

25. An information transmission method, comprising: The PEMC sends the first information to the PIN server; Wherein, the first information includes at least one of the following: The first identification information is used to identify the PINE that does not accept becoming a PEGC in the PIN; The second identification information is used to identify the PEMC, and the PEMC does not have a gateway capability; The first indication information is used to indicate that the PIN established by the PEMC is in a deactivated state or to indicate that there is no available PEGC in the PIN; The second indication information is used to indicate that the PINE corresponding to the first identification information does not accept to become a PEGC in the PIN, or the PEMC corresponding to the second identification information does not have a gateway capability; A first request is used to request to establish a PIN.

26. The method according to claim 25, further comprising: The PEMC receives second information from the PIN server, wherein the second information is used to indicate that the second PINE as the PEGC is accepted in the PIN established by the PEMC, or the second information indicates acceptance of the first request; The PEMC determines the PEGC in the established PIN according to the second information, or establishes a deactivated PIN.

27. The method according to claim 26, further comprising: The PEMC sends a third request to the second PINE, wherein the third request is used to request the second PINE to serve as a PEGC in the PIN established by the PEMC.

28. The method according to claim 27, further comprising: The PEMC receives a third response from the second PINE, wherein the third response is used to indicate that the second PINE accepts or refuses to become a PEGC in the PIN.

29. The method according to claim 28, wherein: The first information is further used to request updating of the PEGC in the PIN established by the PEMC, or to instruct the second PINE to completely refuse to become the PEGC in the PIN established by the PEMC.

30. The method according to any one of claims 26 to 29, wherein: The second PINE comprises: A PINE that is a master PEGC of a PIN established by the PEMC; The PINE is a secondary PEGC of the PIN established by the PEMC.

31. The method according to claim 30, wherein: The PEMC determines, according to the second information, a PEGC in the established PIN, including at least one of the following: In the case that the primary PEGC is unreachable or refuses to become the PEGC in the PIN established by the PEMC, and there is at least one secondary PEGC that does not refuse to become the PEGC in the PIN established by the PEMC, the PEMC uses the secondary PEGC as the primary PEGC in the PIN established by it; In the case that the primary PEGC is reachable and does not refuse to become the PEGC in the PIN established by the PEMC, the PEMC uses the primary PEGC as the primary PEGC in the PIN established by it; In the case where the primary PEGC is reachable and does not refuse to become the PEGC in the PIN established by the PEMC, the PEMC ignores the target PEGC, where the target PEGC is unreachable or refuses to become the PEGC in the PIN established by the PEMC.

32. The method according to any one of claims 26 to 31, wherein: The PEMC establishes a deactivated PIN according to the second information, including: In the case where the second information is used to accept the first request, if the second information includes eighth indication information, and the eighth indication information is used to indicate that there is no available PEGC in the PIN, or the PIN is not activated, then the PEMC establishes a deactivated PIN.

33. The method according to any one of claims 25 to 32, further comprising: The PEMC receives seventh information from the PIN server, wherein the seventh information is used to indicate a reason for a PIN establishment failure or a reason for a PIN deactivation.

34. The method of claim 33, wherein: The seventh information is used to indicate at least one of the following: No PEGC available; PIN is not activated.

35. The method according to any one of claims 32 to 34, further comprising: The PEMC sends ninth indication information to the PINE in the PIN based on the seventh information or the eighth indication information, where the ninth indication information is used to indicate at least one of the following: no PEGC is available in the PIN, no gateway is available in the PIN, and the PIN is not activated.

36. A method for transmitting information, comprising: PINE sends a first message to the PIN server; The first information includes at least one of the following: The third indication information is used to indicate whether the PINE has a gateway capability or not; Fourth indication information, used to instruct the PINE to accept or refuse to be a PEGC in the PIN; Parameter information of the PINE.

37. The method of claim 36, wherein: The parameter information of the PINE includes at least one of the following: The media access control MAC address of the PINE; The Internet Protocol (IP) address of the PINE; The port number of the PINE; Capability information of the PINE.

38. The method of claim 37, wherein: The capability information of the PINE includes at least one of the following: The maximum number of PINEs supported when the PINE is used as a PEGC; The maximum transmission rate supported by the PINE; The maximum transmission rate supported by PINE as PEGC; The maximum number of PINs supported when the PINE is used as a PEGC.

39. The method according to any one of claims 36 to 38, wherein: The PINE sends first information to the PIN server, including: The PINE sends registration information to the PIN server, where the first information includes the registration information, and the registration information is used to indicate whether the PINE has gateway capability or not, or to indicate whether the PINE accepts or does not accept being a PEGC in the PIN.

40. The method according to any one of claims 36 to 39, wherein: Before the PINE sends the first information to the PIN server, the method further includes: The PINE receives a second request from the PIN server, the second request being used to request the PINE to serve as a PEGC in the PIN; The PINE sends first information to the PIN server, including: The PINE sends a second response to the PIN server, wherein the second response carries the first information, and the first information indicates that the PINE accepts or refuses to be a PEGC in the PIN.

41. The method according to any one of claims 36 to 40, further comprising: The PINE receives a third request from the PEMC, wherein the third request is used to request the PINE to serve as a PEGC in the PIN established by the PEMC; The PINE sends a third response to the PEMC, wherein the third response is used to indicate that the PINE accepts or refuses to become a PEGC in the PIN.

42. An information processing device, comprising: The first receiving module is configured to receive first information, wherein the first information satisfies at least one of the following: The first information is related to a PIN element PEGC having gateway capability; The first information includes a first request, and the first request is used to request to establish a PIN; A first execution module is configured to execute a first operation according to the first information, wherein the first operation includes at least one of the following: Determine the PEGC information in the PIN; rejecting the first request; Deactivate PIN; Update the personal Internet of Things network element PINE information of PEGC in PIN; Sending second information to the PIN element PEMC having management function, wherein the second information is used to indicate that the PINE as the PEGC is accepted in the PIN, or the second information indicates acceptance of the first request.

43. An information transmission device, comprising: A first sending module, used for sending first information to a PIN server; Wherein, the first information includes at least one of the following: The first identification information is used to identify the PINE that does not accept becoming a PEGC in the PIN; The second identification information is used to identify the PEMC, where the PEMC does not have a gateway capability; The first indication information is used to indicate that the PIN established by the PEMC is in a deactivated state or to indicate that there is no available PEGC in the PIN; The second indication information is used to indicate that the PINE corresponding to the first identification information does not accept to become a PEGC in the PIN, or the PEMC corresponding to the second identification information does not have a gateway capability; A first request is used to request to establish a PIN.

44. An information transmission device, comprising: A second sending module, used for sending the first information to the PIN server; The first information includes at least one of the following: The third indication information is used to indicate whether the PINE has a gateway capability or not; Fourth indication information, used to instruct PINE to accept or reject as PEGC in PIN; PINE parameter information.

45. A communication device, comprising a processor and a memory, wherein the memory stores programs or instructions that can be run on the processor, and when the programs or instructions are executed by the processor, the steps of the information processing method as described in any one of claims 1 to 24 are implemented, or the steps of the information transmission method as described in any one of claims 25 to 41 are implemented.

46. ​​A readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor, implements the steps of the information processing method as described in any one of claims 1 to 24, or implements the steps of the information transmission method as described in any one of claims 25 to 41.

Citation Information

Patent Citations

  • Method and apparatus for inter-device communication

    CN115734173A

  • Information acquisition and storage method and device, information reporting method and device, terminal and network function

    CN116567656A

  • Method and device for establishing PIN (Personal Identification Number)

    CN116567778A

  • Discovery of internet of things network

    WO2022271957A1

  • Personal internet of things network architecture

    WO2023184137A1