test.csv

Text
"1. SIP is a protocol that supports multimedia communication sessions, allowing users to establish and terminate sessions and manage session parameters. 2. SIP can be used with other protocols like RTP, RTSP, MEGACO, and SDP to build a complete multimedia architecture. 3. SIP does not provide services itself but provides primitives that can be used to implement different services. 4. SIP does not offer conference control services but can be used to initiate a session that uses another conference control protocol. 5. SIP does not provide network resource reservation capabilities. 6. Security is important in SIP, and it provides services like denial-of-service prevention, authentication, integrity protection, encryption, and privacy. 7. SIP works with both IPv4 and IPv6. 8. SIP uses a request/response transaction model, where a request invokes a method on the server and receives one or more responses. 9. SIP messages contain header fields that provide additional information about the message, such as the source and destination addresses. 10. SIP uses proxy servers to facilitate session establishment and routing of requests and responses. 1. The Multimedia-Auth-Request (MAR) command is used by a client to request security information from a server. 2. The Multimedia-Auth-Answer (MAA) command is the server's response to the MAR command. 3. The Registration-Termination-Request (RTR) command is used by a server to request the de-registration of a user. 4. The Registration-Termination-Answer (RTA) command is the client's response to the RTR command. 5. The Push-Profile-Request (PPR) command is used by a server to update subscription data and authentication information for a user. 6. The Push-Profile-Answer (PPA) command is the client's response to the PPR command. 7. There are various result codes that can be included in the response messages to indicate the success or failure of a request. 8. The AVPs (Attribute Value Pairs) defined for the Diameter Multimedia Application include information such as network identifiers, public identities, server names, user data, and supported features. 9. The AVPs may have different flag rules indicating whether they are mandatory, optional, or vendor-specific. 10. The AVPs may or may not be encrypted depending on their specific requirements. - The ACK is sent directly from Alice's softphone to Bob's SIP phone, bypassing the proxies. - The endpoints learn each other's address from the Contact header fields through the INVITE/200 (OK) exchange. - The proxies drop out of the call flow once the endpoints have learned each other's address. - The media packets take a different path from the SIP signaling messages during a session. - Either Alice or Bob can change the characteristics of the media session by sending a re-INVITE. - The other party sends a 200 (OK) to accept the change, or an error response if they don't accept it. - The failure of the re-INVITE does not cause the existing call to fail. - Bob disconnects first and generates a BYE message, which is routed directly to Alice's softphone. - Alice confirms receipt of the BYE with a 200 (OK) response, terminating the session. - Registration is used to learn the current location of a SIP user and is done through REGISTER messages. 1. The HSS returns the stored S-CSCF name if the user is registered, without any S-CSCF capabilities. 2. If the User-Authorization-Type is DE-REGISTRATION, the HSS returns the stored S-CSCF name and sets the Result-Code to DIAMETER_SUCCESS. 3. If the User-Authorization-Type is REGISTRATION or absent, the HSS returns the stored S-CSCF name and sets the Experimental-Result-Code to DIAMETER_SUBSEQUENT_REGISTRATION. 4. If the user is not registered yet, the HSS checks the User-Authorization-Type: a. If it is DE_REGISTRATION and the Authentication pending flag is set, the HSS returns the stored S-CSCF name and sets the Experimental-Result-Code to DIAMETER_SUCCESS. b. If the Authentication pending flag is not set, the HSS does not return any S-CSCF name or capabilities and sets the Experimental-Result-Code to DIAMETER_ERROR_IDENTITY_NOT_REGISTERED. 5. If there is at least one registered Public User Identity, the HSS returns the assigned S-CSCF name and sets the Experimental-Result-Code to DIAMETER_SUBSEQUENT_REGISTRATION. 6. If there is at least one unregistered Public User Identity, the HSS returns the stored S-CSCF name and sets the Experimental-Result-Code to DIAMETER_SUBSEQUENT_REGISTRATION. 7. If there is no registered or unregistered identity, the HSS checks if there is a stored S-CSCF name for the user. If yes, the HSS returns the stored S-CSCF name and sets the Experimental-Result-Code to DIAMETER_SUBSEQUENT_REGISTRATION. 8. If there are no assigned S-CSCF names for any Public User Identity, the HSS may return the Server-Capabilities AVP to enable the I-CSCF to select an S-CSCF. The Experimental-Result-Code is set to DIAMETER_FIRST_REGISTRATION. 9. If the HSS cannot fulfill the request due to a database error, the Result-Code is set to DIAMETER_UNABLE_TO_COMPLY without returning any S-CSCF name or capabilities. 10. The S-CSCF registration/deregistration notification procedure is used to assign an S-CSCF to a Public Identity, download user information, backup S-CSCF Restoration Information, and trigger P-CSCF Restoration mechanism. 1. The SIP protocol uses a series of messages to establish and manage communication sessions. 2. SIP messages contain various headers, such as Via, To, From, Call-ID, and Contact, which provide information about the session participants. 3. The 180 Ringing response indicates that the call is being processed and the recipient's phone is ringing. 4. The 200 OK response indicates that the call has been successfully established. 5. SIP messages can be folded onto multiple lines if the continuation line begins with a space or horizontal tab. 6. Quoted strings are used to represent a string of text, and special characters within the string need to be escaped. 7. SIP URIs can be either SIP-URI or SIPS-URI, and they consist of a scheme, userinfo, hostport, and optional URI parameters and headers. 8. SIP messages can include comments surrounded by parentheses, but comments are only allowed in specific fields. 9. The SIP protocol allows for the use of various transport protocols, such as UDP, TCP, SCTP, and TLS. 10. The SIP protocol supports both IPv4 and IPv6 addresses for identifying hosts. 1. Invalid transit network selection is an error that occurs when the chosen transit network is not valid. 2. Mandatory information element is missing refers to a situation where a required element is not included. 3. Message type non-existent or not implemented indicates that the specified message type does not exist or is not supported. 4. Invalid information element contents means that the content of a specific element is not valid. 5. Message not compatible with call state or message type non-existent or not implemented suggests that the message is not compatible with the current call state or the specified message type is not supported. 6. Information element/parameter non-existent or not implemented refers to a missing or unsupported information element or parameter. 7. Recovery on timer expiry signifies that a recovery action is triggered when a timer expires. 8. Protocol error, unspecified indicates a general error in the protocol without specifying the exact nature of the error. 9. Interworking, unspecified refers to an unspecified issue with interworking between different systems. 10. NO CC Cause CAP - Destination Routing Address represents the destination routing address in a CAP (CAMEL Application Part) network. 1. In interleaving, the frame-blocks in the table of contents will not be placed consecutively in time. 2. The payload header and table of contents are packed into the payload in the same way for both normal order and robust sorting order. 3. The speech frames in the payload are arranged either one whole frame after another or with the octets of all frames interleaved together at the octet level. 4. The last octet of each speech frame must be padded with zero bits if all bits in the octet are not used. 5. The use of robust sorting order for a payload type must be agreed upon through out-of-band means. 6. The frame CRC, when used, is calculated only over the class A bits in the AMR or AMR-WB frame. 7. The transport layer checksum should be used to protect the IP, transport protocol, and RTP headers, as well as the payload header and table of contents. 8. The receiver should re-calculate the CRC over the received class A bits and compare it to the value in the received payload header to check data integrity. 9. If the CRC values mismatch, the receiver should consider the class A bits in the receiver frame damaged and set the Q flag to 0. 10. The UED and/or UEP mechanisms should cover at least the RTP header, payload header, table of contents, and class A bits of a sorted payload. 1. The VLR sends a MAP_READY_FOR_SM request to the HLR if it successfully handles certain indications and the MS Not Reachable Flag is set. 2. If authentication fails during handling of certain indications, the VLR does not send a MAP_READY_FOR_SM request to the HLR. 3. The SGSN sends a MAP_READY_FOR_SM request to the HLR if it successfully handles certain messages and the MS Not Reachable for GPRS flag is set. 4. If authentication fails during handling of certain messages, the SGSN does not send a MAP_READY_FOR_SM request to the HLR. 5. The HLR starts a process when it receives a dialogue opening request using the application context mwdMngtContext. 6. The SMS Interworking MSC starts a process when it receives a dialogue opening request using the application context shortMsgAlertContext. 7. The SM delivery status report procedure is used to set the Service Centre address in the HLR after a failed short message delivery. 8. The SMS-GMSC invokes the short message delivery status report procedure based on certain conditions. 9. The HLR handles a MAP_REPORT_SM_DELIVERY_STATUS indication and ignores the information if it is not received from an IP-SM-GW. 10. The mobile terminated short message transfer procedure for VGCS is used to forward a short message from a Service Centre to the group call anchor MSC. 1. If the VLR or SGSN does not support a service, the CSS operator can use the macro Wait_for_Insert_VCSG_Subs_Data_Cnf to replace the service. 2. If the CSS operator does not consider the unsupported service essential, the CSS sends data for a replacement service in a subsequent MAP_INSERT_SUBSCRIBER_DATA request. 3. The decision to repeat the download of CSG subscriber data after an error response from the VLR or SGSN is an operator option. 4. The number of repeat attempts and the interval between them is also an operator option. 5. The macro Wait_for_Insert_VCSG_Subs_Data_Cnf is used for handling the transfer of CSG subscriber data in the CSS. 6. The process Send_Insert_VCSG_Subs_Data_CSS is used for sending a MAP_INSERT_SUBSCRIBER_DATA request to the VLR or SGSN. 7. The macro Obtain_IMSI_MSC describes the handling of a request from the VLR to provide the IMSI of a subscriber. 8. The macro Obtain_IMSI_VLR describes how the VLR requests the IMSI of a subscriber from the MSC. 9. Tracing macros are used to activate tracing for subscriber activity in the MSC, VLR, and SGSN. 10. The process Subscriber_Present_VLR is invoked when a mobile subscriber becomes active in the VLR. 1. When an Update Location Request is received over the S6d interface, the HSS will clear the URRP-SGSN parameter and notify the Service Related Entities. 2. The HSS will include the subscription data in the ULA command unless explicitly instructed to skip it, and return a Result Code of DIAMETER_SUCCESS. 3. The default APN Configuration in the ULA command will not contain the Wildcard APN and will always have an explicit APN. 4. The GPRS Subscription data will only be present in the ULA command if indicated by the serving node or if there is no APN configuration profile stored for the subscriber. 5. The HSS will store new terminal information and/or UE SRVCC capability if present in the request. 6. If the MME/SGSN supports the Additional-MSISDN feature, the HSS will send the provisioned additional MSISDN along with the MSISDN. 7. LCS-Info, Teleservice-List, and Call-Barring-Info data will be included based on the supported features indicated by the serving node. 8. If the HSS supports ""SMS in MME"" feature and receives the indication that the MME supports it, it will register the MME for SMS and download available SMS related subscription data. 9. If the HSS supports ""SMS in SGSN"" feature and receives the indication that the SGSN supports it, it will indicate in the ULA that ""SMS in SGSN"" is allowed and handle MT SMS accordingly. 10. The HSS may send an Alert-Service-Centre message if the user is considered not reachable and the UE has available memory. 1. The parameter indicates the supplementary service data to be modified by CSE. 2. Call Barring Data contains the call barring feature list and Notification to CSE flag. 3. Call Forwarding Data contains the call forwarding feature list and Notification to CSE flag. 4. ODB Data contains general data and HPLMN specific data for ODB. 5. Requested Subscription Info indicates the subscription information being requested. 6. CS Allocation/Retention priority indicates the priority for Circuit Switched (CS) allocation/retention. 7. ODB Info contains ODB data and Notification to CSE flag. 8. Suppress VT-CSI is used to suppress terminating CAMEL services at the VMSC. 9. Suppress Incoming Call Barring is used to suppress incoming call barrings. 10. gsmSCF Initiated Call is used to indicate that the call was initiated by the gsmSCF. 1. For communication within the same PLMN, a MAP SSN must be included in the called and calling party addresses. 2. SCCP addressing for inter-PLMN communication is network-specific. 3. The called party address for inter-PLMN communication includes SSN indicator, global title indicator, translation type, and routing indicator. 4. The calling party address for inter-PLMN communication includes SSN indicator, point code indicator, global title indicator, translation type, and routing indicator. 5. E.212 numbering plan should not be included as a global title in an SCCP UNITDATA message when using CCITT or ITU-T SCCP. 6. E.214 and E.164 numbering plans are allowed as global titles in SCCP addressing. 7. The MSC can be addressed in various cases, such as handover, short message routing, location request routing, and LMU control. 8. The HLR is addressed during call set-up, location updating, restoration, and network-requested PDP context activation. 9. The VLR is addressed for inter-VLR information retrieval and HLR requests. 10. The GMLC addresses the HLR for a location request using the MS's international E.164 MSISDN, E.214 number, or E.212 number. - The Require header field is used to indicate the options that the client expects the server to support. - The Retry-After header field is used to indicate how long a service is expected to be unavailable or when the called party will be available again. - The Route header field is used to force routing for a request through a specific set of proxies. - The Server header field contains information about the software used by the server to handle the request. - The Subject header field provides a summary or indicates the nature of the call. - The Supported header field lists the extensions supported by the client or server. - The Timestamp header field describes when the request was sent. - The To header field specifies the logical recipient of the request. - The Unsupported header field lists the features not supported by the server. - The User-Agent header field contains information about the client originating the request. 1. The document provides information on various processes and macros related to the handling of subscriber data in a telecommunications network. 2. The IMSI (International Mobile Subscriber Identity) of a subscriber can be obtained by the VLR (Visitor Location Register) or the MSC (Mobile Switching Center) during location updating. 3. Tracing macros are used to activate tracing for a subscriber's activity in the MSC, VLR, or SGSN (Serving GPRS Support Node) if necessary. 4. Short message alert procedures involve processes invoked by the VLR, SGSN, and HLR (Home Location Register) to handle the activation and alerting of service centers. 5. The document provides information on various segmentation mechanisms used to overcome the limitation of message size in the MAP (Mobile Application Part) protocol. 6. SCCP (Signalling Connection Control Part) segmentation, TCAP (Transaction Capabilities Application Part) segmentation, and MAP segmentation are the available mechanisms for message segmentation. 7. The use of SCCP segmentation is recommended for messages that do not cross PLMN (Public Land Mobile Network) boundaries or have low priority. 8. TCAP segmentation includes mechanisms like empty Begin, empty Continue, and TC-Result-NL (Not Last) to segment messages at the TCAP level. 9. MAP segmentation involves segmenting Invoke and Result components into multiple segments, either with or without explicit indication. 10. The document also includes information on the change history of the document, including revisions and corrections made over time. 1. The criteria for handover across service area or location area boundaries are indicated by specific Information Elements (IEs). 2. Inter-system handover, inter-PLMN handover, and inter-MSC handover are all possible for mobile stations. 3. The Reset Timer IF is used to reset a timer, with the Timer Value and Timer ID specified in the IEs. 4. The Send Charging Information IF is used to send charging information from the gsmSCF to the gsmSSF, with the SCI Billing Charging Characteristics and Leg ID specified in the IEs. 5. The Split Leg IF is used to separate a leg from CSID1 and move it to a new call segment, with the Leg To Be Split and New Call Segment specified in the IEs. 6. The Activity Test IF is used to check the continued existence of a relationship between the gsmSCF and gsmSRF or assistSSF. 7. The Cancel IF is used to request the cancellation of a correlated previous IF, with the Invoke ID and Call Segment To Cancel specified in the IEs. 8. The Play Announcement IF is used for inband interaction, with the Information To Send and Disconnect From IP Forbidden specified in the IEs. 9. The Prompt And Collect User Information IF is used to collect information from a call party, with the Collected Info and Information To Send specified in the IEs. 10. The Specialized Resource Report IF is used to indicate the completion or start of announcements or tones, with the All Announcements Complete and First Announcement Started specified in the IEs. 1. The MAP-ACTIVATE-TRACE-MODE service is used to activate subscriber tracing in the VLR or SGSN. 2. The MAP-DEACTIVATE-TRACE-MODE service is used to deactivate subscriber tracing in the VLR or SGSN. 3. The Any_Time_Subscription_Interrogation service is used to request subscription information from the HLR. 4. The Any_Time_Modification service is used to modify information in the HLR. 5. The Note_Subscriber_Data_Modified service is used by the HLR to inform the gsmSCF that subscriber data have been modified. 6. The gsmSCF-Address parameter indicates the address of the interrogating gsmSCF. 7. The IMSI parameter contains the International Mobile Subscriber Identity. 8. The MSISDN parameter contains the Mobile Station International Subscriber Directory Number. 9. The User error parameter is sent by the responder when an error is detected. 10. The Provider error parameter is defined in clause 7.6.1. 1. The document specifies the IP Multimedia (IM) Subsystem Sh interface and its signaling flows and message contents. 2. It also defines the network domain security for IP networks and the Stream Control Transmission Protocol. 3. The document refers to various RFCs and 3GPP specifications for definitions, abbreviations, and command codes. 4. The Sh interface is a Diameter application with the vendor identifier assigned to 3GPP. 5. The document defines command codes for the Sh interface application, including User-Data-Request, User-Data-Answer, Profile-Update-Request, Profile-Update-Answer, Subscribe-Notifications-Request, Subscribe-Notifications-Answer, Push-Notification-Request, and Push-Notification-Answer. 6. The User-Data-Request command is used to request user data from a Diameter server. 7. The User-Data-Answer command is the response to the User-Data-Request command and may contain a Result-Code or Experimental-Result AVP. 8. The Profile-Update-Request command is used to update user data in the server. 9. The Profile-Update-Answer command is the response to the Profile-Update-Request command and may contain a Result-Code or Experimental-Result AVP. 10. The document also defines result code values for success, permanent failures, and transient failures. 1. TIF-CSI is a flag in subscriber data that prevents certain checks when a forwarded number is registered. 2. TO-CSI identifies services offered by the operator to incoming calls on a specific trunk. 3. U-CSI and UG-CSI identify mappings from a USSD service code to a gsmSCF address. 4. VT-CSI identifies subscribers with terminating CAMEL services in the VMSC. 5. DPs are points in a call where certain events are detected by the gsmSCF. 6. DPs can be statically or dynamically armed, and can be disarmed under certain conditions. 7. Criteria at DP-Collected_Info include destination number, basic service, and forwarding triggering criteria. 8. Criteria at DP-Analysed_Information are checked in the originating or forwarding MSC. 9. The HLR stores relevant CAMEL subscriber data and sends it to the visited PLMN. 10. The GMSC, MSC, VLR, gsmSSF, gsmSCF, and gsmSRF are functional entities involved in CAMEL support. 1. The application context is used for reporting authentication failures between VLR and HLR or SGSN and HLR. 2. It is also used for resource management between GMSC and VMSC. 3. Another application context is used for mobile terminating short message relay procedures for VGCS between SMS-GMSC and MSC. 4. The vcsg location updating and cancellation procedures use a specific application context between CSS and VLR or SGSN. 5. The ASN.1 module defines the application context names assigned to MAP application-contexts. 6. The MAP-DialogueInformation module defines the abstract syntax for MAP dialogue information. 7. The MAP-DialoguePDU includes different choices for MAP operations such as open, accept, close, refuse, user abort, and provider abort. 8. The Reason field in MAP-RefuseInfo indicates the reason for refusal, such as invalid destination or originating reference. 9. The MAP-UserAbortInfo and MAP-ProviderAbortInfo provide information about user or provider-initiated aborts. 10. The MAP-Protocol module imports operation codes for various MAP operations related to mobile service, operation and maintenance, call handling, and supplementary services. 1. The document describes various operations and errors in the MAP protocol for mobile service, operation and maintenance, and call handling. 2. The operations include location registration, subscriber information enquiry, handover, authentication management, IMEI management, and more. 3. Each operation has specific arguments, results, and possible error codes associated with it. 4. The document defines timers for each operation, indicating the time limits for their execution. 5. The errors include system failure, data missing, unexpected data value, unknown subscriber, roaming not allowed, and more. 6. The document also mentions reserved error codes for previous versions of the protocol. 7. The MAP protocol supports operations related to mobile service, operation and maintenance, and call handling. 8. The operations involve exchanging information between different network elements. 9. The document provides a comprehensive list of operations and their associated error codes. 10. The MAP protocol is used in GSM networks for efficient communication and management of mobile services. 1. The CAMEL Phase 2 parameter can contain O-CSI, SS-CSI, and TIF-CSI. 2. TDP-Criteria for O-CSI can be associated with O-CSI in CAMEL Phase 2 and onwards. 3. In CAMEL Phase 3, the parameter can contain O-CSI, D-CSI, SS-CSI, VT-CSI, MO-SMS-CSI, M-CSI, and TIF-CSI. 4. TDP-Criteria for VT-CSI can be associated with VT-CSI in CAMEL Phase 3 and onwards. 5. The VLR CAMEL Subscription Info is sent during location updating or when there are changes in the HLR's CAMEL Subscription Info. 6. In CAMEL Phase 1 and 2, the complete set of VLR CAMEL Subscription Info is sent in one dialogue. 7. In CAMEL Phase 3 or higher, specific elements of VLR CAMEL Subscription Info are sent in one dialogue. 8. The VLR CAMEL Subscription Info includes O-CSI, TDP-Criteria for O-CSI, SS-CSI, and TIF-CSI in CAMEL Phase 1 and 2. 9. From CAMEL Phase 3 onwards, the VLR CAMEL Subscription Info may include additional elements like D-CSI, VT-CSI, MO-SMS-CSI, MT-SMS-CSI, and M-CSI. 10. The GPRS Subscription Data parameter contains a list of PDP-contexts a user has subscribed to and is sent during GPRS location updating or when there are changes in the subscriber's GPRS data. 1. SIP is an application-layer control protocol used for creating, modifying, and terminating sessions with multiple participants. 2. SIP allows participants to agree on compatible media types through session descriptions. 3. Proxy servers are used in SIP to route requests, authenticate and authorize users, implement call-routing policies, and provide features. 4. SIP provides a registration function for users to upload their current locations for use by proxy servers. 5. SIP runs on top of different transport protocols. 6. SIP messages include requests and responses, with header fields and bodies. 7. User agents in SIP can act as clients or servers, generating requests and processing responses. 8. Canceling a request in SIP involves specific behavior from both the client and server. 9. SIP supports registrations, allowing users to add, remove, fetch, and refresh bindings. 10. SIP allows for querying capabilities through OPTIONS requests. 1. UG CSI is a global mapping from a USSD service code to a gsmSCF address, applicable to all HPLMN subscribers. 2. If both U CSI and UG CSI are applicable for a service code, U CSI takes precedence. 3. VT CSI identifies subscribers with terminating CAMEL services in the VMSC. 4. DPs are points in a call where certain events are detected by the gsmSCF. 5. DPs can be statically armed or dynamically armed, and can be disarmed based on certain conditions. 6. Criteria at DPÊCollected_Info include destination number triggering, basic service triggering, and forwarding triggering. 7. Criteria at DPÊAnalysed_Information are checked in the originating or forwarding MSC and include specific conditions for call handling. 8. The HLR stores relevant information for CAMEL subscriptions, such as O CSI, D CSI, T CSI, VT CSI, and TIF CSI. 9. The GMSC receives O/D/T CSI from the HLR and requests instructions from the gsmSSF for CAMEL support. 10. The gsmSCF controls the call in the gsmSSF and can establish a connection with a gsmSRF. 1. The SIP protocol uses a series of messages to establish and manage communication sessions between users. 2. SIP messages contain various headers that provide information about the sender, recipient, and the type of communication. 3. SIP messages can be sent between different proxies and servers to route the communication. 4. The ""INVITE"" message is used to initiate a session, and the ""ACK"" message is used to acknowledge the session establishment. 5. The ""BYE"" message is used to terminate a session, and the ""200 OK"" response confirms the termination. 6. SIP URIs are used to identify users and their locations in the network. 7. SIP URIs can include parameters such as transport, user type, method, time-to-live, and more. 8. SIP messages can include headers such as Accept, Content-Type, From, To, Call-ID, CSeq, and more to provide additional information about the communication. 9. SIP messages can be folded onto multiple lines if necessary, and whitespace can be replaced with a single space. 10. Quoted strings and comments can be used within SIP headers to provide additional information or clarify certain values. 1. If a terminal has no preference in receiving mode, it should set CMR=15 in all outbound payloads. 2. If a payload has a CMR value that is not a speech mode or NO_DATA, the receiver should ignore the CMR value. 3. In a multi-channel session, the codec mode request should be interpreted as the desired encoding mode for all channels. 4. An IP end-point should not set the codec mode request based on congestion indications, as congestion is managed by the IP sender. 5. Feedback about congestion should be provided to the IP sender through RTCP or other means. 6. The encoder should follow a received codec mode request, but may change to a lower-numbered mode for congestion control. 7. The CMR field must be set to 15 for packets sent to a multicast group. 8. The encoder should ignore codec mode requests when sending speech to a multicast session, but may use RTCP feedback as a hint for mode change. 9. The requested mode must be among the signalled subset if mode selection is restricted by a session parameter. 10. If the received CMR value is outside the signalled subset, it must be ignored. 1. The text provides a list of opcode descriptions for various protocols such as TCAPOP, INAPCS2, NOKIA_INAP, SINAP, and BELL TCAP. 2. The opcodes represent different operations or actions that can be performed within these protocols. 3. Some examples of opcodes include establishing temporary connections, connecting to resources, disconnecting calls, providing and setting values, and analyzing information. 4. The opcodes also cover activities like playing announcements, collecting user information, managing call segments, and sending charging information. 5. The text mentions specific error codes and their descriptions for different layers and protocols. 6. It also includes information about line service types, service or equipment indicators, termination indicators, and AIN error causes. 7. The opcode descriptions provide insights into the functionality and capabilities of the protocols. 8. The opcodes can be used to understand and troubleshoot issues related to call handling, resource management, and network operations. 9. The text highlights the importance of opcode selection and usage in different scenarios and contexts. 10. Understanding the opcodes can help in designing, implementing, and maintaining efficient and reliable communication systems. 1. Implementations must accept both the long and short forms of each header name. 2. Requests may contain message bodies unless otherwise noted, and the interpretation of the body depends on the request method. 3. The Internet media type of the message body must be given by the Content-Type header field. 4. The Content-Encoding header field must indicate if the body has undergone any encoding such as compression. 5. The character set of the message body is indicated as part of the Content-Type header field value. 6. SIP messages may contain binary bodies or body parts. 7. The body length in bytes is provided by the Content-Length header field. 8. SIP implementations can use UDP or other unreliable datagram protocols, and each datagram carries one request or response. 9. The Content-Length header field value is used to locate the end of each SIP message in a stream. 10. A user agent represents an end system and contains a user agent client (UAC) and a user agent server (UAS). 1. The DRMP AVP is used to indicate the priority of Diameter messages and set the DSCP marking for their transport. 2. The Load AVP is used to support Diameter load control mechanism. 3. This specification assigns AVP values from the AVP Code namespace managed by 3GPP for its Diameter vendor-specific applications. 4. This specification has assigned Experimental-Result-Code AVP values for specific purposes. 5. This specification assigns Command Code values from the range allocated by IANA to 3GPP. 6. IANA has allocated the value 16777217 for the 3GPP Sh interface application. 7. The Sh interface supports various features, including Notif-Eff, Update-Eff, and Additional-MSISDN. 8. The Sh interface uses specific application identifiers, such as 16777217 for 3GPP Rel-5. 9. The Sh interface has undergone several changes and corrections over different versions. 10. The Sh interface supports features like EPS Subscriber State and Location Information Request, Enhanced SRVCC, and Load Control. 1. The operation packages described in clause 17.2.2 include various procedures between different network elements. 2. These operation packages define the operations required for specific procedures, such as location cancellation, roaming number enquiry, information retrieval, and more. 3. The v1-equivalent and v2-equivalent packages can be determined based on certain rules. 4. Some operation packages are applicable only to specific interfaces or versions. 5. The operation packages cover procedures between HLR and VLR, HLR and SGSN, VLR and HLR, VLR and gsmSCF, and more. 6. The packages include operations for call control transfer, interrogation, handover control, subscriber data management, equipment management, and more. 7. Some packages are specific to certain services like short message relay, alerting, data restoration, and group call control. 8. The packages also cover procedures related to GPRS, such as location updating, interrogation, failure reporting, and notifying. 9. The v1-equivalent package is defined differently from the v2-equivalent and v3-equivalent packages. 10. The packages define the operations that the consumer and supplier network elements should invoke for each procedure. 1. The MonitoringMode ENUMERATED type has two values: a-side and b-side. 2. The CallOutcome ENUMERATED type has three values: success, failure, and busy. 3. The RUF-Outcome ENUMERATED type has six values: accepted, rejected, noResponseFromFreeMS, noResponseFromBusyMS, udubFromFreeMS, and udubFromBusyMS. 4. The IST-AlertArg and IST-AlertRes types are used for IST (Integrated Services Digital Network) alerting. 5. The IST-CommandArg and IST-CommandRes types are used for IST commands. 6. The CallTerminationIndicator ENUMERATED type has two values: terminateCallActivityReferred and terminateAllCallActivities. 7. The ReleaseResourcesArg and ReleaseResourcesRes types are used for releasing resources. 8. The RegisterSS-Arg type is used for registering supplementary services. 9. The SS-Info type is a choice between forwardingInfo, callBarringInfo, and ss-Data. 10. The USSD-Arg and USSD-Res types are used for USSD (Unstructured Supplementary Service Data) operations. 1. The present document describes the requirements for the signalling system and the procedures needed at the application level in order to fulfill these signalling needs. 2. MAP consists of a set of MAP services that are provided to MAP service-users by a MAP service-provider. 3. The present document specifies functions, procedures, and information which apply to GERAN Iu mode. 4. The functionality related to GERAN Iu mode is neither maintained nor enhanced. 5. The Signalling System No. 7 specified by CCITT is used to transfer information specific to the PLMN. 6. The present document specifies the MAP protocol specification and the behavior of service providers. 7. The MAP user procedures make use of MAP services. 8. The present document references other 3GPP documents that contain provisions related to the present document. 9. The present document uses modal verbs to indicate requirements, recommendations, permissions, and possibilities. 10. The present document also includes informative annexes and a change history. 1. The list includes various opcode descriptions for different protocols such as EINAPV21, INAPCS1P, ETSI_INAP, ETSI_CAP, ETSI_MAP, and BEL IS41D. 2. These opcodes represent different actions or instructions within each protocol. 3. Some common opcodes include InitialDP, Retrieve/Assist Request Instructions, Establish Temporary Connection, Disconnect Forward Connection, Connect To Resource, Update, Release Call, Request Report BCSM Event, Event Report BCSM, and Request Notification Charging Event. 4. The opcodes also cover actions like Apply Charging, Play Announcement, Prompt And Collect User Information, Specialised Resource Report, Cancel, Activity Test, and Signalling Information. 5. The ETSI_MAP protocol includes opcodes related to location updates, roaming numbers, subscriber data, service activation/deactivation, and authentication. 6. The BEL IS41D protocol opcodes cover actions like handoff, facilities directive, qualification request, blocking/unblocking, registration/notification, location/routing request, and authentication. 7. The TCAPOP protocol opcodes are related to call queue management, call retrieval, and voice message retrieval. 8. Each opcode has a unique identifier in hexadecimal format. 9. The opcodes are used to communicate specific instructions or actions between different systems or components. 10. Understanding the meaning and purpose of each opcode is essential for proper protocol implementation and communication. 1. The gsmSSF will send the Entity Released IF to the gsmSCF when appropriate. 2. The gsmSCF may send the Disconnect Forward Connection With Argument IF to the gsmSSF. 3. The gsmSCF may send the Play Tone IF to the gsmSSF. 4. The gsmSCF may instruct the gsmSSF to arm the O_MidCall or T_MidCall DP. 5. The Charge Indicator IE may be present in the Event Report BCSM IF reporting the O_Answer or T_Answer DP. 6. The gsmSCF may instruct the gsmSSF to arm the O_Term_Seized or Call_Accepted DP. 7. The Location Information IE shall be present in the Event Report BCSM IF reporting the O_Term_Seized or Call_Accepted DP. 8. The gsmSCF may instruct the gsmSSF to arm the O_Change_Of_Position or T_Change_Of_Position DPs. 9. The gsmSCF may send the Basic OR Interrogation Requested IE to the gsmSSF in the Connect or Continue With Argument IF. 10. The gsmSCF may send the Burstlist IE in an Apply Charging IF to enhance warning tones. 1. The MaxNumOfAllowedSimultRegistrations parameter specifies the maximum number of simultaneous registrations allowed. 2. The Identity tag can be a Wildcarded Identity, which has a specific syntax described in 3GPP TSÊ23.003Ê[17]. 3. The IMPU (Public User Identity) may not be explicitly provisioned in the HSS, in which case a Wildcarded IMPU is included in the tPublicIdentityExtension3. 4. The Cx interface user profile includes complex data types such as IMSSubscription, ServiceProfile, and InitialFilterCriteria. 5. The Cx interface user profile also includes extensions for additional information and functionality. 6. The PublicIdentity tag in the ServiceProfile contains information about the user's public identity, including BarringIndication and Identity. 7. The InitialFilterCriteria tag in the ServiceProfile includes information about priority, trigger points, and application servers. 8. The ApplicationServer tag in the InitialFilterCriteria specifies the server name and default handling for the application. 9. The IncludeRegisterRequest and IncludeRegisterResponse tags in the ApplicationServerExtension are optional and can be used to include additional information in the register request and response. 10. The PublicIdentityExtension tag includes additional extensions for the public identity, such as DisplayName, AliasIdentityGroupID, and ServiceLevelTraceInfo. 1. The specification assigns values 300-305 from the range allocated by IANA to 3GPP in IETF RFC 3589. 2."
"The application ID value allocated by IANA for the 3GPP Cx interface application is 16777216. 3. New functionality beyond the Rel-5 standard should be introduced as optional if possible. 4. Backwards incompatible changes should be avoided, but if necessary, new functionality should be introduced as a feature. 5. If a change is still backwards incompatible even as a feature, a new version of the interface should be created by changing the application identifier. 6. Features should have a significant meaning to the operation of the Diameter application and should be defined independently from each other. 7. The support for a feature may be defined as mandatory behavior of a node. 8. The network operator is responsible for keeping the local databases in the S-CSCFs and HSSs consistent when using the shared iFC sets feature. 9. Different aliases groups may be sent within the same service profile if the HSS and S-CSCF support the Alias Indication feature. 10. The IMS Restoration Indication feature allows for the assignment of a new S-CSCF if the current one cannot be contacted. 1. The terminating half BCSM indicates if the call is accepted and answered by the terminating party. 2. If a route select failure occurs, it leads to the Route_Select_Failure DP. 3. A busy indication or not reachable indication from the terminating party leads to the O_Busy DP. 4. If there is no reply from the terminating party, it leads to the O_No_Answer DP. 5. If the calling party abandons the call, it leads to the O_Abandon DP. 6. An exception condition encountered leads to the O_Exception PIC. 7. When the call is active, a connection is established between the originating and terminating parties. 8. Notifications are sent to the gsmSCF if there are changes in position or bearer service. 9. Call release is awaited in the O_Active Entry. 10. If an exception condition is encountered, the gsmSSF sends an error information flow and releases resources. 1. Access Restriction Data has undergone multiple updates and corrections. 2. V2X Subscription Data has been added to the S6a Interface. 3. The IETF drmp draft version has been changed to official RFC 7944. 4. Monitoring events have been deleted. 5. Maximum Response Time has been modified. 6. Enhanced Coverage and Inter-RAT PDN-Continuity have been introduced. 7. Emergency-Info AVP in ULA has been included. 8. Clarifications have been made regarding UE-PC5-AMBR Format and MDT User Consent. 9. Subscription parameters for eDRX and long/short Macro eNodeB IDs have been added. 10. Various updates and corrections have been made to different AVPs and protocols. 1. In the bandwidth-efficient mode, the table of contents (ToC) lists the speech frames in the payload. 2. Each ToC entry includes information about the frame type and whether it is the last frame in the payload. 3. Frames with FT values in the range 9-14 for AMR or 10-13 for AMR-WB should be discarded to avoid data synchronization issues. 4. NO_DATA frames should not be transmitted in any payload format configuration, except in the case of interleaving. 5. The frame quality indicator in the ToC helps with error concealment and improves speech quality. 6. In multi-channel sessions, the ToC entries are placed in consecutive order for each frame-block. 7. The speech data in the payload contains speech frames or comfort noise frames. 8. Each speech frame represents 20 ms of speech encoded with the mode indicated in the FT field of the ToC entry. 9. The payload is formed by packing bits from the payload header, ToC, and speech frames, with padding bits for octet alignment. 10. Padding bits should be set to zero and ignored on reception. 1. The Call Reference Number is allocated by the GMSC and is present in both first and second interrogations. 2. The GMSC Address is the E.164 address of the GMSC. 3. The Call Diversion Treatment Indicator indicates whether the call can be forwarded using supplementary services. 4. Offered CAMEL4 CSIs include O-CSI, D-CSI, and T-CSI. 5. Resume Call Handling is used to request the GMSC to take over handling the call for forwarding. 6. Send Info For ICA is used to request the VLR to provide information for an outgoing call leg. 7. Send Info For Incoming Call is used to request the VLR to provide information for an incoming call. 8. Send Info For MT Reconnected Call is used to request the VLR to provide information for a reconnected MT call. 9. Send Info For Outgoing Call is used to request the VLR to provide information for an outgoing call. 10. Complete Call is used to instruct the MSC to continue the connection of a call. 1. The MAP-FORWARD-NEW-TMSI service is used to allocate a new TMSI to a subscriber during an ongoing transaction. 2. The MAP_RESET service is used to indicate a failure to a list of VLRs, SGSNs, or MMEs after a restart. 3. The MAP_FORWARD_CHECK_SS_INDICATION service is used to indicate to a mobile subscriber that supplementary services parameters may have been altered. 4. The MAP_RESTORE_DATA service is used to update the LMSI in the HLR and request the HLR to send all data to the VLR for storage. 5. The MAP-ANY-TIME-INTERROGATION service is used to request information from the HLR or GMLC at any time. 6. The MAP-PROVIDE-SUBSCRIBER-INFO service is used to request information from the VLR, SGSN, or MME at any time. 7. The IMSI parameter contains the requested IMSI in the MAP-FORWARD-NEW-TMSI service. 8. The Reset-ID LIST parameter is a list of Reset-IDs used in the MAP_RESET service. 9. The gsmSCF-Address parameter is used to specify the address of the gsmSCF in the MAP-ANY-TIME-INTERROGATION service. 10. The User error parameter is used to indicate an error detected by the responder in the MAP-PROVIDE-SUBSCRIBER-INFO service. 1. If the Automatic Rearm IE is present in the Request Report BCSM Event information flow for certain call scenarios, the DP will be automatically rearmed by the gsmSSF when encountered. 2. The BCSMs defined above are used to model CS call scenarios, showing the used and unused BCSMs involved in the call. 3. CAMEL can be applied simultaneously and independently for each subscriber involved in a call. 4. For a mobile originated call, a CAMEL control relationship with gsmSCF will be established if certain conditions are met. 5. For a mobile terminated call at the GMSC or VMSC, separate CAMEL control relationships may be established between the GMSC/VMSC and gsmSCF. 6. Call forwarding at the GMSC or VMSC can trigger a CAMEL control relationship between the GMSC/VMSC and gsmSCF. 7. When the gsmSCF wishes to originate a new call, it establishes communication with the network using CAP signaling. 8. Trunk originated calls can also trigger a CAMEL control relationship between the MSC and gsmSCF. 9. A call may consist of multiple call parties, with each party connected to the call through a leg. 10. Legs can be created, continue to exist, be released, or be moved between call segments based on various events and triggers. - The server should forward the request to the addressed domain following the general behavior for proxying messages. - The registrar should authenticate the UAC and determine if the authenticated user is authorized to modify registrations for the address-of-record. - The registrar extracts the address-of-record from the To header field of the request and converts it to a canonical form. - The registrar checks if the request contains the Contact header field and processes each contact address in the Contact header field. - The registrar determines the expiration interval for each address and searches the list of current bindings using the URI comparison rules. - The registrar updates or removes the binding based on the Call-ID and CSeq values in the request. - If any binding updates fail, the request fails with a 500 (Server Error) response. - The registrar returns a 200 (OK) response with Contact header field values enumerating all current bindings. - The OPTIONS method allows a UA to query another UA or a proxy server for its capabilities. - An OPTIONS request is constructed using the standard rules for a SIP request and the response is constructed using the standard rules for a SIP response. 1. Class 2, 3, and 4 in ASN.1 operation definitions determine the presence of ERROR and RESULT. 2. The field ""ARGUMENT"", ""PARAMETER"", or ""RESULT"" is optional syntactically but mandatory semantically. 3. Missing optional elements in invoke components or inner data structures result in an error component. 4. Missing mandatory elements in parameters or data structures result in a reject component. 5. Timer values in operation definitions have specific ranges. 6. Global operation and error codes in ASN.1 can be encoded as Object Identifiers or integers. 7. Object Identifiers are limited in length and can only be used for operations or errors outside of GSM 29.002. 8. Unknown operation codes are handled according to defined rules. 9. Information elements defined outside of MAP can be carried as values of ASN.1 types or as ExternalSignalInfo. 10. Private extensions can be defined and included in operations based on the version of the application context. 1. UAs should not include certain header fields in an ""inner"" message if they are not included in the ""outer"" message. 2. UAs should ignore encrypted values if they receive certain header fields in an encrypted body. 3. Unknown header fields with an integrity violation should be ignored by SIP UAs. 4. Tunneling SIP messages within S/MIME bodies can provide integrity for SIP header fields. 5. A signed MIME body can provide limited authentication if it contains fundamental dialog identifiers. 6. Replicating all header fields from the request within the signed body helps eliminate confusion. 7. Significant time discrepancies in the Date header should be treated as potential security breaches. 8. Messages with integrity violations may be rejected or existing dialogs terminated. 9. Encryption with S/MIME is typically used to secure message bodies rather than message headers. 10. Encrypted ""message/sip"" MIME bodies should be signed by the sender to provide end-to-end integrity. 1. The ttl parameter is used to determine the time-to-live value of a UDP multicast packet in SIP. 2. The user URI parameter is used to distinguish telephone numbers from user names that resemble telephone numbers. 3. The method parameter specifies the method of the SIP request constructed from the URI. 4. The lr parameter indicates that the element implements the routing mechanisms specified in the document. 5. SIP elements should ignore any uri-parameters that they do not understand. 6. Header fields can be included in a request constructed from the URI using the ""?"" mechanism. 7. SIP and SIPS URIs are compared for equality based on specific rules, including case-sensitivity and parameter matching. 8. When forming requests from a URI, implementations should include transport, maddr, ttl, or user parameters in the Request-URI. 9. Implementations should not honor dangerous header fields or requests that may falsely advertise location or capabilities. 10. Tel URLs can be converted to SIP or SIPS URIs, but equivalence may not always be maintained. 1. The functional behavior of the VLR is specified in 3GPP TSÊ29.002Ê[34]. 2. The handling specific to CAMEL is specified in the CAMEL_MT_SMS_VLR procedure. 3. The functional behavior of the SGSN for delivery of MT short message is specified in 3GPP TSÊ29.002Ê[34]. 4. The procedure for checking CAMEL capability and subscription information is specified in the CAMEL_MT_SMS_SGSN procedure. 5. The gsmSSF or gprsSSF handles both mobile originating and mobile terminating SMS. 6. The Int_Invoke SMS_SSF signal determines which TDP should be armed. 7. The gsmSCF may place free-format charging data in the 'MOSMSRecord' or 'MTSMSRecord' CDR for MO-SMS or MT-SMS services respectively. 8. The Int_SMS_Failure signal may be received only for a MO-SMS service when a MS detach event occurs before the SMS_SSF is invoked. 9. The Process Complete_SMS_FCI_Record is used to close the 'MOSMSRecord' or 'MTSMSRecord' for MO-SMS or MT-SMS services respectively. 10. The information flows between gsmSSF or gprsSSF and gsmSCF include Event Report SMS, Initial DP SMS, Connect SMS, Continue SMS, and Furnish Charging Information SMS. 1. The IE ""Suppression Of Announcement"" indicates that unsuccessful call establishment announcements or tones should be suppressed. 2. The IE ""Suppress TCSI M"" indicates that CAMEL subscription information should not be returned in the first Send Routeing Info ack. 3. The IE ""Supported CAMEL Phases M"" indicates the CAMEL Phases supported by the gsmSCF. 4. The IE ""Offered CAMEL4 CSIs S"" indicates the CAMEL phase 4 CSIs offered by the gsmSCF. 5. The IE ""Call Reference Number M"" carries the Call Reference Number allocated for the call by the gsmSCF. 6. The IE ""GMSC Or gsmSCF Address M"" is the E.164 address of the gsmSCF. 7. The IE ""Call Diversion Treatment Indicator O"" indicates whether the call is allowed to be forwarded on behalf of the called party using Call Forwarding. 8. The IE ""Pre-paging Supported S"" indicates if the gsmSCF supports pre-paging. 9. The IE ""Interrogation Type M"" contains the value ""Basic Call"". 10. The IE ""Suppress MT SS O"" indicates the MT supplementary services that shall be suppressed for the called party. 1. An SDP answerer must include certain parameters unmodified from the SDP offer, such as ""octet-align"", ""crc"", ""robust-sorting"", ""interleaving"", and ""channels"". 2. AMR or AMR-WB packets should be generated according to the specified parameters. 3. The ""mode-set"" parameter can be used to restrict the set of active AMR/AMR-WB modes in a session, especially for gateways to access networks like GSM or 3GPP UMTS. 4. It is recommended to follow the preferred codec configurations defined in 3GPP for greatest interoperability. 5. The mode-set parameter applies to both received and sent media by the declaring entity. 6. If a mode-set was supplied in the offer, the answerer should return it unmodified or reject the payload type. 7. For multicast sessions, the answerer should only participate if it supports the offered mode-set. 8. The parameters ""mode-change-period"" and ""mode-change-capability"" are used in sessions with gateways to determine if the payload type can be supported. 9. The parameter ""mode-change-neighbor"" is a recommendation to restrict the switching of codec modes to its neighbor. 10. The parameters ""maxptime"" and ""ptime"" can affect the performance of the application and should be selected carefully. 1. Each instance of the Core Network Service Authorization class can have zero or one instance of the Subscribed Media Profile Id class, which is used for media parameter authorization. 2. If no instance of the Subscribed Media Profile Id class is present, no filtering related to subscribed media applies in S-CSCF. 3. The Subscribed Media Profile Id is an Integer type attribute that identifies a media profile in the S-CSCF for authorization. 4. Each instance of the Core Network Service Authorization class can have zero or one instance of the List of Service Ids class, which is used for IMS Communication Service Identifier restriction. 5. If no instance of the List of Service Ids class is present, no restriction on IMS Communication Service Identifiers applies in S-CSCF. 6. The List of Service Ids class contains zero or more instances of the Service Id class, which is of type String and identifies authorized IMS Communication Service Identifiers. 7. The Initial Filter Criteria class is used for defining filter criteria and trigger points for contacting an Application Server. 8. Each instance of the Initial Filter Criteria class has a Priority attribute indicating the priority of the filter criteria. 9. The Initial Filter Criteria class can be part of the registered or unregistered user profile, indicated by the ProfilePartIndicator attribute. 10. The Initial Filter Criteria class includes a TriggerPoint class for describing the trigger points to determine if an Application Server should be contacted. 1. The S-CSCF/I-CSCF and HSS/SLF prioritize requests and responses based on the priority level received within the DRMP AVP or the corresponding request. 2. If the required priority level differs from the received priority level, the DRMP AVP is included in the response. 3. If the S-CSCF/I-CSCF or HSS/SLF supports DSCP marking and the transport network utilizes it, the DSCP marking is set according to the required priority level. 4. Diameter requests related to priority traffic contain a DRMP AVP with a high priority level. 5. The inclusion and priority value of the DRMP AVP in Diameter messages are implementation specific unless explicitly requested. 6. The HSS/SLF complies with IETF RFC 7944 when supporting the Diameter message priority mechanism. 7. The HSS/SLF determines the required priority level according to its policies and includes the DRMP AVP in the request it sends. 8. The I-CSCF/S-CSCF may consider load values from Load AVPs of type PEER when selecting the next hop Diameter Agent. 9. The HSS may report its current load by including a Load AVP of type HOST in answer commands. 10. The HSS calculates its current load based on various factors such as traffic, resource usage, and access to external resources. 1. The MAP protocol consists of various services and service primitives. 2. Each service has its own definition, service primitives, and parameter use. 3. The MAP_IST_COMMAND service is defined in section 10.14 and has its own set of service primitives and parameter use. 4. The MAP_RELEASE_RESOURCES service is defined in section 10.15 and also has its own set of service primitives and parameter use. 5. Supplementary services related services are covered in section 11, which includes services like MAP_REGISTER_SS and MAP_ERASE_SS. 6. The MAP_ACTIVATE_SS service is defined in section 11.3 and has its own set of service primitives and parameter use. 7. The MAP_DEACTIVATE_SS service is defined in section 11.4 and has its own set of service primitives and parameter use. 8. The MAP_INTERROGATE_SS service is defined in section 11.5 and has its own set of service primitives and parameter use. 9. The MAP_REGISTER_PASSWORD service is defined in section 11.7 and has its own set of service primitives and parameter use. 10. The MAP_GET_PASSWORD service is defined in section 11.8 and has its own set of service primitives and parameter use. 1. The Multimedia-Auth-Answer (MAA) command is sent by a server in response to the Multimedia-Auth-Request command. 2. The Registration-Termination-Request (RTR) command is sent by a Diameter Multimedia server to request the de-registration of a user. 3. The Registration-Termination-Answer (RTA) command is sent by a client in response to the Registration-Termination-Request command. 4. The Push-Profile-Request (PPR) command is sent by a Diameter Multimedia server to update subscription data and authentication data of a multimedia user. 5. The Push-Profile-Answer (PPA) command is sent by a client in response to the Push-Profile-Request command. 6. Result-Code AVP values are used to inform the success or failure of a request. 7. Permanent Failures category includes errors that indicate a request has failed and should not be attempted again. 8. Diameter Multimedia Application AVPs are defined for the Cx interface protocol. 9. AVPs have different flag rules indicating whether they are mandatory, optional, or vendor-specific. 10. The Visited-Network-Identifier AVP is used to identify the visited network. 1. Proxies in SIP are responsible for routing requests and responses between user agents. 2. Proxies can operate in stateful or stateless mode. 3. In stateful mode, proxies remember information about requests and use it to process future messages. 4. Proxies can forward requests to multiple destinations, known as forking. 5. Stateful proxies have a server transaction for incoming requests and client transactions for outgoing requests. 6. Proxies validate requests, preprocess routing information, and determine the target for each request. 7. Proxies should not generate 100 Trying responses for non-INVITE requests. 8. Proxies can transition from stateful to stateless mode at any time. 9. Stateful proxies create a new server transaction for each new request. 10. Proxies behave as UAS when sending immediate provisional responses. 1. The Result-Code AVP is used to indicate success or errors in the Diameter base protocol. 2. The Experimental-Result AVP is used for S6a/S6d errors and contains the 3GPP Vendor ID and error code. 3. If the IMSI is unknown, a result code of DIAMETER_ERROR_USER_UNKNOWN is returned. 4. If the Context-Identifier is associated with the default APN configuration, the PDN subscription context is not deleted and an error with Result-Code DIAMETER_UNABLE_TO_COMPLY is returned. 5. The MME or SGSN deletes corresponding data based on the request and acknowledges with a Delete Subscriber Data Answer. 6. If the ""Complete APN Configuration Profile Withdrawal"" bit is set in the DSR-Flags AVP, an error with Result-Code DIAMETER_UNABLE_TO_COMPLY is returned. 7. If the Regional Subscription is deleted, the SGSN checks if the SGSN area is restricted and reports it to the HSS. 8. If the EPS Subscription Data is deleted, the MME or SGSN may deactivate affected active EPS bearers. 9. If the Subscribed Charging Characteristics are deleted, the Gn/Gp-SGSN or MME/S4-SGSN maintains the existing characteristics. 10. If the MSISDN is deleted, the MME or SGSN maintains the existing MSISDN for existing PDN connections. 1. If the MME or SGSN does not support a certain feature, the HSS will not send the related information to them. 2. Instead, the HSS may reject location updates or apply barring of roaming in certain cases. 3. Different types of Operator Determined Barring (ODB) categories exist for various types of outgoing calls. 4. The HSS may reject location updates if the MME or SGSN does not support certain ODB categories. 5. The HSS may apply barring of roaming and send a CLR message if the MME or SGSN does not indicate support for a specific ODB category. 6. Regional Subscription Zone Codes can be sent by the HSS to the MME or SGSN, but only if they support this feature. 7. Trace Data can be sent by the HSS to the MME or SGSN, but only if they indicate support for this feature. 8. Different LCS Privacy Exception Classes exist for location-based services. 9. The HSS may store indications of support for certain LCS features by the MME or SGSN and adjust its behavior accordingly. 10. Different SMS-related features, such as Barring of Outgoing Calls, can be supported by the HSS and sent to the MME or SGSN. 1. The MAP_UPDATE_LOCATION service is used to update the location information stored in the HLR and is a confirmed service. 2. The service primitives for the MAP_UPDATE_LOCATION service include Request, Indication, Response, and Confirm. 3. Parameters for the MAP_UPDATE_LOCATION service include IMSI, MSC Address, VLR number, LMSI, Supported CAMEL Phases, SoLSA Support Indicator, IST Support Indicator, Long FTN Supported, Supported LCS Capability Sets, Offered CAMEL 4 CSIs, Inform Previous Network Entity, CS LCS Not Supported by UE, V-GMLC Address, IMEISV, Skip Subscriber Data Update, Supported RAT Types Indicator, Paging Area, Restoration Indicator, MTRF Supported, Equivalent PLMN List, MSISDN-less Operation Supported, MME-Diameter-Address-For MT-SMS, Reset-IDs Supported, ADD Capability, Paging Area Capability, User error, and Provider error. 4. The MAP_CANCEL_LOCATION service is used to delete a subscriber record from the VLR or SGSN and is a confirmed service. 5. The service primitives for the MAP_CANCEL_LOCATION service include Request, Indication, Response, and Confirm. 6. Parameters for the MAP_CANCEL_LOCATION service include IMSI, LMSI, Cancellation Type, and MTRF Supported And Authorized. 7. The MAP_CANCEL_LOCATION service can be used to enforce a location updating from the VLR to the HLR or from the SGSN to the HLR. 8. The MAP_CANCEL_LOCATION service can also be used to request the SGSN or MME to indicate to the MS or UE to initiate an immediate re-attach procedure. 9. The MAP_CANCEL_LOCATION service is used between HSS and IWF, and between IWF and IWF, in an EPS to delete the subscriber record from the MME or SGSN or to release bearer resources without deleting the subscriber record. 10. The MAP_CANCEL_LOCATION service is a confirmed service and uses the primitives defined in the table. 1. The HLR uses a parameter to indicate the available service for a call when two services have been requested. 2. Another parameter is used to indicate the reason for the unavailability of one of the services. 3. The presence of a parameter indicates a request for Mobile Number Portability (MNP) information. 4. The Access Restriction Data parameter refers to restricted radio access technologies for a subscriber. 5. The Supported RAT types indicator parameter indicates the supported RAT types by the network. 6. The UE SRVCC Capability parameter indicates if the UE supports SRVCC capability. 7. The WLAN-offloadability parameter refers to the WLAN offloadability for E-UTRAN or UTRAN. 8. The IMSI-Group-Id parameter refers to the IMSI-Group identifier. 9. The SS-Code parameter refers to one or a set of supplementary services. 10. The SS-Status parameter refers to the state information of individual supplementary services. 1. The SupportedRAT-Types parameter indicates the types of radio access technologies supported, such as UTRAN, GERAN, GAN, I-HSPA-Evolution, E-UTRAN, and NB-IoT. 2. The SuperChargerInfo parameter can either send subscriber data or indicate that the subscriber data is stored. 3. The IST-SupportIndicator parameter indicates the level of support for IST (IP Multimedia Subsystem Service Triggering). 4. The SupportedLCS-CapabilitySets parameter indicates the supported sets of location services capabilities, ranging from Release98 to Release7 or later versions. 5. The UpdateLocationRes message includes the HLR number and optional capabilities for additional functionality. 6. The ADD-Info structure includes information such as IMEISV and the option to skip subscriber data update. 7. The CancelLocationArg message includes various optional parameters for cancellation, such as the type of update and new MSC/VLR numbers. 8. The TypeOfUpdate parameter indicates the type of update, such as SGSN change or MME change. 9. The PurgeMS-Arg message includes optional parameters for purging a mobile station, such as location information and freeze indicators. 10. The SendIdentificationArg message includes parameters for sending identification, such as TMSI and the number of requested vectors. 1. The PPR command code 5.5.0 Dec 2003 CN#22 NP-030500 021 requires checking the S-CSCF name in MAR and SAR. 2. User-Authorization-Type needs to be updated in the PPR command code 5.6.0 Dec 2003 CN#22 NP-030500 027. 3. Clarifications are needed for the inclusion of elements in Charging Information in the PPR command code 5.6.0 Dec 2003 CN#22 NP-030518 029. 4. Application IDs and references were updated in the PPR command code 5.6.0 Dec 2003 CN#22. 5. Error handling for no identification in SAR command needs to be addressed in the PPR command code 5.6.0 Mar 2004 CN#23 NP-040055 035. 6. Charging addresses from HSS need to be updated in the PPR command code 6.0.0 Jun 2004 CN#24 NP-040215 037. 7. Corrections are needed for the Multimedia-Auth-Request (MAR) Command Message Format in the PPR command code 6.1.0 Jun 2004 CN#24 NP-040215 043. 8. Vendor-Id usage by 3GPP needs to be clarified in the PPR command code 6.1.0 Sep 2004 CN#25 NP-040395 065. 9. Application version control needs to be optimized in the PPR command code 6.2.0 Sep 2004 CN#25 NP-040401 056. 10. User Profile Download needs to be simplified in the PPR command code 6.2.0 Sep 2004 CN#25 NP-040396 058. 1. Overload levels in Location Registers can lead to the discarding of MAP operations based on their priority. 2. The priority of application contexts for different entities (HLR, MSC/VLR, SGSN, SMLC) determines which operations are discarded first. 3. The priority rankings in the tables provided are not normative and can be changed by network operators. 4. The selection of application context version should minimize protocol fallbacks and can be based on a version control table. 5. SCCP is used in the Mobile Application Part (MAP) and supports connectionless classes (0 or 1). 6. MAP entities are addressed using sub-system numbers (SSNs) specified in 3GPP TS 23.003. 7. Intra-PLMN addressing within the same PLMN requires the inclusion of MAP SSN in the called and calling party addresses. 8. Inter-PLMN addressing between different PLMNs requires the use of global titles and routing on global title. 9. ANSI T1.112 SCCP can be used for addressing with similar restrictions as the ITU-T/CCITT SCCP. 10. The support of White Book SCCP is mandated for inter-MSC handover/relocation and recommended for other MAP messages. 1. Overload control is required for all entities in the Public Land Mobile Network and Signalling System No. 7. 2. Different procedures can be applied to control processor load for the MSC and MAP entities. 3. Overload levels in Location Registers can result in certain MAP operations being discarded based on priority. 4. SS7 Congestion control requirements should be considered to achieve required traffic reductions. 5. The Mobile Application Part is designed to be compatible with previous versions, except on the MSC-VLR interface. 6. A version negotiation mechanism based on application-context-name is used to negotiate protocol version between entities. 7. A method can be used to minimize protocol fallbacks by selecting the highest supported application context version. 8. A table can be set up to define the highest application context version supported by each destination. 9. SCCP is used by the Mobile Application Part and supports different versions, including White Book SCCP. 10. The Application Entities in MAP are addressed by sub-system numbers (SSNs) specified in 3GPP TS 23.003. 1. The Coupled-Node-Diameter-ID AVP allows the HSS to determine if the UE is served by the MME and SGSN parts of the same combined MME/SGSN. 2. The MME and SGSN exchange Diameter identities over the S6a and S6d interfaces to establish communication. 3. The MME can request registration for SMS if it supports the ""SMS in MME"" feature and the UE requests a combined EPS/IMSI attach or Combined TA/LA Update. 4. The SGSN can provide SMS services by setting the ""SMS in SGSN"" flag in the Feature-List AVP and including the SMS-Register-Request AVP. 5. The MME or SGSN can prioritize PDN connections based on Restoration-Priority information received in the subscription data. 6. The MME or SGSN can determine the offloadability of the UE's PDN Connection(s) based on WLAN-offloadability AVP in the subscription data. 7. The MME or SGSN can invoke extended buffering of downlink packets at the SGW for High Latency Communication based on DL-Buffering-Suggested-Packet-Count AVP in the subscription data. 8. The MME or SGSN replaces stored IMSI-Group-Id with received information and starts/stops monitoring events based on received Monitoring-Event-Configuration AVPs. 9. The HSS checks subscription data, RAT type, EPC access, and roaming restrictions to determine if the UE is allowed access. 10. The HSS includes subscription data in the ULA command based on flags and supported features, and stores terminal information and UE SRVCC capability if present. 1. The INVITE should include an Allow header field indicating the methods that can be used within the dialog. 2. The INVITE should include a Supported header field listing the extensions understood by the UAC. 3. The Accept header field in the INVITE indicates the acceptable Content-Types for the response and subsequent requests within the dialog. 4. The UAC can add an Expires header field to limit the validity of the invitation. 5. The UAC can include additional header fields like Subject, Organization, and User-Agent in the INVITE. 6. The UAC may choose to include a message body in the INVITE, especially for session descriptions. 7. The offer/answer model is used in SIP, where one UA sends an offer and the other UA responds with an answer. 8. Offers and answers can only appear in INVITE requests, responses, and ACK. 9. The UAC must treat the first session description it receives as the answer and ignore subsequent session descriptions. 10. The UAS can indicate progress, accept, redirect, or reject the INVITE with appropriate responses. 1. The GPRS Subscription Data Not Needed Indicator shows that the SGSN does not require GPRS Subscription Data in addition to EPS Subscription Data. 2. The EPS Subscription Data Not Needed Indicator indicates that the SGSN does not need EPS Subscription Data in addition to GPRS Subscription Data. 3. The Node-Type Indicator shows whether the requesting node is a combined MME/SGSN or a single MME or SGSN. 4. The Area Restricted Indicator indicates that the network node area is restricted due to regional subscription. 5. The UE-Reachable Indicator shows that the UE is reachable. 6. The T-ADS Data Retrieval Support Indicator indicates that the SGSN supports retrieval of T-ADS data. 7. The Homogeneous Support Of IMS Voice Over PS Sessions parameter indicates whether IMS voice over PS sessions is homogeneously supported in the SGSN area. 8. The Update of Homogeneous Support Of IMS Voice Over PS Sessions parameter indicates that the support of IMS voice over PS sessions has been updated. 9. The UE SRVCC Capability parameter indicates the UE's capability for Single Radio Voice Call Continuity. 10. The Equivalent PLMN List parameter indicates the list of PLMNs for which the MME/SGSN requests CSG Subscription data. 1. The S-CSCF informs the HSS when a Public Identity is registered or deregistered. 2. The HSS holds information about the registration state of all identities related to an IMS Subscription. 3. User-initiated registration/deregistration procedures are only allowed for distinct Public User Identities. 4. The HSS checks the existence of Public and Private Identities and their association. 5. The HSS checks the type of Public Identity and its activation state for Public Service Identities. 6. The HSS checks the Server Assignment Type and determines the appropriate response based on the assigned S-CSCF. 7. The HSS downloads relevant user information and sets the registration state of the Public User Identity. 8. The HSS may include Associated-Identities and S-CSCF Restoration Information in the response. 9. The S-CSCF uses wildcarded public identity matching to fetch user profiles and registration information. 10. The HSS sends P-CSCF restoration indications to serving nodes if supported and necessary. 1. The document contains a list of proposed updates and clarifications to various aspects of the GSM and UMTS networks. 2. The updates cover topics such as ciphering, authentication data, LCS capability handling, and E911 location provision. 3. There are also proposals for SMS fraud countermeasures, management-based activation impacts, and additions to trace management procedures. 4. Other updates include support for talker priorities, delivery of SMS to voice group calls, and CS data mobile terminating calls from PSTN. 5. The document also includes improvements to VGCS call establishment, addition of UMTS trace parameters to handover procedures, and removal of MAPsec material. 6. There are proposals for enhancements to group call functionalities, support for velocity providing, and enabling the providing of location information based on the current location of the target UE. 7. The updates also cover topics such as support for SMS over IP networks, extension of group ID, and addition of teleservice code to SendGroupCallInfo. 8. There are proposals for accuracy fulfillment indicator parameter to MAP SLR for deferred MT-LR, improvements to SMS router optimization, and addition of UMTS trace parameters to handover procedures. 9. The document also includes updates on topics such as support for IMS centralized service subscription information, eMLPP priority in MAP SRI, and Gr+ enhancements for EPS. 10. There are proposals for RAT frequency selection priority, change in AMBR placement, and addition of APN-OIReplacement and Access Restriction parameters. 1. The offer-answer model is used to modify an existing dialog or session in SIP. 2. Modifying a session can involve changing addresses, ports, adding or deleting media streams, etc. 3. A re-INVITE is an INVITE request sent within an existing dialog to modify the session. 4. Either the caller or callee can initiate a session modification. 5. The behavior of a UA on media failure is determined by local policy. 6. Automated generation of re-INVITE or BYE messages is not recommended to avoid network congestion. 7. If sent automatically, these messages should be sent after a randomized interval. 8. A UAC can add a media stream by creating a new offer and sending it in an INVITE request. 9. The full description of the session, not just the change, is sent in the offer. 10. A UAS can reject a re-INVITE if the session description is not acceptable. 1. The SGs-MME-Identity AVP is a UTF8String type that contains the MME identity used over the SGs interface. 2. The SIPTO-Local-Network-Permission AVP is an Unsigned32 type that indicates whether the traffic associated with a specific APN is allowed for SIPTO at the local network. 3. The Coupled-Node-Diameter-ID AVP is a DiameterIdentity type that contains the S6a or S6d Diameter identity of the coupled node. 4. The OC-Supported-Features AVP is a Grouped type used to support Diameter overload control mechanism. 5. The OC-OLR AVP is a Grouped type used to support Diameter overload control mechanism. 6. The ProSe-Subscription-Data AVP is a Grouped type that contains ProSe related subscription data. 7. The WLAN-offloadability AVP is a Grouped type that contains WLAN offloadability for E-UTRAN or UTRAN. 8. The Reset-ID is an OctetString type that uniquely identifies a resource in the HSS. 9. The MDT-Allowed-PLMN-Id AVP is an OctetString type that contains the PLMN in which the MDT data collection shall take place. 10. The Adjacent-PLMNs AVP is a Grouped type that contains a list of PLMN IDs where an UE is likely to make a handover from the current PLMN. 1. The MME or SGSN includes information about failed monitoring event configurations in a Notify Request to the HSS. 2. The MME or SGSN notifies the HSS when a new PDN-GW is selected for an emergency PDN connection. 3."
"The Result-Code AVP indicates the success or errors in the operation. 4. The Supported-Features AVP contains the list of features supported by the origin host. 5. The MME or SGSN does not use the Notification procedure for emergency attached unauthenticated UEs. 6. The HSS stores new terminal information and UE SRVCC capability received in the Notify request. 7. The HSS updates the Homogeneous Support of IMS Voice Over PS Sessions based on the NOR received from the MME or SGSN. 8. The HSS removes the MME registration for SMS when requested in the NOR. 9. The HSS triggers a Monitoring event cancelation or suspension procedure based on the result code received in the NOR. 10. The HSS updates the VCSG location and retrieves CSG subscription data from the CSS in the Update VCSG Location Procedure. 1. When the configuration UseCorrelateVLAN or UseAlwaysVLAN is set, the VLAN ID is used for traffic lookup, but if it's not present, only the Last leg Source IP Address is considered. 2. The Calling Party Number field is applicable to various protocols and can be found in different CSDR types. 3. The Called Party Number field is applicable to various protocols and can be found in different CSDR types. 4. CAP and INAP de-duplicated generations utilize specific fields to avoid duplication. 5. The Payment Plan feature is optional and is based on the lookup of IMSI on the Mobile Subscriber table. 6. The First Leg Forward Linkset Name is retrieved from the MasterClaw Configuration database and is specific to the initial message of a transaction. 7. The First Leg Backward Linkset Name is retrieved from the MasterClaw Configuration database and is specific to the response message to the initial message of a transaction. 8. The Last Leg Forward Linkset Name is specific to the last forward message in the last leg of a sequence and can be found in different CSDR types. 9. The Last Leg Backward Linkset Name is specific to the first backward message in the last leg of a sequence and can be found in different CSDR types. 10. The OTID field represents the Originating Transaction ID of TCAP and is filled from the BEGIN message or the DTID of the END/CONTINUE message. 1. The dialog in SIP is established through the exchange of requests and responses, with each contributing to the dialog identifier in the To header field. 2. The uniqueness and randomness of tags in the From and To header fields are important for disambiguating multiple dialogs established from a single request. 3. Tags are useful in fault-tolerant systems for recovering dialogs on alternate servers after a failure. 4. The algorithm for generating a tag is implementation-specific, but it must be globally unique and cryptographically random. 5. The Accept header field specifies the acceptable formats for the response, with a default value of application/sdp if not present. 6. The Accept-Encoding header field restricts the content encodings that are acceptable in the response, with identity encoding as the default. 7. The Accept-Language header field indicates the preferred languages for reason phrases, session descriptions, or status responses in the response. 8. The Alert-Info header field specifies an alternative ring tone for the UAS in an INVITE request or a ringback tone for the UAC in a 180 response. 9. The Allow header field lists the methods supported by the UA generating the message. 10. The Authentication-Info header field provides mutual authentication with HTTP Digest, while the Authorization header field contains authentication credentials of a UA. 1. The client transaction in SIP involves the exchange of requests and responses between the client and server. 2. The client transaction has different states, including ""Calling,"" ""Proceeding,"" and ""Completed."" 3. The client transaction uses timers to handle retransmissions and timeouts. 4. The client transaction transitions to the ""Proceeding"" state when it receives a provisional response. 5. The client transaction transitions to the ""Completed"" state when it receives a final response. 6. The client transaction generates an ACK request to acknowledge a final response. 7. The client transaction sets a timer when it enters the ""Completed"" state to handle retransmissions of the final response. 8. The client transaction transitions to the ""Terminated"" state when the timer for retransmissions expires. 9. The non-INVITE client transaction follows a similar state machine as the INVITE client transaction. 10. The non-INVITE client transaction does not use ACK requests and handles responses differently. 1. The arrangement of speech frame-blocks in an interleaving group during an interleaving session follows a specific pattern. 2. The interleaving group starts at speech frame-block n and carries N speech frame-blocks in each payload. 3. The first payload packet of the interleaving group is labeled as s and carries frame-blocks n, n+(L+1), n+2*(L+1), ..., n+(N-1)*(L+1). 4. The next interleaving group will start at frame-block n+N*(L+1). 5. Interleaving only has an effect if the number of frame-blocks per packet (N) is at least 2. 6. The number of frame-blocks per payload (N) and the value of ILL must not be changed within an interleaving group. 7. Interleaving is only applied if the receiver has signaled its use through out-of-band means. 8. The maximum number of frame-blocks allowed in an interleaving group is set using the media type parameter ""interleaving=I"". 9. The table of contents (ToC) in octet-aligned mode consists of a list of ToC entries and an optional list of speech frame CRCs. 10. The ToC entries and speech frame CRCs are organized in a specific format and are used for data integrity checks. 1. The MAP process in the HLR provides subscription information in response to an interrogation from the CAMEL server. 2. If the response cannot be carried in a single component, it is carried in multiple components followed by a TC-Result-L component in a TC-END message. 3. The Any Time Modification procedure involves modifying subscription information in response to a request from the application process in the gsmSCF. 4. The MAP process in the HLR modifies subscriber information in response to a modification request from the CAMEL server. 5. If the response cannot be carried in a single component, it is carried in multiple components followed by a TC-Result-L component in a TC-END message. 6. The Subscriber Data Modification Notification procedure is used to notify a gsmSCF about the modification of subscriber data. 7. The MAP process in the HLR sends modified data to the gsmSCF and may segment the information into multiple requests. 8. The MAP process in the gsmSCF handles a notification of change of subscriber data and stores the received data. 9. The Any Time Interrogation procedure involves retrieving subscriber information from the HLR or GMLC in response to an interrogation from the CAMEL server. 10. The MAP process in the HLR provides subscriber information in response to an interrogation from the CAMEL server. 1. The document is a technical specification for CAMEL Phase 4, which is a custom application for mobile network enhanced logic. 2. The specification supports partial implementation of CAMEL Phase 4 and provides information on architecture, interfaces, detection points, and CAMEL subscriber data. 3. CAMEL Phase 4 includes circuit-switched call control functionalities. 4. The architecture involves various functional entities and interfaces such as HLR-VLR, GMSC-HLR, GMSC-gsmSSF, gsmSSF-gsmSCF, MSC-gsmSSF, gsmSCF-HLR, gsmSCF-gsmSRF, and GMSC-MSC. 5. Detection points (DPs) are used to trigger specific actions in the CAMEL system based on predefined criteria. 6. DPs include Collected_Info, Analysed_Information, Route_Select_Failure, Terminating_Attempt_Authorised, T_Busy, and T_No_Answer. 7. CAMEL subscriber data includes Originating CAMEL Subscription Information (O-CSI) and Dialled Service CAMEL Subscription Information (D-CSI). 8. O-CSI contains information such as TDP List, gsmSCF address, service key, default call handling, DP criteria, CAMEL capability handling, CSI state, and notification flag. 9. D-CSI is used for dialled service-specific CAMEL subscription information. 10. The document is copyrighted by the 3GPP Organizational Partners and is provided for future development work within 3GPP. 1. The reuse of HTTP Digest authentication in SIP provides replay protection and one-way authentication. 2. S/MIME allows for the encryption of MIME bodies within SIP, ensuring end-to-end confidentiality and integrity. 3. S/MIME can also be used to provide integrity and confidentiality for SIP header fields through message tunneling. 4. Proxy servers, redirect servers, and registrars must implement TLS and support mutual and one-way authentication. 5. UAs should be capable of initiating TLS connections and may also act as TLS servers. 6. SIP elements supporting TLS must have a mechanism for validating certificates received during TLS negotiation. 7. Proxy servers, redirect servers, registrars, and UAs may implement IPSec or other lower-layer security protocols. 8. UAs should initiate a TLS connection when contacting proxy servers, redirect servers, or registrars. 9. Proxy servers, redirect servers, and registrars should be configured with at least one Digest realm. 10. UAs may support the signing and encrypting of MIME bodies and transfer of credentials with S/MIME. 1. The MAP-DELETE-SUBSCRIBER-DATA service is used to remove subscriber data from a VLR or SGSN when a subscription is withdrawn. 2. This service is not used for erasure or deactivation of supplementary services. 3. It is also used to remove GPRS subscription data from an SGSN and EPS subscription data from an MME. 4. The service consists of various parameters that specify the data to be deleted. 5. The Basic Service List parameter is used to withdraw one or more basic services from the subscriber. 6. The SS-Code List parameter is used to withdraw one or more supplementary services from the subscriber. 7. The Roaming Restriction Due To Unsupported Feature parameter is used to remove roaming restrictions caused by unsupported features. 8. The CAMEL Subscription Info Withdraw parameter is used to delete CAMEL Subscription Info from the VLR or SGSN. 9. The Regional Subscription Identifier parameter is used to delete all Zone Codes from the subscriber data. 10. The VBS Group Indication parameter is used to delete all Group Ids for the Voice Broadcast teleservice. 1. Certificates received during authentication should be validated with root certificates held by the client. 2. The use of ""transport=tls"" in the SIPS URI scheme has been deprecated. 3. HTTP Digest authentication scheme in SIP allows for replay protection and one-way authentication. 4. S/MIME allows for end-to-end encryption of MIME bodies within SIP messages. 5. Proxy servers, redirect servers, and registrars must implement TLS and support mutual and one-way authentication. 6. UAs may initiate TLS connections and act as TLS servers. 7. All SIP elements supporting TLS must validate certificates received during TLS negotiation. 8. Proxy servers, redirect servers, registrars, and UAs may implement IPSec or other lower-layer security protocols. 9. UAs should establish TLS connections when contacting proxy servers, redirect servers, or registrars. 10. Proxy servers, redirect servers, registrars, and UAs must implement Digest Authorization. 1. The PDN IP Address of the user is specified in 3GPPÊTSÊ32.299Ê[8]. 2. QoS-Class-Identifier is defined in 3GPPÊTSÊ29.212Ê[10]. 3. Allocation-Retention-Priority is defined in 3GPPÊTSÊ29.212Ê[10]. 4. The Priority-Level is specified in 3GPPÊTSÊ29.212Ê[10]. 5. Pre-emption-Capability is defined in 3GPPÊTSÊ29.212Ê[10]. 6. Pre-emption-Vulnerability is specified in 3GPPÊTSÊ29.212Ê[10]. 7. Max-Requested-Bandwidth-DL is defined in 3GPPÊTSÊ29.214Ê[11]. 8. Max-Requested-Bandwidth-UL is specified in 3GPPÊTSÊ29.214Ê[11]. 9. RAT-Type is defined in 3GPPÊTSÊ29.212Ê[10]. 10. MSISDN must be set according to 3GPPÊTSÊ29.329Ê[25]. 1. This document specifies the interactions between the HSS and CSCF in the Cx interface. 2. It also specifies the interactions between CSCF and SLF in the Dx interface. 3. The document addresses the signalling flows for Cx and Dx interfaces. 4. It provides information on the functionality of the Px interface. 5. The document is related to the IP Multimedia (IM) Subsystem and its call control based on SIP and SDP. 6. It describes the architecture and functional solution for the Presence Service. 7. The document references other technical specifications related to IP multimedia, network architecture, and access security. 8. It uses modal verbs like ""shall,"" ""should,"" and ""may"" to indicate requirements, recommendations, and permissions. 9. The document includes a foreword explaining the meanings of modal verbs and their usage. 10. It is subject to change and may be re-released with updated versions based on TSG approval. 1. If the LIPA-Permission for an APN is ""LIPA only,"" the MME/SGSN will only allow LIPA for that APN via authorized CSGs. 2. If the LIPA-Permission for an APN is ""LIPA prohibited,"" the MME/SGSN will not allow LIPA for that APN. 3. If the LIPA-Permission for an APN is ""LIPA conditional,"" the MME/SGSN will allow non-LIPA and LIPA for that APN via authorized CSGs. 4. If the LIPA-Permission is not present for a specific APN, LIPA will not be allowed for that APN. 5. The LIPA-Permission for the Wildcard APN applies to any APN not explicitly present in the subscription data. 6. The SIPTO-Permission for the Wildcard APN applies to any APN not explicitly present in the subscription data. 7. The SIPTO-Local-Network-Permission for the Wildcard APN applies to any APN not explicitly present in the subscription data. 8. If a certain APN is authorized due to having the Wildcard APN in the user subscription, the MME will not store this APN data beyond the UE session. 9. If the MME supports Relay Node functionality and the subscription data indicates the subscriber is not a relay, the MME will reject the attach request as a Relay Node. 10. If trace data is received in the subscriber data, the MME/SGSN will start a Trace Session. 1. The data types for CAMEL include CellGlobalIdOrServiceAreaIdOrLAI, CellGlobalIdOrServiceAreaIdFixedLength, and LAIFixedLength. 2. The data types for subscriber management include BasicServiceCode, Ext-BasicServiceCode, EMLPP-Info, EMLPP-Priority, MC-SS-Info, MaxMC-Bearers, MC-Bearers, and Ext-SS-Status. 3. The data types for geographic location include AgeOfLocationInformation, LCSClientExternalID, LCSClientInternalID, and LCSServiceTypeID. 4. The data types for gprs location registration include GSN-Address. 5. The data types for numbering and identification include IMSI, Identity, IMEI, HLR-Id, HLR-List, LMSI, and GlobalCellId. 6. The data types for signaling information include ExternalSignalInfo, SignalInfo, ProtocolId, Ext-ExternalSignalInfo, Ext-ProtocolId, AccessNetworkSignalInfo, and LongSignalInfo. 7. The data types for network resources include NetworkResource and AdditionalNetworkResource. 8. The data types for preferred CI include NAEA-PreferredCI and NAEA-CIC. 9. The data types for subscriber identity include SubscriberIdentity, IMSI, IMSI-WithLMSI, TMSI, and MSISDN. 10. The data types for LCS include LCSClientExternalID, LCSClientInternalID, and LCSServiceTypeID. 1. The SCEF-Reference-ID, SCEF-ID, AESE-Communication-Pattern, Communication-Pattern-set, Monitoring-Event-Configuration, Monitoring-Event-Report, UE-Reachability-Configuration, eNodeB-ID, SCEF-Reference-ID-for-Deletion, Monitoring-Type, Maximum-Number-of-Reports, Monitoring-Duration, Charged-Party, Location-Information-Configuration, Reachability-Type, Maximum-Response-Time, Reachability-Information, Reachability-Cause, Monitoring-Event-Config-Status, Supported-Services, Supported-Monitoring-Events, DRMP, Reference-ID-Validity-Time, Maximum-UE-Availability-Time, Emergency-Services, Extended-eNodeB-ID, External-Identifier, Loss-Of-Connectivity-Reason, Active-Time, Idle-Status-Indication, MTC-Provider-Info, Traffic-Profile, PDN-Connectivity-Status-Configuration, PDN-Connectivity-Status-Report, Battery-Indicator, Battery-Indicator SCEF-Reference-ID-Ext, SCEF-Reference-ID-for-Deletion-Ext, and Reference-ID-Validity-Time must not be set. 2. The Subscription-Data AVP contains user profile information for EPS and GERAN/UTRAN. 3. The Terminal-Information AVP contains information about the user's terminal. 4. The IMEI AVP contains the International Mobile Equipment Identity. 5. The Software-Version AVP contains the Software Version Number of the International Mobile Equipment Identity. 6. The 3GPP2-MEID AVP contains the Mobile Equipment Identifier of the user's terminal. 7. The ULR-Flags AVP contains a bit mask with various indications. 8. The ULA-Flags AVP contains a bit mask with various indications. 9. The Visited-PLMN-Id AVP contains the concatenation of MCC and MNC. 10. The Feature-List AVP contains features related to Operator Determined Barring and Packet Oriented Services. 1. The document is about the use of UE-Reachability by SGSN in the context of GPRS and LTE networks. 2. It includes updates and additions to various protocols and interfaces. 3. The document covers topics such as anonymous call rejection, vSRVCC updates, and subscriber information handling. 4. It also addresses issues related to CSG subscription, SMS delivery, and UE reachability. 5. There are clarifications and corrections to existing specifications. 6. The document introduces new features like WLAN offloadability and support for NB-IoT. 7. It discusses enhancements to MDT (Minimization of Drive Tests) and T-ADS (Terminal Access Data Storage) retrieval. 8. The document emphasizes the importance of access restriction and coverage optimization. 9. It includes updates to ASN.1 module versions and references to other technical specifications. 10. The document is part of ongoing development work within the 3GPP and has not been approved for implementation. 1. MAP measures include various metrics related to SMS messages, such as payload size, number of MO and MT SMS messages, and success rates. 2. The MAP_SMS_SUBMIT_TIME measure represents the time when an SMS message was submitted, while MAP_SMS_DELIV_TIME represents the time when it was delivered. 3. The MAP_NO_CONCA_SMS measure indicates the number of concatenated SMS messages. 4. The Call Trace Jump field is not applicable in this context. 5. The EOTCAP TDR has common fields like Start Time, End Time, DR Generation Type, and Data Record Type. 6. The Data Record Type field in the EOTCAP TDR indicates the type of procedure or activity performed by the user, such as mobile originating/terminating calls or SMS. 7. The Violation field in the EOTCAP TDR indicates if there were any errors or missing messages in the sequence. 8. The Timeout field in the EOTCAP TDR identifies the type of timeout that occurred during processing. 9. The First Leg Originating Point Code field represents the originating point code of the transaction. 10. The First Leg Destination Point Code field represents the destination point code of the transaction. 1. The MAP_SEND_AUTHENTICATION_INFO service is used to retrieve authentication information from the HLR. 2. The service is used between the VLR and HLR, SGSN and HLR, and BSF and HLR. 3. The requesting node type determines the type of authentication vectors returned. 4. If the HLR cannot provide authentication triplets or quintuplets, an empty response is returned. 5. The VLR, SGSN, or BSF may re-use old authentication triplets, but not quintuplets. 6. The MAP_AUTHENTICATION_FAILURE_REPORT service is used to report authentication failures. 7. The service is used between the VLR and HLR, or SGSN and HLR. 8. The MAP_SET_CIPHERING_MODE service is used to set the ciphering mode and start ciphering. 9. The service is a non-confirmed service and consists of two service primitives. 10. The MAP_CHECK_IMEI service is used to request check of IMEI and obtain equipment status or BMUEF. 1. The AMR and AMR-WB speech codecs are used for encoding and decoding speech in real-time communication applications. 2. The payload format for AMR and AMR-WB in RTP allows for the transmission of speech frames over IP networks. 3. The payload format supports both single-channel and multi-channel audio. 4. The payload format includes parameters for controlling the coding mode, frame type, and frame quality of the speech frames. 5. The payload format can also include parameters for interleaving, robust sorting, and frame-wise CRC. 6. The storage format for AMR and AMR-WB files includes a header and consecutive speech frame-blocks. 7. The storage format supports both single-channel and multi-channel audio. 8. Congestion control mechanisms should be employed when transmitting AMR or AMR-WB speech over RTP. 9. Security considerations include confidentiality, authentication, and integrity of the speech data. 10. External mechanisms such as SRTP can be used for encryption, authentication, and integrity protection. 1. The MAP_REGISTER_SS service is used to register data related to a supplementary service between the MSC, VLR, and HLR. 2. The MAP_ERASE_SS service is used to erase data related to a supplementary service between the MSC, VLR, and HLR. 3. The MAP_ACTIVATE_SS service is used to activate a supplementary service between the MSC, VLR, and HLR. 4. The MAP_DEACTIVATE_SS service is used to deactivate a supplementary service between the MSC, VLR, and HLR. 5. The MAP_INTERROGATE_SS service is used to retrieve information related to a supplementary service between the MSC, VLR, and HLR. 6. The MAP_REGISTER_PASSWORD service is used to register a new password for a supplementary service between the MSC, VLR, and HLR. 7. The MAP_GET_PASSWORD service is used to request a password from the subscriber for a supplementary service between the HLR, VLR, and MSC. 8. The MAP_PROCESS_UNSTRUCTURED_SS_REQUEST service is used to relay information for unstructured supplementary service operation between the MSC, VLR, HLR, and gsmSCF. 9. User error parameters are sent by the responder when an error is detected in the service. 10. Provider error parameters are sent by the responder when there is an error related to the service provider. 1. The HLR can store up to 10 destination numbers for triggering criteria. 2. Overlapping destination numbers should be avoided to prevent unpredictable behavior. 3. Triggering at DPÊAnalysed_Info is based on the called party number or destination routing address. 4. Triggering at DPÊRoute_Select_Failure is based on the release cause code received from ISUP. 5. Triggering at DPÊTerminating_Attempt_Authorised is based on the basic service codes stored in the HLR. 6. Triggering at DPÊT_Busy and T_No_Answer is based on the release cause code received from ISUP or MAP. 7. A CAMEL relationship can be a control relationship or a monitor relationship. 8. EDPs are disarmed by the gsmSSF as they are encountered and reported to the gsmSCF. 9. A control relationship persists as long as there are armed EDPs or the Process CS_gsmSSF is not in Monitoring or Idle state. 10. A control relationship changes to a monitor relationship if there are armed EDPs or outstanding reports. 1. Media encryption is separate from SIP signaling encryption. 2. SIP requires security services to address threats such as registration hijacking, impersonating a server, tampering with message bodies, tearing down sessions, and denial of service attacks. 3. Classic threats demonstrate the need for security services like authentication, confidentiality, integrity, and preventing replay attacks. 4. Transport and network layer security can be provided by TLS or IPSec. 5. TLS is suitable for hop-by-hop security, while IPSec is better for existing trust relationships. 6. SIPS URI scheme allows for secure communication over TLS. 7. SIPS can be used in various contexts like addresses-of-record, contact addresses, and Route headers. 8. SIPS requires mutual TLS authentication and recommends the use of TLS_RSA_WITH_AES_128_CBC_SHA ciphersuite. 9. SIP can use HTTP Digest authentication for replay protection and one-way authentication. 10. S/MIME can be used to encrypt MIME bodies within SIP for end-to-end confidentiality, integrity, and authentication. 1. The processing of a CANCEL request at a server depends on the type of server. 2. CANCEL requests cannot be challenged by the server for proper credentials. 3. If a CANCEL request does not find a matching transaction, the server should respond with a 481 (Call Leg/Transaction Does Not Exist). 4. If a CANCEL request is received before a final response for the original request, the UAS should respond to the INVITE with a 487 (Request Terminated). 5. CANCEL requests have no impact on transactions with other methods defined in the specification. 6. The UAS answers the CANCEL request itself with a 200 (OK) response. 7. The To tag in the response to the CANCEL and the To tag in the response to the original request should be the same. 8. Registration creates bindings in a location service that associate an address-of-record URI with contact addresses. 9. Registrations can be added, removed, queried, or refreshed. 10. The expiration interval of contact addresses can be set and preferences among contact addresses can be indicated. 1. An 'M'ÊIE must always be included, while a 'C'ÊIE is included if the necessary information is available. 2. An 'S'ÊIE is included based on the conditions mentioned in the 'Description' column. 3. An 'O'ÊIE may be included or omitted as required by the service logic. 4. The categorization of IEs is a functional classification for stage 2 information, not for stage 3 ASN.1 syntax. 5. The gsmSCF and IP-SM-GW can discard unsupported IEs, while the HLR returns an error for unsupported IEs. 6. Details of errors and exceptions can be found in 3GPP TSÊ29.002Ê[34]. 7. The gsmSCF can modify information in the HLR at any time using the Any Time Modification Request IF. 8. The Any Time Subscription Interrogation Request IF is used to request subscription information from the HLR at any time. 9. The Notify Subscriber Data Change response IF is used by the gsmSCF to respond to the HLR about changes in subscriber data. 10. The Any Time Modification ack IF is used by the HLR to provide modified information to the gsmSCF. 1. The response to a CANCEL request in SIP should have the same To tag as the original request. 2. SIP uses a location service to discover the current host(s) where a user is reachable. 3. Registration creates bindings in a location service that associate an address-of-record with contact addresses. 4. SIP provides a mechanism called registration for a user agent to create a binding explicitly. 5. A REGISTER request does not establish a dialog in SIP. 6. The Contact header field in a REGISTER request contains the contact addresses to which SIP requests should be forwarded. 7. Registrations can be removed by specifying an expiration interval of ""0"" for the contact address in a REGISTER request. 8. A successful REGISTER response contains a list of all current bindings. 9. Each user agent is responsible for refreshing its own bindings by sending REGISTER requests before the expiration interval has elapsed. 10. A registrar is a UAS that responds to REGISTER requests and maintains a list of bindings accessible to proxy servers and redirect servers. 1. The LCLS-GlobalCallReference is an optional field that is an OCTET STRING with a size of 13 to 15 octets. 2. The LCLS-Negotiation is a BIT STRING with a size of 2 to 8 bits, used for permission indicators. 3. The BSSMAP-ServiceHandoverList is a sequence that can contain multiple BSSMAP-ServiceHandoverInfo elements. 4. The RANAP-ServiceHandover is an OCTET STRING with a size of 1 octet, containing Service-Handover data. 5. The RadioResourceList is a sequence that can contain multiple RadioResource elements. 6. The PrepareHO-Res is a sequence that includes various optional fields such as handoverNumber, relocationNumberList, an-APDU, multicallBearerInfo, and more. 7. The SelectedUMTS-Algorithms is a sequence that includes optional fields for integrityProtectionAlgorithm, encryptionAlgorithm, and extensionContainer. 8. The ChosenIntegrityProtectionAlgorithm is an OCTET STRING with a size of 1 octet, containing IntegrityProtectionAlgorithm data. 9. The ChosenEncryptionAlgorithm is an OCTET STRING with a size of 1 octet, containing EncryptionAlgorithm data. 10. The ChosenRadioResourceInformation is a sequence that includes optional fields for chosenChannelInfo and chosenSpeechVersion. 1. The Proxy-Authorization header field is used for authentication and should not be combined with other header fields. 2. The Proxy-Require header field indicates proxy-sensitive features that must be supported. 3. The Record-Route header field is used by proxies to force future requests to be routed through them. 4. The Reply-To header field contains a return URI that may be different from the From header field. 5. The Require header field is used by UACs to indicate options that the UAS must support. 6. The Retry-After header field indicates how long a service is expected to be unavailable or when the called party will be available again. 7. The Route header field is used to force routing for a request through a set of proxies. 8. The Server header field contains information about the software used by the UAS. 9. The Subject header field provides a summary or indication of the call's nature. 10. The Supported header field lists the extensions supported by the UAC or UAS. 1. The client transaction starts timer B with a value of 64*T1 seconds when a transport is used. 2. Timer A controls request retransmissions and is reset with a value of 2*T1 when it fires. 3. Retransmissions of the request should occur with intervals that double after each transmission. 4. The client transaction should inform the TU if timer B fires while in the ""Calling"" state. 5. Reception of a provisional response transitions the client transaction to the ""Proceeding"" state. 6. Reception of a response with status code from 300-699 transitions the client transaction to the ""Completed"" state. 7. The client transaction should start timer D with a value of at least 32 seconds when it enters the ""Completed"" state. 8. Retransmissions of the final response in the ""Completed"" state should cause the ACK to be re-passed to the transport layer. 9. The ACK request constructed by the client transaction should contain values equal to the original request. 10. The client transaction should transition to the ""Terminated"" state when timer D fires. 1. The handling of gsmSCF initiated calls in the VLR involves the process CAMEL_ICA_VLR. 2. The handling of mobile calls in the gsmSSF involves various processes and procedures such as CS_gsmSSF, Check_Criteria, Connect_To_Resource, Handle_AC, Handle_ACR, Handle_CIR, Handle_CIR_leg, Complete_FCI_record, Complete_all_FCI_records, Handle_SCI, CSA_gsmSSF, Handle_O_Answer, and Handle_T_Answer. 3. Call duration control is an important aspect of handling mobile calls in the gsmSSF. 4. Audible indicators, such as fixed or variable sequences of tones, can be used for call duration control. 5. The gsmSCF has control over e-values and can instruct the gsmSSF to play tones or provide other charging information. 6. The Procedure Handle_SCI is responsible for handling the gsmSCF control of e-values. 7. The process Tsw_For_SCI manages the Tariff Switch Timers for the gsmSCF control of e-values. 8. The gsmSSF performs specific actions based on different events and signals received during the call processing. 9. The outstanding request counter and rules for CAMEL are used to manage resumptions and track the order of events. 10. The process CS_gsmSSF and associated procedures play a crucial role in the overall handling of mobile calls in the gsmSSF. 1. Reason-Phrase should provide more detailed information about syntax problems, such as a missing Call-ID header field. 2. The 401 Unauthorized response indicates that user authentication is required for the request. 3. The 402 Payment Required status code is reserved for future use. 4. The 403 Forbidden response means that the server understood the request but refuses to fulfill it, and authorization will not help. 5. The 404 Not Found status code is returned when the server has definitive information that the user does not exist at the specified domain. 6. The 405 Method Not Allowed response indicates that the method specified in the request is understood but not allowed for the given address. 7. The 406 Not Acceptable status code is returned when the resource identified by the request can only generate response entities with content characteristics not acceptable according to the Accept header field. 8. The 407 Proxy Authentication Required code is similar to 401 Unauthorized but indicates that the client must authenticate itself with the proxy. 9. The 408 Request Timeout status code is returned when the server could not produce a response within a suitable amount of time. 10. The 410 Gone response means that the requested resource is no longer available at the server and no forwarding address is known. 1. The Basic Call State Model (BCSM) provides a high-level model of activities required to establish and maintain communication paths for users. 2. The Call Control Function (CCF) is responsible for call/service processing and control in the network. 3. Call Party Handling (CPH) Information Flow includes Disconnect Leg, Move Leg, or Split Leg information flows. 4. Call Segments contain one or more legs controlled by the same CS_gsmSSF instance, allowing communication between call parties. 5. Call Segment Associations (CSA) contain one or more call segments, allowing movement of legs within the CSA. 6. Detection Points (DP) are points in processing where notifications and transfer of control can occur. 7. Dialled Service CAMEL Subscription Information (D-CSI) identifies subscribers with originating CAMEL dialled services. 8. Forwarding MSCs are MSCs invoking standardized Call Forwarding or Call Deflection supplementary services. 9. Gateway MLC (GMLC) allows external LCS Clients to request real-time information about a Mobile Station's location. 10. Geodetic Information and Geographical Information define the location of a mobile station, coded according to specific recommendations. 1. The information flows used by CAMEL for GPRS control are described in this section. 2. Each information element (IE) is categorized as Mandatory (M), Conditional (C), Specific conditions (S), or Optional (O). 3. Mandatory IEs must always be included, while Conditional IEs are included if the sending entity has the necessary information. 4. Specific conditions for inclusion of an IE are specified in the description table. 5. Optional IEs may be included or omitted as required by the service logic. 6. The categorization is a functional classification and not a stage 3 classification for the ASN.1 syntax of the protocol. 7. Errors and exceptions to these rules are specified in 3GPP TS 29.002 and TS 29.078. 8. The gprsSSF sends information flows to the gsmSCF for various activities like testing, charging reports, entity release, and event reporting. 9. The information elements in these flows include GPRS reference numbers, charging results, quality of service, active status, and PDP IDs. 10. The flows also contain specific information for different events like detach, PDP context establishment, and change of position. 1. The IF is used for the gsmSCF to send responses to the MS via the HLR for MS initiated IF. 2. The SS User Data IE contains the string that will be sent to the MS. 3. The USSD String IE contains the string that will be sent to the gsmSCF. 4. The Data Coding Scheme IE indicates the characteristics of the USSD string. 5. The Unstructured SS Request ack IF is used for the gsmSCF to send responses to the MS via the HLR for the MS initiated IF. 6. The Unstructured SS Notify ack IF is used for the MS to acknowledge the notification received from the gsmSCF via the HLR. 7. The Process Unstructured SS Data IF is used for the MS to request data from the gsmSCF via the HLR. 8. The Process Unstructured SS Request IF is used for the MS to request data from the gsmSCF via the HLR. 9. The Begin Subscriber Activity IF is used by the HLR to start subscriber activity towards the gsmSCF for USSD purposes. 10. The GPRS interworking architecture involves functional entities such as HLR, SGSN, gprsSSF, and gsmSCF. 1. The Call Attempt Elapsed Time for the Calling Party in the Call Information Report should be set to 0. 2. The Call Stop Time and Call Connected Elapsed Time are requested in the Call Information Report. 3. The Release Cause for the call party is requested in the Call Information Report. 4. The Cancel operation is used to cancel all active requests for Event Report BCSM, Apply Charging Report, and Call Information Report. 5. The Collect Information operation is used to collect additional dialled digits from the calling party and report them to the gsmSCF. 6. The Connect operation is used to route a call to a specific destination. 7. The Continue operation is used to proceed with call processing at the DP where it previously suspended. 8. The Continue With Argument operation is used to continue call processing with modified information at the DP where it previously suspended. 9. The Alerting Pattern, Calling Party's Category, and Carrier information elements are used to provide specific details for call processing. 10. The Service Interaction Indicators indicate the type of service interaction to be applied during call processing. 1. The CUG-FeatureList is a sequence that can contain multiple CUG-Feature elements. 2. The InterCUG-Restrictions field is an OCTET STRING with specific bit values indicating different types of CUG access. 3. The LCS-PrivacyExceptionList is a sequence that can contain multiple LCS-PrivacyClass elements. 4. The ExternalClientList is a sequence that can contain multiple ExternalClient elements. 5. The GMLC-Restriction field is an ENUMERATED type with specific values indicating different GMLC restrictions. 6. The NotificationToMSUser field is an ENUMERATED type with specific values indicating different notification options for the MS user. 7. The ServiceTypeList is a sequence that can contain multiple ServiceType elements. 8. The MOLR-List is a sequence that can contain multiple MOLR-Class elements. 9. The ZoneCodeList is a sequence that can contain multiple ZoneCode elements. 10. The DeleteSubscriberDataArg is a sequence that can contain multiple optional elements for deleting subscriber data. 1. The S6a and S6d interfaces enable the transfer of subscriber data between the MME/SGSN and the HSS. 2. The Update Location Procedure is used to update location information in the HSS. 3. The procedure is invoked by the MME/SGSN to inform the HSS about the serving node and update user subscription data. 4. The Update Location Procedure is mapped to the Diameter commands ULR/ULA. 5. The Update Location Request includes information elements such as IMSI, Supported Features, Terminal Information, ULR Flags, Visited PLMN Id, Equivalent PLMN List, RAT Type, SGSN number, Homogeneous Support of IMS Voice Over PS Sessions, V-GMLC address, Active APN, UE SRVCC Capability, MME Number for MT SMS, SMS Register Request, SGs MME identity, Coupled node's Diameter identity, Adjacent PLMNs, and Supported Services. 6. The Update Location Answer includes information elements such as Supported Features and Result Code/Experimental Result. 7. The S6a interface is used for location changes of the MME, while the S6d interface is used for location changes of the SGSN. 8. The procedures, message parameters, and protocol are similar between S6a and S6d. 9. The S13 and S13' interfaces have identical procedures, message parameters, and protocol. 10. The Update Location Procedure is used to update location information and user data in the HSS. 1. MO-SMS and MT-SMS services have different armed and disarmed events: O_SMS_Submission, O_SMS_Failure for MO-SMS and T_SMS_Delivery, T_SMS_Failure for MT-SMS. 2. Charging data for MO-SMS is stored in 'MOSMSRecord' CDR or S-SMO-CDR, while for MT-SMS it is stored in 'MTSMSRecord' or S-SMT-CDR. 3."
"The Int_SMS_Failure signal in state Waiting_For_Instructions is only received for MO-SMS service when a MS detach event occurs before the gsmSCF gives instruction to continue SM processing. 4. When SM submission or failure event occurs, both MO-SMS events are disarmed. When SM delivery or failure event occurs, both MT-SMS events are disarmed. 5. For MO-SMS service, the 'MOSMSRecord' or 'S-SMO-CDR' is closed. For MT-SMS service, the 'MTSMSRecord' or 'S-SMT-CDR' is closed. 6. Information flows are used by CAMEL for SMS control and are categorized as Mandatory (M), Conditional (C), Optional (O), Specific conditions (S), mutually Exclusive (E), or not applicable (-). 7. The gsmSCF sends information flows to the gsmSSF or gprsSSF for event reporting, initial DP SMS, continuing SMS, and furnishing charging information. 8. The gsmSSF or gprsSSF sends information flows to the gsmSCF for connecting SMS, continuing SMS, and releasing SMS. 9. The Connect SMS information flow includes the calling party's number, destination subscriber number, and SMSC address. 10. The Furnish Charging Information SMS information flow includes the FCI Billing Charging Characteristics and FCIBCCCAMEL Sequence 1, which contains free format data to be inserted in the CAMEL logical call record. 1. The document specifies the updated sections of the eoTCAP TDR File Structure v.7.0. 2. The updated sections include common fields, MAP fields, CAP fields, INAP fields, and common measures. 3. The document lists the compatible FIDs for different protocol layers such as CAP, MAP, INAP, TCAP-AP, and more. 4. The eoTCAP DR content includes scenarios for voice calls, location updates, data sessions, short message services, and supplementary services. 5. The DR file structure consists of common fields, layer type, data record type, violation, timeout, source and destination IP addresses, network node details, signalling point details, calling and called party numbers, payment plan, and linkset name. 6. The start and end date and time fields indicate the time interval of the eoTCAP TDRs within the file. 7. The DR generation type specifies the type of eoTCAP transaction data record. 8. The binary format of the DR file stores data records in a proprietary format. 9. The MCLS table and DWH dimension provide additional information for aggregation and analysis. 10. The eoLive aggregation role determines how the data is aggregated in the eoLive application. 1. The media type and subtype for AMR and AMR-WB go in the SDP ""m="" and ""a=rtpmap"" attributes, respectively. 2. The RTP clock rate for AMR is 8000 and for AMR-WB is 16000. 3. The number of channels for AMR and AMR-WB can be explicitly set or omitted, with a default value of 1. 4. The ""ptime"" and ""maxptime"" parameters go in the SDP ""a=ptime"" and ""a=maxptime"" attributes. 5. Any remaining parameters go in the SDP ""a=fmtp"" attribute. 6. Each combination of RTP payload transport format configuration parameters is unique and not compatible with any other combination. 7. The ""mode-set"" parameter can be used to restrict the set of active AMR/AMR-WB modes used in a session. 8. The ""mode-change-period"" and ""mode-change-capability"" parameters are used for mode switching in gateway scenarios. 9. The ""max-red"" parameter limits the usage of redundancy in the stream. 10. Unknown parameters in an offer are removed in the answer. 1. If multiple Private User Identities share a Public User Identity, the HSS will keep the Public User Identity registered and remove any associated S-CSCF Restoration Information. 2. If the HSS decides not to keep the S-CSCF name, the Experimental-Result will indicate DIAMETER_SUCCESS_SERVER_NAME_NOT_STORED. 3. The HSS will check if each Public User Identity in the request is currently registered with one or more Private User Identities. 4. If no Public User Identities are specified in the request, the HSS will check if each Public User Identity associated with the Private User Identity in the request is currently registered. 5. If only one Private User Identity associated with a Public User Identity is registered, the HSS will set the Public User Identity as Not Registered and clear the associated S-CSCF name. 6. If multiple Private User Identities share a Public User Identity that is registered, the HSS will keep the Public User Identity as Registered. 7. If the Server-Assignment-Type indicates NO_ASSIGNMENT, the HSS will check if the Public Identity is assigned to the requesting S-CSCF. If not, the Result-Code will be set to DIAMETER_UNABLE_TO_COMPLY. 8. If the Server-Assignment-Type indicates AUTHENTICATION_FAILURE or AUTHENTICATION_TIMEOUT, the HSS will keep the registration state of the Public User Identity and clear the associated S-CSCF name if the Public User Identity is not registered. 9. If the HSS cannot fulfill the request due to a database error, the Result-Code will be set to DIAMETER_UNABLE_TO_COMPLY. 10. In network-initiated de-registration by the HSS, the HSS will change the state of the Public Identities to Not Registered and notify the S-CSCF of the identities to be de-registered. 1. Field values, parameter names, and parameter values in SIP are case-insensitive, except for quoted strings. 2. Compact forms can be used to represent common header field names in abbreviated form in order to reduce message size. 3. Header fields that appear in a message not matching their category (request or response) should be ignored. 4. The Content-Type header field specifies the Internet media type of the message body. 5. The Content-Length header field indicates the length of the message body in bytes. 6. SIP messages can be carried over unreliable datagram protocols like UDP. 7. The Call-ID header field acts as a unique identifier for grouping messages. 8. The From header field indicates the logical identity of the initiator of the request. 9. The To header field specifies the desired recipient of the request. 10. The Max-Forwards header field limits the number of hops a request can transit. 1. The document contains a list of change requests (CT#) for different versions of a specification. 2. The changes include updates, corrections, clarifications, and additions to various features and functionalities. 3. Some changes address specific issues like error handling, access restrictions, and support for new technologies. 4. The changes are categorized by CT#, CP#, and release version. 5. The document covers a timeline from 2016 to 2023, with multiple releases and updates. 6. The changes aim to improve network performance, data handling, and subscriber management. 7. Some changes involve the addition or removal of AVPs (Attribute Value Pairs) in the Diameter protocol. 8. The updates address issues related to network access, data mode, load control, and communication patterns. 9. The changes also cover topics like emergency services, monitoring events, and support for new RATs (Radio Access Technologies). 10. The document emphasizes the importance of alignment, clarification, and consistency in the specification. 1. The CAMEL Subscription Info Withdraw IE is used to delete all CSIs from the subscriber data in the VLR. 2. The Specific CSI Withdraw IE is used to delete specific elements of CAMEL Subscription Info from the VLR. 3. The Insert Subscriber Data IF is used by the HLR to update the VLR with subscriber data. 4. The Provide Subscriber Info IF is used by the HLR to request information from the VLR about a subscriber. 5. The Provide Roaming Number IF is used by the HLR to request a roaming number from the VLR. 6. The Insert Subscriber Data ack IF is used by the VLR to indicate the result of the Insert Subscriber Data IF to the HLR. 7. The Provide Subscriber Info ack IF is used by the VLR to provide requested information to the HLR. 8. The Update Location IF is used by the VLR to provide information about supported CAMEL phases to the HLR. 9. The Restore Data IF is used by the VLR to provide information about supported CAMEL phases to the HLR. 10. The Send Routeing Info ack IF is used by the HLR to transfer routeing information to the GMSC. 1. If the MME or SGSN does not support a feature, the HSS will not send related information to that MME or SGSN. 2. The HSS may store indications of unsupported features and not send further updates to the MME or SGSN. 3. Different features are applicable for different command pairs and interfaces. 4. The HSS shall not send SMS information to the MME if it does not support SMS in MME feature. 5. The HSS shall not send SMS information to the SGSN if it does not support SMS in SGSN feature. 6. The HSS shall not send LCS information to the SGSN if it does not support certain LCS features. 7. The HSS shall not send Gdd information to the SGSN if it does not support Gdd interface for SMS in SGSN feature. 8. The HSS shall not send ProSe subscription data to the MME if it does not support ProSe capability feature. 9. The HSS shall not send P-CSCF restoration commands if the MME or SGSN does not support P-CSCF restoration feature. 10. The HSS shall not send Reset-ID updates to the MME or SGSN if they do not support Reset-IDs feature. 1. The SGSN and VLR address lists contain the addresses of affected subscribers after a restart. 2. The HLR uses the MAP process to notify the VLR and SGSN about the restart. 3. The VLR and SGSN use the MAP process to handle the notification and update the affected IMSI records. 4. Updates that require local changes in the VLR or SGSN should be performed immediately. 5. Updates that require signaling interaction with other nodes should be deferred until the next authenticated radio contact. 6. The CSS must periodically back up data to non-volatile memory. 7. Restoration procedures are triggered for affected IMSI records after a CSS fault. 8. The gsmSCF is notified about the successful completion of a Mobility Management event. 9. The VLR or SGSN reports the event to the gsmSCF using the MAP process. 10. Macros are used to transfer subscriber data and coordinate operation and maintenance procedures. 1. The Framed-IP-Address AVP is only included for GPRS-IMS-Bundled authentication scheme and when the User's IP Address is IPv4. 2. The Framed-IPv6-Prefix AVP is only included for GPRS-IMS-Bundled authentication scheme and when the User's IP Address is IPv6. 3. The Framed-Interface-Id AVP is only included for GPRS-IMS-Bundled authentication scheme, when the User's IP Address is IPv6, and when the Framed-IPv6-Prefix AVP alone is not unique for the user. 4. The Digest Realm AVP corresponds to the Realm parameter defined in RFC 7616. 5. The Digest Algorithm AVP contains the algorithm, which is typically ""MD5"" if not specified. 6. The Digest QoP AVP contains the Quality of Protection as defined in RFC 7616. 7. The Digest HA1 AVP contains the H(A1) for the ""MD5"" algorithm as defined in RFC 7616. 8. The Alternate Digest Algorithm AVP contains an alternate algorithm as defined in RFC 7616. 9. The Alternate Digest HA1 AVP contains the H(A1) for the alternate algorithm as defined in RFC 7616. 10. The HSS follows a specific order of steps for processing requests, including checking user identities, authentication schemes, registration status, and downloading authentication information. 1. The S6a/S6d interface protocol reuses Diameter AVPs from existing Diameter Applications. 2. The M-bit in the AVP header indicates whether support of the AVP is required. 3. The V-bit in the AVP header indicates whether the optional Vendor-ID field is present. 4. AVPs from the Diameter base protocol specified in IETF RFC 6733 do not need to be supported. 5. The Service-Selection AVP is referenced in IETF RFC 5778 and is used in S6a/S6d. 6. The 3GPP-Charging-Characteristics AVP holds charging characteristics data for EPS APN Configuration and PDP context. 7. The Supported-Features AVP is referenced in 3GPP TS 29.229 and is used in S6a/S6d. 8. The Served-Party-IP-Address AVP holds the PDN IP Address of the user. 9. The QoS-Class-Identifier AVP is referenced in 3GPP TS 29.212 and is used in S6a/S6d. 10. The MIP6-Agent-Info AVP is referenced in IETF RFC 5447 and is used in S6a/S6d. 1. The number of SCCP messages is measured in the ""NUMOF_SCCPMSG"" field. 2. The number of SCCP forward messages is measured in the ""NUMOF_TXSCCP_MSGS"" field. 3. The number of SCCP backward messages is measured in the ""NUMOF_RXSCCP_MSGS"" field. 4. The number of answered calls is measured in the ""ANSWERED_CALL"" field. 5. The number of dropped calls is measured in the ""DROPPED_CALL"" field. 6. The SMS payload size is measured in the ""MAP_PAYLOAD_SZ"" field. 7. The number of MO SMS messages is measured in the ""MAP_NUMBER_OF_MO_SMS_MESSAGES"" field. 8. The success of MO SMS messages is measured in the ""MAP_MO_SMS_SUCC"" field. 9. The number of MT SMS messages is measured in the ""MAP_NUMBER_OF_MT_SMS_MESSAGES"" field. 10. The success of MT SMS messages is measured in the ""MAP_MT_SMS_SUCC"" field. 1. TCAPOP Voice Message is available for assistance. 2. TCAPOP Cancel can be used to terminate a process. 3. TCAPOP Security is a feature for ensuring secure communication. 4. TCAPOP Report assist Termination provides information about the termination of a process. 5. TCAPOP Temporary Handover allows for temporary transfer of control. 6. TCAPOP Automatic Code Gap helps in managing code gaps automatically. 7. TCAPOP When Party Free indicates when a party is available. 8. TCAPOP Indicate Information Provided notifies about the provision of information. 9. TCAPOP Indicate Information Waiting indicates that information is still pending. 10. TCAPOP Play Announcement and Collect Digits is used to play an announcement and collect user input. 1. When a subscriber registers a forwarded-to number, the HLR does not perform any checks or translations. 2. When the Call Deflection supplementary service is invoked, the VLR does not perform any checks or translations. 3. The Terminating CAMEL Subscription Information (T-CSI) includes the TDP List, gsmSCF address, Service Key, Default Call Handling, DP criteria, CAMEL Capability Handling, CSI state, and notification flag. 4. The TDP List in the T-CSI indicates the detection points for triggering. 5. The gsmSCF address in the T-CSI indicates the address used to access the gsmSCF for a subscriber. 6. The Service Key in the T-CSI indicates the service logic to be used by the gsmSCF. 7. The Default Call Handling in the T-CSI determines whether the call should be released or continued in case of errors or call gapping. 8. The DP criteria in the T-CSI determines whether the gsmSSF should request instructions from the gsmSCF. 9. The CAMEL Capability Handling in the T-CSI indicates the requested phase of CAMEL for the service. 10. The notification flag in the T-CSI determines whether a change in the T-CSI should trigger a notification on change of subscriber data. 1. The URI placed into the Record-Route header field must be a SIPS URI. 2. If the request was not received over TLS, the proxy must insert a Record-Route header field. 3. If a proxy receives a request over TLS but generates a request without a SIPS URI in the Request-URI or topmost Route header field value, it must insert a Record-Route header field that is not a SIPS URI. 4. A proxy at a security perimeter must remain on the perimeter throughout the dialog. 5. If the URI placed in the Record-Route header field needs to be rewritten when it passes back through in a response, the URI must be distinct enough to locate at that time. 6. The proxy may include parameters in the Record-Route header field value. 7. If a proxy needs to be in the path of any type of dialog, it should add a Record-Route header field value to every request with a method it does not understand. 8. The URI a proxy places into a Record-Route header field is only valid for the lifetime of any dialog created by the transaction in which it occurs. 9. Endpoints must not use a URI obtained from a Record-Route header field outside the dialog in which it was provided. 10. Record-routing should only be used if required for a particular service. 1. The MAP_SEND_END_SIGNAL service is used to inform MSC-B that the radio path has been established and MSC-A will retain control of the call until it is cleared. 2. The MAP_PROCESS_ACCESS_SIGNALLING service is used to pass information received on the A-interface or Iu-interface from MSC-B to MSC-A. 3. The MAP_FORWARD_ACCESS_SIGNALLING service is used to pass information from MSC-A to MSC-B to be forwarded to the A-interface or Iu-interface of MSC-B. 4. The MAP_PREPARE_SUBSEQUENT_HANDOVER service is used to inform MSC-A that a handover or relocation is required to either MSC-A or another MSC (MSC-B'). 5. The MAP_ALLOCATE_HANDOVER_NUMBER service is used between MSC and VLR to request a handover number. 6. The parameters used in these services include Invoke Id, AN-APDU, Provider error, User error, and various other specific parameters depending on the service. 7. The AN-APDU parameter is used to define the Application Protocol Data Unit. 8. The User error parameter is used to define specific errors related to the nature of the fault. 9. The Provider error parameter is used to define errors related to the service provider. 10. The services mentioned in the text are confirmed services, meaning they require a response or confirmation from the receiving party. 1. The parameter indicates that the call will potentially be optimally routed if the GMSC and HLR are not in the same PLMN. 2. The parameter indicates the phase of OR supported by the GMSC. 3. The parameter indicates the reason for call forwarding, such as a busy subscriber or unreachable mobile subscriber. 4. If the forwarding subscriber requests the GMSC to resume handling the call, the GMSC will interrogate the HLR for forwarding information. 5. The subscriber is identified as having originating CAMEL services or dialled services. 6. The subscriber is identified as having terminating CAMEL services in the GMSC or VMSC. 7. The subscriber is identified as having originating or terminating IP Multimedia Core Network CAMEL services. 8. The CCBS feature parameter contains information related to a certain CCBS request, including the CCBS index, B-subscriber number, B-subscriber subaddress, and basic service group code. 9. The UU Data parameter includes User-To-User Data. 10. The parameter indicates the number portability status of the subscriber. 1. Deactivation and clearing of a previous PDP Context is necessary before processing exceptional conditions. 2. The interface is idled when no activity is detected. 3. The SGSN analyzes GPRS-CSI to determine the appropriate actions to take. 4. APN and GGSN selection procedure is performed for primary PDP context, but not for secondary PDP context. 5. The SGSN checks for operator determined barring categories and invokes them if necessary. 6. The SGSN ensures that an already active PDP context is not reactivated. 7. GGSN address is derived from the Access Point Name by interrogation of a DNS. 8. PDP context is established at the MS and the SGSN. 9. PDP context can be deactivated by the MS, GGSN, or due to a routing area update. 10. CAMEL control of GPRS can be done through Scenario 1 or Scenario 2, but not both at the same time. 1. The Alternate-Digest-HA1 AVP is defined in the same way as Digest-HA1 AVP according to IETF RFC 7616. 2. The Visited-Network-Identifier AVP helps the HSS identify the visited network using an identifier. 3. The Public-Identity AVP contains the public identity of a user in the IMS, either in SIP URL or TEL URL format. 4. The Server-Name AVP contains a SIP-URL used to identify a SIP server, such as an S-CSCF name. 5. The Server-Capabilities AVP provides information to assist the I-CSCF in selecting an S-CSCF. 6. The Mandatory-Capability AVP represents a single mandatory capability or a set of capabilities of an S-CSCF. 7. The Optional-Capability AVP represents a single optional capability or a set of capabilities of an S-CSCF. 8. The User-Data AVP contains the user data required to provide service to a user. 9. The SIP-Number-Auth-Items AVP indicates the number of authentication vectors requested or provided by the S-CSCF. 10. The SIP-Authentication-Scheme AVP indicates the authentication scheme used in the authentication of SIP messages. 1. Implementers should be aware that secure MIME may interfere with certain network intermediaries that rely on viewing or modifying SIP message bodies. 2. The PGP mechanism for encrypting SIP message headers and bodies described in RFC 2543 has been deprecated. 3. S/MIME certificates for end-users assert that the holder is identified by an end-user address, typically an email address. 4. Certificates are associated with keys used to sign or encrypt SIP message bodies. 5. Users should acquire certificates from known public certificate authorities or create self-signed certificates. 6. There are few centralized directories that distribute end-user certificates, but users should publish their certificates in appropriate public directories. 7. SIP can be used to distribute public keys by including the certificate in the CMS SignedData message. 8. When receiving a request with an S/MIME CMS body, the recipient should validate the certificate and compare it to the From header field. 9. If the certificate cannot be verified or does not correspond to the From header field, the recipient must notify the user and request explicit permission before proceeding. 10. S/MIME bodies in SIP messages should be signed with only one certificate, and multiple signatures should not be used. 1. The document outlines various criteria and information related to CAMEL (Customized Applications for Mobile network Enhanced Logic) services. 2. It includes details about DP criteria, gsmSCF address, service key, default call handling, CAMEL capability handling, CSI state, and notification flag. 3. The network CAMEL service information (N-CSI) and translation information flag CAMEL subscription information (TIF-CSI) are also discussed. 4. Terminating CAMEL subscription information (T-CSI) and VMSC terminating CAMEL subscription information (VT-CSI) are described, including their respective components. 5. The document provides a description of CAMEL BCSMs (Basic Call State Models) and their handling in various call scenarios. 6. It explains the leg handling process, including leg creation, continuation, release, and movement. 7. Procedures for CAMEL are outlined, including the overall SDL (Specification and Description Language) architecture and handling of mobile originated, mobile terminating, forwarded, and gsmSCF initiated calls. 8. Information flows between gsmSSF (gsm Service Switching Function) and gsmSCF are described, including activities like call information reporting, call gap, call duration control, and call information request. 9. The document also covers the handling of location updating, data restoration, North American carrier information, and trunk originated calls. 10. It emphasizes the importance of cross-phase compatibility and provides a procedure for CAMEL_Provide_Subscriber_Info. 1. The gsmSSF or gprsSSF can handle mobile originating and mobile terminating SMS. 2. The Int_Invoke SMS_SSF signal determines which TDP to arm. 3. For MO-SMS service, the SMS_Collected_Info TDP is armed, and for MT-SMS service, the SMS_Delivery_Request TDP is armed. 4. The Int_SMS_Failure signal is received only for MO-SMS service when a MS detach event occurs before SMS_SSF is invoked. 5. The SMSC Address and Destination Subscriber Number can be received in CAP ConnectSMS for MO-SMS service. 6. Different events can be armed or disarmed for MO-SMS and MT-SMS services. 7. Charging data can be placed in specific CDRs for both MO-SMS and MT-SMS services. 8. The Int_SMS_Failure signal can be received for MO-SMS service when a MS detach event occurs before the gsmSCF gives instructions to continue SM processing. 9. MO-SMS events are disarmed when SM submission or failure event occurs, and MT-SMS events are disarmed when SM delivery or failure event occurs. 10. For MO-SMS service, the 'MOSMSRecord' or 'S-SMO-CDR' is closed, and for MT-SMS service, the 'MTSMSRecord' or 'S-SMT-CDR' is closed. 1. The 'Open GPRS Dialogue' task box includes tasks for starting a GPRS dialogue, such as allocating a GPRS Reference Number and resources. 2. The 'Terminate GPRS Dialogue' task box includes tasks for closing a GPRS dialogue. 3. The 'Process GPRS_Dialogue_Handler' handles TC_End request primitives from process gprsSSF and sends TC_End TC Messages to gsmSCF under certain conditions. 4. The 'Handle_AC_GPRS' procedure is called with input parameters 'Session' and 'PDP Id' to execute the Apply Charging GPRS procedure for the specified session and PDP context. 5. The 'Handle_ACR_GPRS' procedure is called with input parameters 'Session', 'PDP Id', and 'Session + PDPs' to execute the Apply Charging Report GPRS procedure for the specified session and PDP context. 6. The 'Complete_FCI_Record_GPRS' procedure is called with input parameters 'Session', 'PDP Id', and 'Session + PDPs' to execute the Complete_FCI_Record_GPRS procedure for the specified session and PDP context. 7. The 'Handle_SCI_GPRS' procedure handles e-parameters sent by the gsmSCF for the session and individual PDP contexts. 8. The 'Handle_PDP_Acknowledgement' procedure is called when an event occurs that may signal the activation of a PDP context. 9. GPRS duration and volume control is managed through timers and information flows between the gprsSSF and gsmSCF. 10. The TC guard timer is used to supervise the response from the gsmSCF on the Apply Charging Report GPRS procedure, and if it expires, the gprsSSF may close the TC dialogue. 1. The media type for the AMR codec is allocated from the IETF tree and covers both real-time and non-real-time transfers. 2. The AMR media type registration includes optional parameters for RTP transfer, such as octet-align and mode-set. 3. The mode-set parameter restricts the active codec mode set to a subset of all modes. 4. The mode-change-period parameter specifies the frame-block period at which codec mode changes are allowed for the sender. 5. The mode-change-capability parameter indicates if the client is capable of restricting the mode change period. 6. The maxptime parameter defines the maximum amount of media that can be encapsulated in a payload packet. 7. The crc parameter determines if frame CRCs should be included in the payload. 8. The robust-sorting parameter determines if robust payload sorting should be used. 9. The interleaving parameter indicates if frame-block level interleaving should be used. 10. The AMR-WB media type registration follows a similar structure to the AMR media type registration. 1. The Mobile Application Part (MAP) protocol uses Abstract Syntax Notation One (ASN.1) to define its Abstract Syntax, Operations, and Errors. 2. The Abstract Syntax encompasses all Operations and Errors identified by the various MAP subsystem numbers. 3. The Abstract Syntax is defined for all interfaces except for the A- and B-interfaces. 4. The encoding rules for the Abstract Syntaxes are the Basic Encoding Rules for ASN.1. 5. The definite form is used for length encoding, with the short form used for lengths less than 128 octets. 6. OCTET STRING and BIT STRING values must be encoded in a primitive form. 7. Empty constructors, such as an empty SEQUENCE type, are allowed in the encoding. 8. The mapping of OPERATION and ERROR to TC components is defined in ETS 300 287. 9. The class of an operation is specified in the ASN.1 operation definition. 10. Class 1 operations include RESULT and ERROR in their ASN.1 definitions. 1. The MAP_PREPARE_HANDOVER service is used for handing over or relocating a call from one MSC to another. 2. The service includes various parameters such as Target Cell Id, Target RNC Id, IMSI, and Encryption Information. 3. The service can be used for handovers between GSM and UMTS networks. 4. The service includes parameters for GSM and UMTS algorithms, radio resource information, and AN-APDU. 5. The service can support multiple bearers and includes parameters for RAB ID and GERAN Classmark. 6. The service includes parameters for BSSMAP and RANAP service handover, Iu codecs, and trace propagation. 7. The service can include parameters for LCLS (Local Call Control in a Single MSC) and CSG (Closed Subscriber Group) subscription data. 8. The MAP_SEND_END_SIGNAL service is used to indicate that the radio path has been established and resources can be released. 9. The service includes the AN-APDU parameter. 10. The MAP_PROCESS_ACCESS_SIGNALLING service is used to pass information received on the A-interface or Iu-interface from MSC-B to MSC-A. 1. The SS-EventList defines actions for specific SS-Code values in CAMEL Phase 3. 2. The O-CSI sequence contains information related to call handling and capabilities. 3. The O-BcsmCamelTDPDataList contains information about trigger detection points for CAMEL Phase 2. 4. The DestinationNumberCriteria sequence includes criteria for matching destination numbers. 5. The BasicServiceCriteria sequence contains criteria for basic service codes. 6. The CallTypeCriteria is an enumerated type for different call types. 7. The O-CauseValueCriteria sequence includes criteria for cause values. 8. The T-BCSM-CAMEL-TDP-Criteria sequence contains criteria for trigger detection points in CAMEL Phase 4. 9. The SMS-CSI sequence includes information about SMS handling and capabilities. 10. The MobilityTriggers sequence contains mobility management events for CS and PS domains. 1. The parameter indicates user consent availability for MDT activation. 2. The parameter is used by the VLR, SGSN, and IWF, but not by the CSS. 3. It indicates whether the subscription is for PS Only and permits CS service access only for SMS. 4. It indicates whether the HSS allows SMS to be provided by SGSN over NAS. 5. It indicates the possibility of activating integrity protection of the user plane when GERAN is used. 6. It suggests a DL-Buffering Packet Count for extended buffering of downlink packets at the SGW for High Latency Communication. 7. It contains a list of subscribed Reset-IDs. 8. It contains the subscribed eDRX cycle length, along with the applicable RAT type. 9. It indicates whether IAB operation is authorized for the UE. 10. It indicates regional subscription restrictions or conflicts. 1. The document provides a detailed description of procedures and information flows for various CAMEL services, including GPRS and SMS. 2. The architecture of CAMEL involves several functional entities and interfaces for communication between them. 3. CAMEL Subscriber Data includes information such as gsmSCF address, service key, default handling, and notification flags. 4. The state models for SMS and SS notifications outline the different stages and actions involved in handling these services. 5. Procedures for mobile originating and mobile terminating SMS involve actions in the MSC/SGSN, VLR, and gsmSSF/gprsSSF. 6. Information flows between gsmSSF/gprsSSF and gsmSCF include events, initial DPs, and actions like connect, continue, release, and reset timer. 7. Information flows between HLR and VLR/SGSN include subscriber data deletion and insertion. 8. Information flows between MSC and VLR include continuing CAMEL SMS handling and sending information for MO SMS. 9. Information flows between VLR and MSC include invoke SS results and sending information for incoming calls. 10. Mobility management procedures for CS and GPRS subscribers involve triggers, gsmSCF addresses, service keys, and notification flags. 1. References can be specific or non-specific, with subsequent revisions only applying to specific references. 2. Non-specific references to 3GPP documents imply the latest version in the same Release as the present document. 3. The present document includes various 3GPP technical specifications related to services and system aspects. 4. The document also references ETSI specifications for ISDN and Signalling System No.7. 5. Definitions and abbreviations are provided to clarify the terms used in the document. 6. Basic Call State Model (BCSM) outlines the activities required to establish and maintain communication paths. 7. Call Control Function (CCF) provides call/service processing and control in the network. 8. Call Party Handling (CPH) Information Flow includes Disconnect Leg, Move Leg, and Split Leg information flows. 9. Call Segments contain one or more legs controlled by the same CS_gsmSSF instance. 10. GSM Service Control Function (gsmSCF) contains the CAMEL service logic for implementing OSS. 1. End-user certificates are limited due to the lack of a consolidated authority, but users should acquire certificates from known public certificate authorities. 2. Self-signed certificates can be used as an alternative, but their implications are explored further in Section 26.4.2. 3. There are few centralized directories that distribute end-user certificates, but certificate holders should publish their certificates in appropriate public directories. 4. Users should support a mechanism for importing certificates discovered in public directories corresponding to the target URIs of SIP requests. 5. SIP can be used to distribute public keys by including the certificate in the CMS SignedData message in S/MIME for SIP. 6. When receiving a request with an S/MIME CMS body that includes a certificate, the recipient should validate the certificate and compare the subject to the From header field of the request. 7. If the certificate cannot be verified or does not correspond to the From header field, the recipient must notify the user and request explicit permission before proceeding. 8. When sending a response with an S/MIME body, the sender should structure the body as an S/MIME 'multipart/signed' CMS SignedData body. 9. When receiving a response with an S/MIME CMS body that includes a certificate, the recipient should validate the certificate and compare the subject to the To field of the response. 10. If the certificate cannot be verified or does not correspond to the To header field, the recipient must notify the user and request explicit permission before proceeding. 1. The package ""ss-InvocationNotificationPackage-v3"" facilitates Supplementary Service invocation notification procedures between the MSC, gsmSCF, and HLR. 2. The package ""setReportingStatePackage-v3"" enables procedures between the HLR and VLR to set the reporting state. 3. The package ""statusReportPackage-v3"" includes operations for reporting call results and events between the VLR and HLR. 4. The package ""remoteUserFreePackage-v3"" allows the HLR to indicate to the VLR that the remote user is free. 5. The package ""callCompletionPackage-v3"" facilitates subscriber control of call completion services between the VLR and HLR. 6. The package ""locationSvcGatewayPackage-v3"" includes operations for location service gateway procedures between the GMLC and HLR. 7. The package ""locationSvcEnquiryPackage-v3"" enables location service enquiry procedures between the GMLC and MSC, and between the GMLC and SGSN. 8. The package ""locationSvcReportingPackage-v3"" includes operations for location service enquiry procedures between the MSC and GMLC, and between the SGSN and GMLC. 9. The package ""ist-AlertingPackage-v3"" facilitates alerting procedures between the MSC or Gateway MSC and HLR. 10. The package ""serviceTerminationPackage-v3"" enables immediate service termination procedures between the HLR and Visited MSC or Gateway MSC. 1. The provided text contains a list of operation names and their corresponding values in a certain system. 2. The operations are related to various functionalities such as call signaling, SMS handling, subscriber information, and error reporting. 3. Each operation has a unique value assigned to it for identification purposes. 4. The text also includes error codes and additional error reasons for specific operations. 5. There are fields that capture timestamps, addresses, and other relevant information related to the operations. 6. The CAP layer is mentioned, which is responsible for handling certain operations. 7. The CAP layer also has its own error codes and additional error reasons. 8. The text mentions various causes for call failures, SMS failures, and GPRS failures. 9. The values and names mentioned in the text are used to represent specific functionalities and errors in the system. 10. The provided information is technical in nature and relates to the inner workings of a specific system. 1. The document provides protocol details for the Sh interface based on the Diameter protocol. 2. The Sh interface is not subject to approval by the 3GPP Organizational Partners and should not be implemented. 3. The document defines the Diameter application for the Sh interface, including command codes and AVP values. 4. The User-Data-Request (UDR) command is used to request user data. 5. The User-Data-Answer (UDA) command is used to provide user data in response to a UDR request. 6. The Profile-Update-Request (PUR) command is used to update user profiles. 7. The Profile-Update-Answer (PUA) command is used to indicate the success or failure of a profile update. 8. The Subscribe-Notifications-Request (SNR) command is used to subscribe to notifications. 9. The Subscribe-Notifications-Answer (SNA) command is used to indicate the success or failure of a notification subscription. 10. The document defines various AVPs (Attribute-Value Pairs) used in the Sh interface, such as User-Identity, MSISDN, User-Data, and Service-Indication. 1. The KASME field is an octet string with a size of 32. 2. The RequestingNodeType is an enumerated type with various values, including vlr, sgsn, s-cscf, bsf, gan-aaa-server, wlan-aaa-server, mme, and mme-sgsn. 3. The CheckIMEI-Arg sequence includes the IMEI, requestedEquipmentInfo, and optional extensionContainer. 4. The CheckIMEI-Res sequence includes the equipmentStatus, bmuef, and optional extensionContainer. 5. The RequestedEquipmentInfo is a bit string with equipmentStatus and bmuef as its possible values. 6. The UESBI-Iu sequence includes uesbi-IuA and uesbi-IuB, both of which are bit strings. 7. The EquipmentStatus is an enumerated type with permittedListed, prohibitedListed, and trackingListed as its values. 8. The InsertSubscriberDataArg sequence includes various optional parameters such as imsi, SubscriberData components, extensionContainer, and more. 9. The EDRX-Cycle-Length-List is a sequence of EDRX-Cycle-Length values. 10. The EPS-SubscriptionData sequence includes various optional parameters such as apn-oi-Replacement, rfsp-id, ambr, apn-ConfigurationProfile, and more. 1. The Release Call function does not require any additional actions to be resumed. 2. The process CS_gsmSSF and its associated procedures are depicted in multiple figures. 3. The process gsmSSF_SSME_FSM is instantiated for each Call Gap information flow received from a gsmSCF. 4. The process CSA_gsmSSF and its associated procedures are specific to an opened transaction between the CSA_gsmSSF and the gsmSCF. 5. Assisting case involves the processes CAMEL_Assisting_MSC and Assisting_gsmSSF, with detailed error handling specified in another document. 6. The procedure CAMEL_Provide_Subscriber_Info is called during retrieval of routing information or as a result of Any Time Interrogation from the gsmSCF. 7."
"CAMEL specific handling of location updating and data restoration is performed by the VLR and HLR based on the negotiated CAMEL phase. 8. Cross phase compatibility between the gsmSSF and gsmSCF is achieved by using the CAP phase corresponding to the negotiated CAMEL phase on the HLR-VLR interface. 9. North American Carrier Information is handled by the gsmSSF when both the HPLMN and VPLMN/IPLMN are in North America. 10. Trunk originated calls are handled by the procedures CAMEL_TOC_Dialled_Services, CAMEL_TOC_MSC_INIT, CAMEL_NDS_TOC_INIT, and CAMEL_TOC_LEG1_MSC. 1. The HLR uses the ""Delete Subscriber Data"" information flow to remove CAMEL subscription data from the VLR. 2. The ""Insert Subscriber Data"" information flow is used by the HLR to update the VLR with subscriber data. 3. The ""Provide Subscriber Info"" information flow is used by the HLR to request information from the VLR about the subscriber's state, location, and other details. 4. The ""Provide Roaming Number"" information flow is used by the HLR to request a roaming number from the VLR. 5. The VLR uses the ""Insert Subscriber Data ack"" information flow to inform the HLR about the result of the Insert Subscriber Data operation. 6. The VLR uses the ""Provide Subscriber Info ack"" information flow to provide the requested subscriber information to the HLR. 7. The VLR uses the ""Update Location"" information flow to inform the HLR about the supported CAMEL phases. 8. The VLR uses the ""Restore Data"" information flow to provide information about supported CAMEL phases to the HLR. 9. The HLR uses the ""Send Routeing Info ack"" information flow to transfer routeing information to the GMSC. 10. The GMSC uses the ""Send Routeing Info"" information flow to request information from the HLR for routing an MT call. 1. If the IE for inter-digit timeout is absent, the first digit entered is included in the collected digits. 2. The Change of Position Control Info contains information about changes in location, cell, service area, inter-system handover, inter-PLMN handover, and inter-MSC handover. 3. The Reset Timer IF is used to reset a timer and includes the timer value, timer ID, and call segment ID. 4. The Send Charging Information IF is used to send charging information from the gsmSCF to the gsmSSF, replacing any existing charge advice information. 5. The Split Leg IF is used to separate a leg from CSID1 and move it to a new call segment. 6. The Activity Test IF is used to check the existence of a relationship between the gsmSCF and gsmSRF. 7. The Cancel IF is used to request the cancellation of a correlated previous IF. 8. The Play Announcement IF is used for inband interaction and includes information about the announcement to be played. 9. The Prompt and Collect User Information IF is used to collect information from a call party and includes information about the collected digits and the information to be sent to the user. 10. The Specialized Resource Report IF is used to report the completion of announcements or tones. 1. Subscriber tracing procedures are used when the VLR detects subscriber-related activity for which trace mode is activated. 2. The subscriber tracing activation procedure starts the appropriate process in the HLR depending on whether tracing is required in the MSC/VLR or SGSN. 3. The subscriber tracing deactivation procedure starts the appropriate process in the HLR depending on whether tracing is no longer required in the MSC/VLR or SGSN. 4. The subscriber deletion procedure removes subscriber data from the VLR and HLR for non-GPRS subscribers, and from the SGSN and HLR for GPRS subscribers. 5. The subscriber data modification procedure allows for the modification of subscriber data in the HLR, VLR, and SGSN depending on the type of modification required. 6. The HLR initiates different MAP services (such as MAP_INSERT_SUBSCRIBER_DATA, MAP_DELETE_SUBSCRIBER_DATA, and MAP_CANCEL_LOCATION) based on the type of subscriber data modification. 7. The number of repeat attempts and the interval between successive repeat attempts in subscriber data management procedures are operator options. 8. The subscriber deletion process in the HLR involves invoking processes such as Cancel_GPRS_Location_Child_HLR and Cancel_Location_Child_HLR. 9. The subscriber data modification process in the HLR involves invoking processes such as Insert_Subs_Data_Stand_Alone_HLR and Cancel_GPRS_Location_Child_HLR. 10. The subscriber deletion procedure in the VLR and SGSN is described in separate clauses of the document. 1. The Global Cell Identifier is used for GERAN access, while the Service Area Identifier is used for UTRAN access. 2. The LCS-Reference Number is a reference between a request and a response in a deferred mt-lr procedure. 3. The LCS Privacy Check parameter determines the privacy actions related to positioning, such as notification to the user or requiring user verification. 4. The Additional LCS Capability Sets parameter indicates the supported capability sets of LCS in the VLR or SGSN. 5. The Area Event Info parameter defines the requested deferred MT-LR area event information, including area definition, type of event, occurrence info, and minimum interval time. 6. The Velocity Estimate parameter provides an estimate of the MS velocity and its accuracy. 7. The Accuracy Fulfilment Indicator parameter indicates the fulfilled accuracy of the positioning procedure. 8. The MO-LR Short Circuit Indicator parameter indicates whether the MO-LR short circuit feature is permitted. 9. The Reporting PLMN List parameter provides a list of PLMNs for subsequent periodic MO-LR TTTP requests. 10. The Periodic LDR information parameter refers to the reporting interval and amount of deferred periodic location reports."