Communication method of core network and mobile terminal, computer equipment and storage medium

Abstract

The invention provides a communication method of a core network and a mobile terminal, computer equipment and a storage medium, and belongs to the technical field of data communication. Comprising the following steps of: in a first registration scene, a first service scene, a first control plane service scene and a first de-registration scene which do not negotiate a security context between a mobile terminal and core network equipment; a first registration request message, a first service request message, a first control plane request message and a first de-registration request message sent by a mobile terminal to a core network device are kept unchanged, and after the mobile terminal and the core network device complete security context negotiation, the first service request message, the first control plane request message and the first de-registration request message are sent to the core network device. And deleting plaintext cells in the second registration request message, the second service request message, the second control plane request message and the second registration request message to complete signaling interaction between the mobile device and the core network device. According to the application, the effect of reducing the occupation of air interface resources by signaling interaction between the 5G core network and the mobile terminal so as to improve the utilization rate of the air interface resources can be achieved.

Description

Technical Field

[0001] The present application relates to the field of data communication technology, and in particular to a communication method between a core network and a mobile terminal, a computer device, and a storage medium. Background Art

[0002] With the continuous development of the information age, people's demand for the network is getting higher and higher. People need an efficient, fast and intelligent core network to support their daily work and life. The core network of the fifth generation mobile communication technology (5th Generation Mobile Networks, referred to as 5G) has become the core technology for the development of future networks due to its high speed, high flexibility and high security.

[0003] In the related technology, the 5G mobile terminal realizes the control of the terminal by the 5G core network through non-access stratum signaling (NAS signaling). The initial NAS signaling is the first NAS message for signaling interaction between the 5G mobile terminal and the 5G core network control plane. The initial NAS signaling includes: registration message, service request message and control plane service message, etc. The registration message, service request message and control plane service message may only carry plaintext cells, or may carry plaintext cells and non-plaintext cells at the same time.

[0004] However, when the signaling interaction between the 5G core network and the 5G mobile terminal is carried out based on relevant technologies, there is a problem of repeated carrying of plaintext cells contained in the initial NAS signaling. In the scenario where there are a large number of users in the existing network, the transmission of NAS signaling needs to be transmitted through air interface resources. Duplicate plaintext cells will occupy a large amount of air interface resources, thereby causing a waste of air interface resources. Summary of the invention

[0005] The purpose of this application is to provide a communication method, computer equipment and storage medium between a core network and a mobile terminal, which can reduce the occupation of air interface resources by signaling interaction between a 5G core network and a mobile terminal, so as to improve the utilization rate of air interface resources.

[0006] The embodiment of the present application is implemented as follows:

[0007] According to a first aspect of an embodiment of the present application, a communication method between a core network and a mobile terminal is provided, the method comprising:

[0008] In the first registration scenario, the mobile terminal sends a first registration request message to the core network device, where the first registration request message includes a plaintext cell and does not include a non-plaintext cell;

[0009] The mobile terminal negotiates security context with the core network device;

[0010] After the security context negotiation is completed, the mobile terminal sends a second registration request message to the core network device, where the second registration request message includes a non-plaintext cell but does not include a plaintext cell;

[0011] The core network device performs registration processing according to the first registration request message and the second registration request message.

[0012] As a possible implementation, the above method further includes:

[0013] In the second registration scenario, the mobile terminal sends a third registration request message and a NAS message container to the core network device, the third registration request message includes a plaintext cell and a registration request message identity, and does not include a non-plaintext cell, and the NAS message container is embedded with a non-plaintext cell;

[0014] The core network device performs registration processing according to the third registration request message and the NAS message container.

[0015] As a possible implementation, the above method further includes:

[0016] In the first service scenario, the mobile terminal sends a first service request message to the core network device, where the first service request message includes a plaintext cell and does not include a non-plaintext cell;

[0017] The mobile terminal negotiates security context with the core network device;

[0018] After the security context negotiation is completed, the mobile terminal sends a second service request message to the core network device, where the second service request message includes a non-plaintext cell but does not include a plaintext cell;

[0019] The core network device provides service to the mobile terminal according to the first service request message and the second service request message.

[0020] As a possible implementation, the above method further includes:

[0021] In the second service scenario, the mobile terminal sends a third service request message and a NAS message container to the core network device, the third service request message includes a plaintext cell and an identity authentication and security identifier, but does not include a non-plaintext cell, and the NAS message container has a non-plaintext cell embedded therein;

[0022] The core network device provides a service to the mobile terminal according to the third service request message and the NAS message container.

[0023] As a possible implementation, the above method further includes:

[0024] In the first control plane service scenario, the mobile terminal sends a first control plane request message to the core network device, where the first control plane request message includes a plaintext cell and does not include a non-plaintext cell;

[0025] The mobile terminal negotiates security context with the core network device;

[0026] After the security context negotiation is completed, the mobile terminal sends a second control plane request message to the core network device, where the second control plane request message includes a non-plaintext cell but does not include a plaintext cell;

[0027] The core network device provides target resources for the mobile terminal according to the first control plane request message and the second control plane request message.

[0028] As a possible implementation, the above method further includes:

[0029] In the second control plane service scenario, the mobile terminal sends a third control plane request message and a NAS message container to the core network device, the third control plane request message includes a plaintext cell and a control plane identity, but does not include a non-plaintext cell, and the NAS message container is embedded with a non-plaintext cell;

[0030] The core network device provides the target resource for the mobile terminal according to the third control plane request message and the NAS message container.

[0031] As a possible implementation, the above method further includes:

[0032] In the first deregistration scenario, the mobile terminal sends a first deregistration request message to the core network device, where the first deregistration request message includes a plaintext cell and does not include a non-plaintext cell;

[0033] The mobile terminal negotiates security context with the core network device;

[0034] After the security context negotiation is completed, the mobile terminal sends a second deregistration request message to the core network device, where the second deregistration request message includes a non-plaintext cell but does not include a plaintext cell;

[0035] The core network device disconnects from the mobile terminal according to the first deregistration request message and the second deregistration request message.

[0036] As a possible implementation, the above method further includes:

[0037] In the second deregistration scenario, the mobile terminal sends a third deregistration request message and a NAS message container to the core network device, the third deregistration request message includes a plaintext cell and a deregistration identity, but does not include a non-plaintext cell, and the NAS message container is nested with a non-plaintext cell;

[0038] The core network device disconnects from the mobile terminal according to the third deregistration request message and the NAS message container.

[0039] According to a second aspect of an embodiment of the present application, a computer device is provided, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, the communication method between the core network and the mobile terminal described in the first aspect is implemented.

[0040] According to a third aspect of an embodiment of the present application, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the communication method between the core network and the mobile terminal described in the first aspect above is implemented.

[0041] The beneficial effects of the embodiments of the present application include:

[0042] The embodiment of the present application provides a communication method between a core network and a mobile terminal. The registration request scenario between the mobile terminal and the core network device is determined by whether a security context data structure is established between the mobile terminal and the core network device. If the mobile terminal and the core network device have not established secure uplink and downlink messages before this registration request, the current registration scenario is the first registration scenario. In the first registration scenario, the mobile terminal first sends a first registration request message including only plaintext cells to the core network device, and after the first registration request message is sent, the mobile terminal negotiates the security context with the core network device. After the security context data structure is successfully established between the mobile terminal and the core network device, the mobile terminal sends a second registration request message including only non-plaintext cells and message types to the core network device. The core network device provides registration services for the mobile terminal based on the received first registration request message and the second registration request message. Among them, the first registration request message contains plaintext cells, and the second registration request message only includes non-plaintext cells, which can reduce the occupation of air interface resources by repeated plaintext cells in the second registration request message. In this way, the occupancy of air interface resources by signaling interaction between the 5G core network and mobile terminals can be reduced, thereby improving the utilization rate of air interface resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0043] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0044] Figure 1A flowchart of a first communication method between a core network and a mobile terminal provided in an embodiment of the present application;

[0045] Figure 2 A registration message sent by a mobile terminal to a core network in an existing first registration scenario;

[0046] Figure 3 The optimized first registration request message provided in the embodiment of the present application;

[0047] Figure 4 The optimized second registration request message provided in the embodiment of the present application;

[0048] Figure 5 A flowchart of a second communication method between a core network and a mobile terminal provided in an embodiment of the present application;

[0049] Figure 6 A registration message sent by the mobile terminal to the core network in the existing second registration scenario;

[0050] Figure 7 The optimized third registration request message and NAS message container provided in the embodiment of the present application;

[0051] Figure 8 Define a mapping diagram for existing registration request messages;

[0052] Fig. 9 A mapping relationship diagram is defined for the registration request message optimized in the embodiment of the present application;

[0053] Fig.10 A flowchart of a third communication method between a core network and a mobile terminal provided in an embodiment of the present application;

[0054] Fig.11 A flowchart of a fourth communication method between a core network and a mobile terminal provided in an embodiment of the present application;

[0055] Fig.12 A service request message sent by the mobile terminal to the core network in the existing second service scenario;

[0056] Fig.13 The optimized third service request message and NAS message container provided in the embodiment of the present application;

[0057] Fig.14 Define a mapping diagram for existing service request messages;

[0058] Fig.15 A mapping relationship diagram is defined for the service request message optimized in the embodiment of the present application;

[0059] Fig.16A flowchart of a fifth communication method between a core network and a mobile terminal provided in an embodiment of the present application;

[0060] Fig.17 A flowchart of a sixth communication method between a core network and a mobile terminal provided in an embodiment of the present application;

[0061] Fig.18 Define a mapping relationship diagram for existing control plane request messages;

[0062] Fig.19 A mapping relationship diagram for control plane request message definition optimized in the embodiment of the present application;

[0063] Fig. 20 A flowchart of a seventh communication method between a core network and a mobile terminal provided in an embodiment of the present application;

[0064] Fig.21 A flowchart of an eighth communication method between a core network and a mobile terminal provided in an embodiment of the present application;

[0065] Fig. 22 A service request message sent by a mobile terminal to a core network in an existing second deregistration scenario;

[0066] Fig.23 The optimized third deregistration request message and NAS message container provided in the embodiment of the present application;

[0067] Fig.24 Define a mapping diagram for the existing deregistration request message;

[0068] Fig.25 A mapping relationship diagram is defined for the deregistration request message optimized in the embodiment of the present application;

[0069] Fig.26 A schematic diagram of the structure of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0070] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. The components of the embodiments of the present application described and shown in the drawings here can be arranged and designed in various different configurations.

[0071] Therefore, the following detailed description of the embodiments of the present application provided in the accompanying drawings is not intended to limit the scope of the present application for which protection is sought, but merely represents selected embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.

[0072] At present, 5G mobile terminals use NAS signaling to achieve 5G core network control of terminals.

[0073] Among them, the initial NAS signaling is the first NAS message for signaling interaction between the 5G mobile terminal and the 5G core network control plane. The initial NAS signaling includes: registration message, service request message, and control plane service message, etc. The registration message, service request message, and control plane service message may carry only plaintext cells, or may carry plaintext cells and non-plaintext cells at the same time. However, this solution has the problem of repeated plaintext cells in the initial NAS signaling. The transmission of NAS signaling requires the occupation of air interface resources to achieve implementation, which causes the repeated plaintext cells in the NAS signaling to occupy and waste air interface resources.

[0074] To this end, an embodiment of the present application provides a communication method between a core network and a mobile terminal, wherein, in a first registration scenario, a first service scenario, a first control plane service scenario, and a first deregistration scenario in which a security context is not negotiated between the mobile terminal and the core network device, the first registration request message, the first service request message, the first control plane request message, and the first deregistration request message sent by the mobile terminal to the core network device are kept unchanged, and after the mobile terminal and the core network device complete the security context negotiation, the second registration request message, the second service request message, the second control plane request message, and the second deregistration request message are deleted in the plaintext information element to complete the signaling interaction between the mobile device and the core network device in this scenario; in a second registration scenario, a second service scenario, a second control plane service scenario, and a second deregistration scenario in which a security context has been established between the mobile terminal and the core network device, the registration message identity, the identity authentication and security identity, the control plane identity, the deregistration identity, and the plaintext information element in the NAS message container are deleted to complete the signaling interaction between the mobile device and the core network device in this scenario. In this way, the occupancy of air interface resources by signaling interaction between the 5G core network and mobile terminals can be reduced, thereby improving the utilization rate of air interface resources.

[0075] The communication method between the core network and the mobile terminal provided in the embodiment of the present application is explained in detail below with reference to the accompanying drawings.

[0076] Figure 1This is a flow chart of a communication method between a core network and a mobile terminal provided in this application. This method can be applied to 5G mobile terminals or core network devices. Figure 1 , the embodiment of the present application provides a communication method between a core network and a mobile terminal, including:

[0077] S101. In a first registration scenario, a mobile terminal sends a first registration request message to a core network device, where the first registration request message includes plaintext cells but does not include non-plaintext cells.

[0078] Optionally, the first registration scenario is used to indicate a registration scenario in which no security context is established between the mobile terminal and the core network device. The mobile terminal may be a mobile phone, a portable computer, or other device UE that can establish a communication connection with the core network device. The core network device refers to an electronic device used to provide a core network. The core network device is mainly used to provide a 5G core network for a communication system constructed by the mobile terminal and the core network device. In the 5G network, when the N1 interface between the UE and the access and mobility management function transmits NAS signaling, the NAS signaling may contain both plaintext cells and encrypted cells.

[0079] Optionally, the first registration request message refers to the initial registration request message sent by the mobile terminal to the core network device, the plaintext cell refers to the unencrypted information element in the NAS signaling, and the plaintext cell refers to the necessary information element transmitted before the mobile terminal and the core network device establish a security context. Among them, in the 5G network, the initial NAS message is the first initial NAS message sent after the UE accesses the network. At this time, no security context is established between the mobile terminal UE and the core network device, and security protection cannot be provided for the information. In this case, the mobile terminal UE will send a limited set of plaintext cells IE to the core network device. These IEs only contain information elements necessary to establish security when no security context is established between the mobile terminal and the core network device, such as user identifiers (such as SUCI or GUTI), UE security capabilities, S-TMSI, etc.

[0080] In addition, in the 5G network, the transmission of the initial NAS message needs to clearly distinguish between plaintext cells and encrypted cells. The transmission of plaintext cells can ensure that the necessary authentication and security parameters can be correctly transmitted before the mobile terminal and the core network device establish a security context. Once the security context is established between the mobile terminal and the core network device, all NAS signaling between the mobile terminal and the core network device will be encrypted and integrity protected to ensure the security and reliability of the communication between the mobile terminal and the core network device. Among them, the encrypted cell refers to the information element that has been encrypted. The encrypted cell refers to the sensitive information element transmitted between the mobile terminal and the core network device after the security context is established between the mobile terminal and the core network device to ensure the confidentiality and integrity of the information transmission.

[0081] Optionally, a non-plaintext cell refers to a data unit that is not directly transmitted in plaintext during the communication process, and a non-plaintext cell refers to a data unit that has been processed by encryption or other security measures, which can ensure the confidentiality and security of the data.

[0082] Optionally, in the first registration scenario, the first registration request information sent by the mobile terminal to the core network device only includes plain text registration information, and does not include non-plain text registration information.

[0083] S102: The mobile terminal performs security context negotiation with the core network device.

[0084] Optionally, a security context negotiation is performed between the mobile terminal and the core network device to complete the establishment of a security context between the mobile terminal and the core network device. Among them, security context negotiation refers to the process in which the mobile terminal and the core network device update and confirm the security context with the system through feature negotiation during a communication session. Security context negotiation involves information such as subject identification, keys, passwords, and algorithms to ensure the security of communications between the mobile terminal and the core network device and the confidentiality of data. It is worth noting that the method for the mobile terminal to negotiate a security context with the core network device can be any one of a variety of methods such as key exchange, identity authentication, and security context update, and this application does not make specific limitations on this.

[0085] S103. After the security context negotiation is completed, the mobile terminal sends a second registration request message to the core network device, where the second registration request message includes non-plaintext cells but does not include plaintext cells.

[0086] Optionally, after a security context is established between the mobile terminal and the core network device, the mobile terminal sends a second registration request message to the core network device, and the second registration request message contains only non-plaintext information elements. The first registration request message and the second registration request message are both used to request registration from the core network device, but the first registration request message is used to inform the core network device that this is a message requesting registration, but does not contain registration content, and the second registration request message is used to inform the specific registration content, such as registration identity and other information.

[0087] In an optional embodiment, see Figure 2When an existing mobile terminal sends a registration request to a core network device, if the mobile terminal and the core network device have not established a security context before, the mobile terminal first sends a first registration request message to the core network. The first registration request message only contains plain text information elements, which are mainly used to inform the core network device that the message is mainly used to request registration. After sending the first registration request message, the mobile terminal negotiates the security context with the core network device, and after successfully establishing the security context information, the mobile terminal sends a second registration request message to the core network device. The second registration request message not only contains the plain text information elements in the first registration request message, but also introduces non-plain text information elements. Among them, see Figure 3 , the first registration request message only contains plain text information, the plain text information element includes the content of the dotted box plus the content of the solid box, the dotted box content refers to the message header information of the registration request message, and the solid box content indicates the plain text information element in the registration request message. The first registration request message of this application is consistent with the first registration request message in the prior art, that is, this application does not optimize the first registration request message. In addition, see Figure 4 In the prior art, the second registration request message includes not only plaintext cells repeated with the plaintext cells in the first registration request message, but also non-plaintext cells. In order to reduce the occupation of air interface resources by the repeated plaintext cells in the second registration request message, the present application deletes the plaintext cells in the second registration request message in the prior art to obtain the second registration request message of the present application. The second registration request message of the present application only includes the non-plaintext cells and the message type, that is, Figure 4 The dotted box content and the implementation box content in the second registration request message of the prior art are deleted to improve the utilization rate of air interface resources.

[0088] It is worth noting that air interface resources refer to the spectrum resources required for data transmission between mobile terminals and core network base stations. Spectrum resources include: time domain resources, frequency domain resources and air domain resources. Among them, time domain resources include cyclic prefix CP, symbols, time slots, subframes and radio frames, etc., frequency domain resources include subcarrier spacing SCS, resource blocks RB, resource block groups RBG, bandwidth parts BWP, etc., and air domain resources involve codewords, layers, antenna ports, etc. The allocation and management of air interface resources play an important role in the efficient operation of the 5G core network.

[0089] S104. The core network device performs registration processing according to the first registration request message and the second registration request message.

[0090] Optionally, both the first registration request message and the second registration request message are encoded by the terminal device and sent to the core network device via the base station. The mobile terminal uses different technical means to optimize the second registration request message according to whether a security context data structure is established with the core network device in advance, so that the plaintext elements in the first registration request message and the second registration request message are not sent repeatedly.

[0091] It is worth noting that before the mobile terminal sends the registration request information to the core network device, the message elements of the second registration request message are processed in advance according to whether a security context data structure is established between the mobile terminal and the core network device, so that the plaintext cells of the second registration request message and the first registration request message in the encoded NAS signaling are not sent repeatedly, thereby reducing the occupation and waste of air interface resources by the plaintext cells in the NAS signaling.

[0092] Optionally, after receiving the first registration request message and the second registration request message sent by the mobile terminal, the core network device provides corresponding registration services for the mobile terminal, so that the mobile terminal obtains the authority to access the core network provided by the core network device.

[0093] In an embodiment of the present application, the registration request scenario between the mobile terminal and the core network device is determined by whether a security context data structure is established between the mobile terminal and the core network device. If the mobile terminal and the core network device do not establish a secure uplink and downlink message before this registration request, the current registration scenario is the first registration scenario. In the first registration scenario, the mobile terminal first sends a first registration request message including only plaintext cells to the core network device, and after the first registration request message is sent, the mobile terminal negotiates the security context with the core network device. After the security context data structure is successfully established between the mobile terminal and the core network device, the mobile terminal sends a second registration request message including only non-plaintext cells and message types to the core network device. The core network device provides registration services for the mobile terminal based on the received first registration request message and the second registration request message. Among them, the first registration request message contains plaintext cells, and the second registration request message only includes non-plaintext cells, which can reduce the occupation of air interface resources by repeated plaintext cells in the second registration request message. In this way, the occupation of air interface resources by signaling interaction between the 5G core network and the mobile terminal can be reduced to improve the utilization of air interface resources.

[0094] In an optional embodiment, see Figure 5 , the above method further comprises:

[0095] S501. In the second registration scenario, the mobile terminal sends a third registration request message and a NAS message container to the core network device. The third registration request message includes a plaintext cell and a registration request message identity identifier, but does not include a non-plaintext cell. The NAS message container contains nested non-plaintext cells.

[0096] Optionally, the second registration scenario refers to a registration scenario in which a security context data structure has been established between the mobile terminal and the core network device, and the third registration request message refers to a registration request message sent by the mobile terminal to the core network device when a security context data structure already exists between the mobile terminal and the core network device. The third registration request message is embedded with a NAS message container, the NAS message container only includes non-plaintext cells, and plaintext cells and a registration request message identity are stored outside the NAS message container. The registration request message identity is used to indicate the type of the third registration request message, and is used to inform the core network device that the message is a registration request message.

[0097] It is worth noting that the registration request message identity identifier can be identified as the ID of the third registration request message, which is mainly used to inform the core network device what the message is used for. This application does not make specific restrictions on this.

[0098] S502: The core network device performs registration processing according to the third registration request message and the NAS message container.

[0099] Optionally, the core network device provides a registration service for the mobile terminal according to the plaintext information element and the registration request message identity in the third registration request message sent by the mobile terminal and the non-plaintext information element in the NAS message container.

[0100] In an optional embodiment, see Figure 6 In the scenario where a security context data structure already exists between the mobile terminal and the core network device, the registration request message sent by the mobile terminal to the core network device is a nested structure. Figure 7 The nested structure of the registration request message sent by the mobile terminal to the core network device contains two repeated plaintext cells, and the plaintext cells in the nested structure are repeated twice. The present application deletes the message header in the dotted box and the plaintext cells in the implementation box in the NAS message container so that the plaintext cells appear only once in the nested structure, and only non-plaintext cells are stored in the NAS message container, thereby reducing the occupation of air interface resources by repeated plaintext cells in the nested structure of the prior art.

[0101] In an optional embodiment, see Figure 8 , the registration message definition table provided by the prior art contains multiple plain text cell definitions; however, see Fig. 9 The registration message definition table provided in the embodiment of the present application includes fewer plaintext cell definitions than the plaintext cell definitions in the prior art, thereby reducing the number of repeated occurrences of plaintext cells during NAS signaling editing.

[0102] In an optional implementation manner, the plain text part of the registration request message sent by the mobile terminal to the core network device is defined as follows:

[0103] When the initial NAS message is a REGISTRATION REQUEST message, the cleartext IEs are:

[0104] Extended protocol discriminator;

[0105] Security header type;

[0106] Spare half octet;

[0107] Registration request message identity;

[0108] 5GS registration type;

[0109] ngKSI;

[0110] 5GS mobile identity;

[0111] UE security capability;

[0112] Additional GUTI;

[0113] UE status;

[0114] EPS NAS message container;

[0115] NID; and

[0116] UE determined PLMN with disaster condition.

[0117] In an embodiment of the present application, if the mobile terminal and the core network device have established secure uplink and downlink messages before this registration request, the current registration scenario is the second registration scenario. In the second registration scenario, the mobile terminal directly sends a third registration request message including plaintext cells and non-plaintext cells to the core network device. The NAS message container nested in the third registration request message only stores non-plaintext cells. The plaintext cells and the registration request message identity are stored in the third registration request message. The core network device directly provides registration services to the mobile terminal based on the plaintext cells in the third registration request message, the registration request message identity, and the non-plaintext cells in the NAS message container. This can reduce the duplication of plaintext cells in the nested structure in the prior art and the excessive waste of air interface resources.

[0118] In an optional embodiment, see Fig.10 , the above method further comprises:

[0119] S1001. In a first service scenario, a mobile terminal sends a first service request message to a core network device. The first service request message includes plaintext cells but does not include non-plaintext cells.

[0120] Optionally, the first service scenario is used to indicate a service scenario in which a security context is not established between the mobile terminal and the core network device, and the first service request message refers to an initial service request message sent by the mobile terminal to the core network device, and the first service request message includes plaintext cells required for the mobile terminal to request a service from the core network device. In the first service scenario, the first service request information sent by the mobile terminal to the core network device includes only plaintext cells and does not include non-plaintext cells.

[0121] S1002. The mobile terminal performs security context negotiation with the core network device.

[0122] S1003. After the security context negotiation is completed, the mobile terminal sends a second service request message to the core network device, where the second service request message includes non-plaintext cells but does not include plaintext cells.

[0123] Optionally, after a security context is established between the mobile terminal and the core network device, the mobile terminal sends a second service request message to the core network device, and the second service request message contains only non-plaintext information elements. The first service request message and the second service request message are both used to request services from the core network device, but the first service request message is used to inform the core network device that this is a service request message but does not contain service content, while the second service request message is used to inform the specific service content.

[0124] S1004. The core network device provides service to the mobile terminal according to the first service request message and the second service request message.

[0125] Optionally, both the first service request message and the second service request message are encoded by the terminal device and sent to the core network device via the base station. The mobile terminal uses different technical means to optimize the second service request message according to whether a security context data structure is established with the core network device in advance, so that the plaintext elements in the first service request message and the second service request message are not sent repeatedly.

[0126] Optionally, after receiving the first service request message and the second service request message sent by the mobile terminal, the core network device provides corresponding services for the mobile terminal.

[0127] In an optional embodiment, see Fig.11 , the above method further comprises:

[0128] S1101. In the second service scenario, the mobile terminal sends a third service request message and a NAS message container to the core network device. The third service request message includes plaintext cells and identity authentication and security identifiers, but does not include non-plaintext cells. The NAS message container contains nested non-plaintext cells.

[0129] Optionally, the second service scenario refers to a service scenario in which a security context data structure has been established between the mobile terminal and the core network device, and the third service request message refers to a service request message sent by the mobile terminal to the core network device when a security context data structure already exists between the mobile terminal and the core network device. The third service request message is embedded with a NAS message container, which only includes non-plaintext cells, and plaintext cells and identity authentication and security identifiers are stored outside the NAS message container. The identity authentication and security identifier are used to indicate the type of the third service request message, and are used to inform the core network device that the message is a service request message and provide service request object identity authentication.

[0130] S1102. The core network device provides a service to the mobile terminal according to the third service request message and the NAS message container.

[0131] Optionally, the core network device provides a specific service for the mobile terminal according to the plaintext information element and the identity authentication and security identifier in the third service request message sent by the mobile terminal and the non-plaintext information element in the NAS message container.

[0132] In an optional embodiment, see Fig.12 In the scenario where a security context data structure already exists between the mobile terminal and the core network device, the service request message sent by the mobile terminal to the core network device is a nested structure. Fig.13 The nested structure of the service request message sent by the mobile terminal to the core network device contains two repeated plaintext cells, and the plaintext cells in the nested structure are repeated twice. The present application deletes the message header in the dotted box and the plaintext cells in the implementation box in the NAS message container so that the plaintext cells appear only once in the nested structure, and only non-plaintext cells are stored in the NAS message container, thereby reducing the occupation of air interface resources by repeated plaintext cells in the nested structure of the prior art.

[0133] In an optional embodiment, see Fig.14 , the service message definition table provided by the prior art contains multiple plain text cell definitions; however, see Fig.15 The service message definition table provided in the embodiment of the present application includes fewer plaintext cell definitions than the plaintext cell definitions in the prior art, thereby reducing the number of repeated occurrences of plaintext cells during NAS signaling editing.

[0134] In an optional implementation manner, the plain text part of the service request message sent by the mobile terminal to the core network device is defined as follows:

[0135] When the initial NAS message is a SERVICE REQUEST message, the cleartext IEs are:

[0136] Extended protocol discriminator;

[0137] Security header type;

[0138] Spare half octet;

[0139] ngKSI;

[0140] Service request message identity;

[0141] Service type; and

[0142] 5G-S-TMSI.

[0143] In an optional embodiment, see Fig.16 , the above method further comprises:

[0144] S1601. In a first control plane service scenario, a mobile terminal sends a first control plane request message to a core network device, where the first control plane request message includes a plaintext cell but does not include a plaintext cell.

[0145] Optionally, the first control plane scenario is used to indicate a control plane service scenario in which no security context is established between the mobile terminal and the core network device, and the first control plane request message refers to an initial control plane request message sent by the mobile terminal to the core network device, and the first control plane request message includes the plaintext cells required for the mobile terminal to request the control plane service from the core network device. In the first control plane scenario, the first control plane request information sent by the mobile terminal to the core network device only includes plaintext cells and does not include non-plaintext cells.

[0146] S1602: The mobile terminal performs security context negotiation with the core network device.

[0147] S1603. After the security context negotiation is completed, the mobile terminal sends a second control plane request message to the core network device, where the second control plane request message includes non-plaintext cells but does not include plaintext cells.

[0148] Optionally, after a security context is established between the mobile terminal and the core network device, the mobile terminal sends a second control plane request message to the core network device, and the second control plane request message contains only non-plaintext information elements. The first control plane request message and the second control plane request message are both used to request control plane services from the core network device, but the first control plane request message is used to inform the core network device that this is a control plane service request message, but does not contain control plane service content, and the second control plane request message is used to inform the specific control plane service content.

[0149] S1604. The core network device provides target resources for the mobile terminal according to the first control plane request message and the second control plane request message.

[0150] Optionally, both the first control plane request message and the second control plane request message are encoded by the terminal device and sent to the core network device via the base station. The mobile terminal uses different technical means to optimize the second control plane request message according to whether a security context data structure is established with the core network device in advance, so that the plaintext elements in the first control plane request message and the second control plane request message are not sent repeatedly.

[0151] Optionally, after receiving the first control plane request message and the second control plane request message sent by the mobile terminal, the core network device provides corresponding target resources for the mobile terminal, where the target resources are used to indicate the control plane service resources requested by the control plane request messages.

[0152] In an optional embodiment, see Fig.17 , the above method further comprises:

[0153] S1701. In the second control plane service scenario, the mobile terminal sends a third control plane request message and a NAS message container to the core network device. The third control plane request message includes a plaintext cell and a control plane identity, but does not include a non-plaintext cell. The NAS message container contains nested non-plaintext cells.

[0154] Optionally, the second control plane scenario refers to a control plane service scenario in which a security context data structure has been constructed between the mobile terminal and the core network device, and the third control plane request message refers to a control plane service request message sent by the mobile terminal to the core network device when a security context data structure already exists between the mobile terminal and the core network device. Among them, a NAS message container is embedded in the third control plane request message, and the NAS message container only includes non-plaintext cells. Plaintext cells and a control plane identity are stored outside the NAS message container. The control plane identity is used to indicate the type of the third control plane request message, and is used to inform the core network device that the message is a control plane service request message.

[0155] S1702. The core network device provides target resources for the mobile terminal according to the third control plane request message and the NAS message container.

[0156] Optionally, the core network device provides the target resource for the mobile terminal according to the plaintext information element and the control plane identity in the third control plane request message sent by the mobile terminal and the non-plaintext information element in the NAS message container.

[0157] In an optional embodiment, see Fig.18 , the control plane service message definition table provided by the prior art contains multiple plain text cell definitions; however, see Fig.19 The control plane service message definition table provided in the embodiment of the present application includes fewer plaintext cell definitions than the plaintext cell definitions in the prior art, thereby reducing the number of repeated occurrences of plaintext cells during NAS signaling editing.

[0158] In an optional implementation manner, the plain text part of the control plane service request message sent by the mobile terminal to the core network device is defined as follows:

[0159] When the initial NAS message is a CONTROL PLANE SERVICE REQUEST message, the cleartext IEs are:

[0160] Extended protocol discriminator;

[0161] Security header type;

[0162] Spare half octet;

[0163] ngKSI;

[0164] Control plane service request message identity; and

[0165] Control plane service type.

[0166] In an optional embodiment, see Fig. 20 , the above method further comprises:

[0167] S2001. In a first deregistration scenario, a mobile terminal sends a first deregistration request message to a core network device, where the first deregistration request message includes plaintext cells but does not include non-plaintext cells.

[0168] Optionally, the first deregistration scenario is used to indicate a deregistration scenario in which no security context is established between the mobile terminal and the core network device, and the first deregistration request message refers to an initial deregistration request message sent by the mobile terminal to the core network device, and the first deregistration request message includes a plaintext cell required for the mobile terminal to request the core network device to deregister or disconnect the network connection service. In the first deregistration scenario, the first deregistration request message sent by the mobile terminal to the core network device only includes plaintext cells and does not include non-plaintext cells.

[0169] S2002. The mobile terminal performs security context negotiation with the core network device.

[0170] S2003. After the security context negotiation is completed, the mobile terminal sends a second deregistration request message to the core network device, where the second deregistration request message includes non-plaintext cells but does not include plaintext cells.

[0171] Optionally, after a security context is established between the mobile terminal and the core network device, the mobile terminal sends a second deregistration request message to the core network device, and the second deregistration request message contains only non-plaintext information elements. The first deregistration request message and the second deregistration request message are both used to request the core network device to disconnect the service or deregister the service, but the first deregistration request message is used to inform the core network device that this is a deregistration request message, but does not contain deregistration service content, and the second deregistration request message is used to inform the specific deregistration service content.

[0172] S2004. The core network device disconnects from the mobile terminal according to the first deregistration request message and the second deregistration request message.

[0173] Optionally, both the first deregistration request message and the second deregistration request message are encoded by the terminal device and sent to the core network device via the base station. The mobile terminal uses different technical means to optimize the second deregistration request message according to whether a security context data structure is established with the core network device in advance, so that the plaintext elements in the first deregistration request message and the second deregistration request message are not sent repeatedly.

[0174] Optionally, after the core network device receives the first deregistration request message and the second deregistration request message sent by the mobile terminal, the core network device disconnects from the mobile terminal.

[0175] In an optional embodiment, see Fig.21 , the above method further comprises:

[0176] S2101. In the second deregistration scenario, the mobile terminal sends a third deregistration request message and a NAS message container to the core network device. The third deregistration request message includes a plaintext cell and a deregistration identity, but does not include a non-plaintext cell. The NAS message container has non-plaintext cells nested in it.

[0177] Optionally, the second deregistration scenario refers to a deregistration service scenario in which a security context data structure has been constructed between the mobile terminal and the core network device, and the third deregistration request message refers to a deregistration service request message sent by the mobile terminal to the core network device when a security context data structure already exists between the mobile terminal and the core network device. Among them, a NAS message container is embedded in the third deregistration request message, and the NAS message container only includes non-plaintext cells. Plaintext cells and a deregistration identity are stored outside the NAS message container. The deregistration identity is used to indicate the type of the third service request message, to inform the core network device that the message is a deregistration service request message, and to provide identity authentication for the deregistration service request object.

[0178] S2102. The core network device disconnects from the mobile terminal according to the third deregistration request message and the NAS message container.

[0179] Optionally, the core network device disconnects from the mobile terminal according to the plaintext information element and the deregistration identity in the third deregistration request message sent by the mobile terminal and the non-plaintext information element in the NAS message container.

[0180] In an optional embodiment, see Fig. 22 In the scenario where a security context data structure already exists between the mobile terminal and the core network device, the deregistration service message sent by the mobile terminal to the core network device contains a NAS message container. Fig.23 The deregistration service request message sent by the mobile terminal to the core network device contains two plaintext cells, and the plaintext cells in the NAS message container in the deregistration service request message are repeated. The present application deletes the message header in the dotted box and the plaintext cells in the implementation box in the NAS message container so that the plaintext cells appear only once in the nested structure, and only non-plaintext cells are stored in the NAS message container, thereby reducing the occupation of air interface resources by repeated plaintext cells in the nested structure of the prior art.

[0181] In an optional embodiment, see Fig.24 , the deregistration service message definition table provided by the prior art contains multiple plain text cell definitions; however, see Fig.25 The deregistration service message definition table provided in the embodiment of the present application contains fewer plaintext cell definitions than the plaintext cell definitions in the prior art, thereby reducing the number of repeated occurrences of plaintext cells during NAS signaling editing.

[0182] In an optional implementation manner, the plain text part of the deregistration service request message sent by the mobile terminal to the core network device is defined as follows:

[0183] When the initial NAS message is a DEREGISTRATION REQUEST message, the cleartext IEs are:

[0184] Extended protocol discriminator;

[0185] Security header type;

[0186] Spare half octet;

[0187] De-registration request message identity;

[0188] De-registration type;

[0189] ngKSI; and

[0190] 5GS mobile identity.

[0191] The following describes the computer equipment and computer-readable storage medium used to execute the communication method between the core network and the mobile terminal provided in this application. The specific implementation process and technical effects are described above and will not be repeated below.

[0192] Fig.26 is a schematic diagram of the structure of a computer device provided in an embodiment of the present application. Fig.26 The computer device includes: a memory 2601 and a processor 2602. The memory 2601 stores a computer program that can be run on the processor 2602. When the processor 2602 executes the computer program, the steps in any of the above method embodiments are implemented.

[0193] An embodiment of the present application further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments can be implemented.

[0194] Optionally, the present application also provides a program product, such as a computer-readable storage medium, comprising a program, which, when executed by a processor, is used to execute any of the above-mentioned embodiments of the communication method between the core network and the mobile terminal.

[0195] The above-mentioned integrated unit implemented in the form of a software functional unit can be stored in a computer-readable storage medium. The above-mentioned software functional unit is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor (English: processor) to perform some steps of the methods of various embodiments of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (English: Read-Only Memory, abbreviated: ROM), random access memory (English: Random Access Memory, abbreviated: RAM), disk or optical disk and other media that can store program codes.

[0196] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

[0197] The above description is only the preferred embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A communication method between a core network and a mobile terminal, characterized in that: The method comprises: In the first registration scenario, the mobile terminal sends a first registration request message to the core network device, where the first registration request message includes a plaintext cell and does not include a non-plaintext cell; The mobile terminal performs security context negotiation with the core network device; After the security context negotiation is completed, the mobile terminal sends a second registration request message to the core network device, where the second registration request message includes a non-plaintext cell but does not include a plaintext cell; The core network device performs registration processing according to the first registration request message and the second registration request message.

2. The communication method between the core network and the mobile terminal according to claim 1, characterized in that: The method further comprises: In the second registration scenario, the mobile terminal sends a third registration request message and a NAS message container to the core network device, the third registration request message includes a plaintext cell and a registration request message identity, but does not include a non-plaintext cell, and the NAS message container is nested with a non-plaintext cell; The core network device performs registration processing according to the third registration request message and the NAS message container.

3. The communication method between the core network and the mobile terminal according to claim 1, characterized in that: The method further comprises: In a first service scenario, the mobile terminal sends a first service request message to the core network device, where the first service request message includes a plaintext cell and does not include a non-plaintext cell; The mobile terminal performs security context negotiation with the core network device; After the security context negotiation is completed, the mobile terminal sends a second service request message to the core network device, where the second service request message includes a non-plaintext cell but does not include a plaintext cell; The core network device provides service to the mobile terminal according to the first service request message and the second service request message.

4. The communication method between the core network and the mobile terminal according to claim 1, characterized in that: The method further comprises: In the second service scenario, the mobile terminal sends a third service request message and a NAS message container to the core network device, wherein the third service request message includes a plaintext cell and an identity authentication and security identifier, but does not include a non-plaintext cell, and the NAS message container is embedded with a non-plaintext cell; The core network device provides a service for the mobile terminal according to the third service request message and the NAS message container.

5. The communication method between the core network and the mobile terminal according to claim 1, characterized in that: The method further comprises: In a first control plane service scenario, the mobile terminal sends a first control plane request message to the core network device, where the first control plane request message includes a plaintext cell and does not include a non-plaintext cell; The mobile terminal performs security context negotiation with the core network device; After the security context negotiation is completed, the mobile terminal sends a second control plane request message to the core network device, where the second control plane request message includes a non-plaintext cell but does not include a plaintext cell; The core network device provides target resources for the mobile terminal according to the first control plane request message and the second control plane request message.

6. The communication method between the core network and the mobile terminal according to claim 1, characterized in that: The method further comprises: In the second control plane service scenario, the mobile terminal sends a third control plane request message and a NAS message container to the core network device, wherein the third control plane request message includes a plaintext cell and a control plane identity, but does not include a non-plaintext cell, and the NAS message container is embedded with a non-plaintext cell; The core network device provides target resources for the mobile terminal according to the third control plane request message and the NAS message container.

7. The communication method between the core network and the mobile terminal according to claim 1, characterized in that: The method further comprises: In a first deregistration scenario, the mobile terminal sends a first deregistration request message to the core network device, wherein the first deregistration request message includes a plaintext cell and does not include a non-plaintext cell; The mobile terminal performs security context negotiation with the core network device; After the security context negotiation is completed, the mobile terminal sends a second deregistration request message to the core network device, where the second deregistration request message includes a non-plaintext cell but does not include a plaintext cell; The core network device disconnects from the mobile terminal according to the first deregistration request message and the second deregistration request message.

8. The communication method between the core network and the mobile terminal according to claim 1, characterized in that: The method further comprises: In the second deregistration scenario, the mobile terminal sends a third deregistration request message and a NAS message container to the core network device, wherein the third deregistration request message includes a plaintext cell and a deregistration identity, but does not include a non-plaintext cell, and the NAS message container has a non-plaintext cell embedded therein; The core network device disconnects from the mobile terminal according to the third deregistration request message and the NAS message container.

9. A computer device, characterized in that: include: A memory and a processor, wherein the memory stores a computer program that can be run on the processor, and when the processor executes the computer program, the steps of the method described in any one of claims 1 to 8 are implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the method according to any one of claims 1 to 8.

Images