Information transmission methods, communication device, information transmission system, and storage medium

Abstract

Provided in the embodiments of the present disclosure are information transmission methods, a communication device, an information transmission system, and a storage medium. An information transmission method executed by a terminal comprises: sending first information to a proxy-call session control function (P-CSCF) by means of a control-plane network element of a core network, wherein the first information is used for performing Internet protocol multimedia subsystem (IMS) registration on the terminal.

Description

Information transmission method, communication equipment, information transmission system and storage medium Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to an information transmission method, a communication device, an information transmission system, and a storage medium. Background Art

[0002] IMS (IP Multimedia Subsystem) is a multimedia service that meets the needs of end users for newer and more diverse multimedia services. It not only enables Voice over Internet Protocol (VoIP) services but also enables more efficient management of network, user, and application resources, improving network intelligence and enabling users to experience a converged communication experience across various networks and terminals.

[0003] Summary of the Invention

[0004] With the rapid development of communication technology, there is a problem of high consumption of communication resources in communication networks.

[0005] Embodiments of the present disclosure provide an information transmission method, a communication device, and a storage medium.

[0006] According to a first aspect of an embodiment of the present disclosure, there is provided an information transmission method, the method being performed by a terminal, the method including:

[0007] First information is sent to a Proxy-Call Session Control Function (P-CSCF) through a control plane network element of a core network, wherein the first information is used to register the terminal with an Internet Protocol Multimedia Subsystem (IMS).

[0008] According to a second aspect of an embodiment of the present disclosure, there is provided an information transmission method, the method being performed by a control plane network element of a core network, the method comprising:

[0009] Receiving first information sent by a terminal, wherein the first information is used to perform IMS registration on the terminal;

[0010] The first information is sent to the P-CSCF.

[0011] According to a third aspect of an embodiment of the present disclosure, there is provided an information transmission method, the method being performed by a proxy call session control function (P-CSCF), the method comprising:

[0012] First information sent by a terminal through a control plane network element of a core network is received, wherein the first information is used to perform IMS registration on the terminal.

[0013] According to a fourth aspect of an embodiment of the present disclosure, there is provided an information transmission method, which is performed by an information transmission system. The method includes:

[0014] The terminal sends first information to a control plane network element of a core network, wherein the first information is used to register the terminal with an Internet Protocol Multimedia Subsystem (IMS);

[0015] The control plane network element sends the first information to a proxy call session control function P-CSCF.

[0016] According to a fifth aspect of an embodiment of the present disclosure, a terminal is provided, including:

[0017] The sending module is configured to send first information to the P-CSCF through a control plane network element of the core network, wherein the first information is used to perform IMS registration on the terminal.

[0018] According to a sixth aspect of an embodiment of the present disclosure, a control plane network element of a core network is provided, including:

[0019] a receiving module configured to receive first information sent by a terminal, wherein the first information is used to perform IMS registration on the terminal;

[0020] The sending module is configured to send the first information to the P-CSCF.

[0021] According to a seventh aspect of an embodiment of the present disclosure, a P-CSCF is provided, including:

[0022] The receiving module is configured to receive first information sent by a terminal through a control plane network element of a core network, wherein the first information is used to perform IMS registration on the terminal.

[0023] According to an eighth aspect of an embodiment of the present disclosure, there is provided an information transmission system, the information transmission system comprising:

[0024] A terminal configured to implement the communication method provided by the first aspect;

[0025] A control plane network element of a core network, configured to implement the information transmission method provided in the second aspect;

[0026] The P-CSCF is configured to implement the information transmission method provided by the second aspect.

[0027] According to a ninth aspect of an embodiment of the present disclosure, a communication device is provided, the communication device including:

[0028] one or more processors;

[0029] The processor is used to call instructions to enable the communication device to execute the information transmission method provided by the first aspect, the second aspect or the third aspect.

[0030] According to the tenth aspect of an embodiment of the present disclosure, a storage medium is provided, wherein the storage medium stores instructions, and when the instructions are executed on a communication device, the communication device executes the information transmission method provided by the first aspect, the second aspect or the third aspect.

[0031] It should be understood that the foregoing general description and the following detailed description are merely exemplary and explanatory and are not restrictive of the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present invention and, together with the description, serve to explain the principles of the embodiments of the present invention.

[0033] FIG1a is a schematic diagram showing the architecture of an information transmission system according to an exemplary embodiment;

[0034] FIG1b is a schematic diagram of an IMS network architecture according to an exemplary embodiment;

[0035] FIG1c is a schematic diagram of a 5G system architecture according to an exemplary embodiment;

[0036] FIG1d is a schematic diagram showing the architecture of an information transmission system according to an exemplary embodiment;

[0037] FIG1e is a schematic diagram showing the architecture of an information transmission system according to an exemplary embodiment;

[0038] FIG2 is a schematic flow chart showing an information transmission method according to an exemplary embodiment;

[0039] FIG3a is a schematic flow chart showing an information transmission method according to an exemplary embodiment;

[0040] FIG3 b is a schematic flow chart showing an information transmission method according to an exemplary embodiment;

[0041] FIG3c is a schematic flow chart showing an information transmission method according to an exemplary embodiment;

[0042] FIG4a is a schematic flow chart showing an information transmission method according to an exemplary embodiment;

[0043] FIG4 b is a schematic flow chart showing an information transmission method according to an exemplary embodiment;

[0044] FIG4c is a schematic flow chart showing an information transmission method according to an exemplary embodiment;

[0045] FIG4 d is a schematic flow chart showing an information transmission method according to an exemplary embodiment;

[0046] FIG5 is a schematic flow chart showing an information transmission method according to an exemplary embodiment;

[0047] FIG6 is a schematic flow chart showing an information transmission method according to an exemplary embodiment;

[0048] FIG7a is a schematic structural diagram of a terminal according to an exemplary embodiment;

[0049] FIG7b is a schematic structural diagram of a control plane network element according to an exemplary embodiment;

[0050] FIG7c is a schematic diagram showing the structure of a P-CSCF according to an exemplary embodiment;

[0051] FIG8a is a schematic structural diagram of a UE according to an exemplary embodiment;

[0052] Fig. 8b is a schematic structural diagram of a communication device according to an exemplary embodiment. DETAILED DESCRIPTION

[0053] Embodiments of the present disclosure provide an information transmission method, a communication device, an information transmission system, and a storage medium.

[0054] In a first aspect, an embodiment of the present disclosure provides an information transmission method, the method being executed by a terminal, the method comprising:

[0055] First information is sent to the P-CSCF through a control plane network element of the core network, wherein the first information is used to perform IMS registration on the terminal.

[0056] In the above embodiment, since the terminal can send the first information for IMS registration of the terminal to the P-CSCF through the control plane network element of the core network, compared with the need to establish a packet data unit (PDU) session before the terminal registers with the P-CSCF for IMS, the IMS registration delay and unnecessary network resource consumption caused by the need to establish a PDU session between the terminal and the user plane function (UPF) network element can be reduced.

[0057] In conjunction with some embodiments of the first aspect, in some embodiments, sending the first information to the P-CSCF through the control plane network element of the core network includes:

[0058] A first non-access stratum (NAS) message is sent to the control plane network element, so that the first information carried by the NAS message is sent to the P-CSCF through the control plane network element.

[0059] In the above embodiment, the terminal can send the first information for IMS registration of the terminal to the control plane network element through a NAS message. In this way, the terminal forwards the NAS message to the control plane network element of the core network through the radio access network (RAN) device. Since the NAS message is transparent to the RAN device, the RAN device does not need to parse the content in the NAS message, thereby improving information transmission efficiency and saving communication resources.

[0060] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0061] Second information is sent to the control plane network element through the access network device, wherein the second information is used to indicate that the terminal supports IMS registration through NAS.

[0062] In the above embodiment, the terminal can send second information indicating that the terminal supports IMS registration through NAS to the control plane network element through the access network device, so that the control plane network element knows that the terminal has the ability to support IMS registration through NAS, and thus can determine that the terminal can initiate IMS registration through NAS, which is conducive to improving the success rate of IMS registration for the terminal.

[0063] In conjunction with some embodiments of the first aspect, in some embodiments, sending a first non-access stratum (NAS) message to the control plane network element includes:

[0064] In response to receiving third information sent by the control plane network element through the access network device, the first NAS message is sent to the control plane network element, wherein the third information is used to indicate that the control plane network element supports IMS registration through NAS.

[0065] In the above embodiment, the terminal receives the third information sent by the control plane network element through the access network device, indicating that the control plane network element supports IMS registration through NAS. In this way, the terminal can know that the control plane network element has the ability to support IMS registration through NAS, so that the terminal can initiate IMS registration through NAS, which is beneficial to improving the success rate of IMS registration for the terminal.

[0066] In conjunction with some embodiments of the first aspect, in some embodiments, the second information is carried in a registration request message, and the third information is carried in a registration accept message;

[0067] Alternatively, the second information is carried in a first Radio Resource Control (RRC) message, and the third information is carried in a second RRC message;

[0068] Alternatively, the second information is carried in a second NAS message, and the third information is carried in a third NAS message.

[0069] In the above embodiment, the messages in the communication process may be multiplexed to send the second information and / or receive the third information, thereby reducing the signaling overhead of information transmission and improving the utilization efficiency of communication resources.

[0070] In combination with some embodiments of the first aspect, in some embodiments, the first information is carried in a first container of the first NAS message, and the first container is used for IMS registration.

[0071] In the above embodiment, the first container is used to carry the first information in the first NAS message. This eliminates the need for additional signaling to indicate the first information included in the first NAS message, resulting in simple implementation, low complexity, and reduced signaling overhead.

[0072] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0073] The fourth information sent by the P-CSCF according to the first information is received through the control plane network element; wherein the fourth information is used to indicate the IMS registration result of the terminal.

[0074] In the above embodiment, the control plane network element receives the fourth information sent by the P-CSCF to indicate the IMS registration result of the terminal, so that the terminal can know whether the IMS registration is successful based on the fourth information.

[0075] In combination with some embodiments of the first aspect, in some embodiments, the fourth information is carried in a fourth NAS message sent by the control plane network element to the terminal.

[0076] In the above embodiment, since the NAS message is transparent to the RAN device, the RAN device does not need to parse the content of the NAS message, which makes the information transmission efficiency high and saves communication resources.

[0077] In conjunction with some embodiments of the first aspect, in some embodiments, the control plane network element includes at least one of the following:

[0078] Access and Mobility Management Function (AMF) network element;

[0079] Session Management Function (SMF) network element;

[0080] Policy Control Function (PCF) network element.

[0081] In the above embodiment, the terminal can initiate IMS registration to the P-CSCF through control plane network elements such as AMF, SMF and / or PCF, so that there is no need to establish a PDU session between the terminal and the UPF network element before the terminal performs IMS registration with the P-CSCF, thereby reducing the IMS registration delay and unnecessary network resource consumption caused by the need to establish a PDU session.

[0082] In a second aspect, an embodiment of the present disclosure provides an information transmission method, the method being performed by a control plane network element of a core network, the method comprising:

[0083] Receiving first information sent by a terminal, wherein the first information is used to perform IMS registration on the terminal;

[0084] The first information is sent to the P-CSCF.

[0085] In the above embodiment, since the control plane network element of the core network can receive the first information sent by the terminal to the P-CSCF for IMS registration of the terminal, compared with the need to establish a PDU session before the terminal registers with the P-CSCF for IMS, the IMS registration delay and unnecessary network resource consumption caused by the need to establish a PDU session between the terminal and the user plane function (UPF) network element can be reduced.

[0086] In conjunction with some embodiments of the second aspect, in some embodiments, the first information sent by the receiving terminal includes:

[0087] Receive a first non-access stratum (NAS) message sent by the terminal; wherein the NAS message carries the first information.

[0088] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0089] Second information sent by the terminal through the access network device is received, wherein the second information is used to indicate that the terminal supports IMS registration through NAS.

[0090] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0091] Sending third information to the terminal through the access network device, wherein the third information is used to indicate that the control plane network element supports IMS registration through NAS.

[0092] In conjunction with some embodiments of the second aspect, in some embodiments, the second information is carried in a registration request message, and the third information is carried in a registration accept message;

[0093] or,

[0094] The second information is carried in a first radio resource control (RRC) message, and the third information is carried in a second RRC message;

[0095] or,

[0096] The second information is carried in a second NAS message, and the third information is carried in a third NAS message.

[0097] In combination with some embodiments of the second aspect, in some embodiments, the first information is carried in a first container of the first NAS message, and the first container is used for IMS registration.

[0098] In conjunction with some embodiments of the second aspect, in some embodiments, the method further includes:

[0099] In response to receiving fourth information sent by the P-CSCF according to the first information, the fourth information is sent to the terminal, wherein the fourth information is used to indicate an IMS registration result of the terminal.

[0100] In combination with some embodiments of the second aspect, in some embodiments, the fourth information is carried in a fourth NAS message sent by the control plane network element to the terminal.

[0101] In conjunction with some embodiments of the second aspect, in some embodiments, the control plane network element includes at least one of the following:

[0102] Access and Mobility Management Function (AMF) network element;

[0103] Session Management Function (SMF) network element;

[0104] Policy Control Function (PCF) network element.

[0105] In a third aspect, an embodiment of the present disclosure provides an information transmission method, the method being performed by a proxy call session control function (P-CSCF), the method comprising:

[0106] First information sent by a terminal through a control plane network element of a core network is received, wherein the first information is used to perform IMS registration on the terminal.

[0107] In the above embodiment, since the P-CSCF can receive the first information for performing IMS registration on the terminal sent by the terminal through the control plane network element of the core network, compared with the need to establish a PDU session before the terminal performs IMS registration with the P-CSCF, the IMS registration delay and unnecessary network resource consumption caused by the need to establish a PDU session between the terminal and the user plane function (UPF) network element can be reduced.

[0108] In conjunction with some embodiments of the third aspect, in some embodiments, the method further includes:

[0109] Sending fourth information to the terminal through the control plane network element, wherein the fourth information is used to indicate an IMS registration result of the terminal.

[0110] In conjunction with some embodiments of the third aspect, in some embodiments, the control plane network element includes at least one of the following:

[0111] Access and Mobility Management Function (AMF) network element;

[0112] Session Management Function (SMF) network element;

[0113] Policy Control Function (PCF) network element.

[0114] In a fourth aspect, an embodiment of the present disclosure provides an information transmission method, which is performed by an information transmission system, and the method includes:

[0115] The terminal sends first information to a control plane network element of a core network, wherein the first information is used to register the terminal with an Internet Protocol Multimedia Subsystem (IMS);

[0116] The control plane network element sends the first information to a proxy call session control function (P-CSCF).

[0117] In conjunction with some embodiments of the fourth aspect, in some embodiments, the terminal sending the first information to the control plane network element of the core network includes:

[0118] The terminal sends a first non-access stratum (NAS) message to the control plane network element, where the NAS message carries the first information.

[0119] In conjunction with some embodiments of the fourth aspect, in some embodiments, the method further includes:

[0120] The terminal sends second information to the control plane network element through the access network device, wherein the second information is used to indicate that the terminal supports IMS registration through NAS.

[0121] In combination with some embodiments of the fourth aspect, in some embodiments, the terminal sending a first non-access stratum (NAS) message to the control plane network element includes:

[0122] In response to receiving the third information sent by the control plane network element through the access network device, the terminal sends the first NAS message to the control plane network element, wherein the third information is used to indicate that the control plane network element supports IMS registration through NAS.

[0123] In conjunction with some embodiments of the fourth aspect, in some embodiments, the second information is carried in a registration request message, and the third information is carried in a registration accept message;

[0124] or,

[0125] The second information is carried in a first radio resource control (RRC) message, and the third information is carried in a second RRC message;

[0126] or,

[0127] The second information is carried in a second NAS message, and the third information is carried in a third NAS message.

[0128] In combination with some embodiments of the fourth aspect, in some embodiments, the first information is carried in a first container of the first NAS message, and the first container is used for IMS registration.

[0129] In conjunction with some embodiments of the fourth aspect, in some embodiments, the method further includes:

[0130] The terminal receives, through the control plane network element, fourth information sent by the P-CSCF based on the first information; wherein the fourth information is used to indicate an IMS registration result of the terminal.

[0131] In a fifth aspect, an embodiment of the present disclosure provides a terminal, including:

[0132] The sending module is configured to send first information to the (P-CSCF) through a control plane network element of the core network, wherein the first information is used to perform IMS registration on the terminal.

[0133] With reference to some embodiments of the fifth aspect, in some embodiments, the sending module is configured to:

[0134] A first non-access stratum (NAS) message is sent to the control plane network element, so that the first information carried by the NAS message is sent to the P-CSCF through the control plane network element.

[0135] With reference to some embodiments of the fifth aspect, in some embodiments, the sending module is configured to:

[0136] Second information is sent to the control plane network element through the access network device, wherein the second information is used to indicate that the terminal supports IMS registration through NAS.

[0137] With reference to some embodiments of the fifth aspect, in some embodiments, the sending module is configured to:

[0138] In response to receiving third information sent by the control plane network element through the access network device, the first NAS message is sent to the control plane network element, wherein the third information is used to indicate that the control plane network element supports IMS registration through NAS.

[0139] In conjunction with some embodiments of the fifth aspect, in some embodiments, the second information is carried in a registration request message, and the third information is carried in a registration accept message;

[0140] or,

[0141] The second information is carried in a first radio resource control (RRC) message, and the third information is carried in a second RRC message;

[0142] or,

[0143] The second information is carried in a second NAS message, and the third information is carried in a third NAS message.

[0144] In combination with some embodiments of the fifth aspect, in some embodiments, the first information is carried in a first container of the first NAS message, and the first container is used for IMS registration.

[0145] In conjunction with some embodiments of the fifth aspect, in some embodiments, the method further includes:

[0146] A receiving module is configured to receive, through the control plane network element, fourth information sent by the P-CSCF according to the first information; wherein the fourth information is used to indicate an IMS registration result of the terminal.

[0147] In combination with some embodiments of the fifth aspect, in some embodiments, the fourth information is carried in a fourth NAS message sent by the control plane network element to the terminal.

[0148] In conjunction with some embodiments of the first aspect, in some embodiments, the control plane network element includes at least one of the following:

[0149] Access and Mobility Management Function (AMF) network element;

[0150] Session Management Function (SMF) network element;

[0151] Policy Control Function (PCF) network element.

[0152] In a sixth aspect, an embodiment of the present disclosure provides a control plane network element of a core network, including:

[0153] a receiving module configured to receive first information sent by a terminal, wherein the first information is used to perform IMS registration on the terminal;

[0154] The sending module is configured to send the first information to the P-CSCF.

[0155] With reference to some embodiments of the sixth aspect, in some embodiments, the receiving module is configured to:

[0156] Receive a first non-access stratum (NAS) message sent by the terminal; wherein the NAS message carries the first information.

[0157] With reference to some embodiments of the sixth aspect, in some embodiments, the receiving module is configured to:

[0158] Second information sent by the terminal through the access network device is received, wherein the second information is used to indicate that the terminal supports IMS registration through NAS.

[0159] In conjunction with some embodiments of the sixth aspect, in some embodiments, the method further includes:

[0160] The sending module is configured to send third information to the terminal through the access network device, wherein the third information is used to indicate that the control plane network element supports IMS registration through NAS.

[0161] With reference to some embodiments of the sixth aspect, in some embodiments, the second information is carried in a registration request message, and the third information is carried in a registration accept message;

[0162] or,

[0163] The second information is carried in a first radio resource control (RRC) message, and the third information is carried in a second RRC message;

[0164] or,

[0165] The second information is carried in a second NAS message, and the third information is carried in a third NAS message.

[0166] In combination with some embodiments of the sixth aspect, in some embodiments, the first information is carried in a first container of the first NAS message, and the first container is used for IMS registration.

[0167] In conjunction with some embodiments of the sixth aspect, in some embodiments, the method further includes:

[0168] The sending module is configured to send the fourth information to the terminal in response to receiving the fourth information sent by the P-CSCF according to the first information, wherein the fourth information is used to indicate the IMS registration result of the terminal.

[0169] In combination with some embodiments of the sixth aspect, in some embodiments, the fourth information is carried in a fourth NAS message sent by the control plane network element to the terminal.

[0170] With reference to some embodiments of the sixth aspect, in some embodiments, the control plane network element includes at least one of the following:

[0171] Access and Mobility Management Function (AMF) network element;

[0172] Session Management Function (SMF) network element;

[0173] Policy Control Function (PCF) network element.

[0174] In a seventh aspect, an embodiment of the present disclosure provides a P-CSCF, including:

[0175] The receiving module is configured to receive first information sent by a terminal through a control plane network element of a core network, wherein the first information is used to perform IMS registration on the terminal.

[0176] In conjunction with some embodiments of the seventh aspect, in some embodiments, further comprising:

[0177] The sending module is configured to send fourth information to the terminal through the control plane network element, wherein the fourth information is used to indicate the IMS registration result of the terminal.

[0178] In conjunction with some embodiments of the seventh aspect, in some embodiments, the control plane network element includes at least one of the following:

[0179] Access and Mobility Management Function (AMF) network element;

[0180] Session Management Function (SMF) network element;

[0181] Policy Control Function (PCF) network element.

[0182] In an eighth aspect, an embodiment of the present disclosure provides an information transmission system, the information transmission system comprising:

[0183] A terminal, configured to implement the information transmission method described in the optional implementation manner of the first aspect;

[0184] A control plane network element of a core network, configured to implement the information transmission method described in the optional implementation manner of the second aspect;

[0185] The P-CSCF is configured to implement the information transmission method described in the optional implementation manner of the third aspect.

[0186] In a ninth aspect, an embodiment of the present disclosure provides a communication device, the communication device comprising:

[0187] one or more processors;

[0188] The processor is used to call instructions to enable the communication device to execute the information transmission method described in the optional implementation manner of the first aspect, the second aspect, or the third aspect.

[0189] In the tenth aspect, an embodiment of the present disclosure provides a storage medium, wherein the storage medium stores instructions, which, when the instructions are executed on a communication device, enable the communication device to execute the information transmission method described in the optional implementation of the first aspect, the second aspect, or the third aspect.

[0190] In an eleventh aspect, an embodiment of the present disclosure provides a program product, which, when executed by a communication device, enables the communication device to execute the information transmission method described in the optional implementation manner of the first aspect, the second aspect, or the third aspect.

[0191] In a twelfth aspect, an embodiment of the present disclosure provides a computer program, which, when executed on a computer, enables the computer to execute the information transmission method described in the optional implementation of the first aspect, the second aspect, or the third aspect.

[0192] It is understandable that the above-mentioned terminals, network elements, communication devices, information transmission systems, storage media, program products, and computer programs are all used to execute the information transmission methods provided by the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0193] The present disclosure provides an information transmission method, a communication device, an information transmission system, and a storage medium. In some embodiments, the terms information transmission method, information processing method, and communication method are interchangeable, and the terms information transmission system, information processing system, and the like are interchangeable.

[0194] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0195] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0196] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0197] In the embodiments of the present disclosure, unless otherwise specified, elements expressed in the singular, such as "a", "an", "the", "above", "said", "the", "the", etc., may mean "one and only one", or "one or more", "at least one", etc. For example, when using articles such as "a", "an", "the" in English in translation, the noun following the article may be understood as a singular expression or a plural expression.

[0198] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0199] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

[0200] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "in one case A, in another case B," or "in one case A, in another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The same applies when there are more branches such as A, B, and C.

[0201] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0202] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0203] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0204] In some embodiments, terms such as "...", "determine...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0205] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", and "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0206] In some embodiments, devices, etc. can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. Terms such as "device", "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", and "subject" can be used interchangeably.

[0207] In some embodiments, "network" can be interpreted as devices included in the network (eg, access network equipment, core network equipment, etc.).

[0208] In some embodiments, the terms "access network device (AN device)", "radio access network device (RAN device)", "base station (BS)", "radio base station" "fixed station", "node", "access point", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)", "panel", "antenna panel", "antenna array", "cell", "macro cell", "small cell", "femto cell", "pico cell", "sector", "cell group", "serving cell", "carrier", "component carrier", "bandwidth part (BWP)" and the like may be used interchangeably.

[0209] In some embodiments, the terms "terminal", "terminal device", "user equipment (UE)", "user terminal", "mobile station (MS)", "mobile terminal (MT)", subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, etc. can be used interchangeably.

[0210] In some embodiments, the access network device, the core network device, or the network device can be replaced by a terminal. For example, the various embodiments of the present disclosure can also be applied to a structure in which the communication between the access network device, the core network device, or the network device and the terminal is replaced by communication between multiple terminals (for example, device-to-device (D2D), vehicle-to-everything (V2X), etc.). In this case, it is also possible to set the structure in which the terminal has all or part of the functions of the access network device. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminals (for example, "side"). For example, uplink channels, downlink channels, etc. can be replaced by side channels, and uplinks, downlinks, etc. can be replaced by side links.

[0211] In some embodiments, the terminal may be replaced by an access network device, a core network device, or a network device. In this case, the access network device, the core network device, or the network device may have a structure that has all or part of the functions of the terminal.

[0212] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0213] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0214] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0215] FIG1a is a schematic diagram of the architecture of an information transmission system according to an embodiment of the present disclosure.

[0216] As shown in FIG. 1 a , an information transmission system 100 includes a terminal 101 , a first network device 102 , and a second network device 103 .

[0217] In some embodiments, the terminal 101 includes, for example, a mobile phone, a wearable device, an Internet of Things device, a car with communication function, a smart car, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and at least one of a wireless terminal device in a smart home, but is not limited thereto.

[0218] In some embodiments, the first network device 102 may include, for example, a core network device.

[0219] In some embodiments, the core network device may be a device including a control plane network element, which may include one or more of the first network function, the second network function, and the third network function. It may also be multiple devices or device groups, each including a control plane network element, such as all or part of the first network function, the second network function, and the third network function. The network element may be virtual or physical. The core network, for example, includes at least one of the Evolved Packet Core (EPC), the 5G Core Network (5GCN), and the Next Generation Core (NGC).

[0220] In some embodiments, the first network function is used for access and mobility management, such as registration management, connection management, and mobility management, etc., and the name is not limited thereto. For example, the first network function is AMF.

[0221] In some embodiments, the second network function is used for session management (SM), for example, the second network function is SMF, but the name is not limited thereto.

[0222] In some embodiments, the third network function is used for policy control, such as PCF, but the name is not limited thereto.

[0223] In some embodiments, an access network device is further connected between the terminal 101 and the first network device 102. The access network device is a node or device that connects the terminal to a wireless network. The access network device may include at least one of an evolved NodeB (eNB), a next generation evolved NodeB (ng-eNB), a next generation NodeB (gNB), a node B (NB), a home nodeB (HNB), a home evolved nodeB (HeNB), a wireless backhaul device, a radio network controller (RNC), a base station controller (BSC), a base transceiver station (BTS), a base band unit (BBU), a mobile switching center, a base station in a 6G information transmission system, an open RAN, a cloud RAN, a base station in other information transmission systems, and an access node in a Wi-Fi system, but is not limited thereto.

[0224] In some embodiments, the access network device can be composed of a centralized unit (CU) and a distributed unit (DU), where the CU can also be called a control unit. The CU-DU structure can be used to split the protocol layer of the access network device, with the functions of some protocol layers centrally controlled by the CU, and the functions of the remaining part or all of the protocol layers distributed in the DU, which is centrally controlled by the CU, but is not limited to this.

[0225] In some embodiments, the technical solution of the present disclosure can be applied to the Open RAN architecture. In this case, the interfaces between or within the access network devices involved in the embodiments of the present disclosure can be transformed into internal interfaces of the Open RAN, and the processes and information interactions between these internal interfaces can be implemented through software or programs.

[0226] In some embodiments, the second network device 103 may be a network device independent of the core network device. For example, the second network device is a network device in an IMS network.

[0227] In some embodiments, the second network device 103 may be a single device including the fourth network function, the fifth network function, the sixth network function, etc., or may be a plurality of devices or a group of devices including the fourth network function, the fifth network function, the sixth network function, etc. The network element may be virtual or physical.

[0228] In some embodiments, the fourth network function is, for example, a Proxy Call Session Control Function (P-CSCF).

[0229] In some embodiments, the fifth network function is, for example, an Interrogating-Call Session Control Function (I-CSCF) or a Serving-Call Session Control Function (S-CSCF).

[0230] In some embodiments, the sixth network function is, for example, an application server (AS).

[0231] It can be understood that the information transmission system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution provided by the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution provided by the embodiment of the present disclosure is also applicable to similar technical problems.

[0232] The following embodiments of the present disclosure may be applied to the information transmission system 100 shown in FIG1a, or a portion thereof, but are not limited thereto. The various entities shown in FIG1 are illustrative only. The information transmission system may include all or a portion of the entities shown in FIG1a, or may include other entities other than those shown in FIG1a. The number and form of the entities may be arbitrary. The connection relationship between the entities is illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0233] The embodiments of the present disclosure can be applied to Long Term Evolution (LTE), LTE-Advanced (LTE-A), LTE-Beyond (LTE-B), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G New Radio (NR), Future Radio Access (FRA), New Radio Access Technology (RAT), New Radio (NR), New Radio Access (NX), Future Generation Radio Access (FX), Global System for Mobile Communications (GSM (registered trademark)), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), Public Land Mobile Network (PLMN) networks, Device-to-Device (D2D) systems, Machine-to-Machine (M2M) systems, Internet of Things (IoT) systems, Vehicle-to-Everything (V2X), systems utilizing other communication methods, and next-generation systems based on and extending these methods. Furthermore, multiple systems may be combined (for example, a combination of LTE or LTE-A with 5G).

[0234] In some embodiments, the IP multimedia core network subsystem includes all core network (CN) elements that provide multimedia services, including network elements that collect signaling and media-related information. IP multimedia services are based on session control functions defined by the Internet Engineering Task Force (IETF), which, along with multimedia transport functions, utilize IP connectivity access networks.

[0235] For example, the IMS network architecture diagram is shown in Figure 1b. The IMS network may include, but is not limited to, network functions such as the P-CSCF, I-CSCF, S-CSCF, and AS. The I-CSCF, S-CSCF, and P-CSCF collaborate to process requests from UEs within the IMS network architecture to meet the UE's network requirements. The I-CSCF acts as a transit node, enabling direct information exchange with the S-CSCF and P-CSCF.

[0236] In some embodiments, to achieve access independence and maintain smooth interoperability with terminals on the Internet, the IP Multimedia Subsystem attempts to conform to IETF "Internet standards." Therefore, when IETF protocols are selected, the specified interfaces are as compliant as possible with IETF "Internet standards," such as SIP (Session Initialization Protocol) and RTP (Reliable Transport Protocol).

[0237] In some embodiments, the IP Multimedia Core Network (IM CN) ​​subsystem enables operators to provide multimedia services to users. The IM CN subsystem provides convergence and access to voice, video, messaging, data, and network-based technologies for wireless and wireline users.

[0238] In some embodiments, the 5G system architecture is defined to support data connectivity and services, enabling deployments using technologies such as network function virtualization and software-defined networking. The 5G system architecture should utilize service-based interactions between defined control plane (CP) functions.

[0239] For example, the 5G system architecture diagram can be seen in Figure 1c. The 5G system architecture includes: Network Function (NF) and related interfaces. NF includes but is not limited to: (1) AMF (Access and Mobility Management Function): responsible for user access and mobility management; (2) SMF (Session Management Function): responsible for user session management; (3) UPF (User Plane Function): responsible for user plane processing; (4) AUSF (Authentication Server Function): responsible for authenticating the user's 3GPP (3rd Generation Partnership Project) and non-3GPP access; (5) PCF (Policy Control): responsible for user policy control, including session policy and mobility policy; (6) UDM (Unified Data Management): responsible for user subscription data management; (7) NSSF (Network Slice Selection Function): responsible for selecting the network slice used by the user's service, etc. Related interfaces in the 5G system architecture, for example: N2 is the NG interface between (R) AN and AMF; N3 is the docking interface between (R)AN and UPF, using the GTP-U protocol; N4 is the device interface for separating the control plane SMF and the user plane UPF; N6 is the protocol interface between the internal network side and the external network side, using the GTP-U protocol, etc.

[0240] Some key principles and concepts are as follows:

[0241] - Separation of User Plane (UP) functions from Control Plane (CP) functions, allowing independent scalability, evolution, and flexible deployment, such as centralized locations or distributed (remote) locations;

[0242] - Modular functional design, such as enabling flexible and efficient network slicing;

[0243] - where applicable, define processes (i.e. sets of interactions between network functions) as services so that they can be reused;

[0244] - Enable each network function and its network function service to interact with other network functions and their network function services, directly or indirectly through a service communication proxy, if necessary. This architecture does not exclude the use of another intermediate function to help route control plane messages, such as a Diameter Routing Agent (DRA);

[0245] - Reduce the dependencies between the Access Network (AN) and the Core Network (CN). The architecture is defined as a converged core network with a common AN-CN interface that integrates different access types, such as 3GPP access and non-3GPP access.

[0246] -Support a unified authentication framework;

[0247] -Support for "stateless" network functions, where "compute" resources are decoupled from "storage" resources;

[0248] -Support capability exposure;

[0249] -Support concurrent access to local and centralized services;

[0250] - To support low-latency services and local access to data networks, UP function;

[0251] - In the visited Public Land Mobile Network (PLMN), roaming of locally routed traffic and local burst traffic is supported.

[0252] Before registering with the IMS, the terminal needs to first register with the 5GC and establish a PDU session between the terminal and the UPF. This may delay the IMS registration and unnecessarily consume some network resources. For example, in the network architecture shown in Figure 1d, under this network architecture, before the terminal registers with the P-CSCF for IMS, it needs to establish a PDU session between the terminal and the user plane function (UPF) network element. This will cause IMS registration delays and unnecessary network resource consumption due to the establishment of the PDU session.

[0253] In some embodiments, a first interface for IMS registration may be provided between a control plane network element of the core network (e.g., AMF) and a P-CSCF of the IMS network. The AMF may initiate IMS registration of the terminal to the P-CSCF via the first interface in response to receiving an IMS registration information flow of the terminal. For example, as shown in the network architecture of FIG1e , under this network architecture, the terminal may send first information for performing IMS registration of the terminal to the P-CSCF via the AMF of the core network. In this way, before performing IMS registration with the P-CSCF, the terminal does not need to establish a PDU session between the terminal and the user plane function (UPF) network element, thereby reducing the IMS registration delay and unnecessary network resource consumption caused by establishing the PDU session.

[0254] FIG2 is an interactive diagram of an information transmission method according to an embodiment of the present disclosure. As shown in FIG2 , the present disclosure embodiment relates to an information transmission method for use in an information transmission system 100, the method comprising:

[0255] Step S2101: The terminal sends second information to the first network device.

[0256] In some embodiments, the first network device receives second information sent by the terminal.

[0257] In some embodiments, the first network device may include a control plane network element of the core network. For example, the control plane network element may include at least one of the following: AMF, SMF, PCF.

[0258] In some embodiments, the terminal may be a terminal that supports IMS registration via NAS.

[0259] In some embodiments, when the terminal does not support IMS registration through NAS, the terminal does not send the second information to the first network device.

[0260] In some embodiments, the second information may be capability information of the terminal.

[0261] In some embodiments, the second information is used to indicate that the terminal supports IMS registration through NAS.

[0262] In some embodiments, the second information may be carried in the first message.

[0263] Exemplarily, the first message may be a registration request (Registration Request) message sent by the terminal to the first network device.

[0264] For example, when the terminal registers or re-registers with the network, the second information may be carried in the registration request message, for example, indicating that the terminal supports the capability of IMS registration through NAS, and the first network device receives and stores the capability information of the terminal.

[0265] In another exemplary embodiment, after the second information is sent by the terminal to the access network device, the first message sent by the access network device to the first network device carries the second information. The first message can be an initial terminal message (Initial UE Message) of the terminal or a context suspend request (UE Context Suspend Request) message of the terminal.

[0266] For example, the capability of the terminal to support IMS registration through NAS reported by the access network device to the AMF can be carried in the initial terminal message of the terminal or the context suspension request message of the UE terminal.

[0267] In some embodiments, the second information may be sent by the terminal to the first network device during an initial attach (Attach) process or a tracking area update (TAU) process.

[0268] In some embodiments, the terminal sends an RRC establishment request, including a registration request, to the first network device via the access network device. The terminal may indicate its capability of "supporting IMS registration via NAS" in the registration request.

[0269] In some embodiments, the registration request carries the second information and at least one of the following information: registration type, terminal identifier (ID), and security parameters.

[0270] In some embodiments, the terminal ID includes at least one of the following: Subscription Concealed Identifier (SUCI), Subscriber Permanent Identifier (SUPI), Globally Unique Temporary UE Identity (GUTI), and Permanent Equipment Identifier (PEI).

[0271] In some embodiments, the second information is carried in the first RRC message. For example, the first RRC message can be at least one of the following: RRC establishment request message, RRC establishment completion message, RRC connection recovery request message, RRC connection recovery completion message, etc.

[0272] In some embodiments, the second information is carried in a second NAS message.

[0273] In some embodiments, the first network device includes an AMF, and the second information is sent by the terminal to the access network device, and then sent by the access network device to the AMF through the N2 interface.

[0274] In some embodiments, the first network device includes AMF, and the second information can be sent by the terminal to the AMF through the access network device, and then sent by the AMF to the SMF.

[0275] In some embodiments, the first network device includes an AMF, and the second information can be sent by the terminal to the AMF through the access network device, and then sent by the AMF to the PCF.

[0276] Step S2102: The first network device sends third information to the terminal.

[0277] In some embodiments, the terminal receives third information sent by the first network device.

[0278] In some embodiments, the third information may be network capability information of the first network device.

[0279] In some embodiments, the third information is used to indicate that the first network device supports IMS registration via NAS.

[0280] In some embodiments, in response to receiving the second information sent by the terminal, the first network device sends third information to the terminal.

[0281] In some embodiments, the third information may be carried in the second message.

[0282] Exemplarily, the second message may be a registration accept message sent by the first network device.

[0283] In some embodiments, the terminal sends an RRC establishment request, including a registration request, to the first network device via the access network device. The terminal may indicate its capability of "supporting IMS registration via NAS" in the registration request.

[0284] For example, the second information is carried in a registration request message of the terminal, and the third information is carried in a registration acceptance message sent by the first network device. The registration acceptance message can be used to respond to the registration request message.

[0285] In some embodiments, the third information is carried in the second RRC message. For example, the second RRC message may be at least one of the following: an RRC configuration message, an RRC reconfiguration message, and the like.

[0286] For example, the second information is carried in a first radio resource control RRC message, and the third information is carried in a second RRC message.

[0287] In some embodiments, the third information is carried in a third NAS message.

[0288] For example, the second information is carried in the second NAS message, and the third information is carried in the third NAS message.

[0289] In some embodiments, the first network device includes AMF, and the third information is sent to the access network device by the AMF providing an N2 interface, and then sent to the terminal by the access network device.

[0290] In some embodiments, the third information is used to indicate that the first network device supports IMS registration via NAS.

[0291] In some embodiments, the third information is carried in a second message sent by the first network device to the terminal. For example, the second message is a registration acceptance message.

[0292] In some embodiments, after the terminal passes authentication and authorization, the AMF sends a registration acceptance to the terminal through the RAN.

[0293] For example, if the terminal indicates in the Registration Request that its capability is "support for IMS registration via NAS", the AMF may indicate that its network capability is "support for IMS registration".

[0294] In some embodiments, the first network device is AMF, and the registration acceptance message is sent by the AMF to the access network device through the N2 interface, and then sent by the access network device to the terminal.

[0295] In some embodiments, the third information is carried in a Media Access Control (MAC) Control Element (CE) message.

[0296] Step S2103: The terminal sends first information to the first network device.

[0297] In some embodiments, the first network device receives first information sent by the terminal.

[0298] In some embodiments, the first information is used to perform IMS registration on the terminal.

[0299] In some embodiments, the first information includes a registration information flow. For example, the registration information flow may include: a user identification of the terminal.

[0300] For example, the user identification of the terminal includes at least one of the following: a public user identification (Public User Identity, PUI), a private user identification (Private User Identity, PVI), and a home network domain name.

[0301] In some embodiments, the terminal sends a first NAS message to the first network device. The first information is carried in a first container of the first NAS message. The first container is used for IMS registration.

[0302] For example, the registration information flow may be carried as a first container in an uplink (Uplink) NAS transmission message sent by the terminal to the second network device.

[0303] The terminal may add a new NAS container type in the UL NAS transmission message to indicate that the container is used for IMS registration.

[0304] In some embodiments, the terminal sends the first information to the first network device in response to receiving the second information sent by the first network device through the access network device.

[0305] In some embodiments, the first network device includes an AMF, and the first information is sent by the terminal to the AMF.

[0306] In some embodiments, the first network device includes SMF, and the first information is sent from the terminal to the SMF via AMF.

[0307] In some embodiments, the first network device includes PCF, and the first information can be sent by the terminal to AMF through the access network device, and then sent by AMF to PCF.

[0308] Step S2104: The first network device sends first information to the second network device.

[0309] In some embodiments, a second network device receives first information sent by a network device.

[0310] In some embodiments, the second network device includes a P-CSCF, and the first network device sends the first information to the P-CSCF.

[0311] In some embodiments, the first information is used by the P-CSCF to send the first information to the AS through the I-CSCF or the S-CSCF.

[0312] In some embodiments, the first network device selects a target P-CSCF from the at least one P-CSCF, and forwards the first information to the target P-CSCF.

[0313] In some embodiments, the first network device sends the first information to a P-CSCF selected by the first network device from the at least one P-CSCF based on a preconfigured list.

[0314] For example, the preconfigured list includes identification information of each P-CSCF in at least one P-CSCF. The P-CSCF identification information is used to uniquely identify the P-CSCF. For example, the P-CSCF identification information includes at least one of the following: a P-CSCF address, a P-CSCF name, and a P-CSCF network identifier.

[0315] In some embodiments, the first network device selects a target P-CSCF from the at least one P-CSCF in a round-robin manner based on a preconfigured list.

[0316] In some embodiments, the first network device sends the first information to the second network device via a first interface between the first network device and the second network device. For example, the AMF in the first network device sends the first information to the P-CSCF in the second network device via a first interface between the AMF and the P-CSCF. For another example, the SMF in the first network device sends the first information to the P-CSCF via a second interface between the SMF and the P-CSCF in the second network device. For another example, the PCF in the first network device sends the first information to the P-CSCF via a third interface between the PCF and the P-CSCF in the second network device.

[0317] Step S2105: The second network device determines the fourth information.

[0318] In some embodiments, the fourth information is used to indicate an IMS registration result of the terminal.

[0319] For example, the fourth information is a success status code, the first status information indicates that the IMS registration result of the terminal is successful, and the fourth information is a failure status code, indicating that the IMS registration result of the terminal is failed.

[0320] In some embodiments, the second network device includes a P-CSCF, the P-CSCF sends the first information to the AS through the I-CSCF or the S-CSCF, and receives fourth information fed back by the AS based on the first information.

[0321] For example, after receiving the first information, the P-CSCF sends the first information and the identification information of the P-CSCF to the I-CSCF or the S-CSCF.

[0322] In some embodiments, the second network device binds the terminal's identifier to the identifier or IP address of the first network device for signaling interaction of the terminal.

[0323] In some embodiments, the second network device includes an S-CSCF. Based on the initial filtering condition for the correct AS, the S-CSCF sends registration information to the AS through third-party registration and performs a service control process.

[0324] In some embodiments, the second network device includes an AS, and the AS returns the fourth information to the P-CSCF through the S-CSCF.

[0325] Step S2106: The second network device sends fourth information to the first network device.

[0326] In some embodiments, the first network device receives fourth information sent by the second network device.

[0327] In some embodiments, the second network device sends the fourth information to the first network device through a first interface between the first network device and the second network device.

[0328] Step S2107: The first network device sends fourth information to the terminal.

[0329] In some embodiments, the terminal receives fourth information sent by the first network device.

[0330] In some embodiments, the terminal receives a fourth NAS message carrying fourth information sent by the first network device.

[0331] For example, the fourth information is carried in a downlink NAS transmission message sent by the first network device to the terminal.

[0332] In some embodiments, the term "information" can be interchangeable with terms such as "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "field", and "data".

[0333] In some embodiments, the term "send" can be interchanged with terms such as "transmit", "report", and "transmit".

[0334] The information transmission method involved in the embodiments of the present disclosure may include at least one of steps S2101 to S2107. For example, step S2101 may be implemented as an independent embodiment, and step S2103 may be implemented as an independent embodiment. For example, step S2101 combined with step S2107 may be implemented as an independent embodiment, and steps S2103 to S2107 may be implemented as independent embodiments, but the present disclosure is not limited thereto.

[0335] In some embodiments, step S2101 and step S2102 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0336] FIG3a is a flow chart of an information transmission method according to an embodiment of the present disclosure. As shown in FIG3a, the present disclosure embodiment relates to an information transmission method, which is executed by terminal 101 and includes:

[0337] Step S3101: Send the second information.

[0338] In some embodiments, the optional implementation of step S3101 can refer to the optional implementation of step S2101 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0339] In some embodiments, the terminal sends the second information to the first network device, but is not limited thereto, and the second information may also be sent to other entities.

[0340] Optionally, the second information is used by the first network device to send the third information to the terminal. The optional implementation method thereof can refer to the optional implementation method of step S2102 of FIG2 and other related parts of the embodiment involved in FIG2, which will not be repeated here.

[0341] Step S3102: Obtain third information.

[0342] In some embodiments, the optional implementation of step S3102 can refer to the optional implementation of step S2102 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0343] In some embodiments, the terminal receives the third information sent by the first network device, but is not limited thereto, and may also receive the third information sent by other entities.

[0344] In some embodiments, the terminal obtains third information specified by the protocol.

[0345] In some embodiments, the terminal obtains the third information from upper layer(s).

[0346] In some embodiments, the terminal performs processing to obtain the third information.

[0347] In some embodiments, step S3102 is omitted, and the terminal autonomously implements the function indicated by the third information, or the above function is default or by default.

[0348] Step S3103: Send the first information.

[0349] In some embodiments, the optional implementation of step S3103 can refer to the optional implementation of step S2103 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0350] In some embodiments, the terminal sends the first information to the first network device, but is not limited thereto, and the first information may also be sent to other entities.

[0351] Step S3104: Obtain fourth information.

[0352] In some embodiments, the optional implementation of step S3104 can refer to the optional implementation of step S2107 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0353] In some embodiments, the terminal receives the fourth information sent by the first network device, but is not limited thereto, and may also receive the fourth information sent by other entities.

[0354] In some embodiments, the terminal obtains fourth information specified by the protocol.

[0355] In some embodiments, the terminal obtains the fourth information from an upper layer(s).

[0356] In some embodiments, the terminal performs processing to obtain the fourth information.

[0357] In some embodiments, step S3104 is omitted, and the terminal autonomously implements the function indicated by the fourth information, or the above function is default or by default.

[0358] The information transmission method involved in the embodiments of the present disclosure may include at least one of steps S3101 to S3104. For example, step S3101 may be implemented as an independent embodiment, and step S3103 may be implemented as an independent embodiment. For example, steps S3101 to S3104 may be implemented as an independent embodiment, and steps S3103 to S3104 may be implemented as independent embodiments, but are not limited thereto.

[0359] In some embodiments, step S3101 and step S3102 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0360] FIG3a is a flow chart of an information transmission method according to an embodiment of the present disclosure. As shown in FIG3a, the present disclosure embodiment relates to an information transmission method, which is executed by terminal 101 and includes:

[0361] Step S3101: Send the second information.

[0362] In some embodiments, the optional implementation of step S3101 can refer to the optional implementation of step S2101 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0363] In some embodiments, the terminal sends the second information to the first network device, but is not limited thereto, and the second information may also be sent to other entities.

[0364] Optionally, the second information is used by the first network device to send the third information to the terminal. The optional implementation method thereof can refer to the optional implementation method of step S2102 of FIG2 and other related parts of the embodiment involved in FIG2, which will not be repeated here.

[0365] Step S3102: Obtain third information.

[0366] In some embodiments, the optional implementation of step S3102 can refer to the optional implementation of step S2102 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0367] In some embodiments, the terminal receives the third information sent by the first network device, but is not limited thereto, and may also receive the third information sent by other entities.

[0368] In some embodiments, the terminal obtains third information specified by the protocol.

[0369] In some embodiments, the terminal obtains the third information from upper layer(s).

[0370] In some embodiments, the terminal performs processing to obtain the third information.

[0371] In some embodiments, step S3102 is omitted, and the terminal autonomously implements the function indicated by the third information, or the above function is default or by default.

[0372] Step S3103: Send the first information.

[0373] In some embodiments, the optional implementation of step S3103 can refer to the optional implementation of step S2103 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0374] In some embodiments, the terminal sends the first information to the first network device, but is not limited thereto, and the first information may also be sent to other entities.

[0375] Step S3104: Obtain fourth information.

[0376] In some embodiments, the optional implementation of step S3104 can refer to the optional implementation of step S2107 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0377] In some embodiments, the terminal receives the fourth information sent by the first network device, but is not limited thereto, and may also receive the fourth information sent by other entities.

[0378] In some embodiments, the terminal obtains fourth information specified by the protocol.

[0379] In some embodiments, the terminal obtains the fourth information from an upper layer(s).

[0380] In some embodiments, the terminal performs processing to obtain the fourth information.

[0381] In some embodiments, step S3104 is omitted, and the terminal autonomously implements the function indicated by the fourth information, or the above function is default or by default.

[0382] The information transmission method involved in the embodiments of the present disclosure may include at least one of steps S3101 to S3104. For example, step S3101 may be implemented as an independent embodiment, and step S3103 may be implemented as an independent embodiment. For example, steps S3101 to S3104 may be implemented as an independent embodiment, and steps S3103 to S3104 may be implemented as independent embodiments, but are not limited thereto.

[0383] In some embodiments, step S3101 and step S3102 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0384] FIG3b is a flow chart of an information transmission method according to an embodiment of the present disclosure. As shown in FIG3b, the present disclosure embodiment relates to an information transmission method, which is executed by terminal 101 and includes:

[0385] Step S3201: Send the first information.

[0386] In some embodiments, the optional implementation of step S3201 can refer to the optional implementation of step S2103 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0387] In some embodiments, the terminal sends the first information to the first network device, but is not limited thereto, and the first information may also be sent to other entities.

[0388] Step S3202: Obtain fourth information.

[0389] In some embodiments, the optional implementation of step S3202 can refer to the optional implementation of step S2107 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0390] In some embodiments, the terminal receives the fourth information sent by the first network device, but is not limited thereto, and may also receive the fourth information sent by other entities.

[0391] In some embodiments, the terminal obtains fourth information specified by the protocol.

[0392] In some embodiments, the terminal obtains the fourth information from an upper layer(s).

[0393] In some embodiments, the terminal performs processing to obtain the fourth information.

[0394] In some embodiments, step S3202 is omitted, and the terminal autonomously implements the function indicated by the fourth information, or the above function is default or by default.

[0395] Figure 3c is a flow chart of an information transmission method according to an embodiment of the present disclosure. As shown in Figure 3c, the present disclosure embodiment relates to an information transmission method, which is executed by a terminal. The method includes:

[0396] Step S3301: Send first information to the P-CSCF through the control plane network element of the core network.

[0397] In some embodiments, the first information is used to perform IMS registration on the terminal.

[0398] In some embodiments, the optional implementation of step S3301 can refer to the optional implementation of step S2103 in Figure 2, step S3103 in Figure 3a, step S3201 in Figure 3b, and other related parts in the embodiments involved in Figures 2, 3a, and 3b, which will not be repeated here.

[0399] In some embodiments, in step S3301, sending first information to the P-CSCF through a control plane network element of the core network includes:

[0400] A first NAS message is sent to the control plane network element, so that the first information carried by the NAS message is sent to the P-CSCF through the control plane network element.

[0401] In some embodiments, the method further comprises:

[0402] Step S3302: Send second information to the control plane network element through the access network device, wherein the second information is used to indicate that the terminal supports IMS registration through NAS.

[0403] The optional implementation of step S3302 can refer to step S2101 in Figure 2, the optional implementation of step S3101 in Figure 3a, and other related parts in the embodiments involved in Figures 2 and 3a, which will not be repeated here.

[0404] In some embodiments, in step S3302, the sending a first NAS message to the control plane network element includes:

[0405] In response to receiving third information sent by the control plane network element through the access network device, the first NAS message is sent to the control plane network element, wherein the third information is used to indicate that the control plane network element supports IMS registration through NAS.

[0406] In some examples, the third information sent by the control plane network element through the access network device is received. The optional implementation method of this step can be referred to step S2102 of Figure 2, the optional implementation method of step S3102 of Figure 3a, and other related parts in the embodiments involved in Figures 2 and 3a, which will not be repeated here.

[0407] In some embodiments, the second information is carried in a registration request message, and the third information is carried in a registration accept message;

[0408] Alternatively, the second information is carried in the first RRC message, and the third information is carried in the second RRC message;

[0409] Alternatively, the second information is carried in a second NAS message, and the third information is carried in a third NAS message.

[0410] In some embodiments, the first information is carried in a first container of the first NAS message, where the first container is used for IMS registration.

[0411] In some embodiments, the method further comprises:

[0412] Step S3303: Receive, through the control plane network element, fourth information sent by the P-CSCF according to the first information; wherein the fourth information is used to indicate the IMS registration result of the terminal.

[0413] The optional implementation of step S3303 can refer to the optional implementation of step S2107 in Figure 2, step S3104 in Figure 3a, step S3203 in Figure 3b, and other related parts in the embodiments involved in Figures 2, 3a, and 3b, which will not be repeated here.

[0414] In some embodiments, the fourth information is carried in a fourth NAS message sent by the control plane network element to the terminal.

[0415] In some embodiments, the control plane network element includes at least one of the following:

[0416] AMF network element;

[0417] SMF network element;

[0418] PCF network element.

[0419] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0420] FIG4a is a flow chart of an information transmission method according to an embodiment of the present disclosure. As shown in FIG4a, the present disclosure embodiment relates to an information transmission method, which is executed by the first network device 102. The method includes:

[0421] Step S4101: Obtain the second information.

[0422] In some embodiments, the optional implementation of step S4101 can refer to the optional implementation of step S2101 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0423] In some embodiments, the first network device receives the second information sent by the terminal, but is not limited thereto and may also receive the second information sent by other entities.

[0424] In some embodiments, the first network device obtains second information specified by the protocol.

[0425] In some embodiments, the first network device performs processing to obtain the second information.

[0426] In some embodiments, step S4101 is omitted, the first network device autonomously implements the function indicated by the second information, or the above function is default or by default.

[0427] Step S4102: Send the third information.

[0428] In some embodiments, the optional implementation of step S4102 can refer to the optional implementation of step S2102 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0429] In some embodiments, the first network device sends the third information to the terminal, but is not limited thereto, and the third information may also be sent to other entities.

[0430] Step S4103: Obtain first information.

[0431] In some embodiments, the optional implementation of step S4103 can refer to the optional implementation of step S2103 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0432] In some embodiments, the first network device receives the first information sent by the terminal, but is not limited thereto and may also receive the second information sent by other entities.

[0433] In some embodiments, the first network device obtains first information specified by a protocol.

[0434] In some embodiments, the first network device performs processing to obtain the first information.

[0435] In some embodiments, step S4103 is omitted, the first network device autonomously implements the function indicated by the first information, or the above function is default or by default.

[0436] Step S4104: Send the first message.

[0437] In some embodiments, the optional implementation of step S4104 can refer to the optional implementation of step S2104 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0438] In some embodiments, the first network device sends the first information to the second network device, but is not limited thereto, and the first information may also be sent to other entities.

[0439] Step S4105: Obtain the fourth information.

[0440] In some embodiments, the optional implementation of step S4105 can refer to the optional implementation of step S2106 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0441] In some embodiments, the first network device receives the fourth information sent by the second network device, but is not limited thereto and may also receive the fourth information sent by other entities.

[0442] In some embodiments, the first network device obtains fourth information specified by the protocol.

[0443] In some embodiments, the first network device performs processing to obtain the fourth information.

[0444] In some embodiments, step S4105 is omitted, the first network device autonomously implements the function indicated by the fourth information, or the above function is default or by default.

[0445] Step S4106: Send the fourth message.

[0446] In some embodiments, the optional implementation of step S4106 can refer to the optional implementation of step S2107 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0447] In some embodiments, the first network device sends the fourth information to the terminal, but is not limited thereto, and the fourth information may also be sent to other entities.

[0448] The information transmission method involved in the embodiments of the present disclosure may include at least one of steps S4101 to S4106. For example, step S4101 can be implemented as an independent embodiment, and step S4103 can be implemented as an independent embodiment. For example, step S4101 combined with steps S4103 to S4106 can be implemented as an independent embodiment, and steps S4103 to S4106 can be implemented as independent embodiments, but the present invention is not limited thereto.

[0449] In some embodiments, step S4101 and step S4102 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0450] Figure 4b is a flow chart of an information transmission method according to an embodiment of the present disclosure. As shown in Figure 4b, the present disclosure embodiment relates to an information transmission method, which is executed by a control plane network element of a core network. The method includes:

[0451] Step S4201: receiving first information sent by a terminal;

[0452] Step S4202: Send the first information to the P-CSCF.

[0453] In some embodiments, the first information is used to register the terminal with IMS

[0454] Optional implementations of step S4201 can refer to step S2103 in FIG. 2 , optional implementations of step S4103 in FIG. 4 a , and other related parts in the embodiments involved in FIG. 2 and FIG. 4 a , which will not be described in detail here.

[0455] Optional implementations of step S4202 can be found in step S2104 of FIG. 2 , optional implementations of step S4104 of FIG. 4 a , and other related parts in the embodiments involved in FIG. 2 and FIG. 4 a , which will not be described in detail here.

[0456] In some embodiments, in step S4201, the receiving terminal sends the first information, including:

[0457] Receive a first NAS message sent by the terminal; wherein the NAS message carries the first information.

[0458] In some embodiments, the method further comprises:

[0459] Step S4203: Receive second information sent by the terminal through the access network device, wherein the second information is used to indicate that the terminal supports IMS registration through NAS.

[0460] The optional implementation of step S4203 can refer to step S2101 in Figure 2, the optional implementation of step S4101 in Figure 4a, and other related parts in the embodiments involved in Figures 2 and 4a, which will not be repeated here.

[0461] In some embodiments, the method further comprises:

[0462] Step S4204: Send third information to the terminal through the access network device, wherein the third information is used to indicate that the control plane network element supports IMS registration through NAS.

[0463] The optional implementation of step S4204 can refer to step S2102 in FIG. 2 , the optional implementation of step S4102 in FIG. 4 a , and other related parts in the embodiments involved in FIG. 2 and FIG. 4 a , which will not be described in detail here.

[0464] In some embodiments, the second information is carried in a registration request message, and the third information is carried in a registration accept message;

[0465] Alternatively, the second information is carried in the first RRC message, and the third information is carried in the second RRC message;

[0466] Alternatively, the second information is carried in a second NAS message, and the third information is carried in a third NAS message.

[0467] In some embodiments, the first information is carried in a first container of the first NAS message, where the first container is used for IMS registration.

[0468] In some embodiments, the method further comprises:

[0469] In response to receiving fourth information sent by the P-CSCF according to the first information, the fourth information is sent to the terminal, wherein the fourth information is used to indicate an IMS registration result of the terminal.

[0470] In some examples, the fourth information sent by the P-CSCF based on the first information is received. For optional implementation methods of this step, please refer to step S2106 of Figure 2, the optional implementation methods of step S4104 of Figure 4a, and other related parts in the embodiments involved in Figures 2 and 4a, which will not be repeated here.

[0471] In some embodiments, the fourth information is carried in a fourth NAS message sent by the control plane network element to the terminal.

[0472] In some embodiments, the control plane network element includes at least one of the following:

[0473] AMF network element;

[0474] SMF network element;

[0475] PCF network element.

[0476] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0477] Figure 4c is a flow chart of an information transmission method according to an embodiment of the present disclosure. As shown in Figure 4c, the embodiment of the present disclosure relates to an information transmission method, which is executed by a second network device, and the method includes:

[0478] Step S4301: Obtain first information.

[0479] In some embodiments, the optional implementation of step S4301 can refer to the optional implementation of step S2104 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0480] In some embodiments, the second network device receives the first information sent by the first network device, but is not limited thereto and may also receive the first information sent by other entities.

[0481] In some embodiments, the second network device obtains first information specified by the protocol.

[0482] In some embodiments, the second network device obtains the first information from an upper layer(s).

[0483] In some embodiments, the second network device performs processing to obtain the first information.

[0484] In some embodiments, step S4301 is omitted, the second network device autonomously implements the function indicated by the first information, or the above function is default or by default.

[0485] Step S4302: Determine the fourth information.

[0486] In some embodiments, the optional implementation of step S4302 can refer to the optional implementation of step S2105 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0487] In some embodiments, the second network device includes a P-CSCF, and the P-CSCF sends the first information to the AS through the I-CSCF or the S-CSCF, and receives fourth information fed back by the AS based on the first information.

[0488] Step S4303: Send the fourth message.

[0489] In some embodiments, the optional implementation of step S4303 can refer to the optional implementation of step S2106 in Figure 2 and other related parts of the embodiment involved in Figure 2, which will not be repeated here.

[0490] In some embodiments, the second network device sends the fourth information to the first network device, but is not limited thereto, and the fourth information may also be sent to other entities.

[0491] The information transmission method involved in the embodiments of the present disclosure may include at least one of steps S4301 to S4303. For example, step S4301 can be implemented as an independent embodiment, and step S4303 can be implemented as an independent embodiment. For example, steps S4301 to S4302 can be implemented as an independent embodiment, and steps S4301 to S4303 can be implemented as an independent embodiment, but are not limited thereto.

[0492] In some embodiments, step S4301 is optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0493] Figure 4d is an interactive diagram of an information transmission method according to an embodiment of the present disclosure. As shown in Figure 4d, the embodiment of the present disclosure relates to an information transmission method, which is executed by a P-CSCF, and the method includes:

[0494] Step S4401: Receive first information sent by a terminal through a control plane network element of a core network.

[0495] In some embodiments, the first information is used to perform IMS registration on the terminal.

[0496] The optional implementation of step S4401 can refer to step S2104 in FIG. 2 , the optional implementation of step S4201 in FIG. 4 c , and other related parts in the embodiments involved in FIG. 2 and FIG. 4 c , which will not be described in detail here.

[0497] In some embodiments, in step S4401, receiving first information sent by a terminal through a control plane network element of a core network includes:

[0498] First information sent by the control plane network element is received, where the first information is carried in a first NAS message sent by the terminal to the control plane network element.

[0499] In some embodiments, the method further comprises:

[0500] Step S4402: Send fourth information to the terminal through the control plane network element, where the fourth information is used to indicate the IMS registration result of the terminal.

[0501] The optional implementation of step S4402 can refer to step S2106 and step S2107 in Figure 2, the optional implementation of step S4203 in Figure 4c, and other related parts in the embodiments involved in Figures 2 and 4c, which will not be repeated here.

[0502] In some embodiments, the method further comprises:

[0503] Step S4403: Determine the fourth information.

[0504] The optional implementation of step S4403 can refer to step S2105 in FIG. 2 , the optional implementation of step S4302 in FIG. 4 c , and other related parts in the embodiments involved in FIG. 2 and FIG. 4 c , which will not be described in detail here.

[0505] In some embodiments, the control plane network element includes at least one of the following:

[0506] AMF network element;

[0507] SMF network element;

[0508] PCF network element.

[0509] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0510] FIG5 is an interactive diagram of an information transmission method according to an embodiment of the present disclosure. As shown in FIG5 , the embodiment of the present disclosure relates to an information transmission method, and the method includes:

[0511] Step S5101: The terminal sends first information to a control plane network element of the core network;

[0512] Step S5102: The control plane network element sends the first information to the P-CSCF.

[0513] In some embodiments, the first information is used to register the terminal with IMS

[0514] In some embodiments, the optional implementation methods of step S5101 can refer to the optional implementation methods of step S2103 in Figure 2, step S3103 in Figure 3a, step S3201 in Figure 3b, step S3301 in Figure 3c, and other related parts in the embodiments involved in Figures 2, 3a, 3b, and 3c, which will not be repeated here.

[0515] In some embodiments, in step S5101, the terminal sends first information to a control plane network element of the core network, including:

[0516] The terminal sends a first NAS message to the control plane network element, where the NAS message carries the first information.

[0517] In some embodiments, the method further comprises:

[0518] Step S5102: The terminal sends second information to the control plane network element through the access network device, wherein the second information is used to indicate that the terminal supports IMS registration through NAS.

[0519] Optional implementations of step S5102 may refer to step S2101 in FIG. 2 , optional implementations of step S3101 in FIG. 3 a , and other related parts in the embodiments involved in FIG. 2 and FIG. 3 a , which will not be described in detail here.

[0520] In some embodiments, the method further comprises:

[0521] Step S5103: The control plane network element sends third information to the terminal through the access network device, wherein the third information is used to indicate that the control plane network element supports IMS registration through NAS.

[0522] The optional implementation of step S5103 can refer to the optional implementation of step S2102 in Figure 2, step S4102 in Figure 4a, and other related parts in the embodiments involved in Figures 2 and 4a, which will not be repeated here.

[0523] In some embodiments, in step S5102, the terminal sends a first NAS message to the control plane network element, including:

[0524] In response to receiving the third information sent by the control plane network element through the access network device, the terminal sends the first NAS message to the control plane network element, wherein the third information is used to indicate that the control plane network element supports IMS registration through NAS.

[0525] In some examples, the third information sent by the control plane network element through the access network device is received. The optional implementation method of this step can be referred to step S2102 of Figure 2, the optional implementation method of step S3102 of Figure 3a, and other related parts in the embodiments involved in Figures 2 and 3a, which will not be repeated here.

[0526] In some embodiments, the second information is carried in a registration request message, and the third information is carried in a registration accept message;

[0527] Alternatively, the second information is carried in the first RRC message, and the third information is carried in the second RRC message;

[0528] Alternatively, the second information is carried in a second NAS message, and the third information is carried in a third NAS message.

[0529] In some embodiments, the first information is carried in a first container of the first NAS message, where the first container is used for IMS registration.

[0530] In some embodiments, the method further comprises:

[0531] Step S5103: Receive, through the control plane network element, fourth information sent by the P-CSCF according to the first information; wherein the fourth information is used to indicate the IMS registration result of the terminal.

[0532] The optional implementation of step S5103 can refer to the optional implementation of step S2107 in Figure 2, step S3104 in Figure 3a, step S3203 in Figure 3b, and other related parts in the embodiments involved in Figures 2, 3a, and 3b, which will not be repeated here.

[0533] In some embodiments, the fourth information is carried in a fourth NAS message sent by the control plane network element to the terminal.

[0534] In some embodiments, the control plane network element includes at least one of the following:

[0535] AMF network element;

[0536] SMF network element;

[0537] PCF network element.

[0538] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0539] FIG6 is an interactive diagram illustrating an information transmission method according to an embodiment of the present disclosure. As shown in FIG6b , the present disclosure embodiment relates to an information transmission method, the method comprising:

[0540] Step S6101: UE sends a registration request message.

[0541] In some examples, the registration request carries information indicating that the UE supports IMS registration via NAS.

[0542] In some examples, the UE sends an RRC establishment request to the RAN, including a registration request, and the UE may indicate its capability of "supporting IMS registration via NAS" in the registration request.

[0543] In some examples, the registration request also includes registration type, UEID (suci or 5G-GUTI or PEI), and security parameters.

[0544] In some examples, the RAN forwards the registration request to the AMF over the N2 interface.

[0545] Step S6102: AMF sends a registration accept message to the UE.

[0546] In some examples, the Registration Accept message carries information indicating that the AMF supports IMS registration via NAS.

[0547] In some examples, after the UE passes authentication and authorization, the AMF sends a registration accept message to the UE through the RAN. If the UE indicates its capability of "supporting IMS registration through NAS" in the registration request, the AMF can indicate its network capability of "supporting IMS registration".

[0548] Step S6103: The UE sends an uplink NAS transmission message, which carries an IMS registration information flow.

[0549] In some examples, according to the received network capability “support IMS registration via NAS”, the UE may register with the IMS via NAS.

[0550] In some examples, the UE carries the registration information flow as a NAS container in an uplink NAS transport message and sends it to the P-CSCF.

[0551] In some examples, the registration information flow includes a public user identity (PUI), a private user identity (PVI), a home network domain name, and the like.

[0552] A new NAS container type is added to the uplink NAS transport message to indicate that the container is used for IMS registration.

[0553] Step S6104: AMF sends a registration information flow to P-CSCF.

[0554] In some examples, the AMF receives an uplink NAS transport message from the UE, determines that the container is for IMS registration based on the NAS container type in the uplink NAS transport message, selects a P-CSCF, for example, pre-configured on the AMF, and forwards the registration information flow to the P-CSCF.

[0555] Step S6105: The P-CSCF sends the registration information flow to the I-CSCF or S-CSCF.

[0556] In some examples, after receiving the registration information flow, the P-CSCF sends the registration information flow to the I-CSCF or S-CSCF, and sends the P-CSCF address / name, public user identity, private user identity, and P-CSCF network identifier.

[0557] In some examples, after receiving the registration information flow, the I-CSCF sends the registration information flow to the S-CSCF.

[0558] In some examples, the P-CSCF binds the UE (UE ID) with the AMF (AMF ID or IP address) for signaling interaction of the UE.

[0559] Step S6106: The S-CSCF sends registration information to the AS.

[0560] In some examples, based on the initial filtering conditions for the correct AS, the S-CSCF sends registration information to the AS through third-party registration and performs service control procedures.

[0561] Step S6107: AS sends a 200OK information flow to S-CSCF, indicating that the registration is successful.

[0562] Step S6108: The S-CSCF returns the 200 OK information flow to the P-CSCF to indicate that the registration is successful.

[0563] Step S6109: The P-CSCF sends a 200OK information flow to the terminal through the AMF, indicating that the registration is successful.

[0564] Step S6110: The AMF sends a downlink NAS transport message to the terminal, which includes a 200OK information flow.

[0565] The information transmission method involved in the embodiments of the present disclosure may include at least one of steps S6201 to S6110. For example, step S6101 may be implemented as an independent embodiment, and step S6103 may be implemented as an independent embodiment. For example, steps S6101 to S6110 may be implemented as an independent embodiment, and steps S6103 to S6110 may be implemented as an independent embodiment, but the present invention is not limited thereto.

[0566] In some embodiments, step S6101 and step S6103 may be executed simultaneously, and step S6102 and step S6104 may be executed in an exchanged order or simultaneously.

[0567] In some embodiments, step S6101 and step S6103 may be executed simultaneously, step S6102 and step S6104 may be swapped in order, and step S6102 and step S6110 may be executed simultaneously.

[0568] In some embodiments, step S6101 and step S6102 are optional, and one or more of these steps may be omitted or replaced in different embodiments.

[0569] In the embodiments of the present disclosure, some or all of the steps and their optional implementations may be arbitrarily combined with some or all of the steps in other embodiments, or may be arbitrarily combined with the optional implementations of other embodiments.

[0570] The embodiments of the present disclosure also provide an apparatus for implementing any of the above information transmission methods. For example, an information transmission apparatus is provided, wherein the information transmission apparatus includes a unit or module for implementing each step performed by a terminal in any of the above information transmission methods. For another example, another information transmission apparatus is provided, including a unit or module for implementing each step performed by a first network device (for example, a control plane network element of a core network) in any of the above methods. For another example, another information transmission apparatus is provided, including a unit or module for implementing each step performed by a second network device (for example, a P-CSCF) in any of the above methods.

[0571] It should be understood that the division of the various units or modules in the above devices is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above devices, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0572] In the embodiments of the present disclosure, a processor is a circuit with signal processing capabilities. In one implementation, the processor can be a circuit with instruction reading and execution capabilities, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP). In another implementation, the processor can implement certain functions through the logical relationships of hardware circuits. The logical relationships of the above-mentioned hardware circuits are fixed or reconfigurable. For example, the processor is a hardware circuit implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document to implement the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0573] Figure 7a is a structural diagram of a terminal provided by an embodiment of the present disclosure. As shown in Figure 7a, the terminal 7100 includes: a sending module 7101; the sending module 7101 is configured to send a first message to the P-CSCF through the control plane network element of the core network, wherein the first information is used to perform IMS registration for the terminal. Optionally, the sending module 7101 is used to execute the steps related to information sending executed by the terminal in any of the above information transmission methods, which are not repeated here. Optionally, the terminal 7100 also includes a receiving module, and the above receiving module is used to execute the steps related to reception executed by the terminal in any of the above information transmission methods, which are not repeated here.

[0574] Figure 7b is a structural diagram of the control plane network element of the core network provided by an embodiment of the present disclosure. As shown in Figure 7b, the control plane network element 7200 includes: a receiving module 7201 and a sending module 7202, which are configured to receive the first information sent by the terminal, wherein the first information is used to perform IMS registration for the terminal. Optionally, the receiving module 7201 is used to execute the steps related to information reception performed by the control plane network element of the core network in any of the above information transmission methods, which will not be repeated here. The above-mentioned sending module is used to execute the steps related to sending performed by the control plane network element of the core network in any of the above methods, which will not be repeated here.

[0575] Figure 7c is a schematic diagram of the structure of the P-CSCF provided by an embodiment of the present disclosure. As shown in Figure 7c, the P-CSCF 7300 includes: a receiving module 7301, configured to receive first information sent by a terminal through a control plane network element of the core network, wherein the first information is used to register the terminal with the IMS. Optionally, the receiving module 7301 is used to execute the steps related to information reception performed by the P-CSCF in any of the above information transmission methods, which are not repeated here. Optionally, the P-CSCF 7300 also includes a sending module, which is used to execute the steps related to sending performed by the P-CSCF in any of the above information transmission methods, which are not repeated here.

[0576] Figure 8a is a schematic diagram of the structure of a communication device 8100 provided in an embodiment of the present disclosure. Communication device 8100 can be a network device (e.g., a control plane network element of a core network, a P-CSCF in an IMS network, etc.), a terminal (e.g., user equipment, etc.), a chip, chip system, or processor that supports a network device in implementing any of the above methods, or a chip, chip system, or processor that supports a terminal in implementing any of the above information transmission methods. Communication device 8100 can be used to implement the information transmission method described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0577] As shown in Figure 8a, the communication device 8100 includes one or more processors 8101. The processor 8101 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control the communication device (such as a base station, a baseband chip, a terminal device, a terminal device chip, a DU or a CU, etc.), execute programs, and process program data. The processor 8101 is used to call instructions to enable the communication device 8100 to execute any of the above communication methods.

[0578] In some embodiments, the communication device 8100 further includes one or more memories 8102 for storing instructions. Optionally, all or part of the memories 8102 may be located outside the communication device 8100.

[0579] In some embodiments, the communication device 8100 further includes one or more transceivers 8103. When the communication device 8100 includes one or more transceivers 8103, the communication steps such as sending and receiving in the above method are performed by the transceiver 8103, and the other steps are performed by the processor 8101.

[0580] In some embodiments, a transceiver may include a receiver and a transmitter, which may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0581] Optionally, the communication device 8100 further includes one or more interface circuits 8104, which are connected to the memory 8102. The interface circuits 8104 can be used to receive signals from the memory 8102 or other devices, and can be used to send signals to the memory 8102 or other devices. For example, the interface circuits 8104 can read instructions stored in the memory 8102 and send the instructions to the processor 8101.

[0582] The communication device 8100 described in the above embodiment may be a network device or a terminal, but the scope of the communication device 8100 described in the present disclosure is not limited thereto, and the structure of the communication device 8100 may not be limited by FIG. 8a. The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: (1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data or programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0583] FIG8b is a schematic diagram of the structure of a chip 8200 provided in an embodiment of the present disclosure. If the communication device 8100 can be a chip or a chip system, please refer to the schematic diagram of the structure of the chip 8200 shown in FIG8b, but the present disclosure is not limited thereto.

[0584] The chip 8200 includes one or more processors 8201 , and the processor 8201 is used to call instructions so that the chip 8200 executes any of the above communication methods.

[0585] In some embodiments, chip 8200 further includes one or more interface circuits 8202, which are connected to memory 8203. Interface circuit 8202 can be used to receive signals from memory 8203 or other devices, and can be used to send signals to memory 8203 or other devices. For example, interface circuit 8202 can read instructions stored in memory 8203 and send the instructions to processor 8201. Optionally, the terms interface circuit, interface, transceiver pin, and transceiver are interchangeable.

[0586] In some embodiments, the chip 8200 further includes one or more memories 8203 for storing instructions. Alternatively, all or part of the memories 8203 may be outside the chip 8200.

[0587] The present disclosure also provides a storage medium having instructions stored thereon, which, when executed on the communication device 8100, causes the communication device 8100 to execute any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but may also be a transient storage medium.

[0588] The present disclosure further provides a program product, which, when executed by the communication device 8100, enables the communication device 8100 to perform any of the above communication methods. Optionally, the program product is a computer program product.

[0589] The present disclosure also provides a computer program, which, when executed on a computer, enables the computer to execute any one of the above communication methods.

[0590] Other embodiments of the present invention will readily occur to those skilled in the art after considering the specification and practicing the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the invention that follow from the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the invention being indicated by the following claims.

[0591] It should be understood that the present invention is not limited to the exact construction described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A method for transmitting information, wherein: Executed by a terminal, the method includes: The first information is sent to a proxy call session control function P-CSCF through a control plane network element of the core network, wherein the first information is used to register the terminal with an Internet Protocol Multimedia Subsystem IMS.

2. The method according to claim 1, wherein: The sending the first information to the proxy call session control function P-CSCF through the control plane network element of the core network includes: A first non-access layer NAS message is sent to the control plane network element, so that the first information carried by the NAS message is sent to the P-CSCF through the control plane network element.

3. The method according to claim 2, wherein: The method further comprises: Sending second information to the control plane network element through the access network device, wherein the second information is used to indicate that the terminal supports IMS registration through NAS.

4. The method according to claim 3, wherein: The sending a first non-access layer NAS message to the control plane network element includes: In response to receiving third information sent by the control plane network element through the access network device, sending the first NAS message to the control plane network element, wherein the third information is used to indicate that the control plane network element supports IMS registration through NAS.

5. The method according to claim 4, wherein: The second information is carried in a registration request message, and the third information is carried in a registration acceptance message; or, The second information is carried in a first radio resource control RRC message, and the third information is carried in a second RRC message; or, The second information is carried in a second NAS message, and the third information is carried in a third NAS message.

6. The method according to any one of claims 2 to 5, wherein: The first information is carried in a first container of the first NAS message, where the first container is used for IMS registration.

7. The method according to any one of claims 1 to 6, wherein: The method further comprises: The fourth information sent by the P-CSCF according to the first information is received through the control plane network element; wherein the fourth information is used to indicate the IMS registration result of the terminal.

8. The method according to claim 7, wherein: The fourth information is carried in a fourth NAS message sent by the control plane network element to the terminal.

9. The method according to any one of claims 1 to 8, wherein: The control plane network element includes at least one of the following: Access and mobility management function AMF network element; Session management function SMF network element; Policy control function PCF network element.

10. A method for transmitting information, wherein: The method is performed by a control plane network element of a core network, and includes: Receiving first information sent by a terminal, wherein the first information is used to register the terminal with an Internet Protocol Multimedia Subsystem IMS; The first information is sent to a proxy call session control function P-CSCF.

11. The method according to claim 10, wherein: The first information sent by the receiving terminal includes: Receive a first non-access stratum NAS message sent by the terminal; wherein the NAS message carries the first information.

12. The method according to claim 11, wherein: The method further comprises: Second information sent by the terminal through an access network device is received, wherein the second information is used to indicate that the terminal supports IMS registration through NAS.

13. The method according to claim 12, wherein: The method further comprises: Sending third information to the terminal through the access network device, wherein the third information is used to indicate that the control plane network element supports IMS registration through NAS.

14. The method according to claim 13, wherein: The second information is carried in a registration request message, and the third information is carried in a registration acceptance message; or, The second information is carried in a first radio resource control RRC message, and the third information is carried in a second RRC message; or, The second information is carried in a second NAS message, and the third information is carried in a third NAS message.

15. The method according to any one of claims 11 to 14, wherein: The first information is carried in a first container of the first NAS message, where the first container is used for IMS registration.

16. The method according to any one of claims 10 to 15, wherein: The method further comprises: In response to receiving fourth information sent by the P-CSCF according to the first information, sending the fourth information to the terminal, wherein the fourth information is used to indicate an IMS registration result of the terminal.

17. The method according to claim 16, wherein: The fourth information is carried in a fourth NAS message sent by the control plane network element to the terminal.

18. The method according to any one of claims 10 to 17, wherein: The control plane network element includes at least one of the following: Access and mobility management function AMF network element; Session management function SMF network element; Policy control function PCF network element.

19. A method for transmitting information, wherein: Executed by a proxy call session control function P-CSCF, the method comprises: A first message sent by a terminal through a control plane network element of a core network is received, wherein the first message is used to register the terminal with an Internet Protocol Multimedia Subsystem IMS.

20. The method according to claim 19, wherein: The method further comprises: Sending fourth information to the terminal through the control plane network element, wherein the fourth information is used to indicate an IMS registration result of the terminal.

21. The method according to claim 19 or 20, wherein: The control plane network element includes at least one of the following: Access and mobility management function AMF network element; Session management function SMF network element; Policy control function PCF network element.

22. A method for transmitting information, wherein: Executed by an information transmission system, the method includes: The terminal sends first information to a control plane network element of a core network, wherein the first information is used to register the terminal with an Internet Protocol Multimedia Subsystem IMS; The control plane network element sends the first information to a proxy call session control function P-CSCF.

23. A terminal, comprising: The sending module is configured to send first information to a proxy call session control function P-CSCF through a control plane network element of a core network, wherein the first information is used to register the terminal with an Internet Protocol Multimedia Subsystem IMS.

24. A control plane network element of a core network, comprising: A receiving module, configured to receive first information sent by a terminal, wherein the first information is used to register the terminal with an Internet Protocol Multimedia Subsystem IMS; The sending module is configured to send the first information to a proxy call session control function P-CSCF.

25. A proxy call session control function P-CSCF, comprising: The receiving module is configured to receive first information sent by a terminal through a control plane network element of a core network, wherein the first information is used to register the terminal with an Internet Protocol Multimedia Subsystem IMS.

26. An information transmission system, wherein: The information transmission system comprises: A terminal, configured to implement the information transmission method according to any one of claims 1 to 9; A control plane network element of a core network, configured to implement the information transmission method according to any one of claims 10 to 18; The proxy call session control function P-CSCF is configured to implement the information transmission method according to any one of claims 19 to 21.

27. A communication device, wherein: The communication device comprises: one or more processors; The processor is used to call instructions so that the communication device executes the information transmission method according to any one of claims 1 to 9, claims 10 to 18, and claims 19 to 21.

28. A storage medium, wherein: The storage medium stores instructions, and when the instructions are executed on the communication device, the communication device executes the information transmission method according to any one of claims 1 to 9, claims 10 to 18, and claims 19 to 21.

Images