Information synchronization method, service switching method, request processing method, and device

Abstract

The present application belongs to the technical field of communications, and discloses an information synchronization method, a service switching method, a request processing method, and a device. The information synchronization method in embodiments of the present application comprises: during a PIN creation process or a PIN registration process, a first device executes a first operation. The first operation comprises at least one of the following: receiving a first message from a PIN server, the first message comprising first information; and sending a second message to the PIN server, the second message comprising the first information. The first information comprises at least one of the following: PIN service information, service information of the first device, and PIN description information.

Description

Information synchronization method, service switching method, request processing method and device

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

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

[0003] The present application belongs to the field of communication technology, and specifically relates to an information synchronization method, a service switching method, a request processing method and a device. Background Art

[0004] In a communication system supporting a Personal IoT Network (PIN), a PIN can include one or more Personal IoT Network Elements (PINEs), which can be Internet of Things (IoT) devices or terminals with communication capabilities. In related technologies, PIN-related information cannot be synchronized in a timely manner, or devices cannot negotiate before service switching, resulting in poor PIN service performance.

[0005] Summary of the Invention

[0006] The embodiments of the present application provide an information synchronization method, a service switching method, a request processing method and a device, which can solve the problem of poor PIN service performance caused by the inability to synchronize PIN related information in a timely manner or the inability to negotiate between devices before service switching.

[0007] In a first aspect, an information synchronization method is provided, comprising:

[0008] During a PIN creation process or a PIN registration process, the first device performs a first operation;

[0009] The first operation includes at least one of the following:

[0010] receiving a first message from a PIN server, wherein the first message includes first information;

[0011] sending a second message to the PIN server, where the second message includes the first information;

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

[0013] PIN service information;

[0014] service information of the first device;

[0015] PIN description information.

[0016] In a second aspect, an information synchronization method is provided, comprising:

[0017] During the personal IoT PIN creation process or the PIN registration process, the PIN server performs a second operation;

[0018] The second operation includes at least one of the following:

[0019] Sending a first message to a first device, where the first message includes first information;

[0020] receiving a second message from the first device, where the second message includes the first information;

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

[0022] PIN service information;

[0023] service information of the first device;

[0024] PIN description information.

[0025] In a third aspect, a service switching method is provided, including:

[0026] A first device in a PIN sends a first request message to a second device, where the first request message is used to negotiate a service switching in the PIN.

[0027] In a fourth aspect, a service switching method is provided, comprising:

[0028] The second device in the PIN receives a first request message from the first device, where the first request message is used to negotiate a service switching in the PIN.

[0029] In a fifth aspect, a request processing method is provided, comprising:

[0030] The first device receives a PIN service discovery request message sent by the fourth device;

[0031] The first device sends a PIN service discovery response message to the fourth device, where the PIN service discovery response message includes a first list;

[0032] The first list is a list of devices that support service switching in the PIN, and the first list is determined based on first information, and the first information includes at least one of the following:

[0033] PIN service information;

[0034] service information of the first device;

[0035] PIN description information;

[0036] Alternatively, the first list is a list of devices that meet the first condition;

[0037] The first condition includes at least one of the following:

[0038] having a direct connection with the fourth device;

[0039] having a first application client, the first application client comprising: an application client deployed by the fourth device or an application client corresponding to a switching service;

[0040] Support service switching.

[0041] In a sixth aspect, an information synchronization device is provided, comprising:

[0042] An execution module, configured to execute a first operation during a personal IoT PIN creation process or a PIN registration process;

[0043] The first operation includes at least one of the following:

[0044] receiving a first message from a PIN server, wherein the first message includes first information;

[0045] sending a second message to the PIN server, where the second message includes the first information;

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

[0047] PIN service information;

[0048] service information of the first device;

[0049] PIN description information.

[0050] In a seventh aspect, an information synchronization device is provided, comprising:

[0051] An execution module, configured to execute a second operation during a personal IoT PIN creation process or a PIN registration process;

[0052] The second operation includes at least one of the following:

[0053] Sending a first message to a first device, where the first message includes first information;

[0054] receiving a second message from the first device, where the second message includes the first information;

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

[0056] PIN service information;

[0057] service information of the first device;

[0058] PIN description information.

[0059] In an eighth aspect, a service switching device is provided, comprising:

[0060] A sending module is used to send a first request message to a second device, where the first request message is used to negotiate service switching in a PIN, and the device corresponding to the device is a device in a personal Internet of Things network PIN.

[0061] In a ninth aspect, a service switching device is provided, comprising:

[0062] The receiving module is used to receive a first request message from a first device, where the first request message is used to negotiate service switching in the PIN, and the device corresponding to the device is a device in the personal Internet of Things network PIN.

[0063] In a tenth aspect, a request processing device is provided, comprising:

[0064] A receiving module, configured to receive a personal Internet of Things network PIN service discovery request message sent by a fourth device;

[0065] a sending module, configured to send a PIN service discovery response message to the fourth device, where the PIN service discovery response message includes the first list;

[0066] The first list is a list of devices that support service switching in the PIN, and the first list is determined based on first information, and the first information includes at least one of the following:

[0067] PIN service information;

[0068] service information of the first device;

[0069] PIN description information;

[0070] Alternatively, the first list is a list of devices that meet the first condition;

[0071] The first condition includes at least one of the following:

[0072] having a direct connection with the fourth device;

[0073] having a first application client, the first application client comprising: an application client deployed by the fourth device or an application client corresponding to a switching service;

[0074] Support service switching.

[0075] In the eleventh aspect, a device is provided, which includes a processor and a memory, the memory storing a program or instruction that can be run on the processor, wherein the program or instruction is executed by the processor to implement the steps of the information synchronization method on the first device side as provided in the embodiment of the present application, or the program or instruction is executed by the processor to implement the steps of the information synchronization method on the PIN server side as provided in the embodiment of the present application, or the program or instruction is executed by the processor to implement the steps of the service switching method on the first device side as provided in the embodiment of the present application, or the program or instruction is executed by the processor to implement the steps of the service switching method on the second device side as provided in the embodiment of the present application, or the program or instruction is executed by the processor to implement the steps of the request processing method provided in the embodiment of the present application.

[0076] In the twelfth aspect, a device is provided, comprising a processor and a communication interface, wherein the communication interface is used to perform a first operation during a personal Internet of Things PIN creation process or a PIN registration process; wherein the first operation includes at least one of the following: receiving a first message from a PIN server, the first message including first information; sending a second message to the PIN server, the second message including the first information; wherein the first information includes at least one of the following: PIN service information; service information of the first device; PIN description information.

[0077] In the thirteenth aspect, a device is provided, comprising a processor and a communication interface, wherein the communication interface is used to perform a second operation during a personal Internet of Things PIN creation process or a PIN registration process; wherein the second operation includes at least one of the following: sending a first message to a first device, the first message including first information; receiving a second message from the first device, the second message including the first information; wherein the first information includes at least one of the following: PIN service information; service information of the first device; PIN description information.

[0078] In the fourteenth aspect, a device is provided, including a processor and a communication interface, wherein the communication interface is used to send a first request message to a second device, the first request message is used to negotiate service switching in a PIN, and the device corresponding to the device is a device in a personal Internet of Things network PIN.

[0079] In a fifteenth aspect, a device is provided, comprising a processor and a communication interface, wherein the communication interface is used to receive a first request message from a first device, and the first request message is used to negotiate a service switching in a PIN.

[0080] In the sixteenth aspect, a device is provided, comprising a processor and a communication interface, wherein the communication interface is used to receive a personal Internet of Things network PIN service discovery request message sent from a fourth device; send a PIN service discovery response message to the fourth device, and the PIN service discovery response message includes a first list; wherein the first list is a list of devices that support service switching in the PIN, and the first list is determined based on first information, the first information includes at least one of the following: PIN service information; service information of the first device; PIN description information; or, the first list is a list of devices that meet a first condition; the first condition includes at least one of the following: having a direct connection with the fourth device; having a first application client, the first application client including: an application client deployed by the fourth device or an application client corresponding to the switching service; supporting service switching.

[0081] In the seventeenth 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 information synchronization method on the first device side as provided in the embodiment of the present application are implemented, or the steps of the information synchronization method on the PIN server side as provided in the embodiment of the present application are implemented, or the steps of the service switching method on the first device side as provided in the embodiment of the present application are implemented, or the steps of the service switching method on the second device side as provided in the embodiment of the present application are implemented, or the steps of the request processing method as provided in the embodiment of the present application are implemented.

[0082] In aspect 18, a wireless communication system is provided, including: a first device and a PIN server, wherein the first device can be used to execute the steps of the information synchronization method on the first device side provided in the embodiment of the present application, and the PIN server can be used to execute the steps of the information synchronization method on the PIN server side provided in the embodiment of the present application.

[0083] In the nineteenth aspect, a wireless communication system is provided, including: a first device and a second device, wherein the first device can be used to execute the steps of the service switching method on the first device side provided in the embodiment of the present application, or the first device can be used to execute the steps of the request processing method provided in the embodiment of the present application, and the second device can be used to execute the steps of the service switching method on the second device side provided in the embodiment of the present application.

[0084] In the twentieth aspect, a chip is provided, which includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the information synchronization method on the first device side as provided in the embodiment of the present application, or to implement the information synchronization method on the PIN server side as provided in the embodiment of the present application, or to implement the steps of the service switching method on the first device side as provided in the embodiment of the present application, or to implement the steps of the service switching method on the second device side as provided in the embodiment of the present application, or to implement the steps of the request processing method provided in the embodiment of the present application.

[0085] In aspect 21, a computer program / program product is provided, which is stored in a storage medium, and is executed by at least one processor to implement the steps of the information synchronization method on the first device side as provided in the embodiment of the present application, or the computer program / program product is executed by at least one processor to implement the steps of the information synchronization method on the PIN server side as provided in the embodiment of the present application, or the computer program / program product is executed by at least one processor to implement the steps of the service switching method on the first device side as provided in the embodiment of the present application, or the computer program / program product is executed by at least one processor to implement the steps of the service switching method on the second device side as provided in the embodiment of the present application, or the computer program / program product is executed by at least one processor to implement the steps of the request processing method provided in the embodiment of the present application.

[0086] In an embodiment of the present application, during a PIN creation process or a PIN registration process, a first device performs a first operation; wherein the first operation includes at least one of the following: receiving a first message from a PIN server, the first message including first information; sending a second message to the PIN server, the second message including the first information; wherein the first information includes at least one of the following: PIN service information; service information of the first device; or PIN description information. Because the first device performs the first operation during the PIN creation process or the PIN registration process, synchronization of PIN-related information during the PIN creation process or the PIN registration process can be achieved through at least one of the first and second messages, thereby avoiding the problem of PIN service performance being affected by failure to synchronize PIN-related information in a timely manner, thereby improving PIN service performance. BRIEF DESCRIPTION OF THE DRAWINGS

[0087] FIG1 is a block diagram of a wireless communication system to which embodiments of the present application may be applied;

[0088] FIG2 is a flow chart of an information synchronization method provided in an embodiment of the present application;

[0089] FIG3 is a schematic diagram of information synchronization provided by an embodiment of the present application;

[0090] FIG4 is a schematic diagram of another information synchronization method provided by an embodiment of the present application;

[0091] FIG5 is a schematic diagram of another information synchronization method provided by an embodiment of the present application;

[0092] FIG6 is a schematic diagram of another information synchronization method provided by an embodiment of the present application;

[0093] FIG7 is a flowchart of another information synchronization method provided in an embodiment of the present application;

[0094] FIG8 is a flow chart of a service switching method provided in an embodiment of the present application;

[0095] FIG9 is a flowchart of another service switching method provided in an embodiment of the present application;

[0096] FIG10 is a flowchart of a request processing method provided in an embodiment of the present application;

[0097] FIG11 is a structural diagram of an information synchronization device provided in an embodiment of the present application;

[0098] FIG12 is a structural diagram of another information synchronization device provided in an embodiment of the present application;

[0099] FIG13 is a structural diagram of a service switching device provided in an embodiment of the present application;

[0100] FIG14 is a structural diagram of another service switching device provided in an embodiment of the present application;

[0101] FIG15 is a structural diagram of a request processing device provided in an embodiment of the present application;

[0102] FIG16 is a structural diagram of a communication device provided in an embodiment of the present application;

[0103] FIG17 is a structural diagram of a device provided in an embodiment of the present application;

[0104] FIG18 is a structural diagram of another device provided in an embodiment of the present application. DETAILED DESCRIPTION

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

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

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

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

[0109] FIG1 shows a block diagram of a wireless communication system applicable to an embodiment of the present application. The wireless communication system includes a terminal 11 and a network-side device 12. The terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (PDA), a handheld computer, a netbook, an ultra-mobile personal computer (UMPC), a mobile internet device (MID), an augmented reality (AR), a virtual reality (VR) device, a robot, a wearable device (Wearable Device), an aircraft (Flight Vehicle), a vehicle-mounted device (VUE), a ship-mounted device, a pedestrian user equipment (PUE), an IoT device, a smart home (home appliances with wireless communication capabilities, such as refrigerators, televisions, washing machines, printers, or furniture), a game console, a personal computer (PC), a teller machine (ATM), or a self-service machine, etc. 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, vehicle-mounted controller, vehicle-mounted module, vehicle-mounted component, vehicle-mounted chip or 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.

[0110] 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 (RAN) device, a radio access network function, or a radio access network unit. The access network device may include a base station, a wireless local area network (WLAN) access point (AP), or a wireless fidelity (WiFi) node. Among them, the base station can be referred to as Node B (NB), Evolved Node B (eNB), the next generation Node B (gNB), New Radio Node B (NR Node B), access point, Relay Base Station (RBS), Serving Base Station (SBS), Base Transceiver Station (BTS), radio base station, radio transceiver, Basic Service Set (BSS), Extended Service Set (ESS), Home Node B (HNB), Home evolved Node B (home evolved Node B), Transmission Reception Point (TRP) or other appropriate terms in the relevant field. As long as the same technical effect is achieved, the base station is not limited to specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0111] The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (MME), access mobility management function (AMF), session management function (SMF), user plane function (UPF), policy control function (PCF), policy and charging rules function unit (PCRF), edge application service discovery function (EASDF), unified data management (UDM), unified data repository (UDR), home user server (HSS), centralized network configuration (CNC), network storage function (NRF), network exposure function (NEF), local NEF (L-NEF), binding support function (BSF), application function ( 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.

[0112] In the embodiment of the present application, the above system further includes: a PIN server and an application server (AS). The specific types of the PIN server and AS are not limited in this application example.

[0113] In an embodiment of the present application, a PIN includes one or more PINEs. A PINE may be the above-mentioned terminal, such as a terminal with communication capabilities, or an IoT device, such as a smart home. Specifically, it may be a household appliance with wireless communication capabilities, such as a refrigerator, a television, a washing machine, a printer, or furniture.

[0114] The PIN includes a PIN element with management capability (PEMC) and a PIN element with gateway capability (PEGC).

[0115] Below, in combination with the accompanying drawings, an information synchronization method, a service switching method, an apparatus and a device provided by the embodiments of the present application are described in detail through some embodiments and their application scenarios.

[0116] Please refer to FIG2 , which is a flowchart of an information synchronization method provided in an embodiment of the present application. As shown in FIG2 , the method includes the following steps:

[0117] Step 201: During a PIN creation process or a PIN registration process, a first device performs a first operation.

[0118] The first operation includes at least one of the following:

[0119] receiving a first message from a PIN server, wherein the first message includes first information;

[0120] sending a second message to the PIN server, where the second message includes the first information;

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

[0122] PIN service information;

[0123] service information of the first device;

[0124] PIN description information.

[0125] Among them, the above-mentioned PIN creation process can be a creation process in which the above-mentioned first device requests the PIN server to create a PIN, and the above-mentioned first device can be a PINE or PEMC, specifically a terminal in an embodiment of the present application, such as a terminal with conventional communication functions (such as a mobile phone), or an IoT device, or a smart home, etc.

[0126] In the above-mentioned PIN creation process or PIN registration process, the first device performing the first operation may be performing the first operation at the beginning, middle or end stage of the PIN creation process or PIN registration process.

[0127] The first message may be any message sent by the PIN server to the first device during a PIN creation process or a PIN registration process, and the message includes the first information.

[0128] In the above steps, since the first message is received from the PIN server during the PIN creation process or the PIN registration process, the first message includes the above first information, so that the first device and the PIN server can synchronize the first information during the PIN creation process or the PIN registration process.

[0129] The second message may be any message sent by the first device to the PIN server during a PIN creation process or a PIN registration process, and the message includes the first information.

[0130] In the above steps, since the second message is sent to the PIN server during the PIN creation process or the PIN registration process, the second message includes the above first information, so that the first device and the PIN server can synchronize the first information during the PIN creation process or the PIN registration process.

[0131] The PIN service information may be related information used to describe the services provided by the PIN.

[0132] The service information of the first device may be related information for describing the service provided by the first device in the PIN.

[0133] The PIN description information may be related information used to describe the PIN.

[0134] In the embodiment of the present application, the above steps can be used to enable the first device to perform the first operation during the PIN creation process or the PIN registration process. Thus, at least one of the above-mentioned first message and second message can be used to synchronize PIN-related information during the PIN creation process or the PIN registration process, thereby avoiding the problem of the PIN service performance being affected by the inability to synchronize the PIN-related information in a timely manner, thereby improving the PIN service performance. For example, by synchronizing the PIN-related information during the PIN creation process or the PIN registration process, the problem of the first device or the PIN server being unable to obtain the services supported by the PIN in a timely manner, resulting in the PIN service being limited by the first device or the PIN server, thereby affecting the PIN service performance, can be avoided. Synchronizing the PIN-related information during the PIN creation process or the PIN registration process enables the first device or the server to obtain the services supported by the PIN in a timely manner, allowing the first device or the PIN server to better provide services, thereby improving the PIN service performance.

[0135] As an optional implementation manner, the PIN service information includes at least one of the following:

[0136] An identifier of a service provider of the service provided by the PIN;

[0137] The service type of the service provided by the PIN;

[0138] Service characteristics of the service provided by the PIN.

[0139] The service provided by the PIN may be the sum of services provided by all PINEs in the PIN.

[0140] The service provider identifier may be a client ID, a Generic Public Subscription Identifier (GPSI), or an identity token.

[0141] The above service types may be games, videos, audios, etc.

[0142] The above service characteristics may be characteristics such as service description information or service information.

[0143] In this embodiment, synchronization of at least one of the service provider identification, service type, and service characteristics of the service provided by the PIN can be achieved, so that the PIN server or the first device can better understand the services provided by the PIN, thereby improving the PIN service performance.

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

[0145] an identifier of a service provider of the service provided by the first device;

[0146] a service type of a service provided by the first device;

[0147] Service characteristics of the service provided by the first device.

[0148] The service provided by the first device refers to the service provided by the first device in the PIN.

[0149] In this embodiment, synchronization of at least one of the service provider identification, service type, and service characteristics of the service provided by the first device can be achieved, so that the PIN server or the first device can better understand the service provided by the first device, thereby improving the PIN service performance.

[0150] As an optional implementation manner, the receiving the first message from the PIN server includes:

[0151] A PIN creation response message is received from a PIN server, where the PIN creation response message includes the first information.

[0152] The PIN creation response message may be a PIN creation response message that the PIN server replies to after receiving the PIN creation request message sent by the first device.

[0153] For example: Taking the first device as PINE1 (or PEMC), as shown in Figure 3, PINE1 sends a PIN creation request message to the PIN server, the PIN server processes the PIN creation request, and the PIN server sends a PIN creation response message to PINE1, which includes the above-mentioned first information.

[0154] In this implementation, synchronization of the first information can be achieved through a PIN creation response message, thereby eliminating the need to introduce additional messages and saving transmission overhead of the device.

[0155] It should be noted that, in some embodiments, the embodiments of the present application do not limit the above-mentioned first message to the above-mentioned PIN creation response message. For example, the above-mentioned first message may also be a newly defined message for synchronizing the first information during the PIN creation process or the PIN registration process.

[0156] Optionally, the PIN creation response message carries a PIN profile (PIN profile), and the PIN profile includes the first information.

[0157] The PIN profile may be a profile defined in the protocol, so that the synchronization of the first information can be achieved through the PIN profile defined in the protocol, thereby reducing the complexity of information synchronization.

[0158] The PIN profile may be a PIN profile as shown in Table 1 below:

[0159] Table 1:

[0160] Table 1 above is only an example of a PIN profile, and the embodiments of the present application do not limit the PIN profile.

[0161] In some implementations, the PIN creation response message may be as shown in Table 2:

[0162] Table 2:

[0163] Among them, the above Table 2 is only an example of the PIN creation response message, and the embodiment of the present application does not limit the PIN creation response message.

[0164] In some implementations, the PIN creation response message may also directly carry the first information, and is not limited to carrying the first information through a PIN profile.

[0165] As an optional implementation manner, sending the second message to the PIN server includes:

[0166] A PIN creation request message is sent to a PIN server, where the PIN creation request message includes the first information.

[0167] The PIN creation request message is a request message for requesting the creation of a PIN, for example, the PIN creation request message shown in FIG. 3 .

[0168] In this implementation, the synchronization of the first information can be achieved through the PIN creation request message, so there is no need to introduce additional messages, thereby saving the transmission overhead of the device.

[0169] It should be noted that, in some embodiments, the embodiments of the present application do not limit the above-mentioned second message to the above-mentioned PIN creation request message. For example, the above-mentioned second message may also be a message newly defined in the PIN creation process or the PIN registration process for synchronizing the second information.

[0170] In some implementations, the PIN creation request message may be as shown in Table 3:

[0171] Table 3:

[0172] Among them, the above Table 3 is only an example of the PIN creation request message, and the embodiment of the present application does not limit the PIN creation request message.

[0173] In one embodiment, when creating a PIN, the PIN server includes the PIN profile in a create accept message, or the PEMC includes service information in a create request message, as shown in FIG3 , including the following steps:

[0174] Step 1. The PEMC initiates the PIN creation process and carries service information in the PIN creation request message. The service information includes at least one of the following:

[0175] Provide service provider identification, such as client ID, GPSI, identity token;

[0176] Service type, for example, games, videos, and audio;

[0177] Service characteristics, such as service description information, service information, etc.;

[0178] Optionally, the PIN creation request message also includes PIN description information.

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

[0180] Step 3. The PIN server responds to the PIN creation response (acceptance or rejection) sent by the PEMC. In the case of acceptance, it sends a PIN creation accept message. The PIN creation response message includes a PIN profile.

[0181] In some embodiments, if the PEMC does not carry service information in step 1, the PIN server obtains the service information, which may be obtained through application layer messages, contract signing, etc. Contract signing here means that before the PIN is created, the PIN server has negotiated with the user, for example, what services the PIN can be used for and what services it includes. In this case, the PIN profile on the PIN server side has some initial values, so the PIN server can synchronize the PIN profile with the PEMC in step 3. Application layer messages here refer to the PEMC synchronizing the required parameters in the PIN profile (e.g., services that the PIN can provide) to the PIN server through application layer messages, so the PIN server can synchronize the PIN profile with the PEMC in step 3.

[0182] As an optional implementation manner, sending the second message to the PIN server includes:

[0183] A PIN registration request message is sent to a PIN server, where the PIN registration request message includes the first information.

[0184] The PIN registration request message may be a request message for requesting a PIN server to register in the PIN.

[0185] In some embodiments, the above-mentioned PIN registration request message can be a PINE registration request message as shown in Figure 4. For example: the first device is PINE1. As shown in Figure 4, the first device sends a PINE registration request message to the PIN server. The request message carries first information. The PIN server processes the request and sends a PINE registration response message to the first device.

[0186] In this implementation, synchronization of the first information can be achieved through the PIN registration request message, so there is no need to introduce additional messages, thereby saving transmission overhead of the device.

[0187] In some implementations, the PIN registration request message may be as shown in Table 4:

[0188] Table 4:

[0189] Among them, the above Table 4 is only an example of the PIN registration request message, and the embodiment of the present application does not limit the PIN registration request message.

[0190] In one embodiment, when a PINE registers with a PIN server, it carries service information, as shown in FIG4 , including the following steps:

[0191] Step 1. PINE initiates a PIN registration (eg, PINE registration) process to a PIN server, and carries service information in a PIN registration request message. The PIN registration request message may be a PINE registration request message carrying service information.

[0192] The above service information includes at least one of the following:

[0193] Provide service provider identification, such as client ID, GPSI, identity token;

[0194] Service type, for example, games, videos, and audio;

[0195] Service characteristics, such as service description information, service information, etc.;

[0196] Step 2. Whether the PINE that the PIN server applies for authorization can be registered on the PIN server;

[0197] Step 3. The PIN server responds (accepts or rejects) to PINE's registration request.

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

[0199] The first device sends a first request message to the second device, where the first request message is used to negotiate service switching in the PIN.

[0200] The first request message may be sent to the second device when it is determined to switch the service to the second device, so as to implement negotiation on the service switching with the second device.

[0201] The service switching may be switching the service of the first device in the PIN to the second device.

[0202] In this implementation, negotiation can be performed with the second device before the service is switched to the second device, thereby avoiding the possibility of service switching failure caused by the second device being unprepared, thereby improving the reliability of service switching.

[0203] Optionally, the method further includes:

[0204] The first device receives a first response message from the second device, where the first response message is used to indicate acceptance or rejection of the first request message.

[0205] The first response message is a response made by the second device after receiving the first request message, such as the second device determines whether to accept the first request message according to its own situation.

[0206] The first response message can be used to execute service switching to the second device when the second device accepts the first request message, thereby avoiding service switching failure and improving PIN service performance.

[0207] In the embodiments of the present application, it is not limited to receiving the above-mentioned first response message. For example, in some implementations, a timer can also be started. If the first response message is not received before the timer expires, it is assumed that the second device rejects the above-mentioned first request message.

[0208] Optionally, the first request message includes at least one of the following:

[0209] PIN identification, identification information of the first device, and the first information.

[0210] Among them, the above-mentioned first information refers to the corresponding description of the above-mentioned implementation method and is not repeated here.

[0211] In this implementation, since the first request message includes at least one of the PIN identifier, the identification information of the first device, and the first information, the second device can better determine whether to accept the first request message, thereby making service switching more reliable.

[0212] Optionally, when the first response message indicates rejection of the first request message, the first response message includes a cause value, where the cause value is used to indicate at least one of the following:

[0213] Insufficient resources, inability to perform corresponding service operations, authorization failure.

[0214] The aforementioned insufficient resources may indicate that the second device does not have sufficient resources to provide the switching service.

[0215] The above-mentioned inability to perform the corresponding service operation may indicate that the second device is unable to perform the service operation corresponding to the service switching.

[0216] The authorization failure may indicate that the second device has not obtained the corresponding authorization for the service switching, or the second device is unable to authorize the service switching.

[0217] In this implementation, since the above reason value is included in the case of rejection, the first device can learn the reason for rejection by the second device, thereby avoiding subsequent request for corresponding switching to the second device, thereby saving resource overhead.

[0218] Optionally, the method further includes:

[0219] The first device determines the second device, where the second device satisfies at least one of the following:

[0220] The first device is within the coverage of the same PEGC;

[0221] There is a direct connection with the first device.

[0222] The direct connection with the first device refers to a direct connection communication between the first device and the second device.

[0223] In this embodiment, it is possible to negotiate service switching with the second device only when the second device meets at least one of the above items, so that the service can be switched within the coverage of the same PEGC, which can reduce the overhead of PEGC and does not require the introduction of additional PEGC. In addition, switching is performed on devices with direct connections, so that the service after switching is well connected with the service before switching, thereby improving the PIN service performance.

[0224] Optionally, when the first response message indicates rejection of the first request message, the method further includes at least one of the following:

[0225] The first device determines a third device based on the first list;

[0226] The first device terminates the PIN service switching process when there is no available third device in the first list;

[0227] The third device is used for service switching in the PIN, and the first list is a list of devices that support service switching in the PIN.

[0228] The first list may be a first list obtained by the first device from the PEMG, and the devices included in the list support the service switching, or are understood to support services corresponding to the service switching.

[0229] The fact that there is no available third device in the first list may be understood as that there is no available third device in the first list, for example, all devices in the first list reject the first request message.

[0230] The first device determining the third device based on the first list may be selecting the third device from the first list and sending the first request message to the third device to request service switching to the third device. The service switching process after determining the third device is described in the corresponding description of the second device and is not further described here.

[0231] In this implementation, it is possible to select another device for switching or terminate the service switching process after the second device rejects the request, so as to improve the service switching performance or ensure the integrity of the service switching process.

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

[0233] The first device receives a PIN service discovery request message sent by a fourth device;

[0234] The first device responds to the PIN service discovery request message based on the PIN profile;

[0235] The PIN configuration file includes the first information.

[0236] In this implementation manner, the first device may be a PEMC, and the fourth device is a device that requests service switching.

[0237] The above-mentioned PIN service discovery request message can be used to request information about the service requested by the fourth device, such as information about the service to which the fourth device requests service switching.

[0238] The PIN configuration file mentioned above is described in the above embodiments and will not be described in detail here.

[0239] Responding to the PIN service discovery request message based on the PIN profile may include sending a PIN service discovery response message to the fourth device based on the PIN profile. For example, relevant information about the service requested by the PIN service discovery request message may be determined in the PIN profile, and a PIN service discovery response message including the relevant information may be returned to the fourth device. For example, PINE information and application client information for the requested service may be returned to the fourth device.

[0240] In some implementations, the PIN service discovery response message may carry the first list.

[0241] In this implementation, since the PIN service discovery request message is responded to based on the PIN profile, the PIN service discovery request message can be responded to more accurately through the first information in the PIN profile, so as to return accurate response information to the fourth device.

[0242] In one embodiment, before sending a service to another PINE, a PINE needs to interact with the PINE to determine whether the PINE supports service switching, as shown in FIG5 , including the following steps:

[0243] Step 0: PINE A communicates with the application server through the application layer, and PINE A decides to switch the service to another PINE, where PINE A is already in the PIN.

[0244] Step 1. PINE A triggers a PIN service discovery request to the PEMC, which carries a list of services the PINE A wants to consume.

[0245] Step 2. Upon receiving the request, the PEMC performs an authorization check to verify whether PINE A has the authorization to perform the operation.

[0246] Step 3. Based on the PIN profile, the PEMC provides PINE A with a list of PINE endpoints and application client endpoints providing the requested service in a PIN Service Discovery Response. A PIN service can be represented by the service type provided by the PINE or the application client on the PINE. If the request fails, the PEMC shall provide a failure response indicating the reason for the failure.

[0247] Step 4. PINE A determines PINE B for service switching, as shown below:

[0248] PINE A maintains a service to the AS, and this service corresponds to a service type, such as music or streaming media. PINE A determines potential PINE B for service handover based on whether the PINE has the capability to carry the service, whether the PINE and PINE A have deployed the same application client, whether PINE A and PINE B are within the coverage of the same PEGC, or whether PINE A has a direct connection to the PEGC.

[0249] Step 4a. After determining PINE B for service switching, PINE A sends a PIN service switching negotiation request to PINE B. The request carries the PIN ID, requester ID, and service information (such as PIN service type and PIN service characteristics).

[0250] Step 4b. Upon receiving the request, PINE B decides whether to accept the PIN service handover negotiation request. If the request fails, PINE B shall issue a failure response to indicate the reason for the failure.

[0251] Through steps 4a and 4b, interaction between PINE A and PINE B is increased. If the service switching is not agreed to, a cause value is carried, indicating the reason for not agreeing to the service switching. Optionally, the cause value indicates at least one of the following: insufficient resources, operation not permitted, or authorization failure.

[0252] Step 5. Taking PINE B as an example, PINE switches the service to PINE B: PINE A switches the traffic directly to PINE B through direct communication or PEGC.

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

[0254] The first device receives a PIN service discovery request message sent by a fourth device;

[0255] The first device sends a PIN service discovery response message to the fourth device, where the PIN service discovery response message includes a first list, where the first list is a list of devices that meet a first condition;

[0256] The first condition includes at least one of the following:

[0257] having a direct connection with the fourth device;

[0258] having a first application client, the first application client comprising: an application client deployed by the fourth device or an application client corresponding to a switching service;

[0259] Support service switching.

[0260] In this implementation manner, the first device may be a PEMC, and the fourth device is a device that requests service switching.

[0261] The above-mentioned PIN service discovery request message can be used to request information about the service requested by the fourth device, such as information about the service to which the fourth device requests service switching.

[0262] The above-mentioned first list and the first list in the above-mentioned embodiment may be the same list, or the above-mentioned first list and the first list in the above-mentioned embodiment may be different lists. For example, the first list in the above-mentioned embodiment may be a list determined based on the PIN profile, the first list in this embodiment may be a list determined based on the above-mentioned first condition, or the first list in this embodiment may be a list determined based on the PIN profile and the above-mentioned first condition.

[0263] The above-mentioned first condition may be a condition defined by a protocol or configured on the network side, or a condition determined by the above-mentioned first device.

[0264] That the first application client includes the application client deployed by the fourth device can be understood as that the device in the first list and the fourth device can have the same application client.

[0265] The above-mentioned first application client includes the application client corresponding to the switching service, which can be understood as the device in the above-mentioned first list can deploy the application client corresponding to the switching service, wherein the application client corresponding to the switching service can be the application client corresponding to the service switched by the service switching, that is, the application client is used to process the service switched by the service switching.

[0266] In this embodiment, since the devices in the first list satisfy the first condition, the first list returned by the first device to the fourth device enables the fourth device to more reliably complete service switching, thereby improving PIN service performance. For example, the fourth device can directly perform service switching for the devices in the first list.

[0267] Optionally, the supporting service switching includes:

[0268] Accept a second request message sent by the first device, where the second request message is used to negotiate service switching in the PIN.

[0269] For example, after determining devices that are directly connected to the fourth device or can deploy the first application client, the first device sends a second request message to these devices. After receiving the second request message, these devices reply to the first device with acceptance or rejection.

[0270] Optionally, the second request message includes at least one of the following:

[0271] PIN identification, identification information of the fourth device, the first information, and security credentials, where the security credentials are used for the authorization or authentication process of the service switching.

[0272] In this implementation, since the first request message includes the above-mentioned PIN identifier, the identification information of the fourth device, the first information, and at least one of the security credentials, this allows the devices in the first list to better determine whether to accept the first request message, thereby making service switching more reliable.

[0273] In some implementations, the above-mentioned consent service switching may also be pre-configured. For example, some devices may indicate the default consent switching to the first device in advance.

[0274] In one embodiment, before sending the list of PINE A services supported, the PEMC needs to interact with the candidate PINE B to determine whether PINE B supports service switching, as shown in FIG6 , including the following steps:

[0275] Step 0: PINE A communicates with the application server through the application layer, and PINE A decides to switch the service to another PINE, where PINE A is already in the PIN.

[0276] Step 1. PINE A triggers a PIN service discovery request to the PEMC, which carries a list of services the PINE A wants to consume.

[0277] Step 2. Upon receiving the request, the PEMC performs an authorization check to verify whether PINE A has the authorization to perform the operation.

[0278] Step 2a. The PEMC determines the list of PINE endpoints to which the service traffic from PINE A can be switched (i.e., the first list described above, e.g., including PINE B). The PEMC considers the following conditions to determine the list of PINE endpoints (using PINE B as an example): whether PINE A and PINE B have direct communication capabilities, and whether PINE A and PINE B deploy the same application client that can receive switched traffic.

[0279] In some embodiments, the PEMC sends a PIN management service switch negotiation request to the target PIN client to confirm whether the target PIN client accepts the service switch request. The PIN management service switch negotiation request message includes information such as the requester identifier, security credentials, service information, and PIN ID.

[0280] The PEMC sends a PIN management service switch negotiation request to all PINEs in the PINE endpoint list.

[0281] Step 2b. The target PIN client confirms whether it accepts the service switch and responds to the PEMC. If the request fails, PINE B should give a failure response to indicate the reason for the request failure.

[0282] Step 3. The PEMC provides a list of PINE endpoints and application client endpoints that are willing to provide the requested service to PINE A in the PIN Service Discovery Response. PIN services can be represented by the service type provided by the PINE or by the application client on the PINE. If the request fails, the PEMC shall provide a failure response indicating the reason for the failure.

[0283] Step 4. PINE A determines PINE B for service switching, as shown below:

[0284] PINE A maintains a service to the AS, and this service corresponds to a service type, such as music or streaming media. PINE A determines potential PINE B for service handover based on whether the PINE has the capability to carry the service, whether the PINE and PINE A have deployed the same application client, whether PINE A and PINE B are within the coverage of the same PEGC, or whether PINE A has a direct connection to the PEGC.

[0285] Step 5. Taking PINE B as an example, PINE switches service traffic to PINE B: PINE A directly switches the service flow to PINE B through direct communication or PEGC.

[0286] In some embodiments, step 5 where PINE A switches traffic flow to PINE B includes:

[0287] The application server sends the traffic flow to PINE A through the PEGC. Upon receiving the traffic flow from the specific application to PINE A, the PEGC directly forwards the traffic flow to PINE B. In this implementation, the data traffic sent by the specific application to PINE A is directly sent to PINE B through the PEGC. PINE A no longer receives traffic from the specific application, thus achieving service switching from PINE A to PINE B.

[0288] In an embodiment of the present application, during a PIN creation process or a PIN registration process, a first device performs a first operation; wherein the first operation includes at least one of the following: receiving a first message from a PIN server, the first message including first information; sending a second message to the PIN server, the second message including the first information; wherein the first information includes at least one of the following: PIN service information; service information of the first device; or PIN description information. Because the first device performs the first operation during the PIN creation process or the PIN registration process, synchronization of PIN-related information during the PIN creation process or the PIN registration process can be achieved through at least one of the first and second messages, thereby avoiding the problem of PIN service performance being affected by failure to synchronize PIN-related information in a timely manner, thereby improving PIN service performance.

[0289] Please refer to FIG7 , which is a flowchart of another information synchronization method provided by an embodiment of the present application. As shown in FIG7 , the method includes the following steps:

[0290] Step 701: During the PIN creation process or the PIN registration process, the PIN server performs a second operation.

[0291] The second operation includes at least one of the following:

[0292] Sending a first message to a first device, where the first message includes first information;

[0293] receiving a second message from the first device, where the second message includes the first information;

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

[0295] PIN service information;

[0296] service information of the first device;

[0297] PIN description information.

[0298] Optionally, sending the first message to the first device includes:

[0299] A PIN creation response message is sent to the first device, where the PIN creation response message includes the first information.

[0300] Optionally, the PIN creation response message carries a PIN configuration file, and the PIN configuration file includes the first information.

[0301] Optionally, the method further includes:

[0302] The PIN server obtains the first information through an application layer message or contract information.

[0303] Optionally, the receiving a second message from the first device includes:

[0304] A PIN creation request message is received from a first device, where the PIN creation request message includes the first information.

[0305] Optionally, the receiving a second message from the first device includes:

[0306] A PIN registration request message is received from a first device, where the PIN registration request message includes the first information.

[0307] Optionally, the PIN service information includes at least one of the following:

[0308] An identifier of a service provider of the service provided by the PIN;

[0309] The service type of the service provided by the PIN;

[0310] Service characteristics of the service provided by the PIN.

[0311] Optionally, the service information of the first device includes at least one of the following:

[0312] an identifier of a service provider of the service provided by the first device;

[0313] a service type of a service provided by the first device;

[0314] Service characteristics of the service provided by the first device.

[0315] It should be noted that this embodiment is an implementation of the PIN server corresponding to the embodiment shown in FIG2 . For its specific implementation, please refer to the relevant description of the embodiment shown in FIG2 . To avoid repeated description, this embodiment will not be described in detail.

[0316] Please refer to FIG8 , which is a flowchart of a service switching method provided in an embodiment of the present application. As shown in FIG8 , the method includes the following steps:

[0317] Step 801: A first device in a PIN sends a first request message to a second device, where the first request message is used to negotiate a service switching in the PIN.

[0318] Among them, the above-mentioned first device can be the first device in the embodiment shown in Figure 2. The specific implementation of this embodiment can be found in the embodiment shown in Figure 2, and will not be repeated here.

[0319] Optionally, the method further includes:

[0320] The first device receives a first response message from the second device, where the first response message is used to indicate acceptance or rejection of the first request message.

[0321] Optionally, the first request message includes at least one of the following:

[0322] PIN identification, identification information of the first device, and first information;

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

[0324] PIN service information;

[0325] service information of the first device;

[0326] PIN description information.

[0327] Optionally, when the first response message indicates rejection of the first request message, the first response message includes a cause value, where the cause value is used to indicate at least one of the following:

[0328] Insufficient resources, unable to perform corresponding service operations, authorization failed.

[0329] Optionally, the method further includes:

[0330] The first device determines the second device, where the second device satisfies at least one of the following:

[0331] The first device and the first device are within the coverage of the same PIN unit PEGC with gateway capability;

[0332] There is a direct connection with the first device.

[0333] Optionally, when the first response message indicates rejection of the first request message, the method further includes at least one of the following:

[0334] The first device determines a third device based on the first list;

[0335] terminating the PIN service switching process when there is no available third device in the first list;

[0336] The third device is used for service switching in the PIN, and the first list is a list of devices that support service switching in the PIN.

[0337] Optionally, the PIN service information includes at least one of the following:

[0338] An identifier of a service provider of the service provided by the PIN;

[0339] The service type of the service provided by the PIN;

[0340] Service characteristics of the service provided by the PIN.

[0341] Optionally, the service information of the first device includes at least one of the following:

[0342] an identifier of a service provider of the service provided by the first device;

[0343] a service type of a service provided by the first device;

[0344] Service characteristics of the service provided by the first device.

[0345] In this embodiment, the first request message can be used to negotiate with the second device before the service switching, thereby avoiding the problem of the inability to negotiate between devices before the service switching affecting the PIN service performance, thereby improving the PIN service performance.

[0346] It should be noted that this embodiment is an implementation of the first device corresponding to the embodiment shown in Figure 2. Its specific implementation can refer to the relevant description of the embodiment shown in Figure 2. In order to avoid repeated description, this embodiment will not be repeated.

[0347] Please refer to FIG9 , which is a flowchart of another service switching method provided in an embodiment of the present application. As shown in FIG9 , the method includes the following steps:

[0348] Step 901: A second device in a PIN receives a first request message from a first device, where the first request message is used to negotiate a service switching in the PIN.

[0349] Optionally, the method further includes:

[0350] The second device sends a first response message to the first device, where the first response message is used to indicate acceptance or rejection of the first request message.

[0351] Optionally, the first request message includes at least one of the following:

[0352] PIN identification, identification information of the first device, and first information;

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

[0354] PIN service information;

[0355] service information of the first device;

[0356] PIN description information.

[0357] Optionally, when the first response message indicates rejection of the first request message, the first response message includes a cause value, where the cause value is used to indicate at least one of the following:

[0358] Insufficient resources, unable to perform corresponding service operations, authorization failed.

[0359] Optionally, the PIN service information includes at least one of the following:

[0360] An identifier of a service provider of the service provided by the PIN;

[0361] The service type of the service provided by the PIN;

[0362] Service characteristics of the service provided by the PIN.

[0363] Optionally, the service information of the first device includes at least one of the following:

[0364] an identifier of a service provider of the service provided by the first device;

[0365] a service type of a service provided by the first device;

[0366] Service characteristics of the service provided by the first device.

[0367] It should be noted that this embodiment is an implementation of the second device corresponding to the embodiment shown in Figure 2. Its specific implementation can refer to the relevant description of the embodiment shown in Figure 2. In order to avoid repeated description, this embodiment will not be repeated.

[0368] Please refer to FIG10 , which is a flowchart of another service switching method provided in an embodiment of the present application. As shown in FIG10 , the method includes the following steps:

[0369] Step 1001: The first device receives a PIN service discovery request message sent by a fourth device;

[0370] Step 1002: The first device sends a PIN service discovery response message to the fourth device, where the PIN service discovery response message includes a first list.

[0371] The first list is a list of devices that support service switching in the PIN, and the first list is determined based on first information, and the first information includes at least one of the following:

[0372] PIN service information;

[0373] service information of the first device;

[0374] PIN description information;

[0375] Alternatively, the first list is a list of devices that meet the first condition;

[0376] The first condition includes at least one of the following:

[0377] having a direct connection with the fourth device;

[0378] having a first application client, the first application client comprising: an application client deployed by the fourth device or an application client corresponding to a switching service;

[0379] Support service switching.

[0380] Optionally, the supporting service switching includes:

[0381] Accept a second request message sent by the first device, where the second request message is used to negotiate service switching in the PIN.

[0382] Optionally, the second request message includes at least one of the following:

[0383] PIN identification, identification information of the fourth device, the first information, and security credentials, where the security credentials are used for the authorization or authentication process of the service switching.

[0384] Optionally, the PIN service information includes at least one of the following:

[0385] An identifier of a service provider of the service provided by the PIN;

[0386] The service type of the service provided by the PIN;

[0387] Service characteristics of the service provided by the PIN.

[0388] Optionally, the service information of the first device includes at least one of the following:

[0389] an identifier of a service provider of the service provided by the first device;

[0390] a service type of a service provided by the first device;

[0391] Service characteristics of the service provided by the first device.

[0392] It should be noted that this embodiment is an implementation of the first device corresponding to the embodiment shown in Figure 2. Its specific implementation can refer to the relevant description of the embodiment shown in Figure 2. In order to avoid repeated description, this embodiment will not be repeated.

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

[0394] The service switching method provided in the embodiment of the present application can be executed by a service switching device. In the embodiment of the present application, the service switching device provided in the embodiment of the present application is described by taking the service switching method executed by the service switching device as an example.

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

[0396] Please refer to FIG11 , which is a structural diagram of an information synchronization device provided in an embodiment of the present application. As shown in FIG11 , the information synchronization device 1100 includes:

[0397] An execution module 1101 is configured to execute a first operation during a personal IoT PIN creation process or a PIN registration process;

[0398] The first operation includes at least one of the following:

[0399] receiving a first message from a PIN server, wherein the first message includes first information;

[0400] sending a second message to the PIN server, where the second message includes the first information;

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

[0402] PIN service information;

[0403] service information of the first device;

[0404] PIN description information.

[0405] Optionally, the receiving a first message from the PIN server includes:

[0406] A PIN creation response message is received from a PIN server, where the PIN creation response message includes the first information.

[0407] Optionally, the PIN creation response message carries a PIN configuration file, and the PIN configuration file includes the first information.

[0408] Optionally, sending the second message to the PIN server includes:

[0409] A PIN creation request message is sent to a PIN server, where the PIN creation request message includes the first information.

[0410] Optionally, sending the second message to the PIN server includes:

[0411] A PIN registration request message is sent to a PIN server, where the PIN registration request message includes the first information.

[0412] Optionally, the PIN service information includes at least one of the following:

[0413] An identifier of a service provider of the service provided by the PIN;

[0414] The service type of the service provided by the PIN;

[0415] Service characteristics of the service provided by the PIN.

[0416] Optionally, the service information of the first device includes at least one of the following:

[0417] an identifier of a service provider of the service provided by the first device;

[0418] a service type of a service provided by the first device;

[0419] Service characteristics of the service provided by the first device.

[0420] Optionally, the device further comprises:

[0421] The first sending module is configured to send a first request message to the second device, where the first request message is used to negotiate service switching in the PIN.

[0422] Optionally, the method further includes:

[0423] The first receiving module is configured to receive a first response message from the second device, where the first response message is used to indicate acceptance or rejection of the first request message.

[0424] Optionally, the first request message includes at least one of the following:

[0425] PIN identification, identification information of the first device, and the first information.

[0426] Optionally, when the first response message indicates rejection of the first request message, the first response message includes a cause value, where the cause value is used to indicate at least one of the following:

[0427] Insufficient resources, unable to perform corresponding service operations, authorization failed.

[0428] Optionally, the device further comprises:

[0429] The first determining module is configured to determine the second device, where the second device satisfies at least one of the following conditions:

[0430] The first device and the first device are within the coverage of the same PIN unit PEGC with gateway capability;

[0431] There is a direct connection with the first device.

[0432] Optionally, when the first response message indicates rejection of the first request message, the apparatus further includes at least one of the following:

[0433] a second determining module, configured to determine a third device based on the first list;

[0434] a terminating module, configured to terminate the PIN service switching process when there is no available third device in the first list;

[0435] The third device is used for service switching in the PIN, and the first list is a list of devices that support service switching in the PIN.

[0436] Optionally, the device further comprises:

[0437] A second receiving module, configured to receive a PIN service discovery request message sent from a fourth device;

[0438] A response module, configured to respond to the PIN service discovery request message based on a PIN configuration file;

[0439] The PIN configuration file includes the first information.

[0440] Optionally, the device further comprises:

[0441] a fourth receiving module, configured to receive a PIN service discovery request message sent from a fourth device;

[0442] a second sending module, configured to send a PIN service discovery response message to the fourth device, where the PIN service discovery response message includes a first list, where the first list is a list of devices that meet a first condition;

[0443] The first condition includes at least one of the following:

[0444] having a direct connection with the fourth device;

[0445] having a first application client, the first application client comprising: an application client deployed by the fourth device or an application client corresponding to a switching service;

[0446] Support service switching.

[0447] Optionally, the supporting service switching includes:

[0448] Accept a second request message sent by the first device, where the second request message is used to negotiate service switching in the PIN.

[0449] Optionally, the second request message includes at least one of the following:

[0450] PIN identification, identification information of the fourth device, the first information, and security credentials, where the security credentials are used for the authorization or authentication process of the service switching.

[0451] The above information synchronization device can improve the PIN service performance.

[0452] In the embodiments of the present application, the information synchronization device may be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. For example, the electronic device may be a terminal, or may be a device other than a terminal. For example, the terminal may include but is not limited to the types of terminals listed in the embodiments of the present application, and the other devices may be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

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

[0454] Please refer to FIG. 12 , which is a structural diagram of another information synchronization device provided in an embodiment of the present application. As shown in FIG. 12 , the information synchronization device 1200 includes:

[0455] An execution module 1201 is configured to execute a second operation during a personal IoT PIN creation process or a PIN registration process;

[0456] The second operation includes at least one of the following:

[0457] Sending a first message to a first device, where the first message includes first information;

[0458] receiving a second message from the first device, where the second message includes the first information;

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

[0460] PIN service information;

[0461] service information of the first device;

[0462] PIN description information.

[0463] Optionally, sending the first message to the first device includes:

[0464] A PIN creation response message is sent to the first device, where the PIN creation response message includes the first information.

[0465] Optionally, the PIN creation response message carries a PIN configuration file, and the PIN configuration file includes the first information.

[0466] Optionally, the device further comprises:

[0467] The acquisition module is used to obtain the first information through an application layer message or contract information.

[0468] Optionally, the receiving a second message from the first device includes:

[0469] A PIN creation request message is received from a first device, where the PIN creation request message includes the first information.

[0470] Optionally, the receiving a second message from the first device includes:

[0471] A PIN registration request message is received from a first device, where the PIN registration request message includes the first information.

[0472] Optionally, the PIN service information includes at least one of the following:

[0473] An identifier of a service provider of the service provided by the PIN;

[0474] The service type of the service provided by the PIN;

[0475] Service characteristics of the service provided by the PIN.

[0476] Optionally, the service information of the first device includes at least one of the following:

[0477] an identifier of a service provider of the service provided by the first device;

[0478] a service type of a service provided by the first device;

[0479] Service characteristics of the service provided by the first device.

[0480] The above information synchronization device can improve the PIN service performance.

[0481] The information synchronization device in the embodiment of the present application can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or a chip. The electronic device can be a terminal or a network-side device.

[0482] The information synchronization device provided in the embodiment of the present application can implement the various processes implemented by the method embodiment shown in Figure 7 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0483] Please refer to FIG. 13 , which is a structural diagram of a service switching device provided in an embodiment of the present application. As shown in FIG. 13 , the service switching device 1300 includes:

[0484] The sending module 1301 is used to send a first request message to the second device, where the first request message is used to negotiate service switching in the PIN, and the device corresponding to the device is a device in the personal Internet of Things network PIN.

[0485] Optionally, the device further comprises:

[0486] The first receiving module is configured to receive a first response message from the second device, where the first response message is used to indicate acceptance or rejection of the first request message.

[0487] Optionally, the first request message includes at least one of the following:

[0488] PIN identification, identification information of the first device, and first information;

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

[0490] PIN service information;

[0491] service information of the first device;

[0492] PIN description information.

[0493] Optionally, when the first response message indicates rejection of the first request message, the first response message includes a cause value, where the cause value is used to indicate at least one of the following:

[0494] Insufficient resources, unable to perform corresponding service operations, authorization failed.

[0495] Optionally, the device further comprises:

[0496] The first determining module is configured to determine the second device, where the second device satisfies at least one of the following conditions:

[0497] The first device and the first device are within the coverage of the same PIN unit PEGC with gateway capability;

[0498] There is a direct connection with the first device.

[0499] Optionally, when the first response message indicates rejection of the first request message, the apparatus further includes at least one of the following:

[0500] A second module is configured to determine a third device based on the first list;

[0501] a terminating module, configured to terminate the PIN service switching process when there is no available third device in the first list;

[0502] The third device is used for service switching in the PIN, and the first list is a list of devices that support service switching in the PIN.

[0503] Optionally, the PIN service information includes at least one of the following:

[0504] An identifier of a service provider of the service provided by the PIN;

[0505] The service type of the service provided by the PIN;

[0506] Service characteristics of the service provided by the PIN.

[0507] Optionally, the service information of the first device includes at least one of the following:

[0508] an identifier of a service provider of the service provided by the first device;

[0509] a service type of a service provided by the first device;

[0510] Service characteristics of the service provided by the first device.

[0511] The above service switching device can improve the PIN service performance.

[0512] In the embodiments of the present application, the service switching device can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. For example, the electronic device can be a terminal, or it can be a device other than a terminal. For example, the terminal can include but is not limited to the types of terminals listed in the embodiments of the present application, and the other devices can be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0513] The service switching device provided in the embodiment of the present application can implement the various processes implemented by the method embodiment shown in Figure 8 and achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0514] Please refer to FIG. 14 , which is a structural diagram of another service switching device provided in an embodiment of the present application. As shown in FIG. 14 , the service switching device 1400 includes:

[0515] The receiving module 1401 is used to receive a first request message from a first device, where the first request message is used to negotiate service switching in a PIN, and the device corresponding to the apparatus is a device in a personal Internet of Things network PIN.

[0516] Optionally, the device further comprises:

[0517] A sending module is used to send a first response message to the first device, where the first response message is used to indicate acceptance or rejection of the first request message.

[0518] Optionally, the first request message includes at least one of the following:

[0519] PIN identification, identification information of the first device, and first information;

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

[0521] PIN service information;

[0522] service information of the first device;

[0523] PIN description information.

[0524] Optionally, when the first response message indicates rejection of the first request message, the first response message includes a cause value, where the cause value is used to indicate at least one of the following:

[0525] Insufficient resources, unable to perform corresponding service operations, authorization failed.

[0526] Optionally, the PIN service information includes at least one of the following:

[0527] An identifier of a service provider of the service provided by the PIN;

[0528] The service type of the service provided by the PIN;

[0529] Service characteristics of the service provided by the PIN.

[0530] Optionally, the service information of the first device includes at least one of the following:

[0531] an identifier of a service provider of the service provided by the first device;

[0532] a service type of a service provided by the first device;

[0533] Service characteristics of the service provided by the first device.

[0534] The above service switching device can improve the PIN service performance.

[0535] In the embodiments of the present application, the service switching device can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. For example, the electronic device can be a terminal, or it can be a device other than a terminal. For example, the terminal can include but is not limited to the types of terminals listed in the embodiments of the present application, and the other devices can be servers, NAS, etc., which are not specifically limited in the embodiments of the present application.

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

[0537] Please refer to FIG. 15 , which is a structural diagram of a request processing device provided in an embodiment of the present application. As shown in FIG. 15 , the request processing device 1500 includes:

[0538] The receiving module 1501 is configured to receive a personal Internet of Things network PIN service discovery request message sent by a fourth device;

[0539] A sending module 1502 is configured to send a PIN service discovery response message to the fourth device, where the PIN service discovery response message includes the first list;

[0540] The first list is a list of devices that support service switching in the PIN, and the first list is determined based on first information, and the first information includes at least one of the following:

[0541] PIN service information;

[0542] service information of the first device;

[0543] PIN description information;

[0544] Alternatively, the first list is a list of devices that meet the first condition;

[0545] The first condition includes at least one of the following:

[0546] having a direct connection with the fourth device;

[0547] having a first application client, the first application client comprising: an application client deployed by the fourth device or an application client corresponding to a switching service;

[0548] Support service switching.

[0549] Optionally, the supporting service switching includes:

[0550] Accept a second request message sent by the first device, where the second request message is used to negotiate service switching in the PIN.

[0551] Optionally, the second request message includes at least one of the following:

[0552] PIN identification, identification information of the fourth device, the first information, and security credentials, where the security credentials are used for the authorization or authentication process of the service switching.

[0553] Optionally, the PIN service information includes at least one of the following:

[0554] An identifier of a service provider of the service provided by the PIN;

[0555] The service type of the service provided by the PIN;

[0556] Service characteristics of the service provided by the PIN.

[0557] Optionally, the service information of the first device includes at least one of the following:

[0558] an identifier of a service provider of the service provided by the first device;

[0559] a service type of a service provided by the first device;

[0560] Service characteristics of the service provided by the first device.

[0561] The request processing device can improve the PIN service performance.

[0562] In the embodiments of the present application, the service switching device can be an electronic device, such as an electronic device with an operating system, or a component in an electronic device, such as an integrated circuit or chip. For example, the electronic device can be a terminal, or it can be a device other than a terminal. For example, the terminal can include but is not limited to the types of terminals listed in the embodiments of the present application, and the other devices can be servers, NAS, etc., which are not specifically limited in the embodiments of the present application.

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

[0564] As shown in Figure 16, an embodiment of the present application further provides a communication device 1600, including a processor 1601 and a memory 1602, wherein the memory 1602 stores programs or instructions that can be run on the processor 1601. For example, when the communication device 1600 is a first device, the program or instruction is executed by the processor 1601 to implement the various steps of the above-mentioned information synchronization method, service switching method, or request processing method embodiment, and can achieve the same technical effect. When the communication device 1600 is a PIN server, the program or instruction is executed by the processor 1601 to implement the various steps of the above-mentioned information synchronization method embodiment, and can achieve the same technical effect. When the communication device 1600 is a second device, the program or instruction is executed by the processor 1601 to implement the various steps of the above-mentioned service switching method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0565] An embodiment of the present application further provides a device including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps in the information synchronization method embodiment shown in FIG2 , or the steps in the service switching method embodiment shown in FIG8 or 9 , or the steps in the request processing method embodiment shown in FIG10 . This terminal embodiment corresponds to the first device-side method embodiment described above, and each implementation process and implementation method of the above method embodiment can be applied to this first embodiment and can achieve the same technical effects.

[0566] Specifically, Figure 17 is a schematic diagram of the hardware structure of a device for implementing an embodiment of the present application, which is a first device or a second device.

[0567] The device 1700 includes but is not limited to: a radio frequency unit 1701, a network module 1702, an audio output unit 1703, an input unit 1704, a sensor 1705, a display unit 1706, a user input unit 1707, an interface unit 1708, a memory 1709 and at least some of the components of the processor 1710.

[0568] Those skilled in the art will appreciate that device 1700 may also include a power source (such as a battery) to power various components. The power source may be logically connected to processor 1710 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The device structure shown in FIG17 does not limit the device. The device may include more or fewer components than shown, or may combine certain components or arrange the components differently, which will not be described in detail here.

[0569] It should be understood that in an embodiment of the present application, the input unit 1704 may include a graphics processing unit (GPU) 17041 and a microphone 17042, and the graphics processor 17041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The display unit 1706 may include a display panel 17061, and the display panel 17061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1707 includes a touch panel 17071 and at least one of other input devices 17072. The touch panel 17071 is also called a touch screen. The touch panel 17071 may include two parts: a touch detection device and a touch controller. Other input devices 17072 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.

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

[0571] Memory 1709 can be used to store software programs or instructions and various data. Memory 1709 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store an operating system, applications or instructions required for at least one function (such as a sound playback function, an image playback function, etc.). In addition, memory 1709 may include volatile memory or non-volatile memory. 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. Volatile memory can be random access memory (RAM), static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 1709 in the embodiment of the present application includes but is not limited to these and any other suitable types of memory.

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

[0573] It should be noted that this embodiment mainly takes the first device as a conventional communication terminal as an example, and the embodiment of the present application does not limit the specific structure of the first device.

[0574] In an embodiment where the above device is the first device:

[0575] The radio frequency unit 1701 is configured to perform a first operation during a PIN creation process or a PIN registration process;

[0576] The first operation includes at least one of the following:

[0577] receiving a first message from a PIN server, wherein the first message includes first information;

[0578] sending a second message to the PIN server, where the second message includes the first information;

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

[0580] PIN service information;

[0581] service information of the first device;

[0582] PIN description information.

[0583] Optionally, the receiving a first message from the PIN server includes:

[0584] A PIN creation response message is received from a PIN server, where the PIN creation response message includes the first information.

[0585] Optionally, the PIN creation response message carries a PIN configuration file, and the PIN configuration file includes the first information.

[0586] Optionally, sending the second message to the PIN server includes:

[0587] A PIN creation request message is sent to a PIN server, where the PIN creation request message includes the first information.

[0588] Optionally, sending the second message to the PIN server includes:

[0589] A PIN registration request message is sent to a PIN server, where the PIN registration request message includes the first information.

[0590] Optionally, the PIN service information includes at least one of the following:

[0591] An identifier of a service provider of the service provided by the PIN;

[0592] The service type of the service provided by the PIN;

[0593] Service characteristics of the service provided by the PIN.

[0594] Optionally, the service information of the first device includes at least one of the following:

[0595] an identifier of a service provider of the service provided by the first device;

[0596] a service type of a service provided by the first device;

[0597] Service characteristics of the service provided by the first device.

[0598] Optionally, the radio frequency unit 1701 is further configured to:

[0599] A first request message is sent to the second device, where the first request message is used to negotiate a service switch in the PIN.

[0600] Optionally, the radio frequency unit 1701 is further configured to:

[0601] A first response message is received from the second device, where the first response message is used to indicate acceptance or rejection of the first request message.

[0602] Optionally, the first request message includes at least one of the following:

[0603] PIN identification, identification information of the first device, and the first information.

[0604] Optionally, when the first response message indicates rejection of the first request message, the first response message includes a cause value, where the cause value is used to indicate at least one of the following:

[0605] Insufficient resources, unable to perform corresponding service operations, authorization failed.

[0606] Optionally, the processor 1710 is configured to:

[0607] Determine the second device, where the second device satisfies at least one of the following:

[0608] The first device and the first device are within the coverage of the same PIN unit PEGC with gateway capability;

[0609] There is a direct connection with the first device.

[0610] Optionally, when the first response message indicates rejection of the first request message, the processor 1710 is further configured to perform at least one of the following:

[0611] determining a third device based on the first list;

[0612] terminating the PIN service switching process when there is no available third device in the first list;

[0613] The third device is used for service switching in the PIN, and the first list is a list of devices that support service switching in the PIN.

[0614] Optionally, the radio frequency unit 1701 is further configured to:

[0615] receiving a PIN service discovery request message sent by a fourth device;

[0616] Responding to the PIN service discovery request message based on the PIN profile;

[0617] The PIN configuration file includes the first information.

[0618] Optionally, the radio frequency unit 1701 is further configured to:

[0619] receiving a PIN service discovery request message sent by a fourth device;

[0620] Sending a PIN service discovery response message to the fourth device, where the PIN service discovery response message includes a first list, where the first list is a list of devices that meet a first condition;

[0621] The first condition includes at least one of the following:

[0622] having a direct connection with the fourth device;

[0623] having a first application client, the first application client comprising: an application client deployed by the fourth device or an application client corresponding to a switching service;

[0624] Support service switching.

[0625] Optionally, the supporting service switching includes:

[0626] Accept a second request message sent by the first device, where the second request message is used to negotiate service switching in the PIN.

[0627] Optionally, the second request message includes at least one of the following:

[0628] PIN identification, identification information of the fourth device, the first information, and security credentials, where the security credentials are used for the authorization or authentication process of the service switching.

[0629] In an embodiment where the above device is the first device:

[0630] The radio frequency unit 1701 is configured to send a first request message to the second device, where the first request message is used to negotiate service switching in the PIN.

[0631] Optionally, the radio frequency unit 1701 is further configured to:

[0632] A first response message is received from the second device, where the first response message is used to indicate acceptance or rejection of the first request message.

[0633] Optionally, the first request message includes at least one of the following:

[0634] PIN identification, identification information of the first device, and first information;

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

[0636] PIN service information;

[0637] service information of the first device;

[0638] PIN description information.

[0639] Optionally, when the first response message indicates rejection of the first request message, the first response message includes a cause value, where the cause value is used to indicate at least one of the following:

[0640] Insufficient resources, unable to perform corresponding service operations, authorization failed.

[0641] Optionally, the processor 1710 is configured to:

[0642] Determine the second device, where the second device satisfies at least one of the following:

[0643] The first device and the first device are within the coverage of the same PIN unit PEGC with gateway capability;

[0644] There is a direct connection with the first device.

[0645] Optionally, when the first response message indicates rejection of the first request message, the processor 1710 is further configured to perform at least one of the following:

[0646] determining a third device based on the first list;

[0647] terminating the PIN service switching process when there is no available third device in the first list;

[0648] The third device is used for service switching in the PIN, and the first list is a list of devices that support service switching in the PIN.

[0649] Optionally, the PIN service information includes at least one of the following:

[0650] An identifier of a service provider of the service provided by the PIN;

[0651] The service type of the service provided by the PIN;

[0652] Service characteristics of the service provided by the PIN.

[0653] Optionally, the service information of the first device includes at least one of the following:

[0654] an identifier of a service provider of the service provided by the first device;

[0655] a service type of a service provided by the first device;

[0656] Service characteristics of the service provided by the first device.

[0657] In an embodiment where the above device is the second device:

[0658] The radio frequency unit 1701 is configured to receive a first request message from a first device, where the first request message is used to negotiate service switching in a PIN.

[0659] Optionally, the radio frequency unit 1701 is further configured to:

[0660] A first response message is sent to the first device, where the first response message is used to indicate acceptance or rejection of the first request message.

[0661] Optionally, the first request message includes at least one of the following:

[0662] PIN identification, identification information of the first device, and first information;

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

[0664] PIN service information;

[0665] service information of the first device;

[0666] PIN description information.

[0667] Optionally, when the first response message indicates rejection of the first request message, the first response message includes a cause value, where the cause value is used to indicate at least one of the following:

[0668] Insufficient resources, unable to perform corresponding service operations, authorization failed.

[0669] Optionally, the PIN service information includes at least one of the following:

[0670] An identifier of a service provider of the service provided by the PIN;

[0671] The service type of the service provided by the PIN;

[0672] Service characteristics of the service provided by the PIN.

[0673] Optionally, the service information of the first device includes at least one of the following:

[0674] an identifier of a service provider of the service provided by the first device;

[0675] a service type of a service provided by the first device;

[0676] Service characteristics of the service provided by the first device.

[0677] In an embodiment where the above device is the first device:

[0678] The radio frequency unit 1701 is configured to receive a personal Internet of Things network PIN service discovery request message sent by a fourth device;

[0679] The first device sends a PIN service discovery response message to the fourth device, where the PIN service discovery response message includes a first list;

[0680] The first list is a list of devices that support service switching in the PIN, and the first list is determined based on first information, and the first information includes at least one of the following:

[0681] PIN service information;

[0682] service information of the first device;

[0683] PIN description information;

[0684] Alternatively, the first list is a list of devices that meet the first condition;

[0685] The first condition includes at least one of the following:

[0686] having a direct connection with the fourth device;

[0687] having a first application client, the first application client comprising: an application client deployed by the fourth device or an application client corresponding to a switching service;

[0688] Support service switching.

[0689] Optionally, the supporting service switching includes:

[0690] Accept a second request message sent by the first device, where the second request message is used to negotiate service switching in the PIN.

[0691] Optionally, the second request message includes at least one of the following:

[0692] PIN identification, identification information of the fourth device, the first information, and security credentials, where the security credentials are used for the authorization or authentication process of the service switching.

[0693] Optionally, the PIN service information includes at least one of the following:

[0694] An identifier of a service provider of the service provided by the PIN;

[0695] The service type of the service provided by the PIN;

[0696] Service characteristics of the service provided by the PIN.

[0697] Optionally, the service information of the first device includes at least one of the following:

[0698] an identifier of a service provider of the service provided by the first device;

[0699] a service type of a service provided by the first device;

[0700] Service characteristics of the service provided by the first device.

[0701] The above devices can improve the performance of PIN services.

[0702] It can be understood that the implementation process of each implementation method mentioned in this embodiment can refer to the relevant description of the above-mentioned information synchronization method or service switching method embodiment, and achieve the same or corresponding technical effects. To avoid repetition, it will not be repeated here.

[0703] This embodiment of the present application also provides a device including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is configured to execute a program or instruction to implement the steps of the information synchronization method embodiment shown in FIG7 . This device embodiment corresponds to the aforementioned PIN server-side method embodiment, and each implementation process and implementation method of the aforementioned method embodiment is applicable to this network-side device embodiment and can achieve the same technical effects.

[0704] Specifically, an embodiment of the present application further provides a device. As shown in FIG18 , the network-side device 1800 includes a processor 1801, a network interface 1802, and a memory 1803. The network interface 1802 is, for example, a common public radio interface (CPRI).

[0705] Specifically, the device 1800 of the embodiment of the present application also includes: instructions or programs stored in the memory 1803 and executable on the processor 1801. The processor 1801 calls the instructions or programs in the memory 1803 to execute the methods executed by the modules shown in FIG10 and achieve the same technical effect. To avoid repetition, they will not be elaborated here.

[0706] The network interface 1802 is used to perform a second operation during the PIN creation process or the PIN registration process;

[0707] The second operation includes at least one of the following:

[0708] Sending a first message to a first device, where the first message includes first information;

[0709] receiving a second message from the first device, where the second message includes the first information;

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

[0711] PIN service information;

[0712] service information of the first device;

[0713] PIN description information.

[0714] Optionally, sending the first message to the first device includes:

[0715] A PIN creation response message is sent to the first device, where the PIN creation response message includes the first information.

[0716] Optionally, the PIN creation response message carries a PIN configuration file, and the PIN configuration file includes the first information.

[0717] Optionally, the processor 1801 is further configured to:

[0718] The first information is obtained through application layer messages or contract information.

[0719] Optionally, the receiving a second message from the first device includes:

[0720] A PIN creation request message is received from a first device, where the PIN creation request message includes the first information.

[0721] Optionally, the receiving a second message from the first device includes:

[0722] A PIN registration request message is received from a first device, where the PIN registration request message includes the first information.

[0723] Optionally, the PIN service information includes at least one of the following:

[0724] An identifier of a service provider of the service provided by the PIN;

[0725] The service type of the service provided by the PIN;

[0726] Service characteristics of the service provided by the PIN.

[0727] Optionally, the service information of the first device includes at least one of the following:

[0728] an identifier of a service provider of the service provided by the first device;

[0729] a service type of a service provided by the first device;

[0730] Service characteristics of the service provided by the first device.

[0731] The above devices can improve the performance of PIN services.

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

[0733] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the above-mentioned information synchronization method or service switching method or request processing method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

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

[0735] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned information synchronization method or service switching method or request processing method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

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

[0737] An embodiment of the present application further provides a computer program / program product, which is stored in a storage medium. The computer program / program product is executed by at least one processor to implement the various processes of the above-mentioned information synchronization method, service switching method, or request processing method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0738] An embodiment of the present application further provides a wireless communication system, including: a first device and a PIN server, wherein the first device can be used to execute the steps of the information synchronization method on the first device side provided in the embodiment of the present application, and the PIN server can be used to execute the steps of the information synchronization method on the PIN server side provided in the embodiment of the present application.

[0739] An embodiment of the present application further provides a wireless communication system, including: a first device and a second device, wherein the first device can be used to execute the steps of the service switching method on the first device side provided in the embodiment of the present application, or the first device can be used to execute the steps of the request processing method provided in the embodiment of the present application, and the second device can be used to execute the steps of the service switching method on the second device side provided in the embodiment of the present application.

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

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

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

Claims

1. An information synchronization method, comprising: During a personal IoT PIN creation process or a PIN registration process, a first device performs a first operation; The first operation includes at least one of the following: receiving a first message from a PIN server, wherein the first message includes first information; Sending a second message to a PIN server, wherein the second message includes the first information; The first information includes at least one of the following: PIN service information; service information of the first device; PIN description information.

2. The method of claim 1, wherein: The receiving a first message from the PIN server comprises: A PIN creation response message is received from a PIN server, wherein the PIN creation response message includes the first information.

3. The method of claim 2, wherein: The PIN creation response message carries a PIN configuration file, and the PIN configuration file includes the first information.

4. The method according to any one of claims 1 to 3, wherein: The sending a second message to the PIN server comprises: A PIN creation request message is sent to a PIN server, where the PIN creation request message includes the first information.

5. The method according to any one of claims 1 to 3, wherein: The sending a second message to the PIN server comprises: A PIN registration request message is sent to a PIN server, where the PIN registration request message includes the first information.

6. The method according to any one of claims 1 to 5, wherein: The PIN service information includes at least one of the following: An identifier of a service provider of the service provided by the PIN; The service type of the service provided by the PIN; Service characteristics of the service provided by the PIN.

7. The method according to any one of claims 1 to 6, wherein: The service information of the first device includes at least one of the following: an identifier of a service provider of the service provided by the first device; a service type of a service provided by the first device; Service characteristics of the service provided by the first device.

8. The method according to any one of claims 1 to 7, further comprising: The first device sends a first request message to the second device, wherein the first request message is used to negotiate the service in the PIN Service switching.

9. The method of claim 8, further comprising: The first device receives a first response message from the second device, where the first response message is used to indicate acceptance or rejection of the first request message.

10. The method according to claim 8 or 9, wherein: The first request message includes at least one of the following: PIN identification, identification information of the first device, and the first information.

11. The method according to claim 9 or 10, wherein: In the case where the first response message indicates rejection of the first request message, the first response message includes a cause value, where the cause value is used to indicate at least one of the following: Insufficient resources, unable to perform corresponding service operations, authorization failed.

12. The method according to any one of claims 8 to 11, further comprising: The first device determines the second device, where the second device satisfies at least one of the following: The first device is within the coverage of the same PIN unit PEGC with gateway capability; A direct connection is provided with the first device.

13. The method according to any one of claims 9 to 12, wherein: In the case where the first response message indicates rejection of the first request message, the method further includes at least one of the following: The first device determines a third device based on the first list; The first device terminates the PIN service switching process when there is no available third device in the first list; The third device is used for service switching in the PIN, and the first list is a list of devices supporting service switching in the PIN.

14. The method according to any one of claims 1 to 13, further comprising: The first device receives a PIN service discovery request message sent by a fourth device; The first device responds to the PIN service discovery request message based on the PIN profile; The PIN configuration file includes the first information.

15. The method of any one of claims 1 to 13, further comprising: The first device receives a PIN service discovery request message sent by a fourth device; The first device sends a PIN service discovery response message to the fourth device, where the PIN service discovery response message includes a first list, where the first list is a list of devices that meet a first condition; The first condition includes at least one of the following: having a direct connection with the fourth device; There is a first application client, the first application client comprising: an application client deployed by the fourth device or an application client corresponding to the switching service; Support service switching.

16. The method of claim 15, wherein: The support service switching includes: Accept a second request message sent by the first device, where the second request message is used to negotiate service switching in the PIN.

17. The method of claim 16, wherein: The second request message includes at least one of the following: PIN identification, identification information of the fourth device, the first information, and security credentials, where the security credentials are used for the authorization or authentication process of the service switching.

18. An information synchronization method, comprising: During the personal IoT PIN creation process or the PIN registration process, the PIN server performs a second operation; The second operation includes at least one of the following: Sending a first message to a first device, where the first message includes first information; receiving a second message from a first device, wherein the second message includes the first information; The first information includes at least one of the following: PIN service information; service information of the first device; PIN description information.

19. The method of claim 18, wherein: The sending a first message to the first device includes: A PIN creation response message is sent to the first device, where the PIN creation response message includes the first information.

20. The method of claim 19, wherein: The PIN creation response message carries a PIN configuration file, and the PIN configuration file includes the first information.

21. The method of any one of claims 18 to 20, further comprising: The PIN server obtains the first information through an application layer message or contract information.

22. The method of any one of claims 18 to 20, wherein: The receiving a second message from the first device comprises: A PIN creation request message is received from a first device, where the PIN creation request message includes the first information.

23. The method of any one of claims 18 to 20, wherein: The receiving a second message from the first device comprises: A PIN registration request message is received from a first device, where the PIN registration request message includes the first information.

24. The method of any one of claims 18 to 23, wherein: The PIN service information includes at least one of the following: An identifier of a service provider of the service provided by the PIN; The service type of the service provided by the PIN; Service characteristics of the service provided by the PIN.

25. The method of any one of claims 18 to 24, wherein: The service information of the first device includes at least one of the following: an identifier of a service provider of the service provided by the first device; a service type of a service provided by the first device; Service characteristics of the service provided by the first device.

26. A service switching method, comprising: A first device in a personal Internet of Things network PIN sends a first request message to a second device, where the first request message is used to negotiate a service switch in the PIN.

27. The method of claim 26, further comprising: The first device receives a first response message from the second device, where the first response message is used to indicate acceptance or rejection of the first request message.

28. The method of claim 26 or 27, wherein: The first request message includes at least one of the following: PIN identification, identification information of the first device, and first information; The first information includes at least one of the following: PIN service information; service information of the first device; PIN description information.

29. The method of claim 26 or 27, wherein: In the case where the first response message indicates rejection of the first request message, the first response message includes a cause value, where the cause value is used to indicate at least one of the following: Insufficient resources, unable to perform corresponding service operations, authorization failed.

30. The method of any one of claims 26 to 29, further comprising: The first device determines the second device, where the second device satisfies at least one of the following: The first device is within the coverage of the same PIN unit PEGC with gateway capability; A direct connection is provided with the first device.

31. The method of any one of claims 26 to 30, wherein: In the case where the first response message indicates rejection of the first request message, the method further includes at least one of the following: The first device determines a third device based on the first list; terminating the PIN service switching process when there is no available third device in the first list; The third device is used for service switching in the PIN, and the first list is a list of devices supporting service switching in the PIN.

32. The method of any one of claims 27 to 31, wherein: The PIN service information includes at least one of the following: An identifier of a service provider of the service provided by the PIN; The service type of the service provided by the PIN; Service characteristics of the service provided by the PIN.

33. The method of any one of claims 28 to 32, wherein: The service information of the first device includes at least one of the following: an identifier of a service provider of the service provided by the first device; a service type of a service provided by the first device; Service characteristics of the service provided by the first device.

34. A service switching method, comprising: A second device in a personal Internet of Things network PIN receives a first request message from a first device, where the first request message is used to negotiate a service switching in the PIN.

35. The method of claim 34, further comprising: The second device sends a first response message to the first device, where the first response message is used to indicate acceptance or rejection of the first request message.

36. The method of claim 34 or 35, wherein: The first request message includes at least one of the following: PIN identification, identification information of the first device, and first information; The first information includes at least one of the following: PIN service information; service information of the first device; PIN description information.

37. The method of claim 35 or 36, wherein: In the case where the first response message indicates rejection of the first request message, the first response message includes a cause value, where the cause value is used to indicate at least one of the following: Insufficient resources, unable to perform corresponding service operations, authorization failed.

38. The method of claim 36 or 37, wherein: The PIN service information includes at least one of the following: An identifier of a service provider of the service provided by the PIN; The service type of the service provided by the PIN; Service characteristics of the service provided by the PIN.

39. The method of any one of claims 36 to 38, wherein: The service information of the first device includes at least one of the following: an identifier of a service provider of the service provided by the first device; a service type of a service provided by the first device; Service characteristics of the service provided by the first device.

40. A request processing method, comprising: The first device receives a personal Internet of Things network PIN service discovery request message sent by a fourth device; The first device sends a PIN service discovery response message to the fourth device, where the PIN service discovery response message includes a first list; The first list is a list of devices supporting service switching in the PIN, and the first list is determined based on first information, and the first information includes at least one of the following: PIN service information; service information of the first device; PIN description information; Alternatively, the first list is a list of devices that meet the first condition; The first condition includes at least one of the following: having a direct connection with the fourth device; There is a first application client, the first application client comprising: an application client deployed by the fourth device or an application client corresponding to the switching service; Support service switching.

41. The method of claim 40, wherein: The support service switching includes: Accept a second request message sent by the first device, where the second request message is used to negotiate service switching in the PIN.

42. The method of claim 41, wherein: The second request message includes at least one of the following: PIN identification, identification information of the fourth device, the first information, and security credentials, where the security credentials are used for the authorization or authentication process of the service switching.

43. The method of any one of claims 40 to 42, wherein: The PIN service information includes at least one of the following: An identifier of a service provider of the service provided by the PIN; The service type of the service provided by the PIN; Service characteristics of the service provided by the PIN.

44. The method of any one of claims 40 to 43, wherein: The service information of the first device includes at least one of the following: an identifier of a service provider of the service provided by the first device; a service type of a service provided by the first device; Service characteristics of the service provided by the first device.

45. An information synchronization device, comprising: An execution module, configured to execute a first operation during a personal IoT PIN creation process or a PIN registration process; The first operation includes at least one of the following: receiving a first message from a PIN server, wherein the first message includes first information; Sending a second message to a PIN server, wherein the second message includes the first information; The first information includes at least one of the following: PIN service information; service information of the first device; PIN description information.

46. ​​An information synchronization device, comprising: An execution module, used for executing a second operation during a personal IoT PIN creation process or a PIN registration process; The second operation includes at least one of the following: Sending a first message to a first device, where the first message includes first information; receiving a second message from a first device, wherein the second message includes the first information; The first information includes at least one of the following: PIN service information; service information of the first device; PIN description information.

47. A service switching device, comprising: A sending module is used to send a first request message to a second device, where the first request message is used to negotiate a service switch in a PIN, and the device corresponding to the device is a device in a personal Internet of Things network PIN.

48. A service switching device, comprising: The receiving module is used to receive a first request message from a first device, where the first request message is used to negotiate a service switch in a PIN, and the device corresponding to the apparatus is a device in a personal Internet of Things network PIN.

49. A request processing device, comprising: A receiving module, used to receive a personal Internet of Things network PIN service discovery request message sent by a fourth device; A sending module, configured to send a PIN service discovery response message to the fourth device, wherein the PIN service discovery response message includes a first list; The first list is a list of devices supporting service switching in the PIN, and the first list is determined based on first information, and the first information includes at least one of the following: PIN service information; service information of the first device; PIN description information; Alternatively, the first list is a list of devices that meet the first condition; The first condition includes at least one of the following: having a direct connection with the fourth device; There is a first application client, the first application client comprising: an application client deployed by the fourth device or an application client corresponding to the switching service; Support service switching.

50. A device, comprising a processor and a memory, the memory storing a program or instruction that can be run on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the information synchronization method as described in any one of claims 1 to 17, or the program or instruction, when executed by the processor, implements the steps of the information synchronization method as described in any one of claims 18 to 25, or the program or instruction, when executed by the processor, implements the steps of the service switching method as described in any one of claims 26 to 33, or the program or instruction, when executed by the processor, implements the steps of the service switching method as described in any one of claims 34 to 39, or the program or instruction, when executed by the processor, implements the steps of the request processing method as described in any one of claims 40 to 44.

Images