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

Abstract

The invention discloses an information synchronization method, a service switching method, a request processing method and equipment, and belongs to the technical field of communication, and the information synchronization method in the embodiment of the invention comprises the following steps: in a PIN creation process or a PIN registration process, first equipment executes a first operation; wherein the first operation comprises at least one of the following items: receiving a first message from a PIN server, the first message comprising first information; sending a second message to a PIN server, wherein the second message comprises the first information; wherein the first information comprises at least one of the following items: PIN service information; service information of the first device; the PIN describes information.

Description

Technical Field

[0001] 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

[0002] In a communication system supporting a personal IoT network (PIN), a PIN may include one or more personal IoT network elements (PINEs), which may be Internet of Things (IoT) devices or terminals with communication capabilities, etc. In the related art, there is a situation where relevant information of the PIN cannot be synchronized in time or negotiation between devices cannot be performed before service switching, which results in poor PIN service performance. Summary of the invention

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

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

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

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

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

[0008] Sending a second message to a PIN server, wherein the second message includes the first information;

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

[0010] PIN service information;

[0011] service information of the first device;

[0012] PIN description information.

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

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

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

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

[0017] receiving a second message from a first device, wherein the second message includes the first information;

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

[0019] PIN service information;

[0020] service information of the first device;

[0021] PIN description information.

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

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

[0024] In a fourth aspect, a service switching method is provided, including:

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

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

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

[0028] 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;

[0029] 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:

[0030] PIN service information;

[0031] service information of the first device;

[0032] PIN description information;

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

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

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

[0036] 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;

[0037] Support service switching.

[0038] In a sixth aspect, an information synchronization device is provided, including:

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

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

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

[0042] Sending a second message to a PIN server, wherein the second message includes the first information;

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

[0044] PIN service information;

[0045] service information of the first device;

[0046] PIN description information.

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

[0048] An execution module, used for executing a second operation during a personal IoT PIN creation process or a PIN registration process;

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

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

[0051] receiving a second message from a first device, wherein the second message includes the first information;

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

[0053] PIN service information;

[0054] service information of the first device;

[0055] PIN description information.

[0056] In an eighth aspect, a service switching device is provided, including:

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

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

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

[0060] In a ninth aspect, a request processing device is provided, characterized in that it includes:

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

[0062] 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;

[0063] 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:

[0064] PIN service information;

[0065] service information of the first device;

[0066] PIN description information;

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

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

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

[0070] 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;

[0071] Support service switching.

[0072] 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, and the program or instruction, when executed by the processor, implements the steps of the information synchronization method on the first device side provided in the embodiment of the present application, or the program or instruction, when executed by the processor, implements the steps of the information synchronization method on the PIN server side provided in the embodiment of the present application, or the program or instruction, when executed by the processor, implements the steps of the service switching method on the first device side provided in the embodiment of the present application, or the program or instruction, when executed by the processor, implements the steps of the service switching method on the second device side provided in the embodiment of the present application, or the program or instruction, when executed by the processor, implements the steps of the request processing method provided in the embodiment of the present application.

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

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

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

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

[0077] 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 a switching service; supporting service switching.

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

[0079] In the eighteenth aspect, 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.

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

[0081] In the twentieth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or 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 as provided in the embodiment of the present application.

[0082] In the twenty-first aspect, a computer program / program product is provided, wherein the computer program / program product is stored in a storage medium, and the program / program product is executed by at least one processor to implement the steps of the information synchronization method on the first device side as provided in the embodiment of the present application, or the 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 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 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 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.

[0083] 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 a 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. Since the first device performs the first operation during a PIN creation process or a PIN registration process, synchronization of PIN-related information can be achieved during a PIN creation process or a PIN registration process through at least one of the first message and the second message, so as to avoid the problem that the PIN-related information cannot be synchronized in time and affects the PIN service performance, thereby improving the PIN service performance. BRIEF DESCRIPTION OF THE DRAWINGS

[0084] Figure 1 is a block diagram of a wireless communication system to which the embodiments of the present application can be applied;

[0085] Figure 2 is a flow chart of an information synchronization method provided by an embodiment of the present application;

[0086] Figure 3It is a schematic diagram of information synchronization provided by an embodiment of the present application;

[0087] Figure 4 is a schematic diagram of another information synchronization provided by an embodiment of the present application;

[0088] Figure 5 is a schematic diagram of another information synchronization provided by an embodiment of the present application;

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

[0090] Figure 7 is a flow chart of another information synchronization method provided by an embodiment of the present application;

[0091] Figure 8 is a flow chart of a service switching method provided in an embodiment of the present application;

[0092] Fig. 9 is a flow chart of another service switching method provided in an embodiment of the present application;

[0093] Fig.10 is a flowchart of a request processing method provided by an embodiment of the present application;

[0094] Fig.11 is a structural diagram of an information synchronization device provided in an embodiment of the present application;

[0095] Fig.12 is a structural diagram of another information synchronization device provided in an embodiment of the present application;

[0096] Fig.13 is a structural diagram of a service switching device provided in an embodiment of the present application;

[0097] Fig.14 is a structural diagram of another service switching device provided in an embodiment of the present application;

[0098] Fig.15 is a structural diagram of a request processing device provided in an embodiment of the present application;

[0099] Fig.16 is a structural diagram of a communication device provided in an embodiment of the present application;

[0100] Fig.17 is a structural diagram of a device provided in an embodiment of the present application;

[0101] Fig.18 It is a structural diagram of another device provided in an embodiment of the present application. DETAILED DESCRIPTION

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

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

[0104] The term "indication" in this application can be a direct indication (or explicit indication) or an indirect indication (or implicit indication). A direct indication can be understood as the sender explicitly informing the receiver of specific information, operations to be performed, or request results in the sent indication; an indirect indication can be understood as the receiver determining the corresponding information according to the indication sent by the sender, or making a judgment and determining the operation to be performed or the request result according to the judgment result.

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

[0106] Figure 1A block diagram of a wireless communication system applicable to an embodiment of the present application is shown. The wireless communication system includes a terminal 11 and a network side device 12. Among them, the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer), a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (Ultra-mobile Personal Computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), an augmented reality (Augmented Reality, AR), a virtual reality (Virtual Reality, VR) device, a robot, a wearable device (Wearable Device), an aircraft (flight vehicle), a vehicle-mounted device (Vehicle User Equipment, VUE), a ship-mounted device, a pedestrian terminal (Pedestrian User Equipment, PUE), an IoT device, a smart home (a home appliance with a wireless communication function, such as a refrigerator, a television, a washing machine, a printer or furniture, etc.), a game console, a personal computer (Personal Computer, PC), a teller machine or a self-service machine and other terminal side devices. Wearable devices include: smart watches, smart bracelets, smart headphones, smart glasses, smart jewelry (smart bracelets, smart bracelets, smart rings, smart necklaces, smart anklets, smart anklets, etc.), smart wristbands, smart clothing, etc. Among them, the vehicle-mounted device can also be called a vehicle-mounted terminal, a vehicle-mounted controller, a vehicle-mounted module, a vehicle-mounted component, a vehicle-mounted chip or a vehicle-mounted unit, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application.

[0107] 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, etc. Among them, the base station may be referred to as a Node B (NodeB, NB), an evolved Node B (Evolved Node B, eNB), a next generation Node B (the next generation Node B, gNB), a New Radio Node B (New Radio Node B, NR Node B), an access point, a Relay Base Station (RBS), a Serving Base Station (SBS), a Base Transceiver Station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a Basic Service Set (Basic Service Set, BSS), an Extended Service Set (Extended Service Set, ESS), a home Node B (home evolved Node B, HNB), a home evolved Node B (home evolved Node B), a Transmission Reception Point (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 embodiments of the present application, only the base station in the NR system is used as an example for introduction, and the specific type of the base station is not limited.

[0108] The core network equipment may include but is not limited to at least one of the following: core network node, core network function, mobility management entity (Mobility Management Entity, MME), access mobility management function (Access and Mobility Management Function, AMF), session management function (Session Management Function, SMF), user plane function (User Plane Function, UPF), policy control function (Policy Control Function, PCF), policy and charging rules function unit (Policy and Charging Rules Function, PCRF), edge application service discovery function (Edge Application Server Discovery Function, EASDF), unified data management (Unified Data Management, UDM), unified data storage (Unified Data Repository, UDR), home user server (Home Subscriber Server, HSS), centralized network configuration (CNC), network storage function (Network Repository Function, NRF), network exposure function (Network Exposure Function, NEF), local NEF (Local NEF, or L-NEF), binding support function (Binding Support Function, BSF), application function (Application Function, AF), etc. It should be noted that in the embodiments of the present application, only the core network device in the NR system is introduced as an example, and the specific type of the core network device is not limited.

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

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

[0111] The PIN includes a PIN element with management capability (PIN Element with Management Capability, PEMC) and a PIN element with gateway capability (PIN Element with Gateway Capability, PEGC).

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

[0113] See also Figure 2 , Figure 2 is a flow chart of an information synchronization method provided by an embodiment of the present application, such as Figure 2 As shown, the following steps are included:

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

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

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

[0117] Sending a second message to a PIN server, wherein the second message includes the first information;

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

[0119] PIN service information;

[0120] service information of the first device;

[0121] PIN description information.

[0122] 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, and specifically can be 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.

[0123] 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 the PIN registration process.

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

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

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

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

[0128] The above-mentioned PIN service information may be relevant information for describing the services provided by the PIN.

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

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

[0131] In the embodiment of the present application, the above steps can be used to implement the first operation performed by the first device during the PIN creation process or the PIN registration process, so that the synchronization of the relevant information of the PIN can be implemented during the PIN creation process or the PIN registration process through at least one of the above first message and the second message, so as to avoid the problem that the relevant information of the PIN cannot be synchronized in time and affects the PIN service performance, thereby improving the PIN service performance. For example: by implementing the synchronization of the relevant information of the PIN during the PIN creation process or the PIN registration process, it is possible to avoid the problem that the first device or the PIN server cannot obtain the services supported by the PIN in time, resulting in the limitation of the PIN service of the first device or the PIN server, and affecting the PIN service performance, and implementing the synchronization of the relevant information of the PIN during the PIN creation process or the PIN registration process, so that the first device or the server can obtain the services supported by the PIN in time, so that the first device or the PIN server can better provide services, thereby improving the PIN service performance.

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

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

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

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

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

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

[0138] The above service types may be game, video, audio, etc.

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

[0140] In this implementation, 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 helping to improve the PIN service performance.

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

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

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

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

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

[0146] In this implementation, 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 facilitating the improvement of PIN service performance.

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

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

[0149] The PIN creation response message may be a PIN creation response message replied by the PIN server after receiving the PIN creation request message sent by the first device.

[0150] For example, taking the first device as PINE1 (or PEMC), Figure 3 As shown, 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, and the PIN creation response message includes the above-mentioned first information.

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

[0152] It should be noted that, in some implementations, 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 message newly defined in the PIN creation process or the PIN registration process for synchronizing the first information.

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

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

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

[0156] Table 1:

[0157]

[0158] Among them, the above Table 1 is only an example to illustrate the PIN profile, and the embodiments of the present application do not limit the PIN profile.

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

[0160] Table 2:

[0161]

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

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

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

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

[0166] The PIN creation request message is a request message for requesting to create a PIN, for example, Figure 3 The PIN creation request message shown.

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

[0168] It should be noted that, in some implementations, the second message in the embodiments of the present application is not limited to the PIN creation request message. For example, the second message may also be a newly defined message for synchronizing the second information during the PIN creation process or the PIN registration process.

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

[0170] Table 3:

[0171]

[0172] Among them, the above Table 3 is only an example to illustrate 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 a PIN is created, the PIN server carries the PINprofile in the creation acceptance message, or the PEMC carries the service information in the creation request message, such as Figure 3 As shown, the following steps are included:

[0174] Step 1. 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 audios;

[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, and the PIN creation response message includes a PIN profile.

[0181] In some implementations, if the PEMC does not carry service information in step 1, the PIN server obtains the service information, and may obtain the service information through application layer messages, contracts, etc. The contract 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, what services it includes, etc. 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. The application layer message here means that the PEMC synchronizes the required parameters in the PIN profile (for example, 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 implementations, the PIN registration request message may be as follows: Figure 4 The PINE registration request message shown, for example: the first device is PINE1, such as Figure 4As shown, the first device sends a PINE registration request message to the PIN server, the request message carries the first information, the PIN server processes the request, and the PIN server sends a PINE registration response message to the first device.

[0186] In this implementation, the 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 the 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]

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

[0191] In one embodiment, when PINE registers with the PIN server, it carries service information, such as Figure 4 As shown, the following steps are included:

[0192] Step 1. PINE initiates a PIN registration (such as PINE registration) process to a PIN server, and carries service information in a PIN registration request message, wherein the PIN registration request message may be a PINE registration request (PINEregistration request) message carrying service information.

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

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

[0195] Service type, for example, games, videos, and audios;

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

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

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

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

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

[0201] The first request message may be a message 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.

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

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

[0204] Optionally, the method further includes:

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

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

[0207] The first response message can be used to implement 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.

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

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

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

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

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

[0213] 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:

[0214] Insufficient resources, unable to perform corresponding service operations, authorization failure.

[0215] The above-mentioned insufficient resources may indicate that the second device does not have sufficient resources to provide the switching service.

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

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

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

[0219] Optionally, the method further includes:

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

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

[0222] A direct connection is provided with the first device.

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

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

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

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

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

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

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

[0230] The fact that there is no available third device in the first list can 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.

[0231] The first device determines the third device based on the first list, which may be selecting the third device in the first list to send 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 refers to the corresponding description of the second device, which is not repeated here.

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

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

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

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

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

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

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

[0239] The PIN configuration file mentioned above is described in the above-mentioned implementation manner and will not be described in detail here.

[0240] Based on the PIN profile, responding to the PIN service discovery request message may be, based on the PIN profile, sending a PIN service discovery response message of the PIN service discovery request message to the fourth device. For example, determining the relevant information of the service requested by the PIN service discovery request message in the PIN profile, and returning a PIN service discovery response message including the relevant information to the fourth device. For example, returning the PINE information, application client information, etc. of the requested service to the fourth device.

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

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

[0243] 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. Figure 5 As shown, the following steps are included:

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

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

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

[0247] Step 3. Based on the PIN profile, the PEMC provides PINE A with a list of PINE endpoints and application client endpoint information that are providing the requested service in the 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 give a failure response to indicate the reason for the request failure.

[0248] Step 4. PINE A determines PINE B for service switching as follows:

[0249] PINE A maintains a service to the AS, and the service corresponds to a service type, such as music or streaming media. PINE A determines potential PINE B for service switching based on whether the PINE has the ability 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 with the PEGC.

[0250] 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).

[0251] 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 give a failure response to indicate the reason for the request failure.

[0252] Through steps 4a and 4b, the interaction between PINE A and PINE B is increased. In the case of disagreeing to perform service switching, a reason value is carried, and the reason value indicates the reason for disagreeing to perform service switching. Optionally, the reason value indicates at least one of the following: insufficient resources, operation not allowed, authorization failure.

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

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

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

[0256] 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;

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

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

[0259] 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;

[0260] Support service switching.

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

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

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

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

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

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

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

[0268] Optionally, the supporting service switching includes:

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

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

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

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

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

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

[0275] In one embodiment, before sending the list of supported PINEA service switching, PEMC needs to interact with candidate PINE B to determine whether PINE B supports service switching. Figure 6 As shown, the following steps are included:

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

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

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

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

[0280] In some implementations, 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 of the requester identifier, security credentials, service information, and PIN ID.

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

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

[0283] Step 3. The PEMC provides a list of PINE endpoints and application client endpoint information that accepts 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 the application client on the PINE. If the request fails, the PEMC shall give a failure response to indicate the reason for the request failure.

[0284] Step 4. PINE A determines PINE B for service switching as follows:

[0285] PINE A maintains a service to the AS, and the service corresponds to a service type, such as music or streaming media. PINE A determines potential PINE B for service switching based on whether the PINE has the ability 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 with the PEGC.

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

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

[0288] The application server sends the traffic flow to PINE A through PEGC. When PEGC receives the traffic flow from the specific application to PINEA, it directly sends 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 PEGC, and PINE A will no longer receive traffic from the specific application, thereby achieving service switching from PINE A to PINE B.

[0289] 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 a 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. Since the first device performs the first operation during a PIN creation process or a PIN registration process, synchronization of PIN-related information can be achieved during a PIN creation process or a PIN registration process through at least one of the first message and the second message, so as to avoid the problem that the PIN-related information cannot be synchronized in time and affects the PIN service performance, thereby improving the PIN service performance.

[0290] See also Figure 7 , Figure 7 is a flowchart of another information synchronization method provided by an embodiment of the present application, such as Figure 7 As shown, the following steps are included:

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

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

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

[0294] receiving a second message from a first device, wherein the second message includes the first information;

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

[0296] PIN service information;

[0297] service information of the first device;

[0298] PIN description information.

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

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

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

[0302] Optionally, the method further includes:

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

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

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

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

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

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

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

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

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

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

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

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

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

[0316] It should be noted that this embodiment is Figure 2 The implementation method of the corresponding PIN server in the embodiment shown in the figure can be found in the specific implementation method. Figure 2 To avoid repeated description, the related description of the embodiment shown in the present invention will not be repeated in detail.

[0317] See also Figure 8 , Figure 8 is a flow chart of a service switching method provided by an embodiment of the present application, such as Figure 8 As shown, the following steps are included:

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

[0319] The first device may be Figure 2 The first device in the embodiment shown, the specific implementation of this embodiment can be found in Figure 2 The embodiments shown are not described in detail here.

[0320] Optionally, the method further includes:

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

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

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

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

[0325] PIN service information;

[0326] service information of the first device;

[0327] PIN description information.

[0328] 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:

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

[0330] Optionally, the method further includes:

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

[0332] The first device is within the coverage of the same PIN unit PEGC with gateway capability;

[0333] A direct connection is provided with the first device.

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

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

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

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

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

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

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

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

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

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

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

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

[0346] In this embodiment, the first request message can be used to negotiate with the second device before the service switching, thereby avoiding the problem that the devices cannot negotiate before the service switching and thus affecting the PIN service performance, thereby improving the PIN service performance.

[0347] It should be noted that this embodiment is Figure 2 The implementation of the first device corresponding to the embodiment shown in the figure can be found in the specific implementation of Figure 2 To avoid repeated description, the related description of the embodiment shown in the present invention will not be repeated in detail.

[0348] See also Fig. 9 , Fig. 9 is a flow chart of another service switching method provided in an embodiment of the present application. Fig. 9 As shown, the following steps are included:

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

[0350] Optionally, the method further includes:

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

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

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

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

[0355] PIN service information;

[0356] service information of the first device;

[0357] PIN description information.

[0358] 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:

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

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

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

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

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

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

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

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

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

[0368] It should be noted that this embodiment is Figure 2 The implementation of the second device corresponding to the embodiment shown in the figure can be found in the specific implementation of the second device. Figure 2 To avoid repeated description, the related description of the embodiment shown in the present invention will not be repeated in detail.

[0369] See also Fig.10 , Fig.10 is a flow chart of another service switching method provided in an embodiment of the present application. Fig.10 As shown, the following steps are included:

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

[0371] 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;

[0372] 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:

[0373] PIN service information;

[0374] service information of the first device;

[0375] PIN description information;

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

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

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

[0379] 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;

[0380] Support service switching.

[0381] Optionally, the supporting service switching includes:

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

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

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

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

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

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

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

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

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

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

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

[0393] It should be noted that this embodiment is Figure 2 The implementation of the first device corresponding to the embodiment shown in the figure can be found in the specific implementation of Figure 2 To avoid repeated description, the related description of the embodiment shown in the present invention will not be repeated in detail.

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

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

[0396] 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 method executed by the request processing device as an example.

[0397] See also Fig.11 , Fig.11 is a structural diagram of an information synchronization device provided in an embodiment of the present application, such as Fig.11 As shown, the information synchronization device 1100 includes:

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

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

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

[0401] Sending a second message to a PIN server, wherein the second message includes the first information;

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

[0403] PIN service information;

[0404] service information of the first device;

[0405] PIN description information.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0421] Optionally, the device further comprises:

[0422] The first sending module 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.

[0423] Optionally, the method further includes:

[0424] The first receiving module is used 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.

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

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

[0427] 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:

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

[0429] Optionally, the device further comprises:

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

[0431] The first device is within the coverage of the same PIN unit PEGC with gateway capability;

[0432] A direct connection is provided with the first device.

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

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

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

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

[0437] Optionally, the device further comprises:

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

[0439] A response module, used for responding to the PIN service discovery request message based on the PIN configuration file;

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

[0441] Optionally, the device further comprises:

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

[0443] 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;

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

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

[0446] 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;

[0447] Support service switching.

[0448] Optionally, the supporting service switching includes:

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

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

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

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

[0453] 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. Exemplarily, the terminal may include but is not limited to the types of terminals listed in the embodiments of the present application, and other devices may be servers, network attached storage (NAS), etc., which are not specifically limited in the embodiments of the present application.

[0454] The information synchronization device provided in the embodiment of the present application can achieve Figure 2 The various processes implemented by the method embodiment shown achieve the same technical effect and will not be described again here to avoid repetition.

[0455] See also Fig.12 , Fig.12 is a structural diagram of another information synchronization device provided in an embodiment of the present application, such as Fig.12 As shown, the information synchronization device 1200 includes:

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

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

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

[0459] receiving a second message from a first device, wherein the second message includes the first information;

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

[0461] PIN service information;

[0462] service information of the first device;

[0463] PIN description information.

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

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

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

[0467] Optionally, the device further comprises:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0483] The information synchronization device provided in the embodiment of the present application can achieve Figure 7 The various processes implemented by the method embodiment shown achieve the same technical effect and will not be described again here to avoid repetition.

[0484] See also Fig.13 , Fig.13 is a structural diagram of a service switching device provided in an embodiment of the present application, such as Fig.13 As shown, the service switching device 1300 includes:

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

[0486] Optionally, the device further comprises:

[0487] The first receiving module is used 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.

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

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

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

[0491] PIN service information;

[0492] service information of the first device;

[0493] PIN description information.

[0494] 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:

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

[0496] Optionally, the device further comprises:

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

[0498] The first device is within the coverage of the same PIN unit PEGC with gateway capability;

[0499] A direct connection is provided with the first device.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0514] The service switching device provided in the embodiment of the present application can achieve Figure 8 The various processes implemented by the method embodiment shown achieve the same technical effect and will not be described again here to avoid repetition.

[0515] See also Fig.14 , Fig.14 is a structural diagram of another service switching device provided in an embodiment of the present application, such as Fig.14 As shown, the service switching device 1400 includes:

[0516] 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 a service switch in a PIN, and the device corresponding to the apparatus is a device in a personal Internet of Things network PIN.

[0517] Optionally, the device further comprises:

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

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

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

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

[0522] PIN service information;

[0523] service information of the first device;

[0524] PIN description information.

[0525] 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:

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

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

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

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

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

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

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

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

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

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

[0536] In the embodiment 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 the electronic device, such as an integrated circuit or a chip. For example, the electronic device can be a terminal, or it can be other devices other than a terminal. For example, the terminal can include but is not limited to the types of terminals listed in the embodiment of the present application, and other devices can be servers, NAS, etc., which are not specifically limited in the embodiment of the present application.

[0537] The service switching device provided in the embodiment of the present application can achieve Fig. 9 The various processes implemented by the method embodiment shown achieve the same technical effect and will not be described again here to avoid repetition.

[0538] See also Fig.15 , Fig.15 is a structural diagram of a request processing device provided in an embodiment of the present application, such as Fig.15 As shown, the request processing device 1500 includes:

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

[0540] 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 a first list;

[0541] 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:

[0542] PIN service information;

[0543] service information of the first device;

[0544] PIN description information;

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

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

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

[0548] 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;

[0549] Support service switching.

[0550] Optionally, the supporting service switching includes:

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

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

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

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

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

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

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

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

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

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

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

[0562] The request processing device described above can improve the PIN service performance.

[0563] In the embodiment 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 the electronic device, such as an integrated circuit or a chip. For example, the electronic device can be a terminal, or it can be other devices other than a terminal. For example, the terminal can include but is not limited to the types of terminals listed in the embodiment of the present application, and other devices can be servers, NAS, etc., which are not specifically limited in the embodiment of the present application.

[0564] The service switching device provided in the embodiment of the present application can achieve Fig.10 The various processes implemented by the method embodiment shown achieve the same technical effect and will not be described again here to avoid repetition.

[0565] like Fig.16 As shown, an embodiment of the present application further provides a communication device 1600, including a processor 1601 and a memory 1602, and the memory 1602 stores a program or instruction 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 or 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.

[0566] The 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 used to run a program or instruction to implement the following Figure 2 The steps in the information synchronization method embodiment shown in FIG. Figure 8 The steps or implementations of the service switching method embodiment shown in or 9 are as follows Fig.10 The steps in the request processing method embodiment are shown. This terminal embodiment corresponds to the first device side method embodiment, and each implementation process and implementation mode of the above method embodiment can be applied to the first embodiment and can achieve the same technical effect.

[0567] Specifically, Fig.17 A schematic diagram of the hardware structure of a device for implementing an embodiment of the present application, wherein the device is a first device or a second device.

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

[0569] Those skilled in the art will appreciate that the device 1700 may also include a power source (such as a battery) for supplying power to each component, and the power source may be logically connected to the processor 1710 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Fig.17 The device structure shown in the figure does not constitute a limitation of the device. The device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0570] It should be understood that in the 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 the static picture or video obtained by the image capture device (such as a camera) in the video capture mode or the image capture mode. The display unit 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.

[0571] In the embodiment of the present application, after receiving downlink data from the network side device, the RF unit 1701 can transmit the data to the processor 1710 for processing; in addition, the RF unit 1701 can send uplink data to the network side device. Generally, the RF unit 1701 includes but is not limited to an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

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

[0573] The processor 1710 may include one or more processing units; optionally, the processor 1710 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 1710.

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

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

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

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

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

[0579] Sending a second message to a PIN server, wherein the second message includes the first information;

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

[0581] PIN service information;

[0582] service information of the first device;

[0583] PIN description information.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0605] 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:

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

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

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

[0609] The first device is within the coverage of the same PIN unit PEGC with gateway capability;

[0610] A direct connection is provided with the first device.

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

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

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

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

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

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

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

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

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

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

[0621] 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;

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

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

[0624] 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;

[0625] Support service switching.

[0626] Optionally, the supporting service switching includes:

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

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

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

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

[0631] The radio frequency unit 1701 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.

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

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

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

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

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

[0637] PIN service information;

[0638] service information of the first device;

[0639] PIN description information.

[0640] 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:

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

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

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

[0644] The first device is within the coverage of the same PIN unit PEGC with gateway capability;

[0645] A direct connection is provided with the first device.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0659] The radio frequency unit 1701 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.

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

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

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

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

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

[0665] PIN service information;

[0666] service information of the first device;

[0667] PIN description information.

[0668] 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:

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

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

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

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

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

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

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

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

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

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

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

[0680] 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;

[0681] 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:

[0682] PIN service information;

[0683] service information of the first device;

[0684] PIN description information;

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

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

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

[0688] 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;

[0689] Support service switching.

[0690] Optionally, the supporting service switching includes:

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

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

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

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

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

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

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

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

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

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

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

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

[0703] 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 effect. To avoid repetition, it will not be repeated here.

[0704] The 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 used to run a program or instruction to implement the following Figure 7 The steps of the information synchronization method embodiment are shown. This device embodiment corresponds to the above-mentioned PIN server side method embodiment, and each implementation process and implementation method of the above-mentioned method embodiment can be applied to the network side device embodiment and can achieve the same technical effect.

[0705] Specifically, the present application embodiment also provides a device. Fig.18 As shown, 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).

[0706] Specifically, the device 1800 of the embodiment of the present invention further includes: instructions or programs stored in the memory 1803 and executable on the processor 1801, and the processor 1801 calls the instructions or programs in the memory 1803 to execute Fig.10 The methods executed by the modules shown achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.

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

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

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

[0710] receiving a second message from a first device, wherein the second message includes the first information;

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

[0712] PIN service information;

[0713] service information of the first device;

[0714] PIN description information.

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

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

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

[0718] Optionally, the method further includes:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0733] 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 effect. To avoid repetition, it will not be repeated here.

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

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

[0736] 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 embodiments, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

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

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

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

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

[0741] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including 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 one..." does not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the method and device in the embodiment of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse 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.

[0742] Through the description of the above implementation methods, 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 hardware platform, and of course, can also be implemented by hardware. The computer software product is stored in a storage medium (such as ROM, RAM, disk, CD, etc.), including several instructions to enable a terminal or a network-side device to execute the methods described in each embodiment of the present application.

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

Claims

1. An information synchronization method, characterized in that: include: 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 according to claim 1, characterized in that 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 according to claim 2, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that 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, characterized in that The method further comprises: The first device sends a first request message to the second device, where the first request message is used to negotiate a service switch in a PIN.

9. The method according to claim 8, characterized in that The method further comprises: 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, characterized in that 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, characterized in that 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, characterized in that The method further comprises: 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, characterized in that 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, characterized in that The method further comprises: 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 according to any one of claims 1 to 13, characterized in that The method further comprises: 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 according to claim 15, characterized in that 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 according to claim 16, characterized in that 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, characterized in that: include: 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 according to claim 18, characterized in that 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 according to any one of claims 18 to 20, characterized in that The method further comprises: The PIN server obtains the first information through an application layer message or contract information.

22. The method according to any one of claims 18 to 20, characterized in that 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 according to any one of claims 18 to 20, characterized in that 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 according to any one of claims 18 to 23, characterized in that 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 according to any one of claims 18 to 24, characterized in that 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, characterized in that: include: 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, wherein: The method further comprises: 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 according to claim 26 or 27, characterized in that 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 according to claim 26 or 27, characterized in that 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 according to any one of claims 26 to 29, characterized in that The method further comprises: 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 according to any one of claims 26 to 30, characterized in that 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 according to any one of claims 27 to 31, characterized in that 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 according to any one of claims 28 to 32, characterized in that 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, characterized in that: include: 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, wherein: The method further comprises: 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 according to claim 34 or 35, characterized in that 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 according to claim 35 or 36, characterized in that 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 according to claim 36 or 37, characterized in that 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 according to any one of claims 36 to 38, characterized in that 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, characterized in that: include: The first device receives a personal Internet of Things network PIN service discovery request message sent by the 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 according to any one of claims 40 to 42, characterized in that 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 according to any one of claims 40 to 43, characterized in that 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, characterized in that: include: 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, characterized in that: include: 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, characterized in that: include: 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, characterized in that: include: 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 device is a device in a personal Internet of Things network PIN.

49. A request processing device, characterized in that: include: 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, characterized in that It includes a processor and a memory, the memory storing a program or instruction that can be run on the processor, 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.

51. A readable storage medium, characterized in that: The readable storage medium stores programs or instructions, and when the programs or instructions are executed by the processor, they implement the steps of the information synchronization method as described in any one of claims 1 to 17, or implement the steps of the information synchronization method as described in any one of claims 18 to 25, or implement the steps of the service switching method as described in any one of claims 26 to 33, or implement the steps of the service switching method as described in any one of claims 34 to 39, or implement the steps of the request processing method as described in any one of claims 40 to 44.

Images