阅读说明：本技术 终端、网络接入方法、装置、系统和计算机可读存储介质 (Terminal, network access method, device, system and computer readable storage medium ) 是由 谢沛荣 陈洁 龙彪 李文苡 刘柳 刘佳一凡 王庆扬 曹磊 赵晔 王波 于 2018-07-03 设计创作，主要内容包括：本公开涉及一种终端、网络接入方法、装置、系统和计算机可读存储介质,涉及移动通信技术领域。该终端包括：接收器用于接收网络侧下发的允许接入切片列表,允许接入切片列表中包含各网络切片的接入信息,接入信息包括网络切片的第一标识和第二标识,第一标识用于指示所述网络切片所属的AMF实体,第二标识用于指示网络切片可否被切换；处理器用于响应于用户想要接入新的网络切片,根据第一切片的接入信息和第二切片的接入信息,确定是否断开与第一切片的连接和是否接入第二切片,第一切片为当前接入的网络切片,第二切片为想要接入的网络切片。本公开的技术方案能够提高系统的灵活性和业务处理效率。(The disclosure relates to a terminal, a network access method, a device, a system and a computer readable storage medium, and relates to the technical field of mobile communication. The terminal includes: the receiver is used for receiving an access-allowed slice list issued by a network side, the access-allowed slice list comprises access information of each network slice, the access information comprises a first identifier and a second identifier of the network slice, the first identifier is used for indicating an AMF entity to which the network slice belongs, and the second identifier is used for indicating whether the network slice can be switched or not; the processor is used for responding to the fact that a user wants to access a new network slice, and determining whether to disconnect the first slice and access the second slice according to the access information of the first slice and the access information of the second slice, wherein the first slice is a network slice which is accessed currently, and the second slice is a network slice which is wanted to be accessed. The technical scheme of the disclosure can improve the flexibility and the service processing efficiency of the system.)

1. A terminal, comprising:

a receiver, configured to receive an allowed access slice list issued by a network side, where the allowed access slice list includes access information of each network slice, the access information includes a first identifier and a second identifier of the network slice, the first identifier is used to indicate an access and mobility management function (AMF) entity to which the network slice belongs, and the second identifier is used to indicate whether the network slice may be switched;

a processor, configured to determine whether to disconnect from a first slice and access to a second slice according to the access information of the first slice and the access information of the second slice in response to a user wanting to access a new network slice, where the first slice is a currently accessed network slice and the second slice is a wanted network slice.

2. The terminal of claim 1, wherein,

the processor is used for

Judging whether the first identifications of the first slice and the second slice are the same;

in the same case, the terminal remains connected to the first slice and accesses the second slice; and if not, determining whether to disconnect the first slice and access the second slice according to the second identifier of the first slice.

3. The terminal of claim 2, wherein,

the access information also comprises a switching priority determined according to the subscription information of the user;

the processor is used for

In the event that the first slice cannot be switched, maintaining a connection with the first slice without accessing the second slice;

judging whether the switching priority of the first slice is higher than that of the second slice or not under the condition that the first slice can be switched;

in the case of elevation, maintaining a connection with the first slice without accessing the second slice;

in case of a lower, the connection to the first slice is disconnected and the second slice is switched in.

4. A terminal according to any of claims 1-3,

and the first identifier and the second identifier are generated by a slice selection function NSSF entity or an AMF entity according to subscription information of the user.

5. The terminal of claim 4, wherein,

and the subscription information of the user is acquired by the AMF entity through a unified data management function (UDM) entity.

6. A terminal according to any of claims 1-3,

the receiver receives the list of allowed access slices via an AMF entity.

7. A network access method, comprising:

receiving an access-allowed slice list issued by a network side, wherein the access-allowed slice list comprises access information of each network slice, the access information comprises a first identifier and a second identifier of the network slice, the first identifier is used for indicating an access and mobility management function (AMF) entity to which the network slice belongs, and the second identifier is used for indicating whether the network slice can be switched or not;

in response to a user's desire to access a new network slice, determining whether to disconnect from the first slice and whether to access the second slice according to the access information of the first slice and the access information of the second slice, wherein the first slice is a currently accessed network slice and the second slice is a desired network slice.

8. The network access method of claim 7,

judging whether the first identifications of the first slice and the second slice are the same;

in the same case, the terminal remains connected to the first slice and accesses the second slice;

and if not, determining whether to disconnect the first slice and access the second slice according to the second identifier of the first slice.

9. The network access method of claim 7,

the access information also comprises a switching priority determined according to the subscription information of the user;

the determining whether to disconnect from the first slice and whether to access the second slice according to the second identification of the first slice comprises:

in the event that the first slice cannot be switched, maintaining a connection with the first slice without accessing the second slice;

judging whether the switching priority of the first slice is higher than that of the second slice or not under the condition that the first slice can be switched;

in the case of elevation, maintaining a connection with the first slice without accessing the second slice;

in case of a lower, the connection to the first slice is disconnected and the second slice is switched in.

10. A network access method, comprising:

generating an allowed access slice list, wherein the allowed access slice list contains access information of each network slice, the access information comprises a first identifier and a second identifier of the network slice, the first identifier is used for indicating an access and mobility management function (AMF) entity to which the network slice belongs, and the second identifier is used for indicating whether the network slice can be switched or not;

issuing the list of the allowed access slices so that the terminal responds to a new network slice which a user wants to access, and determining whether to disconnect the first slice and access the second slice according to the access information of the first slice and the access information of the second slice, wherein the first slice is a currently accessed network slice, and the second slice is a network slice which the user wants to access;

and matching the terminal to access or disconnect the corresponding network slice.

11. A network access device, comprising:

a memory; and

a processor coupled to the memory, the processor configured to perform one or more steps of the network access method of any of claims 7-10 based on instructions stored in the memory device.

12. A network access system, comprising:

the slice selection function NSSF entity is selected,

the network slice switching method comprises the steps of generating an allowed access slice list in response to user registration, wherein the allowed access slice list contains access information of each network slice, the access information comprises a first identifier and a second identifier of each network slice, the first identifier is used for indicating an access and mobility management function (AMF) entity to which the network slice belongs, and the second identifier is used for indicating whether the network slice can be switched or not;

the AMF entity is also used for issuing the list of the allowed access slices to the user;

and the terminal is used for receiving the list of the allowed access slices, responding to the situation that the user wants to access a new network slice, and determining whether to disconnect the first slice and access the second slice according to the access information of the first slice and the access information of the second slice, wherein the first slice is a currently accessed network slice, and the second slice is a network slice which wants to be accessed.

13. A computer readable storage medium having stored thereon a computer program which, when executed by a processor, performs one or more steps of the network access method of any of claims 7-10.

Technical Field

The present disclosure relates to the field of mobile communications technologies, and in particular, to a terminal, a network access method, a network access apparatus, a network access system, and a computer-readable storage medium.

Background

The concept of network slices is introduced into the 5G system, each network slice can have different mobility, safety, time delay and reliability, even a charging mode, and can better provide wide connection service for various industries.

Disclosure of Invention

The inventors of the present disclosure found that the following problems exist in the above-described related art: only network slices sharing the same AMF entity with the current network slice can be accessed simultaneously, resulting in poor system flexibility and low service processing efficiency.

In view of this, the present disclosure provides a network access technical solution, which can improve the flexibility of the system and the service processing efficiency.

According to some embodiments of the present disclosure, there is provided a terminal including: a receiver, configured to receive an allowed Access slice list issued by a network side, where the allowed Access slice list includes Access information of each network slice, the Access information includes a first identifier and a second identifier of the network slice, the first identifier is used to indicate an AMF (Access and Mobility Management Function) entity to which the network slice belongs, and the second identifier is used to indicate whether the network slice can be switched; a processor, configured to determine whether to disconnect from a first slice and access to a second slice according to the access information of the first slice and the access information of the second slice in response to a user wanting to access a new network slice, where the first slice is a currently accessed network slice and the second slice is a wanted network slice.

In some embodiments, the processor is configured to determine whether the first identifier of the first slice is the same as the first identifier of the second slice; in the same case, the terminal remains connected to the first slice and accesses the second slice; and if not, determining whether to disconnect the first slice and access the second slice according to the second identifier of the first slice.

In some embodiments, the access information further includes a handover priority determined according to subscription information of the user; the processor is configured to maintain a connection with the first slice without accessing the second slice if the first slice is not switchable; judging whether the switching priority of the first slice is higher than that of the second slice or not under the condition that the first slice can be switched; in the case of elevation, maintaining a connection with the first slice without accessing the second slice; in case of a lower, the connection to the first slice is disconnected and the second slice is switched in.

In some embodiments, the first identifier and the second identifier are generated by an NSSF (Network slice selection Function) entity or an AMF entity according to subscription information of the user.

In some embodiments, the subscription information of the user is obtained by the AMF entity via a UDM (Unified data management function) entity.

In some embodiments, the receiver obtains the list of allowed access slices via an AMF entity.

According to further embodiments of the present disclosure, there is provided a network access method including: receiving an access permission slice list issued by a network side, wherein the access permission slice list comprises access information of each network slice, the access information comprises a first identifier and a second identifier of the network slice, the first identifier is used for indicating an AMF entity to which the network slice belongs, and the second identifier is used for indicating whether the network slice can be switched or not; in response to a user's desire to access a new network slice, determining whether to disconnect from the first slice and whether to access the second slice according to the access information of the first slice and the access information of the second slice, wherein the first slice is a currently accessed network slice and the second slice is a desired network slice.

In some embodiments, determining whether the first identity of the first slice and the second slice is the same; in the same case, the terminal remains connected to the first slice and accesses the second slice; and if not, determining whether to disconnect the first slice and access the second slice according to the second identifier of the first slice.

In some embodiments, the access information further includes a handover priority determined according to subscription information of the user; the determining whether to disconnect from the first slice and whether to access the second slice according to the second identification of the first slice comprises: in the event that the first slice cannot be switched, maintaining a connection with the first slice without accessing the second slice; judging whether the switching priority of the first slice is higher than that of the second slice or not under the condition that the first slice can be switched; in the case of elevation, maintaining a connection with the first slice without accessing the second slice; in case of a lower, the connection to the first slice is disconnected and the second slice is switched in.

According to still other embodiments of the present disclosure, there is provided a network access method including: generating an allowed access slice list, wherein the allowed access slice list contains access information of each network slice, the access information comprises a first identifier and a second identifier of the network slice, the first identifier is used for indicating an AMF entity to which the network slice belongs, and the second identifier is used for indicating whether the network slice can be switched or not; issuing the list of the allowed access slices so that the terminal responds to a new network slice which a user wants to access, and determining whether to disconnect the first slice and access the second slice according to the access information of the first slice and the access information of the second slice, wherein the first slice is a currently accessed network slice, and the second slice is a network slice which the user wants to access; and matching the terminal to access or disconnect the corresponding network slice.

According to still further embodiments of the present disclosure, there is provided a network access apparatus including: a memory; and a processor coupled to the memory, the processor configured to perform one or more steps of the network access method in any of the above embodiments based on instructions stored in the memory device.

According to still further embodiments of the present disclosure, there is provided a network access system including: the NSSF entity is used for responding to user registration and generating an allowed access slice list, wherein the allowed access slice list contains access information of each network slice, the access information comprises a first identifier and a second identifier of the network slice, the first identifier is used for indicating an AMF entity to which the network slice belongs, and the second identifier is used for indicating whether the network slice can be switched or not; the AMF entity is also used for issuing the list of the allowed access slices to the user; and the terminal is used for receiving the list of the allowed access slices, responding to the situation that the user wants to access a new network slice, and determining whether to disconnect the first slice and access the second slice according to the access information of the first slice and the access information of the second slice, wherein the first slice is a currently accessed network slice, and the second slice is a network slice which wants to be accessed.

According to still further embodiments of the present disclosure, there is provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements one or more steps of a network access method in any of the above embodiments.

In the above embodiment, the terminal may automatically determine whether to switch to access a new network slice according to the access information, where the access information is added to the issued allowed access slice list to indicate the AMF entity to which the network slice belongs and whether to be switched. Therefore, the terminal can simultaneously access different network slices belonging to the same AMF entity according to the service requirement, and can also switch to access new network slices belonging to different AMF entities, thereby improving the flexibility of the system and the service processing efficiency.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the description, serve to explain the principles of the disclosure.

The present disclosure may be more clearly understood from the following detailed description, taken with reference to the accompanying drawings, in which:

fig. 1 illustrates a flow diagram of some embodiments of a network access method of the present disclosure;

FIG. 2 illustrates a flow diagram of some embodiments of step 120 in FIG. 1;

FIG. 3 shows a flow diagram of further embodiments of step 120 of FIG. 1;

fig. 4 shows a flow diagram of further embodiments of the network access method of the present disclosure;

fig. 5 illustrates a signaling diagram of some embodiments of the network access method of the present disclosure;

fig. 6 illustrates a block diagram of some embodiments of a network access system of the present disclosure;

fig. 7 illustrates a block diagram of some embodiments of a terminal of the present disclosure;

fig. 8 shows a block diagram of further embodiments of a terminal of the present disclosure;

fig. 9 illustrates a block diagram of still further embodiments of the terminal of the present disclosure.

Detailed Description

Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that: the relative arrangement of the components and steps, the numerical expressions, and numerical values set forth in these embodiments do not limit the scope of the present disclosure unless specifically stated otherwise.

Meanwhile, it should be understood that the sizes of the respective portions shown in the drawings are not drawn in an actual proportional relationship for the convenience of description.

The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the disclosure, its application, or uses.

Techniques, methods, and apparatus known to those of ordinary skill in the relevant art may not be discussed in detail but are intended to be part of the specification where appropriate.

In all examples shown and discussed herein, any particular value should be construed as merely illustrative, and not limiting. Thus, other examples of the exemplary embodiments may have different values.

It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, further discussion thereof is not required in subsequent figures.

Fig. 1 illustrates a flow diagram of some embodiments of a network access method of the present disclosure.

As shown in fig. 1, the method includes: step 110, receiving a list of allowed access slices; and step 120, determining the accessed network slice.

In step 110, the list of slices allowed to be accessed, which is issued by the network side, is received. The allowed access slice list includes access information of each network slice, and the access information includes a first identifier and a second identifier of the network slice. The first identifier is used for indicating the AMF entity to which the network slice belongs, and the second identifier is used for indicating whether the network slice can be switched or not. For example, the terminal may acquire the list of allowed access slices via the AMF entity.

In some embodiments, the AMF entity obtains information about a network slice that a user wishes to access, and obtains subscription information of the user via the UDM entity. The list of allowed access slices corresponding to the user can be generated according to the related information of the network slice that the user wishes to access. The first identity and the second identity may be determined based on subscription information of the user. For example, the AMF entity may generate the allowed access slice list itself, or may send the related information of the network slice desired to be accessed and the subscription information to the NSSF entity, and the NSSF entity generates the allowed access slice list.

In some embodiments, since network slices belonging to the same AMF entity can be accessed concurrently, and network slices belonging to two different AMF entities cannot be accessed concurrently, network slices belonging to the same AMF entity may be regarded as belonging to the same "coexistence group". Network slices belonging to the same "coexistence group" have the same first identity to indicate whether two network slices can be accessed simultaneously.

In some embodiments, the user may configure in the subscription information which network slices may be "preempted" for connection by other network slices while in the connected state, and the AMF entity or the NSSF entity may configure the second identity of the network slice according to the subscription information. For network slices with different first identifications, whether the current network slice can be disconnected and a new network slice can be accessed can be judged according to the second identification, namely whether the new network slice can 'preempt' the current network slice.

Through the above embodiments, a reliable basis can be provided for real-time switching of network slices, thereby improving the flexibility of the system.

In step 120, in response to the user's desire to access a new network slice, it is determined whether to disconnect from the first slice and whether to access the second slice based on the access information of the first slice and the access information of the second slice. The first slice is the currently accessed network slice, and the second slice is the desired network slice.

In this way, the terminal can automatically determine whether the current network slice and the new network slice can be accessed simultaneously or whether the current network slice can be disconnected from accessing the new network slice according to the first identifier and the second identifier added in the allowed access slice list.

Compared with the related technology, even if the new network slice and the current network slice do not belong to the same AMF, the new network slice can be switched according to the service requirement or user configuration, so that the flexibility of the system and the service processing efficiency are improved.

In some embodiments, step 120 may be implemented by the means of fig. 2.

Fig. 2 illustrates a flow diagram of some embodiments of step 120 in fig. 1.

As shown in fig. 2, step 120 includes: step 1210, the user wants to access a new network slice; step 1220, judging whether the existing slice and the new slice belong to the same AMF entity; step 1230, simultaneously accessing the existing slice and the new slice; step 1240, judging whether the existing slice is allowed to be switched; step 1250, exiting the existing slice and accessing the new slice; and step 1260, keeping the existing slice and canceling the new slice.

In step 1201, a user who has accessed the first slice wants to access the second slice.

In step 1220, it is determined whether the first identifier is the same for the first slice and the second slice. If so, go to step 1230; if not, step 1240 is performed.

In step 1230, the terminal remains connected to the first slice and accesses the second slice. The first identifiers are same, and the two network slices belong to the same 'coexistence group', and can be accessed in parallel.

In step 1240, it is determined whether the first slice is allowed to be switched based on the second identifier of the first slice. The first identifiers are different, which means that the two network slices do not belong to the same 'coexistence group' and can not be accessed in parallel. Thus, it can be confirmed by the second identity whether the user allows the network slice to be "preempted" in the subscription information to decide which network slice to access.

Where permitted, perform step 1250; in case not allowed, step 1260 is performed.

In step 1250, the first slice is exited and the second slice is accessed. Therefore, even if the new network slice and the current network slice do not belong to the same AMF, the new network slice can be switched according to the service requirement or user configuration, so that the flexibility of the system and the service processing efficiency are improved.

In step 1260, the first slice is kept and the second slice is not accessed.

In some embodiments, step 120 may also be implemented by the means of fig. 3.

FIG. 3 shows a flow diagram of further embodiments of step 120 of FIG. 1.

As shown in fig. 3, compared to the embodiment in fig. 2, step 120 further includes: in step 1241, it is determined whether the priority of the current slice is higher than the priority of the new slice. In this embodiment, the access information further includes a handover priority of the network slice determined according to the subscription information of the user.

Step 1210-1240 in fig. 3 is the same as that in fig. 2, and will not be described herein again. In case the second identification of the first slice indicates that the first slice is allowed to be switched, step 1241 is performed.

In step 1241, it is determined whether the switching priority of the first slice is higher than the switching priority of the second slice. If not, step 1250 is performed; if so, step 1260 is performed.

In step 1250, the first slice is exited and the second slice is accessed. For example, the user configures the second slice in the subscription information to have a higher handover priority than the first slice, and thus, may choose to access the second slice to meet the user's current business requirements.

In step 1260, the first slice is kept and the second slice is not accessed. For example, the user configures a first slice in subscription information with a higher handover priority than a second slice, and thus may choose to access the first slice to satisfy the user configuration.

Therefore, under the condition that the new network slice and the current network slice do not belong to the same AMF, the appropriate network slice can be selected and switched to be accessed according to the subscription information of the user so as to meet the service requirement or configuration of the user, and therefore the flexibility of the system and the service processing efficiency are improved.

In the above embodiment, the terminal may automatically determine whether to switch to access a new network slice according to the access information, where the access information is added to the issued allowed access slice list to indicate the AMF entity to which the network slice belongs and whether to be switched. Therefore, the terminal can simultaneously access different network slices belonging to the same AMF entity according to the service requirement, and can also switch to access new network slices belonging to different AMF entities, thereby improving the flexibility of the system and the service processing efficiency.

Fig. 4 shows a flow diagram of further embodiments of the network access method of the present disclosure.

As shown in fig. 4, the method includes: step 410, generating a list of slices allowed to be accessed; step 420, issuing an access-allowed slice list; and step 430, connecting or disconnecting the network slice.

In step 410, the NSSF entity or the access and AMF entities generate a list of allowed access slices in response to the user registration.

In step 420, the NSSF entity issues the list of allowed access slices to the terminal of the user via the AMF entity. In response to the user's desire to access a new network slice, the terminal determines whether to disconnect from the first slice and whether to access the second slice based on the access information of the first slice and the access information of the second slice.

In step 430, the cooperating terminal accesses or disconnects the corresponding network slice.

In some embodiments, any of the above embodiments may be implemented by the signaling diagram in fig. 5.

Fig. 5 illustrates a signaling diagram of some embodiments of the network access method of the present disclosure.

As shown in fig. 5, in event 501, the terminal 51 sends a registration request to the AMF entity 52.

In event 502, the terminal 51, together with the AMF entity 52 and other related network elements, completes the authentication of the user. The AMF entity 52 obtains subscription information of the user from the UDM entity (not shown).

At event 503, the AMF entity 52 sends a slice selection request to the NSSF entity 53, where the slice selection request carries information about a network slice subscribed by the user and information about a network slice that the user currently desires to access.

In event 504, the NSSF entity 53 returns a slice selection reply message to the AMF entity 52 carrying the list of allowed access slices. The related information of each network slice of the allowed access slice list comprises a first identifier, a second identifier and a switching priority.

For example, the network slice 54 and the network slice 55 are included in the allowed access slice list. The first identification of the network slice 54 is 1, the second identification is switchable, and the switching priority is 9. The first identifier of the network slice 55 is 2, the second identifier is not switchable, and the switching priority is 3 (for example, the smaller the priority number, the higher the priority can be set).

In event 505, the AMF entity 52 returns a registration response to the terminal 51, where the registration response carries the list of allowed access slices.

At event 506, the user accesses the network slice 54 via the terminal 51 to conduct the service.

In event 507, the user wishes to re-access the network slice 55. The terminal 51 can learn from the list of allowed access slices: network slice 54 belongs to a different "coexistence group" than network slice 55; network slices 54 may be "preempted"; the handover priority (3) of the network slice 55 is higher than the handover priority (9) of the network slice 54. According to the method in any of the above embodiments, the terminal may make a decision to exit the network slice 54 and access the network slice 55.

In event 508, the terminal 51 exits the network slice 54.

In event 509, the terminal 51 accesses the network slice 55.

Fig. 6 illustrates a block diagram of some embodiments of a network access system of the present disclosure.

As shown in fig. 6, the network access system 6 includes an NSSF entity 61 and a terminal 62.

The NSSF entity 61 generates the allowed access slice list in response to the user registration and is also used to issue the allowed access slice list to the user via the AMF entity.

The terminal 62 receives the list of allowed access slices, and in response to a user's desire to access a new network slice, determines whether to disconnect from the first slice and whether to access the second slice based on the access information of the first slice and the access information of the second slice.

Fig. 7 illustrates a block diagram of some embodiments of a terminal of the present disclosure.

As shown in fig. 7, the terminal 7 includes a receiver 71 and a processor 72.

The receiver 71 receives the list of allowed access slices issued by the network side. The processor 72 determines whether to disconnect from the first slice and whether to access the second slice based on the access information of the first slice and the access information of the second slice in response to the user wanting to access a new network slice.

In some embodiments, processor 72 determines whether the first identifier of the first slice is the same as the first identifier of the second slice. In the same case, the terminal remains connected to the first slice and accesses the second slice; and in case of not being identical, determining whether to disconnect the first slice and to access the second slice according to the second identifier of the first slice.

In some embodiments, the access information further includes a handover priority determined according to subscription information of the user. The processor 72 remains connected to the first slice and does not access the second slice in the event that the first slice cannot be switched. And in the case that the first slice can be switched, judging whether the switching priority of the first slice is higher than that of the second slice. In case of a higher than, the connection with the first slice is maintained, and the second slice is not accessed; in the case of undershoot, the connection to the first slice is broken and the second slice is accessed.

In the above embodiment, the terminal may automatically determine whether to switch to access a new network slice according to the access information, where the access information is added to the issued allowed access slice list to indicate the AMF entity to which the network slice belongs and whether to be switched. Therefore, the terminal can simultaneously access different network slices belonging to the same AMF entity according to the service requirement, and can also switch to access new network slices belonging to different AMF entities, thereby improving the flexibility of the system and the service processing efficiency.

Fig. 8 shows a block diagram of further embodiments of a terminal of the present disclosure.

As shown in fig. 8, the terminal 8 of this embodiment includes: a memory 81 and a processor 82 coupled to the memory 81, the processor 82 being configured to perform one or more steps of the network access method in any one of the embodiments of the present disclosure based on instructions stored in the memory 81.

The memory 81 may include, for example, a system memory, a fixed nonvolatile storage medium, and the like. The system memory stores, for example, an operating system, an application program, a Boot Loader (Boot Loader), a database, and other programs.

Fig. 9 illustrates a block diagram of still further embodiments of the terminal of the present disclosure.

As shown in fig. 9, the terminal 9 of this embodiment includes: a memory 910 and a processor 920 coupled to the memory 910, the processor 920 being configured to execute the network access method in any of the embodiments based on instructions stored in the memory 910.

The memory 910 may include, for example, system memory, fixed non-volatile storage media, and the like. The system memory stores, for example, an operating system, an application program, a Boot Loader (Boot Loader), and other programs.

The terminal 9 may further include an input-output interface 930, a network interface 940, a storage interface 950, and the like. These interfaces 930, 940, 950 and the memory 910 and the processor 920 may be connected, for example, by a bus 960. The input/output interface 930 provides a connection interface for input/output devices such as a display, a mouse, a keyboard, and a touch screen. The network interface 940 provides a connection interface for various networking devices. The storage interface 940 provides a connection interface for external storage devices such as an SD card and a usb disk.

As will be appreciated by one skilled in the art, embodiments of the present disclosure may be provided as a method, system, or computer program product. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present disclosure may take the form of a computer program product embodied on one or more computer-usable non-transitory storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

Up to this point, a terminal, a network access method, a network access apparatus, a network access system, and a computer-readable storage medium according to the present disclosure have been described in detail. Some details that are well known in the art have not been described in order to avoid obscuring the concepts of the present disclosure. It will be fully apparent to those skilled in the art from the foregoing description how to practice the presently disclosed embodiments.

The method and system of the present disclosure may be implemented in a number of ways. For example, the methods and systems of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above unless specifically stated otherwise. Further, in some embodiments, the present disclosure may also be embodied as programs recorded in a recording medium, the programs including machine-readable instructions for implementing the methods according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.

Although some specific embodiments of the present disclosure have been described in detail by way of example, it should be understood by those skilled in the art that the foregoing examples are for purposes of illustration only and are not intended to limit the scope of the present disclosure. It will be appreciated by those skilled in the art that modifications may be made to the above embodiments without departing from the scope and spirit of the present disclosure. The scope of the present disclosure is defined by the appended claims.