Data testing method for wireless network high-level protocol, computing device, chip, computer readable storage medium and computer program product

Abstract

The invention provides a data testing method for a wireless network high-level protocol, computing equipment, a chip, a computer readable storage medium and a computer program product, and relates to the technical field of communication. The data testing method for the wireless network high-level protocol comprises the steps that a corresponding control interface and a corresponding data interface are provided for each layer in multiple layers of a high-level protocol stack, the multiple layers are configured to carry out data processing according to the high-level protocol and carry out interlayer data transmission according to the hierarchical structure of the multiple layers, the control interface is configured to selectively start a data test mode of a corresponding layer in the plurality of layers, and the data interface is configured to perform data interaction with the corresponding layer in the plurality of layers; in response to a data test mode of any one of the plurality of layers being enabled via the control interface of the layer, a layer higher than the layer in the hierarchical structure is bypassed via data interaction with the layer via the data interface of the layer.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a data testing method, computing device, chip, computer-readable storage medium, and computer program product for a wireless network high-layer protocol. Background Art

[0002] Data testing of higher-layer protocols (those above the physical layer) is an essential step in wireless network testing. Currently, in major higher-layer protocol data testing, test equipment constructs data using a real or simulated higher-layer protocol stack (such as the Layer 2 protocol stack). Because the protocol stack complies with the core specifications for wireless network higher-layer protocols, in actual use, the upper-layer test control unit configures the necessary parameters for the protocol stack. The higher-layer protocol stack then generates the corresponding data for uplink and downlink transmission according to the core specifications. This makes it difficult to control the data under test. In this article, the term "core specification" refers to the 3GPP standard's higher-layer technical specifications for wireless access networks, and the term "high-layer protocol stack" refers to the software written to comply with the core specifications' requirements for data processing at each higher-layer protocol layer. Summary of the Invention

[0003] To alleviate, mitigate or eliminate the above technical problems, the present disclosure provides a data testing method, computing device, chip, computer-readable storage medium and computer program product for a wireless network high-layer protocol.

[0004] In a first aspect, the present disclosure provides a data testing method for a wireless network high-level protocol, comprising: providing a corresponding control interface and a corresponding data interface for each of a plurality of layers of a high-level protocol stack, wherein the plurality of layers are configured to perform data processing according to the high-level protocol and to perform inter-layer data transmission according to the hierarchical structure of the plurality of layers, the control interface is configured to selectively enable a data test mode of a corresponding layer of the plurality of layers, and the data interface is configured to perform data exchange with the corresponding layer of the plurality of layers; In response to a data test mode of any layer among the plurality of layers being enabled via the control interface of the layer, data is interacted with the layer via the data interface of the layer to bypass layers higher than the layer in the hierarchical structure.

[0005] In a second aspect, the present disclosure provides a computing device. The computing device includes: one or more processors; and one or more memories coupled to the one or more processors and storing instructions thereon. When the instructions are executed individually or collectively by the one or more processors, the computing device performs the method described in the first aspect.

[0006] In a third aspect, the present disclosure provides a chip, which includes a circuit system configured to execute the method described in the first aspect.

[0007] In a fourth aspect, the present disclosure provides a non-transitory computer-readable storage medium storing machine-executable instructions, wherein when the machine-executable instructions are executed by one or more processors of a machine, the machine is caused to perform the method of the first aspect.

[0008] In a fifth aspect, the present disclosure provides a computer program product comprising machine-executable instructions, wherein when the machine-executable instructions are executed by one or more processors of a machine, the machine is caused to perform the method according to the first aspect.

[0009] It should be understood that the invention summary is not intended to identify the key or essential features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The above and other objects, features and advantages of the present disclosure will become more apparent through a more detailed description of some embodiments of the present disclosure in the accompanying drawings, in which: Figure 1 illustrates an exemplary communication network in which exemplary embodiments of the present disclosure may be implemented; Figure 2 A schematic flow chart showing a method for testing data of a wireless network high-layer protocol according to some embodiments of the present disclosure is shown; Figure 3 An exemplary L2 protocol stack is shown in which exemplary embodiments of the present disclosure may be implemented; Figure 4 An exemplary test system is shown in which exemplary embodiments of the present disclosure may be implemented; Figure 5 shows a schematic diagram of data generation according to some embodiments of the present disclosure; Figure 6 A simplified block diagram of a test device suitable for implementing the exemplary embodiments of the present disclosure is shown. DETAILED DESCRIPTION

[0011] The principle of the present disclosure will now be described with reference to some embodiments. It should be understood that the description of these embodiments is merely for illustrative purposes and helps those skilled in the art to understand and implement the present disclosure without placing any restriction on the scope of the present disclosure. The disclosure described herein can be implemented in a manner different from that described below.

[0012] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0013] References herein to "one embodiment," "an embodiment," "an exemplary embodiment," etc., indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with an exemplary embodiment, those skilled in the art will recognize that such feature, structure, or characteristic may be combined with other embodiments, whether or not explicitly described.

[0014] It should be understood that although the terms "first" and "second" and the like may be used herein to describe various objects, these objects should not be limited by these terms. These terms are merely used to distinguish one object from another. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element, without departing from the scope of the exemplary embodiments. The term "and / or" as used herein includes any and all combinations of one or more of the listed terms.

[0015] The terms used herein are intended only to describe specific embodiments and are not intended to limit exemplary embodiments. As used herein, the singular forms "a," "an," and "the" also include the plural forms, unless the context clearly indicates otherwise. As used herein, "a group of elements" or "a set of elements" is intended to include one or more elements. It should also be understood that the terms "comprise," "include," "have," "have," "include," and / or "comprising," when used herein, specify the presence of the features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.

[0016] As used herein, the term "circuitry" may refer to one or more or all of the following: (a) Hardware circuit implementation only (e.g., implementation only in analog and / or digital circuits) (b) a combination of hardware circuitry and software, such as (where applicable): (i) a combination of analog and / or digital hardware circuitry and software / firmware; and (ii) any portion of a hardware processor (including a digital signal processor) with software, software, and memory that work together to enable a device such as a mobile phone or server to perform various functions, and (c) Hardware circuits and / or processors, such as a microprocessor or portion of a microprocessor, that require software (eg, firmware) to operate, but where software is not required for operation, the software may not be present.

[0017] This definition of circuitry applies to all uses of this term herein, including in any claims. As another example, as used herein, the term circuitry also includes an implementation of merely a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also includes, for example, a baseband integrated circuit or processor integrated circuit for a mobile device, or a similar integrated circuit in a server, cellular network device, or other computing network device, if applicable to the particular claimed element.

[0018] As used herein, the term "communication network" refers to a network that complies with any appropriate communication standard, such as Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), New Radio (NR), Non-Terrestrial Network (NTN), etc. Furthermore, communications between terminal devices and network devices in a communication network may be performed according to any appropriate generation of communication protocols, including but not limited to first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G), future sixth generation (6G) communication protocols, and / or any other protocols currently known or to be developed in the future. Embodiments of the present disclosure may be applied to satellite communication systems. Given the rapid developments in communications, future generations of communication technologies and systems will undoubtedly exist, and embodiments of the present disclosure may be implemented using these technologies and systems. The scope of the present disclosure should not be considered limited to the aforementioned systems.

[0019] The term "satellite network equipment" refers to a node located on a satellite or in the ground segment of a satellite communications network. Terminal devices access the network and receive services through this node. Depending on the terminology and technology used, satellite network equipment can refer to a base station (BS) or access point (AP) as a satellite payload, such as a NodeB (NB), an evolved NodeB (eNodeB or eNB), a NR NB (also known as a gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), or a relay node. An example of a relay node is an integrated access and backhaul (IAB) node. The distributed unit (DU) portion of an IAB node can perform the functions of a "satellite network equipment" and therefore operate as a network device. In the following description, the terms "satellite network equipment," "BS," and "node" are used interchangeably.

[0020] The term "terminal device" refers to any terminal device capable of wireless communication. By way of example and not limitation, a terminal device may also be referred to as a communication device, user equipment (UE), subscriber station (SS), portable subscriber station, mobile station (MS), or access terminal (AT). The terminal device may include, but is not limited to, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet computer, a wearable terminal device, a personal digital assistant (PDA), a portable computer, a desktop computer, an image capture terminal device such as a digital camera, a gaming terminal device, a music storage and playback device, an in-vehicle wireless terminal device, a wireless endpoint, a mobile station, a notebook embedded device (LEE), a laptop mounted device (LME), a USB dongle, a smart device, a wireless user equipment (CPE), an Internet of Things (IoT) device, a watch or other wearable device, a head-mounted display (HMD), a vehicle, a drone, medical equipment and applications (e.g., remote surgery), industrial equipment and applications (e.g., robots and / or other wireless devices operating in the context of an industrial and / or automated process chain), consumer electronic devices, relay nodes, devices operating on commercial and / or industrial wireless networks, and the like. The mobile terminal (MT) portion of the IAB node can perform the functions of a "terminal device" and can therefore operate as a terminal device. In the following description, the terms "terminal device", "communication device", "terminal", "user equipment" and "UE" can be used interchangeably.

[0021] While the functionality described herein may be performed in fixed and / or wireless network nodes in various exemplary embodiments, in other exemplary embodiments, the functionality may be implemented in a user equipment device (such as a cell phone, tablet computer, laptop computer, desktop computer, mobile IoT device, or fixed IoT device). For example, the user equipment device may appropriately have the corresponding capabilities described in connection with fixed and / or wireless network nodes. The user equipment device may be a user device and / or a control device, such as a chipset or processor, configured to control the user device when installed therein. Examples of these functions include boot server functionality and / or home subscriber server functionality, which may be implemented in the user equipment device by providing the user equipment device with software configured to cause the user equipment device to perform from the perspective of these functions / nodes.

[0022] Figure 1An exemplary communication network 100 is shown in which embodiments of the present disclosure may be implemented. The communication network 100 includes a satellite network device 110 and terminal devices 120A and 120B served by the satellite network device 110. The terminal devices 120A and 120B may also be collectively referred to as terminal devices 120. The communication network 100 may provide a serving cell 130 to serve the terminal devices 120A and 120B. Figure 1 In the example of FIG, as a satellite communication network, the communication network 100 further includes a ground station 140, a gNB 150, a next-generation core network NGC 160, and a data network 170. The satellite communication network may include a low-orbit satellite (LEO), a medium-orbit satellite (MEO), or a geosynchronous orbit satellite (GEO).

[0023] The ground station 140 acts as a gateway for connecting non-terrestrial networks and public data networks. The gNB 150 acts as an access network, connecting the ground station 140 to the core network NGC 160. The NGC 160 can also be connected to the data network 170 to provide, for example, Internet content services. It will be understood that the communication network 100 is not required to include Figure 1 All elements shown in .

[0024] In some embodiments, satellite network device 110 can function as a base station to communicate with terminal devices 120A and 120B, or as a transparent forwarding node to transparently transmit signals sent by ground station 140 to terminal devices 120A and 120B. In the former case, satellite network device 110 possesses all or some of the functions of a base station. For example, satellite network device 110 can be a gNB or gNB-DU. Satellite network device 110 with gNB functionality can be equipped with or without an inter-satellite link (ISL). In the case of a transparent forwarding node, satellite network device 110 performs only transparent forwarding.

[0025] It should be understood that the number of satellite network devices 110, terminal devices 120A and 120B, and serving cells 130 is for illustrative purposes only and is not intended to be limiting. Communication network 100 may include any suitable number of satellite network devices, terminal devices, and serving cells suitable for implementing embodiments of the present disclosure. It should be noted that the terms "cell" and "serving cell" are used interchangeably herein.

[0026] In communication network 100, satellite network device 110 can transmit data and control information to terminal devices 120A and 120B, and terminal devices 120A and 120B can also transmit data and control information to satellite network device 110. The link from satellite network device 110 to terminal devices 120A and 120B is called a downlink (DL) or forward link, and the link from terminal device 120 to satellite network device 110 is called an uplink (UL) or reverse link.

[0027] Communications in the communication network 100 may conform to any suitable standard, including, but not limited to, Long Term Evolution (LTE), LTE Evolution, LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), Code Division Multiple Access (CDMA), and Global System for Mobile Communications (GSM). Furthermore, communications may be performed in accordance with any generation of communication protocols currently known or developed in the future. Examples of communication protocols include, but are not limited to, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, fifth generation (5G), and sixth generation (6G) communication protocols.

[0028] The Third Generation Partnership Project (3GPP) protocol architecture includes the physical (PHY) layer and higher-level protocol layers. These layers include the media access control (MAC), radio link control (RLC), and packet data convergence protocol (PDCP). In this document, all layers above the physical layer are referred to as higher layers. Software written according to the core specifications for the data processing requirements of each higher-level protocol layer is referred to as the higher-level protocol stack. The higher-level protocol stack consists of one or more layers, each of which is configured to process data according to the higher-level protocol and transfer data between layers according to the layered structure.

[0029] In the current data testing of major high-level protocols, the high-level protocol stack usually generates the corresponding data for uplink and downlink transmission according to the requirements of the core specifications, making it difficult to control the data in the test. In addition, current data tests are mostly field tests or base station simulation tests, and the scenarios established in this way are mostly real network configurations or base station test scenarios with specified configurations. In this scenario, high-level data transmission is usually generated autonomously by the protocol stack, so the data content obtained is normal data content that matches the core specifications, and it is difficult to construct abnormal data content. If it is necessary to construct an abnormal scenario, it is necessary to use additional methods such as signal interference to enter the abnormal scenario. However, in this scenario, it is difficult to accurately control the actual abnormalities generated by the high-level protocol data. As a protocol test, it is difficult to conduct targeted testing on the specified rules of the core specification.

[0030] Figure 2 1 is a flow chart of a method 200 for testing data of a wireless network high layer protocol according to some embodiments of the present disclosure. It should be understood that the method 200 may include additional steps not shown and / or may omit some steps shown, and the scope of the present disclosure is not limited in this regard.

[0031] In step S210, a corresponding control interface and a corresponding data interface are provided for each of the multiple layers of the high-level protocol stack. The multiple layers of the high-level protocol stack are configured to process data according to the high-level protocol and transfer data between layers according to the hierarchical structure of the multiple layers. The control interface is configured to selectively enable a data test mode for a corresponding layer of the multiple layers, and the data interface is configured to exchange data with the corresponding layer of the multiple layers.

[0032] In the following description, the L2 protocol is used as an example for detailed description, but it should be understood that the high layer herein is not limited to L2.

[0033] Figure 3 An exemplary L2 protocol stack 300 in which embodiments of the present disclosure may be implemented is shown. The L2 protocol stack 300 includes a service data adaptation protocol (SDAP) layer 301, a packet data convergence protocol (PDCP) layer 302, a radio link control (RLC) layer 303, and a media access control (MAC) layer 304. These four layers are configured to process data according to the L2 protocol and transfer data between layers according to the hierarchical structure of the four layers.

[0034] In an exemplary embodiment, a corresponding control interface and a corresponding data interface are provided for each of the SDAP layer 301, PDCP layer 302, RLC layer 303, and MAC layer 304 of the L2 protocol stack 300. The control interface of the SDAP layer 301 is configured to selectively enable a data test mode of the SDAP layer 301, and the data interface is configured to exchange data with the SDAP layer 301. The control interface of the PDCP layer 302 is configured to selectively enable a data test mode of the PDCP layer 302, and the data interface is configured to exchange data with the PDCP layer 302. The control interface of the RLC layer 303 is configured to selectively enable a data test mode of the RLC layer 303, and the data interface is configured to exchange data with the RLC layer 303. The control interface of the MAC layer 304 is configured to selectively enable a data test mode of the MAC layer 304, and the data interface is configured to exchange data with the MAC layer 304.

[0035] Please refer to Figure 4 The test system 400 includes a test control unit 410 and an L2 protocol stack 300. The test control unit 410 is configured to manage the test process, send control instructions to each layer of the L2 protocol stack 300, and simulate the construction of L2 data. These control instructions primarily include cell establishment, link establishment at each layer of the protocol stack, and activation / deactivation of the data test mode switch. When the data test mode for the corresponding layer is enabled, the L2 protocol stack 300 switches the data upload and download channels between that layer and higher layers to the data channels connected to the test control unit 410.

[0036] In some embodiments, based on the standard L2 protocol, the layers of the L2 protocol stack 300 are divided into a control plane and a data plane. The control plane is configured to receive instructions from the test control unit 410 and is primarily used to create and delete radio link resources and logical channel resources at each layer, as well as configure channel-related parameters at each layer. The data plane is configured to process air interface data and perform parsing, packetization, and other processing on uplink and downlink data according to the requirements of the core specification.

[0037] Figure 4 In the illustrated embodiment, a data test mode switch is set in the control interface between the control plane of each layer of the L2 protocol stack 300 and the test control unit 410, and a new data interface is added for data exchange between the data plane of each layer and the test control unit 410. At the same time, the original functions of the data plane of each layer of the L2 protocol stack 300 and the data transmission interfaces and functions between data planes that comply with core specifications are retained. The newly added data interfaces of each layer of the L2 protocol stack 300 can only be used after the test control unit 410 activates the data test mode switch of the control plane of that layer.

[0038] In step S220 , in response to a data test mode of any layer among the multiple layers being enabled via the control interface of the layer, data is exchanged with the layer via the data interface of the layer to bypass layers higher than the layer in the hierarchical structure.

[0039] In this document, bypassing a layer higher than the layer in the hierarchy means that the layer does not exchange data with the layer higher than the layer.

[0040] In one exemplary embodiment, please refer to Figure 4 In response to the data test mode of the PDCP layer 302 being enabled via that layer's control interface, data is exchanged with that layer via that layer's data interface, bypassing the higher-level layer in the hierarchical structure (the SDAP layer 301). For example, after the test control unit 410 activates the control plane data test mode switch of the PDCP layer 302, the MAC layer 304 and the RLC layer 303, having not received the instruction to activate the data test mode, continue to process data and complete inter-layer transfers as required by the core specification. However, upon receiving data, the data plane of the PDCP layer 302, because it is in data test mode, will directly pass the data to the test control unit 410 via the newly added data interface, rather than uploading it to the SDAP layer 301. Similarly, the data plane of the PDCP layer 302 no longer receives data sent by the SDAP layer 301, but instead receives PDCP packets from the test control unit 410 via the newly added data interface and sends them to the RLC layer 303.

[0041] In some embodiments, exchanging data with the layer via the layer's data interface includes at least one of the following: constructing a data packet for the layer using a data construction function for the layer and sending the constructed data packet to the layer via the data interface; or receiving a data packet from the layer via the data interface. The data construction function includes a data processing function. Constructing the data packet for the layer includes constructing a data packet header for the data packet using the data processing function.

[0042] Please refer to Figure 4 In addition to constructing the user data payload, the data construction function of the test control unit 410 also constructs the data packet headers of each layer from the SDAP layer 301 to the MAC layer 304, and is selectively called according to the type of data test mode.

[0043] Figure 4In the illustrated embodiment, the data construction functions of the test control unit 410 are divided according to the hierarchical structure of the L2 protocol stack 300. SDAP data construction is a data construction function for the SDAP layer 301. PDCP data construction is a data construction function for the PDCP layer 302. RLC data construction is a data construction function for the RLC layer 303. MAC data construction is a data construction function for the MAC layer 304. The data construction functions for each layer include corresponding data processing functions, which are used to construct the data packet header of the corresponding layer. In some embodiments, the data construction functions for each layer also include corresponding exception field writing functions, which are used to construct the corresponding exception data packet.

[0044] In some embodiments, constructing a data packet for the layer further comprises: in response to receiving a modification to a field in the constructed data packet header, modifying the field to generate an abnormal data packet; and in response to not receiving the modification to the field in the constructed data packet header, abandoning the modification to generate a normal data packet. In some embodiments, modifying a field in the data packet header comprises at least one of the following: modifying a coded value of the field to exceed a predefined range; or modifying a data packet segment sequence number corresponding to the field.

[0045] When it is necessary to construct an abnormal scenario, field modifications can be made in the processed data packet header to achieve the construction of an abnormal data packet. In some embodiments, the abnormal data packet includes a field coding value abnormality or a data logic abnormality. Among them, the field coding value abnormality refers to the situation where the field value exceeds the range defined by the core specification. In this scenario, by removing the restrictions on the coding value check in the data packet encoder, the data packet encoder of the test control unit 410 can still complete the encoding and send the data packet, and check the terminal device's response to the abnormal data packet. The data logic abnormality means that the field values of the data packet are within the range, but the sending timing does not meet the requirements of the core specification, such as when sending multiple segments of packetized data, the segment sending order abnormality is constructed by rewriting the data packet segment sequence number, or the segment is lost. In this scenario, the data packet encoder of the test control unit 410 can complete the encoding and send the data packet, and check the terminal device's response to the abnormal data packet.

[0046] Please refer to Figure 5"Exception field writing" in the data construction functions of each layer is optional. SDAP layer data processing primarily includes QFI mapping calculation. PDCP layer data processing primarily includes PDCP sequence number calculation. RLC layer data processing primarily includes RLC sequence number calculation, RLC data packet indication, packet segmentation, and packet assembly. MAC layer data processing primarily includes packet list reading and generation, MAC CE generation, and MAC Padding generation. The normal processing procedures for these layer functions comply with the core specification requirements.

[0047] After completing its corresponding functional operations, each layer provides an additional exception field to write the function location to construct an exception packet (optional feature). Then, based on the current test mode, it can determine whether to send the packet (including normal packets and possible exception packets) directly to the L2 protocol stack or pass it to the next layer's data processing function.

[0048] In some embodiments, in response to a non-top layer data test mode in a hierarchical structure of multiple layers of a high-level protocol stack being enabled via the control interface of the layer, data of a data packet constructed by a data construction function of a layer above the layer is used as an input parameter of a data processing function of the layer, and a data packet for the layer is generated through the data processing function of the layer.

[0049] Continue to refer Figure 5 In one exemplary embodiment, the data test mode of the SDAP layer 301 of the L2 protocol stack 300 is enabled via the control interface of that layer. If the current test mode is SDAP mode, the data processing function of the SDAP layer 301 of the test control unit 410, after completing data generation, directly sends the data packet to the SDAP layer 301 of the L2 protocol stack 300. After receiving the data packet, the SDAP layer 301 of the L2 protocol stack 300 passes the data packet to the PDCP layer 302. In another exemplary embodiment, the data test mode of the PDCP layer 302 of the L2 protocol stack 300 is enabled via the control interface of that layer. If the current test mode is PDCP mode, the SDAP layer data generated by the data processing function of the SDAP layer 301 serves as an input parameter to the data processing function of the PDCP layer 302 of the test control unit 410. The data processing function of the PDCP layer 302 uses the SDAP layer data as a service data unit (SDU). After completing functions such as PDCP sequence number calculation, the data processing function of the PDCP layer 302 generates a PDCP protocol data unit (PDU) and sends it to the PDCP layer 302 of the L2 protocol stack 300. After receiving the data packet, the PDCP layer 302 of the L2 protocol stack 300 transfers the data packet to the RLC layer 303 .

[0050] In some embodiments, in response to the data test mode of any layer among multiple layers of a high-level protocol stack being enabled via the control interface of that layer, a data packet for that layer is constructed using a data construction function for that layer, and the type of the constructed data packet is identified, indicating whether that layer of the high-level protocol stack needs to process the data packet (such as by subpacketizing, grouping, etc.) before passing it to the next layer. The data packet type includes two types: a service data unit type and a protocol data unit type. Exemplarily, identifying the type of the constructed data packet as a service data unit type instructs the layer to process the received data packet before passing it to the next layer. Identifying the type of the constructed data packet as a protocol data unit type instructs the layer to pass the received data packet directly to the next layer.

[0051] Continue to refer Figure 5 In an exemplary embodiment, the data test mode of the SDAP layer 301 of the L2 protocol stack 300 is enabled via the control interface of the layer. If the current test mode is SDAP PDU mode, then after the data processing function of the SDAP layer 301 of the test control unit 410 completes data generation, it also identifies the data packet type as SDAP PDU. The data packet is then sent to the SDAP layer 301 of the L2 protocol stack 300 based on the data packet type. After receiving the data packet, the SDAP layer 301 of the L2 protocol stack 300 directly passes the data packet to the PDCP layer 302 based on the data packet type. Alternatively, if the current test mode is SDAPSDU mode, then after the data processing function of the SDAP layer 301 of the test control unit 410 completes data generation, it also identifies the data packet type as SDAP SDU. The data packet is then sent to the SDAP layer 301 of the L2 protocol stack 300 based on the data packet type. After receiving the data packet, the SDAP layer 301 of the L2 protocol stack 300 processes the data packet based on the data packet type before passing it to the PDCP layer 302.

[0052] The disclosed embodiments enable flexible control of data during data testing of wireless network high-layer protocols, enabling flexible construction of normal and / or abnormal data packets. This allows for convenient construction of information element (IE) items in the packet header at each layer, construction of abnormal data packets, and the flexible selection of retaining normal processing functions at certain layers, simplifying the complexity of packet construction.

[0053] In some embodiments, information indicating the time of packet delivery is further provided in the constructed data packet; and the data packet is sent to the higher-level protocol stack based on the delivery time. The delivery time of the data packet includes, for example, a frame number, a time slot number, etc. Exemplarily, the delivery time of the data packet is incorporated into the additional information portion of the data packet. When the higher-level protocol stack's runtime reaches a specified time, the data packet is sent to the higher-level protocol stack. Upon receiving the data packet, the higher-level protocol stack reads the additional information portion of the data packet and delivers the data packet based on the delivery time indicated therein.

[0054] In an exemplary embodiment, setting information in a data packet indicating the time of packet delivery includes: sending a control primitive to a higher-level protocol stack to query the current time (e.g., frame number); in response to receiving the current time as fed back by the higher-level protocol stack based on the control primitive, incrementing the received current time by a target increment to obtain the packet delivery time; and incorporating the obtained delivery time into the additional information portion of the data packet. In some embodiments, to improve compliance of the delivery time with protocol requirements, only the fed-back frame number may be used. The time slot number for the current downlink data may be generated by determining the time slot number corresponding to the downlink time slot based on the time slot allocation during cell establishment.

[0055] In another exemplary embodiment, setting information in a data packet to indicate the time point of sending the data packet includes: obtaining time information in the additional information part of the uplink data packet sent by the high-level protocol stack; obtaining the time point of sending the data packet based on the time information; and incorporating the obtained time point of sending into the additional information part of the data packet.

[0056] The embodiments of the present disclosure can control the time point of sending key data packets of concern in data testing, which is convenient for verifying time-related test items such as data channel timers.

[0057] The embodiment of the present disclosure also provides a chip. The chip includes a circuit system, which is configured to execute a reference Figure 2-Figure 5 Any process that is public in question.

[0058] Figure 6 FIG6 is a simplified block diagram of a device 600 suitable for implementing embodiments of the present disclosure. For example, satellite network device 110, terminal device 120, terminal device 220, and computing device may be implemented by device 600. As shown, device 600 includes one or more processors 610, one or more memories 620 coupled to processor 610, and one or more communication modules 640 coupled to processor 610.

[0059] The communication module 640 is used for two-way communication. The communication module 640 has at least one antenna to facilitate communication. The communication interface can represent any interface necessary for communicating with other network elements.

[0060] Processor 610 may be of any type suitable for the local technology network and may include, by way of non-limiting example, one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 600 may have multiple processors, such as application specific integrated circuit chips, which are driven in time to a clock that synchronizes the master processor.

[0061] Memory 620 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 624, electrically programmable read-only memory (EPROM), flash memory, hard disks, compact disks (CDs), digital video disks (DVDs), and other magnetic and / or optical memories. Examples of volatile memories include, but are not limited to, random access memory (RAM) 622 and other volatile memories that do not persist across a power outage.

[0062] Computer program 630 includes computer executable instructions for execution by associated processor 610. Program 630 may be stored in ROM 624. Processor 610 may perform any appropriate actions and processes by loading program 630 into RAM 622.

[0063] The embodiment of the present disclosure can be implemented by the program 630 so that the device 600 can execute the reference Figure 2-Figure 5 Any process of the disclosure discussed. The embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

[0064] In some embodiments, program 630 may be tangibly embodied on a computer-readable medium, which may be contained in device 600 (e.g., memory 620) or another storage device accessible to device 600. Device 600 may load program 630 from the computer-readable medium into RAM 622 for execution. The computer-readable medium may include any type of tangible, non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Program 630 is stored on the computer-readable medium.

[0065] In general, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Certain aspects may be implemented in hardware, while other aspects may be implemented in firmware or software, which may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are shown and described as block diagrams, flow charts, or using some other graphical representation, it should be understood that, as non-limiting examples, the blocks, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or a controller or other computing device, or some combination thereof.

[0066] The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer readable storage medium. The computer program product includes computer executable instructions, such as instructions included in program modules, which are executed in a device on a target real or virtual processor to perform the above-mentioned Figure 2-Figure 5 Any process disclosed herein. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform specific tasks or implement specific abstract data types. In various embodiments, the functionality of program modules can be combined or separated between program modules as needed. Machine-executable instructions for program modules can be executed on local or distributed devices. In distributed devices, program modules can be located in local and remote storage media.

[0067] The program code for executing the method for the disclosed embodiment can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller, a special-purpose computer or other programmable data processing equipment of a general-purpose computer so that when the program code is executed by the processor or controller, the function / operation specified in the flow chart and / or the block diagram is realized. The program code can be executed completely on the machine as an independent software package, partially on the machine, partially on the machine, partially on a remote machine, partially on a remote machine, or all on a remote machine or server.

[0068] In the context of this document, computer program codes or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform various processes and operations as described above. Examples of carriers include signals, computer-readable media, etc.

[0069] A computer-readable medium may be a computer-readable signal medium or a computer-readable storage medium. Computer-readable media may include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or apparatuses, or any suitable combination of the foregoing. More specific examples of computer-readable storage media include an electrical connection having one or more wires, a portable computer floppy disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0070] In addition, although operations are described in a specific order, this should not be understood as requiring that these operations be performed in the specific order or sequence shown, or that all operations shown be performed to obtain the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although several specific implementation details are included in the above discussion, these details should not be interpreted as limiting the scope of this disclosure, but rather as describing features specific to a particular embodiment. Some features described in the context of a separate embodiment may also be combined in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented individually or in any suitable subcombination in multiple embodiments.

[0071] Although the disclosure has been described in language specific to structural features and / or methodological acts, it should be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

[0072] It should be understood that the use of personally identifiable information should be subject to privacy policies and practices generally recognized as meeting or exceeding industry or government requirements for maintaining user privacy. In particular, personally identifiable information data should be managed and processed to minimize the risk of inadvertent or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

Claims

1. A data testing method for a wireless network high-level protocol, characterized in that: include: providing a corresponding control interface and a corresponding data interface for each of a plurality of layers of a high-level protocol stack, wherein the plurality of layers are configured to perform data processing according to the high-level protocol and to perform inter-layer data transmission according to the hierarchical structure of the plurality of layers, the control interface is configured to selectively enable a data test mode of a corresponding layer of the plurality of layers, and the data interface is configured to perform data exchange with the corresponding layer of the plurality of layers; In response to a data test mode of any layer among the plurality of layers being enabled via the control interface of the layer, data is interacted with the layer via the data interface of the layer to bypass layers higher than the layer in the hierarchical structure.

2. The method according to claim 1, wherein The data interaction with the layer via the data interface of the layer includes at least one of the following: constructing a data packet for the layer by using a data construction function for the layer and sending the constructed data packet to the layer via the data interface; Data packets from this layer are received via the data interface.

3. The method according to claim 2, wherein The data construction function includes a data processing function, and the construction of the data packet for this layer includes: The data packet header of the data packet is constructed through the data processing function.

4. The method according to claim 3, wherein The data packet for the layer is constructed and further comprises: In response to receiving a modification to a field in the constructed data packet header, modifying the field to generate an abnormal data packet; and In response to not receiving a modification to a field in the constructed data packet header, abandoning the modification to the field to generate a normal data packet.

5. The method according to claim 4, wherein The modifying of the field comprises at least one of the following: Modify the code value of the field to be outside the predefined range; Modify the data packet segment sequence number corresponding to the field.

6. The method according to any one of claims 3 to 5, wherein: Any layer is a non-top layer in the hierarchical structure, and constructing a data packet for the layer includes: The data of the data packet constructed by the data construction function of the layer above this layer is used as the input parameter of the data processing function of this layer, and the data packet for this layer is generated by the data processing function of this layer.

7. The method according to any one of claims 2 to 5, wherein: The constructing of the data packet for the layer includes at least one of the following: Identifies the constructed data packet as a service data unit type, indicating that the layer will process the received data packet before passing it to the next layer; Identifies the type of the constructed data packet as a protocol data unit type, instructing the layer to pass the received data packet directly to the next layer.

8. The method according to any one of claims 2 to 5, wherein: Also includes: Setting information in the data packet for indicating a time point at which the data packet is to be sent; as well as The data packet is sent to the high-level protocol stack according to the sending time point.

9. The method according to claim 8, wherein The information set in the data packet for indicating the time point of sending the data packet includes: Sending a control primitive for querying the current time point to the high-level protocol stack; In response to receiving the current time point fed back by the high-level protocol stack according to the control primitive, increasing the received current time point by a target increment to obtain a time point for sending the data packet; and The obtained sending time point is compiled into the additional information part of the data packet.

10. The method according to claim 9, wherein The current time point includes a frame number.

11. The method according to claim 8, wherein The information set in the data packet for indicating the time point of sending the data packet includes: Acquire time information in the additional information portion of the uplink data packet sent by the high-level protocol stack; Obtaining a time point for sending the data packet according to the time information; and The obtained sending time point is compiled into the additional information part of the data packet.

12. A computing device, characterized in that: include: one or more processors; as well as One or more memories coupled to the one or more processors and storing thereon instructions, which, when executed individually or collectively by the one or more processors, cause the computing device to perform the method of any one of claims 1-11.

13. A chip, characterized in that: The method comprises a circuit system configured to perform the method of any one of claims 1-11.

14. A non-transitory computer-readable storage medium storing machine-executable instructions, which, when executed by one or more processors of a machine, cause the machine to perform the method of any one of claims 1-11.

15. A computer program product comprising machine-executable instructions which, when executed by one or more processors of a machine, cause the machine to perform the method of any one of claims 1-11.

Images