Method for allocating resources of a satellite-ground integrated network, core network device

Abstract

The application discloses a method for allocating resources of a satellite-ground integrated network and a core network device. The method comprises the following steps: receiving request information sent by a terminal, wherein the request information is used for requesting registration of a network slice; forwarding the request information to a core network device, wherein the core network device comprises a core network entity of a ground network and a core network entity of a satellite network; receiving return information generated by the core network device in response to the request information, wherein the return information comprises first return information containing a target slice identifier and second return information indicating that the terminal registers other types of network slices; in the case that the return information is the first return information, allocating network resources of a target network slice to the terminal, wherein the target network slice is a first network slice or a second network slice; and in the case that the return information is the second return information, transmitting the second return information to the terminal.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of satellite communication, in particular to a method for allocating resources of a satellite-terrestrial integrated network and a core network device. BACKGROUND

[0002] With the rapid development of high-throughput satellite communication technology, the communication capability of satellite networks in terms of rate, delay and reliability has been significantly improved, and can complement and cooperate with terrestrial networks; in a satellite-terrestrial integrated networking scenario formed by the cooperation of terrestrial networks and satellite networks, due to the characteristics of the network such as adjustable communication resources, strong ground mobility and dynamic network topology, and the possibility of multiple satellites covering a terminal, the method for allocating network resources in the related technology cannot be directly applied in the satellite-terrestrial integrated network.

[0003] At present, there is no effective solution to the above problems. SUMMARY

[0004] The embodiments of the present application provide a method for allocating resources of a satellite-terrestrial integrated network and a core network device to at least solve the technical problem that the utilization rate of satellite network resources cannot be improved in a satellite-terrestrial integrated networking scenario.

[0005] According to an aspect of an embodiment of the present application, a method for allocating resources of a satellite-terrestrial integrated network is provided, comprising: receiving request information sent by a terminal, wherein the request information is used to request to register a network slice, and the request information comprises: first type request information used to register a first type network slice, and second type request information used to register a second type network slice, the first type network slice being a network slice of a terrestrial network, and the second type network slice being a network slice of a satellite network; forwarding the request information to a core network device, wherein the core network device comprises: a core network entity of the terrestrial network and a core network entity of the satellite network; receiving return information generated by the core network device in response to the request information, wherein the return information comprises: first type return information containing a target slice identifier, and second type return information indicating that the terminal registers a network slice of another type, the target slice identifier being an identifier of a target network slice allocated for the terminal, and the network slice of another type being different from the type of the network slice requested to be registered by the request information; in a case where the return information is the first type return information, allocating network resources of the target network slice to the terminal, the target network slice being the first type network slice or the second type network slice; and in a case where the return information is the second type return information, transmitting the second type return information to the terminal.

[0006] Optionally, the forwarding the request information to the core network device comprises: determining a type of the request information, wherein the type comprises: first type request information and second type request information; in a case that the request information is the first type request information, forwarding the request information to a core network entity of a terrestrial network in the core network device; in a case that the request information is the second type request information, forwarding the request information to a core network entity of a satellite network in the core network device.

[0007] Optionally, the determining the information type of the request information comprises: obtaining indication information carried by the request information, wherein the indication information at least comprises: a first identifier of a network slice requested by the terminal to register; determining a slice type of the network slice indicated by the first identifier; in a case that the slice type is a first type network slice, determining that the information type of the request information is the first type request information; in a case that the slice type is a second type network slice, determining that the information type of the request information is the second type request information.

[0008] Optionally, the core network device generates the return information by: obtaining indication information carried by the request information, wherein the indication information at least comprises: a first identifier of a network slice requested by the terminal to register, a target service, a subscription slice list corresponding to the terminal, a first position of the terminal, ephemeris information of a target satellite, the target satellite being a satellite corresponding to a satellite network covering the terminal, the ephemeris information at least comprising: a second position of the target satellite, an orbital height of an orbit on which the target satellite runs, the subscription slice list being used to record a second identifier of a network slice allowed to be accessed by the terminal, the target service being a service carried by the network slice requested by the request information to register; in a case that the satellite network does not support the target service, generating first type return information according to the first identifier and the subscription slice list; in a case that the satellite network supports the target service, generating second type return information according to the first position and the ephemeris information.

[0009] Optionally, the generating the first type return information according to the first identifier and the subscription slice list comprises: in a case that the subscription slice list contains a second identifier identical to the first identifier, determining the second identifier as the first type return information.

[0010] Optionally, the generating the second type return information according to the first position and the ephemeris information comprises: determining a moving radius according to the first position and the second position; determining a coverage duration of network resources according to the first position, the second position and the orbital height; and determining the moving radius and the coverage duration as the second type return information.

[0011] Optionally, before the network resources of the target network slice are allocated to the terminal, the method further comprises: receiving a session request sent by the terminal, wherein the session request is used to request to establish a session with the target network slice; forwarding the session request to the core network device; and receiving session request acceptance information returned by the core network device in response to the session request.

[0012] According to another aspect of the embodiments of the present application, a method for allocating resources of a satellite-ground converged network is also provided, comprising: receiving request information forwarded by a wireless base station, wherein the request information is used to request registration of a network slice, and the request information comprises: first type request information used to register a first type network slice, and second type request information used to register a second type network slice, the first type network slice being a network slice of a ground network, and the second type network slice being a network slice of a satellite network; and generating return information in response to the request information, wherein the return information comprises: first type return information containing a target slice identifier, and second type return information indicating that the terminal registers a network slice of another type, the target slice identifier being an identifier of a target network slice allocated to the terminal, and the network slice of another type being different from the type of the network slice requested to be registered by the request information.

[0013] Optionally, the return information generated in response to the request information comprises: obtaining indication information carried by the request information, wherein the indication information at least comprises: a first identifier of the network slice requested to be registered, a target service, a subscription slice list corresponding to the terminal, a first position of the terminal, and ephemeris information of a target satellite, the target satellite being a satellite corresponding to the satellite network covering the terminal, the ephemeris information at least comprising: a second position of the target satellite, and an orbital altitude of an orbit on which the target satellite runs, the subscription slice list being used to record a second identifier of a network slice allowed to be accessed by the terminal, and the target service being a service carried by the network slice requested to be registered by the request information; generating the first type return information according to the first identifier and the subscription slice list in a case where it is determined that the target service is not supported by the satellite network; and generating the second type return information according to the first position and the ephemeris information in a case where it is determined that the target service is supported by the satellite network.

[0014] Optionally, the first type return information is generated according to the first identifier and the subscription slice list, comprising: in a case where the same second identifier as the first identifier exists in the subscription slice list, determining the second identifier as the first type return information.

[0015] Optionally, the second type return information is generated according to the first position and the ephemeris information, comprising: determining a moving radius according to the first position and the second position; determining a coverage duration of network resources according to the first position, the second position, and the orbital altitude; and determining the moving radius and the coverage duration as the second type return information.

[0016] Optionally, in the case where the second type return information is generated, the method further comprises: receiving target request information forwarded by the wireless base station, wherein the target request information is used to request registration of a target satellite network slice, the target satellite network slice being a second type network slice with a coverage range greater than or equal to a range corresponding to the moving radius, and a duration of coverage of the terminal greater than or equal to the coverage duration; and generating return information of the target request information in response to the target request information.

[0017] According to another aspect of the embodiments of the present application, a core network device is also provided, which comprises a network entity of a ground network and a network entity of a satellite network, and is configured to perform the above-mentioned method for allocating resources of a satellite-ground integrated network through the network entity of the ground network or the network entity of the satellite network.

[0018] According to another aspect of the embodiments of the present application, a method for obtaining resources of a satellite-ground integrated network is also provided, which comprises: sending request information to a wireless base station, wherein the request information is used to request registration of a network slice, and the request information comprises first-type request information used to register a first-type network slice and second-type request information used to register a second-type network slice, the first-type network slice is a network slice of a ground network, and the second-type network slice is a network slice of a satellite network; receiving return information transmitted by the wireless base station, wherein the return information comprises first-type return information containing a target slice identifier and second-type return information indicating that the terminal registers a network slice of another type, the target slice identifier is an identifier of a target network slice allocated for the terminal, and the network slice of another type is different from the type of the network slice requested to be registered by the request information; in a case where the first-type return information is received, sending a session request to the wireless base station, wherein the session request is used to request establishment of a session with the target network slice; and in a case where the second-type return information is received, sending target request information to the wireless base station, wherein the target request information is used to request registration of a target satellite network slice, and the target satellite network slice is determined according to the second-type return information.

[0019] According to another aspect of the embodiments of the present application, a communication system of a satellite-ground integrated network is also provided, comprising: a terminal, a radio base station in communication with the terminal, a core network device in communication with the radio base station, wherein the terminal is configured to send request information, wherein the request information is used to request registration of a network slice, and the request information comprises: first type request information used to register a first type network slice, and second type request information used to register a second type network slice, the first type network slice is a network slice of a ground network, and the second type network slice is a network slice of a satellite network; the radio base station is configured to receive the request information and forward the request information to the core network device, wherein the core network device comprises: a core network entity of the ground network and a core network entity of the satellite network; the core network device is configured to generate return information in response to the request information and send the return information to the radio base station, wherein the return information comprises: first type return information containing a target slice identifier, and second type return information indicating that the terminal registers another type network slice, the target slice identifier is an identifier of a target network slice allocated to the terminal, and the another type network slice is different from the type of the network slice requested to be registered by the request information; the radio base station is further configured to, in the case that the return information is the first type return information, allocate network resources of the target network slice to the terminal, the target network slice being the first type network slice or the second type network slice; and the radio base station is further configured to, in the case that the return information is the second type return information, transmit the second type return information to the terminal.

[0020] In the embodiment of the present application, the request information sent by the receiving terminal is adopted, wherein the request information is used to request to register a network slice, and the request information includes: first type request information used to register a first type network slice, and second type request information used to register a second type network slice, the first type network slice is a network slice of a ground network, and the second type network slice is a network slice of a satellite network; the request information is forwarded to a core network device, wherein the core network device includes: a core network entity of the ground network and a core network entity of the satellite network; return information generated by the core network device in response to the request information is received, wherein the return information includes: first type return information containing a target slice identifier, and second type return information indicating that the terminal registers other type network slices, the target slice identifier is an identifier of a target network slice allocated to the terminal, and the other type network slices are different from the type of the network slice requested to be registered by the request information; in the case that the return information is the first type return information, network resources of the target network slice are allocated to the terminal, and the target network slice is the first type network slice or the second type network slice; in the case that the return information is the second type return information, the second type return information is transmitted to the terminal, by providing a network resource allocation method applied to a star-ground fusion network scene, through the enhancement of the terminal, the wireless base station, and the core network slice capability, in the scene of the star-ground fusion network, the ground network slice or the satellite network slice is allocated to the terminal according to the demand of the terminal for the network slice, the technical effect of improving the utilization rate of network resources in the star-ground fusion scene without increasing the interaction signaling and process between the terminal and the network is achieved, and the technical problem of being unable to improve the utilization rate of satellite network resources in the star-ground fusion networking scene is solved. BRIEF DESCRIPTION OF DRAWINGS

[0021] The accompanying drawings, which are included to provide a further understanding of the present application and are incorporated in and constitute a part of this application, illustrate embodiments of the present application and serve to explain the present application, but do not limit the present application. In the drawings:

[0022] Figure 1 is a schematic diagram of a communication system 100 according to an embodiment of the present application;

[0023] Figure 2 is a schematic diagram of a 5G network slice registration process according to the related art;

[0024] Figure 3 is a schematic diagram of a 5G network slice session establishment process according to the related art;

[0025] Figure 4 is a step flowchart of a method for allocating star-ground fusion network resources according to an embodiment of the present application;

[0026] Figure 5 is a schematic diagram of a satellite and a terminal according to an embodiment of the application;

[0027] Figure 6 is a step flow chart of another method for allocating resources of a satellite-terrestrial converged network according to an embodiment of the application;

[0028] Figure 7 is a schematic diagram of a core network device according to an embodiment of the application;

[0029] Figure 8 is a flow chart of a registration network slice according to an embodiment of the application;

[0030] Figure 9 is a flow chart of establishing a session with a network slice according to an embodiment of the application;

[0031] Figure 10 is a step flow chart of a method for acquiring resources of a satellite-terrestrial converged network according to an embodiment of the application;

[0032] Figure 11 is a schematic diagram of a communication system of a satellite-terrestrial converged network according to an embodiment of the application. DETAILED DESCRIPTION

[0033] In order to make the personnel in the art better understand the scheme of the present application, the technical solutions 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 only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative labor should fall within the scope of protection of the present application.

[0034] It should be noted that the terms "first", "second", and the like in the specification and claims of the present application and the above-described drawings are used to distinguish similar objects, and do not necessarily have to describe a specific order or sequence. It should be understood that the data thus used can be interchanged under appropriate circumstances, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusion, for example, a process, method, system, product or device that includes a series of steps or units does not have to be limited to those steps or units clearly listed, but can include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0035] In order to better understand the embodiments of the present application, the technical terms involved in the embodiments of the present application are explained as follows:

[0036] Satellite-terrestrial integration network: a three-dimensional coverage mobile communication network composed of satellite networks (high-orbit satellite networks, medium-low-orbit satellite networks) and terrestrial mobile communication networks, etc. In the satellite-terrestrial integration network, the satellite network and the terrestrial network are complementary and tightly integrated, expanding the network coverage and improving the overall network efficiency.

[0037] Network slicing: dividing a physical network into multiple virtual networks, each virtual network equivalent to a network slice, and the network resources of each virtual network have different bandwidth, delay and reliability to ensure that each virtual network can meet the specific needs of different applications, industries or users to provide the best performance.

[0038] In the related art, terminal devices, wireless base stations and core network entities achieve network entity selection and network resource isolation of traditional ground static networks through slice identification: terminal devices support carrying slice identification to the network, support selecting access to different slices according to applications, support storage and processing of slice-related identification; wireless base stations implement slice-level resource allocation, isolation and processing of intra-slice traffic, support selection of intra-slice core network functions; core network entities complete access control and selection of slices, guide terminal devices (UEs) to access appropriate network slices in combination with the availability of slices, support decision and allocation of slice-related identification of UEs (signed identification, allowed identification, configured identification), and support slice selection policies according to applications. In the application scenario of 5G networks, network slice subnet instances (NSSIs) of 5G network slices represent various network segments within a slice. An NSSI is a combination of network functions and resources, forming an independent part of a slice. Each NSSI provides specific network services and connections for applications or users within a slice. With network slicing, a single physical infrastructure can support multiple use cases simultaneously. For example, one slice may be dedicated to serving mission-critical applications, ensuring low latency and high availability, while another slice may be dedicated to providing enhanced mobile broadband for media streaming or gaming. One of the key advantages of 5G network slicing is the ability to achieve network customization and service differentiation. By customizing the characteristics of each slice, operators can provide specialized services to meet the diverse needs of different industries and applications. With the rapid development of high-throughput satellite communication technology, satellite networks have significantly improved their communication capabilities in terms of speed, latency, reliability, and other aspects, and can complement and cooperate with ground networks, and even replace ground networks in some application scenarios. However, satellite networks also have network characteristics such as strong ground mobility, dynamic network topology, and limited resources, which are not possessed by 5G networks. Therefore, the slicing methods mentioned in current 3rd Generation Partnership Project (3GPP), International Telecommunication Union (ITU) and other standards cannot be directly applied to satellite networks or star-ground integrated networks when providing services to users in satellite and ground network integration scenarios. In order to solve this problem, the present application provides related solutions, which are described in detail below.

[0039] According to an embodiment of the present application, a method for allocating resources of a star-ground integrated network is provided. 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 a logical order is shown in the flowchart, in some cases, the steps shown or described herein can be executed in a different order.

[0040] The technical solutions of the embodiments of the present application can be applied to various communication systems, for example, a Global System of Mobile communication (GSM) system, a Code Division Multiple Access (CDMA) system, a Wideband Code Division Multiple Access (WCDMA) system, a General Packet Radio Service (GPRS), a Long Term Evolution (LTE) system, an LTE Frequency Division Duplex (FDD) system, an LTE Time Division Duplex (TDD), a Universal Mobile Telecommunication System (UMTS), a Worldwide Interoperability for Microwave Access (WiMAX) communication system, or a 5G system, etc.

[0041] For example, the communication system 100 to which the embodiments of the present application are applied is shown in FIG. 1. Figure 1 The communication system 100 can include a network device 110, which can be a device communicating with a terminal device 120 (or a communication terminal, a terminal). The network device 110 can provide communication coverage for a specific geographic area and can communicate with the terminal device located in the coverage area. Optionally, the network device 110 can be a base station (Base Transceiver Station, BTS) in a GSM system or a CDMA system, or a base station (NodeB, NB) in a WCDMA system, or an evolved base station (eNB or eNodeB) in an LTE system, or a radio controller in a cloud radio access network (CRAN), or the network device can be a mobile switching center, a relay station, an access point, a vehicle-mounted device, a wearable device, a hub, a switch, a bridge, a router, a network side device in a 5G network, or a network device in a future evolved public land mobile network (PLMN), etc.

[0042] The communication system 100 further includes at least one terminal device 120 located within the coverage of the network device 110. As used herein, a "terminal device" includes, but is not limited to, an apparatus configured to receive / transmit communication signals via a wired line connection, such as via a Public Switched Telephone Network (PSTN), a Digital Subscriber Line (DSL), a digital cable, a direct cable connection; and / or another data connection / network; and / or a wireless interface, such as for a cellular network, a Wireless Local Area Network (WLAN), a digital television network such as a DVB-H network, a satellite network, an AM-FM broadcast transmitter; and / or another terminal device; and / or an Internet of Things (IoT) device. A terminal device configured to communicate over a wireless interface can be referred to as a "wireless communication terminal", "wireless terminal" or "mobile terminal". Examples of mobile terminals include, but are not limited to, satellite or cellular phones; Personal Communications System (PCS) terminals that can combine a cellular radiotelephone with data processing, facsimile, and data communications capabilities; PDA's that can include a wireless radio telephone, a pager, Internet / Intranet access, Web browser, an organizer, a calendar, and / or a global positioning system (GPS) receiver; and conventional laptop and / or palmtop receivers or other electronic devices that include a radio telephone transceiver. A terminal device can refer to an access terminal, User Equipment (UE), subscriber unit, subscriber station, mobile station, mobile, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device. An access terminal can be a cellular telephone, a cordless telephone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA), a handset with wireless communication capabilities, a computing device, or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5G network, or a terminal device in a future evolved PLMN, etc.

[0043] Optionally, the terminal devices 120 can communicate with each other through Device to Device (D2D) communication.

[0044] Optionally, the 5G system or 5G network can also be referred to as a new radio (NR) system or NR network.

[0045] The 5G network slice has two characteristics of customization and isolation (dedication), wherein the customization refers to deep customization from multiple dimensions such as network performance, network capability, etc. according to the requirements of the terminal, to meet the service quality requirements of the service level agreement (SLA); the dedication refers to that the network slice serves a specific application scenario, and different slices are isolated from each other and do not affect each other. Before the terminal application of the 5G network slice, the terminal needs to register the network slice and establish a session with the network slice, and the entire registration process involves three parts of the terminal, the wireless side and the core network side, wherein the wireless side (such as a wireless network) supports basic functions of the network slice, for example, network slice selection assistance information (NSSAI) reported by the terminal includes two parts, namely slice / service type (SST) for indicating the application scenario of the network slice and slice differentiator (SD) information for distinguishing multiple network slices of the same service type. The wireless side mainly performs network slicing through four modules of basic signaling, service guarantee, quality monitoring and slice management. The core network side supports network slicing, and selects a network entity conforming to the slice configuration to provide services for users in user registration and session business processes. In the business process, the process initiated by the terminal or the network about the slice is identified by single network slice selection assistance information (S-NSSAI) to indicate the related operation of associating the service to a specific slice, and the interaction of the signaling in these processes and the S-NSSAI contained therein as the identifier of the network slice. Figure 2 is a schematic diagram of the registration process of the 5G network slice, as Figure 2As shown, when performing network slice registration, the terminal (UE) sends a registration request to the radio access network (RAN), wherein the registration request contains both parameters sent to the RAN and a registration request sent to the CN, and the RAN parameters can contain a Requested NSSAI (Requested NSSAI) indicating the network slice that the terminal wants to access. Whether to carry and how to carry the Requested NSSAI depends on the value of the Access Stratum Connection Establishment NSSAI Inclusion Mode (the Access Stratum Connection Establishment NSSAI Inclusion Mode) saved in the terminal. In particular, in the case of initial registration or mobile registration update, the registration request also contains the mapping of the Requested NSSAI to ensure that the network can verify whether the S-NSSAI in the Requested NSSAI is allowed to access according to the Subscribed S-NSSAI. If the default NSSAI (Default Configured NSSAI) configured by the system for the terminal is used, the registration request also contains the indication information of the default NSSAI (Default Configured NSSAI Indication). For example, Figure 2As shown, the RAN will receive the registration request and forward it to the core network (CN), and if the RAN parameter contains information for pointing to the core network, the registration request message is forwarded to the core network to which it points; if the RAN parameter does not contain the core network information that can point to the core network, the RAN selects the core network based on the Requested NSSAI, and if the RAN cannot select a suitable AMF, the registration request message is forwarded to the locally configured core network to perform core network selection. The core network (CN) will perform slice-related parameter authorization authentication on the terminal. During authorization authentication, the core network checks the Requested NSSAI according to the obtained subscription slice information (Subscribed S-NSSAI), and if the check is passed, the core network returns information such as network slice information (Allowed NSSAI) that allows the terminal to register to the terminal, to inform the terminal that the multiple network slices indicated by the multiple S-NSSAIs included in the Allowed NSSAI accept the terminal's registration request, and the terminal can use the network resources provided by the multiple network slices indicated by the multiple S-NSSAIs included in the Allowed NSSAI. The core network returns the registration information to the terminal, and also informs the radio access network of all or part of the information of the Allowed NSSAI. The terminal needs to establish a channel for data transmission with the network slice in order to use the resources provided by the network slice, and this channel is called a PDU session. If a PDU session is successfully established, a data transmission channel between the terminal and the network slice is successfully established, Figure 3 is a schematic diagram of a session establishment process of a 5G network slice, as Figure 3 shown, the request for establishing a data transmission channel between the terminal and the network slice is called a PDU session establishment request. The terminal requests the core network (CN) to establish a PDU session via a radio access network (RAN), wherein the UE selects an S-NSSAI from the Allowed NSSAI, the core network determines a session management function (SMF) for establishing a session according to the selected S-NSSAI, the SMF, which is a basic unit in the 5G network service architecture, establishes a PDU session between the terminal and the S-NSSAI. If the PDU session is successfully established, after completing the authorization and resource preparation of the core network, the core network sends a PDU session establishment acceptance message to the terminal, informing the terminal that the PDU session has been successfully established with which network slices, and the core network simultaneously sends a PDU session establishment message containing a data network (DNN) and an S-NSSAI to the radio access network, informing the radio access network which specific networks the terminal connects when establishing a PDU session.

[0046] The embodiment of the present application provides a method for allocating satellite-ground integrated network resources, Figure 4is a step flow chart of a method for allocating resources of a satellite-ground integrated network according to an embodiment of the present application, as shown in Figure 4 The method comprises the following steps:

[0047] In step S402, the request information sent by the terminal is received, wherein the request information is used to request registration of a network slice, and the request information comprises: first type request information used to register a first type network slice, and second type request information used to register a second type network slice, the first type network slice being a network slice of a ground network, and the second type network slice being a network slice of a satellite network.

[0048] The method provided by the embodiments of the present application can be used in a satellite-ground integrated network scenario, and the terminal can apply both resources provided by a ground network and network resources provided by a satellite network; therefore, in step S402, the request message for registering a network slice received by the wireless side (such as a wireless base station) may be a request message (i.e., first type request information) for requesting registration of a ground network slice (i.e., a first type network slice), or a request message (i.e., second type request information) for requesting registration of a satellite ground network slice (i.e., a second type network slice). When the terminal sends the request message, different slice information is carried according to different registration types, for example, if the registration type is initial registration, the terminal carries the requested network slice identifier (Requested NSSAI) based on an existing mechanism; if the registration type is mobility registration, the terminal can carry the identifier of a network slice that has been registered in addition to the Requested NSSAI. The wireless side in the embodiments of the present application includes two types of wireless base stations of a satellite network and a ground network.

[0049] In step S404, the request information is forwarded to a core network device, wherein the core network device comprises: a core network entity of a ground network and a core network entity of a satellite network.

[0050] In step S404, the wireless side receives the request information and forwards it to the core network device. The core network device in the embodiments of the present application includes two types of core network entities, one being a core network entity of a ground network used to provide ground network resources, and the other being a core network entity of a satellite network used to provide satellite network resources, so that the method provided by the embodiments of the present application can be applied to a satellite-ground integrated network.

[0051] Optionally, forwarding the request information to the core network device comprises: determining a type of the request information, wherein the type comprises: first type request information and second type request information; in a case where the request information is the first type request information, forwarding the request information to a core network entity of a ground network in the core network device; in a case where the request information is the second type request information, forwarding the request information to a core network entity of a satellite network in the core network device.

[0052] In the embodiment, the wireless side can select the satellite network entity or the ground network entity for signaling processing based on the slice instance information or the space-time slice information in the existing mechanism; for example, when the wireless side determines that the request information sent by the terminal is request information for requesting a network slice of the ground network (i.e., first type request information), the ground network entity is selected for signaling processing, and the request information sent by the terminal is forwarded to the core network entity of the ground network; when the wireless side determines that the request information sent by the terminal is request information for requesting a network slice of the satellite network (i.e., second type request information), the satellite network entity is selected for signaling processing, and the request information sent by the terminal is also forwarded to the core network entity of the satellite network; in the embodiment, the core network entity of the ground network and the core network entity of the satellite network are both included in the core network device.

[0053] According to an optional embodiment of the application, determining the information type of the request information comprises: obtaining indication information carried by the request information, wherein the indication information at least comprises: a first identifier of a network slice requested by the terminal to register; determining a slice type of the network slice indicated by the first identifier; in a case where the slice type is a first type network slice, determining that the information type of the request information is first type request information; in a case where the slice type is a second type network slice, determining that the information type of the request information is second type request information.

[0054] The request message sent by the terminal carries information (i.e., indication information) related to the network slice to be registered, for example, carries an identifier (i.e., a first identifier) of the network slice to be registered, so that in the above embodiment, before the wireless side determines which core network entity in the core network device to forward the request information to, the indication information carried by the request information can be used to determine which type of network slice the terminal requests to register; for example, the wireless side can locate the network slice indicated by the first identifier according to the first identifier carried in the request information; in a case where the network slice indicated by the first identifier is a network slice of the ground network (i.e., a first type network slice), it can be determined that the request message is first type request information (i.e., request information that needs to be forwarded to the core network entity of the ground network); in a case where the network slice indicated by the first identifier is a network slice of the satellite network (i.e., a second type network slice), it can be determined that the request message is second type request information (i.e., request information that needs to be forwarded to the core network entity of the satellite network).

[0055] In step S406, the core network device receives the request information forwarded by the wireless side (e.g., a wireless base station), and verifies whether the network slice requested by the terminal in the request information is allowed to access the terminal. If so, the core network generates return information (i.e., the first type of return information) containing the identification information of the network slice requested by the terminal (i.e., the target network slice identification). If the network slice requested by the terminal in the request information is not allowed to access the terminal, the core network device can also allocate another network slice in the same network resource to the terminal according to the function to be implemented by the terminal, and send the identification information of the network slice in the same network resource that can carry the function to be implemented by the terminal (i.e., the target network slice identification) to the terminal as the first type of return information. Since the method provided in the embodiments of the present application is applied in a star-satellite converged network, in the embodiments, after receiving the request message, the core network device determines the function to be implemented by the terminal according to the request information. If the core network device judges that the network slice requested by the terminal belongs to a network with a shortage of resources, or there is another type of network that can implement the function to be implemented by the terminal, the core network device generates the second type of return information, which is return information for informing the terminal to register a network slice of a different type (i.e., the other type of network slice) from the network slice requested by the terminal. For example, the network slice requested by the terminal is a network slice of a ground network, and the core network device judges that there is a network slice in a satellite network that can implement the function to be implemented by the terminal, so the core network device generates return information (of the second type) for informing the terminal to register a network slice of the satellite network. In the embodiments, the network slices in the same network are network slices of the same type, and the network slices in different networks are network slices of different types. For example, the network slices of the ground network all belong to the same type of network slice, and the network slices of the ground network and the network slices of the satellite network belong to different types of network slices.

[0056] In step S406, after the core network device receives the request information forwarded by the wireless side (e.g., a wireless base station), it verifies whether the network slice requested by the terminal in the request information is allowed to access the terminal. If so, the core network generates return information (i.e., the first type of return information) containing the identification information of the network slice requested by the terminal (i.e., the target network slice identification). If the network slice requested by the terminal in the request information is not allowed to access the terminal, the core network device can also allocate another network slice in the same network resource to the terminal according to the function to be implemented by the terminal, and send the identification information of the network slice in the same network resource that can carry the function to be implemented by the terminal (i.e., the target network slice identification) to the terminal as the first type of return information. Since the method provided in the embodiments of the present application is applied in a star-satellite converged network, in the embodiments, after receiving the request message, the core network device determines the function to be implemented by the terminal according to the request information. If the core network device judges that the network slice requested by the terminal belongs to a network with a shortage of resources, or there is another type of network that can implement the function to be implemented by the terminal, the core network device generates the second type of return information, which is return information for informing the terminal to register a network slice of a different type (i.e., the other type of network slice) from the network slice requested by the terminal. For example, the network slice requested by the terminal is a network slice of a ground network, and the core network device judges that there is a network slice in a satellite network that can implement the function to be implemented by the terminal, so the core network device generates return information (of the second type) for informing the terminal to register a network slice of the satellite network. In the embodiments, the network slices in the same network are network slices of the same type, and the network slices in different networks are network slices of different types. For example, the network slices of the ground network all belong to the same type of network slice, and the network slices of the ground network and the network slices of the satellite network belong to different types of network slices.

[0057] Optionally, the core network device generates the return information by: obtaining indication information carried in the request information, wherein the indication information at least includes: a first identifier of a network slice requested to be registered, a target service, a subscription slice list corresponding to the terminal, a first location of the terminal, and ephemeris information of a target satellite, the target satellite being a satellite corresponding to a satellite network covering the terminal, the ephemeris information at least including: a second location of the target satellite and an orbital height of an orbit in which the target satellite runs, the subscription slice list being used to record a second identifier of a network slice allowed to be accessed by the terminal, and the target service being a service carried by the network slice requested to be registered by the request information; in a case where it is determined that the satellite network does not support the target service, generating first type return information according to the first identifier and the subscription slice list; and in a case where it is determined that the satellite network supports the target service, generating second type return information according to the first location and the ephemeris information.

[0058] As mentioned in the above embodiment, after the wireless side forwards the request information to the core network device, the core network device generates corresponding return information. Specifically, in this embodiment, the core network device first determines the type of the network slice that the terminal wants to register based on the information (i.e., indication information) about the network slice that the terminal wants to register carried in the request message. Since the method provided in the embodiments of the present application can be applied in the scenario of a star-ground integrated network, the terminal can apply the network resources of the satellite network or request to apply the network resources of the ground network. Therefore, in addition to the identification (i.e., first identification, Requested NSSAI) of the network slice that the terminal requests to register, the subscription slice list (Subscribed S-NSSAI) recording the identification (i.e., second identification) of the network slice that allows the terminal to access, and the service (i.e., target service) that the terminal wants to implement when registering the network slice, the indication information carried in the request information further includes the location (i.e., first location) of the terminal, satellite beam / wave position / ephemeris information, etc. The location of the terminal can be the longitude and latitude of the terminal, and the satellite beam / wave position / ephemeris information can be the beam / wave position / ephemeris information of the satellite (i.e., target satellite) to which the satellite network covering the terminal belongs. The ephemeris information of the target satellite records the location (i.e., second location) of the target satellite, for example, the longitude and latitude of the target satellite, the orbit of the target satellite, and the altitude of the orbit of the target satellite. If the terminal requests to register the network slice of the ground network, the core network device first determines whether the satellite network can carry the target service. If the satellite network can carry the target service, the core network device calculates the allowed slice instance that can be allocated and its available geographical range (such as radius) and time range (such as time length) based on the location information (first location) carried by the terminal when registering and the satellite beam / wave position / ephemeris information, and generates a second type of return information indicating that the terminal registers the satellite network, wherein the second type of return information can carry relevant information indicating the spatio-temporal slice (i.e., satellite network slice) that the terminal registers, for example, the coverage range and coverage time length of the satellite network slice. If the target service that the terminal requests the ground network to implement is not supported by the satellite network, the terminal is authenticated according to the first identification (Requested NSSAI) and the subscription slice list (Subscribed S-NSSAI), and after the authentication is passed, a first type of return information is generated, wherein the first type of return information carries the identification of the network slice of the ground network that allows the terminal to access and can implement the target service, which can be different from the first identification.

[0059] According to an optional embodiment of the present application, generating the first type of return information according to the first identification and the subscription slice list includes: in the case that the second identification in the subscription slice list is the same as the first identification, determining the second identification as the first type of return information.

[0060] As mentioned in the above embodiments, the core network device authenticates according to the first identifier (Requested NSSAI) and the subscription slice list (Subscribed S-NSSAI), specifically, the core network device traverses all network slice identifiers (i.e. the second identifier) contained in the subscription slice list (Subscribed S-NSSAI), and if there is an identifier (i.e. the first identifier) of the network slice requested by the terminal, it is determined that the terminal can access the network slice it requests, at this time, the second identifier (which can also be the first identifier because the second identifier is the same as the first identifier at this time) is contained in the first type of return information and returned to the terminal, informing the terminal that the registration is successful.

[0061] According to another optional embodiment of the present application, the second type of return information is generated according to the first position and the ephemeris information, including: determining a moving radius according to the first position and the second position; determining a coverage duration of the network resource according to the first position, the second position and the orbital height; and determining the moving radius coverage duration as the second type of return information.

[0062] As mentioned in the above embodiments, the core network device can calculate the allowed-to-use slice instance and its available geographical range (such as radius) and time range (such as duration) that can be allocated based on the position information (first position) carried by the terminal registration and the satellite beam / wave position / ephemeris information, specifically, in the present embodiment, the terminal is assumed to be located on the earth, and the core network device can calculate the allowed-to-use slice instance and its available geographical range (such as radius) and time range (such as duration) that can be allocated according to the formula: R = R e sinα and determining the radius R of the target satellite coverage area, wherein R represents the moving radius of the target satellite, R e represents the radius of the earth, α is the angle of the geocentric angle formed between the current position (i.e. the second position) of the target satellite and the earth, sinα is the sine value of α, and arccos(A) represents the tangent value of A, in the present embodiment, is the latitude of the terminal, λ1 is the longitude of the terminal, and λ1 are recorded as the position (i.e. the first position) of the terminal, is the current latitude of the target satellite, λ2 is the current longitude of the target satellite, and λ2 are recorded as the position (i.e. the second position) of the target satellite, and the coverage range of the satellite can be further determined according to the radius; at the same time, the core network device also determines the coverage duration (t) of the satellite network resource provided by the target satellite to the terminal according to the formula: wherein α is the angle of the geocentric angle formed between the current position (i.e. the second position) of the target satellite and the earth, and ω is the angular velocity of the earth rotation, wherein π ≈ 3.14, and T is the period of the earth rotation, h is the orbital altitude of the target satellite, G is the acceleration of gravity, and M is the mass of the Earth. The moving radius (R) and the coverage duration (t) obtained according to the above method are recorded in the second type of return information, and the terminal is informed to request to register a satellite network slice that satisfies the moving radius greater than or equal to the moving radius (R) and the duration of covering the terminal greater than or equal to the coverage duration (t), wherein the coverage duration (t) represents the duration of time during which the satellite network can provide network resources for the terminal. Figure 5 is a schematic diagram of the positions of the satellite and the terminal, as Figure 5 indicated, a plurality of satellites can be covered above the terminal, and therefore, different satellite network slices can be allocated to different terminals by the method provided in the embodiments of the present application, or the same terminal can be switched to different satellite network slices according to its position after movement; for example Figure 5 In the example, the terminal A, the terminal B, and the terminal C are respectively located in different satellite coverage areas, and there is an overlap of coverage, and the core network device allocates reasonable (coverage duration + coverage range + slice instance) information to the terminal based on the positions of the terminal A, the terminal B, and the terminal C. Taking the terminal B as an example, based on the user registration request, the core network obtains the slice instance according to the subscription information (Subscribed S-NSSAI) of the terminal, calculates the geographical range (such as the moving radius R) that can be used by different slice instances based on the reported position information (i.e., the first position), and calculates the time range (such as the coverage duration) that can be used by different slice instances based on the ephemeris information; the core network sends the spatio-temporal slice information to the terminal, which is used for the use of slice information in subsequent service initiation. When the terminal initiates a service request, the corresponding spatio-temporal slice information is carried, and the satellite-borne wireless base station (the wireless base station of the satellite network) selects the satellite-borne mobility management network element or the ground mobility management network element based on the spatio-temporal slice information; the satellite-borne mobility management network element or the ground mobility management network element selects the session management network element based on the spatio-temporal slice information; and the core network completes the establishment of the PDU session and the selection of the routing according to the spatio-temporal slice information. In the above example, the satellite-borne wireless side corresponds to the wireless side, and is used to support dynamic adjustment of resources to provide corresponding services for the current terminal based on the spatio-temporal slice information, and to select the satellite-borne or ground network entity. The terminal side supports storage, identification, and use of appropriate spatio-temporal slice (i.e., the second type of network slice) information in the service process.

[0063] In step S408, the network resources of the target network slice are allocated to the terminal, and the target network slice is the first type of network slice or the second type of network slice.

[0064] In step S408, if the return information received by the wireless side is the return information containing the network slice identifier (i.e., the first type of return information), the resource provided by the network slice indicated by the slice identifier (i.e., the target slice identifier) in the first type of return information is allocated to the terminal, wherein the type of the network slice indicated by the target slice identifier can be the network slice of the ground network (i.e., the first type of network slice) or the network slice of the satellite network (i.e., the second type of network slice).

[0065] Optionally, before the network resource of the target network slice is allocated to the terminal, the method further includes: receiving a session request sent by the terminal, wherein the session request is used to request to establish a session with the target network slice; forwarding the session request to the core network device; receiving session request acceptance information returned by the core network device in response to the session request.

[0066] When the first type of return message is forwarded by the wireless side to the terminal, it indicates that the terminal has successfully registered the network slice, and then the terminal further requests to establish a PDU session with the network slice (i.e., the target network slice) that has completed registration. In this embodiment, when the wireless side receives the session request sent by the terminal for establishing a PDU session, it forwards the session request to the core network device, and receives the return information generated by the core network device in response to the session request. For example, the core network device determines that the terminal can establish a PDU session with the target network slice after verification, and then returns the session request acceptance information to the terminal via the wireless side after successfully establishing the session between the terminal and the target network slice.

[0067] In step S410, the second type of return information is transmitted to the terminal when the return information is the second type of return information.

[0068] In step S410, if the wireless side receives the return information indicating that the terminal registers the other type of network slice (i.e., the second type of return information), the terminal side forwards the return information to the terminal.

[0069] Through the above steps, based on the characteristics of the star-ground integrated network, such as adjustable communication resources, high mobility, dynamic network topology, etc., the star-ground integrated network can flexibly select the satellite (satellite network) or the ground network, dynamically adjust the resources to provide corresponding services for the current terminal, and select the satellite or ground network entity.

[0070] Figure 6 is a step flow chart of another method for allocating resources of a star-ground integrated network according to an embodiment of the present application, as shown in Figure 6 The method includes the following steps:

[0071] In step S602, the core network device receives the request information forwarded by the wireless base station, wherein the request information is used to request registration of a network slice, and the request information includes: first type request information used to register a first type network slice, and second type request information used to register a second type network slice, the first type network slice is a network slice of a ground network, and the second type network slice is a network slice of a satellite network.

[0072] In the whole process of allocating network resources of the satellite-ground convergence network, the core network device is responsible for configuring available network slices for the terminal, the available network slices including: a network slice of a ground network (i.e., a first type network slice) capable of supporting a service requested by the terminal and a network slice of a satellite network (i.e., a second type network slice), and specifically, whether to configure the first type network slice or the second type network slice is determined according to the request information sent by the terminal, therefore, in step S602, the core network device first receives the request information sent by the terminal, and the request information is forwarded via the wireless side, wherein the request information can be a request message (i.e., first type request information) used to request registration of a ground network slice (i.e., a first type network slice), or can be a request message (i.e., second type request information) used to request registration of a satellite ground network slice (i.e., a second type network slice).

[0073] In step S604, return information is generated in response to the request information, wherein the return information includes: first type return information containing a target slice identifier, and second type return information indicating that the terminal registers a network slice of another type, the target slice identifier is an identifier of a target network slice allocated for the terminal, and the network slice of another type is different from the type of the network slice requested by the request information.

[0074] In step S604, after the core network device receives the request information forwarded by the wireless side, the core network device generates corresponding return information. Specifically, the request information carries the identity (i.e., the first identity, Requested NSSAI) of the network slice to be registered. The core network device determines whether the network slice indicated by the first identity allows access to the core network for authentication. If the network slice is allowed, the core network device generates return information (i.e., the first type of return information) indicating that the registration is successful. The first type of return information carries the identity (i.e., the target network slice identity) of the network slice registered successfully. If the network slice is not allowed, the core network device matches other network slices for the terminal in the network to which the network slice indicated by the first identity belongs according to the service to be implemented by the terminal, and registers the terminal with the other network slices. After the registration is successful, the core network device generates the first type of return message. For example, the network slice indicated by the first identity is a network slice of a terrestrial network, and the other network slice is also a network slice of a terrestrial network. In addition, when the core network device receives the (first type) request message requesting to register the network slice of the terrestrial network, the core network device first determines whether the satellite network can carry the service to be implemented by the terminal requesting to register the network slice. If it is determined that the satellite network can also carry the service to be implemented by the terminal requesting to register the network slice, the core network device generates return information (i.e., the second type of return information) indicating the network slice of the satellite network (i.e., the other type of network slice) requested by the terminal.

[0075] Optionally, the return information generated in response to the request information includes: obtaining the indication information carried in the request information, wherein the indication information at least includes: the first identity of the network slice to be registered, the target service, the subscription slice list corresponding to the terminal, the first position of the terminal, and ephemeris information of a target satellite, the target satellite being a satellite corresponding to a satellite network covering the terminal, the ephemeris information at least including: a second position of the target satellite and an orbital height of an orbit on which the target satellite runs, the subscription slice list being used to record the second identity of the network slice allowed to be accessed by the terminal, and the target service being a service carried by the network slice requested to be registered by the request information; in a case where it is determined that the satellite network does not support the target service, generating the first type of return information according to the first identity and the subscription slice list; and in a case where it is determined that the satellite network supports the target service, generating the second type of return information according to the first position and the ephemeris information.

[0076] In the embodiment, the core network device generates the response information (i.e. return information) of the request information by the following method. The core network device first determines the type of the network slice that the terminal wants to register based on the information (i.e. indication information) about the network slice that the terminal wants to register carried by the request message. Since the method provided in the embodiment can be applied in the scenario of star-ground fusion network, the terminal can apply the network resources of the satellite network or request to apply the network resources of the ground network. Therefore, in addition to the identification (i.e. first identification, Requested NSSAI) of the network slice that the terminal requests to register, the service (i.e. target service) that the terminal wants to implement when registering the network slice, and the subscription slice list (i.e. second identification, Subscribed S-NSSAI) recording the identification of the network slice that the terminal is allowed to access, the indication information carried by the request information further includes the position (i.e. first position) of the terminal, satellite beam / wave position / ephemeris information, etc. The position of the terminal can be the longitude and latitude of the terminal, and the satellite beam / wave position / ephemeris information can be the beam / wave position / ephemeris information of the satellite (i.e. target satellite) to which the satellite network covering the terminal belongs. The ephemeris information of the target satellite records the position (i.e. second position) of the target satellite, for example, the longitude and latitude of the target satellite, the orbit of the target satellite, and the altitude of the orbit of the target satellite. If the terminal requests to register the network slice of the ground network, the core network device first determines whether the satellite network can carry the service (i.e. target service) that the terminal wants to implement when registering the network slice. If the satellite network can carry the target service, the core network device calculates the allowed slice instance that can be allocated and its available geographical range (such as radius) and time range (such as time length) based on the position information (first position) carried by the terminal registration and the satellite beam / wave position / ephemeris information, and generates the second type of return information indicating the terminal to register the satellite network. The second type of return information can carry the related information of the space-time slice (i.e. satellite network slice) indicating the terminal registration, for example, the coverage range and coverage time length of the satellite network slice. If the target service that the terminal requests the ground network to implement is not supported by the satellite network, the first type of return information is generated after authentication according to the first identification (Requested NSSAI) and the subscription slice list (Subscribed S-NSSAI). The first type of return information carries the identification of the network slice of the ground network that allows the terminal to access and can implement the target service. The identification can be different from the first identification.

[0077] According to an optional embodiment of the present application, the first type of return information is generated according to the first identification and the subscription slice list, including: in the case that the second identification in the subscription slice list is the same as the first identification, the second identification is determined as the first type of return information.

[0078] As mentioned in the above embodiments, the core network device authenticates according to the first identifier (Requested NSSAI) and the subscription slice list (Subscribed S-NSSAI), specifically, the core network device traverses all network slice identifiers (i.e. the second identifier) contained in the subscription slice list (Subscribed S-NSSAI), and if there is an identifier (i.e. the first identifier) of the network slice requested by the terminal, it is determined that the terminal can access the network slice it requests, at this time, the second identifier (which can also be the first identifier because the second identifier is the same as the first identifier at this time) is contained in the first type of return information and returned to the terminal, informing the terminal that the registration is successful.

[0079] According to another optional embodiment of the present application, the second type of return information is generated according to the first position and ephemeris information, including: determining a moving radius according to the first position and the second position; determining a coverage duration of the network resource according to the first position, the second position and the orbital height; determining the moving radius and the coverage duration as the second type of return information.

[0080] As mentioned in the above embodiments, the core network device can calculate the allowed-to-use slice instance and its available geographical range (such as radius) and time range (such as duration) that can be allocated based on the position information (first position) carried by the terminal registration and satellite beam / wave position / ephemeris information, specifically, in the present embodiment, the terminal is assumed to be located on the earth, and the core network device can calculate the moving radius R of the target satellite according to the formula: R = R e sinα and determines the radius R of the coverage area of the target satellite, where R represents the moving radius of the target satellite, R e represents the radius of the earth, α is the angle of the central angle formed between the current position (i.e. the second position) of the target satellite and the earth, sinα is the sine value of α, and arccos(A) represents the tangent value of A, in the present embodiment, is the latitude of the terminal, λ1 is the longitude of the terminal, and λ1 are recorded as the position (i.e. the first position) of the terminal, is the current latitude of the target satellite, λ2 is the current longitude of the target satellite, and λ2 are recorded as the position (i.e. the second position) of the target satellite, and the coverage range of the satellite can be further determined according to the radius; at the same time, the core network device also determines the coverage duration (t) of the satellite network resource provided by the target satellite to the terminal according to the formula: wherein α is the angle of the central angle formed between the current position (i.e. the second position) of the target satellite and the earth, and ω is the angular velocity of the earth rotation, wherein π ≈ 3.14, and T is the period of the earth rotation, h is the orbit distance from the ground height (i.e. the orbit height) of the target satellite, G is the acceleration of gravity, and M is the mass of the earth. The moving radius (R) and the coverage duration (t) obtained according to the above method are recorded in the second type of return information, and the terminal is informed to request to register a satellite network slice that satisfies the moving radius greater than or equal to the moving radius (R) and the duration of covering the terminal greater than or equal to the coverage duration (t), wherein the coverage duration (t) represents the duration that the satellite network can provide network resources for the terminal.

[0081] According to some optional embodiments of the present application, in the case of generating the second type of return information, further comprising: receiving the target request information forwarded by the wireless base station, wherein the target request information is used to request to register a target satellite network slice, and the target satellite network slice is a second type of network slice with a coverage range greater than or equal to the range corresponding to the moving radius and a duration of covering the terminal greater than or equal to the coverage duration; and in response to the target request information, generating return information of the target request information.

[0082] If the terminal receives the second type of return information, it will again send request information (i.e. target request information) for requesting to register a target satellite network slice, wherein the target satellite network slice is a second type of network slice with a coverage range greater than or equal to the coverage range corresponding to the moving radius (R) carried in the second type of return information and a duration of covering the terminal greater than or equal to the coverage duration (t) carried in the second type of return information; in this embodiment, after the core network device receives the target request information sent by the terminal, it will again perform authentication, and generate corresponding return information according to the authentication result, for example, if the authentication is passed, it means that the terminal can access the target satellite network slice, then the core network device will generate return information informing the terminal that the registration is successful after registering the terminal; otherwise, if the target satellite network slice does not allow the terminal to access, and there is no network slice in the ground-satellite integrated network that can carry the business it wants to implement, return information informing the terminal that the registration fails is generated.

[0083] Through the above steps, in the case that the ground network resources are tight or unavailable, the core network device can select the satellite network to serve the terminal, configure the slice available geographic range based on the current position information of the terminal, and configure the slice available time range based on the satellite beam / position, ephemeris information; the terminal is issued with the spatio-temporal slice information composed of "the identifier of the network slice requested to register + slice available geographic range information + slice available time range information", which is used for subsequent business processes; supporting selecting the spaceborne network entity or the ground network entity to carry the business based on the spatio-temporal slice information; supporting adjusting the business based on the spatio-temporal slice information.

[0084] Figure 7 is a schematic diagram of a core network device according to an embodiment of the present application, asFigure 7 As shown, the core network device includes: a network entity 70 of a ground network, a network entity 72 of a satellite network, and the core network device is configured to perform the above-mentioned method of allocating satellite-ground fusion network resources through the network entity 70 of the ground network or the network entity 72 of the satellite network.

[0085] The scheme provided by the embodiments of the present application is based on a network slicing method in a satellite-ground fusion scenario, and involves the enhancement of the functions of terminals, wireless sides, and core network devices, and the optimization of interactive processes. Through the enhancement of the slicing capabilities of terminals, wireless sides, and core network devices, dynamic and efficient resource utilization can be realized end to end in the satellite-ground fusion network, and corresponding resource guarantees can be provided for various service requirements; at the same time, without increasing the interactive signaling and processes between terminals and networks, efficient utilization and flexible deployment of network resources in the satellite-ground fusion scenario are realized.

[0086] Figure 8 is a registration network slicing process diagram, such as Figure 8As shown, the core network device completes the registration of the network slice through interaction with the terminal and the wireless side, wherein the steps of registering the network slice are as follows: Step 0: The terminal performs a network selection process based on an existing mechanism: selecting whether to request access to a ground network or a satellite network; Step 1: The terminal can optionally carry relevant information of the network slice (such as the identity of the requested network slice Requested NSSAI, the subscribed slice list Subscribed S-NSSAI, etc.); Step 2: The wireless side can select a spaceborne network entity or a ground network entity for signaling processing based on slice instance information or space-time slice information in the existing mechanism, for example, when a network slice of a ground network is requested to be registered, the ground wireless initiates a registration process to the core network based on the slice information carried by the request information, wherein the existing slice instance information only contains the identity of the network slice to be registered, and the space-time slice information contains: the identity of the network slice to be registered + the available geographic range of the network slice + the available time length of the network slice; Step 3, including 3a: The core network determines whether to use a satellite network to carry the business it wants to implement according to the configuration (such as business scheduling rules, network load conditions, network slice subscription information of the terminal, etc.); 3b: If the satellite network can be used to carry the business, determine the satellite network slice instance that can carry the business it wants to implement and the area (moving radius) and coverage time length of the satellite network slice covering the terminal according to the terminal's current location (such as the terminal's latitude and longitude, the latitude and longitude of the communication cell to which the terminal belongs) carried in the request information, satellite beam / wave position / ephemeris information; 3c: If the satellite network cannot carry the business it wants to implement, perform authentication according to the Requested NSSAI and the subscribed slice list Subscribed S-NSSAI in the request information, and allocate the available network slice of the ground network to the terminal; After the core network device completes the allocation of the network slice, Step 4 is performed: If the terminal does not need to switch the satellite network, a first type of return information is sent to the terminal, the first type of return information indicating that the registration is successful and carrying the identity of the registered network slice; If the terminal needs to switch the satellite network, a second type of return information is returned, the second type of return information indicating that the terminal performs subsequent signaling and business processes through the satellite, and the second type of return information carrying space-time slice information is sent to the terminal, indicating that the terminal registers the satellite network slice indicated by the space-time slice information.When the terminal receives the second type of return information, step 5 is performed: the terminal requests slice registration from the satellite network (i.e., sends target request information to the satellite network), and carries the space-time slice information carried in the second type of return information; step 6: the wireless side includes a ground wireless base station and a satellite wireless base station, and since the terminal requests slice registration from the satellite network this time, the satellite wireless base station in the wireless side receives and processes the target request information; the satellite wireless base station forwards the target request information to the core network device, and the core network device can parse the space-time slice information based on the upper layer message to determine whether the satellite network can provide subsequent services for the terminal, and complete the subsequent registration process based on the space-time slice.

[0087] Figure 9 is a flowchart of establishing a session with a network slice, as shown in Figure 9 The core network device establishes a session with a network slice through interaction with the terminal and the wireless side, and the steps of establishing a session with a network slice are as follows: step 1: the terminal initiates a session request, carrying space-time slice information; step 2a: when the terminal requests to establish a session with a certain network slice in the satellite network, the satellite wireless base station of the wireless side receives the session request, and can determine whether to provide dynamic resource adjustment for the terminal based on the space-time slice information reported by the terminal and the current resource situation; and forwards the session request carrying the space-time slice information to the core network device; step 2b: the session request carries the space-time slice information, and selects the satellite network or the ground network for subsequent signaling processing; step 3: the core network device selects the satellite network entity or the ground network contained in the terminal space-time slice information to establish entity bearer, and determines whether dynamic adjustment is needed; step 4: the core network device completes the session establishment, returns a session request acceptance message to the satellite wireless, carrying the confirmed space-time slice information; step 5a: the satellite wireless performs corresponding resource allocation based on the space-time slice information and the resource allocation result in step 2a, and step 5b: forwards the session request acceptance information to the terminal to inform the terminal that the session has been successfully established.

[0088] Figure 10 is a step flowchart of a method for acquiring resources of a satellite-ground integrated network according to an embodiment of the present application, as shown in Figure 10 The method comprises the following steps:

[0089] Step S1002, sending request information to a wireless base station, wherein the request information is used to request registration of a network slice, and the request information comprises: first type of request information used to register a first type of network slice, and second type of request information used to register a second type of network slice, the first type of network slice is a network slice of a ground network, and the second type of network slice is a network slice of a satellite network.

[0090] In step S1002, the terminal sends request information for requesting registration of a network slice to the wireless side (such as a wireless base station). Since the method provided in the embodiments of the present application is applied to a star-ground converged network, the terminal can request registration of a satellite network slice (i.e., a second type of network slice) or a ground network slice (i.e., a first type of network slice). If the (first type) request information for requesting registration of a ground network slice is sent, the request information is received and processed by a ground wireless base station of the wireless side, and a core network entity of a core network of a ground network included in the core network device performs a registration process of the network slice. If the (second type) request information for requesting registration of a satellite network slice is sent, the request information is received and processed by a spaceborne wireless base station of the wireless side, and a core network entity of a satellite network included in the core network device performs a registration process of the network slice.

[0091] In step S1004, the terminal receives return information transmitted by the wireless base station. The return information includes first type return information including a target slice identifier and second type return information indicating that the terminal registers another type of network slice. The target slice identifier is an identifier of a target network slice allocated to the terminal. The other type of network slice is different from the type of the network slice requested by the request information.

[0092] After the core network device completes the registration process, the core network device returns information to the terminal via the wireless base station. In step S1004, the terminal receives the return information forwarded by the wireless base station. The terminal can receive information (i.e., first type return information) indicating a successful registration, which carries an identifier of a successfully registered network slice (i.e., a target network slice identifier). Alternatively, the terminal can receive information (i.e., second type return information) indicating that the terminal needs to be requalified. The second type return information indicates that the terminal requests registration of another type of network slice different from the type of the network slice requested by the terminal in the last time. For example, the last time the terminal requested registration of a ground network slice, and the other type of network slice is a satellite network slice.

[0093] In step S1006, in a case where the first type return information is received, the terminal sends a session request to the wireless base station, where the session request is used to request establishment of a session with the target network slice. In a case where the second type return information is received, the terminal sends target request information to the wireless base station, where the target request information is used to request registration of a target satellite network slice determined according to the second type return information.

[0094] In step S1006, if the terminal receives return information indicating successful registration (i.e., first type of return information), the terminal sends a session establishment request to the wireless base station, the session establishment request carrying the identifier of the successfully registered network slice (i.e., target network slice identifier); if the terminal receives return information indicating redirection (i.e., second type of return information), the terminal again sends request information (i.e., target request information) for requesting registration of a target satellite network slice, wherein the satellite network slice requested by the terminal for registration is determined according to the space-time slice information (identifier of the network slice requested for registration + slice available geographic range information + slice available time range information) carried in the second type of return information.

[0095] Through the above steps, the capability of the network slice can be improved in the early stage of dynamic time-efficient networking with limited resources, and satellite resources can be efficiently utilized.

[0096] Figure 11 is a schematic diagram of a communication system of a satellite-ground integrated network provided by an embodiment of the present application, as shown in Figure 11 The communication system of the satellite-ground integrated network includes a terminal 1102, a wireless base station 1104 in communication with the terminal, and a core network device 1106 in communication with the wireless base station, wherein the terminal 1102 is configured to send request information, wherein the request information is used to request registration of a network slice, and the request information includes first type of request information for registering a first type of network slice and second type of request information for registering a second type of network slice, the first type of network slice is a network slice of a ground network, and the second type of network slice is a network slice of a satellite network; the wireless base station 1104 is configured to receive the request information and forward the request information to the core network device 1106, wherein the core network device 1106 includes a core network entity 1108 of the ground network and a core network entity 1110 of the satellite network; the core network device 1106 is configured to generate return information in response to the request information and send the return information to the wireless base station 1104, wherein the return information includes first type of return information containing a target slice identifier and second type of return information indicating that the terminal registers a network slice of another type, the target slice identifier is an identifier of a target network slice allocated to the terminal, and the network slice of another type is different from the network slice requested to be registered by the request information; the wireless base station 1104 includes a wireless base station of the ground network and a wireless base station of the satellite network, and is further configured to, in a case where the return information is the first type of return information, allocate network resources of the target network slice to the terminal 1102, the target network slice being the first type of network slice or the second type of network slice; and the wireless base station 1104 is further configured to, in a case where the return information is the second type of return information, transmit the second type of return information to the terminal 1102.

[0097] The communication system of the star-ground fusion network provided by the embodiments of the present application is applied in a star-ground fusion network scenario, and relates to a terminal side (including a terminal 1102), a wireless side (including a wireless base station 1104), and a core network side (including a core network device 1106). The core network device 1106 can configure a network slice available geographic range according to current location information of the terminal 1102. For example, the geographic range can be based on the location of the terminal 1102, satellite coverage, and operation, and is configured as a current moving radius of the terminal. Meanwhile, the network slice available time range can be configured based on a satellite beam / position, and ephemeris information. The time-space slice information composed of a slice identifier, slice available geographic range information, and slice available time range information is supported to be issued, and is used for subsequent business processes. The spaceborne or ground network entity carrying service based on the time-space slice information is supported. The service is adjusted based on the time-space slice information. The wireless side supports dynamic adjustment of resources based on the time-space slice information, provides corresponding services for the current terminal, and selects the spaceborne or ground network entity. The terminal side supports storage, identification, and use of suitable time-space slice information in the business process.

[0098] The above sequence numbers of the embodiments of the present application are only for description, and do not represent the advantages or disadvantages of the embodiments.

[0099] In the above embodiments of the present application, the description of each embodiment has its own emphasis, and the parts not described in detail in a certain embodiment can be referred to the related description of other embodiments.

[0100] In the several embodiments of 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 coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interface, unit or module, and can be electrical or other forms.

[0101] 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 multiple units. Part or all of the units can be selected according to actual needs to achieve the purpose of the embodiments of the present application.

[0102] In addition, each function unit in each embodiment of the present application can be integrated in one processing unit, or each unit can be physically present separately, or two or more units can be integrated in one unit. The integrated unit can be realized in the form of hardware or in the form of a software function unit.

[0103] When the integrated unit is realized in the form of a software function unit and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present application or the part that essentially contributes to the related 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 each embodiment of the present application. The foregoing storage medium includes a U disk, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk, and various media that can store program codes.

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

Claims

1. A method for allocating resources of a satellite-terrestrial converged network, characterized in that, The method comprises the following steps: receiving request information sent by a terminal, wherein the request information is used for requesting to register a network slice, and the request information comprises first type request information used for registering a first type network slice and second type request information used for registering a second type network slice, the first type network slice is a network slice of a ground network, and the second type network slice is a network slice of a satellite network; forwarding the request information to a core network device, wherein the core network device comprises a core network entity of the ground network and a core network entity of the satellite network; receiving return information generated by the core network device in response to the request information, wherein the return information comprises first type return information containing a target slice identifier and second type return information indicating that the terminal registers a network slice of another type, the target slice identifier is an identifier of a target network slice allocated to the terminal, and the network slice of another type is different from the type of the network slice requested to be registered by the request information; in a case where the return information is the first type return information, allocating network resources of the target network slice to the terminal, the target network slice being the first type network slice or the second type network slice; in a case where the return information is the second type return information, transmitting the second type return information to the terminal.

2. The method of claim 1, wherein, The method comprises the following steps: determining a type of the request information, wherein the type comprises the first type request information and the second type request information; in a case where the request information is the first type request information, forwarding the request information to a core network entity of a ground network in the core network device; in a case where the request information is the second type request information, forwarding the request information to a core network entity of a satellite network in the core network device.

3. The method of claim 2, wherein, The method comprises the following steps: acquiring indication information carried by the request information, wherein the indication information at least comprises a first identifier of a network slice requested to be registered by the terminal; determining a slice type of the network slice indicated by the first identifier; in a case where the slice type is the first type network slice, determining that the information type of the request information is the first type request information; in a case where the slice type is the second type network slice, determining that the information type of the request information is the second type request information.

4. The method of claim 1, wherein, The core network device generates the return information by the following method: obtaining indication information carried by the request information, wherein the indication information at least includes: a first identifier of a network slice requested to be registered, a target service, a subscription slice list corresponding to the terminal, a first location of the terminal, ephemeris information of a target satellite, the target satellite being a satellite corresponding to a satellite network covering the terminal, the ephemeris information at least including: a second location of the target satellite, an orbital height of an orbit in which the target satellite runs, the subscription slice list being used to record a second identifier of a network slice allowed to be accessed by the terminal, and the target service being a service carried by a network slice requested to be registered by the request information; in a case where the terminal requests to register the first type of network slice, and in a case where it is determined that the satellite network does not support the target service, generating the first type of return information according to the first identifier and the subscription slice list; in a case where the terminal requests to register the first type of network slice, and in a case where it is determined that the satellite network supports the target service, generating the second type of return information according to the first location and the ephemeris information.

5. The method of claim 4, wherein, generating the first type of return information according to the first identifier and the subscription slice list, comprising: in a case where the same second identifier as the first identifier exists in the subscription slice list, determining the second identifier as the first type of return information.

6. The method of claim 4, wherein, generating the second type of return information according to the first location and the ephemeris information, comprising: determining a moving radius according to the first location and the second location; determining a coverage duration of network resources according to the first location, the second location and the orbital height; determining the moving radius and the coverage duration as the second type of return information.

7. The method of claim 1, wherein, before allocating network resources of the target network slice to the terminal, the method further comprising: receiving a session request sent by the terminal, wherein the session request is used to request to establish a session with the target network slice; forwarding the session request to the core network device; receiving session request acceptance information returned by the core network device in response to the session request.

8. A method for allocating resources of a space-earth converged network, characterized in that, comprising: a core network device receiving request information forwarded by a radio base station, wherein the core network device includes: a core network entity of a ground network and a core network entity of a satellite network, the request information is used to request to register a network slice, the request information includes: first type of request information used to register a first type of network slice, and second type of request information used to register a second type of network slice, the first type of network slice being a network slice of a ground network, and the second type of network slice being a network slice of a satellite network; return information generated by the core network device in response to the request information, wherein the return information includes: first type of return information containing a target slice identifier, and second type of return information indicating that a terminal registers a network slice of another type, the target slice identifier being an identifier of a target network slice allocated to the terminal, and the network slice of another type being different from a type of a network slice requested to be registered by the request information.

9. The method of claim 8, wherein, the return information generated in response to the request information, comprising: obtaining indication information carried by the request information, wherein the indication information at least includes: a first identifier of a network slice requested to be registered, a target service, a subscription slice list corresponding to the terminal, a first location of the terminal, ephemeris information of a target satellite, the target satellite being a satellite corresponding to a satellite network covering the terminal, the ephemeris information at least including: a second location of the target satellite, an orbital height of an orbit in which the target satellite operates, the subscription slice list being used to record a second identifier of a network slice allowed to be accessed by the terminal, and the target service being a service carried by a network slice requested to be registered by the request information; in a case where the terminal requests to register the first type of network slice, and in a case where it is determined that the satellite network does not support the target service, generating the first type of return information according to the first identifier and the subscription slice list; in a case where the terminal requests to register the first type of network slice, and in a case where it is determined that the satellite network supports the target service, generating the second type of return information according to the first location and the ephemeris information.

10. The method of claim 9, wherein, generating the first type of return information according to the first identifier and the subscription slice list, comprising: in a case where there is a second identifier identical to the first identifier in the subscription slice list, determining the second identifier as the first type of return information.

11. The method of claim 9, wherein, generating the second type of return information according to the first location and the ephemeris information, comprising: determining a moving radius according to the first location and the second location; determining a coverage duration of network resources according to the first location, the second location and the orbital height; determining the moving radius and the coverage duration as the second type of return information.

12. The method of claim 11, wherein, in a case where the second type of return information is generated, the method further comprises: receiving target request information forwarded by the wireless base station, wherein the target request information is used to request to register a target satellite network slice, the target satellite network slice being a second type of network slice with a coverage range greater than or equal to a range corresponding to the moving radius and a duration of covering the terminal greater than or equal to the coverage duration; generating return information of the target request information in response to the target request information.

13. A core network device, comprising: The core network device comprises: a network entity of a ground network and a network entity of a satellite network, and the core network device is configured to perform the method for allocating resources of a satellite-ground fusion network in any one of claims 8 to 12 through the network entity of the ground network or the network entity of the satellite network.

14. A method for acquiring resources of a space-ground converged network, characterized in that, comprising: a terminal sending request information to a wireless base station, wherein the request information is used to request to register a network slice, and the request information comprises: first type of request information used to register a first type of network slice and second type of request information used to register a second type of network slice, the first type of network slice being a network slice of a ground network, and the second type of network slice being a network slice of a satellite network; The terminal receives return information transmitted by the wireless base station, wherein the return information includes: first type return information containing a target slice identifier, and second type return information indicating that the terminal registers an other type network slice, the target slice identifier being an identifier of a target network slice allocated for the terminal, and the other type network slice being different from a type of the network slice requested to be registered by the request information; The terminal sends a session request to the wireless base station in a case where the first type return information is received, wherein the session request is used to request to establish a session with the target network slice; The terminal sends target request information to the wireless base station in a case where the second type return information is received, wherein the target request information is used to request to register a target satellite network slice, and the target satellite network slice is determined according to the second type return information.

15. A communication system of a satellite-terrestrial converged network, characterized by, Comprise: A terminal, a wireless base station in communication with the terminal, and a core network device in communication with the wireless base station, wherein The terminal is configured to send request information, wherein the request information is used to request to register a network slice, and the request information includes: first type request information used to register a first type network slice, and second type request information used to register a second type network slice, the first type network slice being a network slice of a ground network, and the second type network slice being a network slice of a satellite network; The wireless base station is configured to receive the request information and forward the request information to the core network device, wherein the core network device includes: a core network entity of a ground network, and a core network entity of a satellite network; The core network device is configured to generate return information in response to the request information and send the return information to the wireless base station, wherein the return information includes: first type return information containing a target slice identifier, and second type return information indicating that the terminal registers an other type network slice, the target slice identifier being an identifier of a target network slice allocated for the terminal, and the other type network slice being different from a type of the network slice requested to be registered by the request information; The wireless base station is further configured to, in a case where the return information is the first type return information, allocate network resources of the target network slice to the terminal, the target network slice being the first type network slice or the second type network slice; The wireless base station is further configured to, in a case where the return information is the second type return information, transmit the second type return information to the terminal.

Images