CN114710805B - Interaction method and device for slice service data, electronic equipment and readable medium - Google Patents
Interaction method and device for slice service data, electronic equipment and readable medium Download PDFInfo
- Publication number
- CN114710805B CN114710805B CN202210374881.8A CN202210374881A CN114710805B CN 114710805 B CN114710805 B CN 114710805B CN 202210374881 A CN202210374881 A CN 202210374881A CN 114710805 B CN114710805 B CN 114710805B
- Authority
- CN
- China
- Prior art keywords
- service
- slice
- nssai
- slicing
- slice service
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 230000003993 interaction Effects 0.000 title claims abstract description 71
- 238000000034 method Methods 0.000 title claims abstract description 56
- 238000004364 calculation method Methods 0.000 claims description 3
- 238000004458 analytical method Methods 0.000 claims description 2
- 238000007726 management method Methods 0.000 description 21
- 230000006870 function Effects 0.000 description 19
- 238000010586 diagram Methods 0.000 description 13
- 230000002452 interceptive effect Effects 0.000 description 7
- 238000012545 processing Methods 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 6
- 238000002955 isolation Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 238000004891 communication Methods 0.000 description 4
- 101000979909 Homo sapiens NMDA receptor synaptonuclear signaling and neuronal migration factor Proteins 0.000 description 3
- 101001109689 Homo sapiens Nuclear receptor subfamily 4 group A member 3 Proteins 0.000 description 3
- 102100024546 NMDA receptor synaptonuclear signaling and neuronal migration factor Human genes 0.000 description 3
- 102100022673 Nuclear receptor subfamily 4 group A member 3 Human genes 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 2
- 230000006399 behavior Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 238000013523 data management Methods 0.000 description 2
- 238000005538 encapsulation Methods 0.000 description 2
- 239000013307 optical fiber Substances 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 230000005641 tunneling Effects 0.000 description 2
- 230000001133 acceleration Effects 0.000 description 1
- 230000009471 action Effects 0.000 description 1
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000004069 differentiation Effects 0.000 description 1
- 230000002708 enhancing effect Effects 0.000 description 1
- 239000011521 glass Substances 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
- 230000002123 temporal effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/0252—Traffic management, e.g. flow control or congestion control per individual bearer or channel
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/08—Access security
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/02—Traffic management, e.g. flow control or congestion control
- H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
- H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
- H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
Abstract
The disclosure provides an interaction method, an interaction device, electronic equipment and a readable medium of slice service data, wherein the interaction method of slice service data comprises the following steps: responding to a slicing service requested to register by a terminal, and acquiring an IPv6 address corresponding to the slicing service; according to the slicing service, NSSAI slicing service identifiers are distributed to the terminal, the NSSAI slicing service identifiers are uniformly deployed in a 5GC core network and a 5GC bearing network, and the 5GC bearing network can identify the slicing service requested by the terminal according to the NSSAI slicing service identifiers; generating a data message, wherein NSSAI slice service identification is mapped to an extension header part of an IPv6 address of the data message; and feeding the data message back to the terminal so that the terminal can send a slice service request containing NSSAI slice service identification to the 5GC bearer network. By the embodiment of the disclosure, the accuracy and reliability of identifying the slicing service are improved, and the quality of differentiated service of the slicing network is improved.
Description
Technical Field
The disclosure relates to the technical field of network data interaction, in particular to a slice service data interaction method, a slice service data interaction device, electronic equipment and a readable medium.
Background
Currently, with the scale deployment of 5G networks, IPv6 is a main way, and 3GPP also defines the concept of 5G slice networks, where 5G slice networks include, but are not limited to, a wireless slice subnet, a bearer slice subnet, a core network slice subnet, and the like.
In the related technology, the bearing network of the current operator mainly adopts QoS and VPN to carry out isolation bearing, part of the bearing network only carries out slicing aiming at a control surface, and if network congestion occurs, differentiated service of 2B service cannot be ensured.
However, since the 3GPP does not define the transfer of the RAN/CN domain and the network slice identifier of the bearer on the data plane, there is no guarantee of end-to-end consistency of the network slice.
In addition, the existing carrier network technology adopts the FlexE interface technology to carry out slice isolation, and the method can ensure the service quality of the carrier network, but still is in a service splicing mode facing to a wireless network and a core network, and cannot meet the service requirement of end-to-end slice differentiation.
It should be noted that the information disclosed in the above background section is only for enhancing understanding of the background of the present disclosure and thus may include information that does not constitute prior art known to those of ordinary skill in the art.
Disclosure of Invention
It is an object of the present disclosure to provide an interaction method, apparatus, electronic device and readable medium for slicing traffic data, which overcome, at least to some extent, the problem of end-to-end inconsistency of network slices due to limitations and drawbacks of the related art.
According to a first aspect of embodiments of the present disclosure, there is provided an interaction method of slice service data, applicable to a 5GC core network, the interaction method of slice service data including: responding to a slicing service which a terminal requests to register, and acquiring an IPv6 address corresponding to the slicing service; according to the slicing service, NSSAI slicing service identifiers are distributed to the terminal, the NSSAI slicing service identifiers are uniformly deployed in the 5GC core network and the 5GC carrier network, and the 5GC carrier network can identify the slicing service requested by the terminal according to the NSSAI slicing service identifiers; generating a data message, wherein the NSSAI slice service identifier is mapped to an extension header part of an IPv6 address of the data message; and feeding the data message back to the terminal so that the terminal can send a slicing service request containing the NSSAI slicing service identifier to the 5GC bearer network.
In an exemplary embodiment of the present disclosure, further comprising: and defining attribute information of NSSAI slice service identification corresponding to the slice service request in a header extension header part of the IPv6 address.
In an exemplary embodiment of the present disclosure, further comprising: receiving NSSAI slice service identification fed back by the 5GC bearing network, wherein the NSSAI slice service identification is determined by analyzing the slice service request by the 5GC bearing network; comparing the tunnel path with the NSSAI slice service identifier; and determining whether to respond to the slicing service request according to the comparison result.
According to a second aspect of the embodiments of the present disclosure, there is provided an interaction method for slice service data, applicable to a 5GC bearer network, the interaction method for slice service data including: receiving a slicing service request sent by a terminal; analyzing NSSAI slice service identifiers included in the slice service request, wherein the NSSAI slice service identifiers are distributed to the terminal by a 5GC core network according to slice services, and the NSSAI slice service identifiers are uniformly deployed in the 5GC core network and a 5GC bearing network; and calculating a tunnel path corresponding to the NSSAI slice service identifier through a corresponding relation between a preset VLAN and the NSSAI slice service identifier.
In an exemplary embodiment of the present disclosure, further comprising: and forwarding the NSSAI slice service identifier to the 5GC core network so that the 5GC core network can compare the tunnel path with the NSSAI slice service identifier, and determining whether to respond to the slice service request according to a comparison result.
According to a third aspect of embodiments of the present disclosure, there is provided an interaction method of slice service data, applicable to a terminal, the interaction method of slice service data including: transmitting a slicing service requesting registration to a 5GC core network; receiving a data message fed back by the 5GC core network, wherein an NSSAI slice service identifier is written in an extension header part of an IPv6 address of the data message, and the NSSAI slice service identifier is distributed by the 5GC core network according to the slice service; and sending a slice service request containing the NSSAI slice service identifier to the 5GC bearing network, wherein the NSSAI slice service identifier is uniformly deployed in the 5GC core network and the 5GC bearing network.
According to a fourth aspect of the embodiments of the present disclosure, there is provided an interaction device for slice service data, which is applicable to a 5GC core network, where the interaction device for slice service data: the acquisition module is used for responding to the slicing service requested to be registered by the terminal and acquiring an IPv6 address corresponding to the slicing service; the allocation module is configured to allocate nsai slice service identifiers to the terminal according to the slice service, the nsai slice service identifiers are uniformly deployed in the 5GC core network and the 5GC carrier network, and the 5GC carrier network can identify the slice service requested by the terminal according to the nsai slice service identifiers; the generation module is arranged for generating a data message, and the NSSAI slice service identifier is mapped to an extension header part of an IPv6 address of the data message; and the sending module is used for feeding back the data message to the terminal so that the terminal can send a slice service request containing the NSSAI slice service identifier to the 5GC bearer network.
According to a fifth aspect of the embodiments of the present disclosure, there is provided an interaction device for slice service data, which is applicable to a 5GC bearer network, where the interaction device for slice service data is: the receiving module is used for receiving a slicing service request sent by the terminal; the analysis module is configured to analyze NSSAI slice service identifiers included in the slice service request, the NSSAI slice service identifiers are distributed to the terminal by a 5GC core network according to slice services, and the NSSAI slice service identifiers are uniformly deployed in the 5GC core network and a 5GC carrier network; and the calculation module is used for calculating a tunnel path corresponding to the NSSAI slice service identifier through a corresponding relation between a preset VLAN and the NSSAI slice service identifier.
According to a sixth aspect of the embodiments of the present disclosure, there is provided an interaction device for slice service data, adapted for a terminal, where the interaction device for slice service data: the sending module is used for sending a slicing service which requests registration to the 5GC core network; the receiving module is configured to receive a data message fed back by the 5GC core network, wherein an NSSAI slice service identifier is written in an extension header part of an IPv6 address of the data message, and the NSSAI slice service identifier is distributed by the 5GC core network according to the slice service; the sending module is further configured to send a slice service request including the nsai slice service identifier to the 5GC bearer network, where the nsai slice service identifier is uniformly deployed in the 5GC core network and the 5GC bearer network.
According to a seventh aspect of the present disclosure, there is provided an electronic device comprising: a memory; and a processor coupled to the memory, the processor configured to perform the method of any of the above based on instructions stored in the memory.
According to an eighth aspect of the present disclosure, there is provided a computer-readable storage medium having stored thereon a program which, when executed by a processor, implements the interaction method of slice service data as described in any one of the above.
According to the embodiment of the disclosure, the S-NSSAI slice service identifier is uniformly deployed in the 5GC core network and the 5GC carrier network, so that the end-to-end slice service marking of the 2B service slice is realized, the 5GC carrier network can accurately sense the slice service, the accuracy and the reliability of identifying the slice service are improved, and the differentiated service quality of the slice network is improved.
Further, the technical scheme of the present disclosure also provides an encapsulation format of the IPv6 extended slice label attribute, and provides a transmission scheme of the 5g 2b end-to-end slice service on the slice identifier (S-nsai) data plane of the RAN/CN domain and the bearer domain, so as to meet the slice requirement of the 5g 2b service application scenario.
Furthermore, the configuration of the IP address is simplified, and the accuracy and the reliability of the application of identifying the Slice are improved by configuring an IPv6 address between the RAN/CN and the 5GC bearing network, namely, only the Slice identifier which is in accordance with E2E (Slice Instance-ESI) carried in the IPv6 extension header can enter the network Slice of the 5GC bearing network, and the safety of the network Slice is further ensured.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure. It will be apparent to those of ordinary skill in the art that the drawings in the following description are merely examples of the disclosure and that other drawings may be derived from them without undue effort.
FIG. 1 illustrates a schematic diagram of an exemplary system architecture of an interaction scheme for sliced business data in the related art;
FIG. 2 is a flow chart of an interactive method of slicing business data in an exemplary embodiment of the present disclosure;
FIG. 3 is a flowchart of another method of interaction of slice business data in an exemplary embodiment of the present disclosure;
FIG. 4 is a flowchart of another method of interaction of slice business data in an exemplary embodiment of the present disclosure;
FIG. 5 is a flowchart of another method of interaction of slice business data in an exemplary embodiment of the present disclosure;
FIG. 6 is a flowchart of another method of interaction of slice business data in an exemplary embodiment of the present disclosure;
FIG. 7 is a flowchart of another method of interaction of slice business data in an exemplary embodiment of the present disclosure;
FIG. 8 is a schematic architecture diagram of another interaction scheme for slicing traffic data in an exemplary embodiment of the present disclosure;
FIG. 9 is a schematic diagram of packet interactions of another exemplary embodiment of the present disclosure for an interaction scheme for sliced traffic data;
FIG. 10 is a schematic diagram of a package format of another interaction scheme for sliced traffic data in an exemplary embodiment of the present disclosure;
FIG. 11 is a block diagram of an interactive apparatus for slicing business data in an exemplary embodiment of the present disclosure;
FIG. 12 is a block diagram of another interactive device for slicing business data in an exemplary embodiment of the present disclosure;
FIG. 13 is a block diagram of another interactive device for slicing business data in an exemplary embodiment of the present disclosure;
fig. 14 is a block diagram of an electronic device in an exemplary embodiment of the present disclosure.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments may be embodied in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the present disclosure. One skilled in the relevant art will recognize, however, that the aspects of the disclosure may be practiced without one or more of the specific details, or with other methods, components, devices, steps, etc. In other instances, well-known technical solutions have not been shown or described in detail to avoid obscuring aspects of the present disclosure.
Furthermore, the drawings are only schematic illustrations of the present disclosure, and the same reference numerals in the drawings denote the same or similar parts, and thus a repetitive description thereof will be omitted. Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in software or in one or more hardware modules or integrated circuits or in different networks and/or processor devices and/or microcontroller devices.
Fig. 1 shows a schematic diagram of an exemplary system architecture of an interaction scheme of slice traffic data in the related art.
As shown in fig. 1, an exemplary system architecture for an interaction scheme for sliced traffic data includes: CSMF slice traffic operation 102, NSMF end-to-end slice & subnet management 104, AN NSSMF (AN slice subnet management) 106, TN NSSMF (TN slice subnet management) 108, and CN NSSMF (CN slice subnet management) 110.
In particular, for network slice orchestration and management, 3GPP defines a network slice management system logically comprising three major functions, communication traffic management function (Communication Service Management Function, CSMF), network slice management function (Network Service Management Function, NSMF), network slice subnet management (Network Slice Subnet Management Function, NSSMF).
The CSMF is used for mapping the service requirement of the user to the Network slice requirement, the NSMF converts the Network slice requirement into a requirement of a sub-Network slice, and is responsible for management and arrangement of Network slice examples, the NSSMF converts the requirement of each sub-Network slice into a requirement of a Network function, and the NSSMF is further divided into wireless (Access Network, AN) slice subnet management (AN-NSSMF), core Network (CN) slice subnet management (CN-NSSMF) and transport Network (Transport Network, TN) slice subnet management (TN-NSSMF).
Based on the above architecture, the pull-through of the opposite end-to-end slice only involves the definition of the management level, and there is no excessive definition for the RAN/CN domain and the bearer domain, especially the bearer domain has no substantial content only for the corresponding frame. At present, the end-to-end slicing service developed based on the architecture is realized by loosely coupling the RAN/CN domain and the bearing domain on the forwarding plane or adopting an Overlay (overload) mode, the bearing network has no sense slicing service essence, and the corresponding slicing service quality cannot be ensured under the conditions of network congestion and service safety and convenience.
In addition, the part 5GC bearing network adopts VPN isolation and is mapped by VLAN (Virtual Local Area Network ) +DSCP (Differentiated Services Code Point, differential service code point), in this way, because the service QoS (Quality of Service, service quality) grade is limited, the data with different slice quality requirements run under the same physical interface, the user data isolation and service quality guarantee are strongly related with the network data forwarding, and the end-to-end slice service experience cannot be achieved.
The following describes example embodiments of the present disclosure in detail with reference to the accompanying drawings.
Fig. 2 is a flowchart of an interaction method of slice service data in an exemplary embodiment of the present disclosure.
Referring to fig. 2, the interaction method of slice service data is applicable to a 5GC core network, and the interaction method of slice service data includes:
step S202, responding to a slicing service of which the terminal requests to register, and acquiring an IPv6 address corresponding to the slicing service.
And step S204, an NSSAI slice service identifier is distributed to the terminal according to the slice service, the NSSAI slice service identifier is uniformly deployed in the 5GC core network and the 5GC carrier network, and the 5GC carrier network can identify the slice service requested by the terminal according to the NSSAI slice service identifier.
Step S206, generating a data message, wherein the NSSAI slice service identifier is mapped to an extension header part of an IPv6 address of the data message.
And step S208, feeding the data message back to the terminal so that the terminal can send a slice service request containing the NSSAI slice service identifier to the 5GC bearer network.
According to the embodiment of the disclosure, the S-NSSAI slice service identifier is uniformly deployed in the 5GC core network and the 5GC carrier network, so that the end-to-end slice service marking of the 2B service slice is realized, the 5GC carrier network can accurately sense the slice service, the accuracy and the reliability of identifying the slice service are improved, and the differentiated service quality of the slice network is improved.
Further, the technical scheme of the present disclosure also provides an encapsulation format of the IPv6 extended slice label attribute, and provides a transmission scheme of the 5g 2b end-to-end slice service on the slice identifier (S-nsai) data plane of the RAN/CN domain and the bearer domain, so as to meet the slice requirement of the 5g 2b service application scenario.
Furthermore, the configuration of the IP address is simplified, and the accuracy and the reliability of the application of identifying the Slice are improved by configuring an IPv6 address between the RAN/CN and the 5GC bearing network, namely, only the Slice identifier which is in accordance with E2E (Slice Instance-ESI) carried in the IPv6 extension header can enter the network Slice of the 5GC bearing network, and the safety of the network Slice is further ensured.
Next, each step of the interaction method of the slice service data will be described in detail.
In an exemplary embodiment of the present disclosure, as shown in fig. 3, further comprising:
step S302, defining the attribute information of NSSAI slice service identification corresponding to the slice service request in the header extension header part of the IPv6 address.
In the above embodiment, by defining the attribute information of the nsai slice service identifier corresponding to the slice service request in the header extension header portion of the IPv6 address, the setting scheme of the IP address is simplified, and the interaction efficiency of the network slice is improved.
In an exemplary embodiment of the present disclosure, as shown in fig. 4, further comprising:
step S402, receiving an nsai slice service identifier fed back by the 5GC bearer network, where the nsai slice service identifier is determined by the 5GC bearer network analyzing the slice service request.
Step S404, comparing the tunnel path with the nsai slice service identifier.
Step S406, determining whether to respond to the slicing service request according to the comparison result.
In the above embodiment, by receiving the nsai slice service identifier fed back by the 5GC bearer network, the nsai slice service identifier is determined by analyzing the slice service request by the 5GC bearer network, and comparing the tunnel path with the nsai slice service identifier, if it is determined according to the comparison result that the identifier of one network slice in the 5GC bearer network corresponds to the slice service request, the slice service request is responded, otherwise, the slice service request is not responded.
Fig. 5 is a flowchart of an interaction method of slice service data in an exemplary embodiment of the present disclosure.
Referring to fig. 5, the interaction method of slice service data is applicable to a 5GC bearer network, and the interaction method of slice service data includes:
step S502, receiving a slicing service request sent by a terminal.
Step S504, NSSAI slice service identifiers included in the slice service request are analyzed, the NSSAI slice service identifiers are distributed to the terminal by a 5GC core network according to slice services, and the NSSAI slice service identifiers are uniformly deployed in the 5GC core network and the 5GC carrier network.
Step S506, calculating a tunnel path corresponding to the NSSAI slice service identifier through a corresponding relation between a preset VLAN and the NSSAI slice service identifier.
In an exemplary embodiment of the present disclosure, as shown in fig. 6, further comprising:
step S602, forwarding the nsai slice service identifier to the 5GC core network, so that the 5GC core network compares the tunnel path with the nsai slice service identifier, and determines whether to respond to the slice service request according to the comparison result.
Fig. 7 is a flowchart of an interaction method of slice service data in an exemplary embodiment of the present disclosure.
Referring to fig. 7, the interaction method of slice service data is applicable to a terminal, and the interaction method of slice service data includes:
and step S702, transmitting the slicing service which requests registration to the 5GC core network.
Step S704, receiving a data packet fed back by the 5GC core network, where an nsai slice service identifier is written in an extension header portion of an IPv6 address of the data packet, and the nsai slice service identifier is allocated by the 5GC core network according to the slice service.
Step S706, a slice service request including the nsai slice service identifier is sent to the 5GC bearer network, where the nsai slice service identifier is uniformly deployed in the 5GC core network and the 5GC bearer network.
As shown in fig. 8, an architecture 800 of another interaction scheme for sliced traffic data in an exemplary embodiment of the present disclosure includes: a 2c &2b terminal, an air interface, a bearer network, a core network, etc.
The 2C &2B terminals comprise terminals of common internet surfing service, unmanned aerial vehicles, AR glasses and the like. The 5G NR (SA) is connected to the slice example 1, the slice examples 2, … …, etc. by connecting to the ring aggregation core. Network slice services may include, but are not limited to, 2C services (e.g., VR live postback, VR downstream viewing, game acceleration services, etc.), single-slice type 2B services (e.g., smart police) and shared slice type 2B services, e.g., deployed as three types, 2C slices, single-slice and shared slice, respectively. Network traffic slices ID1, 2, 3 … … n1, n2, n3, etc., and are differentially scheduled to 5QI-1, 5QI-4, 5QI-n, etc., by QoS quality, and these three types of slices are mapped by VLAN1000, VLAN2000, and VLAN3000, respectively.
FlexE (flexible ethernet technology) interface technology based network slice as shown in fig. 8: the wireless side adopts soft slice modes such as slice ID+5QI, the bearing side adopts a mode of combining soft slice and hard slice, and the core network adopts a sharing or independent mode of a hardware resource layer, a virtual resource layer and a network element function layer
Hard isolation is performed on the carrier network side through a FlexE interface technology, although data can be ensured to be isolated in the carrier network, the current 5G granularity standard is adopted for slicing FlexE slices, the resource loss is too large for slicing the carrier network, the number of slices is limited, if multiple services share one slice, the data flow of the same FlexE slice can not be identified according to slice service when the data plane is forwarded, and the service quality in the shared slice can be seriously affected when the shared slice is congested.
In addition, the network slice service generates a virtualized slice instance through PW (pseudowire), RAN (VPN/PlexE interface) and 5GC network elements, which may be, for example, AMF (Access and Mobility Management Function, access and mobility management functions), SMF (Session Management function, session management functions), PCF (Policy Control function, policy control functions), UPF (The User plane function, user plane functions and UDM (The Unified Data Management, unified data management functions), etc., but is not limited thereto.
Based on the architecture shown in fig. 8, as shown in fig. 9, in another architecture 900 of an interaction scheme of slice service data in an exemplary embodiment of the present disclosure, after a 5GC core network and a 5GC bearer network uniformly deploy a slice service (service) identifier 1, a slice service (service) identifier 2, and a slice service (service) identifier 3, a terminal sends a slice service request to a base station, and the slice service request is matched to a corresponding network slice through vlan+sliceid1, vlan+sliceid2, and vlan+sliceid3, respectively.
The initial IP address of the terminal includes: etc (ethernet), IPv6Head (IPv 6 header), HBH (S-NSSAI), GTP ((GPRSTunnelingProtocol, GPRS tunneling protocol), payload), and the like.
The terminal will assign a corresponding nsai slice service tag when registering with the 5GC (core network), and the IP address after the tag includes fields such as ETH (ethernet), IPv6Head (VPN SID), HBH (VTN ID), SRH (packet header of segment route), IPv6Head, HBH (S-nsai), GTP ((GPRSTunnelingProtocol, GPRS tunneling protocol), and Payload).
As shown in fig. 10, a package format 1000 of another interaction scheme of slice service data in an exemplary embodiment of the present disclosure includes: IPv6, traffic type, flow label, message Payload length, next header type, hop limit, source address, destination address, next header type, message length, option type, option length, S-NSSAI identification, GTP tunnel (upper layer protocol data unit) and Payload data, and encapsulated in the manner shown in fig. 10.
The 5G 2B slice service is characterized in that the corresponding wireless service data is packaged in a GTP tunnel because of the channel of the bearing network on the wireless side and the core network side, the bearing network cannot sense the corresponding slice service data forwarding behavior on the wireless terminal and can only be distinguished by a complex VLAN, so that the S-NSSAI slice identifier of the bearing network is defined for the expansion of the IPv6 header, and the uniqueness of the slice service data forwarding behavior and the slice is ensured.
In addition, after the wireless terminal registers with the 5GC core network, the 5GC core network has the capability of providing slicing service, corresponding slicing identifiers are distributed to the terminal, corresponding data are packaged in a GTP tunnel in the communication between the terminal and the 5GC core network, and the GTP heavy NSSAI slicing identifiers are mapped to IPv6 data message packages through IPv6 expansion, so that the bearing network perceives the slicing service type, and the end-to-end guarantee of the slicing service is further improved.
According to the technical scheme, the expanded IPv6 header message format has the end-to-end capability of the corresponding slice identifier in the slice service data forwarding process, and the problem of guaranteeing the 2B service quality with certainty and low time delay in a service loose coupling or Overlay mode is solved.
Corresponding to the method embodiment, the disclosure further provides an interaction device for slicing service data, which can be used for executing the method embodiment.
Fig. 11 is a block diagram of an interactive apparatus for slicing traffic data in an exemplary embodiment of the present disclosure.
Referring to fig. 11, an interaction device 1100 for slicing service data is applicable to a 5GC core network, and the interaction device 1100 for slicing service data includes:
and the acquisition module 1102 is configured to respond to the slicing service requested to be registered by the terminal and acquire the IPv6 address corresponding to the slicing service.
The allocation module 1104 is configured to allocate nsai slice service identifiers to the terminal according to the slice service, where the nsai slice service identifiers are uniformly deployed in the 5GC core network and the 5GC bearer network, and the 5GC bearer network can identify the slice service requested by the terminal according to the nsai slice service identifiers.
The generating module 1106 is configured to generate a data packet, where the NSSAI slice service identifier is mapped to an extension header portion of an IPv6 address of the data packet.
And a sending module 1108, configured to feed back the data packet to the terminal, so that the terminal sends a slice service request including the nsai slice service identifier to the 5GC bearer network.
In an exemplary embodiment of the present disclosure, the interaction device 1100 for slicing service data is further configured to: and defining attribute information of NSSAI slice service identification corresponding to the slice service request in a header extension header part of the IPv6 address.
In an exemplary embodiment of the present disclosure, the interaction device 1100 for slicing service data is further configured to: receiving NSSAI slice service identification fed back by the 5GC bearing network, wherein the NSSAI slice service identification is determined by analyzing the slice service request by the 5GC bearing network; comparing the tunnel path with the NSSAI slice service identifier; and determining whether to respond to the slicing service request according to the comparison result.
Fig. 12 is a block diagram of an interactive apparatus for slicing traffic data in an exemplary embodiment of the present disclosure.
Referring to fig. 12, an interaction device 1200 for slicing service data, adapted to a 5GC bearer network, the interaction device 1200 for slicing service data includes:
and the receiving module 1202 is configured to receive a slice service request sent by the terminal.
The parsing module 1204 is configured to parse the nsai slice service identifier included in the slice service request, where the nsai slice service identifier is allocated to the terminal by the 5GC core network according to the slice service, and the nsai slice service identifier is uniformly deployed in the 5GC core network and the 5GC bearer network.
The calculating module 1206 is configured to calculate a tunnel path corresponding to the nsai slice service identifier through a preset correspondence between VLAN and nsai slice service identifier.
In an exemplary embodiment of the present disclosure, the interaction device 1200 of slice service data is further configured to: and forwarding the NSSAI slice service identifier to the 5GC core network so that the 5GC core network can compare the tunnel path with the NSSAI slice service identifier, and determining whether to respond to the slice service request according to a comparison result.
Fig. 13 is a block diagram of an interactive apparatus for slicing traffic data in an exemplary embodiment of the present disclosure.
Referring to fig. 13, an interaction device 1300 for slicing service data is suitable for a terminal, and the interaction device 1300 for slicing service data includes:
a sending module 1302, configured to send a slice service requesting registration to the 5GC core network.
The receiving module 1304 is configured to receive a data packet fed back by the 5GC core network, where an nsai slice service identifier is written in an extension header portion of an IPv6 address of the data packet, and the nsai slice service identifier is allocated by the 5GC core network according to the slice service.
The sending module 1302 is further configured to send a slice service request including the nsaai slice service identifier to the 5GC bearer network, where the nsaai slice service identifier is uniformly deployed in the 5GC core network and the 5GC bearer network.
Since the functions of the interaction device 1100 for slicing service data, the interaction device 1200 for slicing service data, and the interaction device 1300 for slicing service data are described in detail in the corresponding method embodiments, the disclosure is not repeated herein.
It should be noted that although in the above detailed description several modules or units of a device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit in accordance with embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.
In an exemplary embodiment of the present disclosure, an electronic device capable of implementing the above method is also provided.
Those skilled in the art will appreciate that the various aspects of the invention may be implemented as a system, method, or program product. Accordingly, aspects of the invention may be embodied in the following forms, namely: an entirely hardware embodiment, an entirely software embodiment (including firmware, micro-code, etc.) or an embodiment combining hardware and software aspects may be referred to herein as a "circuit," module "or" system.
An electronic device 1400 according to such an embodiment of the invention is described below with reference to fig. 14. The electronic device 1400 shown in fig. 14 is merely an example and should not be construed as limiting the functionality and scope of use of embodiments of the present invention.
As shown in fig. 14, the electronic device 1400 is embodied in the form of a general purpose computing device. Components of electronic device 1400 may include, but are not limited to: the at least one processing unit 1410, the at least one memory unit 1420, and a bus 1430 connecting the different system components (including the memory unit 1420 and the processing unit 1410).
Wherein the storage unit stores program code that is executable by the processing unit 1410 such that the processing unit 1410 performs steps according to various exemplary embodiments of the present invention described in the above section of the "exemplary method" of the present specification. For example, the processing unit 1410 may perform the methods as shown in the embodiments of the present disclosure.
The memory unit 1420 may include readable media in the form of volatile memory units, such as Random Access Memory (RAM) 14201 and/or cache memory 14202, and may further include Read Only Memory (ROM) 14203.
The memory unit 1420 may also include a program/utility 14204 having a set (at least one) of program modules 14205, such program modules 14205 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment.
Bus 1430 may be a local bus representing one or more of several types of bus structures including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or using any of a variety of bus architectures.
The electronic device 1400 may also communicate with one or more external devices 1440 (e.g., keyboard, pointing device, bluetooth device, etc.), one or more devices that enable a user to interact with the electronic device 1400, and/or any device (e.g., router, modem, etc.) that enables the electronic device 1400 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 1450. Also, electronic device 1400 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet, through network adapter 1460. As shown, the network adapter 1460 communicates with other modules of the electronic device 1400 via the bus 1430. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 1400, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware. Thus, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.) or on a network, including several instructions to cause a computing device (may be a personal computer, a server, a terminal device, or a network device, etc.) to perform the method according to the embodiments of the present disclosure.
In an exemplary embodiment of the present disclosure, a computer-readable storage medium having stored thereon a program product capable of implementing the method described above in the present specification is also provided. In some possible embodiments, the various aspects of the invention may also be implemented in the form of a program product comprising program code for causing a terminal device to carry out the steps according to the various exemplary embodiments of the invention as described in the "exemplary methods" section of this specification, when said program product is run on the terminal device.
The program product for implementing the above-described method according to an embodiment of the present invention may employ a portable compact disc read-only memory (CD-ROM) and include program code, and may be run on a terminal device such as a personal computer. However, the program product of the present invention is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium would include the following: an electrical connection having one or more wires, a portable disk, a hard disk, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The computer readable signal medium may include a data signal propagated in baseband or as part of a carrier wave with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected via the Internet using an Internet service provider).
Furthermore, the above-described drawings are only schematic illustrations of processes included in the method according to the exemplary embodiment of the present invention, and are not intended to be limiting. It will be readily appreciated that the processes shown in the above figures do not indicate or limit the temporal order of these processes. In addition, it is also readily understood that these processes may be performed synchronously or asynchronously, for example, among a plurality of modules.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any adaptations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
Claims (10)
1. The interaction method of the slice service data is characterized by being suitable for a 5GC core network, and comprises the following steps:
responding to a slicing service which a terminal requests to register, and acquiring an IPv6 address corresponding to the slicing service;
according to the slicing service, NSSAI slicing service identifiers are distributed to the terminal, the NSSAI slicing service identifiers are uniformly deployed in the 5GC core network and the 5GC carrier network, and the 5GC carrier network can identify the slicing service requested by the terminal according to the NSSAI slicing service identifiers;
generating a data message, wherein the NSSAI slice service identifier is mapped to an extension header part of an IPv6 address of the data message;
and feeding the data message back to the terminal so that the terminal can send a slicing service request containing the NSSAI slicing service identifier to the 5GC bearer network.
2. The method of interaction of slice traffic data of claim 1, further comprising:
and defining attribute information of NSSAI slice service identification corresponding to the slice service request in a header extension header part of the IPv6 address.
3. The interaction method of slice service data according to claim 1 or 2, further comprising:
receiving NSSAI slice service identification fed back by the 5GC bearing network, wherein the NSSAI slice service identification is determined by analyzing the slice service request by the 5GC bearing network;
comparing a tunnel path with the NSSAI slice service identifier, wherein the tunnel path is determined through the calculation of the corresponding relation between a preset VLAN and the NSSAI slice service identifier;
and determining whether to respond to the slicing service request according to the comparison result.
4. The interaction method of the slice service data is characterized by being suitable for a 5GC bearing network, and comprises the following steps:
receiving a slicing service request sent by a terminal;
analyzing NSSAI slice service identifiers included in the slice service request, wherein the NSSAI slice service identifiers are distributed to the terminal by a 5GC core network according to slice services, and the NSSAI slice service identifiers are uniformly deployed in the 5GC core network and a 5GC bearing network;
calculating a tunnel path corresponding to NSSAI slice service identification through a corresponding relation between a preset VLAN and the NSSAI slice service identification,
before receiving a slicing service request sent by the terminal, the 5GC core network responds to the slicing service requested to be registered by the terminal, acquires an IPv6 address corresponding to the slicing service, distributes NSSAI slicing service identifiers to the terminal according to the slicing service, maps the NSSAI slicing service identifiers to an extension head part of the IPv6 address of a data message, and feeds back the data message to the terminal.
5. The method of interacting sliced traffic data of claim 4 further comprising:
and forwarding the NSSAI slice service identifier to the 5GC core network so that the 5GC core network can compare the tunnel path with the NSSAI slice service identifier, and determining whether to respond to the slice service request according to a comparison result.
6. The interaction method of the slice service data is characterized by being suitable for a terminal, and comprises the following steps:
transmitting a slicing service requesting registration to a 5GC core network;
receiving a data message fed back by the 5GC core network, wherein an NSSAI slice service identifier is written in an extension header part of an IPv6 address of the data message, and the NSSAI slice service identifier is distributed by the 5GC core network according to the slice service;
and sending the slice service request containing the NSSAI slice service identifier to a 5GC bearing network, wherein the NSSAI slice service identifier is uniformly deployed in the 5GC core network and the 5GC bearing network.
7. An interaction device for slice service data, which is suitable for a 5GC core network, comprising:
the acquisition module is used for responding to the slicing service requested to be registered by the terminal and acquiring an IPv6 address corresponding to the slicing service;
the allocation module is configured to allocate nsai slice service identifiers to the terminal according to the slice service, the nsai slice service identifiers are uniformly deployed in the 5GC core network and the 5GC carrier network, and the 5GC carrier network can identify the slice service requested by the terminal according to the nsai slice service identifiers;
the generation module is arranged for generating a data message, and the NSSAI slice service identifier is mapped to an extension header part of an IPv6 address of the data message;
and the sending module is used for feeding back the data message to the terminal so that the terminal can send a slice service request containing the NSSAI slice service identifier to the 5GC bearer network.
8. An interaction device for slicing service data, which is suitable for a 5GC bearer network, comprises:
the receiving module is used for receiving a slicing service request sent by the terminal;
the analysis module is configured to analyze NSSAI slice service identifiers included in the slice service request, the NSSAI slice service identifiers are distributed to the terminal by a 5GC core network according to slice services, and the NSSAI slice service identifiers are uniformly deployed in the 5GC core network and a 5GC carrier network;
the calculation module is set to calculate a tunnel path corresponding to the NSSAI slice service identifier through a corresponding relation between a preset VLAN and the NSSAI slice service identifier;
the interaction device of slice service data is further used for: before receiving a slicing service request sent by the terminal, the 5GC core network responds to the slicing service requested to be registered by the terminal, acquires an IPv6 address corresponding to the slicing service, distributes NSSAI slicing service identifiers to the terminal according to the slicing service, maps the NSSAI slicing service identifiers to an extension head part of the IPv6 address of a data message, and feeds back the data message to the terminal.
9. An interaction device for slicing service data, which is suitable for a terminal, comprises:
the sending module is used for sending a slicing service which requests registration to the 5GC core network;
the receiving module is configured to receive a data message fed back by the 5GC core network, wherein an NSSAI slice service identifier is written in an extension header part of an IPv6 address of the data message, and the NSSAI slice service identifier is distributed by the 5GC core network according to the slice service;
the sending module is further configured to send a slice service request including the nsai slice service identifier to a 5GC bearer network, where the nsai slice service identifier is uniformly deployed in the 5GC core network and the 5GC bearer network.
10. A computer readable storage medium having stored thereon a program which when executed by a processor implements the interaction method of slice service data according to any one of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210374881.8A CN114710805B (en) | 2022-04-11 | 2022-04-11 | Interaction method and device for slice service data, electronic equipment and readable medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210374881.8A CN114710805B (en) | 2022-04-11 | 2022-04-11 | Interaction method and device for slice service data, electronic equipment and readable medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114710805A CN114710805A (en) | 2022-07-05 |
| CN114710805B true CN114710805B (en) | 2024-02-06 |
Family
ID=82173261
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210374881.8A Active CN114710805B (en) | 2022-04-11 | 2022-04-11 | Interaction method and device for slice service data, electronic equipment and readable medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114710805B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109167847A (en) * | 2018-08-09 | 2019-01-08 | 中国联合网络通信集团有限公司 | A kind of generation method and SMF, communication system of the address IPv6 |
| CN113328936A (en) * | 2020-02-28 | 2021-08-31 | 中国电信股份有限公司 | Route control method, system, device and computer readable storage medium |
| WO2021244356A1 (en) * | 2020-06-02 | 2021-12-09 | 中兴通讯股份有限公司 | Data transmission method and apparatus |
| CN113965938A (en) * | 2020-07-02 | 2022-01-21 | 中国联合网络通信集团有限公司 | Slicing service system and slicing service processing method |
| CN114302481A (en) * | 2021-12-28 | 2022-04-08 | 中国联合网络通信集团有限公司 | Slice selection method, MEP, application server, device and computer readable medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109560948B (en) * | 2017-09-25 | 2021-01-29 | 华为技术有限公司 | Network slice deployment method and related equipment |
| US11166179B2 (en) * | 2019-10-11 | 2021-11-02 | Verizon Patent And Licensing Inc. | Method and system for network slicing based on virtual routing and forwarding instances |
-
2022
- 2022-04-11 CN CN202210374881.8A patent/CN114710805B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109167847A (en) * | 2018-08-09 | 2019-01-08 | 中国联合网络通信集团有限公司 | A kind of generation method and SMF, communication system of the address IPv6 |
| CN113328936A (en) * | 2020-02-28 | 2021-08-31 | 中国电信股份有限公司 | Route control method, system, device and computer readable storage medium |
| WO2021244356A1 (en) * | 2020-06-02 | 2021-12-09 | 中兴通讯股份有限公司 | Data transmission method and apparatus |
| CN113965938A (en) * | 2020-07-02 | 2022-01-21 | 中国联合网络通信集团有限公司 | Slicing service system and slicing service processing method |
| CN114302481A (en) * | 2021-12-28 | 2022-04-08 | 中国联合网络通信集团有限公司 | Slice selection method, MEP, application server, device and computer readable medium |
Non-Patent Citations (1)
| Title |
|---|
| Ericsson.S2-186630 "Configured NSSAI update".3GPP tsg_sa\wg2_arch.2018,(第tsgs2_128_vilnius期),全文. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114710805A (en) | 2022-07-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110769039B (en) | Resource scheduling method and device, electronic equipment and computer readable storage medium | |
| CN112165725B (en) | Message processing method and device | |
| US20210320876A1 (en) | Mechanism to coordinate end to end quality of service between network nodes and service provider core | |
| CN109818917B (en) | Communication method and device thereof | |
| CN113132229B (en) | Segment identifier determination method and device | |
| CN113709057A (en) | Network congestion notification method, proxy node, network node and computer equipment | |
| CN110691370A (en) | Data transmission method, device and system | |
| CN112039796B (en) | Data packet transmission method and device, storage medium and electronic equipment | |
| KR20150076041A (en) | System for supporting multi-tenant based on private ip address in virtual private cloud networks and operating method thereof | |
| WO2022001835A1 (en) | Method and apparatus for sending message, and network device, system and storage medium | |
| CN107645433B (en) | Message forwarding method and device | |
| CN112511988B (en) | Message forwarding method, device, system, network device and storage medium | |
| CN111050361A (en) | Message transmission method, device and system | |
| CN112532673B (en) | Message sending method and device, computer readable storage medium and electronic equipment | |
| CN114302426B (en) | Method, device, medium and electronic equipment for controlling service quality in heterogeneous network | |
| CN112788060A (en) | Data packet transmission method and device, storage medium and electronic equipment | |
| CN111491010A (en) | Business cooperative processing method and related equipment | |
| WO2023179457A1 (en) | Method, apparatus and system for identifying service connection, and storage medium | |
| CN114710805B (en) | Interaction method and device for slice service data, electronic equipment and readable medium | |
| CN116527592A (en) | Application layer stream following detection method and device based on APN (access point) and related equipment | |
| CN114980359A (en) | Data forwarding method, device, equipment, system and storage medium | |
| CN116828024A (en) | Service connection identification method, device, system and storage medium | |
| CN114528114B (en) | Data processing method, device and equipment | |
| CN116346294A (en) | Communication method, device, related equipment and storage medium | |
| CN113783963A (en) | Data transmission method, server node, gateway device and network system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |