Search

EP-4740410-A1 - METHOD AND SYSTEM FOR IMPLEMENTING COMMON STACK PLATFORM FOR BYTE DIAGRAM-BASED PROTOCOLS

EP4740410A1EP 4740410 A1EP4740410 A1EP 4740410A1EP-4740410-A1

Abstract

The present disclosure relates to a method and a system for implementing common stack platform for byte diagram-based protocols For decoding the present disclosure encompasses receiving at the common stack platform, a message from a network node, the message comprising one or more information elements (IEs); creating, a stack object for the message, in an event the IE(s) are a familiar type IE; analysing, one or more IEs of the message by passing the message through the stack object; and decoding the message based on the analysis. For encoding messages, the present disclosure encompasses: providing at the common stack platform a value for each IE using a message byte diagram equivalent JSON configuration; and encoding the message based on the providing the value for the each IE. [Figure 3]

Inventors

  • BISHT, BIRENDRA
  • BHATNAGAR, AAYUSH
  • Singh, Harbinder Pal
  • Naskar, Suman
  • KUMAR, PRADEEP
  • ABHISHEK, Roy
  • MANDOWARA, Harshit
  • GARIKAPATI, Sandeep

Assignees

  • Jio Platforms Limited

Dates

Publication Date
20260513
Application Date
20240612

Claims (18)

  1. 1. A method for implementing a common stack platform [301] for decoding messages related to one or more byte diagram-based protocols, the method comprising: receiving, by a transceiver unit [3002] at the common stack platform [301], a message from a network node, the message comprising one or more information elements (IEs), wherein the message relates to one of the one or more byte diagram based protocols, and wherein each of the one or more IEs is one of: a fixed length IE and a variable length IE, and each of the one or more IEs is one of: a familiar type IE and an unfamiliar type IE; creating, by an object creator unit [3004] at the common stack platform [301], a stack object for the message, in an event the one or more IEs is the familiar type IE; analysing, by an analysis unit [3006] at the common stack platform [301], the one or more IEs of the message by passing the message through the stack object, using a message byte diagram equivalent JavaScript Object Notation (JSON) configuration, and one of: a decoding data for a fixed length IE in an event the one or more IE is a fixed length IE, and a decoding data for a variable length IE in an event the one or more IE is a variable length IE; and decoding, by a decoder unit [3008] at the common stack platform [301], the message based on the analysis.
  2. 2. The method as claimed in claim 1, wherein in an event an IE in the message is: the fixed length IE and the unfamiliar type IE, the method further comprises: - performing, by a traversal unit [3010] at the common stack platform [301], a full grammar traversal procedure for the IE; - generating, by the traversal unit [3010] at the common stack platform [301], the decoding data for the fixed length IE based on the full grammar traversal procedure; and storing, by a storage unit [3012] at the common stack platform [301 ], the decoding data generated for the fixed length IE.
  3. 3. The method as claimed in claim 1, wherein in an event an IE in the message is: the variable length IE and the unfamiliar type IE, the method further comprises: - performing, by a traversal unit [3010] at the common stack platform [301], a full grammar traversal procedure for the IE; - generating, by the traversal unit [3010] at the common stack platform [301], the decoding data for the variable length IE based on the full grammar traversal procedure, wherein the decoding data for the variable length IE comprises a graph in form of an adjacency matrix in three-dimensional form; and storing, by a storage unit [3012] of the common stack platform [301 ], the decoding data generated for the variable length IE.
  4. 4. The method as claimed in claim 3, wherein the analysing, by the analysis unit [3006] at the common stack platform [301], the one or more IES of the message using the decoding data for the variable length IE comprises: - performing, by the analysis unit [3006] at the common stack platform [301], a depth first search (DFS) traversal technique on the graph.
  5. 5. A method for implementing a common stack platform [301] for encoding messages related to one or more byte diagram-based protocols, the method comprising: receiving, by a transceiver unit [3102] at the common stack platform [301], an indication for sending a message to a network node, the message comprising one or more information elements (IEs), wherein the message relates to one of the one or more byte diagram based protocols, and wherein each of the one or more IEs is one of a fixed length IE and a variable length IE, and each of the one or more IEs is one of: a familiar type IE and an unfamiliar type IE; creating, by an object creator unit [3104] at the common stack platform [301], a stack object for the message, in an event the one or more IE is the familiar type IE; - providing, by an input unit [3106] at the common stack platform [301 ] , a value for said each of the one or more IEs in the message, using a message byte diagram equivalent JavaScript Object Notation (JSON) configuration, and one of: an encoding data for a fixed length IE in an event the one or more IE is a fixed length IE, and an encoding data for a variable length IE in an event the one or more IE is a variable length IE; and encoding, by an encoder unit [3108] at the common stack platform [301], the message based on the providing the value for the each of the one or more IEs in the message.
  6. 6. The method as claimed in claim 5, the wherein in an event an IE in the message is: the fixed length IE and the unfamiliar type IE, the method further comprises: - performing, by a traversal unit [3110] at the common stack platform [301], a full grammar traversal procedure for the IE; - generating, by the traversal unit [3110] at the common stack platform [301], the encoding data for the fixed length IE based on the full grammar traversal procedure; and storing, by a storage unit [3112] at the common stack platform [301], the encoding data generated for the fixed length IE.
  7. 7. The method as claimed in claim 5, wherein in an event an IE in the message is: the variable length IE and the unfamiliar type IE, the method further comprises: - performing, by a traversal unit [3110] at the common stack platform [301], a full grammar traversal procedure for the IE; - generating, by the traversal unit [3110] at the common stack platform [301], the encoding data for the variable length IE based on the full grammar traversal procedure, wherein the encoding data for the variable length IE comprises a graph in form of an adjacency matrix in three-dimensional form; and storing, by a storage unit [3112] at the common stack platform [301], the encoding data generated for the variable length IE.
  8. 8. The method as claimed in claim 7, wherein the providing, by the input unit [3106] at the common stack platform [301], the value for each of the one or more IES in the message using the encoding data for the variable length IE comprises: - performing, by the analysis unit [3106a] at the common stack platform [301], a depth first search (DFS) traversal technique on the graph.
  9. 9. A system [300] for decoding messages related to one or more byte diagram-based protocols, the system comprising: a transceiver unit [3002] configured to receive, at a common stack platform [301], a message from a network node, the message comprising one or more information elements (IEs), wherein the message relates to one of the one or more byte diagram based protocols, and wherein each of the one or more IEs is one of: a fixed length IE and a variable length IE, and each of the one or more IEs is one of: a familiar type IE and an unfamiliar type IE; an object creator unit [3004] configured to create, at the common stack platform [301], a stack object for the message, in an event the one or more IE is the familiar type IE; an analysis unit [3006] configured to analyse, at the common stack platform [301], one or more IEs of the message by passing the message through the stack object, using a message byte diagram equivalent JavaScript Object Notation (JSON) configuration, and one of: a decoding data for a fixed length IE in an event the one or more IE is a fixed length IE, and a decoding data for a variable length IE in an event the one or more IE is a variable length IE; and a decoder unit [3008] configured to decode, at the common stack platform [301], the message based on the analysis.
  10. 10. The system as claimed in claim 9, the system further comprising a traversal unit [3010] and a storage unit [3012], wherein in an event an IE in the message is: the fixed length IE and the unfamiliar type IE: - the traversal unit [3010] is configured to: o perform, at the common stack platform [301], a full grammar traversal procedure for the IE; and o generate, at the common stack platform [301], the decoding data for the fixed length IE based on the full grammar traversal procedure; and - the storage unit [3012] is configured to store, at the common stack platform [301], the decoding data generated for the fixed length IE.
  11. 11. The system as claimed in claim 9, the system further comprising a traversal unit [3010] and a storage unit [3012], wherein in an event an IE in the message is: the variable length IE and the unfamiliar type IE: - the traversal unit [3010] is configured to: o perform, at the common stack platform [301], a full grammar traversal procedure for the IE; o generate, at the common stack platform [301 ], the decoding data for the variable length IE based on the full grammar traversal procedure, wherein the decoding data for the variable length IE comprises a graph in form of an adjacency matrix in three-dimensional form; and - the storage unit [3012] is configured to store, at the common stack platform [301], the decoding data generated for the variable length IE.
  12. 12. The system as claimed in claim 11, wherein the analysis unit [3006], for analysing the one or more components of the message using the decoding data for the variable length IE, is configured to: - perform, at the common stack platform [301], a depth first search (DFS) traversal technique on the graph.
  13. 13. A system [300] for encoding messages related to one or more byte diagram-based protocols, the system comprising: a transceiver unit [3102] configured to receive, at a common stack platform [301], an indication for sending a message to a network node, the message comprising one or more information elements (IEs), wherein the message relates to one of the one or more byte diagram based protocols, and wherein each of the one or more IEs is one of a fixed length IE and a variable length IE, and each of the one or more IEs is one of: a familiar type IE and an unfamiliar type IE; an object creator unit [3104] configured to create, at the common stack platform [301], a stack object for the message, in an event the one or more IE is the familiar type IE; an input unit [3106] configured to provide, at the common stack platform [301 ] , a value for said each of the one or more IEs in the message, using a message byte diagram equivalent JavaScript Object Notation (JSON) configuration, and one of: an encoding data for a fixed length IE in an event the one or more IE is a fixed length IE, and an encoding data for a variable length IE in an event the one or more IE is the variable length IE; and an encoder unit [3108] configured to encode, at the common stack platform [301], the message based on the providing the value for the each of the one or more IEs in the message.
  14. 14. The system as claimed in claim 13, the system further comprising a traversal unit [3010] and a storage unit [3012], wherein in an event an IE in the message is: the fixed length IE and the unfamiliar type IE: - the traversal unit [3110] is configured to: o perform, at the common stack platform [301], a full grammar traversal procedure for the IE; and o generate, at the common stack platform [301], the encoding data for the fixed length IE based on the full grammar traversal procedure; and - the storage unit [3112] is configured to store, at the common stack platform [301], the encoding data generated for the fixed length IE.
  15. 15. The system as claimed in claim 13, the system further comprising a traversal unit [3010] and a storage unit [3012], wherein in an event an IE in the message is: the variable length IE and the unfamiliar type IE: - the traversal unit [3110] is configured to: o perform, at the common stack platform [301], a full grammar traversal procedure for the IE; o generate, at the common stack platform [301 ], the encoding data for the variable length IE based on the full grammar traversal procedure, wherein the encoding data for the variable length IE comprises a graph in form of an adjacency matrix in three-dimensional form; and - the storage unit [3112] is configured to store, at the common stack platform [301], the encoding data generated for the variable length IE.
  16. 16. The system as claimed in claim 15, wherein the input unit [3106], for providing the value for each of the one or more IES in the message using the encoding data for the variable length IE, is configured to: - perform, at the common stack platform [301], a depth first search (DFS) traversal technique on the graph.
  17. 17. A non-transitory computer readable storage medium storing instructions for decoding message related to one or more byte diagram based protocols, the instructions comprising executable code which, when executed by one or more units of a system [300], causes: a transceiver unit [3002] of the system to receive, at a common stack platform [301], a message from a network node, the message comprising one or more information elements (IEs), wherein the message relates to one of the one or more byte diagram based protocols, and wherein each of the one or more IEs is one of: a fixed length IE and a variable length IE, and each of the one or more IEs is one of: a familiar type IE and an unfamiliar type IE; an object creator unit [3004] of the system to create, at the common stack platform [301], a stack object for the message, in an event the one or more IE is the familiar type IE; an analysis unit [3006] of the system to analyse, at the common stack platform [301], one or more IEs of the message by passing the message through the stack object, using a message byte diagram equivalent JavaScript Object Notation (JSON) configuration, and one of: a decoding data for a fixed length IE in an event the one or more IE is a fixed length IE, and a decoding data for a variable length IE in an event the one or more IE is a variable length IE; and a decoder unit [3008] configured to decode, at the common stack platform [301], the message based on the analysis.
  18. 18. A non-transitory computer readable storage medium storing instructions for encoding messages related to one or more byte diagram based protocols, the instructions comprising executable code which, when executed by one or more units of a system [300], causes: a transceiver unit [3102] of the system to receive, at a common stack platform [301], an indication for sending a message to a network node, the message comprising one or more information elements (IEs), wherein the message relates to one of the one or more byte diagram based protocols, and wherein each of the one or more IEs is one of a fixed length IE and a variable length IE, and each of the one or more IEs is one of: a familiar type IE and an unfamiliar type IE; an object creator unit [3104] of the system to create, at the common stack platform [301], a stack object for the message, in an event the one or more IE is the familiar type IE; an input unit [3106] of the system to provide, at the common stack platform [301], a value for said each of the one or more IEs in the message, using a message byte diagram equivalent JavaScript Object Notation (JSON) configuration, and one of: an encoding data for a fixed length IE in an event the one or more IE is a fixed length IE, and an encoding data for a variable length IE in an event the one or more IE is the variable length IE; and an encoder unit [3108] of the system to encode, at the common stack platform [301], the message based on the providing the value for the each of the one or more IEs in the message.

Description

METHOD AND SYSTEM FOR IMPLEMENTING COMMON STACK PLATFORM FOR BYTE DIAGRAM-BASED PROTOCOLS FIELD OF THE DISCLOSURE [0001] Embodiments of the present disclosure generally relate to network performance management systems. More particularly, embodiments of the present disclosure relate to a method and system for implementing a common stack platform for encoding and decoding messages related to one or more byte diagram-based protocols. BACKGROUND [0002] The following description of the related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art. [0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. The third generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth-generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users. [0004] In the 5G communication system, there is provided a plurality of network functions (NFs), for example an Access and Mobility Management Function (AMF), session management function (SMF), Authentication Server function (AUSF), a Network Slice Selection Function (NSSF), Policy control function (PCF), a Network Repository Function (NRF), and the like. One or more of the aforementioned NFs communicates with each other, to implement multiple activities on the 5G communication system. There are multiple interfaces/protocols for receiving and transmitting messages for the NFs such as the AMF and/or the SMF of 5G network. Each such interface/protocol has large number of messages, and each message has larger number of information elements. For example, 5g- Non-Access Stratum (NAS) has 47 messages and 113 information elements, 4g -NAS has 61 messages and 109 information elements, Packet Forwarding Control Protocol (PFCP) has 22 messages and 248 information elements, General Packet Radio Service (GPRS) Tunnelling Protocol (GTPv2) has 50 messages and 212 information elements. [0005] For decoding and encoding of these messages, one of the existing solutions is a stack platform which decodes and encodes messages that are received or transmitted by NFs such as the AMF and/or the SMF of 5G network. As a result, for different protocols, a separate stack with a large number of messages and information elements has to be developed in existing approaches. This is a labor intensive, a time consuming and an inefficient approach, particularly because where there are changes in any message or information element structure, entire stack platform has to be again developed, tested and deployed. [0006] Further, information element and message specific classes are defined in a stack platform and separate application programming interfaces (APIs) are needed for each message class and information element specific class. Consequently, interfacing of stack platform with core application of the NFs such as the SMF and/or the AMF of 5G network is complex and voluminous work due to large of number of Application Programming Interfaces (APIs) involved in said interfacing. [0007] Thus, there exists an imperative need in the art to develop a method and a system for implementing common stack platform for efficient and effective encoding and decoding of different byte diagram-based protocols such as 5g-NAS, 4g-NAS, PFCP, and GTPv2, which the present disclosure aims to address. OBJECTS OF THE DISCLOSURE [0008] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below. [0009] It is an object of the present disclosure to provide a method and a system for implementing a common stack platform for different byte diagram-based protocols, wherein only common generic encoding and decoding APIs are used which results in reduction of number of Application Programming Interfaces (APIs) involved in interfacing with core application. [0010] It is yet another object