User terminal registration method, apparatus and communication system

Abstract

The application discloses a user terminal registration method, device and communication system. The method comprises the following steps: obtaining broadcast information and user terminal configuration information; determining the type of the user terminal according to the broadcast information and the configuration information; in the case that the type of the user terminal is a satellite access Internet of Things terminal, sending an attachment request to a core network element to complete the registration of the user terminal, wherein the bearer establishment request information in the attachment request is empty or the attachment request does not carry the bearer establishment request information. The application solves the technical problem of low interaction efficiency in the user terminal registration process in the related art.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, in particular to a user terminal registration method and device and a communication system. BACKGROUND

[0002] The Internet of Things is a technology that connects various physical devices, virtual devices, services and information through a network, which can realize intelligent interaction and cooperation between things, people and people. In order to realize the interconnection between Internet of Things devices, Internet of Things network technology needs to be used, and in the case that the user terminal in the Internet of Things needs to be connected to the network, in the related art, in the Internet of Things data transmission scenario in the satellite IoTNTN (Internet of Things Non-Terrestrial Network), the default bearer establishment request information (ESM message container) for the NAS transmission used by the Internet of Things data transmission only plays the role of allocating IP, and there is no user plane data transmission on the bearer, which causes waste of satellite air interface resources, increases the signaling interaction parameters between the core network and the base station, and reduces the interaction efficiency.

[0003] In view of the above problems, no effective solution has been proposed so far. SUMMARY

[0004] The embodiments of the present application provide a user terminal registration method, device and communication system, to at least solve the technical problem of low interaction efficiency in the user terminal registration process in the related art.

[0005] According to an aspect of an embodiment of the present application, a user terminal registration method is provided, comprising: obtaining broadcast information and user terminal configuration information; determining the type of the user terminal according to the broadcast information and the configuration information; in the case that the type is a satellite access Internet of Things terminal, sending an attachment request to a core network element to complete the registration of the user terminal, wherein the bearer establishment request information in the attachment request is empty or the attachment request does not carry the bearer establishment request information.

[0006] Optionally, sending an attachment request to a core network element comprises: sending the attachment request to the core network element through a base station, and the attachment request is used at least to instruct the core network element to establish only a user plane bearer between the core network element and a service gateway.

[0007] Optionally, the sending the attach request to the core network element via the base station comprises: sending a target signaling containing the attach request to the base station via an access layer, the target signaling being used to trigger the base station to send an initial message containing the attach request to the core network element, wherein the attach request is sent by a mobility management function entity in the user terminal to the access layer, and the access layer sends the target signaling to the base station in response to receiving the attach request.

[0008] Optionally, the completing the registration of the user terminal comprises: receiving an attach accept message sent by the core network element, the attach accept message being used to represent that a user plane bearer between the core network element and the serving gateway has been established, the user plane bearer between the core network element and the serving gateway being determined by the core network element based on the type of the user terminal; and completing the registration of the user terminal by the mobility management function entity in response to the attach accept message, wherein the attach accept message does not contain an activate default bearer request.

[0009] Optionally, the method further comprises: in the case that the user terminal requires a bearer, sending a bearer establishment request to the core network element, wherein in the case that the bearer establishment request is for establishing a default bearer, the bearer establishment request is used to request the core network element to establish a default bearer, and in the case that the bearer establishment request is for establishing a dedicated bearer, the bearer establishment request is used to request the core network element to first establish a default bearer and then establish the dedicated bearer.

[0010] Optionally, the method further comprises: sending the attach request to the core network element, wherein the attach request is used to indicate that the type of the user terminal is a satellite access Internet of Things terminal, and in the case that the type of the user terminal is a satellite access Internet of Things terminal, the core network element determines to only establish a user plane bearer between the core network element and a serving gateway.

[0011] Optionally, the method further comprises: sending the attach request to the core network element, wherein in the case that bearer establishment request information in the attach request is not empty, the core network element determines whether the user terminal is a satellite access Internet of Things terminal according to the attach request, and in the case that the type of the user terminal is a satellite access Internet of Things terminal, the core network element determines that the bearer establishment request is a suspend processing request.

[0012] According to another aspect of the embodiments of the present application, another user terminal registration method is provided, comprising: receiving an attachment request sent by the user terminal; determining the type of the user terminal according to the attachment request, and establishing a user plane bearer between the core network element and a serving gateway only in the case that the user terminal is a satellite accessed Internet of Things terminal; and sending an attachment accept message to the user terminal to complete the registration of the user terminal, wherein the attachment accept message does not contain an activation default bearer request.

[0013] According to still another aspect of the embodiments of the present application, a user terminal registration apparatus is provided, comprising: an obtaining module, configured to obtain broadcast information and user terminal configuration information; a determining module, configured to determine the type of the user terminal according to the broadcast information and the configuration information; and a registration module, configured to send an attachment request to a core network element to complete the registration of the user terminal in the case that the type is a satellite accessed Internet of Things terminal, wherein the bearer establishment request information in the attachment request is empty or the attachment request does not carry the bearer establishment request information.

[0014] According to still another aspect of the embodiments of the present application, a communication system is provided, comprising: a user terminal and a core network element; the user terminal is configured to send an attachment request to the core network element in the case that the type of the user terminal is a satellite accessed Internet of Things terminal; and the core network element is configured to complete the registration of the user terminal in response to the attachment request, wherein the bearer establishment request information in the attachment request is empty or the attachment request does not carry the bearer establishment request information.

[0015] According to still another aspect of the embodiments of the present application, a computer device is provided, comprising: a memory and a processor, wherein the memory is configured to store program instructions; and the processor is connected with the memory and configured to execute the above-mentioned user terminal registration method.

[0016] According to still another aspect of the embodiments of the present application, a non-volatile storage medium is provided, comprising a stored computer program, wherein a device in which the non-volatile storage medium is located executes the above-mentioned user terminal registration method by running the computer program.

[0017] According to still another aspect of the embodiments of the present application, a computer program product is provided, comprising computer instructions which, when executed by a processor, implement the above-mentioned user terminal registration method.

[0018] In the embodiment of the present application, the broadcast information and the user terminal configuration information are acquired, the type of the user terminal is determined according to the broadcast information and the configuration information, and in the case that the type is a satellite accessed Internet of Things terminal, an attach request is sent to a core network element to complete the registration of the user terminal, wherein the bearer establishment request information in the attach request is empty or the bearer establishment request information is not carried in the attach request, so that the purpose of reducing the information in the attach request is achieved, thereby realizing the technical effect of improving the signaling interaction efficiency, and further solving the technical problem of low interaction efficiency in the user terminal registration process in the related art. BRIEF DESCRIPTION OF DRAWINGS

[0019] The drawings described herein are used to provide further understanding of the present application, and form a part of the present application. The illustrative embodiments of the present application and their descriptions serve to explain the present application, and do not constitute improper limitations on the present application. In the drawings:

[0020] Figure 1 is a hardware structure block diagram of a computer terminal for implementing a user terminal registration method according to an embodiment of the present application;

[0021] Figure 2 is a flowchart of a user terminal registration method according to an embodiment of the present application;

[0022] Figure 3 is a flowchart of a user terminal sending an attach request according to an embodiment of the present application;

[0023] Figure 4 is a flowchart of another user terminal registration method according to an embodiment of the present application;

[0024] Figure 5 is a flowchart of still another user terminal registration method according to an embodiment of the present application;

[0025] Figure 6 is a structure schematic diagram of a communication system according to an embodiment of the present application;

[0026] Figure 7 is a structure schematic diagram of a user terminal registration device according to an embodiment of the present application. DETAILED DESCRIPTION

[0027] In order to enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, but not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor should fall within the scope of protection of the present application.

[0028] It should be noted that the terms "first", "second", and the like in the description and in the claims of the present application and in the above drawings are used only for distinguishing between similar objects and do not necessarily have a specific temporal or chronological order. It should be understood that the data thus designated can be interchanged under appropriate circumstances, so that the embodiments of the present application described herein can be carried out in other than the order illustrated or described herein. Furthermore, the terms "comprise" and "have" and any variations thereof are intended to cover a non-exclusive inclusion, for example, a process, method, system, product, or apparatus that comprises a list of steps or units is not necessarily limited to those steps or units that are clearly listed, but can include other steps or units that are not clearly listed or inherent to such processes, methods, products, or apparatus.

[0029] To solve the problems in the related art and achieve the technical effect of improving signaling interaction efficiency, an embodiment of the present application provides a user terminal registration method, which can be run in a computer terminal. Figure 1 The computer terminal is explained and described below.

[0030] The user terminal registration method embodiment provided by the present application can be executed in a mobile terminal, a computer terminal, or a similar computing device. Figure 1 A hardware structure block diagram of a computer terminal for implementing the user terminal registration method is shown. As shown in Figure 1 The computer terminal 10 can include one or more processors (processors can include but are not limited to processing devices such as microprocessors MCU or programmable logic devices FPGA, etc.), a memory 104 for storing data, and a transmission module 106 for communication function through wired and / or wireless network connection. In addition, it can also include a display, a keyboard, a cursor control device, an input / output interface (I / O interface), a universal serial bus (USB) port (which can be included as one of the ports of the I / O interface), a network interface, a BUS bus. Those skilled in the art can understand that the computer terminal 10 can include more or less components than those shown in Figure 1 The structure shown is only schematic, which does not limit the structure of the above-mentioned electronic device. For example, the computer terminal 10 can include more or less components than those shown in Figure 1 or have a different configuration than that shown in Figure 1

[0031] ​It should be noted that the one or more processors and / or other data processing circuitry described above can be referred to herein generically as "data processing circuitry." The data processing circuitry can be embodied as software, hardware, firmware, or any combination thereof, in whole or in part. Moreover, the data processing circuitry can be a single standalone processing module, or incorporated in whole or in part within any one of the other elements of the computer terminal 10. As referred to in the embodiments of the present application, the data processing circuitry functions as a processor to control, for example, the selection of the variable resistance terminal path in connection with the interface.

[0032] The memory 104 can be used to store software programs of application software and modules, such as program instructions / data storage means corresponding to the user terminal registration method in the embodiments of the present application. The processor executes various functional applications and data processing by running the software programs and modules stored in the memory 104, i.e. implements the user terminal registration method described above. The memory 104 can include a high-speed random access memory, and can further include a non-volatile memory, such as one or more magnetic storage devices, flash memories, or other non-volatile solid-state memories. In some examples, the memory 104 can further include a memory disposed remotely with respect to the processor, which can be connected to the computer terminal 10 through a network. Examples of the network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0033] The transmission module 106 is configured to receive or send data via a network. Specific examples of the network can include a wireless network provided by a communication provider of the computer terminal 10. In one example, the transmission module 106 includes a network interface controller (NIC) that can be connected to other network devices through a base station so as to be able to communicate with the Internet. In one example, the transmission module 106 can be a radio frequency (RF) module configured to communicate with the Internet in a wireless manner.

[0034] The display can be, for example, a touch screen type liquid crystal display (LCD) that enables a user to interact with the user interface of the computer terminal 10.

[0035] It should be noted that in some alternative embodiments, the above-mentioned Figure 1 The computer terminal shown can include hardware elements (including circuitry), software elements (including computer code stored on a computer readable medium), or a combination of both hardware and software elements. It should be noted that in some embodiments, the functions of the computer terminal described above can be implemented as a plurality of separate modules, or as a plurality of separate hardware components. Figure 1 is merely one example of a particular implementation, and is intended to illustrate the types of components that can be present in the computer terminal described above.

[0036] In the above operating environment, the embodiment of the present application provides a user terminal registration method, it should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although the logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from here.

[0037] Figure 2 is a flowchart of a user terminal registration method according to an embodiment of the present application, as shown in Figure 2 The method comprises the following steps:

[0038] Step S202, obtaining broadcast information and user terminal configuration information.

[0039] In the above step S202, the broadcast information is the broadcast information sent by the base station, and the configuration information at least includes whether the user terminal is an Internet of Things terminal.

[0040] Step S204, determining the type of the user terminal according to the broadcast information and the configuration information.

[0041] In the above step S204, the signal type of the broadcast information can be obtained from the broadcast information, and whether the user terminal is accessed through the satellite is determined based on the signal type.

[0042] Step S206, in the case that the type is a satellite access Internet of Things terminal, sending an attachment request to a core network element to complete the registration of the user terminal, wherein the bearer establishment request information in the attachment request is empty or the attachment request does not carry the bearer establishment request information.

[0043] It should be noted that the Internet of Things terminal can be NB-IOT (Narrow Band-Internet of Things, Narrow Band-Internet of Things device).

[0044] It can be understood that the ESM Message container (bearer establishment request information) is not carried in the attachment request, so the core network element does not send an activation default bearer request to the user terminal, and the user terminal does not need to establish an initial default bearer, directly completes the registration process, saves the signaling, and improves the interaction efficiency.

[0045] Through the above steps S202 to S206, the purpose of reducing the information in the attachment request is achieved, thereby realizing the technical effect of improving the signaling interaction efficiency, and further solving the technical problem of low interaction efficiency in the user terminal registration process in the related art. The following will be described in detail.

[0046] In step S206 of the above user terminal registration method, sending an attach request to a core network element comprises: sending the attach request to the core network element through a base station, the attach request being used to instruct the core network element to only establish a user plane bearer between the core network element and a serving gateway.

[0047] Specifically, the target signaling containing the attach request is sent to the base station through the access layer, the target signaling being used to trigger the base station to send an initial message containing the attach request to the core network element, wherein the attach request is sent to the access layer by a mobility management function entity in the user terminal, and the access layer sends the target signaling to the base station in response to receiving the attach request, as shown in Figure 3 As shown, no interaction is performed between an EMM (EPS Mobility Management) and an ESM (EPS Session Management), and the EMM directly sends an attach request not containing bearer establishment request information to an AS (access layer), the AS sends target signaling (RRC Conn Setup Comp, RRC connection setup success) to the base station in response to the attach request, and the base station sends an Initial UE Msg (initial user terminal message) to the core network element.

[0048] In some embodiments of the present application, the user terminal receives an attach accept message sent by the core network element, the attach accept message being used to represent that a user plane bearer between the core network element and the serving gateway has been established, the user plane bearer between the core network element and the serving gateway being determined by the core network element based on the type of the user terminal; and the registration of the user terminal is completed by a mobility management function entity in response to the attach accept message, wherein the attach accept message does not contain an active default bearer request.

[0049] Specifically, the Attach Accept message received by the terminal does not carry an ESM message container, that is, the network does not send an active default bearer request to the terminal, and the ESM in the user terminal does not establish an initial default bearer, and the registration process is completed by the EMM.

[0050] In the case where the user terminal needs a bearer, a bearer establishment request is sent to the core network element, wherein in the case where the bearer establishment request is to establish a default bearer, the bearer establishment request is used to request the core network element to establish a default bearer, and in the case where the bearer establishment request is to establish a dedicated bearer, the bearer establishment request is used to request the core network element to first establish a default bearer and then establish the dedicated bearer.

[0051] Specifically, the method provided by the embodiments of the present application completes the registration process of the user terminal, but does not establish an initial default bearer, and therefore, if the user terminal initiates a service based on a bearer, if the original process is to establish a default bearer, the original process is followed; if the terminal initiates a service based on a bearer, if the original process is to establish a dedicated bearer, the first default bearer is established, and then the corresponding dedicated bearer is established. For example, if the user terminal initiates a service based on a bearer, in the case where the default bearer can meet the demand of the service, the default bearer can be established, and in the case where the default bearer cannot meet the demand of the service, the default bearer is first established, and then the dedicated bearer that can meet the demand of the service is established.

[0052] In some embodiments of the present application, the user terminal sends the attachment request to the core network element, wherein the attachment request is used to indicate that the type of the user terminal is a satellite access IoT terminal, and in the case where the type of the user terminal is a satellite access IoT terminal, the core network element determines to establish only a user plane bearer between the core network element and a service gateway.

[0053] In some embodiments of the present application, the attachment request is sent to the core network element, wherein in the case where the bearer establishment request information in the attachment request is not empty, the core network element determines whether the user terminal is a satellite access IoT terminal according to the attachment request, and in the case where the type of the user terminal is a satellite access IoT terminal, the core network element determines that the bearer establishment request is a suspension processing request.

[0054] Figure 4 Another user terminal registration process is shown, as shown in Figure 4 Step 1: After the user terminal receives the satellite broadcast, in the case where the user terminal is accessed by a satellite and the user terminal itself is an NB-IOT, the EMM module of the user terminal does not interact with the ESM module, and the initial message of the user terminal does not carry a normal ESM Message container or the ESM Message container is empty.

[0055] Step 2: The user terminal sends an attachment request not carrying an ESM Message container to the base station;

[0056] Specifically, the user terminal sends an initial UE Message to the network based on the RRC Connection Setup Complete message, and the message does not contain an ESM Message container or the container is empty.

[0057] Step 3, authentication and location update of the user terminal are completed;

[0058] Step 4, the MME determines that only an S11-U user plane bearer between the MME and the SGW needs to be established for the NB IoT type terminal of the satellite access type based on the current access type of the user terminal.

[0059] Step 5, a GTP-U path between the MME and the SGW is established.

[0060] Step 6, the core network element sends a message to the user terminal, indicating that the GTP-U path has been established.

[0061] Step 7, the Attach Accept message received by the user terminal does not carry an ESM message container, that is, the network does not send an activation default bearer request to the terminal, the terminal ESM does not establish an initial default bearer, and the EMM continues to process, completing the registration process.

[0062] The embodiment of the application also provides another user terminal registration method, as shown in Figure 5 The method comprises the following steps:

[0063] Step S502, receiving an attachment request sent by the user terminal;

[0064] Step S504, determining the type of the user terminal according to the attachment request, and establishing only a user plane bearer between the core network element and a service gateway in the case that the user terminal is an IoT terminal of satellite access;

[0065] Step S506, sending an attachment acceptance message to the user terminal to complete the registration of the user terminal, wherein the attachment acceptance message does not contain an activation default bearer request.

[0066] The embodiment of the application also provides a communication system, as shown in Figure 6 The system comprises:

[0067] a user terminal 60 and a core network element 62;

[0068] The user terminal 60 is configured to send an attachment request to the core network element 62 in the case that the user terminal is an IoT terminal of satellite access.

[0069] The core network element 62 is configured to complete the registration of the user terminal 60 in response to the attachment request, wherein the attachment request is empty or does not carry the bearer establishment request information.

[0070] Figure 7is a structural diagram of a user terminal registration device according to an embodiment of the present application, as shown in the figure, the device comprises: Figure 7

[0071] An acquisition module 70 is configured to acquire broadcast information and user terminal configuration information.

[0072] A determination module 72 is configured to determine the type of the user terminal according to the broadcast information and the configuration information.

[0073] A registration module 74 is configured to, in the case where the type is a satellite access Internet of Things terminal, send an attachment request to a core network element to complete the registration of the user terminal, wherein the bearer establishment request information in the attachment request is empty or the attachment request does not carry the bearer establishment request information.

[0074] Through the above-mentioned user terminal registration device, the purpose of reducing the information in the attachment request is achieved, thereby realizing the technical effect of improving the signaling interaction efficiency, and further solving the technical problem of low interaction efficiency in the user terminal registration process in the related art.

[0075] In the registration module 74 in the above-mentioned user terminal registration device, a sending sub-module is configured to send an attachment request to a core network element, comprising: sending the attachment request to the core network element through a base station, the attachment request being used at least to instruct the core network element to only establish a user plane bearer between the core network element and a service gateway.

[0076] The sending sub-module comprises a sending unit and a registration unit. The sending unit is configured to send the attachment request to the core network element through a base station, comprising: sending a target signaling containing the attachment request to the base station through an access layer, the target signaling being used to trigger the base station to send an initial message containing the attachment request to the core network element, wherein the attachment request is sent to the access layer by a mobile management function entity in the user terminal, and the access layer sends the target signaling to the base station in response to receiving the attachment request.

[0077] The registration unit is configured to complete the registration of the user terminal, comprising: receiving an attachment acceptance message sent by the core network element, the attachment acceptance message being used to represent that the user plane bearer between the core network element and the service gateway has been established, the user plane bearer between the core network element and the service gateway being determined by the core network element based on the type of the user terminal; and in response to the attachment acceptance message, completing the registration of the user terminal through a mobile management function entity, wherein the attachment acceptance message does not contain an activation default bearer request.

[0078] ​The user terminal registration apparatus further comprises a bearer establishment submodule, configured to send a bearer establishment request to the core network element when the user terminal requires a bearer, wherein the bearer establishment request is used to request the core network element to establish a default bearer when the bearer establishment request is used to request to establish a default bearer, and the bearer establishment request is used to request the core network element to first establish a default bearer and then establish a dedicated bearer when the bearer establishment request is used to request to establish a dedicated bearer.

[0079] The registration module 74 further comprises an establishment submodule, configured to send the attach request to the core network element, wherein the attach request is used to indicate that the type of the user terminal is a satellite access IoT terminal, and the core network element determines to establish only a user plane bearer between the core network element and a serving gateway when the type of the user terminal is a satellite access IoT terminal.

[0080] The registration module 74 further comprises a determination submodule, configured to send the attach request to the core network element, wherein the core network element determines whether the user terminal is a satellite access IoT terminal according to the attach request when bearer establishment request information in the attach request is not empty, and the core network element determines that the bearer establishment request is a suspension processing request when the type of the user terminal is a satellite access IoT terminal.

[0081] It should be noted that, Figure 7 The user terminal registration apparatus shown is configured to execute the user terminal registration method shown, and thus the related explanations and descriptions in the user terminal registration method apply to the user terminal registration apparatus, which will not be described herein again. Figure 2 The user terminal registration method shown, and thus the related explanations and descriptions in the user terminal registration method apply to the user terminal registration apparatus, which will not be described herein again.

[0082] The embodiments of the present application further provide a computer device, comprising a memory and a processor, wherein the memory is configured to store program instructions, and the processor is connected with the memory and configured to execute the user terminal registration method.

[0083] The embodiments of the present application further provide a nonvolatile storage medium, comprising a stored computer program, wherein a device where the nonvolatile storage medium is located executes the user terminal registration method by running the computer program.

[0084] The embodiments of the present application further provide a computer program product, comprising a nonvolatile computer readable storage medium, and the nonvolatile computer readable storage medium stores a computer program, and the computer program is executed by a processor to implement the steps of the user terminal registration method in the present application.

[0085] The embodiment of the present application further provides a computer program product comprising computer instructions which, when executed by a processor, implement the steps of the user terminal registration method in the present application.

[0086] The embodiment of the present application further provides a computer program which, when executed by a processor, implements the steps of the user terminal registration method in the present application.

[0087] The above-mentioned serial numbers of the embodiments of the present application are only for description, and do not represent the advantages or disadvantages of the embodiments.

[0088] In the above-mentioned embodiments of the present application, the description of each embodiment has its own focus, and the parts not described in detail in a certain embodiment can be referred to the relevant description of other embodiments.

[0089] In the several embodiments provided by the present application, it should be understood that the disclosed technology can be implemented in other ways. Of course, the unit embodiment described above is only schematic. For example, the division of the units can be a logical function division, and there can be another division manner in actual implementation, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection between the units can be indirect coupling or communication connection through some interface, electrical or other form.

[0090] The units described as separate components can or can not be physically separate, and the components shown as units can or can not be physical units, that is, they can be located in one place, or can be distributed on a plurality of units. Part or all of the units can be selected according to actual needs to achieve the purpose of the present embodiment.

[0091] In addition, each functional unit in each embodiment of the present application can be integrated into a processing unit, or each unit can exist physically, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be realized in the form of hardware or in the form of a software functional unit.

[0092] The integrated unit, if implemented in the form of a software function unit and sold or used as an independent product, can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application essentially or say the part that contributes to the prior art or the whole or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a server or a network device, etc.) to execute all or part of the steps of the method described in the various embodiments of the present application. The aforementioned storage medium includes various media that can store program codes, such as a U disk, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0093] The above is only the preferred embodiment of the present application, and it should be pointed out that for those skilled in the art, without departing from the principles of the present application, a number of improvements and refinements can be made, which should be considered as the protection scope of the present application.

Claims

1. A user terminal registration method, characterized by, The method comprises: obtaining broadcast information and user terminal configuration information; determining the type of the user terminal according to the broadcast information and the configuration information; in the case that the type is a satellite access Internet of Things terminal, sending an attachment request to a core network element to complete the registration of the user terminal, wherein the bearer establishment request information in the attachment request is empty or the attachment request does not carry the bearer establishment request information; in the case that the user terminal requires a bearer, sending a bearer establishment request to the core network element, wherein in the case that the bearer establishment request is for establishing a default bearer, the bearer establishment request is used to request the core network element to establish a default bearer, and in the case that the bearer establishment request is used to request to establish a dedicated bearer, the bearer establishment request is used to request the core network element to first establish a default bearer and then establish the dedicated bearer.

2. The method of claim 1, wherein, sending an attachment request to a core network element comprises: sending the attachment request to the core network element through a base station, the attachment request being used to instruct the core network element to only establish a user plane bearer between the core network element and a serving gateway.

3. The method of claim 2, wherein, sending the attachment request to the core network element through a base station comprises: sending a target signaling containing the attachment request to a base station through an access layer, the target signaling being used to trigger the base station to send an initial message containing the attachment request to the core network element, wherein the attachment request is sent by a mobile management function entity in the user terminal to the access layer, and the access layer sends the target signaling to the base station in response to receiving the attachment request.

4. The method of claim 2, wherein, completing the registration of the user terminal comprises: receiving an attachment acceptance message sent by the core network element, the attachment acceptance message being used to indicate that a user plane bearer between the core network element and the serving gateway has been established, the user plane bearer between the core network element and the serving gateway being determined by the core network element based on the type of the user terminal; in response to the attachment acceptance message, completing the registration of the user terminal through a mobile management function entity, wherein the attachment acceptance message does not contain an activation default bearer request.

5. The method of claim 1, wherein, The method further comprises: sending the attachment request to the core network element, wherein the attachment request is used to indicate that the type of the user terminal is a satellite access Internet of Things terminal, and in the case that the type of the user terminal is a satellite access Internet of Things terminal, the core network element determines to only establish a user plane bearer between the core network element and a serving gateway.

6. The method of claim 1, wherein, The method further comprises: sending the attachment request to the core network element, wherein in the case that the bearer establishment request information in the attachment request is not empty, the core network element determines whether the user terminal is a satellite access Internet of Things terminal according to the attachment request, and in the case that the type of the user terminal is a satellite access Internet of Things terminal, the core network element determines that the bearer establishment request is a suspension processing request.

7. A user terminal registration method characterized by comprising: The method comprises: receiving an attachment request sent by the user terminal; determining a type of the user terminal according to the attach request, and establishing a user plane bearer between a core network element and a serving gateway only in a case that the user terminal is a satellite accessed IoT terminal; sending an attach accept message to the user terminal to complete registration of the user terminal, wherein the attach accept message does not contain an activate default bearer request; in a case that the user terminal requires a bearer, sending a bearer establishment request to the core network element, wherein in a case that the bearer establishment request is for establishing a default bearer, the bearer establishment request is used to request the core network element to establish a default bearer, and in a case that the bearer establishment request is for establishing a dedicated bearer, the bearer establishment request is used to request the core network element to first establish a default bearer and then establish the dedicated bearer.

8. A user terminal registration apparatus characterized by comprising: comprising: an obtaining module, configured to obtain broadcast information and user terminal configuration information; a determining module, configured to determine a type of the user terminal according to the broadcast information and the configuration information; a registering module, configured to, in a case that the type is a satellite accessed IoT terminal, send an attach request to a core network element to complete registration of the user terminal, wherein bearer establishment request information in the attach request is empty or the attach request does not carry the bearer establishment request information; in a case that the user terminal requires a bearer, sending a bearer establishment request to the core network element, wherein in a case that the bearer establishment request is for establishing a default bearer, the bearer establishment request is used to request the core network element to establish a default bearer, and in a case that the bearer establishment request is for establishing a dedicated bearer, the bearer establishment request is used to request the core network element to first establish a default bearer and then establish the dedicated bearer.

9. A communication system, characterized by comprising: a user terminal and a core network element; the user terminal is configured to, in a case that the type of the user terminal is a satellite accessed IoT terminal, send an attach request to a core network element; the core network element is configured to, in response to the attach request, complete registration of the user terminal, wherein bearer establishment request information in the attach request is empty or the attach request does not carry the bearer establishment request information; in a case that the user terminal requires a bearer, sending a bearer establishment request to the core network element, wherein in a case that the bearer establishment request is for establishing a default bearer, the bearer establishment request is used to request the core network element to establish a default bearer, and in a case that the bearer establishment request is for establishing a dedicated bearer, the bearer establishment request is used to request the core network element to first establish a default bearer and then establish the dedicated bearer.

10. A computer device, comprising: comprising: a memory and a processor, wherein the memory is configured to store program instructions; the processor, connected with the memory, is configured to execute the user terminal registration method in any one of claims 1 to 6.

11. A non-volatile storage medium, comprising: the non-volatile storage medium comprises a stored computer program, wherein a device where the non-volatile storage medium is located executes the user terminal registration method in any one of claims 1 to 6 by running the computer program.

12. A computer program product comprising computer instructions, characterized in that, The computer instructions, when executed by a processor, implement the user terminal registration method of any one of claims 1 to 6.

Images