# US 12,004,261 B2 · Method and entity for checking port consistency of NIDD message > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,004,261 B2 - Document ID: US12004261B2 - Status: Granted - Kind: B2 - Application number: 17/763,581 - Filed: 2020-09-24 - Published: 2022-09-15 - Granted: 2024-06-04 - Earliest claimed: 2019-09-27 - Assignees: Telefonaktiebolaget LM Ericsson (publ) - Applicants: Telefonaktiebolaget LM Ericsson (publ) - Inventors: Wenliang Xu - Web page: https://patentgrep.com/patent/US12004261B2 ## CPC - H04L 45/306: {Route determination based on the nature of the carried application} - H04W 8/26: Network addressing or numbering for mobility support - H04L 47/803: {Application aware} - H04L 47/808: {User-type aware} - H04L 69/22: Parsing or analysis of headers - H04L 45/304: {Route determination for signalling traffic} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract Embodiments of the present disclosure provide a method and an entity for checking port consistency of NIDD message. A first aspect of the present disclosure provides a method performed at a first entity (100), comprising: receiving (S101), from a second entity, a non-internet protocol data delivery, NIDD, message including one or more RDS port numbers; and determining (S102) whether the one or more RDS port numbers are within a configured RDS port list. According to embodiments of the present disclosure, network resources for transmitting the invalid NIDD data may be saved, and undesired actions in the communication system may be avoided. ## Claims ### Claim 1 A method performed at a first entity, comprising: receiving, from a second entity, a non-internet protocol data delivery (NIDD) message comprising a first Reliable Data Service (RDS) port number; and after receiving the NIDD message comprising the first RDS port number, determining whether the first RDS port number included in the NIDD message is within a configured RDS port list; and as a result of determining that the first RDS port number is not within the configured RDS port list, transmitting to the second entity a response message indicating that at least one RDS port number included in the NIDD message is unknown in the first entity. ### Claim 2 (depends on 1) The method of claim 1, wherein the first RDS port number is a source port number and determining whether the first RDS port number is within the configured RDS port list comprises determining whether the source port number in the NIDD message is equal to a configured source port number in the configured RDS port list, or the first RDS port number is a destination port number and determining whether the first RDS port number is within the configured RDS port list comprises determining whether the destination port number in the NIDD message is equal to a configured destination port number in the configured RDS port list. ### Claim 3 (depends on 1) The method of claim 1, further comprising: discarding the NIDD message as a result of determining that the first RDS port number is not within the configured RDS port list. ### Claim 4 (depends on 1) The method of claim 1, wherein the response message comprises a ProblemDetails data structure comprising a cause attribute having a value, and the value of the cause attribute is set to RDS PORT UNKNOWN, thereby indicating that at least one RDS port number included in the NIDD message is unknown in the first entity. ### Claim 5 (depends on 4) The method of claim 4, wherein the response message is transmitted to a Service Capability Server/Application Server (SCS/AS) or an Application Function (AF), and the response message comprises at least one of: a Mobile Terminated (MT) NIDD submit Response message; a Group MT NIDD submit Response message; a NIDD Authorization Notification Request message; or a Mobile Originated (MO) NIDD Indication message. ### Claim 6 (depends on 5) The method of claim 5, further comprising: receiving an updated configured RDS port list from the SCS/AS or the AF, after transmitting the response message; or receiving an updated NIDD message from the SCS/AS or the AF, after transmitting the response message. ### Claim 7 (depends on 4) The method of claim 4, wherein the NIDD message is a Hypertext Transfer Protocol (HTTP) POST message, the NIDD message further comprises non-IP data, and the response message further comprises a status code set to the value 403. ### Claim 8 (depends on 1) The method of claim 1, wherein the first entity determines whether the first RDS port number is within the configured RDS port list after determining that an RDS port verification feature is supported. ### Claim 9 (depends on 1) The method of claim 1, wherein the first entity comprises a Service Capability Exposure Function (SCEF) or a Network Exposure Function (NEF), and the second entity comprises a Service Capability Server/Application Server (SCS/AS), or an Application Function (AF), or a terminal device. ### Claim 10 (depends on 1) The method of claim 1, wherein the response message comprises an NIDD status set to RDS_PORT_UNKNOWN and the first RDS port number. ### Claim 11 A method performed at a second entity, comprising: transmitting, to a first entity, a non-internet protocol data delivery (NIDD) message comprising a first Reliable Data Service (RDS) port number; and after transmitting the NIDD message to the first entity, receiving from the first entity a response message indicating that an RDS port number included in the NIDD message is not included in a configured RDS port list. ### Claim 12 (depends on 11) The method of claim 11, wherein the first RDS port number is a source port number and the first entity is configured to determine whether the source port number is equal to a configured source port number in the configured RDS port list, or the first RDS port number is a destination port number and the first entity is configured to determine whether the destination port number is equal to a configured destination port number in the configured RDS port list. ### Claim 13 (depends on 11) The method of claim 11, wherein the NIDD message is discarded by the first entity as a result of the first entity determining that the first RDS port number included in the NIDD message is not within the configured RDS port list. ### Claim 14 (depends on 11) The method of claim 11, wherein the response message comprises the first RDS port number. ### Claim 15 (depends on 14) The method of claim 14, wherein the second entity comprises a Service Capability Server/Application Server (SCS/AS) or an Application Function (AF), and the response message comprises at least one of: a mobile terminated (MT) NIDD submit Response message; a Group MT NIDD submit Response message; a NIDD Authorization Notification Request message; or a mobile originated (MO) NIDD Indication message. ### Claim 16 (depends on 14) The method of claim 14, further comprising: after receiving the response message, transmitting, to the first entity, an updated configured RDS port list or an updated NIDD message. ### Claim 17 (depends on 11) The method of claim 11, wherein the first entity determines whether the first RDS port number is included in the configured RDS port list, if an RDS port verification feature is supported. ### Claim 18 (depends on 11) The method of claim 11, wherein the first entity comprises a Service Capability Exposure Function (SCEF) or a Network Exposure Function (NEF), and the second entity comprises a terminal device. ### Claim 19 An apparatus, comprising: a receiver for receiving messages; a processor; and a memory, containing instructions executable by the processor, wherein the apparatus is configured to perform a method comprising: after receiving a non-internet protocol data delivery (NIDD) message comprising a first Reliable Data Service (RDS) port number, determining whether the first RDS port number included in the NIDD message is within a configured RDS port list; and as a result of determining that the first RDS port number is not within the configured RDS port list, transmitting a response message, responsive to the NIDD message, indicating that at least one RDS port number included in the NIDD message is unknown in the first entity. ### Claim 20 (depends on 19) The apparatus of claim 19, wherein the response message comprises a ProblemDetails data structure comprising a cause attribute having a value, and the value of the cause attribute is set to RDS PORT UNKNOWN, thereby indicating that at least one RDS port number included in the NIDD message is unknown in the first entity. ### Claim 21 (depends on 19) The apparatus of claim 19, wherein the response message comprises an NIDD status set to RDS_PORT_UNKNOWN and the first RDS port number. ### Claim 22 An apparatus, comprising: a processor; and a memory, containing instructions executable by the processor, wherein the apparatus is configured to perform a method comprising: transmitting, to a first entity, a non-internet protocol data delivery (NIDD) message comprising a first Reliable Data Service (RDS) port number; and after transmitting the NIDD message to the first entity, receiving from the first entity a response message indicating that an RDS port number included in the NIDD message is not included in a configured RDS port list. ### Claim 23 (depends on 22) The apparatus according to claim 22, wherein the response message comprises the first RDS port number.