Information processing method, information transmission method, information processing device, information transmission device and related equipment
Obtaining PEGC information through a PIN server solves the data routing and communication problems caused by the lack of PEGC in personal IoT networks, and realizes the normal operation of the device and communication reliability.
Patent Information
- Application Number
- CN202310543097.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2023-05-12
- Publication Date
- 2024-11-12
AI Technical Summary
In personal IoT networks, the lack of a PIN element (PEGC) with gateway functions will cause devices to fail to route data or communicate normally, and the prior art cannot effectively solve this problem.
The PIN server obtains information related to PEGC, determines whether there is an available PEGC, and if it does not exist, it refuses to establish a PIN request or deactivate the PIN, otherwise it is instructed to PEMC or PINE as the PEGC to ensure the reliability of data routing and communication.
It effectively reduces the probability that devices cannot route data or communication normally due to the lack of PEGC, and ensures the reliability of communication.
Smart Images

Figure CN118945695A_ABST
Abstract
Description
Technical Field
[0001] The present application belongs to the field of communication technology, and specifically relates to an information processing method, an information transmission method, a device and related equipment. Background Art
[0002] In a personal IoT network (PIN), it is necessary to use a PIN element with management capability (PEMC) to manage the PIN, and to use a PIN element with gateway capability (PEGC) to provide data routing or communication for devices in the PIN.
[0003] However, in some cases, there will be no PEGC in the PIN. For example, during the process of PEMC creating a PIN, if there is no suitable PIN element (PINE) that can serve as the PEGC in the PIN, the PIN server will instruct the PEMC that may not have the relevant functions of PEGC or other PINEs that do 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. Summary of the invention
[0004] 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 present, 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.
[0005] In a first aspect, an information processing method is provided, the method comprising:
[0006] The personal Internet of Things PIN server receives first information, wherein the first information satisfies at least one of the following:
[0007] The first information is related to a PIN element PEGC having gateway capability;
[0008] The first information includes a first request, and the first request is used to request to establish a PIN;
[0009] The PIN server performs a first operation according to the first information, wherein the first operation includes at least one of the following:
[0010] Determine the PEGC information in the PIN;
[0011] rejecting the first request;
[0012] Deactivate PIN;
[0013] Update the personal Internet of Things network element PINE information of PEGC in PIN;
[0014] 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.
[0015] In a second aspect, an information transmission method is provided, the method comprising:
[0016] The PEMC sends the first information to the PIN server;
[0017] Wherein, the first information includes at least one of the following:
[0018] The first identification information is used to identify the PINE that does not accept becoming a PEGC in the PIN;
[0019] The second identification information is used to identify the PEMC, and the PEMC does not have a gateway capability;
[0020] 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;
[0021] 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;
[0022] A first request is used to request to establish a PIN.
[0023] In a third aspect, an information transmission method is provided, the method comprising:
[0024] PINE sends a first message to the PIN server;
[0025] The first information includes at least one of the following:
[0026] The third indication information is used to indicate whether the PINE has a gateway capability or not;
[0027] Fourth indication information, used to instruct the PINE to accept or refuse to be a PEGC in the PIN;
[0028] Parameter information of the PINE.
[0029] In a fourth aspect, an information processing device is provided, comprising:
[0030] The first receiving module is configured to receive first information, wherein the first information satisfies at least one of the following:
[0031] The first information is related to a PIN element PEGC having gateway capability;
[0032] The first information includes a first request, and the first request is used to request to establish a PIN;
[0033] 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:
[0034] Determine the PEGC information in the PIN;
[0035] rejecting the first request;
[0036] Deactivate PIN;
[0037] Update the personal Internet of Things network element PINE information of PEGC in PIN;
[0038] 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.
[0039] In a fifth aspect, an information transmission device is provided, comprising:
[0040] A first sending module, used for sending first information to a PIN server;
[0041] Wherein, the first information includes at least one of the following:
[0042] The first identification information is used to identify the PINE that does not accept becoming a PEGC in the PIN;
[0043] The second identification information is used to identify the PEMC, where the PEMC does not have a gateway capability;
[0044] 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;
[0045] 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;
[0046] A first request is used to request to establish a PIN.
[0047] In a sixth aspect, an information transmission device is provided, comprising:
[0048] A second sending module, used for sending the first information to the PIN server;
[0049] The first information includes at least one of the following:
[0050] The third indication information is used to indicate whether the PINE has a gateway capability or not;
[0051] Fourth indication information, used to instruct PINE to accept or reject as PEGC in PIN;
[0052] PINE parameter information.
[0053] In a seventh aspect, a terminal is provided, comprising 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.
[0054] In an eighth aspect, a terminal is provided, comprising a processor and a communication interface;
[0055] The communication interface is used to send first information to the PIN server;
[0056] Wherein, the first information includes at least one of the following:
[0057] The first identification information is used to identify the PINE that does not accept becoming a PEGC in the PIN;
[0058] The second identification information is used to identify the PEMC, where the PEMC does not have a gateway capability;
[0059] 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;
[0060] 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;
[0061] a first request, wherein the first request is used to request to establish a PIN;
[0062] or,
[0063] The communication interface is used to send first information to the PIN server;
[0064] The first information includes at least one of the following:
[0065] The third indication information is used to indicate whether the PINE has a gateway capability or not;
[0066] Fourth indication information, used to instruct PINE to accept or reject as PEGC in PIN;
[0067] PINE parameter information.
[0068] 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.
[0069] In a tenth aspect, a network side device is provided, including a processor and a communication interface;
[0070] The communication interface is used to receive first information, wherein the first information satisfies at least one of the following:
[0071] The first information is related to a PIN element PEGC having gateway capability;
[0072] The first information includes a first request, and the first request is used to request to establish a PIN;
[0073] 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:
[0074] Determine the PEGC information in the PIN;
[0075] rejecting the first request;
[0076] Deactivate PIN;
[0077] Update the personal Internet of Things network element PINE information of PEGC in PIN;
[0078] 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 that the first request is accepted;
[0079] or,
[0080] The communication interface is used to send first information to the PIN server;
[0081] Wherein, the first information includes at least one of the following:
[0082] The first identification information is used to identify the PINE that does not accept becoming a PEGC in the PIN;
[0083] The second identification information is used to identify the PEMC, where the PEMC does not have a gateway capability;
[0084] 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;
[0085] 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;
[0086] a first request, wherein the first request is used to request to establish a PIN;
[0087] or,
[0088] The communication interface is used to send first information to the PIN server;
[0089] The first information includes at least one of the following:
[0090] The third indication information is used to indicate whether the PINE has a gateway capability or not;
[0091] Fourth indication information, used to instruct PINE to accept or reject as PEGC in PIN;
[0092] PINE parameter information.
[0093] 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.
[0094] 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 second aspect.
[0095] In the thirteenth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program 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.
[0096] In the fourteenth aspect, a computer program / program product is provided, wherein the computer program / program product is stored in a storage medium, and the program / program product is executed by at least one processor to implement the steps of the information processing method as described in the first aspect, or the steps of the information processing method as described in the second aspect, or the steps of the information processing method as described in the third aspect.
[0097] In the embodiment of the present application, the PIN server can obtain the 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 can be established and deactivated; if it exists, the PECG can be specifically indicated for the PIN; or the PIN server can update the PINE information supporting the PEGC in the PIN based on the first information, so that the PEMC can determine the available PEGC as well as the updated PINE information supporting 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
[0098] Figure 1a is a schematic diagram of the structure of a wireless communication system to which the embodiments of the present application can be applied;
[0099] Figure 1b is a flow chart of establishing a PIN in the related art;
[0100] Figure 2 This is a flowchart of an information processing method provided in an embodiment of the present application.
[0101] Figure 3 is a flow chart of an information transmission method provided by an embodiment of the present application;
[0102] Figure 4 is a flow chart of another information transmission method provided in an embodiment of the present application;
[0103] Figure 5a This is one of the interaction diagrams between the PIN server, PEMC and PINE;
[0104] Figure 5b This is the second diagram of the interaction between the PIN server, PEMC and PINE;
[0105] Figure 5c This is the third diagram of the interaction between the PIN server, PEMC and PINE;
[0106] Figure 6 is a structural diagram of an information processing device provided in an embodiment of the present application;
[0107] Figure 7 is a structural schematic diagram of an information transmission device provided in an embodiment of the present application;
[0108] Figure 8 is a structural schematic diagram of another information transmission device provided in an embodiment of the present application;
[0109] Fig. 9 It is a structural diagram of a communication device provided in an embodiment of the present application;
[0110] Fig.10 is a schematic diagram of the structure of a terminal provided in an embodiment of the present application;
[0111] Fig.11 It is a structural diagram of a network side device provided in an embodiment of the present application;
[0112] Fig.12 It is a structural diagram of another network side device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0113] The following will be combined with the drawings in the embodiments of the present application to clearly describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of this application.
[0114] The terms "first", "second", etc. of the present 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 one type, and the number of objects is not limited, for example, the first object can be one or more. In addition, "or" in the present application represents at least one of the connected objects. For example, "A or B" covers three schemes, namely, Scheme 1: including A but not including B; Scheme 2: including B but not including A; Scheme 3: including both A and B. The character " / " generally indicates that the objects associated with each other are in an "or" relationship.
[0115] The term "indication" in this application can be 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, operations to be performed, or request results in the sent indication; an indirect indication can be understood as the receiver determining the corresponding information according to the indication sent by the sender, or making a judgment and determining the operation to be performed or the request result according to the judgment result.
[0116] 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 described technology 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 descriptions, but these technologies can also be applied to systems other than NR systems, such as the 6th generation (6 th Generation, 6G) communication system.
[0117] Figure 1aA block diagram of a wireless communication system applicable to an embodiment of the present application is shown. The wireless communication system includes a terminal 11 and a network side device 12. Among them, the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (Ultra-mobile Personal Computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), an augmented reality (Augmented Reality, AR), a virtual reality (Virtual Reality, VR) device, a robot, a wearable device (Wearable Device), an aircraft (flight vehicle), a vehicle-mounted device (Vehicle User Equipment, VUE), a ship-mounted device, a pedestrian terminal (Pedestrian User Equipment, PUE), a smart home (home appliances with wireless communication functions, such as refrigerators, televisions, washing machines or furniture, etc.), a game console, a personal computer (Personal Computer, PC), a teller machine or a self-service machine and 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 referred to as 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 (Wireless Local Area Network, WLAN) access point (Access Point, AS) or a wireless fidelity (Wireless Fidelity, WiFi) node, etc.Among them, the base station may be referred to as a Node B (NB), an evolved Node B (eNB), a next generation Node B (gNB), a New Radio Node B (NR Node B), an access point, a Relay Base Station (RBS), a Serving Base Station (SBS), a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a Basic Service Set (BSS), an Extended Service Set (ESS), a Home Node B (HNB), a Home Evolved Node B, a Transmission Reception Point (TRP) or other appropriate terms in the field. As long as the same technical effect is achieved, the base station is not limited to specific technical terms. It should be noted that in the embodiments 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.
[0118] 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 (Mobility Management Entity, MME), access mobility management function
[0119] Access and Mobility Management Function (AMF), Session Management Function (SMF), User Plane Function (UPF), Policy Control Function (PCF), Policy and Charging Rules Function (PCRF), Edge Application Server Discovery Function (EASDF), Unified Data Management (UDM), Unified Data Repository (UDR), Home Subscriber Server (HSS), Centralized Network Configuration
[0120] (Centralized network configuration, CNC), Network Repository Function (NRF), Network Exposure Function (NEF), Local NEF (Local NEF, or L-NEF), Binding Support Function (BSF), Application Function
[0121] (Application 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 introduced as an example, 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 introduced as an example, and the specific type of the core network device is not limited.
[0122] like Figure 1b As shown, in the related art, the process of creating a PIN is as follows:
[0123] Step 1: 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 (such as obtained via Bluetooth or PIN), and the PIN creation request may include a UE identifier, such as a universal public user identity.
[0124] At least one of identification information such as (Generic Public Subscription Identifier, GPSI), PIN client ID, UE location and PIN client profile information.
[0125] It should be noted that the request for the PEMC to create a PIN may include other PIN elements that have been connected to it.
[0126] The details of the PIN element may be UE identifiers such as GPSI, PIN client ID, UE location, and PIN client profile information. If there are no other PIN elements in the PEMC request to create a PIN, the PEMC requests to create a PIN including itself.
[0127] 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 PEMC requests to join the specific PIN and become a PEMC individually. 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.
[0128] Step 2: The PIN server processes the PIN creation request.
[0129] 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.
[0130] Step 3: The PIN server sends a PIN creation response to the PEMC, which includes the newly assigned PIN ID for indicating the PIN. It also includes a list of PIN elements and their identifiers. If the PIN creation 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.
[0131] 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.
[0132] 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.
[0133] If one or more PEGCs are indicated in the PIN creation response, the PIN server indicates a 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. And, the PIN server also sends a PEGC message about access control in the response. Among them, the access control information includes: user name, account, service set identifier (Service Set Identifier, SSID), basic service set identifier (Basic Service Set Identifier, BSSID). The PIN element in the PIN uses all information to access 5G or access other applications outside the PIN.
[0134] Among them, the PIN server or PEMC can determine the access control information in certain PEGCs.
[0135] 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.
[0136] 2) If the access control information is determined by PEMC, PEMC passes the access control information to PEGC through a PIN creation notification request.
[0137] Steps 4a-4c: If the PIN creation response contains a list of PIN elements, the PEMC generates a PIN creation notification request (such as 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.
[0138] 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.
[0139] From the above process, we can see that the relevant technology has the following defects:
[0140] 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, and the PEMC may not have the relevant functions of the PEGC, which will cause the devices in the PIN to be unable to route data or communicate normally because there is no PEGC;
[0141] 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 access control information
[0142] One or more of (access control info), PIN member indication, PEGC address, and PEGC ID. However, as a terminal with gateway capabilities in the PIN, PEGC may reject the request of PEMC. The reason is that when creating the PIN, PEGC is selected by the PIN server and no agreement is reached between 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.
[0143] In the 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.
[0144] For example, 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:
[0145] Application layer support for Personal IoT Network (PIN APP): is based on the substantial increase in the number of consumer IoT devices. Users mainly use all these personal IoT devices at home or around their bodies to create personal IoT networks. Application layer support for personal IoT networks is the application layer architecture and related processes used to implement PIN applications on 3GPP networks.
[0146] PIN: is a personal network composed of 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 PEGC, or use PEGC to communicate with devices or servers outside the PIN through a 5G network. At least one PEGC is managed by PEMC. Optionally, if an application function (AF) is deployed, PIN management can be implemented with the support of AF. In the embodiment of the present application, AF may sometimes also be referred to as a PIN server.
[0147] PINE: It is the basic unit in PIN, which can include UE or non-3GPP equipment. It can communicate within the PIN (through direct connection from PINE to PINE or indirect connection from PINE to PIN), or communicate outside the PIN through PEGC and 5G Core Network (5G Core Network, 5GC).
[0148] PEGC: As a gateway in the PIN, it has communication capabilities and can help a PINE route data to another PINE. For example, a PEGC has the ability to provide data network (DN) connections for other PIN elements through a 5G network and / or can provide a relay function for communications between PIN elements. Usually only a UE can act as a PEGC.
[0149] PEMC: It is the administrator in the PIN, has communication capabilities, and is used to manage the authorization of various things in the PIN, etc. Optionally, the UE as a PIN element can act as both PEMC and PEGC.
[0150] PEGCs not available in PIN include:
[0151] 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 being the PEGC in the PIN established by the PEMC;
[0152] 2) The PEMC requesting to establish a PIN does not have gateway capabilities.
[0153] 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.
[0154] The information transmission method, information processing method, information transmission device, information processing device and related equipment provided by the embodiments of the present application are described in detail below with reference to the accompanying drawings through some embodiments and their application scenarios.
[0155] See also Figure 2 , an information processing method provided in an embodiment of the present application, the execution subject of which may be a PIN server. Figure 2 As shown, the information processing method may include the following steps:
[0156] Step 201: The PIN server receives first information, wherein the first information satisfies at least one of the following:
[0157] The first information is related to a PIN element PEGC having gateway capability;
[0158] The first information includes a first request, and the first request is used to request to establish a PIN.
[0159] In one implementation, the first information may include information related to a PIN element PEGC with gateway capabilities and a first request.
[0160] Alternatively, the first request may be a PIN establishment request.
[0161] In another implementation, the first information includes information related to a PIN element PEGC having gateway capabilities.
[0162] 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.
[0163] In another embodiment, the PEMC sends a first request to the PIN server to create a PIN. After receiving the first request, the PIN server obtains first information by interacting with the PINE in the PIN, and then determines the PEGC information in the PIN. The first information is related to the PIN element PEGC with gateway capability. The PEMC in this embodiment sends the first request to the PIN server, which can also be understood as: because the PEMC sends the first request, it triggers the PIN server to obtain information related to PEGC, and then uses the information related to PEGC to determine the PEGC information in the PIN.
[0164] In some embodiments, the first information is related to a PIN element PEGC with gateway capability, and 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 or PINEs are accepted as the PEGC in the PIN.
[0165] Step 202: The PIN server performs a first operation according to the first information, wherein the first operation includes at least one of the following:
[0166] Determine the PEGC information in the PIN;
[0167] rejecting the first request;
[0168] Deactivate PIN;
[0169] Update the personal Internet of Things network element PINE information of PEGC in PIN;
[0170] 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.
[0171] Optionally, the first information may come from PEMC or PINE.
[0172] Optionally, the first information can be obtained through multiple steps, for example, first obtaining a portion of the first information from PEMC, and then obtaining another portion of the first information from PINE; or first obtaining a portion of the first information from PINE, and then obtaining another portion of the first information from PEMC. In this case, the above steps 201 and 202 can be performed alternately, such as first performing a portion of the first operation in step 202 according to a portion of the first information, and then performing a portion of the first operation in step 202 according to another portion of the first information. The execution order of steps 201 and 202 is not limited here.
[0173] In one implementation, the PEMC may send the first information to the PIN server during the process of establishing the PIN.
[0174] In another implementation, PEMC may send the above-mentioned first information to the PIN server after establishing the PIN. For example, in 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, and the other part are rejected as PEGCs in the PIN. At this time, PEMC may determine the PEGC in the PIN based on the PINEs accepted as PEGCs in the PIN, and feedback the PINE information 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.
[0175] In another implementation, 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.
[0176] It is worth mentioning that in the relevant technology, the registration process of PINE is as follows:
[0177] 1. PINE (including PINE, PEMC and PEGC) sends a PINE registration request to the PIN server.
[0178] 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.
[0179] If it is a PEMC that triggers the registration request, then 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 a primary or secondary PEMC role.
[0180] 2. The PIN server interacts with the 5G System (5GS) to check whether the PINE identified by GPSI has been subscribed as a PEMC.
[0181] Additionally, the PIN Server may check whether the PINE identified by the GPSI is itself already subscribed as a PEMC. If so, it checks the PIN Profile whether the requesting PIN element can be assigned a primary or secondary role and authorizes the PIN element accordingly. In the case that 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.
[0182] 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 SHOULD issue a Failure Response to PINE to indicate the reason why the registration request failed.
[0183] 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 a PIN server, the PIN server cannot distinguish whether the PINE has gateway capability.
[0184] Through the above-mentioned implementation mode 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.
[0185] 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 an available PEGC in the PIN based on the first information.
[0186] In one implementation, if the PIN server determines that there is no available PEGC in the PIN according to the first information, the PIN may reject the first request for requesting to establish the PIN, that is, reject the establishment of the PIN. In this way, the establishment of a PIN without available PEGC can be avoided.
[0187] In another implementation, if the PIN server determines that there is no available PEGC in the PIN according to the first information, the PIN may be deactivated, for example, by agreeing to the PEMC to establish the PIN and indicating that the established PIN is in a deactivated state, or only agreeing to the PEMC to establish the PIN and not indicating an available PEGC to the PIN. At this time, the established PIN is in a deactivated state.
[0188] Optionally, after establishing a deactivated PIN, if the PIN server obtains an available PEGC in the PIN, the PIN can be activated. For example: a PINE with gateway capabilities in the PIN is registered with the PIN server. At this time, the PIN server can indicate the PINE as the PEGC in the deactivated PIN and activate the PIN. In this way, when there is no available PEGC in the PIN, a deactivated PIN can be established, and the PIN can be activated when there is an available PEGC later. Compared with the previous embodiment, when the PIN is not available, the establishment of the PIN is refused. This can reduce the probability of repeatedly establishing the PIN due to the lack of available PEGC.
[0189] 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.
[0190] Different from the related art, the PIN server does not know whether there is an available PEGC in the PIN, so when there is no available PEGC in the PIN, an unavailable PIN is established. In the embodiment of the present application, the PIN server can determine whether there is an available PEGC in the PIN, so when there is no available PEGC in the PIN, the PIN is refused to be established or a deactivated PIN is established.
[0191] In another optional implementation, determining the PEGC information in the PIN in the first operation may include: the PIN server may determine the available PEGC in the PIN according to the first information.
[0192] For example, during the registration process, the PINE sends first information to the PIN server to indicate whether the PINE has gateway capability. Thus, 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.
[0193] In this implementation manner, the PIN server determines the available PEGC in the PIN according to the first information, so as to specifically indicate to the PEMC the available PEGC in the established PIN.
[0194] In an optional implementation manner, sending the second information to the PEMC in the first operation may include:
[0195] The PIN server determines the PINE 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.
[0196] 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.
[0197] In this implementation manner, the PIN server requests the PINE as the PEGC in the PIN according to the first information, so as to specifically instruct the PEMC to accept the PINE as the PEGC in the PIN established by it.
[0198] In an optional implementation manner, sending the second information to the PEMC in the first operation may include:
[0199] 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.
[0200] 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 information carries the instruction information for deactivating the PIN, or the second information carries the identification information of the PEMC, and the PEMC does not have gateway capability.
[0201] In this implementation, activation of a PIN for which no PEGC is available can be avoided.
[0202] In an optional implementation, updating the PINE information of the PEGC in the PIN in the first operation may include:
[0203] During the PIN establishment process, the PIN server indicates to the PEMC the PINEs that can be used as PEGCs, but some PINEs refuse to be used as PEGCs in the PIN established by the PEMC. At this time, the PEMC can feed back 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.
[0204] In an optional implementation, updating the PINE information of the PEGC in the PIN in the first operation may include:
[0205] 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 accepts being 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.
[0206] As in the above implementation, 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.
[0207] As an optional implementation manner, the second information indicating that the PINE as the PEGC is accepted in the PIN includes at least one of the following:
[0208] The second information indicates a PINE which is a primary PEGC in the PIN established by the PEMC;
[0209] The second information indicates a PINE which is a secondary PEGC in the PIN established by the PEMC.
[0210] In this embodiment, the PIN server may indicate one primary PEGC, or one primary PEGC and at least one secondary PEGC to the PEMC.
[0211] Optionally, the PIN Server may indicate one or more PEGCs during the PIN creation process:
[0212] (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, then the PEMC can use the secondary PEGC as the primary PEGC in the PIN;
[0213] (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.
[0214] In one implementation, 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 PEGC that refuses or is unreachable.
[0215] In another implementation, when there is at least one PEGC that can serve the PIN, the PIN server can update the PEGC information to the PIN.
[0216] In another embodiment, the PIN server confirms that a certain PINE can be used as a PEGC in the PIN during the creation of the PIN. However, for some reason, although a certain PEGC agrees to be a PEGC, it 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.
[0217] 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.
[0218] As an optional implementation manner, the first information includes at least one of the following:
[0219] The first identification information is used to identify the PINE that does not accept becoming a PEGC in the PIN;
[0220] The second identification information is used to identify the PEMC that does not have the gateway capability;
[0221] 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;
[0222] 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;
[0223] The third indication information is used to indicate whether the PINE has a gateway capability or not;
[0224] Fourth indication information, used to instruct PINE to accept or reject as PEGC in PIN;
[0225] PINE parameter information;
[0226] The first request.
[0227] 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.
[0228] 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 a gateway capability.
[0229] In another implementation, the first information may include only 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.
[0230] 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.
[0231] In yet another implementation, the first information may include only the second identification information, in which case it may be assumed by default that the PEMC indicated by the second identification information does not have the gateway capability.
[0232] In another implementation manner, the PEMC may, when determining that there is no available PEGC, send a first indication message to the PIN server to indicate that the PIN is in a deactivated state or that there is no available PEGC in the PIN. For example, the PEMC receives a list of PINEs fed back by the PIN server during the PIN establishment process, and sends a third request to these PINEs to request them to be the PEGC in the PIN. If all PINEs reject the third request and the PEMC does not have a gateway function, the PEMC may send a first indication message to the PIN server to indicate that the PIN is in a deactivated state or that there is no available PEGC in the PIN.
[0233] In another implementation, PINE may send a third indication information or a fourth indication information to the PIN server, for example, the third indication information or the fourth indication information is carried 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.
[0234] In another implementation, the PINE may send parameter information of the PINE to the PIN server, for example, by carrying the parameter information of the PINE in a PINE registration message, so that the PIN server determines whether the PINE supports being a PEGC in the PIN according to the parameter information of the PINE.
[0235] Optionally, the parameter information of the PINE includes at least one of the following:
[0236] PINE's MAC address;
[0237] PINE's Internet Protocol (IP) address;
[0238] The port number of PINE;
[0239] PINE's capability information.
[0240] In one implementation, based on the MAC address or 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 being a PEGC in the PIN.
[0241] In another implementation, based on the capability information of the PINE, it can be determined whether it has the capability to serve as the PEGC in the PIN.
[0242] Optionally, the capability information of the PINE includes at least one of the following:
[0243] The maximum number of PINEs supported when PINE is used as PEGC;
[0244] The maximum transfer rate supported by PINE;
[0245] The maximum transmission rate supported by PINE as PEGC;
[0246] Maximum number of PINs supported when PINE is used as PEGC.
[0247] 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.
[0248] As an optional implementation manner, the PIN server performs a first operation according to the first information, including:
[0249] 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.
[0250] In one implementation, 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.
[0251] Optionally, the PIN server sends second information to the PEMC, the second information is used to accept the first request, and the second information includes eighth indication information, the eighth indication information is used to indicate that there is no available PEGC in the PIN, or the PIN is not activated. In this way, the PEMC can determine that a deactivated PIN is established based on the second information carrying the eighth indication information.
[0252] In another implementation, when the PIN server determines that there is no available PEGC in the PIN according to the first information, accepting the first request may mean that the PIN server sends an acceptance response to the PEMC, and at this time, the PEMC determines that the established PIN is a deactivated PIN according to the absence of available PEGC. For example: when the PIN server determines that there is no PINE accepted as PEGC, it sends an acceptance response to the PEMC, and the acceptance response carries the identification of the PEMC. At this time, the PEMC determines whether it has the gateway capability according to the identification of the PEMC in the acceptance response. If not, it determines that the established PIN is a deactivated PIN. If it has, it determines that the PEMC is also the PEGC in the established PIN.
[0253] In yet another embodiment, in the case where the PIN server refuses to establish a PIN or deactivate a PIN, the PIN server may indicate to the PEMC the reason for refusing to establish a PIN or deactivate a PIN.
[0254] For example, the rejecting the first request or deactivating the PIN includes:
[0255] 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.
[0256] Optionally, the seventh information is used to indicate at least one of the following:
[0257] No PEGC available;
[0258] PIN is not activated.
[0259] In this implementation manner, 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.
[0260] 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:
[0261] 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.
[0262] Optionally, the third identification information is used to identify at least one of the following:
[0263] A PINE that is a master PEGC in a PIN established by the PEMC;
[0264] The PINE is a secondary PEGC in the PIN established by the PEMC.
[0265] 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.
[0266] 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.
[0267] Optionally, if all third requests are rejected, the PIN server receives the first information, further comprising:
[0268] 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.
[0269] In this implementation, 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.
[0270] Optionally, the PIN server performing a first operation according to the first information further includes at least one of the following:
[0271] The PIN server updates the PINE information of the PEGC in the PIN established by the PEMC according to the first information;
[0272] 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;
[0273] 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;
[0274] 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.
[0275] In one embodiment, the PIN server updates the PINE information that is accepted as the PEGC in the PIN established by the PEMC based on the first information, which 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 that is 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 that is accepted as the PEGC in the PIN established by the PEMC.
[0276] In one implementation, the PIN server sends the updated identification information of the PINE that accepts to become the PEGC in the PIN established by the PEMC to the PEMC based on the first information. It can be: when there is a PINE that can be used as the PEGC in the PIN among the newly registered PINEs, the PIN server sends the identification information of the PINE to the PEMC so that the PEMC uses the PINE as the PEGC in the PIN; or, during the PIN establishment process, if all the PINEs that can be used as the PEGC indicated by the PIN server are unreachable or refuse to be used as the PEGC in the PIN, the PIN server can update the PEGC information in the PIN and indicate the updated PEGC information in the PIN to the PEMC.
[0277] In one implementation, 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 established by it. 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.
[0278] 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 may 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 unavailable PEGC.
[0279] As an optional implementation, 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.
[0280] In this implementation, when it is determined that there is no available PEGC in the PIN, such as 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 is no available PEGC in the PIN established by the PEMC. Based on the fifth indication message, the PIN server may update the PEGC in the PIN, or establish a deactivated PIN.
[0281] As an optional implementation manner, the PIN server receives the first information, including:
[0282] 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.
[0283] In this implementation, the PINE reports during the registration process whether the PINE has gateway capability or not, or whether the PINE accepts or does not accept indication information as PEGC in the PIN, so that the PIN server can determine whether it supports PEGC in the PIN based on the registration information.
[0284] As an optional implementation manner, the PIN server performs a first operation according to the first information, including at least one of the following:
[0285] The PIN server determines, based on the registration information, to accept the PINE as the PEGC in the PIN;
[0286] 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;
[0287] 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
[0288] 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.
[0289] Optionally, the fourth information includes at least one of the following:
[0290] The identification information of the PINE accepted as the PEGC in the PIN after the change;
[0291] Modification type;
[0292] Identification information of the PIN (PIN ID);
[0293] PIN profile information;
[0294] Dynamic PIN profile information.
[0295] 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.
[0296] In another implementation, after the PIN is established, if a PINE is unreachable or the registration information is modified to not accept the PEGC as part of the PIN, the PIN server may determine that the PINE is changed to not accept the PEGC as part of the PIN. At this time, if all the PEGCs in the PIN are changed to not accept the PEGC as part of the PIN, the PIN server may indicate to the PEMC that there is no available PEGC in the PIN.
[0297] In one implementation, during the PIN establishment process, the PIN server may determine the target PINE that is accepted as the PEGC in the PIN established by the PEMC request based on the registration information of the registered PINE, thereby sending sixth indication information to the PEMC to instruct the PEMC to request the target PINE to be the PEGC in the PIN established by it.
[0298] In one implementation, 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 established, or to indicate that the PIN established by the PEMC is in a deactivated state, or to refuse the PEMC to establish the PIN.
[0299] 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.
[0300] 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:
[0301] 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;
[0302] The PIN server receives first information, including:
[0303] 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.
[0304] In this embodiment, during the PIN establishment process, the PIN server requests the first PINE for the PEGC in the PIN established as the PEMC request. At this time, the first PINE can feedback an acceptance response or a rejection response to the PIN service, and the PIN server can determine the PEGC in the PIN according to the response, or determine whether there is an available PEGC in the PIN, or determine to reject or accept the first request, or determine whether the established PIN is in an activated state or a deactivated state.
[0305] Optionally, the PIN server performing a first operation according to the first information further includes at least one of the following:
[0306] The PIN server updates the PINE information of the PEGC in the PIN established by the PEMC according to the second response, for example, determining the first PINE that sends the acceptance response as the updated PINE that accepts the PEGC in the PIN established by the PEMC;
[0307] The PIN server sends identification information of the 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: sending second information to the PEMC, and the second information carries identification information of the first PINE that sends the acceptance response;
[0308] The PIN server sends the identification information of the PEMC to the PEMC according to the second response, indicating the PEMC as the PEGC in the PIN established by it, for example: when 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;
[0309] 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, when all the first PINEs send rejection responses, the first request is rejected or the PIN established by the first request is deactivated.
[0310] Optionally, after the PIN server sends the identification information of the PEMC to the PEMC according to the first response to instruct 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:
[0311] 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.
[0312] 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 to the PIN server the fifth information that it does not accept the PEGC in the PIN established by it, or that it does not have the gateway capability.
[0313] In one implementation, the PIN server may determine whether there is an available PEGC in the PIN according to the first response and the fifth information.
[0314] 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.
[0315] 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.
[0316] As an optional implementation manner, the first information further includes PEMC related information or PIN related information;
[0317] The first operation further includes:
[0318] The sixth information is updated, where the sixth information includes at least one of the following:
[0319] PEMC information;
[0320] PIN profile information.
[0321] In this implementation, 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.
[0322] In the embodiment of the present application, the PIN server can obtain the 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 can be established and deactivated; if it exists, the PECG can be specifically indicated for the PIN; or the PIN server can update the PINE information supporting the PEGC in the PIN based on the first information, so that the PEMC can determine the available PEGC together with the updated PINE information supporting 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.
[0323] See also Figure 3 , is a flow chart of an information transmission method provided in an embodiment of the present application, and the execution subject of the information transmission method may be PEMC. Figure 3 As shown, the method may include the following steps:
[0324] Step 301: PEMC sends first information to a PIN server;
[0325] Wherein, the first information includes at least one of the following:
[0326] The first identification information is used to identify the PINE that does not accept becoming a PEGC in the PIN;
[0327] The second identification information is used to identify the PEMC, and the PEMC does not have a gateway capability;
[0328] 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;
[0329] 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;
[0330] A first request is used to request to establish a PIN.
[0331] It should be noted that the various contents of the first information in the embodiment of the present application are similar to those in the Figure 2 The corresponding content of the first information in the method embodiment shown has the same meaning and function, and can be specifically referred to as Figure 2 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 are available PEGCs 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., and how to deal with the situation when there is no PINE accepted as PEGC in the PIN, such as: deactivating the PIN, refusing to establish the PIN, or updating the PEGC in the PIN. Figure 2 The similar beneficial effects of the illustrated method embodiments are not described again here to avoid repetition.
[0332] Optionally, the method further comprises:
[0333] 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;
[0334] The PEMC determines the PEGC in the established PIN according to the second information, or establishes a deactivated PIN.
[0335] In one implementation, the second PINE may 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, and the PINE may 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.
[0336] In another implementation, 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.
[0337] In another embodiment, the second PINE may include any PINE in the PIN, such as all or part of the PINE.
[0338] 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 that supports being 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 an acceptance response as the second PINE.
[0339] After receiving the second information indicating the second PINE, the PEMC may directly use the second PINE as the PEGC in the PIN it has established, or request the second PINE to be the PEGC in the PIN it has established.
[0340] As an optional implementation, the method further includes:
[0341] 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.
[0342] In one embodiment, the method further comprises:
[0343] 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.
[0344] 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 determines by default that the second PINE that does not receive the third response refuses to become the PEGC in the PIN.
[0345] In this embodiment, during the PIN establishment process, the PIN server indicates to the PEMC the second PINE that can be used as the PEGC in the established PIN, and the PEMC requests the second PINE to be used as the PEGC in the established PIN. During this process, the second PINE may refuse or accept to become the PEGC in the PIN, or the second PINE may be unreachable.
[0346] 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.
[0347] In this implementation manner, the PEGC information in the PIN can be updated in time to avoid designating the PEGC in the PIN that refuses to be established by the PEMC as the PEGC in the PIN during the subsequent establishment of the PIN.
[0348] As an optional implementation manner, the second PINE includes:
[0349] A PINE that is a master PEGC of a PIN established by the PEMC;
[0350] The PINE is a secondary PEGC of the PIN established by the PEMC.
[0351] Optionally, the PEMC determines, according to the second information, a PEGC in the established PIN, including at least one of the following:
[0352] 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;
[0353] 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;
[0354] 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.
[0355] 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 has not refused to become the PEGC in the PIN established by the PEMC can be used as the primary PEGC in the PIN it establishes.
[0356] As an optional implementation manner, the PEMC establishes a deactivated PIN according to the second information, including:
[0357] 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.
[0358] In this implementation manner, if there is no available PEGC in the PIN, if 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 it accepts the establishment of the PIN, but there is no available PEGC in the PIN or the PIN is in a deactivated state, so that the PEMC may determine that a PIN with no available PEGC or deactivated is established according to the eighth indication information. Subsequently, the PEMC may manage the PINE in the PIN with no available PEGC or deactivated to not perform data routing.
[0359] As an optional implementation, the method further includes:
[0360] 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.
[0361] Optionally, the seventh information is used to indicate at least one of the following:
[0362] No PEGC available;
[0363] PIN is not activated.
[0364] In this implementation, if there is no available PEGC in the PIN, and the PIN server refuses to establish the PIN or determines to deactivate 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 information. Subsequently, the PEMC may request to update the PEGC, add a PINE with management function to the PIN, etc. to re-request to establish the PIN or activate the PIN based on the reason why the PIN server refuses to establish the PIN or deactivate the PIN.
[0365] As an optional implementation, the method further includes:
[0366] Based on the seventh information or the eighth indication information, the PEMC sends ninth indication information to the PINE in the PIN, 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.
[0367] In this implementation, 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 with the PINE in the PIN that there is no available PEGC in the PIN or the PIN is not activated, so that PINE will not send data to PEMC when there is no gateway in the PIN, resulting in waste of signaling and resources.
[0368] In the embodiment of the present application, the information transmission method performed by PEMC is similar to the following Figure 2 The method shown in the embodiment corresponds to the information processing method performed by the PIN server, and can obtain the same Figure 2 The similar beneficial effects of the illustrated method embodiments are not described again here to avoid repetition.
[0369] See also Figure 4 , is a flowchart of another information transmission method provided in an embodiment of the present application, and the execution subject of the information transmission method may be PINE. Figure 4 As shown, the method may include the following steps:
[0370] Step 401, PINE sends first information to the PIN server;
[0371] The first information includes at least one of the following:
[0372] The third indication information is used to indicate whether the PINE has a gateway capability or not;
[0373] Fourth indication information, used to instruct the PINE to accept or refuse to be a PEGC in the PIN;
[0374] Parameter information of the PINE.
[0375] It should be noted that the various contents of the first information in the embodiment of the present application are similar to those in the Figure 2 The corresponding content of the first information in the method embodiment shown has the same meaning and function, and can be specifically referred to as Figure 2In addition, PINE can provide the PIN server with the first information for assisting in determining the PEGC in the PIN. For example, whether there are available PEGCs in the PIN, which PEGCs are not accepted as PEGCs in the PIN, whether PEMC can be used as PEGC in the PIN, etc., and how to deal with the situation when there is no PINE that is accepted as PEGC in the PIN, such as: deactivating the PIN, refusing to establish the PIN, or updating the PEGC in the PIN, etc. Figure 2 The similar beneficial effects of the illustrated method embodiments are not described again here to avoid repetition.
[0376] Optionally, the parameter information of the PINE includes at least one of the following:
[0377] The media access control MAC address of the PINE;
[0378] The Internet Protocol (IP) address of the PINE;
[0379] The port number of the PINE;
[0380] Capability information of the PINE.
[0381] Optionally, the capability information of the PINE includes at least one of the following:
[0382] The maximum number of PINEs supported when the PINE is used as a PEGC;
[0383] The maximum transmission rate supported by the PINE;
[0384] The maximum transmission rate supported by PINE as PEGC;
[0385] The maximum number of PINs supported when the PINE is used as a PEGC.
[0386] In a first implementation manner, the PINE sends first information to the PIN server, including:
[0387] 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.
[0388] In a second implementation manner, before the PINE sends the first information to the PIN server, the method further includes:
[0389] 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;
[0390] The PINE sends first information to the PIN server, including:
[0391] 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.
[0392] In a third embodiment, the method further comprises:
[0393] 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;
[0394] 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.
[0395] It should be noted that the final PEGC in the PIN can be determined by combining at least one of the above three implementation modes.
[0396] 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.
[0397] In the embodiment of the present application, the information transmission method performed by PINE is similar to the following Figure 2 The method shown in the embodiment corresponds to the information processing method performed by the PIN server, and can obtain the same Figure 2 The similar beneficial effects of the illustrated method embodiments are not described again here to avoid repetition.
[0398] In order to facilitate understanding of the information processing method and information transmission method provided in the embodiments of the present application, the following four implementation modes are taken as examples to illustrate the interaction between the PIN server, PEMC and PINE:
[0399] Example 1: After PIN is created, PEMC synchronizes PINE information that cannot become PEGC to the PIN server
[0400] like Figure 5a As shown, the interaction between the PIN server, PEMC and PINE includes the following steps:
[0401] Step 1: After the PIN is created, the PEMC sends a third request (such as a PINCreation notification request) to the PEGC indicated by the PIN server, the purposes of which may include: 1. notifying that the PEGC is added to the PIN; 2. indicating that PINE-1 is the PEGC in the PIN.
[0402] Step 2: PINE-1 cannot become the PEGC in the PIN indicated by PEMC due to device reasons, capability reasons (such as being set by the user, the maximum number of supported PINs has been reached), etc. Therefore, PINE-1 sends a third response (such as PIN creation notification reject) to PEMC.
[0403] 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.
[0404] Step 3: PEMC sends third information to the PIN server (assuming that the message carrying the third information is the first request message), where the third information is used to request the PIN server to update the PEGC in the PIN.
[0405] For example: after PEMC receives a PIN creation notification reject message from PINE-1; or after PEMC receives an instruction from the PIN server to become the PEGC in the PIN, and after PEMC determines that it cannot become the PEGC, PEMC requests the PIN server to update the PEGC in the PIN.
[0406] Optionally, the first request message carrying the third information may specifically be: a PIN configuration request message, or a PIN creation notification request message.
[0407] It is worth noting that in the related art, PIN creation notification request is only used for PEMC to notify PEGC to be added to PIN or to indicate PINE-1 as PEGC in PIN. In the embodiment of the present application, PIN creation notification request can be reused to request PIN server to update PEGC in PIN.
[0408] Optionally, the first request message includes first indication information, the first indication information indicating that the PIN is in a deactivated state, or indicating that there is no available PEGC in the PIN. The PIN being in a deactivated state 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.
[0409] In some implementations, the first request message is a PIN creation notification request message, wherein the PEGC identifier is set to:
[0410] (a) the PINE-1ID (i.e. the PINE that sends the PIN creation notification reject message and refuses to become a PEGC); or,
[0411] (b) PEMC ID (i.e., the PEMC is instructed to be a PEGC but the PEMC itself does not have the relevant capabilities of a PEGC).
[0412] The PEGC address is set to:
[0413] (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,
[0414] (b) PEMC address information (ie, PEMC is instructed to become PEGC but PEMC itself does not have the relevant capabilities of PEGC).
[0415] The format and content of the PIN creation notification request message are shown in Table 1 below:
[0416] Table 1
[0417]
[0418] In some implementations, the first request message is a PIN configuration request message, wherein:
[0419] (1) Authorization type is set to PEGC role change; and
[0420] (2) The PINE ID of predecessor in the role (PINE ID) is set to:
[0421] (a) the PINE-1ID (i.e. the PINE that sends the PIN creation notification reject message and refuses to become a PEGC); and / or,
[0422] (b) PEMC ID (i.e., the PEMC is instructed to be a PEGC but the PEMC itself does not have the relevant capabilities of a PEGC).
[0423] When both (a) and (b) are included, PINE ID of predecessor in the role can be understood as a list including at least one ID information.
[0424] The format and content of the PIN creation notification request message are shown in Table 2 below:
[0425] Table 2
[0426]
[0427] Step 4: The PIN server receives the first request message sent by the PEMC.
[0428] Optionally, the first request message is a PIN configuration request message or a PIN creation notification request message.
[0429] In some implementations, 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:
[0430] (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;
[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 PEGC information in a PIN, the PIN being identified by a PIN ID;
[0433] (b) Sending a PIN creation notification response message to the PEMC, wherein the PIN creation notification response message includes: the PEGC information in the PIN updated by the PIN server. When no other PINE can be used as the PEGC except the PEMC, the PEGC information in the updated PIN is set to the information of the PEMC. At this time, the PIN server determines that there is no available PEGC in the PIN.
[0434] In some implementations, 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:
[0435] (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;
[0436] (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:
[0437] (a) updating PEGC information in a PIN, the PIN being identified by a PIN ID;
[0438] (b) Sending a PIN configuration response message to the PEMC, wherein the PIN configuration response message includes: the PEGC information in the PIN updated by the PIN server. When no other PINE can be used as the PEGC except the PEMC, the PEGC information in the updated PIN is set to the information of the PEMC. At this time, the PIN server determines that there is no available PEGC in the PIN.
[0439] After receiving the PIN configuration response message, the PEMC performs at least one of the following:
[0440] (1) updating the PEGC information in the PIN based on the PEGC information in the PIN updated by the PIN server;
[0441] (2) If the PEGC information in the PIN updated by the PIN server is the PEMC information, and:
[0442] (a) The PIN configuration request message sent by the PEMC meets the following conditions:
[0443] (i) Authorization type is set to PEGC role change; and
[0444] (ii) PINE ID of predecessor in the role (PINE ID of the predecessor in the PEGC role) includes: PEMC ID;
[0445] Then, the PEMC considers that the PIN server has determined that there is no available PEGC in the PIN; or
[0446] (b) When condition (i) is met, or only condition (ii) is met, or condition (i) and (ii) are not met, PEMC must confirm whether it can become PEGC. If PEMC cannot become PEGC, step 3 of this embodiment is executed, that is, at this time PEMC satisfies conditions (2)-(b) of step 3: PEMC receives an instruction from the PIN server to become a PEGC in the PIN, and PEMC determines that it cannot become a PEGC.
[0447] Example 2: After the PIN is created, the PIN server triggers the update of the PEGC in the PIN to the PEMC
[0448] like Figure 5b As shown, the interaction between the PIN server, PEMC and PINE includes the following steps:
[0449] Step 1: PINE-2 sends registration information (such as PINE registration request) to the PIN server for registering with the PIN server. The PINE registration request message includes indication information, and the indication information is used to indicate at least one of the following: PINE-2 has gateway capability; PINE-2 can become a gateway in the PIN.
[0450] Optionally, the PINE registration request also includes: MAC address, IP address, port number, 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.
[0451] Step 2: The PIN server sends a PINE registration acceptance message to PINE-2 to confirm that PINE-2 is successfully registered in the PIN server. It is worth noting that step 2, as an independent process associated with step 1, can also be executed after step 3 or step 4. The execution order of step 1, step 2, step 3 and step 4 is not limited here.
[0452] Step 3: If at least one of the following is met:
[0453] (1) The PEGC information in the PIN changes;
[0454] (2) The PIN server determines that there is no available PEGC in the PIN;
[0455] 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.
[0456] Optionally, the second request message includes at least one of the following: PIN ID; modification type (Modification type); PINE ID of predecessor in the role (PINE ID of the specified role); PIN profile information (PIN profile information); dynamic PIN profile information (Dynamic PIN profile information).
[0457] Exemplarily, the second request message may be a PIN configuration command (PIN configuration command), and the content carried by the second request message is shown in the following Table 3:
[0458] Table 3
[0459]
[0460] Step 4: PEMC responds to the second request message described in step 3 to indicate the execution result of step 3.
[0461] 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; a result (Result) information, used to indicate the result of the second request message; a cause value (cause), used to indicate the cause of the failure; a PINE ID of failure (PINE ID of failure), used to indicate the PINE ID of the execution failure.
[0462] For example, the content carried by a PIN configuration complete is shown in Table 4 below:
[0463] Table 4
[0464]
[0465] Example 3: During the creation of a PIN, the PIN server confirms the role of the PEGC
[0466] like Figure 5c As shown, the interaction between the PIN server, PEMC and PINE includes the following steps:
[0467] Step 1: PEMC sends a PIN Creation request to the PIN server in order to create a PIN.
[0468] Step 2: After receiving the PIN Creation request sent by PEMC, the PIN server performs at least one of the following:
[0469] (1) Identify PINEs (except PEMC) in PIN that can serve as PEGC, such as PINE-3.
[0470] (2) Send a second request (assuming it is carried in a third request message) to PINE-3, where 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 implementations, the third request message may be a PIN management request message.
[0471] Step 3: After receiving the third request message sent by the PIN server, PINE determines whether it can become a PEGC in the PIN, and sends a message to respond to the third request message. Exemplarily, the third request message is responded to based on the second response (such as a PIN management response message).
[0472] Step 4: The PIN server receives the response message of PINE in step 3. Based on the response message, the PIN server performs at least one of the following:
[0473] (1) Update the PINE in the PIN to become the PEGC information;
[0474] (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 (ie, the PIN Creation response message in the prior art is reused).
[0475] It is worth noting that, in some embodiments, if there is no other PINE except PEMC that can serve as the PEGC in the PIN, the PIN server rejects the request of PEMC to create a PIN, or responds to the request of PEMC 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.
[0476] Example 4: During the creation of a PIN, the PIN server instructs multiple PEGCs, and only some of the PEGCs reject the PEMC's request
[0477] In this embodiment, the PIN server may indicate one or more PEGCs during the creation of the PIN, including a primary PEGC and one or more secondary PEGCs:
[0478] (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, then the PEMC can use the secondary PEGC as the primary PEGC in the PIN;
[0479] (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.
[0480] It is worth noting that the above-mentioned fourth embodiment can be used together with Figure 5a The embodiment 1 shown is used in combination. For example, when at least one PEGC can serve the PIN, the PEMC can also use the embodiment 1 to report the information of the PEGC that cannot serve the PIN to the PIN server while ignoring the rejected or unreachable PEGC.
[0481] The above-mentioned fourth embodiment can be used together with Figure 5b The second embodiment shown is used in combination. For example, when at least one PEGC can serve the PIN, the PIN server can also update the PEGC information to the PIN.
[0482] The above-mentioned fourth embodiment can be used together with Figure 5cThe third embodiment shown is 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.
[0483] The above-mentioned embodiment 4, as Figure 5a The embodiment 1 and the Figure 5c The third embodiment shown 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.
[0484] 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.
[0485] See also Figure 6 The information processing device 600 provided in the embodiment of the present application may be a device within a PIN server.
[0486] like Figure 6 As shown, the information processing device 600 may include the following modules:
[0487] The first receiving module 601 is configured to receive first information, wherein the first information satisfies at least one of the following:
[0488] The first information is related to a PIN element PEGC having gateway capability;
[0489] The first information includes a first request, and the first request is used to request to establish a PIN;
[0490] 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:
[0491] Determine the PEGC information in the PIN;
[0492] rejecting the first request;
[0493] Deactivate PIN;
[0494] Update the personal Internet of Things network element PINE information of PEGC in PIN;
[0495] 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.
[0496] Optionally, the second information indicating that the PINE is accepted as a PEGC in the PIN includes at least one of the following:
[0497] The second information indicates a PINE that is a primary PEGC in the PIN established by the PEMC;
[0498] The second information indicates a PINE which is a secondary PEGC in a PIN established by the PEMC.
[0499] Optionally, the first receiving module 601 is specifically configured to:
[0500] The PIN server receives the first information from the PEMC or PINE.
[0501] Optionally, the first information includes at least one of the following:
[0502] The first identification information is used to identify the PINE that does not accept becoming a PEGC in the PIN;
[0503] The second identification information is used to identify the PEMC that does not have the gateway capability;
[0504] 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;
[0505] 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;
[0506] The third indication information is used to indicate whether the PINE has a gateway capability or not;
[0507] Fourth indication information, used to instruct PINE to accept or reject as PEGC in PIN;
[0508] PINE parameter information;
[0509] The first request.
[0510] Optionally, the parameter information of the PINE includes at least one of the following:
[0511] PINE's media access control MAC address;
[0512] PINE's Internet Protocol (IP) address;
[0513] The port number of PINE;
[0514] PINE's capability information.
[0515] Optionally, the capability information of the PINE includes at least one of the following:
[0516] The maximum number of PINEs supported when PINE is used as PEGC;
[0517] The maximum transfer rate supported by PINE;
[0518] The maximum transmission rate supported by PINE as PEGC;
[0519] Maximum number of PINs supported when PINE is used as PEGC.
[0520] Optionally, the first execution module 602 is specifically configured to:
[0521] 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.
[0522] Optionally, the first execution module 602 is further configured to:
[0523] Sending seventh information to the PEMC, where the seventh information is used to indicate a reason why the PIN establishment fails, or is used to indicate a reason why the PIN is deactivated.
[0524] Optionally, the seventh information is used to indicate at least one of the following:
[0525] No PEGC available;
[0526] PIN is not activated.
[0527] Optionally, the first execution module 602 is further configured to:
[0528] Sending 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.
[0529] Optionally, there is no available PEGC in the PIN, including:
[0530] 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;
[0531] The PEMC does not have gateway capabilities.
[0532] Optionally, when the first information includes the first request from the PEMC, the first execution module 602 is further configured to:
[0533] 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.
[0534] Optionally, the first receiving module 601 is specifically configured to:
[0535] Receive third information from the PEMC, wherein the first information also includes the third information, and 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 PEGCs in the PIN established by the PEMC, or that the PEMC does not have gateway capability.
[0536] Optionally, the third identification information is used to identify at least one of the following:
[0537] A PINE that is a master PEGC in a PIN established by the PEMC;
[0538] The PINE is a secondary PEGC in the PIN established by the PEMC.
[0539] Optionally, the first execution module 602 is specifically configured to:
[0540] According to the first information, update the PINE information of the PEGC in the PIN established by the PEMC;
[0541] sending, to the PEMC, updated identification information of the PINE that accepts to become the PEGC in the PIN established by the PEMC, according to the first information;
[0542] According to the first information, send the identification information of the PEMC to the PEMC, indicating the PEMC as the PEGC in the PIN established by it;
[0543] 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 to deactivate the PIN established by the PEMC, or to receive the first request.
[0544] 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.
[0545] Optionally, the first receiving module 601 is specifically configured to:
[0546] Registration information is received 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 a gateway capability, or whether the PINE accepts or does not accept being a PEGC in a PIN.
[0547] Optionally, the first execution module 602 is specifically configured to execute at least one of the following:
[0548] The PIN server determines, based on the registration information, to accept the PINE as the PEGC in the PIN;
[0549] 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;
[0550] 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
[0551] 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.
[0552] Optionally, the fourth information includes at least one of the following:
[0553] The identification information of the PINE accepted as the PEGC in the PIN after the change;
[0554] Modification type;
[0555] Identification information of the PIN;
[0556] PIN profile information;
[0557] Dynamic PIN profile information.
[0558] Optionally, when the first information includes the first request from the PEMC, the first execution module 602 is further configured to:
[0559] 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;
[0560] The first receiving module 601 is further used for:
[0561] 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.
[0562] Optionally, the first execution module 602 is further configured to execute at least one of the following:
[0563] According to the second response, updating the PINE information of the PEGC accepted as the PIN established by the PEMC;
[0564] 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;
[0565] According to the second response, sending identification information of the PEMC to the PEMC, indicating that the PEMC serves as a PEGC in the PIN established by it;
[0566] 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.
[0567] Optionally, the first execution module 602 is further configured to:
[0568] Fifth information is received from the PEMC, the fifth information indicating that the PEMC accepts or does not accept the PEGC as a PIN established by it, or that the PEMC has or does not have a gateway capability.
[0569] 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.
[0570] Optionally, the first information further includes PEMC-related information or PIN-related information;
[0571] The first operation further includes:
[0572] The sixth information is updated, where the sixth information includes at least one of the following:
[0573] PEMC information;
[0574] PIN profile information.
[0575] The information processing device 600 provided in the embodiment of the present application can realize Figure 2 The various processes implemented by the illustrated method embodiment achieve the same technical effect and will not be described again here to avoid repetition.
[0576] 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.
[0577] See also Figure 7 The information transmission device 700 provided in the embodiment of the present application may be a device within a PEMC.
[0578] like Figure 7 As shown, the information transmission device 700 may include the following modules:
[0579] A first sending module 701, configured to send first information to a PIN server;
[0580] Wherein, the first information includes at least one of the following:
[0581] The first identification information is used to identify the PINE that does not accept becoming a PEGC in the PIN;
[0582] The second identification information is used to identify the PEMC, where the PEMC does not have a gateway capability;
[0583] 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;
[0584] 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;
[0585] A first request is used to request to establish a PIN.
[0586] Optionally, the information transmission device 700 further includes:
[0587] 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;
[0588] The second execution module is used to determine the PEGC in the established PIN according to the second information, or to establish a deactivated PIN.
[0589] Optionally, the information transmission device 700 further includes:
[0590] The third sending module is used 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.
[0591] Optionally, the information transmission device 700 further includes:
[0592] The third receiving module is used 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.
[0593] 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.
[0594] Optionally, the second PINE comprises:
[0595] A PINE that is a master PEGC of a PIN established by the PEMC;
[0596] The PINE is a secondary PEGC of the PIN established by the PEMC.
[0597] Optionally, the second execution module is specifically configured to execute at least one of the following:
[0598] 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;
[0599] 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;
[0600] 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.
[0601] Optionally, the second execution module is further used to:
[0602] 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.
[0603] Optionally, the information transmission device 700 further includes:
[0604] The sixth receiving module is used to receive seventh information from the PIN server, wherein the seventh information is used to indicate the reason for the failure of PIN establishment or the reason for the deactivation of the PIN.
[0605] Optionally, the seventh information is used to indicate at least one of the following:
[0606] No PEGC available;
[0607] PIN is not activated.
[0608] Optionally, the information transmission device 700 further includes:
[0609] 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, and 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.
[0610] The information transmission device 700 provided in the embodiment of the present application can realize Figure 3 The various processes implemented by the illustrated method embodiment achieve the same technical effect and will not be described again here to avoid repetition.
[0611] See also Figure 8 The information transmission device 800 provided in the embodiment of the present application may be a device within a PINE.
[0612] like Figure 8 As shown, the information transmission device 800 may include the following modules:
[0613] The second sending module 801 is used to send the first information to the PIN server;
[0614] The first information includes at least one of the following:
[0615] The third indication information is used to indicate whether the PINE has a gateway capability or not;
[0616] Fourth indication information, used to instruct PINE to accept or reject as PEGC in PIN;
[0617] PINE parameter information.
[0618] Optionally, the parameter information of the PINE includes at least one of the following:
[0619] The media access control MAC address of the PINE;
[0620] The Internet Protocol (IP) address of the PINE;
[0621] The port number of the PINE;
[0622] Capability information of the PINE.
[0623] Optionally, the capability information of the PINE includes at least one of the following:
[0624] The maximum number of PINEs supported when the PINE is used as a PEGC;
[0625] The maximum transmission rate supported by the PINE;
[0626] The maximum transmission rate supported by PINE as PEGC;
[0627] The maximum number of PINs supported when the PINE is used as a PEGC.
[0628] Optionally, the second sending module 801 is specifically configured to:
[0629] 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.
[0630] Optionally, the information transmission device 800 further includes:
[0631] 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;
[0632] The second sending module 801 is further used for:
[0633] A second response is sent to the PIN server, wherein the second response carries the first information, and the first information indicates that the PINE is accepted or rejected as a PEGC in the PIN.
[0634] Optionally, the information transmission device 800 further includes:
[0635] 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;
[0636] The fourth sending module is used to send 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.
[0637] The information transmission device 800 provided in the embodiment of the present application can realize Figure 4 The various processes implemented by the illustrated method embodiment achieve the same technical effect and will not be described again here to avoid repetition.
[0638] like Fig. 9 As shown, the embodiment of the present application further provides a communication device 900, including a processor 901 and a memory 902, the memory 902 stores a program or instruction 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 following Figure 2 When the communication device 900 is a PEMC, the program or instruction is executed by the processor 901 to implement the following Figure 3 The steps of the method embodiment shown in the figure 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 following Figure 4The various steps of the method embodiment shown in the figure can achieve the same technical effect, and to avoid repetition, they will not be described again here.
[0639] The embodiment of the present application also provides a terminal, including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the following Figure 3 or Figure 4 The steps in the method embodiment shown. This terminal embodiment corresponds to the above-mentioned terminal side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to this terminal embodiment and can achieve the same technical effect. Specifically, Fig.10 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.
[0640] 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 a processor 1010.
[0641] Those skilled in the art will appreciate that the terminal 1000 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 1010 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Fig.10 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.
[0642] It should be understood that in the 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 the static picture or video obtained by the image capture device (such as a camera) in the video capture mode or the 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 a joystick, which will not be repeated here.
[0643] In the embodiment of the present application, after receiving downlink data from the network side device, the RF unit 1001 can transmit the data to the processor 1010 for processing; in addition, the RF unit 1001 can send uplink data to the network side device. Generally, the RF unit 1001 includes but is not limited to an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.
[0644] 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, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.), 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.
[0645] The processor 1010 may include one or more processing units; optionally, the processor 1010 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 1010.
[0646] In one implementation, the terminal 1000 functions as a PEMC.
[0647] The radio frequency unit 1001 is used to send the first information to the PIN server;
[0648] Wherein, the first information includes at least one of the following:
[0649] The first identification information is used to identify the PINE that does not accept becoming a PEGC in the PIN;
[0650] The second identification information is used to identify the PEMC, and the PEMC does not have a gateway capability;
[0651] 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;
[0652] 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;
[0653] A first request is used to request to establish a PIN.
[0654] 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;
[0655] The processor 1010 is configured to determine a PEGC in the established PIN according to the second information, or to establish a deactivated PIN.
[0656] Optionally, the radio frequency unit 1001 is further used 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.
[0657] Optionally, the RF 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.
[0658] 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.
[0659] Optionally, the second PINE comprises:
[0660] A PINE that is a master PEGC of a PIN established by the PEMC;
[0661] The PINE is a secondary PEGC of the PIN established by the PEMC.
[0662] Optionally, the determining, according to the second information, a PEGC in the established PIN performed by the processor 1010 includes at least one of the following:
[0663] 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, using the secondary PEGC as the primary PEGC in the PIN established by it;
[0664] 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;
[0665] In the case where 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.
[0666] Optionally, the establishing a deactivated PIN according to the second information executed by the processor 1010 includes:
[0667] 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.
[0668] Optionally, the radio frequency unit 1001 is further used 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.
[0669] Optionally, the seventh information is used to indicate at least one of the following:
[0670] No PEGC available;
[0671] PIN is not activated.
[0672] 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, and 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.
[0673] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the following Figure 3 The relevant description of the information transmission method embodiment shown in the figure achieves the same or corresponding technical effect, and will not be repeated here to avoid repetition.
[0674] In another implementation, the terminal 1000 functions as a PINE.
[0675] The radio frequency unit 1001 is used to send the first information to the PIN server;
[0676] The first information includes at least one of the following:
[0677] The third indication information is used to indicate whether the PINE has a gateway capability or not;
[0678] Fourth indication information, used to instruct the PINE to accept or refuse to be a PEGC in the PIN;
[0679] Parameter information of the PINE.
[0680] Optionally, the parameter information of the PINE includes at least one of the following:
[0681] The media access control MAC address of the PINE;
[0682] The Internet Protocol (IP) address of the PINE;
[0683] The port number of the PINE;
[0684] Capability information of the PINE.
[0685] Optionally, the capability information of the PINE includes at least one of the following:
[0686] The maximum number of PINEs supported when the PINE is used as a PEGC;
[0687] The maximum transmission rate supported by the PINE;
[0688] The maximum transmission rate supported by PINE as PEGC;
[0689] The maximum number of PINs supported when the PINE is used as a PEGC.
[0690] Optionally, the sending of the first information to the PIN server performed by the radio frequency unit 1001 includes:
[0691] 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.
[0692] 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;
[0693] The sending of the first information to the PIN server performed by the radio frequency unit 1001 includes:
[0694] A second response is sent to the PIN server, wherein the second response carries the first information, and the first information indicates that the PINE is accepted or rejected as a PEGC in the PIN.
[0695] Optionally, the radio frequency unit 1001 is further configured to:
[0696] 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;
[0697] 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.
[0698] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the following Figure 4 The relevant description of the information transmission method embodiment shown in the figure achieves the same or corresponding technical effect, and will not be repeated here to avoid repetition.
[0699] The embodiment of the present application also 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 used to run a program or instruction to implement the following Figure 2 or Figure 3 or Figure 4 The steps of the method embodiment shown. This network side device embodiment corresponds to the above network side device method embodiment, and each implementation process and implementation mode of the above method embodiment can be applied to this network side device embodiment and can achieve the same technical effect.
[0700] Specifically, the embodiment of the present application also provides a network side device. Fig.11As shown, 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. The antenna 1101 is connected to the radio frequency device 1102. In the uplink direction, the radio frequency device 1102 receives information through the antenna 1101 and sends the received information to the baseband device 1103 for processing. In the downlink direction, the baseband device 1103 processes the information to be sent and sends it to the radio frequency device 1102. The radio frequency device 1102 processes the received information and sends it out through the antenna 1101.
[0701] 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.
[0702] The baseband device 1103 may include, for example, at least one baseband board on which a plurality of chips are arranged. Fig.11 As shown, 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 to execute the network device operations shown in the above method embodiment.
[0703] The network side device may further include a network interface 1106, which is, for example, a Common Public Radio Interface (CPRI).
[0704] Specifically, the network side device 1100 of the embodiment of the present application further includes: instructions or programs stored in the memory 1105 and executable on the processor 1104, and the processor 1104 calls the instructions or programs in the memory 1105 to execute Figure 6 or Figure 7 or Figure 8 The methods executed by the modules shown achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.
[0705] Specifically, the embodiment of the present application also provides a network side device. Fig.12 As shown, 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).
[0706] Specifically, the network side device 1200 of the embodiment of the present application further includes: instructions or programs stored in the memory 1203 and executable on the processor 1201, and the processor 1201 calls the instructions or programs in the memory 1203 to execute as follows: Figure 6The methods executed by the modules shown achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.
[0707] The 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 following is implemented: Figure 2 or Figure 3 or Figure 4 The various processes of the method embodiment shown can achieve the same technical effect, and will not be described again here to avoid repetition.
[0708] 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-transient readable storage medium.
[0709] The present application embodiment further provides a chip, the chip includes a processor and a communication interface, the communication interface is coupled to the processor, the processor is used to run a program or instruction, to implement the following Figure 2 or Figure 3 or Figure 4 The various processes of the method embodiment shown can achieve the same technical effect, and will not be described again here to avoid repetition.
[0710] 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.
[0711] The present application embodiment further provides a computer program / program product, wherein the computer program / program product is stored in a storage medium, and the computer program / program product is executed by at least one processor to implement the following Figure 2 or Figure 3 or Figure 4 The various processes of the method embodiment shown can achieve the same technical effect, and will not be described again here to avoid repetition.
[0712] The embodiment of the present application also provides a communication system, including: a PIN server, a PEMC and a PINE, wherein the PIN server can be used to perform the following steps: Figure 2 The steps of the method embodiment shown in FIG. 1 and FIG. 2 are used to perform the following steps: Figure 3 The steps of the method embodiment shown in FIG. 1 and FIG. 2 are used to perform the following steps: Figure 4 Steps of the method embodiment are shown.
[0713] It should be noted that, in this article, the term "comprises", "includes" or any other variant thereof is intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "including one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the method and device in the embodiment 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.
[0714] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment method can be implemented by means of a computer software product plus a hardware platform, and of course, it can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, disk, CD, etc.), including several instructions to enable the terminal or network side device to execute the methods described in each embodiment of the present application.
[0715] 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 the present application, ordinary technicians in this field can also make many forms of implementation methods without departing from the purpose of the present application and the scope of protection of the claims, and these implementation methods are all within the protection of the present application.
Claims
1. An information processing method, characterized in that: include: 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, characterized in that 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, characterized in that: 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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 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.
14. The method according to claim 12 or 13, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that: include: 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, characterized in that The method further comprises: 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, characterized in that The method further comprises: 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, characterized in that The method further comprises: 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that The method further comprises: 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 according to claim 33, characterized in that 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, characterized in that The method further comprises: Based on the seventh information or the eighth indication information, the PEMC sends ninth indication information to the PINE in the PIN, 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. An information transmission method, characterized in that: include: 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 according to claim 36, characterized in that 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 according to claim 37, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that The method further comprises: 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, characterized in that: include: 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, characterized in that: include: 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, characterized in that: include: 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, characterized in that: It includes a processor and a memory, 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, it 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.
46. A readable storage medium, characterized in that The readable storage medium stores programs or instructions, 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.
Citation Information
Cited By
Information processing method and apparatus, information transmission method and apparatus, and related device
EP4712539A1
