Section: 13.2.4.3.1.1 clearTextEncapsulatedMessage
Content: The clearTextEncapsulatedMessage is a JSON object that contains the non-encrypted portion of the original message.Specifically, it consists of the following objects: 1.a) Pseudo_Headers – the JSON object that includes all the Pseudo Headers in the message. - For HTTP Request messages, the object contains one entry for each of the ":method", ":path", ":scheme" and ":authority" pseudo headers. If the ":path" pseudoheader contains multiple parts separated by a slash (/) or includes a query parameter (following a "?"), an array is used to represent :path, with one element per part of the path (i.e. per "directory"). NOTE: This enables encryption of individual elements of the path (e.g. if SUPI is passed). - For HTTP Response messages, the object contains the ":status" pseudo header. 1.b) HTTP_Headers – the JSON object that includes all the Headers in the message. All the headers of the request are put into a JSON array called HTTP_Headers.Each entry contains a header name and value, where the value part can be an encoded index to the dataToIntegrityProtectAndCipher block, if the header value is encrypted. 1.c) Payload – the JSON object that includes the content of the payload of the HTTP message. Each attribute or IE in the payload shall form a single entry in the Payload JSON object. If there is any attribute value that requires encryption, it shall be moved into the dataToIntegrityProtectAndCipher JSON object (clause 13.2.4.2), and the original value in this element shall be replaced by the index in the form {"encBlockIdx": <num>} where "num" is the index of the corresponding entry in the dataToIntegrityProtectAndCipher array.