Object information processing method and device, equipment and medium

Abstract

The invention provides an object information processing method and device, equipment and a medium. The method comprises the steps of determining a request processing queue associated with a target request object, obtaining queue processing parameters associated with the request processing queue, and obtaining M object information obtaining requests to be subjected to request merging from N object information obtaining requests based on the queue processing parameters, determining M virtual business objects which send the M object information acquisition requests as merging processing virtual objects, performing request merging processing on the M object information acquisition requests to obtain a merging processing request, and obtaining first object information of a first virtual object based on the merging processing request, and determining the first object information as object information of the target request object, and generating a request data packet for being sent to the merge processing virtual object based on the object information of the target request object. According to the application, when the virtual object requests to obtain the object information, the processing resource consumption of the server can be reduced.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to an object information processing method, apparatus, device, and medium. Background Art

[0002] In an online game, when a character (such as character A) moves, the field of view of character A changes. When a character (such as character B) appears in the newly added field of view of character A, character B needs to request character A's character information from the server.

[0003] However, the inventors discovered in practice that when there are multiple characters B, each of these characters B will send a request to the server to pull information about character A. For example, in a gaming scenario, a large number of characters are gathered together. At this time, when character A moves, multiple characters B may appear simultaneously within the newly added field of view. In this case, the server will obtain the object information of character A once for each information pull request from character B. In other words, when the server receives too many information pull requests, it needs to perform a large number of character information pull operations, consuming a large amount of server processing resources and easily leading to issues such as slow server response and lag. Summary of the Invention

[0004] Embodiments of the present application provide an object information processing method, apparatus, device, and medium, which can reduce the processing resource consumption of a server when a virtual object requests to obtain object information.

[0005] In one aspect, an embodiment of the present application provides an object information processing method, which is executed by a service server and includes:

[0006] Determining a request processing queue associated with a target request object; the request processing queue includes N object information acquisition requests, where N is a positive integer greater than 1, and each object information acquisition request is a request sent by a virtual business object to obtain object information of the target request object; wherein, if the target request object is a first virtual object, the virtual business objects include virtual objects within a field of view change range of the first virtual object, where the field of view change range refers to a range determined by the business server when detecting that the object field of view range of the first virtual object has changed from a first field of view range to a second field of view range;

[0007] Obtaining queue processing parameters associated with a request processing queue, obtaining M object information acquisition requests to be merged from the N object information acquisition requests based on the queue processing parameters, and determining the M virtual business objects that sent the M object information acquisition requests as merged virtual objects; where M is a positive integer less than or equal to N;

[0008] Performing request merging processing on the M object information acquisition requests to obtain a merged processing request, obtaining first object information of the first virtual object based on the merged processing request, and determining the first object information as the object information of the target request object;

[0009] Based on the object information of the target request object, a request data packet is generated for sending to the merged processing virtual object.

[0010] In one aspect, an embodiment of the present application provides an object information processing device, which runs on a service server and includes:

[0011] a queue determination module, configured to determine a request processing queue associated with a target request object; the request processing queue includes N object information acquisition requests, where N is a positive integer greater than 1, and each object information acquisition request is a request sent by a virtual business object to obtain object information of the target request object; wherein, if the target request object is a first virtual object, the virtual business objects include virtual objects within a field of view change range of the first virtual object, where the field of view change range is determined by the business server upon detecting that the object field of view range of the first virtual object has changed from a first field of view range to a second field of view range;

[0012] a request acquisition module, configured to acquire queue processing parameters associated with a request processing queue, acquire M object information acquisition requests to be merged from the N object information acquisition requests based on the queue processing parameters, and determine the M virtual business objects that sent the M object information acquisition requests as merged virtual objects; M is a positive integer less than or equal to N;

[0013] an information acquisition module, configured to perform request merging processing on the M object information acquisition requests to obtain a merged processing request, obtain first object information of the first virtual object based on the merged processing request, and determine the first object information as the object information of the target requested object;

[0014] The data processing module is used to generate a request data packet for sending to the merged processing virtual object based on the object information of the target request object.

[0015] In one aspect, an embodiment of the present application provides a computer device, including a memory and a processor, wherein the memory is connected to the processor, the memory is used to store a computer program, and the processor is used to call the computer program so that the computer device executes the method provided in the above aspect of the embodiment of the present application.

[0016] On one hand, an embodiment of the present application provides a computer-readable storage medium, in which a computer program is stored. The computer program is suitable for being loaded and executed by a processor, so that a computer device with a processor executes the method provided in the above aspect of the embodiment of the present application.

[0017] According to one aspect of the present application, a computer program product is provided, which includes a computer program. When the computer program is executed by a processor, it implements the method provided in any of the above aspects of the embodiments of the present application.

[0018] In an embodiment of the present application, a request processing queue associated with a target request object may be determined. The request processing queue includes N object information acquisition requests, each of which is used by a virtual business object to request object information about the target request object. When the target request object is a first virtual object, the virtual business objects may include virtual objects within a change in the field of view of the first virtual object when the first virtual object moves. At this time, the queue processing parameters can be obtained, and based on the queue processing parameters, M object information acquisition requests to be merged are obtained from the N object information acquisition requests, and the M virtual business objects corresponding to the M object acquisition requests are determined as merged processing virtual objects. When the M object information acquisition requests are merged and the merged processing request is obtained, the object information of the target request object can be determined once based on the merged processing request to generate a request data packet for sending to the merged processing virtual object. In other words, for M object information acquisition requests, it is only necessary to obtain the object information of the target request object once, that is, multiple object information acquisition requests for the same virtual object sent by different virtual business objects can be merged and responded to at the same time. When M is greater than 1, this can reduce the number of times the business server performs role information acquisition operations, thereby reducing the server's processing resource consumption when the virtual object requests to obtain object information. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the description of the embodiments. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0020] Figure 1 This is a schematic diagram of a network architecture provided by an embodiment of the present application;

[0021] Figure 2 This is a schematic diagram of a scene of changing the field of view of an object provided in an embodiment of the present application;

[0022] Figure 3 This is a schematic diagram of an object information acquisition process provided by an embodiment of the present application;

[0023] Figure 4This is a flowchart of an object information processing method provided in an embodiment of the present application;

[0024] Figure 5 This is a schematic diagram of a movement scene of a virtual object provided in an embodiment of the present application;

[0025] Figure 6 This is a schematic diagram of another movement scene of a virtual object provided in an embodiment of the present application;

[0026] Figure 7 This is a schematic diagram of another movement scene of a virtual object provided in an embodiment of the present application;

[0027] Figure 8 This is a schematic diagram of an acquisition process of an object information acquisition request provided in an embodiment of the present application;

[0028] Figure 9 This is a flowchart of another object information processing method provided by an embodiment of the present application;

[0029] Figure 10 This is a schematic diagram of a request processing queue provided in an embodiment of the present application;

[0030] Figure 11 is a schematic diagram of another request processing queue provided in an embodiment of the present application;

[0031] Figure 12 This is a schematic diagram of another request processing queue provided in an embodiment of the present application;

[0032] Figure 13 This is a schematic diagram of a process for obtaining object information provided by an embodiment of the present application;

[0033] Figure 14 This is a schematic diagram of a scenario for obtaining object information provided by an embodiment of the present application;

[0034] Figure 15 is a structural diagram of an object information processing device provided in an embodiment of the present application;

[0035] Figure 16 It is a structural diagram of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0036] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0037] See Figure 1 , Figure 1 This is a network architecture diagram provided by an embodiment of the present application. Figure 1 As shown, the network architecture may include a service server 100 and a service terminal cluster, wherein the service terminal cluster may include one or more service terminals (such as user terminals), and the number of service terminals in the service terminal cluster is not limited here. Figure 1 As shown, the multiple business terminals in the business terminal cluster may specifically include: business terminal 200a, business terminal 200b, ..., business terminal 200n, wherein there may be a communication connection between the business terminal clusters, for example, there is a communication connection between business terminal 200a and business terminal 200b, and there is a communication connection between business terminal 200a and business terminal 200n. At the same time, any business terminal in the business terminal cluster may have a communication connection with the business server 100, so that each business terminal in the business terminal cluster can exchange data with the business server 100 through the communication connection, for example, there is a communication connection between business terminal 200a and business server 100. The above-mentioned communication connection does not limit the connection method, and may be directly or indirectly connected through a wired communication method, or directly or indirectly connected through a wireless communication method, or through other methods, which are not limited in this application.

[0038] It should be understood that Figure 1 Each service terminal in the service terminal cluster shown can be installed with a client for controlling virtual objects (such as game characters, etc.). When the client runs in each service terminal, it can be respectively connected to the above Figure 1 The client can be any type of client, such as a social client, a text processing client, an instant messaging client (e.g., a conference client), an entertainment client (e.g., a game client, a live broadcast client), an information client (e.g., a news client), a shopping client, an in-vehicle client, a multimedia client, or any other client capable of displaying text, images, audio, video, or other data information. The specific type of client is not limited herein.

[0039] For example, the data exchange process between service terminal 200a and service server 100 is described here, using a game client as an example. A game client is a client capable of instantly sending and receiving internet messages and having information search capabilities. The game character controlled by the game client in service terminal 200a can send an object information acquisition request to service server 100. This object information acquisition request is used to obtain object information of the game character controlled by the game client in service terminal 200b. After determining the request packet corresponding to the object information acquisition request according to the technical solution of this application, service server 100 returns it to the game client in service terminal 200a.

[0040] It is understood that the computer device involved in the embodiments of the present application may be a server (for example, Figure 1 The service server 100 shown in FIG. 1 may also be a terminal (eg, Figure 1 Any business terminal in the business terminal cluster shown). Among them, the server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), as well as basic cloud computing services such as big data and artificial intelligence platforms. The terminal can be a smart phone, tablet computer, laptop computer, desktop computer, smart speaker, smart watch, vehicle-mounted terminal, aircraft, etc., but is not limited to this. The embodiments of the present invention can be applied to various scenarios, including but not limited to cloud technology, artificial intelligence, smart transportation, assisted driving, etc.

[0041] It is understandable that Figure 1 It is only an example to characterize the possible network architecture of the technical solution of the present application, and does not limit the specific architecture of the technical solution of the present application, that is, the technical solution of the present application can also provide other forms of network architecture.

[0042] Next, the technical terms involved in the technical fields to which the solutions of the embodiments of the present application may be applied are introduced:

[0043] 1. Virtual scene:

[0044] The scene provided (or displayed) by the client when running on the terminal, the virtual scene refers to the scene created for virtual objects to carry out activities. The virtual scene can be a two-dimensional virtual scene, a 2.5-dimensional virtual scene or a three-dimensional virtual scene, etc. The virtual scene can be a simulation scene of the real world, a semi-simulation and semi-fictional scene, or a purely fictional scene. The virtual scene can include a scene map (also referred to as a map), and the scene map can include a variety of scene models. For example, the various scene models can be castles, railings, stairs, walls, trees, aircraft, and oceans, etc. For ease of description, the scene map in the game scene can also be called a game map. It can be understood that the virtual scene can also be called a virtual space, or a business space, which is not limited here.

[0045] 2. Virtual Objects

[0046] A virtual object refers to a virtual character that is controlled and movable by a user in a virtual scene. The movable virtual character can be a virtual person, a virtual animal, an animated character, etc. The virtual scene includes multiple virtual objects, each of which has its own shape and volume in the virtual scene and occupies a portion of the space in the virtual scene. Optionally, the virtual object is a character controlled by operations on the client. For example, a user (also referred to as a business object, player, etc.) can control the virtual object through peripheral components (such as a keyboard, mouse, handle, etc.) or by clicking on a touch screen display; alternatively, the virtual object can be a non-player character (NPC) set in the virtual scene. Optionally, the number of virtual objects in the virtual scene is preset or dynamically determined based on the number of clients joining the virtual scene. This embodiment of the present application does not limit this. It is understandable that each virtual object has its own shape and volume in the virtual scene and occupies a portion of the space in the virtual scene. Exemplarily, when the virtual scene is a three-dimensional virtual scene, the virtual object is a three-dimensional model created based on animation skeleton technology.

[0047] Non-Player Character (NPC): An object that is pre-set by the developer in a specific virtual scene and is not controlled by the player. The non-player controlled character may also have its own shape and volume in the virtual scene, occupying a portion of the space in the virtual scene. It is understandable that in an embodiment of the present application, the first virtual object and the second virtual object may refer to a virtual pair that can be controlled by the business object (i.e., the user) (such as a first type of virtual object), or may be an object (such as an NPC) that is not controlled by the user (such as a second type of virtual object). For example, when the first virtual object, which is a first type of virtual object, moves, it enters the object field of the second virtual object, which is also a first type of virtual object, then the first virtual object may request the object information of the second virtual object from the business server, and the second virtual object may request the object information of the first virtual object from the business server.

[0048] For another example, when a first virtual object, which is a first type virtual object, moves, it enters the object field of view of a second virtual object, which is a second type virtual object, then the first virtual object can request object information of the second virtual object from the service server.

[0049] For example, if a first virtual object, which is a second-type virtual object, moves and enters the field of view of a second virtual object, which is a first-type virtual object, the second virtual object can request object information from the service server. For ease of explanation, this example assumes that both the first and second virtual objects are first-type virtual objects.

[0050] 3. Field of view:

[0051] Each virtual object has a certain object field of view within the virtual scene in which it resides. For example, in a game scene, the object field of view refers to the area of ​​the game world that the player-controlled game character can see within the game scene. A virtual scene is divided into multiple virtual sub-areas, and the object field of view of a virtual object can be a virtual area composed of multiple virtual sub-areas. In other words, a virtual object (virtual object A) can only see information within the object field of view. When the object field of view of virtual object A changes, virtual object A needs to request the business server to retrieve the object information of virtual objects within the changed field of view. For example, virtual object B within the changed field of view is a newly added virtual object within the object field of view of virtual object A. Virtual object A needs to request the business server to retrieve the object information of virtual object B. In this case, it can be understood that during the movement of virtual object A, virtual object B entered the object field of view of virtual object A. Similarly, at this time, virtual object A also entered the object field of view of virtual object B, and virtual object B also needs to request the business server to retrieve the object information of virtual object A.

[0052] The virtual sub-areas in the virtual scene may be divided into a specified number of virtual sub-areas (around), such as dividing a virtual scene into 100 virtual sub-areas of equal size. Alternatively, the virtual sub-areas may be divided into specified sizes. For example, the virtual scene may be divided into multiple virtual sub-areas of preset sizes. The virtual sub-areas may be of any shape, such as a square, hexagon, or circle, etc. This is not limited here.

[0053] For example, Figure 2 As shown, Figure 2 : This is a schematic diagram of a scene change of an object's field of view provided by an embodiment of the present application; wherein the virtual scene is divided into multiple virtual sub-areas, each of which is a square, and the field of view management rule is to use the adjacent virtual sub-areas of the target virtual sub-area (the virtual sub-area where the virtual object a1 is located) and the target virtual sub-area as multiple virtual sub-areas within the field of view of the target virtual object (for example, 9 virtual sub-areas are obtained, as shown in FIG. Figure 2 The virtual object a1 and the virtual objects b1-b3 in the area 20a are visible to each other (i.e., the virtual object a1 and the virtual objects b1-b3 are within their respective object fields of view), and the virtual object a1 and the virtual objects b4-b7 in the remaining virtual sub-areas outside the area 20a are not visible to each other.

[0054] When virtual object a1 (the first virtual object) moves and its field of view changes, the virtual objects visible to virtual object a1 also change. For example, when virtual object a1 crosses virtual object sub-areas, from virtual object sub-area 20b to virtual object sub-area 20c, the field of view of virtual object a1 changes from the first field of view indicated by area 20a to the second field of view indicated by area 20d. The newly added field of view of the second field of view compared to the first field of view can serve as the field of view change range of virtual object a1 (i.e., the field of view indicated by the virtual sub-areas in area 20d that do not belong to area 20a). At this time, virtual objects b5-b6 are the second virtual objects within the field of view change range of virtual object a1. In other words, virtual object a1 enters the field of view range of virtual objects b5-b6, and virtual objects b5-b6 enter the field of view range of virtual object a1. In other words, virtual objects b5-b6 need to request object information from the service server for virtual object a1, and virtual object a1 needs to request object information from the service server for virtual objects b5-b6.

[0055] It can be understood that virtual objects b5-b6 are newly added virtual objects to virtual object a1, and virtual object a1 is newly added virtual objects to virtual objects b5-b6. The service server will notify virtual object a1 that virtual objects b5-b6 have entered the object field of view of virtual object a1, and will also notify virtual objects b5-b6 that virtual object a1 has entered the object field of view of virtual objects b5-b6.

[0056] It can be understood that at this point, virtual objects b1 and b2 are considered to have left the field of view of virtual object a1. Accordingly, virtual object a1 is considered to have left the field of view of virtual objects b1 and b2. Therefore, the service server notifies virtual object a1 that virtual objects b1-b2 have left the field of view of virtual object a1, and also notifies virtual objects b1-b2 that virtual object a1 has left the field of view of virtual objects b1-b2.

[0057] In other words, at this point, the client of virtual objects b5-b6 will generate an object information acquisition request for virtual object a1 as needed. Based on this object information acquisition request, the service server can retrieve and package the object information of virtual object a1, resulting in a request data packet that is returned to virtual objects b5-b6. Similarly, the client of virtual object a1 will generate an object information acquisition request for virtual objects b5-b6 as needed. Based on this object information acquisition request, the service server can retrieve and package the object information of virtual objects b5-b6, resulting in a request data packet that is returned to virtual object a1.

[0058] For example, in the case of virtual objects b5 and b6 requesting object information from the service server for virtual object a1, virtual object b5 generates an object information acquisition request 21q for virtual object a1. The service server adds object information acquisition request 21q to request processing queue 20A associated with virtual object a1. Virtual object b6 generates an object information acquisition request 22q for virtual object a1. The service server adds object information acquisition request 22q to request processing queue 20A associated with virtual object a1. It will be appreciated that the service server can add each object information acquisition request for virtual object a1 to request processing queue 20A whenever it receives one.

[0059] Similarly, virtual object a1 generates an object information acquisition request X for virtual object b5. The business server adds object information acquisition request X to request processing queue X associated with virtual object b5. Virtual object a1 generates an object information acquisition request Y for virtual object b6. The business server adds object information acquisition request Y to request processing queue Y associated with virtual object b6. In other words, whenever the business server receives an object information acquisition request for a virtual object, it adds the object information acquisition request to the request processing queue associated with the corresponding virtual object.

[0060] For another example, the multiple virtual sub-areas into which the virtual scene is divided may also be in other shapes, such as hexagons.

[0061] It is understood that there is no limitation on the method for determining the virtual sub-areas constituting the virtual area indicated by the object field of view of the virtual object. For example, it may be the virtual sub-area where the virtual object is located and all adjacent virtual sub-areas, or it may be the virtual sub-area where the virtual object is located and adjacent virtual sub-areas corresponding to the direction of the virtual object.

[0062] It can be understood that in this solution, object information acquisition requests requesting object information of the same virtual object are merged and processed through the request processing queue, thereby reducing the number of times the object information of the virtual object is acquired and packaged, thereby reducing server resource consumption.

[0063] For example, Figure 3 As shown, Figure 3 : This is a schematic diagram of an object information acquisition process provided by an embodiment of the present application; wherein, taking the process of acquiring object information of a virtual object a1 (i.e., the target request object, which belongs to the first virtual object when the virtual object a1 moves and the object field of view changes) as an example, the business server determines a request processing queue 50A associated with the virtual object a1, and the request processing queue 50A includes N object information acquisition requests (requests 51q-5nq), which may include the above Figure 4In the example shown, the object information acquisition request 21q sent by the virtual object b5, the object information acquisition request 22q sent by the virtual object b6, and the like, and the queue processing parameter 50a associated with the request processing queue 50A can be obtained. Based on the queue processing parameter 50a, M object information acquisition requests (requests 51p-5mp) to be merged are obtained from the N object information acquisition requests. At this time, M virtual objects that send M object information acquisition requests (that is, the M virtual objects at this time include the second virtual object for the virtual object a1) will be sent. It can be understood that if the M object information acquisition requests include the object information acquisition request 2 1q, then the M second virtual objects include virtual object b5; if the M object information acquisition requests include object information acquisition request 22q, then the M second virtual objects include virtual object b6) determined as the merged processing virtual object 51a for virtual object a1, the M object information acquisition requests are merged to obtain a merged processing request 52a, and the object information 53a of the virtual object a1 is obtained based on the merged processing request 52a, and the object information of the virtual object a1 is determined as the object information of the target request object. Based on the object information of the target request object, a request data packet 54a is generated for sending to the merged processing virtual object.

[0064] It is understandable that the embodiments of the present application can be applied to game scenes, that is, the virtual scenes (also called business space, virtual space) in the embodiments of the present application can be virtual game spaces. The game can be a traditional game or a cloud game. Accordingly, the client running on the terminal device can be an application client for a traditional game or an application client for a cloud game. At this time, the virtual object can be a game character controlled by the user. There can be other game characters within the field of view of the game character, and the character information of other game characters can be pulled up to the business server. Among them, the biggest difference between cloud games and traditional games is the location of game processing and rendering. Traditional games require the game software to be installed on the user's terminal device, and the game processing and rendering tasks are completed locally by the terminal device; while cloud games hand over all the game processing and rendering tasks to the cloud server, and transmit the game screen and sound to the terminal device via the Internet. Accordingly, the game scene (i.e., virtual scene) can include a corresponding scene map, also called a game map. It is understandable that the user can have one or more controllable virtual objects in the game, and then the user can control the corresponding virtual object through an external device (such as a mouse, keyboard, handle, etc.) or by clicking on the touch screen, such as controlling the movement of the corresponding virtual object in the game scene, etc. For the sake of illustration, the following describes this solution using the application in a gaming scenario as an example.

[0065] It is understandable that the game in the embodiment of the present application can be a variety of types of games. The game can be an online game, also known as an online game, which generally refers to an electronic game in which multiple players interact and entertain each other through a computer network. For example, the game can be an action game (Action Game), which is a type of electronic game that emphasizes the player's reaction ability and hand-eye coordination. There are often multiple skills that are released in a continuous manner to form a combo. For example, the game can be a role-playing game (RPG), in which players play one or more team members in a virtual world and play the game in a specific scenario. Usually, this type of game is played by players playing adventurers roaming in the game world, and the various encounters along the way (such as fighting, talking, meeting important people, etc.) are the key to the growth of the player's character and the progress of the game. Optionally, the game can also be a shooting game (FPS), a multiplayer online battle arena (MOBA), etc., which are not limited here.

[0066] Cloud gaming, also known as gaming on demand, is an online gaming technology based on cloud computing. Cloud gaming technology enables thin clients with relatively limited graphics and data processing capabilities to run high-quality games. Players' terminal devices do not need powerful graphics and data processing capabilities; they only need basic streaming capabilities and the ability to receive player input and transmit it to a cloud server. When users experience cloud gaming, they essentially manipulate the cloud game's audio and video streams. For example, input event data is generated through touchscreens, keyboards, mice, joysticks, and other means. This data is then transmitted over the network to a virtual cloud client on the server. The cloud virtual client then processes the events and renders the game screen. The server then generates video stream data based on the game screen generated by the cloud virtual client and transmits it to the application client on the terminal device for display, achieving the purpose of operating the cloud game.

[0067] It is understood that embodiments of the present application can also be applied to virtual social scenarios, where objects can appear as virtual avatars. The virtual avatars here can be either pre-configured avatars based on the object's needs, for example, by selecting appropriate image resources (e.g., virtual wearable items, makeup, hairstyles, etc.) from an image resource library, or reconstructed based on the object's real image to fit the object, such as a virtual avatar rendered by a rendering engine on an application client based on collected real-world object data (e.g., the object's face shape, hairstyle, clothing, etc.). A virtual social scenario refers to a 3D (short for Three Dimensions) virtual space based on the future internet, with connected perception and sharing features, enhanced by virtual reality, or an interactive, immersive, and collaborative world. Just as the physical universe is a series of spatially interconnected worlds, a virtual social scenario can also be considered a collection of many worlds. It is understood that a virtual object is a virtual avatar corresponding to a user. For example, the virtual social scene is a cloud conference scene, and the virtual objects can be people participating in the cloud conference. There may be other people in the field of view of the people participating in the cloud conference, and the personnel information of other people can be pulled up to the business server. It is understandable that in some virtual social scenes, corresponding scene maps can also be included, which can also be called virtual social maps. On the virtual social map, virtual objects can also move.

[0068] It is understandable that the embodiments of the present application can also be applied to navigation scenarios, virtual reality (VR) scenarios, and the like. For example, in a navigation scenario (such as autonomous driving, in-car navigation, mobile phone navigation, etc.), the scene map can be a navigation map, and the virtual objects in the navigation scene can be objects used to represent the user's position (that is, the user can control the movement of the corresponding virtual objects in the navigation map by moving in the real space. For example, if the virtual object is a vehicle, there can be vehicles within the field of view during vehicle driving, and vehicle information of other vehicles can be pulled up to the business server). For another example, in a virtual reality (VR) scenario, the scene map can be a virtual reality map, which can also include virtual objects that can be controlled by the user. The relevant description can refer to the relevant description of the virtual game map above, which will not be repeated here.

[0069] It should be noted that when the business server in the embodiment of the present application obtains the account information of the user corresponding to the virtual object, a prompt interface or pop-up window can be displayed on the corresponding client. The prompt interface or pop-up window is used to prompt the application object that it is currently collecting identity information, client account and other data. Only after the user confirms the prompt interface or pop-up window (such as the user confirms the authorization through the client), the relevant steps for data acquisition are started, otherwise it ends.

[0070] In addition, it can be understood that in the specific implementation of this application, account information and other data related to users and other objects may be involved. When the above embodiments of this application are applied to specific products or technologies, it is necessary to obtain the permission or consent of users and other application objects, and the collection, use and processing of relevant data need to comply with relevant laws, regulations and standards of the relevant regions.

[0071] It is understood that the above scenarios are merely examples and do not limit the application scenarios of the technical solutions provided in the embodiments of this application. The technical solutions of this application can also be applied to other scenarios. For example, those skilled in the art will appreciate that with the evolution of system architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application will also be applicable to similar technical problems.

[0072] For further information, see Figure 4 , Figure 4 This is a flow chart of an object information processing method provided by an embodiment of the present application, such as Figure 4 As shown, the method can be executed by the computer device mentioned above, and the computer device can be a business server, for example, the business server can be the above-mentioned Figure 1 The service server 100 shown in FIG. The method may specifically include the following steps S101 to S104:

[0073] S101: Determine a request processing queue associated with a target request object.

[0074] The request processing queue includes N object information acquisition requests, where N is a positive integer greater than 1. Each object information acquisition request is sent by a virtual business object to obtain object information of a target request object. Specifically, each object information acquisition request is sent by a client corresponding to a virtual business object to a business server to obtain object information of a target request object.

[0075] It is understood that each virtual object may be associated with a request processing queue for storing object information acquisition requests for that virtual object. Whenever the service server receives an object information acquisition request for a virtual object, it adds the object information acquisition request to the request processing queue associated with the corresponding virtual object. The object information acquisition request is used to instruct the acquisition of object information for a particular virtual object.

[0076] The object information may be information required to initially retrieve a virtual object, or information related to rendering and displaying the virtual object in the current virtual scene. For example, if the virtual object is a game character, the object information may include the character's image, clothing, level, health, team, etc. The specific type of object information is not limited herein.

[0077] It is understood that a virtual object can be either a first virtual object or a second virtual object. A first virtual object refers to an object that moves and changes its field of view. A second virtual object refers to a virtual object within the field of view change range of a virtual object. It is understood that the field of view change range is a field of view that falls within the second field of view but not the first field of view.

[0078] It is understandable that a target request object can be either a first virtual object or a second virtual object. That is, when the target request object is the first virtual object, the virtual business object may include a virtual object within the field of view change range of the first virtual object (i.e., the second virtual object corresponding to the first virtual object). Similarly, when the target request object is the second virtual object, the virtual business object may include a virtual object with a field of view change range and the target request object within the field of view change range (i.e., the first virtual object corresponding to the second virtual object). That is, if the virtual business object includes a virtual object whose field of view range has changed and the field of view change range has been determined, then the target request object is the second virtual object within the field of view change range of the virtual business object.

[0079] For example, a business server can detect the movement of virtual object A. Upon detecting that the object field of view of virtual object A has changed from a first field of view to a second field of view, the business server determines the newly added field of view of the second field of view relative to the first field of view as the field of view change range of the virtual object. In this case, virtual object A can be referred to as the first virtual object. In other words, virtual object A is the first virtual object when it serves as the target request object, and the virtual business object requesting object information for virtual object A is the virtual object within the field of view change range of virtual object A. For another example, a business server can detect the movement of virtual object B. Upon determining the field of view change range of virtual object B, and if virtual object A exists within the field of view change range, virtual object B needs to request object information for virtual object A. In this case, virtual object A is the second virtual object when it serves as the target request object, and the virtual business object requesting object information for virtual object A is the first virtual object with a field of view change range, i.e., virtual object B.

[0080] It can be understood that each virtual object in the virtual scene can be in a moving state, that is, when a virtual object serves as a first virtual object, it can also serve as a second virtual object corresponding to another virtual object.

[0081] That is, if the target request object is a first virtual object, the virtual business object includes the virtual objects within the field of view change range of the first virtual object. Similarly, if the target request object is a second virtual object, the virtual business object refers to the virtual object corresponding to the field of view change range of the second virtual object.

[0082] It is understood that when there are multiple second virtual objects within the field of view change range of a first virtual object (virtual object A), each of these multiple second virtual objects will request the service server to pull the object information of virtual object A. Correspondingly, when the second virtual objects within the field of view change range of multiple first virtual objects all include virtual object B, each of these multiple first virtual objects will request the service server to pull the object information of virtual object B.

[0083] That is to say, the business server may receive a large number of object information acquisition requests for virtual object A and a large number of object information acquisition requests for virtual object B. At this time, a large number of object information acquisition requests for virtual object A can be added to the request processing queue associated with virtual object A, and a large number of object information acquisition requests for virtual object B can be added to the request processing queue associated with virtual object B. In this way, the object information acquisition requests for virtual object A can be merged and processed through the request processing queue associated with virtual object A to reduce the number of times the object information of virtual object A is acquired and packaged, and the object information acquisition requests for virtual object B can be merged and processed through the request processing queue associated with virtual object B to reduce the number of times the object information of virtual object B is acquired and packaged.

[0084] It is understandable that in group battle scenes of games (MMO, Massive Multiplayer Online), a large number of virtual objects will be in the same virtual scene and moved by players. For example, a group of virtual objects quickly cross the virtual sub-area at the same time, so that multiple identical virtual objects will enter the object field of view of the group of virtual objects. Any two virtual objects will request each other's object information. In this way, in a short period of time, there will be a large number of repeated object information acquisition requests for a virtual object. At this time, they can be added to the corresponding request processing queue for merge processing to improve the efficiency of a single virtual object in obtaining object information of other virtual objects.

[0085] For example, Figure 5-Figure 7 As shown, Figure 5-Figure 7 1 is a schematic diagram of a moving scene of a virtual object provided by an embodiment of the present application; wherein, in a game competition scene, a large number of virtual objects are gathered together. Taking the perspective of the virtual object 51a as an example, virtual objects 52a-55a may exist in the object field of view of the virtual object 51a (in this case, the field of view 1). That is to say, in the perspective of the player currently corresponding to the virtual object 51a (i.e., on the field of view display interface 1 viewed by the player), the virtual objects 52a-55a within the object field of view of the virtual object 51a can be viewed, and the information of the virtual objects 52a-55a (such as health, etc., which may belong to the object information pulled from the business server) can be viewed. At this time, the player controls the virtual object 51a according to Figure 5The virtual object 51a moves in the direction shown. At this time, the object field of view of the virtual object 51a is changed from field of view 1 to field of view 2. The virtual objects 53a, 54a, 56a, and 57a can exist in the object field of view of the virtual object 51a (at this time, field of view 2). That is to say, in the player's perspective currently corresponding to the virtual object 51a (that is, on the field of view display interface 2 viewed by the player), the virtual objects 53a, 54a, 56a, and 57a within the object field of view of the virtual object 51a can be viewed.

[0086] It is understood that when the service server detects a change in the field of view range of virtual object 51a, it can determine the field of view change range based on field of view range 1 and field of view range 2. If virtual objects 56a and 57a are within the field of view change range, virtual objects 56a and 57a are newly added virtual objects corresponding to virtual object 51a. That is, virtual objects 56a and 57a need to request the object information of virtual object 51a, and virtual object 51a needs to request the object information of virtual objects 56a and 57a. In other words, when the client corresponding to virtual object 51a obtains the object information of virtual objects 56a and 57a, it can render and display virtual objects 56a and 57a. That is, the player corresponding to virtual object 51a can view virtual objects 56a and 57a on field of view display interface 2.

[0087] For example, Figure 6 , virtual objects a1 to virtual objects a3 are in the same virtual sub-area, the object field of view of virtual objects a1-a3 is field of view range 81a, and the object field of view of virtual object b3 is field of view range 82a. Virtual objects a1-a3 move from the current virtual sub-area to another virtual sub-area, and the object field of view of virtual objects a1-a3 changes from field of view range 81a to field of view range 81a'. At this time, virtual objects b1-b3 are in the field of view change range of virtual objects a1-a3, that is, virtual objects b1-b3 are newly added virtual objects of virtual objects a1-a3, that is, at this time virtual objects a1-a3 serve as the first virtual objects, and virtual objects b1-b3 serve as the second virtual objects corresponding to virtual objects a1-a3. Therefore, the business server notifies virtual objects a1-a3 respectively, and virtual objects b1-b3 enter the object field of view of virtual objects a1-a3 (for example, virtual object a1 is notified respectively that virtual objects b1-b3 enter the object field of view, that is, each virtual object in virtual objects b1-b3 corresponds to one notification information, or virtual objects b1-b3 can be notified together, and the same applies to the following related descriptions), and notifies virtual objects b1-b3 that virtual objects a1-a3 enter the object field of view of virtual objects b1-b3.

[0088] At the same time, virtual object b3 moves from its current virtual sub-area to another virtual sub-area. The field of view of virtual object b3 changes from field of view 82a to field of view 82a'. At this point, virtual objects a1-a3 are within the changed field of view of virtual object b3. This means that virtual objects a1-a3 are newly added to virtual object b3. In other words, virtual object b3 now serves as the first virtual object, and virtual objects a1-a3 serve as the second virtual objects corresponding to virtual object b3. Therefore, the service server notifies virtual object b3 that virtual objects a1-a3 have entered the field of view of virtual object b3, and also notifies virtual objects a1-a3 separately that virtual object b3 has entered the field of view of virtual objects a1-a3.

[0089] It is understood that the information notifying the entry into the field of view may or may not be sent repeatedly. If the time interval between sending notification information for the same virtual object at the last moment of the determined distance is less than a first time interval threshold, the information may not be sent repeatedly. It is understood that upon receiving the notification information sent by the service server, the virtual object may send a request to the service server to obtain object information. It is understood that the request to obtain object information may or may not be sent repeatedly. If the time interval between sending object information acquisition requests for the same virtual object at the last moment of the determined distance is less than a second time interval threshold, the information may not be sent repeatedly.

[0090] It is understood that a virtual object (target request object) can be either a first virtual object or a second virtual object. In this case, the virtual business object includes the second virtual object corresponding to the target request object as the first virtual object (i.e., the virtual object within the field of view change range of the first virtual object), and the first virtual object corresponding to the target request object as the second virtual object (i.e., the virtual object corresponding to the field of view change range). A virtual object can correspond to multiple second virtual objects, and a virtual object can correspond to multiple first virtual objects.

[0091] That is to say, on Figure 6In this example, three virtual objects a1-a3 simultaneously move across the boundaries of virtual sub-areas within a short period of time. Sub-areas L1-L3 represent the range of virtual objects a1-a3's field of view exit, while sub-areas L1'-L3' represent the range of virtual objects a1-a3's field of view change. According to the field of view switching logic, virtual objects a1-a3 will each initiate the same object information acquisition request to all virtual objects within sub-areas L1'-L3'. Simultaneously, all virtual objects within sub-areas L1'-L3' will also initiate separate requests to retrieve the object information of virtual objects a1-a3. Assuming there are 30 virtual objects in each of sub-areas L1'-L3', the total number of object information acquisition requests that virtual objects a1-a3 need to send is 3 * 30 = 90. The total number of object information acquisition requests that all virtual objects within sub-areas L1'-L3' need to send is 30 * 3 = 90. Then, because the virtual objects a1 - a3 move simultaneously across the virtual sub-area boundary, the service server needs to obtain and package object information 90+90=180 times in total.

[0092] It can be understood that in this case, there are many repeated object information acquisition requests sent by virtual objects in a short period of time, which shows a relatively obvious time locality. Therefore, the object information acquisition requests can be cached and the same object information acquisition requests initiated by different virtual objects can be merged, so that the processing volume of object information acquisition requests in the local time can be greatly reduced.

[0093] For example, if a target request object has N virtual business objects, then obtaining and packaging the object information of a single virtual object can save approximately (N-1) / N performance overhead. Figure 6 For example, let's take the case of three virtual objects a1-a3 moving simultaneously across the virtual sub-area boundary within a short period of time. Ideally, all object information retrieval requests for the same character can be consolidated, and the service server only needs to retrieve and package object information 3 + 30 = 33 times. This significantly reduces the number of object information retrieval times required by the service server when virtual objects move in groups or pairs.

[0094] At this time, if Figure 7After receiving the notification information from the business server, the virtual object a1 sends an object information acquisition request c11 for the virtual object b1 to the business server, and the business server adds the object information acquisition request c11 to the request processing queue C1 of the virtual object b1; after receiving the notification information from the business server, the virtual object a2 sends an object information acquisition request c12 for the virtual object b1 to the business server, and the business server adds the object information acquisition request c12 to the request processing queue C1 of the virtual object b1; after receiving the notification information from the business server, the virtual object a3 sends an object information acquisition request c13 for the virtual object b1 to the business server, and the business server adds the object information acquisition request c13 to the request processing queue C1 of the virtual object b1.

[0095] Similarly, after receiving the notification information from the business server, the virtual object a1 sends an object information acquisition request c21 for the virtual object b2 to the business server, and the business server adds the object information acquisition request c21 to the request processing queue C2 of the virtual object b2; after receiving the notification information from the business server, the virtual object a2 sends an object information acquisition request c22 for the virtual object b2 to the business server, and the business server adds the object information acquisition request c22 to the request processing queue C2 of the virtual object b2; after receiving the notification information from the business server, the virtual object a3 sends an object information acquisition request c23 for the virtual object b2 to the business server, and the business server adds the object information acquisition request c23 to the request processing queue C2 of the virtual object b2.

[0096] Similarly, after receiving the notification information from the business server, the virtual object a1 sends an object information acquisition request c31 for the virtual object b3 to the business server, and the business server adds the object information acquisition request c31 to the request processing queue C3 of the virtual object b3; after receiving the notification information from the business server, the virtual object a2 sends an object information acquisition request c32 for the virtual object b3 to the business server, and the business server adds the object information acquisition request c32 to the request processing queue C3 of the virtual object b3; after receiving the notification information from the business server, the virtual object a3 sends an object information acquisition request c33 for the virtual object b3 to the business server, and the business server adds the object information acquisition request c33 to the request processing queue C3 of the virtual object b3.

[0097] Similarly, after receiving the notification information from the business server, the virtual object b1 sends an object information acquisition request c41 for the virtual object a1 to the business server, and the business server adds the object information acquisition request c41 to the request processing queue C4 of the virtual object a1; after receiving the notification information from the business server, the virtual object b2 sends an object information acquisition request c42 for the virtual object a1 to the business server, and the business server adds the object information acquisition request c42 to the request processing queue C4 of the virtual object a1; after receiving the notification information from the business server, the virtual object b3 sends an object information acquisition request c43 for the virtual object a1 to the business server, and the business server adds the object information acquisition request c43 to the request processing queue C4 of the virtual object a1.

[0098] Similarly, after receiving the notification information from the business server, the virtual object b1 sends an object information acquisition request c51 for the virtual object a2 to the business server, and the business server adds the object information acquisition request c51 to the request processing queue C5 of the virtual object a2; after receiving the notification information from the business server, the virtual object b2 sends an object information acquisition request c52 for the virtual object a2 to the business server, and the business server adds the object information acquisition request c52 to the request processing queue C5 of the virtual object a2; after receiving the notification information from the business server, the virtual object b3 sends an object information acquisition request c53 for the virtual object a2 to the business server, and the business server adds the object information acquisition request c53 to the request processing queue C5 of the virtual object a2.

[0099] Similarly, after receiving the notification information from the business server, the virtual object b1 sends an object information acquisition request c61 for the virtual object a3 to the business server, and the business server adds the object information acquisition request c61 to the request processing queue C6 of the virtual object a3; after receiving the notification information from the business server, the virtual object b2 sends an object information acquisition request c62 for the virtual object a3 to the business server, and the business server adds the object information acquisition request c62 to the request processing queue C6 of the virtual object a3; after receiving the notification information from the business server, the virtual object b3 sends an object information acquisition request c63 for the virtual object a3 to the business server, and the business server adds the object information acquisition request c63 to the request processing queue C6 of the virtual object a3.

[0100] It can be understood that a target request object corresponds to a request processing queue, and the request processing queue includes an object information acquisition request for the target request object. In other words, the business server can detect changes in the object field of view of virtual object A. When a change in the object field of view of virtual object A is detected, the field of view change range of the virtual object is determined, and the virtual objects within the field of view change range are treated as newly added virtual objects of virtual object A. At this time, virtual object A can be notified that the newly added virtual object has entered the field of view, and the newly added virtual object can be notified that virtual object A has entered the field of view. At this time, the newly added virtual object requests the object information of virtual object A from the business server, and virtual object A requests the object information of the newly added virtual object from the business server. The business server can first cache the received object information acquisition request and add it to the request processing queue of the corresponding virtual object. When the request processing queue of the corresponding virtual object is determined, the object information acquisition request is processed in the request processing queue of the corresponding virtual object.

[0101] That is to say, the target request object is a virtual object that enters the object field of view of the virtual business object, so the virtual business object needs to request the object information of the target request object. It can be understood that the business server can maintain a visible virtual object list for each virtual object, and the visible virtual object list includes virtual objects within the object field of view of the virtual object. When the business server detects that the object field of view of virtual object A has changed, it determines the virtual objects within the field of view change range of virtual object A, and adds the virtual objects within the field of view change range to the visible virtual object list (at the same time, the visible virtual object list of the virtual objects within the field of view change range is added to virtual object A), and deletes the virtual objects that leave virtual object A from the visible virtual object list (at the same time, deletes virtual object A from the visible virtual object list of the virtual objects that leave virtual object A).

[0102] In other words, when virtual object A is added to another virtual object's visible virtual object list, the other virtual object can request information about virtual object A. This means the service server needs to notify the other virtual object that virtual object A has entered its field of view. It can be understood that the other virtual object is the virtual service object in this context, and virtual object A is the target request object in this context. Accordingly, virtual object A is also the virtual service object in this context, and the other virtual object is the target request object in this context.

[0103] Therefore, when the business server determines that a virtual object enters the object field of view of another virtual object, it uses the virtual object as the target request object and the other virtual object as the virtual business object, and thus generates entry field of view notification information for the target request object; the entry field of view notification information is used to notify the virtual business object that the target request object enters the object field of view of the virtual business object; the entry field of view notification information is sent to the virtual business object, so that the virtual business object sends an object information acquisition request for the target request object to the business server based on the entry field of view notification information.

[0104] Optionally, when a virtual object moves in an object gathering area, a large number of object information acquisition requests are generated, while when a virtual object moves in a non-object gathering area, fewer object information acquisition requests are generated. Therefore, a request processing queue caching mechanism can be adopted for virtual objects in the object gathering area. For example, when a business server receives an object information acquisition request sent by a virtual business object and determines that the virtual area indicated by the object field of view of the virtual business object belongs to the object gathering area, the object information acquisition request sent by the virtual business object is added to the request processing queue. It can be understood that when the number of virtual objects in the virtual area indicated by the object field of view of the virtual business object is greater than a quantity threshold, the virtual business object can be regarded as being in the object gathering area. Alternatively, a virtual sub-area in which the number of virtual objects in the virtual scene is greater than a certain quantity threshold is used as an object gathering area. When the virtual area indicated by the object field of view of the virtual business object overlaps with the object gathering area, it is determined that the virtual business object is in the object gathering area.

[0105] Optionally, when the business server receives an object information acquisition request sent by a virtual business object and determines that the virtual area indicated by the object field of view of the target business object belongs to an object aggregation area, the business server adds the object information acquisition request sent by the virtual business object to a request processing queue.

[0106] Optionally, when the business server receives an object information acquisition request sent by a virtual business object and determines that the virtual areas indicated by the object field of view of the target business object and the virtual business object both belong to the object aggregation area, the business server adds the object information acquisition request sent by the virtual business object to the request processing queue.

[0107] Optionally, when the business server receives an object information acquisition request sent by a virtual business object and determines that the virtual area indicated by the object field of view of the target business object or virtual business object belongs to an object aggregation area, the business server adds the object information acquisition request sent by the virtual business object to a request processing queue.

[0108] It is understood that when a virtual object does not meet the request processing queue caching mechanism, the object information acquisition request for the virtual object is directly processed. If there are still unprocessed object information acquisition requests in the request processing queue associated with the virtual object, the unprocessed object information acquisition requests can continue to be processed according to the processing method for the request processing queue.

[0109] It is understood that, taking a request processing queue as an example, the request processing queue includes N object information acquisition requests (N may be different for different request processing queues). The business server may determine the request processing queue to be processed when it detects that the number of N object information acquisition requests in the request processing queue reaches a request number threshold. Alternatively, the request processing queue may be determined when a processing timestamp for the request processing queue is reached. For example, the request processing queue may be determined every 500 milliseconds, that is, at a certain time interval, the arrival processing timestamp is determined and the object information acquisition request in the request processing queue is processed.

[0110] S102. Obtain queue processing parameters associated with the request processing queue, obtain M object information acquisition requests to be merged from N object information acquisition requests based on the queue processing parameters, and determine the M virtual business objects that send the M object information acquisition requests as merged processing virtual objects.

[0111] Wherein, M is a positive integer less than or equal to N.

[0112] The queue processing parameter may be the number of requests to be acquired, and M object information acquisition requests to be merged may be acquired from N object information acquisition requests based on the number of requests to be acquired. The number of requests to be acquired is consistent with M.

[0113] The queue processing parameter may be a maximum request processing number, and may be configured to obtain M object information acquisition requests to be merged from the N object information acquisition requests based on the maximum request processing number when the number of N object information acquisition requests in the request processing queue is greater than or equal to the maximum request processing number. The maximum request processing number remains consistent with M. Alternatively, when the number of N object information acquisition requests in the request processing queue is less than the maximum request processing number, the N object information acquisition requests are used as the M object information acquisition requests to be merged. In this case, N equals M.

[0114] Among them, the queue processing parameters may include the request processing ratio and the minimum request processing number for the request processing queue. Therefore, obtaining M object information acquisition requests to be merged from N object information acquisition requests based on the queue processing parameters can be: determining the initial processing number for the request processing queue based on the request processing ratio and the number of requests of the N object information acquisition requests in the request processing queue (the number of requests is equal to N); the initial processing number is a positive integer less than N; if the initial processing number is greater than or equal to the minimum request processing number, the initial processing number is used as the target processing number for the request processing queue; based on the target processing number, obtaining M object information acquisition requests to be merged from the N object information acquisition requests in the request processing queue; M is consistent with the target processing number.

[0115] It is understood that if the initial processing quantity is less than the minimum request processing quantity, the minimum request processing quantity is used as the target processing quantity. It is also understood that if the request quantity of N object information acquisition requests is less than the minimum request processing quantity, the request quantity of N object information acquisition requests is used as the target processing quantity. In other words, all object information acquisition requests are obtained from the request processing queue and merged for processing.

[0116] It can be understood that the object information acquisition requests to be merged can be acquired from the request processing queue in sequence according to the order in which the object information acquisition requests are added to the request processing queue from earliest to latest.

[0117] That is, the product of the request processing ratio and the number of N object information acquisition requests in the request processing queue can be used as the initial processing number of the request processing queue. It can be understood that this can ensure that the target processing number will not be less than the minimum request processing number nor will it be larger, that is, the number of object information acquisition requests processed at one time will not be too many nor too few, that is, the number of object information acquisition requests processed at one time can be dynamically changed, so that a balance can be achieved in request processing efficiency and processing performance. That is, when the number N is large, the number of object information acquisition requests processed at one time can be adjusted by the request processing ratio. In this way, the object information acquisition requests that are not too few can enable a certain amount of requests to be merged and processed, thereby ensuring request processing efficiency, and the object information acquisition requests that are not too few can prevent the business server from processing a large number of requests at one time, thereby smoothing the server resource processing performance and avoiding glitches.

[0118] For example, a business server defines a time interval for each scheduled processing, such as 500 milliseconds. For a request processing queue, each time a processing timestamp is detected after a certain time interval, the object information acquisition request in the request processing queue is processed, i.e., the object information acquisition request is retrieved from the request processing queue. The business server also defines a request processing ratio, i.e., a processing ratio for each request, such as 20%. It also defines a minimum request processing number, i.e., the minimum number of requests to be processed per processing, such as 10. Thus, during each scheduled processing, the business server obtains the number of object information acquisition requests to be merged from the request processing queue and multiplies the number of requests in the request processing queue by the request processing ratio. If this product is less than the minimum request processing number, the minimum request processing number is used. This product value varies with the number of requests remaining in the request processing queue, but overall, it ensures that object information acquisition requests for virtual objects are processed within (1 / request processing ratio * processing time interval), thus ensuring the timely processing of object information acquisition requests.

[0119] It can be understood that after M object information acquisition requests are taken out, the N object information acquisition requests in the request processing queue become NM object information acquisition requests, and the NM object information acquisition requests in the request processing queue (optionally, also including subsequently added object information acquisition requests) serve as the new N object information acquisition requests when the request processing queue is determined next time.

[0120] For example, Figure 8 As shown, Figure 8 This is a schematic diagram of the acquisition process of an object information acquisition request provided in an embodiment of the present application; wherein, the request processing queue 80A includes N object information acquisition requests q81-request q8n, and the queue processing parameters for the request processing queue A include the request processing ratio and the minimum request processing quantity X1. The initial processing quantity X2 for the request processing queue is determined based on the request processing ratio and the request quantity of the N object information acquisition requests in the request processing queue, and it is judged whether the initial processing quantity is greater than or equal to the minimum request processing quantity; if the initial processing quantity is greater than or equal to the minimum request processing quantity, the initial processing quantity is used as the target processing quantity for the request processing queue; if the initial processing quantity is less than the minimum request processing quantity, the minimum request processing quantity is used as the target processing quantity; based on the target processing quantity, M object information acquisition requests to be merged (such as request q81-request q8m) are obtained from the N object information acquisition requests in the request processing queue. At this time, the request processing queue A includes object information acquisition requests q8m+1-request q8n.

[0121] S103: Perform request merging processing on the M object information acquisition requests to obtain a merged processing request, obtain first object information of the first virtual object based on the merged processing request, and determine the first object information as the object information of the target request object.

[0122] The M object information acquisition requests may be merged to generate a merged processing request, which is used to request object information of the target request object.

[0123] At this time, the first object information of the first virtual object is obtained based on the merged processing request, that is, the object information of the target request object is obtained. It can be understood that if the target request object is the second virtual object, the second object information of the second virtual object is obtained based on the merged processing request; and the second object information is determined as the object information of the target request object.

[0124] It can be understood that when virtual object A, which is the target request object, is the first virtual object, virtual object A has a request processing queue, the virtual business object of virtual object A is virtual object B within the field of view change range of virtual object A (i.e., the second virtual object corresponding to virtual object A), and virtual object B sends an object information acquisition request for virtual object A to the business server. When virtual object C, which is the target request object, is the second virtual object, virtual object C has a request processing queue, the virtual business object of virtual object C is virtual object D with a field of view change range (i.e., the first virtual object corresponding to virtual object C, and virtual object C is within the field of view change range of virtual object D), and virtual object D sends an object information acquisition request for virtual object C to the business server.

[0125] In other words, for the target request object, if the target request object is the first virtual object, it can be considered as obtaining the first object information of the first virtual object. If the target request object is the second virtual object, it can be considered as obtaining the second object information of the second virtual object. However, for the same virtual object, the object information obtained at the same time is the same. In other words, for each of the M object information acquisition requests, the object information of the target request object only needs to be obtained once.

[0126] S104: Generate a request data packet for sending to the merged virtual object based on the object information of the target request object.

[0127] At this time, the object information of the target request object can be packaged to obtain M request data packets corresponding to the object information acquisition requests, and the request data packets can be returned to the M virtual business objects that serve as the merged virtual objects. The M virtual business objects then render and display the target request object within the field of view of the M virtual business objects based on the object information in the request data packets.

[0128] It can be understood that the M object information acquisition requests may include requests sent by a virtual business object that is a first virtual object, and may also include requests sent by a virtual business object that is a second virtual object.

[0129] That is to say, in the game scene, virtual objects within the object's field of view are visible to each other. The number of object information synchronizations of virtual objects within the object's field of view is proportional to the square of the number of virtual objects within the object's field of view. As the number of virtual objects within the field of view change increases, a large number of object information acquisition requests will be generated. Therefore, a large number of object information acquisition and packaging operations will cause a sharp increase in the resource overhead of the business server, which may cause lags during player control. Therefore, the technical solution of the present application optimizes the acquisition and synchronization process of object information of virtual objects, and utilizes the time locality of object information acquisition requests sent by different virtual objects through the client to merge different object information acquisition requests for the same virtual object. This can greatly reduce the number of object information acquisition and packaging times, such as reducing the resource overhead required for the business server to acquire and package object information when synchronizing character information within the field of view during group battles among players, avoiding lags caused by slow server response, and allowing players to have a better experience of real-time interactivity, thousands of people on the same screen, and other more advanced gaming experiences and higher fluency.

[0130] In an embodiment of the present application, a request processing queue associated with a target request object may be determined. The request processing queue includes N object information acquisition requests, each of which is used by a virtual business object to request object information about the target request object. When the target request object is a first virtual object, the virtual business objects may include virtual objects within a change in the field of view of the first virtual object when the first virtual object moves. At this time, the queue processing parameters can be obtained, and M object information acquisition requests to be merged can be obtained from the N object information acquisition requests based on the queue processing parameters, and the M virtual business objects corresponding to the M object acquisition requests can be determined as merged processing virtual objects. When the M object information acquisition requests are merged and the merged processing request is obtained, the object information of the target request object can be determined once based on the merged processing request to generate a request data packet for sending to the merged processing virtual object. That is to say, for M object information acquisition requests, it is only necessary to obtain the object information of the target request object once, that is, multiple object information acquisition requests for the same virtual object sent by different virtual business objects can be merged and responded to at the same time. When M is greater than 1, this can reduce the number of times the business server performs role information acquisition operations, thereby reducing the server's processing resource consumption when the virtual object requests to obtain object information.

[0131] For further information, see Figure 9 , Figure 9 This is a flow chart of an object information processing method provided by an embodiment of the present application, such as Figure 9 As shown, the method can be executed by the computer device mentioned above, and the computer device can be a business server, for example, the business server can be the above-mentioned Figure 1 The service server 100 shown in FIG. The method may specifically include the following steps S201 to S208:

[0132] S201. When receiving an object information acquisition request for a target request object sent by a virtual business object, add the object information acquisition request to a request processing queue associated with the target request object.

[0133] Wherein, each time the business server receives an object information acquisition request for a target request object sent by a virtual business object, the business server adds the object information acquisition request to the corresponding request processing queue.

[0134] For a target request object, the object identifier of the target request object is used as key data, and the request processing queue is used as value data. The value data includes a list of object identifiers of virtual business objects, and each object identifier of the virtual business object in the list corresponds to an object information acquisition request.

[0135] For example, Figure 10 As shown, Figure 10 This is a schematic diagram of a request processing queue provided by an embodiment of the present application; the object identifier a11 of the target request object (such as virtual object a1) is used as the key data key1, and the corresponding request processing queue (value data value1) includes a list of object identifiers of virtual business objects used to request object information of the virtual object a1 (such as object identifier b11, object identifier b12, ..., object identifier b1n), and each object identifier in the list corresponds to an object information acquisition request sent by the corresponding virtual business object (such as request q11, request q12, ..., request q1n).

[0136] Similarly, when there are multiple target request objects, each target request object corresponds to key-value data. For example, if the object identifier a21 of virtual object a2 serves as the key data key2, the corresponding request processing queue (value data value2) includes a list of object identifiers of virtual business objects (e.g., object identifier b21, object identifier b22, ..., object identifier b2n) used to request object information for virtual object a2. Each object identifier in the list corresponds to an object information retrieval request (e.g., request q21, request q22, ..., request q2n) sent by the corresponding virtual business object.

[0137] Alternatively, the object identifier a31 of the virtual object a3 is used as the key data key3, and the corresponding request processing queue (value data value3) includes a list of object identifiers of virtual business objects used to request object information of the virtual object a3 (such as object identifier b31, object identifier b32, ..., object identifier b3n), and each object identifier in the list corresponds to an object information acquisition request sent by the corresponding virtual business object (such as request q31, request q32, ..., request q3n).

[0138] S202: When the processing timestamp for the request processing queue is reached, determine the request processing queue.

[0139] The object information acquisition requests in the request processing queue may be merged and processed at regular intervals, that is, when a certain time interval is reached, the request processing queue with the processing timestamp is determined.

[0140] The request processing queue includes N object information acquisition requests, where N is a positive integer greater than 1. An object information acquisition request is a request sent by a virtual business object for acquiring object information of a target request object.

[0141] It is understood that if the target request object includes a first virtual object, the virtual business object refers to a second virtual object within the field of view change range of the first virtual object, and the field of view change range refers to the field of view range determined by the business server when detecting that the object field of view range of the first virtual object has changed from the first field of view range to the second field of view range. If the virtual business object includes a virtual object whose object field of view range has changed and the field of view change range has been determined, the target request object is the second virtual object within the field of view change range of the virtual business object. For a detailed description of the target request object and the virtual business object, please refer to the relevant description of the above embodiment.

[0142] It is understood that the virtual area indicated by the first field of view may include R1 first virtual sub-areas. The first virtual object is located in a first target virtual sub-area among the R1 first virtual sub-areas. R1 is a positive integer. In other words, the virtual sub-area where the virtual object is located is the target virtual sub-area, and the virtual area indicated by the object field of view of the virtual object is determined based on the target virtual sub-area.

[0143] When the service server detects that the first virtual object crosses from the first target virtual sub-area to the second target virtual sub-area, it determines that the object field of view of the first virtual object is changed from the first field of view to the second field of view corresponding to the second target virtual sub-area; the virtual area indicated by the second field of view includes R2 second virtual sub-areas; the second target virtual sub-area belongs to R2 second virtual sub-areas; R2 is a positive integer; from the R2 second virtual sub-areas, a second virtual sub-area that is different from the R1 first virtual sub-areas is determined, and the field of view indicated by the determined second virtual sub-area is used as the field of view change range. The first target virtual sub-area is different from the second target virtual sub-area. R1 may be equal to or different from R2.

[0144] It is understood that crossing from a first target virtual sub-area to a second target virtual sub-area can mean that the first virtual object moves from the first target virtual sub-area to an adjacent virtual sub-area, jumps from the first target virtual sub-area to another virtual sub-area, or switches to a new virtual sub-area upon entering a new virtual area. There is no limitation on the area crossing scenario here.

[0145] That is to say, when the business server detects the movement of a virtual object, when determining that the virtual object crosses from one virtual sub-area to another virtual sub-area, it determines the new object field of view of the virtual object based on the other virtual sub-area, and at the same time determines the field of view change range of the virtual object based on the object field of view range before crossing (first field of view range) and the object field of view range after crossing (second field of view range). At this time, the virtual object is the first virtual object.

[0146] That is, among the R2 second virtual sub-areas, the second virtual sub-area that is different from the R1 first virtual sub-areas is the virtual area indicated by the field of view change range. Optionally, the service server can maintain a list of virtual objects for each virtual sub-area and use the virtual objects in the virtual object list of the virtual area indicated by the field of view change range as newly added virtual objects corresponding to the first virtual objects.

[0147] Optionally, a first virtual sub-region that is different from the R2 first virtual sub-regions can be determined from the R1 second virtual sub-regions, and the field of view indicated by the determined first virtual sub-region is used as the field of view exit range of the first virtual object. The virtual object within the field of view exit range is used as a third virtual object, and field of view exit notification information is generated for the first virtual object. The field of view exit notification information is used to notify the third virtual object that the first virtual object has left the field of view of the third virtual object, and the field of view exit notification information is sent to the third virtual object. In other words, the third virtual object can be notified that the first virtual object has left the field of view range, and the first virtual object can be subsequently no longer rendered or displayed.

[0148] Similarly, a notification message is generated for the third virtual object that it has left the visual field. This notification message is used to notify the first virtual object that the third virtual object has left the visual field of the first virtual object. In other words, the first virtual object can be notified that the third virtual object has left the visual field, and the third virtual object can no longer be rendered or displayed.

[0149] In other words, the first virtual object is the virtual object whose field of view has changed, the second virtual object is the virtual object within the field of view change, and the third virtual object is the virtual object that has left the field of view. The first and second virtual objects request the service server to retrieve each other's object information. The first and third virtual objects no longer obtain information about each other.

[0150] Optionally, the request processing queue corresponding to a target request object may include multiple request processing queues. Here, two request processing queues are taken as an example. That is, the request processing queue of the target request object may include a first request processing queue and a second request processing queue.

[0151] The N object information acquisition requests include object information acquisition request i; i is a positive integer less than or equal to N; and the virtual business object sending object information acquisition request i is a reference virtual object. Upon receiving object information acquisition request i, the business server may obtain the object distance between the reference virtual object and the target request object; if the object distance is within a first distance range associated with a first request processing queue, object information acquisition request i is added to the first request processing queue. If the object distance is within a second distance range associated with a second request processing queue, object information acquisition request i is added to the second request processing queue.

[0152] That is, when the object distance between the reference virtual object and the target request object is within a first distance range, object information acquisition request i is added to the first request processing queue. When the object distance between the reference virtual object and the target request object is within a second distance range, object information acquisition request i is added to the second request processing queue. Different request processing queues are associated with different distance ranges.

[0153] That is to say, the object information acquisition request can be added to the corresponding request processing queue according to the object distance between the virtual business object and the target request object. It can be understood that the virtual object pays more attention to the virtual object that is closer, and pays less attention to the virtual object that is farther away. Therefore, different request processing queues can be corresponding to different object distances. For example, the object information acquisition request sent by the virtual business object with a closer object distance can be added to the request processing queue 1, and the object information acquisition request sent by the virtual business object with a farther object distance can be added to the request processing queue 2. At this time, the processing speed of the object information acquisition request in the request processing queue 1 can be higher than the processing speed of the object information acquisition request in the request processing queue 2, so that the virtual object can quickly obtain the object information of the virtual object that is closer, thereby improving the flexibility of obtaining object information.

[0154] It is understood that when determining the request processing queue associated with the target request object, the first request processing queue may be determined when a first processing timestamp corresponding to the first request processing queue is reached. Alternatively, the second request processing queue may be determined when a second processing timestamp corresponding to the second request processing queue is reached. The arrival frequencies of the first processing timestamp and the second processing timestamp may be different.

[0155] For example, if the maximum distance value indicated by the first distance range is less than or equal to the minimum distance value indicated by the second distance range (i.e., the first request processing queue corresponds to the request processing queue 1, and the second request processing queue corresponds to the request processing queue 2), then the arrival frequency of the first processing timestamp is higher than the arrival frequency of the second processing timestamp. That is, the time interval between arrivals of the first processing timestamp is less than the time interval between arrivals of the second processing timestamp.

[0156] It is understood that, depending on the distance range setting, a third distance range may also be included, i.e., the request processing queue may further include a third request queue. Object information acquisition requests sent by virtual business objects at a short distance may be added to the first request queue, object information acquisition requests sent by virtual business objects at a medium distance may be added to the second request queue, and object information acquisition requests sent by virtual business objects at a long distance may be added to the third request queue.

[0157] At this time, when the third processing timestamp for the third request processing queue is reached, the third request processing queue is determined.

[0158] The maximum distance value indicated by the first distance range is less than or equal to the minimum distance value indicated by the second distance range, and the maximum distance value indicated by the second distance range is less than or equal to the minimum distance value indicated by the third distance range. Therefore, the arrival frequency of the first processing timestamp is higher than the arrival frequency of the second processing timestamp, and the arrival frequency of the second processing timestamp is higher than the arrival frequency of the third processing timestamp. For ease of explanation, taking the example of a request processing queue including two request processing queues, the processing principle is the same when the request processing queue includes three or more request processing queues.

[0159] For example, Figure 11-12 As shown, Figure 11-12 This is a schematic diagram of a request processing queue provided by an embodiment of the present application; wherein, taking the request processing queue including a first request processing queue 131a (for storing object information acquisition requests sent by virtual business objects at a short distance) and a second request processing queue 132a (for storing object information acquisition requests sent by virtual business objects at a long distance) as an example, when the business server receives the object information acquisition request 133a sent by virtual object a1 for virtual object b1, it determines the object distance 13X between virtual object a1 and virtual object b1 at this time, and determines whether the object distance 13X is within a first distance range; if the object distance 13X is within the first distance range, the object information acquisition request is added to the first request processing queue; if the object distance 13X is within the second distance range, the object information acquisition request is added to the second request processing queue.

[0160] It can be understood that when the first processing timestamp for the first request processing queue is reached, the first request processing queue is determined, and the object information acquisition requests in the first request processing queue are merged and processed. When the second processing timestamp for the second request processing queue is reached, the second request processing queue is determined, and the object information acquisition requests in the second request processing queue are merged and processed.

[0161] For example, Figure 12 At time T1, the first processing timestamp K11 for the first request processing queue arrives. After a certain time interval Z1, the new first processing timestamp K12 for the first request processing queue arrives at time T2. Similarly, at time T3, the second processing timestamp K21 for the second request processing queue arrives. After a certain time interval Z2, the new second processing timestamp K22 for the second request processing queue arrives at time T4. Z1 is less than Z2, that is, the arrival frequency of the first processing timestamp is higher than the arrival frequency of the second processing timestamp.

[0162] S203: Obtain queue processing parameters associated with the request processing queue.

[0163] The queue processing parameters include a request processing ratio and a minimum request processing quantity for the request processing queue.

[0164] It can be understood that if the request processing queue includes a first request processing queue and a second request processing queue, the queue processing parameters include a first queue processing parameter for the first request processing queue and a second queue processing parameter for the second request processing queue.

[0165] The first queue processing parameters for the first request processing queue include a request processing ratio and a minimum request processing quantity for the first request processing queue, and the second queue processing parameters for the second request processing queue include a request processing ratio and a minimum request processing quantity for the second request processing queue.

[0166] S204 : Based on the request processing ratio and the minimum request processing quantity in the queue processing parameters, M object information acquisition requests to be merged are acquired from the N object information acquisition requests.

[0167] When there is one request processing queue for a target request object, the specific process of obtaining M object information acquisition requests to be merged based on the queue processing parameters can be referred to the relevant description of the above embodiment.

[0168] When a request processing queue of a target request object includes a first request processing queue and a second request processing queue, N object information acquisition requests for requesting the target request object are added to the first request processing queue and the second request processing queue respectively.

[0169] For example, N1 object information acquisition requests out of N object information acquisition requests are added to the first request processing queue, and N2 object information acquisition requests out of N object information acquisition requests are added to the second request processing queue. N1 is a positive integer less than or equal to N; N2 is a positive integer less than or equal to N, and the sum of N1 and N2 is equal to N.

[0170] It is understood that when the first processing timestamp is reached, for the first request processing queue, obtaining M object information acquisition requests to be merged from N object information acquisition requests based on the queue processing parameters may be performed by extracting the M object information acquisition requests to be merged from the N1 object information acquisition requests in the first request processing queue based on the first queue processing parameters. The specific process of extracting the M object information acquisition requests to be merged based on the request processing ratio and the minimum request processing quantity in the first queue processing parameters can be found in the relevant description of the above embodiment.

[0171] It is understood that when the second processing timestamp is reached, for the second request processing queue, obtaining M object information acquisition requests to be merged from the N object information acquisition requests based on the queue processing parameters may be performed by extracting the M object information acquisition requests to be merged from the N2 object information acquisition requests in the second request processing queue based on the second queue processing parameters. The specific process of extracting the M object information acquisition requests to be merged based on the request processing ratio and the minimum request processing quantity in the second queue processing parameters can be found in the relevant description of the above embodiment.

[0172] It can be understood that different request processing queues have different numbers of object information acquisition requests, queue processing parameters may be different, and the number of M object information acquisition requests retrieved may be different.

[0173] S205: Determine the M virtual business objects that have sent M object information acquisition requests as merged virtual objects.

[0174] S206 : Perform request merging processing on the M object information acquisition requests to obtain a merged processing request, and obtain object information of the target request object based on the merged processing request.

[0175] S207: Based on the object information of the target request object, generate a request data packet for sending to the merged virtual object. The specific implementation of steps S205-S207 can be found in the relevant description of the above embodiment, which will not be repeated here.

[0176] S208: Return the request data packet to the M virtual business objects serving as the merged processing virtual objects.

[0177] At this time, the request data packet containing the object information of the target request object may be sent to the M virtual business objects respectively.

[0178] For example, Figure 13This is a schematic diagram of a process for obtaining object information provided by an embodiment of the present application; wherein, S151, when the virtual object a1 crosses the virtual sub-area, the business server notifies the virtual object a1 that the virtual objects b1, b2, ..., bn (i.e., newly added virtual objects, i.e., virtual objects within the field of view change range) have newly entered the object field of view of the virtual object a1, which can be a separate notification or a combined notification; S152, at this time, the virtual object a2 and the virtual object a1 are in the same virtual sub-area, and cross to the same virtual sub-area together, and the business server notifies the virtual object a2 that the virtual objects b1, b2, ..., bn have newly entered the object field of view of the virtual object a2. , which can be a separate notification or a combined notification; S153, the business server notifies the virtual objects b1, b2, ..., bn that the virtual objects a1 and the virtual object a2 have newly entered the object field of view of the virtual objects b1, b2, ..., bn, which can be a separate notification or a combined notification; S154, the virtual object a1 initiates an object information acquisition request to the business server to obtain the object information of the virtual objects b1, b2, ..., bn (such as one virtual object corresponds to one request), and at this time the business server caches the received object information acquisition request, that is, adds it to the request processing queue associated with the corresponding virtual object; S155, the virtual object a2 sends a request to the service server to obtain the object information of the virtual objects b1, b2, ..., bn. The server initiates an object information acquisition request to pull virtual objects b1, b2, ..., bn (e.g., one virtual object corresponds to one request). At this time, the business server caches the received object information acquisition request, i.e., adds it to the request processing queue associated with the corresponding virtual object; S156, virtual objects b1, b2, ..., bn initiate an object information acquisition request to pull virtual objects a1, a2 (e.g., one virtual object corresponds to one request). At this time, the business server caches the received object information acquisition request, i.e., adds it to the request processing queue associated with the corresponding virtual object; the business server can start a timer to merge and process virtual objects a1, a2 in sequence. The business server receives the object information acquisition request in the request processing queue associated with a2, b1, b2, ..., bn. At this time, the business server caches the received object information acquisition request, that is, adds it to the request processing queue associated with the corresponding virtual object; when the business server obtains a merge processing request through the object information acquisition request in the request processing queue of a virtual object, it obtains the object information of the virtual object and packages the object information of the virtual object to obtain a request data packet; the business server returns the request data packet to the request sender associated with the merge processing request, that is, the object information can be obtained and packaged once, and can be broadcast to multiple request senders associated with the merge processing request.

[0179] That is to say, S157, the business server returns the request data packet containing the object information of virtual objects b1, b2, ..., bn to the virtual object a1; S158, the business server returns the request data packet containing the object information of virtual objects b1, b2, ..., bn to the virtual object a2; S159, the business server returns the request data packet containing the object information of virtual objects a1 and virtual object a2 to the virtual objects b1, b2, ..., bn.

[0180] For example, Figure 14 61a, request 62a, ..., request 610a; at time T61, the processing timestamp of the request processing queue 60a is reached, and the object information acquisition requests to be merged are obtained from the request processing queue 60a based on the queue processing parameters, such as requests 61a, request 62a, ..., request 610a. 65a, merges requests 61a, 62a, ..., and 65a to obtain a merged processing request 61b, obtains the object information of the target request object based on the merged processing request 61b to obtain a request data packet D61, and uses the virtual business objects (such as object 61c, object 62c, ..., object 65c) that send requests 61a, 62a, ..., and 65a as the merged processing virtual object E61, and sends the request data packet D61 to object 61c, object 62c, ..., object 65c respectively.

[0181] Similarly, if at time T62, the new processing timestamp of the request processing queue 60a is reached again, the object information acquisition requests to be merged are obtained from the request processing queue 60a based on the queue processing parameters, such as request 66a, request 67a, ..., request 612a (it can be understood that during the period T61-T62, new object information acquisition requests 611a, request 612a, ..., request 614a are added to the request processing queue 60a), and the requests 66a, request 67a, ..., request 612a are merged to obtain the merged processing request 62b. Based on the merged processing request 62b, the object information of the target request object is obtained to obtain the request data packet D62, and the virtual business objects (such as object 66c, object 67c, ..., object 612c) that send requests 66a, request 67a, ..., request 612a are used as the merged processing virtual objects E62, and the request data packet D62 is sent to objects 66c, object 67c, ..., object 612c respectively.

[0182] In an embodiment of the present application, when an object information acquisition request for a target request object is received from any virtual business object, the object information acquisition request can be added to a request processing queue associated with the virtual business object. When a processing timestamp for the request processing queue is reached, the request processing queue is determined, and queue processing parameters associated with the request processing queue are obtained. Based on the request processing ratio and the minimum request processing quantity in the queue processing parameters, M object information acquisition requests to be merged are obtained from N object information acquisition requests. The M virtual business objects that send the M object information acquisition requests are determined as merged processing virtual objects. The M object information acquisition requests are merged to obtain a merged processing request. And process the request to obtain the object information of the target request object, generate a request data packet for sending to the merged processing virtual object based on the object information of the target request object, and return the request data packet to the virtual business object that serves as the merged processing virtual object. That is to say, for M object information acquisition requests, it is only necessary to obtain the object information of the target request object once, that is, multiple object information acquisition requests for the same target request object sent by different virtual business objects can be merged and processed, and respond to the multiple object information acquisition requests at the same time. When M is greater than 1, this can reduce the number of times the business server performs the role information acquisition operation, thereby reducing the server's processing resource consumption when the virtual object requests to obtain object information.

[0183] For further information, see Figure 15 , Figure 15 This is a schematic diagram of the structure of an object information processing device provided by an embodiment of the present application. Figure 15 As shown, the object information processing device 1 can be applied to a computer device. It should be understood that the object information processing device 1 can be a computer program (including program code) running on the computer device, for example, the object information processing device 1 can be an application software; it can be understood that the object information processing device 1 can be used to execute the corresponding steps of the method provided in the embodiment of the present application. Figure 15 As shown, the object information processing device 1 may include: a queue determination module 11, a request acquisition module 12, an information acquisition module 13, a data processing module 14, and an object notification module 15; wherein:

[0184] A queue determination module 11 is configured to determine a request processing queue associated with a target request object; the request processing queue includes N object information acquisition requests, where N is a positive integer greater than 1, and each object information acquisition request is a request sent by a virtual business object to obtain object information of the target request object; wherein, if the target request object is a first virtual object, the virtual business objects include virtual objects within a field of view change range of the first virtual object, where the field of view change range is determined by the business server upon detecting that the object field of view range of the first virtual object has changed from a first field of view range to a second field of view range;

[0185] a request acquisition module 12 configured to acquire queue processing parameters associated with a request processing queue, acquire M object information acquisition requests to be merged from the N object information acquisition requests based on the queue processing parameters, and determine the M virtual business objects that sent the M object information acquisition requests as merged virtual objects; M is a positive integer less than or equal to N;

[0186] An information acquisition module 13 is configured to perform request merging processing on the M object information acquisition requests to obtain a merged processing request, obtain first object information of a first virtual object based on the merged processing request, and determine the first object information as object information of a target requested object;

[0187] The data processing module 14 is configured to generate a request data packet for sending to the merged processing virtual object based on the object information of the target request object.

[0188] The queue processing parameters include the request processing ratio and the minimum request processing quantity for the request processing queue;

[0189] The request acquisition module 12 includes:

[0190] The request quantity processing unit 121 is configured to determine an initial processing quantity for the request processing queue based on the request processing ratio and the number of N object information acquisition requests in the request processing queue; the initial processing quantity is a positive integer less than N;

[0191] a processing quantity determining unit 122 for using the initial processing quantity as a target processing quantity for the request processing queue if the initial processing quantity is greater than or equal to the minimum request processing quantity;

[0192] The request acquisition unit 123 is configured to acquire M object information acquisition requests to be merged from the N object information acquisition requests in the request processing queue based on the target processing quantity; M is consistent with the target processing quantity.

[0193] The request acquisition module 12 further includes:

[0194] The processing quantity determining unit 122 is configured to use the minimum requested processing quantity as the target processing quantity if the initial processing quantity is less than the minimum requested processing quantity.

[0195] The object information processing device 1 further includes:

[0196] The object notification module 15 is used to generate entry-in-view notification information for the target request object; the entry-in-view notification information is used to notify the virtual business object that the target request object has entered the object view range of the virtual business object;

[0197] The object notification module 15 is further configured to send the entry-in-view notification information to the virtual business object, so that the virtual business object sends an object information acquisition request for the target request object to the business server based on the entry-in-view notification information.

[0198] The queue determination module 11 further includes:

[0199] The request adding unit 111 is used to add the object information acquisition request sent by the virtual business object to the request processing queue when receiving the object information acquisition request sent by the virtual business object and determining that the virtual area indicated by the object field of view of the virtual business object belongs to the object aggregation area.

[0200] The virtual area indicated by the first visual field includes R1 first virtual sub-areas; the first virtual object is located on a first target virtual sub-area in the R1 first virtual sub-areas; R1 is a positive integer;

[0201] The object notification module 15 further includes:

[0202] The region determination unit 151 is configured to, upon detecting that the first virtual object crosses from the first target virtual subregion to the second target virtual subregion, determine that the object field of view of the first virtual object changes from the first field of view to a second field of view corresponding to the second target virtual subregion; the virtual region indicated by the second field of view includes R2 second virtual subregions; the second target virtual subregion belongs to the R2 second virtual subregions; and R2 is a positive integer.

[0203] The region determining unit 151 is further configured to determine a second virtual subregion different from the R1 first virtual subregions from the R2 second virtual subregions, and use the field of view range indicated by the determined second virtual subregion as the field of view change range.

[0204] The object notification module 15 further includes:

[0205] The leaving object notification unit 152 is configured to determine a first virtual sub-region that is different from the R2 first virtual sub-regions from the R1 second virtual sub-regions, and use the field of view range indicated by the determined first virtual sub-region as the field of view leaving range of the first virtual object;

[0206] The leaving object notification unit 152 is further configured to treat the virtual object within the field of view leaving range as a third virtual object;

[0207] The leaving object notification unit 152 is further configured to generate leaving field of view notification information for the first virtual object; the leaving field of view notification information is used to notify the third virtual object that the first virtual object has left the field of view of the third virtual object;

[0208] The leaving object notification unit 152 is further configured to send leaving field of view notification information to the third virtual object.

[0209] The N object information acquisition requests include an object information acquisition request i; i is a positive integer less than or equal to N; the virtual business object that sends the object information acquisition request i is a reference virtual object; the request processing queue includes a first request processing queue;

[0210] The queue determination module 11 further includes:

[0211] A request adding unit 111 is configured to obtain an object distance between a reference virtual object and a target request object;

[0212] The request adding unit 111 is configured to add the object information acquisition request i to the first request processing queue if the object distance is within a first distance range associated with the first request processing queue.

[0213] Wherein, the request processing queue includes a second request processing queue;

[0214] The request adding unit 111 is further configured to:

[0215] If the object distance is within the second distance range associated with the second request processing queue, the object information acquisition request i is added to the second request processing queue.

[0216] The queue determination module 11 includes:

[0217] A timestamp determining unit 112 is configured to determine the first request processing queue when a first processing timestamp for the first request processing queue is reached;

[0218] upon reaching a second processing timestamp for the second request processing queue, determining the second request processing queue;

[0219] If the maximum distance value indicated by the first distance range is less than or equal to the minimum distance value indicated by the second distance range, the arrival frequency of the first processing timestamp is higher than the arrival frequency of the second processing timestamp.

[0220] Wherein, N1 object information acquisition requests among the N object information acquisition requests are added to the first request processing queue; N1 is a positive integer less than or equal to N; the queue processing parameter includes a first queue processing parameter for the first request processing queue;

[0221] The request acquisition module 12 includes:

[0222] The first request acquiring unit 124 is configured to retrieve M object information acquiring requests to be merged from the N1 object information acquiring requests in the first request processing queue based on the first queue processing parameter.

[0223] wherein N2 object information acquisition requests among the N object information acquisition requests are added to the second request processing queue; N2 is a positive integer less than or equal to N, and the sum of N1 and N2 is equal to N; and the queue processing parameter includes a second queue processing parameter for the second request processing queue;

[0224] The request acquisition module 12 includes:

[0225] The second request acquiring unit 125 is configured to retrieve M object information acquiring requests to be merged from the N2 object information acquiring requests in the second request processing sub-queue based on the second queue processing parameter.

[0226] Wherein, if the virtual business object includes a virtual object whose field of view has changed and whose field of view change range is determined, the target request object is a second virtual object within the field of view change range of the virtual business object;

[0227] The data processing module 14 is further configured to:

[0228] obtaining second object information of the second virtual object based on the merge processing request;

[0229] The second object information is determined as the object information of the target request object.

[0230] The specific implementations of the queue determination module 11, the request acquisition module 12, the information acquisition module 13, the data processing module 14, and the object notification module 15 can be found in the relevant descriptions of the above embodiments and will not be further elaborated here. It should be understood that the description of the beneficial effects obtained by adopting the same method will also not be repeated.

[0231] In the embodiments of the present application, the term "module" or "unit" refers to a computer program or a part of a computer program that has a predetermined function and works together with other related parts to achieve a predetermined goal, and can be implemented in whole or in part by using software, hardware (such as processing circuits or memories) or a combination thereof. Similarly, a processor (or multiple processors or memories) can be used to implement one or more modules or units. In addition, each module or unit can be part of an overall module or unit that includes the function of the module or unit.

[0232] Further, see Figure 16 , Figure 16 This is a schematic diagram of the structure of a computer device provided in an embodiment of the present application. Figure 16 As shown, the computer device 1400 can be a business terminal or a server, and will not be limited here. For ease of understanding, this application takes the computer device as a server as an example. The computer device 1400 may include: a processor 1401, a network interface 1404 and a memory 1405. In addition, the computer device 1400 may also include: a user interface 1403, and at least one communication bus 1402. Among them, the communication bus 1402 is used to realize the connection and communication between these components. Among them, the user interface 1403 may also include a standard wired interface and a wireless interface. The network interface 1404 may optionally include a standard wired interface and a wireless interface (such as a WI-FI interface). The memory 1405 may be a high-speed RAM memory or a non-volatile memory (non-volatile memory), such as at least one disk storage. The memory 1405 may optionally also be at least one storage device located away from the aforementioned processor 1401. As Figure 14 As shown, the memory 1405 as a computer-readable storage medium may include an operating system, a network communication module, a user interface module, and a device control application.

[0233] The network interface 1404 in the computer device 1400 can also provide a network data interaction function. Figure 16 In the computer device 1400 shown, the network interface 1404 can provide network data interaction functions; the user interface 1403 is mainly used to provide an input interface for the user; and the processor 1401 can be used to call the device control application stored in the memory 1405 to execute the above Figure 6 and Figure 9 The description of the object information processing method in the corresponding embodiment can also be performed Figure 15 The description of the object information processing device 1 in the corresponding embodiment will not be repeated here. In addition, the description of the beneficial effects of adopting the same method will not be repeated here either.

[0234] In one possible implementation, the memory 1405 is used to store program instructions. The processor 1401 may call the program instructions to perform the following steps:

[0235] Determining a request processing queue associated with a target request object; the request processing queue includes N object information acquisition requests, where N is a positive integer greater than 1, and each object information acquisition request is a request sent by a virtual business object to obtain object information of the target request object; wherein, if the target request object is a first virtual object, the virtual business objects include virtual objects within a field of view change range of the first virtual object, where the field of view change range refers to a range determined by the business server when detecting that the object field of view range of the first virtual object has changed from a first field of view range to a second field of view range;

[0236] Obtaining queue processing parameters associated with a request processing queue, obtaining M object information acquisition requests to be merged from the N object information acquisition requests based on the queue processing parameters, and determining the M virtual business objects that sent the M object information acquisition requests as merged virtual objects; where M is a positive integer less than or equal to N;

[0237] Performing request merging processing on the M object information acquisition requests to obtain a merged processing request, obtaining first object information of the first virtual object based on the merged processing request, and determining the first object information as the object information of the target request object;

[0238] Based on the object information of the target request object, a request data packet is generated for sending to the merged processing virtual object.

[0239] The queue processing parameters include the request processing ratio and the minimum request processing quantity for the request processing queue;

[0240] When the processor 1401 is configured to obtain M object information acquisition requests to be merged from N object information acquisition requests based on the queue processing parameter, the processor 1401 is specifically configured to:

[0241] Determine an initial processing quantity for the request processing queue based on the request processing ratio and the number of N object information acquisition requests in the request processing queue; the initial processing quantity is a positive integer less than N;

[0242] If the initial processing quantity is greater than or equal to the minimum request processing quantity, the initial processing quantity is used as the target processing quantity for the request processing queue;

[0243] Based on the target processing quantity, M object information acquisition requests to be merged are obtained from the N object information acquisition requests in the request processing queue; M is consistent with the target processing quantity.

[0244] The processor 1401 is further configured to:

[0245] If the initial processing quantity is less than the minimum requested processing quantity, the minimum requested processing quantity will be used as the target processing quantity.

[0246] The processor 1401 is further configured to:

[0247] Generate entry-view notification information for the target request object; the entry-view notification information is used to notify the virtual business object that the target request object has entered the object view range of the virtual business object;

[0248] The entry-in-view notification information is sent to the virtual business object, so that the virtual business object sends an object information acquisition request for the target request object to the business server based on the entry-in-view notification information.

[0249] The processor 1401 is further configured to:

[0250] When receiving the object information acquisition request sent by the virtual business object and determining that the virtual area indicated by the object field of view of the virtual business object belongs to the object aggregation area, the object information acquisition request sent by the virtual business object is added to the request processing queue.

[0251] The virtual area indicated by the first visual field includes R1 first virtual sub-areas; the first virtual object is located on a first target virtual sub-area in the R1 first virtual sub-areas; R1 is a positive integer;

[0252] The processor 1401 is further configured to:

[0253] When it is detected that the first virtual object crosses from the first target virtual sub-region to the second target virtual sub-region, determining that the object field of view of the first virtual object is changed from the first field of view to the second field of view corresponding to the second target virtual sub-region; the virtual region indicated by the second field of view includes R2 second virtual sub-regions; the second target virtual sub-region belongs to the R2 second virtual sub-regions; and R2 is a positive integer;

[0254] A second virtual sub-region that is different from the R1 first virtual sub-regions is determined from the R2 second virtual sub-regions, and a field of view range indicated by the determined second virtual sub-region is used as a field of view change range.

[0255] The processor 1401 is further configured to:

[0256] Determine a first virtual sub-region that is different from the R2 first virtual sub-regions from the R1 second virtual sub-regions, and use the field of view indicated by the determined first virtual sub-region as the field of view exit range of the first virtual object;

[0257] The virtual object that is out of the field of view is regarded as the third virtual object;

[0258] Generate out-of-view notification information for the first virtual object; the out-of-view notification information is used to notify a third virtual object that the first virtual object has left the object's field of view of the third virtual object;

[0259] The out-of-view notification information is sent to the third virtual object.

[0260] The N object information acquisition requests include an object information acquisition request i; i is a positive integer less than or equal to N; the virtual business object that sends the object information acquisition request i is a reference virtual object; the request processing queue includes a first request processing queue;

[0261] The processor 1401 is further configured to:

[0262] Obtaining the object distance between the reference virtual object and the target request object;

[0263] If the object distance is within the first distance range associated with the first request processing queue, the object information acquisition request i is added to the first request processing queue.

[0264] Wherein, the request processing queue includes a second request processing queue;

[0265] The processor 1401 is further configured to:

[0266] If the object distance is within the second distance range associated with the second request processing queue, the object information acquisition request i is added to the second request processing queue.

[0267] When used to determine the request processing queue associated with the target request object, the processor 1401 is specifically used to:

[0268] Upon reaching a first processing timestamp for the first request processing queue, determining the first request processing queue;

[0269] upon reaching a second processing timestamp for the second request processing queue, determining the second request processing queue;

[0270] If the maximum distance value indicated by the first distance range is less than or equal to the minimum distance value indicated by the second distance range, the arrival frequency of the first processing timestamp is higher than the arrival frequency of the second processing timestamp.

[0271] Wherein, N1 object information acquisition requests among the N object information acquisition requests are added to the first request processing queue; N1 is a positive integer less than or equal to N; the queue processing parameter includes a first queue processing parameter for the first request processing queue;

[0272] When the processor 1401 is configured to obtain M object information acquisition requests to be merged from N object information acquisition requests based on the queue processing parameter, the processor 1401 is specifically configured to:

[0273] Based on the first queue processing parameter, M object information acquisition requests to be merged are taken out from the N1 object information acquisition requests in the first request processing queue.

[0274] wherein N2 object information acquisition requests among the N object information acquisition requests are added to the second request processing queue; N2 is a positive integer less than or equal to N, and the sum of N1 and N2 is equal to N; and the queue processing parameter includes a second queue processing parameter for the second request processing queue;

[0275] When the processor 1401 is configured to obtain M object information acquisition requests to be merged from N object information acquisition requests based on the queue processing parameter, the processor 1401 is specifically configured to:

[0276] Based on the second queue processing parameter, M object information acquisition requests to be merged are taken out from the N2 object information acquisition requests in the second request processing sub-queue.

[0277] Wherein, if the virtual business object includes a virtual object whose field of view has changed and whose field of view change range is determined, the target request object is a second virtual object within the field of view change range of the virtual business object;

[0278] The processor 1401 is further configured to:

[0279] obtaining second object information of the second virtual object based on the merge processing request;

[0280] The second object information is determined as the object information of the target request object.

[0281] In addition, it should be pointed out here that: the embodiment of the present application also provides a computer-readable storage medium, and the computer-readable storage medium stores the computer program executed by the object information processing device 1 mentioned above, and the computer program includes a computer program, when the processor executes the computer program, it can execute the above-mentioned Figure 6 and Figure 9The description of the object information processing method in the corresponding embodiment will therefore not be repeated here. In addition, the description of the beneficial effects of adopting the same method will not be repeated. For technical details not disclosed in the computer-readable storage medium embodiment involved in this application, please refer to the description of the method embodiment of this application. As an example, the computer program can be deployed on a computing device for execution, or on multiple computing devices located in one location, or on multiple computing devices distributed in multiple locations and interconnected by a communication network. Multiple computing devices distributed in multiple locations and interconnected by a communication network can constitute a blockchain system.

[0282] In addition, it should be noted that: the embodiment of the present application also provides a computer program product, which includes a computer program, which can be stored in a computer-readable storage medium. The processor of the computer device reads the computer program from the computer-readable storage medium, and the processor can execute the computer program, so that the computer device performs the above Figure 6 and Figure 9 The description of the object information processing method in the corresponding embodiment will not be repeated here. In addition, the description of the beneficial effects of using the same method will not be repeated here. For technical details not disclosed in the computer program product embodiment involved in this application, please refer to the description of the method embodiment of this application.

[0283] It should be noted that for the aforementioned various method embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that this application is not limited by the order of the actions described, because according to this application, some steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by this application.

[0284] The steps in the method of the embodiment of the present application can be adjusted in order, combined and deleted according to actual needs.

[0285] The modules in the device of the embodiment of the present application can be merged, divided and deleted according to actual needs.

[0286] Those skilled in the art will appreciate that all or part of the processes in the above-described method embodiments can be implemented by instructing related hardware through a computer program. The computer program can be stored in a computer-readable storage medium. When executed, the program can include the processes in the above-described method embodiments. The storage medium can be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

[0287] The above disclosure is only a preferred embodiment of the present application, and certainly cannot be used to limit the scope of rights of the present application. Therefore, equivalent changes made according to the claims of the present application are still within the scope covered by the present application.

Claims

1. A method for processing object information, characterized in that: The method is executed by a service server, and includes: Determining a request processing queue associated with a target request object; the request processing queue includes N object information acquisition requests, where N is a positive integer greater than 1, and one object information acquisition request is a request sent by a virtual business object to obtain object information of the target request object; wherein, if the target request object is a first virtual object, the virtual business objects include virtual objects within a field of view change range of the first virtual object, where the field of view change range is determined by the business server when detecting that the object field of view range of the first virtual object has changed from a first field of view range to a second field of view range; Obtaining a queue processing parameter associated with the request processing queue, obtaining M object information acquisition requests to be merged from the N object information acquisition requests based on the queue processing parameter, and determining the M virtual business objects that sent the M object information acquisition requests as merged processing virtual objects, where M is a positive integer less than or equal to N; performing request merging processing on the M object information acquisition requests to obtain a merged processing request, obtaining first object information of the first virtual object based on the merged processing request, and determining the first object information as the object information of the target request object; Based on the object information of the target request object, a request data packet is generated for sending to the merged virtual object.

2. The method according to claim 1, characterized in that The queue processing parameters include a request processing ratio and a minimum request processing quantity for the request processing queue; The acquiring, based on the queue processing parameter, M object information acquisition requests to be merged from the N object information acquisition requests includes: Determining an initial processing quantity for the request processing queue based on the request processing ratio and the number of N object information acquisition requests in the request processing queue; the initial processing quantity is a positive integer less than N; If the initial processing quantity is greater than or equal to the minimum request processing quantity, the initial processing quantity is used as the target processing quantity for the request processing queue; Based on the target processing quantity, M object information acquisition requests to be merged are acquired from the N object information acquisition requests in the request processing queue; M is consistent with the target processing quantity.

3. The method according to claim 2, characterized in that The method further comprises: If the initial processing quantity is less than the minimum requested processing quantity, the minimum requested processing quantity is used as the target processing quantity.

4. The method according to claim 1, wherein The method further comprises: generating entry-in-view notification information for the target request object; the entry-in-view notification information is used to notify the virtual business object that the target request object has entered the object field of view of the virtual business object; The entry-in-view notification information is sent to the virtual business object, so that the virtual business object sends an object information acquisition request for the target request object to the business server based on the entry-in-view notification information.

5. The method according to claim 4, characterized in that The method further comprises: Upon receiving the object information acquisition request sent by the virtual business object and determining that the virtual area indicated by the object field of view of the virtual business object belongs to the object aggregation area, the object information acquisition request sent by the virtual business object is added to the request processing queue.

6. The method according to claim 1, characterized in that The virtual area indicated by the first field of view includes R1 first virtual sub-areas; the first virtual object is located on a first target virtual sub-area in the R1 first virtual sub-areas; R1 is a positive integer; The method further comprises: When detecting that the first virtual object crosses from the first target virtual sub-region to the second target virtual sub-region, determining that the object field of view of the first virtual object is changed from the first field of view to a second field of view corresponding to the second target virtual sub-region; the virtual region indicated by the second field of view includes R2 second virtual sub-regions; the second target virtual sub-region belongs to the R2 second virtual sub-regions; and R2 is a positive integer; A second virtual sub-region different from the R1 first virtual sub-regions is determined from the R2 second virtual sub-regions, and a field of view range indicated by the determined second virtual sub-region is used as the field of view change range.

7. The method according to claim 6, characterized in that The method further comprises: Determining a first virtual sub-region different from the R2 first virtual sub-regions from the R1 second virtual sub-regions, and using a field of view range indicated by the determined first virtual sub-region as a field of view exit range of the first virtual object; Using the virtual object within the visual field exit range as the third virtual object; generating out-of-view notification information for the first virtual object; wherein the out-of-view notification information is used to notify the third virtual object that the first virtual object has left the object field of view of the third virtual object; The out-of-field notification information is sent to the third virtual object.

8. The method according to claim 1, characterized in that The N object information acquisition requests include an object information acquisition request i; i is a positive integer less than or equal to N; the virtual business object that sends the object information acquisition request i is a reference virtual object; the request processing queue includes a first request processing queue; The method further comprises: Acquiring an object distance between the reference virtual object and the target request object; If the object distance is within a first distance range associated with the first request processing queue, the object information acquisition request i is added to the first request processing queue.

9. The method according to claim 8, characterized in that The request processing queue includes a second request processing queue; The method further comprises: If the object distance is within the second distance range associated with the second request processing queue, the object information acquisition request i is added to the second request processing queue.

10. The method according to claim 9, characterized in that Determining a request processing queue associated with the target request object includes: upon reaching a first processing timestamp for the first request processing queue, determining the first request processing queue; upon reaching a second processing timestamp for the second request processing queue, determining the second request processing queue; If the maximum distance value indicated by the first distance range is less than or equal to the minimum distance value indicated by the second distance range, the arrival frequency of the first processing timestamp is higher than the arrival frequency of the second processing timestamp.

11. The method according to claim 9, characterized in that N1 object information acquisition requests among the N object information acquisition requests are added to the first request processing queue; N1 is a positive integer less than or equal to N; the queue processing parameters include a first queue processing parameter for the first request processing queue; The acquiring, based on the queue processing parameter, M object information acquisition requests to be merged from the N object information acquisition requests includes: Based on the first queue processing parameter, M object information acquisition requests to be merged are taken out from the N1 object information acquisition requests in the first request processing queue.

12. The method according to claim 11, characterized in that N2 object information acquisition requests among the N object information acquisition requests are added to the second request processing queue; N2 is a positive integer less than or equal to N, and the sum of N1 and N2 is equal to N; The queue processing parameters include second queue processing parameters for the second request processing queue; The acquiring, based on the queue processing parameter, M object information acquisition requests to be merged from the N object information acquisition requests includes: Based on the second queue processing parameter, M object information acquisition requests to be merged are taken out from the N2 object information acquisition requests in the second request processing sub-queue.

13. The method according to claim 1, wherein If the virtual business object includes a virtual object whose field of view has changed and whose field of view change range has been determined, the target request object is a second virtual object within the field of view change range of the virtual business object; The method further comprises: acquiring second object information of the second virtual object based on the merge processing request; The second object information is determined as the object information of the target request object.

14. An object information processing device, characterized in that: The device runs on a service server and includes: a queue determination module, configured to determine a request processing queue associated with a target request object; the request processing queue including N object information acquisition requests, where N is a positive integer greater than 1, and each object information acquisition request is a request sent by a virtual business object to obtain object information of the target request object; wherein, if the target request object is a first virtual object, the virtual business objects include virtual objects within a field of view change range of the first virtual object, where the field of view change range is determined by the business server upon detecting that the object field of view range of the first virtual object has changed from a first field of view range to a second field of view range; a request acquisition module, configured to acquire queue processing parameters associated with the request processing queue, acquire M object information acquisition requests to be merged from the N object information acquisition requests based on the queue processing parameters, and determine the M virtual business objects that sent the M object information acquisition requests as merged virtual objects; M is a positive integer less than or equal to N; an information acquisition module, configured to perform request merging processing on the M object information acquisition requests to obtain a merged processing request, obtain first object information of the first virtual object based on the merged processing request, and determine the first object information as the object information of the target request object; The data processing module is used to generate a request data packet for sending to the merged processing virtual object based on the object information of the target request object.

15. A computer device, characterized in that: including memory and processor; The memory is connected to the processor, the memory is used to store a computer program, and the processor is used to call the computer program so that the computer device executes the method according to any one of claims 1 to 13.

16. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, which is suitable for being loaded and executed by a processor, so that a computer device having the processor executes the method according to any one of claims 1 to 13.

17. A computer program product, characterized in that The invention comprises a computer program, which implements the method according to any one of claims 1 to 13 when executed by a processor.

Images