CN113301113A

CN113301113A - Profile version determination method, system, electronic device and computer storage medium

Info

Publication number: CN113301113A
Application number: CN202110390970.7A
Authority: CN
Inventors: 牛永民; 黄鹏飞
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2021-04-12
Filing date: 2021-04-12
Publication date: 2021-08-24
Anticipated expiration: 2041-04-12
Also published as: CN113301113B

Abstract

The application provides a profile version determination method, a profile version determination system, electronic equipment and a computer storage medium, relates to the technical field of electronic equipment, and solves the problem of poor profile support effect among Bluetooth equipment. The specific scheme is as follows: the external equipment requests address book synchronization service from the electronic equipment by adopting a first PBAP version; the electronic equipment provides address book synchronization service for the external equipment according to the first PBAP version; under the condition that abnormality occurs during address book synchronization service, the external equipment sends SDP request information to the electronic equipment; the electronic equipment sends second SDP response information to the external equipment; wherein the second SDP response information includes a second PBAP identifier; the second PBAP mark comprises a second version number, or comprises a first version number and a specific indicating bit with a second value; and the external equipment requests the address book synchronization service from the electronic equipment by adopting the second PBAP version according to the second PBAP identification.

Description

Profile version determination method, system, electronic device and computer storage medium

Technical Field

The present application relates to the field of electronic devices, and in particular, to a method and a system for determining a version of an application protocol (profile), an electronic device, and a computer storage medium.

Background

Bluetooth (Bluetooth) is a radio technology supporting short-distance (generally within 10 m) communication between devices, operates in a globally available 2.4GHz wireless band, and can perform data transmission between devices (such as Bluetooth devices for short) with Bluetooth functions, such as mobile phones, notebook computers, wireless headsets, and vehicle tools.

The same profile needs to be adopted between the paired bluetooth devices to implement the corresponding application service (e.g., implement address book synchronization between the bluetooth devices). Generally, the profile of the highest version supported by both parties is adopted between paired bluetooth devices to realize corresponding application services. However, in the actual use process, the bluetooth device may have a poor effect on supporting the profile of the highest version, which may cause an abnormal application service, such as a failure in address book synchronization, and affect the quality of the bluetooth service.

Disclosure of Invention

The application provides a profile version determination method, a profile version determination system, electronic equipment and a computer storage medium, which can be used for improving the abnormal use of application services between paired Bluetooth devices and improving the Bluetooth service quality.

The technical scheme is as follows:

in a first aspect, an embodiment of the present application provides a method for determining a profile version, where the method includes: an ACL link is established between the electronic equipment and the external equipment; the external equipment sends SDP request information to the electronic equipment; the SDP request information is used for inquiring the support capability of the electronic equipment to PBAP; the electronic equipment sends first SDP response information to the external equipment; wherein the first SDP response information comprises a first PBAP identifier; the first PBAP identifier is an identifier of the highest PBAP version supported by the electronic equipment; the external equipment requests address book synchronization service from the electronic equipment by adopting a first PBAP version according to the first PBAP identification and the highest PBAP version supported by the external equipment; the electronic equipment provides the address book synchronization service for the external equipment according to the first PBAP version; under the condition that the address book synchronization service is abnormal, the external equipment sends the SDP request information to the electronic equipment; the electronic equipment sends second SDP response information to the external equipment; wherein the second SDP response information includes a second PBAP identity; the second PBAP identifier comprises a second version number, or comprises a first version number and a specific indicator bit with a second value; the first version number is a version number of the first PBAP version; the external equipment requests the address book synchronization service to the electronic equipment by adopting a second PBAP version according to the second PBAP identification; wherein the first PBAP version is different from the second PBAP version; and the electronic equipment provides the address book synchronization service for the external equipment according to the second PBAP version.

In the above embodiment, under a normal condition, through SDP negotiation, an actual PBAP version for realizing the address book synchronization service is determined between the electronic device and the external device according to a highest PBAP version supported by the electronic device and a highest PBAP version supported by the external device, that is, a first PBAP version is determined. However, during the period of implementing the address book synchronization service by using the first PBAP version, if an abnormality occurs, the actual PBAP version implementing the address book synchronization service will be replaced by the next SDP negotiation between the electronic device and the external device. That is, the actual PBAP version is changed from the first PBAP protocol to the second PBAP protocol. Therefore, the support effect of the PBAP version between the electronic equipment and the external equipment is dynamically combined in the process of selecting the actual use version of the PBAP. The highest support capability and the actual support effect of the electronic equipment and the external equipment are fully considered, the problem that the address book synchronization service between the paired Bluetooth equipment is continuously abnormal in use is solved, and the Bluetooth service quality is improved.

With reference to the first aspect, in a possible design manner, during a period in which the electronic device provides the address book synchronization service to the external device according to the first PBAP version, the method further includes: the electronic equipment judges whether the address book synchronization service is abnormal or not;

under the condition that the address book synchronization service is abnormal, the method further comprises the following steps: the electronic equipment marks the external equipment;

the electronic device sends second SDP response information to the external device, including: and the electronic equipment sends the second SDP response information to the external equipment when determining that the external equipment is the marked equipment.

In the above embodiment, by marking the abnormal external device, it is avoided that the first PBAP version is continuously determined as the actually used PBAP version in the next SDP negotiation. Therefore, the user can adjust the actually used PBAP version by reconnecting the electronic equipment and the external equipment. The user can improve the abnormal address book synchronization service in a re-matching mode, and the user experience is improved.

With reference to the first aspect, in a possible design manner, the determining, by the electronic device, whether the address book synchronization service is abnormal includes:

the electronic equipment monitors whether the ACL link between the electronic equipment and external equipment is disconnected; and when the ACL link is disconnected, determining that the address book synchronization service is abnormal.

In the above embodiment, by combining the characteristics of the address book synchronization service when the abnormality occurs, whether the address book synchronization service is normally performed is monitored by adopting a mode capable of accurately identifying the abnormality, so that the accuracy of monitoring the abnormality is improved.

With reference to the first aspect, in a possible design manner, the electronic device marks the external device, including:

recording the equipment identification of the external equipment or correspondingly recording the equipment identification and the abnormal reason of the external equipment under the condition that the address book synchronous service is continuously detected for N times; wherein N is an integer not less than 2.

In the above embodiment, the external device is marked only when the abnormality occurs a plurality of times in succession. The method and the device improve the identification accuracy of the address book synchronization service abnormity caused by the PBAP version, and can avoid unnecessary PBAP version change to a certain extent.

With reference to the first aspect, in one possible design manner, the first version number is PBAP 1.2; the second version number is PBAP 1.1.

In the embodiment, the problem that the PBAP1.2 used between the electronic equipment and the external equipment is abnormal can be effectively solved.

With reference to the first aspect, in a possible design manner, before the requesting, by using the first PBAP version, the address book synchronization service from the electronic device, the method further includes:

the external equipment displays first prompt information; the first prompt message is used for inquiring whether to request the address book synchronization service;

and the external equipment receives the operation that the user agrees to request the address book synchronous service.

With reference to the first aspect, in a possible design manner, before the electronic device provides the address book synchronization service to the external device according to the first PBAP version, the method further includes:

the electronic equipment displays second prompt information, and the second prompt information is used for inquiring whether to agree with the address book synchronization service requested by the external equipment;

and the electronic equipment receives the operation that the user agrees to the address book synchronization service requested by the external equipment.

With reference to the first aspect, in a possible design manner, the providing, by the electronic device, the address book synchronization service to the external device according to the first PBAP version includes:

the electronic equipment provides the address book synchronization service for the external equipment through a first protocol channel; the first protocol path comprises data format processing, an OBEX protocol, a GOEPv2.0 protocol and an L2CAP protocol;

the electronic equipment provides the address book synchronization service to the external equipment according to the second PBAP version, and the method comprises the following steps:

the electronic equipment provides the address book synchronization service for the external equipment through a second protocol channel; wherein the second protocol path relates to data format processing, OBEX protocol, GOEP v1.0 protocol, RFCOMM protocol and L2CAP protocol.

In the above embodiment, the protocol channel is adjusted to improve the abnormal address book synchronization service caused by the insufficient performance of the device.

In a second aspect, an embodiment of the present application provides a method for determining a profile version, where the method is applied to an electronic device, and an ACL link has been established between the electronic device and an external device, and the method includes:

receiving SDP request information sent by the external equipment; the SDP request information is used for inquiring the support capability of the electronic equipment to PBAP;

sending first SDP response information to the external equipment; wherein the first SDP response information comprises a first PBAP identifier; the first PBAP identifier is an identifier of the highest PBAP version supported by the electronic equipment;

receiving an address book synchronization request sent by the external equipment by adopting a first PBAP version; the first PBAP version is the PBAP version determined by the external equipment according to the first PBAP identifier and the highest PBAP version supported by the external equipment;

providing the address book synchronization service for the external equipment according to the first PBAP version;

when abnormality occurs during the address book synchronization service period and the external device receives the SDP request information sent by the external device again, sending second SDP response information to the external device; wherein the second SDP response information includes a second PBAP identity; the second PBAP identifier comprises a second version number, or comprises a first version number and a specific indicator bit with a second value; the first version number is a version number of the first PBAP version;

receiving the address book synchronization request sent by the external equipment by adopting a second PBAP version; wherein the first PBAP version is different from the second PBAP version; the second PBAP version is the version determined by the external equipment according to the second PBAP identifier;

and providing the address book synchronization service for the external equipment according to the second PBAP version.

With reference to the second aspect, in a possible design manner, during the providing of the address book synchronization service to the external device according to the first PBAP version, the method further includes: judging whether the address book synchronization service is abnormal or not;

under the condition that the address book synchronization service is judged to be abnormal, the method further comprises the following steps: marking the external equipment;

the sending of the second SDP response information to the external device includes: and when the external device is determined to be the marked device, sending the second SDP response information to the external device.

With reference to the second aspect, in a possible design manner, the determining whether the address book synchronization service is abnormal includes:

monitoring whether the ACL link between the ACL link and external equipment is disconnected; and when the ACL link is disconnected, determining that the address book synchronization service is abnormal.

With reference to the second aspect, in one possible design manner, the marking the external device includes:

With reference to the second aspect, in one possible design manner, the first version number is PBAP 1.2; the second version number is PBAP 1.1.

With reference to the second aspect, in a possible design manner, before providing the address book synchronization service to the external device according to the first PBAP version, the method further includes:

displaying second prompt information, wherein the second prompt information is used for inquiring whether the address book synchronization request is approved or not;

and receiving the operation that the user agrees the address book synchronization request.

With reference to the second aspect, in a possible design manner, the providing, according to the first PBAP version, the address book synchronization service to the external device includes:

providing the address book synchronization service for the external equipment through a first protocol channel; the first protocol path comprises data format processing, an OBEX protocol, a GOEPv2.0 protocol and an L2CAP protocol;

the providing the address book synchronization service to the external device according to the second PBAP version includes:

providing the address book synchronization service for the external equipment through a second protocol channel; wherein the second protocol path relates to data format processing, OBEX protocol, GOEP v1.0 protocol, RFCOMM protocol and L2CAP protocol.

In a third aspect, an embodiment of the present application provides a profile version determination system, where the system includes: electronic equipment and external equipment; establishing an ACL link between the electronic equipment and the external equipment;

the external device is used for sending SDP request information to the electronic device; the SDP request information is used for inquiring the support capability of the electronic equipment to PBAP;

the electronic equipment is used for sending first SDP response information to the external equipment; wherein the first SDP response information comprises a first PBAP identifier; the first PBAP identifier is an identifier of the highest PBAP version supported by the electronic equipment;

the external device is further configured to request address book synchronization service from the electronic device by using the first PBAP version according to the first PBAP identifier and the highest PBAP version supported by the external device;

the electronic equipment is further used for providing the address book synchronization service for the external equipment according to the first PBAP version;

the external device is further configured to send the SDP request information to the electronic device when the address book synchronization service is abnormal;

the electronic equipment is further used for sending second SDP response information to the external equipment; wherein the second SDP response information includes a second PBAP identity; the second PBAP identifier comprises a second version number, or comprises a first version number and a specific indicator bit with a second value; the first version number is a version number of the first PBAP version;

the external device is further configured to request the address book synchronization service from the electronic device by using a second PBAP version according to the second PBAP identifier; wherein the first PBAP version is different from the second PBAP version;

the electronic device is further configured to provide the address book synchronization service to the external device according to the second PBAP version.

With reference to the third aspect, in a possible design manner, the electronic device is further configured to determine whether the address book synchronization service is abnormal during a period in which the electronic device provides the address book synchronization service to the external device according to the first PBAP version;

the electronic equipment is also used for marking the external equipment under the condition that the address book synchronous service is abnormal;

the electronic device is further configured to send the second SDP response information to the external device when it is determined that the external device is a marked device.

With reference to the third aspect, in a possible design manner, the electronic device is further configured to monitor whether the ACL link between the electronic device and the external device is disconnected; and when the ACL link is disconnected, determining that the address book synchronization service is abnormal.

With reference to the third aspect, in a possible design manner, the electronic device is further configured to record, when the address book synchronization service is continuously detected for N times, the device identifier of the external device, or record the device identifier of the external device and an abnormal reason correspondingly; wherein N is an integer not less than 2.

With reference to the third aspect, in a possible design manner, the first version number is PBAP 1.2; the second version number is PBAP 1.1.

With reference to the third aspect, in a possible design manner, before the address book synchronization service is requested from the electronic device by using the first PBAP version, the external device is further configured to display a first prompt message; the first prompt message is used for inquiring whether to request the address book synchronization service;

the external device is also used for receiving the operation that the user agrees to request the address book synchronization service.

With reference to the third aspect, in a possible design manner, before the electronic device provides the address book synchronization service to the external device according to the first PBAP version, the electronic device is further configured to display second prompt information, where the second prompt information is used to inquire whether to approve the address book synchronization service requested by the external device;

the electronic equipment is also used for receiving the operation that the user agrees to the address book synchronization service requested by the external equipment.

With reference to the third aspect, in a possible design manner, the electronic device is further configured to provide the address book synchronization service to the external device through a first protocol path; the first protocol path comprises data format processing, an OBEX protocol, a GOEPv2.0 protocol and an L2CAP protocol;

the electronic equipment is also used for providing the address book synchronization service for the external equipment through a second protocol channel; wherein the second protocol path relates to data format processing, OBEX protocol, GOEP v1.0 protocol, RFCOMM protocol and L2CAP protocol.

In a fourth aspect, an embodiment of the present application provides an electronic device, which includes one or more processors and one or more memories; the one or more memories are coupled to the one or more processors for storing computer program code comprising computer instructions which, when executed by the one or more processors, implement the method of the first aspect or any of its possible implementations; or implementing a method as set forth in the second aspect or any of its possible implementations.

In a fifth aspect, an embodiment of the present application provides a method for determining a profile version, where the method includes:

an ACL link is established between the electronic equipment and the external equipment;

the external equipment sends SDP request information to the electronic equipment; wherein the SDP request information is used for inquiring the supporting capability of the electronic equipment to a hands-free call protocol (HFP);

the electronic equipment sends first SDP response information to the external equipment; wherein the first SDP response information includes a first HFP identification; the first HFP identification is an identification of a highest HFP version supported by the electronic device;

the external equipment adopts the first HFP version to request a call control service from the electronic equipment according to the first HFP identifier and the highest HFP version supported by the external equipment;

the electronic device provides the call control service to the external device according to the first HFP version;

under the condition that the call control service is abnormal, the external equipment sends the SDP request information to the electronic equipment;

the electronic equipment sends second SDP response information to the external equipment; wherein the second SDP response information includes a second HFP identification;

the external device requests the call control service from the electronic device by adopting a second HFP version according to the second HFP identifier; wherein the second HFP version is lower than the first HFP version;

the electronic device provides the call control service to the external device according to the second HFP version.

In combination with the fifth aspect, in one possible design,

during the electronic device providing the call control service to the external device according to the first HFP version, the method further includes: the electronic equipment judges whether the call control service is abnormal or not;

in the case that the call control service is abnormal, the method further includes: the electronic equipment marks the external equipment;

In combination with the fifth aspect, in one possible design,

the electronic device determining whether the call control service is abnormal includes:

the electronic equipment monitors whether a silent uplink event occurs or not; and when a silent uplink event occurs, determining that the call control service is abnormal.

With reference to the fifth aspect, in a possible design manner, the electronic device marks the external device, including:

recording the equipment identifier of the external equipment under the condition of continuously detecting N times of silent uplink events, or correspondingly recording the equipment identifier and abnormal reasons of the external equipment; wherein N is an integer not less than 2.

With reference to the fifth aspect, in one possible design, the version number of the first HFP version is HFP 1.7; the version number of the second HFP version is HFP 1.6.

With reference to the fifth aspect, in one possible design, before the requesting a call control service from the electronic device using the first HFP version, the method further includes:

the external equipment displays first prompt information; the first prompt message is used for inquiring whether the call control service is requested or not;

and the external equipment receives the operation that the user agrees to request the call control service.

With reference to the fifth aspect, in one possible design manner, before the electronic device provides the call control service to the external device according to the first HFP version, the method further includes:

the electronic equipment displays second prompt information, and the second prompt information is used for inquiring whether to agree with the call control service requested by the external equipment;

and the electronic equipment receives the operation that the user agrees to the call control service requested by the external equipment.

In a sixth aspect, an embodiment of the present application provides a method for determining a profile version, where the method is applied to an electronic device, and an ACL link has been established between the electronic device and an external device, and the method includes:

receiving SDP request information sent by the external equipment; wherein the SDP request information is used for inquiring the supporting capability of the electronic equipment to HFP;

sending first SDP response information to the external equipment; wherein the first SDP response information includes a first HFP identification; the first HFP identification is an identification of a highest HFP version supported by the electronic device;

receiving a call control request sent by the external equipment by adopting a first HFP version; the first HFP version is determined by the external device according to the first HFP identifier and a highest HFP version supported by the external device;

providing the call control service to the external device according to the first HFP version;

sending second SDP response information to the external equipment under the condition that the call control service period is abnormal and the SDP request information sent by the external equipment is received again; wherein the second SDP response information includes a second HFP identification;

receiving the call control request sent by the external equipment by adopting a second HFP version; wherein the first HFP version is different from the second HFP version; the second HFP version is a version determined by the external device according to the second HFP identifier;

and providing the call control service to the external device according to the second HFP version.

In combination with the sixth aspect, in one possible design,

during the providing of the call control service to the external device according to the first HFP version, the method further includes: judging whether the call control service is abnormal or not;

under the condition that the call control service is judged to be abnormal, the method further comprises the following steps: marking the external equipment;

In combination with the sixth aspect, in one possible design,

the judging whether the call control service is abnormal or not comprises the following steps:

monitoring whether a silent uplink event occurs; and when a silent uplink event occurs, determining that the call control service is abnormal.

In combination with the sixth aspect, in one possible design,

the marking the external device comprises:

In combination with the sixth aspect, in one possible design,

the version number of the first HFP version is HFP 1.7; the version number of the second HFP version is HFP 1.6.

With reference to the sixth aspect, in one possible design manner, before providing the call control service to the external device according to the first HFP version, the method further includes:

displaying second prompt information, wherein the second prompt information is used for inquiring whether the call control request is approved or not;

and receiving the operation that the user agrees the call control request.

In a seventh aspect, an embodiment of the present application provides a computer storage medium, which includes computer instructions that, when executed on an electronic device, cause the electronic device to perform the method according to the second aspect or any one of the possible implementation manners of the second aspect; or implementing a method as claimed in any one of the possible implementations of the sixth aspect or the sixth aspect.

In an eighth aspect, embodiments of the present application provide a computer program product, which when run on a computer, causes the computer to execute the method according to the first aspect or any one of the possible implementation manners of the first aspect; or implementing a method as set forth in the second aspect or any of its possible implementations; or implementing a method as set forth in any one of the possible implementations of the fifth aspect or the fifth aspect; or implementing a method as claimed in any one of the possible implementations of the sixth aspect or the sixth aspect.

It is to be understood that the system according to the third aspect and any possible design thereof provided above, the electronic device according to the fourth aspect, the computer storage medium according to the seventh aspect, and the computer program product according to the eighth aspect are all configured to perform the corresponding methods provided above, and therefore, the beneficial effects achieved by the system according to the third aspect and any possible design thereof may refer to the beneficial effects of the corresponding methods provided above, and are not described herein again.

Drawings

Fig. 1 is an interaction diagram for determining a profile version between an electronic device and an external device provided in the related art;

FIG. 2 is a simplified diagram of a system architecture according to an embodiment of the present application;

fig. 3 is an interaction diagram for determining a profile version between an electronic device and an external device according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of a mobile phone according to an embodiment of the present application;

fig. 5 is an interaction diagram for determining a PBAP version between an electronic device and an external device according to the embodiment of the present application;

fig. 6 is one of exemplary diagrams of an interface of a terminal device according to an embodiment of the present application;

fig. 7 is a second exemplary interface diagram of a terminal device according to the embodiment of the present application;

fig. 8 is an exemplary diagram of a display interface of a mobile phone during a contact list synchronization service according to an embodiment of the present application;

fig. 9 is an exemplary diagram of a directory synchronization service reminder displayed to a user by a mobile phone in an embodiment of the present application;

FIG. 10 is an exemplary diagram of a PBAP structure in an embodiment of the present application;

fig. 11 is an exemplary diagram of a protocol path involved in implementing address book synchronization service according to a first PBAP version in the embodiment of the present application;

fig. 12 is a diagram illustrating an example of a period of address book synchronization service in an embodiment of the present application;

fig. 13 is an exemplary diagram of a protocol path involved in implementing address book synchronization service according to the second PBAP version in the embodiment of the present application;

fig. 14 is an interaction diagram for determining an HFP version between an electronic device and an external device according to an embodiment of the present application;

fig. 15 is a schematic composition diagram of a chip system according to an embodiment of the present application.

Detailed Description

In general, before data transmission is performed between an electronic device having a bluetooth function and an external device, a pairing connection must be performed. The electronic device and the external device may also be collectively referred to as a bluetooth device. In order to enable interoperation between paired Bluetooth devices, the Bluetooth Special Interest Group (SIG) makes a Bluetooth specification.

The bluetooth specification includes two parts, a core protocol (protocol) and an application protocol (profile). The core Protocol includes the lowest 4 layers (Layer) in the bluetooth Protocol stack, a basic Service Discovery Protocol (SDP), and a basic Generic Access Profile (GAP) of all profiles. The core protocol is essential in the bluetooth protocol stack.

In addition to the core protocol, the bluetooth specification must contain some other application layer services and protocols, called profile, or application layer profile. The Profile may include types of telephone directory access Profile (PBAP), hands-free call protocol (HFP), Object Push Profile (OPP), and the like.

Each type of profile may be understood as a protocol stack for implementing a type of application service. PBAP, for example, is a protocol stack for implementing address book synchronization. As another example, HFP is a protocol stack for implementing call control (e.g., answer, hang-up, reject, voice dialing, etc.).

The same version of protocol stack needs to be used between the bluetooth devices that are interoperating. For example, when the external device needs to perform call control on the electronic device, both the electronic device and the external device need to use the same version of HFP. Of course, different protocol stacks are required to implement different application services. For example, HFP is required for implementing the call control service, and PBAP is required for implementing the synchronous address book service.

Before the electronic device and the external device use the profile to realize the application service, the two parties can negotiate the respective supported profiles. For example, after an Asynchronous Connection (ACL) link is established between any two or more bluetooth devices, the device information and supported profile can be queried through an SDP in the bluetooth framework, so that a corresponding connection is established between the bluetooth devices.

As an example, as shown in fig. 1, after an ACL link is established between the electronic device and the external device, the external device may transmit SDP request information to the electronic device. The SDP request information is used for indicating the support capability of the query electronic device for the profile. In some embodiments, it may be used to query all profiles that may be supported by the electronic device. In other embodiments, it may be used to query for a particular profile.

After receiving the SDP request message, the electronic device may send an SDP response message to the external device. Wherein the SDP response information includes the highest profile version supported by the electronic device. For example, in a scenario of querying all profiles supported by the electronic device, the SDP response information includes the highest version information of all profiles supported by the electronic device. For another example, in a scenario of querying a specific profile, the SDP response information includes information of a highest version of the specific profile supported by the electronic device.

The electronic device may determine the highest profile version supported by the electronic device according to a service record (server record) list maintained by the electronic device and the SDP request information. The server record list may include a plurality of server record entries, each of which contains information of one type of application service. Each server record entry may be composed of multiple Service attributes (Service attributes), each of which describes a single characteristic of an application Service.

For example, the SDP request information indicates querying PBAP and HFP. And querying the highest PBAP version and the highest HFP version supported by the electronic equipment through a server record list maintained in the electronic equipment.

Through the interaction of the SDP request information and the SDP response information, the external device can judge the highest profile version commonly supported by the electronic device. Therefore, the external device can request the corresponding application service according to the determined highest profile version supported together. Then, the electronic device provides the corresponding application service to the external device according to the highest profile version commonly supported by the electronic device and the external device, so that a communication channel corresponding to the required service is established.

That is, the highest profile version supported in common is determined as the actual usage version for implementing the corresponding application service between the bluetooth devices.

Obviously, in the related art, the highest profile version supported together is taken as the actual use version, and essentially, the actual use versions of various profiles are determined according to the static capability attributes of the electronic device and the external device. The static capability attribute refers to the capability characteristic measured when the Bluetooth device is not in operation, and represents the attribute that the Bluetooth device can not support. For example, the static capability attribute may be the highest supported capability of the bluetooth device.

To determine the actual usage version example of PBAP between the electronic device and the external device, refer to table 1:

TABLE 1

Highest supported version of electronic device	Highest supported version of external device	Actual use version
			PBAP1.2	PBAP1.2	PBAP1.2
PBAP1.1	PBAP1.2	PBAP1.1
			PBAP1.2	PBAP1.1	PBAP1.1
PBAP1.1	PBAP1.1	PBAP1.1

As shown in table 1, PBAP1.2 is the highest version of PBAP at present, and if both the electronic device and the external device support PBAP1.2, the negotiated actual usage version is PBAP 1.2. If the electronic device supports the highest PBAP1.2 and the external device supports the highest PBAP1.1, the negotiated actual usage version is PBAP 1.1. If the external device supports the highest PBAP1.2 and the electronic device supports the highest PBAP1.1, the negotiated actual use version is PBAP 1.1.

However, the effect of actually supporting the profile version between bluetooth devices is embodied by the dynamic capability attribute. The dynamic capability attribute refers to the actual capability embodied in the actual work of the bluetooth device, and is an attribute representing the 'good and bad' supporting effect of the bluetooth device.

For example, the electronic device and the external device both support PBAP1.2, but the performance of the process of actually using PBAP1.2 by the external device is very poor (e.g., an exception occurs in address book synchronization), and the external device is not suitable for using PBAP1.2 for the characterization of the dynamic capability attribute of the external device.

However, in the related art, when the SDP is used to negotiate the actual use version, the dynamic capability attribute of the bluetooth device is not considered, so that when both parties use PBAP1.2 supported by them to implement address book synchronization, an address book synchronization exception still occurs.

In case of abnormal address book synchronization, the user can recover the address book even in a re-matching mode. That is, by disconnecting the electronic device from the external device, a new round of SDP negotiation is triggered. In a new round of SDP negotiation, PBAP1.2 is still selected as the actual use version among Bluetooth devices. This also means that an anomaly may still occur when the address book synchronization is performed again. Of course, other types of profiles than PBAP have the same problem.

Obviously, in the related art, the quality of the bluetooth service is directly affected by an inflexible profile version determination mode.

In order to improve the problem of abnormal use of application services between paired bluetooth devices and improve the quality of bluetooth services, embodiments of the present application provide a profile version determination method, where an actual use version of a corresponding profile is replaced when an application service abnormality realized through the profile is detected. Therefore, the support effect of the electronic equipment and the external equipment on the profile version is dynamically combined in the process of selecting the actual use version of the profile. The static capability attribute and the dynamic capability attribute of the electronic equipment and the external equipment are fully considered, the problem of continuous abnormal use of the application service between the paired Bluetooth equipment is solved, and the Bluetooth service quality is improved. In addition, the user can complete the improvement of the application service abnormity in a re-matching mode, and the user experience is improved.

Fig. 2 shows a simplified schematic diagram of a system architecture to which embodiments of the present application may be applied. As shown in fig. 2, the system architecture may include: electronic equipment and external equipment.

The electronic device refers to a device supporting connection with an external device through a wireless communication protocol. In particular implementations, the electronic device may be a desktop, laptop, tablet, handheld Computer, cell phone, notebook, Ultra-mobile Personal Computer (UMPC), netbook, as well as a cellular phone, Personal Digital Assistant (PDA), television, VR device, AR device, and the like. As an example, fig. 2 illustrates that the electronic device is a mobile phone.

The external device refers to a device supporting connection with the electronic device through a wireless communication protocol. In specific implementation, the external device may be a wearable device, smart glasses, a smart watch, a keyboard, a sound box, a printer, a smart home device, a vehicle-mounted terminal, an inkcase, an earphone, a bracelet, or the like. The electronic equipment and the external equipment can be interchanged. The intelligent household equipment can be a water dispenser, an air conditioner, a refrigerator and the like. As an example, the external device is a vehicle-mounted terminal in fig. 2.

In this embodiment of the application, as shown in fig. 3, after the ACL link between the electronic device and the external device is established, the external device sends the first SDP request information to the electronic device. After receiving the first SDP request message, the electronic device sends a first SDP response message to the external device. The first SDP request information is used for inquiring the support capability of the electronic equipment for the profile. The first SDP response information carries a first identifier. The first identification is an identification of a highest profile version supported by the electronic device.

Therefore, the external device can determine the highest profile version, also called a first protocol version, commonly supported between the electronic device and the external device according to the first identifier. For example, the external device may compare the profile version indicated by the first identifier with the highest profile version supported by the external device, and determine a lower profile version to obtain the first protocol version.

Thereafter, the external device may request the corresponding application service, also referred to as a first application service, from the electronic device according to the specification of the first protocol version. The electronic device may then provide the first application service to the external device as specified by the first protocol version.

During the providing of the first application service, the electronic device may detect whether the first application service is abnormal. According to different types of the first application service, whether the first application service is abnormal or not can be judged by adopting a proper strategy.

If the electronic equipment detects that the first application service period is abnormal, SDP request information sent by the external equipment is received next time, and the electronic equipment is regarded as second SDP request information.

Generally, the mismatch between the electronic device and the external device may trigger the external device to send the SDP request message to the electronic device again. Of course, when the ACL link between the electronic device and the external device is not disconnected, the vehicle-mounted terminal may send the SDP request information to the mobile phone again.

In some scenarios, the above-mentioned re-matching may be an ACL link disconnection reconnection due to an anomaly of the first application service. In other scenarios, the above-mentioned re-matching may also be an ACL link disconnection reconnection triggered manually by the user.

After the electronic device receives the second SDP request message, it may send a second SDP response message to the external device. Wherein the second SDP response information may comprise the second identity. The second identifier is an identifier of a second protocol version. The second protocol version is different from the first protocol version and is not higher than the first protocol version. And the electronic equipment indicates the external equipment to adopt the second protocol version to realize the first application service through the second SDP response information.

It can be understood that, after receiving the second SDP response message, the external device may also compare the second protocol version indicated by the second identifier with the highest profile version supported by the external device, and select a lower profile version from the second protocol version. Because the highest profile version supported by the external device is not lower than the first protocol version, and meanwhile, the first protocol version is not lower than the second protocol version, the external device can take the second protocol version as the actual use version of the profile after comparison.

That is, the external device may request the first application service from the electronic device according to the specification of the second protocol version. Then, the electronic device provides the first application service to the external device according to the specification of the second protocol version.

That is, both parties agree to implement the first application service in accordance with the specification of the second protocol version.

It can be seen that, when the second SDP request message is received, the electronic device already knows that the first protocol version is supported by the external device. In order to avoid that the first protocol version is selected again to cause abnormal and repeated occurrence, the electronic device enables the external device to request the corresponding application service by adopting different profile versions through the second identifier of the second SDP response information. Through the adjustment to the agreement, improve the problem that the version support effect is not good between the bluetooth equipment, improve the quality of bluetooth service.

For convenience of understanding, in the embodiment of the present application, an electronic device is taken as an example for description. The following describes the components of the mobile phone in detail with reference to the accompanying drawings:

as shown in fig. 4, the mobile phone may include a processor 110, an external memory interface 120, an internal memory 121, a Universal Serial Bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, a Subscriber Identity Module (SIM) card interface 195, and the like. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

It is to be understood that the illustrated structure of the embodiment of the present invention is not to be specifically limited to a mobile phone. In other embodiments of the present application, the handset may include more or fewer components than shown, or combine certain components, or split certain components, or a different arrangement of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

Processor 110 may include one or more processing units, such as: the processor 110 may include an Application Processor (AP), a modem processor, a Graphics Processing Unit (GPU), an Image Signal Processor (ISP), a controller, a memory, a video codec, a Digital Signal Processor (DSP), a baseband processor, and/or a neural-Network Processing Unit (NPU), etc. The different processing units may be separate devices or may be integrated into one or more processors.

A memory may also be provided in processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may hold instructions or data that have just been used or recycled by the processor 110.

In some embodiments, processor 110 may include one or more interfaces. The interface may include an integrated circuit (I2C) interface, an integrated circuit built-in audio (I2S) interface, a Pulse Code Modulation (PCM) interface, a universal asynchronous receiver/transmitter (UART) interface, a Mobile Industry Processor Interface (MIPI), a general-purpose input/output (GPIO) interface, a Subscriber Identity Module (SIM) interface, and/or a Universal Serial Bus (USB) interface, etc.

It should be understood that the interface connection relationship between the modules in the embodiment of the present invention is only schematically illustrated, and does not form a limitation on the structure of the mobile phone. In other embodiments of the present application, the mobile phone may also adopt different interface connection manners or a combination of multiple interface connection manners in the above embodiments.

The wireless communication function of the mobile phone can be realized by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor, the baseband processor, and the like.

Wherein the antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. The mobile communication module 150 may provide a solution including wireless communication of 2G/3G/4G/5G, etc. applied to a mobile phone. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a Low Noise Amplifier (LNA), and the like. The mobile communication module 150 may receive the electromagnetic wave from the antenna 1, filter, amplify, etc. the received electromagnetic wave, and transmit the electromagnetic wave to the modem processor for demodulation. The mobile communication module 150 may also amplify the signal modulated by the modem processor, and convert the signal into electromagnetic wave through the antenna 1 to radiate the electromagnetic wave. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 may be disposed in the same device as at least some of the modules of the processor 110.

The modem processor may include a modulator and a demodulator. The modulator is used for modulating a low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then passes the demodulated low frequency baseband signal to a baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the receiver 170B, etc.) or displays an image or video through the display screen 194. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be provided in the same device as the mobile communication module 150 or other functional modules, independent of the processor 110.

The wireless communication module 160 may provide solutions for wireless communication applied to a mobile phone, including Wireless Local Area Networks (WLANs) (e.g., wireless fidelity (Wi-Fi) networks), Bluetooth (BT), Global Navigation Satellite System (GNSS), Frequency Modulation (FM), Near Field Communication (NFC), Infrared (IR), and the like. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, performs frequency modulation and filtering processing on electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 160 may also receive a signal to be transmitted from the processor 110, perform frequency modulation and amplification on the signal, and convert the signal into electromagnetic waves through the antenna 2 to radiate the electromagnetic waves.

In some embodiments, the handset antenna 1 is coupled to the mobile communication module 150 and the handset antenna 2 is coupled to the wireless communication module 160 so that the handset can communicate with the network and other devices via wireless communication techniques. For example, in the embodiment of the present application, the mobile phone may utilize the wireless communication module 160 to establish a wireless connection with an external device (e.g., a vehicle-mounted terminal) through a wireless communication technology, such as Bluetooth (BT). Based on the established wireless connection, the mobile phone can send voice data to the external equipment and can also receive the voice data from the external equipment.

The mobile phone can implement audio functions through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the earphone interface 170D, and the application processor. Such as music playing, recording, etc.

In the embodiment of the application, when the mobile phone establishes wireless connection with an external device (such as a vehicle-mounted terminal), the vehicle-mounted terminal can be used as an audio input/output device of the mobile phone. For example, the audio module 170 may receive an audio electrical signal transmitted by the wireless communication module 160, so as to implement functions of answering a call, playing music, and the like through the vehicle-mounted terminal. For example, in the process of making a call, the in-vehicle terminal may collect a voice signal of the user, convert the voice signal into an audio electrical signal, and send the audio electrical signal to the wireless communication module 160 of the mobile phone. The wireless communication module 160 transmits the audio electrical signal to the audio module 170. The audio module 170 may convert the received audio electrical signal into a digital audio signal, encode the digital audio signal, and transmit the encoded digital audio signal to the mobile communication module 150. And is transmitted to the opposite-end call device by the mobile communication module 150 to implement a call. For another example, when the user plays music using the media player of the mobile phone, the application processor may transmit an audio electrical signal corresponding to the music played by the media player to the audio module 170. The audio electrical signal is transmitted by the audio module 170 to the wireless communication module 160. The wireless communication module 160 may transmit the audio electrical signal to the vehicle-mounted terminal, so that the vehicle-mounted terminal converts the audio electrical signal into a sound signal and plays the sound signal.

The embodiment of the application provides a profile version determination method, which can be realized by matching electronic equipment and external equipment paired by Bluetooth. For example, the method can be implemented by matching a mobile phone and a vehicle-mounted terminal paired by bluetooth as shown in fig. 4.

The method is suitable for various profiles commonly supported between the electronic equipment and the external equipment. In order to facilitate understanding of those skilled in the art, in the embodiment of the present application, an electronic device is taken as a mobile phone, and an external device is taken as a vehicle-mounted terminal for example.

Under the condition that the mobile phone and the vehicle-mounted terminal are in Bluetooth pairing (namely, an ACL link is successfully established) and the PBAP is supported together, the first application service can be an address book synchronization service. For convenience of understanding by those in the art, the profile version determination method provided in the embodiment of the present application is described below by taking an in-vehicle terminal as a requester of address book synchronization service and a mobile phone as a provider of address book synchronization service as an example.

As shown in fig. 5, the profile version determination method may include the following steps:

s101, the vehicle-mounted terminal sends first SDP request information to the mobile phone.

In this embodiment of the present application, the first SDP request information may be used to indicate a support capability of the querying handset for at least one profile. Meanwhile, PBAP is included in the at least one queried profile.

Illustratively, the vehicle-mounted terminal may query all profiles supported by the mobile phone from the mobile phone through the first SDP request message. Thus, when the handset supports PBAP, the at least one queried profile includes PBAP.

Illustratively, the vehicle-mounted terminal can specify the PBAP query to the mobile phone through the first SDP request message. Thus, the PBAP is also included in the at least one profile that is queried.

Of course, in some possible embodiments, it may also be that the vehicle-mounted terminal has queried all profiles supported by the mobile phone through the SDP request message, and when it is determined that the PBAP is supported by the mobile phone, the vehicle-mounted terminal may directionally query the support capability of the mobile phone for the PBAP through the first SDP request message.

S102, the mobile phone sends first SDP response information to the vehicle-mounted terminal.

The first SDP response message may include a first identifier, which is also referred to as a first PBAP identifier. In addition, the first PBAP identification may be an identification of the highest PBAP version supported by the handset.

In this embodiment of the present application, when the first SDP request message indicates to query the PBAP support capability of the mobile phone, the mobile phone may determine the highest PBAP version that the mobile phone can support according to a server record list maintained therein. Then, based on the highest PBAP version supportable by the mobile phone, a first PBAP identification is determined.

For example, the first PBAP identification may be the version number of the highest PBAP version supportable by the handset. As another example, the first PBAP identification may be a specific indicator bit within the highest PBAP version that the handset can support. For another example, the first PBAP flag may include a version number of the highest PBAP version supportable by the handset and a specific indication bit.

Illustratively, in the case that the handset supports the PBAP of the first version number at the highest, then the matching entry that the handset queries from the server record list is shown in table 2:

TABLE 2

Table 2 shows a Bluetooth application description List (Bluetooth profile Descriptor List) of the mobile phone. Table 2 shows that the value of Supported profile is PBAP. The application version (profile version) is a first version number, and a specific indicator bit (i.e., L2Cap PSM) exists in the bluetooth application list and takes the value of the first version number. In conjunction with table 2, the first PBAP identification may include a first version number and an L2Cap PSM taking a first value. Alternatively, in other embodiments, the first PBAP identification may be an L2Cap PSM taking a first value.

In this embodiment of the application, the first PBAP identifier may instruct the vehicle-mounted terminal to determine a highest PBAP version commonly supported between the mobile phone and the vehicle-mounted terminal, which may also be referred to as a first PBAP version.

Therefore, after receiving the first SDP response information, the vehicle-mounted terminal may determine the first PBAP version (i.e., the first protocol version) according to the highest PBAP version supported by the mobile phone and the highest PBAP version supported by the vehicle-mounted terminal. And determining to request address book synchronization service using the specification of the first PBAP version.

Under the condition that the vehicle-mounted terminal requests the address book synchronization service according to the specification of the first PBAP version, the mobile phone also provides the address book synchronization service for the vehicle-mounted terminal according to the specification of the first PBAP version.

That is, through S101 and S102, the mobile phone and the vehicle-mounted terminal may agree to implement the address book synchronization service using the first PBAP version.

Of course, the manner of implementing the PBAP version of the address book synchronization service is not limited thereto. In other embodiments, the first SDP request message may include an identifier of a highest PBAP version supported by the vehicle-mounted terminal. For example, the in-vehicle terminal supports PBAP1.1 and PBAP1.2, and PBAP1.2 is a version higher than PBAP1.1, the first SDP request message may include a version number of PBAP 1.2.

Under the condition that the first SDP request information comprises the identifier of the highest PBAP version supported by the vehicle-mounted terminal, the first PBAP version between the vehicle-mounted terminal and the mobile phone can be determined by the mobile phone. And informing the vehicle-mounted terminal to request the address book synchronization service to the mobile phone by adopting the specification of the first PBAP version through the first SDP response message. Therefore, the protocol realizes the address book synchronization service by adopting the first PBAP version.

S103, the vehicle-mounted terminal sends an address book synchronization request to the mobile phone according to the specification of the first PBAP protocol.

In some embodiments, after receiving the first SDP response message, the vehicle-mounted terminal may autonomously request the address book synchronization service from the mobile phone, that is, autonomously send an address book synchronization request to the mobile phone.

Of course, in other embodiments, after the vehicle-mounted terminal receives the first SDP response message, the vehicle-mounted terminal may display a first prompt message, where the first prompt message is used to inquire whether to request the address book synchronization service. And when the vehicle-mounted terminal receives the operation that the user agrees to request the address book synchronization service, the vehicle-mounted terminal sends an address book synchronization request to the mobile phone.

For example, when the in-vehicle terminal receives the first SDP response information, the in-vehicle terminal displays an inquiry frame as shown in fig. 6. The inquiry box comprises a text prompt of 'whether to request address book synchronization', a first control with an icon of 'yes' and a second control with an icon of 'no'. And under the condition that the first control clicked by the user is received, triggering to send an address book synchronization request to the mobile phone.

In other embodiments, after the vehicle-mounted terminal receives the first SDP response information, the vehicle-mounted terminal may display the existing address book data. An updating control can be arranged on an interface for displaying the existing address book data. When the user receives the update control, the request for the address book synchronization service is triggered to the mobile phone, namely the vehicle-mounted terminal is triggered by the user operation to send the address book synchronization request to the mobile phone.

For example, after the vehicle-mounted terminal receives the first SDP response information, the vehicle-mounted terminal enters an address list display interface under the operation of a user. As shown in fig. 7, the address book display interface displays an update control in addition to the existing address book data in the vehicle-mounted terminal. And after the user clicks the updating control, the vehicle-mounted terminal sends an address book synchronization request to the mobile phone.

And S104, after receiving the address book synchronization request, the mobile phone provides address book synchronization service for the vehicle-mounted terminal.

After the mobile phone receives the address book synchronization request, the mobile phone can be automatically started to provide address book synchronization service for the vehicle-mounted terminal. As an example, as shown in fig. 8, in the process that the mobile phone provides the address book synchronization service to the vehicle-mounted terminal, the mobile phone may display a prompt message to prompt that the mobile phone is in address book synchronization. Correspondingly, the vehicle-mounted terminal can also display prompt information for displaying the synchronization that the vehicle-mounted terminal is receiving the address book.

In other embodiments, after the mobile phone receives the address book synchronization request, second prompt information is displayed, and the second prompt information is used for inquiring whether the address book synchronization request of the vehicle-mounted terminal is approved or not. And after the mobile phone receives the operation that the user agrees with the address book synchronization request of the vehicle-mounted terminal, providing address book synchronization service for the vehicle-mounted terminal.

For example, as shown in fig. 9, a mobile phone may display a contact list synchronization request of a vehicle-mounted terminal to solicit a user's opinion. And under the condition that the mobile phone receives the operation that the user agrees to synchronize the address book of the mobile phone to the vehicle-mounted terminal, starting to provide address book synchronization service for the vehicle-mounted terminal.

In the process of providing the address book synchronization service for the vehicle-mounted terminal by the mobile phone, the rules of PBAP need to be followed. The PBAP composition is shown in fig. 10. Fig. 10 relates to an application layer, a data format processing layer, an Object Exchange Protocol (OBEX), a public method of OBEX operation (GOEP), a serial communication Protocol (RFCOMM), a Logical Link Control and Adaptation Protocol (L2 CAP), an SDP, a Link Management Protocol (LMP), and a base band layer.

The data format processing layer is used for converting a data format, for example, converting a data format of an address book data packet.

OBEX, a session layer protocol established by the infrared data association (IrDA) for the exchange of data objects over an infrared data link. The bluetooth SIG employs this protocol so that it is possible for the original infrared link-based OBEX application to be easily ported to bluetooth or switched between the two. OBEX is an efficient binary protocol that exchanges objects in a simple and spontaneous way. For the OBEX protocol, the mobile phone plays the role of a server as a provider of object exchange (i.e., address book exchange), and the vehicle-mounted terminal plays the role of a client as a receiver of object exchange.

For GOEP, there can be divided into v1.0 version, v1.2 version and later.

The RFCOMM provides a Serial Emulation interface (API) for Serial Emulation, including Emulation of data signal lines and non-data signal lines. The method can simulate a plurality of serial ports between two devices, can support multi-serial port simulation among a plurality of devices, and simultaneously provides simulation of a modem in the RFCOMM.

A Logical Link Control and Adaptation Protocol (L2 CAP), which is an Adaptation Protocol for shielding a baseband Protocol for a higher layer Protocol, is located above the baseband Protocol, belongs to a data Link layer, provides connection-oriented and connectionless-oriented data services for the higher layer, and completes functions Of Protocol multiplexing, segmentation and reassembly, Quality Of Service (QoS) transmission, group abstraction, and the like.

The Baseband or Link Controller (LC) layer mainly performs the interconversion between the rf signal and the digital or voice signal, and implements the Baseband protocol and other underlying connection protocols.

Exemplarily, in the embodiment of the present application, with reference to fig. 10, a process of providing the address book synchronization service by the mobile phone according to the first PBAP version is as follows:

as shown in fig. 11, each address book packet is first processed according to the protocol path (i).

The protocol path (i) relates to data format processing, obex (server) protocol, goepv2.0 protocol (or a version after goepv 2.0), and L2CAP protocol.

In this embodiment, the address book packet is processed by data format processing, OBEX protocol, goepv2.0 protocol (or a version after goepv 2.0), L2CAP protocol, etc., so that the finally obtained communication packet can meet the requirements of data format processing, OBEX (server) protocol, goepv2.0 protocol (or a version after goepv 2.0), and L2CAP protocol.

Next, the address book packet processed through the protocol path (i.e., the first protocol path) is transmitted to the in-vehicle terminal.

After receiving the address book data packet, the vehicle-mounted terminal may receive the address book synchronization service according to the first PBAP version in the following process: and the vehicle-mounted terminal decodes the received address book data packet according to the protocol channel II. Protocol channel 2 involves L2CAP protocol, goepv2.0 protocol (or version after goepv 2.0), obex (client) protocol, and data format processing.

And S105, during the period of providing the address book synchronization service, the mobile phone detects whether the vehicle-mounted device is disconnected or not.

The vehicle-mounted terminal disconnection means the disconnection of the Bluetooth connection between the mobile phone and the vehicle-mounted terminal.

In practical applications, the processing speed is fast no matter the protocol path (i) in fig. 11 is used to encode data or the protocol path (ii) is used to decode data. However, the data processing efficiency of some vehicle-mounted terminals cannot keep up. Therefore, even if some of the in-vehicle terminals can support the first PBAP version, the data processing efficiency cannot be kept up with the in-vehicle terminals, which results in a synchronization failure (i.e., a service abnormality).

In the embodiment of the application, when the mobile phone provides the address book synchronization service, whether disconnection between the mobile phone and the vehicle-mounted terminal occurs or not can be monitored in real time.

The address book synchronization service period may be in the process of service continuity. For example, as shown in fig. 12 (a), the mobile phone provides the address book synchronization service to the vehicle-mounted terminal starting at a first time, and the address book synchronization service ending at a second time, where a period from the first time to the second time is an address book synchronization service period.

In other embodiments, the address book synchronization service period includes not only the duration of the service, but also the specified duration after the service is finished. As shown in fig. 12 (b), the specified time period is set to 5s, and the time period between the first time and the third time is the address book synchronization service period.

During the address book synchronization service period, the mobile phone can mark the vehicle-mounted terminal after detecting one-time disconnection of the vehicle, so as to record that the vehicle-mounted terminal has poor supporting effect on the commonly supported highest profile version.

For example, the manner of marking the vehicle-mounted terminal may be: correspondingly recording the equipment Identification (ID) of the vehicle-mounted terminal and the reason causing the service abnormity in a preset table. Therefore, the device identification and the abnormal reason of the vehicle-mounted terminal are correspondingly recorded.

For another example, the manner of marking the vehicle-mounted terminal may also be: the mobile phone can write the device ID of the vehicle-mounted terminal into the corresponding device information set. In this way, recording of device identification is achieved. The device information set may be maintained by the mobile phone (that is, the device information set is stored in the mobile phone and updated by the mobile phone). The device information set may also be maintained by a cloud device in communication with the mobile phone, which is not limited herein. And recording the equipment identification of the vehicle-mounted terminal by putting the equipment ID of the vehicle-mounted terminal into the equipment information set.

Certainly, in order to improve the fault tolerance, the mobile phone may detect N times of disconnection of the vehicle and mark the vehicle-mounted terminal during the period of implementing the address book synchronization service by using the first PBAP version, so as to record that the vehicle-mounted terminal has a poor support effect on the commonly supported highest profile version. Wherein N is an integer not less than 2.

In other words, the mobile phone can mark the vehicle-mounted terminal under the condition that the number of times of disconnection of the vehicle is not less than N times. And under the condition that the number of times of disconnection of the continuous vehicle is less than N times, no special mark is made on the vehicle-mounted terminal.

In some embodiments, the manner for the mobile phone to count whether the vehicle-mounted terminal is disconnected for N times between the mobile phone and the vehicle-mounted terminal may be: and during the period of adopting the first PBAP version, increasing one by the disconnection count corresponding to the vehicle-mounted terminal every time the vehicle-mounted terminal is disconnected. And when the disconnection count of the vehicle-mounted terminal reaches N times, marking the vehicle-mounted terminal, and resetting the disconnection times of the vehicle-mounted terminal.

In other embodiments, the manner for the mobile phone to count whether the vehicle-mounted terminal is disconnected for N times between the mobile phone and the vehicle-mounted terminal may be: and (4) counting whether the connection between the mobile phone and the vehicle-mounted terminal is broken for N times continuously. Illustratively, a first PBAP version is adopted to realize the first disconnection of the vehicle-mounted terminal during the address book synchronization service period, and the disconnection count of the vehicle-mounted terminal is counted 1. And after the mobile phone and the vehicle-mounted terminal are reconnected, continuously adopting the first PBAP version to realize the address book synchronization service period, and counting 2 the disconnection count of the vehicle-mounted terminal if the vehicle-mounted terminal is disconnected again. Conversely, if the locomotive disconnection does not occur (namely the synchronous service sequence of the address list is completed), the abnormal times are cleared.

And S106, the vehicle-mounted terminal sends second SDP request information to the mobile phone.

In some embodiments, the abnormal behavior of the address book synchronization service is a vehicle-machine disconnection. After the vehicle is disconnected, if an ACL link is established again between the mobile phone and the vehicle-mounted terminal, the vehicle-mounted terminal can also send SDP request information to the mobile phone again.

In fact, both the first SDP request message and the second SDP request message may be used to query the PBAP support capability of the handset. When the mobile phone has marked the in-vehicle terminal, the mobile phone regards the SDP request information sent by the in-vehicle terminal as the second SDP request information, and the flow proceeds to step S107.

That is, in some embodiments, the method further comprises: after receiving the SDP request message sent by the vehicle-mounted terminal, the mobile phone queries whether the vehicle-mounted terminal has a tag, if the vehicle-mounted terminal has a tag, the process goes to step S107, and if the vehicle-mounted terminal does not have a tag, the process goes to step S102.

For example, after receiving an SDP request sent by the vehicle-mounted terminal, the mobile phone queries whether the device ID carried in the SDP request information belongs to a preset table. If the carried device ID belongs to the preset table and the cause of the service abnormality recorded in the preset table is disconnection of the locomotive, the process proceeds to step S107. If the carried device ID does not belong to the device information set, or the reason for the abnormal service recorded in the preset table is not the locomotive disconnection, the process proceeds to step S102.

For another example, after receiving an SDP request sent by the vehicle-mounted terminal, the mobile phone queries whether the device ID carried in the SDP request information belongs to the device information set. If the carried device ID belongs to the device information set, the flow advances to step S107. If the carried device ID does not belong to the device information set, the process proceeds to step S102.

And S107, the mobile phone sends second SDP response information to the vehicle-mounted terminal.

In the embodiment of the application, in order to avoid that the vehicle-mounted terminal continues to select the first PBAP version when the vehicle-mounted terminal determines the actually used version again. The second SDP response information may include a second identifier, and the second identifier may be a second PBAP identifier. The second PBAP identity is also the identity of the second PBAP version.

Obviously, the second PBAP version is different from the first PBAP version, and the second PBAP version is no higher than the first PBAP version. And the vehicle-mounted terminal can be instructed to request the address book synchronization service by adopting a second PBAP version through the second PBAP identifier. Therefore, under the condition that the support effect of the first PBAP version is not good, the second PBAP version is selected as the actual use version, the synchronous service quality of the address list is improved, and the possibility of disconnection of the vehicle is reduced.

In some embodiments, the difference between the second PBAP version and the first PBAP version may be a difference in the versions themselves. For example, the second PBAP version and the first PBAP version have different corresponding version numbers. As an example, in such an embodiment, the second PBAP version may be lower than the first PBAP version, and the problem of poor support effect of the bluetooth device on the high version protocol is solved by reducing the version.

In order to enable the vehicle-mounted terminal to determine that the specification of the second PBAP version is adopted to request the address book synchronization service, the second PBAP identifier may be a version number of the second PBAP version.

For example, the second version number is lower than the first version number, and the matching entry queried by the handset from the server record list may be as shown in table 3:

TABLE 3

Table 3 shows a Bluetooth application description List (Bluetooth profile Descriptor List) of the mobile phone. Table 3 shows the value of Supported profile as PBAP. The application version (profile version) is the second version number. Referring to table 3, the second PBAP identification may be the second version number in table 3.

It can be understood that the principle of the in-vehicle terminal determining the actually used version of PBAP is: and determining the actual use version according to the PBAP version number in the SDP response information and the highest PBAP version number supported by the SDP response information. That is, when the PBAP version number in the second SDP response message is the second version number, since the version number of the highest PBAP version supported by the vehicle-mounted terminal is not lower than the first version number and the first version number is not lower than the second version number, the vehicle-mounted terminal determines the second PBAP version as the actually used version.

In some embodiments, the difference between the second PBAP version and the first PBAP version may be that the specific indication bits in the same version are different, that is, the supporting effect of the bluetooth device on the protocol is improved by temporarily adjusting the protocol.

In order to enable the vehicle-mounted terminal to determine that the address book synchronization service is requested by adopting the specification of the second PBAP version, the second PBAP identifier in the second SDP response information may be a version number and a specific indication bit.

For example, the matching part that the handset queries from the server record may be table 4:

TABLE 4

Table 4 shows a Bluetooth application description List (Bluetooth profile Descriptor List) of the mobile phone. Table 4 shows the value of Supported profile as PBAP. The application version (profile version) is the first version number, and a specific indicator bit (i.e., L2Cap PSM) exists in the bluetooth application list, and its value is the second value. In conjunction with table 4, the second PBAP identification may be the first version number in table 4 and the L2Cap PSM taking the second value. Alternatively, in other embodiments, the second PBAP identity may also be an L2Cap PSM that takes a second value.

In this embodiment of the application, the vehicle-mounted terminal may send the address book synchronization request to the mobile phone by using the specification of the second PBAP version when receiving the second SDP response message. In other embodiments, the vehicle-mounted terminal may be triggered to send the address book synchronization request to the mobile phone by using the specification of the second PBAP version, when the second SDP response information is received and the vehicle-mounted terminal receives the user operation.

And under the condition of receiving an address book synchronization request sent by the vehicle-mounted terminal, the mobile phone also provides address book synchronization service for the vehicle-mounted terminal according to the specification of the second PBAP version.

Therefore, the address book synchronization service can be realized by adopting the second PBAP version between the mobile phone and the vehicle-mounted equipment through the protocols of S106 and S107.

In addition, whether the second PBAP version is obtained by reducing the version or by changing a specific indication bit in the version, essentially, the second PBAP version is a protocol path for guiding the mobile phone and the vehicle-mounted terminal to change and process the address book data packet. Referring to fig. 10, as shown in fig. 13, the process of providing the address book synchronization service to the vehicle-mounted terminal by the mobile phone according to the specification of the second PBAP version is as follows:

firstly, each address book data packet is processed according to a protocol path (namely, a second protocol path).

The protocol path c relates to data format processing, obex (server) protocol, GOEP v1.0 protocol, RFCOMM protocol, and L2CAP protocol. In other words, the address book data is processed by the data format processing, obex (server) protocol, GOEP v1.0 protocol, RFCOMM protocol, and L2CAP protocol, so that the finally obtained communication data packet can meet the requirements of the data format processing, obex (server) protocol, GOEP v1.0 protocol, RFCOMM protocol, and L2CAP protocol.

And secondly, transmitting the address book data packet processed by the protocol path III to the vehicle-mounted terminal.

In this embodiment of the application, the process of the vehicle-mounted terminal receiving the address book synchronization service according to the second PBAP version may be: and the vehicle-mounted terminal decodes the received address book data packet according to the protocol path. Wherein, the protocol path (IV) relates to the L2CAP protocol, the RFCOMM protocol, the GOEP v1.0 protocol, the OBEX (client) protocol and the data format processing.

Obviously, after the protocol path is replaced, because a layer of protocol is introduced, the processing time of the address book data packet is increased. In other words, the demand for the processing speed of the bluetooth device is reduced. The problem that due to the fact that the processing speed of the Bluetooth device is limited, address book synchronization is abnormal is avoided.

In the embodiment of the application, under the condition that the second PBAP version is adopted, whether locomotive disconnection occurs during the address book synchronization service is detected. And if locomotive disconnection occurs during the address book synchronization service period (for example, one locomotive disconnection occurs or N times of continuous locomotive disconnections occur), the mobile phone cancels the marking of the vehicle-mounted terminal. For example, the mobile phone removes the device ID of the in-vehicle terminal from the device information set. For another example, the cause of the service abnormality corresponding to the in-vehicle terminal in the preset table is changed to another cause.

Therefore, when the mobile phone and the vehicle-mounted terminal are connected again next time, the second PBAP version does not need to be adopted continuously, and the protocol version degradation or the protocol change caused by misjudgment is improved.

Of course, in other possible embodiments, in the case of using the second PBAP version, if a locomotive disconnection occurs during the address book synchronization service is detected, it may also be attempted to use other protocol versions commonly supported between the mobile phone and the vehicle-mounted terminal. The principle is similar to changing from the first PBAP version to the second PBAP version, and is not described herein again.

In summary, the method for determining the profile version provided in the embodiment of the present application is suitable for accurately evaluating the supporting effect of the bluetooth devices on the commonly supported highest version of PBAP through the detection of the disconnection of the vehicle in the case of PBAP. And under the condition that the supporting effect of the highest version PBAP supported by the same is not good, the PBAP actually used among the Bluetooth devices is flexibly adjusted. By means of temporarily adjusting or reducing the protocol content, the problem of poor protocol version support effect between Bluetooth devices is solved, and Bluetooth service quality is improved.

In addition, in some possible scenarios, the mobile phone may also be used as a requester of the address book synchronization service, and the vehicle-mounted terminal may be used as a provider of the address book synchronization service. In this possible scenario, the principle of the method for determining the profile version is the same as that described in the foregoing embodiment, and the difference is only the role exchange between the mobile phone and the vehicle-mounted terminal. For example, after the roles are exchanged, the mobile phone may initiate the first SDP request message to the vehicle-mounted terminal, and the vehicle-mounted terminal returns the first SDP response message to the mobile phone. After the mobile phone judges the actual use version of the PBAP, the mobile phone initiates an address book synchronization request to the vehicle-mounted terminal, and the vehicle-mounted terminal sends the address book synchronization request to the mobile phone. For another example, after the roles are interchanged, the mobile phone may initiate a second SDP request message to the vehicle-mounted terminal, and the vehicle-mounted terminal returns a second SDP response message to the mobile phone. So that the handset can determine the actual usage version of PBAP.

In addition, the profile version determination method provided in the embodiment of the present application may be applicable to HFP in addition to PBAP.

Under the condition that the mobile phone and the vehicle-mounted terminal are paired by Bluetooth and support HFP together, the first application service can be a call control service. For convenience of understanding by those in the art, the profile version determination method provided in the embodiment of the present application is described below by taking an in-vehicle terminal as a requester of a call control service and a mobile phone as a provider of the call control service as an example.

As shown in fig. 14, the profile version determining method may include the following steps:

s201, the vehicle-mounted terminal sends first SDP request information to the mobile phone.

In this embodiment of the present application, the first SDP request information may be used to indicate a support capability of the querying handset for at least one profile. It is understood that HFP is included in the at least one profile being queried.

Illustratively, the vehicle-mounted terminal may query all profiles supported by the mobile phone from the mobile phone through the first SDP request message. Thus, in the case that the handset supports HFP, HFP is included in the at least one profile to be queried.

Illustratively, it may be that the in-vehicle terminal specifies the query HFP to the handset through the first SDP request information. Thus, the at least one profile queried is also considered to include HFP.

Of course, in some possible embodiments, it may also be that the in-vehicle terminal has queried all profiles supported by the mobile phone through the SDP request message, and in a case that it is determined that the mobile phone supports HFP, the in-vehicle terminal may directionally query the capability of the mobile phone for supporting HFP through the first SDP request message.

S202, the mobile phone sends first SDP response information to the vehicle-mounted terminal.

The first SDP response information may include the first HFP identifier (i.e., the first identifier). The first HFP identification may be a version number of the highest HFP version supported by the handset.

In this embodiment of the application, when the first SDP request message indicates to query the support capability of the mobile phone for HFP, the mobile phone may determine the highest HFP version that the mobile phone can support according to a server record list maintained therein. Then, a first HFP identification is determined based on the highest HFP version supportable by the handset.

In the embodiment of the present application, the mobile phone sends the first SDP response message to the vehicle-mounted terminal, so that the vehicle-mounted terminal can be instructed to determine the highest HFP version, also referred to as the first HFP version, supported by the mobile phone and the vehicle-mounted terminal according to the highest HFP version supported by the mobile phone and the highest HFP version supported by the vehicle. And determines that the call control service (i.e., the first application service) is implemented using the first HFP version. When the in-vehicle terminal requests the call control service according to the specification of the first HFP version, the mobile phone also provides the call control service to the in-vehicle terminal according to the specification of the first HFP version.

Thus, through S201 and S202, it can be agreed that the first HFP version is adopted to realize the call control service between the in-vehicle terminal and the mobile phone.

Of course, the manner in which the HFP version of the call control service is agreed to be implemented is not limited thereto. In other embodiments, the first SDP request information may include an identifier of a highest HFP version supported by the vehicle-mounted terminal. For example, if the in-vehicle terminal supports HFP1.6 and HFP1.7 is a version higher than HFP1.6, the version number of HFP1.7 may be included in the first SDP request information.

In a case where the identification of the highest HFP version supported by the in-vehicle terminal is included in the first SDP request information, the first HFP version between the in-vehicle terminal and the mobile phone may be determined by the mobile phone. And notifying the vehicle-mounted terminal that the call control service can be requested to the mobile phone by adopting the specification of the first HFP version through the first SDP response message. Thereby enabling an agreement to implement a call control service using the first HFP version.

S203, establishing Bluetooth communication between the mobile phone and the vehicle-mounted terminal.

In some embodiments, it may be a Synchronous Connection Oriented link (SCO) that establishes a Connection between the handset and the in-vehicle terminal.

And S204, the vehicle-mounted terminal sends a call control request to the mobile phone.

In some embodiments, the in-vehicle terminal may transmit a call control request to the handset according to the specification of the first HFP version under the operation of the user to request a call control service.

And S205, under the condition that the mobile phone receives the call control request, providing the call control service for the vehicle-mounted terminal.

In some embodiments, the mobile phone may provide the call control service to the in-vehicle terminal according to the specification of the first HFP version.

And S206, detecting a silent uplink event during the period that the mobile phone provides the call control service.

In the embodiment of the present application, during the period that the mobile phone provides the call control service, whether a silent uplink EVENT occurs may be detected in real time, for example, whether HiFI _ BSD3_0_ EVENT occurs is detected.

In some embodiments, the in-vehicle terminal is flagged after a silent up-stream event is detected. Understandably, the manner of marking the vehicle-mounted terminal may refer to the description in the foregoing embodiments, and is not repeated here.

In other embodiments, in order to improve the fault tolerance rate, the vehicle-mounted terminal may be marked after N silent uplink events are detected. Wherein N is an integer not less than 2.

In some embodiments, the detecting N silent uplink events may be: n silent up-going events are continuously detected on the premise of using the first HFP version. Illustratively, a silent up event may occur during N consecutive bluetooth calls.

For example, after the successful establishment of SCO, if a silent uplink event occurs during the call control service is detected, the number of detected silent uplink events is recorded as 1. Recording the number of detected silent up events as 2 if a silent up event is detected during the call control service under the condition that the SCO is reconnected next time and the first HFP version is still used; if no silent up event is detected during the call control service, the number of detected silent up events is cleared.

In other embodiments, the detecting N silent up events may further comprise: the total number of occurrences of silent up events during the first HFP version is counted. That is, each silent up event occurring during the first HFP version is counted.

And S207, the vehicle-mounted terminal sends second SDP request information to the mobile phone.

In some embodiments, it may be that a mismatch between the mobile phone and the in-vehicle terminal (i.e., disconnection and reconnection of the ACL link) triggers the in-vehicle terminal to send SDP request information to the mobile phone. In other embodiments, the original ACL link may not be disconnected, and the vehicle-mounted terminal may be triggered by the user to send the SDP request message again.

And under the condition that the mobile phone marks the vehicle-mounted terminal, the mobile phone looks at the SDP request information sent by the vehicle-mounted terminal as second SDP request information.

In some embodiments, the above method further comprises:

after receiving the SDP request message sent by the vehicle-mounted terminal, the mobile phone may query whether the vehicle-mounted terminal has the flag, and if the mobile phone queries that the vehicle-mounted terminal has the flag, the flow proceeds to S208, considering that the received SDP request message is the second SDP request message. If the mobile phone inquires that the vehicle-mounted terminal does not have the mark, the received SDP request information is considered as the first SDP request information, and the process flow enters S202.

And S208, the mobile phone sends second SDP response information to the vehicle-mounted terminal.

In the embodiment of the present application, in order to avoid the in-vehicle terminal determining the actually used version again, the selection of the first HFP version is continued. The second SDP response information may include a second identifier, such as the second HFP identifier. The second HFP identifies the version number of the second HFP version. The in-vehicle terminal may be instructed to request the call control service using the second HFP version through the second HFP identification.

The second HFP version is lower than the first HFP version. Therefore, under the condition that the support effect of the first HFP version is poor, the second HFP version is selected as the actual use version, the address book synchronization service quality is improved, and the possibility of disconnection of the vehicle is reduced.

In this embodiment of the present application, in the case of using the second HFP version, if an abnormality still occurs during the call control service (for example, a silent uplink event is detected once, or N silent uplink events are detected), the method further includes: and the mobile phone cancels the marking of the vehicle-mounted terminal. Therefore, after the mobile phone is re-matched with the vehicle-mounted terminal, the second HFP version does not need to be adopted continuously, and protocol version degradation caused by misjudgment is improved.

Of course, in other possible embodiments of the present application, when the second HFP version is adopted, the abnormality still exists in the call control service, and other versions of the protocol supported in common may also be tried. The principle is similar to changing from the first HFP version to the second HFP version, and is not described herein again.

In summary, the profile version determination method provided in the embodiment of the present application is applicable to HFP, and accurately determines the supporting effect of the highest version HFP supported together among bluetooth devices by detecting a silent uplink event. And under the condition that the supporting effect of the highest version HFP supported by the Bluetooth device is not good, the version of the HFP actually used between the Bluetooth devices is flexibly adjusted, so that the Bluetooth service quality between the Bluetooth devices is improved.

In addition, in some possible scenarios, the mobile phone may also be used as a requester of the call control service, and the vehicle-mounted terminal may be used as a provider of the call control service. In this possible scenario, the principle of the method for determining the profile version is the same as that described in the foregoing embodiment, and the difference is only the role exchange between the mobile phone and the vehicle-mounted terminal.

An embodiment of the present application further provides an electronic device, which may include: a memory and one or more processors. The memory is coupled to the processor. The memory is for storing computer program code comprising computer instructions. The processor, when executing the computer instructions, may cause the electronic device to perform the steps performed by the handset in the embodiments described above. Of course, the electronic device includes, but is not limited to, the above-described memory and one or more processors. For example, the structure of the electronic device may refer to the structure of a mobile phone shown in fig. 4.

The embodiment of the present application further provides a chip system, which can be applied to the electronic device in the foregoing embodiments. As shown in FIG. 15, the system-on-chip includes at least one processor 2201 and at least one interface circuit 2202. The processor 2201 may be a processor in the electronic device described above. The processor 2201 and the interface circuit 2202 may be interconnected by wires. The processor 2201 may receive and execute computer instructions from the memory of the electronic device described above via the interface circuit 2202. The computer instructions, when executed by the processor 2201, may cause the electronic device to perform the steps performed by the cell phone in the embodiments described above. Of course, the chip system may further include other discrete devices, which is not specifically limited in this embodiment of the present application.

Through the above description of the embodiments, it is clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional modules is merely used as an example, and in practical applications, the above function distribution may be completed by different functional modules according to needs, that is, the internal structure of the device may be divided into different functional modules to complete all or part of the above described functions. For the specific working processes of the system, the apparatus and the unit described above, reference may be made to the corresponding processes in the foregoing method embodiments, and details are not described here again.

Each functional unit in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be essentially implemented or make a contribution to the prior art, or all or part of the technical solutions may be implemented in the form of a software product stored in a storage medium and including several instructions for causing a computer device (which may be a personal computer, a server, or a network device) or a processor to execute all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: flash memory, removable hard drive, read only memory, random access memory, magnetic or optical disk, and the like.

The above description is only a specific implementation of the embodiments of the present application, but the scope of the embodiments of the present application is not limited thereto, and any changes or substitutions within the technical scope disclosed in the embodiments of the present application should be covered by the scope of the embodiments of the present application. Therefore, the protection scope of the embodiments of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for determining the profile version of an application protocol is characterized by comprising the following steps:

establishing an asynchronous connection ACL link between the electronic equipment and the external equipment;

the external equipment sends Service Discovery Protocol (SDP) request information to the electronic equipment; the SDP request information is used for inquiring the support capability of the electronic equipment on a telephone directory access protocol (PBAP);

the electronic equipment sends first SDP response information to the external equipment; wherein the first SDP response information comprises a first PBAP identifier; the first PBAP identifier is an identifier of the highest PBAP version supported by the electronic equipment;

the external equipment requests address book synchronization service from the electronic equipment by adopting a first PBAP version according to the first PBAP identification and the highest PBAP version supported by the external equipment;

the electronic equipment provides the address book synchronization service for the external equipment according to the first PBAP version;

under the condition that the address book synchronization service is abnormal, the external equipment sends the SDP request information to the electronic equipment;

the electronic equipment sends second SDP response information to the external equipment; wherein the second SDP response information includes a second PBAP identity; the second PBAP identifier comprises a second version number, or comprises a first version number and a specific indicator bit with a second value; the first version number is a version number of the first PBAP version;

the external equipment requests the address book synchronization service to the electronic equipment by adopting a second PBAP version according to the second PBAP identification; wherein the first PBAP version is different from the second PBAP version;

and the electronic equipment provides the address book synchronization service for the external equipment according to the second PBAP version.

2. The method of claim 1,

during the period that the electronic equipment provides the address book synchronization service to the external equipment according to the first PBAP version, the method further comprises the following steps: the electronic equipment judges whether the address book synchronization service is abnormal or not;

3. The method of claim 2, wherein the determining, by the electronic device, whether the address book synchronization service is abnormal comprises:

4. The method of claim 2, wherein the electronic device tagging the external device comprises:

5. The method of claim 1, wherein the first version number is PBAP 1.2; the second version number is PBAP 1.1.

6. The method of claim 1, wherein prior to the requesting address book synchronization services from the electronic device with the first PBAP version, the method further comprises:

7. The method of claim 1, wherein before the electronic device provides the address book synchronization service to the external device according to the first PBAP version, the method further comprises:

8. The method of any of claims 1-7, wherein the electronic device providing the address book synchronization service to the external device according to the first PBAP version comprises:

9. A profile version determination method is applied to an electronic device, an ACL link is established between the electronic device and an external device, and the method comprises the following steps:

10. The method of claim 9,

during the period of providing the address book synchronization service to the external device according to the first PBAP version, the method further comprises the following steps: judging whether the address book synchronization service is abnormal or not;

11. The method of claim 10, wherein the determining whether the address book synchronization service is abnormal comprises:

12. The method of claim 10, wherein said tagging the external device comprises:

13. The method of claim 9, wherein the first version number is PBAP 1.2; the second version number is PBAP 1.1.

14. The method of claim 9, wherein prior to providing the contact synchronization service to the external device in accordance with the first PBAP version, the method further comprises:

15. The method of any of claims 9-14, wherein providing the contact synchronization service to the external device according to the first PBAP version comprises:

16. A profile version determination system, the system comprising: electronic equipment and external equipment; establishing an ACL link between the electronic equipment and the external equipment;

17. The system of claim 16,

the electronic equipment is further configured to determine whether the address book synchronization service is abnormal or not during the period when the electronic equipment provides the address book synchronization service to the external equipment according to the first PBAP version;

18. The system of claim 17, wherein the electronic device is further configured to monitor whether the ACL link to an external device is broken; and when the ACL link is disconnected, determining that the address book synchronization service is abnormal.

19. The system of claim 17, wherein the electronic device is further configured to record a device identifier of the external device, or record a device identifier and an abnormal reason of the external device correspondingly, when N times of the address book synchronization service abnormality is continuously detected; wherein N is an integer not less than 2.

20. The system of claim 16, wherein the first version number is PBAP 1.2; the second version number is PBAP 1.1.

21. The system of claim 16, wherein the external device is further configured to display a first prompt message before the first PBAP version is used to request the address book synchronization service from the electronic device; the first prompt message is used for inquiring whether to request the address book synchronization service;

22. The system of claim 16, wherein before the electronic device provides the address book synchronization service to the external device according to the first PBAP version, the electronic device is further configured to display a second prompt message, where the second prompt message is used to inquire whether to approve the address book synchronization service requested by the external device;

23. The system according to any one of claims 16-22, wherein the electronic device is further configured to provide the address book synchronization service to the external device via a first protocol path; the first protocol path comprises data format processing, an OBEX protocol, a GOEPv2.0 protocol and an L2CAP protocol;

24. An electronic device, comprising one or more processors and one or more memories; the one or more memories coupled to the one or more processors for storing computer program code comprising computer instructions which, when executed by the one or more processors, implement the profile version determination method of any of claims 1-15.

25. A computer storage medium comprising computer instructions that, when executed on an electronic device, cause the electronic device to perform the method of any of claims 1-15.