State parameter processing method and device, and network equipment

Abstract

The embodiment of the present application provides a state parameter processing method and apparatus, and network equipment. The method is applied to an access network element, and includes: receiving target information sent by a core network element, and obtaining a first state parameter included in the target information; the first state parameter includes a data flow identifier and a first sequence number; the first sequence number is a sequence number corresponding to the transmission order of the first data packet transmitted by the core network element via the target transmission interface; based on the first sequence number, generating a second state parameter of the target data flow corresponding to the data flow identifier; and updating the third state parameter of the target wireless bearer corresponding to the target data flow. The embodiment of the present application solves the problem in the prior art that, when the same data packet is transmitted between different access network nodes, the corresponding bearer count values may be different in the PTM transmission mechanism.

Description

Technical Field

[0001] The present application relates to the field of mobile communication technology, and in particular to a state parameter processing method and device, and network equipment. Background Art

[0002] In wireless communication systems, multiple user equipment (UE) devices may request the same downlink data. To address this situation, the industry has developed a point-to-multipoint (PTM) mechanism. PTM allows the network to use specific radio resources to send a single copy of downlink data, which can then be received simultaneously by multiple UEs. Compared to traditional point-to-point (PTP) or unicast (PTP) mechanisms, this reduces radio resource consumption.

[0003] For the traditional PTP mode, a cell can dynamically adjust air interface transmission parameters based on the channel quality between the base station and the unicast receiving terminal, such as adjusting the modulation and coding scheme (MCS) and beam direction to improve spectrum utilization efficiency. However, for the PTM mode, the base station's signal transmission needs to cover all UEs within the cell as much as possible, even including UEs whose location and channel quality are unknown to the network, such as UEs that are not in radio resource control (RRC). In view of this, the network side often has to adopt relatively conservative air interface transmission parameters, such as MCS with a lower code rate and omnidirectional transmission, in order to use more air interface resources to transmit less information.

[0004] Multicast is applicable in a variety of scenarios, including services with strict latency requirements and relaxed reliability requirements, such as live video platforms, and services with relaxed latency requirements and strict reliability requirements. In most scenarios, the sender hopes to ensure that every UE receiving the service receives all data in sequence without duplication.

[0005] To ensure lossless and in-order delivery of downlink data packets during air interface transmission, wireless communication systems use a bearer mechanism that sets a bearer count for each data packet transmitted over the air interface. This bearer count starts at 0 and increments incrementally. The UE can use the count value for each data packet within a bearer to perform data continuity operations, including sorting data packets and detecting duplication or omissions.

[0006] However, in the 5th Generation New Radio (5G NR) system, the 5G access network node independently determines how to establish a bearer. Specifically, when sending data to the 5G access network, the 5G core network identifies which data flow and service session the packet belongs to. The 5G access network node can then independently decide to include one or more data flows from the same service session in the same bearer for air interface transmission.

[0007] In the PTM scenario, multiple 5G access network nodes may start PTM transmission at different times. The content of the first data packet received by each node from the 5G core network and sent to the UE through the air interface with a bearer count value of 0 may be different. As a result, the bearer count values for data packets with the same content are different between different 5G access network nodes. As a result, when the UE moves between these nodes, it is impossible to perform data continuity operations based on the bearer count values on the data packets, and the service quality requirements of the service cannot be met.

[0008] Therefore, when the same data packet is transmitted between different access network nodes using the existing PTM transmission mechanism, the corresponding bearer count values may be different, resulting in a problem in which service continuity cannot be guaranteed. Summary of the Invention

[0009] The embodiments of the present application provide a state parameter processing method and apparatus, and a network device to solve the problem in the prior art that, when the same data packet is transmitted between different access network nodes, the corresponding bearer count values may be different.

[0010] In a first aspect, an embodiment of the present application provides a state parameter processing method, which is applied to an access network element, including:

[0011] receiving target information sent by a core network element, and obtaining a first state parameter included in the target information; the first state parameter includes a data flow identifier and a first sequence number; the first sequence number is a sequence number corresponding to a transmission order of the first data packet transmitted by the core network element via the target transmission interface;

[0012] generating, based on the first sequence number, a second state parameter of a target data flow corresponding to the data flow identifier; the second state parameter indicating a count value of data packets of the target data flow transmitted by the core network element;

[0013] A third state parameter of a target radio bearer corresponding to the target data flow is updated; the third state parameter indicates a count value of data packets carried by the target radio bearer.

[0014] Optionally, the method comprises:

[0015] When the second data packet is sent through the air interface bearer, it carries a second sequence number; the second sequence number is determined by the third state parameter corresponding to the air interface bearer.

[0016] Optionally, generating, according to the first sequence number, a second state parameter of the target data flow corresponding to the data flow identifier includes:

[0017] Using the first sequence number as a second state parameter of the target data stream corresponding to the data stream identifier; or

[0018] The first sequence number is incremented by one, or the first sequence number is incremented by one and then modulo-processed with a preset sequence number threshold to obtain a second state parameter of the target data flow corresponding to the data flow identifier.

[0019] Optionally, obtaining the first state parameter carried in the target information includes:

[0020] Obtaining a data flow identifier and an initial first sequence number carried in the target information, using the data flow identifier as the data flow identifier of the first state parameter, and using the initial first sequence number as the first sequence number of the first state parameter, or

[0021] Obtain the data flow identifier and the fourth sequence number carried in the target information, use the data flow identifier as the data flow identifier of the first state parameter, and generate the first sequence number of the first state parameter based on the fourth sequence number and the third state parameter.

[0022] Optionally, the target information includes the first data packet or synchronization information.

[0023] Optionally, updating a third state parameter of a target radio bearer corresponding to the target data flow includes:

[0024] Determining a target radio bearer corresponding to the target data flow;

[0025] The second state parameters corresponding to the data flows carried by the target radio bearer are summed to obtain a third state parameter of the target radio bearer.

[0026] In a second aspect, an embodiment of the present application further provides a state parameter processing method, which is applied to a core network element, including:

[0027] Sending target information to an access network element, where the target information carries a first state parameter of the first data packet, so that the access network element generates a second state parameter of a target data flow corresponding to the data flow identifier based on the first sequence number, and updates a third state parameter of a target radio bearer corresponding to the target data flow;

[0028] The first state parameter includes the data flow identifier corresponding to the first data packet and the first sequence number; the first sequence number is a sequence number corresponding to the transmission order of the first data packet transmitted by the core network element via the target transmission interface;

[0029] The second state parameter indicates a count value of data packets of the target data flow transmitted by the core network element; the third state parameter indicates the number of data packets carried by the target radio bearer.

[0030] Optionally, the target information includes the first data packet or synchronization information.

[0031] In a third aspect, an embodiment of the present application further provides a network device, including a memory, a transceiver, and a processor:

[0032] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0033] receiving target information sent by a core network element, and obtaining a first state parameter included in the target information; the first state parameter includes a data flow identifier and a first sequence number; the first sequence number is a sequence number corresponding to a transmission order of the first data packet transmitted by the core network element via the target transmission interface;

[0034] generating, based on the first sequence number, a second state parameter of a target data flow corresponding to the data flow identifier; the second state parameter indicating a count value of data packets of the target data flow transmitted by the core network element;

[0035] A third state parameter of a target radio bearer corresponding to the target data flow is updated; the third state parameter indicates a count value of data packets carried by the target radio bearer.

[0036] Optionally, the processor is configured to:

[0037] When the second data packet is sent through the air interface bearer, it carries a second sequence number; the second sequence number is determined by the third state parameter corresponding to the air interface bearer.

[0038] Optionally, generating, according to the first sequence number, a second state parameter of the target data flow corresponding to the data flow identifier includes:

[0039] Using the first sequence number as a second state parameter of the target data stream corresponding to the data stream identifier; or

[0040] The first sequence number is incremented by one, or the first sequence number is incremented by one and then modulo-processed with a preset sequence number threshold to obtain a second state parameter of the target data flow corresponding to the data flow identifier.

[0041] Optionally, obtaining the first state parameter carried in the target information includes:

[0042] Obtaining a data flow identifier and an initial first sequence number carried in the target information, using the data flow identifier as the data flow identifier of the first state parameter, and using the initial first sequence number as the first sequence number of the first state parameter, or

[0043] Obtain the data flow identifier and the fourth sequence number carried in the target information, use the data flow identifier as the data flow identifier of the first state parameter, and generate the first sequence number of the first state parameter based on the fourth sequence number and the third state parameter.

[0044] Optionally, the target information includes the first data packet or synchronization information.

[0045] Optionally, updating a third state parameter of a target radio bearer corresponding to the target data flow includes:

[0046] Determining a target radio bearer corresponding to the target data flow;

[0047] The second state parameters corresponding to the data flows carried by the target radio bearer are summed to obtain a third state parameter of the target radio bearer.

[0048] In a third aspect, an embodiment of the present application further provides an electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the steps in the state parameter processing method described in the first aspect above are implemented.

[0049] In a fourth aspect, an embodiment of the present application further provides a network device, including a memory, a transceiver, and a processor:

[0050] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations:

[0051] Sending target information to an access network element, where the target information carries a first state parameter of the first data packet, so that the access network element generates a second state parameter of a target data flow corresponding to the data flow identifier based on the first sequence number, and updates a third state parameter of a target radio bearer corresponding to the target data flow;

[0052] The first state parameter includes the data flow identifier corresponding to the first data packet and the first sequence number; the first sequence number is a sequence number corresponding to the transmission order of the first data packet transmitted by the core network element via the target transmission interface;

[0053] The second state parameter indicates a count value of data packets of the target data flow transmitted by the core network element; the third state parameter indicates the number of data packets carried by the target radio bearer.

[0054] Optionally, the target information includes the first data packet or synchronization information.

[0055] In a fourth aspect, an embodiment of the present application further provides a state parameter processing device, applied to an access network element, comprising:

[0056] an information receiving module, configured to receive target information sent by a core network element, and obtain a first state parameter included in the target information; the first state parameter includes a data flow identifier and a first sequence number; the first sequence number is a sequence number corresponding to a transmission order of the first data packet transmitted by the core network element via the target transmission interface;

[0057] a parameter generating module, configured to generate, based on the first sequence number, a second state parameter of a target data flow corresponding to the data flow identifier; the second state parameter indicating a count value of data packets of the target data flow transmitted by the core network element;

[0058] A parameter updating module is used to update a third state parameter of a target radio bearer corresponding to the target data flow; the third state parameter indicates a count value of data packets carried by the target radio bearer.

[0059] In a sixth aspect, an embodiment of the present application further provides a state parameter processing device, which is applied to a core network element and includes:

[0060] an information sending module, configured to send target information to an access network element, wherein the target information carries a first state parameter of a first data packet, so that the access network element generates a second state parameter of a target data flow corresponding to the data flow identifier based on the first sequence number, and updates a third state parameter of a target radio bearer corresponding to the target data flow;

[0061] The first state parameter includes a data flow identifier and a first sequence number corresponding to the first data packet; the first sequence number is a sequence number corresponding to the transmission order of the first data packet transmitted by the core network element via the target transmission interface;

[0062] The second state parameter indicates a count value of data packets of the target data flow transmitted by the core network element; the third state parameter indicates the number of data packets carried by the target radio bearer.

[0063] In the seventh aspect, an embodiment of the present application also provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps in the above method when executing the computer program.

[0064] In an eighth aspect, an embodiment of the present application further provides a processor-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps in the above method are implemented.

[0065] In an embodiment of the present application, target information sent by a core network network element is received, and a first state parameter included in the target information is obtained; based on the first serial number, a second state parameter of a target data flow corresponding to a data flow identifier is generated, and a third state parameter of a target wireless bearer corresponding to the target data flow is updated, so that when the same data packet is transmitted between different access network network elements, the corresponding bearer count values are the same, thereby ensuring service continuity of the UE when switching between different access network network elements. BRIEF DESCRIPTION OF THE DRAWINGS

[0066] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments of the present application. Obviously, the drawings described below are only 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.

[0067] Figure 1 One of the flow charts of the state parameter processing method provided in the embodiment of the present application;

[0068] Figure 2 The second flowchart of the state parameter processing method provided in the embodiment of the present application;

[0069] Figure 3 This is one of the structural block diagrams of the state parameter processing device provided in an embodiment of the present application;

[0070] Figure 4 The second structural block diagram of the state parameter processing device provided in the embodiment of the present application;

[0071] Figure 5 One of the network device structure block diagrams provided in the embodiment of the present application;

[0072] Figure 6This is the second structural block diagram of the network device provided in the embodiment of the present application. DETAILED DESCRIPTION

[0073] In the embodiments of this application, the term "and / or" describes the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship.

[0074] In the embodiments of the present application, the term "plurality" refers to two or more than two, and other quantifiers are similar.

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

[0076] The embodiments of the present application provide a state parameter processing method and apparatus, and a network device to solve the problem in the prior art that, when the same data packet is transmitted between different access network nodes, the corresponding bearer count values may be different.

[0077] Among them, the method and the device are based on the same application concept. Since the principles of solving problems by the method and the device are similar, the implementation of the device and the method can refer to each other, and the repeated parts will not be repeated.

[0078] In addition, the technical solutions provided in the embodiments of the present application can be applicable to a variety of systems, especially 5G systems. For example, applicable systems may be global system of mobile communication (GSM) systems, code division multiple access (CDMA) systems, wideband code division multiple access (WCDMA) general packet radio service (GPRS) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, long term evolution advanced (LTE-A) systems, universal mobile telecommunication systems (UMTS), worldwide interoperability for microwave access (WiMAX) systems, 5G new air interface (NR) systems, etc. These various systems include terminal devices and network equipment. The system may also include a core network part, such as an evolved packet system (EPS), a 5G system (5GS), etc.

[0079] The terminal device involved in the embodiments of the present application may be a device that provides voice and / or data connectivity to a user, a handheld device with wireless connection function, or other processing devices connected to a wireless modem. In different systems, the name of the terminal device may also be different. For example, in a 5G system, the terminal device may be called a user equipment (UE). A wireless terminal device can communicate with one or more core networks (CN) via a radio access network (RAN). The wireless terminal device can be a mobile terminal device, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal device. For example, it can be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device that exchanges language and / or data with a radio access network. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), and other devices. The wireless terminal device may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal device, an access terminal device, a user terminal device, a user agent, or a user device, but is not limited in the embodiments of the present application.

[0080] The network device involved in the embodiments of the present application may be a base station, which may include multiple cells providing services to terminals. Depending on the specific application scenario, the base station may also be called an access point, or may be a device in an access network that communicates with a wireless terminal device through one or more sectors on an air interface, or may be named otherwise. The network device may be used to interchange received air frames with Internet Protocol (IP) packets, acting as a router between the wireless terminal device and the rest of the access network, wherein the rest of the access network may include an Internet Protocol (IP) communication network. The network device may also coordinate attribute management of the air interface. For example, the network device involved in the embodiments of the present application may be a network device (Base Transceiver Station, BTS) in the Global System for Mobile communications (GSM) or Code Division Multiple Access (CDMA), or a network device (NodeB) in Wide-band Code Division Multiple Access (WCDMA), or an evolutionary network device (eNB or e-NodeB) in the Long Term Evolution (LTE) system, a 5G base station (gNB) in the 5G network architecture (next generation system), or a home evolved Node B (HeNB), a relay node, a home base station (femto), a pico base station (pico), etc., and is not limited in the embodiments of the present application. In some network structures, the network device may include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit may also be geographically separated.

[0081] Network devices and terminal devices can each use one or more antennas for Multiple Input Multiple Output (MIMO) transmission. MIMO transmission can be either Single User MIMO (SU-MIMO) or Multi User MIMO (MU-MIMO). Depending on the configuration and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO, or Massive-MIMO. It can also use diversity transmission, precoding, or beamforming.

[0082] In wireless communication systems, handover refers to the operation of changing the transmission path within the communication network for a service. During a handover process involving a change in the Packet Data Convergence Protocol (PDCP) network element (i.e., a service originally transmitted through one PDCP network element is at a certain point switched to another), to improve the continuity of downlink services sent via PTP, and even to ensure lossless, in-order delivery, the source PDCP network element provides the target PDCP network element with data received from the core network but not yet delivered to the UE. This mechanism is called "data forwarding."

[0083] Normally, the mapping of service flows to radio bearers on the source PDCP network element side and the target PDCP network element side is the same, and data forwarding can be performed at the granularity of the radio bearer, with each data packet containing a sequence number. At the same time, the source PDCP network element side will also provide the target PDCP network element side with a summary of the transmission status of the source PDCP network element, where the PDCP count value indicates which PDCP data packets have been successfully received by the UE through the air interface. During the switching process, the UPF will send an end marker (End Marker) to the source transmission path for each session, and all subsequent data will be sent through the new transmission path. When the source PDCP network element side receives the end marker sent by the UPF, it knows that the session is no longer transmitted through the N3 channel on the source side, and the previously received data packet is the last data packet transmitted through this channel. Thereafter, for each radio bearer, when all the data that needs to be forwarded on the radio bearer has been sent to the target PDCP network element side, the source PDCP network element side will send an end marker. When the target PDCP receives this end marker for the radio bearer, it knows that the data forwarding for the radio bearer has ended. After that, new data packets received from the UPF via the Service Data Adaptation Protocol (SDAP) layer will be numbered based on the count value of the last data packet forwarded. This mechanism ensures that the PDCP count value and data packet content are continuous when the UE receives data.

[0084] However, if the target UE is in the switching process, and the target PDCP network element side of the service data is sending it in PTM mode, then in order not to interfere with the service continuity of other UEs that are receiving the service data, the PDCP count value will not be adjusted for the target UE. Therefore, in order to ensure the service continuity of the target UE, it is required that the PDCP count values of the source side and the target side should be the same when transmitting service data packets with the same content. Therefore, in order to ensure that different PDCP network elements have the same PDCP count values when transmitting service data packets with the same content, an embodiment of the present application provides a state parameter processing method, such as Figure 1 As shown, the method is applied to an access network element, and the method includes:

[0085] Step 101: Receive target information sent by a core network element, and obtain a first state parameter included in the target information; the first state parameter includes a data flow identifier and a first sequence number; the first sequence number is a sequence number corresponding to the transmission order of the first data packet transmitted by the core network element via the target transmission interface.

[0086] Among them, the access network network element is such as a PDCP network element or a Radio Link Control (RLC) network element; the core network network element is such as a User Plane Function (UPF) network element, an Access and Mobility Management Function (AMF) network element, or a Session Management Function (SMF) network element. For ease of explanation, in the embodiment of the present application, the access network network element is taken as a PDCP network element and the core network network element is taken as a UPF network element. Other situations (the access network network element is other network elements, or the core network network element is other network elements) are similar to the embodiment of the present application and will not be repeated here.

[0087] Specifically, the AMF network element is a relatively core module in the network, and each UE is only connected to one AMF at the same time. The AMF network element communicates with the SMF network element through the Nsmf interface, for example, requesting the SMF to establish, modify, and release the service context. Service data is managed by the SMF network element in the form of a session based on service attributes, IP routing of the backbone network and other parameters, and each session is managed by only one SMF. In each session, according to the quality of service (QoS) requirements of different service data, it can be divided into one or more service data flows, and a data flow identifier can be set for each service data flow. The SMF network element manages the UPF network element through the N4 interface, for example, requesting the UPF to establish, modify, and release the transmission channel for service data.

[0088] When receiving the target information sent by the core network element, the access network element obtains the first state parameter included in the target information; the first state parameter includes a data flow identifier and a first sequence number.

[0089] Specifically, the data flow identifier is the identifier of the data flow to which the currently transmitted service data packet belongs. For example, when the UPF network element sends service data that can be transmitted over the air interface using PTM via the N3 interface, it sets a state variable Tx_NEXT_i_UPF for each data flow, where i identifies the data flow identifier. Typically, the initial value of this state variable is 0, but it can also be other values.

[0090] The first sequence number is a sequence number corresponding to the transmission order of the first data packet transmitted by the core network element via the target transmission interface; the target transmission interface is, for example, the N3 interface. Typically, the UPF network element exchanges service data with an external data network (e.g., a backbone network) in the northbound direction via the N6 interface, and exchanges service data with access network elements in the southbound direction via the N3 interface. If the access network is a 5G wireless access network, the N3 interface is also called the NG-U interface, which is the user plane portion of the NG interface.

[0091] When the UPF sends the first packet of data stream i over the N3 interface, it adds a first sequence number (Sequence Number) to the packet header, denoted by Tx_NEXT_N3_i_UPF. By adding the interface sequence number, the N3 channel ensures lossless, in-order transmission of all packets in the session.

[0092] Thus, when a first data packet that can be transmitted over the air interface using PTM is received via the N3 interface, the first sequence number is sent to the SDAP layer of the access network device (e.g., gNB). The SDAP layer maps the first data packet to the corresponding radio bearer based on the data flow identifier in the data packet and the preset mapping relationship, and sends the first data packet along with the first sequence number to the PDCP layer of the gNB.

[0093] Step 102: Generate a second state parameter of the target data flow corresponding to the data flow identifier based on the first serial number; the second state parameter indicates a count value of data packets of the target data flow transmitted by the core network element.

[0094] The access network element further processes the first serial number to obtain a second state parameter; the second state parameter indicates the count value of the data packets of the target data flow transmitted by the core network element, such as the count value of the data packets of the target data flow i.

[0095] Optionally, the second state parameter is represented by Rx_NEXT_N3_i_PDCP_j, where j represents the identifier of PDCP; the first sequence number can be added by 1 to obtain the second state parameter, and the second state parameter represents the sequence number of the next N3 data packet of the first data packet currently transmitted; the first sequence number can also be added by 1 and the modulus of the preset sequence number upper limit plus 1 is used as the first sequence number; optionally, the preset sequence number upper limit plus 1 is represented by rangeN3SN, and its value can be 2 24 .

[0096] Step 103: Update a third state parameter of a target radio bearer corresponding to the target data flow; the third state parameter indicates a count value of data packets carried by the target radio bearer.

[0097] The access network element generates a PDCP data packet belonging to the target (for example, wireless bearer k) based on the second state parameter, sets the count value of the PDCP data packet to the third state parameter (Tx_NEXT_Uu_k_PDCP_j), and performs subsequent processing, such as intercepting the lowest several bits (preset data bit number) of the count value as the third state parameter and submitting it to the lower protocol layer.

[0098] Specifically, after generating the second state parameter, the access network element updates the third state parameter; the third state parameter represents the count value of all data flows mapped to the radio bearer k, that is, the sum of the number of data packets mapped to the target radio bearer, that is, the PDCP count value of the target radio bearer; optionally, the PDCP count value is usually set to a maximum threshold, for example, the maximum threshold is 2 32 ; If the third state parameter is greater than or equal to the maximum threshold, the lowest several bits (preset number of data bits) of the PDCP count value are truncated as the third state parameter.

[0099] In this way, on the one hand, when two different access network elements map data streams according to the same mapping relationship from data stream to wireless bearer, and transmit service data packets through the air interface in PTM mode, the sequential transmission based on the core network element through the N3 interface ensures that the two access network elements can receive service data in exactly the same order.

[0100] On the other hand, when calculating the third state parameter (PDCP count value, i.e. bearer count value) for the PDCP data packet, the value of the third state parameter is always: the second state parameter of the previous data packet of all data streams contained in the wireless bearer. Because different access network elements receive data packets via the N3 interface in the same order, their respective "previous data packet for each data flow" is also the same when processing any data packet. Therefore, as long as the mapping between data flows and data bearers is the same across different access network elements, the third state parameter calculated for the same service data is also the same. When the access network element sends data packets to the UE via the air interface bearer, it determines the sequence number of the transmitted data packet based on the third state parameter. In other words, the sequence number of the data packet received by the UE is determined based on the third state parameter. Therefore, if the UE switches between different access network elements, for example, from gNB1 to gNB2, the third state parameter calculated by gNB1 and gNB2 for the same service data is the same, and the sequence numbers sent to the UE by both are also the same. In other words, the sequence numbers of data packets received by the UE at different access network elements are consistent, thereby ensuring service continuity when the UE moves between gNBs.

[0101] In an embodiment of the present application, target information sent by a core network element is received, and a first state parameter included in the target information is obtained; based on the first sequence number, a second state parameter of a target data flow corresponding to a data flow identifier is generated, and a third state parameter of a target wireless bearer corresponding to the target data flow is updated, so that when the same data packet is transmitted between different access network elements, the corresponding bearer count values are the same, thereby ensuring service continuity of the UE when switching between different access network elements. The embodiment of the present application solves the problem in the prior art that, when the same data packet is transmitted between different access network nodes, the corresponding bearer count values may be different in the PTM transmission mechanism.

[0102] In an optional embodiment, the method includes:

[0103] When the second data packet is sent through the air interface bearer, it carries a second serial number; the second serial number is determined by the third state parameter corresponding to the air interface bearer, for example, the lowest several bits (preset data bit number) of the third state parameter are intercepted as the second serial number.

[0104] Since the corresponding bearer count values are the same when different access network elements transmit the same data packet, if the UE switches between different access network elements, for example, from gNB1 to gNB2, since the third state parameters calculated by gNB1 and gNB2 for the same service data are also the same, the sequence numbers sent to the UE by both are also the same. In other words, the sequence numbers of the data packets received by the UE under different access network elements are consistent, thereby ensuring service continuity when the UE moves between gNBs.

[0105] In an optional embodiment, generating, based on the first sequence number, a second state parameter of the target data flow corresponding to the data flow identifier includes:

[0106] Using the first sequence number as a second state parameter of the target data stream corresponding to the data stream identifier; or

[0107] The first sequence number is incremented by one, or the first sequence number is incremented by one and then modulo-processed with a preset sequence number threshold to obtain a second state parameter of the target data flow corresponding to the data flow identifier.

[0108] The first sequence number can be added by 1 to obtain the second state parameter, and the second state parameter represents the sequence number of the next N3 data packets of the currently transmitted first data packet; the first sequence number can also be added by 1 and the modulus of the preset sequence number threshold (preset sequence number upper limit) plus 1 is used as the first sequence number; optionally, the value of the preset sequence number threshold plus 1 can be 2 24 .

[0109] In an optional embodiment, obtaining the first state parameter carried in the target information includes:

[0110] Obtaining a data flow identifier and an initial first sequence number carried in the target information, using the data flow identifier as the data flow identifier of the first state parameter, and using the initial first sequence number as the first sequence number of the first state parameter; or

[0111] Obtain the data flow identifier and the fourth sequence number carried in the target information, use the data flow identifier as the data flow identifier of the first state parameter, and generate the first sequence number of the first state parameter based on the fourth sequence number and the third state parameter.

[0112] Since in wireless communication systems, count values, sequence numbers, and state variables are often stored in a format of non-negative integers with a fixed bit length, there is theoretically a case of numerical loops (for example, in an 8-bit non-negative integer value, 255+1=0). Therefore, the first sequence number of the first state parameter is generated based on the fourth sequence number and the third state parameter. For example, if the number of data bits of the fourth sequence number is less than the number of data bits of the third state variable, it means that some data bits of the original fourth sequence number have been truncated; for example, if the third state parameter is 5 data bits and the fourth sequence number is 3 data bits, it means that the fourth sequence number is the result of truncating the lowest 3 bits of the original fourth sequence number; that is, after the hyperframe number (HFN), the original fourth sequence number has had its highest data bits truncated; therefore, in an embodiment of the present application, if the fourth sequence number lacks N data bits compared to the third state parameter, the first N data bits of the third state variable are added to the fourth sequence number to restore the first sequence number.

[0113] For example, in order to reduce resource consumption, when the UPF network element sends downlink data, it still includes the N3 sequence number (the fourth sequence number). When the gNB network element receives the data, it first determines the N3 count value from the third state parameter corresponding to the N3 sequence number, and then determines the first sequence number.

[0114] In an optional embodiment, the target information includes the first data packet or synchronization information.

[0115] If PDCP is processing the earliest received data packet, such as the first data packet of data stream i, it is unable to calculate the second state parameter due to the lack of the previous data packet of the data stream; therefore, when the access network element starts to receive service data through the N3 interface, and the service data can be transmitted through the air interface using PTM, the UPF sends a synchronization message through the N3 interface, which includes the identifier of each data stream in the corresponding session and the first sequence number for the data stream.

[0116] In this way, after receiving the synchronization information, the access network element initializes the value of the second state parameter to the second state parameter calculated according to the first sequence number in the synchronization information according to the identifier of the data flow in the synchronization information.

[0117] In an optional embodiment, updating the third state parameter of the target radio bearer corresponding to the target data flow includes:

[0118] Determining a target radio bearer corresponding to the target data flow;

[0119] The second state parameter corresponding to the data flow carried by the target wireless bearer is summed to obtain the third state parameter of the target wireless bearer. The third state parameter represents the count value of all data flows mapped to the target wireless bearer, that is, the sum of the number of data packets mapped to the target wireless bearer, that is, the PDCP count value of the target wireless bearer.

[0120] As an example, see Table 1 below, which shows some state parameters for a service session transmitted over the air interface using PTM. This session contains three data flows, labeled R, G, and B. Both gNB1 and gNB2 map data flows R and G to radio bearer 1 and data flow B to radio bearer 2.

[0121] gNB1 starts receiving data as soon as UPF starts sending data through the N3 interface, while gNB2 starts receiving data after UPF has transmitted 10 data packets.

[0122] Wherein, Tx_NEXT_N3_R_UPF represents the first sequence number of data stream R;

[0123] Tx_NEXT_N3_G_UPF indicates the first sequence number of data stream G;

[0124] Tx_NEXT_N3_B_UPF indicates the first sequence number of data stream B;

[0125] Rx_NEXT_N3_R_PDCP_1 represents the second state parameter of data flow R in PDCP1;

[0126] Rx_NEXT_N3_G_PDCP_1 represents the second state parameter of data flow G in PDCP1;

[0127] Rx_NEXT_N3_B_PDCP_1 indicates the second state parameter of data flow B in PDCP1;

[0128] Tx_NEXT_Uu_1_PDCP_1 represents the third state parameter of radio bearer 1;

[0129] Tx_NEXT_Uu_2_PDCP_1 represents the third state parameter of radio bearer 2.

[0130] Table 1:

[0131]

[0132]

[0133] As shown in Table 1, at time T0, the N3 interface transmits synchronization information indicating that the current first sequence number of each data flow is 0. At this point, access network element gNB1 directly sets the second state parameter for each data flow to the corresponding first sequence number value, i.e., 0. Simultaneously, gNB1 sets the third state parameter of radio bearer 1 to the sum of the second state parameters corresponding to data flow R and data flow G, i.e., 0, and sets the third state parameter of radio bearer 1 to the second state parameter corresponding to data flow B, i.e., 0.

[0134] At time T1, N3 transmits data packet 0 of data stream B. At this time, access network element gNB1 determines that the first sequence number of data stream B is 0, adds 1 to the first sequence number, and obtains the second state parameter 1. At the same time, it updates the third state parameter of radio bearer 2 to the value of the second state parameter of data stream B, that is, 1.

[0135] At time T2, N3 transmits data packet 0 of data stream G. Access network element gNB1 determines that the first sequence number of data stream G is 0, adds 1 to the first sequence number, and obtains the second state parameter 1. Simultaneously, the third state parameter of radio bearer 1 is updated to the sum of the second state parameters of data streams R and G, that is, 1.

[0136] At time T3, N3 transmits data packet 1 of data stream B. Access network element gNB1 determines that the first sequence number of data stream G is 1, increments the first sequence number by 1, and obtains the second state parameter 2. Simultaneously, it updates the third state parameter of radio bearer 2 to the value of the second state parameter of data stream B, which is 2.

[0137] …

[0138] When gNB2 starts receiving data packets at different times, the third state parameter calculated in the same manner as above is the same. Therefore, the sequence numbers of the data packets sent to the UE by gNB1 and gNB2 are also the same. The sequence numbers of the data packets received by the UE under different gNB network elements are consistent, thereby ensuring service continuity when the UE moves between gNBs.

[0139] In an embodiment of the present application, target information sent by a core network network element is received, and a first state parameter included in the target information is obtained; based on the first serial number, a second state parameter of a target data flow corresponding to a data flow identifier is generated, and a third state parameter of a target wireless bearer corresponding to the target data flow is updated, so that when the same data packet is transmitted between different access network elements, the corresponding bearer count values are the same, thereby ensuring service continuity of the UE when switching between different access network elements.

[0140] See also Figure 2 , an embodiment of the present application provides a state parameter processing method, the method being applied to a core network element, the method comprising:

[0141] Step 201: Send target information to the access network element, carrying the first state parameter of the first data packet in the target information, so that the access network element generates the second state parameter of the target data flow corresponding to the data flow identifier according to the first serial number, and updates the third state parameter of the target wireless bearer corresponding to the target data flow.

[0142] Among them, the access network element is, for example, a PDCP network element or an RLC network element; the core network element is a UPF network element, an AMF network element, or an SMF network element. For ease of explanation, in the embodiment of the present application, the access network element is an PDCP network element and the core network element is an UPF network element. Other situations (the access network element is other network elements, or the core network element is other network elements) are similar to the embodiment of the present application and will not be repeated here.

[0143] Specifically, the AMF network element is a relatively core module in the network, and each UE is only connected to one AMF at the same time. The AMF network element communicates with the SMF network element through the Nsmf interface, for example, requesting the SMF to establish, modify, and release the service context. Service data is managed by the SMF network element in the form of a session based on service attributes, IP routing of the backbone network and other parameters, and each session is managed by only one SMF. In each session, according to the quality of service (QoS) requirements of different service data, it can be divided into one or more service data flows, and a data flow identifier can be set for each service data flow. The SMF network element manages the UPF network element through the N4 interface, for example, requesting the UPF to establish, modify, and release the transmission channel for service data.

[0144] When receiving the target information sent by the core network element, the access network element obtains the first state parameter included in the target information; the first state parameter includes a data flow identifier and a first sequence number.

[0145] Specifically, the data flow identifier is the identifier of the data flow to which the currently transmitted service data packet belongs. For example, when the UPF network element sends service data that can be transmitted over the air interface using PTM via the N3 interface, it sets a state variable Tx_NEXT_i_UPF for each data flow, where i identifies the data flow identifier. Typically, the initial value of this state variable is 0, but it can also be other values.

[0146] The first state parameter includes the data flow identifier corresponding to the first data packet and the first sequence number; the first sequence number is the sequence number corresponding to the transmission order of the first data packet transmitted by the core network element via the target transmission interface; the target transmission interface is, for example, the N3 interface. Under normal circumstances, the UPF network element exchanges service data with the external data network (such as the backbone network) in the northbound direction through the N6 interface, and exchanges service data with the access network element in the southbound direction through the N3 interface. If the access network is a 5G wireless access network, the N3 interface is also called the NG-U interface, which is the user plane part of the NG interface.

[0147] The second state parameter indicates a count value of data packets of the target data flow transmitted by the core network element; the third state parameter indicates a number of data packets carried by the target radio bearer. The access network element further processes the first sequence number to obtain the second state parameter; the second state parameter indicates a count value of data packets of the target data flow transmitted by the core network element, such as a count value of data packets of target data flow i.

[0148] The access network element generates a PDCP data packet belonging to the target (for example, wireless bearer k) based on the second state parameter, sets the count value of the PDCP data packet to the third state parameter (Tx_NEXT_Uu_k_PDCP_j), and performs subsequent processing, such as intercepting the lowest several bits (preset data bit number) of the count value as the third state parameter and submitting it to the lower protocol layer.

[0149] Specifically, after generating the second state parameter, the access network element updates the third state parameter; the third state parameter represents the count value of all data flows mapped to the radio bearer k, that is, the sum of the number of data packets mapped to the target radio bearer, that is, the PDCP count value of the target radio bearer; optionally, the PDCP count value is usually set to a maximum threshold, for example, the maximum threshold is 2 32 ; If the third state parameter is greater than the third state parameter, the lowest several bits (preset number of data bits) of the PDCP count value are truncated as the third state parameter.

[0150] In this way, on the one hand, when two different access network elements map data streams according to the same mapping relationship from data stream to wireless bearer, and transmit service data packets through the air interface in PTM mode, the sequential transmission based on the core network element through the N3 interface ensures that the two access network elements can receive service data in exactly the same order.

[0151] On the other hand, when calculating the third state parameter (PDCP count value, i.e. bearer count value) for the PDCP data packet, the value of the third state parameter is always: the second state parameter of the previous data packet of all data streams contained in the wireless bearer. Because different access network elements receive data packets via the N3 interface in the same order, their respective "previous data packet for each data flow" is also the same when processing any data packet. Therefore, as long as the mapping between data flows and data bearers is the same across different access network elements, the third state parameter calculated for the same service data is also the same. When the access network element sends data packets to the UE via the air interface bearer, it determines the sequence number of the transmitted data packet based on the third state parameter. In other words, the sequence number of the data packet received by the UE is determined based on the third state parameter. Therefore, if the UE switches between different access network elements, for example, from gNB1 to gNB2, the third state parameter calculated by gNB1 and gNB2 for the same service data is the same, and the sequence numbers sent to the UE by both are also the same. In other words, the sequence numbers of data packets received by the UE at different access network elements are consistent, thereby ensuring service continuity when the UE moves between gNBs.

[0152] In an optional embodiment, the target information includes the first data packet or synchronization information.

[0153] If PDCP is processing the earliest received data packet, such as the first data packet of data stream i, it is unable to calculate the second state parameter due to the lack of the previous data packet of the data stream; therefore, when the access network element starts to receive service data through the N3 interface, and the service data can be transmitted through the air interface using PTM, the UPF sends a synchronization message through the N3 interface, which includes the identifier of each data stream in the corresponding session and the first sequence number for the data stream.

[0154] In this way, after receiving the synchronization information, the access network element initializes the value of the second state parameter to the second state parameter calculated according to the first sequence number in the synchronization information according to the identifier of the data flow in the synchronization information.

[0155] In an embodiment of the present application, target information is sent to an access network element, and the target information carries a first state parameter of a first data packet, so that the access network element generates a second state parameter of a target data stream corresponding to a data stream identifier according to a first sequence number, and updates a third state parameter of a target wireless bearer corresponding to the target data stream, so that when the same data packet is transmitted between different access network elements, the corresponding bearer count values are the same, thereby ensuring service continuity of the UE when switching between different access network elements. The embodiment of the present application solves the problem in the prior art that, when the same data packet is transmitted between different access network nodes, the corresponding bearer count values may be different in the PTM transmission mechanism.

[0156] The above introduces the state parameter processing method provided by the embodiment of the present application. The following will introduce the state parameter processing device provided by the embodiment of the present application in conjunction with the accompanying drawings.

[0157] See also Figure 3 The embodiment of the present application further provides a state parameter processing device, which is applied to an access network element, including:

[0158] The information receiving module 301 is used to receive the target information sent by the core network network element and obtain the first state parameter included in the target information; the first state parameter includes a data flow identifier and a first sequence number; the first sequence number is the sequence number corresponding to the transmission order of the first data packet transmitted by the core network network element via the target transmission interface.

[0159] Among them, the access network element is, for example, a PDCP network element or an RLC network element; the core network element is a UPF network element, an AMF network element, or an SMF network element. For ease of explanation, in the embodiment of the present application, the access network element is an PDCP network element and the core network element is an UPF network element. Other situations (the access network element is other network elements, or the core network element is other network elements) are similar to the embodiment of the present application and will not be repeated here.

[0160] Specifically, the AMF network element is a relatively core module in the network, and each UE is only connected to one AMF at the same time. The AMF network element communicates with the SMF network element through the Nsmf interface, for example, requesting the SMF to establish, modify, and release the service context. Service data is managed by the SMF network element in the form of a session based on service attributes, IP routing of the backbone network and other parameters, and each session is managed by only one SMF. In each session, according to the QoS requirements of different service data, it can be divided into one or more service data flows, and a data flow identifier can be set for each service data flow. The SMF network element manages the UPF network element through the N4 interface, for example, requesting the UPF to establish, modify, and release the transmission channel for service data.

[0161] When receiving the target information sent by the core network element, the access network element obtains the first state parameter included in the target information; the first state parameter includes a data flow identifier and a first sequence number.

[0162] Specifically, the data flow identifier is the identifier of the data flow to which the currently transmitted service data packet belongs. For example, when the UPF network element sends service data that can be transmitted over the air interface using PTM via the N3 interface, it sets a state variable Tx_NEXT_i_UPF for each data flow, where i identifies the data flow identifier. Typically, the initial value of this state variable is 0, but it can also be other values.

[0163] The first sequence number is a sequence number corresponding to the transmission order of the first data packet transmitted by the core network element via the target transmission interface; the target transmission interface is, for example, the N3 interface. Typically, the UPF network element exchanges service data with an external data network (e.g., a backbone network) in the northbound direction via the N6 interface, and exchanges service data with access network elements in the southbound direction via the N3 interface. If the access network is a 5G wireless access network, the N3 interface is also called the NG-U interface, which is the user plane portion of the NG interface.

[0164] When the UPF sends the first packet of data stream i over the N3 interface, it first adds a first sequence number (Tx_NEXT_N3_i_UPF) to the packet header. This addition of the interface sequence number ensures lossless, in-order transmission of all packets in the session.

[0165] Thus, when a first data packet that can be transmitted over the air interface using PTM is received via the N3 interface, the first sequence number is sent to the SDAP layer of the access network device (e.g., gNB). The SDAP layer maps the first data packet to the corresponding radio bearer based on the data flow identifier in the data packet and the preset mapping relationship, and sends the first data packet along with the first sequence number to the PDCP layer of the gNB.

[0166] The parameter generation module 302 is used to generate a second state parameter of the target data flow corresponding to the data flow identifier based on the first serial number; the second state parameter indicates the count value of the data packets of the target data flow transmitted by the core network network element.

[0167] The access network element further processes the first serial number to obtain a second state parameter; the second state parameter indicates the count value of the data packets of the target data flow transmitted by the core network element, such as the count value of the data packets of the target data flow i.

[0168] Optionally, the second state parameter is represented by Rx_NEXT_N3_i_PDCP_j, where j represents the identifier of PDCP; the first sequence number can be added by 1 to obtain the second state parameter, and the second state parameter represents the sequence number of the next N3 data packet of the first data packet currently transmitted; the first sequence number can also be added by 1 and the modulus of the preset sequence number upper limit plus 1 is used as the first sequence number; optionally, the preset sequence number upper limit plus 1 is represented by rangeN3SN, and its value can be 2 24 .

[0169] The parameter updating module 303 is configured to update a third state parameter of a target radio bearer corresponding to the target data flow; the third state parameter indicates a count value of data packets carried by the target radio bearer.

[0170] The access network element generates a PDCP data packet belonging to the target (for example, wireless bearer k) based on the second state parameter, sets the count value of the PDCP data packet to the third state parameter (Tx_NEXT_Uu_k_PDCP_j), and performs subsequent processing, such as intercepting the lowest several bits (preset data bit number) of the count value as the third state parameter and submitting it to the lower protocol layer.

[0171] Specifically, after generating the second state parameter, the access network element updates the third state parameter; the third state parameter represents the count value of all data flows mapped to the radio bearer k, that is, the sum of the number of data packets mapped to the target radio bearer, that is, the PDCP count value of the target radio bearer; optionally, the PDCP count value is usually set to a maximum threshold, for example, the maximum threshold is 2 32 ; If the third state parameter is greater than the third state parameter, the lowest several bits (preset number of data bits) of the PDCP count value are truncated as the third state parameter.

[0172] In this way, on the one hand, when two different access network elements map data streams according to the same mapping relationship from data stream to wireless bearer, and transmit service data packets through the air interface in PTM mode, the sequential transmission based on the core network element through the N3 interface ensures that the two access network elements can receive service data in exactly the same order.

[0173] On the other hand, when calculating the third state parameter (PDCP count value, i.e. bearer count value) for the PDCP data packet, the value of the third state parameter is always: the second state parameter of the previous data packet of all data streams contained in the wireless bearer. Because different access network elements receive data packets via the N3 interface in the same order, their respective "previous data packet for each data flow" is also the same when processing any data packet. Therefore, as long as the mapping between data flows and data bearers is the same across different access network elements, the third state parameter calculated for the same service data is also the same. When the access network element sends data packets to the UE via the air interface bearer, it determines the sequence number of the transmitted data packet based on the third state parameter. In other words, the sequence number of the data packet received by the UE is determined based on the third state parameter. Therefore, if the UE switches between different access network elements, for example, from gNB1 to gNB2, the third state parameter calculated by gNB1 and gNB2 for the same service data is the same, and the sequence numbers sent to the UE by both are also the same. In other words, the sequence numbers of data packets received by the UE at different access network elements are consistent, thereby ensuring service continuity when the UE moves between gNBs.

[0174] Optionally, in an embodiment of the present application, the method includes:

[0175] When the second data packet is sent through the air interface bearer, it carries a second sequence number; the second sequence number is determined by the third state parameter corresponding to the air interface bearer.

[0176] Optionally, in the embodiment of the present application, the parameter generation module 302 includes:

[0177] a first processing submodule, configured to use the first sequence number as a second state parameter of the target data flow corresponding to the data flow identifier; or

[0178] The second processing submodule is configured to add one to the first serial number, or perform a modulo process on the first serial number after adding one to the first serial number and then performing a modulo process on the preset serial number threshold, to obtain a second state parameter of the target data flow corresponding to the data flow identifier.

[0179] Optionally, in the embodiment of the present application, the information receiving module 301 includes:

[0180] a first acquisition submodule, configured to acquire a data flow identifier and an initial first sequence number carried in the target information, use the data flow identifier as the data flow identifier of the first state parameter, and use the initial first sequence number as the first sequence number of the first state parameter, or

[0181] The second acquisition submodule is used to obtain the data flow identifier and the fourth serial number carried in the target information, use the data flow identifier as the data flow identifier of the first state parameter, and generate the first serial number of the first state parameter based on the fourth serial number and the third state parameter.

[0182] Optionally, in an embodiment of the present application, the target information includes the first data packet or synchronization information.

[0183] Optionally, in the embodiment of the present application, the parameter updating module 303 includes:

[0184] a determination submodule, configured to determine a target radio bearer corresponding to the target data flow;

[0185] The summing submodule is configured to sum the second state parameters corresponding to the data flows carried by the target radio bearer to obtain a third state parameter of the target radio bearer.

[0186] In an embodiment of the present application, the information receiving module 301 receives the target information sent by the core network network element and obtains the first state parameter included in the target information; the parameter generating module 302 generates the second state parameter of the target data flow corresponding to the data flow identifier according to the first serial number, and the parameter updating module 303 updates the third state parameter of the target wireless bearer corresponding to the target data flow, so as to realize that when the same data packet is transmitted between different access network network elements, the corresponding bearer count value is the same, so as to ensure the service continuity of the UE when switching between different access network network elements.

[0187] See also Figure 4 The embodiment of the present application further provides a state parameter processing device, which is applied to a core network element, including:

[0188] The information sending module 401 is used to send target information to the access network network element, carrying the first state parameter of the first data packet in the target information, so that the access network network element generates the second state parameter of the target data flow corresponding to the data flow identifier according to the first serial number, and updates the third state parameter of the target wireless bearer corresponding to the target data flow.

[0189] Among them, the access network element is, for example, a PDCP network element or an RLC network element; the core network element is a UPF network element, an AMF network element, or an SMF network element. For ease of explanation, in the embodiment of the present application, the access network element is an PDCP network element and the core network element is an UPF network element. Other situations (the access network element is other network elements, or the core network element is other network elements) are similar to the embodiment of the present application and will not be repeated here.

[0190] Specifically, the AMF network element is a relatively core module in the network, and each UE is only connected to one AMF at the same time. The AMF network element communicates with the SMF network element through the Nsmf interface, for example, requesting the SMF to establish, modify, and release the service context. Service data is managed by the SMF network element in the form of a session based on service attributes, IP routing of the backbone network and other parameters, and each session is managed by only one SMF. In each session, according to the quality of service (QoS) requirements of different service data, it can be divided into one or more service data flows, and a data flow identifier can be set for each service data flow. The SMF network element manages the UPF network element through the N4 interface, for example, requesting the UPF to establish, modify, and release the transmission channel for service data.

[0191] When receiving the target information sent by the core network element, the access network element obtains the first state parameter included in the target information; the first state parameter includes a data flow identifier and a first sequence number.

[0192] Specifically, the data flow identifier is the identifier of the data flow to which the currently transmitted service data packet belongs. For example, when the UPF network element sends service data that can be transmitted over the air interface using PTM via the N3 interface, it sets a state variable Tx_NEXT_i_UPF for each data flow, where i identifies the data flow identifier. Typically, the initial value of this state variable is 0, but it can also be other values.

[0193] The first state parameter includes a data flow identifier and a first sequence number corresponding to the first data packet; the first sequence number is a sequence number corresponding to the transmission order of the first data packet transmitted by the core network element via the target transmission interface; the target transmission interface is, for example, the N3 interface. Under normal circumstances, the UPF network element exchanges service data with the external data network (such as the backbone network) in the northbound direction through the N6 interface, and exchanges service data with the access network element in the southbound direction through the N3 interface. If the access network is a 5G wireless access network, the N3 interface is also called the NG-U interface, which is the user plane part of the NG interface.

[0194] The second state parameter indicates a count value of data packets of the target data flow transmitted by the core network element; the third state parameter indicates a number of data packets carried by the target radio bearer. The access network element further processes the first sequence number to obtain the second state parameter; the second state parameter indicates a count value of data packets of the target data flow transmitted by the core network element, such as a count value of data packets of target data flow i.

[0195] The access network element generates a PDCP data packet belonging to the target (for example, wireless bearer k) based on the second state parameter, sets the count value of the PDCP data packet to the third state parameter (Tx_NEXT_Uu_k_PDCP_j), and performs subsequent processing, such as intercepting the lowest several bits (preset data bit number) of the count value as the third state parameter and submitting it to the lower protocol layer.

[0196] Optionally, in an embodiment of the present application, the target information includes the first data packet or synchronization information.

[0197] In an embodiment of the present application, the information sending module 401 sends target information to an access network element, and the target information carries a first state parameter of a first data packet, so that the access network element generates a second state parameter of a target data stream corresponding to a data stream identifier according to a first sequence number, and updates a third state parameter of a target wireless bearer corresponding to the target data stream, so as to achieve the same bearer count value when the same data packet is transmitted between different access network elements, thereby ensuring the service continuity of the UE when switching between different access network elements. The embodiment of the present application solves the problem in the prior art that the corresponding bearer count values may be different when the same data packet is transmitted between different access network nodes in the PTM transmission mechanism.

[0198] It should be noted that the division of units in the embodiments of the present application is schematic and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0199] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0200] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0201] like Figure 5 As shown, an embodiment of the present application further provides a network device, including a memory 520, a transceiver 540, and a processor 510;

[0202] Memory 520, for storing computer programs;

[0203] a transceiver 540 for receiving and sending data under the control of the processor 510;

[0204] The processor 510 is configured to read the computer program in the memory 520 and perform the following operations:

[0205] receiving target information sent by a core network element, and obtaining a first state parameter included in the target information; the first state parameter includes a data flow identifier and a first sequence number; the first sequence number is a sequence number corresponding to a transmission order of the first data packet transmitted by the core network element via the target transmission interface;

[0206] generating, based on the first sequence number, a second state parameter of a target data flow corresponding to the data flow identifier; the second state parameter indicating a count value of data packets of the target data flow transmitted by the core network element;

[0207] A third state parameter of a target radio bearer corresponding to the target data flow is updated; the third state parameter indicates a count value of data packets carried by the target radio bearer.

[0208] Optionally, in the embodiment of the present application, the processor 510 is configured to:

[0209] When the second data packet is sent through the air interface bearer, it carries a second sequence number; the second sequence number is determined by the third state parameter corresponding to the air interface bearer.

[0210] Optionally, in the embodiment of the present application, generating, according to the first sequence number, a second state parameter of the target data flow corresponding to the data flow identifier includes:

[0211] Using the first sequence number as a second state parameter of the target data stream corresponding to the data stream identifier; or

[0212] The first sequence number is incremented by one, or the first sequence number is incremented by one and then modulo-processed with a preset sequence number threshold to obtain a second state parameter of the target data flow corresponding to the data flow identifier.

[0213] Optionally, in the embodiment of the present application, obtaining the first state parameter carried in the target information includes:

[0214] Obtaining a data flow identifier and an initial first sequence number carried in the target information, using the data flow identifier as the data flow identifier of the first state parameter, and using the initial first sequence number as the first sequence number of the first state parameter, or

[0215] Obtain the data flow identifier and the fourth sequence number carried in the target information, use the data flow identifier as the data flow identifier of the first state parameter, and generate the first sequence number of the first state parameter based on the fourth sequence number and the third state parameter.

[0216] Optionally, in an embodiment of the present application, the target information includes the first data packet or synchronization information.

[0217] Optionally, in the embodiment of the present application, updating the third state parameter of the target radio bearer corresponding to the target data flow includes:

[0218] Determining a target radio bearer corresponding to the target data flow;

[0219] The second state parameters corresponding to the data flows carried by the target radio bearer are summed to obtain a third state parameter of the target radio bearer.

[0220] Among them, Figure 5 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors 510 represented by processor 510 and various circuits of memory 520 represented by memory 520 are linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are all well known in the art and therefore will not be described further herein. The bus interface 530 provides an interface. The transceiver 540 may be a plurality of components, i.e., a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, such as a wireless channel, a wired channel, an optical cable, and the like. The processor 510 is responsible for managing the bus architecture and general processing, and the memory 520 may store data used by the processor 510 when performing operations.

[0221] The processor 510 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor 510 may also adopt a multi-core architecture.

[0222] The processor 510 is configured to execute any of the methods provided in the embodiments of the present application according to the obtained executable instructions by calling the computer program stored in the memory 520. The processor 510 and the memory 520 may also be physically separated.

[0223] like Figure 6 As shown, an embodiment of the present application further provides a terminal, including a memory 620, a transceiver 640, and a processor 610;

[0224] Memory 620, for storing computer programs;

[0225] a transceiver 640 for receiving and sending data under the control of the processor 610;

[0226] The processor 610 is configured to read the computer program in the memory 620 and perform the following operations:

[0227] Sending target information to an access network element, where the target information carries a first state parameter of the first data packet, so that the access network element generates a second state parameter of a target data flow corresponding to the data flow identifier based on the first sequence number, and updates a third state parameter of a target radio bearer corresponding to the target data flow;

[0228] The first state parameter includes a data flow identifier and a first sequence number corresponding to the first data packet; the first sequence number is a sequence number corresponding to the transmission order of the first data packet transmitted by the core network element via the target transmission interface;

[0229] The second state parameter indicates a count value of data packets of the target data flow transmitted by the core network element; the third state parameter indicates the number of data packets carried by the target radio bearer.

[0230] Optionally, in an embodiment of the present application, the target information includes the first data packet or synchronization information.

[0231] Among them, Figure 6In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors 610 represented by processor 610 and various circuits of memory 620 represented by memory 620 are linked together. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are all well known in the art and therefore will not be described further herein. The bus interface 630 provides an interface. The transceiver 640 may be a plurality of components, i.e., a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, such as a wireless channel, a wired channel, an optical cable, and the like. The processor 610 is responsible for managing the bus architecture and general processing, and the memory 620 may store data used by the processor 610 when performing operations.

[0232] The processor 610 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor 610 may also adopt a multi-core architecture.

[0233] The processor 610 is configured to execute any of the methods provided in the embodiments of the present application according to the obtained executable instructions by calling the computer program stored in the memory 620. The processor 610 and the memory 620 may also be physically separated.

[0234] It should be noted here that the above-mentioned device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0235] An embodiment of the present application further provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the state parameter processing method.

[0236] The processor-readable storage medium can be any available medium or data storage device that can be accessed by the processor, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO)), optical storage (such as CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (such as ROMs, EPROMs, EEPROMs, non-volatile memories (NANDFLASH), solid-state drives (SSDs)), etc.

[0237] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage and optical storage, etc.) that contain computer-usable program code.

[0238] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the steps in the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0239] These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor-readable memory produce an article of manufacture comprising an instruction device that implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0240] These processor-executable instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are performed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 a process or multiple processes and / or boxes Figure 1 The steps for the function specified in one or more boxes.

[0241] Obviously, those skilled in the art may make various changes and modifications to this application without departing from the spirit and scope of this application. Thus, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalents, this application is intended to include these modifications and variations.

Claims

1. A state parameter processing method, applied to an access network element, characterized in that: include: Receiving target information sent by a core network element, and obtaining a first state parameter included in the target information; The first state parameter includes a data stream identifier and a first sequence number; The first sequence number is a sequence number corresponding to the transmission order of the first data packet transmitted by the core network element via the target transmission interface; generating, based on the first sequence number, a second state parameter of a target data flow corresponding to the data flow identifier; the second state parameter indicating a count value of data packets of the target data flow transmitted by the core network element; A third state parameter of a target radio bearer corresponding to the target data flow is updated according to the second state parameter; the third state parameter indicates a count value of data packets carried by the target radio bearer.

2. The state parameter processing method according to claim 1, characterized in that: The method comprises: When the second data packet is sent through the air interface bearer, it carries a second sequence number; the second sequence number is determined by the third state parameter corresponding to the air interface bearer.

3. The state parameter processing method according to claim 1, characterized in that: Generating, according to the first sequence number, a second state parameter of the target data stream corresponding to the data stream identifier includes: Using the first sequence number as a second state parameter of the target data stream corresponding to the data stream identifier; or The first sequence number is incremented by one, or the first sequence number is incremented by one and then modulo-processed with a preset sequence number threshold to obtain a second state parameter of the target data flow corresponding to the data flow identifier.

4. The state parameter processing method according to claim 1, characterized in that: The obtaining of the first state parameter carried in the target information includes: Obtaining a data flow identifier and an initial first sequence number carried in the target information, using the data flow identifier as the data flow identifier of the first state parameter, and using the initial first sequence number as the first sequence number of the first state parameter, or Obtain the data flow identifier and the fourth serial number carried in the target information, use the data flow identifier as the data flow identifier of the first state parameter, and generate the first serial number of the first state parameter based on the fourth serial number and the third state parameter.

5. The state parameter processing method according to claim 1, characterized in that: The target information includes the first data packet or synchronization information.

6. The state parameter processing method according to claim 1, characterized in that: The updating of the third state parameter of the target radio bearer corresponding to the target data flow includes: Determining a target radio bearer corresponding to the target data flow; The second state parameters corresponding to the data flows carried by the target radio bearer are summed to obtain a third state parameter of the target radio bearer.

7. A state parameter processing method, applied to a core network element, characterized in that: include: Sending target information to an access network element, where the target information carries a first state parameter of the first data packet, so that the access network element generates a second state parameter of a target data flow corresponding to the data flow identifier based on the first sequence number, and updates a third state parameter of a target radio bearer corresponding to the target data flow based on the second state parameter; The first state parameter includes a data flow identifier and a first sequence number corresponding to the first data packet; the first sequence number is a sequence number corresponding to the transmission order of the first data packet transmitted by the core network element via the target transmission interface; The second state parameter indicates a count value of data packets of the target data flow transmitted by the core network element; the third state parameter indicates the number of data packets carried by the target radio bearer.

8. The state parameter processing method according to claim 7, characterized in that: The target information includes the first data packet or synchronization information.

9. A network device, characterized in that: Including memory, transceiver, processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: receiving target information sent by a core network element, and obtaining a first state parameter included in the target information; the first state parameter includes a data flow identifier and a first sequence number; the first sequence number is a sequence number corresponding to a transmission order of the first data packet transmitted by the core network element via the target transmission interface; generating, based on the first sequence number, a second state parameter of a target data flow corresponding to the data flow identifier; the second state parameter indicating a count value of data packets of the target data flow transmitted by the core network element; A third state parameter of a target radio bearer corresponding to the target data flow is updated according to the second state parameter; the third state parameter indicates a count value of data packets carried by the target radio bearer.

10. The network device according to claim 9, characterized in that The processor is configured to: When the second data packet is sent through the air interface bearer, it carries a second sequence number; the second sequence number is determined by the third state parameter corresponding to the air interface bearer.

11. The network device according to claim 9, wherein: Generating, according to the first sequence number, a second state parameter of the target data stream corresponding to the data stream identifier includes: Using the first sequence number as a second state parameter of the target data stream corresponding to the data stream identifier; or The first sequence number is incremented by one, or the first sequence number is incremented by one and then modulo-processed with a preset sequence number threshold to obtain a second state parameter of the target data flow corresponding to the data flow identifier.

12. The network device according to claim 9, wherein: The obtaining of the first state parameter carried in the target information includes: Obtaining a data flow identifier and an initial first sequence number carried in the target information, using the data flow identifier as the data flow identifier of the first state parameter, and using the initial first sequence number as the first sequence number of the first state parameter, or Obtain the data flow identifier and the fourth serial number carried in the target information, use the data flow identifier as the data flow identifier of the first state parameter, and generate the first serial number of the first state parameter based on the fourth serial number and the third state parameter.

13. The network device according to claim 9, wherein: The target information includes the first data packet or synchronization information.

14. The network device according to claim 9, wherein: The updating of the third state parameter of the target radio bearer corresponding to the target data flow includes: Determining a target radio bearer corresponding to the target data flow; The second state parameters corresponding to the data flows carried by the target radio bearer are summed to obtain a third state parameter of the target radio bearer.

15. A network device, characterized in that: Including memory, transceiver, processor: A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of the processor; and a processor for reading the computer program in the memory and performing the following operations: Sending target information to an access network element, where the target information carries a first state parameter of the first data packet, so that the access network element generates a second state parameter of a target data flow corresponding to the data flow identifier based on the first sequence number, and updates a third state parameter of a target radio bearer corresponding to the target data flow based on the second state parameter; The first state parameter includes the data flow identifier corresponding to the first data packet and the first sequence number; the first sequence number is a sequence number corresponding to the transmission order of the first data packet transmitted by the core network element via the target transmission interface; The second state parameter indicates a count value of data packets of the target data flow transmitted by the core network element; the third state parameter indicates the number of data packets carried by the target radio bearer.

16. The network device according to claim 15, characterized in that The target information includes the first data packet or synchronization information.

17. A state parameter processing device, applied to an access network element, characterized in that: include: An information receiving module is configured to receive target information sent by a core network element and obtain a first state parameter included in the target information; The first state parameter includes a data flow identifier and a first sequence number; the first sequence number is a sequence number corresponding to the transmission order of the first data packet transmitted by the core network element via the target transmission interface; a parameter generating module, configured to generate, based on the first sequence number, a second state parameter of a target data flow corresponding to the data flow identifier; the second state parameter indicating a count value of data packets of the target data flow transmitted by the core network element; A parameter updating module is used to update a third state parameter of a target radio bearer corresponding to the target data flow according to the second state parameter; the third state parameter indicates a count value of data packets carried by the target radio bearer.

18. A state parameter processing device, applied to a core network element, characterized in that: include: an information sending module, configured to send target information to an access network element, wherein the target information carries a first state parameter of a first data packet, so that the access network element generates a second state parameter of a target data flow corresponding to the data flow identifier according to the first sequence number, and updates a third state parameter of a target radio bearer corresponding to the target data flow according to the second state parameter; The first state parameter includes the data flow identifier corresponding to the first data packet and the first sequence number; the first sequence number is a sequence number corresponding to the transmission order of the first data packet transmitted by the core network element via the target transmission interface; The second state parameter indicates a count value of data packets of the target data flow transmitted by the core network element; the third state parameter indicates the number of data packets carried by the target radio bearer.

19. A processor-readable storage medium, characterized in that: The processor-readable storage medium stores a computer program, and the computer program is configured to cause the processor to execute the method according to any one of claims 1 to 8.

Images