A cross-terminal video car viewing method and system based on vehicle source context binding

Abstract

This application discloses a cross-platform video car viewing method and system based on vehicle source context binding, comprising: receiving a video car viewing request message generated by a C-end application in response to a user's initiated video car viewing request; the video car viewing request message carrying vehicle source context, which includes at least a store identifier, a user identifier, user attention information, and a target vehicle source identifier; generating a unique video session identifier and establishing a mapping relationship between the video session identifier and the target vehicle source identifier; determining a unique target answering terminal from multiple candidate B-end terminals according to a preset allocation strategy; sending an answering notification to the target answering terminal; retrieving the vehicle source context from the session storage area based on the video session identifier; and displaying vehicle source details based on the target vehicle source identifier. This method improves the connection rate of video car viewing requests and the efficiency of store collaborative processing.

Description

Technical Field

[0001] This application belongs to the field of online vehicle sales technology, specifically involving a cross-platform video car viewing method and system. Background Technology

[0002] With the deep integration of internet technology and the automotive industry, online sales of used cars have become an important transaction channel. Users browsing vehicle details pages through C-end applications to view vehicle images, specifications, inspection reports, pricing information, and financing options has become an essential step before making a purchase decision. To further obtain accurate information about the vehicle's condition, users typically contact dealerships via phone, online instant messaging, or general video conferencing tools to view the vehicle's condition in real time and interact with the salesperson. In these scenarios, how to efficiently connect C-end browsing behavior with B-end explanation services has become a pressing technical problem to be solved in this field.

[0003] Currently, in online used car sales, after browsing vehicle information through consumer applications, users typically contact a dealership by phone, online instant messaging, or a general video call tool to further understand the actual condition of a particular vehicle. However, in this approach, the user's vehicle browsing activity and the video call initiation process are usually independent of each other. Figure 1 As shown, after a salesperson connects the call, they often still need to manually ask the user which car they are looking at, and then manually search for the corresponding vehicle in the store's system using the inventory number, model name, or location information before they can begin the on-site explanation. Therefore, the existing technology has the following drawbacks:

[0004] 1. The reliance on manual interaction for vehicle information transmission leads to inefficiency. When users contact sales via phone or instant messaging, target vehicle information cannot be automatically transmitted to the B-end during the call setup process. After the salesperson connects, they must manually inquire about the vehicle information and search it in the store's system, resulting in a significant time delay between the call connection and the start of the explanation.

[0005] 2. User browsing behavior data cannot be synchronized to the presentation platform. Information such as inspection reports, pricing details, financing options, and vehicle condition details that users focus on while browsing on the consumer (C) side cannot be simultaneously transmitted to the business (B) side during a call. Salespeople need to repeatedly ask users about their concerns during the presentation, resulting in a lack of targeted explanations and low communication efficiency. Summary of the Invention

[0006] This application provides a cross-platform video car viewing method and system based on vehicle source context binding, which solves the problem of low communication efficiency in the prior art.

[0007] Firstly, a cross-platform video car viewing method based on vehicle source context binding, the method comprising:

[0008] The system receives a video car viewing request message sent by a C-end terminal. The video car viewing request message is generated by the C-end terminal in response to a video car viewing request initiated by a user on the vehicle source details page. The video car viewing request message carries the vehicle source context, which includes at least a store identifier, user attention information, and one or more target vehicle source identifiers.

[0009] Generate a unique video session identifier, create a third-party RTC room and establish an association between the video session identifier and the third-party RTC room, establish a mapping relationship between the video session identifier and the target vehicle source identifier, and write the vehicle source context into the session storage area; send the access parameters of the third-party RTC room to the C-end terminal;

[0010] According to the preset allocation strategy, a unique target receiving terminal is determined from multiple candidate B-end terminals;

[0011] A call answering notification is sent to the target receiving terminal. The call answering notification includes at least the video session identifier, vehicle source context, and access parameters of the third-party RTC room, so that the target receiving terminal enters the third-party RTC room according to the access parameters, establishes a two-way video link with the C-end terminal, extracts the target vehicle source identifier from the vehicle source context, and retrieves the target vehicle source details information according to the target vehicle source identifier.

[0012] Optionally, in the above scheme, the vehicle source context may also include user identifier and terminal network status;

[0013] The user attention information includes one or more of the following: browsing page identifier, user dwell time, user click area, and user attention tag.

[0014] Optionally, in the above scheme, after receiving the video car viewing request message generated by the C-end application in response to the user's initiation of a video car viewing request, the method further includes:

[0015] Based on the target vehicle identifier and store identifier, the target vehicle status, store operation status, and store sales online status are determined and verified. After the verification is passed, a unique video session identifier is generated.

[0016] In the above scheme, optionally, when the video car viewing request is a reservation call request, the vehicle source context also includes reservation time information;

[0017] After receiving the request message, a reservation task is generated based on the reservation time information. When the current time arrives at the reservation time, the target vehicle source status, store operation status, and store sales online status are determined based on the target vehicle source identifier and store identifier for verification. After the verification is successful, the video session identifier is generated.

[0018] Optionally, in the above scheme, the method further includes:

[0019] In response to a meeting request from one or more other C-end users based on the same video session identifier, the corresponding third-party RTC room is obtained based on the video session identifier, and the meeting parameters of the third-party RTC room are sent to the multiple C-end terminals so that the multiple C-end terminals can access the same third-party RTC room.

[0020] Optionally, in the above scheme, after sending an answer notification to the target answering terminal, if no answer confirmation message is received from the target answering terminal within a preset time period, the next candidate B-end terminal is selected as the target answering terminal and an answer notification is sent according to a preset allocation strategy.

[0021] Optionally, in the above scheme, after the video call corresponding to the video session identifier ends, the behavior data reported by the C-end application, the behavior data reported by the B-end application, and the communication data returned by the third-party real-time communication service are obtained according to the video session identifier to generate a structured session record.

[0022] The structured session record includes one or more of the following: initiation time, connection time, sales connection identifier, call duration, target vehicle identifier, whether the call was transferred, number of new members, and contact information.

[0023] Optionally, in the above scheme, the method further includes:

[0024] Monitor the network quality of the bidirectional audio and video link;

[0025] When the network quality is detected to be lower than a preset threshold, a weak network degradation strategy is executed. The weak network degradation strategy includes one or more of the following: reducing the video bitrate, reducing the video resolution, switching the bidirectional audio and video link to a unidirectional video plus voice link, or switching to a pure voice link.

[0026] Secondly, a cross-platform video car viewing system based on vehicle source context binding, the system comprising:

[0027] The car viewing request message receiving module is used to receive video car viewing request messages sent by the C-end terminal. The video car viewing request message is generated by the C-end terminal in response to the video car viewing request initiated by the user on the car source details page. The video car viewing request message carries the car source context, which includes at least the store identifier, user attention information, and one or more target car source identifiers.

[0028] Video session identifier generation module: used to generate a unique video session identifier, create a third-party RTC room and establish the association between the video session identifier and the third-party RTC room, establish the mapping relationship between the video session identifier and the target vehicle source identifier, and write the vehicle source context into the session storage area; and send the access parameters of the third-party RTC room to the C-end terminal;

[0029] Target answering terminal determination module: used to determine a unique target answering terminal from multiple candidate B-end terminals according to a preset allocation strategy;

[0030] The call answering notification sending module is used to send a call answering notification to the target answering terminal. The call answering notification includes at least the video session identifier, vehicle source context, and access parameters of the third-party RTC room, so that the target answering terminal can enter the third-party RTC room according to the access parameters, establish a two-way video link with the C-end terminal, extract the target vehicle source identifier from the vehicle source context, and call the target vehicle source details information according to the target vehicle source identifier.

[0031] Thirdly, a computer program product is provided, including a computer program / instruction that, when executed by a processor, implements the steps of the cross-platform video car viewing method based on vehicle source context binding described in the first aspect above.

[0032] Compared with the prior art, this application has at least the following beneficial effects:

[0033] This application achieves decoupling and parallelism between video call link establishment and vehicle source information synchronization by binding the vehicle source context and establishing a mapping relationship between the video call identifier and the target vehicle source identifier during the video call creation stage. When the C-end initiates a video car viewing request, the vehicle source context, including the store identifier, user focus information, and target vehicle source identifier, is written into the session storage area and the access parameters are sent to the C-end terminal. This allows the B-end terminal to directly enter the third-party RTC room and establish a two-way video link with the C-end terminal after receiving the answer notification containing the video call identifier and access parameters. At the same time, the vehicle source context is retrieved from the session storage area based on the video call identifier, and the target vehicle source identifier is automatically extracted to generate and display the vehicle source card. This decouples and parallelizes the establishment of the video call link and the synchronization of vehicle source information, avoiding the cumbersome process of manual confirmation and searching for the target vehicle source after the call is connected in traditional solutions. It significantly shortens the time from connection to start of explanation and improves the sales response efficiency and explanation relevance in video car viewing scenarios.

[0034] Meanwhile, by pre-verifying the vehicle status, store operation status, sales online status, and availability of third-party real-time communication services, and determining a unique target answering terminal based on the terminal's online status, busy / idle status, and preset allocation strategy, system-level single-person answering allocation is achieved. This effectively avoids conflicts caused by multiple terminals responding simultaneously, and improves the connection rate of video car viewing requests and the efficiency of store collaborative processing. Attached Figure Description

[0035] Figure 1 A flowchart illustrating a cross-platform video car viewing method based on vehicle source context binding, as described in the prior art;

[0036] Figure 2 A flowchart illustrating a cross-platform video car viewing method based on vehicle source context binding, as provided in one embodiment of this application;

[0037] Figure 3 A schematic diagram of the system composition involved in the video car viewing method based on cross-end vehicle source context synchronization provided in one embodiment of this application;

[0038] Figure 4 Another flowchart of a cross-platform video car viewing method based on vehicle source context binding is provided as an embodiment of this application;

[0039] Figure 5 This is a flowchart illustrating the abnormal scene handling process in a video car viewing method provided in one embodiment of this application. Detailed Implementation

[0040] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments.

[0041] In one embodiment, such as Figure 2 and Figure 4 As shown, a cross-platform video car viewing method based on vehicle source context binding is provided, the method including:

[0042] Step S1: Receive a video car viewing request message sent by the C-end terminal. The video car viewing request message is generated by the C-end terminal in response to the video car viewing request initiated by the user on the vehicle source details page. The video car viewing request message carries the vehicle source context, which includes at least the store identifier, user attention information, and one or more target vehicle source identifiers.

[0043] Step S1 specifically includes:

[0044] (1): The C-end application receives video viewing requests initiated by users on the vehicle details page. The request can be an instant call request or an appointment call request.

[0045] (2): When a user initiates a request, the C-end application extracts information such as the vehicle source identifier, store identifier, user identifier, user focus information, and terminal network status corresponding to the current vehicle source. The user focus information includes the browsing page identifier, user dwell time, user click area, and user focus tags. If it is a reservation call, the reservation time information is also extracted. The C-end application collects user behavior data on the vehicle source details page through front-end data collection technology, including vehicle source identifier, store identifier, user identifier, and user focus information. User focus tags are user preference information, that is, certain query conditions selected by the user when searching for a vehicle source of interest. For example, preferences such as fuel type, price range, mileage range, low fuel consumption, high range, large space, good comfort, and daily commuting are obtained.

[0046] (3): The C-end application encapsulates the above data into a video car viewing request message and sends it to the business middle platform. The request message includes at least: vehicle source ID, store ID, user ID, call mode identifier, appointment time information, user attention tag set and network status identifier.

[0047] Step S2: Generate a unique video session identifier, create a third-party RTC room and establish an association between the video session identifier and the third-party RTC room, establish a mapping relationship between the video session identifier and the target vehicle source identifier, and write the vehicle source context into the session storage area; send the access parameters of the third-party RTC room to the C-end terminal.

[0048] Step S2 specifically includes:

[0049] (1): After receiving the request message, the business middle platform verifies the vehicle source status, store operation status, store sales online status, and the availability status of the third-party RTC service. For the instant call mode, a video session is created directly after the verification is passed; for the appointment call mode, an appointment task is generated first, and the status verification is performed again when the appointment time arrives.

[0050] (2): The business middle platform generates a unique video session identifier, establishes a mapping relationship between the video session identifier and the target vehicle source identifier, and writes the relevant vehicle source context into the session storage area. For example Figure 3 The diagram shows the connections between C-end applications, B-end applications, business middleware, and third-party RTC services.

[0051] Step S3: Based on the preset allocation strategy, determine the unique target receiving terminal from multiple candidate B-end terminals.

[0052] In step S3, the business platform determines a unique target answering terminal from multiple candidate B-end terminals based on a preset allocation strategy, namely the online status, busy / idle status, duty priority, historical connection rate, vehicle ownership relationship, or appointment scheduling rules of the store sales terminal, so as to realize the single-person answering of the system allocation.

[0053] This can be done in the following way: First, filter candidate B-ends for the corresponding stores based on store identifiers. Then, based on the preset list of answerers for the target stores, sequentially select idle candidate B-ends and perform verification. If the device is idle, a call notification is sent if the condition is met; otherwise, the next answerer is selected. Allocation strategies are also included, but will not be elaborated here.

[0054] Step S4: Send an answer notification to the target receiving terminal. The answer notification includes at least the video session identifier, vehicle source context, and access parameters of the third-party RTC room, so that the target receiving terminal enters the third-party RTC room according to the access parameters, establishes a two-way video link with the C-end terminal, extracts the target vehicle source identifier from the vehicle source context, and retrieves the target vehicle source details information according to the target vehicle source identifier.

[0055] The business platform sends a call answering notification to the target receiving terminal. The call answering notification includes at least a video session identifier and vehicle source context information; the vehicle source context information also includes vehicle source summary information; the vehicle source summary information preferably includes one or more of the following: brand information, vehicle source image, warehouse location information, vehicle model name, and inventory number.

[0056] After receiving a call notification, the B-end application preloads the target vehicle identifier and displays a floating call overlay. Once the sales representative answers the call, the B-end application connects to a third-party RTC service to establish an audio / video link. Simultaneously, it generates a "vehicle source card" based on the vehicle source summary information in the video session. This vehicle source card is used to access the vehicle source details page.

[0057] When a session corresponds to only one target vehicle source, the B-end automatically displays a single vehicle source card; when there are multiple vehicle sources to be explained in the session, the B-end automatically displays a list of vehicle source cards, arranged in a preset order.

[0058] After a salesperson clicks on any vehicle listing card, the system automatically enters the corresponding vehicle details page, displaying basic vehicle information, inspection reports, pricing information, financing options, inspection labels, preparation information, and helpful explanations and tips for users.

[0059] In the aforementioned cross-platform video car viewing method based on vehicle source context binding, the vehicle source context is bound during the video session creation stage, and a mapping relationship is established between the video session identifier and the target vehicle source identifier. When the C-end initiates a video car viewing request, the vehicle source context, including the store identifier, user focus information, and target vehicle source identifier, is written into the session storage area and the access parameters are sent to the C-end terminal. This allows the B-end terminal to directly enter the third-party RTC room and establish a two-way video link with the C-end terminal after receiving the answer notification containing the video session identifier and access parameters. Simultaneously, the vehicle source context is retrieved from the session storage area based on the video session identifier, and the target vehicle source identifier is automatically extracted to generate and display the vehicle source card. This achieves decoupling and parallelism between the establishment of the video call link and the synchronization of vehicle source information, avoiding the cumbersome process of manual confirmation and searching for the target vehicle source after the call is connected in traditional solutions. It significantly shortens the time from connection to start of explanation and improves the sales response efficiency and explanation targeting in video car viewing scenarios.

[0060] In one embodiment, the vehicle source context also includes a user identifier and a terminal network status;

[0061] User attention information includes one or more of the following: page browsing identifiers, user dwell time, user clicked areas, and user attention tags.

[0062] In one embodiment, after receiving the video car viewing request message generated by the C-end application in response to the user's initiation of a video car viewing request, the method further includes:

[0063] Based on the target vehicle identifier and store identifier, the target vehicle status, store operation status, and store sales online status are determined and verified. After the verification is passed, a unique video session identifier is generated.

[0064] In one embodiment, when the video car viewing request is a reservation call request, the vehicle source context also includes reservation time information;

[0065] After receiving the request message, a reservation task is generated based on the reservation time information. When the current time arrives at the reservation time, the target vehicle source status, store operation status, and store sales online status are determined based on the target vehicle source identifier and store identifier for verification. After the verification is successful, the video session identifier is generated.

[0066] In one embodiment, the method further includes: responding to a meeting request from one or more other C-end users based on the same video session identifier; obtaining the corresponding third-party RTC room based on the video session identifier; and sending the meeting parameters of the third-party RTC room to the multiple C-end terminals, so that the multiple C-end terminals can access the same third-party RTC room.

[0067] When multiple C-end users participate in a car viewing together, the business platform sends access parameters to multiple C-end terminals based on the same video session identifier, enabling multiple C-end users to enter the same third-party RTC room and thus share the same video explanation stream from the B-end sales.

[0068] When the B-end switches the current vehicle source, the current vehicle source card, or the current explanation page, the business platform synchronizes one or more of the following with all C-end users in the room: the current vehicle source identifier, the current card number, and the current explanation stage information, to ensure that the display status is consistent across multiple C-end users.

[0069] During the video presentation, the B2B application provides sales staff with supplementary information based on user-focused tags, and supports switching between presentation pages such as exterior, interior, engine compartment, trunk, inspection report, pricing scheme, and financing scheme according to the current presentation content.

[0070] In one embodiment, such as Figure 5 As shown, after sending an answer notification to the target answering terminal, if no answer confirmation message is received from the target answering terminal within a preset time period, the next candidate B-end terminal is selected as the target answering terminal and an answer notification is sent according to a preset allocation strategy.

[0071] In this embodiment, if the target receiving terminal does not answer, rejects, or times out, the service platform will automatically transfer the session to the next candidate B terminal according to the preset routing policy, while maintaining the continuous reuse of the original video session and vehicle source context.

[0072] In one embodiment, when the video call corresponding to the video session identifier ends, the behavior data reported by the C-end application, the behavior data reported by the B-end application, and the communication data returned by the third-party real-time communication service are obtained according to the video session identifier to generate a structured session record.

[0073] The structured session record includes one or more of the following: initiation time, connection time, sales connection identifier, call duration, target vehicle identifier, whether the call was transferred, number of new members, and contact information.

[0074] During a video session, the C-end, B-end, and third-party RTC side upload the running logs to the business platform. After the video session ends, the business platform aggregates the logs from the C-end, B-end, and third-party RTC side, generates a structured session record, and sends it back to the CRM, lead system, or operation analysis system.

[0075] In one embodiment, such as Figure 5 As shown, the method further includes:

[0076] Monitor the network quality of the bidirectional audio and video link;

[0077] When the network quality is detected to be lower than a preset threshold, a weak network degradation strategy is executed. The weak network degradation strategy includes one or more of the following: reducing the video bitrate, reducing the video resolution, switching the bidirectional audio and video link to a unidirectional video plus voice link, or switching to a pure voice link.

[0078] When the system detects that the network quality is lower than a preset threshold, it executes a weak network degradation strategy, including reducing the bit rate, reducing the resolution, switching from two-way video to one-way video with audio, or switching to audio mode but retaining the current vehicle source explanation page.

[0079] When a video session is abnormally disconnected, the terminal recovers status data such as the target vehicle source identifier, the current explanation stage, and the current card number from the session storage area based on the video session identifier, thereby restoring the explanation state to that before the disconnection.

[0080] In one embodiment, a cross-platform video car viewing system based on vehicle source context binding is provided, including:

[0081] The car viewing request message receiving module is used to receive video car viewing request messages sent by the C-end terminal. The video car viewing request message is generated by the C-end terminal in response to the video car viewing request initiated by the user on the car source details page. The video car viewing request message carries the car source context, which includes at least the store identifier, user attention information, and one or more target car source identifiers.

[0082] Video session identifier generation module: used to generate a unique video session identifier, create a third-party RTC room and establish the association between the video session identifier and the third-party RTC room, establish the mapping relationship between the video session identifier and the target vehicle source identifier, and write the vehicle source context into the session storage area; and send the access parameters of the third-party RTC room to the C-end terminal;

[0083] Target answering terminal determination module: used to determine a unique target answering terminal from multiple candidate B-end terminals according to a preset allocation strategy;

[0084] The call answering notification sending module is used to send a call answering notification to the target answering terminal. The call answering notification includes at least the video session identifier, vehicle source context, and access parameters of the third-party RTC room, so that the target answering terminal can enter the third-party RTC room according to the access parameters, establish a two-way video link with the C-end terminal, extract the target vehicle source identifier from the vehicle source context, and call the target vehicle source details information according to the target vehicle source identifier.

[0085] Compared with the prior art, this application has at least the following beneficial technical effects:

[0086] 1. By binding the vehicle source context during the video session creation phase, the audio and video link and the business link are established in an integrated manner, avoiding the need for manual vehicle confirmation again after the connection is established.

[0087] 2. After the call is answered by the B-end, the vehicle source card or a list of vehicle source cards will be automatically displayed, which will significantly shorten the time from the connection to the start of the explanation and improve the sales response efficiency.

[0088] 3. By allowing direct access to the details page via vehicle source cards and linking the display of inspection reports, pricing information, and financing options, the completeness of information and operational efficiency of on-site sales presentations can be improved.

[0089] 4. By synchronizing user-focused tags, the content explained to B-end users is better matched with the content that users are interested in, thereby improving the relevance of the explanations.

[0090] 5. Improve the connection rate of video car viewing requests and the efficiency of store collaborative processing by using the system's assigned single-person answering and automatic call transfer mechanism for unanswered calls.

[0091] 6. By using a multi-person room sharing and current vehicle listing synchronization mechanism, multiple C-end users can collaboratively view vehicles and maintain a consistent display status, enhancing the shared vehicle viewing experience.

[0092] 7. Maintain vehicle source context during weak network degradation and link loss recovery to improve the continuity and stability of the video car viewing process.

[0093] 8. By transmitting structured session data back, a reliable data foundation is provided for subsequent lead generation analysis, service quality assessment, and business optimization.

[0094] This application may also be submitted in the following manner:

[0095] 1. In terms of terminal allocation, in addition to being based on duty priority, it can also be allocated based on idle time, vehicle maintenance ownership, regional polling or appointment scheduling rules.

[0096] 2. In terms of audio and video link configuration, in addition to the third-party RTC room mode, point-to-point call mode or a hybrid mode coordinated by the business middle platform can also be adopted.

[0097] 3. Regarding the transmission method of vehicle source context, in addition to carrying vehicle source summary information in the answer notification, it is also possible to only transmit the video session identifier, and then the B-end can retrieve the complete vehicle source information based on the video session identifier.

[0098] 4. Regarding the generation method of user attention points, it can be generated based on one or more of the following: user click behavior, dwell time, inquiry text, voice input, and historical preference model.

[0099] 5. The vehicle listing can be arranged according to user interest level, vehicle priority, reservation order, or a sales-defined order.

[0100] 6. In scenarios with multiple people in the same room, it can support a fixed display of the main vehicle source, or it can support switching between the main vehicle source and the candidate vehicle source list.

[0101] 7. In the output of the session, in addition to sending back to CRM, it can also automatically generate follow-up tasks, lead priorities, sales quality inspection records or user profile tags.

[0102] The key point of this application is:

[0103] 1. When initiating an instant call or appointment call on the C-end, the target vehicle identifier, store identifier, user identifier, appointment information, and browsing focus points are written into the video session context.

[0104] 2. The business middle platform determines the unique B-end target answering terminal based on the store's online sales status, busy / idle status, and allocation strategy, thereby realizing a single-person answering mechanism allocated by the system.

[0105] 3. After a video call is answered, the B-end automatically displays a vehicle source card or a list of vehicle source cards based on the vehicle source context in the video session, instead of relying on manual search for the target vehicle source.

[0106] 4. Click on the vehicle source card to enter the vehicle source details page, and link to display explanatory and supplementary content such as inspection reports, quotation information, and financing options.

[0107] 5. Organize multiple C-end users to join the same RTC room in the same video session, and synchronize the current vehicle source identification, card number or explanation stage information.

[0108] 6. In scenarios of missed calls, timeouts, rejected calls, weak network conditions, or connection failures, maintain continuous reuse of the same vehicle source context to avoid disconnection between session state and business state.

[0109] 7. After the video session ends, send back a structured report of the initiator, the connection, the explanation, the transfer, the number of new members, and the data collection results.

[0110] In one embodiment, a computer program product is also provided, including a computer program / instructions that, when executed by a processor, implement the steps of the methods described in the embodiments above.

[0111] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

Claims

1. A cross-terminal video look method based on vehicle source context binding, characterized in that, The method includes: The system receives a video car viewing request message sent by a C-end terminal. The video car viewing request message is generated by the C-end terminal in response to a video car viewing request initiated by a user on the vehicle source details page. The video car viewing request message carries the vehicle source context, which includes at least a store identifier, user attention information, and one or more target vehicle source identifiers. Generate a unique video session identifier, create a third-party RTC room and establish an association between the video session identifier and the third-party RTC room, establish a mapping relationship between the video session identifier and the target vehicle source identifier, and write the vehicle source context into the session storage area; send the access parameters of the third-party RTC room to the C-end terminal; According to the preset allocation strategy, a unique target receiving terminal is determined from multiple candidate B-end terminals; A call answering notification is sent to the target receiving terminal. The call answering notification includes at least the video session identifier, vehicle source context, and access parameters of the third-party RTC room, so that the target receiving terminal enters the third-party RTC room according to the access parameters, establishes a two-way video link with the C-end terminal, extracts the target vehicle source identifier from the vehicle source context, and retrieves the target vehicle source details information according to the target vehicle source identifier.

2. The cross-platform video car viewing method based on vehicle source context binding according to claim 1, characterized in that, The vehicle source context also includes user identifier and terminal network status; The user attention information includes one or more of the following: browsing page identifier, user dwell time, user click area, and user attention tag.

3. The cross-platform video car viewing method based on vehicle source context binding according to claim 1, characterized in that, After receiving the video car viewing request message generated by the C-end application in response to the user's initiated video car viewing request, the method further includes: Based on the target vehicle identifier and store identifier, the target vehicle status, store operation status, and store sales online status are determined and verified. After the verification is passed, a unique video session identifier is generated.

4. The cross-platform video car viewing method based on vehicle source context binding according to claim 3, characterized in that, When the video car viewing request is a reservation call request, the vehicle source context also includes reservation time information; After receiving the request message, a reservation task is generated based on the reservation time information. When the current time arrives at the reservation time, the target vehicle source status, store operation status, and store sales online status are determined based on the target vehicle source identifier and store identifier for verification. After the verification is successful, the video session identifier is generated.

5. The cross-platform video car viewing method based on vehicle source context binding according to claim 1, characterized in that, The method further includes: In response to a meeting request from one or more other C-end users based on the same video session identifier, the corresponding third-party RTC room is obtained based on the video session identifier, and the meeting parameters of the third-party RTC room are sent to the multiple C-end terminals so that the multiple C-end terminals can access the same third-party RTC room.

6. The cross-platform video car viewing method based on vehicle source context binding according to claim 1, characterized in that, After sending an answer notification to the target answering terminal, if no answer confirmation message is received from the target answering terminal within a preset time period, the next candidate B-end terminal is selected as the target answering terminal and an answer notification is sent according to a preset allocation strategy.

7. The cross-platform video car viewing method based on vehicle source context binding according to claim 1, characterized in that, When the video call corresponding to the video session identifier ends, the behavior data reported by the C-end application, the behavior data reported by the B-end application, and the communication data returned by the third-party real-time communication service are obtained according to the video session identifier to generate a structured session record. The structured session record includes one or more of the following: initiation time, connection time, sales connection identifier, call duration, target vehicle identifier, whether the call was transferred, number of new members, and contact information.

8. The cross-platform video car viewing method based on vehicle source context binding according to claim 1, characterized in that, The method further includes: Monitor the network quality of the bidirectional audio and video link; When the network quality is detected to be lower than a preset threshold, a weak network degradation strategy is executed. The weak network degradation strategy includes one or more of the following: reducing the video bitrate, reducing the video resolution, switching the bidirectional audio and video link to a unidirectional video plus voice link, or switching to a pure voice link.

9. A cross-platform video car viewing system based on vehicle source context binding, characterized in that, The system includes: The car viewing request message receiving module is used to receive video car viewing request messages sent by the C-end terminal. The video car viewing request message is generated by the C-end terminal in response to the video car viewing request initiated by the user on the car source details page. The video car viewing request message carries the car source context, which includes at least the store identifier, user attention information, and one or more target car source identifiers. Video session identifier generation module: used to generate a unique video session identifier, create a third-party RTC room and establish the association between the video session identifier and the third-party RTC room, establish the mapping relationship between the video session identifier and the target vehicle source identifier, and write the vehicle source context into the session storage area; and send the access parameters of the third-party RTC room to the C-end terminal; Target answering terminal determination module: used to determine a unique target answering terminal from multiple candidate B-end terminals according to a preset allocation strategy; The call answering notification sending module is used to send a call answering notification to the target answering terminal. The call answering notification includes at least the video session identifier, vehicle source context, and access parameters of the third-party RTC room, so that the target answering terminal can enter the third-party RTC room according to the access parameters, establish a two-way video link with the C-end terminal, extract the target vehicle source identifier from the vehicle source context, and call the target vehicle source details information according to the target vehicle source identifier.

10. A computer program product, comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by the processor, they implement the steps of the method described in claims 1-8.

Images